So last week a friend asked me to s-off his phone for him.. The phone ended up bricking (recovery gone, no os, etc...)..
Where I am at:
1. The phone is S-ON (Actually says "Monarudo PVT Ship S-ON"
2. The phone has an unlocked boot loader
3. The phone has TWRP 2.4 installed
4. HBoot 1.33
5. Radio 1.01.01.0110
6. OpenDSP v6.120.274.0114
7. eMMC-boot
8. The phone has a 4.1.1 based rom installed (Tried carbon 4.3 based, same issue and CM 4.2 based, same issue)
I have tried moonshine and face's s-off with no luck. I get about half way through with moonshine and it just sits there counting, adding periods.
I have tried :
1. Flashing a stock hboot 1.15
2. Flashing the stock splash
3. Flashing the stock RUU
Issues :
1. The phone gets NO reception Just the X with empty bars. I don't know if its the radio or something. Every once and a while I get 2 bars for a second but it goes away.
PLEASE HELP! I feel horrible that my buddy has to borrow my bionic until this is fixed.
when I tried the stock RUU from HTC it gets to a point and fails telling me incorrect image or seomthing like that.. Should have written it down, I can run it again if the error helps.
janderson2k said:
when I tried the stock RUU from HTC it gets to a point and fails telling me incorrect image or seomthing like that.. Should have written it down, I can run it again if the error helps.
Click to expand...
Click to collapse
Have you tried doing moonshine in ubuntu live cd/usb?
janderson2k said:
So last week a friend asked me to s-off his phone for him.. The phone ended up bricking (recovery gone, no os, etc...)..
Where I am at:
1. The phone is S-ON (Actually says "Monarudo PVT Ship S-ON"
2. The phone has an unlocked boot loader
3. The phone has TWRP 2.4 installed
4. HBoot 1.33
5. Radio 1.01.01.0110
6. OpenDSP v6.120.274.0114
7. eMMC-boot
8. The phone has a 4.1.1 based rom installed (Tried carbon 4.3 based, same issue and CM 4.2 based, same issue)
I have tried moonshine and face's s-off with no luck. I get about half way through with moonshine and it just sits there counting, adding periods.
I have tried :
1. Flashing a stock hboot 1.15
2. Flashing the stock splash
3. Flashing the stock RUU
Issues :
1. The phone gets NO reception Just the X with empty bars. I don't know if its the radio or something. Every once and a while I get 2 bars for a second but it goes away.
PLEASE HELP! I feel horrible that my buddy has to borrow my bionic until this is fixed.
Click to expand...
Click to collapse
Try
1 You need update to new Firmware 2.06 (for moonshine)
2 You need to Re lock Bootloader in order to RUU
3 you need to downgrade Hboot to 1.15 to RUU ( your phone show 1.33)
http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Hope this help buddy
finanandroid said:
Try
1 You need update to new Firmware 2.06 (for moonshine)
2 You need to Re lock Bootloader in order to RUU
3 you need to downgrade Hboot to 1.15 to RUU ( your phone show 1.33)
http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Hope this help buddy
Click to expand...
Click to collapse
Anyone have a recommended method to downgrade the hboot? I havnt been able to get the 1.15 to flash to the phone.. Relocking the bootloader is cake.
I appreciate your help, Sorry if I sound n00bish.
janderson2k said:
Anyone have a recommended method to downgrade the hboot? I havnt been able to get the 1.15 to flash to the phone.. Relocking the bootloader is cake.
I appreciate your help, Sorry if I sound n00bish.
Click to expand...
Click to collapse
Every one learn everyday.
Download 1.15 stock hboot. Rename to PL83IMG.zip. when u renamed it make sure is not zip.zip cause this file is already zip so u try only to rename it to PL83IMG (right click the file in your pc and check properties to make sure windows got it already as a zip extension) and place in the folder that contains ( in ur pc) your android-adb folder*
there is where any zip should go, with the exception of user preferences location. (or different folder named by the user)
Step 1) adb reboot bootloader
Step 2) fastboot oem rebootRUU
Step 3) Command to directory containing your renamed hboot zip (i.e. C:\android-adb\)
Step 4) fastboot flash zip PL83IMG.zip
*** When it says it is done in the terminal/cmdprompt execute step 5 )
[The green bar only fills up about 75% of the way]
Step 5) fastboot reboot-bootloader
Profit. Put the RUU Folder in same directory. right click and run it as administrator
soff
W00t! S-Off is done.. HBoot time....
?
finanandroid said:
Every one learn everyday.
Download 1.15 stock hboot. Rename to PL83IMG.zip. when u renamed it make sure is not zip.zip cause this file is already zip so u try only to rename it to PL83IMG (right click the file in your pc and check properties to make sure windows got it already as a zip extension) and place in the folder that contains ( in ur pc) your android-adb folder*
there is where any zip should go, with the exception of user preferences location. (or different folder named by the user)
Step 1) adb reboot bootloader
Step 2) fastboot oem rebootRUU
Step 3) Command to directory containing your renamed hboot zip (i.e. C:\android-adb\)
Step 4) fastboot flash zip PL83IMG.zip
*** When it says it is done in the terminal/cmdprompt execute step 5 )
[The green bar only fills up about 75% of the way]
Step 5) fastboot reboot-bootloader
Profit. Put the RUU Folder in same directory. right click and run it as administrator
Click to expand...
Click to collapse
So I am not sure whats up but I went through the process :
Code:
C:\adb>fastboot oem rebootRUU
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.051s]
finished. total time: 0.052s
C:\adb>fastboot flash zip PL83IMG.zip
< waiting for device >
sending 'zip' (434 KB)...
OKAY [ 0.218s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.020s]
finished. total time: 2.241s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.048s
and when I get back to bootloader it still says HBoot 1.33.. I used this hboot : http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
Any ideas?
I have the same Problem,but my Phone ist S-ON and Locked with H-Boot 1.33
Radio 1.01.04.0308
OpenDSP v4.120.240.0920
No Recovery,no Root,aahh
I can´t Unlock the Bootloader
Error Code: 160.
Error Reason: MID Not Allowed.
I can´t Downgrade to 1.15
c:\ADB>fastboot flash zip PL83IMG
sending 'zip' (434 KB)...
OKAY [ 0.203s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.250s
What can i do?
Should I try RUU now or do I need hboot @ 1.15?
janderson2k said:
Should I try RUU now or do I need hboot @ 1.15?
Click to expand...
Click to collapse
yes u need Hboot, but you did before unlock, s-off with moonshine method or revone?
you can try RUU now but If you get an Image 158 error during RUU, try flashing the stock hboot again.
All sorted out.. Thanks everyone. I s offed, unlocked, and flashed new radio. All is well
Sent from my SCH-I605 using Tapatalk 2
letschky said:
I have the same Problem,but my Phone ist S-ON and Locked with H-Boot 1.33
Radio 1.01.04.0308
OpenDSP v4.120.240.0920
No Recovery,no Root,aahh
I can´t Unlock the Bootloader
Error Code: 160.
Error Reason: MID Not Allowed.
I can´t Downgrade to 1.15
c:\ADB>fastboot flash zip PL83IMG
sending 'zip' (434 KB)...
OKAY [ 0.203s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.250s
What can i do?
Click to expand...
Click to collapse
Is there no possibility?
I wanted Moonshine S-OFF,'ve updated the firmware and forgot to unlock the bootloader.
Now I have the software version 1.15.605.1, but the HBOOT version is 1.33 wlan can not be switched on and the screen flickers often know clearly wrong boot.img of the software2.06 and the modules from 1.15.
and I can not unlock the bootloader also'm not unlock with my old Unlock_code.bin.
I know now no longer continue...
Go here http://chat.andirc.net:8080/?channels= this People help
Today I had the same problem in my 10 minutes dna worked again
Related
Hello!
I installed Munjeni's special hboot partition (to increase usable space) and wanted to update the phone back to stock (to take back to att).
The RUU utility failed with code of 152.
The partition failed.
Now the phone is "stuck" at the black HTC screen with four warning triangles in each corner.
Any ideas?
I can fastboot and issue some commands...
I am s-on, hboot 1.02.
Thanks in advance!
DanGeorges said:
Hello!
I installed Munjeni's special hboot partition (to increase usable space) and wanted to update the phone back to stock (to take back to att).
The RUU utility failed with code of 152.
The partition failed.
Now the phone is "stuck" at the black HTC screen with four warning triangles in each corner.
Any ideas?
I can fastboot and issue some commands...
I am s-on, hboot 1.02.
Thanks in advance!
Click to expand...
Click to collapse
If the bootloader is accessible, you can try grabbing the rom.zip out of the RUU (run it & let it load, then search in Windows' temporary folder for "rom.zip". If not there's probably a download somewhere), and rename it to "LIBEIMG.zip" on the root of the SD card.
Then boot into the bootloader (vol down) and it should pick it up and start flashing (might be a confirmation before it does)
Edit: Well I looked at the title again... does this mean its not accessible?
It should be if fastboot is, but I've never had the bad triangles so not completely sure..
If not, alternate option that may work: extract the hboot image from rom.zip and flash it with fastboot (if its allowed)
This is the RUU zip: http://www.mediafire.com/?tay1j415ymvukh5
drumist said:
This is the RUU zip: http://www.mediafire.com/?tay1j415ymvukh5
Click to expand...
Click to collapse
Thank you for the link. I'm downloading it now.
I can fastboot, but I'm S-on (from one of my flashes).
What's the fastboot command for flashing the hboot? Will this even let me?
I'll give this a try. Thanks again!
When I try to fastboot flash a recovery, here's what I get:
C:\Mobile\Android\Fastboot and ADB Tool>fastboot flash recovery recovery.img
sending 'recovery' (3716 KB)... OKAY [ 0.875s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.578s
C:\Mobile\Android\Fastboot and ADB Tool>
For hboot - does anyone have an idea which hboot I can try flashing?
WinSuk said:
If the bootloader is accessible, you can try grabbing the rom.zip out of the RUU (run it & let it load, then search in Windows' temporary folder for "rom.zip". If not there's probably a download somewhere), and rename it to "LIBEIMG.zip" on the root of the SD card.
Then boot into the bootloader (vol down) and it should pick it up and start flashing (might be a confirmation before it does)
Edit: Well I looked at the title again... does this mean its not accessible?
It should be if fastboot is, but I've never had the bad triangles so not completely sure..
If not, alternate option that may work: extract the hboot image from rom.zip and flash it with fastboot (if its allowed)
Click to expand...
Click to collapse
I'll try the hboot image and see what happens.
What's the fastboot command?
I tried:
fastboot flash hboot
and
fastboot flash boot
Both gave me an invalid signature:
C:\>fastboot flash hboot hboot_liberty_7227_1.02.0000_101104.nb0
sending 'hboot' (512 KB)... OKAY [ 0.234s]
writing 'hboot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.328s
C:\>fastboot flash boot hboot_liberty_7227_1.02.0000_101104.nb0
sending 'boot' (512 KB)... OKAY [ 0.234s]
writing 'boot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.328s
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
I am having issues with re-unlocking my dna. I tried using the RUU to flash it back to stock but I had some problems with the RUU (error 170). I tried rerunning rumrunner (which work fine the first time) and at the end it had an error and still read a relocked with s-off in fastboot. I need to know how to complete the RUU and start from scratch, or how to re-unlock it from where I am. Thanks for the help.
RUU is failing because of hboot.
But, you're s-off. So change your CID and unlock at HTC DEV
Sent from my DLX using xda app-developers app
Phaded said:
RUU is failing because of hboot.
But, you're s-off. So change your CID and unlock at HTC DEV
Sent from my DLX using xda app-developers app
Click to expand...
Click to collapse
I didn't think you can use that method any more?
You can change cid if you're s-off
Phaded said:
RUU is failing because of hboot.
But, you're s-off. So change your CID and unlock at HTC DEV
Sent from my DLX using xda app-developers app
Click to expand...
Click to collapse
Would there be any particular number to change it to? Also would you please link me to a post with instruction on how to change the cid?
Boot into bootloader
fastboot oem writecid 22222222
Fastboot reboot-bootloader
fastboot getvar cid (should be 2s)
If so, go to htcdev and unlock
Okay so the dev unlock worked but, when it rebooted it got stuck onthe boot image and never fully booted. I left it on for a whole night. now when I try to flash/erase anything twrp is unable to mount anything. I tried wiping it with fastboot -w but is doesn't allow it. Is there any way to remount everything?
Run the RUU. You won't lose s-off. Then flash recovery, then rom.
Phaded said:
Run the RUU. You won't lose s-off. Then flash recovery, then rom.
Click to expand...
Click to collapse
How would you run the ruu when it won't boot into rom?
A ruu is the Rom.
I'm guessing u have a zip ruu
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot reboot
Sent from my HTC6435LVW using XDA Premium 4 mobile app
wrestech said:
How would you run the ruu when it won't boot into rom?
Click to expand...
Click to collapse
You boot into the bootloader and the run the RUU. The RUU is an .exe
Phaded said:
You boot into the bootloader and the run the RUU. The RUU is an .exe
Click to expand...
Click to collapse
Depends what ruu he downloaded. There is a zip ruu also.
thayl0 said:
A ruu is the Rom.
I'm guessing u have a zip ruu
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot reboot
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will you post a link when I tried flashing the zip I found I got this
sending 'zip' (15846 KB)...
OKAY [ 1.803s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 2.548s
wrestech said:
Will you post a link when I tried flashing the zip I found I got this
sending 'zip' (15846 KB)...
OKAY [ 1.803s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 2.548s
Click to expand...
Click to collapse
Stop using the zip and use the exe
wrestech said:
Will you post a link when I tried flashing the zip I found I got this
sending 'zip' (15846 KB)...
OKAY [ 1.803s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 2.548s
Click to expand...
Click to collapse
You need update your Hboot in order to run RUU
Flashing both Firmwares link below, will put you ready to run the latest Ruu.
Recall put both files in ur adb folder as the rom.zip too
follow direction on links 1 and 2.
http://forum.xda-developers.com/showpost.php?p=48680578&postcount=44
Download this Ruu as zip file to flashing in fastboot> Rom.zip *** Flash first Firmware1 and Firmware2*** above link
http://forum.xda-developers.com/showpost.php?p=48498759&postcount=1
additional: after running firmware1 and firmware2 IF rom.zip fail
https://docs.google.com/file/d/0B32gqnbh2ZecYTlvV1dlZTVRS0E/edit?pli=1 RUU.exe move to adb folder >right click run as administrator .
Note: this RUU.exe worked like butter when the Bootloader is locked. no tested with unlocked bootloader.
It worked
Thanks for all the help,
I my phone is now working. I used the firmware links that finanandroid linked to and flash them. I then tried flashing the rom.zip through RUU but is was blocked (failed remote 24 parsing ). I then reflashed recovery (CWM) and tried wiping the cache to check and see if everything was mounting. It was. So I adb sideloaded cm 10.2 and everything is working great!
wrestech said:
Thanks for all the help,
I my phone is now working. I used the firmware links that finanandroid linked to and flash them. I then tried flashing the rom.zip through RUU but is was blocked (failed remote 24 parsing ). I then reflashed recovery (CWM) and tried wiping the cache to check and see if everything was mounting. It was. So I adb sideloaded cm 10.2 and everything is working great!
Click to expand...
Click to collapse
Just post back here if you need any more help.
Hi All,
Sometime ago I was able to install android 4.3 using the moonshine method. After sometime, I decided to go back to stock. I followed a tutorial on how to get back to stock RUU.
-Entered Boot loader, typed in cmd prompt "fastboot oem lock" received the word that lock was successful.
-Proceeded to run the RUU executable file 1.15 but received the "158 error"
Now my phone has been wiped of any OS since I relocked the phone, but it still says "moonshine s-off".
I tried to use TWRP recovery adb sideload the proper hboot file to match the RUU but get this message
Failed
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:TWFunc::Copy_Log -- Can't open destination lo
E:Unable to mount '/cache'
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
WRONG OPERATION!
E:Error executing updater binary in zip'data/
I am at a complete loss as what to do now. I've been at this for 3 hours now and its driving me crazy. PLEASE HELP!
Can anyone walk me through the steps of pushing the hboot zip via adb sideload?
Will adb sideload not work if my fastboot is locked?
I tried to follow this tutorial to go back to stock because I S-OFF'd moonshine
http://forum.xda-developers.com/showthread.php?t=2293919
My issue is trying to copy the lock bootloader zip file to my phone. Adb sideload is not working, there is no OS since I did the "fastboot oem lock" wiped my phone.
I tried to do a restore in TRWP but after it finished, when starting its stuck on the CM splash screen.
Please help.......................
sideshow9090 said:
I tried to follow this tutorial to go back to stock because I S-OFF'd moonshine
http://forum.xda-developers.com/showthread.php?t=2293919
My issue is trying to copy the lock bootloader zip file to my phone. Adb sideload is not working, there is no OS since I did the "fastboot oem lock" wiped my phone.
I tried to do a restore in TRWP but after it finished, when starting its stuck on the CM splash screen.
Please help.......................
Click to expand...
Click to collapse
There use to be a command you could enter to lock it. I would message phaded and ask him for the command sense the zip isn't working.
sideshow9090 said:
Hi All,
Sometime ago I was able to install android 4.3 using the moonshine method. After sometime, I decided to go back to stock. I followed a tutorial on how to get back to stock RUU.
-Entered Boot loader, typed in cmd prompt "fastboot oem lock" received the word that lock was successful.
-Proceeded to run the RUU executable file 1.15 but received the "158 error"
Now my phone has been wiped of any OS since I relocked the phone, but it still says "moonshine s-off".
I tried to use TWRP recovery adb sideload the proper hboot file to match the RUU but get this message
Failed
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:TWFunc::Copy_Log -- Can't open destination lo
E:Unable to mount '/cache'
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
WRONG OPERATION!
E:Error executing updater binary in zip'data/
I am at a complete loss as what to do now. I've been at this for 3 hours now and its driving me crazy. PLEASE HELP!
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B32gqnbh2ZecTUk4TW5QZ1M4cFU/edit?usp=sharing
MD5: 03C6174C4C5331E84520AD7C32EB2837
download that, and then boot into fastboot usb mode, and
fastboot oem rebootRUU
fastboot flash zip SENSE_5_RUU_ROM.zip
it is essentially an RUU but in zip form
WILL WIPE DEVICE (INCLUDING SDCARD)
if this doesnt work, do an @"my xda handle" and ill come back to this
also the only way to flash firmware is through fastboot, made that clear in my instructions, if you got the download from my thread, if you didnt well... now you know lol
@.torrented
This is what I did in command prompt and my result
C:\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.054s]
finished. total time: 0.054s
C:\Android\sdk\platform-tools>fastboot flash zip SENSE_5_RUU_ROM.zip
sending 'zip' (920285 KB)...
OKAY [ 34.998s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 41.151s
C:\Android\sdk\platform-tools>
The phone ends up being in the black HTC screen. Am I supposed to do something after this?
sideshow9090 said:
@.torrented
This is what I did in command prompt and my result
C:\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.054s]
finished. total time: 0.054s
C:\Android\sdk\platform-tools>fastboot flash zip SENSE_5_RUU_ROM.zip
sending 'zip' (920285 KB)...
OKAY [ 34.998s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 41.151s
C:\Android\sdk\platform-tools>
The phone ends up being in the black HTC screen. Am I supposed to do something after this?
Click to expand...
Click to collapse
Also this is what my fastboot screen looks like
moonshine S-OFF
MONARUDO PVT SHIP S-OFF
CID-VZW_001
HBOOT-1.33.4444
RADIO-1.01.04.0308
OpenDSP-v6.120.274.0114
eMMC-boot
Jan 15 2013, 19:37:51:-1
FASTBOOT USB
But when I type in adb devices its just says "List of Devices Attached"
sideshow9090 said:
Also this is what my fastboot screen looks like
moonshine S-OFF
MONARUDO PVT SHIP S-OFF
CID-VZW_001
HBOOT-1.33.4444
RADIO-1.01.04.0308
OpenDSP-v6.120.274.0114
eMMC-boot
Jan 15 2013, 19:37:51:-1
FASTBOOT USB
But when I type in adb devices its just says "List of Devices Attached"
Click to expand...
Click to collapse
I am not a dev but it looks like your bootloader is locked. your cid should be all 11111 or all 222222
I goofed up, You will need to go to the bottom of my COLLECTION thread and follow the instructions posted at the bottom under the RUU LINKS section
not the .exe files
[Collection] HTC Droid DNA Firmware [RADIO][HBOOT][RUU]
@.torrent
YOU ARE THE MAN! Donation coming your way....THANKS AGAIN!
sideshow9090 said:
@.torrent
YOU ARE THE MAN! Donation coming your way....THANKS AGAIN!
Click to expand...
Click to collapse
I take it that it worked?
I've got a friend's HTC One M8 that's stuck in HBOOT. I can't flash a new recovery, I've tried both TWRP and CWM. Either time I get an error message "FAILED (remote: image update error)"
I'm at the end of my thread here with things I can try to fix it. I've searched almost all topics to no avail.
Here's the getvar dump:
C:\Users\Adrian>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
--
Device says *** UNLOCKED *** on screen, doesn't say TAMPERED (not sure what this is).
Anything fastboot commands usually result in a failed message but the device is recognized if I type "fastboot devices".
Here's a sample when trying to use Squabbi's toolkit:
target reported max download size of 1830727680 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.607s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.678s
I've tried using an ATT RUU, various recovery files, etc. The phone boots straight into HBOOT. Any other commands apart from fastboot on the device result in a quick flash of another screen and returns to the fastboot USB screen.
What can I do to get this device back up and running? For some reason I just can't get the recovery file to flash so I can move forward already. Am I missing something? I just got the device from a friend. He mentioned he was watching YT when all of a sudden the device went into this boot loop.
Thanks in advance!
adriankeith said:
I've got a friend's HTC One M8 that's stuck in HBOOT. I can't flash a new recovery, I've tried both TWRP and CWM. Either time I get an error message "FAILED (remote: image update error)"
Thanks in advance!
Click to expand...
Click to collapse
Hello
I'm no expert but it sounds like a radio issue
Have you tried a new RUU
Also what is your (bootloader) version-main:
Thanks
jcbjoe said:
Hello
I'm no expert but it sounds like a radio issue
Have you tried a new RUU
Also what is your (bootloader) version-main:
Thanks
Click to expand...
Click to collapse
Admittedly, I've got an iOS device myself so I'm going to have to defer to your expertise. I believe I've tried a new RUU (an ATT .exe file? It was a full blown installer, told me what version i was on, what version it would be updating to.. does this sound right?).
How can I get you the bootloader version?
adriankeith said:
Admittedly, I've got an iOS device myself so I'm going to have to defer to your expertise. I believe I've tried a new RUU (an ATT .exe file? It was a full blown installer, told me what version i was on, what version it would be updating to.. does this sound right?).
How can I get you the bootloader version?
Click to expand...
Click to collapse
C:\Users\Adrian>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: < --
jcbjoe said:
C:\Users\Adrian>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: < --
Click to expand...
Click to collapse
That was a straight copy paste from my command line. So.. I guess if there's nothing there.. ??
RUU
adriankeith said:
That was a straight copy paste from my command line. So.. I guess if there's nothing there.. ??
Click to expand...
Click to collapse
You can try this
1.58.502.1 full RUU
jcbjoe said:
You can try this
1.58.502.1 full RUU
Click to expand...
Click to collapse
Unfortunately, it seems with any of these RUU installers I get a USB connection error. I have to think it has something to do with me being unable to enable the USB Debugging mode of the phone.
Any other ideas?
adriankeith said:
Unfortunately, it seems with any of these RUU installers I get a USB connection error. I have to think it has something to do with me being unable to enable the USB Debugging mode of the phone.
Any other ideas?
Click to expand...
Click to collapse
Can you get into fastboot mode ?
IF you can get into fastboot mode we are fine .. we don't need adb
Think of fastboot as the bios and adb as the software
IF your usb is jacked you need to try another computer
EDIT: If fastboot works go to This Thread
The first download link is the firmware that you need
1. Download the firmware
2. Put your phone in fastboot mode
3. fastboot erase cache
4. fastboot oem rebootRUU
5. fastboot flash zip thefirmwareyoudownload.zip < -- if it fails you might have to do this 2x
6. fastboot reboot-bootloader
7. Tell us what you see after words
jcbjoe said:
Can you get into fastboot mode ?
IF you can get into fastboot mode we are fine .. we don't need adb
Think of fastboot as the bios and adb as the software
IF your usb is jacked you need to try another computer
Click to expand...
Click to collapse
I'm able to get into fastboot USB mode but any of the critical commands I've tried running (fastboot flash recovery image.img) all throw errors.
Like this --
sending 'recovery' (12846 KB)...
OKAY [ 1.272s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.341s
---
edit:
Here's the error I get when trying to erase the cache:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
Click to expand...
Click to collapse
adriankeith said:
I'm able to get into fastboot USB mode but any of the critical commands I've tried running (fastboot flash recovery image.img) all throw errors.
Like this --
sending 'recovery' (12846 KB)...
OKAY [ 1.272s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.341s
---
edit:
Here's the error I get when trying to erase the cache:
Click to expand...
Click to collapse
Did you flash the firmware file from the link i provided ?
Firmware < -- Flash this first .. don't flash anything individually .. you need to update the firmware don't unpack it
jcbjoe said:
Did you flash the firmware file from the link i provided ?
Firmware < -- Flash this first .. don't flash anything individually .. you need to update the firmware don't unpack it
Click to expand...
Click to collapse
How do I flash this file?
adriankeith said:
How do I flash this file?
Click to expand...
Click to collapse
Download it
.. once you download it you will see it says firmware.zip
Then you put it on your desktop or your Downloads folder
Then
1. fastboot erase cache
2. fastboot oem rebootRUU
3. fastboot flash zip firmware.zip < -- if it fails you might have to do this 2x (remember you flash it to where its at .. so if its in windows on your desktop it would be fastboot flash zip ~/Desktop/firmware.zip or in Downloads it would be fastboot flash zip ~/Downloads/firmware.zip
4. fastboot reboot-bootloader
5. Tell us what you see after words
jcbjoe said:
Download it
.. once you download it you will see it says firmware.zip
Then you put it on your desktop or your Downloads folder
Then
1. fastboot erase cache
2. fastboot oem rebootRUU
3. fastboot flash zip firmware.zip < -- if it fails you might have to do this 2x (remember you flash it to where its at .. so if its in windows on your desktop it would be fastboot flash zip ~/Desktop/firmware.zip or in Downloads it would be fastboot flash zip ~/Downloads/firmware.zip
4. fastboot reboot-bootloader
5. Tell us what you see after words
Click to expand...
Click to collapse
Here's the problem when I try to attempt the first command
C:\Users\Adrian>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
adriankeith said:
Here's the problem when I try to attempt the first command
C:\Users\Adrian>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
Click to expand...
Click to collapse
Can you rename the firmware.zip to 0p6bimg.zip
Once you do that put the file onto the root of your sdcard (meaning not in a folder)
Credits for the Below Method (an0ther Post# 1)
2. Simply move the "0p6bimg.zip" to the ROOT of your EXT micro sd card.
3. Boot to your boot loader. There are many ways to get to your boot loader. A lot of custom roms have it built into the restart menu. If you have usb debugging enabled its just "adb reboot bootloader" If you can't get there with one of these methods, simply make sure phone is on, hold vol up and power for 11 seconds until screen shuts off, let go and hold vol down and power until boot loader comes up. "about 4 seconds"
4. Click HBOOT in your boot loader. Your phone will automatically scan the file and ask if you want to update. Hit vol up for yes or vol down for no.
5. Phone will begin RUU restore. You can watch what it does on the screen as it will go through a list and bypasses are normal. It will reboot boot loader and you can watch progress bars in the top right corner. It goes through a TON of them so do NOT turn off phone for any reason and let it finish. The process takes about 15 minutes give or take. Once it is done, it will say complete, press power to reboot. Again do not power off phone or even touch it for that matter during this process.
jcbjoe said:
Can you rename the firmware.zip to 0p6bimg.zip
Once you do that put the file onto the root of your sdcard (meaning not in a folder)
Credits for the Below Method (an0ther Post# 1)
2. Simply move the "0p6bimg.zip" to the ROOT of your EXT micro sd card.
3. Boot to your boot loader. There are many ways to get to your boot loader. A lot of custom roms have it built into the restart menu. If you have usb debugging enabled its just "adb reboot bootloader" If you can't get there with one of these methods, simply make sure phone is on, hold vol up and power for 11 seconds until screen shuts off, let go and hold vol down and power until boot loader comes up. "about 4 seconds"
4. Click HBOOT in your boot loader. Your phone will automatically scan the file and ask if you want to update. Hit vol up for yes or vol down for no.
5. Phone will begin RUU restore. You can watch what it does on the screen as it will go through a list and bypasses are normal. It will reboot boot loader and you can watch progress bars in the top right corner. It goes through a TON of them so do NOT turn off phone for any reason and let it finish. The process takes about 15 minutes give or take. Once it is done, it will say complete, press power to reboot. Again do not power off phone or even touch it for that matter during this process.
Click to expand...
Click to collapse
Got a wrong zipped image while it was loading the zip file.
adriankeith said:
Got a wrong zipped image while it was loading the zip file.
Click to expand...
Click to collapse
Try any of the links in the Thread
You have to rename it to 0p6bimg.zip
jcbjoe said:
Try any of the links in the Thread
You have to rename it to 0p6bimg.zip
Click to expand...
Click to collapse
Yep, I renamed it to the 0P6BIMG.zip and when it began to load the file it agave me that error. I'll try that thread now.
--
Still getting the "Wrong Zipped Image!" error. I did this previously with a different firmware and it got through some of the process but bombed out after something and put me back in HBOOT. Couldn't launch recovery, couldn't launch anything. Fastboot USB shows up fine.
adriankeith said:
Yep, I renamed it to the 0P6BIMG.zip and when it began to load the file it agave me that error. I'll try that thread now.
--
Still getting the "Wrong Zipped Image!" error. I did this previously with a different firmware and it got through some of the process but bombed out after something and put me back in HBOOT. Couldn't launch recovery, couldn't launch anything. Fastboot USB shows up fine.
Click to expand...
Click to collapse
You Possibly have a bricked device
You can try chatting on freenode via irc
irc.freenode.net #sunshine-support or #htc-dev or #venomroms .. all these channels have htc devices m7 or m8
Thanks
jcbjoe said:
You Possibly have a bricked device
You can try chatting on freenode via irc
irc.freenode.net #sunshine-support or #htc-dev or #venomroms .. all these channels have htc devices m7 or m8
Thanks
Click to expand...
Click to collapse
I was coming to that conclusion quickly.
Thanks for your help though. I appreciate it.
adriankeith said:
Unfortunately, it seems with any of these RUU installers I get a USB connection error. I have to think it has something to do with me being unable to enable the USB Debugging mode of the phone.
Any other ideas?
Click to expand...
Click to collapse
Since you are s-in and bootloader unlocked, you need to relock the bootloader to run an RUU. This shouldn't give you a USB connection error, but its at least worth a try to relock.
Also, try to connect the phone to PC, go into Window Device Manager, and see if you can format the internal memory to FAT32. Some folks have had issues with internal memory corrupted, and cannot install recovery; and this fix worked for them.
---------- Post added at 10:17 AM ---------- Previous post was at 10:13 AM ----------
jcbjoe said:
You Possibly have a bricked device
Click to expand...
Click to collapse
I doubt it. So far, I've only seen on these forums one M8 where the screen still comes on, and extensive help from several folks couldn't get it back up and running. Being able to get into hboot means we can recover, 99.99% of the time.
Still a lot of things left to try.