Database Users

Nero v3 infinite reboot issue

Hi guys
So I installed Nero v3 on my Vibrant, and all is well. I followed the steps on the Nero thread. I like it very much.
Then I decided to flash my gf's phone. It seemed to go well at first, but then some odd stuff started happening. First, I can't open the "Settings" menu - nothing happens. Second, lots of stuff force-closes all the time.
Those two are minor issues, though. Somewhere between 5-15 minutes after flashing, the entire GUI will force close. The phone will vibrate, then the Team Whisky logo will appear again (as if rebooting), and the GUI will appear and begin the regular startup procedure. It will get as far as "Preparing internal SD card" before the GUI will crash again. This cycle continues indefinitely. Once it has begun, not even pulling the battery and rebooting it will solve the problem.
Any advice?
My plan is to find a way to back up the SD card data and format it, since it always crashes on "Preparing internal SD card." However, I doubt this will help, since the other issues (constant force-closes) don't seem to have anything to do with that.

stoanhart said:
Hi guys
So I installed Nero v3 on my Vibrant, and all is well. I followed the steps on the Nero thread. I like it very much.
Then I decided to flash my gf's phone. It seemed to go well at first, but then some odd stuff started happening. First, I can't open the "Settings" menu - nothing happens. Second, lots of stuff force-closes all the time.
Those two are minor issues, though. Somewhere between 5-15 minutes after flashing, the entire GUI will force close. The phone will vibrate, then the Team Whisky logo will appear again (as if rebooting), and the GUI will appear and begin the regular startup procedure. It will get as far as "Preparing internal SD card" before the GUI will crash again. This cycle continues indefinitely. Once it has begun, not even pulling the battery and rebooting it will solve the problem.
Any advice?
My plan is to find a way to back up the SD card data and format it, since it always crashes on "Preparing internal SD card." However, I doubt this will help, since the other issues (constant force-closes) don't seem to have anything to do with that.
Click to expand...
Click to collapse
Was her phone stock before you started tinkering with it?
In any case I'd suggest re-download nerov3 (to avoid corrupted download issue), ODIN back to JFD (remove the ghosts from the past ROM's) and reflash.

Phone was stock aside from rooting for the purpose of TitaniumBackup. It has never had anything installed on it.
I'm currently Odin flashing back to stock, and I'll give it another shot.

stoanhart said:
Phone was stock aside from rooting for the purpose of TitaniumBackup. It has never had anything installed on it.
I'm currently Odin flashing back to stock, and I'll give it another shot.
Click to expand...
Click to collapse
Good luck!

Well, I did the Odin flash to stock, then installed Nero. After first boot, I left it untouched for 20 minutes or so, and then did a clean reboot. Upon starting up, I was once again stuck in the loop.
Boo

stoanhart said:
Well, I did the Odin flash to stock, then installed Nero. After first boot, I left it untouched for 20 minutes or so, and then did a clean reboot. Upon starting up, I was once again stuck in the loop.
Boo
Click to expand...
Click to collapse
Did you re-download nero? It might be a corrupted download, I haven't seen anyone with the same symptoms.
Does it happen if Voodoo is disabled?
EDIT: Saw that you didn't even have a chance to enable it, hmm, try a different ROM? Axura or Eugene's work.

No, I didn't try re-downloading it. Perhaps I'll give that a try, although it is the same file I flashed onto my phone.
After a bit of time playing with Nero, though, I'm considering going back. The parts that work are slick and wonderful, but it very much feels like beta software. In particular, scrolling lists or web pages is choppy. I've heard this criticism of Android before, but I've never experienced it with the original Vibrant software. It was always so smooth. It makes me think that maybe Samsung was using GPU acceleration in some places. Also, I seem to have some problems with the touchscreen becoming unresponsive, especially in the browser if it's blocked waiting for data (another bug...).
Is it possible to run the JL5 modem on the stock image? That would be great.

[SOLVED] Suddenly G2 boots only into recovery mode (loop)

Sometime last night, my AT&T G2 (D800) decided to go from being powered on and idling, to going into TWRP recovery mode. All by itself. I saw this, unplugged it from USB, and tried to reboot into system mode. But it simply won't do anything except boot into recovery. Powering off, trying to get to the bootloader, none of that works.
This is not a custom ROM, it's 4.2.2 stock from LG. I only rooted the phone, which was several weeks ago, and haven't had any problems, aside from TWRP not wanting to back up anything. I've been using Android since the original TMO G1 with JesusFreke's ROM, so I have a pretty good idea of what I'm doing, hopefully.
The only recent changes I've made are:
I updated busybox about 3 days ago (but have rebooted fine since)
I grabbed several legit apps from the market last night
Last night I also DL'ed, but did not apply, a ~50MB OTA update that has been pending. I don't think that would install without explicit permission anyway, which I didn't give it?
This phone was encrypted from the start. Maybe that;'s what prevents TWRP backups,, but right now I'm seeing TWRP errors/logs saying something like "Unable to mount \data". And yet I can browse to other folders, and see filenames in \etc for example. However, I don't see any files at all in \boot.
Since this phone has no external memory, and it's customized and has numerous configured apps, I really really don't want to have to wipe it. Although at this point, that may not even fix the problem? Even if it did, since I haven't been able to make backup images, it would be a Bad Thing™ either way. (Yes, I do have a secondary plan with Titanium, with backups going to cloud storage, but these are tedious and now a few weeks old. And wouldn't restore the ROM & system en masse.)
Please help.

Solved?
I'm not sure what caused this to occur, but I found somewhat of a solution after digging deep into my Google-fu.
I followed the instructions in this XDA thread and it actually worked. I didn't have adb access, but I was able to use dd successfully. It allowed me to boot into the device, unencrypt it, then arrive at the lock screen.
However, when I put in the lock code, it went apesh!t and played multiple notification sounds, with a blue circular wait symbol. It also flashed the LED from green to blue, as it normally only does during boot. Once I pressed the power button, I was back back into TWRP.
So then I followed Step 2 again, and once in the phone, I used terminal to run the dd command from inside the OS. This might be what it ultimately needs, because the prior attempt in TWRP had an error to the effect of "no space left on device".
I can't call it Solved yet, but it looks good to at least be able to get in and use the phone. I'm backing up with Titanium before I do anything else and will reboot and test its permanency later.

I'm gonna close this thread now that I think I have a handle on what is going on. The fix does survive a reboot, so I believe it's possible to repair the issue permanently per the instructions above. I also ran the phone for 3 hours with heavy app usage and no problems.
I believe what may have happened is my OTA decided to override my choice to NOT update the ROM, as some have reported in this Reddit thread. There's a lot of good info in that one, including how to stop getting nagged by turning the OTA notifications off, or to freeze it entirely with Titanium Backup if rooted.
Anyway, what apparently happens is that when the OTA/upgrade goes to reboot, and encounters a custom recovery, it gets confused... when you try to power cycle or reboot again, it sees the stock recovery still hasn't run whatever it wanted, so it starts recovery again Lather, rinse, repeat.
Fun times.

[Q] Galaxy S4 restarts every 10 minutes

Well for starters, high everyone!
I have an issue with my S4 and I've searched all over but none of what has been recommended helps.
The issue I have is that my phone will restart about every 10 minutes (give or take). I used Reboot Logger to determine this. The phone only restarts when it is idle. It WILL NOT restart if I am using it (screen is on). The weird part is that it doesn't even go through the whole reboot sequence. The screen will stay black the entire time. The notification button pulses and the home buttons will light up like it was restarting though.
I had a bad battery and had it replaced with a stock Samsung battery. I've tried pulling the SD card, pulling the battery for 10 minutes, pulling the battery while the phone is on, and I've performed two factory resets.
The one thing I have noticed is that, after performing the factory reset, I get an "error" under the little android dude. This also happens if I do a cache wipe.
My model is the SPH-L720 running on android v4.3. The phone has never been rooted and there are no software or firmware updates that are found.
I was beginning to think that this was a hardware issue but the consistency in reboot intervals makes me believe otherwise. At this point I'm at a loss. I rooted my old phone but my experience in that area is very limited. I have read that the cache partition is bad from the factory on some of these (hence the error message) so I was thinking about rooting the phone and trying to use a good cache partition, but that's the only other option I could think of.

sounds like a voltage prob....or mem prob... id redownload a new rom..wipe wipe wipe..reinstall and that should fix it
Sent from my SPH-L720 using xda app-developers app

Insufficient voltage at idle was my first thought too, but if you haven't undervolted (since you aren't even rooted), that seems less likely. If I were you, I'd root the phone so I could do more to figure things out. Maybe try bumping up the voltage a little on the lower clock speeds.

Ok, first of all, do not root your phone. As you admitted yourself, you have limited experience in this area, and there is nothing that rooting will do for you. Not to mention, if you think you have a bad cache partition, you don't need root to fix it. Your phone is stock, running the stock kernel, there is no reason to suspect voltage issues that are not hardware related. If you root the phone, you will likely trip KNOX, and void your warranty.
My personal opinion is that your phone has a hardware problem. If you want to truly start over, either recover your phone through KIES, or better yet, download and flash via ODIN a stock MK2 ROM from this forum. Since this is a stock, signed ROM, you will not trip KNOX, and it will rewrite every partition properly on it's own. This is all assuming you don't have a hardware problem. But do not go ahead and try to fix anything yourself besides what I mentioned. You will not succeed, and likely lose your warranty in the process.
Edit: did you buy this phone new or used? If you bought it used, more than likely somebody ruined it for you. And more than likely, you can fix it. If this was a new device, more than likely it will be a warranty issue. That's why you shouldn't do anything to void the warranty.

If you're going to use odin for anything, just make sure you follow someone's directions step by step. Otherwise very bad things can happen.

im also having a slightly similar problem
Problem : The screen after a sleight amount of time of being on, or sometimes instantly when opening the lockscreen it freezes for 10-15 sec then shoots black lines across it, then reboots.
Things ive tried :
1. Installing a new rom ( from AOKP 4.4 and Triforce 4.3)
2. Changing modem (from MJA, MK2, NAE)
3. Changing the type
of Gapps i was using. (4.3 gapps for triforce, aokp 4.4 gapps, and pa gapps)
Current Phone Info:
Rom: aokp_jfltespr_kitkat_nightly_2014-02-08
Modem/Firmware: NAE
Gapps: Pa.gapps 4.4.x
Let me know if you need anything more! plz!

I'll look into Odin before I root. The phone was also purchased new. I spent most of today monkeying around with different settings to see if I could trigger the issue as well. As it turns out, the phone will only restart at idle if it's plugged into the charger, or the wifi is on. If wifi is off and it's not plugged in it's fine. I am also using the stock Samsung charger that came with the phone. Again though, if I'm actively using the phone it doesn't happen (charging or connected to wifi). I did turn the phone off earlier to charge it but would keep freezing at the sprint logo upon boot up. I thought it was bricked for a second... I wiped the cache (didn't do a factory reset) and that fixed it, but now I have that stupid issue where videos won't play on wifi, only on 4G or 3G. It's an issue I thought I had solved.
Le sigh. This is frustrating. The Odin option is looking to be my best bet it seems.

Tizamarou said:
im also having a slightly similar problem
Problem : The screen after a sleight amount of time of being on, or sometimes instantly when opening the lockscreen it freezes for 10-15 sec then shoots black lines across it, then reboots.
Things ive tried :
1. Installing a new rom ( from AOKP 4.4 and Triforce 4.3)
2. Changing modem (from MJA, MK2, NAE)
3. Changing the type
of Gapps i was using. (4.3 gapps for triforce, aokp 4.4 gapps, and pa gapps)
Current Phone Info:
Rom: aokp_jfltespr_kitkat_nightly_2014-02-08
Modem/Firmware: NAE
Gapps: Pa.gapps 4.4.x
Let me know if you need anything more! plz!
Click to expand...
Click to collapse
Since you are running a custom source-built ROM, first thing to do would be to ODIN a stock ROM. If the problems go away, you have your answer. If not, this would likely be a warranty issue. Of course you tripped KNOX most likely already.

sputnik767 said:
Ok, first of all, do not root your phone. As you admitted yourself, you have limited experience in this area, and there is nothing that rooting will do for you. Not to mention, if you think you have a bad cache partition, you don't need root to fix it. Your phone is stock, running the stock kernel, there is no reason to suspect voltage issues that are not hardware related. If you root the phone, you will likely trip KNOX, and void your warranty.
My personal opinion is that your phone has a hardware problem. If you want to truly start over, either recover your phone through KIES, or better yet, download and flash via ODIN a stock MK2 ROM from this forum. Since this is a stock, signed ROM, you will not trip KNOX, and it will rewrite every partition properly on it's own. This is all assuming you don't have a hardware problem. But do not go ahead and try to fix anything yourself besides what I mentioned. You will not succeed, and likely lose your warranty in the process.
Click to expand...
Click to collapse
Alright I'm a little confused as to what exactly I should be using. I found this:
http://forum.xda-developers.com/showthread.php?t=2575470
which is a stock ROM. Although I also found this:
http://forum.xda-developers.com/showthread.php?t=2259513&highlight=odin
which is the stock firmware.
Which one do I use, or do I use both of them?

Dfeeds said:
Alright I'm a little confused as to what exactly I should be using. I found this:
http://forum.xda-developers.com/showthread.php?t=2575470
which is a stock ROM. Although I also found this:
http://forum.xda-developers.com/showthread.php?t=2259513&highlight=odin
which is the stock firmware.
Which one do I use, or do I use both of them?
Click to expand...
Click to collapse
Neither. Use this one : http://forum.xda-developers.com/showthread.php?t=2601443
Follow instructions in the thread. This is a completely stock rom with no root or mods and will not trip the Knox bootloader. If you flash anything other than this, including custom recovery, cf autoroot, etc, you will void your warranty.

rebooting
i had this problem once and it was related to a corrupt file on my sdcard believe it or not. there are Defraggers out there for your android file system and internal SD card but your Ext sc you would have to do on your PC. it worked for me. the one i used is called CLEAN i got it off amazon app store.
cyberweasal
Dfeeds said:
Well for starters, high everyone!
I have an issue with my S4 and I've searched all over but none of what has been recommended helps.
The issue I have is that my phone will restart about every 10 minutes (give or take). I used Reboot Logger to determine this. The phone only restarts when it is idle. It WILL NOT restart if I am using it (screen is on). The weird part is that it doesn't even go through the whole reboot sequence. The screen will stay black the entire time. The notification button pulses and the home buttons will light up like it was restarting though.
I had a bad battery and had it replaced with a stock Samsung battery. I've tried pulling the SD card, pulling the battery for 10 minutes, pulling the battery while the phone is on, and I've performed two factory resets.
The one thing I have noticed is that, after performing the factory reset, I get an "error" under the little android dude. This also happens if I do a cache wipe.
My model is the SPH-L720 running on android v4.3. The phone has never been rooted and there are no software or firmware updates that are found.
I was beginning to think that this was a hardware issue but the consistency in reboot intervals makes me believe otherwise. At this point I'm at a loss. I rooted my old phone but my experience in that area is very limited. I have read that the cache partition is bad from the factory on some of these (hence the error message) so I was thinking about rooting the phone and trying to use a good cache partition, but that's the only other option I could think of.
Click to expand...
Click to collapse

sputnik767 said:
Neither. Use this one : http://forum.xda-developers.com/showthread.php?t=2601443
Follow instructions in the thread. This is a completely stock rom with no root or mods and will not trip the Knox bootloader. If you flash anything other than this, including custom recovery, cf autoroot, etc, you will void your warranty.
Click to expand...
Click to collapse
That solved my problem, thank you! I spent the last couple days testing it just to be sure I wouldn't be crying wolf. The phone has yet to restart on me even while charging or using wifi. The error message I would receive after a cache wipe or factory reset went away as well. It makes me wonder if the bad partition was what caused my old battery to fail.

Dfeeds said:
That solved my problem, thank you! I spent the last couple days testing it just to be sure I wouldn't be crying wolf. The phone has yet to restart on me even while charging or using wifi. The error message I would receive after a cache wipe or factory reset went away as well. It makes me wonder if the bad partition was what caused my old battery to fail.
Click to expand...
Click to collapse
Great, I am glad it worked out, and hopefully your problem is resolved. I doubt that your old battery failed due to a bad partition, and I have to wonder how your partition got messed up in the first place, but that's just a curiosity and is irrelevant in the grand scheme of things. Just remember that if you decide to root, cf_autoroot works but will trip the KNOX bootloader and potentially void your warranty.

[Q] Galaxy S4 won't boot past recovery (urgent)

This is somewhat urgent because I am leaving the country for two weeks on Friday, and need a working phone. I am not sure what happened today, but my Sprint Galaxy S4 (SPHL720TBK) wouldn't connect to WIFI at my house. My tablet would, so I know it was a phone issue. I rebooted then was going through settings, and just checking things. The phone rebooted itself, and when it came back up, it went through a couple of screens, one of which asked about activation. It seemed like it was installing an update from Sprint, which it had been trying to do for a week or so. But it kept failing, saying it didn't have enough space for the download, despite there being several GB free internally and on the SD card. (I figured it must be because it was rooted). After a couple of additional screens on which I could only answer OK, the phone rebooted again, and that was it. It would not boot again. I decided to power off the phone and deal with it tonight. I can boot into recovery, and connect with Odin. I can boot to recovery and connect with ADB (in sideload mode). I know I could just do a factory reset, but unfortunately, I do not have a full backup since the end of January, and I would rather not lose everything. The phone was running v 4.4.2. I had rooted the phone several months ago with CF Auto Root using CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5, so it was essentially stock, but rooted. Is there anything I can do to get the phone back on its feet that will not lose everything? Or anyway to copy data from the phone with it in this state? Any assistance will be VERY much appreciated! Thanks!

Fixed it myself
andrewt2323 said:
This is somewhat urgent because I am leaving the country for two weeks on Friday, and need a working phone. I am not sure what happened today, but my Sprint Galaxy S4 (SPHL720TBK) wouldn't connect to WIFI at my house. My tablet would, so I know it was a phone issue. I rebooted then was going through settings, and just checking things. The phone rebooted itself, and when it came back up, it went through a couple of screens, one of which asked about activation. It seemed like it was installing an update from Sprint, which it had been trying to do for a week or so. But it kept failing, saying it didn't have enough space for the download, despite there being several GB free internally and on the SD card. (I figured it must be because it was rooted). After a couple of additional screens on which I could only answer OK, the phone rebooted again, and that was it. It would not boot again. I decided to power off the phone and deal with it tonight. I can boot into recovery, and connect with Odin. I can boot to recovery and connect with ADB (in sideload mode). I know I could just do a factory reset, but unfortunately, I do not have a full backup since the end of January, and I would rather not lose everything. The phone was running v 4.4.2. I had rooted the phone several months ago with CF Auto Root using CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5, so it was essentially stock, but rooted. Is there anything I can do to get the phone back on its feet that will not lose everything? Or anyway to copy data from the phone with it in this state? Any assistance will be VERY much appreciated! Thanks!
Click to expand...
Click to collapse
Since I didn't spark enough interest for anyone to offer advice, had to spend most of the afternoon/evening fixing these problems myself. Everything seems to be working, so I thought I would pass along key parts of this hard-learned lesson in case anyone else finds himself in such a situation.
First I booted into adb sideload mode, which is all I could do anyway. I installed philz_touch_6.23.9-jflte.zip and the aromafm.zip. I was then able to boot into a "normal" recovery mode. Aromafm was troublesome, and I eventually had to manually put the zip into place for it to work consistently. These are both WONDERFUL , and I highly recommend them both. Thanks very much to the creators! I used the file manager to find the files that I didn't want to lose, and used ADB to pull the files over to my PC. (ADB pull <source> <target>) Then I did a full wipe and factory reset. That did little other than delete all my data, which I had already copied anyway. The phone still would not boot past recovery.
I tried to use ADB to install a new ROM, but got a variety of errors. My phone being an L720T, there are not many ROM's available, at least not for which I could find functioning links. I finally found a TAR, L720TVPUBNG5_L720TSPTBNG5_L720TVPUBNG5_HOME.tar.md5, and used ODIN v3.09 to install that.
I still need to go back and re-root the phone, and install lots of APPS and restore data, but at least I have a functioning phone, and I can do the rest on my plane ride tomorrow.
I found the information I needed in a variety of posts here on xda developers, and would not have been able to get through this without all the helpful advice posted to other threads. So thanks to all of you for the wealth of information available here!

[A2017G] LineageOS 14.1 - Can not access TWRP anymore, can't get through setup either

Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks

OmegaFighter said:
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
Click to expand...
Click to collapse
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty

Choose an username... said:
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Click to expand...
Click to collapse
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.

OmegaFighter said:
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
Click to expand...
Click to collapse
good