[Q] Booting takes ages, bootloader corrupt? - HTC One X+

I've been going from AOKP to CM 10.1.3 stable a few days ago.
After about two days of no problems at all, my phone all of a sudden went really hot (like 58°C), battery drained from almost full to complete empty within less than two hours. I didn't install any new apps or flashed any updates.
I switched it off, turned it on again, but the battery drain continued. After being drained, it wouldn't boot to system and wouldn't charge for a whole while, saying "2%+" in TWRP for ages.
The problem now is, when I push the power button to turn it on, it doesn't react for about 2 to 5 minutes, then all of a sudden shows the HTC logo for another five minutes, then shows the CM bootanimation for another 5 to 10 minutes. If it finally finishes booting, I can use the system with almost no problems.
Flashing another version of CM (latest snapshot) and the matching kernel didn't help.
Can it be, that my bootloader is somehow corrupt?
Could it be a hardware issue like faulty memory?
Any ideas would be very welcome.
Thanks

19Uhr30 said:
I've been going from AOKP to CM 10.1.3 stable a few days ago.
After about two days of no problems at all, my phone all of a sudden went really hot (like 58°C), battery drained from almost full to complete empty within less than two hours. I didn't install any new apps or flashed any updates.
I switched it off, turned it on again, but the battery drain continued. After being drained, it wouldn't boot to system and wouldn't charge for a whole while, saying "2%+" in TWRP for ages.
The problem now is, when I push the power button to turn it on, it doesn't react for about 2 to 5 minutes, then all of a sudden shows the HTC logo for another five minutes, then shows the CM bootanimation for another 5 to 10 minutes. If it finally finishes booting, I can use the system with almost no problems.
Flashing another version of CM (latest snapshot) and the matching kernel didn't help.
Can it be, that my bootloader is somehow corrupt?
Could it be a hardware issue like faulty memory?
Any ideas would be very welcome.
Thanks
Click to expand...
Click to collapse
yes CM 10.2 (M1 Snapshot) has a LONG boot as does the nightlies due to a change i made for it to run smoother. but supply me with a log anyway of boot.

Lloir said:
yes CM 10.2 (M1 Snapshot) has a LONG boot as does the nightlies due to a change i made for it to run smoother. but supply me with a log anyway of boot.
Click to expand...
Click to collapse
Thanks for the quick reply, Lloir.
Is the time it takes my phone from pushing the power button to showing the HTC logo in any way related to the ROM it's running?
I've attached a log. There are many different (driver-) problems of which I'm not sure they are related to my initial problem.
Thanks for your help.

19Uhr30 said:
Thanks for the quick reply, Lloir.
Is the time it takes my phone from pushing the power button to showing the HTC logo in any way related to the ROM it's running?
I've attached a log. There are many different (driver-) problems of which I'm not sure they are related to my initial problem.
Thanks for your help.
Click to expand...
Click to collapse
power button > logo nope, but that can take a little bit anyway. my device takes SOMETIMES around 5-10seconds to display anything

Lloir said:
power button > logo nope, but that can take a little bit anyway. my device takes SOMETIMES around 5-10seconds to display anything
Click to expand...
Click to collapse
5-10 seconds is what I was used to before yesterday. Now it's more like several minutes.
Any ideas? Could reflashing the bootloader help? Erasing boot partition and reflashing?

19Uhr30 said:
5-10 seconds is what I was used to before yesterday. Now it's more like several minutes.
Any ideas? Could reflashing the bootloader help? Erasing boot partition and reflashing?
Click to expand...
Click to collapse
Bootloader and boot partition are 2 diffrent things. Boot partition stores the kernel. I doubt your bootloader is corrupt as your phone wouldnt even switch on if it was.
The only way to reflash bootloader with S-On devices is finding a compatible RUU.
Sent from my HTC One X+ using Tapatalk

AndroHero said:
I doubt your bootloader is corrupt as your phone wouldnt even switch on if it was.
Click to expand...
Click to collapse
Makes sense. I'm S-OFF btw.
When I flash a boot.img, does it overwrite the boot partition? Would it make sense to fastboot erase boot first?

19Uhr30 said:
Makes sense. I'm S-OFF btw.
When I flash a boot.img, does it overwrite the boot partition? Would it make sense to fastboot erase boot first?
Click to expand...
Click to collapse
Yeah when you flash a boot.img it overwrites boot partition. there is no real need to wipe boot before flashing a new kernel, but if you want to try it, it will cause no harm.
Sent from my HTC One X+ using Tapatalk
---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------
AndroHero said:
Yeah when you flash a boot.img it overwrites boot partition. there is no real need to wipe boot before flashing a new kernel, but if you want to try it, it will cause no harm.
In theory if you have S-Off, you could try reflashing bootloader. But be warned this is a last resort method. AFAIK Jtag is disabled with Tegra 3 so if something did go wrong, you would have a permanent brick.....
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
Sent from my HTC One X+ using Tapatalk

AndroHero said:
In theory if you have S-Off, you could try reflashing bootloader. But be warned this is a last resort method. AFAIK Jtag is disabled with Tegra 3 so if something did go wrong, you would have a permanent brick.....
Click to expand...
Click to collapse
Thanks for the warning and your help. Will try a few last things first. Flashing a RUU will change the bootloader without the risk of bricking my phone?
Have you any other thoughts or opinions on this issue?

Alright, so I ended up wanting to run the RUU to return to stock.
Now the damn problem is, as I start running it, it reboots the bootloader first and waits for the phone. But as it takes my phone ages to reboot, the software stops with a connection error after one minute or so.
What can I do?
After relocking the bootloader, my fastboot is showing me a security warning and won't boot to system or recovery any more.
Is it finally dead?
Sent from my Nexus 7 using xda app-developers app

19Uhr30 said:
Alright, so I ended up wanting to run the RUU to return to stock.
Now the damn problem is, as I start running it, it reboots the bootloader first and waits for the phone. But as it takes my phone ages to reboot, the software stops with a connection error after one minute or so.
What can I do?
After relocking the bootloader, my fastboot is showing me a security warning and won't boot to system or recovery any more.
Is it finally dead?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
If u have a custom ROM installed and locked bootloader u will get the security warning

[email protected] said:
If u have a custom ROM installed and locked bootloader u will get the security warning
Click to expand...
Click to collapse
Thanks, that's what I noticed. Do you know how to remove or reset it?

19Uhr30 said:
Thanks, that's what I noticed. Do you know how to remove or reset it?
Click to expand...
Click to collapse
U can unlock it again and flash custom recovery to install any custom ROM .....or if ur hboot is 1.35 u can run RUU and return to stock
if ur hboot is not 1.35 u got no other choice than unlocking ur bootloader

[email protected] said:
U can unlock it again and flash custom recovery to install any custom ROM .....or if ur hboot is 1.35 u can run RUU and return to stock
if ur hboot is not 1.35 u got no other choice than unlocking ur bootloader
Click to expand...
Click to collapse
Thanks for the summary. But sadly the first solution doesn't solve my problem and the second solution doesn't work because of my problem.

Okay, I found something interesting here:
http://forum.xda-developers.com/showpost.php?p=32574569&postcount=2
It says, I can fetch the ROM, the RUU wants to flash and flash it manually in HBOOT. I found the ROM and I think it would go round my problem with the 5 minutes of boot time.
Does anybody know, if this would work with my enrc2b?
Any dangers with using this method?
And most importantly, how will I have to name the file?

Alright, so I managed to return to stock now with the appropriate RUU, sensor problems and camera crash persist. But at least, I can return it to HTC for service now.
Here's how I got the RUU to run:
First, after running the .exe, I accepted the warning screen. Then I went to C:\Users\_user_\AppData\Local\Temp\ where I found a temporary folder, created by the RUU. It looked like this on my computer {C528E446-42D4-4210-B236-35BE15A71702} and it contains a dotnetinstaller.exe.
There is also a subfolder, where I found a ARUWizard.ini. Checking this out, I could change the values for "UpdateTimeout" and "VerifyTimeout" to way more than the default 90 seconds. This indeed helped. After saving the .ini, I went through the rest of the RUU.
The software was now waiting long enough for my phone to boot. But obviously there was another problem, since the update wouldn't run.
I remembered that after a reboot, I sometimes had to unplug the USB cable once and plug it back in for the connection to work and to see my device under fastboot devices.
I did this, while the black HTC screen was showing up and finally, the RUU went through the whole update process.
Thanks for all the support!

Related

[Q] Tricking battery into thinking it's charged

First, some backup on my problem: http://forum.xda-developers.com/showpost.php?p=26683314&postcount=4114 (tl;dr: any ROM I flash puts me in a seemingly inescapable boot loop, and rewriting boot.img sadly doesn't seem to help). This is still unresolved, and I think I've tried just about everything... getting pretty desperate there.
To make matters worse, my battery just died. I've heard there's a way to trick it into thinking it's charged so that you can access the bootloader at least temporarily (see: http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking -- I'm aware the article only mentions the DROID X, but I thought there must be some way to do this on the EVO 3D as well). Any ideas? I don't really want to have to buy a second battery, especially seeing as I'd have to wait several days for it to arrive - and wouldn't be able to use my phone until then.
Any help with either issue would be MUCH appreciated. Thanks so much!
3vo-noob said:
First, some backup on my problem: http://forum.xda-developers.com/showpost.php?p=26683314&postcount=4114 (tl;dr: any ROM I flash puts me in a seemingly inescapable boot loop, and rewriting boot.img sadly doesn't seem to help). This is still unresolved, and I think I've tried just about everything... getting pretty desperate there.
To make matters worse, my battery just died. I've heard there's a way to trick it into thinking it's charged so that you can access the bootloader at least temporarily (see: http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking -- I'm aware the article only mentions the DROID X, but I thought there must be some way to do this on the EVO 3D as well). Any ideas? I don't really want to have to buy a second battery, especially seeing as I'd have to wait several days for it to arrive - and wouldn't be able to use my phone until then.
Any help with either issue would be MUCH appreciated. Thanks so much!
Click to expand...
Click to collapse
if you plug the charger into the phone, the bootloader should be able to draw power from it, if I'm not mistaken.
3vo-noob said:
To make matters worse, my battery just died. I've heard there's a way to trick it into thinking it's charged so that you can access the bootloader at least temporarily (see: http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking -- I'm aware the article only mentions the DROID X, but I thought there must be some way to do this on the EVO 3D as well). Any ideas? I don't really want to have to buy a second battery, especially seeing as I'd have to wait several days for it to arrive - and wouldn't be able to use my phone until then.
Any help with either issue would be MUCH appreciated. Thanks so much!
Click to expand...
Click to collapse
Try- adb reboot-bootloader
that should boot up into your bootloader.
3vo-noob said:
To make matters worse, my battery just died. I've heard there's a way to trick it into thinking it's charged so that you can access the bootloader at least temporarily
Any help with either issue would be MUCH appreciated. Thanks so much!
Click to expand...
Click to collapse
I've accessed the boot loader without the battery installed. Plug into AC and use adb or power volume down to boot into boot loader.
Sent from my PG86100
rotheens spirit,
coal686 said:
I've accessed the boot loader without the battery installed. Plug into AC and use adb or power volume down to boot into boot loader.
Sent from my PG86100
Click to expand...
Click to collapse
Nope... Plugged into AC, but no matter how long I hold volume down + power, it won't get to the bootloader. Interestingly, when I plug it into my Mac, it still gives me a popup asking whether to connect the device to OS X or Windows (I have Fusion)... ideas?
3vo-noob said:
First, some backup on my problem: http://forum.xda-developers.com/showpost.php?p=26683314&postcount=4114 (tl;dr: any ROM I flash puts me in a seemingly inescapable boot loop, and rewriting boot.img sadly doesn't seem to help). This is still unresolved, and I think I've tried just about everything... getting pretty desperate there.
To make matters worse, my battery just died. I've heard there's a way to trick it into thinking it's charged so that you can access the bootloader at least temporarily (see: http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking -- I'm aware the article only mentions the DROID X, but I thought there must be some way to do this on the EVO 3D as well). Any ideas? I don't really want to have to buy a second battery, especially seeing as I'd have to wait several days for it to arrive - and wouldn't be able to use my phone until then.
Any help with either issue would be MUCH appreciated. Thanks so much!
Click to expand...
Click to collapse
I guess the first thing we need to know is, is your phone CDMA or GSM?
If you are flashing CDMA roms on a GSM or vise versa, it will never work. Its like putting diesel fuel in a gas engine. It won't run.
You have to flash a rom that is compatible with your phone.
Reckon we start there.
zcink said:
I guess the first thing we need to know is, is your phone CDMA or GSM?
If you are flashing CDMA roms on a GSM or vise versa, it will never work. Its like putting diesel fuel in a gas engine. It won't run.
You have to flash a rom that is compatible with your phone.
Reckon we start there.
Click to expand...
Click to collapse
Yup... I have a CDMA model & I'm checking each ROM to make sure it's specific to the CDMA EVO 3D
3vo-noob said:
Yup... I have a CDMA model & I'm checking each ROM to make sure it's specific to the CDMA EVO 3D
Click to expand...
Click to collapse
Have you tried the latest version of 4EXT Recovery Touch?
or how are able to flash any rom?
zcink said:
Have you tried the latest version of 4EXT Recovery Touch?
or how are able to flash any rom?
Click to expand...
Click to collapse
I'm using clockworkmod recovery touch... all the ROMs flash just fine, but once the flashing is done, the phone gets stuck in a bootloop
After an hour or so on the AC, my phone is able to power on & enter bootloader mode, but I still can't get out of the boot loop. Help plz?
3vo-noob said:
After an hour or so on the AC, my phone is able to power on & enter bootloader mode, but I still can't get out of the boot loop. Help plz?
Click to expand...
Click to collapse
Wanna try 4ext recovery?
your bootloader should say Unlocked and you are probably S-ON. Correct?
In fastboot. When you plug in your USB cable to the computer, it should now say fastbootusb.
If you can get that far, yeah, just flash the newest 4ext Recovery and try to flash your roms through that.
The newest has the ability to flash S-ON with one extra boot that will eliminate the need to flash the boot.img separately.
here is the link for it:
http://forum.xda-developers.com/showthread.php?t=1560279
***one possible thing I can think of that you may be doing wrong is when you flash the boot.img, it has to be the SAME one from the rom you flash.
anyway use 4ext instead.
zcink said:
your bootloader should say Unlocked and you are probably S-ON. Correct?
In fastboot. When you plug in your USB cable to the computer, it should now say fastbootusb.
If you can get that far, yeah, just flash the newest 4ext Recovery and try to flash your roms through that.
The newest has the ability to flash S-ON with one extra boot that will eliminate the need to flash the boot.img separately.
here is the link for it:
http://forum.xda-developers.com/showthread.php?t=1560279
***one possible thing I can think of that you may be doing wrong is when you flash the boot.img, it has to be the SAME one from the rom you flash.
anyway use 4ext instead.
Click to expand...
Click to collapse
Thanks SO much to everyone who helped! Thanks to you, I'm now happily using MeanROM!
3vo-noob said:
Thanks SO much to everyone who helped! Thanks to you, I'm now happily using MeanROM!
Click to expand...
Click to collapse
Glad to see you got it working. Thumbsup!
zcink said:
Glad to see you got it working. Thumbsup!
Click to expand...
Click to collapse
On an unrelated note, the one major feature that seems to be missing from 4EXT Recovery Control is the ability to update your ROM from within the app... I really admired that feature in ClockworkMod. Is there any other way to do this?
3vo-noob said:
On an unrelated note, the one major feature that seems to be missing from 4EXT Recovery Control is the ability to update your ROM from within the app... I really admired that feature in ClockworkMod. Is there any other way to do this?
Click to expand...
Click to collapse
Well yes, as the Developer updates the rom, you just use 4ext and reflash it over the top of the old one. Takes about 3 mins.
---------- Post added at 11:46 PM ---------- Previous post was at 11:34 PM ----------
Did you order another battery?
I just bought a lot of 10 of em from this company:
http://www.dhgate.com/new-li-ion-ph...r-htc/p-ff808081321fe6450132294c18783c3d.html
Should be like a lifetime supply. As long as you don't charge them, the shelf life should be many years.
$38.00 for 10 of them = $3.80 each. Very cheap! Took about 2 weeks to get them.

[Q] I cannot get pass the splash screen no matter what

Greetings to all I'am somewhat new to the android rooting,
I'm more used to to the sprint touch pro roms.But non the less I have successfully
lost track of how I cannot get pass the splash screen.I began using cmw-4.0.1.4
after researching it was ok but found out it was more hassle then nessecary I
finally have what works per the post in the forums.I was able to root it when I
was able to get pass the splash screen .titainium backup, root folder superuser ect...
all worked fine then tried to install the SOS_M_1.4 rom and thats all she
wrote.I was able to install to the very end including MeanROM-ICS-v091-E3D to
the end but couldnt get pass the splash screen after that. I do apologize for
the lengthy request for help I'm lost in the sauce right now
hboot 1.5 S-on
Unlocked
TWRP1.1
su-2.3.6.3zip
blackbolo said:
Greetings to all I'am somewhat new to the android rooting,
I'm more used to to the sprint touch pro roms.But non the less I have successfully
lost track of how I cannot get pass the splash screen.I began using cmw-4.0.1.4
after researching it was ok but found out it was more hassle then nessecary I
finally have what works per the post in the forums.I was able to root it when I
was able to get pass the splash screen .titainium backup, root folder superuser ect...
all worked fine then tried to install the SOS_M_1.4 rom and thats all she
wrote.I was able to install to the very end including MeanROM-ICS-v091-E3D to
the end but couldnt get pass the splash screen after that. I do apologize for
the lengthy request for help I'm lost in the sauce right now
hboot 1.5 S-on
Unlocked
TWRP1.1
su-2.3.6.3zip
Click to expand...
Click to collapse
Ooh HBOOT. In 1.5 S-On , users have difficulty flashing ics ROMs . My only recommendation is , DOWNGRADE !
http://forum.xda-developers.com/showthread.php?t=1563342
Sent from my PG86100 using Tapatalk 2
Comments Withdrawn
I see that was info I wish I knew before I've been at this all day literally small breaks in between I'm currently stuck in a loop I can get into the recovery no problem but having I've tried has lead me here asking for help
Comments Withdrawn
zcink said:
So, not sure what you're saying you can get into recovery? What recovery are you using?
Latest 4EXT?
Can you flash a rom?
Try a 401 rom and if you are using 4ext recovery, you should be all set.
Click to expand...
Click to collapse
twrp1.1 actually
blackbolo said:
twrp1.1 actually
Click to expand...
Click to collapse
Im on the cdma network aswell I think in honesty Ive mixed up the files that are used for the command prompt :crying: so Im really going off of the threads
Comments Withdrawn
zcink said:
Ok well the advise I gave you was sound. From experience.
But you do what you want. Seems you will anyway.
Good luck to ya.
Click to expand...
Click to collapse
okay so you say you had this problem before ? its just im not getting enough detail to go about it I should say Im still new to this
Comments Withdrawn
blackbolo said:
okay so you say you had this problem before ? its just im not getting enough detail to go about it I should say Im still new to this
Click to expand...
Click to collapse
I appreciate the help
blackbolo said:
I appreciate the help
Click to expand...
Click to collapse
ok thanks bro ( when I said I was going off the threads) I didn't mean I was not taking head to your advice I was saying that's how I've been learning about my problem so far
zcink said:
You need to flash this recovery:
http://forum.xda-developers.com/showthread.php?t=1561999
When you do it will ask if you are S-On -- say yes. Then when you boot into recovery and flash a rom it will boot one extra time and flash the boot.img for you so you don't have to do it manually.
Flash any CDMA rom with the base 401 and it should boot up all the way for you. Give it time on the first boot, could take up 10 mins or so.
Click to expand...
Click to collapse
thank you again.I how do I install it being that its apk file,i cant access home screen to get it my phone so what other was are there?
I'm having the same problem. I figured out by holding down the power button for 20 seconds when its stuck in the splash screen it will bypass the issue. If that doesn't work pull the battery out and put it back in. Hold down the power button down 20 seconds while it attempts to boot.... hopefully that will get it to boot into what ever Rom you previously flashed. I have flashed, several differant roms, done super wipes, modified wipes, flashed differant recoveries, updated the radio, and I'm still having issues where I get stuck in the splash screen or I have issues where I can't boot into recovery (its a hit or miss after a couple of different approaches)
This all happened after I went from ICS back to GB (mean rom)
Sent from my HTC Flyer using Tapatalk 2
Sent from my HTC Flyer using Tapatalk 2
Comments Withdrawn
I was only trying to help blackbolo boot past the splash screen.
I was only sharing my experience and resolution to my problem with the splash screen and recovery.
I'm not new to this...
When I mentioned recoveries:
I am having issues directly rebooting in to any recovery from bootloader or my rom
I have flashed twrp, 4ext and clockworkmod,one recovery at a time through 4EXT/ root toolbox/rom manager/adb and bootloader. After every flash I attempt to boot into recovery. For the most part each attempt failed where I get stuck in a boot loop or it freezes in the splash screen.
The only success I have had is clockworkmod 5.0.2.0 where I can reboot directly into recovery from my Rom or Bootloader... but I am still have issues booting back into my rom from recovery/initial power on/ bootloader. It gets stuck in the splashscreen or boot loops. I have super wiped and reflashed meanrom, then modified wiped reflashed, reflashed radio...
Either way when my phone reboots it stays in the splash screen till I pull and put back the battery. hold down the power button as it boots showing the splash....
Again I was just sharing what works for me for now till I trouble shoot and figure out what it could be... this used to happen to me when I had my G1 and the MyTouch Slide... there was residual files on the sdcard or partitions that prevented the phone to properly boot...
Sent from my HTC Flyer using Tapatalk 2
Comments Withdrawn
h8dannyboy said:
I'm having the same problem. I figured out by holding down the power button for 20 seconds when its stuck in the splash screen it will bypass the issue. If that doesn't work pull the battery out and put it back in. Hold down the power button down 20 seconds while it attempts to boot.... hopefully that will get it to boot into what ever Rom you previously flashed. I have flashed, several differant roms, done super wipes, modified wipes, flashed differant recoveries, updated the radio, and I'm still having issues where I get stuck in the splash screen or I have issues where I can't boot into recovery (its a hit or miss after a couple of different approaches)
This all happened after I went from ICS back to GB (mean rom)
Sent from my HTC Flyer using Tapatalk 2
Sent from my HTC Flyer using Tapatalk 2
Click to expand...
Click to collapse
I definitely appreciate the consideration I wasn't sure if was all alone I'm still going tru the boot loop as Iam typing now its crazy I'm starting over from scratch to see were I went wrong SDK to TWRP has to be something I missed.that 4extrecovery isnt going to work for me as I haven't found a way to get it installed,as Im stuck at the splash screen looping :laugh:
Comments Withdrawn
zcink said:
Just flash an older rom, any rom for your phone. GB for now. By whatever way you flash now. You have to take the extra step of extracting the boot.img and putting in your tools folder.
Then flash the boot.img from the adb with the command fastboot flash boot boot.img
Once you get a rom to boot all the way up then I recommend installing 4ext recovery touch.
Click to expand...
Click to collapse
ok now that is what I needed to hear thank a million bro ? and I haven't been able to locate a rom that doesn't require a kernel to install or flash to the phone.? which tools folder you speak of I think thats the problem Ive had actually

First Time I've had this problem....help

i'm having some strange issues that I've never really had before. The phone is stuck in 3G for some reason....and the SD card isn't mounting automatically. i just got done relocking the phone and flashing an RUU and I think that changed something at a deep level that I changed for the better at one time or another....cause I used to flash any rom under the sun and NEVER have an issue whatsoever. Its on the 2.25HBOOT and just a stock RUU for now...
I'm about to unlock it and and put a recovery on it and start modding it again...but don't want to go do all that and not have the 4G or SDcard working after. I know about the Old firmware patch and I did not have to use that before. Its just confusing to me.
Also I am S-OFF....ideas?
Justin
Did you flash the ruu twice? Everything doesnt stick sometimes if u flash once.
Sent from my ADR6425LVW using Tapatalk 2
Geerboy said:
i'm having some strange issues that I've never really had before. The phone is stuck in 3G for some reason....and the SD card isn't mounting automatically. i just got done relocking the phone and flashing an RUU and I think that changed something at a deep level that I changed for the better at one time or another....cause I used to flash any rom under the sun and NEVER have an issue whatsoever. Its on the 2.25HBOOT and just a stock RUU for now...
I'm about to unlock it and and put a recovery on it and start modding it again...but don't want to go do all that and not have the 4G or SDcard working after. I know about the Old firmware patch and I did not have to use that before. Its just confusing to me.
Also I am S-OFF....ideas?
Justin
Click to expand...
Click to collapse
Flash to the stock recovery and do a factory reset in hboot. That will solve the issue
Geerboy said:
i'm having some strange issues that I've never really had before. The phone is stuck in 3G for some reason....and the SD card isn't mounting automatically. i just got done relocking the phone and flashing an RUU and I think that changed something at a deep level that I changed for the better at one time or another....cause I used to flash any rom under the sun and NEVER have an issue whatsoever. Its on the 2.25HBOOT and just a stock RUU for now...
I'm about to unlock it and and put a recovery on it and start modding it again...but don't want to go do all that and not have the 4G or SDcard working after. I know about the Old firmware patch and I did not have to use that before. Its just confusing to me.
Also I am S-OFF....ideas?
Justin
Click to expand...
Click to collapse
Yes what they said...although I'm not a big believer in routine double flashing....uh...exactly what RUU did you flash?
topgun1953 said:
Yes what they said...although I'm not a big believer in routine double flashing....uh...exactly what RUU did you flash?
Click to expand...
Click to collapse
actually when i flashed a RUU.. the first pass only had a couple of chechmarks and you could totally tell it didnt fully install everything because there were alot that it skipped/ not checked. 2nd passthrough it was fully checked off on what it was trying to install.
funnyangrykid said:
actually when i flashed a RUU.. the first pass only had a couple of chechmarks and you could totally tell it didnt fully install everything because there were alot that it skipped/ not checked. 2nd passthrough it was fully checked off on what it was trying to install.
Click to expand...
Click to collapse
yeah, I think it flashes the hboot first and then reboots itself to do the rest. This is not the same as flashing the whole thing twice.:good:

[Q] Rezound wont turn on

Well I've really done it this time. The phone will not power up at all. Ever since the whole Google Maps Rebooting issue the phone has been worthless. It hasn't been able to be turned on in a week. Just black screen. Before it completely failed it would boot, but after about 10 seconds it would restart or power off.
I have a feeling that the battery is not charging. When I plug it in to charge the orange battery led lights up but for only a couple of seconds and then it turns off. Maybe I need to get an external charger or something to charge my battery.
I would love to send the phone back for warranty, but I'm unlocked and rooted, so I am afraid that they won't help me out with warranty. Also, I would love to sell the phone, but obviously I'm not going to sell a phone that doesn't work.
If I could just get the phone to turn on so I can get some of my personal documents off of it that would be great. For some reason the phone stopped syncing contacts a few months ago and I need to get these off of the phone. Anyway. Any help would be appreciated. Thanks for any help/ideas.
Have you tried putting in a new battery? Also what recovery did you have on your device?
HTC Rezound
luis86dr said:
Have you tried putting in a new battery? Also what recovery did you have on your device?
HTC Rezound
Click to expand...
Click to collapse
I haven't tried a new battery. I don't have one. I might have to get one or an external charger.
I am using CWM touch. Yeah, I have read on here that CWM is crap for the rezound.
currentsupply said:
I haven't tried a new battery. I don't have one. I might have to get one or an external charger.
I am using CWM touch. Yeah, I have read on here that CWM is crap for the rezound.
Click to expand...
Click to collapse
there's your problem. the touch recovery will not allow the phone to charge when its 100% dead.
let me find the thread you need to bring it back to life
EDIT: follow this guide and report back please
http://forum.xda-developers.com/showthread.php?t=1711408
edit2: here is a mini ADB and fastboot zip i have. it will give you the tools you need if you dont have them of course. link
synisterwolf said:
there's your problem. the touch recovery will not allow the phone to charge when its 100% dead.
let me find the thread you need to bring it back to life
EDIT: follow this guide and report back please
http://forum.xda-developers.com/showthread.php?t=1711408
edit2: here is a mini ADB and fastboot zip i have. it will give you the tools you need if you dont have them of course. link
Click to expand...
Click to collapse
Thanks for you help. I will try this as soon as I get home this evening. I will report back, thanks again...
currentsupply said:
Thanks for you help. I will try this as soon as I get home this evening. I will report back, thanks again...
Click to expand...
Click to collapse
you're welcome.
on a side note, if you like touch recovery and that's why you chose CMW touch, the TWRP is a good alliterative. LINK
synisterwolf said:
there's your problem. the touch recovery will not allow the phone to charge when its 100% dead.
let me find the thread you need to bring it back to life
EDIT: follow this guide and report back please
http://forum.xda-developers.com/showthread.php?t=1711408
edit2: here is a mini ADB and fastboot zip i have. it will give you the tools you need if you dont have them of course. link
Click to expand...
Click to collapse
Lol just checked thread when I got home. Beat me to it.
HTC Rezound
Ok, I did that trick and I am back in business. Thanks for your help. Now I need to figure out how to go back to stock. I would like to install the RUU file, stock ota file.
I am looking for instructions on how to do this. I know there are many threads covering this, but not very many good answers.
currentsupply said:
Ok, I did that trick and I am back in business. Thanks for your help. Now I need to figure out how to go back to stock. I would like to install the RUU file, stock ota file.
I am looking for instructions on how to do this. I know there are many threads covering this, but not very many good answers.
Click to expand...
Click to collapse
here is the global ruu http://bit.ly/RaKEAr, instructions are on mostly on rom's on how to do this. very simple to do!
i followed nil's 6.1 version to do it.
abrego47 said:
here is the global ruu http://bit.ly/RaKEAr, instructions are on mostly on rom's on how to do this. very simple to do!
i followed nil's 6.1 version to do it.
Click to expand...
Click to collapse
does this file get flashed in recovery like a normal rom? Does it take me back to locked/non-rooted? Thanks.
Rename to PH98IMG.zip, put on the root of the external SD, boot to bootloader and it will do the rest automatically. Make sure you delete the file from the SD after you're done so you won't have trouble in the future.
EDIT: It might reboot two or three times during the installation and look like it's doing some things multiple times. That's normal, so don't panic.
currentsupply said:
does this file get flashed in recovery like a normal rom? Does it take me back to locked/non-rooted? Thanks.
Click to expand...
Click to collapse
Rename to PH98IMG.zip and flash in boot loader.
currentsupply said:
does this file get flashed in recovery like a normal rom? Does it take me back to locked/non-rooted? Thanks.
Click to expand...
Click to collapse
Flashing the RUU will get you phone back to 100% right out of the box stock.
it will update your hboot to 2.27 and lock it.
it will wipe internal storage.
it will give you global firmware and kernel.
all you need to do is relock the device via fastboot command " fastboot oem lock"
then place zip on root of the sd card and rename it to PH98IMG.zip
boot into hboot and it will detect it.
first flash will update hboot, firmware, kernel, splash, radio
it will reboot automatically. (back to fastboot)
then go back to hboot and let it run one more time. (this will take a while as its wiping, formatting, then installing system files)
after its all complete it will boot the phone into the os.
Ok, I'm going to go for this tonight when I get off work.
Hopefully the RUU OS stops the rebooting problem I am having. I am currently running Scott's Clean ROM. I was working great since about May, but now even after a few wipes and re-installs, it still has the reboot bug. Phone won't stay on for longer than 5 minutes and it continually reboots and quickly drains the battery. Basically it is unusable. I was able to flash Amon Recovery and that did fix the charging issue, but it didn't help with the reboots.
Hopefully after the RUU it's back to stable.
currentsupply said:
Ok, I'm going to go for this tonight when I get off work.
Hopefully the RUU OS stops the rebooting problem I am having. I am currently running Scott's Clean ROM. I was working great since about May, but now even after a few wipes and re-installs, it still has the reboot bug. Phone won't stay on for longer than 5 minutes and it continually reboots and quickly drains the battery. Basically it is unusable. I was able to flash Amon Recovery and that did fix the charging issue, but it didn't help with the reboots.
Hopefully after the RUU it's back to stable.
Click to expand...
Click to collapse
It should, Scotts Rom is to old. Once you do the ruu, do a clean install of a newer Rom
Sent from my iPhone...
So far so good. Thanks for your help guys. Right now it is loading the ph98img.zip in the hboot,
checking..[ph98img.zip]
Androids on Skateboards on bottom of screen ****RELOCKED**** in purple on top
Do I want to start update it asks.. Vol Up for yes
it's going through the list. screen goes black.... waiting..... back on
HBOOT IS UP AGAIN LOOKS LIKE IT'S STARTING OVER.... AGAIN LOADING....[PH98IMG.zip]
Vertical status bar on right upper again going through loading....
again Checking..[PH98IMG.zip]
..... Waiting ......
Update is in progress.....
Do not power off the device!
stayed at system for a while... now Update Complete, press power to reboot.. ok
htc on white
beats logo
4G LTE logo
and.......
WAITING..... AND I'M IN.. HELL YEAH.. CROSSES FINGERS FOR NO REBOOTS!
currentsupply said:
does this file get flashed in recovery like a normal rom? Does it take me back to locked/non-rooted? Thanks.
Click to expand...
Click to collapse
it depends if you are s-on or s-off?
currentsupply said:
WAITING..... AND I'M IN.. HELL YEAH.. CROSSES FINGERS FOR NO REBOOTS!
Click to expand...
Click to collapse
giggidy.
Let us know if you need anymore help.

Amaze is supposedly dead

Phone was working great until it just froze, I did a battery pull and now it won't go past the HTC white logo screen.
It boots into recovery, but only as safe mode.
Cannot access internal memory or external memory.
Haven't tried wiping the system since I can't really access the storage space to flash anything, or even restore a backup.
It's not dead. Simone else just posted the same exact problem.
Download the latest ruu. Pull your external sdcard.
Put sdcard in the computer.
Copy the ph85img.zip to it.
Put sdcard in phone.
Boot to bootloader.
Follow the on screen instructions.
That'll get you back to square one.
Also look for Odysseus' post in the other threads. He has some good information on this subject.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
It's not dead. Simone else just posted the same exact problem.
Download the latest ruu. Pull your external sdcard.
Put sdcard in the computer.
Copy the ph85img.zip to it.
Put sdcard in phone.
Boot to bootloader.
Follow the on screen instructions.
That'll get you back to square one.
Also look for Odysseus' post in the other threads. He has some good information on this subject.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thank you for the advice. I was thinking about putting the ruu but I wasn't sure. I needed confirmation on this issue.
I will keep you posted about what happens.
Darin_Ram said:
Thank you for the advice. I was thinking about putting the ruu but I wasn't sure. I needed confirmation on this issue.
I will keep you posted about what happens.
Click to expand...
Click to collapse
As Chevy said, someone else posted with this exact same problem a day or two ago. Since you're S-off and unlocked the procedure is to download the latest factory image for your device. You can't flash one from another carrier or you'll brick it. There are links in one of the "pinned" threads at the top of the forums.
Once you have it downloaded rename it to "PH85IMG.zip" (note the capitalization must be exactly the same) and place it in the root of your external SD card. Now comes the fun part. It won't flash on an unlocked bootloader, so you must relock it using ADB commands or with the Amaze toolkit (don't worry you won't loose S-off). BTW I hope you saved the HTC unlock blob from when you first unlocked as you'll need it again to unlock later.
Flash the image from the bootloader hboot. When it's finished then go to settings / about phone /software information and accept any HTC updates. With a T-Mobile phone there will be at least three OTA's depending on which image you installed. Two of them are 30MB and require rebooting in between. The last one just updates a couple of .apks and doesn't need a reboot. You need these to get the latest radio.
Once all of the updating is finished you'll be back to factory with the latest radio. Now all you have to do is unlock, install a recovery, reroot, SuperCID, and you'll be ready to play again.
I hope this helps
Thanks again for the help, the phone is functional again. Does anybody have any idea why this happens?
Odysseus1962 said:
As Chevy said, someone else posted with this exact same problem a day or two ago. Since you're S-off and unlocked the procedure is to download the latest factory image for your device. You can't flash one from another carrier or you'll brick it. There are links in one of the "pinned" threads at the top of the forums.
Once you have it downloaded rename it to "PH85IMG.zip" (note the capitalization must be exactly the same) and place it in the root of your external SD card. Now comes the fun part. It won't flash on an unlocked bootloader, so you must relock it using ADB commands or with the Amaze toolkit (don't worry you won't loose S-off). BTW I hope you saved the HTC unlock blob from when you first unlocked as you'll need it again to unlock later.
Flash the image from the bootloader hboot. When it's finished then go to settings / about phone /software information and accept any HTC updates. With a T-Mobile phone there will be at least three OTA's depending on which image you installed. Two of them are 30MB and require rebooting in between. The last one just updates a couple of .apks and doesn't need a reboot. You need these to get the latest radio.
Once all of the updating is finished you'll be back to factory with the latest radio. Now all you have to do is unlock, install a recovery, reroot, SuperCID, and you'll be ready to play again.
I hope this helps
Click to expand...
Click to collapse
Holy crap I did none of the above. The ruu flashed on the unlocked bootloader, I didn't even capitalize it.
The bootloader stayed unlocked, I didn't check the supercid on it................................................................ I just re-installed the recovery
It booted fine though, so I have no idea what's going on
Darin_Ram said:
Thanks again for the help, the phone is functional again. Does anybody have any idea why this happens?
Click to expand...
Click to collapse
I'm as careful as they come. but it happened to me a few weeks back too. Sometimes you just get a bad flash, other times NAND memory cells get stuck (they wear out over time) or are slow to accept data. All it takes is an important part of the file system flashed onto a bad data block and the whole thing can get stuck in a loop. For me I had been trying out a bunch of ROMS and somehow a kernel failed to flash. I ended up with a kernel mismatch (kernel modules don't match the kernel) which resulted in a bootloop.
As a precaution I just keep an old 2GB SD-card handy that only has the Amaze image on it, so in case of an emergency all I have to do is relock the bootloader, stick in the SD card and I'm back in action within 15 mins.
Odysseus1962 said:
I'm as careful as they come. but it happened to me a few weeks back too. Sometimes you just get a bad flash, other times NAND memory cells get stuck (they wear out over time) or are slow to accept data. All it takes is an important part of the file system flashed onto a bad data block and the whole thing can get stuck in a loop. For me I had been trying out a bunch of ROMS and somehow a kernel failed to flash. I ended up with a kernel mismatch (kernel modules don't match the kernel) which resulted in a bootloop.
As a precaution I just keep an old 2GB SD-card handy that only has the Amaze image on it, so in case of an emergency all I have to do is relock the bootloader, stick in the SD card and I'm back in action within 15 mins.
Click to expand...
Click to collapse
That's a good idea, but is it really necessary for me right now? You know, since the bootloader is still unlocked, SuperCID is still 1's and I'm still S-OFF?
If it happens again, I'll re-lock, reload, and re-flash
Darin_Ram said:
Holy crap I did none of the above. The ruu flashed on the unlocked bootloader, I didn't even capitalize it.
The bootloader stayed unlocked, I didn't check the supercid on it................................................................ I just re-installed the recovery
It booted fine though, so I have no idea what's going on
Click to expand...
Click to collapse
Did you flash from your SD card or push the ruu with ADB? Usually it will only accept the zip image from the bootloader, but the ruu can be pushed with ADB.
What ever the case I'm just glad things worked out.
Odysseus1962 said:
Did you flash from your SD card or push the ruu with ADB? Usually it will only accept the zip image from the bootloader, but the ruu can be pushed with ADB.
What ever the case I'm just glad things worked out.
Click to expand...
Click to collapse
Flashed via SD card.
By the way, can we dual boot this phone?
I know, it's risky booting it to two os, but I'm just wondering cause making backups and restoring nandroids are becoming a pain every time I want to take good photos. :/ So I was wondering if we could dual boot.
I dual booted my old defy that only had about half the ram, and half the processing speed lmao so why not this device?
Darin_Ram said:
Flashed via SD card.
By the way, can we dual boot this phone?
I know, it's risky booting it to two os, but I'm just wondering cause making backups and restoring nandroids are becoming a pain every time I want to take good photos. :/ So I was wondering if we could dual boot.
I dual booted my old defy that only had about half the ram, and half the processing speed lmao so why not this device?
Click to expand...
Click to collapse
I could dual boot on my old HD2 as well. I don't believe any devs here have written a bootloader with that capability for the Amaze, but you could always just do a search and find out for yourself. It might be just a matter of porting an existing app to this device. Good luck!!!!
Odysseus1962 said:
I could dual boot on my old HD2 as well. I don't believe any devs here have written a bootloader with that capability for the Amaze, but you could always just do a search and find out for yourself. It might be just a matter of porting an existing app to this device. Good luck!!!!
Click to expand...
Click to collapse
I googled it, the only thing that came up was an old thread about someone asking for the system/cache/boot sizes.
Looks like no one really wanted it for this device.
I wish they did though, the Sense camera is amazing
Darin_Ram said:
I googled it, the only thing that came up was an old thread about someone asking for the system/cache/boot sizes.
Looks like no one really wanted it for this device.
I wish they did though, the Sense camera is amazing
Click to expand...
Click to collapse
I know what you mean. One reason I keep coming back to NRG is because of camera and video. I can't find a replacement that comes close.
Odysseus1962 said:
I know what you mean. One reason I keep coming back to NRG is because of camera and video. I can't find a replacement that comes close.
Click to expand...
Click to collapse
I've actually never flashed that one lol
But I was reading up and apparently there's a HD camera mod (can't remember if it was the desire or sensation) that was supposed to take better 1080p videos and superb photos.
I saw it floating the forums a while ago, but it was a sense cam so I couldn't flash it. I had Pac 4.3 at the time.
Now I'm on 4.4 Evervolv, so far so good. Lowest ram usage I've ever had with a lot of apps installed, so I'm happy with it.
I may or may not try Cyanogenmod 11 but I'm in no hurry.
Darin_Ram said:
Thanks again for the help, the phone is functional again. Does anybody have any idea why this happens?
Click to expand...
Click to collapse
No idea why it happens but I had the same symptoms - wouldn't get past the HTC logo but this happened after I had simply powered the phone off and removed the battery after I wasn't going to use it for a while [playing with the Lumia 920].
It seemed like the partition map gets wiped out or something causing the problem.
The hdd camera is in the aroma installer I'm my viper Rom.
Well also be the camera default in the upcoming release of jellybean sense and other future releases.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
The hdd camera is in the aroma installer I'm my viper Rom.
Well also be the camera default in the upcoming release of jellybean sense and other future releases.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Sounds good, but no kit kat?
One Rom at a time... Lol
Ravike and I have been working on this for a while now. Can't progress until we get the next level finished, then the next version will be hopefully easier. We are getting closer. Ravike has a lot of building from scratch to do.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
One Rom at a time... Lol
Ravike and I have been working on this for a while now. Can't progress until we get the next level finished, then the next version will be hopefully easier. We are getting closer. Ravike has a lot of building from scratch to do.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Ooooh
I used your rom, I love the full gpu rendering. Haven't tried the camera yet, but looking forward to that HD mod that's on there.
Nenamark2 gets 50.5 fps!!!!!!!!!! That's the most I've ever seen this device go up to!!!!
Damn! Awesome lol
Antutu shows that the graphics goes over the 4000 mark. Definitely love it.
Darin_Ram said:
Ooooh
I used your rom, I love the full gpu rendering. Haven't tried the camera yet, but looking forward to that HD mod that's on there.
Nenamark2 gets 50.5 fps!!!!!!!!!! That's the most I've ever seen this device go up to!!!!
Damn! Awesome lol
Antutu shows that the graphics goes over the 4000 mark. Definitely love it.
Click to expand...
Click to collapse
ViperAmaze was one of the first ROMs I tried when I got mine. I loved everything about it except I had Bluetooth pairing and WiFi tethering issues. Since I'm a truck driver, I need hands free on my daily driver. Unfortunately, it seems most if not all of the builds that are not derived directly from the OEM HTC Amaze, have some type of Bluetooth or WiFi issue that's not easily overcome.

Categories

Resources