Related
I went to update my firmware because I couldn't use the new instagram. Of course the phone froze at the boot screen I tried a recovery at first that didn't work. I then tried a factory reset and it has done the same thing can anyone help me fix this problem I hate ig for this.
Be more specific
My Nexus 7 2013 running stock 4.4.4 is not able to boot up to the lock/home screen. It just stays at the four dots or petals boot animation indefinitely. It does not freeze(animation goes on smoothly) nor does it go back to the bootloader again.
I have done cache wipe and factory reset.
I have flashed stock 4.4.4 factory image again and in the process unlocked the bootloader as of now.
But there is no change in the situation. I love this tablet and I am desperate to get this sorted out. Please help me.
I am in the same situation. I got my device back from Asus repair today, it was unlocked and running a custom KitKat rom, but only the screen was broken and that was what was repaired (at my own expense).
I turned it on and it was stuck at the 4 swirling dots for more than 20 mins, so I wiped the device completely in TWRP and tried to flash a stock factory image (Lollipop) - same problem. I tried flashing a factory KitKat image, also stuck at boot animation.
I then re-flashed TWRP since it had been replaced by the stock recovery, and then sideloaded a custom Lollipop rom (Screwd) - still same problem.
It is strange that I can use adb and fastboot, but nothing gets past the swirling dots. Hopefully someone can point us both in the right direction....
ems328i said:
I am in the same situation. I got my device back from Asus repair today, it was unlocked and running a custom KitKat rom, but only the screen was broken and that was what was repaired (at my own expense).
I turned it on and it was stuck at the 4 swirling dots for more than 20 mins, so I wiped the device completely in TWRP and tried to flash a stock factory image (Lollipop) - same problem. I tried flashing a factory KitKat image, also stuck at boot animation.
I then re-flashed TWRP since it had been replaced by the stock recovery, and then sideloaded a custom Lollipop rom (Screwd) - still same problem.
It is strange that I can use adb and fastboot, but nothing gets past the swirling dots. Hopefully someone can point us both in the right direction....
Click to expand...
Click to collapse
Ya I can understand. All we can do is wait for useful suggestions.
bump
Clonazepam said:
bump
Click to expand...
Click to collapse
If the tab gets to the spinning dots, it means the bootloader is not corrupt, so there must be a way to restore. Since there's nothing else you can do, why don't you back up the tab, then erase everything, especially formatting the internal storage (using the format button in TWRP) twice, and re-flash a rom. It seems some residue is preventing the thing from booting up. It happened to me on the TF300 a few times when the new bootloader was incompatible with the old one. Good luck.
graphdarnell said:
If the tab gets to the spinning dots, it means the bootloader is not corrupt, so there must be a way to restore. Since there's nothing else you can do, why don't you back up the tab, then erase everything, especially formatting the internal storage (using the format button in TWRP) twice, and re-flash a rom. It seems some residue is preventing the thing from booting up. It happened to me on the TF300 a few times when the new bootloader was incompatible with the old one. Good luck.
Click to expand...
Click to collapse
I tried that but I had no luck. Any other suggestions?
Clonazepam said:
I tried that but I had no luck. Any other suggestions?
Click to expand...
Click to collapse
Depending on the TWRP version, some claim it would fail to format completely. Phil's Touch (Arter's version 6.58.9) however would. You might want to try that. I personally haven't experienced it with this model, so I just pass the information along. Unless the EMMC physical structure is damaged somehow and cannot be written to, in which case the only solution is a replacement motherboard since you cannot find an OEM Emmc, let alone replace and program it.
ems328i said:
I am in the same situation. I got my device back from Asus repair today, it was unlocked and running a custom KitKat rom, but only the screen was broken and that was what was repaired (at my own expense).
I turned it on and it was stuck at the 4 swirling dots for more than 20 mins, so I wiped the device completely in TWRP and tried to flash a stock factory image (Lollipop) - same problem. I tried flashing a factory KitKat image, also stuck at boot animation.
I then re-flashed TWRP since it had been replaced by the stock recovery, and then sideloaded a custom Lollipop rom (Screwd) - still same problem.
It is strange that I can use adb and fastboot, but nothing gets past the swirling dots. Hopefully someone can point us both in the right direction....
Click to expand...
Click to collapse
So you sent your tablet to ASUS to have the screen replaced and they sent it back to you unable to boot? That's not something you should have to deal with, I'd call ASUS and demand that they repair it.
graphdarnell said:
Depending on the TWRP version, some claim it would fail to format completely. Phil's Touch (Arter's version 6.58.9) however would. You might want to try that. I personally haven't experienced it with this model, so I just pass the information along. Unless the EMMC physical structure is damaged somehow and cannot be written to, in which case the only solution is a replacement motherboard since you cannot find an OEM Emmc, let alone replace and program it.
Click to expand...
Click to collapse
I just tried with Philz recovery but still had no luck. i formatted everything and then flashed a factory image but still it's the same.
_MetalHead_ said:
So you sent your tablet to ASUS to have the screen replaced and they sent it back to you unable to boot? That's not something you should have to deal with, I'd call ASUS and demand that they repair it.
Click to expand...
Click to collapse
That's what I've done now, but I was hoping to avoid sending it off for 2-3 weeks after already not having it for the last 2 1/2 weeks
ems328i said:
That's what I've done now, but I was hoping to avoid sending it off for 2-3 weeks after already not having it for the last 2 1/2 weeks
Click to expand...
Click to collapse
Yeah, that sucks. I'd probably try and fix it myself too. But with what ASUS charges for repair you'd think they'd send it back to you on perfect working order. I called yesterday to see what it cost to replace the screen because mine is all scratched up and they wanted $200. Ridiculous. Might as well just buy a new one.
Any other methods to fix this problem anyone?
Clonazepam said:
My Nexus 7 2013 running stock 4.4.4 is not able to boot up to the lock/home screen. It just stays at the four dots or petals boot animation indefinitely. It does not freeze(animation goes on smoothly) nor does it go back to the bootloader again.
I have done cache wipe and factory reset.
I have flashed stock 4.4.4 factory image again and in the process unlocked the bootloader as of now.
But there is no change in the situation. I love this tablet and I am desperate to get this sorted out. Please help me.
Click to expand...
Click to collapse
Clonazepam - Our sincerest apologies in regards to the issues you're having with your Nexus 7. Please send us an emailed description of the issue along with your Nexus' serial number to [email protected] and we will assist you as best as possible.
Asus_USA said:
Clonazepam - Our sincerest apologies in regards to the issues you're having with your Nexus 7. Please send us an emailed description of the issue along with your Nexus' serial number to [email protected] and we will assist you as best as possible.
Click to expand...
Click to collapse
I bought the tablet in India and I still live in India. Will you be able to assist me here?
ems328i said:
I am in the same situation. I got my device back from Asus repair today, it was unlocked and running a custom KitKat rom, but only the screen was broken and that was what was repaired (at my own expense).
I turned it on and it was stuck at the 4 swirling dots for more than 20 mins, so I wiped the device completely in TWRP and tried to flash a stock factory image (Lollipop) - same problem. I tried flashing a factory KitKat image, also stuck at boot animation.
I then re-flashed TWRP since it had been replaced by the stock recovery, and then sideloaded a custom Lollipop rom (Screwd) - still same problem.
It is strange that I can use adb and fastboot, but nothing gets past the swirling dots. Hopefully someone can point us both in the right direction....
Click to expand...
Click to collapse
Did you update the bootloader to 04.14 ? It is required to update the bootloader to run lolipop. Try flashing the new bootloader.IMG and then installing stock or custom lolipop ROM.
str1ker0ne said:
Did you update the bootloader to 04.14 ? It is required to update the bootloader to run lolipop. Try flashing the new bootloader.IMG and then installing stock or custom lolipop ROM.
Click to expand...
Click to collapse
Yes, I had updated the bootloader. I have now RMA'd again....
ems328i said:
Yes, I had updated the bootloader. I have now RMA'd again....
Click to expand...
Click to collapse
All I can suggest right now is try a different ROM like aosp or cm official. You seem to be doing everything correctly. You can also try flashing the original 4.3 factory image with 03.14 bootloader maybe it'll boot. Then revert back to lolipop.
str1ker0ne said:
All I can suggest right now is try a different ROM like aosp or cm official. You seem to be doing everything correctly. You can also try flashing the original 4.3 factory image with 03.14 bootloader maybe it'll boot. Then revert back to lolipop.
Click to expand...
Click to collapse
Thanks but as I mentioned I have RMA'd it again so i don't have it anymore...
ems328i said:
Thanks but as I mentioned I have RMA'd it again so i don't have it anymore...
Click to expand...
Click to collapse
Hopefully they won't charge you this time.
bump to original question
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
So I tried sideloading. I was able to get into the stock recovery. I tried wiping cache and data, then tried installing the newest stock rom.
Everything seemed to work. Then I had to restart. A message popped up after the same "Your device software can't be checked for corruptions. Please lock the bootloader". It had the title in blue stating "Encryption unsuccessful".
Then said, "Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Then there is a single button that says, "Reset Phone".
Problem still persists.
Help please...
Why did you bought a bootlooped phone?
Sin Stalker said:
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
Click to expand...
Click to collapse
When my Nexus 5x got into bootloop, I sent it to LG and they had to change the whole circuit. So yeah.
When you flash Google Factory Image, it flash the stock kernel.
If you have warranty, then send it to Google/LG. If you haven't got, then you're in problem. New motherboard needed, but it's expensive.
See the following thread for more info.
https://forum.xda-developers.com/nexus-5x/help/5x-bootloop-cause-fix-t3476794/
khalifakk said:
Why did you bought a bootlooped phone?
Click to expand...
Click to collapse
Cause its cheaper.
Sin Stalker said:
Cause its cheaper.
Click to expand...
Click to collapse
Then face the consequences...
khalifakk said:
Then face the consequences...
Click to expand...
Click to collapse
What consequences?
Hardware bootloop can't be fix by software.
Duckscreen said:
Hardware bootloop can't be fix by software.
Click to expand...
Click to collapse
Exactly. Everyone has either been able to get a replacement under warranty or was pretty much screwed if it was out of warranty.
Sent from my Nexus 5X using Tapatalk
Sin Stalker said:
What consequences?
Click to expand...
Click to collapse
A bootlooped phone for ever....
I recommend you will install kernel adiutor app after try rooting
I recommend you will install kernel adiutor app after try rooting
Almost I got no bootloop even no random reboot nexus 5x's state
Hi Everyone,
I have a 5T running android 9 - completely stock. The device is SIM free, I have never customised it at all - if anything it's never been connected to a PC even.
A few days ago I was using my phone as normal (on whatsapp) but it completely froze. It now boots up to the "Your device is corrupt and cannot be trusted and may not work properly" - it freezes on start up and won't work at all.
- I can get to the fastboot screen
- I can get to the recovery screen to install from ADB
The fastboot screen says in red - device state - locked.
The device is a clean, un-customised phone. Only a few days prior I checked for any OTA updates but I haven't received android 10 yet.
I haven't flashed phone firmware or anything for years now. (By years, I literally mean years - back in the Nokia 8210 days). My only other experience of flashing firmware was with Samsung phones and 'debranding' them.
As I was not trying to root the device or anything - how do I fix this issue? I've searched the forums but I cannot fine a scenario similar to mine therefore I'm a bit confused as to what to do to resolve it.
I've tried to sideload this - oneplus.com/uk/support/softwareupgrade/details?code=PM1574156155944 via recovery but it says installation failed.
Any help appreciated thanks!
Sounds like you're straight out of luck to recover any data if your device is completely stock, as to unlock your bootloader to access encrypted data would mean a factory reset. You could try try one of the unbrick tools using the guide here. You will lose your data.
I tried the unbrick tool here - forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
... and it doesn't work. The phone now boots to a blank screen with a constant white LED.
Could this be a hardware issue?
I'm not too concerned about losing my data - already gave up on trying to keep my data when the problem first occurred!
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
oneplus5t_ said:
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
Click to expand...
Click to collapse
Problem fixed?
unfortunately not. Any ideas on next steps?
That's an odd issue for sure. My only idea would be installing TWRP and maybe formatting from there and using fix permissions etc. to see if it has any effect.
I've done some googling to try and understand "TWRP" but I'm not sure I fully understand. Are there any forum posts I can refer to?
- phone has been flashed several times
- before this whole saga dev mode was enabled, but only to reduce animation scale - USB debugging was never enabled
- the phone has always been stock / sim free - never rooted
Thanks
Can you get into recovery? If yes then try connecting to a pc whilst in recovery as it should let you open your phones internal storage on PC but im not too sure if stock recovery allows it, (TWRP) does. Then copy whatever files you need. Let us know if you can get into fastboot mode aswell
It sounds similar to an issue I have just experienced with a friends 5T. In my case it's a hardware issue (seems like Wi-Fi has died). Just for kicks try to flash the Android 7 firmware. For some reason it allowed me to boot the phone fine and use it, albeit without any Wi-Fi. I sideloaded OOS 4.7.6 and that seems to be the last version 7. You could also use the older unbrick software. Academic I fear as I think you have a hardware issue.
Hi guys, can you help a little. Has anyone had the following problem. Something happened to the phone as it worked and started to reboot itself. I reset it to factory settings, installed the latest version of the software through Odin, but it started to reboot again. Is it possible to have a hardware problem? Any ideas?