Original article is published on this site and created by ZeroNull and vdsirotkin (4pda.ru).
How to:
1. The tablet should be already upgraded to stock ICS for A100/A101 (or stock ICS A500/A501/A510 for other tablets).
2. Download this archive on the computer. Unpack it to any place.
3, On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on.
4. Сonnect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
6. Now you will have to install the following programs:
SuperUser APK
Titanium Backup
At first it is necessary to start the Superuser program, at least 1 time after receiving root. And only then programs that require root access.
ATTENTION!
Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!
Change:
The error of final check of receiving root is corrected (The messaging that "root" isn't received, though it was not so)
Support of A510 of tablets is improved
This method uses the 'mempodroid' exploit and some workings out by ZeroNull and vdsirotkin (4pda.ru).
List of rooting versions:
New - ICS_rooting_A10x_A5xx.zip
Old - ICS_rooting.zip
PS: I understand English rather badly, but I'll try to help, if it is necessary.
PS2: Command "Mount ro/rw" for directory /system (partition) - works perfectly!
PS3: This method does not work on the A511 tablets
Just tried this and it works perfectly as described; tested on Linux Mint 12, the su binary is even the latest, superuser is required from the market to grant permissions of course.
Thanks for this post ZeroNull.
I couldn't try Crossix's great .bat as we're a Windows free household, and the Missus keeps forgetting her laptop! This filled the gap nicely, will try to see what I can do with memory management now.
Thanks!
Always please!
Not at all
I was afraid that something was translated incorrectly. But now everything is all right!
Thank you very much worked perfect could not be easier I now have rw permission
Thank you, thank you, thank you, thank you. I can now load Siraxis on here and start gaming via PS3 wireless controller.
Not only is this the best 7incher on the market, you can get it for under $300
ZeroNull said:
Original article is published on this site and created by ZeroNull and vdsirotkin (4pda.ru).
How to:
1. The tablet should be already upgraded to ICS for A100.
2. Download this archive. Unpack it to any place.
3, On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on.
4. Сonnect the tablet to the computer.
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
6. Now you will have to install the following programms:
SuperUser APK
Titanium Backup
ATTENTION!
Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!
This method uses the 'mempodroid' exploit and some workings out by ZeroNull and vdsirotkin (4pda.ru).
PS: I understand English rather badly, but I'll try to help, if it is necessary.
PS2: Command "Mount ro/rw" for directory /system (partition) - works perfectly!
Click to expand...
Click to collapse
is this a permanent root? or temporary? it give r/w permission on system folder?
spino1970 said:
is this a permanent root? or temporary? it give r/w permission on system folder?
Click to expand...
Click to collapse
Permanent
spino1970 said:
is this a permanent root? or temporary? it give r/w permission on system folder?
Click to expand...
Click to collapse
Definitely allows r/w access, done so myself with root explorer, and root has stuck after a reboot.
Sent from my A100 using xda premium
ZeroNull said:
Permanent
Click to expand...
Click to collapse
thanx! what will happen if i'll try this over the crossix one? is it better to wipe the device and start from a clean installation?
And, it already mount r/w or i need to do it manually?
thanx again!
This should be moved in the development section. Thanks gonna try it now.
---------- Post added at 11:09 AM ---------- Previous post was at 10:55 AM ----------
spino1970 said:
thanx! what will happen if i'll try this over the crossix one? is it better to wipe the device and start from a clean installation?
And, it already mount r/w or i need to do it manually?
thanx again!
Click to expand...
Click to collapse
Did this over crossix and worked fine. I can now R/O system folder. Didn't have to wipe.
FINALLY!! A system r/w root that sticks! Outstanding work!
Zeronull, EXCELLENT post! It worked for me.
Your instructions were very understandable.
Thanks again!
I get this error - I had had the partial root before I tried this method.
Full root for A100 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, File exists
push: tools/su -> /data/local/tools/su
push: tools/runit.sh -> /data/local/tools/runit.sh
push: tools/mount.sh -> /data/local/tools/mount.sh
push: tools/mempodroid -> /data/local/tools/mempodroid
push: tools/getroot.sh -> /data/local/tools/getroot.sh
push: tools/delroot.sh -> /data/local/tools/delroot.sh
push: tools/busybox.sh -> /data/local/tools/busybox.sh
push: tools/busybox -> /data/local/tools/busybox
8 files pushed. 0 files skipped.
1299 KB/s (839527 bytes in 0.631s)
Unable to chmod /data/local/tools/loop: Operation not permitted
2274 KB/s (37273 bytes in 0.016s)
-
Preparation is finished.
-
Executing of the main script.
/system/bin/sh: /data/local/tools/runit.sh: cannot execute - Permission denied
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
myprecious27 said:
I get this error - I had had the partial root before I tried this method.
Full root for A100 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, File exists
push: tools/su -> /data/local/tools/su
push: tools/runit.sh -> /data/local/tools/runit.sh
push: tools/mount.sh -> /data/local/tools/mount.sh
push: tools/mempodroid -> /data/local/tools/mempodroid
push: tools/getroot.sh -> /data/local/tools/getroot.sh
push: tools/delroot.sh -> /data/local/tools/delroot.sh
push: tools/busybox.sh -> /data/local/tools/busybox.sh
push: tools/busybox -> /data/local/tools/busybox
8 files pushed. 0 files skipped.
1299 KB/s (839527 bytes in 0.631s)
Unable to chmod /data/local/tools/loop: Operation not permitted
2274 KB/s (37273 bytes in 0.016s)
-
Preparation is finished.
-
Executing of the main script.
/system/bin/sh: /data/local/tools/runit.sh: cannot execute - Permission denied
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
Click to expand...
Click to collapse
Can you access /data/local without root on your tab? If so, try deleting this folder and then running the process again, that's all I can think of.
I deleted the folder, but still it didn't work - so I created the folder /data/local/tools in root explorer then it went without a hitch.
myprecious27 said:
I deleted the folder, but still it didn't work - so I created the folder /data/local/tools in root explorer then it went without a hitch.
Click to expand...
Click to collapse
If you have used some other rooting methods, wipe your tablet (for example - flash through recovery) and try my method again.
ZeroNull said:
Original article is published on this site and created by ZeroNull and vdsirotkin (4pda.ru).
How to:
1. The tablet should be already upgraded to ICS for A100.
2. Download this archive. Unpack it to any place.
3, On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on.
4. Сonnect the tablet to the computer.
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
6. Now you will have to install the following programms:
SuperUser APK
Titanium Backup
ATTENTION!
Don't install Busybox! It is already installed and established! If you reinstall it, some programs will become unable to access root permissions!
This method uses the 'mempodroid' exploit and some workings out by ZeroNull and vdsirotkin (4pda.ru).
PS: I understand English rather badly, but I'll try to help, if it is necessary.
PS2: Command "Mount ro/rw" for directory /system (partition) - works perfectly!
Click to expand...
Click to collapse
Awesome! It all worked! Thanks a bunch!
I did the other root from before, this time I just deleted the folder /data/local/tools and then ran your script. Maybe you should add that to the begining of your script as it will clean everything up from before? Or you could just use a new folder
Either way, THANKS!
OH man thanks, it worked great. I did it right over crossix "double click" root and can now mount system r/w and back to r/o without doing anything else.
Would it be safe now to delete the data/local/rootme folder now that it's not being used as a loop?
Edit: I guess what I'm asking is, what would the clean up process be to clean up other rooting methods?
get root!! thanks a lot.
myprecious27 said:
I get this error - I had had the partial root before I tried this method.
Full root for A100 ICS. Simple method.
-
-
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, File exists
push: tools/su -> /data/local/tools/su
push: tools/runit.sh -> /data/local/tools/runit.sh
push: tools/mount.sh -> /data/local/tools/mount.sh
push: tools/mempodroid -> /data/local/tools/mempodroid
push: tools/getroot.sh -> /data/local/tools/getroot.sh
push: tools/delroot.sh -> /data/local/tools/delroot.sh
push: tools/busybox.sh -> /data/local/tools/busybox.sh
push: tools/busybox -> /data/local/tools/busybox
8 files pushed. 0 files skipped.
1299 KB/s (839527 bytes in 0.631s)
Unable to chmod /data/local/tools/loop: Operation not permitted
2274 KB/s (37273 bytes in 0.016s)
-
Preparation is finished.
-
Executing of the main script.
/system/bin/sh: /data/local/tools/runit.sh: cannot execute - Permission denied
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
Click to expand...
Click to collapse
I got this error too, but when I open superuser it works, mine got rooted..
P.S. I didnt remove superuser before Ive flashed ICS...
Related
Ive been rooted for a while and never cared much to removing the yellow triangle until now.
So much has changed with updates, modems, auto root etc...
I'm wondering what is the best way to rid the yellow triangle today?
I'm rooted
Calkulin's v2.5
Rogue Kernel v1.1.2
Modem EL13
Thanks in advance...
Wow look at all the posts that show up when you search for yellow triangle.
Here is my favorite. I suggest buying a jig from eBay for $3 shipped but if your in a hurry you can do this.
http://forum.xda-developers.com/showthread.php?t=1331782&highlight=Yellow+triangle
gedster314 said:
Wow look at all the posts that show up when you search for yellow triangle.
Here is my favorite. I suggest buying a jig from eBay for $3 shipped but if your in a hurry you can do this.
http://forum.xda-developers.com/showthread.php?t=1331782&highlight=Yellow+triangle
Click to expand...
Click to collapse
Exactly. Searched and came across dozens of threads, most dated back to october and november. Since there's been OTA updates, modems, new root method bypassing yellow triangle... I'm wondering which route applies to me? Any/best way to get rid of yellow triangle without jig at this point?
I remember reading somewhere after flashing a custom rom you could flash the stock rom over it afterwards to remove the yellow triangle.
I just started getting into this stuff yesterday and have rooted my phone and managed to install clockworkmod.
Problem is I really just want to remove Carrier IQ and the yellow triangle then I'll be happy. I need some assistance xedomax! or whoever...
Odin flash stock eg30 kernel to get rid of yellow triangle, you can get from odin eg30 in my sig, then use auto root in my sig to root, add cwm, and disable ciq
sfhub said:
Odin flash stock eg30 kernel to get rid of yellow triangle, you can get from odin eg30 in my sig, then use auto root in my sig to root, add cwm, and disable ciq
Click to expand...
Click to collapse
sfhub thanks- so basically flash the stock kernel (not rom), then use auto root to root the phone, add cwm (no idea how yet) which enables the ability to disable ciq, right?
Anyone feel comfortable explaining some of this stuff over voice by chance, I'd appreciate it.
Ci2e said:
sfhub thanks- so basically flash the stock kernel (not rom), then use auto root to root the phone, add cwm (no idea how yet) which enables the ability to disable ciq, right?
Click to expand...
Click to collapse
Option A - root
Option C - install cwm
Option D - disable ciq
The screenshot in the post will help visualize
Finished step A no problems, then I got to C then selected A for EG30+CWM and got this:
Code:
BOOTIMGSTKREC = no
BOOTIMGSCRIPT = install-boot-eg30-cwm.sh
...Proceeding to copy necessary files...
push: copy2sd/000root/Superuser.apk -> /sdcard/000root/Superuser.apk
push: copy2sd/000root/su -> /sdcard/000root/su
push: copy2sd/000root/install-unroot.sh -> /sdcard/000root/install-unroot.sh
push: copy2sd/000root/install-root.sh -> /sdcard/000root/install-root.sh
push: copy2sd/000root/install-cleanup.sh -> /sdcard/000root/install-cleanup.sh
push: copy2sd/000root/install-ciq-on.sh -> /sdcard/000root/install-ciq-on.sh
push: copy2sd/000root/install-ciq-off.sh -> /sdcard/000root/install-ciq-off.sh
push: copy2sd/000root/install-boot-zImage.sh -> /sdcard/000root/install-boot-zIm
age.sh
push: copy2sd/000root/install-boot-el13.sh -> /sdcard/000root/install-boot-el13.
sh
push: copy2sd/000root/install-boot-el13-cwm.sh -> /sdcard/000root/install-boot-e
l13-cwm.sh
push: copy2sd/000root/install-boot-ek02.sh -> /sdcard/000root/install-boot-ek02.
sh
push: copy2sd/000root/install-boot-ek02-cwm.sh -> /sdcard/000root/install-boot-e
k02-cwm.sh
push: copy2sd/000root/install-boot-eg31.sh -> /sdcard/000root/install-boot-eg31.
sh
push: copy2sd/000root/install-boot-eg31-cwm.sh -> /sdcard/000root/install-boot-e
g31-cwm.sh
push: copy2sd/000root/install-boot-eg30.sh -> /sdcard/000root/install-boot-eg30.
sh
push: copy2sd/000root/install-boot-eg30-cwm.sh -> /sdcard/000root/install-boot-e
g30-cwm.sh
push: copy2sd/000root/install-boot-common.sh -> /sdcard/000root/install-boot-com
mon.sh
push: copy2sd/000root/func.inc.sh -> /sdcard/000root/func.inc.sh
push: copy2sd/000root/busybox -> /sdcard/000root/busybox
19 files pushed. 0 files skipped.
500 KB/s (1948487 bytes in 3.804s)
push: copy2sd-img/000root/zImage-el13-cwm -> /sdcard/000root/zImage-el13-cwm
protocol failure
----
error: device not found
---- END LOG ----
Check for any errors. Assuming there are none, BootImg install was SUCCESSFUL.
----
Getting ready to reboot...
This reboot will take slightly LONGER than usual since it will be
recreating Dalvik-Cache.
Your phone MAY be slightly SLOWER for a SHORT TIME after boot is
complete while it performs maintenance.
This is all NORMAL.
Press any key to continue . . .
I just tried it again and always get the error device not found.
Ci2e said:
I just tried it again and always get the error device not found.
Click to expand...
Click to collapse
Did your phone crash or something? It seems adb stopped talking to your phone in the middle of a file copy and hasn't been able to talk to it since.
Try rebooting your phone and your PC and try again. It looks like everything was proceeding as expected until the connection to your phone suddenly went black.
sfhub said:
Did your phone crash or something? It seems adb stopped talking to your phone in the middle of a file copy and hasn't been able to talk to it since.
Try rebooting your phone and your PC and try again. It looks like everything was proceeding as expected until the connection to your phone suddenly went black.
Click to expand...
Click to collapse
Code:
push: copy2sd/000root/install-boot-ek02-cwm.sh -> /sdcard/000root/install-boot-e
k02-cwm.sh
push: copy2sd/000root/install-boot-eg31.sh -> /sdcard/000root/install-boot-eg31.
sh
push: copy2sd/000root/install-boot-eg31-cwm.sh -> /sdcard/000root/install-boot-e
g31-cwm.sh
push: copy2sd/000root/install-boot-eg30.sh -> /sdcard/000root/install-boot-eg30.
sh
push: copy2sd/000root/install-boot-eg30-cwm.sh -> /sdcard/000root/install-boot-e
g30-cwm.sh
push: copy2sd/000root/install-boot-common.sh -> /sdcard/000root/install-boot-com
mon.sh
push: copy2sd/000root/func.inc.sh -> /sdcard/000root/func.inc.sh
push: copy2sd/000root/busybox -> /sdcard/000root/busybox
19 files pushed. 0 files skipped.
1813 KB/s (1948487 bytes in 1.049s)
push: copy2sd-img/000root/zImage-el13-cwm -> /sdcard/000root/zImage-el13-cwm
push: copy2sd-img/000root/zImage-el13 -> /sdcard/000root/zImage-el13
push: copy2sd-img/000root/zImage-ek02-cwm -> /sdcard/000root/zImage-ek02-cwm
push: copy2sd-img/000root/zImage-ek02 -> /sdcard/000root/zImage-ek02
push: copy2sd-img/000root/zImage-eg31-cwm -> /sdcard/000root/zImage-eg31-cwm
push: copy2sd-img/000root/zImage-eg31 -> /sdcard/000root/zImage-eg31
push: copy2sd-img/000root/zImage-eg30-cwm -> /sdcard/000root/zImage-eg30-cwm
push: copy2sd-img/000root/zImage-eg30 -> /sdcard/000root/zImage-eg30
8 files pushed. 0 files skipped.
3887 KB/s (67102720 bytes in 16.857s)
----
Installing BootImg - EG30+CWM... Done
----
BootImg = zImage-eg30-cwm
STATUS1 = 32765+0 records in 32765+0 records out 8387840 bytes transferred in 2.
367 secs (3543658 bytes/sec)
STATUS2 = 32765+0 records in 32765+0 records out 8387840 bytes transferred in 2.
755 secs (3044588 bytes/sec)
----
Waiting for filesystem to sync... Done
---- END LOG ----
Check for any errors. Assuming there are none, BootImg install was SUCCESSFUL.
----
Getting ready to reboot...
This reboot will take slightly LONGER than usual since it will be
recreating Dalvik-Cache.
Your phone MAY be slightly SLOWER for a SHORT TIME after boot is
complete while it performs maintenance.
This is all NORMAL.
Press any key to continue . . .
Now A/C is complete, but I remember seeing su is out of date, I attempted to run D again and noticed at the top.
Code:
Proceeding with install
----
Asking for root permissions... su: not found
Done
---- BEGIN LOG ----
INSTALLDESC = CIQ Disable
INSTALLSCRIPT = install-ciq-off.sh
...Proceeding to copy necessary files...
push: copy2sd/000root/Superuser.apk -> /sdcard/000root/Superuser.apk
push: copy2sd/000root/su -> /sdcard/000root/su
push: copy2sd/000root/install-unroot.sh -> /sdcard/000root/install-unroot.sh
push: copy2sd/000root/install-root.sh -> /sdcard/000root/install-root.sh
push: copy2sd/000root/install-cleanup.sh -> /sdcard/000root/install-cleanup.sh
push: copy2sd/000root/install-ciq-on.sh -> /sdcard/000root/install-ciq-on.sh
push: copy2sd/000root/install-ciq-off.sh -> /sdcard/000root/install-ciq-off.sh
push: copy2sd/000root/install-boot-zImage.sh -> /sdcard/000root/install-boot-zIm
age.sh
push: copy2sd/000root/install-boot-el13.sh -> /sdcard/000root/install-boot-el13.
sh
push: copy2sd/000root/install-boot-el13-cwm.sh -> /sdcard/000root/install-boot-e
l13-cwm.sh
push: copy2sd/000root/install-boot-ek02.sh -> /sdcard/000root/install-boot-ek02.
sh
push: copy2sd/000root/install-boot-ek02-cwm.sh -> /sdcard/000root/install-boot-e
k02-cwm.sh
push: copy2sd/000root/install-boot-eg31.sh -> /sdcard/000root/install-boot-eg31.
sh
push: copy2sd/000root/install-boot-eg31-cwm.sh -> /sdcard/000root/install-boot-e
g31-cwm.sh
push: copy2sd/000root/install-boot-eg30.sh -> /sdcard/000root/install-boot-eg30.
sh
push: copy2sd/000root/install-boot-eg30-cwm.sh -> /sdcard/000root/install-boot-e
g30-cwm.sh
push: copy2sd/000root/install-boot-common.sh -> /sdcard/000root/install-boot-com
mon.sh
push: copy2sd/000root/func.inc.sh -> /sdcard/000root/func.inc.sh
push: copy2sd/000root/busybox -> /sdcard/000root/busybox
19 files pushed. 0 files skipped.
2086 KB/s (1948487 bytes in 0.912s)
----
/data/local/tmp/sh: not found
---- END LOG ----
Check for any errors. Assuming there are none, install was SUCCESSFUL.
----
Getting ready to reboot...
Press any key to continue . . .
I still have the yellow triangle, and ciq is still there just inactive. My sprint phone came with a voodoo carrier iq score of 400 using zedomax kernel made it 570 and now its at 270 better than nothing I suppose.
What can I do to finish what I have started?
Ci2e said:
So now C is complete but I remember seeing su is out of date, I attempted to run C again and noticed at the top.
Click to expand...
Click to collapse
That means "su" was working when Option C ran.
The su is out of date is not being generated by the rooting package. It sounds like the Superuser app is telling you that. Maybe it installed some update and broke su.
What happens when you do "adb shell" and type "su"? That is basically what the CIQ script you ran is doing and the response is that "su" can't be found.
What is adb exactly and shell and where do I run it lol
All the new terminology is killing me!
# su
su
su: not found
#
I don't know what happened to your su, but it seems it is not around anymore.
Try running Option A again. That should give you su back. Then run Option D and disable CIQ.
What results do I want after running A? --+ ++- +-+ +++ ---
Oddly enough this is making me want to play StarCraft II, lol...
Code:
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40322cd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd198cb 0xafd395cf
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
---- STATUS of ZERG on PREVIOUS few lines ----
Waiting for device to be connected [press CTRL-C to cancel]... Found device
Installing persistent root... Done
Waiting for filesystem to sync... Done
---- END LOG ----
Check the STATUS of ZERG above, this exploit depends on a
condition which doesn't always hit
[-] Hellions with BLUE flames !
Means the EXPLOIT will NOT work on this version of the ROM.
However, if your ADB is rooted, the persistent root install MAY still work.
Check for additional errors in that section of the log.
[-] Zerglings did not leave interesting stuff
Means the exploit did NOT work during this pass
After reboot you'll need to RE-RUN the root install script
It may take SEVERAL attempts before the condition hits
[+] Rush did it ! It's a GG, man !
Means the exploit was SUCCESSFUL. Script will reboot, then you are DONE!
----
Getting ready to reboot...
Press any key to continue . . .
----
Cleaning up temporary files... Done
Rebooting
If it takes LONGER than 30 seconds to initiate reboot
manually reboot using the POWER button to power OFF/ON
----
Activity complete - review status logs above if needed
----
Press any key to continue . . .
Just finished A again and a reboot and I still don't have the superuser listed under applications with the skeleton icon. Instead I have a gray and green android icon "Superuser" listed in applications. Does the icon look different because of the differing methods?
Ci2e said:
Just finished A again and a reboot and I still don't have the superuser listed under applications with the skeleton icon. Instead I have a gray and green android icon "Superuser" listed in applications. Does the icon look different because of the differing methods?
Click to expand...
Click to collapse
That is the Superuser v3 icon. The previous version you had that probably came with your ROM was the v2.3 icon.
You should have root installed at this point.
BTW in case it wasn't obvious if you choose Option F from the main screen it will increase the scroll buffer so you can see all the log info.
Now that you mention that will come in very handy.
Okay so I have ran A, C, and D again. Although I still have the yellow triangle on the boot screen and carrier iq is still there but dormant.
So now I can flash the EG30 stock kernel to get rid of the triangle and I'm done, or no?
Is it worth upgrading to EK or is it too much hassle?
Ci2e said:
...
Although I still have the yellow triangle on the boot screen
...
So now I can flash the EG30 stock kernel to get rid of the triangle and I'm done, or no?
...
Is it worth upgrading to EK or is it too much hassle?
Click to expand...
Click to collapse
I actually would have ODIN flashed the stock EG30 kernel as the first step, because I would have wanted to end up with a kernel that had CWM (EG30+CWM), but doing it at the end works too for getting rid of the triangle. If you want EG30+CWM, just run Option C again after you ODIN stock EG30 kernel back. Make sure you are only flashing the kernel, not the whole ROM.
As to EK02, I would suggest you run like this for a day or two. If you like the way it performs, don't bother upgrading. If there is something lacking, post in the Q&A section and ask if it would be resolved if you went to EK02.
Personally I actually like the EG30 release. IF I had LoS, I might be enticed to go to a newer version, but since I've never seen it with my setup, I'm just purely comparing the ROMs.
I'm actually running EL13 kernel right now with EG30 Modem and EG30 ROM but that could change tomorrow to another combination.
sfhub said:
I actually would have ODIN flashed the stock EG30 kernel as the first step, because I would have wanted to end up with a kernel that had CWM (EG30+CWM), but doing it at the end works too for getting rid of the triangle. If you want EG30+CWM, just run Option C again after you ODIN stock EG30 kernel back. Make sure you are only flashing the kernel, not the whole ROM.
Click to expand...
Click to collapse
What does CWM stand for and do? How do I ensure I am only flashing the kernel?
I think I've been using the latest zedomax kernel but I can't really tell there is no difference besides the yellow triangle. While I'm researching I end up with 15 separate tabs all from xda-developers. I've almost got it, if I don't get it soon I think I might get a headache. Where's the server everyone hangs out to talk and chill?
Alex1x said:
Ive been rooted for a while and never cared much to removing the yellow triangle until now.
So much has changed with updates, modems, auto root etc...
I'm wondering what is the best way to rid the yellow triangle today?
I'm rooted
Calkulin's v2.5
Rogue Kernel v1.1.2
Modem EL13
Thanks in advance...
Click to expand...
Click to collapse
Look up Chris41g's thread in the development section. I followed those steps and got rid of that bothersome triangle on my screen. It was simple and straightforward. Trust!
Sent from my SPH-D710 using XDA App
asbjörn said:
Look up Chris41g's thread in the development section. I followed those steps and got rid of that bothersome triangle on my screen. It was simple and straightforward. Trust!
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
That's funny I've already read it. If you haven't been here keeping up with everything all this is very overwhelming good thing there are a few of you very actively helping ppl like me. tyvm =]
I would like to root My LT18i Xperia Arc S, just so I can get rid of the bloatware, although if I could upgrade to ICS as well then that would be cool. I've found loads of instructions on how to root, but none for my firmware version, which is 4.0.2.C.0.5. The phone is locked to Three (a UK network operator). A lot of the instructions talk of downgrading the firmware from various versions to 4.0.2.A.0.42, and then rooting from there, although none list my particular firmware. Is this method possible for my firmware version? If it's not and I try anyway will I wreck my phone? I'd like to be as sure as possible before I start. My boot loader is locked.
Thank you.
timswait said:
I would like to root My LT18i Xperia Arc S, just so I can get rid of the bloatware, although if I could upgrade to ICS as well then that would be cool. I've found loads of instructions on how to root, but none for my firmware version, which is 4.0.2.C.0.5. The phone is locked to Three (a UK network operator). A lot of the instructions talk of downgrading the firmware from various versions to 4.0.2.A.0.42, and then rooting from there, although none list my particular firmware. Is this method possible for my firmware version? If it's not and I try anyway will I wreck my phone? I'd like to be as sure as possible before I start. My boot loader is locked.
Thank you.
Click to expand...
Click to collapse
Have you run SEUS or PC Companion at all? There's been 5 FW releases since then according to Wotan Server.
From what I have heard, the regular root method for GB, 4.0.2.A.0.58 and lower, should work also on 4.0.2.C.0.5 firmware. Give it a try, you got nothing to lose there.
OK, so I really am a total numpty, I was assuming that all updates could come OTA, and because I didn't have any updates available when I checked on the phone I must have the latest version, I hadn't realised that updating it from a PC did a full update. :silly:
So I'm now updated to ICS, although in a way my original question remains... Now my build number is 4.1.L.0.8, so can I follow the root guides for 4.1.A.0.562, for example the guide here: androidauthority.com/xperia-arc-s-lt18i-root-android-4-0-ics-80266 ? And equally importantly, if I try to follow the guide and it doesn't work on my firmware will it simply do nothing, or will it wreck the phone?
Thank you guys, I thought I had done a lot of reading up on rooting and flashing and unlocking boot loaders, but missed the obvious and a simple comment like "Have you tried SEUS" can make all the difference!
timswait said:
OK, so I really am a total numpty, I was assuming that all updates could come OTA, and because I didn't have any updates available when I checked on the phone I must have the latest version, I hadn't realised that updating it from a PC did a full update. :silly:
So I'm now updated to ICS, although in a way my original question remains... Now my build number is 4.1.L.0.8, so can I follow the root guides for 4.1.A.0.562, for example the guide here: androidauthority.com/xperia-arc-s-lt18i-root-android-4-0-ics-80266 ? And equally importantly, if I try to follow the guide and it doesn't work on my firmware will it simply do nothing, or will it wreck the phone?
Thank you guys, I thought I had done a lot of reading up on rooting and flashing and unlocking boot loaders, but missed the obvious and a simple comment like "Have you tried SEUS" can make all the difference!
Click to expand...
Click to collapse
If it doesnt work, your phone should be fine. But that also means that you've been doing something wrong. Give it a go
Sent from Xperia Arc S
I followed the instructions here for rooting:
http://forum.xda-developers.com/showthread.php?t=1601038&nocache=1
It seemed to go through all the stages, the phone rebooted several times and it came up "All done" at the end. The good news is that the phone still works fine, the bad news is that it doesn't seem to be rooted. I've installed Titanium Backup and it comes up with "could not acquire root privileges, please check that your phone is rooted", so I assume this means it hasn't worked? Is there any other way to see if it's rooted? This is the output from running the rooting batch script:
Code:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- symlinking tmp directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- enabling emulator hack
/system/bin/sh: cannot create /data/local.prop: Permission denied
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
3059 KB/s (1075144 bytes in 0.343s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
--- Free space on /system : 56068 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/bin/sh: /system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
--- rebooting
ALL DONE!!!
Press any key to continue . . .
There's four links to root threads now in my guide, give them a read.
Thanks, that guide was very useful. I've actually used a combination of the techniques, and it seems to have worked Here's what I did, might be useful to someone, also please if anyone who knows better than me can see any problems then please let me know if I'm going to have problems in the future
1. Backed up my firmware using the instructions from 100rabh791 here:
http://talk.sonymobile.com/message/178992
2. Flashed back to 4.1.A.0.562 Kernel using Nabeel's instructions here:
http://talk.sonymobile.com/thread/41119?start=0&tstart=0
3. Rooted using DooMLoRD's root kit here:
http://forum.xda-developers.com/showthread.php?t=1601038
At this point I seemed to have a fully working and rooted phone, however I thought it was best to go back to my original build version (4.1.L.0.8), so I re-flashed my backed up firmware, However this lost my root privileges, so I was back to the start. So I re-did steps 1-3 and then:
4. Re-flashed back to my original firmware, but checked the options "Exclude system", "Exclude baseband", "Exclude Fota" and "Exclude TA" (in other words just left Kernel unchecked).
So as I understand it (which I possibly don't), I should be back on my original, most up to date build version, but now have root access, please correct me if there's anything wrong with what I've done.
timswait said:
So as I understand it (which I possibly don't), I should be back on my original, most up to date build version, but now have root access, please correct me if there's anything wrong with what I've done.
Click to expand...
Click to collapse
Nice one, doesn't look like you'll have any issues, but the main thing is you've got root. What does it say in your Settings/About Phone/Build Number?
XperienceD said:
Nice one, doesn't look like you'll have any issues, but the main thing is you've got root. What does it say in your Settings/About Phone/Build Number?
Click to expand...
Click to collapse
4.1.L.0.8 which is what it was on after the official upgrades before I started the rooting process.
Hi,
A few days ago, I did unlock and root my N7 (2013) using "Nexus Root Toolkit (v.1.6.8)" by WugFresh. I followed the instructions to the letter and everything went OK, it seemed. My N7 (JSS15J) is unlocked and I have root access, as confirmed by "Titanium Backup" and "Root Checker Pro" app.
However, my N7 cannot mount "System" - which is why I cannot delete any system app bloatware (also confirmed by "System App Remover" & Root Checker Pro app). When rooting my N7 (2012) and my SGS3, everything worked just perfectly and I never had these kind of issues...
I did factory-reset a number of times, went through the unlock/root process again, rooted again via UPDATE-SuperSU-v1.51.zip etc etc. - no dice. TWRP v2.6.0.0 is installed and working. I also installed & updated BusyBox, and I wiped of Dalvik - but still no root access to "System", or "mount".
As I just found out, "Root Checker Pro" actually explains why I can't mount "System" and/or don't have root access... I just don't know what to do about it:
Congratulations! You have root access!
Super User Application Status:
SuperSU application - version 1.51 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 112164 2008-08-01 07:00 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your Nexus 7 device by Root Checker Pro version 1.3.4 from joeykrim in the Android Market - http://goo.gl/NcnHn
What did I miss?
Can someone please help me to install whatever is needed to gain root access to "System"? "System App Remover" app shows that "System" is not mounted but downloading a separate "mount app" did not do the trick either...
Thanks for your help & suggestions, guys!
System is already mounted or you wouldn't be running android.
What you probably want to do is "remount"
mount -o remount,rw /system /system
But if all you want is to remove apps, perhaps it is easier if you just use Titanium to freeze them first and once you are sure you don't need them you can delete them, but I would just leave them frozen.
sfhub said:
System is already mounted or you wouldn't be running android.
What you probably want to do is "remount"
mount -o remount,rw /system /system
But if all you want is to remove apps, perhaps it is easier if you just use Titanium to freeze them first and once you are sure you don't need them you can delete them, but I would just leave them frozen.
Click to expand...
Click to collapse
Thanks, sfhub... I'll give that a try!
Doesn't look good, I'm afraid:
C:\platform-tools>mount -o remount,rw /system /system
'mount' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Any further suggestions, please?
androidarmin said:
Doesn't look good, I'm afraid:
Click to expand...
Click to collapse
Seems like I tried in the wrong place... I'll give it another try; sorry
Well... downloaded a Terminal Emulator from Google Play..
But now I'm getting a "mount: Operation not permitted" error...
Googled a ton and found a lot of good advice... and even figured things out using ADB (hint: adb shell) - but nothing worked in the end.
Seems like my "SU" may be the culprit, but I'll figure things out when I have more time... meaning, on the weekend. Probably go back to stock and then start over. Seems to be the simplest way right now.
Thanks so far, guys!
androidarmin said:
Well... downloaded a Terminal Emulator from Google Play..
But now I'm getting a "mount: Operation not permitted" error...
Click to expand...
Click to collapse
In adb, you need to type su first to give yourself root privileges before you can mount /system
You need to mount system as read/write in order to remove apps from it.
Sent from my Nexus 7 (2013)
Thanks, sfhub & Muikkuman... I know/I did. Still doesn't work.
Sent from my GT-I9300 using Tapatalk 4
androidarmin said:
Thanks, sfhub & Muikkuman... I know/I did. Still doesn't work.
Click to expand...
Click to collapse
what happens if you do in a command prompt in your adb directory
adb shell
su
Yes this seem strange.
Sent from my Nexus 7 (2013)
My suggestion would be to update TWRP, back-up important data, format data in recovery, look for decent rom, flash rom/gapps/latest supersu.
Then go to 'advanced' in recovery and fix permissions. Reboot recovery and tick 'mount' 'system', respectively install root file explorer of your liking.
No quick solution but should do the trick..
My suggestion is DO NOT delete anything, period. Nurse disable from settings or use pm disable.
Deleting stuff is completely pointless and WILL cause you problems in the future.
androidarmin said:
Thanks, sfhub & Muikkuman... I know/I did. Still doesn't work.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Dont know if you got this sorted. i was having the same problem with my son's Nexus 7 and came across this tutorial for Total Commander
http://www.androidpolice.com/2011/0...ns-remount-rw-in-total-commander-for-android/
Great little short cut to get the job done and can now get Total Commander free on Google Play.
So whats up guys,
I've got my new LG G-Pad 8.3 2 days ago and now.
I only want to root it. No Custom-Roms and CWMR etc.
The problem is:
No matter what I try, I can't root the device and I absolutely hv no Idea why.
Ofc I followed exact the instructions in the XDA-Developer thread.
The ERROR msg says:
Mounting system RW and pushung SU, then remounting system RO again
mount: Operation not permitted
failed to copy 'su' to '/system/xbin/su' : Read-only file system
Unable to open /system/xbin/su: No such file or directory
Unable to open /system/xbin/su: No such file or directory
mount: Operation not permitted
Installing superuser
4083 KB/s <2025538 bytes in 0.484s>
pkg: /data/local/tmp/superuser.apk
Success
Screenshot is also attached.
Any solutions
SOLVED!
The known Root methods in the Forum are working only for the LG G-Pad 8.3 Android 4.2.2!
If people updated it to 4.4.2 before rooting, have to use the following rooting method:
Note: I am not responsible if you make any mistakes or this does not work for you. Don’t forget to backup! I backed up my entire SD card.
Recommended:
Backup your data
Battery charged more than 50%
All things you will need:
Installed USB Drivers
IOroot25 (can be found here in the Forum!)
Rootchecker [Download]
How to Root LG G Pad 8.3 Steps:
1. Download and extract the IOroot25
2. Make sure your phone is in USB Debugging mode. Plug phone to PC.
3. Set USB mode to Charging only
4. Make sure ADB has been installed, and ADB has the proper permission
5. Run script and follow the onscreen instructions. (you can skip the Airplane part, because theres no thing such airplane mode on
our LG G-Pad 8.3
6. Windows: Double-click on root.bat
Linux: cd into IOroot folder -> chmod +x root.sh -> ./root.sh
Mac: cd into /IOroot/mac folder -> chmod +x root.sh -> ./root.sh
Confirm root with rootchecker.
Screenshot is attached ^_^. Enjoy.
Hi,
im trying to install twrp and having a tough time trying to find a solution to my problem, ive rooted using zeroepochs guide, when i run the command to extract and install the recovery.zip i get a read only error as below
[email protected]:/ $ sh /sdcard/firetv2_recovery_v5.zip
Extracting unzip...
Remounting /system read-write...
mount: Invalid argument
Extracting...
checkdir: cannot create extraction directory: /system/recovery
Read-only file system
ln: /system/bin/ext4_resize: Read-only file system
Remounting /system read-only...
any help is appreciated.
You need to go into root admin.
Use the command "Su" to get into root shell
Hi, thanks I've tried that and get the same issues?
skirocket said:
Hi, thanks I've tried that and get the same issues?
Click to expand...
Click to collapse
After su command was sent through ADB, have you granted access on the pop up screen that appears at first use?
- Reset (unplug and plug back in) unit
- let it boot into main menue
- connect through ABD
- at adb shell prompt type su
- enter
- A pop up screen should appear on your TV asking you to grant access for su
- using your FireTV remote select yes and press OK.
- see if issue is solved
bula1ca said:
After su command was sent through ADB, have you granted access on the pop up screen that appears at first use?
- Reset (unplug and plug back in) unit
- let it boot into main menue
- connect through ABD
- at adb shell prompt type su
- enter
- A pop up screen should appear on your TV asking you to grant access for su
- using your FireTV remote select yes and press OK.
- see if issue is solved
Click to expand...
Click to collapse
hi thanks for the reply, i have done that and it says that i have been granted SU but i get this message
[email protected]:/ # sh /sdcard/firetv2_recovery_v5.zip
Extracting unzip...
Remounting /system read-write...
mount: Invalid argument
Extracting...
checkdir: cannot create extraction directory: /system/recovery
Read-only file system
ln: /system/bin/ext4_resize: Read-only file system
Remounting /system read-only...
Sorry to pick this up again. But i have the same Issue. How have you installed TWRP?
Thanks
I used King root, then installed a custom rom, had too many problems trying to install twrp previously.
skirocket said:
I used King root, then installed a custom rom, had too many problems trying to install twrp previously.
Click to expand...
Click to collapse
Thank you
so you used this guide http://www.aftvnews.com/how-to-root...covery-and-a-pre-rooted-rom-all-without-a-pc/ with your rooted Fire Tv2?
i used this guide http://www.aftvnews.com/how-to-root-the-fire-tv-2-using-kingroot-no-usb-cable-required/. but at the time if i remember i updated my box to stock update 5.0.5 from 5.0.4 then rooted again.
Hi, the trick is to use this Guide http://www.aftvnews.com/how-to-root-the-amazon-fire-tv-2/
Worked perfectly
I know this is an old thread but I'll post what worked for me just in case...
On ADBLink, select Root → Mount /system RW. This will make /system writable.
Not sure if this is necessary, but I switch back to RO (read only) once I was done with my changes.