Unroot Droid 3 without computer? - Motorola Droid 3

Ok, so I haven't figured out the cord thing yet (phone won't connect to any computer using the stock cord, I can get it to show its charging...thats it!), so I am wondering if there is anyway to unroot without a computer? PLEASE HELP!!! I AM GETTING DESPERATE!!!

ajgates92 said:
Ok, so I haven't figured out the cord thing yet (phone won't connect to any computer using the stock cord, I can get it to show its charging...thats it!), so I am wondering if there is anyway to unroot without a computer? PLEASE HELP!!! I AM GETTING DESPERATE!!!
Click to expand...
Click to collapse
Open market and grab "terminal emulator", once you have it open it up and follow the steps as root (first thing you type into the terminal emulator is "su")
1./ remount /system to rw "busybox mount -o remount,rw /system
2./ erase root files "rm /system/xbin/su" "rm /system/bin/su" "rm /system/app/Superuser.apk" "rm /system/xbin/busybox"
3./ remount system ro and reboot "busybox mount -o remount,ro /system" "reboot"
these paths are for root w/zergs but they might be the same for Petes etc. This will clear all files and symlinks that were created when you rooted your device.

I am trying this now, thanks for the quick reply. Will let you know how it works!
Edit: Can you please put the exact code string I should enter into the Terminal? Thank you
Double Edit: I'm an idiot! I read your post wrong, I got it right this time and it worked!!! THANK YOU SO MUCH!!!!!

Droid 3 stock cables suck f(2 d3s and both cables died).. be sure to also check with no stovk cable...
Enviado desde mi DROID3 usando Tapatalk

ajgates92 said:
I am trying this now, thanks for the quick reply. Will let you know how it works!
Edit: Can you please put the exact code string I should enter into the Terminal? Thank you
Double Edit: I'm an idiot! I read your post wrong, I got it right this time and it worked!!! THANK YOU SO MUCH!!!!!
Click to expand...
Click to collapse
No worries, I'm glad you got it working. You're not an idiot, I'm a cryptic poster

So terminal app comes with superuser and busybox?

poetryrocksalot said:
So terminal app comes with superuser and busybox?
Click to expand...
Click to collapse
No, terminal app usually comes on custom roms but stock rooted users will have to download it for free off the market.

Related

I need help about rooting

Hello everyone.
First off all i hope this post is in the right section.
Let me get this out off the way first:
Im not good at english, and im not good at cmd files and so on.
But! i can succecsfully root my phone and get the # in cmd.
The reason im rooting is becouse i want the market patch so i can see all apps.
Here is my questions:
1. Whenever i try to adb push vending......
It says "the file is read-only" i cheked its not read only
So how do i fix that?
2. In the guide to root the phone he says:
"You can do anything then! Look at /system, /data, etc etc. You're broken free, my friend"
Where can i see the /system and so on? he says look at, but where can i look at it? how can i like acces the folders?.
So on the easy way, i search a way to install the market patch.
Thank you everyone
Bump, i really hope someone will help
Anyone? please?
When you have root, you need to mount r/w partition:
- adb push tattoo-hack.ko ./data/local/bin/tattoo-hack.ko (if you haven't did it before)
- adb shell
$
- su
#
- # insmod /data/local/bin/tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
And now you have mounted in r/w, so:
- adb push Vending-Tattoo-patched.apk /system/app/Vending.apk
p.s. ah...you can access system folders with Root Explore (it needs root)
I never had to mount anything. I did the latest root hack in the sticky at top of forum and then i installed the full market apk. Worked a treat.
ephumuris said:
I never had to mount anything. I did the latest root hack in the sticky at top of forum and then i installed the full market apk. Worked a treat.
Click to expand...
Click to collapse
I'm happy for you, but someone like me (and mafiapanda in that case) did old manual root.
Ty
Thank you im going to try it out now, thanks
Okay, after i get the
#
then i did what you said.
i get it again
# adb push vending.....
"adb not found"
Ehhmm can you help me there?
Everyting was succesfull except pushing it.
mafiapanda said:
Okay, after i get the
#
then i did what you said.
i get it again
# adb push vending.....
"adb not found"
Ehhmm can you help me there?
Everyting was succesfull except pushing it.
Click to expand...
Click to collapse
Of course, it's normal
You have to write "adb push vending....." non in "adb shell" but in "adb" (open another cmd and as for example "cd c:\android\tools", then "adb push" etc.)
Stupid me
Am so thankfull to you guys, you really helped me alot Thank you really much!
Okay, now i get "permisson denied" when im trying to "adb push vending..."
I opened a new CMD and typed cd c android tools, i just get permission denied.
Can anyone help me about that? Thank you guys so far
mafiapanda said:
Okay, now i get "permisson denied" when im trying to "adb push vending..."
I opened a new CMD and typed cd c android tools, i just get permission denied.
Can anyone help me about that? Thank you guys so far
Click to expand...
Click to collapse
Have you opened new cmd closing the other or not?
You don't have to close the first cmd.
Try. If it doesn't work, probably there are some problems with the root procedure, in that case try that solution: Root in 1 click. It contains: root, boot.img, market (also recovery if you choose it).
Yea, i have tryed root in 1 click, but does it really include market?
Root in 1 click gives me the same error ?
Okay maybe this is alot to ask for but is there anyone out there that can make a video of it all from rooting to push market. i would be so thankfull.
And its not just for me, it would help alot out there. im so thank full
Damn, now it says "read only file system" again.
Can anyone post a detalied how-to Thank you really much.
Im going to bed now, cheking this post tommorow.
Btw, i would love to have talk with someone on msn, steam or mail.
Am from denmark if it matters.
THANK YOU
mafiapanda said:
Damn, now it says "read only file system" again.
THANK YOU
Click to expand...
Click to collapse
You have to repeate that every time you reboot:
- adb shell
$
- su
#
- # insmod /data/local/bin/tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
And then you have mounted in r/w:
- adb push Vending-Tattoo-patched.apk /system/app/Vending.apk
(one time)
Okay I Will try that when I get home. Can I use the 2. 1 market I mean so I can have all the 500 apps or is it only for 2 1 firmware modded phones?
mafiapanda said:
Okay I Will try that when I get home. Can I use the 2. 1 market I mean so I can have all the 500 apps or is it only for 2 1 firmware modded phones?
Click to expand...
Click to collapse
Use v2 patch, not 2.1. It has worked for me.
YES! I cant ****ing believe it!! I succed !! im am so happy
Thank you very very very much 1000 times.
YES MAN im so happy now.
Maybe i should at a guide to this forum? i dont know if anyone needs it but..
Okay last last question, when i search for "video" i see 300 results which am very happy for but, on the picture he had 500 how can i get 500 ?
mafiapanda said:
YES! I cant ****ing believe it!! I succed !! im am so happy
Thank you very very very much 1000 times.
YES MAN im so happy now.
Maybe i should at a guide to this forum? i dont know if anyone needs it but..
Okay last last question, when i search for "video" i see 300 results which am very happy for but, on the picture he had 500 how can i get 500 ?
Click to expand...
Click to collapse
You're welcome
300 rather than 500? I'll try..

help with froyo 2.2.13 install

ok, so i tried to get help in the actual froyo 2.2.13 install thread but i'm not getting an answer.
i downloaded, installed, and it said it was successful.. i rebooted, went into the settings to see if it changed, and it still said 2.2.9. i tried to do it again and now my phone will not reboot into recovery using droid x bootstrap or rom manager... won't even go into it if i do it manually... i tried to uninstall bootstrap and rom manager and reinstalling, no luck. please help.
brandon2x said:
ok, so i tried to get help in the actual froyo 2.2.13 install thread but i'm not getting an answer.
i downloaded, installed, and it said it was successful.. i rebooted, went into the settings to see if it changed, and it still said 2.2.9. i tried to do it again and now my phone will not reboot into recovery using droid x bootstrap or rom manager... won't even go into it if i do it manually... i tried to uninstall bootstrap and rom manager and reinstalling, no luck. please help.
Click to expand...
Click to collapse
Try these comands from :
AllDroid Public Board»Motorola»Droid X Forums»Droid X Rooting»How to get 2.2, Rooted, on your Droid X
under:
If you have /system/xbin/su and /system/app/Superuser.apk, but cannot use "Superuser" (no prompts from Superuser app, "permission denied" when you try to run "su"), just do the following:
Run "adb shell"
Run "/system/xbin/su"
Watch your screen for Superuser app to prompt for permission and click "allow"
Run "mount -o remount,rw /dev/block/system /system"
Run "cp /system/xbin/su /system/bin/su"
Run "chmod 4755 /system/bin/su"
Open the SuperUser application on the phone (app launcher) and make sure that "superuser" isn't listed and denied. If so, "forget it" and return to step 2. If you can't find SuperUser, it's not installed and you should download from this posts attachments and "adb install Superuser.apk"
[optional] Run "mount -o remount,ro /dev/block/system /system"
This should help you get your su working again.
not sure on your process so if you still do not have the .13 I would go back to your process and see what you are missing. I rebooted into recovery from bootstrap when I installed mine. Then I had to do the above commands to get my su back.
If you still don't have it, try the FULL instructions from here:
MDW Presents: Droid X 2.3.13 - The Froyo Upgrade
read through it and see if #5 from step 2 pertains to you.
The biggest thing to remember is to mount before you select the file to load on your sd card.
This thread:
Motorola Droid 2Droid 2 Android DevelopmentHow to root the Droid 2
will also be helpful regarding root if you have further questions.
Hope this helps.
My su is working fine. Nothing is being denied when I open it. Just cannot get to recovery with any option... im lost...
Sent from my DROIDX using XDA App
Maybe just double check through adb shell even if you are not having su issues?
Run "adb shell"
Run "/system/xbin/su"
Watch your screen for Superuser app to prompt for permission and click "allow" (I never saw any request)
Run "mount -o remount,rw /dev/block/system /system"
Run "cp /system/xbin/su /system/bin/su"
Run "chmod 4755 /system/bin/su"
I had similar issues of nothing being denied after a successful install and had to do the su commands. It helped me to reboot into recovery afterwards.
Sent from my DROIDX, Froyo FTW. Obsidian?
Ok im still learning.... how do I "run adb shell" and do these commands you're telling me...
Sent from my DROIDX using XDA App
brandon2x said:
Ok im still learning.... how do I "run adb shell" and do these commands you're telling me...
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I saw your post in the other thread. The best thing you can do is go through the links I gave you. Start with the root thread and click the more directions link in it. read through the processes and make sure you download all files and also understand what sbf is. Once you have all of the tools to do root and load whatever leak or rom you want you should be set. Understanding what is going on is key. This is a decision you are making to alter your phone for your benefit. Take the time to download SDK and whatever else is needed for your computer. Become familiar with what shell is and how to get there as well as explore within it. If you can get shell down and how to access your su and run commands, you should know enough to start. There are many things you need to research in order to be confident in what you are doing. I am sure you will not have a problem, just putting the time in to figure out everything is key. This is what I had to do.
I think that this is the best advice I can give you. None of us can know exactly what you are doing so you need to know the processes and choose which one is going to work for your circumstance. Good luck and if you have anymore problems I am sure all of us on xda can figure out a solution for you.
ok, finally, with a little help i got my phone rerooted and back to normal. learned a lot in the process too. thanks to all...

OLYFR_U4_1.5.2 Market Fix

Here is a simple fix for the market issues between stock and 1.5.2 - it assumes you have flashed the 1.5.2 sbf, and also re-rooted your device.
adb shell (or open a terminal on your phone)
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
reboot
I have been running with this most of the day with no issues noticed..
-G
how funny i JUST discovered this earlier today was going to post it on the forums. great minds think alike . my n64oid is back!
Funny, I just told someone else how to do this this morning. I'm surprised this hasn't come up sooner. I've been using this since the sbf has been released with no problems, guess I should have posted this solution sooner my b :-(
Sent from my MB860 using Tapatalk
Anyway to do this through terminal?
Sent from my MB860 using XDA App
Same commands without the first adb shell..
How do I enable RW to system?
Trying to do the market fix script but get RO error on write to /system.
from a command prompt in windows/linux:
you: adb shell
reply: $
you: su
(accept prompt on device, make sure it's unlocked and @ homescreen or it might not pop up)
reply: #
you: mount -o rw,remount /dev/block/mmcblk0p12 /system
reply: (copies it back)
you: sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
reply:
you: reboot
What are the "market issues?"
Da_G said:
from a command prompt in windows/linux:
you: adb shell
reply: $
you: su
(accept prompt on device, make sure it's unlocked and @ homescreen or it might not pop up)
reply: #
you: mount -o rw,remount /dev/block/mmcblk0p12 /system
reply: (copies it back)
you: sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
reply:
you: reboot
Click to expand...
Click to collapse
Thanks,
I made some assumptions that people would know the prerequisites
I edited the original.
-G
relaxed said:
What are the "market issues?"
Click to expand...
Click to collapse
Well, I had several apps I paid for that I could not load. I had the same issues with my G-Tablet until I loaded my N1 build id in the same file a while back..
-G
Well I did it with the first method and it works fine except the market doesn't update to the new market.
ghost_o said:
Thanks,
I made some assumptions that people would know the prerequisites
I edited the original.
-G
Click to expand...
Click to collapse
Sent from my MB860 using Tapatalk
Fixter said:
Well I did it with the first method and it works fine except the market doesn't update to the new market.
Click to expand...
Click to collapse
First method?
The sed command is the only command I have posted.. You could use 'vi' directly on the device as well.. My market updated to the new version just fine after I made the change. (albeit I used vi on the device through adb shell). I just posted the sed string for people not familiar with unix, or who might want to script it..
ghost_o said:
First method?
The sed command is the only command I have posted.. You could use 'vi' directly on the device as well.. My market updated to the new version just fine after I made the change. (albeit I used vi on the device through adb shell). I just posted the sed string for people not familiar with unix, or who might want to script it..
Click to expand...
Click to collapse
I meant to say the first method where you only posted
Adb shell
su
sed
reboot.
Nothing about remounting, like what Da_G posted. Might have something to do with it?
Fixter said:
I meant to say the first method where you only posted
Adb shell
su
sed
reboot.
Nothing about remounting, like what Da_G posted. Might have something to do with it?
Click to expand...
Click to collapse
Ahhh, you must have already run something that re-mounted it rw for you. It would have failed otherwise... You can always try to put it back, and let the market update, and then change it again to get the apps back. I seriously doubt that is what is keeping your market from updating though.
ghost_o said:
Ahhh, you must have already run something that re-mounted it rw for you. It would have failed otherwise... You can always try to put it back, and let the market update, and then change it again to get the apps back. I seriously doubt that is what is keeping your market from updating though.
Click to expand...
Click to collapse
Thats exactly what I'm thinking. That doesn't have to do anything with the Market updating... Stupid market... -kicks-
Fixter said:
Thats exactly what I'm thinking. That doesn't have to do anything with the Market updating... Stupid market... -kicks-
Click to expand...
Click to collapse
should be able to reverse by switching up this part:
sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
to:
sed -i 's!OLYFR_U4_1.2.6/1296900353!OLYFR_U4_1.5.2/1298398352!' /system/build.prop
then have the market update without a problem and then reapply the fix, though I'm sure you thought of this already XD
Djazin said:
should be able to reverse by switching up this part:
sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
to:
sed -i 's!OLYFR_U4_1.2.6/1296900353!OLYFR_U4_1.5.2/1298398352!' /system/build.prop
then have the market update without a problem and then reapply the fix, though I'm sure you thought of this already XD
Click to expand...
Click to collapse
Yeah I tried that with no success... I wonder if it was the Gingerblur.
Works great. I was wondering where some of my apps had ran off to!
sed: write error
Hey, I was wondering if anyone here could help me.
I've reflashed from GingerBLUR 6.5, and can't seem to apply the market fix. I keep getting a write error when I apply the sed command.
You have to be rooted, and remount /system as read/write prior. The mount command right before the serd command is needed. Also, make sure your "su" command is successful. If not, the rest will not work..

Root instructions...

Originally posted by Stetsonaw at androidforums...
Please be aware that I did not write these instructions. I only posted them. Stetsonaw wrote these instructions. While comfortable in ADB and have rooted my phone many times in testing as well as rolled back the versions etc... I have no more insight into how or why it is not working for you. If you followed the directions exactly on a version 4 phone, this should work no problem.
Haxcid
Links to the necessary files are listed at the bottom.
Remember, I am not at fault if you brick your phone, now, proceed.
Connect your phone in charge only mode to install the LG Bootstrapper and drivers, or grab the LG Universal Drivers.
Change your USB Mode to Internet Connection
Go into Settings/Applications/Development and ensure USB Debugging is turned on
If all goes according to plan, you should see the ADB Ladybug icon in your notification bar
I updated the Rootzwiki page with the same info found below.
Busybox actually comes installed by LG on the Revo, how awesome is that??
Download the rageagainstthecage binary
Download the SU binary
Move these files to the same directory your adb.exe is in.
Code:
The > and # characters below illustrate the prompt
you should have, if you have the $ when you go into adb shell,
exit out and type 'adb usb' then go back into adb shell and
you should see the #
Open Command prompt (either use the Windows Key+R and type cmd or start/run, then type cmd)
32-bit users: >cd c:\program files\android\android-sdk\platform-tools
64-bit users: >cd c:\program files (x86)\android\android-sdk\platform-tools
Or >cd (whatever directory adb is in)
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
>adb shell (If this gives you a $ prompt instead of a # prompt, type 'su', if that fails, 'exit', 'adb usb' like above.)
#mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
#busybox cp /data/local/temp/su /system/bin/su
#chmod 6755 /system/bin/su
Verify the file is in place w/correct permissions
#cd /system/bin
#ls -l *su
After the ls command you should see the following returned by the system:
-rwsr-sr-x root root 26248 2011-05-29 01:09 su
At this point, you may way to remove the files you put in /data/local/temp (optional):
#rm /data/local/temp/su
#rm /data/local/temp/rage
continue with commands
#reboot
Download and install SuperUser from the Market
Thanks Zennmaster, _mrbirdman_ for finding the linux routes and birdman for helping me out, and droidx8971 for helping me find all the information possible!
http://wikifilez.com/Root Files/revolution/rageagainstthecage-arm5.bin
http://wikifilez.com/Root Files/revolution/su
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe
Just a note for some. The rageagainstthecage bin file may be detected as a virus/trojan. It is not. You may want to disable your antivirus before downloading the .bin file.
I run avira on my desktop and it caught the file as a virus everytime I downloaded it and then deleted it. Avast on my laptop however did not.
Root is simple if you follow the instructions. You need to make sure that adb recognizes your device. Takes 5 minutes to complete, took me longer to install adb again and update it.
Any reason to not use the one click method? Seems to be working
bwhxeon said:
Any reason to not use the one click method? Seems to be working
Click to expand...
Click to collapse
No idea. I have not used the one click. Create a thread for it. I posted what I know which is adb.
Successfully Rooted
with RootzWiki instructions for Windows, needed the remount and busybox lines to overcome the permission denied when pushing su.
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
MXFrodo195 said:
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
Click to expand...
Click to collapse
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
Oh ya I know, I just always keep a stock one, on the Inc if you factory reset from an AOSP rom, you'd bootloop, so you had to make sure you were on a Sense 1.0 or stock rom(from my experience), so I was just making sure it was no big deal to go back.
Any idea when we will have cw on this?
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
I tried the factory reset. I am still rooted.
navycow said:
I tried the factory reset. I am still rooted.
Click to expand...
Click to collapse
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
MXFrodo195 said:
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
If you have to return your device, simply remove the superuser app, after you unfreeze anything you may have frozen then factory reset. They honestly will never know it was rooted. The only way now that you can really tell is the super user app from market.
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Thank you for confirming this. My revolution just came in the mail today!
Thanks for posting this here for me Haxcid!
Sent from 1885
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Cool thanks for checking. Any benefits for ADB over S1C? Can't wait to finally root and freeze half these apps. I think we need a few more twitters to praise koush for a recovery on this beast.
Sent from my VS910 4G using XDA Premium App
Is there recovery for this now? Did I miss something?
stetsonaw said:
Is there recovery for this now? Did I miss something?
Click to expand...
Click to collapse
No No, I was saying we need to praise Koush's good work so he will make one faster .
And Stetsonaw, any idea if I root through ADB, can I unroot with S1C, since it uses the same idea.
S1C for whatever reason will not run(tried three computers, a XP, Vista, and Win7 lol), it keeps freezing at the same spot, everytime.
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
stetsonaw said:
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
Click to expand...
Click to collapse
Hmmm, ya now my computer for whatever reason won't open up ADB through command. This is getting irritating lol. Should be nice and simple, but it just won't go through. If I downloaded the SDK Manager like 4 months ago, it shouldn't matter, correct?
make sure you change directory to wherever your adb.exe is located... as in:
Code:
cd C:\Program Files\Android\android-sdk-windows\platform-tools

HELP! Su was in the folder but device not found!

I followed the instructions exactly but now device not found and I folowed the video exactly, su is in the folder (((
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
abd reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
The adverts are back on the screen, what do I do please
Its nearly 2am in the morning
device is found now, what point do I pick up the command prompts up at?
please
Rovers82517 said:
please
Click to expand...
Click to collapse
ah, man, I'm seriously lost, it fails everytime with these 2 commands,
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
the su file is definately in the platform-tools folder :/
Rovers82517 said:
ah, man, I'm seriously lost, it fails everytime with these 2 commands,
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
the su file is definately in the platform-tools folder :/
Click to expand...
Click to collapse
If your drivers are installed correctly now, use the root tool in development section. Then there are no mistakes. If you insist on the manual method though, you need to put the su file and superuser.apk in your folder titled carol and Start over completely
onemeila said:
If your drivers are installed correctly now, use the root tool in development section. Then there are no mistakes. If you insist on the manual method though, you need to put the su file and superuser.apk in your folder titled carol and Start over completely
Click to expand...
Click to collapse
the files are in there, I've checked and double checked.
when I can get it to see the device again the command prompt has a # instead of a $
I can't afford to brick this thing, I don't know of any other methods, can you tell me what you mean or post the link?
It's gone 2am now I could do with even a little sleep tonight
Thank you for replying
ah, my bad, I know what tool you mean cheers dude
Rovers82517 said:
the files are in there, I've checked and double checked.
when I can get it to see the device again the command prompt has a # instead of a $
I can't afford to brick this thing, I don't know of any other methods, can you tell me what you mean or post the link?
It's gone 2am now I could do with even a little sleep tonight
Thank you for replying
ah, my bad, I know what tool you mean cheers dude
Click to expand...
Click to collapse
No problem, sometimes it just takes a lot of banging your head.
still no luck
I've copied both files to 'carol' as well as platform-tools, what have I done wrong?
Fixed but I'm not sure how
It repeatedly said file not found but in the end I decided to skip to step 4 on QemuRoot and it had worked lol very strange
Think I'll leave it a while before I attempt custom roms lol
Thanks for your help peeps
Rovers82517 said:
It repeatedly said file not found but in the end I decided to skip to step 4 on QemuRoot and it had worked lol very strange
Think I'll leave it a while before I attempt custom roms lol
Thanks for your help peeps
Click to expand...
Click to collapse
From my personal experience is best way how to root kindle fire by qemu (development part of forum) its quite easy... to solve problem if your device isn't found I had to create folder .android in my “documents“ like it is when you will instantly sdk
You have to create it via command line... mkdir .android
Create there required file how it is described in qemu thread. Reinstal kindle adb drivers and try qemu once more.. that worked for me like a charm.
Tomorrow when I will be on PC I will post step by step guide
Kerbik

Categories

Resources