Related
Ok I just need a little help and advice so if you one of you out there in XDAland can help I’ll be truly grateful…
I’ve got the 32gb Nexus 7 which I rooted via the Wugfresh method and added I CWM for my recovery and did the OTA update to Jelly Bean 4.2.1. The last 6 months life have been peachy. Even the misses and her iDevices are jealous of my little corner of Android heaven.
So last night pick up the 7 and notice it’s running a tad sluggish and I also notice the battery is low and flashing red, so I plug in the power cable and attempted to shut it down and it just hangs… I give it 5 minutes and still not shut down so I hold power & volume down and get in to the Bootloader from here I select start and the tablet just hangs on the Google cross (red, blue, yellow, green). This now happens every time I power down even though there has been a good charge (6 hours) done. If I now go back in the Bootloader and try selecting the Recovery Mode I get the Android robot with the red warning triangle and the words “No Command” and that’s it. If I try the factory reset of power button & volume up from recovery mode I get nothing.
From the bootloader I see
Fastboot Mode
Product Name - grouper
Variant - grouper
HW version - ER3
Bootloader Version - 4.13
Baseband Version - n/a
Serial Number xxxxxxxxxxxxxxxxxxxx
Signing - not defined yet
LOCK STATE - UNLOCKED
Can someone advise what the best thing I can do to revive the 7? I don’t mind losing the data but I’m just unsure what to do next. I’ve read a few threads but none pointed me in the direction I think I need to be in…
Thanks in advance for any help given.
That's funny as I put my 16gig nexus 7 on charge a couple of hours ago and just went to pick it up and it was on the bootloader screen, but I managed to reboot and everything is fine, its funny cos I've had similar experience with galaxy s3 but that was dead after a night on charge. I've sent the s3 of for repair under warranty thinking it was the sudden death syndrome on the s3, but now I'm worried the charger might be at fault.
Has anyone heard of a charger frying an android phone or putting nexus 7 in bootloader mode? Or is it just a coincidence?
Sent from my Nexus 7 using xda premium
@OP
The recovery you describe is the stock recovery. If you used an OTA process after rooting, probably that is what overwrote the CWM install you did previously - so that explains why you see what you do when you boot to recovery via the bootloader menu.
When you use the "reset by holding the power button down for 30 seconds" you are crashed the running OS and potentially corrupted any filesystems which are mounted "rw" (read-write). So, that might explain the bootloops that occurred thereafter.
You have a couple options, but before you try any of them, I would suggest that you observe the "power state animation" that occurs for about 10 seconds when you plug the tablet in to the charger with the tablet turned off: it shows you graphically how much charged the battery has. If the animation starts with a nearly all black battery, and then "fills up", the battery is still deeply discharged; if it is all white, or mostly all white, and the animation only "tops off" the battery, it has a good charge.
If that animation shows a battery which is still discharged, I would try to solve that problem before doing anything further. It was a low battery condition that got you into trouble in the first place; no point in making things even worse.
OK. Well, if you weren't a toolkit user, I would suggest a couple things that could be done manually using a custom recovery to attempt a repair of the /data filesystem, or rescuing your raw data for a later data recovery effort. But they involve command-line stuff, so me mentioning it is a waste of time. Suffice it to say that if you still have an unlocked bootloader and functioning drivers on your PC, you can re-install whatever custom recovery you want (using either fastboot or Wugfresh) and then use the capabilities of that custom recovery. Given that you didn't even realize that your custom recovery went missing until now, that's probably also a waste of time too - I probably can safely assume you don't know what its' full capabilities are.
So, flash a custom recovery and perform a reformat of the userdata partition ("Wipe Data" in TWRP, don't know what it is in CWM). You could even try taking a Nandroid backup before doing this, but the problem with doing this is that by default it will try writing to /data - so under the presumption that your userdata partition is hosed up, writing a whole lot of stuff to it (the backup) may not create a reliable backup image(s). With TWRP you could write backups to an external device, though.
That leaves a factory reset. If you do it with the stock recovery (simultaneously press power and vol-up for about 1 second after the recovery splash screen shows up to get the menu), it will erase EVERYTHING in the /data partition - including your everything in the psuedo-SD card.
Without any further learning on your part (abandonment of toolkits), it seems like the stock recovery factory reset is the least-effort solution for you. As I said, this will destroy ALL of your data on the device, but your device should return to a bootable condition. If you made any Nandroid backups and got them off the tablet, you could restore them after installing the custom recovery which made those same backups.
good luck
As last user said, if you have any nandroids you could restore them. And honestly it'd be so much easier to just boot an img. Not that hard.
Sent from my Motorola XPRT
Defibrillator...
Sent from my Nexus 7 using xda app-developers app
@bftb0
Thanks for the response and I’m going to follow your advice… I have done the command line root method twice with this my phones the HTC Desire and the then Sensation so I have experience in the dark art… it was just I couldn’t see a way of enabling the ADB drivers so my PC and 7 could look at/see each other but I have found the following http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
and this goes over what I need to do so I’ll give this a try and see how it goes. Like I say I don’t really need the data, I only used the 7 as a media hub and social media tool so I don’t mind putting the music and films back on it and the few apps and games is no big deal.
@FitAmp if this don’t work I may be taking your advice hahahahahaha!!!
bricked
slybunda said:
bricked
Click to expand...
Click to collapse
@slybunda May I ask why you say bricked?
Another case where the N7 seems to overly discharge the battery and not be able to recharge it. I've heard of this several times, it just won't charge the battery once it gets too low.
I bet if you can get the battery to charge it'll be fine. Or failing all else, this place has the battery for $30.
http://www.portatronics.com/product...oogle-Asus-Nexus-7-Original-Battery-Part.html
It is NOT bricked.
Dr Asqueroso said:
@slybunda May I ask why you say bricked?
Click to expand...
Click to collapse
Hi, Dr Asqueroso...
'Bricked' is a certainly a bit pre-emptive... if the BOOTLOADER is still good (and from your description, it sounds like it still is), then you have a very good chance of resurrecting your tablet.
The thing is, from your description, you're only 'bootlooping'... which is trivial to get out of... if you have a recent NANDROID backup (or for that matter, a flashable ROM .zip), on your internel storage and you know how to FASTBOOT FLASH a CUSTOM RECOVERY.
Your options are threefold...
----------------------
1) Use the STOCK FACTORY recovery to perform a factory reset. (As detailed by bftb0, earlier).
2) FASTBOOT FLASH a custom recovery (CWM or TWRP).
-- http://www.teamw.in/project/twrp2/103
-- http://www.clockworkmod.com/rommanager
I note you used CWM previously, so fastboot flash this recovery, and restore your last NANDROID backup. If you didn't make any NANDROIDs, then flash some other CUSTOM ROM. Or better still, use the 'wipe data' option in your Custom Recovery. I've had 'bootloops' and other weird egregious behavior myself, and this usually fixes it. (Sometimes, even wiping 'CACHE' and 'DALVIK' can make mysterious problems vanish!.)
3) Restore back to FACTORY stock.
-- http://developers.google.com/android/nexus/images
(You need the 'nakasi' version for your 'grouper' tablet).
This last option carries some risk, because it reflashes the BOOTLOADER, which is always a risky procedure (a corrupt flash will hardbrick the tablet). So, ABSOLUTELY make sure your tablet is fully charged AND you have a good USB connection to your PC.
I note you're still on bootloader v4.13, so you could edit the 'flash-all.*' script from Factory Stock JellyBean 4.1.2 (JZO54K) to remove the command to flash the bootloader. Flash as normal (by running the script), and then take the OTA update to 4.2.2 (JDQ39) over WiFi... this will still update the bootloader (to v4.18), but because of the way OTAs work, the risk is significantly reduced.
----------------------
But before you contemplate doing any of this... you need to ascertain if your battery is in good shape.
Here's what I would recommend if the battery is failing to charge correctly...
1. Plug the Nexus 7 into a wall charger.
2. Immediately press Volume Down and Power at the same time to reach the Bootloader
3. From the Bootloader menu, press Volume Down until you see “Power Off Device.”
4. Press the Power button to select the "Power Off Device" option.
5. Once your device is off, unplug the charger and then plug it back into the device.
If you see a large white battery shaped logo, that is flashing nearly all white, then you have a good level of charge... if it's flashing nearly all black (with only a bit of white), then the charge level is low... and fastboot flashing anything is not recommended.
Good luck... and hope this helps.
Rgrds,
Ged.
GedBlake said:
Hi, Dr Asqueroso...
'Bricked' is a certainly a bit pre-emptive... if the BOOTLOADER is still good (and from your description, it sounds like it still is), then you have a very good chance of resurrecting your tablet.
The thing is, from your description, you're only 'bootlooping'... which is trivial to get out of... if you have a recent NANDROID backup (or for that matter, a flashable ROM .zip), on your internel storage and you know how to FASTBOOT FLASH a CUSTOM RECOVERY.
Your options are threefold...
----------------------
1) Use the STOCK FACTORY recovery to perform a factory reset. (As detailed by bftb0, earlier).
2) FASTBOOT FLASH a custom recovery (CWM or TWRP).
-- http://www.teamw.in/project/twrp2/103
-- http://www.clockworkmod.com/rommanager
I note you used CWM previously, so fastboot flash this recovery, and restore your last NANDROID backup. If you didn't make any NANDROIDs, then flash some other CUSTOM ROM. Or better still, use the 'wipe data' option in your Custom Recovery. I've had 'bootloops' and other weird egregious behavior myself, and this usually fixes it. (Sometimes, even wiping 'CACHE' and 'DALVIK' can make mysterious problems vanish!.)
3) Restore back to FACTORY stock.
-- http://developers.google.com/android/nexus/images
(You need the 'nakasi' version for your 'grouper' tablet).
This last option carries some risk, because it reflashes the BOOTLOADER, which is always a risky procedure (a corrupt flash will hardbrick the tablet). So, ABSOLUTELY make sure your tablet is fully charged AND you have a good USB connection to your PC.
I note you're still on bootloader v4.13, so you could edit the 'flash-all.*' script from Factory Stock JellyBean 4.1.2 (JZO54K) to remove the command to flash the bootloader. Flash as normal (by running the script), and then take the OTA update to 4.2.2 (JDQ39) over WiFi... this will still update the bootloader (to v4.18), but because of the way OTAs work, the risk is significantly reduced.
----------------------
But before you contemplate doing any of this... you need to ascertain if your battery is in good shape.
Here's what I would recommend if the battery is failing to charge correctly...
1. Plug the Nexus 7 into a wall charger.
2. Immediately press Volume Down and Power at the same time to reach the Bootloader
3. From the Bootloader menu, press Volume Down until you see “Power Off Device.”
4. Press the Power button to select the "Power Off Device" option.
5. Once your device is off, unplug the charger and then plug it back into the device.
If you see a large white battery shaped logo, that is flashing nearly all white, then you have a good level of charge... if it's flashing nearly all black (with only a bit of white), then the charge level is low... and fastboot flashing anything is not recommended.
Good luck... and hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
First of all a massive Thank You all so much for the advice...
I think I've got it in the respects of each step but I'm just stuck with getting the drivers to work. I've installed the Java Dev Kit, the latest SDK from the Android site and successfully installed both the Tools and the Google USB Drivers. I also got the Asus drivers for the 7 and I have unziped the stock recovery JZO54K which ready to go. However can't get my 7 to show up in CMD Prompt via ADB devices string but if add my sensation it pops up everytime...
I've tried this process on a Windows 8 machine and a XP install too and the 7 is never picked up.
Does this mean the 7 is dead and stuck in the factory boot menu? What am I doing wrong?
This is killing me... :crying:
Dr Asqueroso said:
First of all a massive Thank You all so much for the advice...
I think I've got it in the respects of each step but I'm just stuck with getting the drivers to work. I've installed the Java Dev Kit, the latest SDK from the Android site and successfully installed both the Tools and the Google USB Drivers. I also got the Asus drivers for the 7 and I have unziped the stock recovery JZO54K which ready to go. However can't get my 7 to show up in CMD Prompt via ADB devices string but if add my sensation it pops up everytime...
I've tried this process on a Windows 8 machine and a XP install too and the 7 is never picked up.
Does this mean the 7 is dead and stuck in the factory boot menu? What am I doing wrong?
This is killing me... :crying:
Click to expand...
Click to collapse
No... it just means you're stuck in what is ubiquitously called 'driver hell'. Windows has always been a pain in the arse when it comes to drivers.
If you have a Windows XP box, you could try the following...
Download my copy of the FASTBOOT/ADB files for XP...
http://dl.dropboxusercontent.com/u/...orXP-MD5_8e02ab9b4b8463b9ee5c2063477b01ec.zip
Unzip to a folder on the Windows Desktop.
Unzip and copy the files from nakasi-jzo54k into the same folder.
You should now have a folder with the following files in it...
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
Delete 'bootloader-grouper-3.41.img' and edit 'flash-all.bat' to reflect this... that is to say, remove the line...
Code:
fastboot flash bootloader bootloader-grouper-3.41.img.
This is to avoid unnecessarily flashing the BOOTLOADER partition, and which in any event will only downgrade your current BOOTLOADER.
-----
Boot your Nexus 7 into BOOTLOADER mode, by pressing Vol. Down (& hold) and the Power Button.
Connect your Nexus 7 to your Windows XP PC, via a USB cable (preferably the one that shipped with the N7 originally).
Open a command prompt window on the folder into which you have copied all of the aforementioned files, and type...
Code:
fastboot devices
It should return a SERIAL NUMBER... if it does, you have a working FASTBOOT connection, and you're free to run flash-all.bat
This should restore JellyBean 4.1.2... and upon a successful reboot and a WiFi connection, an OTA upgrade will be proffered.
Allow this, and your Nexus will be upgraded to JellyBean 4.2.2 (JDQ39).
Good luck.
Rgrds,
Ged.
Okay so I have a folder with the following
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
But I'm stuck on the edit line?? sorry for being a pain can you explain this bit.. how do you edit the flash-all.bat??
Delete 'bootloader-grouper-3.41.img' and edit 'flash-all.bat' to reflect this... that is to say, remove the line...
Code:
fastboot flash bootloader bootloader-grouper-3.41.img.
This is to avoid unnecessarily flashing the BOOTLOADER partition, and which in any event will only downgrade your current BOOTLOADER.
Open the bat file in notepad.
Sent from my Galaxy Nexus
Done the edit and ran the flash-all.bat... The serial number has appeared after the fastboot command but now I seem stuck on the sending system command of 446268 been like this for 20+ minutes and somehow my bootloader is showing 3.41 on the tablet.
What next?
Dr Asqueroso said:
Okay so I have a folder with the following
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
But I'm stuck on the edit line?? sorry for being a pain can you explain this bit.. how do you edit the flash-all.bat??
Click to expand...
Click to collapse
Sometimes it's easier to 'just do' than explain 'how to do'...
Here is the modified 'flash-all.bat' script, with the line removed.
http://dl.dropboxusercontent.com/u/37483979/flash-all-MD5_ a687082ef3179feb40ba108436dc5768.zip
------
Maybe I'm just being overcautious when it comes to BOOTLOADER stuff...
It's entirely possible you could just run the original 'flash-all.bat' as is... without problems... as many people do, and as Google intended.
So, it's not critical you delete bootloader-grouper-3.41.img or run the modified .bat file... just ensure you have a damn good USB connection and power to both devices before you do.
Rgrds,
Ged.
---------- Post added at 12:55 AM ---------- Previous post was at 12:41 AM ----------
Dr Asqueroso said:
Done the edit and ran the flash-all.bat... The serial number has appeared after the fastboot command but now I seem stuck on the sending system command of 446268 been like this for 20+ minutes and somehow my bootloader is showing 3.41 on the tablet.
What next?
Click to expand...
Click to collapse
Sending /system has always been problematic for me as well... you need to change to a different USB port on your PC.
Using the Vol. Keys navigate to RESTART BOOTLOADER... disconnect and reconnect to a different USB port, and try again.
If you're BOOTLOADER is showing 3.41, don't worry about it. The issue was never about the version, but about flashing it.
This will be taken care of later, with the OTA upgrade.
Rgrds.
Ged.
There must be something else going wrong as every step I've taken thus far has worked but the final sending bit... currently on my machine see the following... it's been like this for 2 hours...
Dr Asqueroso said:
There must be something else going wrong as every step I've taken thus far has worked but the final sending bit... currently on my machine see the following... it's been like this for 2 hours...
Click to expand...
Click to collapse
2 hours is way too long... it should take less than 5 minutes to flash back to stock.
I suspect a USB connectivity issue... open another command prompt window, and type
Code:
fastboot devices
If you don't see a SERIAL NUMBER, then your FASTBOOT connection has died...
Try again, from a different USB port... and maybe a different USB cable.
----
You are actually getting somewhere though... your screenshot indicates that 'boot' went over successfully.
Don't give up hope - persevere!
Rgrds,
Ged.
Ok I'll try it again when I get home from work...
Okay followed all the steps but I think the tablet is not going to play nice... I just can't get past the sending system bit.
The 7 is now showing
Fastboot Mode (in red)
Product Name - grouper
Variant - grouper
HW version - ER3
Bootloader Version - 4.18
Baseband Version - n/a
Serial Number xxxxxxxxxxxxxxxxxxxx (now showing my number)
Signing - not defined yet
LOCK STATE - UNLOCKED
My CMD prompt window is yet again just showing sending system and nothing. Been like this for the past 30 mins or so... I've swapped my USB ports over tried and the process a few times and still no joy. I think I've been defeated.
It looks like the 7 will have to go back... but can I make a warranty claim from Asus in it's current state or will I have to lock it somehow??
Failing that I'll "lose" it and claim off the house insurance.
Oooops the CMD window is doing something different...
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4944 KB)...
OKAY [ 0.656s]
writing 'boot'...
OKAY [ 0.203s]
sending 'recovery' (5446 KB)...
OKAY [ 0.719s]
writing 'recovery'...
OKAY [ 0.219s]
erasing 'system'...
OKAY [ 0.094s]
sending 'system' (471804 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5264.891s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
< waiting for device >
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s
C:\android-sdk\platform-tools>
Anyone with any suggestions as to my next move?
Hello, after updating my Nexus 7 (Wi-FI) via OTA my nexus wouldn't turn on... it just got stuck on the nexus logo.
I tried wiping, flashing the OTA via sideload, also tried flashing the factory image also via sideload, but I kept getting an error (error 7 I think).
After that, I used the fastboot update image-nakasi-krt16s.zip but it got stuck on sending system < 611886 KB >.
I don't know what else to do, any help would be appreciated!
Same problem here. I'm running a pure stock. In rooted device and it bricked on me.
Sent from my SGH-M919 using XDA Premium 4 mobile app
theblackout said:
Hello, after updating my Nexus 7 (Wi-FI) via OTA my nexus wouldn't turn on... it just got stuck on the nexus logo.
I tried wiping, flashing the OTA via sideload, also tried flashing the factory image also via sideload, but I kept getting an error (error 7 I think).
After that, I used the fastboot update image-nakasi-krt16s.zip but it got stuck on sending system < 611886 KB >.
I don't know what else to do, any help would be appreciated!
Click to expand...
Click to collapse
Speaking of getting stuck with the "sending system" process, It was also mentioned in this thread.
It seems that you could go back to 4.3 by flashing factory images and flash 4.4 factory image again, then you are good to go.
Just for you information.
noradoor said:
Speaking of getting stuck with the "sending system" process, It was also mentioned in this thread.
It seems that you could go back to 4.3 by flashing factory images and flash 4.4 factory image again, then you are good to go.
Just for you information.
Click to expand...
Click to collapse
Same thing using that thread, I.
fastboot erase system
fastboot flash system system.img (old 4.3 img)
stuck on sending system <529061 KB>
getting nervous here, any other ideas?
OK, I finally got it back to life!
I fastboot cwm recovery, then adb sideload this rom: http://forum.xda-developers.com/showthread.php?t=2222374
That should do it
theblackout said:
OK, I finally got it back to life!
I fastboot cwm recovery, then adb sideload this rom: http://forum.xda-developers.com/showthread.php?t=2222374
That should do it
Click to expand...
Click to collapse
I will try this when i get home from work and see how it goes.
Ksealy03 said:
I will try this when i get home from work and see how it goes.
Click to expand...
Click to collapse
Hi, Ksealy03...
Erm... but before you do that... Whilst fastboot flashing stock Android 4.4 (KitKat), you might want to try changing the USB cable that connects your Nexus 7 to your PC to a different USB port on your PC. Or, possibly even changing the USB cable completely.
The 'stuck on sending image' problem is a commonly reported one here on XDA.
Indeed, I myself don't recall NOT having the problem, whenever I fastboot flash factory stock... it's always the same, "Oh no, here we go again... still sending system image" after five minutes. It's almost predictable - I just expect it happen now.
Anyway... I then disconnect my USB cable from my PC, reboot the Nexus 7 bootloader... reconnect my USB cable TO A DIFFERENT USB PORT on the PC - and begin the flash procedure all over again... and then it works! System image goes over.
Quite why this happens, I've no idea... but I suspect it has something to do with the size of system image, 'cos everything else (recovery, etc) goes over quite happily, without problems. At some point the fastboot connection dies (times out?), and you have to re-establish it.
Rgrds,
Ged.
GedBlake said:
Hi, Ksealy03...
Erm... but before you do that... Whilst fastboot flashing stock Android 4.4 (KitKat), you might want to try changing the USB cable that connects your Nexus 7 to your PC to a different USB port on your PC. Or, possibly even changing the USB cable completely.
The 'stuck on sending image' problem is a commonly reported one here on XDA.
Indeed, I myself don't recall NOT having the problem, whenever I fastboot flash factory stock... it's always the same, "Oh no, here we go again... still sending system image" after five minutes. It's almost predictable - I just expect it happen now.
Anyway... I then disconnect my USB cable from my PC, reboot the Nexus 7 bootloader... reconnect my USB cable TO A DIFFERENT USB PORT on the PC - and begin the flash procedure all over again... and then it works! System image goes over.
Quite why this happens, I've no idea... but I suspect it has something to do with the size of system image, 'cos everything else (recovery, etc) goes over quite happily, without problems. At some point the fastboot connection dies (times out?), and you have to re-establish it.
Rgrds,
Ged.
Click to expand...
Click to collapse
Ok im actually trying it now. i have a different USB cable that I will use.
teraonic 318
No luck. because my debugger is not on I can t do anything. ADB and fastboot wont even recognize the device. probably just call up Asus.
Ksealy03 said:
No luck. because my debugger is not on I can t do anything. ADB and fastboot wont even recognize the device. probably just call up Asus.
Click to expand...
Click to collapse
I had a similar issue that I was able to fix. Hopefully this will help you too.
I have a Nexus 7 that is rooted, stock ROM, unlocked bootloader. I have gotten many OTA updates since buying the device, and all previous OTA updates have completed without a hitch.
On the most recent OTA Kit Kat update, the device froze when trying to apply the update. It just displayed the boot animation in perpetuity.
I was able to use the Nexus Toolkit here on XDA (LINK) to load the stock Kit Kat ROM. Hope that helps.
Hi there
@bftb0 : yet another victim of the corrupt bootloader .img ! (see thread #2573015)
bftb0 said:
The versions distributed with JWR66Y and KOT49H* Google factory images are INVALID.
Click to expand...
Click to collapse
Device : Nexus 7 2012 wifi (grouper), stock 4.4.4 KTU84P, never rooted before
Symptoms : black screen, not booting at all even to bootloader. :crying:
Only faint light of hope is that my PC is still reacting to plugging the Nexus in with USB.
Windows beeps and shows an "unknown usb device" error then fails finding a driver.
Windows Device manager shows "APX" with yellow sign below "Other devices".
Question : bricked or any hope left ? Pleeease what can I do ?
How I got there :
NRT hung when flashing bootloader while reinstalling stock 4.4.0 (nakasi-krt16s-factory-da7dee49).
The story, going from bad to worse :
It started with a sudden reboot for not appearent reason (incidentally while an Avast routine scan was running).
Then endless reboot, with the 4 color balls shaking indefinitely (power plugged in or not).
Looked at forums... Reboot into bootloader. Recovery mode, wiped cache. Got plenty of error msg "E:failed to mount /cache"
Bootloop! Sometimes showing just the white Google logo, sometimes showing the rolling colors for a few seconds.
Recovery mode, erase user data (no backup, hate this thing). Again plenty of error msg "E:failed to mount /cache"
Could the missing /cache be related to Avast since the first reboot occurred while it was running? Maybe the theft protection is overly proctective?
Installed Nexus Root Toolkit 1.8.4 (extremely well done utility btw, ***huge congrats*** :good on Win 7 64bits. Installed drivers #1.
Tried flashing a clean 4.4.4 (nakasi-ktu84p-factory-76acdbe9).
FAILED (remote: Bootloader is locked.)
Successfully unlocked bootloader with NRT. Restart with an open lock below the white Google logo. So far so good.
Try flashing 4.4.4 again, same image.
writing 'bootloader'... FAILED (remote: (InvalidState))
What the heck ?!
Found the thread #2573015 I was quoting above on corrupt bootloader .img files from Google.
As it turns out, the bootloader MD5 is also WRONG in KTU84P.
Managed somehow to restart into bootloader again in spite of the bad bootloader...
Maybe the old one was not completely replaced yet?
Quick quick, let's try flashing another bootloader that works !
This time use the latest available with a non-corrupt bootloader .img : 4.4.0 (nakasi-krt16s-factory-da7dee49)
erasing 'boot'... blahblah
sending 'bootloader' (2100 KB)... OKAY [ 0.281s]
writing 'bootloader'... *** STUCK ***
Wait and wait until lost hope
Tried rebooting but nothing happens, just black screen, I end up with the symptoms I described upfront.
When plugged into the pc, keeping power button down makes windows beep, and the "APX" unknown device comes and goes in win device manager. Adding the vol+ or vol- buttons (or both) produces identical results.
Uninstalled APX device from PC. Power button down. Windows beeps "unknown usb device". "APX" shows up again in device manager... And so on.
Screen still pitch black.
Any other USB driver I can try to regain a working connection?
Worth looking into other remedies, like nkFlash?
GedBlake said:
If you corrupt, or erase the bootloader... the Nexus 7 is dead, from which there is known recovery. Although it's been speculated that an nvFlash tool could flash a new bootloader.
Click to expand...
Click to collapse
Thanks for reading me so far, I know it's long, but if you've read to this point maybe you can help?
What a similar story
this is such a coincidence as I have also had the dreaded bad to worse stage as my story started off here http://forum.xda-developers.com/showthread.php?t=2783631 and then got much worse and it continues here http://forum.xda-developers.com/showthread.php?t=2798181 .
I have been searching on the internet for the last month and so far there does not seem to be any general solution (which does not require hardware device surgery) to this particular type of problem as it is not something Google appear to have expected. I found that a lot of people seem to say its hypothetically possible to repair this thing via software means as that is how it was rendered inoperable in the first place and they also say it is not practically possible to hard brick any device through software means although with the nexus 7 there seems to be some kind of issue with crypto-signing which makes it a nightmare to access the hardware through nvflash unless there was some blob file made before hand
I am currently discussing the situation in this thread and you could join it to keep up to date
http://forum.xda-developers.com/showthread.php?t=2798181&page=2
Hi All,
My Nexus 6P started bootlooping, i.e can't get passed the "Google" screen. Unfortunately, I do not have a backup of my pictures. I would like to get them off the phone.
I tried to recover it by wiping the cache and sideloading the official rescue ota image (angler-ota-n2g48c). That did not solve the problem. When running
Code:
fastboot flashing unlock
, I get
Code:
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
So the bootloader appears to be locked. Unlocking it would erase the device as far as I can tell. Is there any way to get the pictures off the device?
Thanks a lot in advance!
You are correct, unlocking will erase your phone with all the data. When you connect your phone to the computer and if it doesn't automatically recognize the device then you don't have MTP is selected and you haven't enabled USB debugging which will allow the device to connect to a computer.
Did you use Google Photos? then your photos should automatically be backed.
madtowneast said:
Hi All,
My Nexus 6P started bootlooping, i.e can't get passed the "Google" screen. Unfortunately, I do not have a backup of my pictures. I would like to get them off the phone.
I tried to recover it by wiping the cache and sideloading the official rescue ota image (angler-ota-n2g48c). That did not solve the problem. When running
Code:
fastboot flashing unlock
, I get
Code:
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
So the bootloader appears to be locked. Unlocking it would erase the device as far as I can tell. Is there any way to get the pictures off the device?
Thanks a lot in advance!
Click to expand...
Click to collapse
Like Draxz said, if you were using Google Photos they should all be in your cloud. Any luck there?
Tried adb pulling the photos directory? (DCIM I believe)
Solution for data recovery off bootlooping Nexus 6P
Hi there, I have just been in a similar situation where my Nexus 6P randomly went into bootloop and I didn't have all my data backed up. After countless hours of research and talking to data recovery companies I found Digital Recovery in Hamilton New Zealand and the guy there, James, managed to get my data off AND fix my phone! Give these guys a call 0800 77 77 22. Everyone else told me it was impossible but James worked hard and researched until he found a solution. So don't give up hope and don't factory reset or wipe your device, there is hope to get your data back and get your phone working again.
hi yesterday i was far from home with 5% battery and i take some calls some photos and battery 0%
when i got home i plugged in and battery is too laow message screen appear and after the message:
The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device to learn more:
g.co/ABH
can.t be power off when this message appear, i need to let battery drain and power key do nothing
and msmdownloand show nothing
Oneplus 6T on latest beta
Windows 10 i don.t know if has all drivers needed for a unbricked process
amkulcsar said:
hi yesterday i was far from home with 5% battery and i take some calls some photos and battery 0%
when i got home i plugged in and battery is too laow message screen appear and after the message:
The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device to learn more:
g.co/ABH
can.t be power off when this message appear, i need to let battery drain and power key do nothing
and msmdownloand show nothing
Oneplus 6T on latest beta
Windows 10 i don.t know if has all drivers needed for a unbricked process
Click to expand...
Click to collapse
I've had this before. If your phone has fully discharged and you plug in the charger the phone will boot up and stay on that message.
Just leave it to charge for five minutes, unplug the charger, then force reboot it by holding the power and volume down buttons together until it reboots. It should then boot normally and then you can plug in and continue charging.
ebproject said:
I've had this before. If your phone has fully discharged and you plug in the charger the phone will boot up and stay on that message.
Just leave it to charge for five minutes, unplug the charger, then force reboot it by holding the power and volume down buttons together until it reboots. It should then boot normally and then you can plug in and continue charging.
Click to expand...
Click to collapse
SOLVED
wait till screen get of install drivers correctly then press volume keys (+ and -) and connect to pc, in device manager appear at ports as qualcom... and open msmdownload tool and press start
amkulcsar said:
SOLVED
wait till screen get of install drivers correctly then press volume keys (+ and -) and connect to pc, in device manager appear at ports as qualcom... and open msmdownload tool and press start
Click to expand...
Click to collapse
Yeah you didn't need to do that. Just disconnect the charger and hard reboot and you would have been fine like I said, but oh well.
amkulcsar said:
SOLVED
wait till screen get of install drivers correctly then press volume keys (+ and -) and connect to pc, in device manager appear at ports as qualcom... and open msmdownload tool and press start
Click to expand...
Click to collapse
Did you manage to get rid off the corrupted screen message doing this?
That's a standard message if you've unlocked your bootloader. It doesn't signify corruption or an actual issue. You won't get rid of it without locking your bootloader.
Hello everyone, I unlocked my bootloader, but unfortunately I made an error when unlocking it but flashing it. so that he writes me when starting qualcom crashdump mode. and I don't know how to get out of it. also where I get the original onplus6 t software. and i work with linux via terminal. who can help me with this? on the one hand, where can I get the original os9 andriod software? and the second question is how I get the whole thing back on my cell phone and that it comes out of this warning from the grass dump
Hello. Please look on XDA for MSM tool for your device (enchilada or fajita depending on 6 or 6t). It will reinstall OOS back on your phone and relock the bootloader. There are a few videos on YouTube that will guide you through the process. It's a (short) but stressful process, but it does really work.
carrabelloy said:
Hello everyone, I unlocked my bootloader, but unfortunately I made an error when unlocking it but flashing it. so that he writes me when starting qualcom crashdump mode. and I don't know how to get out of it. also where I get the original onplus6 t software. and i work with linux via terminal. who can help me with this? on the one hand, where can I get the original os9 andriod software? and the second question is how I get the whole thing back on my cell phone and that it comes out of this warning from the grass dump
Click to expand...
Click to collapse
If your original plan was to get custom firmware don't bother with msm tool and getting stock, it's unnecessary. Twrp can be booted from fastboot if your bootloader is unlocked and you can do anything you need to do from there.
carrabelloy said:
Hello everyone, I unlocked my bootloader, but unfortunately I made an error when unlocking it but flashing it. so that he writes me when starting qualcom crashdump mode. and I don't know how to get out of it. also where I get the original onplus6 t software. and i work with linux via terminal. who can help me with this? on the one hand, where can I get the original os9 andriod software? and the second question is how I get the whole thing back on my cell phone and that it comes out of this warning from the grass dump
Click to expand...
Click to collapse
I'm in the same boat. Have you found any solution yet? I also use linux.
Brettroth said:
If your original plan was to get custom firmware don't bother with msm tool and getting stock, it's unnecessary. Twrp can be booted from fastboot if your bootloader is unlocked and you can do anything you need to do from there.
Click to expand...
Click to collapse
This was my plan and I soon realized I was not ready. I have unlocked the phone and the bootloader but I'm stuck, not able to get twrp to flash. Here's my error message:
[email protected]:/home/chad/Downloads# fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (32628 KB)...
OKAY [ 0.973s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 0.975s
[email protected]:/home/chad/Downloads#
ce_lloyd said:
This was my plan and I soon realized I was not ready. I have unlocked the phone and the bootloader but I'm stuck, not able to get twrp to flash. Here's my error message:
[email protected]:/home/chad/Downloads# fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (32628 KB)...
OKAY [ 0.973s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 0.975s
[email protected]:/home/chad/Downloads#
Click to expand...
Click to collapse
Should be fastboot boot (path and filename of twrp.img) once it boots then you can flash twrp from within.
I have done that as well. It appears to work, but then I get QUALCOM CrashDump Mode Attempted to kill init! wxitcode=0x0000000b complete..and..exit
This is a T-Mobile branded phone, does that matter or change anything?
ce_lloyd said:
I have done that as well. It appears to work, but then I get QUALCOM CrashDump Mode Attempted to kill init! wxitcode=0x0000000b complete..and..exit
This is a T-Mobile branded phone, does that matter or change anything?
Click to expand...
Click to collapse
If you are on a11 you have to use the twrp.img that is posted on the cross development thread that works for opt6 and 6t. TWRP-3.6.0_11-OP6xT.img