UPDATE: Posted more info in the Misc Android Development section - here.
Hi all, sorry if this is the wrong place to post but hopefully someone else with a rooted Sharp ADS1 can test this out, or even find this usefull - its been working for me for a few days so far and I'd like to share for testing.
I extracted the stock recovery image, used the clockworkmod builder site and have a (mostly) fully working CWM 6 for that device. I've been using it for about a few days, and it works nicely. It wont mount the USB storage on mines, the device was rooted with SuperOneClick.
Started when I saw a youtube video on how to get it into the stock recovery screen (hold Power and Sym while booting).
I was able to make a nandroid backup of my image, I already removed some bloatware from the device. I'm working on a CWM flashable zip of what I have, maybe someone else can do a fully stock image (mines is missing a few bits for a factory-reset).
I also extracted images of the all partitions on the device. I'm working on getting CyanogenMod (working with CM7 at the moment) running on this thing, still trying to figure what to compile it as lol. I managed to get the Kernel to compile, but I'm working on getting a Gingerbread ROM to use with this device.
Specs I noticed on this:
MSM7227/MSM7x27 cpu
Adreno 200 GPU
512MB RAM, 512MB ROM (200-ish accessible by user)
Hardware Keyboard
WiFI/Bluetooth/etc..
Wondering if theres a similar device I can try using their ROM and testing the zImage I compiled.
QUICK N DIRTY INSTRUCTIONS:
-Device must be rooted (use SuperOneClick 2.3.3)
-Copy the flash_image and CWM recovery image for the ADS1 onto the root of your SDCARD (to make things easy for now)
-Using ADB I remounted the sdcard by running the following (otherwise, you'll get permission denied even with/as root)
Code:
mount -o remount,exec /dev/block/vold/179:1 /sdcard
-I used flash_image from my sdcard (pushed it with ADB in Ubuntu), I took the CWM recovery.img file and also pushed that to the sdcard.
Code:
cd /sdcard
./flash_image recovery /sdcard/recovery.img
reboot
-As the phone reboots, hold Power and Sym and it should take you to the CWM Recovery screen after it blinks once.
Now you can do backups/restore images, clear dalvik, battery stats. Only thing that didnt work for me was mounting USB mass storage via Advanced menu. Once you get it installed, do a nandroid backup asap!
LINK TO CWM FILE (contains stock recovery.img, flash_image and clockworkmod in the CWM folder).
here
file is packed with 7zip.
I have more info on my findings on this lil device incase anyone is interested including partition mounting, etc.. root info recovery and system dump info also some random notes on the kernel.
I'm using this as a learning experience/hobby, and I'd like to share incase anyone was wondering what makes this thing tick lol. Have a nice day all!
EDIT:
heres a pic of mines booting into CWM for inspiration
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
system and nandroid backups
Didnt wanna wait to edit, but heres img files for all partitions on froyo - and here's a nandroid backup (should boot, but do a factory reset/wipe data/cache and dalvik in CWM and you''re like new).
Also, the new boot.img and splash,img flash when I put em in a CWM zip however no boot with a "quick" ported GB CM7 rom (still waiting for repo sync to finish ) - flashed a zte v9 as the hardware was similar (even running the grab proprietary files grabbed almost EVERYTHING - there were a few that were off). Hopefully someone can find this interesting for the device. There's a few others that looked promising, I'm taking a break for now tho lol
UPDATE:
Tried using a ROM kitchen to play with the stock rom, didn't work too well lol. I managed to restore a nandroid, but WiFi keeps showing as an error (think it may have had something to do with an option for tethering/wifi that I thought I said No to in the Kitchen's menu...). Also , the signed ROM from the Kitchen seemed to BJork the SuperUser/Root - gonna try flashing a SuperUser CMW zip (3.x)
Also, even with experimenting different roms - CWM is typically accessible via Power + Sym combo. No luck with ro.secure=0 in the stock boot.img - hopefully someone with more experience can help get something running on this lil thing. I'll keep moving forward anyways, have a few ideas of things to try out - albeiit somewhat limited, it's a start . Hope this is usefull to anyone trying to mod this sucker.
UPDATE:
Wifi's back, typing from the device. Restored to a old backup using CWM, on reboot toggled airplane mode and was able to see and join my SSID.
(another) UPDATE:
Looking at other models that seem to have similar hardware, Commtiva Z71, Spice MI300 and ZTE v9 (they have the MSM7227 600MHz/Adreno 200 GPU combo - other specs are very similar). Not sure what they have for sensors, etc.. but I found the ones on the ADS1
Code:
Sensors:
BMA150 Acceleration Sensor: 0.2mA by Bosch Sensortech
MS-3C (YAS529) Magnetic SEnsor: 4.0 mA by Yamaha Corp
MS-x Orientation Sensor: 0.0 mA by Yamaha Corp
ISL29011 Light Sensor: 0.0 mA by INTERSIL
ISL29011 Proximity Sensor: 0.0 mA By INTERSIL
random info from the "features" of the phone (build.prop related?)
Code:
Features:
android.hardware.location.network
android.hardware..wifi
android.hardware..telephony
android.hardware..location
android.hardware..touchscreen.multitouch
android.hardware..sensor.compass
android.hardware..camera
android.hardware..bluetooth
android.hardware..sensor.proximity
android.hardware..microphone
android.hardware..sensor.light
android.hardware..location.gps
android.hardware..camera.autofocus
android.hardware..telephony.gsm
android.hardware..sensor.accelerometer
android.software.live_wallpaper
android.hardware..hardware.touchscreen
glEsVers=2.0
Build Info/Kernel Config from Device.
I've attatched the system.info.gz and config.gz for the stock kernel dumped from my own device.
As far as some ROM testing I did earlier, CyanogenMod 6 for the Z71 (using the Sharp ADS1 boot.img) actually makes it past the Sharp logo and goes to the CyanogenMod boot animation, it stays there but its trying to load something lol. (Luckily I have a few nandroid backups, so flashing back to my previously rooted setup seems to work).
Maybe if I can find something that can work with this setup, then I can look at that device for something to base off to work with CM7. Fun learning experience so far. Going to try a ZTE V9 rom with the Sharp boot image and see what results from that (just trying to see what makes it past the initial boot logo). Might try swapping the build.prop in and see if that does anything lol (using the CM6 keys in their build.prop).
I'm guessing for the CM7 source (or AOSP), I'd have to find a device/manufacturer/device that I can base off for a working sharp/ads1 folder grabbing the needed proprietary files and libs.
Sharp fx plus no clockworkmod
My rooted sharp fx plus is now unable to boot up after doing some modification. I do not have the clockworkmod recovery, so I am unable to load any unsigned roms so I keep getting the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Can someone help me please. THANKS IN ADVANCE
rrkevon said:
My rooted sharp fx plus is now unable to boot up after doing some modification. I do not have the clockworkmod recovery, so I am unable to load any unsigned roms so I keep getting the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Can someone help me please. THANKS IN ADVANCE
Click to expand...
Click to collapse
Hi there, AFAIK you will need a custom recovery to load an unsigned .zip - I have not been able to find a way around that with the stock recovery. Unfortunately neither Sharp or PCD Phones has released a signed update.zip (or kernel sources for the ADS1) to restore it to stock from the sdcard.
Only thing I can think of is try using ADB logcat if possible to track where its looping, and maybe remedy it (remove/replace the offending apk or clear dalvik cache).
AmauryRR said:
Hi there, AFAIK you will need a custom recovery to load an unsigned .zip - I have not been able to find a way around that with the stock recovery. Unfortunately neither Sharp or PCD Phones has released a signed update.zip (or kernel sources for the ADS1) to restore it to stock from the sdcard.
Only thing I can think of is try using ADB logcat if possible to track where its looping, and maybe remedy it (remove/replace the offending apk or clear dalvik cache).
Click to expand...
Click to collapse
Thanks. I'll see if i can
rrkevon said:
Thanks. I'll see if i can
Click to expand...
Click to collapse
I might have found something, when I was rooting a Galaxy I997(?) - there was a modified 3e recovery that allowed loading unsigned images.
If theres a way to modify the ADS1 factory recovery to allow unsigned images, then there may be some hope. For the galaxy, it was replacing a recovery binary with the modified one in /bin and booting to that (rooted phone ofcourse).
If I have some time I'll dig mines up and flash it to stock and try from there.
If the phone is stuck in a bootloop, but has the filesystem mounted then there may be hope. I'll try to see whats possible this weekend maybe.
AmauryRR said:
I might have found something, when I was rooting a Galaxy I997(?) - there was a modified 3e recovery that allowed loading unsigned images.
If theres a way to modify the ADS1 factory recovery to allow unsigned images, then there may be some hope. For the galaxy, it was replacing a recovery binary with the modified one in /bin and booting to that (rooted phone ofcourse).
If I have some time I'll dig mines up and flash it to stock and try from there.
If the phone is stuck in a bootloop, but has the filesystem mounted then there may be hope. I'll try to see whats possible this weekend maybe.
Click to expand...
Click to collapse
I also tried using a signer software, however, it seems only part of the rom was signed. This was the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
Installation aborted.
I realize this is old, but so's my phone (ADS1) and apparently the links. All of AmauryRR's hosting links appear broken. I'm not running Windows, so SuperOneClick isn't much help.
ADB only sees:
List of devices attached
???????????? no permissions
Also, Volume-Down + Power from off doesn't appear to be the boot menu combination. I can't post in the developer section yet, so necroposting it is.
rrkevon said:
I also tried using a signer software, however, it seems only part of the rom was signed. This was the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
Installation aborted.
Click to expand...
Click to collapse
From what I remember, the recovery itself had to be modified to allow unsigned roms to work - Signing it yourself, I'm not sure if it'll give the recovery the "signature" its expecting.
nstewart said:
I realize this is old, but so's my phone (ADS1) and apparently the links. All of AmauryRR's hosting links appear broken. I'm not running Windows, so SuperOneClick isn't much help.
ADB only sees:
List of devices attached
???????????? no permissions
Also, Volume-Down + Power from off doesn't appear to be the boot menu combination. I can't post in the developer section yet, so necroposting it is.
Click to expand...
Click to collapse
Yeah, I had to drop my site for a while - I host it myself as a hobby with whatever I have to spare, and unfortunately funds weren't right. Just started a new job, so hopefully I'll be able to get my old site back up.
If you're running linux, IIRC you have to make sure the udev(?) permissions are correct for the device/user. Been a while, so bear with me lol (haven't had this phone in a while, since sharp wasn't helping with the source) - alternately, I think you can try running adb as root (sudo adb kill-server, then sudo adb) and it should recognize the device in terminal.
I can host the stuff for you if you want.
Sent from my SHARP-ADS1 using xda app-developers app
Related
ClockworkMod Recovery (Unofficial)Finally we have fully functioning CWM recovery for the LG C800, also known as the T-Mobile USA MyTouch Q, also known as the Bell/Virgin Canada Eclypse! After many said it couldn't be done... here we are!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to Install
0. Prerequisites
You will need:
- ADB and fastboot (http://dottech.org/downloads/adb_fastboot_and_other_tools.zip)
- LG's ADB drivers, available here.
Optionally, you will need:
- Root. (Use SuperOneClick root) Note: Root is not required for flashing via fastboot, but may be required for recovering should anything go wrong!
1. Back up your old recovery! ROOT REQUIRED
Open up a shell on your device by using adb shell or running your terminal emulator.
If you see a $ prompt, type
Code:
su
to get root. Otherwise if you see a # prompt you are ready to proceed.
Type
Code:
dd if=/dev/block/mmcblk0p17 of=/sdcard/stock-recovery.img
to write the stock recovery to your sd card. This will take about 8 MB of space.
2. Prepare the phone for future awesomeness
First, we must get the device into fastboot mode. In order to do this you must be able to have ADB access to the device. ADB is accessible when you are on the charging screen and when the phone is fully booted. You can enable ADB (debugging) access in the Application settings to access the adb service while your phone is fully booted.
Get the phone to the charging screen or enable ADB in the OS. Now, plug in the phone and verify you have adb access from your computer:
Code:
adb devices
If your phone is not showing up, go into device manager and make sure the LG ADB drivers are properly installed.
Once you have ADB access, run this command on your computer:
Code:
adb reboot bootloader
This brings the device into fastboot mode. What does fastboot mode look like? Well, it looks like a whole lot of nothing, mainly. If your phone boots up at this point and hangs out at the LG logo for a while, you're in fastboot mode. To verify it's in fastboot mode, run
Code:
fastboot devices
it should show something like
Code:
C:\androidsdk\platform-tools\> fastboot devices
? fastboot
If you see this, you are ready to flash!
3. Flash!
To flash, first run
Code:
fastboot erase recovery
This erases the recovery partition and ensures that everything is zeroed out so nothing gets in the way.
Now run
Code:
fastboot flash recovery C:\Path\to\downloaded\lgc800-recovery-cwm-chui101.img
protip: Tab autocompletes. It saves a lot of key strokes if you have a lot of long folder names like I do!
It should almost instantaneously transfer the recovery image, and pause just a few seconds more to write the CWM recovery image. When done, you can type
Code:
fastboot reboot
to reboot the phone back into the main OS.
4. Reboot into recovery!
To reboot into recovery:
- Issue an adb reboot recovery from your computer wherever you have ADB access (charging screen, stock recovery, or the main Android environment if you have it enabled there.)
- Or, from the phone's powered off state, hold down VOL DOWN, F, and A, and press the power button. Once the LG logo appears, you can release the power button. Once the LG logo disappears and reappears, release all the the buttons.
Welcome to CWM recovery! You can take a nandroid backup, mount USB storage, and flash zips from here! Hopefully this opens the door to CM9 and other custom ROMs on this device!
Buttons are:
MENU or VOL+ = up
HOME or VOL- = down
GENIUS or ENTER = select
BACK or DEL = back
Note: If anything goes wrong, you can return to stock recovery by using
Code:
dd if=/sdcard/stock-recovery.img of=/dev/block/mmcblk0p17
, or by using the CWM flashable zip available below. Note: Above command REQUIRES ROOT.
Downloads
It is recommended that you check the MD5 sum of your downloads!
CWM 6.0.1.2 Fastboot Image MD5: b8d15a0ee9486f0a9662dd5747c50c43
CWM 6.0.1.2 CWM Flashable ZIP MD5: 44ec9d19d5814fcfac8397c7d9a77559
USB functionality has been fixed as of 25 August. If you downloaded 6.0.1.2 before then, you might need to flash the update! If you are having any additional issues with this recovery please let me know!
Older versions:
CWM 6.0.0.0 Fastboot Image MD5: 3f5661d6120eddfd7c436c439805a310
Stuff to Flash from CWM
CyanogenMod 9 (Unofficial) Thread
Stock 2.3.6 ROM (V10V) MD5: f71cac4b1b534d94bb29d5c21a4ed8a1
NOTE: You should perform a wipe/factory reset if you are coming from a ROM other than the stock 2.3.4 that shipped with the phone.
Stock 2.3.4 ROM (V10D, bloatware and CarrierIQ removed) MD5: b6d8c04fb19cd9847027930dfb9fa7e8
NOTE: This image contains issues due to CIQ removal such as unreliable MMS/SMS retrieval. This should be only used as a last resort.
Stock Baseband for T-MOBILE MyTouch Q ONLY MD5: 2c2dcaeb6d75b37ff0b41f311665814c
Stock Recovery (from LG V10V 2.3.6 ROM) MD5: c9f606bc9033264d967ae98516cc044b
Thanks to:
misterfamilyguy for getting the ball rolling
vtinoc for getting the ball rolling again
mudtub for helping build all those recovery images and deodexing
This is amazing. Thanks!
This is good news for Q users.
Sent from my LG-E739 using Tapatalk 2
Doing some digging in the kernel source, it seems like this device is related to the LG e510, which has CM7.2 currently. We may be able to flash the e510 builds. More to come...
Thanks for your contribution .
Nevermind, it's related in name only. The MyTouch Q has the code name "Univa Q" which is its only connection really to the e510 (Univa). That and its screen size. The system board seems to be more related to the e739.
Thanks chui101 for getting the ball rolling. Good work.
Is there a link to the kernel source for the LGE C800?
I would certainly be interested in compiling a kernel and CM7 or even CM9. I have all the proprietary files needed, just need to dig around in the source and I'll upload to my github repo.
Yeah they have a 2.6 series kernel for gingerbread posted:
http://www.lg.com/global/support/opensource/opensource.jsp
search for LGC800, and it should be there.
I'm trying to get CM9 to build and I think I'm way over my head with the kernel config!
Thanks for the link, I haven't seen the Open Source page for LGE before.
If you have time or a repo I would certainly like to help and get the proprietary and device libs setup for a build. Shouldn't be too much work for the initial compile.
The C800 and the E739 are basically the same, except the C800 has a slide out keyboard.
Maybe you can flash the E739 builds of CM7/9.
Sent from my LG-E739 using Tapatalk 2
It's not quite that simple, C800 is mdpi while E739 is hdpi. Also, the partition sizes are different, and the e739 kernel doesn't have the hardware keyboard. I'm pretty sure that's enough to require a completely different build.
The kernel builds fine from LG's source code, but I'm not convinced it'll be compatible with cm9. Also, I can't get a kernel config to build CM9 for me. I'm trying to adapt the /arch/arm/configs/univaq_perf_revc_defconfig that's used in LG's kernel build for the CM9 kernel but am not having much luck... Any ideas?
I was unaware that the Q was MDPI.
No, that much of ideas. I'm not a DEV, i just port ROMS to the E739
Our phones are identical, except for mine been HDPI and yours MDPI.
---------- Post added at 01:46 AM ---------- Previous post was at 01:39 AM ----------
You CAN try and port a rom from the e739.
You'll just have to resize the images to fit your screen.
http://forum.xda-developers.com/showthread.php?t=785864
Use your phone's kernel and such important files.
It might boot, but the differences do extend beyond screen size. The camera chips are different, there is an additional LED flash on the Q, and no front-facing camera. It seems the softkeys and touchscreen also may use different drivers if I am reading the kernel configuration correctly. Still, I am using the e739 as a jumping off point.
If you need help, just ask here or in a PM.
Boy do I need help! Lol. Would you happen to know what needs to be done to a gingerbread kernel to get it to work with ICS?
Cyanogenmod did that for us lol so I haven't really messed with the kernel.
Except for editing the BOOTCLASSPATH but that's bout it.
But if I were you I'll start working with a GB 2.3.7 rom.
Sent from my LG-E739 using Tapatalk 2
2b doesn't work, writes it out and when i reboot to check CWM, it's still stock recovery and wipes out the phone. How do I get this on my phone? Fastboot doesn't work on this device.
fastboot does work. You can also get it into fastboot by holding down home as you turn on the phone.
chui101 said:
fastboot does work. You can also get it into fastboot by holding down home as you turn on the phone.
Click to expand...
Click to collapse
Tried it. Just boots like normal, gotta do acrobatics holding home and plugging in USB cable because it'll draw power from USB and screw it up.
Let's just make an update.zip so we can go into stock recovery and just flash on the new zip and not fiddle around with fastboot and dd niether of which work.
Try porting some images from the P500. It MPDI.
Here are the steps required to backup the Fuhu Nabi 2, install a custom recovery, root, and gapps using Ubuntu(12.10) Linux.
This also works on Windows(other than installing adb and fastboot) if you just remove the 'sudo' from the commands.
For a scripted Windows install, check out Nabi Lab: http://forum.xda-developers.com/showthread.php?p=36758895
Original root from jmztaylor, Includes the new gapps(t499user) and the new TWRP 2.3.3.0 from aicjofs(thanks!)
You should do all of the OTA updates before rooting(otherwise you might lose WiFi) When I posted this the latest version was 1.9.37. Settings>About Tablet>Update>Check Update
Download the needed files then extract all of the files to your home folder to begin. http://dl.dropbox.com/u/6529005/Fuh...Backup-Root-Recovery-Gapps 30December2012.zip
Open a terminal(ctrl+alt+t) and run the following command to install ADB and Fastboot (Universe).
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On the device, enable USB debugging in Settings>Developer options, then connect USB cable.
Just in case the adb server is already running, lets kill it using:
Code:
adb kill-server
Now we will start the server and reboot the device:
Code:
sudo adb reboot-bootloader
Once the device has rebooted into the bootloader, we will flash the new recovery image using fastboot:
Code:
sudo fastboot flash recovery recovery.img
When fastboot is finished, boot the new recovery kernel on the Nabi2 by pressing vol+ then vol-(down to recovery) then vol+ to select.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We will push the follwing files to the device.
First we will push the Root file.
Code:
adb push root.zip /sdcard/root.zip
Now we will push the Google Apps File
Code:
adb push gapps.zip /sdcard/gapps.zip
This is the script that will backup then install Root and Google Apps onto the device.(you can also skip the script and do it manually if you like, but make sure you do a backup)
Code:
adb push backup-root-gapps.openrecoveryscript /cache/recovery/openrecoveryscript
Now we will reboot the device and let the script do it's thing.
Code:
adb reboot recovery
Once you log into your device, start up SuperSU to make sure that root 'sticks'.
Your Fuhu Nabi2 is now rooted, w/gapps, and a custom recovery, Now click on the "thanks" button
NOTE: The following is if you ever need to do an OTA update, which requires the original Nabi2 recovery.
Download the original Nabi2 recovery image to your home folder https://www.box.com/s/9ogqkk8uu71bqrnpz9w1
Reboot the device into the bootloader
Code:
sudo adb reboot-bootloader
Finally we will flash the original recovery image to the device
Code:
sudo fastboot flash recovery nabi2_original_recovery.img
Thank you very much! In about 10 minutes, everything was the way things should be! Specifically, a nicely rooted tablet so that my son could thoroughly his tablet! Now if I can get XBMC working properly, then life would be perfect! Thanks again!!!!
Fuhu Nabi2 Common issues and FAQ.
Glad it helped you out! It's a great little tablet.
To make Nabi2 more like a regular tablet now that you have Root and Google Play, you can prevent the tablet from starting Nabi Mode/Monarch UI by checking the box in Settings>Security>'Set Parent Mode as default mode'.
You can also remove the files in the /vendor/app/ folder if you want to free up some space. Just make sure to have 'Parent Mode as default mode' checked before you remove these files, or when you reboot the tablet it will give you a blank screen.
Code:
NvCPLSvc.apk, fuhu_AddApps.apk, fuhu_AppZone.apk, fuhu_Books.apk, fuhu_ChoreList.apk, fuhu_Crafts.apk, fuhu_Fan-a-tech.apk, fuhu_KidzMode.apk, fuhu_NabiCare.apk, fuhu_NabiCloud.apk, fuhu_NabiSpinletsPlusICS.apk, fuhu_NabiSpinletsPlusParentICS.apk, fuhu_NabiSync.apk, fuhu_OOBE.apk, fuhu_ParentalDashboard.apk, fuhu_SpinletPlusVideo.apk, fuhu_SwitchKids.apk, fuhu_TreasureBox.apk, fuhu_University.apk, fuhu_Videos.apk, fuhu_Web.apk, fuhu_nabiMD.apk
I used ES File Explorer to remove the files. First you have to go into the ES File Explorer settings and check all the boxes in 'Root Settings'. Alternatively you could use the file manager in the custom recovery we flashed in the first post or any other file manager with root capabilities.
If you need to get into fastboot or recovery manually, turn off the Nabi2 and then hold the vol+ and power button until the menu comes up. You use the vol- to navigate and the vol+ to select.
Nabi2 Teardown Thread: http://forum.xda-developers.com/showthread.php?t=2024105
Technical Specs for the Fuhu Nabi2
Display: 7-inch, Capacitive, Multi-Touch Display, 1024 x 600 Resolution
CPU: NVIDIA® Tegra® 3, Super 4-PLUS-1™ Quad Core with 5th Battery Saver Core
Storage: 8 GB, Expandable via MicroSD (Up to 32 GB); Plus 2 GB FREE Cloud Storage
Memory: 1GB RAM
Camera: 2MP Front Facing Camera; 720p Video
Battery: 3,850 mAh Rechargeable Lithium-ion Battery
Size & Weight: (with Drop-Safe Bumper) Width: 8.69 Inches (220.8 mm) Height: 6.05 Inches (153.7 mm) Depth: 1.14 Inches (29.08 mm)
Weight: 1.31 Pounds (596 g)
OS: Android 4.0, Ice Cream Sandwich
Network: Wi-Fi 802.11 b/g/n Bluetooth 3.0
Input / Output: Micro USB 2.0 Port, Mini HDMI MicroSD Compatible Cartridge Slot, 3.5 mm Standard Audio Jack, Built-In Microphone, DC Connector
Audio + Video Format:
Audio: MP3, AAC
Video: MPEG-4, H.263, H.264
Charger Output: 5vdc 2000mA
Charger Plug: 2.35mm OD and 0.7mm ID
Gmail App will force close if you don't have gmail checked in Settings>Accounts&Sync>Click on email>Checkmark Gmail.
Some games on the Fuhu Nabi2 use openfeint, to disable/block this you can install AdAway https://play.google.com/store/apps/details?id=org.adaway and add the following to the blacklist. This prevents the program from contacting the openfeint servers.
Code:
openfeint.com
api.openfeint.com
scoreloop.com
Some Games that use openfeint:
Code:
Fruit Ninja, Tiny Wings, The Moron Test, Robot Unicorn Attack, Championship Manager series, Bomberman Touch 2: Volcano Party, Fieldrunners, geoDefense, geoDefense Swarm, Minigore, Pocket God, Rollercoaster Rush, Jetpack Joyride
Here is a copy of the build.prop http://pastebin.com/5hCHd4bb
If you really, really messed up and have to restore the device back to stock because you didn't follow directions and lost wifi etc etc, I created a thread for restoring to factory from scratch. http://forum.xda-developers.com/showthread.php?p=35287470
ANDROID UPGRADING MESSAGE:
If you used a different gapps other than the one posted above or http://forum.xda-developers.com/showthread.php?t=2065878 you will probably get an "Android Upgrading" message every time you reboot. This is caused by two stray odex files that need to be removed/deleted. You can just install the new gapps package or take care of the files manually.
Code:
/system/apps/Gallery2.odex
/system/framework/com.google.widevine.software.drm.odex
Thanks for this man. The only thing I'd recommend is adding a piece, or a URL, on how to add the repo's for apt to pull those adb packages. These commands you step through are handy in *nix or Windows(-sudos). Thanks again!
Thanks, I didn't even notice that adb and fastboot were in the Universe repos as I had it enabled already.
I'll go double check then. I am running Ubuntu 13 off USB stick now and had enabled universe repo but maybe didn't get a clean update before checking for pkg. Will try again and see what's up...
I thought it required some custom repos, nothing preconfigured. If it is in universe my bad.
Thank you, for this thread was able to root daughter tablet with this tutorial. Tried the script in other thread but did not help. Thanks again
Sent from my NABI2-NV7A
Yup, its in universe, my bad.
Sent from my SPH-D700 using Tapatalk 2
Here is a quote from tikiral on installing ADB and Fastboot on Windows.
tikiral said:
Speaking of posts
@shizzy t499's post is really an excellent guide. The only thing you'd change if you're on Windows is that instead of doing the 'apt-get' you'll just download and install the SDK Tools from Google (http://dl.google.com/android/installer_r21.0.1-windows.exe) > Start up the SDK Manager.exe file from the install directory > Scroll to the very bottom > Check off Extras>Google USB Driver > Click Install packages...
After install, you should be able to go into Device Manager and update the driver's on any stray android devices and bam, you should be all set to go.
Thanks again for all the info @t499.
Click to expand...
Click to collapse
Finally got a chance to perform this on my Nabi 2. Installed with no problems what so ever and was quick too. I performed the install using Ubuntu 12.10. I found it much easier and less stressful this way. Now I have to do this to both my daughters Nabi 2 tablets.
I just finished up removing the Monarch UI apps for a normal tablet. Man I really love this tablet. I have almost all my G apps installed which I have been wanting for some time now.
Just follow the instructions to the letter and you can't go wrong with Linux. Now if we could get Jelly Bean on this it would be awesome! I posted a question about the Nabi XD in the Q&A and posted specs comparing both if anyone caught it. I am pretty sure it's possible if someone can get a hold of the XD and port it over.
Thanks again t499user and all the devs that worked to make this tablet usable.
Glad it worked for you! I would love to see some JB action on here.
Just wated to shout out and say thanks many texts were sent over getting my sons tablet rooted but we got it finally no thanks to WINDOWS, Linux is the way to go! Thank you so much for the support and late night time spent working on this! :good::victory:
Hi,
Thanks so much for your new gapp package, got it working great now. Can I check if I install the default nabi recovery image again will I loose access to google play store...?
caughron01 said:
Just wated to shout out and say thanks many texts were sent over getting my sons tablet rooted but we got it finally no thanks to WINDOWS, Linux is the way to go! Thank you so much for the support and late night time spent working on this! :good::victory:
Click to expand...
Click to collapse
I am so glad that we got it working, after switching to Linux it was pretty easy eh
dave2986 said:
Hi,
Thanks so much for your new gapp package, got it working great now. Can I check if I install the default nabi recovery image again will I loose access to google play store...?
Click to expand...
Click to collapse
The default recovery would only be needed if you have to apply a new OTA update. Other than that, I would just leave the TWRP recovery, but it has no effect on the play store.
t499user;36219934
The default recovery would only be needed if you have to apply a new OTA update. Other than that said:
I have to say, that I have never been able to reflash the stock recovery after I first flashed TWRP. Every time I tried, all I got was the defective kernelpanic-Android lying on his back and I had to reflash TWRP via fastboot. So far I installed all updates from zip-files via TWRP. However, every update resulted in a defective recovery and after every update I had to reflash TWRP.
If you know that, it takes very little time but I wonder what might have gone wrong in the first place....
If some of you could spread some light, please feel free!
Cheers
DiePlage
BTW: I've tried the stock recovery from this thread http://forum.xda-developers.com/showthread.php?t=2041224
Click to expand...
Click to collapse
DiePlage said:
I have to say, that I have never been able to reflash the stock recovery after I first flashed TWRP. Every time I tried, all I got was the defective kernelpanic-Android lying on his back and I had to reflash TWRP via fastboot. So far I installed all updates from zip-files via TWRP. However, every update resulted in a defective recovery and after every update I had to reflash TWRP.
If you know that, it takes very little time but I wonder what might have gone wrong in the first place....
If some of you could spread some light, please feel free!
Cheers
DiePlage
BTW: I've tried the stock recovery from this thread http://forum.xda-developers.com/showthread.php?t=2041224
Click to expand...
Click to collapse
Have you tried to restore the unrooted stock backup that was made in the beginning of jmz rootpackage, if you didn't make 1 or use it. There are some stock posted. Unrar and put in TWRP/BACKUPS/your number folders and restore from TWRP recovery RESTORE. I have and was completely back to stock.
You can find stock in jmz files but it is any older version. Look thru the many post tho and others have posted stock 1.9.37
http://forum.xda-developers.com/showthread.php?t=1905674
ALD3 said:
Have you tried to restore the unrooted stock backup that was made in the beginning of jmz rootpackage, I have and was completely back to stock.l]
Click to expand...
Click to collapse
I have tried to just flash the stock recovery. I thought this should be enough to do OTAs. Maybe I could find another stock recovery besides the one noted...
DiePlage said:
I have tried to just flash the stock recovery. I thought this should be enough to do OTAs. Maybe I could find another stock recovery besides the one noted...
Click to expand...
Click to collapse
Forgot that I had 1 downloaded already. Try this 1 from my Box. Stock 1.9.37
https://www.box.com/shared/but3ihiutkw62pa4gayd
DiePlage said:
Android lying on his back and I had to reflash TWRP via fastboot.
Click to expand...
Click to collapse
That is the stock recovery, it will happen that way if you don't install root.zip, and possibly after an update.
To get to the menu of the stock recovery, after getting to android laying down, you push the vol buttons.
Really hoping someone can help me. Im trying to Root the Nabi 2 on my Mac. Im following the command lines, without the "sudo" text, and when i flash the recovery, my terminal says waiting for device, and nothing happens.
i know my adb is working, bc it detects the Nabi 2 when i run the ADB devices command, and it will reboot into the bootloader.
Any suggestions??
Edit
Found this link, and all worked out. Didn't have to root, or flash recovery or anything like that, but i only really need youtube as of right now, so it worked well for me
http://everythingnabi.blogspot.ca/2012/08/googlie-booglie.html
This is an update to the TWRP recovery for the Nabi 2.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
At this point this recovery is still considered in testing. The normal disclaimers apply. Have a good backup moved to your computer from the previous recovery.
Before starting this your Nabi should be updated to 1.9.37. 2 people that have 1.9.34 - (Madagascar Bundle) and 1.9.35 or 1.9.36 - (UK Versions) were having issues.
Please check your version in Settings-About Tablet-Product version, it needs to be 1.9.37 currently, other tablet versions besides 1.9.37 are experimental see below.
This is for Nabi 2
Nabi JR 4GB is HERE
NabiXD is HERE
Nabi JR 16GB is HERE
If you have Nick/Disney read up about different build for those.
Updates
Mar 15th 2015
TWRP 2.8.5.0 KK and JB http://forum.xda-developers.com/showpost.php?p=59452953&postcount=2592
2.7.1.0 http://forum.xda-developers.com/showpost.php?p=54972620&postcount=105
Jan 9th 2013
-Change to symlinked partition structure in recovery.fstab as we have found some Nabi's may have different structure
-Added Nabi Kernel version to TWRP screen for easier troubleshooting
-Added Nabi logo in place of Android(just for fun)
Initial
-Latest TWRP 2.3.3.0
-Changed to the prebuilt kernel from Nabi 1.9.37
-Fixed touch issues with some tablets with previous recovery(still testing this)
For more information on TWRP and change log see the TeamWin Website
Download
There are 5 downloads provided. The first is an installer for those less comfortable with the command line, it can install either version of TWRP, and restore the stock recovery if you are updating or returning Nabi to stock. The second two are for people that just want TWRP 2.3.3.0 and can do a manual install. The final two are the last 2.3.3.0 with static partitions should you need to revert.
Auto Installer
Recovery Installer for Nabi(Recovery installer for both old and new kernel TWRP 2.3.3.0, TWRP 2.2.2.1, and STOCK recovery) Use install method 1
Current recovery.img
TWRP 2.3.3.0 for Nabi 1.9.37(Only TWRP 2.3.3.0, manual install, this is what you should be trying to use) Use install method 2 or 3
TWRP 2.3.3.0 for Nabi for versions less then 1.9.37(Only TWRP 2.3.3.0, manual install, EXPERIMENTAL, older Nabi kernel if not working with above) Use install method 2 or 3
Older recovery recovery.img
TWRP 2.3.3.0 for Nabi 1.9.37(Only TWRP 2.3.3.0, manual install, this is what you should be trying to use) Use install method 2 or 3
TWRP 2.3.3.0 for Nabi for versions less then 1.9.37(Only TWRP 2.3.3.0, manual install, EXPERIMENTAL, older Nabi kernel if not working with above) Use install method 2 or 3
Installation
-Method 1 (Recommended install , guided installer)
-Download "Recovery Installer for Nabi" from above
-Extract TWRPinstaller.zip
-Run RecoveryUpdater.bat
Code:
Select option 1 for a Nabi on 1.9.37 and follow directions
Select option 2 for a Nabi not 1.9.37 (UK 1.9.35 or 1.9.36 or Madagascar 1.9.34)
Select option 3 to go back to 2.2.2.1 recovery if option 1 or 2 do not work
Select option 4 to return your Nabi to stock recovery after restoring stock ROM
-Method 2 (manual temporary install, will keep your current recovery)
-Download "TWRP 2.3.3.0 for Nabi" or "TWRP 2.3.3.0 for Nabi for versions less then 1.9.37" for your version
-Extract recovery.img from TWRPrecovery(2).zip to your adb directory
-From a command prompt in your adb directory
Code:
adb reboot-bootloader
fastboot boot recovery.img
-Method 3 (manual permanent install, will overwrite your current recovery)
-Download "TWRP 2.3.3.0 for Nabi" or "TWRP 2.3.3.0 for Nabi for versions less then 1.9.37" for your version
-Extract recovery.img from TWRPrecovery(2).zip to your adb directory
-From a command prompt in your adb directory
Code:
adb reboot-bootloader
fastboot flash recovery recovery.img
Other
Device source https://github.com/aicjofs/android_device_fuhu_mt799
TWRP source https://github.com/TeamWin/Team-Win-Recovery-Project/
Credits
TeamWin team for TWRP.
Dees_Troy for build tutorials.
jmztaylor for the device code to work from.
aicjofs said:
Anyone want to guinea pig a TWRP build I made?
It's version 2.3.3.0 with the latest Nabi kernel. I don't think it will fix touchscreen issues but worth a try. EDIT: Some early results are indicating it is fixing touchscreen issues.
You can try it without installing it permanently
extract recovery.img from TWRPrecovery.zip to your adb directory
adb reboot-bootloader
fastboot boot recovery.img
That won't put it on the device just boot it to ram and you will maintain your current TWRP after a reboot. To make it survive reboot obviously you would need to
fastboot flash recovery recovery.img
http://home.comcast.net/~aicjofs/TWRPrecovery.zip
Click to expand...
Click to collapse
Tried your recovery, all I could say it's perfect. Touch screen in TWRP recovery is 100%. Have ben plagued with the touch screen error in recovery prior to aicjofs latest 2.3.3.0 TWRP recovery.
jmztaylor, aicjofs, t499user, e2950 deserve the XDA Nabi 2 award. Have owned the tablet maybe 3 weeks, in that time was able to restore from soft brick, get a working gapps witout 'Android Upgrading", and new updated 2.3.3.0 TWRP recovery. Got to Love XDA community.
All we need now is our own forum :laugh:
Sent from my GT-I9300
+ 1 on all that above
+ i wanted a updated version -
+ thank you
ps: *MY* nabi box says "ages 4-to 40" i think no matter what the age is
they all going to be happy with all this cool stuff.
good job
Glad to see people are happy u made this
:good:
Great to see more development starting to happen for the Nabi 2, thanks!
maybe its just me and i noticed today that i can not get in to Fast boot unless usb is plugged in.
anyone else getting the same ?
I have 2 responses from people where this version has touchscreen issues. It is for a 1.9.36(UK Version) and what I believe is a 1.9.34(Madagascar version) I updated the OP but it looks like you should only be using this on 1.9.37 right now.
Eric Karz said:
maybe its just me and i noticed today that i can not get in to Fast boot unless usb is plugged in.
anyone else getting the same ?
Click to expand...
Click to collapse
I always have usb plugged in so I never noticed.
CWM
aicjofs are you doing a CWM recovery for the nabi 2?
Eric Karz said:
aicjofs are you doing a CWM recovery for the nabi 2?
Click to expand...
Click to collapse
I did a CWM for the Nabi. Everything worked except I was having a hard time mounting the /sdcard properly. The internal sdcard as we know it is actually in /data/media(so it's on the data partition), I was able to manually "mount" it(symlink) through shell, but I couldn't make it auto mount. I'm sure it's something simple through init.rc or something but I couldn't get it working right to mount at boot time. On a side note to that, since it's on the data partition care has to be made that if the data partition is wiped that the sdcard is moved off and then back. I'm not sure if CWM does that with a loop device or something, just moves it or what, but it's dangerous. Lot's of devices have it set up this way so I think it would be accounted for, but I know TWRP accounts for it. I'm not sure extendcommand was working correctly either, it appeared to, but log was complaining about it. As it was I had early feedback that new TWRP was fixing touchscreen issues so I put it on back burner, as part of the reason for even building CWM was for those that had touchscreen issues. Only real change was to the BoardConfig.mk for BOARD_HAS_NO_SELECT_BUTTON to make CWM "function" less mounting problems.
Now I'm trying to decide if we are better using /dev/block/platform/sdhci-tegra.3/by-name in the recovery.fstab for those Nabi's with different partition structure. jmztaylor was kind enough to give me his ear and I think we should do tegra by name. No reason we shouldn't have one TWRP version, 2 at most. Once I get TWRP working for all Nabi versions for sure, I will probably revisit it.
Updated to symlink partitions for Nabi's that have been found that might contain a different partition structure.
Nabi kernel version added for easier troubleshooting
Nabi logo
Test Report
I was able to use the nabi lab but i must admit i had problems
the first was adb\adb.exe start-server stays on when not even using the program. the problem that this caused for me is just way to much to type ...lol
so i added adb\adb.exe kill-server at the bottom of the bat file so it looks like this
:Main_7
adb\adb.exe kill-server
EXIT
The next one i uninstalled pdanet
2nd (Probably the most important step) the install of drivers "android_winusb.inf"
this one is not anything new to me
"right click and install' and i got "The INF file you selected does not support this method".
So my work around was to install it manually.
Now in the Device Manager i see Samsung phone with "Fuhu Nabi 2 ADB Interface" in it (Q is this what we suppose to see?)
3 is a question
after also installing the driver in this state . i see in the device manager Samsung phone with "google galxy nexus ADB Interface" (Q is that correct?)
I ask because i can also change it to " Fuhu Nabi 2 BootLoader Interface "
Both work
4 Suggestion
Make a built in test for both modes before proceeding
like
1) press to make sure you can boot to bootloader mode
Stop here if it didn't work
2) press to make tablet Reboot (when in bootloader mode)
IF its a success you can proceed to the next option .
thanks for the hard work you are doing , Much thanks
Eric Karz said:
I was able to use the nabi lab but i must admit i had problems
the first was adb\adb.exe start-server stays on when not even using the program. the problem that this caused for me is just way to much to type ...lol
so i added adb\adb.exe kill-server at the bottom of the bat file so it looks like this
:Main_7
adb\adb.exe kill-server
EXIT
The next one i uninstalled pdanet
2nd (Probably the most important step) the install of drivers "android_winusb.inf"
this one is not anything new to me
"right click and install' and i got "The INF file you selected does not support this method".
So my work around was to install it manually.
Now in the Device Manager i see Samsung phone with "Fuhu Nabi 2 ADB Interface" in it (Q is this what we suppose to see?)
3 is a question
after also installing the driver in this state . i see in the device manager Samsung phone with "google galxy nexus ADB Interface" (Q is that correct?)
I ask because i can also change it to " Fuhu Nabi 2 BootLoader Interface "
Both work
4 Suggestion
Make a built in test for both modes before proceeding
like
1) press to make sure you can boot to bootloader mode
Stop here if it didn't work
2) press to make tablet Reboot (when in bootloader mode)
IF its a success you can proceed to the next option .
thanks for the hard work you are doing , Much thanks
Click to expand...
Click to collapse
Ok I really need to make a thread for Nabi Lab. Was that a hint? haha. Excellent feedback as always.
1. Yes you are correct that it should be added. I will add it.
:Main_7
adb\adb.exe kill-server
EXIT
2. What version of windows are you using? Also 32bit or 64bit? I had no issues with 7 and 8 64 bit after disabling windows driver signature enforcement, are you sure it took the "disable driver signature enforcement" after the reboot? That's the only thing that I know that would cause that. XP worked but I did manual mode as you did while testing. It's a modified Samsung driver so it might display that.
3. Also possibly related to the above. However I don't think so... It's possible that installing PDA net doesn't remove driver store/inf(depending on windows version). For example on Windows 7 open /windows/system32/driverstore/filerepository and search for "android" there is likely extra ones. So it just reinstalled the PDA net one. It should say Fuhu Nabi 2, so I think you are using the old driver. Both drivers are so you see the option for Nabi labelled one. You would have to unisntall in device manager and then remove all of android infs. Then reinstall.
4. Useful feature. That's not too hard to add since it detects the mode based off of it can run the getprop command. Give me an example when you would want it to do this so I can add it logically. Just really adding "fastboot reboot" and detecting. Are you thinking automatic detection like refreshing on it own?
Thanks for the feedback. You were already credited in the readme, but maybe you need some more credit
before i forget http://forum.xda-developers.com/showthread.php?t=1905674&page=131&highlight=nabi post 1302.
i was thinking
after the driver install
something like
1) test 1- Action > adb.exe reboot-bootloader
@echo Do you see the pretty green word "Bootloader" ? lol sorry i am tired
nabilab.bat
what ya think ?
line 137
explorer.exe .\driver
to
%windir%\explorer.exe .\driver
plus it seem to be the only way it works for me ...lol
i did at one time have some changes in my windows enviroment variables
but i think i changed it back .
Eric Karz said:
what ya think ?
line 137
explorer.exe .\driver
to
%windir%\explorer.exe .\driver
plus it seem to be the only way it works for me ...lol
i did at one time have some changes in my windows enviroment variables
but i think i changed it back .
Click to expand...
Click to collapse
Will that even be necessary if we go with the driver.bat you posted integrated in to the main bat file? I have been busy with my job last few days but I was able to run it in a few environments and it was working. The driver works, Im just working for an experience where anyone that can click a mouse/use a keyboard can install it. I think the PDAnet one is messy, that program even installs the apk to your tablet. Nonetheless the driver from a fundemental standpoint is the most important part, even if most people already have some functional driver. I want to get the driver cleaned up and the 2 known typos(although the 2nd might not be necessary if the driver install changes)
If I get those fixed make a Nabi Lab thread and work on ideas people have or want to see. Since you have been over the code what do you think of my hack job? Haha. Just notepad, not even notepad++, let alone a proper sciprting editor, I just kept adding stuff, it started as a simple recovery installer and then I got sloppy, and my variables and calls are a mess and named ridiculous. Kind of embarrassing. I haven't written that much code from scratch in 20 years, most of the time you have a base and can just work from there. That driver you linked gave me an idea of adding color to highlight errors and important parts, mostly cosmetic. For line by line color changes I have to use chgcolor and echoj. Easy enough to add to the download but changing all the echos is a tone of work.
I hope you know I appreciate your contributions.
opps my bad - forgetting the part about adding it to the main bat file .
just getting nabi lab to work for every one that uses it is the main goal.
code always has to start some place - i am sure as time goes on people will recommend things to to it.
the color in the Install bat was just to wake you up and watch what you are doing.
here is a example of something my brain skips over - Even though its proper and must be read in order to achive the goal
“Then hit VOL - until Recovery Kernel is selected
My brain only wants to hit vol 1 time haha
my brain should tell me to keep pressing Vol - until I see “Recovery Kernel” selected.
I see that Twrp is up to 2.4.0.0
Is there anything that nabi 2 users would benifit from it ?
Re: [recovery][nabi2] twrp 2.3.3.0
I too am wondering this!
Sent from my EVO using xda app-developers app
Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
Support for exFAT formatted sdcards (also thanks to bigbiff)
Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
Added wipe cache and dalvik after ADB Sideload
Replaced many system calls with their native C counterparts
Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
Fixed AOSP recovery commands to run after decryption on encrypted devices
Improvements for building TWRP in CM10.1
Other minor bugfixes and improvements
Click to expand...
Click to collapse
Seems interesting, I'll see about making a test build sometime this week unless someone beats me to it.
I'm short on time these days. Here is a build that boots. I tested an install. You can try and put through paces. fastboot boot recovery.img to test and not replace current.
Download TWRP 2.4.0.0
NabiRootXD v2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a tool for rooting, installing Gapps(Play Store, etc), and adding custom TWRP recovery on Nabi XD. It's written as a windows command line batch file, and is based off NabiLab I made for Nabi2.
It was an adventure to say the least. I include some of the hurdles for those that want to duplicate the root process or just to place my thoughts "on paper" because of the 100's of posts I read from those that posted detailed information and allowed me to gain useful insight in how I could adapt things for the XD, and explain in one swoop to the many PM's I have received about "when will we see root on the XD" why it took so freaking long. Those that just want the program can continue to the Overview section.
What started as an interesting avenue was TWRP using the Nabi2 kernel was booting the NabiXD to TWRP without video. I thought it possible to dd the recovery, or boot kernel. Unfortunately it was unable to recognize internal storage as a block device and that ended that. Like a few devices on Android 4.1.1 and above the standard once click program using Bin4ry's ADB restore exploit doesn't work. It doesn't work for a couple of reasons, when restoring fakebackup.ab in locks up writing the first file, and even if it did work placing ro.kernel.qemu=1 in local.prop doesn't work because Jelly Bean doesn't parse any property files to set the ownership of adb daemon. Searching the file system I found su2 in the xbin directory. This was promising as it is the su program but renamed, also unfortunate was its permissions had no setuid bit set and while it was executable it would not change uid to 0. I then foolishly went down the path of nvflash(forced recovery). I attempted a few different avenues here to try and possibly get the SBK to unlock nvflash, that proved uneventful, especially without root access. I tried extracting what "could" be the key from the Nabi2 it hope it was reused. That lead no where, it would be awesome to have access to it for many other reasons but it turned out to be an exercise in learning but ultimately a waste of time. Then on to other Android exploits... Tried Samba, debugfs, and vfat exploit. All of those are either patched or I'm not skilled enough. I finally returned to looking at the ADB restore exploit.
The "tabletS" exploitation showed promise as it takes the avenue of installing /dev/sh vs ro.kernel. A side effect of the failed ADB restore bug was leaving a directory with full permissions. Bads3ctor had an interesting fakebackup.ab that was more reliable at making a directory or file that you simlinked have full permissions. Now you can step through the tabletS script more effectively where you couldn't before by manually setting permissions for files/directories you need by doing the restore for each file and directory you need. The script installs VPNfaker and backs up the /data/app directory, then creates a new app directory. This however will cause the NabiXD to rerun the initial kidsmode setup and breaks everything. You can dance around that by not rebooting, and VPN faker will still give you a Term app with system uid. From there you can't symlink the sysfs links properly to data/property but that can be worked around by moving and then removing files. Finally you can makedev /dev/sh and run su from /data/local/tmp. The end result is that the exploits and bugs found by others are adequate when strung together in the right order on the NabiXD just not the one click solutions provided on the forums, they needed some modifications and done by hand to figure out for the NabiXD
Here is a nice publication I found in my searches that is more layman terms for older root methods. http://www.sourceconference.com/publications/bos12pubs/android-modding-source.pdf
Overview
Video Overview of NabiRootXD - a video tutorial of the use of NabiRootXD.
-Root the Nabi XD
-Install Gapps(Play Store, etc)
-Make a stock backup of unrooted device
-Install stock, or TWRP recovery
-NabiLab patching system to install updates to this program
Version 2
-Fixed scripting error causing early exit
-Added 7z for patching system
Download
Read the installation section below to determine which version you want.
File names:
NabiRootXD.zip 96MB (Version 2)
Download
Download Mirror
Installation
NEW INSTALLS
1) Download NabiRootXD
NabiRootXD.zip 96MB
2) Extract the zip files to a location of your choosing. Run the NabiRootXD.bat file.
Prerequisites
1) Script is for Windows
2) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
3) ADB and Fastboot driver. Most popular are the PDAnet drivers. You can get them here: PDAnet drivers
Usage
Obviously using this script on your NabiXD voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Root, Gapps, Recovery
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps. This is Jelly Bean Gapps dated 10/11/2012 without Google Search. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
MENU 2 - Install Recoveries
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.2.3
Installs TWRP 2.4.4.0. This is the latest at this time. It has a screen timeout, if the screen goes black touch the screen to wake the screen, it's not locked up.
Menu Option 2 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 3 - Patch NabiLab
Menu Option 1 - Install Patch
For any updates to NabiRootXD this is where you can automatically load them. Basically you will download NabiPatchXD.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Credits - If you see these guys buy them a beer.
jzmtaylor - Original Nabi2 script that this is based off of.
Bin4ry, Bads3ctor, HEXcube, drjbliss - all the bugs/exploits needed to accomplish root
Dees_Troy - TWRP build tutorial
Eric Karz - TWRP Theming and rooting assistance
TeamWin - They are the guys that make TWRP possible
Weeee more Easter goodies haha.
thanks aicjofs
Sir can i use this tool for installing Gapps for unrooted Galaxy Tab 7.0+ (wifi)? bcoz i updated my tablet for Honeycomb to Ice creamsandwich (China Firmware), everything is fine except that i cant open google playstore...
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
srgsng25 said:
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
Click to expand...
Click to collapse
The gapps removes the problem in system/app/quicksearchbox.apk you can rename it toquicksearchbox.bak
only other way I can think of is some how playstore added it to data/app
rename com.google.android.googlequicksearchbox.apk to com.google.android.googlequicksearchbox.bak
hth
ps: thank the op he spent hours and hours to make this happen = sacrificed his free time
Thanks for the feedback.
Perhaps we should have used the 7/26/2012 gapps? http://goo.im/gapps/gapps-jb-20120726-signed.zip 10/11/2012 is suppose to be 4.1.1 backward compatible, but perhaps there are some bugs with it on XD. Flash over the top of the current one. It will leave behind /system/app/thinkfree.apk, /system/app/microbes.apk and /system/lib/libmicrobes_jni.so, which you could remove manually. Wipe caches.
How about GPS stuff? Is that working?
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Eric Karz said:
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Click to expand...
Click to collapse
Do we know that the GPS works at all?
aicjofs said:
Do we know that the GPS works at all?
Click to expand...
Click to collapse
with gapps installed it doesn't seem to work .
maybe we are going to need a edited gapps ?
I'm just going to remove Google Search for now. That is highly annoying, I was messing around with ways to fix it, and got it to open in apps when you press the settings button, I was previously only getting it when pressing back button.. I updated the downloads. Until we figure out the fix, it's just too troublesome.
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
srgsng25 said:
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
Click to expand...
Click to collapse
I don't know if there is a hidden proxy. I'm not sure of your question. You could try going to settings-wifi. Long press the name of the network and a pop up will come up. Modify network, show advanced options. There is the proxy and DNS, for DNS you have to be static. I think there is 4.4.4.4 in there by default, plus what your router gives out.
If you are talking about something more underground I think you could use a getprop in adb shell or term.apk. I know I have seen stuff in there for DNS, something like dhcp.wlan0.dns there is stuff in there about "change" too. Should be able to set if you "su" and do a setprop. That would only be good until reboot, but could help you trouble shoot. I think it's set here /system/etc/dhcpcd/dhcpcd-hooks/20-dns.conf, maybe not in Jellybean. Anyway those are places to look if it's more then in settings that you are looking for.
ok it seems that this might be a work around to the quick search problem
edit the buildprop and change
ro.sf.lcd_density=160
to
ro.sf.lcd_density=145
I tried 149,150,59 and 120
120 does seem to fix it also but the screen makes every thing look smaller and some may not like that .(I do)
also I had to install BusyBox in order to get a few things to work including
build prop Editor by Nathan Campos (this tool seems to be a good test app to see if you have proper permissions)
note that the swipe screen will be a bit smaller under 160
maybe some one can use this info to edit quick search box we wouldn't have to change anything?
i am trying to get this tablet to use my network opendns settings and web filters
Can someone direct me to where I can get a Vista MTP driver for the Navi XD? I installed PdaNet as instructed but the tool wont connect, and I have a yellow exclamation mark by MTP Device. Can't seem to find anything else online.
EDIT: After rebooting a few times, then disabling my firewall, the tool connected. Thanks for the awesome tool.
Looks like an OTA was released for the Nabi XD today that bumbs the Nabi XD up to version 1.3.5. I tried doing the stock recovery option but the NabiRootXD app just closes out after selecting it. I looked into the NabiRootXD.bat file and I noticed on line 483 that it says to "GOTO Install_4" which doesn't seem to exist. I believe it should actually say "GOTO Install_2".
After making this change I was able to restore to the stock recovery to perform the OTA.
Now once I tried to install the OTA it appeared to atart the installs and then fails with the dead android symbol about a third of the way through. No idea what the problem is now so I'll just wait for others to try this and see what their results are.
yup getting the dead droid
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
OTA procedure
srgsng25 said:
yup getting the dead droid [
BOOT into TWRP and perform and system restore to pre-root image
reboot
download and install the OTA
reapply root and gapps
Click to expand...
Click to collapse
aicjofs said:
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
Click to expand...
Click to collapse
Thanks for the update aicjofs! I'll test this out shortly and let you know how everything goes.
This thread intends to be a general thread for all things about the NuVision Tablet. The aim is to help other users of this tablet to be able to root their device, get a temporary recovery and to unbrick their device. I will add the guides for the following posts below in time. This would not have been possible without help from @andrei_kr.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Technical Specifications:
Display: 8-inch IPS HD capacitive touchscreen
Resolution: 1280 x 800
Operating System: Android 4.4 Kit Kat
Processor: Intel® Atom Processor
Memory: 1GB DDR
Storage: 16GB
Micro SD Card Slot: Yes, expandable up to 64GB
Camera - Rear: 2MP
Camera - Front: 2MP
Audio: 3.5mm stereo jack with microphone
Wireless: Wi-Fi 802.11 b/g/n
Bluetooth: Bluetooth 4.0
Battery Type: Rechargeable lithium-ion
Battery Life: 6+ hours; results will vary based on usage and settings
Port: Micro USB
Sensor(s): Accelerometer
Backup/Root/Recovery
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
How to backup of your stock ROM, install CWM and Root your device.
Requirements
ADB/Fastboot Drivers
Intel Android USB Drivers
SDcard (8GB of higher)
Temp recovery script
SuperSU
Steps
Download and unpack IntelAndroid-FBRL-07-24-2015.7z
Power off tab.
Hold Vol+ and press Power on the tab 5-10 seconds
You can see logo about 10 sec and after that DROIDBOOT will load
Connect USB cable to PC
Run launch.bat from IntelAndroid-FBRL-07-24-2015 folder
Type ACCEPT and press Enter
Type 5 and ENTER (cwm.zip)
Type T3 and ENTER (or T4)
CWM will load after 10 sec.
Select backup to external sd card.
After the backup is complete, copy it to the PC to ensure it's safe.
Follow steps 1-10 again and go to install zip from sdcard or external and select the SuperSU zip file and flash it.
NOTE: DO NOT FLASH ANY ROMS WITH THIS RECOVERY IT IS ONLY TEMPORARY. I DID NOT TEST XPOSED SO BE CAREFUL.
Credits
@andrei_kr
@social-design-concepts
@vampirefo
@Chainfire
Unbrick your Tab!
To unbrick your device all you simply have to do is go back to the CWM and restore your backup that you created earlier. If you don't have one, here is a copy of a working backup ---> Google Drive. Credits to @andrei_kr, say thanks!
How to fix touch!
If you unbricked your tablet and your touch isn't working, there is no need to worry. @andrei_kr has provided a guide on how to fix that touchscreen. Credits to him.
NOTE: If your touch is working then do not try this, it will mess up your touch!!
You probably got this touchscreen issue by flashing a different kernel with incorrect drivers.
Now your configuration is likely to differ from the native. You can view the konifig in command prompt or in the terminal :
Code:
cat /proc/gt9xx_config
(only mtk) or using the gtp_tools apk (it is in the attached file below).
It starts with the byte sequence: 0x41 0x1C 0x02 0xC0 0x03
0x41 - 65 version
0x1C 0x02 - 540 horizontal resolution
0xC0 0x03 - 960 vertical resolution
Touch must somehow work to press the button, if there is support otg, then it's easier, you can connect a mouse.
1. Install the gtp_tools_v2.6_20140126_special.apk
2. Go to the option Firmware update. Click refresh, see IC Version: 913_1020 then touch GT913 firmware and 1020.
3. Go to the option Config Settings, press read, the data were considered. Under Normal Config we have:
65 version
540 horizontal resolution
960 vertical resolution
4. Click browse, select click browse to the native config.
5. Native configuration take from your device, in the same paragraph, press the save (saves the backup config file). Native configuration for Fly IQ446 in the attached file. Press send.
6. If nothing has changed, look at the version you have and native config. Then change the version of the file in the native config in your hex.
Example: 0x41 = 65 home, a stranger 0x49 = 73 => replace the 0x41 to 0x49.
Xposed does work
Make sure you're rooted and have a working backup.
Download and install Xposed but don't run yet.
Version name:
2.6.1
Release type:
Stable (low risk of bugs)
Download:
de.robv.android.xposed.installer_v32_de4f0d.apk (711.77 KB)
Number of downloads:
11,141,690 in total · 8,610 in the last 24 hours
MD5 checksum:
de4f0dc569f96dbcc5668d40fa76040b
Uploaded on:
Tuesday, May 20, 2014 - 21:59
Changes:
- Fixed a crash with some apps (Disa, Rdio)
- Some minor UI improvements
- A few translation updates
Now either use an android terminal emulator or ADB and run these commands
1. su
2. echo 148 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
3. chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
Now you can install the Xposed framework.
max0r4axor said:
Xposed does work
Make sure you're rooted and have a working backup.
Download and install Xposed but don't run yet.
Version name:
2.6.1
Release type:
Stable (low risk of bugs)
Download:
de.robv.android.xposed.installer_v32_de4f0d.apk .
Click to expand...
Click to collapse
Thanks for report.
First want to say much thanks for this thread, it was getting frustrating trying to find a solution.
I have encountered a slight issue trying to unstuck 2 of these devices.
neither have been rooted and are stock devices.
i cant seem to get cwm to locate the backup that you supplied.
do i need to copy it to the cwm backup folder on my sd card?
Jingbadguy said:
First want to say much thanks for this thread, it was getting frustrating trying to find a solution.
I have encountered a slight issue trying to unstuck 2 of these devices.
neither have been rooted and are stock devices.
i cant seem to get cwm to locate the backup that you supplied.
do i need to copy it to the cwm backup folder on my sd card?
Click to expand...
Click to collapse
Yes you do. Copy it to your sd card. Btw if your device is stock why do you want to restore this one?
kirito9 said:
Yes you do. Copy it to your sd card. Btw if your device is stock why do you want to restore this one?
Click to expand...
Click to collapse
both are stuck in bootloader.
i was assuming i could just just reflash...
cant find a stock copy anywhere...
Jingbadguy said:
both are stuck in bootloader.
i was assuming i could just just reflash...
cant find a stock copy anywhere...
Click to expand...
Click to collapse
Oh I thought they were working. Follow the procedure above to fix.
NuVision TM101A510L
Will this method work with the NuVison TM101A510L. It seems like a lot of work to do if I'm not sure about this model. Also I have a problem with this model overheating and crashing when I play Pixel Gun 3d and it's pissing me off. I just fired off a curse filled missive to NuVision support. They don't even list this model on their registration page and it seems they have no faith in this model. I will never buy this brand again, in fact I would recommend against it to my customers. I've used Azpen tablets with no problem rooting or playing Pixel Gun 3d. I took a chance and I'm so damned sorry I did.
;angry
Thank you so much for this thread!!! I have been looking for a recovery for a few months now and cant believe I didn't find this until now...
ok so a minor problem... I cant seem to flash the recovery... Not sure if ive placed the recovery file on my sd card properly or not cause i locate a few backup files none of which have any effect. I gave up in frustration untill now. ( Currrently working on a few androids one rooting one imea changing so figured id take a crack at these devices again. THe layer of dust on these things are getting a bit thick.)
williamglick said:
Will this method work with the NuVison TM101A510L. It seems like a lot of work to do if I'm not sure about this model. Also I have a problem with this model overheating and crashing when I play Pixel Gun 3d and it's pissing me off. I just fired off a curse filled missive to NuVision support. They don't even list this model on their registration page and it seems they have no faith in this model. I will never buy this brand again, in fact I would recommend against it to my customers. I've used Azpen tablets with no problem rooting or playing Pixel Gun 3d. I took a chance and I'm so damned sorry I did.
;angry
Click to expand...
Click to collapse
I think the models numbers are specific so I can't say for certain that this will work with your tab. Try the fastboot/rooting procedure first and then maybe you can just restore the system partition only not corrupting the boot/kernel.
Unidave199 said:
Thank you so much for this thread!!! I have been looking for a recovery for a few months now and cant believe I didn't find this until now...
Click to expand...
Click to collapse
You're welcome. I waited months also before finding a working backup.
Jingbadguy said:
ok so a minor problem... I cant seem to flash the recovery... Not sure if ive placed the recovery file on my sd card properly or not cause i locate a few backup files none of which have any effect. I gave up in frustration untill now. ( Currrently working on a few androids one rooting one imea changing so figured id take a crack at these devices again. THe layer of dust on these things are getting a bit thick.)
Click to expand...
Click to collapse
You are using the fastboot method correct? If the recovery script says finished as in no errors show on the screen then it could be the device itself. What do you see?
kirito9 said:
You are using the fastboot method correct? If the recovery script says finished as in no errors show on the screen then it could be the device itself. What do you see?
Click to expand...
Click to collapse
ill let you know just as soon as i can get back to working on those devices... im prety sure if memory serves correctly, that I was getting some errors regarding unable to mound sd or ext sd. I could be wrong but thats what comes to mind.
Im up to my neck in jobs on other devices. (rooting galaxy S5, changing imei on another S5, IMEI change on a LG Stylo 2 plus, Galaxy Tab 2 system issues need to diagnose, and several screen and lcd replacments)
STUCK
ok so i have a little time to work on these....
When i run the launch.bat and get to fastboot, it goes through the instalation and everything checks ok till the very end where it says failed cause too many links.
included the screenshot so you can see.
At this point im unsure if i just need to try flashing the supersu zip like it instructs but having tried befor it had no luck.
can I not just flash twrp on this thing then su like with most root methods?
after ive flashed super su, when i go to restor the working backup i see a list of backups... including yours but when i select it i always get :
checking md5 sums...
md5 mismatch!
what now?
(i tried just flashing the boot but even that comes back with same error)
I know on other devices the recovery is an img file any the one you provide is a rar... i extracted to my desktop and was gonna try flashing with abd/fastboot but since its not an img file, im thinking it wont work...
any thoughts?
Im still unsure how to flash the recovery that u supply in the section for fixing bootloop....
Jingbadguy said:
ok so i have a little time to work on these....
When i run the launch.bat and get to fastboot, it goes through the instalation and everything checks ok till the very end where it says failed cause too many links.
included the screenshot so you can see.
At this point im unsure if i just need to try flashing the supersu zip like it instructs but having tried befor it had no luck.
can I not just flash twrp on this thing then su like with most root methods?
Click to expand...
Click to collapse
The too many links error is common for this device. Touch doesn't work with TWRP on this device so CWM is out only go. You can root and using cwm like any other root method.