Hi,
Searched xda, tried few methods, but cant root and put cwm on my device.
Only think that was done now, is unlocking bootloader via htc dev.
Any ideas which root method will work and how to put cwm on it?
Android: 2.2
Baseband: 47.51.35.17U_7.13.35.05
Kernel: 26.32.17
Build/software nr: 3.15.405.3
Hboot 1.02.0000
****unlocked*****
Legend PVT Ship ON
Radio: 7.13.35.05
Managed to root via htc super tool, but stock on getting cwm.
AS my phone is htc-dev unlocked, with s-on shown in bootloader, i tried both methods from here:
http://forum.xda-developers.com/showthread.php?t=1290841&page=3
doesnt work, adb says:
D:\HTC\Android_Fastboot_KIT_V2.1>fastboot flash boot boot.img
sending 'boot' (3136 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: image update error)
Just tried this also, doesnt work...
D:\HTC\Android_Fastboot_KIT_V2.1>fastboot flash recover recovery_legend_5.0.2.8.
img
sending 'recover' (3136 KB)...
OKAY [ 0.382s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.026s
k, tried some tricks from my HOX, it did the job.
Any way to mount sd-ext under stock rom and to move most of the apps to it?
Any scripts, apps for that?
Stegy said:
Just tried this also, doesnt work...
D:\HTC\Android_Fastboot_KIT_V2.1>fastboot flash recover recovery_legend_5.0.2.8.
img
sending 'recover' (3136 KB)...
OKAY [ 0.382s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.026s
Click to expand...
Click to collapse
Check your command you typed it should not be recover it should be recovery
Sent from my Legend using xda app-developers app
I had tried a CWM build and decided to go back to stock as there were issues with the keyboard.
I have RUU_Puccini_LTE_Rogers_WWE_1.26.631.4_Radio_1.05.550I.09v2_30.68.550I.12_release_219377_signed
I re-locked my device and when I run the RRU it fails "Partition Update Failed" error and it is the SBL1 partition
Any ideas
Home screen
Relocked
Security Warning
Puccinilte PVT Ship S-on RL
Hboot-1.78.0010
eMMC-boot
Aug 30 2011,22:25:56
When I try to flash boot.img from the RUU
fastboot flash boot boot.img
sending 'boot' (3730 KB)...
OKAY [ 0.401s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.048s
More info:
ERROR [152]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
I have also tried RUU_Puccini_LTE_Rogers_WWE_1.26.631.4_Radio_1.05.550I.09v2_30.68.550I.12_release_219377_signed and received the same error
Well I know you cannot flash a boot.img through fastboot unless your bootloader is unlocked or you are S-OFF, so that explains why that fails.
As for the RUU failing to run, try running it while in fastboot. Also, try re-downloading either of these Roger's RUUs:
http://www.androidfiles.org/ruu/?dir=Puccini
So I tried the flash-all to update to new version, and it failed with the system.img error everyone talks about.
I saw that that was common, so I went ahead with flashing each image separately. However, when I try to flash the bootloader, I get the following error:
E:\adb\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk
\platform-tools>fastboot flash bootloader boot.img
target reported max download size of 518205818 bytes
sending 'bootloader' (8278 KB)...
OKAY [ 0.555s]
writing 'bootloader'...
(bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: header error)
finished. total time: 1.143s
Any idea how to fix this? Googling it didn't come up with anything. I just downloaded the newest version of fastboot by updating the android SDK today, so I don't think it's that.
I got the exact same error when I tried flashing my Nexus 5, before attempt my Nexus 9. I actually uninstalled the SDK and dowloaded and installed a whole fresh version and the Flash All script worked fine after that for both the N5 and N9. Both have been running great! The animations, volume slider for exampt, are so much smoother in M. Lots of little tweaks.
If it's working properly on the N9, fastboot will sparse the System image and send it to the device in multiple uploads and flashes.
Of course you would have failed. You have done it the wrong way. The bootloader command should be like:
fastboot flash bootloader bootloader.img
but you flashed bootloader with kernel boot.img
Hey everyone,
I lately tried to root my HTC One M8, but due to some mistakes I got stuck and just have access to the bootloader,but I'm not able to get in my phone. I've have unlocked the bootloader and have S-On. I would be pleased, if someone could tell me how I reset my phone to factory state. I'm pretty new to such things, so let me know if you need further informations. I really hope that you guys can help me, all of this made so frustrated.
Thanks in advance
Matthew F.
You have access to Bootloader. Can you Boot into recovery? There you will find a selection for factory reset.
http://www.androidcentral.com/sites...arge/public/postimages/108579/m7-recovery.jpg
I can't confirm that's the best course to take, but its there if recovery is.......
If that does not work, then you will need to relock the bootloader and run the RUU for your variant of the M8, and it must be the same version or newer. You can not downgrade while S-On.
Cremnomaniac said:
You have access to Bootloader. Can you Boot into recovery? There you will find a selection for factory reset.
I can't confirm that's the best course to take, but its there if recovery is.......
Click to expand...
Click to collapse
I can't get in recovery, it just goes back to the bootloader
es0tericcha0s said:
If that does not work, then you will need to relock the bootloader and run the RUU for your variant of the M8, and it must be the same version or newer. You can not downgrade while S-On.
Click to expand...
Click to collapse
I tried to install the ruu, but everytime I get this message 'Error 120: low main battery' and the install Setup stops
It has to be above 30% before it will run, if I remember right.
es0tericcha0s said:
It has to be above 30% before it will run, if I remember right.
Click to expand...
Click to collapse
Yeah that's right, but my battery is about 70%
It might not be due to the software being messed up and the bright white screen of the bootloader. You can try extracting the rom.zip from the RUU exe and flashing via fastboot manually. http://forum.xda-developers.com/showthread.php?t=2497614 - this is for the M7 but the same basic principles apply. I don't believe that it requires the 30% this method, but it's been a bit since I have flashed manually.
es0tericcha0s said:
It might not be due to the software being messed up and the bright white screen of the bootloader. You can try extracting the rom.zip from the RUU exe and flashing via fastboot manually. http://forum.xda-developers.com/showthread.php?t=2497614 - this is for the M7 but the same basic principles apply. I don't believe that it requires the 30% this method, but it's been a bit since I have flashed manually.
Click to expand...
Click to collapse
so, I've followed this guide, but now I'm stuck again. Everytime I type in this command 'fastboot flash zip C:/mini-sdk/rom.zip' I get a error-message 'target reported max download size of 1826418688 Bytes error: cannot load 'C:/mini-sdk/Rom.zip'.
Any ideas for that?
Is the rom zip IN the folder titled C:/mini-sdk?
Yes, it is.
es0tericcha0s said:
Is the rom zip IN the folder titled C:/mini-sdk?
Click to expand...
Click to collapse
Yes, it is.
If your command prompt is already pointed to the adb/fastboot folder then you should be able to just use the command:
fastboot flash zip rom.zip
instead of fastboot flash zip C:/blahblahblah
es0tericcha0s said:
If your command prompt is already pointed to the adb/fastboot folder then you should be able to just use the command:
fastboot flash zip rom.zip
instead of fastboot flash zip C:/blahblahblah
Click to expand...
Click to collapse
The command prompt is already pointed in the adb/fastboot Folder, but i still get the same error ('target reported max download size of...'). Do my phone has to be unlocked or locked, S-on or S-off at that Moment?
Locked if S-On. S-Off, either way.
es0tericcha0s said:
Locked if S-On. S-Off, either way.
Click to expand...
Click to collapse
hmm... it already was relocked and s-on. What do I have to do?
and the Software Status says 'Modified', if that's necessary
Matthew F. said:
so, I've followed this guide, but now I'm stuck again. Every time I type in this command 'fastboot flash zip C:/mini-sdk/rom.zip' I get a error-message 'target reported max download size of 1826418688 Bytes error: cannot load 'C:/mini-sdk/Rom.zip'.
Any ideas for that?
Click to expand...
Click to collapse
I'm not sure this is the problem, but it sounds familiar. It may be the version of adb/fastboot you're using. Try using this one posted by Dottat.
Its the Fastboot link at the bottom of the OP
http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
Read about the options for installing RUUs. There's a few.
PS - Its customary when asking for help to provide some basic info about your phone. I don't see that you have even mentioned which ROM your currently running. There are RUUs for s-on and s-off.
Cremnomaniac said:
I'm not sure this is the problem, but it sounds familiar. It may be the version of adb/fastboot you're using. Try using this one posted by Dottat.
Its the Fastboot link at the bottom of the OP
http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
Read about the options for installing RUUs. There's a few.
PS - Its customary when asking for help to provide some basic info about your phone. I don't see that you have even mentioned which ROM your currently running. There are RUUs for s-on and s-off.
Click to expand...
Click to collapse
Sorry sir, I'm using this ROM https://www.androidfilehost.com/?fid=95916177934546378 (should be the right one) and here are some Infos about my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH485WM02248
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 21(ms)
I also downloaded Dottat's fastboot/adb Version and typed in following commands:
-fastboot oem rebootRUU (no Problem with this command)
-fastboot Flash zip 0P6B10000.zip (renamed it after my mid)
But then I get this error-message:
C:\Users\Frank\Desktop\HTC_fastboot_adb>fastboot flash zip 0P6B10000.zip
sending 'zip'... (46606 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
FAIL32 header error
FAILED (remote: 32 header error)
Execution time is 8(s)
Any ideas for this Problem?
PS - I wouldn't have come this far without your help, so thank you
Matthew F. said:
Sorry sir, I'm using this ROM https://www.androidfilehost.com/?fid=95916177934546378 (should be the right one)
I also downloaded Dottat's fastboot/adb Version and typed in following commands:
-fastboot oem rebootRUU (no Problem with this command)
-fastboot Flash zip 0P6B10000.zip (renamed it after my mid)
But then I get this error-message:
C:\Users\Frank\Desktop\HTC_fastboot_adb>fastboot flash zip 0P6B10000.zip
sending 'zip'... (46606 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
FAIL32 header error
FAILED (remote: 32 header error)
Execution time is 8(s)
Any ideas for this Problem?
PS - I wouldn't have come this far without your help, so thank you
Click to expand...
Click to collapse
May I suggest that you do some more research BEFORE you use that file.
The file you link to is an RUU! Executable. I know, I just downloaded it and opened it to be sure.
If your renaming it, and trying to use fastboot, you are using the wrong file. The file your trying to flash is NOT flash-able via fastboot. Again, its an RUU.exe file. If you don't know what that is, you shouldn't be using it.
Do some research on RUU's......
i've lost my lost my imei during restoring a back up through twrp, then i encounter "Your device is corrupt. It cannot be trusted and will not boot". then i've flash a kdz H85010i_00_OPEN_EU_OP_0923.kdz, then when i try to reunlock my bootloader this is the result.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.035s]
writing 'unlock'...
(bootloader) ----------------------------------
(bootloader) Device-ID
(bootloader) 1C7832DD225B0CB8263BC96BB2F36819
(bootloader) B648B077E9D51C1E7B6290DB93F87B4D
(bootloader) ----------------------------------
(bootloader) IMEI
(bootloader) 000000000000000
(bootloader) ----------------------------------
(bootloader) Error!!
(bootloader) Wrong Bootloader Unlock key
FAILED (remote failure)
finished. total time: 0.159s
Me too
Im having the same problem... haven't found a solution yet but Im continuing to look!
Does anyone else have any ideas? I got into this position after the following:
Bricked my phone after wiping the misc partition - got certificate errors
Used LGUP and Uppercut to install v20d
Now, when I try to re-unlock I get the error above.
*#06# shows my IMEI correctly, it's just in the bootloader where it doesn't (which seems pretty odd). Im currently planning to try a different \ older kdz to see if that helps
FIXED IT!
Good news, I found a fix!
All I had to do was a factory reset (via LG Stock recovery steps) (I didn't use the older KDZ in the end). After that, I rebooted to bootloader and successfully flashed my existing unlock.bin
Not sure why this helped. After running LGUP, I noticed that I had all of my older apps still installed, but nothing was properly working (e.g. couldn't even copy files in File Manager). I suspect the factory reset removed whatever was upsetting the bootloader.
Hope this helps! Good luck