Related
i dont know exactly whats happened here, but i've tried to get my WFS sorted with a different rom than the carriers bloated version.
what i've done is updated hboot to 1.08.0099 and unlocked the boot loader sucessfully (hboot has *** UNLOCKED *** across the top; i used the HTCDEV.com process).
i believe i've got permanent root too.
when i attempt to flash CWM (via PG76IMG.zip), it appears to flash ok, but if i reboot the phone and try to access recovery, it just gets stuck on a white HTC screen.
i've redownloaded the CWM file to see if it's a corrupt download, but still the same problem.
CWM isnt a big issue, although it is nice to have.
however i also am unable to flash another rom either via the PG76IMG.zip SD method, or RUU.
i beleive i've done everything right, and i'm not entirely new to unlocking/rooting devices; only did my HTC Desire last week so the general process is still new in my head.
If your rooted install rom manager and flash recovery from there.
I had problems installing cwm from sd, so used the tool from here http://forum.xda-developers.com/showthread.php?t=1431969
previously was this one mediafire.com/?b0bsb4ms4lo714b
just plug the usb in sync and folow the instructions
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Swazi Samurai said:
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Click to expand...
Click to collapse
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
S1L3nTShaDoWz said:
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
Click to expand...
Click to collapse
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Swazi Samurai said:
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Click to expand...
Click to collapse
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
S1L3nTShaDoWz said:
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
Click to expand...
Click to collapse
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Swazi Samurai said:
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Click to expand...
Click to collapse
I formatted my SD card and was finally able to transfer the RUU. The bootloader begins to run the 0P6BIMG file, but it fails right after it starts parsing. I tried running it several times and the results were the same.
I really wish I could get ADB to recognize my phone so I can flash a custom recovery... When I plug my phone into a USB port, my computer makes a noise, the phone says "USB" next to Fastboot, and HTC Sync Manager begins to load. When HTC Sync Manager comes up, it says "HTC Sync Manager couldn't connect to your phone." Windows Device Manager also does not have anything listed for an Android device.
I've noticed when the phone is not powered on and simply charging from the USB port, an "HTC MTP Device" driver tries to install, but fails. Could this be the problem? I've tried plugging the phone into 3 different computers and they all get the MTP failure.
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not specifically trying to install the GPE RUU at the moment. I had the stock GSM recovery installed based on my original CID and I'm trying to load the associated RUU.
I originally loaded GPE 4.4.3 with TWRP and downloaded the 4.4.4 update OTA from Google. Before restarting my phone and installing the update, I flashed the stock GSM recovery for CID CWS_001. This may have been what caused the issue initially when the phone tried to apply the update if it was looking for a GPE recovery.
I know I cannot install the GPE RUU because I'm S-ON and ADB does not recognize my device so I cannot change the MID or CID. At this point, I'm really just trying to get back to stock so I can start fresh.
Is it possible that when the 4.4.4 update tried to run, it associated my recovery with GPE and now that's why it will not install the stock RUU due to a mismatch? I'm really just guessing at this point.
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
I'll give that a try and report back. Thanks for the input.
3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
You are the freakin man!!! I edited the template from the post you suggested, added my MID/CID, and packaged it with the TWRP image. Booted right from the SD and I now have custom recovery! I wish I could buy you a beer!
No problem mate. Glad I could help. :thumbup::thumbup::beer:
Sent from my HTC One_M8 using XDA Free mobile app
So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help
Hi,
Did you try to reflash your recovery and try to install another rom like ViperOne M8? Or if you want i can send you the stock ROM Android 6.0
Laurens54321 said:
So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help
Click to expand...
Click to collapse
You seem to be going about things rather haphazardly:
1) Not sure exactly what "some OTAs" refers to. But there is typically only one OTA that will properly work. That being the one that is for your CID (carrier version) and for the next software version (can't skip any).
2) Along the same lines, you can't just flash any RUU. It has to be for your CID and MID (Error 130 usually means wrong MID), and equal or greater version number than main version on the phone (no "downgrading" unless you have s-off).
3) "messing around with stuff that didnt work" doesn't tell us anything about how you got to the current condition. You need to be specific and detailed, if you want us to be able to tell what you did, and how to recovery.
4) You can't unroot and OTA, it has to be a stock (never rooted) ROM and stock recovery.
5) boot.img in itself probably won't help your situation. And signature verify fail usually means you tried to flash without the bootloader unlocked (which won't work).
Are you S-OFF? If so, this works;
1) Download 0P6BIMG.zip. You'll have to Google
"dottat @ XDA M8 RUU" to get the file as I haven't
made at least ten posts here and can't post links yet.
2) Place 0P6BIMG.zip on an SD card formatted fat32 ONLY.
3) Boot your phone, allow HBOOT to recognize 0P6BIMG.zip
and follow the prompts.
RESULT: This will land you on STOCK kitkat 1.55.605.2
pre-rooted with stock recovery.
----------------------------------------------------------------
CREDIT: dottat @ XDA
Hello guys I have an M9 unlocked with s-off, android 7.0 with twrp 2.8.5.0 and bootloader unlocked. When I tried to flash SuperSU-v2.82-20170528234214.zip my phone won't pass the HTC logo on white screen. So I tried to sideload SuperSU-v2.82-20170528234214-TEST-1.zip because I read it was for bootloop accidents but my pc (yes I have HTC drivers) says there's not attached device in prompt command, so I couldn't try dirty flashing with ViperOne too. Also my SD card can't be read by pc cuz the card reader is old XP. As final solution I tried RUU but it says phone is not linked to pc or that it has low battery but it's not true. What I have to do????
EDIT: I solved this problem by flashing LeeDroid but in some way I lost IMEI and baseband, so I'm trying to reflash stock with RUU 4.30.617.12 and see what happens...
EDIT: I successfully installed nougat and TeamHelix Thermal mod. Could you recommend me a good ROM on Nougat?
This thread has been created for users who are experiencing a hard brick, soft brick, boot loop, or random shutdown on their HTC 10. Feel free to ask your question(s) here.
Going forward, new threads created regarding the topics listed above will be CLOSED by the moderating staff. Please remember to follow the XDA forum rules when posting.
Cheers,
Magnum_Enforcer
FSM
Well, I've pretty much managed to screw up my HTC 10. I'm on the latest 3.16.401.2 WWE, S-ON, with the bootloader relocked and stock recovery. I can access the download mode, the bootloader and the stock recovery, but I can't unlock the bootloader since I can't active the OEM unlock option. The phone doesn't boot, it's stuck in a bootloop at the white HTC logo.
Using the OTA available for WWE gives me the Status 7 fail error. Is there anything else I can do, besides from waiting for the Oreo WWE RUU?
Thanks in advance.
TheMadKing said:
Well, I've pretty much managed to screw up my HTC 10. I'm on the latest 3.16.401.2 WWE, S-ON, with the bootloader relocked and stock recovery. I can access the download mode, the bootloader and the stock recovery, but I can't unlock the bootloader since I can't active the OEM unlock option. The phone doesn't boot, it's stuck in a bootloop at the white HTC logo.
Using the OTA available for WWE gives me the Status 7 fail error. Is there anything else I can do, besides from waiting for the Oreo WWE RUU?
Thanks in advance.
Click to expand...
Click to collapse
I won't even ask how or why....
But yes you could S-off or wait for an RUU to magically appear.
Those are the two options.
santod040 said:
I won't even ask how or why....
But yes you could S-off or wait for an RUU to magically appear.
Those are the two options.
Click to expand...
Click to collapse
It's pretty complicated, but long story short, I was stupid.
I can't S-Off without being able to boot the phone, so well, I'll probably just wait for a RUU.
HTC 10 boot loop
Hello guys,
my wife yesterday tried to update OTA (our htc 10 are completely stock) to OREO from Nougat 2.41.401.41. Something went wrong and it's stuck in a boot loop. I can get in bootloader and tried to install the ota, which I downloaded, manually from SD card, but after verifying it says "error: partition has unexpected content". Is there a way to get the phone back working even with data loss? Thanks really for the help, the phone has never been modified, I am getting crazy reading the forums but I am a total noob ?
i have seen i need a ruu, possibly zip since I can't boot and activate USB debug. Can someone please share a run.zip link at least equal to 2.41.401.41 (European)? Thank you very much
I have the same issue, HTC 10 in a boot loop after applying the OTA Oreo update. I'm able to get into bootloaders and such, but i need the data thats on the phone... Allready tried taking out the SIM and SD-card. Does anyone know if this can be fixed?
Same problem here!
After Reading what the rest of you lot mentioned here, i have the exact same problems! Installed the update from Nougat to Oreo, and the phone went into bootloader! I was stupid enough to delete most of it through TWRP, and even dumber to RELOCK it so that TWRP is out of the Picture. Download mode appears, but the recovery just brings me back to bootloader. Oh yes, and the OS is missing.
and fastboot / adb wont recognize the HTC Connected to the PC anymore.. Guess this is a total Brick? should i send it back since i have a warranty? Will they be able to fix this?
I too was stupid and relocked it while reverting to stock. At this point I had also flashed the stock recovery and recovered to what turned out to be a non-functional backup. (Stuck in boot-loop)
Thankfully Fastboot did however still work while in download mode, and I was able to unlock it again by flashing the same unlock_token.bin that I have kept since I unlocked it the first time, slapped in twrp again and I was good for another go.
M8 can you help out linking some procedure for a noob like me? Should I use a ruu? I am completely stock
I'm no expert in this my self just FYI, but installing a RUU is usually a straight forward process.
You need to download a ruu for your particular CID (Depens on where the phone was sold and what -if any- carrier the phone is locked to.)
I have an european unlocked one so the RUU I used was this: https://androidfilehost.com/?fid=817550096634797504
You can find more in this thread: https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Download the ruu (just short of 2GB in size) , rename it to 2PS6IMG.zip and put it in the root of an SD-card and insert it into the phone.
Reboot it into download mode by holding power+volume down until the grey HTC logo appears.
It should now detect the zip file in the sd-card and ask you to install it. Press volume up to confirm.
This will re-install everything (System image, recovery, firmware etc) all existing data gets destroyed.
Worked like a charm for me, and was able to do a Oreo OTA right away after the first boot.
Thanks a lot for your help, I'll give you a feedback asap.
varg300 said:
I'm no expert in this my self just FYI, but installing a RUU is usually a straight forward process.
You need to download a ruu for your particular CID (Depens on where the phone was sold and what -if any- carrier the phone is locked to.)
I have an european unlocked one so the RUU I used was this: https://androidfilehost.com/?fid=817550096634797504
You can find more in this thread: https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Download the ruu (just short of 2GB in size) , rename it to 2PS6IMG.zip and put it in the root of an SD-card and insert it into the phone.
Reboot it into download mode by holding power+volume down until the grey HTC logo appears.
It should now detect the zip file in the sd-card and ask you to install it. Press volume up to confirm.
This will re-install everything (System image, recovery, firmware etc) all existing data gets destroyed.
Worked like a charm for me, and was able to do a Oreo OTA right away after the first boot.
Click to expand...
Click to collapse
Everything worked smoothly! Thank you so much!
Hi,
I have HTC_10, Unlocked, S-ON, J_15, 1.90.401.5
Had custom ROM nougat, later flash with stock MM firmware (EU 401), after my phone base-band and IMEI gone and no sim card now.
any help please ???
husnainrasheed said:
Hi,
I have HTC_10, Unlocked, S-ON, J_15, 1.90.401.5
Had custom ROM nougat, later flash with stock MM firmware (EU 401), after my phone base-band and IMEI gone and no sim card now.
any help please ???
Click to expand...
Click to collapse
Flash the ruu that is posted 1 post above yours.
IMEI not showing
Mr Hofs said:
Flash the ruu that is posted 1 post above yours.
Click to expand...
Click to collapse
Thanks for reply, I flashed with this RUU, Oreo update showing now but still no IMEI and Baseband..
Any solution to fix this IMEI or base band issue ??
husnainrasheed said:
Thanks for reply, I flashed with this RUU, Oreo update showing now but still no IMEI and Baseband..
Any solution to fix this IMEI or base band issue ??
Click to expand...
Click to collapse
Take the OTA. Did you flash a Oreo ROM while on nougat firmware? If so updating to Oreo will fix the problem.
Thanks Alot
yldlj said:
Take the OTA. Did you flash a Oreo ROM while on nougat firmware? If so updating to Oreo will fix the problem.
Click to expand...
Click to collapse
:good::good:
I updated to Oreo and now I am back on track.
everything is back to normal, IMEI and baseband as well working SIM.
thanks alot man ..
:good:
I have an Indian HTC 10 (SD 820) full stock, no modifications. One day the phone froze and i restarted it and from that day it hasn't booted up. The htc logo shows up while it vibrates, then again the same screen. Stuck in a bootloop. When i get to bootloader and boot to recovery, the grey htc logo comes for 1 second and then it goes back to the original boot animation and it loops again until the phone dies. Whenever i plug my phone to the charger, it immediately gets stuck into the boot loop. Please help me !! Any fix please !
budgati said:
I have an Indian HTC 10 (SD 820) full stock, no modifications. One day the phone froze and i restarted it and from that day it hasn't booted up. The htc logo shows up while it vibrates, then again the same screen. Stuck in a bootloop. When i get to bootloader and boot to recovery, the grey htc logo comes for 1 second and then it goes back to the original boot animation and it loops again until the phone dies. Whenever i plug my phone to the charger, it immediately gets stuck into the boot loop. Please help me !! Any fix please !
Click to expand...
Click to collapse
Hold the power button and the volume down button to reboot to download mode. From there you can flash an RUU.zip to fix it.
What is needed to direct you to the proper RUU.zip to download and flash is for you to boot to download mode and post here what it says next to "OS"