Day 1
After accidentally dropping the battery out my TP2 phone while processes were loading for OS, it started doing an infinite loop back ever time right before the Os starts to load. After removing the sim and sd card, I then Attempted a Hard reset...the load was successful, after it reboots and goes to the screen saying Preparing your phone for first use, it then starts the infinite loop Again at that screen every time...
DAY 2
After doing some research, i decided to load the stock rom on it...but the same thing happens with the infinite loop back...
I'm definitely at a lost of what else I could do to fix this because I really do love this phone...
Please, any suggestions or pointing me the right direction would be very appreciated...
THKX,
Related
My Tecno L3 has been giving me some weird signs lately,You know while playing SEGA games and the Cartridge freezes, the way the pixels bust out... my phone started doing that and yesterday it did it again and it rebooted but while trying to reboot it got caught up in a bootloop just displaying Tecno... nothing else and I formatted a couple of times and while trying to format it this one time it was taking a long time so I just removed the battery and when I rebooted it, it goes straight to recovery mode still trying to format like before. I didn't try to root it. Please could You suggest something for me to do?
I have read several threads on similar problems but none that are the same as mine.
I bought my shield tablet (16gb wifi) off Amazon so I can't really tell you much about it's exact specs. All I know is that I was told that only early manufacturer runs had rooting and OTG issues, and that newer runs had OTG out of the box.
Mine doesn't have OTG enabled, and it would not root with most of the common self installing root apps. So I believe it is an older version.
I have been installing all Nvidia updates as the update notification comes up on my tablet except for the latest one released a couple days ago. (waiting for WiFi to down load)
I was running marvel future fight at the time my tablet did a forced shutdown for a low battery.
Later I plugged it in to charge for a few minutes. When I first plugged it in I got the normal warning image of an empty battery telling me I could not boot yet.
I waited several minutes and tried to boot, but the boot process took an extensive amount of time.
But the real issue is that now I have read several threads on similar problems but none that are the same as mine.
I bought my shield tablet (16gb wifi) off Amazon so I can't really tell you much about it's exact specs. All I know is that I was told that only early manufacturer runs had rooting and OTG issues, and that newer runs had OTG out of the box.
Mine doesn't have OTG enabled, and it would not root with most of the common self installing root apps. So I believe it is an older version.
I have been installing all Nvidia updates as the update notification comes up on my tablet except for the latest one released a couple days ago. (waiting for WiFi to down load)
I was running marvel future fight at the time my tablet did a forced shutdown for a dead battery.
Later I plugged it in to charge for a few minutes. When I first plugged it in I got the normal warning image of an empty battery telling me I could not boot yet.
I waited several minutes and tried to boot, but the boot process took an extensive amount of time.
But the real issue is that now, every time I boot it up, once the Nvidia logo disappears instantly before the lock screen or anything else can come up, the notification that one of two processes have stopped comes up. Those being System UI, and Cellular Data.
This would normally be no problem but the instant I click OK the same warning pops back up. It is just stuck in the same loop, process stops, I hit OK and repeat for as long as my patients lasts and I try rebooting...
(why a 16gb WiFi only model even needs the cellular data process is beyond me or why it would prevent a complete boot... )
Any way I started research and found the power + volume down bootloader option.
It took me several tries to figure out how to even get the timing right for that to work. But once there it was no help.
First option for Factbook gave this result :
Cold booting Linux
Then the Nvidia logo, and the same system UI has stopped warningtI have read several threads on similar problems but none that are the same as mine.
I bought my shield tablet (16gb wifi) off Amazon so I can't really tell you much about it's exact specs. All I know is that I was told that only early manufacturer runs had rooting and OTG issues, and that newer runs had OTG out of the box.
Mine doesn't have OTG enabled, and it would not root with most of the common self installing root apps. So I believe it is an older version.
I have been installing all Nvidia updates as the update notification comes up on my tablet except for the latest one released a couple days ago. (waiting for WiFi to down load)
I was running marvel future fight at the time my tablet did a forced shutdown for a dead battery.
Later I plugged it in to charge for a few minutes. When I first plugged it in I got the normal warning image of an empty battery telling me I could not boot yet.
I waited several minutes and tried to boot, but the boot process took an extensive amount of time.
But the real issue is that now every time I boot it up.
Once the Nvidia logo disappears instantly before the lock screen or anything else can come up, the notification that one of two processes have stopped comes up. Those being System UI, and Cellular Data.
(why a 16gb WiFi only model even needs that process is beyond me or why it would prevent a complete boot... )
Any way I started research and found the power + volume down bootloader option.
It took me several tries to figure out how to even get the timing right for that to work. But once there it was no help.
First option for Fastboot
It says cold booting Linux the displays the Nvidia logo, but up comes the same warning of one of those stopped processes that will pop up as fast as I can click OK, for as long as I will click ok...
I tried the recovery option and that gave me the error of no command with the dead android with the warning sign popping out of his insides.
Just hit the reboot option and as of right now it did not boot... Will try holding down the power for manual reboot. As it will not power on normally now.
Manual reboot to the options again and going to try the power off option.
I am thinking that I might be able to fix this by flashing from a pic... But I wouldn't know as I have never gotten into that stuff before.
Cellular data stopped is still coming up on boot attempt... Only other option I know to try is open the menu back up and try the recovery again or maybe on the of chance hitting continue might do something different that changes things up and let's it finish booting.
I assume it is not actually completing the boot cycle as I cannot bring up the soft keys nor does the lock screen come up.
(don't get me started on the evils of soft keys. )
Anyway any help anyone can give would be great!
Hi guys, I'm experiencing some really strange issues. Literally all of a sudden my phone started to display a "android.process.acore has stopped" error, which comes up literally every 10 seconds making the phone unusable. I managed to stop that occasionally by forcing stop my contacts but it doesn't always work and eventually it comes back. I've tried to get into TWRP to reset my phone but guess what, it seems corrupted as it is stuck in a loop when I boot into it, it only displays the initial screen.
So, what do you guys suggests?
Ever since yesterday my Google Pixel has been stuck in a seemingly endless bootloop. It all started when I was using the phone as normal, then it suddenly froze. I tried turning it back on, but that's when it started happening. Every time it resets there is always either a blue line in a random location or a blue smear on the bottom of the screen. I can't access recovery, but fortunately the bootloader is unlocked (as it says in the title). But even that doesn't seem to help as every time I flash a factory image, it does the same thing.
I have searched for any situations similar to mine, but I either encounter vague/unhelpful solutions from Google on the Google forums, or threads that aren't specific enough. I am making sure to be as specific as I possibly can so I don't try the wrong solution and mess my phone up even further.
I was successful at one point a little while ago. Throughout the day I let it do its thing to drain the battery, until it finally died. I noticed that when I turned it on, it had the "No command" message with the dead Android robot instead. I reflashed the stock image one more time, and it was successful. However, I was an idiot and took my phone off the charger, and with what minuscule battery life was left, it quickly died, strangely setting me back to the bootlooping I had originally.
I'm new to this website (and pretty much forums in general), and I had just signed up for this specific reason, so apologies if I come off as a bit clueless.
(Edit: It still seems like a chance-based thing, but the no command message may pop up after letting the phone die and turning it on.)
I'm having this same issue as of today. Have you had any luck resolving it?
Same here. I updated the most recent "security update" (~44MB) and the phone started to repetitively reboot cycle. First, it last for 3-4 hours of normal use, then quickly down to 10 min. And then it couldn't even pass the animation to complete the reboot. Called/emailed Google service. Tried to wipe/factory reset in recovery mode. No help. Or even worse. It's now stuck at the"Google" screen for a minute, and reboot. Any thought?
hi all, ive had my s7 for 3 years now, amazing phone, but a few weeks ago this freezing reboot problem appeared and idk whats going on, my phone isnt rooted, and ive never messed with custom OS or any of that, its on android 7 stock, the battery is still good, but im wondering if this freezing problem is software or hardware related, when it freezes and reboots it gets stuck on the first logo, if i dont force it to shut off it will stay that way or keep rebooting till it runs out of battery, so after i force it to shut off sometimes it reboots immediatly and sometimes it stays black for a while and boots randomly, i try to go into recovery menu and most times it freezes on no command screen and if i leave it there the phone gets incredibly hot, so i force shut it again and this time with the charger connected so it shows charging icon as if its shut down... i leave it for a while then turn it on and its working untill it freezes again... i am considering installing lineage os incase the firmware is corrupt but im not very familiar with all of this and after reading other posts where the user did way more complicated stuff and the problem maintained... im not sure if its really gonna work, so im looking for advice on here