Related
Hi All,
I am trying to Unlock my Samsung Vibrant phone which is updated to version 2.2.
When i try to install Busybox installer app which was downloaded from market, it is giving the error "Failed to install busybox!"
When i search in google somewhere it mention for Android v2.2 i need to install Busybox installer v1.2 but when i downloaded from maket i am getting v1.19.
how to download Busybox v1.2 (googled, but didnt get correct link) or install busybox v1.9 in Androidv2.2?
or is there any method to unlock phone with out using busybox?
Thanks in advance.
chsundar said:
Hi All,
I am trying to Unlock my Samsung Vibrant phone which is updated to version 2.2.
When i try to install Busybox installer app which was downloaded from market, it is giving the error "Failed to install busybox!"
When i search in google somewhere it mention for Android v2.2 i need to install Busybox installer v1.2 but when i downloaded from maket i am getting v1.19.
how to download Busybox v1.2 (googled, but didnt get correct link) or install busybox v1.9 in Androidv2.2?
or is there any method to unlock phone with out using busybox?
Thanks in advance.
Click to expand...
Click to collapse
Had the same issue when I tried to root my stock 2.2 Vibrant.
Busybox has to be installed somewhere in /system, I believe. The version of 2.2 that Samsung Kies installs, however, has /system packed completely full of bloatware, so there's no room for busybox.
What worked for me was to root with SuperOneClick, then reboot my phone. That got the Superuser app working, so I could use a file manager (I used Super Manager) with root privileges to go into /system and delete some of the bloat to make room for busybox.
An alternative choice is to just flash something else, instead of sticking with a rooted stock 2.2 firmware. As far as I know, all stock 2.1 builds have room in /system for whatever you might need to put there.
let me try to install file manage and clean some unwanted files and try again...
chsundar said:
let me try to install file manage and clean some unwanted files and try again...
Click to expand...
Click to collapse
I used Super Manager for the job, but I think about any file manager that can use root privileges would work.
Be sure to only delete bloat. Stuff like Sims 3, Amazon mp3, Slacker Radio, that sort of thing. Those are really just apps, and have no business being in /system. They're only put there because T-Mobile didn't want us to be able to delete the bloat they were paid to pre-load onto our phones. /system also holds all sorts of stuff your phone needs to work properly, so you can end up forced to Odin to stock if you delete stuff that's not bloat.
http://forum.xda-developers.com/showthread.php?t=925400 is the thread that I followed to get root working on my previously stock 2.2 Froyo Vibrant. It's /system/app that you need to clean up bloat from.
Thanks i could delete unwanted apps and free up some space in system folder. I could unlock my phone and use AT&T sim.
Hello,
I wish to install (and use) the application DME Excitor (corporate emails) but it is detecting the root in some way.
I have a i9100 device with cm9.1 (latest stable one) & siyah kernel 5.0.1.
I've also made sure (using ExTweaks) that the kernel is not re-rooting the device every boot.
I've tried to remove the root using "Hide my root" / "ExTweaks" / "SuperSU" - and others that say they will hide the root - so far with no success!!!
Can you please suggest how to prevent DME from detecting my root?
I really don't mind unrooting the device - but please do not suggest me to return to stock!
Any help will be highly appreciated! :good::good::good:
bump
bump
any luck? i have the same problem, only worst, i need to use dme on n7, and without root i can't have android stock browser, which makes my device half usable from my pov...
florox said:
any luck? i have the same problem, only worst, i need to use dme on n7, and without root i can't have android stock browser, which makes my device half usable from my pov...
Click to expand...
Click to collapse
sorry - no success yet
In case you find any way, please let me know
In my case it was a combination of:
1. Install SuperSU only on /data, not on /system - there's an option for that in SuperSU
2. Uncheck "Enable Superuser" in SuperSU settings
3. Reboot device
bkraptor said:
In my case it was a combination of:
1. Install SuperSU only on /data, not on /system - there's an option for that in SuperSU
2. Uncheck "Enable Superuser" in SuperSU settings
3. Reboot device
Click to expand...
Click to collapse
Did you tried it with DME ?
By default, installing the SuperSU from the play store is in '/data' (you can later change that option in settings to be set on '/system')
Anyway, tried that, didn't worked.
Any help would be highly appreciated. :good:
I wouldn't have posted the solution above if I hadn't tried it first with the program in question (DME). Make sure there's no /system/app/Superuser.apk (by installing SuperSU / Superuser only on /data) and also make sure to uncheck the "Enable Superuser" option within SuperSU.
bkraptor said:
I wouldn't have posted the solution above if I hadn't tried it first with the program in question (DME). Make sure there's no /system/app/Superuser.apk (by installing SuperSU / Superuser only on /data) and also make sure to uncheck the "Enable Superuser" option within SuperSU.
Click to expand...
Click to collapse
Hi,
First of all thanks for trying to help.
There's no any Superuser.apk in /system/app/ (that's the first thing I've checked).
And I did made sure to uncheck the "Enable Superuser" option within SuperSU.
Still doesn't work.
If you don't mind me asking, could you please provide me with more details on your firmware?
Which rom are you using (is it Cyanogenmod)?
Special kernel?
CWM ?
Any details would help.
And once again, thanks!
Stock Samsung (XWLSS) firmware rooted via SuperSU CWM method, then uninstalled SuperSU via "Reinstall" option in SuperSU, then install SuperSU from the Play store, then uncheck the "Enable Superuser" option in SuperSU, then reboot. At this point DME will start and ask for credentials.
bkraptor said:
Stock Samsung (XWLSS) firmware rooted via SuperSU CWM method, then uninstalled SuperSU via "Reinstall" option in SuperSU, then install SuperSU from the Play store, then uncheck the "Enable Superuser" option in SuperSU, then reboot. At this point DME will start and ask for credentials.
Click to expand...
Click to collapse
Thanks for the info.
I was afraid that you would note you're using a rooted stock firmware.
The thing is that by going back to stock rom, there's no need to root it and then unroot it to use the DME (simply use the stock firmware unrooted).
The first post on this thread was a question on how to use the DME on different rom than the stock one (such as CM).
After that being said, I would like to thank you for trying, but this didn't help me, since I wish to use the Cyanogenmod rom and DME together.
If you still have any suggestions on how to use the DME with a non-stock rom, I would be more than happy to hear.
I don't see how running CM is any different than running official. You should check that after disabling Superuser from within SuperSU that there is no "su" binary anywhere within the directories in the PATH variable (i.e. /system/bin or /system/xbin).
Is dual booting a stock/cm setup possible, and would that serve as a "workaround"?
Edit...just thought....even if possible, the dual boot kernel would probably give the game away....
Sent from my CM10 powered S2 via XDA Developers App
is there any solution at this point? I have cm installed and i want to use dme on my rooted phone...
finally!!! fully functional nexus 7 ))
meaning stock browser AND DME running
rooted with this method (from stock 4.2.2):
http://forum.xda-developers.com/showthread.php?t=2233852
installed stock browser from here:
https://play.google.com/store/apps/details?id=de.mkrtchyan.aospinstaller
SuperSU settings (many thanks to bkraptor):
http://forum.xda-developers.com/showpost.php?p=42009031&postcount=6
Can someone please let me know how to install superSU in /data. As If I instal UPDATE-SuperSU-v1.51.zip by using PhilZ-cwm6. It is installed by default in /system.
If I install it using Playstore it does the same got installed in /system. and further conflicts with SU installed by PhilZ-cwm6.
Will appreciate any suitable advice
Hello! I recently updated to stock 5.1.1. I have root access and have set SELinux to permissive as well. Problem is I cannot delete system apps or convert them to user apps using ROM Toolbox or any other method. I can freeze them though. Any idea how can i do this???? e.g. Chrome at the moment is a system app I want to delete it...how can I do this on 5.1.1
Thank you in advance
Since 5.1 came out I've been reading a lot of threads & posts of users with semi-root problems. Because you don't have a proper o real root access you won't be able to do much. My advise is "simple": Build yourself a prerooted zip with all the latest software:
23.4.A.0.546 .ftf
PRF Creator v0.9
SuperSU 2.46
XZDR 2.8.21
I don't know if the SELinux thing is the same as modifying the XZDR.prop but I did. This 2 lines are "true": dr.initd.active=true and dr.keep.byeselinux=true
I don't have any root problems, even when installing 5.1.1 from 4.4.2. Other thing I do: After installing the pre-rooted .zip, I flash a "stripped" .ftf: I select all the 3 wipes, No final verification and Reset customizations BUT excluding system. The phone starts "like new" but with fully functional root and recoveries.
If you want to keep your semi-rooted phone but want to delete system apps, use a debloating script. It is like a flashable .zip but will not install anything, just delete whatever you want.
I managed to remove movie creator with the kinguser app that comes with kingroot.give it a try
Sent from my D6503 using Tapatalk
After successfully having flashed the stock firmware for this phone, installed TWRP, and installing the Xposed framework, I thought I would share what I did.
First, I ODIN'D the 4.4.2 firmware, generously hosted by Tsar3000 at:
http://www.tsar3000.com/Joomla/inde...ini AT&T Firmwares&catid=55:samsung&Itemid=82
Secondly, I used kingoroot apk to root the phone, which worked the first time.
EDITED PART: you need to download SElinux changer and set it to permissive after rooting and before doing anything else.
Third, I downloaded the safestrap(TWRP) apk for this phone at:
https://www.androidfilehost.com/?fid=24499762636000015
And then, the Xposed Installer:
http://repo.xposed.info/module/de.robv.android.xposed.installer
Then finally, I used the recovery flashable zip to install SuperSU(Version 2.79):
http://www.supersu.com/download
EDIT TWO: BEFORE DEBLOATING, USE SAFESTRAP TO REBOOT TO RECOVERY THEN BACKUP YOUR ROM. I was able to use System app safe remover to get the total down from over 200 to 48 apps with no failure. Be careful though.. Removing certain key modules is causing home button malfunctioning after removing.
From there, use System App Safe Remover to remove Kingoroot and it's own SuperUser app.
FOR SCREENSHOTS, CHECK ATTACHMENTS.(taken after I de-bloated)
System App Safe Remover
I followed all the steps as stated in the OP with great success, but the only part I'm confused about is the System app remover utility. Is that found on the Play Store, or is it built into the Superuser app we flash in the recovery. You'll have to forgive me I am pretty rusty when it comes to Android. It's what happens when you become dependent on iOS for so long.
yes, stock is a ROM. based on a few past handsets, the customized / debloated stock ROM is the way to go. i'm by no means an expert, but not finding a thread for it, decided to make one. if you found your way here, you're welcome to discuss issues you're facing, whether it be magisk, xposed, debloat, whatnot. needless to say i'm just a punter, not the dev.
mine is NPP25.137-15 cedric, but i assume most of the issues arising are the same across the stock builds.
NPP25.137-33 is downloadable here.
https://mega.nz/#!jcp0UCiS!1EXQUYdNftgRrHsdBvmsmn4e_IZy3GtytOaoET9Kjm0
disclaimer: anything you do is between you and your gadget.
XDA:DevDB Information
[ROM][semiOFFICIAL][7.0] rooted stock [magisk], ROM for the Moto G5
Contributors
zdoe
ROM OS Version: 7.x Nougat
Based On: stock
Version Information
Status: Stable
Stable Release Date: 2017-01-01
Created 2017-12-18
Last Updated 2017-12-19
anyone got xposed working on this?
for me, xposed-v88.2-sdk24-arm.zip installs ok, but the modules don't see it. what i need most is the appopsxposed module.
Download link? Features?...
Fedray said:
Download link? Features?...
Click to expand...
Click to collapse
The link Is there
It's only a stock ROM without junk apps and pre-rooted
this thread is not a true DEV-thread - but one to disuss issues in using stock ROM
peter9811 said:
The link Is there.
It's only a stock ROM without junk apps and pre-rooted
Click to expand...
Click to collapse
this thread is not a true DEV-thread - but one to discuss issues in using stock ROM. there's a download link to one version of it. haven't tried to install it though, but there's guides on the net if you want/need to do so.
however, the link's ROM is from motorola, it's not debloated, and rooting is a separate matter - guides are again foundable for that.
thanks for this, but we already have a thread with stock rom, how to install it and root is there...so the firmware from your link is the stock firmware, not rooted or something. I think this thread is useless
look here
Can i flash it with TWRP?
Cricamju said:
Can i flash it with TWRP?
Click to expand...
Click to collapse
i believe you can't flash with TWRP - but using ADB and a handful of different command lines.
this thread may give you pointers.
i don't think anyone has made a flashable zip (yet).
good
@showlyshah, could we have a conversation here about upgrading magisk to latest. i'd sent you a PM, but the msg thread would help others as well...
How to install this ROM?
I'm noob.
Thx
zdoe said:
@showlyshah, could we have a conversation here about upgrading magisk to latest. i'd sent you a PM, but the msg thread would help others as well...
Click to expand...
Click to collapse
ok - i bit the bullet and upgraded magisk to 15.2 and the latest magisk manager.
root is ok, but various applications say that busybox is not installed - and stericsson's doesn't install. however, it seems that apps requiring busybox are still working. @showlyshah is your busybox ok?
lcosta2 said:
How to install this ROM?
I'm noob.
Thx
Click to expand...
Click to collapse
RTFF for a link to installation instructions. but likely you already have stock - that's what you got when you bought your phone.
zdoe said:
ok - i bit the bullet and upgraded magisk to 15.2 and the latest magisk manager.
root is ok, but various applications say that busybox is not installed - and stericsson's doesn't install. however, it seems that apps requiring busybox are still working. @showlyshah is your busybox ok?
Click to expand...
Click to collapse
No.. since magisk module for busy box wont install.. i did install it via busybox installer.
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
showlyshah said:
No.. since magisk module for busy box wont install.. i did install it via busybox installer.
Click to expand...
Click to collapse
And i got working busy box. If you find problems with magisk installer app.. install with twrp installer. Btw. It didn't trip safety net..
showlyshah said:
No.. since magisk module for busy box wont install.. i did install it via busybox installer.
And i got working busy box. If you find problems with magisk installer app, install with twrp installer. Btw. It didn't trip safety net..
Click to expand...
Click to collapse
i'm now on 15.3 magisk & 5.5.5 magisk manager. for me, it installs seemingly OK using the magisk-busybox installer script, both from the magisk manager & from recovery. stericsson busybox installer fails to install.
but the end result is the same, terminal reports "busybox: not found" and TWRP manager that it's not installed.
but there's a busybox folder at /sbin/.core/busybox - and apps needing it seem to work.
zdoe said:
i'm now on 15.3 magisk & 5.5.5 magisk manager. for me, it installs seemingly OK using the magisk-busybox installer script, both from the magisk manager & from recovery. stericsson busybox installer fails to install.
but the end result is the same, terminal reports "busybox: not found" and TWRP manager that it's not installed.
but there's a busybox folder at /sbin/.core/busybox - and apps needing it seem to work.
Click to expand...
Click to collapse
If apps cant find it.. it is not symlinked.. busybox is a swis army knife.. that means.. it is capable of doing most of the fuctions of various modules by its own.. normally.. apps need to use these modules ( binaries ) for doing things.. for example.. if there is a zip application.. it uses the "zip " binary to work out.. dns.. etc are some another modules..
In case of busy box.. most of these binaries are coded into that single busybox binary.. and its much less heavy on system.. and thats why some developers use it for different functions rather than using several individual binaries to accomplish the same..
The benifit is.. you only need to load a single binary .. but if individual binaries are called. Then all of these binaries will have to load and unload.
So... In a busybox installer.. there is a script that points to busy box binary.. from its normal individual binary. Its called symlink. I mean.. if you properly symlink a busybox .. and then if an app calles for a binary.. eg.. zip binary.. the system will point that call to busybox binary and not zip binary.
Also busy box binary is more reliable as it gets upadtes more frequently than normal binaries.. its bit more stable and low on hardware resources usage.
So.. what i am saying is.. even if busybox binary is installed on system.. but if it is not properly symlinked.. the apps cant find it out..
That is the problem.. thats why i said.. find the latest twrp flashable busybox.. busybox installer cant install busybox in magisk installed system. Simply because magisk use its own binary folder and not normal xbin or bin folder.
In twrp.. the installer just install busybox into xbin and symlink it properly.. so its the only working way for f2fs error phones like moto g5 and others ( where magisk module wont work)
showlyshah said:
If apps cant find it.. it is not symlinked.. busybox is a swis army knife.. that means.. it is capable of doing most of the fuctions of various modules by its own.. normally.. apps need to use these modules ( binaries ) for doing things.. for example.. if there is a zip application.. it uses the "zip " binary to work out.. dns.. etc are some another modules. ... In twrp.. the installer just install busybox into xbin and symlink it properly.. so its the only working way for f2fs error phones like moto g5 and others ( where magisk module wont work)
Click to expand...
Click to collapse
thanks for the busybox explanation, illuminating, even if i kinda knew - have seen/used it on various linux-based boxes before (mostly routers). but yes, i'm still a noob.
as i stated at https://forum.xda-developers.com/apps/magisk/module-magic-folder-binder-t3621814/page85#post75191777
, the @VR25 magic fmount now installed for me (the f2fs-loopback-bug-workaround-2018.1.1-NOMOUNT version). as did the magisk module busybox installer. so i assume i'm now good, and wonder why your situation is different.
i'm kinda psyched - if magic fmount works, the ROM is finally ready for prime time / actual use. thanks google for making it this hard.
zdoe said:
thanks for the busybox explanation, illuminating, even if i kinda knew - have seen/used it on various linux-based boxes before (mostly routers). but yes, i'm still a noob.
as i stated at https://forum.xda-developers.com/apps/magisk/module-magic-folder-binder-t3621814/page85#post75191777
, the @VR25 magic fmount now installed for me (the f2fs-loopback-bug-workaround-2018.1.1-NOMOUNT version). as did the magisk module busybox installer. so i assume i'm now good, and wonder why your situation is different.
i'm kinda psyched - if magic fmount works, the ROM is finally ready for prime time / actual use. thanks google for making it this hard.
Click to expand...
Click to collapse
Oh.. hahah.. its not actually google.. its moto.. they choose f2fs ( that too with out full permissions for third party apps) when i dig into it.. i found that the stock kernel wont allow magisk to mount image.
So only ways are..
1) use a third party kernel with proper f2fs patches
2) patch stock kernel with f2fs patches
3) use a different mount partion for magisk. ( Thats what done with the f2fs fix magisk module)
I tried it. Unfortunately. It wont stick after reboot on my stock os.
Btw.. u said u play with routers.. can you tell me a way to access ( with root permissions) on huawei e5577 pocket modem.. mine was locked to some carrier, unlock will never work, so i mixmatched firmware files.. and now its working .. but i have a problem with wifi .. the modem wont connect two devices in 2.4 ghz band.. but it works perfectly on 5ghz band... So i like to dig into its firmware. And check more
showlyshah said:
Oh.. hahah.. its not actually google.. its moto.. they choose f2fs ( that too with out full permissions for third party apps) when i dig into it.. i found that the stock kernel wont allow magisk to mount image.
So only ways are:
1) use a third party kernel with proper f2fs patches
2) patch stock kernel with f2fs patches
3) use a different mount partion for magisk. ( Thats what done with the f2fs fix magisk module)
I tried it. Unfortunately. It wont stick after reboot on my stock os.
Btw.. u said u play with routers.. can you tell me a way to access ( with root permissions) on huawei e5577 pocket modem.. mine was locked to some carrier, unlock will never work, so i mixmatched firmware files.
Click to expand...
Click to collapse
well, moto f'd up on f2fs, but google made the fundamental user-hostile decision to write data onto a hard-to-access partition, not give the user the choice. there could be a per-app menu like for notifications: store data on extSD / intSD.
good rundown on the f2fs bug. but my phone seems to have accepted the @VR25 workaround. (still testing magic fbind). at least the module(s) survive boots. go figure.
routers - don't know enough to help you. much like android - each box has a different set of problems based on hardware / firmware combo. i only buy routers that are known to behave well with opensource firmware.
debloating - anyone? what can we remove from stock ROM?
here is a list that i got from some other moto ROM's thread, assume ours would be (about) the same:
/system/app/3c_main
/system/app/Bug2GoStub
/system/app/com.motorola.android.nativedropboxagent
/system/app/MotGeoFenceSvc
/system/app/MotoSignatureApp
/system/etc/bug2go
/system/framework/com.motorola.android.dropboxhelper.jar
/system/priv-app/3c_checkin
/system/priv-app/3c_devicemanagement
/system/priv-app/3c_notification
/system/priv-app/3c_ota
/system/priv-app/IncrementalUpdates
but i'm sure you can take out more... anyone play with this?
there's a debloater as one of the magisk-modules:
https://forum.xda-developers.com/apps/magisk/module-terminal-debloater-debloat-t3584163
but it doesn't run at least for me - first some permission issue, then "module not found." besides, it only provides an UI for removing apps, it doesn't have any opinion on what to take out.
EDIT: version 8 of the debloater does work. 8.2 doesn't.