Hello, I have a verizon htc one m7. I am rooted and s-off.
1: getvar info
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.066s
2: In the the bootloader screen if I choose recovery the phone tries to load twrp screen goes to entering recovery goes black then the entering recovery screen comes back up and stays until I power down:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3: I have tried fastboot, flashify, rom toolbox pro and linux to flash twrp images. every one of them does so without error, yet I can not get into twrp. The md5 on every file I have tried to flash checked out ok.
4: I installed the ruu from dottat kitkat 4.4.2 and 4.4.3 and installed the ruu version of twrp 2.7.0.8 and 2.7.1.12 and still recovery does not load. This is after installing an ruu and wipes the phone completely.
5:I have tried everything that has been suggested including running the commands from a linux terminal.
If anybody knows how to fix this please help!
vaping redhead said:
Hello, I have a verizon htc one m7. I am rooted and s-off.
1: getvar info
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3910mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.066s
2: In the the bootloader screen if I choose recovery the phone tries to load twrp screen goes to entering recovery goes black then the entering recovery screen comes back up and stays until I power down:
3: I have tried fastboot, flashify, rom toolbox pro and linux to flash twrp images. every one of them does so without error, yet I can not get into twrp. The md5 on every file I have tried to flash checked out ok.
4: I installed the ruu from dottat kitkat 4.4.2 and 4.4.3 and installed the ruu version of twrp 2.7.0.8 and 2.7.1.12 and still recovery does not load. This is after installing an ruu and wipes the phone completely.
5:I have tried everything that has been suggested including running the commands from a linux terminal.
If anybody knows how to fix this please help!
Click to expand...
Click to collapse
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
jpradley said:
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
Click to expand...
Click to collapse
they are in zip format and can be downloaded from dottat thread in the developer section. you use the command fasboot flash zip "filename"
http://forum.xda-developers.com/verizon-htc-one/development/ruu-vzw-kitkat4-4-3-sense-6-s-off-t2867643
http://forum.xda-developers.com/showthread.php?t=2765784
vaping redhead said:
they are in zip format and can be downloaded from dottat thread in the developer section. you use the command fasboot flash zip "filename"]
Click to expand...
Click to collapse
OK, thanks.
But what's wrong with the file format that most everyone uses for a recovery installation, which isn't a *zip file, but a *img file?
jpradley said:
OK, thanks.
But what's wrong with the file format that most everyone uses for a recovery installation, which isn't a *zip file, but a *img file?
Click to expand...
Click to collapse
It is my understanding that img files can be flashed directly from fastboot or flashify etc. the zip file contains the image file and also a txt file and can only be flashed while your phone is in ruu mode "fastboot oem rebootRUU"
since there is 2 files that it why it is zipped. the txt file contained in there is the istructions that tell the rom update utility how to flash the enclosed recovery image file.
jpradley said:
Educate me: what's an RUU version of TWRP, as opposed to any other kind?
Which precise filename(s) of TWRP are you trying, where are you getting them?
Click to expand...
Click to collapse
Fastboot erase cache
Then flash your recovery again and see what you have.
dottat said:
Fastboot erase cache
Then flash your recovery again and see what you have.
Click to expand...
Click to collapse
I have tried that command, it does not solve recovery not loading. Trust me I have tried every suggestion I can find on the internet and nothing solves this. I am hoping someone out there has knowledge of exaclty how the recovery partition works because at this point it would appear that the recovery partition on my phone is either not being written to or is corrupted.
vaping redhead said:
I have tried that command, it does not solve recovery not loading. Trust me I have tried every suggestion I can find on the internet and nothing solves this. I am hoping someone out there has knowledge of exaclty how the recovery partition works because at this point it would appear that the recovery partition on my phone is either not being written to or is corrupted.
Click to expand...
Click to collapse
When you flash the ruu mode twrp put a -w on the end of the command.
dottat said:
When you flash the ruu mode twrp put a -w on the end of the command.
Click to expand...
Click to collapse
I will try. Here are the results
c:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
c:\adb>fastboot flash zip M7_RUU_TWRP.zip -w
target reported max download size of 1514139648 bytes
sending 'zip' (9360 KB)...
OKAY [ 1.059s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,10
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,30
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,61
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,87
(bootloader) [RUU]UZ,recovery,98
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
OKAY [ 3.179s]
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 4.250s
Revovery still does not load.
vaping redhead said:
I will try. Here are the results
c:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
c:\adb>fastboot flash zip M7_RUU_TWRP.zip -w
target reported max download size of 1514139648 bytes
sending 'zip' (9360 KB)...
OKAY [ 1.059s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,10
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,30
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,61
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,87
(bootloader) [RUU]UZ,recovery,98
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
OKAY [ 3.179s]
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 4.250s
Revovery still does not load.
Click to expand...
Click to collapse
Failed (remote not allowed)
Is a sure sign that something isn't set up right for flashing to the device.
It will never work if that is the result in terminal.
Are you using Usb 2.0 and the original data cable that is meant for the device?
I think you probably never successfully flashed any recovery.
I would advise trying a cable meant for this device.
santod040 said:
Failed (remote not allowed)
Is a sure sign that something isn't set up right for flashing to the device.
It will never work if that is the result in terminal.
Are you using Usb 2.0 and the original data cable that is meant for the device?
I think you probably never successfully flashed any recovery.
I would advise trying a cable meant for this device.
Click to expand...
Click to collapse
I am using the htc cable that came with the phone. I will double check that I am using USB 2.0 and try a different cable.
I also noticed wihen flashing with rom toolbox pro is says successful yet also says #error: cannot locate recovery partition
Is it possible my recovery partitiion is not there?
I just tried several cables including the the one from htc. I also made sure I was using a usb 2.0 port. I still get the failed(remote not allowed)
Thank you for the help btw.
Hi, I think I have figured this one out. I changed my phone from blue to red. Verizon only offers silver or blue. Anyway I thought I might have damaged my motherboard, So I bought a silver verizon htc one off ebay with a cracked screen. (easy fix). So I swapped the hardware from the silver to my red and with a new board in the red shell twrp does not load. However my old board wich twrp would not load on is now in the silver shell and twrp now loads. Bottom line the red shell is the problem.
vaping redhead said:
Hi, I think I have figured this one out. I changed my phone from blue to red. Verizon only offers silver or blue. Anyway I thought I might have damaged my motherboard, So I bought a silver verizon htc one off ebay with a cracked screen. (easy fix). So I swapped the hardware from the silver to my red and with a new board in the red shell twrp does not load. However my old board wich twrp would not load on is now in the silver shell and twrp now loads. Bottom line the red shell is the problem.
Click to expand...
Click to collapse
Update. The red shell is 100% to blame for recovery software not loading. I did some more tinkering with two m7 motherboards and in a stock verizon silver shell twrp loads. Both board when in the red shell, twrp does not load.
If anyone out there was thinking of converting their blue or silver verizon m7 to a different color. Be warned that your recovery software will probably not load once you transfer the hardware over to the new shell.
I guess if I want a red htc one that twrp works on, I have to get a m8
vaping redhead said:
Update. The red shell is 100% to blame for recovery software not loading. I did some more tinkering with two m7 motherboards and in a stock verizon silver shell twrp loads. Both board when in the red shell, twrp does not load.
If anyone out there was thinking of converting their blue or silver verizon m7 to a different color. Be warned that your recovery software will probably not load once you transfer the hardware over to the new shell.
I guess if I want a red htc one that twrp works on, I have to get a m8
Click to expand...
Click to collapse
Or just.... Paint it with a good quality modeling paint (like you buy for model cars, boats, etc). It is durable and lasts if you know how to coat it correctly.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Doesn't seem to me that you solved the initial problem, just found a work around for it. I have the same problem with my phone not accepting the stock recovery for what ever reason. It will, however, accept the TWRP recovery, but this doesn't do me any good wrt warranty returns. before I S-On and Lock it, I need to have the stock recovery installed.
gryghst72 said:
Doesn't seem to me that you solved the initial problem, just found a work around for it. I have the same problem with my phone not accepting the stock recovery for what ever reason. It will, however, accept the TWRP recovery, but this doesn't do me any good wrt warranty returns. before I S-On and Lock it, I need to have the stock recovery installed.
Click to expand...
Click to collapse
Have you tried ruu? That should flash the stock recovery and everything else stock. Need to ruu when you s-on to ensure everything is okay before turning secure flag on.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Have you tried ruu? That should flash the stock recovery and everything else stock. Need to ruu when you s-on to ensure everything is okay before turning secure flag on.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
I have RUU'd the following and in different orders:
5.28.605.2_NoBoot-IMG_firmware.zip
VZW.M7.5.28.605.2.PN0731IMG.zip
as well as "fastboot flash recovery 5.28.605.2_Stock_recovery.img"
all with a scattering of "fastboot erase cache".
The flash says it is successful, but when I boot to recovery, the screen graphics are garbage and when not garbage, it's the ! droid after the usual 15-20 sec blank screen. When I flash TWRP either via flash recovery or RUU that takes and works just fine. But this obviously isn't a "back to stock" set up.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3899mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.164s
Thoughts?
gryghst72 said:
I have RUU'd the following and in different orders:
5.28.605.2_NoBoot-IMG_firmware.zip
VZW.M7.5.28.605.2.PN0731IMG.zip
as well as "fastboot flash recovery 5.28.605.2_Stock_recovery.img"
all with a scattering of "fastboot erase cache".
The flash says it is successful, but when I boot to recovery, the screen graphics are garbage and when not garbage, it's the ! droid after the usual 15-20 sec blank screen. When I flash TWRP either via flash recovery or RUU that takes and works just fine. But this obviously isn't a "back to stock" set up.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3899mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.164s
Thoughts?
Click to expand...
Click to collapse
Have you tried the 2.x.y.z signed ruu in santod's stock Rom/firmware thread? Unsigned ruus are good, but sometimes a signed, official ruu gets the job done that unofficial ones can't.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Have you tried the 2.x.y.z signed ruu in santod's stock Rom/firmware thread? Unsigned ruus are good, but sometimes a signed, official ruu gets the job done that unofficial ones can't.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Is the signed one located here? I have not only because I have not read that one can go backwards, especially that far back. Can this be done successfully? What are the risks? Does the signed RUU contain all he necessary files to restart after the flash, are there any supporting flashes necessary (HBOOT, Recovery, Radios, etc.) Is this a viable solution or a shot in the dark which could brick the device?
Thanks for the on-going troubleshooting. I'm not trying to be a pain, just being careful since I am unfamiliar with the bootload/security features build into the system.
---------- Post added at 03:33 PM ---------- Previous post was at 02:58 PM ----------
I tried to RUU flash the 1.10.605.10 version .. here was my result:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Android>fastboot flash zip PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178274 KB)...
OKAY [ 44.569s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 51.044s
C:\Android>fastboot flash zip PN07IMG_M7_WL_JB_50_VZW_422_VERIZON_WWE_1.10.605.10_Radio_1.12.42.0906_NV_VZW_3.71_002_release_334098_signed_2.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178274 KB)...
OKAY [ 44.632s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 51.075s
C:\Android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.031s
Well, that didn't do anything, good or bad. Just didn't take and phone operates just fine as a phone, but still no recovery image, stock or otherwise.
Downloading 2.x.y.z signed version now. Will report the results after flash attempt.
Same results:
C:\Android>adb reboot-bootloader
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.062s]
finished. total time: 0.062s
C:\Android>fastboot flash zip RUU_2_10_605_1.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1232586 KB)...
OKAY [ 41.931s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 48.420s
Related
I was able to unlock the bootloader following the instructions on HTCDev. However, I am now unable to install a custom recovery. I have tried using both the 'fastboot' and the 'PC36IMG.zip' methods with the 'AmonRA-v2.3-hausmod_revA', and the 'PC36IMG_ra-supersonic-4.3-smelkus-ics',
When using the Fastboot method the recovery seems to flash, but afterwards, when I navigate and select 'recovery', the device sticks in the splash screen that reads 'htc EVO 4G'.
Here is the Terminal output from an example:
c-s-MacBook-Pro-15:~ c$ fastboot devices
HT08******27 fastboot
c-s-MacBook-Pro-15:~ c$ fastboot flash recovery PC36IMG_ra-supersonic-4.3-smelkus-ics.img
sending 'recovery' (4140 KB)...
OKAY [ 1.475s]
writing 'recovery'...
OKAY [ 1.775s]
finished. total time: 3.250s
c-s-MacBook-Pro-15:~ c$ fastboot erase cache
erasing 'cache'...
OKAY [ 1.227s]
finished. total time: 1.227s
When I use 'PC36IMG.zip' file to the root of the SD method, I get 'main version is older. Would you like to reboot?''
If I change 'mainver: 1.00.000.0' to 'mainver: 4.67.651.3' in the 'android-info.txt' file inside the zip (like suggested elsewhere), I get 'Parsing PC36IMG.zip...', then nothing.
It does read 'ÚNLOCKED' at the top of the bootloader screen now, and I checked md5 sums.
Any suggestions or help would be appreciated.
The Phone no longer boots up properly. Sticks in boot-loop when not booting to bootloader. It's a Sprint device. Was having issues with seemingly random powering down. Was able to boot after unlocking bootloader, but now doesn't (may have úninstalled' necessary 'bloatware').
Further info about device:
localhost:~ g$ fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.18.0001
(bootloader) version-baseband: 2.15.00.01.15
(bootloader) version-cpld: None
(bootloader) version-microp: 041f
(bootloader) version-main: 5.07.651.6
(bootloader) serialno: HT08******27
(bootloader) imei: 3************7
(bootloader) product: supersonic
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PC3610000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 4b46e889
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
I have been having call issues with my phone and need to send it back to VZW.
This phone was Rooted, with S-Off and Unlocked in the Bootloader, I started researching today how to put it back to stock and in the process I have simply soft bricked my phone and have tried and exhausted everything I could find.
When I reboot into RUU and try to flash the Decrypted file for my 1.10.65.10 it fails:
C:\fastboot>fastboot flash zip M7RUU.zip
sending 'zip' (1178304 KB)...
OKAY [ 60.146s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 196.594s
I am not able to go into or load any recovery files either, I am only able to do fastboot commands and no adb commands.
I really have searched all over xda forums and have not found the answer
My HTC currently will not boot and is able to fastboot only.
It is Displaying:
TAMPERED
RELOCKED
Security Warning
M7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-1.12.42.1104
OpenDSP-v31.120.274.0617
OS-1.10.605.10
eMMC-boot 2048MB
Sep 9 2013, 11:53:38.0
FASTBOOT USB
ETC..
Here are the notes from fastboot get var
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.1104
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA37YS901096
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4011mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-57eb7f637d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please if you have any advice or assistance, I woudl love to hear it I am on Win 7 32bit machine and is the same machine and cable I have used to do all the previous rooting and set it to s-off in the first place.
Thank you
Another error I receive:
C:\fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.001s
You must run an encrypted version of the RUU since you are back to S-ON. If you stayed at S-OFF you can run the decrypted RUU. Try to S-OFF again and then PM me and I will send you a link to help you out. If you can't. Run the following RUU. Link below.
http://bit.ly/vzwone-15
Flyhalf205 said:
You must run an encrypted version of the RUU since you are back to S-ON. If you stayed at S-OFF you can run the decrypted RUU. Try to S-OFF again and then PM me and I will send you a link to help you out. If you can't. Run the following RUU. Link below.
http://bit.ly/vzwone-15
Click to expand...
Click to collapse
Not to mention he's not even in ruu mode.
Sent from my HTC6600LVW using Tapatalk
dottat said:
Not to mention he's not even in ruu mode.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
Very tru dottat..
@tomwatez make sure when you hook to usb. In the command
fastboot oem rebootRUU
fastboot flash zip ruu.zip <---- You'll most likely have to do this command twice with the signed encrypted RUU
Flyhalf205 said:
Very tru dottat..
@tomwatez make sure when you hook to usb. In the command
fastboot oem rebootRUU
fastboot flash zip ruu.zip <---- You'll most likely have to do this command twice
Click to expand...
Click to collapse
And yes....if s-on make sure the ruu isn't older than software running on the phone.
Sent from my HTC6600LVW using Tapatalk
Flyhalf205 said:
You must run an encrypted version of the RUU since you are back to S-ON. If you stayed at S-OFF you can run the decrypted RUU. Try to S-OFF again and then PM me and I will send you a link to help you out. If you can't. Run the following RUU. Link below.
http://bit.ly/vzwone-15
Click to expand...
Click to collapse
Thank you I'll give it a shot!
Flyhalf205 said:
You must run an encrypted version of the RUU since you are back to S-ON. If you stayed at S-OFF you can run the decrypted RUU. Try to S-OFF again and then PM me and I will send you a link to help you out. If you can't. Run the following RUU. Link below.
http://bit.ly/vzwone-15
Click to expand...
Click to collapse
Flyhalf205 said:
Very tru dottat..
@tomwatez make sure when you hook to usb. In the command
fastboot oem rebootRUU
fastboot flash zip ruu.zip <---- You'll most likely have to do this command twice with the signed encrypted RUU
Click to expand...
Click to collapse
I actually have been using those commands and have been running it in RUU mode all day, been at it for about 8 hrs trying all sorts of different things.
The thing different now is that I have a link to a signed ru instead... trying it now, its been running for about 10 mins and is at this point:
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.043s]
finished. total time: 0.043s
C:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (1178525 KB)...
OKAY [ 57.957s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
tomwatez said:
i actually have been using those commands and have been running it in ruu mode all day, been at it for about 8 hrs trying all sorts of different things.
The thing different now is that i have a link to a signed ru instead... Trying it now, its been running for about 10 mins and is at this point:
C:\fastboot>fastboot oem rebootruu
...
(bootloader) start verify: 3
okay [ 0.043s]
finished. Total time: 0.043s
c:\fastboot>fastboot flash zip ruu.zip
sending 'zip' (1178525 kb)...
Okay [ 57.957s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
Click to expand...
Click to collapse
blah blah blah>> nothing to read here
Flyhalf205 said:
Very tru dottat..
@tomwatez make sure when you hook to usb. In the command
fastboot oem rebootRUU
fastboot flash zip ruu.zip <---- You'll most likely have to do this command twice with the signed encrypted RUU
Click to expand...
Click to collapse
Is thsi why you said to run twice?
C:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (1178525 KB)...
OKAY [ 57.957s]
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...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 1031.357s
tomwatez said:
Is thsi why you said to run twice?
C:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (1178525 KB)...
OKAY [ 57.957s]
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...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 1031.357s
Click to expand...
Click to collapse
Yes. Run it again. and It should run fine.
looks successful.. Now before I do anything else.. end goal is stock but want to wait after I get my replacement tomorrow to see what is on it.
what is the next step from here:
(bootloader) [RUU]UZ,radio,94
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,34
(bootloader) [RUU]WP,radio,68
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
OKAY [410.428s]
finished. total time: 468.138s
tomwatez said:
looks successful.. Now before I do anything else.. end goal is stock but want to wait after I get my replacement tomorrow to see what is on it.
what is the next step from here:
(bootloader) [RUU]UZ,radio,94
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,34
(bootloader) [RUU]WP,radio,68
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
OKAY [410.428s]
finished. total time: 468.138s
Click to expand...
Click to collapse
Your all good. So why are you getting it replaced after we just got it to stock?
Been having lots of issues with breaking up and dropped calls, not to mention the speaker is crackling..Verizon exhausted the troubleshooting and said we will send you a replacement. I wanted to try putting it back to stock to see if those things were still happening... So now that it is stock and I had s-off previously should I be good to go to redo s-off and rom, root it if I chose to keep it and it works better
tomwatez said:
Been having lots of issues with breaking up and dropped calls, not to mention the speaker is crackling..Verizon exhausted the troubleshooting and said we will send you a replacement. I wanted to try putting it back to stock to see if those things were still happening... So now that it is stock and I had s-off previously should I be good to go to redo s-off and rom, root it if I chose to keep it and it works better
Click to expand...
Click to collapse
Hope it all works out...I fear the supply of pre-4.3 phones is dwindling
Sent from my Nexus 7 using Tapatalk
dottat said:
Hope it all works out...I fear the supply of pre-4.3 phones is dwindling
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
The directions and link that was listed worked perfectly and I'm back up and running.
Thank you All! Lets see if the one I get is pre 4.3 or not.. I may just send it back if mine is working better.
tomwatez said:
The directions and link that was listed worked perfectly and I'm back up and running.
Thank you All! Lets see if the one I get is pre 4.3 or not.. I may just send it back if mine is working better.
Click to expand...
Click to collapse
Got the replacement today, sounds and looks great.. Best of all it was on 4.2.2 and 1.10.605.10, s-on, however the hboot is on 1.54.
I'm trying s-off right now and it seems to be going good so far, will report if it doesn't unlock...
Thanks again for your great support!
Sorry the pros are helping
Sent from my HTC6500LVW using XDA Premium HD app
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178525 KB)...
OKAY [ 53.441s]
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) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 186.403s
I'm using the instructions from this thread: http://forum.xda-developers.com/showthread.php?p=51514093
what should I do? please help me
You can S-off an m7vzw on 4.4.2 now. Use WeakSauce.apk for temp root, then firewater to s-off.
http://forum.xda-developers.com/showthread.php?t=2699089
Hi everybody
I have a M8 GPE unlocked/un-rooted/s-on with stock 4.4.4 and today i said that I will not wait for the OTA to come, and decided to flash it myself.
When going to recovery i saw that there is no option to adb sideload a file, strange, so I booted in TWRP (not flashed) and tried to sideload from there. I could not make the ADB sideload work in TWRP also because of some errors, and I tried the install zip option. When flashing the OTA zip I got an error saying that the required version is *4.4.4* and that i had *4.4.2*. I know for sure that I had 4.4.4 because i got the update myself and apply it automatically from within android.
Trying to do a factory reset in TWRP in order to try again the OTA zip file, i wiped the system partition (my bad) and since then i am stucked in bootloader/recovery without any way to boot into OS.
I tried to reboot into RUU and flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip, but i get the error (probably because i am s-on):
Code:
target reported max download size of 1830617088 bytes
sending 'zip' (635732 KB)...
OKAY [ 26.906s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 27.080s
Anybody can tell if there is any way to flash the stock image on the phone?
As I understood I could do s-off only from OS, and for me that ism not possible
Thanks for the help in advance,
galiganu
Code:
platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
I just read that in order to flash back the stock rom i have to be locked, so i did fastboot oem lock. Tried to flash the RUU image and i get this:
Code:
platform-tools>fastboot flash zip RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
target reported max download size of 1830617088 bytes
sending 'zip' (635732 KB)...
OKAY [ 26.190s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 56.180s
Any ideas?
Same error as above i get with RUU-HTC_One_M8_GPE_4.4.3-2.10.1700.4.zip and RUU-HTC_One_M8_GPE_4.4.4-2.12.1700.1.zip.
hi guys, no idea about my issue?
i managed to install CM11 in the end... at least i can use the phone until i figure out how to get back to stock gpe
solution here thanks to ckpv5
http://forum.xda-developers.com/showpost.php?p=57398166&postcount=3274
Hello all,
I'm having a bit of a time rectifying this problem, and my usual Google/XDA searches haven't unfortunately bore any fruit.
The problem in a nutshell:
I unlocked my phone via HTC Dev, it was S-Off, and bootloader was unlocked.
I was using Viper Rom, last one before their 4.0/4.1 Lollipop release - no prroblems.
I was using an older 3.X firmware (I forget which - probably inconsequential in any case).
I wiped my phone in preparation for installing the 4.1 Rom with TWRP.
I installed the new Rom via TWRP, I wiped again with the Rom's wiper.
I rebooted my phone after a successful wipe.
I booted into the rom, but a whole bunch of processes failed (com.android ones), however I was able to, at this point, get into my wifi and set up my accounts etc.
After this, I had a black screen, though my notification bar etc. were there.
I thought it might be a firmware issue, and so I used fastboot RUU to install the firmware version 4.16.401.10. Everything was fine, and it has flashed successfully.
Unfortunately, the bootloader is now once again locked (relocked, to be exact), and I can't boot back into the Rom OS to run adb commands to unlock it once again.
Fastboot commands such as flash unlocktoken are met with fails.
I have no idea how to proceed from this point forwards.
So, I'd appreciate any and all help at this point to get me back up and running again! Maybe I'll learn something along the way too
Thanks in advance!
edit: Ah yes, here is my getvar information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *************
(bootloader) imei: *************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Can you post the error you get when trying to unlock the phone?
You don't actually need to be unlocked to flash a custom recovery, you just flash a ZIP via RUU mode (it's what I do on the rare occasion I want to root my phone to try something)
Sure, which error are you talking about?
When trying to use my unlock token, I get the following:
target reported max download size of 1826152448 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.135s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
Click to expand...
Click to collapse
I thought there was a fastboot oem unlock, but as it turns out, there isn't.
When trying to flash TWRP 2.8.5.0 (mine is an international UK/EU version, not sprint or verizon or tmobile, carrier SIM unlocked) - I get:
target reported max download size of 1826152448 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.683s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.689s
Click to expand...
Click to collapse
Do you require any additional information?
Thank you for the quick response to my plight!
Edit: Oh, do I have to be in RUU mode to install TWRP? If so, that might be my noobish mistake!
Edit2: nope, RUU mode won't let me do it either
target reported max download size of 1826418688 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.698s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.704s
Click to expand...
Click to collapse
For example, you could flash this ZIP file in RUU mode for the latest TWRP and keep the bootloader locked:
https://www.hightail.com/download/UlRTcXlpOC9iV3hMWE1UQw
You shouldn't have to be in RUU mode, I just made this ZIP to flash TWRP with a locked bootloader
Thank you for this, however I'm getting the same error.
Am I doing this correctly?
(Using Ubuntu)
Terminal command: sudo fastboot oem rebootRUU
Wait for silver HTC logo on phone screen.
(After unzipping the recovery.img file) sudo fastboot flash recovery recovery.img
Same error as above -
target reported max download size of 1826418688 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.735s]
writing 'recovery'...
FAILED (remote: not allowed)
Click to expand...
Click to collapse
fastboot flash recovery recovery.img <--- wrong
fastboot flash zip recoveryRUU.zip <--- this one
I love you man! Thank you so much!
Worked, TWRP reinstalled, happy days!
For my own knowledge, why did using 'flash recovery' not work? And why did using RUU and flashing the zip work?
Thank you
Because you can't flash partitions in RUU mode, only ZIP files
Individual partitions are flashed in fastboot but you need the bootloader unlocked to do that
Nicely put, thank you. I'll remember all this for future.
Thanks again both!
What you can do now, though, is lock/unlock the bootloader from TWRP...
1. Boot into TWRP
2. Connect phone to your PC (make sure drivers are installed and that your device is recognised when you type adb devices)
3. Get into the shell by typing adb shell
4. Type the following command to unlock the bootloader (probably best to copy/paste this):
Code:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
5. Exit shell by typing exit
6. Reboot phone to the bootloader and check you're now 'unlocked'
Parts taken from this thread by @scotty1223 - http://forum.xda-developers.com/showthread.php?t=2708571
EddyOS said:
Can you post the error you get when trying to unlock the phone?
You don't actually need to be unlocked to flash a custom recovery, you just flash a ZIP via RUU mode (it's what I do on the rare occasion I want to root my phone to try something)
Click to expand...
Click to collapse
EddyOS said:
What you can do now, though, is lock/unlock the bootloader from TWRP...
1. Boot into TWRP
2. Connect phone to your PC (make sure drivers are installed and that your device is recognised when you type adb devices)
3. Get into the shell by typing adb shell
4. Type the following command to unlock the bootloader (probably best to copy/paste this):
Code:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
5. Exit shell by typing exit
6. Reboot phone to the bootloader and check you're now 'unlocked'
Parts taken from this thread by @scotty1223 - http://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
Hey, thank you! Sorry, I didn't look back on my topic once I'd managed to solve it. Cheers for the instructions!
HeadKandy said:
Hey, thank you! Sorry, I didn't look back on my topic once I'd managed to solve it. Cheers for the instructions!
Click to expand...
Click to collapse
This is new information for me... And I'm stuck too wanting to root..but don't want to use the htcdev token and want to install TWRP.
Q#1: Do I put the recoveryRUU.zip in the platform-tools directory?
Q#2: What is RUU mode? I've done plenty of things in fastboot (flashed recoveries before...I guess I didn't realize I was flashing a partition)... So the whole RUU thing is confusing me. Aren't you just rebooting into fastboot and flashing that zip?
I see the correct commands above, but I just want to confirm what I'm doing exactly.
Thank you very much in advance!
syntropic said:
This is new information for me... And I'm stuck too wanting to root..but don't want to use the htcdev token and want to install TWRP.
Q#1: Do I put the recoveryRUU.zip in the platform-tools directory?
Q#2: What is RUU mode? I've done plenty of things in fastboot (flashed recoveries before...I guess I didn't realize I was flashing a partition)... So the whole RUU thing is confusing me. Aren't you just rebooting into fastboot and flashing that zip?
I see the correct commands above, but I just want to confirm what I'm doing exactly.
Thank you very much in advance!
Click to expand...
Click to collapse
1. Yes
2. It's the mode used to flash the RUU - fastboot oem rebootRUU
EddyOS said:
1. Yes
2. It's the mode used to flash the RUU - fastboot oem rebootRUU
Click to expand...
Click to collapse
Ok... I guess when I hear RUU I think of the .exe run in Windows to update or restore to factory. Didn't know there was a "mode".
But thanks! I'll put your zip in platform-tools, and then run the above commands.
How is the zip created? Is that something I can do fairly easily?
No. It's extracted from the EXE version of the RUU and in encrypted by HTC (unless you have the right tools to hack it)
EddyOS said:
No. It's extracted from the EXE version of the RUU and in encrypted by HTC (unless you have the right tools to hack it)
Click to expand...
Click to collapse
What tools do I need? Like a disassembler or Ollydbg?
[deleted earlier self-solved error]
---------- Post added at 01:28 PM ---------- Previous post was at 01:02 PM ----------
This is quite frustrating.... I am not sure why I am finding so many obstacles to what looked like an effortless way to flash a custom recovery...
I ran the fastboot flash zip recoveryRUU.zip
and received the following response from adb.
target reported max download size of 1826418688 bytes
sending 'zip' (12223 KB)...
OKAY [ 1.440s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 3.869s
Any idea what "41 model id check fail" could mean?? It doesn't sound good.
I researched this and it looks like it has something to do with the a version mismatch or something. Not sure.
I ran getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.531.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: ********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 06f11f5b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
and noticed that my bootloader and HeadKandy's bootloader are different... could that be the problem?
Above you said you created the recoveryRUU.zip from an HTC RUU. So could the variant of the RUU you used to create that zip be the issue??
I appreciate any help as I would love to root this without having to use HTCDEV token to unlock the bootloader.
This is a very interesting and cool way to get around having to unlock the boot loader with a HTC token, but flashing a zip containing the custom recovery requires that I create that zip...which I have no idea how to do.
Is there any source for any custom recovery that's in a flashable zip format already?? If so, I could use that, then root it/unlock bootloader and then install TWRP.
syntropic said:
What tools do I need? Like a disassembler or Ollydbg?
[deleted earlier self-solved error]
---------- Post added at 01:28 PM ---------- Previous post was at 01:02 PM ----------
This is quite frustrating.... I am not sure why I am finding so many obstacles to what looked like an effortless way to flash a custom recovery...
I ran the fastboot flash zip recoveryRUU.zip
and received the following response from adb.
target reported max download size of 1826418688 bytes
sending 'zip' (12223 KB)...
OKAY [ 1.440s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 3.869s
Any idea what "41 model id check fail" could mean?? It doesn't sound good.
I researched this and it looks like it has something to do with the a version mismatch or something. Not sure.
I ran getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.531.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: ********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 06f11f5b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Sorry, I thought you were the OPand noticed that my bootloader and HeadKandy's bootloader are different... could that be the problem?
Above you said you created the recoveryRUU.zip from an HTC RUU. So could the variant of the RUU you used to create that zip be the issue??
I appreciate any help as I would love to root this without having to use HTCDEV token to unlock the bootloader.
This is a very interesting and cool way to get around having to unlock the boot loader with a HTC token, but flashing a zip containing the custom recovery requires that I create that zip...which I have no idea how to do.
Is there any source for any custom recovery that's in a flashable zip format already?? If so, I could use that, then root it/unlock bootloader and then install TWRP.
Click to expand...
Click to collapse
Sorry, I thought you were the OP! That RUU won't work at all as you have to be on x.xx.401.x to flash it (it's the EU RUU, yours looks like T-Mobile)
syntropic said:
This is quite frustrating.... I am not sure why I am finding so many obstacles to what looked like an effortless way to flash a custom recovery...
Click to expand...
Click to collapse
I don't find this surprising at all. You are trying to flash a custom recovery with a locked bootloader. And one of the whole points (arguably the main point) of the locked bootloader is to prevent installing custom recovery.
A locked bootloader means you can only flash something that is properly signed, meaning it also has to pass the CID, MID checks. Since the zip you are trying to flash is not for your CID, you will get a fail.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unlocking bootloader a second time did it!
Hi there,
yesterday a friend of mine came around and told me he tried to update from AHRD 3.28.401.9 to 4.16.401.10.
He told me he followed the guides but he end up in a working ARHD Lollipop - but without the ability
to flash anything via fastboot ('ERROR' remote:not allowed) while having bootloader 'RELOCKED'.
He also tried to update to the lastest firmware - FUU as well - but without success.
I tried alot to fix it - but also without success.
The last option and idea I had was to unlock the bootloader at HTCDEVs a second time.
I did it like described in the public tuts around here at XDA.
AND IT WORKED !
This might not work in every case - but it is an option since your bootloader is already unlocked and because this might be you last option
As usual -> I am not responsible for bricked devices ... etc, if you try this!
Regards,
brush2
Here is the final result of fastboot getvar all (bootloader is now 'UNLOCKED'):
Code:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-cpld: None
version-microp: None
version-main: 4.16.401.10
version-misc: PVT SHIP S-OFF
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__001 (HTC_102 originally)
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
[Q] Unknown command "unlocktoken" and "43 main version check fail"
Hello,
I try to apply a CustomROM to a Wildfire S. Two years ago I did it with another Wildfire S but the current device doesn't work...
At first some details of the device:
Code:
$ fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0099
(bootloader) version-baseband: 7.60.39.12M
(bootloader) version-cpld: None
(bootloader) version-microp: 0451
(bootloader) version-main: 20.26.401.4
(bootloader) serialno: SH26LTR04002
(bootloader) imei: 359144046869429
(bootloader) product: marvel
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PG7610000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3940mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 510e562c
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.005s
I received the unlock token by HTCdev but on flashing a error message appears that the command is unknown.
Code:
$ fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 0.000s
HBOOT is in version 1.09.0099 - the same as mentioned in RUU "HTC EU". Unfortunally I can't figure out what version of Fastboot I have. So I've tried to flash the newest one.
I downloaded the "HTC EU"-RUU, extracted the rom.zip by executing with wine and tried to flash.
Code:
$ fastboot oem rebootRUU
...
OKAY [ 0.098s]
finished. total time: 0.098s
$ fastboot flash zip rom.zip
sending 'zip' (212 KB)...
OKAY [ 0.513s]
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...
FAILED (remote: 43 main version check fail)
finished. total time: 7.146s
It doesn't will be sucessfull even if I repeat the flash command.
Does anybody know what's going wrong? Am I right that I need to flash the new RUU. Why that doesn't work?
Bye Markus
The execution of the RUU.exe on a fresh installed WinXP showed that there was already a newer version than necessary. The problem was simply the old version of Linux' fastboot binary of Ubuntu's repository. Another old one by my own or the binary of htcdev.com worked fine.