Hello devs...
I'm working on updating the root update.zip's for the Samsung Galaxy S I9000...
But i can't seem to get it to work.
I will include the old working update.zip and the updated update.zip that doesn't work. I really need some help!
The new update.zip applies but after that the phone doesn't seems to be rooted.
I updated Busybox and Superuser in the (new)update.zip
BackfireNL said:
Hello devs...
I'm working on updating the root update.zip's for the Samsung Galaxy S I9000...
But i can't seem to get it to work.
I will include the old working update.zip and the updated update.zip that doesn't work. I really need some help!
The new update.zip applies but after that the phone doesn't seems to be rooted.
I updated Busybox and Superuser in the (new)update.zip
Click to expand...
Click to collapse
Have you noticed that the old update has both an updater-script and an update-script, but the new update does not? I'm not sure why it would need both, but it makes me wonder if the updater-script is doing anything. I would copy the old update-script into the new update, zip, resign, and try again. Actually, I might even get rid of the updater-script and update-binary. It appears to me that they are just duplicating what the update-script is doing.
Maybe updater-script and update-binary aren't supported? Seems unlikely but who knows...
I know I had a similar problem, but mine stemmed down to there being no 'sh' binary in system.
Try skimming through your recovery.log after applying the update, and do a logcat while trying to use a root feature. Other than that I'm not too sure.
GT9500
BackfireNL said:
Hello devs...
I'm working on updating the root update.zip's for the Samsung Galaxy S I9000...
But i can't seem to get it to work.
I will include the old working update.zip and the updated update.zip that doesn't work. I really need some help!
The new update.zip applies but after that the phone doesn't seems to be rooted.
I updated Busybox and Superuser in the (new)update.zip
Click to expand...
Click to collapse
Where can you find for GT9500?
Related
Ok, so I must admit I am still learning stuff. I have a deodexed KA5 that I would like to post but have been unable to add root to it. I have the su binary in /system/bin and the superuser.apk in /system/app, but when I flash the rom in recovery I get an su symlink error and the installation aborts. Any help would be appreciated. Thank you.
I may not be able to help, but if you post it... we can download and look in there.
I think I might have got it figured out. It has to do with how the update-script is set up and they weren't matching up. Gonna try repacking this and giving it another go. Really want to get this out to ppl.
Yay it boots!
is it odexed or deodexed?
Also, you need the su binary in /system/bin but it also needs to symlink to /system/xbin.
If you're doing an odexed rom, the recent releases haven't had enough room to add root and install busy box and keep everything the same. So you'll need to remove some bloat from the system file (which you can add to the data file) in order to have root with busy box.
hi guys, I have an error that i couldnt find a solution by searching in this forum:
i had a full, stock OLYFR_U4_4.1.83 image SBF'd, rooted it, WIFI&tether enabled and sideloading enabled. Also I believe HDMI mirror AND/OR used the Webtop Mod that doesnt require the docking bay. my problem is now, that i get the OTA update to 4.5.91 (about 161 MB), but at reboot-install i get the error
error in /cache/blur_version.4.1.83.MB860.ATT.en.US.zip
status 7
install aborted
I did the WebTop Restore Mod and I *BELIEVE* its put back to "stock"but I am not 100% sure.
can somebody please point me in the right direction to fix this so OTA can be applied ? In addition are there certain things to be considered that I have used the GingerBreak Mod for Root access before the OTA upgrade to 4.5.91 ?
thx-a-thon
cheers
@
imhaving the same issue! Help please!
If I am not mistaken you cannot pull and apply the OTA via the Software update function if you have modified anything in the /system directory. I had a problem because I changed by bootanimation, which got me in a boot loop when trying to install the update. I ended up unlocking via pudding and flashing the 2.3.4 update... You could also update via MSU (Motorola Software Update) via the Motorola Support site..
Edit: Are you using Stock recovery to try to install the update?
Im getting the same error, i think it's because i messed with the bootanimation.zip to remove the default at&t logo... How do I restore that damn logo?
The name of the file which the install/update fails on is in the error. Replace it with the stock apk and you'll be good. It helps to know what mods modified what system file apk's so you can reverse the changes. dockservice.apk, the odex files and portalapp.apk all stopped me from updating OTA; but once I restored factory apk's in the system app path I was good to go.
http://forum.xda-developers.com/showthread.php?t=1163342&page=1
use that .zip to extract any files that you modified. I don't know if that will work but you can try.
It will work as long as all the modified apks are replaced and it is made easier by the fact the ota update tells you which apk or odex file is failing the install.
Sent from my MB860 using Tapatalk
Hi, when installing Busybox with Stericsson Installer it allow to choose between system/bin or system/xbin to install it, which one to choose and why ? What's the difference ?
I have another question, sorry but I don't want to make another thread.
SuperSU has an option "Survival Mode" that says that we must disable it before Nandroid Backup, what happends if I forgot to disable it ?
Thanks for your help, sorry if it was already asked (search results didn't help me).
For the installation paths, i dont really think it matters whether you put it in either of the above.
About survival mode, again i say it does not really matter whether you disable it or not. Your nandroid backup will go smooth.
Some developer can explain it to you in detail if any of the above really matters.
Sent from my LG-E730 using Tapatalk 2
Ok, thanks.
If anyone has more infos your welcome.
I always install to /system/xbin because you then don't overwrite the symlinks of the tools that point to toolbox (Android's poor version of coreutils). On the other hand, if you'd rather have the Busybox tools as default then install to /system/bin.
Regarding survival mode: AFAIR file system corruption (at least with my U8800pro) because CWM doesn't know how to remove the immutable attribute off the su binary, so I'd make sure it's off when restoring.
qwerty12 said:
I always install to /system/xbin because you then don't overwrite the symlinks of the tools that point to toolbox (Android's poor version of coreutils). On the other hand, if you'd rather have the Busybox tools as default then install to /system/bin.
Regarding survival mode: AFAIR file system corruption (at least with my U8800pro) because CWM doesn't know how to remove the immutable attribute off the su binary, so I'd make sure it's off when restoring.
Click to expand...
Click to collapse
Neither in htc wildfire nor in lg optimus sol disabling the survival is important. I have flashed and restored a hundred times but nothing happened..
Sent from my LG-E730 using Tapatalk 2
Well, I think this is definitely new so I put this right here: just downloaded Stericson's BusyBox Pro installer from Play Store (as usual) to my Moto X Play on 6.0 Marshmallow and it is asking for the unusual default installation path of "/su/bin". As discussed here, "system/xbin" or "system/sbin" are usually the preferred installation paths for BusyBox, so this change simply got me stuck in the process thinking where to install BusyBox. My first thought is that BusyBox is 'auto-choosing' where to be installed according to system characteristics and I should go on, make my life easier and just install where it is asking me to, but... I don't know. Does somebody have a similar experience?
CNK80Q3MX said:
Well, I think this is definitely new so I put this right here: just downloaded Stericson's BusyBox Pro installer from Play Store (as usual) to my Moto X Play on 6.0 Marshmallow and it is asking for the unusual default installation path of "/su/bin". As discussed here, "system/xbin" or "system/sbin" are usually the preferred installation paths for BusyBox, so this change simply got me stuck in the process thinking where to install BusyBox. My first thought is that BusyBox is 'auto-choosing' where to be installed according to system characteristics and I should go on, make my life easier and just install where it is asking me to, but... I don't know. Does somebody have a similar experience?
Click to expand...
Click to collapse
I am having the same question.. I have viewed each of the 4 directories using a root file explorer and noticed /bin /xbin and su/bin su/xbin all contain ifferent files so im not sure if doing that helped me o confused me more. Lol but im not sure it matters ,well im sure it makes differences but I cant find a difference other than some symlinks may be rewritten and handled by busybox instead of androids tool box.... Once again that means nothing to me without knowing what exactly androids tool.box is... I know a couple tool boxes but unfortunantly this is not one, ... So if anyone has a link to explain this or an educated opinion that would be great! Thanks..
Also looking for this answer rn.. haven't found it yet.. this is my first look, from experience I believe MM build is recognized and BusyBox recommends install location based on Android Version. I'll look for a more definitive answer and post if I find.
Shagerty said:
Also looking for this answer rn.. haven't found it yet.. this is my first look, from experience I believe MM build is recognized and BusyBox recommends install location based on Android Version. I'll look for a more definitive answer and post if I find.
Click to expand...
Click to collapse
UPDATING: I'm wondering that being MM, Busybox installer chooses su/bin path automatically (some suggest "su/xbin", which is not present in stock MM, hence installer su/bin choice) in order to make Busybox "systemless". SuperSu actually does the same. Though I'm pretty sure about this, I'm also looking for confirmation. Since this thread and its early answers even date back to 2012 when there was no MM and "systemless" stuff wasn't that popular (I assume) they point to install Busybox in "system/xbin" or "system/bin"...
babylonbwoy said:
Hi, when installing Busybox with Stericsson Installer it allow to choose between system/bin or system/xbin to install it, which one to choose and why ? What's the difference ?
Click to expand...
Click to collapse
It really doesn't matter where you install either system/bin or system/xbin.........it always symlink to other as example if you install to system/bin then it'll symlink to system/xbin and vice versa
Mainak007 said:
It really doesn't matter where you install either system/bin or system/xbin.........it always symlink to other as example if you install to system/bin then it'll symlink to system/xbin and vice versa
Click to expand...
Click to collapse
I think it's a little bit too late, thread is from 2012.
I'm done with all that now, no more flashing rom, no more bootloader unlock.
I used to get all the flagship but I didn't change since XZ5 Dual.
babylonbwoy said:
I'm done with all that now, no more flashing rom, no more bootloader unlock.
I used to get all the flagship but I didn't change since XZ5 Dual.
Click to expand...
Click to collapse
Why??.......do you frightened of bricking device??????
You can get all smartphone firmware Here
:highfive::fingers-crossed:
babylonbwoy said:
I think it's a little bit too late, thread is from 2012.
Click to expand...
Click to collapse
And I gave the answer for other who will visit the forum next time:angel:
Mainak007 said:
And I gave the answer for other who will visit the forum next time:angel:
Click to expand...
Click to collapse
thanks, I'm currently looking for pros and cons of intalling to:
/system/xbin
/system/bin
/sbin
custom path
I've read that one of those paths was temporary installation and that on next reboot it would be deleted. I want to installit permanent.
Robert4321 said:
thanks, I'm currently looking for pros and cons of intalling to:
/system/xbin
/system/bin
/sbin
custom path
I've read that one of those paths was temporary installation and that on next reboot it would be deleted. I want to installit permanent.
Click to expand...
Click to collapse
Doesn't matter..... Install anywhere and symlink to others
Mainak007 said:
Doesn't matter..... Install anywhere and symlink to others
Click to expand...
Click to collapse
Just install it to any folder in $PATH and execute it as any other command.
Code:
echo $PATH
Robert4321 said:
thanks, I'm currently looking for pros and cons of intalling to:
/system/xbin
/system/bin
/sbin
custom path
I've read that one of those paths was temporary installation and that on next reboot it would be deleted. I want to installit permanent.
Click to expand...
Click to collapse
Banking / payment apps are looking in 3 mentioned paths to detect whether Android got rooted or not: hence best is to install BB to custom path.
BusyBox Pro says that it can is unsuccessful at installing in the /system/xbin folder on my Moto G Stylus 5G, I don't suppose anyone could explain to me why this keeps happening could they? Also, I don't have the option to install to /system/sbin either. The only options I have are /system/xbin, /system/bin, and custom. But when I install and reboot i have to reinstall BusyBox Pro again. I noticed in the settings tab that you can have busybox, on every boot, reinstall to /sbin....how is this possible if you install to /bin? also, how can I get it to install to /xbin? there is also another option that says busybox will, on every boot, be removed from /sbin as long as busybox has been installed to /bin or /xbin, but the feature I'm speaking of assists kernels that re-install busy box to /sbin on every boot.....OMG!!! Which option do I choose? Or should I not choose any, and just reinstall each time i boot up, which will be very tedious.....Please HELP!!!..... Also, should I choose Smart Install? Or just use install without the Smart Install option ticked? Sorry I see there are similar posts here, but I don't really understand where I would install if i chose to install to a custom path, which is why I'm asking such questions if it seems repetitive I apologize. Thanks in advance!
Hi everybody. I learned so much from this forum (and also from others) in one year and tried to share my knowledge to those who try to learn like me.
Now i would like to share one of my experiences. i dont know if someone wrote about this, yet i could not find anywhere in this forum. When we share a "port" for example "s4 keyboard for s3", we say that we need root access in order to use this port. But when i think, if this apk files replace themselves with the original ones and rom thinks that they are the originals, why should we need root access? Of course we need recovery to flash them but do we absolutely need root? And i flashed 3 separate ports (keyboard, launcher and callrecord) into a fresh installed 4.3 MK6 stock rom without root and they worked... and still do... (scripts have to delete odex files automatically)
Installing a recovery will increase the binary counter and since your binary is up why not rooting right? But those who dont want to root their phone but still want to use the visuality, can install a recovery and flash the ports without rooting... Tested and proven...
You need root access for applications/ports that will need to be installed in system directories (that only the superuser can alter). Some directories/partitions are read-only, so you have to mount the them as writable too. It all depends on the application.
alex.sg said:
You need root access for applications/ports that will need to be installed in system directories (that only the superuser can alter). Some directories/partitions are read-only, so you have to mount the them as writable too. It all depends on the application.
Click to expand...
Click to collapse
If editing apps from rom then yes. But if you are flashing them through recovery you dont need root access for read and write permitions. Script also does that itself. Thats what im talking about
Galaxy S3 tapatalk 2 ile
As you may know, there's a well-known Android 5.0 Lollipop issue - Memory leak.
Lots of community built ROMs out there has already applied the "supposed" fix.
Why not our LG G Watch?
For such devices which has a very long uptime, memory leaks are critical.
This "fix" should benefit to a "stabler" LG G Watch
Just throw the attached "services.jar" on /system/framework and reboot.
It'll rebuild all of the ART caches, so the initial boot after applying may take up to 15 minutes.
<Tested on Android 5.0.2 Lollipop build>
V2 - Support for Android 5.0.2 Lollipop build
Memory leak patches taken from
https://github.com/temasek/android_frameworks_base/commits/cm-12.0/services/core/java/com/android/server/display
Thanks to @temasek !!
Hello arter97. Thanks for your support. Could you please be so kind to tell us how to do it?
For your information, I am currently on Gohma 2.3 and to tell you the truth, with the wear mini launcher running on the background, the g watch sometimes feels unresponsive.
Thanks again for your patience
Does this require root
Hey is there anyway that you might be able to make a flashable zip so we can install it with twrp? Please
ewalk4866 said:
Hey is there anyway that you might be able to make a flashable zip so we can install it with twrp? Please
Click to expand...
Click to collapse
Let me see what I can do. I tried adb pushing the file into /system/framework/ myself, but kept running into read only issues.
Apoplectic1 said:
Let me see what I can do. I tried adb pushing the file into /system/framework/ myself, but kept running into read only issues.
Click to expand...
Click to collapse
Make it with TWRP also Recovery
sallto said:
Make it with TWRP also Recovery
Click to expand...
Click to collapse
And here we go.
https://drive.google.com/file/d/0B7r1gfrm1vXoYVJzVEdkYjNEUTg/view?usp=sharing
Great thank you
Can someone please post instructions for getting the zip file on to the watch so that it can flashed by TWRP. Or how to move the services.jar to the proper location on the watch with correct permissions. I have already searched the threads, however all I can find are how to sideload apps not move files.
*Update* Finally found what I needed, so here it is.
adb push services.zip /sdcard/services.zip
Moguledyouth said:
Can someone please post instructions for getting the zip file on to the watch so that it can flashed by TWRP. Or how to move the services.jar to the proper location on the watch with correct permissions. I have already searched the threads, however all I can find are how to sideload apps not move files.
*Update* Finally found what I needed, so here it is.
adb push services.zip /sdcard/services.zip
Click to expand...
Click to collapse
That's the one, though I usually do adb push services.zip /sdcard/Download/services.zip, but it makes no difference whether it's in the sdcard, or a subdirectory.
Great job guys, my watch is finally usable again, thanks a lot @arter97 for making this and @Apoplectic1 for making it a zip so it is easier to apply the mod.
Do we still need this file if we're on 5.0.2?
arter97 said:
As you may know, there's a well-known Android 5.0 Lollipop issue - Memory leak.
Lots of community built ROMs out there has already applied the "supposed" fix.
Why not our LG G Watch?
For such devices which has a very long uptime, memory leaks are critical.
This "fix" should benefit to a "stabler" LG G Watch
Just throw the attached "services.jar" on /system/framework and reboot.
It'll rebuild all of the ART caches, so the initial boot after applying may take up to 15 minutes.
<Tested on Android 5.0.1 Lollipop LWX48P build>
Memory leak patches taken from
https://github.com/temasek/android_frameworks_base/commits/cm-12.0/services/core/java/com/android/server/display
Thanks to @temasek !!
Click to expand...
Click to collapse
@arter97 is this fix also available for Nexus 5? I've used this - isn't it enough?
Thanks
Thank you! I'm waiting for an updated Ghoma release as I didn't see any sense in returning to stock to do the ota update, while it works its very smooth for me, in the mean time we'll see if this solves my crash about every-other day issue.
FYI if you're having trouble pushing the file directly to /system/framework I'd recommend placing it somewhere that doesn't require root privs to write to, such as /sdcard/Download and then doing an adb shell, su, remount system, and copying it from there into /system/framework. Make sure you back up your current services.jar in case something goes wonky.
--edit-- ERROR: caused watch to fall into a completely unresponsive state, though the time was still updating. Had to connect to usb and force a reboot with adb to break it out of whatever happened. Don't have time to diagnose further right now, reverted to stock services.jar for the moment. I'm not saying this is a general issue with this mod yet, just that it didn't work on my watch.
New V2 for 5.0.2 is now up.
Im getting "read only file system" or something like that. Also cant get it to work with su commands. I'd appreciate if someone will make flashable zip for 5.0.2 update (im currently on stock recovery, but it can be changed easily with g watch tools)
Actually i made flashable zip myself (not sure if correct, but it worked). But considering fact that first "services.jar" which was uploaded for older version should replace file by same name in system/framework, shouldnt newest version be called "services" also? Now i ended up having in my framework folder "services_v2.jar" AND "services.jar". Should i rename this one with "v2"? Or is it intended to leave both of them?
Lasiu said:
Actually i made flashable zip myself (not sure if correct, but it worked). But considering fact that first "services.jar" which was uploaded for older version should replace file by same name in system/framework, shouldnt newest version be called "services" also? Now i ended up having in my framework folder "services_v2.jar" AND "services.jar". Should i rename this one with "v2"? Or is it intended to leave both of them?
Click to expand...
Click to collapse
It's only services.jar. Rename the new one.
Thanks @arter97! Looking forward to a more stable 5.0.2!
buru898 said:
It's only services.jar. Rename the new one.
Click to expand...
Click to collapse
Thats what i did, working great, thanks! Do any of you by any chance know how to stop ota notification from appearing? (i tried going back to 5.0.1 after installing 5.0.2 but this notification appeared again )