[Q] su freezes programs asking for root access, need fix. - Galaxy Ace S5830 Q&A, Help & Troubleshooting

I have a Samsung Galaxy Ace from Telcel in Mexico running CyanogenMod 7.2.0 stable, using Link2SD and ClockworkMod 5.0.2.7 (I think, will edit later).
As of lately I've been getting some random weird behavior with su. Every now and then, it will cause any app asking for root access to freeze, and after much wailing and desperate fiddling the only way I could fix it was by restoring a known-good Clockwork backup. It's been happening for about a week already about every 2 days or so and I am sick and tired of having to restore backups all the time.
Is there a way to manually fix su without having to restore an older backup? If not or if I am completely in the wrong, then just what is going on?

Did you update su binary?
Sent from my GT-S5830 using xda premium

Some time ago I updated my su binary to the latest version.
If this is the problem, is there a way to downgrade su? I have previously tried to look for a way to do it but found nothing.

download superSu from the market . i was having the same problem and for me is work now...good luck

OK, I just tried running SuperSU. It didn't work, when I start it it says I should update my su binary and then it gets stuck forever trying to install it.
I can't do it right now because I'm at work, but I'm thinking about something like this to downgrade su:
Make a CWM backup
Extract the backup's system.tar under Linux on my desktop computer (not Windows because that would break the files' UNIX-like attributes).
Replace the current su binary with an older su from a previous backup.
Repack and recalculate the MD5 hashes
Flash the modded backup with CWM
Since it won't be until 8 hours later that I'll have a chance to test it, what could possibly go wrong?

Da_Nuke said:
OK, I just tried running SuperSU. It didn't work, when I start it it says I should update my su binary and then it gets stuck forever trying to install it.
I can't do it right now because I'm at work, but I'm thinking about something like this to downgrade su:
Make a CWM backup
Extract the backup's system.tar under Linux on my desktop computer (not Windows because that would break the files' UNIX-like attributes).
Replace the current su binary with an older su from a previous backup.
Repack and recalculate the MD5 hashes
Flash the modded backup with CWM
Since it won't be until 8 hours later that I'll have a chance to test it, what could possibly go wrong?
Click to expand...
Click to collapse
Just replace it manually.MD5 might create some problems otherwise.Or have you tried that already?
Insert witty sentence here

Related

[GUIDE] upgrade / root Gingerbread / Froyo, flash custom roms July/05

I thought it might be useful to put all the info into one thread.
I hope it's completely needless to say that I don't take any credit, since I haven't contributed anything to make that possible
This guide is for rooting your CURRENTLY installed firmware, flashing custom roms, or if you want to upgrade to Gingerbread
If you are NOT S-OFF yet, you either need to get / use an XTC Clip, or use a software exploit / hack (AlpharevX).
The basic differences between both approaches are the following:
AlpharevX:
"Software" S-OFF using an exploit
Bootloader S-OFF
It will flash a hacked HBOOT that sets your device S-OFF.
If you flash an unmodified RUU, or anything that replaces this HBOOT, you will lose S-OFF
-> Not a problem if you stay with custom roms!
Completely free and great solution!
XTC Clip:
Complete "hardware" S-OFF
All locks removed including sim and cid lock.
Permanent solution (radio S-OFF)
-> You can flash anything and won't lose S-OFF
Costs money, or you need to find someone that owns a Clip to do this for you
UPDATE:
Hawkysoft posted about a rare occurrence that has been reported after using AlpharevX:
If you get a security warning in hboot, you will need an XTC Clip to get you running again!
Of course you might also send your phone to repair, but you'll most likely need to pay for that.
So if you experience this problem, either get someone with an XTC Clip to help you out, or buy an "XTC Clip Pay as you go", which is a very cheap variant that comes only with one use (rechargeable) and costs around 30USD.​
See the following tutorial to set your device S-OFF with AlpharevX: GUIDE -> S-OFF
And pause at the point where you should install CWMR (ClockworkMod Recovery) to consider the following options:
Do you want to switch to a custom rom after S-OFF?
-> continue with the guide above installing CWMR
Do you want to keep your official firmware and replace your official recovery with CWMR?
--> continue with the guide above installing CWMR,
but before you install a custom rom, make a backup of your current firmware in CWMR!
Do you want to keep your orig firmware AND the official recovery?
--> don't continue with the guide above and follow this guide instead
​
Be it Froyo or Gingerbread doesn't matter.
If you insist you only want to root your Froyo rom and not upgrade to Gingerbread immediately, please scroll further down.
A rooted Froyo rom is NOT necessary for flashing and afterwards rooting Gingerbread!
If you need further details about flashing custom roms just scroll down.
If you haven't done so already (you didn't get an OTA or you didn't do it manually yet) and you want to upgrade to Gingerbread, here's a short guide on how to flash it first..
How to install the Gingerbread update​
download one of the Gingerbread Roms
http://forum.xda-developers.com/showthread.php?t=1033922
This link is for the Incredible S only of course, but the following works also for the Desire S, but then please use a rom for your phone
ATTENTION: If you are NOT S-OFF yet and you are planning to using AlpharevX, you MUST use an ruu compatible with AlpharevX! Check that first!
start the RUU installer
[*]go into your tmp folder to get rom.zip from the extracted files of the RUU installer:
Access the tmp folder by clicking on start/run and put %tmp% into the textbox. Or for windows 7 put this into this search textbox in the "start menu"
Look for the most recent folder (sort by date). In that folder look for rom.zip or simply do a search.
After acquiring rom.zip from your tmp folder you can exit the RUU installer
[*]Put rom.zip onto your sdcard and name it PG32IMG.zip.
boot into the bootloader.. (press and hold vol.down + press power) it will automatically start to install it and ask you if you want to proceed.
After a reboot remove PG32IMG.zip from your sdcard (otherwise it would ask you to reinstall the update each time you boot into the bootloader)
use morelocales2 from the market if you need additional languages
finished. Now follow the steps below for rooting the fw
Guide below partly out of date!
It works, but there are easier methods available now.Work in progress​
What you need if you want to root your Gingerbread rom:​
an incredible S / Desire S that is S-OFF
Gingerbreak OR SuperOneClick newest version
Busybox
UPDATE:
Some users reported that they weren't able to root using SuperOneClick or Gingerbreak.apk no matter what they tried.
After I reflashed my IS I also run into problems. Although it's not unusual that it doesn't work the 1st time, I decided to do it manually.
I have attached a zip with all the files needed and a script that you could try which does everything for you.
It doesn't do any magic or different than SuperOneClick, but if you do it this way you get to see what's actually happening and if it fails and where / why.
When using this you also don't need to reboot between the tries, reinserting / remounting your sdcard is sufficient.
Please report any bugs.
How to use:​
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
download the zip file: View attachment 596033
extract the zip and open a shell/command prompt and change into that directoy
on Linux start runexploit.sh, on Windows start runexploit.cmd
if Gingerbreak doesn't finish and you ONLY get to see lots of "sendmsg() failed?" without any other messages in between, you should try any of the following options:​
hit ctrl + c to abort, unmount / remount your sdcard and start over. It could take a few tries
Doublecheese reported it took him 8-9x​
WHILE Gingerbreak is running and printing "sendmsg() failed?" forever, pull and take out your SDcard completely and reinsert it
this worked well for vontdeux, jkolner and me​
Thanks to Vontdeux, Doublecheese, jkolner and everyone else afterwards for the feedback!​
now, after you see '#', you can hit ctrl + c or close the shell
run root.sh on Linux or root.cmd on Windows from the same directory. This will install su, SuperUser.apk and busybox
when it's finished you're done and have root
then it's very recommended to get "rom manager" from the market, open it and install clockworkmod recovery for installing custom roms, backing up your system et.c.
Files:
Big thanks to Chainfire for GingerBreak and CLShortFuse for SuperOneClick!​
SuperOneClick: http://forum.xda-developers.com/showthread.php?t=803682
OR Gingerbreak: get the latest version here: http://forum.xda-developers.com/showthread.php?t=1044765
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:​
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
use the latest SuperOneClick which might be easier.
start the application and select "GingerBreak" as exploit.
But respect the info and warning of the creator of the Gingerbreak.apk:
Chainfire said:
WARNING: Apparently on some devices the root exploit causes the SD card (internal or external) to be formatted. Also, if it gets stuck but you do see the card mounting/unmounting, try formatting your SD card yourself and try again (or use a different SD card) often this works (a fix for both issues is being looked at)
Click to expand...
Click to collapse
click root check Chainfire's post if you run into problems (also with SuperOneClick because it uses his exploit): http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
after it's finished your phone will reboot and you're essentially done.
Alternatively, don't use SuperOneClick but follow the guide of Chainfire from the beginning to install Gingerbreak on your device and root your phone: http://forum.xda-developers.com/showthread.php?p=13086954#post13086954​
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
What you need if you want to root your Froyo rom:​
an Incredible S / Desire S that is S-OFF
SuperOneClick newest version
(optional, but highly recommended) Busybox installer app
Files:
Update: apparently the current SuperUser app is crashing for some users.
If you experience these problems see the next section
Big thanks to CLShortFuse for SuperOneClick!​
SuperOneClick:: http://forum.xda-developers.com/showthread.php?t=803682
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:​
use the latest SuperOneClick
start the application and select "psneuter" as exploit.
click root
after it's finished you might need to reboot for getting Superuser app to pop up when needed.
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
So how to flash custom roms?:
it's extremely easy ​
put your favorite custom rom onto your sdcard
install rom manager if you haven't done so already
open rom manager and click "install ClockworkMod Recovery
next click "install rom from sdcard"
select your custom rom you put on your sdcard
select to backup your currently installed rom just in case you want to revert back
Most of the time you also need to check wipe cache and data (follow the instructions of the creator of that custom rom to find out if you need to do that or not. If you wipe your data, all your current settings will be lost however so make a backup!)
wiping Dalvik Cache is always a good idea and won't harm your settings
after pressing ok, Rom manager will boot into Recovery, backup your current rom (if you told it to), wipe (if you told it to), install the custom rom and reboot
Solution for SuperUser crashing:
All thanks go to rmk40 who patched SuperUser for us running newer versions of Sense:
http://forum.xda-developers.com/showthread.php?t=886999
rmk40 said:
The latest official build of Superuser does not work with newer Sense ROMs (such as Vision 1.72+, anything released recently). HTC has started utilizing a relatively new feature of sqlite; a journaling mode called WAL (write-ahead logging). It's actually smart. WAL journaling should improve sqlite throughput, which represents a large amount of Android's IO and benefits applications across the board. The downside is it broke Superuser because it's actually special in its' use of sqlite.
Click to expand...
Click to collapse
How to install the patched version
Update 5/14: Fixed a serious bug in the replace_su script that made it pretty much useless ​
If you didn't root your phone yet
You might want to patch SuperOneClick before using it the first time.
Either download the patched su and SuperUser.apk, or just use the already patched version of SuperOneClick attached to this post. View attachment 591017
If you already rooted your phone:
Usually the first app requesting root access does work with the unpatched version, so you can use this to gain root access on the shell to replace SuperUser and su with the patched versions. If SuperUser doesn't pop up, open Superuser and remove all apps you already whitelisted for su access and try again
To keep it simple, I have attached an archive with a script to do this for you: View attachment 595753​
make sure USB Debugging is enabled (in settings/apps/development)
extract replace_su.zip on your windows or linux pc
open a terminal and change into that directory
on windows run replace_su.cmd, on linux run replace_su.sh
the script needs root access so you need to press allow when SuperUser pops up on the phone
If you already installed a custom recovery and want to do it that way:​
Just download rmk40's flashable zip: http://forum.xda-developers.com/showthread.php?t=886999
put it onto your sdcard
reboot into recovery by starting rom manager and selecting reboot into recovery
if this doesn't work because SuperUser fc, shutdown your phone completely (fast boot disabled in settings/power). Press and hold vol-down and press power. From the bootloader menu: select "recovery"​
use ClockworkMod to flash the zip. "install/flash zip from sdcard.."
you can also just replace those files (SuperUser.apk and su) in your SuperOneClick directory and then re-run SuperOneClick.
Here's the "patched" SuperOneClick View attachment 591017​
Update 5/14: Fixed an error in the replace_su script.
Update 5/10: updated because of a request to re-add the Froyo rooting info
Update 5/09: updated because of SuperUser crashing issue
Update 4/27: updated due to new version of SuperOneClick now supporting Gingerbreak
Update 4/26: updated because of Gingerbreak, which makes this much shorter and easier. Thanks very much Chainfire for all the hard work!
Update 4/24: thanks very much to Hawkysoft for pointing out that psneuter doesn't work for Gingerbread and further instructions)
So if you are already gingerbreaded, please scroll down
Update 4/23: OFFICIAL CLOCKWORKMOD RECOVERY NOW AVAILABLE!!
Big thanks to Koush and Hawkysoft!
Hawkysoft said:
time has arrived, after supplying all the info, koush did a hell of a job with creating this
download rommanager from the market
and install the recovery for the Incredible S
WARNING DO NOT PARTITION SDCARD <- THIS WILL BRICK YOUR DEVICE, A FIX IS ON THE WAY
all thanks go out to koush offcourse
i tested:
backup, whipe data, restore, reboot... all worked
bugs found:
sdcard > if you do parition this, you will end up jtaggin your device cuz its bricked! (the fix is on the way)
backup time > in the folder it shows a wrong time that it has been created atleast for me it does.. it shows a 3 hour difference idk how its set but its not a big deal in my opinion
Click to expand...
Click to collapse
Please check the post by Hawkysoft!
http://forum.xda-developers.com/showthread.php?t=1046759
Nice, thanks!
OTA Updates
TimMun said:
Nice, thanks!
Click to expand...
Click to collapse
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
madmaxx82 said:
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
Click to expand...
Click to collapse
I don't know the answer to this question but first I would like to actually see an update
TimMun said:
I don't know the answer to this question but first I would like to actually see an update
Click to expand...
Click to collapse
Haha, it was really funny coincidence. After I s-offed the phone I got an OTA
BTW: If anyone wants to be S-OFF and doesn't mind visiting me in Austria, I'd help you out. For free of course
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
timbo007up said:
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
Click to expand...
Click to collapse
Thanks, so if it doesn't work you'd need to reflash the original recovery first..
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
Ahh thanks for the warning
Since the custom recovery is installed already anyway when there's an OTA update available, wouldn't the following work?
If I get notified about an available OTA update, I could flash a complete RUU, then get the OTA and afterwards re root + reflash the custom recovery?
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
nikant said:
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Correct. Its only needed to flash custom roms.
Sorry for newb question... What does S-OFF mean?
Read the rooting topic in the dev section,
But to make it easy for you: S-OFF means Security Off.
Which allows us to (over)write system files
timbo007up said:
Correct. Its only needed to flash custom roms.
Click to expand...
Click to collapse
And nandroid Can't live without it... of course especially if you flash custom roms, but also if you don't, titanium is just not always 10.000% enough
There is another recovery available from GOAPK with Reboot function that works.
can you confirm that it fully works with backin up and restoring?
since the current one failes at restoring
;p
testing it...
first try to backup FAIL <- Error while generating md5 sum!
second time as well this is a major failing recovery
I am going to try porting clockwork myself from scratch tonight
Sent from my HTC Incredible S using Tapatalk
With this recovery in the first post, I had an error at the time of restoration, with the one I posted, an error of md5 sum, but with the tutorial as an attachment, the worries of md5 sum is adjusted by 5 minutes
So I can now restore quietly after each crash, as I try to adapt a framework-res.apk to my Incredible S
Just at it now
creating md5 sums failed.. restore of course also failes..
I just restored a previously created backup with the one from llnhhy successfully
So we have a recovery that has all the functions, but has trouble creating md5 sum, and another that did not have the reboot function with a problem of restore, by mixing the two should do it .. .

Motoblur Update 219 +Download (Instructions modified for Root users)

DOWNLOAD AND INSTALL AT YOUR OWN RISK.
This will temporarily disable Safestrap, but once appled, you can restore Safestrap, and your previous Safe system should still be intact.
This is the Motorola update that is being soak tested. To install it, I unfroze all apps, used Voodoo Root Keeper to backup root, and installed from SD card.
To install from SD:
1. Download the file and place it at the root of the SD. After backing up root with Voodoo and unfreezing all apps, prepare to shut down the phone. You should temp-unroot with VooDoo at this point.
2. When turning the phone on, press and hold vol-up and vol-down at the same time. When you have the bootloader menu, press vol-down and then vol-up to get to Motorola recovery.
3. Reveal the recovery options by pressing vol-up and vol-down at the same time when the android and exclanation mark appears.
4. Choose to install a zip from SD, and choose the update. Power button serves as select, volume buttons to move selection.
5. When the update finishes and your phone reboots, restore root from Voodoo, and re-freeze any bloat. You can also restore Safestrap now.
Direct Download of Update Package:
http://omniimpact.com/android/motorola_updates/Blur_Version.6.13.215.XT894.Verizon.en.US.zip
Recommended Software:
- AntTek App Manager
- Voodoo OTA Root Keeper
NOTE: If you lose Root accidentally, that is OK, just re-root the same way you did before.
NOTE 2: Did you delete or modify your system apps instead of just freezing them? This update will fail. You need to take these packages from the original firmware and use them to replace yours. The zip file contains just the packages you need extracted from skylarmb's very useful ROM.
Sent from my DROID4 using XDA
All i did was use voodoo to temp unroot and installed update. Worked fine for me. But if this post was here before i did anything i would've followed it. I am having one issue tho. Play store wants to force close a bit. Not alot but it never did before
Sent from my DROID4 using xda premium
These directions are gathered from several locations and are designed to cover most situations. If you have not frozen bloat applications, you don't need to do the unfreezing part. My goal was to try to answer everything important in one place, such as keeping root, restoring safestrap, and bypassing the system integrity check.
Sent from my DROID4 using XDA
I have been able to get all the way the the install part but it keeps aborting because of an invalad signature. I also read that you need to installing fro the sdcard-ext. While in recovery I have no option to navigate to my ext card... any thought? Thanks everyone
Sent from under a rock
Motorola's recovery ONLY shows the external sd card, sd-ext is just what Android calls it. If you are failing in a bad signature, have you made sure to unfreeze all apps? The patch checks that the initial system is intact before installing, so all the original software has to be there.
Sent from my DROID4 using XDA
any chance to get the original system files? i deleted mine and TB couldn't restore them ;_;
Sent from my DRIOD 4 Husky Edition
Here is a copy of my /system/app folder. Some stuff is frozen, but everything is in there. Let me know if the file is corrupted, I zipped and uploaded it from my phone. The frozen stuff has _fro appended to the file name.
http://omniimpact.com/android/motorola_updates/systemappfolder.zip
Sent from my DROID4 using XDA
Thanks for the instructions. Everything installed fine for me and root was easy to restore. The battery life has been great the last 2 days, but haven't used it a ton yet.
thanks a lot for the files! I'm still having update issues though
Code:
Update location: /cache/Blur_Version.6.13.215.XT894.Verizon.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Verifying current system...file "/system/app/BackupAssistanceClient.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/BackupAssistanceClient.apk", "fd7e227c5c96c613ec46c2ed3ffe47785c9576e3", "691854fac80eefce82740d7204de4e22c1a0d9e1")
assert failed: apply_patch_check("/system/app/BackupAssistanceClient.apk", "fd7e227c5c96c613ec46c2ed3ffe47785c9576e3", "691854fac80eefce82740d7204de4e22c1a0d9e1")
E:Error in /cache/Blur_Version.6.13.215.XT894.Verizon.en.US.zip
(Status 7)
Installation aborted.
i think it's saying a checksum failed on BackupAssistanceClient.apk. how does one go about fixing this?
Make sure you have removed _fro from the apks related to backup assistant if you are copying them over. Also, I just realized, it might be an updated version (omg! Unlisted updated component!) Grab skylarmb's stock rooted rom, unzip it, and use the apk from there. It's a bit more of a pain than just a single zip of the folder, but it should have the upgradeable version of the apk.
Sent from my DROID4 using XDA
i "deforsted" the apps you mentioned. i'm going to also try and get those original apks as well.
Sent from my DRIOD 4 Husky Edition
I find it odd that the update could conflict with itself. If that is the case, Verizon has a serious oversight since that means any partially applied update would brick a phone (instead of just resuming where it left off). Let me know how it works out.
Sent from my DROID4 using XDA
what you said did the trick! the update is finally patching right now. I had to replace the system files one by one until they all passed the verification step.
omniuni said:
DOWNLOAD AND INSTALL AT YOUR OWN RISK.
This will temporarily disable Safestrap, but once appled, you can restore Safestrap, and your previous Safe system should still be intact.
This is the Motorola update that is being soak tested. To install it, I unfroze all apps, used Voodoo Root Keeper to backup root, and installed from SD card.
To install from SD:
1. Download the file and place it at the root of the SD. After backing up root with Voodoo and unfreezing all apps, shut down the phone.
2. When turning the phone on, press and hold vol-up and vol-down at the same time. When you have the bootloader menu, press vol-down and then vol-up to get to Motorola recovery. Once the Android and ! appear, press vol-up and vol-down at the same time to reveal the menu.
3. Choose to install a zip from SD, and choose the update. Power button serves as select, volume buttons to move selection.
4. When the update finishes and your phone reboots, restore root from Voodoo, and re-freeze any bloat. You can also restore Safestrap now.
Direct Download of Update Package:
http://omniimpact.com/android/motorola_updates/Blur_Version.6.13.215.XT894.Verizon.en.US.zip
Recommended Software:
- AntTek App Manager
- Voodoo OTA Root Keeper
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
You forgot a key step... I bolded it above.
---------- Post added at 05:47 AM ---------- Previous post was at 05:25 AM ----------
Root is not working on mine any longer...
I ran the Voodoo OTA Root Keeper and backed up root before doing anything and all 5 checkboxes were green, confirming that I had backed up root...now that I am updated, I went back into Voodoo OTA Root Keeper and Device Rooted and Root Permission Granted are grey...hitting Restore Root says "Voodoo OTA Root Keeper has been granted Superuser Permissions" followed by "root su restored" yet the checkboxes don't change to green, and I can't run anything requiring root because my device "is not rooted."
Please help!
Edit - Also, opening the safestrap apk causes a force close...
I had zero apps frozen, and zero issues applying the update. I did make a complete nandroid backup before updating...
I am sorry, I updated the directions; if you check the way OTA rootkeeper works, you are supposed to temp-unroot BEFORE you apply the update. You are still OK, though. Just re-run the original root exploit and you will get root back. The patch does not prevent the original root method from working.
http://forum.xda-developers.com/showthread.php?t=1522911
Sent from my DROID4 using XDA
omniuni said:
I am sorry, I updated the directions; if you check the way OTA rootkeeper works, you are supposed to temp-unroot BEFORE you apply the update. You are still OK, though. Just re-run the original root exploit and you will get root back. The patch does not prevent the original root method from working.
http://forum.xda-developers.com/showthread.php?t=1522911
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
Ok, re-rooting worked. I also updated my binary SU and reinstalled safestrap. I rebooted and am running another nandroid backup for safety.
Thanks!
Really noob question here... I just got my droid 4 and was going to apply this update, the post says update 219, the file is update 215...?? Will this file take me to 219 or keep me at 215?
Thanks!
Sent from my DROID4 using XDA
A good question deserves a good answer about a really dumb thing:
Motorola names their updates based on the verion that you are coming FROM and not what you are going TO. In a sense, I guess this is because they are incremental updates, or in other words, they each assume the last one was installed. By naming this way, you can always tell what the next update to apply is based on what revison you are currently running with little danger of accidentally missing one because you forget it and messing up your phone.
TL;DR;
It will upgrade you to 219.
Sent from my DROID4 using XDA
Thanks for the prompt reply, I'm used to letting dev put updates into roms and just flashing, never done one this way. I always learn something new in the forums!
Sent from my DROID4 using XDA
Anything worth a crap in this update?
I've looked but can't find anything that would make it worth the trouble.
Sent from my DROID4 using Tapatalk 2

Keep getting partial root... (I've tried at least)

stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
I had same problem tried almost everything and in the last had to flash stock GB to start over again.
guitarplayerone said:
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
Click to expand...
Click to collapse
Flash back to GB and root and then come to CM9 or CM10.
guitarplayerone said:
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
Click to expand...
Click to collapse
Had you tried the rooting method of dr ketan. http://forum.xda-developers.com/showthread.php?t=1329360
guitarplayerone said:
stupid stupid question, but I keep getting partial root (adb su shows # but cannot write to /system)
Root Explorer as well as mount system rw app both cannot mount system as rw
SuperSU binary updates fine
However, what is odd is that I have sucessfully deleted system apps (eg phone.apk), via TIB and they do not run on the phone anymore. I have also occasionally been able to restore them via TIB
I have tried flashing CF-Root LRB via odin, same result.
I have tried flashing Abyssnote42 and then flashing the ROM via abyssnote, but still get partial root.
I don't get it- according to the post in this forum, all I needed to do was flash CF-Root and that should have done it.
I have Mobile Odin Pro, but there are no .tar files which I can find for ICS (everyone is doing CWM releases).
Also, AdAway does not seem to be able to write to the hosts file, which imo seems like it is unable to write to /system.
The very few times TIB has been able to mount /system/app as rw and I have overwritten files, nothing has changed (so it looks like they were never overwritten in the first place).
I want root to be able to write to /system, not use 'kewl root appz'. (Trying to overwrite phone.apk and contacts.apk)... i've also tried making CWM flashable zips but CWM won't flash them...
I have been able to get GB full root by flashing pre-rooted stock, this is all for Kingdroid ICS 4.0.4
Am I missing something? Can CWM install a rooted kernel? Should an Odin flash of a rooted kernel get full root? Sorry for the dumb question, but I really tried
Click to expand...
Click to collapse
Last few months ago im also having the same problem. No matter which method i had try..dr.ketan...start from gb...no luck at all. The partial root problem still remain.
Luckily i met someone to gv me help. And his method 100% works.
Please report back if u able obtain full root. Other wise i will gv u the proper step to obtain full root.
Good luck
Sent from my GT-N7000 using xda premium
Maybe the problem lies with busybox. Try getting busybox binary updated. I've read some people can do it by installing busybox from Google Play. For my case usually I inject busybox directly via CWM, but it is potentially dangerous so I won't share it here.
When I had this prob, I tried everything bo no luck, so flashed gb again.
Sent from my GT-N7000
lee yun khong said:
Last few months ago im also having the same problem. No matter which method i had try..dr.ketan...start from gb...no luck at all. The partial root problem still remain.
Luckily i met someone to gv me help. And his method 100% works.
Please report back if u able obtain full root. Other wise i will gv u the proper step to obtain full root.
Good luck
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I am having exactly this problem.
I have tried everything over and over and still partial root.
I would REALLY appreciate your help with getting full root on my note.
u need to give more details. what rom are u on?

TWRP, System writing, Supersu, Impossible?

I have had my fair share of problems modifying android before but I have never had a phone flat out lie to me and say an operation was successful and actually nothing happened at all.
Have had my nexus 6 for a year or so now. Have had minor issues rooting / modifying marshmallow in the past but I figured out it was all caused by the system partition having basically 0 free space. Made a huge mistake and installed to the latest 7.0 OTA. Wanted to simply enable tethering and edit the thermal config to not shut cores down. Should be as simple as pulling the files, editing them, pushing them back to the phone in twrp with the system partition mounted and thats the end of it right? Wrong.
First of all twrp 3.0.2 refuses to let me touch the system partition without some giant prompt about how its going to make itself stick and offer to root the phone. Simple enough I have seen it in previous versions I say yes as usual except twrp proceedes to immediately spew a bunch of superuser files that do nothing throughout the system partition without asking me if I want root. Dumb but whatever. I mount /system as read write and I go edit and replace my two files like usual (build.prop and thermal config). No matter if I ADB push or use twrps built in file manager it claims the file replacement is successful. Reboot into android and not only have both files not been touched (Verified by adb pull) but the recovery gets overwritten with the factory recovery anyways. (NEVER had issues with twrp sticking on marshmallow. Now after every reboot it gets wiped out)
Second of all if I select yes to twrp mounting system as writable and it does its spewing as I mentioned before then installing SuperSU instantly causes the phone to not boot. Rewrite the boot.img to factory and it boots fine OR Rewrite the clean factory system image and the SuperSU boot works fine. But modifying /system with twrp and then running supersu at the same time is a no go. TWRP is obviously doing something stupid to system that pisses off supersu so undoing twrps mess or uninstalling supersu makes it bootable again.
I dont even want root! Everyone is claiming you need to run "settings put global tether_dun_required 0" as root along with adding the usual "net.tethering.noprovisioning=true" in the build.prop to get native tethering working again! On 6.X only the build.prop edit was needed to get it working.
So long story short. I just want native tethering to work and to tweak my /system/etc/thermal-engine-shamu.conf . Is there anyone here who has done this successfully on nougat? I feel like its all twrps fault but im far too tired and frustrated to try another version tonight.
You must be running an old version of TWRP. Update to the latest, as the latest no longer offers to root your device for you. The version of superuser included was ancient and caused the device to bootloop.
As to TWRP being overwritten Android 7.0 I believe does that on a stock system. If I recall, there is a script that needs to be modified to prevent it.
Strephon Alkhalikoi said:
You must be running an old version of TWRP. Update to the latest, as the latest no longer offers to root your device for you. The version of superuser included was ancient and caused the device to bootloop.
As to TWRP being overwritten Android 7.0 I believe does that on a stock system. If I recall, there is a script that needs to be modified to prevent it.
Click to expand...
Click to collapse
It's stated in the op he's using twrp 3.0.2.
Didgeridoohan said:
It's stated in the op he's using twrp 3.0.2.
Click to expand...
Click to collapse
I misread his post then. I wonder if perhaps he is running TWRP via fastboot instead of installing it.
Flashing recovery using "fastboot flash recovery XXX.img"

Correct root and TWRP recovery for OOS 4.1.6 on OP3T - please.

I've been all over the OP3T forums looking for current information about the correct versions of TWRP and (Magisk or SuperSU) to use with stock OOS 4.1.6. I kept my old TWRP 3.0.4-1 and when I tried to apply SuperSU 2.79 SR3 I got an unusable system and had to restore from nandroid backup. I updated to TWRP 3.1.1-2 as per the Official TWRP app and now every time I try to reboot to system from TWRP it warns "No OS installed", but the reboot works fine. I have Magisk 13.2 ready to install but I'm reluctant until I know I have the right combination - the TWRP 3.1.1-2 backup is missing some partitions and I want to make sure I can at least recover my system if Magisk screws things up.
I've been all over the forums and all the relevant threads were closed months ago, or are written about OOS 4.0.3 or 4.1.1, or describes some hideous way someone turned their 3T into a pile of molten lava. Is there any current information about what combination of TWRP and a root zip will work with the latest OOS 4.1.6? Everything is stock except the unlocked bootloader. I don't want to flash a different ROM, I don't care about passing SafetyNet, I just want to root and go on with my life.
A couple of numbers is all I ask. I can't be the only one. Please - I've been without root for a week and it's bugging me.
TWRP 3.1.1-2 has got at least one major bug where it reports the OP3T as a OP3. That'll mess up your OP3T specific installations... Don't know if there are any other bugs, since I'm staying on 3.1.1-0 until they fix that bug. You also have the option of using blu_spark's TWRP. I've never tried it, but many users swears by it.
What works for me:
OOS 4.1.6
Franco Kernel r25
TWRP 3.1.1-0 (official)
Magisk v13.2
Magisk Manager 5.0.6
No issues whatsoever (for me)...
Thanks for that. I'd rather not change kernels, though. How likely is it that the same combination works with the stock kernel? Does anyone have that running?
OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."
So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.
Advice?
OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."
So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.
Advice?
Scratch that request. Things seem to be turning around - su works in terminal emulator, lets me ls privileged directories like /data. Root Explorer is working again. The only thing that isn't is AdAway, which can't write the hosts file. Otherwise the system seems to be rooted and working OK.
I'm still nervous that TWRP can't see that there's an OS on the phone, and I haven't seen any other reports of this.
It looks like Magisk can't mount /system read-write. Adaway won't install, and neither will Busybox. Titanium Backup also reports problems. I tried installing Busybox and the installation failed when it tried to remount system /rw.
Will look for solutions to this problem and report back here.
I've found many solutions to this problem, like installing busybox (Stericson Busybox apparently doesn't work in OOS 4.1.6, tried two others. Problem is, busybox will only install into a partition on /system, which requires that /system be read/write.
When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...
JMB2K said:
When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...
Click to expand...
Click to collapse
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.
mobilityguy said:
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.
Click to expand...
Click to collapse
I seem to remember having that problem once before.... Can't recall what I did, I think it involved something with the terminal... I'm not at my desk right now, I'll look into it shortly and see if I can remember
Problem solved. The more I looked at the symptoms, the more I realized that the OTA I took after unrooting with SuperSU corrupted the system partition somehow. The first time I tried applying the OTA with the stock recovery it failed, but I was able to reboot and apply 4.1.6. That's when the trouble began - I was unable to reapply SuperSU. Fortunately I had done a nandroid backup between the upgrade and the attempt to re-root, and after the SuperSU script failed I was able to restore the backup (made and restored using TWRP 3.0.4-1) and continue working. It was either at that point or earlier, during the OTA itself, that /system was damaged - not badly enough to prevent the phone from working perfectly well, but enough to keep TWRP from mounting /system read/write. From that point on I was doomed. None of my other attempts to fix the problem had a chance as long as TWRP was restricted to mounting /system read-only. Then it got worse.
After a semi-failed attempt to install Magisk (rooted applications worked as long as they didn't try writing to /system) I restored my pre-root 4.1.6 backup one more time. After that, TWRP wouldn't mount /system at all, which prevented me from making any more nandroid backups.
It was time to act. I could keep using the phone unrooted, but the longer I went on the more work would be required to put things completely right. The risk would increase because I couldn't take any more snapshots of the phone to fall back to if I munged the device again. I also had a positive reason to fix things - during the two days the phone was rooted but couldn't access /system, Titanium Backup kicked in and did a full backup of all my software and settings.
With a damaged file system and full backups, there was no reason for halfway measures. I copied all my user data off the phone and used LloydSmallwood's unbrick tool to flash the phone back to its original OOS 3.5.4 state. That took care of rebuilding all file structures. As soon as I rebooted, OOS upgraded to 4.1.6 in one step, taking care of the system upgrade. Unlocked the bootloader, installed TWRP 3.1.1-0 (not 3.1.1-2, which has a serious bug for the 3T as someone posted above). I was able to mount and unmount /system from TWRP's mount screen, no problem. Ran Magisk 13.3 script without a problem, installed Titanium Backup, and tested an app restore. No problem. I'm now in the midst of copying all my stuff back onto the phone, after which I'll restore all missing apps and be back in business (I hope).
It's possible I could have done something tricky like reformatting /system and restoring the partition from my last good nandroid backup. But I always would have been concerned that problems would have popped up later, maybe during the Android O upgrade, when it would be way too late to recover my then-current setup. After seeing virtually every combination of working and non-working features, it just made sense to build from a clean system.
So thanks have been given to LloydSmallwood for his absolutely indispensable unbrick tool (this is the second time it has saved my phone). I should also thank my Galaxy S3, running the current build of LineageOS, which has gotten me through the two days it took to set my OnePlus straight. The Galaxy has performed better than a five year old phone running brand-new software should ever be expected to - if it supported LTE I could consider using it as a daily driver. This has been an education, and a reminder of how important it is to keep good backups at every step throughout an upgrade - and routinely during production use.
Thanks to all who gave advice in this thread.

Categories

Resources