Develop Bugs

[Q] Recovery doesn't work or not installed?

I'm not sure why but my recovery mode doesn't work, it just show me a little Android with a red signal and no one letter...
My phone is already rooted but I dont remember if I installed a recovery mode or if it was part of the root process, I need to install a "sound fix" zip, but I can't right now...any ideas??? Can I fix it without lose my data?

I think you don't have a custom recovery yet... Flash one and good to go.
Sent from Google Nexus 4 @ crSimple

Yes, you can install or flash and update recovery without losing data.
If proper USB drivers are installed and you can use ADB with the GNexus while is in developer mode, then you are ready.
Download latest CWM Recovery or TWRP Recovery.
Reboot the phone to bootloader mode. If your ROM has it in power option, you can use that to boot into bootloader.
Otherwise with adb: adb reboot-bootloader
On your computer, put above the recovery .img file in same folder as adb and fastboot executables.
then: fastboot flash recovery name-of-recovery-file.img
You will get an OK, success confirmation if all done properly. Now you can boot to recovery. Done.

Is there a simpler way? I'm not very "acquainted" with ADB :/, something more, ADB for X64 is about 480mb! Is that normal or Am I downloading another thing???

Jerber said:
Is there a simpler way? I'm not very "acquainted" with ADB :/, something more, ADB for X64 is about 480mb! Is that normal or Am I downloading another thing???
Click to expand...
Click to collapse
If you have never used ADB tools or ever attempted bootloader commands, it is probably not recommended for you to change stuff around because there may be a chance something can go wrong and you might not have immediate help to restore your phone. Doing these changes are permanent to your phone, so just keep that in mind if you still want to attempt it (eg you don't know how to return it to stock yet).
Personally, I don't recommend all-in-one tools because of the same reason as above, you don't learn anything if you need to do something command related or mess up.
It sounds like your phone is still bootloader locked to stock version of android but you may have have used SuperSU or some root exploit to get root previously.
All you need are 4 things:
Read and understand the guide @efrant posted for newbies: http://forum.xda-developers.com/showthread.php?t=1812959
Universal Naked Driver
ADB lite - ADB with less stuff, around 2MB
CWM or TWRP recovery img file (previous post)
When you think you are ready just post back.

kaijura said:
If you have never used ADB tools or ever attempted bootloader commands, it is probably not recommended for you to change stuff around because there may be a chance something can go wrong and you might not have immediate help to restore your phone. Doing these changes are permanent to your phone, so just keep that in mind if you still want to attempt it (eg you don't know how to return it to stock yet).
Personally, I don't recommend all-in-one tools because of the same reason as above, you don't learn anything if you need to do something command related or mess up.
It sounds like your phone is still bootloader locked to stock version of android but you may have have used SuperSU or some root exploit to get root previously.
All you need are 4 things:
Read and understand the guide @efrant posted for newbies: http://forum.xda-developers.com/showthread.php?t=1812959
Universal Naked Driver
ADB lite - ADB with less stuff, around 2MB
CWM or TWRP recovery img file (previous post)
When you think you are ready just post back.
Click to expand...
Click to collapse
Thanks, I'm gonna read it now!
My GN is on 4.3, with bootloader unlocked and rooted (of course) my intention with CWM is install a soundfix cuz GN has a VERY low sound and I'm missing some calls and sms all time :/
I used to have a Xperia device and I remember that root process and the installation of CWM are very easy in comparison with my GN, I thought it will be easy too.

Jerber said:
Thanks, I'm gonna read it now!
My GN is on 4.3, with bootloader unlocked and rooted (of course) my intention with CWM is install a soundfix cuz GN has a VERY low sound and I'm missing some calls and sms all time :/
I used to have a Xperia device and I remember that root process and the installation of CWM are very easy in comparison with my GN, I thought it will be easy too.
Click to expand...
Click to collapse
Should be simple for you from what is mentioned above.
After installing the drivers and adb, phone connected via usb, Steps 1-3
1. Set your phone to bootloader mode. 2 ways to do it:
A. Turn phone off, VOL+ and - and power button at same time until you see it.
B. Using PC: after adb is installed, use command terminal and go to folder it is installed in and type adb reboot-bootloader
2. In bootloader mode, flash the CWM recovery.
With your recovery .img file located in the same folder as adb and fastboot executables: in the terminal type fastboot flash recovery recovery-clockwork-6.0.4.3-maguro.img (or the toro or toroplus with the CWM image depending on your Galaxy Nexus type).
3. Boot to recovery.
Hit Vol button a few times until you see recovery on the screen while in bootloader mode, press power button to continue.
Don't forget to make a backup of stuff, including your EFS/radio folder.

Try this www.youtube.com/watch?v=foLQCNxroHw&app=desktop&persist_app=1&hl=en-GB&guid=&client=mv-google&gl=RO it's a complete guide but it's for nexus 10. Same thing with the gnex

Thanks a lot guys! I will try to do it!, something more
*I saw another option but I'm not sure if it work with the GN, some people say that a easy way is just download the app "Rom manager" from the Play Store and install the CWM from the app, what do you think about it?
*I have some little problems with stock 4.3 (for example, my bluetooth is useless :S), Do you recommend me switch to a stable CM rom (like the last official 10.2.0)?
Im not hurry for 4.4 or CM11, but I'm not sure if 10.2.0 has some bugs, anyways seems like a better option than the stock 4.3.

Can't Get Into Recovery Mode

Following the steps provided by Team Win on http://teamw.in/project/twrp2/213, I flashed the pre lokid recovery img that they provided, however I can't access it, I get "Secure booting Error! Cause: boot certification verify"
My firmware is V50020d(seems to be a troublemaker)
Command used
Steps Taken:
1. Enter adb shell
2. Get root using su
3. dd if=/sdcard/openrecovery-twrp-2.8.0.1-awifi.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
How I try to enter recovery mode:
Power + Down, Release Power, Press and Hold Up + Power, Release All Three, Press Power again and again

Here are some suggestions:
First, go here
1. If you don't have root, see the instructions in the above thread to run ioroot.
2. To flash TWRP, follow the instructions in Step 3 of the first post.
3. After that, you can update to one of the later versions of TWRP here. TWRP 2.7.1.0 seems stable, not sure about the latest one
3. After you do that, you will probably want to flash your boot environment back to 4.2.2 base to avoid problems with AOSP roms that you might want to install later. If you're only going to use stock-based roms, you probably won't want to do this. Look here for instructions for that here.

woody1 said:
Here are some suggestions:
First, go here
1. If you don't have root, see the instructions in the above thread to run ioroot.
2. To flash TWRP, follow the instructions in Step 3 of the first post.
3. After that, you can update to one of the later versions of TWRP here. TWRP 2.7.1.0 seems stable, not sure about the latest one
3. After you do that, you will probably want to flash your boot environment back to 4.2.2 base to avoid problems with AOSP roms that you might want to install later. If you're only going to use stock-based roms, you probably won't want to do this. Look here for instructions for that here.
Click to expand...
Click to collapse
The linked provided only works for 20a and 20b, do you have a mehtod that works for 20d?

Oh, you will need to edit the .bat file to change the reference to 20b to 20d. That should do it.

woody1 said:
Oh, you will need to edit the .bat file to change the reference to 20b to 20d. That should do it.
Click to expand...
Click to collapse
So now the message is "Device Unlock, so Boot Success" however still no recovery mode.
Am I better off going back to stock and trying again?

kidanime3d said:
So now the message is "Device Unlock, so Boot Success" however still no recovery mode.
Am I better off going back to stock and trying again?
Click to expand...
Click to collapse
I just did this recently, starting with a stock recovery of 20d and ending up with root and TWRP, so I know this should work. First, do you have root? When you ran the bat file to install TWRP, did it appear to run successfully?

kidanime3d said:
So now the message is "Device Unlock, so Boot Success" however still no recovery mode.
Am I better off going back to stock and trying again?
Click to expand...
Click to collapse
Getting in to the recovery also seems to have a problem if the device has a cable plugged in. I find that If I do an adb reboot recovery and then I unplug the device it will enter recovery. I believe this issue is fixed in later recoveries but the one that you should now have on your device will not properly boot recovery with a cable connected.

woody1 said:
I just did this recently, starting with a stock recovery of 20d and ending up with root and TWRP, so I know this should work. First, do you have root? When you ran the bat file to install TWRP, did it appear to run successfully?
Click to expand...
Click to collapse
Flash stock via the LG Support Tool, then did everything again and now running CM11 M10
Beer

muiriddin said:
Getting in to the recovery also seems to have a problem if the device has a cable plugged in. I find that If I do an adb reboot recovery and then I unplug the device it will enter recovery. I believe this issue is fixed in later recoveries but the one that you should now have on your device will not properly boot recovery with a cable connected.
Click to expand...
Click to collapse
You were right adb caused an issue for some reason.
Beer

I installed 7.1.1 by mistake. What now? Help

I bought my 5X in October and came here to root my phone and be able to use the ElementalX and the Advanced Interactive Governor tweaks.
Everything was working fine and my phone really performed outstandingly.
Then I saw the OTA 7.1.1. popping up. I didn't allow it until I installed it by mistake yesterday...
Now I'm stuck with google asking me to lock the bootloader.
I can access the bootloader. I get a lot of options.
I can access the recovery mode and it gets me to RecoveryProject 3.0.2-2 by Teamwin.
I already have the Android platform tools on my desktop and it's working.
From there I have 2 questions :
1. Is there a way to not wipe all the contents on my phone? I didn't get the chance to backup all the data on it.
2. After that how can I get my phone working with the latest android version as I was before, unrooted and running with EX Kernel Manager.
Thanks for your help.

1. try installing the supersu zip from the recovery
2.EX Kernel Manager cannot work without root. so you need to root your device

Thanks a lot for you answer!
1. So by installing SuperSu zip from the recovery I would be able to backup my phone data?
2. I meant rooted sorry. So my phone is already rooted and I'm fine with staying that way.

Enzoli said:
Thanks a lot for you answer!
1. So by installing SuperSu zip from the recovery I would be able to backup my phone data?
Click to expand...
Click to collapse
yes
you can actually backup you device from TWRP recovery.
flash the supersu zip and you will boot normally without any data lose

Insane! thanks a lot.
One more noob question. I got the latest superSu zip.
How can I flash it from the recovery?
How can i transfer it to the phone?

Ok I almost got it.
My only question left is how can I transfer the SuperSu zip file onto my phone since I don't have access to anything else than Bootloader and TWRP

Enzoli said:
Ok I almost got it.
My only question left is how can I transfer the SuperSu zip file onto my phone since I don't have access to anything else than Bootloader and TWRP
Click to expand...
Click to collapse
adb sideload from twrp

OK guys thanks. When I use adb sideload in twrp advanced menu it gets stuck on "Starting ADB sideload feature... "
And when I type ADB devices on the command prompt it does not show my device but if I'm just in the menu before sideload it does find my device and says the serial number + recovery.
What am I doing wrong?
Thanks for helping.

You should be able to transfer files while being in recovery using MTP mode.

How do I use MTP mode? Sorry what does that mean. Can't find an explanation on the internet.
I've looked at all the options in the menu but can't find such a option.
I really feel stupid.

Ok guys I transfered SuperSu to my phone using adb push.
I flashed my phone with SuperSu but when i reboot my phone, it still tells me I need to lock my bootloader.
What shall I do now?

I keep going to the Googl screen with the little locker and then I reach the No Command screen.
The phone won't boot into Android no more. Guys please help I'm desperate. Is my phone dead?

Ok so I guess my phone is now in bootloop.
Still anyone willing to help?

OK I tried many things in despair and now I cannot enter the recovery mode anymore. It just gets stuck on the teamwin screen.
Guess it's time to buy a new phone.

So miracle I could enter the recovery.
Now I don't know where to go. I would like to be able to enter normal android but my phone will keep on showing android screen with little lock and the end on the No command screen. Endlessly.

Ok. THread can be closed. I managed to flash a factory image. Lost all my data but I got a working phone so I guess it's not to bad.

...

Enzoli said:
Ok. THread can be closed. I managed to flash a factory image. Lost all my data but I got a working phone so I guess it's not to bad.
Click to expand...
Click to collapse
If you ever need help on updating your software to the latest Android version, follow my guide as a reference:
https://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk

Boot-To-Root Boot-Loop

My setup
Pixel XL from Verizon
Bootloader unlocked
Bootloader Version 8996-0121001-1611091517
Baseband 8996-012511-1611190200
Android 7.1.1 NOF26V
Kernal 3.18.31-g367e645 Dec 7, 23, 2016
Twrp Version 3.0.2.0 RC1
I have tried following this guide to get root access https://www.xda-developers.com/root-is-now-available-for-the-google-pixel-and-pixel-xl/
My steps are
1. boot phone into fastboot
2. from pc run fastboot boot boot-to-root.img
3. the phone reboots
4. Phone is stuck with the 4 colored dots jumping over each other
5. i've given this screen up to 30 minutes with no results.
6. Forcing a reboot causes the same issue
7. Flash stock android via the official google factory image method
I have attempted this other method as well http://www.theandroidsoul.com/root-pixel-xl-magisk/
But after TWRP says it's successful, i boot into my OS and there is no supersu and if i manually install supersu, it says no root access.

You are doing it the old way that was for 7.1.
You want SU 2.79 SR3
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
And you want TWRP RC1.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
I would not install TWRP at this point. So copy SU to your phone. Then boot to TWRP.
Fastboot BOOT twrp.img
With twrp.img being the correct name of the file. Then in TWRP install the SU you copied.

The old way... Sheesh, there's only so much space up here. But thank you. You've saved be a big headache when my XL finally arrives.
Edit: you boot TWRP, not flash through fastboot?

Larzzzz82 said:
The old way... Sheesh, there's only so much space up here. But thank you. You've saved be a big headache when my XL finally arrives.
Edit: you boot TWRP, not flash through fastboot?
Click to expand...
Click to collapse
You boot it, always.
If you want to install it you copy the twrp ZIP to the phone. Boot it with the TWRP image file then install the twrp zip from within twrp.
Gotta be done that way. Partition layout has changes, they are a bit intertwined now.
I dont install TWRP anymore.

That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.

Larzzzz82 said:
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Click to expand...
Click to collapse
That might be doable, I am not a ROM guy. Root and kernel only....and I always got a PC.

so I would just want to pull down the twrp RC1 image file, boot from fastboot without flashing it, and use it to flash the SU SR3? All i want is root access at the moment on the pixel XL.
if i understand this right, this will just give me SU with root, and not install any form of TWRP.

steber04 said:
so I would just want to pull down the twrp RC1 image file, boot from fastboot without flashing it, and use it to flash the SU SR3? All i want is root access at the moment on the pixel XL.
if i understand this right, this will just give me SU with root, and not install any form of TWRP.
Click to expand...
Click to collapse
Exactly.

Larzzzz82 said:
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Click to expand...
Click to collapse
You don't need a PC if you just install TWRP.

TonikJDK said:
Exactly.
Click to expand...
Click to collapse
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?

steber04 said:
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
Click to expand...
Click to collapse
What files are you pushing that you cannot just load directly with the device powered up?

steber04 said:
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
Click to expand...
Click to collapse
You will need fastboot, so you can fastboot boot twrp. I don't push the SU zip with adb, I just copy/download it to the phone before I reboot into Fastboot. Make sure you get Fastboot from Google, not the Minimal one.
https://developer.android.com/studio/releases/platform-tools.html

Unable to install twrp

So this is my millet 6, I try Adb, TWRP manager, but my computer can use U disk mode, you can also use the official phone assistant to install the development version, but can not install the TWRP Manager to TWRP Recoey. You can view the video, hope everyone can help me.
https://www.facebook.com/100015187571561/posts/614327575750156/

潇霄小云 said:
So this is my millet 6, I try Adb, TWRP manager, but my computer can use U disk mode, you can also use the official phone assistant to install the development version, but can not install the TWRP Manager to TWRP Recoey. You can view the video, hope everyone can help me.
https://www.facebook.com/100015187571561/posts/614327575750156/
Click to expand...
Click to collapse
Did you unlocked bootloader? You have to flash twrp with adb while the phone is in fastboot mode.

mArIuS% said:
Did you unlocked bootloader? You have to flash twrp with adb while the phone is in fastboot mode.
Click to expand...
Click to collapse
I am sure to unlock bl。

The twrp manager always downloads the img file repeatedly, as if the img file could not be used. My moto xforce button is blue and can be installed after clicking twrp

Hey, I'm having the same issue here :S Already tried with Linux and Windows, both same issue... Fastboot detects my device, but it got stuck in there... I'm using the latest version of stock firmware...
I never faced this issue before, for sure my phone is unlocked and I already flashed like hundreds of time in the past. Is there something new?
Thanks!