Hi everyone! I really appreciate it if you can help! I connected my ZTE AXON Pro phone to the computer and deleted some folders and files in my phone through Android File Transfer, and the phone worked normally after I deleted the files. But the next day when I turned it on, it was stuck at the "AXON" logo screen. I went to two repair shops. One could do nothing about it and suggested me to contact a data recovery company since I need the data in my phone. The other shop thought my phone was fairly old (I started to use it in 2017) and they suspected that the battery had gone bad and wasn't supplying enough voltage for a full boot cycle. They ordered a new battery and tried floating it plugged in, but the phone still wouldn't boot. They said the motherboard was also getting very hot approximately where the power supply chip would be. They tried to charge the new battery but nothing brought the phone to life, so they diagnosed it as a power supply chip failure. They couldn't fix it. But I think the problem is caused by me deleting the files that affect the system. After that I put the phone in recovery mode and wiped cache partition, but it still wouldn't fully boot up and it's stuck in bootloop: Now when I turn it on it's stuck at the "AXON" logo screen for a few minutes and then "Android is starting...Optimizing app 1 of 3.""Android is starting Optimizing app 2 of 3.""Android is starting Optimizing app 3 of 3." show up, and then "Android is starting apps." shows up. Then it restarts and stucks at the "AXON" logo screen, and repeats the loop over and over again until the battery is completely drained.
I have some very important app data in the internal storage and I can't afford to lose it. Does anyone know how to fix the bootloop without losing data? Thanks a lot!!!!!
Boot this Androd 5.1 based phone into "Safe Mode":
Safe mode can help you investigate and find problem apps if optimizing app 1 of 1 ... issue is caused by unsuitable or broken apps. You can stop Android optimizing apps by booting the device in Safe mode.
jwoegerbauer said:
Boot this Androd 5.1 based phone into "Safe Mode":
Safe mode can help you investigate and find problem apps if optimizing app 1 of 1 ... issue is caused by unsuitable or broken apps. You can stop Android optimizing apps by booting the device in Safe mode.
Click to expand...
Click to collapse
Thank you for replying! I just tried to boot it into safe mode, but it didn't work. When I saw the ZTE logo on the screen I quickly pressed volume down and held it for about one minute or longer, but the phone was still stuck at the "AXON" logo screen and started the bootloop. It wouldn't load in safe mode. I've tried a few times, but it still doesn't work.
Related
Please help my phone is confused like it is blinking lg logo but not getting on. In charge it gets on but in few seconds it gets off.
I think you are in soft brick state for some reason.. Did you try to do anything prior to this situation?
How did that happened? Similar issue happened to me, heres my post from other thread:
My H955 suddenly rebooted and it keeps on bootloop. It turns on fully and after 10-30 seconds (the hotter it gets, the less time it stays booted up) reboots again. After I left it to cooldown, there was error that root is gone or smth like that, and I had to agree to EULA and terms&conditions but the phone rebooted again. Maybe some kind of update was pushed in or whatever. This is the first time for me to happen. I have not installed new apps or mods on my phone like in two weeks.
Btw, seems like this is soft reboot, because there is no sounds and it didn't asked for SIMs PIN. I guess it has something to do with xposed..
I have used this method http://www.hard-reset.mobi/lg-g-flex-2-hard-reset/#to do factory reset. It seems to work, however phone still reboots. @mnshkpr8 try this to do factory reset, maybe this will help you.
Later I will try this http://forum.xda-developers.com/g-flex2/help/to-unbrick-g-flex-2-ls996-t3286105
Hi. I have similar problem here.
My phone wont pass LG logo if without charging on, the phone keep booting.. And if i charging on the phone just works fine, but if i plug out the charger the phone just turn off and restart again. Mine still using stock rom. Any suggest ?
This happened to me today as i edited one system file so I could get any app on split screen, I used flashtool and flashed the same kdz in normal mode, It flashed and everything is normal again.
any solution to this?
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!
So here's the gist. My s4 has been rooted for a while and very recently while removing some apps and bloatware I decided to remove the "Help" app since it seemed useless. I think I messed my phone up by doing that because by then my s4 would randomly give me the black screen of death or get stuck in a boot loop. To fix these problems I would take out the battery and hold the power button for a minute, or clear cache from the boot loader menu or reboot in safe mode which would inexplicably fix my phone normally for some reason. But all these options only temporarily fixed my phone and it would just continue with the same problems (Boot loop, black screen of death, etc).
I eventually resorted to factory resetting my phone, all though not the conventional way At first I tried decrypting my s4 but my stupid usb cord stopped being recognized by my pc and that screwed up the decryption so my phone factory resetted itself on it's own pretty much. Now I'm having trouble getting to the boot loading screen but I can get to the download/odin screen.
I looked up online and different guides told me the last resort is to do something called an emergency firmware recovery. I looked up on youtube what to do, tried using Kies but Kies said it doesn't support the s4. I then tried using Smart Switch but when I get to the screen where it tells me to enter my serial number, I enter it and it tells me that I'm entering the wrong serial number, even though I triple checked what it is! I google searched if other people were having this problem with smart switch and other people are having similar problems as I am. I'm running out of ideas on how to save my phone. I don't think it's a hardware problem because I haven't dropped my phone very recently. Does anyone have any ideas on what I can do next?
XDA Visitor said:
So here's the gist. My s4 has been rooted for a while and very recently while removing some apps and bloatware I decided to remove the "Help" app since it seemed useless. I think I messed my phone up by doing that because by then my s4 would randomly give me the black screen of death or get stuck in a boot loop. To fix these problems I would take out the battery and hold the power button for a minute, or clear cache from the boot loader menu or reboot in safe mode which would inexplicably fix my phone normally for some reason. But all these options only temporarily fixed my phone and it would just continue with the same problems (Boot loop, black screen of death, etc).
I eventually resorted to factory resetting my phone, all though not the conventional way At first I tried decrypting my s4 but my stupid usb cord stopped being recognized by my pc and that screwed up the decryption so my phone factory resetted itself on it's own pretty much. Now I'm having trouble getting to the boot loading screen but I can get to the download/odin screen.
I looked up online and different guides told me the last resort is to do something called an emergency firmware recovery. I looked up on youtube what to do, tried using Kies but Kies said it doesn't support the s4. I then tried using Smart Switch but when I get to the screen where it tells me to enter my serial number, I enter it and it tells me that I'm entering the wrong serial number, even though I triple checked what it is! I google searched if other people were having this problem with smart switch and other people are having similar problems as I am. I'm running out of ideas on how to save my phone. I don't think it's a hardware problem because I haven't dropped my phone very recently. Does anyone have any ideas on what I can do next?
Click to expand...
Click to collapse
Hi,
Kindly register yourself at XDA post which you can query in http://forum.xda-developers.com/galaxy-s4/help
Experts there may be able to help you
Hi!
Very weird situation. Before that everything was stock and OK (no custom ROM or anything).
- If the phone is unplugged, nothing works at all (key combinations,...)
- The battery is charged, at some point, when totally off, it showed the battery charging, 60% at least. But have not been able to go back into this mode.
- When connected, it starts booting, but keeps rebooting very fast (1-2 s after Samsung splash screen).
- Unable to boot into Recovery mode (UP+HOME+PWR, for wiping cache,...). Just does nothing, howerver long I wait
- Unable to boot "directly" into Maintenance Mode (all buttons), more on that later
- Can boot into Download (ODIN) mode (DOWN+HOME+PWR) very easily. I was able to flash stock ROM, but nothing changed.
- From ODIN mode I can boot into Maintenance mode (all buttons). I can navigate the menu, but any choice, even Factory Reset, gets me directly back to the reboot loop...
As I can not even turn it off, I cannot drain the battery (at least not quick). As soon as I disconnect the cable it goes dark (whatever mode I am in).
Anything I missed that I could try before throwing the phone?
Thanks!
SOLVED
Just to leave a trace on what happened:
- Left the phone alone, un plugged, for 8-10 hours.
- Just to see, tried to reboot it normally,
- It booted on a blue/cyan display, with "installing updates".
- At one point before I had that screen, but after 10 seconds it rebooted into the loop cycle. And after playing with the recovery reboots, I had never managed to get this special boot again.
- This time it stayed on "installing updates" for 1-2 mn, then rebooted, and Voilà!!!
So apart from my magic touch of doing nothing, don't really know what happened... So much for the recovery recipe!
A fairly similar thing happened to my girlfriend's g920v yesterday. We haven't been that lucky that it got fixed.
The situation is slightly different though, it boots for about 3 seconds, makes the low battery sound, battery indicator says 0%, then shuts back down.
Tried flashing stock in odin a few times, a few factory resets, nothing.
It seems like an OTA update failed and now the stupid locked bootloader won't let me or the or OS fix it.
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
guimou_qc said:
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
Click to expand...
Click to collapse
There's got to be some connection of some sort, yours is the 4th post I've seen here or on Reddit this month about bootloops probably related to updates
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
bigblkyj said:
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
Click to expand...
Click to collapse
If what you've described is correct, all of the solutions involve flashing the stock firmware which will of course wipe the device.
Were your photos not stored in a folder on the SD card?
There is a chance you can recover the device using Samsung Kies with the emergency recover option but if you've encountered the "no command" screen it's not looking good.
Unfortunately I did have an SD card installed, but I normally kept my camera pics on the phone's memory, since I have had an SD card fail as well and lost everything on there.
So this took an unexpected turn yesterday pretty much right after posting this... I've been messing with the phone, unplugging the battery each time, and have managed to get into different menus which kept making me think that something still had to be working if I could do that. Well, after leaving the No Command message on the screen it magically booted into the Recovery menu with (finally) the option to wipe the cache partition, which I did and rebooted normally. Believe it or not, it booted normally and into the OS like nothing ever happened?!
I instantly plugged it into my PC and ran Smart Switch which started taking a backup! About 25% though the device restarted again and was really warm to the touch on the RF covers inside. Bummer...
So I figured heat was now the issue for some reason... I waited for it to cool and then reinstalled the SD card and figured, if I could get it to boot long enough, the SD card is a quicker transfer and I'd just use ES File Explorer to try and do a photo dump to the SD card and see how far it would get. It actually made it all the way through and gave me enough time to grab some other stuff before getting hot and restarting again.
I believe the overheating is being caused by my opening of the device though... Currently I have the antennas removed and the speaker so that I'm able to quickly access the battery connector (which BTW seems to be the trick here to this working) But inadvertently, without the larger wireless charging coil in place, it relieved the pressure on the motherboard and broke the thermal paste connection between the chipset and the copper heatsink (I didn't tear it down further to check, but I can hear the 'sticking and peeling' when you press down on it).
I think what I'm going to do is apply pressure with a chip clip or something similar (non conductive) and see if I can grab a backup again before it restarts. After the cache wipe the phone seems to understand that it's plugged in and charging now which is a new thing as well...
Sorry for the long winded posts, but if this at all helps even one person with the same situation as I have, maybe that'll be worth getting lost in here