guys I finally have been able to root mu atrix hd on jb . this is what worked for me http://forum.xda-developers.com/showthread.php?p=35905543#post35905543
Did you have partial root previously? If you didn't, a new thread was warranted. If you had partial root, why create a new thread?
After I upgraded ota to jb. Su ceased to work entirely the binary would not update. and all root apps were no longer working. i did have a su-backup but was getting nowhere in my attempts to use the app. i was only able to invoke a root prompt. i looked all over the internet not just the xda forums. i tried mattigriffs root restore. i typed into a command prompt for several hours each day.. all i ever got was a root prompt in adb shell. no prompt on the phone emulator. this is the only page that has worked for me. i noticed right away that the code was written differently than any other that i tried. also the su used is different(it is described as wide open) any way because of this i felt that others who were /are in the same boat. no root. may be able to get root back. I hope that answers your question. have a great day! .
Simple yes or no would have worked. I was hoping that by chance someone was stating that they didn't have root previously and were able to obtain root using this method.
Someone tested if it works on 4.1.1 official without prior recovery Boodoo ota?
Sent from my MB886 using xda premium
ashraf sharif said:
After I upgraded ota to jb. Su ceased to work entirely the binary would not update. and all root apps were no longer working. i did have a su-backup but was getting nowhere in my attempts to use the app.
Click to expand...
Click to collapse
Thats what happened to me as well
Would this work if i havent rooted my device prior tho official jb update
Sent from my MB886 using xda premium
My question too any idea
Sent from my MB886 using xda premium
sickkside13 said:
Would this work if i havent rooted my device prior tho official jb update
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
If I wasn't at work I would try it.
Lol me 2. I bought the phone online but it already came with jb i didnt knew the bootloader was locked .
Sent from my MB886 using xda premium
I think what that is fake
Sent from my MB886 using xda premium
i am no expert. and from my reading the forums. the consensus is that if you lost root after the upgrade then you have a chance of regaining it. this method was not meant as a root for atrix hd. but it worked for me. one thing that helps is the abilithy to invoke a root prompt in adb shell. i had a su-backup in /system/usr/we-need-root. ,/su-backup; su i was able to achieve shell root only until today. the the commands used are not identical to the ones i have tried for the past 11 days and the su used is described as 'wide open' whatever that means. Another thing i noticed was that the instructions said to download the su from the play store and update the binary while still in adb shell. , instead of rebooting. when i did this the binary finally gained root.I tried alot of methods none worked except for this one.i was not expecting this to work but it did. I dont know why. all i know is it worked for me. if you choose to try this . best of luck and i sincerely hope it works for you too.
This is gonna sound dumb but, how do I "log in to ADB" (Step 2)? I got the same problem u had and am trying to figure this method out.
Sent from my MB886 using xda premium
i got the shell prompt working with these commands found on this page http://forum.xda-developers.com/showthread.php?t=1911261
Code:
adb shell:
$ cd /system/usr/we-need-root
$./su-backup; su (that is a semicolon immediately after the ./su-backup)
# mount -o remount,rw /system
(do what needs to be done)
#exit
... su-backup must have permissions as such: (get permissions by typing this into adb shell: ls -l /system/usr/we-need-root ) If you get an error, than this specifically won't work for you.
Code:
Required su-backup permissions for manual root restore
$ ls -l /system/usr/we-need-root/su-backup
-rwsr-sr-x root ... basically, if you can find a su-backup with proper permissions (and cannot restore root with voodoo or supersu), you can manually use that to repair your root access configuration. Maybe this is well known... but to those who don't this could be useful.
Thanks
Man, I cannot figure this out for some reason.
Sent from my MB886 using xda premium
logging in to adb
cmdru1980 said:
This is gonna sound dumb but, how do I "log in to ADB" (Step 2)? I got the same problem u had and am trying to figure this method out.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
download java developement kit and android sdk
the sdk has a section called tools where you will find fastboot and adb unzip the files and install the drivers.your first cmd will be cd or'change directory" to wherever the adb folder is. then type adb shell. this should restart the daemon. good luck
This is what I get.
Sent from my MB886 using xda premium
Thank you, Ashraf! I think I got it. I really appreciate it!
Sent from my MB886 using xda premium
I am confused
Sent from my MB886 using xda app-developers app
adolfo778 said:
I am confused
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Yeah I'm confused now as well. If the people here did not have partial root to begin with and were running stock Jelly Bean firmware and then went through these steps to get root access, this needs to be made more clear. If these are users that already had root access from a previous attempt but temporarily lost it during the upgrade process, that should be clarified and merged over into another thread and perhaps edited into the first post.
Related
Hi everyone,
I have some issues with the emulator, so I'd like to know:
- Why do I get "out of memory" error messages when trying to push files?
I tried to remount /system as rw but it keeps failing... the only command that worked is adb install... I tried adb remount also.
Most important:
- Can I run the recovery mode in the Emulator?
- Also I would like to know how should be used recovery'sources to make an img file. There is the Android.mk file, but I do not succeed to compil it.
Thank you very much for those lights!
I'm really exited about getting thoses steps solved so I could more easelly dev on morphs and play around with recovery images.
should I post in dev forum?
im sry, i just wanna dev for android..
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
i cannot believe no one can answer my 2 questions in the whole xda community..
again, i just would like to dev for android
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
"EXCUSE ME" If Someone Else Has Something Similar Posted, But I Got Tired Of Reading A Thousand Posts Just To "ALMOST" Get My Question Answered!!
Anyway I Know The Last "OTA" Sent Out From Sprint or HTC (Whoever- Sent It Out) *BROKE* My Ability To Access The "Clockwork Recovery" Menu-Screen!
Since Then I Turned Security From "On to Off" With "Unrevoked-4ever" But I've Read That Even After Flashing "Unrevoked-4ever" It's Possible For Them To Send Me Another "OTA" & Re-break My Root Access!!
Does Anyone Know If What I Read Is "TRUE or Bull-Sh#%".... Am I Really "Unrevoked-4ever"???
1 More Thing What's The Benefits Of A OTA???
Sent from my HERO200 using XDA App
DISABLE OTA UPDATES!!!!
To disable OTA updates that will patch this exploit, (after rooting and booted after creating a nandroid backup) run the following commands from Command Prompt.
Code:
cd C:\android-sdk-windows\tools
Code:
adb remount
Code:
adb shell
Code:
mv /system/etc/security/otacerts.zip /system/etc/security/otacerts.zip.bak
After doing this, the OTA updates WILL still download, BUT they will not pass signature checks to flash because of the code you just entered.
Did you do this when you rooted your phone? ^^
Pulled this from [Guide] How to Root Sprint 2.1 CDMA Hero
Twolazyg said:
DISABLE OTA UPDATES!!!!
To disable OTA updates that will patch this exploit, (after rooting and booted after creating a nandroid backup) run the following commands from Command Prompt.
Code:
cd C:\android-sdk-windows\tools
Code:
adb remount
Code:
adb shell
Code:
mv /system/etc/security/otacerts.zip /system/etc/security/otacerts.zip.bak
After doing this, the OTA updates WILL still download, BUT they will not pass signature checks to flash because of the code you just entered.
Did you do this when you rooted your phone? ^^
Pulled this from [Guide] How to Root Sprint 2.1 CDMA Hero
Click to expand...
Click to collapse
No... To Tell You The Truth I Rooted With "Universal Androot" Because I Was Somewhat *NEW* To The Whole "ADB/SDK/ROOT" Thing, But Since I've Probably Learned 20X More Then I Did! But As Far As "ADB" Goes I'm Still Kind Of Scared To Try Out!! Although I Have A Wireless ADB App Installed On My Phone, Does That Work, Or I Should Say Will That Work For The Command You Suggested? Also Thanx For Your Help!!
Sent from my HERO200 using XDA App
PMGRANDS said:
No... To Tell You The Truth I Rooted With "Universal Androot" Because I Was Somewhat *NEW* To The Whole "ADB/SDK/ROOT" Thing, But Since I've Probably Learned 20X More Then I Did! But As Far As "ADB" Goes I'm Still Kind Of Scared To Try Out!! Although I Have A Wireless ADB App Installed On My Phone, Does That Work, Or I Should Say Will That Work For The Command You Suggested? Also Thanx For Your Help!!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I've never used an app to root my phone, I followed a guide and did it right the first time. Here is the guide thread. What is the wireless ADB app you're using? Try terminal emulator with the commands, or take 15 min and un-root your phone, then re-root using this guide, that may solve the other issue you're having with the wigets and icons being odd. Let me know how this works for you.
PMGRANDS said:
No... To Tell You The Truth I Rooted With "Universal Androot" Because I Was Somewhat *NEW* To The Whole "ADB/SDK/ROOT" Thing, But Since I've Probably Learned 20X More Then I Did! But As Far As "ADB" Goes I'm Still Kind Of Scared To Try Out!! Although I Have A Wireless ADB App Installed On My Phone, Does That Work, Or I Should Say Will That Work For The Command You Suggested? Also Thanx For Your Help!!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
If you search android Dev section I've posted how to install adb in like 15 min also in the same thread its another guide as well either way you can have adb in 15 or 20 min tops real simple and the commands he posted will work fine I'm mobile @ work so I can't link but good luck
Root-Hack-Mod-Always™
Twolazyg said:
I've never used an app to root my phone, I followed a guide and did it right the first time. Here is the guide thread. What is the wireless ADB app you're using? Try terminal emulator with the commands, or take 15 min and un-root your phone, then re-root using this guide, that may solve the other issue you're having with the wigets and icons being odd. Let me know how this works for you.
Click to expand...
Click to collapse
Okay, I Think I Just Might Do That... Also As Far As The App I Have, It's Called "ADB Wireless", But I Also Have "Terminal Emulator"!! Which One Would You Use?? "Terminal Emulator" Guess That's Why You Posted It Obviously??.... Lol!! 1 More Thing What's The Benefits Of The OTA's?? Seems Like They Only Eff-Up Root Access!! And Thanx Once Again 4 Your Help!!
Sent from my HERO200 using XDA App
laie1472 said:
If you search android Dev section I've posted how to install adb in like 15 min also in the same thread its another guide as well either way you can have adb in 15 or 20 min tops real simple and the commands he posted will work fine I'm mobile @ work so I can't link but good luck
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
Thank You!!
Sent from my HERO200 using XDA App
I noticed this morning that there were repeated messages stating that "shell is requesting/granted superuser permissions". After rebooting my phone, nothing looked different. Then I read an article online on phandroid (unable to post links currently.) that mentioned a "rootchecker". I confirmed what I found after going into recovery "q/e 1/1" on my phone. Sorry about the noob type question here. Has anyone come up with a counter reset for this? Or are we more or less due to the locked bootloader?
So far no way to reset the counter has been found. The best you can do is unroot and get a 0/1, but that's practically pointless. I'll let you know if things change.
Sent from my DROID4 using Tapatalk 2
The Magician Type 0 said:
So far no way to reset the counter has been found. The best you can do is unroot and get a 0/1, but that's practically pointless. I'll let you know if things change.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Has anyone try to format the entire phone, and then fast boot back?
Someone mentioned trying that, but I never heard the results.
Sent from my DROID4 using Tapatalk 2
Pretty sure the two things you saw are unrelated. The repeated superuser requests come from /system/bin/dumpstate. It was doing that on my phone too but I just manually killed it and that stopped. For qe you need to remove qe from the boot partition, some of the custom roms here have removed it already.
Sent from my DROID4 using Tapatalk
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
jsnweitzel said:
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
It's almost like Motorola has us all figured out! This and the unrootable Atrix HD... I think we just have to get better. I'm sure there is a root check somewhere in nvram or something
Sent from my Nexus 7 using Tapatalk 2
jsnweitzel said:
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Whoa. I mean, it probably just writes a value somewhere we can't touch (yet?), but still.
repeated shell auto-granted permissions
fade_to_red said:
I noticed this morning that there were repeated messages stating that "shell is requesting/granted superuser permissions". After rebooting my phone, nothing looked different. Then I read an article online on phandroid (unable to post links currently.) that mentioned a "rootchecker". I confirmed what I found after going into recovery "q/e 1/1" on my phone. Sorry about the noob type question here. Has anyone come up with a counter reset for this? Or are we more or less due to the locked bootloader?
Click to expand...
Click to collapse
highlandsun said:
Pretty sure the two things you saw are unrelated. The repeated superuser requests come from /system/bin/dumpstate. It was doing that on my phone too but I just manually killed it and that stopped. For qe you need to remove qe from the boot partition, some of the custom roms here have removed it already.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I too have the repeated shell granted superuser permissions.
Its been so annoying, that I've just kept it temp-unrooted until i need root.
You say that it comes from "/system/bin/dumpstate", how do i go about fixing this?
Note: I rooted my phone with the D4 ICS tool. I had been thinking that the problem was with that - maybe it didn't clean up properly after rooting. Now I know that wasn't it.
EDIT: Found out how:
aidfarh said:
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated. There's a few ways you can do this:
Using ADB. Just type in the computer command prompt with the phone connected via USB. Of course, you need USB debugging enabled and have the android SDK installed on the computer.
Code:
adb shell chmod a-x /system/bin/dumpstate
Using Terminal Emulator on the phone. Just type the following commands:
Code:
$ su
# chmod a-x /system/bin/dumpstate
Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
Click to expand...
Click to collapse
Morlok8k said:
I too have the repeated shell granted superuser permissions.
Its been so annoying, that I've just kept it temp-unrooted until i need root.
You say that it comes from "/system/bin/dumpstate", how do i go about fixing this?
Note: I rooted my phone with the D4 ICS tool. I had been thinking that the problem was with that - maybe it didn't clean up properly after rooting. Now I know that wasn't it.
EDIT: Found out how:
Click to expand...
Click to collapse
After doing this, here is what i did in a terminal emulator:
Code:
su
mount -o remount,rw /system
chmod 644 /system/bin/dumpstate
i had to do the "644" instead of "a-x" because i kept getting an error message "Bad mode 10|"
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
No such file??
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
No such file???
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
It's /system/bin/dumpstate not /sys/bin/dumpstate
removing execute permissions does not do anything.
Should I or shouldn't I?
Got my new D4 some 2 months back, unrooted.
Was planning to root it. Now going through this thread, brings me to a question "Should I or shouldn't I?"
supraket said:
Got my new D4 some 2 months back, unrooted.
Was planning to root it. Now going through this thread, brings me to a question "Should I or shouldn't I?"
Click to expand...
Click to collapse
I say.....
You should:
unlock tether, free apps, better phone, harder to replace if something goes wrong (worth it to me)
You shouldn't:
warranty risk, stock performance, easy replacement
je2854 said:
removing execute permissions does not do anything.
Click to expand...
Click to collapse
I haven't personally tried this, but is this executable required for anything else?
Why not rename it and leave a dummy script in it's place?
intellitek said:
I haven't personally tried this, but is this executable required for anything else?
Why not rename it and leave a dummy script in it's place?
Click to expand...
Click to collapse
I think it would still try to read it (the coding) seeing it is coming from Moto themselves... IDK though.
the file is meant for QE warranty purposes
je2854 said:
I think it would still try to read it (the coding) seeing it is coming from Moto themselves... IDK though.
the file is meant for QE warranty purposes
Click to expand...
Click to collapse
Okay, well, let's say, hypothetically-speaking, somebody was willing to experiment with this.
When exactly does this "rootchecker" run? I guess I'd need to rename/replace it before it runs, but after I've rooted. Or somehow before, although I believe that's currently not possible. I'll try and see if the bin is signed.. not sure how to check if it's actually verifying it on exec, though, without rooting.
EDIT: Nevermind, it looks like it's built into the boot and recovery .img files?
Hi, when I want to install a samba server, I have an error all the time. I am using Ubuntu 12.04 LTS liveCD 32bit. What can I do?
[email protected]:~$ mkdir /tmp/share
[email protected]:~$ sudo apt-get install samba
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
samba : Depends: samba-common (= 2:3.6.3-2ubuntu2) but 2:3.6.3-2ubuntu2.3 is to be installed
Depends: libwbclient0 (= 2:3.6.3-2ubuntu2) but 2:3.6.3-2ubuntu2.3 is to be installed
Recommends: tdb-tools but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Sent from my MB886 using xda app-developers app
I ran into that issue but I figured out that the live CD doesn't boot with wifi by default so I ended face palming myself . lol but if your wifi is on try the live usb option.
Try rebooting system and I used Ubuntu 12.10 but I actually had it already installed but try it again with with a wired connection as yesterday I keep getting similar errors til I connected via wired. Also I copy and paste every command instead of typing it my self to avoid mistakes
ATRIX HD running BATAKANG 1.10
Ok I tried with a wired connection and I got the same error I am goin to try with a usb stick with ubuntu 12.04 lts and 12.10
Ok It work with ubuntu 12.10 usbstick but what I have to do to keep the root because I used voodoo OTA RootKeeper v2 and when I reboot and restore root with it I doesnt work root cheker say that i dont have proper root access. What to do to keep root
voodoo ota root keeper isnt responding after I restore root
http://www.samba.org/samba/security/CVE-2012-2111
Is that the latest version from Ubuntu? If it is, I hope they at least patched it for you.
Did u downloaded from the play store and if the root checker doesn't detect it reboot ; but make sure you back up root . Reboot and then install safestrap 3 (its somewhere in this forums its not hard to find )and then once u reboot phone again it should boot into a recovery screen right after Motorola logo you can continue and then check for root .
ATRIX HD running BATAKANG 1.10
LeGenDz R3DeaDz said:
Ok It work with ubuntu 12.10 usbstick but what I have to do to keep the root because I used voodoo OTA RootKeeper v2 and when I reboot and restore root with it I doesnt work root cheker say that i dont have proper root access. What to do to keep root
Click to expand...
Click to collapse
After you get root open superuser app and update binary
Sent from my MotoAHD Maxx
I don't see any update button in the app
Sent from my MB886 using xda app-developers app
It should prompt you with an update window
ATRIX HD running BATAKANG 1.10
LeGenDz R3DeaDz said:
I don't see any update button in the app
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
You tap the binary version on the very left screen and it'll pop up with a window to update.
Sent from my MotoAHD Maxx
Thank you
Sent from my MB886 using xda app-developers 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.