My phone just got into bootloop. I have tried several fixes and managed to install TWRP. Most of the fixes I have tried doesn't work.
I will try to boot by Heating it up so much (it was one of the fixes). But can i use custom roms? instead of modified roms
If the bootloop is due to a failed memory chip, nothing is going to help.
When you say bootloop, you mean it is stuck on one particular and won't proceed?
Have you tried installing a stock KK ROM?
Related
Trying to help out my friend. He rooted his Galaxy S 4G and was trying out different roms and now it's stuck in recovery. He brought it to me--I can pretty much fix anything Android--I've helped a lot of people on XDA, but this one has completely stumped me.
I've Odin'd several different Official Stock restore packages, recovery packages, etc. Everything has the same effect, no matter the rom or the recovery, the phone will always (re)boot back into recovery. Selecting reboot system reboots it back into recovery. No matter what. I must have flashed Stock via Odin about 10 times today. Same results every time.
Right now it's stuck in the 3e recovery screen. But I can flash a Voodoo recovery, but it still gives the same effect.
Does anyone have any ideas? Is there a bootloader sequence anyone knows about, that he may have changed? Any help is appreciated.
Thanks everyone!
Follow the guide in the second link of my signature to fix.
Awesome! That worked! Followed the guide. I had already flashed stock, but I didn't know you could flash the bootloaders using a .jar package. It worked. I guess he jacked with his bootloaders.
actually, bootloaders would corrupt boot period. You'd be stuck in a "FIRMWARE UPGRADE FLASH FAILED" screen, or phone won't boot period. So, I think I know what the problem was.
When hopping from roms to other roms, specially on Kxx Based Touchwiz roms, your cache tends to get corrupted. Had you reflashed cache.rfs and a stock zImage using heimdall, it'd fix the issue, and data wouldn't vanish.
xt926 with unlocked bootloader and can run 10.1 nightly from get.cm with no problem. However, when I install a 10.2 nightly - whether from get.cm, epinter, dhacker or skrilaz - even though the initial boot comes up clean, rebooting after the initial boot gets stuck on the boot logo.
I have tried different recovery images - cwm, twrp, oudhs - and different versions of each.
I have tried clean installs, full formats and dirty upgrades from 10.1.
I have tried multiple force boots from this state (power+vol up).
I have tried with and without the updated gapps and UPDATE-SuperSU-v1.51.zip.
Restoring from backup does not get past this hang. The only way out is to revert to stock (I use mattlegroff's DROID_RAZR_HD_Utility_1.21).
Does anyone have any idea how I might get past this or even get a log?
Only thing that fixed this for me was to flash back to stock 4.1.2, flash newest CWM touch recovery, then flash newest nightly, Gapps, and SU. Then, a popup comes up saying something about the ROM wants to flash your boot image, and asks if you'd like to fix this. I answered YES (fix) and been working since.
Any chance you could link where you got your recovery and SU?
Much appreciated.
Same issue here...
I've also tried everything listed above. I've done everything i can possibly think of to get cm 10.2 on my xt926. For some reason my phone just isn't making it after the first reboot. I've searched and found similar issues but none of the troubleshooting has been working for me. I hope to find a way around this. I need that 10.2!
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
GeorgeHahn said:
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
Click to expand...
Click to collapse
one of 2 things should fix this problem,
use cwm 6.0.3.5 from here or
go to recovery/mounts and storage and format the data-media line (i know it says sd card but its internal, do not format the external ed card line or you will loose data on it)
also i updated matts utiliity to the latest ota, so you dont have to take the ota just to get the baseband. its in the dev forum. i will be updating it to a newer version if you wait until later, with the newest recoveries.
edit, btw 2.6.0.0 is not the latest twrp although i recommend using cwm as some have had issues with twrp including me.
First off, the latest TWRP seems to have fixed the problems (for me, anyway). Second, you'll need to use the most up-to-date GAPPs when you flash. Also, a lot of people have noted that mounting sytem prior to doing their wipes has solved the reboot issues.
Thanks a ton for the help. Flashed latest CWM and bumped up to 4.4 and everything's working fine. I appreciate the help!
I have been having issues with TWRP inverting itself. I know the fix for it is in the *#2663# menu, but in all reality it is annoying to half to fix this everytime I go into TWRP. How do I fix this issue? Its getting frustrating.
Any help is appreciated .
Edit:
I failed to say that I am using the SM-G920T (T-Mobile) Variant of this phone.
Reflash back to stock 5.1.1 ROM via odin.
Thats the obvious. I appreciate the input, but would rather not have to go that route. If there is any other way to resolve this issue, that would be great.
tenebris said:
I have been having issues with TWRP inverting itself. I know the fix for it is in the *#2663# menu, but in all reality it is annoying to half to fix this everytime I go into TWRP. How do I fix this issue? Its getting frustrating.
Any help is appreciated .
Edit:
I failed to say that I am using the SM-G920T (T-Mobile) Variant of this phone.
Click to expand...
Click to collapse
I don't think it's twrp causing your issue. Thus only happened to me when flashing aou's stock recovery. If it is happening to you because of twrp I would imagine it's the same reason it happened to me when flashing recover. You have the wrong version of twrp. Try following these instructions to get the correct twrp for your phone. Hope this helps
http://forum.xda-developers.com/showthread.php?t=3080940
Realize I flashed the Edge version. Thanks @drock212
I have also seen this, for no apparent reason trwp did this after I tried to flash a custom rom and the device got stuck in a boot loop. So flash back to stock android 7 rom, then reflash twrp etc.
b1k3rdude said:
I have also seen this, for no apparent reason trwp did this after I tried to flash a custom rom and the device got stuck in a boot loop. So flash back to stock android 7 rom, then reflash twrp etc.
Click to expand...
Click to collapse
Found the fix and posted it here -
- https://forum.xda-developers.com/galaxy-s6/help/touchscreen-x-axis-reversed-t3157830/page2
Hey all,
As I am getting fed up with the 5.1.1 stock ROM of Nvidia, I want to flash a custom Nougat ROM to my Nvidia Shield. I have already unlocked the bootloader, installed TWRP, and rooted my device. This all went without problems.
But then I tried installing a custom ROM, but after installation of both the ROM and the Gapps, the tablet just doesn't want to get past the Nvidia boot logo. Then I have no choice but to back up in recovery, and to recover my backup.
The process I mentioned I have tried for at least 6 different ROM's, and all of them don't get passed the nvidia boot logo. So this means Im still stuck with the 5.1.1 version from Nvidia (don't worry, I won't brick it)
I have the original non-K1 32-bit Shield. I have a feeling that it has something to do with this, and that that is the reason why I cant flash ROM's.
My question is, does anyone recognize this issue, or, does anyone know how to fix this?
Kind Regards,
Horizon
Edit1: Another thing worth mentioning (maybe) is that it can't a md5 file for each custom ROM I try to install, but this shouldn't be a problem right?
HorizonR2 said:
But then I tried installing a custom ROM, but after installation of both the ROM and the Gapps, the tablet just doesn't want to get past the Nvidia boot logo. Then I have no choice but to back up in recovery, and to recover my backup.
Edit1: Another thing worth mentioning (maybe) is that it can't a md5 file for each custom ROM I try to install, but this shouldn't be a problem right?
Click to expand...
Click to collapse
I could be that the custom Roms need the newer bootloader.
So you should try install latest OTA, avoid the kill switch and than you should be able to install a custom rom
And the md5 is just to check if the ZIP is damaged or so, which happens nearly never.
And it doesnt matter if you have a k1 or an original Shield Tablet
is there a partial blob I can flash for the new bootloader without installing the entire Stock ROM? I have the same problem and really don't want anything to do with Nvidia software unless absolutely necessary.
ddvche said:
is there a partial blob I can flash for the new bootloader without installing the entire Stock ROM? I have the same problem and really don't want anything to do with Nvidia software unless absolutely necessary.
Click to expand...
Click to collapse
Read this guide on how to install Nougat; it explains all: https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
Hello all. I found my Moto G ( XT1033) and decided to use it as a backup phone. Anyway, I flashed a CM12.1 ROM. Worked well for a while before switching off and getting stuck on a bootloop. Strange, I've already used it for some time. I thought maybe there were some problems with the ROM file. But now, I've tried it with Tesla, Blisspop, CM11, CM13. All have worked well for me in the past. Every ROM is facing the same problem.
Any help would be appreciated.
i face the same problem. its like everyday i have to do stock rom on my phone because it stuck on boatloader.
if all new clean flashed ROMs result in boot loops, you will have to reinstall stock ROM (with fastboot) to fix it. flashing stock ROM with custom recovery will not fix it though
koshikas said:
if all new clean flashed ROMs result in boot loops, you will have to reinstall stock ROM (with fastboot) to fix it. flashing stock ROM with custom recovery will not fix it though
Click to expand...
Click to collapse
Any idea what's causing it, though? I'm not able to flash a ROM into the device using the fastboot method. I've tried various builds, they all show the error after a few commands 'PARTITION SIZE IS SMALL' .
i'm not exactly sure whether you did it right. refer;
https://forum.xda-developers.com/showthread.php?t=2542219
https://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795