Hey folks..so I want to start flashing kernels and yes I know I probably should have gone s-off way sooner but I want to do it now. I've been rooting and romming my phones for a while but this whole s-off procedure continued to scare the crap out of me. But..I don't want to limit my choices when it comes to roms and kernels so I guess I'll do it anyway.
However, I am currently running RUU 4.03.605.2 with Vigor360 1.1 s modified kernel.
Can I still go s-off even though I am now running the global leak (or is it now impossible) and if so, can someone point me in the right direction?
Thank you kind gents n ladies!
I've heard of several people being successful on 4.03.605.2 with the 3.14.605.5 ControlBear version.
Only other advice I can offer is don't give up, try different wires if you're having trouble, and pay attention to the troubleshooting page if you decide you want back out and try again later. I've S-OFF'ed three Rezounds. The first took 3 days, the second 2 minutes, and the third 30 minutes.
dplane said:
Hey folks..so I want to start flashing kernels and yes I know I probably should have gone s-off way sooner but I want to do it now. I've been rooting and romming my phones for a while but this whole s-off procedure continued to scare the crap out of me. But..I don't want to limit my choices when it comes to roms and kernels so I guess I'll do it anyway.
However, I am currently running RUU 4.03.605.2 with Vigor360 1.1 s modified kernel.
Can I still go s-off even though I am now running the global leak (or is it now impossible) and if so, can someone point me in the right direction?
Thank you kind gents n ladies!
Click to expand...
Click to collapse
i did s-off with viper's rom and the .5. i was on global too, don't let it scare you or you will not get it. i couldn't get the timing for the life of me. first two hours was a hassle, then i had to get my other battery(thought i bricked my phone) then i relized that they had a metrnome with the correct timing and it worked the first time. but use a different memory card. all of these things can be found under the s-off instructions.:good:
its really easy man you can do it. i reccemend using speaker wire as its more pliable than a paperclip.. if you need help i can walk you thru it on gtalk. just pm me for me gtalk. otherwise. goodluck and yes the 3.14.605.5 ControlBear version is the correct one just lock your bootloader, run the full ruu agan( 4.03.605.2), flash amonRA, then flash this in recovery (https://docs.google.com/file/d/0B0ZJtM40GdJ0MEpGeG1ZWi0yNDA/edit) to gain root on stock global, download root checker from the app store to be sure you got root before you begin. then boot phone and check usb debugging, connect your phone to the comp(within the stock rom), start control bear.. make sure to back up EVERYTHING as it could all get wiped. (internal sd, external sd, and your nandroid if you so choose) i reccemend using a spare sd card if you have one.. ive only done my phone but it took me all of 2 trys.. i got weird errors a couple times (other than "error: still sober" got that once) if you do just run control bear again
Thanks for the responses and moral support folks!
Collin, I may have to hit you up for that assistance soon, I'd rather be safe then sorry so I might feel better if I have someone to "hold my hand"
May not get around to it til Sat afternoon or Sunday though.
famouscollin said:
its really easy man you can do it. i reccemend using speaker wire as its more pliable than a paperclip.. if you need help i can walk you thru it on gtalk. just pm me for me gtalk. otherwise. goodluck and yes the 3.14.605.5 ControlBear version is the correct one just lock your bootloader, run the full ruu agan( 4.03.605.2), flash amonRA, then flash this in recovery (https://docs.google.com/file/d/0B0ZJtM40GdJ0MEpGeG1ZWi0yNDA/edit) to gain root on stock global, download root checker from the app store to be sure you got root before you begin. then boot phone and check usb debugging, connect your phone to the comp(within the stock rom), start control bear.. make sure to back up EVERYTHING as it could all get wiped. (internal sd, external sd, and your nandroid if you so choose) i reccemend using a spare sd card if you have one.. ive only done my phone but it took me all of 2 trys.. i got weird errors a couple times (other than "error: still sober" got that once) if you do just run control bear again
Click to expand...
Click to collapse
I'm working with the same situation as the OP. You posted a link to a second recovery to flash after Amon Ra, I've tried that link and it forces me to request access. Which recovery is it and is there another link or are you able to give me access to that one?
Hey guys.
I am a complete newb with most this stuff.
I am not sure how I look at RUU I have. I will say that my phone was pretty much stock through the official ICS release.
Currently I have CM9 flashed as my rom.
Is there anyway I can S-OFF my phone?
Sax1031 said:
Hey guys.
I am a complete newb with most this stuff.
I am not sure how I look at RUU I have. I will say that my phone was pretty much stock through the official ICS release.
Currently I have CM9 flashed as my rom.
Is there anyway I can S-OFF my phone?
Click to expand...
Click to collapse
If you haven't already, I would say start by checking out unlimited.io They have all the basic details about how to achieve S-OFF. Without knowing more specifics about your setup it would be hard someone to give a more specific answer.
neowisdom1031 said:
If you haven't already, I would say start by checking out unlimited.io They have all the basic details about how to achieve S-OFF. Without knowing more specifics about your setup it would be hard someone to give a more specific answer.
Click to expand...
Click to collapse
Yea I have went there.
I have the program downloaded. I am on Gray's CM9 rom.
Followed all the instructions. When the program runs it goes like this:
Starting up....
Connecting to device....
Searching device.....
Found device......
Backing up.....
Permission denied.....
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.
like I said my phone was stock till the official ICS update released. After that I unlocked the boot loader and just recently flashed my first rom, through Amon Ra.
If I could kindly ask you what info you need, and possibly how to access the info, to help me out. Do I need to flash a stock rom back?
---------- Post added at 08:27 PM ---------- Previous post was at 07:29 PM ----------
I hope to god my hboot was stock. As I am running a previous RUU.
Hopefully once I do this, I will be able to S-OFF.
Sax1031 said:
Yea I have went there.
I have the program downloaded. I am on Gray's CM9 rom.
Followed all the instructions. When the program runs it goes like this:
Starting up....
Connecting to device....
Searching device.....
Found device......
Backing up.....
Permission denied.....
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.
like I said my phone was stock till the official ICS update released. After that I unlocked the boot loader and just recently flashed my first rom, through Amon Ra.
If I could kindly ask you what info you need, and possibly how to access the info, to help me out. Do I need to flash a stock rom back?
---------- Post added at 08:27 PM ---------- Previous post was at 07:29 PM ----------
I hope to god my hboot was stock. As I am running a previous RUU.
Hopefully once I do this, I will be able to S-OFF.
Click to expand...
Click to collapse
If you're able to flash back to stock that would be the best place to start for S-OFF
neowisdom1031 said:
If you're able to flash back to stock that would be the best place to start for S-OFF
Click to expand...
Click to collapse
I flashed back to the first ICS RUU.
I think I know why it said permission denied. Because I didn't have actual root access.
At the point of trying the wire trick.
Edit: Achieved S-OFF. Thanks so much guys. Going from 3 days ago of flashing my first rom. To having to relock the device, run the first ICS Ruu, then doing the wire trick. Hell of a learning curve on these things. Thanks everyone for all the help.
Just a quick update. I was able to achieve S-Off while using this specific RUU. It took a few time flashing the RUU and a rooted rom to finally get it but it is possible with this RUU.
neowisdom1031 said:
Just a quick update. I was able to achieve S-Off while using this specific RUU. It took a few time flashing the RUU and a rooted rom to finally get it but it is possible with this RUU.
Click to expand...
Click to collapse
Fwiw I also was able to go s-off using this ruu and flashing supersu from a temporary amon ra. Not as tough as it thought.
Sent from my ADR6425LVW using xda app-developers app
.
Did you put the Juopunutbear executable and files into the same folder
that Android fastboot, adb, and other files are located?
michaelbsheldon said:
Did you put the Juopunutbear executable and files into the same folder
that Android fastboot, adb, and other files are located?
Click to expand...
Click to collapse
It shouldn't matter. ControlBear has its own versions of everything it needs.
Sent from my HTC Rezound using Tapatalk 2
So this is what i've done and its failing with the error: "Secondary backup FAILED!!"
-I reset everything by using the RUU 4.03.605.2.
-I then set the debugging mode, unlocked the bootloader
-Put AmonRa3.15 as my recovery
-Flashed the CWM SuperSU.
-Confirmed root access by using TitaniumBackup.
-Started the ControlBearRelease_vigor_ICS_3.14.605.5 for the ICS leak process.
-Then I get the fun error Secondary backup FAILED!!.
I'm using the latest version of JuopunutBear 0.4. Help?
-------------update---------------
So I re-flashed the full RUU and went through all the steps and still same outcome. "Secondary backup Failed!". I read that only version .1 may work if this error occurs?
=-\
Izeltokatl said:
So this is what i've done and its failing with the error: "Secondary backup FAILED!!"
-I reset everything by using the RUU 4.03.605.2.
-I then set the debugging mode, unlocked the bootloader
-Put AmonRa3.15 as my recovery
-Flashed the CWM SuperSU.
-Confirmed root access by using TitaniumBackup.
-Started the ControlBearRelease_vigor_ICS_3.14.605.5 for the ICS leak process.
-Then I get the fun error Secondary backup FAILED!!.
I'm using the latest version of JuopunutBear 0.4. Help?
-------------update---------------
So I re-flashed the full RUU and went through all the steps and still same outcome. "Secondary backup Failed!". I read that only version .1 may work if this error occurs?
=-\
Click to expand...
Click to collapse
i s-offed with the global ruu and and this version of control bear https://docs.google.com/file/d/0B0ZJtM40GdJ0SmVBbm40anJpRTg/edit ia got a few wierd errors but just started it up again and all went well..also make sure you have htc sync uninstalled from your computer
famouscollin said:
i s-offed with the global ruu and and this version of control bear https://docs.google.com/file/d/0B0ZJtM40GdJ0SmVBbm40anJpRTg/edit ia got a few wierd errors but just started it up again and all went well..also make sure you have htc sync uninstalled from your computer
Click to expand...
Click to collapse
Ya that's the exact same version I have, not really sure what to do? I re-did everything back to RUU again to no avail.
Izeltokatl said:
Ya that's the exact same version I have, not really sure what to do? I re-did everything back to RUU again to no avail.
Click to expand...
Click to collapse
you can try backing up your sd cards and partition them before you start the control bear process, and your sure you have root access correct? via rootchecker, tatanium backup or somethin gand usb degugging checked? if your still having issues look for apophis' thread named "so you need assistance, WE ARE HERE TO HELP" post in that thread im sure he can help you walk thru it..
When I bought my rezound used it had a constant boot loop issue. That's why I got it fairly cheap. I immediayly ran the global ruu hoping it would boot. It still boot looped. I was able to unlock, flash recovery and install newts xxx. I have tried to boot other romsand they give me issues too. Is there any way I can s off in my current configuration because I am pretty confident another ruu from my sd card just won't boot. Has anyone had success being on a custom Rom w global firmware hboot 2.27?
Related
Hey Guys, fairly new to posting here, but was hoping this could help some of you.
#####################################################################
# If you are running a stock ROM you can ignore this, there are better threads for you out there.
#####################################################################
When the OTA came out I knew I wanted the new radios, but have had nothing but problems putting them on.
I have spent the last couple of hours reading and generally just being frustrated. I eventually got to the conclusion I wanted and I thought having all of this OTA update junk in one place might be helpful for others.
History:
- I was running Ineffabilis 12/29. (great ROM)
- Went to Senseless ICS (great ROM, bluetooth problems, persistent with all current ICS's, was insurmountable for me)
- Went to Team BAMF Rezound Cubed ROM, used this ROM to get out of the ICS trap because it flashes a kernel after it flashes the ROM.
Coming From ICS, Team BAMF Cubed or the New clean GB rom:
If you have installed a ROM that updated the Main Ver (all ICS roms or Team BAMF rom, or the new clean GB rom, then you will need to reset the main ver to 1.00.000.00 to run the RUU.
To do that go to this thread: http://forum.xda-developers.com/showpost.php?p=21875151&postcount=1
Next:
Once you have your main ver set to 1.00.000.00. You will need to follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1466474 (summary below)
1) You will need to reflash the stock recovery (a great way to do that is using Cleanflash, get it here: http://www.scottsroms.com/downloads.php?do=file&id=57) -- You can find the stock flash recovery image in the thread above.
2) Reboot to Fastboot and run "fastboot oem lock" from your DOS command line. This will reboot your phone back into fastboot/hboot.
3) Run the RUU.exe from Windows using the download from scottsroms here: http://www.scottsroms.com/downloads.php?do=cat&id=11
4) Go through and install the OTA updates. Go to settings, and software update.
5) Go back to HTCDev.com and unlock the bootloader as you have in the past.
6) Flash a new recovery.img, such as amonRa, (fastboot flash recovery nameofrecovery.img)
7) The world is now yours! Install ICS if you would like or any other ROM or install su if you prefer.
Credits:
!! mrbracht for the mainver fixed (saved my bacon)
!! FlyHalf205 for the rest of this
!! scrosler for generally being awesome and all the great tool's, roms, ruu, etc.
I've downloaded the recovery and unziped it. Then I moved it to fastboot but when I type fastboot flash recovery recovery_sign.img I get a error cannot load.
FlagAZ said:
I've downloaded the recovery and unziped it. Then I moved it to fastboot but when I type fastboot flash recovery recovery_sign.img I get a error cannot load.
Click to expand...
Click to collapse
The stock recovery? What mainversion are you?
I checked today it was something like 1.0.6. I know that it was not updated.
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
I've been trying all day with no like...... I'm lost with all the post about how to do this (flash this, unload this, do it this way)......
okay so what is the text of the error?
i keep getting hung up in the RUU... my MainVer is the same version as the RUU, or was, but now i can't reboot my phone, just tuck in bootloader/fastboot, and with the stock recovery lol...
my ADB won't open either
---------- Post added at 09:26 PM ---------- Previous post was at 08:39 PM ----------
platinumrims said:
i keep getting hung up in the RUU... my MainVer is the same version as the RUU, or was, but now i can't reboot my phone, just tuck in bootloader/fastboot, and with the stock recovery lol...
my ADB won't open either
Click to expand...
Click to collapse
pah, gave up. unlocked reflashed amon ra, and restored my nandroid... :'(
Maybe this reply is too late. Sorry...
But, was it locked and having the stock recovery when you were trying the RUU? Also you run the RUU from windows while the phone is in hboot mode.
pngwyn said:
Also you run the RUU from windows while the phone is in hboot mode.
Click to expand...
Click to collapse
Yes, that is how I always do it.
Wow. I'm impressed with the details you provided. I was debating flashing ICS and had questions about going back. You answered all my questions. Thanks for posting your findings. I really appreciate it.
Updated
So by resetting the mainver, will I be able to flash ICS then say Ineffabilis 12/29 without worrying about updating any kernels? Also, just to confirm, once I flash ICS, I'd have to reset the mainver before going back to Ineffabilis 12/29.
Sent from my ADR6425LVW using xda premium
I go back and forth between ics and gb roms without any issues, never got a mainver error.
Sent from my HTC Rezound using XDA Premium
raider3bravo said:
Wow. I'm impressed with the details you provided. I was debating flashing ICS and had questions about going back. You answered all my questions. Thanks for posting your findings. I really appreciate it.
Updated
So by resetting the mainver, will I be able to flash ICS then say Ineffabilis 12/29 without worrying about updating any kernels? Also, just to confirm, once I flash ICS, I'd have to reset the mainver before going back to Ineffabilis 12/29.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Glad you found the post useful.
As far as I understand, you won't have any issues switching between GB and ICS and back to GB (other than needing to make sure you are running a compatible kernel). If you go back to ineffabilis after ICS you will need to find a way to get the kernel on the system (probably through fastboot or adb) and then flash ineffabilis, for me it was easiest to go back to GB using team bamf because it included the kernel and then you could flash ineffabilis and all should have been well.
The real reason to worry about main ver (as far as I know) is so that you can flash the ruu and return to stock. I guess there are also some other problems with kernels and them checking what mainver you have before flashing, but I am not familiar with those issues.
The nice thing is with the mainver hack above you won't ever have to worry by resetting the mainver, pushing the stock recovery, relocking and then flashing using the RUU utility it is possible to get completely back to factory condition.
Best Regards!
pngwyn said:
Maybe this reply is too late. Sorry...
But, was it locked and having the stock recovery when you were trying the RUU? Also you run the RUU from windows while the phone is in hboot mode.
Click to expand...
Click to collapse
I was using the ruu on Windows and had my phone in Hboot.
I relocked it, via an app someone made here on the forums because I couldn't get ADB to run at all. It would flash up in a window and close immediately. And I re installed SDK 10 Times and couldn't ever get adb to re instal or update.
Also had the stock recovery flashed...
When I used the app to relock the phone I had a "security warning" message under the relock status in fastboot, dunno if that's normal.
Then when trying to run the ruu I got a 155 error, but it wasn't the same one as listed in the report, or it didn't say the same thing at least. Then I kept getting battery lower than 30% errors so it wouldn't let me redo it after the 3rd try. Even though my phone was at like 85% when I got frustrated and decided booted it back up...
I'd like to try it again some other time but idk what else to do to get my ADB functioning ATM so I can check or change my MainVer (which was the same version as the ruu, also dunno if that mattered, I just though as long as it wasn't higher the ruu would work)
Any info would be mucho appreciated lol. :banghead:
platinumrims said:
I was using the ruu on Windows and had my phone in Hboot.
I relocked it, via an app someone made here on the forums because I couldn't get ADB to run at all. It would flash up in a window and close immediately. And I re installed SDK 10 Times and couldn't ever get adb to re instal or update.
Also had the stock recovery flashed...
When I used the app to relock the phone I had a "security warning" message under the relock status in fastboot, dunno if that's normal.
Then when trying to run the ruu I got a 155 error, but it wasn't the same one as listed in the report, or it didn't say the same thing at least. Then I kept getting battery lower than 30% errors so it wouldn't let me redo it after the 3rd try. Even though my phone was at like 85% when I got frustrated and decided booted it back up...
I'd like to try it again some other time but idk what else to do to get my ADB functioning ATM so I can check or change my MainVer (which was the same version as the ruu, also dunno if that mattered, I just though as long as it wasn't higher the ruu would work)
Any info would be mucho appreciated lol. :banghead:
Click to expand...
Click to collapse
I am not familiar with anything you experienced.
You shouldn't need adb for anything you are trying to do. It doesn't sound like you are getting the mainver error (if you were you would be getting the error after trying to go through the RUU wizard and it actually tells you your mainver is 2.00.###.## for whatever it is. If you are sure you haven't done anything to update your main ver than chances are your mainver is not the problem.
I am just guessing but this is what I am imagining could be solutions.
- Use 'fastboot oem lock' from the hboot prompt when in fastboot usb mode (ie your usb cable is plugged in.
- Make sure you are using the .exe version of the RUU. If you are not using the .exe version then that definitely could be the problem, if you are using the .exe version then perhaps the file got corrupted when you downloaded it. Try deleting and redownloading.
- You have said that you are running the stock recovery which sounds correct. But make sure you aren't using the stock recovery from one of your own backups use the one that is provided in the thread from my link above.
... In conclusion you shouldn't need ADB if your main version is the stock mainver. Flash the stock recovery first of all, then use the command 'fastboot oem lock' it will tell you it is locked it will reboot the phone (I think it even gives you an error in the dos prompt.) But then when it reboots it reboots to hboot and will say relocked at the top in the bright purple. Then be sure to run the RUU version .exe. If the RUU you have still isn't working download another (this is the one that worked for me: http://www.scottsroms.com/downloads.php?do=file&id=37)
Sorry wish I could be more helpful but I don't have relevant experience for what is happening for you but I do know what worked for me and I do believe it will work for you.
Good luck!
I doubt seriously that its my mainver. I'm wondering if it had something to do with that,weird security thing I had showing up in my fastboot. I will try it again maybe tomorrow night or something. Thank for your help
THANKS
I had to do the main ver fix and everything, great guide made everything super easy
Hey guys,
So with the recent hboot downgrade option, it seems like it's finally time to root my virgin 3VO, but I need a little help at least with some big picture stuff.
I know that with the HTC unlock, the device is wiped. By doing the hboot downgrade that doesn't seem to be the case. Is it possible to downgrade hboot, get s-off, unlock and then do a nandroid backup of my current phone setup?
In the downgrade instructions, you are supposed to run revolutionary in the final steps, but I'm fuzzy on what this tool does versus some of the other tools like TWRP2 (htcdumblock?) or HTCSupertoolv3. Could somebody give me a quick rundown on these, and if I will need them?
In the hboot downgrade video I watched, the device has a 2.08 RUU on it, while I have the latest OTA 2.17. Will that cause any issues? I've downloaded both the hbootdowngrade toolkit, as well as RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.exe
I should probably mention my intentions too... I'd like to get a stock backup to revert to (my current config if possible), then try out some ROMs (maybe MeanROM to start) and chad's latest 2.17 kernel.
MUCH appreciated!
:: edit :: figured out
Any suggestions would be greatly appreciated!
:: edit :: figured out
Okay, so despite being stuck in a boot loop, apparently the tacoroot temp root was successful. I was able to push the other commands to get mainver: 1.10.651.2
My problem is, that because it wont actually boot, I can't back up my apps with Titanium. Do I have any other options?
ccs86 said:
Okay, so despite being stuck in a boot loop, apparently the tacoroot temp root was successful. I was able to push the other commands to get mainver: 1.10.651.2
My problem is, that because it wont actually boot, I can't back up my apps with Titanium. Do I have any other options?
Click to expand...
Click to collapse
I haven't gone thru this whole downgrade process, I've only done step 3 in order to unbrick my phone from something unrelated, but I know enough to tell you that you're already past the point that you can backup your apps/ROM. You need to keep going thru the instructions for downgrading your hboot til you're completely done and your phone's booted up. If you decided to check the box when you first set your phone up for "keeping this device backed up with Google" (paraphrasing here), then once you set up ANY sense ROM, as long as you have that option enabled as you go thru the setup process, once you click on play store/market, your phone will automatically start downloading all the apps you previously had on your phone.
---------- Post added at 10:45 PM ---------- Previous post was at 10:42 PM ----------
ccs86 said:
Hey guys,
So with the recent hboot downgrade option, it seems like it's finally time to root my virgin 3VO, but I need a little help at least with some big picture stuff.
I know that with the HTC unlock, the device is wiped. By doing the hboot downgrade that doesn't seem to be the case. Is it possible to downgrade hboot, get s-off, unlock and then do a nandroid backup of my current phone setup?
In the downgrade instructions, you are supposed to run revolutionary in the final steps, but I'm fuzzy on what this tool does versus some of the other tools like TWRP2 (htcdumblock?) or HTCSupertoolv3. Could somebody give me a quick rundown on these, and if I will need them?
In the hboot downgrade video I watched, the device has a 2.08 RUU on it, while I have the latest OTA 2.17. Will that cause any issues? I've downloaded both the hbootdowngrade toolkit, as well as RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.exe
I should probably mention my intentions too... I'd like to get a stock backup to revert to (my current config if possible), then try out some ROMs (maybe MeanROM to start) and chad's latest 2.17 kernel.
MUCH appreciated!
Click to expand...
Click to collapse
you have a lot of questions. I'm going out for a bit but if you don't have answers by the time I get back, I can help you with at least a few more of your questions. Also, I'd recommend not posting 5x in a row next time, be patient, someone will eventually help you
edit: can't count...
ccs86 said:
Hey guys,
So with the recent hboot downgrade option, it seems like it's finally time to root my virgin 3VO, but I need a little help at least with some big picture stuff.
I know that with the HTC unlock, the device is wiped. By doing the hboot downgrade that doesn't seem to be the case. Is it possible to downgrade hboot, get s-off, unlock and then do a nandroid backup of my current phone setup?
In the downgrade instructions, you are supposed to run revolutionary in the final steps, but I'm fuzzy on what this tool does versus some of the other tools like TWRP2 (htcdumblock?) or HTCSupertoolv3. Could somebody give me a quick rundown on these, and if I will need them?
In the hboot downgrade video I watched, the device has a 2.08 RUU on it, while I have the latest OTA 2.17. Will that cause any issues? I've downloaded both the hbootdowngrade toolkit, as well as RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.exe
I should probably mention my intentions too... I'd like to get a stock backup to revert to (my current config if possible), then try out some ROMs (maybe MeanROM to start) and chad's latest 2.17 kernel.
MUCH appreciated!
Click to expand...
Click to collapse
I'll try to answer some of your questions, but I'm no pro.
I made a backup right before I downgraded so I didn't lose any info, but it sounds like you're past that point.
Revolutionary will get you "s-off", its the only thing that will give you that, that's the point of downgrading. Dumlock is for hboot 1.5 users. Once you downgrade, you won't need it.
2.17 will be fine, that's what I was on.
At the point you're at, either you can turn back now and run the 2.08, 2.17 ruu.exe from hboot, or if you're not scared, then its time for you to brick.
I suggest getting all your terminals to the "waiting for device" state before you brick. Just so you know that won't be an issue because once you brick there's no turning back.
w0rdOo said:
I haven't gone thru this whole downgrade process, I've only done step 3 in order to unbrick my phone from something unrelated, but I know enough to tell you that you're already past the point that you can backup your apps/ROM. You need to keep going thru the instructions for downgrading your hboot til you're completely done and your phone's booted up. If you decided to check the box when you first set your phone up for "keeping this device backed up with Google" (paraphrasing here), then once you set up ANY sense ROM, as long as you have that option enabled as you go thru the setup process, once you click on play store/market, your phone will automatically start downloading all the apps you previously had on your phone.
---------- Post added at 10:45 PM ---------- Previous post was at 10:42 PM ----------
you have a lot of questions. I'm going out for a bit but if you don't have answers by the time I get back, I can help you with at least a few more of your questions. Also, I'd recommend not posting 5x in a row next time, be patient, someone will eventually help you
edit: can't count...
Click to expand...
Click to collapse
Yeah, part of that was trying to get my 10 posts so I could post in the dev forum
Sent from my PG86100 using Tapatalk 2 Beta-4
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
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
BrahManty said:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
Click to expand...
Click to collapse
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
acejavelin said:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
Click to expand...
Click to collapse
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
BrahManty said:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
Click to expand...
Click to collapse
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
acejavelin said:
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
Click to expand...
Click to collapse
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
acejavelin said:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
Click to expand...
Click to collapse
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
BrahManty said:
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
Click to expand...
Click to collapse
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
acejavelin said:
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
Click to expand...
Click to collapse
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
BrahManty said:
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
Click to expand...
Click to collapse
Cool, glad you got it working.
That firmware is actually pretty decent and rock solid stable, you shouldn't have any more software related issues... Plus you can root/ROM like normal from that version, the radios may be slightler lower than most recommended versions, but they should work fine. If you do decide to go the ROM route again, I would suggest going S-OFF before starting, it will just make it easier in the long run.
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
*** TAMPERED ***
*** LOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
JoeKamel said:
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
Click to expand...
Click to collapse
You should be able to just boot into twrp and flash a rom
Sent from my ADR6425LVW using xda premium
izzaeroth said:
You should be able to just boot into twrp and flash a rom
Click to expand...
Click to collapse
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
JoeKamel said:
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
Click to expand...
Click to collapse
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Sent from my ADR6425LVW using xda premium
izzaeroth said:
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Click to expand...
Click to collapse
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
JoeKamel said:
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
Click to expand...
Click to collapse
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Click to expand...
Click to collapse
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
JoeKamel said:
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
Click to expand...
Click to collapse
Recovery = twrp
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
S-off is S-off... installing a RUU wont change that, it may set you back to 'Locked", but you are S-off so it doesn't matter, you can stay locked&s-off and its no different than unlocked/S-off.
If you are going back to stock and are S-off I would use the Global Mode Leak (4.3.605.2) available on AndroidPolice and flash in Hboot... rename file to PH98IMG.zip and place in root of SD card (how it gets there is a irrelevant) then reboot into Hboot, confirm and wait.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
I created a similar thread the other day but it got so overwhelming and it was just confusing me more so I deleted it. I'm starting a fresh one so I can maybe explain myself better, not confuse anyone else and get better answers.
I just got a replacement Rezound in the mail today. My phone is currently on 4.05.605.14 710RD, LOCKED, HBOOT is 2.28.0000 & radios are 2.23.10.0123r/2.23.10.0124r.
That last time I was able to S-OFF I used the wire method and ControlBear for Windows. I went to the website Unlimited.IO and they no longer support Windows so I have no idea on how to S-OFF since I did it months ago. However, I did find ControlBear v0.1 for Windows here on the forums: http://forum.xda-developers.com/showpost.php?p=27764982&postcount=2079 My first question is will this version work for me? If you download it and open it you can see the zips contents. I wasn't sure If had to RUU back down to an earlier version for it to work? And last time I ended up being on a Juopunutbear HBOOT somehow.
So basically I want to be able to get back onto CyanogenMod 10.1 properly this time. I haven't done anything to my phone yet, still unrooted, on stock, etc.. I know my first step is too unlock it using the htcdev website but from there I'm confused, I can't remember the steps its been too long.
I need someone to please explain how I can get back to CM 10.1 and remain on the latest firmware/drivers/hboot etc. So I need help with rooting, s-off, how to get TWRP recovery back on, which to do first, etc.
I appreciate the help and I'll make sure I save this in case it ever happens again. Also, my apologies again for the previous thread, it was just too much going on, I just need simple steps.
Am not positive but i think u will need Ubuntu as that one wont work on the new 2.28 hboot. So lets start with u installing ubuntu on a drive or live cd
Sent from my Infected Rezound using xda app-developers app
xanda143 said:
Am not positive but i think u will need Ubuntu as that one wont work on the new 2.28 hboot. So lets start with u installing ubuntu on a drive or live cd
Sent from my Infected Rezound using xda app-developers app
Click to expand...
Click to collapse
ControlBear 0.1 worked for me on Windows, took a few tries but it finally pulled through. These where my steps:
1. unlocked
2. flashed recovery
3. flashed [ROM] OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13
4. flashed boot.img from the rom
5. did wired trick with CB 0.1
so i think im good now? just have a couple questions.
- my phone now says tampered/locked/s-off? last time i s-off it didnt have that tamper there, is this normal?
- im still on hboot 2.28.0000 & radio 2.23.10.0123r/2.23.10.0124r. is this latest hboot/firmware/radio?
- im still on that rom that i linked above. im good to go ahead and flash and jb rom now?
- last, is there anything else i need to do with my phone? fixing the mainver, etc.
xXezmacXx said:
- my phone now says tampered/locked/s-off? last time i s-off it didnt have that tamper there, is this normal?
- im still on hboot 2.28.0000 & radio 2.23.10.0123r/2.23.10.0124r. is this latest hboot/firmware/radio?
Click to expand...
Click to collapse
That's normal if you're still using an unpatched hboot. If you will still use some fastboot commands (I use fastboot boot zImage/fastboot flash zimage zImage alot) then look into vynlfreak's 2.27 patched hboot. DO NOT UNLOCK flash patched hboot instead.
xXezmacXx said:
- im still on that rom that i linked above. im good to go ahead and flash and jb rom now?
- last, is there anything else i need to do with my phone? fixing the mainver, etc.
Click to expand...
Click to collapse
Flash your rom and don't worry about mainver.
Just wanted to thank you two. I have always been hesitant about s-offing my phone. But seeing it here in a few simple steps gave me the courage to finally pull the trigger. I know I am super late to the S-Off party, but am thrilled to finally have arrived!