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
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?
Hey guys,
I was running the latest Viper rom. Every great once in a while the phone would just turn off. I could get it back fine and this happened about 5-6 times. Today the phone got stuck in a boot loop. I figured something went wrong.
I attempted to restore the phone to stock using the RUU thread found here: http://forum.xda-developers.com/showthread.php?t=2152993
I restored it once fine, said it was good. Phone only rebooted over and over. The HTC logo came up 3-4 times then screen went blank. So I flashed again. Same thing, nothing.
Now I had been playing around and think I updated my radio. Now the RUU from that thread above says it cannot upgrade my phone. I can get to fastbook and lock and unlock the bootloader. I did install latest TWRP but it never enters recovery. I had hoped to just install a basic rom from the 2.04 update and be done. But I cannot get into recovery.
I'm stuck and don't know what else to do. Is there and RUU file like the one above for the new 2.04?
I still think something else is wrong with this phone. Somehow doubt VZW will take it back and exchange.
S-ON
Phone displays HBOOT-1.33.0001
RADIO-1.01.01.0110
Any ideas what I can do next please?
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Tersanyus said:
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Click to expand...
Click to collapse
Did you take the verizon update as you mentioned 2.04? If you did you will have to wait a bit yet to root again. Your only option would be stock verizon. Their software update basically closed the previously open window. If not...You HAVE updated radio per the # you posted, not sure if that really matters with regard to recovery. It seems like you have compounded many issues. I would try relocking bootloader and flash stock RUU again. Try to get back to stock verizon. If that's a no go, would try reflashing old radio and try stock ruu. How are you getting to try bootloader/recovery, turning on phone holding down vol button? Last ditch if it's says s-on and locked, I think you would be ok to try for a new phone.
I did not take the OTA from Verizon. I never got any prompt for an update. I did the updates for Viper that turned I think just turned that off.
Getting to bootloader is fine. I can lock it and unlock it fine. I know the RUU only loads if locked. I know recovery can only be installed if unlocked I believe. And yes I do that from vol down plus power button.
If I use newest TWRP recovery just gives a whole bunch of colored lines. If I try 2.4.0.0 I can see TWRP come up briefly then the phone reboots again.
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Tersanyus said:
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Click to expand...
Click to collapse
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
---------- Post added at 10:39 AM ---------- Previous post was at 09:48 AM ----------
rootntootn said:
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
Click to expand...
Click to collapse
Can you get to fastboot? adb can communicate with the phone? Says in red fastboot usb? Also how are you doing RUU, assuming your using executable from your pc? Forgot to ask..
Yes I can get to fastboot fine. I do a "fastboot devices" and it is read. adb doesn't seem to do anything though. The RUU is the .exe I found.
For the cid I did the old one so mine reads all 1's. I didn't think I could so the new cid as I cannot boot into Android at all.
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
rootntootn said:
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Click to expand...
Click to collapse
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
BTW There was nothing wrong with your phone, it's just that when you restored, you needed to flash the boot.img from your rom that you restored. It was most likely a kernel issue that we could correct with viper.
It sounds like you just need to install the matching rom and boot.img. If you're s off, just fastboot flash the boot.img for whatever rom you currently have installed. For the OTA update, you can install the radios without an RUU if you're s off.
I ran for several hours and several reboots on the RUU .exe file. When I downloaded a custom rom from http://forum.xda-developers.com/showthread.php?t=2150262 - That fan fine for an hour or so. Then boot loop over and over again. Thankfully I made a backup in twrp. I restored that and all is well.
I can't stand this factory rom, the part that really annoys me, besides the VZW bloat, is the recent apps button. For over a year with other HTC's I am used to making that the menu button. Had that in the custom rom.
So it looks like that rebooting loop just means I need to fastboot the boot.img?
I go back to the rom I linked about and fastboot the boot.img. I really liked viper rom but am going to stick to stock that is rooted and debloated.
My cid is all 1's since I did that before all this OTA came out. I did that about 3 weeks ago the day I got the phone.
Thanks for the tips. I'll let you know what happens when I go back to the rom above.
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Sorry about the 2's info but read that the older cid apk would no longer work (from thread below) and myself put on the new one which yields the all 2's. Bottom line, glad you made progress, hopefully problem resolved
http://forum.xda-developers.com/showthread.php?t=2109862
I had already had my phone's bootloader unlocked and rooted and had a GPe ROM installed and worked perfectly. THEN I saw that you could literally make it a Google Play edition phone complete with OTA and worked on trying to achieve that. Getting my phone S-Off wasn't working because I believe of my HBOOT version (1.55) so I was told to download this stock ROM that would downgrade me to reach a version that I could then run revone to achieve S-OFF.
POST: http://forum.xda-developers.com/showpost.php?p=45487258&postcount=55
I ran a backup through TWRP first and then flahsed this ROM, which has kept my HTC One at the HTC One splash screen. I connected it to my computer/ADB and got it into the bootloader to go into custome recovery BUT the recovery takes me to a black screen with a phone and red triangle, so it's like my recovery isn't there anymore. Fine.
I download the latest TWRP for my phone(triple checked) and ran the fastboot flash recovery command through ADB but it says
"(bootloader) signature checking...FAILED (remote: signature verify fail)"
is there some sort of way to disable the signature check using ADB or am I actually going about this the wrong way?
I'll admit, I don't do this stuff oftem, so ask as many questions as needed as I probably left out details you may need
I may be wrong but you may have to re-lock the bootloader and run the ruu back to stock.
nandroid backup restore won't change the hboot so I don't think you'll have any luck there.
I'm running ARHD 40 just till we can find a way to run s-off on our AT&T devices.
noobsquared said:
I may be wrong but you may have to re-lock the bootloader and run the ruu back to stock.
nandroid backup restore won't change the hboot so I don't think you'll have any luck there.
I'm running ARHD 40 just till we can find a way to run s-off on our AT&T devices.
Click to expand...
Click to collapse
Not to sound n00b-ish, but what would be the best way of doing this?
EDIT: Actually it is relocked already! Duh! On the bootloader screen it says "TAMPERED" and then "RELOCKED" below that
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
noobsquared said:
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
Click to expand...
Click to collapse
I actually had that downloaded but I was just concerned if that was the right move since it wipes the phone.
noobsquared said:
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
Click to expand...
Click to collapse
I hate to say this actually, but I can't find that .exe in the link. I don't know exactly what I'm looking for in it.
h_smith said:
I hate to say this actually, but I can't find that .exe in the link. I don't know exactly what I'm looking for in it.
Click to expand...
Click to collapse
Here you go:
http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
You can always unlock the bootloader again, install twrp and try to boot and see if that works.
Install the nandroid backup matching your system and you can then get to your data.
noobsquared said:
You can always unlock the bootloader again, install twrp and try to boot and see if that works.
Install the nandroid backup matching your system and you can then get to your data.
Click to expand...
Click to collapse
But how would I do that if I can't even boot up the phone past the splash screen? I did all of the unlocking and TRWP installing via the phone
Downloading and installing the file right now. It's going slow as hell but I'll run when I get the chance
THANK YOU FOR STICKING WITH ME!
h_smith said:
But how would I do that if I can't even boot up the phone past the splash screen? I did all of the unlocking and TRWP installing via the phone
Downloading and installing the file right now. It's going slow as hell but I'll run when I get the chance
THANK YOU FOR STICKING WITH ME!
Click to expand...
Click to collapse
Sure thing man. It's stuck at that screen because when your phone is unlocked, it allows custom recovery but when it's locked, it won't boot unless it finds the stock recovery. I am not 100% sure but I've had that issue as well. I had to run the RUU to get back to stock since you can't lock the bootloader with custom recovery and expect it to boot. It may vary from device to device but I've always had to RUU back to stock or fastboot flash stock recovery to get past that screen before you lock the bootloader. You can try again, there is stock recovery posted by someone in forums. Download that, try to go in fastboot mode and try fastboot flash recovery recovery_name.img. I think once you've locked the bootloader it may not work but worth a shot.
noobsquared said:
Sure thing man. It's stuck at that screen because when your phone is unlocked, it allows custom recovery but when it's locked, it won't boot unless it finds the stock recovery. I am not 100% sure but I've had that issue as well. I had to run the RUU to get back to stock since you can't lock the bootloader with custom recovery and expect it to boot. It may vary from device to device but I've always had to RUU back to stock or fastboot flash stock recovery to get past that screen before you lock the bootloader. You can try again, there is stock recovery posted by someone in forums. Download that, try to go in fastboot mode and try fastboot flash recovery recovery_name.img. I think once you've locked the bootloader it may not work but worth a shot.
Click to expand...
Click to collapse
Thank you. I'm downloading the .exe and will post the results. But it looks like that might take a few hours :/
hey is there another link? that one is so slow and keeps timing out :/
You can either use download manager or chrome browser is pretty good at managing that.
Try this: http://d-h.st/VWf
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
I just did a google search for the term RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_R and gave you the second result I got. Just search for the name of the file and you will find plenty of links.
Hope that helps.
This sounds like the exact same problem I had. The RUU and directions solved that one for me too...
Link to RUU: http://www.htc.com/us/support/news.aspx?p_id=628&p_name=htc-one-att
Other thread: http://forum.xda-developers.com/showthread.php?t=2492266
THANK YOU NOOB!!
I managed to get it fixed. Turns out HTC hosted that exact file so I downloaded it and it fixed my phone. Good times..