Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode and in RUU mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
awer25 said:
Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
Click to expand...
Click to collapse
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
alray said:
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
Click to expand...
Click to collapse
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
Click to expand...
Click to collapse
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
Click to expand...
Click to collapse
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
Thank you for that explanation. I got into RUU mode by doing fastboot oem rebootRUU, which took me to a black screen with silver HTC. That may not be RUU mode...I'm just guessing.
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
edit: Wait, there is also a 3.22.1540.1 ruu.zip on htcdev.com so try it first.
fastboot oem rebootRUU
fastboot flash zip <name_of_file>.zip
fastboot flash zip <name_of_file>.zip
fastboot reboot
Click to expand...
Click to collapse
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
awer25 said:
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
Click to expand...
Click to collapse
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
alray said:
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
Click to expand...
Click to collapse
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
awer25 said:
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
Click to expand...
Click to collapse
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on.
Click to expand...
Click to collapse
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
alray said:
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
Click to expand...
Click to collapse
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
awer25 said:
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
Click to expand...
Click to collapse
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
alray said:
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
Click to expand...
Click to collapse
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
awer25 said:
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
Click to expand...
Click to collapse
Try the ruu.exe on windows 7.
alray said:
Try the ruu.exe on windows 7.
Click to expand...
Click to collapse
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
awer25 said:
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
Click to expand...
Click to collapse
I got it! I had to relock my bootloader for some reason. Then, the Windows RUU installed fine.
Thank you alray for your help!
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
-marco- said:
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
Click to expand...
Click to collapse
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
awer25 said:
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
Click to expand...
Click to collapse
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3867mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
-marco- said:
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
finished. total time: 0.066s
Click to expand...
Click to collapse
-marco- said:
I am at work in the office and at some point I look at my phone and I see it rebooted on its own. now it's stuck forever on the HTC one beats audio loading screen.
I didn't even touch anything before. Tried to reboot but it just gets stuck there.
Click to expand...
Click to collapse
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
nkk71 said:
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
Click to expand...
Click to collapse
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
-marco- said:
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
Click to expand...
Click to collapse
Well first I would recommend you update recovery to TWRP
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
since they are more compatible when flashing 4.4 ROMs (make sure to check MD5 on the files, that site doesn't play nice with download managers!)
Code:
[B]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader[/B]
-> enter recovery
Second, in TWRP, make a nandroid backup, you may need it later *** (please check below)
Third, put a ROM on the phone (in custom recovery):
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HT34xxxxxxxx recovery <- you need to be in recovery
[B]adb push <name of rom>.zip /sdcard/[/B] <- this will take about 5 mins without any progress
and install the ROM, don't select WIPE during installation, and you should have your million $ question solved... all apps, data, etc should be there, but if you get apps crashing it's because of the "dirty-flash"
As to which ROMs you can use for the above procedure, there's is a 100% stock version of 4.19.401.9 here: http://forum.xda-developers.com/showthread.php?t=2224752
I'm personally using ARHD 52.0 from here: http://forum.xda-developers.com/showthread.php?t=2183023 (stock but with improvements, and rooted)
I haven't checked if there's a 100% stock 4.20.707.6 ROM around, so you could do some googling and see.
Hope that helps
*** once you've done the backup, you can try wiping "data, cache, dalvik", and then restore the nandroid... sometimes that works
if not keep the nandroid, as it has all the information, and you can use Nandroid Manager (in play store) to extract individual information, if need be.
Good Luck
Related
Hey guys Im trying to fix my HTC One. I was on a call last night and the battery died and now it will only boot to fastboot. Problem is my Windows 8 box is not working with ADB. ADB does not see the device, but fastboot works. I try booting to twrp recovery and it just reboots to the HTC logo.
Can anyone help me out? I dont mind completely blasting it, but I dont want to waste a $600 phone.
Also good to note guys
piftoffpenguin said:
Hey guys Im trying to fix my HTC One. I was on a call last night and the battery died and now it will only boot to fastboot. Problem is my Windows 8 box is not working with ADB. ADB does not see the device, but fastboot works. I try booting to twrp recovery and it just reboots to the HTC logo.
Can anyone help me out? I dont mind completely blasting it, but I dont want to waste a $600 phone.
Click to expand...
Click to collapse
By the way at fastboot usb screen I have
*****Tampered*****
*****Unlocked*****
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
piftoffpenguin said:
By the way at fastboot usb screen I have
*****Tampered*****
*****Unlocked*****
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
Click to expand...
Click to collapse
adb doesnt work in fastboot mode;
Just flash the custom recovery again
fastboot flash recovery recovery-file-here.img
Thanks for the reply
darksnoopy said:
adb doesnt work in fastboot mode;
Just flash the custom recovery again
fastboot flash recovery recovery-file-here.img
Click to expand...
Click to collapse
I have tried this several times. I even tried to flash clockwork and a few different versions of twrp, and clear the cache and when I go to recovery it shows the Teamwin splash screen and then it reboots.
It says it transferred successfully, but even when I flashed clockwork I still see the Teamwin splash when entering recovery mode.
Image attached of successful flash
darksnoopy said:
adb doesnt work in fastboot mode;
Just flash the custom recovery again
fastboot flash recovery recovery-file-here.img
Click to expand...
Click to collapse
I just tried to flash clockwork as seen in the picture as well. Same issue, when I hit recovery, Teamwin splash and then it begins another endless reboot. Thanks again for the reply.
piftoffpenguin said:
I just tried to flash clockwork as seen in the picture as well. Same issue, when I hit recovery, Teamwin splash and then it begins another endless reboot. Thanks again for the reply.
Click to expand...
Click to collapse
hm i dont know if i can help anymore... but some steps to do
fastboot erase cache
then write the recovery again
again fastboot erase cache
reboot your device and then try to boot into recovery
else
flash stock recovery and then try again to flash custom recovery...
Last choice is to restore with a RUU
P.S If you dont have any luck flashing openrecovery-twrp-2.6.3.3-m7.img then try with this version:
openrecovery-twrp-2.6.3.0-m7.img
EDIT: twrp25.img???? i dont think this recovery is meant for htc one..you are flashing wrong version of twrp.... flash with the recoveries i mentioned above
Its correct - actually TWRP 2.5.0.0 renamed
darksnoopy said:
hm i dont know if i can help anymore... but some steps to do
fastboot erase cache
then write the recovery again
again fastboot erase cache
reboot your device and then try to boot into recovery
else
flash stock recovery and then try again to flash custom recovery...
Last choice is to restore with a RUU
P.S If you dont have any luck flashing openrecovery-twrp-2.6.3.3-m7.img then try with this version:
openrecovery-twrp-2.6.3.0-m7.img
EDIT: twrp25.img???? i dont think this recovery is meant for htc one..you are flashing wrong version of twrp.... flash with the recoveries i mentioned above
Click to expand...
Click to collapse
That's just the filename that I renamed TWRP 2.5.0.0 to for a simpler command.
I found the problem but dont know how to fix it. My device is in Fastboot which means no ADB. Also without being able to boot I can't change that (at least I dont think I can.).
Anyhow the damned thing re-engaged S-ON and its blocking access to the NAND (even if its saying it wrote to it, it can't be because of S-ON).
How do I RUU?
HTC One M7 Tmobile.
Thanks for the info sir. Much appreciated.
piftoffpenguin said:
That's just the filename that I renamed TWRP 2.5.0.0 to for a simpler command.
I found the problem but dont know how to fix it. My device is in Fastboot which means no ADB. Also without being able to boot I can't change that (at least I dont think I can.).
Anyhow the damned thing re-engaged S-ON and its blocking access to the NAND (even if its saying it wrote to it, it can't be because of S-ON).
How do I RUU?
HTC One M7 Tmobile.
Thanks for the info sir. Much appreciated.
Click to expand...
Click to collapse
type
fastboot getvar all
post here without your imei and serial number
Getvar
darksnoopy said:
type
fastboot getvar all
post here without your imei and serial number
Click to expand...
Click to collapse
C:\Users\cwatson\Desktop\FASTBOOT>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.14.3250.15
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.27.531.7
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0713000
INFOcidnum: T-MOB010
INFObattery-status: good
INFObattery-voltage: 4330mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
This is the RUU for your phone ruu_m7_ul_jb_50_tmous_1-27-531-11_radio_4a-17-3250-20_10-40-1150-04_release_324846_signed-exe
you can find it at htc1guru but to use it you must relock your bootloader and i wouldnt advice it cause of this error
piftoffpenguin said:
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
Click to expand...
Click to collapse
I dont want to risk to brick your device so it would be better to post your problem at the Tmobile htc one forum at xda here
http://forum.xda-developers.com/htc-one-tmobile/help
Unlock can I relock
darksnoopy said:
This is the RUU for your phone ruu_m7_ul_jb_50_tmous_1-27-531-11_radio_4a-17-3250-20_10-40-1150-04_release_324846_signed-exe
you can find it at htc1guru but to use it you must relock your bootloader and i wouldnt advice it cause of this error
I dont want to risk to brick your device so it would be better to post your problem at the Tmobile htc one forum at xda here
http://forum.xda-developers.com/htc-one-tmobile/help
Click to expand...
Click to collapse
If I unlock my bootloader can I relock in without ADB access and S-on or will that be a one way street??
piftoffpenguin said:
If I unlock my bootloader can I relock in without ADB access and S-on or will that be a one way street??
Click to expand...
Click to collapse
bootloader unlocking happens in fastboot with fastboot flash unlocktoken unlock_code.bin so no you dont need adb
Are you locked or unlocked right now?
Unlocked
darksnoopy said:
bootloader unlocking happens in fastboot with fastboot flash unlocktoken unlock_code.bin so no you dont need adb
Are you locked or unlocked right now?
Click to expand...
Click to collapse
I'm unlocked and have my unlock_code.bin as well saved.
piftoffpenguin said:
I'm unlocked and have my unlock_code.bin as well saved.
Click to expand...
Click to collapse
if you want to lock it and try to run the RUU give the command fastboot oem lock but i would not advice it and i take no responibility since i dont have a tmobile phone. I recommend to post on tmobile forum for help
Tried RUU
darksnoopy said:
if you want to lock it and try to run the RUU give the command fastboot oem lock but i would not advice it and i take no responibility since i dont have a tmobile phone. I recommend to post on tmobile forum for help
Click to expand...
Click to collapse
I tried the RUU you recommended. It said RUU ERROR 171 USB Connection Error. I can send it fastboot commands manually and the RUU sees its Rom version and requests the upgrade and reboots, but it then bombs. It also would not let me relock giving the following error:
... INFOLock successfully...
INFOmipi display off
INFOmipi_dsi_cmds_tx_ext
INFOpm8921_vreg_disable function, vreg_id = 38
INFOpm8921_vreg_disable function, vreg_id = 1
INFOTZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
INFOUse PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.158s
Is this device finished or is there anything else I can do?
Trying this now
Reference:
http://forums.androidcentral.com/ht...k-bootloader-cant-get-into-recovery-help.html
"when you have all that done open a cmd prompt and with the phone in fastboot usb mode type these cmd's
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
with the last cmd, if it comes back with a error about flushing or something like that just type the cmd again "
Dunno but I am at my wits end and do not know if the EPROM is even good now:
May have it beat finally
Crossing my fingers.
NOTE** This did not work earlier today despite MANY attempts.
I downloaded clockwork recovery to my fastboot computer folder.
I renamed it to recovery.img.
I ran fastboot boot recovery.img and I got clockwork.
I found the Viper ROM I installed months ago.
It ran the install.
Now it rebooted and I got endless reboot again lol ****E! Curse you and your S-On HTC!!!!
piftoffpenguin said:
Crossing my fingers.
NOTE** This did not work earlier today despite MANY attempts.
I downloaded clockwork recovery to my fastboot computer folder.
I renamed it to recovery.img.
I ran fastboot boot recovery.img and I got clockwork.
I found the Viper ROM I installed months ago.
It ran the install.
Now it rebooted and I got endless reboot again lol ****E! Curse you and your S-On HTC!!!!
Click to expand...
Click to collapse
Simple, s-off your device.
Sent from my HTC One using Tapatalk
Restore factory settings and wipe cache and dalvik cache and flash the rom again
How
xcrazydx said:
Simple, s-off your device.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
How do I s-off the device when Adb commmands are not working and an RUU isnt even working?
Hi! I tried to convert my M7 to a GPE with OTAs, but this did not succeed. After that I tried to simply revert it back to stock, this also failed and I am now at a state where the phone boots up, as usual, to the homescreen, but turns off after 3 seconds only to repeat the process. I believe this to be a sort of boot loop.
I have tried pretty much everything I could think of. I tried using ADB, but found out that USB debugging is not on and I am not able to turn it on because of the boot loop.
I tried flashing the GPE.zip and stock GPE recovery in order to "start fresh", but this does not seem to have any effect.When flashing the GPE.zip I get the error: FAILED (remote:99 unknown fail). However, when flashed stock recovery it seems to succeed, but just as the CWM/ TWRP recovery, I am not able to access it, because it turns off and begins the boot loop.
I then tried flashing Cyanogenmod and CWM/ TWRP, but this did not do anything either. Tried to simply do a factory reset through the bootloader, nope.
My current state is S-ON, Bootloader Unlocked and the only way to interact with the phone is fastboot, because I can't access ADB in order to S-OFF...
So my first question is whether there is a way to S-OFF through fastboo? Since every thread and site I read requires ADB, which I cannot access.
If not.. What to do ?
Thanks in advance!
Sari95 said:
I tried using ADB, but found out that USB debugging is not on and I am not able to turn it on because of the boot loop.
Click to expand...
Click to collapse
ADB is only usable from a booted OS or from custom recovery. In bootloader mode, you can only use FASTBOOT.
I tried flashing the GPE.zip and stock GPE recovery in order to "start fresh" but this does not seem to have any effect.When flashing the GPE.zip I get the error: FAILED (remote:99 unknown fail).
Click to expand...
Click to collapse
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
However, when flashed stock recovery it seems to succeed, but just as the CWM/ TWRP recovery, I am not able to access it, because it turns off and begins the boot loop.
Click to expand...
Click to collapse
When you flash the recovery partition, also erase cache and reboot the bootloader before attempting to boot in recovery mode. Also make sure the recovery you are flashing is compatible with you variant (i.e M7_UL)
I then tried flashing Cyanogenmod and CWM/ TWRP, but this did not do anything either.
Click to expand...
Click to collapse
How? define "did not do anything either" any error message?
Tried to simply do a factory reset through the bootloader, nope.
Click to expand...
Click to collapse
factory reset only wipe /data of the rom currently installed on your phone, this will not magically revert all the mess you did
My current state is S-ON
Click to expand...
Click to collapse
You must be S-OFF to convert to GPE !!
Bootloader Unlocked and the only way to interact with the phone is fastboot because I can't access ADB in order to S-OFF...
Click to expand...
Click to collapse
you need a working rom to s-off. and again adb only works from recovery. Also from a booted OS with usb debugging ON
So my first question is whether there is a way to S-OFF through fastboo?
Click to expand...
Click to collapse
No
If not.. What to do ?
Click to expand...
Click to collapse
flash a sense based rom (doesnt require s-off)
achieve s-off
flash a gpe rom and do the full conversion (i.e with a GPE ruu)
never s-on and never relock your bootloader when converted to gpe or say goodbye to your phone
alray said:
ADB is only usable from a booted OS or from custom recovery. In bootloader mode, you can only use FASTBOOT.
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
When you flash the recovery partition, also erase cache and reboot the bootloader before attempting to boot in recovery mode. Also make sure the recovery you are flashing is compatible with you variant (i.e M7_UL)
How? define "did not do anything either" any error message?
factory reset only wipe /data of the rom currently installed on your phone, this will not magically revert all the mess you did
You must be S-OFF to convert to GPE !!
you need a working rom to s-off. and again adb only works from recovery. Also from a booted OS with usb debugging ON
No
flash a sense based rom (doesnt require s-off)
achieve s-off
flash a gpe rom and do the full conversion (i.e with a GPE ruu)
never s-on and never relock your bootloader when converted to gpe or say goodbye to your phone
Click to expand...
Click to collapse
Thanks for answering! I am now stuck at the first step :l I believe I've found the correct stock RUU for my device, HTC One M7 bought in Norway, but when I try to download it from htc1guru.com, it downloads a little bit and stops. I am not able to download the full .zip file in order to flash it. I have tested to see if it has anything to do with my internet connection to do, but it doesn't have anything to do with it.
I am now downloading Android Revolution for M7, hoping that it will work....
Do you know if this issue with htc1guru.com is common or not?
Btw, I think it is best if I explain to you the whole process:
1. I downloaded a google play Edition RUU.zip that I could flash to convert the device into GPE.
2. Unlocked and S-OFF'd the device, then I flashed the RUU.zip. After these steps, I had a GPE device. However, the RUU I downloaded was Kitkat 4.4, which I thought would automatically update to 4.4.3. This did not happen.
3. I read more and understood that my CID and modelid had to be changed to CID: GOOGL001 and modelid: PN0712000, and so I did. I did not take note of my original CID, of course, so I don't know what that was :/
4. After having changed those settings, I once again tried to update it with OTA, as one would do with a GPE device, without any luck.
5. Reading on, it became clear that the device had to have stock recovery, which I downloaded and flashed. Once again, no luck with the OTA update. After this point, I gave up the GPE dream and decided to return to stock.
6. Then I read a tutorial to return back to stock, which told me to lock the bootloader and S-ON in order to flash the stock rom. This is did, but the process failed and I was left with a device booting up to homescreen, turning off and on in this endless boot loop.
Hope this helps to clarify my situation
Sari95 said:
6. Then I read a tutorial to return back to stock, which told me to lock the bootloader and S-ON in order to flash the stock rom. This is did, but the process failed and I was left with a device booting up to homescreen, turning off and on in this endless boot loop.
Click to expand...
Click to collapse
Well, I don't know where this tutorial was from, but you don't have to s-on to flash a ruu., you don't even need to relock bootloader to flash a ruu when you have s-off. Never S-ON back unless you absolutely must (sending phone for repair under warranty).
post a fastboot getvar all
are you still able to unlock bootloader?
alray said:
Well, I don't know where this tutorial was from, but you don't have to s-on to flash a ruu., you don't even need to relock bootloader to flash a ruu when you have s-off. Never S-ON back unless you absolutely must (sending phone for repair under warranty).
post a fastboot getvar all
are you still able to unlock bootloader?
Click to expand...
Click to collapse
Yeah... stupid of me not to read several tutorials before trying to return to stock :l
My getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4086mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
I believe I am able to unlock bootloader, yes. A picture is attached, which shows my current bootloader.
Sari95 said:
no luck with the OTA update. After this point, I gave up the GPE dream and decided to return to stock.
Click to expand...
Click to collapse
with s-off, you can download and flash ota update manually.
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
Sari95 said:
Yeah... stupid of me not to read several tutorials before trying to return to stock :l
My getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4086mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
I believe I am able to unlock bootloader, yes. A picture is attached, which shows my current bootloader.
Click to expand...
Click to collapse
thats a good thing you can unlock the bootloader again! many GPE users a stuck with unlockable bootloader with hboot 1.55+.
was you able to flash arhd? Then s-off the phone again and run the ruu you want again (stock or gpe)
alray said:
with s-off, you can download and flash ota update manually.
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
thats a good thing you can unlock the bootloader again! many GPE users a stuck with unlockable bootloader with hboot 1.55+.
was you able to flash arhd? Then s-off the phone again and run the ruu you want again (stock or gpe)
Click to expand...
Click to collapse
If by ARHD you mean Android Revolution HD, then no, I am not able to flash it. I get the error : FAILED (24 parsing failure), then nothing happens.
I also tried flashing stock Rug, but since I've changed my CID to CWS__001, while my MID is P0712000, they are in conflict and the RUU doesn't work either. Tried editing the info - Android. The, but no luck there either
Sari95 said:
If by ARHD you mean Android Revolution HD, then no, I am not able to flash it. I get the error : FAILED (24 parsing failure), then nothing happens.
I also tried flashing stock Rug, but since I've changed my CID to CWS__001, while my MID is P0712000, they are in conflict and the RUU doesn't work either. Tried editing the info - Android. The, but no luck there either
Click to expand...
Click to collapse
please post a picture when you got the FAILED error when attempting to flash arhd
alray said:
please post a picture when you got the FAILED error when attempting to flash arhd
Click to expand...
Click to collapse
ok.. so I tried flashing it now, there's a different error.
Sari95 said:
ok.. so I tried flashing it now, there's a different error.
Click to expand...
Click to collapse
ok.... so you are trying to flash a rom from fastboot
with fastboot, you flash recovery, ruu, and firmware only.
roms are flashed from custom recovery... not with fastboot
maybe you should have answered the question above from post #2:
I tried flashing the GPE.zip and stock GPE recovery in order to "start fresh" but this does not seem to have any effect.When flashing the GPE.zip I get the error: FAILED (remote:99 unknown fail).
Click to expand...
Click to collapse
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
---------- Post added at 09:06 PM ---------- Previous post was at 09:04 PM ----------
push the rom to your sdcard and flash it using twrp 2.6.3.3
alray said:
ok.... so you are trying to flash a rom from fastboot
with fastboot, you flash recovery, ruu, and firmware only.
roms are flashed from custom recovery... not with fastboot
maybe you should have answered the question above from post #2:
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
---------- Post added at 09:06 PM ---------- Previous post was at 09:04 PM ----------
push the rom to your sdcard and flash it using twrp 2.6.3.3
Click to expand...
Click to collapse
Sorry about that. The only recovery I have been able to flash is this one from this thread http://forum.xda-developers.com/showthread.php?t=2739126 . All "normal" CWM/TWRP recoveries will not boot up.
I just flashed ARHD, but when the Aroma installer finishes and I reboot the system this happens:
1. Screen turns off, then on.
2. A Google logo appears, turns off
3. Google logo appears, boots into the recovery I mentioned above
Any idea what this means?
Sari95 said:
Sorry about that. The only recovery I have been able to flash is this one from this thread http://forum.xda-developers.com/showthread.php?t=2739126 . All "normal" CWM/TWRP recoveries will not boot up.
Click to expand...
Click to collapse
why? do you have the active cmd line overflow error?
alray said:
why? do you have the active cmd line overflow error?
Click to expand...
Click to collapse
I do not, no, but after trying the usual CWM/ TWRP, the only recovery that actually would boot up was this one.
Sari95 said:
I do not, no, but after trying the usual CWM/ TWRP, the only recovery that actually would boot up was this one.
Click to expand...
Click to collapse
well try to download twrp 2.6.3.3 again from here
check md5: 72067aefb69541d40e8420d7aa46408d
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot the recovery
alray said:
well try to download twrp 2.6.3.3 again from here
check md5: 72067aefb69541d40e8420d7aa46408d
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot the recovery
Click to expand...
Click to collapse
All right, so now I am able to boot into proper TWRP through the steps, even though I have done the exact ones before anyway, I flashed ARHD again, but still no luck, as it does the same.
"1. Screen turns off, then on.
2. A Google logo appears, turns off
3. Google logo appears, boots into the recovery I mentioned above"
Sari95 said:
All right, so now I am able to boot into proper TWRP through the steps, even though I have done the exact ones before anyway, I flashed ARHD again, but still no luck, as it does the same.
"1. Screen turns off, then on.
2. A Google logo appears, turns off
3. Google logo appears, boots into the recovery I mentioned above"
Click to expand...
Click to collapse
have you wiped when you have flashed arhd?
and have you checked md5 value of the rom before flashing it?
alray said:
have you wiped when you have flashed arhd?
Click to expand...
Click to collapse
Of course. these are the steps after booting into recovery:
1. Wipe
2. Advanced Wipe --> check every box
3. Swipe to wipe
4. Install --> flash ARHD through USB OTG
Sari95 said:
Of course. these are the steps after booting into recovery:
1. Wipe
2. Advanced Wipe --> check every box
3. Swipe to wipe
4. Install --> flash ARHD through USB OTG
Click to expand...
Click to collapse
what version of arhd?
alray said:
what version of arhd?
Click to expand...
Click to collapse
The latest I believe:
"Android_Revolution_HD-One_71.1"
Sari95 said:
The latest I believe:
"Android_Revolution_HD-One_71.1"
Click to expand...
Click to collapse
have you checked md5 just in case?
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done.. The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery tried push with adb a new system FAILED tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
And my question is there a way to that my HTC One to get back to life?
Sorry about the topic and sorry about my bad english but i miss my HTC One
Sent from my SM-N9005 using XDA Premium 4 mobile app
No one could help me?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Laurentiu27 said:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done.. The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery tried push with adb a new system FAILED tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
And my question is there a way to that my HTC One to get back to life?
Sorry about the topic and sorry about my bad english but i miss my HTC One
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Please ensure you have a custom recovery (TWRP) and your bootloader is UNLOCKED if you are going to side load or push a custom rom onto your phone. If you are going to use the RUU route, then you need to have the bootloader LOCKED or RELOCKED. Here is a post that explains the steps to each method.
Laurentiu27 said:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
Click to expand...
Click to collapse
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done..
Click to expand...
Click to collapse
Locking the bootloader is only needed if you want to go back to stock using a RUU. I don't know if its what you have tried to do or any other method (guru reset rom, nandroid backup, stock odexed rom, Ruu.zip or ruu.exe?) The output of "fastboot getvar all" could help (dont post IMEI and SN) + what recovery and version # are you using?
The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery
Click to expand...
Click to collapse
bootloader can't wipe anything by itself. You probably did something wrong, can't tell you what at this point.
tried push with adb a new system
Click to expand...
Click to collapse
Which one? You need to be more precise i.e I tried to adb push X rom X version #.
FAILED
Click to expand...
Click to collapse
Again, be more precise. What was the error code/message? + post a screenshot of the cmd prompt when it fail
tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
Click to expand...
Click to collapse
Stop rushing things, or you'll probably make the situation worst. We will help you step by step if needed.
And my question is there a way to that my HTC One to get back to life?
Click to expand...
Click to collapse
Probably but:
what is your goal? you want to flash a custom rom or return back to stock rom?
Post the output of fastboot getvar all excluding imei and sn
what is your recovery + what is the version?
post a picture of the bootloader screen
when you speak about a rom/recovery always be specific what name and version
Soon as I get my HTC back from a friend ho want to try do it i will post everything thing that is needed with screenshots and errors
Sent from my SM-N9005 using XDA Premium 4 mobile app
ok got my htc one back still dead
im using twrp recovery latest one
now pls guide me step by step how to do it
i don't care if is a custom or stock just want my htc back to life
This is what i got on it in the white screen is Android revolution hd tring to bot(installed with otg cable and USB) the other 2 pictures are the the data from bootloader and the twrp recovery
Sent from my SM-N9005 using XDA Premium 4 mobile app
alray said:
Locking the bootloader is only needed if you want to go back to stock using a RUU. I don't know if its what you have tried to do or any other method (guru reset rom, nandroid backup, stock odexed rom, Ruu.zip or ruu.exe?) The output of "fastboot getvar all" could help (dont post IMEI and SN) + what recovery and version # are you using?
bootloader can't wipe anything by itself. You probably did something wrong, can't tell you what at this point.
Which one? You need to be more precise i.e I tried to adb push X rom X version #.
Again, be more precise. What was the error code/message? + post a screenshot of the cmd prompt when it fail
Stop rushing things, or you'll probably make the situation worst. We will help you step by step if needed.
Probably but:
what is your goal? you want to flash a custom rom or return back to stock rom?
Post the output of fastboot getvar all excluding imei and sn
what is your recovery + what is the version?
post a picture of the bootloader screen
when you speak about a rom/recovery always be specific what name and version
Click to expand...
Click to collapse
i atached up a few pictures about my phone you can read there what are they
i just want my phone back to life no matter if stock or custom
thank you
Laurentiu27 said:
ok got my htc one back still dead
im using twrp recovery latest one
now pls guide me step by step how to do it
i don't care if is a custom or stock just want my htc back to life
Click to expand...
Click to collapse
@alray asked for more info:
* Post the output of fastboot getvar all excluding imei and sn
* what is your recovery + what is the version?
* post a picture of the bootloader screen
* when you speak about a rom/recovery always be specific what name and version
and "latest" is not a version, you need to post a real version number and link to location/thread where you got your files from (both recovery and ROM)
this is the data from fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3750mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
im using twrp 2.7.1.1
custom rom android revolution hd 71.1
nkk71 said:
@alray asked for more info:
* Post the output of fastboot getvar all excluding imei and sn
* what is your recovery + what is the version?
* post a picture of the bootloader screen
* when you speak about a rom/recovery always be specific what name and version
and "latest" is not a version, you need to post a real version number and link to location/thread where you got your files from (both recovery and ROM)
Click to expand...
Click to collapse
this is the data from fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3750mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
im using twrp 2.7.1.1
custom rom android revolution hd 71.1
and tere is a few post earlier 3 pictures one about bootloader one about booting the rom and last is the twrp
this is the thread of the rom http://forum.xda-developers.com/showthread.php?t=2183023
Laurentiu27 said:
i atached up a few pictures about my phone you can read there what are they
i just want my phone back to life no matter if stock or custom
thank you
Click to expand...
Click to collapse
download twrp recovery 2.6.3.3 and save it to your adb/fastboot folder.
Make sure md5 match: 72067aefb69541d40e8420d7aa46408d
plug your phone to your computer and boot it in bootloader
open a command prompt from your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-booloader
now download this rom and save it to your adb/fastboot folder
Make sure md5 match:: CCC848CBF2B74C5FA33FD7E2269B0499
boot your phone in twrp recovery main menu
open a command prompt from your adb/fastboot folder
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait for the file to transfer, there is no progress bar, just wait until adb show the file transfer is completed (5-10 min)
then in twrp, select ''install'' browse the sdcard content and select "Android_Revolution_HD-One_71.1.zip"
and swipe to confirm flash. When asked to wipe your phone, select yes.
reboot phone to OS and see if it works or not.
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
alray said:
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
Click to expand...
Click to collapse
many have said 2.7.1.1 works fine, i haven't tried and am quite happy with 2.6.3.3... the 2.7 series not only had problems with flashing and charging, but also nandroids, but not sure about 2.7.1.1
but from the 3rd screenshot of the OP, that doesn't look like an m7 ROM, the bootanimation is distorted indicated it's not for 1080x1920 display.
PS: he should also format data, system and cache within twrp 2.6.3.3
alray said:
download twrp recovery 2.6.3.3 and save it to your adb/fastboot folder.
Make sure md5 match: 72067aefb69541d40e8420d7aa46408d
plug your phone to your computer and boot it in bootloader
open a command prompt from your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-booloader
now download this rom and save it to your adb/fastboot folder
Make sure md5 match:: CCC848CBF2B74C5FA33FD7E2269B0499
this is what i get
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
boot your phone in twrp recovery main menu
open a command prompt from your adb/fastboot folder
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait for the file to transfer, there is no progress bar, just wait until adb show the file transfer is completed (5-10 min)
then in twrp, select ''install'' browse the sdcard content and select "Android_Revolution_HD-One_71.1.zip"
and swipe to confirm flash. When asked to wipe your phone, select yes.
reboot phone to OS and see if it works or not.
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
Click to expand...
Click to collapse
this is what i get
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
error:device not found
update:seems that now is pushing it
flashed now waiting to boot
nkk71 said:
many have said 2.7.1.1 works fine, i haven't tried and am quite happy with 2.6.3.3... the 2.7 series not only had problems with flashing and charging, but also nandroids, but not sure about 2.7.1.1
but from the 3rd screenshot of the OP, that doesn't look like an m7 ROM, the bootanimation is distorted indicated it's not for 1080x1920 display.
PS: he should also format data, system and cache within twrp 2.6.3.3
Click to expand...
Click to collapse
the image is when tries to boot but i can asure is 71.1 ARH i downloade it 4 times from their server
that is the image when it tries to boot i get that screen
Laurentiu27 said:
the image is when tries to boot but i can asure is 71.1 ARH i downloade it 4 times from their server
that is the image when it tries to boot i get that screen
Click to expand...
Click to collapse
check md5 and you'll know if its the right rom. must match the md5 value I posted above.
if it still dont work, do what nkk71 said above, format data cache and system. you'll have to push to rom again after formatting.
to format data, go in twrp, ''wipe'' ---> "Format data"
to format system and cache go in "wipe" --> advanced wipe --> select cache and system and swipe to wipe
then adb push the rom again and install it again.
From flash screenshots
Sent from my SM-N9005 using XDA Premium 4 mobile app
Laurentiu27 said:
From flash screenshots
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so does it boot or not?
alray said:
so does it boot or not?
Click to expand...
Click to collapse
thank you!!! Thank you!!! It worked!!!
Laurentiu27 said:
thank you!!! Thank you!!! It worked!!!
Click to expand...
Click to collapse
:highfive:
Hey my HTC won't enter into recovery how do I fix it I have tried resetting the ruu but it keeps saying failed I need help bad ?
Yotekiller said:
Hey my HTC won't enter into recovery how do I fix it I have tried resetting the ruu but it keeps saying failed I need help bad ?
Click to expand...
Click to collapse
you have an AT&T Phone what file are you trying to flash? and how long has your OS been like that in the bootloader ?
Also your s-off so relocking the bootloader was not needed
clsA said:
you have an AT&T Phone what file are you trying to flash? and how long has your OS been like that in the bootloader ?
Also your s-off so relocking the bootloader was not needed
Click to expand...
Click to collapse
It's been like this for 60 days I have been in jail lol it crashed right before I went in yes it's att the file is a ruu zip m7 ul jb43 sense50 Mr cinguler us 3.17.502.3 decrypted sorry I didn't have the link handy for the file
Yotekiller said:
Hey my HTC won't enter into recovery how do I fix it I have tried resetting the ruu but it keeps saying failed I need help bad ?
Click to expand...
Click to collapse
can you post a "fastboot getvar all" excluding IMEI and s/n
it looks like you messed up some things, including your misc partition, fix that first: http://forum.xda-developers.com/showthread.php?t=2739126
then use an RUU
PS: you'll need to have bootloader unlocked, if you can't manage to unlock it in this state, let me know (but i'll need the output of your getvar all, excluding IMEI and s/n)
getvar all
nkk71 said:
can you post a "fastboot getvar all" excluding IMEI and s/n
it looks like you messed up some things, including your misc partition, fix that first: http://forum.xda-developers.com/showthread.php?t=2739126
then use an RUU
PS: you'll need to have bootloader unlocked, if you can't manage to unlock it in this state, let me know (but i'll need the output of your getvar all, excluding IMEI and s/n)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: 000000000000
(bootloader) imei: 000000000000
(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: 4042mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Screen shot
This is all I get when eentering recovery
yotekiller82 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-main: 8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
First off, make sure you're not on Windows 8.1, use Win7 or ubuntu or mac.
flash the attached file (that will downgrade hboot to 1.44, and install the noBCB recovery):
fastboot oem rebootRUU
fastboot flash zip fw_hb144_twrp-nobcb.zip
fastboot flash zip fw_hb144_twrp-nobcb.zip <- yes TWICE
fastboot reboot-bootloader
fastboot erase cache
-> enter RECOVERY
then follow the steps http://forum.xda-developers.com/showthread.php?t=2739126 to fix your corrupted misc partition.
once done, use https://www.androidfilehost.com/?fid=23501681358544977 to reset everything back to stock (in case something else is corrupt)
rename the above file to ruu.zip:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE
fastboot reboot-bootloader
i tried that didnt work
nkk71 said:
First off, make sure you're not on Windows 8.1, use Win7 or ubuntu or mac.
flash the attached file (that will downgrade hboot to 1.44, and install the noBCB recovery):
fastboot oem rebootRUU
fastboot flash zip fw_hb144_twrp-nobcb.zip
fastboot flash zip fw_hb144_twrp-nobcb.zip <- yes TWICE
fastboot reboot-bootloader
fastboot erase cache
-> enter RECOVERY
then follow the steps http://forum.xda-developers.com/showthread.php?t=2739126 to fix your corrupted misc partition.
once done, use https://www.androidfilehost.com/?fid=23501681358544977 to reset everything back to stock (in case something else is corrupt)
rename the above file to ruu.zip:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE
fastboot reboot-bootloader
Click to expand...
Click to collapse
ok the first step worked but everytime i try to step 2 it locks up my pc and wont push the ruu onto the phone any help on that one im using a laptop with win 7
yotekiller82 said:
ok the first step worked but everytime i try to step 2 it locks up my pc and wont push the ruu onto the phone any help on that one im using a laptop with win 7
Click to expand...
Click to collapse
can you be more specific, which "step 2" doesn't work, also best to copy/paste your command prompt output (please copy/paste, screenshots are very hard to read).
Step 2
nkk71 said:
can you be more specific, which "step 2" doesn't work, also best to copy/paste your command prompt output (please copy/paste, screenshots are very hard to read).
Click to expand...
Click to collapse
OK the first part of the post went good downgraded the hboot to 1.44 the second ruu won't go to the phone when you try to push it on it looks like it works it starts flashing a single bar on the next line a couple times then locks up the pic while the phone is setting in the black logo I have let it set for 20 min what is going on Idk how much more I can tell yall
I have got a copy of skydragon to flash in recovery but in the initial setupit keep rebooting so iI'm getting closer if that helps
Yotekiller said:
OK the first part of the post went good downgraded the hboot to 1.44 the second ruu won't go to the phone when you try to push it on it looks like it works it starts flashing a single bar on the next line a couple times then locks up the pic while the phone is setting in the black logo I have let it set for 20 min what is going on Idk how much more I can tell yall
I have got a copy of skydragon to flash in recovery but in the initial setupit keep rebooting so iI'm getting closer if that helps
Click to expand...
Click to collapse
Do you have htcsync installed on your pc it's known to cause problems with RUU mode. If so uninstall htcsync but keep the drivers.
Then try flash the RUU again
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Htc sync
Danny201281 said:
Do you have htcsync installed on your pc it's known to cause problems with RUU mode. If so uninstall htcsync but keep the drivers.
Then try flash the RUU again
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
No I don't have htc sync installed ? I really need my phone back up and running
Yotekiller said:
No I don't have htc sync installed ? I really need my phone back up and running
Click to expand...
Click to collapse
just reboot the phone and start the RUU process again till it finishes.
Did you md5 check your RUU download to be sure it's not corrupt ?
Yotekiller said:
OK the first part of the post went good downgraded the hboot to 1.44 the second ruu won't go to the phone when you try to push it on it looks like it works it starts flashing a single bar on the next line a couple times then locks up the pic while the phone is setting in the black logo I have let it set for 20 min what is going on Idk how much more I can tell yall
I have got a copy of skydragon to flash in recovery but in the initial setupit keep rebooting so iI'm getting closer if that helps
Click to expand...
Click to collapse
It would really help, if you copy/pasted your command prompt output.
Let's break this down again:
Step 1
First off, make sure you're not on Windows 8.1, use Win7 or ubuntu or mac.
Step 2
flash the attached file (that will downgrade hboot to 1.44, and install the noBCB recovery):
fastboot oem rebootRUU
fastboot flash zip fw_hb144_twrp-nobcb.zip
fastboot flash zip fw_hb144_twrp-nobcb.zip <- yes TWICE
fastboot reboot-bootloader
fastboot erase cache
Step 3
-> enter RECOVERY
then follow the steps http://forum.xda-developers.com/showthread.php?t=2739126 to fix your corrupted misc partition.
Step 4
once done, use https://www.androidfilehost.com/?fid=23501681358544977 to reset everything back to stock (in case something else is corrupt)
rename the above file to ruu.zip:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE
fastboot reboot-bootloader
Am understanding correctly that
Step 1: confirmed
Step 2: successful
Step 3: completed successfully
Step 4: this is where you get stuck??
Reboot the ruu
nkk71 said:
It would really help, if you copy/pasted your command prompt output.
Let's break this down again:
Step 1
First off, make sure you're not on Windows 8.1, use Win7 or ubuntu or mac.
Step 2
flash the attached file (that will downgrade hboot to 1.44, and install the noBCB recovery):
fastboot oem rebootRUU
fastboot flash zip fw_hb144_twrp-nobcb.zip
fastboot flash zip fw_hb144_twrp-nobcb.zip <- yes TWICE
fastboot reboot-bootloader
fastboot erase cache
Step 3
-> enter RECOVERY
then follow the steps http://forum.xda-developers.com/showthread.php?t=2739126 to fix your corrupted misc partition.
Step 4
once done, use https://www.androidfilehost.com/?fid=23501681358544977 to reset everything back to stock (in case something else is corrupt)
rename the above file to ruu.zip:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE
fastboot reboot-bootloader
Am understanding correctly that
Step 1: confirmed
Step 2: successful
Step 3: completed successfully
Step 4: this is where you get stuck??
Click to expand...
Click to collapse
Yes step 4 trying to flash the second file you give me
Yotekiller said:
Yes step 4 trying to flash the second file you give me
Click to expand...
Click to collapse
check MD5, and if the error persists:
hint:
It would really help, if you copy/pasted your command prompt output.
Copying command
nkk71 said:
check MD5, and if the error persists:
hint:
It would really help, if you copy/pasted your command prompt output.
Click to expand...
Click to collapse
It's kind of hard to do as I start the step 4 and it locks up the pc it won't response to anythingiI do I'm sorry I'm new to all this is there something I can do to get the pc to stop freezing up
I'm sorry if I don't understand what your trying to tell me ?
Yotekiller said:
It's kind of hard to do as I start the step 4 and it locks up the pc it won't response to anythingiI do I'm sorry I'm new to all this is there something I can do to get the pc to stop freezing up
I'm sorry if I don't understand what your trying to tell me ��
Click to expand...
Click to collapse
your pc completely freezes
then either fix your PC issues (whatever they may be, drivers, antivirus programs, firewalls, etc), or make life simple and make an Ubuntu Live USB (no need to install it, you can boot directly off a USB stick), check FAQ #5 here
The computer
nkk71 said:
your pc completely freezes
then either fix your PC issues (whatever they may be, drivers, antivirus programs, firewalls, etc), or make life simple and make an Ubuntu Live USB (no need to install it, you can boot directly off a USB stick), check FAQ #5 here
Click to expand...
Click to collapse
Yea the computer freezes up won't do nothing working on gettinga uUSB drive fixed up I don't have the fastest Internet where I live so lol sorry I have been trouble
Update I have one of my laptops running ubuntu now so hopefully in the next few days I can get all the drivers and everything I need to get the phone running again thanks for the help will update asap
Yotekiller said:
Yea the computer freezes up won't do nothing working on gettinga uUSB drive fixed up I don't have the fastest Internet where I live so lol sorry I have been trouble
Update I have one of my laptops running ubuntu now so hopefully in the next few days I can get all the drivers and everything I need to get the phone running again thanks for the help will update asap
Click to expand...
Click to collapse
You don't need drivers for your phone on ubuntu. If you have ubuntu running with adb/fastboot installed that's all you need. It will work
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!". All night it was restarting until the battery was dead this morning. Volume up and power work, and give 5 fails to mount the sd card. Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada. It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Is there anything else I can do with it? or is it just a paperweight now?
Thanks.
Well... There is one thing you could do.
squidstings said:
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!". All night it was restarting until the battery was dead this morning. Volume up and power work, and give 5 fails to mount the sd card. Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada. It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Is there anything else I can do with it? or is it just a paperweight now?
Thanks.
Click to expand...
Click to collapse
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant so you can just go ahead and root your phone then flash a ROM of your choice. Follow the steps I'll be listing below. Do these at your OWN RISK.
Prerequisites
-Working adb and fastboot. If you don't have them you can try using this.
-Your preferred custom ROM.
-Windows computer (WIndows 8.1 is fine).
-Your phone with a good amount of battery in it.
Unlocking and flashing process
1.Unlock your bootloader using HTC Dev.
2.Flash a custom recovery.
You flash a custom recovery like this using fastboot.
Code:
fastboot flash recovery <recoveryName>.img
3.Use TWRP to copy the ROM zip file to your internal storage.
4.Do a nandroid backup.
5.Do an advanced wipe (Wipe data, system, cache and dalvik cache partitions).
6.Do a factory reset (Wipe Data/Factory reset).
7.Flash the ROM's kernel using fastboot.
Code:
fastboot erase cache
then
Code:
fastboot flash boot <imageName>.img
7.Flash your preferred ROM.
8.Tell me if it worked and enjoy!
squidstings said:
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!".
Click to expand...
Click to collapse
This screen is the stock recovery main page.
Volume up and power work, and give 5 fails to mount the sd card.
Click to expand...
Click to collapse
You'll always get this "sd card mount fail" 5 times when revealing the stock recovery menu, its normal on the M7, there is no sd card to mount.
Code:
Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada.
Can you post the output of "fastboot getvar all" or at least post all the info you see in your bootloader menu.
It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Click to expand...
Click to collapse
Uninstall HTC Sync, you don't want this thing to interact with the phone while fixing it. Don't uninstall drivers, just HTC sync.
Is there anything else I can do with it? or is it just a paperweight now?
Click to expand...
Click to collapse
There is a RUU for Rogers to brings your phone back to stock but first, post your "fastboot getvar all" so we can make sure it will flash fine on your phone.
@The Android Manual Just for your information my friend:
The Android Manual said:
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant
Click to expand...
Click to collapse
Yes rogers are M7_UL too.
so you can just go ahead and root your phone then flash a ROM of your choice.
Click to expand...
Click to collapse
There is a RUU for Rogers, would recommend to wait for OP's phone info to see if he can use it and keep his phone locked & stock... unless he prefer a custom rom over stock
-Windows computer (WIndows 8.1 is fine).
Click to expand...
Click to collapse
It depends, fastboot commands won't work on Win 8.1 if his hboot is 1.44 as explained here
7.Flash the ROM's kernel using fastboot.
Code:
fastboot erase cache
then
Code:
fastboot flash boot <imageName>.img
Click to expand...
Click to collapse
Won't hurt but not needed (unlike some other htc's phone). Kernel partition (boot) isn't secured on the M7 which mean boot.img can be flashed in recovery if the bootloader is unlocked (s-off not needed). For this reason, all custom roms you'll find here will flash their own kernel automatically at the same time you flash the rom.
alray said:
This screen is the stock recovery main page.
You'll always get this "sd card mount fail" 5 times when revealing the stock recovery menu, its normal on the M7, there is no sd card to mount.
Code:
Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada.
Can you post the output of "fastboot getvar all" or at least post all the info you see in your bootloader menu.
Uninstall HTC Sync, you don't want this thing to interact with the phone while fixing it. Don't uninstall drivers, just HTC sync.
There is a RUU for Rogers to brings your phone back to stock but first, post your "fastboot getvar all" so we can make sure it will flash fine on your phone.
@The Android Manual Just for your information my friend:
Yes rogers are M7_UL too.
There is a RUU for Rogers, would recommend to wait for OP's phone info to see if he can use it and keep his phone locked & stock... unless he prefer a custom rom over stock
It depends, fastboot commands won't work on Win 8.1 if his hboot is 1.44 as explained here
Won't hurt but not needed (unlike some other htc's phone). Kernel partition (boot) isn't secured on the M7 which mean boot.img can be flashed in recovery if the bootloader is unlocked (s-off not needed). For this reason, all custom roms you'll find here will flash their own kernel automatically at the same time you flash the rom.
Click to expand...
Click to collapse
The last HTC device that lasted 3 years with me was the One X (my AT&T M7 either got bricked or had battery issue) and I never tried to get it S-OFF'ed since I really did no't see any use for it back in the day plus its screen was having problems anyway. This is new knowledge for me thanks!
and to the OP, if you need more help the quote button is your friend.
Good luck!
The Android Manual said:
The last HTC device that lasted 3 years with me was the One X
Click to expand...
Click to collapse
Wow mine (Tegra version) only lasted 13 months, had the infamous wifi issue (repaired myself) , overheat issue and motherboard finally died. I was very reluctant to buy htc again but finally I'm very satisfied with my M7.
Sorry, stomach flu
no idea what "fastboot getvar all" is.
I've already done the factory reset and wipe with the HTC tech, no improvement.
I'm not sure what info you need.
squidstings said:
Sorry, stomach flu
no idea what "fastboot getvar all" is.
I've already done the factory reset and wipe with the HTC tech, no improvement.
I'm not sure what info you need.
Click to expand...
Click to collapse
You can try the Roger's RUU in this post. You will need to follow the instructions in the OP. I believe in your case, since there is no 6.xx version for Roger's you can go directly to the Lollipop version.
The Android Manual said:
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant so you can just go ahead and root your phone then flash a ROM of your choice. Follow the steps I'll be listing below. Do these at your OWN RISK.
Prerequisites
-Working adb and fastboot. If you don't have them you can try using this.
-Your preferred custom ROM.
-Windows computer (WIndows 8.1 is fine).
-Your phone with a good amount of battery in it.
Unlocking and flashing process
1.Unlock your bootloader using HTC Dev.
Click to expand...
Click to collapse
I went to the site, HTCDev but my pc wouldn't allow me to do anything stating the certificate was unacceptable.
squidstings said:
I went to the site, HTCDev but my pc wouldn't allow me to do anything stating the certificate was unacceptable.
Click to expand...
Click to collapse
Looks like an issue with your web browser or something related with your internet option. You might want to try another browser or to adjust your browser security settings.
alray said:
Looks like an issue with your web browser or something related with your internet option. You might want to try another browser or to adjust your browser security settings.
Click to expand...
Click to collapse
I use firefox. I'll try another browser. which would you recommend? Chrome or IE
herre's my getvar info
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.631.8
version-misc: PVT SHIP S-ON
serialno:xxxx
imei:xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 3778mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
squidstings said:
I use firefox. I'll try another browser. which would you recommend? Chrome or IE
herre's my getvar info
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.631.8
version-misc: PVT SHIP S-ON
serialno:xxxx
imei:xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 3778mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
mb_guy said:
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
Click to expand...
Click to collapse
Thanks for the advice. I believe I've downloaded that RUU already ( sorry, what's the difference between RUU and ROM? is one custom and the other carrier generated?). I managed to get the identifier token last night, but the phone's never been set to allow usb debugging. will that cause issues with flashing? I'm not worried about losing anything, it's going to my son, so better clean.
mb_guy said:
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
Click to expand...
Click to collapse
I downloaded the ruu from the link on XDA but the .zip won't extract.
squidstings said:
Thanks for the advice. I believe I've downloaded that RUU already ( sorry, what's the difference between RUU and ROM?
Click to expand...
Click to collapse
A RUU stands for Rom Update Utility. Its an official file from HTC that flashes many partitions like the system partition (the rom/OS), the recovery partition, bootloader, radio partition, touch drivers, IR drivers...... well all partitions that are not specific to your phone and that will make it stock again. The only partition that are not flashed when using a RUU are those containing unique info about your phone like the MFG partition containing your IMEI number, Serial number, Date of manufactures etc.
A rom is only the /system partition flashed using a custom recovery. So when you flash a ROM (eiither custom or stock) you only flash the system partition and all other are kept like they was before the flash.
but the phone's never been set to allow usb debugging. will that cause issues with flashing? I'm not worried about losing anything, it's going to my son, so better clean.
Click to expand...
Click to collapse
You don't need usb debugging when flashing a RUU. USB debuging is only needed to use ADB commands when booted in the OS. A RUU is flashed using FASTBOOT commands when booted in the bootloader.
squidstings said:
I downloaded the ruu from the link on XDA but the .zip won't extract.
Click to expand...
Click to collapse
This is explained in the same post from where you have downloaded the file.... You might want to read the OP of the thread you are downloading files from :good: Not trying to be rude btw but lack of reading can sometime makes the situation worst. so just for you here it is again: The ruu are encrypted so they can't be extracted or opened and don't need to be, only flash it on your phone.
This is a collection of lollipop ruu.zip files for our beloved htc one m7 801.
I cannot test all of these files so any feedback will be welcome.
Also I have no responsibility if you phone explodes after flashing any of these files, I am just the uploader.
As many in this thread, ask about zip corruption, zip are not corrupted they are encrypted and can't open normally , they need decryption check md5 and dont try to unzip them
Click to expand...
Click to collapse
and instruction how to flash the ruu are posted just below these warnings, just click on the "show more" button.
---------- Post added at 05:12 PM ---------- Previous post was at 04:54 PM ----------
@squidstings
Might be easier to just unlock the bootloader, flash a recovery and then a rom like suggested at post #2
Youv said you already have your identifier token, go ahead and submit it to htcdev.com/bootloader (must create and account first). They will reply with an e-mail containing a file named Unlock_code.bin. Download and save the file in the same folder where you have adb and fastboot installed on your computer.
Then boot your phone in bootloader, make sure "fastboot usb" is shown in red (if not select the FASTBOOT option)
Open a terminal window from the same folder where you have adb and fastboot on your computer.
Type:
Code:
fastboot oem flash unlocktoken Unlock_code.bin
don't forget the capital U at Unlock_code.bin, fastboot and adb commands are case sensitive.
You should now see a screen asking if you want to unlock the phone, select YES (use volume up/down and power button)
The phone should then reboot to bootloader after performing a factory reset. Once done, confirm that your bootloader screen shows ***UNLOCKED*** and post back here, I'll post the isntruction how to flash the recovery.
Then boot your phone in bootloader, make sure "fastboot usb" is shown in red (if not select the FASTBOOT option)
Open a terminal window from the same folder where you have adb and fastboot on your computer.
Type:
Code:
fastboot oem flash unlocktoken Unlock_code.bin
don't forget the capital U at Unlock_code.bin, fastboot and adb commands are case sensitive.
You should now see a screen asking if you want to unlock the phone, select YES (use volume up/down and power button)
The phone should then reboot to bootloader after performing a factory reset. Once done, confirm that your bootloader screen shows ***UNLOCKED*** and post back here, I'll post the isntruction how to flash the recovery.[/QUOTE]
Thanks for the explanations.
Tried that. and got a command error
C:\Android>fastboot oem flash unlocktoken Unlock_code.bin
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
C:\Android>
I did read everything. got a bit confused by different methods and files suggested (maybe just different wording for the same proceedure?). I've been looking for ROMs and RUUs all day. after I've fixed this phone (hopefully) i want to root my m7.
squidstings said:
Thanks for the explanations.
Tried that. and got a command error
C:\Android>fastboot oem flash unlocktoken Unlock_code.bin
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
Click to expand...
Click to collapse
Sorry my bad here, its not "fastboot oem flash unlocktoken Unlock_code.bin"
Its "fastboot flash unlocktoken Unlock_code.bin" (remove "oem")
Full instructions are available at htcdev.com/bootloader, you might want to double-check the commands there since it looks like i'm a little tired
alray said:
Sorry my bad here, its not "fastboot oem flash unlocktoken Unlock_code.bin"
Its "fastboot flash unlocktoken Unlock_code.bin" (remove "oem")
Full instructions are available at htcdev.com/bootloader, you might want to double-check the commands there since it looks like i'm a little tired
Click to expand...
Click to collapse
I'm sorry. been reading so much about ROMs and RUUs that I forgot that I already unlocked the bootloader. I downloaded the 7.17.631.7.zip from the collection threat on here but it doesn't seem to work. sorry for the wasted time. SOOO sorry!
squidstings said:
I'm sorry. been reading so much about ROMs and RUUs that I forgot that I already unlocked the bootloader. I downloaded the 7.17.631.7.zip from the collection threat on here but it doesn't seem to work. sorry for the wasted time. SOOO sorry!
Click to expand...
Click to collapse
Think you're still confused with ROMs and RUUs.
Roms are what you'll find in the dvelopment forms and require custom recovery like twrp and bootloader unlocked. Roms likely just replace the system partition.
Ruu are total phone restore to stock, it will delete data and replace the phones recovery, system, data and boot partitions. To flash you require the bootloader locked, when the phone is S-on..
So if you want to flash the ruu 7.17.631.7 you need to relock the bootloader (fastboot oem lock), once you have that done, check for the latest OTA 7.17.631.35 and apply while you still have stock recovery. Then if you want a custom recovery like twrp again, unlock the bootloader (hope you kept the unlock token from before) @alray gave you the adb command a post or two above. Then flash the recovery.
Hope this helps.
mb_guy said:
Think you're still confused with ROMs and RUUs.
Roms are what you'll find in the dvelopment forms and require custom recovery like twrp and bootloader unlocked. Roms likely just replace the system partition.
Ruu are total phone restore to stock, it will delete data and replace the phones recovery, system, data and boot partitions. To flash you require the bootloader locked, when the phone is S-on..
So if you want to flash the ruu 7.17.631.7 you need to relock the bootloader (fastboot oem lock), once you have that done, check for the latest OTA 7.17.631.35 and apply while you still have stock recovery. Then if you want a custom recovery like twrp again, unlock the bootloader (hope you kept the unlock token from before) @alray gave you the adb command a post or two above. Then flash the recovery.
Hope this helps.
Click to expand...
Click to collapse
Now I'm completely confused. I thought I was unlocking it in order to bring it back from brickdom. I do understand RUU's and ROMs. It doesn't matter what I decide to put on it. My son would probably enjoy a rooted phone even if he knows nothing about it. The phone's a few years old so something as fast as it used to be would be enjoyed by him.
squidstings said:
Now I'm completely confused. I thought I was unlocking it in order to bring it back from brickdom. I do understand RUU's and ROMs. It doesn't matter what I decide to put on it. My son would probably enjoy a rooted phone even if he knows nothing about it. The phone's a few years old so something as fast as it used to be would be enjoyed by him.
Click to expand...
Click to collapse
Ok, let me try again.
If you want to flash a rom,
1) unlocked bootloader (you have)
2) Flash custom recovery like twrp (I don't see that you have done this) so may be easier to go the ruu route.
3) Use custom recovery to install rom. I like the arhd ones
If you want to flash the RUU
1) relock the bootloader
2) flash the ruu, once this is done and the phone rebooted and running it will be at 7.17.631.7, go to settings about and check for system updates. You should receive an OTA which is 7.17.631.35. Install it.
3) You can leave the phone like this, or re-unlock the bootloader and flash a custom recovery like twrp. This will give you the ability to do nandroid backups, root the phone or install custom roms if you want.
Either method should work, the choice is yours
Hope this is clearer.