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
Related
Hey guys Im trying to fix my HTC One. I was on a call last night and the battery died and now it will only boot to fastboot. Problem is my Windows 8 box is not working with ADB. ADB does not see the device, but fastboot works. I try booting to twrp recovery and it just reboots to the HTC logo.
Can anyone help me out? I dont mind completely blasting it, but I dont want to waste a $600 phone.
Also good to note guys
piftoffpenguin said:
Hey guys Im trying to fix my HTC One. I was on a call last night and the battery died and now it will only boot to fastboot. Problem is my Windows 8 box is not working with ADB. ADB does not see the device, but fastboot works. I try booting to twrp recovery and it just reboots to the HTC logo.
Can anyone help me out? I dont mind completely blasting it, but I dont want to waste a $600 phone.
Click to expand...
Click to collapse
By the way at fastboot usb screen I have
*****Tampered*****
*****Unlocked*****
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
piftoffpenguin said:
By the way at fastboot usb screen I have
*****Tampered*****
*****Unlocked*****
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
Click to expand...
Click to collapse
adb doesnt work in fastboot mode;
Just flash the custom recovery again
fastboot flash recovery recovery-file-here.img
Thanks for the reply
darksnoopy said:
adb doesnt work in fastboot mode;
Just flash the custom recovery again
fastboot flash recovery recovery-file-here.img
Click to expand...
Click to collapse
I have tried this several times. I even tried to flash clockwork and a few different versions of twrp, and clear the cache and when I go to recovery it shows the Teamwin splash screen and then it reboots.
It says it transferred successfully, but even when I flashed clockwork I still see the Teamwin splash when entering recovery mode.
Image attached of successful flash
darksnoopy said:
adb doesnt work in fastboot mode;
Just flash the custom recovery again
fastboot flash recovery recovery-file-here.img
Click to expand...
Click to collapse
I just tried to flash clockwork as seen in the picture as well. Same issue, when I hit recovery, Teamwin splash and then it begins another endless reboot. Thanks again for the reply.
piftoffpenguin said:
I just tried to flash clockwork as seen in the picture as well. Same issue, when I hit recovery, Teamwin splash and then it begins another endless reboot. Thanks again for the reply.
Click to expand...
Click to collapse
hm i dont know if i can help anymore... but some steps to do
fastboot erase cache
then write the recovery again
again fastboot erase cache
reboot your device and then try to boot into recovery
else
flash stock recovery and then try again to flash custom recovery...
Last choice is to restore with a RUU
P.S If you dont have any luck flashing openrecovery-twrp-2.6.3.3-m7.img then try with this version:
openrecovery-twrp-2.6.3.0-m7.img
EDIT: twrp25.img???? i dont think this recovery is meant for htc one..you are flashing wrong version of twrp.... flash with the recoveries i mentioned above
Its correct - actually TWRP 2.5.0.0 renamed
darksnoopy said:
hm i dont know if i can help anymore... but some steps to do
fastboot erase cache
then write the recovery again
again fastboot erase cache
reboot your device and then try to boot into recovery
else
flash stock recovery and then try again to flash custom recovery...
Last choice is to restore with a RUU
P.S If you dont have any luck flashing openrecovery-twrp-2.6.3.3-m7.img then try with this version:
openrecovery-twrp-2.6.3.0-m7.img
EDIT: twrp25.img???? i dont think this recovery is meant for htc one..you are flashing wrong version of twrp.... flash with the recoveries i mentioned above
Click to expand...
Click to collapse
That's just the filename that I renamed TWRP 2.5.0.0 to for a simpler command.
I found the problem but dont know how to fix it. My device is in Fastboot which means no ADB. Also without being able to boot I can't change that (at least I dont think I can.).
Anyhow the damned thing re-engaged S-ON and its blocking access to the NAND (even if its saying it wrote to it, it can't be because of S-ON).
How do I RUU?
HTC One M7 Tmobile.
Thanks for the info sir. Much appreciated.
piftoffpenguin said:
That's just the filename that I renamed TWRP 2.5.0.0 to for a simpler command.
I found the problem but dont know how to fix it. My device is in Fastboot which means no ADB. Also without being able to boot I can't change that (at least I dont think I can.).
Anyhow the damned thing re-engaged S-ON and its blocking access to the NAND (even if its saying it wrote to it, it can't be because of S-ON).
How do I RUU?
HTC One M7 Tmobile.
Thanks for the info sir. Much appreciated.
Click to expand...
Click to collapse
type
fastboot getvar all
post here without your imei and serial number
Getvar
darksnoopy said:
type
fastboot getvar all
post here without your imei and serial number
Click to expand...
Click to collapse
C:\Users\cwatson\Desktop\FASTBOOT>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.14.3250.15
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.27.531.7
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0713000
INFOcidnum: T-MOB010
INFObattery-status: good
INFObattery-voltage: 4330mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
This is the RUU for your phone ruu_m7_ul_jb_50_tmous_1-27-531-11_radio_4a-17-3250-20_10-40-1150-04_release_324846_signed-exe
you can find it at htc1guru but to use it you must relock your bootloader and i wouldnt advice it cause of this error
piftoffpenguin said:
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
Click to expand...
Click to collapse
I dont want to risk to brick your device so it would be better to post your problem at the Tmobile htc one forum at xda here
http://forum.xda-developers.com/htc-one-tmobile/help
Unlock can I relock
darksnoopy said:
This is the RUU for your phone ruu_m7_ul_jb_50_tmous_1-27-531-11_radio_4a-17-3250-20_10-40-1150-04_release_324846_signed-exe
you can find it at htc1guru but to use it you must relock your bootloader and i wouldnt advice it cause of this error
I dont want to risk to brick your device so it would be better to post your problem at the Tmobile htc one forum at xda here
http://forum.xda-developers.com/htc-one-tmobile/help
Click to expand...
Click to collapse
If I unlock my bootloader can I relock in without ADB access and S-on or will that be a one way street??
piftoffpenguin said:
If I unlock my bootloader can I relock in without ADB access and S-on or will that be a one way street??
Click to expand...
Click to collapse
bootloader unlocking happens in fastboot with fastboot flash unlocktoken unlock_code.bin so no you dont need adb
Are you locked or unlocked right now?
Unlocked
darksnoopy said:
bootloader unlocking happens in fastboot with fastboot flash unlocktoken unlock_code.bin so no you dont need adb
Are you locked or unlocked right now?
Click to expand...
Click to collapse
I'm unlocked and have my unlock_code.bin as well saved.
piftoffpenguin said:
I'm unlocked and have my unlock_code.bin as well saved.
Click to expand...
Click to collapse
if you want to lock it and try to run the RUU give the command fastboot oem lock but i would not advice it and i take no responibility since i dont have a tmobile phone. I recommend to post on tmobile forum for help
Tried RUU
darksnoopy said:
if you want to lock it and try to run the RUU give the command fastboot oem lock but i would not advice it and i take no responibility since i dont have a tmobile phone. I recommend to post on tmobile forum for help
Click to expand...
Click to collapse
I tried the RUU you recommended. It said RUU ERROR 171 USB Connection Error. I can send it fastboot commands manually and the RUU sees its Rom version and requests the upgrade and reboots, but it then bombs. It also would not let me relock giving the following error:
... INFOLock successfully...
INFOmipi display off
INFOmipi_dsi_cmds_tx_ext
INFOpm8921_vreg_disable function, vreg_id = 38
INFOpm8921_vreg_disable function, vreg_id = 1
INFOTZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
INFOUse PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.158s
Is this device finished or is there anything else I can do?
Trying this now
Reference:
http://forums.androidcentral.com/ht...k-bootloader-cant-get-into-recovery-help.html
"when you have all that done open a cmd prompt and with the phone in fastboot usb mode type these cmd's
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
with the last cmd, if it comes back with a error about flushing or something like that just type the cmd again "
Dunno but I am at my wits end and do not know if the EPROM is even good now:
May have it beat finally
Crossing my fingers.
NOTE** This did not work earlier today despite MANY attempts.
I downloaded clockwork recovery to my fastboot computer folder.
I renamed it to recovery.img.
I ran fastboot boot recovery.img and I got clockwork.
I found the Viper ROM I installed months ago.
It ran the install.
Now it rebooted and I got endless reboot again lol ****E! Curse you and your S-On HTC!!!!
piftoffpenguin said:
Crossing my fingers.
NOTE** This did not work earlier today despite MANY attempts.
I downloaded clockwork recovery to my fastboot computer folder.
I renamed it to recovery.img.
I ran fastboot boot recovery.img and I got clockwork.
I found the Viper ROM I installed months ago.
It ran the install.
Now it rebooted and I got endless reboot again lol ****E! Curse you and your S-On HTC!!!!
Click to expand...
Click to collapse
Simple, s-off your device.
Sent from my HTC One using Tapatalk
Restore factory settings and wipe cache and dalvik cache and flash the rom again
How
xcrazydx said:
Simple, s-off your device.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
How do I s-off the device when Adb commmands are not working and an RUU isnt even working?
Hi! I tried to convert my M7 to a GPE with OTAs, but this did not succeed. After that I tried to simply revert it back to stock, this also failed and I am now at a state where the phone boots up, as usual, to the homescreen, but turns off after 3 seconds only to repeat the process. I believe this to be a sort of boot loop.
I have tried pretty much everything I could think of. I tried using ADB, but found out that USB debugging is not on and I am not able to turn it on because of the boot loop.
I tried flashing the GPE.zip and stock GPE recovery in order to "start fresh", but this does not seem to have any effect.When flashing the GPE.zip I get the error: FAILED (remote:99 unknown fail). However, when flashed stock recovery it seems to succeed, but just as the CWM/ TWRP recovery, I am not able to access it, because it turns off and begins the boot loop.
I then tried flashing Cyanogenmod and CWM/ TWRP, but this did not do anything either. Tried to simply do a factory reset through the bootloader, nope.
My current state is S-ON, Bootloader Unlocked and the only way to interact with the phone is fastboot, because I can't access ADB in order to S-OFF...
So my first question is whether there is a way to S-OFF through fastboo? Since every thread and site I read requires ADB, which I cannot access.
If not.. What to do ?
Thanks in advance!
Sari95 said:
I tried using ADB, but found out that USB debugging is not on and I am not able to turn it on because of the boot loop.
Click to expand...
Click to collapse
ADB is only usable from a booted OS or from custom recovery. In bootloader mode, you can only use FASTBOOT.
I tried flashing the GPE.zip and stock GPE recovery in order to "start fresh" but this does not seem to have any effect.When flashing the GPE.zip I get the error: FAILED (remote:99 unknown fail).
Click to expand...
Click to collapse
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
However, when flashed stock recovery it seems to succeed, but just as the CWM/ TWRP recovery, I am not able to access it, because it turns off and begins the boot loop.
Click to expand...
Click to collapse
When you flash the recovery partition, also erase cache and reboot the bootloader before attempting to boot in recovery mode. Also make sure the recovery you are flashing is compatible with you variant (i.e M7_UL)
I then tried flashing Cyanogenmod and CWM/ TWRP, but this did not do anything either.
Click to expand...
Click to collapse
How? define "did not do anything either" any error message?
Tried to simply do a factory reset through the bootloader, nope.
Click to expand...
Click to collapse
factory reset only wipe /data of the rom currently installed on your phone, this will not magically revert all the mess you did
My current state is S-ON
Click to expand...
Click to collapse
You must be S-OFF to convert to GPE !!
Bootloader Unlocked and the only way to interact with the phone is fastboot because I can't access ADB in order to S-OFF...
Click to expand...
Click to collapse
you need a working rom to s-off. and again adb only works from recovery. Also from a booted OS with usb debugging ON
So my first question is whether there is a way to S-OFF through fastboo?
Click to expand...
Click to collapse
No
If not.. What to do ?
Click to expand...
Click to collapse
flash a sense based rom (doesnt require s-off)
achieve s-off
flash a gpe rom and do the full conversion (i.e with a GPE ruu)
never s-on and never relock your bootloader when converted to gpe or say goodbye to your phone
alray said:
ADB is only usable from a booted OS or from custom recovery. In bootloader mode, you can only use FASTBOOT.
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
When you flash the recovery partition, also erase cache and reboot the bootloader before attempting to boot in recovery mode. Also make sure the recovery you are flashing is compatible with you variant (i.e M7_UL)
How? define "did not do anything either" any error message?
factory reset only wipe /data of the rom currently installed on your phone, this will not magically revert all the mess you did
You must be S-OFF to convert to GPE !!
you need a working rom to s-off. and again adb only works from recovery. Also from a booted OS with usb debugging ON
No
flash a sense based rom (doesnt require s-off)
achieve s-off
flash a gpe rom and do the full conversion (i.e with a GPE ruu)
never s-on and never relock your bootloader when converted to gpe or say goodbye to your phone
Click to expand...
Click to collapse
Thanks for answering! I am now stuck at the first step :l I believe I've found the correct stock RUU for my device, HTC One M7 bought in Norway, but when I try to download it from htc1guru.com, it downloads a little bit and stops. I am not able to download the full .zip file in order to flash it. I have tested to see if it has anything to do with my internet connection to do, but it doesn't have anything to do with it.
I am now downloading Android Revolution for M7, hoping that it will work....
Do you know if this issue with htc1guru.com is common or not?
Btw, I think it is best if I explain to you the whole process:
1. I downloaded a google play Edition RUU.zip that I could flash to convert the device into GPE.
2. Unlocked and S-OFF'd the device, then I flashed the RUU.zip. After these steps, I had a GPE device. However, the RUU I downloaded was Kitkat 4.4, which I thought would automatically update to 4.4.3. This did not happen.
3. I read more and understood that my CID and modelid had to be changed to CID: GOOGL001 and modelid: PN0712000, and so I did. I did not take note of my original CID, of course, so I don't know what that was :/
4. After having changed those settings, I once again tried to update it with OTA, as one would do with a GPE device, without any luck.
5. Reading on, it became clear that the device had to have stock recovery, which I downloaded and flashed. Once again, no luck with the OTA update. After this point, I gave up the GPE dream and decided to return to stock.
6. Then I read a tutorial to return back to stock, which told me to lock the bootloader and S-ON in order to flash the stock rom. This is did, but the process failed and I was left with a device booting up to homescreen, turning off and on in this endless boot loop.
Hope this helps to clarify my situation
Sari95 said:
6. Then I read a tutorial to return back to stock, which told me to lock the bootloader and S-ON in order to flash the stock rom. This is did, but the process failed and I was left with a device booting up to homescreen, turning off and on in this endless boot loop.
Click to expand...
Click to collapse
Well, I don't know where this tutorial was from, but you don't have to s-on to flash a ruu., you don't even need to relock bootloader to flash a ruu when you have s-off. Never S-ON back unless you absolutely must (sending phone for repair under warranty).
post a fastboot getvar all
are you still able to unlock bootloader?
alray said:
Well, I don't know where this tutorial was from, but you don't have to s-on to flash a ruu., you don't even need to relock bootloader to flash a ruu when you have s-off. Never S-ON back unless you absolutely must (sending phone for repair under warranty).
post a fastboot getvar all
are you still able to unlock bootloader?
Click to expand...
Click to collapse
Yeah... stupid of me not to read several tutorials before trying to return to stock :l
My getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4086mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
I believe I am able to unlock bootloader, yes. A picture is attached, which shows my current bootloader.
Sari95 said:
no luck with the OTA update. After this point, I gave up the GPE dream and decided to return to stock.
Click to expand...
Click to collapse
with s-off, you can download and flash ota update manually.
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
Sari95 said:
Yeah... stupid of me not to read several tutorials before trying to return to stock :l
My getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4086mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
I believe I am able to unlock bootloader, yes. A picture is attached, which shows my current bootloader.
Click to expand...
Click to collapse
thats a good thing you can unlock the bootloader again! many GPE users a stuck with unlockable bootloader with hboot 1.55+.
was you able to flash arhd? Then s-off the phone again and run the ruu you want again (stock or gpe)
alray said:
with s-off, you can download and flash ota update manually.
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
thats a good thing you can unlock the bootloader again! many GPE users a stuck with unlockable bootloader with hboot 1.55+.
was you able to flash arhd? Then s-off the phone again and run the ruu you want again (stock or gpe)
Click to expand...
Click to collapse
If by ARHD you mean Android Revolution HD, then no, I am not able to flash it. I get the error : FAILED (24 parsing failure), then nothing happens.
I also tried flashing stock Rug, but since I've changed my CID to CWS__001, while my MID is P0712000, they are in conflict and the RUU doesn't work either. Tried editing the info - Android. The, but no luck there either
Sari95 said:
If by ARHD you mean Android Revolution HD, then no, I am not able to flash it. I get the error : FAILED (24 parsing failure), then nothing happens.
I also tried flashing stock Rug, but since I've changed my CID to CWS__001, while my MID is P0712000, they are in conflict and the RUU doesn't work either. Tried editing the info - Android. The, but no luck there either
Click to expand...
Click to collapse
please post a picture when you got the FAILED error when attempting to flash arhd
alray said:
please post a picture when you got the FAILED error when attempting to flash arhd
Click to expand...
Click to collapse
ok.. so I tried flashing it now, there's a different error.
Sari95 said:
ok.. so I tried flashing it now, there's a different error.
Click to expand...
Click to collapse
ok.... so you are trying to flash a rom from fastboot
with fastboot, you flash recovery, ruu, and firmware only.
roms are flashed from custom recovery... not with fastboot
maybe you should have answered the question above from post #2:
I tried flashing the GPE.zip and stock GPE recovery in order to "start fresh" but this does not seem to have any effect.When flashing the GPE.zip I get the error: FAILED (remote:99 unknown fail).
Click to expand...
Click to collapse
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
---------- Post added at 09:06 PM ---------- Previous post was at 09:04 PM ----------
push the rom to your sdcard and flash it using twrp 2.6.3.3
alray said:
ok.... so you are trying to flash a rom from fastboot
with fastboot, you flash recovery, ruu, and firmware only.
roms are flashed from custom recovery... not with fastboot
maybe you should have answered the question above from post #2:
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
---------- Post added at 09:06 PM ---------- Previous post was at 09:04 PM ----------
push the rom to your sdcard and flash it using twrp 2.6.3.3
Click to expand...
Click to collapse
Sorry about that. The only recovery I have been able to flash is this one from this thread http://forum.xda-developers.com/showthread.php?t=2739126 . All "normal" CWM/TWRP recoveries will not boot up.
I just flashed ARHD, but when the Aroma installer finishes and I reboot the system this happens:
1. Screen turns off, then on.
2. A Google logo appears, turns off
3. Google logo appears, boots into the recovery I mentioned above
Any idea what this means?
Sari95 said:
Sorry about that. The only recovery I have been able to flash is this one from this thread http://forum.xda-developers.com/showthread.php?t=2739126 . All "normal" CWM/TWRP recoveries will not boot up.
Click to expand...
Click to collapse
why? do you have the active cmd line overflow error?
alray said:
why? do you have the active cmd line overflow error?
Click to expand...
Click to collapse
I do not, no, but after trying the usual CWM/ TWRP, the only recovery that actually would boot up was this one.
Sari95 said:
I do not, no, but after trying the usual CWM/ TWRP, the only recovery that actually would boot up was this one.
Click to expand...
Click to collapse
well try to download twrp 2.6.3.3 again from here
check md5: 72067aefb69541d40e8420d7aa46408d
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot the recovery
alray said:
well try to download twrp 2.6.3.3 again from here
check md5: 72067aefb69541d40e8420d7aa46408d
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot the recovery
Click to expand...
Click to collapse
All right, so now I am able to boot into proper TWRP through the steps, even though I have done the exact ones before anyway, I flashed ARHD again, but still no luck, as it does the same.
"1. Screen turns off, then on.
2. A Google logo appears, turns off
3. Google logo appears, boots into the recovery I mentioned above"
Sari95 said:
All right, so now I am able to boot into proper TWRP through the steps, even though I have done the exact ones before anyway, I flashed ARHD again, but still no luck, as it does the same.
"1. Screen turns off, then on.
2. A Google logo appears, turns off
3. Google logo appears, boots into the recovery I mentioned above"
Click to expand...
Click to collapse
have you wiped when you have flashed arhd?
and have you checked md5 value of the rom before flashing it?
alray said:
have you wiped when you have flashed arhd?
Click to expand...
Click to collapse
Of course. these are the steps after booting into recovery:
1. Wipe
2. Advanced Wipe --> check every box
3. Swipe to wipe
4. Install --> flash ARHD through USB OTG
Sari95 said:
Of course. these are the steps after booting into recovery:
1. Wipe
2. Advanced Wipe --> check every box
3. Swipe to wipe
4. Install --> flash ARHD through USB OTG
Click to expand...
Click to collapse
what version of arhd?
alray said:
what version of arhd?
Click to expand...
Click to collapse
The latest I believe:
"Android_Revolution_HD-One_71.1"
Sari95 said:
The latest I believe:
"Android_Revolution_HD-One_71.1"
Click to expand...
Click to collapse
have you checked md5 just in case?
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done.. The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery tried push with adb a new system FAILED tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
And my question is there a way to that my HTC One to get back to life?
Sorry about the topic and sorry about my bad english but i miss my HTC One
Sent from my SM-N9005 using XDA Premium 4 mobile app
No one could help me?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Laurentiu27 said:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done.. The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery tried push with adb a new system FAILED tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
And my question is there a way to that my HTC One to get back to life?
Sorry about the topic and sorry about my bad english but i miss my HTC One
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Please ensure you have a custom recovery (TWRP) and your bootloader is UNLOCKED if you are going to side load or push a custom rom onto your phone. If you are going to use the RUU route, then you need to have the bootloader LOCKED or RELOCKED. Here is a post that explains the steps to each method.
Laurentiu27 said:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
Click to expand...
Click to collapse
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done..
Click to expand...
Click to collapse
Locking the bootloader is only needed if you want to go back to stock using a RUU. I don't know if its what you have tried to do or any other method (guru reset rom, nandroid backup, stock odexed rom, Ruu.zip or ruu.exe?) The output of "fastboot getvar all" could help (dont post IMEI and SN) + what recovery and version # are you using?
The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery
Click to expand...
Click to collapse
bootloader can't wipe anything by itself. You probably did something wrong, can't tell you what at this point.
tried push with adb a new system
Click to expand...
Click to collapse
Which one? You need to be more precise i.e I tried to adb push X rom X version #.
FAILED
Click to expand...
Click to collapse
Again, be more precise. What was the error code/message? + post a screenshot of the cmd prompt when it fail
tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
Click to expand...
Click to collapse
Stop rushing things, or you'll probably make the situation worst. We will help you step by step if needed.
And my question is there a way to that my HTC One to get back to life?
Click to expand...
Click to collapse
Probably but:
what is your goal? you want to flash a custom rom or return back to stock rom?
Post the output of fastboot getvar all excluding imei and sn
what is your recovery + what is the version?
post a picture of the bootloader screen
when you speak about a rom/recovery always be specific what name and version
Soon as I get my HTC back from a friend ho want to try do it i will post everything thing that is needed with screenshots and errors
Sent from my SM-N9005 using XDA Premium 4 mobile app
ok got my htc one back still dead
im using twrp recovery latest one
now pls guide me step by step how to do it
i don't care if is a custom or stock just want my htc back to life
This is what i got on it in the white screen is Android revolution hd tring to bot(installed with otg cable and USB) the other 2 pictures are the the data from bootloader and the twrp recovery
Sent from my SM-N9005 using XDA Premium 4 mobile app
alray said:
Locking the bootloader is only needed if you want to go back to stock using a RUU. I don't know if its what you have tried to do or any other method (guru reset rom, nandroid backup, stock odexed rom, Ruu.zip or ruu.exe?) The output of "fastboot getvar all" could help (dont post IMEI and SN) + what recovery and version # are you using?
bootloader can't wipe anything by itself. You probably did something wrong, can't tell you what at this point.
Which one? You need to be more precise i.e I tried to adb push X rom X version #.
Again, be more precise. What was the error code/message? + post a screenshot of the cmd prompt when it fail
Stop rushing things, or you'll probably make the situation worst. We will help you step by step if needed.
Probably but:
what is your goal? you want to flash a custom rom or return back to stock rom?
Post the output of fastboot getvar all excluding imei and sn
what is your recovery + what is the version?
post a picture of the bootloader screen
when you speak about a rom/recovery always be specific what name and version
Click to expand...
Click to collapse
i atached up a few pictures about my phone you can read there what are they
i just want my phone back to life no matter if stock or custom
thank you
Laurentiu27 said:
ok got my htc one back still dead
im using twrp recovery latest one
now pls guide me step by step how to do it
i don't care if is a custom or stock just want my htc back to life
Click to expand...
Click to collapse
@alray asked for more info:
* Post the output of fastboot getvar all excluding imei and sn
* what is your recovery + what is the version?
* post a picture of the bootloader screen
* when you speak about a rom/recovery always be specific what name and version
and "latest" is not a version, you need to post a real version number and link to location/thread where you got your files from (both recovery and ROM)
this is the data from fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3750mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
im using twrp 2.7.1.1
custom rom android revolution hd 71.1
nkk71 said:
@alray asked for more info:
* Post the output of fastboot getvar all excluding imei and sn
* what is your recovery + what is the version?
* post a picture of the bootloader screen
* when you speak about a rom/recovery always be specific what name and version
and "latest" is not a version, you need to post a real version number and link to location/thread where you got your files from (both recovery and ROM)
Click to expand...
Click to collapse
this is the data from fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3750mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
im using twrp 2.7.1.1
custom rom android revolution hd 71.1
and tere is a few post earlier 3 pictures one about bootloader one about booting the rom and last is the twrp
this is the thread of the rom http://forum.xda-developers.com/showthread.php?t=2183023
Laurentiu27 said:
i atached up a few pictures about my phone you can read there what are they
i just want my phone back to life no matter if stock or custom
thank you
Click to expand...
Click to collapse
download twrp recovery 2.6.3.3 and save it to your adb/fastboot folder.
Make sure md5 match: 72067aefb69541d40e8420d7aa46408d
plug your phone to your computer and boot it in bootloader
open a command prompt from your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-booloader
now download this rom and save it to your adb/fastboot folder
Make sure md5 match:: CCC848CBF2B74C5FA33FD7E2269B0499
boot your phone in twrp recovery main menu
open a command prompt from your adb/fastboot folder
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait for the file to transfer, there is no progress bar, just wait until adb show the file transfer is completed (5-10 min)
then in twrp, select ''install'' browse the sdcard content and select "Android_Revolution_HD-One_71.1.zip"
and swipe to confirm flash. When asked to wipe your phone, select yes.
reboot phone to OS and see if it works or not.
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
alray said:
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
Click to expand...
Click to collapse
many have said 2.7.1.1 works fine, i haven't tried and am quite happy with 2.6.3.3... the 2.7 series not only had problems with flashing and charging, but also nandroids, but not sure about 2.7.1.1
but from the 3rd screenshot of the OP, that doesn't look like an m7 ROM, the bootanimation is distorted indicated it's not for 1080x1920 display.
PS: he should also format data, system and cache within twrp 2.6.3.3
alray said:
download twrp recovery 2.6.3.3 and save it to your adb/fastboot folder.
Make sure md5 match: 72067aefb69541d40e8420d7aa46408d
plug your phone to your computer and boot it in bootloader
open a command prompt from your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-booloader
now download this rom and save it to your adb/fastboot folder
Make sure md5 match:: CCC848CBF2B74C5FA33FD7E2269B0499
this is what i get
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
boot your phone in twrp recovery main menu
open a command prompt from your adb/fastboot folder
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait for the file to transfer, there is no progress bar, just wait until adb show the file transfer is completed (5-10 min)
then in twrp, select ''install'' browse the sdcard content and select "Android_Revolution_HD-One_71.1.zip"
and swipe to confirm flash. When asked to wipe your phone, select yes.
reboot phone to OS and see if it works or not.
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
Click to expand...
Click to collapse
this is what i get
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
error:device not found
update:seems that now is pushing it
flashed now waiting to boot
nkk71 said:
many have said 2.7.1.1 works fine, i haven't tried and am quite happy with 2.6.3.3... the 2.7 series not only had problems with flashing and charging, but also nandroids, but not sure about 2.7.1.1
but from the 3rd screenshot of the OP, that doesn't look like an m7 ROM, the bootanimation is distorted indicated it's not for 1080x1920 display.
PS: he should also format data, system and cache within twrp 2.6.3.3
Click to expand...
Click to collapse
the image is when tries to boot but i can asure is 71.1 ARH i downloade it 4 times from their server
that is the image when it tries to boot i get that screen
Laurentiu27 said:
the image is when tries to boot but i can asure is 71.1 ARH i downloade it 4 times from their server
that is the image when it tries to boot i get that screen
Click to expand...
Click to collapse
check md5 and you'll know if its the right rom. must match the md5 value I posted above.
if it still dont work, do what nkk71 said above, format data cache and system. you'll have to push to rom again after formatting.
to format data, go in twrp, ''wipe'' ---> "Format data"
to format system and cache go in "wipe" --> advanced wipe --> select cache and system and swipe to wipe
then adb push the rom again and install it again.
From flash screenshots
Sent from my SM-N9005 using XDA Premium 4 mobile app
Laurentiu27 said:
From flash screenshots
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so does it boot or not?
alray said:
so does it boot or not?
Click to expand...
Click to collapse
thank you!!! Thank you!!! It worked!!!
Laurentiu27 said:
thank you!!! Thank you!!! It worked!!!
Click to expand...
Click to collapse
:highfive:
Hello,
Ill get right to the point. I need a working RUU, I've tried so many that I'm going to lose my mind!
Each time I get a 130 or 131 error and regularely a 155 error. I can go into recovery but side-load etc. don't work. I don't know why so don't ask me.
A little info about the phone:
bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.111.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4292mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help.
39 vieuws and nobody has even left a reply ._.
1gangstabob2 said:
Hello,
Ill get right to the point. I need a working RUU, I've tried so many that I'm going to lose my mind!
Each time I get a 130 or 131 error
Click to expand...
Click to collapse
Error 130 = wrong MID thats mean the ruu you are using isn't for your phone.
Error 131 = Wrong CID thats also mean the ruu isn't the right one for your phone
and regularely a 155 error.
Click to expand...
Click to collapse
error 155 = wrong image ruu, mean that you are not using the correct ruu for your phone
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.63.111.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
Click to expand...
Click to collapse
There is no RUU you can use on that phone with S-ON. What you can do is to s-off and then flash another version RUU, return back to stock using a nandroid backup or simply flash a custom rom.
---------- Post added at 09:37 AM ---------- Previous post was at 09:36 AM ----------
1gangstabob2 said:
39 vieuws and nobody has even left a reply ._.
Click to expand...
Click to collapse
Do you prefer 39 persons posting random things to confuse you more? If someone visit this thread, it doesn't mean he know the answer...
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
btw what happened to your phone?
alray said:
Error 130 = wrong MID thats mean the ruu you are using isn't for your phone.
Error 131 = Wrong CID thats also mean the ruu isn't the right one for your phone
error 155 = wrong image ruu, mean that you are not using the correct ruu for your phone
There is no RUU you can use on that phone with S-ON. What you can do is to s-off and then flash another version RUU, return back to stock using a nandroid backup or simply flash a custom rom.
---------- Post added at 09:37 AM ---------- Previous post was at 09:36 AM ----------
Do you prefer 39 persons posting random things to confuse you more? If someone visit this thread, it doesn't mean he know the answer...
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
btw what happened to your phone?
Click to expand...
Click to collapse
I tried Android Revolution HD 82 ROM but it went in a bootloop. Now it doesn't boot anymore and I can only get to recovery and Hboot menu. Sideload doesn't work anymore and I don't know what to do anymore..... Also S-off wasn't possible because I had 1.55 or something like that. I don't know what to do....
1gangstabob2 said:
I tried Android Revolution HD 82 ROM but it went in a bootloop. Now it doesn't boot anymore and I can only get to recovery and Hboot menu. Sideload doesn't work anymore and I don't know what to do anymore..... Also S-off wasn't possible because I had 1.55 or something like that. I don't know what to do....
Click to expand...
Click to collapse
What recovery (name and version) are you using?
S-OFF can be achieved on hboot 1.55 but you'll first need a working rom.
alray said:
What recovery (name and version) are you using?
S-OFF can be achieved on hboot 1.55 but you'll first need a working rom.
Click to expand...
Click to collapse
I did give it a try sometime with Revone but it gave a weird error, also I was using TWRP but now clockworkmod, even if I flash TWRP bakc again it wont work... and when I try to go in recovery it says it cant mount data¿
EDIT: I just tried to go in recovery and it didnt gave any "cant mount" errors¿?¿
1gangstabob2 said:
I did give it a try sometime with Revone but it gave a weird error, also I was using TWRP but now clockworkmod, even if I flash TWRP bakc again it wont work... and when I try to go in recovery it says it cant mount data¿
Click to expand...
Click to collapse
I asked a simple answer: what recovery (name and version are you using)
example of answer: I have used CWM 6.?.?.? or TWRP 2.?.?.? to flash the rom.
---------- Post added at 03:08 PM ---------- Previous post was at 03:08 PM ----------
1gangstabob2 said:
I did give it a try sometime with Revone but it gave a weird error, also I was using TWRP but now clockworkmod, even if I flash TWRP bakc again it wont work... and when I try to go in recovery it says it cant mount data¿
EDIT: I just tried to go in recovery and it didnt gave any "cant mount" errors¿?¿
Click to expand...
Click to collapse
revone can only be used on hboot 1.44. for higher hboot version use others exploits.
alray said:
I asked a simple answer: what recovery (name and version are you using)
example of answer: I have used CWM 6.?.?.? or TWRP 2.?.?.? to flash the rom.
---------- Post added at 03:08 PM ---------- Previous post was at 03:08 PM ----------
revone can only be used on hboot 1.44. for higher hboot version use others exploits.
Click to expand...
Click to collapse
Clockworkmod Recovery 6.0.4.3
1gangstabob2 said:
Clockworkmod Recovery 6.0.4.3
Click to expand...
Click to collapse
arhd must be flashed using twrp 2.6.3.3. I would suggest you to flash that recovery version and try again to flash arhd:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
then boot in recovery and try to flash arhd again
report back after you have tried this.
alray said:
arhd must be flashed using twrp 2.6.3.3. I would suggest you to flash that recovery version and try again to flash arhd:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
then boot in recovery and try to flash arhd again
report back after you have tried this.
Click to expand...
Click to collapse
But I don't have the file on my SD card anymore...How do I install it then?
1gangstabob2 said:
But I don't have the file on my SD card anymore...How do I install it then?
Click to expand...
Click to collapse
use adb push to copy to rom from your computer to the phone storage.
Code:
adb push name_of_rom.zip /sdcard
the rom must be in the same folder where you have adb and fastboot
phone must be booted in twrp main menu.
alray said:
use adb push to copy to rom from your computer to the phone storage.
Code:
adb push name_of_rom.zip /sdcard
the rom must be in the same folder where you have adb and fastboot
phone must be booted in twrp main menu.
Click to expand...
Click to collapse
I've already got it working, I flashed the TWRP and it sensed that some files were damaged and offered to recover them, so I let it recover them and enabled MTP via TWRP and litteraly the first thing I did was take a back-up. Now im on Maximus HD. Thanks anyway m8.
EDIT: Already got a bootloop from Maximu HD... What am I doing wrong? @alray
1gangstabob2 said:
I've already got it working, I flashed the TWRP and it sensed that some files were damaged and offered to recover them, so I let it recover them and enabled MTP via TWRP and litteraly the first thing I did was take a back-up. Now im on Maximus HD. Thanks anyway m8.
EDIT: Already got a bootloop from Maximu HD... What am I doing wrong? @alray
Click to expand...
Click to collapse
the rom is bootlooping after you have flashed it?
Have you cheked your md5 on both the rom and the recovery to make sure its not a bad download?
alray said:
the rom is bootlooping after you have flashed it?
Have you cheked your md5 on both the rom and the recovery to make sure its not a bad download?
Click to expand...
Click to collapse
They don't match...Does this mean I can't use this ROM?
1gangstabob2 said:
They dont match...Does this mean I cant use this ROM?
Click to expand...
Click to collapse
If the rom MD5 doesnt match the value from where you have downloaded the file, its a bad download. Download again
alray said:
If the rom MD5 doesnt match the value from where you have downloaded the file, its a bad download. Download again
Click to expand...
Click to collapse
This time it did match and now it isn't booting at all...Also said set_metadata_recursive some changes failed. What does it mean by that?
1gangstabob2 said:
This time it did match and now it isnt booting at all...Also said set_metadata_recursive some changes failed. What does it mean by that?
Click to expand...
Click to collapse
Are you using twrp 2.6.3.3 or another version?
similar problem
alray said:
Are you using twrp 2.6.3.3 or another version?
Click to expand...
Click to collapse
HI , i have similar but terrible problem in flashing custom ROM in HTC one M7 .
after unlocked the bootloader and install TWRP recovery , the phone works fine . However , when i was trying to flash ARHD ROM , after the successful installation and reboot system , i was directed back to the recovery again. I was suggested to change the recovery through the method from youtube video. and i was able to flash the ROM through CWM. However , when i was reboot the system , i was directed to the TWRP that doesn't work properly with flashing on the screen. I was trying to install the stock ROM back but error happened and installation was aborted. NO matter what recovery i used , no matter how i format the data , i'm still directed to TWRP that work / doesn't work properly . Any expert opinion are very very appreciated. Thank you .
the root access also missing as well. im using the latest TWRP and CWM.
yusiongng said:
HI , i have similar but terrible problem in flashing custom ROM in HTC one M7 .
after unlocked the bootloader and install TWRP recovery , the phone works fine . However , when i was trying to flash ARHD ROM , after the successful installation and reboot system , i was directed back to the recovery again. I was suggested to change the recovery through the method from youtube video. and i was able to flash the ROM through CWM. However , when i was reboot the system , i was directed to the TWRP that doesn't work properly with flashing on the screen. I was trying to install the stock ROM back but error happened and installation was aborted. NO matter what recovery i used , no matter how i format the data , i'm still directed to TWRP that work / doesn't work properly . Any expert opinion are very very appreciated. Thank you .
the root access also missing as well. im using the latest TWRP and CWM.
Click to expand...
Click to collapse
oh c'mon guys, this has been mentioned thousands and thousands of times, and it's even mentioned in the FAQ sticky!!
if you get set_metadata errors, you need to use TWRP 2.6.3.3 or 2.8.0.0 or 2.8.0.1 (if you have m7_u or m7_ul, not the other versions!!
alray said:
Are you using twrp 2.6.3.3 or another version?
Click to expand...
Click to collapse
2.8.1.0.
.
yusiongng said:
HI , i have similar but terrible problem in flashing custom ROM in HTC one M7 .
after unlocked the bootloader and install TWRP recovery , the phone works fine . However , when i was trying to flash ARHD ROM , after the successful installation and reboot system , i was directed back to the recovery again. I was suggested to change the recovery through the method from youtube video. and i was able to flash the ROM through CWM. However , when i was reboot the system , i was directed to the TWRP that doesn't work properly with flashing on the screen. I was trying to install the stock ROM back but error happened and installation was aborted. NO matter what recovery i used , no matter how i format the data , i'm still directed to TWRP that work / doesn't work properly . Any expert opinion are very very appreciated. Thank you .
the root access also missing as well. im using the latest TWRP and CWM.
Click to expand...
Click to collapse
Go to recovery and wipe everything. If you can't go into recovery then do a factory reset via the HBoot and if you have done the wiping flash a new recovery (I use the toolkit HTC one toolkit) and if you have succeeded go into recovery and the new recovery will fix the errors for you.
nkk71 said:
oh c'mon guys, this has been mentioned thousands and thousands of times, and it's even mentioned in the FAQ sticky!!
if you get set_metadata errors, you need to use TWRP 2.6.3.3 or 2.8.0.0 or 2.8.0.1 (if you have m7_u or m7_ul, not the other versions!!
Click to expand...
Click to collapse
I litterally never have seen this. But thanks anyway.
UPDATE: I somehow got the MaxHD working...I suspect it has to do with the separate boot.img file which I have flashed via Fastboot.
Thanks for all the help and may this thread help alot of others.
Hi,
I've kind of soft bricked my phone. Good thing is still able to fastboot as my PC detects it via USB.
I am new to Android rooting, flashing etc.
I had android Lollipop before I messed up phone. I've downloaded Nandroid backup and RUU for Indian version of HTC One 802d from other threads on XDA.
I am not sure of process to use that Nandroid backup. I've CWM recovery but don't have root access. Bootloader iss unlocked.
For other thing i.e. RUU that I downloaded is a zip file. But for some strange reason I'm not able to extract it on windows 7. It says compressed zip folder is invalid. I also downloaded Chinese RUU which is again zip and doesn't extarct, gives same error.
I am new to all this though I've some knowledge about computers and gadgets.
Please help me on how to get back my phone working may by Nandroid or RUU or anything else.
Please let me know if any details or information is needed.
Greatly appreciate any help in this regard. Thank you!
Hi,
Can someone please help me with this? :crying:
First of all, you can't unzip RUU.zip because it's encrypted. And why are you trying to unzip it anyway? Other thing - your phone is most likely S-on, so, in order to flash RUU.zip, you need stock recovery and locked or relocked bootloader. My suggestion is to go and do some reading on how to flash RUU. There are loads of tutorials online. And make sure you understand everything before you go ahead with flashing
donkeykong1 said:
First of all, you can't unzip RUU.zip because it's encrypted. And why are you trying to unzip it anyway? Other thing - your phone is most likely S-on, so, in order to flash RUU.zip, you need stock recovery and locked or relocked bootloader. My suggestion is to go and do some reading on how to flash RUU. There are loads of tutorials online. And make sure you understand everything before you go ahead with flashing
Click to expand...
Click to collapse
Thanks a lot for your reply!
Okay I get a point about RUU.zip not opening. I was trying it at first place cause I saw it some video that he opens it and then runs a setup file in it which opens windows wizard which then guides step by step to flash RUU from GUI.
Yes, my phone is S-On and I've been doing quite a lot reading since past couple of days and understading things better with every reading.
Now, I need further help. I'll first briefly explain how I messed up my phone. I had android L with Sense 6 in my cellphone before I started playing with it and decided to root. After watching few tutorials I first unlocked Bootloader then flashed cwm recovery. After that I took a backup from cwm and then installed SuperSu.zip from cwm recovery and rebooted phone normally. It started but SuperSu installed earlier was stopping regularly throwing error messages. I also downloaded rootChecker app and it showed that I didn't have root access.
Here, I slightly panicked as this is first time I was playing around with it. I rebooted my phone, went to cwm recovery and tried restoring back up that I took earlier as said above. But I didn't have root access and since then my phone went in bootloop and not starting.
My PC detects it when I connect in fastboot USB and i am able to execute fastboot commands.
=======================================================================================
Now, I,ll explain steps I am following to get my phone working :
1) I downloaded few RUU zip latest being from here --> http://www.mediafire.com/download/k...1_09B_release_391798_signed+by+jamesjerss.zip
2) Downloaded stock recovery for KITKAT from other xda thread --> http://forum.xda-developers.com/showthread.php?t=2617159
3) flashed this stock recovery then relocked my phone. fastboot oem lock.
4) executed fastboot oem rebootRUU
5) executed fastboot flash zip ruu.zip with the ruu zip downloaded in step 1 above
but it fails with version check failed , some error like this don't remember exact wording of it. I can get you that if needed by trying one more time.
Also, I can provide other information like getvar all and hboot version etc if required but kindly help me get out of this. Really appreciate your help.
I just want to highlight one more thing that I visited HTC care centre yesterday and without looking much at device just by looking at bootloader and cwm recovery he said that OS is corrupt and I'll need to replace mother board which costs half the price of phone. I don't believe him. It is just soft bricked and am able to connect in fastboot USB.
Please guide me on how to proceed further ahead.
Thank you once again!
<<Just getting you the output after running flash zip>>
C:\Users\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>fastboo
t flash zip ruukkn.zip
target reported max download size of 1542111232 bytes
sending 'zip' (1344718 KB)...
OKAY [ 75.112s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 190.871s
Post a fastboot getvar all please. Don't forget to remove your IMEI and serial no. That guy at HTC care is an idiot ?
donkeykong1 said:
Post a fastboot getvar all please. Don't forget to remove your IMEI and serial no. That guy at HTC care is an idiot
Click to expand...
Click to collapse
Lol. He certainly seems to be one.
Below is result of getvar all -->
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: 2.04.30.0316
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.720.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: A1000037A674B4
(bootloader) product: m7cdwg
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0751000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4314mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d0e3b226
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
OK. The reason for "signature verify fail" error is because you're trying to flash older firmware than your current one. Find a matching or newer firmware, and flash away. Just don't unzip it ?
donkeykong1 said:
OK. The reason for "signature verify fail" error is because you're trying to flash older firmware than your current one. Find a matching or newer firmware, and flash away. Just don't unzip it
Click to expand...
Click to collapse
he he I won't do that definitely.
But earlier yesterday I had tried with Lollipop RUU downloaded from -->
androidfilehost.com/?fid=24052804347774374
but that too failed with similar signature verify fail.
What should I do?
<<<<<<<<<<<<<<Just to point out>>>>>>>>>>>>>>>>>>>>>>>>>>
Lollipop RUU that I downloaded is like PN07IMG_M7C_DWG_L50_SENSE60_MR_hTC_Asia_India_]7.17 .720.6_Radio_1237.29.35.0903 release_426120_signed.zip whereas from getvar results shared above it shows version like --> bootloader) version-main: 7.17.720.15
does it make a difference? if yes, that's the latest RUU I can find online.
How can I proceed in this scenario?
So, you can't flash a RUU, because there isn't one for your phone. Now, unlock your bootloader again, and flash TWRP recovery for your phone
donkeykong1 said:
So, you can't flash a RUU, because there isn't one for your phone. Now, unlock your bootloader again, and flash TWRP recovery for your phone
Click to expand...
Click to collapse
Okay but what after flashing TWRP recovery? How will it help?
yogeshchaudhari21 said:
Okay but what after flashing TWRP recovery? How will it help?
Click to expand...
Click to collapse
We'll find a TWRP nandroid backup and restore it [emoji6]
donkeykong1 said:
We'll find a TWRP nandroid backup and restore it [emoji6]
Click to expand...
Click to collapse
oh I see.
In that case I've CWM nandroid backup again downloaded from other XDA thread I shared earlier though it's for android 4.2.2
CWM Nandroid Backup (Android 4.2.2):
M7DWG_CWM_Nandroid_Backup_CID_HTC__038_2.37.720.1. zip - 998.74 MB
But as I'm doing all this for first time and am pretty much noob , I'm not sure how to use it to my benefit.
Can you please guide how can I use that nandroid back up to restore it in my phone?
Thank you!
yogeshchaudhari21 said:
oh I see.
In that case I've CWM nandroid backup again downloaded from other XDA thread I shared earlier though it's for android 4.2.2
CWM Nandroid Backup (Android 4.2.2):
M7DWG_CWM_Nandroid_Backup_CID_HTC__038_2.37.720.1. zip - 998.74 MB
But as I'm doing all this for first time and am pretty much noob [emoji14] , I'm not sure how to use it to my benefit.
Can you please guide how can I use that nandroid back up to restore it in my phone?
Thank you!
Click to expand...
Click to collapse
For that one you need CWM recovery. I'll be home in about 20 minutes and I'll walk you through the process
donkeykong1 said:
For that one you need CWM recovery. I'll be home in about 20 minutes and I'll walk you through the process
Click to expand...
Click to collapse
Oh sure! I'll be waiting.
I do have a cwm recovery although it's not touch version but that doesn't matter I guess.
Really appreciate your support. Thanks!
I'm back. did you flash the recovery yet?
donkeykong1 said:
I'm back. did you flash the recovery yet?
Click to expand...
Click to collapse
Hey hi!
Yes, I did.
yogeshchaudhari21 said:
Hey hi!
Yes, I did.
Click to expand...
Click to collapse
OK. Now enter your recovery and choose backup. Wait till it's done, so we can put your new backup in the same folder
donkeykong1 said:
OK. Now enter your recovery and choose backup. Wait till it's done, so we can put your new backup in the same folder
Click to expand...
Click to collapse
OMG something weird. Phone is not entering recovery after I flashed cwm recovery again. It's coming to bootloader but not going to recovery and just restarting. :| Let me keep trying.
yogeshchaudhari21 said:
OMG something weird. Phone is not entering recovery after I flashed cwm recovery again. It's coming to bootloader but not going to recovery and just restarting. :| Let me keep trying.
Click to expand...
Click to collapse
Did you unlock your bootloader again?
donkeykong1 said:
Did you unlock your bootloader again?
Click to expand...
Click to collapse
Yes I did unlock and then flashed recovery. I've been doing it quite a few times since yesterday so got used to it. This is something strange happening.