Related
I've been trying to root 4 different Nexus 10s running 4.2.1 using the wugs toolkit. I was able to unlock the first Nexus10, but when I tried to root the device, it got stuck on the Jellybean "X" on the final boot up. After waiting about 20 minutes, I just decided to flash the stock. I then tried rooting it again and it actually worked this time. The problem is that when I try to unlock the next 3 Nexus10s, they will unlock, but then get stuck on the Jellybean X. I then tried the same process of flashing to stock and trying again, but it still doesn't seem to work. Is anyone else having this problem? Should I just try like a million times? Thanks.
try clearing the dalvik cache and data and reflash , it might work
I cant mount my device.I cant see my sdcard on computer or install(in TWRP).When I flash cwm touch.It told me can't mount sdcard.What the hell??? Now its already half bricked cant boot into android.:crying:
Boot up recovery, wipe everything except system and reboot, it should come up ok. For some reason both my N7 and N10 hung at 'X' during unlocking but that fixed them..
Sent from my Nexus 10 using Tapatalk HD
Nexus 10 stuck on X
Disconn3ct said:
Boot up recovery, wipe everything except system and reboot, it should come up ok. For some reason both my N7 and N10 hung at 'X' during unlocking but that fixed them..
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
having same issue, installed CWM and unlocked bootloader, when resterted it just hangs on the X. these is no was to put any files on the tablet so where can i go from here? is this thing a paperweight?
First time flashing CM, and I may have messed up.
I rooted, installed TWRP, everything went perfect. I made a backup, and then tried to do a factory wipe. The wipe ended with the messages "unable to mount /system", "... /cache" and another one. I still tried to flash, and it just immediately got stuck, nothing happened. I rebooted, and everything worked fine. It was the Samsung stock image and all my apps were still there. I'm assuming it just didn't wipe at all.
I then went full retard mode, and tried to do a restore. I wanted to be sure my phone wouldn't fail on me in the recent future because some random stuff may have been partially wiped or something. Feel free to tell me I have the IQ of a chimp.
This completely messed things up, as it just got stuck at "Restoring System...". Eventually I restarted it with the power button. Now it can't boot normally, it can't boot into recovery mode, which just leaves download mode.
Any way I can fix this and subsequently install CM properly? I'm using TWRP 2.6.3.0. I've been told it's recommended to use 2.5, as the other version may have some issues (including not being able to recognize partitions). Only download mode still seems to work, so maybe there's a way to flash my phone back into the living world?
Versions:
Team Win Recovery Project 2.6.3.0
CyanogenMod 10.1.3 (RC2 jfltexx)
Thanks!
No idea really but maybe try to flash default rom/recovery etc with odin?
I've had this problem. Seeing as you only have download mode you have to flash a stock Rom and start again. Recoveries for our phone are still I development. Use official CMW to install CM, using links in Op.
Sent from my GT-I9505 using XDA Premium 4 mobile app
HANDSY said:
I've had this problem. Seeing as you only have download mode you have to flash a stock Rom and start again. Recoveries for our phone are still I development. Use official CMW to install CM, using links in Op.
Click to expand...
Click to collapse
I got the Samsung stock ROM of july, flashed it using download mode, and everything was back! I then rooted it again, and installed CMW (see versions below). I went into recovery, and tried to do a backup. It told me it failed: "Error while making a backup image of /data!". I then wondered if it may have been due to a lack of storage (which could very well be, as that was the issue before and the old backup by Teamwin was probably still on it somewhere), so I rebooted my phone. That's when it just failed and kept showing the Samsung logo at boot. I tried flashing my ROM again, again the logo. Then I did a factory reset using the regular recovery (cache and data reset), which fixed it. Now all my apps and data are gone, but that's no problem.
I'm back at the unrooted Samsung stock image now. Any ideas what I did wrong? These were the versions I used:
CF-Auto-Root-jflte-jfltexx-gti9505
i9505-cwm-recovery-6.0.3.2(0611)
Odin3 v3.07
I did nothing more than root, install CMW, try a backup and then it all went to ****. I'm surprised a backup can even do that.
Mmm I'm not too familiar with the internal workings of backups. Perhaps something was corrupted during flashing? Glad to hear that you have got your phone working again. There is an updated version of CMW somewhere in the original development thread.
Sent from my GT-I9505 using XDA Premium 4 mobile app
i've had the exact same issue.
I did go back to stock firmware and recovery, rerooted(chainfire) and installed the latest CWM 6.0.3.6.
Then, i did download Jamals Google play 4.3 rom, placed it on my SDcard and did follow the instructions. Works like a charm, and i've got noe clue what happened to my phone. however, it works now.
Chillzone said:
i've had the exact same issue.
I did go back to stock firmware and recovery, rerooted(chainfire) and installed the latest CWM 6.0.3.6.
Then, i did download Jamals Google play 4.3 rom, placed it on my SDcard and did follow the instructions. Works like a charm, and i've got noe clue what happened to my phone. however, it works now.
Click to expand...
Click to collapse
I tried CMW 6.0.3.6 and the Google Play 4.3 ROM as you said, and it works perfectly! I didn't try a backup this time, as it didn't exactly have anything to back up anymore.
Finally my precious vanilla Android again, I missed it since I switched from my Galaxy Nexus to my S4. Thanks a lot guys!
Edit: I do seem to be having one issue. Quite frequently after it's booted, and I enter the SIM pin, the message "Unlocking SIM card..." stays there indefinitely. I can use the phone but the message covers everything up. This doesn't always happen, but quite often. I've read some ROMs can't handle SIM lock, like CM. This is a Google Play edition, however. Is it normal that this doesn't work?
I can seem to fix it by holding the power button, and choosing "Unlock SIM" from the menu. I guess it's not that bad as I don't often reboot my phone.
My Nexus 6P is stuck in boot loops. I got it back from one of the repair centers and same thing again. It worked for like 5 mins and looping at the Google screen. I can't get into Recovery. I used the Nexus Root Toolkit to do everything possible and nothing. It seems to send the files fine but it will not boot. It just loops no matter what I try to do. Even tried sending TWRP recovery and can't get into that either. Is there any method that can do a complete format and start fresh? what do I do? If I can't fix his I am probably sending back to one of the repair centers again and using my S4 for another 3 weeks. If there is any method to wipe this thing 100% and get a clean install across the board like a computer Hard drive would that even work?
What do you mean by "send the files fine"?
Can you get bootlader? If you can, you can try flashing Nougat IMG.
Enviado de meu Nexus 6P usando Tapatalk
When I use anything on the Nexus Root Toolkit it goes though the process fine with no errors but it won't boot. Even if I try to send the stock recovery or TWRP it still can't boot into recovery. CMD says it went "ok" I tried so many processes of sending any OS to it and nothing. Loops on the Google screen. SO annoying.
LiquidAlloy said:
When I use anything on the Nexus Root Toolkit it goes though the process fine with no errors but it won't boot. Even if I try to send the stock recovery or TWRP it still can't boot into recovery. CMD says it went "ok" I tried so many processes of sending any OS to it and nothing. Loops on the Google screen. SO annoying.
Click to expand...
Click to collapse
Time to learn some fastboot dealings. In this General section, go to the sticky thread for rooting and returning back to stock.
Edit: here's the thread link: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Just please read and take your time, you will be able to fix your device if it's just a software issue.
Heads up, this is a bit of reading
Ok so two nights ago, I was messing with the phone a little bit attempting to put Google Assistant on the phone. I had gotten a new cable from Amazon which enabled me to finally plug my 6P into the computer and my bootloader was already unlocked as I did so before but the issue was that I didn't have twrp yet on my phone. After I got it all set up with adb/fastboot etc. I tried to flash twrp. It didn't work, I kept getting stock recovery to come up so I ended up chalking it up for another day. As I was watching my beloved school lose in the Rose Bowl, I realized that the phone was rebooting. Not sure why but it just started doing it. After that, the phone turned on after rebooting for about 45 mins and it stood on for about 10 mins. After that, it went back to bootlooping and did so without getting to the android boot up screen all night.
Pissed, I decided to try to fix it myself but after I woke up, I found the recovery to be inaccessible through the bootloader which I could previously enter even through all of the bootlooping. After the bootlooping started, I couldn't flash a recovery so figuring it was the new cable, I switched to the older one. Well after doing that, I was able to flash the stock recovery and get adb working again. Using a guide, I flashed the newest factory image that was just released which is N4F26J (my phone was on the NMF26F update), and after a few bootloops, the phone turned on!
Ecstatic, I skipped past all the setup screens and went immediately to developer options and I activated usb debugging. Shortly after this, the bootlooping restarted and I wasn't able to get it to get back to the phone. Using the Wugs toolkit, I continued to use that to get the factory images on the Nexus and usually after I would use it to flash the ota, it would reboot a few times and get to the welcome screen where I could use the phone for about 5 mins. before it started bootlooping again. Fearing it was just Google's OTAs, I switched ROMs using twrp and adb to this ROM https://forum.xda-developers.com/nexus-6p/development/rom-debloated-prerooted-deoxeded-t3372600 (All Credit For The Rom Goes To Him), and after a few reboots, I got it up and running but after a few mins, the bootlooping started again. I noticed that when I use the toolkit to get into the twrp recovery, it constantly says in Red Letters about it not being able to mount storage.
If anyone please can help me figure this out, I would really really appreciate it. I can't send it to Huawei because it has a very slight crack on the screen and with me being a college student, I can't afford the $160 that they want to replace it. Somebody please give me any type of insight so I can try to fix this on my own. Please
btw before every flash, I followed all steps you should with wiping cache, dalvik, etc. Not sure if that would make a difference
Exbruce said:
Heads up, this is a bit of reading...
Click to expand...
Click to collapse
Since you are familiar with NRT, I would start by running Advanced Utilities and fastboot FORMAT cache, system and userdata. Then go back to Flash Stock+ Unroot. Make sure you are set on at least NMF26F if Wug hasn't already updated to N4F26J yet. Flash stock. That should get you back up and running. There are other ADB options from the PC if this doesn't work for you.
v12xke said:
Since you are familiar with NRT, I would start by running Advanced Utilities and fastboot FORMAT cache, system and userdata. Then go back to Flash Stock+ Unroot. Make sure you are set on at least NMF26F if Wug hasn't already updated to N4F26J yet. Flash stock. That should get you back up and running. There are other ADB options from the PC if this doesn't work for you.
Click to expand...
Click to collapse
Ok I'll give it a shot and let you know how it goes.
Exbruce said:
Ok I'll give it a shot and let you know how it goes.
Click to expand...
Click to collapse
I think the problem you had with TWRP not sticking on Nougat is that you need to flash SuperSU after or the phone will revert back to stock recovery. Not that it helps with your boot loop issue.
v12xke said:
Since you are familiar with NRT, I would start by running Advanced Utilities and fastboot FORMAT cache, system and userdata. Then go back to Flash Stock+ Unroot. Make sure you are set on at least NMF26F if Wug hasn't already updated to N4F26J yet. Flash stock. That should get you back up and running. There are other ADB options from the PC if this doesn't work for you.
Click to expand...
Click to collapse
Tried it and no dice. Hasn't stopped bootlooping for the past hour
I think you have the issue aoy of us are having which after three or four days I have not been able to fix. RMA with Huawei maybe the only way out of it.
Sorry man it doesn't look good.
v12xke said:
Since you are familiar with NRT, I would start by running Advanced Utilities and fastboot FORMAT cache, system and userdata. Then go back to Flash Stock+ Unroot. Make sure you are set on at least NMF26F if Wug hasn't already updated to N4F26J yet. Flash stock. That should get you back up and running. There are other ADB options from the PC if this doesn't work for you.
Click to expand...
Click to collapse
galakanokis said:
I think you have the issue aoy of us are having which after three or four days I have not been able to fix. RMA with Huawei maybe the only way out of it.
Sorry man it doesn't look good.
Click to expand...
Click to collapse
Yeah it sucks simply because I've managed to get it from not booting to recovery to booting to the Rom but it just won't stick. This is hands down the worst experience I've ever had with a phone. The fact that Huawei wont replace it without that $160 is ridiculous to me because I've really done nothing wrong with it, it just konked out leaving me without a phone. Wow
Its probably google trying to force us into a pixel phone. If my 6p eats it, im done with Google phones. I love this phone. Its the best ive ever had. I'd definitely pay 160 for another if they could assure me no more bootloops. It sucks for people that can't afford it.
Exbruce said:
..... After the bootlooping started, I couldn't flash a recovery so figuring it was the new cable, I switched to the older one. Well after doing that, I was able to flash the stock recovery and get adb working again. Using a guide, I flashed the newest factory image that was just released which is N4F26J (my phone was on the NMF26F update), and after a few bootloops, the phone turned on!
Ecstatic, I skipped past all the setup screens and went immediately to developer options and I activated usb debugging. Shortly after this, the bootlooping restarted and I wasn't able to get it to get back to the phone. Using the Wugs toolkit, I continued to use that to get the factory images on the Nexus and usually after I would use it to flash the ota, it would reboot a few times and get to the welcome screen where I could use the phone for about 5 mins. before it started bootlooping again. Fearing it was just Google's OTAs, I switched ROMs using twrp and adb to this ROM https://forum.xda-developers.com/nexus-6p/development/rom-debloated-prerooted-deoxeded-t3372600 (All Credit For The Rom Goes To Him), and after a few reboots, I got it up and running but after a few mins, the bootlooping started again. I noticed that when I use the toolkit to get into the twrp recovery, it constantly says in Red Letters about it not being able to mount storage.
Click to expand...
Click to collapse
There well may well be a hardware problem with your device BUT I read your post again and I see a few possibilities. One is that you may have been using an unreliable data cable, and you didn't mention hash checking files before flashing. Second, it sounds like you had installed a factory image, and afterwards applied an OTA to the phone (and then a custom rom). Once you apply the full N4F26J image, there is no need use any OTA! Start with the latest image. Lastly, your data became encrypted when you booted the first time so you are getting mounting errors in TWRP. My advice would be to reformat again as above, manually download the full factory image N4F26J and use NRT to install it. NRT has not updated the toolkit yet, so you will have to d/l manually. NRT should hash check the file you downloaded. Use the bricked mode to Unroot+Flash Stock. You never mentioned running unencrypted, so I assume the default encryption is what you want. The idea is to attempt to get you back to stock with a device free from bootloops. If this doesn't work, then you'll need to use ADB.
v12xke said:
There well may well be a hardware problem with your device BUT I read your post again and I see a few possibilities. One is that you may have been using an unreliable data cable, and you didn't mention hash checking files before flashing. Second, it sounds like you had installed a factory image, and afterwards applied an OTA to the phone (and then a custom rom). Once you apply the full N4F26J image, there is no need use any OTA! Start with the latest image. Lastly, your data became encrypted when you booted the first time so you are getting mounting errors in TWRP. My advice would be to reformat again as above, manually download the full factory image N4F26J and use NRT to install it. NRT has not updated the toolkit yet, so you will have to d/l manually. NRT should hash check the file you downloaded. Use the bricked mode to Unroot+Flash Stock. You never mentioned running unencrypted, so I assume the default encryption is what you want. The idea is to attempt to get you back to stock with a device free from bootloops. If this doesn't work, then you'll need to use ADB.
Click to expand...
Click to collapse
Ok I'll give it a shot and let's see how this goes *fingers crossed*
UPDATE: Gave it a shot and it booted up to the welcome screen for about 2 mins and then started the bootloop all over again. Looks like the only option is to RMA the device at this point
Exbruce said:
Ok I'll give it a shot and let's see how this goes *fingers crossed*
UPDATE: Gave it a shot and it booted up to the welcome screen for about 2 mins and then started the bootloop all over again. Looks like the only option is to RMA the device at this point
Click to expand...
Click to collapse
Your phone is worth a lot more than 160.00 so it's probably best to RMA even if the charge seems unfair. You could always sell the RMA phone for a lot more than 160.00 if you've had enough of the 6P.
Exbruce said:
UPDATE: Gave it a shot and it booted up to the welcome screen for about 2 mins and then started the bootloop all over again. Looks like the only option is to RMA the device at this point
Click to expand...
Click to collapse
Sorry to hear that. Not ready to throw in the towel?
Have you tried doing a factory reset after the latest bootloop?
Any errors when formatting the 3 partitions, or during the flash process?
It could be looping for some reason during the initial encryption process which happens during first boot. I would try using a "no force-encrypt" modified boot.img before booting the first time to prevent the encryption process. If you prevent encryption, you may prevent the bootloop. You can find the boot.img on this forum, or use Wug's from the previous build, or even flash SU 2.79 to modify your boot.img.
If that doesn't work, you could try extracting files you need from the factory image, fastboot format and flash img files manually, including the modified boot.img.
Hi All!
I seem to be stuck in a bootloop on my 6P. I was running the latest Pure Nexus build, and I was having a bit of trouble with some apps, so I decided to reboot into TWRP and wipe the cache. After booting up again, everything seemed normal. The phone was running for a minute or so, and it just shut off. After that, it just keep rebooting. It's not a normal bootloop. I do not reach the animation, I only get to the screen where it says "google" and has the unlocked padlock symbol on the bottom. After that, it starts all over again with the "cannot check for corruption screen."
To be very clear: I can't boot anything at all, including recovery. I have tried flashing multiple versions of TWRP and multiple versions of the stock recovery.
Here is what I've tried so far:
I have flashed back to the latest 7.1.1 release both manually and using the flash all command
I used fastboot to erase the system, cache, boot, and userdata. I ran the commands normally and also with -w.
I've tried to flash an older version of android - 6.0, I think.
Nothing seems to work. I haven't made it to the boot animation once since it shut down.
I also left it on the charger all night just to be sure. The battery was at about 75% when it shut down.
Thanks!
RMA bro.
mtpease said:
Hi All!
I seem to be stuck in a bootloop on my 6P. I was running the latest Pure Nexus build, and I was having a bit of trouble with some apps, so I decided to reboot into TWRP and wipe the cache. After booting up again, everything seemed normal. The phone was running for a minute or so, and it just shut off. After that, it just keep rebooting. It's not a normal bootloop. I do not reach the animation, I only get to the screen where it says "google" and has the unlocked padlock symbol on the bottom. After that, it starts all over again with the "cannot check for corruption screen."
To be very clear: I can't boot anything at all, including recovery. I have tried flashing multiple versions of TWRP and multiple versions of the stock recovery.
Here is what I've tried so far:
I have flashed back to the latest 7.1.1 release both manually and using the flash all command
I used fastboot to erase the system, cache, boot, and userdata. I ran the commands normally and also with -w.
I've tried to flash an older version of android - 6.0, I think.
Nothing seems to work. I haven't made it to the boot animation once since it shut down.
I also left it on the charger all night just to be sure. The battery was at about 75% when it shut down.
Thanks!
Click to expand...
Click to collapse
Can you get to the bootloader?
I'm going to go out on a limb and say if you flash a factory image and get no errors but it's still boned the way you described then RMA if your answer. Your in an every growing boat!!
Sent from my Nexus 6P using XDA-Developers Legacy app
jhs39 said:
Can you get to the bootloader?
Click to expand...
Click to collapse
Yeah, I can get in to the bootloader just fine. I can flash anything I want wit no errors. I just can't boot anything.
CyberpodS2 said:
I'm going to go out on a limb and say if you flash a factory image and get no errors but it's still boned the way you described then RMA if your answer. Your in an every growing boat!!
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah, google agrees with me. They've sent me a new phone. I wish I could have found a solution, though.
mtpease said:
Yeah, google agrees with me. They've sent me a new phone. I wish I could have found a solution, though.
Click to expand...
Click to collapse
Glad your warranty worked for you. Pure Nexus seems to be a recurring factor in several threads. I've never used it myself. Over in this thread, an experienced user ran into a bootloop that would not clear with a fresh wipe and installation with flash-all.bat or even flashing partitions manually. Flash-all.bat finished with no errors but still looping. As a last resort he used Skipsoft's Toolkit to re-install stock and it worked. The toolkit script formats userdata and cache and this appears to be what solved the problem. Interestingly, he was able to reproduce the problem with PN. After installing it, he went into a bootloop again and the toolkit again got him back to stock. So, others that are stuck in a bootloop especially after running or updating PN should try formatting userdata and cache, or use the toolkit.