Develop Bugs

[Q] Gingerbread, recovery mode = FAIL

Hey guys!
I've tried to update my android 2.2 to gingerbread, both with the official update and the oxygen update, with the same result: my phone reboots, starts doing something - I get a green statusbar - and after about 1/4th of the bar it all ends up with a phone with a read exclamation mark and a red triangle.
The first time I got there, I though this was something that should happen, and left my phone around for two hours without anything happening.
I googled around and ended up doing a hard reset, which didn't change a thing.
I then tried to go into recovery mode from the boot meny, and end up with the exact same result.
So... what the hell is happening? Anyone got a clue? I would really appreciate some kind of sollution!

Its probably because you have a corrupted update file.
Try downloading it again.
If your branded to a certain carrier, then download the update for that carrier.

I've downloaded the update each time I've tried to make the update. I've tried with the oxygen ROM too, and tried loading recoverymode both from boot menu and clockworkmod. Nothing works. Amen...

So let me get this straight, you are trying to do OTA updates with a custom ROM + clockworkmod!?
It does not work like that. OTA updates are ONLY for 100% stock phones (ok, you can have Radio S-OFF, but no root). As you are using a custom ROM, why don't you just flash a Gingerbread based ROM instead of trying to mess around with OTAs, which obviously is impossible?

Uh, well, I have the standard ROM, but I did not know that it's impossible to install OTA updates when my phone's rooted. But it obviously doesn't work out
I've tried with the oxygen gingerbread release too, but same **** as I described in my original post happens. So what I've done:
- Install OTA update - failed
- Install oxygen-rom - failed
then, Hard reset +
- OTA update, without root - failed
- go into recovery mode from boot-menu - failed
hard reset + root +
- oxygen gingerbread - failed
- recovery mode from boot meny - failed
- recovery mode from ROM manager - failed
I really hoped that a hard reset would do the trick, but there you go...

Again, you cannot get any OTA because you have ClockworkMod.
Sent from my Desire HD using Tapatalk

So... How do I get any update if I can't install Oxygen either? (assuming Oxygen's ROM also qualify as OTA...)

Flash this ROM from CWM Recovery like any other ROM. Its Gingerbread with root, nothing else added.

Thanks!
But I'm still having serious problems getting into recoverymode, or even backing up my existing ROM. It seems whenever I do ANYTHING that requires my DHD to reboot, it ends up with the phone-with-red-eclamationmark-sign. No matter if I've done a hard reset either...

Holene said:
Thanks!
But I'm still having serious problems getting into recoverymode, or even backing up my existing ROM. It seems whenever I do ANYTHING that requires my DHD to reboot, it ends up with the phone-with-red-eclamationmark-sign. No matter if I've done a hard reset either...
Click to expand...
Click to collapse
The red exclamation mark is the stock recovery, so you dont have clockwork recovery. I would recommend starting from scratch installing clockwork then all should be good

Oh, nice to know But I used ROM manager to flash clockwork recovery (at least it said so).
When you say start form scratch, would that imply hard reset, root it, flash CWR and hopefully it will work?

Holene said:
Oh, nice to know But I used ROM manager to flash clockwork recovery (at least it said so).
When you say start form scratch, would that imply hard reset, root it, flash CWR and hopefully it will work?
Click to expand...
Click to collapse
Yes, you did S-off? As that would explain why clockwork didn't flash

Oh, well, uhm.
No.
Damn Thanks!

[Q] Having Issues Upgrading to new OTA

I am having trouble getting the 4.04 update to work, I get to the android, then it lays down with a red exclamation point out of his stomach.
I was running Kang B36 w Franco Milestone
I used option 9 on the toolkit my build toro 4.02
I restored facotry image for my phone via option 8
I reflashed stock recovery via option 10
finally I locked my bootloader via option 11
restarted my phone downloaded the update and now it stays stuck on the Android with the red exclamation out of his stomach halfway thru the update.
anyone know the reason why my phone will not update?
did I screw the Basseband? IMEI? or serial? the same thing happend on my Droid Razr when I modified the Build.prop but I never touched the build.prop on my GNEX.

gfropr said:
I am having trouble getting the 4.04 update to work, I get to the android, then it lays down with a red exclamation point out of his stomach.
I was running Kang B36 w Franco Milestone
I used option 9 on the toolkit my build toro 4.02
I restored facotry image for my phone via option 8
I reflashed stock recovery via option 10
finally I locked my bootloader via option 11
restarted my phone downloaded the update and now it stays stuck on the Android with the red exclamation out of his stomach halfway thru the update.
anyone know the reason why my phone will not update?
did I screw the Basseband? IMEI? or serial? the same thing happend on my Droid Razr when I modified the Build.prop but I never touched the build.prop on my GNEX.
Click to expand...
Click to collapse
1) Don't use a toolkit. You don't know what it is doing exactly, so you don't know where it went wrong.
2) I suspect that there is still something that is not stock. I would follow the instructions here, which takes you through the whole process set-by-step (make sure you do the optional steps in part D). That way you can be certain that nothing messed up. Once you do that, then you can have a look here for how to use the OTA update file to update.
3) Don't re-lock your bootloader.

Thank you very much I was unaware of the issues with tool kits, I assumed they worked good since they are stickied.
Sent from my DROID RAZR using xda premium

When I boot into recovery from fastboot my android has a red triangle with a exclamation point, do you think my stock recovery is corrupted?

I am having the same exact probem. I am running the stock 4.0.2 that the phone came with. I used a toolkit that was posted in the Development forums to unlock and root the phone. Other than that, its totally stock.
When I do the OTA update, It gets to the dead android with a triangle coming from his stomach,
I have to pull the battery to get the phone booted, and its still on 4.0.2.
Anyone have any suggestions?

gfropr said:
When I boot into recovery from fastboot my android has a red triangle with a exclamation point, do you think my stock recovery is corrupted?
Click to expand...
Click to collapse
What you see IS the stock recovery screen. (To see the menu, you need to press power and volume up together.) However, if you are seeing that screen when you try to install the update, it is because something on your device is not stock, or, it is not the correct version of stock for the update.
The easiest way to flash the update (assuming you are all stock) is to follow one of the methods in the second link I posted.

Did my JB update just get screwed up?

Ok, so i have been patiently waiting for the JB update on my Play store purchased USA GSM GN that I have been using on Tmobile.
I finally get the update while I am at work, cant download since I don't have wifi there. The wait until 5pm was agonizing!
I finally get home, download the update, it asks to restart and install, i click ok.
It reboots into recovery, but I see the andorid guy with the triangle and a red exclamation mark! It stays there for a couple of minutes and then just boots normally into android os without applying the update.
I rebooted manually into recovery to see if I could reproduce the issue and sure enough i get the red exclamation mark.
I held down Volume Up and Power button and it boots into stock recovery (3e) where i cannot find anything to apply and I just wiped cache and data and rebooted.
Of course, now I check for system update and it says system is up to date.
What just happened? I was rooted, but with stock recovery, locked bootloader.
Anybody else have this issue. How do I fix it so that the next time it finds the update i don't have this happen again??
Thanks in advance,
I could just pull my hair out in frustration....

Dude q&a section this is development wrong section
Sent from my Galaxy Nexus using Tapatalk 2

Why is this in development?
Read forum rules
Questions go in Q&A
Thread moved
FNM

You must be 100% stock for the OTA to apply. Correct radio, UI, build.prop, etc.

hmm i was just thinking this could be the reason.
A little while back i had modified the build.prop for removing boot animation (using GN Toolkit).
In fact i have been trying to restore the backup of the build.prop file back, but haven't been able to.
Any ideas on how to restore everything back to stock (i even tried that option of downloading google stock image IMM76D from the toolkit) and flashed it, but I still get the exclamation point when I boot into recovery...

kgdg said:
hmm i was just thinking this could be the reason.
A little while back i had modified the build.prop for removing boot animation (using GN Toolkit).
In fact i have been trying to restore the backup of the build.prop file back, but haven't been able to.
Any ideas on how to restore everything back to stock (i even tried that option of downloading google stock image IMM76D from the toolkit) and flashed it, but I still get the exclamation point when I boot into recovery...
Click to expand...
Click to collapse
That android with the exclamation point is the stock recovery, press volume up and power button at the same time a few times and the recovery menu should pop up
Sent from my Galaxy Nexus using xda premium

Look at the "flash" link in my sig to return to stock, and the "update" link to update to 4.1.1 from 4.0.4.
Sent from my Galaxy Nexus using Tapatalk 2

efrant,
I will follow the instructions on the flash link to go completely stock, I assume that will fix the red exclamation issue.
All i want is to put the device in a state that will be able to download the official JB (and future) updates and install them.
I thought I was already in that position when I got the OTA earlier today and downloaded it, but when i tried to install it, it booted into recovery and gave me that red mark, so I was assuming that the issue is with the (stock) recovery image.
Would that be a correct assumption?

negrobombon,
I understand that and that works and have tried that. But I am trying to understand if this exclamation mark showing up in recovery is the cause for the OTA to not install?
Or is it unrelated? It sounds like it is unrelated as people are saying the exclamation mark just means that it is stock recovery.
That seems to be proven since I followed the link erfant posted to go completely back to stock and after all that, I still have that exclamation mark in the recovery.
It really doesn't matter if I can confirm that is NOT the cause for my OTA to not install.
Now I am completely stock and looks like I will have to wait again for the OTA to show up (I just want to OTA, not apply the update manually as I want to test if this time around, the OTA installs correctly)...

efrant said:
Look at the "flash" link in my sig to return to stock, and the "update" link to update to 4.1.1 from 4.0.4.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
efrant,
I would just like to say, what a fantastic job you did on the steps in that guide.
It's definitely my preferred way of doing it instead of a toolkit blackbox method where you don't know what it is doing and it's great for when it works, but if it doesn't...you have no idea how to troubleshoot and don't know which step it failed on or what the error is.
Now, have to go back to #*#*checkin*#*# to see if that will speed up my OTA (not really sure if that helps at all). It seems like that does the same thing as Settings->About->System Update->Check Now...

Help! My phone is bricked!

Ok so I have a samsung galaxy s3 att and I have been rooted for the past month or so, no issues. Then, I decide to install a custom rom so I get a stable cm11 and attempt to flash it and it says my cwm version is too low so the reboot my phone so I can update it. The phone starts to boot and gets stuck on the att globe logo with the blue light pulsing. I shut off the phone, pull out the battery and try again, still nothing. I start getting scared so I restore the nandroid backup I made right before this custom rom incident and boot it, still gets stuck at the same place. I really need my phone fixed so can someone help me please??
I was talking to @sd_shadow on another forum earlier and was wondering if he could help me?

supy99 said:
Ok so I have a samsung galaxy s3 att and I have been rooted for the past month or so, no issues. Then, I decide to install a custom rom so I get a stable cm11 and attempt to flash it and it says my cwm version is too low so the reboot my phone so I can update it. The phone starts to boot and gets stuck on the att globe logo with the blue light pulsing. I shut off the phone, pull out the battery and try again, still nothing. I start getting scared so I restore the nandroid backup I made right before this custom rom incident and boot it, still gets stuck at the same place. I really need my phone fixed so can someone help me please??
I was talking to @sd_shadow on another forum earlier and was wondering if he could help me?
Click to expand...
Click to collapse
this thread may help
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"

Don't panic
Grab the latest version of philz touch recovery https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
The zips are made to be flashed from a recovery like cwm. Install it using cwm, reboot into recovery and philz should come up. You should be able to proceed with wiping and installing your custom rom at this point.
If the zip doesn't work out for some reason, you could also use Odin to flash a .tar.md5 from that link to update your recovery.

Try this: http://forum.xda-developers.com/showpost.php?p=60162192&postcount=2

Red Triangle w/ exclamation mark when trying to update to Android 5.0

Hi everyone,
I am currently trying to update my phone for the 5th time to Lollipop.
I have a rooted HTC One M8 with a custom flashed recovery (which I did ages ago, with the assist of a tutorial on youtube).
I think I need help trying to reflash the recovery back to stock, I tried to reflash the recovery myself but I still get the same red triangle w/ exclamation error. I am too much of a newbie with this stuff to fix it myself and I find myself in a place where I don't know how to update!! :crying:
Could anyone please link me to a guide on how to reflash the recovery to stock? I really have no idea what I am doing
Many thanks

You are rooted. The Lollipop OTAs check for any changes in /system, and root is definitely a change. Even if it wasn't, most of the stuff you would do as root will make a change. There are ways to get around that, but the easiest way is to unroot and see if that fixes it. If it doesn't, then RUU back to stock (or restore a backup that isn't rooted) and try it again.
I don't know what your skill level is, but the update will inform you which file it failed on if you really want to try to fix it. However, it can quickly become a massive PITA if you really use your root privileges.

gauzah said:
I think I need help trying to reflash the recovery back to stock, I tried to reflash the recovery myself but I still get the same red triangle w/ exclamation error.
Click to expand...
Click to collapse
That is stock recovery. You just need to press VOL UP button and POWER button to get into recovery when you see that screen.