Related
Dear developers,
I got a problem, there were a lot of things I could help my self with but now i'm stuck.
My HTC Desire Z won't boot... I can't flash anything to my phone because the bootloader is locked and I can't find a official RUU that would help me out.
I tried to boot in fastboot and I get the HTC logo with in every corner an exclamation, when I disconnect the phone I get the following screen:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.51.26
eMMC-boot
Apr 11 2011,23:36:27
RUU
- no reboot possible
- screen says RUU (when plugged in, RUU USB)
- can't find device with adb devices
- can find device with fastboot devices
- not possible to make goldcard, because no adb connection
- running new RUU didn't work either (because I can't find a RUU for 2.42.405.5)
I have no solution, can someone please help me?
------- Update
I have a gold card using another phone
If I now just try to flash something on my phone I get a signature error
What happened around the time your phone stopped booting? Did you go to HTC website to get the latest ruu from them? Also boot back to fastboot and try
fastboot check_emmc_mid
Sent from my Nexus 7 using xda premium
On the HTCDev.com I can vind a RUU for software version: 2.42.405.2 but I have 2.42.405.5
Now I tried the command: fastboot oem check_emmc_mid and get the output:
...
(bootloader) Manufacturer ID, MID=45
(bootloader) eMMC should be Sandisk
OKAY [ 0.009s]
finished. total time: 0.010s
I don't understand anything about it, I hope you do
And I tried a the command: fastboot oem boot and than I get the output:
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is HTC__E11
(bootloader) setting->cid::HTC__E11
(bootloader) serial number: SH0BNRT08614
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =496
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.10.51.26 androidboot.c
(bootloader) id=HTC__E11 androidboot.batt_poweron=die_battery androidboot
(bootloader) .carrier=HTC-Dutch androidboot.mid=PC1011000 androidboot.key
(bootloader) caps=qwerty androidboot.mode=normal androidboot.serialno=SH0
(bootloader) BNRT08614 androidboot.bootloader=0.85.0013 zygote_oneshot=of
(bootloader) f kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:27964 msec
FAILED (status read failed (Too many links))
finished. total time: 7.423s
And mij device gives a normal boot logo (the white one instead of the black one with the "!" in every corner)
Just wanted to se which emmc you had as one is prone to failure, you do have a good one though!
Now its all about finding the right bit to flaash for you which may be a bit hard as unrooted and bootloader locked phones only allow new os versions to be flashed. I won't be near a computer for a while but when I get back ill try to dig up a file for you
Sent from my SGH-T839 using Tapatalk 2
if you would like to do I'd be very grateful!
yeah seems like you have the latest version right now other than the latest g2 ruu but you dont have super cid so you wont be able to flash that either
do you remember what happened when your phone stopped working? may help figure this out.
also just for fun what output do you get when you type this in fastboot
fastboot flash system system.img
dont worry that there is no image, im more concerned if your current bootloader will allow you to do this, i doubt it but why not
also check this
fastboot oem partition_test all
Like evry other flash I try:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
and the output of the partiton test:
(bootloader) [ERR] Command error !!!
I think the phone does not flash because the bootloader is locked? (S-ON)
I do not know how the device can not work anymore, I've bought via ebay ...'m a bit ripped off because it said that the phone worked
yeah a bit ****ty of whomever sold it to you, id try for a refund!
i take it you tried the basic stuff like booting to recovery and doing a factory reset?
this is real annoying too being without knowing the cause and having such limited access its hard to fix this thing, one of those deals where if i had it in front of me i think i could figure it out! but really you are going to need an updated ruu signed by htc to get this thing up and running if all the simple fixes havent worked... i guess you can see if debugging will work in recovery mode? if so then should still be fixable...
I tried a lot, can't boot to recovery because there is no.
it automaticly boots into RUU mode and if i try to boot it in to bootloader, system or recovery it stuck at the HTC logo.
How can I debugg the device? I know how to debug C# applications with Dot Net but a simple android phone is a lot harder
I could send my phone to your house if u think that would help?
Problem solved! partially i used a RUU from asia with a higher Version
dont send me the phone i live far away, send it back to whoever sold it to you and get the refund. hell ill sell you one that does work!
by debugging i meant to see if it were turned on on the phone, this is what allows for adb to work where you do the debugging. adb wont work in bootloader/fastboot mode, only in os and recovery. but again the problem is you can flash a recovery or os being you have a locked/shipped bootloader, the only thing to do at this point is to work with the limited fastboot commands you have or install a PC10IMG.zip, again the problem with this is they have to be signed by htc and be of a new version then your phone thinks you have installed... kinda stuck without some nicer options
Oh, I had forgotten that "adb" for android debugging bridge stands.
I do not have adb access only fastboot access, and a PC10IMG.zip does not work,like you already said it needs to have a htc signature.
Sending my phone to you was a joke.
But it is now almost entirely successful. I have an official RUU software used with a higher number, I had 2.42.405.5 and I have set up a foreign RUU and it worked "HTC Asia WWE 2.42.707.3"
I now have at least access to the HBoot, now I'll have to see how I can get S-OFF. flashing and "get_identifier_token" are still not working
Awesome news! So as of right now you have a stock ROM/Hboot/recovery?
If that is the case go right over to the xda wiki for the vision and root your phone with gfree!
Do it now before anything else brakes! Once you root (only use gfree method laid out in wiki) then everything else will be easy! Let me know how things go or if you need a hand!
*can't believe I glossed over that ruu!
Sent from my Nexus 7 using xda premium
He does not work well, he gets stuck on the normal boot logo.
If I run fastboot reboot bootloader he walks onto the boot screen. Install another RUU does not work, it stuck on "wait for bootloader"
Now the option "Image CRC" is added to the HBOOT menu, and I ran a factory reset that fails, that is what crashed my phone
can you post everything on your new hboot screen here? also everything that image crc says or any other options that may have appeared. also does it let you boot to a recovery?
Code:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
crc output:
7 times vibrate
Code:
calculating... please wait
osbl: 0x7EE4ED8C
amss: 0x0
hboot: 0x887F7ABB
boot: 0x0
recovery: 0x0
system: 0x0
Press power key to go back.
I could get into recovery but after I did the factory reset (what went wrong) I can't. I can only get into the bootloader by "VOL-" and "POWER" but if I from fastboot reboot-bootloader command doing he stack onto the HTC logo.
well according to this you have no system, kernel or recovery installed right now just a locked bootloader with all security flags on.
can you try another ruu, or flash the same one again? also look in here nipqer made these and they may help you out... actually he or ghul would be very helpful on this unless you can wait longer, i have some things im working on right now and i can look this over again tonight when i have some more time.
see if you can find them or another helpful one at FREENODE make a name and join #g2root
Yeah, yesterday I was @ the chat on freenode, they told me to try the asian RUU (a) I'll try the DZ_PC10IMG.zip form your link and if that doesnt work I'll wait for the next option
Thanks a lot!
I can't flash any RUU because after the command "reboot bootloader" he keeps waiting for the bootloader but the device gets stuck on the htc logo and doesn't boot to the bootloader, even if I set it from "VOL UP" + "POWER" to the bootloader the RUU installer status remains: "Waiting for bootloader"
After entering the bootloader menu is scans the SDCARD and finds the PC10IMG.zip
telling me: loading...[PC10IMG.zip], after that it's saying: Checking..[PC10IMG.zip].
After checking it just goes back to the Menu without asking me to update etc.
And I tried to flash a stock recovery but than I got a Signatue failure.
Try taking the pc10img off SD card or removing SD altogether
Then of will boot into fastboot, the in fastboot mode type
fastboot OEM rebootRUU
Sent from my Nexus 7 using xda premium
Update: This is an AT&T carrier unlocked phone. Bootloader says INVALID_VER_INFO for RADIO and OpenDSP.
Doing research on this INVALID_VER_INFO, your phone can be functioning normally with this issue: http://forum.xda-developers.com/showthread.php?t=2715056
Most results for this are those who tried doing something unofficial with their phone. My phone updated an official update over the air (wasn't trying to root it or anything). Somewhere it must have failed, and I can only get to the recovery portion. I read that part of recovering your phone would be to first unlock the bootloader, but that hasn't worked. I registered, followed every step on HTCDev, even the final command completed successfully. My phone still reads LOCKED. I also noticed the RADIO and OpenDSP say "INVALID_VER_INFO". Right now I'm downloading the M8's RUU, but that'll be another hour (big file, slow Internet). The phone is not under warranty.
Am I on the right path?
tmontney said:
Most results for this are those who tried doing something unofficial with their phone. My phone updated an official update over the air (wasn't trying to root it or anything). Somewhere it must have failed, and I can only get to the recovery portion. I read that part of recovering your phone would be to first unlock the bootloader, but that hasn't worked. I registered, followed every step on HTCDev, even the final command completed successfully. My phone still reads LOCKED. I also noticed the RADIO and OpenDSP say "INVALID_VER_INFO". Right now I'm downloading the M8's RUU, but that'll be another hour (big file, slow Internet). The phone is not under warranty.
Am I on the right path?
Click to expand...
Click to collapse
Yes you are. As long as you are downloading the correct RUU for your device/carrier, you are doing exactly what you should do. There's no need for an unlocked bootloader if the RUU was meant for you.
tmontney said:
=Right now I'm downloading the M8's RUU
Click to expand...
Click to collapse
Be aware that the RUU needs to match your CID. You can't run an RUU for just any M8 version.
Otherwise, as indicated above, if you phone is not modified already (bootloader unlock, root, etc.) and an RUU is available for your CID, there is no need to unlock the bootloader. In fact, an unlocked bootloader will prevent the RUU from working unless the phone is s-off.
My bootloader is still locked. I never saw a disclaimer message, and I still see the locked string on my screen. I can even verify it is locked with "fastboot oem lock". It will say "Device was already locked".
Seems like RUU is actually working. Before I could never get past "battery less than 30% message" when it had been charging forever.
RUU made it reboot, never rebooted, then asked for QHSUSB_BULK driver on my PC. Second time, it did eventually reboot. It took quite a while for it to do so. By that time the software must have timed out. I don't know why it has to reboot to bootloader, because it's already in the bootloader (that's all I can get to).
Every time it reboots to the bootloader, I get "USB CONNECTION ERROR".
tmontney said:
I also noticed the RADIO and OpenDSP say "INVALID_VER_INFO".
Click to expand...
Click to collapse
Radio not reading a number is a bad sign; as is the RUU not working.
Seeing as your phone is fully stock, and the problem was caused by an official update, you may be a candidate for a warranty replacement/repair.
I also wouldn't personally recommend further attempts to unlock the bootloader for that reason (may void warranty).
Running fastboot oem rebootRUU gives this output...
Code:
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.043s]
finished. total time: 10.043s
If it helps, I just remembered it was an unlocked AT&T phone. It's been some time since I've tried to fix this phone. If I didn't use the correct term, I mean it's an unlocked carrier (not bootloader).
I also noticed I must have downloaded a very old RUU. Its version was much lower than my phone's (version 1.5 RUU to version 3 something on my phone). I'm downloading the most recent.
redpoint73 said:
Radio not reading a number is a bad sign; as is the RUU not working.
Seeing as your phone is fully stock, and the problem was caused by an official update, you may be a candidate for a warranty replacement/repair.
I also wouldn't personally recommend further attempts to unlock the bootloader for that reason (may void warranty).
Click to expand...
Click to collapse
Where would I go to replace a carrier unlocked phone? I'm no longer trying to unlock the bootloader. I was never successful in unlocking it anyway. I don't believe it's under warranty, and I have no idea where or how to check.
tmontney said:
Where would I go to replace a carrier unlocked phone? I'm no longer trying to unlock the bootloader. I was never successful in unlocking it anyway. I don't believe it's under warranty, and I have no idea where or how to check.
Click to expand...
Click to collapse
If the device version is intended for your region, you may be able to get warranty service through HTC for a period of 1 year. So for the AT&T version, if you are in the US, you may still be able to get warranty.
I say "may" since I am not sure how SIM unlock affects the warranty. You can contact HTC warranty department, and they can probably answer the question (of whether you have warranty or not) and if so, guide you through that process.
Where did you purchase the phone from? Was it a 3rd party seller? How old is the phone, and did you check the seller's return policy?
Alternately, if you have no warranty, you may be able to find a repair service in your area with JTAG, which may bring the phone back to life, for a price.
---------- Post added at 02:16 PM ---------- Previous post was at 02:12 PM ----------
tmontney said:
Code:
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.043s]
finished. total time: 10.043s
Click to expand...
Click to collapse
I don't know much about these types of error outputs, but there are plenty of folks here who know more (so hopefully they can chime in).
But from what I can gather, the output looks to somewhat verify the idea that the update somehow damaged/corrupted some emmc partitions (maybe a radio brick?).
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
tmontney said:
Doing research on this INVALID_VER_INFO, your phone can be functioning normally with this issue: http://forum.xda-developers.com/showthread.php?t=2715056
Click to expand...
Click to collapse
That issue is known and related to using TWRP (custom recovery). You never did that, so its not the same issue.
Not sure whether there are instances of the issue (radio version not listed) for stock devices, and the device still working properly.
You don't have a lot of options with a stock device, aside from RUU.
Again, I'd suggest to check with HTC whether you have a valid warranty, and go from there.
Bought it not more than 2 months ago off eBay. Said it was new, but I feel it was refurbished.
Try this site to check your device warranty status
http://imeidata.net/warranty/htc
ckpv5 said:
Try this site to check your device warranty status
http://imeidata.net/warranty/htc
Click to expand...
Click to collapse
My God, it says I still have a month left. There may be hope if this RUU doesn't work.
Never mind, out of warranty.
The proper RUU failed. RUU says it's rebooting my phone, when my phone comes back RUU says USB CONNECTION ERROR.
Is there nothing left? Unlocking the bootloader failed. I can't flash recovery because bootloader is locked. Recovery and factory defaults are broken.
tmontney said:
The proper RUU failed.
Click to expand...
Click to collapse
What do you mean by "proper RUU"? What were you using before, and which one are you using now (full filename, or link it).
Try to but your phone in bootloader - fastboot mode. Since you phone is not booting, it will need to be in this mode for the RUU to run.
redpoint73 said:
What do you mean by "proper RUU"? What were you using before, and which one are you using now (full filename, or link it).
Try to but your phone in bootloader - fastboot mode. Since you phone is not booting, it will need to be in this mode for the RUU to run.
Click to expand...
Click to collapse
http://dl3.htc.com/application/RUU_...40.45.C33065.00_F_release_426617_signed_2.exe
tmontney said:
http://dl3.htc.com/application/RUU_...40.45.C33065.00_F_release_426617_signed_2.exe
Click to expand...
Click to collapse
So what RUU were you trying to run before?
What is your present hboot number?
What is your present main version number?
redpoint73 said:
So what RUU were you trying to run before?
What is your present hboot number?
What is your present main version number?
Click to expand...
Click to collapse
The RUU I linked is the one I tried running.
HBOOT: 3.19.0.0000
I assume "main version number" is the OS version: 3.42.502.1
tmontney said:
The RUU I linked is the one I tried running.
Click to expand...
Click to collapse
Got it. For some reason, I was under the impression you tried to run 2 different RUUs. Probably just misinterpreted your wording.
tmontney said:
HBOOT: 3.19.0.0000
I assume "main version number" is the OS version: 3.42.502.1
Click to expand...
Click to collapse
Yes, main version and OS version are the same. The terminology just varies depending on what method you use to look it up.
The RUU you are using is okay to run based on your hboot and OS number. I asked before if you tried to run the RUU while you phone is in bootloader-fastboot mode. Try that, and see if you still get the USB connection error.
redpoint73 said:
Got it. For some reason, I was under the impression you tried to run 2 different RUUs. Probably just misinterpreted your wording.
Yes, main version and OS version are the same. The terminology just varies depending on what method you use to look it up.
The RUU you are using is okay to run based on your hboot and OS number. I asked before if you tried to run the RUU while you phone is in bootloader-fastboot mode. Try that, and see if you still get the USB connection error.
Click to expand...
Click to collapse
Fastboot is the only mode I can go in (well that and HBOOT). It will give me an error when it tells the phone to reboot.
Take a look at this thread: http://androidforums.com/threads/htc-one-m8-stuck-in-bootloader.917358/ I started a thread for this issue there, and they're pretty certain my phone is bricked.
tmontney said:
Fastboot is the only mode I can go in (well that and HBOOT). It will give me an error when it tells the phone to reboot.
Take a look at this thread: http://androidforums.com/threads/htc-one-m8-stuck-in-bootloader.917358/ I started a thread for this issue there, and they're pretty certain my phone is bricked.
Click to expand...
Click to collapse
By "they" you mean the one guy that is helping you there.
I'm not giving up just yet.
As long as the phone is in fastboot mode, USB connection error is usually due to issues on the PC side. Try uninstalling HTC drivers,and re-installing. Try a different USB port, cables, etc.
redpoint73 said:
By "they" you mean the one guy that is helping you there.
I'm not giving up just yet.
As long as the phone is in fastboot mode, USB connection error is usually due to issues on the PC side. Try uninstalling HTC drivers,and re-installing. Try a different USB port, cables, etc.
Click to expand...
Click to collapse
Alright, but I tried using the ROM.zip on my SD card and that failed. By "failed", it failed step 1 in the update process. Doesn't that rule out any PC-side issues? I'm out of town until Sunday, so I'm unable to try anything right now.
Post #9 and #20 should be of interest.
I've got this phone for a while now but since i updated it to official marsmallow it's been stuck into bootloader. The phone is stock, still locked and S-ON. I've tried to unlock it so i can use a custom rom but when i do the official bootloader unlock from htc it goes all okay until it should promp me on the phone screen to confirm bootloader unlock, i can't find a way to make it work. I also tried to use the RUU but when it's rebooting my phone into bootloader (witch it is already) it doesn't reboot the phone goes stand by and the program stops. I the tried to get the zip RUU into an SD but the CID doesn't match since i got the Vodafone UK one so my cid is VODAP001 and i can't find the right RUU for this version. Can someome please help, i'm desperate.
I've tried to use the RUU.zip file from cmd using comand fastboot oem rebootRUU bur it gives me this message:
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.058s]
finished. total time: 10.058s
BlackMambo90 said:
I've got this phone for a while now but since i updated it to official marsmallow it's been stuck into bootloader. The phone is stock, still locked and S-ON. I've tried to unlock it so i can use a custom rom but when i do the official bootloader unlock from htc it goes all okay until it should promp me on the phone screen to confirm bootloader unlock, i can't find a way to make it work. I also tried to use the RUU but when it's rebooting my phone into bootloader (witch it is already) it doesn't reboot the phone goes stand by and the program stops. I the tried to get the zip RUU into an SD but the CID doesn't match since i got the Vodafone UK one so my cid is VODAP001 and i can't find the right RUU for this version. Can someome please help, i'm desperate.
I've tried to use the RUU.zip file from cmd using comand fastboot oem rebootRUU bur it gives me this message:
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.058s]
finished. total time: 10.058s
Click to expand...
Click to collapse
same issue here
did you find the solution?
skierr said:
same issue here
did you find the solution?
Click to expand...
Click to collapse
Yeah I had to send it to support since it had a hardware problem with the memory ( I've pinpointed the problem to the ROM) if you your warranty is expired maybe you should try replacing the motherboard
skierr said:
same issue here
did you find the solution?
Click to expand...
Click to collapse
You have the same sector/emmc errors? Of you just have the problem of stuck in bootloader? Those are two very different things. With the second one being quite possibly fixable.
You need to be specific if you want any meaningful help. Saying you have the "same issue" is never sufficient for folks to give help; and is just going to end up confusing you and others.
Assuming it is not a hardware emmc failure, and you want some direction, please provide the following:
- If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
- If you don't know how to do fastboot, what OS number and radio number does it say on the phone's bootloader screen?
- Bootloader locked or unlocked?
- Any other mods (TWRP, custom ROM, etc.).
- What events led to the current condition? Did you try to flash something, or update OS? Or just happened spontaneously?
- Exact names/version numbers of files you installed, or tried to flash.
The more detail you can give, the better.
Hi,
I had tried rooting my At&T HTC One M9 using the NOOB friendly guide written by KingInTheNorth. After completing, my phone wouldn't boot up. It got into a bootloop. I then found a guide (from another website) on how to reload the stock RUU. I followed the direction but it looks as if the file was bad. The following is copied from the command prompt.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip C:/Use
Downloads/M9fullstock.zip
target reported max download size of 800000000 bytes
sending 'zip' (79642 KB)...
OKAY [ 5.185s]
writing 'zip'...
(bootloader) HOSD CL#682052
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14 RU_ZIP_INFO_ERROR android-info missing or malformed )
finished. total time: 8.400s
Now my phone is stuck on the screen that shows a phone with a green arrow in a green circle pointing down. I've tried rebooting but it doesn't respond to any button presses. Did I ruin my phone? Can anyone help?
Try to type fastboot reboot in your command prompt. It should reboot your phone. If you're lucky it will reboot your phone normally and it's fully functional. If not, your phone will boot into bootloader which will mean your rom is wiped.
That's not a RUU that you were trying to flash and the guide written by KingInTheNorth is outdated since different firmware versions of the M9 can only get rooted with different versions of SuperSU. Check the ReadMe thread for the guides and files you may need.
@Suurbier91: Never recommend people to reboot if a flash failed unless they know exactly what's going on. There are some flashing errors that can only get fixed if the phone gets flashed immediately, again. A reboot makes those bricks permanent and unrecoverable.
Thanks for the direct to the Read Me. I've found a lot of good information there. After my battery died, I charged the phone and it's coming back on. It still has a boot loop that lasts for between five to ten minutes before booting up. I am going to try following one of the threads I found on here to get back to stock. Hopefully that will take care of the boot loop issue. I was wanted to root it so I could upgrade to Nougat. The phone was originally AT&T but I paid to unlock it and I'm now on Cricket but I don't receive any OTA updates.
That's probably so because the phone is only sim unlocked but still using the AT&T firmware. Don't ask me why they're allowed to do so (it wouldn't be possible in the EU) but AT&T won't let you download OTAs if there isn't an AT&T sim card inserted into your phone.
If you don't need the AT&T branded firmware then I'd get S-OFF and convert my phone to the dev edition if I were you. If you choose to stay on the AT&T firmware then you can update your phone via a RUU. Be aware that it's not possible to update from firmware 3.x or lower to firmware 4.x via RUUs due to new encryption keys.
Sent from my HTC One M9 using XDA Labs
Hi all,
@THE company I work we found a htc one m8s that when I booted it went straight to bootloader menu.
I want to get it working again so I started reading here on the forums, download some stuff from ruu.lalleman.net that I found in one of the other treads. In the end i'm still stuck and i'm hoping to get some advice through this channel.
Here is my current status
when the devices is connected to the PC it boots ALWAYS straight to bootloader with the following info
software status : Modified
unlocked
m8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.000
[email protected]
OS-1.16.401.10
eMMC-boot 2048MB
aug 13 2015
Fastboot USB with the normal stuff
when I try to load a RUU through the exe I reboot the device and then keeps waiting with in the end a disconnect (saying I need to connect my device) the device itself is already back in bootloader window.
when I try to use htc_fastboot to flash a recovery it gives me
fastboot flash recovery recovery.img
sending 'recovery' (6002 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 1(s)
but then on reboot it's straight back to bootloader menu no recovery
when I try to lock the device I get
fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: 15
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
(bootloader) [INFO] Rebooting device arbiter!!I PMIC arbitery-
FAILED (unknown status code)
Execution time is 1(s)
I did get it unlocked (as it was locked before but relocking is not working)
Also fastboot devices shows me the devices but adb devices shows nothing (tried both htc drives and general android ones)
These are my var all info
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__031
(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: 1d456ef7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
Execution time is 28(ms)
Hoping on any help from here
Greetings
Tom
Little update:
I kept on trying different versions from recovery / boot / ruu's in the hope that one works but nothing so far.
In another topic somewhere I did found that as long as my device is unlocked it will not work to use RUU, so locking the device again will be my first step.
I did notice that when I ended my adventure yesterday evening I wasn't able to turn the phone off, I always rebooted (in like a millisecond) back to bootloader as long as it was connected to the pc. I had to remove the usb connection and then try couple of times with volume-up / power to turn it off.
I did do the 2 minutes bright licht / volume up + down + power button trick to reset the battery but that didn't change anything.
also as a last minute addition
when I do the fastboot -> image CRC i'm getting a 0X0 on sbl2 - sbl3 - boot and recovery so it seems that what ever I do with htc_fastboot flash is not sticking.
Going to look into trying to get it locked again now first in combination with trying to find out why I can't write to the damn phone (adb isn't working ether so maybe driver problem also ?)
The adventure continues
Tom
adb works only while on running OS or in custom recovery (don't know whether it works on stock recovery) not on fastboot/bootloader.
Only fastboot (generic) or htc_fastboot works on fastboot.
Is the RUU that you tried
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip ?
ckpv5 said:
adb works only while on running OS or in custom recovery (don't know whether it works on stock recovery) not on fastboot/bootloader.
Only fastboot (generic) or htc_fastboot works on fastboot.
Is the RUU that you tried
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip ?
Click to expand...
Click to collapse
That is indeed the RUU i tried, i got it based on the fastboot var all i did.
Still trying to get my Phone locked again as that is holding back the ruu upgrade now from what i see.
Have you tried using htc_fastboot to relock ?
It seems fastboot generic mostly not working for M8s.
ckpv5 said:
Have you tried using htc_fastboot to relock ?
It seems fastboot generic mostly not working for M8s.
Click to expand...
Click to collapse
Yhea i did it with the htc_fastboot version.
another update,
After some more trial and error while aiming for the locking of my phone i'm still stuck.
Both my boot and my recovery are empty it seems (the 0x0 from the image crc) and all the others still have 0xA.....B or what ever value in them
All the writing I do like
C:\tel>htc_fastboot.exe flash recovery recovery_signed.img
sending 'recovery' (30080 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
seems to be working but that doesn't change the crc value's nether does it allow me to use the recovery from the hboot menu.
also when I type stuff like htc_fastboot oem rebootRUU it brings me straight back to the bootloader menu, no black screen to do htc_fastboot flash zip rom.zip.
What I didn't try yet is using a SD-card and see if that fixes it (I could put that card in my other phone, write stuff to it and use it in the M8s.
Anybody got any expereance for using a sdcard to flash the device back to stock.
@ this moment I will be kind of happy with anything that advances me a step
Tom
I got it to work
You may as well give up.
Android will continue to suck and be a deep state tool.
kruc Ire said:
I got it to work
You may as well give up.
Android will continue to suck and be a deep state tool.
Click to expand...
Click to collapse
How do you mean give up ?
is there no way arround based on your opinion from what i posted above ?
I Always hoped it was my lack of knowledge that was holding me back in fixing it ...
Ok if you wanna do it like i did you gotta use the sd card. It should work. Call it by its shortened name and relock the phone first. It can take a long time in several stages.
I was a bit down on android since google keeps screwing with it like taking away panoramio and adding miles upon miles of bloat and force resetting my permissions which I believe I have finally found a solution to in m8s.
If you wanna do it you can. Use that same 1.8 GB firmware we can find on the web. And rename it to the m8s required: 0PKVIMG.zip (i am going offa memory but this looks right to me???) and put it in the root of your microSD. The bootloader should be "relocked" anything I forgot? You don't have to reflash the std recovery first unless I forgot
Then once these things are inplace you should see a full flash after bootin ta bootloader.
kruc Ire said:
Ok if you wanna do it like i did you gotta use the sd card. It should work. Call it by its shortened name and relock the phone first. It can take a long time in several stages.
I was a bit down on android since google keeps screwing with it like taking away panoramio and adding miles upon miles of bloat and force resetting my permissions which I believe I have finally found a solution to in m8s.
If you wanna do it you can. Use that same 1.8 GB firmware we can find on the web. And rename it to the m8s required: 0PKVIMG.zip (i am going offa memory but this looks right to me???) and put it in the root of your microSD. The bootloader should be "relocked" anything I forgot? You don't have to reflash the std recovery first unless I forgot
Then once these things are inplace you should see a full flash after bootin ta bootloader.
Click to expand...
Click to collapse
I did those things and placed the file on the SD card ( 0PKVIMG.zip )
When I go to the phone then and run it it gives me the following error:
Device halted due to Large Image update fail!
press <power> to reboot.
I looked into that and seems I need to do a partial flash for that but didn't found more info on that yet.
Also i'm still stuck on the htc_fastboot OEM lock error i'm getting (see above)
Tom
TomBrunson said:
I did those things and placed the file on the SD card ( 0PKVIMG.zip )
When I go to the phone then and run it it gives me the following error:
Device halted due to Large Image update fail!
press <power> to reboot.
I looked into that and seems I need to do a partial flash for that but didn't found more info on that yet.
Also i'm still stuck on the htc_fastboot OEM lock error i'm getting (see above)
Tom
Click to expand...
Click to collapse
You need to have plenty of space. I have seen large image update fail at some time before. I'll see if I can find my photos from the flash on my m8 (I used the m8 to document the m8s firmware flash). It doesn't have to be "locked", "relocked" is enough
I made that video but if the F'N censors won't let me put up the lyrics of a song they HATE in their pinheads then I won't be posting their garbage they WOULD view.
I'll keep putting up large videos though just to chew up this sh!tty world's resources. If it's a world of creeps it's
Music videos mostly. Ooh how they HATE my beautiful music...and I can hear the little b##ch there in her fuzzy chair. Like she spoke directly into my head. And if it hadn't taken me so long to make a thumbnail she wouldn't have been able to install her trick. Literally FFFF youtube.
kruc Ire said:
You need to have plenty of space. I have seen large image update fail at some time before. I'll see if I can find my photos from the flash on my m8 (I used the m8 to document the m8s firmware flash). It doesn't have to be "locked", "relocked" is enough
Click to expand...
Click to collapse
Is there a different command to Relock as to Lock ?
I couldn't find anything else then htc_fastboot oem lock
Tom
Ok i'm over it. I attached a different (worse) song and reuploaded it. No censorship now.
HTC M8s firmware flash in photos:
Please note I only started making a video because I noticed that time bar on upper right about 15 minutes into the (uninterrupted) flash. So that took a long time and I was concerned about the messed up and overprinted text and made photos during every new screen between the third or fourth at the start (when I caught up with my camera) up till the time of video starting.
So yeah what I am trying to say is it seemed to take very long, with many seemingly false starts and failures. Only by waiting did it finally achieve correctness.
thank you for the video
Seems so that it's still the same issue for me as I don't get my phone locked or relocked
i'll keep on looking aint giving up that quick
TomBrunson said:
thank you for the video
Seems so that it's still the same issue for me as I don't get my phone locked or relocked
i'll keep on looking aint giving up that quick
Click to expand...
Click to collapse
Are you sure you have the correct command? There is a lot of bad info out there. Better get a 2nd source and third for commands. Did you be sure to enable adb bridge in dev options? Can't forget to do that. Go through the entire thing at HTC.dev and do all it says and download their fastboot. Then be sure to have adequate space on phone and storage. You have a nandroid? Then you could try wiping and starting from zero with the flash. This may have been what I done. I definitely did something like that similarly very recently and I think it was cause I was trying the new Los rom just before I gave up on it and decided to do this firmware.
kruc Ire said:
Are you sure you have the correct command? There is a lot of bad info out there. Better get a 2nd source and third for commands. Did you be sure to enable adb bridge in dev options? Can't forget to do that. Go through the entire thing at HTC.dev and do all it says and download their fastboot. Then be sure to have adequate space on phone and storage. You have a nandroid? Then you could try wiping and starting from zero with the flash. This may have been what I done. I definitely did something like that similarly very recently and I think it was cause I was trying the new Los rom just before I gave up on it and decided to do this firmware.
Click to expand...
Click to collapse
When I got the phone it was locked, I then did all the steps to unlock it as I hoped that would be the solution. Those steps did work but it didn't solve the problem. I think wanted to do the RUU thing but therefor the phone needs to be locked or relocked (htc_fastboot oem lock) but hat gives me errors as I posted before.
I'm still in the process of reading as much as possible to find different ways to lock or relock the phone in order to do the RUU update.
Greetings,
Tom
You have never gotten it to lock? I thought you said you couldn't get the zip to work?
---------- Post added at 06:53 PM ---------- Previous post was at 06:38 PM ----------
TomBrunson said:
When I got the phone it was locked, I then did all the steps to unlock it as I hoped that would be the solution. Those steps did work but it didn't solve the problem. I think wanted to do the RUU thing but therefor the phone needs to be locked or relocked (htc_fastboot oem lock) but hat gives me errors as I posted before.
I'm still in the process of reading as much as possible to find different ways to lock or relock the phone in order to do the RUU update.
Greetings,
Tom
Click to expand...
Click to collapse
What output does your cmd window give u? Can you show a screenshot of what your command is and the output.
I see. You are trying to put a lollipop. Still first ya gotta lock it does anyone remember the rules for firmware flash? Is it going to screw up the phone to flash the MM 60 sense 70 ? Dude are you in Europe? The 60 70 I flashed from my microSd was a EUROPE.