Database Develop

[Q] HTC One won't boot into recovery after ota

Hey guys,
Okay, I have a stock HTC One with S-On and locked bootloader.It has stock recovery and hboot 1.44. It is running 1.28.401.7 firmware with cid of HTC__001.
Today morning I tried to install OTA Update for 4.2.2, but there was some problem.
The device rebooted, went into stock recovery and then abruptly rebooted to the ROM. There was a message saying "There was an abnormal reboot. Send data to HTC?" and then a "Update was corrupted, please download again"
Later, I decided to manually flash the OTA Update but the phone wouldn't enter stock recovery.
So I unlocked the bootloader and tried flashing twrp 2.6.3.0 and tried to boot into it.
But the device flashes "Entering recovery" for about a second and boots back to rom.
I tried clearing the cache through fastboot, I tried different versions of twrp eg 2.5.0.0, 2.6.3.3 multiple times.
But it did not work.
Also, I have installed custom recovery in the past so this problem has not been forever.
A lot of people have had this problem but unfortunately none of their solutions worked for me :/
Can you please suggest me a way to get recovery working again?
I have the RUU but it is useless without s-off and everything else needs root, for which i need the custom recovery.
Any help would be appreciated!
Thanks!

anibjoshi said:
Hey guys,
Okay, I have a stock HTC One with S-On and locked bootloader.It has stock recovery and hboot 1.44. It is running 1.28.401.7 firmware with cid of HTC__001.
Today morning I tried to install OTA Update for 4.2.2, but there was some problem.
The device rebooted, went into stock recovery and then abruptly rebooted to the ROM. There was a message saying "There was an abnormal reboot. Send data to HTC?" and then a "Update was corrupted, please download again"
Later, I decided to manually flash the OTA Update but the phone wouldn't enter stock recovery.
So I unlocked the bootloader and tried flashing twrp 2.6.3.0 and tried to boot into it.
But the device flashes "Entering recovery" for about a second and boots back to rom.
I tried clearing the cache through fastboot, I tried different versions of twrp eg 2.5.0.0, 2.6.3.3 multiple times.
But it did not work.
Also, I have installed custom recovery in the past so this problem has not been forever.
A lot of people have had this problem but unfortunately none of their solutions worked for me :/
Can you please suggest me a way to get recovery working again?
I have the RUU but it is useless without s-off and everything else needs root, for which i need the custom recovery.
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Did you tried to re-download the ota file? Looks like its corrupted.
Also you can't apply ota update with custom recovery. If you wanted to manually apply ota, you should have unlocked bootloader only and booted in stock recovery.
you should try to clear cache, re-install stock recovery and re-download the ota and try again
btw you don't need s-off to ruu from your version. s-off is required when ruu is a downgrade in version and when you need to downgrade hboot. you should be fine to restore from that ruu without s-off
---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------
anibjoshi said:
Hey guys,
Okay, I have a stock HTC One with S-On and locked bootloader.It has stock recovery and hboot 1.44. It is running 1.28.401.7 firmware with cid of HTC__001.
Today morning I tried to install OTA Update for 4.2.2, but there was some problem.
The device rebooted, went into stock recovery and then abruptly rebooted to the ROM. There was a message saying "There was an abnormal reboot. Send data to HTC?" and then a "Update was corrupted, please download again"
Later, I decided to manually flash the OTA Update but the phone wouldn't enter stock recovery.
So I unlocked the bootloader and tried flashing twrp 2.6.3.0 and tried to boot into it.
But the device flashes "Entering recovery" for about a second and boots back to rom.
I tried clearing the cache through fastboot, I tried different versions of twrp eg 2.5.0.0, 2.6.3.3 multiple times.
But it did not work.
Also, I have installed custom recovery in the past so this problem has not been forever.
A lot of people have had this problem but unfortunately none of their solutions worked for me :/
Can you please suggest me a way to get recovery working again?
I have the RUU but it is useless without s-off and everything else needs root, for which i need the custom recovery.
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
and btw its easier to s-off on 1.44 hboot, so if you want s-off better to try it now with revone

alray said:
Did you tried to re-download the ota file? Looks like its corrupted.
Also you can't apply ota update with custom recovery. If you wanted to manually apply ota, you should have unlocked bootloader only and booted in stock recovery.
you should try to clear cache, re-install stock recovery and re-download the ota and try again
btw you don't need s-off to ruu from your version. s-off is required when ruu is a downgrade in version and when you need to downgrade hboot. you should be fine to restore from that ruu without s-off
and btw its easier to s-off on 1.44 hboot, so if you want s-off better to try it now with revone
Click to expand...
Click to collapse
So if i flash the RUU with s-on, unlocked bootloader, custom recovery and non root, it will be fine?
It wont brick my phone?
Yes, i tried revone, it says failed to map memory 15 times and then error code 2

alray said:
Did you tried to re-download the ota file? Looks like its corrupted.
Also you can't apply ota update with custom recovery. If you wanted to manually apply ota, you should have unlocked bootloader only and booted in stock recovery.
you should try to clear cache, re-install stock recovery and re-download the ota and try again
btw you don't need s-off to ruu from your version. s-off is required when ruu is a downgrade in version and when you need to downgrade hboot. you should be fine to restore from that ruu without s-off
---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------
and btw its easier to s-off on 1.44 hboot, so if you want s-off better to try it now with revone
Click to expand...
Click to collapse
That RUU is not working! It says download the correct version of RUU and try again!
Will it be okay if i flash a later version eg 2.XX.XXX.X? I have s-on...will it brick my device?
Please reply
Thank you

alray said:
Did you tried to re-download the ota file? Looks like its corrupted.
Also you can't apply ota update with custom recovery. If you wanted to manually apply ota, you should have unlocked bootloader only and booted in stock recovery.
you should try to clear cache, re-install stock recovery and re-download the ota and try again
btw you don't need s-off to ruu from your version. s-off is required when ruu is a downgrade in version and when you need to downgrade hboot. you should be fine to restore from that ruu without s-off
---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------
and btw its easier to s-off on 1.44 hboot, so if you want s-off better to try it now with revone
Click to expand...
Click to collapse
I am in big problem. Please tell me what i should do. The 1.28.401.7 RUU failed to install.
It gives an error:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
What should I do? Can I flash a 2.24 RUU with s-on?
can i flash the stock rom guru reset 1.29? http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
I have 1.28.401.7 version installed.
Please help me I have no idea what to do
Thanks!

You should install a stock recovery that matches the software you had before trying to update.
As to the RUU, you can flash an OTA if you were trying to update to 4.2.2, I think. I used this one 1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
Have you tried it?

anibjoshi said:
I am in big problem. Please tell me what i should do. The 1.28.401.7 RUU failed to install.
It gives an error:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
What should I do? Can I flash a 2.24 RUU with s-on?
can i flash the stock rom guru reset 1.29? http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
I have 1.28.401.7 version installed.
Please help me I have no idea what to do
Thanks!
Click to expand...
Click to collapse
sorry to reply late, I was very busy at work.
Post the output of ''fastboot getvar all'' minus imei and s/n, so i can confirm you have the right RUU for your phone. Also, according to nkk71' table here, if S-ON, you can only use ruu with locked/relocked bootloader (if ruu is the same or higher version). So you probably need to re-lock bootloader.
post the getvar 1st

badjoras said:
You should install a stock recovery that matches the software you had before trying to update.
As to the RUU, you can flash an OTA if you were trying to update to 4.2.2, I think. I used this one 1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
Have you tried it?
Click to expand...
Click to collapse
Where do i find the stock recovery for the software?
Im sorry i have no idea about it
Can u please guide me?
Thanks

alray said:
sorry to reply late, I was very busy at work.
Post the output of ''fastboot getvar all'' minus imei and s/n, so i can confirm you have the right RUU for your phone. Also, according to nkk71' table here, if S-ON, you can only use ruu with locked/relocked bootloader (if ruu is the same or higher version). So you probably need to re-lock bootloader.
post the getvar 1st
Click to expand...
Click to collapse
C:\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed by me
(bootloader) imei: removed by me
(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: 3778mV
(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
I have no idea why it fails at the end.
Also I have read that if I lock or relock the bootloader and i am not on stock recovery i will brick the device. So do i need to install stock recovery before locking the device?
If so, where do i find the stock recovery of this firmware? Can i pull it from the RUU.zip?
Also, the phone is not entering recovery..it enters for like a second and then goes back to rom..I tried so many different versions of twrp and cwm..it doesnt work
Revone is also not working...it gives me Failed to map memory 15 times then error 2
Also, how do i relock the bootloader! I am s-on! I believe u need s-off to lock the bootloader
I guess the phone is pretty ****ed up
Thanks

anibjoshi said:
Where do i find the stock recovery for the software?
Im sorry i have no idea about it
Can u please guide me?
Thanks
Click to expand...
Click to collapse
RUU should install the stock recovery on your device =)

badjoras said:
RUU should install the stock recovery on your device =)
Click to expand...
Click to collapse
The ruu doesnt get installed as i have s on and unlocked bootloader...and i cant lock bootloader with a custom recovery
is there a way to pull stock recovery from ruu.zip?
Also how do i relock the bootloader with s on?
Revone doesnt work...it says failed to map memory and gives error code 2
What do i do now
Thanks

anibjoshi said:
The ruu doesnt get installed as i have s on and unlocked bootloader...and i cant lock bootloader with a custom recovery
is there a way to pull stock recovery from ruu.zip?
Also how do i relock the bootloader with s on?
Revone doesnt work...it says failed to map memory and gives error code 2
What do i do now
Thanks
Click to expand...
Click to collapse
using fastboot, type this cmd: fastboot oem lock this will relock the bootloader

clsA said:
using fastboot, type this cmd: fastboot oem lock this will relock the bootloader
Click to expand...
Click to collapse
I have custom recovery installed...will that be a problem? Will i have to install stock recovery before locking the bootloader?
Cuz i have read somewhere that u have to have stock recovery before u lock the bootloader or it bricks the device
Is it true?
Thanks

anibjoshi said:
I have custom recovery installed...will that be a problem? Will i have to install stock recovery before locking the bootloader?
Cuz i have read somewhere that u have to have stock recovery before u lock the bootloader or it bricks the device
Is it true?
Thanks
Click to expand...
Click to collapse
no you have to have stock hboot not stock recovery
Your s-on so you have stock hboot

clsA said:
no you have to have stock hboot not stock recovery
Your s-on so you have stock hboot
Click to expand...
Click to collapse
C:\HTCOneRoot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Unknown error))
finished. total time: 1.484s
I got this message

clsA said:
no you have to have stock hboot not stock recovery
Your s-on so you have stock hboot
Click to expand...
Click to collapse
Hey but the bootloader shows relocked! Does it mean its okay or is there some problem?
Thanks

anibjoshi said:
C:\HTCOneRoot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Unknown error))
finished. total time: 1.484s
I got this message
Click to expand...
Click to collapse
you are relocked in the bootloader ...run the RUU

clsA said:
are you relocked in the bootloader ?
Click to expand...
Click to collapse
Yes it shows relocked in the bootloader.
What was the failed message at the end?

anibjoshi said:
Yes it shows relocked in the bootloader.
What was the failed message at the end?
Click to expand...
Click to collapse
it doesn't matter move on

clsA said:
it doesn't matter move on
Click to expand...
Click to collapse
While running the ruu...it stops at 7% and says waiting for bootloader
If i try to manually put it into bootloader it doesnt go...it boots into rom
and then i get a usb connection error
is it okay if i use adb commands while ruu is waiting for bootloader?
Or will that cause a problem
Thanks

[SOLVED] Flashed wrong ROM, neither ROM nor recovery are working

Hi everybody,
I've been flashing custom ROMs for years now, but now I screwed up -.-
I've got a One M7UL and accidentally flashed a Sprint ROM .. Now the only thing left working is fastboot.
If I try to boot into TWRP recovery (tried different versions already) the splashscreen will appear and crash back into bootloop. If I try to boot into clockwork recovery, it will boot but throw various errors 'E:Can't mount /cache/[..]' .. as soon as I try to do anything @ clockwork, it will crash back into bootloop.
I thought about flashing a RUU, but the bootloader is unlocked but still s-on. Modelid: PN0170000 Cidnum: VODAP102. I think the device has to be s-off to flash a RUU.exe, correct ? How about a RUU.zip ? oO Is there a way to get the device s-off without having ADB working ? How do I find a working RUU for this device, because I've read that I need a '1.xx.161.xx' for it's a Vodafon-brand and I won't find a damn usable RUU for it .. Is there a way to use a different RUU ?
help would be MUCH appreciated
thx & greets
hendi

Ok, got ADB working at the damaged clockword recovery .. but sideloading another ROM won't work and it seems like Revone S-OFF only works with a booted 4.2.2 ROM -.-
Any suggestions ?

Here's the output off '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.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxx
(bootloader) imei: xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4246mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.052s

If I could get my hands on another HTC ONE M7ul PN0710000/VODAP102 would I be able to build my own RUU ?
Help would be really appreciated ^^

Have you tried fastboot erase cache?
Sent from my GT-I9305 using xda app-developers app

nateboi81 said:
Have you tried fastboot erase cache?
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
yep, sadly without any success.. I also tried different versions of TWRP & clockwork recovery.
thx for the reply

doomhendi said:
If I could get my hands on another HTC ONE M7ul PN0710000/VODAP102 would I be able to build my own RUU ?
Help would be really appreciated ^^
Click to expand...
Click to collapse
it's been a while but i think the old developer edition RUU may work
this is the one for hboot 1.44
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/

clsA said:
it's been a while but i think the old developer edition RUU may work
this is the one for hboot 1.44
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
Click to expand...
Click to collapse
hey there
Don't I need a RUU with the version 1.xx.161.xxx because of the s-on + Vodafon-branding ? oO

doomhendi said:
hey there
Don't I need a RUU with the version 1.xx.161.xxx because of the s-on + Vodafon-branding ? oO
Click to expand...
Click to collapse
Yes .. but some of the developer RUU had a different android-info.txt that encompassed a bunch of different models .. I'm just not sure which ruu it was
Maybe @nkk71 could chime in

clsA said:
Yes .. but some of the developer RUU had a different android-info.txt that encompassed a bunch of different models .. I'm just not sure which ruu it was
Maybe @nkk71 could chime in
Click to expand...
Click to collapse
ah, cool that's good to know oO - I am already downloading

doomhendi said:
ah, cool that's good to know oO - I am already downloading
Click to expand...
Click to collapse
Sorry I was doing some more reading ..that RUU requires CID 11111111 and MID PN0712000, I'll keep looking

clsA said:
Yes .. but some of the developer RUU had a different android-info.txt that encompassed a bunch of different models .. I'm just not sure which ruu it was
Maybe @nkk71 could chime in
Click to expand...
Click to collapse
Sorry, didn't read, but if s-on, then don't start fashing things not for your phone... High chance you won't be able to unlock bootloader again!
If s-off, then ok.
Sent from my HTC One using Tapatalk

clsA said:
Sorry I was doing some more reading ..that RUU requires CID 11111111 and MID PN0712000, I'll keep looking
Click to expand...
Click to collapse
big thanks, pal

nkk71 said:
Sorry, didn't read, but if s-on, then don't start fashing things not for your phone... High chance you won't be able to unlock bootloader again!
If s-off, then ok.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
hey, yeah I am afraid it's still s-on .. but I didn't try to flash it so far.
How can I manually lock the bootloader again ? oO I've just tried method 1 from your guide (http://forum.xda-developers.com/showpost.php?p=47794190&postcount=3) but the bootloader still says it's unlocked oO
I haven't tried yet, but 'fastboot oem lock' should do the trick .. Now I just need a fitting RUU oO
Damn it, I'm kinda flashoholic since the good old Windows Mobile 6.51 Pro-times .. but I never took the wrong ROM xX
You guys really seem to know what you are doing .. the wrong ROM seems to have messed up at least the cache partition, may be there is another way than flashing a RUU, to fix this ? If I would be able to get clockwork recovery to install a working rom, it should reconstruct everything or at least give me the opportunity to s-off the device oO
I would be really grateful for some help
I just got an idea: Is it possible to tweak an developers RUU ? oO
Sorry for all the questions, I just really want to get that baby up an running again ^^

doomhendi said:
hey, yeah I am afraid it's still s-on .. but I didn't try to flash it so far.
How can I manually lock the bootloader again ? oO I've just tried method 1 from your guide (http://forum.xda-developers.com/showpost.php?p=47794190&postcount=3) but the bootloader still says it's unlocked oO
I haven't tried yet, but 'fastboot oem lock' should do the trick .. Now I just need a fitting RUU oO
Damn it, I'm kinda flashoholic since the good old Windows Mobile 6.51 Pro-times .. but I never took the wrong ROM xX
You guys really seem to know what you are doing .. the wrong ROM seems to have messed up at least the cache partition, may be there is another way than flashing a RUU, to fix this ? If I would be able to get clockwork recovery to install a working rom, it should reconstruct everything or at least give me the opportunity to s-off the device oO
I would be really grateful for some help
I just got an idea: Is it possible to tweak an developers RUU ? oO
Sorry for all the questions, I just really want to get that baby up an running again ^^
Click to expand...
Click to collapse
sure you can try
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7ul
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

clsA said:
sure you can try
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7ul
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
sorry, may be you misunderstood me: The bootloader is open & s-on. I've tried to flash different versions of TWRP & Clockwork Recovery via fastboot, including erase cache.. TWRP won't even start and Clockwork will start but throw multiple 'Can't Mount / Open /cache/[...]' errors and crash as soon as I try to do anything

doomhendi said:
sorry, may be you misunderstood me: The bootloader is open & s-on. I've tried to flash different versions of TWRP & Clockwork Recovery via fastboot, including erase cache.. TWRP won't even start and Clockwork will start but throw multiple 'Can't Mount / Open /cache/[...]' errors and crash as soon as I try to do anything
Click to expand...
Click to collapse
try and flash the stock recovery and do a factory reset
then try and flash TWRP again
Stock recovery's are here >> http://d-h.st/users/guich/?fld_id=29380#files

clsA said:
try and flash the stock recovery and do a factory reset
then try and flash TWRP again
Stock recovery's are here >> http://d-h.st/users/guich/?fld_id=29380#files
Click to expand...
Click to collapse
damn, sorry I've spent the whole day and night, reading how to possibly fix this and already tried to flash stock recovery .. The recovery won't start at all. It doesn't matter if I try to start via 'Factory Reset' or 'Recovery'.
According to the errors clockwork recovery throws, I guess the partition table got (partly?) messed up oO
*edit* Of cause I've tried again, following the link you've just sent me - thx for the effort

doomhendi said:
damn, sorry I've spent the whole day and night, reading how to possibly fix this and already tried to flash stock recovery .. The recovery won't start at all. It doesn't matter if I try to start via 'Factory Reset' or 'Recovery'.
According to the errors clockwork recovery throws, I guess the partition table got (partly?) messed up oO
*edit* Of cause I've tried again, following the link you've just sent me - thx for the effort
Click to expand...
Click to collapse
do you know how to start stock recovery ?

clsA said:
do you know how to start stock recovery ?
Click to expand...
Click to collapse
After flash, erase cache & reboot-bootloader, I've tried 'Factory Reset' @ Hboot and the 'usual' way via the bootloader oO

[Q] Conversion to GPE led to eternal boot loop. Fix?

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?

My HTC One Dead Dead dead

Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done.. The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery tried push with adb a new system FAILED tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
And my question is there a way to that my HTC One to get back to life?
Sorry about the topic and sorry about my bad english but i miss my HTC One
Sent from my SM-N9005 using XDA Premium 4 mobile app

No one could help me?
Sent from my SM-N9005 using XDA Premium 4 mobile app

Laurentiu27 said:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done.. The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery tried push with adb a new system FAILED tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
And my question is there a way to that my HTC One to get back to life?
Sorry about the topic and sorry about my bad english but i miss my HTC One
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Please ensure you have a custom recovery (TWRP) and your bootloader is UNLOCKED if you are going to side load or push a custom rom onto your phone. If you are going to use the RUU route, then you need to have the bootloader LOCKED or RELOCKED. Here is a post that explains the steps to each method.

Laurentiu27 said:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
Click to expand...
Click to collapse
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done..
Click to expand...
Click to collapse
Locking the bootloader is only needed if you want to go back to stock using a RUU. I don't know if its what you have tried to do or any other method (guru reset rom, nandroid backup, stock odexed rom, Ruu.zip or ruu.exe?) The output of "fastboot getvar all" could help (dont post IMEI and SN) + what recovery and version # are you using?
The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery
Click to expand...
Click to collapse
bootloader can't wipe anything by itself. You probably did something wrong, can't tell you what at this point.
tried push with adb a new system
Click to expand...
Click to collapse
Which one? You need to be more precise i.e I tried to adb push X rom X version #.
FAILED
Click to expand...
Click to collapse
Again, be more precise. What was the error code/message? + post a screenshot of the cmd prompt when it fail
tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
Click to expand...
Click to collapse
Stop rushing things, or you'll probably make the situation worst. We will help you step by step if needed.
And my question is there a way to that my HTC One to get back to life?
Click to expand...
Click to collapse
Probably but:
what is your goal? you want to flash a custom rom or return back to stock rom?
Post the output of fastboot getvar all excluding imei and sn
what is your recovery + what is the version?
post a picture of the bootloader screen
when you speak about a rom/recovery always be specific what name and version

Soon as I get my HTC back from a friend ho want to try do it i will post everything thing that is needed with screenshots and errors
Sent from my SM-N9005 using XDA Premium 4 mobile app

ok got my htc one back still dead
im using twrp recovery latest one
now pls guide me step by step how to do it
i don't care if is a custom or stock just want my htc back to life

This is what i got on it in the white screen is Android revolution hd tring to bot(installed with otg cable and USB) the other 2 pictures are the the data from bootloader and the twrp recovery
Sent from my SM-N9005 using XDA Premium 4 mobile app

alray said:
Locking the bootloader is only needed if you want to go back to stock using a RUU. I don't know if its what you have tried to do or any other method (guru reset rom, nandroid backup, stock odexed rom, Ruu.zip or ruu.exe?) The output of "fastboot getvar all" could help (dont post IMEI and SN) + what recovery and version # are you using?
bootloader can't wipe anything by itself. You probably did something wrong, can't tell you what at this point.
Which one? You need to be more precise i.e I tried to adb push X rom X version #.
Again, be more precise. What was the error code/message? + post a screenshot of the cmd prompt when it fail
Stop rushing things, or you'll probably make the situation worst. We will help you step by step if needed.
Probably but:
what is your goal? you want to flash a custom rom or return back to stock rom?
Post the output of fastboot getvar all excluding imei and sn
what is your recovery + what is the version?
post a picture of the bootloader screen
when you speak about a rom/recovery always be specific what name and version
Click to expand...
Click to collapse
i atached up a few pictures about my phone you can read there what are they
i just want my phone back to life no matter if stock or custom
thank you

Laurentiu27 said:
ok got my htc one back still dead
im using twrp recovery latest one
now pls guide me step by step how to do it
i don't care if is a custom or stock just want my htc back to life
Click to expand...
Click to collapse
@alray asked for more info:
* Post the output of fastboot getvar all excluding imei and sn
* what is your recovery + what is the version?
* post a picture of the bootloader screen
* when you speak about a rom/recovery always be specific what name and version
and "latest" is not a version, you need to post a real version number and link to location/thread where you got your files from (both recovery and ROM)

this is the data from fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3750mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
im using twrp 2.7.1.1
custom rom android revolution hd 71.1

nkk71 said:
@alray asked for more info:
* Post the output of fastboot getvar all excluding imei and sn
* what is your recovery + what is the version?
* post a picture of the bootloader screen
* when you speak about a rom/recovery always be specific what name and version
and "latest" is not a version, you need to post a real version number and link to location/thread where you got your files from (both recovery and ROM)
Click to expand...
Click to collapse
this is the data from fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3750mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
im using twrp 2.7.1.1
custom rom android revolution hd 71.1
and tere is a few post earlier 3 pictures one about bootloader one about booting the rom and last is the twrp
this is the thread of the rom http://forum.xda-developers.com/showthread.php?t=2183023

Laurentiu27 said:
i atached up a few pictures about my phone you can read there what are they
i just want my phone back to life no matter if stock or custom
thank you
Click to expand...
Click to collapse
download twrp recovery 2.6.3.3 and save it to your adb/fastboot folder.
Make sure md5 match: 72067aefb69541d40e8420d7aa46408d
plug your phone to your computer and boot it in bootloader
open a command prompt from your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-booloader
now download this rom and save it to your adb/fastboot folder
Make sure md5 match:: CCC848CBF2B74C5FA33FD7E2269B0499
boot your phone in twrp recovery main menu
open a command prompt from your adb/fastboot folder
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait for the file to transfer, there is no progress bar, just wait until adb show the file transfer is completed (5-10 min)
then in twrp, select ''install'' browse the sdcard content and select "Android_Revolution_HD-One_71.1.zip"
and swipe to confirm flash. When asked to wipe your phone, select yes.
reboot phone to OS and see if it works or not.
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?

alray said:
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
Click to expand...
Click to collapse
many have said 2.7.1.1 works fine, i haven't tried and am quite happy with 2.6.3.3... the 2.7 series not only had problems with flashing and charging, but also nandroids, but not sure about 2.7.1.1
but from the 3rd screenshot of the OP, that doesn't look like an m7 ROM, the bootanimation is distorted indicated it's not for 1080x1920 display.
PS: he should also format data, system and cache within twrp 2.6.3.3

alray said:
download twrp recovery 2.6.3.3 and save it to your adb/fastboot folder.
Make sure md5 match: 72067aefb69541d40e8420d7aa46408d
plug your phone to your computer and boot it in bootloader
open a command prompt from your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-booloader
now download this rom and save it to your adb/fastboot folder
Make sure md5 match:: CCC848CBF2B74C5FA33FD7E2269B0499
this is what i get
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
boot your phone in twrp recovery main menu
open a command prompt from your adb/fastboot folder
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait for the file to transfer, there is no progress bar, just wait until adb show the file transfer is completed (5-10 min)
then in twrp, select ''install'' browse the sdcard content and select "Android_Revolution_HD-One_71.1.zip"
and swipe to confirm flash. When asked to wipe your phone, select yes.
reboot phone to OS and see if it works or not.
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
Click to expand...
Click to collapse
this is what i get
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
error:device not found
update:seems that now is pushing it
flashed now waiting to boot

nkk71 said:
many have said 2.7.1.1 works fine, i haven't tried and am quite happy with 2.6.3.3... the 2.7 series not only had problems with flashing and charging, but also nandroids, but not sure about 2.7.1.1
but from the 3rd screenshot of the OP, that doesn't look like an m7 ROM, the bootanimation is distorted indicated it's not for 1080x1920 display.
PS: he should also format data, system and cache within twrp 2.6.3.3
Click to expand...
Click to collapse
the image is when tries to boot but i can asure is 71.1 ARH i downloade it 4 times from their server
that is the image when it tries to boot i get that screen

Laurentiu27 said:
the image is when tries to boot but i can asure is 71.1 ARH i downloade it 4 times from their server
that is the image when it tries to boot i get that screen
Click to expand...
Click to collapse
check md5 and you'll know if its the right rom. must match the md5 value I posted above.
if it still dont work, do what nkk71 said above, format data cache and system. you'll have to push to rom again after formatting.
to format data, go in twrp, ''wipe'' ---> "Format data"
to format system and cache go in "wipe" --> advanced wipe --> select cache and system and swipe to wipe
then adb push the rom again and install it again.

From flash screenshots
Sent from my SM-N9005 using XDA Premium 4 mobile app

Laurentiu27 said:
From flash screenshots
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so does it boot or not?

alray said:
so does it boot or not?
Click to expand...
Click to collapse
thank you!!! Thank you!!! It worked!!!

Laurentiu27 said:
thank you!!! Thank you!!! It worked!!!
Click to expand...
Click to collapse
:highfive:

[Q] My HTC ONE bootloop after WTPR All-in-one kit HELP

hi.. help
I managed to unlock my htc soon after used the all-in-one program to install htc twpr installed custom android by twpr ... in time to reboot happens bootloop TWPR ... someone could help me do unroot anything to do android back ... lose the data is not the only problem I want to phone back to work even if it is up to scratch
Can i disable wtpr ? how?
when my htc is so.... bootloader Unlock ... S-OFF
..thanks

carlos Eduardo martins said:
hi.. help
I managed to unlock my htc soon after used the all-in-one program to install htc twpr installed custom android by twpr ... in time to reboot happens bootloop TWPR ... someone could help me do unroot anything to do android back ... lose the data is not the only problem I want to phone back to work even if it is up to scratch
Can i disable wtpr ? how?
when my htc is so.... bootloader Unlock ... S-OFF
..thanks
Click to expand...
Click to collapse
The All in one toolkits are all out of date .. you need to learn fastboot and adb for yourself if your going to mess with your phone
https://www.youtube.com/watch?v=z5ZyDsPfU1g
post your results for fastboot getvar all (minus your serial no. and IMEI)

thanks
thanks clsA
ok now learning to use adb fastboot
trying to find a RUU to unroot my htc because it did not work update the WTPR continues on the same version.
but does not appear the firmware version (bootloader) version-main: ?? I'm thinking that deleted the OS
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxx
(bootloader) imei: xxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4324mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse

carlos Eduardo martins said:
thanks clsA
ok now learning to use adb fastboot
trying to find a RUU to unroot my htc because it did not work update the WTPR continues on the same version.
but does not appear the firmware version (bootloader) version-main: ??
Click to expand...
Click to collapse
Download and flash TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Download this rom
https://www.androidfilehost.com/?fid=23501681358543706
and put it in your fastboot folder
now push it to your phone from the command prompt and the Phone in TWRP Main screen
adb push Guru_Reset_M7_5.11.401.10-TeHashX.zip /sdcard/
now flash the rom in TWRP / Install
If you want to receive updates in the future select stock recovery install.

almost
ok .. but gave error when locating the fastboot zip follows below ..
C:\OneDrivers_Fastboot\Fastboot>adb push Guru_Reset_M7_5.11.401.10-TeHashX.zip /
sdcard/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
the bootloop does WTPR 2.6.1 first version I installed using ALL-IN-ONE and when I use bootloader recovery enters WTPR 2.6.3.3

carlos Eduardo martins said:
ok .. but gave error when locating the fastboot zip follows below ..
the bootloop does WTPR 2.6.1 first version I installed using ALL-IN-ONE and when I use bootloader recovery enters WTPR 2.6.3.3
Click to expand...
Click to collapse
Fix your PC drivers
See post 2 / FAQ 2 http://forum.xda-developers.com/showthread.php?t=2541082

---------- Post added at 12:49 AM ---------- Previous post was at 12:43 AM ----------
[/COLOR]
clsA said:
Fix your PC drivers
See post 2 / FAQ 2 http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
I am having essentially the same problem. I am following your instructions and ran into the same issue as the original poster in that adb wont see my device. I went to the link you provided to fix the drivers but it wants S-OFF to begin diagnosis. I am S-ON on Hboot 1.56. Rumrunner wants me to be in a booted up ROM to install which I cannnot do. My devices is telling my it cant access /data and /data/media and so i've been unable to install any ROM.

hammerchucker said:
---------- Post added at 12:49 AM ---------- Previous post was at 12:43 AM ----------
[/COLOR]
I am having essentially the same problem. I am following your instructions and ran into the same issue as clsA in that adb wont see my device. I went to the link you provided to fix the drivers but it wants S-OFF to begin diagnosis. I am S-ON on Hboot 1.56. Rumrunner wants me to be in a booted up ROM to install which I cannnot do. My devices is telling my it cant access /data and /data/media and so i've been unable to install any ROM.
Click to expand...
Click to collapse
it has nothing to do with s-off page 2 - FAQ 2
http://forum.xda-developers.com/showthread.php?t=2541082
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>adb devices
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse

clsA said:
Download and flash TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Download this rom
https://www.androidfilehost.com/?fid=23501681358543706
and put it in your fastboot folder
now push it to your phone from the command prompt and the Phone in TWRP Main screen
adb push Guru_Reset_M7_5.11.401.10-TeHashX.zip /sdcard/
now flash the rom in TWRP / Install
If you want to receive updates in the future select stock recovery install.
Click to expand...
Click to collapse
Will this also work for Sprint? It says for stock rom AT&T.
---------- Post added at 01:59 AM ---------- Previous post was at 01:47 AM ----------
hammerchucker said:
Will this also work for Sprint? It says for stock rom AT&T.
Click to expand...
Click to collapse
Okay, I found the Guru website and the Sprint version.

hammerchucker said:
Will this also work for Sprint? It says for stock rom AT&T.
---------- Post added at 01:59 AM ---------- Previous post was at 01:47 AM ----------
Okay, I found the Guru website and the Sprint version.
Click to expand...
Click to collapse
Sprint also uses a different Recovery
http://techerrata.com/browse/twrp2/m7wls

clsA said:
Download and flash TWRP 2.6.3.3
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and put it in your fastboot folder
now push it to your phone from the command prompt and the Phone in TWRP Main screen
adb push Guru_Reset_M7_5.11.401.10-TeHashX.zip /sdcard/
now flash the rom in TWRP / Install
If you want to receive updates in the future select stock recovery install.
Click to expand...
Click to collapse
this hard all the time something happens that disturbs and now entered the recovery mode WTPR 2.6.3.3 as suggested to try to copy the room to sdcard this request password .. searched but have not found solution

carlos Eduardo martins said:
this hard all the time something happens that disturbs and now entered the recovery mode WTPR 2.6.3.3 as suggested to try to copy the room to sdcard this request password .. searched but have not found solution
Click to expand...
Click to collapse
what password ? was your file system encrypted ?
if so you need to go to Wipe / Format Data and type yes then reboot and push the rom to your phone

clsA said:
what password ? was your file system encrypted ?
if so you need to go to Wipe / Format Data and type yes then reboot and push the rom to your phone
Click to expand...
Click to collapse
yes ! I´ll try

resolved
clsA said:
what password ? was your file system encrypted ?
if so you need to go to Wipe / Format Data and type yes then reboot and push the rom to your phone
Click to expand...
Click to collapse
Great Man!!!!!!!!:victory:
thank you clsA for your attention ...
thank´s for solving my problem and give me knowledge ... and even provided me with latest version htc one and I was wanting to install.....
I hope q this post will help others who are as same problem ... not use htc all-in-one guys ..
can copy the room installed HTC sync ... and then using WTPR data - with fastboot command
so one more question clsA ... how can I update my htc one correctly after you take this step? ...
once again thank you

carlos Eduardo martins said:
Great Man!!!!!!!!:victory:
thank you clsA for your attention ...
thank´s for solving my problem and give me knowledge ... and even provided me with latest version htc one and I was wanting to install.....
I hope q this post will help others who are as same problem ... not use htc all-in-one guys ..
can copy the room installed HTC sync ... and then using WTPR data - with fastboot command
so one more question clsA ... how can I update my htc one correctly after you take this step? ...
once again thank you
Click to expand...
Click to collapse
If you want to update your phone to 6.x.401.x you just flash the firmware and Stock odexed rom
you can find both in the developer forums