Database Info

[HOW-TO] Unlock Bootloader and Root Using Linux

Hey all. Had a few issues trying to unlock and root my own phone on my Linux box, so I decided to post what I learned in the process in case anyone else visiting the forums runs into the same problem.
First, a little background on me, since I'm fairly new here at the xda forums (let alone to the Photon Q).
My foray into the Android world started with the OG Droid. The moment I held that baby in my hands, I knew I wanted to be a part of the community the Android platform would spawn. With the OG and the Droid3, I didn't do much more than help others find certain settings options, or explain how to perform a specific task. However, I learned some of the basics of theming during the last few days I had my D3 before I (sadly) traded it in when I switched from Verizon to Sprint.
When I switched carriers, I picked up the Samsung Transform Ultra, and I've been a major contributor in that arena, particularly over at the phone-specific area of androidforums. I've learned a lot in the time I've had the device, especially with creating flashable zip files and theming. I now look forward to seeing what all I will learn while contributing to the Photon Q community.
Now, before we get into the actual instructions, the obligatory Disclaimer:
I AM IN NO WAY RESPONSIBLE FOR WHAT MAY OR MAY NOT HAPPEN TO YOUR PHONE WHILE FOLLOWING THESE INSTRUCTIONS! FOLLOW THIS GUIDE AND ANY HELP I OR OTHERS GIVEAT YOUR OWN RISK! THIS WILL VOID YOUR WARRANTY!
These instructions assume you are starting with a new phone (meaning it hasn't been unlocked or rooted yet), are relatively familiar with root, are using Linux on your machine, and are fairly comfortable navigating your way around both the phone and PC. As of this writing (5-18-2013), I am running Ubuntu Linux 13.04 on my system, and am basing my instructions on such a setup. Also, the Android SDK and the 'tools' and 'platform-tools' portions from the SDK must be installed and up-to-date.
With all that out of the way, let's get into the guide, shall we?
To ensure the best chance for success, make sure the following applies:
USB debugging is on and the MTP option in "USB computer connection" is selected. This ensures that 'adb' and 'fastboot' will recognize the phone.
Unless otherwise noted, the instructions below assume the phone is connected to your computer via USB, and said computer has its own internet connection independent of the phone.
Before we begin, make sure to have the SuperSU zip downloaded to the root of the SD card (phone or external card), and the preferred recovery image downloaded and moved to the same location that 'adb' and 'fastboot' are in ("/home/user/androidSDK/platform-tools", for example).
CAUTION: If any other Android devices are plugged into your computer in addition to your phone, the 'adb' and 'fastboot' commands will affect ALL devices connected at the time!
To make the guide a little easier to follow, commands that need to be typed will be marked like this. Text to look for will be formatted this way.
Part i: Required tools and downloads:
Depending on which recovery you want to use, I recommend using the SuperSU made available at that recovery's thread. In the event that a SuperSU zip isn't made available, download one from one of the other recovery's threads, then download the recovery img you prefer.
TWRP v2.5.0.0 - thread/SuperSU - here recovery img - here
CWM v6.0.1.0 - thread/SuperSU/recovery img - here
OpenRecovery v2.05 - thread/recovery img - here
PART A: Unlocking the Bootloader
1. Follow instructions #1-6 on the how-to found here.
Open a Terminal window and type lsusb, then look for a line with Motorola PCS; copy down the ID number to the left of Motorola PCS because we will need it shortly (it should look something like 12ab:cd34, though your numbers will be different).
Using Terminal, type sudo gedit /etc/udev/rules.d/51-android.rules. "gedit" can be replaced with your preferred text editor if you don't want to use it or don't have it installed.
Enter your sudo password, and add this line to the file: SUBSYSTEM=="usb", ATTRS{idVendor}=="12ab", ATTRS{idProduct}=="cd34", MODE="0666" GROUP="androiddev", SYMLINK+="android%n", changing "12ab" to match the left part of the ID number you copied down earlier, and "cd34" to the part to the right of the colon.
Save the changes made to the file, then close the text editor. Type sudo service udev restart to ensure both computer and phone recognize the changes that have recently been made (you may not need to re-enter your sudo password if you made the changes to "51-android.rules" quickly enough).
Now go back to the DroidLife (DL) How-To, and pick up at step #8. The only difference is that your Terminal window will look more like this:
(bootloader) 0123456789ABCDEF#0123456789ABCD
(bootloader) EF0123456789ABCDEF01234567#0123
(bootloader) 456789ABCDEF0123456789ABCDEF012
(bootloader) 34567#0123456789ABCDEF012345678
(bootloader) 9ABCDEF
Helpful Hint: the first fourteen numbers on the first line are also your IMEI/MEID (0123456789ABCD in the example above), so if you need that, now's a good time to copy it down as well.
When entering the number in on Motorola's website, it's VERY IMPORTANT no white spaces are included in the number. Using the above example, the number should look like
Code:
0123456789ABCDEF#0123456789ABCDEF0123456789ABCDEF01234567#0123456789ABCDEF0123456789ABCDEF01234567#0123456789ABCDEF0123456789ABCDEF[/COLOR][/FONT]
[*]After following the rest of the DL guide, your phone will reboot normally.
PART B: Installing recovery and obtaining root:
Before beginning this part, make sure your phone's battery has at least 20% (or there-abouts) charge remaining, or 'fastboot' will refuse to flash the recovery.
Open Terminal (if it's not already), navigate to where 'adb' is installed, then type fastboot reboot-bootloader or adb reboot bootloader to get the phone to reboot into the bootloader.
Once the phone is in the bootloader, type fastboot flash recovery <your-recovery-filename-here>.img, replacing <your-recovery-filename-here> with the name of the recovery you would like to use. For example, if you wanted to use TWRP, the above command would look like: fastboot flash recovery openrecovery-twrp-2.5.0.0-asanti_c.img. If the recovery installation was successful, you will get the following lines:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7084 KB)...
OKAY [ 0.563s]
writing 'recovery'...
OKAY [ 1.823s]
finished. total time: 2.386s
Note that the first line says "Variable not supported!". As long as "sending 'recovery'..." and "writing 'recovery'..." say "OKAY" beneath them, then this so-called error can be ignored in most cases.
While holding the Volume-up and Volume-down buttons, press the power button on the phone to reboot it and exit out of the bootloader.
When the options menu comes up, press the Volume-down button until "Recovery" is selected, then press the Volume-up button.
Once in recovery, make a backup of your phone, should you ever need to return to stock for any reason (such as an insurance exchange - since the first half of the guide voids the warranty ). Once that finishes, then flash the SuperSU.zip and reboot the phone.
If everything went well, there will be a super-user app in your app drawer, and root checkers will tell you that your device is rooted. Congratulations!
(Optional) After granting root access to a few apps that require it (such as Terminal Emulator when su is typed in, Titanium Backup or other app backup utilities, Root explorers, etc.), reboot the phone into recovery, and make a second backup of your now stock-rooted phone...mostly just for posterity, but also to keep from having to do it again in the future, should you ever choose to return to stock but want to keep root.
PART C: Wall of Glory
This guide would not be possible if not for the following people and their contributions:
Solust for his guide on the same process on a Windows machine.
arrrghhh for porting TWRP over for our phones, and his thread.
Skrilax_CZ for porting Open Recovery for our phones and his thread.
Shabbypenguin for porting CWM, his thread, and the SuperSU zips.
ChainsDD for the SuperSU app.
Motorola for the Photon Q!
Google for the Android mobile Operating System.
Droid Life for the guide on unlocking the Photon Q's bootloader.
If I've forgotten anyone or made any other mistakes, please PM me and I'll be sure to make the change.
Thanks for playing along! Hope others find this handy; I ended up having to figure most of this out the hard way. Either way, it's been a fun ride figuring out a new phone.

Root for US Asus MeMO FHD 10 build v5.0.21

Well... Here it is.
I also have some script files i found and all the info you need to create your own pre-rooted rom using your current system files if you like that option better. I am currently working on a custom 5.0.1 rom.
READ THE WHOLE POST BEFORE YOU DO THIS!!!
I am only giving you a step by step process put into a easy to use reference guide to help you obtain "root" on your device. I am providing this "As-Is". If you read the whole guide and decide to try it on your own device just know that It may/will void any product warranty that you may have on the device if any. Any time you do anything to your tablet via fastboot or any other means you run the risk of "bricking" your device, or loosing all of your data. I am not responsible for any damage to your device, and i will not be responsible for any damage or loss that you may have as a result of this post, or any instructions that i give here. If you have any questions feel free to send me a message and I will try to help you out, if i can....
I looked and looked and looked through many forums without much luck, and I finally found out how to root the U.S. version ASUS MEMO FHD 10 that has been updated to 4.3 - V5.0.21 by using a pre rooted system rom. If you are not running that version you can go to” Settings - About Tablet - System Update” to update it to 5.0.21
First things first...
Fully charge your tablet, and make a backup of your system!!!
1. Make sure the tablet has a good charge. It will not charge while you are doing this, and who knows what will happen if it dies halfway through the process.
2. Turn USB debugging mode on in the "Developer Options" menu under settings on your tablet.
If you do not have the "Developer Options" menu just go down to "About Tablet" and click the "Build Number" button six or seven times and it will say "developer mode enabled", or something to that effect, and it will unlock the "Developer Options" menu for you.
3. Turn off your tablet.
4. Hold down the volume up button , and press the power button until your tablet turns on. It will boot into fastboot for you.
Connect your tablet via USB cable to your computer, and set it aside.
Now your tablet is ready to go and it is time to set up your computer.
1. To get your computer to recognize your tablet in usb debugging mode you need to install the intel drivers.
2. Download and install minimal adb fastboot.
3. Download the pre-rooted system rom, and then put that rom into the folder that you installed fastboot in on your computers hard drive.
4. I used minimal_adb_fastboot_v1.1.3_setup.exe to do this next part with no problems whatsoever. the only thing was I needed to type the .exe from the command prompt for it to work on my laptop. You might not need to.
Now you have your computer all set up, your tablet is all ready, and it is time to finally do some rooting.
1. On your computer, open up a command prompt, and navigate to the folder that you installed fastboot to.
2. Enter the following commands one line at a time into your fastboot window. (See transcript below)
fastboot.exe devices (Just to make sure your device is connected properly.)
fastboot.exe erase system (Optional I think? I didn't use it and mine works great)
fastboot.exe flash system us_me302c-v5.0.21-jb_4.3-system.gz (Replace with your image file name if you are using a different one)
If done right it should look something like this.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe devices
1111111111111111 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe flash system us_me302c-v5.0.21-jb_4.3-system.gz
sending 'system' (771129 KB)...
OKAY [ 95.862s]
writing 'system'...
OKAY [ 74.116s]
finished. total time: 169.978s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
And guess what. You're all done…
Now just sit back and let it reboot a few times.
You are going to want to make sure you have a superuser app and enjoy…
Im not an expert but after a few weeks of hunting for it i finally found out how to do it.
Many thanks go out to everyone who worked on this for all of us, and if you found this post helpful please feel free to add some thanks.

[RECOVERY] Nabi bigtab hd 20"

TWRP recovery for Nabi Bigtab 20"
Must have unlocked bootloader​
Download:attachment below
install via adb
"adb reboot-bootloader"
"fastboot flash recovery recovery.img"
Compiled by me with help from @aicjofs

I need help getting a fastboot driver to work for this tablet. So far I've had no luck. What drivers did you use?

Just in case others have this problem and arrive here....
I recently got a Nabi Big 20 HD tablet to use as a camera viewer in a nursery at our church. The only problem was, when I turned it on, it kept giving me an error, stating that I had to hook up to the wifi, and that the FUHU servers had a problem. Essentially, since Fuhu went out of business, you can’t connect to the fuhu servers.
Since you can’t connect to the servers, setup can’t be completed, and this 20″ tablet became a 20″ paperweight. Obviously, that would not do, so I figured out how to use fastboot mode, TWRP, and the advanced file manager to delete the unneeded junk to make the tablet functional again. Below are my instructions, performed from a Linux computer. You could do this from Windows as well, if you download the right tools.
Before you begin, you will need the TWRP recovery image, which you can get from here: http://www.mediafire.com/folder/rul6liygr1rw3/Nabi_big_20_hd_tablet or from https://forum.xda-developers.com/android/development/recovery-nabi-bigtab-hd-20-t3035372
Power off the tablet.
Hold the volume up and power on buttons, and release them when you see the menu options.
NOTE: This is actually fastboot mode!
Perform an OEM unlock
[email protected]:~$ fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 13.625s]
finished. total time: 13.625s
[email protected]:~$
After this it reboots and starts up again, so power off the tablet.
Hold the volume up and power on buttons again, release them when you see the menu options.
NOTE: Once again, this is actually fastboot mode!
Flash the recovery image.
[email protected]:~/Downloads$ fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (8646 KB)...
OKAY [ 0.313s]
writing 'recovery'...
OKAY [ 0.314s]
finished. total time: 0.627s
[email protected]:~/Downloads$
From the still open menu, use the volume keys to scroll down to “recovery mode” and press the power button once to choose it. NOTE: it will show the NABI screen, then reboot into TWRP. Unfortunately, ADB does not work in this version of TWRP.
Go to “Mount” and check “System” and then click to disable MTP.
Press the home key or back key to get back to the main menu.
Click “Advanced”.
Click “file manager”.
Scroll to “priv-app” and select it.
Click on each of these items and choose to delete them:
fuhu_addapps2.apk
fuhu_appzone2.apk
fuhu_drmmanagerservice.apk
fuhu_nabiaccountmanager.apk
fuhu_nabiupdater.apk
–Personally, I just deleted all “fuhu” apps in this folder, but I think you only need those ones.
Then in the “app” folder, delete all the fuhu apps. Yes, I’m pretty sure you need to delete all of these ones.
Select the home or back button to get to the main TWRP screen.
Reboot to system.
Enjoy!
NOTE: It should start up, and may go through the Google setup (if you never started it before), and then will drop you off in “parent mode”.
At this point, I recommend installing a regular launcher, such as Trebuchet, Apex launcher, Nova launcher, etc. I used Apex launcher personally, because you can “hide” unwanted apps, and I use it to hide the unwanted Nabi apps. You should be able to see the Chrome browser in the parent mode window, use that to download the apk for the launcher you want (or use the Google account if you set up an account).
Once a launcher is installed, press the home key, and choose to always use the launcher you installed. You can now use this tablet as a regular Android tablet.
TWRP does have the option to install SuperSU and root the device. That’s completely up to you. Kingo Root also works incredibly well on this tablet. It will be stuck on Android 4.4.2, so it is a little outdated, but seems to work rather well. It was designed for gaming, so it is pretty powerful for as old as it is.
Linux – keep it simple.

AlaskaLinuxUser said:
Just in case others have this problem and arrive here....
I recently got a Nabi Big 20 HD tablet to use as a camera viewer in a nursery at our church. The only problem was, when I turned it on, it kept giving me an error, stating that I had to hook up to the wifi, and that the FUHU servers had a problem. Essentially, since Fuhu went out of business, you can’t connect to the fuhu servers.
Since you can’t connect to the servers, setup can’t be completed, and this 20″ tablet became a 20″ paperweight. Obviously, that would not do, so I figured out how to use fastboot mode, TWRP, and the advanced file manager to delete the unneeded junk to make the tablet functional again. Below are my instructions, performed from a Linux computer. You could do this from Windows as well, if you download the right tools.
Before you begin, you will need the TWRP recovery image, which you can get from here: http://www.mediafire.com/folder/rul6liygr1rw3/Nabi_big_20_hd_tablet or from https://forum.xda-developers.com/android/development/recovery-nabi-bigtab-hd-20-t3035372
Power off the tablet.
Hold the volume up and power on buttons, and release them when you see the menu options.
NOTE: This is actually fastboot mode!
Perform an OEM unlock
[email protected]:~$ fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 13.625s]
finished. total time: 13.625s
[email protected]:~$
After this it reboots and starts up again, so power off the tablet.
Hold the volume up and power on buttons again, release them when you see the menu options.
NOTE: Once again, this is actually fastboot mode!
Flash the recovery image.
[email protected]:~/Downloads$ fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (8646 KB)...
OKAY [ 0.313s]
writing 'recovery'...
OKAY [ 0.314s]
finished. total time: 0.627s
[email protected]:~/Downloads$
From the still open menu, use the volume keys to scroll down to “recovery mode” and press the power button once to choose it. NOTE: it will show the NABI screen, then reboot into TWRP. Unfortunately, ADB does not work in this version of TWRP.
Go to “Mount” and check “System” and then click to disable MTP.
Press the home key or back key to get back to the main menu.
Click “Advanced”.
Click “file manager”.
Scroll to “priv-app” and select it.
Click on each of these items and choose to delete them:
fuhu_addapps2.apk
fuhu_appzone2.apk
fuhu_drmmanagerservice.apk
fuhu_nabiaccountmanager.apk
fuhu_nabiupdater.apk
–Personally, I just deleted all “fuhu” apps in this folder, but I think you only need those ones.
Then in the “app” folder, delete all the fuhu apps. Yes, I’m pretty sure you need to delete all of these ones.
Select the home or back button to get to the main TWRP screen.
Reboot to system.
Enjoy!
NOTE: It should start up, and may go through the Google setup (if you never started it before), and then will drop you off in “parent mode”.
At this point, I recommend installing a regular launcher, such as Trebuchet, Apex launcher, Nova launcher, etc. I used Apex launcher personally, because you can “hide” unwanted apps, and I use it to hide the unwanted Nabi apps. You should be able to see the Chrome browser in the parent mode window, use that to download the apk for the launcher you want (or use the Google account if you set up an account).
Once a launcher is installed, press the home key, and choose to always use the launcher you installed. You can now use this tablet as a regular Android tablet.
TWRP does have the option to install SuperSU and root the device. That’s completely up to you. Kingo Root also works incredibly well on this tablet. It will be stuck on Android 4.4.2, so it is a little outdated, but seems to work rather well. It was designed for gaming, so it is pretty powerful for as old as it is.
Linux – keep it simple.
Click to expand...
Click to collapse
Woah, wasn't expecting to see you here.
Thanks for that guide, had one as well but had since sold it

Thanks - the guide helped me unbrick my Nabi Big Tab 20"
AlaskaLinuxUser said:
Just in case others have this problem and arrive here....
I recently got a Nabi Big 20 HD tablet to use as a camera viewer in a nursery at our church. The only problem was, when I turned it on, it kept giving me an error, stating that I had to hook up to the wifi, and that the FUHU servers had a problem. Essentially, since Fuhu went out of business, you can’t connect to the fuhu servers.
Since you can’t connect to the servers, setup can’t be completed, and this 20″ tablet became a 20″ paperweight. Obviously, that would not do, so I figured out how to use fastboot mode, TWRP, and the advanced file manager to delete the unneeded junk to make the tablet functional again. Below are my instructions, performed from a Linux computer. You could do this from Windows as well, if you download the right tools.
Before you begin, you will need the TWRP recovery image, which you can get from here: http://www.mediafire.com/folder/rul6liygr1rw3/Nabi_big_20_hd_tablet or from https://forum.xda-developers.com/android/development/recovery-nabi-bigtab-hd-20-t3035372
Power off the tablet.
Hold the volume up and power on buttons, and release them when you see the menu options.
NOTE: This is actually fastboot mode!
Perform an OEM unlock
[email protected]:~$ fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 13.625s]
finished. total time: 13.625s
[email protected]:~$
After this it reboots and starts up again, so power off the tablet.
Hold the volume up and power on buttons again, release them when you see the menu options.
NOTE: Once again, this is actually fastboot mode!
Flash the recovery image.
[email protected]:~/Downloads$ fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (8646 KB)...
OKAY [ 0.313s]
writing 'recovery'...
OKAY [ 0.314s]
finished. total time: 0.627s
[email protected]:~/Downloads$
From the still open menu, use the volume keys to scroll down to “recovery mode” and press the power button once to choose it. NOTE: it will show the NABI screen, then reboot into TWRP. Unfortunately, ADB does not work in this version of TWRP.
Go to “Mount” and check “System” and then click to disable MTP.
Press the home key or back key to get back to the main menu.
Click “Advanced”.
Click “file manager”.
Scroll to "system" and select it.
Scroll to “priv-app” and select it.
Click on each of these items and choose to delete them:
fuhu_addapps2.apk
fuhu_appzone2.apk
fuhu_drmmanagerservice.apk
fuhu_nabiaccountmanager.apk
fuhu_nabiupdater.apk
–Personally, I just deleted all “fuhu” apps in this folder, but I think you only need those ones.
Then in the “app” folder, delete all the fuhu apps. Yes, I’m pretty sure you need to delete all of these ones.
Select the home or back button to get to the main TWRP screen.
Reboot to system.
Enjoy!
NOTE: It should start up, and may go through the Google setup (if you never started it before), and then will drop you off in “parent mode”.
At this point, I recommend installing a regular launcher, such as Trebuchet, Apex launcher, Nova launcher, etc. I used Apex launcher personally, because you can “hide” unwanted apps, and I use it to hide the unwanted Nabi apps. You should be able to see the Chrome browser in the parent mode window, use that to download the apk for the launcher you want (or use the Google account if you set up an account).
Once a launcher is installed, press the home key, and choose to always use the launcher you installed. You can now use this tablet as a regular Android tablet.
TWRP does have the option to install SuperSU and root the device. That’s completely up to you. Kingo Root also works incredibly well on this tablet. It will be stuck on Android 4.4.2, so it is a little outdated, but seems to work rather well. It was designed for gaming, so it is pretty powerful for as old as it is.
Linux – keep it simple.
Click to expand...
Click to collapse
This was perfect. I could not figure out how to get this device into FastBoot until I read your post today. The only tweak I had to make I added in line above was after I went to filemanager I had to select "system" before selecting "privapp".

hexagon_founder said:
This was perfect. I could not figure out how to get this device into FastBoot until I read your post today. The only tweak I had to make I added in line above was after I went to filemanager I had to select "system" before selecting "privapp".
Click to expand...
Click to collapse
Glad it helped!
And thanks for the note, yes, priv app is under system, and I forgot to mention that! [emoji3]
Sent from my Sony Xperia XA2 Ultra with Android 10

Hi, can you explain how you got into fastboot mode, or post a video? I am holding the plus sign button and the power button, but all that happens is the Nabi Bigtab flashes a few times, then stays dimly lit. It never loads any information, nothing about fastboot. Thanks.
EDIT: I figured it out. You have to press - the negative sign and the power button, NOT the plus sign, to get to the menu where you can choose recovery mode. THAT is the fastboot menu. It wasn't clear from the instructions. Make sure the tablet is hooked up when you do this and it should display on your PC as a "Fastboot" device.

I would appreciate help, my attempts are failing on this step using the nabilab64 drivers, minimal ADB, and this command:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
BT20A00000211140829 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.015s
I am using a USB 2.0 hub and a 3.0 plug. Same results. Also tried a different PC.
Thank you.

CCrusader said:
I would appreciate help, my attempts are failing on this step using the nabilab64 drivers, minimal ADB, and this command:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
BT20A00000211140829 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.015s
I am using a USB 2.0 hub and a 3.0 plug. Same results. Also tried a different PC.
Thank you.
Click to expand...
Click to collapse
CCrusader said:
Hi, can you explain how you got into fastboot mode, or post a video? I am holding the plus sign button and the power button, but all that happens is the Nabi Bigtab flashes a few times, then stays dimly lit. It never loads any information, nothing about fastboot. Thanks.
EDIT: I figured it out. You have to press - the negative sign and the power button, NOT the plus sign, to get to the menu where you can choose recovery mode. THAT is the fastboot menu. It wasn't clear from the instructions. Make sure the tablet is hooked up when you do this and it should display on your PC as a "Fastboot" device.
Click to expand...
Click to collapse
Odd, on mine it is the positive (+ up) volume button. Maybe it varied with different year models?
As for the adb command issue with Windows, I'm not sure, I use Linux... sorry I can't be more help.
Edit: perhaps try full adb, instead of minimal version?
Sent from my Sony Xperia XA2 Ultra with Android 10

AlaskaLinuxUser said:
Odd, on mine it is the positive (+ up) volume button. Maybe it varied with different year models?
As for the adb command issue with Windows, I'm not sure, I use Linux... sorry I can't be more help.
Edit: perhaps try full adb, instead of minimal version?
Sent from my Sony Xperia XA2 Ultra with Android 10
Click to expand...
Click to collapse
I'll try it. What version of ADB were you using and where did you get yours?
What version of the Nabi driver did you use? Does Linux support it natively?
I am using Windows 10. What version of Linux were you using?
Doing this for a customer so I'd like to figure out how to get this done. This has been a bumpy process so far.
Thanks.

CCrusader said:
I'll try it. What version of ADB were you using and where did you get yours?
What version of the Nabi driver did you use? Does Linux support it natively?
I am using Windows 10. What version of Linux were you using?
Doing this for a customer so I'd like to figure out how to get this done. This has been a bumpy process so far.
Thanks.
Click to expand...
Click to collapse
I used Ubuntu 18.04, and installed adb and fastboot from the Ubuntu repository. I did not need any drivers, as Ubuntu Linux was able to talk to fastboot right out of the box. Literally, the above steps was all I did.
Not bashing Windows, but Android runs a Linux kernel, and most Linux distributions can work with it much easier than Windows.
You can download a Ubuntu live CD and install adb and fastoob on your live run to do the job, if you don't want to install Ubuntu on a computer.
Hope that helps.
Sent from my Sony Xperia XA2 Ultra with Android 10

I got ubuntu and ran it off a live USB. Had to enable the app universe in software center, then installed ABP and fastboot. It unlocked the OEM and allowed flashing like a charm. Thank you. I hope this info helps someone else out, especially the minus sign rather than the plus sign.

CCrusader said:
I got ubuntu and ran it off a live USB. Had to enable the app universe in software center, then installed ABP and fastboot. It unlocked the OEM and allowed flashing like a charm. Thank you. I hope this info helps someone else out, especially the minus sign rather than the plus sign.
Click to expand...
Click to collapse
Glad it worked out! [emoji3]
Sent from my Sony Xperia XA2 Ultra with Android 10

I cannot get my WIndows 10 pc to recognize the big tab as an adb device. It is in fastboot mode (Start, Power off, and Recover mode menu) and I have installed all proper adb and fastboot drivers as well as tried using NabiLab and Mehtuus Nabi Root to install any sort of drivers. The tablet will either appear as "Unknown USB Device (Device Descriptor Request Failed)" or as "Fastboot" with the little exclamation mark and triangle next to it.
I have also tried booting into a live linux installation and get the same issue: adb will not detect the device.
I got a 24" paper weight...

I am in the same page, just got my 24" and could not pass the update page until I mess up the entire system.
Anyone here still got the stock ROM for the 24?
I found this somewhere but not sure what it is.

crazytiger1983 said:
I am in the same page, just got my 24" and could not pass the update page until I mess up the entire system.
Anyone here still got the stock ROM for the 24?
I found this somewhere but not sure what it is.
Click to expand...
Click to collapse
I'm also looking for files for the 24" version. Did you figure out what this file was for?

I have good news and bad news.
I somehow got the ROM file but its not from NABI, its from INFOCUS.
The problem is the could not get google play work.
Maybe someone here would have better idea what is wrong with it.

crazytiger1983 said:
I have good news and bad news.
I somehow got the ROM file but its not from NABI, its from INFOCUS.
The problem is the could not get google play work.
Maybe someone here would have better idea what is wrong with it.
Click to expand...
Click to collapse
So the file you attached in your post from March is the in focus flash files?

No, this is the one

crazytiger1983 said:
No, this is the one
Click to expand...
Click to collapse
Thanks. I just recently purchased one of these and am waiting for it to arrive. I don't know what state it will be in when I receive it. So what is the file for then from back in March?

Need Serious help Rooting the K1 Nvidia Shield Tablet on Linux MInt 18

(first, If im on the wrong thread can you help with asking a moderator to move it to the correct place, or how ever that would work? Thanks!!)
Im on Linux Mint 18 Sarah Cinnamon 64 bit
I'm trying to root my Nvidia K1 shield tablet. no idea what im doing and the more I research this the more confusing it gets. Seems like If you ran windows theres "Clear Cut & Right to the Point" instructions about how to do this on about 14 hundred pages of great info including great you tube videos which heavily explain it, in great easy to understand detail.
What Ive done so far.
installed ADB and BootLoader (but ive no idea how to actually use these programs yet, still figuring that one out)
I have sucessfully Unlocked the Device
Now im trying to flash the .img I hit this command (from terminal) and get this result
$ fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.658s]
writing 'recovery'...
OKAY [ 0.651s]
finished. total time: 1.309s
Now following these steps at this website http://developer.download.nvidia.co.../0_0_0_Factory/HowTo-Flash-Recovery-Image.txt
im on the:
$ fastboot flash boot boot.img
error: cannot load 'boot.img'
Now ive no idea what to do, how to fix this ,or even if im following the right directions. what I need is (im going to throw a nice Trump statement here)
Can someone explain how you root a Nvidia shield K1 tablet, start to finish, ON LINUX, and every step simplified along the way explained, PERIOD!!!!
Everyone starts to tell you how to do this, then they jump on a windows PC throwing me all off...
now my .img file is from this website https://www.androidfilehost.com/?fid=24269982087005399
its in my downloads folder if that matters??? Not sure but i think it does. If i need to move this .img file somewhere please explain how to do it, don't just say "oh your problem is you need to move it to /usb/local/ or something," and just leave it there. remember i need help, so if I need to move things and use commands please help me with that. thank you
You know I got my MCSE, MCSA, A+ SERVER+ NET+ NOVEL and I can write python Programs and im getting into Julia. I know DOS, & I feel im a power User on Andriod, and ive been using personal computers since the 1970's. But when it comes to linux, I cant even google my way out of anything, even if the problem is very minor and simple, still, I cant google my way out of anything on linux its crazy. I keep having to write on forums on threads to find the answer. Someone with my Creds, granted most were aquired in 2002, shouldnt struggle like I do with linux, the support is terrible, and I dont mean updates for software and hardware, im sure thats fine. But when it comes to user support and the documentation for instruction, you get pages of results that have more links then answers on the page to other peoples help pages, that link more to other pages. You cant just goto 1 page, get the answer, done finished your allset, NOPE LINUX does not work that way and its to bad, I see why most of the world doesn't use it.
Good analogy right here, if someone in your neighborhood is giving out free gold to anyone, you know ya whole villiage or town is going to be there getting free gold, ya well, if Linux was that good, the whole world would be using it, and there not, and its free just like the gold. So does that tell you anything?

settled that, smashed the tablet, going to mount it on my wall as a reminder for tech not to mess with me. and yes linux sucks balls!!!!

Maverick617 said:
settled that, smashed the tablet, going to mount it on my wall as a reminder for tech not to mess with me. and yes linux sucks balls!!!!
Click to expand...
Click to collapse
I suggest anger management and growing some sort of ability to wait periods of time before going all hulk smash... You waited all of 2 hours for someone to tell you you had already finished all you needed a pc for... After flashing the twrp recovery over adb all you needed to do was boot into it. you could have done so by shutting it off then holding vol down and power to get you to the fastboot menu then use the volume rockers to go to recovery the power button will be enter in this case and it should boot the recovery you just loaded.
From there you flash the super su binary you already downloaded and when you boot into the tablet after that you can load a apk from the google play store supersu is what i use then you are rooted...

mirrin said:
I suggest anger management and growing some sort of ability to wait periods of time before going all hulk smash... You waited all of 2 hours for someone to tell you you had already finished all you needed a pc for... After flashing the twrp recovery over adb all you needed to do was boot into it. you could have done so by shutting it off then holding vol down and power to get you to the fastboot menu then use the volume rockers to go to recovery the power button will be enter in this case and it should boot the recovery you just loaded.
From there you flash the super su binary you already downloaded and when you boot into the tablet after that you can load a apk from the google play store supersu is what i use then you are rooted...
Click to expand...
Click to collapse
Also just going to add the process is the same in mint/ubuntu as it is in windows. Getting fastboot/adb is the only difference, and it basically tells you how to do if you try using fastboot without it installed. Also make sure you are in the right directory and type the correct name or you get the cant load message.

Additionally as someone who had to learn linux cli on Red hat i would have to say vs ms dos about the same... if the op thinks mint is bad i have some old yellow dog and mandrake 7.0 disk i can send him. He does not know the pain of trying to find the drivers on repositories and such just to get the sound and Ethernet working... Had the issue of my realtek 10/100 card not working under linux but my 3com card would if i had preloaded the drivers...
I have tried unbuntu and mint both gave a very similar experience to installing windows. With the exception unlike windows i did not need to patch 1000 things before using it and everything just worked.
Also Android is linux...
SHIELD TABLET K1 RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method: (If you had done this after the part you loaded what ever recovery nvidia tried pushing on you it should have worked)
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
(I dont even know what this from nvidia is talking about)http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172 <--go to the xda first next time...
To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata
fastboot flash staging blob
(Better instructions that i found on this place)
https://twrp.me/devices/nvidiahshieldtablet.html
adb reboot bootloader
(https://dl.twrp.me/shieldtablet/) Download latest here rename the .img file twrp.img maesure the file is in the adb folder...
fastboot flash recovery twrp.img
fastboot reboot
After boot you can issue this command
adb rebooot recovery
or
shut off the tablet
hold vol down then hold power
then press vol down until recovery is highlighted then push power button...
Unlocking the Bootloader<you needed to do this first>
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
Click to expand...
Click to collapse

Screwed hoping so kind person can help

Okay so I recognize if I had more money I could pay for home internet. But I don't so I'm here with a budget phone, less than ideal tech skills, and can't seem to figure out how to root.
I've borrowed multiple windows 10 computers all the same result.
I've installed the latest Adb drivers from multiple sources. Re-installed drivers. Uninstalled drivers to no avail
I have my bootloader unlocked. I downloaded the latest firmware. I extracted it and patched the boot.img.
whenever I type fastboot flash boot magisk_patched.img this is the result
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
when in fastboot mode i see on my phone
device state: unlocked
boot slot:b
Hoping someone can help Life is frustrating without internet.

Jmcarls20 said:
Okay so I recognize if I had more money I could pay for home internet. But I don't so I'm here with a budget phone, less than ideal tech skills, and can't seem to figure out how to root.
I've borrowed multiple windows 10 computers all the same result.
I've installed the latest Adb drivers from multiple sources. Re-installed drivers. Uninstalled drivers to no avail
I have my bootloader unlocked. I downloaded the latest firmware. I extracted it and patched the boot.img.
whenever I type fastboot flash boot magisk_patched.img this is the result
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
when in fastboot mode i see on my phone
device state: unlocked
boot slot:b
Hoping someone can help Life is frustrating without internet.
Click to expand...
Click to collapse
Just a tip, if you're in dire need of a computer, I'd recommend a raspberry pi. It's really handy for your situation. I also don't have home internet and was using purely a Pi for a fair while, it's definitely enough for adb/fastboot stuffs among other things.
Now, onto your issue. Have you tried specifying the boot slot? Normally you shouldn't have to specify the slot but in your case you may have to.
You can try running the command
Code:
fastboot flash boot_b magisk_patched.img
Also, verify that the magisk_patched.img is in the directory you started the terminal/PowerShell window in with the adb executable.
Sent from my Pixel 3a XL using XDA Labs

can you flash anything else in fastboot? or are you only trying to flash the patched magisk image?

I've attached the latest platform tools from Google.
Unzip this folder to the root of your C:/ so it looks like this: C:/adb
Put your magisk_patched.img in the folder then shift+right click anywhere in the folder and "open command prompt here".
With your phone in bootloader mode, at the prompt type: fastboot flash boot magisk_patched.img
I've just done this to check and mine worked first time . Let me know how you get on .

Is the modified magisk file in the same directory as the SDK tools?
I do not recommend that you start using "boot partition" specific commands. You should not have to specify which boot partition to write to. If it's not working that is an indication of a larger issue that needs to be resolved. I've seen plenty of people make things worse when they start using boot partition specific commands.

Wow thank you for the support. I got it to flash by boot_b but then I tried to reboot and the touch screen didn't work so I reflashed the original boot.img and then redid the boot file today and will try it tonight. Will keep everyone posted and will re try other solutions tonight. Going to have to look into raspberry pi to that sounds like a nice project to try