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*
This is the account of my foolishness and I advice everyone not to follow it.:::
1.installed Linux installer std and complete Linux installer from play store.
2.when the 2nd app failed to unmount and GUI crashed showing some errors with busybox, followed 3rd step.
3. found the embedded busybox from 1st app n directly placed it in /system /xbin
4. the original busybox is gone n everything is fine but got too many errors in reading root directory of phone. None of the file manager is showing me root.
5. I'm suspecting that it has done something wrong with my cwm recovery as well for which I can't take a chance of bricking my phone.
6. NOW I need kind advice of u ppl on how to confirm the presence of recovery.img or whatever it should be to recover my cwm backed up data.
boot into recovery, if recovery do not boot then pull battery and start the mobile it will start normally, download busybox installer from play store (the one from stephen)
install busybox through the app(busybox problem will be solved)
download tass recovery cwm.tar file and flash with odin you will get cwm recovery back
did it
I've already tried busybox installers. non of them worked cause the whole root directory is unreadable to any of my apps except diskusage n similar things those show memory occupied.
then you should flash firmware and root again
Superuser
maybe update superuser binary?
solved
chmod 777 path name n got busybox 1.12
You lost root access because there is no busybox. Reflash the ROM. Easy way out.
nothing lost at all just replaced.
as I've stated the command above u, it was just a busybox w/0 permissions. I was getting permission denied.
thanks to Gael péron for his Help.
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.
Hey there browsing with all those ads is a real pain, therefore i wanted to edit the hosts-file since adaway didn't worked.
Therefore i wanted to use the content of this page and add it to my hosts-file:
http://someonewhocares.org/hosts/
problem is, i can't mount /system with total commander although root is working (flashtool installed busybox fine as the root popup comes up and asking for root).
the bootloader is unlocked and via adb shell in root mount i also get:
Code:
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
is there another way? can i somehow flash the hosts-file trough recovery?
You must not have full root. Install RIC Killer or XZDR to defeat this protection.
i thought only "temp root" existed besides the full root? well NUTS Dual Recovey is also installed... gonna check out the RIC Killer...
:Edit: Ok, neither the "Windows" RIC-Reboot Remount Fix worked, as the ZIP-Version trough Dual Recovery....
what would be the best way to reinstall root (altough it is an system app?)
The command you specified works fine for me. Further, root explorer via ES Explorer.
What root APK do you have installed? SuperSU, for example, has a "complete unroot" command you can use unroot.... but since there's no one-click root for 5.1.1, re-rooting isn't possible without reflashing. I suppose a dirty flash back over top 51.1 isn't as risky as between versions, so you could try that in order to re-root.
How did you root initially? My process for 5.1.1 has been to flash the FTF, SuperSU, and XZDR all in one go, no reboots between. People have had issues getting full root to work especially if the SuperSU and XZDR steps are separated by a reboot.
sorry for the long pause i was at vacation and there i had no chance to try something (since a backup would be needed first in case of fire )
I've been installing a prerooted tft the day 5.1.1 came out. RIC Killer didn't worked and fully unrooting well... doesn't work either
Flashing a zipped SuperSU or something like that won't work? I mean - i can unroot it go to XZDR and flash it again - this should work right?
Exactly what it says title. My phone is both I think rooted and unrooted.
I tried all the possible rooting methods, none of it are working. Only thing worked was unbricking the phone. Right now on stock 4.4.2.
Trying to use ioroot25 but phone get stuck when it does adb recovery reboot. Dead android with red escalation mark.
Kingroot total failure.
Ran I think ioroot5?; \
Code:
Mounting system RW and pushing 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
3671 KB/s (1468798 bytes in 0.390s)
pkg: /data/local/tmp/superuser.apk
What should I do
GUYS I need help. I just did a fresh install of stock VS980 23A. the custom recovery still has showing me a red mark. But this time in fastboot, it shows UNROOTED Before it showed rooted
Does this mean my phone was 'half rooted?
Ok, I have honestly hit the wall. I don't know what way out.
Only way out I thought was if I could push the TWRP files via adb i could fix it to bypass the restrictions but I can't. When I try pushing loki_tool and twrp.img via adb using ioroot folder, I get "permission denied".
I can't access the stock recovery because from the Googling I did, the stock recovery is corrupted and requires custom recovery. How the hell can I get custom recovery in if I can't even access the adb root permission.
Yes I tried the 'su' in adb method, it doesn't even recognize the command.
Going to google if I can install TWRP/custom recovery for lg g2 vs980 using download mode.
Victory! All those lame ass tools, loki_tool, lg_one_click_root, iorootv25-1-2-3-5 version. None worked!!
But this bad boy did it! -> http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906