Database Info

Has anyone ever bootlooped for no apparent reason?

Just wondering if anyone has ever bootlooped their Charge for no apparent reason. I wasn't flashing anything I was just transferring some videos from my computer to my SD card when suddenly I noticed I can't install any apps from the market it just endlessly installs. So I hold the power button and click restart, get the Samsung logo & my boot animation but the boot animation NEVER ends. I battery pulled twice already and attempted to remove the SD card(since transferring files to it seems to be the only cause for this problem) but alas, to no avail. I rebooted into clockwork, reflashed Eclipse, cleared cache, dalvik cache and rebooted. Still, nothing.
If anyone has had this happen to them or just knows how to fix this please let me know, it's quite shocking considering I did absolutely nothing except transfer a video to my SD card. I'd prefer not to flash the .pit/.md5 since I haven't backed up in a while but if it's totally necessary I'll make the sacrifice for the greater good.

Your phone is force closing due to something if the boot animation never ends. If you use adb and get a logcat, it is possible that we could figure out what it is and maybe fix it. However, wiping /data and doing a factory reset will fix it if you want to go that root. Also Q&A

I just did a factory reset, didn't want to but I need my phone. Bummed I'm going to have to redownload like 35+ apps though, my fault for not backing up more frequently.

I have some random acore fc's sometimes that can only be fixed by wiping and flashing. Good thing I keep everything backed up every few days. I wish there was an option to schedule backups.
Sent from my Droid Charge running GummyFroyo 1.9.1

Yeah it bootlooped so I did a factory reset & reflashed, everything seemed fine but then i got all these force closes. This is so aggravating!
update: Flashed the .pit/.md5 combo to go back to stock, just gonna start over.

[Q] NS4G is possesed

I have a strange situation going on with my phone and I could use some advice.
My issues started after loading the "official" IMM76D ROM, the rooted and odexed version. Phone would shut off like it was dead after charging all night. Wont boot back up without a battery pull. It would freeze up while the screen was on forcing a battery pull. Basically unusable for more than 10 minutes.
Here is where I might have messed things up. I tried to wipe the phone completely, including the SD card. Factory Reset multiple times, wiped everything multiple times. I even did a repartition of the SD card thinking it would format it further.
Where I'm at now. The phone still boots into the 4.0.4 ROM and I still have CM recovery. But now no matter what I do, factory reset, format/wipe EVERYTHING including the SD card, use fastboot to load a whole new setup, THE PHONE BOOTS RIGHT BACK INTO THE ROM AND SD CARD STILL HAS EVERYTHING. I dont get it.
I have ODIN 1.87 downloaded but it wont see my phone in download mode. I have all the correct drivers loaded including PDAnet, and my phone is correctly detected as Android ADB Device. Interesting side note: fastboot detects the phone, ADB does not. dont know if that means anything.
Sorry for the long winded post but I have been at this for 4 days now and I really need my phone back! Any ideas??

Maybe flash stock rom or CWM recovery from fastboot would solve the partitions issue. I remember when i had my old HTC magic i would sometimes change the partition layout and to reverse it i would have to reflash my recovery.
But as i said, this is all theory and can work or not.

Brand new Nexus 5 DOA

The the device came in today and when I turn it on The Google logo comes, turns off and restarts for a boot loop. I even did a full restore using the recovery toolkit like swoggers and even then no luck. I was able to install twrp with no issue. Anyone have the same issue ?
Thanks

Anyone?

saadkhan07 said:
Anyone?
Click to expand...
Click to collapse
I had problems AFTER I installed TWRP, but before that it booted just fine.
My problems started after unlocking the bootloader and installing TWRP. Try wiping as much as possible (except System) with TWRP. I read somewhere it's a problem with the cache partition. I also went into "Mount" in TWRP (I think that's what it's called) and mounted System. I'm telling you all this from memory, not sure exactly how I fixed it, but eventually I was able to turn the phone on.
Hopefully this is the reason you're having problems. It'd be frustrating to have to try and get another one from the Goog.

Accidentally deleted TouchWiz Home? What can I do?

So I accidentally uninstalled Touchwiz Home and the phone keeps on rebooting. I got into the regular recovery mode and cleared cache, but the phone still reboots. The swiping screen turns on, but then it says "com.android.phone has stopped working or something like that and then immediately restarts. Is there a way to fix this? Or at least recover all of my files before restoring it? I really do not want to lose all of my files. Thanks.

juicylemon said:
So I accidentally uninstalled Touchwiz Home and the phone keeps on rebooting. I got into the regular recovery mode and cleared cache, but the phone still reboots. The swiping screen turns on, but then it says "com.android.phone has stopped working or something like that and then immediately restarts. Is there a way to fix this? Or at least recover all of my files before restoring it? I really do not want to lose all of my files. Thanks.
Click to expand...
Click to collapse
There may be a couple of ways of correcting this. Much will depend on what bootloader and modem you are on.
Are you on a stock ROM, and if so what version?
Or, are you on a TouchWiz based custom ROM?
If you are rooted and have USB debugging enabled you may be able to adb to copy files and/or directories to a computer. You have probably already copied everything from the external sdcard to your computer. It is unfortunate that the stock recovery does not have file manager that allows you to copy to the external sdcard, TWRP does. TWRP may be an option if you are on an early version of the stock ROM.
As a final resort, on times when I have upgraded with OTAs or flashed custom ROMs without formating the internal sdcard the media partition remained intact. This may not be true with an Odin flash of the stock ROM. Then again /media may still be preserved.

TWRP Bootloop (SM-J327P)

I've been stressed out lately about trying to root my Samsung Galaxy J3 Emerge.
I got TWRP 3.1.0-0 and went on install but the supersu 2.82 zip file wasn't showing so I tried to fix it.
First I tried Format Data and that didn't work, then I tried Changing File System for System, Data, and Cache one by one and that seemed to have worked. The supersu file showed and I installed it.
Then I Rebooted System and it said,"No OS Installed! Are you sure you wish to reboot?" and this has happened to me before so I figured it would reboot back into TWRP and I would have to boot to download mode, and install the firmware through Odin, but that didn't happen, what happened instead was when I Rebooted System, on the top right it said,"kernal is not seandroid enforcing, set warrenty bit:kernal" and would keep bootlooping, I went back into TWRP by taking the battery out and putting it back in then holding power, home, and volume up and I was back in TWRP.
The thing is it would keep doing this and I'm kinda stuck right now tbh. I already tried Formatting Data, Flashing a ROM, and installing the SM-J327P Firmware, but nothing worked. I'm guessing the only way to fix this is by changing back to my original File Systems and then installing the Firmware through Odin, but I'm stupid and don't remember the original File Systems. So if any of you could tell me the default File System for System, Data, and Cache or another way to fix this that would be great. Thanks

I'm still stuck in this situation...
Any help plz?

IYaWonaRoo said:
I've been stressed out lately about trying to root my Samsung Galaxy J3 Emerge.
I got TWRP 3.1.0-0 and went on install but the supersu 2.82 zip file wasn't showing so I tried to fix it.
First I tried Format Data and that didn't work, then I tried Changing File System for System, Data, and Cache one by one and that seemed to have worked. The supersu file showed and I installed it.
Then I Rebooted System and it said,"No OS Installed! Are you sure you wish to reboot?" and this has happened to me before so I figured it would reboot back into TWRP and I would have to boot to download mode, and install the firmware through Odin, but that didn't happen, what happened instead was when I Rebooted System, on the top right it said,"kernal is not seandroid enforcing, set warrenty bit:kernal" and would keep bootlooping, I went back into TWRP by taking the battery out and putting it back in then holding power, home, and volume up and I was back in TWRP.
The thing is it would keep doing this and I'm kinda stuck right now tbh. I already tried Formatting Data, Flashing a ROM, and installing the SM-J327P Firmware, but nothing worked. I'm guessing the only way to fix this is by changing back to my original File Systems and then installing the Firmware through Odin, but I'm stupid and don't remember the original File Systems. So if any of you could tell me the default File System for System, Data, and Cache or another way to fix this that would be great. Thanks
Click to expand...
Click to collapse
You have to use the getprop command to get your software number. Then you have to restore that EXACT software. You might have probably updated unknowingly, and the bootloader updated too. So restoring to an older firmware might bootloop. It was a huge pain in the butt to get mines working after this issue but I got it right after a few tries. I flashed the custom J327p rom they made for it, factory reset and just waited until it booted. Was a long time but after trying every restore and refreshing, I got it working. There's the newest firmware out (idk the name since I just have the metro version of this phone now) but only that one will get the phone running. If you ever do get it running, root with magisk as this phone is VERY sensitive to SU and won't work half the time

savagevegeta said:
You have to use the getprop command to get your software number. Then you have to restore that EXACT software. You might have probably updated unknowingly, and the bootloader updated too. So restoring to an older firmware might bootloop. It was a huge pain in the butt to get mines working after this issue but I got it right after a few tries. I flashed the custom J327p rom they made for it, factory reset and just waited until it booted. Was a long time but after trying every restore and refreshing, I got it working. There's the newest firmware out (idk the name since I just have the metro version of this phone now) but only that one will get the phone running. If you ever do get it running, root with magisk as this phone is VERY sensitive to SU and won't work half the time
Click to expand...
Click to collapse
Thanks for the reply but I have tried restoring with a firmware with my exact software number, model, version, changelist, build date, country/carrier(sprint), and security patch level and I did a format data, yet It didn't work... As far as I know, the bootloop was not caused by the firmware, it was caused by me manually changing the Partitions' File Systems, however I do not remember the original File Systems for the partitions. In case this madders, the way I changed it was by pressing "Wipe" in TWRP, then "Advanced Wipe", then selecting "System", then "Repair or Change File System", then "Change File System", and choosing a random button. I also selected "Data" and "Cache" but I did it individually, one at a time.

IYaWonaRoo said:
Thanks for the reply but I have tried restoring with a firmware with my exact software number, model, version, changelist, build date, country/carrier(sprint), and security patch level and I did a format data, yet It didn't work... As far as I know, the bootloop was not caused by the firmware, it was caused by me manually changing the Partitions' File Systems, however I do not remember the original File Systems for the partitions. In case this madders, the way I changed it was by pressing "Wipe" in TWRP, then "Advanced Wipe", then selecting "System", then "Repair or Change File System", then "Change File System", and choosing a random button. I also selected "Data" and "Cache" but I did it individually, one at a time.
Click to expand...
Click to collapse
That's a tough one. I've never touched those options in TWRP. Have you used Odin to completely wipe the phone from everything including TWRP and flashing stock?

savagevegeta said:
That's a tough one. I've never touched those options in TWRP. Have you used Odin to completely wipe the phone from everything including TWRP and flashing stock?
Click to expand...
Click to collapse
I do have a brother that has the EXACT same phone as me so I tried installing TWRP on his phone and checking the original File Systems, however TWRP doesn't install on his phone for some reason. I enabled developer options, USB debugging, OEM, and installed the drivers and when I install TWRP recovery on his phone through odin it says it was successful but for some reason when I boot into the bootloader it's the regular one that comes with the phone and not TWRP. I'm guessing this is because he has low storage (95% used up). But he doesn't cooperate with me and says he doesn't want the TWRP on his phone because virus blah blah idk (and I don't know how to remove it without factory reset, which he doesn't want to do even though he can backup his stuff) also doesn't want to delete or free up storage from his phone. So I'm going to try wiping my phone through odin i guess...

IYaWonaRoo said:
I do have a brother that has the EXACT same phone as me so I tried installing TWRP on his phone and checking the original File Systems, however TWRP doesn't install on his phone for some reason. I enabled developer options, USB debugging, OEM, and installed the drivers and when I install TWRP recovery on his phone through odin it says it was successful but for some reason when I boot into the bootloader it's the regular one that comes with the phone and not TWRP. I'm guessing this is because he has low storage (95% used up). But he doesn't cooperate with me and says he doesn't want the TWRP on his phone because virus blah blah idk (and I don't know how to remove it without factory reset, which he doesn't want to do even though he can backup his stuff) also doesn't want to delete or free up storage from his phone. So I'm going to try wiping my phone through odin i guess...
Click to expand...
Click to collapse
Storage space has nothing to do with flashing recoveries because they have their own partition. I suggest you flash the same TWRP you used on his phone, then as soon as it finishes flashing, boot into recovery IMMEDIATELY by pressing volume up, power, and home. do NOT let the device boot. If you screw up and it gets to the Samsung animation, flash again and try again. This is because some of the latest Android devices tend to restore recovery upon boot for some reason. Through my experience, anyways. Try this and let me know your results.

savagevegeta said:
Storage space has nothing to do with flashing recoveries because they have their own partition. I suggest you flash the same TWRP you used on his phone, then as soon as it finishes flashing, boot into recovery IMMEDIATELY by pressing volume up, power, and home. do NOT let the device boot. If you screw up and it gets to the Samsung animation, flash again and try again. This is because some of the latest Android devices tend to restore recovery upon boot for some reason. Through my experience, anyways. Try this and let me know your results.
Click to expand...
Click to collapse
Ok. It worked and my phone is back, the problem is now my brothers phone keeps popping up a message on his home screen saying, "Unfortunately, TouchWiz home has stopped.", and "Unfortunately, Google Services Framework has stopped", and other messages over and over and he can't do anything after installing TWRP. I've tried rebooting, and force stopping and clearing cache of Google Services and TouchWiz but nothing worked

IYaWonaRoo said:
Ok. It worked and my phone is back, the problem is now my brothers phone keeps popping up a message on his home screen saying, "Unfortunately, TouchWiz home has stopped.", and "Unfortunately, Google Services Framework has stopped", and other messages over and over and he can't do anything after installing TWRP. I've tried rebooting, and force stopping and clearing cache of Google Services and TouchWiz but nothing worked
Click to expand...
Click to collapse
You have to factory reset. I don't know how you're gonna do it but that's the only way to get out of it otherwise you might have been doing something else other than installing TWRP and broke something. I suggest you restore to stock and try again. If you didn't make a back up, you might be bricked unless you flash the stock firmware with a computer

savagevegeta said:
You have to factory reset. I don't know how you're gonna do it but that's the only way to get out of it otherwise you might have been doing something else other than installing TWRP and broke something. I suggest you restore to stock and try again. If you didn't make a back up, you might be bricked unless you flash the stock firmware with a computer
Click to expand...
Click to collapse
Thank you so much for your help! My phone is back and luckily my brother had a backup so we fixed his phone and I rooted with Magisk which apparently I needed a micro SD card because my internal storage showed as 0mb and tried everything to fix it ,which is why I was in this mess in the first place, then I finally decided to buy an SD card and it worked!

IYaWonaRoo said:
Thank you so much for your help! My phone is back and luckily my brother had a backup so we fixed his phone and I rooted with Magisk which apparently I needed a micro SD card because my internal storage showed as 0mb and tried everything to fix it ,which is why I was in this mess in the first place, then I finally decided to buy an SD card and it worked!
Click to expand...
Click to collapse
The steps to fix storage 0mb are clearly posted in the TWRP thread.

ashyx said:
The steps to fix storage 0mb are clearly posted in the TWRP thread.
Click to expand...
Click to collapse
I have tried manually mounting, format data, wiping system, cache, and data one by one, changing the File Systems one by one, and alot more. NOTHING WORKED. However every youtube video that I have seen about rooting my exact phone with twrp, all had and used micro SD cards! I tried avoiding buying one but every time I try to fix it any other way it ends up either not doing anything or screwing up my device. Once savagevegeta helped me out of the mess I caused by trying to fix the 0mb I decided screw it, no other method worked so might as well try buying a SD card, and guess what happened, IT WORKED! And I realized why every single guide and yt video used micro SD cards for my model.

IYaWonaRoo said:
I have tried manually mounting, format data, wiping system, cache, and data one by one, changing the File Systems one by one, and alot more. NOTHING WORKED. However every youtube video that I have seen about rooting my exact phone with twrp, all had and used micro SD cards! I tried avoiding buying one but every time I try to fix it any other way it ends up either not doing anything or screwing up my device. Once savagevegeta helped me out of the mess I caused by trying to fix the 0mb I decided screw it, no other method worked so might as well try buying a SD card, and guess what happened, IT WORKED! And I realized why every single guide and yt video used micro SD cards for my model.
Click to expand...
Click to collapse
I guarantee you're doing it incorrectly. See my TWRP thread for correct instructions to mount data.

ashyx said:
I guarantee you're doing it incorrectly. See my TWRP thread for correct instructions to mount data.
Click to expand...
Click to collapse
I probably was doing it wrong lol. But its fixed now so dont worry

IYaWonaRoo said:
I probably was doing it wrong lol. But its fixed now so dont worry
Click to expand...
Click to collapse
Your data partition will still be unmountable and remain 0mb, which means you are unable to make a backup.
However if you're happy with it in that state...

Re: bootloop
have you tried grabbing the no verity/encrypt form the rooting forum, this solves seandroid problem