fabiobassa Posted March 23, 2021 Share Posted March 23, 2021 no it is not strange , when you WIPE emmc you have NOTHING in the board, only the MASKROM mode that is buried in the SOC. maskrom is even early than idbloader; maskrom resides in SOC, idbloader resides in nand or emmc. BUT..... since you are speaking to maskrom via teh USB subsystem ...... you cannot speak to the nand/emmc UNTIL you load at least idbloader. That is the reason why rkdeveloptool doesn't give any command: in this moment rkdeveloptool does not even know of the existence of the nand/emmc Once via the maskrom-usb set of instruction you load a idbloader ( something that initializes the ddr and the internal storage nand/emmc) , well starting from THIS moment rkdeveloptool can speak with the nand/emmc NOTE that you can just upload the idbloader : ./rkdeveloptool db loader-bla-bla.bin OR you can upload and the BURN.. in this second case: ./rkdeveloptool db loader-bla-bla.bin and then ./rkdeveloptool ul loader-bla-bla.bin Some very INTERESTING studies by @jock revealed that is also usefull program the idbloader with another tool calle upgrade_tool that provides a sort of " formattation" of internal storage. Once idbloader is in place , well we can start speaking of which type of OS ( android or linux) we can flash into the board Hope this helps 0 Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.