Database Info

[Q] 3.1 @rooted devices

OK, so why does 3.1 update fail on a rooted device ?
The only thing I did when rooting my device was to replace
the "su" program. If I revert that change, will the OTA update
work ?
Anybody has the original "su" and it's mode settings (ls -l) ?
Thanks,
rudi
PS: Actually, I guess we need the "su" from 3.0.1 ...

But to get "su" on there in the first place, you likely had to flash your boot.img.
The update checks your system and boot.img to verify that it's stock before proceeding, as applying patches to modded files will likely have craptastic results.
What method are you using to update? What specific error message are you getting on the failure?

Yeah, so if reverse the boot.img and "su" package, the original
update should work ?
I don't remember the error message, I got the OTA update, and
it basically failed. Has not shown up again ...
Thanks,
rudi

FYI, I was able to root my xoom without loosing any data following these steps:
http://www.mydroidworld.com/forums/...ow-manually-update-your-xoom-3-1-3-0-1-a.html

luudee said:
I don't remember the error message, I got the OTA update, and
it basically failed. Has not shown up again ...
Click to expand...
Click to collapse
Weird...I'm rooted...got the OTA update, hit Install now, it went through the countdown process to reboot and install update, but then nothing happend. No reboot, no error message. I manually shutdown and turned on the device and got nothing.
Is that what happened to you?
--Q

Yeah, that's what happened to me as well. It looks like it will install the update,
but than shows some message for a second and than shows the android with
the Explanation mark (Warning sign).
If you check, you will see that you are still using 3.0.1 ... (At least that was my case).
Follow the post i referenced above, it is easy, safes all your data and gives
you 3.1 and root.
Cheers,
rudi

Thanks...that was my original plan, but then I got the OTA notification and figured I'd do that instead. Guess not! LOL
--Q

Having trouble rooting, any help?

I am following the guide from the cyanogenmod wiki on how to get CM on my droid 2, however I am getting hung up on one step.. all previous steps have worked fine and I am running android 2.2. I am getting stuck on running the rageagainstthecage script.
I run this command;
/data/local/tmp/rageagainstthecage-arm5.bin
and it appears to run. I then lose my adb connection. Upon restarting adb, I am unable to see the device with 'adb devices'. I am able to browse the phone storage, though. The only way to get it to show up with adb again is to reboot the phone. Upon rebooting and doing an 'adb shell' I still have the $ prompt instead of the # prompt. Any ideas?

Have you tried it my way?
http://forum.xda-developers.com/showthread.php?t=1466786
It's a bit easier than the CMWiki way.

Google 'pete's root tools' and use it. It takes 5 minutes and does everything for you. It's as close to a 'one click' as you can get on gingerbread.

beepea206 said:
Google 'pete's root tools' and use it. It takes 5 minutes and does everything for you. It's as close to a 'one click' as you can get on gingerbread.
Click to expand...
Click to collapse
OK, will this work with the 2.3.3 update?

loudog3114 said:
OK, will this work with the 2.3.3 update?
Click to expand...
Click to collapse
yes, look for link in my sig sbf/root/rom
then look for droid 3 root

[kill write protection] MotoWpNoMo

Introducing MotoWpNoMo. The purpose of this application is to disable the pesky write protection on BL-locked motorola devices. After successfully running this application, you will no longer need to boot recovery or use other methods to temporarily remove write protection. This exploit is permanent in the sense it will survive factory resets, reflashing the device, etc. However, like with any exploit, you should not expect it to survive OTA's or other updates. This application will work with many motorola devices, however I'm only posting it here to keep the files and feedback consolidated (plus, I'm lazy). THIS IS NOT A BOOTLOADER UNLOCK, IT ONLY REMOVES WRITE PROTECTION. Let's get started....
Credits and terms:
beaups and fuses for MotoWpNomo application. jcase for root and gunnyman and brianr134 for testing. MotoWpNomo MAY NOT BE REHOSTED, REPACKAGED, INTEGRATED INTO A ONE-CLICK, BAT, SHELL SCRIPT, OR ANY OTHER APPLICATION. THE ONLY PLACE TO ACQUIRE THIS APPLICATION SHALL BE RIGHT HERE, IN THIS THREAD. THIS IS NOT OPEN SOURCE, DON'T ASK!
Pre-requisites:
1.) Working root (su). Jcase's methods are fully supported here
2.) Working adb and fastboot drivers. Yes, that means WORKING. Don't clutter this thread with driver issues
3.) Linux (32 bit) or windows
4.) Disable all firewalls/internet security/antivirus before running. This is the #1 issue encountered when running the application
Instructions:
Linux (preferred):
1.) download the application: motowpnomo
2.) extract the archive: tar -xf [filename]
3.) run the application: sudo ./wpbegone
4.) follow the on-screen prompts
Windows:
1.) download the application: motowpnomo
2.) extract the archive
3.) run wpbegone.exe as administrator
4.) follow the on-screen prompts
After the application is complete, you can verify with:
adb shell getprop ro.boot.write_protect
If you see "0", that pesky write protection is gone
Donations are appreciated and can be made to (paypal): [email protected]
support is available in #MotoWpNoMo on the freenode and andirc networks.

Wow... Sounds great.
So... What part of the phone is changed? How do you revert to stock?
Thanks!

Ctrl-Freak said:
Wow... Sounds great.
So... What part of the phone is changed? How do you revert to stock?
Thanks!
Click to expand...
Click to collapse
1.) a magical part
2.) you don't

It works! Thanks Beaups

Nice. Will try when I get home
Sent from my XT1058 using Tapatalk

If you are running this on a Mac in a VM, each time the phone reboots and the program is waiting for adb, unplug the phone and plug it back in once the phone is started up again or else the process will fail.

Sounds great but is there no way to get back to write-protected other then OTA? Will flashing the FXZ restore it?
Sent from my XT1049 using Tapatalk

would this work on the droid line up?

TheWhiteChallenger said:
would this work on the droid line up?
Click to expand...
Click to collapse
possibly. try it.

RobertsDF said:
Sounds great but is there no way to get back to write-protected other then OTA? Will flashing the FXZ restore it?
Sent from my XT1049 using Tapatalk
Click to expand...
Click to collapse
in what case would you want write-protection back? also, no, flashing FXZ will not restore it.

PERFECT!!! Hated that i couldnt write protect off even with an unlocked bootloader!! Now everything is fine!!! :good:

beaups said:
possibly. try it.
Click to expand...
Click to collapse
cool. i will. if it works ill let you know so you can setup a thread in the droid ultra/maxx forum if you would like
---------- Post added at 03:46 PM ---------- Previous post was at 03:44 PM ----------
oh, so are you guys flashing your stock recovery back after this w/o issues?

TheWhiteChallenger said:
cool. i will. if it works ill let you know so you can setup a thread in the droid ultra/maxx forum if you would like
---------- Post added at 03:46 PM ---------- Previous post was at 03:44 PM ----------
oh, so are you guys flashing your stock recovery back after this w/o issues?
Click to expand...
Click to collapse
Recovery will not affect this. If you get issue on other device, pm me. Should be able to add support.
Sent from my HTC6435LVW using Tapatalk

beaups said:
Recovery will not affect this. If you get issue on other device, pm me. Should be able to add support.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
ok ill let u know via pm, im trying something else right now if that works i should be able to tell you in a couple hours. and i was wondering if stock recovery could be re-flashed to re-enable a standard factory reset not to remove mod. so that should work right?

TheWhiteChallenger said:
ok ill let u know via pm, im trying something else right now if that works i should be able to tell you in a couple hours. and i was wondering if stock recovery could be re-flashed to re-enable a standard factory reset not to remove mod. so that should work right?
Click to expand...
Click to collapse
Yes you can flash stock recovery after this.
Sent from my HTC6435LVW using Tapatalk

Do you thing this would work on the Droid RAZR?

After running it said no su fu after rebooting su binaries weren't up to date and su couldnt fix. Ran adb and got the 0 so it worked then had to run a couple commands from the root thread and all is well again.

Ran into an issue and jumped in your IRC. Hopefully someone is around to help.

Code:
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (4/120)
Waiting
Test 2: Booting device
Waiting for ADB (37/120)
must play a little while longer...
it's so cold in here
hmm, hold please
..............................................
[*********************************************]
ERROR: looks like device is not rooted. su or FU!!!
[email protected] ~ $ adb shell getprop ro.boot.write_protect
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1
Any idea what would cause it to not work? If there's a way for me to pull a log of what failed specifically, I could probably be of more help.
VZW Moto X locked BL running 4.4.

Are you rooted?

4.4 (V2) root still work using Jcase method?

Hey guys,
I apologize for making a new thread about this but I think some others may have this question too. So I received the second 4.4 OTA today and I'm curious if the Root exploit SlapMyMoto from Jcase will work with this new OTA? I do not know if it it is the same update as all it says it "Kitkat ... update (19.5.3.en.us)" nothing about 4.4 or 4.4.2. Thanks in advance for any input

it should...the actual OS update is the same as what we got in December.

dano1282 said:
it should...the actual OS update is the same as what we got in December.
Click to expand...
Click to collapse
for the VZW non Developer Edition right? I'm reading up on MotoWpNoMo and it references an unlocked bootloader.
Also can I do this method if I did RockMyMoto before MotoWpNoMo to gain root?

Have you already installed 4.4? If so, you're out of luck. The Moto X can be downgraded back to 4.2.2 but the DROID line can not.
Don't attempt to FXZ 4.2.2 or you'll have issues.
Sent from my XT1080 using xda app-developers app

If you follow jcase's instructions for SlapMyMoto I can verify it works. Did it this morning on my Maxx, but as stated earlier, you can not root if you've already updated to 4.4, and you can not go back to 4.2.2. If I'm remembering correctly, the basic process was: from 4.2.2, root, permanently remove write protection, go back to stock 4.2.2 (after camera update), then SlapMyMoto.

osucowboy96 said:
If you follow jcase's instructions for SlapMyMoto I can verify it works. Did it this morning on my Maxx, but as stated earlier, you can not root if you've already updated to 4.4, and you can not go back to 4.2.2. If I'm remembering correctly, the basic process was: from 4.2.2, root, permanently remove write protection, go back to stock 4.2.2 (after camera update), then SlapMyMoto.
Click to expand...
Click to collapse
here's what i've done so far. rooted using RockMyMoto AFTER camera update. Still on 4.2.2 I do not know how to remove the Write protection because I tried using MotoWpNoMo and I keep getting a "1". Also, What do you mean by "go back to stock" after removing Wp?

Carrzy said:
here's what i've done so far. rooted using RockMyMoto AFTER camera update. Still on 4.2.2 I do not know how to remove the Write protection because I tried using MotoWpNoMo and I keep getting a "1". Also, What do you mean by "go back to stock" after removing Wp?
Click to expand...
Click to collapse
keep hammering it with MotoWpNoMo. You have to get that to work and must get write protection off (0). Took several tries on mine to get it to work. Make sure you are running it with admin priv and all your antivirus etc is off and are following directions exactly.
back to stock means after you have done the above, reflash 4.2.2 camera update (15.15) to REMOVE root and get it back to a stock build.
Then do the SlapMyMoto steps 1-3, then take 4.4 update, then finalize Slap steps.

jkhouw1 said:
keep hammering it with MotoWpNoMo. You have to get that to work and must get write protection off (0). Took several tries on mine to get it to work. Make sure you are running it with admin priv and all your antivirus etc is off and are following directions exactly.
back to stock means after you have done the above, reflash 4.2.2 camera update (15.15) to REMOVE root and get it back to a stock build.
Then do the SlapMyMoto steps 1-3, then take 4.4 update, then finalize Slap steps.
Click to expand...
Click to collapse
In addition, when I did MotoWpNoMo the first time, I noticed it was asking for root access on my phone and I had to unlock my phone and give it access. The first time failed, I believe, due to not immediately having root access (I got a line with like 4-5 "T"s followed by either a bunch of dashes or asterisks, then next line was "Press Enter to exit" or something similar). The second time I ran it, since it now had root access, it ran like a charm.
To get back to 12.15.15 after removing write protection, I used HouseOfMoto, keeping data. Some prefer a full wipe.
Good luck, and if you run into any other issues I'll help any way I can. No expert, but I'll offer what limited advice I can.

osucowboy96 said:
In addition, when I did MotoWpNoMo the first time, I noticed it was asking for root access on my phone and I had to unlock my phone and give it access. The first time failed, I believe, due to not immediately having root access (I got a line with like 4-5 "T"s followed by either a bunch of dashes or asterisks, then next line was "Press Enter to exit" or something similar). The second time I ran it, since it now had root access, it ran like a charm.
To get back to 12.15.15 after removing write protection, I used HouseOfMoto, keeping data. Some prefer a full wipe.
Good luck, and if you run into any other issues I'll help any way I can. No expert, but I'll offer what limited advice I can.
Click to expand...
Click to collapse
I gave it root access but I still get the T's and asterisks. I'll keep trying tho and I appreciate the help guys

Alright so I was able to disable Write protection successfully but now I don't know how to to create and FXZ file for House Of Moto (steps, 3,4 & 5)

Possible Root

Okay so as the fire just updated to 5.4.0.0 and now 5.4.1.0 this means there is an exploit somewhere. If it doesnt have a changelog, Amazon probably increased security.
I would recommend getting No Root Firewall of the play store. Block internet for all amazon apps except Amazon Downloader, and Google play services (this could show as an Amazon app)(This prevents auto updates)
When an update comes out with no changelog DO NOT UPDATE TO IT. AmazonFresh this when they find an error. And an error could mean possible root.
If you did the steps above you shouldn't be receiving updates, there for meaning, you have the possibility of root.

Cancel Update?
Hi,
I installed Netguard and blocked System Update and some Alex services.
At first that kept system updates from connecting and it said: "can't check update" or something.
10 Minutes later suddenly the 5.6.0.0 update shows up and it says it will install when inactive.
What can I do to prevent it from updating?
Running 5.4.0.1
P.S.
Kingroot still not working,
"rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin" did nothing (no files)
"rm -rf /cache/*" gives 'Permission denied'
using adb shell

Has anyone tried the root yet?
https://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276

0v3rdr1v3 said:
Has anyone tried the root yet?
https://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
Click to expand...
Click to collapse
The last comment on that post is from 2016. It says:
"This root method is no longer supported and does not work on recent devices. Thread closed."

lehnin said:
Hi,
I installed Netguard and blocked System Update and some Alex services.
At first that kept system updates from connecting and it said: "can't check update" or something.
10 Minutes later suddenly the 5.6.0.0 update shows up and it says it will install when inactive.
What can I do to prevent it from updating?
Running 5.4.0.1
P.S.
Kingroot still not working,
"rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin" did nothing (no files)
"rm -rf /cache/*" gives 'Permission denied'
using adb shell
Click to expand...
Click to collapse
Hmm, maybe PM clear <packagename>

sorry new guy here...
thefanum said:
The last comment on that post is from 2016. It says:
"This root method is no longer supported and does not work on recent devices. Thread closed."
Click to expand...
Click to collapse
Does this mean that rooting these is NEVER going to be a possibility? Or a new method is being developed and is not out yet? Also I have 2 HD 8's, one is on 5.6 and the other is on 5.4.0.1. Does the factory reset bring it back to 5.4.0.1?

Aethernoob said:
Does this mean that rooting these is NEVER going to be a possibility? Or a new method is being developed and is not out yet? Also I have 2 HD 8's, one is on 5.6 and the other is on 5.4.0.1. Does the factory reset bring it back to 5.4.0.1?
Click to expand...
Click to collapse
These have been out for months without a root solution. I would guess it could easily be months more before we find a solution. Or longer, if at all.
Factory resetting will not downgrade your firmware ever on any device. Do not attempt to downgrade manually, as it would brick it.
If you factory reset, it will try to auto update as soon as you connect to WiFi. If you set it up without network access, and then remote the OTA feature, it may not upgrade the firmware. I just did exactly this, and it went fine. But there's no room for error.
Your best bet for root is to block OTA's and wait. As far as we know, there is no root method even under development currently. Although, if I were working on one, I sure wouldn't tell anyone, and get "ETA'd" to death.

[QUOTE="thefanum, post: 74729008, member: 4404866"]These have been out for months without a root solution. I wo
thefanum said:
These have been out for months without a root solution. I would guess it could easily be months more before we find a solution. Or longer, if at all.
Factory resetting will not downgrade your firmware ever on any device. Do not attempt to downgrade manually, as it would brick it.
If you factory reset, it will try to auto update as soon as you connect to WiFi. If you set it up without network access, and then remote the OTA feature, it may not upgrade the firmware. I just did exactly this, and it went fine. But there's no room for error.
Your best bet for root is to block OTA's and wait. As far as we know, there is no root method even under development currently. Although, if I were working on one, I sure wouldn't tell anyone, and get "ETA'd" to death.
Click to expand...
Click to collapse
Being super green in this field if you "brick" it and then "unbrick" it will that just fastboot it back to factory set points? Also is there a glossary for all these acronyms... it would be glorious if there was!!!

Aethernoob said:
Being super green in this field if you "brick" it and then "unbrick" it will that just fastboot it back to factory set points? Also is there a glossary for all these acronyms... it would be glorious if there was!!!
Click to expand...
Click to collapse
Brick means physically broken, usually forever. As in, your tablet is now as useful as a brick. There are soft bricks where just the firmware is broken, but can be fixed by reflashing (still won't downgrade). But we're taking about a full brick. As in, you destroy your tablet and have to buy a new one.