This is the account of my foolishness and I advice everyone not to follow it.:::
1.installed Linux installer std and complete Linux installer from play store.
2.when the 2nd app failed to unmount and GUI crashed showing some errors with busybox, followed 3rd step.
3. found the embedded busybox from 1st app n directly placed it in /system /xbin
4. the original busybox is gone n everything is fine but got too many errors in reading root directory of phone. None of the file manager is showing me root.
5. I'm suspecting that it has done something wrong with my cwm recovery as well for which I can't take a chance of bricking my phone.
6. NOW I need kind advice of u ppl on how to confirm the presence of recovery.img or whatever it should be to recover my cwm backed up data.
boot into recovery, if recovery do not boot then pull battery and start the mobile it will start normally, download busybox installer from play store (the one from stephen)
install busybox through the app(busybox problem will be solved)
download tass recovery cwm.tar file and flash with odin you will get cwm recovery back
did it
I've already tried busybox installers. non of them worked cause the whole root directory is unreadable to any of my apps except diskusage n similar things those show memory occupied.
then you should flash firmware and root again
Superuser
maybe update superuser binary?
solved
chmod 777 path name n got busybox 1.12
You lost root access because there is no busybox. Reflash the ROM. Easy way out.
nothing lost at all just replaced.
as I've stated the command above u, it was just a busybox w/0 permissions. I was getting permission denied.
thanks to Gael péron for his Help.
Related
I Have installed on MY I9000 the Darky's 9.2 Extreme edition.
Is there a way to reinstall it?
I would reinstall "write and Go" app.
I Have found the apk but when i try to install it by tap directly on apk file the system respond with "Application not installed"
Can anyone help me?
However, the Darky's 9.2 Extreme edition is fantastic.
go to www.romkitchen.org and select create update.zip select all the apps you want and then generate it and flash it thru CWM easy peasy lemon squeazy will take you less than 5 mins.
Thanks a lot . I have downloaded the generated file but the name is update-AiGIQJ8kLa.zip
I need to rename it in update.zip before flashing?
During the generation of update.zip in the rom kitchen site, if i chose "none" in the boot animation step when i flash remain the current boot animation?
Thanks in advance
Sent from my GT-I9000 using Tapatalk
Hi,
I have tryed to install the file generated for the site but i have a problem.
When i install the update vie CWM i read:
Finding update package
opening update pakage
installing update
Then the procedure reamain bloked with the the bar always gray.
I waited 10 minutes then I removed the battery and put back.
The Phone reboot without the new application.
Help me please.
Thanks. Thanks
when you go into recovery mode what does it say ??
does it say something like clockwork mod recovery or does it say something like 'android recovery system <3e>
you need to be on recovery 2e ( clockwork mod) to flash update.zip files.
oh and yes the boot animation will stay intact
I'm in the Clockworkmod Recovery v2.5.1.3 - Voodoo lagfix.
not in 2E. This is the CWM that start automatically when i choose recovery from the reboot pane on the Darky's 9.2 system.
how do I start CWM 2e?
Thanks
Hello I found the solution using adb looking in the forums.
Adb I unmounted and remounted in r/w the partition /system /app.
Then I copied the application from the internal sd to /system/app
I used the following commands ....
adb shell
su
mount -o remount,rw /dev/block/mtdblock6 /system
cp sdcard/xxx.apk system/app
chmod 644 system/app/xxx.apk
where xxx is the name of application . In my case WriteandGo
Thanks
hi all,
I was running my TX with advanced kernel v4, rooted:
http://forum.xda-developers.com/showthread.php?t=1922925
yesterday i installed Miui Security from here:
http://forum.xda-developers.com/showthread.php?t=1663222
Then the root is gone. I checked that /system/bin/su and /system/xbin/su are still there but they are inter-linking with symbolic link when i view them with root explorer.
fixes tried:
When i use ADB push trying to replace them, it said "too many symbolic links encountered"
I cannot remove both file as i cannot su in ADB shell.
I booted into CWM recovery but ADB is not enabled in CWM.
I reflashed the flashable zip in CWM to gain root access with no error message prompted, but after reboot into system the SU files are still the same
I reflashed the kernel with flashtools and fastboot, still no change applied to the phone.
Any idea?
finally got it fixed...
I rewrite the updater-script in the CWM flashable zip for root package to force remove both /system/bin/su and /system/xbin/su and rewrite them back.
Thanks for watching...
I've the same problem
Hi guys,
I've the same problem.
I've flashed my Xperia T with MIUI-3.11.22 rom.
I've activated the root permission on Security tab, but my phone doesn't give me the root access (I've tried to install adbd insecure and BusyBox but the result is "problem with root access".
Some ideas?
Thx
Just got HTC One launch day.
Immediately began work on rooting the phone. Installed TWRP and got root access for the most part, but found that this did not give rw access to the system partition.
Found viperboy's post regarding this issue. When I tried to flash the zip file "Sprint_One_Root_Disable_System_RW_Protection.zip" the phone rebooted. After, SuperSU was no longer installed nor was su for root access. TWRP is now no longer able to flash anything at all. The phone still works fine but I seem to be back to ground zero.
Just hoping someone else has encountered this.
- Update -
Upon further exploring I found that all the files were pushed to the android system and that the su file still exists in /system/xbin/, but There is no longer permission to run said command. I tried manually re-pushing all the files but no change.
It seems if anything (even TWRP) tries to access the system partition the phone reboots.
Hi all,
I am unable to remove supersu and unroot my phone to send it for repair..
After using Full unroot from within SuperSU to unroot my phone then restart as directed but when the phone restarts, I still have supersu installed.
I have manually deleted the SuperSU from /data and SU from /bin and SU from /xbin but when I do a full factory wipe to remove my google account and any other details from the phone, on restart the SuperSU is back........................................
Any advice please.
Thanks all
worf105 said:
Hi all,
I am unable to remove supersu and unroot my phone to send it for repair..
After using Full unroot from within SuperSU to unroot my phone then restart as directed but when the phone restarts, I still have supersu installed.
I have manually deleted the SuperSU from /data and SU from /bin and SU from /xbin but when I do a full factory wipe to remove my googal account and any other details from the phone, on restart the SuperSU is back........................................
Any advice please.
Thanks all
Click to expand...
Click to collapse
Am loosing my hair with this
worf105 said:
Am loosing my hair with this
Click to expand...
Click to collapse
If you originally rooted by flashing superuser or supersu in custom recovery (TWRP/CWM) then superuser.apk and su binary are installed in the system partition and a factory reset will not remove them. Further, attempting to delete them using a file explorer won't work either because the system partition is write protected once the OS boots (they appear to delete, but return on reboot.)
One solution is to remove the root files in custom recovery by flashing the attached zip, it has a script that will delete /system/app/superuser.apk and /system/xbin/su files.
Another solution is to install the RUU for your phone, that will reinstall a fresh copy of the system partition without root files.
cschmitt said:
If you originally rooted by flashing superuser or supersu in custom recovery (TWRP/CWM) then superuser.apk and su binary are installed in the system partition and a factory reset will not remove them. Further, attempting to delete them using a file explorer won't work either because the system partition is write protected once the OS boots (they appear to delete, but return on reboot.)
One solution is to remove the root files in custom recovery by flashing the attached zip, it has a script that will delete /system/app/superuser.apk and /system/xbin/su files.
Another solution is to install the RUU for your phone, that will reinstall a fresh copy of the system partition without root files.
Click to expand...
Click to collapse
Thank you (only wish there is an RUU for 2.24.161.1 VODAP001 as I would really love to get back to stock) will get back to you as soon as I try your solution.
Cheers,
worf105
worf105 said:
Thank you (only wish there is an RUU for 2.24.161.1 VODAP001 as I would really love to get back to stock) will get back to you as soon as I try your solution.
Cheers,
worf105
Click to expand...
Click to collapse
It worked, it worked great, Thanks cschmitt :good::good::good::good::good:
Hello everyone,
I've tried to install SuperSU via TWRP recovery (SuperSU 2.56) but it seems to fail: after I completed the install from zip via TWRP, I chose to reboot.
While booting, before the logo screen, a warning appeared which was saying that "the Device is corrupted and cannot be trusted anymore". Anyway, I tapped on the power button to use the Nexus, and when i went to check the root status with "Root checker" it showed me that the root wasn't applied successfully.
Is there something I can do about removing that warning or any suggestion that anyone can tell me to install properly the root? I don't know what actually went wrong.
I appreciate any kind of answer and I'll thank you all in advance for the attention.
Have a nice day.
P.S. I forgot to mention that I have Nexus 6 with 6.0.1 firmware, MMB29X
jos90 said:
.....
I've tried to install SuperSU via TWRP recovery (SuperSU 2.56) but it seems to fail: after I
Click to expand...
Click to collapse
The corrupt message is normal, when the system is not complete stock.
I think it is better that upgrade to MOB30I in case you have a N6. Upgrade kernel, bootloader, radio and system.
All you need is here: http://forum.xda-developers.com/showthread.php?t=3059493
It concerns a prerooted stock ROM.
I've never ever seen the famous "corrupt" message. I update stock each month by flashing manually, installing TWRP and finally flashing SuperSU from TWRP.
I would suggest doing that with MOB30I and SuperSU v2.71, not the very old v2.56.
That is from the old version of su that you used. The old ones modify system, and you get that message.
Reflash the system partition then use su 2.71.
pet peeve.
I don't like root checker. ... none of them are open source..... why risk giving root access to an unknown app for this one simple check?
Instead download terminal emulator from Jackpal (open source, also available verified against source on Fdroid). Execute the su command, grant access in the popup, and verify the prompt changes from $ to # (that indicates root has been obtained by terminal emulator). Then type exit exit to get out of app. And by the way, you might keep terminal emulator app around after you verify...there's a lot you can do with it.