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
Related
Welp, after spending over 26 honest-to-God hours researching a "cure" for this, I am still without a solution. I hope a kind soul will be able to guide me to the light, because I have been unable to find it on my own.
I am going to try to be as through as possible, if for nothing else than doing a mental checklist to see if I missed some obvious step along the journey. Also, maybe a keen observer will be able to spot what I'm doing wrong.
So,
My Asus Prime is bricked. I'm stuck on scenario 3 (according to this post:http://forum.xda-developers.com/showthread.php?t=1514088&)
In chronological order, here's what happened:
1. I'm running Virtuous Prime 1.0
2. I flash ClockworkMod Recovery Touch v5.8.1.8
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
5. I flashed a new ROM, then hit 'reboot system now'
6. I'm stuck at the Asus logo screen; Android won't boot.
I am able to access recovery and activate Fastboot mode; definitely scenario 3.
Then, also in chronological order:
1. I restarted the tablet, pressed the up volume key and accessed the other menu with 3 options
2. I hit the 'wipe data' option
3. Try to boot Android
4. Still stuck at the 3 option screen
From what I read, this situation is likely the result of clockworkMod Recovery flashing a bad kernel. Supposedly, it can fixed by flashing a 'good' kernel via fastboot, which requires both a "stock kernel" and a more recent clockwork mod recovery image.
I downloaded the SDK package and downloaded pretty much everything, including the USB drivers. I downloaded a stock kernel called stock_9.4.2.21_kernel-signed and a CWM recovery image and placed them inside the "tools" folder.
I opened a command window and while having the tablet plugged in, typed 'adb devices'. I get 'List of devices attached' but then a blank space.
Here's what happened next:
1. I re-plugged in the tablet in Recovery mode to my AMD X64 Windows 7 PC and got an "USB device not recognized" message.
2. I went to Device Manager and under "Universal serial bus controllers" I see a yellow triangle mark besides an "unknown device" option.
3. Right click on "unknown device" and try to update the drivers manually using the Universal_Naked_Driver_Beta_0.6.1
4. When I select the folder in which the drivers are located Windows gives me a message of "the best driver software for your device is already installed". Back to step 3.
5. I try "let me pick from a list of device drivers on my computer" and hit "have disk option"
6. Upon choosing the android_apxusb file inside the universal naked drivers folder, I get the following error: "the folder you specified doesn't contain a compatible software driver for your device (...) make sure it is designed to work with Windows for x64-based systems."
7. Try again this time choosing file android_apxusb; same error.
I heard that some Windows 7 x64 users are having issues installing drivers; that may be my case too. I, however, don't have access to any other Window or Macs or Linux PCs in my house. Still, if this is the issue, then I might try redoing things in a different PC at a friend's house or something.
Bottom line? I think I know what to do, but I can't install the universal naked (nor the official Asus Prime) drivers. What now? Is there an easy fix for Brick scenario 3?
I have read God knows how many discussions on the subject, but I haven't been able to find a solution to my issue. I got no support from Freenode #asus-transformer; some ops were even downright rude. Any help is greatly appreciated.
For what is worth, I'll be donating $50 to whoever is able to help me navigate through this issue and get my tablet back and running.
Thanks again for reading this far.
TL;DR: I bricked my Prime and I'm stuck in scenario 3. I will donate $50 dollars to whoever can help me unbrick it.
Hey,
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Go to the freenode IRC Channel "#asus-transformer" on Freenode (http://webchat.freenode.net/?channels=asus-transformer) and ask for help like described in the unbrick thread!
Greetz
Edit: No need for donate!
hanzo001 said:
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
Click to expand...
Click to collapse
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Thanks for your answer; I'll answer yours
djmcnz said:
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
Click to expand...
Click to collapse
1. Yes, in that order; I backed an empty ROM
2. No, I don't have a valid nandroid backup (go figure; just this single freaking time I forgot to backup before wiping data/cache/dalvik cache)
3. No other ROM on my device. I had a new ROM when I performed the flashing, but when I got to the point where I hit "deleate data" in the 3-option menu, I lost everything on the SD card
4. When I wipe and reflash I'm stuck on the same loop. Maybe flashing a 'good' ROM will fix it; the issue is, my PC doesn't know what I'm plugging in when I connect the tablet to it.
Thank you for your support
Thank you, I'll try a Live CD. I'm downloading now even as we speak.
When that's finished, I'll grab the Linux files.
I guess that sorts of confirms my hypothesis that my main issue is with Windows... *sigh* WINDOWS!
I tried getting help from freenode's #asus-transformer in the past, but... lets say that on the overall my experience could have been better. I'll try again later tonight, where hopefully I'll be able to talk to RaYmAn, a volunteer in the original Diamonback post who is offering supports to users in my specific situation.
By the way, thanks for pointing me with a clickable link to the IRC chat; I've never used IRC before in my life, and getting it to work, dumb as it may sound, took me quite to figure out. Thank you again for your help and support!
chrischdi said:
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Click to expand...
Click to collapse
Thank you for your answer. It is really nice to have a helpful person around; Like I mentioned in my op, my experience on freenodes' #asus-transformer chat was a bit... discouraging. I figured most would want some form of payment for their time, but here you both are, proving that there is kindness in this world.
I'll address your comments:
1. I did wipe /System; after NOTHING I tried on recovery worked, I did manual wiping of everything, trying to boot each time; similar results.
2. I do not have a good ROM on the memory card. Before doing the 'wipe data' from the 3-option menu, re-flashing a good ROM did no good nevertheless. From here is where I started suspecting that it was the fault of CWM not flashing a proper kernel.
3. I tried the advanced restore as well, an like in #1, I tried rebooting each time, just to make sure it would work. But it didn't.
Thank you again for your support. It feels great to know there's someone backing you up out of the goodness of their heart.
Right now I'll try to redo my steps from a Live CD Linux environment; hopefully that'll work. Freaking Windows...
Doktaphex said:
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Click to expand...
Click to collapse
Thank for your support, guys
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
hanzo001 said:
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
Click to expand...
Click to collapse
Hope it works out for the best, life is better with a little Nix in it.
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
You cannot use an external SDcard with any version of CWM for the Prime.
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Thanks for the thought. I tried that too; for some reason, ClockworkMod Recovery won't read the SD card at all!
Linux
[Update]
In general, this could be going better.
I finally got Ubuntu.
I plugged in the tablet while (the tablet is) on recovery mode, and nothing happens.
I was expecting a pop-up menu, or a notification somewhere acknowledging that I connected a device to the PC, but nothing. I'm just going to assume that Linux somehow knows.
I then downloaded the Android SDK for Linux, unziped, and there's no executable file inside. I'm supposed to download the rest of the file via the terminal, apparently, but this one doesn't work like its Windows counterpart either, so I have no clue what to do now.
Jesus...
Bottom line: I'm in Linux, I downloaded the Android SDK, the universal naked drivers and a stock kernel. Now what?
Try to get ADB running in the recovery mode.
In the files of ViperMOD are the executables. Just open up a console / shell and go to the directory via the "cd" command.
Then in the ViperMOD directory execute "sudo ./adb shell" to try the adb connection.
If the adb connection is ok, mount the sdcard via Recovery Menu and then push a file / rom to the sdcard.
For example with the command:
"sudo ./adb push /media/rom.zip /sdcard/"
(I don't know if this are the correct paths.)
Greetz
Thank you, Chris.
While on the terminal, I'm inside the viperMOD folder. Whenever I try execute "sudo ./adb shell" I get this: "sudo ./adb: order not found"
The tablet is plugged in, and in recovery mode.
I haven't installed Java nor the Android SDK because I haven't figured out a way to do it --why can't Linux be double-click action-oriented? *sigh* Anyway, does not having those things installed have something to do with the answer I'm getting from the Terminal?
If so, how in the world do I install them?
I'm never using Touch Recovery again, my word.
Thanks in advance.
Hey,
are you sure that there is "order not found?"
Try the command "ls" to see what files are available. If there is one, called "adb" you are in the right directory. If there is no "adb" then you have to move to the right directory.
Maybe you could try a "chmod +x adb" first and then execute "sudo adb shell" or such if you are in the right directory.
This is going to sound like a stupid question and sorry if it does. but you can access clockwork still right? what happens when you try to flash back your backup? This is important because I had an error sort of like yours that no one could solve here want to make sure its what happened to me. When i tried to restore the original rom it would get to the part where it was restoring data partition and then error on me reading file or something like that. If thats what you see i know the answer. or at least how i fixed mine.
push a rom
Read NIlsonf post about how to adb push a rom to cwm, you get a stock rooted rom
And adb push the blob file, then run the dd command, unmount staging mount data.
This is what fixed mine, and it looks like it fixed nilsonf's also.
Was this ever resolved? I have the same issue and it looks like I've been through many of the same steps as you've gone through. If you were able to do anything to fix it, please let me know.
I would even up the reward to $100.
Just thinking
Why dont you get someone elses CWM backup and adb push it to the device and restore it from that?
Does anyone else have the issue where the Clockwork mod wont install. I have tried using rom manager, and did the terminal and pushing the blob file through but it just refuses to install. All the transformer does is give me a logo. The next step i tried is using the Goo manager to install the recovery but same thing, it refuses to boot to it or install technically!!
PLEASE HELP! does anyone know what im doing wrong or if there is a way to fix this?
(if this is the wrong forum for this please inform me immediately.)
hahmoode said:
Does anyone else have the issue where the Clockwork mod wont install. I have tried using rom manager, and did the terminal and pushing the blob file through but it just refuses to install. All the transformer does is give me a logo. The next step i tried is using the Goo manager to install the recovery but same thing, it refuses to boot to it or install technically!!
PLEASE HELP! does anyone know what im doing wrong or if there is a way to fix this?
(if this is the wrong forum for this please inform me immediately.)
Click to expand...
Click to collapse
On an unlocked device I don't think there can be aproblem to install a recovery.
All methods (terminal one or apps like Rom Manager and Goo) are in fact the same, copying the img or blob file in the flash partition, and the real flash occurs at next boot.
hahmoode said:
Does anyone else have the issue where the Clockwork mod wont install. I have tried using rom manager, and did the terminal and pushing the blob file through but it just refuses to install. All the transformer does is give me a logo. The next step i tried is using the Goo manager to install the recovery but same thing, it refuses to boot to it or install technically!!
PLEASE HELP! does anyone know what im doing wrong or if there is a way to fix this?
(if this is the wrong forum for this please inform me immediately.)
Click to expand...
Click to collapse
yes should be in Q & A
1. YOU ARE NOT RUNNING ASUS SOFTWARE ANYMORE. THAT IS WHY ASUS PROVIDED A WARNING WHEN YOU UNLOCK. YOU SHOULD EXPECT ISSUES WITH ROMS, IT IS BOUND TO HAPPEN.
2. The full wipe of the internal SD is for a fresh start. Its basically the same as re-installing windows, Kiss all your stuff goodbye unless you back it up beforehand. Don't cry to use that you lost your stuff because you decided to rush and not read the menu and select the correct choice.
3. Team Wookie are normal people with normal jobs and somewhat normal families that in turn this things take priority first, NOT YOUR PRIME. If issues arise we will work best with you as long as you are respectful and not a prick towards the team demanding stuff. We will address these issues on our clock, not yours.
4. Any future things you would like to see in future editions of this ROM please send me a PM and I will forward the information on to the rest of the team to discuss if it is possible. Keep in mind that we will not include paid apps in this rom because we will not rob out of other developers pockets for their hard work and also dropping the soap in prison leads to bad things that we want to avoid. JUST BECAUSE A REQUEST IS MADE IT DOES NOT GUARENTEE THAT IT WILL BE HONORED OR IN THE NEXT VERSION WHENEVER IT COMES OUT.
5. Team Wookie greatly appreciates all it's followers and feedback so don't ever think that your not appreciated, at least when it comes to a rom on a tablet level, the rest of your real world life is on you.
6. RESEARCH RESEARCH RESEARCH. We know there are a lot of posts now, 178ish pages and growing, please search through these pages to see if a solution has been found to your problem first before posting.
7. This is not the forum to ask how do I root my tablet or flash a rom. There are plenty of other threads on XDA and videos on youtube that explain how to do it with the current version software that you have.
This has been a public service announcement from Team Wookie, Long live the rebellion.
---------- Post added at 09:14 AM ---------- Previous post was at 09:06 AM ----------
Download goo manager from the play store and in the upper right hand corner select recovery. It will ask for superuser permissions then let it do its thing. However it will not show a progress bar or anything but rather just go back to the main menu. Just wait a few minutes and you will ge a pop up saying it is now installed.
---------- Post added at 09:17 AM ---------- Previous post was at 09:14 AM ----------
This is not an issue because the rom is designed to work this way and I have flashed it this way many times. I have a video coming up shortly showing the whole install from twrp to desktop, im just editing it now. If anyone is feeling scared about doing this before you flash get the adb software package and try to push a test file to your tablet ( i just made a test.txt file) and see if it actually works. If the poop hits the fan then you know you can always push the zip file back because you confirmed ADB working with your computer and tablet.
For those having ADB issues follow this guide I made up. the best thing to do is to try to push a test file before you flash is you are going to super wipe and if you are really that nervous about it. This is based off of windows 7 64 bit but should be the same for windows 7 32 bit. I can confirm this works. Regardless ADB is good to have if you run any Android devices, not just this ROM so in case poop ever hits the fan here ya go:
This solved it for Winblows 7 64 bit. For others having the same problem on Winblows 7 64 bit (should be the same for 32 bit miuns the X86 Directory)
1. Go into settings on the prime and make sure USB debugging has a check in it in under SYSTEM > Developer options > USB Debugging
2. Plug your prime into your Winblows 7 laptop and let it install its drivers. Open up device manager by going to Start > Control Panel > Hardware and Sound > and click on device manager under devices and printers. If you see at the top of device manager ASUS Android devices and when you expand it you see ASUS Android Composite ADB Interface you already have the ADB drivers installed and can skip down to #6
3. Go to ASUS website and download the USB drivers for the TF201. Download Vipermod Primetime 4.6 here for the ADB drivers http://goo.im/devs/viperboy/Prime/vi...eTime_v4.6.zip then extract the zip file to a normal file. You only need the drivers from the tool.
4. Plug your prime into your Winblows 7 laptop and let it install its drivers. Open up device manager by going to Start > Control Panel > Hardware and Sound > and click on device manager under devices and printers.
5. You should see the prime listed under portable devices. Uninstall the driver then update the driver manually. Browse to the folder you created from the Vipermod primetime zip. Make sure there is a check in check sub folders. Winblows should detect the drivers and then convert the prime to a ASUS Android Device.
6. Go into settings on the prime and make sure there is no check in Launch ASUS Sync under PERSONAL > Accounts & Sync > Launch ASUS Sync
7. Press Control, Shift, Escape at the same time and make sure there are no instances of ASUS Sync or Splashtop runnung in services in Winblows 7.
8. Download and Install the latest Android SDK. I installed all the libraries and such just to be on the safe side. http://developer.android.com/sdk/index.html
9. DISCONNECT YOUR PRIME FROM THE USB AND REBOOT YOUR PRIME AND YOUR WINBLOWS LAPTOP. After both devices reboot plug in your tablet into your Winblows laptop.
10. Navigate to C:\Program Files (x86)\Android\android-sdk\platform-tools and click on the ADB file. A command prompt will open and spool up a bunch of stuff then close. All the stuff spooling I am assuming was the ADB server starting.
11. Hold down shift then right click inside platform-tools folder and select open command prompt here. You should be in a command prompt window showing the directory C:\Program Files (x86)\Android\android-sdk\platform-tools
12. type adb devices. You should see your primes serial number pop up.
13. make a test file in the platform-tools directory, i just used a simple text file to test then type:
adb push test.txt /sdcard/
It would be easier to just put the Rom you are going to flash in this directory so when it is time to push the rom it would be:
adb push nameofrom.zip /sdcard/
If SDCARD not recognized try:
adb push nameofrom.zip /system/media/
14. browse to your sdcard and you should see your file there. If you are already in the sdcard folder window on your prime, leave the folder then come back and it should be there.
15. You should be able to push files now after superwiping. You may need to push to /system/media/ if /sdcard/ is not found. Make sure you have all the / in the directory structure when pushing.
16. From inside recovery select install zip from sdcard and browse to the folder you pushed it to then flash awa
Sent from my Transformer Prime TF201 using xda app-developers app
So with those steps it still hasn't installed recovery! So the thing is that i have full root, and my prime is unlocked, but it just WONT install recovery using any app or manually! Is there a idea on why my prime wont let me?
(Thanks for that long answer btw i tried a lot of it but stil no dice )
Have you tried twrp? The link is HERE. I found its more reliable on the prime. Just my opinion.
fredgar75 said:
Have you tried twrp? The link is HERE. I found its more reliable on the prime. Just my opinion.
Click to expand...
Click to collapse
I will deff try it when i get home from work thank you i will let you know later! (THANKS SO MUCH FOR SOME MORE ADVICE ON THIS)
Ok just to be sure. You did unlock through asus? And you are rooted I know you said you have but just want to make sure. The only reason you wouldnt be able to flash a recovery is if your not unlocked. Just trying to rule out the obvious.
Simple steps:
1-Unlock prime
2-Download the ROM of your choice.
3-Download Goo Manager from the Play Store. Open it and hit menu - Install OpenRecoveryScript. The app will ask for su perms and may exit back to the main screen. Hit the install button again and the app will download the recovery, flash it and reboot. You'll see the flashing process and your tablet will reboot again. At this point you can hold vol down, then up to enter recovery.
4-Flash ROM
5-Profit!!
Doesn't get any easier, takes about 10 minutes for everything.
I used the multi root tool, viper mods tool I think it was, from a long time ago that was designed for rooting the .15 firmware, even though I was on .21 or .28 and I didn't use it to root, I only used the option to install recovery, which installs the latest TWRP recovery when I had a similar issue.
It worked great, I just ran the program on the computer and told it to install recovery.
Sent from my ADR6425LVW using xda premium
Hi to All,
Well I got an ASUS TF201 March 2012 and I never messed with it much, just net surfing and watching movies and listening to music....
I wanted to get rid of some apps that I dont use at all e.g Amazon Kindle but found out with research that I can do that. Also tried to use apps like Titanium Backup again I couldnt. I am new to the Tablet world this is my first. So I did some research and terms of root, unlock etc came up. So I know the difference between them. In order not to lose my warranty and since I just want to be able to delete certain unwanted apps and add other apps, I just want to for now root my TF201.
Did more research but I still cant get an answer or get some of the methods to work for me.
Below is the specs for my Asus TF201
1. So I have JB (Android Version 4.1.1), dont know if it came with it or got updated like I said I didnt mess with the tablet alot
2. Build #: JRO03C.US_epad-10.4.2.17-20121018
I plugged in the USB to my Windows XP laptop for the first time today and ofcourse I am missing the drivers. I went to ASUS website and couldnt figure what I need.
1. Does anyone have the ASUS Sync that I need on my laptop
2. Also does anyone have the drivers that I need on my laptop so my ASUS is recognized. I installed some drivers from the xda forum to use the DebugFS Root but got a message that I need to install the latest drivers. Does anyone have them or can tell share a link for me to get them.
All I want basically is to have the current drivers on my laptop and the ASUS Sync thing and be able to ROOT my tablet. Most of the threads I read are for the Android Version ICS 4.0.
Any help on this is greatly appreciated
Thanks
RB
ramez75 said:
Hi to All,
Well I got an ASUS TF201 March 2012 and I never messed with it much, just net surfing and watching movies and listening to music....
*SNIP*
1. Does anyone have the ASUS Sync that I need on my laptop
2. Also does anyone have the drivers that I need on my laptop so my ASUS is recognized. I installed some drivers from the xda forum to use the DebugFS Root but got a message that I need to install the latest drivers. Does anyone have them or can tell share a link for me to get them.
All I want basically is to have the current drivers on my laptop and the ASUS Sync thing and be able to ROOT my tablet. Most of the threads I read are for the Android Version ICS 4.0.
Any help on this is greatly appreciated
Thanks
RB
Click to expand...
Click to collapse
Asus Suite including Sync:
http://support.asus.com/Download.as...ite_v1_0_41.zip#ASUS_Pad_PC_Suite_v1_0_41.zip
I just went through the unlock part yesterday so fresh in the mind it ASSUMES AN SD CARD IS INSTALLED and WINDOWS OS!
Asus Unlock Tool:
http://support.asus.com/Download.as...ck_Device_App_V6.apk#UnLock_Device_App_V6.apk
Get TWRP for TF201Jellybean:
TWRP Page
On that page are instructions including a download link for JB BOOTLOADER ONLY! MAKE SURE YOU GET THE RIGHT TWRP FILE FOR YOUR DEVICE. THE ICS ONE IF YOU ARE ON ICS, OR THE JB ONE IF YOU ARE ON JB:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
Download bin4ry's root tool to get the ADB file
When that is downloaded you can compare the MD5 hash because its a good idea to do that. You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Use it to generate an MD5 hash of the TWRP download to what it saysthe files MD5 hash is on the download web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Then I downloaded Ultimate Backup Tool from here:
http://goo.gl/iOUwe
Unzip it so you have fastboot.exe
Rename the TWRP you downloaded to TWRP.blob and copy it to where you have fastboot unzipped.
Finally download SuperSU zip file from:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
Now we need to unlock the device. Copy the unlocker APK to the SD card. Run a file explorer on our tables and browse to the SD card (/Removable/MicroSD). Tap the APK to install. Once installed run the Icon for the unlocker and follow directions. There are several warnings etc.. You will need wifi connected and it will unlock your device and VOID YOUR WARRANTY!.
The unlock will take a few minutes. When it is successfull you will see a notice on device boot up that says the device is unlocked.
Once unlocked, power it off. Once off power it onby holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install. I got drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here"
if you don't get the command window here option then you will have to open a command prompt. open the run dialog and type CMD and hit enter. This will get a dos command windows. Use the change directory (CD) command to change the current folder in the DOS window to where your fastboot file and TWRP.blob are.
In the command window paste:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted.
Once I confirmed my Stock OS loaded I copied the Super SU zip file we downloaded above over to the device via the USB cable to the root of my SD card. Once the copy complets shutdown the device again.
Once off, power it on and press and hold both the power buttons and volume down again. When the menu appears you should already have RCK (recovery) hightlighted so press volume up to load TWRP recovery.
Once TWRP loads the top left option is "Install" tap that.
You will see a few choices, select the radio button to install from SD card (external source it may say). Tap the super su zip file: Superuser-3.1.3-arm-signed.zip to choose it.
Slide the slider at the bottom to the right.
This will flash superSU to your device. When done, reboot (should only take a few seconds).
When you boot up SuperSU is installed.
To test root with ADB:
Your tab must be plugged in to the USB port of the computer of course.
If you installed the SDK tools it is there or use the one from bin4ry's root tool as follows:
Unzip the downloaded root tool from bin4ry mentioned above. Use the command windows to change directory of the unzipped folder and further in to the "STUFF" folder. type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the command sudo on my tab so every time in a terminal I want root I will type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Edits:
I have editted this based on questions below to make it more complete..
First Thank yo uso much for taking the time and sharing the good info. Ofcourse there is alot of foreign terminology you have used and I will need to read you reply a number of time till it soaks in and I am sure I will have follow-up questions.
So it seems the only way I can get to root my TF201 (running JB) is to unlock it which means losing the warranty. Well if thats the only route then so be it....
I guess first thing is to successfully unlock the TF201
hx4700 Killer said:
Asus Suite including Sync:
http://support.asus.com/Download.as...ite_v1_0_41.zip#ASUS_Pad_PC_Suite_v1_0_41.zip
I just went through the unlock part yesterday so fresh in the mind it ASSUMES AN SD CARD IS INSTALLED and WINDOWS OS!
Asus Unlock Tool:
http://support.asus.com/Download.as...ck_Device_App_V6.apk#UnLock_Device_App_V6.apk
Get TWRP for TF201Jellybean:
http://teamw.in/project/twrp2/93
On that page are instructions including a download link for JB BOOTLOADER ONLY!:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
When that is downloaded you can compare the MD( its a good idea to do that). You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Use it to generate an MD5 hash of the TWRP download to what it says on the web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Then I downloaded Ultimate Backup Tool from here:
http://goo.gl/iOUwe
Unzip it so you have fastboot.exe
Rename the TWRP you downloaded to TWRP.blob and copy it to where you have fastboot unzipped.
Finally download SuperSU zip file from:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
Now we need to unlock the device. Run the unlocker tool you downloaded. For here its fuzzy for me because I found the APK file I got from the Asus download and copied it over to my tablets SD card via USB. Then I used the built in file browser to find it on my SD card and ran it. By whatever means you will need to run the unlocker tool on your tablet to unlock. You will need wifi connected and it will unlock your device and VOID YOUR WARRANTY!.
The unlock will take a few minutes. When it is successfull you will see a notice on device boot up that says the device is unlocked.
Once unlocked, power it off. Once off power it onby holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install. I got drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here"
In the command window paste:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted.
Once I confirmed my Stock OS loaded I copied the Super SU zip file we downloaded above over to the device via the USB cable to the root of my SD card. Once the copy complets shutdown the device again.
Once off, power it on and press and hold both the power buttons and volume down again. When the menu appears you should already have RCK (recovery) hightlighted so press volume up to load TWRP recovery.
Once TWRP loads the top left option is "Install" tap that.
You will see a few choices, select the radio button to install from SD card (external source it may say). Tap the super su zip file: Superuser-3.1.3-arm-signed.zip to choose it.
Slide the slider at the bottom to the right.
This will flash superSU to your device. When done, reboot (should only take a few seconds).
When you boot up SuperSU is installed. ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Click to expand...
Click to collapse
Yes, unlock it. There is no root method for tf201 on JB outside of unlock. An exploit may come up some day but nothing soon I would wager.
I tried to organize it by Al the stuff you need to download first. Then steps to use what you downloaded. It you follow it precisely things would become clearer.
Hi,
Ok I was going through the instructions and downloading all the necessary files and I ran into an issue with downloading the TWRP for JB. Well the link you have allows me to download either the *.img or the *.blob extensions. So I went ahead and downloaded the *.blob extension. I did the MD5 as you recommended and visually checked it with the image on the website and they dont match. I got the below
"b6bae17dac81a126d5d3ad8e27fd5007" which is entirely different than the one on the webpage. I also tried the *.img and no luck there. So I stopped. What do I do now where can I get the TWRP
Thanks
hx4700 Killer said:
Get TWRP for TF201Jellybean:
http://teamw.in/project/twrp2/93
On that page are instructions including a download link for JB BOOTLOADER ONLY!:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
When that is downloaded you can compare the MD( its a good idea to do that). You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Use it to generate an MD5 hash of the TWRP download to what it says on the web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Click to expand...
Click to collapse
hx4700killer
I did some googling and found the below link
http://forum.xda-developers.com/showthread.php?t=1510737
the link has "Direct apk link (dropbox)"....Is this what you referred too? I downloaded the file, should I move it to the SD card and run it from within the tablet?. Is there a way to run an apk file.
Also
I downloaded Android SDK on my laptop. I run the eclipse.exe as per the instructions on the website but nothing happens
Thank you
RB
Download the APK from the link I gave above. It comes straight from ASUS. I had gotten it 2 months ago and I guess I thougth I had run an installer and copied the APK from there but it is in fact just an APK to download directly.
When you copy it to the SD card nothing is needed to run it. Just tap on the file in a file explorer on the tablet and it will install itself. once installed run the installed unlock app and follow the directions.
The link from ASUS has a zip file. So i did download it and extract it to the SD card. Moved the SD card to the tablet but there is no apk file.....Also do i use the twrp file even if the md5 didnt match.
Thanks
Sent from my Transformer Prime TF201 using xda app-developers app
ramez75 said:
The link from ASUS has a zip file. So i did download it and extract it to the SD card. Moved the SD card to the tablet but there is no apk file.....Also do i use the twrp file even if the md5 didnt match.
Thanks
Sent from my Transformer Prime TF201 using xda app-developers app
Click to expand...
Click to collapse
The second link that says it is for the unlock tool is the APK.
Ok the unlock worked successfully. So my TF201 is unlocked.
Following the rest of your post, next thing on the hit parade is to have the correct TWRP for JB (Open_recovery_TWRP.blob). At this point the MD5sum using WinMD doesnt match the image on the website. Do I still go ahead and use it or will it cause issue....
Ofcourse I dont understand what is the use of the MD5sum number
Thanks
hx4700 Killer said:
Download the APK from the link I gave above. It comes straight from ASUS. I had gotten it 2 months ago and I guess I thougth I had run an installer and copied the APK from there but it is in fact just an APK to download directly.
When you copy it to the SD card nothing is needed to run it. Just tap on the file in a file explorer on the tablet and it will install itself. once installed run the installed unlock app and follow the directions.
Click to expand...
Click to collapse
ramez75 said:
Ok the unlock worked successfully. So my TF201 is unlocked.
Following the rest of your post, next thing on the hit parade is to have the correct TWRP for JB (Open_recovery_TWRP.blob). At this point the MD5sum using WinMD doesnt match the image on the website. Do I still go ahead and use it or will it cause issue....
Ofcourse I dont understand what is the use of the MD5sum number
Thanks
Click to expand...
Click to collapse
The MD5 is confirmation that what you downloaded matches what was uploaded to the server. It runs an algorithm against the file contents and generates that long number. When you compare the number to what is on the server page they should match.
If they don't match then HELL NO do not flash it or you will have a bricked device. Redownload it and don't flash anything unless the MD5 matches.
I totally missed that you posted this above or I would have told you sooner.
Thanks, well then i cant use that link i cant get the MD5 to match. I will google and see if I can find a twrp file that will work for me
hx4700 Killer said:
The MD5 is confirmation that what you downloaded matches what was uploaded to the server. It runs an algorithm against the file contents and generates that long number. When you compare the number to what is on the server page they should match.
If they don't match then HELL NO do not flash it or you will have a bricked device. Redownload it and don't flash anything unless the MD5 matches.
I totally missed that you posted this above or I would have told you sooner.
Click to expand...
Click to collapse
ramez75 said:
Thanks, well then i cant use that link i cant get the MD5 to match. I will google and see if I can find a twrp file that will work for me
Click to expand...
Click to collapse
This is the MD5 hash that you should get:
19d93f4ec4685b8124468684eb2913fc
This is the exact download link I used for my TF201 running the most recent JB Update:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
The file you get is: openrecovery-twrp-2.3.1.0-tf201-JB.blob which is the one I say to rename to twrp.blob
I would NOT flash anything not from the source on this one. If its wrong your device is trash.
Hi again,
Ok so i got the correct TWRP.blob and I changed its name and put it in the folder with fastboot.exe. i plugged in my tf201 to my laptop followed the power volume sequence. I held the shift and right clicked on the folder but i didnt see "Open command window here". So how do i got about that. Do i use the "cmd" in the run from start to open the black dos screen and change directory (cd..) till i get to the folder that has the fastboot.exe
Thanks
hx4700 Killer said:
Once unlocked, power it off. Once off power it onby holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install. I got drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here"
In the command window paste:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
...
Click to expand...
Click to collapse
Yes, just open CMD and "cd" your way to the directory. Just make sure you end up inside the directory (ie. "...\UBTv1.3.2>")
ramez75 said:
Hi again,
Ok so i got the correct TWRP.blob and I changed its name and put it in the folder with fastboot.exe. i plugged in my tf201 to my laptop followed the power volume sequence. I held the shift and right clicked on the folder but i didnt see "Open command window here". So how do i got about that. Do i use the "cmd" in the run from start to open the black dos screen and change directory (cd..) till i get to the folder that has the fastboot.exe
Thanks
Click to expand...
Click to collapse
Followed all the instructions and seemed all were successfull. I see a Superuse icon created. What do you mean by ADB? and what will yield root when I type?, where do I type?. I dont understand the last sentence, please can you empahsize on it
Thanks again
hx4700 Killer said:
ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Click to expand...
Click to collapse
ramez75 said:
Followed all the instructions and seemed all were successfull. I see a Superuse icon created. What do you mean by ADB? and what will yield root when I type?, where do I type?. I dont understand the last sentence, please can you empahsize on it
Thanks again
Click to expand...
Click to collapse
Lol, guess I didnt include one of those in the downloads. After flashing TWRP I assume you "Installed" the superuser zip? This is what roots the device.
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
http://ul.to/xdevcthz
Your tab must be plugged in to the USB port of the computer of course.
Download the ZIP file and decompress. Use CMD to change directory to the unzipped folder and further in to the "STUFF" folder. type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the sudo on my tab so every time in a terminal I want root I will type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
Adding:
i just remembered that you said you downloaded the android SDK. ADB is in amongst those files as well.
By the i still didnt follow the below instructions but it seems i am already rooted because i was able to download titanium backup. So what will the below steps give me more.
Also how do i get rid of apps like Amazon kindle??.....
Below you say that you used the method from binary but you also say it doesnt wok with the prime. So i presume tf201 is the prime, so i still follow the below right
hx4700 Killer said:
Lol, guess I didnt include one of those in the downloads. After flashing TWRP I assume you "Installed" the superuser zip? This is what roots the device.
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
http://ul.to/xdevcthz
Your tab must be plugged in to the USB port of the computer of course.
Download the ZIP file and decompress. Use CMD to change directory to the unzipped folder and further in to the "STUFF" folder. type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the sudo on my tab so every time in a terminal I want root I will type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
Adding:
i just remembered that you said you downloaded the android SDK. ADB is in amongst those files as well.
Click to expand...
Click to collapse
ramez75 said:
By the i still didnt follow the below instructions but it seems i am already rooted because i was able to download titanium backup. So what will the below steps give me more.
Also how do i get rid of apps like Amazon kindle??.....
Below you say that you used the method from binary but you also say it doesnt wok with the prime. So i presume tf201 is the prime, so i still follow the below right
Click to expand...
Click to collapse
What I meant was I use ADB from that root method from bin4ry. He includes ADB.EXE and needed DLL files so its a quick one stop shop for ADB.
Does the adb shell command give you anything? No its just proves root is available. Rootcheckers can also do it. ADB is just a way in to your device from a desktop machine.
I have never removed an APP but I believe removing its APK file from /system/app folder allows it to be removed or does remove it. ( i would save it somewhere in case you need/want it back)
Thank you for an easy to follow way to root a 4.1.1 JB OTA TF-201. It worked exactly as you described.
You may want to let some of the noob users know what in each zip file they need. It really helps if all the files you download are in one location unless you are familiar the windows command line.
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
I am attempting to build a compatibility file for my Polaroid PMID1000. Unfortunately this old device uses a special touch screen driver I have never found on other devices, and it is using kernel "3.0.8 #139 PREEMPT". I am using an older rom found here: http://www.slatedroid.com/topic/64378-rom-carbonrom-422/ and have success booting on my compatibility file. The issue is the touch screen is not interacting with the OS (there are other issues but I want to tackle this first). The kernel allows me to boot and the android GUI starts up (I can interact with a mouse just fine). Getevent shows me interacting with the screen so touches are being generated, but they are not getting to the GUI. Looking for any help you may want to provide.
Files can all be found here, including a logcat, dmesg, lsmod my compatibility zip as well as the carbon rom and gapps . https://drive.google.com/folderview?id=0B0c1jpaziDZ-S2hoczN0U0FiN3M&usp=sharing
going forward not backward
So I built a new kernel (3.0.101+) and have the gsensor and touch working now. Install the Carbon ROM, the GAPPS and the new compatibility file: PMID1000_carbon.compatibility-v1.zip
The only issue I have is no sound from the speaker, if you plug in a head set the sound is there.... anyone have an idea on this?
Domenic
new script.bin for sound and aokp support
I have updated the file and there is now sound support. I had a typo in my script.bin! I have also included a zip file for aokp_907_unofficial_2013-08-03.
PMID1000_carbon.compatibility-v2.zip
PMID1000_aokp.compatibility-v2.zip
Domenic
the process
domenictroilo said:
I have updated the file and there is now sound support. I had a typo in my script.bin! I have also included a zip file for aokp_907_unofficial_2013-08-03.
PMID1000_carbon.compatibility-v2.zip
PMID1000_aokp.compatibility-v2.zip
Domenic
Click to expand...
Click to collapse
So...I have the PMID1000, but what exactly is the process for this? I plan on using the CarbonROM(most likely). I have the Livesuite software on my pc, and all. I'm just curious as to what steps I need to take to make this thing work well? haha
I apologize for my ignorance,
Jonathan
jonathanhatch88 said:
So...I have the PMID1000, but what exactly is the process for this? I plan on using the CarbonROM(most likely). I have the Livesuite software on my pc, and all. I'm just curious as to what steps I need to take to make this thing work well? haha
I apologize for my ignorance,
Jonathan
Click to expand...
Click to collapse
Firstly remember that all data will be wiped from the tablet, and the camera's will not work; also I would not expect a beginner to attempt this so I will not write up a detailed step-by-step, but an overview of the files and when/how they will be used. Of course you will require a computer and a USB connection to the tablet and the drivers required. I am not certain if Windows Update will find them, so you may need to find them as well.
With all the above in mind lets start (note I am doing this from memory as I do not have the tablet handy):
You need to start by installing cwm (cwm6028-a10-9part-v2.zip) on the tablet. For this you will need a copy of adb.exe, which I have provided as the file adb.zip on my Google Drive which includes the files you need. The tablet will need to have USB Debugging enabled.
Enable USB Storage
Unzip all files in cwm6028-a10-9part-v2.zip and transfer them to the tablet.
Turn off USB Storage
From a command prompt (cmd.exe in windows) change to the directory when you have unzipped adb.zip and run the command 'adb shell' you will get another prompt. Note I have 'quoted' the commands but the quotes are not required when you run the commands.
type 'cd /mnt/sdcard'
type 'ls' and verify the file recovery.img is in this directory and if it is
type 'cat recovery.img > /dev/block/nandg'
once this command has finished type 'echo -en "boot-recovery\0" > /dev/block/nandf; sync; reboot'
The tablet will restart in cwm.
To move around in cwm use the home button to move the selection down and the power button to select.
copy the following files (do NOT unzip them) to the same directory as you put adb.exe.
CARBON-JB-UNOFFICIAL-20130619-1010-907.zip
gapps-jb-20130812-signed.zip
PMID1000_carbon.compatibility-v2.zip
On the tablet choose the option "install zip from sideload"
At the windows command prompt type 'adb sideload CARBON-JB-UNOFFICIAL-20130619-1010-907.zip'
Note you may need to run the command again if your computer has not found the tablet device.
Repeat the above two steps for the other two zip files.
Once completed on the tablet choose the option "wipe data/factory reset" then the option "reboot system now" Note the first reboot of the table will take longer than you would expect, don't worry you will get back to a functional tablet in about 5 minutes. Note the "wipe data/factory reset" is extremely important as you will not get a functional tablet if you skip this step.
Domenic
WOW. Far superior to my half-root/play store work around I was using before.
Thank you! This works really well on my PMID1000. Great instructions too!
I've noticed that with the Carbon ROM I don't have on-screen volume keys. Is that normal, or should I try clearing the cache, and doing another wipe data/factory reset?
I'm going to try the AOKP ROM next.
Thanks again, Domenic! It's hard to find anyone doing any development for these. I guess that means I should upgrade sometime haha
Jonathan
P.S. Any chance you know how I could adjust the internal partition to allow more space for apps?
I have not found a way to get the volume on the bottom screen, these builds do not allow for it.... but you could try an app from the play store, look for status bar volume and you should find something. The one other real issue I have besides the camera not working is the speakers do not disable when you plug in a head phone. It is fine until you want to use it on the bus and don't want to distract anyone.
I am not certain that you can make the app size larger, but you could try to install Link2SD from the playstore. It allows you to move (link) applications to you SD card freeing up space.
PS I am not a real developer, just a bit of a hack to cobble this together...