[Q] Help, I think that I bricked my phone using Revolutionary process - Thunderbolt Q&A, Help & Troubleshooting

Help, I was following the Revolutionary process on the youtube video. I got to S-OFF, but it wouldn't let me load the recovery program and now Revolutionary won't see my phone. I had an update .IMG on the SD card, which I removed by letting the phone re-install the update and then deleting it via USB. I still have S-Off, and the SU file is on my SD car, but I never renamed it. How can I fix this? I don't know how to use adb and my SD card is read-only when I put it into my laptop. If I go into recovery or fastboot I just get the phone triangle ! icon.
Am I ****ed? If so, how hard?
Thanks!
What my boot screen says:
-Revolutionary-
MECHA XD Ship S-OFF
HBOOT-6.04.1002
Microp-/
RADIO-1.48.00.0906w_1
eMMC-boot
Feb 23 2011,20:42:55
HBOOT (Blue)
Vol up
Vol down
Power
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
HBOOT USB
IMAGE CRC

Never mind fixed it
Never mind, I got in, removed the file, got the recovery working and it's looking like it's still a phone and not a paperweight.

Related

Help on Rezound please

OK.. Brand new Rezound. I used Hasoon's All-In-One Kit and I was able to unlock and install the CWM (GB). But I was unable to do anything else. I am looking to just get Root for some programs I like.
But now I thing something went terribly wrong when I tried load a new PH98IMG.zip. I got in the bootloader (power+vol down) and I see:
**** Unlocked ****
Vigor PVT SHIP S-ON RL
HBOOT-2.11.0000
RADIO-0.95.00.1118r/0.95.00.1223r
OpenDSP-v10.6.0.7611.00.0919
eMMC-boot
Oct 6 2011, 15:43:22
Memory Card contents: PH98IMG.zip, GB Firmware Patch.zip and Vigor_Stock_Doedexed_3.14.605.5.zip
**Note: I have yet to register this phone with Verizon**
At startup, with the memory card in it will allow me to boot into a screen called HBOOT where I can select FastBoot, Recovery, etc.. It then starts the upgrade process and says Done! so I reboot. After the second HTC screen flashes the screen goes blank and does nothing else.
I removed the memory card and attempted a Factory Reset, but nothing seems to work.
Thoughts? Help?? I am new at this but was successful on my previous Rezound so I am not sure whats going on here.
Appreciate it.
OK. Loaded Vigor and the GB Firmware but not PH98IMG.zip to the SD Card and used Recovery to flash.
Rebooted the phone and am now at the 4GLTE screen. Hoping it gets further, but now that I have gotten there, should I use the Bootloader to run PH98IMG.ZIP?
*** UPDATE ***
Ok.. I went ahead and copied the PH98IMG.ZIP and updated via bootloader and it all works now.. Wow.. What a pain in the arse!!

[Q] EVO 3D GSM boot loop after ics ruu

Sorry to bother, I was to post this last night, then I tried a bit more and failed, I really need help now!
htcdev unlocked Evo 3D GSM(shooteru)
HBOOT shows below:
SHOOTER-U PVT SHIP S-ON RL
H-Boot-1.49.0018
eMMC-boot
I have been through and still in this mess since last afternoon, totally noob at the beginning, so forgive my stupid mistakes please.
1. I tried to use cwm v4.0.1.4 to flash the cm9-20130310-nightly-shooteru.zip (with gapps-ics-20120429-signed.zip)into the phone, and wiped cache and data before install zip. But after the installation, the phone just stuck at the HTC logo screen, fastboot mode and cwm are still available.
2. Flash in the boot.img but no luck.
3. Tried the official RUU_SHOOTER_U_ICS_35_S_htc_Asia_HK... but error 155 was reported.
4. Then I do some google and drag the rom.zip file from the RUU, renamed it to PG86IMG.zip and copied it to my SD card. FASTBOOT loaded the file, but the situation doesn't change a bit.
5. Google again, change my CID according to the android-info.txt extract from the ruu rom, relock the phone, and the RUU installed successfully, at least it looks like that at the moment, but it comes out that it just stay in boot loop.
6. Now I dont even have the official recovey(also boot loop), unlocked it again thru htcdev, tried to flash in the cwm touch v5.8.0.2 for shooteru, did not work. So status right now is unlocked, s-on, hboot 1.53.0007, no recovery, keep rebooting.
7. Exhausted and frustrated, I come here for any help. It's driving me crazy now, 'cause this is a friend(a girl indeed)'s phone.
I really need your help, pls!
Appreciate any relate information and concern in advance!
#################################################
rerun the ruu and set to the factory mode in hboot, problem solved!
forgot to mention
I don't know if this still matter though, I can see the cm9 robot screen after the RUU install failed in the step 3 because of wrong cid, but it stuck about 20 minutes, so I changed to the RUU method.
I think you have to be on an hboot 00007
花、不凋落っ said:
I think you have to be on an hboot 00007
Click to expand...
Click to collapse
thank you, I found out this and solve the problem by reinstall from the ruu, forgot to delete my post.

[Q] Evo 3D weird bootloop

-Unlocked-
SHOOTER_U PVT SHIP S-OFF RL
HBOOT-1.49.007
RADIO-11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
So the problem here is that my Evo 3D GSM bootloops no matter what i flash. I can get in to HBOOT and Fastboot but can't get in to recovery, or boot a rom. I tried flashing various versions of cwm and 4EXT and none seem to work. I boot to HBOOT select recovery but it just goes back to bootlooping. Tried flashing various roms (had Viper3D for like a month and then one night it started bootlooping), even tried flashing a RUU multiple times but the bootloop goes on. And since that didn't help i unlocked again and downgraded HBOOT. For a period of time the phone didn't boot but that was because the battery is drained and can't charge when off, so I'm using a Desire X battery.
Before flashing RUU
-Revolutionary-
SHOOTER_U PVT SHIP S-OFF RL
HBOOT-1.49.1107
RADIO-11.25-3504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
Any ideas would be helpfull.
I don't know what ruu you need, but you need to make sure its right.
Then without hooking your phone up, run ruu on windows.
Let it load up, the go to run and type %temp%
In the window that pops up, look for the newest folder, that will contain a file named rom.zip drag it to your desktop.
Rename it pg86img.zip
Now, you need to get that file to the root of your sd card, use a card reader, another phone, something.
Make sure it is the only pg86img.zip on your card.
Once you have the pg86img.zip on your sd, put it back in your EVO, and boot to bootloader. Accept the update and it should do the rest.
Do no relock before you do this. It is not necessary.
When you finally get booted remove that file or rename it.
Hope that gets you going
Sent from my HTCEVOV4G using xda app-developers app
Sorry for taking so long to reply, didn't have the time until now. I tried your method and it still didn't work
Though this I might try but I'm not too cozy with having to brick my device and i have no Linux experience. Not much else I can try...
Also is there a way to get back S-ON, because a while ago I sent the phone to repairs but they rejected my warranty because of s-off and revolutionary. Is my warranty still valid even if I revert back?
are you sure recovery is flashed ok? drivers may be the issue. try reinstalling drivers and running RUU or flashing recovery

[Q] stock Rezound won't boot after RUU, stuck on white HTC screen

My wife's Rezound just stopped working last week, and Verizon has said "lotsa luck," so I'm wondering if anyone here can help me.
Phone was bone-stock, unrooted, and it says S-ON. I have no idea what OTA updates it had (sorry!)
The phone would only get to the white HTC screen and would freeze, so with tech support I tried to do a factory reset from HBOOT. Nothing too important on the phone, so losing all data is not a huge deal.
But in the process it would show a green circle logo, and then a moment later would change to a red triangle logo and then reboot (and subsequently freeze at the white HTC screen). <--this is where VZ tech bailed.
So I put the 4.03.605.2 RUU from androidpolice on the SD card as a PH98IMG.zip, and HBOOT would recognize it, "verify" it, and then state "Main Version is Older! Update Fail!"
Next, I downloaded 4.05.605.14 from this http://forum.xda-developers.com/showpost.php?p=40949419&postcount=11 thread (and verified the md5). I did the same thing: put it on SD card, booted, and waited. It checked the image (with the blue bar on the upper right), then verified the image (with the yellow bar), and then went straight to HBOOT. I used fastboot, and then "reboot bootloader" to open HBOOT again, and it did the same check and verify steps.
Things were looking up at this point, so I tried booting the phone, but it just got stuck at the white HTC screen again. So I pulled the battery, rebooted into HBOOT, went into fastboot. I unzipped the RUU file on my computer, copied the boot.img into the folder (on the computer) with fastboot, and then tried "fastboot flash boot boot.img" from the command prompt. It said "sending 'boot' OK", then "writing 'boot' signature checking... FAILED (remote: signature verify fail) finished."
I'm admittedly not very familiar with the process at all, but I'm pretty frustrated that this hasn't worked at this point. My hope was that putting the latest RUU on the device would fix any problems with the software. At this point my only goal is to get it booted into a usable state. Any ideas?
Thanks in advance!
for what it's worth, HBOOT lists this information:
Code:
***LOCKED***
VIGOR PVT SHIP S-ON RL
HBOOT-2.28.0000
RADIO-2.21.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7700.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
According to what you listed for your hboot, it looks like you were already at 4.05.605.14. (One weird thing though is what you have listed in the beginning of the Radio. Yours is saying: 2.21.10.0123r and it should be 2.23.10.0123r.) But unfortunately with S-on, you are stuck and cannot go back to the 4.03.605.2 like you were trying or anything earlier. I am no expert but I am pretty sure that in order to use that download, you must replace the stock recovery and install a modified recovery such as AmonRa (my favorite) or TWRP. Then you use the modified recovery to flash that 4.05.605.14 rooted zip file. But in order to install the modified recovery, you must have an unlocked bootloader so you have to unlock the bootloader. And you may have to extract the boot.img file and flash that using adb flashboot commands with the phone in flashboot usb and attached to your computer before flashing the whole zip file in the modified recovery.
So use the HTCdev site to unlock, then put AmonRa on the device, then try the RUU again. Got it, I'll give it a try in the morning. Thanks!
And, after double-checking, I had two typos:
RADIO-2.23.10.0123r,
and OpenDSP-v14.6.0.7708.00.0507.

[Q] Can't Load ROM on HTC One

Ok, to say up front I forgot to upload the ROM to the phone's storage FIRST.
Here are the steps I took today:
Today I received my new HTC One
I unlocked the Bootloader from HTCdev.com website - everything went smooth
I downloaded a custom ROM and flashed boot.img and 43_twrp_recovery.img
I loaded TWRP recovery and I thought I could mount a drive letter to upload the ROM, Seems I can't do that and these phones doesn't have a external sd card available.
Evidently after the fact I was told I shouldn't of flashed the boot.img and the phone will not boot but instead restarts after a minute or two. (This is my problem, I can enter recovery but I can't get the phone back to a working order)
I was instructed by someone to do the RUU but when I try it connects to the phone, displays the version and I choose to Upgrade the ROM. It reboots the phone into Bootloader with a black background with white htc lettering. From there it does nothing, I left it for over an hour with 5% progress. I unhooked the usb cable and the phone showed a error "loading zip into fail! update fail!"
The RUU I tried to load was this below, the phone is an AT&T HTC One 32GB
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
I can still get into TWRP recovery, fastboot and bootloader just fine. I tried by recommendation to transfer the file via adb.exe but it keeps showing an error, can't connect to phone.
Here is the info on fastboot screen
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
Oct 4 2013,00:49:44.1770
The device is recognized in fastboot using "fastboot.exe devices".
I am seriously at a loss right now and need dire help if anyone has any recommendations.
Thank you in advance for your time in reading this!
cybernine said:
Ok, to say up front I forgot to upload the ROM to the phone's storage FIRST.
Here are the steps I took today:
Today I received my new HTC One
I unlocked the Bootloader from HTCdev.com website - everything went smooth
I downloaded a custom ROM and flashed boot.img and 43_twrp_recovery.img
I loaded TWRP recovery and I thought I could mount a drive letter to upload the ROM, Seems I can't do that and these phones doesn't have a external sd card available.
Evidently after the fact I was told I shouldn't of flashed the boot.img and the phone will not boot but instead restarts after a minute or two. (This is my problem, I can enter recovery but I can't get the phone back to a working order)
I was instructed by someone to do the RUU but when I try it connects to the phone, displays the version and I choose to Upgrade the ROM. It reboots the phone into Bootloader with a black background with white htc lettering. From there it does nothing, I left it for over an hour with 5% progress. I unhooked the usb cable and the phone showed a error "loading zip into fail! update fail!"
The RUU I tried to load was this below, the phone is an AT&T HTC One 32GB
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
I can still get into TWRP recovery, fastboot and bootloader just fine. I tried by recommendation to transfer the file via adb.exe but it keeps showing an error, can't connect to phone.
Here is the info on fastboot screen
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
Oct 4 2013,00:49:44.1770
The device is recognized in fastboot using "fastboot.exe devices".
I am seriously at a loss right now and need dire help if anyone has any recommendations.
Thank you in advance for your time in reading this!
Click to expand...
Click to collapse
Use my encrypted rom.zip here
http://forum.xda-developers.com/showthread.php?t=2695749
clsA said:
Use my encrypted rom.zip here
http://forum.xda-developers.com/showthread.php?t=2695749
Click to expand...
Click to collapse
I'll give this a try as well, Im in the say boat as the Op, but my Hboot is 1.44..
cybernine said:
Ok, to say up front I forgot to upload the ROM to the phone's storage FIRST.
Here are the steps I took today:
Today I received my new HTC One
I unlocked the Bootloader from HTCdev.com website - everything went smooth
I downloaded a custom ROM and flashed boot.img and 43_twrp_recovery.img
I loaded TWRP recovery and I thought I could mount a drive letter to upload the ROM, Seems I can't do that and these phones doesn't have a external sd card available.
Evidently after the fact I was told I shouldn't of flashed the boot.img and the phone will not boot but instead restarts after a minute or two. (This is my problem, I can enter recovery but I can't get the phone back to a working order)
I was instructed by someone to do the RUU but when I try it connects to the phone, displays the version and I choose to Upgrade the ROM. It reboots the phone into Bootloader with a black background with white htc lettering. From there it does nothing, I left it for over an hour with 5% progress. I unhooked the usb cable and the phone showed a error "loading zip into fail! update fail!"
The RUU I tried to load was this below, the phone is an AT&T HTC One 32GB
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
I can still get into TWRP recovery, fastboot and bootloader just fine. I tried by recommendation to transfer the file via adb.exe but it keeps showing an error, can't connect to phone.
Here is the info on fastboot screen
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
Oct 4 2013,00:49:44.1770
The device is recognized in fastboot using "fastboot.exe devices".
I am seriously at a loss right now and need dire help if anyone has any recommendations.
Thank you in advance for your time in reading this!
Click to expand...
Click to collapse
Bootloader needs to be relocked to flash a ruu.exe with s-on
Says
C:\Android>fastboot flash zip Rom.zip
load_file: could not allocate 1556101543 bytes
error: cannot load 'Rom.zip': Not enough space
Dafuq?!
I wanted to give an update on the situation and a resolve to the issue.
I finally got the problem resolved by the help of a friend (wildchild).
I ended up downloading another RUU that matched my current version (3.17.502.3). I locked the bootloader and flashed using RUU in HBOOT. That process went through successfully and got the phone restored back to factory.
I unlocked the bootloader and phone went back to factory again!
I enabled WiFi to do a OTA update to 4.19.1540.9
Once that was completed I transferred the custom ROM to the internal storage of the phone.
Booted into recovery and done a backup using twrp recovery. I copied that to my PC just in case.
Booted back into twrp recovery and wiped the data and installed the custom ROM, took about 10 minutes or less to boot the OS. Finished!
Wanted to thank everyone who posted suggestions and for the help. Basically I took the same road as what cLsA had suggested, I believe either way would have gotten me the same results except I may have taken a longer road. Thanks for the RUU ROM cLsA, I'll save it for later !

Categories

Resources