I was running the full stock rooted 4.3 rom, and stock recovery. I downloaded the OTA through the setting menu. After installing the update through the onscreen prompt, phone goes into recovery and starts the install. It gets to the halfway point, and the icon changes to a red triangle with an exclamation point. After holding volume up+power, it takes me to the stock recovery menu. It's says the installation was aborted because it could not mount sd card. Now I am stuck. I can't reboot the phone, it hangs on the logo. No options in Stock recovery work, as far as installing the update. My phone is being sold soon, so I have nothing in my storage as far as flashable ROMs go. Im an idiot. Do I have any options to get this bad boy working and ready for the sale? Just to clarify, my bootloader is unlocked and I am S off. I had flashed different hboots to remove the red text and unlocked text in the bootloader. Can I just RUU back to stock?
Sent from my SM-N900V using Tapatalk
I think RUU is probably your only option at this point... just curious though, the stock 4.4 OTA rom has been available here for like more than a week so why in the world did you decide to get it from the settings menu? Anyway, I think the issue was you needed to flash the stock recovery before installing the OTA because it needs it in order to flash correctly. You can't get into the bootloader at all?
If you can get into Fastboot, flash the latest TWRP and then flash the full 4.4.2 ROM. That will get you back up and running.
Sorry, I thought I had edited the OP last night. I went ahead and and just RUU'd back to 4.3, and then accepted the update via the system. I am selling the phone, and for some reason the dude buying wants it stock unrooted, with S Off and the bootloader unlocked. Whatev. So I originally flashed the odexed full stock rom, and the stock recovery, and then got hung up during the install of the OTA. I think it was the modifed HBOOT that I put on at one point. Anyways, after the RUU, everything went fine. Phone is running unrooted 4.4.2, with S-off and the bootloader still unlocked. All is well! I couldn't believe how simple the RUU process was. I have a Mac, and it was just a couple commands in terminal. Took about 10 minutes, with 9 of those minutes spent waiting for the RUU to finish.
sdot_sd said:
Sorry, I thought I had edited the OP last night. I went ahead and and just RUU'd back to 4.3, and then accepted the update via the system. I am selling the phone, and for some reason the dude buying wants it stock unrooted, with S Off and the bootloader unlocked. Whatev. So I originally flashed the odexed full stock rom, and the stock recovery, and then got hung up during the install of the OTA. I think it was the modifed HBOOT that I put on at one point. Anyways, after the RUU, everything went fine. Phone is running unrooted 4.4.2, with S-off and the bootloader still unlocked. All is well! I couldn't believe how simple the RUU process was. I have a Mac, and it was just a couple commands in terminal. Took about 10 minutes, with 9 of those minutes spent waiting for the RUU to finish.
Click to expand...
Click to collapse
Sounds like the best way to buy it for some people. Otherwise, we would see them posting on here in a couple days needing to ruu to recover their "new" phone.
Sent from my Nexus 7 using Tapatalk
Related
I downloaded the OTA update and it killed my phone. It is a non rooted stock phone.
I can access the bootloader so its not fully bricked. It just sits there on the first screen like its having issues with its rom.
The info on the bootloader screen.
Supersonic EVT2-2 Ship S-On
HBOOT-0.79.0000
MICROP=041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.05.00.06.10
APR 14 2010,15:14:34
I roamed around and tried several of the rooting tools and such but nothing worked. The .exe files to set the thing back wont work.
Just wondering if I am SOL atm or there some way I can fix this?
What happened when you tried using the RUU? Did you try using the zip file?
I tried all 3 of the current .exe files on the roms page. All of the give bootloader veerson error. The .zip files most of them give a older verson error.
The RUU_Supersonic_1.32.651.6 .zip does nothing. Gives no error, no options just back to the bootloader.
Least the bootloader works. If there is a new rooter out maby i can fix it myself because the sprint dealers can not do anything.
you can have them fill out in the paperwork to get you another one..
its still under 30 day warranty
but so far your SOL.
there are no root methods for the OTA.
so either way, you have to wait it out.
CYBERxNUKE said:
you can have them fill out in the paperwork to get you another one..
its still under 30 day warranty
but so far your SOL.
there are no root methods for the OTA.
so either way, you have to wait it out.
Click to expand...
Click to collapse
Yea I got it from radioshack. They know whats up and when they get a phone im getting it replaced. I do not want to root it, i just want to a working state. Yet if i get one with a old rom/bootloader on it... hell ya im rooting it.
If anyone has any ideas on how to simply flash it to stock, like a ligit htc/sprint way im all ears.
Well I was able to fix it using the rru exe that was posted yesterday. \o/
firefoxinc said:
Well I was able to fix it using the rru exe that was posted yesterday. \o/
Click to expand...
Click to collapse
got a link you could throw my way of what you used?
My phone isn't bricked, but when I try to use the sprint .exe RRU, once it goes into boot loader mode it gives me some error about version.
I don't know if my phone is only 1/2 bricked or what, or if it's just an issue with the latest over the air update screwing things up. I never flashed any new roms, just did Unrevoked 1 method before I did the OTA. I would guess my phone is 100% stock at this point.
accelerus said:
got a link you could throw my way of what you used?
My phone isn't bricked, but when I try to use the sprint .exe RRU, once it goes into boot loader mode it gives me some error about version.
I don't know if my phone is only 1/2 bricked or what, or if it's just an issue with the latest over the air update screwing things up. I never flashed any new roms, just did Unrevoked 1 method before I did the OTA. I would guess my phone is 100% stock at this point.
Click to expand...
Click to collapse
There is no "half bricked" a bricked phone is one that no longer works appropriately. You've got a brick instead of a phone because it doesn't work.
If you do the OTA, or have done the OTA, you cannot root and cannot restore to factory settings. I think the exe the OP is referring to is of the OTA update, ie, he won't be able to root.
If you can boot to Android, you're phone is fine, just not rootable.
accelerus said:
got a link you could throw my way of what you used?
My phone isn't bricked, but when I try to use the sprint .exe RRU, once it goes into boot loader mode it gives me some error about version.
I don't know if my phone is only 1/2 bricked or what, or if it's just an issue with the latest over the air update screwing things up. I never flashed any new roms, just did Unrevoked 1 method before I did the OTA. I would guess my phone is 100% stock at this point.
Click to expand...
Click to collapse
Here is to the thread
http://forum.xda-developers.com/showthread.php?t=717024
I have been searching the web for how to relock my EVO. This is because i am taking it back to sprint for a screen fix and I have learned from the PPCGEEKS thread all the problems and warranty stuff related to rooting as well as the odds of them discovering that I have rooted it. I just don't want to risk it and I would like to know how to relock, just for the knowledge.
Does anyone have specific instructions how??
PPCGEEKS Thread: http://forum.ppcgeeks.com/showthread.php?t=126849
http://shipped-roms.com/shipped/Supersonic/
Download first and last, and flash in the same sequence.
So thats all?? its done? It's unrooted? That seems simple.
Yep, that's how easy it is.
On some phones (one out 5 I "control") I had to get all 3 and flash in the same sequence, otherwise last one wouldn't flash over the first - not sure why.
redsolar said:
last one wouldn't flash over the first - not sure why.
Click to expand...
Click to collapse
that surprises me. the latest RUU should flash over anything *theoretically*.
what error did it give you when you attempted?
yes, it should be easy to restore the phone to stock. think of all their service departments fixing/refurb'n phones. one simple flash and its all completely stock no matter what was loaded before.
for those more technically included, since this is the dev board, if the eng build RUU is loaded the PRI is downgraded and as of now, no currently released RUU is able to upgrade the PRI ... but thats such a small issue, can almost guarantee nobody will notice.
Damn screen... I have to do the same thing, and just one other question, besides those files I will just have to use Htc Sync to flash them right?
Yellowcard8992 said:
Damn screen... I have to do the same thing, and just one other question, besides those files I will just have to use Htc Sync to flash them right?
Click to expand...
Click to collapse
Those RUUs are just exe files. So sync will provide you with drivers yes, but after downloading you just run from that download with your phone plugged in.
wow after reading that thread on ppcgeeks i dont think i ever want to leave xda! must be a young crowd over there. i ran the latest 1.47 RUU that i downloaded from HTC before I returned my phone. much to my surprise they didn't even take the phone out of the box! still, since it only takes 10 minutes might as well do it.
barnacles10 said:
Those RUUs are just exe files. So sync will provide you with drivers yes, but after downloading you just run from that download with your phone plugged in.
Click to expand...
Click to collapse
are you talking about just using the volume down and power button method?
redsolar said:
Yep, that's how easy it is.
On some phones (one out 5 I "control") I had to get all 3 and flash in the same sequence, otherwise last one wouldn't flash over the first - not sure why.
Click to expand...
Click to collapse
whats the point in running all 3 on a phone you are returning? just running the first one is good enough to unroot and restore to stock. i only ran the most recent one, because i had already upgraded the baseband and was unable to run the earlier ones because of it.
joeykrim said:
that surprises me. the latest RUU should flash over anything *theoretically*.
what error did it give you when you attempted?
yes, it should be easy to restore the phone to stock. think of all their service departments fixing/refurb'n phones. one simple flash and its all completely stock no matter what was loaded before.
for those more technically included, since this is the dev board, if the eng build RUU is loaded the PRI is downgraded and as of now, no currently released RUU is able to upgrade the PRI ... but thats such a small issue, can almost guarantee nobody will notice.
Click to expand...
Click to collapse
I was surprised too when I tried first.
The 1.47 RUU just sat on the "waiting for bootloader" screen and timed out after ~90 seconds, "unable to find phone" (tried multiple times) and the screen would get stuck in white bootloader/RUU message (battery pull required) - so i am guessing 0.76.2 bootloader was too low for it. That was flashing from 3.2.2+ DamageControl ROM, didn't try from any other one, since the DC -> 1.36 -> 1.47 stock worked well.
And yes, the PRI caveat is there, but as joeykrim said, that's minor, plus you can always say "PRI what - huh?", right?
OneStepAhead said:
whats the point in running all 3 on a phone you are returning? just running the first one is good enough to unroot and restore to stock. i only ran the most recent one, because i had already upgraded the baseband and was unable to run the earlier ones because of it.
Click to expand...
Click to collapse
Running latest OTA makes you seem more of a "dumb user" who wouldn't even know what root is?
Yellowcard8992 said:
are you talking about just using the volume down and power button method?
Click to expand...
Click to collapse
No. RUUs are handled differently. You download the file. And run it on your computer with the phone plugged in. It does everything for you. You DO NOT flash these via recovery.
Update on my phone
I took it to the sprint store yesterday and against everything I have heard the guy at the store turned my phone and checked it. Thank god I used redsolar's posted method. I must have the appearance of someone who would root there phone. It passed his inspection, luckily.
Thanks for the help
I rooted with the new Simpleroot OTA Edition, with Fresh Rom 053, and RA-Rec.
I'm trying to start over from stock so I can re-root my phone, but I can't get the RUU's to work. The oldest one will actually try and put the phone in bootloader, but while its waiting for bootloader it eventually just stops and gives me the 170 error, usb connector problem.
So is there any other way to go about this? Any help would be greatly appreciated.
murdercitydan said:
I rooted with the new Simpleroot OTA Edition, with Fresh Rom 053, and RA-Rec.
I'm trying to start over from stock so I can re-root my phone, but I can't get the RUU's to work. The oldest one will actually try and put the phone in bootloader, but while its waiting for bootloader it eventually just stops and gives me the 170 error, usb connector problem.
So is there any other way to go about this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
ya what I do is replug the usb coord then try ruu again while the phone is stuck on the HTC sign,then if that doesn't work I just manually go into bootloader myself (power+volume down) then use the ruu.exe, works everytime but then it tells me my current version is not valid, so if you ota'd you probably won't ever be able to go back to 1.32.651.1/.6 stock but you can just use the new 1.47.651.1 ruu to regain stock after ota.
Tundricles said:
ya what I do is replug the usb coord then try ruu again while the phone is stuck on the HTC sign,then if that doesn't work I just manually go into bootloader myself (power+volume down) then use the ruu.exe, works everytime but then it tells me my current version is not valid, so if you ota'd you probably won't ever be able to go back to 1.32.651.1/.6 stock but you can just use the new 1.47.651.1 ruu to regain stock after ota.
Click to expand...
Click to collapse
Thanks a **** load Tundricles, you saved my ass.
I was getting so pissed, I'd run the RUU and once it got to opening the bootloader on my phone it was get frozen on the HTC screen, and the RUU would get the use connection error. So I unplugged my phone, and noticed it was in the bootloader, but if the usb was plugged in, it wouldn't show the bootloader screen for some reason. So I just plugged it back in and started the RUU back up, it instantly went past the "Waiting for bootloader..." message and started updating.
Thank you, and for anyone else having similar problems, READ THIS!
Flashing the RUU doesn't restore the stock recovery does it?
I ran Unrevoked 2 a while back and I have RUU'd but I'm pretty sure Clockwork Mod is still there.
Sent from my EVO 4G using the XDA App.
ViViDboarder said:
Flashing the RUU doesn't restore the stock recovery does it?
I ran Unrevoked 2 a while back and I have RUU'd but I'm pretty sure Clockwork Mod is still there.
Sent from my EVO 4G using the XDA App.
Click to expand...
Click to collapse
It should. RUU replaces everything but PRI
Sent from my PC36100 using XDA App
murdercitydan said:
Thanks a **** load Tundricles, you saved my ass.
I was getting so pissed, I'd run the RUU and once it got to opening the bootloader on my phone it was get frozen on the HTC screen, and the RUU would get the use connection error. So I unplugged my phone, and noticed it was in the bootloader, but if the usb was plugged in, it wouldn't show the bootloader screen for some reason. So I just plugged it back in and started the RUU back up, it instantly went past the "Waiting for bootloader..." message and started updating.
Thank you, and for anyone else having similar problems, READ THIS!
Click to expand...
Click to collapse
np glad I could help
OK,
I used the Simple Root method to unlock my EVO. I'm clueless as to how this benefits me and what to do with the rooted phone now.
Of course Sprint released the OTA 2.2 update just days after I did this and I just want to return my phone the the stock ROM. I've tried several methods and none work. Everything I do leaves me with the Superuser Permissions still on phone and I cannot complete the OTA 2.2 update. I don't want a custom ROM, I just want the stock OTA ROM.
Someone please help with a step by step of how to remove the Clockwork Mod boot system and return my phone to out of box condition so I can get up to date.
Thanks (I hope).
Flashing the stock RUU maybe??!?!?!?! lol
tried that
Yes That would seem logical. I tried that but it doesn't get rid of the boot system which is preventing me from getting the OTA 2.2 update. I want to revert completely.
Admittedly I don't really understand all this rooting business so it does me little good to have my phone rooted.
I can revert my ROM but it doesn't get rid of the clockwork mod boot system and therefore I still cannot complete the OTA update. Every time I try the update it starts to install and then goes to a page with a caution triangle and just freezes there and I have to pull the battery and reboot and I'm at the same place I was before.
I don't understand how to flash a ROM anyhow.
You can download the 3.26.651.6 RUU .exe from this mirror
http://www.mediafire.com/?3z4zbt3vco1ijs7
USB your phone to your computer and run that exe. You will end up with the same stock froyo as the the OTA update will ultimately give you.
If you used the official 1.47 RUU, and it completed properly, then you should be completely stock. It wipes all the partitions and puts you back to stock. You can also look for the stock .6 Froyo rom that's been rooted. I know I've seen it around here somewhere. Grab the one that is Odexed, as it hasn't been tampered with at all except to add SU permissions.
My wife got her replacement Inc2 today after the one she got last week just died. She was on Froyo so I might of.. swapped her phones.. anyways, I rooted, went to the bathroom and the stupid ota ran I guess because when I came back the phone was on GB 2.3.3 however my boot screen shows S-OFF. Can anyone help me to verify that S-OFF is indeed still off. I can post any screen shots etc.. I am still a noob when it comes to the Inc2.
If your boot screen says S-Off, you are S-Off
Sent from my stock, bloated ADR6350 using XDA Premium App
Did you flash clockworkmod recovery when you rooted? I didn't think the OTA would take if you had a custom recovery. In any event, since you're still s-off, you're fine.
I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.
kujayhawks77 said:
I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.
Click to expand...
Click to collapse
Alpharev changed ur hboot to a higer version than the one in the OTA.. this is why it kept you S-OFF.. if I'm wrong someone correct me.
So basically I just got really lucky and kept my S-OFF even though the OTA went through.
kujayhawks77 said:
So basically I just got really lucky and kept my S-OFF even though the OTA went through.
Click to expand...
Click to collapse
No. stock hboot is .97. alpharev bumped you up to 1.something.. idk I used XTC clip.. since your hboot is newer than the OTA.. it keeps you S-OFF, pretty smart by alpha.
So does this open a gateway to first root in Froyo and then go gingerbread and retain the root?
Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Now when I use the term "gateway" I say this loosely because it doesn't fix anything for anyone who is already on GB. If indeed this works, it would only work for a small percentage who get Froyo and don't flash clockwork before running the OTA.
I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA
tnez said:
I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA
Click to expand...
Click to collapse
2.1??? I think you are mistaken, sir
beenz said:
2.1??? I think you are mistaken, sir
Click to expand...
Click to collapse
He was mistaken cause it is sense 2.1 but android 2.2
Sent from my Incredible 2 using XDA Premium App
kujayhawks77 said:
Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Click to expand...
Click to collapse
I've been wondering about this. I got my Dinc2 early July and I'm still on stock, unrooted Froyo. Somehow the OTA update to GB hasn't hit yet. Could I run ApharevX to get S-off and stop there for now? I am happy with bloated stock for the time being and want to be able to receive OTA updates, but would like to have the option down the road to add Clockworkmod and flash custom ROMs. From kujayhawks experience it seems that this should be possible.
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
P.S. First post, though I've been lurking around for a while. Great forum/community.
xenakis said:
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
Click to expand...
Click to collapse
It appears from reports that S-off stays after the OTA to 2.3, so yea, that would seem to be the case.
If you turn S-off with AlphaRev, you might want to just go ahead and install Clockwork recovery at the same time. Doing so won't root or install SuperUser or anything, but you would be able to then backup your phone and be ready to flash if you wanted.
If you install clockwork recovery you won't be able to receive OTAs though, just keep that in mind. You can flash back to the stock recovery, but unless you are familiar with ADB, it won't necessarily be an easy process.
When I go to 'check for system updates' it says 'system is currently up to date'. But its not because the OTA came out and my wife updated hers.
I rooted my phone a while back, is this why? My phone says my software is 2.1 update 1. I had bricked my phone a while back and installed the file to bring it back to 'stock' supposadly.
My phone also says Incredible XC SHIP S-Off when i go to recovery.
Any ideas on how to get my phone to recognize and install the OTA update?
Thanks pros.
dontstopgetit said:
When I go to 'check for system updates' it says 'system is currently up to date'. But its not because the OTA came out and my wife updated hers.
I rooted my phone a while back, is this why? My phone says my software is 2.1 update 1. I had bricked my phone a while back and installed the file to bring it back to 'stock' supposadly.
My phone also says Incredible XC SHIP S-Off when i go to recovery.
Any ideas on how to get my phone to recognize and install the OTA update?
Thanks pros.
Click to expand...
Click to collapse
So you're on 2.1? You'll probably want to bring it to 2.2 Stock. You can stay S-OFF, you'll just need to be stock 2.2 with Android Recovery, not ClockworkMod custom recovery. You can get the Stock Android Recovery from Doug Piston's site here.
If you go back to S-ON and stock 2.2, then that the OTA, you won't be able to root again until Unrevoked comes up with a method to root again.
EDIT: Once you get everything to that point, the OTA may not come to your phone right away, so you may need to wait. I'm not sure if they're rolling it out randomly in small batches, or how they're doing it this time.
+1 on updating to 2.2 froyo
did you get a notification of the update on your phone? not all phones get it at the exact same time and it could be days before you get it. if you are rooted and have a file explorer app you look in the cache folder under the root directory of the phone to see if you got the update but it didn't install.
Awesome thanks. I'm on Doug Piston's site but am confused as to which Stock Android Recovery listed I need to download and install. There are like 10. Help. Thanks.
dontstopgetit said:
Awesome thanks. I'm on Doug Piston's site but am confused as to which Stock Android Recovery listed I need to download and install. There are like 10. Help. Thanks.
Click to expand...
Click to collapse
There's only one stock recovery there. It's labeled: Stock Recovery from lord knows who.
All of the others are ClockworkMod recoveries, various versions of them.