So here is my situation and I did try to search but couldn't find an answer.
I did the unrevoked>forever>stock recovery so I am still rooted but back to stock recovery.
Last night I got the OTA and it started to run but about a third into the green bar it went to a red triangle. So the updated failed an am still on 2.1
Could this be because I was in my basement with crappy signal, it dropped and didn't download the file or is it because I am still rooted?
I do not have clockwork recovery on there anymore and was told that it would be fine to have root and still install the OTA.
Thanks for any help!
Related
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!
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
cvall91 said:
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
Click to expand...
Click to collapse
I thought rooted phones weren't allowed to update via Kies or OTA.
allenjthomsen said:
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I guess I'll try to download it again and see if that works. Do you know if that's through Kies or through manually downloading it then using Odin?
Techngro said:
I thought rooted phones weren't allowed to update via Kies or OTA.
Click to expand...
Click to collapse
Well it seemed to update for me. At least the verification process went through. I used Wanam Xposed and had the fake system status thing checked. Either way something went wrong and didn't finish the updating process and got stuck at boot logo with no recovery options.
The OTA update did not work though. I was able to get the update downloading after Wanam, but once the download finished, the update failed before trying to install. Did not try OTA again though I just went to Kies, then Odin. But all 3 methods failed.
a few weeks ago I wanted to get the 4.4.3 update on my M8 but being rooted and missing apps I couldn't, so I found the developer edition rom and flashed the rom then flashed the firmware.
the thing is I have had root access ever since with out the need to use SuperUser, a little concerned any APK could access the phone and make a Mess I downloaded chainfires SU from google store, it immediately told me I needed to up date the SU binary, I cancelled and backed out but the phone rebooted and factory reset as if it was trying to update the SU via recovery.
eventually the phone rebooted and guess what, I am now missing the same APK files as before.
is it possible that it is the superuser apk causing the loss of the other apks and not the rooting process?
I am now going to have to reflash the ROM when I get home, how ever this morning before work I wanted to flash it, but when I used "FastBoot Boot Trecvoery.img" (touch recovery) the phone just hung and did not boot into recovery, stock recovery, longer shows the usual htc phone and red triangle logo, instead it just shows a white screen with htc written in grey
the phone works fine, but how do I get the ROM to reflash if I cant boot into custom recovery, I do not want to flash custom recovery as I prefer stock everything until my warranty expires.
am I going to have to S-off and start again?
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.
Hi, I was rooted Magisk and twrp installed, I kept getting a notification of an update but just kept ignoring it. About the same time my phone started dropping signal all the time so I thought it might have something to do with the update. I went back to full stock 27.1 . When I try to get the update it downloads it and when it gets ready to install it says working in the background it shows a progress bar for a sec then pops up a screen telling me that something went wrong and update failed and nothing was changed and i just click ok. I get no type of error messages or any thing explaining what the problem is. As of right im not rooted or any custom rom or recovery installed just bootloader unlocked, SO what did I do wrong and how do I fix it???
When you say you went back to stock, do you mean you factory reset or you went as far as doing the flash-all?
Unseeablething said:
When you say you went back to stock, do you mean you factory reset or you went as far as doing the flash-all?
Click to expand...
Click to collapse
I did the flash-all...
I too did a flash all after installing the OTA, now I can't install the OTA anymore.