I was running Twisted's 4.0.4 build ever since release, all the way up to his 1/13 build(which was plagued with a lot of issues) but I attributed my issues to that build exclusively... as it turns out, it isn't the case at all.
A few days after clean flashing the 1/13 build with 4ext recovery, all partitions properly formatted to ext4 I started experiencing several issues with my bolt. First, occasionally I would plug it in to charge and it would reboot, show the boot SPLASH a couple of times and eventually boot into the OS. Again, I thought it was the build, but then when I tried to boot into recovery I noticed I couldn't. The vol+power didn't work and I couldn't reboot into recovery from the OS. It would just boot loop to splash a couple of times and (sometimes longer than others) boot loop until it booted up. Eventually I tried reflashing recovery, assuming that somehow my recovery partition wasn't working properly. A las, I was able to boot into recovery after recovery reflash, then I loaded the 12/24 build but the same behavior occured. At this point, I assumed I'm going back to stock and I don't care all that much since I was going to be upgrading. I took the .19 Gingerberad OTA PG05IMG.zip and copied it over to my SD card. Which was quite the chore since at this point it was taking longer and longer to actually get to the OS and I had no other means to copy to a microSD card.
Now here I am, I flashed the PG05IMG of the .19 Gingerbread and it still behaves the same way! Would it have something to do with Revolutionary HBOOT? I'm stumped, but at this point I can't really get to the OS or recovery. I did get to the OS once, but when I tried to plug it in to send over ADB commands/files it rebooted!
I was going to sell it rather cheap, but now I just might give it to a dev. Any help would be greatly appreciated!
...random fact, I put on the newest ICS radios from the OTA but other than that I don't know
Maybe pull out your SD card and try and boot up the phone. How old is your battery? Did you flash just the ota radios or did you flash the update with the new boot? Sounds almost like your min clock speed is to low?
Sent from my Nexus 7 using Tapatalk HD
Dark Jedi said:
Maybe pull out your SD card and try and boot up the phone. How old is your battery? Did you flash just the ota radios or did you flash the update with the new boot? Sounds almost like your min clock speed is to low?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I tried without SD card, same issue. Battery is practically brand new. OTA radios only, I didn't adjust my clock speeds. I tried to go back to .19 complete package and same thing.
Sent from my SCH-I535 using Tapatalk 2
Bump?
Sent from my SCH-I535 using Tapatalk 2
Did you do a full wipe data,system, both caches? I have heard 4ext seems to be having issues with the ota based ics roms. Maybe try flashing teamwin to just see if that's your issue.
Sent from my ADR6425LVW using Tapatalk 2
Related
I was running A05PTH3ORY V1.4X and wanted to put on a new kernel to see if I could get better batter life. I flashed Tiamat's kernel and everything seemed to work fine for a little while while it was sitting on my desk. About 30 minutes later I reached over to unlock it and nothing, it had shut off.
I go to turn it on and I get a boot loop on the white HTC screen. I get into recovery to restore a backup and it get a minute into the restore and automatically reboots. So I try again but wipe data/cache first, same thing. So I try to just install a new ROM, same thing, reboots.
Don't know where to go from here....any help?
Can I rename a ROM to PG05IMG.zip and flash it through the bootloader????
schmaltzy said:
Can I rename a ROM to PG05IMG.zip and flash it through the bootloader????
Click to expand...
Click to collapse
No
tbolt ^_^_^
Same thing happened to me. You have to find the correct RUU to flash in bootloader. I flashed the stock RUU. Although I lost root, phone was fine again.
schmaltzy said:
I was running A05PTH3ORY V1.4X and wanted to put on a new kernel to see if I could get better batter life. I flashed Tiamat's kernel and everything seemed to work fine for a little while while it was sitting on my desk. About 30 minutes later I reached over to unlock it and nothing, it had shut off.
I go to turn it on and I get a boot loop on the white HTC screen. I get into recovery to restore a backup and it get a minute into the restore and automatically reboots. So I try again but wipe data/cache first, same thing. So I try to just install a new ROM, same thing, reboots.
Don't know where to go from here....any help?
Click to expand...
Click to collapse
Another member had the same problem as you and what eventually fixed it was a factory RUU run from the computer. You would then need to root the phone again. The other fix to try first is a different Micro SD card. Apparently if the Micro SD is bad or corrupted, when the phone is trying to restore the backup it encounters an error and reboots. If you don't have another Micro SD card then you can try formatting the current one. Formatting the Micro SD card will erase everything, I'm sure you know that. If you want to run a factory RUU from your computer this site has a couple different RUU's to choose from http://dougpiston.com/ThunderBolt/RUU/ Download one of the .exe RUU's not the .zip RUU's. Once you download it to your computer run it from your computer with the phone plugged in and turned on. Running the RUU is a last resort because you'll have to root your phone again, but if you've exhausted all your other options then go for it.
EEdaesung said:
No
tbolt ^_^_^
Click to expand...
Click to collapse
Tbolt! Thanks for the help on the IRC! It worked!
I flashed the MR1 RUU and it got me in. So all is well!
Question though....why? I can understand a boot loop because of my phone not meshing well with the kernel, but why wouldn't it let CWR work correctly?
schmaltzy said:
Tbolt! Thanks for the help on the IRC! It worked!
I flashed the MR1 RUU and it got me in. So all is well!
Question though....why? I can understand a boot loop because of my phone not meshing well with the kernel, but why wouldn't it let CWR work correctly?
Click to expand...
Click to collapse
Had the same problem and cure. I suspected a fubar clockwork only because I was running an older version.
courtesy of my rooted bolt
ILMF said:
Had the same problem and cure. I suspected a fubar clockwork only because I was running an older version.
courtesy of my rooted bolt
Click to expand...
Click to collapse
HMMM.....I was running the most up to date CWR.
I could really use some help here guys. Last night I flashed a new ROM - ThunderShed-v1.6_CM7.2-tbolt using Rom Manager/ClockworkMod (had been using CM7.1 without issue). I also updated the kernal to imoseyon_leanKernel_v6.2.1AOSP (didn't change ANY kernal settings) after reboot and install gapps. Everything seemed fine, however after powering off and back on again. I am now stuck in a boot loop. HTC screen phone vibrates, black screen, then HTC screen. I then attempted to boot into HBoot screen which I was able to do. Clicked on recovery and attempted to get into clockwork mod and restore the backup I'd created. Phone just reboots don't get to recovery and continuous HTC Screen black HTC Screen. This isn't my first rodeo with flashing roms (no expert by any stretch, but I'm pretty familiar with the process). Somehow I've screwed something up badly. I did attempt factory reset. I've also tried to downgrade to an older RUU although the RUU is loaded in HBOOT and seems to install (other than Bootloader is bypassed, due I believe because of Revolutionary ERROR - Can not roll back hboot version). Everything else Boot, recovery, system, splash1, userdata, etc all appear to update and show oK. After rebooting I'm back in the boot loop. I've tried installing stock roms rooted and unrooted without resolving the problem. ADB doesn't help either just never returns the device serial number. Loopfix just sits there waiting for device.
I'm am S-OFF (via Revolutionary)
-Revolutionary-
MECHA XD SHIP S-OFF
HBOOT-6.04.1002
MICROP-/
RADIO-1.16.00.0402w_1
eMMC-boot
Feb 23 2011,20:42:55
There is no PG05IMG.zip file on my SD card. (apparently can cause boot looping)
I googled to my hearts content, browsed every forum and blog I could to find a solution. Found similar issues but was not able to use any of the know fixes out there. Part of the problem is ADB doesn't see my phone. I've looked at 'loop fix' and 'thunderbolt all in one tool' these don't work for me. Any suggestions would be welcome. I'd prefer not to have to throw money at the problem to fix it.
I know I screwed the pooch on this one, maybe someone has the skills to help me unscrew it.
Thanks much in advance!
Rem
What happens when you connect the phone via USB? Does the computer detect it? You could try flashing cwm through hboot
sent from my jellybolt courtesy of the jester
dizzyman1180 said:
What happens when you connect the phone via USB? Does the computer detect it? You could try flashing cwm through hboot as PG05IMG. See if that works and you can get into recovery.
sent from my jellybolt courtesy of the jester
Click to expand...
Click to collapse
sent from my jellybolt courtesy of the jester
dizzyman1180 said:
What happens when you connect the phone via USB? Does the computer detect it? You could try flashing cwm through hboot
sent from my jellybolt courtesy of the jester
Click to expand...
Click to collapse
Windows 7 does signal that it sees a USB device but it shows unknown device. I've tried the HTC Drivers and the android USB drivers from google. Nothing doing. I am currently trying to install CWM via hboot (PG05IMG.zip). Got into CWM once tried to restore back to my backup but after the restore process same thing.
Thank you for your suggestions!
Rem
No problem. Report back with your progress.
sent from my jellybolt courtesy of the jester
dizzyman1180 said:
No problem. Report back with your progress.
sent from my jellybolt courtesy of the jester
Click to expand...
Click to collapse
UPDATE: Unable to get CWR through HBOOT.
Rem
I have the same problem.
I have a brand new(refurbished) thunderbolt. I recently installed
*07-25-2012* JELLYBLUR *V1.3* CM7.2 - SPJESTER Production
I completely wiped and cleared the device. All was running fine, until I unplugged it from the charger then poof, boot loop. I can also access hboot but nothing seems to work. I have flashed a few roms, but I'm out of my depth here.
I will try putting and image on the sd card, since it does try to flash a radio when it boots.
Either of you tried an RUU. Download 605.9 or 605.19, change it PG05IMG.zip and flash it through hboot, see if it goes through.
Sent from my ADR6400L using xda premium
I have successfully flashed both recovery, and the latest mr4 radio from hboot.
Without the sd card, I was able to get it booted once after each flash. Unplugging it forced it right back into boot loop(whether card was in or not).
The only options that work are hboot, and fast boot. Neither connects to adb, or the all in one tool.
Can I flash a regular rom from hboot? I have previous version of thundershed, and various stock roms on the SD card?
dizzyman1180 said:
Either of you tried an RUU. Download 605.9 or 605.19, change it PG05IMG.zip and flash it through hboot, see if it goes through.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I've tried RUU both .9 and .19 both seem to flash fine. But after reboot same boot loop. After trying a few more times flashing various RUU I flashed .19 again. After rebooting the phone I was able to get into the phone, everything setup fine, google account, wireless, etc. But after rebooting again. Back in same boot loop. I've also tried using 2 different SD card to rule out a bad SD. Unfortunately same thing. Starting to think this is hardware not a bad rom or firmware.
Rem
Ok I tried a factory wipe, no go either....
Tried installing regular rom renamed as "pg....." that didn't work.
So I've been told as long as you have hboot you can fix anything...Not sure whats next? At this point I'd be happy to start over.
Okay, I'm gonna try and see if I can get a dev to check out this thread for you guys. Because I am not sure what to tell you to do next at this point. Its exceeded my knowledge.
Sent from my ADR6400L using xda premium
dizzyman1180 said:
Okay, I'm gonna try and see if I can get a dev to check out this thread for you guys. Because I am not sure what to tell you to do next at this point. Its exceeded my knowledge.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Dizzyman any help is appreciated. Thanks for taking an interest and trying to help!
Rem
ok, I am not exactly sure what happened...I left my phone with no sim, no memory card and no battery alone for about 7 hours.
I came home with the intent to flash twrp from fastboot usb. I plugged it into usb port, put memory card and battery in. The phone on its own turned on, and voila it was in Clockwork.
Note the SIM card was not in the phone. I accidentally left it in the other tbolt I am replacing.
I factory wiped, cleared cache, and then installed thundershed from zip on SD. It has booted twice and seems to be running as it should be.
I put the sim card in and now its boot looping again. Removing the sim it boots and runs fine. The sim works fine on another thunderbolt, so I must assume the sim is fine.
I compared phones both were running the same rom and same radios. Kernels were different so I flashed imoseyon kernel to match the working phone. No go still boot looping.
Assurion sent me a "new" retail sim. Verizon told me to use my old one in the new phone. However the "new" phone will boot loop continuosly with old sim card. I have verified that the rom, radios, etc are all the same.
The mystery deepens...
tonyagee said:
ok, I am not exactly sure what happened...I left my phone with no sim, no memory card and no battery alone for about 7 hours.
I came home with the intent to flash twrp from fastboot usb. I plugged it into usb port, put memory card and battery in. The phone on its own turned on, and voila it was in Clockwork.
Note the SIM card was not in the phone. I accidentally left it in the other tbolt I am replacing.
I factory wiped, cleared cache, and then installed thundershed from zip on SD. It has booted twice and seems to be running as it should be.
I put the sim card in and now its boot looping again. Removing the sim it boots and runs fine. The sim works fine on another thunderbolt, so I must assume the sim is fine.
I compared phones both were running the same rom and same radios. Kernels were different so I flashed imoseyon kernel to match the working phone. No go still boot looping.
Assurion sent me a "new" retail sim. Verizon told me to use my old one in the new phone. However the "new" phone will boot loop continuosly with old sim card. I have verified that the rom, radios, etc are all the same.
The mystery deepens...
Click to expand...
Click to collapse
Attempted the above on my device but no luck. Just same reboot loop. Just FYI. Thanks for the tip.
Rem
Even the different sim, eventually led to the same issue. I finally just convinced assurian that my replacement phone is defective (which is may be).
The only thing I can think of is that the jelly rom, combined with the all in one root tool somehow made a bad situation or the phone is simply defective.
Now my task is to see if I can flash something to make this stock...lol...I really don't want to send back a phone to assurion with clockwork and revolution on it if I can help it.
I suspect its going to be tricky as ADB doesn't work..
Here is where I stand.
1. Flashed a stock room, through hboot
2. Flashed a stock hboot through hboot. (this didn't work, revolution is locked)
3. I rebooted back to hboot.
4. removed sim card, and sd car.
5. Then I selected "Recovery" it went into standard recovery i let it sit for a bit, then it rebooted on its own back to stock, unactivated state.
I used the files from this thread
After this is seems to function perfectly normal, except I still have a revolutionary boot loader, and soff.
I let the phone reboot, and once it loaded I was able to get adb to work perfectly fine. I then returned to the above guide and fixed the boot loader, and s-off as directed. Its now completely stock. I mean it might be a version or so from whats current but a simple ota update would take care of it.
Its all brand new...Of course, I am still going to return it to asurian as I have no idea if it had a hardware issue, or what it was.
tonyagee said:
Here is where I stand.
1. Flashed a stock room, through hboot
2. Flashed a stock hboot through hboot. (this didn't work, revolution is locked)
3. I rebooted back to hboot.
4. removed sim card, and sd car.
5. Then I selected "Recovery" it went into standard recovery i let it sit for a bit, then it rebooted on its own back to stock, unactivated state.
I used the files from this thread
After this is seems to function perfectly normal, except I still have a revolutionary boot loader, and soff.
I let the phone reboot, and once it loaded I was able to get adb to work perfectly fine. I then returned to the above guide and fixed the boot loader, and s-off as directed. Its now completely stock. I mean it might be a version or so from whats current but a simple ota update would take care of it.
Its all brand new...Of course, I am still going to return it to asurian as I have no idea if it had a hardware issue, or what it was.
Click to expand...
Click to collapse
Tonyagee that's for the step by step. Tried on my Tbolt. Still boot looping. I appreciate you documenting what you did THANK YOU!
Your welcome...I definitely was on the edge of my skill set for sure....
So my thunderbolt is is in the same boat. The main cause for the boot looping seems to come from unplugging the usb from charging.
Mine will randomly stop the infinite boot looping and boot up. Sometimes it's quick. Sometimes it will take hours.
Most of the time when I manage to get it to run it is very difficult to get back into a custom recovery. It has to reboot the phone to get into recovery which most of the time just puts it into the infinite boot loop again.
If I plug mine into a computer it will charge but will not recognize the phone.
I've tried every fix known to man. No luck. I've come to deal with it as I've had this problem for two or three months now.
Sent from my ADR6400L using Tapatalk 2
---------- Post added at 08:09 PM ---------- Previous post was at 07:37 PM ----------
tonyagee said:
ok, I am not exactly sure what happened...I left my phone with no sim, no memory card and no battery alone for about 7 hours.
I came home with the intent to flash twrp from fastboot usb. I plugged it into usb port, put memory card and battery in. The phone on its own turned on, and voila it was in Clockwork.
The mystery deepens...
Click to expand...
Click to collapse
Mine has done the same thing. I read that one of the failsafe ways to boot up clock work mod recovery is that it will automatically boot up after a battery pull and turn the phone back on with it plugged in.
If I plug the phone in while it is completely shut down it automatically powers it on and 9 times out of 10 it randomly reboots but sometimes it will boot up into recovery.
Sent from my ADR6400L using Tapatalk 2
i just upgraded to 2.2.1 and now my phone keeps rebooting when i try to do anything with system (wipe or write a new rom). phone continually rebooting, if my current rom tries to load phone reboots again.
when i plug in light does not come on...
any ideas or is this thing dead? i can still get into recovery and have some battery life just not sure what to do... already reflashed recovery
seems like my /system/ is hosed not sure how to fix if possible
tried nandroid restore.. it reboots
tried to reflash existing.. it reboots
i can still get into recovery though but if i do anything with 'system' it reboots
any ideas how to get that fixed or probably have to replace? i cant even overwrite my custom boot logo. ugh lol
Try relocking the bootloader, then fast boot the ruu
Sent from my EVO using xda app-developers app
jdizzle316 said:
Try relocking the bootloader, then fast boot the ruu
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
thanks im downloading the RUU..
How exactly did you update to the newest base?
Figured I would update this thread in hopes of helping someone else if they get stuck here.
I had upgraded to the new base with PJ75IMG and that went well - had used other ROMs on that new base.
What had happened was I was flashing venom on TWRP 2.2.0 and it rebooted phone when it hit system (why system was damaged in first place not sure, i had just rebooted into recovery).
I had to oem lock, ruu, oem unlock (even though it said s-off for lazypanda it was not working) and then i was able to re-flash twrp (this time pushed 2.2.1 through fastboot).
I've put a lot of evo's in bad spots but the behavior I saw on this was new for me.. Anything I touched 'system' from twrp or if my rom tried to load, phone would cycle. Light would NOT go on when plugged in.
Either way rocking new rom and am good! thanks guys
Well let me explain my predicament. The other day I flash somex's something explosive rom after a wipe of the everything I need to wipe ( Data,Cache,Davlik) When it was finished flashing I got to rebooting. I ended up with a blank, yet illuminated screen ( if that makes sense) I waited about 20 minutes. After coming to the conclusion that the ROM doesn't work I did another wupe of everything needed. Then i flashed JoseGalre's ROM since it has aroma it told me that it had an error and coundln't finsih the instalation. I wiped again and reflashed, same error. I wanted to see what would happen if it let it boot up w/o recovery and it ended up in a boot loop. I tried to go back to 4ext and it seemed to load up just fine but half way through the startup it ends up back in the bootloop. I ran Hasoon's all in one kit and flashed TWRP and it worked just fine until I flash a rom. It seemed to be working just fine then it suddenly crashes and we're back in the loop. I've been trying to fix for the last few days but to no avail. I marked the title as urgent because my parents are going out of town for the weekend and I really need a phone. They havn't a clue that it doesn't work becausse they get home before me. Any help would be appreciated a great deal.
I've had something similar happen and freaked out my phone was down for half a day.
Try booting into the boot loader by holding vol down and power boot into recovery, wipe everything then format everything except SD card and try restoring a backup. Hopefully you made one or two in the past.
Sent from my HTC Amaze 4G running Evervolv jellybean 4.3
Illstatic said:
Well let me explain my predicament. The other day I flash somex's something explosive rom after a wipe of the everything I need to wipe ( Data,Cache,Davlik) When it was finished flashing I got to rebooting. I ended up with a blank, yet illuminated screen ( if that makes sense) I waited about 20 minutes. After coming to the conclusion that the ROM doesn't work I did another wupe of everything needed. Then i flashed JoseGalre's ROM since it has aroma it told me that it had an error and coundln't finsih the instalation. I wiped again and reflashed, same error. I wanted to see what would happen if it let it boot up w/o recovery and it ended up in a boot loop. I tried to go back to 4ext and it seemed to load up just fine but half way through the startup it ends up back in the bootloop. I ran Hasoon's all in one kit and flashed TWRP and it worked just fine until I flash a rom. It seemed to be working just fine then it suddenly crashes and we're back in the loop. I've been trying to fix for the last few days but to no avail. I marked the title as urgent because my parents are going out of town for the weekend and I really need a phone. They havn't a clue that it doesn't work becausse they get home before me. Any help would be appreciated a great deal.
Click to expand...
Click to collapse
I don't think you wiped properly. You needed to format ALL PARTITIONS. I can't stress that enough lol.
Edit: Go into bootloader first. Hold volume down then hold power as well. Choose recovery and format all partitions. If that works you're good! :thumbup:
Use the toolkit and flash 4ext. And make sure whenever you flash Roms that you format all partitions.
If that doesn't work you need to flash a RUU, get it back to stock, it will still retain S OF. Then flash 4ext again. Your problems should be fixed for sure if my first method doesn't work.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hey guys it completly out of the question to format my internal storage so keep that in mind
GB or IC RUU and which one?
You don't have to format internal storage just data, cache, system, and boot
Sent from my HTC Amaze 4G running CyanogenMod 10.1
Illstatic said:
Hey guys it completly out of the question to format my internal storage so keep that in mind
GB or IC RUU and which one?
Click to expand...
Click to collapse
Just choose format all partitions.
If you want to use a ruu use the T-Mobile ICS RUU.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So i changed the name of the RUU i download to PH85img.zip and use the all in one tool kit to flash it. The black htc loading screen came up. I waited until it finished and then the bootloader came up with a list of things it head to unzip and then load. After all of that was finished it gave me an error. After reading a message that you should get an error ( i now realize this was at another stage) so i though nothing of it and rebooted. A black screen with 4 warning triangles came up. I let it load all day and when i got home i plugged it back in and I noticed it looked like it was unplugging after securing the charger in I came the conclusion that it wasn't holding a charge and dying on the battery. Normally I would leave it alone but when you plug in the charger it turns itself on. I've began living with the fact that my phone is bricked. But any help would be appreciated.
BTW is there a way to get data (music pictures contacts) that were saved on the internal storage?
Probably should have gone with full caps on the PH85IMG.zip
It's easier just to put the zip on your external sdcard and gone in to bootloader.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
Probably should have gone with full caps on the PH85IMG.zip
It's easier just to put the zip on your external sdcard and gone in to bootloader.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
So is there anything that I can do when I plug it in it wont boot or charge at all so am i truly bricked or is there still hope
Illstatic said:
So is there anything that I can do when I plug it in it wont boot or charge at all so am i truly bricked or is there still hope
Click to expand...
Click to collapse
Should be hope, check out the unbricking project...
http://forum.xda-developers.com/showthread.php?t=1627882:cowboy:
Had a random issue today. I periodically reboot to recovery and wipe cache/dalvik every day. Today when I tried it was stuck at splash screen. It simply kept rebooting to splash and would hang up. I could get to bootloader. But that was it. I manually shut it down a few times and finally removed my sdcard. After about a half hour and a lot of stress I finally got it to boot in to Rom. Thinking it might help I downloaded goo manager and updated twrp to 2.6.3.0. It was strange because now all seems fine. Any thoughts on what happened? Is my firmware going out?
============================================================
current setup
htc evolte
hboot:1.19 s-off
twrp 2.6.3.0
Firmware 3.17
anthraxed digital bath
Are you sure you didn't accidentally wipe the system partition? That might have done the bad trick..
Yeah I'm sure. Now my evo is definitely soft bricked. Splash screen bootloops and the internal sd won't preload in bootloader. I think I have to attempt to flash stock recovery via hboot and push ruu as well. For now I just upgraded to the one.
Sent from my HTCONE using xda app-developers app
Darealboot said:
Yeah I'm sure. Now my evo is definitely soft bricked. Splash screen bootloops and the internal sd won't preload in bootloader. I think I have to attempt to flash stock recovery via hboot and push ruu as well. For now I just upgraded to the one.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Try using VipeRuu... But that's a 3.16, I don't think there is a 3.17 RUU...
Sent from my SPH-L900 using Tapatalk 4
Mine has behaved in similar way for about past two weeks where it randomly reboots and then bootloops to splash screen over and over. After a few minutes it will finally boot into the rom. I am on decks 10.2. It was worst with a couple of releases ago, I think 0916 or something but it has done it a couple of times with 1006 which was still current IRC version as of earlier this week. I don't know what triggered it to start happening, whether it was the ROM itself or some other app I added. I did find that usually I could boot into recovery, clear dalvik and cache then reboot and it seemed to work but not always. It's a nuisance but I've never had it not recover from bootloop within a few minutes. btw this was with a full wipe and factory reset in both cases.
Mine started after flashing the latest firmware via fastboot. Idk what else to try other than what's already stated. I may try to push older firmware first. I'd hate to have a dead device sitting around. I guess when I find the time I'll get to work on it.
Sent from my HTCONE using xda app-developers app
Viper ruu worked on latest 3.17 firmware. I was nervous for sure. But success!
Sent from my HTCONE using xda app-developers app
Me too.
In the last hour, my phone got stuck in a boot loop. I wasn't doing anything at the time; in fact it was sitting on my desk. I've been using my phone all day without issue. It had plenty of juice left prior to this issue.
I was running Deck's latest.
This happened to me tonight. It's been a total nightmare trying to fix it.
Well idk what kind of bootloops you guys are having, but if u flashed the latest firmware recently and are having splash screen bootloops, then the fix is stated above. Viperruu will work great. Just make sure you read the op thoroughly.
Sent from my HTCONE using xda app-developers app