Yesterday my N7 'crashed' on me...
Device Info: N7 32gb non-3G, Android 4.2.1, Rooted via Toolkit, Stock, CWM v6.0.1.0 (non-touch), Bootloader 4.1.3 Unlocked (of course)
Recent changes: I had initially installed a 2nd account for my son to play games on without messing up my progress shortly after 4.1.2 launched... I immediately noticed that the N7 seemed more sluggish but put up with it so he would have his own account. Well he hasn't used my N7 for weeks and I hoped that maybe if I uninstalled that 2nd account that the sluggishness would go away... So a few days ago I went into settings and removed it... Not sure if it made a big difference. I only mention this because I am not sure if it had anything to do with what happened yesterday...
The Crash: Yesterday when I came home with my N7 I heard some notifications letting me know that it had logged into my home wifi and had connected with Gmail... About an hour later I went to use the tablet and when I hit the power button I briefly saw the wallpaper and unlock pattern. Almost immediately the wallpaper disappeared and was replaced by blackness. I could still see the unlock pattern and then the screen 'shifted' - got smaller, bigger and then bam... the tablet reset. This whole thing took just a few seconds.
After that it seemed to be stuck at the nexus logo/animation... I assume it was stuck in a boot loop. I let it go for a good 30 minutes and nothing changed... still had the animation. At that point I did the following:
So I rebooted into the bootloader and rebooted from there... same result.
So I rebooted into the bootloader and then recovery and rebooted from there... same result.
I gave up in frustration and powered it off from the bootloader and went to bed.
Today I went back into recovery and did a Nandroid backup. It gave me no options, it just did a full backup. Based on the amount of free space that was reported it seemed as if my SD card partition was intact. Up to that point I didn't know if the glitch maybe wiped everything out...
After that I formatted the /cache, /system and /data (not sure of the order). Then I tried rebooting and now it won't go past the Google screen with the unlock icon.
So I went back into recovery to see if I had a zip that I could flash. The only one there on my SD card that I can find is the CWM/Superuser one from the toolkit. That file is named CWM-SuperSU-v0.94-signed.zip and is in the root directory. I checked and the Nandroid backup seems to be where it should be...
So I figured that I need to flash the factory image but cannot seem to mount the N7 via USB. When I plug it in my Windows 7 machine, Win 7 lets me know that it has installed the "Nexus ADB" driver that my N4 installed and seems to be connected. But there is NO /USB in the Mount menu in Recovery and Windows 7 doesn't see the N7 from the My Computer/Windows Explorer.
My Questions:
Do I need to 'push' a stock image via ADB?
What ADB command do I type to see if the N7 is in-fact accessible from my Windows 7 machine?
I am assuming that when I formatted the three partitions mentioned above I wiped the boot ability of the N7. Is that why it won't go past the Google screen now?
Did I do anything wrong in what I've done so far?
Thanks in advance!
OldDogEyes said:
Yesterday my N7 'crashed' on me...
Device Info: N7 32gb non-3G, Android 4.2.1, Rooted via Toolkit, Stock, CWM v6.0.1.0 (non-touch), Bootloader 4.1.3 Unlocked (of course)
Recent changes: I had initially installed a 2nd account for my son to play games on without messing up my progress shortly after 4.1.2 launched... I immediately noticed that the N7 seemed more sluggish but put up with it so he would have his own account. Well he hasn't used my N7 for weeks and I hoped that maybe if I uninstalled that 2nd account that the sluggishness would go away... So a few days ago I went into settings and removed it... Not sure if it made a big difference. I only mention this because I am not sure if it had anything to do with what happened yesterday...
The Crash: Yesterday when I came home with my N7 I heard some notifications letting me know that it had logged into my home wifi and had connected with Gmail... About an hour later I went to use the tablet and when I hit the power button I briefly saw the wallpaper and unlock pattern. Almost immediately the wallpaper disappeared and was replaced by blackness. I could still see the unlock pattern and then the screen 'shifted' - got smaller, bigger and then bam... the tablet reset. This whole thing took just a few seconds.
After that it seemed to be stuck at the nexus logo/animation... I assume it was stuck in a boot loop. I let it go for a good 30 minutes and nothing changed... still had the animation. At that point I did the following:
So I rebooted into the bootloader and rebooted from there... same result.
So I rebooted into the bootloader and then recovery and rebooted from there... same result.
I gave up in frustration and powered it off from the bootloader and went to bed.
Today I went back into recovery and did a Nandroid backup. It gave me no options, it just did a full backup. Based on the amount of free space that was reported it seemed as if my SD card partition was intact. Up to that point I didn't know if the glitch maybe wiped everything out...
After that I formatted the /cache, /system and /data (not sure of the order). Then I tried rebooting and now it won't go past the Google screen with the unlock icon.
So I went back into recovery to see if I had a zip that I could flash. The only one there on my SD card that I can find is the CWM/Superuser one from the toolkit. That file is named CWM-SuperSU-v0.94-signed.zip and is in the root directory. I checked and the Nandroid backup seems to be where it should be...
So I figured that I need to flash the factory image but cannot seem to mount the N7 via USB. When I plug it in my Windows 7 machine, Win 7 lets me know that it has installed the "Nexus ADB" driver that my N4 installed and seems to be connected. But there is NO /USB in the Mount menu in Recovery and Windows 7 doesn't see the N7 from the My Computer/Windows Explorer.
My Questions:
Do I need to 'push' a stock image via ADB?
What ADB command do I type to see if the N7 is in-fact accessible from my Windows 7 machine?
I am assuming that when I formatted the three partitions mentioned above I wiped the boot ability of the N7. Is that why it won't go past the Google screen now?
Did I do anything wrong in what I've done so far?
Thanks in advance!
Click to expand...
Click to collapse
Use this tool to connect via adb and restore stock+unroot then after re-lock the bootloader, this will give you the same state as when the tablet left the factory then re-root and start over
http://www.wugfresh.com/nrt/
Oli1122 said:
Use this tool to connect via adb and restore stock+unroot then after re-lock the bootloader, this will give you the same state as when the tablet left the factory then re-root and start over
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Will I lose the SD partition?
My Nandroid backup isn't backed up anywhere else...
That was the first thing I was going to do after connecting the dead N7 to my Windows 7 machine...
Nervous about that aspect!
Thanks
OldDogEyes said:
Will I lose the SD partition?
My Nandroid backup isn't backed up anywhere else...
That was the first thing I was going to do after connecting the dead N7 to my Windows 7 machine...
Nervous about that aspect!
Thanks
Click to expand...
Click to collapse
Yes locking and unlocking your bootloader will wipe all data as far as Im aware. I dont know how viable your Nandrid backup would be regardless though. It was made after the boot looping errors occurred right? That would probably mean restoring a back up from that time frame would reapply all those errors. You could try to pull your nandroid back up using adb to see if theres anything salvageable from it and Id redo everything on your device. Heres a link to a bunch of useful ADB commands which may help ya out. ADB useful commands
cjsspape said:
I dont know how viable your Nandrid backup would be regardless though. It was made after the boot looping errors occurred right? That would probably mean restoring a back up from that time frame would reapply all those errors.
Click to expand...
Click to collapse
That is true. As you can tell I am semi-knowledgeable but not as proficient as many.
So I thought that the Nandroid backup was divided into different pieces... And that I could choose which pieces to restore and by doing that, just restore the portion of my tablet that represented the 'setup' (apps, layout, etc) but not the OS... Maybe I'm wrong about that...
As for ADB, yes, I thought about that as well and already did an ADB Pull to grab the Nandroid ... now I'm doing one to grab everything on the SD Card.
Thanks for that!
Yeh you should be fine so long as you backup your sd before hand. You can also use the same nexus tool to backup your apps and restore them using the developer tools backup
Related
Hi all,
I think I've managed to partially brick my phone, the bizarre thing is that it still mostly works, but I've lost PC connectivity, Wi-Fi and the SD card!
Had my Hero (on Orange UK, standard Orange ROMs) for a while, so thought it about time to play with rooting it and trying some new ROMs out.
Installed Amon-Ra's recovery image (v1.5.2), did a nandroid backup, copied everything obvious off the SD card to my PC (usual precautions).
1. Installed Amon-Ra recovery 1.6.2 - all ok
2. re-flashed with the rooted "stock" HTC image 2.73.405.66, and latest radio (JU6.35.09.26) - all looked ok for a few days
3. decided to try out one of the android 2.1 roms (BeHero) - that got stuck on the boot logo for about 50 mins, so figured that wasn't working.
So tried re-flashing the 2.74.305.66 as that was still on the SD card. That kept re-booting, so I gave up and restored my nandroid backup.
Then things really went wierd!
1. On boot-up I get a notification that the SD card has been removed, even though it is there. Will try to get a clean one, and re-format on the PC, but I'm guessing the partition table has been corrupted?
2. Wi-Fi doesn't work - it just says "Can't start Wi-Fi"
3. If I look in the ROM settings, I'm clearly using the rooted 2.73.405.66 and latest radio! My nandroid backup should have been the default Orange ROM and old radio, and I've definitely went back to that in terms of apps, setttings, etc... Not sure how I still have the new ROM!
4. No PC connectivity (this is a bummer), when I plugin I get "USB device not recognized" on the PC, and the phone claims it is "charging (AC)", I don't get the usual notifications about USB mounting or syncing. So ADB/fastoot don't see it. Not sure if this is related to the SD issue, or the ROM version (maybe I've got a mis-match somewhere)
Other than that, the phone works fine, I can sync with google, internet (though that is a bit flaky), and download apps. Battery life seems to be down to 1 day though, so maybe I still have some android 2.1 stuff lurking around.
Without an SD, I can't download any ROMs though, and without a PC connection, I can't use nandroid or try to debug it that way... Guess I'm stuck?
Anyway, just curious if anyone had any suggestions.
Cheers.
Dan
did you do a wipe before you restored the nandroid restore? if not then thats the problem, always do a data wipe before restoring nandroid backups
have you tried reflashing the radio? also try to wipe after restoring the nandroid, just in case.
edit: valid point about wiping BEFORE flashing. what i meant is that if that doesn't work, try to wipe after restoring as well and see if it boots then.
cheers, no I didn't do a wipe as I figured the nandroid restore was the whole of the ROM, so it would overwrite everything.
Done a wipe now but still no joy. Can't reflash anything without SD or PC access...
Still confused as to why the restore has clearly left a newer ROM in place...
can't you just enter recovery do a wipe and then re flash the rom. recovery should have access to the sd card regardless of what state the rom is in.
I thought you should have tried it, but on a second read, did you try mounting the SD card through recovery?
Hi,
I just tried that again, and even the recovery tool can't mount the SD card, I have re-formatted it and have a clean 2Gb one as well, neither can be seen from the recovery partition.
Looks like I've managed to get it in some really bizare state, my gf says I should have left it alone, don't think I'm ever going to live this down
dancollins said:
Hi,
I just tried that again, and even the recovery tool can't mount the SD card, I have re-formatted it and have a clean 2Gb one as well, neither can be seen from the recovery partition.
Looks like I've managed to get it in some really bizare state, my gf says I should have left it alone, don't think I'm ever going to live this down
Click to expand...
Click to collapse
Have you tried powering up WITHOUT the sd in, then once it is fully loaded, insert ur SD and see if it picks anything up.
just tried that, no joy...
the loss of PC comms is confusing me too, even in recovery mode... might have to claim I dropped it and send it back to orange!
Eventually managed to sort this out, the phone had gone into some strange testing mode, that disabled the uart (USB) and the sdcard.
Found a really useful post on Modaco's forums, search for "No ADB & No SD", look for post #81.
Turned out I had to use fastboot oem enableqxdm 0 to turn on the SD card (at which point WiFi magically started working again!), then reflash the SPL (scary!) which allowed the mystical command "fastboot oem eraseconfig" that also re-enabled the UART and USB connectivity was restored!
As a bonus, I now have SPL 1.76.2007 which has the fastboot holes in, and allows me to remote boot a recovery image. Previously I had 1.76.007 which was locked against that (so had to reflash recovery).
Just goes to show there is almost always a way back!
Excellent,... I this may just help out others.
Do us a favour though pal,... press edit on your 1st post, to change your thread title. Maybe "Nandroid restore left other stuff around?... No ADB, No SD,...... [SOLVED]
i tried to flash paranoid android on my n7 running stock 4.2( i was rooted and unlocked ) after flashing all i get is setup wizard has stopped repeatedly i can boot back to recovery but when i click on install zip there are no files there anymore and the backup i made is no longer there either im not sure what to do next i can get to bootloader and recovery but i cant mount sd card or do anything really any help would be greatly appreciated ive been googling for a couple of hours and cant find my specific problem thanks
Recovery > Factory Reset / Wipe
^ that should get it back to working
You can also "adb shell" in while in recovery and look if your backups are in a subfolder of /data/media, like /data/media/0 most likely.
And in the future always keep a copy of your backups on your PC
HellcatDroid said:
Recovery > Factory Reset / Wipe
^ that should get it back to working
You can also "adb shell" in while in recovery and look if your backups are in a subfolder of /data/media, like /data/media/0 most likely.
And in the future always keep a copy of your backups on your PC
Click to expand...
Click to collapse
i tried recovery but it does nothing im trying to set up adb but it just makes no sense to me at all its almost like the computer doesnt even see the phone i know it has to be something simple as to why i cant access the files from clockwork recovery but for the life of me i cant figure it out
Download Google Nexus 7 Toolkit V3.2.0
choose option "9. Download, Extract + Flash Google Factory Stock Rom and follow the instructions..
i had the exact same problem with my nexus 7 and this worked like a charm
hope it helps.
Thanks for the help but I fixed the problem. I let it boot to the setup screen where it kept saying setup wizard has stopped. From there I could recognize the device on a computer and transfer files over even though it read grouper on full android and not nexus 7. Now I'm on eclipse and it seems to be working great but I'm going to get rid of clockwork and install twrp just so I can hopefully not have that happen again. One weird thing though when I look for my backup I made prior to all of this and even the paranoid android ROM and gapps I can't find them anywhere on my SD card its like they literally vanished.
Sent from my Nexus 7 using Tapatalk 2
oogabooga912666 said:
Thanks for the help but I fixed the problem. I let it boot to the setup screen where it kept saying setup wizard has stopped. From there I could recognize the device on a computer and transfer files over even though it read grouper on full android and not nexus 7. Now I'm on eclipse and it seems to be working great but I'm going to get rid of clockwork and install twrp just so I can hopefully not have that happen again. One weird thing though when I look for my backup I made prior to all of this and even the paranoid android ROM and gapps I can't find them anywhere on my SD card its like they literally vanished.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Where did you copy the files to? I have the same thing. The only folders I have are: Alarms, android, carbon, clockworkmod, dcim, digital editions, download, mobile systems, movies music notifications pictures podcasts and ringtones?
Unless there is a wy for it to be an actual drive right now it shows up as a music device in my computer.
when you did a wipe did you wipe all data? I know when I went to flash a ROM I wiped data like I did with my bolt and it erased everything on my n7.
Sent from my Infected HTC Rezound using Tapatalk 4 Beta
Hi guys, I hope this thread is still active...
I'm having the same problem here. I tried installing cyanogenmod onto my n7 and am now getting the same "unfortunately, setup wizard has stopped" message. I've tried wiping the data and rebooting, to no avail. I have the toolkit, but it won't recognize the tablet so I can't reboot from there. I have a backup on my PC, but can't get to it! Sigh...
Thanks in advance for the help
My N7 is rooted and stock... I used the N7 Toolkit method... My N7 is 32gb non-3G version...
It's been working fine, no problems. I thought that it was a little laggy since I installed a 2nd account on it ... so a day ago I deleted the 2nd account hoping to get rid of the lagginess that started after installing the 2nd account.
Today I came home with the N7 and I heard some notifications when it logged into my Wifi... And about 30 mins later I went to use it and the wall paper that is usually showing went black, the screen did some funny things and the tablet reset.
Now it's stuck in a boot loop...
I can get into the bootloader and recovery, but whenever I exit, it goes back into the boot loop.
Since I hadn't installed anything custom when rooting, do I even have Nandroid? Can I back it up and connect to USB before wiping?
Does wiping erase the SD portion of the memory?
Any ideas for troubleshooting? Would love to know what happened here...
Thanks...
What did you come up with by searching the forums or Google?
Hemidroids said:
What did you come up with by searching the forums or Google?
Click to expand...
Click to collapse
As with many things, the info that I found is conflicting. Since I had been burned by trying things before verifying what I was doing, for once, I decided to reach out for advice BEFORE I erased something that isn't recoverable.
Yes, I know that many on XDA hate users who ask for help before researching on their own. The problem for me is that I couldn't find a clear answer.
Since I made my post, I tried a few things...
Details and questions are here: http://forum.xda-developers.com/showthread.php?t=2089144
Thanks for your response, although I get the feeling that you had expected me to know the answer to my question...
OldDogEyes said:
My N7 is rooted and stock... I used the N7 Toolkit method... My N7 is 32gb non-3G version...
It's been working fine, no problems. I thought that it was a little laggy since I installed a 2nd account on it ... so a day ago I deleted the 2nd account hoping to get rid of the lagginess that started after installing the 2nd account.
Today I came home with the N7 and I heard some notifications when it logged into my Wifi... And about 30 mins later I went to use it and the wall paper that is usually showing went black, the screen did some funny things and the tablet reset.
Now it's stuck in a boot loop...
I can get into the bootloader and recovery, but whenever I exit, it goes back into the boot loop.
Since I hadn't installed anything custom when rooting, do I even have Nandroid? Can I back it up and connect to USB before wiping?
Does wiping erase the SD portion of the memory?
Any ideas for troubleshooting? Would love to know what happened here...
Thanks...
Click to expand...
Click to collapse
First if you have a custom recovery, boot into that, wipe cache, then dalvik, and try rebooting. See if that works.
Nandroid would be the backup of your entire ROM that you made either using ROM Manager or manually initiating a backup in recovery.
Wiping using ClockworkMod Recovery or TWRP Recovery will leave the /sdcard area (/data/media) alone, however it'll remove your ROM. At that point, you'll need to re-flash a custom ROM to your device. If you reload the stock N7 images from Google, it WILL erase your /sdcard section!
You can push files to your device while in recovery using the adb push command. You can also pull files from your device using the adb pull command.
adb push <name of file> <location on device you want to push to>
EXAMPLE: adb push ROM.zip /sdcard/
adb pull <location of file on device>
EXAMPLE: adb pull /sdcard/ROM.zip
Research adb, adb push, adb pull commands.
Yes i know. I ****ed up. But somehow i was tinkering and managed to delete the entire internal storage. I can still get into fast boot and.twrp. Can someone please help me?
What was i trying to fix? Check my other thread about the headphone jack.
Edit:Also. Twrp says i dont have an os above every swipe screen...
AW: [Q] Nexus 7 stuck on google screen boot
Have you tried reflashing stock?
Sent from my Nexus 7 running Android 4.2.1
If you have an OTG cable and a USB key you should be able to make ROMs or other backups which you preserved OFF THE TABLET available to TWRP.
If not, take the above poster's advice and install pure stock to copy stuff (ROMs, recovery images, etc) back on to the tab via MTP.
I too blew away all of /data once with that "format data" button in the touch version of TWRP; I feel your pain.
Um.....I may have made a mistake and swiped on all the clear screens...including internal memory...so...T_T Am i screwed???
JoshuaXedos said:
Um.....I may have made a mistake and swiped on all the clear screens...including internal memory...so...T_T Am i screwed???
Click to expand...
Click to collapse
You're not really screwed, you should be able to flash another ROM from recovery.
As long as you can get into fastboot, you'll be fine. The easiest way is to download and install Nexus Root Toolkit, then use the "back to stock" part to flash the factory image following the instruction.
I have got something even worse
My nexus 7 tab started freezing during use and then after booting in safe mode and wiping cache in recovery mode it now doesn't even go past the google screen. I haven't even flashed anything to it at all and it's showing these crazy symptoms (The bootloader is still locked and the device is not even rooted). I still have access to the adb sideload mode and fastboot but I am confused af as to what has happened
Any ideas guys?
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.