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
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
Hi guys,
I have a Desire I bought unlocked on eBay. Though initially thinking it was factory unlocked, and having bought it under that pretense, I now think it's been unlocked by some other means. It doesn't appear to be rooted, having no superuser app but I'm not sure how else it could have been unlocked? If any one can shed some light here, that would be great.
I received the OTA update tonight, and after downloading and resetting it simply wouldn't get past 90% on the install before resetting itself. After about 15 minutes I switched it off and switched it on again, and it booted into my homescreen, with a "loading" alert and a rotating circle, no percentage.
Eventually that stopped, and it looked like everything was ok. I checked the version and it said I was running 2.2. Awesome, so I go about my business and realise I have no 3G or wireless connections. I check the settings and under WiFi it says "error", and I can't enable it. My APN is gone too. I can get that online, but it seems like there's an issue with the radio so I haven't bothered. It doesn't connect to the network anyway. It also resets occasionally, it seems when it has to load SenseUI but I can't confirm this.
What could it be? I'm not sure where the phone came from. It's a Black a8181 model with the Orange case branding, but the OS is unbranded. The locale is English (Singapore/Taiwan/a few others), though I thought the Black model was only in the UK. I'm in Australia, on vodafoneAU.
Is there anything I can do?
Cheers guys, I really hope I haven't (basically) bricked it.
Firstly, removing the SIM lock from the phone has nothing to do with rooting. Usually, you just stick in an "incorrect" SIM, and it will ask for an unlock code which you can buy online.
Given that the OTA update was a patch, it sounds to me like you have a partially patched ROM and this is causing your problems.
However, since it basically boots up and works to a fashion, it isn't bricked and chances are it is fairly easily recovered.
IMHO, you have two options.
1. Install a 2.1 RUU to downgrade your phone.
2. Root the phone using UnreEVOked and load a custom 2.2 ROM.
Both of these should be quite easily so long as your previous attempt to upgrade hasn't already updated HBOOT.
Turn you phone off and then power on again whilst holding down the volume down button - your phone should boot into HBOOT.
Look for the HBOOT version on the second line and post back what it says here.
Regards,
Dave
You've received a branded phone that has been debranded (you should have been told this) - you can't upgrade these without a goldcard. What's happened is part of the upgrade has worked, but other parts failed.
To recover you'll need a goldcard, which will be more difficult to make with the phone rebooting all the time.
teppic74 said:
To recover you'll need a goldcard, which will be more difficult to make with the phone rebooting all the time.
Click to expand...
Click to collapse
If the OP can get UnrEVOked running, and doesn't mind having a custom recovery image (good thing!), he/she shouldn't need a goldcard.
Regards,
Dave
foxmeister said:
If the OP can get UnrEVOked running, and doesn't mind having a custom recovery image (good thing!), he/she shouldn't need a goldcard.
Regards,
Dave
Click to expand...
Click to collapse
That's true, though it does mean going down the custom ROM route, which might not be wanted.
Thanks guys, that's really good info.
I'm not too concerned about running custom ROMs, I've been thinking about doing it for a while, just don't know enough about how to root and flash. There are some good guides here, I'm just a bit nervous about doing it. I also don't know what the best ROM would be. I'm really just after a factory standard Desire with Sense ROM, the most out of the box it could be.
I assume an RUU is like a rollback? In which case, what would I be rolling back to. I have no idea how it was debranded, so I don't know what ROM I'd need to roll back to.
As for the goldcard, what would that do? Is that rolling back, or fixing what I have now? It doesn't crash too often, I can probably baby it through.
Sorry for the questions guys, just want to know my options. I didn't think it was too badly bricked, but you never know. I bricked my XDA Mini II trying to flash a new ROM, so you can see my hesitation :/
An RUU is an official way to flash the phone with HTC's own software. That is how the phone was debranded in the first place, and you can do the same to get it back to normal. It does require a goldcard though, which is a minor software patch on the sdcard.
If you root and install a custom ROM (and update the radio) you'll have a working phone again, and you can make a goldcard in your own time.
If I go with an RUU, will OTA updates work? That's really the only thing I'd miss about a custom ROM, the convenience of OTA.
foxmeister said:
Look for the HBOOT version on the second line and post back what it says here.
Click to expand...
Click to collapse
Hboot - 0.80.0000
papalazarou said:
If I go with an RUU, will OTA updates work? That's really the only thing I'd miss about a custom ROM, the convenience of OTA.
Hboot - 0.80.0000
Click to expand...
Click to collapse
You'll get ota updates if you use an ruu. Just make sure you have your goldcard in when you apply them.
teppic74 said:
You'll get ota updates if you use an ruu. Just make sure you have your goldcard in when you apply them.
Click to expand...
Click to collapse
Cool, will the process in the link in your sig do the trick? And the goldcard, will I need to keep it in permanently, or only when updating? Trying to decide if I should use a dedicated card for it, or include it on the card I keep in there.
Thanks for the help, I'll run the RUU tomorrow morning.
I'm trying to run unrevoked to root and reflash it, but it get's to a point and fails, saying "failed to flash recovery image".
Any thoughts?
EDIT:
I've now created a goldcard and am trying the downgrade process in the link in your sig. I've followed all the instructions, but when I ran the downgrade util, after asking for my password, nothing happens.
papalazarou said:
I'm trying to run unrevoked to root and reflash it, but it get's to a point and fails, saying "failed to flash recovery image".
Any thoughts?
EDIT:
I've now created a goldcard and am trying the downgrade process in the link in your sig. I've followed all the instructions, but when I ran the downgrade util, after asking for my password, nothing happens.
Click to expand...
Click to collapse
Yeah, that's my fault for leaving a testing point in the Mac/Linux version of the utility. It was mentioned in the bugs section, but probably not made clear enough. It's fixed now.
I've searched the forums and have not found a situation that really matches mine.
I've been running on a Cyanogen nightly build for probably two months with no problems. Out of nowhere this morning my phone reboots itself (while it was idle; I wasn't even touching it) and then gets stuck in a boot loop. I get the White HTC Evo 4G screen, then it powers off and comes back up to the white screen again. Over and over.
All I can get do is hboot. Even telling hboot to go into the recovery mode puts my back into the boot loop. Fastboot, clear storage, and hboot usb all seem to work though. I've tried downloading the PC36IMG.zip file (http://forum.xda-developers.com/showthread.php?t=780141) in that thread, but hboot loads it and tells me that it is older than my current version, and only gives me the option to reboot, or not to reboot. Doesn't load the image.
Here is the information on my hboot screen:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.97.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Aug 19 2010, 14:29:08
Anybody have any ideas? Thanks!
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
NewZJ said:
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
Click to expand...
Click to collapse
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
luck has been wished
Kuhmo said:
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
Click to expand...
Click to collapse
This didn't work. Everything is still the same, except that my hboot version is now 2.10.0001. Any other thoughts?
still won't not into any rom? did you get errors?
NewZJ said:
still won't not into any rom? did you get errors?
Click to expand...
Click to collapse
No, the app on the PC said everything was successful. The progress bar on the phone progressed without errors too.
what happens when you reboot the phone not going into bootloader?
Just the HTC EVO 4G splash screen. Over and over and over...
does it show the boot animation or just stuck on splash?
Just the splash. No animation.
pull the battery, remove your sdcard, put the battery back in, see if it gets to the animation
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Wrong button..
xHausx said:
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I asked my wife to check this thread from the car on the way to dinner. Saw the response. So I took my laptop inside with us and used the RUU one more time. No luck. I decided that it must be a hardware issue. I took the SD out and removed the evidence that the phone had been rooted, then took it to the sprint service center up the road. They just replaced it for me. Thanks for your time! I DO want to root my phone again, the ROMs are just so much better than the stock installation. Should I not install the OTA updates if I'm going to root it? Which guide should I follow for rooting?
never do OTA when rooted, use unrevoked to root, unrevoked.com
NewZJ said:
never do OTA when rooted, use unrevoked to root, unrevoked.com
Click to expand...
Click to collapse
Not when rooted. I meant should I update to the latest OTA UNTIL I decide to do the root again? Is the latest OTA unrootable?
Same deal.
Here is the post that I put in the wrong forum that I was about to post here until I saw this thread...
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...
2) Anyone know how to turn S-(back)ON in my current situation?
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )
run the ruu to s-on then trade for another
NewZJ said:
run the ruu to s-on then trade for another
Click to expand...
Click to collapse
Ack, sorry... didn't mention in previous post. I fired up windows to run the RUU (I don't trust wine to that stuff) but it couldn't detect the device.
I ran unrevoked 3 and tried a few things and decided it was not for me, I ran the Sprint RUU and it all worked fine. But under the bootloader screen it still shows S-off. Can I renable it?
venom_762 said:
I ran unrevoked 3 and tried a few things and decided it was not for me, I ran the Sprint RUU and it all worked fine. But under the bootloader screen it still shows S-off. Can I renable it?
Click to expand...
Click to collapse
Sry to hear that. See if THIS helps.
oooh that sucks. you have to re-root (you can just use unrevoked 3 again), then put the unrevoked s-on tool (found in the FAQ section of this thread http://unrevoked.com/rootwiki/doku.php/public/forever ) on the root of your sdcard. boot into recovery, and flash it as you would a rom. then check bootloader to make sure it is s-on. if it is, run the ruu again.
just curious, why dont u like root?
I just tried to re-run Unrevoked 3 and it will not reconnect, the tool just says waiting for device.
And I don't like root because of too much power.
venom_762 said:
I just tried to re-run Unrevoked 3 and it will not reconnect, the tool just says waiting for device.
And I don't like root because of too much power.
Click to expand...
Click to collapse
usb debugging is probably not on. try that.
too much power? like too much battery consumption (wtf?) or too much power over the phone?
too much stuff for me to f-with.
venom_762 said:
too much stuff for me to f-with.
Click to expand...
Click to collapse
hahah ok then. so ya turn debugging on (settings, applications, development, usb debugging) and put the phone on charge only and run unrevoked.
ok I found it, I was trying to root from the hboot screen.
Can't I just wait for the OTA from sprint and that would just turn S-back on?
venom_762 said:
Can't I just wait for the OTA from sprint and that would just turn S-back on?
Click to expand...
Click to collapse
no, it wouldnt turn s-on, and you might not even be able to accept it. if you are having a hard time using unrevoked, seeing as your rom no longer has root permissions, i can lead you through manually flashing amon-ra recovery to your phone and you can flash ur s-on from there.
I just got it to root again using Unrevoked 3 and restored to right after my first root. I should be able to now install the S-on tool and install it from the recovery menu?
venom_762 said:
I just got it to root again using Unrevoked 3 and restored to right after my first root. I should be able to now install the S-on tool and install it from the recovery menu?
Click to expand...
Click to collapse
That is correct. Also, I'm pretty sure that since you were still S off, you could've just flashed a pc36img of a recovery from the bootloader, flashed the s on tool, and then ran RUU.
Edit : just saw that dk already suggested that. Sorry.
Sent from my PC36100 using XDA App
Update I figured it out and ran the S-on tool, booted into the bootloaded and verified it was back on. I then ran the RUU and it should be fully stock and ready to install the OTA?
I just don't want to be that guy does not or has a failed update when the official OTA is out.
Anyone? I dying to know if I can install the next ota.
venom_762 said:
Anyone? I dying to know if I can install the next ota.
Click to expand...
Click to collapse
If you're back to stock, s on, and aren't on the latest OTA, then yes, you can take the OTA if you'd like to. That will bring you up to the latest software update.
Sent from my PC36100 using XDA App
Great I am relieved, I just wondered if when its pushed out if I have problems seeing it. Thank you guys for all of your help.
venom_762 said:
Great I am relieved, I just wondered if when its pushed out if I have problems seeing it. Thank you guys for all of your help.
Click to expand...
Click to collapse
sorry for leaving you in the dark for a while. that was one crazy day. but i'm at my comp now so i can help (not that there's anything left to do).
if i were you, i'd double check you are fully unrooted. boot into bootloader, and make sure you are s-on. then boot into recovery and make sure you have no custom recovery, just the stock htc one. also make sure your rom has no superuser app installed. if not, you are all good.
No prob man, I booted into the bootloader and S-On is back on and then tried to boot into recovery, a black screen with a red triangle came up so I assume there's no recovery installed. There is also no superuser Icon in the app draw.
The main reason I returned to stock is,is that this is my primary and only phone. I plan on getting the Nexus S when it come to sprint so I will see you guys again. That way if I bork the NS I got my trusty evo to activate.
Again thank you all for the help.
venom_762 said:
No prob man, I booted into the bootloader and S-On is back on and then tried to boot into recovery, a black screen with a red triangle came up so I assume there's no recovery installed. There is also no superuser Icon in the app draw.
The main reason I returned to stock is,is that this is my primary and only phone. I plan on getting the Nexus S when it come to sprint so I will see you guys again. That way if I bork the NS I got my trusty evo to activate.
Again thank you all for the help.
Click to expand...
Click to collapse
ok ya ur totally unrooted. enjoy the cage some prefer it there.
just saying, the evo is freaking hard to brick.
Hello all, I'm in serious need of some help, I've been working at this for a couple of hours now and can't figure it out, so I turn to you, o mighty forum.
I have an HTC Incredible and I'm currently running MIUI and clockwork recovery mod. I've been having all kinds of problems lately, and I want to just delete everything on my phone and get it back to stock, the way it was when I turned it on for the first time out of the box. If anyone can help me get this done I will be forever grateful, because I'm at my wits end. I have no idea what to do, or where to start, so if anyone could provide me with a step-by-step instructions, I would be very happy.
Thank you
bobrea said:
Hello all, I'm in serious need of some help, I've been working at this for a couple of hours now and can't figure it out, so I turn to you, o mighty forum.
I have an HTC Incredible and I'm currently running MIUI and clockwork recovery mod. I've been having all kinds of problems lately, and I want to just delete everything on my phone and get it back to stock, the way it was when I turned it on for the first time out of the box. If anyone can help me get this done I will be forever grateful, because I'm at my wits end. I have no idea what to do, or where to start, so if anyone could provide me with a step-by-step instructions, I would be very happy.
Thank you
Click to expand...
Click to collapse
Id be glad to help you. First off though are you s-off, and once you go stock again do you plan on rerooting in the future?
cmlusco said:
Id be glad to help you. First off though are you s-off, and once you go stock again do you plan on rerooting in the future?
Click to expand...
Click to collapse
Thanks for the reply. Right now I am S-On. And no, I don't plan on rooting again.
bobrea said:
Thanks for the reply. Right now I am S-On. And no, I don't plan on rooting again.
Click to expand...
Click to collapse
Ok then all you need to do is flash an ruu thru hboot.
Go here (http://pvillecomp.com/?page_id=22)and download the Gingerbread PB31IMG.zip
From the home screen of the phone hit Menu - Settings - Applications, and make sure fastboot is NOT checked.
Then go here (http://pvillecomp.com/?page_id=79) to learn how to flash the ruu thru hboot.
If you have any issues i will be keeping an eye on the thread.
I think I tried this earlier but it didn't work due to something about a newer version already be installed. I'll keep you posted.
bobrea said:
I think I tried this earlier but it didn't work due to something about a newer version already be installed. I'll keep you posted.
Click to expand...
Click to collapse
What android version are you on now? If its 4.08.605.2 then you will need to do the ruu exe with a pc. Its the first one on the pvillecomp link where the PB31IMG is.
To be totally honest I'm not sure. I tried using an RUU earlier but it kept saying my phone wasnt plugged in and it couldn't run, even though the phone was plugged in.
bobrea said:
To be totally honest I'm not sure. I tried using an RUU earlier but it kept saying my phone wasnt plugged in and it couldn't run, even though the phone was plugged in.
Click to expand...
Click to collapse
To do the ruu exe you need to have htc sync installed on your pc, to get the right drivers. Im not positive but you may need to remove the adb drivers first.
Baseband version: 2.15.00.07.28
Kernel Version:
2.6.37.6-cyanogenmod+
Android Version: 2.3.7
bobrea said:
Baseband version: 2.15.00.07.28
Kernel Version:
2.6.37.6-cyanogenmod+
Android Version: 2.3.7
Click to expand...
Click to collapse
Thats the problem your on a custom rom thats ported, and a higher android version than the latest stock ruu for the inc, so the ruu thinks yout trying to downgrade. Since your still on the correct radio needed for unrevoked to achieve s-off, i would reroot and s-off the phone with unrevoked, then flash a stock ota based inc rom (perferably 4.06.605.3), then go s-on again with the s-on patch, then do the ruu and it shouldnt give the firmware too new error anymore, and should get you back to complete stock.
What does that mean/how do I do it? I'm totally clueless here.
What does that mean/how do I do it? I'm totally clueless here. I just downloaded unrevoked 3.
bobrea said:
What does that mean/how do I do it? I'm totally clueless here.
Click to expand...
Click to collapse
Go here (http://unrevoked.com/#inc) get the unrevoked program and run it to root your phone and get s-off again. Instructions are on that page for using it.
Then flash this rom thru clockworkmod recoveryrecovery (http://forum.xda-developers.com/showthread.php?t=1247253), and reboot.
Then flash the s-on tool thru recovery (http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip)
Then do the PB31IMG.zip ruu again, it should work this time, and you will be complete stock.
Not exactly sure what's going on here. I used unrevoked 3 and got the original OS back on there, but when unrevoked runs, it asks if I want to install that PB31IMG file. I chose to not update with that and just reboot into recovery (which if I'm correct should be clockwork,) so I could flash that ROM, but when I reboot the device, I get a black screen wiith a picture of the phone and an ! in a red triangle. The unrevoked program just says "waiting for reboot..."
bobrea said:
Not exactly sure what's going on here. I used unrevoked 3 and got the original OS back on there, but when unrevoked runs, it asks if I want to install that PB31IMG file. I chose to not update with that and just reboot into recovery (which if I'm correct should be clockwork,) so I could flash that ROM, but when I reboot the device, I get a black screen wiith a picture of the phone and an ! in a red triangle. The unrevoked program just says "waiting for reboot..."
Click to expand...
Click to collapse
Go aheda and let unrevoked do the PB31IMG, that is the cwm recovery. The red triangle is still the stock recovery. Are you s-off now?
Nope, I'm still S-on. Not really sure what happened, but I have the original OS on the phone and from what I can tell, it's working fine. But I'm still S-on
I'm going to call it a night. I'll check this thread tomorrow when I get back from work and class. Thanks so much for all of your help so far.
bobrea said:
Nope, I'm still S-on. Not really sure what happened, but I have the original OS on the phone and from what I can tell, it's working fine. But I'm still S-on
Click to expand...
Click to collapse
Welk then you are stock just like the day you got it. If you want you can do the gingerbread ruu now, and it should not give the firmware too new error, ir you can stick with froyo, and at some point it will pop up with the latest ota to install.
Thanks so much, again. This was driving me crazy.