Database Users

Rooting my phone - Every step of the way.

I bought my Samsung Nexus S from a Koodo booth here in Canada two days ago and have been enjoying it quite a lot since. I've also been reading up on the wealth of information pertaining to rooting it and trying to sort out so many different factors. I notice I'll have to use the search feature to find one little triviality that comes along and the fix it.
Then I decided to just make my own thread where I'll post every step of the ways I find and how I figure out how to solve my issues involved with rooting my phone.
To start, I found out you can create a backup with NANdroid.
I couldn't find any information on where to download this elusive "NANdroid" and then heard from This thread that all I have to do is
kenvan19 said:
Now lets get started. First, how does one install mods on Android? Lets do a NANDroid backup to begin:
1) Turn your phone off.
2) While holding the Volume Up button press the power button until the screen turns on and you will see a black screen with an Android on it and a lot of numbers and words that will mean nothing to you. This is called the Bootloader. In both the bootloader and the recovery mod you will use the volume buttons to navigate between options and the power button to select one.
3) Navigate down to Recovery option and select it.
4) Navigate down to backup and restore
5) Navigate down to backup and select it and let it run.
Click to expand...
Click to collapse
This didn't seem to be the case when I followed these steps; coming first to the predicted screen,
(containing this information)
Code:
FASTBOOT MODE
HW VERSION - REV 16
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020UCKB2
CARRIER INFO - ATT (but im with Koodo?)
SERIAL NUMBER - Lots of digits.
LOCK STATE - LOCKED
Also giving me the option to select between
Reboot Bootloader
Reboot
Recovery
Power Off
When going into recovery mode I'm greeted with an animation of a box with an arrow coming out of it. This turns into a triangle with a exclamation in the middle of it.
From here I press power and volume up to come to a menu that is supposed to have a NANdroid option I've been told.
Instead; I get the options:
Reboot system now
Apply update from /sdcard
wipe data/factory reset
wipe cache partition
At this point I'm currently stumped, though I'll continue searching as I'd rather not be stuck without a backup before starting the rooting process.
UPDATE: Even though I'm weary of proceeding without backing up, I'm sure I'll be able to restore my phone back to factory somehow.
I spent the night downloading and installing the Android SDK, then started configuring my device for use on windows 7.
Currently I'm in the bootloader interface after installing my phone's device drivers while being in fastboot mode.
The drivers take a couple of minutes, but they install successfully!
On I go, I'll just point DOS to the directory I want it to. Now I'll run the program through dos. What's this?! AND ERROR!?
Psht, I WOULD be missing the "AdbWinApi.dll" Not a hard thing to fix. I'll just google for the file!
Oh! I don't even have to download the file, the directory has just changed!
That was an easy problem to solve with many solutions provided!
Time to try again!
Sweet, it works. WHOA! TEXT ON MY ANDROID WHAT ARE YOU DOING!
And I select Yes to come to a nice screen that says my phone is now unlocked!
Now I need to download an image file? Okay. I can do this.
Okay, flash recovery the flashboot. Looks like the image has updated since the thread's instructions. Hopefully it's still compatible.
Now I just need to root. Just need to install a nice zip file.
AAAND, I can't seem to push it onto my phone for some reason. Time to search.
Oh, I can just copy and paste this file by enabling USB storage and dragging it over.
I'll just follow the rest of the steps, to no errors! Whoo! I'm free to install any ROM I want!

You'll need a custom recovery for nandroid, but first you will need to root. There's guides in the nexus s general section on doing that.
I kind of like this post.
Sent from my Nexus S using XDA Premium App

apreichner said:
You'll need a custom recovery for nandroid, but first you will need to root. There's guides in the nexus s general section on doing that.
I kind of like this post.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I just read through Kursk's guide for rooting the i9020a and i9023 and noticed I have no ability to backup my android in the case something goes wrong.
Am I missing something, or do I have to root before having the privilege of backing up my phone's current ROM.
edit: Got sidetracked by a thread in the Chef's forum and learned that Java is the language for App development for Androids. Been reading about the Android OS and how it works for the past couple of hours. Brains bursting. xd

http://forum.xda-developers.com/showthread.php?t=895545
^ Has pretty much all you need to know for installing a custom recovery and rooting your phone.
It's only once you've installed ClockWorkRecovery Mod that you'll be able to easily make backups.

[GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices on 4.1.X (newbie friendly)

Having recently purchased a TF300T with intent to customize the hell out of it, I ran into a big problem. There wasn't one definitive guide for my general case, some of the steps I read weren't completely clear, and I often had to put pieces together from multiple guides to get where I wanted. Halfway through the process it occurred to me that sharing my experience in form of a guide could give the community something I wish that I had when I began. So enough with the intro, let's visualize the process before we begin.
This guide is for new owners of TF300T devices that have Jelly Bean 4.1.X preflashed from the factory. ​
joelalmeidaptg said:
If your tablet has 4.2.1 Android version from Asus, DO NOT FLASH A RECOVERY THAT WAS ACTUALLY MADE FOR 4.1 TABLETS! You will end up on a PERMANENT BRICK with no solution until now. You won't be able to use fastboot ever again. You won't be able to flash anything ever again. You will be stuck with a bricked tablet!
If you are looking for a Recovery for a 4.2.1 bootloader (and a complete guide for updating), read this thread: http://forum.xda-developers.com/showthread.php?t=2187982 Don't do it with any other tutorial: they are for 4.1 bootloaders!
Click to expand...
Click to collapse
For those curious...
My TF300T was one of the Champagne Gold models purchased from Groupon with a serial that begins with C9. I recall seeing a user with a Champagne Gold from Amazon that still had ICS. If you're still on ICS, this guide isn't for you-- Read up on NVflash and decide if you want to take advantage of it BEFORE you upgrade to JB.
Here's an overview of what we will be doing:
Click to expand...
Click to collapse
Unlock the TF300T
Backup apps, app data and files (Recommended, Optional)
Install ClockworkMod Recovery (soon to be replaced with TWRP; I gave in)
Root the TF300T (Optional)
Backup your stock Asus ROM (Recommended, Optional)
Flash a Custom ROM
Backup your working Custom ROM (Optional)
Additional information you should know:
Click to expand...
Click to collapse
This guide has been made with the total android noob in mind. Having only owned an android tablet for a week, I too am an android noob. On the flipside, I'm no noob to hardware and software exploits and modifications. I've tried to make this friendly for any type of noob, but there are a few instances where I expect basic menu and Windows 7 navigation skills.
ClockworkMod Recovery doesn't appear to have a "Shutdown" function, nor does it display current battery level-- for this reason, the recommendation and warning to have a battery charged to at least 60% is extremely heavy. The worst thing that can happen to any device is usually an incomplete flash. Don't let it happen to you-- start charging your TF300T NOW.
I have seen reports that "Fastboot" doesn't work properly on Windows 7 64-bit. This guide addresses that issue, as I also encountered it. If you don't know what "Fastboot" is, in the words of an admirable comedian, "You gonna learn today". Don't worry about it for now!
Your device came with JB-- you didn't miss the bus for NVflash. In your case, the bus never came.
I am not responsible for any damages caused to (but not limited to) yourself or your device.
Even if you think you're pretty good at figuring this stuff out, stick to the directions as close as possible.
If you love tweaks, you're going to love your custom ROMs.
Let's get started!
Unlocking Your TF300T
Click to expand...
Click to collapse
WARNING: Unlocking your TF300T will void your warranty. If your device breaks or fails under normal use, don't expect Asus to pick up the tab! Be aware that once unlocked, it cannot be relocked.
There are two ways you can go about this-- Either download the official Asus unlock utility for Windows or download the .apk and install from your tablet (Asus utility still working! I successfully unlocked mine on JB 4.1.1). I chose to download the .apk and install directly on my tablet, therefore this is the method I will cover.
To download the .apk file, scan the QR Code below with Barcode Scanner (free; on Play store) and open the URL to the Asus Support page for the TF300T. Alternatively, if you are viewing this thread on your TF300T, you may simply tap the code below.
​
On the Asus Support page, select "Android" as your OS. The page will reload and present you with a list. Click on "Utilities", then after it has loaded, download the Unlock Device App. When it is done downloading, a notification will pop up in the lower right corner. Click on it to install the Unlock tool. You'll also be able to open the app immediately after the install completes-- open it now.
After scrolling to the bottom of the End User Licence Agreement, select the checkbox indicating that you agree to those terms. You should now have access to the slider that will unlock your tablet. Stay connected to your wifi and unlock when ready. The unlock will not work without access to the internet.
If I recall correctly, your tablet should reboot. Just let it do what it wants. After it's done doing it's thing, take this opportunity to make backups! when you and your tablet are ready, we'll continue on to the next step.
Setting Up The Android SDK and Installing ClockworkMod Recovery
Click to expand...
Click to collapse
​Perhaps this was the most frustrating part of my experience-- Installing the Android SDK went fine when I could actually find the .exe download. After that it was a matter of getting the drivers for Fastboot working properly. I was able to narrow it down to a problem for users of Windows 7 64-bit.
From your PC, go HERE, scroll down and click on "Download For Other Platforms". Scroll down more and under the "SDK Tools Only" downloads, you should find a download that looks like: "installer_r##-windows.exe" where "##" is the revision number. Download this .exe and assuming Windows is installed on C:\, install it to either "C:\tools\android-sdk" or "C:\android-sdk". If Windows is not installed to drive letter C, replace the drive letter with the correct letter for your system. Do the same when following the command prompt examples that follow.
Open the Android SDK Manager. Search for "SDK Manager" in the start menu and you should find a result with the same name and a little android icon. Once it's open, you'll be presented with a list. Check the box next to the "Tools" folder, then expand the "Extras" folder and check the box next to "Google USB Driver". In the lower right corner, click "Install packages...", agree to all when ready and begin your downloads.
In the settings application of your tablet, go to the "Developer options" tab near the bottom. Ensure that the switch in the top right corner is in the "ON" position, then under the "Debugging" header, enable "Android debugging". Read the following carefully before you continue: Shut down your tablet and connect your USB cable. Hold the power and volume down buttons at the same time. Keep holding until you see a menu. The menu will consist of a few items, among them there is "RCK", a USB icon, an Android icon, and a "Wipe Data" icon. Tap volume down until the USB icon is selected, then press volume up. Cross your fingers and hope drivers install automatically.
They probably won't, so have windows look in the \android-sdk\extras\ folder. It should say the drivers installed successfully. Either way, open the start menu, and right click on "Computer". Click "Manage", then in the left hand pane of the new window, click "Device Manager". The "Other Devices" section may be already expanded in the center pane. If it is, look to see if "Fastboot" appears in that section with a yellow exclamation mark.
If it isn't there, you shouldn't be worried-- check for a section called "Android Phone" or "Portable Devices". Look for a device called "Android ADB Interface" or "Fastboot". It shouldn't have a yellow exclamation mark next to it.
In the event you have the device appearing with a yellow exclamation mark next to it, go HERE and download PdaNet. This was my remedy for this error. Unplug your TF300T from your computer and install PdaNet following instructions. During the install a warning will appear to install unsigned drivers. Install the driver anyway, and let the installation finish. You can now plug your TF300T back in, and it should be recognized automatically. Just in case, hold the volume down and power buttons again until your tablet restarts and you see your hidden menu again. Once again, tap volume down until the USB icon is selected, then press volume up again to select it. Check the Device Manager again and you should find the "Android Phone" section at the top. Within it, you'll find a device called "Android ADB Interface".
Now that we have your tablet and computer set up nicely, we can finally install ClockworkMod (CWM) Recovery. Go to THIS thread and download the attachment called "recovery-jb.img" (thanks XpLoDWilD!). It is VERY important that you download "recovery-jb.img" as this is the version for users with Jelly Bean bootloader!
Rename the file you just downloaded to "recovery.img" and place it in \android-sdk\platform-tools . In Windows 7, open the Start Menu and search for "cmd". You should see a result called "cmd.exe". Right click that result and click "Run as Administrator". Now type the following commands into the new command prompt window in order to flash CWM Recovery:
Code:
cd C:\tools\android-sdk\platform-tools\
fastboot -i 0x0B05 flash recovery recovery.img
DON'T unplug your tablet!! Don't close the window either! Wait for the command prompt to finish what it's doing, then you can type the final command:
Code:
fastboot -i 0x0B05 reboot
Your tablet will reboot. Once it has fully rebooted, shut it down and hold volume down and power again to access our tablet's hidden menu. This time, instead of selecting the USB icon, select "RCK" and press volume up. If I'm not mistaken, "RCK" stands for "ReCovery Kernel". ClockworkMod Recovery should load up. If it doesn't, then you were not successful in flashing CWM. If it does, then you can go to the Backup and Restore menu and create a backup.
I was overconfident when I went through all this, and I didn't make a backup-- for me, I wasn't able to get my SD card detected (64GB fat32), but even in this case you should be able to make a backup to your "Internal SD card". Unfortunately, you are on your own for this step. Make sure that you transfer this backup to your PC after creating it. You may need to disable Developer options in your TF300T's settings before you can transfer files over again.
In THIS post, XpLoDWilD gives instructions on how to Root your tablet. If I'm not mistaken, this applies to users who are using a ROM that does not already have root. If you care about Root right now, you can go ahead and flash his attached .zip file using CWM to your TF300T.
When I did this, I selected the .zip file with CWM and then went back to the main menu to select reboot. CWM then prompted me that it needed to fix permissions in order to keep Root. I tried it both ways-- first I let it fix permissions, then used a Play store app to check for root. Test came up negative, so I tried again without allowing it to fix permissions. Negative again. I tried again, allowing it to fix permissions again and then left it alone. If you are successful in rooting your TF300T, you can use Titanium Backup to backup your device later. However I used an app that did not require root that worked fine. The choice is yours.
Flashing a custom ROM
Click to expand...
Click to collapse
Now it's time to find a custom ROM to flash. For my guide I will cover Baked TF300T Blackbean #6-- Based on CyanogenMod10, and quite a nice upgrade from the stock ROM. The only downside I found is the Asus App Backup application is not included and cannot be installed. I'm unsure why this is the case-- I have even attempted to install it via CWM with no success. If you need this app or the App Locker app, I suggest you choose a non-CM10 ROM. You are on your own in deciding an alternative, but I have heard great things about CleanROM and I seem to recall reading that these incompatible Asus apps work on it. Don't take my word for it-- do your own research to make sure!
It should also be noted that ROMs like Blackbean #6 have some potentially dangerous settings that can make a power user salivate profusely.
Spiderman's Dad said:
With great power comes great responsibility
Click to expand...
Click to collapse
Okay, so it was his uncle, whatever. But either way, if you're going to install this ROM (or any other with overclock tweaks), BE CAREFUL when selecting different settings for CPU speed and overclocking. I used to overclock my PC as a hobby and pushed a 1.8GHz CPU to 2.77GHz on air cooling.. The thing I learned in the process is if you don't have the proper settings, your computer becomes unstable and weird things start happening. Data corruption, clicking the Start Menu does something crazy and unusual, PC crashes randomly, etc... Some of these errors are due to insufficient cooling-- a problem you cannot remedy when working with a portable device.
Assuming you are new to this tablet like I am, use this rule of thumb when dealing with foreign and potentially dangerous things: DON'T TOUCH IT until you understand it. Then when you understand it, understand it again. Then when you feel you've understood it twice, take baby steps. It's like jumping up a cement set of stairs-- you're definitely not going to try to jump five steps in your first attempt, unless you want to risk smashing your face and bloodying yourself up. Take it one step at a time-- make sure you can land on your feet before deciding to go further.
There's a lot of other options Blackbean #6 has that the average user can still appreciate, so ignore those overclocking/CPU stuff and focus on the other tweaks. Nova Launcher is included and is pretty sweet. I upgraded to Nova Launcher Prime and feel it's worth the extra $4, but I'll leave that for you to decide. There are more options than merely Nova Launcher alone, and not all of them have a price tag.
Without further adieu, let's download the Blackbean #6 ROM and Gapps. Head over to THIS official release thread for the downloads. The names of the files you want are:
baked_tf300t_blackbean-6_jb-bl_b6.zip
gappsinverted-jb-20121029-signed.zip​
Put them into a folder called "bb6" and copy the folder over to your TF300T. If your SD card is working in CWM (from CWM, go to the "mount" menu and try to mount SD card), copy the folder to your SD card.
NOW is the time to do any final backups before your fresh ROM install! I recommend "App Backup & Restore" on the Play store. If your tablet is rooted, you can also use Titanium Backup. Both will work fine, though generally speaking people seem to prefer Titanium Backup. People also seem to prefer TWRP over CWM, but I personally find the design unappealing. More importantly, I could only find a proper guide on installing CWM on a factory flashed JB TF300T.
Once you've made your backups, don't do anything until these backups are safely transferred to your PC! Don't forget to backup your music, movies and photos...
Now that you're 100% confident you've made all the backups you need and your battery is well charged and ready to go, let's flash your custom ROM! Shutdown and enter our hidden menu you should be very familiar with by now. Boot into CWM (with RCK icon from hidden menu selected, press volume up), then press volume up/down to navigate.
READ THE FOLLOWING SECTION BEFORE DOING ANYTHING ELSE:
Select "install zip from sdcard" and tap power. If you placed your "bb6" folder on your SD card, tap the power button once more. If it says "Can't mount /sdcard/" in the bottom left corner, then select "choose zip from internal sdcard" and tap power. Earlier you should have put your ROM and Gapps in a folder called "bb6". If you can't find this folder in either the SD card or internal SD card locations, GO BACK, reboot, and make sure you put the folder on your TF300T or your SD card. You should also make sure that the ROM and the Gapps file are inside that folder as well. Do NOT unzip them! They are just fine as they are. We are NOT flashing the ROM and Gapps yet, we are merely making sure they are there before you wipe your tablet. If the files are there, go back to CWM's main menu.
Select "wipe data/factory reset" and tap the power button. Confirm that you want to wipe, wait for it to finish.
Now select "wipe cache partition" and press the power button. Confirm that you want to wipe, wait for it to finish.
Go back to the main menu and select "advanced" and tap power, then select "wipe dalvik cache" and tap power. Confirm that you want to wipe, wait for it to finish.
Don't worry! Your ROM and Gapps should still be in your bb6 folder. Navigate to "install zip from sdcard" again, and let's make the magic happen. We are going to install the ROM first, then install Gapps. Only after both the ROM and Gapps are installed will we reboot our tablet.
So select the ROM first, confirm that you want to install, wait for it to finish. This one will take a long time compared to the Gapps. Just be patient and wait, even though it looks like it's not doing anything.
Then select the Gapps, confirm that you want to install, wait for it to finish.
Finally, reboot your tablet and cross your fingers. You should be greeted with the sweet victory of the startup animation. Go through the first time setup routine, and make sure the tablet works. From here you can optionally backup your custom ROM, but I recommend getting your settings the way you like them before you backup.
Give yourself a pat on the back--you survived! Hope this guide helped someone out-- I was able to sort through my problems fine, but I felt it important to share my experience. I know I couldn't have been the first to hop through these hoops anyway.
Congrats on your custom ROM Transformer Pad. Enjoy your tablet.
P.S. Questions? Comments? Suggestions? If you have any of the three, feel free to share! If it's a suggestion, please PM me and I'll see about making edits to my guide. All are appreciated, and especially anything that clears up any uncertainties I've expressed.
Special thanks (individuals and groups I owe credit for my process):
Drgravy, Team Baked, and everyone who wrote code that was used in the Blackbean ROMs. Blackbean #6 is my first custom ROM, and so far it's been great!! Keep up the awesome work!
XpLoDWilD, for CWM Recovery + Root on TF300T. These files and instructions were the major keys in making my endeavor a success
I also want to send out a big thank you to every other individual and team who has released a custom ROM for the TF300T-- admirable work, and far more than I could ever do. Thanks for giving us options and making us excited to have a customized tablet!
(....And many more! Currently in finals week (yikes) and can't recall everything right now-- will add more as I remember)

It's a shame that such a well written guide has so little thanks. Have mine.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Very nice. hopefully this helps people just getting the tf300.
note, if you want to install TWRP recovery instead, your command will change accordingly, just make sure you type in the exact file name you want to flash. so if your recovery file is named twrp.blob:
fastboot -i 0x0B05 flash recovery twrp.blob

Thanks!
Your guide helped me a lot. I had problems only with root. Flashed 4 times, but always got "no root acces". Finally, I downloaded root package from here http://forum.xda-developers.com/showthread.php?t=1845377 and it works well

is there any way around that "unknown error..." when i try to use the unlock app yet?
I keep trying but the same error message keeps coming up

sq1ne said:
is there any way around that "unknown error..." when i try to use the unlock app yet?
I keep trying but the same error message keeps coming up
Click to expand...
Click to collapse
Is your tf300 new? first hand? or have u ever sent it to asus for repair before?

Well written, well thought out instructions. Many, many thanks!! I'm still having some trouble though. I get stuck once I download the unlock app, open it, agree to the EULA, then another warning appears that is a black screen white text and a yellow triangle. Nothing happens after that. There are no buttons to agree, no checkboxes, nothing happens. Any advice?
*UPDATE* Figured it out. Be sure to sent the font in settings->display->font size to small, then you will see it. The large font pushes the agree button off the bottom of the screen.

It would be great if CWM in this OP were replaced with TWRP. Many are having issues with CWM. Me being one of them. I flashed TWRP with fastboot and no more problems!
I agree with the post above. Sad that such a well written post has so little thanks. :good:

thnx for this amazing guide, but I am still unsure of this guide will work for me.
I am from Holland (Europe)
specs from my ASUS Transformer TF300T:
Android 4.1.1
Kernel 3.1.10 ([email protected])
Buildnr JR003C.WW_epad-10.4.2.18-20121122
Pad EC Version PAD-EC20T-0216
My question is...will this guide also work for me? ...since I have JB 4.1.1 & build 10.4.2.18
I am also worried about the fact that this guide in for an american(?) transformer I gues...so do I need other files then the files mentioned?
I would love to have ROOT and install a custom rom and remove bloatware etc.
thnx for the help in advance!

Thank you so much, perfect for so many people here.
Can you edit it with TWRP? I would use this right now but as above poster said there have been issues with CWM so don't want to try it.
P.s. i got mine from groupon too

Tamaskan said:
Is your tf300 new? first hand? or have u ever sent it to asus for repair before?
Click to expand...
Click to collapse
bought mine brand new just this past Black Friday.
updated to .18 firmware
I don't want to have to send it in.

GodfleshNL said:
thnx for this amazing guide, but I am still unsure of this guide will work for me.
I am from Holland (Europe)
specs from my ASUS Transformer TF300T:
Android 4.1.1
Kernel 3.1.10 ([email protected])
Buildnr JR003C.WW_epad-10.4.2.18-20121122
Pad EC Version PAD-EC20T-0216
My question is...will this guide also work for me? ...since I have JB 4.1.1 & build 10.4.2.18
I am also worried about the fact that this guide in for an american(?) transformer I gues...so do I need other files then the files mentioned?
I would love to have ROOT and install a custom rom and remove bloatware etc.
thnx for the help in advance!
Click to expand...
Click to collapse
Yes, it will work, I've tried it. But i suggest you use TWRP custom recovery though. CWM has high chances of getting bricked.

Tamaskan said:
Yes, it will work, I've tried it. But i suggest you use TWRP custom recovery though. CWM has high chances of getting bricked.
Click to expand...
Click to collapse
Could you also please add a NOOB tutorial for installing TWRP Recovery (this forum is very confusing in getting the right tutorials / avoiding outdated tutorials which would brick my TF300T etc)?
Example:
quote from XDA forum in TWRP topic: "The fastest and easiest way to install TWRP is to use the GooManager app" <--- GooMnager needs ROOT so I can't use this method?
My ASUS TF300T is completely untouched & unrooted still and don't won't to mess it up.

GodfleshNL said:
Could you also please add a NOOB tutorial for installing TWRP Recovery (this forum is very confusing in getting the right tutorials / avoiding outdated tutorials which would brick my TF300T etc)?
Example:
quote from XDA forum in TWRP topic: "The fastest and easiest way to install TWRP is to use the GooManager app" <--- GooMnager needs ROOT so I can't use this method?
My ASUS TF300T is completely untouched & unrooted still and don't won't to mess it up.
Click to expand...
Click to collapse
www.mediafire.com/?7v1gwbbzqzvzto7 <- fastboot and twrp, the twrp is out dated so if you want you can download new one from twrp website.
2)Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (you must click the fastboot and adb when extracred and i suggest you put your extracted fastboot and recovery zip in C:\(foldername) and then open cmd)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
fastboot -i 0x0b05 flash recovery tf300t-jb.blob
Credits to krabappel2548.

Tamaskan said:
www.mediafire.com/?7v1gwbbzqzvzto7 <- fastboot and twrp, the twrp is out dated so if you want you can download new one from twrp website.
2)Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (you must click the fastboot and adb when extracred and i suggest you put your extracted fastboot and recovery zip in C:\(foldername) and then open cmd)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
fastboot -i 0x0b05 flash recovery tf300t-jb.blob
Credits to krabappel2548.
Click to expand...
Click to collapse
Here is a little update on my progress...
- I unlocked the bootloader of my TF300T
- I managed to install latest TWRP
- Made a (COMPLETE) backup of the untouchedl system with TWRP <--- DO THIS BEFORE ANYTHING ELSE!
- Rooted the TF300T with the WW file in this topic: http://forum.xda-developers.com/showthread.php?t=2033205 <----works awesome!
- Made a second (COMPLETE) backup of the now ROOTED system with TWRP
- Tried installing the latest "Cleanrom 3.01 Inheritance", but got the infamous "bootloop" too...the rom has been pulled down from the forum till that is fixed ( I thought I had done something wtong flashing a custom rom, but actually a lot of others had the same problem)
- Waiting for a "bootloop fixed" Cleanrom Inheritance 3.02....and gonna try flashing it again.

first of all thanks a lot ive been going crazy looking for this!! my question is will it work for me?
i bought my tf300t in sept with ics and upgraded to jb....
also i tried this not to long ago and ran into a problem after i unlocked
so right now its just unlocked but not rooted do i need to reverse that or what?
my apologies im extremely noob haha

GodfleshNL said:
Here is a little update on my progress...
- I unlocked the bootloader of my TF300T
- I managed to install latest TWRP
- Made a (COMPLETE) backup of the untouchedl system with TWRP <--- DO THIS BEFORE ANYTHING ELSE!
- Rooted the TF300T with the WW file in this topic: http://forum.xda-developers.com/showthread.php?t=2033205 <----works awesome!
- Made a second (COMPLETE) backup of the now ROOTED system with TWRP
- Tried installing the latest "Cleanrom 3.01 Inheritance", but got the infamous "bootloop" too...the rom has been pulled down from the forum till that is fixed ( I thought I had done something wtong flashing a custom rom, but actually a lot of others had the same problem)
- Waiting for a "bootloop fixed" Cleanrom Inheritance 3.02....and gonna try flashing it again.
Click to expand...
Click to collapse
i never backup.... I only backup app using titanium backuo, if something on the rom goes wrong i just reflash latest firmware from asus website. If you like custom roms, i suggest you use Energy Rom if you want OC or Hydro rom if you want just modified stock rom with better performance.

I have a problem while I try to run the flash recovery command. I have done all steps prior to this.The only difference I see is in device manager I get "ASUS Android Devices". Now, the error I am getting comes after trying to run the command, I get "error: cannot load 'recovery.img' No error" . I have also tried the pdanet solution. Thank you for your help in advance.

Stupid question... but I am going to ask it. Having never rooted my TF300 it is on latest firmware will this guide still apply to be even though I bought my device running ICS but have updated to latest firmware? Have never rooted tablets before so all new to this.

Agera said:
Stupid question... but I am going to ask it. Having never rooted my TF300 it is on latest firmware will this guide still apply to be even though I bought my device running ICS but have updated to latest firmware? Have never rooted tablets before so all new to this.
Click to expand...
Click to collapse
It will work as long as you are using Jelly Bean

Nexus 10 (Manta) Help Thread - Ask Your Questions Here!

Samsung/Google Nexus 10 Help Thread!
mantaray​
Welcome to the Nexus 10 help thread! You can ask all questions here without the need of background knowledge. This thread is dedicated to solve users problems, so if you don't want to start a new thread for your question, ask it here. Members ready to help will be monitoring this thread and provide answers as soon as possible. For a list of supporters, see here:
Current List of Supporters@demkantor - All Things Nexus - adb & fastboot expert!
@lj50036 - GitHub Expert and All Around Android Guy!
@rirozizo - Battery Guru and Android Know It All!
@XxLordxX - The Unbricker!​
Click to expand...
Click to collapse
Supporters: If you want to be put on or off the list, just send me a PM!
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @ like above. Also, if you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible for posting there, you may post here. And Please Read The 2nd & 3rd Post Of This Thread Before Posting! Thank you!
ROM developers: Please read this. Consider if you want to have a ROM specific help thread or not, if not, most likely questions about your ROM will be asked here if the users aren't eligible for posting in development section.
To all of you: Remember the Rules and the Forum Etiquette

Knowledge is Power!
This section is not meant to offend but rather inform XDA members, please read, understand and abide by what is said in this post... you will never be called a n00b if you do!
First Read This:
~~~~This alone will save you - thanks Tony Stark~~~~
How to post your problem or question
This isn't really complicated but the more you know the more likely you can find your own answer.
But we are here to help! So the more information you give us, the better/faster we may help you!
Step One
Have you searched for the answer to your problem/question?
If not do this first, both the search button in the XDA forums and Google work wonders.
At least attempt to show you did a little research before you scream help or this ROM is garbage, Not searching or just simply complaining will get you ignored EVEN IF YOU WRITE IN ALL CAPS
All questions belong in Q&A Forum All General Phone discussion in General NEVER post random problems in Developers section
Step Two
So you have searched for your answer and can't find it, that's okay, it happens to all of us. But before you create a new thread seek out a similar one (in the proper forum for you device) and ask there - or here.
You may think a new thread is better but in truth people look at the old ones just as much, and keeping all similar questions in one thread helps to elevate congestion and makes the next guys search a ton easier.
Step Three
Know what to post. This means explain your problem as best you can (dont write a book, just not "help my phone is possessed by demons" this is not helpful)
So this means explain all about your phone, boot into your bootloader and write down all from that screen within your post. Are you rooted? Explain where your troubles began and what you have tried to do to fix it.
Give details as much as possible, this often will include a logcat. Which there are many ways to get, learn how to before you have a problem.
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg ; adb logcat -b system -b radio -b events -b main
Code:
cat /proc/last_kmsg
Also read THIS or maybe try THIS
Use pastebin or codewraps around your logcat ( # sign from above)
Obviously every problem and question will require different information, but the more you give the better chance someone can help you.
Step Four
Wait for your answer, do not post the same question in ten threads, one will do. While you are waiting keep searching for your own answer.
When someone gives you help say thank you (with the thanks button preferably - don't make a post that just says thanks... nope, never)
Even if you don't like the answer be grateful someone took time from their day to try and help, If you think it's bad advice maybe reiterate your question and politely ask for a clearer or better explanation to the solution.
Once you have an answer
Edit first post to add the fix. If there was no fix maybe explain why there is no fix in first post.
This will help others searching for a similar problem later. Make sure your helper was thanked as well.
*Remember ROMs, Kernels, etc, may be posted in the developer section, basic questions shouldn't be in those threads. If you must add something, like a bug report, be sure to add a logcat or you man not be helped.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Again, please understand that no one here is paid, we are here to learn and we help for fun. so please be respectful...

Quick Tips!
Okay, so if you look through the Q&A thread here the number one issue that keeps popping up is "Help Bootloop!" and "Help I Think it's Bricked!"
So here is a quick guide that will most often fix these issue (90% of the time anyway)
First things first.... Drivers
Now many of you have these installed, so if you can connect your device to PC through USB and are able to communicate with adb and fastboot just skip this.
If however you can not, then you need to download appropriate drivers for Windows.
You can get these through the Adroid SDK if you already have this
Or direct from the OEM following the link HERE
Or some say having the Naked Drivers works best, so try HERE or HERE or HERE
If you need help installing these then see the next chunk on adb/fastboot or feel free to ask here as well!
*Linux users just need the android rules set up, see fastboot link for how to...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
So after drivers are up... Fastboot!
Well here is many's big fear, but fear not as the terminal is not that scary!
For an in depth explanation on how to use fastboot, I highly suggest reading through THIS
It will have all you need to know and if there are any further question please feel free to ask here or in the fastboot thread.
If you have any issues running fastboot (or adb) commands, please copy and paste all input/output from terminal/cmd here so one of your helpers can assist better.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You can connect to PC and you know the commands.. but what to flash?
For the most part we want to use the stock firmware found here (some OTAs HERE for another use)
Download the latest for mantaray (currently 4.4.2-(KOT49H)
Now check MD5sum or sha1 for a match (Linux use terminal, windows use THIS)
If all is good lets extract the contents (I prefer 7zip but whatever)
So if all of your prep work is a success then when you type
Code:
fastboot devices
Into a terminal/CMD you will see your serial number
If not be sure you are in bootloader mode (power on while holding volume +)
Also have a high quality USB cable if not the one that came with your device
*Still have issue, ask in this thread!
If you have a locked bootloader it may be wise to
Code:
fastboot oem unlock
Then follow the below info, if you don't want to unlock your tablet just run the flash-all.bat to get similar results
And now you have a bunch of images, lets erase and flash so we will be oh so clean!
*have everything backed up first! this will erase your tablet!
Code:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
now after we cleaned things up, lets flash back to stock!
Code:
fastboot flash bootloader nameofbootloader.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
(Everything should be named accordingly except for bootloader, so change this command)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Congrats! You can reboot to a functioning tablet!
Some quick notes:
If you want a custom recovery, fell free to instead flash latest TWRP or CWM or whatever.
You do not need to use stock recovery for the above to work, but you will need your custom recovery in a .img
Similarly if you want a custom ROM instead of stock you can do this, but only if your dev supplies you with the system.img, if not just boot to recovery, make a nandroid, wipe all, flash custom ROM and gapps through adb sideload.
If you still have a bootloop or a "brick" then ask us here and someone will be glad to give you personal assistance.
Or for real time help you can see if anyone is at ##Manta_Help_IRC on freenode
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Anything I missed feel free to ask in this thread!
Happy Flashing!

Tech Specs and More!
Want To Know More About Your Tablet
GENERAL INFO
GSM ARENA
Factory Images "mantaray" for Nexus 10
AOSP
Click to expand...
Click to collapse

Quick Linux/Unix Rooting Guide
First of all, you need to have Fastboot and ADB. To do as such open your command line and type:
Code:
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/fastboot
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/adb
Now that you have both files, you need to setup them to be able to use. As you're an Unix user you'll probably get what I'll do here, you can do it slightly different, but this way was the easiest IMO, also it makes the procedure for next times using adb and fastboot easier. Type the following:
Code:
sudo mv fastboot /usr/bin/fastboot
sudo mv adb /usr/bin/adb
sudo chmod 755 /usr/bin/fastboot
sudo chmod 755 /usr/bin/adb
Now that you have adb and fastboot set up it's time to start the real thing. First of all, make sure to backup your device, as everything will be lost in this procedure! First you need to unlock your device bootloader (if it is already unlocked, skip this part). Please, go to settings, "About Device" and click multiple times "Build Number", a new tab will appear in settings, called "Developer Options", go there and enable USB Debugging. Now plug your Nexus 10 on your PC and type this to check if your device was recognized:
Code:
adb devices
If something came up it was successfully recognized and you can follow up :victory:, but it nothing appeared you may need to check this:
http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/
When you get your device recognized do the following:
Code:
adb reboot bootloader
Wait for the device to reboot, when it turns on again, you'll type the following:
Code:
sudo fastboot oem unlock
Now follow the instructions on your tablet screen. As soon as your bootloader is unlocked the device will reboot, so you'll now download the recovery and the Superuser.
Get the TWRP from here (download the .img file): http://www.teamw.in/project/twrp2/128
Get the SuperSU from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
Click to expand...
Click to collapse
Copy SuperSU to your device internal memory (that's probably empty now) and rename the .img file of TWRP to recovery.img. Now enable USB debugging again (it's explained above lol) and replug the tablet on your PC. Time for typing again! (Please, open the terminal in the folder where the recovery.img is located).
Code:
adb reboot bootloader
Wait for it to reboot, and then type:
Code:
sudo fastboot boot recovery.img
(If you want to install the recovery permanently in the device, type 'sudo fastboot flash recovery recovery.img' before issuing the command above).
Now you probably see a screen like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click in Install and select the SuperSU zip that you copied to your tablet internal memory earlier. When the flash is complete, reboot the tablet and congratulations! You're rooted :victory:.
Hope this helps anyone who may need it!
Click to expand...
Click to collapse
Quick Linux/Unix Restoring to Stock Guide
So you've decided that you don't want root anymore or you did something and want to restore to stock? That's not a hard thing to do! Just follow these steps and you'll be fine.
First you need to have adb and Fastboot ready. To do as such open your command line and type:
Code:
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/fastboot
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/adb
Now that you have both files, you need to setup them to be able to use. As you're an Unix user you'll probably get what I'll do here, you can do it slightly different, but this way was the easiest IMO, also it makes the procedure for next times using adb and fastboot easier. Type the following:
Code:
sudo mv fastboot /usr/bin/fastboot
sudo mv adb /usr/bin/adb
sudo chmod 755 /usr/bin/fastboot
sudo chmod 755 /usr/bin/adb
Now that you have adb and fastboot set up it's time to start the real thing. First of all, make sure to backup your device, as everything will be lost in this procedure! First you need to unlock your device bootloader (if it is already unlocked, skip this part). Please, go to settings, "About Device" and click multiple times "Build Number", a new tab will appear in settings, called "Developer Options", go there and enable USB Debugging. Now plug your Nexus 10 on your PC and type this to check if your device was recognized:
Code:
adb devices
If something came up it was successfully recognized and you can follow up :victory:, but it nothing appeared you may need to check this:
http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/
When you get your device recognized do the following:
Code:
adb reboot bootloader
Wait for the device to reboot, when it turns on again, you'll type the following:
Code:
sudo fastboot oem unlock
Now you'll follow the instructions on screen. When your device is unlocked, you'll have to download the stock firmware you want from one of those links:
Android 4.2.2. - https://dl.google.com/dl/android/aosp/mantaray-jdq39-factory-d79f489e.tgz
Android 4.3 - https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Android 4.4 - https://dl.google.com/dl/android/aosp/mantaray-krt16s-factory-94413961.tgz
Android 4.4.2 - https://dl.google.com/dl/android/aosp/occam-kot49h-factory-02e344de.tgz[/CODE]
Click to expand...
Click to collapse
Now that you're done with your download, you'll extract the .tgz package the way you prefer. Now, open a command line in the folder where the extracted files are and (with your device plugged on fastboot mode) just type:
Code:
chmod 755 flash-all.sh
sudo ./flash-all.sh
The procedure will now begin. It can take some time to finish. When it ends, it's recommended that you lock back your booloader, which is as easy as unlock. Type (tablet plugged in fastboot):
Code:
sudo fastboot oem lock
Hope this helps!
Click to expand...
Click to collapse
~Lord

XxLordxX said:
If you want I can do the Linux walkthrough and script . I'll be more than glad to assist in this.
~Lord
"This Story Ends Where It Began"
Sent from my monstrous Xperia Z1
Click to expand...
Click to collapse
Yes a Linux walk-through is what I was going to do... I can also do a windows one it will just take me a bit longer... Thx lj

i want in! "all-round-android-guy"
Sent from my Nexus 4

Nexus 10
I've followed the instructions, unlocked the bootloader all the commands executed with "okay" but then on reboot the tablet is exactly like it's been from the get go, still showing user info and still showing all downloaded apps and updates, nothing works correctly. Thought maybe was a half installed update or virus. Nothing I've tried resets this to Factory. It's the Gtp 8110

kerriganinks said:
I've followed the instructions, unlocked the bootloader all the commands executed with "okay" but then on reboot the tablet is exactly like it's been from the get go, still showing user info and still showing all downloaded apps and updates, nothing works correctly. Thought maybe was a half installed update or virus. Nothing I've tried resets this to Factory. It's the Gtp 8110
Click to expand...
Click to collapse
What is your PC's OS.....:good:

OS
lj50036 said:
What is your PC's OS.....:good:
Click to expand...
Click to collapse
Windows 7 64 bit. on several machines. I tried 3 diff systems same results, even tried the hated toolkits, but the bootloader locks on any reboot at all. Negating any changes, the fastboot at least didn't reboot so it said all commands were completed, but nothing actually changed. I'm having issues reading those verifications on the page to post, is there a way around that. I got the phone number to call this in to Samsung for service, something has it locked and I've wasted way too much of my life toward trying to work on someone else's tablet. I've used the flash method on several phones and tablets in the past, so not a complete novice, just know it's not giving the same results as for others because something's wrong with the tablet.

This indeed is a strange issue, it seems others have had the same challenge
http://forum.xda-developers.com/showthread.php?t=2638227
Can you try the fastboot method of restoring stock again and this time copy and paste all input/output here
Also can you write down all info on bootloader screen
Sent from my Nexus 4 using XDA Premium 4 mobile app

Nexus 10 Boot behavior
Hello forum gurus!
I have a question regarding the boot behavior of the Nexus 10 that you'll probably know something about.
I need to have the device boot straight to the android desktop after it's been plugged in while in an off state. Usually, most devices boot into a battery-charging screen when you apply power while they're off, then they top up the battery and go to sleep, waiting for you to press the power button.
I'm hoping there is a way to alter this behavior and get the device to boot into android's desktop straight up. I've seen this setting being changed between different ROMs and I'd like to hear your opinion how to get the change done.
This is for a project of mine, the way I see it, i'll be using a few of these tablets for an installation.
Thank you for your feedback in advance!
Best,
Stef

Hi wheezardth
Unfortunately I can't answer your question directly as I have never attempted this. The boot sequence is controlled by the bootloader but I have often seen android devices with a custom recovery boot directly to recovery when being off and then plugging in. So this would mean that the bootloader must look to the kernel (which a recovery is a kernel) for some direction at this point.
It more than likely is possible to alter either the kernel partition or possibly the recovery to do exactly what you are after but how you implement this I can't say off hand. But I will say it is unwise to attempt to alter the bootloader itself so look to kernel ninjas for help on this one.
I'll talk with some people who may have an answer on this and get back to you and if you know any (they don't have to own a n10) ask them and see if they may have an answer
Best of luck and I'll let you know what I find
Sent from my Nexus 7 using XDA Premium 4 mobile app

Thanks a lot, also for the quick response.
I'll wait for your reply, so we don't end up pestering the same people twice for the same thing.
BR,W
demkantor said:
Hi wheezardth
Unfortunately I can't answer your question directly as I have never attempted this. The boot sequence is controlled by the bootloader but I have often seen android devices with a custom recovery boot directly to recovery when being off and then plugging in. So this would mean that the bootloader must look to the kernel (which a recovery is a kernel) for some direction at this point.
It more than likely is possible to alter either the kernel partition or possibly the recovery to do exactly what you are after but how you implement this I can't say off hand. But I will say it is unwise to attempt to alter the bootloader itself so look to kernel ninjas for help on this one.
I'll talk with some people who may have an answer on this and get back to you and if you know any (they don't have to own a n10) ask them and see if they may have an answer
Best of luck and I'll let you know what I find
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Please Help
Main issue: Unable to write to internal storage
Symptoms: Cannot write to external storage,
Google Play FC
Opening Gallery shows "no external storage available"
Opening camera shows "insert an SD card before using the camera"
Trying to open internal sd from ES file explorer storage/emulator/0 not found.
I installed Omni Rom. Then i changed to other roms which were already in the storage.I noticed I could not write to internal storage but i could read.I tried 3 roms then i switched to stock 4.4.2 and locked my bootloader. I heard installing a custom kernel may help so I tried flashing one but didnt help. I can install APK's through ADB but not otherwise.I cannot download anything also.
Currently im in stock 4.4.2 rooted bootloader unlocked.
My problem is different as i can install apk's that means the emmc is not corrupted? (Not sure)
Storage shows: 26.75 GB available Total : 27.30
Please help me

unitnerd said:
Main issue: Unable to write to internal storage
Symptoms: Cannot write to external storage,
Google Play FC
Opening Gallery shows "no external storage available"
Opening camera shows "insert an SD card before using the camera"
Trying to open internal sd from ES file explorer storage/emulator/0 not found.
I installed Omni Rom. Then i changed to other roms which were already in the storage.I noticed I could not write to internal storage but i could read.I tried 3 roms then i switched to stock 4.4.2 and locked my bootloader. I heard installing a custom kernel may help so I tried flashing one but didnt help. I can install APK's through ADB but not otherwise.I cannot download anything also.
Currently im in stock 4.4.2 rooted bootloader unlocked.
My problem is different as i can install apk's that means the emmc is not corrupted? (Not sure)
Storage shows: 26.75 GB available Total : 27.30
Please help me
Click to expand...
Click to collapse
Hi,
Did you try formatting your storage? I know that relocking the bootloader will format, but maybe you need to reformat with a PC or something... Make sure you didn't select a bad partition .
Sorry, but this issue is a little weird... And I can't help you too much, I'll think a little more, but hope this helps a little.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1

XxLordxX said:
Hi,
Did you try formatting your storage? I know that relocking the bootloader will format, but maybe you need to reformat with a PC or something... Make sure you didn't select a bad partition .
Sorry, but this issue is a little weird... And I can't help you too much, I'll think a little more, but hope this helps a little.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1
Click to expand...
Click to collapse
How do i reformat with pc?

hi, i am very new to android (i still use a flip phone)
i have unlocked my nexus 10 (4.4.2), and have stopped there.
after the final steps in post #3
>fastboot erase system -w
>fastboot erase boot
>fastboot erase recovery
>fastboot flash bootloader nameofbootloader.img
>fastboot flash system system.img
>fastboot flash userdata userdata.img
>fastboot flash cache cache.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>Congrats! You can reboot to a functioning tablet!
after the reboot, would the device be rooted?
thanks in advance.

Not if using the factory image, you would still need to boot into recovery and flash superuser, then it would be rooted. Or boot to recovery and flash one of the many custom ROMs, all of which are prerooted
Really the only thing you need to do is unlock the bootloader, flash a custom recovery, then either flash a custom ROM or su
Sent from my Nexus 4 using XDA Premium 4 mobile app

thanks for the reply,
it looks like a 'catch 22' , but im sure its just that, i am seriously confused.
after reading several links, that link, to yet another linked guide.
i thought that i would use team win recovery project but it requires root. so thats a no go.
i checked a few others but same situation, require root to use.
could you/someone recomend a stable recovery or whatever i need.
...my head hurts, ill revisit this tomorrow.

Help with rooting my zenfone laser model ze551kl

Hello. I have a few questions on rooting this phone. (My first time rooting)
First off, Is this the same model as the ze550kl (I assume so but not 100% sure). I have attempted to root this phone through the instructions provided in posts on this website for model ze550kl but I must be doing something wrong with the programs ect. I have never rooted a phone and so this is my first try and I would really like a full in detail screenshot follow through if available to do with the programs once downloaded and any other programs you may need on windows 10 to get to where I need to be. I dislike the zenui so much that is my main reason to root the phone is to remove this and other bloatware as well as some of my friends have some apps that are pretty neat that I would like that are only available through root.. I have also tried other methods posted on YouTube but I think I'm doing something wrong on all of my attempts. I would also like to know if there is a way to make a backup of the original files prior to rooting so I can send my phone in because I have a 2 year warantee if something was to happen (dropped, broken, ect.). In relation to the screenshots if there is any files that have to be placed on the phones hard drive from something I download off the internet please state this specifically, I believe that one or 2 ways I have seen required this but it seems vauge and I don't think it was done correctly by me. I am great at following detailed instructions but I don't know what exactly it is I need to do as I have never done this before so if something has to have a specific name please note that.
Thank you for the help.

My ZF2L should be showing up any minute now, so I'll let you know when it gets here. I'm no expert, but I've been rooting my Android devices since 2009. I think I can help you out.

HampTheToker said:
My ZF2L should be showing up any minute now, so I'll let you know when it gets here. I'm no expert, but I've been rooting my Android devices since 2009. I think I can help you out.
Click to expand...
Click to collapse
Thank you, I think I'm just missing an important step. The zenui just isn't my style. Will be nice to be able to remove

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 02:07 PM ---------- Previous post was at 01:28 PM ----------
Yeah, I think you just need more comprehensive instructions. It happens from time to time. From what I can tell so far, it's a pretty straightforward process for those that are familiar with root, but to a beginner it can be a bit much. As soon as mah lazah is dunna chargin' I'll walk you through the steps I took to root it, install custom recovery, and make a backup of your entire system just in case you ever need to restore your phone to a stock-rooted-but otherwise unmodified state. I should have something up in the next couple hours ?

Updated, rooted, and installed custom recovery. I'll post a short write-up shortly.

First off, I'm going to answer your questions since I didn't previously.
Sorvas33 said:
First off, Is this the same model as the ze550kl (I assume so but not 100% sure).
Click to expand...
Click to collapse
No, they're different, but I'm not entirely sure by how much. I'm 100% sure that they're probably maybe 90% or so compatible, but there are differences. I just don't know them without checking. I wouldn't go flashing anything that doesn't explicitly state that it's for the 551 or is compatible or has had a 551 user test and report success. There are some things that are kind of universal (and we'll get into that a little), but for now let's just stick with using caution.
Sorvas33 said:
I would also like to know if there is a way to make a backup of the original files prior to rooting so I can send my phone in because I have a 2 year warantee if something was to happen (dropped, broken, ect.)
Click to expand...
Click to collapse
We'll make a backup using TWRP, but you'll have to be rooted. A TWRP backup (or nandroid backup) is like a snapshot of your current system. You can customize it and only backup certain parts of the system as well as restore certain parts, but I wouldn't worry about that. Most of the time you'll want a complete backup, anyway. But, to answer your question, no, you'll have to be rooted, but you can always unroot from the phone using the Supersu app. If the damage is physical an unrooted backup wouldn't matter anyway.

So, here's my (hopefully) brief write-up to acquire root, install recovery, make a backup, and ,optionally, install the Xposed framework. Before getting started be sure to have plugged your phone into your computer for Windows to download and install drivers for your ZF2L. Also, you will need to download and install adb in order to use command prompt to flash files to your phone. This link will take you to a thread here at XDA for Minimal ADB and Fastboot. This is the easiest way to install and use adb and fastboot on your computer. Once you have it installed you can proceed to the next steps.
First, you'll need to unlock your bootloader using the app found here. It's in a .zip files for whatever reason, so you'll need to use 7zip or WinZip or WinRAR or something on your computer to extract it and install to your phone. You can plug your phone in and place the extracted app on your external or internal storage or use a cloud storage app like Dropbox or Google Drive to transfer it to your phone. If you plug it in and place on your internal or external storage, then you'll need to use File Manager (it's a stock app) to find and install it. Once installed just run the app. It's extremely user friendly and straightforward. Your phone will reboot when it's done.
Next, you'll have to temporarily boot a modified boot.img using Minimal adb and fastboot. Once this step is completed and the phone boots up you'll need to go to the Play Store and install Supersu as well as Busybox if you want your root apps to work properly.
Go here on your computer and download the modified boot.img named boot_200007.img and place it in the Minimal adb and fastboot folder. As you can see in this screenshot:
my adb and fastboot folder is located at C:\Windows\Minimal ADB and Fastboot. Once you have the boot.img copied to the right folder go ahead and connect your phone, if it isn't already. Hold the power button and restart the phone. As soon as the screen goes off hold the volume up button until the phone boots into fastboot mode. If you have trouble with this, you can just turn the phone off, and then press and hold power and volume up until it boots into fastboot mode. Right click the Minimal adb and fastboot icon and select run as administrator. As long as it's installed correctly, the following commands shouldn't give you any error messages. Before we go further, let me briefly explain what we're doing at this point. We have two options: we can flash the boot.img which will physically write it to the proper partition on your phone, or we can simply boot the phone while the modified boot.img remains on your computer and unwritten to the phone, which is what we want to do in this case. To do this we enter the following command:
fastboot boot boot_200007.img
Your phone should reboot on it's own and once it does open the app drawer and check to see if Supersu is installed. If it isn't, open Play and install it, as well as Busybox. Open Supersu and make sure you have root. Once your done, open Busybox and install Busybox to /system/xbin and reboot when finished. At this point, you can disconnect your phone and ensure the Supersu does give you any errors. Test it by installing your favorite root apps, and since you're new to root, I'll give you some suggestions. You can do a google search to find Adaway. It isn't available in the Play Store because it's an adblocker and ads are Google's bread and butter, but it sure is nice to use apps without intrusive apps trying to sell you something no matter where you go. Root + Adaway have been solving that problem for years. Next we have Root Explorer which is my root file manager of choice. Another community favorite is ES File Manager. Both are great. Titanium Backup, Flashify (install it for the next step), and Viper4Android (not in Play search XDA) are all must have apps for root users. Install and open some of those (especially Flashify) just to verify that they work and let's move on the next step.
Download TWRP here and place it on either internal or external storage. Open Flashify and select Recovery Image and then find and select recovery551_200431.img. This will write the TeamWinRecoveryProject custom recovery to the recovery partition of your phone which will allow you to view, backup, restore, and modify all the relevant partitions that make up the Android operation system. At this moment, it's important to understand that you are now more than capable of completely and totally bricking your phone...but you're also capable of recovering from most problems that can arise from flashing mods and using root apps. This is where we'll make a complete backup for just that very reason.
After you've flashed TWRP using Flashify, you'll be prompted to reboot. Do so, and your phone will reboot into recovery. You'll see a message one the first run with a check box to disable modifications to system or something along those lines (can't remember exactly what it says lol), just don't check it. Leave the box uncheck and swipe the bar to allow modifications to system. Now, you should see the main menu. Select Backup and make sure that Boot, System, Data, and Cache are selected and rename the backup to something along the lines of "stock_rooted" or "stock_backup" if you wish and you're ready to create a nandroid backup. Swipe the button and give it a few minutes. Once done, just reboot and you're good to go.
Now to install Xposed, you'll first need to install the Xposed Installer .apk on your phone from here. To flash Xposed, reboot into recovery (turn off then hold power + volume down) and select Install then select the Xposed .zip package xposed-v80-sdk21-arm64.zip that you downloaded and placed on your internal (preferrably) or external storage beforehand. Once finished just reboot and you're done. Be warned that the first boot after installing Xposed will take a long time (approx. 5-10 minutes). Greenify, Gravitybox (LL), Youtube Adaway, Flat Style Bar Indicators, MaxLock, and NotifyClean are just a few of my favorite Xposed modules. Be sure to read the descriptions for these modules carefully and do not forget that Xposed modules can be tricky and cause problems if they're not compatible with your phone. Honestly, you should ask here before installing any modules that I haven't already mentioned.
Anyway, that's my brief write-up lol. Hopefully, that isn't too hard to follow. Don't hesitate to reply back if you encounter a problem, have any questions, or simply want to report your success and ask for tips. I'll leave you with this little tip: don't give up on ZenUI. It definitely doesn't hold a flame to stock Android, but if you use a third party launcher like Nova Launcher and use Developer Options to increase animation speed to .5 seconds (or turn them off entirely) it's really not so horrible, in my opinion. It's damn sure not TouchWiz.

HampTheToker said:
So, here's my (hopefully) brief write-up to acquire root, install recovery, make a backup, and ,optionally, install the Xposed framework. Before getting started be sure to have plugged your phone into your computer for Windows to download and install drivers for your ZF2L. Also, you will need to download and install adb in order to use command prompt to flash files to your phone. This link will take you to a thread here at XDA for Minimal ADB and Fastboot. This is the easiest way to install and use adb and fastboot on your computer. Once you have it installed you can proceed to the next steps.
First, you'll need to unlock your bootloader using the app found here. It's in a .zip files for whatever reason, so you'll need to use 7zip or WinZip or WinRAR or something on your computer to extract it and install to your phone. You can plug your phone in and place the extracted app on your external or internal storage or use a cloud storage app like Dropbox or Google Drive to transfer it to your phone. If you plug it in and place on your internal or external storage, then you'll need to use File Manager (it's a stock app) to find and install it. Once installed just run the app. It's extremely user friendly and straightforward. Your phone will reboot when it's done.
Next, you'll have to temporarily boot a modified boot.img using Minimal adb and fastboot. Once this step is completed and the phone boots up you'll need to go to the Play Store and install Supersu as well as Busybox if you want your root apps to work properly.
Go here on your computer and download the modified boot.img named boot_200007.img and place it in the Minimal adb and fastboot folder. As you can see in this screenshot:
my adb and fastboot folder is located at C:\Windows\Minimal ADB and Fastboot. Once you have the boot.img copied to the right folder go ahead and connect your phone, if it isn't already. Hold the power button and restart the phone. As soon as the screen goes off hold the volume up button until the phone boots into fastboot mode. If you have trouble with this, you can just turn the phone off, and then press and hold power and volume up until it boots into fastboot mode. Right click the Minimal adb and fastboot icon and select run as administrator. As long as it's installed correctly, the following commands shouldn't give you any error messages. Before we go further, let me briefly explain what we're doing at this point. We have two options: we can flash the boot.img which will physically write it to the proper partition on your phone, or we can simply boot the phone while the modified boot.img remains on your computer and unwritten to the phone, which is what we want to do in this case. To do this we enter the following command:
fastboot boot boot_200007.img
Your phone should reboot on it's own and once it does open the app drawer and check to see if Supersu is installed. If it isn't, open Play and install it, as well as Busybox. Open Supersu and make sure you have root. Once your done, open Busybox and install Busybox to /system/xbin and reboot when finished. At this point, you can disconnect your phone and ensure the Supersu does give you any errors. Test it by installing your favorite root apps, and since you're new to root, I'll give you some suggestions. You can do a google search to find Adaway. It isn't available in the Play Store because it's an adblocker and ads are Google's bread and butter, but it sure is nice to use apps without intrusive apps trying to sell you something no matter where you go. Root + Adaway have been solving that problem for years. Next we have Root Explorer which is my root file manager of choice. Another community favorite is ES File Manager. Both are great. Titanium Backup, Flashify (install it for the next step), and Viper4Android (not in Play search XDA) are all must have apps for root users. Install and open some of those (especially Flashify) just to verify that they work and let's move on the next step.
Download TWRP here and place it on either internal or external storage. Open Flashify and select Recovery Image and then find and select recovery551_200431.img. This will write the TeamWinRecoveryProject custom recovery to the recovery partition of your phone which will allow you to view, backup, restore, and modify all the relevant partitions that make up the Android operation system. At this moment, it's important to understand that you are now more than capable of completely and totally bricking your phone...but you're also capable of recovering from most problems that can arise from flashing mods and using root apps. This is where we'll make a complete backup for just that very reason.
After you've flashed TWRP using Flashify, you'll be prompted to reboot. Do so, and your phone will reboot into recovery. You'll see a message one the first run with a check box to disable modifications to system or something along those lines (can't remember exactly what it says lol), just don't check it. Leave the box uncheck and swipe the bar to allow modifications to system. Now, you should see the main menu. Select Backup and make sure that Boot, System, Data, and Cache are selected and rename the backup to something along the lines of "stock_rooted" or "stock_backup" if you wish and you're ready to create a nandroid backup. Swipe the button and give it a few minutes. Once done, just reboot and you're good to go.
Now to install Xposed, you'll first need to install the Xposed Installer .apk on your phone from here. To flash Xposed, reboot into recovery (turn off then hold power + volume down) and select Install then select the Xposed .zip package xposed-v80-sdk21-arm64.zip that you downloaded and placed on your internal (preferrably) or external storage beforehand. Once finished just reboot and you're done. Be warned that the first boot after installing Xposed will take a long time (approx. 5-10 minutes). Greenify, Gravitybox (LL), Youtube Adaway, Flat Style Bar Indicators, MaxLock, and NotifyClean are just a few of my favorite Xposed modules. Be sure to read the descriptions for these modules carefully and do not forget that Xposed modules can be tricky and cause problems if they're not compatible with your phone. Honestly, you should ask here before installing any modules that I haven't already mentioned.
Anyway, that's my brief write-up lol. Hopefully, that isn't too hard to follow. Don't hesitate to reply back if you encounter a problem, have any questions, or simply want to report your success and ask for tips. I'll leave you with this little tip: don't give up on ZenUI. It definitely doesn't hold a flame to stock Android, but if you use a third party launcher like Nova Launcher and use Developer Options to increase animation speed to .5 seconds (or turn them off entirely) it's really not so horrible, in my opinion. It's damn sure not TouchWiz.
Click to expand...
Click to collapse
Thank you man, I will try this when I get a chance (working 14 hour days ATM) but I will let you know how it goes.also what model member do you have. Because the box I have is we're I got my model number. I can't find the one listed on my box in the device itself.

Exact same model...ZE551KL.
In About Phone the model number is ASUS_Z00TD.

HampTheToker said:
Exact same model...ZE551KL.
In About Phone the model number is ASUS_Z00TD.
Click to expand...
Click to collapse
Exactly what I have. Sweet. I'll update you once I'm done. Thank you for your help and assistance. Any app advice? For uninstalling and cleaning hdd/ram. And theme?

Come on, bro...I gotta know if that's friendly enough to get you squared away...

HampTheToker said:
Come on, bro...I gotta know if that's friendly enough to get you squared away...
Click to expand...
Click to collapse
I should have time either tomorrow or next weekend all depending and I'll let you know then. Depends on how much I have to work. I check this post about once to twice a day. Thank you for your effort and time. I really do appreciate it.

Now I do have one more question on my mind. Does the Asus zenfone that we have keep a flash tracker? Meaning that it keeps track if a phone was rooted. The reason I ask is that I have a 2 year warantee and I know that this will "void" it unless I flash it back. But if they have a tracker then I need to make sure there is a way to reset that as well. From what I have read personally it is only Samsung that is keeping track in this way. Thanks for your help Mr.Toker

Yeah, that's mostly a Sammy thing. I'm coming from a Galaxy S4 that's been passed down to my six year old. I'm all too familiar with flash counters and KNOX security. Thankfully, I don't believe Asus has anything like that. That's one of the many reasons I chose this phone over anything Cricket had to offer. I don't care how good the hardware is, if it can't be unlocked and rooted, then I don't want it.
But, to answer your question more directly, no, I don't believe your warranty will be affected.

Also, I'm going to paste this warning from the developer that built TWRP for us.
Warning
Do not try to fix permission, if you do not know exactly what this is ?
Home > Advance > Fixpermission
Click to expand...
Click to collapse

Just figured I'd add that I believe I read unlocking your boot loader voids the warranty. As of right now, I'm pretty sure there's no way to root without unlocking it, and no way to re-lock it after unlocking.
Sent from my ASUS_Z00TD using Tapatalk

CKtheProblem said:
Just figured I'd add that I believe I read unlocking your boot loader voids the warranty. As of right now, I'm pretty sure there's no way to root without unlocking it, and no way to re-lock it after unlocking.
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
"oem relock bootloader" should do the trick, but I haven't tried it. Sure, technically unlocking your bootloader and rooting voids your warranty, but it's not like either sends a message to Asus in the background stating that you've voided your warranty. The only way they'd know is if you sent it to them for a claim while still rooted. Even then, if it's bricked, it's bricked. They still won't know. If it's not bricked and it's just hardware, then you should be able to unroot.
Honestly, rooting your device has always been a risk to your warranty, but I've yet to have any issues with it since I started rooting my devices in 2009.

HampTheToker said:
"oem relock bootloader" should do the trick, but I haven't tried it. Sure, technically unlocking your bootloader and rooting voids your warranty, but it's not like either sends a message to Asus in the background stating that you've voided your warranty. The only way they'd know is if you sent it to them for a claim while still rooted. Even then, if it's bricked, it's bricked. They still won't know. If it's not bricked and it's just hardware, then you should be able to unroot.
Honestly, rooting your device has always been a risk to your warranty, but I've yet to have any issues with it since I started rooting my devices in 2009.
Click to expand...
Click to collapse
Yeah you're probably right. Luckily, I've never had to send a phone I rooted back in for repairs so I can't say anything about the process.
Sent from my ASUS_Z00TD using Tapatalk

Thanks for those root/recovery instructions, just got this same phone and model number yesterday and just now found the files needed ! You rock! What roms do you suggest?

tmjm28 said:
Thanks for those root/recovery instructions, just got this same phone and model number yesterday and just now found the files needed ! You rock! What roms do you suggest?
Click to expand...
Click to collapse
at present we have only stock rom, no custom rom is available for zenfone laser.

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