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
Related
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
Hey guys, this is my first thread in XDA have quite some experience with samsung android but pretty new with HTC.
So, I dropped my HTC one day and it got stuck in a bootloop after few days. I havent change anything, stock, unrooted, never flashed any ROM into it, etc. I tried flashing RUU into it using fastboot command but it ddnt work since its still S-on.
Im working on mac as a platform and i dont think this is a major issue?
I am able to access recovery mode and fastboot mode, but wasnt able to push any file into it since debugging mode is off before the bootloop. ./adb devices command wont detect the phone. I also have HTC Sync installed on my mac but again, it wont detect the phone.
I also printed the getvar all result here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.631.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36xxxxxxx7
(bootloader) imei: 3544xxxxxx23453
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3876mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
also attached is screenshot of bootloader mode.
please help. my phone have been like this for 2-3 weeks now
RoyalChalksHere said:
Hey guys, this is my first thread in XDA have quite some experience with samsung android but pretty new with HTC.
So, I dropped my HTC one day and it got stuck in a bootloop after few days. I havent change anything, stock, unrooted, never flashed any ROM into it, etc. I tried flashing RUU into it using fastboot command but it ddnt work since its still S-on.
Im working on mac as a platform and i dont think this is a major issue?
I am able to access recovery mode and fastboot mode, but wasnt able to push any file into it since debugging mode is off before the bootloop. ./adb devices command wont detect the phone. I also have HTC Sync installed on my mac but again, it wont detect the phone.
I also printed the getvar all result here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.631.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36xxxxxxx7
(bootloader) imei: 3544xxxxxx23453
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3876mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
also attached is screenshot of bootloader mode.
please help. my phone have been like this for 2-3 weeks now
Click to expand...
Click to collapse
First of all is there any warranty left on the device. If there is it would be a good idea to take advantage of that before tampering with it. Especially as this happened after you dropped the phone. So there's a good chance it's a hardware problem.
I assume you've tried to factory reset from stock recovery?
If there's no warranty your best option is to unlock the bootloader. This will allow you to flash a Custom recovery. Then you can push a Rom to the phone, as adb will work in a custom recovery weather debugging is enabled or not.
I recommend TWRP 2.6.3.3 recovery it's not the latest twrp but is the most stable.
Danny201281 said:
First of all is there any warranty left on the device. If there is it would be a good idea to take advantage of that before tampering with it. Especially as this happened after you dropped the phone. So there's a good chance it's a hardware problem.
I assume you've tried to factory reset from stock recovery?
If there's no warranty your best option is to unlock the bootloader. This will allow you to flash a Custom recovery. Then you can push a Rom to the phone, as adb will work in a custom recovery weather debugging is enabled or not.
I recommend TWRP 2.6.3.3 recovery it's not the latest twrp but is the most stable.
Click to expand...
Click to collapse
yes ive tried factory reset too. I bought it in september 2013 from someone else and i think i lost the receipt, so i dont think I can take advantage of the warrant. i will keep looking though. is there any good link to unlock the bootloader?
RoyalChalksHere said:
yes ive tried factory reset too. I bought it in september 2013 from someone else and i think i lost the receipt, so i dont think I can take advantage of the warrant. i will keep looking though. is there any good link to unlock the bootloader?
Click to expand...
Click to collapse
www.htcdev.com to unlock the bootloader. You'll need to register an account. Then go to the Unlock my Bootloader section. Follow the instructions to get the Unlock code
I tried resetting rooted device... it rebooted in trwp... so i wiped it from there
when i reboot it doesn't move from the htc logo screen
when i try to power off, the soft keys blink and thats it.. nothing more.. i don't know what else to
@CallMe_Y_C said:
I tried resetting rooted device... it rebooted in trwp... so i wiped it from there
when i reboot it doesn't move from the htc logo screen
when i try to power off, the soft keys blink and thats it.. nothing more.. i don't know what else to
Click to expand...
Click to collapse
When you say you wiped it in twrp, did you Factory Reset or did you Format Data?
If you used Format Data then you wiped your entire device including the installed Rom. You should be able to force the device to power of by holding the power button for 60secs.
Then power on while holding volume down to get to the bootloader. Then you can boot to recovery and push a Rom with adb. :good:
awesome, thanks @Danny201281 i got TWRP to work on my HTC one. now on to custom rom. Which one is the best for HTC One? Any suggestion anyone? =)
RoyalChalksHere said:
awesome, thanks @Danny201281 i got TWRP to work on my HTC one. now on to custom rom. Which one is the best for HTC One? Any suggestion anyone? =)
Click to expand...
Click to collapse
Hehe I will always recommend Android Revolution HD because it's my favorite
But honestly is depends what you want from a Rom. ARHD is close to stock. It's very stable with no real bugs. It also has xposed support so you can make your own modifications. For me this gives a more personal experience.
MaximusHD is also a very popular close to stock Rom.
Or then you have the likes of Viper Rom or insertcoin which are more heavily modified.
But either way you look at it ARHD is a good place to start. It should be flashed with TWRP 2.6.3.3 TO avoid problems installing as most newer versions of TWRP don't seem to agree with the Aroma installer the Rom is packaged with :good:
Danny201281 said:
Hehe I will always recommend Android Revolution HD because it's my favorite
But honestly is depends what you want from a Rom. ARHD is close to stock. It's very stable with no real bugs. It also has xposed support so you can make your own modifications. For me this gives a more personal experience.
MaximusHD is also a very popular close to stock Rom.
Or then you have the likes of Viper Rom or insertcoin which are more heavily modified.
But either way you look at it ARHD is a good place to start. It should be flashed with TWRP 2.6.3.3 TO avoid problems installing as most newer versions of TWRP don't seem to agree with the Aroma installer the Rom is packaged with :good:
Click to expand...
Click to collapse
hey. ok so i downloaded AICP and installed them through TWRP and everything works fine. BUT, when i got to my homepage and use the phone for a couple of minutes, it restarted on its own. Any idea on why this is happening?
RoyalChalksHere said:
hey. ok so i downloaded AICP and installed them through TWRP and everything works fine. BUT, when i got to my homepage and use the phone for a couple of minutes, it restarted on its own. Any idea on why this is happening?
Click to expand...
Click to collapse
Go to Setting>About>Phone Identity
Is your IMEI displayed properly there?
Also check Setting>About>Software Information>More
Is your Baseband displayed correctly here?
Danny201281 said:
Go to Setting>About>Phone Identity
Is your IMEI displayed properly there?
Also check Setting>About>Software Information>More
Is your Baseband displayed correctly here?
Click to expand...
Click to collapse
oh they are both unknown. what should I do?
RoyalChalksHere said:
oh they are both unknown. what should I do?
Click to expand...
Click to collapse
9 times out of 10 this is a Hardware problem. You can try and flash a Firmware package and after that the only thing left Is to s-off and try an ruu. But if firmware doesn't fix it an ruu probably won't either.
As the phone had been dropped there's a high chance it's a hardware problem.
But I'll see if I can find a firmware package you can try. It's worth a go before writing it off.
Danny201281 said:
9 times out of 10 this is a Hardware problem. You can try and flash a Firmware package and after that the only thing left Is to s-off and try an ruu. But if firmware doesn't fix it an ruu probably won't either.
As the phone had been dropped there's a high chance it's a hardware problem.
But I'll see if I can find a firmware package you can try. It's worth a go before writing it off.
Click to expand...
Click to collapse
oh. so i guess warranty is the only way to go. or new phone. =( i even lost pictures from internal storage.
I couldn't find a firmware package but I did find this OTA. It contains the firmware we need. Download it and open the zip on your pc. Extract the firmware.zip and put the firmware.zip in your fastboot folder.
http://www.htc1guru.com/dld/ota_m7_...-19-631-9_release_372926h4tumwerl14wrs0u-zip/
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
< --- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Now you will need to unlock the bootloader again with your Unlock_code.bin
Flash TWRP and Flash your Rom again before the phone will boot. Then reboot the phone. :fingers-crossed:
If that doesn't do it Warranty is a possibility but you will need s-off to remove the signs the phone was tampered with.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
Yeah unfortunately Unlocking the Bootloader Wipes the device.
Danny201281 said:
I couldn't find a firmware package but I did find this OTA. It contains the firmware we need. Download it and open the zip on your pc. Extract the firmware.zip and put the firmware.zip in your fastboot folder.
http://www.htc1guru.com/dld/ota_m7_...-19-631-9_release_372926h4tumwerl14wrs0u-zip/
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
< --- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Now you will need to unlock the bootloader again with your Unlock_code.bin
Flash TWRP and Flash your Rom again before the phone will boot. Then reboot the phone. :fingers-crossed:
If that doesn't do it Warranty is a possibility but you will need s-off to remove the signs the phone was tampered with.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
Yeah unfortunately Unlocking the Bootloader Wipes the device.
Click to expand...
Click to collapse
so, it failed and shows this:
Mustafas-MacBook-Airlatform-tools mustafafarhanarifin$ ./fastboot flash zip OTA_M7_UL_K44_SENSE60_MR_Rogers_WWE_5.11.631.8_R-4.19.631.9_release_372926h4tumwerl14wrs0u.zip
target reported max download size of 1514139648 bytes
sending 'zip' (720552 KB)...
OKAY [ 28.648s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 111.120s
RoyalChalksHere said:
so, it failed and shows this:
Mustafas-MacBook-Airlatform-tools mustafafarhanarifin$ ./fastboot flash zip OTA_M7_UL_K44_SENSE60_MR_Rogers_WWE_5.11.631.8_R-4.19.631.9_release_372926h4tumwerl14wrs0u.zip
target reported max download size of 1514139648 bytes
sending 'zip' (720552 KB)...
OKAY [ 28.648s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 111.120s
Click to expand...
Click to collapse
You flashed the wrong zip. The firmware zip is inside the OTA
Open the OTA_M7_UL_K44_SENSE60_MR_Rogers_WWE_5.11.631.8_R-4.19.631.9_release_372926h4tumwerl14wrs0u.zip On your pc inside it is a firmware.zip extract the firmware.zip and flash it with the previous procedure
Danny201281 said:
I couldn't find a firmware package but I did find this OTA. It contains the firmware we need. Download it and open the zip on your pc. Extract the firmware.zip and put the firmware.zip in your fastboot folder.
http://www.htc1guru.com/dld/ota_m7_...-19-631-9_release_372926h4tumwerl14wrs0u-zip/
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
< --- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Now you will need to unlock the bootloader again with your Unlock_code.bin
Flash TWRP and Flash your Rom again before the phone will boot. Then reboot the phone. :fingers-crossed:
If that doesn't do it Warranty is a possibility but you will need s-off to remove the signs the phone was tampered with.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
Yeah unfortunately Unlocking the Bootloader Wipes the device.
Click to expand...
Click to collapse
Danny201281 said:
You flashed the wrong zip. The firmware zip is inside the OTA
Open the OTA_M7_UL_K44_SENSE60_MR_Rogers_WWE_5.11.631.8_R-4.19.631.9_release_372926h4tumwerl14wrs0u.zip On your pc inside it is a firmware.zip extract the firmware.zip and flash it with the previous procedure
Click to expand...
Click to collapse
youre amazing man. looks fine so far. baseband and IMEI is registered. im currently on android lollipop, and couldnt find any suitable gapps file. do you happen to know?
ok, so I shut down the phone to get back into fastboot mode with the button combo, but now it is not even turning on. black screen, not even charging. wtf.
Danny201281 said:
When you say you wiped it in twrp, did you Factory Reset or did you Format Data?
If you used Format Data then you wiped your entire device including the installed Rom. You should be able to force the device to power of by holding the power button for 60secs.
Then power on while holding volume down to get to the bootloader. Then you can boot to recovery and push a Rom with adb. :good:
Click to expand...
Click to collapse
i think i did both
i will try that after i get some charge on it
battery died last night
---------- Post added at 12:49 PM ---------- Previous post was at 12:23 PM ----------
@CallMe_Y_C said:
i think i did both
i will try that after i get some charge on it
battery died last night
Click to expand...
Click to collapse
can i get a suggested rom or supm to follow?
steps
thanks
RoyalChalksHere said:
youre amazing man. looks fine so far. baseband and IMEI is registered. im currently on android lollipop, and couldnt find any suitable gapps file. do you happen to know?
Click to expand...
Click to collapse
RoyalChalksHere said:
ok, so I shut down the phone to get back into fastboot mode with the button combo, but now it is not even turning on. black screen, not even charging. wtf.
Click to expand...
Click to collapse
Sorry man I had to get some sleep, So it was looking good for while then
What happened exactly? You flashed the firmware and Rom and all was ok. Then you just power off to go to bootloader and it never came back on? Did you flash anything in between that or that was it? You say you had a lollipop Rom can you provide a link to it please?
Is the device detected when you connect it to your pc? Does it show on device manager, maybe as Unknown device or QHSUSB_DLOAD?
---------- Post added at 04:09 PM ---------- Previous post was at 03:59 PM ----------
@CallMe_Y_C said:
i think i did both
i will try that after i get some charge on it
battery died last night
---------- Post added at 12:49 PM ---------- Previous post was at 12:23 PM ----------
can i get a suggested rom or supm to follow?
steps
thanks
Click to expand...
Click to collapse
I'd be happy to make a suggestion but can you post your getvar all? Not all roms are compatible with all devices.
It's kind of important to know what I'm recommending a Rom for
Alright, I recently purchased a phone that was stuck at the screen with the download icon in the arrow circle (http://forum.xda-developers.com/album.php?albumid=11886). When it is like this is can not be put into hboot. I then somehow got the phone into a boot loop. I did wipe the cache and that did not fix the problem. I did a factory reset via hboot, and it sent me back to the screen I mentioned before (http://forum.xda-developers.com/album.php?albumid=11886). I've now gotten the phone back into boot looping so I can access hboot. Recovery does work and you can access all the options. This phone is basically a stock HTC One M7. Has not been rooted, is locked, and it S-ON. Any help would be appreciated.
Thank you!
Flash a RUU
jdgreat4 said:
Flash a RUU
Click to expand...
Click to collapse
Could you link me to a tutorial? Apparently I need to know my MID and CID, and the video I did find to do that, needed usb debugging turned on in the settings which I don't even know if that is on. Can you link me to a how to tutorial for how to do this?
CloudHD said:
Could you link me to a tutorial? Apparently I need to know my MID and CID, and the video I did find to do that, needed usb debugging turned on in the settings which I don't even know if that is on. Can you link me to a how to tutorial for how to do this?
Click to expand...
Click to collapse
post the output of "fastboot getvar all", remove your imei and serialno before posting it
alray said:
post the output of "fastboot getvar all", remove your imei and serialno before posting it
Click to expand...
Click to collapse
Do I need a computer to do this? There's no option for this under fastboot in hboot. Currently don't have a computer available to me.
CloudHD said:
Do I need a computer to do this? There's no option for this under fastboot in hboot. Currently don't have a computer available to me.
Click to expand...
Click to collapse
Yes you need a computer with the latest android sdk installed and latest HTC drivers installed.
Btw, why did you buy this phone?
alray said:
Yes you need a computer with the latest android sdk installed and latest HTC drivers installed.
Btw, why did you buy this phone?
Click to expand...
Click to collapse
I bought it for a friend. He wanted something other than his locked up att samsung s4 active. He doesn't have much money and he figured he could fix this one and if he could't, he would just sell it again. I am personally used to iPhones (typing this on a jailbroken 4s right now) so this is all pretty new to me. We started troublesing it yesterday and he seemed to get stumped. He hates forums so I went ahead and signed up and made this post for him. Currently I have no access to a computer right now (at least one where I can install sdk and so on), but will have access later today. Will post when I have it.
CloudHD said:
I bought it for a friend. He wanted something other than his locked up att samsung s4 active. He doesn't have much money and he figured he could fix this one and if he could't, he would just sell it again. I am personally used to iPhones (typing this on a jailbroken 4s right now) so this is all pretty new to me. We started troublesing it yesterday and he seemed to get stumped. He hates forums so I went ahead and signed up and made this post for him. Currently I have no access to a computer right now (at least one where I can install sdk and so on), but will have access later today. Will post when I have it.
Click to expand...
Click to collapse
Latest HTC driver here: http://www.mediafire.com/download/8pawcxm9walwras/HTC_Driver_4.14.0.001.exe
You can install minimal adb and fastboot instead of the complete sdk, will be easier to use for you: http://forum.xda-developers.com/showthread.php?t=2317790
Once you have both installed, connect the phone to your computer, make sure its booted in bootloader mode --> fastboot mode and showing "fastboot usb" in red.
On your computer: Start menu --> Programs --> Minimal adb and fasboot --> minimal adb and fastboot
in the command prompt, type:
Code:
fastboot getvar all
copy and paste the output here (except the imei and s/n)
see you later
alray said:
Latest HTC driver here: http://www.mediafire.com/download/8pawcxm9walwras/HTC_Driver_4.14.0.001.exe
You can install minimal adb and fastboot instead of the complete sdk, will be easier to use for you: http://forum.xda-developers.com/showthread.php?t=2317790
Once you have both installed, connect the phone to your computer, make sure its booted in bootloader mode --> fastboot mode and showing "fastboot usb" in red.
On your computer: Start menu --> Programs --> Minimal adb and fasboot --> minimal adb and fastboot
in the command prompt, type:
Code:
fastboot getvar all
copy and paste the output here (except the imei and s/n)
see you later
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(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: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
CloudHD said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(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: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Ok well there is no RUU you can use with s-on so while the bootloader is locked all you can do is try to flash the current firmware. If the phone doesn't boot after that you will need to unlock the bootloader.
Download the firmware here https://www.androidfilehost.com/?fid=23501681358543602 put the zip in your fastboot folder on your pc and rename it "firmware.zip" Now with fastboot usb connected in the bootloader flash the firmware with the following fastboot commands
Code:
fastboot erase cache
fastboot oem rebootRUU
case sensitive
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now try to reboot the phone. If it doesn't boot you should now at least be able to do a factory reset. But you will need to unlock the bootloader at www.htcdev.com register an account and follow the instructions in the Unlock My Bootloader section. :good:
Danny201281 said:
Ok well there is no RUU you can use with s-on so while the bootloader is locked all you can do is try to flash the current firmware. If the phone doesn't boot after that you will need to unlock the bootloader.
Download the firmware here https://www.androidfilehost.com/?fid=23501681358543602 put the zip in your fastboot folder on your pc and rename it "firmware.zip" Now with fastboot usb connected in the bootloader flash the firmware with the following fastboot commands
Code:
fastboot erase cache
fastboot oem rebootRUU
case sensitive
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now try to reboot the phone. If it doesn't boot you should now at least be able to do a factory reset. But you will need to unlock the bootloader at www.htcdev.com register an account and follow the instructions in the Unlock My Bootloader section. :good:
Click to expand...
Click to collapse
Followed your instructions. Everything went good. I did a factory reset and the phone actually ended up rebooting. It's now just sitting here, and seems to be stuck at the htc logo. Going to go ahead and follow the steps to unlock my bootloader then report back.
@Danny201281 Boot loader is now unlocked!
CloudHD said:
@Danny201281 Boot loader is now unlocked!
Click to expand...
Click to collapse
Now the bootloader is unlocked you will need to flash a custom recovery and install a new Rom.
Download this http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img *<<<<< Put this in your fastboot folder and rename it recovery.img
Download this https://www.androidfilehost.com/?fid=23501681358545274
Boot the device to the bootloader and connect fastboot usb. Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
When back in the bootloader select Recovery from the menu to load TWRP recovery. Before we do anything else a little spring cleaning. Select "Wipe" from the TWRP menu the "Format Data" You will be prompted to type yes to continue. When its done Select "Reboot" then "Reboot Recovery" You will see a message "No OS Installed" Reboot anyway and say No when asked to install supersu.
Now back in TWRP recovery you should be able to see the Internal Storage on your PC. Copy the rom file to the Internal Storage then from the TWRP menu select install and choose the rom .zip :good:
During the install with Aroma choose these options
Stock Radio = Yes
Stock Recovery = Yes
Root = No
When the install is completed reboot the device and hopefully it should boot up normally without any problems :good: :fingers-crossed:
P.S The first boot after a new flash can take an extended amount of time. Don't be supprised if it's stuck on the HTC logo screen for 15 minutes+ Just be patient
Danny201281 said:
Now the bootloader is unlocked you will need to flash a custom recovery and install a new Rom.
Download this http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img *<<<<< Put this in your fastboot folder and rename it recovery.img
Download this https://www.androidfilehost.com/?fid=23501681358545274
Boot the device to the bootloader and connect fastboot usb. Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
When back in the bootloader select Recovery from the menu to load TWRP recovery. Before we do anything else a little spring cleaning. Select "Wipe" from the TWRP menu the "Format Data" You will be prompted to type yes to continue. When its done Select "Reboot" then "Reboot Recovery" You will see a message "No OS Installed" Reboot anyway and say No when asked to install supersu.
Now back in TWRP recovery you should be able to see the Internal Storage on your PC. Copy the rom file to the Internal Storage then from the TWRP menu select install and choose the rom .zip :good:
During the install with Aroma choose these options
Stock Radio = Yes
Stock Recovery = Yes
Root = No
When the install is completed reboot the device and hopefully it should boot up normally without any problems :good: :fingers-crossed:
P.S The first boot after a new flash can take an extended amount of time. Don't be supprised if it's stuck on the HTC logo screen for 15 minutes+ Just be patient
Click to expand...
Click to collapse
Thank you! My friend wanted to ask about soff and root for his device
CloudHD said:
Thank you! My friend wanted to ask about soff and root for his device
Click to expand...
Click to collapse
For s-off he will have to use Sunshine App it's the only working method for hboot 1.57. It does cost $25 but It's very easy. Just install and run the app :good:
Rooting can be done a number of ways the 2 easiest are to allow TWRP to install SupeSu when leaving recovery. Or you can install root with the Guru reset rom by selecting root during the installer. Also if he want's to keep the TWRP recovery don't take the stock recovery during the rom install.
Danny201281 said:
For s-off he will have to use Sunshine App it's the only working method for hboot 1.57. It does cost $25 but It's very easy. Just install and run the app :good:
Rooting can be done a number of ways the 2 easiest are to allow TWRP to install SupeSu when leaving recovery. Or you can install root with the Guru reset rom by selecting root during the installer. Also if he want's to keep the TWRP recovery don't take the stock recovery during the rom install.
Click to expand...
Click to collapse
alright. when formatting, I have been getting an unable to mount /cache and /system. should i be worries. Also, so when I do install the supesu? Can you give me some more detailed instructions like you have been doing? They're very helpful!!2220
CloudHD said:
alright. when formatting, I have been getting an unable to mount /cache and /system. should i be worries. Also, so when I do install the supesu? Can you give me some more detailed instructions like you have been doing? They're very helpful!!2220
Click to expand...
Click to collapse
Unable to mount /cache and /system happens during format or after? Did you reboot recovery after the format?
When you exit recovery TWRP will detect wheather or not the device is rooted. If it's not rooted TWRP will ask if you want to install supersu to root the phone. Say yes and TWRP will install root.
Although you could just install root when you install the rom. Just install with these options instead
Stock = Recovery No
Stock = Radio Yes
Root = Yes
Danny201281 said:
Unable to mount /cache and /system happens during format or after? Did you reboot recovery after the format?
When you exit recovery TWRP will detect wheather or not the device is rooted. If it's not rooted TWRP will ask if you want to install supersu to root the phone. Say yes and TWRP will install root.
Although you could just install root when you install the rom. Just install with these options instead
Stock = Recovery No
Stock = Radio Yes
Root = Yes
Click to expand...
Click to collapse
It seems to say this while it is updating partition details. Havent rebooted it as I wasn't sure about the cache and everything. So I guess before.
CloudHD said:
It seems to say this while it is updating partition details. Havent rebooted it as I wasn't sure about the cache and everything. So I guess before.
Click to expand...
Click to collapse
Reboot Recovery and then copy over and install the rom :good:
When you format data it is like repartitioning the phone. All the partitions are gone until you reboot. That's the reason they won't mount
Danny201281 said:
Reboot Recovery and then copy over and install the rom :good:
Click to expand...
Click to collapse
Alright, Thank you very much!!!
Will update how it all wetn when finished.
So I'm trying to update my firmware so I can get android 5.1 working on my phone to try it out. But I am running into trouble with adb finding my phone.
When I enter "adb devices" it returns a list of nothing, entering kill-server and start-server doesn't help.
My phone says fastboot USB when I plug it in and my computer says HTC One is found and working in the device manager (on my windows 8 machine it had a yellow exclamation next to it saying unknown device so I switched to a windows 7 machine which picks it up instantly)
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44) as that is needed to update the firmware however it cannot connect to my phone either (same adb problem)
adb is seemingly installed correctly, I've tired all usb 2 and usb 3 ports on my laptop and tried multiple usb cables. I've tried uninstalling and reinstalled different HTC drivers, I also tried installing the google usb drivers.
I need helps
Cofffey said:
So I'm trying to update my firmware so I can get android 5.1 working on my phone to try it out. But I am running into trouble with adb finding my phone.
When I enter "adb devices" it returns a list of nothing, entering kill-server and start-server doesn't help.
My phone says fastboot USB when I plug it in
Click to expand...
Click to collapse
If your phone says "fastboot usb" then it its booted in bootloader / fastboot mode.
ADB only works from a booted rom with usb debugging turned on or from a booted custom recovery (no matter if usb degug is on/off)
when in bootloader / fastboot usb mode, use fastboot commands, in this case "fastboot devices" will work.
and my computer says HTC One is found and working in the device manager (on my windows 8 machine it had a yellow exclamation next to it saying unknown device so I switched to a windows 7 machine which picks it up instantly)
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44)
Click to expand...
Click to collapse
hboot 1.44 isn't compatible with windows 8, use windows 7 or the windows 8 drivers fix. Will work fine after hboot is updated.
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44)
Click to expand...
Click to collapse
To achieve s-off on hboot 1.44 use Revone
as that is needed to update the firmware
Click to expand...
Click to collapse
S-OFF is only needed if you flash a custom firmware.
adb is seemingly installed correctly, I've tired all usb 2 and usb 3 ports on my laptop and tried multiple usb cables.
Click to expand...
Click to collapse
Always use usb 2.0 ports.
Post the outpuf of "fastboot getvar all" remove imei and sn before posting and also tell us what you want to do exactly, what firmware are you trying to flash?
I need helps[/QUOTE]
alray said:
If your phone says "fastboot usb" then it its booted in bootloader / fastboot mode.
ADB only works from a booted rom with usb debugging turned on or from a booted custom recovery (no matter if usb degug is on/off)
when in bootloader / fastboot usb mode, use fastboot commands, in this case "fastboot devices" will work.
hboot 1.44 isn't compatible with windows 8, use windows 7 or the windows 8 drivers fix. Will work fine after hboot is updated.
To achieve s-off on hboot 1.44 use Revone
S-OFF is only needed if you flash a custom firmware.
Always use usb 2.0 ports.
Post the outpuf of "fastboot getvar all" remove imei and sn before posting and also tell us what you want to do exactly, what firmware are you trying to flash?
I need helps
Click to expand...
Click to collapse
[/QUOTE]
Thanks for the reply!
I was following this video https://www.youtube.com/watch?v=ybu7fZa41so
using the fastboot commands listed which would result in cmd saying "waiting for device" forever. I didn't know adb and fastboot were different commands, adb works now that I know how to use it. Fastboot is still giving me trouble always waiting.
Should I update Hboot? I have my phone connected to a win7 laptop so that isn't a problem. Are there benefits other than windows 8?
C:\Users\Coffey>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****************
(bootloader) imei: ******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4063mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
When I flash a 5.1 rom, I get stuck in a loop of updating apps, it will update all the apps then restart and do it again forever.
I'm trying to install the firmware and rom from this page http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
It says I must have the latest firmware which they have provided, I'm using the second firmware they have linked https://www.androidfilehost.com/?fid=23991606952599455
Do I need s-off for this firmware?
Thanks you for your time.
Edit: It just clicked that I was able to get fastboot imformation when before it would just wait, now when running fastboot oem rebootRUU it just produces 3 dots and becomes unresponsive
Cofffey said:
Thanks for the reply!
I was following this video https://www.youtube.com/watch?v=ybu7fZa41so
using the fastboot commands listed which would result in cmd saying "waiting for device" forever. I didn't know adb and fastboot were different commands, adb works now that I know how to use it. Fastboot is still giving me trouble always waiting.
Should I update Hboot? I have my phone connected to a win7 laptop so that isn't a problem. Are there benefits other than windows 8?
C:\Users\Coffey>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****************
(bootloader) imei: ******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4063mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
When I flash a 5.1 rom, I get stuck in a loop of updating apps, it will update all the apps then restart and do it again forever.
I'm trying to install the firmware and rom from this page http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
It says I must have the latest firmware which they have provided, I'm using the second firmware they have linked https://www.androidfilehost.com/?fid=23991606952599455
Do I need s-off for this firmware?
Thanks you for your time.
Edit: It just clicked that I was able to get fastboot imformation when before it would just wait, now when running fastboot oem rebootRUU it just produces 3 dots and becomes unresponsive
Click to expand...
Click to collapse
The linked firmware is a custom firmware and requires s-off to be flashed. Why not simply updating your phone normally via ota updates from 1.29.666.5 to the latest Bell mobility version 7.17.666.7 and then you'll be able to flash 5.0+ custom roms.
If you want s-off better to achieve it now, its an easy task when on hboot 1.44 (revone s-off), newer hboot version will requires to use paid methods like sunshine s-off.
alray said:
The linked firmware is a custom firmware and requires s-off to be flashed. Why not simply updating your phone normally via ota updates from 1.29.666.5 to the latest Bell mobility version 7.17.666.7 and then you'll be able to flash 5.0+ custom roms.
If you want s-off better to achieve it now, its an easy task when on hboot 1.44 (revone s-off), newer hboot version will requires to use paid methods like sunshine s-off.
Click to expand...
Click to collapse
I had to install a 4.4.2 rom in order to s-off which I did, how would I go about getting an ota update?
Cofffey said:
I had to install a 4.4.2 rom in order to s-off which I did, how would I go about getting an ota update?
Click to expand...
Click to collapse
you are s-off now?
alray said:
you are s-off now?
Click to expand...
Click to collapse
Yea, currently running 4.4.2 Maximus HD 11.0.0
I tried to flash the custom firmware but ran into another error: failed (remote 42 custom id check fail)
Cofffey said:
Yea, currently running 4.4.2 Maximus HD 11.0.0
I tried to flash the custom firmware but ran into another error: failed (remote 42 custom id check fail)
Click to expand...
Click to collapse
Change your CID to GOOGL001:
boot in bootlaoder / fastboot usb mode
using fastboot enter these commands:
Code:
fastboot oem writecid GOOGL001
fastboot reboot-bootloader
Then confirm your cid is now GOOGL001:
Code:
fastboot oem readcid
output must be "GOOGL001"
reboot in ruu mode:
Code:
fastboot oem rebootRUU
flash this firmware, not the one you have linked above:
Code:
fastboot flash zip m7_GPE_5.1_FULL_firmware.zip
fastboot flash zip m7_GPE_5.1_FULL_firmware.zip
fastboot reboot-bootloader
then reflash twrp:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Boot in recovery, push the GPE rom to your phone and flash it. Reboot and your phone should boot in the 5.1 rom (first boot can take up to 10-15 mins, will be stuck at htc splash screen)
Dont forget to backup your important files before, the firmware flash will wipe your phone.
alray said:
Wait, I'll make some modification to the firmware so it can be flashed on your phone and I'll send it to you in a few minutes.
Click to expand...
Click to collapse
I couldn't find the bell firmware anywhere online, would I be able to use 5.1 roms on another firmware?
Cofffey said:
I couldn't find the bell firmware anywhere online, would I be able to use 5.1 roms on another firmware?
Click to expand...
Click to collapse
see edited post above. (#8)
alray said:
see edited post above. (#8)
Click to expand...
Click to collapse
Thanks for all the help, downloading all the files now
Quick question how do I push the 5.1 rom while in twrp? With adb?
Cofffey said:
Thanks for all the help, downloading all the files now
Quick question how do I push the 5.1 rom while in twrp? With adb?
Click to expand...
Click to collapse
If you flash the latest twrp version (2.8.7.0), you'll be able to see your phone storage from your computer when booted in twrp main menu. Copy your rom (drag and drop) from its current location to "My computer --> HTC One --> internal storage --> your rom.zip here"
or you can use adb push
Phone must be booted in twrp main menu and the rom.zip mus tbe in the same folder where adb is installed:
Code:
adb push your_rom.zip /sdcard
the command window will be unresponsive as long as the transfer is not completed (around 10 min)
alray said:
If you flash the latest twrp version (2.8.7.0), you'll be able to see your phone storage from your computer when booted in twrp main menu. Copy your rom (drag and drop) from its current location to "My computer --> HTC One --> internal storage --> your rom.zip here"
or you can use adb push
Phone must be booted in twrp main menu and the rom.zip mus tbe in the same folder where adb is installed:
Code:
adb push your_rom.zip /sdcard
the command window will be unresponsive as long as the transfer is not completed (around 10 min)
Click to expand...
Click to collapse
Everything is up and running! Thanks for all the help!
One last question though haha, would you flash something like ElementalX on top of this 5.1 rom?
Cofffey said:
Everything is up and running! Thanks for all the help!
One last question though haha, would you flash something like ElementalX on top of this 5.1 rom?
Click to expand...
Click to collapse
If you need some of elementalX features then yes flash it, you can always revert back to the previous kernel that comes with the rom by extracting it from the rom.zip and flashing it using fastboot:
Code:
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
ElementalX kernel must be flashed in recovery.
Hi Everyone
This is somewhat urgent and random. I literally woke up today and my phone has had the "No Command" Dialogue.. I do not know how it came about, the phone was working fine the night before, so I am not sure if the phone tried to update. The phone keeps on restarting back to the No Command dialogue. Your Help will be greatly appreciated!
I have an HTC One M7 GPE. It says LOCKED and S-On
LATOKYO said:
Hi Everyone
This is somewhat urgent and random. I literally woke up today and my phone has had the "No Command" Dialogue.. I do not know how it came about, the phone was working fine the night before, so I am not sure if the phone tried to update. The phone keeps on restarting back to the No Command dialogue. Your Help will be greatly appreciated!
I have an HTC One M7 GPE. It says LOCKED and S-On
Click to expand...
Click to collapse
So your phone is rebooting to the stock recovery.
First, try to erase cache
Code:
fastboot erase cache
fastboot reboot
If that doesn't work, try a factory reset
And finally you might be able to restore the phone using a RUU, you'll have to post the output of "fastboot getvar all" so we can direct you to the correct one.
Thank you so much for your response.
Questions:
How and where do I type those commands, and how do I use the "getvar"
alray said:
So your phone is rebooting to the stock recovery.
First, try to erase cache
Code:
fastboot erase cache
fastboot reboot
If that doesn't work, try a factory reset
And finally you might be able to restore the phone using a RUU, you'll have to post the output of "fastboot getvar all" so we can direct you to the correct one.
Click to expand...
Click to collapse
LATOKYO said:
Thank you so much for your response.
Questions:
How and where do I type those commands, and how do I use the "getvar"
Click to expand...
Click to collapse
already explained how yesterday to someone else in this thread http://forum.xda-developers.com/htc-one/help/htc-one-tampered-unlocked-t3150682
alray said:
already explained how yesterday to someone else in this thread http://forum.xda-developers.com/htc-one/help/htc-one-tampered-unlocked-t3150682
Click to expand...
Click to collapse
OK. I have both the Driver and SDK Installed.
LATOKYO said:
OK. I have both the Driver and SDK Installed.
Click to expand...
Click to collapse
ok so first try
Code:
fastboot erase cache
fastboot reboot
alray said:
ok so first try
Code:
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
OK.
I have some questions about what I installed, and If i installed the correct programs. I installed the SDK and the Drivers. Do I need to to install the packages with in the SDK? Do I also need to install the minimal ADB fastboot? Also, how do I access the command window, is it just the basic command prompt. I am a noob. I apologize.
alray said:
ok so first try
Code:
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I am typing the command in the ADB fastboot command prompt window. I am also typing the command at the "No Command" dialogue. Is that where/when I should be typing the commands? Or at the boot loader?
I typed in the first command, and it say's it's waiting for device.
How do I know if it's reading via USB.
alray said:
ok so first try
Code:
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
OK. So i typed the commands. It responded. It Rebooted. But now it reboots back to the error triangle, but this time it doesn't say anything. Just the Android on its back.
LATOKYO said:
I am typing the command in the ADB fastboot command prompt window. I am also typing the command at the "No Command" dialogue. Is that where/when I should be typing the commands? Or at the boot loader?
I typed in the first command, and it say's it's waiting for device.
Click to expand...
Click to collapse
The phone must be booted in bootloader / fastboot usb mode like explained in the link posted above.
How do I know if it's reading via USB.
Click to expand...
Click to collapse
using the command
Code:
fastboot devices
will output the device serial number if the computer detects it.
alray said:
The phone must be booted in bootloader / fastboot usb mode like explained in the link posted above.
using the command
Code:
fastboot devices
will output the device serial number if the computer detects it.
Click to expand...
Click to collapse
OK. So i typed the commands. It responded. It Rebooted. But now it reboots back to the error triangle, but this time it doesn't say anything. Just the Android on its back. I also have the GetVAR if you want that? I shouldn't post the IMEI and Serial Number, right?
LATOKYO said:
OK. So i typed the commands. It responded. It Rebooted. But now it reboots back to the error triangle, but this time it doesn't say anything. Just the Android on its back. I also have the GetVAR if you want that? I shouldn't post the IMEI and Serial Number, right?
Click to expand...
Click to collapse
yes post it but remove the imei and s/n.
you might want to try a factory reset meanwhile
alray said:
yes post it but remove the imei and s/n.
you might want to try a factory reset meanwhile
Click to expand...
Click to collapse
Since I never backed anything up, I am royally screwed? Or is there a way to back things up as of now?
Here is the GetVAR.
C:\Program Files (x86)\Minimal ADB and Fastboot>
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
LATOKYO said:
Since I never backed anything up, I am royally screwed? Or is there a way to back things up as of now?
Here is the GetVAR.
C:\Program Files (x86)\Minimal ADB and Fastboot>
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
Click to expand...
Click to collapse
If you didn't synced your files with a cloud service like dropbox/google drive you'll loose everything on the phone. The only way to backup files from a phone in this state is by using adb from a custom recovery but since your bootloader is locked you can't do that (unlocking the bootloader to flash a custom recovery will wipe the phone).
You can use the 5.11.1700.3 RUU to restore your phone. This will also wipe everything from the phone like if it was brand new.
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
make sure to use the fastboot.exe version posted in that thread to flash the ruu.
alray said:
If you didn't synced your files with a cloud service like dropbox/google drive you'll loose everything on the phone. The only way to backup files from a phone in this state is by using adb from a custom recovery but since your bootloader is locked you can't do that (unlocking the bootloader to flash a custom recovery will wipe the phone).
You can use the 5.11.1700.3 RUU to restore your phone. This will also wipe everything from the phone like if it was brand new.
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
make sure to use the fastboot.exe version posted in that thread to flash the ruu.
Click to expand...
Click to collapse
This is quite tragic. Do you know why my phone is in the state it's in? Originally, it kept trying to install 5.1, but it kept getting an error and stopping, would this have been the cause? I don't even understand why it did that.
So, If I do do the RUU to restore. can I go back to install the 5.1. Or will it do it automatically for me?
I really appreciate your help! I wish more people could answer.
alray said:
If you didn't synced your files with a cloud service like dropbox/google drive you'll loose everything on the phone. The only way to backup files from a phone in this state is by using adb from a custom recovery but since your bootloader is locked you can't do that (unlocking the bootloader to flash a custom recovery will wipe the phone).
You can use the 5.11.1700.3 RUU to restore your phone. This will also wipe everything from the phone like if it was brand new.
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
make sure to use the fastboot.exe version posted in that thread to flash the ruu.
Click to expand...
Click to collapse
Also,
Should I take this opportunity to do anything with my phone, like Unlock or S-Off? Is it worth it. Since I may have to wipe it clean, I might as well make it fully unlocked and s-off? Your thoughts?
LATOKYO said:
This is quite tragic. Do you know why my phone is in the state it's in?
Click to expand...
Click to collapse
It could be because of corrupted files, failed ota updates or even hardware failure.
Originally, it kept trying to install 5.1, but it kept getting an error and stopping, would this have been the cause?
Click to expand...
Click to collapse
Its possible
So, If I do do the RUU to restore. can I go back to install the 5.1. Or will it do it automatically for me?
Click to expand...
Click to collapse
The ruu will install the same version you were on before the phone died, you should be able to update to 5.1 after (6.04.1700.6).
LATOKYO said:
Also,
Should I take this opportunity to do anything with my phone, like Unlock or S-Off? Is it worth it. Since I may have to wipe it clean, I might as well make it fully unlocked and s-off? Your thoughts?
Click to expand...
Click to collapse
The phone must be able to boot in order to achieve s-off and since its s-on the bootloader must be locked or re-locked to flash the RUU.
Once it can boot then you can achieve s-off if you want before updating it.
alray said:
It could be because of corrupted files, failed ota updates or even hardware failure.
Its possible
The ruu will install the same version you were on before the phone died, you should be able to update to 5.1 after (6.04.1700.6).
The phone must be able to boot in order to achieve s-off and since its s-on the bootloader must be locked or re-locked to flash the RUU.
Once it can boot then you can achieve s-off if you want before updating it.
Click to expand...
Click to collapse
OK.
For the RUU Install, since I am an idiot and afriad:
Step by Step:
- I install the RUU for 5.11.1700.3 (since that's what my GetVar says I have)
- I follow these steps afterwards:
1. Rename file to RUU.zip
2. Place it in adb folder
3. Reboot phone to fastboot mode
4. S On need to relock bootloader (fastboot oem lock) , S Off lock not needed
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe : Here
Rename htc_fastboot to fastboot or if you don't rename it, then the command will be "htc_fastboot flash zip RUU.zip"
Run the following commands from your adb folder:
6.htc_fastboot oem rebootRUU
7.htc_fastboot flash zip RUU.zip
8.htc_fastboot reboot-bootloader
And then I am done?
LATOKYO said:
OK.
For the RUU Install, since I am an idiot and afriad:
Step by Step:
- I install the RUU for 5.11.1700.3 (since that's what my GetVar says I have)
- I follow these steps afterwards:
1. Rename file to RUU.zip
2. Place it in adb folder
3. Reboot phone to fastboot mode
4. S On need to relock bootloader (fastboot oem lock) , S Off lock not needed
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe : Here
Rename htc_fastboot to fastboot or if you don't rename it, then the command will be "htc_fastboot flash zip RUU.zip"
Run the following commands from your adb folder:
6.htc_fastboot oem rebootRUU
7.htc_fastboot flash zip RUU.zip
8.htc_fastboot reboot-bootloader
And then I am done?
Click to expand...
Click to collapse
Yes no need to do step 4 as your bootloader is already locked.
Don't forget you need to use fastboot.exe version provided in this thread
And careful when renaming the file to "ruu.zip". If the .zip is hidden before renaming the file "ruu" do not add .zip because you'll have double file extensions (ruu.zip + the hidden .zip = ruu.zip.zip). If you want to avoid double file extension, configure Window so it will never hide file extension.
If you have any problem during this process, post a screenshot of your command window so we can see what is wrong exactly.
@alray
Yes no need to do step 4 as your bootloader is already locked.
Don't forget you need to use fastboot.exe version provided in this thread
And careful when renaming the file to "ruu.zip". If the .zip is hidden before renaming the file "ruu" do not add .zip because you'll have double file extensions (ruu.zip + the hidden .zip = ruu.zip.zip). If you want to avoid double file extension, configure Window so it will never hide file extension.
If you have any problem during this process, post a screenshot of your command window so we can see what is wrong exactly.
Click to expand...
Click to collapse
Also, Can I do all this on MAC, or can this only be done on Windows?