Related
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 cannot get into regular bootloader. It just either sits and stalls, goes to HTC screen, or just straight to recovery. This has happened on and off before but I was always able to get it after a few tries. I've been trying for 2 days since the new ICS was released by Sprint but it's been no go.
I believe I have 1.5 Hboot, but I can't tell for sure because I can't access it. I had to take the long route when I had to root with the HTC unlock thing, etc.
I've tried to get to HBoot using QuickBoot app and using the menu option within TWRP 1.1 and now 2.2 (thought that might be the problem, but guess not)...still just stalls and nothing happens after reset
I've been using only rooted OTA's on my phone and only rooted for bloatware removal and wifi tether. No custom roms. No ICS leak.
The buttons of course work. As soon as I take my finger off of the Down volume button, the phone will activate and boot up normal in some cases.
I don't know if this is causing other issues with my phone as it self reboots or freezes a few times a week. I was looking forward to ICS update because I was hoping it would fix the reboots and freezing. Everything else works fine with the phone.
Any help would be greatly appreciated.
try "adb reboot bootloader" and see if your phone gets into bootloader.
mnomaanw said:
try "adb reboot bootloader" and see if your phone gets into bootloader.
Click to expand...
Click to collapse
Don't you have to be in Bootloader to get the adb commands to work? I tried using fastboot to connect and no go.
brokenmouse said:
Don't you have to be in Bootloader to get the adb commands to work? I tried using fastboot to connect and no go.
Click to expand...
Click to collapse
Look under settings/battery or power saver and uncheck fastboot?
Then you can actually get into hboot.
AFAIK, adb commands work in android, fastboot commands work in bootloader.
just make sure USB DEBUGGING is checked in settings.
When that happens to me, I remove the battery for about a minute, put it back in, hold down volume down, then hold power. It will boot right to bootloader.
Save the Drama for your Mama with Tapatalk 2
coal686 said:
When that happens to me, I remove the battery for about a minute, put it back in, hold down volume down, then hold power. It will boot right to bootloader.
Click to expand...
Click to collapse
This caused a lot of trouble for me trying to flash MeanRom and Tribulattifather's ICS OTA with 4EXT because it kept trying to go into bootloader after the install to do the "smart install" or whatever. The phone would just black out upon reboot and sit there or if I tried doing bootloader manually, it would go straight to recovery again. I was up until 4 in the morning trying to get my phone to fully boot last night...never did.
Brought my phone to work today and left it off nearly all day. I thought I was seriously screwed and would have to do a RUU update/unbrick from work. Lo and behold it went into bootloader first try.
I'm restoring a backup now through TWRP 2.2 (because it doesn't have the smart install feature). We'll see if
What do you think is causing these problems? I don't want anything crazy...just a solid ICS rom or rooted OTA. Most ROMs I read suggest using 4EXT to flash, but I'm afraid of running into this again. Any suggestions or thoughts?
as mentioned above, installed the TWRP 2.2 from bootloader and restored a backup (that worked a long time ago). Now i'm having the same issue I had last night. It won't boot up at all except to recovery again.
For most people, being s-off is the best thing to do. S-on and ICS tend to bootloop. For some reason, 4ext and flash image GUI don't seem to work well in ICS either for some.
Have you tried flashing a GB ROM?
Save the Drama for your Mama with Tapatalk 2
I'm going to have to figure out how to get back to complete stock. Everytime I flash a rom...doesn't matter what it is, the phone will say the flash is done, then reboot to...NOTHING...just a black screen. I've let it sit and nothing happens.
Followed a guide on androidcentral that had a nice restore to stock guide. Did the RUU from my computer and now it's acting normal again. It must've been really messed up because when I had it talking to ADB and did the reboot reloader command (as someone stated), the screen was solid black, though the RUU still saw it.
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
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.
I did this a while ago because i was going to try rooting, then changed my mind. Anyway, no I'll effects, until recently when, T-Mobile pushed out a software update. Tried doing the update (numerous times), but nothing happened. Called T-Mobile; no help. Forgot about it since I read it was a minor update. Anyway, since my phone had been using up batteries very fast, I decided to do a factory reset. Strangely, this did not work either. Again t-mobile ; no help. Then got the idea to unlock the boot loader again and see what happens. That worked. Was able to wipe the phone. Then with the bootloader unlocked, I again attempted to do the software update. Phone rebooted and went right into 4ext recovery and after the update failed at first, giving me a message that the ext. Sd card could not be found. I used 4ext to mount the ext SD, which was not mounted. The update successfully completed. Apparently, with the phone in relocked state, many things seem to be not possible.
joep229 said:
I did this a while ago because i was going to try rooting, then changed my mind. Anyway, no I'll effects, until recently when, T-Mobile pushed out a software update. Tried doing the update (numerous times), but nothing happened. Called T-Mobile; no help. Forgot about it since I read it was a minor update. Anyway, since my phone had been using up batteries very fast, I decided to do a factory reset. Strangely, this did not work either. Again t-mobile ; no help. Then got the idea to unlock the boot loader again and see what happens. That worked. Was able to wipe the phone. Then with the bootloader unlocked, I again attempted to do the software update. Phone rebooted and went right into 4ext recovery and after the update failed at first, giving me a message that the ext. Sd card could not be found. I used 4ext to mount the ext SD, which was not mounted. The update successfully completed. Apparently, with the phone in relocked state, many things seem to be not possible.
Click to expand...
Click to collapse
You must have done something wrong I was on ARHD then I relocked bootloader and ran the stock ruu then booted up and downloaded and installed the update. All worked first time no issues at all.
Sent from my HTC_Amaze_4G using xda app-developers app
dntipwn said:
You must have done something wrong I was on ARHD then I relocked bootloader and ran the stock ruu then booted up and downloaded and installed the update. All worked first time no issues at all.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for the response, but can't imagine what I could I have done wrong? All I did when trying to install the update was click the 'update now' box. phone simply rebooted to recovery and did nothing else. Navigated to 'reboot'. Phone rebooted and update was still there un-installed. Checked software version; unchanged. When trying to do system restore, tried it from security menu and also tried booting direct to recovery. Highlighted 'system restore', pushed power button. Both ways and the phone simply rebooted with everything still intact!!
P.S. Didn't know ARHD works with Amaze 4g? Would love to try it, but a little anxious about doing wire thing to get to s-off. It's my only phone. Is it risky?
joep229 said:
Thanks for the response, but can't imagine what I could I have done wrong? All I did when trying to install the update was click the 'update now' box. phone simply rebooted to recovery and did nothing else. Navigated to 'reboot'. Phone rebooted and update was still there un-installed. Checked software version; unchanged. When trying to do system restore, tried it from security menu and also tried booting direct to recovery. Highlighted 'system restore', pushed power button. Both ways and the phone simply rebooted with everything still intact!!
P.S. Didn't know ARHD works with Amaze 4g? Would love to try it, but a little anxious about doing wire thing to get to s-off. It's my only phone. Is it risky?
Click to expand...
Click to collapse
Well I'm pretty sure that with the locked bootloader and stock Rom there won't be any issues I was not rooted or any of that. And I'm not S-off. I didn't mess with any of that wire crap just make sure you have 4ext recovery and have smart flash enabled in the options and you can flash all the Roms you want. Just make sure before every Rom flash you make sure the smart flash is enabled unless you configure it to stay on.
Sent from my HTC_Amaze_4G using xda app-developers app
My strange problems are continuing. Yesterday I was finally able to do a factory reset and update the software on my phone. Now for some strange reason, I can no longer enable WiFi or Bluetooth. It's as if since I told T-mobile that I had unlocked, and relocked my phone, they sent a signal to my phone to totally screw it up.!!!
joep229 said:
My strange problems are continuing. Yesterday I was finally able to do a factory reset and update the software on my phone. Now for some strange reason, I can no longer enable WiFi or Bluetooth. It's as if since I told T-mobile that I had unlocked, and relocked my phone, they sent a signal to my phone to totally screw it up.!!!
Click to expand...
Click to collapse
Ok well what i would do in this situation would be to just start over fresh. First download the newest ruu we have from here for tmobile: http://forum.xda-developers.com/showthread.php?t=1617644, which would be this one: RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip and make sure you rename it PH85IMG.zip and place that on your externel sd card. Once you do that make sure you phones boot loader is locked (i use hansoons tool kit for all this) once boot loader is locked (says relocked) then you can boot into I think its called hboot (the screen where is says locked/relocked/unlocked/) by powering phone off then pushing Vol down key and power at the same time and hold it will bring you to a screen where it will start reading the file you just put on you sd card and ask if you want to update. Vol up for yes and vol down for no select yes and it will do its thing and it will ask to press power button to reset and the will boot up to stock ICS and everything should work fine.
Thank you so much. Actually had to do it a little differently. Downloaded the ruu and renamed it. Put it in the data subfolder of all-in-one kit. Used Hasoon's to reboot to bootloader. Then flashed the ruu using Hasoon's. Same thing, I guess. Anyway, everything works now. I put the PH85IMG.zip in the root of the sdcard. any idea why rebooting to the bootloader did not find it and start the flash? Says PH85IMG.zip not found.
dntipwn said:
Well I'm pretty sure that with the locked bootloader and stock Rom there won't be any issues I was not rooted or any of that. And I'm not S-off. I didn't mess with any of that wire crap just make sure you have 4ext recovery and have smart flash enabled in the options and you can flash all the Roms you want. Just make sure before every Rom flash you make sure the smart flash is enabled unless you configure it to stay on.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
dntipwn - you said you didn't mess with the wire crap. Were you able to flash ARHD to your phone with s-on? Can you give me some tips?
joep229 said:
dntipwn - you said you didn't mess with the wire crap. Were you able to flash ARHD to your phone with s-on? Can you give me some tips?
Click to expand...
Click to collapse
Yes all you have do is first unlock bootloader, then you will need to flash a 4ext recovery, after that root is needed. The easiest way its to use hansoons tool. After all that our done you will need to download super wipe.zip from the arhd page and the room of choice I actually get better battery on NRG stock rom. Boot into recovery flash super wipe it will reboot then flash the rom reboot which will take about 5 to 10 mins. After it boots up I like to let it sit without touching it for 10mins reboot then set up the phone then reboot again and you should be set.
Sent from my SCH-I905 using xda app-developers app
The key of you are s-on is to enable smart flash in 4ext. Its under settings in recovery
Sent from my HTC Ruby using xda app-developers app
I just successfully reverted my Amaze to sufficient stock to effect the download; download was already on the device but wouldn't install. Here were my steps.
Flashed stock recovery from CWM by extracting recovery.img from firmware.zip inside the OTA update zip.Rebooted into HBOOT, entered FASTBOOT.
=> fastboot flash recovery recovery.img
Attempted to apply the update from Recovery. Fail.
Initiated update from Settings | About Phone | Software updates. Update rebooted the phone...
Update complained about a mismatch in build.prop. Oops; I forgot that I'd edited it to override the "HTCLinkify" fix for Apple.
=> Edited /system/build.prop, removed ro.da1.method=enabled line, reverted ro.da1.enabled=false to true.
Rebooted.
Initiated the software update again, which it downloaded.
Started the update again, which rebooted the phone, updated without interruption, and rebooted into the new version (confirmed by popup and Settings | About phone | Software information).
=> Success.
I did not have to relock the bootloader. At this point I'd reflash recovery to CWM or TWRP again, but this was done on a phone which has a defective charging circuit, so I'm relocking the bootloader and returning it to T-Mobile.