Related
Okay, a little background here:
HTC Evo 4G LTE
Android Version: 2.3.3
Baseband Version: 2.15.00.11.19
Kernel Version 2.6.37.4-cyanogenmod
Mod Version: 7.0.3.1-supersonic
Okay so i acquired this phone in a trade (upgrading from a Evo 4G) and have attempted to activate it with my sprint number. Every time I get to the step where I have to press ##etc... the phone will not cooperate. From what I understand, this is due to the lack of sense.
I have clockwork recovery premium installed and am familiar with the procedure for flashing a rom. I just need someone to point me in the right direction of which rom I need to install/do other things to get this phone activated.
Any help would be greatly appreciated! If any additional info is needed, please let me know! Thanks!
Grab one of the roms from the development section like meanrom and flash it over, wipe the phone first, if you have any trouble booting to android fastboot the kernel
om4 said:
Grab one of the roms from the development section like meanrom and flash it over, wipe the phone first, if you have any trouble booting to android fastboot the kernel
Click to expand...
Click to collapse
Thank you for the fast response.
Well, I may have already messed up. I saw the check for updates button in clockwork recovery and downloaded the newest cyanogen mod that it recommended ( 7.2. something I think, I can't remember). I flashed it and it is now stuck on the boot logo.
Could I apply the fastboot thing you are talking about to this situation? If so, how do I do that on windows 7? Sorry for my ignorance.
Just grab a sense Rom like mean and flash it, it has a kernel installer built in. You really should be using teamwin recovery
http://db.tt/zyPbGmtO
Extract that and open cmd inside the folder, connect to fastboot and type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img and once that's done flash meanrom
om4 said:
Just grab a sense Rom like mean and flash it, it has a kernel installer built in. You really should be using teamwin recovery
Extract that and open cmd inside the folder, connect to fastboot and type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img and once that's done flash meanrom
Click to expand...
Click to collapse
okay i did the steps to the best of my understanding and i got this response in cmd.
recovery-twrp-2.2.2.0-jewel.i
sending 'recovery' (7356 KB).
OKAY [ 1.901s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.902s
Any suggestions?
Hmm so write failed, odd
Gotta think about this one, maybe someone else has a solution already
om4 said:
Hmm so write failed, odd
Gotta think about this one, maybe someone else has a solution already
Click to expand...
Click to collapse
I can still access my clockwork recovery. Could I just put the mean rom on an sd card and flash it through clockwork? Thanks for your help.
Cwm is not very reliable on our phones. Try it but if it doesn't boot you will need to extract boot.img and place it in the adb folder and flash it using fastboot flash boot boot.img
om4 said:
Cwm is not very reliable on our phones. Try it but if it doesn't boot you will need to extract boot.img and place it in the adb folder and flash it using fastboot flash boot boot.img
Click to expand...
Click to collapse
Okay, so I attempted to flash through clockwork recovery and got this message
"Error in /sdcard/MeanROM-ICS-V47-jewel-ltevo.zip
(Status 0)
Installation aborted."
I guess the installer is dependant on twrp, I'm not that familiar with cwm though
om4 said:
I guess the installer is dependant on twrp
Click to expand...
Click to collapse
Okay, well is there any way I can just completely wipe it and get it back to stock? Or anything? Sorry, I am just kind of freaking out a little right now...
Well there is the ruu, I'd try fastboot again though
When in bootloader type fastboot devices to make sure its connected, and try to flash twrp again
om4 said:
Well there is the ruu, I'd try fastboot again though
When in bootloader type fastboot devices to make sure its connected, and try to flash twrp again
Click to expand...
Click to collapse
Well it identifies it using the fastboot devices cmd. I tried to flash it again on another computer ending in the same error.
Is there any way that the recovery package you linked to could be faulty or something?
You can try downloading it again from the twrp website but if it had been bad I'm sure it would have failed the signature verification
Try fastboot getvar all and tell me what the output is
om4 said:
You can try downloading it again from the twrp website but if it had been bad I'm sure it would have failed the signature verification
Try fastboot getvar all and tell me what the output is
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0001
(bootloader) version-baseband: 2.15.00.11.19
(bootloader) version-cpld: None
(bootloader) version-microp: 041f
(bootloader) version-main: 3.26.651.6
(bootloader) serialno: HT08THL01989
(bootloader) imei: 355195000000017
(bootloader) product: supersonic
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PC3610000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3655mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3b95cc40
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
can you still get into cm10? You can try installing twrp from goo manager. Install that and I'm menu install open recovery script. Otherwise relock the bootloader and run ruu, I can't think of any reason that fastboot can't flash recovery unless its locked but output states phone is soff
om4 said:
can you still get into cm10? You can try installing twrp from goo manager. Install that and I'm menu install open recovery script. Otherwise relock the bootloader and run ruu, I can't think of any reason that fastboot can't flash recovery unless its locked but output states phone is soff
Click to expand...
Click to collapse
No, every time I try to reboot into cm10 it will hang on the boot logo except one time when it booted into recovery. Could you link me a good guide to relock the bootloader and run ruu?
Is there any where else I can post this to get some additional input?
Since you're soff you can try the update zip twrp offers, it goes on root of sd card and bootloader will install. Don't forget to rename it to PJ75IMG.zip. Otherwise, download ruu and in fastboot relock bootloader "fastboot oem lock" and then run ruu
om4 said:
Since you're soff you can try the update zip twrp offers, it goes on root of sd card and bootloader will install. Don't forget to rename it to PJ75IMG.zip. Otherwise, download ruu and in fastboot relock bootloader "fastboot oem lock" and then run ruu
Click to expand...
Click to collapse
Well I can't get the phone to do anything now...its just showing a black screen (no backlight or anything). I was going to try to do the zip.
Have I messed up? Now I am getting worried
You can't get into bootloader at all? Have you tried holding power to reboot phone?
Hi guys,
This is my first post on XDA. Recently, I rooted my HTC one ATT to 4.3 google edition, and everything was fine. However today morning (November 27, 2013) i got a message that said I was able to upgrade to Android 4.4, so I pressed download and install. However, when i went into CWM, it glitched up, and my OS booting screen became green, and wouldn't boot I then decided to download the newest version of Cyanogenmod, since i had it on my SD card. However, CWM then said it was unable to mount the sd card, and then I had no idea what to do. As of right now, whenever i boot into cyanogen mod, it goes into the booting image, and then the phone turns off temporarily, and goes back to the cyanogenmod booting image. And when i try going into recovery, my phone just says "Entering Recovery" and doesn't respond. I've already tried flashing TWRP over CWM via fastboot, but that hasn't worked. I have been phoneless the whole day, and don't know what to do. Please help.
tl;dr installed 4.4, f'd up phone, recovery and OS not working
I believe that you need to flash the stock recovery for the GPE Rom.
Sent from my HTC One using Tapatalk
prith98 said:
Hi guys,
This is my first post on XDA. Recently, I rooted my HTC one ATT to 4.3 google edition, and everything was fine. However today morning (November 27, 2013) i got a message that said I was able to upgrade to Android 4.4, so I pressed download and install. However, when i went into CWM, it glitched up, and my OS booting screen became green, and wouldn't boot I then decided to download the newest version of Cyanogenmod, since i had it on my SD card. However, CWM then said it was unable to mount the sd card, and then I had no idea what to do. As of right now, whenever i boot into cyanogen mod, it goes into the booting image, and then the phone turns off temporarily, and goes back to the cyanogenmod booting image. And when i try going into recovery, my phone just says "Entering Recovery" and doesn't respond. I've already tried flashing TWRP over CWM via fastboot, but that hasn't worked. I have been phoneless the whole day, and don't know what to do. Please help.
tl;dr installed 4.4, f'd up phone, recovery and OS not working
Click to expand...
Click to collapse
NEVER TAKE OTA UPDATE ON CUSTOM RECOVERY !!!
Boot to bootloader / fastboot usb
then run the command
fastboot erase cache
now flash your recovery
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
and again fastboot erase cache
next fastboot reboot-bootloader
now try this ->> http://forum.xda-developers.com/showthread.php?t=2358781
clsA said:
NEVER TAKE OTA UPDATE ON CUSTOM RECOVERY !!!
Boot to bootloader / fastboot usb
then run the command
fastboot erase cache
now flash your recovery
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
and again fastboot erase cache
next fastboot reboot-bootloader
now try this ->> http://forum.xda-developers.com/showthread.php?t=2358781
Click to expand...
Click to collapse
When I run "sudo ./fastboot flash recovery ~/Downloads/openrecovery-twrp-2.6.3.3-m7.img" I get
Code:
sending 'recovery' (9184 KB)...
OKAY [ 1.198s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.158s
Should I carry on going through the steps?
janne_oksanen said:
When I run "sudo ./fastboot flash recovery ~/Downloads/openrecovery-twrp-2.6.3.3-m7.img" I get
Code:
sending 'recovery' (9184 KB)...
OKAY [ 1.198s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.158s
Should I carry on going through the steps?
Click to expand...
Click to collapse
no you need to download the file again and do a md5 check that the file is not corrupt
and flash again. I would also move the file to the same directory as fastboot
clsA said:
no you need to download the file again and do a md5 check that the file is not corrupt
and flash again. I would also move the file to the same directory as fastboot
Click to expand...
Click to collapse
I checked the checksum, it matches. Moved the file to the same dir as fastboot, still getting the same error. Also the link to the rest of the instruction is no good, because I don't have s-off and I have HBOOT-1.54.000.
janne_oksanen said:
I checked the checksum, it matches. Moved the file to the same dir as fastboot, still getting the same error. Also the link to the rest of the instruction is no good, because I don't have s-off and I have HBOOT-1.54.000.
Click to expand...
Click to collapse
rumrunner works with hboot 1.54
give me the results from fastboot getvar all
and we can try and find you a RUU to flash
clsA said:
rumrunner works with hboot 1.54
give me the results from fastboot getvar all
and we can try and find you a RUU to flash
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [sorry, not giving out this ;]
(bootloader) imei: [sorry, not giving out this ;]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
@janne_oksanen
delete sorry you have no recovery
Edit: If you do manage to get twrp flashed try this Guru Reset
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
I'm sorry but everything i find requires you have s-off or at least custom recovery installed
maybe someone else can help you
I'm in the same unfortunate boat as OP. I haven't been able to boot or enter recovery or download mood, just a blue screen. Am I just borked?
Hello,
My HTC One m7 was bootloader unlocked and I used TWRP 2.8.4.0 recovery. I also installed CyanogenMod 10.2.1. Last night while playing music, the phone restarted on its own and got stuck on a boot loop (just boots to a white HTC screen and restarts to the same after 10-15 sec). Now the Phone is not recognized in adb (is blank under devices connected, another phone shows up fine) but I can send across commands (reboot to bootloader, relock bootloader...etc). I tried flashing the recovery again, but it says it went across fine, but gets to the boot loop again. I tried flashing the HTC factory ruu, it goes for about 22%, says it is complete but get to the bootloop again. Please help :crying:
Hboot - 1.55
Simpleusername said:
Hello,
My HTC One m7 was bootloader unlocked and I used TWRP 2.8.4.0 recovery. I also installed CyanogenMod 10.2.1. Last night while playing music, the phone restarted on its own and got stuck on a boot loop (just boots to a white HTC screen and restarts to the same after 10-15 sec). Now the Phone is not recognized in adb (is blank under devices connected, another phone shows up fine) but I can send across commands (reboot to bootloader, relock bootloader...etc). I tried flashing the recovery again, but it says it went across fine, but gets to the boot loop again. I tried flashing the HTC factory ruu, it goes for about 22%, says it is complete but get to the bootloop again. Please help :crying:
Hboot - 1.55
Click to expand...
Click to collapse
are you still stuck ?
Boot Loop
clsA said:
are you still stuck ?
Click to expand...
Click to collapse
Yup...still stuck. Had been travelling, so didn't try much in the last two days. Adb does not recognize the decive, but fastboot commands work. CANNOT push recovery as it says it is a success, but Can't boot to recovery.
Simpleusername said:
Yup...still stuck. Had been travelling, so didn't try much in the last two days. Adb does not recognize the decive, but fastboot commands work. CANNOT push recovery as it says it is a success, but Can't boot to recovery.
Click to expand...
Click to collapse
Did you relock the bootloader to flash the RUU ? and did you unlock it to flash TWRP again ?
Boot Loop
clsA said:
Did you relock the bootloader to flash the RUU ? and did you unlock it to flash TWRP again ?
Click to expand...
Click to collapse
Yes. I did.
Simpleusername said:
Yes. I did.
Click to expand...
Click to collapse
The next step i would take is format data in TWRP, but be aware this will totally wipe the phone, sdcard and all
you would then need to flash a rom back to the phone
After that your option is to relock and reflash the same firmware your on now
Boot Loop
clsA said:
The next step i would take is format data in TWRP, but be aware this will totally wipe the phone, sdcard and all
you would then need to flash a rom back to the phone
After that your option is to relock and reflash the same firmware your on now
Click to expand...
Click to collapse
As long as I can get the Phone working, I don't care about the data. But I can't get to recovery. can you post the steps.
Simpleusername said:
As long as I can get the Phone working, I don't care about the data. But I can't get to recovery. can you post the steps.
Click to expand...
Click to collapse
Try this
If you just simply want it working, just follow this, note that unlocking the bootloader will erase the entire contents of your phone.
you can unlock your bootloader with your phone in bootloader mode, follow the instructions here, http://www.htcdev.com/bootloader
your bootloader now says TAMPERED and UNLOCKED at the top, your warranty is now void.
the instructions will provide you with some files, adb and fastboot, keep hold of those, you will need them.
once your bootloader is unlocked, flash 2.6.3.3 recovery from here, (2.6.3.3 is the most compatible to date, all the others give some sort of problem) http://techerrata.com/browse/twrp2/m7
download the recovery file, place it in the same folder as fastboot and adb on your computer, and with your phone in bootloader/fastbootUSB mode type
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
download this: http://www.androidfilehost.com/?fid=23501681358545274
again put it in the same folder as adb and fastboot, for ease rename the file to rom.zip
enter recovery (main screen only, no sub menu's) and type:
adb push rom.zip /sdcard/
it will appear unresponsive, takes about 5 mins to push, once done, the cmd window will let you know.
unplug your phone and then in recovery select install, and select rom.zip from the list, swipe to begin the install, follow the on screen instructions.
Click to expand...
Click to collapse
Boot Loop
clsA said:
Try this
Click to expand...
Click to collapse
I don't have the phone with me, I'll try it tomorrow. Thanks.
Boot Loop
clsA said:
Try this
Click to expand...
Click to collapse
I tried the steps, but still no-go. The recovery goes through fine (acc. to cmd prompt)...I erase cache, reboot to bootloader and try to go to recovery, It says booting to recovery and then resumes the bootloop. I tried different recoveries, does not work. Could one reason be that USB debugging might have been disabled...? I don't know if that matters at this point, since I can't boot to anywhere and the memory is wiped clean, but I'm out of ideas and clutching at straws.
BTW...I found this thread that could explain something about this. If true...well so much for a graduation present.
http://forums.androidcentral.com/ht...ootloader-can-t-get-into-recovery-help-3.html
Simpleusername said:
I tried the steps, but still no-go. The recovery goes through fine (acc. to cmd prompt)...I erase cache, reboot to bootloader and try to go to recovery, It says booting to recovery and then resumes the bootloop. I tried different recoveries, does not work. at this point, I'm out of ideas.
Click to expand...
Click to collapse
Flash a ROM
Sent from my SM-A500FU using XDA Free mobile app
Boot Loop
mygalaxya said:
Flash a ROM
Sent from my SM-A500FU using XDA Free mobile app
Click to expand...
Click to collapse
Cannot flash a ROM as adb does not recognise device.
Simpleusername said:
I tried the steps, but still no-go. The recovery goes through fine (acc. to cmd prompt)...I erase cache, reboot to bootloader and try to go to recovery, It says booting to recovery and then resumes the bootloop. I tried different recoveries, does not work. Could one reason be that USB debugging might have been disabled...? I don't know if that matters at this point, since I can't boot to anywhere and the memory is wiped clean, but I'm out of ideas and clutching at straws.
BTW...I found this thread that could explain something about this. If true...well so much for a graduation present.
http://forums.androidcentral.com/ht...ootloader-can-t-get-into-recovery-help-3.html
Click to expand...
Click to collapse
usb debugging is only for when the phone is booted up to android os
post your fastboot getvar all and we can try stock recovery or firmware flash
Also please list all the files you have tried / RUU / Recovery / anything else
Boot Loop
clsA said:
usb debugging is only for when the phone is booted up to android os
post your fastboot getvar all and we can try stock recovery or firmware flash
Also please list all the files you have tried / RUU / Recovery / anything else
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(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: 4091mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
File Versions tried -
TWRP - 2.8.4.0
TWRP - 2.6.3.3
ROMS - CM 10.2.1
Factory RUU - RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
Simpleusername said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(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: 4091mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
File Versions tried -
TWRP - 2.8.4.0
TWRP - 2.6.3.3
ROMS - CM 10.2.1
Factory RUU - RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
Click to expand...
Click to collapse
Everything looks ok
lock the bootloader - fastboot oem lock
Flash this firmware > https://www.dropbox.com/s/o1o487pmdfi9dyo/firmware_3.17.502.3.zip?dl=0
fastboot oem rebootRUU
fastboot flash zip firmware_3.17.502.3.zip
fastboot flash zip firmware_3.17.502.3.zip
fastboot reboot-bootloader
it will replace your recovery with the stock recovery
from bootloader choose recovery, wait a few seconds and hold volume up and tap power
this will bring up the menu in stock recovery
choose Factory Reset, when it finishes try and boot up your phone. if it won't boot try the RUU again
Be sure you RUU is not corrupt check it's md5 it should be >
Filename: RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe
MD5: 20f152644d2187b158ca9cdc887db40a
Click to expand...
Click to collapse
Boot Loop
clsA said:
Everything looks ok
lock the bootloader - fastboot oem lock
Flash this firmware > https://www.dropbox.com/s/o1o487pmdfi9dyo/firmware_3.17.502.3.zip?dl=0
fastboot oem rebootRUU
fastboot flash zip firmware_3.17.502.3.zip
fastboot flash zip firmware_3.17.502.3.zip
fastboot reboot-bootloader
it will replace your recovery with the stock recovery
from bootloader choose recovery, wait a few seconds and hold volume up and tap power
this will bring up the menu in stock recovery
choose Factory Reset, when it finishes try and boot up your phone. if it won't boot try the RUU again
Be sure you RUU is not corrupt check it's md5 it should be >
Click to expand...
Click to collapse
I did that and I get
C:\HTC\adb_fastboot_drivers>fastboot flash zip firmware_3.17.502.3.zip
sending 'zip' (40022 KB)...
OKAY [ 3.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.296s.
Now, when I try to boot to recovery, it reboots to fastboot. Even factory reset in bootloader does the same and reboots to fastboot.
I then tried the factory RUU. MD5 checked, Antivirus, Firewall disabled. Run it as admin. samething. Update window on PC goes upto 22% and stays there, bar on phone goes through to completion and then I get a "Your ROM update has been completed. Your phone is ready to use" and back to the bootloop AGAIN...
Simpleusername said:
I did that and I get
C:\HTC\adb_fastboot_drivers>fastboot flash zip firmware_3.17.502.3.zip
sending 'zip' (40022 KB)...
OKAY [ 3.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.296s.
Now, when I try to boot to recovery, it reboots to fastboot. Even factory reset in bootloader does the same and reboots to fastboot.
I then tried the factory RUU. MD5 checked, Antivirus, Firewall disabled. Run it as admin. samething. Update window on PC goes upto 22% and stays there, bar on phone goes through to completion and then I get a "Your ROM update has been completed. Your phone is ready to use" and back to the bootloop AGAIN...
Click to expand...
Click to collapse
you can extract the rom.zip from your windows temp folder when the RUU is running
copy it to your fastboot folder and try and flash it manually
fastboot oem rebootRUU
fastboot flash zip Rom.zip
fastboot flash zip Rom.zip
fastboot reboot-bootloader
Boot Loop
clsA said:
you can extract the rom.zip from your windows temp folder when the RUU is running
copy it to your fastboot folder and try and flash it manually
fastboot oem rebootRUU
fastboot flash zip Rom.zip
fastboot flash zip Rom.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
I used this method to get it...
http://forum.xda-developers.com/showthread.php?t=2534428
Didn't work. Just as before, the flash is successful, but reboots to the bootloop. Also, while going through the cmd process logs, I found a failure
start image[sbl1-1] unzipping & flushing...
[RUU]UZ,sbl1-1,0
[RUU]UZ,sbl1-1,100
signature checking...
verified fail
I don't know what that means, but maybe someone can make sense of it.
Simpleusername said:
I used this method to get it...
http://forum.xda-developers.com/showthread.php?t=2534428
Didn't work. Just as before, the flash is successful, but reboots to the bootloop. Also, while going through the cmd process logs, I found a failure
start image[sbl1-1] unzipping & flushing...
[RUU]UZ,sbl1-1,0
[RUU]UZ,sbl1-1,100
signature checking...
verified fail
I don't know what that means, but maybe someone can make sense of it.
Click to expand...
Click to collapse
that fail is meaningless the RUU contains files for more than one phone and the files that are not for your phone just say fail
If you look the same files will say success further down (or up)
If your phone is still in a bootloop after RUU and factory reset from stock recovery I have no more ideas
Boot Loop
clsA said:
that fail is meaningless the RUU contains files for more than one phone and the files that are not for your phone just say fail
If you look the same files will say success further down (or up)
If your phone is still in a bootloop after RUU and factory reset from stock recovery I have no more ideas
Click to expand...
Click to collapse
Yeah, I guessed that's pretty much it. I'll prob sell it for parts on ebay. Thanks for your help nonetheless.
Hi all,
My girlfriend got a China Mobile htc Desire 610t.
When I tried to unlock / use CWM recovery / root in order to upgrade it to a regular (non-chinese) Android, I got stuck at some point and now the phone keeps booting into FASTBOOT... even when I say POWER DOWN, it'll come back to FASTBOOT
Any ideas? I looked at several other posts but none of the suggested things seem to work.
The main problem from the beginning of my efforts was that I can't seem to get into recovery mode... the phone says "Entering Recovery..." but then it just goes back to FASTBOOT.
I also tried to find an RUU but none I found for the htc 610 would pass the signature check.
Any ideas?
getvar gives me these details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.101.1161.16.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.37.1403.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HC45NWS02483
(bootloader) imei: not needed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a3_tl
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9O50000
(bootloader) cidnum: HTCCN704
(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: 04768f7d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any help is highly appreciated!!!
Martin
MartinNeedsHelp said:
Hi all,
My girlfriend got a China Mobile htc Desire 610t.
When I tried to unlock / use CWM recovery / root in order to upgrade it to a regular (non-chinese) Android, I got stuck at some point and now the phone keeps booting into FASTBOOT... even when I say POWER DOWN, it'll come back to FASTBOOT
Any ideas? I looked at several other posts but none of the suggested things seem to work.
The main problem from the beginning of my efforts was that I can't seem to get into recovery mode... the phone says "Entering Recovery..." but then it just goes back to FASTBOOT.
I also tried to find an RUU but none I found for the htc 610 would pass the signature check.
Any ideas?
getvar gives me these details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.101.1161.16.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.37.1403.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HC45NWS02483
(bootloader) imei: not needed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a3_tl
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9O50000
(bootloader) cidnum: HTCCN704
(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: 04768f7d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any help is highly appreciated!!!
Martin
Click to expand...
Click to collapse
One more thing, while the phone tries to get into recovery mode, I see the following text in red at the bottom of the screen:
"This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action."
hi
try reflash twrp recovery by dd Install Method if you have rooted device.
Thanks for the quick reply.
Since I was never able to get into recovery mode, the device is unlocked but not rooted.
So the SU method won't work.
I can place fastboot commands and flashed different recovery packages already (twrp, cwm, stock) unfortunately without success. The phone just won't load the recovery mode.
Any ideas?
The desire 610 doesn't support any custom recoveries besides TWRP. I dint know why u used CWM because it doesn't support the desire 610. So if u flash TWRP for the a3_tl it should be fine.
Sent from my HTC Desire 610 using XDA Free mobile app
try this methode:
Fastboot Install Method (No Root Required):
You will need the platform-tools from the Android SDK on your computer. Find the SDK Only section on the page linked and install the SDK and download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on your computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
adb reboot bootloader
You should now be in fastboot mode. Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
there is direct link: TWRP
michelkovacic said:
try this methode:
Fastboot Install Method (No Root Required):
You will need the platform-tools from the Android SDK on your computer. Find the SDK Only section on the page linked and install the SDK and download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on your computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
adb reboot bootloader
You should now be in fastboot mode. Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
there is direct link:
Click to expand...
Click to collapse
Thanks michelkovacic, I had tried that already - even with different versions of TWRP - unfortunately with no success.
I tried it again now and installed twrp-2.8.7.0-a3ul.img. Got the OKAY / OKAY in the cmd windows but when I choose "RECOVERY" in HBOOT, I see the htc logo for a short second and am back in FASTBOOT (or FASTBOOT USB if the USB is still connected).
I tried to find "the proper key combo to enter recovery"... but was unsuccessfull... Also, I don't know when to push it. E.g. I never get the screen with the red attention sign like with most stock recoveries where you can then press keys... this D610 jumps right back into the FASTBOOT menu...
Reading MGfusion's reply, I noticed that I had used the wrong TWRP... all I can find for the D610 is for a3_ul... but mine is a3_tl...!
Any idea where I can find that TWRP or even the stock recovery for that model?
Googling didn't help much and only sent my Antivirus into a frenzy...
Any more ideas?
MGfusion said:
The desire 610 doesn't support any custom recoveries besides TWRP. I dint know why u used CWM because it doesn't support the desire 610. So if u flash TWRP for the a3_tl it should be fine.
Sent from my HTC Desire 610 using XDA Free mobile app
Click to expand...
Click to collapse
Hi MGfusion,
I tried several versions of TWRP first, none of them worked (--> after flashing them and hitting "RECOVERY" in HBOOT, I always saw the htc logo for a quick second and was right back in the FASTBOOT menu...)
So you mention "the a3_tl"... when I search for the TWRP for the D610, I always see the "a3ul"... maybe that's my problem?!
Any tipps, where I can find the TWRP recovery for a3_tl? So far I only got malware offered...
Thanks!
a3ul I's the same as a3tl it just means they are from models from different regions
Sent from my HTC Desire 610 using XDA Free mobile app
any progress?
I got the same china mobile version D610T and stuck at same place~~
MGfusion said:
a3ul I's the same as a3tl it just means they are from models from different regions
Sent from my HTC Desire 610 using XDA Free mobile app
Click to expand...
Click to collapse
OK, I just - again - flashed every available a3_ul TWRP... without success.
I tried
twrp-2.8.7.0-a3ul.img 11.3M
twrp-2.8.6.0-a3ul.img 11.2M
twrp-2.8.5.0-a3ul.img 11.1M
twrp-2.8.4.0-a3ul.img 11.1M
twrp-2.8.3.0-a3ul.img 11.1M
twrp-2.8.1.0-a3ul.img 11M
twrp-2.8.0.1-a3ul.img 10.8M
twrp-2.8.0.0-a3ul.img 10.8M
twrp-2.7.1.0-a3ul.img 10.7M
and always got an OKAY / OKAY from fastboot, did the reboot, tried to get into recovery and... was back to FASTBOOT.
Again, for a quick second I see "Entering Recovery..." on the top and bam, I'm back in FASTBOOT.
The FASTBOOT screen shows "*** TAMPERED ***" and "*** UNLOCKED ***" on top.
There must be something I could do...?!
I also tried to find an RUU but none worked with my phone. They all failed the signature check.
Any help would be highly appreciated!
flyingcowboy said:
any progress?
I got the same china mobile version D610T and stuck at same place~~
Click to expand...
Click to collapse
Unfortunately not .
:crying::crying::crying:
MartinNeedsHelp said:
Unfortunately not .
Click to expand...
Click to collapse
Hi,
Are you still having issues? If so check this article out: http://forum.xda-developers.com/desire-610/general/info-htcdev-unlock-root-t2844323 I had the same issue with being stuck in fastboot and went through the HTCDev bootloader unlock. It gives you step by step instructions on how to unlock the bootloader. If phone shows unlocked in fastboot I would just command "fastboot oem lock" that'll relock it, then do the htcdev bootloader unlock.
HTCDev Bootloader Unlock: "Under "Select Your Device", scroll ALL THE WAY TO THE BOTTOM, and choose "All Other Supported Models". I know it works, because I just did it. IT WILL WIPE YOUR DEVICE DATA."
Hope this helps.
Sent from my HTC Desire 610 using XDA Free mobile app
Thanks for the tip!
I'll make sure I try that when I'm back at home, out if town for a couple weeks.
stuck in boot loader - ClearD Please help!!!!
MartinNeedsHelp said:
Thanks for the tip!
I'll make sure I try that when I'm back at home, out if town for a couple weeks.
Click to expand...
Click to collapse
i tried relocking my bootloader so that i could update the RUU..unfortunately my phone now does not turn on...it keeps booting and rebooting to fastboot...i cant access recovery...each time i try it reboots to the htc logo but then goes straight to the fastboot menu...i can access the phone through cdm or adb but my pc does not recognize the phone in my computer...this is my only phone and im afraid that i might have bricked the device....please anyone if u have any knowledge on how to solve this issue, i would greatly appreciate it...by any chance the person that started this topic Martinneedshelp could assist me....any one please:crying:
Unfortunately my phone is also still in that state. Nothing really worked so far. So as long as no one here has any further ideas, I think we're screwed.
MartinNeedsHelp said:
Unfortunately my phone is also still in that state. Nothing really worked so far. So as long as no one here has any further ideas, I think we're screwed.
Click to expand...
Click to collapse
Luckily i got my phone to boot...the solution i found was to download a RUU file...from the htc ROM downloads page...ran it from my pc with the phone connected...it updated the rom and booted the phone...
My problem now is with the wifi not connecting...i had this problem b4 after rooting the phone...ClearD was kind enough to assist me in getting that fixed by booting into recover and wiping dalvik cache...that was successful then but now since i dont have root access anymore, i dont have twrp installed therefore i cant boot into recovery to wipe dalvik..
I dont want to root the phone again so i was wondering if anyone had a solution in getting the wifi to work...
Find another way to wipe the dalvik cache
Sent from my HTC Desire 610 using XDA Free mobile app
same problem with same cid
any help ? ((((
my phone only fastboot!
Hey everyone,
I lately tried to root my HTC One M8, but due to some mistakes I got stuck and just have access to the bootloader,but I'm not able to get in my phone. I've have unlocked the bootloader and have S-On. I would be pleased, if someone could tell me how I reset my phone to factory state. I'm pretty new to such things, so let me know if you need further informations. I really hope that you guys can help me, all of this made so frustrated.
Thanks in advance
Matthew F.
You have access to Bootloader. Can you Boot into recovery? There you will find a selection for factory reset.
http://www.androidcentral.com/sites...arge/public/postimages/108579/m7-recovery.jpg
I can't confirm that's the best course to take, but its there if recovery is.......
If that does not work, then you will need to relock the bootloader and run the RUU for your variant of the M8, and it must be the same version or newer. You can not downgrade while S-On.
Cremnomaniac said:
You have access to Bootloader. Can you Boot into recovery? There you will find a selection for factory reset.
I can't confirm that's the best course to take, but its there if recovery is.......
Click to expand...
Click to collapse
I can't get in recovery, it just goes back to the bootloader
es0tericcha0s said:
If that does not work, then you will need to relock the bootloader and run the RUU for your variant of the M8, and it must be the same version or newer. You can not downgrade while S-On.
Click to expand...
Click to collapse
I tried to install the ruu, but everytime I get this message 'Error 120: low main battery' and the install Setup stops
It has to be above 30% before it will run, if I remember right.
es0tericcha0s said:
It has to be above 30% before it will run, if I remember right.
Click to expand...
Click to collapse
Yeah that's right, but my battery is about 70%
It might not be due to the software being messed up and the bright white screen of the bootloader. You can try extracting the rom.zip from the RUU exe and flashing via fastboot manually. http://forum.xda-developers.com/showthread.php?t=2497614 - this is for the M7 but the same basic principles apply. I don't believe that it requires the 30% this method, but it's been a bit since I have flashed manually.
es0tericcha0s said:
It might not be due to the software being messed up and the bright white screen of the bootloader. You can try extracting the rom.zip from the RUU exe and flashing via fastboot manually. http://forum.xda-developers.com/showthread.php?t=2497614 - this is for the M7 but the same basic principles apply. I don't believe that it requires the 30% this method, but it's been a bit since I have flashed manually.
Click to expand...
Click to collapse
so, I've followed this guide, but now I'm stuck again. Everytime I type in this command 'fastboot flash zip C:/mini-sdk/rom.zip' I get a error-message 'target reported max download size of 1826418688 Bytes error: cannot load 'C:/mini-sdk/Rom.zip'.
Any ideas for that?
Is the rom zip IN the folder titled C:/mini-sdk?
Yes, it is.
es0tericcha0s said:
Is the rom zip IN the folder titled C:/mini-sdk?
Click to expand...
Click to collapse
Yes, it is.
If your command prompt is already pointed to the adb/fastboot folder then you should be able to just use the command:
fastboot flash zip rom.zip
instead of fastboot flash zip C:/blahblahblah
es0tericcha0s said:
If your command prompt is already pointed to the adb/fastboot folder then you should be able to just use the command:
fastboot flash zip rom.zip
instead of fastboot flash zip C:/blahblahblah
Click to expand...
Click to collapse
The command prompt is already pointed in the adb/fastboot Folder, but i still get the same error ('target reported max download size of...'). Do my phone has to be unlocked or locked, S-on or S-off at that Moment?
Locked if S-On. S-Off, either way.
es0tericcha0s said:
Locked if S-On. S-Off, either way.
Click to expand...
Click to collapse
hmm... it already was relocked and s-on. What do I have to do?
and the Software Status says 'Modified', if that's necessary
Matthew F. said:
so, I've followed this guide, but now I'm stuck again. Every time I type in this command 'fastboot flash zip C:/mini-sdk/rom.zip' I get a error-message 'target reported max download size of 1826418688 Bytes error: cannot load 'C:/mini-sdk/Rom.zip'.
Any ideas for that?
Click to expand...
Click to collapse
I'm not sure this is the problem, but it sounds familiar. It may be the version of adb/fastboot you're using. Try using this one posted by Dottat.
Its the Fastboot link at the bottom of the OP
http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
Read about the options for installing RUUs. There's a few.
PS - Its customary when asking for help to provide some basic info about your phone. I don't see that you have even mentioned which ROM your currently running. There are RUUs for s-on and s-off.
Cremnomaniac said:
I'm not sure this is the problem, but it sounds familiar. It may be the version of adb/fastboot you're using. Try using this one posted by Dottat.
Its the Fastboot link at the bottom of the OP
http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
Read about the options for installing RUUs. There's a few.
PS - Its customary when asking for help to provide some basic info about your phone. I don't see that you have even mentioned which ROM your currently running. There are RUUs for s-on and s-off.
Click to expand...
Click to collapse
Sorry sir, I'm using this ROM https://www.androidfilehost.com/?fid=95916177934546378 (should be the right one) and here are some Infos about my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH485WM02248
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP102
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 21(ms)
I also downloaded Dottat's fastboot/adb Version and typed in following commands:
-fastboot oem rebootRUU (no Problem with this command)
-fastboot Flash zip 0P6B10000.zip (renamed it after my mid)
But then I get this error-message:
C:\Users\Frank\Desktop\HTC_fastboot_adb>fastboot flash zip 0P6B10000.zip
sending 'zip'... (46606 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
FAIL32 header error
FAILED (remote: 32 header error)
Execution time is 8(s)
Any ideas for this Problem?
PS - I wouldn't have come this far without your help, so thank you
Matthew F. said:
Sorry sir, I'm using this ROM https://www.androidfilehost.com/?fid=95916177934546378 (should be the right one)
I also downloaded Dottat's fastboot/adb Version and typed in following commands:
-fastboot oem rebootRUU (no Problem with this command)
-fastboot Flash zip 0P6B10000.zip (renamed it after my mid)
But then I get this error-message:
C:\Users\Frank\Desktop\HTC_fastboot_adb>fastboot flash zip 0P6B10000.zip
sending 'zip'... (46606 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
FAIL32 header error
FAILED (remote: 32 header error)
Execution time is 8(s)
Any ideas for this Problem?
PS - I wouldn't have come this far without your help, so thank you
Click to expand...
Click to collapse
May I suggest that you do some more research BEFORE you use that file.
The file you link to is an RUU! Executable. I know, I just downloaded it and opened it to be sure.
If your renaming it, and trying to use fastboot, you are using the wrong file. The file your trying to flash is NOT flash-able via fastboot. Again, its an RUU.exe file. If you don't know what that is, you shouldn't be using it.
Do some research on RUU's......