Develop Bugs

G2 reverts itself to previous day?

Hi guys, my friend has an unrooted, stock gingerbread G2 that every so often will turn itself off and revert itself a couple of days. Like a nandroid restore almost. Say he takes some pictures and downloads some apps. A few days later it will crash and turn itself back on, but the apps and pictures he downloaded will be gone and it will be as if he never downloaded them. I'm not sure how else to describe it.. any ideas? He says he thinks it has to do with putting music on it because whenever he puts on new music it will crash and revert shortly after to before the music was put on the phone.
Sent from my Galaxy Nexus using xda premium

I cannot imagine how that would be possible without some sort of backup/restore software that would need root. Sure your mate isn't winding you up?

that sounds strange...
maybe he should do a real factory reset or wipe cache?
EDIT: push power & volume down to enter bootloader / here choose recovery and red triangle will show up then press power & volume up to enter recovery (just for the case that you don´t know, because you seem to have a nexus)

That sounds like a serious problem, either he's pulling your leg or something is wrong with the phone. I'd definitely say backup whatever he needs, and then give wiping the phone a chance because losing pictures and data like that isn't cool.

I've heard that some ROMs writeback and requires a complete shutdown or restart cycle to commit various information and the new stock gb might be doing that.
Try having your friend do a restart (proper one, not battery pulling) after the installation of apps and all that to see if the problem persists. If it does, then I would suggest a factory wipe and start from scratch since something is really screwing with your friend's phone
Sent from my Desire Z via XDA App

Hi guys, thanks for the responses!
I don't think he's pulling my leg because he's not the kind of person to do something like that, nor does he really know enough about phones to just think of something like this on the spot..
I will have him try to do a proper reset as mputtr suggests before doing a full wipe, but in any event thanks again for the ideas

Reboot Loop NEW FINDINGS

Hey guys, my gnex has just been stricken (for the second time) by the boot loop. Managed to fix it last time with a flash of the google image, but this time it isnt working.
Same as usual, mine features the greyed out wifi toggle as well, and reboots every time the screen goes off (which makes sense that I've been noticing it go off every 2 minutes).
I have found that the device will not reboot if it is plugged in and set in the dev options to "stay awake" while charging. This seems to keep it running, same if I set the time-out to longer. My theory has to do with the distribution of power...I think that something is telling the phone it doesn't have enough power to function.
Like everyone else I've done endless factory resets, flashed the goog image and such and such to no avail. Currently stock but I left my bootloader unlocked atm. I can still boot into recov and everything and even flash other roms.
Has anyone else noticed this, or could someone who is also having the problem confirm the screen thing?
I think last time I posted I was on winmo, missed this forum.

Bump? Anyone else having this issue?

Just send it in for warranty. I sent mine in and Samsung exchanged the phone

I havent been paying attention, are many people having this issue? It sounds scary. Were you on a custom rom when this started?

My Nexus has been stuck on "Turning WiFi on.." since I've had it. It would also constantly boot loop itself whenever the screen went off. I flashed the new AOKP build to avoid this issue, however, the WiFi still does not work If I'm ever on stock again, I'll give stay awake a shot.
I live in the U.S. with the GSM GNex, so warranty is out of the question unfortunately.

Fixed the loop by flashing aopk again with franco's kernel. Brilliant but my Wifi is still messed up. I flashed a new baseband XXKL1 and no improvements. I'm gonna just wait it out for a bit because I've seen some threads elsewhere where that has actually worked, but who knows. I'll probably cave and send it out soon.

RogerPodacter said:
I havent been paying attention, are many people having this issue? It sounds scary. Were you on a custom rom when this started?
Click to expand...
Click to collapse
Yes and no. It happened twice and the second time I fixed it by going FROM stock to AOPK with included kernel. Now it happened on THAT setup so I went back to stock and no dice. Its a very weird problem....

I got exactly the same problem. Wifi didn't work (grey toggle) so I tried to bring the warranty conditions back, but got an endless boot each time screen goes off.

mastergrifis said:
I got exactly the same problem. Wifi didn't work (grey toggle) so I tried to bring the warranty conditions back, but got an endless boot each time screen goes off.
Click to expand...
Click to collapse
Try booting into the bootloader and using the gnex toolkit to go back to stock and relock. Good luck. Logcat isnt even logging my wifi issues, its like my wifi adapter was removed entirely.

ShatteredAxe said:
Try booting into the bootloader and using the gnex toolkit to go back to stock and relock. Good luck. Logcat isnt even logging my wifi issues, its like my wifi adapter was removed entirely.
Click to expand...
Click to collapse
That's what I did, I used the toolkit to go back to stock and after that I got those annoying reboot. Of course wifi doesn't work anyway... That's really frustrating

mastergrifis said:
That's what I did, I used the toolkit to go back to stock and after that I got those annoying reboot. Of course wifi doesn't work anyway... That's really frustrating
Click to expand...
Click to collapse
You and I are in the EXACT same boat my friend. I just cant afford being without this phone, my job depends on social media and email. DAMN YOU SAMSUNG!!!!!

ShatteredAxe said:
You and I are in the EXACT same boat my friend. I just cant afford being without this phone, my job depends on social media and email. DAMN YOU SAMSUNG!!!!!
Click to expand...
Click to collapse
I have a Desire Z by my side, but of course I want my Gnex back as new. The only thing that scares me is the warranty. I'm not sure if it's still valid. I mean, apparently there's no sign of root/bootloaderunlocked, but how can I explain that suddenly my phone has started rebooting itself without any reasons?

Yeah, only option is to just try and see what happens.

Galaxy Nexus freeze after unlock **UNROOTED** troubleshooting

Alright, so here is what's going on.
I had my alarm go off earlier today, got up, unplugged my phone like normal. I swiped off the notifications I didn't care about like a tapatalk message etc. I noticed that Google Current's automatically updated. I'm sure that's no huge deal.
I locked the screen and went about my day. I tried to swipe to unlock, and the phone freezes and reboots. The phone is responsive until you unlock it, then it just freezes and reboots.
Tried safe mode once, and it worked fine. I then turned it off, and tried normally booting again, same freezing and rebooting. So I went to go back to safe mode, and now safe mode is doing the same thing, which means that a factory reset is now out of the question.
What the hell man.
Specs:
- Samsung Galaxy Nexus
- All stock apps except added Facebook and Tapatalk
- Jellybean 4.2.2 software I believe. I'd double check if I could.
- Still locked and unrooted
Any ideas on where to go from here? No warranty, so any ideas would help
It turns on, goes to lock screen. Then freezes when I try to get anywhere from that lock screen. Even on safe mode.
Then it will reboot automatically after about 30 seconds.
I should note I received a text in this time, and thought maybe just pulling the notification bar down and going straight to the text would work. The notification bar works, but when I hit the text, it froze the same way.
This must be some sort of self check or some Android process crashing. But I can't utilize safe mode to fix it.
Any ideas on what to do? I know there are threads with this problem, but this involves an unrooted phone, of which I have seen no threads, or threads with answers. I am not experienced with getting too far into Android, so just a direction to go, or something to try when I get home would be awesome. (At work currently)
The only options I have right now are the options upon booting with the volume down, which are Start - Restart bootloader - Recovery Mode and Turn off. In this screen, here is my info:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro 16GB
HW VERSION - 9
BOOTLOADER VERSION - PRIMELA03
BASEBAND VERSION I9250UGLL1
CARRIER INFO - NONE
SERIAL NUMBER - xxxxxxx
SIGNING - production
LOCK STATE - LOCKED
In recovery mode, I see a dead android guy with a red triangle and an exclamation mark in it.
I realize you guys probably get a lot of dumb questions so I tried unloading all the information I could. My replies will be 5 minutes apart, as I'm new and I see that's a restriction on being here.
Thanks in advance

You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.

Daedalus93 said:
You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.
Click to expand...
Click to collapse
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.

slipstreamconversion said:
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.
Click to expand...
Click to collapse
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme

Daedalus93 said:
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme
Click to expand...
Click to collapse
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again

slipstreamconversion said:
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again
Click to expand...
Click to collapse
Yes. My phone recently was stuck on a bootloop and I've already sent it for repair. Yeah drops are never good
No problem

HTC 10 performance issues

Hi everyone, I am having few issues with my HTC 10. I bought this from HTC pre-order it from them. It was working fine for 2 weeks but now its just getting to be a pain for the past 2 weeks. I dont have a lot of third part apps installed on the phone hard 4-5 and are basic apps. Other than that I my usage is normal. I have checked everything and there is nothing that is spiking the processor or memory.
1: The phone lags a lot while scrolling or opening the main apps. I will press somewhere and it literally takes 2 seconds for it to open or execute it.
2: I am a normal user and only use the data services when needed. The screen brightness is between 40-50 % but battery does not even last a day. Again I have nothing on my phone that would be using a lot of battery.
3: My phone forget to connect to saved network using Wi-fi I mostly have to manually go to setting and chose the device to connect to it.
Using the power saving mode is the same and at times is even worse. The performance is just pissing me on this phone.
Any one with any ideas on this would be greatly appreciated.

factory reset

ruizit0 said:
factory reset
Click to expand...
Click to collapse
Or if you want to evade this as long as possible go into recovery and wipe Cache.

ruizit0 said:
factory reset
Click to expand...
Click to collapse
I did the factory reset and still the wi-fi issue. I will test it out for few days and see if the remaining two issues return.

that wifi issue happens only on your home wifi or other wifi to ? Seems your home router configurations, try on another networks.

ruizit0 said:
that wifi issue happens only on your home wifi or other wifi to ? Seems your home router configurations, try on another networks.
Click to expand...
Click to collapse
It was on my home network. Its been better now but I was having an issue with mobile data too. If I turned it off and then tried to turn mobile data on again it won't turn on. I would have to choose airplane mode and then turn that off and then turn on data to make it work.
The issue stopped after the factory reset. But I had that again. Originally the issues started after two weeks of use. Still have few days to go and hoping that it works fine, cause if does not that's going to piss me a lot as I don't have anything on my phone that should give me performance issues.
I had M8 before this and I loved that phone, in fact I love HTC in general it's just the thing about this amount of money+such hardware specs= awesome performance.

you on factory rom right or any custom rom ? if it's factory rom and if you are still experiencing all that issues after a factory reset, well or you doing something wrong or you need to return your phone because it's not right.

HELP!! S20 Ultra stuck in boot loop during REGULAR USE, Wont go in Recovery Mode!!

Hello all,
I need some serious help here. I was using my Samsung Galaxy S20 Ultra when DURING USAGE, the phone decided to reboot. It is rare but it happens. But the problem escalated when it refused to reboot again. It has constantly been in a boot loop ever since. It did fully RESTART TWICE in the middle but before I could unlock the phone it slipped back into its boot loop coma.
Everything on the phone is stock, updated to the latest versions for all I know. No combination of power and volume buttons help. What it only does it switch it from boot loops to a static boot screen.
ANY HELP OR EXPLAINATION WILL BE APPRECIATED !!
Sincerely,
SRV

These phones should never spontaneously reboot. That indicates a potentially severe problem; always take any sign of system instability seriously. Often it's the only warning you get before a boot loop.
You need to get into safe mode or the boot menu to do a factory reset. Make sure you're using the proper sequence and timing matters. Try holding the power button down for at least 30 seconds.
Poorly written apps can do this. It may be the firmware was corrupted (possibly a single event upset) or a hardware failure. Play with it...

@blackhawk
I have tried:
power button hold for long
power button + volume up
power button + volume down
all three
The current situation is:
It is stuck on boot screen for 5~10 random minutes then starts cycling again. What do you figure could be the reason for it to have fully restarted (then gone back bootlooping) when the situation was fresh ?
Do you think i should let it drain out ? (How long would it take lol)
Perhaps try unplugging the battery/ removing SD card WHILE its still booting ?

Don't know, not normal behavior. Maybe someone else has seen this before.
Try pulling the SD card* and sim card.
Try hooking up to the PC. Let it drain out ie hard reboot. Anything to break the cycle.
*it's backed up, right?

My S20U had the exact same issue last year. I had to send it in for repair and they replaced the motherboard.

planeinmountain said:
My S20U had the exact same issue last year. I had to send it in for repair and they replaced the motherboard.
Click to expand...
Click to collapse
You weren't able to get it in recovery at all right ? and how much did it end up costing you ?

blackhawk said:
Don't know, not normal behavior. Maybe someone else has seen this before.
Try pulling the SD card* and sim card.
Try hooking up to the PC. Let it drain out ie hard reboot. Anything to break the cycle.
*it's backed up, right?
Click to expand...
Click to collapse
I let it drain to zero, it calmly powers off and saves a tiny amount of battery just to display the 0% battery image when I try to turn it on. The the moment I plug it back in, bootloop.
Though I'm sure you mean let it drain dead zero, I've left it to do that.

panzer27 said:
I let it drain to zero, it calmly powers off and saves a tiny amount of battery just to display the 0% battery image when I try to turn it on. The the moment I plug it back in, bootloop.
Though I'm sure you mean let it drain dead zero, I've left it to do that.
Click to expand...
Click to collapse
The last really good flagship Samsung made was the N10+ snap. Everything that followed has had hardware issues, mostly the displays. The only way you know there are issues though is when people post about them on forums. Who knows what the actual number is? Only Samsung and those wimps won't owe up to it.
It may still be a firmware issue and not hardware.
If it is hardware it may be an issue with a ribbon cable or other module, and not the mobo. A Samsung Experience center at Best buy may be able to help and reflash it. Don't give up quit yet.
Yes drain it until it won't try to boot and the battery auto shuts down. You probably saw a "robound" effect where the battery recovered enough to have enough power to boot.
If it needs a mobo consider the repair price vs the price of a new (still available) or used N975U1/N975U. In my opinion this is a better Note in spite of some of the missing features. Just a rock solid work horse that's form factor is superb, well balanced with perhaps the best display in terms of color/gamma accuracy and calibration. I have two of them... no regrets. They are a joy to use.
The 3 yo one has over 8k hours on it and it looks, feels and runs like new, zero display degradation.
Only repair has been a battery replacement. A new one will be loaded with Android 10 which I prefer over 11/12. Pie though is still my favorite and the oldest one is still running on Pie.
I'm not pleased with Samsung's flagships since the N10+... Samsung just keeps dropping balls and lives on hype rather than solid performance.
Sammy, you suck elephant balls bad now.

My wife and I also experienced a similar issue with our S20 Ultra 5G. Except ours was an update that literally just killed the device. We tried every combination of buttons to get into recovery or bootloader mode with no success. Ultimately we had to send the device to a Samsung service center to have the LCD, battery and motherboard switched out.

blackhawk said:
The last really good flagship Samsung made was the N10+ snap. Everything that followed has had hardware issues, mostly the displays. The only way you know there are issues though is when people post about them on forums. Who knows what the actual number is? Only Samsung and those wimps won't owe up to it.
It may still be a firmware issue and not hardware.
If it is hardware it may be an issue with a ribbon cable or other module, and not the mobo. A Samsung Experience center at Best buy may be able to help and reflash it. Don't give up quit yet.
Yes drain it until it won't try to boot and the battery auto shuts down. You probably saw a "robound" effect where the battery recovered enough to have enough power to boot.
If it needs a mobo consider the repair price vs the price of a new (still available) or used N975U1/N975U. In my opinion this is a better Note in spite of some of the missing features. Just a rock solid work horse that's form factor is superb, well balanced with perhaps the best display in terms of color/gamma accuracy and calibration. I have two of them... no regrets. They are a joy to use.
The 3 yo one has over 8k hours on it and it looks, feels and runs like new, zero display degradation.
Only repair has been a battery replacement. A new one will be loaded with Android 10 which I prefer over 11/12. Pie though is still my favorite and the oldest one is still running on Pie.
I'm not pleased with Samsung's flagships since the N10+... Samsung just keeps dropping balls and lives on hype rather than solid performance.
Sammy, you suck elephant balls bad now.
Click to expand...
Click to collapse
Thanks for your inputs...
I let the battery drain condiderably, then with that low battery, I just pressed power button. Voila, recovery screen.
I have wiped the cache partition and am waiting for it to reboot (which the command line the screen says)
Does it say "rebooting..." for a long time or am I screwed further ?

panzer27 said:
Thanks for your inputs...
I let the battery drain condiderably, then with that low battery, I just pressed power button. Voila, recovery screen.
I have wiped the cache partition and am waiting for it to reboot (which the command line the screen says)
Does it say "rebooting..." for a long time or am I screwed further ?
Click to expand...
Click to collapse
Go for safe mode at the most. Normal mode will likely loop you again.
If you don't need to recover data> factory reset most rikky tik. Clearing the cache for this won't do squat.
The user data partition is corrupted at the least. If a factory reset clears the boot loop, be careful what you reload... or you'll be doing this again.
This is assuming the loop was caused by a 3rd party app or malware. A definite possibility.
Remember if you encrypted the SD card a factory reset will wipe that key and your access.

blackhawk said:
Go for safe mode at the most. Normal mode will likely loop you again.
If you don't need to recover data> factory reset most rikky tik. Clearing the cache for this won't do squat.
The user data partition is corrupted at the least. If a factory reset clears the boot loop, be careful what you reload... or you'll be doing this again.
This is assuming the loop was caused by a 3rd party app or malware. A definite possibility.
Remember if you encrypted the SD card a factory reset will wipe that key and your access.
Click to expand...
Click to collapse
I am dead sure it is Malware.
I got it up and running and looping a few times now. The battery draining probably cleared some flags that prevented a normal reboot.
Phone has survived a minute in safe mode. Let's see

blackhawk said:
Go for safe mode at the most. Normal mode will likely loop you again.
If you don't need to recover data> factory reset most rikky tik. Clearing the cache for this won't do squat.
The user data partition is corrupted at the least. If a factory reset clears the boot loop, be careful what you reload... or you'll be doing this again.
This is assuming the loop was caused by a 3rd party app or malware. A definite possibility.
Remember if you encrypted the SD card a factory reset will wipe that key and your access.
Click to expand...
Click to collapse
Current status is that it stays on for 2~5 minutes.
There is a software update should I go for it ?

panzer27 said:
Current status is that it stays on for 2~5 minutes.
There is a software update should I go for it ?
Click to expand...
Click to collapse
Negative. Keep the playing field level. An update now could brick it.
Factory reset if you can. No known rootkits can worm out of the user data partition on Android 9 or higher. A factory reset will purge it if that's the cause. Kill the intruder.
Delete your Samsung and especially Google accounts in settings first if possible. Reset your Google account password after you factory reset, write it down. If it was malware try to figure out when, where and how it breached the device. Any odd behavior that signaled the event.

blackhawk said:
Negative. Keep the playing field level. An update now could brick it.
Factory reset if you can. No known rootkits can worm out of the user data partition on Android 9 or higher. A factory reset will purge it if that's the cause. Kill the intruder.
Delete your Samsung and especially Google accounts in settings first if possible. Reset your Google account password after you factory reset, write it down. If it was malware try to figure out when, where and how it breached the device. Any odd behavior that signaled the event.
Click to expand...
Click to collapse
I should have read this on time, I wen for the software update Wont go beyond 25%. Boot looping

blackhawk said:
Negative. Keep the playing field level. An update now could brick it.
Factory reset if you can. No known rootkits can worm out of the user data partition on Android 9 or higher. A factory reset will purge it if that's the cause. Kill the intruder.
Delete your Samsung and especially Google accounts in settings first if possible. Reset your Google account password after you factory reset, write it down. If it was malware try to figure out when, where and how it breached the device. Any odd behavior that signaled the event.
Click to expand...
Click to collapse
I am in download mode. Can I flash a stock firmware using odin ? and will that Still keep my phone legit ?

panzer27 said:
I should have read this on time, I wen for the software update Wont go beyond 25%. Boot looping
Click to expand...
Click to collapse
Did it completely download the update?
If not try to get into boot menu again. Factory reset. Otherwise it will need to be reflashed.

panzer27 said:
I am in download mode. Can I flash a stock firmware using odin ? and will that Still keep my phone legit ?
Click to expand...
Click to collapse
As long as you flash the correct stock rom. Make sure it's the right one!!!
Not sure about the best method. Make sure you find out what is the best shot as you could hard brick the phone if you goof this up.
Throw it to Samsung if in doubt.
I've been fortunate and never had to do this. One reason I leave the Android firmware alone, avoiding even upgrades and updates. Android firmware flashing is the most complicated I've seen. A PC bios or a Canon Pro shooter, router are a snap to do by comparison.

blackhawk said:
Did it completely download the update?
If not try to get into boot menu again. Factory reset. Otherwise it will need to be reflashed.
Click to expand...
Click to collapse
It downloaded everything, rebooted and started installing the update. Reached 30% then slipped to bootlooping vigorously. To get to the boot menu I would have to discharge the phone again. Because of the installation process, do you think draining the battery could brick the phone ? I could leave it to discharge if this is not a risk and 30% will be rolled back.
Do advise.

panzer27 said:
It downloaded everything, rebooted and started installing the update. Reached 30% then slipped to bootlooping vigorously. To get to the boot menu I would have to discharge the phone again. Because of the installation process, do you think draining the battery could brick the phone ? I could leave it to discharge if this is not a risk and 30% will be rolled back.
Do advise.
Click to expand...
Click to collapse
Update or reflashing the stock rom?
You should never interrupt when it's flashing. Yeah it could definitely at least soft brick it.