Database Users

Updating to 4.3 Image with fastboot failed.

Hi guys
I was trying to update to 4.3 using fastboot and after finishing i got stuck with the google on the screen. So i went on to try it again, this time installing each .img in the zip manually. While i was sending the System.img the usb connection broke and i tried again to no avail. So i was like lets do this again. So i went i started all over again with erasing boot, now the terminal is stuck on that and not going forward. Im out of options. Really need help, im helpless here. Please.
Thank You

Cantacid said:
Hi guys
I was trying to update to 4.3 using fastboot and after finishing i got stuck with the google on the screen. So i went on to try it again, this time installing each .img in the zip manually. While i was sending the System.img the usb connection broke and i tried again to no avail. So i was like lets do this again. So i went i started all over again with erasing boot, now the terminal is stuck on that and not going forward. Im out of options. Really need help, im helpless here. Please.
Thank You
Click to expand...
Click to collapse
Is that a Mac? There is another thread with a guy having issues flashing system.img using a Mac. Not sure if he was able to fix it or not. He was able to flash all the other images just not system.img.
For reference from Efrant's thread on flashing image files if your phone hangs during first boot try this:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2010312
I had the boot issue when I first flashed the images and just formatting the cache fixed it for me. I later had to do a factory reset as the phone was reporting the wrong storage size, 8 GB instead of 16 GB and the reset fixed it.
Here is the other guys Mac thread, not sure it will help you or not.
http://forum.xda-developers.com/showthread.php?t=2377647

kzoodroid said:
Is that a Mac? There is another thread with a guy having issues flashing system.img using a Mac. Not sure if he was able to fix it or not. He was able to flash all the other images just not system.img.
For reference from Efrant's thread on flashing image files if your phone hangs during first boot try this:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2010312
I had the boot issue when I first flashed the images and just formatting the cache fixed it for me. I later had to do a factory reset as the phone was reporting the wrong storage size, 8 GB instead of 16 GB and the reset fixed it.
Here is the other guys Mac thread, not sure it will help you or not.
http://forum.xda-developers.com/showthread.php?t=2377647
Click to expand...
Click to collapse
And the thing about cleaning caches is locking and unlocking bootloader does the same. Tried, i cant install recovery and system .img for some reason.
Thank you for the quick reply, seems the like the guy is having the same issue. Will post it there as well.
The issue is to fastboot the system.img

Cantacid said:
And the thing about cleaning caches is locking and unlocking bootloader does the same. Tried, i cant install recovery and system .img for some reason.
Thank you for the quick reply, seems the like the guy is having the same issue. Will post it there as well.
The issue is to fastboot the system.img
Click to expand...
Click to collapse
I see you are in the other thread too but I will post this here also.
According to this thread when using a Mac you don't flash the system or kernel (boot) images.
http://forum.xda-developers.com/showthread.php?t=2377691

kzoodroid said:
I see you are in the other thread too but I will post this here also.
According to this thread when using a Mac you don't flash the system or kernel (boot) images.
http://forum.xda-developers.com/showthread.php?t=2377691
Click to expand...
Click to collapse
Yeah you do. I just did this on my Mac for my Nexus 4 and Nexus 7 last night with absolutely no issues.
The procedure I used is as follows...
1.1) Download the factory image and ensure all .img files are extracted to the "platform-tools" folder
1.2) Boot phone into fastboot mode by powering it down then holding volume down/power at the same time until the fastboot screen appears
2) Plug the phone into the computer via USB cable
3) Open terminal and type: fastboot devices (if it recognizes your phone's serial number you are ready to move forward)
4) Reboot by typing: fastboot reboot-bootloader (I do this just to test the connection but it's not 100% necessary)
5) Flash the bootloader: fastboot flash bootloader /Users/kevin/Desktop/Android/sdk/platform-tools/bootloader.img
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio /Users/kevin/Desktop/Android/sdk/platform-tools/radio.img
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system /Users/kevin/Desktop/Android/sdk/platform-tools/system.img
10) Flash the data partition: fastboot flash userdata /Users/kevin/Desktop/Android/sdk/platform-tools/system.img (Note: this command will wipe your device)
11) Flash the kernel/ramdisk: fastboot flash boot /Users/kevin/Desktop/Android/sdk/platform-tools/boot.img
12) Flash the recovery partition: fastboot flash recovery /Users/kevin/Desktop/Android/sdk/platform-tools/recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== (the second option seems to work better for most people and it's what I used)
14) Reboot: fastboot reboot
After completing step 14 your phone should reboot to the initial setup screen. If you follow those steps vigorously you won't have any issues. If it doesn't work you did something wrong and should start over. If it doesn't work on a second try then I'd re-download the system image from HERE again just to be sure the .img files you are ultimately trying to use aren't corrupt somehow.

sn0warmy said:
Yeah you do. I just did this on my Mac for my Nexus 4 and Nexus 7 last night with absolutely no issues.
The procedure I used is as follows...
1.1) Download the factory image and ensure all .img files are extracted to the "platform-tools" folder
1.2) Boot phone into fastboot mode by powering it down then holding volume down/power at the same time until the fastboot screen appears
2) Plug the phone into the computer via USB cable
3) Open terminal and type: fastboot devices (if it recognizes your phone's serial number you are ready to move forward)
4) Reboot by typing: fastboot reboot-bootloader (I do this just to test the connection but it's not 100% necessary)
5) Flash the bootloader: fastboot flash bootloader /Users/kevin/Desktop/Android/sdk/platform-tools/bootloader.img
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio /Users/kevin/Desktop/Android/sdk/platform-tools/radio.img
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system /Users/kevin/Desktop/Android/sdk/platform-tools/system.img
10) Flash the data partition: fastboot flash userdata /Users/kevin/Desktop/Android/sdk/platform-tools/system.img (Note: this command will wipe your device)
11) Flash the kernel/ramdisk: fastboot flash boot /Users/kevin/Desktop/Android/sdk/platform-tools/boot.img
12) Flash the recovery partition: fastboot flash recovery /Users/kevin/Desktop/Android/sdk/platform-tools/recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== (the second option seems to work better for most people and it's what I used)
14) Reboot: fastboot reboot
After completing step 14 your phone should reboot to the initial setup screen. If you follow those steps vigorously you won't have any issues. If it doesn't work you did something wrong and should start over. If it doesn't work on a second try then I'd re-download the system image from HERE again just to be sure the .img files you are ultimately trying to use aren't corrupt somehow.
Click to expand...
Click to collapse
In the other walk through flash system image and boot image is replaced by "./fastboot update image-occam-jwr66v.zip". This could help those who are having problems flashing the system image file. I've also seen this method used for windows in that all you flash is the bootloader image then the update image and your done.

-w is to clear the userdata, but the problem is its not pushing the system.img on the phone! Tried without -w and yet the same issue! I have restored my previous rom and madea nandroid for 4.2.2 stock! Might go back to that and try updating ota! Can somebody confirm if i have to lock bootloader and lose root to get an update!
I have no clue why the same steps work for 4.2.2 but not 4.3 image files!
Sent from my Nexus 4 using Tapatalk 4 Beta

One thing I don't think anyone has mentioned (which may actually be the core solution to this problem for everyone) is that you need to update your SDK Platform from 17 to 18 and you need to install "Android Support Repository" in order for 4.3 to properly flash. To do this open terminal and paste the path to the "android" executable file found under sdk/tools. My path was:
/Users/kevin/Desktop/Android/sdk/tools/android
After pasting the appropriate path into terminal hit enter. This will open the SDK Manager. Once SDK Manager is open it will ask to update outdated drivers. One of the drivers being updated is SDK Platform. Before hitting the update button scroll down to the 'Extras' folder and check the box next to "Android Support Repository". Now hit the update button.
After doing this, reboot the computer (may or may not be necessary) and try flashing again by following the steps I provided in post #5. Let me know if that solved it.

Well, i may try that! But as if now, went to bootcamp, installed drivers and sideloaded 4.3. I may still try updating sdk, just in case i may neeed to do this again!
Where is this sdk/tools?
Sent from my Nexus 4 using Tapatalk 4 Beta

Cantacid said:
Well, i may try that! But as if now, went to bootcamp, installed drivers and sideloaded 4.3. I may still try updating sdk, just in case i may neeed to do this again!
Where is this sdk/tools?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
sdk/tools is located wherever you extracted the .zip file to. In my case I just put it all in a parent folder on the desktop called "Android".

Boot loop / blank screen

so I could use some major help! I received my new nexus yesterday and I believe i've already soft-bricked it somehow but I can't seem to recover it. I've read that you should change the APNs from the cingular ones to the new att settings. I did this, and then I rebooted phone, but somehow it got stuck in a boot loop. so i was like S%^T, and all. so like a moron I started messing around in fastboot and I unlocked the bootloader through cmd line. I found this article http://forum.xda-developers.com/showthread.php?t=2010312 which I figured was my best chance for a recovery. I also tried the Nexus Root Toolkit v1.7.1 and told it i was softbricked / bootloop scenario. I've tried loading the twrp, cwrm, stock recoveries, but evertime I try to boot to the screen is on, but blank. i dont get the android with the !..
NOTHING is working!
I think my major problem at this point is i NEED usb debugging enabled, but I cant get into android gui itself to enable this option.
Believe me ANY help is greatly appreciated and I'll but you a pizza and have it delivered to your home...:laugh:

This should be easy, just put your device on bootloader and use this tool, make sure you have the ADB and Fastboot files with it all.
https://developers.google.com/android/nexus/images#occamjwr66y
Sent from my Nexus 4 using Tapatalk 4

Done this also. I used the 4.2.2 files for Mako. Then followed the link instructions that I posted from that link.
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
At step 8 it doesn't reboot saying it failed and I have to hardboot back into bootloader from every step forward where required. Eventually I can flash all the img files and reboot phone. I'll then see and android logo with a blue rotating sphere and status bar, then reboots. it does this several times then screen goes blank.

evo_guy said:
Done this also. I used the 4.2.2 files for Mako. Then followed the link instructions that I posted from that link.
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
At step 8 it doesn't reboot saying it failed and I have to hardboot back into bootloader from every step forward where required. Eventually I can flash all the img files and reboot phone. I'll then see and android logo with a blue rotating sphere and status bar, then reboots. it does this several times then screen goes blank.
Click to expand...
Click to collapse
Well I was able to run the "flash-all" batch file with success, no errors or bootloader reboot issues. Phone rebooted again and now I'm suppose to be waiting for Dalvik Cache to rebuild. This is about 10 mins ago though, any ideas how long it takes to do this??

evo_guy said:
Well I was able to run the "flash-all" batch file with success, no errors or bootloader reboot issues. Phone rebooted again and now I'm suppose to be waiting for Dalvik Cache to rebuild. This is about 10 mins ago though, any ideas how long it takes to do this??
Click to expand...
Click to collapse
Should take around 10-15 min. If its taking more than 20 minutes i would suggest going into the bootloader, then into the stock recovery and doing a factory reset from there.

Chromium_ said:
Should take around 10-15 min. If its taking more than 20 minutes i would suggest going into the bootloader, then into the stock recovery and doing a factory reset from there.
Click to expand...
Click to collapse
well screen was blank the entire time. I did see the Google logo but NO nexus logo. i rebooted to bootloader and selected recovery and still was blank......FML

evo_guy said:
well screen was blank the entire time. I did see the Google logo but NO nexus logo. i rebooted to bootloader and selected recovery and still was blank......FML
Click to expand...
Click to collapse
Try flashing the stock images again. http://forum.xda-developers.com/showthread.php?t=2010312

Chromium_ said:
Try flashing the stock images again. http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
no different. just sits at a blank screen, i see the google with the unlocked symbol at bottom which then changes to a blank screen and sits there....
do i have to have USB Debugging enabled to accomplish any of these changes??

evo_guy said:
no different. just sits at a blank screen, i see the google with the unlocked symbol at bottom which then changes to a blank screen and sits there....
do i have to have USB Debugging enabled to accomplish any of these changes??
Click to expand...
Click to collapse
USB Debugging is just really a ADB switch for the OS.
Sent from my Nexus 4 using Tapatalk 4

Trouble flashing 5.0.0! Help needed!!!

Need help here!
My Nexus 10 was with stock 4.4.4, rooted with TWRP. I decided to flash the factory image files by removing the -w in flash-all.sh. However it ended up with being stuck with the rotating balls. After about 45 minutes, I decided to go to the fastboot mode (pwr+both volumes), then select recovery (I planned to do factory reset and clear cache). After trying to reboot into recovery mode (pwr + one volume button), it now shows an open bootloader with following message below the bootloader (the bootloader seems still unlocked):
Dowloading...
Do not turn off target!!
What does it mean? What is it exactly downloading? And what should I do? Should I lock the bootloader? Also it does not respond now if I push the volume buttons. It's not recognized on my Mac with the with the following command:
fastboot devices
I also notice the following line:
Reboot Mode Flag: NONE
Now I just booted into recovery, but it shows the bootloader with the exclamation mark! After a few minutes, it automatically switched to the never-ending rotating balls. What can I do?

When you get the Downloading...message you're in the Recovery screen. Don't worry about the message. Press vol up and power to get into the recovery menu - there you can wipe cache and system. As you're in recovery, Fastboot devices will not recognise your tablet, only adb commands.
If I was you and this didn't work, I'd just reboot into fastboot and flash the image files manually. You'll lose root, data and twrp but these can easily be gotten back through fastboot.

Hi,
In case you want help to flash Stock Firmware files. Check the Manta Help Thread .
http://forum.xda-developers.com/showthread.php?t=2670400
~Lord

Boot from SD card. EMMC memory is dead

I have the wt86047(HM2014813,HM2XTDPro) and I have dead emmc on my phone. The internal /data /system and /cache partitions are unmountable. So I decided that I try to boot from sdcard.
I have used this tutorial Dual boot to partition my sdcard and modify the recovery and the rom(Lineage 14.1) to look for the system, data and cache partitions on sdcard.
But when I try to boot up the phone is stuck at the MI logo and I see my device in fastboot. To be able to boot to my device I need in fastboot to execute fastboot boot modifiedboot.img. This is not too much convenient as I need pc to turn my phone on. I also can only boot recovery and not to get to the recovery mode. I can however flash the image to the /recovery partition. I suspect that my /boot partition is also corrupted. I tried to manualy flash boot also with no succes. Any ideas how to boot the phone without need to use fastboot?

I have the exact same issue with the same phone.
You have modified only the fstab file ?

nings008 said:
I have the exact same issue with the same phone.
You have modified only the fstab file ?
Click to expand...
Click to collapse
In boot.img yes(fstab.qcom), in TWRP the etc/recovery.fstab and in the updater script any mention of /system and /data.
The phone boots with the fastboot boot, but it is quite slow as I have quite cheap sd card in it. I would buy a better one If I would be able to boot the phone without computer.
EDIT: Camera is also not working for some reason

Try folding the fastboot ROM.
Same thing happened to me. I tried and flashed the fastboot image. It worked. This happened to me a long time ago. Don't worry about bootloader if you can see the fastboot screen with the mi man on your phone .
http://bigota.d.miui.com/V8.0.1.0.K...DG_20160805.0000.29_4.4_global_daca6227c0.tgz
This is the link for the fastboot file for Redmi 2 aka wt88047 or any other version of the Redmi 2.
Just use the following method to flash using ADB and should be successful.
Steps to Flash MIUI Fasboot ROM Without Using Mi Flash Tool {Using Command Prompt}
We would like to suggest that Please use the Official Flashing method through Mi Flash Tool if that method didn’t work for you then try this method.
Below is the overall method to Flash MIUI 8/9 Using Command Prompt. The commands use in this method are pretty common. For most of the users are familiar with this Commands.
Quick Requirments:
Download Fastboot ROM of your device.
Xiaomi USB Driver & ADB Driver of your device.
Try Mi PC Suite if above USB Driver doesn’t work for you.
Flash MIUI Fastboot ROM Using Command Prompt
1. Download the Fastboot ROM you want to flash from the above download link. Extract the Downloaded Fastboot ROM in your Windows PC.
2. Enter into Download Folder. You will see some Files & Folder out there. Again go to Images Folder.
3. Boot your device into Fastboot Mode. To do this Switch off your phone. Now, Press Power Button + Volume Down button to boot your device into Fastboot Mode.
4.In that folder “Open Command Window” by Holding Shift Button + Right Click button of the mouse. You will see Command Prompt will open there.
5.Type following Command to check whether your device is connected or not.
fastboot devices
6. Below the command, If it shows the device then you are ready to flash. Now, Execute following commands one by one to flash the whole ROM.
fastboot flash system system.img
Press Enter to Continue
fastboot flash boot boot.img
Press Enter to Continue
fastboot flash recovery recovery.img
Press Enter to Continue
fastboot flash cache cache.img
Press Enter to Continue
Want Complete erase of data? All Data will be deleted it will be like new device. Then type this following commands.
fastboot erase userdata
Press Enter to Continue
fastboot flash userdata userdata.img
Press Enter to Continue
All Flashing process in complete. Now, Type the following code & hit enter button to Reboot your device normally.
fastboot reboot
That’s it! Congratulation! You have successfully Installed Latest MIUI Fastboot ROM. Your device bootloader is locked now & You device is unrooted. Please let me know if it helped.

d2211basu said:
Same thing happened to me. I tried and flashed the fastboot image. It worked. This happened to me a long time ago. Don't worry about bootloader if you can see the fastboot screen with the mi man on your phone .
Click to expand...
Click to collapse
This won't help. This is the hardware issue. The storage chip on the motherboard is dead. You can not write anything to it. It is possible to replace that chip but it is a quite difficult operation.

tulen_kobi said:
Any ideas how to boot the phone without need to use fastboot?
Click to expand...
Click to collapse
Looking for the same.
https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171

Redmi 2 Hard Bricked or Boot Dead Repair
tulen_kobi said:
I have the wt86047(HM2014813,HM2XTDPro) and I have dead emmc on my phone. The internal /data /system and /cache partitions are unmountable. So I decided that I try to boot from sdcard.
I have used this tutorial Dual boot to partition my sdcard and modify the recovery and the rom(Lineage 14.1) to look for the system, data and cache partitions on sdcard.
But when I try to boot up the phone is stuck at the MI logo and I see my device in fastboot. To be able to boot to my device I need in fastboot to execute fastboot boot modifiedboot.img. This is not too much convenient as I need pc to turn my phone on. I also can only boot recovery and not to get to the recovery mode. I can however flash the image to the /recovery partition. I suspect that my /boot partition is also corrupted. I tried to manualy flash boot also with no succes. Any ideas how to boot the phone without need to use fastboot?
Click to expand...
Click to collapse
Follow This Link
https://globaltech2u.com/how-to-bring-a-boot-dead-or-hard-bricked-redmi-2-back-to-life

Help Wiping (or Unlocking) With a Broken Screen

The screen on my Stock unrooted & locked Nexus 6P is completely non-functional (shattered, not displaying anything, likely not responding to touch) and I'd like to wipe it before disposing of it.
I'm able to blindly navigate to the bootloader but I'm having trouble unlocking for the purposes of
Code:
fastboot erase system -w
.
Process
Boot into bootloader then issue the unlock command:
Code:
fastboot flashing unlock
Because I can't see the screen, I'm assuming pressing up or down will select 'Yes' and power will confirm it.
Either way (up+pwr or down+pwr or just pwr) the phone restarts and I let it sit for a while.
I reboot into the bootloader but the unlocked variable returns no.
I figured the closest analog would be to reflash via
Code:
fastboot -w update "image.zip"
, which will wipe userdata and cache - is that sufficient?

Don't worry....just download and install Nexus toolkit or do it manually by downloading Adb fastboot minimal <10mb size.
First, install driver for flashing firmware.
Reboot to bootloader,
Connect to pc,it will make sound if connected.
Now,put system.img to adb minial folder.
Right click and open cmd in adb minimal folder.
Type adb fastboot flash system system.img
Then,in the middle disconnect from pc.since,it will corrupt your system file.Do this for 2-3 times,that is flashing system.img and disconnecting in the middle to insure that system file have corrupted.
Then,at last flash system.img till end to complete.
Voila...you will have a factory reset phone.
I did this trick before selling my galaxy s5 broken display phone.
When buyer put display in front of me,it was factory reset.

Phylum said:
The screen on my Stock unrooted & locked Nexus 6P is completely non-functional (shattered, not displaying anything, likely not responding to touch) and I'd like to wipe it before disposing of it.
I'm able to blindly navigate to the bootloader but I'm having trouble unlocking for the purposes of
Code:
fastboot erase system -w
.
Process
Boot into bootloader then issue the unlock command:
Code:
fastboot flashing unlock
Because I can't see the screen, I'm assuming pressing up or down will select 'Yes' and power will confirm it.
Either way (up+pwr or down+pwr or just pwr) the phone restarts and I let it sit for a while.
I reboot into the bootloader but the unlocked variable returns no.
I figured the closest analog would be to reflash via
Code:
fastboot -w update "image.zip"
, which will wipe userdata and cache - is that sufficient?
Click to expand...
Click to collapse
Run a drill bit through the upper 1/4 of the screen and through the motherboard then dispose.

hawkswind1 said:
Run a drill bit through the upper 1/4 of the screen and through the motherboard then dispose.
Click to expand...
Click to collapse
Lol sounds good to me!
zameer hassan said:
Don't worry....just download and install Nexus toolkit or do it manually by downloading Adb fastboot minimal <10mb size.
First, install driver for flashing firmware.
Reboot to bootloader,
Connect to pc,it will make sound if connected.
Now,put system.img to adb minial folder.
Right click and open cmd in adb minimal folder.
Type adb fastboot flash system system.img
Then,in the middle disconnect from pc.since,it will corrupt your system file.Do this for 2-3 times,that is flashing system.img and disconnecting in the middle to insure that system file have corrupted.
Then,at last flash system.img till end to complete.
Voila...you will have a factory reset phone.
I did this trick before selling my galaxy s5 broken display phone.
When buyer put display in front of me,it was factory reset.
Click to expand...
Click to collapse
Excellent excellent excellent advice - much appreciated.

You need to have USB debugging enabled btw to unlock your phone and issue those fastboot commands.