Related
Hello,
This will be a long read. Thanks in advance for your patience. I'm not skilled in android or mobile phones in general, so I'll try to be the most descriptive possible on this.
I have a HTC Desire Z phone which suddenly has ceased to work. I've checked a bunch of threads that list some steps to follow, but I've noticed that all the steps are for rooted devices, so I'm unsure about them. The amount of information found is overwhelming.
This phone is not under warranty. I've had it like for two months so far. Apparently, bought as new (boxed, etc) from a store remnant. So I cannot send it to service, etc.
What happened is as follows. 2 days ago I was doing like 3 or 4 simultaneous updates (apps like firefox, skype, google maps...that I remember) via wifi. Some ended, some were about to end I think. I left the phone unattended for a while, and when I came back, it had a black screen with a red triangle / exclamation icon. I never had similar problems before. Maybe a few restarts because it was unresponsive (which I assume it's normal for a smartphone nowadays).
After this, I removed the battery, put it back, and turned the phone on. It started as usual, but as soon as it connected to the net, when the small synchronizing icon (circling arrow) appeared at the top of the screen, it froze. So I repeated the battery thing and as soon as it started, deactivated the synchronization, the wifi and the data connection.
I don't exactly remember if I was able to deactivate all the three, but the phone froze again. Only got a white screen with the HTC logo in the next boot. The usual "quietly brilliant"-or something message never appeared. Stuck forever. Repeated a few times and same thing.
So I entered the "Volume Down + Power Menu", and hit Factory Reset. It seemed to restart, showed a black screen with a circling green + phone icon and an animated progress bar below (not showing progress, just animating), and after a while the screen went totally black. Some seconds later, the phone vibrated 7 times. And it still does this if I repeat the factory reset operation.
BTW, I don't understand why at the right-end of the progress bar, there's a small micro-sd icon, like if the phone were trying to read or write anything from/to the sd card (a factory reset should not need anything external, IMO). Anyway, this process behaves exactly with or without an sd card in the slot.
The phone does not start after this vibration-thing. I have to remove the battery, wait some seconds and put it back. After this, it starts and immediately shows the previous animation and does the vibration thing, like if it was in a Factory Reset "loop" (quoted because I have to totally turn it off for it to happen again).
-I assume that the vibration is some sort of error code, but I've not found any source for this, which is kinda stupid.
To break that "loop", I have to start the phone again, with the Volume Down thing, to get the HBOOT menu:
Code:
VISION PVT SHIP [B]S-OFF[/B]
HBOOT-0.85.0013
MICROP-0424
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
After some searches, I noticed that the "S-OFF" part might be an indication that the phone is rooted. At this point, I'm not sure. However, I had (i.e., several days ago) tried to copy/create some file in the filesystem using either the ADB Shell, or a shell application. That was not possible. Isn't this a good indication that the phone was not booting as root?
BTW, phone is not visible through "adb devices". But "fastboot devices" lists it OK.
A command like "fastboot flash recovery ..." ends with
Code:
FAILED (remote: not allowed)
This gives me the idea that the firmware memory (or whatever is named) is read-only at this time (?), so what the "S-OFF" means then?
Anyway...
That happened on day 1 after the problem. Then I found this thread:
http://forum.xda-developers.com/showthread.php?t=2474781
And went through the RUU route, accordingly.
Downloaded the file RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.3_Radio_12.56.60.25_26.10.04.03_M_release_224299_signed.exe from shipped-roms.com, and ran it.
That worked. The OS was reinstalled and the phone was able to boot as factory default.
Side note: This RUU thing actually did a subtle downgrade. The previous installed version was 2.42.405.4, according to the program.
So I began to set up the phone, configured an APN, connected to the Internet, went to the Market and downloaded one required app. It installed successfully, but as soon as I tried to execute it, the phone froze and had to remove the battery to turn it on again. And it went back to the original problem, stuck at boot, white screen + HTC logo. Any subsequent RUU application execution gets hung in the "Reboot to bootloader..." part. Nothing starts to be copied. The phone (in the FASTBOOT USB menu) is also frozen after this. :crying:
I also tried a previous RUU: RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe from the same source. Same behavior.
I have no idea about what happened. The phone was running again, with working phone network, wifi, gps, sd filesystem, etc.
Oh, almost forgot it. Before finding the RUU solution, I tried putting an official Gingerbread firmware in the PC10IMG.zip file, in the root of the SD. The file was parsed OK by the phone, but when I proceeded with the update, it got stuck in the first item (updating "boot" or so - I don't remember). I think this is because the "not allowed" condition I previously got with the fastboot application.
OK. These are some details I got AFTER running some fastboot commands in the phone, now that it's boot stuck again.
First of all, this is my current HBOOT menu header:
Code:
VISION PVT SHIP S-OFF
HBOOT-0.85.0013
MICROP-042[B]5[/B]
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
>fastboot devices
Code:
SH115RT01882 fastboot
>fastboot oem boot
Code:
(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 super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::[B]11111111[/B]
(bootloader) serial number: SH115RT01882
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =493
(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.04.03_M androidboot
(bootloader) .cid=11111111 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=ALL androidboot.mid=PC10***** androidboot.keycap
(bootloader) s=qwerty androidboot.mode=normal androidboot.serialno=SH115R
(bootloader) T01882 androidboot.bootloader=0.85.0013 zygote_oneshot=off k
(bootloader) memleak=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:125342 msec
FAILED (status read failed (Too many links))
finished. total time: 7.101s
After this, the phone is hung in the white screen / HTC logo part.
>fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0013
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 2.42.405.3
(bootloader) serialno: SH115RT01882
(bootloader) imei: 320864213579134
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: [B]PC10*****[/B]
(bootloader) cidnum: [B]11111111[/B]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4133mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 81c588a7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
See that kinda fake modelid and cidnum? I certainly have no idea about what do they mean, but isn't that a proof that the phone is rooted?
>fastboot oem list_partition_emmc
Code:
(bootloader) index, type, start, num
(bootloader) 0, 0x4D, 0x1, 0x3E8
(bootloader) 1, 0x45, 0x3E9, 0x80
(bootloader) 2, 0x46, 0x469, 0x2328
(bootloader) 3, 0x5, 0x2791, 0x43186E
OKAY [ 0.016s]
finished. total time: 0.016s
>fastboot oem check_emmc_mid
Code:
(bootloader) Manufacturer ID, MID=15
(bootloader) eMMC should be samsung
OKAY [ 0.008s]
finished. total time: 0.009s
>fastboot -w
Code:
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.001s
Short question. Any ideas? :fingers-crossed:
Thanks again for your help!
S-OFF means you can basically write to (almost) any part of the device and disables signature checks on firmware images....
riahc3 said:
S-OFF means you can basically write to (almost) any part of the device and disables signature checks on firmware images....
Click to expand...
Click to collapse
Makes sense.
But "fastboot erase userdata" should work then. It only gets "FAILED (remote: not allowed)".
ADB does not find the phone.
RUUs get stuck at the "Reboot to bootloader..." part. Phone also gets stuck here.
I'm stuck too...
S-off, like riahc3 said, means security flags are removed but this is for firmware so it doesn't mean rooted which would be for software. Which from what you've stated I doubt it was rooted.
The shipped bootloader though won't allow for many fastboot commands, that's why you get errors
The cid has been changed to allow for any firmware to be flashed, but the bad news is the Samsung chip which is prone to failure,
At this point I would attempt to flash an engineering bootloader and then custom recovery and os, hopefully you will be good after this
http://forum.xda-developers.com/showthread.php?t=2348266
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
S-off, like riahc3 said, means security flags are removed but this is for firmware so it doesn't mean rooted which would be for software. Which from what you've stated I doubt it was rooted.
The shipped bootloader though won't allow for many fastboot commands, that's why you get errors
The cid has been changed to allow for any firmware to be flashed, but the bad news is the Samsung chip which is prone to failure,
At this point I would attempt to flash an engineering bootloader and then custom recovery and os, hopefully you will be good after this
http://forum.xda-developers.com/showthread.php?t=2348266
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your reply.
I tried this with the engineering bootloader:
>fastboot flash hboot 0.84.2000_hboot-eng.img
Code:
sending 'hboot' (1024 KB)...
OKAY [ 0.187s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.189s
Is "hboot" a special name? According to the fastboot help, after "flash" comes a partition name, and I don't find that in the list returned by "fastboot oem boot".
Anyway, still "not allowed".
hboot, bootloader, SPL, these are all interchangeable terms, you will not see it listed in oem boot because that doesn't list partitions
Being you still have a shipped bootloader that command won't work, you need to flash it as a PC10IMG.zip, the link I attached has a thread on bricks and one on fastboot, read those and there is a link to a PC10IMG.zip that should hopefully work for you
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
hboot, bootloader, SPL, these are all interchangeable terms, you will not see it listed in oem boot because that doesn't list partitions
Being you still have a shipped bootloader that command won't work, you need to flash it as a PC10IMG.zip, the link I attached has a thread on bricks and one on fastboot, read those and there is a link to a PC10IMG.zip that should hopefully work for you
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You mean, copying that file in the SD and booting, right?
Will do.
In that link you attached, there's a section with "Important Brick Info!", with another link to "When all Else Fails Boot From SD".
They talk about booting CM7.1 from recovery. But I don't see (at least, it's not clear for me) any engineering hboot in the file they attach. Is this something completely different? And it seems it's for rooted phones...
When you say "Being you still have a shipped bootloader that command won't work, you need to flash it as a PC10IMG.zip", these two things are pretty clear for me:
I DO need the engineering hboot.
I would need to put this engineering hboot image inside a compressed file named PC10IMG.zip in the sd card, and boot the phone with that.
If this is the case, I have the image at hand, but I've noticed that all the PC10IMG files include a file named "android-info.txt" and I don't know how to create this one (maybe it's easy).
Is this the path to follow?
Thanks for the time you're investing on this.
PS. What is this then?
Code:
(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
Copied from what "fastboot oem boot" returns.
Its checking boot sequence not listing all partitions
See the 30th post
http://forum.xda-developers.com/showthread.php?t=
Hopefully you can flash the PC10IMG.zip and will then have an engineering bootloader and a custom recovery, with these you will have a much higher likelihood of fixing your phone, but being you have the chip prone to failure you may need to boot from sd
You'll need a custom recovery in order to boot from SD, this is a last resort though
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Its checking boot sequence not listing all partitions
See the 30th post
http://forum.xda-developers.com/showthread.php?t=
Hopefully you can flash the PC10IMG.zip and will then have an engineering bootloader and a custom recovery, with these you will have a much higher likelihood of fixing your phone, but being you have the chip prone to failure you may need to boot from sd
You'll need a custom recovery in order to boot from SD, this is a last resort though
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ugh, you didn't specify a thread id in that link.
Bump
What happened after the flash?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
What happened after the flash?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, you sent me some link and addressed me to the 30th post, but the link was incomplete.
http://forum.xda-developers.com/showthread.php?t=1728208y
Sent from my SGH-T699 using XDA Premium 4 mobile app
demkantor said:
http://forum.xda-developers.com/showthread.php?t=1728208y
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi.
Code:
Parsing...[SD ZIP]
[ 1 ] RECOVERY
[ 2 ] SPLASH1
[ 3 ] TP
[ 4 ] TP
[ 5 ] BOOTLOADER
[ 6 ] RADIO_V2
[ 7 ] RADIO_CUST
Answered Yes to "Do you want to start update?".
Frozen as soon as it begins the update:
Code:
[I][ 5 ] BOOTLOADER Updating[/I]
.
Emmc is bad, need to replace motherboard, sorry
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Emmc is bad, need to replace motherboard, sorry
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, I've already contacted HTC for this. I have no idea about how much would it cost, but they can do it.
Anyway, taking advantage from your expertise here, do you think if in these cases they replace just the chip or the whole motherboard?
Also, -and I prefer to ask it here first before showing myself as a daring retard-.... This device is the euro version...do you think it makes sense if I request a change to the usa version? (I'm talking about the HSDPA/3G frequencies here). I'm pretty sure this can be done only at hardware level (probably a single chip replacement?), but if they replace the motherboard, I don't see how difficult would be just "putting this instead of this one", considering that we don't use the euro frequencies here either. Is this a valid request?
Thanks for your help.
It will cost more than its worth to have HTC do it, unless somehow you still have a warranty but that would be surprising. Yes the radio bands differ between the desire z and g2, what I would suggest is buying a broken one from eBay for cheap and swap logic boards, if you dig I bet you can find one for 40$ or less which will be much cheaper than sending it to htc
Sent from my Nexus 7 using XDA Premium 4 mobile app
Buy a new one bro..
Hello.
I sent my phone to HTC and they replaced the motherboard. The whole cost was still cheaper than buying a new phone, so I went that route.
Since they get the replacements from their available stock, I had not much control on what they were using. So guess what...Samsung eMMC chip again.
Three questions:
1-Is this chip really that bad and I'm condemned? :laugh:
2-Rooting my phone would give me any options if the same problems happens in a future?
3-Considering that:
a) I have the old motherboard
b) a Sandisk eMMC chip does cost about 10 bucks
c) I know someone with the right tools to replace this chip.
If the same problem happens in a future and I replace the chip myself, should this work immediately of should I have to "prepare" this chip with some special software?
Thanks for all the support given with my issue.
The Samsung emmc is prone to failure but that doesn't mean it will die in a week, a month or a year, some have had it work for years
Rooting and true radio s-off is amazing and will help with other problem, just not a fried emmc, not even JTAG can fix this
Soldering a new chip is tricky if you haven't done real fine soldering before, so be careful doing it yourself
Depends how and where you bought the chip, many vision specific ones come preloaded with firmware/software
If it doesn't you will need JTAG equipment to flash it
Hope all goes well for you!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hellooow!
I noticed i got an message when relocking my bootloader.
It is relocked but still wondering what this means?
see bold text
hope someone knows! Thnx!
I'm S-OFF
HTC one m8 stock android 4.4.4
3.28.401.9
Radio 1.22.21331147A1.29G
ps: already searched foru and google and www etc...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully…
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again…
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.153s
0kk0 said:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully…
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again…
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.153s
Click to expand...
Click to collapse
Hi,
i have the same problem- searched the web etc, i didnt find what is the problem.
and it is not relocked on my phone, so i suppose its not on yours either
mato123 said:
Hi,
i have the same problem- searched the web etc, i didnt find what is the problem.
and it is not relocked on my phone, so i suppose its not on yours either
Click to expand...
Click to collapse
Hi!
No mine relocks fine.. it says RELOCKED and i can unlock it again and relock etc.. but everytime got that "error" message.
Are you s-off?
0kk0 said:
Hi!
No mine relocks fine.. it says RELOCKED and i can unlock it again and relock etc.. but everytime got that "error" message.
Are you s-off?
Click to expand...
Click to collapse
no, im S-ON and every time i try it says ***UNLOCKED***
mato123 said:
no, im S-ON and every time i try it says ***UNLOCKED***
Click to expand...
Click to collapse
you could try to download correct 0P6BIMG.zip for your device and place it on sdcard in your phone.
Then flash it from bootloader...
It flashed correctly on mine(unlocked) without fastboot oem lock
And then try to relock it again?
0kk0 said:
you could try to download correct 0P6BIMG.zip for your device and place it on sdcard in your phone.
Then flash it from bootloader...
It flashed correctly on mine(unlocked) without fastboot oem lock
And then try to relock it again?
Click to expand...
Click to collapse
Sorry, what is 0P6BIMG.zip? how can i find one for myself? im at&t one m8.
Also what should i write in fastboot command?
mato123 said:
Sorry, what is 0P6BIMG.zip? how can i find one for myself? im at&t one m8.
Also what should i write in fastboot command?
Click to expand...
Click to collapse
That zip is all in one file to flash stock system/os firmare recovery etc...
Here is more info for flashing RUU for your device: http://forum.xda-developers.com/att-htc-one-m8/general/lolipop-ruu-htc-att-m8-t3075854
0kk0 said:
That zip is all in one file to flash stock system/os firmare recovery etc...
Here is more info for flashing RUU for your device: http://forum.xda-developers.com/att-htc-one-m8/general/lolipop-ruu-htc-att-m8-t3075854
Click to expand...
Click to collapse
i ran RUU.exe and this is what i get:
capture.png where it rebooted to bootloader, fastboot usb mode, took it quite a while, cca 1 min
capture1.png says sth is wrong with usb
mato123 said:
i ran RUU.exe and this is what i get:
capture.png where it rebooted to bootloader, fastboot usb mode, took it quite a while, cca 1 min
capture1.png says sth is wrong with usb
Click to expand...
Click to collapse
strange...
have you tried:
1) From a powered off state, hold VOLUME DOWN while powering on the device.
2) Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
3) Connect the device to the PC while in this state and attempt the ROM update again.
0kk0 said:
I noticed i got an message when relocking my bootloader.
I'm S-OFF
Click to expand...
Click to collapse
There is no reason to relock the bootloader, since you are s-off.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
0kk0 said:
you could try to download correct 0P6BIMG.zip for your device and place it on sdcard in your phone.
Then flash it from bootloader...
It flashed correctly on mine(unlocked) without fastboot oem lock
And then try to relock it again?
Click to expand...
Click to collapse
It won't work for that guy, since he is s-on.
The reason it flashed for you with the bootloader unlocked, is since you are s-off.
redpoint73 said:
There is no reason to relock the bootloader, since you are s-off.
Click to expand...
Click to collapse
thnx for your answer but doenst answer my question
i got an "error" ans whas wondering what it means etc...
mato123 said:
i ran RUU.exe and this is what i get:
capture.png where it rebooted to bootloader, fastboot usb mode, took it quite a while, cca 1 min
capture1.png says sth is wrong with usb
Click to expand...
Click to collapse
You have a USB connectivity issue, so this is probably the reason why fastboot oem lock does not work.
Make sure you run the command while the phone is booted into bootloader-fastboot mode.
redpoint73 said:
You have a USB connectivity issue, so this is probably the reason why fastboot oem lock does not work.
Make sure you run the command while the phone is booted into bootloader-fastboot mode.
Click to expand...
Click to collapse
tnx for your answer.
i was in bootloader in fastboot usb mode already.
i sent you PM regarding whole situation. should i continue to write here or make a new thread?
hi,
someone gave me a bricked HTC M8 and i wanna fix it for him. i don't know what got him to be bricked...
the situation is this:
- Boot Loop
- Fastboot working
- Unlocking Worked
- Able to flash TWRP and enter recovery mode
- mounting for all partition fails with unable to mount
- TWRP "Repair" fails: "E:/sbin/e2fck -fp /dev/block/mmcnlk0p47 proccess ended with ERROR=8 ; unable to repair /data ; Error repairing fail system"
- TWRP "Change File System" to ESX4 not working: "unable to mount /data ; Unknown MTP message type: 1 ; Error changing file system; unable to mount /system ; unable to mount /data ; unable to mount /devlog ; unable to mount storage"
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.1540.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 55eb39ab
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
PLS HELP what doo?
Install the dev edition ruu.....
Mr Hofs said:
Install the dev edition ruu.....
Click to expand...
Click to collapse
how?
omer323 said:
hi,
someone gave me a bricked HTC M8 and i wanna fix it for him. i don't know what got him to be bricked...
the situation is this:
- Boot Loop
- Fastboot working
- Unlocking Worked
- Able to flash TWRP and enter recovery mode
- mounting for all partition fails with unable to mount
- TWRP "Repair" fails: "E:/sbin/e2fck -fp /dev/block/mmcnlk0p47 proccess ended with ERROR=8 ; unable to repair /data ; Error repairing fail system"
- TWRP "Change File System" to ESX4 not working: "unable to mount /data ; Unknown MTP message type: 1 ; Error changing file system; unable to mount /system ; unable to mount /data ; unable to mount /devlog ; unable to mount storage"
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.1540.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 55eb39ab
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
PLS HELP what doo?
Click to expand...
Click to collapse
You CID number BS_US001 is developper edition M8. As @Mr Hofs suggested, Download Dev edition RUU, Boot into fastboot and install RUU.
Grab this RUU.exe (not OTA, RUU): https://onedrive.live.com/?authkey=!AJ5pbUC2atPkSaA&id=8B8E71545D3D985B!1658&cid=8B8E71545D3D985B
Turn On phone and go to bootloader, connect it to PC, install drivers and run RUU.exe on PC.
omer323 said:
- Unlocking Worked
Click to expand...
Click to collapse
I assume you mean bootloader unlock, as the term "unlock" is vague and can mean several things.
You will need to relock to run the RUU, since you are s-on. Do so with the command:
fastboot oem lock
Also, this isn't a brick. A brick by definition is not fixable. At least not without opening the phone, and JTAG, replacing motherboard, etc.
What you have is no boot, and you don't know how to recover. That isn't a brick.
WTF.
i did "fastboot oem lock" which resulted with:
[PGFS] partition_update_pgfs: pg1fs_security
TZ_HTC_SVC_ENC ret = 0
[PGFS] partition_update_pgfs: pg2fs_sec_recover
Lock successfully...
deinit_lcd
mipi display off
mdp_clock_off
turn off fd8c2308 failed 1 times. Try again...
disable_mmss_clk done
pll1_disable done
TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7
[CRITICAL] SPMI write command failure:
= 4
[CRITICAL] SPMI write command failure:
= 4
[ERR] Cannot halt SPMI arbiter!!
[INFO] Rebooting device
us read failed (No such file or directory))
tal time: 1.227s
than i run RUU, which failed, i pressed recover, it told to me to unplug the device and shut it down.
and not it won't turn on no mather what!! not even battery logo....
WHAT HAVE I DONE
omer323 said:
WTF.
i did "fastboot oem lock" which resulted with:
Click to expand...
Click to collapse
Was it unlocked before, or not? This wan't clear to me, from what you posted.
After the command, was it RELOCKED or UNLOCKED?
omer323 said:
than i run RUU, which failed
Click to expand...
Click to collapse
What was the failure message and/or error number?
RUU failed before sending or writing anything?
You need to be specific, and provide as much detail as necessary.
omer323 said:
i pressed recover, it told to me to unplug the device and shut it down.
and not it won't turn on no mather what!! not even battery logo....
Click to expand...
Click to collapse
What does that mean "no matter what"? I doesn't tell us anything about what you tried, or didn't try. Please be specific instead of vague statements, that tell us nothing.
Try holding power and vol up for 30 to 60 seconds, and see if there is any change.
I don't think you did anything serious, that wasn't already screwed up. You are s-on, and assuming the RUU failed before sending/writing anything, then a true brick is unlikely.
redpoint73 said:
Was it unlocked before, or not? This wan't clear to me, from what you posted.
Click to expand...
Click to collapse
UNLOCKED
redpoint73 said:
After the command, was it RELOCKED or UNLOCKED?
Click to expand...
Click to collapse
RELOCKED
redpoint73 said:
What was the failure message and/or error number?
RUU failed before sending or writing anything?
You need to be specific, and provide as much detail as necessary.
Click to expand...
Click to collapse
i don't remember exactly what heppened, BUT i found RUU log file on my computer,
i attached the log.
redpoint73 said:
What does that mean "no matter what"? I doesn't tell us anything about what you tried, or didn't try. Please be specific instead of vague statements, that tell us nothing.
Try holding power and vol up for 30 to 60 seconds, and see if there is any change.
I don't think you did anything serious, that wasn't already screwed up. You are s-on, and assuming the RUU failed before sending/writing anything, then a true brick is unlikely.
Click to expand...
Click to collapse
the screen is black.
every combination of buttons i try results NOTHING - nothing on screen, no vibrations...
i tried holding all the combinations for a long time...
the only thing i get - if i plug the device via USB, every ~20 seconds i see in device manager that it disconnect for a second and connected again as QHSUSB_BULK
THANK YOU SO MUCH FOR HELPING~!!!
omer323 said:
every combination of buttons i try results NOTHING - nothing on screen, no vibrations...
i tried holding all the combinations for a long time...
Click to expand...
Click to collapse
You shouldn't be trying "every" combination. You should be trying the one I specified.
Put the phone on wall charger (not connected to computer) or a few hours, and try again.
Then try the combo I specified. Try it with and without the wall charger connected.
---------- Post added at 01:03 PM ---------- Previous post was at 01:01 PM ----------
What RUU did you run exactly? Was it the one linked in Post #5 above? What was the exact file name?
I don't have any reason to be suspicious of this link, specifically. But on the other hand, this RUU is easily downloaded direct from HTC, and I don't see a reason to download from some other (unconfirmed) source. Or for all we know, the download was corrupt/damaged.
redpoint73 said:
You shouldn't be trying "every" combination. You should be trying the one I specified.
Click to expand...
Click to collapse
tried it.... nothing...
redpoint73 said:
Put the phone on wall charger (not connected to computer) or a few hours, and try again.
Then try the combo I specified. Try it with and without the wall charger connected.
Click to expand...
Click to collapse
ill try that...
redpoint73 said:
---------- Post added at 01:03 PM ---------- Previous post was at 01:01 PM ----------
Click to expand...
Click to collapse
redpoint73 said:
What RUU did you run exactly? Was it the one linked in Post #5 above? What was the exact file name?
I don't have any reason to be suspicious of this link, specifically. But on the other hand, this RUU is easily downloaded direct from HTC, and I don't see a reason to download from some other (unconfirmed) source. Or for all we know, the download was corrupt/damaged.
Click to expand...
Click to collapse
yes, the link he gave me.
filename: RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2
omer323 said:
filename: RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2
Click to expand...
Click to collapse
Well, the file name is right. Assuming the file is what it says it is, and not damaged or corrupt during download, it possible for the correct RUU to brick the phone. It doesn't happen often, but I have seen it happen a few times, even on completely stock (unmodified) M8 devices and the correct, official RUU.
Or its possible that it was messed up before, such as bad emmc, and the RUU just made it worse.
In any case, charging for a few hours, then trying power+vol up is about all you can do at this point.
QHUSB is Qualcomm emergency mode. Try to get out of it by pressing (for long) Vol UP + Power.
For me it looks like fried eMMC chip... Sometimes it happens. Some time ago my One M7 died at me because of this in exactly the same way.
eMMC chip was corrupted before running RUU - unable to mount partition and errors during "fastboot oem lock".
redpoint73 said:
I don't have any reason to be suspicious of this link, specifically. But on the other hand, this RUU is easily downloaded direct from HTC, and I don't see a reason to download from some other (unconfirmed) source.
Click to expand...
Click to collapse
It's from this thread: http://forum.xda-developers.com/showthread.php?t=2701376
I don't think it's suspicious or unconfirmed.
I'm pretty sure that this RUU.exe is correct, because I was flashing with it few times.
Please check MD5 checksum. My working RUU.exe (downloaded from thread linked above) checksum is: c661c073d368274c3137d5080c88a45c and file size of 1 548 439 552 bytes (on disk).
radkor said:
It's from this thread: http://forum.xda-developers.com/showthread.php?t=2701376
I don't think it's suspicious or unconfirmed.
I'm pretty sure that this RUU.exe is correct, because I was flashing with it few times.
Click to expand...
Click to collapse
As I said, I don't have any reason to doubt the source. But for lack of any other evidence (the subsequent report that you did use it a few times does count for something there) I have no reason to trust it more than the official source. The RUU is available for download direct from HTC, so I don't see a reason to use a mirror (unless its faster): http://www.htc.com/us/support/htc-one-m8/news/
Again, I don't doubt the mirror. Mr Hofs has made valuable contributions here, so if he posted it; I trust it. But I was just trying to consider every possibility for the OP's issue.
redpoint73 said:
The RUU is available for download direct from HTC, so I don't see a reason to use a mirror (unless its faster): http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
OK, but on HTC's site it's only newest MM update available for download.
I can't see a link for older LP ROM which OP was using. Best for him (as he has S-ON) was to reflash ROM version that he already have, basing on pasted "fastboot getvar all" result.
If he would flash newer version (MM) with S-ON, then he will be stuck on this newer version without possibility to downgrade, unless he's S-OFF.
As I said earlier, phone supposedly "bricked" earlier, what you can see during "fastboot oem lock" and resulting error messages after issuing this command.
QHSUSB_DLOAD mode is because of bad NAND.
I've had similiar issue with my M7: http://forum.xda-developers.com/htc-one/help/bricked-device-swap-to-dev-ed-partially-t3015574/
I hope you're not blaming me for unsuccessful OP's phone flashing or earlier bricking?
radkor said:
OK, but on HTC's site it's only newest MM update available for download.
Click to expand...
Click to collapse
You're right, I forgot we were talking about LP (OP's current state).
The direct HTC link for OP's current LP version is here: http://dl3.htc.com.s3.amazonaws.com/application/RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2.exe
radkor said:
I hope you're not blaming me for unsuccessful OP's phone flashing or earlier bricking?
Click to expand...
Click to collapse
Of course not! I never stated any such thing. Just considering every possibility, like a corrupt RUU file. But as I already stated, the fact that you reported using it successfully (and more than once) tells me the file is good.
redpoint73 said:
The direct HTC link for OP's current LP version is here: http://dl3.htc.com.s3.amazonaws.com/application/RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2.exe
Click to expand...
Click to collapse
I'm downloading it right now just to compare it with RUU.exe posted on Mr Hofs' thread.
EDIT:
OK, CRC is exactly the same. Everyone can check this. So I think we can exclude corrupted RUU.exe linked on Mr Hofs' thread. It's exactly the same as the file on HTC servers.
charged for hours, pressed VOL-UP+POWER for 2 minutes with or without charging, and..... NOTHING
the only response i get is the red led when charged and the QHUSB when plugged to computer
so i guess it's bricked for ever
omer323 said:
charged for hours, pressed VOL-UP+POWER for 2 minutes with or without charging, and..... NOTHING
the only response i get is the red led when charged and the QHUSB when plugged to computer
so i guess it's bricked for ever
Click to expand...
Click to collapse
Most likely, yes.
I mentioned early in the thread that this wasn't a brick. As long as the screen comes on (as it did earlier), it almost never is. But this is the relatively uncommon exception, which can be caused by a bad emmc or radio brick.
omer323 said:
charged for hours, pressed VOL-UP+POWER for 2 minutes with or without charging, and..... NOTHING
the only response i get is the red led when charged and the QHUSB when plugged to computer
so i guess it's bricked for ever
Click to expand...
Click to collapse
Try Power + Volume Up + Volume Down more that 2 minutes ... usually about to close 3 minutes, it should up. This is how I got out from QHUSD many times...
But a bad emmc is also possible .. if that is the reason, then only HTC can fix it.
Also after fastboot oem lock, did you do fastboot reboot-bootloader to confirm the bootloader is relocked then only run RUU ?
I don't see you mentioned that except after fastboot oem lock you ran the RUU right away.
Originally unlocked bootloader through HTC-DEV
CID: 11111111
Hboot 3.19.0.0000
Radio-1.2121331147A1.19_2G
M8_UL_CA PVT SHIP S-OFF
I'm trying to relock the bootloader so I can RUU, however keep getting the following error when running "fastboot oem lock"
Code:
(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) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.230s
After the above message, the phone goes from unlocked -> relocked. However I believe the phone is still actually unlocked because I'm getting Error: 155 when I try to run an RUU. I also can see the red text on the charging screen indicating the phone is unlocked.
I have also used this method http://forum.xda-developers.com/showthread.php?t=2708571 to try unlock/relock, and also tried to relock and use HTC-DEV to lock but no matter what, I'm still getting Error 155.
Also, none of the user data is being wiped when I use fastboot flash unlocktoken Unlock_code.bin
blazerxzero said:
Originally unlocked bootloader through HTC-DEV
CID: 11111111
Hboot 3.19.0.0000
Radio-1.2121331147A1.19_2G
M8_UL_CA PVT SHIP S-OFF
1. I'm trying to relock the bootloader so I can RUU, however keep getting the following error when running "fastboot oem lock"
2. After the above message, the phone goes from unlocked -> relocked. However I believe the phone is still actually unlocked because I'm getting Error: 155 when I try to run an RUU. I also can see the red text on the charging screen indicating the phone is unlocked.
Click to expand...
Click to collapse
1. You don't need to relock bootloader to run RUU on S-Off device.
2. Are you trying to run Marshmallow RUU ? You'll get error 155 if the current firmware is lower than Marshmallow. You need to flash its Marshmallow firmware first then run RUU.
Thanks for the reply, I tried your method of matching the RUU with the firmware version and got a different error.
Error couldn't allocate space, even though the RUU image was smaller than the available storage.
The solution which resolved the problem was to rename the correct RUU version zip load onto SD card and flash using the bootloader auto-detection method.
Hey guys
Last night my phone(HTC m8 eye 5.07.401.1) slowed down badly, after a while it restarted automatically and fastboot screen showed up.
Things I've tried:
1-Restarting the phone after fully charging it for 1 billion times (worked once but the phone was frozen and restarted automatically again)
2- Trying to unlock the boot loader(Got the unlock_code.bin file, tried to load it to the phone using adb, it said success or done or something like that but nothing changed)
3-Trying to flash the official rom , didn't work
4-removing the SIM and SD card and restarting the phone, didn't work
by the way, usb debugging was not active last time the phone was working normally, Also the phone have not experienced any unusual activity like rooting or flashing custom roms or...
What can I do?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA00000000000
(bootloader) imei: 3580000000000000
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mels_tuhl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B81000
(bootloader) cidnum: HTC__J15
(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: 5c9466dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
------------------------------------------------------------------------------------------- fastboot results----------------------
C:\fastboot>fastboot devices
FA57LY901038 fastboot
C:\fastboot>fastboot oem rebootRUU
...
(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.041s]
finished. total time: 10.041s
C:\fastboot>fastboot flash zip update.zip
target reported max download size of 1826332672 bytes
sending 'zip' (1687274 KB)...
OKAY [ 57.179s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 118.969s
---------------------------------------------------------------------------------------
I don't have the "eye", only the "standard" M8, but I'll try to help as much as I can, as far as anything that I believe is common between the two M8 versions (unlocking bootloader, flash RUU, etc.).
bahmaniq said:
2- Trying to unlock the boot loader(Got the unlock_code.bin file, tried to load it to the phone using adb, it said success or done or something like that but nothing changed)
Click to expand...
Click to collapse
So the bootloader screen says LOCKED? I assume that is what you mean by "nothing changed", but I want to be clear on this.
bahmaniq said:
3-Trying to flash the official rom , didn't work
Click to expand...
Click to collapse
What is the exact file name? It's best to provide specific file name/version info when asking for help. I've seen a lot of cases where the person "thought" they were flashing the right RUU, but in fact, it was not even the right one.
But based on what you've described so far (bootloader will not unlock, RUU will not run, emmc error) it sounds like a hardware emmc failure.
redpoint73 said:
So the bootloader screen says LOCKED? I assume that is what you mean by "nothing changed", but I want to be clear on this.
Click to expand...
Click to collapse
Yes, *****LOCKED***** it says, I guess it is very serious on this one. Based on knowledge I gathered in these 2 days, I think it should show a black confirmation screen after I try to unlock it (using *.bin file), but it simply does not.
redpoint73 said:
What is the exact file name? It's best to provide specific file name/version info when asking for help. I've seen a lot of cases where the person "thought" they were flashing the right RUU, but in fact, it was not even the right one.
Click to expand...
Click to collapse
Yes you are right, RUU is the most important part and I did not elaborate. There is a big chance that the RUU is the Achilles Heel!! Exact file name is: 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
redpoint73 said:
But based on what you've described so far (bootloader will not unlock, RUU will not run, emmc error) it sounds like a hardware emmc failure.
Click to expand...
Click to collapse
So, that's it, I'm gonna play "One last goodbye" and let the history judge. 2 years of EMERGENCY CALLS ONLY, 2 years of zero antenna...
After a silent peaceful night
You took my heart away
oh I wish, I wish you could have stayed
bahmaniq said:
Yes you are right, RUU is the most important part and I did not elaborate. There is a big chance that the RUU is the Achilles Heel!! Exact file name is: 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Click to expand...
Click to collapse
That is not the RUU for the M8 eye. It's the RUU for the "regular" Euro M8. That is why you have signature error. Not sure where you can find the RUU for the "eye".
One more questions, is the phone going to fastbootRUU mode after running the command: fastboot oem rebootRUU
The error "command never completed" would suggest NO. But I'm curious whether the phone actually goes to RUU mode or not. RUU mode is signified by a black screen with large HTC logo. A progress bar will also appear below the logo, when the RUU starts to install. But in your case, you my have not gotten far enough for the progress bar to appear.
If the phone does not in fact even go to RUU mode due to emmc error, then it is probably irrelevant whether you have the right RUU or not. You will not get the RUU to run, if you can't even enter RUU mode.
redpoint73 said:
That is not the RUU for the M8 eye. It's the RUU for the "regular" Euro M8. That is why you have signature error. Not sure where you can find the RUU for the "eye".
One more questions, is the phone going to fastbootRUU mode after running the command: fastboot oem rebootRUU
The error "command never completed" would suggest NO. But I'm curious whether the phone actually goes to RUU mode or not. RUU mode is signified by a black screen with large HTC logo. A progress bar will also appear below the logo, when the RUU starts to install. But in your case, you my have not gotten far enough for the progress bar to appear.
If the phone does not in fact even go to RUU mode due to emmc error, then it is probably irrelevant whether you have the right RUU or not. You will not get the RUU to run, if you can't even enter RUU mode.
Click to expand...
Click to collapse
It has been a long time since the last time I was here but the problem is not solved. Sorry for the delay, and No the black screen with HTC logo does not appear.
Is there anything I can do to get rid of this fastboot screen? or the phone is useless