I just rooted my Prime using the new method. It has an unknown serial. I found this ratchet tool: http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/
How can I get it to work? When I type adb push ratchet /data/local/, I get an error saying "failed to copy 'ratchet' to '\data\local\\ratchet' : Permission denied.
have to type in "su" to get root rights
I have uploaded a screenshot of the problem.
I can't type su before I enter adb shell. And when I do, the device is not found. Drivers are installed. It is recognized in my computer.
Okay, so I manually copied the ratchet file to the tablet using a file manager. Then in ADB I typed the commands. It asked for serial number, I entered it. Told me to restart and it should be fixed but the serial number is still unknown in settings
Any ideas on how to get it to work? Or does it just not work on jellybean and I'll have to send it in (again) ?
QUOTE=sahilcc7;40175980]Okay, so I manually copied the ratchet file to the tablet using a file manager. Then in ADB I typed the commands. It asked for serial number, I entered it. Told me to restart and it should be fixed but the serial number is still unknown in settings
Any ideas on how to get it to work? Or does it just not work on jellybean and I'll have to send it in (again) ?[/QUOTE]
You could try asking for help from one of the developers of ratchet tool.
http://forum.xda-developers.com/newreply.php?do=newreply&p=40175980
https://github.com/IEF?tab=activity
I am willing to supply logs and experiment if we can get some help.
Download file for Ratchet
Hello,
Not sure if I'm supposed to be posting on such an old thread (let me know, I'm new). I'm getting the "unknown serial" error on my TF700T. I'm trying to download ratchet using the link that was provided, but all I'm getting is a 404 error, so can't download it. I cannot for the life of me find anywhere else to download that file, they all point to that broken site. Does anybody happen to still have that file that they would be willing to send me? I would appreciate it so much!
Related
So as the title suggests whenever I run the crackin.bat file in order to prepare my legend to be downgraded, it always displays the
cr--rw---- 1 1001 2002 90 line instead of the needed crwxrwxrwx 1 1001 2002 90 line.
I have looked everywhere to find a solution to this problem yet no matter where I look, everybody seems to be able to fix this by just either turning off and on their phone or wiping it. But I have tried all of those and, I have also tried doing this step on a different computer and reinstalling the needed files yet to no avail.
So if anybody has a possible workaround please do share it so I can finally root my phone after many tedious hours.
Sorry for the noob question and many thanks in advanced to anyone who can help me.
Azaruc said:
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
That should be enough to make it possible to run the 1.31 RUU.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11863394&postcount=2
Ahh, thank you. I had come across that before but i just didn't think that it would help! Silly me.
Ok, is there an IRC chat for the legend somewhere, im STILL getting this error. I can't find visionary+ anywhere where im sure enough its not going to mess up my phone, and i aparently am missing the files needed however none of the guides have downloads of everything i need.
PLEASE can someone help me? im so confused nothing is making sense. I get to copying files from DxDrx but that is nonexistant, what am i missing?
Ok, i got passed this step by doing these steps
1: download visonary here
http://forum.xda-developers.com/atta...3&d=1290501865
or here
http://content.modaco.net/dropzone/com.modaco.visionaryplus.r13.apk
or you can get it off the market
Then download hack4legend here http://www.multiupload.com/I3ZALKWB6A and unzip it somewhere (this is adb and the rooting tools)
2: install and open up visonary on your phone and do a temp root on your phone.
3: open up cmd and type in the following
cd "your hack4legend path here but with out the "" "
adb shell
su
4: after you do that on your computer you should see a notification on your phone come up, it might take a little. Accept it.
5: type this into the command promt
/data/local/flash_image misc /data/local/misc1-2.img
6: run the 1.31 RUU and your good.
Hope this helps
Unreal_628 said:
Ok, i got passed this step by doing these steps
5: type this into the command promt
/data/local/flash_image misc /data/local/misc1-2.img
Click to expand...
Click to collapse
/data/local/flash_image: not found
what am i doing wrong? i had to copy the contents of hack4legend to my adb folder so i have adb, is that it? do i have to change the drectory somewhere?
Mmm, if their is a platform tools sub folder in the android sdk try putting the hack 4 legend in there and re trying. It will either have to go in there or the tools sub folder in the android sdk.
And also make sure that when you use the cd command make sure to not just go to the android ask folder but into the platform - tools/tools depending on where you put your hack, try putting it in both and using different paths. Also you might wanna try updating the adb module "android sdk platform - tools revision 3" through the sdk manager.
And as allways make sure you have usb debugging on and have your phone connected to the computer through charge mode only.
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.
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
duuude im baked said:
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
Click to expand...
Click to collapse
Thought I would share some info I found when I ran into the wifi problem on my daughter's nabi. I did some searches on the internet and the typical answer I found for solving the wifi issue was "reset the device" or "unroot and return to stock rom - flash all updates and reroot". Being a glutton for punishment, and the fact I didn't want to reset the device, I searched and searched and was able to fix my daughter's wifi without doing a reset or unroot/reroot. Before I get into it I wanted to mention that wifi failures can happen for a number of reasons so while this worked for myself, it may not work for you.
Some prerequisites:
Most importantly; you need a rooted device. If you do not have root access you will not be able to write files or access the commands to fix the issue I am about to outline.
Some knowledge of linux would be helpful, but not necessarily required.
Lets get started:
Warning! It goes without saying but I will say it anyways - you can mess up your nabi by rooting it. Some of the commands below could mess up your nabi bad. If this scares you then you probably should not proceed any further. I am not responsible for any damage you do to your nabi.
Commands are listed between ' and ' - do not use the ' when inputing the commands.
Note: The first two/three steps are not necessary but they do give you insight as to how I was able to determine my problem. If following this doesn't fix the problem for you the logcat output may give you some important info that you can google that may help you fix your particular problem.
Note: Steps 5 and on can be skipped if you have a text editor (vi or nano) on your device. If you have a text editor loaded simply edit the conf file directly.
1. You will need to run the command 'adb logcat' in a command-line window and in your appropriate directory. Adb is available as part of the android sdk but can also be found stand alone since most people do not need the sdk.
2. Try to turn on the wifi. You should see the output of your adb logcat window scroll some data. If the wifi is not attempting to turn on at all sometimes you can move between the settings options then go back to the wifi settings and move the slider. If you cannot get your wifi to turn on you can scroll the window up and attmept to find the data from when the device started up. In the output you should see lines that talk about wlan0 and probably something that says "failed" somewhere. In my case I could see where the wlan0 enabled but then a few lines down it said something about "Line: 25 failed" and "failed to parse file".
3. The file is actually a configuration file used by the wifi kernal module/driver. In my case this file had become corrupted.
4. Set adb in root mode (won't work if the device does not have root access) by running 'adb root' at the command-line. You may need to click on an "allow root permission" window on the actual device after running this command.
5. Run 'adb pull /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb shell' from command line.
b. 'su'
c. 'cat /data/misc/wifi/wpa_supplicant.conf' - copy the output from the command and paste into a text editor (see note in step 6 on why NOT to use notepad).
d. Save the file as wpa_supplicant.conf, preferrably in the same diretory as adb.
e. 'exit' twice should exit you from the adb shell and return you to your command-line. If all else failes a "ctrl-c" should drop you out of adb.
6. Use a text editor to open wpa_supplicant.conf. The file should be located int he same directory as adb. If you are using Windows I would strongly suggest you NOT use notepad. Notepad will typically change all the EOLs (End Of Line) from \n to \r\n which will really mess things up worse.
7. In the file you should see "network={" entries. There maybe one entry, there maybe many entries. You can remove all lines between "network={" and "}" including the latter themselves. If you see your 'home' network listed you can leave it as the only entry and make sure its priority is set to 1 but it maybe better to remove it as well just in case it contains part of the corrupted data.
8. Save the file.
9. Do 'adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb push wpa_supplicant.conf /sdcard/wpa_supplicant.conf' from command-line.
b. Run 'adb shell'
c. 'su'
d. 'dd if=/sdcard/wpa_supplicant.conf of=/data/misc/wifi/wpa_supplicant.conf'
e. Do 'exit' twice to exit the adb shell. If all else fails then a "ctrl-c" should drop you ot of adb.
10. If the wpa_supplicant file was corrupted then the wifi should now be able to enable and you should now be able to connect to a network.
I hope this is helpful to at least a few people.
Today, I finally have found where to post for newbies, so I post, thought 4 hours ago I posted on androidforums.
Here is very difficult to operate with this site, and to use this site for with android devices is quite impossible. Only in windows, and not every comfortable. Anyway, I see, that is the first university on the net
Click to expand...
Click to collapse
.
just enter in google: tablet h007 and you shall see the specification, cos I can`t post link now. If anyone has the backup for this model, it shall be about 560 MB. Let me know, not to trouble anyone.
The tablet was rooted by kingoroot, but as you know or not, kingoroot, offers root acces, as the 1 service started, when the device is on, but it does not provide general full root settings, as for example when we are in the recovery menu.
I used some kernel tuner application, and I did not make any backups at all. I edited the file with this application, called build.prop, where I change the attribute of user for superuser. In that way, I though, I could get permissions of full root, I did that, because, I could not see my system partition generally, only from total commander, I could see and do whatever I want. After, I rebooted, and the problem started.
I attach here, my device specifications: Which I watched, while I could use the device:
Android system recovery 3e with sw version: alps.kk1.mp1.v2.11. It is on the photo though but with the different name.
MS board: d95b
Mt6582 (Chip)
All the rest is on the photo
foto.lovestudio.biz/image.uploads/30-07-2015/original-9ec17e355b096718359535e5af42aa4c.png
I have windows vista 32bit 2 service pack.
MTKdroidTools, the application I tried, 4 different versions, 1, last, and 2 in the years, when my phone was produced. It does not read my phone, saying, it is not present. Though all 4 kind of drivers are installed, even adb device driver is installed and all is perfect, all is connected.
The only thing I can use in this mtkdroidtools is adb terminal. I enter there the following command: adv devices, which shows some number of device connected with sideload.
Something like that:
List of devices attached
01234565ABCDEFG recovery
but at the place of recovery, I have
List of devices attached
01234565ABCDEFG sideload
Then, after reading stack-exchange site, I understand, that now I can enter the system partition to get my build.prop file, to change superuser for user as it was before and to return in back to the device, and get my phone worked. But I can`t do that. Cos as I stated before, the device is rooted only by kingoroot, and I works only as the 1 st. service inside android operating system, but not in recovery menu.
So I cant use the following command to get it right. Cos when I enter any of them, but first of all, I enter: adb usb - it says: error: closed
You can then copy the file off the phone:
adb pull /system/build.prop c:\build.prop
You can now edit it in any text editor (recommend Notepad++ because it will preserve the Unix style line endings,) and then copy it back to the phone:
adb push c:\build.prop /system/build.prop
To work with adb terminal, of course I am in the recovery menu and I enter inside ADB SIdeload Application.
I know how to deal as you see, with this problem, but I can`t get to the file, to the system partition in the whole, cos as I understand, the phone is not rooted.
So guys, let`s see what happens next, I am looking forward to your suggestions.
lovestudio said:
.
just enter in google: tablet h007 and you shall see the specification, cos I can`t post link now. If anyone has the backup for this model, it shall be about 560 MB. Let me know, not to trouble anyone.
The tablet was rooted by kingoroot, but as you know or not, kingoroot, offers root acces, as the 1 service started, when the device is on, but it does not provide general full root settings, as for example when we are in the recovery menu.
I used some kernel tuner application, and I did not make any backups at all. I edited the file with this application, called build.prop, where I change the attribute of user for superuser. In that way, I though, I could get permissions of full root, I did that, because, I could not see my system partition generally, only from total commander, I could see and do whatever I want. After, I rebooted, and the problem started.
I attach here, my device specifications: Which I watched, while I could use the device:
Android system recovery 3e with sw version: alps.kk1.mp1.v2.11. It is on the photo though but with the different name.
MS board: d95b
Mt6582 (Chip)
All the rest is on the photo
foto.lovestudio.biz/image.uploads/30-07-2015/original-9ec17e355b096718359535e5af42aa4c.png
I have windows vista 32bit 2 service pack.
MTKdroidTools, the application I tried, 4 different versions, 1, last, and 2 in the years, when my phone was produced. It does not read my phone, saying, it is not present. Though all 4 kind of drivers are installed, even adb device driver is installed and all is perfect, all is connected.
The only thing I can use in this mtkdroidtools is adb terminal. I enter there the following command: adv devices, which shows some number of device connected with sideload.
Something like that:
List of devices attached
01234565ABCDEFG recovery
but at the place of recovery, I have
List of devices attached
01234565ABCDEFG sideload
Then, after reading stack-exchange site, I understand, that now I can enter the system partition to get my build.prop file, to change superuser for user as it was before and to return in back to the device, and get my phone worked. But I can`t do that. Cos as I stated before, the device is rooted only by kingoroot, and I works only as the 1 st. service inside android operating system, but not in recovery menu.
So I cant use the following command to get it right. Cos when I enter any of them, but first of all, I enter: adb usb - it says: error: closed
You can then copy the file off the phone:
adb pull /system/build.prop c:\build.prop
You can now edit it in any text editor (recommend Notepad++ because it will preserve the Unix style line endings,) and then copy it back to the phone:
adb push c:\build.prop /system/build.prop
To work with adb terminal, of course I am in the recovery menu and I enter inside ADB SIdeload Application.
I know how to deal as you see, with this problem, but I can`t get to the file, to the system partition in the whole, cos as I understand, the phone is not rooted.
So guys, let`s see what happens next, I am looking forward to your suggestions.
Click to expand...
Click to collapse
I am sorry, so no one knows, on 3 sites, no one knows. let me know, then I shall not check every hour this post. I t`s better to know, that nothing possible, that believe that smth. is possible. thanks.
Per this issue, and specifically this comment, I'm trying to grant the BATTERY_STATS permission to GSam Battery Monitor. I've tried the adb command "pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS" but can't get it to work. I've also tried "pm grant com.gsamlabs.bbm android.Manifest.permission.BATTERY_STATS" but the results are the same. Doing it through ConnectBot gives me the following error:
Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 10338 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
Doing it through adb gives me this:
Bad argument: java.lang.IllegalArgumentException: Unknown package: com.gsamlabs.bbm
This is on a stock Moto Z Play, 7.1.1
kernel:
3.18.31-perf-g757c8d9
[email protected] #1
Build number NPN26.118-22
Are you running the pro version? Then it needs to be com.gsamlabs.bbm.pro
The error is because it can't find a package named com.gsamlabs.bbm, so I would investigate why that's occurring. Either there's a typo (I don't see one) or that's not the correct package name.
ConnectBot won't work because ConnectBot doesn't have superuser permissions. Unless your device is rooted it'll have to be done through adb or using a PC-side program which effectively does the same thing.
Thanks! I think that was it, as adding .pro to the end didn't give an error. But it didn't actually say it was successful, either. It just spit out all the adb usage info like if you just type "adb" with no parameters. Any idea how I know if it worked?
vertigo_2_20 said:
Thanks! I think that was it, as adding .pro to the end didn't give an error. But it didn't actually say it was successful, either. It just spit out all the adb usage info like if you just type "adb" with no parameters. Any idea how I know if it worked?
Click to expand...
Click to collapse
Do the advanced stats in BBM work now? Also, are you on the paid version of BBM? That's the pro version, iirc.
You are typing "adb -d shell pm grant com.gsamlabs.bbm.pro android.permission.BATTERY_STATS", right?
Got busy with other stuff and just now got back to this, but I got it working. The reason I got the output I did before was because I was typing an invalid command, since pm grant isn't one of the commands of adb.exe. I had to type adb shell THEN type the command, and then it worked (and I just noticed you said that, I must have overlooked that when I looked at it before since I was busy). Also, for anyone that might come across this trying to do this, GSam didn't automatically recognize that this was done. I had to go through the steps of having it show me how to do it and at the end of that it worked. One final note, I had to update to the latest SDK for it to work, the version I was using was too old. Thanks again for the help apraetor!
Yea, I had a feeling after re-reading your original post that you were missing the "adb -d shell" portion, glad it's working.
vertigo_2_20 said:
Got busy with other stuff and just now got back to this, but I got it working. The reason I got the output I did before was because I was typing an invalid command, since pm grant isn't one of the commands of adb.exe. I had to type adb shell THEN type the command, and then it worked (and I just noticed you said that, I must have overlooked that when I looked at it before since I was busy). Also, for anyone that might come across this trying to do this, GSam didn't automatically recognize that this was done. I had to go through the steps of having it show me how to do it and at the end of that it worked. One final note, I had to update to the latest SDK for it to work, the version I was using was too old. Thanks again for the help apraetor!
Click to expand...
Click to collapse