Still trying to decipher a bit of the lingo/tools but...
I did an "adb reboot bootloader" and it just hangs at the "G'zone" bootup screen.
And an "adb reboot recovery" gives me the exclamation point with the android.
Where do I go about getting/enabling the bootloader or recovery console?
(Also did several variations on the power up and pushing volume down, picture button etc with no change in the default boot behavior.)
Fastboot Disabled
Looks like the source of my troubles is due to fastboot being disabled.
Doing "adb reboot fastboot" just causes it to reboot normally.
Attempting to find a way to enable fastboot mode.
Related
I cant seem to ADB from the bootloader. It works fine when the Xoom is on but when i enter "adb reboot bootloader" it reboots in to boot loader and stops working.
I have the necessary drivers as its showing "Mot Single ADB Interface" under device manager.
When i enter adb devices its saying "list of devices attached" but there is no device under it.
When i enter "adb get-state" it comes back with "UNKNOWN"
Please help
When you say that it stops working, are you trying to enter other ADB commands or are you using fastboot? I've just tried all of the same commands as you have entered and I get the exact same results. It seems to me (and I'm by no means an expert in adb having just learnt the basics so far) that in bootloader the standard ADB commands do not work. Once in bootloader it seems that you need to use the fastboot commands to flash an img file.
Also, in bootloader mode the xoom is no longer recognised by the pc, just press vol up + popwer and it should reboot, or I guess you could also enter fastboot reboot to do the same thing.
I just got this phone, and was told to unlock the bootloader and flash custom recovery as the first step, so I'm following this guide: forums.oneplus.net/threads/full-guide-setting-drivers-up-unlocking-bootloader-flashing-recovery-roms-kernels-rooting.291274/
I've been following it to a T and everything was working well. Once I got up to #3 and type in cmd "fastboot reboot" and it boots back to normal mode (so I can disable Cyanogen Recovery), typing "adb reboot bootloader" in cmd returns "error: device not found." If I'm in fastboot mode and enter "fastboot oem device-info" it returns true for tampered and unlocked so I know I have the bootloader unlocked. If I'm in normal mode, the phone shows up in device manager under portable devices. If I uninstall it, it disappears from the list. Once I unplug it and plug it back in, it pops back up in the same place, saying device installed correctly. If I try to update the drivers, most of the options from the Manufacturer list (see in the gifs from the guide) are gone, including the google ones.
How do I move from here? should I just wipe the whole thing and try again? What's the best way to do that? If I use the the USBDeview thing and remove the A0001 driver, will that allow me to put the android ADB Interface on the phone (Basically starting over)?
Thanks friends. Really excited to get going on Android!
threemor said:
I just got this phone, and was told to unlock the bootloader and flash custom recovery as the first step, so I'm following this guide: forums.oneplus.net/threads/full-guide-setting-drivers-up-unlocking-bootloader-flashing-recovery-roms-kernels-rooting.291274/
I've been following it to a T and everything was working well. Once I got up to #3 and type in cmd "fastboot reboot" and it boots back to normal mode (so I can disable Cyanogen Recovery), typing "adb reboot bootloader" in cmd returns "error: device not found." If I'm in fastboot mode and enter "fastboot oem device-info" it returns true for tampered and unlocked so I know I have the bootloader unlocked. If I'm in normal mode, the phone shows up in device manager under portable devices. If I uninstall it, it disappears from the list. Once I unplug it and plug it back in, it pops back up in the same place, saying device installed correctly. If I try to update the drivers, most of the options from the Manufacturer list (see in the gifs from the guide) are gone, including the google ones.
How do I move from here? should I just wipe the whole thing and try again? What's the best way to do that? If I use the the USBDeview thing and remove the A0001 driver, will that allow me to put the android ADB Interface on the phone (Basically starting over)?
Thanks friends. Really excited to get going on Android!
Click to expand...
Click to collapse
You probably don't have ADB enabled on your OPO, but you don't even need it for this. "adb reboot bootloader" is just a handy way of rebooting to fastboot without shutting down and holding the up volume button while turning it on. Once you get into fastboot by doing that, continue on as the guide says! (i.e. "fastboot flash recovery xxxx.img")
So I was trying to unlock the bootloader of my Huawei honor 6x, so I installed adb and tested it with "adb devices" and it found my phone. Next I entered "adb reboot bootloader" and the phone booted into the Fastboot & Rescue Mode. The next step was to enter "fastboot oem unlock [unlockcode]" but the cmd returned that remote access was denied. I tried it again with the same result. So I ran "adb devices" but my phone, although it was still connected, didn't show up.
So then I decided to install the Hisuite like the phone says but hisuit does not recognice the phone, but windwos makes a sound when I plug the USB in and out. I tried the restore system option but it says that my phone is not supported.
I tried rebooting it by holding down the power button, but nothing happens.
What do I do now? I have run out of ideas. How do I get my phone back?
Edit:
Managed to reboot the device by pressing all the buttons for 10 minutes. Don't know which combination worked but it did.
Thanks in advance.
While u are on fastboot and rescue mod ,long clicking the power button will reboot the device to system
Hello. I can't get my phone rooted in any way.
I want to Root so I can use TWRP app to flash TWRP recovery .img, and after that I can boot into TWRP recovery and flash new ROM. Correct????
What I've tried so far. OppoTools 1.6.5 = One key root gets hard stuck on Oppo logo at start-up and then I have to flash Coloros ROM again from recovery. Also KingRoot says app not installed. On windows version of KingRoot it gets to some percentage and then it Fails.
I have downloaded "unlocked bootloader" Coloros from this forum that was mentioned before ( Dropbox link )
I have also tried two different ColorOs versions.
I have installed 15sec ADB installer.
I plug my phone into PC and run CMD.
I type adb devices into command prompt and it detects my R7 plus.
then I try to command " adb reboot bootloader "
Phone restarts normally and doesnt go to bootloader. Tell me if im stupid, but isn't Bootloader different than Recovery? Because I can get to recovery command "adb reboot recovery"
I tried some weird button combination Vol+ Vol- + Power and phone semibricked for awhile and PC didnt even react USB driver correctly and almost waved the white flag on this case.
I've enabled USB-debuggin and OEM unlock from devices dev-options.
When I to type command "fastboot oem unlock" on command prompt is says Waiting for device. Nothing pops-up on device and nothing happens.
So now Im stuck on situation that my phone doesnt launch into bootloader where presumably "fastboot oem unlock" would work?
If you have flashed the version of Color OS that has bootloader enabled, you should simply need to go into the settings, enable USB debugging and OEM unlocking, then shutdown the phone before holding the power and volume+ buttons and waiting the ADB bootloader screen. After that, just plug it into the computer and follow the guide on flashing twrp with ADB.
Hello everybody,
I have a LG K520EMW with Android 10 Stock ROM,
According to Treble Check I have a system supporting system-as-root and a system partition A/B
So I downloaded a GSI from the phhusson's Treble Experimentations
But here are my problems :
- the phone won't boot at all on Fastboot mode (tried adb reboot bootloader, adb reboot-bootloader, both from sideload mode and normal mode, tried plugging the phone when it's off holding vol + or Vol - keys, and using QuickBoot, obviously didn't help because the phone is not rooted)
- the phone won't boot either on Recovery mode, it displays "No Command", i've tried all possible key combinations with vol +, vol -, power, camera, nothing happens and it stays on "No Command",
- Can't root with any tool, I tried KingRoot, KingoRoot, mtk-su
The only door open for me right now is sideload, I know I can type "adb sideload rom.zip" but the issue is I haven't unlocked bootloader, so I don't know what happens if I do this...
I've found nothing on the web about this phone, so if anyone have some informations or knows any procedure on another phone which would be applicable on this model, it would be great
Well, some news, i've figured out a dirty vay to access Fastboot mode, very very dirty :
I've tried, just to see what it does, adb sideload lineageOS-18.1-etc.img, and like a rabbit getting out of a hat, a recovery menu appeared and I could access Fastboot,
Now, I still have to find out why when I try fastboot oem unlock or fastboot oem device-id ( LG official procedure )
I have enabled OEM unlock in debugging options of course
On the Fastboot screen, Bootloader version is unknown,
When I try fastboot boot twrp.img, it answers "Download is not allowed on locked devices"
So, if anyone has an idea, I'd be very grateful