Related
Hi , greeting everyone !
Before appearing ICS, I made a small update custom, including small changes in the original firmware 3.2.79.
This release is permanently ROOT, busybox is installed proper and is unique , Su and Superuser is up to date ! At the bottom you have Update of this version (activated vibrator and fixed adb command).
Included : 24/01/12
- new boot animation;
- battery percentage, and other new Icon;
- several applications in addition ( office free, flashplayer 11,adobe air.....+++);
- windows animations;
- Sony Ericsson Xperia Arc sound and other stuff.....
Now we have latest update of Su binary v3.0.3.2 , Superuser v3.0.7(41), unique busybox v1.19.3 installed into system/xbin ;
There is no need to install busybox.apk or busybox installer.apk from market, busybox is already installed into /system/xbin/
Also included some tweaks : - increase sdcard speed, - managemant ram memory....and increase reaction speed !
These are the files you need for install this Custom Rom :
- archos.ext4 => http://www.4shared.com/archive/tOxGcPqa/archos.html , http://hotfile.com/dl/143897684/d5edc5d/archos.7z.html
- zImage => http://www.4shared.com/file/KXp8bLDa/zImage.html ; http://hotfile.com/dl/144036333/e7d0e75/zImage.html
- initramfs.cpio.gz => http://www.4shared.com/zip/HnEobpnG/initramfscpiogz.html
How install :
- because the file structure is changed , you need perform a clean installation : Recovery -> Format System -> Reformat Devices...-> I Understand -> ok -> copy firmware_archos_it4.aos into new driver -> ok. After reboot copy archos.ext4 into Internal Storage ( data/media/), 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 ....now you have clean install custom rom
Solved - md5sum into superuser when you try to update the su binary , now check md5sum OK!
I did not managed any version of .squashfs because android compiler can't install busybox into system/xbin ( .squashf is NOT RW ), this is why I presented only version of ext4 ...Good Luck !
****************************************************************
Update : 27/01/12
- now >adb shell - fixed and enabel vibrator
- archos.ext4 => http://www.4shared.com/zip/dOscQIvA/archos_up.html ; http://hotfile.com/dl/143982123/b452656/archos_up.zip.html
What did you use to increase ram?
Sent from my HTC Desire HD using xda premium
Quinny899 said:
What did you use to increase ram?
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
Hi! ...I just increase free ram , lol !
surdu_petru said:
Hi! ...I just increase free ram , lol !
Click to expand...
Click to collapse
Ok
Sent from my ARCHOS 80G9 using xda premium
good job tomorrow i try it (multumesc )
Maryanos25 said:
good job tomorrow i try it (multumesc )
Click to expand...
Click to collapse
..cu placere ....incearca-l nu vei regreta !
with pleasure ...try it...you'll no regret !
Nu ama avut rabdare si l-am instalat. Merge ok. Merci mult.
Y dont have patience and y instaled. Its ok. Thanks.
Sent from my ARCHOS 80G9 using xda premium
Quick question, and I appologize if this is the wrong place for this, I'm currently running your 3.2.78 (ext4). Do I need to update the stock firmware directly from archos first or can I just flash this 3.2.79 rom over what I currently have. Also I "removed android kernel" earlier to always boot rooted if that matters. So what's the best way of going about this?
surdu_petru said:
I did not managed an version of .squashfs because I can't install busybox into system/xbin ( .squashf is R/O ), this is why I presented only version of ext4 ...Good Luck !
Click to expand...
Click to collapse
You can try this:
-get a copy of busybox and symlinks from a working rom (make a .tar or .tar.gz of G9's [email protected])
-copy busybox+symlinks in appropriate directories and chmod them (just to be sure)
-mksquashfs
This *should* work (I've messed around a bit with squashfs on another device)
First custom rom i've seen. Great ! Thank you very much. I will try it later
First thank you surdu_petru Every new rooted/modified rom, I need to start tablet with "original" rom to copy the ext rom into the tablet, and every time, restarting for the first time after the update from sde with the "new" rom, I have SuperUser with empty list (and I have to re-add all the programs in my list). Is there a way to copy the ext rom without booting with original rom? thank you and sorry for my poor english
hitman72 said:
Is there a way to copy the ext rom without booting with original rom? thank you and sorry for my poor english
Click to expand...
Click to collapse
Not yet, accessing /data/media requires a working system (adb is not present in SDE/recovery)
However you should be able to update using "previous" custom firmware- system filename is different
install directly over the version rooted 3.2.79.
Work good. =)
Boot animation - maybe simply text android install? =) Can i change it himself?
gen_scheisskopf said:
You can try this:
-get a copy of busybox and symlinks from a working rom (make a .tar or .tar.gz of G9's [email protected])
-copy busybox+symlinks in appropriate directories and chmod them (just to be sure)
-mksquashfs
This *should* work (I've messed around a bit with squashfs on another device)
Click to expand...
Click to collapse
OK thanks !....but do not want to complicate ... I let the compiler to perform, if he says he can not because I have not rw rights !...I left it ..... I know that there are solutions, but leave it in for users !
ro4sho said:
First custom rom i've seen. Great ! Thank you very much. I will try it later
Click to expand...
Click to collapse
Thanks , lol....
gegabit said:
install directly over the version rooted 3.2.79.
Work good. =)
Boot animation - maybe simply text android install? =) Can i change it himself?
Click to expand...
Click to collapse
Sure, you can change what you want, system is RW, but attention ! do it carefully !
gen_scheisskopf said:
Not yet, accessing /data/media requires a working system (adb is not present in SDE/recovery)
However you should be able to update using "previous" custom firmware- system filename is different
Click to expand...
Click to collapse
In my builds, I added a mechanism to do that, the idea was to add a ".update" to filename to have the initrd replace the old image with the ".update" image before mounting and booting.
Surdu_petru, I don't know if you did the same in your initrd. As gen_scheisskopf mentioned in the sde thread, wiping dalvik-cache is probably a good idea if build changes, it could be done silently there or asked with a menu ? And a common file naming convention between us would help, I saw that you use the archos.img, we could define this as a standard ?
letama said:
In my builds, I added a mechanism to do that, the idea was to add a ".update" to filename to have the initrd replace the old image with the ".update" image before mounting and booting.
Surdu_petru, I don't know if you did the same in your initrd. As gen_scheisskopf mentioned in the sde thread, wiping dalvik-cache is probably a good idea if build changes, it could be done silently there or asked with a menu ? And a common file naming convention between us would help, I saw that you use the archos.img, we could define this as a standard ?
Click to expand...
Click to collapse
Ok I know what you mean...and yes ! for Stock firmware_3.2.79 (files.ext4/squqsh).update exist into initramfs, but because I made some changes in directory structure into Custom Rom , now .update it's not perform .
Ok it's very good idea , for future I'll rename (archos.ext4/squashfs).update
Thanks for your advice !
surdu_petru
will there be a custom rom for the archos 80 g9 250hdd or a root method
it would be nice to have a custom rom on my hard drive tablet
root method only seems to work on sd card versions of this nice tablet
regards phil
philmein said:
surdu_petru
will there be a custom rom for the archos 80 g9 250hdd or a root method
it would be nice to have a custom rom on my hard drive tablet
root method only seems to work on sd card versions of this nice tablet
regards phil
Click to expand...
Click to collapse
Hi!
This custom rom it's work for G9 tablett 80/101 but I don't know if it is supported for HDD.....maybe @letama or or another endorsed person will answer.....for you !
How can I make it work on stock firmware for my Ace. I put newest firmware on my phone, rooted it and tried to install CronMod.. After install phone booted but still shows 147 MB of memory. How can I make it work?
Thread moved to Q & A section.
palito1980 said:
How can I make it work on stock firmware for my Ace. I put newest firmware on my phone, rooted it and tried to install CronMod.. After install phone booted but still shows 147 MB of memory. How can I make it work?
Click to expand...
Click to collapse
One of the prerequisites of the script is that it requires init.d support
If your ROM has a folder /system/etc/init.d/ only custom roms have this feature afaik.
U need to change kernel for that !
Check nims1 kernel, or battery extender ... or psn
121C4 said:
One of the prerequisites of the script is that it requires init.d support
If your ROM has a folder /system/etc/init.d/ only custom roms have this feature afaik.
Click to expand...
Click to collapse
Nope. As long as the kernel supports int.d folder, he's good to go. He just needs to flash a custom kernel with int.d folder supported.
____________________
Sometimes I wonder about being a success in this mediocre world
CallMeLewis | Yeowwwai
I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
i'll try this
kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Seems that disabler zip did not work.
Any other brilliant ideas................
Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk
kingvortex said:
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.
Rooks said:
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.
Click to expand...
Click to collapse
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.
Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Only brilliant idea here was flashing something before backing up your rom.
Sent from my Nexus 5 using Tapatalk
GermainZ said:
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.
Click to expand...
Click to collapse
I did not mean to be rude or ANY disrespect.
So guys, PLEASE point me to right direction so that i can bring back my device.
rovo89 said:
In case you get into a boot loop:
First, try using the safemode by pressing any hardware key repeatedly. You can find a short explanation how it works here.
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
rovo89 said:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Where can i find disabler zip file?
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Rooks said:
Where can i find disabler zip file?
Click to expand...
Click to collapse
From the linked post:
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
Rooks said:
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
GermainZ said:
From the linked post:
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
Click to expand...
Click to collapse
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.
Rooks said:
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.
Click to expand...
Click to collapse
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.
Rooks said:
Yes i've tried three different files, all failed to install.
Click to expand...
Click to collapse
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?
Rooks said:
Where can i find disabler zip file?
I downloaded some file from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.
GermainZ said:
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.
Click to expand...
Click to collapse
I'll try to get logcat for this issue.
rovo89 said:
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?
Click to expand...
Click to collapse
Yes, it's the stock recovery and i've tried several times with hardware keys but safe mode did not work in my scenario.
esgie said:
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.
Click to expand...
Click to collapse
I've tried three different file with different sizes (143kb, 121kb and 145kb), all these files include the same script ("updater-script" file) by Tungswenty.
ui_print("");
ui_print("");
ui_print("------------------------");
ui_print(" Xposed disabler tool ");
ui_print(" by Tungswenty ");
ui_print("------------------------");
ui_print("");
ui_print("Mounting system partition");
ifelse(!is_mounted("/system"),
run_program("/sbin/busybox", "mount", "/system"));
assert(is_mounted("/system"));
ifelse(run_program("/system/bin/sh", "-c", "test -f /system/bin/app_process.orig") == 0,
(
ui_print("Restoring the original app_process file");
assert(run_program("/sbin/busybox", "cp", "-a", "/system/bin/app_process.orig", "/system/bin/app_process"));
set_perm(0, 2000, 0755, "/system/bin/app_process");
ui_print("Restore complete.");
ui_print("You should now be able to boot normally and remove all traces of Xposed from within the Installer app.");
),
(
ui_print("No backup found for app_process, nothing to be performed!");
));
ui_print("");
ui_print("Done.");
ui_print("");
Click to expand...
Click to collapse
Rooks said:
Yes, it's the stock recovery
Click to expand...
Click to collapse
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).
rovo89 said:
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).
Click to expand...
Click to collapse
I've stock rom and recovery, there is no custom rom or recovery available for my device (Toshiba Excite 10 SE aka AT300SE).
So with stock rom and recovery it won't accept any zips and i can't format system partition with stock recovery. And about adb, i don't know where to start. In recovery there is an option to push a file through adb but when i connect my device while this option, my pc does not recognize the device, neither i can update the adb drivers.
Rooks said:
I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.
Click to expand...
Click to collapse
HOW YOU ROOT...???!!!
PLEASE TELL ME
I CANT FIND IN WEB....
Give me a links if you can ....
THANKS
Can someone make a dual boot kernel for i9305?
dnm3 said:
Can someone make a dual boot kernel for i9305?
Click to expand...
Click to collapse
up
up
Any developer can make a application to swich rom (install internal/external kernel)? like: http://forum.xda-developers.com/showthread.php?t=2639112 (or edit this)
All need is keep Manage Roms (tab) options ...
If is select Set this rom as Internal/External , app make a copy of boot.img
And if select Boot internal/external rom, app install boot.img (from internal/external) and reboot
(and if is possible to edit update.script / fstab mounts..is grate..but first time (if is easy) need to set and install roms.
So?
I'm working now on a .sh script for dual-boot...
il3gal said:
I'm working now on a .sh script for dual-boot...
Click to expand...
Click to collapse
Sorry for triple ! (i can delete two messages)
Who want to test with me a Dual-Boot script. PM !
I use Nameless 2.0 rom and for me it works (work only with rom who have boot.img file inside (for a moment))
I tested with RR and CM12 and it work's.
Is there anyway someone can make an addon.d script for both magisk and the phh root? There's a similar script that you can find here that does this for xposed. Also, the Gapps use it. This would be very helpful so we don't have to reflash the scripts everytime.
Link_of_Hyrule said:
Is there anyway someone can make an addon.d script for both magisk and the phh root? There's a similar script that you can find here that does this for xposed. Also, the Gapps use it. This would be very helpful so we don't have to reflash the scripts everytime.
Click to expand...
Click to collapse
Ummm...
That makes no sense...
The magisk.img is in data... Survives dirty flash... The magical part of magisk... Is injected into the boot.img... Which, afaik, isn't possible via addon.d
Link_of_Hyrule said:
Is there anyway someone can make an addon.d script for both magisk and the phh root? There's a similar script that you can find here that does this for xposed. Also, the Gapps use it. This would be very helpful so we don't have to reflash the scripts everytime.
Click to expand...
Click to collapse
That makes no sense like the other guy said & only works with ROMs that have implemented that function (generally update-script that calls a script in root of the zip in CyanogenMods). If you install any ROM that have not that function, then nothing is backed up & /system is replaced as regular.
Addon.d is simply a folder with .sh scripts that are run when flashing a new rom update. Obviously, this won't work with stock roms but it should work for Lineage OS and similar roms I think. Sadly I don't know how to write .sh scripts.
Link_of_Hyrule said:
Addon.d is simply a folder with .sh scripts that are run when flashing a new rom update. Obviously, this won't work with stock roms but it should work for Lineage OS and similar roms I think. Sadly I don't know how to write .sh scripts.
Click to expand...
Click to collapse
Learn Bash, is easy to do like check how works other .sh scripts or if you are lazy search tutorials in Google xD...
Old thread, but I just discovered this "Flash After Update" script (actually @osm0sis pointed it out to me) which will flash any zip in a designated folder after flashing rom update.
osm0sis said:
99-flashafterupdate.sh addon.d script (many devices) - attached
For ROMs that don't have "Flash After Update" support built into their delta/update process. During an upgrade, this script will flash zips from a sdcard directory after all other addon.d backup/restore actions have completed. This can be used to flash SuperSU and then an AnyKernel2 kernel on CyanogenMod, for example. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
Click to expand...
Click to collapse
Especially handy if you keep your device unrooted, and can't use a tool such as this:
https://play.google.com/store/apps/details?id=se.davison.autoflasher
Link_of_Hyrule said:
Is there anyway someone can make an addon.d script for both magisk and the phh root? There's a similar script that you can find here that does this for xposed. Also, the Gapps use it. This would be very helpful so we don't have to reflash the scripts everytime.
Click to expand...
Click to collapse
Have a look at this:
https://github.com/topjohnwu/Magisk/issues/175
So is he integration the feature directly into Magisk?
Why don't you submit the changes as a pull request?
Edit: Tested the script. I can use the official Lineage OS updater now! No need for a third party app to auto flash Magisk want update.
Sent from my Nexus 7 using Tapatalk