root problem after rooting ics(ota update) - bootloader question - Acer Iconia A500

hello , my iconia just updated to ics(ota update). i root my a500 with ics root tool. after that i tried to install the supersu but i get installation failed error. After that i tried the superuser and i saw that i have the 3.0.3.2 version but i cant update. im getting this error : remounting /system as rw fail. any ideas?
My second question has to do about boot loader etc. im confused with all that information..
After the update acording to Acer recovery installer i have 0.03.12 ics version( before update i had 3.1 and cmw recovery installed) . to be able to flash a custom rom i have to change the bootloader with afterota tool? and then just install a the cmw recovery from acer recovery installer?
thanks

giannis-21 said:
hello , my iconia just updated to ics(ota update). i root my a500 with ics root tool. after that i tried to install the supersu but i get installation failed error. After that i tried the superuser and i saw that i have the 3.0.3.2 version but i cant update. im getting this error : remounting /system as rw fail. any ideas?
My second question has to do about boot loader etc. im confused with all that information..
After the update acording to Acer recovery installer i have 0.03.12 ics version( before update i had 3.1 and cmw recovery installed) . to be able to flash a custom rom i have to change the bootloader with afterota tool? and then just install a the cmw recovery from acer recovery installer?
thanks
Click to expand...
Click to collapse
First question. Having root and system rw is not exactly the same, especially with the ICS Iconia tablets. You can use a file manager, like ES Explorer or RootExplorer and try changing the /system to rw.
If you can't get /system rw with the tool you used, try Zero-Nulls rooting tool.
http://forum.xda-developers.com/showthread.php?t=1546593
Next question. Bootloader. If you want to install custom ICS roms, it's advisable to install the Unlocked bootloader and CWM. Reason is, ICS and the stock bootloader, is really a pain when trying to get /system rw. The unlocked bootloader and a custom rom/kernel have the security features taken out, so all you need is SU and don't need anything to get /system rw.
Not to mention the unlocked bootloader has fastboot, and, you can change your boot images.
Some people keep the stock rom, and just change to the modified kernel via CWM for the easy /system rw
Regardless, pay attention to the instructions, and keep in mind, if you are on stock ICS, you have to delete the boot-recovery.p file from /system, or else when you boot to the OS, it will overwrite your CWM.
MD

1)problem with root solved with the es explorer solution. thanks.
2) ok i will install an unlocked bootlader according to afterota tool . thanks

giannis-21 said:
1)problem with root solved with the es explorer solution. thanks.
2) ok i will install an unlocked bootlader according to afterota tool . thanks
Click to expand...
Click to collapse
Yeah, gotta set permissions. Remember to delete that boot-recovery.p file. Before you start doing things. Otherwise, your CWM you install, will get overwritten 1st time you boot into your stock OS.
Write down your UID number, always.
MD

Related

i need help

i was looking and serching for a fix my nexus s , i update from Alpha 13 to ICS 4.0.3 and i lost ither root or SU permicion can someone guime to right way i nedd get to CWM and go to my backups and i can do the rest i try update SU buth i not able to get CWM i just get stock recovery i try update SU from app not root acdsse .
I would think that you need to flash your recovery again. fastboot your recovery .img then flash rom manager after you reboot and you should be ok. do this the same way you did when you originally rooted your phone.
You may need to unlock bootloader, root and install. Official stock ROM erased them all.

[Q] Why no su access after it's rooted?

I rooted my Nexus 7 a few days ago and was able to replace bootanimation. But now I want to replace my new version of bootanimation using Root Explorer, I found I have no super user access (the terminal prompt does not change from $ to # when I type su at the adb shell). The /system is mounted as r/o. I also have the busybox and supersu zip files on the sdcard. Can anyone please tell me what happen here and help me back to su mode? Thanks in advance!!
KJTseng said:
I rooted my Nexus 7 a few days ago and was able to replace bootanimation. But now I want to replace my new version of bootanimation using Root Explorer, I found I have no super user access (the terminal prompt does not change from $ to # when I type su at the adb shell). The /system is mounted as r/o. I also have the busybox and supersu zip files on the sdcard. Can anyone please tell me what happen here and help me back to su mode? Thanks in advance!!
Click to expand...
Click to collapse
I can't see any reason why you'd become unrooted unless you either replace the system partition (via an update or rom change or fastboot flash or whatever) or delete the binary yourself. If you didn't do either of those it could be either a problem with supersu, a problem with the binary, or a problem with your kernel. Try putting the root binary (su) back on the phone and trying again, and if that fails try using SuperUser instead of Supersu. If neither work you may need to do a factory reset and try again.
did you upgrade to 4.1.2? You must have lost root during the process. Just re-root it. I used the toolkit.
cooljais said:
did you upgrade to 4.1.2? You must have lost root during the process. Just re-root it. I used the toolkit.
Click to expand...
Click to collapse
oh, yes!!!! I just upgraded a couple of days ago from JRO03D to JZO54K. THANK YOU!!
I tried re-rooting again (w/o flashing custom recovery) after I upgrade Nexus Root Toolkit to v1.5.4 t support 4.1.2, But get stuck at the message "waiting for your device to finish booting back up." Nexus 7 is at the TWRP mode and can't get out of it. So I reboot to bootloader mode and eventually the toolkit tells me to run SuperSU and Busybox. Still doesn't work since I still don't have super user access. What shall I do next? I know there are still few more steps after the TWRP.

[Q] Update to franco kernel but cannot update SU binaries

Hi All,
Please forgive me for this noob question but I updated to franco kernel a few days ago which i absolutely love how fast it its. The problem I am having is that my superSU binaries will not update and neither with busybox. I do have the toolbox and tried to installed the CWM-SuperSU.zip and still have the error message that the binaries failed to update and SU just closes. Can someone help me? I really want to keep this kernel...:crying:
Thanks again
The kernel has no relation to the applications.
nickd1976 said:
Hi All,
Please forgive me for this noob question but I updated to franco kernel a few days ago which i absolutely love how fast it its. The problem I am having is that my superSU binaries will not update and neither with busybox. I do have the toolbox and tried to installed the CWM-SuperSU.zip and still have the error message that the binaries failed to update and SU just closes. Can someone help me? I really want to keep this kernel...:crying:
Thanks again
Click to expand...
Click to collapse
Hi, nickd1976...
That is most peculiar...
A kernel is part of a boot.img file...(along with ramdisk)... and franco's kernel is one of the easiest to flash, consisting of nothing more than a singular boot.img file.
The boot.img in the franco.Kernel-nightly-r47.zip, can simply be extracted and fastboot flashed...
Code:
fastboot flash boot boot.img
The accompanying updater-script in franco's zip does something similar, when flashing via a custom recovery... (although done slightly differently).
Extract...
Code:
..
package_extract_file("boot.img", "/dev/block/mmcblk0p2");
..
-----------
But the point is this... flashing a kernel is flashing a new boot.img... to the boot partition.
AND IT DOESN'T TOUCH SYSTEM... where the SU binary lives... and thus should have no effect on the SU binary.
If you're having problems with root, it probably has nothing to do with franco...
------------
Here's what I would try...
Get Chainfires SU updater package from here http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip.
Fully unroot, by going to the SuperSU app>>SETTINGS TAB and select the option 'Full unroot, Cleanup for permanent unroot'.
Reboot your tablet as normal. Confirm you are unrooted (by running Titanium or typing 'su' in terminal emulator..).
Reboot your tablet into recovery (CWM/TWRP)...
...reflash Chainfire's SU updater package..
Upon reboot, you should be re-rooted.
------------
In conclusion, I can only say that I have been running franco's kernels for a couple of months now, and I've never had any problems with root at all.
Rgrds,
Ged.

(REQ)Samsung A700YD android 5.0.2 root

Hi everyone,
After my A700YD upgrade to android 5.0.2, I cannot find a feasible solution to root my phone. I have tried the CF root or TWRP recovery of other A700 model but my phone stuck at samsung logo after reboot. Could anyone help me to root my A700YD? Many thanks.
dropbox.com/s/vfcms69qfn0vziq/BL_A700YDZSU1BOL4.tar.md5?dl=0
dropbox.com/s/phmabycaq9d5dm0/recovery.img?dl=0
Could anyone help? You can find the BL and recovery in the above links. New users cannot post link, sorry
Anyone can help?
Install twrp then use supersu v2.65
ashyx said:
Install twrp then use supersu v2.65
Click to expand...
Click to collapse
I have tried some twrp recovery. It can enter the recovery successfully but it cannot boot normally. It stuck at samsung logo.
ashyx said:
Install twrp then use supersu v2.65
Click to expand...
Click to collapse
I've tried to dig more in it, and what I get is
1. The only way I succeed is by using KingRoot, and the method it's using is by exploiting and keeping a daemon background and the su file for calling the daemon. So that means after reboot, root is lost.
3. Replacing KingRoot with SuperSU's su file will lead to a bootloop, same as goes to installing zip by twrp.
4. In the bootloop, logcat shows that it is repeating a particular normal boot process
5. In the bootloop, using adb shell and typing "su" will not get into root, despite su is located in xbin.
6. Busybox functions normally.
Any ideas?
ProtoAES256 said:
3. Replacing KingRoot with SuperSU's su file will lead to a bootloop, same as goes to installing zip by twrp.
Click to expand...
Click to collapse
Incorrect, installing supersu version 2.6x> with twrp will patch the boot image to prevent bootloop on samsung devices.
ashyx said:
Incorrect, installing supersu version 2.6x> with twrp will patch the boot image to prevent bootloop on samsung devices.
Click to expand...
Click to collapse
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
ProtoAES256 said:
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
Click to expand...
Click to collapse
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
pianman said:
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
Click to expand...
Click to collapse
From my current experience, no. The sad thing is I'm not skilled enough to do it myself, and seemly there is no reason that skilled devs are willing to have a head in to this not-quite-popular device.
Btw, you need to format /system partition before you flash the kitkat(well, maybe it works maybe it don't, it's just my experience.)
ProtoAES256 said:
Whether or not the patch applies, it will still stuck in bootloop.
Same thing occured on current BETA supersu
Click to expand...
Click to collapse
Nope, it will only do that if you attempt to replace Kingroot with supersu.
If you apply supersu to a clean stock boot and system partition it shouldn't boot loop.
---------- Post added at 10:16 AM ---------- Previous post was at 10:11 AM ----------
pianman said:
Hi, I'm very interesting to this discussion, because yesterday my a700yd update to lollipop, then I root it with king root, but many app eg. leandroind not function with kingroot, so I use kingroot remove script but i'm occurred in bootloop, so I reflash original kitkat firmware but the phone does'nt work correctly, so I reflash lollipop firmware and all work perfectly. Now I would ask you if there is a functionally root method for a700yd?
Ps:when I do a wipe data in recovery mode, I have an error: E:can't mount /preload.
Click to expand...
Click to collapse
If you have twrp installed I will upload a modified version of SuperSU which will allow systemless root on 5.0.2.
This will patch the boot image and should prevent a bootloop.
ashyx said:
Nope, it will only do that if you attempt to replace Kingroot with supersu.
If you apply supersu to a clean stock boot and system partition it shouldn't boot loop.
Click to expand...
Click to collapse
Weird, I did format my /system, /data and /cache before pushing in stock rom and supersu...
Isn't it sufficient to remove KingRoot?
Edit:
Or did I just messed up something?
ProtoAES256 said:
Weird, I did format my /system, /data and /cache before pushing in stock rom and supersu...
Isn't it sufficient to remove KingRoot?
Edit:
Or did I just messed up something?
Click to expand...
Click to collapse
If you flashed the stock rom that should remove the Kingroot and Super su binaries.
Are you using a stock kernel?
Usually only 5.1.1 and 6.0> need a patched boot.img as Samsung don't use root protection on 5.0.2 firmware.
However never say never and Samsung may may now be using root prevention in the later 5.0.2 kernels.
This means that a patched boot image is required to circumvent Samsung's root prevention.
If you have the boot.img I can patch it manually.
ashyx said:
If you flashed the stock rom that should remove the Kingroot and Super su binaries.
Are you using a stock kernel?
Usually only 5.1.1 and 6.0> need a patched boot.img as Samsung don't use root protection on 5.0.2 firmware.
However never say never and Samsung may may now be using root prevention in the later 5.0.2 kernels.
This means that a patched boot image is required to circumvent Samsung's root prevention.
If you have the boot.img I can patch it manually.
Click to expand...
Click to collapse
here you go, extracted from A700YDZSU1BOL4_A700YDZZT1BOL4_A700YDZSU1BOL4_HOME.tar
https://mega.nz/#!14IE3YoA!mRAhQSJCgZ53r5teACeJGWMwrftIY0g0GvZM0LMX9Kg
Hi everyone!
I found this two files, they are recovery.img and supersu 2.46. I still haven't tested them, because recovery is in img format and it has only the Chinese language. If anyone can help me translate the recovery and convert it in tar.md5 format. I found this 2 files on a700yd chinese forum. Thanks!
Same device platform. So should be compatible.
http://forum.xda-developers.com/samsung-a-series/general/recovery-twrp-galaxy-a7-t3153369
ashyx said:
Same device platform. So should be compatible.
http://forum.xda-developers.com/samsung-a-series/general/recovery-twrp-galaxy-a7-t3153369
Click to expand...
Click to collapse
I wiped my phone again and tried it
Here's my procedure
Wipe everything excluding external storage
reboot to bootloader and odin in stock rom
reboot to bootloader again and odin in twrp
reboot to recovery
twrp pops up patch notification(agrees and applied)
install SuperSU 2.65(stable) via sideload
reboot into system
Bootloop. ):
What does not cause bootloop
Stock ROM
TWRP installed only with stock ROM
What causes bootloop
installing SuperSU just after TWRP install (via zip or sideload)
Other problems
installing SuperSU from TWRP built-in will cause a recovery loop(unable to get past recovery screen)
=========
the recovery works good! (a good news at least)
ProtoAES256 said:
I wiped my phone again and tried it
Here's my procedure
Wipe everything excluding external storage
reboot to bootloader and odin in stock rom
reboot to bootloader again and odin in twrp
reboot to recovery
twrp pops up patch notification(agrees and applied)
install SuperSU 2.65(stable) via sideload
reboot into system
Bootloop. ):
What does not cause bootloop
Stock ROM
TWRP installed only with stock ROM
What causes bootloop
installing SuperSU just after TWRP install (via zip or sideload)
Other problems
installing SuperSU from TWRP built-in will cause a recovery loop(unable to get past recovery screen)
=========
the recovery works good! (a good news at least)
Click to expand...
Click to collapse
Try the supersu version above.
ashyx said:
Try the supersu version above.
Click to expand...
Click to collapse
i just update myphone to new firmware. i see something new eg : About device > "android security patch level"
i have same prolem (myphone boot stuck after flash superuser.zip v2.62-2.72 via twrp). And i try reflash one old boot.img via odin then myphone boot up normally with superuser.
i think the new boot.img make myphone stuck.
Can you please help me patch the new boot.img !?
ps: i'm so sorry for my bad english
https://drive.google.com/folderview?id=0B7uFmNBw-G1QalBCZERkeUpjd0U&usp=sharing
Hi Guys!
I ask you if someone used cf-auto root on this device and it was able to root the phone? Thanks.
hkopenh17071 said:
Hi everyone,
After my A700YD upgrade to android 5.0.2, I cannot find a feasible solution to root my phone. I have tried the CF root or TWRP recovery of other A700 model but my phone stuck at samsung logo after reboot. Could anyone help me to root my A700YD? Many thanks.
dropbox.com/s/vfcms69qfn0vziq/BL_A700YDZSU1BOL4.tar.md5?dl=0
dropbox.com/s/phmabycaq9d5dm0/recovery.img?dl=0
Could anyone help? You can find the BL and recovery in the above links. New users cannot post link, sorry
Click to expand...
Click to collapse
http://forum.xda-developers.com/samsung-a-series/development/galaxy-series-cf-auto-root-t3280406

ADB Sideload SuperSU on encrpyted phone

According to the following post, I should be able to gain root on my encrypted phone.
wgspoelstra said:
Yes, decryption is broken right now. On all versions of TWRP available, that support Oxygen OS 3.x.x, decryption is non-functional.
I have a workaround for flashing zips with an encrypted phone:
Boot into recovery, flash SuperSU over ADB Sideload, reboot phone.
You now have working root. Any zips you want to flash, place them in /system/media folder.
I use Root Explorer for this. When you boot back into recovery, mount /system and navigate to /system/media folder.
This way you can still flash all zips you want without decryption.
Click to expand...
Click to collapse
But I am having issues. Most notably, ADB does not recognize my phone unless I connect while in the OS or in stock recovery. If I connect while using any custom recovery (I've tried Hybrid and a few versions of TWRP), ADB does not list my phone when I run ADB devices. It's also very wonky trying to get stock recovery back on my phone afterwards, but that's a different issue.
While attempting to flash SuperSU when using stock recovery, the command sends the file and the phone begins the "update". It runs for about a second and then I get a "Installation Failed" message on my phone's screen. I've tried many different versions of SuperSU.
My current setup is the latest OOS (3.0.2) and stock recovery. The device is encrypted. My bootloader is unlocked, but I do not have root.
Could someone please help me out here? I have to have encryption on the phone for my work, but I really want to have root as well. Being able to customize my phone is why I went with OnePlus, but it's not proving to be any better than my Samsung Galaxy S4!!! Please help!

Categories

Resources