Related
First ....THANKS @letama, and last but not least thanks to @tRAcE3k for .ext4 build.
Official Stock Firmware v3.2.79 => ROOT, Update : Su binary v3.0.3.2, Superuser v3.0.7 and busybox v1.19.3, Add : enables vibrator and adjust volume !
(There is no need to install busybox.apk or busybox installer.apk from market, busybox is already installed into /system/xbin/ - only for .ext4)
This ROM is only for SDE enable ( recovery) ....you can use it as a daily ROM...
These are the files you need :
- zImage => http://www.4shared.com/file/KXp8bLDa/zImage.html
- initramfs.cpio.gz => http://www.4shared.com/archive/6Y9sMqJ5/initramfscpio.html
- archos_3.2.79.squashfs => http://www.4shared.com/zip/-vo5gkRr/firmware_3279squashfs.html (...version without busybox and update!)
- archos_3.2.79.ext4 => http://www.4shared.com/zip/dmrcBtJM/3279_updat.html
How install this :
- connect device via USB cable
- adb push archos_3.2.79.squashfs data/media/ ........for read-only /system
- adb push archos_3.2.79.ext4 data/media/..............for read-write /system and other stuff
- reboot into recovery , Recovery System-> Developer Edition Menu -> Remove Kernel ( for boot only to SDE) -> I Understand -> Ok -> Developer Edition Menu -> Flash Kernel and Initramfs -> copy zImage and initramfs into new driver -> Ok ! that's all
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
hitman72 said:
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
Click to expand...
Click to collapse
No, you have to flash zImage and initramfs.cpio.gz in sde developer menu each time. First, filename changed and it's hardcoded in initramfs, second, Archos bugfixes are also in the kernel so new zImage is required.
Thanks surdu_petru for taking the relay!
letama said:
No, you have to flash zImage and initramfs.cpio.gz in sde developer menu each time. First, filename changed and it's hardcoded in initramfs, second, Archos bugfixes are also in the kernel so new zImage is required.
Thanks surdu_petru for taking the relay!
Click to expand...
Click to collapse
old firmware (3.2.77 etc) must be removed manually from device?
ext link is invalid "......". ciao ;-)
gegabit said:
old firmware (3.2.77 etc) must be removed manually from device?
Click to expand...
Click to collapse
When everything works, yes, you can remove the previous .ext4 from internal storage. That's the only thing you have to remove.
hitman72 said:
ext link is invalid "......". ciao ;-)
Click to expand...
Click to collapse
now its upload to share.
- archos_3.2.79.ext4 => /.......future upload ..... it's 512Mb ext4...........
Click to expand...
Click to collapse
Hi Folks.
Thought I'd do my bit. Here are some more sources to download the ext4 firmware.zip
http://www.multiupload.com/0OTX0D54XW
Thanks to surdu_petru for the original image and tRAcE3k for the repacking instructions in this post.
Thanks
Trev
hitman72 said:
hi, If I have your archos_3.2.78.ext4, can I copy only archos_3.2.79.ext4 to data/media? Or for every new rom is always necessary copy even zImage and initramfs.cpio.gz? thank you
Click to expand...
Click to collapse
[email protected] sure is right....on the ather hand, every new firmware ( ex. firmware_archos_it4.aos) has its own boot image ( boot.img = zImage + initramfs) -used to boot devices and has its own flash files / system files which are grouped in an archive ( contains - libraries, aplikations, and other stuff ) - used to run system android , and all these are closely linked ....I think you can now better understand how to use them, and why ......
hitman72 said:
ext link is invalid "......". ciao ;-)
Click to expand...
Click to collapse
Ok...Now is valid link : http://www.4shared.com/zip/bp7XjWzY/archos_3279ext4.html....
Good luck!
Downloaded the ext4 version and couldn't get it to work.
Only root through the ADB Shell functioned, anything else Superuser automatically got denied, even though in the Superuser app it was set to prompt.
Chmodded the su binary to 6755 and it started to work
droobey said:
Downloaded the ext4 version and couldn't get it to work.
Only root through the ADB Shell functioned, anything else Superuser automatically got denied, even though in the Superuser app it was set to prompt.
Chmodded the su binary to 6755 and it started to work
Click to expand...
Click to collapse
Ok! Now just upload new update .....
First off Thanks very much surdu_petru for the work!
Please excuse my novice ability here, but...
I'm not sure if I did everything correctly, but I don't have root anymore. (i did with 3.2.78)
I did the adb push of the archos_3.2.79 to /data/media
then did the flash of intramfs and zImage from the beginning of this post.
I rebooted into developer and Root Checker says i don't have Root anymore?
Do i need to chmod the SU binary now to fix? if so where is the SU binary located in the filesystem? (i'm not sure how i would execute that command, via adb?)
revere521 said:
First off Thanks very much surdu_petru for the work!
Please excuse my novice ability here, but...
I'm not sure if I did everything correctly, but I don't have root anymore. (i did with 3.2.78)
I did the adb push of the archos_3.2.79 to /data/media
then did the flash of intramfs and zImage from the beginning of this post.
I rebooted into developer and Root Checker says i don't have Root anymore?
Do i need to chmod the SU binary now to fix? if so where is the SU binary located in the filesystem? (i'm not sure how i would execute that command, via adb?)
Click to expand...
Click to collapse
OK! Try >adb shell chmod 6755 system/bin/su
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
revere521 said:
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
Click to expand...
Click to collapse
same problem here the chmod doesn't solve it.
Eacy root command runed gets a deny from superuser even when tel superuser to allow everything
revere521 said:
Thanks!
I ran adb shell chmod 6755 system/bin/su, the rebooted into developer again.
In file explorer, SU is listed as Readable:Yes Writable:no and hidden:no
Root Checker Basic still says i don't have proper root access, titanium backup and busybox show denied in the log.
I broke it lol, maybe i need to try again from the beginning.
Click to expand...
Click to collapse
.....after install all....try to update Superuser into Market......
Update doesn't help :-(
surdu_petru said:
.....after install all....try to update Superuser into Market......
Click to expand...
Click to collapse
Update doesn't help :-(
tryed the update fix of superuser also
Update of the su binarie failde at md5sum check
basd82 said:
Update doesn't help :-(
tryed the update fix of superuser also
Update of the su binarie failde at md5sum check
Click to expand...
Click to collapse
OK I know.....just wait max 1 hour and I'll uploaded the new archos_3.2.79 files...with it everything works perfectly ( I have tested all , root_explorer, es file explorer, Root Check ....it's OK !!!!!).
basd82 said:
same problem here the chmod doesn't solve it.
Eacy root command runed gets a deny from superuser even when tel superuser to allow everything
Click to expand...
Click to collapse
ok! but now problem was solved.....just redownload the new firmware_3.2.79 files , unpack and enjoy*
I flash my OB with v20o (smartflash - root), its ok, root,
Now i can flash with v20C.kdz , original p970H.
I used tool to extrat files ap and cp.
Root is a big problem.
Flash smartflash or kdz, bam my root bye.
How i can make file .zip to flash for CWM.
FLash it with R&D testtool + workaround, use cwm injection method (search for it).
Thats how you ll get your phone with the correct software + root
I found use cwm injection method, but is not clear to me.
When i flash with V20o - rooted, i used smartflash, after process reboot in cwm and install from zip superuser. Thats it i do.
After flash using smartflash phone reboot in cwm, send superuser and ok.
the question is how inject cwm. I read topic about this but is not clear for me.
Can you help me?
I can only guide you here again: http://forum.xda-developers.com/showthread.php?t=1512203
I think it doesnt work with smartflash. But if you use an already rooted version, there also is no need to inject
If you are in CWM, simply make a full wipe and you can install any custom ROM you want already.
Then there is no need to really root and boot it
in this topic
http://forum.xda-developers.com/showpost.php?p=23788913&postcount=170
File cp ap, flash smartflash, auto reboot in cwm mode, install SU.
how make cwm inject in file to flash? is the question.
Phone simple reboot in cwm after flash witch SF.
And don't send SU to phone in first boot, bye bye root, need flash again and send zip SU.
I want make this in other V20XX, its cool.
When you are in CWM, you need to flash superuser.zip, then you can restart.
And dont forget to wipe
How inject cwm in my files, i have files and i need how inject cwm. that it
N00BY0815 said:
When you are in CWM, you need to flash superuser.zip, then you can restart.
And dont forget to wipe
Click to expand...
Click to collapse
All this ok for me.
Simple i do, in my files, i want inject cwm. Only this so
I think is that
Op afraid that lg might know this and patch it. I call that's a bull. I don't think lg engineer didn't know how to use dd. As long as we have unecrypted bin file we can patch it. Btw, how can one conceal a patching method using simple dd when you have unpatch file and patched file to compare? Even I managed to figure it out. Op true intention known only to himself.
So, to patch your bin file: (this is done on ubuntu, i don't know if windows got dd)
1. Download cwm at http://download.clockworkmod.com/rec...8.1.3-p970.img to the folder where you keep your bin file.
2. Open terminal and cd to the same folder as above
3. What we need to find is the location where we're suppose to copy cwm into the bin file. dd is bit-stream reader and it will show us the location in term of bytes. We need to search for ANDROID! string. So type:
dd if=LGP970AT-00-V20b-SEA-XXX-JAN-02-2012+0_AP.bin| strings -n 8 -t d| grep ANDROID!
result:
1436661 ANDROID!
1703936 ANDROID!
6422528 ANDROID!
bla..bla..bla...
4. Look of the last entry which contain the ANDROID! string and take note of its byte location (6422528 in this case)
5. Now it's time to copy cwm into the bin file. Type:
dd if=<cwm.img> bs=1 seek=<byte location> conv=notrunc of=<rom.bin>
So in this case:
dd if=recovery-clockwork-touch-5.8.1.3-p970.img bs=1 seek=6422528 conv=notrunc of=LGP970AT-00-V20b-SEA-XXX-JAN-02-2012+0_AP.bin
6. That's it. Your rom is ready to be flash using smartflash tool. You can run the same command in step 3 to verify that cwm is succesfully copied into the bin file. If at the same byte location the ANDROID! string change to [email protected] then you're good to go.
Don't waste your bandwidth to download the op's file if you can do this yourself and beside there's nothing to test, not that op modified the rom in any way. You would be better off testing huexxx zues rom imho.
Savvy?
Edit: Forgot to add. Credit goes to people who found this rooting method. I didn't found it only take a look at it.
Sent from my LG-P970 using XDA App
Flash the *.tar.md5 file using Odin3 v1.87 as PDA or Heimdall (extract cache.img and recovery.img in *.tar.md5 file first). Make sure "Re-Partition" and "F. Reset Time" unchecked, "Auto Reboot" checked!
SuperSU v0.96 from Chainfire, SuperSU: "su" in "adb shell" without any prompt!
ClockWorkMod recovery 6.0.1.1
BusyBox v1.20.2-cm9
Remove all existing root and busybox before installing the new one
Fix busybox symlink, prevent it conflict to Android toolbox
sysrw and sysro script for remounting /system read write or read only
Backup /etc/install-recovery.sh script to /etc/install-recovery.sh.backup and /system/recovery-from-boot.p patch to /system/recovery-from-boot.p.backup if exists, so we can restore it if necessary
Single step for ClockWorkMod recovery and root!
Luigi2012SM64DS video tutorial: http://youtu.be/pAvze-VNzj8
UPDATE 16/01/2013:
- P3100 CWM recovery 6.0.2.7, SuperSU 0.99
UPDATE 17/09/2012:
- P3100 CWM recovery 6.0.1.3
- P3110 & P3113 CWM recovery 6.0.1.1
- P3113 Samsung recovery repacked from http://forum.xda-developers.com/showthread.php?t=1887077, thanks ruben00.
UPDATE 15/09/2012:
A modified Samsung recovery, now accept an update package signed by Google's testkey. The idea came from Chainfire's CF-Root. BIG THANKS for Chainfire.
UPDATE:
Recovery for P3110 or P3113 can be combined with my own cache.img for one-step recovery and root installation. Extract appropriate recovery and use heimdall to flash your device:
Code:
$ sudo heimdall flash --recovery recovery.img --cache cache.img
or create ODIN flashable package:
Code:
$ tar -H ustar -c cache.img recovery.img > CWM-6.0.1.1-SuperSU-0.96-BusyBox-1.20.2-P3110.tar
$ md5sum -t CWM-6.0.1.1-SuperSU-0.96-BusyBox-1.20.2-P3110.tar >> CWM-6.0.1.1-SuperSU-0.96-BusyBox-1.20.2-P3110.tar
$ mv CWM-6.0.1.1-SuperSU-0.96-BusyBox-1.20.2-P3110.tar CWM-6.0.1.1-SuperSU-0.96-BusyBox-1.20.2-P3110.tar.md5
Boot to Windows and flash using ODIN.
Tested on leaked 4.1.1 JellyBean for GT-P3100.
TIP:
- Disable notification in SuperSU settings!
- Reset the flash counter using Triangle Away from Chainfire
- Since my English very bad, you can follow [How To] ROOT- Galaxy Tab 2 10.1 [GT-P5113 / 5100 / 5110 & 4.0.4 UPGRADE or OEM] as a reference, thanks weltwon
Credit:
Google, Samsung, koush, Chainfire, codeworkx, dsixda, weltwon
Unroot and restore back 4.1.1 JellyBean stock OTA recovery:
Disconnect from PC and power off P3100
Boot P3100 to recovery mode (VOLUME UP + POWER)
Connect P3100 to PC
Extract signed_root_p3100.zip
Copy cleaner script to P3100 and then unroot P3100:
Code:
$ adb push cleaner /tmp/
$ adb shell
# busybox mount /system
# busybox mount -o remount,rw /system
# busybox mount /data
# busybox mount -o remount,rw /data
# busybox mv /system/recovery-from-boot.p.backup /system/recovery-from-boot.p
# busybox mv /system/etc/install-recovery.sh.backup /system/etc/install-recovery.sh
# sh /tmp/cleaner
# umount /system
# umount /data
Reboot from recovery menu.
Cheers!! :thumbup::beer: will try later
Edit** worked great!! Thank you :thumbup: 1+
Sent from my GT-P3100 using xda app-developers app
Thank you!!! Been searching for JB root everywhere!! Will try later!
After rooting, can app such as Root Explorer or Titanium Backup run without any problem?
greeny2010 said:
After rooting, can app such as Root Explorer or Titanium Backup run without any problem?
Click to expand...
Click to collapse
Disable SuperSU notification, Root Explorer or Titanium Backup can run without any problem.
ketut.kumajaya said:
Disable SuperSU notification
Click to expand...
Click to collapse
How then we give access to Apps ?
silentvisitor said:
How then we give access to Apps ?
Click to expand...
Click to collapse
Request dialog.
One-step recovery and root installation for P3110 or P3113
UPDATE:
Recovery for P3110 or P3113 can be combined with my own cache.img for one-step recovery and root installation. Extract appropriate recovery and use heimdall to flash your device:
Code:
$ sudo heimdall flash --recovery recovery.img --cache cache.img
or create ODIN flashable package:
Code:
$ tar -H ustar -c cache.img recovery.img > CWM-6.0.1.1-SuperSU-0.96-BusyBox-1.20.2-P3110.tar
$ md5sum -t CWM-6.0.1.1-SuperSU-0.96-BusyBox-1.20.2-P3110.tar >> CWM-6.0.1.1-SuperSU-0.96-BusyBox-1.20.2-P3110.tar
$ mv CWM-6.0.1.1-SuperSU-0.96-BusyBox-1.20.2-P3110.tar CWM-6.0.1.1-SuperSU-0.96-BusyBox-1.20.2-P3110.tar.md5
Boot to Windows and flash using ODIN.
UPDATE 15/09/2012:
A modified Samsung recovery, now accept an update package signed by Google's testkey.
348 + 65 downloads = 6 thanks, c'mon don't be a leech!
Please,can you pack latest CWM 6.0.1.3 for P3100 in .tar format for Odin (PC) ?Here it's the linl http://jenkins.cyanogenmod.com/job/android/7989/artifact/archive/recovery.img .Thanks a lot! Best Regards!
viasat said:
Please,can you pack latest CWM 6.0.1.3 for P3100 in .tar format for Odin (PC) ?Here it's the linl http://jenkins.cyanogenmod.com/job/android/7989/artifact/archive/recovery.img .Thanks a lot! Best Regards!
Click to expand...
Click to collapse
#1 post updated. I hope people will stop making a new thread in development section about how to root P31XX :silly:
do I
so if I have a P3113 and want the OTA update packages that are signed by google test keys-do I flash the samsung recovery and the cwm recovery 6.0.1.1
This is phenomenal work.
I will point my rooting posts to this single post, rooting couldnt get any easier with this
---------- Post added at 04:44 AM ---------- Previous post was at 04:40 AM ----------
nutpn said:
so if I have a P3113 and want the OTA update packages that are signed by google test keys-do I flash the samsung recovery and the cwm recovery 6.0.1.1
Click to expand...
Click to collapse
that would half work , since the OTA installer checks for recovery to be samsung.
But I think if your rom is deodexed it will fail because the OTA's normally patch both .apk and the .odex files
This is great work, but I think you need a better explanation of what each options does and how they are installed in your OP. Then people will have less questions and problems.
Thanks
I managed successfully to install a costume Recovery manager and Rooted my GT-P3100. oh boy! I thought that is never gonna happen anytime soon.
Though, I would recommend you to make the topic short and use latest version instead of giving me long of list of files on the attachment
Thank you so much, root is working just perfect, I managed to use softwares that require root with no problem.
Does it work on ICS 4.0.3 and 4.0.4 too?
Thanks for such a great job.
I have a gt 2 7.0 p3110 . I need to go back to stock /out of the box status. If I have the firmware,can I just do so by flashing said firmware from recover menu?
I also have a custom kernel. Will it get rid of the kernel?
shinydesert said:
Does it work on ICS 4.0.3 and 4.0.4 too?
Thanks for such a great job.
Click to expand...
Click to collapse
Personally, it worked on 4.0.4. I managed to Root and install CWM recovery.
I don't have an answer if it will work for 4.0.3.
I hope that help
Xdevillived666 said:
I have a gt 2 7.0 p3110 . I need to go back to stock /out of the box status. If I have the firmware,can I just do so by flashing said firmware from recover menu?
I also have a custom kernel. Will it get rid of the kernel?
Click to expand...
Click to collapse
To return to pure factory state, first use triangle away app 1.95 to reset counter to zero, then flash stock via pc odin, do not worry about counter, it will not increase with stock firmware, it increases only with custom firmwares or files flashed via pc odin
Sent from my GT-I9300 using xda app-developers app
hi all,
I was running my TX with advanced kernel v4, rooted:
http://forum.xda-developers.com/showthread.php?t=1922925
yesterday i installed Miui Security from here:
http://forum.xda-developers.com/showthread.php?t=1663222
Then the root is gone. I checked that /system/bin/su and /system/xbin/su are still there but they are inter-linking with symbolic link when i view them with root explorer.
fixes tried:
When i use ADB push trying to replace them, it said "too many symbolic links encountered"
I cannot remove both file as i cannot su in ADB shell.
I booted into CWM recovery but ADB is not enabled in CWM.
I reflashed the flashable zip in CWM to gain root access with no error message prompted, but after reboot into system the SU files are still the same
I reflashed the kernel with flashtools and fastboot, still no change applied to the phone.
Any idea?
finally got it fixed...
I rewrite the updater-script in the CWM flashable zip for root package to force remove both /system/bin/su and /system/xbin/su and rewrite them back.
Thanks for watching...
I've the same problem
Hi guys,
I've the same problem.
I've flashed my Xperia T with MIUI-3.11.22 rom.
I've activated the root permission on Security tab, but my phone doesn't give me the root access (I've tried to install adbd insecure and BusyBox but the result is "problem with root access".
Some ideas?
Thx
Model Number - GT-S5830
Android Version - 2.3.6
Baseband version - S5830XWKT3
Kernel Version - 2.6.35.7-perf-CL787041 [email protected] #1
Build Number - GINGERBREAD.XWKT7
Virgin Galaxy Ace S5830.... i cannot root it.
so far i've tried..( This Guide )
universal_gb_root_v25.zip / universal_gb_unroot_v9.zip
and...
upd_1.zip / unroot.zip
and.....
AceGingerRoot.zip
also tried superoneclick which cannot root it on any setting.
what have I overlooked ?
i had planned to root it, install CWM recovery and make backup of the Optus carrier rom, then instal custom rom.... maybe i should download australian rom from sammobile and flash that replacing the current optus carrier one.
also when i load into the default android system recovery (Pwr + home key), down the bottom there is a message in yellow saying...
-- Appling Muti-CSC --
Can't access to '/system/csc/OPP/system'.
i have no idea what that means.
simmo2302 said:
Model Number - GT-S5830
Android Version - 2.3.6
Baseband version - S5830XWKT3
Kernel Version - 2.6.35.7-perf-CL787041 [email protected] #1
Build Number - GINGERBREAD.XWKT7
Virgin Galaxy Ace S5830.... i cannot root it.
so far i've tried..( This Guide )
universal_gb_root_v25.zip / universal_gb_unroot_v9.zip
and...
upd_1.zip / unroot.zip
and.....
AceGingerRoot.zip
also tried superoneclick which cannot root it on any setting.
what have I overlooked ?
i had planned to root it, install CWM recovery and make backup of the Optus carrier rom, then instal custom rom.... maybe i should download australian rom from sammobile and flash that replacing the current optus carrier one.
also when i load into the default android system recovery (Pwr + home key), down the bottom there is a message in yellow saying...
-- Appling Muti-CSC --
Can't access to '/system/csc/OPP/system'.
i have no idea what that means.
Click to expand...
Click to collapse
If your phone is unlocked try to flash a fresh stock rom via Odin, maybe you don't have enought free space in your system patition
cheers i'll try that. freeing up some space.
also i dont know if it is locked to Optus (the carrier) or not, does it matter if it is ?
if so i might have to look into that....
simmo2302 said:
cheers i'll try that. freeing up some space.
also i dont know if it is locked to Optus (the carrier) or not, does it matter if it is ?
if so i might have to look into that....
Click to expand...
Click to collapse
hmmm... well aparently it IS locked to the carrier Optus network. - i dont kno how/if that effects it being rooted or not.
i tried to root the device with the gb_universal_v25.zip again, and then without rebooting installing CWM 5.0.26.
the CWM is there now. but still no root.
simmo2302 said:
hmmm... well aparently it IS locked to the carrier Optus network. - i dont kno how/if that effects it being rooted or not.
i tried to root the device with the gb_universal_v25.zip again, and then without rebooting installing CWM 5.0.26.
the CWM is there now. but still no root.
Click to expand...
Click to collapse
Do you have thinkdroid installed?
Viper The Ripper said:
Do you have thinkdroid installed?
Click to expand...
Click to collapse
OK, just had a terrible time with this, but i may have got it now..... (have tried to do as much research myself, so i dont be a noob and ask every noob question under the sun)
i ended up getting the crappers with it, so in the menu settings i did a factory reset.
and... got stuck in a boot loop.....
rebooted into recovery.. wiped data/factory reset, wiped cache, wiped davlik aswell.
rebooted, and still boot loop.
put Ace into download mode (Pwr +vol dwn + home), ran Odin multidownloader 4.38 and used proper firmware (one package) from sammobile and coopers_v1.0.ops, and reflashed stock FW onto the Ace.
successfully passed Odin, rebooted.. (cant remember if it worked right away or if i had to do another wipe session).... but got it working again...
went back into recovery (reverted back to stock now)... tried rooting with universal_gb_root_v25... didnt work... unrooted with universal_gb_unroot_v9.
tried for ages to find universal_gb_root_v26 but couldnt find a site that didnt want me to do a survey and give my mobile number... so i found (somewhere) a universal_gb_root_v25b.
rooted with that.... rebooted.. and checked with 3 different SU / root checkers... and each one says Root is Good ! Yay !
so now i'm going to go back and put on ClockworkMod Recovery 5.0.2.6 and then try some custom roms
still undecided which one to use. (ideally looking for one, lean, fast and stable considering how restricted the Ace is)
cheers for all your help.
simmo2302 said:
OK, just had a terrible time with this, but i may have got it now..... (have tried to do as much research myself, so i dont be a noob and ask every noob question under the sun)
i ended up getting the crappers with it, so in the menu settings i did a factory reset.
and... got stuck in a boot loop.....
rebooted into recovery.. wiped data/factory reset, wiped cache, wiped davlik aswell.
rebooted, and still boot loop.
put Ace into download mode (Pwr +vol dwn + home), ran Odin multidownloader 4.38 and used proper firmware (one package) from sammobile and coopers_v1.0.ops, and reflashed stock FW onto the Ace.
successfully passed Odin, rebooted.. (cant remember if it worked right away or if i had to do another wipe session).... but got it working again...
went back into recovery (reverted back to stock now)... tried rooting with universal_gb_root_v25... didnt work... unrooted with universal_gb_unroot_v9.
tried for ages to find universal_gb_root_v26 but couldnt find a site that didnt want me to do a survey and give my mobile number... so i found (somewhere) a universal_gb_root_v25b.
rooted with that.... rebooted.. and checked with 3 different SU / root checkers... and each one says Root is Good ! Yay !
so now i'm going to go back and put on ClockworkMod Recovery 5.0.2.6 and then try some custom roms
still undecided which one to use. (ideally looking for one, lean, fast and stable considering how restricted the Ace is)
cheers for all your help.
Click to expand...
Click to collapse
I'd tell you that if you didn't have enough space on the system partition, maybe you could try flashing THIS before rooting your device and then you'll try flashing root again so...
Try The Ultimatum
Sent From my GT-S5830.
Current Rom-The Ultimatum
Kernel-Fire OC Kernel
Audio Manager-BEATS
Hit Thanks you unthankful $*%$&. Its There For A Reason.
Samsung Galaxy Ace [GT-S5830] root method (Optus branded units and possibly others)
I tried many methods, and none would work with my Optus branded S5830. I assume it was partly due to having less than 1MB available on the /system partition. After some perseverance, it now has root, here was my method, hopefully it can help others.
Some files mentioned in this are available here: http://goo.gl/6XlwEx
1. Install Samsung USB drivers: SAMSUNG_USB_Driver_for_Mobile_Phones.exe
2. Install and setup (for atleast your android version) the SDK from Google (http://developer.android.com/sdk/index.html)
3. Ensure that the platform-tools (or which ever folder contains adb.exe) is in your system path variable (google it).
4. Put custom recovery image on sdcard: recovery-clockwork-5.0.2.6-galaxyace.zip
5. Turn off device, and boot to recovery (home + power)
6. Flash recovery-clockwork-5.0.2.6-galaxyace.zip and reboot
7. Turn off device, and boot to recovery again (home + power)
8. From a command prompt, run 'adb shell' it should drop you to a shell with root privileges (#).
Code:
> adb shell
#
9. Mount the '/system' partition from the custom recovery (mount partitions)
10. Make some room on your '/system' partition, delete Skype, Think Office, etc. You will need to do this as the bloatware has left no room for the su binary and SuperUser.apk
11. To get rid of skype or Think Office, from the command line type the following and then press enter.
Code:
# rm /system/app/Skype.apk
# rm /system/app/thinkdroid.apk
12. Extract universal_gb_root_v25.zip to a folder, and open another command prompt at .\universal_gb_root_v25\system\xbin and type the following commands:
Code:
> adb push busybox /system/xbin/
> adb push sqlite3 /system/xbin/
> adb push ssh /system/xbin/
> adb push su /system/xbin/
> adb push ..\app\Rootvalidator.apk /system/app/
> adb push ..\app\Supersu.apk /system/app/
13. Go Back to you 'adb shell' command prompt, and type the following to confirm the files have been pushed (you should not get a 'No such file or directory' message)
Code:
# ls /system/xbin/su
# ls /system/app/Supersu.apk
14. Set file access permissions (change mode) with the chmod command
Code:
# cd /system/xbin
# chmod 6755 su
# chmod 755 busybox
# chmod 755 sqlite3
# chmod 755 ssh
# chmod 644 /system/app/Supersu.apk
15. Now also copy the files you pushed to /system/xbin to /system/bin
Code:
# cp su /system/bin/
# cp ssh /system/bin/
# cp busybox /system/bin/
# cp sqlite3 /system/bin/
Code:
# reboot
The phone should reboot as normal,
17. Once in turn on USB debugging (google it). Go Back to you 'adb shell' command prompt (which will have quit the shell after the reboot) and type:
Code:
> adb shell
$
18. Note that this time there is likely a $ prompt, if so, enter the command 'su' and hit enter. SuperSU should pop up on your device asking for su rights, say yes. If you get the # prompt, you are now rooted.
Code:
$ su
#
19. As an alternative to steps 17 and 18, (after the reboot, before turning on USB debugging), you can just open Rootvalidator from your app drawer to test for root privileges. You will also notice the SuperSU and cwm_recovery apps now in the app drawer too.
If it hasn't worked, make sure you've followed the steps correctly, you can safely repeat them, or play with the file's (busybox, sqlite3, ssh and su) user owner/group owners so they match most of the the other files in '/system/bin' and see if it helps. USe 'ls -l', 'chown' and 'chgrp' (again, google their usage)
ie. as an example, below shows that 'busybox' is owned by user 'root' and group 'shell', to change the group ownership to root, i would type 'chgrp root busybox' at a root (#) prompt.
Code:
# ls -l
-rwxr-xr-x root shell 2007456 2008-08-01 22:00 busybox
-rwsr-sr-x root root 311872 2013-12-08 09:09 su
- The End -
I think you should you should flash a stock rom via odin.