getting from a to be. need help with a lot! - HTC Rezound

ok so ill be honest. ive been out of the loop for a long time and have very little idea whats going on with android development and whatnot. im hoping someone can help me get to where i need to get. attached are screenshots of what firmware im on and and rom. i want to get onto cm9 and i have tried flashing it but it wouldnt boot. i think i have s-off and i dont know how to unlock it. (noob i know) any info helps and id really appreciate it. thanks

LWell, we know you are bootloader unlocked because you have a custom ROM installed. If you want CM9, and you are s-on, make sure you follow the instructions in the OP of that thread.
You can check your s-off status by shutting your phone off, pull battery, put battery back in, and press volume down and power until you see the white screen. Up in the top right it will say either s-on or s-off.

edward650 said:
ok so ill be honest. ive been out of the loop for a long time and have very little idea whats going on with android development and whatnot. im hoping someone can help me get to where i need to get. attached are screenshots of what firmware im on and and rom. i want to get onto cm9 and i have tried flashing it but it wouldnt boot. i think i have s-off and i dont know how to unlock it. (noob i know) any info helps and id really appreciate it. thanks
Click to expand...
Click to collapse
If you're s-off, there is no reason to unlock (aside from fastboot commands, but that seems trivial once you've achieved s-off). Also, looks like you're on GB firmware. If I was you, I'd RUU with the latest leak from AndroidPolice. If you're s-off, it's easy. Just re-flash amonra 3.15 after you run the ruu. You'll have the latest radios, as well as ICS. That's where to start; then it's very easy to flash a CM9 ROM.

iamwalterwhite said:
If you're s-off, there is no reason to unlock (aside from fastboot commands, but that seems trivial once you've achieved s-off). Also, looks like you're on GB firmware. If I was you, I'd RUU with the latest leak from AndroidPolice. If you're s-off, it's easy. Just re-flash amonra 3.15 after you run the ruu. You'll have the latest radios, as well as ICS. That's where to start; then it's very easy to flash a CM9 ROM.
Click to expand...
Click to collapse
i thought it had s-off but it is on and the top says unlocked. how can i changed it back to off? when trying to get on the RUU leak it wont work, ill try again tomorrow but maybe you know whats up

So you're S-On and locked, but you want to be S-Off? You need to run Jupunout-Bear if you just want to be unlocked go to HTC Dev. If you're unlocked your boot and radio partitions are still locked, but can be flashed via the fastboot command. If you're S-Off you can do it directly from the phone.
The wire trick for S-Off can be tricky to do perfectly, since you need to time it correctly which is 1.5 seconds. Someone made a metronome sound file but its a pain to start the process, play the sound file and then do the wire trick. I found out that the easiest way to do is it to just skip the file and use a rigid piece of wire and start with the ground pin depressed and then tap pin 1 twice since it's a lot harder to miss than by doing it vice versa, which I did multiple times. Also the words mississippi mississippi when said at a normal speed equal just about 1.5 seconds.

Related

[Q] How do I get back to hboot 1.4 from 1.5 with s-off?

So I had some "help" from a well meaning visiting nephew who was playing with my phone and noticed that I had an update available and decided that I should really have the latest software on my phone...so now I am on 2.17 with hboot 1.5, locked bootloader and all with no custom recovery BUT I am still s-off. I have a NAND backup that is not to old that I did with CWM, but how do I get to that to install it?
I have been looking for several hours and cant seem to find a solution...maybe I'm just searching under the wrong keywords...nevertheless HELP!!!!!!!
I am in the process of downloading a 1.13 stock ruu. Will that work or is there a quicker way to get this done?
I would prefer to avoid HTC unlock if I can, and my understanding is that with s-off, I should be able to.
Thanks for helping bail my ass out guys and girls!
(I thought about it, but no, I didnt beat the kid...his intentions were good...at least they better have been...)
Have you tried flashing a cwm recovery? I think I read someone had the same problem.seens your s-off you should still be able to flash a recovery, and after that's done then you can be able to wipe and flash anything you want, and you well even be able to downgrade your hboot.
Nope, it wont let me flash a recovery through fastboot...access denied (phone shows locked). I cant install it with "flash image gui" because i dont have root.
I know it should be an easy fix because I have the all important s-off...I just cant find how to do it.
taminrob said:
So I had some "help" from a well meaning visiting nephew who was playing with my phone and noticed that I had an update available and decided that I should really have the latest software on my phone...so now I am on 2.17 with hboot 1.5, locked bootloader and all with no custom recovery BUT I am still s-off. I have a NAND backup that is not to old that I did with CWM, but how do I get to that to install it?
I have been looking for several hours and cant seem to find a solution...maybe I'm just searching under the wrong keywords...nevertheless HELP!!!!!!!
I am in the process of downloading a 1.13 stock ruu. Will that work or is there a quicker way to get this done?
I would prefer to avoid HTC unlock if I can, and my understanding is that with s-off, I should be able to.
Thanks for helping bail my ass out guys and girls!
(I thought about it, but no, I didnt beat the kid...his intentions were good...at least they better have been...)
Click to expand...
Click to collapse
S-Off just means that the security is off, and you're able to write onto the boot partition of the phone when flashing a ROM, in one shot. If your Hboot = 1.50, you may have to unlock your bootloader via HTCDEV method, your phone gets wiped. Try HTC SuperTool, maybe it will work, since you're S-Off.
http://forum.xda-developers.com/showthread.php?p=21538250
Follow my post and the links in there should get you back to 1.4
Sent from my HTC Evo 3D using Tapatalk
Thank you, that got me back in where I needed to be! Was able to load CWM again and restored from my back up...now all I need to do is make since of all the conflicting instructions to do this update so the icon goes away...found some that are fairly clear, but the links are broken now that the upload sites are blacklisted.
Either way, just glad to have my hboot back where it belongs.

[Q] Looking to S-Off a friends Rezound...overview

So, coming from a Thunderbolt...rooting and getting s-off on a rezound seems like rocket science in comparison. I've read and read for the past four weeks but I'm asking for your guys' help and clarification before I proceed.
Here is what has happened so far: My buddies Rezound is currently HTC dev unlocked with a custom ICS rom on it with S-on. I want to get him s-off so flashing roms and kernels will be a piece of cake without adding a bunch more steps. I figured out how to do it and understand the process myself pretty clearly but trying to explain it to my buddy...yeah, I might as well be trying to teach him another language.
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms). This already is getting complex to me. On my good old thunderbolt I just had to use revolutionary to get s-off then it was flash whatever I wanted, gingerbread or froyo and flash compatible radios.
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
antiseen said:
So, coming from a Thunderbolt...rooting and getting s-off on a rezound seems like rocket science in comparison. I've read and read for the past four weeks but I'm asking for your guys' help and clarification before I proceed.
Here is what has happened so far: My buddies Rezound is currently HTC dev unlocked with a custom ICS rom on it with S-on. I want to get him s-off so flashing roms and kernels will be a piece of cake without adding a bunch more steps. I figured out how to do it and understand the process myself pretty clearly but trying to explain it to my buddy...yeah, I might as well be trying to teach him another language.
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms). This already is getting complex to me. On my good old thunderbolt I just had to use revolutionary to get s-off then it was flash whatever I wanted, gingerbread or froyo and flash compatible radios.
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
Click to expand...
Click to collapse
Just s-off on GB. You can do it on ICS or GB works the same way. Just if you RUU to ICS you will have to reunlock to soff.
Once s-off he can flash any ruu he wants in any order and keep s-off.
Also on a secondary note, you must have not had a thunderbolt when we first got s-off as getting s-off manually took about 30+ mins of constant cmd line use.
S-off on the rezound is much easier than it sounds. The only part that gives people trouble is the wire trick and mainly because it is all about timing.
Sent from my ADR6425LVW using XDA
I will say this outright: you can S-off right now using the GB package option on unlimited.io since that is the firmware you have. Answering the rest of this assuming an upgrade to ICS firmware, but that is the simplest path.
antiseen said:
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms).
Click to expand...
Click to collapse
Correct. If you're patching the firmware is still Gingerbread. Check in the bootloader for "hboot 2.11" to confirm this. Only way you can update firmware and radios while S-on is to run a RUU.
antiseen said:
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
Click to expand...
Click to collapse
When a phone gets an OTA update, it is expecting you to be on the latest official release. That currently is the 2.01.605.11 Gingerbread build, the first OTA we had. That means you need to be on the GB firmware, and stock everything else, not on ICS firmware.
That said, last part is correct: You would re-lock, flash an ICS RUU, unlock again, put recovery back on, and either flash a pre rooted stock ROM based on the leaks, or root the stock ROM yourself. Then you are on ICS firmware, ready for S-off.
antiseen said:
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
Click to expand...
Click to collapse
Leave the ROM. Do a nandroid backup. Re-lock and flash the RUU. You can restore the nandroid afterwards, just be sure to repatch the thing to new ICS firmware if you go that route. Check second listing in the Roll Up Sticky post in the Dev section.
antiseen said:
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
Click to expand...
Click to collapse
Unlimited.io has files for GB firmware and the first three out of four ICS leaks. Note this last leak, the fourth one, is compatible with the unlimited.io files for the third leak ("5/7 leak"). So little was changed, so you're safe going with that combo if you wish.
nosympathy said:
Also on a secondary note, you must have not had a thunderbolt when we first got s-off as getting s-off manually took about 30+ mins of constant cmd line use.
Click to expand...
Click to collapse
You're actually right. I didn't get my TB til June and I spent months reading how to get s-off and finally did it in...august or september, I forget. It was MUCH easier by then.
I was familiar with the original process(only by reading, but felt confident in doing it that way) but by the time I was done learning everything about it, revolutionary method came out and I did it that way.
I know that I can get s-off right now on his gingerbread firmware, my only question is what happens when ICS does get released and all the good ROMS start to come out? I want to get him on an AOSP rom when they come out. I feel like he'll be stuck on gingerbread firmware and when it comes time to flash any of the ICS roms, he'll be clueless. I could figure out how to do it if it required an extra step or two but explaining that to him might be a bit much. I'd rather him be geared for ICS (he has no intention of going back to gingerbread, ever).
Also, I was under the impression that flashing a RUU would make it S-on. So if I ever wanted to upgrade his firmware to ICS we would have to do the wire trick again to achieve s-off once more.
Anyway, Thanks a ton guys for your feedback already. Love this community and you're both a great help. Thanks for the clarification/instructions phantasm.
antiseen said:
I feel like he'll be stuck on gingerbread firmware and when it comes time to flash any of the ICS roms, he'll be clueless. I could figure out how to do it if it required an extra step or two but explaining that to him might be a bit much. I'd rather him be geared for ICS (he has no intention of going back to gingerbread, ever).
Click to expand...
Click to collapse
Hop through S-off with the GB files from unlimited.io. Keep the stock bootloader for now rather than flashing the JuopunutBear hboot when their program asks you. (Note S-off makes the bootloader "Locked" again, but the JB files are hacked so you can use them *as if* they are Unlocked status... handy and makes it simpler to get the phone ready for warranty exchanges again. But! We want to make sure we get ICS firmware and radios first...then slap on an *ICS* JB bootloader...)
antiseen said:
Also, I was under the impression that flashing a RUU would make it S-on. So if I ever wanted to upgrade his firmware to ICS we would have to do the wire trick again to achieve s-off once more.
Click to expand...
Click to collapse
Nope. Once you achieve S-off you keep S-off. The only thing that affects S-off is turning the flag back on manually yourself with some fastboot commands.
So now you will be S-off and with a Locked stock bootloader. Download the RUU from the 6/10 leak here, rename to just PH98IMG.zip and flash it in bootloader:
http://www.androidfilehost.com/main/-Support_Files-/RUU/Vigor/RUU_Vigor_3.14.605.10_PH98IMG.zip
Then grab "[ICS][2.25][JB][5-7]PH98IMG.zip" from SuperChilPil's repository. (Note the 6/10 leak and the 5/7 leak have the same bootloaders just like the first pair of leaks did, so this is fine to use.) Rename to PH98IMG.zip and flash in bootloader:
http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/
This will make you S-off with a JuopunutBear hacked hboot, running the latest firmware and ROM available. Choose a recovery to flash, preferably TWRP or AmonRa. ClockworkMod has charging issues, there is a fix floating around thanks to NilsP and his own source if you insist. You can then proceed to flash the ICS custom ROM of your choice.
TWRP:
http://forum.xda-developers.com/showthread.php?t=1613576
AmonRa:
http://forum.xda-developers.com/showthread.php?t=1339679
CWM (fixed):
http://forum.xda-developers.com/showthread.php?t=1722989
Edit: User zhp pilot claims this version of CWM is also not functioning properly at this time, see the thread. Proceed with caution on CWM.
And don't forget to make a splash screen now that you are S-off lol, stop blinding yourself with that white HTC screen:
http://forum.xda-developers.com/showthread.php?t=1615811
~~~
Other useful files for S-off if you don't have them on the PC... The latest HTC drivers (extracted from HTC Sync so you don't have to download all of that) and an adb/fastboot mini console:
https://rapidshare.com/files/1796700693/HTCDriver_3.0.0.021.exe
http://rapidlibrary.com/files/adb-fastboot-and-other-tools-zip_ulcmnmxxtci89on.html
antiseen said:
Anyway, Thanks a ton guys for your feedback already. Love this community and you're both a great help. Thanks for the clarification/instructions phantasm.
Click to expand...
Click to collapse
Nope, thanks you for asking.
antiseen said:
So, coming from a Thunderbolt...rooting and getting s-off on a rezound seems like rocket science in comparison. I've read and read for the past four weeks but I'm asking for your guys' help and clarification before I proceed.
Here is what has happened so far: My buddies Rezound is currently HTC dev unlocked with a custom ICS rom on it with S-on. I want to get him s-off so flashing roms and kernels will be a piece of cake without adding a bunch more steps. I figured out how to do it and understand the process myself pretty clearly but trying to explain it to my buddy...yeah, I might as well be trying to teach him another language.
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms). This already is getting complex to me. On my good old thunderbolt I just had to use revolutionary to get s-off then it was flash whatever I wanted, gingerbread or froyo and flash compatible radios.
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
Click to expand...
Click to collapse
In order to S-off the Rezound, you need to be HTCDEVunlocked, Rooted and on Stock Rom.

CDMA HBOOT 1.50 Boost Mobile

I have an HTC EVO 3D That I purchased yesterday, and It's been flashed to Boost Mobile (A company owned and operated by Sprint) Boost is a CDMA service. I am interested in rooting my device, but when I tried this method: http://forum.xda-developers.com/showthread.php?t=1218193 I was stopped because my HBOOT isn't supported. Baffled, I went searching the forums and found this:http://forum.xda-developers.com/showthread.php?t=1547695 unfortunately, I'm not sure if it's safe to proceed with this procedure, because I wasn't there when my phone was flashed, and I don't know if HTC Dev was used. Furthermore, I don;t know if I have S-On of S-OFF, because I didn't flash my phone. Also, it has come to my understanding that linux is required for that method of HBOOT downgrade. Is there any way I can avoid that? It's kind of a lot of trouble.
You can check if you're s-on or s-off by looking at the top of the hboot screen. Pull the batt, put it back in, hold vol down + power.
If you don't have s-off, the downgrade is easy, linux is easy. After the downgrade you have to use revolutionary.io to achieve s-off and it'll likely screw up your boost flash. I'll edit with a thread link for prepping to downgrade with a carrier flashed phone.
Edit... http://forum.xda-developers.com/showthread.php?t=1646815
wikdNoob said:
You can check if you're s-on or s-off by looking at the top of the hboot screen. Pull the batt, put it back in, hold vol down + power.
If you don't have s-off, the downgrade is easy, linux is easy. After the downgrade you have to use revolutionary.io to achieve s-off and it'll likely screw up your boost flash. I'll edit with a thread link for prepping to downgrade with a carrier flashed phone.
Click to expand...
Click to collapse
Hboot says I have S-ON. By following the steps in that link you'll give, will I be able to restore my flash without losing MMS and 3G, etc.?
I'm really not sure, I've never flashed a phone. If you don't mind me asking, why do you want s-off? It's nice to have because it makes flashing roms easier but its not required to flash roms, and if your not sure you can flash your phone back, its probably not worth the risk.
wikdNoob said:
I'm really not sure, I've never flashed a phone. If you don't mind me asking, why do you want s-off? It's nice to have because it makes flashing roms easier but its not required to flash roms, and if your not sure you can flash your phone back, its probably not worth the risk.
Click to expand...
Click to collapse
Well the whole idea is that i need to downgrade HBOOT in order to root, and I was under the impression that to downgrade Hboot i needed to have S-OFF.
No, you just need to unlock at htcdev. Then you can root, give me a sec and ill give you another link. Once you think you can flash your phone to boost, I suggest getting s-off. Just less issues with s-off flashing.
Edit... A lot of guides out there, check the roll up sticky thread. This one will probably work. http://forum.xda-developers.com/showthread.php?t=1239821
wikdNoob said:
No, you just need to unlock at htcdev. Then you can root, give me a sec and ill give you another link. Once you think you can flash your phone to boost, I suggest getting s-off. Just less issues with s-off flashing.
Edit... A lot of guides out there, check the roll up sticky thread. This one will probably work. http://forum.xda-developers.com/showthread.php?t=1239821
Click to expand...
Click to collapse
THank man, i wish i could click thanks a thousand times. I'll try this method and see what i get.
Any time.. btw, you might be able to do the wire trick to get s-off without messing up the flash. It's in the dev section, called something like junoputabear s-off. Ask in that thread, maybe someone will know.
wikdNoob said:
Any time.. btw, you might be able to do the wire trick to get s-off without messing up the flash. It's in the dev section, called something like junoputabear s-off. Ask in that thread, maybe someone will know.
Click to expand...
Click to collapse
I got root, and recovery but for some reason the fastboot method wher you extrtact the boot.img and use fastboot to load recovery doesn't work for ICS roms, they bootloop. I found a working Gingerbread rom and I like it. Only issue is i wanted an ICS app. Btw, which gapps should I flash for 2.3.4?
_xNova said:
I got root, and recovery but for some reason the fastboot method wher you extrtact the boot.img and use fastboot to load recovery doesn't work for ICS roms, they bootloop. I found a working Gingerbread rom and I like it. Only issue is i wanted an ICS app.
Click to expand...
Click to collapse
From what I remember, if you boot a recovery from fastboot (fastboot boot recovery.img), you wouldn't need to extract any boot image. When you boot a recovery from fastboot, you'll be able to write to the boot partition, so all you need to do is flash the rom and it should work. With that said, I've read a lot of times that flashing ics roms with s-on will cause bootloops. I've never seen that personally, I was s-off before ics came along.
Btw, which gapps should I flash for 2.3.4?
Click to expand...
Click to collapse
You probably know this but ill say it just incase. You only flash gapps on aosp roms. I think all the ics gapps say ics in the name, and most of the time gapps for any rom are linked in the same thread as the rom.
Look at your pm in a little bit. I'm gonna send you some stuff that'll help you figure out how to correctly flash a phone so that you can s-off without worry. I can't really post it here.
Edit... Sent

[Q] Accidentally started first part of update

So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"​
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"​
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound

[Q] Downgrading from 1.58 HBOOT to 1.4 and S-OFF.

Hey guys....
I feel really stupid about this entire thing but I've finally decided to post here because I'm getting desperate.
The guide in question (http://forum.xda-developers.com/showthread.php?t=1563342) is fairly striaghtforward. Except the links are really scattered, at least for me. I'm on HBOOT 1.58, and I've had numerous problems even getting to the point where my phone is relocked (it's currently HTC unlocked because I use an MIUI port ROM) successfully. I would bring my problems to that thread, but I don't have 10 posts, which is a questionable rule but w/e.
Anyway, here's my problem. First, I'll tell you what I've done so far, and the problem I've come across both times.
1. Place a "2.89 RUU" or whatever onto my SD card and call it PG86IMG. This is where most of my confusion is. OP of that thread hasn't yet covered what the difference between 2.17 and 2.89 is, but my understand is that 2.17 corresponds with HBOOT 1.5 and 2.89 to 1.58. Honestly, all these numbers piss me off when there's little to no documentation of what the hell they even mean. This file is about 448 MB and my understanding was that it was a stock RUU and would make it so I could access my phone while it was still locked, which you can't do with a 3rd party ROM like the one I usually use.
2. Lock my phone's bootloader. I just did fastboot oem lock in Windows and it rebooted to *** RELOCKED *** *** Security Warning ***. Apparently this is normal, and now I need to flash said RUU.
3. Flash the RUU. This took an EXTREMELY long time, and it went through Loading PG86IMG.zip.. then to some other stage that took much less time to complete. After that it just sits in the bootloader.
Here's my concern... I can't access my SD card. Why? Because I can't even get out of the bootloader or fastboot. All it does is sit here, and since I can't remove the update file PG86IMG.zip, if I try to enter recovery (which I'm sure won't work anyway) it will try to start loading that file again. I don't really know what step I missed here, but it's probably because I'm fairly clueless when it comes to this stuff, lol.
So, I did this once, and then I waited about 6 hours for HTCdev's site to stop crashing so I could unlock my phone again. Made it through a school day with my old ROM and stuff, deleted the update files so they wouldn't run again, etc. etc.
Now, I'm doing it again today with this new 2.89 RUU or whatever and the same exact problem is happening. So now I'm at a stage where my phone is entirely useless until HTCdev.com starts actually sending e-mails. I swear, these crashes on HTCdev's part could not be more untimely.
So basically, what am I doing wrong with relocking my phone? OP implies that I should be able to start my phone (not the bootloader, but actually start it) because they ask after you've supposedly re-locked the bootloader for you to move a new PG86IMG.zip file onto your SD card, which I'm unable to do because my phone can't get out of fastboot/bootloader screen. That's the next step, which is actually doing the downgrading.
And yes, I know that it's possible for HBOOT 1.58 because someone else already did it (last post in the thread).
At this point, I don't really care when I get it to work, man. This is proving to be such a gigantic pain in the ass just to install a new Jelly Bean ROM. I JUST WANT JELLY BEAN!
If anyone can send a noob in the right direction, that'd be great. I have all week and all weekend, but I've run out of time to waste on this for today. I guess most of what I need is to know what files I'm supposed to be downloading, because I have a feeling that's most of what I'm getting wrong.
I hope I've explained my problem well enough, and thanks a ton to anyone who just suffered through reading my essay and can offer help. I'll be sending this to OP of the guide as a PM so hopefully if none of you guys can help they can.
Thanks a ton everyone, I just want to get Jelly Bean on my phone and stop dealing with MIUI :laugh:
Update: Found this thread: http://forum.xda-developers.com/showthread.php?t=1495358. I believe this will probably help me out a lot! Wish I would've seen it sooner.
TL;DR: Need better explanation of how to relock 1.58 hboot bootloader with a stock rom, and where to find the rom.
Honestly, your post was tl;dr for me, but I think you would be best served to follow ramjet's guide to s-off. It's really the easiest and includes everything you need.
http://forum.xda-developers.com/showthread.php?t=1889438
coal686 said:
Honestly, your post was tl;dr for me, but I think you would be best served to follow ramjet's guide to s-off. It's really the easiest and includes everything you need.
http://forum.xda-developers.com/showthread.php?t=1889438
Click to expand...
Click to collapse
Lol. I'm not surprised. I tend to pour my heart out on forums when I get to the point of desperation.
Gonna be honest with you, zero interest in the wire tap method. Zero. Not trying it. Not even going to think about it. Sorry, I appreciate the idea but honestly screw that.
Logic33 said:
Lol. I'm not surprised. I tend to pour my heart out on forums when I get to the point of desperation.
Gonna be honest with you, zero interest in the wire tap method. Zero. Not trying it. Not even going to think about it. Sorry, I appreciate the idea but honestly screw that.
Click to expand...
Click to collapse
Then, honestly, you are EXTREMELY limited as to what you can do. S-Off is your best bet. Good Luck.
raptoro07 said:
Then, honestly, you are EXTREMELY limited as to what you can do. S-Off is your best bet. Good Luck.
Click to expand...
Click to collapse
I don't understand how that limits me at all. I just want to use the downgrade method to hboot 1.4 and s-off. I never had any intention of staying on hboot 1.5, and certainly not hboot 1.58.
Logic33 said:
I don't understand how that limits me at all. I just want to use the downgrade method to hboot 1.4 and s-off. I never had any intention of staying on hboot 1.5, and certainly not hboot 1.58.
Click to expand...
Click to collapse
From my understanding, the downgrade method works with hboot 1.58, but you have to brick your phone twice. But it really is the more challenging method so you may want to reconsider your stance on the wire trick. I've yet to hear of an unhappy customer who followed ramjet's guide.
coal686 said:
From my understanding, the downgrade method works with hboot 1.58, but you have to brick your phone twice. But it really is the more challenging method so you may want to reconsider your stance on the wire trick. I've yet to hear of an unhappy customer who followed ramjet's guide.
Click to expand...
Click to collapse
I'm not sure.
However, this thread can be closed because I *finally* got the RUU to work properly! I was doing things in the wrong order, and not using the .exe was a silly idea. It's much easier that way. Currently have stock ROM running on a locked 1.58 hboot. Now I can continue!
Logic33 said:
I'm not sure.
However, this thread can be closed because I *finally* got the RUU to work properly! I was doing things in the wrong order, and not using the .exe was a silly idea. It's much easier that way. Currently have stock ROM running on a locked 1.58 hboot. Now I can continue!
Click to expand...
Click to collapse
Good! :thumbup:
Keep posting questions, we'll do our best to help.
coal686 said:
Good! :thumbup:
Keep posting questions, we'll do our best to help.
Click to expand...
Click to collapse
LOLJK. I swear, at this point HTC must be trolling me. It's loaded up now. Thanks for trying to help everyone! I can't wait to get Jelly Bean on here soon!
Doubt this will help, but did you remove the PG86IMG.zip from your sd card? Also, did you run the ruu.exe while in bootloader (it will say fastboot usb in red). I'm sort of grasping at straws since the ruu usually works without issue when using the exe.
coal686 said:
Doubt this will help, but did you remove the PG86IMG.zip from your sd card? Also, did you run the ruu.exe while in bootloader (it will say fastboot usb in red). I'm sort of grasping at straws since the ruu usually works without issue when using the exe.
Click to expand...
Click to collapse
I have a feeling you didn't see my update It magically decided to work. Here comes double bricking action... this should be (un)fun D:
i am on hboot 1.58 and used HTC Unlock and wire trick to get s-off. i was about to flash a JB Rom but realized that it requires hboot to be lower than 1.58. so all i do is pick the first hboot 1.40 from Here, put it in the root of SD, boot up the phone in recovery and flash that PG86IMG.zip.
once its done ill swap the SD with another one which would have the ROM i want to install, then boot again in recovery and wipe Dalvik+cache, and then flash ROM?
am i doing it right?
thank you.
chubaan said:
i am on hboot 1.58 and used HTC Unlock and wire trick to get s-off. i was about to flash a JB Rom but realized that it requires hboot to be lower than 1.58. so all i do is pick the first hboot 1.40 from Here, put it in the root of SD, boot up the phone in recovery and flash that PG86IMG.zip.
once its done ill swap the SD with another one which would have the ROM i want to install, then boot again in recovery and wipe Dalvik+cache, and then flash ROM?
am i doing it right?
thank you.
Click to expand...
Click to collapse
No, do it from the bootloader
Sent from my skz_tenderloin using xda premium
fdavila17 said:
No, do it from the bootloader
Sent from my skz_tenderloin using xda premium
Click to expand...
Click to collapse
I have the exact situation with my wife's phone? I want to install Pacman on her phone which is still stock. Is all I have to do what chubaan said?
ruckstande said:
I have the exact situation with my wife's phone? I want to install Pacman on her phone which is still stock. Is all I have to do what chubaan said?
Click to expand...
Click to collapse
Just download the hboot you want, 1.50 or below to get PACMAN to.boot, rename it as PG86IMG.zip place it on the root of your sd card, go to.the bootloader and select yes to apply update , and your done
Sent from my PG86100 using xda premium
Thank you.. that's what I did. And after you're done make sure to wipe dalvik and cache from recovery, at least in my case I had to. And then flash the rom. And that's it..
Sent from my PG86100 using XDA Premium App

Categories

Resources