Database Users

Full Downgrade from 2.1root (any) to 1.5 stock - FULLY WORKING

Download removed, go ahead and thank user nimdae for pointing out the wrongness of my work. I am done with Eris dev work because of people like him.
nimdae <-- that user right there.
THIS IS NOT FOR LEAK USERS SO DON'T ASK
*start rant* THIS MEANS DON'T MESSAGE ME ASKING HOW TO USE IT ON 2.1LEAK, ITS NOT CURRENTLY POSSIBLE TO DOWNGRADE FROM LEAK. PLEASE STOP SENDING ME MESSAGES ASKING HOW.*end rant*
If it bricks your phone, not my fault (it shouldn't and I hope it doesn't).
Please read and follow the directions included in this thread.
unzipme.zip md5sum: 0ed3c91d7574367d65428b3bc230f217
This is fully working, I just did a full reflash to 1.5, including the kernel, the system software, the radio firmware, recovery image and the bootloader.
This must be done from a PC with Fastboot, which comes with windows. Linux/Mac users will have to find it and compile it. You will need to have Amon's recovery image installed to use this downgrade, at the end we will overwrite his image with the stock one.
Inside unzipme.zip are three files
downgrade.zip md5sum: c440c87f1e67f4b62e05da0d255e80e9
-Do not unzip/open/alter this file
--Contains your kernel, radio firmware, and system.
recovery.img md5sum: 71a4b633bdb32de9dcdd8953fef43cdc
--stock recovery image
hboot.nb0 md5sum: 38899da4e5e002e3be22900f5f4eb6f7
--Original bootloader
Step one:
Put hboot.nb0 and recovery.img in the tools dir of your sdk.
Put downgrade.zip on the sdcard of your phone
Step two:
Turn your phone off, then turn it back on holding the power button (red) and send button (green). Once in the boot loader press volume down, then volume up to get to Amon's recovery image. Go to wipe, wipe dalvik cache, and do a factory reset (aka wipe data). Then choose flash zip from sdcard, and flash downgrade.zip. The phone will flash the kernel, and system softare, then ask you to reboot. Let it reboot so it can flash the radio, it will restart back in the recovery image. You can power down your phone now.
Once the phone says "Formatting CACHE:" wait 30seconds and your done. This is an minor error in the update-config on my part, but it is not harmful and I won't be fixing it.
At this point if your just wanted 1.5 back, you are done.
If you want the original bootloader and recovery image, (ie 100% stock) continue on.
Step three:
Plug your phone into your PC. Power your phone on using the power button (red) and send button (green). Your phone should now be sitting back at the bootloader screen and say FASTBOOT USB. Now on your PC, go to the sdk tools dir in command line. Issue this command.
Code:
fastboot flash recovery recovery.img
Let it flash, when done wait a minute (just to make sure).
Then issue this command
Code:
fastboot flash hboot hboot.nb0
Once this is done, wait a minute then pull your battery and restart your phone.
You are now back at factory stock.
Thank you ivanmmj for showing me how to do this crud, and zifnab06 for telling me the right way to flash hboot.
...
..
.
jcase

Risk of losing root permanently? I could be up to test, but I won't be home til after 5 pst. I'll hit you up on irc later to check if you're still looking for someone.

This is not the droid your looking for......

move along move along.

What are the risks / requirements?

Darn, if this was a 2.1leak to 1.5 test, I would so be your guinea pig, since I'm getting a new phone tomorrow anyway. lol

Ruh17 said:
Risk of losing root permanently? I could be up to test, but I won't be home til after 5 pst. I'll hit you up on irc later to check if you're still looking for someone.
Click to expand...
Click to collapse
no you could just root again by loading the rooted 2.1 rom

Thanks jamezelle. Good job devs. Don't know how you find the time to work your magic every day.

I have 2 eris's here. Ones an extra. Let me know..

This kind of gets me excited being on 2.1 leak atm but I guess I should not bother to get hopes up doing things while rooted is a lot easier than when not so Im guessing I am going to be stuck.

OH DANG!!!!!
i am so excited!!! if you're like 90% seure it will work i volunteer!!!
i love 2.1 but i WANT to root SO BAD

Too bad its not for 2.1 leakers huh?

Has anyone tried this? I have an extra eris sitting around running the 2.1 root. If it has not been tried i will test it on the extra one (warranty have to send it back in a few days)

morbidpete said:
Has anyone tried this? I have an extra eris sitting around running the 2.1 root. If it has not been tried i will test it on the extra one (warranty have to send it back in a few days)
Click to expand...
Click to collapse
Please try it! I want to have a sure downgrade after root.

no links :-/

Apparently I need to fix it, and i dont have time right now.

jcase said:
Apparently I need to fix it, and i dont have time right now.
Click to expand...
Click to collapse
ohh ok. NP

where is the link to download
?

bah never mind shouldhave read the last post.... =X

Now, if I root and go stock, the engineering bootloader stays correct? Would they notice that the engineering bootloader was there if I turned it in for warranty? What's the difference in appearance on the engineering bootloader?

Dire situation! Help please.

I was so excited to update to Ice Cream Sandwich but my wifi xoom is stock rooted on 3.2.1 and so I booted into clockworkmod recovery readying my nandroid backup before I set it to stock and it stays frozen on the backing up data portion. I don't think I had enough free space for a full back up so I force reset and now I'm stuck in a boot loop. I can't get my tablet to mount on the computer and the external sd card has never worked correctly. I have pictures and movies of my baby when he was first born and I don't wanna lose this data forever. How the HELL do I fix this? Any way to transfer the contents of my xoom or am I completely f*****? I should've gotten an Ipad. I'm obviously not smart enough to handle Android.

Let's see. You can't brick these things first of all, I tried its almost impossible.
Reboot the sucker with volume+ and power and go into the dev forum and read the rest of the instructions.
Sent from my Xoom using Tapatalk

I appreciate the quick reply but I've reset the xoom several times. It'll stay on the honeycomb boot animation forever or until the battery dies. I don't know what to do.

If you flash a recovery you should then be able to get
into the recovery stage, from there you can mount the
Xoom and hopefully back up your photographs onto
your computer. Search forums for the recovery to use,
the info already on the site is much better than I can
hope to provide... good luck and I hope you save your
pictures

jessman1988 said:
I appreciate the quick reply but I've reset the xoom several times. It'll stay on the honeycomb boot animation forever or until the battery dies. I don't know what to do.
Click to expand...
Click to collapse
Boot to recovery and make sure that still works. Then let's go from there.
Do you have ADB running on your computer? We can use that to fix things.
It's nearly impossible to totally brick a XOOM. I've brought mine back from exactly the same boot issue you are talking about.
---------- Post added at 05:48 PM ---------- Previous post was at 05:34 PM ----------
Cut and Pasted from NearDood's thread about 3 or 4 down:
1) Go to this link: http://developer.motorola.com/products/software/ link and download the US release (122 mb, down the bottom of first table). This is the stock release of android that my device was shipped with.
2) Unzip it and extract the contents (should be a set of .img files) to your android-sdk/tools folder (You will need the android SDK, fortunately, there are plenty of tutorials on how to obtain/install it, just search it in Google or right here on xda)
3) Put your xoom into fastboot mode (power on and during the motorola logo repeatedly press volume down until the menu appears in top left of screen, press volume down until you see fastboot, then press volume up, will show starting fastboot protocols)
4) Open a command window in your /tools directory (select tools folder and shift+right click and choose it from the menu that appears in windows)
5) Type the following: fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache

athletex2 said:
Boot to recovery and make sure that still works. Then let's go from there.
Do you have ADB running on your computer? We can use that to fix things.
It's nearly impossible to totally brick a XOOM. I've brought mine back from exactly the same boot issue you are talking about.
---------- Post added at 05:48 PM ---------- Previous post was at 05:34 PM ----------
Cut and Pasted from NearDood's thread about 3 or 4 down:
1) Go to this link: http://developer.motorola.com/products/software/ link and download the US release (122 mb, down the bottom of first table). This is the stock release of android that my device was shipped with.
2) Unzip it and extract the contents (should be a set of .img files) to your android-sdk/tools folder (You will need the android SDK, fortunately, there are plenty of tutorials on how to obtain/install it, just search it in Google or right here on xda)
3) Put your xoom into fastboot mode (power on and during the motorola logo repeatedly press volume down until the menu appears in top left of screen, press volume down until you see fastboot, then press volume up, will show starting fastboot protocols)
4) Open a command window in your /tools directory (select tools folder and shift+right click and choose it from the menu that appears in windows)
5) Type the following: fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Click to expand...
Click to collapse
U realize this will wipe the entire xoom right

Hello. Thanks for posting the tutorial. I have the SDK and everything set up from when I rooted my Xoom but I realize that I should back things up more often and I might as well just format and start fresh. I'm pretty damn depressed but then I could update to ICS and I just want the headache to be over. Any way to copy the contents of the xoom on my pc, or would I have to be booted up properly first?

Okay. I directions and even relocked the xoom. Now it's stuck on the dual core motorola screen without a boot animation. I even repeated the directions again to try and fix it. What do I do now? This is so stupid...It made it worse.

athletex2 said:
Boot to recovery and make sure that still works. Then let's go from there.
Do you have ADB running on your computer? We can use that to fix things.
It's nearly impossible to totally brick a XOOM. I've brought mine back from exactly the same boot issue you are talking about.
---------- Post added at 05:48 PM ---------- Previous post was at 05:34 PM ----------
Cut and Pasted from NearDood's thread about 3 or 4 down:
1) Go to this link: http://developer.motorola.com/products/software/ link and download the US release (122 mb, down the bottom of first table). This is the stock release of android that my device was shipped with.
2) Unzip it and extract the contents (should be a set of .img files) to your android-sdk/tools folder (You will need the android SDK, fortunately, there are plenty of tutorials on how to obtain/install it, just search it in Google or right here on xda)
3) Put your xoom into fastboot mode (power on and during the motorola logo repeatedly press volume down until the menu appears in top left of screen, press volume down until you see fastboot, then press volume up, will show starting fastboot protocols)
4) Open a command window in your /tools directory (select tools folder and shift+right click and choose it from the menu that appears in windows)
5) Type the following: fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Click to expand...
Click to collapse
Never try that because it will erase everything!!!

I was already aware of that but I really just want my stupid Xoom to start up again and even after erasing everything and flashing everything it won't even grant me with a simple boot-up. What the hell do I do to fix my Xoom now that everything's gone and I have nothing to lose?

jessman1988 said:
Okay. I directions and even relocked the xoom. Now it's stuck on the dual core motorola screen without a boot animation. I even repeated the directions again to try and fix it. What do I do now? This is so stupid...It made it worse.
Click to expand...
Click to collapse
since you have relock your device, you have already lost all your data, there is no way back. (you shouldn't relock it in the first place)
and right now, you want to "unbrick" your xoom and that's simple:
1) go to fastboot
2) unlock the bootloader again
3) go to http://developer.motorola.com/products/software/
4) download the right image for your device
5) extract the zip file
6) flash the images with fastboot using the instructions shown on the website
7) (optional) lock the bootload again, or you can leave it unlocked

I downloaded the second from the top like I was told to but it stays stuck at the motorola screen. Everything says it was successful in fastboot but I just can't get it to boot up. What else is there to try? I have I wifi US xoom. Did I download the wrong rom?

I know this should not matter, but when you did all of this did you still have your SD card in the Xoom? If so take it out and try again. I was having some issues flashing my Xoom and after I took the SD card out everything worked fine.

I actually took my SD card out before I did anything with fastboot. I've never been able to get recovery to read my sd either. Basically, I need some magic cure all through fast boot or I'm gonna have to chuck my Xoom in the closet with all my other "broken devices".

Okay. In an act of desperation I've unlocked my device again and have some version 3 clockworkmod recovery installed and I got Team EOS nightly 36 of ICS installed. I wanted the official 4.0.3 but seeing as how my xoom can somewhat function again, what is the best firmware, hands down to be running on and can i get a tutorial on how to get there? Thanks again for helping a poor n00b out, but I don't know where to go from here. I want a stable OS, and the nightlies kinda make me feel unsure. Thank you so much.

jessman1988 said:
Okay. In an act of desperation I've unlocked my device again and have some version 3 clockworkmod recovery installed and I got Team EOS nightly 36 of ICS installed. I wanted the official 4.0.3 but seeing as how my xoom can somewhat function again, what is the best firmware, hands down to be running on and can i get a tutorial on how to get there? Thanks again for helping a poor n00b out, but I don't know where to go from here. I want a stable OS, and the nightlies kinda make me feel unsure. Thank you so much.
Click to expand...
Click to collapse
The Eos nightlys are absolutely stable and on #37 for wingray, is quite complete. You will need to flash the Eos GApps v10.2, then once you set everything up, just stick with that until Eos releases their final version.
You have nothing to gain from going to the "official" stock ICS rom. Take some time to get to know the Xoom and hows/whys of flashing before going on another adventure...that's my advice!

Hey thanks. I'm glad I picked a decent one. I just can't get some of my game,es working. Even ones that say they're compatible with ice cream sandwich and my Xoom. Is this normal for a test build? I'm gonna be freaking out if I can't play my modern combat 3. Lol'

jessman1988 said:
Hey thanks. I'm glad I picked a decent one. I just can't get some of my game,es working. Even ones that say they're compatible with ice cream sandwich and my Xoom. Is this normal for a test build? I'm gonna be freaking out if I can't play my modern combat 3. Lol'
Click to expand...
Click to collapse
just in case you want to flash to stock so you can have the soak test ICS you need to go back to stock using this
Build HWI69 for US Retail from this section MZ604 - XOOM with Wi-Fi
a few boxes down

Thanks a bunch. Is there a link or further instruction because I messed up because I didn't have clear direction. I got modern combat 3 working by installing EOS nightly 37 but its very choppy and grand theft auto 3 freezes whenever it goes in game. I would very much like to use the official version if its more stable.

It's not an issue of stability; it's how the build, which I think is now a debugging build, is recognized by the game app. If the games are the most important for you, then happy flashing!

[Q] Sorry... but how to root?

Hi Everyone, first - I apologize if this is already covered somewhere in here, I promise you that I scrolled through dozens of posts and even bricked my xoom twice before I decided to write here... so here is my situation:
I have a MZ604 WIFI only US version xoom, currently restored back to original and updated to latest Google allows 4.1.2 JB, device is locked.
I want to get to 4.2.2 but I know Google don't support us anymore, so looking at how to root then ROM to 4.2.2
Again - I'm sorry if this is existing somewhere in here, the only posts I could find were out dated (from 2011 and 2012) and did not work, can someone please explain / guide / direct me to a clear instructions on how to first of all root the machine? then flash to any of the suggested ROMS? your favorite rom suggestion is also appreciated!
For example - I found this:
http://forum.xda-developers.com/showthread.php?t=1997434
and this:
http://forum.xda-developers.com/showthread.php?t=2026100
and they both look awesome! but no instructions, how to root first, then I guess I need CWM to install the actual rom? maybe this is for people who are already familiar with the steps and are comfi with just the link,but I need a little help...
Thanks again and sorry...
Me

Please help?
mtadmor said:
Hi Everyone, first - I apologize if this is already covered somewhere in here, I promise you that I scrolled through dozens of posts and even bricked my xoom twice before I decided to write here... so here is my situation:
I have a MZ604 WIFI only US version xoom, currently restored back to original and updated to latest Google allows 4.1.2 JB, device is locked.
I want to get to 4.2.2 but I know Google don't support us anymore, so looking at how to root then ROM to 4.2.2
Again - I'm sorry if this is existing somewhere in here, the only posts I could find were out dated (from 2011 and 2012) and did not work, can someone please explain / guide / direct me to a clear instructions on how to first of all root the machine? then flash to any of the suggested ROMS? your favorite rom suggestion is also appreciated!
For example - I found this:
http://forum.xda-developers.com/showthread.php?t=1997434
and this:
http://forum.xda-developers.com/showthread.php?t=2026100
and they both look awesome! but no instructions, how to root first, then I guess I need CWM to install the actual rom? maybe this is for people who are already familiar with the steps and are comfi with just the link,but I need a little help...
Thanks again and sorry...
Me
Click to expand...
Click to collapse
Any reply? please? someone? help me get there

mtadmor said:
Any reply? please? someone? help me get there
Click to expand...
Click to collapse
If you want to install a custom 4.2.2 ROM, you don't have to root. All you have to do is unlock your bootloader. Make sure you have adb and fastboot set up (there are tons of tutorials around on how to do this), then boot your Xoom into bootloader mode. To do this, turn it on, wait for the Motorola logo, count to 3 at a reasonable speed, then hit volume down. Keep hitting volume down until the screen reads "fastboot mode" and then press volume up. Plug the Xoom into USB, go to a command prompt, and type:
fastboot oem unlock
Follow the on-screen instructions to unlock your bootloader. It will wipe all your data. Once that's done, boot up your Xoom and download whatever custom ROM you want. Put it on the Xoom's internal storage somewhere. Next, download ClockworkMod recovery for the Xoom WiFi. Put this on your PC somewhere and rename it to cwm.img (easier to type that way).
Reboot back into bootloader fastboot mode (instructions above). Go to a command prompt and change directories to whatever folder you saved ClockworkMod into. Type this:
fastboot flash recovery cwm.img
fastboot reboot
Wait for the Motorola logo. Count to 3 at a reasonable speed, press volume down. This time, press volume down until you see "Recovery Mode". Press volume up. This will boot you into ClockworkMod recovery.
Use the volume keys to navigate the menus and the power button to select. Scroll down to "Install ZIP from sdcard", then navigate to find wherever you put the custom ROM file on your Xoom's internal storage. Flash it, then do a wipe data and cache (also inside clockworkmod), then reboot your Xoom.
At this point, your custom ROM should boot and you should be in business.

This answer was already answered on Xoom FAQ, please check it for further information
"This Story Ends Where It Began" - Octavarium (Dream Theater)

here is the link to FAQ http://forum.xda-developers.com/showthread.php?t=2145522

[ROOT] Guide for the Moto Maxx XT 1225

Updated guide rewritten here: http://forum.xda-developers.com/showpost.php?p=68538891&postcount=1
WARNING: THIS IS FOR THE MOTO MAXX ONLY. I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT MIGHT HAPPEN TO YOUR BELONGINGS.
@respider made a custom recovery for us. It's not even beta, it's alpha. What it means is that it's the first attempt to make a custom recovery. Bugs are expected.
To root, you can use the attached datroot, or SuperSU
Before anything, go to the Motorola website and unlock your bootloader.
1. Download the file attached. Download the recovery
2. Leave the maxxpatched.img in your PC and put datroot.zip in your phone.
3. Open a terminal with adb and fastboot. If you don't know what i'm talking about, Google it.
4. In terminal use:
Code:
adb reboot bootloader
Your phone will reboot and you'll see the fastboot screen.
5. Unzip the recovery and rename the file to recovery.img
Code:
fastboot boot recovery.img
6. Now you'll boot into the recovery. Press simultaneously Power and Vol UP to show the commands.
Some users say the best way is to hold the Vol UP and then press and release the Power.
7. Install > click on the datroot.zip/supersu.zip> let it install > clear cache and dalvik
8. Reboot system.
9. You've got root.

glad to see the recovery is being useful... I hope we manage to get a working TWRP or CWM soon

Do I need to unlock the bootloader first??

ellopr said:
Do I need to unlock the bootloader first??
Click to expand...
Click to collapse
If he says no, he just earned like over 5 grand.

Maxx only were his first words, yes you must unlock your bootloader first.

Did this couple of days back, worked perfectly!! Now waiting for custom recovery and roms
---------- Post added at 10:48 PM ---------- Previous post was at 10:45 PM ----------
Hey since some of us are rooted, any body with knowledge care to look into trying to boost the sound of this baby a little?

tested
NOT WORKING ON DROID TURBO

prking07 said:
Did this couple of days back, worked perfectly!! Now waiting for custom recovery and roms
---------- Post added at 10:48 PM ---------- Previous post was at 10:45 PM ----------
Hey since some of us are rooted, any body with knowledge care to look into trying to boost the sound of this baby a little?
Click to expand...
Click to collapse
Bummed i aint' got root. Anyway. 'mixer_paths.xml' search xda for the proper values to modify. Its super simple and should dramatically increase the volumes. I've used this method on a bunch of phones running stock 4.x.x. Will work on 5.0 also. Tested on my nexus 7 2nd gen.

I'm sure Danger2u was 'reporting' and not 'complaining'.. easy enough to understand. it's way impossible OP would have been trying this on a turbo either,...

There needs to be a Moto Maxx forum. Seeing this in the turbo forum from my turbo just makes me sad.

alexcreto said:
5.
Code:
fastboot boot maxxpatched.img
6. Now you'll boot into the recovery.
Click to expand...
Click to collapse
When I get to step 5 and try to boot into recovery, only a resting android with a red exclamation point is shown.
And a text that says "Ningún comando" which means "No command".
I can't do anything else, after a while the phone reboots itself into my homescreen.
What should I do? What could be wrong?
UPDATE: Ok, after a while I found the solution:
When it shows "no command", press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key. It will display additional menu options.
Click to expand...
Click to collapse
Thanks to sbdc003 in androidforumshttp://androidforums.com/
Thanks @alexcreto, great tutorial!

ImpheOtus said:
When I get to step 5 and try to boot into recovery, only a resting android with a red exclamation point is shown.
And a text that says "Ningún comando" which means "No command".
I can't do anything else, after a while the phone reboots itself into my homescreen.
What should I do? What could be wrong?
Click to expand...
Click to collapse
Oh, my bad...
I'm so used to that I forgot to mention.
Press simultaneously Power and Vol UP

alexcreto said:
Oh, my bad...
I'm so used to that I forgot to mention.
Press simultaneously Power and Vol UP
Click to expand...
Click to collapse
Thank you!
I'm comming from Galaxy SII and S4 and I had never had to do this so it's my first time with fastboot, ADB and custom recoveries.

ImpheOtus said:
Thank you!
I'm comming from Galaxy SII and S4 and I had never had to do this so it's my first time with fastboot, ADB and custom recoveries.
Click to expand...
Click to collapse
Don't worry man, glad you enjoyed.

i understand very well that the guide is for Moto Maxx and NOT for Droid turbo.
but like some cases a method works on other phone that are similar
so i tested and just say that is not working on Droid turbo
in this way other users will not try on their Turbo
and i don t make any flame or other

frankeegee said:
I guess there is a reason for your name, eh? ?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I try, but my xt 1225 is not recognized, no drives installed? I have de MDM 2.4.5, but in Windows 7 not Works. How to download latest version of drives to Motorola xt1225?
adb devices not list my xt1225. I try with minimal adb and fastboot and Android SDK.
How to fix this? I need unlock bootloader.
Thanks
Thanks

muccioli said:
I try, but my xt 1225 is not recognized, no drives installed? I have de MDM 2.4.5, but in Windows 7 not Works. How to download latest version of drives to Motorola xt1225?
adb devices not list my xt1225. I try with minimal adb and fastboot and Android SDK.
How to fix this? I need unlock bootloader.
Thanks
Thanks
Click to expand...
Click to collapse
In the control panel, access the device manager and find your phone among the connected devices.
(Im not running Win right now, so Im gonna try to tell you the steps by memory)
You have to right click and install updates to it.
Instead of letting it find them over the net, you'll choose the option to choose one from the list.
In that list find and pick the Moto Comp ADB
That should make it work.
If I switch to Win later today I'll update this post.
Hope it helps....

alexcreto said:
In the control panel, access the device manager and find your phone among the connected devices.
(Im not running Win right now, so Im gonna try to tell you the steps by memory)
You have to right click and install updates to it.
Instead of letting it find them over the net, you'll choose the option to choose one from the list.
In that list find and pick the Moto Comp ADB
That should make it work.
If I switch to Win later today I'll update this post.
Hope it helps....
Click to expand...
Click to collapse
Many thanks, but,
Do not have Moto Comp ADB in the options.
I try again use SDK, show message Daemon not start. Start daemon in port 5037. Daemon start. But nothing is happening. Don not show my device.

muccioli said:
Many thanks, but,
Do not have Moto Comp ADB in the options.
Click to expand...
Click to collapse
I remember that there was a parent called Motorola and a parent called Android ADB. Did you check both?

help
well im in the same position of the non recognized adb drivers i can't get my unlocked bootloader, and i wanna ask. after achieving root, can i install xposed framwork an then the gravity box, to make some changes??

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...