[Q] Need help with unbrick. - Nexus 7 (2013) Q&A

Hello, everyone!
First of all, I want to thank all the xda comminity for help, I recieved, but today I have to ask for help again.
I have read all the topics I was able to find and followed some advices, but they didn't help...So back to start..
I have Asus Nexus 7 2013 16Gb Wi-Fi. It had latest Android 4.4.2 from OTA update.
Few day ago I had to reboot it, because the screen stopped responding for touches (the hardware buttons still worked). Such thing happened before, so I didn't panic. I pushed the Power button for a long time and the device was switched off. Then I tried to boot it again and... it hang on Google logo.
I tried to reboot it few more times, but I got the same result. Here is the list of my following steps and results:
I booted to fastboot and tried to boot recovery - fail. still have only google logo.
booted to fastboot and unlocked it by
Code:
fastboot oem unlock
. - fail. still have only google logo.
downloaded the latest factory image and flashed if by
Code:
flash-all
. Everything flashed successfully, but..fail. still have only google logo and open locker on a screen.
downloaded custom recovery and flashed. Tried to boot to recovery again - fail. still have only google logo with locker.
tried to flash cyanogenmod. it flashed but... fail again. only google logo with locker.
erased all the partitions through fastboot and flashed previous factory image. fail - still have google logo.
Please, if anyone can suggest something to resurrect my Nexus, tell me, what should I try next.
Or it is a brick? =(
Is there any chance to get any log from bootloader?
I don't know, if this could help, but here is info from fastboot:
fastboot getvar all
(bootloader) version-bootloader: FLO-04.02
(bootloader) version-baseband: none
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: flo 16G
(bootloader) serialno: 05848bba
(bootloader) product: flo
(bootloader) secure_boot: enabled
(bootloader) lock_state: unlocked
(bootloader) project: flo
(bootloader) off-mode-charge: yes
(bootloader) uart-on: no
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0x0000000000aee000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000034800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000023000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x000000031b7fbe00
all:
Click to expand...
Click to collapse

Demian87 said:
Hello, everyone!
First of all, I want to thank all the xda comminity for help, I recieved, but today I have to ask for help again.
I have read all the topics I was able to find and followed some advices, but they didn't help...So back to start..
I have Asus Nexus 7 2013 16Gb Wi-Fi. It had latest Android 4.4.2 from OTA update.
Few day ago I had to reboot it, because the screen stopped responding for touches (the hardware buttons still worked). Such thing happened before, so I didn't panic. I pushed the Power button for a long time and the device was switched off. Then I tried to boot it again and... it hang on Google logo.
I tried to reboot it few more times, but I got the same result. Here is the list of my following steps and results:
I booted to fastboot and tried to boot recovery - fail. still have only google logo.
booted to fastboot and unlocked it by
Code:
fastboot oem unlock
. - fail. still have only google logo.
downloaded the latest factory image and flashed if by
Code:
flash-all
. Everything flashed successfully, but..fail. still have only google logo and open locker on a screen.
downloaded custom recovery and flashed. Tried to boot to recovery again - fail. still have only google logo with locker.
tried to flash cyanogenmod. it flashed but... fail again. only google logo with locker.
erased all the partitions through fastboot and flashed previous factory image. fail - still have google logo.
Please, if anyone can suggest something to resurrect my Nexus, tell me, what should I try next.
Or it is a brick? =(
Is there any chance to get any log from bootloader?
I don't know, if this could help, but here is info from fastboot:
Click to expand...
Click to collapse
I posted somewhere In Q&A on how to unbrick the device so please go ahead and take a look
---------- Post added at 05:52 PM ---------- Previous post was at 05:52 PM ----------
I'm a bit lazy to retype out the instructions all over again

Bobbi lim said:
I posted somewhere In Q&A on how to unbrick the device so please go ahead and take a look
---------- Post added at 05:52 PM ---------- Previous post was at 05:52 PM ----------
I'm a bit lazy to retype out the instructions all over again
Click to expand...
Click to collapse
Thank you for a suggestion to search your posts.
I found only the same post in this thread: http://forum.xda-developers.com/showthread.php?t=2624688
and some flash-all decision here: http://forum.xda-developers.com/showthread.php?p=49347871#post49347871
As you can see, I have already tried to flash-all few times and this piece of advice was useless in my case, unfortunatelly.

Related

Stuck at HTC logo, can't recover

Hey guys, I'm having quite an issue here trying to help a friend with her DesireZ, it's stuck at the HTC logo and won't start up...
Here's a list of things I've tried:
- Volume Down + Power > RECOVERY > will vibrate 7 times and then it's stuck.
- FASTBOOT - Flash new RUU - says "Rebooting to bootloader" on the PC but nothing ever happens.
- renamed rom.zip from the RUU to PC10IMG.ZIP, placed it on SDCARD, Volume Down + Power - it will see the file but... when the update process starts it gets stuck at the very first step "Bootloader - updating" and it freezes there.
The owner said she never tried anything like rooting it or changing the ROM or anything like that... what could be wrong??
THanks!
so she actually got a stock phone.
two things you could try:
1. if the phone is stock you can´t enter recovery through bootloader (power & volume -) - you have to use power & volume + (here you could try to wipe cache or do a factory reset)
2. you can force the phone to boot using fastboot and typing: fastboot oem boot (at least you will get an output what goes wrong while booting)
Thanks for the reply. Volume+ and power doesn't do anything it seems... if I do Volume- and Power I get to the bootloader (FASTBOOT, RECOVERY, FACTORY RESET, SIMLOCK, etc...) ... I tried FACTORY RESET but it freezes there. How can I wipe the cache?
This is what I get when i do fastboot oem boot
C:\Android>fastboot oem boot
...
(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 0x25202
(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__032
(bootloader) setting->cid::HTC__032
(bootloader) serial number:
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =504
(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=HTC__032 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=HTC-EastEurope androidboot.mid=PC1011000 android
(bootloader) boot.keycaps=qwerty androidboot.mode=normal androidboot.seri
(bootloader) alno=SH19ERT00226 androidboot.bootloader=0.85.0013 zygote_on
(bootloader) eshot=off 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:19715 msec
FAILED (status read failed (Too many links))
finished. total time: 8.296s
C:\Android>
Delete the serial number in your posting.
try to enter recovery, you should see something like a red triangle then push volume + & power and you should see a menu... here you should be able to wipe cache
there is also a fastboot way to do this ...fastboot erase cache is the command for wiping, but it only works with eng hboot.
Is the ruu you used the same as your stock rom? other people fixed it with using the right PC10IMG.zip
or you can hope for warranty
Sent from my HTC Vision using XDA App
I have a similar problem, I think. I'll try to be as informative as possible, but I'm very new at troubleshooting my device.
As with the other phone, mine will continue to get stuck at the HTC logo, then reboot.
I was browsing market, when it froze. I just left it frozen, and waited for it to restart. Once it restarted, it came up with the phone with the triangle icon. Not knowing what it meant, I took out the battery and reinserted it.
On reboot, it began its boot cycle.
I get no response holding volume up + power, nor volume down + power.
I tried reinserting battery, removing memory card and removing sim card - restarting after each step, but still nothing.
Only way to break the boot cycle is to remove battery, but when rebooted, it starts over again.
Please help?
first of all you need to somehow enter bootloader (volume- & power) try it a few times after you pulled the battery...
is your phone rooted?
No, sorry, I forgot to say that. Not rooted. Too worried about viruses and stuff.
*EDIT*
Yay - got into the boot section. I hit recovery and I get the phone with the red warning triangle. Does that mean that it's not working, or that it's working on recovering?
Breagha said:
No, sorry, I forgot to say that. Not rooted. Too worried about viruses and stuff.
*EDIT*
Yay - got into the boot section. I hit recovery and I get the phone with the red warning triangle. Does that mean that it's not working, or that it's working on recovering?
Click to expand...
Click to collapse
no it´s normal if you are not rooted. now press power & volume + to enter menu and then first thing to try is wiping cache and see if you can boot into the rom afterwards
I cleared cache and it said it did so successfully.
However when I asked it to restart, it continues the reboot cycle
*Edit*
Yay! It works when I take out my memory card now! You're a life saver!
What do I do now?
Breagha said:
I cleared cache and it said it did so successfully.
However when I asked it to restart, it continues the reboot cycle
Click to expand...
Click to collapse
hm... next thing you could try is a factory reset (should be a option in recovery)
EDIT: if this doesn´t work you could try the PC10IMG.zip as described above - never done this, but i guess you have to use one that is the same as your stock rom...
EDIT 2: you can boot into the rom without sdcard? if so try to format your sdcard (don´t know if there is a option for it in stock recovery) or buy a new one
I got into my OS when I took out the memorycard..
I think it already did a factory reset, 'cause it's asking me to set it up again, only now it's frozen on my language selection screen. Is there a ctrl+alt+delete for androids? >.<
Breagha said:
I got into my OS when I took out the memorycard..
I think it already did a factory reset, 'cause it's asking me to set it up again, only now it's frozen on my language selection screen. Is there a ctrl+alt+delete for androids? >.<
Click to expand...
Click to collapse
no, press the power button for 5 sec maybe the phone shuts down... or pull the battery and to be sure do a factory reset again and then try to boot into the OS again
EDIT: skip the sign in part go to settings and enable usb debugging...
It's working, it's working!! You're my hero! I thought I'd have to send it back in and wait 14 work days to get it back >.<
*huggles* Merry happy awesome Christmas to you
help please
crzvm said:
Hey guys, I'm having quite an issue here trying to help a friend with her DesireZ, it's stuck at the HTC logo and won't start up...
Here's a list of things I've tried:
- Volume Down + Power > RECOVERY > will vibrate 7 times and then it's stuck.
- FASTBOOT - Flash new RUU - says "Rebooting to bootloader" on the PC but nothing ever happens.
- renamed rom.zip from the RUU to PC10IMG.ZIP, placed it on SDCARD, Volume Down + Power - it will see the file but... when the update process starts it gets stuck at the very first step "Bootloader - updating" and it freezes there.
The owner said she never tried anything like rooting it or changing the ROM or anything like that... what could be wrong??
THanks!
Click to expand...
Click to collapse
hey i have the exact same thing, my desire z froze when i received a htc update and got stuck once it restarted and now im stuck in the same boat as above.
its a non rooted UK htc desire z and i have tried:
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
Rom from shippedroms.com but it just freezes saying rebooting to bootloader.
Please help and tell me how to fix it as you have managed to do so.
thanks
---------- Post added at 06:21 PM ---------- Previous post was at 06:05 PM ----------
also the current image rom on my desire z is version 2.42.405.4 and the RUU says to flash it to 2.42.405.2 - would that be a problem???
Same problem
sal2103 said:
hey i have the exact same thing, my desire z froze when i received a htc update and got stuck once it restarted and now im stuck in the same boat as above.
its a non rooted UK htc desire z and i have tried:
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
Rom from shippedroms.com but it just freezes saying rebooting to bootloader.
Please help and tell me how to fix it as you have managed to do so.
thanks
---------- Post added at 06:21 PM ---------- Previous post was at 06:05 PM ----------
also the current image rom on my desire z is version 2.42.405.4 and the RUU says to flash it to 2.42.405.2 - would that be a problem???
Click to expand...
Click to collapse
I have a same problem, but nothing helped me what U wroted in the post... It can not came into recovery just vibrate several times and power off, or when I try to factory reset from bootloader screan it just frozen and only help is pulling the battery off.
So, no recovery, no factory reset, no adb communication... Please help, Thanks!
Sam Problem
So around 2 weeks ago I was using my G2 at a McDonald's and all of a sudden it turned off . . . Long Story short, it's stuck on the HTC screen. I can access Bootloader but doing recovery or factory reset does not do anything. I cannot access adb but I can use fastboot
Vision PVT SHIP S-ON
HBOOT-0.82.0008
MICROP-0425
RADIO-26.13.04.19_M
eMMC-boot
Apr 13 2011, 14:51:54
I also tried flashing several PC10IMG.zip files to no avail as each would end up with a "MAIN VERSION IS OLDER" error. I also made a GoldCard but have no idea how to properly apply it to the situation. Please I have spent 3 days working on this, I need help

Error 255 in TWRP when I try to restore a stock Android 6.0

Hello, I have my M8 with Android 6.0 and software version 6.16.708.1 , I installed TWRP 3.0.2-0 and I downloaded the backup 6.16.708.1_ckpv5 , when I 'm in the step of the restore the backup, jumps to me an error ( attached image error) extractTarFork () enden process with error : 255, and then it does not continue, could someone help me ?. I'm trying to install a previous version of android, but it still with the error :S.
Anybody?
kikirimai said:
..... I'm trying to install a previous version of android, but it still with the error :S.
Click to expand...
Click to collapse
Try with TWRP 2.8.7.0
ckpv5 said:
Try with TWRP 2.8.7.0
Click to expand...
Click to collapse
I tried it but it doesn't work :S what more can I do?
Anybody?????
Try fastboot erase cache after install TWRP ...
Can you post your fastboot getvar all without serial & imei no. ?
Usually this error is related to partition problem .. maybe flashing the firmware, then TWRP follow by fastboot erase cache command can fix this.
ckpv5 said:
Try fastboot erase cache after install TWRP ...
Can you post your fastboot getvar all without serial & imei no. ?
Usually this error is related to partition problem .. maybe flashing the firmware, then TWRP follow by fastboot erase cache command can fix this.
Click to expand...
Click to collapse
I tried to install TWRP and then I did fastboot erase cache, but it doesn't work, I'm posting the fatboot getvar all, what more can I do, if I flash system in CMD it can works?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.708.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: HTC__622
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
kikirimai said:
I tried to install TWRP and then I did fastboot erase cache, but it doesn't work, I'm posting the fatboot getvar all, what more can I do, if I flash system in CMD it can works?
Click to expand...
Click to collapse
First - a stupid question (because it happened before) - you do flash a correct version TWRP meant for HTC M8, right ? The one that you downloaded from https://dl.twrp.me/m8/
If the answer is yes for the above, try flashing firmware.
Get the firmware fw_6.16.708.1.zip and read how-to in my thread here : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Then unlock the bootloader with the unlock_code.bin .. when successfully unlocked, the system will reboot but it will fail .. press both power + volume up button .. when the screen goes black, release both buttons but press and hold volume down button. This will get you to hboot, press power once to get to bootloader/fastboot ... flash TWRP then try to restore backup.
ckpv5 said:
First - a stupid question (because it happened before) - you do flash a correct version TWRP meant for HTC M8, right ? The one that you downloaded from https://dl.twrp.me/m8/
If the answer is yes for the above, try flashing firmware.
Get the firmware fw_6.16.708.1.zip and read how-to in my thread here : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Then unlock the bootloader with the unlock_code.bin .. when successfully unlocked, the system will reboot but it will fail .. press both power + volume up button .. when the screen goes black, release both buttons but press and hold volume down button. This will get you to hboot, press power once to get to bootloader/fastboot ... flash TWRP then try to restore backup.
Click to expand...
Click to collapse
Bro, thanks a lot for you help, I really really appreciate it. I fixed my problem with flashing the nandroid 4.16.708.1 with TWRP 2.8.7.0 but I have the same error that it makes me to flash my cellphone, I dont have signal and the cellphone doesnt show to me the imei, do you think if I put the imei in fastboot can it works? (Sorry for my english) and one more time thank you for all your support .
kikirimai said:
....but I have the same error that it makes me to flash my cellphone, I dont have signal and the cellphone doesnt show to me the imei, do you think if I put the imei in fastboot can it works?
Click to expand...
Click to collapse
So .. that's your actual problem. If it is not hardware problem, you can fix this by flashing firmware as I mentioned above. A few people succeed to fix the same problem by flashing firmware.
ckpv5 said:
So .. that's your actual problem. If it is not hardware problem, you can fix this by flashing firmware as I mentioned above. A few people succeed to fix the same problem by flashing firmware.
Click to expand...
Click to collapse
Perfect, Im going to do all your instructions and then reply, thank you for all
Im sorry, where is the unlock_code.bin? and how can I flash/install that?
Edit: Actually I know that xD sorry.
Man, you are amazing, thanks for your support , I did all your instructions and it works, my cellphone now has signal and all its correct, only one thing, the backup 6.16.708.1_ckpv5 maybe its wrong, I couldn't flash it, but it doesn't matter, I installed nandroid 4.xxx, thank you one more time , greetings!
Maybe the 6.x download is bad..
You can install stock recovery then check OTA to update from current 4.x

Failed to boot download mode

Please help, very, very need firmware 4.16.118.3, or the file itself pulled "hosd.img".
Sorry for my english, but I read better than I write.
As far as I know HTC haven't released the nougat ruu for any M9's.
Beamed in by telepathy.
The 118 SKU doesn't seem to have a Nougat (4.x.xxx.xx) update. Where are you getting that version number?
If your goal is getting Android Nougat: Assuming your phone boots to Android, you may be able to achieve S-OFF via Sunshine, change your SKU and update to Nougat.
If your goal is fixing the download mode issue: a RUU associated with your SKU & OS version should set your phone straight. Could you post the output of the "fastboot getvar all" (be sure to remove the IMEI information)?
Android does not start, only works Bootloader and Recovery. Phone is T-mobile Poland.
First was Android 6.0 Marshmallow version number 3.35.118.12, then on February 25 she appeared update Android 7.0 Nougat version number 4.16.118.3.
After a week when I turn on the phone appeared application errors, then I made Wipe cache, after the phone hung up on the HTC logo and constantly reboot.
When I entered the Bootloader I saw that changed status ***Software status Modified**, phone all the time was ***Locked*** and ***S-ON***
C:\fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(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:************
all:
finished. total time: 0.146s
That getvar all is the response from bootloader. You need to do that in download mode.
To save you the hassle I can tell you that your nand is corrupt and beyond repair. Only HTC can fix it.
"status modified" on a totally stock phone that wont boot means corrupt nand and as dead as a door stop.
Dead nands are becoming more and more popular it seems..
Beamed in by telepathy.
Thank you for your help, phone sent to the service.
shivadow said:
That getvar all is the response from bootloader. You need to do that in download mode.
To save you the hassle I can tell you that your nand is corrupt and beyond repair. Only HTC can fix it.
"status modified" on a totally stock phone that wont boot means corrupt nand and as dead as a door stop.
Dead nands are becoming more and more popular it seems..
Beamed in by telepathy.
Click to expand...
Click to collapse
What about a stock m9 which shows "status modified", does boot to Android, but does not boot to download or recovery modes (black screen with red text - "Failed to boot to download mode ..."). Is this also the sign of a corrupt NAND?
-Tim
LindwurmPL said:
Thank you for your help, phone sent to the service.
Click to expand...
Click to collapse
what problem about your phone? i have same problem too
TimR1 said:
What about a stock m9 which shows "status modified", does boot to Android, but does not boot to download or recovery modes (black screen with red text - "Failed to boot to download mode ..."). Is this also the sign of a corrupt NAND?
-Tim
Click to expand...
Click to collapse
Yes Tim, it can very well be a corrupt nand. The problem you have there is without download mode you can't flash any stock firmware to reset the device to what i call "stock stock". Only htc would be able to repair that.

H3g_001

Hi all i acquired an htc m8 with no O/S on it and am looking for a method to re-install
Ive been going round in circles for days now and am about to send it to a watery grave before i end up there
Heres the getvar info
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.771.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: beyoncesbum
(bootloader) imei: deadbeefratstew
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.010s
I have twrp 3.0.0-0 installed
Bootloader is unlocked.
cariier is UK-3
Any assistance would be greatly appreciated.
Thanks in advance
stephen
hi
follow this thread instruction to restore the stock os read all the the steps and foloow it
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
you can flash any custom rom to have a working device !!!!!!!!
Thanks ill give this a go
i have flashed a custom rom. but i ended up with a deaf phone !, now this may be hardware and not the rom hence the need to stock it so i can confirm it either way.
Ive also had numerous rom/nand failures hence my request for assistance.
Thanks again
Stephen
ps can i use the TWRP 3.0 to install or is that version specific ?
Ok i flashed 4.25.771.6 all went smoothly and i got audio indication of the phones boot up :-} the phone is now installing apps, but i did this previously and it hung overnight attempting to initialize the apps so im waiting hopeflly for a successful installation !.
Stephen
Cant thank you enough, the phone is now alive and kicking
I cant believe how simple and quick that was as ive spent quite a few frustrating days attempting to get it operational, and thought i was on a pointless mission, ive waded though an awful lot of os/roms/nands all with little success.
thank you
very much
stephen
Marshmallow
Ive just attempted an update to 6.13.771.4 mm from the same link, but the O/S hangs on "apps initialization"
Also i did download the update via OTA but on reboot into TWRP i dont see an option to flash the rom
Do i need to update through progressive versions ?
Thanks
Stephen
Essef1959 said:
Ive just attempted an update to 6.17mm from the same link, but the O/S hangs on "apps initialization"
Also i did download the update via OTA but on reboot into TWRP i dont see an option to flash the rom
Do i need to update through progressive versions ?
Thanks
Stephen
Click to expand...
Click to collapse
Read all the steps again and use the proper files as mentioned in the guide-thread
You can't flash stock OTA with twrp
Do a factory reset before and after doing all the steps
Sent from my HTC M8 using XDA Labs
Heres a list of my progress so far.
1) Flashed version 4.25.771.6 using TWRP 3.0.0000 and all works fine following the guide you linked.
2) Once the above is flashed, im then informed it will auto update to 6.13.771.4 and proceeds to download the required files via OTA
once downloaded the system attempts to update, which results in a re-boot into TWRP recovery and hence it fails.
3) Flashed version 6.13.771.4 using TWRP 3.0.0000 and it hangs at "APP Initialization" following the guide you linked.
Am i right in thinking that if i remove TWRP and return to the stock boot, that the OTA update would install ?.
Thanks for your advice so far
Stephen
Ps my works Pc uses a second user account Essef1959/Piperetti are the same user
@ahmed.ismael said read all the steps but it seems you didn't as you missed step 11, install stock revovery for OTA to proceed with installation.
ckpv5 said:
@ahmed.ismael said read all the steps but it seems you didn't as you missed step 11, install stock revovery for OTA to proceed with installation.
Click to expand...
Click to collapse
4th line of my last post indicated i had already worked that one out, and yours was the answer i was looking for thanks ,although i used the term boot and not recovery
stephen
ok i installed stock recovery img, and OTA downloaded the latest 6.13.771.4
the phone set this up then rebooted into recovery mode and installed, but i still have the issue of the system hanging on "starting apps" !
Stephen ?
piperetti said:
ok i installed stock recovery img, and OTA downloaded the latest 6.13.771.4
the phone set this up then rebooted into recovery mode and installed, but i still have the issue of the system hanging on "starting apps" !
Stephen ?
Click to expand...
Click to collapse
What about flashing a custom rom ?
also i would suggest you to flash the firmware but flash a custom rom first to see how it will goes
Sent from my HTC M8 using XDA Labs
I Have flashed a custom rom but this did,nt function with any audio related process.
I,ll have another attempt at one, but dont understand why it fails with a pucka rom ?.
Thanks
Stephen
Ok i flashed leedroids latest offering with TWRP 3, installed fine but once again it hangs on "App Initialization" i left it running for more than an hour.
So obviously there is an issue somewhere ?.
Stephen
Essef1959 said:
Ok i flashed leedroids latest offering with TWRP 3, installed fine but once again it hangs on "App Initialization" i left it running for more than an hour.
So obviously there is an issue somewhere ?.
Stephen
Click to expand...
Click to collapse
Try to restore the backup again but this time don't install the stock recovery but install the firmware from post #5 in the same thread ( it may and may not help in booting the device )
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Try to restore the backup again but this time don't install the stock recovery but install the firmware from post #5 in the same thread ( it may and may not help in booting the device )
Click to expand...
Click to collapse
Same problem sticks on "starting apps" with stock nand/leedroid rom.
Stephen
Essef1959 said:
Same problem sticks on "starting apps" with stock nand/leedroid rom.
Stephen
Click to expand...
Click to collapse
Try with aosp rom then
In general that's not a good sign
Sent from my HTC M8 using XDA Labs
Weird as it works flawlessly with version 4.25.771.6
:-{
stephen
---------- Post added at 12:16 PM ---------- Previous post was at 12:16 PM ----------
Weird as it works flawlessly with version 4.25.771.6
:-{
stephen
Essef1959 said:
Weird as it works flawlessly with version 4.25.771.6
:-{
stephen
---------- Post added at 12:16 PM ---------- Previous post was at 12:16 PM ----------
Weird as it works flawlessly with version 4.25.771.6
:-{
stephen
Click to expand...
Click to collapse
Yeah i have seen it before,someone have the same case as yours
Marshmallow RUU won't boot but any older RUU will boot just fine
So you have a very limited option either stick with a lollipop rom or an aosp rom ( i think nougat roms will boot just fine )
Sorry there is no much you can do
Sent from my HTC M8 using XDA Labs
You,ve been very help full and saved me an awful lot of time which i would have wasted looking for the right s/w, so again thanks for your advice.
I am enjoying the phone at the moment but will attempt a nougat install in the future, so dont get to comfy yet lol.
Stephen

HTC One M8s Bricked - No Recovery Boot. Always Boot into bootloader

Hello.
i searched this forum and not found the answer. thats why i started new thread. appologize if duplicate Q/A exist.
Flashing Recovery and boot_signed.img and try to boot into recovery. no luck. always get into bootloader. tried to flash other partitions, but getting error from remote (device). tried stock rom with RUU. but after rebooting device RUU does not detect. and exit with code 171.
unable to flash any partition with fastboot flash patition name partitionfile.img
but can only flash boot and recovery.
tried ziped rom with sd card. but it stuck on device halted while parsing large image. and prompt to reboot
got phone in bricked mode.
Bootloader UNLOCKED. tried to relock with fastboot oem lock but not lock. status is UNLOCKED
***SYSTEM STATUS IS MODIFIED***
This is can be only change after moving to stock.
LOG FILE of getvar
Code:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.13.111.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT55DYS00****
(bootloader) imei: 358031060861***
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: T-MOB101
(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: e31b162e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
Please advise.
sylentears said:
Hello.
i searched this forum and not found the answer. thats why i started new thread. appologize if duplicate Q/A exist.
Flashing Recovery and boot_signed.img and try to boot into recovery. no luck. always get into bootloader. tried to flash other partitions, but getting error from remote (device). tried stock rom with RUU. but after rebooting device RUU does not detect. and exit with code 171.
unable to flash any partition with fastboot flash patition name partitionfile.img
but can only flash boot and recovery.
tried ziped rom with sd card. but it stuck on device halted while parsing large image. and prompt to reboot
got phone in bricked mode.
Bootloader UNLOCKED. tried to relock with fastboot oem lock but not lock. status is UNLOCKED
***SYSTEM STATUS IS MODIFIED***
This is can be only change after moving to stock.
LOG FILE of getvar
Please advise.
Click to expand...
Click to collapse
Have you tried booting TWRP recovery without actually installing it?
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
fastboot boot recovery NAME OF RECOVERY.img
For example: fastboot boot recovery twrp3.0.1.1.img
---------- Post added at 07:53 PM ---------- Previous post was at 07:30 PM ----------
Since your device reports bootloader to be unlocked, you should be able to :
1. Boot your device to bootloader
2. Connect to PC ( i presume you have drivers installed )
3. Run: fastboot devices
4. Upon successful device discovery try to boot twrp as written above
5. If the phone boots to twrp, do a full wipe in twrp
6. Try sideloading cyanogen rom and then installing it.
---------- Post added at 07:54 PM ---------- Previous post was at 07:53 PM ----------
If that works, either leave the phone as it is, or try ruu to go back to stock
twrprecovery.img. but after that device stuck and go unresponsive. And does not accept any command.
sylentears said:
twrprecovery.img. but after that device stuck and go unresponsive. And does not accept any command.
Click to expand...
Click to collapse
Sorry I didn't understand your post. What did you do and what happened?
when send this command with fastboot boot twrp3.x.x.x.img device accept command and after successfull message on fastboot command. device does not respond even i keep for some time. and after draining battery it power off itself. and when i put this on charge after little charging it goes to bootloader again. i hope so. now cleared.
sylentears said:
when send this command with fastboot boot twrp3.x.x.x.img device accept command and after successfull message on fastboot command. device does not respond even i keep for some time. and after draining battery it power off itself. and when i put this on charge after little charging it goes to bootloader again. i hope so. now cleared.
Click to expand...
Click to collapse
Have you tried both versions of twrp?
Would you please specify the versions???
sylentears said:
Would you please specify the versions???
Click to expand...
Click to collapse
https://ruu.lalleman.net/HTC_M8S(QL_UL)/Recovery/
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
You will find some stock recoveries there as well.
already been tried with. but device not reboot ro recovery after this command
fastboot boot twrpver.img
Click to expand...
Click to collapse
and also
fastboot boot stockrecovery.img
Click to expand...
Click to collapse
I m able to flash recovery and boot into recovery image command. but does not effect on device.
It might be a eMMC chip issue???
Image CRC check result
rpm :0xAxxxxxxAB
sbl1: :0x9xxxxxxC4
sbl2 :0x0
sbl3 :0x0
tz :0xCxxxxxxxDC
radio :0x3xxxxxxx83
hboot :0x6DxxxxxxGA
boot :0x0
recovery :0x0
system :0x2xxxxxxxx8C
0x0 stated partition images are reported corrupted or damaged. i think it can fixed only by Qualcomm USB mode to extract rom image
sylentears said:
Image CRC check result
rpm :0xAxxxxxxAB
sbl1: :0x9xxxxxxC4
sbl2 :0x0
sbl3 :0x0
tz :0xCxxxxxxxDC
radio :0x3xxxxxxx83
hboot :0x6DxxxxxxGA
boot :0x0
recovery :0x0
system :0x2xxxxxxxx8C
0x0 stated partition images are reported corrupted or damaged. i think it can fixed only by Qualcomm USB mode to extract rom image
Click to expand...
Click to collapse
Have you ever done that Qualcomm usb mode? I have one perfectly working HTC m8s, so if you could shed some light on the procedure that would be great. Googling didn't give me much insight in relation to it.
If you have Easy jtag pro box then it can fix. please see this video.
Not sure if this helps but I was unable to get twrp 3.x.x workING.
I'm on 2.8.7
Can you Boot into stock. and able to flash ruu image with PC Application or able to flash .zip image with SD Card.
post the status of work and let us advise you further.
Note: TWRP will only work if your bootloader is unlocked. and still will not work if the partition structure is damaged. check CRC check on fastboot Screen.
Sorry I thought this usb qualcomm mode can be used with pc and phone only
Ok
so you are in dead boot mode. and only cant connect in Qualcomm USB mode 9008
watch this tutorial carefully and try to unbrick your phone and back to bootloader mode and reflash stock image or stock backup.
Hit Thanks or like if it does help you.
Try booting to TWRP again using HTC_Fastboot. Fastboot will not work with a HTC, they have their own version.
sylentears said:
Ok
so you are in dead boot mode. and only cant connect in Qualcomm USB mode 9008
watch this tutorial carefully and try to unbrick your phone and back to bootloader mode and reflash stock image or stock backup.
Hit Thanks or like if it does help you.
Click to expand...
Click to collapse
how to use this method on htc one m8? as i am facing ,
rpm :0xAxxxxxxAB
sbl1: :0x9xxxxxxC4
sbl2 :0x0
sbl3 :0x0
tz :0xCxxxxxxxDC
radio :0x3xxxxxxx83
hboot :0x6DxxxxxxGA
this sbl2 and sbl3 values as 0x0 any leads?

Categories

Resources