Is there any way to temporary root EVO GSM ics hboot 1.53 ?
Don't know about temp. ..... But this will help you root http://forum.xda-developers.com/showthread.php?t=1787426
invince2 said:
Don't know about temp. ..... But this will help you root http://forum.xda-developers.com/showthread.php?t=1787426
Click to expand...
Click to collapse
Tnx for rply.
I know for that tut but dont whana lose my warranty.
bump, i'd like to temp root to backup apps/data before unlocking... is this possible?
ls3c6 said:
bump, i'd like to temp root to backup apps/data before unlocking... is this possible?
Click to expand...
Click to collapse
I will try this one, as it says - it should create temp root for locked bootloader devices:
http://forum.xda-developers.com/showthread.php?t=1340255
doesn't work:
[-] Not a 2.2/2.3 Android ...
--- WAITING FOR DEVICE TO RECONNECT
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
3478 KB/s (1075144 bytes in 0.301s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- 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
ls3c6 said:
doesn't work:
[-] Not a 2.2/2.3 Android ...
--- WAITING FOR DEVICE TO RECONNECT
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
3478 KB/s (1075144 bytes in 0.301s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- 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
Click to expand...
Click to collapse
read through that thread, there was discussion on some errors people gets, maybe will find solution there
Related
Hello,
I've become an owner of a new I9100P
kernel: 2.6.35.7-I9100PXXKK5-CL750989
[email protected] #2
bulid number: GINGERBREAD.XXKK5
baseband: I9100PXXKI3
I'm having some problems rooting it.
ZergRush kit is unable to root the phone:
Code:
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
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
2598 KB/s (1075144 bytes in 0.404s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
142 KB/s (439 bytes in 0.003s)
df: /mnt/.lfs: Function not implemented
--- Free space on /system : 6868 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/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
--- rebooting
ALL DONE!!!
Also tried with SuperOneClickv2.3.3 but no luck.
Any suggestions how to root it?
So nobody has rooted I9100P yet?
ZergRush doesn't work on 2.3.6, unless you do the "RAM crash" method. Load apps until you have over 500mb RAM used, then do ZergRush method again.
Sent from my GT-I9100 using XDA
hi no matter which program i try , i just cannot ' Root" The Phone.
have Tried superoneclick -Galaxy s2 Root and all i get is errrors saying :
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
cannot stat 'files\zergRush': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
/system/bin/sh: ./data/local/tmp/zergRush: not found
--- WAITING FOR DEVICE TO RECONNECT
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
2767 KB/s (1075144 bytes in 0.379s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- 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, No such file or directory
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 *, No such file or directory
--- rebooting
what am i doing wrong ? i am 4.0.3 baseland version 19100xxlps
Check your phones development thread, there are separate threads for each version of the SGSII make sure you have the correct thread for your phone.
warmride said:
hi no matter which program i try , i just cannot ' Root" The Phone.
have Tried superoneclick -Galaxy s2 Root and all i get is errrors saying :
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
cannot stat 'files\zergRush': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
/system/bin/sh: ./data/local/tmp/zergRush: not found
--- WAITING FOR DEVICE TO RECONNECT
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
2767 KB/s (1075144 bytes in 0.379s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- 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, No such file or directory
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 *, No such file or directory
--- rebooting
what am i doing wrong ? i am 4.0.3 baseland version 19100xxlps
Click to expand...
Click to collapse
U cannot because ur special<3
Sent from my SGS2 powered by cm9 love
I have the same issue as bartoloandre98...
I am on 4.0.3
Thanks
zergRush is not able to root ICS ROMs.
Do you now which one i can use to root my device but i don't want the yellow triangle on the boot up
Thanks
Yes, I do. You can too by doing a little looking.
Find a matching (or closest match) CFRoot kernel (assuming you have an I9100/T), flash it. Done. Root + CWM. Not rocket surgery.
Unless you're having a whole heap of problems you haven't told us about I.E "I have the same issue as bartoloandre98...I am on 4.0.3" is vague as you know what. Bit hard to help you without details
P.S - Zergrush won't work with 4.0.3
Edit - Oinky is right. This stuff has been done to death on here.
Oh well
Thanks for the update and your kind help
Thanks
Just downloaded Odin. Open it via a pc and flash a kernel like siyah which contains CWM. Make sure its tar format and open this in pda in Odin then your flashed.
Will take approx 15 seconds
Sent from my SG2 on steroids
NTOP said:
Do you now which one i can use to root my device but i don't want the yellow triangle on the boot up
Thanks
Click to expand...
Click to collapse
Several ways to remove this. Easiest way download triangle away app from the market
Sent from my SG2 on steroids
OK, here's what I've done. I downgraded and rooted my SK17 several hours ago, and then removed some bloatware. everything went great, but then I decided I want to replace stock camera app with this one. as I didn't know how to do it, I thought "hey, why don't just delete the SemcCameraUI.apk from system/app and replace it with downloaded one"? so I did it, but it still didn't want to work. so I tried to reboot the phone. the app still wasn't working [by then I guessed it's not the way it's done], and then Root Explorer decided that it doesn't want to work with such a stupid human and told me that it can't delete the apk nor change the permissions because it's a read-only file. and the SuperUser app was force-closing.
so I flashed the phone with .58 again, I learnt that I lost the root, so I tried rooting it again, and then I got the message from the zergRush script:
failed to copy 'files\SuperUser.apk' to 'system/app/./SuperUser.apk': Read-only file system
Click to expand...
Click to collapse
any suggestion what should I do to root it again?
note: every time I flashed .ftf file, I was unchecking "wipe data", "wipe cache" and "wipe apps log".
najodleglejszy said:
OK, here's what I've done. I downgraded and rooted my SK17 several hours ago, and then removed some bloatware. everything went great, but then I decided I want to replace stock camera app with this one. as I didn't know how to do it, I thought "hey, why don't just delete the SemcCameraUI.apk from system/app and replace it with downloaded one"? so I did it, but it still didn't want to work. so I tried to reboot the phone. the app still wasn't working [by then I guessed it's not the way it's done], and then Root Explorer decided that it doesn't want to work with such a stupid human and told me that it can't delete the apk nor change the permissions because it's a read-only file. and the SuperUser app was force-closing.
so I flashed the phone with .58 again, I learnt that I lost the root, so I tried rooting it again, and then I got the message from the zergRush script:
any suggestion what should I do to root it again?
note: every time I flashed .ftf file, I was unchecking "wipe data", "wipe cache" and "wipe apps log".
Click to expand...
Click to collapse
check this thread for rooting http://forum.xda-developers.com/showthread.php?t=1709880
er, yeah. that's how I rooted. I did it once, and then, as I said in post #1, lost it.
Nj, post the entire Rooting log.. That might help in knowing the problem more precisely..
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
--- pushing zergRush
cannot stat 'files\zergRush': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
./data/local/tmp/zergRush: not found
--- WAITING FOR DEVICE TO RECONNECT
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
2837 KB/s (1075144 bytes in 0.370s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 178304 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/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
--- rebooting
at first I realized the antivirus removed the ZergRush file so I disabled it and unpacked the archive once again, but still no result.
najodleglejszy said:
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
--- pushing zergRush
cannot stat 'files\zergRush': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
./data/local/tmp/zergRush: not found
--- WAITING FOR DEVICE TO RECONNECT
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
2837 KB/s (1075144 bytes in 0.370s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 178304 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/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
--- rebooting
at first I realized the antivirus removed the ZergRush file so I disabled it and unpacked the archive once again, but still no result.
Click to expand...
Click to collapse
There's your fault.
As I had suspected it..
The anti-virus removes the ZergRush file even from the .zip or .rar file..
Disable anti-virus, download the rootingkit files again and the unpack and root your phone..
NOTE: While rooting, using flashtool, flashing kernel, please disable anti-virus temporarily.
And also while rooting your phone close flashtool if it's open.
all done, thanks! turns out I'm too dumb to remember that antivirus can peek inside zipped files.
btw, can anyone hint me how to replace the camera app with the one I was trying to?
najodleglejszy said:
all done, thanks! turns out I'm too dumb to remember that antivirus can peek inside zipped files.
btw, can anyone hint me how to replace the camera app with the one I was trying to?
Click to expand...
Click to collapse
NP
And flash the MDPI-GB-CamExtreme.zip file using CWM..
It's only for stock ROM I guess.
And don't forget to backup first using CWM.
thanks once again! thread can be locked now.
Hi!
Question related to Samsng Galaxy Mini S5570.
After been using link2sd without problem, I restore the phone for cleaning propurse and I had the bad idea of update the fimware with Kies, It stop at 80% and after two hours, desesperate I disconnect the cable. Good point of that I could do an emergency recovery with Kies.
The problem now is when I try to root, I get this error log with 'Easy rooting toolkit' (and many others):
Note: I have tried also with the same Universal Gingerbread that worked with other Mini 2.3.6 like a charm.
Code:
--- DEVICE FOUND
--- pushing busybox
1590 KB/s (1075144 bytes in 0.660s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- 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/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
--- rebooting
ALL DONE!!!
I found a thread with a good rooting solution, http://forum.xda-developers.com/showthread.php?t=1869493
but related to Samsung Galaxy S II.
Do you know any way to resolve this?
Thanks for help!
I am unable to root my neo L I searched all over the forum got the same issue but no solution to this problemplease help
i am following this guide to root http://forum.xda-developers.com/showthread.php?t=2222057 my flash tool is 0.9.13
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[-] Not a 2.2/2.3 Android ...
--- WAITING FOR DEVICE TO RECONNECT
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
4101 KB/s (1075144 bytes in 0.256s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- 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 app, Is a directory
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
this is snip it from DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su
Rooot is not happening.