I accidently updated my SuperSU in google store, and it required me to update my SuperSU binary. However, I can't update my SuperSU binary because my vol up button is broken...so is there anything i can do, can i just leave it no updating the binary...I have a Samsung S3
You can use either third party apps, such as Quick Reboot, https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot , to reboot into recovery, or, through terminal in a root shell run "reboot recovery", or use adb for " adb reboot recovery", plenty of ways to get into recovery without using hardware keys
Related
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.
CLOCKWORKMOD FOR XPERIA T/TL/TX/V v7 - Linux/OsX bash shell script
I converted in bash this. All credits go to davidmarco.
This is for:
Rooted phones
Locked bootloader
Stock firmwares T/TL/TX/V (JB)
What is working:
Backup
Restore
External SD
Flash zip files
Mount/Unmount partitions
And so on, so apparently all (further testing and feedback will be appreciated)
Note: You must install adb tool on your system (Ubuntu based distro: sudo apt-get install android-tools-adb)
Installing:
Installing CWM for the first time is as simple as:
Download CWM v7 installer and unzip
Enable USB debugging and connect phone to your computer
Run install.sh
Entering CWM:
Disconnect usb cable and power off the phone
Power on the phone
When SONY logo appears:
On Xperia T/TX/TV press repeatedly (not holding) volume-down button until the phone vibrates
On Xperia V running JB try one of these:
Press repeatedly (not holding) power button until the phone vibrates
Tap repeatedly the screen
Wait a few seconds and you will be on CWM
Navigating CWM:
Volume+ for up
Volume- for down
Power button for enter/ok
Unable to enter recovery?
Make sure you have granted superuser permissions to adb shell. Sometimes this occurs when running install.bat for the first time, sometimes not. Best way is open a windows command prompt, enter "adb shell" and then enter "su". Your super user application will ask you for grant permissions, accept and retry running install.sh.
Keep in mind that at the moment installing CWM will broke OTA updates, even if you unroot and/or remove CWM.
CWM4XperiaTV_v7i_JB_shell.zip
What if i flashed back into stock , will the OTA updates not function too ?
or the OTA update will not work when we install CWM ?
thanks for the answer
sony_84 said:
What if i flashed back into stock , will the OTA updates not function too ?
or the OTA update will not work when we install CWM ?
thanks for the answer
Click to expand...
Click to collapse
If you install CWM OTA updates do not work. If you install stock rom with flashtool , CWM is gone and OTA updates works
If you took the 4.4.2 update
and don't want to downgrade
or jump through hoops to get root access back try this.
The fix for this problem is to download lg mobile support tool
on your pc (search in google its the second link)
Click on options-upgrade recovery
Let it download
You will need to plug your phone
In via USB for the last 10 percent
(Your phone will boot into download mode and restart)
You will now be unrooted and able to
Reroot with stumproots brute force (use stumproot not towelroot)
Oh and you will get download mode back
Power off-vol up+ plug in USB
Getting recovery
This part can get complicated if you let it.
Download SuperSU (preferred from chainfires website, download the zip and open with es file manager or root manager I don't care in the folder common you will find the su apk, install it)
Don't open su yet, download the freedom flex apk and install your choice of recovery and reboot
Now open supersu
The binaries will probably fail to download that's OK.
Reboot into recovery if you can't get into recovery use adb
The command is: adb reboot recovery
Now flash that su zip you downloaded from chainfire
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.
I have just bought a new Pixel 5 which came with Android 11. I want to install TWRP, switch it over to crDroid-7, and install Magisk-23.0.
I performed the following procedure, and it seems to have worked just fine, except for the Magisk-23.0 installation. These are the steps I followed, and below this, I describe the problem with Magisk-23.0 ...
(1) Unlock the bootloader
(A) After initializing Android, select Settings and go to About Phone and tap a few times on Build Number until it says that Developer Mode is enabled(B) Select Settings->System->Advanced->Developer options(C) Select OEM Unlocking(D) Exit Settings(E) Attach the USB cable and run this: adb reboot bootloader(F) Run this: fastboot flashing unlock(G) Using the Volume-Up/Down keys, select "Unlock", and then press the Power key(H) Reboot and re-initialize Android
(2) Flash TWRP
(A) When Android is running, push TWRP to /sdcard/ as follows: adb push twrp-3.7.0_11-0-redfin.img /sdcard/
(B) Run this: adb reboot bootloader(C) Run this: fastboot boot twrp-3.7.0_11-0-redfin.img(D) In TWRP, select Advanced=>Install recovery ramdisk(E) Find twrp-3.7.0_11-0-redfin.img on /sdcard and select it, followed by Swipe to install(F) At this point, TWRP be installed. Test it by rebooting into Android and then ...(G) Run this: adb reboot bootloader(H) Using the Volume-Up/Down keys, select ""Recovery mode" and press the Power key; TWRP should come up. Then reboot back to Android
(3) Install crDroid-7
(A) Run this: fastboot flash boot crDroidAndroid-11.0-20220825-redfin-signed-v7.21-boot.img(B) Boot to recovery; this will be the crDroid recovery.(C) Navigate to Factory Reset and then Format data(D) Navigate to Update via ADB and sdeload this: crDroidAndroid-11.0-20220825-redfin-signed-v7.21.zip(E) This should install crDroid-7; reboot and initialize the OS
(4) Install Magisk-23.0
(A) Boot into recovery(B) Sideload this: Magisk-v23.0.zip(C) Reboot and then open up Magisk and configure it as normal.
I succesfully performed the standard Magisk-23.0 install.
However, if do "Hide the Magisk app", Magisk no longer gets recognized when I try to start up any apps that request root, and root is not granted.
If I un-hide the Magisk app on the crDroid-7-enabled Pixel 5, then other apps have no problem requesting and obtaining root.
When I run Magisk-23.0 on my Android 10 OnePlus device, this problem does not occur, and after hiding the Magisk app, other apps still successfully request and obtain root. This seems to be either a Pixel 5 issue or an Android 11 issue.
Any thoughts or suggestions?
Thank you very much in advance.