Related
I love my phone to death, but the few things I have left I want to do/use on my phone require busybox. I could just flash a new rom, but I like the stock rom as it is, and don't want to have to install the 150 apps i have all over again (and am too poor for titanium backup donate).
So i just want to install busybox on my phone. I've been googling, and reading, and googling some more, but I still can't seem to get past the first few steps. I am new to ADB and really don't know what I am doing, but I tend to be good at following directions.
Right now im using this guide:
http://www.gadgetsdna.com/busybox-installation-steps-on-jailbroken-android-device/683/
I get to:
adb push busybox /data/local
and cmd throws "adb: permission denied"
I have searched to no avail, and have tried everything my limited linux command experience has to try. I'm down to begging yall for some help.
Is your phone root?
One click root. Didn't know if that would hurt anything. I have already installed CM6 and gone back to stock, so i figured installing busybox would be no problem.
I used the universal androot app and it installed busybox for me. Piece of cake.
You could install Titanium Backup and then click "Problems?"
why don't u just get it from the Market?
Hey all, just purchased my Milestone 1 from my local provider nTelos. They are CDMA carrier located in the Shenandoah Valley of Virginia. Now, everything has been working fine for almost a week and a half now, but yesterday upon trying to update my Busybox install (from 1.14.x to 1.17.x) it completely killed my root. What I mean by that is no Barnacle, no Titanium Backup, no SuperUser privileges!
Even from the Terminal Emulator, if I try to su into the system after "rerooting" with Universal Androot, it says that I need to be suid for it to work.
Upon typing anything else, suid, root, suid su, etc. it says permission denied.
ADB is a hit or miss because I can obtain shell root using SUPEROneClick for a short time in order to push and pull things from the device. Thinking this would be a cure all, I tried rooting with SOC and found out that it cannot do this because it cannot find the mount path. Digging around further, I find out that my Android can't access /etc/fstab because it doesn't exist on Android devices do to no media drives.
So, is there anyone out there that can help me in any way possible? I've been digging online for over 24 hours for this and have yet to find anything helpful/useful for my situation. I'm thinking if I can reset the "su" permissions or remove Busybox and reinstall, it could fix things? Idk, any help is appreciated!
I reinstalled the GOT 2.2.1 ROM and also could not get BusyBox to work. Even though the phone is rooted, apparently, BusyBox cannot remount.
Anyway, I'm no longer using Titanium. So long as you have real root access, there are plenty of other back up apps that you can use (Root Explorer, Super Manager, etc.).
Try z4root by RyanZA for rooting your phone. I'm sick of BusyBox and its fussiness.
Found out that after flashing with the sbf file for my build A854, I was unable to join the nTelos network. Had to get a new phone, for free of.course
Sent from the Milestone
I claim no credit for this but after the 893 OTA you wont have root and you will have to go this way to get it back.
Original post I robbed this from [HERE]
You will need adb to do this. You can get the download here depending on your operating system. ADB
Download the follow file: it contains the exploit, su, Superuser
Download exploit -->Exploit.zip
1) Unzip contents of folder to your Desktop
2) open a command terminal and navigate to the folder (cd Desktop/Exploit)
3) type the following commands
---> adb push zerg /data/local
---> adb push su /data/local
---> adb push Superuser.apk /data/local
---> adb shell
---> cd /data/local
---> chmod 777 zerg
---> ./zerg
4) Wait for the root to be gained
5) type the following commands
---> adb shell (only type this if you are no longer in [email protected])
---> mount -o rw,remount /dev/null /system
---> cat /data/local/su > /system/bin/su
---> cat /data/local/Superuser.apk > /system/app/Superuser.apk
---> chmod 4755 /system/bin/su
---> chmod 4755 /system/app/Superuser.apk
---> reboot
This is from P3Droid.
Click to expand...
Click to collapse
Worked like a charm. Thanks!
want to do this for my brother, you just connect the phone to the computer with usb debugging mode enabled right?
Fyi if you correctly root and forever root prior to the ota you will retain root. The update does not remove root if it was forever rooted.
Sent from my DROID BIONIC using XDA App
I used this method on a used Bionic I bought that has 5.7.893. It worked perfectly.
Why do you guys make it so difficult? All you need to do is use R3L3AS3DRoot to restore, root, and forever root your Bionic. And, POW! You will have a rooted Bionic once again, without D/L unnecessary software and typing commands. Props to DHacker.
charlie310 said:
Why do you guys make it so difficult? All you need to do is use R3L3AS3DRoot to restore, root, and forever root your Bionic. And, POW! You will have a rooted Bionic once again, without D/L unnecessary software and typing commands. Props to DHacker.
Click to expand...
Click to collapse
Because R3L3AS3DRoot restores a 886 system and not an 893 system, which is the reason you would "D/L unnecessary software."
So, sure you'll be rooted with an 886 system which isn't current.
you forgot last step....then update and youll still have forever root
I restored and forever rooted my bionic, then did OTA, and still have root. I was on rooted stock previously, but restored because I wasn't able to get or pull the OTA update due to "error try again later".
Sent from my DROID BIONIC using Tapatalk
Terror_1 said:
Because R3L3AS3DRoot restores a 886 system and not an 893 system, which is the reason you would "D/L unnecessary software."
So, sure you'll be rooted with an 886 system which isn't current.
Click to expand...
Click to collapse
Let's think about this logically:
D/L and unzip R3L3AS3DRoot and use 3 clicks to restore/forever root your phone, then D/L the update using a 3 clicks.
Or, D/L and install ADB, D/L and install Java SE, and D/L & unzip the Exploit Zip and type in 15 command lines to root your phone.
It's pretty obvious what is considered easier and requires less unnecessary software.
BTW, if you are flashing a ROM, then option 1 is always the best way to go since you don't have to D/L the OTA update since most ROMs have the update built in (and you already have the updated radio).
getting replacement bionic for radio issues tomorrow hopefully. will i have to use this most likely or will it unrootable? any info would be great thanks!
charlie310 said:
D/L and unzip R3L3AS3DRoot and use 3 clicks to restore/forever root your phone, then D/L the update using a 3 clicks.
It's pretty obvious what is considered easier and requires less unnecessary software.
Click to expand...
Click to collapse
You forget that some of us already have all the prerequisites. I personally can't say if your method works or not. It failed several times for me, so I gave up and zerg worked.
luke1333 said:
getting replacement bionic for radio issues tomorrow hopefully. will i have to use this most likely or will it unrootable? any info would be great thanks!
Click to expand...
Click to collapse
I am partial to doing things manually myself but I guess 43v3r does it too.
I personally had no luck with it.
Sent from my DROID BIONIC using XDA App
what version could you not root?
Does zerg work on 5.9.901 ?
luke1333 said:
what version could you not root?
Click to expand...
Click to collapse
893 43v3r doesn't work on, if you restore the 886 then root you should be fine. Just doing the update then trying to gain root isn't going to work.
kris7778 said:
Does zerg work on 5.9.901 ?
Click to expand...
Click to collapse
I don't know for sure but I am pretty confident that it would.
THANKS!
Flawless victory!
Binarality!
Has anyone rooted a previously unrooted device running version 5.9.901? Who's process?
This method worked for me, but I notice that my 3g service was weak and my 4g was gone. Even if i restarted the phone I couldn't get my 4g to work. This was after the 4g issue with VW braking it. Has anyone else had this problem?
1 click method
is there any 1 click method out there that can be used to do this ,,i used 4ever root a couple of time to restore my phone after screwing it up .. but now even that wont work .. so yeah i have the update but no root ...no matter how i try to do it before or after ..
and i unfortunately do not know how to connect to adb to push anything to my phone .. im not that technical with it ....dont have a clue .ive tried but not easy for me that is thanking you in advance Robb
One question, if I update and then for any reason I can't get root can I go back to stock rom you know the one before ota and start over? ???
Sorry for my english lol
Sent from my DROID BIONIC using XDA App
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Does nobody have an idea? Would be very sad if I couldn't use it anymore. Although I'm the only one to blame. Does someone have experience on sending it back to amazon for warranty? As far as I know rooted devices lose their warranty.. :-/
Karelian_ said:
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Click to expand...
Click to collapse
At this point, I would send it back to Amazon. all they will check for is physical damage and send it back to China. I hear some people bricking their tablet several times and getting a replacement. Thing is that Amazon's warranty questions are only water damage and did you drop it questions. So you don't even have to BS them to get a replacement.
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
braider said:
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
There are no exploits for this boot loader yet. Don't think a fastboot cord will do much at the time.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app
Did noone come up with a solution, because i did the same thing, with the framework-res.apk
i can make a fastboot cable if itll do any good without an unlocked bootloader. could i possibly push the most recent update.bin from amazon and restore the device to stock???
---------- Post added at 04:06 AM ---------- Previous post was at 03:10 AM ----------
i wouldnt take bricked for an answer and i found a fix
what i did was make sure the kindle was connected to adb and typed the following
adb reboot
adb wait-for-device shell su
the shell managed to snag the SU file and displayed # before the device looped thru all of the boot apps over and over, but then CMD froze.
so i tried this
adb reboot
adb wait-for-device shell su mount -o remount,rw -t ext4 /dev/block/platform/omap/omap.hsmmc.1/by-name/system /system
and in one line got root access and remounted the system as RW
my problem was that framework-res APK was replaced with ZIP so all i had to do was rename it
# cp /system/framework/framework-res.zip /system/framework/framework-res.apk
and success!!
# exit
$ exit
adb reboot
and she booted right up!!!!
First response so please be kind. My KFSOWI is stuck in the bootloop too. I have a factory cable and can get into fastboot but don't have any factory images to restore. Anyone have any ideas?
Do you get any adb access? I don't think casebook will be any help until someone unlocks the bootloader
Sent from my KFSOWI using XDA Premium 4 mobile app
Hi, everybody!
Several days ago i've got OTA update from VERIZON. You can download it from attach.
Changelog from official Motorola site
I agreed and installed this update. After it i had 98.72.18-8 SW version.
So, i have had the trouble: i couldn't got root rights by Dan Rosenberg exploit - Motorola fixed the way, we had root on previous JB 98.72.18 and 98.72.18-2 !
After analysing install-script file from OTA update and thinking around it i decided to downgrade with RSDLite to 98.72.18 and do some manipulations with SU binary:
Start point: 98.72.18-2 installed, rooted
Code:
adb kill-server
adb start-server
sleep 5
adb shell su -c "mount -o remount,rw /system"
adb shell su -c "cd /system/bin/ && mv run-as run-as2 && mv /system/xbin/su run-as" #because of script do chmod on this file
adb reboot recovery
#turn on Sideload manually in recovery
adb sideload Blur_Version.98.72.182.XT894.Verizon.en.US.zip
sleep 400
adb kill-server
adb start-serversleep 5
adb shell run-as -c "mount -o remount,rw /system" #i used RUN-AS instead SU =)
adb shell run-as -c "cd /system/bin/ && mv run-as /system/xbin/su && mv run-as2 run-as"
adb shell su -c "chmod 6755 /system/bin/su"
this way gave me root rights for adb Shell, but applications still not getting root.
Any ideas, how to fix?))
Sorry for mistakes, i've tryed to avoid it)
way to fix
So, i fixed it!
1. At the start, we have 98.72.182 system, rooted by Dan Rosenberg exploit
2. Installing Safestrap recovery
3. Downloading on sdcard-ext latest SuperSU
4. Under Safestrap, installing UPDATE-SuperSU-v1.89.zip
5. Reboot to stock Android, bying SuperSu pro key, installing
6. Going to settings, and uncheck Screen block (set NONE)
7. Going to Superuser -> settings, install checkboxes: Survival mode, Enable su during boot, Trust system user
8. Reboot to the stock recovery, installing OTA update
9. Booting to OS.... (After booting you can return screen block )
10. Enjoy!
Orrrrrrrr update su binaries and back up root with voodoo. Temp disable root install update then voodoo. Restore root and enjoy... now I can only say because this is what worked for me without all the extra hoopla
Sent from my DROID4 using Tapatalk
rruleford said:
Orrrrrrrr update su binaries and back up root with voodoo. Temp disable root install update then voodoo. Restore root and enjoy... now I can only say because this is what worked for me without all the extra hoopla
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I can take a video with Vodoo, which will fail with restoring root.
Before posting, i've tryed voodo ota keeper, and ota keeper function in another superuser software)
Thanks for the heads up on the update breaking root. I'll have to wipe my phone and start fresh before I do the update......unless I go kitkat.
Update.....
I tried voodoo and the OTA would not come through for me. It looks like the update will be more complicated than it's worth so the kitkat rom's will be in my near future.
Voodooo worked for me on latest O.T.A
karlsdroids said:
Thanks for the heads up on the update breaking root. I'll have to wipe my phone and start fresh before I do the update......unless I go kitkat
Click to expand...
Click to collapse
Voodooo worked for me on latest O.T.A
rruleford said:
Orrrrrrrr update su binaries and back up root with voodoo. Temp disable root install update then voodoo. Restore root and enjoy... now I can only say because this is what worked for me without all the extra hoopla
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
mercermtn said:
Voodooo worked for me on latest O.T.A
Click to expand...
Click to collapse
Voodoo worked for me too. Just got the OTA notice today from VZW. Followed rruleford's steps and it worked.
This was my first time using Voodoo, and possibly my imagination or possibly not - but something funky happned where I needed to reboot the phone and re-check enable in SuperSU, which was obscured by the fact Voodoo was stating it ~had~ root...
So, is there anything besides these bugfixes in the update? Any Android version updates or maybe a fix for the Shift key behaving like a lunatic?
Dang.
My wife already applied the update to her D4 and now I've lost root on that device. Can anyone advise me what to do? Should I use RSDLite like OP states? I am confused because Moto SBF page says "never flash an older version"...
tried using voodoo and the update wouldn't work...dono what to do.
svrnmnd said:
tried using voodoo and the update wouldn't work...dono what to do.
Click to expand...
Click to collapse
Did you disable SuperSU after you backed up w/ Voodoo?
Negative, how do I disable? NOTE I use superuser not superuserSU
Sent from my DROID4 using xda app-developers app
svrnmnd said:
Negative, how do I disable? NOTE I use superuser not superuserSU
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Im not 100% sure w/Superuser - its probably similar: in settings uncheck 'Enable Superuser'
Also - if anyone out there has info on helping me w/ my wifes D4 here (a couple posts up) I would appreciate it...
bigmatty said:
Im not 100% sure w/Superuser - its probably similar: in settings uncheck 'Enable Superuser'
Also - if anyone out there has info on helping me w/ my wifes D4 here (a couple posts up) I would appreciate it...
Click to expand...
Click to collapse
Looks like you'll have to wait for a new method to be released orrrrr if another d4 is available that's rooted try downloading voodoo on both devices and backup root on rooted device then copy backup file to unrooted phones voodoo directory and try to restore that way and don't forget to update su binaries
Sent from my XT894 using Tapatalk
rruleford said:
Looks like you'll have to wait for a new method to be released orrrrr if another d4 is available that's rooted try downloading voodoo on both devices and backup root on rooted device then copy backup file to unrooted phones voodoo directory and try to restore that way and don't forget to update su binaries
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Awesome - thanks for the reply! Yes, I have my D4 same as hers, working well and w/ a Voodoo backup... I had considered this, but couldn't find the Voodoo file backup location. Do you by chance know where it is?
Why are y'all struggling so much with this.
1. You don't need to unroot.
2. You don't need to unfreeze anything.
3. RAZR_BLADE root method still works. You have to clear cache and data and force close Smart Actions before re-rooting.
I've done three Droid 4's already. All had different apps/services frozen via Titanium Backup and all were of course rooted. One (mine) got the SOAK at version .188 and the other two got the roll out at version .189.
Install update, clear Smart Actions and re-root with the razr_blade method .bat files.
Simple, works and reauthorizing Titanium Backup will refreeze all the apps you had frozen before the update.
Sent from my Nexus 10 using Tapatalk
bigmatty said:
Awesome - thanks for the reply! Yes, I have my D4 same as hers, working well and w/ a Voodoo backup... I had considered this, but couldn't find the Voodoo file backup location. Do you by chance know where it is?
Click to expand...
Click to collapse
Not to sure as I deleted all mine when installing cm11 on stock ROM slot. Try above method with RAZR blade?
Sent from my XT894 using Tapatalk
tcrews said:
Why are y'all struggling so much with this.
1. You don't need to unroot.
2. You don't need to unfreeze anything.
3. RAZR_BLADE root method still works. You have to clear cache and data and force close Smart Actions before re-rooting.
I've done three Droid 4's already. All had different apps/services frozen via Titanium Backup and all were of course rooted. One (mine) got the SOAK at version .188 and the other two got the roll out at version .189.
Install update, clear Smart Actions and re-root with the razr_blade method .bat files.
Simple, works and reauthorizing Titanium Backup will refreeze all the apps you had frozen before the update.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
On 1 & 2 - not entirely sure anyone said to unroot or unfreeze, but I did read where it was advised to 'temp disable root', and when I followed that step voodoo did work great to allow me to update and restore root.
THANK YOU for 3!! I assumed based on some of the other comments that it didn't work. I just tried it on the other phone, and it DID restore root. VERY MUCH appreciated!!
So I use voodoo to unroot I disabled superuser but the update starts and fails everytime, I don't know why, the little android starts to update, then just gets a red x through it...
Sent from my DROID4 using xda app-developers app
I have quite a few apps frozen, but apparently nothing that prevented the install from being downloaded automatically. I unrooted with Voodoo, installed the update, restored root and all is well.