Database Users

I think I bricked my nexus (my fault) please help!

Hello all,
I think I may have bricked my nexus one. It is completely my fault for attempting things that I knew little about, so flame away But after the flaming, if anyone is willing to help I would be sooooo thankfull...
I successfully rooted my phone following the instructions on this page: (all links edited with a double asterisk as I don't believe I can post links)
h**p://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Then successfully installed cyanogenmod (which is awesome!) following this page:
h**p://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
All was well, I even got the modaco desire rom up and running, and was happily switching back and forth using the recovery screen. I had nand backups for specific setups, etc.
Then I decided it would be good to know how to go back to stock, and found this page:
h**p://**w.androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
I followed the instructions to the letter (I think) except for erasing userdata (it said "failed: remote not allowed"). I thought that things would be ok, since I'd recently wiped, so I followed the page till the end.
The phone rebooted, and I got the original nexus boot animation - but it's in an endless loop! What's worse, it that now when I try to go to the bootloader or recovery mode, I get the exclamation triangle with the little android.
Is there any way through a command prompt (or other method) that I can fix this? I tried to re-flash the RA recovery image through the command prompt, but the response was, "waiting for device."
ANYTHING that anyone can suggest to help, I would be so thankful! I've been loving the nexus, and hate to think that I crippled it
Thanks in advance,
Randy

I doubt its bricked.
Noticed you didnt mention that fast boot doesnt work? (power button+trackball) try it.
Once you get to fastboot you can flash any ROM back. (fastboot flash **** commands from a command shell)

Did you ever perform a Nand Backup from Recovery?

It's not bricked, the only way to brick is to interrupt power when flashing a Radio image

Connect phone to PC. Open command prompt.
adb reboot recovery
Wipe, reflash.

So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One

nexus5894 said:
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
Click to expand...
Click to collapse
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404

Paul22000 said:
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Click to expand...
Click to collapse
............................

It worked!!!!!
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
​
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!

Randy Malkoski said:
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
​
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Click to expand...
Click to collapse
Glad to hear it. You learn the most by trial and error.

I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....

revonomics said:
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
Click to expand...
Click to collapse
Tell me what i need to download again and how to go about it...i really need my phone working again ((((

[Q] stuck at shut down screen after interrupting update

tl;dr: Interrupted update. cant do jack. tried acer tech support. failed
I grew bored with waiting the two minutes for my tablet to install the new update. so i stood up and hit the power button to put it to sleep like a boss. then i cam back later, the lock screen was unresponsive
i figured out be double tapping the pwr button i was able to unlock the tablet to see the powering down screen (see attachment). I can get to the setting menu, but evrytime i try to mess around in it, the window closes itself.
an interesting note is that the time is wrong, and the battery suddenly went from 100% to 15%
I called acer tech support, and with ther guidance...
pressed the reset button to no effect
powered on holding the pwr & vol- buttons down to get an error (see attachment). then the tablet turns off.
Ive dled some "update.zip" files i found online that are supposedly used to unbrick the tab... but i just got the same error picture(see attachment)
one other thing i tried was to hold the power and vol+ buttons. this cleared a chache, but had no other effect.
I am a noob at droid, but not to tech. i would like to avoid perma bricking, and im unsure about mailing this in. waiting is gay. I would like to restore it to factory settings w/o rooting it etc. as ive never done that before. but im not opposed to installing a CFW if it somes to that...
Im looking for ideas guys here guys. wtf is wrong with this thing?

Haha
Lmao "hit the power button to put it to sleep like a boss", funny ****.
Can't help you though sorry

ive been around he web, and have seen this exact series of symptoms happen to a handful of other guys... i haven figured out a solution yet, and it is looking more and more like ill be sending it in via warranty
my best guess at this point is i have corrupted a crucial system file. as to why i can do jack in the factorys recovery mode... idk. but then again, idk what the factorys recovery mode should look like or how it would function. youtube only shows CWR... which i dont have
if i believed i could anything reasonably withing my abilities, i would... but voiding the warranty on a long shot seems dumb.
still ANY ideas would be great

I too faced exactly the same problem today.. Dunno why this is happening... I am too worried now... Kindly post the solution as you find them...
Am sure calling tech-support is just waste of time..
Thanks in advance..

IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.

npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??

stuck on same screen also!
My friend and i who both purchased this Acer Iconia tab are both having the same problem. We both received a message on the tablets to do the update. We both got stuck and have gone thru tech line and there is no remedy. She was able to return hers within the 15 day period; I on the other hand am a week over that so have to mail it to Acer for repair. I'm thinking this is more than a cooincidence and there is a problem more spread... Acer would neither verify or confirm....

buntzmehta said:
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??
Click to expand...
Click to collapse
He said the root of his SDCARD. You can take out the sdcard and put it in a sd cardreader on a computer and copy the file to it then put it back in the tablet. The file worked for him so it might be worth trying. Just have patience while it is loading as some of these updates take a while to load and sometimes you may not see anything happening but it is. The more patches and roms you load on Android the more you'll learn to just leave it alone and let the updates finish. Its pretty rare for updates to be messed up. Its usually people getting anxious and clicking on stuff.
Good luck
Sent from my A501 using Tapatalk

still stuck on shutdown screen any updates?
Anyone had any luck with a fix? If not --sending it to Acer for warranty repair after the hurricane hits..Sure hope this isn't a wide spreasd Acer issue do to the new download. Wish I could just return the thing all together. Worked well while I had it a whole 3 weeks...... Thanks in advance for any information.

npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
Thanks a lot dear npena.. you are simply great.. i was very anxious initially to try your method as no other member here who face the same problem thanked or recommended your suggestion...
I tried it and it worked... I am really very thankful to you...
Cheers..
you are my hero indeed.. thank once again..
BuntZ

Friends, who face this problem you must try it... it just takes few mins b4 you can get your acer tab to work again beautifully without loosing any settings or installed apps... they remain intact...

Yay!
Glad you got it running again - had a similar problem when doing a ota update myself, was so worried I bricked the tab, went thru about 7 update.zip files until I found one that magically worked, letting me get back into the system and flash the correct rom for my region

hi! i have the same problem with my a500. I write a guide to solve this problem. Problem in firmware. here is the gude http://forum.xda-developers.com/showthread.php?t=1572622

[Q] Nexus 7 Bootloop

Hi! I have Nexus 7 and I've used it for 4 months, it's on warranty. It started to lag couple of days and I rebooted it sometimes, but on the one reboot it didn't start Android and stucked on X logo, after another reboot it started a bootloop from X logo to Google logo on and on. After another reboot it stucks only on Google screen. I've tried to wipe data and cache partition, but it also stucks. I also tried Nexus 7 Toolkit, but it gets an error on unlock bootloader. I also tried to do it via Windows' cmd.exe with fastboot oem unlock, the same problem. I can't find any working method. Please, help.

You can use the toolkit to revert back to set stock rom. Download the stock .img from the toolkit and perform the flash. Make sure you boot to the bootloader to do this.
Entering the command fastboot oem unlock on a unlocked device will not do anything if the bootloader is already unlocked.
Sent from my Nexus 4 using Tapatalk 2

scream4cheese said:
You can use the toolkit to revert back to set stock rom. Download the stock .img from the toolkit and perform the flash. Make sure you boot to the bootloader to do this.
Entering the command fastboot oem unlock on a unlocked device will not do anything if the bootloader is already unlocked.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I'm having the EXACT same problem. Also had my N7 for about 4 mos. I'm going to try the above suggestion also. Please post your results and I'll do the same.
---------- Post added at 10:46 PM ---------- Previous post was at 10:42 PM ----------
scream4cheese said:
You can use the toolkit to revert back to set stock rom. Download the stock .img from the toolkit and perform the flash. Make sure you boot to the bootloader to do this.
Entering the command fastboot oem unlock on a unlocked device will not do anything if the bootloader is already unlocked.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
If I'm already unlocked (not rooted), what steps should I follow? I'm new to all this and, although I've rooted a phone once before, I barely remember what I did back then. I don't even know what you mean by "perform the flash." Can you provide some more specific directions? I have the toolkit downloaded. Thanks!
---------- Post added at 11:34 PM ---------- Previous post was at 10:46 PM ----------
Ok - figuring this out slowly. Can someone tell me where in my folders I can find my bootloader file?

ctychick said:
I'm having the EXACT same problem. Also had my N7 for about 4 mos. I'm going to try the above suggestion also. Please post your results and I'll do the same.
---------- Post added at 10:46 PM ---------- Previous post was at 10:42 PM ----------
If I'm already unlocked (not rooted), what steps should I follow? I'm new to all this and, although I've rooted a phone once before, I barely remember what I did back then. I don't even know what you mean by "perform the flash." Can you provide some more specific directions? I have the toolkit downloaded. Thanks!
---------- Post added at 11:34 PM ---------- Previous post was at 10:46 PM ----------
Ok - figuring this out slowly. Can someone tell me where in my folders I can find my bootloader file?
Click to expand...
Click to collapse
You can't find the bootloader file. It's embedded within the system. Unless you have the flashable zip then you can use that. Why do you need it anyways?

ten char .

Bad block on nand flash
Sent from my ST18i using xda app-developers app

Hi mate*
Dunno if you got things sorted but I had the same problem last week. I'd let the unit run flat and stay flat for a coupla days and bootloop is the price I paid. So, I call Asus who inform me that it's under warranty and to send it in for repair. Fair dos to them that's good service but I don't wanna be without my Nexus for 2 weeks so I have another play with it having previously had no joy resetting it using power and vol up/down etc.*
I'd managed to get some charge into it by waiting for the bootloop to turn it on and then manually turning it off. Not sure how quickly yours restarts but I had lockscreen for 10 seconds or so before restarting the cycle. That said it wasn't long enough to reset to factory settings but it was long enough to turn off wifi. Dunno why I tried this, sheer desperation probably but after a restart with wifi off and a full battery I was able to access my stuff and back it up to pc.*
I then was able to perform a factory reset and set the device up again, including wifi and apps. Since then it's been good as gold (but I won't let it drop below 20% charge!) but as there's only 4 months of warranty left Asus are gonna let me send it in to have a new motherboard anyway - might as well as its been wiped anyhow. The last thing I want if for it to [email protected]#k up a week after the warranty's ran out.*
I hope this helps you or other searching for a fix bud, let us know *

Lolpoppa said:
Hi mate*
Dunno if you got things sorted but I had the same problem last week. I'd let the unit run flat and stay flat for a coupla days and bootloop is the price I paid. So, I call Asus who inform me that it's under warranty and to send it in for repair. Fair dos to them that's good service but I don't wanna be without my Nexus for 2 weeks so I have another play with it having previously had no joy resetting it using power and vol up/down etc.*
I'd managed to get some charge into it by waiting for the bootloop to turn it on and then manually turning it off. Not sure how quickly yours restarts but I had lockscreen for 10 seconds or so before restarting the cycle. That said it wasn't long enough to reset to factory settings but it was long enough to turn off wifi. Dunno why I tried this, sheer desperation probably but after a restart with wifi off and a full battery I was able to access my stuff and back it up to pc.*
I then was able to perform a factory reset and set the device up again, including wifi and apps. Since then it's been good as gold (but I won't let it drop below 20% charge!) but as there's only 4 months of warranty left Asus are gonna let me send it in to have a new motherboard anyway - might as well as its been wiped anyhow. The last thing I want if for it to [email protected]#k up a week after the warranty's ran out.*
I hope this helps you or other searching for a fix bud, let us know *
Click to expand...
Click to collapse
I tries this but it doesnt seem to work for me, i had the same issue as you and now it seems as though it is bricked :/ i tried doing the steps you mentioned but it didnt work for me. i get to the home screen for about 10 secs till it restarts. i want to save my music/pictures and i dont know what to do (i never enabled developer options either) any ideas?

Possible way to save any bricked Nexus device!

Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!

That explains why the OTA for the N preview was the same size as the image, and why after upgrading to March security release I didn't have to download a different OTA to get to N

So is this usable in all situations? If yes then should download it & store it safely

Interesting thing, can this update bypass factory reset protection?

iluvatrix said:
So is this usable in all situations? If yes then should download it & store it safely
Click to expand...
Click to collapse
I would assume this could be used in any situation where you have a paper wait. So say you're on marshmallow build and somehow things go wrong ,bootloader locked USB debugging not check ,with this ota you can still sideload but it will be an N build which is fine at least you'll have a working device that now you can revert back to your original build. So I'm keeping this as well. I really don't need to but its nice to have just in case. I normally keep my bootloader unlocked at all times anyways just in case things go haywire... Someone correct me if I'm not correct please. Have a nice weekend all?
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Good question..

Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Most likely not, because normally when receiving an OTA all of that remains intact but, I think it's worth a test.

This will NOT bypass factory reset protection. This is just an update.zip that is a signed "FULL" image rather than a "DIFFERENCE" image. That means that it just doesn't need to perform the verification step before proceeding to install the update.
There is also another "problem" with relying on these as the ultimate unbrick files, which is that if you happen to install some official build that is NEWER than N-pre1, then the recovery will refuse to "downgrade". So while it may be useful for now while nobody is running anything newer than N-pre1, it isn't a permanent solution.

This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish

Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
doitright said:
This will NOT bypass factory reset protection.
Click to expand...
Click to collapse
The first N preview apparently has a bug that will allow a user to bypass FRP (if they are on the first N preview)
http://www.androidpolice.com/2016/0...ory-reset-protection-workaround-on-android-n/

flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
I'm glad to hear it worked for you

Works for me boss
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:

mowgli762 said:
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:
Click to expand...
Click to collapse
Why didn't you just flash the system.IMG if the bootloader was unlocked?

holeindalip said:
Why didn't you just flash the system.IMG if the bootloader was unlocked?
Click to expand...
Click to collapse
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).

mowgli762 said:
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).
Click to expand...
Click to collapse
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.

holeindalip said:
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.
Click to expand...
Click to collapse
Good - case specific information needs no apology - Diplomacy has never been alluded to as being in my skill set (too much glass in my house to throw stones).
Thanks for your interest and info.

TriguyRN said:
Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!
Click to expand...
Click to collapse
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .

atef79 said:
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .
Click to expand...
Click to collapse
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face

TriguyRN said:
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face
Click to expand...
Click to collapse
I already shared your post in my topic that I made in the Nexus 6p section to help all who bricked there devices with locked bootloader, and thx again .
This is my topic link
http://forum.xda-developers.com/nexus-6p/help/command-t3308390/post66086939#post66086939

just want to ask would this method work if the phone has not been authorized to a specific PC ?

iluvatrix said:
just want to ask would this method work if the phone has not been authorized to a specific PC ?
Click to expand...
Click to collapse
I'm not sure what you mean by "if the phone has not been authorized to a specific PC". As far as I am aware Android phones are not authorized to a PC, that is an Apple thing...

No Factory Reset Option

My daughter managed to change the pattern on her phone while on vacation and she can't remember what the new one is. I have gotten into the boot menu in attempts to completely reset the phone, however, there is no option for factory reset. Can somebody please tell me how to wipe this phone so she can use it again.

I'm just gonna ask for someone who knows better. I guess you'd be better off leaving the bootloader locked so you can have the warranty, so would it be possible to flash TWRP through fastboot, then delete lockscreen database stuff with it, then flash stock recovery? All without unlocking the phone?
Also could you tell us the model? Is it an A2017G, A2017, or A2017U?
If the phone hasn't got fastboot, you would have to use MiFlash to flash A2017*_FASTBOOT_UNLOCK_EDL then get TWRP and delete the files.
---------- Post added at 10:56 PM ---------- Previous post was at 10:49 PM ----------
Also, if you do that process you could avoid resetting the phone. I'm just not sure if you can change system stuff without unlocking the bootloader. so until someone with actual knowledge shows up I'd advise you to hold on tight.

MasterDDF said:
My daughter managed to change the pattern on her phone while on vacation and she can't remember what the new one is. I have gotten into the boot menu in attempts to completely reset the phone, however, there is no option for factory reset. Can somebody please tell me how to wipe this phone so she can use it again.
Click to expand...
Click to collapse
unlock the bootloader.

Jusz go into recovery mode, shutdown the phone wait for 5 seconds than push the volume up and Power button at the same time and wait till. you are in recovery mode, than you can factory reset the phone
https://youtu.be/Rw5TMxyAGMc

nuridurdu27 said:
Jusz go into recovery mode, shutdown the phone wait for 5 seconds than push the volume up and Power button at the same time and wait till. you are in recovery mode, than you can
Click to expand...
Click to collapse
If only it was that simple. That was the first thing I did after 30 failed attempts for her figuring out her pattern. However there isn't am option to reset to factory. I've never seen a phone not have the option before

Choose an username... said:
I'm just gonna ask for someone who knows better. I guess you'd be better off leaving the bootloader locked so you can have the warranty, so would it be possible to flash TWRP through fastboot, then delete lockscreen database stuff with it, then flash stock recovery? All without unlocking the phone?
Also could you tell us the model? Is it an A2017G, A2017, or A2017U?
If the phone hasn't got fastboot, you would have to use MiFlash to flash A2017*_FASTBOOT_UNLOCK_EDL then get TWRP and delete the files.
---------- Post added at 10:56 PM ---------- Previous post was at 10:49 PM ----------
Also, if you do that process you could avoid resetting the phone. I'm just not sure if you can change system stuff without unlocking the bootloader. so until someone with actual knowledge shows up I'd advise you to hold on tight.
Click to expand...
Click to collapse
Slightly embarrassing realizing I even had the model of phone wrong. Not listening to my wife anymore. It is an axon 7 mini. Model B2017G. If there is a moderator that would like to relocate the post that would be fine

lafester said:
unlock the bootloader.
Click to expand...
Click to collapse
Is there a walkthrough on unlocking the bootloader? I haven't messed with getting that done before.

MasterDDF said:
Model B2017G.
Click to expand...
Click to collapse
Oops... Sorry man, but there's no proven way(or probably just no way) of doing this kind of stuff on the Axon 7 mini. For some reason there are zero developers for that phone
The only other thing I can think of is to put a bunch of random patterns, then wait, then do that again until the phone decides to leave you put her Google account and password. I hope that works...
Or one other thing, but I'm almost sure this won't work: if the phone has Nougat, which I doubt, you can look over at zte support if there's a Marshmallow system zip. Download it and extract the zip that's inside the zip, then throw it inside an SD card, put it in the phone, then go to the recovery and select to flash update, select it. It should wipe everything to oblivion.
---------- Post added at 01:42 AM ---------- Previous post was at 01:28 AM ----------
MasterDDF said:
Is there a walkthrough on unlocking the bootloader? I haven't messed with getting that done before.
Click to expand...
Click to collapse
Wait - even better, there seems to be a factory reset option. Look at this:
https://forum.xda-developers.com/axon-7-mini/help/b2017g-forgot-password-factory-data-t3596774

Choose an username... said:
[/COLOR]
Wait - even better, there seems to be a factory reset option. Look at this:
https://forum.xda-developers.com/axon-7-mini/help/b2017g-forgot-password-factory-data-t3596774
Click to expand...
Click to collapse
Was worth a shot. But I don't even get a robot. Any other device I've owned I get the robot laying on the ground.

MasterDDF said:
Was worth a shot. But I don't even get a robot. Any other device I've owned I get the robot laying on the ground.
Click to expand...
Click to collapse
I don't know. If that phone hasn't got a recovery then ZTE is weirder than I thought. Try power + volume up or power + volume down, it has to do something...

Hello, MasterDDF. I'm afraid that the last maintenance update removed the factory reset option from the Android Recovery Menu, however, we've confirmed that an update will be released soon for the Axon 7 Mini device. Since you are unable to unlock the device, we're happy to repair or replace the device utilizing your warranty. If you'd like additional information or, have any questions or concerns, please feel free to contact our Support team at 1-800-617-5065 or, via our social media on Facebook ZTEUSA, and Twitter ZTE_USA.
ZTEUSA Support