Related
I have serious trouble.
I tried unroot my phone but when I tried to install original ROM, I got message about fail. I rebooted the phone into recovery and restored nand backup.
I tried newer ROM. This rans longer, updated HBOOT from 1.09 to 1.13 and removed root (now I have S-ON) but then I got error "Main Version is older!" Now I can boot only info boorloader. When I use ROM in file PG32IMG.zip I got error message again.
Can anybody help me? I don't need S-OFF but I need working phone
HTC Incredible S, previous ROM was CyanogenMod 7.1 nightly, HBOOT was 1.09 but now is 1.13.
Then I try use alpharev I have no connection to phone. Driver manager says that device is working properly but then I got message that it was not recognized.
I really need drivers to connect phone un fastboot and made S-OFF again or install stock ROM (this rather). How I can recognize the right ROM?
Thanks!
P.S. I looked into forum but all solutions are for dirrerent phones
Your going to have to remove your sd card and load it into your computer with another device and replace the pg32img.zip file with another Rom.... I think.
itsbeertimenow said:
Your going to have to remove your sd card and load it into your computer with another device and replace the pg32img.zip file with another Rom.... I think.
Click to expand...
Click to collapse
I tried this but I don't know which ROM is correct for me. I tried three ROMs and every ends with error or with no message but also no effect
I want to help dude but I've never heard of this. Are you flashing a froyo or gingerbread Rom?
libb said:
I have serious trouble.
I tried unroot my phone but when I tried to install original ROM, I got message about fail. I rebooted the phone into recovery and restored nand backup.
I tried newer ROM. This rans longer, updated HBOOT from 1.09 to 1.13 and removed root (now I have S-ON) but then I got error "Main Version is older!" Now I can boot only info boorloader. When I use ROM in file PG32IMG.zip I got error message again.
Can anybody help me? I don't need S-OFF but I need working phone
HTC Incredible S, previous ROM was CyanogenMod 7.1 nightly, HBOOT was 1.09 but now is 1.13.
Then I try use alpharev I have no connection to phone. Driver manager says that device is working properly but then I got message that it was not recognized.
I really need drivers to connect phone un fastboot and made S-OFF again or install stock ROM (this rather). How I can recognize the right ROM?
Thanks!
P.S. I looked into forum but all solutions are for dirrerent phones
Click to expand...
Click to collapse
dude are you stuck at security warning bootloader???
Sent from my HTC Incredible S using xda premium
santhoshpirate said:
dude are you stuck at security warning bootloader???
Click to expand...
Click to collapse
Yes
I can run fastboot and bootloader. But I cannot connect to phone from Windows.
itsbeertimenow said:
I want to help dude but I've never heard of this. Are you flashing a froyo or gingerbread Rom?
Click to expand...
Click to collapse
I flashed Gingerbread.
I tried this ROMS in this order:
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.0225_2_NV_VZW1.92_release_181303_signed.exe (cleared CM7.1 but not recovery)
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe (cleared recovery and S-OFF, Error message)
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe (nothing, load, check then nothing - try to flash from card)
libb said:
Yes
I can run fastboot and bootloader. But I cannot connect to phone from Windows.
Click to expand...
Click to collapse
read the post carefully!
http://forum.xda-developers.com/showpost.php?p=18706124&postcount=6
santhoshpirate said:
read the post carefully!
http://forum.xda-developers.com/showpost.php?p=18706124&postcount=6
Click to expand...
Click to collapse
I read it twice.
Now I can connect via fastboot.exe but I have problem with versions.
Whe I try flash ROM, I got this:
Code:
sending 'zip' (293453 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: 12 signature verify fail)
or this
Code:
sending 'zip' (262360 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
fastboot getvar all returns:
Code:
INFOversion: 0.5
INFOversion-bootloader: 1.13.0000
INFOversion-baseband: 3805.06.03.03_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.32.1010.1
INFOserialno: HT12WTD01939
INFOimei: 355301040865167
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4010mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8a731c6e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
I desperated because I flashed before latest radio and I'm afraid that the mainver is too high. Can you please advice me which ROM I could use?
On display I see:
*** Security Warning ***
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3805.06.03.03_M
eMMC-boot
Apt 1 2011, 18:34:39
use "fast boot getvar all" to get the mainver is. And than go to "h ttp://goo-inside.me/ruu/vivo" to download a new PG32IMG.zip
Delete the space between h and t.
---------- Post added at 10:01 AM ---------- Previous post was at 09:55 AM ----------
1.go to "goo-inside.me/ruu/vivo/full" and download "PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip"
2.Flash it
3.revolutionary S-OFF
4.use adb and misc_version to write a new version that you are pending to flash.
5.reboot to Bootloader
6.Make a cup of coffee
7.OK
keroro430 said:
download "PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip"
2.Flash it
Click to expand...
Click to collapse
Code:
c:\SDK_15\platform-tools>fastboot flash zip PG32IMG_Vivo_Gingerbread_S_KT_KR_2.3
2.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip
sending 'zip' (262360 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
What could be wrong?
P.S. I have removed SIM and also microSD card, i't ok?
When I flash it via RUU, I got:
Code:
c:\SDK_15\platform-tools>fastboot reboot
rebooting...
c:\SDK_15\platform-tools>fastboot erase cache
erasing 'cache'... OKAY
c:\SDK_15\platform-tools>fastboot oem rebootRUU
... OKAY
c:\SDK_15\platform-tools>fastboot flash zip PG32IMG_Vivo_Gingerbread_S_KT_KR_2.3
2.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip
sending 'zip' (262360 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
Okay this is really old and from the evo xda threads but check it out it describes unbricking evo phones that were bricked by installing old ruu's. I'm not saying to follow this at all but it might lead you to try a different method of flashing I dunno
h ttp://forum.xda-developers.com/showthread.php?t=654119
Your going to have to mess around til you get it. Just don't let your battery get too low. Also make sure the radio isn't in the packaged zip your flashing, its not vital.
Create a goldcard, and copy the PG32IMG.zip to the root of sdcard(goldcard),enter the hboot and flash it.
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
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.
Over the weekend my phone died and somehow it got stuck in boot loop with tempered flag, I reflashed the recovery from TWRP to Clockwork and factory reset, it returned back to stock..sort of.
Everything had been slow ever since the latest OTA, hence the unlock, root and recovery change but I didn't flash any rom. Until today. I tried flashing "Android Revolution HD 81.0"
Now it won't boot through, at most I get now is bootloader/fastboot/recovery or stuck on green HTC screen.
I tired using RUU via exe (can't find zip because htc1guru.com appears to be down) and it gets stuck at checking header 5%
Issues: S-ON/Hboot 1.57/No USB Debug=no adb=no firewater
I've followed every how-to there is, but all of them require USB debug in some way, I can't get into the phone to get it down, therefore adb doesn't work. at most I have are fastboot commands.
Im at my wits. I just want to get it back to stock, to do that I would need S-off or even just have a RUU that works. This is the RUU:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
I've relocked it prior to update RUU but it didn't make a difference except preventing me to enter recovery for other tasks.
ANY help is appreciated
Here are my fastboot getvar all info:
C:\AndroidSDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXX
(bootloader) imei:XXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(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.108s
Click to expand...
Click to collapse
PlinXoom said:
Over the weekend my phone died and somehow it got stuck in boot loop with tempered flag, I reflashed the recovery from TWRP to Clockwork and factory reset, it returned back to stock..sort of.
Everything had been slow ever since the latest OTA, hence the unlock, root and recovery change but I didn't flash any rom. Until today. I tried flashing "Android Revolution HD 81.0"
Now it won't boot through, at most I get now is bootloader/fastboot/recovery or stuck on green HTC screen.
I tired using RUU via exe (can't find zip because htc1guru.com appears to be down) and it gets stuck at checking header 5%
Issues: S-ON/Hboot 1.57/No USB Debug=no adb=no firewater
I've followed every how-to there is, but all of them require USB debug in some way, I can't get into the phone to get it down, therefore adb doesn't work. at most I have are fastboot commands.
Im at my wits. I just want to get it back to stock, to do that I would need S-off or even just have a RUU that works. This is the RUU:
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
I've relocked it prior to update RUU but it didn't make a difference except preventing me to enter recovery for other tasks.
ANY help is appreciated
Here are my fastboot getvar all info:
Click to expand...
Click to collapse
You must flash ARHD using TWRP 2.6.3.3
you can not use older RUU version to restore your phone with S-ON
You can restore your phone back to stock using a nandroid backup of your version and then flash the stock recovery back.
USB debugging is only needed to use ADB when the phone is booted in the OS. Or you can also use ADB from custom recovery even if USB debug is NOT turned on.
So depending what your goal is you should try to either flash TWRP 2.6.3.3 and reflash ARHD or restore your phone using a nandroid backup if the latest dev edition software.
PlinXoom said:
Over the weekend my phone died and somehow it got stuck in boot loop with tempered flag, I reflashed the recovery from TWRP to Clockwork and factory reset, it returned back to stock..sort of.
Everything had been slow ever since the latest OTA, hence the unlock, root and recovery change but I didn't flash any rom. Until today. I tried flashing "Android Revolution HD 81.0"
Now it won't boot through, at most I get now is bootloader/fastboot/recovery or stuck on green HTC screen.
I tired using RUU via exe (can't find zip because htc1guru.com appears to be down) and it gets stuck at checking header 5%
Issues: S-ON/Hboot 1.57/No USB Debug=no adb=no firewater
Click to expand...
Click to collapse
alray is correct, you can not flash that RUU because you are S-ON and it is a lower version than your present phone. There is no RUU for your version at the moment only an OTA. Here is the stock firmware for your version. This would give you stock recovery, stock hboot but it may wipe all of your personal data off of the phone. Place the file in your fastboot/adb folder and rename it firmware.zip. Then you would flash it in bootloader/FASTBOOT USB:
Code:
[B][I]fastboot oem lock[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
After the reboot, you can install TWRP and then flash ARHD 81.0.
C:\AndroidSDK\sdk\platform-tools>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.146s
C:\AndroidSDK\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.034s]
finished. total time: 0.034s
C:\AndroidSDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47665 KB)...
OKAY [ 2.657s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.713s
C:\AndroidSDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47665 KB)...
OKAY [ 2.653s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.709s
C:\AndroidSDK\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (47665 KB)...
OKAY [ 2.653s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.710s
C:\AndroidSDK\sdk\platform-tools>
Click to expand...
Click to collapse
I downloaded the file and flashed it, that's what I got.
I went ahead and flashed TWRP 2.6.3.3, that allowed me to have ADB and then I sideloaded the ARHD, now it's working and im setting up.
Question, now that I have the OS back, how should I go about getting S-off and the tampered warning removed. I presume this would save me from loads of trouble down the load. Thanks again in advance.
PlinXoom said:
I went ahead and flashed TWRP 2.6.3.3, that allowed me to have ADB and then I sideloaded the ARHD, now it's working and im setting up.
Question, now that I have the OS back, how should I go about getting S-off and the tampered warning removed. I presume this would save me from loads of trouble down the load. Thanks again in advance.
Click to expand...
Click to collapse
Achieve S-OFF with firewater or sunshine
Download and install this Bootloader Reset Tool
I went ahead and tried with firewater but ran into HTC anti firewater warning. I was told I needed to go back to stock Rom with bulletproof kernel to get it to work then load ARHD after. Being that if I don't intend to change the Rom any time soon, is it worth doing all the swapping around?
PlinXoom said:
I went ahead and tried with firewater but ran into HTC anti firewater warning. I was told I needed to go back to stock Rom with bulletproof kernel to get it to work then load ARHD after. Being that if I don't intend to change the Rom any time soon, is it worth doing all the swapping around?
Click to expand...
Click to collapse
If you develop an issue down the road it is easier to fix with the phone being S-OFF. However, it is a personal choice.
I figured as much, thanks again! :highfive:
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