Related
Howdy!
What is this?
This is a PH39IMG.zip that you flash via HBOOT to restore your phone to stock unrooted Gingerbread shipping ROM. This will also remove Clockwork Recovery
Click to expand...
Click to collapse
Why should I use this/care?
If you've updated your phone to the Ice Cream Sandwich build that AT&T pushed out OTA, or flashed your phone manually, you may at some point in time wish to go back to Gingerbread.
If you do, you'll find that the PH39IMG.zip and RUU that you would have previously tried to use don't work, since ICS updated your HBOOT.
This is essentially a "return to warranty" kit. This doesn't remove the "*UNLOCKED*" flag on HBOOT, but it will allow you to return to some semblance of stock just in case.
Click to expand...
Click to collapse
How do I use this?
Your bootloader must be unlocked to flash this.
Download the file, put it on your external SD, and boot to HBOOT. Accept the update when prompted.
If you're trying to return your phone to AT&T for warranty, you should probably also re-lock your bootloader also ("fastboot oem lock")
Please note!
This is not for HTC Raider / Velocity / Generic Holiday users!
This restores the shipping HTC Vivid ROM for AT&T.
Click to expand...
Click to collapse
Downloads
Restore to unrooted Gingerbread Stock: http://goo-inside.me/private/iomonster/htcvivid/roms/restore-gb-from-ics/PH39IMG.zip
Click to expand...
Click to collapse
Hopefully this should alleviate some of the fears associated with updating your phone.
I will upload a "return to stock ICS" ph39img here too soon...
<Removed>
Youssarian said:
Ok, I was stuck in boot loop after OTA, then going to the rooted rom. Could not get it to play nice. Tried this to take me back to GB so I could start over and did the above exactly. After running the update, which appears to work with the little status bar going up and down as it should, it gets stuck at the Hboot screen. (Attached.)
After pulling the battery, it boots to HTC white screen, reboots once, then sticks on the HTC white screen. I can get back to Hboot, but not sure where to proceed from here?
Click to expand...
Click to collapse
How do you have S-OFF?
Sent from my HTC PH39100
JEANRIVERA said:
How do you have S-OFF?
Sent from my HTC PH39100
Click to expand...
Click to collapse
His device came like that when it was purchased
Sent from my HTC Holiday
Youssarian said:
Ok, I was stuck in boot loop after OTA, then going to the rooted rom. Could not get it to play nice. Tried this to take me back to GB so I could start over and did the above exactly. After running the update, which appears to work with the little status bar going up and down as it should, it gets stuck at the Hboot screen. (Attached.)
After pulling the battery, it boots to HTC white screen, reboots once, then sticks on the HTC white screen. I can get back to Hboot, but not sure where to proceed from here?
Click to expand...
Click to collapse
What I did was take out the sd card and put into a card reader and deleted the ph file then booted back into fastboot to finish process
Sent from my HTC Flyer P510e using Tapatalk
Youssarian said:
Ok, I was stuck in boot loop after OTA, then going to the rooted rom. Could not get it to play nice. Tried this to take me back to GB so I could start over and did the above exactly. After running the update, which appears to work with the little status bar going up and down as it should, it gets stuck at the Hboot screen. (Attached.)
After pulling the battery, it boots to HTC white screen, reboots once, then sticks on the HTC white screen. I can get back to Hboot, but not sure where to proceed from here?
Click to expand...
Click to collapse
You need to pull the PH39IMG.zip file off your SD card as Hboot looks for it to see if an update is available before it does anything else.
Sent from my HTC PH39100 using xda premium
<Removed>
removed........
Is there anyway to flash this on lock boot loaders.
Sent from my Galaxy Nexus using xda premium
Dxtra said:
Is there anyway to flash this on lock boot loaders.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
If your bootloader was relocked prior to attempting to flash the RUU or PH39img.zip, then youre doing the right thing.
8125Omnimax said:
If your bootloader was relocked prior to attempting to flash the RUU or PH39img.zip, then youre doing the right thing.
Click to expand...
Click to collapse
I've never got a chance to unlock the bootloaders. I was completely stock before the ics update.
Sent from my Galaxy Nexus using xda premium
You must have your bootloader unlocked to flash this image. You can re-lock it afterwords, but you may get a *SECURITY WARNING* in HBOOT, since if you have the new HBOOT, you technically should also have stock ICS.
Until a *working* ICS RUU surfaces, this is as good as it gets.
thecubed said:
Until a *working* ICS RUU surfaces, this is as good as it gets.
Click to expand...
Click to collapse
i posted a working RUU already....
Pirateghost said:
i posted a working RUU already....
Click to expand...
Click to collapse
Of the same version as the OTA? Apologies if so
thecubed said:
Of the same version as the OTA? Apologies if so
Click to expand...
Click to collapse
2 minor revisions lower than the OTA.....but it serves as an EASY way for the ravenous n00bs to get ICS
Pirateghost said:
2 minor revisions lower than the OTA.....but it serves as an EASY way for the ravenous n00bs to get ICS
Click to expand...
Click to collapse
And that's why I just downloaded and am installing now! Thanks much!!
hey cubed, how are you?
before unlocking bootloader, i flashed the ics ruu so i'm on new hboot and radio,
since i unlocked bootloader and running a wc's 3.5 rom, however i have an issue, when i talk on the phone from speaker, ppl hear their echo, so i'm thinking radio issue, i tried to flash back the gb ruu and no go cuz of bootloader, so i downgraded with the method in OP but it didn't downgrade radio, i tried again to flash gb ruu and no luck, i put the radio.img from the gb ruu into ur zip and now it won't recognize it at all (guessing due to signature) so i'm flashing the stock ics ruu now to see if im gona have the same problem or not. by the way when i flashed ur downgrade zip and loaded, the phone would not connect to any network at all and being a stock rom the option to search for network is greyed out.
so i'm guessing bottom line is im stuck with this new radio since we don't have s-off correct?
is there any way so far to totally downgrade back to the original ship ruu ? bootloader, radio and all ?
thanks
lebmb said:
hey cubed, how are you?
before unlocking bootloader, i flashed the ics ruu so i'm on new hboot and radio,
since i unlocked bootloader and running a wc's 3.5 rom, however i have an issue, when i talk on the phone from speaker, ppl hear their echo, so i'm thinking radio issue, i tried to flash back the gb ruu and no go cuz of bootloader, so i downgraded with the method in OP but it didn't downgrade radio, i tried again to flash gb ruu and no luck, i put the radio.img from the gb ruu into ur zip and now it won't recognize it at all (guessing due to signature) so i'm flashing the stock ics ruu now to see if im gona have the same problem or not. by the way when i flashed ur downgrade zip and loaded, the phone would not connect to any network at all and being a stock rom the option to search for network is greyed out.
so i'm guessing bottom line is im stuck with this new radio since we don't have s-off correct?
is there any way so far to totally downgrade back to the original ship ruu ? bootloader, radio and all ?
thanks
Click to expand...
Click to collapse
I really don't think it's a radio issue. I believe it's a network issue. I've had an echo on several devices I've used from the original iPhone through iPhone 4 blackberrys inspire and now vivid. But it is not all the time just every once in a while.
Sent from my HTC PH39100 using Tapatalk
jayv81 said:
I really don't think it's a radio issue. I believe it's a network issue. I've had an echo on several devices I've used from the original iPhone through iPhone 4 blackberrys inspire and now vivid. But it is not all the time just every once in a while.
Sent from my HTC PH39100 using Tapatalk
Click to expand...
Click to collapse
yeah i've had it happen randomly before in some phones, but this is consistent every single call for the past 3 days. in different areas, with different people at different times.
i just finished flashing the stock ics ruu and it connected to the network fine and made a couple of quick phone calls and no echo
btw the ppl i talk to hear them selves, i don't hear any echo, it all sounds well on my end. im gona try another 3.5 rom and see what happens
EDIT: just tried holiraider, and it did it. leme see what other roms i can flash
so a quick update, even with a custom sense 3.0 rom, i can't connect to a network at all, it only works with 3.5 roms and i people i talk to have an echo, and only fix is running an ics rom, for some reason when i push the ics ril files into a 3.5 rom i loose all network connections, baseband says unknown and all the phone info except serial number is unknown in the hardware info.
so very strange. so even when using this guide, and restoring the fully stock gb i still cant use the phone
uploaded wrong screenies, i'll update in a sec
EDIT: well i tried again, and flashed thecubed zip and i'm back on the stock 3.0 unrooted, and i noticed that i was able to get the signal up and running when i toggle wifi. by default on first boot its on, so i connected to my wifi as usual, but i dunno why i just turned it off so the network came right up and all was fine with the signal. i turned wifi back on and no problems. i turned it off, no problems. so i restarted the phone, and it won't connect to the network, so i turn wifi on and now i am connected and have full signal. strange, so i wonder if that's due to the radio, or something happened to my phone since i seem to be the only one having those issues
really sorry for starting a new thread but i've been searching like crazy and i have not found anything like what i have to deal with.
So the phone WAS a stock rogers Raider, sim unlocked when i bought it. Everything was okay until i started messing around with it.
What has happened to the phone:
I used hasoon's kit to unlock the bootloader and gain root access, along with rom manager and cwm because i wanted to download an ics rom for my phone. well the VERY NEXT DAY the stock ota update for ics came out for my phone, and when i tried to update it the official way it would get stuck on the htc screen until my battery completely died beyond repair, so 2 weeks later when the new battery came in the mail, i was still rooted and on 2.3. I learned after that the ota updates do not work on my rooted phone for some reason, so i tried to install an ics rom through clockworkmod recovery, and now when i try to boot my phone it gets stuck at the htc screen and doesnt do anything more, but using power and vol. UP i can still access hboot, which says "unlocked with s-on" ive tried to hit "factory reset" but it still wont boot.
If possible, what i would like to do to the phone:
Completely restore the phone to stock, locked bootloader, unrooted, and to a stock gingerbread so i can install the ota ice cream sandwich update.
I know i'm asking for a ton of help but please hear me out, im honestly getting depressed because of this darn phone.
Also, please use words as simple as you can because im really not the type of person who shouldve even started with all this stuff!
jperta said:
really sorry for starting a new thread but i've been searching like crazy and i have not found anything like what i have to deal with.
So the phone WAS a stock rogers Raider, sim unlocked when i bought it. Everything was okay until i started messing around with it.
What has happened to the phone:
I used hasoon's kit to unlock the bootloader and gain root access, along with rom manager and cwm because i wanted to download an ics rom for my phone. well the VERY NEXT DAY the stock ota update for ics came out for my phone, and when i tried to update it the official way it would get stuck on the htc screen until my battery completely died beyond repair, so 2 weeks later when the new battery came in the mail, i was still rooted and on 2.3. I learned after that the ota updates do not work on my rooted phone for some reason, so i tried to install an ics rom through clockworkmod recovery, and now when i try to boot my phone it gets stuck at the htc screen and doesnt do anything more, but using power and vol. UP i can still access hboot, which says "unlocked with s-on" ive tried to hit "factory reset" but it still wont boot.
If possible, what i would like to do to the phone:
Completely restore the phone to stock, locked bootloader, unrooted, and to a stock gingerbread so i can install the ota ice cream sandwich update.
I know i'm asking for a ton of help but please hear me out, im honestly getting depressed because of this darn phone.
Also, please use words as simple as you can because im really not the type of person who shouldve even started with all this stuff!
Click to expand...
Click to collapse
Use the guide in my signature. It's step 6. Basically what it entails is relocking the bootloader (an OTA, RUU, PH zip all won't work with an unlocked bootloader), then running the Rogers ICS RUU for your device (the link for that is in the guide). The RUU does the same thing as the OTA. That's the easiest way to do it. No need to mess around with going back to stock GB and all that. You can go straight to stock ICS if you re-lock your bootloader and run the ICS RUU.
jperta said:
really sorry for starting a new thread but i've been searching like crazy and i have not found anything like what i have to deal with.
So the phone WAS a stock rogers Raider, sim unlocked when i bought it. Everything was okay until i started messing around with it.
What has happened to the phone:
I used hasoon's kit to unlock the bootloader and gain root access, along with rom manager and cwm because i wanted to download an ics rom for my phone. well the VERY NEXT DAY the stock ota update for ics came out for my phone, and when i tried to update it the official way it would get stuck on the htc screen until my battery completely died beyond repair, so 2 weeks later when the new battery came in the mail, i was still rooted and on 2.3. I learned after that the ota updates do not work on my rooted phone for some reason, so i tried to install an ics rom through clockworkmod recovery, and now when i try to boot my phone it gets stuck at the htc screen and doesnt do anything more, but using power and vol. UP i can still access hboot, which says "unlocked with s-on" ive tried to hit "factory reset" but it still wont boot.
If possible, what i would like to do to the phone:
Completely restore the phone to stock, locked bootloader, unrooted, and to a stock gingerbread so i can install the ota ice cream sandwich update.
I know i'm asking for a ton of help but please hear me out, im honestly getting depressed because of this darn phone.
Also, please use words as simple as you can because im really not the type of person who shouldve even started with all this stuff!
Click to expand...
Click to collapse
You need to read before you jump the gun and mess around
First of all you can't be rooted and you can't have an unlocked bootloader for official updates/ruus
Second you can't flash ics unless you are s off and get an ics hboot
Here's the fix,
1) download the ruu from HTC website...I can try and find a link later
2) boot into hboot then fastboot
3) run the tool kit and use the relock bootloader option
4) if your phone reboots just go back to fastboot
5) if your bootloader now says relocked then just run the ruu
Ruu is official update done through a computer
Sent from my HTC PH39100 using Tapatalk 2
resuldsd (Simonds)
mg2195 said:
You need to read before you jump the gun and mess around
First of all you can't be rooted and you can't have an unlocked bootloader for official updates/ruus
Second you can't flash ics unless you are s off and get an ics hboot
Here's the fix,
1) download the ruu from HTC website...I can try and find a link later
2) boot into hboot then fastboot
3) run the tool kit and use the relock bootloader option
4) if your phone reboots just go back to fastboot
5) if your bootloader now says relocked then just run the ruu
Ruu is official update done through a computer
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Thank you both for your replies, i absolutely agree i really regret doing this, a link would be greatly appreciated too. and i just relocked my bootloader and it says "relocked security warning" so i guess its relocked, and finally how would i run the ruu? Im really sorry for being so clueless
The ICS Rogers RUU is here. Just boot into hboot and run it on your computer.
psmpar traditional
slapshot30 said:
The ICS Rogers RUU is Just boot into hboot and run it on your computer.
Click to expand...
Click to collapse
okay thanks so much, it always says "All free download slots are in use" which is strange because it only says that when i try to download the rogers ruu. i guess i just have to wait.
*update*
okay one more annoying question i promise. if i download gingerbread ruu from hotfile, i cant post the link but from another thread it works, and by doing what you said, hboot, plugin to computer and run the .exe, can i then upgrade to 4.0 by using the ota?
When i re-locked my bootloader, to confirm i went into h-boot, and it should say "Re locked bootloader".
But follow slapshot guide to the tee and you'll be good.
Sent from my HTC-X710a using xda app-developers app
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
mikhailov1 said:
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
Click to expand...
Click to collapse
try this http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
it worked for some users
Thanks. Will try when I get home. I was able to use my Win 7 computer at work to unlock the boot loader again, but I cannot get S Off. I ran rumrunner and it looked like it was working, but then said FATAL: download update. Is there no rumrunner for GPE?
Sent from my HTC One using Tapatalk
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Prash8429 said:
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Click to expand...
Click to collapse
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
mikhailov1 said:
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
Click to expand...
Click to collapse
you can still get OTA with a rooted phone, as long as you have stock recovery and flashed stock ruu.... tip if your having trouble with flashing ruu change the zip file name to something simple like ruu.zip worked for me.:good:
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Can you tell me if your bootloader was 1.54 or 1.55? I have been unable to get Windows 8.1 to recognize the 1.54 bootloader. It always says "device not recognized" If yours was 1.54.0000 I will try this fix. Thanks.
I am 1.54.
Sent from my Nexus 5 using Tapatalk
Thanks for this, helped me out alot
Sent from my HTC One using XDA Premium 4 mobile app
I Recently Bought an Htc one (M7) {running android 4.3} from an electronics shop well 4.4 Kitkat Just came out so I was all excited to update to check out all the changes... sadly I was mistaken. The previous owner had tried to root the phone so im stuck with a phone that is "Tampered" "Unlocked"
with "s-on" not to bad right? well the recovery on the phone is Team win project recovery... and the phone is not rooted
I want to return the phone to stock or at least beable to get normal ota updates
Can some one give me a detailed step by step walkthrough of how to switch the phones recovery back to stock im not very tech savy in this field
Smerfurdt92 said:
I Recently Bought an Htc one (M7) {running android 4.3} from an electronics shop well 4.4 Kitkat Just came out so I was all excited to update to check out all the changes... sadly I was mistaken. The previous owner had tried to root the phone so im stuck with a phone that is "Tampered" "Unlocked"
with "s-on" not to bad right? well the recovery on the phone is Team win project recovery... and the phone is not rooted
I want to return the phone to stock or at least beable to get normal ota updates
Can some one give me a detailed step by step walkthrough of how to switch the phones recovery back to stock im not very tech savy in this field
Click to expand...
Click to collapse
you have to flash a RUU
Boachti said:
you have to flash a RUU
Click to expand...
Click to collapse
Its a Tmobile phone is there one for tmobile?
and doesnt that require s-off?
well the ruu I tried wouldnt even run on my Laptop
There are some T-Mobile RUU's. Check the T-Mobile forum. Specifically this thread: http://forum.xda-developers.com/showthread.php?t=2496074
Me personally I would check to see what HBOOT version is on there and if it's lower than 1.57, go S-OFF before doing anything else. Then just use TWRP to flash a stock or stock-ish 4.4 ROM and never mind OTA's.
Sent from my HTC One using xda app-developers app
NxNW said:
There are some T-Mobile RUU's. Check the T-Mobile forum. Specifically this thread: http://forum.xda-developers.com/showthread.php?t=2496074
Me personally I would check to see what HBOOT version is on there and if it's lower than 1.57, go S-OFF before doing anything else. Then just use TWRP to flash a stock or stock-ish 4.4 ROM and never mind OTA's.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thank you guys im looking further into it. Does the phone need to be rooted to flash a rom or just have the bootloader unlocked?
For kit Kat it needs to be s-OFF. Let's get that out of the way first.
And some s-OFF methods require a rooted ROM to work as I recall. So it's already getting complicated.
But a typical custom Rom doesn't *need* root, in fact after flashing you will discover it *gives* you root.
Going that route requires work and some reading. Then again, getting an RUU to run successfully does too.
Basically the situation you''re in is not horrible, but to go all the way forward (S-OFF Kit Kat with ability to do anything you want in the future) or all the way back (totally locked down stock system capable only of accepting OTA's ) will require work either way.
Sent from my HTC One using xda app-developers app
So basicaly it may be simpler if I...
1 s-off
2 download rom
2.5 put on phone memory
3 go to team win recovery
4 Click install and choose said rom?
is that the basics of it?
if I want the least amount of trouble?
Also I guess what makes this most confusing for me is the non stock recovery
and to use fire water for the s-off I need to remove htc sync from the phone?
I feel im doing more work and stressing than i should be?
Yes Im quite Noobish..
Pretty much yes.
There could be adventures along the way, but I think this outcome would position you well for the future.
The biggest question is how old is your HBOOT.
There is no S-OFF for 1.57 and existing exploits for 1.56 don't always work.
If you can get S-OFF, you can do anything, including a) destroying your phone by mistake; b) changing your mind later and going back to S-ON; and, my personal favorite, c) destroying your phone in the act of trying to go back to S-ON (due to modified/ damaged HBOOT partition).
If you can't get S-ON, well, see if you can get back to stock.
Occasionally you are truly stuck and can neither go forward nor backward.
Which in your case is not so bad. 4.3 works great. Honestly plenty of people here are trying to go *back* to 4.3 after trying 4.4.
With S-OFF you can always do that. S-ON, not so much..
Sent from my HTC One using xda app-developers app
Yeah.. now i have a pretty blue screen that once every 10 minutes or so will flash the google logo so yup bricked...
That would qualify as an "adventure". Still, it sounds like something less than "bricked".
See if you can enter HBOOT (hold down volume-down and power buttons for a few seconds or if you're in a boot loop , just hold down volume-down as phone is booting up).
If so, you can select fastboot and you should have the option to power down. That should give the battery a rest and give you time to think.
At some point you need to have the android tools fastboot and adb set up on your computer.
When you do, enter HBOOT, select fastboot (with phone plugged into computer via USB) and run the command fastboot getvar all.
Post the results here.
The first post of this thread doesn't really contain enough detail for others to help you otherwise.
Sent from my HTC One using xda app-developers app
Hi All,
I'm new here and I came here because of some verizon HTC One (M7, cid = vzw001) troubles.
Last year when I got the phone I was intent on making it like a Google play edition phone. I did rumrunner to get s-off and I unlocked the bootloader somehow (I don't remember) and rooted it. I tried flashing a GPE rom but being a noob, I flashed a GSM rom and it did not boot. In a frantic effort to make my phone usable I downloaded a deodexed verizon stock rom and flashed it, and thankfully it worked. I was able to get the Sense 5.5 OTA update after that. A little while later, I installed TWRP because I did not have a recovery at all. Now the Sense 6 update has been out for awhile now and I had tried updating to it but it would take me straight to TWRP and stop. Later on I read about how TWRP stops OTA updates so I installed a stock recovery. I also uninstalled root. Today I looked at my mom's HTC One, and I looked at her stats under Recovery Menu:
hboot: 1.57
radio: 1.13.41.0.421
OS: 4.10.605
I flashed a 1.13.41.0.421 radio and updated somehow the hboot got updated when tinkering and now all those specs match my Mom's, but it is obviously not the same OS. My phone from the settings says it is 4.4.2, 3.11.605.1.
What can I do to essentially return it to fresh out of the box state with restored ota capability? I want to be able to update normally like my Mom's phone and I don't care about root access. I'm not sending it in for warranty do I don't care about turning S-ON or dealing with tampered flags.
Also I'm sort of a noob. I only have a basic idea on how to use fastboot, so a step by step walkthrough would be helpful.
Thanks,
sugehtc
surgehtc said:
Hi All,
I'm new here and I came here because of some verizon HTC One (M7, cid = vzw001) troubles.
Last year when I got the phone I was intent on making it like a Google play edition phone. I did rumrunner to get s-off and I unlocked the bootloader somehow (I don't remember) and rooted it. I tried flashing a GPE rom but being a noob, I flashed a GSM rom and it did not boot. In a frantic effort to make my phone usable I downloaded a deodexed verizon stock rom and flashed it, and thankfully it worked. I was able to get the Sense 5.5 OTA update after that. A little while later, I installed TWRP because I did not have a recovery at all. Now the Sense 6 update has been out for awhile now and I had tried updating to it but it would take me straight to TWRP and stop. Later on I read about how TWRP stops OTA updates so I installed a stock recovery. I also uninstalled root. Today I looked at my mom's HTC One, and I looked at her stats under Recovery Menu:
hboot: 1.57
radio: 1.13.41.0.421
OS: 4.10.605
I flashed a 1.13.41.0.421 radio and updated somehow the hboot got updated when tinkering and now all those specs match my Mom's, but it is obviously not the same OS. My phone from the settings says it is 4.4.2, 3.11.605.1.
What can I do to essentially return it to fresh out of the box state with restored ota capability? I want to be able to update normally like my Mom's phone and I don't care about root access. I'm not sending it in for warranty do I don't care about turning S-ON or dealing with tampered flags.
Also I'm sort of a noob. I only have a basic idea on how to use fastboot, so a step by step walkthrough would be helpful.
Thanks,
sugehtc
Click to expand...
Click to collapse
Here is a step by step instructions for returning to stock. There is a Verizon HTC One Forum which has a ton of information much more than this forum. The Verizon phone is very different than the GSM version.
majmoz said:
Here is a step by step instructions for returning to stock. There is a Verizon HTC One Forum which has a ton of information much more than this forum. The Verizon phone is very different than the GSM version.
Click to expand...
Click to collapse
I read the thread but the link to the decrypted ruu was gone.
---------------------------------------------------------------------------------------------------------------------
I flashed a 1.44 hboot
and the did fastboot reboot-bootloader
it went to a bootloop and I cant use fastboot
When I plug in my phone to the computer
my phone never says fastboot usb
Windows also says "malfuctioning device"
When I press power on
It goes to boot loop
I can enter the recovery menu
I have no idea how to use adb.
I think I'm screwed.
surgehtc said:
I read the thread but the link to the decrypted ruu was gone.
---------------------------------------------------------------------------------------------------------------------
I flashed a 1.44 hboot
and the did fastboot reboot-bootloader
it went to a bootloop and I cant use fastboot
When I plug in my phone to the computer
my phone never says fastboot usb
Windows also says "malfuctioning device"
When I press power on
It goes to boot loop
I can enter the recovery menu
I have no idea how to use adb.
I think I'm screwed.
Click to expand...
Click to collapse
It looks like you got a corrupt hboot flash. I hope you got the hboot from the Verizon forum instead of this forum. This forum is geared to the GSM phones not the CDMA phones. You need to find a hboot for a Verizon phone in zip format to flash in recovery. The hboot controls the bootloader, so this could be the issue.
If you get that straighten out and you are able to use fastboot again, this post has a stock rom and firmware you can flash. Then you would have been back to stock. Spend time in the Verizon forum.
majmoz said:
It looks like you got a corrupt hboot flash. I hope you got the hboot from the Verizon forum instead of this forum. This forum is geared to the GSM phones not the CDMA phones. You need to find a hboot for a Verizon phone in zip format to flash in recovery. The hboot controls the bootloader, so this could be the issue.
If you get that straighten out and you are able to use fastboot again, this post has a stock rom and firmware you can flash. Then you would have been back to stock. Spend time in the Verizon forum.
Click to expand...
Click to collapse
I did get it from the verizon section.
But I have no custom recovery and no fastboot
I can't adb sideload either.
What should I do?