Ok guys, I think this is going to be a hard one, i'll try to explain as good as I can:
Core problem:
After replacing my broken display assembly (before, I was on PA beta 5, rooted, unlocked, supercid and s-off) the phone went into bootloop. I reopened the case and found i had accidentally switched the grey and blue antenna connectors on the motherboard. I don't know if that was what was causing the bootloops but it's the only thing i found wrong inside the case.
So far so good. But after fixing the cable error the bootloops persisted and i wasn't able to go to recovery (TWRP 2.8.xx).
Then followed a whole lot of tampering and trying to fix things (I know this was a very bad idea)
What I tried already after reading a whole lot of threads:
1. Return to s-on (what a complete brain fart, as with no working rom i cannot reverse this)
2. Factory reset via hboot
3. bootloader relocked then unlocked then relocked again to flash ruus
4. tried flashing ruu's via fastboot (zip) and via exe. No luck, the zip file flashing hangs at "(bootloader) checking signature" and after a while fails with an unknown error and the ruu exe flashing stops with "htc-fastboot has stopped working"
5. tried flashing recovery img via fastboot; result: all twrp recoveries from 2.7.xx on upwards won't boot (bootloop); 2.6.xx works but cannot flash cm11 or PA; it says "successful for cm10 but rebooting results in bootloop again)
6. tried flashing recovery zip via twrp 2.6.xx => same result as 5.
7. on twrp 2.6.xx i tried reformating cache, data and system partitions via mkfs.ext4. then retried 4. and 5. => same results
EDIT1: 8. rewritten version-main from 4.19.xxxxxx to 1.00.000.0 (via HTC One All-In-One Toolkit by Hasoon2000) in an desperate attempt to fix ruu flashing, no luck as well (i think that even broke more things )
EDIT2: now that i think of it, somewhere along the line flashing a ruu zip sort of worked, because it updated my hboot from 1.44 to 1.57. Which is making things even worse i think.
current state:
i can start in bootloader mode, and from there start recovery (still twrp 2.6.xx)
fastboot getvar all gives:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT357W*******
(bootloader) imei: 3544************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
If you need any additional info, i'd gladly supply.
anyone has an idea of what to try next? my last resort would be to send it in to a JTAG flashing service, but i'd rather not do that as it is expensive.
thx in advance,
uuzi
uuzi said:
Ok guys, I think this is going to be a hard one, i'll try to explain as good as I can:
Core problem:
After replacing my broken display assembly my phone (before brick, I was on PA beta 5, rooted, unlocked, supercid and s-off) the phone was in a bootloop. I reopened the case and found i had accidentally switched the grey and blue antenna connectors on the motherboard. I don't know if that was what was causing the bootloops but it's the only thing i found wrong inside the case.
So far so good. But after fixing the cable error the bootloops persisted and i wasn't able to go to recovery (TWRP 2.8.xx).
Then followed a whole lot of tampering and trying to fix things (I know this was a very bad idea)
What I tried already after reading a whole lot of threads:
1. Return to s-on (what a complete brain fart, as with no working rom i cannot reverse this)
2. Factory reset via hboot
3. bootloader relocked then unlocked then relocked again to flash ruus
4. tried flashing ruu's via fastboot (zip) and via exe. No luck, the zip file flashing hangs at "(bootloader) checking signature" and after a while fails with an unknown error and the ruu exe flashing stops with "htc-fastboot has stopped working"
5. tried flashing recovery img via fastboot; result: all twrp recoveries from 2.7.xx on upwards won't boot (bootloop); 2.6.xx works but cannot flash cm11 or PA; it says "successful for cm10 but rebooting results in bootloop again)
6. tried flashing recovery zip via twrp 2.6.xx => same result as 5.
7. on twrp 2.6.xx i tried reformating cache, data and system partitions via mkfs.ext4. then retried 4. and 5. => same results
current state:
i can start in bootloader mode, and from there start recovery (still twrp 2.6.xx)
fastboot getvar all gives:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT357W*******
(bootloader) imei: 354436054678733
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
If you need any additional info, i'd gladly supply.
anyone has an idea of what to try next? my last resort would be to send it in to a JTAG flashing service, but i'd rather not do that as it is expensive.
thx in advance,
uuzi
Click to expand...
Click to collapse
First of all and as I'm sure you've discovered going back to S-on is never a good fix for anything except warranty
(bootloader) version-main: 1.00.000.0 < ----- I noticed this in your getvar, that is not normal especially with hboot 1.57 I've never seen anything like that before. Don't know if this is a hardware issue. Flashing firmware may solve it but with s-on and super cid I'm not even sure thats possible or which firmware you can use with your version main that way. Going back to s-on may well have been the nail in the coffin here I'm afraid.
If your able to boot recovery you can push a rom to flash but you need to fix the firmware first as I fear that's the cause of your bootloop. Hopefully @nkk71 @clsA or @majmoz have somthing to add here :good:
oh yeah that's somethong i've forgot to add, i've manually written version-main: 1.00.000.0 in a desperate attempt to get the ruu to flash correctly. will edit my original post to include that.
uuzi said:
oh yeah that's somethong i've forgot to add, i've manually written version-main: 1.00.000.0 in a desperate attempt to get the ruu to flash correctly. will edit my original post to include that.
Click to expand...
Click to collapse
What was the original version main?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
What was the original version main?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
4.19.xxxxxx which was when it updated hboot to 1.57 i guess
sorry i edited some things in my OP
uuzi said:
EDIT2: now that i think of it, somewhere along the line flashing a ruu zip sort of worked, because it updated my hboot from 1.44 to 1.57. Which is making things even worse i think.
Click to expand...
Click to collapse
When you flashed the ruu did your run
Code:
fastboot flash zip "nameofruu".zip
Twice?
You have to flash the zip twice the first flash just updates hboot. Second flash installs the ruu.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
When you flashed the ruu did your run
Code:
fastboot flash zip "nameofruu".zip
Twice?
You have to flash the zip twice the first flash just updates hboot. Second flash installs the ruu.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
i'm not really sure right now, i'm trying again now
Danny201281 said:
(bootloader) version-main: 1.00.000.0 < ----- I noticed this in your getvar, that is not normal especially with hboot 1.57 I've never seen anything like that before.
Click to expand...
Click to collapse
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
uuzi said:
4.19.xxxxxx which was when it updated hboot to 1.57 i guess
sorry i edited some things in my OP
Click to expand...
Click to collapse
4.19 is hboot 1.56 (with the exception of some .70x. editions, but those have a different MID, unless I'm mistaken)
hboot 1.57 would imply a 5.xx or higher firmware
so the problems:
1- there is no ruu for 1.57 hboot (ie 5.xx or 6.xx)
2- you have SuperCID, so don't know if you can unlock using HTCdev anymore... try!!
3- you don't have a ROM on it to get S-OFF, which you desperately need
if you manage to get unlocked, flash TWRP, install a stock ROM, and Sunshine S-OFF
but anyway, with all you did, this could very well be a hardware problem now, no?
Result:
Code:
C:\unbrick>fastboot oem rebootRUU
(bootloader) Start Verify: 3
OKAY [ 0.030s]
finished. total time: 0.031s
C:\unbrick>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 32.802s]
writing 'zip'...
(bootloader) signature checking...
FAILED (status read failed (Unknown error))
finished. total time: 801.973s
nkk71 said:
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
4.19 is hboot 1.56 (with the exception of some .70x. editions, but those have a different MID, unless I'm mistaken)
hboot 1.57 would imply a 5.xx or higher firmware
so the problems:
1- there is no ruu for 1.57 hboot (ie 5.xx or 6.xx)
2- you have SuperCID, so don't know if you can unlock using HTCdev anymore... try!!
3- you don't have a ROM on it to get S-OFF, which you desperately need
if you manage to get unlocked, flash TWRP, install a stock ROM, and Sunshine S-OFF
but anyway, with all you did, this could very well be a hardware problem now, no?
Click to expand...
Click to collapse
it being a hardware problem is my biggest fear
i can unlock using htcdev, so that's one good thing, the remaining problem is now that i can't flash any twrp recovery later that anything 2.6.xxx. 2.7.xxx and 2.8.xxx result in bootlooping when trying to start recovery
nkk71 said:
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
Click to expand...
Click to collapse
Yeah I got that after he had said he'd changed it manually. Just caught me off guard thought it was something bigger. :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 05:01 PM ---------- Previous post was at 04:57 PM ----------
uuzi said:
it being a hardware problem is my biggest fear
i can unlock using htcdev, so that's one good thing, the remaining problem is now that i can't flash any twrp recovery later that anything 2.6.xxx. 2.7.xxx and 2.8.xxx result in bootlooping when trying to start recovery
Click to expand...
Click to collapse
What about TWRP 2.6.3.3 If it's still working maybe you can flash ARHD to get it booting maybe.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
OH MY F**** GOD!
TWRP 2.6.3.3 and ARHD 82.0 did the trick!
IT WORKED! i'm in ARHD right now! VERY VERY VERY much apprieciated!
YOU my man are my personal hero!
uuzi said:
OH MY F**** GOD!
TWRP 2.6.3.3 and ARHD 82.0 did the trick!
IT WORKED! i'm in ARHD right now! VERY VERY VERY much apprieciated!
YOU my man are my personal hero!
Click to expand...
Click to collapse
Glad to here your back up good job :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Related
Ok, so im new here to the htc forums but not the rooting community. I previously had all nexus devices and this is my first htc/one device. I dont understand what image version im on bc when i look under Settings>About>Software Info I see Software Version - 1.29.651.10. So Why is that i cant run this RUU without any problems? Im using this guide... http://forum.xda-developers.com/showthread.php?t=2250904
I Keep getting an error at the end. heres what i did
First i flashed this.... Sprint_HTC_One_1.29.651.10_Stock_Deodexed.zip
Second... fastboot oem lock (from bootloader screen)
Third... Ran the setup.exe from this this Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Fourth... i accepted the terms but my image version said 1.31.651.2. the image version didnt match when i ran the RUU.
at the end i get the error code 140. im posting some images so you guy can see.
in the bootloader screen i did: fastboot getvar all and got this
Last login: Tue Aug 13 21:11:14 on ttys000
MacBook-Pro:~ AbeVilla$ fastboot devices
FA35SS902798 fastboot
MacBook-Pro:~ AbeVilla$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35SS902798
(bootloader) imei: 990001468472873
(bootloader) meid: 99000146847287
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4043mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
so im am assuming that im flashed to this version of 1.29.651.10 android so to speak, but my actual image version is1.31.651.2? if i am understanding this correctly, that means i could flash any version i want but my actual bootloader is set on this1.31.651.2. So the RUU im using will not work until there is an updated version of the RUU, right? what if i was s-off? im currently s-on. would i be able to flash it back to stock if i was s-off and the image versions didnt match in the RUU? This is my first Htc devices and im felling kinda noobish.. please help.
So here is my fix..
I flashed a bone stock rom with no root found here... or restore nandroid. I usually make a nandroid backup before i flash su.zip. but anyway, after the restore i booted into the bootloader and types fastboot oem lock. then i proceeded to reboot, but my device kept booting into bootloader. i tried fastboot erase cache which didn't help. so i grabbed the firmware from this thread http://forum.xda-developers.com/showthread.php?t=2368907 . In the bootloader type...
fastboot oem reboot RUU
now you should be in a black screen with the htc logo
fastboot flash zip /navigate/to/zip/file
you will get fail the first time(pre-hboot update: please flush immediately)
just make sure your device is still in the RUU mode(black screen with htc logo, if not redo first step)
fastboot flash zip /navigate/to/zip/file
it should proceed to flash and get flash successful!
oh you might get a loading bar underneath the htc logo. this is normal. just make sure that in the terminal it said successful.
unplug and hold the power till it restarts.
now you are bone stock with stock recovery. this is the closest I've came to being stock since there currently isn't a RUU tool for the latest firmware. hope this helps. BIG THANKS TO bigdaddy619 for the input!
Techno Droid said:
Ok, so im new here to the htc forums but not the rooting community. I previously had all nexus devices and this is my first htc/one device. I dont understand what image version im on bc when i look under Settings>About>Software Info I see Software Version - 1.29.651.10. So Why is that i cant run this RUU without any problems? Im using this guide... http://forum.xda-developers.com/showthread.php?t=2250904
I Keep getting an error at the end. heres what i did
First i flashed this.... Sprint_HTC_One_1.29.651.10_Stock_Deodexed.zip
Second... fastboot oem lock (from bootloader screen)
Third... Ran the setup.exe from this this Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Fourth... i accepted the terms but my image version said 1.31.651.2. the image version didnt match when i ran the RUU.
at the end i get the error code 140. im posting some images so you guy can see.
in the bootloader screen i did: fastboot getvar all and got this
Last login: Tue Aug 13 21:11:14 on ttys000
MacBook-Pro:~ AbeVilla$ fastboot devices
FA35SS902798 fastboot
MacBook-Pro:~ AbeVilla$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35SS902798
(bootloader) imei: 990001468472873
(bootloader) meid: 99000146847287
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4043mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
so im am assuming that im flashed to this version of 1.29.651.10 android so to speak, but my actual image version is1.31.651.2? if i am understanding this correctly, that means i could flash any version i want but my actual bootloader is set on this1.31.651.2. So the RUU im using will not work until there is an updated version of the RUU, right? what if i was s-off? im currently s-on. would i be able to flash it back to stock if i was s-off and the image versions didnt match in the RUU? This is my first Htc devices and im felling kinda noobish.. please help.
Click to expand...
Click to collapse
s-off should let you ruu any image
Techno Droid said:
Ok, so im new here to the htc forums but not the rooting community. I previously had all nexus devices and this is my first htc/one device. I dont understand what image version im on bc when i look under Settings>About>Software Info I see Software Version - 1.29.651.10. So Why is that i cant run this RUU without any problems? Im using this guide... http://forum.xda-developers.com/showthread.php?t=2250904
I Keep getting an error at the end. heres what i did
First i flashed this.... Sprint_HTC_One_1.29.651.10_Stock_Deodexed.zip
Second... fastboot oem lock (from bootloader screen)
Third... Ran the setup.exe from this this Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Fourth... i accepted the terms but my image version said 1.31.651.2. the image version didnt match when i ran the RUU.
at the end i get the error code 140. im posting some images so you guy can see.
in the bootloader screen i did: fastboot getvar all and got this
Last login: Tue Aug 13 21:11:14 on ttys000
MacBook-Pro:~ AbeVilla$ fastboot devices
FA35SS902798 fastboot
MacBook-Pro:~ AbeVilla$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35SS902798
(bootloader) imei: 990001468472873
(bootloader) meid: 99000146847287
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4043mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
so im am assuming that im flashed to this version of 1.29.651.10 android so to speak, but my actual image version is1.31.651.2? if i am understanding this correctly, that means i could flash any version i want but my actual bootloader is set on this1.31.651.2. So the RUU im using will not work until there is an updated version of the RUU, right? what if i was s-off? im currently s-on. would i be able to flash it back to stock if i was s-off and the image versions didnt match in the RUU? This is my first Htc devices and im felling kinda noobish.. please help.
Click to expand...
Click to collapse
The Software Version - 1.29.651.10 refers to the software version of the rom you are running if you were to flash a rom based on 1.31.651.2 your software version in settings would reflect that.
Since you are s-on your phone most likely came with 1.31.651.2 why are you trying to go backwards? If you just want to go back to stock there is a stock 1.31.651.2 rom(rooted and unrooted) in Indirects thread.
bigdaddy619 said:
The Software Version - 1.29.651.10 refers to the software version of the rom you are running if you were to flash a rom based on 1.31.651.2 your software version in settings would reflect that.
Since you are s-on your phone most likely came with 1.31.651.2 why are you trying to go backwards? If you just want to go back to stock there is a stock 1.31.651.2 rom(rooted and unrooted) in Indirects thread.
Click to expand...
Click to collapse
BC I need to send it back to sprint and plus in want to learn the process so I know exactly what im doing. Is there and ruu for the version my boot loader reflects?
Sent from my One using Tapatalk 2
Techno Droid said:
BC I need to send it back to sprint and plus in want to learn the process so I know exactly what im doing. Is there and ruu for the version my boot loader reflects?
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
There is not an RUU for 1.31.651.2
I would suggest unlocking again
flash twrp 2.5.0.0
flash the Stock(no root) 1.31 rom in Indirect's thread
then relock again(your bootloader will say RE-LOCKED not LOCKED)
I kinda figured that I just had a brain fart about it. But when I flash a stock rom and relock bootloader it won't boot up I just keep booting into the bootloader. So if in was on an earlier version of 1.29.651.10 I would be able to relock and be stock, right?
Sent from my One using Tapatalk 2
Techno Droid said:
I kinda figured that I just had a brain fart about it. But when I flash a stock rom and relock bootloader it won't boot up I just keep booting into the bootloader. So if in was on an earlier version of 1.29.651.10 I would be able to relock and be stock, right?
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Did you check the MD5 on the stock rom you were trying to flash maybe it was a bad download?
In was on it running and all. Then I proceeded and relocked. Or did I do something wrong here?
Sent from my One using Tapatalk 2
Techno Droid said:
In was on it running and all. Then I proceeded and relocked. Or did I do something wrong here?
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Check PM
Same Issue As Techno Droid - ! SOS ! - 7 day old brick
Hi all,
I'm hoping someone can assist me here, its been a week now without my phone due to my botched attempts to flash a custom rom. I have the exact same situation as TechnoDroid's initial post, and same exact fails. I tried Techno Droids fix, but am getting the following error from this command:
fastboot oem reboot RUU
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.003s.
I've flashed the 1.31 stock ROM from Indirect's thread, and re-locked the bootloader, but I always get an OS that has no apps and begins a system boot loop after a few minutes.
Also, if I can find a compatible nandroid backup and flash it through TWRP would that be a possible fix?
Any help is greatly appreciated, I'll be looking into purchasing a backup phone from my MVNA, but would really like to unbrick this one since I paid full boat for an unlocked version!
- cheers
dancesWitShoes said:
Hi all,
I'm hoping someone can assist me here, its been a week now without my phone due to my botched attempts to flash a custom rom. I have the exact same situation as TechnoDroid's initial post, and same exact fails. I tried Techno Droids fix, but am getting the following error from this command:
fastboot oem reboot RUU
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.003s.
I've flashed the 1.31 stock ROM from Indirect's thread, and re-locked the bootloader, but I always get an OS that has no apps and begins a system boot loop after a few minutes.
Also, if I can find a compatible nandroid backup and flash it through TWRP would that be a possible fix?
Any help is greatly appreciated, I'll be looking into purchasing a backup phone from my MVNA, but would really like to unbrick this one since I paid full boat for an unlocked version!
- cheers
Click to expand...
Click to collapse
Check PM
BD619 said:
Check PM
Click to expand...
Click to collapse
having the same issue: stock deodexed flashed but unable to get ruu,, tsk (Sprint HTC One 1.29.651.10!)
pls help,,
I'm the next one in line with the same question, but no other answers helped me yet. What I did wrong was adb sideloading the OTA file using CWM recovery. That part I understand, so completely my own fault.
However, the update is still on the SD card and I tried to load stock recovery via fastboot so that I can install OTA from the SD card. What I get is something I find a lot of others have as well; the recovery fails to mount sd card 5 times. When I try to "Apply from SD card" I get an error "Check cid failed! --invalid operation--" and the phone reboots. The same error happens to users in many places, an example here: androidcentral . com/how-manually-update-your-google-play-edition-htc-one-android-44-kitkat
I think I can recover the phone with instructions (I can't post URLs yet) that will install a different recovery and uses adb sideload. But it also erases the sdcard which I try to avoid.
So, Is there anyone who can advice me what to do? If it cannot be avoided that my sdcard will be wiped; so be it. But I will manage doing that, I'm looking for an alternative at the moment. I suspect that if I find the correct recovery version that it will "mount" the "sdcard" (which I think is an emulation because the HTC One has no sdcard??) will also allow me to recover my phone with sdcard intact. But I find it difficult to find the correct recovery.img. I've tried two versions *can't find numbers back right now, will post if needed*.
HTC One, converted into GPe (so tampered and unlocked)
HBOOT 1.44
ruud.walraven said:
I'm the next one in line with the same question, but no other answers helped me yet. What I did wrong was adb sideloading the OTA file using CWM recovery. That part I understand, so completely my own fault.
However, the update is still on the SD card and I tried to load stock recovery via fastboot so that I can install OTA from the SD card. What I get is something I find a lot of others have as well; the recovery fails to mount sd card 5 times. When I try to "Apply from SD card" I get an error "Check cid failed! --invalid operation--" and the phone reboots. The same error happens to users in many places, an example here: androidcentral . com/how-manually-update-your-google-play-edition-htc-one-android-44-kitkat
...
HTC One, converted into GPe (so tampered and unlocked)
HBOOT 1.44
Click to expand...
Click to collapse
Ruud, I don't know if I completely understand your story, but you are able to get into stock recovery right? If so, do not choose 'Apply from SD card', but 'Apply from phone'. I got the same error messages (fails to mount SD card...), but if the OTA file is on your phone, you have to choose phone storage.
mbroeders said:
Ruud, I don't know if I completely understand your story, but you are able to get into stock recovery right? If so, do not choose 'Apply from SD card', but 'Apply from phone'. I got the same error messages (fails to mount SD card...), but if the OTA file is on your phone, you have to choose phone storage.
Click to expand...
Click to collapse
I should have mentioned that the other options (apply from phone and apply from cache) don't work either. One thing I am unsure about is if this is indeed the stock recovery.img I put back on. Is there a single recovery.img for HTC One, or a list where I can find which one came standard so I can put it back. My suspicion is that that recovery will work, although the guy I bought the phone from may have installed recovery/images that may have reformatted everything in a way that stock won't work any longer...
I noticed most people need to post fastboot getvars all. Makes sense to figure out what software I need so here it is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
ruud.walraven said:
I noticed most people need to post fastboot getvars all. Makes sense to figure out what software I need so here it is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Are you sure this is the GPe version? I get a feeling that you have the Sense version and then it won't work of course. (sorry if I'm wrong)
Sent from my HTC One using XDA Premium 4 mobile app
I've tried a whole range of things that didn't help. Don't want to preserve the sd card any longer.
Flashed recovery versions: 1.29.401.12, 2.24.401.8, 3.07.1700.1 and 3.58.1700.5.
Neither version was able to reinstall from sdcard. But I found out later that I may have done *something* to the sdcard (see CWM below)
Next I flashed CWM to try flashing a nandroid. However during the process I couldn't browse my sdcard anymore. Before flashing above recoveries I had CWM and then I could see all files. May have done something wrong.
After trying the mentioned nandroid a few times I realized that I am S-ON.
I have been trying to get S-OFF for the last few hours because I found a file I want to use on my phone (See htc1guru . com/2013/11/android-4-4-kit-kat-google-edition-3-58-1700-5-ruu-ota-files/). I've looked at Moonshine, but my phone is not in the list of supported rom versions (1.29.401.12). I tried Revone, but get error = 1.
So now I'm not sure what to do next!!
mbroeders said:
Are you sure this is the GPe version? I get a feeling that you have the Sense version and then it won't work of course. (sorry if I'm wrong)
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am absolutely sure I have a Sense version originally. I bought it from someone who unlocked the bootloader and replaced the sense firmware with GPe. OTA was working because I OTA-ed to 4.3. I've contacted him this morning, but he says to have no idea what files he used.
you bought it from an idiot.
you can't properly convert to GPE with s-on. That's why your hboot, mainver and cid are all wrong for a GPE conversion.
I assume you're boot-loader unlocked? flash cwm or TWRP. Then restore this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__102-1-29-401-12-2013-05-16-zip/
after restoring that nandroid try to s-off with revone and or rumrunner.
Revone: http://forum.xda-developers.com/showthread.php?t=2314582
Rumrunner: http://forum.xda-developers.com/showthread.php?t=2488772
once your s-off you can properly convert your phone to GPE. The problem wasn't just that you flashed it with a custom recovery but that the phone was never in a proper state to receive OTA for GPE!
use the RUU from here once your s-off to convert to GPE 4.4 : http://forum.xda-developers.com/showthread.php?t=2358781
you'll also want to go supercid with fastboot oem writecid 11111111
ruud.walraven said:
I am absolutely sure I have a Sense version originally. I bought it from someone who unlocked the bootloader and replaced the sense firmware with GPe. OTA was working because I OTA-ed to 4.3. I've contacted him this morning, but he says to have no idea what files he used.
Click to expand...
Click to collapse
I'm downloading all required files right now. In the meantime looking into everything to make sure to not further brick it once S-OFF. Tricky business!
ipfreelytech said:
you'll also want to go supercid with fastboot oem writecid 11111111
Click to expand...
Click to collapse
There's one question I found: according to this thread SuperCid 11111111 doesn't get OTA and the best bet for me would be HTC__001. Is that correct, or can I also choose from HTC_001 or GOOGL001? (the latter I remember reading is supposed to be good too). In any case ... I suppose I can best follow your instructions and I can change the cid to whatever needed afterwards anyway.
edit: It took 1.5 hours to download the nandroid, but something must have gone wrong because the file cannot be opened by winzip nor 7z. After the failed opening of the file I've md5-ed the entire zip file and it doesn't match the checksum on the download link. So started download again...
I have a problem; the download stops at different points, never completing. Must be a problem in the connection or at htc1guru. Is there an alternative file/download/mirror I can use as well? Have searched google for the same file with no results.
I was finally able to download the file through FF. Every time the download failed I started again, but paused and replaced the .part file with the failed download. When you resume FF detects the last bit and resumes from there. Best part was that I got my Chrome 900+MB download and used that as .part file. So I could resume nearly finished. Ran the checksum to be sure nothing funny had happened because of my tinkering. To quote Borat: great success.
However, after restoring the nandroid through CWM I tried both Revone and Rumrunner. Revone fails error = 1 and Rumrunner assumes I start from my homescreen (which I can't). A bit unwise, but I tried anyway from both fastboot and CWM but in neither case will Rumrunner continue. It claims there is no ADB connection (even though the phone shows up in adb devices).
So I am stuck for now. Still looking at as many posts about S-OFF as I can to see if I find some vital piece of inof I missed or something I can still try. But for now I'd like some idea's how to achieve S-OFF..
What is the date in your hboot version? If after June, then revone won't work. Have you tried moonshine?
SaHiLzZ said:
What is the date in your hboot version? If after June, then revone won't work. Have you tried moonshine?
Click to expand...
Click to collapse
hboot has a date? Hboot is 1.44 and bootloader start screen says apr 12 2013, is that what you mean?
My version (1.29.401.12) is not supported by moonshine for as far as I can tell.
I also notice now that fastboot getvars bootmode says: fastboot. Shouldn't this be disabled for revone and/or rumrunner?
ruud.walraven said:
...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
...
Click to expand...
Click to collapse
Just a question: In a sense I can't have messed anything up that bad because I'm S-ON. So if I would install the 4.3 release that was on the device before I sideloaded the 4.4 OTA through CWM, wouldn't it just work because all things point to the correct places? Since I broke it with adb sideloading, I could restore the device probably just as well, right?
In any case; I still would want to S-OFF my device to go through ipfreelytech's steps and get a functioning 4.4 GPe. But So far I found that Moonshine doesn't support my device and for both rumrunner and revone I need to start from a booted up android homescreen. So all three options don't seem to work. Did I really brick my phone, or is there still hope??
I had same problem on my device. I decided to install CWM instead of TWRM, downloaded RUU 4.2.2 and flashed it. Next I get update to 4.3 and 4,4 later and now everytning works perfect.
ziolooo said:
I had same problem on my device. I decided to install CWM instead of TWRM, downloaded RUU 4.2.2 and flashed it. Next I get update to 4.3 and 4,4 later and now everytning works perfect.
Click to expand...
Click to collapse
Willing to try, but I don't see the RUU file needed on http://forum.xda-developers.com/showthread.php?t=2428276 nor on htc1guru.com. This should be done through fastboot oem rebootRUU, right? If everything works I'm don. if OTA or some functions don't wrok I maybe able to S-OFF and follow previous instructions till the end. And if it doesn't work I'm back to where I am now anyway.
ruud.walraven said:
Willing to try, but I don't see the RUU file needed on http://forum.xda-developers.com/showthread.php?t=2428276 nor on htc1guru.com. This should be done through fastboot oem rebootRUU, right? If everything works I'm don. if OTA or some functions don't wrok I maybe able to S-OFF and follow previous instructions till the end. And if it doesn't work I'm back to where I am now anyway.
Click to expand...
Click to collapse
Here you have good tutorial how to install RUU:
http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
Download and flash RUU from this site.
ziolooo said:
Here you have good tutorial how to install RUU:
http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
Download and flash RUU from this site.
Click to expand...
Click to collapse
Thanks for the link. That won't work though because I'm still trying to achieve S-OFF which is a prerequisite to follow that guide.
ruud.walraven said:
Thanks for the link. That won't work though because I'm still trying to achieve S-OFF which is a prerequisite to follow that guide.
Click to expand...
Click to collapse
http://htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-moonshine-windows-0147992/
ziolooo said:
http://htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-moonshine-windows-0147992/
Click to expand...
Click to collapse
I already tried that.
ruud.walraven said:
...
In any case; I still would want to S-OFF my device to go through ipfreelytech's steps and get a functioning 4.4 GPe. But So far I found that Moonshine doesn't support my device and for both rumrunner and revone I need to start from a booted up android homescreen. So all three options don't seem to work. Did I really brick my phone, or is there still hope??
Click to expand...
Click to collapse
Hey guys need ur help with going back to stock.Essentially I flashed the stock ruu and locked the bootloader and toggled my device from S-OFF to S-ON but i forgot to flash the stock recovery after rooting my phone using TWRP. Now my device is S-ON with bootloader locked and with custom recovery.I tried to use revone-0.2.1 to S-OFF and then unlock my bootloader but after few tries it says successful but when i checked the bootloader it shows S-ON and tampered.I even used firewater thta was also unsuccessful so please i need urgent help.
P.S My phone is still rooted.
You don't need to soff to flash stock recovery. You need unlocked bootloader. Unlock it using aio kit and you can flash stock recovery after that. You cannot flash recovery with a locked bootloader.
Sent from my All Metal HTC One.
Android 4.4.2 - Sense 6.0
well i tried using revone's option of unlocking bootloader shows error code -1
Hboot is 1.44
and if ur talking about using the unlock bin code i need stock recovery for that.Can someone provide me a signed stock recovery as i tried to flash a recovery from ruu but it shows signature verification failure.
Bump need urgent help
Slim Shady said:
Bump need urgent help
Click to expand...
Click to collapse
what's your current "fastboot getvar all" (except IMEI and s/n)
nkk71 said:
what's your current "fastboot getvar all" (except IMEI and s/n)
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4179mV
(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.044s
Slim Shady said:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_u
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
finished. total time: 0.044s
Click to expand...
Click to collapse
well I couldn't find signed ruu, OTA, or signed firmware for your version, so best to start over from the beginning (unlock, s-off, etc), and do it again.
but one thing:
Essentially I flashed the stock ruu and locked the bootloader and toggled my device from S-OFF to S-ON but i forgot to flash the stock recovery after rooting my phone using TWRP
Click to expand...
Click to collapse
the RUU already has stock recovery, so why would you have TWRP there?
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.
nkk71 said:
what's your current "fastboot getvar all" (except IMEI and s/n)
Click to expand...
Click to collapse
nkk71 said:
well I couldn't find signed ruu, OTA, or signed firmware for your version, so best to start over from the beginning (unlock, s-off, etc), and do it again.
but one thing:
the RUU already has stock recovery, so why would you have TWRP there?
Click to expand...
Click to collapse
actually after applying the ruu i rooted the phone using twrp then locked the bootloader and then S-on the device.
Slim Shady said:
actually after applying the ruu i rooted the phone using twrp then locked the bootloader and then S-on the device.
Click to expand...
Click to collapse
see my last edit:
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.
Thats what I thought... restoring via RUU restores the recovery also.
nkk71 said:
see my last edit:
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.
Click to expand...
Click to collapse
Not even able to access twrp now. Is there any way u can help me ???
Slim Shady said:
Not even able to access twrp now. Is there any way u can help me ???
Click to expand...
Click to collapse
why can't you access TWRP
anyway, start from the beginning, unlock, s-off, etc.
nkk71 said:
why can't you access TWRP
anyway, start from the beginning, unlock, s-off, etc.
Click to expand...
Click to collapse
tried firewater not working asking to start the process again saying nasty chaser , then tried revone it reports success but when i check the bootloader it says s-on i just don't know what to do.
What happens when you choose recovery from bootloader?
finally success took a leap of faith used unlock token from htc and it worked yay.
Thanks to all the people who advised me and helped me troubleshoot.
can i run the ruu after i lock bootloader and return to s-on ???
also wanted to ask this
first i should get rid of tampered and lock my bootloader
then i should flash the ruu and them i should go S-on
right ?
Slim Shady said:
can i run the ruu after i lock bootloader and return to s-on ???
also wanted to ask this
first i should get rid of tampered and lock my bootloader
then i should flash the ruu and them i should go S-on
right ?
Click to expand...
Click to collapse
can you check my guide on how to do it: http://forum.xda-developers.com/showthread.php?t=2541082
RUU.ZIP method using this http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
this is a decrypted ruu.zip, so it only works with S-OFF.
got a new problem tampered text is not going away
getting error code -2 with revone
Slim Shady said:
got a new problem tampered text is not going away
Click to expand...
Click to collapse
WHY?? (how about more details next time )
EDIT: read the guide!!
nkk71 said:
WHY?? (how about more details next time )
EDIT: read the guide!!
Click to expand...
Click to collapse
Actually issue was dd commands and revone wasn't working for tampered so tried the guru rest and voila it worked.Now atlast everything's back to stock now i can give htc my phone and tell them to change it or repair it cause of the imsi issue im facing with the phone which happened after i got jtag brick repair.
Hey guys,
Sorry if I am in the wrong place for this question but I am completely stuck. I recently bought a HTC One M7 which was rooted. I did not know this when I was buying it. The new update came out and my phone asked me to update. I hit yes. My phone switched off and didn't come back on. After extensive research I got it back on to find the following:
1) It was rooted
2)Bootloader started up and TWRP is on the phone
3) There is now nothing on the phone. No firmware or packages at all
4) When I try to flash anything I get the error message: can't mount to system. I can mount to everything else ok just not internal storage.
I am unsure what recovery image and RUU to use. The phone (I was told was unlocked) was O2(Giffgaff).
Details are:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
Radio-4A.21.3263.04
OpenDSP-v32.120.724.0909
OS-3.62.206.1
eMMC-boot 2048MB
Oct 18 2013, 00:29:38. 0
IMAGE CRC
rpm: 0xC5567FC
sbl1: 0x9FE7A28C
sbl2: 0XA915A4DD
sbl3: 0xB221B6BB
tz: 0XCCD5DF62
radio: 0XEFA42613
hboot: 0xC174663B
boot: 0x94C89910
recovery: 0x59BF6CD
system: 0xFF83AB1
Any help at this stage would be greatly appreciated! I am about to just give up and bin it...
Thanks in advance!
When does it fail mounting system? When flashing a ROM in TWRP or flashing an RUU?
aooga said:
When does it fail mounting system? When flashing a ROM in TWRP or flashing an RUU?
Click to expand...
Click to collapse
it seems to be both. I try to flash RUU via fastboot and I get a signature fail. So I try to flash a ROM to the phone and it says failed to mount system. I put the items on a usb and tried it but get an 'unable to unzip' error. Its a bit above me to be honest. Thank you so much for helping.
olimoh8464 said:
it seems to be both. I try to flash RUU via fastboot and I get a signature fail. So I try to flash a ROM to the phone and it says failed to mount system. I put the items on a usb and tried it but get an 'unable to unzip' error. Its a bit above me to be honest. Thank you so much for helping.
Click to expand...
Click to collapse
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...
Devilish_Angel said:
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...
Click to expand...
Click to collapse
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?
olimoh8464 said:
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?
Click to expand...
Click to collapse
... run it from desktop while phone in bootloader. no need to run boot image ...
olimoh8464 said:
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?
Click to expand...
Click to collapse
RUU must match your CID number.
I add you here link to a good thread:
http://forum.xda-developers.com/showthread.php?t=2358738
tetakpatalked from Nexus 7 flo
Devilish_Angel said:
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...
Click to expand...
Click to collapse
This is wrong. You can flash the ruu that mathches the cid and mid of your phone even with a locked bl.
Sent from my GT-I9505 using Tapatalk
Thank you for the advice and the link! I will go try this now and let you know how I get on!
aooga said:
This is wrong. You can flash the ruu that mathches the cid and mid of your phone even with a locked bl.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
... did i say something different than what you are saying ...
@aooga Angel's point was S-On, I think.
tetakpatalked from the legendary i9000
olimoh8464 said:
Hey guys,
Sorry if I am in the wrong place for this question but I am completely stuck. I recently bought a HTC One M7 which was rooted. I did not know this when I was buying it. The new update came out and my phone asked me to update. I hit yes. My phone switched off and didn't come back on. After extensive research I got it back on to find the following:
1) It was rooted
2)Bootloader started up and TWRP is on the phone
3) There is now nothing on the phone. No firmware or packages at all
4) When I try to flash anything I get the error message: can't mount to system. I can mount to everything else ok just not internal storage.
I am unsure what recovery image and RUU to use. The phone (I was told was unlocked) was O2(Giffgaff).
Details are:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
Radio-4A.21.3263.04
OpenDSP-v32.120.724.0909
OS-3.62.206.1
eMMC-boot 2048MB
Oct 18 2013, 00:29:38. 0
IMAGE CRC
rpm: 0xC5567FC
sbl1: 0x9FE7A28C
sbl2: 0XA915A4DD
sbl3: 0xB221B6BB
tz: 0XCCD5DF62
radio: 0XEFA42613
hboot: 0xC174663B
boot: 0x94C89910
recovery: 0x59BF6CD
system: 0xFF83AB1
Any help at this stage would be greatly appreciated! I am about to just give up and bin it...
Thanks in advance!
Click to expand...
Click to collapse
Post a fastboot getvar all
RUU.exe files or ROM Update Utility files are executable files that run on Windows PC
RUU.zip files are simply the same as above but rather than using a Windows exe file to run them, they are packaged in a zip file that can be flashed in Fastboot mode
The RUU has to match your CID/MID. If your S-On, the RUU as to be same version or higher
Sent from my Nexus 7 using XDA Premium 4 mobile app
Devilish_Angel said:
... did i say something different than what you are saying ...
Click to expand...
Click to collapse
Uh..yeah. You said:
when bootloader is unlocked and phone s-on, no ruu will work
Click to expand...
Click to collapse
bored_stupid said:
Post a fastboot getvar all
RUU.exe files or ROM Update Utility files are executable files that run on Windows PC
RUU.zip files are simply the same as above but rather than using a Windows exe file to run them, they are packaged in a zip file that can be flashed in Fastboot mode
The RUU has to match your CID/MID. If your S-On, the RUU as to be same version or higher
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks! Is there any way you could tell me the correct RUU to download? I will post a fastboot getvar all after work this evening. I tried one that I thought was right but when I click to run it as administrator I get prompted with the normal are you sure? click yes and nothing happens. It just doesn't run. Tried downloading it again but still nothing. Any ideas?
olimoh8464 said:
Thanks! Is there any way you could tell me the correct RUU to download? I will post a fastboot getvar all after work this evening. I tried one that I thought was right but when I click to run it as administrator I get prompted with the normal are you sure? click yes and nothing happens. It just doesn't run. Tried downloading it again but still nothing. Any ideas?
Click to expand...
Click to collapse
Yeah no problems. Off to work myself now, but will post correct link if any and possible other solutions.
Sent from my HTC One using XDA Premium 4 mobile app
bored_stupid said:
Yeah no problems. Off to work myself now, but will post correct link if any and possible other solutions.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
C:\Users\milo\Desktop\Newest>fastboot getvar all
(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.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W900013
(bootloader) imei: 3578640********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3965mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
OMG My phone literally did the same exact thing today!! I woke up, a few things were force closing so I decided that I would just reboot the phone...... Big mistake, once I did that, the phone just stayed in the booting up animation. So I figured hey what ever ill just reflash the ROM in TWRP.......Nope, couldn't boot into recovery either, the phone would flash the TWRP screen then just reset itself. Again, I thought no biggie ill just reinstall TWRP. This (again) proved to be useless, after multiple (successful) install's the phone still refused to boot into TWRP. So I finally got CWM to install, a noticed a few things at the bottom of the screen about something not being mounted properly, I didn't pay that much attention to it, i just wanted my phone back at that point. I tried to wipe my phone for a fresh flash, but as soon as the wipe began the phone reset itself. At this point I was on the brink of throwing this thing into the torrential down-pour that god decided to place in my city.
Next I tried to install Viper ROM because I knew it had a wipe functionality built into it's Aroma installer. Went through all the checklists got to the start install screen, clicked next, and then began to wipe......... and then reset again........
So finally I got TWRP reinstalled, and go install a fresh ROM and and immediately met with a screen full of : "Unable to Mount XXXXXXX" (Picture attached). So then I figure alright well my last resort has to be to use a RUU. Found this nice little thread (http://forum.xda-developers.com/showthread.php?t=2316726) and decided to use the FUU (4.19.401.11 Full Wipe). Unfortunately all that did was move my HBoot from 1.4 (or something like that) to 1.5 (or something like that), put the tamper flag back, and bring back the annoying red text at the bottom of the phone at boot (the thing about development build, blah blah blah). I reinstalled TWRP yet again hoping for the best, but still nothing. It cant seem to mount anything (what ever that means).
So now im here, stuck using my old One X. Any suggestions or answers or criticism would be very much appreciated.
Thank you!!!!!
olimoh8464 said:
C:\Users\milo\Desktop\Newest>fastboot getvar all
(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.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W900013
(bootloader) imei: 3578640********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3965mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
This is the RUU.exe you require. Run from PC
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353143_signed_2-exe/
Sent from my HTC One using XDA Premium 4 mobile app
bored_stupid said:
This is the RUU.exe you require. Run from PC
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353143_signed_2-exe/
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for that! I have downloaded it and tried to run it but it doesn't open? I get the loading message after I click run as administrator but nothing happens. Do I need HTC sync installed or deleted for this?
Thanks
olimoh8464 said:
Thanks for that! I have downloaded it and tried to run it but it doesn't open? I get the loading message after I click run as administrator but nothing happens. Do I need HTC sync installed or deleted for this?
Thanks
Click to expand...
Click to collapse
Did you check the MD5
4961fdbbadba53c9640f3638f56faec1
When you say nothing happens.. Doesn't it even try to run?
Sent from my HTC One using XDA Premium 4 mobile app
[Fixed][Solution]
This should work for anyone who soft bricked there device but still has the 1.44 HBoot to allow them to still flash a recovery. I did not come up with any of this but was helped by nkk71 who showed me the way. I dealt with this problem for over 2 days now non-stop trying to fix it only missing 1 step that made all the difference.
This method is for a HTC One (M7) Sprint Variant:
-Be sure to use HTCDev to unlock your phone and flash a custom recovery. (I used TWRP)
-Be sure to have all the adb and fastboot exe files needed. If you bricked your phone you most likely already do but if not there are tons of links on the forums to help you get all the information you need from them.
-Check to make sure what RUU your phone is at by going into fastboot and using a cmd window type: fasboot getvar all. This will display your phones information. If you happen to be at 1.31 like my phone was you will need to do the next step, if not then find your recovery.
- Fix your version main to say 1.29.651.10 by editing the misc partition
Boot into recovery
In the recovery mount your device. I mounted all parts in TWRP.
Open a cmd window and doucle check that your device is connected by typing: adb devices
(If it shows a set up numbers and letters and then says recovery then that is your device.)
Now type: adb shell
type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
type: adb reboot bootloader
Once it loads back into the bootloader click on fastboot and check to see if your device is connected by typing: fastboot devices
If you see you device type: fastboot oem lock (This will relock your device)
- Now you are ready to run the RUU. (After it runs your phone is back to stock)
If any of this is confusing, there are links below that were used to get me through this. If you need to do this I wish you luck.
Original Post:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.
toxicfumes22 said:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.
Click to expand...
Click to collapse
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output
nkk71 said:
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output
Click to expand...
Click to collapse
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4117mV
(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.059s
2) Yes on Sprint, but with no activation on this phone now.
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
BTW, Thank you for the response.
toxicfumes22 said:
BTW, Thank you for the response.
Click to expand...
Click to collapse
Sure, no problem.
toxicfumes22 said:
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
2) Yes on Sprint, but with no activation on this phone now.
Click to expand...
Click to collapse
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
toxicfumes22 said:
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
Click to expand...
Click to collapse
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
toxicfumes22 said:
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
Click to expand...
Click to collapse
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction
nkk71 said:
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
Click to expand...
Click to collapse
Nice trick, still learning a lot from you
alray said:
Nice trick, still learning a lot from you
Click to expand...
Click to collapse
it's an "old trick", i take no credit at all for it ... as long as hboot version is the same, fixing the version-main (using adb or even the "misctool" <- it's somewhere on xda, dont have a link handy atm) should work fine
extract:
Code:
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version... [I]<- this is where it would fail, without that fix[/I]
(bootloader) checking hboot version... [I]<- this is where it would fail if hboot is higher[/I]
(bootloader) start image[boot] unzipping & flushing...
nkk71 said:
Sure, no problem.
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction
Click to expand...
Click to collapse
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.
toxicfumes22 said:
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.
Click to expand...
Click to collapse
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.
New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(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
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.
toxicfumes22 said:
New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(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
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.
Click to expand...
Click to collapse
yes should work fine now, give it a try.
alray said:
yes should work fine now, give it a try.
Click to expand...
Click to collapse
nkk71 said:
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.
Click to expand...
Click to collapse
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.
toxicfumes22 said:
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.
Click to expand...
Click to collapse
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
All thanks for you
My only contribution here was to say "give it a try" :laugh:
alray said:
All thanks for you
My only contribution here was to say "give it a try" [emoji23]
Click to expand...
Click to collapse
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk
nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
I copied and pasted, its exactly what I used. If it's wrong let me know and I'll fix though.
Another update though is I am now Unlocked with S-Off w/o Tampered. Basically what I wanted.
Now should be my last questions, but it's a good idea to update to the newest firmware correct?
Firmware will never be able to stop me from achieve what I just did to fix the phone correct?
nkk71 said:
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
Yup, I was going to not do a thing until I had a response. I was just worried I'd somehow mess it up. Just one confirmation that it looked good was enough to give me confidence.