Fuhu Nabi General information
1. Introduction
It was only recently that the Nabi2 got it's own forum. This device has been out a couple of years so the information you may be looking for is spread all over XDA. The largest single chunk of information resides in the Nabi 2 Root and Gapps Install by jmz, the problem is that thread is now 265 plus pages and mostly impossible to search. What I find more troubling is that the methods in which we go about root, modding etc evolve over time and newer users are using methods and tools that are now obsolete and can create more issues then they solve. Also while the moderators have done a wonderful job, not every Nabi thread is here in this section of the forum so I wanted to link to those that are pertinent.
While this is a Nabi2 forum I personally find it a better use of this corner of XDA to discuss all Nabi products, and this information post will discuss them all. Nabi JR, Nabi 2 Original, Disney and Nick, Nabi XD, Nabi2S, Nabi Dreamtab(Intel and Nvidia) , Nabi BigTab 20" and 24".
Most of the discussion will be catering to Microsoft Windows users as it is the most common usage scenario. It also will be light on discussion of the Intel version of the Dreamtab as it quite different.
Also look at the wiki. Information is very dated but there is some useful stuff, be careful with what you are flashing as the wiki is more informational then current methods. I would recommend asking before using any of the scripts or programs. http://forum.xda-developers.com/wiki/Fuhu_nabi_2
2.Basics
With the exception of the Nabi Dreamtab by Intel (DMTAB-IN08A), all the Fuhu Nabi products are built on Nvidia Tegra2, Tegra3, or Tegra 4. Therefore most methods of modding, recovery, etc are similar with a few device specific difference. The main utility we use is a custom recovery called TWRP, if you have come from other devices you might have used CWM, Odin, and countless other utilities, TWRP will be accomplishing the tasks on the Nabi devices. All the Nabi's already have a "stock" recovery on the device. It is useful for taking OTA(updates) and factory resetting but it's limitations end there, and this is where the TWRP custom recovery will come in to play.
There are 4 modes of operation for Nabi's
Each mode offers different usage scenarios and you should familiar with what they look like and which one you are in.
-Android
-Recovery -
-Bootloader/Fastboot
-Forced recovery/nvflash/APX
Windows are driver can be a pain but necessary before you can do anything else
No matter which method you choose or need to use the Windows drivers must be installed on your computer before you can do anything, without getting that setup nothing else is going to matter.
Most mods, rooting, and recovering devices and are done by one of 2 methods.
-Tool/Script - This is usually done by a GUI/Command prompt tool where the user clicks a few buttons and the magic happens in the background
-Manually - This is getting the hands dirty method, typing command lines, moving and unzipping files and is unfortunately common as there aren't many of the tools/scripts mentioned above.
3. The 4 Operational Modes
1. Android Usage: ADB and File Transfer.
-The normal operational mode for the device, and why you bought the tablet. ADB is NOT enabled by default, you will need to turn it on to perform any ADB operations. To enable ADB on the device:
-Login to parent mode
-Open Settings and see if "Developer Options" is listed if not
------Go to "About tablet".
------Click on Builder Number 10 or so times.
------Eventually you will see developer options are enabled.
-Open Developer Options and turn them on in top right corner
-Check the box USB debugging
-When using ADB on newer software builds when you execute a command the first time you will need to authorize on the tablet the first time, you can prevent this pop up by checking the box to always trust your computer.
2. Bootloader Usage: Fastboot. Booting to recovery. Booting to nvflash. Installing TWRP or stock recoveries.
Allows selection of other 3 modes, and utilizing fastboot commands.
How to enter bootloader/fastboot mode:
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line: adb reboot-bootloader
3. Recovery Usage: ADB, File Transfer, Installing Mods and Root, Recovering backups, Recovering Device.
There are 2 different versions of recovery. "Stock" and "TWRP". Stock is what comes with your device, and can be identified by the "dead android" picture when it boots up. Stock recovery is rather limited so if you see the "dead android" know you have stock recovery on the device. The 2nd possible recovery is TWRP, and the one used for most things you will be doing. It should say Team Win Recovery Project, or TWRP when it boots up.
How to enter recovery mode:
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen.
-Use the vol + and - keys to select recovery kernel. (one key will highlight the selection and the other key will "select" what's highlighted)
Device powered on:
-Use ADB and execute from the command line: adb reboot recovery
4. Forced Recovery Usage: Last resort for recovering dead tablet, heavy duty modding.
Rarely used. Can modify tablet, and prevent bricks. Only useful on Nabi2 Original, Disney, and Nick.
How to enter forced recovery mode:
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen.
-Use the vol + and - keys to select forced recovery. (one key will highlight the selection and the other key will "select" what's highlighted)
-screen will be completely blank, you will also need a windows APX driver to communicate with device.
4. Drivers
The windows drivers are problematic. There can be conflicts with other drivers, or just not found for the Nabi, or 64bit driver signature enforcement. As previously mentioned to utilize almost any operation for modding/rooting etc. you must have the drivers installed. None of the manual methods or auto tools are going to work if you don't get this accomplished.
It most cases you will only need 2 drivers. ADB interface and Fastboot/Bootloader Interface. The 3rd will only be needed on the rare chance you need to use the APX interface. What is important to understand is your computer will only see the interface that is used depending on the "Operational Mode" the tablet is in. For example if you are in Android or Recovery your computer will see ADB interface but NOT the fastboot interface. If you are in the bootloader interface(and have selected fastboot protocol) you will see the fastboot interface and NOT the ADB interface. So to install both drivers, you will have to boot to Android or Recovery and install one driver and then the bootloader to install the other. The order in which you do this will depend on which operational modes are available to you depending on the health of the tablet. (The same would apply if you need to use Forced recovery, you will need to be in that mode to install the 3rd driver APX interface, again this is rare)
Device Manger is the best way to see what is happening. With your tablet plugged in to the computer open device manager and look for either yellow ! or ? or something under the tree for "Android Device". If you are seeing the yellow ! or ? for your device then likely the drivers are not installed.
There are a few drivers and methods that seem to work best for most users. One of the bigger issues is 64bit driver signature enforcement. Windows Vista,7,8, and 10 do not like to install drivers that aren't digitally signed. There are 3 drivers that I am going to recommend. 2 are digitally signed drivers and there other is not.
PDAnet: I really don't like recommending this but it seems to work in most scenarios. Remember your tablet will have to enter both modes to install both drivers and remember that ADB will not show up by default in Android unless you enable it(see the operational mode section above)
http://pdanet.co/a/
NabiLab drivers: These are digitally self signed by me. That will require rootCA to be installed. This could create a security risk if someone was to steal my signing key. If that worries you don't use them or uninstall the drivers and certificate when you are done.
http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
Universal naked:
If you aren't technically savvy I would use these as last resort. It will require you to disable "windows driver signature enforcement"(google it because it depends on windows version). Extract the zip package. Enter device manager and find your device, and manually update driver by pointing to the folder you extracted the zip.
http://forum.xda-developers.com/showthread.php?t=2263822
5. Tools and Automated scripts.
There aren't a lot of current tools available. They have mostly aged beyond their usefulness. The reasons are quite a few.
1. As the Nabi's upgrades the Android software from Ice Cream Sandwich to Jellybean to KitKat, the bootloader also changes. This changes how TWRP is able to see the internal storage and usually it can't. An Ice Cream Sandwich bootloader needs to use a TWRP for that version. For example the original Nabi2 has 3 different TWRP versions for the 3 different bootloaders. A lot of the older tools were made with a TWRP that no longer will work with your device. This will show up as TWRP "unable to mount" errors, and therefore the tool/script will fail for that reason.
2. Gapps. Originally many Nabi devices didn't have a Google Play store option. A lot of the tools still work on that premise, but most Nabi's have Google Play now. Google Apps also change with the Android version. So the tools can make mods based on that old information will cause problems.
3. Super user. A lot of older tools with "root" scripts don't have a current super user(root) binary and daemon. Newer Android version need a more up to date Super User install. With this situation you won't cause as many problems but will not good root with the script like you expect.
I will try to keep the list somewhat up to date
4. Mods. Like above, the mods that change your screen and/or add functionality, are heavily dependent on your android version, and will usually make your tablet un bootable if using an incompatible one.
Taking that in to account it's important to realize using old tools will cause you more issues then using no tools at all. I will try to keep the list some what up to date but in general there aren't many still usable tools.
The only tool that is even somewhat current is NabiLabGUI 2015, it can deal with quite a few of the Nabi products, and is at least very good at troubleshooting and has a command line setup that you can use to follow other users command line suggestions.
Get it here. http://nabtabhacks.com/nabilabgui2015/publish.htm
Here is the thread for the OLD version of the program. http://forum.xda-developers.com/showthread.php?t=2391449
Remember none of these are going to work if you haven't set up the drivers
Nabi2 Original/Disney/Nick
Old software not to use: jmzroot package, Ubuntu install from scratch, original NabiLab(non GUI version), and most others.
Really just stick with NabiLab2015 if you need a automated solution.
NabiXD
The XD hasn't changed much so this probably still will work http://forum.xda-developers.com/showthread.php?t=2207499
Nabi JR
For the Tegra2 4GB NABI-NV5A(couple years old) NabiLab2015 can do some functions or this tool http://forum.xda-developers.com/showthread.php?t=2200119
For the Tegra3 16GB NABI-NV5B(also a couple years old) NabiLab2015 can do some functions.
For the newest NabiJR SNBJR-MT5C - Not much, no TWRP even available yet.
Nabi DreamTab Nvidia Edition
Latest installer http://forum.xda-developers.com/showpost.php?p=63151136&postcount=46
Nabi BigTabs
None
Nabi 2S(newer Nabi 2 tablet)
None
If the tools aren't working your are going to need to do it by hand. See next section.
6. Setting up to do it by hand
Remember none of this is going to work if you haven't set up the drivers. Putting it all together now, also recall that you must be in the right "Operational Mode" to use either fastboot or to use ADB.
First of all I should mention that NabiLabGUI2015 has an option to work from the command line and has a lot of this already setup but to start from scratch:
When you setup the drivers earlier you got a driver for ADB and a driver for fastboot. Now to then talk to those interfaces you will need software to do that. Specifically an ADB.exe and fastboot.exe.
-Download and install this package(pay attention to where you install this as you will likely need to put files in there later): http://forum.xda-developers.com/showthread.php?t=2317790
-From your start menu select "Minimal ADB and Fastboot" this should open a command prompt where you can type commands
-If you didn't pay attention or forgot where you installed the files, at the command prompt that opens type "explorer ." The period is important, explorer <space bar> and a period. So type what is between the quotes.
Now you can drop and drag, unzip, etc the files you need in to that folder. You are done with manual setup.
For nvflash setup(Only for Nabi2 Orig, Nick, Disney NOT 2S, this step won't normally ever be required, and is only here for completeness)
-Download the nvflash.zip attached to this post.
-Make a new folder in the same folder as above and call it nvflash
-Extract the contents of the nvflash.zip in to the nvflash folder
-At the command prompt type "cd nvflash" to change in to the folder and use nvflash
THIS IS STILL A WORK IN PROGRESS
7. Getting TWRP on the device
The most common form of using TWRP is to install to the recovery partition of your device. Remember on certain devices(Nabi2 for example) the version of TWRP you use has to match the bootloader on the device, and the bootloader "type" will almost always correlate to the version of Android you are/were using. So if your Android ROM is Kitkat, the bootloader will be KitKat and you should use the KitKat TWRP. There are various tools linked above in the tools and scripts section that can install TWRP automatically depending on device or you can also use "dd" from Android to install it. In this section the manual method of installing will be highlighted.
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
On some device the bootloader is "locked", without unlocking the bootloader TWRP cannot be loaded. Unlocking the bootloader will erase ALL personal data on the device. If you see a message like this when trying to load TWRP:
downloading 'recovery.img'...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.003s
You will need to unlock the bootloader with following command
Code:
fastboot oem unlock
OR
Code:
fastboot -i 0x0489 oem unlock
8. TWRP List and Downloads
Latest TWRP Recovery for all Nabi devices, download links, and discussion threads.
*Updated as of 04/19/2018*
Also see my AFH account https://androidfilehost.com/?w=files&flid=41986
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
Code:
[U][B]Nabi2 Disney and Nick (NABI-NV7A-D or NABI-NV7A-N)[/B][/U]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
Code:
[U][B]Nabi2S (SNB02-NV7A)[/B][/U]
KitKat TWRP 2.7.1[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3148865&d=1423018617"] Download[/URL]
Code:
[B][U]Nabi JR A (Tegra2 4GB, NV5A)[/U][/B]
TWRP 2.6.3[URL="https://androidfilehost.com/user/?w=settings-dev-files&flid=44896"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2200119"] Link[/URL]
Code:
[B][U]Nabi JR B (Tegra3 16 NV5B)[/U][/B]
TWRP 2.6.3[URL="https://androidfilehost.com/user/?w=settings-dev-files&flid=44897"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2391468"] Link[/URL]
Code:
[B][U]Nabi JR New (SNBJR-MT5C)[/U][/B]
None - Work in progess
Code:
[B][U]Nabi XD (NV10A)[/U][/B]
TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3171414&d=1424242604"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2207459"] Link[/URL]
Code:
[B][U]Nabi Dreamtab Nvidia NV08B[/U][/B]
TWRP 3.0.0[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3692992&d=1458705735"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917"] Link[/URL]
Code:
[B][U]Nabi Dreamtab Intel IN08A[/U][/B]
Tethered CWM recovery see here: [URL="http://forum.xda-developers.com/showpost.php?p=57825022&postcount=25"]Link[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917"] Link[/URL]
EDIT 11/5/2019 Might be a recovery download mirror Download
Discussion Thread Link[/CODE]
Code:
[B][U]Nabi BigTab NV24A[/U][/B]
No TWRP - Working in progress, the TWRP for the NV20A 20" BigTab can bring up ADB
Discussion Thread [URL="https://forum.xda-developers.com/nabi-2/general/nabi-nabi-se-discussion-thread-t3770816"] Link[/URL]
Code:
[B][U]Nabi SE[/U][/B]
TWRP 3.0.2 [URL="https://github.com/huckleberrypie/device_Mattel_NabiSE/releases"] Downlaod[/URL]
Discussion Thread [URL="https://forum.xda-developers.com/nabi-2/general/nabi-nabi-se-discussion-thread-t3770816"] Link[/URL]
9. Recovering Bricked Devices
In this section we will go over recovery from non booting devices. I would classify non booting as one of three situations.
1) Tablet is being used normally and one day it has crashed or when restarted sits at the bootamination(spinning Nabi logo, Dreamworks characters)
If you haven't been doing anything but using the tablet normally then the most likely culprit is that some file is corrupt on the data partition. While there are ways to replace just that file if you suspect which one it is the simple solution is to try and wipe the data partition and start fresh. There are two ways to accomplish this:
a) Use the stock recovery if you haven't installed TWRP or haven't unlocked the bootloader. Boot the stock recovery using "recovery" in Section 3 above. Press both vol+ and vol - and the same time and you should get a menu where you can select to factory reset. This wipes ALL data from the tablet. When complete try to boot the tablet.
b) Use TWRP recovery from section 7 above. TWRP will give you some flexibility in that you can back up the data partition before you wipe it(in case the issue wasn't actually the data partition you can restore the data back), and TWRP will not delete "internal storage" if you do a factory reset.
-Boot TWRP
-<optional> Backup data partition to EXTERNAL sdcard(be safe and back up to external card not internal)
-<optional> While connected to computer backup the remaining files on the "internal sd" with windows explorer(Device should show up as an MTP device on later TWRP versions)
-Select Wipe tab and factory reset
2) You have installed a mod, installed a root application that has made a system modification, installed a zip file, or were just playing around swiping and wiping things in TWRP. Sometimes this will appear the same as above with a bootloop and boot animation that goes on forever.
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Backup tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
10. ROM List and Downloads
Also see my AFH account https://androidfilehost.com/?w=files&flid=41986
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
KitKat 3.0.13 ROM[URL="https://www.androidfilehost.com/?fid=24052804347843199"] Download[/URL]
ROM Mirror [URL="http://www.nabtabhacks.com/downloads/3013stock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087011778"] Download[/URL]
Code:
[U][B]Nabi2 Disney(NABI-NV7A-D)[/B][/U]
KitKat 3.0.4 ROM[URL="https://www.androidfilehost.com/?fid=24052804347843201"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/304D.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087011793"] Download[/URL]
Code:
[U][B]Nabi2 Nick (NABI-NV7A-N)[/B][/U]
KitKat 3.0.5 ROM[URL="https://www.androidfilehost.com/?fid=24052804347843202"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/305N.zip"] Download[/URL]
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
Code:
[U][B]Nabi2S (SNB02-NV7A)[/B][/U]
KitKat 2.0.141107[URL="https://www.androidfilehost.com/?fid=24052804347850076"] Download[/URL]
Mirror[URL="http://www.nabtabhacks.com/downloads/2_0_141107stock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087011808"] Download[/URL]
Code:
[B][U]Nabi JR A (Tegra2 4GB, NV5A)[/U][/B]
Latest Stock ROM[URL="https://www.androidfilehost.com/?fid=24052804347850083"] Download[/URL]
Mirror [URL="http://www.nabtabhacks.com/downloads/njr1stBACKUP.rar"] Download[/URL]
Bootloader: None
Code:
[B][U]Nabi JR B (Tegra3 16 NV5B)[/U][/B]
Latest Stock ROM[URL="https://www.androidfilehost.com/?fid=24052804347850077"] Download[/URL]
Mirror [URL="http://www.nabtabhacks.com/downloads/JRB.zip"] Download[/URL]
Bootloader: None
Code:
[B][U]Nabi JR New (SNBJR-MT5C)[/U][/B]
None - Work in progess
Code:
[B][U]Nabi XD (NV10A)[/U][/B]
EDIT 11/5/2019 ROM Mirror[URL="https://androidfilehost.com/?fid=24269982087013990"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2207459"] Link[/URL]
Bootloader: None
Code:
[B][U]Nabi Dreamtab Nvidia NV08B[/U][/B]
1312 ROM[URL="https://www.androidfilehost.com/?fid=24269982087013911"] Download[/URL]
ROM mirror [URL="http://www.nabtabhacks.com/downloads/1312stock.zip"] Download[/URL]
Bootloader[URL="https://www.androidfilehost.com/?fid=24269982087013988"] Download[/URL]
Code:
[B][U]Nabi Dreamtab Intel IN08A[/U][/B]
EDIT 11/5/2019 from some files I found.
Maybe a ROM backup [URL="https://www.androidfilehost.com/?fid=24533100289589801"] Download [/URL]
[STRIKE]Tethered CWM recovery see here: [URL="http://forum.xda-developers.com/showpost.php?p=57825022&postcount=25"]Link[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917"] Link[/URL]
Code:
[B][U]Nabi BigTab NV20A[/U][/B]
TWRP 2.8.1 [URL="https://www.dropbox.com/s/p1gh6oo34sgbwri/recovery.img?dl=0"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/android/help/24-tab-hd-powered-nabi-rooting-t2932197"] Link[/URL]
Code:
[B][U]Nabi BigTab NV24A[/U][/B]
No TWRP - Working in progress, the TWRP for the NV20A 20" BigTab can bring up ADB
Discussion Thread [URL="http://forum.xda-developers.com/android/help/24-tab-hd-powered-nabi-rooting-t2932197"] Link[/URL]
[/STRIKE]
One last post for misc and other
nabi dream tab
hello I have a nabi dream tab that dead and wont boot i follow thw instruction in the forums and re install the stock rom
and boot loader. everything was successful but the tablet still wont boot up its stuck on powered by android
any advice please
Suck4 said:
hello I have a nabi dream tab that dead and wont boot i follow thw instruction in the forums and re install the stock rom
and boot loader. everything was successful but the tablet still wont boot up its stuck on powered by android
any advice please
Click to expand...
Click to collapse
Which ROM did you reinstall? What version 1.3.7, 1.3.12? Have you tried doing a tablet wipe/factory reset?(obviously you will lose everything on the tablet)
Nabi dream tab
aicjofs said:
Which ROM did you reinstall? What version 1.3.7, 1.3.12? Have you tried doing a tablet wipe/factory reset?(obviously you will lose everything on the tablet)
Click to expand...
Click to collapse
I tried both the 1.3.7 and 1.1.12 with boot loader 137 and still no success..
Before I did all that reading and trying I first tried the factory reset but the tablet still didnt boot so i went on to use the twrp tool and follow the instruction here in the forums but still no luck..
I also did some further research and from what i understand it appears that the firmware is what i need to flash so i open up the tablet and try to use the board id and processor type to find it but no luck.. (not sure if i needed to do that but since the twrp didnt work i tried another method) its the dream tab NVO8B..
t
All very nice, but will there ever be tips for doing this stuff on Linux? We do not run MSWin in our household. Granted, it will probably be a few months before I once again try rooting/flashing the Nabi2S, so there's time for the Linux methods to come out if they ever do.
Suck4 said:
I tried both the 1.3.7 and 1.1.12 with boot loader 137 and still no success..
Before I did all that reading and trying I first tried the factory reset but the tablet still didnt boot so i went on to use the twrp tool and follow the instruction here in the forums but still no luck..
I also did some further research and from what i understand it appears that the firmware is what i need to flash so i open up the tablet and try to use the board id and processor type to find it but no luck.. (not sure if i needed to do that but since the twrp didnt work i tried another method) its the dream tab NVO8B..
t
Click to expand...
Click to collapse
I'd be interested if it helped to format system and data in TWRP before the restore next time.
jelabarre59 said:
All very nice, but will there ever be tips for doing this stuff on Linux? We do not run MSWin in our household. Granted, it will probably be a few months before I once again try rooting/flashing the Nabi2S, so there's time for the Linux methods to come out if they ever do.
Click to expand...
Click to collapse
Most of the time the commandine stuff is still the same when it comes to fastboot or adb. A lot of the scripts are easy to modify for linux.
Android keeps restoring all apps
I've got the NabiLab 2015gui, wiped and restored the Nabi2 to 3.0.13, installed twrp through it. I've flashed to the MinimalNabiWipe.zip, and rebooted and it goes right back to please wait while android updates 117 apps. I also can't get it to accept the changes recommended at trendblog.net/fix-kitkat-sd-card-write-restriction/ (which I had found while reading through 50+ of the most recent pages in the Nabi 2 Root and Gapps Install thread, it throws a generic error that it couldn't save. Any ideas?
damfn said:
I've flashed to the MinimalNabiWipe.zip, and rebooted and it goes right back to please wait while android updates 117 apps.
Click to expand...
Click to collapse
I would check to see if you have .odex files that are orphaned. If minimalnabiwipe.zip deleted the .apk and leaves behind the associated .odex file what you describee will happen.
damfn said:
I also can't get it to accept the changes recommended at trendblog.net/fix-kitkat-sd-card-write-restriction/ (which I had found while reading through 50+ of the most recent pages in the Nabi 2 Root and Gapps Install thread, it throws a generic error that it couldn't save. Any ideas?
Click to expand...
Click to collapse
Make sure /system is mounted read AND write?
aicjofs said:
I would check to see if you have .odex files that are orphaned. If minimalnabiwipe.zip deleted the .apk and leaves behind the associated .odex file what you describee will happen.
Click to expand...
Click to collapse
Can you point me in the direction of the .odex file locations? As I did a look around all the folders I could find in twrp and couldn't find .odex.
aicjofs said:
Make sure /system is mounted read AND write?
Click to expand...
Click to collapse
You are correct, I ended up removing "es file manager" and installing "total commander file manager" as it would do it for me.
hi all
I appreciate the awesome write up to help get this done.
I am having trouble, though. I am going thru nabilabgui. I get as far as rebooting below and then nothing happens when I hit a key. It appears that the nabi also freezes on reboot. Not sure what is going on. I tried going thru the manual method and seem to be confused.
Anyway, I would be happy to provide more details to help with this. Any help is appreciated, thank you.
******** Install Recovery and Root for JB and KK ********
Make sure device is connected and detected. Press any key.
Press any key to continue . . .
# Rebooting device
# If stuck here drivers are not installed
< waiting for device >
sending 'recovery' (8176 KB)...
OKAY [ 2.115s]
writing 'recovery'...
Press any key to continue . . .
OKAY [ 1.571s]
finished. total time: 3.686s
Press any key to continue . . .
# If writing recovery OKAY is stated above
# Press VOL - button on device until bootloader is selected
# Push VOL + to select.
# Press VOL - button on device until recovery kernel is selected
# Push VOL + to select.
# Press enter when you see TWRP has booted
Press any key to continue . . .
Press any key to continue . . .
# Pushing root to your device
# Ignore external SD card error if you have none installed
# This will take a few minutes. Wait.
mount: mounting /external_sdcard on vfat failed: No such file or directory
5580 KB/s (4017098 bytes in 0.703s)
0 KB/s (25 bytes in 1.000s)
# Rebooting recovery to flash gapps and root rom.
# Please wait until backup and install has been completed
# Once it has completed hit enter
Press any key to continue . . .
aeneas3 said:
hi all
I appreciate the awesome write up to help get this done.
I am having trouble, though. I am going thru nabilabgui. I get as far as rebooting below and then nothing happens when I hit a key. It appears that the nabi also freezes on reboot. Not sure what is going on. I tried going thru the manual method and seem to be confused.
Anyway, I would be happy to provide more details to help with this. Any help is appreciated, thank you.
******** Install Recovery and Root for JB and KK ********
Make sure device is connected and detected. Press any key.
Press any key to continue . . .
# Rebooting device
# If stuck here drivers are not installed
< waiting for device >
sending 'recovery' (8176 KB)...
OKAY [ 2.115s]
writing 'recovery'...
Press any key to continue . . .
OKAY [ 1.571s]
finished. total time: 3.686s
Press any key to continue . . .
# If writing recovery OKAY is stated above
# Press VOL - button on device until bootloader is selected
# Push VOL + to select.
# Press VOL - button on device until recovery kernel is selected
# Push VOL + to select.
# Press enter when you see TWRP has booted
Press any key to continue . . .
Press any key to continue . . .
# Pushing root to your device
# Ignore external SD card error if you have none installed
# This will take a few minutes. Wait.
mount: mounting /external_sdcard on vfat failed: No such file or directory
5580 KB/s (4017098 bytes in 0.703s)
0 KB/s (25 bytes in 1.000s)
# Rebooting recovery to flash gapps and root rom.
# Please wait until backup and install has been completed
# Once it has completed hit enter
Press any key to continue . . .
Click to expand...
Click to collapse
You don't mention what device you have? I'm guessing Nabi2 of some sort, which particular model? Judging by the log it seemed to have written recovery, at which point is it hanging? The way I had to write it as windows app and emulating a command window(so if I ever stopped updating the GUI program someone could edit the batch files on the backend to do what they needed) I couldn't find a good way to end the script very gracefully(I'm not very strong at that language), but it looks like it finished normally.
aicjofs said:
You don't mention what device you have? I'm guessing Nabi2 of some sort, which particular model? Judging by the log it seemed to have written recovery, at which point is it hanging? The way I had to write it as windows app and emulating a command window(so if I ever stopped updating the GUI program someone could edit the batch files on the backend to do what they needed) I couldn't find a good way to end the script very gracefully(I'm not very strong at that language), but it looks like it finished normally.
Click to expand...
Click to collapse
sorry, nabi 2. thanks! so the next step would be flashing a rom?
It hangs at the end of the text there.
"# Rebooting recovery to flash gapps and root rom.
# Please wait until backup and install has been completed
# Once it has completed hit enter
Press any key to continue . . .'
Thank you. And the program is awesome, no need for apologies about how it ends!
i try restore to stock my nabi XD
i try flash nabi XD with rom stock, 15stock.zip in twrp and faild and to restore as backup, It is restored only well and stays in the logo.
help
my whatsapp +18097191879:crying::crying::crying::crying:
sergioagilp said:
i try flash nabi XD with rom stock, 15stock.zip in twrp and faild and to restore as backup, It is restored only well and stays in the logo.
help
my whatsapp +18097191879:crying::crying::crying::crying:
Click to expand...
Click to collapse
Are you trying to flash("install") the zip or extract the zip(system.win, etc) and restore? I'm not sure which part is failing for you. Which TWRP version?
Did you also do a factory reset after the flash?
Any one have scatter file I'm in twrp but it cannot mount any thing it says internal disc as zero I need to format it but cannot as Windows does not see it so if I use a scatter file try and flash it so flash tools
Any chance there will support for the Nabi Jr (new) soon? I made mistake of buying 2 from Amazon on t assumption that they were completely "hackable".
LOG IN Issue: It's Nabi 2 Demo Device I guess
Dear XDA friends,
This is Zeeshan from Pakistan. Few days back I purchased a used*Nabi 2 from*the local market here in Pakistan. The salesman gave this password to enter*into*the mommy/daddy mode "zxcv6789" which was working perfectly fine.
Then I thought of creating my own nabi account to enhance my daughter's Nabi experience. I registered through my own email ID,*which have*been working fine . However lately I decided to factory reset the Nabi 2 to improve its speed and performance, here is where I have been stuck from last so many days.
After the hard factory reset the tablet did not ask for setting up my Nabi account but it automatically logged in to the nabi mode and now when I try to login into to the mommy mode it says your password is incorrect, when I click on the forgot password link it says "An email has been sent to you. Please allow a few minutes for* delivery. ([email protected])" which seems to be nabi's own email ID and I am in a doubt that this device could be a store demo unit however when I purchased and before the factory reset it was working like a normal one, no demo nothing.
How can I fix this issue to login to Nabi 2 using my own registered email ID.
Following are the details of my Nabi2 device:
About this nabi
Account: [email protected]
Model No: NABI2NV7A-D
Android Version: 4.0.4
Build Number: IMM76L
Product Version: 1.9.23
Many thanks in advance.
Looking forward to any help.
Related
Hi, i need help to rooting my Ascend D1.
Do anyone help???
Tks.
powerdgo said:
Hi, i need help to rooting my Ascend D1.
Do anyone help???
Tks.
Click to expand...
Click to collapse
I have root and recovery on my ascend Ascend D1 (u9500) (NOT Quad!)
First i followed steps 1-7 here:
[not allowed to post link since i have to few posts]
ht tp : / / johnnyparanoia.blogspot . se/2012/06/how-to-root-huawei-ascend-p1-u9200.html
In step one i chose ("just the tools...")
To get ClockWorkMod Recovery i had to experiment a bit. Note that i believe that using CWM might hinder the possibilities to install official updates from Huawei.
How i did i wrote in a comment to the blog post previously mentioned.
I managed to install recovery (ClockWorkMod Recovery v5.8.4.5) after a lot of messing around.
First i installed Android Control (to c:\AndroidControl)
I downloaded cwm_touch_recovery_viva_beta.img and put it in c:\AndroidControl
Then i went into the phones download mode (or whatever it is called) by:
a: Turning off phone and wait a while
b: Hold Volume down and connect usb cable from computer
Now a new device shows up called Blaze. No driver could be identified. (in W7x64)
I Selected it in Device Manager and forced it to use "Android adapter ADB Interface" (I selected: Update driver software / Browse my computer... / Let me pick from a list... / Mobile phone (I think it was) / Android adapter ADB Interface).
I had the driver availible there. This might be from installing HiSuite earlier.
Now i started the command prompt (cmd) and went to c:\AndroidControl.
Then i ran the commands:
"fastboot devices" (to confirm that the device was identified. If no device is found an error will be thrown.)
"fastboot flash recovery cwm_touch_recovery_viva_beta.img"
"fastboot reboot"
Baseband version is: "IMC1202_20120620_PENTA"
Kernel version is: 3.0.8-00028-gf1d0793 [email protected] #1
Build number is: U9500-1V100R001C00B215
Kurbits!
Actually I did tried hard to follow your steps but it dostn't work. Luckily, after a long day trying i'm now successfully got my D1 a CWM (ClockWorkMod Recovery v5.8.4.5).
However, still i can't ROOT it, i've been tried the UnlockRoot but no chance. Can you tell me how you have it ROOTED?
I plan to flash an international version but the process always aborted. Is there any trick to do it? The CWM always look for UPDATE.ZIP while the firmware that I've downloaded has only UPDATE.APP
Do you have any suggestions on how this can be accomplished?
Thanks!
Kurbits said:
I have root and recovery on my ascend Ascend D1 (u9500) (NOT Quad!)
First i followed steps 1-7 here:
[not allowed to post link since i have to few posts]
ht tp : / / johnnyparanoia.blogspot . se/2012/06/how-to-root-huawei-ascend-p1-u9200.html
In step one i chose ("just the tools...")
To get ClockWorkMod Recovery i had to experiment a bit. Note that i believe that using CWM might hinder the possibilities to install official updates from Huawei.
How i did i wrote in a comment to the blog post previously mentioned.
I managed to install recovery (ClockWorkMod Recovery v5.8.4.5) after a lot of messing around.
First i installed Android Control (to c:\AndroidControl)
I downloaded cwm_touch_recovery_viva_beta.img and put it in c:\AndroidControl
Then i went into the phones download mode (or whatever it is called) by:
a: Turning off phone and wait a while
b: Hold Volume down and connect usb cable from computer
Now a new device shows up called Blaze. No driver could be identified. (in W7x64)
I Selected it in Device Manager and forced it to use "Android adapter ADB Interface" (I selected: Update driver software / Browse my computer... / Let me pick from a list... / Mobile phone (I think it was) / Android adapter ADB Interface).
I had the driver availible there. This might be from installing HiSuite earlier.
Now i started the command prompt (cmd) and went to c:\AndroidControl.
Then i ran the commands:
"fastboot devices" (to confirm that the device was identified. If no device is found an error will be thrown.)
"fastboot flash recovery cwm_touch_recovery_viva_beta.img"
"fastboot reboot"
Baseband version is: "IMC1202_20120620_PENTA"
Kernel version is: 3.0.8-00028-gf1d0793 [email protected] #1
Build number is: U9500-1V100R001C00B215
Click to expand...
Click to collapse
try adb restore
khmerppc said:
Kurbits!
Actually I did tried hard to follow your steps but it dostn't work...
However, still i can't ROOT it, i've been tried the UnlockRoot but no chance. Can you tell me how you have it ROOTED?...
Click to expand...
Click to collapse
Hi. So you have tried steps 1-7 from ht tp : / / johnnyparanoia.blogspot . se/2012/06/how-to-root-huawei-ascend-p1-u9200.html [not allowed to post link since i have to few posts]
Where does it go wrong? I´ll qoute the steps for reference only.
The url referred in step one is: h ttp://w ww.mediafire.com/?7pdfh11ue8ykyk6
Step 1 - Download ...just the tools here - b113 b115 root u9200[Nixing] Tools Only and extract to your desktop.
Step 2 - Enable USB debugging on your phone - Settings -> Developer options -> USB debugging and plug it into your PC
Step 3 - Run hwadb.exe and let it finish.
Step 4 - Run ubl.exe and wait for it to finish.
Step 5 - Disconnect your phone from your PC and Reboot.
Step 6 - Check to see if Superuser has been installed on your phone.
Step 7 - If you find Superuser in your menu, Congratulations your phone is rooted
Click to expand...
Click to collapse
I got it to work without problem. If you can specify where it goes wrong could you post a screenshot of what happens or be more specific about which step that does not seem to work.
Kurbits!
Thanks for the reply. I've successfully rooted it now but not with the steps in the URL u provided. What I did was tried to fix the permission and root it via CWM.
Anyway, what I really wanna do now is to flash it with international firmware offered in Huawei download page for D1. But the thing is that the firmware is come with UPDATE.APP instead of UPDATE.ZIP and I did try to rename it but no chance, always aborted.
Do you have any idea how to get it done?
Cheers
J
Kurbits said:
Hi. So you have tried steps 1-7 from ht tp : / / johnnyparanoia.blogspot . se/2012/06/how-to-root-huawei-ascend-p1-u9200.html [not allowed to post link since i have to few posts]
Where does it go wrong? I´ll qoute the steps for reference only.
The url referred in step one is: h ttp://w ww.mediafire.com/?7pdfh11ue8ykyk6
I got it to work without problem. If you can specify where it goes wrong could you post a screenshot of what happens or be more specific about which step that does not seem to work.
Click to expand...
Click to collapse
the automated process from this thread did not work on my D1, but this manual process did:
download mempodroid and su from
http://forum.xda-developers.com/showpost.php?p=21756513&postcount=1
follow all instructions in that post up to the mempodroid command (1st 4)
execute mempodroid with these args instead (copied from the ubl.exe tool posted by the OP)
Code:
./mempodroid 0xd734 0xad9f sh
execute the rest of the commands from the mempodroid root post (up to the adb reboot)
Hey did you try the Bin4ry method? its so simple and took me seconds to root!
I am on the quad but im sure it should work through this restore method!
http://forum.xda-developers.com/showthread.php?t=1886460
Reflashing U9500 to stock / Upgrading HUAWEI firmware
I have been searching these and other forums for a while trying to determine how to (a) update my CWM & rooted U9500 to the newest huawei build (221), and (b) return the phone entirely to stock (remove root & CWM). The main issue with either is that with CWM installed I couldn't figure out how to install Huawei's firmware UPDATE.APP files retrieved from their website. Here's how I got that to work:
I used the current firmware from Huawei: U9500-1,Android 4.0,V100R001C00B221,General Version (I can't post links)
Extract the HUAWEI zip and copy the dload folder (containing UPDATE.APP) to a micro sd card
Download split_updata.pl & crc binary from modaco.com forum (google "Repacking UPDATA.APP")
Run the split_updata.pl script with the path to UPDATE.APP as a command line argument. It should extract a bunch of unknown files to the output directory.
unknown_file.7 (should be 5697536 bytes) is the official recovery partition. This is what you will replace CWM with. You can rename it to recovery.img, or just use the created filename when flashing.
Boot phone in download mode:
* Power off
* Hold POWER & VOLUME DOWN buttons
* Release both when Huawei logo appears
* Phone should not continue booting or enter CWM
Run fastboot devices and make sure something is listed (mine only printed a bunch of question marks, but it worked fine)
Run fastboot flash recovery recovery.img
Run fastboot reboot
After the phone boots up normally, go to settings -> storage -> software upgrade -> sd card upgade and click confirm.
This will reboot into the official recovery image and start the upgrade process. This will also remove CWM, root/superuser, and any other changes to the OS you have made.
If you were just looking to upgrade, you can reflash CWM and/or root the phone again. If you were looking to return to stock, you can then reboot into Android and run the factory reset option.
d_ckhole said:
I have been searching these and other forums for a while trying to determine how to (a) update my CWM & rooted U9500 to the newest huawei build (221), and (b) return the phone entirely to stock (remove root & CWM). The main issue with either is that with CWM installed I couldn't figure out how to install Huawei's firmware UPDATE.APP files retrieved from their website. Here's how I got that to work:
I used the current firmware from Huawei: U9500-1,Android 4.0,V100R001C00B221,General Version (I can't post links)
Extract the HUAWEI zip and copy the dload folder (containing UPDATE.APP) to a micro sd card
Download split_updata.pl & crc binary from modaco.com forum (google "Repacking UPDATA.APP")
Run the split_updata.pl script with the path to UPDATE.APP as a command line argument. It should extract a bunch of unknown files to the output directory.
unknown_file.7 (should be 5697536 bytes) is the official recovery partition. This is what you will replace CWM with. You can rename it to recovery.img, or just use the created filename when flashing.
Boot phone in download mode:
* Power off
* Hold POWER & VOLUME DOWN buttons
* Release both when Huawei logo appears
* Phone should not continue booting or enter CWM
Run fastboot devices and make sure something is listed (mine only printed a bunch of question marks, but it worked fine)
Run fastboot flash recovery recovery.img
Run fastboot reboot
After the phone boots up normally, go to settings -> storage -> software upgrade -> sd card upgade and click confirm.
This will reboot into the official recovery image and start the upgrade process. This will also remove CWM, root/superuser, and any other changes to the OS you have made.
If you were just looking to upgrade, you can reflash CWM and/or root the phone again. If you were looking to return to stock, you can then reboot into Android and run the factory reset option.
Click to expand...
Click to collapse
You need to correctly install the drivers for both adb and fastboot.
It would be a nightmare on a 64bit Windows system, but it's quite easy on Linux/MacOS systems.
Ok, so I attempted to root a Nabi 2 so I could use the SD card to hold apps since the onboard memory is terrible and I bricked the dang thing. I unlocked root supposedly using a one click app method, then I was able to attempt to update using the updater already on the Nabi. During the reboot, thats when it bricked. It is stuck in a constant boot loop mode that eventually ends up on a dead android screen.
My main problem is I know there has got to be a way to restore a stock rom/os on it, but every how to guide out there assumes that I already know what the hell they are talking about. SDK, ADB, HIV, STD, its irritating. Also, I tried TWRP, ADB, etc. but since the Nabi is in a constant boot loop and dead android screen, I can't get my PC to recognize it for more than 5 seconds. Is there a step by step guide to what I need to do for a novice? Like step 1. "since your PC can't recognize the device in the first place this is where you start". Step 2, use "this program, then this, and this is why".
Can anyone out there help me get pointed in the right direction? I am tech savvy but the existing guides assume too much, have broken links, and don't say anything about what to do when you can't even get your device to be recognized.
Thanks
Aaron
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Higher-Primate said:
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Click to expand...
Click to collapse
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
aicjofs said:
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
Click to expand...
Click to collapse
I want to say it was running 4.1 or 4.2 but I'm not positive. Stupid me should have written it down. Is it possible to load any of the versions now that I have wiped it? I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen. From there I did a - and + and got an option to side load recovery or boot to ADB I think it was. So since I can at least get there, is there anything I can do? Other than that, TWRP won't recognize it and says no drivers are loaded. I'm assuming because I can't get the Nabi to stay stable long enough to actually load anything on to it? The device recognizes for a few seconds then disappears.
Higher-Primate said:
I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen.
Click to expand...
Click to collapse
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
aicjofs said:
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
Click to expand...
Click to collapse
Ok, I tried fastboot, but it doesn't really do anything. Once I go into fastboot, I have more options. Bootloader, continue, reboot bootloader, reboot, and power off. None of the options allows the Nabi to show up as a device in device manager. Everything just takes me to the dead android unfortunately.
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Higher-Primate said:
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Click to expand...
Click to collapse
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
aicjofs said:
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
Click to expand...
Click to collapse
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Higher-Primate said:
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Click to expand...
Click to collapse
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
aicjofs said:
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
Click to expand...
Click to collapse
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Higher-Primate said:
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Click to expand...
Click to collapse
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
aicjofs said:
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
Click to expand...
Click to collapse
No problem at all. Ok, that seemed to have done something. I put in the exact one you just changed above, and I rebooted normally, now I have a TWRP screen on the Nabi display. Now, what instructions do I need to follow? Do I still use NabiLab2015, if so the Disney/Nick or NV7A - US? Both now say "TWRP +mount:mounting /system on ext4 failed: no such file or directory.
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Higher-Primate said:
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Click to expand...
Click to collapse
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
aicjofs said:
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
Click to expand...
Click to collapse
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Higher-Primate said:
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Click to expand...
Click to collapse
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
aicjofs said:
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
Click to expand...
Click to collapse
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Higher-Primate said:
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Click to expand...
Click to collapse
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3013stock.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK3013bootloader.zip you downloaded and install it.
- Reboot
aicjofs said:
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3013stock.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK3013bootloader.zip you downloaded and install it.
- Reboot
Click to expand...
Click to collapse
What happens if it won't let me create the backup folder? It errors out and says it can't create one.
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
All you will need link, at the end of the post. I don't know for how long it will be up, but you can use it for now.
By the way.... Should you find something useful here... please hit the thanks button in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00 (or any latest version).
Steps:
1. Install the windows drivers you downloaded
Note : If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
2. Open the folder you extracted SP Flashtool and run it as administrator.
3. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet. (should work with holding the power key down for a little longer than 10 seconds. If not hold down volume key and power button for the same amount of time - tested and working)
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a. adb reboot bootloader
b. fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10. Choose reboot to system and allow complete boot cycle! Essential!
11. Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version).
12. Once installed back to the windows terminal and issue:
a. adb reboot bootloader
b. fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note : Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
All you will need and credits:
https://drive.google.com/drive/fold...ourcekey=0-SDvJaXtWWk-TY9B53ct8dw&usp=sharing (thanks button, thanks button, thanks button!!! )
Results:
(it is in Greek, but you get the idea )
Hope I have helped! Happy playing with the commands and whole process! :good:
Lastly, if you get stuck at any point, you can either use this thread or PM me for further advice, explanation and/or any kind of assistance.
Note: Special thanks to @MotoJunkie01 for actually taking the time to further help people on this thread, as unfortunately I do not currently have the time to do so myself. It is worth checking out @MotoJunkie01 's threads also. There, you can find very useful and updated information.
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
If you find it useful, just hit thanks in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00
Steps:
1. Install the windows drivers you downloaded
2. Open the folder you extracted SP Flashtool and run it as administrator.
4. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet.
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a.adb reboot bootloader
b.fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10.Choose reboot to system and allow complete boot cycle! Essential!
11.Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version.
12.Once installed back to the windows terminal and issue:
a.adb reboot bootloader
b.fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note 1: Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
Note 2: If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
I apologize for not being able to post links, but I believe the required software is not particularly hard to find.
Hope I have helped! Happy playing with the commands and whole process! I will continue to help as much as I can :good:
Click to expand...
Click to collapse
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
MotoJunkie01 said:
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
Click to expand...
Click to collapse
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
r&xp said:
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
Click to expand...
Click to collapse
Thank you for the encouragement. I am in hopes that we can eventually get a dedicated device forum for the tb3-850f. I truly believe this tablet has the potential for plenty of future development.
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Rimmir said:
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Click to expand...
Click to collapse
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
r&xp said:
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Click to expand...
Click to collapse
Lol yessir, thanked!
MotoJunkie01 said:
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
Click to expand...
Click to collapse
Looking forward to it. I picked mine up from walmart just yesterday for using as a google maps/car media center
My Lenovo Tab 3 replacement finally arrived in the mail. I'll be picking up where I left off on compiling both unmodified stock and custom stock-based ROMs for this tablet.
On my modified stock based ROM, I'm considering the implementation of Substratum (Root Ver) for theming, but I would like to get the input of other device owners first. So far, I have debloated, deodexed and zipaligned the OS. I am including the modified/patched boot image with SuperSU v2.79 SR3 binaries installed for systemless root, Nova Launcher, Pixel Icon Pack, BusyBox v1.26.2 binaries pre-injected in /su/xbin/, and Kernel Adiutor-Mod installed in /system/apps/ for user defined adjustments to the stock kernel and governors.
You guys please give me input on what you would like included in the ROM. Thanks
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
Click to expand...
Click to collapse
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
chienfou said:
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
Click to expand...
Click to collapse
Really glad it worked for you!!!
Thumbs up! :good::good:
load the scatter file .txt in SP Flashrom is OK ... it show me purple color until finish loading the file.
but how come when I hit the green button Download, it seems like nothing downloading,
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
yiukiang said:
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
Click to expand...
Click to collapse
Try again to get TWRP installed to your /recovery partition or, alternatively, try to simply boot into TWRP from fastboot with the fastboot boot twrp.img command. It is common for members to experience some difficulty in installing custom recovery on this device. It has been my experience that most members are successful the second time around.
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
yiukiang said:
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
Click to expand...
Click to collapse
System updates (OTAs) won't install on rooted operating systems. To install an OTA, you must have unmodified stock /boot, /system, and /recovery partitions installed. On the GPS issue, go to Settings, Apps, and ensure Google Maps has been granted location access permission.
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
xavier234 said:
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
Click to expand...
Click to collapse
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
MotoJunkie01 said:
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
Click to expand...
Click to collapse
Hello, I'll weigh in on this one. There are multiple threads above the TB3-850F on this forum and also another forum.
I initially followed a different thread and instructions which caused my problem. Notably do not allow TWRP write access !!! This mistake caused the soft-brick.
Anyone following any other advice about TB3-850F or downloading any other image BEWARe. Only follow the advice in this thread by r&xp:
https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Following this advice I now restored original image and then rooted in just a few hours.. Thank you r&xp for the good advice. :laugh:
I’ve been lurking on these forums for a while and I have decided that I’m willing to take the risk to unlock my Thor’s potential. I have made sure to read through advised reading materials, and searching through other posts before posting. (I tried figuring out how to quote multiple posts to make this thread easier to navigate but I couldn't, sorry)
Device: Kindle Fire HDX 7” 3rd Generation running Fire OS 4.5.5.3
I will be using a Windows 10 Home machine to do this.
Purpose: Allow for the device to work well in Google’s ecosystem so I can have a useful device for medical school.
I am currently trying to learn the steps outlined here, but I have some concerns:
Does it matter whether or not I factory reset my device before I begin?
Will my computer’s OS cause any issues? According to this, there might be some driver issues? Should I download the “Motorola Device manager”?
Where is the “aboot_vuln.mbn” file? Do I obtain it once I follow the steps in order?
I want to use “Minimal ADB and Fastboot” instead of the attached “15 seconds ADB Installer v1.4.3” because the later has not been updated in a while and the former was updated this month. According to the install instructions for the former, I need to have my device already plugged in and the “kindle fire USB driver” already installed. Will this affect step 4 of the procedure or anything else?
On step 5, am I correct in my assumption that changing the driver will be a simple few click process?
On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
What ROM do you recommend for my needs? And could you provide me a link to the correct download/discussion board? I would prefer a ROM running at least Nougat that has long-term support planned. I read that “Fire Nexus ROM” is pretty basic, so I don’t think I want it. As of now, I’m looking at CM/Lineage 14.1, but I don’t know what ROM would work on my device from the website. AospExtended seems like a good option but apparently, there are wi-fi issues which are a deal-breaker.
Thank you so much for reading through this. Hopefully all my research and proves to be useful for anyone trying to help. If I’m able to get this working cleanly, I would be willing to make a cleaned up guide for this version and device to better aid future people.
hwwof said:
I’ve been lurking on these forums for a while and I have decided that I’m willing to take the risk to unlock my Thor’s potential. I have made sure to read through advised reading materials, and searching through other posts before posting. (I tried figuring out how to quote multiple posts to make this thread easier to navigate but I couldn't, sorry)
Device: Kindle Fire HDX 7” 3rd Generation running Fire OS 4.5.5.3
I will be using a Windows 10 Home machine to do this.
Purpose: Allow for the device to work well in Google’s ecosystem so I can have a useful device for medical school.
Click to expand...
Click to collapse
Hello @hwwof -
You have done your homework (thank you!) and presented reasonable questions. I'm going to answer the first five 'in-line' below. Responses will be brief to keep the thread serviceable for those accessing XDA content on small screens; don't read anything into that. Bounce back on any items that need further elaboration.
hwwof said:
I am currently trying to learn the steps outlined here, but I have some concerns:
Does it matter whether or not I factory reset my device before I begin?
Click to expand...
Click to collapse
No; however, it would be better if you did NOT reset the device.
hwwof said:
Will my computer’s OS cause any issues? According to this, there might be some driver issues? Should I download the “Motorola Device manager”?
Click to expand...
Click to collapse
Nope. Drivers installed via the Motorola Device manager are properly signed which mitigates any potential issues on 64-bit Win 10 builds (yet another reason to use the Moto drivers vs others that have been posted)
hwwof said:
Where is the “aboot_vuln.mbn” file? Do I obtain it once I follow the steps in order?
Click to expand...
Click to collapse
It's contained within aboot-13-thor.zip; just named differently.
hwwof said:
I want to use “Minimal ADB and Fastboot” instead of the attached “15 seconds ADB Installer v1.4.3” because the later has not been updated in a while and the former was updated this month. According to the install instructions for the former, I need to have my device already plugged in and the “kindle fire USB driver” already installed. Will this affect step 4 of the procedure or anything else?
Click to expand...
Click to collapse
Good idea. Your device does not need to be tethered while installing Minimal ADB and Fastboot. Take note of where the package is installed (typically "C:\Program Files (x86)\Minimal ADB and Fastboot") and practice opening a command window focused in that folder. To make life simpler you can direct the installer to place the files in "c:\work" which is a lot easier to type.
hwwof said:
On step 5, am I correct in my assumption that changing the driver will be a simple few click process?
Click to expand...
Click to collapse
Yes - but here's were it gets interesting and a bit frustrating. Even with the Moto drivers Windows can be very fussy communicating with HDX devices. To complicate matters there are two modes to deal with: ADB and Fastboot. You'll learn which is which as time goes on and will likely have to switch Windows drivers for each mode. Sometimes a reboot is needed to get everyone talking. Note there is no danger involved simply tethering your device and issuing basic queries.
To test basic ADB communications:
- execute step #2 (only) from the linked procedure
- open a Windows command prompt as outlined above
- boot HDX into FireOS and move past the screen lock
- tether device to windows; take note of any noises and/or confirmation messages
- in the window command prompt issue the command "adb devices" and press Enter. What happens?
Post back results and we'll go from there.
Thank you @Davey126 . I appreciate you taking the time to help me out. Answers to the other questions would be very appreciated as well!
Here are my results that you requested:
The kindle beeped, and the internal storage popped up on my computer. I ran the minimal adb and fastboot program, and got this output:
Code:
C:\adb>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
D0FBA0A0351401GB unauthorized
C:\adb>
And on the kindle, I got a “Allow USV debugging” popup on the kindle and it showed my computer’s RSA Fingerprint. I then pressed allow. I took note of the fingerprint just in case. I then tried ejecting my device but it wouldn’t let me because a program was still using it. I ran “adb devices” again and got this output:
Code:
C:\adb>adb devices
List of devices attached
D0FBA0A0351401GB device
C:\adb>
hwwof said:
Thank you @Davey126 . I appreciate you taking the time to help me out. Answers to the other questions would be very appreciated as well!
Click to expand...
Click to collapse
Second response is positive. Next issue the following command: 'adb reboot bootloader'. This will place your device in fastboot mode. If you are very lucky a 'Ready' prompt will appear on the device below the word 'fastboot'. Most likely you will need to head to Windows Device Manager, identify which entry is associated with the tethered HDX and then change the device driver to 'Moto Composite' or something similar (might not have the wording exactly right). Once you get a 'Ready' prompt issue the following command: 'fastboot devices'. If you get a response similar to 'adb devices' then you are good to go.
Hints/tips:
- to help determine which entry(s) are associated with your HDX tether/untether your device while Windows Device Manager is open
- right click an entry to change the device driver; navigate 'Browse my computer ...' -> 'Let me pick ...'; do not choose any of the automated options
- if you can't get a Ready prompt and/or an response to 'fastboot devices' reboot both devices and try again
- if still no joy change USB ports and cables; the latter are especially problematic (people never believe that until trying 1821 other things - ugh!)
Report back and we'll go from there. I know you prefer the rest of your questions answered up front. Experience suggests an incremental approach is more productive - for you, me and future readers.
Davey126 said:
Second response is positive. Next issue the following command: 'adb reboot bootloader'. This will place your device in fastboot mode. If you are very lucky a 'Ready' prompt will appear on the device below the word 'fastboot'. Most likely you will need to head to Windows Device Manager, identify which entry is associated with the tethered HDX and then change the device driver to 'Moto Composite' or something similar (might not have the wording exactly right). Once you get a 'Ready' prompt issue the following command: 'fastboot devices'. If you get a response similar to 'adb devices' then you are good to go.
Hints/tips:
- to help determine which entry(s) are associated with your HDX tether/untether your device while Windows Device Manager is open
- right click an entry to change the device driver; navigate 'Browse my computer ...' -> 'Let me pick ...'; do not choose any of the automated options
- if you can't get a Ready prompt and/or an response to 'fastboot devices' reboot both devices and try again
- if still no joy change USB ports and cables; the latter are especially problematic (people never believe that until trying 1821 other things - ugh!)
Report back and we'll go from there. I know you prefer the rest of your questions answered up front. Experience suggests an incremental approach is more productive - for you, me and future readers.
Click to expand...
Click to collapse
Thank you! Now it says "ready" but I'm concerned about how to unplug it without messing anything up. here's the output:
Code:
Microsoft Windows [Version 10.0.16299.248]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
D0FBA0A0351401GB fastboot
C:\adb>
You are correct that I would prefer having all the answers upfront, but it's only so I can then question the answers to get a better understanding before messing with the device. A quick reply would be appreciated!
hwwof said:
Thank you! Now it says "ready" but I'm concerned about how to unplug it without messing anything up. here's the output:
{content removed}
You are correct that I would prefer having all the answers upfront, but it's only so I can then question the answers to get a better understanding before messing with the device. A quick reply would be appreciated!
Click to expand...
Click to collapse
Great!! The purpose of this exercise was to validate connectivity in two different modes and, if needed, provide a safe 'test' environment for remediation. No worries about breaking the tether if there is no active data transfer taking place. Simply unplug and then long press <power> until the device shuts down.
In response to your other questions:
Q: On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
A: Follow the steps as quoted
Q: Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
A1: You should assume all content on your device will be erased following completion of Step #9 (although it will likely remain intact)
A2: The two files you will be 'flashing' with the dd command should be located in the same folder as "Minimal ADB and Fastboot"
A3: Deal with that later (flashing ROM)
Q: ROMs:
A: All of the Nougat based custom ROMs for HDX are stable and feature complete. Nuances are subtle and probably not worth worrying about now; you can always change later. My personal preference is AEX (AospExtended). That said, Lineage 14.1 and Slim 7 are both excellent alternatives.
Davey126 said:
Great!! The purpose of this exercise was to validate connectivity in two different modes and, if needed, provide a safe 'test' environment for remediation. No worries about breaking the tether if there is no active data transfer taking place. Simply unplug and then long press <power> until the device shuts down.
In response to your other questions:
Q: On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
A: Follow the steps as quoted
Q: Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
A1: You should assume all content on your device will be erased following completion of Step #9 (although it will likely remain intact)
A2: The two files you will be 'flashing' with the dd command should be located in the same folder as "Minimal ADB and Fastboot"
A3: Deal with that later (flashing ROM)
Q: ROMs:
A: All of the Nougat based custom ROMs for HDX are stable and feature complete. Nuances are subtle and probably not worth worrying about now; you can always change later. My personal preference is AEX (AospExtended). That said, Lineage 14.1 and Slim 7 are both excellent alternatives.
Click to expand...
Click to collapse
So I completed the instructions, booted to TWRP, turned it off, booted up, did the unlock batch, but I didn't get "unlock code is correct". I got a lot of green lines "getvar slot-count...OK getvar:slot-suffixes...OK getvar:has-slot:unlock...OK getvarartition-type:unlock...OK getvar:max-download-size...[[0x20000000 ]] download:00000000..." Here's the cmd when I try running unlock.bat https://gyazo.com/a041dc49c786f9846d706c049eacbbf3
Did I mess something up or am I unlocked? I'm not sure what to do from here. I was still able to get back to TWRP. It's telling me to swipe to allow modifications or to keep read only. Where do I proceed from here? I'm reading in some places to wipe before installing, and a lot of other conflicting information. I downlaoded the AEX november build and would like to flash it. Do I have any need for rooting or SuperSU?
Again, Thank you so much for all your help
*deleted*
*deleted*
hwwof said:
So I completed the instructions, booted to TWRP, turned it off, booted up, did the unlock batch, but I didn't get "unlock code is correct". I got a lot of green lines "getvar slot-count...OK getvar:slot-suffixes...OK getvar:has-slot:unlock...OK getvarartition-type:unlock...OK getvar:max-download-size...[[0x20000000 ]] download:00000000..." Here's the cmd when I try running unlock.bat https://gyazo.com/a041dc49c786f9846d706c049eacbbf3
Did I mess something up or am I unlocked? I'm not sure what to do from here. I was still able to get back to TWRP. It's telling me to swipe to allow modifications or to keep read only. Where do I proceed from here? I'm reading in some places to wipe before installing, and a lot of other conflicting information. I downlaoded the AEX november build and would like to flash it. Do I have any need for rooting or SuperSU?
Again, Thank you so much for all your help
Click to expand...
Click to collapse
Device is NOT unlocked. Tied up for the next hour or two; will respond then. Do not wipe or attempt to flash anything. Sorry for wait ...
Davey126 said:
Device is NOT unlocked. Tied up for the next hour or two; will respond then. Do not wipe or attempt to flash anything. Sorry for wait ...
Click to expand...
Click to collapse
Thank you for being on top of this! I'm glad I was patient and didn't immediately try flashing anything. I'll try to wait up! I apologize if I fall asleep.
hwwof said:
Thank you for being on top of this! I'm glad I was patient and didn't immediately try flashing anything. I'll try to wait up! I apologize if I fall asleep.
Click to expand...
Click to collapse
Quick activity while you wait:
- boot into TWRP (power down; press <power>+<vol-up> for ~3 sec then release)
- swipe to allow modifications
- tap the backup option, select all partitions except cache, swipe to execute
- when complete tether device; should connect in adb mode
- from look for a new device/drive in Windows File Explorer
- click <device ID> -> Internal Storage; should see a folder named TWRP
- drag or right-click folder to a storage location on your Win 10 machine
- congrats! You have just made a backup of your device -and- placed a reserve copy on your Windows machine
Comment: prior to backing up you had completed the most risky tasks (stuff that could have yielded a soft/hard brick). It's all downhill from here. Will post more info on unlocking and installing a new ROM in a bit; real-life is calling . Fully understand if you need to sleep; post will be waiting in the morning. Penning this from Northeast USA; timezone UTC-5.
Davey126 said:
Quick activity while you wait:
- boot into TWRP (power down; press <power>+<vol-up> for ~3 sec then release)
- swipe to allow modifications
- tap the backup option, select all partitions except cache, swipe to execute
- when complete tether device; should connect in adb mode
- from look for a new device/drive in Windows File Explorer
- click <device ID> -> Internal Storage; should see a folder named TWRP
- drag or right-click folder to a storage location on your Win 10 machine
- congrats! You have just made a backup of your device -and- placed a reserve copy on your Windows machine
Comment: prior to backing up you had completed the most risky tasks (stuff that could have yielded a soft/hard brick). It's all downhill from here. Will post more info on unlocking and installing a new ROM in a bit; real-life is calling . Fully understand if you need to sleep; post will be waiting in the morning. Penning this from Northeast USA; timezone UTC-5.
Click to expand...
Click to collapse
I appreciate you so much! And I completely understand. I hope everything you're working on gets resolved!
I have backed it up as you suggested! Since the back-up is also on the internal drive, it will be deleted later, correct? It's 5gbs out of the already small storage space.
hwwof said:
I appreciate you so much! And I completely understand. I hope everything you're working on gets resolved!
I have backed it up as you suggested! Since the back-up is also on the internal drive, it will be deleted later, correct? It's 5gbs out of the already small storage space.
Click to expand...
Click to collapse
With the 5GB TWRP backup folder safely copied off-device you can delete the local copy at any time...although there is no immediate reason to do so.
Next step is to unlock the bootloader:
- verify 'get_code.bat' & 'unlock.bat' reside in the same folder as adb.exe and fastboot.exe
- look around to see if you have a file called 'unlock.code' from a previous run of 'get_code.bat'; if so place it in the same folder
- tether device and boot into fastboot (easiest way: boot into TWRP and then use reboot menu to boot the bootloader) [<--what an awkward sentence!]
- enter 'fastboot devices' to validate communication between host and device
- execute unlock.bat; if you get a green 'OK' the bootloader is unlocked!
- if not boot into FireOS (get past unlock screen), tether, verify adb communication is working and then run 'get_code.bat' to (re)create the 'unlock.code' file
- repeat steps 2-4 (above)
If that doesn't work and/or you are unable to boot into TWRP then a bit of extra work will be needed to generate a valid unlock code. Brief outline:
- download legacy Fire Nexus ROM from here (it does NOT require an unlocked bootloader)
- tether device and into TWRP
- from Windows copy downloaded ROM to a folder on the device (suggest creating a new folder with your initials as the name)
- from the TWRP main menu tap Wipe then swipe to perform a 'factory reset'
- from the TWRP main menu tap Install
- navigate to the folder where you stored the downloaded ROM
- select the ROM zip and then click to install
- when complete allow the device to restart; after a 3-5 min it should boot into Fire Nexus; skip the Google config (not needed)
- enable developer options and adb bridge
- tether device and verify adb connectivity
- run 'get_code.bat' to generate a fresh unlock.code file
I will be traveling much of Sunday with irregular network access. I'll try to respond to an questions/problems as time permits. Apologies in advance for any delays.
Davey126 said:
With the 5GB TWRP backup folder safely copied off-device you can delete the local copy at any time...although there is no immediate reason to do so.
Next step is to unlock the bootloader:
- verify 'get_code.bat' & 'unlock.bat' reside in the same folder as adb.exe and fastboot.exe
- look around to see if you have a file called 'unlock.code' from a previous run of 'get_code.bat'; if so place it in the same folder
- tether device and boot into fastboot (easiest way: boot into TWRP and then use reboot menu to boot the bootloader) [<--what an awkward sentence!]
- enter 'fastboot devices' to validate communication between host and device
- execute unlock.bat; if you get a green 'OK' the bootloader is unlocked!
- if not boot into FireOS (get past unlock screen), tether, verify adb communication is working and then run 'get_code.bat' to (re)create the 'unlock.code' file
- repeat steps 2-4 (above)
If that doesn't work and/or you are unable to boot into TWRP then a bit of extra work will be needed to generate a valid unlock code. Brief outline:
- download legacy Fire Nexus ROM from here (it does NOT require an unlocked bootloader)
- tether device and into TWRP
- from Windows copy downloaded ROM to a folder on the device (suggest creating a new folder with your initials as the name)
- from the TWRP main menu tap Wipe then swipe to perform a 'factory reset'
- from the TWRP main menu tap Install
- navigate to the folder where you stored the downloaded ROM
- select the ROM zip and then click to install
- when complete allow the device to restart; after a 3-5 min it should boot into Fire Nexus; skip the Google config (not needed)
- enable developer options and adb bridge
- tether device and verify adb connectivity
- run 'get_code.bat' to generate a fresh unlock.code file
I will be traveling much of Sunday with irregular network access. I'll try to respond to an questions/problems as time permits. Apologies in advance for any delays.
Click to expand...
Click to collapse
Welp, device won't boot into FireOS. It boots straight to Fastboot. I tried Installing nexus ROM but I got "can't install this package over newer build updater process ended with error:7".
hwwof said:
Welp, device won't boot into FireOS. It boots straight to Fastboot. I tried Installing nexus ROM but I got "can't install this package over newer build updater process ended with error:7".
Click to expand...
Click to collapse
Error 7 is pretty generic and can be due to a conflict between install package and TWRP or an issue with the system partition. It's a solvable issue without too much work. They the following in the order listed.
1) In TWRP tap wipe -> advanced. Tick system, data, dalvik and cache; leave internal storage unticked. Tap the appropriate button to execute. Return to main menu and reboot back into recovery. Then try to install the Nexus ROM.
2) Download an older build of TWRP from here and transfer to adb/fastboot folder on Windows. Boot device into fastboot mode and issue the following command to install:
sudo fastboot -i 0x1949 flash recovery <recovery-image>
Will check back in 5-6 hours on progress.
Davey126 said:
Error 7 is pretty generic and can be due to a conflict between install package and TWRP or an issue with the system partition. It's a solvable issue without too much work. They the following in the order listed.
1) In TWRP tap wipe -> advanced. Tick system, data, dalvik and cache; leave internal storage unticked. Tap the appropriate button to execute. Return to main menu and reboot back into recovery. Then try to install the Nexus ROM.
2) Download an older build of TWRP from here and transfer to adb/fastboot folder on Windows. Boot device into fastboot mode and issue the following command to install:
sudo fastboot -i 0x1949 flash recovery <recovery-image>
Will check back in 5-6 hours on progress.
Click to expand...
Click to collapse
First one didn't work, second one put this out:
C:\adb>sudo fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
'sudo' is not recognized as an internal or external command,
operable program or batch file.
hwwof said:
First one didn't work, second one put this out:
C:\adb>sudo fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
'sudo' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Drop the sudo prefix ...
Davey126 said:
Drop the sudo prefix ...
Click to expand...
Click to collapse
"
C:\adb>fastboot devices
D0FBA0A0351401GB fastboot
C:\adb>fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
target reported max download size of 536870912 bytes
sending 'recovery' (9220 KB)...
OKAY [ 0.361s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.424s
C:\adb>
"
hwwof said:
"
C:\adb>fastboot devices
D0FBA0A0351401GB fastboot
C:\adb>fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
target reported max download size of 536870912 bytes
sending 'recovery' (9220 KB)...
OKAY [ 0.361s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.424s
C:\adb>
"
Click to expand...
Click to collapse
This suggest the vulnerable bootloader was not properly installed. You will probably need to repeat the installation procedure from the point of placing the device in 'bulk' mode. Be sure to pay attention to file indexes and file identifiers that follow "if=".
@draxie - would you agree with this assessment? Poster is following this guide and using the files attached to that post.
After few day i find out solution how to install custom ROM to my Lenovo tablet. I think its first guide how to do it because every other guides were for TB2-X30F but not for TB2-X30L.
Installation guide:
FILES TO DOWNLOAD:
ALL FILES: https:// drive.google.com/drive/folders/1heVQAryphuXNVt5k-HsUhfRrVr9MV34D
ALL LINKS WORK ! JUST DELETE THE SPACE BEFORE drive.google.com...
1) On the tablet, at Settings, you must activate on the Developer Options the Bootloader Unlock (OEM unlocking) and USB debugging. Uncheck Verify apps over USB.
How to unlock Developer: https: //youtu.be/g5wkFAWDsg0
2) Download these files directly to your Android device, not to SD card.
a) https:// drive.google.com/file/d/1230xFbPA7DOGMhuX59yagEd6w1gNCI4o/view SuperSU-v2.79.zip (for me working only v2.79)
b) https:// drive.google.com/file/d/1vRW5RZixtNVfKbJ7nL2EUetANydfmLNg/view Gapps.zip (open_gapps-arm-7.1-micro-20180721)
b) https:// drive.google.com/file/d/13Mp8guzzOvb17s88IQyez_9reozpTNbw/view boot.img (from LiOS14-UNOFFICIAL-TB2-X30L)
3) Power off completely the tablet.
4) REMOVE SD CARD ! (because for me a part of system was installed on SD card).
5) Make sure you have a good cable so the connection between PC and tablet is perfect.
6) Download https: //drive.google.com/file/d/1XTDYs7kxagj-CXHsH_yyQnMXqYwAP_hK/view ADB and Fastboot to your PC .(here are the drivers too).
7) Unzip the zip archive and run with Administrator the apps from inside of the zip. To all the questions you must to press key Y to grant all the rights it needs.
8) Press and hold Volume up and plug in usb. Now you are in stock recovery menu.
9) From stock recovery select reboot to bootloader by using volume keys and power keys.
10) Wait about 5-10sec to tablet boot in bootloader mode. (shows lenovo logo in screen when ready)
11) Download the https:// drive.google.com/file/d/15IH55DgmD6SmlILjTukGeNcmYgUPcmCg/view recovery.img(its TWRP version for Lenovo Tab2 x30f so it wont work properly) and copy it into folder adb at local disk C (installed on step 7)
12) Run CMD with administrator and type cd C:\adb to select the adb folder.
13) In cmd type fastboot unlock-go and press enter. In case this command does not work, please try fastboot -s or fastboot oem unlock-go or fastboot oem unlock .
14) Flash recovery with command fastboot flash recovery recovery.img and then type fastboot boot recovery.img
15) From TWRP select Install and browse to emmc folder and then to your folder where you stored all files you downloaded.
(in bottom right corner you have Images... or Zips... here you can choose what type of file you want to install.
Install SuperSU-v2.79.zip
16) Now in menu select Wipe -> Advanced Wipe and check Dalvik Cache, Data and Cache. Wipe them.
17) Go back to menu and select Install. And install boot.img. At top of display check Boot and flash it.
19) Download https:// drive.google.com/file/d/1MlDxidIqLOZv_QZ91i8bsHgGdBMf7l9g/view LiOS14-UNOFFICIAL-TB2-X30L.zip and copy it into folder adb at local disk C (C:\adb).
18) Go to Menu select Advanced and open ADB Sideload. Go back to CMD on your pc and type
adb devices
If its your tablet properly connected you will see some letters and numbers and sideload. After that type
adb sideload LiOS14-UNOFFICIAL-TB2-X30L.zip
Now wait for finish the installation. If its installed corectly you will see Succesful at the top.
19) Repeate step number 15 and again install SuperSU-v2.79.zip (In installation you will see Boot image patcher)
20) Unplug your tablet from PC. And reboot it. First reboot may take 5-10 minutes and can reboot few times. DO NOT INTERRUPT THIS PROCESS.
21) After first start (set language, date..) Turn off devices.
22) Power on devices to recovery mode
(Press continuously the volume up and power key. When the screen on the tablet has started, release the power key and keep pressing the volume up key)
23) Now select again Install and install Gapps (open_gapps-arm-7.1-micro-20180721.zip). Then reboot it.
Now you have installed LiOS14-UNOFFICIAL (Android 7.1), with all stock apps(gapps) and also rooted device.
this is exactly what i was looking for 3 weeks ago. my sister asked if i could have a look at her old tablet. i managed to do it by translating myself through some russian forums. btw. does netflix work? on my sisters one it does not atm. i guess the play protect thing.
binocchio said:
this is exactly what i was looking for 3 weeks ago. my sister asked if i could have a look at her old tablet. i managed to do it by translating myself through some russian forums. btw. does netflix work? on my sisters one it does not atm. i guess the play protect thing.
Click to expand...
Click to collapse
You need to download apk from Netflix site.
https:// help.netflix.com/en/node/57688
direct link to apk
https:// netflixhelp.s3.amazonaws.com/netflix-4.16-200217-release.apk
mutrin said:
You need to download apk from Netflix site.
https:// help.netflix.com/en/node/57688
direct link to apk
https:// netflixhelp.s3.amazonaws.com/netflix-4.16-200217-release.apk
Click to expand...
Click to collapse
my sister is very grateful
Thank you very much.
What build date has this rom? Sec. patches?
Can you please post your local manifest?
Very interesting guide, unfortunately the links don't work...
Is it possible to restore them?
Tanks. Max
I think its first guide how to do it because every other guides were for TB2-X30F but not for TB2-X30L.
I have only found lineage os for x30l, can someone please link lineage (Android 7) for x30f?
The difference between L and F is that L is the sim card variant. Ive read several people getting "insert sim card" when installing L on a F tablet. So I dont want messages like this.
Thanks for this tutorial. It was possible, to upgrade this old Tablet.
Do you know, if there is anything newer version for our Lenovo?
mutrin said:
After few day i find out solution how to install custom ROM to my Lenovo tablet. I think its first guide how to do it because every other guides were for TB2-X30F but not for TB2-X30L.
Installation guide:
FILES TO DOWNLOAD:
ALL FILES: https:// drive.google.com/drive/folders/1heVQAryphuXNVt5k-HsUhfRrVr9MV34D
1) On the tablet, at Settings, you must activate on the Developer Options the Bootloader Unlock (OEM unlocking) and USB debugging. Uncheck Verify apps over USB.
How to unlock Developer: https: //youtu.be/g5wkFAWDsg0
2) Download these files directly to your Android device, not to SD card.
a) https:// drive.google.com/file/d/1230xFbPA7DOGMhuX59yagEd6w1gNCI4o/view SuperSU-v2.79.zip (for me working only v2.79)
b) https:// drive.google.com/file/d/1vRW5RZixtNVfKbJ7nL2EUetANydfmLNg/view Gapps.zip (open_gapps-arm-7.1-micro-20180721)
b) https:// drive.google.com/file/d/13Mp8guzzOvb17s88IQyez_9reozpTNbw/view boot.img (from LiOS14-UNOFFICIAL-TB2-X30L)
3) Power off completely the tablet.
4) REMOVE SD CARD ! (because for me a part of system was installed on SD card).
5) Make sure you have a good cable so the connection between PC and tablet is perfect.
6) Download https: //drive.google.com/file/d/1XTDYs7kxagj-CXHsH_yyQnMXqYwAP_hK/view ADB and Fastboot to your PC .(here are the drivers too).
7) Unzip the zip archive and run with Administrator the apps from inside of the zip. To all the questions you must to press key Y to grant all the rights it needs.
8) Press and hold Volume up and plug in usb. Now you are in stock recovery menu.
9) From stock recovery select reboot to bootloader by using volume keys and power keys.
10) Wait about 5-10sec to tablet boot in bootloader mode. (shows lenovo logo in screen when ready)
11) Download the https:// drive.google.com/file/d/15IH55DgmD6SmlILjTukGeNcmYgUPcmCg/view recovery.img(its TWRP version for Lenovo Tab2 x30f so it wont work properly) and copy it into folder adb at local disk C (installed on step 7)
12) Run CMD with administrator and type cd C:\adb to select the adb folder.
13) In cmd type fastboot unlock-go and press enter. In case this command does not work, please try fastboot -s or fastboot oem unlock-go or fastboot oem unlock .
14) Flash recovery with command fastboot flash recovery recovery.img and then type fastboot boot recovery.img
15) From TWRP select Install and browse to emmc folder and then to your folder where you stored all files you downloaded.
(in bottom right corner you have Images... or Zips... here you can choose what type of file you want to install.
Install SuperSU-v2.79.zip
16) Now in menu select Wipe -> Advanced Wipe and check Dalvik Cache, Data and Cache. Wipe them.
17) Go back to menu and select Install. And install boot.img. At top of display check Boot and flash it.
19) Download https:// drive.google.com/file/d/1MlDxidIqLOZv_QZ91i8bsHgGdBMf7l9g/view LiOS14-UNOFFICIAL-TB2-X30L.zip and copy it into folder adb at local disk C (C:\adb).
18) Go to Menu select Advanced and open ADB Sideload. Go back to CMD on your pc and type
adb devices
If its your tablet properly connected you will see some letters and numbers and sideload. After that type
adb sideload LiOS14-UNOFFICIAL-TB2-X30L.zip
Now wait for finish the installation. If its installed corectly you will see Succesful at the top.
19) Repeate step number 15 and again install SuperSU-v2.79.zip (In installation you will see Boot image patcher)
20) Unplug your tablet from PC. And reboot it. First reboot may take 5-10 minutes and can reboot few times. DO NOT INTERRUPT THIS PROCESS.
21) After first start (set language, date..) Turn off devices.
22) Power on devices to recovery mode
(Press continuously the volume up and power key. When the screen on the tablet has started, release the power key and keep pressing the volume up key)
23) Now select again Install and install Gapps (open_gapps-arm-7.1-micro-20180721.zip). Then reboot it.
Now you have installed LiOS14-UNOFFICIAL (Android 7.1), with all stock apps(gapps) and also rooted device.
Click to expand...
Click to collapse
I have followed the instructions and successfully installed LiOS14. Then, however, I have factory reset the tablet via Settings. Now it always boots to TWRP, no matter what I have tried I could not installed back the LiOS14 I only have TWRP right now.
Any help?
Boyalikus said:
I have followed the instructions and successfully installed LiOS14. Then, however, I have factory reset the tablet via Settings. Now it always boots to TWRP, no matter what I have tried I could not installed back the LiOS14 I only have TWRP right now.
Any help?
Click to expand...
Click to collapse
Same here
For me, this worked:
Lg v20 keeps booting to twerp recovery after factory reset. Megarom
Really not loving this phone and this rom. After learning I can't return to stock. Decided to factory reset it andoesn't then it boots directly to twerp recovery. Do did the first factory recovery from within the phone. Then after it booted into...
forum.xda-developers.com
The tablet can also run on LineageOS 16 which is Android 9.
As I saw that the guys in the Russian 4PDA-Forum had been able to create a LiOS16, I was able to make some adjustments and compile a ROM with most recent security patches which now runs on my good old TB2-X30L / TAB2 A10-30:
lineage-16.0-20210328-UNOFFICIAL-TB2-X30L.zip | by kenschbacher9 for 10
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
it seems that google drives are off. Can someone re-upload please?
Hallo,
I have installed LiOS14-UNOFFICIAL-TB2-X30L.zip. The installation was without problems.
But I am having problem with WiFi - problem of MAC 02:00:00:00:00:00. I have tried a lots of tips but nothig worked. Two times I was succesfull to set some MAC, but always, after while, it was gone. No able to reproduce to set.
Is it really so difficult to set somehow the MAC addres for the WiFi?
As I understand the setting of the MAC differs between different releases of OS. Does anybody know how it work in this release? It should by known where this relaese expects the MAC setting. Am I right?
1. temporary succes: Setting MAC in system/etc/firmware/wlan/qca_cld/wlan_mac.bin (I think. Its longer time ago and there was more attempts). It lasted for few months. It is not mine device so I don't know how it was handled.
2. temporary succes: I copied system/etc/firmware/wlan dir to system/vendor/firmware/wlan. I did it based on how it is in Samsung Galaxy S4 mini with Lineage 16. It worked. After restart I had to swith off and on the airplane mode to set MAC. After few attempts it was gone. No able to reproduce to set the MAC.
I am not Linux expert
nonicktoday said:
The tablet can also run on LineageOS 16 which is Android 9.
As I saw that the guys in the Russian 4PDA-Forum had been able to create a LiOS16, I was able to make some adjustments and compile a ROM with most recent security patches which now runs on my good old TB2-X30L / TAB2 A10-30:
lineage-16.0-20210328-UNOFFICIAL-TB2-X30L.zip | by kenschbacher9 for 10
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Thank you very much, install your rom on my TB2-X30F and it goes very well, the only drawback that I present is that the wifi is very slow but the rom is excellent, thank you very much for your work.
palamaro said:
it seems that google drives are off. Can someone re-upload please?
Click to expand...
Click to collapse
it still work. u just need to remove the space between htttp:// AND drive.google.com...
nonicktoday said:
The tablet can also run on LineageOS 16 which is Android 9.
As I saw that the guys in the Russian 4PDA-Forum had been able to create a LiOS16, I was able to make some adjustments and compile a ROM with most recent security patches which now runs on my good old TB2-X30L / TAB2 A10-30:
lineage-16.0-20210328-UNOFFICIAL-TB2-X30L.zip | by kenschbacher9 for 10
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Hi all, I've been trying to install the L16 version but I cannot install gapps or any zip from twrp. What is the procedure to install it correctly?
Boyalikus said:
I have followed the instructions and successfully installed LiOS14. Then, however, I have factory reset the tablet via Settings. Now it always boots to TWRP, no matter what I have tried I could not installed back the LiOS14 I only have TWRP right now.
Any help?
Click to expand...
Click to collapse
removing battery worked for me
Ive tried this tutorial and i bricked my tablet (i didn t backup the original firmware ) but i learned something new
for everybody who bricked their tablets lenevo tab 2 tb2 x30L do this:
1.first install Qualcomm_USB_Driver_v1.0 https://androiddatahost.com/nbyn6
2.install qfill 2.0.0.5 https://mydevfiles.com/download/qfil-tool-v2-0-0-5/
3.in qfill select flat build , progammer path is where you have your stock rom and load content same thing
4.press volume up +volume down and power button at the same time on your tablet *screen should be black*
5.press download content in qfil as soon as you connect the tablet to pc
stock firmware https://firmwarefile.com/lenovo-tab-2-tb2-x30l
^ english is not my first language so sorry for mistakes ^
[DELETED]
mutrin said:
After few day i find out solution how to install custom ROM to my Lenovo tablet. I think its first guide how to do it because every other guides were for TB2-X30F but not for TB2-X30L.
Installation guide:
FILES TO DOWNLOAD:
ALL FILES: https:// drive.google.com/drive/folders/1heVQAryphuXNVt5k-HsUhfRrVr9MV34D
ALL LINKS WORK ! JUST DELETE THE SPACE BEFORE drive.google.com...
1) On the tablet, at Settings, you must activate on the Developer Options the Bootloader Unlock (OEM unlocking) and USB debugging. Uncheck Verify apps over USB.
How to unlock Developer: https: //youtu.be/g5wkFAWDsg0
2) Download these files directly to your Android device, not to SD card.
a) https:// drive.google.com/file/d/1230xFbPA7DOGMhuX59yagEd6w1gNCI4o/view SuperSU-v2.79.zip (for me working only v2.79)
b) https:// drive.google.com/file/d/1vRW5RZixtNVfKbJ7nL2EUetANydfmLNg/view Gapps.zip (open_gapps-arm-7.1-micro-20180721)
b) https:// drive.google.com/file/d/13Mp8guzzOvb17s88IQyez_9reozpTNbw/view boot.img (from LiOS14-UNOFFICIAL-TB2-X30L)
3) Power off completely the tablet.
4) REMOVE SD CARD ! (because for me a part of system was installed on SD card).
5) Make sure you have a good cable so the connection between PC and tablet is perfect.
6) Download https: //drive.google.com/file/d/1XTDYs7kxagj-CXHsH_yyQnMXqYwAP_hK/view ADB and Fastboot to your PC .(here are the drivers too).
7) Unzip the zip archive and run with Administrator the apps from inside of the zip. To all the questions you must to press key Y to grant all the rights it needs.
8) Press and hold Volume up and plug in usb. Now you are in stock recovery menu.
9) From stock recovery select reboot to bootloader by using volume keys and power keys.
10) Wait about 5-10sec to tablet boot in bootloader mode. (shows lenovo logo in screen when ready)
11) Download the https:// drive.google.com/file/d/15IH55DgmD6SmlILjTukGeNcmYgUPcmCg/view recovery.img(its TWRP version for Lenovo Tab2 x30f so it wont work properly) and copy it into folder adb at local disk C (installed on step 7)
12) Run CMD with administrator and type cd C:\adb to select the adb folder.
13) In cmd type fastboot unlock-go and press enter. In case this command does not work, please try fastboot -s or fastboot oem unlock-go or fastboot oem unlock .
14) Flash recovery with command fastboot flash recovery recovery.img and then type fastboot boot recovery.img
15) From TWRP select Install and browse to emmc folder and then to your folder where you stored all files you downloaded.
(in bottom right corner you have Images... or Zips... here you can choose what type of file you want to install.
Install SuperSU-v2.79.zip
16) Now in menu select Wipe -> Advanced Wipe and check Dalvik Cache, Data and Cache. Wipe them.
17) Go back to menu and select Install. And install boot.img. At top of display check Boot and flash it.
19) Download https:// drive.google.com/file/d/1MlDxidIqLOZv_QZ91i8bsHgGdBMf7l9g/view LiOS14-UNOFFICIAL-TB2-X30L.zip and copy it into folder adb at local disk C (C:\adb).
18) Go to Menu select Advanced and open ADB Sideload. Go back to CMD on your pc and type
adb devices
If its your tablet properly connected you will see some letters and numbers and sideload. After that type
adb sideload LiOS14-UNOFFICIAL-TB2-X30L.zip
Now wait for finish the installation. If its installed corectly you will see Succesful at the top.
19) Repeate step number 15 and again install SuperSU-v2.79.zip (In installation you will see Boot image patcher)
20) Unplug your tablet from PC. And reboot it. First reboot may take 5-10 minutes and can reboot few times. DO NOT INTERRUPT THIS PROCESS.
21) After first start (set language, date..) Turn off devices.
22) Power on devices to recovery mode
(Press continuously the volume up and power key. When the screen on the tablet has started, release the power key and keep pressing the volume up key)
23) Now select again Install and install Gapps (open_gapps-arm-7.1-micro-20180721.zip). Then reboot it.
Now you have installed LiOS14-UNOFFICIAL (Android 7.1), with all stock apps(gapps) and also rooted device.
Click to expand...
Click to collapse
Will this work with x30F?