Hey guys.
I was wondering if anyone could take some time and help figure out what's wrong with my Htc one!
So my new phone broke and so i went back to my One that i haven't used in ages.
Anyways it was alredy rooted with S-Off and first thing i was trying todo was to install TWRP and a new rom.
After i installed twrp and rebooted the phone and upon start i sent me directly in to the "power off + Volume down" menu and i tried to enter Recovery.
All i get is "Active cmdline overflow! (2169 Bytes)" then nothing more.
So i tried some fastboot commands and this is what i get from
Fastboot devices ÒÀü«/ë¥-1ý}ËÙ fastboot
I reckoning something is wrong here because the name has never shown like this before.
If i try adb devices i get nothing.
So i started to belive that maybe the cable was ****ed and now i almost tried 7 diffrent cables and all of them is giving me the same message.
I tried a diffrent computer, i tried in windows 10 and now im in Ubuntu 16.04 and still cant get adb to show the device.
This is what i get from "fastboot getvar all"
HTML:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ҟ���/륑-1�}��
(bootloader) imei: ****************** <---------- CHANGED THIS ONE TO STARS!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Anyway the (bootloader) serialno: ҟ���/륑-1�}�� and (bootloader) modelid: � dosent look good right ?
Well i did follow this guide "https://forum.xda-developers.com/showthread.php?t=2739126" and i can install twrp and everything but i cant enter it and the adb commands further in the guide dosent work because adb wont list the phone.
I also tried:
HTML:
sudo fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.039s]
finished. total time: 0.039s
sudo fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1514139648 bytes
sending 'zip' (501 KB)...
OKAY [ 0.243s]
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.644s
And there's something wrong with the mode id
What is my option, is the phone ****ed or is it possible to fix it ?
Thanks in advanced!
Have you tried to flash stock recovery or RUU?
JB_ said:
Hey guys.
I was wondering if anyone could take some time and help figure out what's wrong with my Htc one!
So my new phone broke and so i went back to my One that i haven't used in ages.
Anyways it was alredy rooted with S-Off and first thing i was trying todo was to install TWRP and a new rom.
After i installed twrp and rebooted the phone and upon start i sent me directly in to the "power off + Volume down" menu and i tried to enter Recovery.
All i get is "Active cmdline overflow! (2169 Bytes)" then nothing more.
So i tried some fastboot commands and this is what i get from
Fastboot devices ÒÀü«/ë¥-1ý}ËÙ fastboot
I reckoning something is wrong here because the name has never shown like this before.
If i try adb devices i get nothing.
So i started to belive that maybe the cable was ****ed and now i almost tried 7 diffrent cables and all of them is giving me the same message.
I tried a diffrent computer, i tried in windows 10 and now im in Ubuntu 16.04 and still cant get adb to show the device.
This is what i get from "fastboot getvar all"
HTML:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ҟ���/륑-1�}��
(bootloader) imei: ****************** <---------- CHANGED THIS ONE TO STARS!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Anyway the (bootloader) serialno: ҟ���/륑-1�}�� and (bootloader) modelid: � dosent look good right ?
Well i did follow this guide "https://forum.xda-developers.com/showthread.php?t=2739126" and i can install twrp and everything but i cant enter it and the adb commands further in the guide dosent work because adb wont list the phone.
I also tried:
HTML:
sudo fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.039s]
finished. total time: 0.039s
sudo fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1514139648 bytes
sending 'zip' (501 KB)...
OKAY [ 0.243s]
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.644s
And there's something wrong with the mode id
What is my option, is the phone ****ed or is it possible to fix it ?
Thanks in advanced!
Click to expand...
Click to collapse
What roms did you flashed (post a link) ? Active cmdline overflow is caused by a corrupted misc partition, most of the time because the user flashed a rom for another device than the m7. During the installation, the updater script of that rom flash images to wrong partitions (since all phone models have a different partition layout). Some partitions are unique to each m7 and if they get corrupted, a simple ruu flash will not solve your problem.
Your adb problem is most likely a driver issue. Make sure you have the latest drivers from HTC (those that are bundled with HTCSync) and try again. The only way out of this is to make p19 healthy again by following that guide you linked (if it was caused by an incompatible rom flash...waiting for your link).
Btw do not attempt to downgrade to hboot 1.44 if you're using windows 8/10 or you'll also loose fastboot connectivity.
alray said:
What roms did you flashed (post a link) ? Active cmdline overflow is caused by a corrupted misc partition, most of the time because the user flashed a rom for another device than the m7. During the installation, the updater script of that rom flash images to wrong partitions (since all phone models have a different partition layout). Some partitions are unique to each m7 and if they get corrupted, a simple ruu flash will not solve your problem.
Your adb problem is most likely a driver issue. Make sure you have the latest drivers from HTC (those that are bundled with HTCSync) and try again. The only way out of this is to make p19 healthy again by following that guide you linked (if it was caused by an incompatible rom flash...waiting for your link).
Btw do not attempt to downgrade to hboot 1.44 if you're using windows 8/10 or you'll also loose fastboot connectivity.
Click to expand...
Click to collapse
Well as I want to remember it I don't think I have flashed a rom yet, I never got that far I just tried to flash twrp 2.8.4.0.
Do i even need drivers in Ubuntu ? I was under the influence that I didn't need any.
JIMSHERIKO said:
Have you tried to flash stock recovery or RUU?
Click to expand...
Click to collapse
Well if I understand it right when I try to flash a RUU it just says unknown modelid and I think because it's corrupted or something. :/
JB_ said:
Do i even need drivers in Ubuntu ? I was under the influence that I didn't need any.
Click to expand...
Click to collapse
No you don't, only on windows, sorry. ADB should work fine from twrp and no drivers required on ubuntu, adb will not work from the bootloader.
alray said:
No you don't, only on windows, sorry. ADB should work fine from twrp and no drivers required on ubuntu, adb will not work from the bootloader.
Click to expand...
Click to collapse
Ah so i need to get TWRP up and running for adb to work then.
Well looks like i got my awnser then. Thank you for your time!
Related
So I have done this so many times in the past playing with my HTC AMAZE 4G, to which i thought having some fun with my HTC ONE would be easy enough. But without a SD card.. i feel SOL.
I have been scouring the forums for possible fixes to no solution...
Currently I have the phone unlocked with "tampered" on the top.
My boot loader reads:
M7_UL PVT SHIP S-ON
HBOOT-1.56.0000
RADIO-4A.24.3263.09
OpenDSP-v32.120.274.0909
OS-4.19.531.10
Feb 3 2014,18:42:45.0
For all that is holy, i cannot get this thing to recognize ADB in console. I have been using Hasoon2000's AIO tool, which i used in the past on this phone and my priors.. but when I was in TWRP accidentally deleted my OS..? Everything I have tried has failed.
I am running Windows 8.1 which shouldn't be an issue with my Hboot version, so I am wondering what possible solutions there may be to get this fixed and finally get Cyanogen on this phone!
I have tried using the HTC recovery to go back to stock but i get errors when using the .zip i found which was supposed to be the RUU from the .exe HTC has out and yes i re-locked the phone for this. In terms of anything i think if i were able to get adb working i might be able to send CM11 to my phone directory and "recover" to that?
Thanks in advance!
EDIT: When i tried using the RUU zip i get this in my cmd.
sending 'zip' (227216 KB)...
OKAY [ 12.212s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 37.092s
I also ran Getvar and got this... Some people said it would help to have this info on some other threads....
C:\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4161mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
mtywe said:
EDIT: When i tried using the RUU zip i get this in my cmd.
sending 'zip' (227216 KB)...
OKAY [ 12.212s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 37.092s
Click to expand...
Click to collapse
That's not an RUU, and there is no ruu 4.19.531.10 or higher as far as i know.
so do this: http://forum.xda-developers.com/showthread.php?t=2228274&page=3
mtywe said:
So I have done this so many times in the past playing with my HTC AMAZE 4G, to which i thought having some fun with my HTC ONE would be easy enough. But without a SD card.. i feel SOL.
I have been scouring the forums for possible fixes to no solution...
Currently I have the phone unlocked with "tampered" on the top.
My boot loader reads:
M7_UL PVT SHIP S-ON
HBOOT-1.56.0000
RADIO-4A.24.3263.09
OpenDSP-v32.120.274.0909
OS-4.19.531.10
Feb 3 2014,18:42:45.0
For all that is holy, i cannot get this thing to recognize ADB in console. I have been using Hasoon2000's AIO tool, which i used in the past on this phone and my priors.. but when I was in TWRP accidentally deleted my OS..? Everything I have tried has failed.
I am running Windows 8.1 which shouldn't be an issue with my Hboot version, so I am wondering what possible solutions there may be to get this fixed and finally get Cyanogen on this phone!
I have tried using the HTC recovery to go back to stock but i get errors when using the .zip i found which was supposed to be the RUU from the .exe HTC has out and yes i re-locked the phone for this. In terms of anything i think if i were able to get adb working i might be able to send CM11 to my phone directory and "recover" to that?
Thanks in advance!
EDIT: When i tried using the RUU zip i get this in my cmd.
sending 'zip' (227216 KB)...
OKAY [ 12.212s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 37.092s
I also ran Getvar and got this... Some people said it would help to have this info on some other threads....
C:\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4161mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
Boot your phone in custom recovery
adb push name_of_rom.zip /sdcard/
Wait for the file to transfer (5-10 min)
Install your rom
Sent from my HTC One using XDA Free mobile app
alray said:
Boot your phone in custom recovery
adb push name_of_rom.zip /sdcard/
Wait for the file to transfer (5-10 min)
Install your rom
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
so i run adb push and it shows the time and bytes of the file... but does not show up in my /sdcard/
i also tried sideloading... and got this error, once it finishes loading it over:E:Error executing updator binary in zip '/data/ updating partition details
i think i ran into the same issue two years back when I tried getting pure CM on my last phone...
any ideas?
mtywe said:
i also tried sideloading... and got this error, once it finishes loading it over:E:Error executing updator binary in zip '/data/ updating partition details
i think i ran into the same issue two years back when I tried getting pure CM on my last phone...
any ideas?
Click to expand...
Click to collapse
what is your twrp version?
you might also read this: http://wiki.cyanogenmod.org/w/Install_CM_for_m7
alray said:
what is your twrp version?
you might also read this:
Click to expand...
Click to collapse
OLD.... updating to the newest version now.
alray said:
what is your twrp version?
you might also read this: ]
Click to expand...
Click to collapse
Looks like we have a success!
I tried using the sideloader first which failed but adb push did the trick.
Thanks for the help!
mtywe said:
Looks like we have a success!
I tried using the sideloader first which failed but adb push did the trick.
Thanks for the help!
Click to expand...
Click to collapse
:good:
can you edit your thread title to add [Solved] ?
Im without Os.
(bootloader) version: 0.5
(bootloader) version-bootloader:
(bootloader) version-baseband: 4
(bootloader) version-cpld: None
(bootloader) version-microp: Non
(bootloader) version-main: 5.16.
(bootloader) version-misc: PVT S
(bootloader) serialno: SH36LW901
(bootloader) imei: 3578640560898
(bootloader) meid: 0000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-806
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: goo
(bootloader) battery-voltage: 42
(bootloader) partition-layout: G
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.103s
I tried everything. (i think so)
C:\Users\Orbeet\Desktop\HTC\adb>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1206124 KB)...
OKAY [ 56.016s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 56.282s
Or
C:\Users\Orbeet\Desktop\HTC\adb>fastboot flash zip Guru_Reset_M7_2.24.161.1.zip
target reported max download size of 1515692032 bytes
sending 'zip' (1128558 KB)...
OKAY [ 52.967s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 69.887s
Please Help
orbeet said:
Im without Os.
(bootloader) version: 0.5
(bootloader) version-bootloader:
(bootloader) version-baseband: 4
(bootloader) version-cpld: None
(bootloader) version-microp: Non
(bootloader) version-main: 5.16.
(bootloader) version-misc: PVT S
(bootloader) meid: 0000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-806
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: goo
(bootloader) battery-voltage: 42
(bootloader) partition-layout: G
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.103s
I tried everything. (i think so)
C:\Users\Orbeet\Desktop\HTC\adb>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1206124 KB)...
OKAY [ 56.016s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 56.282s
Or
C:\Users\Orbeet\Desktop\HTC\adb>fastboot flash zip Guru_Reset_M7_2.24.161.1.zip
target reported max download size of 1515692032 bytes
sending 'zip' (1128558 KB)...
OKAY [ 52.967s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 69.887s
Please Help
Click to expand...
Click to collapse
remove your IMEI and serialno from your getvar all.
repost your getvar all correctly so we can see all the info: S-???? 5.16.???????
what firmware.zip are you using (link) and why? you don't need to flash firmware to get an OS on your phone...
fastboot flash zip Guru_Reset_M7_2.24.161.1.zip ---> this can not be flashed this way, must be flashed from a custom recovery, however it also looks like its not the right version. You getvar: 5.16.??? ---> and you are trying to flash a 2.24
You'll probably have to flash a custom rom
orbeet said:
Im without Os.
Please Help
Click to expand...
Click to collapse
Remove the imei and serialno from your getvar all. Also, you have cutoff some important information on the getvar all, i.e., version bootloader, version main. Why don't you think you have an OS? What was the firmware version you were trying to install?
I think your are trying to install the older versions of your phone and that is why it is failing. You are S-ON so you can only install the same or higher versions of OS and firmware.
alray said:
remove your IMEI and serialno from your getvar all.
repost your getvar all correctly so we can see all the info: S-???? 5.16.???????
what firmware.zip are you using (link) and why? you don't need to flash firmware to get an OS on your phone...
fastboot flash zip Guru_Reset_M7_2.24.161.1.zip ---> this can not be flashed this way, must be flashed from a custom recovery, however it also looks like its not the right version. You getvar: 5.16.??? ---> and you are trying to flash a 2.24
You'll probably have to flash a custom rom
Click to expand...
Click to collapse
1. How to do point 1? (remove IMEI and serialno) ?? i dont get it?
2. I dont know how to do this correctly
3. I tried lots of and no one match (around 5) i had searched "radio 4T.27.3218.14"
4. i can not enter my phone from windows. Win7 see only removable disk but its blank.
Photo
orbeet said:
1. How to do point 1? (remove IMEI and serialno) ?? i dont get it? Go to your first post and choose Edit then remove the imei and serial number
2. I dont know how to do this correctly In the command window with your fastboot getvar all... choose select all then copy
3. I tried lots of and no one match (around 5) i had searched "radio 4T.27.3218.14" Radio has nothing to do with it your OS is listed in the screen shot you posted
4. i can not enter my phone from windows. Win7 see only removable disk but its blank. You can only access your phone in windows when it's booted to the OS... you don't have (you say)
Click to expand...
Click to collapse
Try these instructions
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
Guru_Reset_M7_5.11.401.10-TeHashX.zip
http://www.androidfilehost.com/?fid=23501681358543706
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
one more image.
Iv done everything U say and nothing.
??!
Is this all?
People, please help me.
orbeet said:
1. How to do point 1? (remove IMEI and serialno) ?? i dont get it?
2. I dont know how to do this correctly
3. I tried lots of and no one match (around 5) i had searched "radio 4T.27.3218.14"
4. i can not enter my phone from windows. Win7 see only removable disk but its blank.
Click to expand...
Click to collapse
edit your 1st post and remove the EMEI line and the SERIALNO line, these are sensitive number you don't want to share
repost it again and make sure to copy/paste all the content
(bootloader) version: 0.5
(bootloader) version-bootloader: ???????????
(bootloader) version-baseband: 4 ?????????????
(bootloader) version-cpld: None
(bootloader) version-microp: Non
(bootloader) version-main: 5.16.???????????
(bootloader) version-misc: PVT S????????????
(bootloader) serialno: remove!
(bootloader) imei: remove!
(bootloader) meid: 0000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-806
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: goo
(bootloader) battery-voltage: 42
(bootloader) partition-layout: G
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.103s
Click to expand...
Click to collapse
if you want pple to reply to your post, then quote them or they will not be notified of your post.
try adb push instead of adb sideload
Code:
adb push Guru_Reset_M7_5.11.401.10-TeHashX.zip /sdcard/
then when the file is transferred (wait 5-10 min) install from twrp
orbeet said:
Is this all?
People, please help me.
Click to expand...
Click to collapse
First, hard reboot pressing the power and volume down buttons until you see the bootloader and then scroll through the options to hit "REBOOT" not "REBOOT BOOTLOADER" you'll probably boot into your rom after a couple of minutes but thats not a fix, it's just a way to use your phone for now.
Having no OS means you probably tried to flash a custom firmware or downgrade your FW but you can only do that while S-OFF
OR you where using a different kind of recovery like multirom or an old clockworkmod recovery or something, give us a little bit more info on what you where doing before you "lost" your OS and what recovery, what ROM and what you where hoping to accomplish just so we can see what went wrong. It's best when you need to do something to read the guide your using from top to bottom twice, most guides go through multiple posts not just the first to point out areas you might run into problems and things to avoid. I recently had a similar problem trying to remove multirom and reverting to stock, I was flashing the 1.57 FW with TWRP but after flashing ARHD 71.1 it still gave me "no OS installed", I reverted to stock using the RUU.zip install method with all partitions and FW and ROM to complete stock.
As the title says, I just bircked my M7... the thing is, that I tried to update TWRP recovery, but the thing is, that my phone is a m7ul, and I tried the twrp for m7, now i can only enter bootloader, but i can't do anything, i can't go to rebootRUU, i can't install any other recovery.
when I put:
fastboot reboot recovery - it just stays there, like stuck
fastboot getvar all - I get all this info
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXX (actual SN masked)
(bootloader) imei: XXXXXXXXXXXXX (actual IMEI masked)
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3943mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
fastboot flash recovery openrecovery-twrp-2.8.0.2-m7ul.img - it says:
Code:
target reported max download size of 1526722560 bytes
sending 'recovery' (11610 KB)...
OKAY [ 1.688s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.858s
and then it gets stuck...
What can I do??
Did you erase cache after the recovery flash?
And your phone is a great candidate for rumrunner s-off on hboot 1.55
ZeroCool11 said:
As the title says, I just bircked my M7... the thing is, that I tried to update TWRP recovery, but the thing is, that my phone is a m7ul, and I tried the twrp for m7, now i can only enter bootloader, but i can't do anything, i can't go to rebootRUU, i can't install any other recovery.
when I put:
fastboot reboot recovery - it just stays there, like stuck
fastboot getvar all - I get all this info
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXX (actual SN masked)
(bootloader) imei: XXXXXXXXXXXXX (actual IMEI masked)
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3943mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
fastboot flash recovery openrecovery-twrp-2.8.0.2-m7ul.img - it says:
Code:
target reported max download size of 1526722560 bytes
sending 'recovery' (11610 KB)...
OKAY [ 1.688s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.858s
and then it gets stuck...
What can I do??
Click to expand...
Click to collapse
Code:
fastboot reboot recovery
This command doesn't exist so its normal that its not doing anything.
update your android sdk and your HTC drivers to latest version and flash twrp 2.6.3.3, check MD5 on your downloads.
Btw why updating the recovery? Recovery doesn't need to be updated, newer recovery doesn't mean better. Unless the rom you want to flash absolutely need a specific version (mentioned in the rom OP), stay with 2.6.3.3, its the most stable version.
Btw twrp for M7 is what you need for your M7_UL. "M7" twrp are compatible for M7_UL and M7_U
I tried to install TWRP 2.6.3.3 and it shows this:
< waiting for device >
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.218s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.388s
I Tried Rummrunner and it doesn't work, i can't get to RebootRUU... or Recovery... i can only go to Bootloader... and that's all...
Please wait....
..........
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Press ENTER to exit
ZeroCool11 said:
I Tried Rummrunner and it doesn't work, i can't get to RebootRUU... or Recovery... i can only go to Bootloader... and that's all...
Please wait....
..........
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Press ENTER to exit
Click to expand...
Click to collapse
I think you need to start over
In bootloader / fastboot usb / use fastboot oem lock
then flash this RUU from your PC
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
When you phone boots up skip all the setup and go to settings / developer options / usb debugging is checked
then settings / Power / fastboot at the bottom is unchecked
Now try adb devices / you see you phone serial number / if no fix your drivers / install htc sync the in add remove programs, uninstall htc sync / this will leave just the driver installed.
after adb works on the phone in android do / adb reboot-bootloader
now fastboot devices / returns the serial number
now unlock bootloader / flash TWRP 2.6.3.3 with
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
You should now have working custom recovery and can continue to flash a rom with root and use rumrunner to s-off
Hello, sorry, i was AFK for the weekend , about that, when I Put "fastboot oem lock" it says OK and then it gets stuck, then, after I reboot it says that is unlocked...
WHAT ruu should i flash to get back to stock, tried flashing roms but i get stuck in a bootloop the htc screen or it reboots to bootloader? this is my fastboot getvar all info.
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA348S906097
(bootloader) imei: 99xxxxxxxxxxxxx
(bootloader) meid: 99xxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3837mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-371c4f408e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.376s
Dpimpim said:
WHAT ruu should i flash to get back to stock, tried flashing roms but i get stuck in a bootloop the htc screen or it reboots to bootloader? this is my fastboot getvar all info.
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA348S906097
(bootloader) imei: 99xxxxxxxxxxxxx
(bootloader) meid: 99xxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3837mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-371c4f408e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.376s
Click to expand...
Click to collapse
M7_WLS = Sprint so use a sprint RUU
your bootloop issue is probably because you are trying to flash GSM rom not compatible with the sprint variant.
alray said:
M7_WLS = Sprint so use a sprint RUU with CWS__001 cid
your bootloop issue is probably because you are trying to flash GSM rom not compatible with the sprint variant.
Click to expand...
Click to collapse
any link to get the ruu? will be appreciated
Dpimpim said:
any link to get the ruu? will be appreciated
Click to expand...
Click to collapse
htc1guru.com but this site is currently down
(link removed)
save it in the same folder where you have fastboot and adb on your computer, rename it ruu "ruu.zip" to make it easier in the command prompt
open a command prompt from that folder (or cd to that folder)
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
Do not do what said above if your computer is running windows 8. Must be done using Win7, Linux or MacOS.
alray said:
htc1guru.com but this site is currently down
so you can use that one posted by nkk71 on androidfilhost.com
save it in the same folder where you have fastboot and adb on your computer, rename it ruu "ruu.zip" to make it easier in the command prompt
open a command prompt from that folder (or cd to that folder)
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
Do not do what said above if your computer is running windows 8. Must be done using Win7, Linux or MacOS.
Click to expand...
Click to collapse
should i relock bootloader prior to that?
Dpimpim said:
should i relock bootloader prior to that?
Click to expand...
Click to collapse
Do not relock the bootloader, your phone is s-off so relocking the bootloader is not needed. Better to leave it unlocked.
alray said:
Do not relock the bootloader, your phone is s-off so relocking the bootloader is not needed. Better to leave it unlocked.
Click to expand...
Click to collapse
just downloaded the ruu file. will get back at you with how it goes
alray said:
Do not relock the bootloader, your phone is s-off so relocking the bootloader is not needed. Better to leave it unlocked.
Click to expand...
Click to collapse
C:\adb>fastboot flash zip ruu.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1033216 KB)...
OKAY [ 51.189s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 58.905s
the flashing failed
Dpimpim said:
C:\adb>fastboot flash zip ruu.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1033216 KB)...
OKAY [ 51.189s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 58.905s
the flashing failed
Click to expand...
Click to collapse
sorry my bad, linked the wrong ruu
this one should work https://www.androidfilehost.com/?fid=23203820527945356
alray said:
sorry my bad, linked the wrong ruu
this one should work https://www.androidfilehost.com/?fid=23203820527945356
Click to expand...
Click to collapse
haha! downloading, will get back at you. thanks a bunch
alray said:
sorry my bad, linked the wrong ruu
the download worked. i'm now on stock rom. thanks
Click to expand...
Click to collapse
Okay lots of issues hopefully one easy fix,
I have had a HOM2 given to me to fix for my friend so just want it back to stock , it has no radios it mentions invalid_ver_* , same for another option, the bootloader is LOCKED here is my getvar info
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH466WR01102
(bootloader) imei: 35***********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
, its bootlooping into bootloader, so my first thought was unlock bootloader flash recovery and side load a rom, play with radios and such after, but trying to unlock the bootloader doesn't work I've tried HTC dev twice to check the unlock code but it pushes it to the device and claims it was successful I get this;
**UNLOCK CODE***
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.109s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.125ss
tried different USB cables and ports but every time I try I don't get the unlock splash screen asking me to unlock, so I went through the forums and tried a few things found that clearing cache or and data gives me
**CLEAR CACHE***
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 5.038ss
I tried flashing recovery (just for kicks) I get
***SEND RECOVERY***
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery-twrp-2.8.5.0.img
sending 'recovery' (11796 KB)...
OKAY [ 10.472s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 11.316sss
Which I guess is to be expected,
I then found an RUU for the device and was thankful the unlocking didn't work so I was still locked, but every one I try to download is corrupt? Anybody have a working link for a UK ee (orange) radios and firmware? And do I have the right idea with this, download, rename, chuck it on an sdcard and bootloader should find it automatically?
Thanks for any advice
martipello86 said:
Okay lots of issues hopefully one easy fix,
I have had a HOM2 given to me to fix for my friend so just want it back to stock , it has no radios it mentions invalid_ver_* , same for another option, the bootloader is LOCKED
Click to expand...
Click to collapse
Since the phone was given to you, Are you using an original HTC cable???? you need that for any flashing to work.
Yes I have an original HTC cable,
martipello86 said:
Yes I have an original HTC cable,
Click to expand...
Click to collapse
kativiti said:
Since the phone was given to you, Are you using an original HTC cable???? you need that for any flashing to work.
Click to expand...
Click to collapse
I have the original cable, just does not want to work, and the RUU says its corrupt when I try to put it on the SD card
kativiti said:
Since the phone was given to you, Are you using an original HTC cable???? you need that for any flashing to work.
Click to expand...
Click to collapse
i found a way to get the ruu onto the sdcard by uploading the file to dropbox and redownloading it straight to the memory card then stuck it in the phone tried an orange ruu it gets half way through updating then stops and spits out a message to say its not the right cid so i got the wwe version that looks like itll work but then fails and tells me 'MAIN VERSION IS OLDER' update failed.
ANY IDEAS WELCOME!!!!!!!