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.
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
Evening!!
I'm hoping you all might be able to help me out here. I have been running the OTA GB ROM for months now. Tonight I rebooted my phone by just holding the power button and hitting reboot. Its now however stuck on the HTC screen and won't boot past it.
I can get into the FASTBOOT menu and such, however when I try to go into the RECOVERY the phone just shuts off, or it will just reboot back into the HTC screen. I've tried download the Rezound_All-In-One_Kit_v2.0 and was able to flash the recovery again however I'm getting the same results, phone just shuts off.
Any idea on how to get my phone back? I really don't care about the data on the phone, just want to get it backup and working. lol I'm really confused as to why all the sudden its getting stuck on the HTC screen.
Did you try removing the battery and putting it back in?
are you rooted? which recovery?
I'm using Amon Ra style vigor and I am unlocked/rooted.
I'm trying to get ADB to detect my phone, but not having luck in that realm either. Was just going to try to push a ROM over to the phone. However it does not appear that it will detect my phone when in the FASTBOOT USB mode. I do a adb devices and it just comes back as none being found...
Kabish said:
I'm using Amon Ra style vigor and I am unlocked/rooted.
Click to expand...
Click to collapse
Download the RUU. Relock your phone ("fastboot oem lock" from command prompt), and run the ruu from your PC while connected to USB. After that you can unlock your phone again and start from scratch.
link to the RUU:
http://forum.xda-developers.com/showpost.php?p=22045045&postcount=58
Will do downloading now, and thank you for the link. I so want to bang my head on the table.
Kabish said:
I'm trying to get ADB to detect my phone, but not having luck in that realm either. Was just going to try to push a ROM over to the phone. However it does not appear that it will detect my phone when in the FASTBOOT USB mode. I do a adb devices and it just comes back as none being found...
Click to expand...
Click to collapse
disconnect your phone
close command prompt
ctrl+alt+del and kill any adb process
take out your battery, then put your battery back and connect your phone to your PC and boot to fastboot.
open up CMD again and you should be able to detect your phone.
Ugh...
"ERROR [140]: BOOTLOADER VERSION ERROR"
"The ROM Update Utility cannot update your Android Phone.
Please get the correct ROM Update Utility and try again"
Kabish said:
Ugh...
"ERROR [140]: BOOTLOADER VERSION ERROR"
"The ROM Update Utility cannot update your Android Phone.
Please get the correct ROM Update Utility and try again"
Click to expand...
Click to collapse
you're on the latest gb update?
Yes I should be on the latest OTA. I had my phone rooted when I first got it, then Verizion did an OTA update which was messing with my phone. So I did an RUU and then re-rooted with the OTA Pre Root ROM.
Trying to follow this thread now.. Corsses Fingers...
http://forum.xda-developers.com/showthread.php?t=1338916&page=6
Kabish said:
Yes I should be on the latest OTA. I had my phone rooted when I first got it, then Verizion did an OTA update which was messing with my phone. So I did an RUU and then re-rooted with the OTA Pre Root ROM.
Trying to follow this thread now.. Corsses Fingers...
http://forum.xda-developers.com/showthread.php?t=1338916&page=6
Click to expand...
Click to collapse
gl. let me know how it goes.
Looks like that is not going to work.. I pulled the "firmware" file from that post and renamed it to the PH98IMG.ZIP.
It goes to "Loading...PH98IMG.ZIP
Then
Parsing...PH98IMG.ZIP
Then it just goes back to the main HBOOT menu.
I did unlock my phone again since I had locked it to run the RUU. Any suggestions on how to get the RUU to run?
Ran the RUU again from the link that you sent me. Getting this info when running it:
FROM IMAGE VERSION: 3.10.605.7
TO IMAGE VERSION: 2.01.605.11
Guessing it going from 3.10 to 2.01 is the issue???
Kabish said:
Ran the RUU again from the link that you sent me. Getting this info when running it:
FROM IMAGE VERSION: 3.10.605.7
TO IMAGE VERSION: 2.01.605.11
Guessing it going from 3.10 to 2.01 is the issue???
Click to expand...
Click to collapse
so you are on the leaked ruu?
Apparently so...
I was sure I was on the OTA Stock one though, but apparently not, or I jacked things up trying to fix everything and flashed the wrong one.
I'm trying to go through post to downgrade my Mainver file. Thing is since I can't get into Recovery for whatever reason, and stupid ADB won't list my phone its making this difficult. I can run commands, example locking/unlocking but it won't let me shell in.
Kabish said:
Apparently so...
I was sure I was on the OTA Stock one though, but apparently not, or I jacked things up trying to fix everything and flashed the wrong one.
I'm trying to go through post to downgrade my Mainver file. Thing is since I can't get into Recovery for whatever reason, and stupid ADB won't list my phone its making this difficult. I can run commands, example locking/unlocking but it won't let me shell in.
Click to expand...
Click to collapse
try to run the leak again.relock, put the ph file on the root of your sd card, then run the file in hboot once. after that finishes, run it again.
http://androidcommunity.com/htc-rezound-android-4-0-ics-leaked-with-sense-3-6-get-it-now-20120316/
download the stock version. you need to be relocked to do this.
after that, unlock, flash a recovery, then proceed to install an ics rom, like clean rom or the many others out there.
after you flash the leak twice, and boot to the OS for the first time, it can take up to 10 minutes to boot up in some cases. be patient.
Ok, i'll give that a go...
If I'm reading that post right though it saying that is ICS?? I was not running ICS, I had tried ICS but it was too buggy for my taste so I flashed back my restore and kernel. I'm wondering if I accidently flashed the ICS PH98IMG file.
I'm willing to give it a go though... Its going to take for EVER to download that file though as its on Rapidshare and I'm getting an eta of 6hrs lol.
What really just gets me is that I've not touched my phone as far as rooting/updating since February. And out of the blue it decides to take a dump on me...
Kabish said:
Ok, i'll give that a go...
If I'm reading that post right though it saying that is ICS?? I was not running ICS, I had tried ICS but it was too buggy for my taste so I flashed back my restore and kernel.
I'm willing to give it a go though... Its going to take for EVER to download that file though as its on Rapidshare and I'm getting an eta of 6hrs lol.
Click to expand...
Click to collapse
ICS isn't that buggy especially after flashing a good rom. I actually have no bugs at all. Clean ROM is as stable as they come.
When you flashed the leak before, you lost the ability to fully revert back to pre leak status. you can however install a gb rom, but your radios ad such stay upgraded to the leak versions.
---------- Post added at 01:51 AM ---------- Previous post was at 01:48 AM ----------
Kabish said:
What really just gets me is that I've not touched my phone as far as rooting/updating since February. And out of the blue it decides to take a dump on me...
Click to expand...
Click to collapse
If its February, then you aren't on the leak. you just need to reset your main version I believe.
If I remember correctly my phone kept crashing on me. Granted this is when ICS first came out. I don't remember running an RUU though for ICS, however I did run one to get the OTA update.
I have a A500 tablet as well, which it is running ICS so I kind of get the two all mixed up when I think what I've done lol I've changed ROMS on my A500 so many times that my volume rocker is almost warn out
Found another host for the ICS Stock, it will be done in about 10 minutes.
Kabish said:
If I remember correctly my phone kept crashing on me. Granted this is when ICS first came out. I don't remember running an RUU though for ICS, however I did run one to get the OTA update.
I have a A500 tablet as well, which it is running ICS so I kind of get the two all mixed up when I think what I've done lol I've changed ROMS on my A500 so many times that my volume rocker is almost warn out
Found another host for the ICS Stock, it will be done in about 10 minutes.
Click to expand...
Click to collapse
ICS leak isnt in ruu format. perhaps thats why you dont remember it.
INSTALL:
- rename the downloaded leak file to “PH98IMG.zip” (no quotes)
– Place the renamed file onto the root of the SD Card
- relock your device
– Power down your device
– Reboot into the bootloader by holding VOL DOWN + Power
– The flashing process should begin automatically
- once complete, go back to bootloader and flash a second time.
I am a complete noob. Sprint Evo 3d 1.5 s-on, I have been running Viper IC3D for a month now, loving it,should have stuck with that. I wanted to try one of the Jelly Bean Roms, specifically the Team D.I.R.T. one, but I didn't want to have to keep flashing the two roms back and forth. Found out about Boot Manager Pro on here, and found a thread about using it with hboot 1.5 s-on. followed the instructions, booted into D.I.R.T. rom. fiddled with it, decided to go back to my phone rom. Boot Manager kept unexpectedly closing on me, wouldn't stay open long enough to do anything. So I went into recovery and restored my nandroid of Viper. But D.I.R.T. loaded! Said screw it, and wiped and reflashed Viper. D.I.R.T. loaded! Couldn't get anything but that ROM to load no matter what I did. Uninstalled Boot Manager, nothing but D.I.R.T.So I hunted around here and found a thread that said if all else failed, to manually remove Bootloader from sd and go from there. Did that, and it soft bricked my phone. I can get into recovery, but no matter what I do when I reboot it hangs in HTC white boot screen. I cannot afford another phone and don't get an upgrade til next year. Please Say there is a solution to this! I cried all last night, couldn't sleep, and I'm crying again. Side note, i accidentally erased half the C; Drive on my laptop trying things I found on another android forum,and system restore didn't work. So I'm back here, and I'm scared to try anything else, but I have to do something. Help!!!!!!
Flash the kernel. All will be well.
Viper rom should include boot.img.
Extract it to sdk-tools folder.
Open terminal, cd to sdk-tools directory.
Hold volume plus down on phone. Hit power button on fastboot option.
Plug in phone to computer. It should say fastboot usb on phone screen now. If not, install htc drivers.
Go to terminal. Type "fastboot flash boot boot.img
Should see some stuff happen on computer screen, phone will reboot.
Do that then report back.
Sent from my PG86100 using Tapatalk 2
can I do this using my rootevo3dnew package? I had a bad experience trying to install android sdk
You don't install sdk-tools. It's just a bunch if exe's in a folder.
That other thing you said, never heard of it.
Sent from my PG86100 using Tapatalk 2
Marta9227 said:
can I do this using my rootevo3dnew package? I had a bad experience trying to install android sdk
Click to expand...
Click to collapse
Yes you can, as long as you have fastboot and adb in there you'll be good, just put the boot.img in the same folder
Sent from my EVO 3DMA with a little "Common Sense"
please read my post carefully again and again it will solve your problem, I had the same problem
http://forum.xda-developers.com/showthread.php?t=1853065
I'm doomed. I was able to flash CWM this way, although it didn't help me at all. But I tried to flash the boot img and it didn't work. Didn't seem to recognize the command.
I'm cdma s-on? So basically you relocked and flashed an RUU and then relocked?
try to relock and flash with RUU it will work
At first when you were unable to boot back to phone rom, you should have went into recovery and flash the update.zip located in the sdcard/bootmanager/phonerom.
Anyway try to flash back to viperrom again then boot your recovery via fast boot since you are not s-off. And flash the update.zip from the phone rom folder. If everything fails just relock your bootloader and use the ruu.exe and you should be fine.
Marta9227 said:
I'm doomed. I was able to flash CWM this way, although it didn't help me at all. But I tried to flash the boot img and it didn't work. Didn't seem to recognize the command.
Click to expand...
Click to collapse
The command is: fastboot flash boot c:\(navigate to the sdk map with boot.img)\boot.img
For instance. for me it's c:\Users\(my name)\boot.img
Because i have my sdk and boot.img in my User map.
I believe boot manager creates the files for the second rom on the sd card. maybe thats why the D.I.R.T rom is loading.. My advice, try a different sdcard and see if the viper rom starts (you still might have to flash the boot.img via adb because of s-on)
I have no idea where the files for second rom are created so maybe if someone else could help out here. Then it should be a simple matter of deleting the second rom from the sd card and then go ahead and flash your viper rom.
http://init2winitapps.com/stories/BMManual.html
^^ this tell you all you need to know about dual booting.
Thanks to everyone! Relocked and ran RUU safely back to stock now debating if I have the guts to unlock again lol
Sent from my PG86100 using xda app-developers app
Do it!
Do it! The RUU will save you anyways lol
Should I do the stock ics ota first? I know that will make me hboot 1.58. Can I still HTC dev unlock 1.58? And can I get a new code? Didn't save the old one
Sent from my PG86100 using xda app-developers app
Yes you will have to get new code from htcdev. Though i wouldn't recommend updating hboot cause its known to cause some issues with some roms
first off, I'm an idiot with this whole thing and shouldn't be doing it probably. i just don't know enough about it to be playing with expensive phones like this so i understand I deserve whatever i get.
i was running a custom rom on an S-ON phone. i forgot the name of the rom (was made by TEAM COOL or something). But I wanted to unroot and go back to normal stock ROM and download the JB update. First, in the SU app, I did a complete unroot. that did nothing except not let me use the app anymore.
then I tried doing the RUU way of going back, but when it would go to the loading bootloader portion, the usb would disconnect and it would fail with error 171.
so then, and i don't know how i got here, but i went into recovery and did a factory reset and now i have no rom. I have tried installing meanrom but it fails after some line regarding a kernal. my phone won't do anything except boot to the white HTC screen or into the bootloader.
i have no idea what to do, I just want it working at this point.
i've been searching forums like crazy but all the solutions are things I already have done or things that won't work for me.
If you haven't done so yet, you need to relock the bootloader before running ruu. Put your phone in fastboot and using SDK or ADB Tools, type fastboot oem lock
om4 said:
If you haven't done so yet, you need to relock the bootloader before running ruu. Put your phone in fastboot and using SDK or ADB Tools, type fastboot oem lock
Click to expand...
Click to collapse
thank you for your help! however, whenever i do this, it just says < waiting for device >
so i finally got a rom to install--clean rom. that is the one i used to have. but when i reboot, it gets stuck on a black screen and won't go any further.
I had the same thing happen. Had to run a boot.img flash utility i found on another thread elsewhere on xda. The flash utility was updated for jb. If i can locate where i found it then i will get back to you.
Sent from my EVO using Tapatalk 2
I was curious if you ever found that rom or if anybody can help me? The phone is still out of commission. It's been tough to make it through the holidays especially since my laptop was stolen the very next day that all this happened
bump again. I'm assuming the phone is bricked for good if the brightest minds on the subject don't even know
i'm using my dad's old evo 4g for now.
unclefarkus said:
bump again. I'm assuming the phone is bricked for good if the brightest minds on the subject don't even know
i'm using my dad's old evo 4g for now.
Click to expand...
Click to collapse
Have you tried meanbean? It has the boot.img flash tool baked in for s-on, just follow the instructions to the tee in the OP... It's in the Android development thread... Good luck
Sent from my EVO using xda app-developers app
Sounds like you need to flash a Rom that has the s-on installer or fastboot flash the kernel for the Rom you have installed
Most roms come with the kernel installer built in now days. just keep trying to flash em. fyi if your phone turns on , even a little bit , you are not bricked
I am trying to flash meanbean. I wiped the cahes and did factory reset, then flashed the ROM. It's been on "Installing /system..." for about 30 minutes now. Something seems wrong. I'm scared to interrupt it in case that's normal or if interrupting it will break it for good.
Well, I think that might be because my twrp version is really old...2.1.8. I tried updating but had no luck.
Now nothing flashes. It gets to 'verifying partition sizes' then fails. Tried this on several roms that would previously flash, just not work.
unclefarkus said:
Well, I think that might be because my twrp version is really old...2.1.8. I tried updating but had no luck.
Now nothing flashes. It gets to 'verifying partition sizes' then fails. Tried this on several roms that would previously flash, just not work.
Click to expand...
Click to collapse
Update twrp through goomanager, its in the market, then try again.
Sent from my EVO using xda premium
mrlakadaddy said:
Update twrp through goomanager, its in the market, then try again.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
lol how could he do that if he dont have any rom installed...dafuq?
You need to FASTBOOT install it:
Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery TWRP.img
Boatiy said:
lol how could he do that if he dont have any rom installed...dafuq?
You need to FASTBOOT install it:
Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
Don't forget the clear cache commands
Sent from my EVO using xda app-developers app
I have given this a go, however, as I should expect by now, nothing happens.
It says "waiting for device" and that's it
Upon typing "adb devices" nothing shows up.
Furthermore, when I go to Fastboot, Fastbook usb does show up, but I get a message on the computer saying the usb device has malfunctioned.
unclefarkus said:
I have given this a go, however, as I should expect by now, nothing happens.
It says "waiting for device" and that's it
Upon typing "adb devices" nothing shows up.
Furthermore, when I go to Fastboot, Fastbook usb does show up, but I get a message on the computer saying the usb device has malfunctioned.
Click to expand...
Click to collapse
Can you get into bootloader? If so go to the TWRP website and download the hboot zip. Put on external sd card and enter bootloader.
Sent from my EVO using Tapatalk 2
Perhaps what is happening when you try oem lock and get that error is that adb is still running from a prior attempt or because of some other program. Try opening your task manager and ending all processes of adb and other programs that connect to the phone. Then try oem locking again and go from there.
Sent from my EVO using xda premium
I made a little bit of progress!
I determined that Windows 8 was the reason I get the usb malfunctioning message. I obtained a Windows 7 computer and it worked like a charm.
That said, I'm not out of the woods yet.
I relocked the phone using fastboot and then have been attempting to flash a stock RUU now that the usb issue is sorted out.
That seems to work but it gets stuck at "sending....." for as long as 35 minutes. I've tried about 4 times, giving between 20-35 minutes and it won't go beyond sending.
I can at least fastboot now; but the phone is locked. Which is fine; I just want back to stock anyways.
Tampered
Re-locked
S-On
Hboot-1.19.0000
Radio-1.12.11.0809
OpenDSP-v29-1.0.45.0622
eMMC-boot
Aug 9 2012
I flashed the 2.13.651.1 RUU by the way.
Any new advice haha?
I loaded a PJ img via sd card and it's alive and updating to JB OTA right now! Thanks for all the help over the past month folks
I have a rezound that is now semi-broken. I've got Arman's recovery, but I can't seem to flash anything. I'm really hoping someone can help me out!
I have an hboot that says tampered, unlocked hboot,
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12, 2012 16:47:46
This whole thing is acting weird, and I've been working on it for a few hours. I can't seem to get a rom actually working. Maybe I'm not waiting enough, but I left it there for five minutes on the boot screen and it did nothing. I've tried both OTA superstock and Ecliptic, neither to any avail.
Fastboot is being a *****. I've tried everything I can to get fastboot to work, and it will not. It just simply wont work. So I'm hoping someone has some ideas, because I would really like to make sure this isn't my first real brick. plz <3
What commands are you using? And what files are you trying to flash?
Sent from my HTC Rezound using Xparent Skyblue Tapatalk 2
I can help you with Ecliptic, which should have just been a simple reboot to hboot after rom flash and then normal reboot. What exactly is occurring? Are you getting "mainver is older" error?
I've tried flashing both hboot_7230ddr2_Runnymede_1.28.0006_20120424 and supermisc - and at this point, I believe the partition tables are borked. I currently have amonra for the recovery, and now when I try and install zip from sdcard it gets all lame and says it cannot mount it. I think what needs to happen first is through ADB I need to find a way to flash a full RUU or something. It used to have 4.03 on it, so I know I'm not far away from success.
oh and at no point has flashboot oem lock ever worked. No Flashboot command has ever responded with anything. I have uninstalled all HTC drivers, removed Sense, and installed just the revolutionary drivers, and they still don't work.
Win 7 x64 -
If the phone boots to hboot fine you should be able to get the ph98img ruu for 605.12 and put that on your SD card and have it reflash your phone. It will fix partition problems as well. Can you try that and report back?
Sent from my ADR6425LVW using Tapatalk 2
@cellularticulate
Going by your info in post #4 it sounds like your trying to flash stuff meant for the Sensation XL. You can't do that, also to add you are s-on and if you try to load an eng hboot you WILL brick.
Run through this PH98IMG RUU in bootloader mode.
http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Snuzzo said:
@cellularticulate
Going by your info in post #4 it sounds like your trying to flash stuff meant for the Sensation XL. You can't do that, also to add you are s-on and if you try to load an eng hboot you WILL brick.
Run through this PH98IMG RUU in bootloader mode.
http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Click to expand...
Click to collapse
And make sure you allow the RUU to complete, it will run through twice. It will go to a black screen for several seconds and then it will start over again. Make sure you don't interrupt it. Iirc, it will end up in bootloader when it's done, or maybe it reboots the phone.
It will only run through once, hboot and radio versions will match.
Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
I need to fix the sd card permissions, I think. I will try flashing the RUU. I'm supposed to rename it and place it on my sdcard, and then just boot into hboot? It just...starts...automatically?
cellularticulate said:
I need to fix the sd card permissions, I think. I will try flashing the RUU. I'm supposed to rename it and place it on my sdcard, and then just boot into hboot? It just...starts...automatically?
Click to expand...
Click to collapse
If the ph98img is correct it (hboot) will detect it and prompt you to press up to start the update....
Sent from my Nexus 7 using Tapatalk HD
So I think I just realized why this has been a catastrophic failure this entire time. It's supposed to be on an EXTERNAL sd, right?
cellularticulate said:
So I think I just realized why this has been a catastrophic failure this entire time. It's supposed to be on an EXTERNAL sd, right?
Click to expand...
Click to collapse
Lol...yup...the small things get ya. Good luck finishing it up tonight. Finish ruu, unlock, flash custom recovery (I prefer the ph98img version of recoveries most of the time). Then load whatever ROM you want from recovery -or- continue rooting/setting up the stock ota ROM.
Sent from my Nexus 7 using Tapatalk HD
I still dont know why fastboot never worked :\ But yeah. That's literally all it was. The external SD card vs internal. I wish that was clarified somewhere. But I guess I know this going forward now!
I've got the RUU re-flashed, but I'm still stuck at the ecliptic boot screen. Ill try and do a fix permissions and see if that works.
cellularticulate said:
I've got the RUU re-flashed, but I'm still stuck at the ecliptic boot screen. Ill try and do a fix permissions and see if that works.
Click to expand...
Click to collapse
If you are stuck at the boot screen it's likely you don't have the correct kernel flashed for that rom. Did fastboot ever work for you? If not, do you have a ph98img version of the kernel for ecliptic? Snuzzo will probably chime in here shortly since i think that's his kernel...
I do not have a zip of his kernel, and fastboot still doesn't work. When I try and flash twrp and gives the mainver is old error, and I don't have time to fix this before work. Hopefully someone gives me golden advice and I can get this thing fixed. Three days now :\
Snuzzo, I know you don't do this specifically for money, but I will be donating to you. You've been a huge help.
you as well dottat.
One thing that's strange is I still think my partitions are messed up. I tried using the misctool to write an image to /sdcard2 and no matter what I tried, I couldn't find it. What's strange is when I'm in a shell, it shows this really, really weird login, and keeps kicking me OUT of the shell every couple of minutes. I'm going to try and switch back to TWRP since that what was on this phone when I got it. And yes, the phone was in working condition, things have just inherently gotten worse. http://puu.sh/2XtmZ.png
<3 y'all
OK what status are you at currently and why are you trying to flash that particular partition? Youre getting mainver is older? Hmmmm
You still got the latest twrp on here? If so, flash erez v9 then flash this
http://d-h.st/FZc
That's a dual purpose kernel zip. Do a fresh kernel flash with it. It should also set your mainver properly.
Sent from my Nexus 7 using Tapatalk HD
cellularticulate said:
I do not have a zip of his kernel, and fastboot still doesn't work. When I try and flash twrp and gives the mainver is old error, and I don't have time to fix this before work. Hopefully someone gives me golden advice and I can get this thing fixed. Three days now :\
Snuzzo, I know you don't do this specifically for money, but I will be donating to you. You've been a huge help.
you as well dottat.
One thing that's strange is I still think my partitions are messed up. I tried using the misctool to write an image to /sdcard2 and no matter what I tried, I couldn't find it. What's strange is when I'm in a shell, it shows this really, really weird login, and keeps kicking me OUT of the shell every couple of minutes. I'm going to try and switch back to TWRP since that what was on this phone when I got it. And yes, the phone was in working condition, things have just inherently gotten worse. http://puu.sh/2XtmZ.png
<3 y'all
Click to expand...
Click to collapse
If you let the RUU fun fully and you still have ecliptic boot screen showing you either didn't let the RUU fun fully or something really wonky is going on.. If you let the RUU run fully, you should have a stock rom booting by itself. Can we at least get to that point? We can probably get you around it. .but i would feel better starting from a fresh RUU.
Snuzzo said:
OK what status are you at currently and why are you trying to flash that particular partition? Youre getting mainver is older? Hmmmm
You still got the latest twrp on here? If so, flash erez v9 then flash this
http://d-h.st/FZc
That's a dual purpose kernel zip. Do a fresh kernel flash with it. It should also set your mainver properly.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
@Snuzzo - what's erez v9? tried googling. Didn't see it in the guides on here either.