I plan on rooting with SOC 2.3.3 soon (SGP5.0 USA). I just want to be sure I do it right.
1. Phone on USB Debugging mode
2. Make sure the Android drivers for your phone are installed
3. Plug in USB cable, DO NOT mount your SD card.
4. Click "SuperOneClick.exe" on PC (right click, run as administrator)
5. Click Root
Is that right? Does the batch of SOC files need to be at PC root or can they be anywhere? Just want all my eggs in the right basket before trying this.
I tried this and i've used soc b4 but I could not get it to work!
Sent from my YP-G70 using xda premium
same here, I can't root with both superoneclick and doomlord's. I have 2.3.6, what can I do?
Flash rumirand r13 kernel from this forum and then superoneclick will root it in 10 seconds..your rom stays the same..stock.
Odd. Still showing 0 kb in /system after using included SU.
Sent from my YP-G70
Hi guys, how did you overcame problem with "No space left on device"? I read the whole thread, but didn't find solution for it. The same happened to me when I used SuperOneClickv2.3.3-ShortFuse for rooting Froyo 2.2.2 (G70XXKD6).It was my first time rooting... what's the problem installing busybox? It's showing "No space left on device". Thanks for the help.
Have you tried to use towelroot? It should work considering the kernel on these devices are really old and are not patch against the vulnerability that towelroot uses.has anyone done this recently? Rooting YP-G70 (5.0 wifi)
i am at 2.3.6 firmware version and i think i tried every method on XDA so far.
Debug Developer mode enabled,
this batch (http://xdaforums.com/showthread.php?t=1424358) gives me:
--- STARTING ----
--- Cleaning
rm failed for *, No such file or directory
--- Pushing zergRush"
721 KB/s (23052 bytes in 0.031s)
--- Correcting permissions
--- Executing zergRush
[**] 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.
[+] Found a GingerBread ! 0x00025118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] 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
2692 KB/s (1075144 bytes in 0.390s)
--- 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
" Your device should now be rooted. "
" "
" It's time to update your su binary. "
" Open the Superuser app, go to Preferences (Menu\Preferences),"
" and hit Su Binary v3.X (3.0, in this case). When prompted, "
" update to the newest version of the su binary. "
" Congratulations, you've successfully rooted! "
" If something went wrong, pm apapousek on the XDA Forums"
" or email anthony@papousek.org "
Press any key to continue . . .
also tried SuperOneClick. didn't work
any rom attempted from Recovery Mode gives (No space left on device) error.
anyone? Bueller?
Have you tried to use towelroot? It should work considering the kernel on these devices are really old and are not patch against the vulnerability that towelroot uses.
Here's it's link:
https://towelroot.com/
Hope it helps!
Can't you force root with towelroot? I was pretty sure you could before. In the case you can't do it, you could try to use kingo root. Here's an article from CNET about it:thanks for the link. but it didn't work.
in app message says "this phone is not supported"
get give download link for the SAMSUNG USB Driver for Mobile Phones installer? thanks
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XXKPF
ro.build.version.incremental=XXKPF
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Fri Sep 16 20:45:13 KST 2011
ro.build.date.utc=1316173513
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-67
ro.build.tags=release-keys
ro.product.model=YP-G70
ro.product.brand=samsung
ro.product.name=YP-G70
ro.product.device=YP-G70
ro.product.board=YP-G70
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=YP-G70
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=YP-G70-user 2.3.5 GINGERBREAD XXKPF release-keys
ro.build.fingerprint=samsung/YP-G70/YP-G70:2.3.5/GINGERBREAD/XXKPF:user/release-keys
# Samsung Specific Properties
ro.build.PDA=G70XXKPF
ro.build.hidden_ver=G70XXKPF
ro.build.changelist=562492
ro.csc.sales_code=SER
ro.flash.resolution=720
# end build properties