Related
June 02, 2015
Edit: If anyone has a link to the stock ROM for the Ascend G7, please let me know. I would love to make a custom ROM that doesn't take up 98% of all resources 99% of the time.
Hello everyone.
Before I get started, here is everything you need to know about this post.
- This root works as of June 29, 2015
- This is a rooting process for the Huawei Ascend G7
- I did not make this, so please consider supporting all mentioned sources
- I am a new user to XDA, but I've been developing for over a decade. I will regularly check this post if enough people who view it have questions
There are two parts to this process.
First, we unlock the bootloader
Second, we flash a recovery, and subsequently, SU (root)
Let's get started. This will take at least 16 hours. User interaction 5 minutes, and about a 16 hour wait for an email response from Huawei.
Also, I have a new account, so I cannot post links. So please bear with me. I will upload photos in as best order as I can.
Before we get started, please note that your phone will factory reset in this process.
First thing's first. The Ascend G7 requires an unlocked bootloader, before any root can take place. This is obviously temporary, until someone finds a circumvention. But for now, this is how this needs to be done.
Send an email to [email protected], with this format:
Dear Sir/Madam
Please may I request the bootloader unlock code for my Huawei Ascend G7?
Here are some Details:
Serial Number: (Found under Settings --> About phone --> Status)
IMEI: (Found under Settings --> About phone --> Status)
Baseband version: (Found under Settings --> About phone)
Please could you send me the code directly, as I cannot access the product ID on my device.
Thank You
Your name
This part is important. Sometimes, they do not even reply to your email(s). It is recommended - nay, required - for you to put "URGENT" in the subject field of the email. Something along the lines of "URGENT Request Bootloader Unlock Code." It would also be best if you mark your email as urgent/high priority, as well.
Meanwhile, while you wait for the email from them with your unlock code, (expect it to arrive the day after), download the Android SDK and the Java JDK, if you haven't already. What you need most are the SDK tools, which you can also download by typing in "SDK tools android" in Google and finding a download for the stand-alone tools.
Make sure Android Studio is updated, if you already have it. To make sure you have everything you need, open up command prompt in platform-tools, by holding shift and right clicking somewhere on the white, in the folder, (explained in attached picture).
Then, plug in your phone. Make sure USB debugging is enabled. To do so, go to Settings --> About phone --> Tap "Build Number" 7 times in a row. Then go back, and you will see "Developer options." Click on that, and enable USB debugging. Also, this optional, but I like to enable the "Stay Awake" function.
Make sure to accept any prompts that your phone will ask.
Then, go to the command prompt and type in "adb devices" without the quotations.
If you've done everything correctly so far, you should see something similar to the attached command prompt image file.
If everything checks out, let's proceed. If not, post below, and I, or fellow XDA users, will help you out.
Proceed to type in, "adb reboot bootloader" without the quotations, into the command prompt window that you opened. Your Ascend G7 should reboot into fastboot, where you will see something like the attached picture below, of the bootloader screen.
Except, it will say Phone Locked instead of Phone Unlocked.
Now, go back to your command line, and type in "fastboot reboot," to have access to your phone and its functions, while you wait for the email from Huawei.
`````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
Everything below this line should be done AFTER receiving a reply email from Huawei, with your unlock code.
Now, download the "PHILZ-TOUCH-6.rar" file. I cannot attach it here because it exceed file size limit. No virus, no surveys, here's the link, https/goo.gl/sxPv7I. Just add a colon and a forward slash after https. It is not a virus, in case your firewall or antivirus software brings up red flags. I will post the whole ZIP that I've downloaded from another website. There's a bunch of redundant elements in the folder, but just in case you know what you're doing and might need the tools, I'll keep them there. But all you will need are 2 things from the folder. They're mentioned next.
Go to where you extracted PHILZ to, and hold shift and right click and open a command window in that directory, and type in "adb devices" one more time to make sure your device is listed and connected. Then, type in "adb reboot bootloader," give it a second, and then when fastboot loads up, type in,
fastboot oem unlock 123456789123
Replace "123456789123" with the unlock code provided to you from the Huawei email. Give it a second, and then you should be good. It should now say "Phone Unlocked" in red. Now, type
"fastboot reboot"
in the command line (that was opened in the PHILZ folder), without quotations. Then type,
adb reboot bootloader, one more time, and then,
Navigate to the PHILZ folder, and run "install-windows.bat" as administrator, if using Windows.
If using Linux, run "Install-Linux.sh," and if using a Mac, run "Install-Max.sh"
Now, in CMD type,
fastboot boot recovery.img
Then, again type in
fastboot reboot
Your phone will reboot.
`````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
Aaaaaaand that's it! You should now be rooted. I recommend going to play store, and downloading a Root Checker to ascertain root access.
The last picture, where it says I have root access now, is a program called Root Genius. It's a one click tool to root any android device - obviously except the Ascend G7, (knowing my luck). But it does work as a root checker as well, if you want to ascertain root access. You can also download Root Checker from the play store; works more or less the same way.
Any questions, feel free to ask. Re-reading this, I could see if the instructions bring confusion to some. I will be glad to clarify any questions.
Works
Root confirmed G7-L01
some point that I did not understood
dear wertywhy,
your guide is really well done, but there are some points not clear to me
1) open up command prompt in platform-tools
what is platform-tools? A specific folder? I was not able to find it
2) if I open the command prompt from any forlder using the shift+right button as you said and then write adb devices I get this message:
'adb' is not recognized as in internal or external command operable progrma or batch file. What should I do?
3) when I connect the phone by usb cable, should I do something more (like enabling device file manager, pc suite or other options) or just connect it in charge only mode?
thank you for your time!
and... by the way, I'm really impressed that I got the anwer from Huawei with the code, that's really cool! Thank you!!
---------- Post added at 04:09 PM ---------- Previous post was at 03:19 PM ----------
I found the platform-tools folder, now if I type adb devices from a prompt open from that folder I don't get the error message anymore, but I get nothing, just the flashing prompt line (the huawei phone is on and usb connected to pc)
dear wertywhy,
your guide is really well done, but there are some points not clear to me
1) I had to install hi-suite to let the command adb work (before that adb was not finding the phone)
2) the file names of adb inside PHILZ_TOUCH is adb-windows and fastboot is fastboot-windows
3) when I input the command adb-windows devices inside the prompt inside the PHILZ folder the result is device offline, I could unlock the phone running the command from platform-tools directory (phone is unlocked now) but I can't run the command to root the phone until I have this "device offline"
Point 1 and 2 are not problem, just something that happened to me, but point 3 is stopping me, any idea how to solve point 3?
Frankleoni said:
3) when I input the command adb-windows devices inside the prompt inside the PHILZ folder the result is device offline, I could unlock the phone running the command from platform-tools directory (phone is unlocked now) but I can't run the command to root the phone until I have this "device offline"?
Click to expand...
Click to collapse
I'm having the same problem. I tried toggling usb debugging off and back on, tried another usb port and another PC (WIN 7 and 8) but none of that helped.
<device offline>
Frankleoni said:
dear wertywhy,
your guide is really well done, but there are some points not clear to me
1) I had to install hi-suite to let the command adb work (before that adb was not finding the phone)
2) the file names of adb inside PHILZ_TOUCH is adb-windows and fastboot is fastboot-windows
3) when I input the command adb-windows devices inside the prompt inside the PHILZ folder the result is device offline, I could unlock the phone running the command from platform-tools directory (phone is unlocked now) but I can't run the command to root the phone until I have this "device offline"
Point 1 and 2 are not problem, just something that happened to me, but point 3 is stopping me, any idea how to solve point 3?
Click to expand...
Click to collapse
Hi Frank,
Let's troubleshoot,
If it lists your device as offline, open up cmd (Run --> cmd), and type in,
taskkill /f /im adb.exe
Then, restart your G7; when it boots up, turn off and then on USB debugging, then find PHILZ, and retry point 3. If device is still offline, please let me know. The issue sounds like it's within the phone, not within ADB.
Alternatively, if that doesn't work, please delete PHILZ off your computer, and wherever it says "PHILZ" in my guide, replace it with the attached folder, (attached with this reply).
Cheers
PS, please make sure to check that your phone is not only in USB debugging mode, but that you've approved/allowed your computer access to your phone, (a prompt will show up on the Ascend G7 that asks you whether or not you trust your PC). And also make sure your phone isn't just set to "charge" when plugged in - activate/select MTP when you connect your phone to computer.
<device offline>
lume12 said:
I'm having the same problem. I tried toggling usb debugging off and back on, tried another usb port and another PC (WIN 7 and 8) but none of that helped.
Click to expand...
Click to collapse
Please refer to my reply to Frankleoni below.
Thank you for replying chy_vak,
I tried your solution in both the PHILZ folder and the new folder you attached. The device shows offline in both of them. However in the build-tools folder it shows online. The command line taskkill /f /im adb.exe terminated adb but the device still shows offline. I did everything in the exact order you wrote.
offline
search Kings Root via Google Chrome, install it and run it Easy and without chat with Huawei support
Kingroot Works like a charm !
@chy_vak, Thank you for your Work. 1st Part works great. 2nd Part went wrong, i dunno why i`ve tried every thing. I hate this Kingroot think, don`t touch it you never will leave it.
I have connect my G7 because unlock works. When i use CMD from Adb Tool it is connected, when i use command prompt from Philz he cant see and find the mobile?? Something for you absolute clearly, isn`t for other. Sry cant do screenshot with notebook and Win 10. have fun
Another Working Method to Root Huawei Ascend G7-L01/L03
Greetings!
I got an Ascend G7 Recently and I needed to Root it as soon as I got it. That's why I kind of broke my head looking for the current methods to do it. I found this one very promising so I started working. I followed the steps that were given to us one by one. Everything was alright until I tried to install the Windos-Installer.bat as administrator, I tried to many ways to this method work, but as much as I tried, I couldn't go with it, that's why I started working for 11 hours until I got it. This Worked for me, and I want to share it with you.
Please read the following notes before you start by rooting your device:
-As usually, do it at your own risk, I'm not responsable of any brick, or issue that damaged your device.
-This Method is working great on Windows 10
-This Method is working at 04/08/2015
-This Method, was tried by me, the directions I give to you, are based on my work by rooting my device and my experience, the software and files included were made and posted by someone else including the person who wrote this post: http://forum.xda-developers.com/gen...-confirmed-t3125621/post61122491#post61122491
-You can find screenshots of the procedure below
-You will need a microSD
-I strongly recommend you to have at least 80% of battery to avoid risks of bricks
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Here begins the directions:
1.- As has been said, you will need to unlock your device bootloader in order to root your phone. So as they said, you will need to write an email to Huawei. The mail you will send should look like this:
To: [email protected],
[email protected]
Subject: (URGENT) Unlock Bootloader
Model: Huawei G7-L03/L01 (Depends on your version)
Serial Number: (The one that comes in your Huawei's box)
IMEI: (You can get it on your box or in the info included on Configuration->About the phone->State
Product ID: (You can get it by typing on the Dial the next code: *#*#1357946#*#*)
I appreciate your concern of reading this. Waiting for a response.
Sincerely: (Your name)
After a while (Could take between 15 minutes and 16 hours depending on their time) A Huawei worker will answer you something like this:
Dear Customer,
Thank you for supporting Huawei device. My working number is ****. Your unlock code :************** , please keeping your unlock code properly.Thank you!
Huawei Terminal Company limited
1.1.- (OPTIONAL) As we are going to unlock the bootloader, we are going to make a factory reset, so I strongly recomend you to make a backup with the official huawei backup app in order to restore our settings, apps, and files.
1.2.- Once Again, as has been said, you will need to download the whole Android suite (Android Studio) the last version, update your java version, and download the last drivers for your device (A good way to do the last is by installing the HiSuite of Huawei).
1.3.- You need to activate the debug mode. You can find it in: Configuration->Developer Options->USB Debug (If you dont have the Developer options enabled, you have to go to Configuration->About the phone->Compilation And tap this last one 7 times)
2.- Download the .rar a the end of the page and extract it where you want, includes everything we are going to need. [You must put the file ''superuser.zip'' on your microSD (In the root of the microSD)]. After Downloading it, you must open a cmd window, running it as administrator. After that you will write:
cd (Here you should paste the ubication of your extracted File Ex: C:\Users\Josh\Downloads\Root Ascend G7)
Now you are in this ubication that includes adb. Write:
adb devices
You should see: List of devices attached, a code and the word device (There is a capture below). If you do, we can proceed.
3.- Type :
adb reboot bootloader
It should load a white page with the Android pet and the words FASTBOOT&RESCUE MODE Below there is the phrase ''PHONE LOCKED'' in color. Now type:
fastboot oem unlock *********** (The code Huawei gave to you)
Now your phone will make a factory reset. You will see how it reboots by itself and back to the default settings. You will need to activate the debug USB mode again. By this point its supposed your bootloader is now unlocked, to probe it, we will type again:
adb devices (To check it is correctly plugged)
Then we will type:
adb reboot bootloader
And now at the end of the page it should say: ''PHONE UNLOCKED''. If you do, we can proceed.
4.- At this point, you have two options: You can replace your stock recovery mode by a ClockWorkMod Recovery (I strongly recomend you to do that) or you can just ROOT the phone whithout replacing your stock recovery.
If you decided by replacing your stock recovery follow the next directions: We still have our CMD window opened and running adb while the phone it is on the bootloader mode. So now what you have to do it's to type:
fastboot flash recovery recoveryP.img (CMD will work and show a few commands)
And after that type:
fastboot reboot
Your phone will reboot again normally and we can proceed.
If you decided not to replace your stock recovery instead of typing ''fastboot flash recovery recoveryP.img'' you have to type:
fastboot boot recoveryP.img (This will send you directly to CWM recovery)
5.- You must acces to CWM Recovery.
If you installed it on your phone, turn off your device and then press the power button and vol+ until the Huawei logo appears, you should be in the recovery mode by now.
If you didn't install it, you already are in CWM recovery.
6.- With the vol and power buttons or the touch buttons at the end you should be able to navigate on the recovery. We go to:
Advanced Functions->Re-root System (SuperSu)->Yes-Apply SuperSu (You will see a few code at the end of the screen)
7.- Without leaving the recovery mode, go to the main screen and now we go to:
Install Zip->Choose zip from /sdcard->superuser.zip (The one that you previously putted on your microSD)->Yes-Install superuser.zip
(You will see again a few code at the end of the page) We go back to the main screen and Select:
Reboot System now
8.- It's supposed we are ROOT now. At first you will see the ''superuser'' app installed. To probe that works, Install ''android-terminal-emulator-1-0-70-multi-android.apk'' that it is included on the folder ''Terminal'' form the file you downloaded. Now open a new terminal window and type
su (If everything worked, superuser will ask for permissions)
8.1.- Restore your data with the Huawei Backup App
And that is all we have superuser acces now. If you have any question or issue let me know and I will help you.
https://mega.co.nz/#!Al9FxDBY!QHkljnnIbjURX01A59tJPNkAVQd3LbKTqRJHD_nNxrs
Thank you!
Cant boot into recovery
Hey guys so i tried following this procedure but it never works :/ if i flash the custom recovery and try boot into it, the phone directly goes to fastboot and rescue mood so cant boot into recovery, not even the stock recovery. if i try directly booting into the custom recovery it says dtb not found :/ can someone please help me?
the model is G7-L11 and the bootloader is unlocked
Engineer Mode Huawei Ascend G7 L03
Huawei Ascend G7 L03
Hi,
I have tried every thing to go into Engineer Mode.... Even Mobile Uncle Does not do that!
Please some one Help....
Huawei Ascend G7 L03
thanks for the translated philz touch
Hello everyone, I have a big problem with a Huawei G7. I did Philz Touch and Root. How can I go back to stock rom?
I've emailed Huawei 3 times now, left a week in between emails, and still haven't received my unlock code. Has anyone else had this issue?
Thanks
1.- As has been said, you will need to unlock your device bootloader in order to root your phone. So as they said, you will need to write an email to Huawei. The mail you will send should look like this:
To: [email protected],
[email protected]
Subject: (URGENT) Unlock Bootloader
Model: Huawei G7-L03/L01 (Depends on your version)
Serial Number: (The one that comes in your Huawei's box)
IMEI: (You can get it on your box or in the info included on Configuration->About the phone->State
Product ID: (You can get it by typing on the Dial the next code: *#*#1357946#*#*)
I appreciate your concern of reading this. Waiting for a response.
Sincerely: (Your name)
Does anyone have a good tutorial on how to flash twrp on the phone ? I've tried different things but it never works
any other method exept this email method? they wont answer me.
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.
I got the Dell Venue 8 7840 as an early Christmas gift (for myself, at Best Buy) and was saddened to learn getting root was (nearly) impossible. I followed various guides (many written this summer, before the latest batch of updates - as of December 2015) but found myself nowhere. Then, I found my answer.
Well, fellow root-wanter, I'm here to tell you it is possible, but it won't be easy.
How I Got Here
Right out of the box, I hastily updated to all the latest firmware updates from Dell. That was my biggest hurdle. So if you plan to do this and you haven't updated the device yet, DON'T UPDATE! Follow the several guides here to get root.
Too late? Already screwed the pooch? Read on.
Generally speaking, you need to do a few steps to get where you want to be. They are (roughly) as follows:
Unlock the Bootloader (developer settings change, adb commands)
Use the Intel Flash Tool to flash an earlier firmware, thus making your device able to boot a temporary ClockworkMod Recovery (CWM)
Use clockwork to wipe the system and cache, then reinstall the OS and SuperUser
Reboot and Enjoy!
Here's the long version of steps I took to make this possible:
Getting Started
As a prerequisite, please install at least the minimum adb/fastboot tools. For first timers, ADB is the Android Debug Bridge, which allows command-line access to system level tools when working with an Android device. It's the backbone of this entire process. Fastboot is a debug mode wherein you can run certain commands on the system, without the presence of an OS. As an Android user, and certainly as somebody who's found themselves on XDA, you should become familiar with fastboot and its abilities. You also can (and should) download the entire set of platform tools (part of the Software Development Kit) as a matter of course.
There are several other tools, firmware files, images, etc. that you will need. I've put all the files I used together in a single zip file, which you can download here:
Dell Venue 8 7840 Tools and Files (zip)
* (Thanks to the many contributors on this forum, like toxic_garden, enzymeyllw, mrgardiner and of course xBIGREDDx. Also Chainfire for SuperSU!)
Once you have all your files downloaded, you need to grab the Intel flash tool. My god is that tool a pain in the ballsack. It's also a necessary evil. Give Dell your firstborn, install the damn tool, and let's move on.
Seperately, you will need an SD card with the following files on it: update.zip and UPDATE-SuperSU-v2.46.zip
Ready to Go? Good.
First, enable Developer Options in Android. To do that, go into Settings >> About Tablet >> and tap the Build Number a bunch of times. After some vigorous tapping, a toast message (The little gray-oblong, semitransparent box near the bottom) will pop up and tell you "You're now a developer!". Congrats.
Go into Developer Options, look a few items down the list for "OEM Unlocking" and enable that sucker. If you were successful, it was the first step toward greatness.
If you have to back anything up, now's the time to do it. Because these next steps will wipe your device clean.
Install the Intel Drivers if you haven't already, and in Developer Options enable USB Debugging (it's not too far down below OEM Unlocking)
Some more drivers will install on your PC, and switch it over to Camera (PTP) mode when you see the selection option in the Notification tray. Eventually, if you played your cards right, you'll see an RSA Security request on your device, asking if you want to trust your PC and displaying a hex address. Click OK.
On your PC, find your platform-tools folder (in the Android SDK folder) or wherever you installed the minimal adb/fastboot tools.
In this folder, hold down Shift and right-click, then choose "Open Command Window Here" (alternately, go to the Start menu, type cmd and right-click "Run as Administrator" then navigate to your folder with adb.exe and fastboot.exe in it.)
Cool, take a breather. How are you feeling? Good? Good.
In the black window, type adb devices. You should see a string of numbers or numbers/letters and something like 'unauthorized' in the list. If it's blank, the ADB drivers are not installed properly. Go to your device manager, find anything with a question mark/yellow icon that looks like intel or android or moorefield, and install the drivers manually. You can search XDA if you get stuck on this step.
Back in the black window, type: adb reboot bootloader
Your device should immediately black out and, after a short while, go to the bootloader menu.
From here, go back to the black window and type: fastboot devices
You should see another set of numbers/letters and a word after. As long as you see something, you're golden. If it doesn't show up, you may need to double check those drivers. Another set of drivers will need to install for your device to be seen in this state. Just stick with it, you'll get there.
All good? Then type fastboot oem unlock
You'll get a warning, but just continue on.
Once unlocked, it's time to flash new firmware. Note: For me, this was absolutely the biggest PITA step. The tool was written with virtually no instructions. What follows is how I got it to work.
While you're still in the bootloader menu, you should see confirmation that your device is unlocked. YAY!
Use the menu to boot the device normally. Note: All your user data is gone, so your tablet will act like it's brand new again. Skip through as much BS as you can and get back to the home screen of your tab. Go to settings, and re-enable USB Debugging like last time.
While that's happening, go to your PC and fire up the Intel Phone Flash Tool. (Nice name, Intel.)
Load up the firmware folder "Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397", and specifically choose from the dropdown to flash the file: flash-DDO_BB.xml
If the tool thinks your device is not connected, that's okay. If the tool thinks your device is connected, that's OK too. Don't sweat it.
With the tool still running, as soon as its connected (allow Android Debugging, change to PTP or what have you) hit the Start to Flash button.
It will try about 100 times to find your device (you can see a little console log at the bottom of the tool) ... while it's searching, hold the power button on your device and POWER IT OFF. (Yes, off. Counter-intuitive, I know.)
As it powers off, it will enter some quasi-dream state that Intel dreamed up that will allow it to flash the firmware. Give it a bit of time, and eventually the firmware will flash successfully. HOORAY! You just paved the way for CWM.
Now go back to the folder of files and tools I told you to download, and find the folder "IntelAndroid-FBRL-05-16-2015-PTR" (alternately, search on XDA and find that tool yourself)
Load up the tool, hit accept, then choose option T4 (not T1-3, T4)
If you were successful, it will slowly begin copying over files and having its way with your tablet, and eventually some little white text will appear on your Tablet screen. Soon, ClockwordMod Recovery will start up.
From here, go to Mounts and Storage. Make sure /system is not mounted, and External SD is mounted. Wipe the /system partition, just to be sure. And again, make sure it's not mounted.
Go back to the main CWM screen, and choose "install zip from sd card", and then the option for the external sd.
Find and flash the update.zip file (this will give your cleared out tablet Android 5.1)
Now find and flash UPDATE-SuperSU-v2.46.zip
Go back to the main menu, and Wipe Cache Partition.
Back at the main menu, Reboot System Now.
If all went well and I didn't totally screw up this guide, your newly rooted tablet should boot up. It may appear to be stuck on the Dell loading screen a while, but it's not. Give it time, and Lollipop will come right up.
From here, download SuperUser and BusyBox from Google Play, if either of those things aren't present on your tablet. Now take advantage of Titanium Backup to remove all that unwanted crapware, and Greenify (at least) to keep those pesky apps at bay.
Enjoy! If this worked, please let me know. As I said, this is what worked for me - but everybody's situation is different, and I'm sorry if this did not work for you. Obligatory I am not responsible if your device bricks, dies or otherwise craps the bed. Use this guide at your own risk.
Some threads that helped me through, increased my sanity, and eased my upset stomach:
Toxic_Garden's Guide: http://forum.xda-developers.com/showpost.php?p=64391058&postcount=16
Mr Gardiner's Guides: http://forum.xda-developers.com/showpost.php?p=62833258&postcount=4, http://forum.xda-developers.com/dell-venue/general/7840-stuck-bootloop-bricked-t3178937
Enzymeyllw's Guide: http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
Insight from xBIGREDDx: http://forum.xda-developers.com/del...-8-7840-developer-files-posted-t3144232/page4
A side note: a few of those unbricking guides tried to have me use the adb shell to send the system image to the device, but I didn't find that necessary. Just flashing update.zip with CWM got me far enough along to get the tablet running. I'm not sure if that will come back to bite me in the ass, but hopefully not.
johnsag49 said:
I got the Dell Venue 8 7840 as an early Christmas gift (for myself, at Best Buy) and was saddened to learn getting root was (nearly) impossible. I followed various guides (many written this summer, before the latest batch of updates - as of December 2015) but found myself nowhere. Then, I found my answer.
Well, fellow root-wanter, I'm here to tell you it is possible, but it won't be easy.
How I Got Here
Right out of the box, I hastily updated to all the latest firmware updates from Dell. That was my biggest hurdle. So if you plan to do this and you haven't updated the device yet, DON'T UPDATE! Follow the several guides here to get root.
Too late? Already screwed the pooch? Read on.
Generally speaking, you need to do a few steps to get where you want to be. They are (roughly) as follows:
Unlock the Bootloader (developer settings change, adb commands)
Use the Intel Flash Tool to flash an earlier firmware, thus making your device able to boot a temporary ClockworkMod Recovery (CWM)
Use clockwork to wipe the system and cache, then reinstall the OS and SuperUser
Reboot and Enjoy!
Here's the long version of steps I took to make this possible:
Getting Started
As a prerequisite, please install at least the minimum adb/fastboot tools. For first timers, ADB is the Android Debug Bridge, which allows command-line access to system level tools when working with an Android device. It's the backbone of this entire process. Fastboot is a debug mode wherein you can run certain commands on the system, without the presence of an OS. As an Android user, and certainly as somebody who's found themselves on XDA, you should become familiar with fastboot and its abilities. You also can (and should) download the entire set of platform tools (part of the Software Development Kit) as a matter of course.
There are several other tools, firmware files, images, etc. that you will need. I've put all the files I used together in a single zip file, which you can download here:
Dell Venue 8 7840 Tools and Files (zip)
* (Thanks to the many contributors on this forum, like toxic_garden, enzymeyllw, mrgardiner and of course xBIGREDDx. Also Chainfire for SuperSU!)
Once you have all your files downloaded, you need to grab the Intel flash tool. My god is that tool a pain in the ballsack. It's also a necessary evil. Give Dell your firstborn, install the damn tool, and let's move on.
Seperately, you will need an SD card with the following files on it: update.zip and UPDATE-SuperSU-v2.46.zip
Ready to Go? Good.
First, enable Developer Options in Android. To do that, go into Settings >> About Tablet >> and tap the Build Number a bunch of times. After some vigorous tapping, a toast message (The little gray-oblong, semitransparent box near the bottom) will pop up and tell you "You're now a developer!". Congrats.
Go into Developer Options, look a few items down the list for "OEM Unlocking" and enable that sucker. If you were successful, it was the first step toward greatness.
If you have to back anything up, now's the time to do it. Because these next steps will wipe your device clean.
Install the Intel Drivers if you haven't already, and in Developer Options enable USB Debugging (it's not too far down below OEM Unlocking)
Some more drivers will install on your PC, and switch it over to Camera (PTP) mode when you see the selection option in the Notification tray. Eventually, if you played your cards right, you'll see an RSA Security request on your device, asking if you want to trust your PC and displaying a hex address. Click OK.
On your PC, find your platform-tools folder (in the Android SDK folder) or wherever you installed the minimal adb/fastboot tools.
In this folder, hold down Shift and right-click, then choose "Open Command Window Here" (alternately, go to the Start menu, type cmd and right-click "Run as Administrator" then navigate to your folder with adb.exe and fastboot.exe in it.)
Cool, take a breather. How are you feeling? Good? Good.
In the black window, type adb devices. You should see a string of numbers or numbers/letters and something like 'unauthorized' in the list. If it's blank, the ADB drivers are not installed properly. Go to your device manager, find anything with a question mark/yellow icon that looks like intel or android or moorefield, and install the drivers manually. You can search XDA if you get stuck on this step.
Back in the black window, type: adb reboot bootloader
Your device should immediately black out and, after a short while, go to the bootloader menu.
From here, go back to the black window and type: fastboot devices
You should see another set of numbers/letters and a word after. As long as you see something, you're golden. If it doesn't show up, you may need to double check those drivers. Another set of drivers will need to install for your device to be seen in this state. Just stick with it, you'll get there.
All good? Then type fastboot oem unlock
You'll get a warning, but just continue on.
Once unlocked, it's time to flash new firmware. Note: For me, this was absolutely the biggest PITA step. The tool was written with virtually no instructions. What follows is how I got it to work.
While you're still in the bootloader menu, you should see confirmation that your device is unlocked. YAY!
Use the menu to boot the device normally. Note: All your user data is gone, so your tablet will act like it's brand new again. Skip through as much BS as you can and get back to the home screen of your tab. Go to settings, and re-enable USB Debugging like last time.
While that's happening, go to your PC and fire up the Intel Phone Flash Tool. (Nice name, Intel.)
Load up the firmware folder "Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397", and specifically choose from the dropdown to flash the file: flash-DDO_BB.xml
If the tool thinks your device is not connected, that's okay. If the tool thinks your device is connected, that's OK too. Don't sweat it.
With the tool still running, as soon as its connected (allow Android Debugging, change to PTP or what have you) hit the Start to Flash button.
It will try about 100 times to find your device (you can see a little console log at the bottom of the tool) ... while it's searching, hold the power button on your device and POWER IT OFF. (Yes, off. Counter-intuitive, I know.)
As it powers off, it will enter some quasi-dream state that Intel dreamed up that will allow it to flash the firmware. Give it a bit of time, and eventually the firmware will flash successfully. HOORAY! You just paved the way for CWM.
Now go back to the folder of files and tools I told you to download, and find the folder "IntelAndroid-FBRL-05-16-2015-PTR" (alternately, search on XDA and find that tool yourself)
Load up the tool, hit accept, then choose option T4 (not T1-3, T4)
If you were successful, it will slowly begin copying over files and having its way with your tablet, and eventually some little white text will appear on your Tablet screen. Soon, ClockwordMod Recovery will start up.
From here, go to Mounts and Storage. Make sure /system is not mounted, and External SD is mounted. Wipe the /system partition, just to be sure. And again, make sure it's not mounted.
Go back to the main CWM screen, and choose "install zip from sd card", and then the option for the external sd.
Find and flash the update.zip file (this will give your cleared out tablet Android 5.1)
Now find and flash UPDATE-SuperSU-v2.46.zip
Go back to the main menu, and Wipe Cache Partition.
Back at the main menu, Reboot System Now.
If all went well and I didn't totally screw up this guide, your newly rooted tablet should boot up. It may appear to be stuck on the Dell loading screen a while, but it's not. Give it time, and Lollipop will come right up.
From here, download SuperUser and BusyBox from Google Play, if either of those things aren't present on your tablet. Now take advantage of Titanium Backup to remove all that unwanted crapware, and Greenify (at least) to keep those pesky apps at bay.
Enjoy! If this worked, please let me know. As I said, this is what worked for me - but everybody's situation is different, and I'm sorry if this did not work for you. Obligatory I am not responsible if your device bricks, dies or otherwise craps the bed. Use this guide at your own risk.
Some threads that helped me through, increased my sanity, and eased my upset stomach:
Toxic_Garden's Guide: http://forum.xda-developers.com/showpost.php?p=64391058&postcount=16
Mr Gardiner's Guides: http://forum.xda-developers.com/showpost.php?p=62833258&postcount=4, http://forum.xda-developers.com/dell-venue/general/7840-stuck-bootloop-bricked-t3178937
Enzymeyllw's Guide: http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
Insight from xBIGREDDx: http://forum.xda-developers.com/del...-8-7840-developer-files-posted-t3144232/page4
A side note: a few of those unbricking guides tried to have me use the adb shell to send the system image to the device, but I didn't find that necessary. Just flashing update.zip with CWM got me far enough along to get the tablet running. I'm not sure if that will come back to bite me in the ass, but hopefully not.
Click to expand...
Click to collapse
This is fantastic. Can you verify build and firmware versions?
I haven't tried to go back to Stagefright yet. Right now:
Software version: Venue 8 7840-user 5.1 LMY47I
Build: BBP803A171200DEL
@jumpup Why do you quote the first post ?
thedreamix said:
@jumpup Why do you quote the first post ?
Click to expand...
Click to collapse
Force of habit with the XDA premium mobile app.
There is a specific version number for firmware that will indicate if the post-Stagefright firmware is installed. Go in to the My Dell app, and from the top right-hand corner, select Device Info from the list of options.
See the attached screenshot for reference.
Hi John,
thank you for your work. I unlocked my device, but it won't let me get past step 23. What do you mean by turning off? Holding the off button for ten seconds? Holding it shortly, then select shut down? One more thing: It asks me whether I like to proceed with the image on my 7840.
This is my log for the 10sec version:
01/02/16 01:07:37.800 INFO : [Port 1/1/4] XFSTK-STATUS--Detecting Intel Device - Attempt #40
01/02/16 01:07:37.800 INFO : [Port 1/1/4] XFSTK-STATUS--Detecting Intel Device - Timeout
01/02/16 01:07:38.466 INFO : [Port 1/1/4] XFSTK-STATUS--Detecting Intel Device - Attempt #41
01/02/16 01:07:38.466 INFO : [Port 1/1/4] XFSTK-STATUS--Aborting download process.
01/02/16 01:07:38.466 INFO : [Port 1/1/4] xfstkFlashTool exited with error code 13 Unknown error!
01/02/16 01:07:38.468 ERROR : [Port 1/1/4] Command `"C:\Program Files (x86)\Intel\Phone Flash Tool Lite\xfstkFlashTool.exe" "-1" "D:\dell-venue-8-7840-dec-2015\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\dnx_fwr_blackburn_qs_rd_opensource.bin" "D:\dell-venue-8-7840-dec-2015\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\ifwi_blackburn_qs_rd_opensource.bin" "" "D:\dell-venue-8-7840-dec-2015\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\droidboot_dnx.img" "0x80000c27" "none" "none" "0"` failed
01/02/16 01:07:38.469 ERROR : [Port 1/1/4] Flash failed (Command type: Ifwi)
01/02/16 01:07:38.747 INFO : [Port 1/1/4] Device lost on 1/1/4
---------- Post added at 01:41 AM ---------- Previous post was at 01:14 AM ----------
Restarted laptop. It also says this before starting to flash:
01/02/16 01:37:29.545 INFO : OS version detected: Windows 8.1 (x64)
01/02/16 01:37:29.546 INFO : SSL supported: No
01/02/16 01:37:29.587 INFO : Disk space available on drive C:/ : 4.06 GB
01/02/16 01:37:29.642 INFO : Adb and fastboot binaries OK
01/02/16 01:37:29.912 INFO : Phone Flash Tool Lite initialized successfully
01/02/16 01:37:29.919 INFO : [Port 1/1/4] New device detected on 1/1/4 (id=0100030000000002)
01/02/16 01:38:08.931 WARNING: Bootloader DnX file not specified in flash file ("os_dnx" key)
01/02/16 01:38:09.115 INFO : Ready to flash!
01/02/16 01:38:09.125 INFO : Flash file D:\dell-venue-8-7840-dec-2015\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\flash-DDO_BB.xml [Default] loaded
Tourist06 said:
Hi John,
thank you for your work. I unlocked my device, but it won't let me get past step 23. What do you mean by turning off? Holding the off button for ten seconds? Holding it shortly, then select shut down? One more thing: It asks me whether I like to proceed with the image on my 7840.
This is my log for the 10sec version:
01/02/16 01:07:37.800 INFO : [Port 1/1/4] XFSTK-STATUS--Detecting Intel Device - Attempt #40
01/02/16 01:07:37.800 INFO : [Port 1/1/4] XFSTK-STATUS--Detecting Intel Device - Timeout
01/02/16 01:07:38.466 INFO : [Port 1/1/4] XFSTK-STATUS--Detecting Intel Device - Attempt #41
01/02/16 01:07:38.466 INFO : [Port 1/1/4] XFSTK-STATUS--Aborting download process.
01/02/16 01:07:38.466 INFO : [Port 1/1/4] xfstkFlashTool exited with error code 13 Unknown error!
01/02/16 01:07:38.468 ERROR : [Port 1/1/4] Command `"C:\Program Files (x86)\Intel\Phone Flash Tool Lite\xfstkFlashTool.exe" "-1" "D:\dell-venue-8-7840-dec-2015\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\dnx_fwr_blackburn_qs_rd_opensource.bin" "D:\dell-venue-8-7840-dec-2015\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\ifwi_blackburn_qs_rd_opensource.bin" "" "D:\dell-venue-8-7840-dec-2015\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\droidboot_dnx.img" "0x80000c27" "none" "none" "0"` failed
01/02/16 01:07:38.469 ERROR : [Port 1/1/4] Flash failed (Command type: Ifwi)
01/02/16 01:07:38.747 INFO : [Port 1/1/4] Device lost on 1/1/4
---------- Post added at 01:41 AM ---------- Previous post was at 01:14 AM ----------
Restarted laptop. It also says this before starting to flash:
01/02/16 01:37:29.545 INFO : OS version detected: Windows 8.1 (x64)
01/02/16 01:37:29.546 INFO : SSL supported: No
01/02/16 01:37:29.587 INFO : Disk space available on drive C:/ : 4.06 GB
01/02/16 01:37:29.642 INFO : Adb and fastboot binaries OK
01/02/16 01:37:29.912 INFO : Phone Flash Tool Lite initialized successfully
01/02/16 01:37:29.919 INFO : [Port 1/1/4] New device detected on 1/1/4 (id=0100030000000002)
01/02/16 01:38:08.931 WARNING: Bootloader DnX file not specified in flash file ("os_dnx" key)
01/02/16 01:38:09.115 INFO : Ready to flash!
01/02/16 01:38:09.125 INFO : Flash file D:\dell-venue-8-7840-dec-2015\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\flash-DDO_BB.xml [Default] loaded
Click to expand...
Click to collapse
The boot state he's talking about usually has your device appearing in Device Manager as "Intel Mooresfield Device". It's a maintenance mode for firmware flashing, etc.
A little trivia: the Dell Venue 8 7840 was Intel's initial foray into Android-on-Intel with its newer x86 boards. The Venue (along with the Lenovo Yoga 2 series) are fortunate enough to have this mode. That's why they're "unbrickable" to a large extent. The Venue was a joint venture with Intel's teams and is still their promoted flagship device for devs hopping on to the platform.
So how do I make it work? I didn't find a "Intel Mooresfield Device" in the device manager, but other entries for the tablet.
Settings: Tablet: OEM Unlocking on, USB debugging on
Computer: running Phone Flash Tool Lite. NOT running any other phone related stuff (e.g. ADB) after 2nd try.
A little more trivia: I actually won my tablet at an Intel fair stand, it had a developer sticker on it's back
Tourist06 said:
So how do I make it work? I didn't find a "Intel Mooresfield Device" in the device manager, but other entries for the tablet.
Settings: Tablet: OEM Unlocking on, USB debugging on
Computer: running Phone Flash Tool Lite. NOT running any other phone related stuff (e.g. ADB) after 2nd try.
A little more trivia: I actually won my tablet at an Intel fair stand, it had a developer sticker on it's back
Click to expand...
Click to collapse
CONGRATS ON THAT WIN! Which OS are you using do this?
Thanks! Best win since winning a sleigh as a child!
I'm using Windows 10 64, all updates installed .
Is there any other way to get that info? I went a little nuts when I got root and wiped out a lot of the dell software including my dell.
I'm still stuck at step 23, does anyone know how to get past it?
I'm stuck at 23/24 as well... my device goes black and the flash tool starts trying to do something then starts erroring out with connection failed messages before it finally gives up. Does this tool not work with Windows 10 64bit?
Log Attached
dpicts said:
I'm stuck at 23/24 as well... my device goes black and the flash tool starts trying to do something then starts erroring out with connection failed messages before it finally gives up. Does this tool not work with Windows 10 64bit?
Log Attached
Click to expand...
Click to collapse
Win10 64bit
Flash tool Writing process reach #40
flash failed
Shut down 7840 In writing process #1-30
success
I am getting:
(bootloader) Checking unlock authorization.
FAILED (remote: couldn't change state)
finished. total time: 0.271s
I have switched OEM Unlock on in the Dev Options...... I have another Venue 8 that it worked fine on. I have no idea what the issue is..
I found my issue. I was on the old firmware which did not support the unlock.
On that note why can we not just perm flash a recovery now that we have an unlocked bootloader?
dancrosoft said:
I found my issue. I was on the old firmware which did not support the unlock.
On that note why can we not just perm flash a recovery now that we have an unlocked bootloader?
Click to expand...
Click to collapse
I am stuck at the same place the others were. I dont think this method works any more.
Works great. I was able to follow directions as noted. Worked on Windows 10 X64, and turned off the power button by menu after 2 seconds running the Intel update, and when tablet was fully updated with latest Dell Firmware.
---------- Post added at 01:08 AM ---------- Previous post was at 01:06 AM ----------
I got an update for the Dell firmware. Is it something to install or avoid due to bootlooping and stuffs?
joeminati said:
Works great. I was able to follow directions as noted. Worked on Windows 10 X64, and turned off the power button by menu after 2 seconds running the Intel update, and when tablet was fully updated with latest Dell Firmware.
---------- Post added at 01:08 AM ---------- Previous post was at 01:06 AM ----------
I got an update for the Dell firmware. Is it something to install or avoid due to bootlooping and stuffs?
Click to expand...
Click to collapse
I'd avoid updating for now.
Not sure where to ask this... how can I install permanent CWM (or TWRP) recovery on my 7840? I saw the other thread about CWM 6.0.x but saw no mention of which models of Venue it actually worked on and don't want to brick my device trying it...
OFFICIAL ONEPLUS 2 STOCK RESET
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 3.0.2
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen 3.0.2 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.14 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.19_160604" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
2. Run the Qualcomm setup wizard (also located in the qc folder)
3. When setup completes, launch Command Prompt as an Administrator and type bcdedit /set testsigning on
4. Restart your computer. (Once it gets on, you should see a watermark stating Test Mode in the bottom right corner. If not, type bcdedit in Command Prompt as an Administrator to check if testsigning shows on. If not, repeat step 3.)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.19_160604 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 3).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
6. Launch Command Prompt as an Administrator and type bcdedit /set testsigning off and reboot. Your system should no longer be in Test Mode.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus.
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Finally Managed to get a hand on this after a late night session with OnePlus. Great that we now have the MM Stock Reset which should theoretically help to get back to stock regardless of the ROM, customizations etc.
I believe this is the best option to use to return to stock from CM.
fareed_xtreme said:
OFFICIAL ONEPLUS 2 STOCK RESET
CREDITS
OnePlus Team for the Files.
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Click to expand...
Click to collapse
Thank you for mentioning me, Great Work
Is it recommended to do this to make sure that the installation is well made?
I installed 3.0.2 via OTA but my battery life is mediocre(3 hours). I know that in my Samsung devices it was better to clean flash the room yourself rather than doing it via OTA but I don't know about oneplus 2.
Should I just factory reset it or maybe do this whole procedure ?(except step C)
mantiyeah said:
Is it recommended to do this to make sure that the installation is well made?
I installed 3.0.2 via OTA but my battery life is mediocre(3 hours). I know that in my Samsung devices it was better to clean flash the room yourself rather than doing it via OTA but I don't know about oneplus 2.
Should I just factory reset it or maybe do this whole procedure ?(except step C)
Click to expand...
Click to collapse
You have a few options.
1. This threads Stock Reset option guarantees your phone will be Stock OnePlus, just as a new phone (Bootloader Locked, Recovery Stock, Kernel Stock etc). However, it requires some time and effort. [Recommended]
2. Factory Reset may fix your Battery issue (not sure) but it is the quickest method.
3. You could use @Spannaa 's Fastboot images to flash all the images in this thread but via fastboot which is quicker and requires minimal setup. [Recommended]
Hello , after b3 command of the tools I FAILED appears . Tips ?
---------- Post added at 02:43 PM ---------- Previous post was at 02:14 PM ----------
Thank you. Solved !!
fareed_xtreme said:
You have a few options.
1. This threads Stock Reset option guarantees your phone will be Stock OnePlus, just as a new phone (Bootloader Locked, Recovery Stock, Kernel Stock etc). However, it requires some time and effort. [Recommended]
2. Factory Reset may fix your Battery issue (not sure) but it is the quickest method.
3. You could use @Spannaa 's Fastboot images to flash all the images in this thread but via fastboot which is quicker and requires minimal setup. [Recommended]
Click to expand...
Click to collapse
Hello again,
When you say ''to flash all the images in this thread'' do you mean the 1. OnePlus2 Stock Reset Oxygen OS 3.0.2 and the 2. Qualcomm Drivers Version 1.00.14 ???
Or does it mean that flashing via fastboot the spanna image I am flashing everything at once?
Thank you very much
mantiyeah said:
Hello again,
When you say ''to flash all the images in this thread'' do you mean the 1. OnePlus2 Stock Reset Oxygen OS 3.0.2 and the 2. Qualcomm Drivers Version 1.00.14 ???
Or does it mean that flashing via fastboot the spanna image I am flashing everything at once?
Thank you very much
Click to expand...
Click to collapse
My Friend, you need to do any one of the above 3 mentioned methods. You could:
1. Follow this guide, the first post which has all the details. This is the method used by OnePlus to restore your phone when you have issues.
3. You could alternatively flash via Fastboot using the images from the mentioned thread.
You chose either one of the above mentioned procedures. Not both. If you run into issues do let is know. The procedure is detailed and if you follow my guide to the dot, you should be all set in the first attempt itself (for Flashing method 1)
Thanks fareed_xtreme, everything went well. Good job !
Sim and wifi not detected!!
fareed_xtreme said:
OFFICIAL ONEPLUS 2 STOCK RESET
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 3.0.2
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen 3.0.2 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.14 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.19_160604" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
2. Run the Qualcomm setup wizard (also located in the qc folder)
3. When setup completes, launch Command Prompt as an Administrator and type bcdedit /set testsigning on
4. Restart your computer. (Once it gets on, you should see a watermark stating Test Mode in the bottom right corner. If not, type bcdedit in Command Prompt as an Administrator to check if testsigning shows on. If not, repeat step 3.)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.19_160604 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 3).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
6. Launch Command Prompt as an Administrator and type bcdedit /set testsigning off and reboot. Your system should no longer be in Test Mode.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus.
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Click to expand...
Click to collapse
I did as told and was able to boot up successfully. But unfortunately the sim and wifi are not getting detected...do you have any solution for this? Also the phone keeps rebooting at random...would be really thankful for a quick solution to this.
Thx!! My OnePlus 2 is almost dead. Fastboot recovery only works for CM recovery, and there is no ROM inside sdcard. I flash TWRP, but no working. ADB sideload, TZ version problem - no luck. Thank you for sharing this thread.
Now is back and alive again
muthukumarc said:
I did as told and was able to boot up successfully. But unfortunately the sim and wifi are not getting detected...do you have any solution for this? Also the phone keeps rebooting at random...would be really thankful for a quick solution to this.
Click to expand...
Click to collapse
Which version of OnePlus 2 do you have? I have tested this on the European version.
Try this, Re-Flash the whole package AGAIN. After the first boot, reboot into recovery and reset to factory defaults. If it still does not work out, then let me know.
fareed_xtreme said:
Which version of OnePlus 2 do you have? I have tested this on the European version.
Try this, Re-Flash the whole package AGAIN. After the first boot, reboot into recovery and reset to factory defaults. If it still does not work out, then let me know.
Click to expand...
Click to collapse
Thank you for the fast response...i have the A2003 that i bought in india...I am still having the same problem...flashed the os again and did a hard reset...but still sim and wifi are not detected.
Tryed this one but when i upgrade to 3.0.2or clean flash this my camera stays black. Any help for this?
muthukumarc said:
Thank you for the fast response...i have the A2003 that i bought in india...I am still having the same problem...flashed the os again and did a hard reset...but still sim and wifi are not detected.
Click to expand...
Click to collapse
Even I have an A2003, European version and Indian version are the same. Have you pressed the square button to verify if the Package you have downloaded is in good shape and not corrupted? Do check that.
Alternatively head over to this thread and try flashing through TWRP using the Fastboot package of 3.0.2.
Or you could flash the modem file manually if you know how it's done.
Also as a last resort, try flashing an older version of the stock reset (there will be a version 2.2.0 in the general section or through Fastboot using the thread provided above).
If after all this it still does not work, please open a ticket with OnePlus. Sorry for the inconvenience.
C.H.T.J. said:
Tryed this one but when i upgrade to 3.0.2or clean flash this my camera stays black. Any help for this?
Click to expand...
Click to collapse
Do follow the above recommendations. However, if it did not work for you with other ROMs, Resets or Fastboot Zips, then I am very sure, none of the above steps will be of much use. Maybe CM might help but again, it's a longshot. Best option for you is to open a Ticket with OnePlus as this looks more inclined towards a driver or hardware issue.
fareed_xtreme said:
Even I have an A2003, European version and Indian version are the same. Have you pressed the square button to verify if the Package you have downloaded is in good shape and not corrupted? Do check that.
Alternatively head over to this thread and try flashing through TWRP using the Fastboot package of 3.0.2.
Or you could flash the modem file manually if you know how it's done.
Also as a last resort, try flashing an older version of the stock reset (there will be a version 2.2.0 in the general section or through Fastboot using the thread provided above).
If after all this it still does not work, please open a ticket with OnePlus. Sorry for the inconvenience.
Do follow the above recommendations. However, if it did not work for you with other ROMs, Resets or Fastboot Zips, then I am very sure, none of the above steps will be of much use. Maybe CM might help but again, it's a longshot. Best option for you is to open a Ticket with OnePlus as this looks more inclined towards a driver or hardware issue.
Click to expand...
Click to collapse
Sorry for the delayed response...i tried the fastboot method as well i have wifi now but no sim yet... i think i found out the problem. The IMEI number seems to be missing... and i read that would be the case for sim not detected.... i tried lots of methods (trying to get into engineering mode & using terminal emulator) to rectify it but was unsuccessful... I think the methods i saw were all for mediatek phones...couldnt find one for qualcomm....do you know any right way for fixing the IMEI issue? Thank you so much for your help so far on this.
muthukumarc said:
Sorry for the delayed response...i tried the fastboot method as well i have wifi now but no sim yet... i think i found out the problem. The IMEI number seems to be missing... and i read that would be the case for sim not detected.... i tried lots of methods (trying to get into engineering mode & using terminal emulator) to rectify it but was unsuccessful... I think the methods i saw were all for mediatek phones...couldnt find one for qualcomm....do you know any right way for fixing the IMEI issue? Thank you so much for your help so far on this.
Click to expand...
Click to collapse
I don't have much information on this. If your IMEI doesn't show, it means that one of your device specific partition is corrupted (I guess it's EFS, not sure). If you have a nandroid backup of all your partitions, then you could use them to recover. Else, your options are limited and your only friend is Google search. This doesn't usually happen.
When everything is ok. Press the start button. and let the progress finish.
Click to expand...
Click to collapse
How much time it can take? Mine is going on for almost two hours now
Only Stop button is clickable and the square button too. Start,Enum, Exit are grayed out.(not clickable)
Btw i did press the stop button after getting frustrated for more than half an hour.
And then again performed integrity check. And then again pressed the start button.
When it finish, does it show some notification?
Chhatrapal said:
When everything is ok. Press the start button. and let the progress finish.
How much time it can take? Mine is going on for almost two hours now
Only Stop button is clickable and the square button too. Start,Enum, Exit are grayed out.(not clickable)
Btw i did press the stop button after getting frustrated for more than half an hour.
And then again performed integrity check. And then again pressed the start button.
When it finish, does it show some notification?
Click to expand...
Click to collapse
This could mean that it is still waiting for your device to connect. Have you double checked your drivers and have you found the different line in the flashing app? You will need to restart the process and follow it step by step again.
It will usually take between 8 - 12 minutes max to finish flashing in the app. Also once it's done, in the app all lines will turn green (if I recall correctly).
So i've tried this and various other methods along similar lines. The flashing tool finishes and goes green but then also goes red.
On the reboot, recovery is still missing and i have fastboot.
If i use 'fastboot continue', I boot into the rom for setup and everything starts to work. However, I don't have any recovery, so the phone does not boot. Bootloader is now locked too so I can't try to flash recovery.
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: