Develop Bugs

Cant enter recovery

my phone will not boot into recovery mode through CWM or by powering off and manually starting it. I get a dead android with a red triangle and ! sign, how can i fix this?
galaxy nexus (verizon)
4.0.2
rooted via Gnex tool kit

That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.

anton2009 said:
That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.
Click to expand...
Click to collapse
If you are rooted, you need to check the CWM thread for the file to delete through root explorer and then re-flash CWM to get it to stick.

Or use rom manager to flash it.

Jubakuba said:
Or use rom manager to flash it.
Click to expand...
Click to collapse
Ah yea, good point.
I prefer the difficult and manual way lol

Or re-flash your recovery from fastboot, then boot into it, and install whatever ROM you wanted.

OR don't flash cwm at all, just 'fastboot boot cwm.img', allow it a few seconds to enter cwm, then do your thing, flash your rom/much needed zips, reboot and you're good to go.
this world is all about choice ain't it?

bk201doesntexist said:
OR don't flash cwm at all, just 'fastboot boot cwm.img', allow it a few seconds to enter cwm, then do your thing, flash your rom/much needed zips, reboot and you're good to go.
this world is all about choice ain't it?
Click to expand...
Click to collapse
I agree. This option will let you boot into cwm once. when you finish there and reboot your nexus will wipe every trace of cwm. When you need it again just use the same trick again.
Sent from my Galaxy Nexus using XDA

anton2009 said:
That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.
Click to expand...
Click to collapse
Before anybody suggests I use search - I DID search, and it brought me to this thread.
Background: After unboxing my shiny new GNex last week, I immediately flashed stock yakju IMM76D using GNex Tookit.
So ... let me make sure I understand this. With stock recovery, when I fire up fastboot and select recovery, it is NORMAL to get the little dead robot with a red triangle above him? And the only way I've found to get out of it is to pull the battery? Seems odd.....
(I did temporarily flash CWM via the Toolkit and it worked fine. I don't want to leave it on as I understand it will prevent me from getting future OTA updates.)

As long as you run stock ICS, you'll always get that error upon every boot, even if you rename/delete the "boot-from-recovery.p" or whatever. The only solution is to flash a custom ROM and that error will be permanently gone.
At least what I've read and heard and what it's like for me.
If you get that error, your phone will reboot after a minute or so, but like I said it should be gone after flashing a custom ROM.

Theshawty said:
As long as you run stock ICS, you'll always get that error upon every boot, even if you rename/delete the "boot-from-recovery.p" or whatever. The only solution is to flash a custom ROM and that error will be permanently gone.
At least what I've read and heard and what it's like for me.
Click to expand...
Click to collapse
no.
you delete the file, then flash CWM.
it is not a error. that is the stock recovery and if you press vol up and vol down (might have to press power too) it should get you a menu.

Zepius said:
no.
you delete the file, then flash CWM.
it is not a error. that is the stock recovery and if you press vol up and vol down (might have to press power too) it should get you a menu.
Click to expand...
Click to collapse
I renamed it, it should be the same as doing away with it. However, upon rebooting, I faced that triangle. I ran stock 4.0.4 by the time.

you still have to reflash CWM after deleting/renaming the file.

Zepius said:
you still have to reflash CWM after deleting/renaming the file.
Click to expand...
Click to collapse
Which I did, but the problem wouldn't wanna go away.

Theshawty said:
Which I did, but the problem wouldn't wanna go away.
Click to expand...
Click to collapse
Step-by-step:
1) Delete /system/recovery-from-boot.p (need root of course).
2) Delete /system/etc/install-recovery.sh (need root of course).
3) Check to make sure that the above files no longer exist.
4) Flash CWM AFTER making sure the above files are not present on your system.
5) Reboot.

efrant said:
Step-by-step:
1) Delete /system/recovery-from-boot.p (need root of course).
2) Delete /system/etc/install-recovery.sh (need root of course).
3) Check to make sure that the above files no longer exist.
4) Flash CWM AFTER making sure the above files are not present on your system.
5) Reboot.
Click to expand...
Click to collapse
Thanks, but no thanks. I run a a custom ROM now so the issue doesn't seem to be there anymore.
I haven't read about the install script but ill be sure to follow your guide when and if I ever return to stock. They're awesome.
Sent from my Galaxy Nexus using Tapatalk 2

Theshawty said:
Thanks, but no thanks. I run a a custom ROM now so the issue doesn't seem to be there anymore.
Click to expand...
Click to collapse
Just for additional info, those files are not present on any original stock ROMs. They are added to a stock ROM if that stock ROM is updated, i.e., OTA update. They serve no purpose but to re-flash the stock recovery (i.e., which is the android lying on its back with the red !) On every boot of your device.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Just for additional info, those files are not present on any original stock ROMs. They are added to a stock ROM if that stock ROM is updated, i.e., OTA update. They serve no purpose but to re-flash the stock recovery (i.e., which is the android lying on its back with the red !) On every boot of your device.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ah, ok.
Speaking of nothing, what's the real deal with no OTA's available for yakju users? Is Google really working on fixing the notorious signal-drop issue?

Theshawty said:
Ah, ok.
Speaking of nothing, what's the real deal with no OTA's available for yakju users? Is Google really working on fixing the notorious signal-drop issue?
Click to expand...
Click to collapse
Who knows? I personally don't care, and no one else should either, as:
1) the OTA update file to IMM76D is availability for any yakju user to install,
2) the full IMM76D image is available to install,
3) the IMM76D source has been pushed to AOSP.
Those are three options for you to get IMM76D on your device, with the first one being the same as an OTA update.
For me, IMM76D runs perfectly fine, and better than ICL53F.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
For me, IMM76D runs perfectly fine, and better than ICL53F. 2
Click to expand...
Click to collapse
What radio are you using? The XXLA2?

Jellybean root

ok you need to have clockworkmod installed...
Code:
fastboot flash recovery recovery.img
(insecure boot.img)
unzip boot.img.zip, boot to bootloader and
Code:
fastboot flash boot boot.img
or flash JRN84D-insecure-boot.zip from recovery
-put the CWM-SuperSU-v0.92-mod.zip on your sd and flash
done. :good:
if you have problems...
flash Koush's Jellybean repack (IMM76I OR IMM30D) http://d-h.st/Gkh
If recovery isn't sticking for you, delete recovery-from-boot.p in /system
I can do this for the other superuser as well...this is chainfire's super su

Thanks. May I clarify if I have to do both to get root or either one?

mcdull said:
Thanks. May I clarify if I have to do both to get root or either one?
Click to expand...
Click to collapse
the boot image is insecure...not necessarily needed

Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.

mcdull said:
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
Click to expand...
Click to collapse
sure, give me a minute

Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?

pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
bootloader mode -> reflash clockwork recovery using fastboot.

pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img

Thanks guys appreciate the tip.

not working
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.

krishmasand said:
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
Click to expand...
Click to collapse
reboot, then open supersu and then update

Worked like a charm, I've got clockwork back after a little adb action and now I'm restoring some apps with titanium. Can't wait to see the development on this. Just think I almost sold this phone and bought a Galaxy S3 today, may wait a week or so now.

Thanks guys you are amazing!!!

Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update

tramane said:
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
Click to expand...
Click to collapse
ok your the second guy...first hasn't responded back. did you reboot and try again?
which "jellybean" version are you on? koush's on rom manager seems to be the best (no wifi issues for one)

ogdobber said:
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.

other superuser
still doesn't work, do you think you can try the other SuperUser app? D:

Enhanced said:
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
Click to expand...
Click to collapse
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM

[please delete]

IINexusII said:
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
Click to expand...
Click to collapse
I knew common sense told me that I would need to delete the /system/recovery-from-boot.p file, but it wasn't posted here so I didn't bother.
Thanks.

Can't start ClockworkMod (URGENT)

I've installed it correctly but once i boot into recovery I just get a picture of android with a warning sign being pulled out of his stomach...
so im with factory reset phone in the middle of flashing a new rom and can't continue

I really don't know what's wrong bud you may need to use a toolkit or a program to fast boot your device back to stock. Which version of the nexus do you have?
Sent from my Galaxy Nexus using xda app-developers app

I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you update your Android build either using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Click to expand...
Click to collapse
This is from Efrant's Android 101 guide: http://forum.xda-developers.com/showthread.php?t=1812959

Don't delete the files, simply rename them. If you ever want to get back to stock recovery (for instance, for an OTA to install you need it to be stock) you can simply name it back to original and reboot.

Petrovski80 said:
Don't delete the files, simply rename them. If you ever want to get back to stock recovery (for instance, for an OTA to install you need it to be stock) you can simply name it back to original and reboot.
Click to expand...
Click to collapse
or you can just flash the stock recovery with fastboot.

thank you for the super fast answers guys
i tried to rename them with astro but says that i don't have permissions for that
i'm rooted

Fking1 said:
thank you for the super fast answers guys
i tried to rename them with astro but says that i don't have permissions for that
i'm rooted
Click to expand...
Click to collapse
You have to mount /system as read/write

DynamicRam said:
You have to mount /system as read/write
Click to expand...
Click to collapse
no idea how to do that

Fking1 said:
no idea how to do that
Click to expand...
Click to collapse
Use another file explorer such as Solid Explorer. https://play.google.com/store/apps/details?id=pl.solidexplorer

This is amazing, got help within minutes and as i write this the new rom is being installed, thank you so much!

[OTA][TWRP] ZVA to ZVC modified OTA (See Notes)

DISCLAIMER:
Your device, your responsibility. I am happy to offer these tools but understand the risks before even considering.
Thank you.
OK, I've finally got a working OTA so I'll post this for now.
If we are able to improve on this without breaking something else I will edit this later.
IMPORTANT NOTES:
1) This has been tested and will flash TWRP to complete the OTA process.
2) At time of original post you will lose Loki exploit. I have provided suggestions in Post #2 how to get around that.
3) I had latest SuperSU and root prior to flashing this. It held without further action.
4) I highly recommend making a backup and storying a copy off your phone before starting in case TOT is required.
We had several issues in testing and that backup helped get back to a place to keep testing.
5) Do not wipe cache/dalvik between flashes of the OTA zip. You'll lose the stage counter and have to start over.
6) This ZIP will only work on a complete (odexed, bloated) stock ROM. You can be rooted but you cannot be debloated or deodexed.
If you made modifications to the stock ROM you will need to undo them. The most common, wifi tether, I've addressed in Post #2.
Link to current working OTA:
http://www.rwilco12.com/Files/Garwynn Projects/LS980/ZVAtoZVC/ZVAtoZVCTest7.zip
Instructions:
1. Download and store on phone. You do not need to store in /cache/fota.
2. Reboot to TWRP. Before flashing this ZIP you will need to turn off signature verification.
This is because I broke the signature when I modified the OTA.
You can certainly turn back on after this has been flashed.
3. Flash ZIP. This is phase 1.
It checks that everything is right for patching, flashes the modem and replaces kernel with TWRP.
When this finishes, reboot to system. This will load TWRP again but from boot partition.
4. Flash exact same ZIP again. This is phase 2 and very quick as it just flashes TWRP to recovery partition.
When this finishes, reboot back to recovery.
5. Flash exact same ZIP one more time to execute phase 3.
This is the actual patch process and will take some time.
It also undoes the aboot revert and drops the ZVC stock kernel in boot partition so TWRP is no longer there.
6. When last flash finishes, wipe cache/dalvik and reboot to system.
If the update fails on any step, stop and restore the recommended backup.
If that doesn't work use the ZV8 TOT and restore your phone.
(This is why I suggest backing everything up before update, better to be safe than sorry)
Thanks to autoprime, savoca and viperboy for bearing with on testing so far.
Thanks and hopefully we'll be able to improve on this in the coming days.

Supplement Post:
Pre-OTA Install Q/A:
1) What if I have Wifi Tether installed?
A: Use ZVAServices.zip in the post below, then flash this zip.
This rule applies for anything that fails on first part. If a patch check fails it means the file doesn't match ZVA stock and needs to be swapped out.
***WARNING***
The information below will show you how to get in and out of TWRP after OTA.
If you didn't use the OTA zip in the first post you must flash TWRP into recovery before anything else. Let's not brick any more, okay?
Please do not use these files before and understand the process before trying this.
This method of getting in and out of TWRP breaks download mode while aboot is reverted.
3 people have bricked and cannot flash a TOT already because the steps were not followed.
There are better solutions in the works now and should be posted soon.
2) What if I want to use TWRP?
A: Download this file:
http://www.rwilco12.com/Files/Garwynn Projects/LS980/ZV8_aboot.img
..and this file for later:
http://www.rwilco12.com/Files/Garwynn Projects/LS980/ZVAtoZVC/ZVCRadio_Full.zip
and from ADB shell or terminal, su then the following:
Code:
dd if=/sdcard/Download/ZV8_aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
(assumes file is in Download folder)
Note: I have assumed you already have TWRP flashed from OTA.
If you're doing this from anything else, flash TWRP in Flashify before anything else.
... then reboot into recovery.
3) Okay, but if I flash the aboot revert I break the stock kernel and download mode, right?
A: Yes, but that's why you grabbed that ZVCRadio_Full.zip.
Flash that in TWRP right before booting back to stock KitKat or to fix download mode.
4) Will there be an easier way for this?
A: Probably, but I don't like leaving loose ends. This is a workaround until a safer solution (in works by Savoca and others) are ready.

Count me in for testing. Im a trucker so battery life and gps a must. Ill test them heavily

I am currently on rooted ZV8 with twrp as the recovery, can I flash this directly or will I have to first update it to ZVA ?

Thanks garwynn for the extremely quick work. You are awesome!
Sent from the Moon using Tapatalk with my G2

Waiting for the full ROM. OTA seems a bit risky.

What is the md5 hash? I think i have a bad download. I got the following:
eb477d1d078b7bad0c7f0565d0717a31

Loki exploit
Mr: garwynn, what's the Loki exploi? And could we still keep rooting after installing this?Thanks.

yournamehere said:
What is the md5 hash? I think i have a bad download. I got the following:
eb477d1d078b7bad0c7f0565d0717a31
Click to expand...
Click to collapse
If you're trying sig check that will fail. I did not re-sign this. I'll generate md5 hash in a bit.
Sent from my LG-LS980 using Tapatalk

No sig check here it just keeps failing about half way. Also using twrp 6.2.3.3 blue

fail
yournamehere said:
No sig check here it just keeps failing about half way. Also using twrp 6.2.3.3 blue
Click to expand...
Click to collapse
as soon as I hit install it gives me error as well.

This isnt an april fools thing right?
Sent from my LG-D801 using Tapatalk

bishaarcc said:
as soon as I hit install it gives me error as well.
Click to expand...
Click to collapse
What does it show in the log? And definitely not joke.
Sent from my LG-LS980 using Tapatalk

Hmmmm never thought about that. Been on vaca last week. The size is right for the uodate as my phone has the full ota ready to install but im rooted and have wifi hotspot.

yournamehere said:
Hmmmm never thought about that. Been on vaca last week. The size is right for the uodate as my phone has the full ota ready to install but im rooted and have wifi hotspot.
Click to expand...
Click to collapse
Wifi tether is the problem. Give me 30 mins and I'll attach a zip to fix that.
Sent from my LG-LS980 using Tapatalk

Hey garwynn, do you think flashing this over stock rooted would work? Just an idea.
Edit: Stock rooted ZVA*
Sent from my LG-LS980 using XDA Premium 4 mobile app

jthein1989 said:
Hey garwynn, do you think flashing this over stock rooted would work? Just an idea.
Edit: Stock rooted ZVA*
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's what I did. But if you have the wifi tether hack installed that has to be undone first.
The attached file will do the trick. Flash this first in TWRP before trying the modified OTA.

No rush, but will we see a ZVC full, stock rooted ROM anytime soon? I am relying on the permanent sim unlock, so have to be extra careful.

Supplement Post:
1) What if I have Wifi Tether installed?
A: Use ZVAServices.zip in the post below, then flash this zip.
2) What if I want to use TWRP?
A: Download this file:
http://www.rwilco12.com/Files/Garwynn Projects/LS980/ZV8_aboot.img
..and this file for later:
http://www.rwilco12.com/Files/Garwynn Projects/LS980/ZVAtoZVC/ZVCRadio_Full.zip
and from ADB shell or terminal:
Code:
dd if=/sdcard/Download/ZV8_aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
(assumes file is in Download folder)
... then reboot into recovery.
3) Okay, but if I flash the aboot revert I break the stock kernel, right?
A: Yes, but that's why you grabbed that ZVCRadio_Full.zip.
Flash that in TWRP right before booting back to stock KitKat.
4) Will there be an easier way for this?
A: Probably, but I don't like leaving loose ends. So for now I offer a workaround.

Cleaned up instructions so there's a better understanding of what's going on.
Hopefully that resolves most questions. If not, feel free to keep asking and I'll be happy to answer.

[Q] 5.0.1 Rooted to 5.0.2 Without Data Loss

For some reason I'm just not able to Google this answer or find it here on XDA.
I'm on 5.0.1 (LRX22C) and want to go to 5.0.2 (LRX22G). I have downloaded an OTA update capture and tried to adb sideload it.
It failed. After a sec I thought, "duh. I'm rooted with franco kernel installed." I then did the following:
* Used SuperSU to unroot
* Booted to bootloader
* Flashed stock recovery and kernel
* Rebooted to recovery
* Attempted adb sideload again
This still gave a failure message.
The only other post I've seen where anyone is attempting the same suggests to use Nexus Root Tookit. I'm running Xubuntu. I've loaded it through wine but all the files it downloads are failing hash checks (though the app).
Can anyone post how to go from rooted 5.0.1 to 5.0.2 (LRX22G from LRX22C) without loosing user land data? I'd really do not want to flash the recovery image.
Notes: When trying to sideload with latest CWM recovery the script says that I'm on 4.0.4 (I think) and with TWRP it says I'm on 4.3. With stock recovery it gives me an error about the recovery script (7) or something similar.
Thanks,
Mike G.

Make sure you have downloaded the proper OTA for Nexus 7(2013).
Hashcheck fails in Nexus Root Toolkit is common.After Hashfails,there will be a dialog box which contains the steps to do it manually with the Link to the files.Download it & follow the instruction.
I hope this helps

I'm having the exact same problem. I'm attaching what's appearing on TWRP.

All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.

I just used wugfresh's toolbox to do it. A piece of cake. I enjoyed a cup of coffee while I watched being updated.

You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.

yosmokinman said:
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
So I can just ”fastboot flash system system.img" from the 5.0.2 image and not loose data?
That seems like it would be the easiest. I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Sent from my Nexus 7 using XDA Free mobile app

^Yes. It's a good idea to flash boot as well just to get in the habit of it, it didn't change this time I don't think but I could later. Only flash the bootloader if it's a new version no need otherwise.
I simply ran:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Done, flash su through twrp to get root back.
You probably don't need to format cache but theres no reason not to and it could save you some trouble.

newkydawg said:
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
Click to expand...
Click to collapse
that worked perfectly for me. thx

mikejr83 said:
I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Click to expand...
Click to collapse
NRT opens a terminal window (a real-time log) and tells you exactly what it's doing while it does its work.

All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
I have a n7 2013 I have already rooted and installed twrp and SuperSU. I'm currently running 4.4.2 and to update to 5.02. Currently I'm getting the ota update msg for 4.4.3 which I've continued to ignore. With google not messaging me to update to 5.02 makes me think it's required to go to 4.4.3,4.4.4,5,5.02 is that correct? Or can one jump directly to 5.02? I want to keep root and twrp and my existing data I see mentioning of restoring stock recovery first. Why would one do that? What's the point of installing a custom recovery in the first place?
Long time ago I read that ota will work when rooted, but you'll lose root which then can be restored with twrp without losing data. Is that no longer true? Or is it only true of KitKat but not lollipop?