So I decided to be the lab rat and took the update and tried unlocking bootloader and I confirmed this myself I am unlocking and about to flash kernel and root tools I will post in a few minutes wish results
t1gartist said:
So I decided to be the lab rat and took the update and tried unlocking bootloader and I confirmed this myself I am unlocking and about to flash kernel and root tools I will post in a few minutes wish results
Click to expand...
Click to collapse
It can all be done. did it earlier. all is still good.
I just did the same thing. I updated the firmware going back to stock via RUU and accepting the OTA Update, and re-flashing my original Unlock_code.bin. Now running ViperDNA 1.1.2 with the new firmware just fine.
You do know that since u flashed the venom Rom your back to old firmware?
Check your update the Verizon one will be there again. I did the same thing. Decided to stay stock until venom is updated.
Sent from my HTC6435LVW using xda premium
does anyone know if I flash the current system write kernel, will it undo any of the new update from the OTA?
Not entirely sure, the update flashes a new boot.img, try it and see. U can always revert. It won't hurt anything.
Sent from my HTC6435LVW using xda premium
cmay227 said:
You do know that since u flashed the venom Rom your back to old firmware?
Check your update the Verizon one will be there again. I did the same thing. Decided to stay stock until venom is updated.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Not entirely. I don't have the Rom portion of the new update, but the radio firmware and other portions of the update are still there (the underlying framework). But yeah, I'm not making full use of it until I use a 2.04-based ROM.
sadly i tried 10 times last night it would unlock until rebooted and i would be showed locked again to im not sure what the hell
cmay227 said:
Not entirely sure, the update flashes a new boot.img, try it and see. U can always revert. It won't hurt anything.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
tried flashing the system write kernel, and all hell breaks loose. Its gonna take some time for the dev to incorporate all the changes.
Flashed back to RUU for now.
t1gartist said:
sadly i tried 10 times last night it would unlock until rebooted and i would be showed locked again to im not sure what the hell
Click to expand...
Click to collapse
Are you certain it wasn't 9 times or 11 times?
Turn phone off all the way. Then boot into bootloader and run unlock.bin command.
Sent from my HTC6435LVW using xda premium
Backing up my internal memory guess I'll give it a go what the heck its Friday right?
binzokun said:
tried flashing the system write kernel, and all hell breaks loose. Its gonna take some time for the dev to incorporate all the changes.
Flashed back to RUU for now.
Click to expand...
Click to collapse
Custom kernels won't work on the update?
Here are the steps I took YMMV
Backup Internal Memory
Verify Fastboot and ADB Drivers are properly installed
Boot into Bootloader
RUN "fastboot OEM Lock"
Phone reboots
Run RUU as Administrator
Wait
Boot Device
Connect to WiFi
Run Software Update from Settings
Wait
Install Update
Checked for Updates Again (Nothing)
Copy Unlock_Code.bin to your fastboot directory
ADB Reboot Bootloader
Open command prompt from fastboot directly
Run "fastboot unlock token Unlock_code.bin"
Follow the prompts
Reboot bootloader verify unlocked
Place Recovery.img in fastboot directory
RUN "fastboot flash recovery recovery.img"
Reboot
Copy over Rooted ROM
Reboot into Recovery and flash
Profit
zone23 said:
Here are the steps I took YMMV
Backup Internal Memory
Verify Fastboot and ADB Drivers are properly installed
Boot into Bootloader
RUN "fastboot OEM Lock"
Phone reboots
Run RUU as Administrator
Wait
Boot Device
Connect to WiFi
Run Software Update from Settings
Wait
Install Update
Checked for Updates Again (Nothing)
Copy Unlock_Code.bin to your fastboot directory
ADB Reboot Bootloader
Open command prompt from fastboot directly
Run "fastboot unlock token Unlock_code.bin"
Follow the prompts
Reboot bootloader verify unlocked
Place Recovery.img in fastboot directory
RUN "fastboot flash recovery recovery.img"
Reboot
Copy over Rooted ROM
Reboot into Recovery and flash
Profit
Click to expand...
Click to collapse
Sorry for the noobish question, but will I have to go through such a complex procedure as this if I'm on stock rom, unlocked and rooted? Rooting alone the first time was quite time consuming for me :\
I know I could simply stick with what I have now. I'd really like to have the new firmware though, which supposedly fixes audio and wifi issues.
supertoast92 said:
Sorry for the noobish question, but will I have to go through such a complex procedure as this if I'm on stock rom, unlocked and rooted? Rooting alone the first time was quite time consuming for me :\
Click to expand...
Click to collapse
My suggestion then would be to wait and see if someone comes up with a way to flash the radios. That is the only reason I went through the process.
If I have a backup of stock rooted, do I still have to use RUU?
Will do, thanks!
Word of caution people, once you install the OTA update, your HBoot get updated, so the current RUU stops working. Once you apply the update, there's no going back. All custom kernels don't work, I spend all night trying all of them, the phone just stuck at the boot animation.
I would suggest holding out until all the kernels/custom roms/RUUs are updated, cause if anything goes wrong you have very little tools to work with, especially when we don't have S-Off.
That's good to know. Thank you!
Sent from my HTC DNA
Related
I realize that there are tons of threads about this but I haven't been able to find any that match my setup.
So I S-OFF'd while running the gb firmware, now I want to update to the ics ota firmware so I can run cm9. My question is that do I need to change my hboot after running the ruu, and if so how do I do that? I know these are probably simple questions but I just want to make sure I don't brick my only phone.
Sent from my ADR6425LVW using xda app-developers app
Without having to do the full ruu get these files listed from here http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/
[ICS][2.25][JB][5-7]PH98IMG.zip - This is radio/pateched hboot combo
&
PH98IMGSTOCKREC.zip This is stock recovery
Updated the radio/hboot with that combo. Then once completed flash the stock recovery and then do a factory reset. Once completed go back into hboot, reflash custom recovery. Then in your custom recovery wipe data/cache then choose your rom.
Snuzzo said:
Updated the radio/hboot with that combo.
Click to expand...
Click to collapse
I do that by renaming it to PH98IMG.zip correct? And I flash the stock recovery by renaming that PH98IMG.zip as well right?
magicnanners said:
I do that by renaming it to PH98IMG.zip correct? And I flash the stock recovery by renaming that PH98IMG.zip as well right?
Click to expand...
Click to collapse
Stock recovery, you can do that or extract it out and fastboot flash. The radio/hboot will need to be renamed.
Snuzzo said:
Stock recovery, you can do that or extract it out and fastboot flash. The radio/hboot will need to be renamed.
Click to expand...
Click to collapse
Awesome thanks I might wait until tomorrow to start all of this because if I don't finish tonight I won't have a phone in the morning lol. But thank you for your help I really appreciate it
magicnanners said:
I realize that there are tons of threads about this but I haven't been able to find any that match my setup.
So I S-OFF'd while running the gb firmware, now I want to update to the ics ota firmware so I can run cm9. My question is that do I need to change my hboot after running the ruu, and if so how do I do that? I know these are probably simple questions but I just want to make sure I don't brick my only phone.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Simple answer would be ....if you are soff. And fastboot is properly setup, then type fast boot OEM lock when you are in fast boot mode. It will lock and reboot. Pull battery. Boot back into bootloader (assuming you have a stock boot loader) and run the latest ics ruu exe. Then once it boots. Enable adb debbuging. Disable quickboot in power setting. Pull battery. Go back to fast boot. HTC dev unlock. You should already still have the unlock token on your pc. Unlock the bootloader. Then fastboot the recovery. Go to the recovery ( I like amon ra) and flash super user. Then reboot...or flash your Rom. All done.
stkiswr said:
Simple answer would be ....if you are soff. And fastboot is properly setup, then type fast boot OEM lock when you are in fast boot mode. It will lock and reboot. Pull battery. Boot back into bootloader (assuming you have a stock boot loader) and run the latest ics ruu exe. Then once it boots. Enable adb debbuging. Disable quickboot in power setting. Pull battery. Go back to fast boot. HTC dev unlock. You should already still have the unlock token on your pc. Unlock the bootloader. Then fastboot the recovery. Go to the recovery ( I like amon ra) and flash super user. Then reboot...or flash your Rom. All done.
Click to expand...
Click to collapse
You don't need to OEM Lock if you're S-Off.
darkghost568 said:
You don't need to OEM Lock if you're S-Off.
Click to expand...
Click to collapse
I'm sorry. I did that and forgot lol. Hell if your s off you can pretty much do what ever.
stkiswr said:
I'm sorry. I did that and forgot lol. Hell if your s off you can pretty much do what ever.
Click to expand...
Click to collapse
Ikr
Hey everyone,
So I have successfully HTC Unlocked my Rezound bootloader, installed Amon Ra, and then installed and booted the CM9 unofficial. Problem was that CM9 wasn't quite as cooperative as I'd hoped - it is unofficial, after all, and so I decided to abandon that in favor of Nils' Business ROM. Here's where I ran into issues.
I have tried everything in every order I can find online and think of, including Nils' writeup. So, for the life of me, I cannot get the leaked ICS RUU to boot (4.03.605.2 as listed in his instructions on XDA). Install runs fine every time I do it from the relocked (I checked) stock HBOOT, all steps included. Every time it reboots (and I've tried forcing it back into hboot to do the install a second time) it just goes to the white HTC screen and starts boot looping. Tried it a million ways, no go. Also worth noting - the stock recovery doesn't install properly, either. Some'fin is hinky, here.
So I've tried just "assuming" it went fine anyhow and then proceeding with the install for Nils' ROM and same deal, no go, although with one difference. With Nils' ROM, it does display the boot splash screen "Nils Business ROM" or what have you about 1 out of every 4 "boots" in the loop cycle, and then reboots again.
I think I am going to perform S-OFF tomorrow if I have the time, and then try it again using the S-OFF instructions, but I would sincerely appreciate any help from you all. Honestly, I'm at near wit's end with this device, and I don't want to be, I enjoy this chase too much, but I *really* want the reward at the end of it, lol.
Any help is deeply appreciated.
- Katie
Re: [Q]
I'm guessing because of the corrupted recovery, you have a bad download of the RUU. Try re downloading and check the md5 hash for a match. The ruu should reboot itself after the first pass and end up in bootloader again for the second pass.... If not then after the first pass just hold down power + vol down to get back to bootloader.
Hope this helps
Sent from my ADR6425LVW using xda app-developers app
Make sure that you have a booting ROM before you s-off. You will cause yourself all kinds of heartache if you don't.
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Snuzzo said:
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Click to expand...
Click to collapse
Hey, thanks. Yeah, the RUU does check out just fine against an MD5SUM.
nm.... just read your original post again and you say you did relock the phone. I was hoping it was something simple like that that was overlooked.
Carry on...
feralicious said:
Nothing to see here, folks, move along.
Click to expand...
Click to collapse
Right now, I cannot S-OFF because it requires a working stock image, and I'll be lucky to get anything more than CM9 unofficial working here.
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
feralicious said:
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
Click to expand...
Click to collapse
Well that's the trick. CM9 didn't work well enough to even be worth backing up. I'm trying to reinstall it again now just to see if I get there - and it looks like I will. Once I'm back up with that, I'm not sure where to go from there. The phone barely worked under CM9. Really hoping to get Nils' ROM on there, since it gives all the nice features of a stock device without the bloatware. Even if I never get S-OFF, I'll be perfectly happy with just Nils' software.
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
feralicious said:
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
Click to expand...
Click to collapse
I did try wiping everything first. No luck. I will try the CleanWipe tomorrow, because right now, whatever my issues are, I'm being prevented from solving them since I can't S-OFF and I can't even seem to get a working ROM to make the phone worth having! Ugh.
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Thank you, your magnanimity! Seriously, lol, you're gracing my thread just by being here. :victory:
feralicious said:
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Click to expand...
Click to collapse
Thanks for the clicky, Feralicious. Same results, unfortunately. I'm going to try doing the RUU flash of Nils' ROM instead. Do you guys know where I can get the ICS firmware by itself? I cannot be sure that it's actually flashed right, unfortunately.
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
I'll do that stuff and let you know. Thank you!
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
ncc74656m said:
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
Click to expand...
Click to collapse
My DNA said something about failing when I locked it. But it locked just fine.
Since it is failing.
fastboot oem rebootRUU
fastboot oem lock ----if unlocked
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Should work Maybe
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
Click to expand...
Click to collapse
Ok, so, this part including a factory reset got me to "HTC Quietly Brilliant" screen, but then it bootloops again. Tried factory resetting again to no avail. Trying the second part.
Flyhalf205 said:
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Click to expand...
Click to collapse
Same thing as before unfortunately. :/ Performed a factory reset afterwards to be safe - no go. Everything shows OK though in both this and the above install. *shrug*
Flyhalf205 said:
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
ncc74656m said:
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
Click to expand...
Click to collapse
I really wouldn't see why you would need a Sense rom to get s-off. I would imagine it would just need su and busybox installed. But nandroid then try a sense rom again. Make sure you flash the boot.img through fastboot
I'm trying to help a buddy of mine. He has a Thunderbolt, issued through work. It is stock, unrooted, locked, never modded. He recently got the ICS OTA update. Phone was functional, but laggy and a bit unstable. He did a factory reset, and initially the phone was fine for a few hours, then it was acting buggy. After a reboot it was fine for a bit, then froze. Usable time kept diminishing with subsequent reboots. He tried another factory reset, and the phone won't boot now. If you power it up, you get the white screen with the HTC logo, then a black screen, and nothing ever happens. I can get to Hboot. I can get to fastboot. Not sure if recovery does anything. I get the recovery screen, then a reboot, and then nothing.
I've been trying to read up on how to fix this, and I'm not sure how to go about it since the phone is currently locked, and won't boot. I looked at the Thunderbolt All In One tool, but it looks like it needs the phone to be booted to start the process.
My end goal is to get back to stock, unrooted, (Gingerbread, then OTA update I suppose), and S-on. But to do that, I need to obtain s-off first. Any info would be greatly appreciated.
I've attached a couple of pics.
Thank you.
a little side note
from what I've read verison has been replacing some phones that the ota has killed or broken something..
worth checking out...
I believe even out of warrenty..
cujo6801 said:
a little side note
from what I've read verison has been replacing some phones that the ota has killed or broken something..
worth checking out...
I believe even out of warrenty..
Click to expand...
Click to collapse
Good to know. Thank you. I think because it was employer issued, he's going to try to get a newer device if we can't get it running. But I just had to make some attempt to get it running.
Pm disconnecktie as you should be able to flash via abd beings you can get in to fastboot. He knows a lot about the workings of these phones.
Sent from my ADR6425LVW using Tapatalk 2
It could possibly be fixed by fastboot flashing the official release but I think a package would need to be put together for that to work correctly. Since the phone doesn't boot it limits the ways to fix it especially since we don't have an Ruu for the ics ota. Also because it doesn't boot adb commands are useless. Fastboot commands are unlikely to work either but I guess you could try by connecting the usb cable. Open a command prompt and type fastboot devices. If it shows the serial number then fastboot commands will work.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
It could possibly be fixed by fastboot flashing the official release but I think a package would need to be put together for that to work correctly. Since the phone doesn't boot it limits the ways to fix it especially since we don't have an Ruu for the ics ota. Also because it doesn't boot adb commands are useless. Fastboot commands are unlikely to work either but I guess you could try by connecting the usb cable. Open a command prompt and type fastboot devices. If it shows the serial number then fastboot commands will work.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Fastboot does work. I was able to do the "fastboot devices" command before, and saw the phone. I was also able to "fastboot flash zip" the file from post 12 from this tread (link below), BUT even though the file transferred from the computer to the phone, the actual flash failed... I'm assuming because the phone is locked.
http://forum.xda-developers.com/showthread.php?t=2120985&page=2
Try downloading the official ota zip over at the developer section. Put it on the root of your sd card and rename it to PG05IMG. Then run the update through fastboot. I seriously doubt this will solve the problem long term but it may work. I have doubts. I am beginning to think htc released the ota purely for development purposes. More and more people are popping in here with problems similar to this.
Sent from my ADR6400L using Tapatalk 2
I downloaded santod040's full ODEXED ICS ROM. That's the only thing I noticed that said "Official". Hopefully I didn't miss something obvious. I put it on the SD card and renamed it. Booted Hboot, and the file loaded, checked, then stopped and went back to the Hboot menu. No option to flash or install. Then, I tried doing fastboot flash zip from the command line while the phone was in Fastboot. It sent the file, and loaded it, then failed booloader signature checking. I'm not sure if there is another method to try. I have SOME working knowledge on how to do this stuff, but not as much as many of the members here, I'm sure.
SoundTech said:
I downloaded santod040's full ODEXED ICS ROM. That's the only thing I noticed that said "Official". Hopefully I didn't miss something obvious. I put it on the SD card and renamed it. Booted Hboot, and the file loaded, checked, then stopped and went back to the Hboot menu. No option to flash or install. Then, I tried doing fastboot flash zip from the command line while the phone was in Fastboot. It sent the file, and loaded it, then failed booloader signature checking. I'm not sure if there is another method to try. I have SOME working knowledge on how to do this stuff, but not as much as many of the members here, I'm sure.
Click to expand...
Click to collapse
You need to be rooted to use a rom
Sent from my Nexus 7 using Tapatalk 2
Yeah, that wasn't too swift of me, was it now?
I grabbed the zip from this thread:
http://forum.xda-developers.com/showthread.php?t=2144326
Tried Hboot with the file renamed, same results as previous post. Tried fastboot flash zip, same results as above. No joy.
Going to try to see if HTCDev will get the bootloader unlocked in the current phone state.
Well since the ota isn't a downgrade I thought it may work. If HTC dev is able to unlock his bootloader maybe he can get further.
Sent from my personally built from source CM10.1 N7.
Bootloader is unlocked now, since it was all through fastboot. Still S-on. Tried with the OTA zip still on the SD card as "PG05IMG.zip." It loaded, started to check, started to parse for a moment, then went back to the Hboot screen, reboot got me nowhere. I need to go deal with the rest of life now. I'll try again tomorrow. I appreciate everyone's help today. Thank you.
At this point just s off and install a recovery then you can flash that ROM.
Sent from my Nexus 7 using Tapatalk 2
Use this guide here. Make sure you have plenty of time before hand and FOLLOW THE DIRECTIONS IN ORDER TO A T. It is very important that you don't skip over stuff. This is the only current method to get s off with ics.
Sent from my ADR6400L using Tapatalk 2
Long day at work, but back to it. Making sure the battery is charged up, and downloading files.
I'm looking at a post on ThunderboltForums. Making absolutely sure here: Is THAT the one I should be following?
Follow-up: At the end of step 28, after flashing the .19 ROM, is says to use the All-In-One tool. IF I plan to be stock, unrooted, locked, S-on, it seems I'm there at this point, and I can let the OTA update run. Is that correct?
Thanks again.
Looks like I'm on stock Gingerbread, S-off, re-locked, stock recovery. Heck, it finally boots! I'll see about trying OTA update tomorrow.
Thanks again.
S off and relocked? You need to run the allinonetool first and unlock the bootloader before you flash anything.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
S off and relocked? You need to run the allinonetool first and unlock the bootloader before you flash anything.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Huh. I never did use the tool. I went through the steps on the ThunderboltForums post all the way through flashing the .19 ROM. Unless I missed something or did something wrong, before the flash it said I would be re-locked and S-on. After the flash it said the phone should be "back to normal". The next step was the All-In-One tool. But the device actually booted into android with the .19 ROM. That was the first time I saw it boot since I got my hands on it. Perhaps the process in that thread helped repair whatever part of the system was buggered up to begin with?
Regardless, I tried the OTA update, and the phone took the ICS update through Verizon. It seems to be running better now than it did before. It's back in my buddy's possession, and he's in the process of getting his apps and data reinstalled.
He thanked me profusely for getting it running again. So I, in turn, pass his thanks on to everyone here that helped me out, the people that worked to get the Thunderbolt resources to where they are now, and to the forum in general for existing and doing what it does. Thank you all.
Ok since I have less than 10 posts I can not post in the area that I would have liked to:
http://forum.xda-developers.com/showthread.php?t=2559232
I am having the same Issue as badfishie in that I am stuck on the:
Under Test 2:
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
FATAL: Download updated package at www.rumrunner.us
After I Downloaded it again a second time, and the DNA version. Yes I tried the first version first, and investigated it.
I have followed GrzlyAdms advice and factory reset my device numerous times.
I even gone so far as to Return my device to factory Sence 5.
http://forum.xda-developers.com/showthread.php?t=2570548
My bootloader still shows S-OFF from the moonshine that I was successful at applying.
But after the OTA with Voodoo OTA Rootkeeper not able to keep root...
http://forum.xda-developers.com/showthread.php?t=1241517
I am once again trying to gain root access for my device.
I have:
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
Made sure to use a USB 2.0 port, and Original USB cord
Made sure adb can see my device
Run soju as Administrator
Drivers installed with Tool kit: http://forum.xda-developers.com/showthread.php?t=2219175
AV and firewall disabled
Using Windows 7 x64 and Minimal ADB and Fastboot http://forum.xda-developers.com/showthread.php?t=2317790
Any assistance would be appreciated. Thanks!
Mind if I ask why are you trying to unlocked you bootloader and soff or your already soff?
Ok, I'll try to help best I can. Hopefully one of the more experienced folks can chime in too as they'll probably be way more helpful. I've got a couple guesses, but need to know a bit more. Please know that I'm only providing my best guesses as I haven't run into this problem.
What firmware version were you on when you tried rumrunner? It sounds like you already had an unlocked bootloader and s-off... through moonshine. Did you end up with a locked bootloader? If so, how? You mentioned that you went back to sense 5. What method? Did you ruu back to a stock rom or just flash one of the Custom/stock ROMs.
Here is one possible option. I would suggest reading through the thread thoroughly before diving in...
- Go back to 100% stock with locked bootloader and s-on: http://forum.xda-developers.com/showthread.php?t=2293919
Then make sure you've taken any OTA updated to get to 3.06.605.4 and you should be able to use rumrunner.
GrzlyAdms said:
Ok, I'll try to help best I can. Hopefully one of the more experienced folks can chime in too as they'll probably be way more helpful. I've got a couple guesses, but need to know a bit more. Please know that I'm only providing my best guesses as I haven't run into this problem.
What firmware version were you on when you tried rumrunner? It sounds like you already had an unlocked bootloader and s-off... through moonshine. Did you end up with a locked bootloader? If so, how? You mentioned that you went back to sense 5. What method? Did you ruu back to a stock rom or just flash one of the Custom/stock ROMs.
Here is one possible option. I would suggest reading through the thread thoroughly before diving in...
- Go back to 100% stock with locked bootloader and s-on: http://forum.xda-developers.com/showthread.php?t=2293919
Then make sure you've taken any OTA updated to get to 3.06.605.4 and you should be able to use rumrunner.
Click to expand...
Click to collapse
The reason the thing is failing is because he already has a unlocked bootloader with soff. I don't know why he is trying to unlock something that is already unlocked. All he needs to do is download something like superuser or flash a custom rom with root built into it.
thayl0 said:
The reason the thing is failing is because he already has a unlocked bootloader with soff. I don't know why he is trying to unlock something that is already unlocked. All he needs to do is download something like superuser or flash a custom rom with root built into it.
Click to expand...
Click to collapse
10-4. That's kinda what I thought too, but figured I'd try to confirm by asking a few questions. I have seen a few people get stuck with s-off but a locked bootloader if they goof up the process trying to go back to 100% stock. Thought I'd ask the questions just in case this is what he did.
Ok, I would like to keep the Stock Android, but would like to have root access.
I an unsure how to gain root access with out turning S-ON.
I could follow that and turn S-ON again,
But if you have another method of gaining ROOT with out flashing a custom ROM,
I would be grateful for your assistance.
Sorry for any confusion on that,
I spent 10hrs trying to figure this out yesterday,
it was necessary to put down and look at another day.
I have tried downloading superuser and supersu from the play store, neither give me access to root
However I have looked on your forums since you suggested simply flashing another rom already with root access - Thanks for that btw
this post shows the full version, but has odex and deodex, well deodex is pulled, may i ask what the difference is?
http://forum.xda-developers.com/showthread.php?t=2560010
I will flash the odex one now and see what happens, thanks again I needed a fresh look at this I guess.
p1droidx said:
I have tried downloading superuser and supersu from the play store, neither give me access to root
However I have looked on your forums since you suggested simply flashing another rom already with root access - Thanks for that btw
this post shows the full version, but has odex and deodex, well deodex is pulled, may i ask what the difference is?
http://forum.xda-developers.com/showthread.php?t=2560010
I will flash the odex one now and see what happens, thanks again I needed a fresh look at this I guess.
Click to expand...
Click to collapse
You must already have a superuser app to install one from the play store. Flash a superuser zip from recovery. That will put both the app and the required binaries in place.
Yo this is a random question if I go back to stock 2.06 soff and rooted will rumrunner update me or what?
Sent from my HTC6435LVW using Tapatalk 4
TheRealDeadApe said:
You must already have a superuser app to install one from the play store. Flash a superuser zip from recovery. That will put both the app and the required binaries in place.
Click to expand...
Click to collapse
Uh ok, let me look for this, maybe you already have a link, if not, I will try and find it, and if I find it I will post it here.
deathrow1992 said:
Yo this is a random question if I go back to stock 2.06 soff and rooted will rumrunner update me or what?
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
From what I have learned so far, running rumrunner when you are already S-OFF will net you a FAILED message. if your DNA is already S-OFF then feel free to flash whatever ROM you want.. well sorta, make sure it's for the DNA, and flash at your own risk.
I took the OTA after achieving S-OFF with moonshine and it removed my root access... now I am in this boat where I want to regain root.
I have finally finished downloading the zip from: http://forum.xda-developers.com/showthread.php?t=2560010
But I have no idea how to flash it, step by step instructions would be helpful since this is my first flash and I have yet to figure it out. I have tried fastboot flash zip but that didn't work, and I am unfamilar with this....
The FAQ here: http://forum.xda-developers.com/showthread.php?t=2188944
is of no help unfortunately....
I found some Instructions that tell you to boot into recovery, but when I try to boot into recovery all I get is a RED ! and Triangle above a screen. like something went wrong :/
Start by downloading ROM and the patch and copy the file to the SD card’s root in your device.
Reboot your phone into recovery mode. For this, power off your device and restart it keeping the volume down key pressed. Your phone will be booted into bootloader fastboot mode.
In the Recovery mode, use the ‘Power ’key to select and to navigate use the ‘Volume’ keys.
Use ‘backup and restore’ option to create a backup.
Now perform three steps in a row: first wipe data//factory reset, then wipe cache and lastly wipe dalvik cache accessing the advanced menu.
Now install zip from your sdcard, then select ROMs zip file you copied to your phone and choose zip.
Redo it for Patch file once you are done with ROM installation.
At the end, reboot your phone.
Lovely I didn't have a recovery installed, using the tools: http://forum.xda-developers.com/showthread.php?t=2219175
I installed the TWRP 2.5.0.0 recovery,
THEN I was able to enter recovery and flash the ROM.
WOW what a experience, this has been.
p1droidx said:
I have finally finished downloading the zip from: http://forum.xda-developers.com/showthread.php?t=2560010
But I have no idea how to flash it, step by step instructions would be helpful since this is my first flash and I have yet to figure it out. I have tried fastboot flash zip but that didn't work, and I am unfamilar with this....
The FAQ here: http://forum.xda-developers.com/showthread.php?t=2188944
is of no help unfortunately....
I found some Instructions that tell you to boot into recovery, but when I try to boot into recovery all I get is a RED ! and Triangle above a screen. like something went wrong :/
Start by downloading ROM and the patch and copy the file to the SD card’s root in your device.
Reboot your phone into recovery mode. For this, power off your device and restart it keeping the volume down key pressed. Your phone will be booted into bootloader fastboot mode.
In the Recovery mode, use the ‘Power ’key to select and to navigate use the ‘Volume’ keys.
Use ‘backup and restore’ option to create a backup.
Now perform three steps in a row: first wipe data//factory reset, then wipe cache and lastly wipe dalvik cache accessing the advanced menu.
Now install zip from your sdcard, then select ROMs zip file you copied to your phone and choose zip.
Redo it for Patch file once you are done with ROM installation.
At the end, reboot your phone.
Lovely I didn't have a recovery installed, using the tools: http://forum.xda-developers.com/show....php?t=2219175
I installed the TWRP 2.5.0.0 recovery,
THEN I was able to enter recovery and flash the ROM.
WOW what a experience, this has been.
Click to expand...
Click to collapse
well glad you got it sorted out.... it can be quite a lot to take in if you have never done anything like that before. but once you have done it a few times it is much easier to do and remember especially if you run into problems.
cheers
and happy customizing.
deathrow1992 said:
Yo this is a random question if I go back to stock 2.06 soff and rooted will rumrunner update me or what?
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
Rumrunner doesn't update nothing. Try asking your question again.
Sent from my dlx using XDA Premium 4 mobile app
thayl0 said:
Rumrunner doesn't update nothing. Try asking your question again.
Sent from my dlx using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I was kind messed up last night today is my bday. what I meant to ask is can I receive the ota update if I go back to stock soff rooted 2.06 and if not what do I have to do to get it
Sent from my HTC6435LVW using Tapatalk 4
deathrow1992 said:
Sorry I was kind messed up last night today is my bday. what I meant to ask is can I receive the ota update if I go back to stock soff rooted 2.06 and if not what do I have to do to get it
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
if you want the 3.06.605.4 update (aka 4.2.2) and you are already s-off - and want STOCK no root: http://forum.xda-developers.com/showthread.php?t=2570548
if you want root to go with that: http://forum.xda-developers.com/showthread.php?t=2560010
if you are stock 2.06 you can take the OTA even if you are s-off, but if you have root, you will loose root taking the ota.
p1droidx said:
if you want the 3.06.605.4 update (aka 4.2.2) and you are already s-off - and want STOCK no root: http://forum.xda-developers.com/showthread.php?t=2570548
if you want root to go with that: http://forum.xda-developers.com/showthread.php?t=2560010
if you are stock 2.06 you can take the OTA even if you are s-off, but if you have root, you will loose root taking the ota.
Click to expand...
Click to collapse
So will the second link you have me work even if I'm on a 2.06 custom Rom? Thanks for the help by the way
Sent from my HTC6435LVW using Tapatalk 4
deathrow1992 said:
So will the second link you have me work even if I'm on a 2.06 custom Rom? Thanks for the help by the way
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
if you want to revert to stock, since i didn't flash the second till i flashed the first, i would suggest that you do that, if you want to go with another custom rom, follow it's instructions, if it asks for a specific starting point, aka stock 4.2.2 then flash the first one then flash the custom one.
Software version 1.54.1540.9 w/Extreme Power Saving... Uploading ota now for folks who need or want it
https://drive.google.com/file/d/0Bx5-C2BrwNVxdjY2WVVsdXBIUzA/edit?usp=sharing
Wonders_Never_Cease said:
Software version 1.54.1540.9 w/Extreme Power Saving... Uploading ota now for folks who need or want it
https://drive.google.com/file/d/0Bx5-C2BrwNVxdjY2WVVsdXBIUzA/edit?usp=sharing
Click to expand...
Click to collapse
Thanks! I hope I can extract the firmware.zip out of this and RUU mode flash it on my Dev. I only want the updated firmware.
All you have to do after download is pull it outta the ota and flash it as you would any other firmware
Wonders_Never_Cease said:
All you have to do after download is pull it outta the ota and flash it as you would any other firmware
Click to expand...
Click to collapse
That's what I thought too, but now i'm hard bricked!!! :crying:
I used fastboot oem rebootRUU and then fastboot flash zip firmware.zip
I updated the firmware in my M7 a few times using this method without incident, but my M8 is now dead...
what was your cid? this was only for developer builds I redid my device twice with it...flashed a complete nand back up and then this ota through stock recovery... did you do the firmware upgrade to 1.54 euro? or any other firmware related flashes?
1 fastboot oem writecid BS_US001
2 fastboot oem readcid
3 fastboot reboot-bootloader
4 fastboot oem rebootRUU
5 fastboot flash zip nameofzip.zip
6 fastboot reboot-bootloader
guyd said:
That's what I thought too, but now i'm hard bricked!!! :crying:
I used fastboot oem rebootRUU and then fastboot flash zip firmware.zip
I updated the firmware in my M7 a few times using this method without incident, but my M8 is now dead...
Click to expand...
Click to collapse
Are you not super cid? When you say hard bricked what is your m8 doing now? Can you get to bootloader. You can't even flash unless you are soff or have true developer edition phone so I would assume you made your phone super cid too?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Wonders_Never_Cease said:
what was your cid? this was only for developer builds I redid my device twice with it...flashed a complete nand back up and then this ota through stock recovery... did you do the firmware upgrade to 1.54 euro? or any other firmware related flashes?
1 fastboot oem writecid BS_US001
2 fastboot oem readcid
3 fastboot reboot-bootloader
4 fastboot oem rebootRUU
5 fastboot flash zip nameofzip.zip
6 fastboot reboot-bootloader
Click to expand...
Click to collapse
CID was BS_US002 on a Developer Edition. No firmware upgrades, it was original!!!
I was S-OFF with custom ROM, custom Kernel, and custom Recovery. That's it.
I removed the boot.img and recovery.img out of the zip prior to flashing.
The flash process appeared to work, and nearly all pieces installed successfully.
But after I issued a fastboot reboot, it was dead! No screen, no led, no nothing.
Computer doesn't see it as a device, thus adb or fastboot no longer work.
My first hard brick ever, and I hope my last!
guyd said:
CID was BS_US002 on a Developer Edition. No firmware upgrades, it was original!!!
I was S-OFF with custom ROM, custom Kernel, and custom Recovery. That's it.
I removed the boot.img and recovery.img out of the zip prior to flashing.
The flash process appeared to work, and nearly all pieces installed successfully.
But after I issued a fastboot reboot, it was dead! No screen, no led, no nothing.
Computer doesn't see it as a device, thus adb or fastboot no longer work.
My first hard brick ever, and I hope my last!
Click to expand...
Click to collapse
Hate to hear that. I'm sure you have already tried this but just in case you haven't. Vol up and power for 10 sec then immediately vol down and power for 5 seconds. Even if you don't see bootloader try fastboot command. Try with and without phone plugged in.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Well sorry to hear this,probably reason it borked your device is it needs the stock recovery i think to finish flashing,didnt look at [email protected] but that would be my guess...I always flash stock recovery before flashing an ruu or firmware zip.
guyd said:
CID was BS_US002 on a Developer Edition. No firmware upgrades, it was original!!!
I was S-OFF with custom ROM, custom Kernel, and custom Recovery. That's it.
I removed the boot.img and recovery.img out of the zip prior to flashing.
The flash process appeared to work, and nearly all pieces installed successfully.
But after I issued a fastboot reboot, it was dead! No screen, no led, no nothing.
Computer doesn't see it as a device, thus adb or fastboot no longer work.
My first hard brick ever, and I hope my last!
Click to expand...
Click to collapse
an0ther said:
Hate to hear that. I'm sure you have already tried this but just in case you haven't. Vol up and power for 10 sec then immediately vol down and power for 5 seconds. Even if you don't see bootloader try fastboot command. Try with and without phone plugged in
Click to expand...
Click to collapse
Tried those like fifty times! My device is is bricked harder than a diamond...
Wish I knew what exactly happened so I don't do it again. As I said in my previous post, I've done this same thing on my M7 several times without a hitch. Only difference I saw this time was that the RUU flash routine didn't stop after flashing the hboot like it did on my M7 and make me run it one more time to get the rest of the firmware flashed. To be sure I got it all, I flashed it a second time anyway. That was the only difference I saw!
---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------
Wonders_Never_Cease said:
Well sorry to hear this,probably reason it borked your device is it needs the stock recovery i think to finish flashing,didnt look at [email protected] but that would be my guess...I always flash stock recovery before flashing an ruu or firmware zip.
Click to expand...
Click to collapse
I've ran the RUU flash command on my M7 with a custom recovery several times without incident. Didn't see why it would be any different on the M8, but something is. Wish I would have had an MD5 to verify my download, but it extracted fine so I think it was good.
Only one thing I found that was different from the M7 to the M8.
In the M7 it used hbootpreupdate:3
In the M8 it used hbootpreupdate:12
Wish I knew what this does different.
how did you remove the boot and recovery out of zip? Mine says corrupted when i try to unzip which usually means its encrypted. If you just manually zipped it back up that could be the problem. I don't know what happened and am interested to figure out. At least it is just dead and htc should swap it out no problem.
I'm curious. Sorry if this a silly question, I'm still new to all of this...
Wonders_Never_Cease, So I should flash back to the recoverydevm8.img you provided previously in the A_T_T_Test_1_12_1540_17_ISIS ROM you created first?
Thanks.
Safest way I would suggest is do a restore of a nand backup to completely stock developer build including recovery(1.12.1540.17) and then flash this via stock recovery if you havent gotten the notification after you revert to everything stock...You do not need to relock bootloader if s-off'd...as long as everything else is stock itll flash just fine...Hope this answered your questions about flashing this file.
skhullar said:
I'm curious. Sorry if this a silly question, I'm still new to all of this...
Wonders_Never_Cease, So I should flash back to the recoverydevm8.img you provided previously in the A_T_T_Test_1_12_1540_17_ISIS ROM you created first?
Thanks.
Click to expand...
Click to collapse
Thanks for the guidance.
Lets say a newbie, in his infinite wisdom excitedly rushed to apply a great ROM and failed to create a nand backup of his stock setup... Where would such a bonehead be able to get his hands on a complete nand backup of the stock developer build?
Wonders_Never_Cease said:
Safest way I would suggest is do a restore of a nand backup to completely stock developer build including recovery(1.12.1540.17) and then flash this via stock recovery if you havent gotten the notification after you revert to everything stock...You do not need to relock bootloader if s-off'd...as long as everything else is stock itll flash just fine...Hope this answered your questions about flashing this file.
Click to expand...
Click to collapse
skhullar said:
I'm curious. Sorry if this a silly question, I'm still new to all of this...
Wonders_Never_Cease, So I should flash back to the recoverydevm8.img you provided previously in the A_T_T_Test_1_12_1540_17_ISIS ROM you created first?
Thanks.
Click to expand...
Click to collapse
I would suggest you make your phone super cid before you do any flashing.
Hes already running my rom....Not needed,using brightstar cid works fine as att and developer builds are same mid
an0ther said:
I would suggest you make your phone super cid before you do any flashing.
Click to expand...
Click to collapse
Ill send you a link in the a.m.,lol
skhullar said:
Thanks for the guidance.
Lets say a newbie, in his infinite wisdom excitedly rushed to apply a great ROM and failed to create a nand backup of his stock setup... Where would such a bonehead be able to get his hands on a complete nand backup of the stock developer build?
Click to expand...
Click to collapse
Link and instructions sent...Enjoy
Thank You!
Wonders_Never_Cease said:
Link and instructions sent...Enjoy
Click to expand...
Click to collapse
So no definite way to convert to Dev Edition then I'm guessing, right?