Related
I have a Verizon ADR6350VW HTC Incredible 2. I decided to 'upgrade' it to a new ROM.
I unlocked the boot loader and installed ClockwrkMod Recovery v5.0.2.0
*** UNLOCKED ***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.0312
eMMC-boot
Jul 18 2011,12:39:36
I tried putting an incredible 2 ROM (Viper) and since then it won't fully boot, it gets stuck forever on the green HTC logo on the white background.
I can get to the bootloader, and tried reflashing the same or other downloaded ROMs (all meant for the HTC incredible 2). Without much luck.
The original flashing process was not interrupted. I did a lot of googling and reading (but missed the S-ON/S-OFF part originally), and have tried many different ways to get out of this without luck.
3rd party ROM will flash and complete the process (but still won't boot), Verizon ROMs will give me an error (cannot open flash, bad). I did check the md5 checksums on ALL the files I used, and tried flashing from adb to no avail.
Before anyone asks, Yes I do clear the data, cache and Dalvik cache before flashing. I am at a loss of what to try next, short of finding someone reputable online to do it for a fee.
Thanks,
Wahran
wahran99 said:
I have a Verizon ADR6350VW HTC Incredible 2. I decided to 'upgrade' it to a new ROM.
I unlocked the boot loader and installed ClockwrkMod Recovery v5.0.2.0
*** UNLOCKED ***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.0312
eMMC-boot
Jul 18 2011,12:39:36
I tried putting an incredible 2 ROM (Viper) and since then it won't fully boot, it gets stuck forever on the green HTC logo on the white background.
I can get to the bootloader, and tried reflashing the same or other downloaded ROMs (all meant for the HTC incredible 2). Without much luck.
The original flashing process was not interrupted. I did a lot of googling and reading (but missed the S-ON/S-OFF part originally), and have tried many different ways to get out of this without luck.
3rd party ROM will flash and complete the process (but still won't boot), Verizon ROMs will give me an error (cannot open flash, bad). I did check the md5 checksums on ALL the files I used, and tried flashing from adb to no avail.
Before anyone asks, Yes I do clear the data, cache and Dalvik cache before flashing. I am at a loss of what to try next, short of finding someone reputable online to do it for a fee.
Thanks,
Wahran
Click to expand...
Click to collapse
1st recommendation: go s-off
2nd recommendation: flash the boot img from the rom in fastboot...I don't know the exact process because I am s-off, but it is discussed in many of the development threads, so now you know what terms to search for at least.
gtdtm said:
1st recommendation: go s-off
2nd recommendation: flash the boot img from the rom in fastboot...I don't know the exact process because I am s-off, but it is discussed in many of the development threads, so now you know what terms to search for at least.
Click to expand...
Click to collapse
Thank you for your reply.
Going S-OFF: I tired, most guides online will show you how to do by going to the OS first (and enabling USB debug). The only one I found from Revolutionary involved doing it from the adb. When I boot into ClockwrkMod, I can run adb just fine (doing adb devices returns the correct S/N amongst other things), but revolutionary tool complains it can't find the device.
I will google again your second recommendation.
wahran99 said:
Thank you for your reply.
Going S-OFF: I tired, most guides online will show you how to do by going to the OS first (and enabling USB debug). The only one I found from Revolutionary involved doing it from the adb. When I boot into ClockwrkMod, I can run adb just fine (doing adb devices returns the correct S/N amongst other things), but revolutionary tool complains it can't find the device.
I will google again your second recommendation.
Click to expand...
Click to collapse
From Nitsuj17 in the viper thread post 2:
If you are dev unlock, you need to pull the boot.img from the rom zip and fastboot it in hboot
The process will be the same for any rom as long as you are dev unlocked.
gtdtm said:
From Nitsuj17 in the viper thread post 2:
If you are dev unlock, you need to pull the boot.img from the rom zip and fastboot it in hboot
The process will be the same for any rom as long as you are dev unlocked.
Click to expand...
Click to collapse
gtdtm,
Thank you again for trying to help, I am still getting no where. I reloaded the Viper ROM, it said it installed correctly (after going through the selection menus and waiting on the progress bar to finish), I had previously extracted the boot.img file and put it with my fastboot.exe. This is my output (I blanked out the S/N with 'x')
C:\HTC>fastboot devices
HTxxxxxxxxxx fastboot
C:\HTC>fastboot erase cache
erasing 'cache'... OKAY [ 1.064s]
finished. total time: 1.064s
C:\HTC>fastboot oem rebootRUU
... OKAY [ 0.338s]
finished. total time: 0.339s
C:\HTC>fastboot flash zip boot.img
sending 'zip' (3786 KB)... OKAY [ 1.155s]
writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
finished. total time: 6.902s
Any idea where to go from here?
wahran99 said:
gtdtm,
Thank you again for trying to help, I am still getting no where. I reloaded the Viper ROM, it said it installed correctly (after going through the selection menus and waiting on the progress bar to finish), I had previously extracted the boot.img file and put it with my fastboot.exe. This is my output (I blanked out the S/N with 'x')
C:\HTC>fastboot devices
HTxxxxxxxxxx fastboot
C:\HTC>fastboot erase cache
erasing 'cache'... OKAY [ 1.064s]
finished. total time: 1.064s
C:\HTC>fastboot oem rebootRUU
... OKAY [ 0.338s]
finished. total time: 0.339s
C:\HTC>fastboot flash zip boot.img
sending 'zip' (3786 KB)... OKAY [ 1.155s]
writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
finished. total time: 6.902s
Any idea where to go from here?
Click to expand...
Click to collapse
I'm really guessing here, but try fastboot flash boot boot.img
---------- Post added at 01:33 PM ---------- Previous post was at 01:29 PM ----------
wahran99 said:
gtdtm,
Thank you again for trying to help, I am still getting no where. I reloaded the Viper ROM, it said it installed correctly (after going through the selection menus and waiting on the progress bar to finish), I had previously extracted the boot.img file and put it with my fastboot.exe. This is my output (I blanked out the S/N with 'x')
C:\HTC>fastboot devices
HTxxxxxxxxxx fastboot
C:\HTC>fastboot erase cache
erasing 'cache'... OKAY [ 1.064s]
finished. total time: 1.064s
C:\HTC>fastboot oem rebootRUU
... OKAY [ 0.338s]
finished. total time: 0.339s
C:\HTC>fastboot flash zip boot.img
sending 'zip' (3786 KB)... OKAY [ 1.155s]
writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
finished. total time: 6.902s
Any idea where to go from here?
Click to expand...
Click to collapse
Try this one. The author includes 2 ways to flash boot.img
http://forum.xda-developers.com/showpost.php?p=22639929&postcount=1
gtdtm said:
I'm really guessing here, but try fastboot flash boot boot.img
---------- Post added at 01:33 PM ---------- Previous post was at 01:29 PM ----------
Try this one. The author includes 2 ways to flash boot.img
http://forum.xda-developers.com/showpost.php?p=22639929&postcount=1
Click to expand...
Click to collapse
fastboot flash boot boot.img worked without error, then I followed it with "fastboot reboot", it took about 15mn, but now it's booted to the SIM unlock screen (that would be my next step).
Thank you very much for all your help! I just registered today to these forums, I see a thank you meter next to the avatar, but can't see I way to 'officially' click and thank you, I will look again....
wahran99 said:
fastboot flash boot boot.img worked without error, then I followed it with "fastboot reboot", it took about 15mn, but now it's booted to the SIM unlock screen (that would be my next step).
Thank you very much for all your help! I just registered today to these forums, I see a thank you meter next to the avatar, but can't see I way to 'officially' click and thank you, I will look again....
Click to expand...
Click to collapse
I'm glad you got it going. You'll probably want to remember that method since you'll have to do it any time you flash a rom.
gtdtm said:
I'm glad you got it going. You'll probably want to remember that method since you'll have to do it any time you flash a rom.
Click to expand...
Click to collapse
Since I posted that message, I had to put back the Verizon stock ROM, so I can SIM unlock the phone (apparently you cannot use the unlock code with a 'cooked' ROM, something I didn't know), and while doing that, HBOOT got downgraded to 0.97, which allowed me to S-OFF the phone with revolutionary. I got the phone SIM unlocked and put back the Viper ROM on it.
In summary, learning from my mistakes, and if I am not mistaken:
1. If you plan to SIM unlock the phone, do it while it is still on stock firmware, it will save you a lot of time and headaches.
2. If you are unlocking the boot loader, S-OFF the phone as well (and put Clockworkmod on it as well), it would make life a lot easier.
3. Then you can go an experiment with ROMs....
gtdtm: Thank you again for your help and patience, and most importantly for keeping me going, as I was about to give up on this phone.
Wahran99
wahran99 said:
Since I posted that message, I had to put back the Verizon stock ROM, so I can SIM unlock the phone (apparently you cannot use the unlock code with a 'cooked' ROM, something I didn't know), and while doing that, HBOOT got downgraded to 0.97, which allowed me to S-OFF the phone with revolutionary. I got the phone SIM unlocked and put back the Viper ROM on it.
In summary, learning from my mistakes, and if I am not mistaken:
1. If you plan to SIM unlock the phone, do it while it is still on stock firmware, it will save you a lot of time and headaches.
2. If you are unlocking the boot loader, S-OFF the phone as well (and put Clockworkmod on it as well), it would make life a lot easier.
3. Then you can go an experiment with ROMs....
gtdtm: Thank you again for your help and patience, and most importantly for keeping me going, as I was about to give up on this phone.
Wahran99
Click to expand...
Click to collapse
No problem. Next challenge: Put TWRP on it instead of Clockwork.
I've been trying to flash an AT&T HTC One M8 with the GPe ROM found here: http://forum.xda-developers.com/showthread.php?t=2706441
I've used this guide and everything went fine: http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
I was in the TWRP Recovery and wanted to format the internal sd card for a fresh start, so I formatted. Afterwards I was unable to get back into the recovery, for some reason I can't erase or format recovery using fastboot, erasing the cache and flashing the recovery image again only brings me to a flickering TeamWin screen, then tries to normally boot but nothing is there for it to boot into so it just sits in a boot loop.
I've tried Philz recovery as well. That works for a little bit but after 10-15 seconds the phone tries to boot normally again and I get stuck in the boot loop.
I tried running `fastboot oem rebootRUU`, that brought me to a black HTC screen and gave me the ability to use fastboot. In RUU mode, I erased the cache again and reflashed the recovery, then erased the cache again and rebooted to fastboot. Tried to boot into Recovery and was greeted with the flickering TeamWin logo and a boot loop.
Can anyone give me a hand here?
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..
http://forum.xda-developers.com/showthread.php?t=2708589
This should set you to the GPE that you were on.
If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
androidbuff123 said:
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..
http://forum.xda-developers.com/showthread.php?t=2708589
This should set you to the GPE that you were on.
If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
Click to expand...
Click to collapse
I'm trying that now, will post back with results
androidbuff123 said:
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..
http://forum.xda-developers.com/showthread.php?t=2708589
This should set you to the GPE that you were on.
If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
Click to expand...
Click to collapse
I tried that and I'm still in a boot loop. This was the output:
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.266s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.618s
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.404s
JustLikeThat said:
I tried that and I'm still in a boot loop. This was the output:
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.266s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.618s
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.404s
Click to expand...
Click to collapse
Doesn't the ruu post say that the flash will fail the first time and if you try it again it should go thru.
Sent from my HTC One_M8 using Tapatalk
androidbuff123 said:
Doesn't the ruu post say that the flash will fail the first time and if you try it again it should go thru.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, and I did try twice but got the same error both times (the error I got was different than in the example). I just realized I don't have S-Off, but am stuck in bootloader without any access to `adb`
You need to be soff
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
JustLikeThat said:
Yes, and I did try twice but got the same error both times (the error I got was different than in the example). I just realized I don't have S-Off, but am stuck in bootloader without any access to `adb`
Click to expand...
Click to collapse
You can also boot a recovery without actually flashing it. Once in boot loader try
flashboot boot recovery.img
Use the actual name of the recovery image instead of recovery.img.
Make sure the twrp or whatever recovery you are using is in the same folder.
Sent from my HTC One_M8 using Tapatalk
androidbuff123 said:
You need to be soff
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
How can I make my phone S-Off without any access to ADB though? I'm pretty much stuck in Bootloader/Fastboot
JustLikeThat said:
How can I make my phone S-Off without any access to ADB though? I'm pretty much stuck in Bootloader/Fastboot
Click to expand...
Click to collapse
if you are able to do fastboot commands.. try using the firewater s-off http://firewater-soff.com/instructions/
you may not be to do this either since you said you don't have adb. Can't help you beyond here.. If you are able to get to RUU mode.. I would suggest trying flashing RUUs since they are most comprehensive.
Did you try flashing the sense RUU?
androidbuff123 said:
You need to be soff
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
You can also boot a recovery without actually flashing it. Once in boot loader try
flashboot boot recovery.img
Use the actual name of the recovery image instead of recovery.img.
Make sure the twrp or whatever recovery you are using is in the same folder.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...
But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
JustLikeThat said:
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...
But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
Click to expand...
Click to collapse
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.
Have you tried fastboot flash boot.img?
of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
androidbuff123 said:
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.
Have you tried fastboot flash boot.img?
of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
Click to expand...
Click to collapse
Using Philz, I see that it can't mount or open anything in `/cache/`... I'm guessing that that's because I wiped the internal storage with TWRP initially. Is there anyway I can mount my phone and add the directories manually?
It really sounds like I need access to ADB but I can't run anything because nothing can mount the internal storage.
In the bootloader, what is next to OS-?
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
androidbuff123 said:
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.
Have you tried fastboot flash boot.img?
of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
Click to expand...
Click to collapse
I've tried that now. It looks as if it's trying to boot but then I just end up back in the bootloader. I'll try with a different image.
In the mean time: I had managed to get Philz CWM formatting the storage properly (with /system, /data, etc), and without any errors that it couldn't mount /cache/recovery (because I had managed to format /cache manually before it rebooted). It's still rebooting 10-15 seconds after booting into recovery, even in the middle of formatting...
I have done more exploring in between reboots and it doesn't look like there's an `/sdcard` directory that it can mount either
umjammerlammy said:
In the bootloader, what is next to OS-?
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
Click to expand...
Click to collapse
Nothing, since it was wiped earlier.
JustLikeThat said:
Nothing, since it was wiped earlier.
Click to expand...
Click to collapse
Try flashing the recovery using the htc one all-in-one toolkit. see if that helps. I'm pretty much out of ideas beyond this point.
JustLikeThat said:
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...
But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
Click to expand...
Click to collapse
Restore a stock backup in twrp then flash the att ruu
If you are in the US message me your number and I can walk you through it
Sent from my HTC One_M8 using XDA Premium 4 mobile app
UPDATE
As mentioned in my initial post, I wiped/formatted my internal memory so I have no internal file structure.
My attempts at booting into or flashing a recovery are failing after 10-15 seconds since they can't mount to anything in the internal memory.
I'm stuck in Bootloader and it seems like the only tool I can utilize is `fastboot`.
I'm currently looking for a way to restore a file structure to my internal memory.
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
What about flashing the stock recovery and then trying a factory wipe?
Hi,
I have a serious problem. My phone for some reason was working fine, but all the sudden is now stuck in HBOOT.
i have tried recovery but the phone would just shut itself down. i couldn't not use adb even though before the phone went into this state, i turned the USB debugging mode on
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
please help , many thanks
Bump, I'm having the same problem on my tmobile m8
mmmgosu said:
Hi,
I have a serious problem. My phone for some reason was working fine, but all the sudden is now stuck in HBOOT.
i have tried recovery but the phone would just shut itself down. i couldn't not use adb even though before the phone went into this state, i turned the USB debugging mode on
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
please help , many thanks
Click to expand...
Click to collapse
raphi809 said:
Bump, I'm having the same problem on my tmobile m8
Click to expand...
Click to collapse
What versions of the M8 do you have?
EddyOS said:
What versions of the M8 do you have?
Click to expand...
Click to collapse
I have a t-mobile m8, I actually started a thread over there http://forum.xda-developers.com/tmobile-htc-one-m8/help/m8-bricked-soloution-t2818678 but so far no answers either
raphi809 said:
I have a t-mobile m8, I actually started a thread over there http://forum.xda-developers.com/tmobile-htc-one-m8/help/m8-bricked-soloution-t2818678 but so far no answers either
Click to expand...
Click to collapse
In which case stick to your thread as opposed to jumping on to others, makes it easier to follow
EddyOS said:
In which case stick to your thread as opposed to jumping on to others, makes it easier to follow
Click to expand...
Click to collapse
Yes, if you have already started a thread asking for help, don't jump around.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
mmmgosu said:
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
Click to expand...
Click to collapse
What response do you get for:
fastboot devices
If it returns the device ID, than try:
fastboot erase cache
Then try to flash recovery again.
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
when i tried fastboot devices it returns an ID
but when i tried
fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
i have at&t
Maybe try to flash one of the modded hboots?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hawkysoft said:
Maybe try to flash one of the modded hboots?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do i do that?
fastboot oem rebootRUU
fastboot flash zip name_of.zip
fastboot reboot-bootloader
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hard to help you if you do not even bother to answer all the questions posed to you. As I asked earlier:
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
redpoint73 said:
Hard to help you if you do not even bother to answer all the questions posed to you. As I asked earlier:
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
Click to expand...
Click to collapse
I tried factory reset but it doesn't seem to be doing anything, just a white screen with android picture.
what do you mean by " corrupts the internal memory on modded devices?"
i tried
fastboot oem rebootRUU
but it says ...
(bootloader) [DEBUG] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(560): error 2
(bootloader) Start Verify: 3
(bootloader) [DEBUG] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.018s]
finished. total time: 0.018s
question, can i flash TWRP with 0p6bimg.zip?
If yes, can anyone provide the file?
Thanks
mmmgosu said:
I tried factory reset but it doesn't seem to be doing anything, just a white screen with android picture.
what do you mean by " corrupts the internal memory on modded devices?"
Click to expand...
Click to collapse
It means you should never ever do that (factory reset in bootloader) if bootloader unlocked, rooted, etc.. Only within the OS Settings or in recovery.
What this means, is that on a stock device, factory reset in bootloader works normally; but on a modded (rooted, etc.) device this corrupts the internal memory and renders it unable to be read or written to. This is probably why can't wipe cacher, install custom recovery, reboot RUU, etc (all are giving you errors reading data; and I think this is the reason why).
Connect the phone to a Windows PC (sorry if that is not what you use, its all I know) and use Device Manager to format the phone's internal memory. Once its formatted try again to wipe cache and flash custom recovery again.
This is great info to tuck away for future reference. How should the memory be formatted? FAT32 or exFAT?
Sent from my Nexus 10
bruce7373 said:
How should the memory be formatted? FAT32 or exFAT?
Click to expand...
Click to collapse
FAT32.
redpoint73 said:
It means you should never ever do that (factory reset in bootloader) if bootloader unlocked, rooted, etc.. Only within the OS Settings or in recovery.
What this means, is that on a stock device, factory reset in bootloader works normally; but on a modded (rooted, etc.) device this corrupts the internal memory and renders it unable to be read or written to. This is probably why can't wipe cacher, install custom recovery, reboot RUU, etc (all are giving you errors reading data; and I think this is the reason why).
Connect the phone to a Windows PC (sorry if that is not what you use, its all I know) and use Device Manager to format the phone's internal memory. Once its formatted try again to wipe cache and flash custom recovery again.
Click to expand...
Click to collapse
How exactly does one format the phone's internal memory via Device Manager?
adriankeith said:
How exactly does one format the phone's internal memory via Device Manager?
Click to expand...
Click to collapse
Couldn't actually tell you "exactly" myself as I haven't personally had to do it. But I know its been given as advice many times, and reported to work (at least for some instances of corrupted internal memory or can't mount memory).
In brief, open Device Manager, browse to the device/internal memory, and try to find the option to format FAT32.
Ok, I'm in the same pickle as person above. Let me just post the state the phone was in before everything happened. Unlocked bootloader, s-on, Android revolution HD installed (4.4.3). Friend tried to get back to stock and now the phone is stuck in hboot. Things done to phone: bootloader relocked, tried to change tampered flag without success, flashed stock recovery and boot image. Fastboot devices returns Id, storage is not recognized, adb commands do not work. I think he also tried to do factory reset while in hboot. Just stumbled upon this format memory thing, will do it once I get home. What are the steps after, can I just flash the correct ROM.zip or some moded hboot? If you can just point me in right direction I would very much appreciate it, thanks. Also if you need any additional info just ask for it
Similar problem here also,
I could really use some help guys! The new GPE 6.0 images are out on XDA. http://forum.xda-developers.com/htc...uu-m8-google-play-edition-5-1-lmy470-t3226765
I did a full wipe then I put on the rom using the zip file first through TWRP and it did install but the radio drivers failed.
So I then downloaded the system img file ruu and renamed it to 0P6BIMG.zip and now it is just stuck in a loop and will not boot into the Operating system. It will just freeze at the White HTC logo.
I press the power button and the volume up button to reset the device then push the power button and volume down button to get into the bootloader the bootloader instantly selects Hboot and starts loading up the 0P6BIMG.zip. The phone then procedes to give me the highlighted HBoot option and the message "Press <POWER> to reboot." Which then reboots right into the White HTC loading screen.
The phone is unlocked and has s-on. I have tried using ADB commands but cannot get an ID with ADB devices command.
Can someone help a brotha out?
Hi
I have tried going back to Sense stock after trying out GPE edition lollipop flavour.
Unfortunately somewhere along the way something has gone horrible wrong and I'm now stuck in a bootloop with a Red Triangle
My bootloader is currently locked, althougth I am S-Off. I can still access fastboot and RUU but the problem is when I try to flash standard or twrp recovery i get the following error message
From RUU
./fastboot flash recovery recov.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.442s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.447s
So I currently have no os, no recovery and no way of loading a recovery back on as you can see above... am I screwed ???
Have now managed to put stock recovery back (via ruu) on and at the top of the screen it says entering recovery but never gets any further ...
Have tried again to install twrp ... no joy there what so ever
Dont' Worry I got the same problem but I fixed it!!
gsusx said:
Hi
I have tried going back to Sense stock after trying out GPE edition lollipop flavour.
Unfortunately somewhere along the way something has gone horrible wrong and I'm now stuck in a bootloop with a Red Triangle
My bootloader is currently locked, althougth I am S-Off. I can still access fastboot and RUU but the problem is when I try to flash standard or twrp recovery i get the following error message
From RUU
./fastboot flash recovery recov.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.442s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.447s
So I currently have no os, no recovery and no way of loading a recovery back on as you can see above... am I screwed ???
Click to expand...
Click to collapse
Hi
Press power,volume up and down for 90 seconds.It will enter into bootloader.
Then press recovery. If it is not going to recovery,stay in the bootloader mode. Connect to the pc.
Download this software from this website.
http://www.hasoon2000.info/
Click your phone model.
(If it is HTC ONE M8 CLICK this link http://www.hasoon2000.info/?device=One%202014%20(M8))
Unzip it.
open the software.
Unlock the bootloader by following the step shown on the software.
After,
Click any recovery but I prefer TWRP.
Install custom rom and you are good to go
Absolute legend ... thank you !!!
Hey guys,
my girlfriend has an M9. Saturday it lied idle on the table and rebooted itself. When it booted it just showed the white screen with the HTC logo and the read disclaimer warning.
I rebooted with power off and volume up and the phone just bootlooped all the time. Shows black screen with HTC Logo.
I tried to press the Vol down button on a restart but that didnt work it just bootlooped as before. Then I pressed Vol up +down and could enter the bootloader. From there I entered twrp and tried to wipe the system and then it just shows:
"Could not mount /data and unable to find crypto footer." and it failed to mount /cache , /system, /data, /devlog, /carrier , /cota , /preload and "Unable to mount storage" followed by failes in /data and cache.
Every fail have an (Invalid argument).
I also tried following fastboot commands:
format system
Couldn't parse partition size '0x0X118000000'.
erasing 'system'...
OKAY [ 0.241s]
finished. total time: 0.241s
format data
Formatting is not supported for file system with type ''.
format cache
Couldn't parse partition size '0x0X14000000'.
erasing 'cache'...
OKAY [ 0.270s]
finished. total time: 0.270s
flash zip 0PJAIMG.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2368399706 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2368399706 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2368399706 is not a multiple of the block size 4096
OKAY [ 1.015s]
writing 'zip' 1/1...
(bootloader) HOSD CL#671447
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.209s
The output of getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(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: VODAP102
all:
finished. total time: 0.006s
Could someone please tell me if it even possible to rescue the phone? Is there something I forget to try or do somebody know something?
I appreciate every help i could get.
And forgive my bad english.
I think Twrp has gone mental.. If i remember correctly you have to flash back to stock. Follow flippy's thread in the general section.
Beamed in by telepathy.
Thx for the answer first.
I already tried what is shown at the spreadsheet of Flippy. I downloaded the right RUU again and gave it one more try but the same. It appears "Start ui_updating". After a few seconds the screen turns black and it appears the HTC logo on an black screen and it vibrates and turn black agan and again the logo with vibration. If i immediatly try to flash it a second time, itcontinues,shows name of system types but the percent is still 0. When it reaches a certain system type (after 10 or 12) it reboots to the white screen with the green HTC logo and the red disclaimer and stuck there.
Do you have an idea?
I have the same error. We have to do something and solve this. Can you solve it?
you can also just get a backup for twrp, which is matching your cid/mainversion, wipe everything except your internal storage and restore the backup
Like i said at the beginning, its not possible to wipe the partitions. They cant be mounted by twrp. I tried already to install an TWRP Backup with the right CID but even that failed because twrp couldn't write to the partitions.
THX for your answers
Ah fock, at first remove your imei from first post, then tell me if your phone is s-offed or not
Sent from my HTC One M9 using XDA-Developers mobile app
Oh sry overlocked that the imei was there.
The phone is s-on.
get stock recovery for your mainversion/cid, re-lock the bootloader, and flash a signed firmware matching your cid/mainversion, and flash with fastboot oem rebootRUU
then fastboot flash firmware nameofthezip.zip and do this a second time and then fastboot erase cache and reboot into download mode, unlock bootloader again and flash twrp and you should be able to wipe everything
DeeZZ_NuuZZ said:
get stock recovery for your mainversion/cid, re-lock the bootloader, and flash a signed firmware matching your cid/mainversion, and flash with fastboot oem rebootRUU
then fastboot flash firmware nameofthezip.zip and do this a second time and then fastboot erase cache and reboot into download mode, unlock bootloader again and flash twrp and you should be able to wipe everything
Click to expand...
Click to collapse
It wont work. Phone dont let us to write anything
We cant change cid, mid, lock and unlock bootloader. It is emmc issue. Emmc have to change.
P.s. my phone is s-off.
degerli43 said:
It wont work. Phone dont let us to write anything
We cant change cid, mid, lock and unlock bootloader. It is emmc issue. Emmc have to change.
P.s. my phone is s-off.
Click to expand...
Click to collapse
you should be able to fix it with an install of a RUU. s-off has more chances for that.
the other guy should try to flash the firmware zip in RUU mode, not just normal mode. it should work.. if not he has to get a RUU, if that doesn't work.. yea only RMA or how it is called for you should help. if they won't fix it, sell the device, and get another one
DeeZZ_NuuZZ said:
you should be able to fix it with an install of a RUU. s-off has more chances for that.
the other guy should try to flash the firmware zip in RUU mode, not just normal mode. it should work.. if not he has to get a RUU, if that doesn't work.. yea only RMA or how it is called for you should help. if they won't fix it, sell the device, and get another one
Click to expand...
Click to collapse
When i type fastboot oem rebootRUU the phone rstarting rebooting continuously so i cant flash anything. It s very expensive device here and i love it. I will be so sad if it wont fix
DeeZZ_NuuZZ said:
get stock recovery for your mainversion/cid, re-lock the bootloader, and flash a signed firmware matching your cid/mainversion, and flash with fastboot oem rebootRUU
then fastboot flash firmware nameofthezip.zip and do this a second time and then fastboot erase cache and reboot into download mode, unlock bootloader again and flash twrp and you should be able to wipe everything
Click to expand...
Click to collapse
Ok when i type fastboot oem lock in the download mode, it restarts and stops again in the bootloop on the HTC logo with blackscreen. If I press Vol UP+DOWN I can see that the device is still unlocked.
Do you have any other ideas? And thx for your help
VGLink said:
Ok when i type fastboot oem lock in the download mode, it restarts and stops again in the bootloop on the HTC logo with blackscreen. If I press Vol UP+DOWN I can see that the device is still unlocked.
Do you have any other ideas? And thx for your help
Click to expand...
Click to collapse
Get the proper HTC fastboot files and try with that...if that doesn't work, your phone is dead..I can't help further, sorry
Sent from my HTC One M9 using XDA-Developers mobile app
Hi, its not possible to enter RUU or to relock or Flash the Phone. It seems its gone dead by itself. Nevertheless thank You for your help .