[Q] Another plea for help! - AT&T HTC One (M7)

I attempted to install the latest Viper ROM over the Viper I had currently on my HTC One. It said it installed, then went to reboot, and stayed on the white screen for a while. I rebooted, but it did the same thing again. I got to looking in TWRP and it didn't have an OS installed, and it had wiped my backups. Now, I can get to TWRP, and I can get to Fastboot, but I can't connect with ADB. I have an OTG USB cable, but when I try to install a zip from my USB drive, I get the error message, "E:Unable to mount '/system'". When I go to MOUNT in TWRP, it won't let me select System to mount it.
I thought this would be the perfect time to go with the GPE RUU, but I can't connect with ADB.
What do I do? (deep breaths taken already)

try formating your data in twrp then reboot into recovery then mount usb-otg and flash or transver then rom to sd card

rushwal said:
I attempted to install the latest Viper ROM over the Viper I had currently on my HTC One. It said it installed, then went to reboot, and stayed on the white screen for a while. I rebooted, but it did the same thing again. I got to looking in TWRP and it didn't have an OS installed, and it had wiped my backups. Now, I can get to TWRP, and I can get to Fastboot, but I can't connect with ADB. I have an OTG USB cable, but when I try to install a zip from my USB drive, I get the error message, "E:Unable to mount '/system'". When I go to MOUNT in TWRP, it won't let me select System to mount it.
I thought this would be the perfect time to go with the GPE RUU, but I can't connect with ADB.
What do I do? (deep breaths taken already)
Click to expand...
Click to collapse
did you flash the newest version of TWRP 2.6.3.3 ?
When I flash from the usb otg adapter
I shut the phone completely off
hookup the cable and flash drive
bootup recovery / select wipe/ factory reset / then install
on the install screen I browse to the usb otg by tapping the Storage: and choosing usb otg
then back and when you choose install again you should be in the root of the flash drive
choose your rom and install. first boot up sometimes takes over 5 min to complete be patient before you give up and reboot the phone from the white htc screen.

clsA said:
did you flash the newest version of TWRP 2.6.3.3 ?
When I flash from the usb otg adapter
I shut the phone completely off
hookup the cable and flash drive
bootup recovery / select wipe/ factory reset / then install
on the install screen I browse to the usb otg by tapping the Storage: and choosing usb otg
then back and when you choose install again you should be in the root of the flash drive
choose your rom and install. first boot up sometimes takes over 5 min to complete be patient before you give up and reboot the phone from the white htc screen.
Click to expand...
Click to collapse
How do I install new version of TWRP other than by methods on the TWRP web page? If I can't adb, can't do it by app?
http://teamw.in/project/twrp2/164
When I try to Factory Reset, I get the cannot mount SYSTEM error.
When I try to install, I get the cannot mount SYSTEM error.
Terror starting to creep in despite deep breaths.

rushwal said:
How do I install new version of TWRP other than by methods on the TWRP web page? If I can't adb, can't do it by app?
http://teamw.in/project/twrp2/164
When I try to Factory Reset, I get the cannot mount SYSTEM error.
When I try to install, I get the cannot mount SYSTEM error.
Terror starting to creep in despite deep breaths.
Click to expand...
Click to collapse
Here is the recovery flashable version of twrp 2.6.3.3
Turn the phone completely off (hold power for 10-15 seconds)
now boot to recovery power + vol down
then flash the file below and repeat the power off

thanks!

clsA said:
Here is the recovery flashable version of twrp 2.6.3.3
Turn the phone completely off (hold power for 10-15 seconds)
now boot to recovery power + vol down
then flash the file below and repeat the power off
Click to expand...
Click to collapse
Still getting Unable to mount System error.

rushwal said:
Still getting Unable to mount System error.
Click to expand...
Click to collapse
can you post the results for fastboot getvar all and maybe you can RUU back to stock

clsA said:
can you post the results for fastboot getvar all and maybe you can RUU back to stock
Click to expand...
Click to collapse
I'm not able to connect via ADB.

rushwal said:
I'm not able to connect via ADB.
Click to expand...
Click to collapse
Have you tried fastboot from the bootloader screen?
What os is on your PC?
How did you unlock the bootloader to get twrp?
Sent from my HTC One using Tapatalk

clsA said:
Have you tried fastboot from the bootloader screen?
What os is on your PC?
How did you unlock the bootloader to get twrp?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
If I power up the device, it starts up into TWRP. If I hold down pwr+vol down, I can get into fastboot, but I haven't found anything I can do from there except boot into recovery.
I've been using my Windows 8.1 laptop, but I also have access to a Windows 7.
I used the HTC dev web site to unlock back when I got it. I had to do the change to Rogers device in order to unlock. It's been a while since I did this, and I've been running Viper ROM for so long, I don't remember everything I've done.
Thanks for your help!

rushwal said:
If I power up the device, it starts up into TWRP. If I hold down pwr+vol down, I can get into fastboot, but I haven't found anything I can do from there except boot into recovery.
I've been using my Windows 8.1 laptop, but I also have access to a Windows 7.
I used the HTC dev web site to unlock back when I got it. I had to do the change to Rogers device in order to unlock. It's been a while since I did this, and I've been running Viper ROM for so long, I don't remember everything I've done.
Thanks for your help!
Click to expand...
Click to collapse
From the win 7 PC boot to the bootloader fastboot USB and run the command fastboot getvar all and post your results
This will tell what hboot your on and the mainver of your firmware, so you can determine which RUU will return your phone to Stock
Sent from my HTC One using Tapatalk

clsA said:
From the win 7 PC boot to the bootloader fastboot USB and run the command fastboot getvar all and post your results
This will tell what hboot your on and the mainver of your firmware, so you can determine which RUU will return your phone to Stock
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks, I will try when I get home.

clsA said:
From the win 7 PC boot to the bootloader fastboot USB and run the command fastboot getvar all and post your results
This will tell what hboot your on and the mainver of your firmware, so you can determine which RUU will return your phone to Stock
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Ok, finally got ADB working on the W7 machine.
C:\Users\Walter>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 4211mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.046s

rushwal said:
Ok, finally got ADB working on the W7 machine.
C:\Users\Walter>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 4211mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.046s
Click to expand...
Click to collapse
Fantastic your phone has never been updated.. it will be easy to s-off with revone
you should do that right away. after that thier are a bunch of AT&T files you can use to get your phone back into new condition.
http://www.htc1guru.com/downloads/ruu-file-downloads/
all the files with cingular in the name will work on your phone
I would go directly to US 3.17.502.3 after you get s-off
edit your post and remove you serial and iemi like I did in the quote

clsA said:
Fantastic your phone has never been updated.. it will be easy to s-off with revone
you should do that right away. after that thier are a bunch of AT&T files you can use to get your phone back into new condition.
http://www.htc1guru.com/downloads/ruu-file-downloads/
all the files with cingular in the name will work on your phone
I would go directly to US 3.17.502.3 after you get s-off
edit your post and remove you serial and iemi like I did in the quote
Click to expand...
Click to collapse
What if I want to put GPE on it. Easy?

clsA said:
Fantastic your phone has never been updated.. it will be easy to s-off with revone
you should do that right away. after that thier are a bunch of AT&T files you can use to get your phone back into new condition.
http://www.htc1guru.com/downloads/ruu-file-downloads/
all the files with cingular in the name will work on your phone
I would go directly to US 3.17.502.3 after you get s-off
edit your post and remove you serial and iemi like I did in the quote
Click to expand...
Click to collapse
I keep getting device not found when I try to ADB.

rushwal said:
I keep getting device not found when I try to ADB.
Click to expand...
Click to collapse
adb only works in recovery or when the phone is booted to android
you can convert to GPE, but you need to run the AT&T RUU first to make sure all your partitions are correct
and your phone is working correctly. I still recommend getting s-off first
and here's a tutorial on RUU
http://www.andromods.com/unroot-locking/how-to-restore-to-stock-unbrick-unrooting-htc-one-m7.html

clsA said:
adb only works in recovery or when the phone is booted to android
you can convert to GPE, but you need to run the AT&T RUU first to make sure all your partitions are correct
and your phone is working correctly. I still recommend getting s-off first
and here's a tutorial on RUU
http://www.andromods.com/unroot-locking/how-to-restore-to-stock-unbrick-unrooting-htc-one-m7.html
Click to expand...
Click to collapse
While in recovery, when I try to ADB following the instructions to get S-OFF using revone, I am getting device not found.

Ok, I'm back running again! Thanks for your help!
Now to get GPE on there.

Related

[Q]Phone is in a bootloop, hopes this pinpoints my problem

@clsA
My HTC one is caught in a bootloop, i recently tried to flash the Android Revolution 41.0 rom on clockworkmod recovery (idk if that is the issue since the thread recommended me to use twrp) anyway the installation worked fine until the last step (i dont remember unfortunately), i skipped it accidentally and thus began the bootloop. i tried to go into recovery and would only get the CWM 6.0.4.3 logo for a few seconds and then it would boot back to the htc logo. I was using windows 8.1 and tried to flash a new recovery, rom, whatever. the problem was windows would not recognize my usb device. I read some threads and decied to re install all the android software i had on my computer (htc sync,SDK, etc.) still no go. I went ahead and booted up my pc with Ubuntu 13.10, im still having the same initial issue of USB recognition. anytime i type adb devices i get the list of devices with nothing, everytime i try to run a fastboot command nothing happens. anyway this is what on my bootloader screen and getvar:
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13off
OpenDSP-v26.120.274.0202
eMMc-boot
when i run fastboot getvar all i get <waiting for devices> and nothing else happens, @clsA might be correct about my phone not being s-off ill see how to fix that and update as i go, thanks in advance for any other help. not that i am currently using ubuntu
went ahead and tried running the moonshine s-off when tryingto check for updates there was an error and the program stopped...
!! Do NOT for any reason touch, unplug, lick or maim your device !!
Checking for updates......
ERROR: Cannot check for updates
Click to expand...
Click to collapse
qibz said:
went ahead and tried running the moonshine s-off when tryingto check for updates there was an error and the program stopped...
Click to expand...
Click to collapse
yeah your not going to have any luck with windows 8.1, your hboot on your phone has to be 1.55.000 before windows 8 will work.
So your basically stuck learning Ubuntu till you get your phone updated.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT359W918802
(bootloader) imei: 354439052875079
(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: 4284mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 3.666s
Click to expand...
Click to collapse
fially got the fastboot getvar all command to work on my other windows 8 machine. wet ahead and fastboot cachee clear still stuck in bootloop, will try other methods sice this machine does recognize my phoe, thanks again
qibz said:
fially got the fastboot getvar all command to work on my other windows 8 machine. wet ahead and fastboot cachee clear still stuck in bootloop, will try other methods sice this machine does recognize my phoe, thanks again
Click to expand...
Click to collapse
reflash recovery
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then install root http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
then try and get s-off
http://forum.xda-developers.com/showthread.php?t=2314582
clsA said:
reflash recovery
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then install root http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
then try and get s-off
http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
I tried to flash recovery, no go, I am however able to fastboot boot recovery.img I went ahead and wiped dalvik cache system cache and data. went back to the bootloader and tried to flash the recovery again, no go. I wanted to try and boot up a rom and maybe be able to flash a recovery that way, rom wont boot.
if i am able to boot into twrp via boot can i flash a recovery or rom that way, i dont want to do anything else and brick my phone.
thanks again
qibz said:
I tried to flash recovery, no go, I am however able to fastboot boot recovery.img I went ahead and wiped dalvik cache system cache and data. went back to the bootloader and tried to flash the recovery again, no go. I wanted to try and boot up a rom and maybe be able to flash a recovery that way, rom wont boot.
if i am able to boot into twrp via boot can i flash a recovery or rom that way, i dont want to do anything else and brick my phone.
thanks again
Click to expand...
Click to collapse
what is the error you get flashing recovery ?
did you md5 check your download.
paste the command window here so I can see whats happening
clsA said:
what is the error you get flashing recovery ?
did you md5 check your download.
paste the command window here so I can see whats happening
Click to expand...
Click to collapse
PROBLEM SOLVED!!
booting the recovery was the key to my solution
fastboot boot<name of recovery>.img
once i was in twrp i cleared the cache, data, system, and anything other thing i could find. i then went and flashed htc dumlock and reflashed recovery within twrp. i was then able to reboot into recover (cwm 6.0.4.3). from there i just used adb sideload to flash CM 10.2 and GAPPS 4.3 and finally got my phone back up and running.
thanks again for everything, i hope my solution can help others who have my problem
qibz said:
PROBLEM SOLVED!!
booting the recovery was the key to my solution
fastboot boot<name of recovery>.img
once i was in twrp i cleared the cache, data, system, and anything other thing i could find. i then went and flashed htc dumlock and reflashed recovery within twrp. i was then able to reboot into recover (cwm 6.0.4.3). from there i just used adb sideload to flash CM 10.2 and GAPPS 4.3 and finally got my phone back up and running.
thanks again for everything, i hope my solution can help others who have my problem
Click to expand...
Click to collapse
Glad to here your back up and running

[Q]

After unsuccessfully trying to manually update to 4.4.2 I have semi-bricked my phone.
Bootloader menu currently has Tampered, Relocked, Security Warning and S-On. I accidentally wiped data while in recovery while attempting to flash something. I had flashed (I believe) a modified stock kernel for 4.4 (or 4.3, not sure). Edit: Hboot 1.55
-Because it's not S-Off, I can't run an RUU.exe and downgrade.
-I can't seem to enter recovery either. It says "entering recovery" and then goes back to the bootloader screen. When I try to flash a new recovery, I get a "remote: signature verify fail" error. Any sort of recovery.img file gets this same error. I've tried installing a different recovery and the same error shows up.
-I've tried using revone: http://forum.xda-developers.com/showthread.php?t=2314582 except I it says "error: device not found" when I try to initiate it.
Is it possible to find a 4.3/4.4.2 RUU zip/exe and try to flash/run a current/higher version firmware? If anybody could also post a link to the stock 4.3 kernel it would be appreciated.
Thanks.
I need the phone for use very soon. Something tells me I did revone wrong. Any options I have? Isn't there a desktop program that lets you restore your HTC back to factory stock?
mch277 said:
After unsuccessfully trying to manually update to 4.4.2 I have semi-bricked my phone.
Bootloader menu currently has Tampered, Relocked, Security Warning and S-On. I accidentally wiped data while in recovery while attempting to flash something. I had flashed (I believe) a modified stock kernel for 4.4 (or 4.3, not sure).
-Because it's not S-Off, I can't run an RUU.exe and downgrade.
-I can't seem to enter recovery either. It says "entering recovery" and then goes back to the bootloader screen. When I try to flash a new recovery, I get a "remote: signature verify fail" error. Any sort of recovery.img file gets this same error. I've tried installing a different recovery and the same error shows up.
-I've tried using revone: http://forum.xda-developers.com/showthread.php?t=2314582 except I it says "error: device not found" when I try to initiate it.
Is it possible to find a 4.3/4.4.2 RUU zip/exe and try to flash/run a current/higher version firmware? If anybody could also post a link to the stock 4.3 kernel it would be appreciated.
Thanks.
I need the phone for use very soon. Something tells me I did revone wrong. Any options I have? Isn't there a desktop program that lets you restore your HTC back to factory stock?
Click to expand...
Click to collapse
Can you get into fastboot? If so, post the results of fastboot getvar all (minus IMEI and SN).
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 4320mV
(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
If you are attempting to get s-off revone will not work on you... You should try rumrunner instead
Sent from my HTC One using XDA Premium 4 mobile app
TopoX84 said:
If you are attempting to get s-off revone will not work on you... You should try rumrunner instead
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried. Except rumrunner needs you to be able to boot into Android first. I accidentally wiped data while in recovery (ROM, etc) and now I only have fastboot. I can't even access recovery/flash a new recovery/flash anything at all really. I can get into the silver HTC logo with "fastboot oem rebootRUU" but that's about it. Anything I attempt to flash while doing that will get a signature verification fail.
Update: I unlocked the bootloader again and can now enter recovery. The issue is, it appears that I have no "SD card". I can't access or even mount it to computer so I can put a ROM inside when I select "choose zip from /sdcard.

[Q] Stuck in a bootloop

Hi everyone,
I have my AT&T HTC One that's stuck in a bootloop due to me flashing a ROM (ARHD). I did not notice I still had S-On (S-Off is needed to flash the ROM) and now stuck in a loop. I can access recovery (TWRP 2.6.3.3) but sideload just stays at the message that's says its starting.
Bootloader is also accessible, I have all my adb files and fastboot files. I just want to get back to stock 4.3 or 4.4.2, or even a custom rom if it'll work.
Here are my vars:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
Any help is appreciated.
EDIT: Managed to get sideload working, just opened cmd and had the TWRP running sideload, but it was stuck at the words starting so I checked for devices and found it. sideloaded stock AT&t rooted ROM by dark 2099 (http://forum.xda-developers.com/showthread.php?t=2676986) and still bootlooping after wiping caches and factory reset.
EDIT2: Sideloaded the ROM again now not bootlooping but stuck at HTC logo, still can use recovery and bootloader.
52me52 said:
Hi everyone,
I have my AT&T HTC One that's stuck in a bootloop due to me flashing a ROM (ARHD). I did not notice I still had S-On (S-Off is needed to flash the ROM) and now stuck in a loop. I can access recovery (TWRP 2.6.3.3) but sideload just stays at the message that's says its starting.
Bootloader is also accessible, I have all my adb files and fastboot files. I just want to get back to stock 4.3 or 4.4.2, or even a custom rom if it'll work.
Here are my vars:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3*********
(bootloader) imei: 354***********
(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: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
Any help is appreciated.
EDIT: Managed to get sideload working, just opened cmd and had the TWRP running sideload, but it was stuck at the words starting so I checked for devices and found it. sideloaded stock AT&t rooted ROM by dark 2099 (http://forum.xda-developers.com/showthread.php?t=2676986) and still bootlooping after wiping caches and factory reset.
EDIT2: Sideloaded the ROM again now not bootlooping but stuck at HTC logo, still can use recovery and bootloader.
Click to expand...
Click to collapse
Edit your post to remove the serial no and IMEI
Try fastboot erase cache from fastboot USB (bootloader)
And how did you get to version-main: 4.20.502.1 ?
clsA said:
Edit your post to remove the serial no and IMEI
Try fastboot erase cache from fastboot USB (bootloader)
And how did you get to version-main: 4.20.502.1 ?
Click to expand...
Click to collapse
Hoping to hear from you, saw you in other Q&A posts!
I tried that fastboot erase cache still same thing. Any help is appreciated, hopefully I can get this done today it's my dad's.
EDIT: thinking about using an RUU but method would I take? .exe or .zip? I tried using an RUU and it failed and gave me that somehow. .exe RUU btw.
EDIT: the RUU is called elevate-RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2
52me52 said:
Hoping to hear from you, saw you in other Q&A posts!
I tried that fastboot erase cache still same thing. Any help is appreciated, hopefully I can get this done today it's my dad's.
Click to expand...
Click to collapse
Flash twrp again and erase cache after
what rom are you sideloading ? nvm I see
you cant RUU your software is too new and you need s-off
where did you find this
EDIT: the RUU is called elevate-RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R1 0_Radio_4T.24.3218.09_10.26.1718.01L_release_35656 5_signed_2
Click to expand...
Click to collapse
clsA said:
Flash twrp again and erase cache after
what rom are you sideloading ? nvm I see
you cant RUU your software is too new and you need s-off
Click to expand...
Click to collapse
Same situation still at HTC logo, ok I just saw that now too about the RUU.
Link:http://www.androidruu.com/index.php?developer=M7 first one.
52me52 said:
Same situation still at HTC logo, ok I just saw that now too about the RUU.
Click to expand...
Click to collapse
slow down and answer these questions
how did you get to version-main: 4.20.502.1 ?
and where is the RUU you listed.
also are you doing MD5 check of all the files your flashing ?
clsA said:
slow down and answer these questions
how did you get to version-main: 4.20.502.1 ?
and where is the RUU you listed.
also are you doing MD5 check of all the files your flashing ?
Click to expand...
Click to collapse
1) from the RUU I used.
2)just posted/edited
3)No I don't really do that
52me52 said:
1) from the RUU I used. ??? link
2)just posted/edited ??? link
3)No I don't really do that - how do you know your files are not corrupt ?
Click to expand...
Click to collapse
If everything is a big secret I can't help you
clsA said:
If everything is a big secret I can't help you
Click to expand...
Click to collapse
It's my link from the post above your last one: http://www.androidruu.com/index.php?developer=M7
I never check the MD5 because I never had a problem until now.
What would you recommend at this point?
52me52 said:
It's my link from the post above your last one: http://www.androidruu.com/index.php?developer=M7
I never check the MD5 because I never had a problem until now.
Click to expand...
Click to collapse
Who posted this RUU .. how did you find it ?
and why is it not the same main version as in you getvar
I'm downloading it now I'll see whats up
clsA said:
Who posted this RUU .. how did you find it ?
and why is it not the same main version as in you getvar
I'm downloading it now I'll see whats up
Click to expand...
Click to collapse
I came across this link: http://forum.xda-developers.com/showthread.php?t=2265618
I scrolled down to return to stock and pressed the first link for RUUs here: http://forum.xda-developers.com/showthread.php?t=2194707
pressed m7 and got the page of the RUUs.
The main version I don't really know, I ran it and it failed and when I redid the 'fastboot getvar all' I saw it. Thanks for all your help.
52me52 said:
I came across this link: http://forum.xda-developers.com/showthread.php?t=2265618
I scrolled down to return to stock and pressed the first link for RUUs here: http://forum.xda-developers.com/showthread.php?t=2194707
pressed m7 and got the page of the RUUs.
The main version I don't really know, I ran it and it failed and when I redid the 'fastboot getvar all' I saw it. Thanks for all your help.
Click to expand...
Click to collapse
Ok well it appears to be a Real RUU
but the MD5 failed - means it's corrupt
can you md5 check your file and compare it to mine ?
this is the md5 on the download page
fdbaccdda9519a321059b02e2dec49b2
clsA said:
Ok well it appears to be a Real RUU
but the MD5 failed - means it's corrupt
can you md5 check your file and compare it to mine ?
this is the md5 on the download page
fdbaccdda9519a321059b02e2dec49b2
Click to expand...
Click to collapse
Mine also failed same thing. Except my code in orange is different than yours.
52me52 said:
Mine also failed same thing. Except my code in orange is different than yours.
Click to expand...
Click to collapse
ok well lets try and get your phone working
flash this stock recovery
https://www.dropbox.com/s/rns2nj5hn7lwjln/recovery.img
then do a factory reset from the bootloader
I'll post more here while your do that...
Next step is redownload TWRP from here
http://techerrata.com/browse/twrp2/m7
and md5 check it
then flash it
and redownload My Rom here >> http://www.androidfilehost.com/?fid=23329332407576941
again md5 check it and sideload it
clsA said:
ok well lets try and get your phone working
flash this stock recovery
https://www.dropbox.com/s/rns2nj5hn7lwjln/recovery.img
then do a factory reset from the bootloader
I'll post more here while your do that
Click to expand...
Click to collapse
Good bless you and thanks, but should I do a backup of some sort?
52me52 said:
Good bless you and thanks, but should I do a backup of some sort?
Click to expand...
Click to collapse
no theirs nothing to backup
I downloaded the RUU again and got the exact same number as the first time
MD5: 5F121D72B8FA3F6F1704588467752605
clsA said:
no theirs nothing to backup
Click to expand...
Click to collapse
15-17 minutes till download finishes, sorry for keeping you up and thanks for the help.
52me52 said:
15-17 minutes till download finishes, sorry for keeping you up and thanks for the help.
Click to expand...
Click to collapse
did you flash the stock recovery and do the factory reset ?
did the phone try and boot up ?
first boot will sometimes take 5 - 7 min on the HTC logo
clsA said:
did you flash the stock recovery and do the factory reset ?
did the phone try and boot up ?
first boot will sometimes take 5 - 7 min on the HTC logo
Click to expand...
Click to collapse
Did that and stays on the logo, going to flash your rom now.
I got a bad md5, do I pick a mirror to download?
52me52 said:
Did that and stays on the logo, going to flash your rom now.
Click to expand...
Click to collapse
just don't forget everytime you flash a recovery to erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and in TWRP when you do factory reset
clear delvic and cache also
not sdcard

[Q] HTC One M7 stuck in Boot Loop

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.

Stuck in FASTBOOT...

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!

Categories

Resources