Quote:
Originally Posted by petrovich
Thanks a lot!
Well, none of these two helped with adb reboot-bootloader command(same complaint), but AndroidTool said(not sure what button was pressed then) "Found One Loader Device" and did create ExportImage files by my requests. So now I probably have the backup(or see the question below).
I'm going to flash Onx c67ml ROM to my Boyue T62D. Is this abd "not found device" on reboot-bootloader critical, or only the AndroidTool's "Found One LOADER device" is sufficient and thus I can continue while I see it, just ignoring the adb complaint?
Thanks again.
Upd. Please ignore the question. I couldn't wait and continued at my own risk. The answer is(at least in my case) "yes, ignore the adb complaint". Now I'm playing with my Onyxized Boyue device. Thanks for the advise with buttons!
|
Glad it helped! Sorry for my short advice, I was in a kind of hurry.
Long answer:
ADB is very helpful to get remote access to your device (including system partition) but you don't need adb to get into bootloader mode, the aformentioned key combination does the same trick as adb reboot-bootloader.
In this bootloader mode access to the different portions of the device memory is possible with the tools you mentioned (backup, flash, change size of partitions ... even bricking it is quite easy).
Your adb problem could have been related to different reasons.
Most often the driver is not properly installed, sometimes (on the device) SuperUser.apk is not giving root permission to adb (due to the connected to USB screen it doesn't show up) and it has to be set to give it allways to system apps. In this thread there are some posts describing how to overcome various adb problems.
Enjoy the new ROM!