Hello,
Here is my problem.
My Desire X was working fine, until yesterday. About 1,5 - 2 months ago, i installed a custom rom, this one: http://forum.xda-developers.com/showthread.php?t=2555350, which worked great, It had no problem. I charged the phone the other day, and yesterday at about 21:00 PM my phone had ~6% battery left. When I got home, at 21:30 I wanted to put the phone on charge. I pulled the phone out of pocket, but it was turned off. I assumed it ran out of all battery power. I plugged in the charger, I waited about 2 minutes before I opened it, then .. surprise: It opened the phone, the first HTC logo appeared, with a short vibration, but then when the next logo had to appear, it just vibrated 7 times and then freezes. Since then my phone vibrates 7 times on boot, and freezes. To restart the phone I have to take out the battery and put it on again.
The one thing I can do, is to enter on Bootloader, and Fastboot, but not recovery or factory reset. When I try to enter recovery from bootloader, the phone restarts and then the 7 vibration again. ADB device is not recognized on bootloader.
I tried flashing other recovery boot images with fastboot, it says succesfully but then again, restarts and vibrates 7 times.
In bootloader it says:
PROTO PVT SHIP S-ON RL
HBOOT-1.25.0002
RADIO-1.15.40.04
eMMC-boot
Apr 3 2013,15:50:50:1352
I have searched about this, I found several topics about this problem but with other phones, nothing on Desire X. I know it could be a hardware problem, but some say it could be a software problem. Besides I haven't done anything wrong to point to a hardware problem. What could it be??
Please, If you know anything about this, post your thoughts.
Thanks in advance.
What I can imagine is that something with the filesystem on the system partition has gone wrong. One interesting thing is, that we get the 7 vibrations as well if we try to run rumrunner on our device in order to get S-OFF. Your case indicates that the multiple vibrations might indicate a filesystem problem. Maybe @nightwalkerkg and @atis112 can share their thoughts on this one as well as they already tried the rumrunner.
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
What I can imagine is that something with the filesystem on the system partition has gone wrong. One interesting thing is, that we get the 7 vibrations as well if we try to run rumrunner on our device in order to get S-OFF. Your case indicates that the multiple vibrations might indicate a filesystem problem. Maybe @nightwalkerkg and @atis112 can share their thoughts on this one as well as they already tried the rumrunner.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, I tried to run rumrunner, but since this require adb connection, and adb doesn't recognize my phone. I only got fastboot working, and even this is limited. For example if I enter "fastboot erase cache" my phone freezes and stop responding, and I have to take out the battery then put it on again, and re-enter bootloader. On the other hand, when I try to boot an recovery image (.img), it works, then restarts and .. back to 7 vibrations. Any other suggestion?
Actually this indicates a problem with the power button,it's probably stuck. There are number of threads that have the same issue and they all indicate a power button problem. Try cleaning it. That is the only reasonable thing i can come up with since you didn't use rumrunner and the phone worked day before.
http://forum.xda-developers.com/showthread.php?t=1794284&page=2
nightwalkerkg said:
Actually this indicates a problem with the power button,it's probably stuck. There are number of threads that have the same issue and they all indicate a power button problem. Try cleaning it. That is the only reasonable thing i can come up with since you didn't use rumrunner and the phone worked day before.
http://forum.xda-developers.com/showthread.php?t=1794284&page=2
Click to expand...
Click to collapse
Could be the power button the problem? Yet... I can switch between fastboot an Hboot in bootloader using the power button, and easily. Doesn't seem that it is faulty. In my opinion this is not the problem.
Some other ideas?
Can you flash any RUU? Maybe flash the hboot again..
NVM...
I think the EMMC is fried..
when I try some commands with fastboot it says:
fastboot erase cache
...
erasing 'cache'...
FAILED (status read failed (Too many links))
finished. total time: 309.998s
fastboot oem rebootRUU
...
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
OKAY [ 1.263s]
finished. total time: 1.263s
fastboot getvar all
...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.25.0002
(bootloader) version-baseband: 1.15.40.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.20.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxx
(bootloader) imei: xxxxxxxx
(bootloader) meid:
(bootloader) product: proto
(bootloader) platform: HBOOT-8225
(bootloader) modelid: PM6610000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 1.220s
So my guess is that the EMMC is gone.
But I've read somewhere that i could run android from external sdcard. Do you have any idea how can I do this on my Desire X?
crissoo7 said:
I think the EMMC is fried..
when I try some commands with fastboot it says:
fastboot erase cache
...
erasing 'cache'...
FAILED (status read failed (Too many links))
finished. total time: 309.998s
fastboot oem rebootRUU
...
(bootloader) [SD/EMMC]Error status=0x400008
(bootloader) DATA_TIMEOUT
(bootloader) SD: write failed in CMD25.
OKAY [ 1.263s]
finished. total time: 1.263s
fastboot getvar all
...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.25.0002
(bootloader) version-baseband: 1.15.40.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.20.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxx
(bootloader) imei: xxxxxxxx
(bootloader) meid:
(bootloader) product: proto
(bootloader) platform: HBOOT-8225
(bootloader) modelid: PM6610000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 1.220s
So my guess is that the EMMC is gone.
But I've read somewhere that i could run android from external sdcard. Do you have any idea how can I do this on my Desire X?
Click to expand...
Click to collapse
Looks like. Try to claim warranty after flashing stock boot and recovery and relocking your phone and hope that they'll replace your motherboard.
dansou901 said:
Looks like. Try to claim warranty after flashing stock boot and recovery and relocking your phone and hope that they'll replace your motherboard.
Click to expand...
Click to collapse
If I could to a stock flashing and recovery I would not be needed to claim waranty . As long as I can't write or read anyhing on EMMC, I can't do any of these. Besides I have no warranty no more...
Thanks anyway.
If you find anything else about what I previously asked, please let me know.
crissoo7 said:
If I could to a stock flashing and recovery I would not be needed to claim waranty . As long as I can't write or read anyhing on EMMC, I can't do any of these. Besides I have no warranty no more...
Thanks anyway.
If you find anything else about what I previously asked, please let me know.
Click to expand...
Click to collapse
You don't have warranty? Because If you have, there is an easy solution. Kill your motherboard and send the phone to warranty! If they can't turn it on, they won't see that you unlocked your bootloader.
Related
Hello everyone. I am having an issue and cannot seem to understand what I am doing wrong. I have a view I got for Christmas. It seems like it was partially got the OTA updates. It ran for a while and then started just cycling through the power on / sprint 4g splash screen then would reboot. I can get into Fastboot. I have been messing with it for a few days. Here is where I am at. I was able to find this link http://forum.xda-developers.com/showthread.php?t=1423397 and follow the recomendations there. I flashed the firmware.zip and that went fine then i was able to unlock the bootloader via the HTC dev site (I was unable to do this prior to flashing). After that it seems that everything else fails.
on the fastboot screen I am showing:
unlocked
express PVT SHIP s-on RL
hboot-1.14.0005
microp-0656
radio-1.05.01.1006_3
emmc-boot
c:\htcview>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0005
(bootloader) version-baseband: 1.05.01.1006_
(bootloader) version-cpld: None
(bootloader) version-microp: 0656
(bootloader) version-main: 2.23.651.1
(bootloader) serialno: HT163HY00369
(bootloader) imei: 355195000000017
(bootloader) product: express
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG4120000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4116mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f821d4db
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
I have tried flashing:
RUU_Express_KT_KT_KR_1.24.1010.1_Radio_20.35c.30.089BU_3809.06.05.01_M_release_199840_signed
which fails once it hits the signatures on the install. So it is communicating and deletes the user data and starts the install. I have tired several different RUU packages and they all fail. Right now this thing just reboots constantly. any ideas? Suggestions?
Thanks,
Aaron
Wait, are you implying that OTA updates bricked your stock view?
You are not rooted or s-off'ed or anything, is that correct?
the only thing I did was try to unlock the device via the htcdev site. followed their instructions and then started getting the reboots not sure what I did wrong. I would like to be able to s-off and load custom roms but I cannot get anything to load. I have tried the viper rom and also the ruu file in the above post. I do not believe I am rooted but I cannot tell as I cannot boot into the operating system. I can get to the fastboot menu and I can get into Revolutionary CWM v4.0.1.4 console. I am stuck there as nothing else seems to load or install. everything keeps failing.
Downgrade to Gingerbread using RUU and then run revolutionary then just use the update method posted in the forums.
the problem is that when I run the RUU it fails. I cannot get anything to complete for me to be able to even get the system up. The ruu starts and eventually gives me an error stating it cannot communicate with the phone.
still trying different things, but have not progressed anywhere past that yet.
Fastboot flash a recovery (i made a supertool that flashes a recovery its in flyer and view development boards.)
Sent aboard the Evo Express
where do I find the recovery image?
....I suggest you just use the tool I made. It comes with all the images you could need and automatically chooses your device. You just decide which recovery you want and you need to declare which OS you're on (Honeycomb or Gingerbread)
cool got it. Finally got an image to take. Thanks for all your help!
Here's some phone history:
Factory S-Off
Flashed TWRP and permaroot here
Flashed ViperLTE 1.0.0
Ran that for a while, then the RUU came out.
Flashed the RUU.
Unlock comes along, so I unlocked it. Then I flashed ViperLTE 2.0.0, and had the sync and phone process issue so I relocked and changed the CID back.
Been running great up until today.
So I go to unlock my screen to reply to a text, and the LED isn't flashing and the touch seemed unresponsive. So I reboot to hboot, and it tells me "battery low replace battery" then "press power to continue" or something along those lines.
I went into recovery and nothing works, no touch, no LEDs, I just see the recovery.
At this point I got scared. Battery pull, reboot. Boots up into ROM, but no touch. I get texts, email updates, etc in the statusbar showing but when I tried calling the phone, the process stopped and everything looked frozen in the background.
Reboot into recovery, and while sitting there plugged in the battery DROPS
So I turned the phone completely off for an hour, still no charging.
Booted up into the ROM, and as I'm sitting here the battery is charging again.
Heres my post in the viper thread:
jtdogblue said:
It's been plugged in for a while now and no change in the indicated charge in recovery or once booted. Should I go ahead and try flashing the recovery?
EDIT: The phone's been off completely and wasn't charging, as it's sitting in recovery the battery level is.... dropping?
e:\android>fastboot flash recovery recovery.img
sending 'recovery' (9820 KB)...
OKAY [ 1.107s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.144s
e:\android>
e:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.15.0000
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT26JS309742
(bootloader) imei: 990000641796059
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3690mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3321eb88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.082s
Edit: I booted up and the battery is charging again.
Click to expand...
Click to collapse
So, that's where I'm at. Just figured I'd start a new thread instead of spamming the viper one.
Out of curiosity, if you were already s-off, why did you run the Fake CID unlock? With s-off, you should be able to push whatever you want onto the phone, including recovery and ROMs.
You may need to re-lock the bootloader and use the RUU to restore your phone to "factory" (with s-off) and start over. However, I do not know if the latest RUU will affect your s-off status, though, so proceed with great caution. Maybe andybones can confirm if the latest RUU has any negative effect on s-off.
junkmail9 said:
Out of curiosity, if you were already s-off, why did you run the Fake CID unlock? With s-off, you should be able to push whatever you want onto the phone, including recovery and ROMs.
You may need to re-lock the bootloader and use the RUU to restore your phone to "factory" (with s-off) and start over. However, I do not know if the latest RUU will affect your s-off status, though, so proceed with great caution. Maybe andybones can confirm if the latest RUU has any negative effect on s-off.
Click to expand...
Click to collapse
I keep asking myself the same question. The ruu.exe isn't working, it does absolutely nothing for me, so I flashed the individual things through hboot the first time didnt effect soff
jtdogblue said:
I keep asking myself the same question. The ruu.exe isn't working, it does absolutely nothing for me, so I flashed the individual things through hboot the first time didnt effect soff
Click to expand...
Click to collapse
since you decided to do the htc dev-unlock (which idk why, since u were s-off)
in order for you to run an RUU in bootloader, you need to re-lock the bootloader..
here's mine
C:\apktool>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.1111
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-75a5dc7e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.103s
C:\apktool>
---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------
also you have to run a command to turn it back to S-ON, other than that it's perm.
andybones said:
since you decided to do the htc dev-unlock (which idk why, since u were s-off)
in order for you to run an RUU in bootloader, you need to re-lock the bootloader..
here's mine
C:\apktool>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.1111
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-75a5dc7e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.103s
C:\apktool>
---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------
also you have to run a command to turn it back to S-ON, other than that it's perm.
Click to expand...
Click to collapse
I left the bootloader relocked. The RUU isn't working. It gets all the way through loading the installshield wizzard then just quits.
I'm about to spike this phone into the ground. $250 out the freaking window
jtdogblue said:
I left the bootloader relocked. The RUU isn't working. It gets all the way through loading the installshield wizzard then just quits.
I'm about to spike this phone into the ground. $250 out the freaking window
Click to expand...
Click to collapse
sounds to me like the bootloader is unlocked man.
andybones said:
sounds to me like the bootloader is unlocked man.
Click to expand...
Click to collapse
It says *RELOCKED* at the top. Also, the ruu doesnt let me click anything, just loads up then quits
PLEASE stay with me. I'm about to die here pressing refresh every 5 seconds
jtdogblue said:
It says *RELOCKED* at the top. Also, the ruu doesnt let me click anything, just loads up then quits
PLEASE stay with me. I'm about to die here pressing refresh every 5 seconds
Click to expand...
Click to collapse
INSTRUCTIONS
1) Download this - MD5 = 55023CC10B59FDEC0AAA6695C4CF83FB
2) rename to PJ53IMG.zip (make sure it's not named PJ53IMG.zip.zip...)
3) put the PJ53IMG.zip on the root of your SD-Card. (not in any folders)
4) reboot to bootloader
5) let the phone do its magic
6) enjoy Sense 4.1
I am VERY appreciative of any help you provide, I didn't mean to come across as pushy in any way. Thank you again
jtdogblue said:
I am VERY appreciative of any help you provide, I didn't mean to come across as pushy in any way. Sorry
Click to expand...
Click to collapse
Thank you. I appreciate that.
Please try this
INSTRUCTIONS
1) Download this - MD5 = 55023CC10B59FDEC0AAA6695C4CF83FB
2) rename to PJ53IMG.zip (make sure it's not named PJ53IMG.zip.zip...)
3) put the PJ53IMG.zip on the root of your SD-Card. (not in any folders)
4) reboot to bootloader
5) let the phone do its magic
6) enjoy Sense 4.1
---------- Post added at 06:34 PM ---------- Previous post was at 06:14 PM ----------
Once you are S-OFF it is permanent. Only way to get back to S-ON is with a fastboot command.
andybones said:
Thank you. I appreciate that.
Please try this
INSTRUCTIONS
1) Download this - MD5 = 55023CC10B59FDEC0AAA6695C4CF83FB
2) rename to PJ53IMG.zip (make sure it's not named PJ53IMG.zip.zip...)
3) put the PJ53IMG.zip on the root of your SD-Card. (not in any folders)
4) reboot to bootloader
5) let the phone do its magic
6) enjoy Sense 4.1
---------- Post added at 06:34 PM ---------- Previous post was at 06:14 PM ----------
Once you are S-OFF it is permanent. Only way to get back to S-ON is with a fastboot command.
Click to expand...
Click to collapse
Didnt work
jtdogblue said:
Didnt work
Click to expand...
Click to collapse
wow really
I'm thinking by unlocking bootloader you may have messed something up?
have you tried setting the phone back to the original CID?
andybones said:
wow really
I'm thinking by unlocking bootloader you may have messed something up?
have you tried setting the phone back to the original CID?
Click to expand...
Click to collapse
Yes, I had to set it to the original CID to get it re locked.
e:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.15.0000
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT26JS309742
(bootloader) imei: 990000641796059
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3639mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3321eb88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
e:\android>
jtdogblue said:
Yes, I had to set it to the original CID to get it re locked.
e:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.15.0000
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT26JS309742
(bootloader) imei: 990000641796059
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3639mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3321eb88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
e:\android>
Click to expand...
Click to collapse
only other thing I can think of is to try installing RUU using fastboot command
fastboot oem rebootRUU
also just for the heck of it (yes i know you are locked) but just for ****s and gigs, do a relock again, make sure the phone reboots, then try fastboot oem rebootRUU
andybones said:
only other thing I can think of is to try installing RUU using fastboot command
fastboot oem rebootRUU
also just for the heck of it (yes i know you are locked) but just for ****s and gigs, do a relock again, make sure the phone reboots, then try fastboot oem rebootRUU
Click to expand...
Click to collapse
I ran the fastboot oem rebootRUU and now its stuck on the darker black and silver htc screen...
jtdogblue said:
I ran the fastboot oem rebootRUU and now its stuck on the darker black and silver htc screen...
Click to expand...
Click to collapse
I think that is good..
should mean it's installing RUU..
andybones said:
I think that is good..
should mean it's installing RUU..
Click to expand...
Click to collapse
Well the first time I did it, it showed everything being done in hboot. I'll let it sit an hour or so and report back.
ok with it in the black screen, put the PJ53IMG.zip in your sdk folder and then do this command
fastboot flash zip PJ53IMG.zip
*you should now see it flashing things. do not for any reason interupt it during this process. when its finished:
fastboot reboot-bootloader
---------- Post added at 07:30 PM ---------- Previous post was at 07:29 PM ----------
jtdogblue said:
Well the first time I did it, it showed everything being done in hboot. I'll let it sit an hour or so and report back.
Click to expand...
Click to collapse
no need for that..
if it's installing in hboot ur good to go.
andybones said:
ok with it in the black screen, put the PJ53IMG.zip in your sdk folder and then do this command
fastboot flash zip PJ53IMG.zip
*you should now see it flashing things. do not for any reason interupt it during this process. when its finished:
fastboot reboot-bootloader
---------- Post added at 07:30 PM ---------- Previous post was at 07:29 PM ----------
no need for that..
if it's installing in hboot ur good to go.
Click to expand...
Click to collapse
NOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
e:\android>fastboot flash zip PJ53IMG.zip
sending 'zip' (583416 KB)...
OKAY [ 19.895s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 23.620s
jtdogblue said:
NOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
e:\android>fastboot flash zip PJ53IMG.zip
sending 'zip' (583416 KB)...
OKAY [ 19.895s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 23.620s
Click to expand...
Click to collapse
whoa, you did this when in the rebootRUU mode right?
the black with silver
I bought a T-Mobile USA HTC One from a guy who said it would randomly reboot. When I got it, it was S-ON had Bixie GE Rom and would reboot consistently about every 3 minutes. I managed to downgrade to get S-OFF and have spent a week trying every back-to-stock guide, RUU, firmware flash, Nandroid backup imaginable for both Sense and GE. On GE, I can at least get past the intro and use the phone until reboot, but Sense will always boot to the lock screen and never go further. Any Sense Rom or RUU would not bring up the initial setup. All still had a 3 minute reboot.
Of everything I tried, the [ROM] [AUG 3] [ANDROID 4.3] 3.06.1700.10 - Stock HTC Google Play Edition v1.1 was the only one to fix the reboot issue, but I'm still not able to get service (Baseband and IEMI unknown).
I accept there might be problem with the SIM slot, but does anyone happen to know why this particular Rom would work when everything else failed? All my Google-fu point toward using RUU's, but they simple will not stick, unlocked, relocked, stock recovery, you name it.
T-Mobile Kernel issue?
Any help is appreciated.
does it go into the bootloader and can you get fastboot usb going? try doing
Code:
fastboot getvar all
and see if it looks normal. use mine for reference.
This is after I tried stock
Sieze said:
does it go into the bootloader and can you get fastboot usb going? try doing
Code:
fastboot getvar all
and see if it looks normal. use mine for reference.
Click to expand...
Click to collapse
Yes, it goes into bootloader just fine. This is my getvar after my last attempt at T-Mo RUU:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA**********
(bootloader) imei: 355**************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4042mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.069s
looks normal too me. have you tried a cutsom kernel? and have you tried full GPE conversion at any time?
it deffinately sounds like the phone is being a boner. if you have TWRP flashed try doing a factory data reset through it and see if it has issues wiping certain things most namely cache and dalvik cache.
and if after you do that nothing presents itself make sure youve got a ROM zip in phone storage or on a flash drive for use with usb otg and wipe system then try and flash a stock ROM and see if it fixes it.
best of luck and hopefully you get it working.
Hello everyone,
I have a rooted, unlocked, s-on htc m8 with TWRP recovery, which I seem to have messed up pretty badly.
I was trying to follow a guide to convert my phone to GPe. Being a complete noob I stupidly overlooked the step:
"Connect your HTC One to your computer using a USB cable and copy the ROM file to your phone’s SD card root folder."
Actually I don't even know which file that would be since the zip-file I downloaded had a boot.img file but nothing with a .rom extension. Anyway I missed this step and flashed the boot.img file to my phone using fastboot
"Fastboot flash boot boot.img
fastboot reboot"
The phone got stuck in a boot loop hanging at the HTC splash. I managed to get to recovery and, after reading xda-university.com/as-a-user/how-to-recover-from-a-bootloop page I did a factory reset wiping the data cache and dalvik. Now if I try to boot it regularly it doesn't even get to the splash I just get a black screen. I can still get into the bootloader by holding power + vol up and then vol down once it reboots.
I could really use some help on this, I'm way out of my depth and the phone was a present from my gf . All I want now is to get the thing back to being a working phone.
Thanks in advance,
phb07jm said:
Hello everyone,
I have a rooted, unlocked, s-on htc m8 with TWRP recovery, which I seem to have messed up pretty badly.
I was trying to follow a guide to convert my phone to GPe. Being a complete noob I stupidly overlooked the step:
"Connect your HTC One to your computer using a USB cable and copy the ROM file to your phone’s SD card root folder."
Actually I don't even know which file that would be since the zip-file I downloaded had a boot.img file but nothing with a .rom extension. Anyway I missed this step and flashed the boot.img file to my phone using fastboot
"Fastboot flash boot boot.img
fastboot reboot"
The phone got stuck in a boot loop hanging at the HTC splash. I managed to get to recovery and, after reading xda-university.com/as-a-user/how-to-recover-from-a-bootloop page I did a factory reset wiping the data cache and dalvik. Now if I try to boot it regularly it doesn't even get to the splash I just get a black screen. I can still get into the bootloader by holding power + vol up and then vol down once it reboots.
I could really use some help on this, I'm way out of my depth and the phone was a present from my gf . All I want now is to get the thing back to being a working phone.
Thanks in advance,
Click to expand...
Click to collapse
So you have access to fastboot? Good, run this command "fastboot getvar all", remove the serial number and imei, and post the results. Good news? Running the proper RUU will fix this and only take about 15 minutes.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
bford152 said:
So you have access to fastboot? Good, run this command "fastboot getvar all", remove the serial number and imei, and post the results. Good news? Running the proper RUU will fix his and only take about 15 minutes.
Click to expand...
Click to collapse
BTW, you have to be S-off to convert to GPe
Thanks for the speedy reply!
That is good news! This is the output from getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0
(bootloader) version-baseband: 1.24.21331
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:~~~~~~~~~~~
(bootloader) imei: ~~~~~~~~~~~
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Is it just a question of downloading the stock RUU (presumably from htc) and running it while connected via fastboot USB.
Thanks again,
phb07jm said:
Thanks for the speedy reply!
That is good news! This is the output from getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0
(bootloader) version-baseband: 1.24.21331
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:~~~~~~~~~~~
(bootloader) imei: ~~~~~~~~~~~
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Is it just a question of downloading the stock RUU (presumably from htc) and running it while connected via fastboot USB.
Thanks again,
Click to expand...
Click to collapse
Hey, just download and run this from a PC... It'll update your AT&T device (I'm assuming) to Marshmallow Unlocked/Dev Ed http://www.htc.com/us/support/htc-one-m8/news/
Edit: BTW, make sure the phone is connected to the PC in fastboot mode
That worked perfectly!
Thanks so much for getting me out of trouble, and as a bonus updated to Marshmallow.
Okay, so I've got an AT&T M7 that has has (as far as I can tell - a stock version running 4.42 and HTC Sense 6.0) the Software number is 5.12.502.2.
The problem is, that apparently something is extremely corrupted - and I get messages like "Swiftkey has stopped", except replace Swiftkey with tons of other things, as it keeps happening over and over.
If I reboot, any changes that were made (downloads, settings, ANYTHING), apparently gets erased, or is not saved.
I can boot into recovery (which is TWRP 2.7.1.1, and again - any changes I make are not actually written. I can attempt to flash roms (cm, htc1guru stock images, etc.), and they will generally go through the motions of running - and even say 'successful' at the end, but if you reboot after that, everything is still as it was before. No changes at all (think of it like Groundhog Day... every day I can kill myself, eat whatever I want, kill other people(delete stuff, change things, add things) - but after the phone sleeps (aka restarts), the day (aka the phone) is reset as if I did absolutely nothing.)
I have tried wiping cache, data, system, literally EVERYTHING and it does absolutely nothing.
Also, if I try the main Factory Reset from inside the ROM itself, it says it is doing something, but then reboots and everything is back as it was also.
I've tried fastboot boot <insert multiple recovery images multiple times.img>, and it just locks up the phone and I have to hard restart it.
I've tried fastboot flash <new recovery.img> - it actually says successful, but again - does nothing after rebooting.
I am literally going crazy here... I can push files temporarily to the device, and try to do stuff with them, but in the end nothing can seem to make any difference.
I have tried going through htcdev unlock with Unlock_code.bin, and it doesn't do anything.
fastboot oem lock does nothing
Everything I've found says maybe S-OFF would help, but I can't seem to find any way to get that done.
Please, can ANYONE help me figure out how to get this stupid thing to be at all useful again? All help is appreciated. Below is my
e:\Downloads>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSOREDFORMYPARANOIA
(bootloader) imei: CENSOREDFORMYPARANOIA
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4272mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
Follow the unlock your bootloader thread..
wingsltd said:
Follow the unlock your bootloader thread..
Click to expand...
Click to collapse
Bootloader is unlocked, and I have tried re-unlocking. Nothing changes. I mean, I appreciate the input - but did you even read the post above? Answers like that make me feel like I'm talking to Tier I tech support at Gateway or something.