Related
Hi everyone!
I've been searching and reading around trying to solve a bootloop problem on my HTC Desire S/Saga (or at least I think it is a bootloop problem) but, so far, I've had no luck.
Here's what has happened and what's going on:
1) S-off and got hboot 6.98.1002 through revolutionary
2) phone worked normally for six months and suddenly, without any changes or flashes, it rebooted and started a boot loop, ie, I can't get into any in-OS menus.
3) Choosing recovery of factory settings from hboot menu just reboots the phone and restarts the loop.
4) I've tried flashing (both through fastboot and android flasher) the eng hboot 0.98.0000 and clockworkmod recovery images but neither had any effect.
Phone was vodafone-locked, running a vanilla Android 2.3.4.
hboot menu data:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
I don't have any backup data from pre-revolutionary, either :|
I'm knocking my head against the walls, hoping that the phone's only temporarily bricked... any ideas?
Thanks in advance for helping a n00b...
Doesn't sound like a hboot problem you me, but that could just be me. And I don't think flashing the stock hboot will help.
Are you sure you are flashing the ENG hboot? It's 0.98.2000. 0.98.0000 is most likely your stock hboot and can't be flashed over revolutionary hboot in most cases.
So to get back to stock stock..... You will need to run your RUU after the new hboot has been flashed.
Another option is for you to install a custom ROM and avoiding the RUU. I still suggest you flash the ENG hboot though.
Head for this thread for help
http://forum.xda-developers.com/showthread.php?t=1488672
Thanks everybody!
I've been away for the last few days so I haven't been able to test anything, but tomorrow evening I'll test both suggestions and post feedback.
Thanks again!
So, I've trying out your suggestions and...
foX2delta said:
Doesn't sound like a hboot problem you me, but that could just be me. And I don't think flashing the stock hboot will help.
Are you sure you are flashing the ENG hboot? It's 0.98.2000. 0.98.0000 is most likely your stock hboot and can't be flashed over revolutionary hboot in most cases.
So to get back to stock stock..... You will need to run your RUU after the new hboot has been flashed.
Another option is for you to install a custom ROM and avoiding the RUU. I still suggest you flash the ENG hboot though.
Click to expand...
Click to collapse
So I tried to flash the ENG hboot from this thread, using android flasher and later using this method, but adb never lists my Saga.
Fastboot lists it correctly, though. I *think* I had USB debugging on, if I recall correctly.
Using androidflasher I get a flash ok notice and then the bootloop just restarts...
Any ideas?
mOh19973 said:
Head for this thread for help
http://forum.xda-developers.com/showthread.php?t=1488672
Click to expand...
Click to collapse
Thanks moh19973, I'll leave feedback at your thread (no luck, though..)
thanks again to everybody
Opalid said:
Hi everyone!
I've been searching and reading around trying to solve a bootloop problem on my HTC Desire S/Saga (or at least I think it is a bootloop problem) but, so far, I've had no luck.
Here's what has happened and what's going on:
1) S-off and got hboot 6.98.1002 through revolutionary
2) phone worked normally for six months and suddenly, without any changes or flashes, it rebooted and started a boot loop, ie, I can't get into any in-OS menus.
3) Choosing recovery of factory settings from hboot menu just reboots the phone and restarts the loop.
4) I've tried flashing (both through fastboot and android flasher) the eng hboot 0.98.0000 and clockworkmod recovery images but neither had any effect.
Phone was vodafone-locked, running a vanilla Android 2.3.4.
hboot menu data:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
I don't have any backup data from pre-revolutionary, either :|
I'm knocking my head against the walls, hoping that the phone's only temporarily bricked... any ideas?
Thanks in advance for helping a n00b...
Click to expand...
Click to collapse
Your problem sounds exactly like the one on the thread linked below.... in which case, if you just try the steps from the concerned thread, and are still unable to fix your device, it can be written off as another dead eMMC...
Just follow the instructions on this thread...maybe you will have better luck than the OP?
http://forum.xda-developers.com/showthread.php?t=1507106
So did your hboot change or not? If hboot and recovery won't flash then I have to agree with above, fried emmc :-(
yeah it could be an emmc problem, you may want to check the sticky in the development forum, if this is the real problem there is a possibility for a fix, not necessarily emmc replacement
enigmaamit said:
Your problem sounds exactly like the one on the thread linked below.... in which case, if you just try the steps from the concerned thread, and are still unable to fix your device, it can be written off as another dead eMMC...
Just follow the instructions on this thread...maybe you will have better luck than the OP?
http://forum.xda-developers.com/showthread.php?t=1507106
Click to expand...
Click to collapse
Thanks, tried everything and had the exact same results. Fried eMMC, I guess..
This is really wierd, I got a phonecall, turned the call off, the phone rebooted and entered the bootloop.
Nothing fishy or wierd, no flashing erros, just a regular phonecall from my boss. Damn :|
If only I could get the normal hboot on I could repair it under warranty
Well, thanks everybody
Try going for warranty repair, for a few guys over here at xda no one checked (or din not care) whether the phone was rooted or s-off when they went to service their phone. Maybe you'll get lucky too. Good luck!
Hi all,
I hope one of you masterminds is able to help me out.
I tried to root my sensation without s-off with hecdev.com (using One_X_All-In-One_Kit_v1.0) and then tried to install cm9 from one the links here via revcovery with CWM 5.8.0.9.
But then I was stuck with the loading animation...
I cannot run Android now, so I cannot flash a stock RUU.
I can enter bootloader, which seems to be unlocked, here's the info:
"Unlocked"
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
I was on the latest official ROM (ICS, via OTA) before trying that.
I have not succeeded in flashing a ROM anymore.
Do I need to get S-Off first?
Or is HBOOT to new? Do I have to revert? How?
I tried older HBOOT, but it wouldn'T do anything after PArsing
Please help, any hint is appreciated =/
PS: I would be more than happy to have a stock rom again...as mentioned, cannot use a ruu.exe file, as it seems fastboot usb ist not recognizable by ruu.exe
Edit: After the 4th or 5th try, RUU recognized the phone when in fastboot usb mode, but update fdailed, cwm saif "security fail" ... sigh, seems I really blew it this time
the_bmg said:
PS: I would be more than happy to have a stock rom again...as mentioned, cannot use a ruu.exe file, as it seems fastboot usb ist not recognizable by ruu.exe
Edit: After the 4th or 5th try, RUU recognized the phone when in fastboot usb mode, but update fdailed, cwm saif "security fail" ... sigh, seems I really blew it this time
Click to expand...
Click to collapse
Hi,
Start again using THIS GUIDE
Flash the boot.img from your ROM through fastboot.
Extra step 1 from this guide: http://forum.xda-developers.com/showthread.php?p=25587345
Be sure to use the boot.img from your ROM.
Then make a clean install of the ROM again.
Also, read that thread for the sake of understanding what you're doing.
There is NO need yet to flash an RUU.
Latest OTA comes with hboot 1.29 which is locked.
You might not be in the latest one, perhaps start with an RUU with.the latest fw (3.33).
Sent from my HTC Sensation using xda premium
thanks malybru & kgs1992 - tried that, and the 4ext touch recoery said both superwipe and the rom installed correctly.
but when rebooting the white screen with the green htc logo appears right away and nothing more happens...any idea? I may have messed up the kernel before, but when asked by ext4 recovery whether to flash a kernel, tried both custom and stock, none changed the problem with booting up
@Raven2k: Manually installing boot.img with fastbok seemed to help, at least I come over the white screen, am stuck with the beatsaudio logo right now - thanks so far =)
the_bmg said:
thanks malybru & kgs1992 - tried that, and the 4ext touch recoery said both superwipe and the rom installed correctly.
but when rebooting the white screen with the green htc logo appears right away and nothing more happens...any idea? I may have messed up the kernel before, but when asked by ext4 recovery whether to flash a kernel, tried both custom and stock, none changed the problem with booting up
Click to expand...
Click to collapse
Can you try this again
Flash boot.img again as kgs explained
Then flash the rom again... Don't do any wipe
Sent from my pyramid.. Through blazing fast sonic waves
Amazing, guys! Thanks for your help, my phone is back :good::fingers-crossed::laugh:
the_bmg said:
Amazing, guys! Thanks for your help, my phone is back :good::fingers-crossed::laugh:
Click to expand...
Click to collapse
good
and for thanks ..there is a button for that
Apologies in advance as I know there are many similar threads on here but I've read so much I'm just getting confused! Here goes...
Yesterday I tried to install the official version of ICS onto my Desire S. I followed all of the steps and the computer said the software had been successfully installed. Since then my phone will not boot past the HTC logo screen. I can get into the hboot screen by booting with power on + volume down and my computer recognises the phone when i plug it in in fastboot. It won't go into recovery mode and a factory reset doesn't work. I have tried re-installing the software but it makes no difference. I bought the phone second hand and it was already rooted so I don't have the programs that were used.
When booting in hboot the following info apppears:
-revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT - 6.98.1002
RADIO - 3831.19.00.110
eMMC-boot
Mar 10 2011, 14:58:38
I have read that this version of hboot is not compatible and that I require an hboot upgrade but i'm not sure how to do this as I cannot access the sd folder of my phone and I don't have an external micro SD reader.
Any help would be greatly appreciated. Even if means reverting back to gingerbread or using another ROM. I just want my phone to work again!
This guy have a same problem here http://forum.xda-developers.com/showthread.php?t=1892274 and already solved
Sent from my HTC Desire S using xda app-developers app
if your phone is detected in fastboot, the best bet you have is to install a custom recovery and then flash another ROM through it.
check this thread, you may find something to help you.. http://forum.xda-developers.com/showthread.php?t=1186401
I would recommend the CM10 by nk111. http://forum.xda-developers.com/showthread.php?t=1776256&highlight=all+credit
Try the latest stable one. ie, the 30-Oct version.
I think this is something similar with you http://forum.xda-developers.com/showthread.php?t=1892274
Read thoroughly, solution is post no8 only if you have the same issue.
how do I install a custom recovery with my phone in it's current state? and where can i get it from?
rain987 said:
I think this is something similar with you http://forum.xda-developers.com/showthread.php?t=1892274
Read thoroughly, solution is post no8 only if you have the same issue.
Click to expand...
Click to collapse
Thank you. I read that thread earlier. It does sound very similar. As i cannot access my sd folder how do I put the updated hboot file in there? do i need to get hold of a micro sd reader?
check this. and go through it, the info you seek will be there.. http://forum.xda-developers.com/showthread.php?t=1186401
lauraenelson said:
Thank you. I read that thread earlier. It does sound very similar. As i cannot access my sd folder how do I put the updated hboot file in there? do i need to get hold of a micro sd reader?
Click to expand...
Click to collapse
Errr u could try putting the file into the sd with another phone.
If u can enter recovery mode, u can connect the sd card with the computer.
lauraenelson said:
Apologies in advance as I know there are many similar threads on here but I've read so much I'm just getting confused! Here goes...
Yesterday I tried to install the official version of ICS onto my Desire S. I followed all of the steps and the computer said the software had been successfully installed. Since then my phone will not boot past the HTC logo screen. I can get into the hboot screen by booting with power on + volume down and my computer recognises the phone when i plug it in in fastboot. It won't go into recovery mode and a factory reset doesn't work. I have tried re-installing the software but it makes no difference. I bought the phone second hand and it was already rooted so I don't have the programs that were used.
When booting in hboot the following info apppears:
-revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT - 6.98.1002
RADIO - 3831.19.00.110
eMMC-boot
Mar 10 2011, 14:58:38
I have read that this version of hboot is not compatible and that I require an hboot upgrade but i'm not sure how to do this as I cannot access the sd folder of my phone and I don't have an external micro SD reader.
Any help would be greatly appreciated. Even if means reverting back to gingerbread or using another ROM. I just want my phone to work again!
Click to expand...
Click to collapse
I had the same issue and manage to fixed it by following this link: http://forum.xda-developers.com/showthread.php?t=1679338
I used a second sd card, I formatted it first and only put the file I need at that time on it. I
In step 5 Reboot into bootloade, select recovery wait till you see the screen with the red triangle exclamation mark and press the volume up and power button at the same time.
You will enter the Android system recovery <3e> and see the following options:
reboot system now
apply update from SD card
wipe data/factory reset
wipe cache partition
wipe the cache partition and wipe data/factory reset
Now following step B from this link: http://forum.xda-developers.com/showthread.php?t=1858508
When update is finished - reboot, then configure ICS and delete PG88IMG.zip from sd card.
Thanks very much for your help guys. I've managed to sort the problem. For everyone else out there with the same problem I'll tell you what I did....
The hboot version on my phone (6.98.1002) is not compatible with the official ICS software update.
http://forum.xda-developers.com/showthread.php?t=1488672 - this thread shows how to update the hboot when stuck in bootloop.
I then reinstalled the ICS ruu onto my phone and it is now working fine although it is no longer rooted.
Could someone please tell me the best way to root my phone again. In the bootloader menu it still says revolutionary s-off but i cannot access ROM manager or titanium backup. Do I need to fully root it again?
Since you installed the official RUU, your root is probably gone.. You will have to fully root the phone again to get root access.
You could try flashing a custom recovery in fastboot, and then flashing SuperSu or superuser from recovery.
teadrinker said:
You could try flashing a custom recovery in fastboot, and then flashing SuperSu or superuser from recovery.
Click to expand...
Click to collapse
This. As long as you're S-OFF, rooting is just a matter of flashing custom recovery (using fastboot), and flashing SuperSU ZIP in recovery. The first step is covered in so many tutorials that any search will lead you right to it.
Sorry for late response but thank you all who helped me. My phone is now fully functional and I couldn't have done it without you guys. Much appreciated!
lauraenelson said:
Sorry for late response but thank you all who helped me. My phone is now fully functional and I couldn't have done it without you guys. Much appreciated!
Click to expand...
Click to collapse
Report this thread to a mod to be closed.
Sent from my HTC Desire S using xda app-developers app
Mark the thread as solved
“Hardware: The parts of a computer system that can be kicked.”
(Jeff Pesis)*
Hi all,
My sensation has been shutting down for no reason for a long time now. No matter what ROM, what kernel, even I have changed the battery twice. It just sometimes turns off, and when I reboot (if it does) it either has very low battery or it will keep shutting down until I plug it in.
To me, it seems like there is something misleading the power level or something. I have super wiped the phone, even reformatted my SD, changed recovery and did the same, flashed thousands of roms (4.1 and 4.2)... and it still does the same.
Funny enough, it doesnt happen when I am in recovery mode (for example, after it shuts down, I reboot into recovery, spend some time there, then reboot and as soon as it boots, bam it shuts down).
This makes me think there is something in a partition that is not touched by the wiping scripts that is bugged and therefore is not fixed after flashing roms etc.
I recently manually wiped and formatted all of my Asus Transformer's partitions (even the recovery) using my PC and it works great, that fixed a problem that also was carried on from ROM to ROM. Hopefully there is a way to do the same for my sensation to give it a 100% clean start.
Thank you very much in advance!
Sent from my Transformer TF101 using Tapatalk 4 Beta
TheKaser said:
Hi all,
My sensation has been shutting down for no reason for a long time now. No matter what ROM, what kernel, even I have changed the battery twice. It just sometimes turns off, and when I reboot (if it does) it either has very low battery or it will keep shutting down until I plug it in.
To me, it seems like there is something misleading the power level or something. I have super wiped the phone, even reformatted my SD, changed recovery and did the same, flashed thousands of roms (4.1 and 4.2)... and it still does the same.
Funny enough, it doesnt happen when I am in recovery mode (for example, after it shuts down, I reboot into recovery, spend some time there, then reboot and as soon as it boots, bam it shuts down).
This makes me think there is something in a partition that is not touched by the wiping scripts that is bugged and therefore is not fixed after flashing roms etc.
I recently manually wiped and formatted all of my Asus Transformer's partitions (even the recovery) using my PC and it works great, that fixed a problem that also was carried on from ROM to ROM. Hopefully there is a way to do the same for my sensation to give it a 100% clean start.
Thank you very much in advance!
Sent from my Transformer TF101 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi,
The recovery 4EXT has a "Format all partitions except sd card" option.
Look HERE for an installation guide.
Alternatively,you could run a RUU ,which will return all your partitions to stock.
Look HERE
Have you tried the trick of jamming some card to improve the contact of your battery?
It may just be loose,and the card keeps it firmly in place.
malybru said:
Hi,
The recovery 4EXT has a "Format all partitions except sd card" option.
Look HERE for an installation guide.
Alternatively,you could run a RUU ,which will return all your partitions to stock.
Look HERE
Have you tried the trick of jamming some card to improve the contact of your battery?
It may just be loose,and the card keeps it firmly in place.
Click to expand...
Click to collapse
Hi, thank you for your reply.
I used to have 4ext and I have used many times the format all option. I recently switched to TWRP recovery to try their formatting options too. Neither solved the problem.
Also, I have two anker batteries, I have made sure they are not loose. Nevertheless, this happens even when the phone resting on the table, so I am sure that is not the issue. I have switched them wth my gf's sensation, and hers works fine and mine doesn't.
I will try the RUU option to see if going back to stock will remove any kind of bricking that may have occured after so many flashes..
do you think there is anything that is not touched by rom flashing, recovery changing, and partition formatting that may be the cause of the problem? I also updated the firmware too 3.32 I believe it was (the latest) for JB 4.2.2... I dont know what else I can flash or change or format to try to eliminate this powering-off issue...
thanks a lot once more
TheKaser said:
Hi, thank you for your reply.
I used to have 4ext and I have used many times the format all option. I recently switched to TWRP recovery to try their formatting options too. Neither solved the problem.
Also, I have two anker batteries, I have made sure they are not loose. Nevertheless, this happens even when the phone resting on the table, so I am sure that is not the issue. I have switched them wth my gf's sensation, and hers works fine and mine doesn't.
I will try the RUU option to see if going back to stock will remove any kind of bricking that may have occured after so many flashes..
do you think there is anything that is not touched by rom flashing, recovery changing, and partition formatting that may be the cause of the problem? I also updated the firmware too 3.32 I believe it was (the latest) for JB 4.2.2... I dont know what else I can flash or change or format to try to eliminate this powering-off issue...
thanks a lot once more
Click to expand...
Click to collapse
Hi,
The RUU option seems all that is left.
Backup everything before you start.
Are you supercid?
malybru said:
Hi,
The RUU option seems all that is left.
Backup everything before you start.
Are you supercid?
Click to expand...
Click to collapse
Yes, back in the day I used revolutionary, got supercid, and recently I updated the firmware to 3.33 (hboot 1.27.1100), and I am S-OFF.
my bootloader:
-Firmware 3.33 .
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OpenADSP-V05.6.0.2226.00.0418
eMMC-boot
Might this be caused by the radio? it's the only thing I havent changed recently.
Also, being supercid, and S-OFF, do I have to lock the bootloader and S-ON? I quickly looked at the RUU thread and that is what I understood...
thanks man!
TheKaser said:
Yes, back in the day I used revolutionary, got supercid, and recently I updated the firmware to 3.33 (hboot 1.27.1100), and I am S-OFF.
my bootloader:
-Firmware 3.33 .
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OpenADSP-V05.6.0.2226.00.0418
eMMC-boot
Might this be caused by the radio? it's the only thing I havent changed recently.
Also, being supercid, and S-OFF, do I have to lock the bootloader and S-ON? I quickly looked at the RUU thread and that is what I understood...
thanks man!
Click to expand...
Click to collapse
Hi,
Noooooooooooooooooooooooooooooooooo!!!!!!!!!!!!!
DO NOT GO TO HTCDEV if you are s-off.
The reason I asked is because you can flash any RUU being s-off and super cid.
Just choose a 3.33 European RUU to run.
EDIT:
Look HERE
Just use the guide to show you how to run it.
malybru said:
Hi,
Noooooooooooooooooooooooooooooooooo!!!!!!!!!!!!!
DO NOT GO TO HTCDEV if you are s-off.
The reason I asked is because you can flash any RUU being s-off and super cid.
Just choose a 3.33 European RUU to run.
EDIT:
Look HERE
Just use the guide to show you how to run it.
Click to expand...
Click to collapse
thanks man, I will run the RUU. I believe I have already done this in the past, but my memory is terrible xDD
3.2 Using RUU to restore partitions
Find your right RUU using 2 in this guide.
Flash your RUU as you normally would by double clicking the executable & following the instructions, you phone must be connected to PC via fastboot USB (in the bootloader).
If you get a Hboot Pre-update message, re-run the RUU once again with your phone connected in fastboot USB.
If the previous step fails, follow points listed under 4. Flashing RUU manually.
Reboot your device to bootloader, your bootloader should now say *Locked* or *Relocked*
Click to expand...
Click to collapse
From the tutorial on RUU in the link you provided, the last point on bootloader being locked or relocked... will I need to do revolutionary again or the other method to unlock it again? Will this be drawback flashing a new ROM?
thanks!
TheKaser said:
thanks man, I will run the RUU. I believe I have already done this in the past, but my memory is terrible xDD
From the tutorial on RUU in the link you provided, the last point on bootloader being locked or relocked... will I need to do revolutionary again or the other method to unlock it again? Will this be drawback flashing a new ROM?
thanks!
Click to expand...
Click to collapse
Hi,
Bootloader will not be affected because you are s-off.
You will not lose s=off either.
YOU WILL LOSE EVERYTHING else.
So,backup first.
You will end up with stock recovery,ROM and kernel.
You will need to re-install a custom recovery,before you install a new ROM.
See how it all works before you do anything.
malybru said:
Hi,
Bootloader will not be affected because you are s-off.
You will not lose s=off either.
YOU WILL LOSE EVERYTHING else.
So,backup first.
You will end up with stock recovery,ROM and kernel.
You will need to re-install a custom recovery,before you install a new ROM.
See how it all works before you do anything.
Click to expand...
Click to collapse
well, the RUU went fine, but now I have a locked bootloader, and can't flash a recovery via fastboot. (still S-OFF).
TheKaser said:
well, the RUU went fine, but now I have a locked bootloader, and can't flash a recovery via fastboot. (still S-OFF).
Click to expand...
Click to collapse
Hi,
Look HERE
Post 2:
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
Should unlock your phone again.
Run the phone for a while.
Does it still reboot?
malybru said:
Hi,
Look HERE
Post 2:
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
Should unlock your phone again.
Run the phone for a while.
Does it still reboot?
Click to expand...
Click to collapse
sweet, that did the trick
I flashed a dark splash screen and the cwm recovery. All went well and I could flash my 4.2.2 rom. I will restore my titanium backup apps and hope for the best. Cant tell now if the sudden turning off still happens because my phone has been plugged in all the time while I was doing this.
I will report probably tomorrow once the battery is bit used.
Sir, I must say, you are a legend. Thank you very very much for your help!!! your rock!:good: :laugh:
TheKaser said:
sweet, that did the trick
I flashed a dark splash screen and the cwm recovery. All went well and I could flash my 4.2.2 rom. I will restore my titanium backup apps and hope for the best. Cant tell now if the sudden turning off still happens because my phone has been plugged in all the time while I was doing this.
I will report probably tomorrow once the battery is bit used.
Sir, I must say, you are a legend. Thank you very very much for your help!!! your rock!:good: :laugh:
Click to expand...
Click to collapse
Hi,
Hope it all works out.
Can't flash anything, keeps saying "E:footer is wrong signature verification failed"
I think I've done messed up now...
I've been having a lot of issues with my HTC One M8 (Verizon) (rooted, s-off) phone since the screen was replaced. Mainly, my GPS signal completely stopped working. Anyway, that has led me flashing various ROMS, update.zip files, and 0p6bimg.zip files. Previously, I was working on a 32-bit Win7 laptop during the first round of nonsense. I'd be able to trace back my steps better but since that laptop is no longer in my possession, along with all the various files I used during the process. During that time, I had pretty much bricked my phone where it was stuck on the red Verizon splash screen indefinitely. Eventually, through much trial and error and internet searching, IRCC I flashed some new FUU and RUU files. Ultimately, I was able to successfully sideload the ViperOneM8_4.3.0_OTA Lollipop ROM and get back up and running (still minus GPS lock, but that's beside the point right now).
Fast forward to today, I was intending to flash a different ROM and messed up big time. I loaded the new ROM onto my storage, then powered the phone on into the bootloader. When I tried flashing the new ROM I was given an error (I don't remember specifically what it was, but the flash didn't go through). I then tried wiping data and cache, then tried again. Still didn't work.
Now I'm stuck here with the only the stock recovery mode and the unlocked bootloader as my only options. I'm now working on a different 64-bit Win8 laptop and for the life of me can't even get ADB properly setup where a command prompt "adb devices" command shows that my phone is being recognized. Any time I try to flash any firmware or ROM from the stock recovery I get the following error:
E:footer is wrong
E:signature verification failed
Aborting installation
I'm totally stuck and have no clue what to do. I can't even flash back to the previous Venom ROM I had installed before today's wipe... Can anybody help???
FWIW, my bootloader screen currently shows this info:
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.19.0.0000
RARIO-1.12.20.1211
OpenDSP-v47.2.2-00564-M8974_FO.1024
OS-4.17.605.5 (4.17.605.5)
eMMC-boot 2048MB
Feb 3 2015,21:50:28.290
trevorparsons said:
I think I've done messed up now...
I've been having a lot of issues with my HTC One M8 (Verizon) (rooted, s-off) phone since the screen was replaced. Mainly, my GPS signal completely stopped working. Anyway, that has led me flashing various ROMS, update.zip files, and 0p6bimg.zip files. Previously, I was working on a 32-bit Win7 laptop during the first round of nonsense. I'd be able to trace back my steps better but since that laptop is no longer in my possession, along with all the various files I used during the process. During that time, I had pretty much bricked my phone where it was stuck on the red Verizon splash screen indefinitely. Eventually, through much trial and error and internet searching, IRCC I flashed some new FUU and RUU files. Ultimately, I was able to successfully sideload the ViperOneM8_4.3.0_OTA Lollipop ROM and get back up and running (still minus GPS lock, but that's beside the point right now).
Fast forward to today, I was intending to flash a different ROM and messed up big time. I loaded the new ROM onto my storage, then powered the phone on into the bootloader. When I tried flashing the new ROM I was given an error (I don't remember specifically what it was, but the flash didn't go through). I then tried wiping data and cache, then tried again. Still didn't work.
Now I'm stuck here with the only the stock recovery mode and the unlocked bootloader as my only options. I'm now working on a different 64-bit Win8 laptop and for the life of me can't even get ADB properly setup where a command prompt "adb devices" command shows that my phone is being recognized. Any time I try to flash any firmware or ROM from the stock recovery I get the following error:
E:footer is wrong
E:signature verification failed
Aborting installation
I'm totally stuck and have no clue what to do. I can't even flash back to the previous Venom ROM I had installed before today's wipe... Can anybody help???
FWIW, my bootloader screen currently shows this info:
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.19.0.0000
RARIO-1.12.20.1211
OpenDSP-v47.2.2-00564-M8974_FO.1024
OS-4.17.605.5 (4.17.605.5)
eMMC-boot 2048MB
Feb 3 2015,21:50:28.290
Click to expand...
Click to collapse
You need to flash my ruu from ruu mode in boot loader. Nothing posted on here is going to flash on stock recovery for you. Nothing.
Sent from my HTC6535LVW using Tapatalk
dottat said:
You need to flash my ruu from ruu mode in boot loader.
Can you either point me in the right direction or give some guidance on this pretty please? I don't remember how I did this the first time around.
Click to expand...
Click to collapse
trevorparsons said:
dottat said:
You need to flash my ruu from ruu mode in boot loader.
Can you either point me in the right direction or give some guidance on this pretty please? I don't remember how I did this the first time around.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3047103
EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(tweaks zip)(newest)
If you are still stuck tomorrow I can help you remotely using team viewer
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
dottat said:
trevorparsons said:
http://forum.xda-developers.com/showthread.php?t=3047103
EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(tweaks zip)(newest)
If you are still stuck tomorrow I can help you remotely using team viewer
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Yesssss!! That got me back up and running back to Android 4.4.2 (along with HTC Sense 6.0). Might be jumping the gun but it also looks like my GPS is able to lock on now too!ust
But I think I overlooked the custom recovery part. I'm not clear on when I flash this portion:
RUU Mode TWRP 2.8.6.0 TWRP that will flash while in RUU mode
https://www.androidfilehost.com/?fid=96042739161893174
md5 5fb9035b4f860487a24b357b59edb18f
Click to expand...
Click to collapse
I tried to install TWRP through the Goole Play app TWRP Manager [Root] which prompted installation of BusyBox and a few other features. Once I tried to reboot into recovery mode I got the red triangle with exclamation point that doing volume_up + power brought me into the stock recovery, which of course failed at flashing anything. At that point I went to reboot back to normal and it then hung up forever on the white HTC splash screen, this time with the red text at the bottom "This build is for dev purposes only. Do not distribute out of HTC..."
Gonna reflash the RUU and get back to where I was for now.
UPDATE: Reflashed the RUU, now back to Android 4.4.2 with working GPS and wifi. Still not so sure about getting a custom recovery going though.
I still haven't figured out how to get ADB commands to work yet, so this part (if I understand it correctly) I'm still SOL on:
Optional If you wish to flash a custom recovery before leaving RUU mode you can. This is helpful if you have relocked for any reason as you CAN flash a recovery using this method while locked (since s-off). Download the ruuM8TWRP_2_8_5.zip below and place it in your working fastboot/adb directory. Once in place, issue the following command.
fastboot flash zip ruuM8_TWRP_2_8_5L.zip
Click to expand...
Click to collapse
Otherwise, I downloaded Flashify from the Google Play and tried first flashing TWRP. Downloaded and installed just fine seemingly, but then when I tried to reboot to recovery I got the white screen with the green HTC logo in the middle along with the purple text at the top that reads "Loading (or booting?) into recovery..." but it just hangs. Went back to Flashify and tried CWM. Also downloaded and installed fine, but this time trying to reboot into recovery it'd show that same white screen only for a second and then go right back to the bootloader. Back in Flashify, tried the third option, Philz, and it wouldn't even download ("something went wrong, try again later").
Obviously I'm in need of getting a custom recovery on there, but once that's done I'd also like to update to Digitalhigh GPE. Once I do have a custom recovery working again, would I be okay to go ahead and go through the process linked below?
http://forum.xda-developers.com/showthread.php?t=2716306
And FWIW, my bootloader screen now has this info:
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000 --- Used to be 3.19.0.0000
RARIO-0.89.20.0321 --- Used to be 1.12.20.1211
OpenDSP-v38.2.2-00542-M8974.0311 --- Used to be v47.2.2-00564-M8974_FO.1024
OS-1.55.605.2 --- Used to be 4.17.605.5 (4.17.605.5)
eMMC-boot 2048MB
Apr 1 2014,00:26:53:290 --- Used to be Feb 3 2015,21:50:28.290
Click to expand...
Click to collapse
trevorparsons said:
dottat said:
Yesssss!! That got me back up and running back to Android 4.4.2 (along with HTC Sense 6.0). Might be jumping the gun but it also looks like my GPS is able to lock on now too!ust
But I think I overlooked the custom recovery part. I'm not clear on when I flash this portion:
I tried to install TWRP through the Goole Play app TWRP Manager [Root] which prompted installation of BusyBox and a few other features. Once I tried to reboot into recovery mode I got the red triangle with exclamation point that doing volume_up + power brought me into the stock recovery, which of course failed at flashing anything. At that point I went to reboot back to normal and it then hung up forever on the white HTC splash screen, this time with the red text at the bottom "This build is for dev purposes only. Do not distribute out of HTC..."
Gonna reflash the RUU and get back to where I was for now.
UPDATE: Reflashed the RUU, now back to Android 4.4.2 with working GPS and wifi. Still not so sure about getting a custom recovery going though.
I still haven't figured out how to get ADB commands to work yet, so this part (if I understand it correctly) I'm still SOL on:
Otherwise, I downloaded Flashify from the Google Play and tried first flashing TWRP. Downloaded and installed just fine seemingly, but then when I tried to reboot to recovery I got the white screen with the green HTC logo in the middle along with the purple text at the top that reads "Loading (or booting?) into recovery..." but it just hangs. Went back to Flashify and tried CWM. Also downloaded and installed fine, but this time trying to reboot into recovery it'd show that same white screen only for a second and then go right back to the bootloader. Back in Flashify, tried the third option, Philz, and it wouldn't even download ("something went wrong, try again later").
Obviously I'm in need of getting a custom recovery on there, but once that's done I'd also like to update to Digitalhigh GPE. Once I do have a custom recovery working again, would I be okay to go ahead and go through the process linked below?
http://forum.xda-developers.com/showthread.php?t=2716306
And FWIW, my bootloader screen now has this info:
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000 --- Used to be 3.19.0.0000
RARIO-0.89.20.0321 --- Used to be 1.12.20.1211
OpenDSP-v38.2.2-00542-M8974.0311 --- Used to be v47.2.2-00564-M8974_FO.1024
OS-1.55.605.2 --- Used to be 4.17.605.5 (4.17.605.5)
eMMC-boot 2048MB
Apr 1 2014,00:26:53:290 --- Used to be Feb 3 2015,21:50:28.290
Click to expand...
Click to collapse
I am not sure how....but you downloaded my older ruu. Use the one in the link to flash. There's also instructions for twrp in there as well.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse