Related
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 so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
To be honest, I would say just wait for the OTA, Verizon themselves have confirmed it has been/will be released today 8/27. Then there will be no worrying, since you don't want root this would be the best way.
boomertwo said:
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
Click to expand...
Click to collapse
I'm sorry this has nothing to do with what you're asking, I've read, and don't know sorry man, but I do have a quick question for you. I see you have never rooted, or maybe or have, I thought maybe you hadn't for some reason, but anyway, I see you HBOOT it .77, how long have you had your phone since?
Yes I had rooted the phone recently for about 2 weeks then it got messed up but thanks to an unrevoked member I was able to recover the phone. It wasn't bricked or anything but some how the NAM was messed up which prevented me from using *228 to update roaming or my ability to activate the phone after a factory reset. I do remember it having hboot .79 before rooting though.
Update: I verified that the hboot in the stock restore img file I used had only hboot 77 in it and not 79. This means I downgraded to 77 without knowing it at first. (From the threads I have read it is stated that .77 and .79 are interchangeable so I don't think I need to worry about it when the ota comes I hope..)
I've had it for about 3 months now so I'm out of the return policy and I do like the phone and have no intention of returning it.
After trying root out for those 2 weeks I found that for me I didn't really gain anything that seemed worth it for my personal needs.
Also I like to tinker with stuff but since I'm in a 2 year contract I rather not take the risk of bricking it and having to pay for the next 2 years for service I can't even use due to my own fault of breaking the device.
Right now I'm just wondering if it is safe to apply the file that can be found in the ruu without root and without breaking the device since it has the same build number and radio number as the update that verizon has stated on the update page.
.77
I am on my third incredible, and all 3 shipped to me with v.77. Last one shipped was 8/9 (wow, maybe this one is a keeper).
jdmba said:
I am on my third incredible, and all 3 shipped to me with v.77. Last one shipped was 8/9 (wow, maybe this one is a keeper).
Click to expand...
Click to collapse
were these all brand new phones, refurbs..?
To my understanding of this whole .77, .79 HBOOT is that these two are interchangeable and doesn't matter which one you have. I was just curious because at first I used the RUU that gave me software 1.22.605.0 and the latest is 1.22.605.2 and I never got an OTA update for the latest 2.1. but I think this is normal since the servers are doing the new thing.
and from what I think, if you had .77, and got the OTA for the latest 2.1 that came out a while ago, it kept the .77, but if you did the latest 2.1 through the RUU on ur computer instead of OTA it updated the HBOOT to .79 as well.
This is how it was with the Droid Eris with the leaks and stuff which blocked you out of root.
...
BlazeD OnE said:
were these all brand new phones, refurbs..?
Click to expand...
Click to collapse
Phone # 1 - New ... would get hotter and hotter (even when not in use) until it would enter a reboot cycle. It would also reboot randomly during the day.
Phone # 2 - Refurb ... got it with a bad speaker, but otherwise it worked perfectly.
Phone # 3 - Refurb ... still going.
boomertwo said:
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
Click to expand...
Click to collapse
in theory that should work.
k.electron said:
in theory that should work.
Click to expand...
Click to collapse
Well I took the plunge and can confirm that the method in my original post does work and without a hitch(For me at least.)I did this after reading another question thread that had a guy basically asking the same thing and was recommended just to follow to step 6. I cannot link to anything yet so I will just give you the thread title that is located in the Q&A section of this forum for the droid incredible.
Thread Title: "[Q] Applying RUU update to stock phone"
The phone did however reboot the bootloader and put me into fastboot. I did not pull the battery but instead selected bootloader again and it continued the update on its own.
I'm successfully not root and s-on with android 2.2(HTC stock)
Hboot .92
Stock Recovery.
*Before you say it.. I know I'm now not able to get root till unrevoked or another dev team releases new tools for this version. I did this by choice*
*I in no way will recommend anyone to do this and will not take responsibility for your phone being turned into a paper weight* < You have been warned..
Sooooo.. anyone want to clarify how to extract rom.zip from the RUU please?
Just download the extracted ROM. It's on page 6 or 7 in the RUU thread.
NinjaRicky said:
Sooooo.. anyone want to clarify how to extract rom.zip from the RUU please?
Click to expand...
Click to collapse
did you get it?
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.
Hi everyone,
I've downloaded the latest OTA update (1.7.405.2). The phone reboots and starts the update process but fails at some point by displaying the red triangle hazard.
Could some please tell me what's going on? I never had any problems installing OTAs before.
I have Visionary installed with PermRoot.
Your help is greatly appreciated.
I got the same problem, first OTA on my phone.
Seems like the PermRoot breaks the update.
There are countless other threads saying basically the same.
Installed Visionary+, Rooted, Removed HTC apps, OTA Update doesn't work.
Click to expand...
Click to collapse
You could try installing via bootloader, but your DHD would return to factory settings.
Download This ROM. Rename it to PD98IMG.zip and place on your SD Card.
Turn off your DHD (Disable FastBoot) and power on holding VOL DOWN.
Your DHD will then apply the update itself. With the new update you will not be able to root, HTC have fixed the exploit Visionary+ used. A new method to root will have to be found.
It could be worth having a sticky mentioning that being permrooted stops the updates from performing with instructions to unroot the phone possibly?
I have made an update without any problems. I had stock ROM (no root, nothing). Downloaded around 40 MB, installation process took about 5-10 minutes. I have noticed after update - during video rec camera became smoother (better), aslo before the update I had a problem with 3g internect connectivity. When I switched on the Router on my DHD, 3G connectivity used to went off (dissapear) from the bar. And I had to switch it off mannualy and on again to make it work. After update this is gone! Now router works perfect on DHD.
andyharney said:
Seems like the PermRoot breaks the update.
There are countless other threads saying basically the same.
Click to expand...
Click to collapse
I had visionary+, permroot, all htc aps on stock. Update took a loooong time but my DHD turned on
I think PermRoot does not break the update.
Installed Visionary+, Rooted,Removed HTC apps, OTA Update doesn't work.
Click to expand...
Click to collapse
That breaks the update.
SIRJEDI said:
I had visionary+, permroot, all htc aps on stock. Update took a loooong time but my DHD turned on
I think PermRoot does not break the update.
Click to expand...
Click to collapse
Yes, permroot does not break the update because it does not change or remove anything on /system. It just adds su and Superuser.apk. As soon as you remove something stock, or change anything stock (like build.prop) it breaks.
Hmmm,,,, I am kindoff waiting for root,,, else its no fun,,
Sent from my Desire HD using XDA App
Help
Hi guys. I have a 1 week old DHD. Its not rooted, i dont even deleted any HTC software. I didnt use anything strange. I used launcher pro but doesnt matter...
I get the same red rectangle... Do you know why? And how can i solve it?
Don't upgrade it the official way. Unless you are 200% sure you don't need root.
Sent from my performance enhanced Desire HD.
So here's my story. I bought my VZW HTC One on day one. Brought it home and immediately unlocked (via HTCDev) and rooted it before Verizon blocked the unlock the next day. So I am bootloader unlocked, rooted, and S-ON. Now here is where I screwed up in two areas. The first being that I think I have somehow over written the original stock recovery with my Frankenstein one. So the Frankenstein one is that I originally had an HTC Incredible 2 unlocked, rooted, and S-OFF and I took my last full TitaniumBackup from the Inc2 and restored it to the new HTC One. The problem with doing this was the backed up system files from the Inc2 were applied to the One and now it causes some strange crashes when using some of the HTC sense apps such as HTC's contact list. However in this strange setup most everything works perfectly and I've left it this way since that first day. The other annoyance here is that I keep getting reminded to install some of the OTA updates that have come out but it will not install them so I've missed them all and it stills keeps alerting me to install them.
Now what would I like to do from here? I would like to be able to keep root, keep unlock, gain S-OFF and start over with stock rom and be able to get the OTA updates (if possible). This way I can still get back to the backups I have made in Titanium, only this time instead of restoring all, I would only restore hand picked apps, leaving out the old Inc2 system files. Is there anyone out there who would be willing to help me with step-by-step detailed instructions? I would greatly appreciate it.
lostnsound said:
So here's my story. I bought my VZW HTC One on day one. Brought it home and immediately unlocked (via HTCDev) and rooted it before Verizon blocked the unlock the next day. So I am bootloader unlocked, rooted, and S-ON. Now here is where I screwed up in two areas. The first being that I think I have somehow over written the original stock recovery with my Frankenstein one. So the Frankenstein one is that I originally had an HTC Incredible 2 unlocked, rooted, and S-OFF and I took my last full TitaniumBackup from the Inc2 and restored it to the new HTC One. The problem with doing this was the backed up system files from the Inc2 were applied to the One and now it causes some strange crashes when using some of the HTC sense apps such as HTC's contact list. However in this strange setup most everything works perfectly and I've left it this way since that first day. The other annoyance here is that I keep getting reminded to install some of the OTA updates that have come out but it will not install them so I've missed them all and it stills keeps alerting me to install them.
Now what would I like to do from here? I would like to be able to keep root, keep unlock, gain S-OFF and start over with stock rom and be able to get the OTA updates (if possible). This way I can still get back to the backups I have made in Titanium, only this time instead of restoring all, I would only restore hand picked apps, leaving out the old Inc2 system files. Is there anyone out there who would be willing to help me with step-by-step detailed instructions? I would greatly appreciate it.
Click to expand...
Click to collapse
I would
1) flash the signed RUU (not 100% necessary)
1a) Gain S-OFF using rumrunner (it supports ALL versions, so just download the correct one, I am assuming 1.10.605.8 as you said you missed the two OTA updates)
2) Once you are S-OFF, go into fastboot, and fastboot flash the stock recovery.
3) Now that you are S-OFF and on the stock recovery you may take the OTA (Or just flash a ROM such as Santod040's that is based on it, that's what you do when rooted, NEVER take an OTA just wait for ROM DEVs, but these two OTA's have been deemed OK and doesn't touch root)
I don't know a thing about Titanium backup, sorry.
Best to start fresh on the HTC One, IMHO.
Thanks so much for the response! This is very helpful. One question though, after getting S-OFF from Rumrunner you say to flash stock recovery. I'm not sure if it is still intact or not. Can I just proceed with flashing the ROM or is it absolutely necessary to flash stock recovery first?
Sent from my HTC6500LVW using Xparent BlueTapatalk 2
andybones said:
I would
1) flash the signed RUU (not 100% necessary)
1a) Gain S-OFF using rumrunner (it supports ALL versions, so just download the correct one, I am assuming 1.10.605.8 as you said you missed the two OTA updates)
2) Once you are S-OFF, go into fastboot, and fastboot flash the stock recovery.
3) Now that you are S-OFF and on the stock recovery you may take the OTA (Or just flash a ROM such as Santod040's that is based on it, that's what you do when rooted, NEVER take an OTA just wait for ROM DEVs, but these two OTA's have been deemed OK and doesn't touch root)
I don't know a thing about Titanium backup, sorry.
Best to start fresh on the HTC One, IMHO.
Click to expand...
Click to collapse
#2 is not necessary. The RUU will flash a stock recovery.
sorry guys, was late. def no need to re-flash stock recovery after RUU. Noob mistake, my apologies
OK, I'm not very familiar with RUU's. Where does this come from? A quick search in the forum yielded a list of a bunch of them. I'm not sure which one is the right one. To me they don't look any different from custom ROMs. Sorry for being a noob, still learning how all this works.
Sent from my HTC6500LVW using Xparent BlueTapatalk 2
when you go into fastboot mode on your phone read and see what the radio you have... and based on that number you could get rumrunner and also you can get the right RUU i dont know if the RUU will relock the phone tho but i think you can unlock it if you saved the tocken in case you dont want to get s-off
---------- Post added at 06:04 AM ---------- Previous post was at 06:00 AM ----------
and dont worry we all were noobs before, fact im a noob when it comes to HTC phone used to have Motorolas.. but couldnt overlook the speakers on this beauty...