Hi
Please can anyone help please?
Got a HTC One M8 on o2. I installed a custom rom (Viper One) and used it fine for over a year.
I've since changed to a S6 edge and wanted to revert my old phone back to stock rom unrooted.
In doing so I messed up!!!
I'm now stuck with a handset, everything wiped (including the operating system and backups)
I have TWRP recovery and need to re-install stock rom.
Can anyone help?
Thank you
This section is absolutely filled with the same question.
Have a GOOD read here
http://forum.xda-developers.com/showthread.php?t=3086860
Ah right sorry, thanks... Will check it out
bah77 said:
I'm now stuck with a handset, everything wiped (including the operating system and backups)
Click to expand...
Click to collapse
If I'm understanding you correctly, you wiped the OS, not realizing it would cause your phone to be without . . . an operating system?
NO, the operating was wiped by accident
bah77 said:
NO, the operating was wiped by accident
Click to expand...
Click to collapse
Well the easiest way without going through any hassle to fix your phone and make it Stock/Like Brand New is to run a RUU.
I will explain how to do this process with a PC and you should be good to go :good:
1. Download HTC drivers for your PC if you haven't already Here, install and uninstall HTC Sync Manager while KEEPING "HTC Driver Installer".
2. Download the RUU that best matches your phone Here, you can possibly find a O2 RUU on xda but I did not find one my self for you unfortunately, otherwise if your phone is a GSM variant phone you can flash the international RUU from Here (Instructions would be different in this case)
3. Get your phone into bootloader by TWRP or if your phone is off then hold down VOL DOWN and POWER BUTTON at the same time until HBOOT shows up.
4. Plug your device via USB into the computer and verify that you see "Fastboot USB" on your phone's screen.
5. Run the RUU .exe file, I recommend you "Run as Administrator".
6. Follow the on screen instructions and sit back 10-20 minutes as your phone becomes brand new, do not interupt the process or you could have a permanent phone brick.
bah77 said:
Ah right sorry, thanks... Will check it out
Click to expand...
Click to collapse
Is your problem fixed ? Do you still need a RUU for this ? Or the TWRP backup that you found in that link is good enough ?
Sorry not had time to try yet but hoping to in the next day or two
Thanks for the help guys, will let you know how i get on
bah77 said:
wanted to revert my old phone back to stock rom unrooted.
In doing so I messed up!!!
I'm now stuck with a handset, everything wiped (including the operating system and backups)
I have TWRP recovery and need to re-install stock rom.
Click to expand...
Click to collapse
Seems (from the vague description) that a few things went wrong:
1) You may have been proceeding without the proper knowledge of how to return to stock, and at least somewhat, "making it up" as you went along or "experimenting". This is not the proper way to go about things when modding (or in this case "unmodding") a phone. Stick to specific instructions and guides, as already pointed out the process to return to stock is well documented.
2) No degree of wiping or factory resets is going to restore a stock ROM, if you have a custom ROM installed (if that is what you were trying to do); which is a somewhat common misconception. Also, wiping things without understanding the result is a bad idea. The Wipe options are called "Advanced" for a reason. If you don't understand what it is (or the results of wiping it) than don't do it.
The process to return to working stock has been outlined by others. But if you want more specific help, you will need to do a getvar all and post the output (being sure to delete your IMEI and serial number, as those are personal info) so we can better determine the way forward. But in summary, you have 2 choices:
a) Relock the bootloader and run the proper RUU, of one exists for your CID version.
b) Restore the stock nandroid that corresponds to your CID and main version (firmware), then flash the correct corresponding stock recovery.
Been stuck like this for 40 minutes
bah77 said:
Been stuck like this for 40 minutes
Click to expand...
Click to collapse
What did you do ?
Do you have right RUU ? Can you give the RUU name that you are using ?
I saw you use a ROM.zip .. AFAIK your O2 RUU is an exe file.
You also need USB 2.0 and latest HTC USB Drivers installed.
Do i need to re lock the bootloader first?
Discussion has resumes here:
http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-brick-t3243115
Thread closed.
Related
Hello Everyone,
I am having an issue with my M8.
I decided to try out SkyDragon, give it a shot.
I downloaded the ROM, put it on my SDcard. Flashed Philz 6.25 recovery, did NOT make a nandroid backup (I know i'm an idiot),then proceeded to flash the rom via Philz.
I flashed the Rom, and followed all the instructions, I then rebooted the phone. Still stuck at the bootscreen. I read the Q&A and tried to flash the rom multiples times. Still stuck on the boot screen. I have an unlocked bootloader with S-ON.
I just got this phone a few months ago and I am unable to take it out of this state. Could use some help. Thank you.
Is your firmware up to date? Not sure about Skydragon specifically, but long boot times (along with broken WiFi) is often a symptom of outdated firmware.
Let the phone alone for 10 minutes or so, and see if it eventually boots, and isn't actually "stuck" (but rather just takes a REALLY long time).
To flash a different ROM, adb push it to internal storage, or put in on your SD with a USB card reader connected to your computer. Then boot into recovery and flash.
redpoint73 said:
Is your firmware up to date? Not sure about Skydragon specifically, but long boot times (along with broken WiFi) is often a symptom of outdated firmware.
Let the phone alone for 10 minutes or so, and see if it eventually boots, and isn't actually "stuck" (but rather just takes a REALLY long time).
To flash a different ROM, adb push it to internal storage, or put in on your SD with a USB card reader connected to your computer. Then boot into recovery and flash.
Click to expand...
Click to collapse
Hello,
I've actually tried flashing another ROM "Android HD Revolution" I believe. The phone shows the HTC Screen along with some red text at the bottoms saying "this build is for developer purposes only....". The phone then stays on the HTC screen for ~3mins then reboots and continues to boot loop.
You just need to flash the new firmware that is found in the sky dragon OP.
Easiest way is to use fastboot. Google fastboot firmware m8. Lots of guides out there. It's only a few commands.
Edit: Should have asked if you are s-off. That will make a difference in your ability to flash new firmware.
Sent from my HTC One_M8 using XDA Free mobile app
OLEO34 said:
You just need to flash the new firmware that is found in the sky dragon OP.
Easiest way is to use fastboot. Google fastboot firmware m8. Lots of guides out there. It's only a few commands.
Edit: Should have asked if you are s-off. That will make a difference in your ability to flash new firmware.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Hello Thanks for the reply.
However, I am currently S-ON, I have searched ways to achieve S-OFF but they all require installing a ROM. However, I cannot flash any rom, I will just get the bootloop. If you could advise on a method that would work for my situation, I would be very grateful.
Default-G8way said:
... However, I cannot flash any rom, I will just get the bootloop. If you could advise on a method that would work for my situation, I would be very grateful.
Click to expand...
Click to collapse
Start with fastboot getvar all command in fastboot/bootloader, put the result here (delete serialno and imei no.) .. then we'll see whether is there any stock ROM available for your device.
Default-G8way said:
Hello Everyone,
I am having an issue with my M8.
I decided to try out SkyDragon, give it a shot.
I downloaded the ROM, put it on my SDcard. Flashed Philz 6.25 recovery, did NOT make a nandroid backup (I know i'm an idiot),then proceeded to flash the rom via Philz.
I flashed the Rom, and followed all the instructions, I then rebooted the phone. Still stuck at the bootscreen. I read the Q&A and tried to flash the rom multiples times. Still stuck on the boot screen. I have an unlocked bootloader with S-ON.
I just got this phone a few months ago and I am unable to take it out of this state. Could use some help. Thank you.
Click to expand...
Click to collapse
You needed to make sure you have the latest GPE software, s-off and supper cid... Also you need to know and have ADB/FASTBOOT installed on your PC.. All which can be found throughout all of the various threads.... Right now you soft bricked your device and needed to return to stock... And stay the process over.
lilbigdude1 said:
You needed to make sure you have the latest GPE software, s-off and supper cid... Also you need to know and have ADB/FASTBOOT installed on your PC.. All which can be found throughout all of the various threads.... Right now you soft bricked your device and needed to return to stock... And stay the process over.
Click to expand...
Click to collapse
You don't "need" the latest gpe software. The rom runs fine on the latest sense firmware.
Mr Hofs said:
You don't "need" the latest gpe software. The rom runs fine on the latest sense firmware.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=53838669
So ? Just like i said.....no need for gpe
Issue Resolved!
Hello Everyone.
The issue is resolved. Through many flashes, wipes and commands. Its done. I was able to flash the rom, let the rom sit for ~20mins, and it finally booted up into Lollipop. I now have no wifi. However, I should be able to follow the FAQ to get S-OFF and fix my wifi!. Thanks team. I really appreciate it.
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Webbage said:
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Click to expand...
Click to collapse
You don't provide much information so it's hard to help. So let's start at the bginning: What firmare version are you using? (It's stated in Download Mode in the line with "OS" at the beginning.)
You tried to flash a RUU? Which one? Have there been any error outputs? If yes, which ones? Since you're S-OFF flashing a RUU should not be a problem at all so these outputs are very important if you want any help.
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Webbage said:
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Click to expand...
Click to collapse
As far as I know Sneakyghost doesn't provide any RUUs. Those are only firmware packages that do not contain a rom. So it's no miracle that you're still booting ARHD.
You can download O2 RUUs from here, here or here. Any of the X.XX.206.X files will work since you are S-OFF. Do you have a SD card that is not bigger than 32gb? If yes, format it to fat32, copy one O2 RUU to its root directory and rename that file to "0PJAIMG.zip". If you then boot to Download Mode you will be asked to push the Volume Up button and the RUU will start flashing. If it reboots to system instead of rebooting to Download Mode you will have to power off your phone and boot to Download Mode manually. The RUU will continue then. At the end you will be asked to push the power button so that your phone gets shut down. If you now start your phone you will be back on a stock system.
Be aware that there is no RUU for your current firmware. Since you're S-OFF that doesn't matter but your phone will be downgraded at the end.
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Webbage said:
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Click to expand...
Click to collapse
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Agreed, use the s-off command to change back to "LOCKED" and leave it s-off. Too much of a risk otherwise.
If in the unlikely event they see it, you can play dumb, because a few rare people have gotten s-off phones from the factory and it doesn't prove you did anything.
Flippy498 said:
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Click to expand...
Click to collapse
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Webbage said:
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Click to expand...
Click to collapse
Didn't the RUU flash the corresponding stock recovery?
Flippy498 said:
Didn't the RUU flash the corresponding stock recovery?
Click to expand...
Click to collapse
My bad, I didn't check.
All sorted now, thanks again bud!
Hello,
I am in need of some help.
2 weeks ago i bought the HTC One M9.
A few days ago the update to android 6.0 message popped up.
I have probably tried updating it like 15 times already, but everytime the first part is downloaded, and my phone reboots, after 1/4th of the updating it shows a red triangle with an exclamation point in it.
I have tried wiping the cache, it didn't help.
Honestly i don't have a clue what's wrong, or where i can find out what went wrong, so i would really appriciate all the help i can get.
Example of what happens:
malmgrens [dot] org/bilder/htc_recovery_mode [dot] jpg
A few more details will be helpful:
- what variant do you have (locale & carrier)?
- is your phone modified (ie, custom recovery and/or root)?
In order to take an over-the-air update, the phone must be completely stock. If it is not, you'll need an RUU to restore your phone to stock (be sure to backup your information first). Then you'll be able to take the OTA update.
computerslayer said:
A few more details will be helpful:
- what variant do you have (locale & carrier)?
- is your phone modified (ie, custom recovery and/or root)?
In order to take an over-the-air update, the phone must be completely stock. If it is not, you'll need an RUU to restore your phone to stock (be sure to backup your information first). Then you'll be able to take the OTA update.
Click to expand...
Click to collapse
Hey, thanks so much for your reply
I am pretty sure i got the dutch version, it might be belgium.
The carrier is vodafone.
I am pretty sure its not rooted etc, since i didn´t do anything with it.
What does stock and RUU mean?(I am a total noob with this.)
appie.0606 said:
Hey, thanks so much for your reply
I am pretty sure i got the dutch version, it might be belgium.
The carrier is vodafone.
I am pretty sure its not rooted etc, since i didn´t do anything with it.
What does stock and RUU mean?(I am a total noob with this.)
Click to expand...
Click to collapse
Hi there,
To clarify - your phone boots to its current software with no problem, right? If so, it would be a wise thing for you to determine your MID (model ID) and CID (carrier ID). There are a number of guides - Google is your friend. I recommend looking up ADB installation, your OS (Mac, Windows, Linux) and going from there.
Once you know your MID & CID, we can help you find out what firmware is available for you.
To learn about RUUs, VenomROM has a great page that explains about what they are and how to use them.
Peace,
Computerslayer
computerslayer said:
Hi there,
To clarify - your phone boots to its current software with no problem, right? If so, it would be a wise thing for you to determine your MID (model ID) and CID (carrier ID). There are a number of guides - Google is your friend. I recommend looking up ADB installation, your OS (Mac, Windows, Linux) and going from there.
Once you know your MID & CID, we can help you find out what firmware is available for you.
Peace,
Computerslayer
Click to expand...
Click to collapse
Yes my phone boots to current software without any problems right now.
Some info i found:
CID: VODAPE17
MID did not show for some reason. I tried multiple ways using adb shell and fastboot, but shell doesnt show anything and fastboot gets stuck at waiting for device.
Is finding my MID nessecary to fix this update problem? If so how can i find it?
Power of your M9
Power on & press at the same time to enter in the bootloader, volume -
on the top of the screen, is it writed locked or unlocked?
You can see more information in download mode...
bzhmobile said:
Power of your M9
Power on & press at the same time to enter in the bootloader, volume -
on the top of the screen, is it writed locked or unlocked?
You can see more information in download mode...
Click to expand...
Click to collapse
Hey thanks for your reply.
It says unlocked. Is that normal or could it be an/the issue?
If you are unlocked, it's related to your issue.
You have to flash a RUU to be "stock" and ready for the OTA...
bzhmobile said:
If you are unlocked, it's related to your issue.
You have to flash a RUU to be "stock" and ready for the OTA...
Click to expand...
Click to collapse
Alright, so if i understand correctly i can flash a RUU (whatever it is lol) without having to backup without doing a clean install. The phone wont wipe my data?
Would this guide be what you mean?
how-to-flash-ruu-firmware-htc-one-m9/
from naldotech
com
If you flash an RUU....your device will be wiped clean....as it came out of the box...
Then you can OTA on a clean....stock rom....g
The Thread is a good one.
More explication of what is needed in post2 or post 3 of TWRP thread (about Google's new limitation for the OTA).
Beware flashing a RUU will wipe everything, don't forget to backup all you take care...
Alright, I will start at the beginning. I plugged my phone into my PC. HTC Sync manager popped up and told me there was an update for my device. So I was excited knowing it was the Marshmallow update. Everything was going smooth until my cable disconnected while it was installing. It failed and my phone was doing nothing. So like an idiot, I rebooted it.. Now my phone will not go past the HTC logo on boot. I tried wiping the cache partition from Android Recovery but no luck. I'm not really sure what to do at this point. My phone was not rooted, and it is *Locked*. I just want my phone back.. Any help would be so much appreciated, because I'm pretty unsure of what to do.
By the way I am not worried about saving what is on the phone. It's the HTC One M8 (Verizon).
Hi,
I'm a beginner here myself but based on what I read lately it might be possible to go into fastboot mode and flash a Lollipop RUU file.
You'll need a couple of tools on your PC (adb and fastboot) and a step by step guide, both easy to find with a quick search. The harder part is to locate the appropriate file to flash, at least I have trouble with that piece...
Good luck !
Gnondpom said:
it might be possible to go into fastboot mode and flash a Lollipop RUU file.
Click to expand...
Click to collapse
Depends on how far it got in the update. If enough of the MM update installed, LP may constitute a "downgrade", which is not allowed unless you have s-off. In that case, OP may need to use the Marshmallow RUU. But I agree, that RUU is the best bet. RUU will wipe the phone, but I think we're past the point of trying to recovery data at this point, anyway.
TO the OP, what does it say for OS number on the bootloader screen?
Presumably, the phone is s-on, as it sounds like it was never modified?
The Verizon RUUs are here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Another option to flashing the RUU using fastboot, is to put the RUU zip on an SD card (if you have one) and flash. Instructions are in the link (Option 2). This is probably easiest of the options (again, assuming you have an SD card), especially if you don't have fastboot setup, and aren't familiar with it).
redpoint73 said:
Depends on how far it got in the update. If enough of the MM update installed, LP may constitute a "downgrade", which is not allowed unless you have s-off. In that case, OP may need to use the Marshmallow RUU. But I agree, that RUU is the best bet. RUU will wipe the phone, but I think we're past the point of trying to recovery data at this point, anyway.
TO the OP, what does it say for OS number on the bootloader screen?
Presumably, the phone is s-on, as it sounds like it was never modified?
The Verizon RUUs are here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Another option to flashing the RUU using fastboot, is to put the RUU zip on an SD card (if you have one) and flash. Instructions are in the link (Option 2). This is probably easiest of the options (again, assuming you have an SD card), especially if you don't have fastboot setup, and aren't familiar with it).
Click to expand...
Click to collapse
OS # is (6.21.605.3) The update was just about finished before it disconnected. So I believe you are correct. I don't mind data loss, would rather just get the device functional again.
It is S-ON, it was never modified in any way. I will check out the links and see what I can do. Thank you for all the info!:good:
Hi guys,
Got a phone a need to revive. I received unusable. Mother gave it to my sisters friend and she said it doesnt work. I now see why cause he was trying to mod it.
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
So currently "fastboot getvars" reports back all the info. It's showing version-main 6.13.206.5 and I just want official O2 stock so can use the phone. Ideally sim unlocked but could hassle O2 for that later since it was my mother's contract.
Basically just want to get a working recovery image on and then flash stock. CID is 02__001
Any suggestion to revive this welcomed, please.
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
ckpv5 said:
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
Click to expand...
Click to collapse
No, I cannot get into it. When I select HBOOT, then select recovery it just shows white screen, ANDROID and then back to the menu. TWRP no longer works. That's what I'm trying to fix or put on a stock recovery image and then stock OS/firmware.
Just wondering if I need to UNLOCK it again and also do I need USB debug on. I cannot boot into OS so unable to set USB debug.
To UNLOCK bootloader can that be done if you can only get into bootloader menu? S-ON is enabled but not 100% that will stop recovering it? That's just for signed rom/firmware and I just need something stock.
You don't need usb debugging on to unlock the bootloader as it is done on fastboot mode (bootloader).
First I suggest you install the O2 firmware only then see whether you can boot to OS (assuming the OS is still stock base)
Second, re unlock bootloader with unlock_code.bin that you can get from htcdev.com, install twrp 3.x and restore the stock backup and relock bootloader and reflash firmware. This will get your device to fully stock.
So far, I don't see any RUU for your device version that you can get for free, only paid site has it.
Tainted said:
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
Click to expand...
Click to collapse
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
redpoint73 said:
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
Click to expand...
Click to collapse
ok, well made some progress.
unlocked the bootloader the official way. Very quick which I was surprised.
This then repoened up the recovery menu working.
then used fastboot to install latest twrp
then installed S.Team-JW-7.5.0.zip !!!
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Wondering if end of the line. Any suggestions? I assume need to get into TWRP and flash stock update from ckpv5.
Must say thanks for replies guys. ckpv5 you done some good work on here.
Tainted said:
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Click to expand...
Click to collapse
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
redpoint73 said:
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
Click to expand...
Click to collapse
Hi there,
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
The ROM install finished, battery was at about 80% and everything looked good and I let it reboot the phone. And then it went dead. Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes. My S7 edge shows up. It flash an orage dot twice, so appears to be a in loop.
I charged the phoned and no luck with any of the power+ vol +/- keys. No response from any of those? I let the phone sit till flat and no orange light and then charged it today and still nothing. Not sure if it's a bad battery but it was up at 83% showing in the TWRP menu and working plugged or unplugged.
It's become a challenge now to make it work, I havent had to mod phones since my HTC One which got heavily modded and then back to stock. I stopped doing that after modding every phone I had since HTC Desire Android 2.3. So been about 4 years since doing all this again. Never had one that was totally bricked.
Tainted said:
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
Click to expand...
Click to collapse
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
Tainted said:
Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes.
Click to expand...
Click to collapse
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
redpoint73 said:
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
Click to expand...
Click to collapse
Cheers for that. Not getting much except for the 2 brief flashes of orange light.
Any chance the battery is totally messed and this is the problem?
Tainted said:
Any chance the battery is totally messed and this is the problem?
Click to expand...
Click to collapse
It's possible. Or it might be something else like motherboard or emmc. It's impossible to say for sure.