Howdy folks,
Yesterday, I was the proud owner of a sleek little TCT.Alcatel OneTouch A554C, formally know as a Virgin Mobile Venture running Android version 2.3.5.
It was successfully and surprisingly easy to root by utilizing 2 cool little apps, Ministro and Poot-Debug.
After root, I subsequently downloaded some root tools (eg., Titanium Backup Pro, Superuser Elite, System App Uninstaller).
That was last week.
Yesterday, I got a bit cocky. I needed to clear up some internal memory so I used "System App Uninstaller" to uninstall a few apps. If I remember correctly, the apps were as follows: Google Maps, Google Maps Street View, Calculator, Digital Clock, Setup Wizard, Android Live Wallpaper, Live Wallpaper Picker, Magic Smoke Wallpaper, Music Visualization Wallpaper, and the TouchPal Keyboard French and Spanish Language Packs.
So far so good, right? However, I believe I may have snarfed-up when I uninstalled the Setup Wizard. But I'll get to that in a minute.
Now with Titanium Backup, I moved some apps to the sd card. Included was the stock launcher, Smart Launcher Pro, SPB Shell, AVG Anti-Virus, and Superuser Elite. Then I rebooted through Titanium Backup and I haven't viewed any pornographic material since!
After reboot, the phone got stuck on the final boot animation frame. I panicked, pulled the battery, booted into recovery then rebooted a 2nd time.
This time it booted to the pull-down lock screen. I unlocked and seen:
"Sorry! The application com.android.setup wizard has stopped unexpectedly. Please try again." Along with a "Force Close" option. I forced closed and the screen went black with the exception of the status bar. The phone is still on but otherwise...nada.
When I press the power button, same thing happens: pull-down lock screen, screen goes black. Or sometimes, it will turn on and boot loop.
Major panic time!!! I booted into recovery again and performed a factory reset to no avail.
Another clue to note: I can connect & access the sd card via usb to desktop.
Also, I did have the good sense to backup all apps, system and user, through ES File Explorer and stored them both on sd card and in the cloud via Yandex Disk prior to this bricking fiasco. Now, what do I do with them? I now realize it was possibly a mistake moving all 3 launchers to the sd card. How do I get the stock launcher back to the phone?
Or, should I:
1- Attempt a base rom reinstall or
2- Attempt a custom rom install or
3- Use it solely as a time piece/mass storage device or
4- Throw it very hard and very ******* far away from me!?
I realize this is an obscure little cheap phone but it's the only one I have. Any valid feedback would be greatly appreciated.
You can go to the Play Store on any browser and choose a launcher to install. Or if you have USB Debugging on, you can side load an launcher apk. Or if you install a custom recovery, you can install another rom or sideload an apk there. Or you can flash the original firmware via SP Flash Tool.
Lots of options and none of them need to be throwing it against the wall.
es0tericcha0s said:
You can go to the Play Store on any browser and choose a launcher to install. Or if you have USB Debugging on, you can side load an launcher apk. Or if you install a custom recovery, you can install another rom or sideload an apk there. Or you can flash the original firmware via SP Flash Tool.
Lots of options and none of them need to be throwing it against the wall.
Click to expand...
Click to collapse
Hmmm...Ok, thanks. Dig your username, by the way.
First thing is, install from play store would be possible if I had data service or if I was able to enable wi-fi. I only have calling & texting service on this phone and as for wi-fi, I can't enable it due to the problem of not being able to access the settings menu. All I have when it does boot, and it only fully boots when it is connected to a PC, is the pull-down lockscreen displaying time, date, status bar and the original wallpaper. Pull it down and the screen goes black with status bar still displayed along with time & battery level.
Secondly, USB debugging was enabled prior to all of this but I panicked & performed a factory reset. Don't think it's still on.
And lastly, is installing either a custom recovery, (which, to be frank, I'm just not that savvy) another rom or flashing original firmware even possible without a PC? Because I only have access to a PC without administrative privileges so therefore...no installing exe's without a password. Maybe this program lab will allow me, quite possibly not.
Hell, would I even still have root after a reset/data wipe?
Thanks, anyway, Esoteric Chaos
Off subject: The Joker was an Agent of Chaos. Loved Heath Ledger as The Joker.
Silver Rivers said:
Hmmm...Ok, thanks. Dig your username, by the way.
First thing is, install from play store would be possible if I had data service or if I was able to enable wi-fi. I only have calling & texting service on this phone and as for wi-fi, I can't enable it due to the problem of not being able to access the settings menu. All I have when it does boot, and it only fully boots when it is connected to a PC, is the pull-down lockscreen displaying time, date, status bar and the original wallpaper. Pull it down and the screen goes black with status bar still displayed along with time & battery level.
Secondly, USB debugging was enabled prior to all of this but I panicked & performed a factory reset. Don't think it's still on.
And lastly, is installing either a custom recovery, (which, to be frank, I'm just not that savvy) another rom or flashing original firmware even possible without a PC? Because I only have access to a PC without administrative privileges so therefore...no installing exe's without a password. Maybe this program lab will allow me, quite possibly not.
Hell, would I even still have root after a reset/data wipe?
Thanks, anyway, Esoteric Chaos
Off subject: The Joker was an Agent of Chaos. Loved Heath Ledger as The Joker.
Click to expand...
Click to collapse
You can go to ANY browser - even on the PC and log into your account and hit Install and it will send the command to your phone to install it. Pretty nifty. But you did say you factory reset, so that isn't actually going to work. Sorry.
The rest of the stuff would require a PC, though I don't think admin rights are needed, so there's that...
If you don't have your phone logged into Google or USB Debugging enabled, you're kind of stuck without a PC.
es0tericcha0s said:
You can go to ANY browser - even on the PC and log into your account and hit Install and it will send the command to your phone to install it. Pretty nifty. But you did say you factory reset, so that isn't actually going to work. Sorry.
The rest of the stuff would require a PC, though I don't think admin rights are needed, so there's that...
If you don't have your phone logged into Google or USB Debugging enabled, you're kind of stuck without a PC.
Click to expand...
Click to collapse
Well, on these PCs it certainly does. I thought I was on track yesterday and tried to install a copy of Odin that I found. Can't install without a frigging admin pass.
Someone else just suggested I try a stock rom flash. Might as well, right? Happen to know where I could find a good reliable copy? That also happens to be free?
Not sure why you were trying to use Odin for a non Samsung phone...?
The stock rom flash would only be possible via PC or if you had a custom recovery installed.
Here's what you would need to do for the Virgin Mobile Venture:
Download CWM: http://www.sendspace.com/file/4gt04i
Download adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download rom: http://goo.im/devs/LeslieAnn/Venture/Stock_Venture.zip - Put on SD card.
Drivers: http://pdanet.co/bin/PdaNetA4150.exe (this program is for USB tethering and installs the adb drivers for your phone as well as many others)
The CWM img will need to be in the folder you unzipped for adb/fastboot. You'll need to boot to fastboot mode by powering on with while holding Volume Up.
Open a terminal prompt and change directories to your adb/fastboot folder. Then run this command:
fastboot flash recovery nameofrecovery.img - fill in the nameofrecovery with whatever the CWM file name is.
(if this doesn't work - make sure that your PC is reading the phone correctly by using the command: fastboot devices . If you don't get anything back, make sure you check the Device Manager for errors. If you have them, try reinstalling the drivers and rebooting the PC)
Then pop the battery out and then reboot to recovery via powering on while holding volume down. Once there, you should be able to do a factory reset and then install the stock rom zip. The volume keys should scroll through selections and the Enter key for accept, or Power if that doesn't work. Not really sure about this particular phone.)
Actually, you might just be able to use adb to install a launcher apk once you have CWM installed. Might be a little easier.
launcher apk must be in adb folder then while in CWM:
adb install nameoflauncher.apk
Note: You can rename zips and apks to be easier to type the commands.
es0tericcha0s said:
Not sure why you were trying to use Odin for a non Samsung phone...?
Click to expand...
Click to collapse
Yeah, me either. I was all over the place yesterday grasping at anything. So Odin is only for Samsungs, huh? Guess I can delete the exe file from my sd.
Right then. I'm about to proceed with your advice. Cross your fingers and toes.
Thanks mate!
The CWM img will need to be in the folder you unzipped for adb/fastboot.
Click to expand...
Click to collapse
and
launcher apk must be in adb folder then while in CWM
Click to expand...
Click to collapse
Wait, what? Please excuse my ignorance, but am I missing something. ADB didn't come in a zip. It's an installer. I think you may have to dumb this down a bit more, mate.
Silver Rivers said:
and
Wait, what? Please excuse my ignorance, but am I missing something. ADB didn't come in a zip. It's an installer. I think you may have to dumb this down a bit more, mate.
Click to expand...
Click to collapse
Sorry, I meant in the folder that it extracts the files too.
es0tericcha0s said:
Sorry, I meant in the folder that it extracts the files too.
Click to expand...
Click to collapse
Right, got it.
Silver Rivers said:
Right, got it.
Click to expand...
Click to collapse
If you can't run the exe file, then let me know, and I'll just upload a zip / folder with the necessary files. You do not need admin access to run the adb commands.
es0tericcha0s said:
If you can't run the exe file, then let me know, and I'll just upload a zip / folder with the necessary files. You do not need admin access to run the adb commands.
Click to expand...
Click to collapse
That would be really cool, actually. But check this out:
I talked someone into allowing me to utilize his laptop. I installed ADB, moved the Launcher APK to the folder suggested, ran the commands but the command prompter responded with "waiting for device" and progressed no further. Could it be a driver issue? I was under the impression that if the PC recognizes your device (which it did) then a new driver install was not necessary.
Dude was real cool about it even though I ran his battery down quite significantly and didn't even accomplish anything.
So, if I had the ADB files then I could just copy them to...say the PC desktop and run the command prompter from there? If so, then yes please upload and I'll just try it that route rather than rely on someone's personal PC. Know what i mean?
I do appreciate all of this. I'm getting quite the education here. If you ever get married, let me know and I'll come and dance as my favor to you.:good:
Peace...I'll return tomorrow.
What mode were you in when trying to install? The laptop had the most up to date drivers? You checked the Device Manager to make sure there was no yellow exclamation mark next to the phone? It's not unheard of for the PC to recognize in one mode, but not load the correct drivers in another, as there are different drivers for the phone depending on if it is booted, in recovery, or download mode or whatever they call it for that phone. Just make sure to get the PDAnet drivers installed and reboot. That should do the trick.
Everything else you should need will be in here:
https://dl.dropboxusercontent.com/u/9903887/adbfastboot.zip
es0tericcha0s said:
What mode were you in when trying to install? The laptop had the most up to date drivers? You checked the Device Manager to make sure there was no yellow exclamation mark next to the phone? It's not unheard of for the PC to recognize in one mode, but not load the correct drivers in another, as there are different drivers for the phone depending on if it is booted, in recovery, or download mode or whatever they call it for that phone. Just make sure to get the PDAnet drivers installed and reboot. That should do the trick.
Everything else you should need will be in here:
https://dl.dropboxusercontent.com/u/9903887/adbfastboot.zip
Click to expand...
Click to collapse
I was in Recovery and I was also attempting to install the just the Launcher versus the entire ROM. And I was also feeling a tad bit rushed, cause dude was right there informing me of his battery status. "Well, it's down to 30%." Then 2 mins later.."Ok, looks like it just fell to 25%."
Haha...so yeah, with him pressuring me, I spaced on checking the device manager. This desktop that I'm on today seems to be cool. Just checked the manager & it informs me that my device is 'working properly'.
Off to give it another bloody joust, mate. Wish me luck...
Can you fully explain how to do this
es0tericcha0s said:
Not sure why you were trying to use Odin for a non Samsung phone...?
The stock rom flash would only be possible via PC or if you had a custom recovery installed.
Here's what you would need to do for the Virgin Mobile Venture:
Download CWM: http://www.sendspace.com/file/4gt04i
Download adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download rom: http://goo.im/devs/LeslieAnn/Venture/Stock_Venture.zip - Put on SD card.
Drivers: http://pdanet.co/bin/PdaNetA4150.exe (this program is for USB tethering and installs the adb drivers for your phone as well as many others)
The CWM img will need to be in the folder you unzipped for adb/fastboot. You'll need to boot to fastboot mode by powering on with while holding Volume Up.
Open a terminal prompt and change directories to your adb/fastboot folder. Then run this command:
fastboot flash recovery nameofrecovery.img - fill in the nameofrecovery with whatever the CWM file name is.
(if this doesn't work - make sure that your PC is reading the phone correctly by using the command: fastboot devices . If you don't get anything back, make sure you check the Device Manager for errors. If you have them, try reinstalling the drivers and rebooting the PC)
Then pop the battery out and then reboot to recovery via powering on while holding volume down. Once there, you should be able to do a factory reset and then install the stock rom zip. The volume keys should scroll through selections and the Enter key for accept, or Power if that doesn't work. Not really sure about this particular phone.)
Actually, you might just be able to use adb to install a launcher apk once you have CWM installed. Might be a little easier.
launcher apk must be in adb folder then while in CWM:
adb install nameoflauncher.apk
Note: You can rename zips and apks to be easier to type the commands.
Click to expand...
Click to collapse
I have a old ass iMac desktop that has not been used in 5plus years at all and I'm a mother of 3 with no clue how to do any of this if you can dumb it down for me that would be very help full as well I have no clue where to download any of the needed files please help. My email is [email protected]
Thank you
Related
So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Sounds to me like a permissions issue. I had that after I fiddled with the contacts database to unrestrict pictures from third party apps. I would double check any files you modified and make sure they got chmod'ed back to what they should be.
You will have to somehow access the Settings to re-enable adb. When you did a factory reset, you disabled USB Development (aka adb).
For now the only known way to recover is through adb. No fastboot or signed update.zip for now.
navalynt said:
So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Click to expand...
Click to collapse
When I lost ADB access because of a hard reset (I think), this is what I did to fix my issue: http://forum.xda-developers.com/showthread.php?t=974824
I never lost root after a hard reset so I went to the market and bought root explorer and sqlite editor and copied the adbd to the /sbin folder to fix adb. I then bought sqlite editor and followed this: http://forum.xda-developers.com/showthread.php?t=972760 to re-enable side loading of apps. To install apps that I had the apk's for.
I still lose adb after a reset, but I can copy the adbd file to the /sbin folder and adb works again until I reset the phone.
I made a post about losing adb access on the motorola support forums: https://supportforums.motorola.com/message/332307#332307 to see if there were any solutions, but Mark said he would get back to me after trying to reproduce my problem.
I hope this helps.
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
No problem. That sucks, I'm not sure what you can do. Hopefully motorola or someone here will get a sbf soon so we can mess with our phones and have a way to fully recover. I hope you get it working again. Good luck!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
shadowscreation said:
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Requires USB Debugging to be enabled, but I have no access to enabled it due to Settings force closing and no ADB access in pre-boot.
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
adlx.xda said:
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
Click to expand...
Click to collapse
It won't let me install a downloaded APK because of the security restriction.
If you have an SD card, try booting into recovery with an update.zip on the file.
I can get into the recovery, but the update.zip file needs to be signed. I created one that will push the original copies of the framework files I was working with but it won't install because it's signed with test keys. The stock recovery 3e needs update.zip files signed with the manufacturer release-keys which only Motorola has.
https://supportforums.motorola.com/thread/46051?tstart=30
I started a thread on the official Motorola Owner's Forum in hopes I can find a full factory restore method for the OS. It's unfortunate that unlike HTC and other manufacturers who release full wipe RUU files Motorola has chosen to keep their restore files internally.
http://www.4shared.com/file/7YXo_gmO/update.html
That's the link to the update.zip file I was trying to use that fails because it's only signed with test-keys.
Retracteddd
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
spencerj2001 said:
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
Click to expand...
Click to collapse
Does adb on your computer see your device, since it's not fully booted?
Connect your tablet with USB cable.
On your PC, in the same folder as your adb files, open a command prompt in that location (shift+right click).
Type "adb devices" and see if yours come up as connected.
I doubt it will though, sounds like how I bricked my first prime, when I pushed a deodexed framework to it.
Might also want to try looking in the Dev section, under the how to unbrick your device thread, and see if you can attempt to revert to a different firmware via installing a blob file, but if you can't access your internal or external SD cards, to read/write the blob file (b/c your device won't fully boot) you may be SOL.
Next time unlock the boot loader first an make a nandroid backup, before messing w/ system files, that way you can easily restore. If your still in your 30 day window of purchase, you might consider a quick return/swap... would be the eaisest thing to do.
Sent from my CM7 Atrix 4G
no adb does not see my device but i can access the internal sd card
Swiftks said:
Does adb on your computer see your device, since it's not fully booted?
Connect your tablet with USB cable.
On your PC, in the same folder as your adb files, open a command prompt in that location (shift+right click).
Type "adb devices" and see if yours come up as connected.
I doubt it will though, sounds like how I bricked my first prime, when I pushed a deodexed framework to it.
Might also want to try looking in the Dev section, under the how to unbrick your device thread, and see if you can attempt to revert to a different firmware via installing a blob file, but if you can't access your internal or external SD cards, to read/write the blob file (b/c your device won't fully boot) you may be SOL.
Next time unlock the boot loader first an make a nandroid backup, before messing w/ system files, that way you can easily restore. If your still in your 30 day window of purchase, you might consider a quick return/swap... would be the eaisest thing to do.
Sent from my CM7 Atrix 4G
Click to expand...
Click to collapse
spencerj2001 said:
no adb does not see my device but i can access the internal sd card
Click to expand...
Click to collapse
If you can access the internal card, its weird that adb can't see your device... oh well... try reverting to a earlier/different firmware via a blob. See thread in dev section.
Sent from my CM7 Atrix 4G
i did exactly the same mistake: i uninstalled some system apps (the asus preinstalled apps, with titanium) without unlocking the bootloader, and after a wipe from the stock recovery i'm not able to go beyond setup configuration, it always stops. but i can see and use internal and external memory from my computer. did you find a solution?
Today I tried to flash the CyanogenMod 9 Nightly 06-30-12, coming from Build 35 of AOKP and after factory resetting and clearing Dalvik I went to install the zip and while flashing it I got a build-prop related error!
All of my NANDROIDS gave me a data error when flashing and now I am pretty f'd! I /really/ need to fix this ASAP but have no idea how.
-Samsung Galaxy Tab 10.1 Wifi-
-CWM 4-
On a second note, does anywhere know where I can get my screen replaced for cheap? I dropped my tab a few months back and the screen got MAJOR cracked, though it still does technically work (I still use the screen, it works but it's cracked is all...) and after calling Samsung and waiting for over 1 and a half hours they told me they wanted $150 to fix it, which if I recall is about half of what I payed for it anyway...
To be honest, I'd be lying if I said I was happy with Samsung over all.
I mean, bad customer support, the proprietary connection cable, and lack of official updates (along with the ugly TouchWiz that I'm not sure /who/ likes ) don't make me that happy...
Anyway, can anyone help me please?
Thanks in advance!
Update your recovery: http://droidbasement.com/db-blog/?p=2655
If you have a GT-P7510 (p4wifi), in this post are flashable zips (with your current recovery) of CWM and TWRP, in case you prefer this method: http://forum.xda-developers.com/showpost.php?p=28051448&postcount=29
After that, flash your ROM like always.
Yeah, thanks, were it so easy. I fired up ODIN multiple times, no matter what, unsuccessful. Like always, my computer would not recognize my tablet. Yes, I have the bloody Samsung drivers, yes I've tried reinstalling them (several times in the last few months), yes I've tried using different USB ports! And what? Nothing. Nothing at all. For the last few months I have not been able to transfer movies/music to my tablet via file transfer and I can't even get the stupid odin download thing to work. To be honest, I really am pissed off with this broken pile of trash. Would trade it in for a similar tablet any time.
Did you try any of the flashable zips for a new recovery?
About the USB, it sounds like a different problem, but for the file transfers, are you sure you have MTP selected? (answer #5 --> http://forum.xda-developers.com/showthread.php?t=1642009 )
If you haven't tried it yet, you could use a different computer, another OS (some Linux distro and check that adb works), change the USB cable.
I can't use a flashable zip since I can't copy files onto the tablet >.>
Also, yes, for file transfers I /do/ have MTP selected always and it doesn't work eitherway.
Essentially, I am stuck with a $300+ ugly and broken thing that I can only use as a paperweight for the huge mess I call my desk. Yay.
>Rage sidenote; Samsung, go take the money I payed for **** and shove it.
And I guess you don't have your old ROM (AOKP build 35) in your tab.
Try with adb (in recovery), but if you can't get a working USB connection (using other computers or OS), maybe there's something physically wrong with your tablet.
No, I don't. I'm stupid enough to delete the ROM zip after flashing it to save space on the tablet...
How do I do this ADB thing? I've heard of it before alot but never used it or looked into it...
Read this: for windows -> http://forum.xda-developers.com/showthread.php?t=1387527 , for Ubuntu -> http://forum.xda-developers.com/showthread.php?t=921169
After everything is installed, boot your tablet into recovery and try running in your command line application (CMD for windows):
adb devices
If it shows that a device (and ID number and the actual state, e.g. recovery) is connected, your golden!
If you have another android device, try it too, to be sure that is working.
To transfer a file the command is
adb push /path/to/file /path/in/tablet
In windows I guess is something like this:
adb push C:\path\to\file /path/in/tablet
so I'd do something like
adb push C:\ADB\CWM-5.5.0.4-p4wifi.zip mnt/sdcard/ ?
Im dling the ADB files right now
adb push C:\ADB\CWM-5.5.0.4-p4wifi.zip /mnt/sdcard/
You need the slash at the star and end of the path of the tablet.
While installing PdaNet it failed, said it couldnt connect through to the device or w/e
Also,I don't recall having ADB on when I had the tablet. I might've but I don't think I kept debugging on for the general time...
This is so frustrating >.>
I'm not sure about that error in PdaNet, I can help you with adb but I don't use Windows, so there's things I can't test.
If you didn't select ADB debugging in your ROM it doesn't matter, you're doing this from recovery.
BTW, do you have other android device?
adb seems to be working and copying, but I can't find the file in Recovery while doing choose a zip to apply!
Yes, I have an LG Optimus V on Virgin Mobile running tdm's AMAZING Quattrimus Alpha 10 on Ice Cream Sandwich/ Android 4.0.4
this is what I get
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb devices
List of devices attached
43C800340009517 recovery
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb push C:\CWM-5.5.0.4-p4wifi.zip
43C800340009517\sdcard\download
1328 KB/s (4147569 bytes in 3.048s)
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>
If you connect your phone and execute
adb devices
What's the output?
If you do the same with your tablet, what's the output?
with the tablet it's
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb devices
List of devices attached
43C800340009517 recovery
with my phone it doesn't wanna show up in Recovery or not.... Hmm.
Well, it shows fine, then you should be able to transfer the files
First, in your recovery, go through the steps to install some zip file, but just go as far as selecting the directory, then go back
Now in your PC try running something like this, change your path in windows:
adb push C:\CWM-5.5.0.4-p4wifi.zip /sdcard/
The in your recovery, select install and should show there. The thing is that most likely the sdcard wasn't mounted in your tab
Edit, to mount your sdcard in recovery do: mounts and storage > mount /sdcard > Go back
The do the transfer in your PC.
Hmm
While I was holding it to my gut, pushing the end of the cable into my stomach (It was the only way to get it to be recognized) I fooled around and went into download mode, hoping that on the contrary I could do that, turn it off, and when I went back into Recovery it would be there when it finally said the cable WAS connected and then I rushed to open Odin and wrote it through, and it frickin' wrote CWM v5 right on and it worked, I'll be damned!
Maple, I can not thank you enough for helping me with this, I am in great debt.
You're welcome, I'm glad it worked. Knowing how to use adb is really useful. And now you know that something is wrong with your cable.
Or in the connector pins or w/e of the tablet... The cable works fine for charging though....
You are my savior, bro.
Wifi and OTA updates were working fine before I rooted my kids' Nabi 2. I never tried an OTA update until after I rooted them, which doesn't work (I tried 2.1 since it said it was available). I followed the directions at http://forum.xda-developers.com/showthread.php?t=2041224 and it worked great to restore to stock 1.9.12, but wifi doesn't work now (mine could have been 1.9.37 originally). I tried the "wifi fix" mentioned, but there are still no wifi networks displayed like there were earlier today. I do not have a micro SD card to install the updates from, as mentioned in the replies. If I were to buy one, can I just put the OTA updates from http://forum.xda-developers.com/wiki/Fuhu_nabi_2 on it, and install from it somehow?
I tried to copy fuhu_nabi2_138139_1937_ota.zip to the device and install through the recovery kernel, but got an "assert failed" error. Any ideas as to what can be done to at least update this to 1.9.37, or maybe do a "stock install" of 1.9.37 instead of 1.9.12 so I have a better chance of wifi working? Please be specific as to what I need to try and in what order...some of the tools I tried seem to be inconsistent in results (Nabi Lab was latest I used). I am comfortable using what t499user has to go back to 1.9.12, I just wish I could use the same method to go to something newer...
I had the wifi problem this past spring. I backed up all my apps and data then flashed back to stock with NabiLab. Re-rooted and all was fine again.
You should also be able to use TWRP to flash back to stock. See TWRP thread http://forum.xda-developers.com/showthread.php?t=2074501
Some more info that may help http://forum.xda-developers.com/showthread.php?t=2248495
This experience is only my second time with TWRP and updating the Nabi. I've previously tried reverting to the backup in the "stockunrooted" folder, which is where I think the original was. I now recall that this had been updated to 2.0 using OTA before it was rooted.
Using TWRP, I tried reverting back to stockunrooted just now. Wifi works again, but OTA still does not (2.1 downloaded and seemed to install quicker, but upon reboot all I saw was "an error installing" message and it went directly to TWRP (where I just rebooted and it went to the Nabi screen). I am not sure what else to try. There is also an "oem" folder available for restore in TWRP, but that is the one created using t499user's process to go to 1.9.12. I initially used t499user's tutorial because I thought maybe something was wrong with the stockunrooted backup.
I have a few questions. Is updating TWRP to the latest version important? If yes, how do I do that (I've seen http://forum.xda-developers.com/showthread.php?t=2074501 before, but still not sure how to download/install 2.6.1.0)? If this has been reverted to "stock" and OTA updates still don't work, how do I apply them manually (from http://forum.xda-developers.com/wiki/Fuhu_nabi_2)?
I just noticed that the "stockunrooted" backup has things that aren't stock. Internal Storage has an Android folder with com.google.apps subfolders, etc. I am back to the original problem, and that is going to "stock" (something other than 1.9.12).
Cool, I figured out how to install 205to210.zip (TWRP 2.3.3.0)...For anyone interested, I copied the zip to Nabi/Internal Storage/TWRP, booted while holding +, pressed - to 'recovery kernel,' pressed + to choose it, then chose install. There is one more update I tried (2127stock.zip), but I get a flash error and it did not install. Considering (so far) I cannot get back to "stock unrooted" and use OTA updates, does anyone know how I can install this?
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
brentford said:
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
Click to expand...
Click to collapse
Yes its probably wise to update to TWRP 2.6.1.0. Get the file
Download
Follow "Method 3" here
http://forum.xda-developers.com/showthread.php?t=2074501&highlight=nabi
As for getting a stock image. You were using the zips here http://forum.xda-developers.com/wiki/Fuhu_nabi_2
You dont "Install" those zips. You need to extract the contents. boot.win, system.win, etc. and put them in the TWRP folder.(TWRP/BACKUPS/XXXXXX/folder)
Make a folder called 2127 put the filed in there. Then "Restore in TWRP. Then you should have a stock system. Same goes for 1937stock.zip 205stock.zip
If you have questions ask away.
Thank you all! I think I am getting it. Since I am reading (and had first hand experience) that Google Play isn't working very well with 2.1.27, I will go back to 2.05. That should keep the kids happy. I will let you know if I have more questions.
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
brentford said:
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
Click to expand...
Click to collapse
Google play won't work with 2.1.27 unless you delete some apps from /system/vendor/apps before installing gapps
As long as you have the bootloader(with the 4 options boot normal, fastboot, recovery kernel, forced recovery) and working USB port there are always options.
So is ADB not working in TWRP or in Android or both? It's probably best to copy boot.emmc.win, data.ext4.win and restore those too since you have done so much stuff. Boot contains you kernel, and data the apps. You will be back to a stock tablet with no game saves or anything so make sure you got off the tablet what you needed
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
brentford said:
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
Click to expand...
Click to collapse
Before browsing with TWRP file manager you need to go to the "Mount" tab, put an X in system. Then go to file manager.
Probably have to remove around ~50MB, maybe a bit less. Lots of people choose Wings, but obviously Wings is something some kids love. Really depends on the user.
When you flash stock, it often reset USB debugging to off in Android settings, if you flashed data too.
USB debugging is still on. Do you know anything about whether or not gapps has any problems with rooted Nabi 2.1? You have been a great help!
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
brentford said:
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
Click to expand...
Click to collapse
The only problem gapps has is there isn't enough room for it with a stock 2.1. You have to remove something.
Mount everything in TWRP. Go to file manager. /data/media is internal storage. You will find your files. Copy them back to /system/vendor/apps. Might have to set permissions.
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
brentford said:
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
Click to expand...
Click to collapse
You might be out of space again depending on what you copied back and why the icons are blank. Check with
adb shell df (in Android)
Look at system and see how much space you have free.
Or it could be permissions. You can use a file manager in Android such as ES File Explorer or Astro. You need to go to the setting in the app and enable whatever option they have to browse and remount "system" as read/write that will require root and should prompt you to accept. Then you can browse to the directory. You could also use TWRP File manager the same as when you copied files. There is a permissions tab.
I think the permission you want is 0644(for TWRP), or wr-r--r--(for ES). Same thing just different nomenclature.
Similar issue as OP
Hi guys, I have done pretty much the same thing as the OP. The wireless will not turn on or find any networks. I have tried reverse tethering, but have lost root and pretty much any other way to get internet to the nabi 2, so I can update from version 1.9.12. The big problem is I cannot use TWRP because when I boot into recovery and try to get there I get the dead green android guy with the exclamation point error and it hangs there until a hard restart. Any ideas on how to fix this. Is there a way to push an update through the SD card? Any ideas and suggestions would be greatly appreciated. I have already spent more time than I would have liked trying to fix this.
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
aicjofs said:
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
Click to expand...
Click to collapse
Well I swear I have tired this, but decided to give it another go and it worked! Got TWRP up and running then ran NabiLab to return to stock 1.9.37. Wireless is working and updating to 2.1 and then will give root a shot and GApps. Thanks for getting back on track!
Hello All! I'm sorry, I'm very new to this. Can someone please point me in the direction of instructions that I need to follow in order to root my son's Star Wars Nabi? I'm not sure if it's a nabi 2 or not.. I can't find that anywhere. We just bought it for Christmas. The internal storage is used up and the games won't move to the SD card - so, I figured my only option was to root it. There are so many pages out there with root instructions and I'm not sure which ones to use. Any help would be greatly appreciated.
MrsPurchase15 said:
Hello All! I'm sorry, I'm very new to this. Can someone please point me in the direction of instructions that I need to follow in order to root my son's Star Wars Nabi? I'm not sure if it's a nabi 2 or not.. I can't find that anywhere. We just bought it for Christmas. The internal storage is used up and the games won't move to the SD card - so, I figured my only option was to root it. There are so many pages out there with root instructions and I'm not sure which ones to use. Any help would be greatly appreciated.
Click to expand...
Click to collapse
What is the name of the device in the "about tablet" tab in settings?
It's probably closely related to the nabi2S of i were to guess. You can either try a root method like Kingo root or a TWRP method. Since you are the first person I have seen here with a Star Wars I don't have all the answers.
-If you use Kingo there is no backup to help you if something goes wrong.
-If you use TWRP method there may not even be a version of TWRP that will work, and initially you will not want to install TWRP but run it from ram. So the commands will be a bit different then what you see on the forums. With that method though you will have a backup.
aicjofs said:
What is the name of the device in the "about tablet" tab in settings?
It's probably closely related to the nabi2S of i were to guess. You can either try a root method like Kingo root or a TWRP method. Since you are the first person I have seen here with a Star Wars I don't have all the answers.
-If you use Kingo there is no backup to help you if something goes wrong.
-If you use TWRP method there may not even be a version of TWRP that will work, and initially you will not want to install TWRP but run it from ram. So the commands will be a bit different then what you see on the forums. With that method though you will have a backup.
Click to expand...
Click to collapse
It doesn't have a name :/ It has a model number (SNB02-NV7A), an edition number (SNB02-NV7A-US-SW), android version (4.4.2), a kernel version (3.1.10) and then a build and hard ware number.
I appreciate the advice though. Thank you!
MrsPurchase15 said:
I appreciate the advice though. Thank you!
Click to expand...
Click to collapse
SNB02-NV7A is the model number for the NABI2S. It's likely the Nabi2S TWRP will work for the tablet. To use it though you will likely have to unlock the bootloader and that will erase all your personal data on the tablet. It's the safer method since you will have a backup of your tablet, but will require you to get your hands dirty.
You can read through this http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 and see if it's something you want to try.
Using the above linked thread as the basic outline, in general you would:
-Setup adb/fastboot and the windows driver.
-Unlock the bootloader(wiping all personal data on tablet)
-"fastboot boot" NOT "fastboot flash" the Nabi2S TWRP recovery to the tablet RAM.
- backup the recovery, boot, system, and addon(preload) partitions. Then you can always recovery the tablet if something goes wrong, and help others that need to recover their tablet.
-Download SuperSU and flash from TWRP to obtain root.
I can help with more detailed instructions but if it's something that seems uncomfortable to try then I don't want to type it all out. Again a kingo root or other root method will likely give you root, I personally like having a clean backup before beginning and there is none in existence yet.
Thank you so much! I am absolutely willing to try it. I can't do much worse to it then the state it's already in.
MrsPurchase15 said:
Thank you so much! I am absolutely willing to try it. I can't do much worse to it then the state it's already in.
Click to expand...
Click to collapse
Again the Nabi general information thread is going to be the biggest help in understanding what needs to be done. That information is here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 The procedure below isn't as long as it looks I tried to add some troubleshooting stuff along the way.
Best to have a mircoSD card for this well at least 4GB. Start with the microSD in your computer if possible.
1) First you will need to grab all the files you need:
-Drivers: Refer to drivers section #4 in the General Info Thread. Your choice if you want to try PDAnet, NabiLab, or Universal Naked Drivers. The NabiLab drivers are self installing and work pretty good in a lot of situations but not always. Download which ever one you choose to your computer. I'm going to talk about Nabilab and Universal as first resorts, we will revisit PNAnet if you are having driver issues.
-ADB and Fastboot tools. Here it's best to refer to section #6 in the General Thread. Specifically:
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.
-TWRP for the NABI2S. Get that file here: TWRP for Nabi2S
After this step you should have downloaded 3 files and the ADB/fastboot files you should have installed. That leaves the remaining 2 files. One should be NABI2S_TWRP271.img, copy that file to the folder where you installed ADB/fastboot(remember you can find that folder by selecting Minimal ADb and Fastboot from your start menu and typing "explorer ." as explained above.) The remaining file is the which ever driver package you picked. If it's universal naked extract the zip file to a place you know. If it's Nabilab drivers go ahead and install them. PDAnet we will try later if these 2 don't work.
2) Boot the Nabi to fastboot with the USB cable plugged in to your computer. Also open device manager on your computer so you can see when the interface comes up. I don't have a Nabi2S so this may be not exactly right. Start with the tablet off. Press and hold the power button AND the vol up buttons at the same time. At some point you should boot up and have a small text menu in the top corner of the screen.(If that doesn't work try power and vol down buttons). One of the menu items will be fastboot protocol. You will want to highlight that text using the volume keys, and then select it using the volume keys.(again I an not sure which is which. Vol - might change which is highlighted, and vol + will select that line, or vice versa, remember which does does what as you will need it later on). Keep trying combinations or timings if it's not working. When it's right your computer will acknowledge a new device plugged in and the device manager screen should show a fastboot or unknown interface.
3) Getting the drivers working. If you chose the Nabilab drivers they should automatically install, and in device manager you should see and item called Android device, and when expanding that entry some bootloader or fastboot interface(When you see this you should be done with this step). The tablet will also switch the text on the screen to say something like "continue", "bootlader", blah, blah. If you went with universal naked drivers this is where you would locate the unknown or fastboot device with the yellow exclamation mark and manually install the driver by pointing them to the folder you extracted(There could be driver signing issues depending on which version of windows you are using. You will have to google "disable windows driver signature enforcement", but basically you will reboot the computer disabling driver signature enforcement. Hopefully if you picked the Nabilab drivers and they work on your computer this step will be pretty painless and not as long as it looks.
4) Unlocking the bootloader. If you have the command window open now great, if not from your start menu select "Minimal ADB and Fastboot" this should open a command prompt. REMEMBER this step will erase all you data on the tablet, game saves, pictures, etc.
Get ready to acknowledge some text on the tablet itself as you have to be pretty quick using the volume keys to highlight and select(Same function as what you noted in step 2). At the command prompt type:
Code:
fastboot oem unlock
OR
Code:
fastboot -i 0x0489 oem unlock
On the tablet some text will pop up asking yes or no do you really want to unlock the bootloader? The selection is made with the volume keys. You should see some confirmation of erasing tablet and completed.
If this step isn't working when you type the command i.e. "waiting for device" the drivers probably still aren't installed correctly. If something failed in this step you may be forced to reboot the tablet and get back in fastboot mode(step2)
5) Install TWRP. With tablet in fastboot mode. Type at the command prompt:
Code:
fastboot boot NABI2S_TWRP271.img
or
Code:
fastboot -i 0x0489 boot NABI2S_TWRP271.img
If you are getting file not found errors the NABI2S TWRP file isn't in the folder. If all goes right the tablet will boot to TWRP. This is where we may have problems as I'm not sure if the NABI2S TWRP can boot the Star Wars Nabi. If it's not booting then we are pretty much done at this point...
6) Getting SuperSU(root). If the tablet booted TWRP. Download this UPDATE-SuperSU-v2.46.zip. Copy that file to your microSD you have inserted in the computer. When that is done safely eject the card from the computer and put it in the tablet.
7) In TWRP select the "mount" tab and check MicroSD(external storage) and the check box should become checked.
8) Make a backup. Select the "backup" tab in TWRP. You will have the options to backup "recovery" "boot" "system" and "preload(or addon)" select all 4 of those. Then select the backup location as MicroSD(external storage). Swipe to backup.
9) Only if step 8 worked install root. Select the TWRP "install" tab. Back out to the highest level, and find external_storage. The UPDATE SUperSU zip should be there. Select it and swipe to install.
10) Only if the step 8 and 9 worked go to the "reboot" tab and reboot. If they didn't work. Press and hold the power key until the tablet shuts off, and we can troubleshoot. If you rebooted the tablet will take a long time to boot initially since you wiped the tablet and it will have to rebuild data. You can then reset up the tablet.
11) Get superSU from Play Store and verify root.
12) If all this work your backup will likely be a benefit to future users so sharing it might be something to consider.
Well.. I followed everything above and it all appeared to work perfectly - however, I still can't access the microSD card to store games. Any ideas?
MrsPurchase15 said:
Well.. I followed everything above and it all appeared to work perfectly - however, I still can't access the microSD card to store games. Any ideas?
Click to expand...
Click to collapse
Are you using an app to do this(like link2sd)? Or just hoping root alone would allow you to do this?
I was hoping the root would allow me but I take it that's wrong, lol.
MrsPurchase15 said:
I was hoping the root would allow me but I take it that's wrong, lol.
Click to expand...
Click to collapse
Haha. Understood. You do need root to do it, but root is needed for the apps that can make it possible. My kids never had the problem when they had their old Nabi2's so I'm not as much help on the "how to" portion but I understand how the apps work. Read through this thread to gain some understanding of what it takes now that you have root. http://forum.xda-developers.com/showthread.php?t=2086338
There is another way also where you stop using internal storage altogether and use an external by editing the ramdisk but it has some limitations as well.
This was awesome i have the same star wars edition and everything works well i even made a backup which i can post and i used the 3.0.1.3 kernel backup to restore the tablet and it still worked