Related
Hi, can somebody help me…? Please….:crying:
After flash mine M7 at&t sense with RUU-HTC_One_GE-2.14.1700.15.zip every thing was perfect recieved 2 OTA updates to KK4.4.2 them I tried to root it by adb command but get this error
C:\Users\SONYMANIAC\Desktop\Android\adb platforms-tools 1.0.31\adb>fastboot oem
unlock
…
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.582s]
finished. total time: 0.585s
Device Info
LOCKED
M7UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.62.1700.1
eMMC-boot 2048MB
Dec 9 2013, 00:38:19.0
Thanks a lot to all of you.
sonymaniac said:
Hi, can somebody help me…? Please….:crying:
After flash mine M7 at&t sense with RUU-HTC_One_GE-2.14.1700.15.zip every thing was perfect recieved 2 OTA updates to KK4.4.2 them I tried to root it by adb command but get this error
C:\Users\SONYMANIAC\Desktop\Android\adb platforms-tools 1.0.31\adb>fastboot oem
unlock
…
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.582s]
finished. total time: 0.585s
Device Info
LOCKED
M7UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.62.1700.1
eMMC-boot 2048MB
Dec 9 2013, 00:38:19.0
Thanks a lot to all of you.
Click to expand...
Click to collapse
did you tried to unlock via htcdev.com?
or unlocking bootloader with revone since you are s-off?
DONT GO BACK S-ON!
Thanks
alray said:
did you tried to unlock via htcdev.com?
or unlocking bootloader with revone since you are s-off?
DONT GO BACK S-ON!
Click to expand...
Click to collapse
Yes I tried but doesen't work and if itry to install another RUU it freeze after "sending zip" ...
sonymaniac said:
Yes I tried but doesen't work and if itry to install another RUU it freeze after "sending zip" ...
Click to expand...
Click to collapse
which ruu?
Since you are s-off you can put twrp recovery.img in a firmware.zip and flash it in ruu mode with fastboot flash zip firmware.zip. No need to unlock bootloader.
Also need android-info.txt in the firmware.zip, that's it.
Thanks
alray said:
which ruu?
Click to expand...
Click to collapse
RUU-HTC_One_GE-4.4.2-3.62.1700.1_Rooted
RUU-HTC_One_GE-2.14.1700.15 this is installed and work
great after update to KK4.4.2 but I can't root it...
Also, if you really want to unlock bootloader, downgrade to hboot 1.4.4 and use revone to unlock. Then reflash GPE ruu.
Thanks
cschmitt said:
Since you are s-off you can put twrp recovery.img in a firmware.zip and flash it in ruu mode with fastboot flash zip firmware.zip. No need to unlock bootloader.
Also need android-info.txt in the firmware.zip, that's it.
Click to expand...
Click to collapse
can you recommend me some firmware to try install on the device...?
Thanks a lot.
sonymaniac said:
can you recommend me some firmware to try install on the device...?
Click to expand...
Click to collapse
Here is a firmware.zip containing TWRP 2.6.3.4 for m7ul that can be flashed in RUU mode with s-off: firmware_twrp.zip
Note: This firmware flashes TWRP recovery only, nothing else. All other firmware files (hboot, sbl, radio, etc.) will remain untouched. It does NOT factory reset, or erase /system or /data partitions.
To install, reboot into bootloader and then:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware_twrp.zip
fastboot erase cache
fastboot reboot-bootloader
Device will reboot into bootloader; select recovery and it will reboot into TWRP, then flash superuser/supersu to root.
Many Thanks
Hi, thank you very much i did it but received this error:
C:\Users\SONYMANIAC\Android\Rom\adt-bundle-windows-x86-20131030\adt-bundle-windo
ws-x86-20131030\sdk\platform-tools>fastboot flash zip firmware_twrp.zip
sending 'zip' (9271 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 235.678s
It keep sending zip whitout answer...
I think so it is because the bootloader are locked but can't fine a effective method to unlock it.
I downgrade hboot from 1.54 to 1.44 and have installed KK 4.4.2 google edition if this information can help to solve...
Thank you again.
sonymaniac said:
Hi, thank you very much i did it but received this error:
C:\Users\SONYMANIAC\Android\Rom\adt-bundle-windows-x86-20131030\adt-bundle-windo
ws-x86-20131030\sdk\platform-tools>fastboot flash zip firmware_twrp.zip
sending 'zip' (9271 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 235.678s
It keep sending zip whitout answer...
I think so it is because the bootloader are locked but can't fine a effective method to unlock it.
I downgrade hboot from 1.54 to 1.44 and have installed KK 4.4.2 google edition if this information can help to solve...
Thank you again.
Click to expand...
Click to collapse
So you were able to flash the RUU-HTC_One_GE-2.14.1700.15.zip conversion RUU in fastboot, but not the firmware_twrp.zip ? That doesn't make sense, since with s-off bootloader lock state shouldn't matter.
From what I've read the 'too many links' error can be a corrupt zip, or USB port/cable problem.
Have you tried to flash the recovery.img directly with: fastboot flash recovery recovery.img
You could just unlock the bootloader with revone: http://forum.xda-developers.com/showthread.php?t=2497712
sonymaniac said:
Hi, thank you very much i did it but received this error:
C:\Users\SONYMANIAC\Android\Rom\adt-bundle-windows-x86-20131030\adt-bundle-windo
ws-x86-20131030\sdk\platform-tools>fastboot flash zip firmware_twrp.zip
sending 'zip' (9271 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 235.678s
It keep sending zip whitout answer...
I think so it is because the bootloader are locked but can't fine a effective method to unlock it.
I downgrade hboot from 1.54 to 1.44 and have installed KK 4.4.2 google edition if this information can help to solve...
Thank you again.
Click to expand...
Click to collapse
cschmitt said:
So you were able to flash the RUU-HTC_One_GE-2.14.1700.15.zip conversion RUU in fastboot, but not the firmware_twrp.zip ? That doesn't make sense, since with s-off bootloader lock state shouldn't matter.
From what I've read the 'too many links' error can be a corrupt zip, or USB port/cable problem.
Have you tried to flash the recovery.img directly with: fastboot flash recovery recovery.img
You could just unlock the bootloader with revone: http://forum.xda-developers.com/showthread.php?t=2497712
Click to expand...
Click to collapse
The zip you created was intended for ruu mode if i read correctly, and the OP didn't "fastboot oem rebootRUU" first.
nkk71 said:
The zip you created was intended for ruu mode if i read correctly, and the OP didn't "fastboot oem rebootRUU" first.
Click to expand...
Click to collapse
I'm not sure that's the case; the error from attempting to flash in 'regular' fastboot mode is:
Code:
X:\HTCOne>fastboot flash zip firmware_twrp.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9271 KB)...
OKAY [ 1.280s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.315s
Also fairly certain the error isn't caused by a locked bootloader. I just re-locked my bootloader and was able to flash firmware_twrp.zip in RUU mode just fine.
Code:
X:\HTCOne>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.062s]
finished. total time: 0.062s
X:\HTCOne>fastboot flash zip firmware_twrp.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9271 KB)...
OKAY [ 1.279s]
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,31
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,52
(bootloader) [RUU]UZ,recovery,62
(bootloader) [RUU]UZ,recovery,76
(bootloader) [RUU]UZ,recovery,88
(bootloader) [RUU]UZ,recovery,98
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
OKAY [ 3.410s]
finished. total time: 4.691s
cschmitt said:
I'm not sure that's the case; the error from attempting to flash in 'regular' fastboot mode is:
Code:
X:\HTCOne>fastboot flash zip firmware_twrp.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9271 KB)...
OKAY [ 1.280s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 1.315s
Also fairly certain the error isn't caused by a locked bootloader. I just re-locked my bootloader and was able to flash firmware_twrp.zip in RUU mode just fine.
Code:
X:\HTCOne>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.062s]
finished. total time: 0.062s
X:\HTCOne>fastboot flash zip firmware_twrp.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9271 KB)...
OKAY [ 1.279s]
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,31
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,52
(bootloader) [RUU]UZ,recovery,62
(bootloader) [RUU]UZ,recovery,76
(bootloader) [RUU]UZ,recovery,88
(bootloader) [RUU]UZ,recovery,98
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
OKAY [ 3.410s]
finished. total time: 4.691s
Click to expand...
Click to collapse
As far as I know (and tried... not this but other stuff), with a locked or relocked bootloader (I'm S-Off) any "fastboot flash ....." command will result in "FAILED (remote: not allowed)" or similar.
Basically, my conclusion:
A) "fastboot flash ...." (in normal mode) won't work unless UNLOCKED irrelevant whether S-On or S-Off
B) "fastboot flash zip ..." (in RUU mode) will only work if: LOCKED/RELOCKED with S-On, or S-Off and then lock status doesnt matter.
Many Thanks
Thanks for your help.
I tried to flash .zip .img and it failed
sending zip or recovery or firmware and never end
fastboot mode or RUUmode get the same error
Thanks
On RUUmode received this
C:\Users\SONYMANIAC\Android\Rom\android-sdk_r22.3-windows\android-sdk-windows\pl
atform-tools>fastboot flash zip firmware_twrp.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9271 KB)...
It never completed the flash action :crying:
Thanks
I tried whit both Mode Normal and RUU getting the same failed
C:\Users\SONYMANIAC\Android\Rom\android-sdk_r22.3-windows\android-sdk-windows\pl
atform-tools>fastboot flash zip firmware_twrp.zip
target reported max download size of 1526722560 bytes
sending 'zip' (9271 KB)...
Many Thanks
cschmitt said:
So you were able to flash the RUU-HTC_One_GE-2.14.1700.15.zip conversion RUU in fastboot, but not the firmware_twrp.zip ? That doesn't make sense, since with s-off bootloader lock state shouldn't matter.
From what I've read the 'too many links' error can be a corrupt zip, or USB port/cable problem.
Have you tried to flash the recovery.img directly with: fastboot flash recovery recovery.img
You could just unlock the bootloader with revone: http://forum.xda-developers.com/showthread.php?t=2497712
Click to expand...
Click to collapse
FAILED too many links received when disconnect from usb because never finish from sending "zip or recovery or firmware"
sonymaniac said:
Hi, thank you very much i did it but received this error:
C:\Users\SONYMANIAC\Android\Rom\adt-bundle-windows-x86-20131030\adt-bundle-windo
ws-x86-20131030\sdk\platform-tools>fastboot flash zip firmware_twrp.zip
sending 'zip' (9271 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 235.678s
It keep sending zip whitout answer...
I think so it is because the bootloader are locked but can't fine a effective method to unlock it.
I downgrade hboot from 1.54 to 1.44 and have installed KK 4.4.2 google edition if this information can help to solve...
Thank you again.
Click to expand...
Click to collapse
If you downgraded hboot to 1.44 then use revone, @cschmitt gave you a link. Since you are having issues unlocking bootloader using fastboot, use revone to unlock it should work since you are on 1.44.
Sent from my SGH-I337 using xda app-developers app
Many Thanks
cschmitt said:
So you were able to flash the RUU-HTC_One_GE-2.14.1700.15.zip conversion RUU in fastboot, but not the firmware_twrp.zip ? That doesn't make sense, since with s-off bootloader lock state shouldn't matter.
From what I've read the 'too many links' error can be a corrupt zip, or USB port/cable problem.
Have you tried to flash the recovery.img directly with: fastboot flash recovery recovery.img
You could just unlock the bootloader with revone: http://forum.xda-developers.com/showthread.php?t=2497712
Click to expand...
Click to collapse
Sorry but can't use revone because minimum requirements devices must be rooted and mine isn't root
Hello
I have HTC one m7_u cid 332 hboot 1.55
For my phone there is no stock RUU searched every where
Phone is hang on HTC logo
I can go to fast boot menu tryed to unlock bootloader with htcdev but not work
My question is there any way to s-off or unlock boot loader without USB debugging on ?????
Tanx
afghan-gsm-mastermind said:
Hello
I have HTC one m7_u cid 332 hboot 1.55
For my phone there is no stock RUU searched every where
Phone is hang on HTC logo
I can go to fast boot menu tryed to unlock bootloader with htcdev but not work
My question is there any way to s-off or unlock boot loader without USB debugging on ?????
Tanx
Click to expand...
Click to collapse
bootloader is unlocked with fastboot not adb, so usb debugging is not required. Btw usb debugging only affect the usb connection when the phone is booted in the OS so its does not affect bootloader unlocking, fastboot commands or adb commands from recovery.
alray said:
bootloader is unlocked with fastboot not adb, so usb debugging is not required. Btw usb debugging only affect the usb connection when the phone is booted in the OS so its does not affect bootloader unlocking, fastboot commands or adb commands from recovery.
Click to expand...
Click to collapse
I tried unlocking bootloader with htcdev all thing gose OK but after restart phone is lock again I should say phone is dead and hang on HTC logo
Waiting for help .......
afghan-gsm-mastermind said:
Waiting for help .......
Click to expand...
Click to collapse
how are we suppose to help you with a locked bootloader ?
clsA said:
how are we suppose to help you with a locked bootloader ?
Click to expand...
Click to collapse
I've told him this in a previous thread. . Without an unlocked bootloader he is stuck.. He has to unlock first...
Sent from my GT-I9505 using XDA Premium 4 mobile app
s-on, No Os, unlocked, got twrp. Cant install stock RUU!!
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot
AnonZA said:
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot
Click to expand...
Click to collapse
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's
Sent from my GT-I9505 using XDA Premium 4 mobile app
AnonZA said:
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot
Click to expand...
Click to collapse
sounds like your trying to sideload a RUU.zip .. that won't work
to flash RUU.zip use
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip <<yes two times
fastboot reboot
you just need the rom.zip in the same folder as fastboot
HTC__016
bored_stupid said:
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 3847mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------
clsA: I tried those command million of times. It kept coming back with "boot loader signature verification..." My phone is WIPED as you can see. So usb debugging is off presumably..
Click to expand...
Click to collapse
You have the international M7 ul so download and install this rom. Follow the guide on installing
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Sent from my GT-I9505 using XDA Premium 4 mobile app
I Formatted partition using "How to: Fix a corrupted DATA partition on the HTC One" Then tried these commands (1) fastboot oem rebootRUU (2) fastboot flash zip rom.zip
{C:\Users\####\Desktop\Mini SDK>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1239446 KB)...
OKAY [ 46.879s]
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: 61.244s
I think my next step is a stock stock RUU right?
Thanks a lot for the help..
Wrong one Apparently..
bored_stupid said:
You have the international M7 ul so download and install this rom. Follow the guide on installing
(LINK)
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ran with admin rights, went through all the windows till i said update.. then i get error code 155, and that error code means incorrect ROM according to the programs readme!
What other ROM should I try?
Sorry to be such a pain.. I just need to use my device again.. lol
AnonZA said:
I Formatted partition using "How to: Fix a corrupted DATA partition on the HTC One" Then tried these commands (1) fastboot oem rebootRUU (2) fastboot flash zip rom.zip
{C:\Users\####\Desktop\Mini SDK>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1239446 KB)...
OKAY [ 46.879s]
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: 61.244s
I think my next step is a stock stock RUU right?
Thanks a lot for the help..
Click to expand...
Click to collapse
Basically you are trying to flash a file in the bootloader that is not intended to be flashed that way. Use custom recovery or it may be an update, in that case it needs stock recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Hi Guys
i think i really messed up my HTC one first of all here's the screen details on the boot loader
and I'm a complete noobie on android and this is phone is my frist android device
****UNLOCKED****
M7_UL PVT SHIP S-OFF RH
CID-HTC__044
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Apr 25 2014
PC: Windows 7 Ultimate
The story is I tried to root my device using this tutorial in youtube from zedomax
and it was a success without trouble,
So I tried to install a custom ROM ViperOne_6.2.0.zip
and its where everything got messed up when the installation returned an error during installation
I tried reinstalling and i think i wiped all the data on the storage including the backup using the TWRP wipe button including OS files
after several attempts i was able to re enter TWRP and/or CWP trying to install via Sideload command but failed
i cant load zip files via my PC too because my pc cant read/write the storage of my phone. (I installed USB drivers and phone is detectable on device manager)
now the bootloader have this error Active cmdline overflow! (1094 Bytes)
Since I'm a real newbie in android may I kindly ask a step-by-step instruction on how can i recover if possible from this trouble.
I would really appreciate everyone's help from this forum.
here's a guide to fix that active cmdline overflow, you messed up one of your partitions and your phone wont work until you fix that issue, you need to follow that guide to the letter, do not skip any parts, read it all first and understand it, if you get any of the commands wrong you could end up with a complete brick so copy and paste them.
http://forum.xda-developers.com/showthread.php?t=2739126
Thank you for the quick reply,
I tried to install "fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img" on fastboot. It installed correctly
when I erased cache then rebooted the fast booth, the "Active cmdline overflow! (**** Bytes)" error was gone
but when i enter recovery, it reboots again to fastboot and the error reappears.
and the cycle repeats again.
I can't get past this
one more thing...I noticed that you used a different adb C:\ADB3> is there a version 3 or is it just a folder name?
when I try to detect device in fastboot:
D:\HTCOne recover\HTCOneRoot>fastboot devices
FA32GW9**** fastboot
but when i try to use the same command on adb:
D:\HTCOne recover\HTCOneRoot>adb devices
List of devices attached
nothing on the list. And ADB commands don't work because it can't recognize the device.
I really need your help. Thanks in Advance
I would like to add that I can't access the phone storage through my PC
one more thing...
how would I know if i got these?
from the guide
"Well you need adb commands, root and busybox... which are only available in a custom recovery or a rooted ROM (with USB debugging enabled)"
1. adb commands
2. root and
3. busybox
4. custom recovery or a rooted ROM (with USB debugging enabled)
which are only available in a custom recovery or a rooted ROM (with USB debugging enabled)"
WilmanB said:
Thank you for the quick reply,
I tried to install "fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img" on fastboot. It installed correctly
when I erased cache then rebooted the fast booth, the "Active cmdline overflow! (**** Bytes)" error was gone
but when i enter recovery, it reboots again to fastboot and the error reappears.
and the cycle repeats again.
I can't get past this
one more thing...I noticed that you used a different adb C:\ADB3> is there a version 3 or is it just a folder name?
Click to expand...
Click to collapse
have you restored mmcblk0p19 like said in the guide?
but when i try to use the same command on adb:
D:\HTCOne recover\HTCOneRoot>adb devices
List of devices attached
nothing on the list.
and ADB commands don't work because it can't recognize the device.
I really need your help. Thanks in Advance
I would like to add that I can't access the phone storage through my PC
Click to expand...
Click to collapse
adb only works from custom recovery or from a booted rom with usb debug on. adb will not works from bootloader and you will not see phone storage from bootloader.
alray said:
have you restored mmcblk0p19 like said in the guide?
Click to expand...
Click to collapse
but adb does not recognize my phone so i cant restore mmcblk0p1 like it says on the instruction
adb wont respond to any adb commands
but fastboot is responsive
"adb only works from custom recovery or from a booted rom with usb debug on."
how do i do this? How will I know if I'm running in a booted ROM with USB debug On?
I install "fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img" on fastboot. It installed correctly but it wont enter recovery mode
First of all you will know if you are running a booted Rom if your phone boots up lol, in your case, yours doesn't, so ignore this and usb debugging.
Fastboot commands only work in bootloader.
Adb commands for you will only work inside recovery.
You must get into recovery to use adb to fix your phone, the reason you apprear to not be able to get in is because of your hboot version, you need to downgrade it, however I leave this completely in your hands and won't be held responsible if you brick your phone, simply, if you flash even the slightest wrong hboot, you'll have a brick, read the rest of that thread after the instructions, your same issue is in that thread.
WilmanB said:
but adb does not recognize my phone so i cant restore mmcblk0p1 like it says on the instruction
adb wont respond to any adb commands
but fastboot is responsive
Click to expand...
Click to collapse
ADB commands = Usable from custom recovery mode or from a normally booted phone (not your case)
FASTBOOT commands = Usable only from bootloader, where you currently are. You can't use adb here
"adb only works from custom recovery or from a booted rom with usb debug on."
how do i do this? How will I know if I'm running in a booted ROM with USB debug On?
Click to expand...
Click to collapse
flash the nobcb verison of twrp, boot in recovery and then you'll be able to use ADB commands.
I install "fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img" on fastboot. It installed correctly but it wont enter recovery mode
Click to expand...
Click to collapse
Code:
fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot in recovery mode again.
if you are still not able to boot the nobcb recovery, better to ask in the thread Seanie280672 linked you
Wow, thank you all very much. I am now able to enter recovery mode using HBOOT -1.44.0000 through CWT recovery
no more cmdline overflow.
and I'm done restoring mmcblk0p19
now i just need to find the correct RUU to flash I need your help again guys? I'm not really sure what RUU to flash or what to do next from here
WilmanB said:
Wow, thank you all very much. I am now able to enter recovery mode using HBOOT -1.44.0000 through CWT recovery
no more cmdline overflow.
and I'm done restoring mmcblk0p19
now i just need to find the correct RUU to flash I need your help again guys? I'm not really sure what RUU to flash or what to do next from here
Click to expand...
Click to collapse
post the output of "fastboot getvar all" excluding imei and serialno and we'll be able to tell you what ruu you can use.
alray said:
post the output of "fastboot getvar all" excluding imei and serialno and we'll be able to tell you what ruu you can use.
Click to expand...
Click to collapse
@elray
Thanks for replying these are what i got from the getvar command
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.707.1
version-misc: PVT SHIP S-OFF
serialno: FA32GW9*****
imei: 3558590500*****
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__044
battery-status: good
battery-voltage: 4318mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
gencheckpt: 0
I wish you can locate a proper RUU for my device.
I would also like to ask if it is possible to install custom ROM on my phone.
I tried to install the ViperOne 6.2.0 and Android Revolution HD 71.1 but it's both unsuccessful
now I'm stuck on Android 4.2.2 in HTC Sense 5 because i can't install new updates to KitKat and Sense 6
WilmanB said:
@elray
Thanks for replying these are what i got from the getvar command
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.707.1
version-misc: PVT SHIP S-OFF
serialno: FA32GW9*****
imei: 3558590500*****
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__044
battery-status: good
battery-voltage: 4318mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
gencheckpt: 0
I wish you can locate a proper RUU for my device.
I would also like to ask if it is possible to install custom ROM on my phone.
I tried to install the ViperOne 6.2.0 and Android Revolution HD 71.1 but it's both unsuccessful
now I'm stuck on Android 4.2.2 in HTC Sense 5 because i can't install new updates to KitKat and Sense 6
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/ruu-zip-m7_u_asia_wwe_custom_guruu_3-63-707-4-zip/
or any other ruu if you change your mid/cid
alray said:
http://www.htc1guru.com/dld/ruu-zip-m7_u_asia_wwe_custom_guruu_3-63-707-4-zip/
or any other ruu if you change your mid/cid
Click to expand...
Click to collapse
Sorry @alray but the file in your link returned an error while flashing
3x to flash without rebooting, returned this error:
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.103s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.549s
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.183s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.610s
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.112s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.540s
D:\HTCOne recover\HTCOneRoot>fastboot reboot
rebooting...
finished. total time: 0.038s
I think the RUU file is incompatible with my device that's why it wont proceed.
this is the filename:
RUU Zip M7_U_Asia_WWE_Custom_GuRUU_3.63.707.4.zip
Android.txt
modelid: PN0711000
modelid: PN0714000
cidnum: HTC__044
cidnum: HTC__038
mainver: 3.63.707.4
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
WilmanB said:
Sorry @alray but the file in your link returned an error while flashing
3x to flash without rebooting, returned this error:
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.103s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.549s
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.183s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.610s
D:\HTCOne recover\HTCOneRoot>fastboot flash zip RUU.zip
sending 'zip' (1206124 KB)...
OKAY [ 46.112s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 46.540s
D:\HTCOne recover\HTCOneRoot>fastboot reboot
rebooting...
finished. total time: 0.038s
I think the RUU file is incompatible with my device that's why it wont proceed.
this is the filename:
RUU Zip M7_U_Asia_WWE_Custom_GuRUU_3.63.707.4.zip
Android.txt
modelid: PN0711000
modelid: PN0714000
cidnum: HTC__044
cidnum: HTC__038
mainver: 3.63.707.4
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Click to expand...
Click to collapse
was your phone in ruu mode?
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
alray said:
was your phone in ruu mode?
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
Click to expand...
Click to collapse
yes sir it was in ruu mode. the one with green HTC logo and black background.
WilmanB said:
yes sir it was in ruu mode. the one with green HTC logo and black background.
Click to expand...
Click to collapse
try this one: http://www.htc1guru.com/dld/ruu_m7_...0-13_10-33-1150-01_release_311678_signed-exe/
otherwise, change your mid and cid and try to flash another version ruu.
Hi there.
My phone is a m7_ul, with s-on, Hboot unlocked.
Code:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4a.26.3263.05
OpenDSP-v32.120.274.0909
OS-4.19.161.11
eMMC-boot 2048MB
Mar 5 2014, 15:58:33.0
My phone has been bricked for a while. Originally water damaged, it at first wouldn't take any custom roms or wouldn't set back to stock, but eventually I managed to get it there and it was working fine, except that at random the phone died or rebooted. Eventually I tried putting a custom ROM on it again, and that didn't quite work, because of the phone randomly rebooting. And I guess here is where I went wrong (I can literally imagine you guys flinch when I say this): I hit 'factory recovery' in bootloader.
So now I can't do anything, besides going from hboot/bootloader onto 'fastboot' (and 'show barcode'). Going from hboot/bootloader onto 'recovery' brings me to fastboot. Even 'power down' or 'reboot bootloader' from fastboot brings me back to fastboot. Sometimes at random times the phone becomes unresponsive even in fastboot so that I have to do a hard reset with power and vol-down keys. The phone charges fine, only switches off when the battery is flat. As soon as it has enough power it goes into fastboot mode.
Plugged into my win8 machine it shows in device manager as 'my htc' (but not on the 'this pc'-view!).
In fastboot, I get the serial number when I enter 'fastboot devices', which is great. With 'fastboot getvar all' I get the following:
Code:
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.26.3263.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3742mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
HOWEVER Trying to flash a custom recovery (like the latest TWRP or CWM), I get following error:
Code:
c:\Android>fastboot flash recovery twrp/recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9948 KB)...
OKAY [ 1.332s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.505s
I tried this with numerous recoveries, but no luck. I managed to fastboot erase cache no problem.
but yeah. since i cant flash any recovery, i cant flash any new custom or stock rom. please please help.
herchenm said:
Hi there.
My phone is a m7_ul, with s-on, Hboot unlocked.
Code:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4a.26.3263.05
OpenDSP-v32.120.274.0909
OS-4.19.161.11
eMMC-boot 2048MB
HOWEVER Trying to flash a custom recovery (like the latest TWRP or CWM), I get following error:
[CODE]c:\Android>fastboot flash recovery [COLOR="Blue"]twrp/recovery.img[/COLOR]
target reported max download size of 1514139648 bytes
sending 'recovery' (9948 KB)...
OKAY [ 1.332s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.505s
I tried this with numerous recoveries, but no luck. I managed to fastboot erase cache no problem.
but yeah. since i cant flash any recovery, i cant flash any new custom or stock rom. please please help.
Click to expand...
Click to collapse
Remove the imei and serialno from your post.
Since you are on Win 8, you might try Win 7 or Ubuntu (nkk71 has instructions Q5).
I don't know of a way to recover what's there, maybe someone else will have a suggestion. You can always flash in, oemRUU mode, a signed RUU and later flash recovery. But, you will lose all of your data, pic, music, etc.
There are certainly other ways to recover. Anyone?
---------- Post added at 09:15 PM ---------- Previous post was at 09:09 PM ----------
I don't know of a way to recover what's there, maybe someone else will have a suggestion. You can always flash in, oemRUU mode, a signed RUU and later flash recovery. But, you will lose all of your data, pic, music, etc. This rom (http://forum.xda-developers.com/showthread.php?t=2676986) will leave you with a 1.54 hboot, so you won't downgrade to 1.44 and get stuck as the previous poster suggests.
There are certainly other ways to recover. Anyone?
majmoz said:
Remove the imei and serialno from your post.
Click to expand...
Click to collapse
done.
majmoz said:
Since you are on Win 8, you might try Win 7 or Ubuntu (nkk71 has instructions Q5).
Click to expand...
Click to collapse
not sure how that would help me? the phone is being detected and displays as 'my htc' in the windows device manager as well as with the "fastboot devices" command.
this is not the problem.
the problem is that i can't flash anything because of the returned error (image update error), which needs to be fixed but i dont know how
davidrol said:
I don't know of a way to recover what's there, maybe someone else will have a suggestion. You can always flash in, oemRUU mode, a signed RUU and later flash recovery. But, you will lose all of your data, pic, music, etc.
There are certainly other ways to recover. Anyone?
---------- Post added at 09:15 PM ---------- Previous post was at 09:09 PM ----------
I don't know of a way to recover what's there, maybe someone else will have a suggestion. You can always flash in, oemRUU mode, a signed RUU and later flash recovery. But, you will lose all of your data, pic, music, etc. This rom (http://forum.xda-developers.com/showthread.php?t=2676986) will leave you with a 1.54 hboot, so you won't downgrade to 1.44 and get stuck as the previous poster suggests.
There are certainly other ways to recover. Anyone?
Click to expand...
Click to collapse
I don't mind losing all my data. I think the phone is pretty bricked as it is, so if I could get it to work with your help, that'd be a win. Screw keeping the data haha.
I will try flashing the ROM you linked to and get back to you.
davidrol said:
you can always flash in, oemRUU mode, a signed RUU and later flash recovery
Click to expand...
Click to collapse
What do you mean with that? How do I do that? I can't get into recovery (as I cant flash that via the fastboot command) so I cant adb push/sideload
Please help
davidrol said:
This rom (http://forum.xda-developers.com/showthread.php?t=2676986) will leave you with a 1.54 hboot, so you won't downgrade to 1.44 and get stuck as the previous poster suggests.
Click to expand...
Click to collapse
can i still use that though its AT&T and my cidnum is VODAP102?
also, how do I install that ROM if I have no recovery? Im confused.
herchenm said:
can i still use that though its AT&T and my cidnum is VODAP102?
also, how do I install that ROM if I have no recovery? Im confused.
Click to expand...
Click to collapse
No you can't flash that one. You will have to find a signed RUU that matches your VODAP102 cidnum and your model number. Here's the link describing how to flash an RU in fastboot: http://forum.xda-developers.com/showthread.php?t=2251800.
davidrol said:
No you can't flash that one. You will have to find a signed RUU that matches your VODAP102 cidnum and your model number. Here's the link describing how to flash an RU in fastboot: http://forum.xda-developers.com/showthread.php?t=2251800.
Click to expand...
Click to collapse
Am I right in assuming that there isn't any RUU for my cid etc. needs? Haven't been able to found one yet maybe you can help?
Thanks for the link as well! Guess I'm gonna have to find the right RUU first
There is a way to change your cid in fastboot. I haven't the needed to so you'll need to do the research. If changing your cid isn't a problem, heres something: http://www.htc1guru.com/dld/ruu_m7_u_jb_50_htc_europe_1-29-401-2_r_radio_4a-14-3250-13_10-33-. You wont be able to flash an incorrect ruu with s-on (security on).
Sent from my SAMSUNG-SGH-I957 using xda
herchenm said:
can i still use that though its AT&T and my cidnum is VODAP102?
also, how do I install that ROM if I have no recovery? Im confused.
Click to expand...
Click to collapse
your using the wrong command to flash recovery
do it like this
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
you get the file here >> http://techerrata.com/browse/twrp2/m7
Get 2.6.3.3 no other
Your s-on you can't change CID and MID to match an AT&T RUU
your best to flash a Guru reset or a stock .401 Rom
Here's the link to change your cid to supercid: http://forum.xda-developers.com/showthread.php?t=2317536
---------- Post added at 07:33 PM ---------- Previous post was at 07:10 PM ----------
Also, put the twrp file in the same-folder-as-fastboot.
clsA said:
your using the wrong command to flash recovery
do it like this
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
you get the file here >> http://techerrata.com/browse/twrp2/m7
Get 2.6.3.3 no other
Your s-on you can't change CID and MID to match an AT&T RUU
your best to flash a Guru reset or a stock .401 Rom
Click to expand...
Click to collapse
I've been using exactly that command, and like I said, I keep getting the same error (see first post). Nonetheless I tried the recovery you linked to as well, and got the same error:
Code:
c:\Android>fastboot flash recovery or_twrp/openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.336s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.615s
I really cannot flash any recoveries.
davidrol said:
Here's the link to change your cid to supercid: http://forum.xda-developers.com/showthread.php?t=2317536
---------- Post added at 07:33 PM ---------- Previous post was at 07:10 PM ----------
Also, put the twrp file in the same-folder-as-fastboot.
Click to expand...
Click to collapse
following the instructions on the guide you linked to I get following error:
Code:
c:\Android>fastboot oem readcid
...
(bootloader) cid: VODAP102
OKAY [ 0.002s]
finished. total time: 0.003s
c:\Android>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.001s]
finished. total time: 0.003s
So I cant seem to change the CID :S
I tried changing s-on to s-off so I can change the CID. I used the moonshine s-off (http://forum.xda-developers.com/showthread.php?t=2291087 and downloaded the moonshine_m7_1.29.401.13.zip (which was the only .401 rom)
deinstalled HTC Sync Manager.
command 'fastboot devices' returned the serial number and that the phone is in fastboot-mode.
extracted the zip-file onto my computer into a separate folder, ran the distiller.exe. I confirm everything, it starts running, and then I get following error:
Code:
Ok?
(Yes/No)
Yes
!! Do NOT for any reason touch, unplug, lick or maim your device !!
Checking for updates......
Please wait....
..........
ERROR: run distiller again and READ
Press ENTER to exit
maybe I downloaded the wrong zip-file from Moonshine? Maybe i need to try this one, cause it's vodafone and obvs my CID is Voda? moonshine_m7_1.29.161.11.zip
What do you think?
Try rumrunner
SaHiLzZ said:
Try rumrunner
Click to expand...
Click to collapse
tried that. similar result:
Code:
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Press ENTER to exit
herchenm said:
I've been using exactly that command, and like I said, I keep getting the same error (see first post). Nonetheless I tried the recovery you linked to as well, and got the same error:
Code:
c:\Android>fastboot flash recovery or_twrp/openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.336s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.615s
Click to expand...
Click to collapse
i hate to be the bearer of bad news, but pretty sure your phone is a goner
can you try the following command:
fastboot oem rebootRUU
do you get to RUU mode?
you're probably also unable to relock and unlock you device, correct?
nkk71 said:
i hate to be the bearer of bad news, but pretty sure your phone is a goner
can you try the following command:
fastboot oem rebootRUU
do you get to RUU mode?
you're probably also unable to relock and unlock you device, correct?
Click to expand...
Click to collapse
fastboot oem rebootRUU gives me the following (but the bootloader isnt locked, which I think I need to do first, no?)
Code:
c:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.065s]
finished. total time: 1.067s
herchenm said:
fastboot oem rebootRUU gives me the following (but the bootloader isnt locked, which I think I need to do first, no?)
Code:
c:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.065s]
finished. total time: 1.067s
Click to expand...
Click to collapse
nope sorry mate, it's a goner, your phone is fried
time for a new phone, sorry
nkk71 said:
nope sorry mate, it's a goner, your phone is fried
time for a new phone, sorry
Click to expand...
Click to collapse
i locked the bootloader now and got this
Code:
c:\Android>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.157s
and on the screen of the phone it says
Code:
*** tampered ***
*** relocked ***
*** security warning ***
{followed by the rest}
what does that 'security warning' and the error in the relocking of bootloader mean?
herchenm said:
i locked the bootloader now and got this
Code:
c:\Android>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.157s
and on the screen of the phone it says
Code:
*** tampered ***
*** relocked ***
*** security warning ***
{followed by the rest}
what does that 'security warning' and the error in the relocking of bootloader mean?
Click to expand...
Click to collapse
security warning is because you are not on [your] stock version
but it doesn't matter, the phone is fried
i'm really sorry
PS: i'm actually surprised the lock command worked
Dear all,
My friend's phone is always rebooting and isn't working, even, I have tried to enter recovery no use, even, I have tried to install custom recovery no use.
I have downloaded many firmwares and it's not working, even the Original HTC ROMs can't update the phone with Signature Error, I read many forum threads but, the information isn't clear for me and didn't find a direct steps to follow, I really appreciate your help,
The device is showing
********** TAMPERED ********
********** RELOCKED ********
M7_UL IVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO -4T.29.3218.08
OpenDSP-v32.120.274.0909
OS-6.09.401.5
wMMC-boot 2048MB
I got the fastboot getvar all for your reference.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXX
(bootloader) imei: xxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4299mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.087s
Click to expand...
Click to collapse
Thanks in advance
magcp said:
Dear all,
My friend's phone is always rebooting and isn't working, even, I have tried to enter recovery no use, even, I have tried to install custom recovery no use.
I have downloaded many firmwares and it's not working, even the Original HTC ROMs can't update the phone with Signature Error, I read many forum threads but, the information isn't clear for me and didn't find a direct steps to follow, I really appreciate your help,
The device is showing
********** TAMPERED ********
********** RELOCKED ********
M7_UL IVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO -4T.29.3218.08
OpenDSP-v32.120.274.0909
OS-6.09.401.5
wMMC-boot 2048MB
I got the fastboot getvar all for your reference.
Thanks in advance
Click to expand...
Click to collapse
You can unlock the bootloader, flash twrp 2.8.5.0 and restore this backup: https://www.androidfilehost.com/?fid=23622183712472331 then flash back the stock 6.09.401.5 recovery.
Or
Keep the bootloader relocked and flash the 7.19.401.2 RUU: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
btw remove your imei and serialno from your post above.
Hi, Thank you so much, I'll try both methods and I'll let you know,
PS: I have removed the IMEI, thanks for letting me know.
Kind regards,
alray said:
You can unlock the bootloader, flash twrp 2.8.5.0 and restore this backup: https://www.androidfilehost.com/?fid=23622183712472331 then flash back the stock 6.09.401.5 recovery.
Or
Keep the bootloader relocked and flash the 7.19.401.2 RUU: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
btw remove your imei and serialno from your post above.
Click to expand...
Click to collapse
alray said:
You can unlock the bootloader, flash twrp 2.8.5.0 and restore this backup: https://www.androidfilehost.com/?fid=23622183712472331 then flash back the stock 6.09.401.5 recovery.
Or
Keep the bootloader relocked and flash the 7.19.401.2 RUU: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
btw remove your imei and serialno from your post above.
Click to expand...
Click to collapse
Hi, I have tried to flash the lolipop ruu, and it gave me this error (using htc_fastboot):
sending 'zip'... (43283 KB) OKAY
sending time = 3.511 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 9(s)
Plus, I can't unlock the bootloader it is still stating relocked
magcp said:
Hi, I have tried to flash the lolipop ruu, and it gave me this error (using htc_fastboot):
sending 'zip'... (43283 KB) OKAY
sending time = 3.511 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 9(s)
Plus, I can't unlock the bootloader it is still stating relocked
Click to expand...
Click to collapse
is your phone booted in ruu mode?
alray said:
is your phone booted in ruu mode?
Click to expand...
Click to collapse
Yes, it is
magcp said:
Hi, I have tried to flash the lolipop ruu, and it gave me this error (using htc_fastboot):
sending 'zip'... (43283 KB) OKAY
sending time = 3.511 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 9(s)
Plus, I can't unlock the bootloader it is still stating relocked
Click to expand...
Click to collapse
magcp said:
Yes, it is
Click to expand...
Click to collapse
43283 kb only? Its 42 Mb only, you are either not flashing the right file or the file is corrupted. The 7.19.401.2 ruu is 1.56 Gb so fastboot should report:
Code:
sending 'zip'... [B][COLOR="Red"](1637620 KB)[/COLOR][/B] OKAY.
alray said:
43283 kb only? Its 42 Mb only, you are either not flashing the right file or the file is corrupted. The 7.19.401.2 ruu is 1.56 Gb so fastboot should report:
Code:
sending 'zip'... [B][COLOR="Red"](1637620 KB)[/COLOR][/B] OKAY.
Click to expand...
Click to collapse
Hi, Thanks for your reply, I really don't know, I can confirm that the file is 1.56 GB on Disk, I can't open it with WinRar or Zip7 but, I downloaded this file twice, I'll try again in few hours and I'll let you know, by the way, I have flashed the 5.1 on my Nexus 6 and it was sending the file in chunks but, I don't know about HTC,
Thanks again
magcp said:
Hi, Thanks for your reply, I really don't know, I can confirm that the file is 1.56 GB on Disk, I can't open it with WinRar or Zip7 but, I downloaded this file twice, I'll try again in few hours and I'll let you know, by the way, I have flashed the 5.1 on my Nexus 6 and it was sending the file in chunks but, I don't know about HTC,
Thanks again
Click to expand...
Click to collapse
By the way, I have tried the EXE file and it gave me Signature error as well, so, I guess it's not corrupted zip file.
Any ideas???
I don't know why it is not accepting to unlock the phone, I tried it many times, and it's "RELOCKED"
Thanks
magcp said:
By the way, I have tried the EXE file and it gave me Signature error as well, so, I guess it's not corrupted zip file.
Any ideas???
I don't know why it is not accepting to unlock the phone, I tried it many times, and it's "RELOCKED"
Thanks
Click to expand...
Click to collapse
whats wrong when trying to unlock the bootloader?
alray said:
whats wrong when trying to unlock the bootloader?
Click to expand...
Click to collapse
I don't know, I execute this command and I got this results:
C:\...\Downloads>fastboot flash unlocktoken "Unlock_code (1).bin"
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.013s]
finished. total time: 0.157s
Click to expand...
Click to collapse
Then, I choose YES then POWER, the phone restarts but nothing happens, it CAN NOT enter RECOVERY just white screen saying "Entering Recovery..." then after a while a black screen appears and stays there, then, I press VOL Down + POWER to enter fastboot. and "RELOCKED" message is there.
Thanks
magcp said:
I don't know, I execute this command and I got this results:
Then, I choose YES then POWER, the phone restarts but nothing happens, it CAN NOT enter RECOVERY just white screen saying "Entering Recovery..." then after a while a black screen appears and stays there, then, I press VOL Down + POWER to enter fastboot. and "RELOCKED" message is there.
Thanks
Click to expand...
Click to collapse
looks like your bootloader was relocked with a custom recovery. You can't unlock the bootloader if a custom recovery is installed and you can't boot to your custom recovery if the bootloader is relocked. You will have to reflash the stock firmware.
download the firmware from here: https://www.androidfilehost.com/?fid=23622183712460395
Code:
fastboot oem rebootRUU
fastboot flash zip 6.09.401.5_signed_firmware.zip
fastboot flash zip 6.09.401.5_signed_firmware.zip
fastboot reboot-bootloader
then get a new unlock_code.bin
Code:
fastboot oem get_identifier_token
submit the token to htcdev.com/bootloader and wait for your unlock_code.bin
Code:
fastboot flash unlocktoken Unlock_code.bin
alray said:
looks like your bootloader was relocked with a custom recovery. You can't unlock the bootloader if a custom recovery is installed and you can't boot to your custom recovery if the bootloader is relocked. You will have to reflash the stock firmware.
download the firmware from here: https://www.androidfilehost.com/?fid=23622183712460395
Code:
fastboot oem rebootRUU
fastboot flash zip 6.09.401.5_signed_firmware.zip
fastboot flash zip 6.09.401.5_signed_firmware.zip
fastboot reboot-bootloader
then get a new unlock_code.bin
Code:
fastboot oem get_identifier_token
submit the token to htcdev.com/bootloader and wait for your unlock_code.bin
Code:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
When trying to flash the zip it said:
Code:
sending 'zip' (44368 KB)...
OKAY [ 3.349s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.281s
magcp said:
When trying to flash the zip it said:
Code:
sending 'zip' (44368 KB)...
OKAY [ 3.349s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.281s
Click to expand...
Click to collapse
can you post a complete screenshot of your command prompt please?
Here you are,
htc_fastboot.exe
is the same as
fastboot.exe
but, I was just checking
Thanks
magcp said:
Here you are,
htc_fastboot.exe
is the same as
fastboot.exe
but, I was just checking
Thanks
Click to expand...
Click to collapse
you must reboot in ruu mode before flashing the zip:
Code:
fastboot oem rebootRUU
Phone will reboot to a black screen with silver HTC logo
alray said:
you must reboot in ruu mode before flashing the zip:
Code:
fastboot oem rebootRUU
Phone will reboot to a black screen with silver HTC logo
Click to expand...
Click to collapse
I did already,
magcp said:
I did already,
Click to expand...
Click to collapse
Well its very strange, with s-on and relocked bootloader you should be able to flash this firmware. Don't know why the signature verification is failing. Try with this one: https://www.androidfilehost.com/?fid=23622183712462447
or this one: https://www.androidfilehost.com/?fid=23622183712459334
You can also try to extract the firmware.zip from this ota: https://www.androidfilehost.com/?fid=23622183712458585 and flash it
and always make sure your MD5 match before flashing.
alray said:
Well its very strange, with s-on and relocked bootloader you should be able to flash this firmware. Don't know why the signature verification is failing. Try with this one: https://www.androidfilehost.com/?fid=23622183712462447
or this one: https://www.androidfilehost.com/?fid=23622183712459334
You can also try to extract the firmware.zip from this ota: https://www.androidfilehost.com/?fid=23622183712458585 and flash it
and always make sure your MD5 match before flashing.
Click to expand...
Click to collapse
I have verified the first two and tried and still, signature error, is there something wrong with the bootloader?? can I flash another bootloader?
alray said:
Well its very strange, with s-on and relocked bootloader you should be able to flash this firmware. Don't know why the signature verification is failing. Try with this one: https://www.androidfilehost.com/?fid=23622183712462447
or this one: https://www.androidfilehost.com/?fid=23622183712459334
You can also try to extract the firmware.zip from this ota: https://www.androidfilehost.com/?fid=23622183712458585 and flash it
and always make sure your MD5 match before flashing.
Click to expand...
Click to collapse
I have downloaded the OTA and after verifying, I extracted the firmware.zip and flash it, and still Signature Error
Code:
C:\Users\MAG\Downloads>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.035s]
finished. total time: 0.036s
C:\Users\MAG\Downloads>fastboot flash zip firmware.zip
sending 'zip' (44368 KB)...
OKAY [ 3.255s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.187s