Database Users

[Q] Nexus 4 Bootloop Troubles!!

There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.

saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
It would have saved you a lot of problems of you had of done it manually, without a toolkit
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using Tapatalk

Same problem !
saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
---------- Post added at 01:19 PM ---------- Previous post was at 01:02 PM ----------
priyab said:
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
Click to expand...
Click to collapse
Hey the flash-all.bat worked !!!! .. I just waited for like 15 mins after the flash-all.bat was done and viola! its back

This is great find
Those who face this issue can go to safe mode and backup their data while on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.

Nexus 7 2012 Retrieve data without USB debugging, Bootloop. Solved !!

Hi hope I have come to the right place for help. My Nexus 7 16GB 2012 wifi is freezing after the google logo during the boot animation of the spinning circles and stays like this. I have done some reading and I can get into recovery mode and would like to retrieve pictures/personal data but I have not enabled USB debugging, have a stock rom kitkat, but not sure which version, and have a locked bootloader, not rooted. Is it possable to still get the data off of the device. If someone could point me in the right direction it would be much appreciated.
Thanks in advance for a response
Sent from my GT-I9100 using XDA Free mobile app

alscott51 said:
High hope I have come to the right place for help. My daughters Nexus 7 16GB 2012 wifi is freezing after the google logo when booting at the spinning circles and stays like this. I have done some reading and I can get into recovery mode and would like to retrieve pictures/personal data but I have not enabled USB debugging, have a stock rom kit kat, but not sure which version, and have a locked bootloader, and not rooted. Is it possable to still get the data off of the device. If someone could point me in the right direction it would be much appreciated.
Thanks in advance for a response
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Use adb pull command

Ok Im not familiar with this programme but have read a bit about it. I will try and venture into this alien world of abd and see what happens.
Sent from my GT-I9100 using XDA Free mobile app

Installed Minimal ADB and Fastoot, connected the Nexus installed the ADB driver from Asus in device manager. Booted into the bootloader and when I used "Fastboot devices" I can see my devices seial number. When I try "ADB devices" nothing is seen. I have read I need USB debugging selected and the device booted to use ADB, both of which I can not do as I am stuck in a boot loop.
Sent from my GT-I9100 using XDA Free mobile app

You can't use adb in fastboot mode. It seems possible to pull files with fastboot, but it isn't fun.
Maybe you can flash something via fastboot to make it boot again? That would be the best way imho.

alscott51 said:
Installed Minimal ADB and Fastoot, connected the Nexus installed the ADB driver from Asus in device manager. Booted into the bootloader and when I used "Fastboot devices" I can see my devices seial number. When I try "ADB devices" nothing is seen. I have read I need USB debugging selected and the device booted to use ADB, both of which I can not do as I am stuck in a boot loop.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Go to recovery and try adb commands. In bootloader you can use only fastboot commands.

Ok I booted to the bootloader, from here selected recovery where the little Android is laying on its back. Now device manager showed nothing connected. Used the power + volume-up combo to get to the four recovery options, still nothing in device manager. Selected side load adb option and bingo welcome sound of device being connected. Windows didn't find a driver so downloaded adb driver from Asus but device manager refused to use it. Did some reading and downloaded Koush's universal driver and now device manager showed device connected and driver installed. The ADB devices command now shows the Nexus info. Now to learn the pull command. ....
Sent from my GT-I9100 using XDA Free mobile app

Done lots if reading on this and think I am beat. From what I have read the with the Nexus 7 in its current state (stock, locked bootloader, unrooted, no usb debugging) the sdcard is not reachable through the stock recovery sideload option in any way. I had a ray of hope from the above link to pull files via fastboot but I have read the thread and it seems the person says it was misleading information that they posted. I followed information in another thread and tried extracting boot, recovery and system files from a nexus factory image and flash them via fastboot but it fails stating the bootloader is locked. If I unlock the bootloader I will lose the sdcard data I want, as I will have to perform a factory reset. So as suggested I could install a CWM/TWRP recovery, but to do this via fastboot I need to unlock the bootloader......
I am thankful for people taking the time to help and for all suggestion posted but unfortunately I can not find a fix. I would be sooo grateful if someone could prove my finding wrong....
Off to do some reading about mounting the sdcard via adb shell but don't think this will work via stock recovery
Sent from my GT-I9100 using XDA Free mobile app

Install and configure any ftp/sftp/ssh server from Google play and download data wireless.

jkkk88 said:
Install and configure any ftp/sftp/ssh server from Google play and download data wireless.
Click to expand...
Click to collapse
Can't get the nexus to boot up, just bootloader and recovery accessible so don't think I'll be able to do this.
Sent from my GT-I9100 using XDA Free mobile app

Fixed it and saved all data.
Sent from my GT-I9100 using XDA Free mobile app

Sideload fix
Managed to fix this without losing anything (sdcard, docs, pictures, apps, setting etc). Took a while mostly due to lack of understanding of fastboot and ADB sideload from the recovery options.
Lots of posts advising to boot into the bootloader and use adb and fastboot. Everything I read to do with using fastboot commands via the nexus bootloader (insatalling boot/system/recovery etc) involved having an unlocked bootloader or having to unlock it as in my situation. This of course involves a factory reset of the Nexus resulting in a loss of the data that I was trying to retrieve, so i ruled this option out.
As suggested I should try the ADB pull command, but because I had not previosly enabled the USB debugging option via the setting menu everything I read said this was not an option. Read in one forum post something like "As you have not enabled USB debugging ADB is dead to you, just flash a factory image via recovery".... and lose all your data... this is not what I wanted to hear so I abandoned this option aswell.
Then I discovered sideloading. With this you can manually install an OTA update (the ones that pop up in your notification window saying something like "System update available") via the Nexus recovery option "apply update from adb". This does not invlove wiping any data , apps etc as it would just install the differences between what you are currently running eg. 4.4.2 and the updated android you want to go to eg 4.4.3. This is different to flashing a full factory image via fastboot were everything would be erased/formatted and an entirely new install would be flashed. Of course... simple when you know what the option is for and what you are doing. Of course I had had no clue what sideloading was all about.
So with my new knowledge I downloaded an OTA update from here:
http://forum.xda-developers.com/showthread.php?t=1745781&highlight=4+23
but wasnt sure what version of KitKat was running prior to the bootloop. I knew it was somewhere around 4.4.2.. so took a chance and tried KTU48L from KOT49H (4.4.3 from 4.4.2) and copied it to the Minimal ADB folder.
I booted the Nexus to the recovery mode and selected "apply update from adb". The tablet then conected to the PC (windows) as shown by Device manager. (I used Koush's universal ADB driver as windows failed to find anything of use). https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I opened Minimal ADB downloaded from here
http://forum.xda-developers.com/showthread.php?t=2317790
and typed "adb devices" which showed the Nexus was connected.
I then typed "adb sideload nexus OTA file name.zip"
Lots of sending files messages appeared in the adb window the Nexus disconnected from the PC and showed this...
Finding update package...
Opening update package...
Verifying update package...
Insatlling update...
Verifying current system...
Removing unneeded files...
Patching system files...
Patching boot image....
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions..
Patching remaining system files...
script succeeded: result was [/system]
Install fromADB complete.
All looked good so I rebooted the Nexus but I was still stuck in a bootloop at the four spinning circles. I tried clearing the cache from the recovery menu several times powering it down and leaving it to boot but after half an hour accepted failure.
So I tried downloading KTU84P from KTU84L (4.4.4 from 4.4.3) and repeated the procedure. this time not as much files seemed to be sent to the Nexus, I guess this was just a small update. Again it showed "script succeeded" but still failed to get past the spinning circles of the boot animation.
Thinking I was defeated again I was going to give up but tried downloading LRX21P from KTU84P (5.0 from 4.4.4). This time when I sideloaded a mass of files were sent to the Nexus much much more then the other two updates, obviously KitKat 4.4.4 to lollipop 5.0 was a big update. Again I got the "script succeeded" but this time I got the new Lollipop boot animation and the Nexus fully booted.
I can only guess that the big update to Lollipop removed or replaced files or did something to replace the faultly part of my install that other OTA updates did not change.
Anyway I did not find any other fix that advised sideloading an OTA update to fix a bootloop, maybe I just looked in the wrong places. I tried to write this in laymans terms for non techie people in the hope that it may help someone else in the same situation who like me knows very little about android.
Thanks to the forum for the information...
Also link here with some info about half way down page on effects of usb debugging being enabled for sideloading, and near the bottom of the page a good link to a sideload pdf guide.
https://productforums.google.com/forum/#!topic/nexus/Fhl6VVb0kio

Extreme Hard Bricked Nexus 7 2012

Hello everyone! I am new to this forum and quite a lot happy to be a part of XDA:laugh:
So here is my problem...
I have a Nexus 7 2012 and I do various experiments on my tablet like hacking through softwares and installing custom roms and all but I dont do any kind of modding
I had previously installed SlimKat custom rom 4.4.4 but after sometime it gave me some errors which I wanted to eliminate and so I decided that I would flash the stock rom
I used the Nexus Root Toolkit but it did not help. It gave me unwanted errors
I mean the first 7 to 8 times I flashed the Rom it gave me no error but my nesus would was always stuck in boot loop
I tried every available method to remove the bootloop situation but now I am totally hopeless(98%)
the rest 2% hope depends to situations : Whether the developers would provide me other usefull information or I would send it to a shop
These Things I should let you know before you provide a solution:
1. I have tried flashing from both methods , i.e, the root toolkit method and through the SDK method
2. even in the root toolkit i have tried it by both softbricked condition and normal condition
3. Right now my main problem is that everytime it tries to flash the rom the cmd says some kind of failiures like No such device or address and Invalid Argument and all
4. Methods like changing the ports or using another cable, I have tried already
Thank You in Advance, brothers:good:

[Q] Bricked Nexus 4

Hello Guys,
yesterday I restarted my Nexus 4, running the cm-13.0-20160520-NIGHTLY-mako. It stuck at the bootlogo, so I tried to reflash it in the twrp 2.8.7.0 recovery. But I got the error message "E:/ unable to mount /cache".
After that I was trying to solve this issue by wiping the cache, but I got the same error message -> The phone wasn't booting
From now on I did several things to solve my problem. I don't know the exact order.
- I've downloaded the Nexus Root Toolkit from WugFresh -> Tried to use the Flash Stock + Unroot Option with Soft-Bricked/Bootloop status enabled -> I choosed the 5.1.1 Factory Image -> In the cmd window, I get in every point the same error message "Falied (remote: flash write failure) -> I get the same message when I'm trying to manually flash each part of the factory image via fastboot
- Within the Toolkit I also tried to format cache, system and Userdata, but afther this I get the same error when trying to do the step before
- I think also used the Fastboot Flash options, but I'm not sure.
- After that I attempted to flash the cm13.zip via adb-sideload in TWRP. Here is a part from the error message I get:
"(...) could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume (...)
E: Error executing updater binary in zip 'sideload/package.zip'
E: Unable to mount '/data'
- In TWRP the Internal Storage is shown with 0mb
- Currently only the bootloader is working fine and I also can get a fastboot and adb connection to the phone
-> Loading the recovery is only possible by booting a recovery image in fastboot
Can somebody tell me if it is possible to restore my Nexus 4 and how to do it?
Thank you in advance :fingers-crossed:
PS: I hope I mentioned all the important points. If some information is missing, feel free to ask me.

Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?

audit13 said:
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Thank you for your answer.
I tried to flash the newest cm13 in TWRP and with adb Sideload. I get the same error.
Also the 4.2 Stock rom doesn't work. Same problem as with the 5.1.1 factory image.
I also switched the cable and the USB ports, but it leads to the same error messages.

Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.

From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.

audit13 said:
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
Click to expand...
Click to collapse
I get the same error message as always: Falied (remote: flash write failure)
nerotNS said:
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
Click to expand...
Click to collapse
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:

Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.

audit13 said:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
Click to expand...
Click to collapse
Unfortunately yes. After locking the bootloader via fastboot, the bootloader is marked as unlocked after rebooting.
Do I have to change the mainboard?

This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.

audit13 said:
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
Click to expand...
Click to collapse
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.

tobi.king said:
I get the same error message as always: Falied (remote: flash write failure)
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Click to expand...
Click to collapse
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
tobi.king said:
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
Click to expand...
Click to collapse
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.

nerotNS said:
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
Click to expand...
Click to collapse
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.

tobi.king said:
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
Click to expand...
Click to collapse
Awesome, glad to be of service

Help fixing bricked Nexus 7?

Hi guys, a few weeks ago I revived my old 2012 N7 and have been getting some decent use out of it, however after trying to flash one of the Nexus factory images I think I may have bricked the device. I'll get straight to the point and explain more further down.
1. The bootloader is unlocked
2. The tablet boots into this screen - https://i.imgur.com/nzYaXLt.jpg
3. Whenever I boot into the bootloader the screen turns off (I believe the bootloader is the main cause of this issue)
4. Booting to recovery does nothing
5. Fastboot works(at least detects the device - https://i.imgur.com/yUGTVjh.jpg
6. When i try to flash a nexus factory image I get this error, then the tablet boots into the bootloader with a black screen - https://i.imgur.com/Kc9adlJ.jpg
7. Attempting to flash TWRP recovery results in this error - https://i.imgur.com/SHuQZWK.jpg
8. A video of what happens when I try different things: https://youtu.be/JBBT__nGJS8
I'm pretty sure the issues happened because there was some sort of failure halfway through a factory image flash(I flashed quite a few of the factory images but was trying to find the one I liked the most), so I unplugged the tablet( I know:/ ) as the flashing wasn't progressing at all after the error.
If anyone can help it'll be massively appreciated, I hope I've made it clear on what's going on with the device, and I'll be able to further explain things if needed

Sorry to tell you, but it looks to me as if the emmc memory is broken ... bootloader cannot be flashed / updated. If you had done a backup of your binary blobs before as described here there would have been the chance to reformat and to recover from scratch. Otherwise I suppose there is nothing you can do now. Our devices are becoming ancient ...

AndDiSa said:
Sorry to tell you, but it looks to me as if the emmc memory is broken ... bootloader cannot be flashed / updated. If you had done a backup of your binary blobs before as described here there would have been the chance to reformat and to recover from scratch. Otherwise I suppose there is nothing you can do now. Our devices are becoming ancient ...
Click to expand...
Click to collapse
Cheers for the reply It does make sense that the memory is broken as the tablet often fully freezed/switched off randomly during the last 4/5 days of its life. Just a shame because it was actually working surpisingly well before the memory issues! And also, thank you for the 7.1.2 AOSP ROM, definitely the best working ROM I tried as it never seemed to have any issues with it

TheGrade said:
Hi guys, a few weeks ago I revived my old 2012 N7 and have been getting some decent use out of it, however after trying to flash one of the Nexus factory images I think I may have bricked the device. I'll get straight to the point and explain more further down.
1. The bootloader is unlocked
2. The tablet boots into this screen - https://i.imgur.com/nzYaXLt.jpg
3. Whenever I boot into the bootloader the screen turns off (I believe the bootloader is the main cause of this issue)
4. Booting to recovery does nothing
5. Fastboot works(at least detects the device - https://i.imgur.com/yUGTVjh.jpg
6. When i try to flash a nexus factory image I get this error, then the tablet boots into the bootloader with a black screen - https://i.imgur.com/Kc9adlJ.jpg
7. Attempting to flash TWRP recovery results in this error - https://i.imgur.com/SHuQZWK.jpg
8. A video of what happens when I try different things: https://youtu.be/JBBT__nGJS8
I'm pretty sure the issues happened because there was some sort of failure halfway through a factory image flash(I flashed quite a few of the factory images but was trying to find the one I liked the most), so I unplugged the tablet( I know:/ ) as the flashing wasn't progressing at all after the error.
If anyone can help it'll be massively appreciated, I hope I've made it clear on what's going on with the device, and I'll be able to further explain things if needed
Click to expand...
Click to collapse
You still might be able to recover your Nexus with my guide. Go check it out.