My phone bootloops into teamwin logo with no commands, it's not recognize by my PC even though it was before I flash new vendor and a custom rom. it will allow me to go into fastboot.
It happens to me now, but with stock 7.1.1 (beta program).
rodrigo82 said:
It happens to me now, but with stock 7.1.1 (beta program).
Click to expand...
Click to collapse
How did you fix it? I am a Mac-user and Nexus Root Toolkit is not available for me
yychun1217 said:
How did you fix it? I am a Mac-user and Nexus Root Toolkit is not available for me
Click to expand...
Click to collapse
I googled it and I discovered that there's no fix.
It's a hardware problem, specifically on emmc controller.
End of story: I bought a Samsung J5 Metal and I still missing my dearest N5X.
And my N5X only works on bootloader.
I'm having a similar issue my phone froze and was bootlooping. I was able to access recovery and recover files from the SD. However Im now having a hard turning on the phone and when I do, I can get it into bootloader/ recovery but computer won't recognize it. So I can't lock the bootloader and unroot to send it in for repair. I'm probably going to send I'm the phone as is and hope it gets fixed. It's crazy that it just froze while I was using YouTube and started bootlooping. Now using my Nexus5
Sent from my Nexus 5
Related
I tried flashing a kernel believed to be ExcaliBur on my HTC One M8, but as soon as i rebooted the screen was black yet still on.
I know it's not bricked completely because i can still hear sounds, feel vibrations and see the LED's work properly. Basically I have a "blind" phone. I have began to look into a way to capture my screen one frame at a time with my computer.
Please help me!
Running Android 4.4.4 Cyanogenmod Snapshot 11
T-Mobile
TWRP 2.8.0.3
Tried getting back to bootloader and flashing back the boot.img you had before flashing new kernel?
If the device still has "some" interaction then you should be able to connect it to PC and use the adb reboot bootloader command to boot it into bootloader.
BerndM14 said:
Tried getting back to bootloader and flashing back the boot.img you had before flashing new kernel?
If the device still has "some" interaction then you should be able to connect it to PC and use the adb reboot bootloader command to boot it into bootloader.
Click to expand...
Click to collapse
I actually DID just get into my bootloader. I had to mess around by pressing the buttons until i finally got it to boot into bootloader. Now I flashed a stock kernel for now, I always keep it in my SD Card.
I found you can use a program called Wondershare MobileGo for Android that can read whatever is on your phone if you happen to be "blind" like me.
P.S. I really need a kernel for CMod that has fast charge. Currently ExcaliBur is off the list.
I haven't heard of Wondershare MobileGo, seems interesting.
I can't help with custom Kernels, I always stick with stock, haven't flashed a custom kernel since way back with my S3. Sorry, can't help there.
Thanks anyways! Notice I got my phone working again! I flashed the stock, and then reflashed CMod and nothing was wiped. Interestingly...
Sent from my One M8 using XDA Free mobile app
That's quite lucky, any other time I've heard of this happening the phone's died completely.
Hello everybody,
i hope the xdadevs can help me with my problem.
Since two Days i try to recover my Nexus 7 form a bootloop.
A week ago i flashed Kali Nethunter 2.0 via TWRP on my Device (Nexus 7 2003 Wifi) - Everything worked fine till yesterday.
My device run out of energy so i loaded it and startet it shortly after that.
Then i regognized the bootloop. I tried to restart the device but it had no effect.
After that i tried to boot into the Recovery Mode with TWRP to restore my working backup. But it got stucked on the loading screen of TWRP too.
Now i tried to recover some images and fix the problem with some manuals which seemed promising. - no success
After a while i did something incredible stupid and locked my bootloader again (i wanted to try to lock and unlock it since some tools couldnt flash the stock rom).
The situation right now:
I cant boot up normaly: Stuck while "Google" is displayed
I cant boot in Recovery Mode (TWRP): Stuck on the blue TWRP Logo
If i try to use the Skipsoft Toolkit or something else it fails - or do i miss something
Recover the Stock rom by using the "flash-all.bat" fails because of this (pastebin. c0m/ie0dBv1D). I used the stock rom of Android 4.4.4(razor-ktu84p) because every other stockrom says this (pastebin. c0m/Dz31k8qu).
I wonder why the stock rom needs to get the bootloader unlocked... ive red so much about it that it just works out of the box..... am i doing something wrong ?
If i try to unlock again, the selection screen on the tablet shows up. I choose yes and hit the Power button. At the console the output <bootloader> erasing userdata" shows up and "freezes?!"... nothing happens afterwards.
Thats about it and this is where i am stuck. I would really appreciate if someone could help me ! I would even reward or spend some money on help.
I try to fix it meanwhile and update this post if something new happens.
I had to alternate the links because im a new member, im sorry for that !
Thanks in advanced and sorry for the spelling
did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?
diehard2013 said:
did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?
Click to expand...
Click to collapse
Yeah i tried it but it couldnt fix my problems. Returning to Stock Rom will always tell me that i need the bootloader unlocked... and i cant unlock it.
My PC and Linux Notebook where recognizing before it was bricked. Now it only gets detected in fastboot because it wont start anymore.
I've been watching several threads for the last few days, and have not seen this exact issue. I would greatly appreciate some help.
Device:
- Nexus 5X LGH790 32GB
- Stock bootloader / fastboot
- Never unlocked / rooted / etc.
The only advanced thing I've done is join the beta program a few months ago to get 7.0 early. Got that without any issue.
Issue:
I received the 7.1.1 OTA on the day it came out. Installed with no problems. The next day, the phone just froze in the middle of regular use. After about 15 seconds, it started boot looping to the Google splash screen. I can hold volume-down to enter fastboot, but when I select recovery mode, it just starts looping again. Pretty much all I could do was power it off. I did find out by accident that if I left it looping for long enough, sometimes it actually loaded normally (I even saw beta program warning/notice). But when I tried using it for more than a minute, it would freeze, reboot, and loop again.
What I've already tried:
- I tried using the WugFresh NRT fix softbrick method. I was able to quickly turn on debugging one of the times that I left it to loop. But when NRT sent a reboot the phone, it threw it back into the loop and NRT stopped recognizing the device.
- I tried to follow the unbrick procedure using a TOT file in this thread: http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766 But even after using LGUP, I still cannot even get into recovery mode.
- I filed a bug in the AOSP here: https://code.google.com/p/android/issues/detail?id=225802.
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
DC_Knight said:
Update: I tried using LGUP again. The phone still gets stuck on the Google screen then boot loops.
Now, however, I am able to get into recovery mode consistently. Other threads have suggested doing an OTA sideload at this point. But I cannot seem to get my device recognized. The NRT shows no ADB devices connected. So I'm still stuck. Is there another way to try sideload?
Click to expand...
Click to collapse
Try fastboot/bootloader mode and fastboot flash the OTA manually.
Update 2: Seems like all the other things I tried over the last few days have caused various unofficial USB drivers to be installed. I've tried uninstalling most of them. I downloaded the google USB driver from latest SDK. But my 5X is still recognized as a Kedacom device when it is sitting at FastBoot.
However, I must have made some progress because I was able to start the sideload process. Unfortunately, I am now stuck on yet another error. The phone hangs at "verifying update package" and then after about 2 minutes... it reboots itself and starts looping again!
I thought I had it. So close. Now I want to throw the phone. Going to sleep, but would be grateful for any other suggestions in the morning.
- DCK
use nrt to erase all partitions, then download 7.1 factory image, unzip and flash one by one the partitions.
DC_Knight said:
...
I'm at a loss here. On another thread, a member suggested this type of loop was a hardware/solder joint issue. I suppose that's possible... but man, what a coincidence that would be! Just now after the OTA the hardware fails? Any other thoughts? I'm pretty new to a lot of the terms/methods here, so maybe I missed something.
Thanks, DCK.
Click to expand...
Click to collapse
Sounds like the boot loop issue many people have been having (the hardware/solder issue). It happened to me a few weeks ago after upgrading to Android 7.0. I got a replacement device from google.
If you're bootloader is locked, NRT or any other method to flash the factory image is not going to work. The only suggestion I have is to un-enroll in the beta program and hope your device will boot long enough to flash the ota Google will send the device to get back to 7.0. Note, this will wipe your device.
Sent from my Nexus 9 using XDA-Developers mobile app
Same problem here. It can't be recognized after I reboot to fastboot. So I can't flash anything.
If the device isn't recognized try this http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33. It's worked for a few of us with the same problem
Sent from my Nexus 9 using XDA-Developers mobile app
Enter stock recovery then flash the full ota via adb sideload
I was playing hearthstone as usual with my 8 month old nexus 5x. Then all of a sudden it froze and restarted itself. I wasn't mad cause it was the first time in 8 months. Then after 2 hours my phone started bootlooping. I was able to see the android boot screen and launcher sometimes, but now i can't get past through google screen. I am able to use fastboot mode and flash images via nexus root toolkit or skipsoft but i can't use twrp. I've tried:
-Nexus Root Toolkit's flash stock+unroot option
-Flashing Pixel Rom
-Can't LGUP and tot image cause i get the "there is no handset connected. Please, connect a handset." error.
I'm now considering baking or freeze my nexus 5x. I know there are lots of people having the same issue these days but I still have a bit of hope because i can access fastboot mode and flash roms.
any help would be very appreciated, thanks.
atahanu said:
I was playing hearthstone as usual with my 8 month old nexus 5x. Then all of a sudden it froze and restarted itself. I wasn't mad cause it was the first time in 8 months. Then after 2 hours my phone started bootlooping. I was able to see the android boot screen and launcher sometimes, but now i can't get past through google screen. I am able to use fastboot mode and flash images via nexus root toolkit or skipsoft but i can't use twrp. I've tried:
-Nexus Root Toolkit's flash stock+unroot option
-Flashing Pixel Rom
-Can't LGUP and tot image cause i get the "there is no handset connected. Please, connect a handset." error.
I'm now considering baking or freeze my nexus 5x. I know there are lots of people having the same issue these days but I still have a bit of hope because i can access fastboot mode and flash roms.
any help would be very appreciated, thanks.
Click to expand...
Click to collapse
I had the same issue 3 weeks ago. I had access to just the fastboot and the recovery lgup did not work either. It went to repair and the verdict was motherboard out of service and to change
androcib said:
I had the same issue 3 weeks ago. I had access to just the fastboot and the recovery lgup did not work either. It went to repair and the verdict was motherboard out of service and to change
Click to expand...
Click to collapse
the point is i bought this phone from u.s and there is no repair service for it in my country.
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