Hello an sorry for my bead english.
Today i tried to root my htc 10 and after i relockd oem, my patter to unlock the encription its not working... I can't enter in to twrp.
I tried to unlock the bootloader again and nothig...
It's there any way to recover frome this?
Are you able to enter download mode still (volume down+power). If so do the command "fastboot getvar all" in fastboot mode and post back here. pls delete imei or serial number info
ayyu3m said:
Are you able to enter download mode still (volume down+power). If so do the command "fastboot getvar all" in fastboot mode and post back here. pls delete imei or serial number info
Click to expand...
Click to collapse
Thx for the reply!
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: FA65MBN00470
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 354261072618309
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__034
DjAurelian83 said:
Hello an sorry for my bead english.
Today i tried to root my htc 10 and after i relockd oem, my patter to unlock the encription its not working... I can't enter in to twrp.
I tried to unlock the bootloader again and nothig...
It's there any way to recover frome this?
Click to expand...
Click to collapse
When TWRP asks for the password (your post looks like you still have TWRP installed?), tap "cancel" (or something like that ~ I don't remember exactly but I think it's cancel)
Then go to advanced > file manager and navigate to data/system/locksettings.db and delete that.
When you reboot you can enter a new password.
xunholyx said:
When TWRP asks for the password (your post looks like you still have TWRP installed?), tap "cancel" (or something like that ~ I don't remember exactly but I think it's cancel)
Then go to advanced > file manager and navigate to data/system/locksettings.db and delete that.
When you reboot you can enter a new password.
Click to expand...
Click to collapse
It's "reloked". I can't access twrp. I need a way to unlock bootloader witouth bootin in to android..... so i cand access twrp an install the backup... i don't know....
I was talking about the pattern enctiption @ the boot of android not frome the bigining of twrp..
DjAurelian83 said:
It's "reloked". I can't access twrp. I need a way to unlock bootloader witouth bootin in to android..... so i cand access twrp an install the backup... i don't know....
I was talking about the pattern enctiption @ the boot of android not frome the bigining of twrp..
Click to expand...
Click to collapse
Boot your phone to download mode by pressing power + vol down to boot it up.
From download mode select bootloader
From bootloader select recovery
If TWRP is still on your phone it'll take you to that.
And I realize what were talking about. Following my previous instructions will remove the pattern lock (and any other password/PIN) via TWRP so you can boot into your phone.
xunholyx said:
Boot your phone to download mode by pressing power + vol down to boot it up.
From download mode select bootloader
From bootloader select recovery
If TWRP is still on your phone it'll take you to that.
And I realize what were talking about. Following my previous instructions will remove the pattern lock (and any other password/PIN) via TWRP so you can boot into your phone.
Click to expand...
Click to collapse
I tried and it's getting stuck in a reboot loop, or its shuting down after 1-2 seconds
As long as i know twrp works only if bootloader is unloked.
Ok, today i manage to reinstall the firmware and when i try to enter recovery mode, i get the exclamation red triangle. It's not shuting down any more.
I forgot to say, i have a clean twrp recovery saved if it help's somehow, including the system_image.emmc ...
Ok... So i did it!!!!!!!!!!!!!! It's alive again!!!!!!!!!
Hope this help's all with the same issue
If are in the same "place" follow there spteps and u will be able to hard reset ur phone:
1. reflush your phone firmware. This will erase any custom recovery and instrall the stock one.
2. reboot in to download mode -> reboot in to bootloader -> reboot to recoverry
3. in recoverry you will get the red triangle with exclamation marck, don't get cared The red triangle with exclamation isn't an error or problem or anything, it's what the stock recovery looks like!
At this screen, press Volume Up + Power, and you get the menu.
After that is all yours! Navigate volume bottons to wher you need!
If u got qwestions just reply to this post.
Thnx and have funn u all!!
Related
My cousins phone will only turn on for the like 5 seconds than keep on turning off and on. He has a locked bootloader ,factory recovery and rom and is s-on. I think there is something wrong with the recovery mode because it boot into it but I can still go into fastboot mode. My question is could I still unlock the bootloader and put a custom recovery because I don't think he put it into usb debugging and if I can't then what else could I do to fix it.
hamugee68 said:
My question is could I still unlock the bootloader and put a custom recovery because I don't think he put it into usb debugging and if I can't then what else could I do to fix it.
Click to expand...
Click to collapse
You don't need debugging to unlock the bootloader and install custom recovery. Those things are done with fastboot, which doesn't require debugging to be on. Only adb needs debugging to be on.
redpoint73 said:
You don't need debugging to unlock the bootloader and install custom recovery. Those things are done with fastboot, which doesn't require debugging to be on. Only adb needs debugging to be on.
Click to expand...
Click to collapse
I tried to unlock the bootloader everything was going well until I confirmed it on the phone and it rebooted to a red triangle and exclamation point like it did when I tried to boot into recovery. I don't know what to do now.
hamugee68 said:
I tried to unlock the bootloader everything was going well until I confirmed it on the phone and it rebooted to a red triangle and exclamation point like it did when I tried to boot into recovery. I don't know what to do now.
Click to expand...
Click to collapse
That is the stock recovery. Try holding vol up (or maybe its vol down, I can never remember) then just pressing and releasing the power button, to show the recovery menu options. From there, just reboot the phone. Or alternately, just hold vol up and power until the phone reboots (may need to hold the buttons for a minute or so).
Reboot into bootloader, and see if the bootloader was successfully unlocked or not.
If so, go into fastboot mode and continue the process (flash TWRP)>
redpoint73 said:
That is the stock recovery. Try holding vol up (or maybe its vol down, I can never remember) then just pressing and releasing the power button, to show the recovery menu options. From there, just reboot the phone. Or alternately, just hold vol up and power until the phone reboots (may need to hold the buttons for a minute or so).
Reboot into bootloader, and see if the bootloader was successfully unlocked or not.
If so, go into fastboot mode and continue the process (flash TWRP)>
Click to expand...
Click to collapse
The recovery menu is frozen and when i boot into bootloader it says locked.
hamugee68 said:
The recovery menu is frozen and when i boot into bootloader it says locked.
Click to expand...
Click to collapse
Enter bootloader-fastboot mode (if its not already) and try to unlock the bootloader again.
redpoint73 said:
Enter bootloader-fastboot mode (if its not already) and try to unlock the bootloader again.
Click to expand...
Click to collapse
I tried to unlock it three time and everytime it was the same.
hamugee68 said:
I tried to unlock it three time and everytime it was the same.
Click to expand...
Click to collapse
Same unlock token every time? If so, try going thru HTCDev.com again, and get a new token, and see if it makes any difference.
Otherwise, if you version has RUU, I'd try RUU and start the bootloader unlock process over again.
redpoint73 said:
Same unlock token every time? If so, try going thru HTCDev.com again, and get a new token, and see if it makes any difference.
Otherwise, if you version has RUU, I'd try RUU and start the bootloader unlock process over again.
Click to expand...
Click to collapse
I tried both when i would try to unlock the bootloader with a different token i got the same result and when i try to use ruu it would just restart the phone.
hamugee68 said:
I tried both when i would try to unlock the bootloader with a different token i got the same result and when i try to use ruu it would just restart the phone.
Click to expand...
Click to collapse
Need more info. Do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
And what RUU are you trying (exact file name)?
redpoint73 said:
You don't need debugging to unlock the bootloader and install custom recovery. Those things are done with fastboot, which doesn't require debugging to be on. Only adb needs debugging to be on.
Click to expand...
Click to collapse
I'm on the same boat, can't unlock the bootloader, it goes all fine until it should promp me on the phone screen to confirm bootloader unlock, i simply stay in the bootloader as if nothing happened.
(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: 6.12.161.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Hie everyone i am new here and i have an htc one m8 which is bootloader locked , s on and i dont have root access nor custom recovery installed .
All other tutorials i found here are more so related to those htc m8 devices with either bootloader unlocked or custom recovery installed and since the device is stuck on decrypt storage page i cant install an RUU firmware exe i downloaded and also i cant install a custom firmware too .
i found a tutorial on how to unlock bootloader and did got my token id from fastboot since it is the only thing working so far and am stuck with the stock recovery so i cannot get into adb mode.
when flashing the unlock code bin file in fastboot it says successfully and the warning page also appears which prompts me to choose to unlock bootloader or not . and after selecting unlock bootloader the device restarts into recovery mode i which i thought i have to factory reset for the bootloader process to be complete but still after factory reset the device boots straight to the decrypt storage page and when i reboot again into fastboot mode the bootloader is still locked like nothing happened . tried all methods to unlock bootloader and not factory reset in hope of getting better results but still its the same problem . so if there is another solution that might help me to unlock my bootloader or flash custom recovery or force it to install my RUU exe firmware without debugging i would greatly appreciate it
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Sxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__016
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
thats from getvar
and i also downloaded this firmware i dont know if it is the correct one for my device since its showing region as south africa (Region : VODA-Africa-South)
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
any help related to my problem is greatly appreciated
Just follow this ,Might help
The correct RUU for your device
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Just follow this ,Might help
The correct RUU for your device
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
ok let me try it and update you with the results
hie when i type fastboot oem rebootRUU it reboots and boots into the system where it shows decrypt storage again . installed htc sync and uninstalled it leaving the drivers installed i dont know what is happening now , what should it display when it is in RUU MODE?
cliffordmoyo said:
hie when i type fastboot oem rebootRUU it reboots and boots into the system where it shows decrypt storage again . installed htc sync and uninstalled it leaving the drivers installed i dont know what is happening now , what should it display when it is in RUU MODE?
Click to expand...
Click to collapse
i dont know how i did it but for a moment is showed me the allow usb debug screen and i could see the device on adb devices command prompt screen then i tried to install the RUU.exe firmware but it failed and rebooted now its no longer detected on adb :crying:
cliffordmoyo said:
i dont know how i did it but for a moment is showed me the allow usb debug screen and i could see the device on adb devices command prompt screen then i tried to install the RUU.exe firmware but it failed and rebooted now its no longer detected on adb :crying:
Click to expand...
Click to collapse
The RUU.exe from your first post?
That will not work for you. That RUU is for AT&T devices. The only way you would be able to flash that would be if you were S-Off and changed you CID to 11111111 (or AT&T's CID)
Take the RUU.zip (6.12.401.4 ~ the 401 being the important part, that is the identifier for your model) and rename the .zip to 0P6BIMG.zip (that's a zero, not the letter). The best way to do rename would be to place it onto your extSD so you can see the .zip extension (it is sometimes hidden on your PC) and use a file explorer so you don't accidentally rename it to 0P6BIMG.zip.zip
Boot to bootloader after this is renamed and on extSD (formatted to FAT32), and you should be prompted to flash it by pressing vol up. When the flash is finished, you'll be prompted to press power to reboot, and you are done.
Hope this helps
xunholyx said:
The RUU.exe from your first post?
That will not work for you. That RUU is for AT&T devices. The only way you would be able to flash that would be if you were S-Off and changed you CID to 11111111 (or AT&T's CID)
Take the RUU.zip (6.12.401.4 ~ the 401 being the important part, that is the identifier for your model) and rename the .zip to 0P6BIMG.zip (that's a zero, not the letter). The best way to do rename would be to place it onto your extSD so you can see the .zip extension (it is sometimes hidden on your PC) and use a file explorer so you don't accidentally rename it to 0P6BIMG.zip.zip
Boot to bootloader after this is renamed and on extSD (formatted to FAT32), and you should be prompted to flash it by pressing vol up. When the flash is finished, you'll be prompted to press power to reboot, and you are done.
Hope this helps
Click to expand...
Click to collapse
thank you for the reply . so i did download this firmware with the 6 .12.401.4 in its original name hope it is the correct one please confirm
(0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip)
and using extsd card is the best way to flash my device than using fastboot command prompt with RUU zip file stil in pc ? hope i am getting the steps right
cliffordmoyo said:
thank you for the reply . so i did download this firmware with the 6 .12.401.4 in its original name hope it is the correct one please confirm
(0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip)
and using extsd card is the best way to flash my device than using fastboot command prompt with RUU zip file stil in pc ? hope i am getting the steps right
Click to expand...
Click to collapse
Yeah, you can also flash it in fastboot from PC. You'll probably get an "Error 90". That's the hboot pre-update and nothing to worry about. When you get it don't disconnect, just enter the flash command (fastboot flash zip "name of firmware".zip) a second time to reflash it.
xunholyx said:
Yeah, you can also flash it in fastboot from PC. You'll probably get an "Error 90". That's the hboot pre-update and nothing to worry about. When you get it don't disconnect, just enter the flash command (fastboot flash zip "name of firmware".zip) a second time to reflash it.
Click to expand...
Click to collapse
sadly i guess i have got a bigger problem than i thought , so i tried with pc using these commands fastboot oem rebootRUU and the devices reboots straight into normal mode , and i did also the extsd tutorial you gave me and the device checks the file and prompts me if i want to continue bt after pressing the vol up button the device reboots again straight into normal mode where i am having the decrypt storage issue .if only i had that usb debugging screen prompt again i guess i would have had better odds since before it failed it actually went into RUU flash mode showing only the htc logo with black background
thank you for the quick response by the way
cliffordmoyo said:
sadly i guess i have got a bigger problem than i thought , so i tried with pc using these commands fastboot oem rebootRUU and the devices reboots straight into normal mode , and i did also the extsd tutorial you gave me and the device checks the file and prompts me if i want to continue bt after pressing the vol up button the device reboots again straight into normal mode where i am having the decrypt storage issue .if only i had that usb debugging screen prompt again i guess i would have had better odds since before it failed it actually went into RUU flash mode showing only the htc logo with black background
thank you for the quick response by the way
Click to expand...
Click to collapse
You can turn on usb debugging in settings > developer options, but it shouldn't be needed for fastboot commands.
Try flashing this firmware.zip first, then run the RUU.zip again.
xunholyx said:
You can turn on usb debugging in settings > developer options, but it shouldn't be needed for fastboot commands.
Try flashing this firmware.zip first, then run the RUU.zip again.
Click to expand...
Click to collapse
tried that last firmware zip but just want to confirm if i did the correct procedure ......
i downloaded this file you linked me : M8_6.12.401.4_WWE_TWRP2870.zip renamed it to 0P6BIMG.zip , copied it to my sdcard and and rebooted into bootloader . i could see the checking progress bar but then it just doesnt give me the prompt screen for vol up to continue or vol down to cancel , its just saying press power to reboot.
then tried fastboot oem rebootRUU but the fone is just stubborn and reboots into normal mode again not in RUU mode so i cant flash the zip firmware with fastboot . Another thing i noticed is when i finish unlocking bootloader and gets the success message with continue to unlock bootloader screen and then phone reboots into recovery (stock recovery) there is a chain of errors like "cannot mount data , cannot mount emmc" too but when i repeat the bootloader unlock process again this time with an sdcard in device i get "no cw files in sdcard" message when it reboots into recovery but still the bootloader wont be unlocked despite of repeating the process several times. the phone is still brand new never opened and i think this is somehow software related for i was beginning to think that its hardware issue but an app cause this "device decrypt storage" after the phone rebooted
Any idea where i can get htc mtp device drivers as i have reinstalled my operating system and installed htc syn too but those are the only ones failling to install now am on 32bit windows os , the ones i have downloaded are not installing maybe if those install i might recieve an "allow usb debugging " screen as i did earlier on before the screen didnt want to show up again
do you have any idea what might cause device to reboot into os/normal mode when executing the fastboot reboot-bootloader same as fastboot oem rebootRUU the device quickly reboots and enter into normal mode and does not hold those command . also if have downloaded almost 17 unlockcode.bin files from htc dev i kept on requesting after the bootloader wont get unlocked , it shows unlockcode flashed successfully in command prompt but when device reboots the bootloader is still locked . i still love my htc m8 but it seems i am the only one in this enter forum who has this problem since other are successfully getting their devices fixed :crying::crying:
Hey,
my problem is that, after a reboot, my phone went into a bootloop.
I tried to enter the Recovery or the Download mode but it does not working.
After an automatic restart there is the bootloop again.
I can enter the Bootloader.
Official Software status
Unlocked
S-OFF
an interesting thing is that when i try to read my cid or mid with
fastboot getvar cid/mid
there is nothing to read out. It's empty.
Code:
c:\android>fastboot getvar cid
cid:
finished. total time: 0.036s
c:\android>fastboot getvar mid
mid:
finished. total time: 0.003s
domme0852 said:
Hey,
my problem is that, after a reboot, my phone went into a bootloop.
I tried to enter the Recovery or the Download mode but it does not working.
After an automatic restart there is the bootloop again.
I can enter the Bootloader.
Official Software status
Unlocked
S-OFF
an interesting thing is that when i try to read my cid or mid with
fastboot getvar cid/mid
there is nothing to read out. It's empty.
Click to expand...
Click to collapse
What is the output with fastboot getvar all?
Code:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61b000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:xxxxxxxxxxxx
all:
finished. total time: 0.380s
Since you have access to the bootloader did you try entering recovery from the bootloader itself?...or try using: fastboot reboot recovery, or adb reboot recovery?
I basically have the same problem as you... except my phone is still bootloader locked and s-on. Have you tried putting a 2PS6IMG.zip file (ruu) on the root of a FAT32 formatted microSD card and see if you can access download mode that way?
chrisz5z said:
Since you have access to the bootloader did you try entering recovery from the bootloader itself?...or try using: fastboot reboot recovery, or adb reboot recovery?
Click to expand...
Click to collapse
I tried both. Via bootloader and fastboot command but nothing worked.
adb reboot recovery also doesn't work. There is no devices in adb mode.
Code:
c:\android>adb devices
List of devices attached
c:\android>
mang0 said:
I basically have the same problem as you... except my phone is still bootloader locked and s-on. Have you tried putting a 2PS6IMG.zip file (ruu) on the root of a FAT32 formatted microSD card and see if you can access download mode that way?
Click to expand...
Click to collapse
The download mode is, as I see it, completely bricked. There is no way to enter it.
Without an SDcard it should at least boot into it. But the device is going back to the bootloop.
To answer your question... no I don't try it
domme0852 said:
I tried both. Via bootloader and fastboot command but nothing worked.
adb reboot recovery also doesn't work. There is no devices in adb mode.
Code:
c:\android>adb devices
List of devices attached
c:\android>
The download mode is, as I see it, completely bricked. There is no way to enter it.
Without an SDcard it should at least boot into it. But the device is going back to the bootloop.
To answer your question... no I don't try it
Click to expand...
Click to collapse
You wouldn't be able to see much information via fastboot getvar all unless you were in download mode, so it's not really that strange.
Sometimes you can "trick" (I don't know if that's the correct word) the system into entering download mode from the above method.
At least, from this post and this post, that is what I gathered.
mang0 said:
Sometimes you can "trick" (I don't know if that's the correct word) the system into entering download mode from the above method.
At least, from this post and this post, that is what I gathered.
Click to expand...
Click to collapse
I tried the Method but the Phone still don't want to boot into download mode. It starts the bootloop like before.
I also tried to do an Update via the RUU.exe but this doesn't work too. The program stops with the error low battery although the phone was the whole night on the charger in bootloader. (Don't know if it does not charge right in this state)
Help I have the same problem
Its a simple fix. Take your phone back to carrier or HTC
My HTC One M9 decided to freeze and crash suddenly. I woke up one morning, the phone's alarm didn't go off, and LineageOS did not respond to touch input.
Upon rebooting I'm stuck in a boot loop (HTC boot logo).
I've tried going into recovery and wipe cache, system, data, and every other partition and reflash. No avail, though I can still boot into TWRP recovery:
Code:
Failed to mount /cache (invalid argument)
Failed to mount /data (no such device).
Failed to wipe dalvik.
Unable to mount storage.
I tried resetting to factory by using P98IMG.zip.
It says boot into download mode failed.
I suspect a corrupt internal memory (NAND fried).
Help? How can I get my phone working again?
Just out of curiosity, did you always update your twrp and supersu?.
Beamed in by telepathy.
shivadow said:
Just out of curiosity, did you always update your twrp and supersu?.
Beamed in by telepathy.
Click to expand...
Click to collapse
No, I used TWRP 2.8.7.0 for himaul and I didn't ever update supersu.
Hello, I am in a same situation. Any updates or solutions?
I cant even get CID and MID
\platform-tools>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA5B5YJ02594
all:
Finished. Total time: 0.152s
fastboot getvar cid
cid:
Finished. Total time: 0.011s
fastboot getvar mid
mid:
Finished. Total time: 0.013s
Click to expand...
Click to collapse
The internal NAND chip was fried. The device is irreversibly broken, it needed a new motherboard and at that point you're better off buying a new phone. It's unfixable.
0x80h said:
The internal NAND chip was fried. The device is irreversibly broken, it needed a new motherboard and at that point you're better off buying a new phone. It's unfixable.
Click to expand...
Click to collapse
How do you figure that? Just based on cid and mid?
I'm in a similar situation, trying to troubleshoot a phone that has never been flashed or unlocked. It can now only get to bootloader, no recovery or download mode. Its cid and mid also return blank in fastboot. Does that mean it is fried?
Any help is appreciated
Rakmo said:
How do you figure that? Just based on cid and mid?
I'm in a similar situation, trying to troubleshoot a phone that has never been flashed or unlocked. It can now only get to bootloader, no recovery or download mode. Its cid and mid also return blank in fastboot. Does that mean it is fried?
Any help is appreciated
Click to expand...
Click to collapse
Try to access download mode or recovery from both button combo and via bootloader. The information returned from fastboot is garbage because you need to do the getvar command while the phone is in download mode, not bootloader.
Try holding all 3 buttons and variations of 2 button combos. Sim in, sim out, sd in, sd out. You need download mode regardless. No download mode means dead as because that is the only way to flash any firmware. The os version will be displayed in download mode at the very top, if you get that far.
shivadow said:
Try to access download mode or recovery from both button combo and via bootloader. The information returned from fastboot is garbage because you need to do the getvar command while the phone is in download mode, not bootloader.
Try holding all 3 buttons and variations of 2 button combos. Sim in, sim out, sd in, sd out. You need download mode regardless. No download mode means dead as because that is the only way to flash any firmware. The os version will be displayed in download mode at the very top, if you get that far.
Click to expand...
Click to collapse
Thanks a lot for the tips Okay, here's what happens:
If I hold Volume up and down while starting, I get to the bootloader where I can choose reboot, reboot to bootloader, download mode, recovery mode, and power down.
If I try to just boot (or hold volume up while), it show HTC on white background for ~20 seconds, before rebooting and looping
If I hold volume down while starting, or choose download mode from the bootloader, I get white HTC on black background for ~1 second, before rebooting and looping.
If I choose recovery mode from the bootloader, I get "Failed to boot to recovery mode", and something about the build being for development purposes only (the phone has never been flashed or anything).
It is a family member's phone, so I cannot currently test with SD or SIM, I'm doing everything with those empty. Though, when the problem first appeared, both were present. Should I try to test with those?
Sounds like it's fked. No download mode means no fix.
Hi all, here's a problem I hope you guys can help me with.
My M9 powered down on friday and I have not been able to get it to boot back up since. When I attempt to power it on the HTC logo appears, phone vibrates then it turns back off, this then continues to loop.
If I hold vol up, vol down and power I'm presented with the screen reading the following:
*** Software status: Official ***
*** LOCKED ***
*** S-ON ***
-
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
POWER DOWN
'Reboot' restarts the loop.
'Reboot to bootloader' returns me to the same screen.
'Download mode' takes me to DL mode.
'Recovery mode' returns the following: "Failed to boot to recovery mode. Press vol up or down to back to menu"
Selecting power down is the only way to stop the loop and power off the phone.
The phone is stock, S-ON, Bootloader locked, no CFW or Custom Recovery, no OEM unlocking or Developer options enabled.
Do I have any chance of recovering this? Thanks in advance.
If you can boot in download mode(you said you can) do "fastboot getvar all" and post the result here(remove imei,sn).
lucyr03 said:
If you can boot in download mode(you said you can) do "fastboot getvar all" and post the result here(remove imei,sn).
Click to expand...
Click to collapse
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: ###############
(bootloader) version-main: 3.35.161.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_96.00.51201G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: VODAP001
all:
finished. total time: 0.004s
Here is the right RUU for your device: https://androidfilehost.com/?fid=24438995911969361
I recommend the sdcard method: just rename the zip to 0PJAIMG.zip and put in the root of your fat32 formatted sdcard.
Then boot in download mode and follow the on-screen instructions.
Note: This procedure will wipe all of your internal storage.
lucyr03 said:
Here is the right RUU for your device: https://androidfilehost.com/?fid=24438995911969361
I recommend the sdcard method: just rename the zip to 0PJAIMG.zip and put in the root of your fat32 formatted sdcard.
Then boot in download mode and follow the on-screen instructions.
Note: This procedure will wipe all of your internal storage.
Click to expand...
Click to collapse
Thanks!
I'll give this a shot when I get home from work and report back.
lucyr03 said:
Here is the right RUU for your device: https://androidfilehost.com/?fid=24438995911969361
I recommend the sdcard method: just rename the zip to 0PJAIMG.zip and put in the root of your fat32 formatted sdcard.
Then boot in download mode and follow the on-screen instructions.
Note: This procedure will wipe all of your internal storage.
Click to expand...
Click to collapse
Update: I've given this a try with no success.
I renamed the file and placed it on the root of my SD card then booted to DL mode. Then I pressed VolUp to start flash. 'Start ui_updating' appears at the top for about 5 seconds and then the phone reboots and begins looping again.
316894 said:
Update: I've given this a try with no success.
I renamed the file and placed it on the root of my SD card then booted to DL mode. Then I pressed VolUp to start flash. 'Start ui_updating' appears at the top for about 5 seconds and then the phone reboots and begins looping again.
Click to expand...
Click to collapse
That's strange, maybe your phone have an hardware problem.
Try to flash from the pc.
You need adb, htc drivers and htc_fastboot.exe
Boot your phone in download and connect to the pc.
"htc_fastboot flash zip RUU.zip" - do the command again when it ask(phone reboots itself back in download mode).
Note: Replace RUU.zip with your path to ruu.
After the process is completed do "fastboot reboot"
lucyr03 said:
That's strange, maybe your phone have an hardware problem.
Try to flash from the pc.
You need adb, htc drivers and htc_fastboot.exe
Boot your phone in download and connect to the pc.
"htc_fastboot flash zip RUU.zip" - do the command again when it ask(phone reboots itself back in download mode).
Note: Replace RUU.zip with your path to ruu.
After the process is completed do "fastboot reboot"
Click to expand...
Click to collapse
Tried this:
Code:
C:\>htc_fastboot flash zip RUU.zip
sending 'zip'... (133005 KB) OKAY
sending time = 7.398 secs
writing 'zip'... (bootloader) HOSD CL#671447
FAIL9 RU_SECURITY_FAIL zip from usb command in download mode
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
Execution time is 9(s)
I would question which ruu you're using.. I dont think you have the correct one.
shivadow said:
I would question which ruu you're using.. I dont think you have the correct one.
Click to expand...
Click to collapse
I'm using the following RUU as suggested by lucyr03, would you suggest another?
"0PJAIMG_HIMA_UHL_M60_SENSE70_MR_Vodafone_UK_3.35.161.12_Radio_01.01_U11440792_96.00.51201G_F_release_464298_signed.zip"
That's the correct firmware.. Seems like your phone is bricked.