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,,
So I can't seem to find a solution to my specific issue. A little background first. I was on Modaco switch beta 13 and decided I'd move on to something else because 1) hadn't been an update for quite a while and 2) I really didn't switch back to Sense except when I wanted to play around with Zoe. I restarted into CWM recovery and tried to flash CM 11. It gave me an error and I realized I was downlevel on CWM recovery. I tried to flash an updated CWM and now only have access to fastboot. When I try to boot to recovery it gives me the HTC splashscreen and hangs. I tried TWRP, CWM, and stock with the same results.
Checking fastboot getvar I noticed some really strange entries. serialno and modelid were corrupt. Here is the output of fastboot getvar all
Code:
# 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.1540.3
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ߞ�X�C
w\ `2�#
(bootloader) imei: xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.063s
# fastboot getvar mid
mid: �
finished. total time: 0.002s
# fastboot getvar serialno
serialno: ߞ�X�C
w\ `2�#
finished. total time: 0.002s
I read the following post to recover my serial number
http://forum.xda-developers.com/showthread.php?t=1724475
I don't believe I had the ENG hboot so I get the following:
Code:
fastboot oem writemid PN07120
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.012s
# fastboot oem writeserialno 1234567890
...
FAILED (status malformed (0 bytes))
finished. total time: 1.000s
I tried flashing the ENG hboot, but....
Code:
# fastboot flash zip ENG_hboot.zip
sending 'zip' (475 KB)...
OKAY [ 0.242s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.648s
Yep, catch 22. Corrupt model ID, so it won't flash.
Another interesting thing I noticed was the 2nd line on the display in fastboot
Code:
**** UNLOCKED ****
M7_UL UNKNOWN SHIP S-OFF RH
CID=BS_US001
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
...
Anyway one of the messages in the forums said that once they resolved the model ID and serial number everything worked.
Unfortunately this is my main phone and I'd like to use it. Not very useful right now. Anyone have any ideas?
vmcp said:
So I can't seem to find a solution to my specific issue. A little background first. I was on Modaco switch beta 13 and decided I'd move on to something else because 1) hadn't been an update for quite a while and 2) I really didn't switch back to Sense except when I wanted to play around with Zoe. I restarted into CWM recovery and tried to flash CM 11. It gave me an error and I realized I was downlevel on CWM recovery. I tried to flash an updated CWM and now only have access to fastboot. When I try to boot to recovery it gives me the HTC splashscreen and hangs. I tried TWRP, CWM, and stock with the same results.
Checking fastboot getvar I noticed some really strange entries. serialno and modelid were corrupt. Here is the output of fastboot getvar all
Code:
# 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.1540.3
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ߞ�X�C
w\ `2�#
(bootloader) imei: xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.063s
**** UNLOCKED ****
M7_UL UNKNOWN SHIP S-OFF RH
CID=BS_US001
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
...
Anyway one of the messages in the forums said that once they resolved the model ID and serial number everything worked.
Unfortunately this is my main phone and I'd like to use it. Not very useful right now. Anyone have any ideas?
Click to expand...
Click to collapse
Maybe you can edit the android-info.txt of the eng hboot. I.E replacing the ''MODELID: PN0710000'' for ''MODELID: ********* '' don't forget to add your CID too (BS_US001). Or maybe replacing the MODELID with your corrupted MID: (MODELID: �)
Which eng hboot are you trying to flash? There are some rumrunner hboot with eng commands set (full set of fastboot oem commands) here: http://rumrunner.us/hboots/
or maybe with the eng hboot from here
edit: Did you erased cache after flashing recovery?
if you can get recovery to boot then you could use this tool to change MID
did you tried a ruu.zip? even if im almost sure it will output the same model id error...
alray said:
Maybe you can edit the android-info.txt of the eng hboot. I.E replacing the ''MODELID: PN0710000'' for ''MODELID: ********* '' don't forget to add your CID too (BS_US001). Or maybe replacing the MODELID with your corrupted MID: (MODELID: �)
Click to expand...
Click to collapse
I was actually thinking/wondering about that. I guess that'll be my next step. I wasn't sure what to put for the MODELID since mine currently is corrupt. But I suppose I could try both. Good idea.
Which eng hboot are you trying to flash? There are some rumrunner hboot with eng commands set (full set of fastboot oem commands) here: http://rumrunner.us/hboots/
or maybe with the eng hboot from here
Click to expand...
Click to collapse
I have the ENG hboot from the 2nd link. I haven't tried rumrunner hboot. I'll d/l and give that a go too.
edit: Did you erased cache after flashing recovery?
if you can get recovery to boot then you could use this tool to change MID
Click to expand...
Click to collapse
Yes, I did erase cache. Don't know if I need to, but usually do that every time I try something.
Yeah, saw that thread too. I thought it'd be easy to do if I had adb/recovery.
did you tried a ruu.zip? even if im almost sure it will output the same model id error...
Click to expand...
Click to collapse
Yep. same result.
Thanks for the ideas, I'll give 'em a try.
EDIT: So I tried the rumrunner hboot and the ENG hboot.
Code:
# fastboot flash zip ENG_hboot.zip
< waiting for device >
sending 'zip' (474 KB)...
OKAY [ 0.241s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.648s
I got the same thing even when I tried to add the corrupt entry in the android-info.txt. Is there any way to bypass the model ID check?
DO NOT lock bootloader or go S-ON.
You should flash the HTC DEV edition firmware. Also use a different computer/USB/port to ensure this problem is in the phone
SaHiLzZ said:
DO NOT lock bootloader or go S-ON.
Click to expand...
Click to collapse
Yeah, no joke!
You should flash the HTC DEV edition firmware. Also use a different computer/USB/port to ensure this problem is in the phone
Click to expand...
Click to collapse
Yes, I tried the RUU from HTC's site for the developer edition and it claimed my battery was low. I'll charge and try again.
It was a good idea to try a different computer. I had already tried two different USB cables and a different port. All with the same results. Even the other computer gave me the same response.
So I had a few ideas. 1) modify the fastboot source to ignore the error for incorrect mid and flash anyway. After trying a few hacks with the code I read the protocol.txt and determined that it wasn't fastboot that was complaining but the bootloader. So that left my other idea (which was actually the first idea I had). Find out what that gibberish was and put that in the android-info.txt as my modelid then hope the bootloader did a compare with the gibberish I had in the android-info.txt. Unfortunately that didn't work either. I re-compiled fastboot with a few mods of my own so I could get the full details of the gibberish. I modified the output to give me the hex values of what the phone thought it's serial number and model id was. Here is the output:
Code:
# ./fastboot getvar modelid
modelid: �
b8
finished. total time: 0.002s
root# ./fastboot getvar serialno
serialno: ߞ�X�C
w\ `2�#
df9ef4588043d60a775c096032ea23
finished. total time: 0.002s
So I even tried an android-info.txt with the hex b8 value ctrl-code value, not the string b8, and got the same result...
Oh and yes I also tried with the wildcard modelid: *********
Same result.
Code:
# ./fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.071s]
finished. total time: 0.071s
# ./fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.042s]
finished. total time: 0.042s
# ./fastboot flash zip ENG_hboot.zip
< waiting for device >
sending 'zip' (475 KB)...
OKAY [ 0.241s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.645s
vmcp said:
Yeah, no joke!
Click to expand...
Click to collapse
looks really messy in here!! :crying:
is there any way you can get to an "adb shell" (custom recovery or booted ROM)?
you have "(bootloader) version-bootloader: 1.44.0000"
can you please try
fastboot boot <name of custom recovery>.img
if you can get to adb working let me know...
---------- Post added at 09:47 PM ---------- Previous post was at 09:29 PM ----------
though just for info, last (actually, one and only attempt with such corrupt partitions), didnt work
FYI: http://forum.xda-developers.com/showpost.php?p=50067052&postcount=30
nkk71 said:
looks really messy in here!! :crying:
is there any way you can get to an "adb shell" (custom recovery or booted ROM)?
you have "(bootloader) version-bootloader: 1.44.0000"
can you please try
fastboot boot <name of custom recovery>.img
if you can get to adb working let me know...
---------- Post added at 09:47 PM ---------- Previous post was at 09:29 PM ----------
though just for info, last (actually, one and only attempt with such corrupt partitions), didnt work
FYI: http://forum.xda-developers.com/showpost.php?p=50067052&postcount=30
Click to expand...
Click to collapse
I tried this but got to the same white HTC splashscreen. Just sits there. Never seems to make it to recovery.
I've tried ADB commands, but it appears it isn't fully loaded so I'm not able to connect via ADB. I'll try flashing the RUU, but it sounds like that other person in that thread didn't have good results even after a successful RUU flash! :crying:
I'm really starting to get worried that there isn't much I can do to fix the issue. I'm going crazy without a phone.
vmcp said:
I tried this but got to the same white HTC splashscreen. Just sits there. Never seems to make it to recovery.
I've tried ADB commands, but it appears it isn't fully loaded so I'm not able to connect via ADB. I'll try flashing the RUU, but it sounds like that other person in that thread didn't have good results even after a successful RUU flash! :crying:
I'm really starting to get worried that there isn't much I can do to fix the issue. I'm going crazy without a phone.
Click to expand...
Click to collapse
I know!!! Spent 3 or 4 serious teamviewer sessions with him, after getting android-info.txt "fixed" (for that MID, if you can call it that), and successfully fully flashing ruu (from a to z), still nothing.
and without able to get (and eventually, if possible, write) to the specific partitions in question, then it looks like it will need a motherboard replacement.
nkk71 said:
I know!!! Spent 3 or 4 serious teamviewer sessions with him, after getting android-info.txt "fixed" (for that MID, if you can call it that), and successfully fully flashing ruu (from a to z), still nothing.
and without able to get (and eventually, if possible, write) to the specific partitions in question, then it looks like it will need a motherboard replacement.
Click to expand...
Click to collapse
uh oh! Perhaps the only saving grace for me is that I have an unlocked bootloader. I read about using hexedit to make a malformed android-info.txt. Perhaps I should try that. Although I'm a little worried because I kinda thought I tried that. But wasn't able to flash the ENG bootloader.
vmcp said:
uh oh! Perhaps the only saving grace for me is that I have an unlocked bootloader. I read about using hexedit to make a malformed android-info.txt. Perhaps I should try that. Although I'm a little worried because I kinda thought I tried that. But wasn't able to flash the ENG bootloader.
Click to expand...
Click to collapse
check
ROUND 2: was able to create a "good" (as you mentioned "malformed" android-info.txt), and able to flash anything and everything in ruu mode
ROUND 5: got the bootloader unlocked
==> still no joy
if you can get to read / write partitions, let me know, I know which ones i'm after, though only through adb; if there is a way doing it in fastboot i would love to know.
---------- Post added at 11:45 PM ---------- Previous post was at 11:18 PM ----------
hmm, am i thinking of what i'm thinking? would that even be possible?
OP
@ayk33
i'm gonna check something tomorrow
@ayk33 you still have that phone?
nkk71 said:
check
ROUND 2: was able to create a "good" (as you mentioned "malformed" android-info.txt), and able to flash anything and everything in ruu mode
ROUND 5: got the bootloader unlocked
==> still no joy
if you can get to read / write partitions, let me know, I know which ones i'm after, though only through adb; if there is a way doing it in fastboot i would love to know.
Click to expand...
Click to collapse
This is kinda scary. Looks like the exact same issue the other guy had!
So I found out I had a special char before the proper hex number. So I was able to flash the ENG bootloader. I've set my serial number and model ID via fastboot oem write* commands. Now getvar shows correct information:
Code:
# ./fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: UNKNOWN ENG S-OFF
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN07120
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4239mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Although all is NOT good. I still think that the model id is messed up somewhere. From the bootloader if I select "barcode", it displays correct IMEI and S/N. The Model ID is still all jacked up and has all sorts of gibberish. I don't get it because the getvar mid displays the correct model ID (PN07120).
I flashed recovery and tried to boot to recovery (also using the command you gave me), but hangs in the same spot. Still no ADB access! :crying:
vmcp said:
This is kinda scary. Looks like the exact same issue the other guy had!
So I found out I had a special char before the proper hex number. So I was able to flash the ENG bootloader. I've set my serial number and model ID via fastboot oem write* commands. Now getvar shows correct information:
Code:
# ./fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: UNKNOWN ENG S-OFF
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN07120
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4239mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Although all is NOT good. I still think that the model id is messed up somewhere. From the bootloader if I select "barcode", it displays correct IMEI and S/N. The Model ID is still all jacked up and has all sorts of gibberish. I don't get it because the getvar mid displays the correct model ID (PN07120).
I flashed recovery and tried to boot to recovery (also using the command you gave me), but hangs in the same spot. Still no ADB access! :crying:
Click to expand...
Click to collapse
Mid is 9 characters!
I'm gonna check something tomorrow... wicked!
Sent from my HTC One using Tapatalk
nkk71 said:
Mid is 9 characters!
I'm gonna check something tomorrow... wicked!
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Ah, that could have been my problem. I re-wrote the mid by the following:
Code:
# ./fastboot oem writemid PN0712000
...
(bootloader) Start Verify: 0
OKAY [ 0.073s]
finished. total time: 0.073s
But the model id is still messed up on the barcode.
One other thing to note is it still shows UNKNOWN instead of PVT for version-misc. I'd guess that be causing problems too. Sounds like more than just the mid and serialno got corrupt.
vmcp said:
Ah, that could have been my problem. I re-wrote the mid by the following:
Code:
# ./fastboot oem writemid PN0712000
...
(bootloader) Start Verify: 0
OKAY [ 0.073s]
finished. total time: 0.073s
But the model id is still messed up on the barcode.
One other thing to note is it still shows UNKNOWN instead of PVT for version-misc. I'd guess that be causing problems too. Sounds like more than just the mid and serialno got corrupt.
Click to expand...
Click to collapse
So any updates? The real problem is that the partition that got corrupted contains a lot of info, that cannot be found anywhere else on the phone (not only MID and serial number, much more)
I even think I've thought of a way to rewrite that partition, but the question is: with what information (MID, PID, s/n, etc).
Do you still have the box of the phone? (some of that info in that partition is on the original box, but not all of it)
nkk71 said:
I even think I've thought of a way to rewrite that partition, but the question is: with what information (MID, PID, s/n, etc).
Do you still have the box of the phone? (some of that info in that partition is on the original box, but not all of it)
Click to expand...
Click to collapse
Are you thinking mmcblk0p6, the mfg partition? I think that could work by dumping a known good one, flashing over the corrupt partition in fastboot or recovery and then using eng hboot to rewrite original sn, imei, mid, cid, etc.
Imei is etched on sim tray, other info can also be found in a couple of other partitions.
cschmitt said:
Are you thinking mmcblk0p6, the mfg partition? I think that could work by dumping a known good one, flashing over the corrupt partition in fastboot or recovery and then using eng hboot to rewrite original sn, imei, mid, cid, etc.
Imei is etched on sim tray, other info can also be found in a couple of other partitions.
Click to expand...
Click to collapse
Yep, exactly :good:
CID and IMEI, not worried about, the original ones can be found in two other partitions (unless CID was changed, but of little consequence), the bad ones (that don't seem to be anywhere else), are: MAC (hmm), MID, S/N, PID and the others I don't even know what they mean
and would the rest of the parameters in that partition (board version, gains, etc) matter.
PS: unfortunately can't seem to get to recovery in any way with a corrupt p6, trust me I tried
nkk71 said:
PS: unfortunately can't seem to get to recovery in any way with a corrupt p6, trust me I tried
Click to expand...
Click to collapse
But fastboot is OK? If so, eng hboot has a lot of commands, maybe possible to flash mfg info into p6 that way. Don't have access to my laptop atm, but can check it out later if you don't get to it first. ?
cschmitt said:
But fastboot is OK? If so, eng hboot has a lot of commands, maybe possible to flash mfg info into p6 that way. Don't have access to my laptop atm, but can check it out later if you don't get to it first. ?
Click to expand...
Click to collapse
actually, I was thinking of simply:
fastboot flash /dev/block/mmcblk0p6 <name of good p6>.img
(or /dev/mmcblk0p6 or mmcblk0p6, whatever would work)
but I would really like to pull the corrupted one first, since so many parameters are repeated in p6, then if it's only partially corrupted, one could (theoretically) reconstruct it.
Problem is, I have no idea how to "dd" it out, using only fastboot. in ENG hboot there are commands, but I've found zero (concrete) information about their use.
If the partition can be pulled using adb then it can be compared to a working file and being right information be inserted and written back to the device that is my theory.
sent from my mobile device
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
EFS professional allows this on samsung devices. Someone will need to check if the same is true on htc
sent from my mobile device
SaHiLzZ said:
If the partition can be pulled using adb then it can be compared to a working file and being right information be inserted and written back to the device that is my theory.
sent from my mobile device
Click to expand...
Click to collapse
no adb , that would make things a lot easier (maybe), only fastboot commands, so if anybody knows how to "dd" partitions using fastboot only please let us know.
Hello guys,
I bought a shiny new M8 and wanted to sell my M7 now. Problem: I can't for the heck of it figure out how to revert back to stock. I was on ARHD all the time.
First of all, my getvar all. I was S-OFF.
F:\fastboot>fastboot getvar all
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.09.401.1
version-misc: PVT SHIP S-OFF
serialno: SH35JWxxxxx
imei: 354436056xxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4279mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-f361905d64
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.064s
Click to expand...
Click to collapse
I already relocked the bootloader as I understood that it needs to be relocked to install an official RUU. So far so good.
I downloaded the latest RUU (RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_R adio_4A.23.3263.28_10.38r.1157.04L_release_353069_ signed_2-1.exe) and it just gets stuck at Checking Header and 5%.
I googled a bit and found this thread here where it is suggested to use m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed and then OTA all the way up. Well, this RUU won't even begin the update process as it says that this RUU is incompatible, right before the flash should start.
I even tried extracting the Rom.zip out the latest RUU and flashing it manually, this is what I get:
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of th
e block size 4096
sending sparse 'zip' (1490936 KB)...
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of th
e block size 4096
OKAY [ 67.418s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 67.608s
Click to expand...
Click to collapse
Can anyone point me in the right direction here? I don't really know what else to try.
fBx said:
Hello guys,
I bought a shiny new M8 and wanted to sell my M7 now. Problem: I can't for the heck of it figure out how to revert back to stock. I was on ARHD all the time.
First of all, my getvar all. I was S-OFF.
I already relocked the bootloader as I understood that it needs to be relocked to install an official RUU. So far so good.
I downloaded the latest RUU (RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_R adio_4A.23.3263.28_10.38r.1157.04L_release_353069_ signed_2-1.exe) and it just gets stuck at Checking Header and 5%.
I googled a bit and found this thread here where it is suggested to use m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed and then OTA all the way up. Well, this RUU won't even begin the update process as it says that this RUU is incompatible, right before the flash should start.
I even tried extracting the Rom.zip out the latest RUU and flashing it manually, this is what I get:
Can anyone point me in the right direction here? I don't really know what else to try.
Click to expand...
Click to collapse
you already have a thread here: http://forum.xda-developers.com/showthread.php?t=2796167 for the same issue. why a 2nd one?
btw you don't need to relock bootloader to flash ruu when the phone is s-off.
Would it work to flash a nandroid backup of an original german unbranded phone via CWM?
fBx said:
Hello guys,
I bought a shiny new M8 and wanted to sell my M7 now. Problem: I can't for the heck of it figure out how to revert back to stock. I was on ARHD all the time.
First of all, my getvar all. I was S-OFF.
I already relocked the bootloader as I understood that it needs to be relocked to install an official RUU. So far so good.
I downloaded the latest RUU (RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_R adio_4A.23.3263.28_10.38r.1157.04L_release_353069_ signed_2-1.exe) and it just gets stuck at Checking Header and 5%.
I googled a bit and found this thread here where it is suggested to use m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed and then OTA all the way up. Well, this RUU won't even begin the update process as it says that this RUU is incompatible, right before the flash should start.
I even tried extracting the Rom.zip out the latest RUU and flashing it manually, this is what I get:
Can anyone point me in the right direction here? I don't really know what else to try.
Click to expand...
Click to collapse
I have the same problem, How did you fix?
maxwilliam100 said:
I have the same problem, How did you fix?
Click to expand...
Click to collapse
try to flash the firmware first
alray said:
try to flash the firmware first
Click to expand...
Click to collapse
Thanks for the tip @alray
I'm downloading the firmware and will defenately follow directions form this link
trjlive (dot) com/guide-install-firmware-htc-one-m7/
In the meantime here is the info from my phone
HTML:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: xxxxxxxx
imei: xxxxxxxxxxxxxxxx
meid: 99000146508682
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: 11111111
battery-status: good
battery-voltage: 3947mV
partition-layout: Generic
ecurity: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-371c4f408e
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.072s
maxwilliam100 said:
Thanks for the tip @alray
I'm downloading the firmware and will defenately follow directions form this link
trjlive (dot) com/guide-install-firmware-htc-one-m7/
In the meantime here is the info from my phone
HTML:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: 11111111
battery-status: good
battery-voltage: 3947mV
partition-layout: Generic
ecurity: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-371c4f408e
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.072s
Click to expand...
Click to collapse
Wait, you have a sprint phone? Hope you ar enot trying to flash this 4.19.401.9 ruu for GSM phones?
Btw you have s-off, you can use every ruu intended for sprint variant m7wls (x.xx.651.x RUU). Do not attempt to flash ruu for GSM variants. You should also set back your cid to its original value (SPCS_001).
And remove your S/N, IMEI and MEID numbers from your above post, these are sensitive data you want to keep for yourself.
alray said:
Wait, you have a sprint phone? Hope you ar enot trying to flash this 4.19.401.9 ruu for GSM phones?
Btw you have s-off, you can use every ruu intended for sprint variant m7wls (x.xx.651.x RUU). Do not attempt to flash ruu for GSM variants. You should also set back your cid to its original value (SPCS_001).
And remove your S/N, IMEI and MEID numbers from your above post, these are sensitive data you want to keep for yourself.
Click to expand...
Click to collapse
I'm not sure if this is sprint, its not branded anywhere(See attached images). The download is completed, Should i proceed from the link i provided? @alray
Excuse i cannot attache the images directly here because i'm a new user, please see the links below to see how the phone looks like.
i.imgur.com/6kzhlUS.jpg
i.imgur.com/mMDQ6uZ.jpg
maxwilliam100 said:
I'm not sure if this is sprint, its not branded anywhere(See attached images). The download is completed, Should i proceed from the link i provided? @alray
Excuse i cannot attache the images directly here because i'm a new user, please see the links below to see how the phone looks like.
i.imgur.com/6kzhlUS.jpg
i.imgur.com/mMDQ6uZ.jpg
Click to expand...
Click to collapse
your fastboot getvar and bootloader revels you have a Sprint phone .. Use Only Sprint Files
http://forum.xda-developers.com/sprint-htc-one
maxwilliam100 said:
I'm not sure if this is sprint, its not branded anywhere(See attached images). The download is completed, Should i proceed from the link i provided? @alray
Excuse i cannot attache the images directly here because i'm a new user, please see the links below to see how the phone looks like.
i.imgur.com/6kzhlUS.jpg
i.imgur.com/mMDQ6uZ.jpg
Click to expand...
Click to collapse
M7_WLS = Sprint = CDMA phone = different partition table = flash a ruu not for sprint and you'll end with a bricked phone.
use a x.xx.651.x ruu for cid SPCS_001 and mid PN0720000 only
http://www.htc1guru.com/dld/ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip/
and do not use windows 8 to flash it or you'll be stuck
use windows 7, MacOs or linux.
alray said:
M7_WLS = Sprint = CDMA phone = different partition table = flash a ruu not for sprint and you'll end with a bricked phone.
use a x.xx.651.x ruu for cid SPCS_001 and mid PN0720000 only
http://www.htc1guru.com/dld/ruu-zip-m7_wls_jb_50_sprint_1-29-651-10_ruu_decrypted-zip/
and do not use windows 8 to flash it or you'll be stuck
use windows 7, MacOs or linux.
Click to expand...
Click to collapse
@maxwilliam100
theirs also
Sprint 4.xx RUU
https://www.androidfilehost.com/?fid=23329332407573774
Sprint 5.xx RUU
http://forum.xda-developers.com/showthread.php?t=2795856
Thank you very much @alray and @clsA
I'm now downloading this ruu and since its at zip then i think i will have to rename the zip file to ruu.zip and flash from
fastboot oem rebootRUU
fastboot flash zip ruu.zip
Click to expand...
Click to collapse
Is there anything else that i should be aware of?
maxwilliam100 said:
Thank you very much @alray and @clsA
I'm now downloading this ruu and since its at zip then i think i will have to rename the zip file to ruu.zip and flash from
Is there anything else that i should be aware of?
Click to expand...
Click to collapse
you may have to do the fastboot flash zip ruu.zip 2 times
clsA said:
you may have to do the fastboot flash zip ruu.zip 2 times
Click to expand...
Click to collapse
Thanks Guys,
After three weeks of googling every available thing and failure, i came here as my last hope... PM random people on the internet and youtube..... without any success
Many thanks to @alray and @clsA
:highfive:
Hi all,
My friend handed me his HTC One M7 the other day and it was looping at the beginning Android / HTC screen from boot, he took the lollipop update but it failed somewhere along the way and this is how it's ended up.
The device is not rooted and is not bootloader unlocked, i've tried to flash a few RUU files to bring it back to life but the vast majority of them only get as far as 1/5 checking header.
I'm more than happy to root the device and install a custom rom but I wasn't sure if it needed to be bootable to do so, afaik the bootloader unlocking doesn't require to have the device on, infact I don't think you need to have the OS to get a custom recovery either? Anyway, i'd like for him to retain his warranty so if there's a way for him to get it back to stock HTC then i'd prefer to do that.
If that's not possible and unlocking the bootloader, installing a custom rom is then I'll do that.
Any help would be greatly appreciated.
Many thanks.
PS: I have had the m7 before but I didn't have it when android 5 was available so i'm a little out of touch with what may go wrong.
dladz said:
Hi all,
My friend handed me his HTC One M7 the other day and it was looping at the beginning Android / HTC screen from boot, he took the lollipop update but it failed somewhere along the way and this is how it's ended up.
The device is not rooted and is not bootloader unlocked, i've tried to flash a few RUU files to bring it back to life but the vast majority of them only get as far as 1/5 checking header.
I'm more than happy to root the device and install a custom rom but I wasn't sure if it needed to be bootable to do so, afaik the bootloader unlocking doesn't require to have the device on, infact I don't think you need to have the OS to get a custom recovery either? Anyway, i'd like for him to retain his warranty so if there's a way for him to get it back to stock HTC then i'd prefer to do that.
If that's not possible and unlocking the bootloader, installing a custom rom is then I'll do that.
Any help would be greatly appreciated.
Many thanks.
PS: I have had the m7 before but I didn't have it when android 5 was available so i'm a little out of touch with what may go wrong.
Click to expand...
Click to collapse
Connect the phone to your computer, Boot it in bootloader mode select "fastboot" mode and make sure "fastboot usb" is shown in red. Open a fastboot command prompt:
Code:
fastboot getvar all
post the output here but make sure to hide the imei and serialno before posting.
Thanks mate I'm in bed at the moment but will do after work tomorrow,, Appreciate your help, im guessing this is to see what firmware is installed? Or hboot? I'll come back tomorrow, Many thanks.
dladz said:
Thanks mate I'm in bed at the moment but will do after work tomorrow,, Appreciate your help, im guessing this is to see what firmware is installed? Or hboot? I'll come back tomorrow, Many thanks.
Click to expand...
Click to collapse
Firmware, hboot, CID, MID, S-ON/S-OFF, M7_UL/M7_U
Checking header 1/5..ill give you a clue...your ruu that you going to flash,it has to match firmware that is on it now...as you are s-on,you cant change firmware.so,try with other ruu's,some that maches firmware number..not older,not newer.
And like others said,give them "getvar all" info.
Sent from my HTC One using XDA Free mobile app
Chaps you are both legends, I'm just running round getting ready for work. I'll jump on this when I get home. Appreciate your help. Thanks.
alray said:
Connect the phone to your computer, Boot it in bootloader mode select "fastboot" mode and make sure "fastboot usb" is shown in red. Open a fastboot command prompt:
Code:
fastboot getvar all
post the output here but make sure to hide the imei and serialno before posting.
Click to expand...
Click to collapse
C:\ANDROID SDK\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W909506
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3596mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Here you go mate.
currently downloading this https://www.androidfilehost.com/?fid=95832962473396760 it's for version 6.09.401.11 which was listed.
Unless there's something i'm supposed to do.
dladz said:
C:\ANDROID SDK\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W909506
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3596mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Here you go mate.
currently downloading this https://www.androidfilehost.com/?fid=95832962473396760 it's for version 6.09.401.11 which was listed.
Unless there's something i'm supposed to do.
Click to expand...
Click to collapse
Would recommend to simply flash the latest ruu (7.19.401.2) which will fix and update the phone to the latest version.
Instructions and file here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
alray said:
Would recommend to simply flash the latest ruu (7.19.401.2) which will fix and update the phone to the latest version.
Instructions and file here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
I did actually try that one mate, that's how i got the 1/5 checking headers problem, and it simply doesn't go any further, i'll give it another whirl but as far as i can remember it was that version.
brb after checking.
Actually I didn't flash one of these but the version does ring a bell. Downloading now mate.
The previous one i mentioned i flash via fastboot flash zip but it still loops, 20 mins until that one downloads. Will let you know and thank you by the way.
dladz said:
I did actually try that one mate, that's how i got the 1/5 checking headers problem, and it simply doesn't go any further, i'll give it another whirl but as far as i can remember it was that version.
brb after checking.
Actually I didn't flash one of these but the version does ring a bell. Downloading now mate.
Click to expand...
Click to collapse
Im almost sure you were trying to flash the 4.xx.401.x version not the one I have linked above.
alray said:
Im almost sure you were trying to flash the 4.xx.401.x version not the one I have linked above.
Click to expand...
Click to collapse
I flashed this one https://www.androidfilehost.com/?fid=95832962473396760 which is 6.09.401.11 but it didn't work, not to worry anyway, i'll give the one you linked to a whirl too, just waiting for it to download, 10 mins left.
dladz said:
i'll give the one you linked to a whirl too, just waiting for it to download, 10 mins left.
Click to expand...
Click to collapse
I'm 100% confident it will work. Just make sure to use the fastboot version linked in that thread which is a version made by HTC. Only this version of fastboot will work to flash this ruu since the "normal" fastboot can't handle the file size of that ruu. Also make sure your bootloader is locked or relocked.
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
alray said:
I'm 100% confident it will work. Just make sure to use the fastboot version linked in that thread which is a version made by HTC. Only this version of fastboot will work to flash this ruu since the "normal" fastboot can't handle the file size of that ruu. Also make sure your bootloader is locked or relocked.
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
Click to expand...
Click to collapse
Oh really? Why didn't i know this !? See I've been gone from HTC for far too long, should be getting the M9 soon though. One of my contracts expires soon, i've got a few, need to check on them. You thinking of getting the M9 ? Think Samsung has made a mistake going with the Exynos.
Ok it's downloaded, i'll grab that fastboot and give it a whirl. Fingers crossed.
alray said:
I'm 100% confident it will work. Just make sure to use the fastboot version linked in that thread which is a version made by HTC. Only this version of fastboot will work to flash this ruu since the "normal" fastboot can't handle the file size of that ruu. Also make sure your bootloader is locked or relocked.
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot reboot
Click to expand...
Click to collapse
Ok i got this
C:\HTC Fastboot>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 44(ms)
C:\HTC Fastboot>fastboot flash zip PN07IMG_M7_U_L50_SENSE60_MR_HTC_Europe_7.19.4
01.102_Radio_4T.35.3218.16_10.33Q.1718.01D_release_421804_signed.zip
sending 'zip'... (43287 KB) OKAY
sending time = 2.844 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 9(s)
C:\HTC Fastboot>
Rebooting.
EDIT: Bootloop mate.
dladz said:
Oh really? Why didn't i know this !? See I've been gone from HTC for far too long, should be getting the M9 soon though. One of my contracts expires soon, i've got a few, need to check on them. You thinking of getting the M9 ? Think Samsung has made a mistake going with the Exynos.
Click to expand...
Click to collapse
I'll might grab the M9 later this year when the price will drop a bit. I'm still satisfied with my M7 and doesn't feel like I need something more.
Ok it's downloaded, i'll grab that fastboot and give it a whirl. Fingers crossed
Click to expand...
Click to collapse
Dont forget you'll need the dll files in the same folder where you have htc's fastboot and the ruu. You can simply replace fastboot.exe with htc's fastboot in your sdk folder were the required dll files are
---------- Post added at 12:16 PM ---------- Previous post was at 12:14 PM ----------
dladz said:
Ok i got this
C:\HTC Fastboot>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 44(ms)
C:\HTC Fastboot>fastboot flash zip PN07IMG_M7_U_L50_SENSE60_MR_HTC_Europe_7.19.4
01.102_Radio_4T.35.3218.16_10.33Q.1718.01D_release_421804_signed.zip
sending 'zip'... (43287 KB) OKAY
sending time = 2.844 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAIL41 model id check fail
FAILED (remote: 41 model id check fail)
Execution time is 9(s)
C:\HTC Fastboot>
Click to expand...
Click to collapse
you have downloaded the 7.19.401.102 version. You have to use the 7.19.401.2 version hence why the "check ID fail". .102 version is for M7_U and .2 version is for M7_UL (the one you have).
alray said:
Would recommend to simply flash the latest ruu (7.19.401.2)
Click to expand...
Click to collapse
alray said:
you have downloaded the 7.19.401.102 version. You have to use the 7.19.401.2 version hence why the "check ID fail". .102 version is for M7_U and .2 version is for M7_UL (the one you have).
Click to expand...
Click to collapse
Just copied the HTC fastboot into the SDK platforms and tools folder, reflashing now.
dladz said:
Just copied the HTC fastboot into the SDK platforms and tools folder, reflashing now.
Click to expand...
Click to collapse
read my post above you are flashing the wrong ruu. You need 4.19.401.2 not 4.19.401.102
alray said:
you have downloaded the 7.19.401.102 version. You have to use the 7.19.401.2 version hence why the "check ID fail". .102 version is for M7_U and .2 version is for M7_UL (the one you have).
Click to expand...
Click to collapse
Ah, idiot. Sorry
Couldn't see a european one though? This device is unlocked, wouldn't it have the providers software on otherwise?
Ok downloading, sorry mate, my eyes are failing me, getting old.
Ok so I think it's all done mate, looks like it's going to load up, I mean the script has finished running but the green bar is still onscreen.
[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.