Unlocking->insecure boot->root->flash cm10 with amplifier support your Q without apk
!!!!!!THIS IS NOW ALL FIXED AND PROPERLY WORKING BY THESE INSTRUCTIONS HOPE THIS HELPS YOU ALL!!!!!!
Unlocking->insecure boot->root->flash cm10 with amplifier support your Q without
Q apk.
this is a guide I compiled from the following devs that are credited and thanked
below.
Apparently Google did not like that we are using our Q's again and have killed
the servers that host our Nexus Q apk, if you are currently logged into your Q
you will not notice it. If you try logging into another Q or relog into your Q for
the first time. It will not work any more.
I have 3 of these and want to keep the Q community alive, I needed to figure out
as many of you how to access your Q through adb if the app is dead to enable usb
debugging so you can load cheap cast and continue to use your Q.
This will get adb debugging back so you can load a custom recovery and get
cheapcast back running through CyanogenMod.
!!!!You will need a otg cable powered is a good idea these are $10.00 here ->
-------------------------------------------------------------------------------
To fastboot unlock your device / Credit and thanks to -> fiveipads
-------------------------------------------------------------------------------
1. cmd to platform-tools
2. Reboot to the bootloader -> cover your Q with your hand -> power on nexus Q as
soon as you see red remove your hand -> (will go solid red and you are in
bootloader)
3. Unlock your device* (with fastboot tool) (type) -> fastboot oem unlock
(immediately copy and paste this into tool and hit enter you have only 5 secs) ->
fastboot oem unlock_accept
4.Q will reboot and turn purple etc.
5.Unplug Q and restart in bootloader see #2. (type) -> fastboot getvar unlocked
(this verifies you unlocked your Q->should reply->unlocked:yes)IF NOT DO NOT
PROCEED TILL IT DOES.
-------------------------------------------------------------------------------
Load a unsecure boot image with adb enabled / Credit and thanks to -> ObsidianX
-------------------------------------------------------------------------------
1.Download -> http://forum.xda-developers.com/attachment.php?attachmentid=1563302&d=1355508721
2.This is a modified boot.img from the factory Nexus Q images that enables adb
debugging on boot in root mode.->Test before you flash!
3.Put the file you download into you platform-tools folder(make sure no other
images have the same name in that folder)
4.Flash the image -> (type in fastboot) -> fastboot flash boot boot-root.img
(image will write should say ok and writing boot etc.)
5.Pull the power on your q and restart the Q
-------------------------------------------------------------------------------
Load Clockwork Mod Recovery / Credit and thanks to -> Koush
-------------------------------------------------------------------------------
1.Download koush's ClockworkMod Recovery.
koush's ClockworkMod Recovery ->
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.3.1-steelhead.img
md5: dec2a809a20e8cb236ae092e71d8d5fe
2.Connect the Nexus Q to the computer via USB.
3.Make sure the fastboot binary is in your PATH or that you place the downloaded
image in the same directory as fastboot. (rename the downloaded recovery file
recovery-clockwork-6.0.3.1-steelhead.img to -> recoveryq.img to make it easy to
type)
4.Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader or by using the hardward -> cover your Q with your hand ->
power on nexus Q as soon as you see red remove your hand -> (will go solid red
and you are in bootloader)
5.Once the device is in fastboot mode, verify your PC sees the device by typing
-> fastboot devices
***If you don't see your device serial number, and instead see "<waiting for
device>", fastboot is not configured properly on your machine. See fastboot
documentation for more info.
6.FLASH ClockworkMod Recovery onto your device (type) -> fastboot flash recovery
recoveryq.img
(should confirm by okay if not do it again till it does)
7.(type) -> fastboot reboot (this will reboot your device to the factory startup
screen) -> (type) adb devices (make sure your device shows up) -> (type) -> adb
reboot recovery (you should be in clockworkMod recovery)
--------------------------------------------------------------------------------
Install Cyanogenmod to your Q through adb on Clockwork Mod / Credit and thanks to Cyanogen mod crew and hharte for amplifier support and Anthony Hopf for updated working zip file.
--------------------------------------------------------------------------------
1.Download the prebuilt release of CyanogenMod you wish to install.
Here is a build of CM10.1 from repo sync on 6/17/2013 for each of TAS5713 and SPIDF outputs:
Please go easy on the downloads or mirror these files if desired. They are on my private server so bandwidth is limited. *****IF YOU CAN MIRROR THESE LINKS CONTACT ME WITH THE LINK*****
TAS5713 (Audio Amplifier):
Download: https://www.dropbox.com/s/vk77uq7dmpazzpz/cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip (148MB)
MD5SUM: adc98db7a9905b89c0d2fa9eab601f58 *cm-10.1-20130617-UNOFFICIAL-steelhead_TAS5713.zip
SPDIF:
Download: http://www.magicandroidapps.com/download/cm-10.1-20130617-UNOFFICIAL-steelhead_SPDIF.zip (148MB)
MD5SUM: ec26a86a5011cf480a9efb3cee63e000 *cm-10.1-20130617-UNOFFICIAL-steelhead_SPDIF.zip
HDMI: Use stock CM 10.1 nightly build. found here ->http://get.cm/?device=steelhead
Note: If, after installing, you don't have any sound, then install gapps and download "Audio Manager" from the Play Store. Run Audio Manager and select the "Mute" profile, and then select the "Loud" profile.
2.Rename your cm10 file to -> cm10.zip (this will make it easier to type later)
3.Move your cm10.zip to your platform-tools folder again like you did the recoveryq.img file
4.To install boot into recovery mode (type) -> fastboot boot recovery.img (or if you are still at recovery ignore this)
5.When Q has reached recovery mode, push the cm10.zip to /sdcard using adb, (type) -> adb push cm10.zip /sdcard/
6.To push gapps (if desired download here -> http://goo.im/gapps/gapps-jb-20130301-signed.zip md5SUM: b7e53e96e1c8b1a1c4865bf29418c8e0 and rename to gapps.zip and move to platform-tools folder)(type) -> adb push gapps.zip /sdcard/
7.From within recovery, "install zip from sdcard" and browse to cm10.zip file After this has installed, it is a good idea to wipe data and cache.
8.Then install gapps (if desired) by again choosing "install zip from sdcard" and choosing the gapps.zip file.
9.If cm10.1 gets stuck in a boot loop, then you probably forgot to wipe. Reboot the Q back into fastboot as follows:
Unplug power for Nexus Q and wait about 10 seconds.
Plug Q back in.
When the LED lights up on the top of the Q, cover it with your hand until the LED ring turns red. This has to be done in less than one second. If you miss it, try again.
As soon as the ring is RED, remove your hand, and the Q should be in fastboot mode.
10.Now, you can "fastboot -w" to wipe, or "fastboot boot recovery.img" to boot into recovery and wipe using the menu
OR YOU CAN INSTALL THIS ICS BASED ROM BASED ON THE STOCK IMAGE HERE->
http://api.viglink.com/api/click?fo...=Download it&jsonp=vglnk_jsonp_13777850981938
YOU MUST USE ICS BASED GAPPS.
--------------------------------------------------------------------------------
Install Cheapcast to q with auto boot option / credit and thanks to -> Sebastian Mauer and other devs involved (YOU NOW NEED THE OTG CABLE AND A MOUSE)
--------------------------------------------------------------------------------
1.Start your q get the otg cable plug it in wait for the Q to boot all the way the plug the mouse into the otg cable it should work.
2.+Sebastian Mauer's CheapCast allows an Android device to act as a target for #chromecast enabled applications. Android device == Nexus Q; chromecast enabled application == +Google Play Music.
3.Go to the asop brower on the Q and go to this link -> http://www.androidfilehost.com/?fid=23060877489999380
4.Download the apk do not use the store version at this time it is broken.
5.Using a file explorer find and open the apk it will be in the downloads folder. (you may need to authorize installing 3rd party apps in the security menu) once installed open cheapcast tick enable on startup and start sevices button. Now reboot your Q using a reboot button apk from the store.
6.Now your Q will be recognized as a target for any Chromecast enabled app upon startup, like Google Play Music it will also work on youtube as I have verified this, however if using the steelhead internal amp zip it will not output sound except to the internal amp. Use your device (I'm using my S4 GPE) to start and enjoy!
7.If for some reason the apk stops working on boot you may need to reinstall it and restart it for on boot starting. Your Q will now be on all day long so unplug it when not using it. until someoen makes a remote turn off apk or something.
Edit: All the XDA folks who put up a bounty? Please donate to Sebastian - grab the CheapCast app and hit the donate button!
______________________________________________________________________________
(If your Q boots up and the resolution looks wrong you will need to use a different tv or monitor ot happened to me)
I hope this help anyone like me who thought everything on this forums was way to hard to find and put together, this is all tested and is done how I typed it in.
If you mess it up DO NOT COME TO ME CRYING!
If I helped you, click my thanks button and send your donations to all the devs mentioned above, also donate to cheap cast to make it stay around.
Obviously Google does not want us to keep using our Q balls so make sure we keep devs working for us here by posting and showing interest.
Thanks- Ian
OTG cable
At what point did you need an OTG cable? Looks like you did all this via PC? Thanks so much!!!! I have two of them, both had USB debugging enabled until I did factory resets on them this morning. <sigh> The folks at Google were very nice and excruciatingly unhelpful when I called them about it this afternoon. But... apparently a "Nexus Q expert" will get back to me very soon, and I'm sure the response will be the standard Google canned response regarding the Q.
Still trying to figure out how to authorize adb debugging with only 1 usb port please someone explain
Figured it out
The TAS5713 build wont download properly for me, i have tried several times and it keeps downloading as a 121MB file rather than the 148MB that the post states, can someone post a working build?
Thankyou for the guide, can i suggest you add a note about using adb while in CWM, i had to use the universal naked drivers to get the Q to appear in adb devices
unknownkwita said:
The TAS5713 build wont download properly for me, i have tried several times and it keeps downloading as a 121MB file rather than the 148MB that the post states, can someone post a working build?
Thankyou for the guide, can i suggest you add a note about using adb while in CWM, i had to use the universal naked drivers to get the Q to appear in adb devices
Click to expand...
Click to collapse
I will try that later and report back if it works for me
This is now all fixed and working correctly!
im hosting the rom Anthony uploaded in this g+ post. To the best of my knowledge it is the TAS5713 CM10.1 rom that was originally modified by hharte. Ill keep it up for the foreseeable future. I TAKE NO RESPONSIBILITY FOR ANYTHING.
https://docs.google.com/file/d/0B8a2mhiG243Ja1lqc0xVQzAwdjQ/edit?usp=sharing
Could someone please post a video on youtube of how to do this?
dts924s said:
Could someone please post a video on youtube of how to do this?
Click to expand...
Click to collapse
Seriously....read man....... its laid out exactly how to do it.
If you need a video you do not need to be hacking your Q
ianandamy said:
This is now all fixed and working correctly!
Click to expand...
Click to collapse
Does the amplifier, optical out and HDMI work or does only one of the outputs work depending on the ROM installed?
Thank you.
kario said:
Does the amplifier, optical out and HDMI work or does only one of the outputs work depending on the ROM installed?
Thank you.
Click to expand...
Click to collapse
EVERYTHING DEPENDS ON THE ROM INSTALLED.
i WOULD USE THE SINGULARITY PROJECT ROM AS IT REMAINS ALL INTACT.
5.Flash the image -> (type in fastboot) -> fastboot flash boot-root.img
Should be: fastboot flash boot boot-root.img
ianandamy said:
EVERYTHING DEPENDS ON THE ROM INSTALLED.
i WOULD USE THE SINGULARITY PROJECT ROM AS IT REMAINS ALL INTACT.
Click to expand...
Click to collapse
Once this rom is installed how does one get past the nexus q welcome screen?
I still can't believe that CM didn't integrate the amp functionally in their ROM..
watso4183 said:
Once this rom is installed how does one get past the nexus q welcome screen?
Click to expand...
Click to collapse
Hit the "home" key on your KB.
Lokifish Marz said:
Hit the "home" key on your KB.
Click to expand...
Click to collapse
Is there a way yo get your ROM to boot to the launcher and not to the nexus q screen? If so can you give me the adb cmds??
ianandamy said:
Is there a way yo get your ROM to boot to the launcher and not to the nexus q screen? If so can you give me the adb cmds??
Click to expand...
Click to collapse
Remove or rename AtHomeThemeService.apk, HubBroker.apk and Visualizer.apk from v1.0.2 and flash it. This will remove the stock Q services/frontend without breaking the audio output.
Thanks for the great guide, I just bought my Q a few days ago. I will definitely try this out. It is good to know, that the community is still alive.
Sent from my Nexus S using Tapatalk 4
Load a unsecure boot image with adb enabled / Credit and thanks to -> ObsidianX
-------------------------------------------------------------------------------
1.Download -> http://forum.xda-developers.com/atta...2&d=1355508721
2.This is a modified boot.img from the factory Nexus Q images that enables adb
debugging on boot in root mode.->Test before you flash!
3.Put the file you download into you platform-tools folder(make sure no other
images have the same name in that folder)
4.This is to test it first before you permanatly install it -> (type in fastboot)
-> fastboot boot boot-root.img (If the device reboots and the mute light goes
from red to off then you've successfully booted! Run `adb devices` to ensure it's
showing up and that you can connect to it. If all goes well (which it should)
then you can flash the boot image)
5.Flash the image -> (type in fastboot) -> fastboot flash boot-root.img
(image will write should say ok and writing boot etc.)
6.Pull the power on your q and restart the Q
-------------------------------
you have fastboot flash boot-root.img
its supposed to be-- fastboot "flash boot" boot-root.img
Related
This is long, but it's nice for noobs because it's detailed. It's honestly kind of fun, I promise. I'm assuming you have WINDOWS. This is based off of the guide by torxx!. It's modified because some of the info is outdated (you don't have to flash the boot.mg separately, for example). If you are NOT a noob you can just look at the "overview" for each step. This will work with all versions of the HTC One, assuming the kernel works. I have only tested the kernel with the T-mobile variant because that's what I have.
UNLOCKING YOUR DEVICE WILL WIPE YOUR DEVICE. THIS IS A SECURITY FEATURE. BACKUP FIRST.
Part 1- gaining unlock token
Overview: go to htcdev.com and unlock bootloader
Be sure you've turned off fast boot option in power menu; usb debugging should be on (settings -> developer options).
Go to http://www.htc.com/www/software/htc-sync-manager/[1] and install HTC SYNC. Alternatively, if you know what you're doing, you can install these drivers:
x86 http://www.mediafire.com/?qabo1tue2v1ky75 x64 http://www.mediafire.com/?8dl8s3l9mr6ggr9
Go on http://www.htcdev.com[4] and create yourself an account on HTCDEV.
Download these adb/fastboot files: http://d-h.st/RvD
Make a new folder anywhere. We'll use C:/fastboot as an example.
Extract the zip downloaded to the new folder
Go Here http://www.htcdev.com/bootloader/[6] and select "All Other Supported Models" and "then begin unlock bootloader" (check the boxes, click proceed, all that good stuff). YOU CAN IGNORE THE DIRECTIONS THAT THEY TELL YOU (and follow this guide instead).
Power off your phone. Power your phone on by holding power and volume down.
Highlight 'Fastboot' the volume buttons then press power to "select".
Plug your phone into your PC and open a Command Prompt. (windows XP - Click Start > Run > type CMD in box then press OK; Windows 7 - Click Start > type CMD in search box then press Enter) Change directory to your folder where we put fastboot files by typing cd c:\fastboot for example.*
*Alternatively, you can just hold down shift and right click in the folder and select "open command window here". Neat huh?
Type this into your command prompt window: fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files
Type this into your command prompt window: fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol+ to accept and power to confirm.
Part 2
Overview: flash your recovery. Boot into recovery. Turn phone off if it boots into OS. Boot into back into recovery. You're done!
Download a recovery:
TWRP (the one I use): http://forum.xda-developers.com/showthread.php?t=2173870
CWM 2: http://forum.xda-developers.com/showthread.php?t=2172979
CWM: http://forum.xda-developers.com/showthread.php?t=2173863
Place the Recovery file to the folder where the fastboot.exe is.
Same thing as above- boot (volume down + power) into the bootloader and highlight 'Fastboot' the volume buttons then press power to "select".
Do the same thing as with the command prompt above. This time, however, you'll be typing:
fastboot flash recovery "name_of_the_recovery.img"
For example:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
then type:
fastboot erase cache
From the menu, boot into recovery (use volume to move up and down, power to select). The phone might boot to the OS instead of recovery, don't worry!
Turn off phone then turn on (while holding volume down) to boot back into the bootloader.
TAMPERED shows up, boot into recovery and now your recovery should be working!
Part 3- obtaining root
Overview: flash a super tool
Download a super user tool for root:
SuperSU (I use this one): http://forum.xda-developers.com/showthread.php?t=1538053
SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Alternatively, download this: http://forum.xda-developers.com/showthread.php?t=2266025. This is a stock rooted rom for T-Mobile. If you download and flash this instead of the super user tool, you're done. (This rom includes super user)
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip super user tool to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
If you are a t-mobile user you're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead.
I recommend these kernels: http://forum.xda-developers.com/showthread.php?t=2255900 or http://forum.xda-developers.com/showthread.php?t=2233665&highlight=menu
Download it.
Installing custom rom/kernel ("flashing a rom")
Overview: Download Rom, boot into recovery and wipe and then flash.
According to Shenye, even though your device is s-on, you can still flash boot now. So just do this:
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip kernel/cutom rom to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
ixrs said:
This is long, but it's nice for noobs because it's detailed. It's honestly kind of fun, I promise. I'm assuming you have WINDOWS. This is based off of the guide by torxx!. It's modified because some of the info is outdated (you don't have to flash the boot.mg separately, for example). If you are NOT a noob you can just look at the "overview" for each step. This will work with all versions of the HTC One, assuming the kernel works. I have only tested the kernel with the T-mobile variant because that's what I have.
UNLOCKING YOUR DEVICE WILL WIPE YOUR DEVICE. THIS IS A SECURITY FEATURE. BACKUP FIRST.
Part 1- gaining unlock token
Overview: go to htcdev.com and unlock bootloader
Be sure you've turned off fast boot option in power menu; usb debugging should be on (settings -> developer options).
Go to http://www.htc.com/www/software/htc-sync-manager/[1] and install HTC SYNC. Alternatively, if you know what you're doing, you can install these drivers: x86 http://www.mediafire.com/?qabo1tue2v1ky75 x64 http://www.mediafire.com/?8dl8s3l9mr6ggr9
Go on http://www.htcdev.com[4] and create yourself an account on HTCDEV.
Download these adb/fastboot files: http://d-h.st/RvD
Make a new folder anywhere. We'll use C:/fastboot as an example.
Extract the zip downloaded to the new folder
Go Here http://www.htcdev.com/bootloader/[6] and select "All Other Supported Models" and "then begin unlock bootloader" (check the boxes, click proceed, all that good stuff). YOU CAN IGNORE THE DIRECTIONS THAT THEY TELL YOU (and follow this guide instead).
Power off your phone. Power your phone on by holding power and volume down.
Highlight 'Fastboot' the volume buttons then press power to "select".
Plug your phone into your PC and open a Command Prompt. (windows XP - Click Start > Run > type CMD in box then press OK; Windows 7 - Click Start > type CMD in search box then press Enter) Change directory to your folder where we put fastboot files cd c:\fastboot*
*Alternatively, you can just hold down shift and right click in the folder and select "open command window here". Neat huh?
Type this into your command prompt window: fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files
Type this into your command prompt window: fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol+ to accept and power to confirm.
Part 2
Overview: flash your recovery. Boot into recovery. Turn phone off if it boots into OS. Boot into back into recovery. You're done!
Download a recovery:
TWRP (the one I use): http://forum.xda-developers.com/showthread.php?t=2173870
CWM 2: http://forum.xda-developers.com/showthread.php?t=2172979
CWM: http://forum.xda-developers.com/showthread.php?t=2173863
Place the Recovery file to the folder where the fastboot.exe is.
Same thing as above- boot (volume down + power) into the bootloader and highlight 'Fastboot' the volume buttons then press power to "select".
Do the same thing as with the command prompt above. This time, however, you'll be typing:
fastboot flash recovery name_of_the_recovery.img
For example:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
then type:
fastboot erase cache
From the menu, boot into recovery (use volume to move up and down, power to select). The phone might boot to the OS instead of recovery, don't worry!
Turn off phone then turn on (while holding volume down) to boot back into the bootloader.
TAMPERED shows up, boot into recovery and now your recovery should be working!
Part 3- obtaining root
Overview: flash a super tool
Download a super user tool for root:
SuperSU (I use this one): http://forum.xda-developers.com/showthread.php?t=1538053
SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Alternatively, download this: http://forum.xda-developers.com/showthread.php?t=2266025. This is a stock rooted rom. If you download and flash this instead of the super user tool, you're done. (This rom includes super user)
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip super user tool to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
If you are a t-mobile user you're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead.
I recommend these kernels: http://forum.xda-developers.com/showthread.php?t=2255900 or http://forum.xda-developers.com/showthread.php?t=2233665&highlight=menu
Download it.
Installing custom rom/kernel ("flashing a rom")
Overview: Download Rom, boot into recovery and wipe and then flash.
According to Shenye, even though your device is s-on, you can still flash boot now. So just do this:
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip kernel/cutom rom to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
Click to expand...
Click to collapse
Thanks for this awesome tutorial man. It definitely should help give noobs a much better understanding!
Sent from my HTC One using xda premium
thanks! this worked great. perfect for all the noobs
Thanks!! I was on the fence about rooting (since the one is so great out of the box) but had an immediate need for tethering. You got me up and running in ~20 Minutes!!
Glad to hear! I think you may have rooted your phone faster than me, lol.
Thank you for this. I am on the fence about which new device i will be purchasing and good to know someone went to the trouble with rooting instructions
rolling56 said:
Thank you for this. I am on the fence about which new device i will be purchasing and good to know someone went to the trouble with rooting instructions
Click to expand...
Click to collapse
Thanks for your kind words! I tried hard to make these instructions as easy as possible, it looks like others found it easy but if you have any questions let me know.
im having trouble unlocking. after i get the unlock code and put it in my folder, i do the cmd 'fastboot unlocktoken Unlock_code.din'. but i get an error "cannot load Unlock_code.bin". am i missing something?
OK
I'll test it out on mines here and let you know
msterner123 said:
im having trouble unlocking. after i get the unlock code and put it in my folder, i do the cmd 'fastboot unlocktoken Unlock_code.din'. but i get an error "cannot load Unlock_code.bin". am i missing something?
Click to expand...
Click to collapse
Did you change directory to that folder?
Can you take a screenshot?
ixrs said:
Did you change directory to that folder?
Can you take a screenshot?
Click to expand...
Click to collapse
Worked like a champ! Thanks! I can't believe I missed that.
Does anyone know where I can find the stock ROM for T-Mobile to flash back to stock?
kgor93 said:
Does anyone know where I can find the stock ROM for T-Mobile to flash back to stock?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2276446
Seems to be where the stock stuff is at.
ixrs said:
http://forum.xda-developers.com/showthread.php?t=2276446
Click to expand...
Click to collapse
Thank you! I've been looking all over for that. Guess it was finally posted today.
kgor93 said:
Thank you! I've been looking all over for that. Guess it was finally posted today.
Click to expand...
Click to collapse
The only problem is that it has not been zipped, so we cannot use it to flash back to stock yet. Once it does, I'm going to be all over it! I wish I had been a bit more patient and just stuck out stock a few days more. I would've been able to realize how much disabling of installed apps just through the HTC settings menu. Not everything can be "disabled", but quite a bit can...
One of the few times where I think stock software is pretty good! Props to HTC!
I've heard this kinda thing voids the warranty, is that the case for the t-mobile 0ne?
Great tutorial but as usual I have been having saveer problems getting the HTC device to install properly so it can be detected in fastboot and recovery. Have been trying on both my laptop and desktop all day...
whitephenix said:
Great tutorial but as usual I have been having saveer problems getting the HTC device to install properly so it can be detected in fastboot and recovery. Have been trying on both my laptop and desktop all day...
Click to expand...
Click to collapse
Where are you stuck? I heard there was a problem with Win 8 x64 on usb 3.0.
Their was a problem for me with Windows 7 pro on my desktop but i finaly got it to work on my laptop.. I am led to think due to previous issues ultimate works better than pro or perhaps my hardware configuration on my homebrew leads windows to have certain comparability issues... The issue is spacifically with hardware detection and driver install errors. But like I said I got it to work on my laptop.
Sent from my HTC One using xda app-developers app
How easy is it to revert back to stock if you decide you don't want to use a custom rom anymore? Are factory images available to flash? Is it as easy as Samsung phones?
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.
Full Disclaimer: All credit for this goes to @enzymeyllw, whose guide I followed. It looks like that guide has gone offline (and has been cloned on a few dozen shameless websites), so I thought I'd rewrite it for the sake of anyone else needing help. All of the files can be found around this site, and I'll do my best to update this later with links. But for now, I'll post the instructions. Additional thanks goes to @xBIGREDDx and @anggusss. Hard to imagine my device has been bricked for the last 9 months... (Also, kinda funny how I just posted this and it has already been ripped off on >3 other websites.)
What you'll need:
Phone Flash Tool: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Open-Source Firmware Files: http://opensource.dell.com/releases...s_rd_opensource-blankphone-userdebug-1397.zip
Tethered Root for Windows (Thanks to @social-design-concepts for this): http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
-or-
Tethered Root for Linux / Mac (Thanks to @vampirefo for this): http://forum.xda-developers.com/dell-venue/general/linux-tethered-cwm-recovery-version-t2963104
System and Boot Images (Thanks to @xBIGREDDx for these):
- System.img: https://mega.co.nz/#!w9AjBCSI!YdQenTLDVVk0M9xx1LJT1OnKq5VhESgiyULA1FVIA8A
- Boot.img: https://mega.co.nz/#!Fk4FUSza!1gY1RjvnEI_HS0zk17WTHiywXFWc1VOCH-P2V5fVFPI
1. Phone Flash Tool
- Install USB drivers (if on Windows)
- Install Phone Flash Tool Lite
- Run PFT, open "Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397.zip"
- Select "flash-DD0_BB.xml" and flash it
- Tablet will restart in bootloader, flashing isn't done yet, so wait
- Sometimes it can be hard to get the progress bar past 4% before things fail. Just keep trying if this happens, it'll randomly work.
2. Tethered Recovery ("IntelAndroid-FBRL-07-24-2015.7z")
- Unpack the system image (from "system.zip") to a convenient directory
- With tablet still in Bootloader mode, open app, select CWM mode, then T4
- Phone will restart in CWM once everything loads
3. Flash system
- Go to the mounts / format area, format "/system" and then unmount it
- Insert Micro SD card and mount it
- Format "/external_sd"
- On computer, type "adb push <path-to-system.img> /external_sd/", wait for it to finish
- When finished, type "adb shell" to enter the device shell (make sure the prompt is "~ #" to make sure you are root (or type "whoami" at the prompt to confirm root)
- (If not root, restart to bootloader and trigger the tethered recovery again. You should be root this time.)
- Type in "dd if=/external_sd/system.img of=/dev/block/by-name/system" and wait for it to finish
- When finished, type "exit" on your computer to close the shell
- Reboot the device (to bootloader)
4. Flash boot
- Back on the computer, type in "fastboot devices" to confirm the tablet is connected
- Type "fastboot flash boot <path-to-boot.img" in order to flash the boot
5. Reboot
- On the device, tell it to boot normally
- Wait. It's a first-boot so it's gonna be a bit slow as the cache is built and whatnot
6. Enjoy!
7. (Optional) Root using the Update-SU.zip using the tethered mode again.
I noticed that it won't take any updates so this leaves you vulnerable to the Stagefright bug. It also sometimes boots to the bootloader and waits to you to select normal boot. Sorry. (Anyone know how to help?)
wirebook said:
Full Disclaimer: All credit for this goes to @enzymeyllw, whose guide I followed. It looks like that guide has gone offline (and has been cloned on a few dozen shameless websites), so I thought I'd rewrite it for the sake of anyone else needing help. All of the files can be found around this site, and I'll do my best to update this later with links. But for now, I'll post the instructions. Additional thanks goes to @xBIGREDDx and @anggusss. Hard to imagine my device has been bricked for the last 9 months... (Also, kinda funny how I just posted this and it has already been ripped off on >3 other websites.)
What you'll need:
Phone Flash Tool: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Open-Source Firmware Files: http://opensource.dell.com/releases...s_rd_opensource-blankphone-userdebug-1397.zip
Tethered Root for Windows (Thanks to @social-design-concepts for this): http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
-or-
Tethered Root for Linux / Mac (Thanks to @vampirefo for this): http://forum.xda-developers.com/dell-venue/general/linux-tethered-cwm-recovery-version-t2963104
System and Boot Images (Thanks to @xBIGREDDx for these):
- System.img: https://mega.co.nz/#!w9AjBCSI!YdQenTLDVVk0M9xx1LJT1OnKq5VhESgiyULA1FVIA8A
- Boot.img: https://mega.co.nz/#!Fk4FUSza!1gY1RjvnEI_HS0zk17WTHiywXFWc1VOCH-P2V5fVFPI
1. Phone Flash Tool
- Install USB drivers (if on Windows)
- Install Phone Flash Tool Lite
- Run PFT, open "Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397.zip"
- Select "flash-DD0_BB.xml" and flash it
- Tablet will restart in bootloader, flashing isn't done yet, so wait
- Sometimes it can be hard to get the progress bar past 4% before things fail. Just keep trying if this happens, it'll randomly work.
2. Tethered Recovery ("IntelAndroid-FBRL-07-24-2015.7z")
- Unpack the system image (from "system.zip") to a convenient directory
- With tablet still in Bootloader mode, open app, select CWM mode, then T4
- Phone will restart in CWM once everything loads
3. Flash system
- Go to the mounts / format area, format "/system" and then unmount it
- Insert Micro SD card and mount it
- Format "/external_sd"
- On computer, type "adb push <path-to-system.img> /external_sd/", wait for it to finish
- When finished, type "adb shell" to enter the device shell (make sure the prompt is "~ #" to make sure you are root (or type "whoami" at the prompt to confirm root)
- (If not root, restart to bootloader and trigger the tethered recovery again. You should be root this time.)
- Type in "dd if=/external_sd/system.img of=/dev/block/by-name/system" and wait for it to finish
- When finished, type "exit" on your computer to close the shell
- Reboot the device (to bootloader)
4. Flash boot
- Back on the computer, type in "fastboot devices" to confirm the tablet is connected
- Type "fastboot flash boot <path-to-boot.img" in order to flash the boot
5. Reboot
- On the device, tell it to boot normally
- Wait. It's a first-boot so it's gonna be a bit slow as the cache is built and whatnot
6. Enjoy!
7. (Optional) Root using the Update-SU.zip using the tethered mode again.
I noticed that it won't take any updates so this leaves you vulnerable to the Stagefright bug. It also sometimes boots to the bootloader and waits to you to select normal boot. Sorry. (Anyone know how to help?)
Click to expand...
Click to collapse
Any news? I'm stuck at 5.0.2. I wonder if it's possible to port cyanogenmod.
Hey there! Super helpful tutorial and most helpful so far that I found! However, my tablet just goes black after I press Normal Boot and just stays that way. Also when performing ADB Shell (Mac) for some reason it stays in the shell for few seconds and goes back. Any ideas why that might be happening? On top of that I can only enter the shell command really quickly so I have no idea when it finishes copying system.img across... Any help would be appreciated!
Hi guys,
does this method flash the 7840 with a 5.0.2 image or with a 5.1 one?
Thanks
I tried and I can reply to myself: it restores a clean 5.0.2 image ...
EDIT: xposed framework work perfectly on 5.0.2 . I'm perfectly happy with it now
Guys, please disable Driver Signature before installing ANYTHING on your PC to mod, change or rescue your DELL 7840
Intels Platform Flash Tool wont flash ( ifwi error ), and tethered recovery wont upload through bootloader
took me a while to realise itself, even though i did it many many times, after not doing for couple of years, i almost forgott that you need to allow unsigned driver installatino before
have grait ****,
Iko
What if you can't boot into fastboot mode? When I try to boot into fastboot, the screen only shows a battery logo with a question mark inside. I saw that there's a fix for this problem on Intel processor devices like the Zenfone and Del Venue 8 3840 using xFSTK Downloader. But that requires dnx_PRQ.bin and droidboot.img.POS.bin, which I don't Dell ever released. Any solved this problem before?
Flash tool wont detect tablet
So i would love to try this out, im new to this whole thing and have the problem that the flashtool cant find my device
Any Tips ?
I'm unable to get further then 3%, at best. my tablet starts and shows USB icon, nothing more.
anybody has solved this ever ? has unbricked this model ? I have searched everywhere, not found any one person who solved this with usb ICON showing.
please help, if you know how to .
Intel Flashing
You need to use 'On Demand Flash" option from Intel Flash Tool. Start flashing from computer and continue on your device.
For Venue 7840
- Unplug
- Power off
- Press and hold both Volume keys
- Plug USB cable
- Release keys
It will start loading automatically
I've use Intel Flash Tool Lite 5.3.2
wirebook said:
1. Phone Flash Tool
- Install USB drivers (if on Windows)
- Install Phone Flash Tool Lite
- Run PFT, open "Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397.zip"
- Select "flash-DD0_BB.xml" and flash it
- Tablet will restart in bootloader, flashing isn't done yet, so wait
- Sometimes it can be hard to get the progress bar past 4% before things fail. Just keep trying if this happens, it'll randomly work.
Click to expand...
Click to collapse
I stucked on step 1. If I use "On demand flash", after the dell plugged in, the program close by itself. If I don't use "On demand flash", it display
Flash failed (Ifwi)
Click to expand...
Click to collapse
Any help is appreciated!
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:
After few day i find out solution how to install custom ROM to my Lenovo tablet. I think its first guide how to do it because every other guides were for TB2-X30F but not for TB2-X30L.
Installation guide:
FILES TO DOWNLOAD:
ALL FILES: https:// drive.google.com/drive/folders/1heVQAryphuXNVt5k-HsUhfRrVr9MV34D
ALL LINKS WORK ! JUST DELETE THE SPACE BEFORE drive.google.com...
1) On the tablet, at Settings, you must activate on the Developer Options the Bootloader Unlock (OEM unlocking) and USB debugging. Uncheck Verify apps over USB.
How to unlock Developer: https: //youtu.be/g5wkFAWDsg0
2) Download these files directly to your Android device, not to SD card.
a) https:// drive.google.com/file/d/1230xFbPA7DOGMhuX59yagEd6w1gNCI4o/view SuperSU-v2.79.zip (for me working only v2.79)
b) https:// drive.google.com/file/d/1vRW5RZixtNVfKbJ7nL2EUetANydfmLNg/view Gapps.zip (open_gapps-arm-7.1-micro-20180721)
b) https:// drive.google.com/file/d/13Mp8guzzOvb17s88IQyez_9reozpTNbw/view boot.img (from LiOS14-UNOFFICIAL-TB2-X30L)
3) Power off completely the tablet.
4) REMOVE SD CARD ! (because for me a part of system was installed on SD card).
5) Make sure you have a good cable so the connection between PC and tablet is perfect.
6) Download https: //drive.google.com/file/d/1XTDYs7kxagj-CXHsH_yyQnMXqYwAP_hK/view ADB and Fastboot to your PC .(here are the drivers too).
7) Unzip the zip archive and run with Administrator the apps from inside of the zip. To all the questions you must to press key Y to grant all the rights it needs.
8) Press and hold Volume up and plug in usb. Now you are in stock recovery menu.
9) From stock recovery select reboot to bootloader by using volume keys and power keys.
10) Wait about 5-10sec to tablet boot in bootloader mode. (shows lenovo logo in screen when ready)
11) Download the https:// drive.google.com/file/d/15IH55DgmD6SmlILjTukGeNcmYgUPcmCg/view recovery.img(its TWRP version for Lenovo Tab2 x30f so it wont work properly) and copy it into folder adb at local disk C (installed on step 7)
12) Run CMD with administrator and type cd C:\adb to select the adb folder.
13) In cmd type fastboot unlock-go and press enter. In case this command does not work, please try fastboot -s or fastboot oem unlock-go or fastboot oem unlock .
14) Flash recovery with command fastboot flash recovery recovery.img and then type fastboot boot recovery.img
15) From TWRP select Install and browse to emmc folder and then to your folder where you stored all files you downloaded.
(in bottom right corner you have Images... or Zips... here you can choose what type of file you want to install.
Install SuperSU-v2.79.zip
16) Now in menu select Wipe -> Advanced Wipe and check Dalvik Cache, Data and Cache. Wipe them.
17) Go back to menu and select Install. And install boot.img. At top of display check Boot and flash it.
19) Download https:// drive.google.com/file/d/1MlDxidIqLOZv_QZ91i8bsHgGdBMf7l9g/view LiOS14-UNOFFICIAL-TB2-X30L.zip and copy it into folder adb at local disk C (C:\adb).
18) Go to Menu select Advanced and open ADB Sideload. Go back to CMD on your pc and type
adb devices
If its your tablet properly connected you will see some letters and numbers and sideload. After that type
adb sideload LiOS14-UNOFFICIAL-TB2-X30L.zip
Now wait for finish the installation. If its installed corectly you will see Succesful at the top.
19) Repeate step number 15 and again install SuperSU-v2.79.zip (In installation you will see Boot image patcher)
20) Unplug your tablet from PC. And reboot it. First reboot may take 5-10 minutes and can reboot few times. DO NOT INTERRUPT THIS PROCESS.
21) After first start (set language, date..) Turn off devices.
22) Power on devices to recovery mode
(Press continuously the volume up and power key. When the screen on the tablet has started, release the power key and keep pressing the volume up key)
23) Now select again Install and install Gapps (open_gapps-arm-7.1-micro-20180721.zip). Then reboot it.
Now you have installed LiOS14-UNOFFICIAL (Android 7.1), with all stock apps(gapps) and also rooted device.
this is exactly what i was looking for 3 weeks ago. my sister asked if i could have a look at her old tablet. i managed to do it by translating myself through some russian forums. btw. does netflix work? on my sisters one it does not atm. i guess the play protect thing.
binocchio said:
this is exactly what i was looking for 3 weeks ago. my sister asked if i could have a look at her old tablet. i managed to do it by translating myself through some russian forums. btw. does netflix work? on my sisters one it does not atm. i guess the play protect thing.
Click to expand...
Click to collapse
You need to download apk from Netflix site.
https:// help.netflix.com/en/node/57688
direct link to apk
https:// netflixhelp.s3.amazonaws.com/netflix-4.16-200217-release.apk
mutrin said:
You need to download apk from Netflix site.
https:// help.netflix.com/en/node/57688
direct link to apk
https:// netflixhelp.s3.amazonaws.com/netflix-4.16-200217-release.apk
Click to expand...
Click to collapse
my sister is very grateful
Thank you very much.
What build date has this rom? Sec. patches?
Can you please post your local manifest?
Very interesting guide, unfortunately the links don't work...
Is it possible to restore them?
Tanks. Max
I think its first guide how to do it because every other guides were for TB2-X30F but not for TB2-X30L.
I have only found lineage os for x30l, can someone please link lineage (Android 7) for x30f?
The difference between L and F is that L is the sim card variant. Ive read several people getting "insert sim card" when installing L on a F tablet. So I dont want messages like this.
Thanks for this tutorial. It was possible, to upgrade this old Tablet.
Do you know, if there is anything newer version for our Lenovo?
mutrin said:
After few day i find out solution how to install custom ROM to my Lenovo tablet. I think its first guide how to do it because every other guides were for TB2-X30F but not for TB2-X30L.
Installation guide:
FILES TO DOWNLOAD:
ALL FILES: https:// drive.google.com/drive/folders/1heVQAryphuXNVt5k-HsUhfRrVr9MV34D
1) On the tablet, at Settings, you must activate on the Developer Options the Bootloader Unlock (OEM unlocking) and USB debugging. Uncheck Verify apps over USB.
How to unlock Developer: https: //youtu.be/g5wkFAWDsg0
2) Download these files directly to your Android device, not to SD card.
a) https:// drive.google.com/file/d/1230xFbPA7DOGMhuX59yagEd6w1gNCI4o/view SuperSU-v2.79.zip (for me working only v2.79)
b) https:// drive.google.com/file/d/1vRW5RZixtNVfKbJ7nL2EUetANydfmLNg/view Gapps.zip (open_gapps-arm-7.1-micro-20180721)
b) https:// drive.google.com/file/d/13Mp8guzzOvb17s88IQyez_9reozpTNbw/view boot.img (from LiOS14-UNOFFICIAL-TB2-X30L)
3) Power off completely the tablet.
4) REMOVE SD CARD ! (because for me a part of system was installed on SD card).
5) Make sure you have a good cable so the connection between PC and tablet is perfect.
6) Download https: //drive.google.com/file/d/1XTDYs7kxagj-CXHsH_yyQnMXqYwAP_hK/view ADB and Fastboot to your PC .(here are the drivers too).
7) Unzip the zip archive and run with Administrator the apps from inside of the zip. To all the questions you must to press key Y to grant all the rights it needs.
8) Press and hold Volume up and plug in usb. Now you are in stock recovery menu.
9) From stock recovery select reboot to bootloader by using volume keys and power keys.
10) Wait about 5-10sec to tablet boot in bootloader mode. (shows lenovo logo in screen when ready)
11) Download the https:// drive.google.com/file/d/15IH55DgmD6SmlILjTukGeNcmYgUPcmCg/view recovery.img(its TWRP version for Lenovo Tab2 x30f so it wont work properly) and copy it into folder adb at local disk C (installed on step 7)
12) Run CMD with administrator and type cd C:\adb to select the adb folder.
13) In cmd type fastboot unlock-go and press enter. In case this command does not work, please try fastboot -s or fastboot oem unlock-go or fastboot oem unlock .
14) Flash recovery with command fastboot flash recovery recovery.img and then type fastboot boot recovery.img
15) From TWRP select Install and browse to emmc folder and then to your folder where you stored all files you downloaded.
(in bottom right corner you have Images... or Zips... here you can choose what type of file you want to install.
Install SuperSU-v2.79.zip
16) Now in menu select Wipe -> Advanced Wipe and check Dalvik Cache, Data and Cache. Wipe them.
17) Go back to menu and select Install. And install boot.img. At top of display check Boot and flash it.
19) Download https:// drive.google.com/file/d/1MlDxidIqLOZv_QZ91i8bsHgGdBMf7l9g/view LiOS14-UNOFFICIAL-TB2-X30L.zip and copy it into folder adb at local disk C (C:\adb).
18) Go to Menu select Advanced and open ADB Sideload. Go back to CMD on your pc and type
adb devices
If its your tablet properly connected you will see some letters and numbers and sideload. After that type
adb sideload LiOS14-UNOFFICIAL-TB2-X30L.zip
Now wait for finish the installation. If its installed corectly you will see Succesful at the top.
19) Repeate step number 15 and again install SuperSU-v2.79.zip (In installation you will see Boot image patcher)
20) Unplug your tablet from PC. And reboot it. First reboot may take 5-10 minutes and can reboot few times. DO NOT INTERRUPT THIS PROCESS.
21) After first start (set language, date..) Turn off devices.
22) Power on devices to recovery mode
(Press continuously the volume up and power key. When the screen on the tablet has started, release the power key and keep pressing the volume up key)
23) Now select again Install and install Gapps (open_gapps-arm-7.1-micro-20180721.zip). Then reboot it.
Now you have installed LiOS14-UNOFFICIAL (Android 7.1), with all stock apps(gapps) and also rooted device.
Click to expand...
Click to collapse
I have followed the instructions and successfully installed LiOS14. Then, however, I have factory reset the tablet via Settings. Now it always boots to TWRP, no matter what I have tried I could not installed back the LiOS14 I only have TWRP right now.
Any help?
Boyalikus said:
I have followed the instructions and successfully installed LiOS14. Then, however, I have factory reset the tablet via Settings. Now it always boots to TWRP, no matter what I have tried I could not installed back the LiOS14 I only have TWRP right now.
Any help?
Click to expand...
Click to collapse
Same here
For me, this worked:
Lg v20 keeps booting to twerp recovery after factory reset. Megarom
Really not loving this phone and this rom. After learning I can't return to stock. Decided to factory reset it andoesn't then it boots directly to twerp recovery. Do did the first factory recovery from within the phone. Then after it booted into...
forum.xda-developers.com
The tablet can also run on LineageOS 16 which is Android 9.
As I saw that the guys in the Russian 4PDA-Forum had been able to create a LiOS16, I was able to make some adjustments and compile a ROM with most recent security patches which now runs on my good old TB2-X30L / TAB2 A10-30:
lineage-16.0-20210328-UNOFFICIAL-TB2-X30L.zip | by kenschbacher9 for 10
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
it seems that google drives are off. Can someone re-upload please?
Hallo,
I have installed LiOS14-UNOFFICIAL-TB2-X30L.zip. The installation was without problems.
But I am having problem with WiFi - problem of MAC 02:00:00:00:00:00. I have tried a lots of tips but nothig worked. Two times I was succesfull to set some MAC, but always, after while, it was gone. No able to reproduce to set.
Is it really so difficult to set somehow the MAC addres for the WiFi?
As I understand the setting of the MAC differs between different releases of OS. Does anybody know how it work in this release? It should by known where this relaese expects the MAC setting. Am I right?
1. temporary succes: Setting MAC in system/etc/firmware/wlan/qca_cld/wlan_mac.bin (I think. Its longer time ago and there was more attempts). It lasted for few months. It is not mine device so I don't know how it was handled.
2. temporary succes: I copied system/etc/firmware/wlan dir to system/vendor/firmware/wlan. I did it based on how it is in Samsung Galaxy S4 mini with Lineage 16. It worked. After restart I had to swith off and on the airplane mode to set MAC. After few attempts it was gone. No able to reproduce to set the MAC.
I am not Linux expert
nonicktoday said:
The tablet can also run on LineageOS 16 which is Android 9.
As I saw that the guys in the Russian 4PDA-Forum had been able to create a LiOS16, I was able to make some adjustments and compile a ROM with most recent security patches which now runs on my good old TB2-X30L / TAB2 A10-30:
lineage-16.0-20210328-UNOFFICIAL-TB2-X30L.zip | by kenschbacher9 for 10
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Thank you very much, install your rom on my TB2-X30F and it goes very well, the only drawback that I present is that the wifi is very slow but the rom is excellent, thank you very much for your work.
palamaro said:
it seems that google drives are off. Can someone re-upload please?
Click to expand...
Click to collapse
it still work. u just need to remove the space between htttp:// AND drive.google.com...
nonicktoday said:
The tablet can also run on LineageOS 16 which is Android 9.
As I saw that the guys in the Russian 4PDA-Forum had been able to create a LiOS16, I was able to make some adjustments and compile a ROM with most recent security patches which now runs on my good old TB2-X30L / TAB2 A10-30:
lineage-16.0-20210328-UNOFFICIAL-TB2-X30L.zip | by kenschbacher9 for 10
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Hi all, I've been trying to install the L16 version but I cannot install gapps or any zip from twrp. What is the procedure to install it correctly?
Boyalikus said:
I have followed the instructions and successfully installed LiOS14. Then, however, I have factory reset the tablet via Settings. Now it always boots to TWRP, no matter what I have tried I could not installed back the LiOS14 I only have TWRP right now.
Any help?
Click to expand...
Click to collapse
removing battery worked for me
Ive tried this tutorial and i bricked my tablet (i didn t backup the original firmware ) but i learned something new
for everybody who bricked their tablets lenevo tab 2 tb2 x30L do this:
1.first install Qualcomm_USB_Driver_v1.0 https://androiddatahost.com/nbyn6
2.install qfill 2.0.0.5 https://mydevfiles.com/download/qfil-tool-v2-0-0-5/
3.in qfill select flat build , progammer path is where you have your stock rom and load content same thing
4.press volume up +volume down and power button at the same time on your tablet *screen should be black*
5.press download content in qfil as soon as you connect the tablet to pc
stock firmware https://firmwarefile.com/lenovo-tab-2-tb2-x30l
^ english is not my first language so sorry for mistakes ^
[DELETED]
mutrin said:
After few day i find out solution how to install custom ROM to my Lenovo tablet. I think its first guide how to do it because every other guides were for TB2-X30F but not for TB2-X30L.
Installation guide:
FILES TO DOWNLOAD:
ALL FILES: https:// drive.google.com/drive/folders/1heVQAryphuXNVt5k-HsUhfRrVr9MV34D
ALL LINKS WORK ! JUST DELETE THE SPACE BEFORE drive.google.com...
1) On the tablet, at Settings, you must activate on the Developer Options the Bootloader Unlock (OEM unlocking) and USB debugging. Uncheck Verify apps over USB.
How to unlock Developer: https: //youtu.be/g5wkFAWDsg0
2) Download these files directly to your Android device, not to SD card.
a) https:// drive.google.com/file/d/1230xFbPA7DOGMhuX59yagEd6w1gNCI4o/view SuperSU-v2.79.zip (for me working only v2.79)
b) https:// drive.google.com/file/d/1vRW5RZixtNVfKbJ7nL2EUetANydfmLNg/view Gapps.zip (open_gapps-arm-7.1-micro-20180721)
b) https:// drive.google.com/file/d/13Mp8guzzOvb17s88IQyez_9reozpTNbw/view boot.img (from LiOS14-UNOFFICIAL-TB2-X30L)
3) Power off completely the tablet.
4) REMOVE SD CARD ! (because for me a part of system was installed on SD card).
5) Make sure you have a good cable so the connection between PC and tablet is perfect.
6) Download https: //drive.google.com/file/d/1XTDYs7kxagj-CXHsH_yyQnMXqYwAP_hK/view ADB and Fastboot to your PC .(here are the drivers too).
7) Unzip the zip archive and run with Administrator the apps from inside of the zip. To all the questions you must to press key Y to grant all the rights it needs.
8) Press and hold Volume up and plug in usb. Now you are in stock recovery menu.
9) From stock recovery select reboot to bootloader by using volume keys and power keys.
10) Wait about 5-10sec to tablet boot in bootloader mode. (shows lenovo logo in screen when ready)
11) Download the https:// drive.google.com/file/d/15IH55DgmD6SmlILjTukGeNcmYgUPcmCg/view recovery.img(its TWRP version for Lenovo Tab2 x30f so it wont work properly) and copy it into folder adb at local disk C (installed on step 7)
12) Run CMD with administrator and type cd C:\adb to select the adb folder.
13) In cmd type fastboot unlock-go and press enter. In case this command does not work, please try fastboot -s or fastboot oem unlock-go or fastboot oem unlock .
14) Flash recovery with command fastboot flash recovery recovery.img and then type fastboot boot recovery.img
15) From TWRP select Install and browse to emmc folder and then to your folder where you stored all files you downloaded.
(in bottom right corner you have Images... or Zips... here you can choose what type of file you want to install.
Install SuperSU-v2.79.zip
16) Now in menu select Wipe -> Advanced Wipe and check Dalvik Cache, Data and Cache. Wipe them.
17) Go back to menu and select Install. And install boot.img. At top of display check Boot and flash it.
19) Download https:// drive.google.com/file/d/1MlDxidIqLOZv_QZ91i8bsHgGdBMf7l9g/view LiOS14-UNOFFICIAL-TB2-X30L.zip and copy it into folder adb at local disk C (C:\adb).
18) Go to Menu select Advanced and open ADB Sideload. Go back to CMD on your pc and type
adb devices
If its your tablet properly connected you will see some letters and numbers and sideload. After that type
adb sideload LiOS14-UNOFFICIAL-TB2-X30L.zip
Now wait for finish the installation. If its installed corectly you will see Succesful at the top.
19) Repeate step number 15 and again install SuperSU-v2.79.zip (In installation you will see Boot image patcher)
20) Unplug your tablet from PC. And reboot it. First reboot may take 5-10 minutes and can reboot few times. DO NOT INTERRUPT THIS PROCESS.
21) After first start (set language, date..) Turn off devices.
22) Power on devices to recovery mode
(Press continuously the volume up and power key. When the screen on the tablet has started, release the power key and keep pressing the volume up key)
23) Now select again Install and install Gapps (open_gapps-arm-7.1-micro-20180721.zip). Then reboot it.
Now you have installed LiOS14-UNOFFICIAL (Android 7.1), with all stock apps(gapps) and also rooted device.
Click to expand...
Click to collapse
Will this work with x30F?