Related
Question about HTC One m7
Ive got the reboot loop problem...
Yester i wantend to instal a new rom
After installation its said failed en keeps a reboot problem
now i watch movies and it works perfect until iv come to fastboot zip ruu.zip
it fails ...
youtube.com/watch?v=C0G0hKY4P9Y
I can go to my bootloadermode but not in my recoverymode
So i think everything is away from my phone
Please make it à little easy for me ... Its all new for me
Htc One m7
code: [2.24.401.8]
my bootloader is back Locked
Can u help me please ... i need my htc !!!
grtz
No'one ?
Karroowte said:
Question about HTC One m7
Ive got the reboot loop problem...
Yester i wantend to instal a new rom
After installation its said failed en keeps a reboot problem
now i watch movies and it works perfect until iv come to fastboot zip ruu.zip
it fails ...
youtube.com/watch?v=C0G0hKY4P9Y
I can go to my bootloadermode but not in my recoverymode
So i think everything is away from my phone
Please make it à little easy for me ... Its all new for me
Htc One m7
code: [2.24.401.8]
my bootloader is back Locked
Can u help me please ... i need my htc !!!
grtz
Click to expand...
Click to collapse
No one can help me ? i need my phone !
Karroowte said:
No one can help me ? i need my phone !
Click to expand...
Click to collapse
Need more information, can you post output from "fastboot getvar all" , If you already had a custom recovery installed, you need to re unlock your bootloader for it to work, That may be your problem with it not booting. Can you also post bootloader info.
info
mb_guy said:
Need more information, can you post output from "fastboot getvar all" , If you already had a custom recovery installed, you need to re unlock your bootloader for it to work, That may be your problem with it not booting. Can you also post bootloader info.
Click to expand...
Click to collapse
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT332W900154
(bootloader) imei: 354436053062863
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
So i must try evrything again just with my bootloader unlock, nog its relocked
Karroowte said:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT332W900154
(bootloader) imei: 354436053062863
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
So i must try evrything again just with my bootloader unlock, nog its relocked
Click to expand...
Click to collapse
If you have a custom recovery like TWRP or CWM installed the bootloader must remain unlocked!
no
mb_guy said:
If you have a custom recovery like TWRP or CWM installed the bootloader must remain unlocked!
Click to expand...
Click to collapse
i cant go to my recovery, so i think i dont have one ...
Karroowte said:
i cant go to my recovery, so i think i dont have one ...
Click to expand...
Click to collapse
bootloader isn't recovery. Does the device show relocked in the bootloader screen. If so unlock the bootloader again from the htcdev site, I'm assuming you must have done this once.
Exactly what all did you do yesterday, please explain step by step.
step
mb_guy said:
bootloader isn't recovery. Does the device show relocked in the bootloader screen. If so unlock the bootloader again from the htcdev site, I'm assuming you must have done this once.
Exactly what all did you do yesterday, please explain step by step.
Click to expand...
Click to collapse
i explain what im doing now,
my bootloader is unlocked
firt off all i got a map with evrything in, my zip file and fastboot, .....
shift + right click and open a window
i typ in
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip (i namedt the zip file ruu)
Karroowte said:
i explain what im doing now,
my bootloader is unlocked
firt off all i got a map with evrything in, my zip file and fastboot, .....
shift + right click and open a window
i typ in
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip (i namedt the zip file ruu)
Click to expand...
Click to collapse
What ruu are you flashing?
flash
mb_guy said:
What ruu are you flashing?
Click to expand...
Click to collapse
2.24.401.8
Karroowte said:
2.24.401.8
Click to expand...
Click to collapse
The entire file name would help, also the download link. I think the issue is that that is the wrong file.
wrong
mb_guy said:
The entire file name would help, also the download link. I think the issue is that that is the wrong file. flashable ruu's are .exe not zip And you do need a locked bootloader for those.
Click to expand...
Click to collapse
can u pleas pleas pleas send me the correct thing .... now im 2 days lookin how i fix my HTC one m7
and i realy realy realy want it now fix ...
can u send me the correct Ruu or somthing that fix my htc
thnx mate !
Karroowte said:
can u pleas pleas pleas send me the correct thing .... now im 2 days lookin how i fix my HTC one m7
and i realy realy realy want it now fix ...
can u send me the correct Ruu or somthing that fix my htc
thnx mate !
Click to expand...
Click to collapse
So let's backup a bit here.
Yesterday your phone was stock?
No custom recovery?
Locked bootloader?
You wanted to change rom so found the ruu and attempted to flash
Today the phone bootloops.?
Bootloader is unlocked?
Still no custom recovery?
no
mb_guy said:
So let's backup a bit here.
Yesterday your phone was stock?
No custom recovery?
Locked bootloader?
You wanted to change rom so found the ruu and attempted to flash
Today the phone bootloops.?
Bootloader is unlocked?
Still no custom recovery?
Click to expand...
Click to collapse
Yesterday i had a costum rom, Viper One
and i think unlocked bootloader with ***TAMPERED***
uhm yea i want to change te rom, but i think now there is nothing on my device because he reboot loops and wen i choose recovery he reboot loops
the bootloop is since yesterday when the installation failed from the athor rom, after then he loops
nog is my bootloader unlocked
Think
Karroowte said:
Yesterday i had a costum rom, Viper One
and i think unlocked bootloader with ***TAMPERED***
uhm yea i want to change te rom, but i think now there is nothing on my device because he reboot loops and wen i choose recovery he reboot loops
the bootloop is since yesterday when the installation failed from the athor rom, after then he loops
nog is my bootloader unlocked
Click to expand...
Click to collapse
OK so if you had viper one you must have had a custom recovery. I think this will work for you.
Download and flash TWRP 2.6.3.4 be sure to get the m7_ul version, this should get recovery working again.
http://techerrata.com/browse/twrp2/m7ul
Then use this guru reset file to reset your phone. Read the info and watch the video, then download the one for your device cid and partno
http://www.htc1guru.com/downloads/stock-rom-downloads/
should be this one
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
You will likely have to use adb push to get the zip to your device, you can do this in twrp (lots of threads on how to do this)
---------- Post added at 09:47 AM ---------- Previous post was at 09:30 AM ----------
Karroowte said:
i explain what im doing now,
my bootloader is unlocked
firt off all i got a map with evrything in, my zip file and fastboot, .....
shift + right click and open a window
i typ in
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip (i namedt the zip file ruu)
Click to expand...
Click to collapse
just another thought. If you haven't started on the guru reset path, You could also try this .
Do what you did here using the ruu you found (assuming it is correct) , but issue the last command twice
so
fastboot oem rebootruu
fastboot flash zip ruu.zip
fastboot flash zip ruu.rip
and see what happens, may be that simple
YEAAH
mb_guy said:
Think
OK so if you had viper one you must have had a custom recovery. I think this will work for you.
Download and flash TWRP 2.6.3.4 be sure to get the m7_ul version, this should get recovery working again.
http://techerrata.com/browse/twrp2/m7ul
Then use this guru reset file to reset your phone. Read the info and watch the video, then download the one for your device cid and partno
http://www.htc1guru.com/downloads/stock-rom-downloads/
should be this one
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
You will likely have to use adb push to get the zip to your device, you can do this in twrp (lots of threads on how to do this)
---------- Post added at 09:47 AM ---------- Previous post was at 09:30 AM ----------
just another thought. If you haven't started on the guru reset path, You could also try this .
Do what you did here using the ruu you found (assuming it is correct) , but issue the last command twice
so
fastboot oem rebootruu
fastboot flash zip ruu.zip
fastboot flash zip ruu.rip
and see what happens, may be that simple
Click to expand...
Click to collapse
ok thnx, but the download are going slow !
i just instal EZToolkit advanced and flash my recovery, and my recovery works
maybe can i use somthing else ?
link
mb_guy said:
Think
OK so if you had viper one you must have had a custom recovery. I think this will work for you.
Download and flash TWRP 2.6.3.4 be sure to get the m7_ul version, this should get recovery working again.
http://techerrata.com/browse/twrp2/m7ul
Then use this guru reset file to reset your phone. Read the info and watch the video, then download the one for your device cid and partno
http://www.htc1guru.com/downloads/stock-rom-downloads/
should be this one
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
You will likely have to use adb push to get the zip to your device, you can do this in twrp (lots of threads on how to do this)
---------- Post added at 09:47 AM ---------- Previous post was at 09:30 AM ----------
just another thought. If you haven't started on the guru reset path, You could also try this .
Do what you did here using the ruu you found (assuming it is correct) , but issue the last command twice
so
fastboot oem rebootruu
fastboot flash zip ruu.zip
fastboot flash zip ruu.rip
and see what happens, may be that simple
Click to expand...
Click to collapse
the guru files, dont wanne download ...
you have another rom ?
i can go to recovery maybe just (push file to phone) with another rom ?
an so instal ? or not ?
and so yes, can u tell me wich rom of give me a download link ?
Karroowte said:
ok thnx, but the download are going slow !
i just instal EZToolkit advanced and flash my recovery, and my recovery works
maybe can i use somthing else ?
Click to expand...
Click to collapse
Try your original ruu but do the flash zip twice before reboot.
Can always do the guru later if needed
sd
mb_guy said:
Try your original ruu but do the flash zip twice before reboot.
Can always do the guru later if needed
Click to expand...
Click to collapse
hi guys, a friend of my makes some own Roms ... and he helpt me yesterday and today,
iv got TWRP on my phone back, and i can use Adb,
the problem is, my phone doesnt find my SDcard ... crap ...
does somebody knows how you reset or reinstall your SDCard ?
thnks
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?
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
It happened when i was trying to flash a stock recovery img, so that i could update my htc one m7 with the official update from the phone "OTA_M7_UL_L50_SENSE60_MR_HTC_EUROPE_7.19.401.2-6.09.401.11_release_4217922wykl17vamtts1919.zip"
I cant do anything from the bootloader, beside i have my" Unlock_code" from past and can get that working allright, even that doesnt unlocks my phone anymore.
All though im able to use my phone, i want to update to the latest version.
So anyone out there in the big world, who can help me?
dukocuk said:
It happened when i was trying to flash a stock recovery img, so that i could update my htc one m7 with the official update from the phone "OTA_M7_UL_L50_SENSE60_MR_HTC_EUROPE_7.19.401.2-6.09.401.11_release_4217922wykl17vamtts1919.zip"
I cant do anything from the bootloader, beside i have my" Unlock_code" from past and can get that working allright, even that doesnt unlocks my phone anymore.
All though im able to use my phone, i want to update to the latest version.
So anyone out there in the big world, who can help me?
Click to expand...
Click to collapse
If you want to update your phone, why are you trying to unlock its bootloader? Do you have re-locked your bootloader with a custom recovery installed? Unlocking the bootloader will wipe /data/preload folder and preventing the ota update to install... I do not really understand what you are trying to do here because you are not giving much information about the actual state of your phone...
Is your phone running the stock rom?
You have relocked the bootloader with a custom recovery?
please post the output of "fastboot getvar all" (remove imei and serialno before posting)
alray said:
If you want to update your phone, why are you trying to unlock its bootloader? Do you have re-locked your bootloader with a custom recovery installed? Unlocking the bootloader will wipe /data/preload folder and preventing the ota update to install... I do not really understand what you are trying to do here because you are not giving much information about the actual state of your phone...
Is your phone running the stock rom?
You have relocked the bootloader with a custom recovery?
please post the output of "fastboot getvar all" (remove imei and serialno before posting)
Click to expand...
Click to collapse
i was trying to update it so i flashed a stockrecovery on it, else i wouldnt be able to update my phone with the OTA it gave me because i had a custom recovery on it before.
All i want is to update my phone with the stock rom, and then unlock it , so i can have a custom recovery again.
i messed it pretty good, so i have no recovery on it now i guess.
Its TAMPERED, RELOCKED and S-ON
my "fastboot getvar all" output is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3813mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.108s
dukocuk said:
i was trying to update it so i flashed a stockrecovery on it, else i wouldnt be able to update my phone with the OTA it gave me because i had a custom recovery on it before.
All i want is to update my phone with the stock rom, and then unlock it , so i can have a custom recovery again.
i messed it pretty good, so i have no recovery on it now i guess.
Its TAMPERED, RELOCKED and S-ON
my "fastboot getvar all" output is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3813mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.108s
Click to expand...
Click to collapse
What happens when you try to unlock the bootloader?
alray said:
What happens when you try to unlock the bootloader?
Click to expand...
Click to collapse
i can do flash unlock_code.bin, then it just deletes everything and im starting a fresh htc. In bootloader it then says tampered and relocked + s-on, it wont unlock it and even that it is locked, it wont update it to the newest official OTA update (7.19.401.2 / 804.78MB).
When it tries to enter recovery it isay: TAMPERED, RELOCKED and Security Warning , it just goes in the bootloader and not recovery.
dukocuk said:
i can do flash unlock_code.bin, then it just deletes everything and im starting a fresh htc. In bootloader it then says tampered and relocked + s-on, it wont unlock it and even that it is locked, it wont update it to the newest official OTA update (7.19.401.2 / 804.78MB).
When it tries to enter recovery it isay: TAMPERED, RELOCKED and Security Warning , it just goes in the bootloader and not recovery.
Click to expand...
Click to collapse
do you have a custom recovery installed ?
if so, the only way you can unlock the bootloader is to flash the stock firmware to put stock recovery back on, you cant lock or relock the bootloader with custom software on your phone.
Stock firmware here: https://www.androidfilehost.com/?fid=95832962473395871
i had custom recovery, but i flashed stockrecovery on it. Must have bricked the recovery somehow, because now i have no reecovery. If i try to flash the recovery i get this, no matter if i try to flash custom or stock recovery:
D:\adb>fastboot flash recover recovery_6.09.401.5.img
target reported max download size of 1514139648 bytes
sending 'recover' (12570 KB)...
OKAY [ 1.519s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.767s
maybe because its locked, and i cant unlock it.
dukocuk said:
i had custom recovery, but i flashed stockrecovery on it. Must have bricked the recovery somehow, because now i have no reecovery. If i try to flash the recovery i get this, no matter if i try to flash custom or stock recovery:
D:\adb>fastboot flash recover recovery_6.09.401.5.img
target reported max download size of 1514139648 bytes
sending 'recover' (12570 KB)...
OKAY [ 1.519s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.767s
maybe because its locked, and i cant unlock it.
Click to expand...
Click to collapse
yup, beacuse your bootloader is locked, only way to fix it is to flash the firmware, is there anything on the phone internal storage that you need to keep, pictures, musci, documents etc ?
Seanie280672 said:
yup, beacuse your bootloader is locked, only way to fix it is to flash the firmware, is there anything on the phone internal storage that you need to keep, pictures, musci, documents etc ?
Click to expand...
Click to collapse
the hel-l with my docs and stuff, how do you flash this .zip file? I cant reach my recovery, since its messed.
dukocuk said:
the hel-l with my docs and stuff, how do you flash this .zip file? I cant reach my recovery, since its messed.
Click to expand...
Click to collapse
with the phone in fastbootUSB mode and the zip in the same folder as adb and fastboot on your computer, issue these commands:
ps: its easier if you rename the download to just firmware rather than M7_UL_Firmware_6.09.401.11
fastboot oem rebootRUU (case sensetive) phone screen will go black with silver HTC logo
fastboot flash zip firmware.zip (first time it might say failed: please flush again) so issue the command again
fastboot flash zip firmware.zip
make sure it now says successful at the bottom - this is important
if so then,
fastboot reboot-bootloader
if not report back here first
when you get back to the bootloader, try and unlock it again, you may have to go back to HTCDev site and get a new unlock token.
Seanie280672 said:
with the phone in fastbootUSB mode and the zip in the same folder as adb and fastboot on your computer, issue these commands:
ps: its easier if you rename the download to just firmware rather than M7_UL_Firmware_6.09.401.11
fastboot oem rebootRUU (case sensetive) phone screen will go black with silver HTC logo
fastboot flash zip firmware.zip (first time it might say failed: please flush again) so issue the command again
fastboot flash zip firmware.zip
make sure it now says successful at the bottom - this is important
if so then,
fastboot reboot-bootloader
if not report back here first
when you get back to the bootloader, try and unlock it again, you may have to go back to HTCDev site and get a new unlock token.
Click to expand...
Click to collapse
im tampered and unlocked now after i did what you told, but i used my old Unlock.bin. Where do i go from here?
dukocuk said:
im tampered and unlocked now after i did what you told, but i used my old Unlock.bin. Where do i go from here?
Click to expand...
Click to collapse
ok follow these instructions I laid out for someone else if your looking to return to stock, they are exactly the same for your phone as your on the same firmware:
http://forum.xda-developers.com/showpost.php?p=59273464&postcount=4
ps. you dont need to lock or relock your bootloader to update, you only need locked or relocked whilst s-on to flash firmware or run an RUU.
Seanie280672 said:
ok follow these instructions I laid out for someone else if your looking to return to stock, they are exactly the same for your phone as your on the same firmware:
http://forum.xda-developers.com/showpost.php?p=59273464&postcount=4
ps. you dont need to lock or relock your bootloader to update, you only need locked or relocked whilst s-on to flash firmware or run an RUU.
Click to expand...
Click to collapse
so all you need is a stock recovery to update OTA? When do i use firmware and RUU? Sorry my noobish questions, did read the guides but didnt get the idea fully.
dukocuk said:
so all you need is a stock recovery to update OTA? When do i use firmware and RUU? Sorry my noobish questions.
Click to expand...
Click to collapse
use firmware for when you have problems like you did earlier or if your s-off, earlier RUU's are only if your phone is S-off and saves all this messing around, its full firmware and rom in one package, if you were s-off, then we could of just flashed the corrisponding firmware to an RUU, ran the RUU, you'd then be 100% factory stock, just boot and update from there.
theres a bit more to it than just stock recovery, your rom has to be 100% stock, no root, no custom kernals or anything like that, no removed stock apps.
trouble is, when you unlock the bootloader, it deletes a hidden folder (data/preload folder) its HTC's little way of say, now you've unlocked, you can never update with us again, that backup will put all of that back on your phone.
Seanie280672 said:
use firmware for when you have problems like you did earlier or if your s-off, earlier RUU's are only if your phone is S-off and saves all this messing around, its full firmware and rom in one package, if you were s-off, then we could of just flashed the corrisponding firmware to an RUU, ran the RUU, you'd then be 100% factory stock, just boot and update from there.
theres a bit more to it than just stock recovery, your rom has to be 100% stock, no root, no custom kernals or anything like that, no removed stock apps.
trouble is, when you unlock the bootloader, it deletes a hidden folder (data/preload folder) its HTC's little way of say, now you've unlocked, you can never update with us again, that backup will put all of that back on your phone.
Click to expand...
Click to collapse
So you gave me the firmware, its on the phone now.
I had Unlock.bin, but i can see it has supersu installed in it.
i flashed to stockrecovery from where you helped the other guy.
Im waiting for my download OTA update to finish (official).
Will i be able to update it even that i see its rootet (supersu)???
dukocuk said:
So you gave me the firmware, its on the phone now.
I had Unlock.bin, but i can see it has supersu installed in it.
i flashed to stockrecovery from where you helped the other guy.
Im waiting for my download OTA update to finish (official).
Will i be able to update it even that i see its rootet (supersu)???
Click to expand...
Click to collapse
try it, but I think you'll have to follow that whole post of mine that I linked you too, superSU modifies system files to root, so the OTA may error out.
if it does error, you'll have to start from here "what you need to do is flash TWRP 2.8.5.0 from here:" and follow every step, you wont need that firmware that you downloaded earlier again, just dont lock your bootloader.
Seanie280672 said:
try it, but I think you'll have to follow that whole post of mine that I linked you too, superSU modifies system files to root, so the OTA may error out.
if it does error, you'll have to start from here "what you need to do is flash TWRP 2.8.5.0 from here:" and follow every step, you wont need that firmware that you downloaded earlier again, just dont lock your bootloader.
Click to expand...
Click to collapse
you gave him https://www.androidfilehost.com/?fid=95832962473396067, what will it be on my phone? That other zip file you gave me? Is it that one i should install from recovery? If yes, why? Didnt i just installed it from RUU?
dukocuk said:
you gave him https://www.androidfilehost.com/?fid=95832962473396067, what will it be on my phone?
Click to expand...
Click to collapse
same files for your phone, have a look at the version main on your fastbootgetvar all on the first page 6.09.401.11 that download is the same version main, M7_UL_TWRP_Nandroid_6.09.401.11_(inkl._preload-Ordner).rar and this part means it contains the data/preload folder (inkl._preload-Ordner)
dukocuk said:
That other zip file you gave me? Is it that one i should install from recovery? If yes, why? Didnt i just installed it from RUU?
Click to expand...
Click to collapse
bin that firmware file, you wont need it again.
Seanie280672 said:
same files for your phone, have a look at the version main on your fastbootgetvar all on the first page 6.09.401.11 that download is the same version main, M7_UL_TWRP_Nandroid_6.09.401.11_(inkl._preload-Ordner).rar and this part means it contains the data/preload folder (inkl._preload-Ordner)
bin that firmware file, you wont need it again.
Click to expand...
Click to collapse
Thank, i followed the guide you made for that person, it helped me out too.
I appreciate it.
Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...
From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.
dorsetqpr said:
From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.
Click to expand...
Click to collapse
Correct
Hoelli169 said:
Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...
Click to expand...
Click to collapse
Windows 8 and hboot 1.44 are not compatible. You should use Windows 7 or better still Linux (preferably ubuntu 32bit)
Sent from my M7 ARHD 84-Kitkat
OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(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.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:
Hoelli169 said:
OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(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.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:
Click to expand...
Click to collapse
Download this recovery. http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware. Then use rumrunner to gain s-off. :good:
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
Download this recovery.
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Worked!
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Click to expand...
Click to collapse
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware.
Click to expand...
Click to collapse
219486214 reboots later... JB*3.62.401.1, hooray!
Then use rumrunner to gain s-off. :good:
Click to expand...
Click to collapse
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery
Hoelli169 said:
Worked!
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
219486214 reboots later... JB*3.62.401.1, hooray!
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery
Click to expand...
Click to collapse
You need stock rom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here https://www.androidfilehost.com/?w=files&flid=32777
You must flash at least one zip for each firmware version. I.e if your on 3.xx.401.x then you have to flash
4.xx.401.x
5.xx.401.x
6.xx.401.x
7.xx.401.x
Then you can flash twrp and install a lollipop rom. You should have the rom on the internal storage before you start as the device won't boot after flashing the firmware as it will replace the stock boot.img. So you will need to flash a rom before it will boot. :good:
Commands for flashing the firmware zip as follows.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip "name-of-firmware".zip
fastboot flash zip "name-of-firmware".zip
fastboot reboot-bootloader
Flash TWRP, Install Rom, Done :good:
Sent from my SM-T230 using Tapatalk
Danny201281 said:
You need stock tom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!
Hoelli169 said:
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!
Click to expand...
Click to collapse
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk
Danny201281 said:
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^
Hoelli169 said:
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^
Click to expand...
Click to collapse
[emoji28] few!! Yeah firmware can be tricky. Glad you got it sorted though. Dexter's thread is a life saver. . Enjoy lollipop :good:
Sent from my SM-T230 using Tapatalk