Database Develop

[Q] latest MIUI vs EXT2 partition and A2SD, problem

Hi!
Quick question to everybody. Recently I've installed MIUI 1.5.20 on my MM, before that parted SD into FAT32(7GB, primaty+active)+EXT2(1GB, primary). Now in Settings>System>SD, in section A2SD+ it says "This device does not support A2SD+", is there something more that I should have done to make it work properly?

DrNO[PL] said:
Hi!
Quick question to everybody. Recently I've installed MIUI 1.5.20 on my MM, before that parted SD into FAT32(7GB, primaty+active)+EXT2(1GB, primary). Now in Settings>System>SD, in section A2SD+ it says "This device does not support A2SD+", is there something more that I should have done to make it work properly?
Click to expand...
Click to collapse
Nothing is wrong with it as far as I know. I had the same "issue" as well and my ext2 partition worked fine. I think it might just be because of the ext2 partition not being a native feature to the Milestone? Everything is fine though, don't worry

ok... so how can I check if it works? afaik it should hold apps relocated to SD, so if i go via root explorer to sd-ext folder (mount point), .apks should be there, right?

DrNO[PL] said:
ok... so how can I check if it works? afaik it should hold apps relocated to SD, so if i go via root explorer to sd-ext folder (mount point), .apks should be there, right?
Click to expand...
Click to collapse
Yes. Also you can try looking at /system/app and it might be there as well.

thx a 1M going to try it out... after reflashing with own-modified version from a scratch :]

unfortunately, /sd-ext is still empty.
ok, can any one tell me what are the correct steps, am I missing something? here is what i did:
1. factory reset (org froyo)
2. partitioned SD:
a) FAT32 7GB primary active
b) EXT2 1GB primary
3. rsd lite > g.o.t. 2.2.1 + open recovery 1.46 + or-extfs-update2 + V6supercharge
4. full wipe
5. applied miui 1.5.20 + minor fixes
should it work already(?)

DrNO[PL] said:
unfortunately, /sd-ext is still empty.
ok, can any one tell me what are the correct steps, am I missing something? here is what i did:
1. factory reset (org froyo)
2. partitioned SD:
a) FAT32 7GB primary active
b) EXT2 1GB primary
3. rsd lite > g.o.t. 2.2.1 + open recovery 1.46 + or-extfs-update2 + V6supercharge
4. full wipe
5. applied miui 1.5.20 + minor fixes
should it work already(?)
Click to expand...
Click to collapse
Which MIUI are you using? Did you try rebooting the phone after you restored all your apps?

PROBLEM SOLVED
it's latest MIUI 1.5.20, solution as follows:
1. after installing MIUI, flash via AOR >>THIS script
2. reboot device to the OS and instal (from market) "A2SDGUI"
3. reboot device (just to be sure)
4. njoy
later in mentioned app, you can set dalvik location and/or initiate swap
(@Admins/Mods: for me thread to be closed, thx)
thanks goes to skwara for advice, tkirton for script and skadude66 for trying to help

DrNO[PL] said:
PROBLEM SOLVED
it's latest MIUI 1.5.20, solution as follows:
1. after installing MIUI, flash via AOR >>THIS script
2. reboot device to the OS and instal (from market) "A2SDGUI"
3. reboot device (just to be sure)
4. njoy
later in mentioned app, you can set dalvik location and/or initiate swap
(@Admins/Mods: for me thread to be closed, thx)
thanks goes to skwara for advice, tkirton for script and skadude66 for trying to help
Click to expand...
Click to collapse
Glad it works I'm guessing when you say latest 1.5.20, you're talking about miuiandroid.com's version of MIUI? Because eybee1970's version includes automatic app2ext scripts and shouldn't be that hard to use.

right... you asked about whose release is it, it's not quite original, but based on it. skwara@android.com.pl makes PL version better suited to our local demands, there's no preinstalled app2ext. maybe that's even better, rom is lighter, and more open to your own way of customisation ;P hope someone will find this thread useful if he/she is not using eybee1970's version

[ROM] (CWM) HoneyComb Froyo V.3 (06-07-11)

It is New release of HoneyComb Froyo Builds ...
* Working :
- Everything except Camera & BT
- Downloading from market may take long time to start at first time ..
* Features :
- Very Stable & Fast & Smooth Froyo CWM build ..
- Very Fast Wifi with No Dropping ..
- Very Good battery life ..
- Neocore : 25.6 FPS
* Kernel Related issues :
- You may not hear voice during incoming call > Just activate the speaker & deactivate it again to solve this issue ..
- Charging while in android isn't working > You should connect the charger before hitting (haret.exe) ..
-----------------------------------------------------------------
* Installing instructions :
1- Format SDcard To 4 Partitions :
- 1- partition: FAT32 (SDcard / Rest)
- 2- partition: EXT2 (System / about 250 MB )
- 3- partition: EXT2 (Data / about 450 MB)
- 4- partition: EXT2 (Cache / about 100 MB)
* Make sure That all partitions are set PRIMARY ..
2- Extract Package & Copy [npkboot] Folder to root SDcard ..
3- Copy [HoneyComb Build V.3] To root SDcard without extraction ..
4- Run Haret & wait till it ask you to press Volume Down shortly to launch ClockworkMod Recovery ..
5- While In recovery menu , choose " install zip from SD card >>
choose zip from sdcard and select " HoneyComb Build V.3.zip " ..
- Then return back to main menu using " ok " key , Then choose " reboot system now "
6- Run " HARET.exe " & leave it to continue booting into Android ...
** For More info see THIS TOPIC
------------------------------------
** Very Important :
* Please don't install GAPPS after rom installation directly , Otherwise you'll have a serious problems ..
So you must :
1- Install HoneyComb V.3
2- Run the build
3- Restart it
4- Install Gapps
* Attached Kernel is highly overclocked , it may not work with all kovsky devices , so if it doesn't work with you, try to change the overclocking value from 652 to 614 mhz in startup.txt ..
- If it is still not working , replace this kernel with "Turbo kernel" attached to package ...
*********************************************
* Thanks To :
- Neopeek ( For CWM & Many others )
- TiaD8 ( Many tweaks & stuff taken from his builds )
- Highlandsun ( For his libs )
- People made these themes & icons .
- All other persons who i forgot to mention ..
**********************************
DOWNLOAD
^^^^^^^^^^^^^^^^^^
* On Screen Answer interface
* For Keyboard Freezing proplem
**********************************
If you like my work, Please just Don't Mirror my links ..
Don't Forget To click Thanks Button ...

* Installing instructions :
1- Format SDcard To 4 Partitions :
- 1- partition: FAT32 (SDcard / Rest)
- 2- partition: EXT2 (System / about 250 MB )
- 3- partition: EXT2 (Data / about 450 MB)
- 4- partition: EXT2 (Cache / about 100 MB)
* Make sure That all partitions are set PRIMARY ..
2- Extract Package & Copy [npkboot] Folder to root SDcard ..
3- Copy [HenDroiD_V2.zip] To root SDcard without extraction ..
4- Run Haret & wait till it ask you to press Volume Down shortly to launch ClockworkMod Recovery ..
5- While In recovery menu , choose " install zip from SD card >>
choose zip from sdcard and select " HenDroiD_V2.zip " ..
- Then return back to main menu using " ok " key , Then choose " reboot system now "
6- Run " HARET.exe " & leave it to continue booting into Android ...
** For More info see THIS TOPIC

finally.....great work man....!!! download now....

nice work !!!
needo why you delete languages from this ROM?? ( please return choose czech language in Settings )

are the Keypad drivers modules or not ?

RenEdi said:
nice work !!!
needo why you delete languages from this ROM?? ( please return choose czech language in Settings )
Click to expand...
Click to collapse
this build isn't supporting many laguages, but you can use morelocale ( Attached to this post )
djkarl said:
are the Keypad drivers modules or not ?
Click to expand...
Click to collapse
the separate keypad modules isn't included in this package , i think you wan't need it again > i'm using it for more than 8 hours with no keyboard stoppage ..

trying now

Tried it for 2 hours now. I had only one wifi connection lost. But that was the only error. Market works. It's fast and stable LOVE IT ^^

I'll give it a try asap! =)
is AZERTY keymap available ?

can someone make a video on how to Become the process we do start the haret I've done it many times k no can do let us help someone. instructions I pay close attention but nothing.
sorry my english!

tried this for a few hours and the build is quite solid and stable, but with all other android builds ive tried, the keypad freezes all the time for me. froze 3 times so far in 4 hours. guess i still cant use any android build until thats fixed in the kernels. ill try the turbo keernel tosee if its any better

i have a problem, it don't ask me: press volume down
Do you know why that is?
(Sorry for my bad English)

Gameforce said:
i have a problem, it don't ask me: press volume down
Do you know why that is?
(Sorry for my bad English)
Click to expand...
Click to collapse
When you start android and the code is displayed there is the pinguine on the top, wenn the pinguin disapear and the code begin at the top, than press vol down

wi fi
- Very Fast Wifi with No Dropping .. ---- NOT Working for me.. when i try to start wi fi my x1 reboots back in winmo
great speedy rom, very fast!!!!

neoofoox said:
When you start android and the code is displayed there is the pinguine on the top, wenn the pinguin disapear and the code begin at the top, than press vol down
Click to expand...
Click to collapse
Oke thanks,
And do you know how long i need to wait before the pinguine dissapeared???

great rom !! but if i make a call or get incoming call,,i can't found red and green button in my screen,,so i used red/green button in under screen..thank very much

Gameforce said:
Oke thanks,
And do you know how long i need to wait before the pinguine dissapeared???
Click to expand...
Click to collapse
It should apeare after 30-60sec (normaly shorter)

PsychoAssasin said:
tried this for a few hours and the build is quite solid and stable, but with all other android builds ive tried, the keypad freezes all the time for me. froze 3 times so far in 4 hours. guess i still cant use any android build until thats fixed in the kernels. ill try the turbo keernel tosee if its any better
Click to expand...
Click to collapse
you can use the kernel with separate keyboard modulus so you can activate it with one touch everytime it freazes ...
ncw2k69 said:
- Very Fast Wifi with No Dropping .. ---- NOT Working for me.. when i try to start wi fi my x1 reboots back in winmo
great speedy rom, very fast!!!!
Click to expand...
Click to collapse
i don't know the reason , but it may be winmo related or radio related , BTW try to enable wifi in Winmo & start android ...
vannanta said:
great rom !! but if i make a call or get incoming call,,i can't found red and green button in my screen,,so i used red/green button in under screen..thank very much
Click to expand...
Click to collapse
yes it was excluded , it is always getting distorted & some times doesn't work ...

neoofoox said:
It should apeare after 30-60sec (normaly shorter)
Click to expand...
Click to collapse
it depends on the SDcard contents , if there are many files & folders it'll take longer & so on ...

needo said:
it depends on the SDcard contents , if there are many files & folders it'll take longer & so on ...
Click to expand...
Click to collapse
Ah okay I didn't know. I have quite clean sdcard.
And I have one question. After Installing gapps (after launching android) everything worked fine and I never get a force close message. But after starting Android after reboot I get a lot of force close messages. (The process android.process.acore has stopped unexpectedly. Please try again.)
I use turbo kernel (this one in the turbo kernel folder @612mHz)
The included one didn't work. I pressed harret and then phone restarted (i tried both 652 and 614 mHz) Do someone know what's the problem? But that is not so urgent

[ROM] - Custom Rom Honeycomb 3.2.1 - firmware_3.2.79 , ext4 for SDE

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 !

[Gen9]Modified init for HDD and flash G9, 350MB & "no-busybox" archos.ext4

[Gen9]Modified init for HDD and flash G9, 350MB & "no-busybox" archos.ext4
Updated version- should work on HDD models too
Disclaimer: use this at your own risk. I'm not responsible if your tablet wants to kill you.
Here's modified init for suduru_petru's rooted 3.2.80 firmware
Now also for HDD models
Tests were done by philmein
Before you start
-make sure that you have more than 512MB free space in internal memory (/data) or more than 350MB if you want to use attached system file
Features
-system image runs from /data partition (internal flash)
-dalvik-cache wipe is done for system updates, also can be triggered manually
Installation
1. Install SDE menu- INSTRUCTIONS
2. Prepare required files- copy archos.ext4.update file to the root of the card (if you have archos.ext4 just rename it to archos.ext4.update)
NOTE this MUST be archos.ext4.update file, zipped files will not work
3. Boot to Recovery (Volume+ and Power), then Developer Edition Menu -> Flash Kernel and Initramfs. New drive will popup on your pc, copy kernel_test_hdd7.zip contents on it
NOTE- you need zImage and initramfs.cpio.gz files, zip will not work
Click Ok to flash kernel.
4. Now boot to Special Developement Edition
NOTE- first boot will take longer (files must be copied) so don't panic
5. Do not delete archos.ext4.backup file from storage- this is a backup in case you have to do data wipe (Reset Android)
6. Enjoy
Usage:
To update system: copy archos.ext4.update file to storage and reboot
To wipe dalvik-cache: place an empty file wipe-dalvik.update in the storage and reboot- you can use djnilse's script
If you had to wipe data (Reset Android): don't worry, just reboot
If you had to format storage: make sure that when system boots
Download:
Kernel and initramfs
http://dl.dropbox.com/u/14106051/archos/kernel_hdd_test7.zip
smaller archos.ext4.update
This is shrinked suduru_petru's rooted firmware, now only 350MB
No other changes done
http://www.mediafire.com/?eqwlocit0nniw7k
"No busybox" archos.ext4
http://www.mediafire.com/?fzizmy60e769ow9
This is only rooted archos.ext4.update, custom busybox seems to make problems with USB host functions
Info for developers: http://forum.xda-developers.com/showpost.php?p=22310057&postcount=13
Old version
What is changed
-dalvik-cache is wiped for every firmware update
-dalvik-cache wipe can be started manually
How does it work
Dalvik-cache wipe is higly recommended with every firmware update (or replacing stock with a modified one), also can help with app FC's.
For every firmware update- archos.ext4/squashfs.update file- dalvik-cache is wiped automatically (and you can't do anything about it )
To trigger dalvik-cache wipe on your own place a file named wipe-dalvik.update in internal storage (/data/media) and reboot.
NOTE: first boot after wipe will take longer
Installtion
Zip contains both zImage and initramfs.cpio.gz, installation as usual: Developer Edition Menu -> Flash Kernel and Initramfs then copy zImage and initramfs.cpio.gz to the new drive that pops up on the pc and click OK on the tablet.
DOWNLOAD
http://dl.dropbox.com/u/14106051/archos/kernel.zip
MD5: 8EB000BC1105A3613B35C8F82F35EF41
Info for developers: http://forum.xda-developers.com/showpost.php?p=22179468&postcount=8
EDIT:
Script for easy creating wipe-dalvik.update file by djnilse: HERE

hi, Let's see if I understand correctly. for updating is necessary first copy new firmaware and empty file called "wipe-dalvik.update" in /data/media. reboot table in sde and copy zImage and initramfs.cpio.gz. rebooting and delete "wipe-dalvik.update". is correct? thank you

hitman72 said:
hi, Let's see if I understand correctly. for updating is necessary first copy new firmaware and empty file called "wipe-dalvik.update" in /data/media. reboot table in sde and copy zImage and initramfs.cpio.gz. rebooting and delete "wipe-dalvik.update". is correct? thank you
Click to expand...
Click to collapse
Not exactly.
When firmware is updated -archos.[...].update file- dalvik-cache is wiped anyway without any option not to wipe it.
Wipe-dalvik.update file is needed if you want to wipe dalvik-dache eg. when apps have a lot of FC's.
But in order to have possibility to wipe dalvik-cache you have to flash modified init posted here (for ease of use zImage is included in zip, flash it as usual)
tapatalked from Desire

good work
this will be a better alternative for cleaning the system
i've made a script to write and remove the dalvik-wipe.update to storage
simply run it with ScriptManager or with a Terminal Emulator
this script doesnt need root rights
@gen_scheisskopf you could include a link to this in your post
and THIS IS NOT A test file
simply just rename it in dalvik.sh
run it with:
Code:
sh dalvik.sh
and dont forget to hit the thanks button
------------------------EDIT--------------------------------------------
don't hit the thanks button, this was not difficult
try to make a shell script on your own Here a tutorial have fun
-----------------------EDIT:10.02.2012------------------------------------
i ve removed the option to wipe the dalvik-wipe.update because its not necessary

djnilse said:
good work
this will be a better alternative for cleaning the system
Click to expand...
Click to collapse
Dalvik-cache wipe is included in all "standard" recoveries and it really can help in various situations (sometimes for bootloop also)
djnilse said:
i've made a script to write and remove the dalvik-wipe.update to storage
simply run it with ScriptManager or with a Terminal Emulator
this script doesnt need root rights
@gen_scheisskopf you could include a link to this in your post
and THIS IS NOT A test file
simply just rename it in dalvik.sh
run it with:
Code:
sh dalvik.sh
Click to expand...
Click to collapse
There is no need to remove wipe-dalvik.update, init does this just as with firmware .update files.
djnilse said:
and dont forget to hit the thanks button
Click to expand...
Click to collapse
Oh, c'mon......

gen_scheisskopf said:
Dalvik-cache wipe is included in all "standard" recoveries and it really can help in various situations (sometimes for bootloop also)
There is no need to remove wipe-dalvik.update, init does this just as with firmware .update files.
Oh, c'mon......
Click to expand...
Click to collapse
i worked for that about an hour, now i know more about linux shell scripts
and for the changes in the init
can it be modified with all kind of linux shell commands ???

djnilse said:
i worked for that about an hour, now i know more about linux shell scripts
and for the changes in the init
can it be modified with all kind of linux shell commands ???
Click to expand...
Click to collapse
Ask letama, he knows initrd best
tapatalked from Desire

I've checked supercharger script and honestly I'm not sure if it's absolutely safe to use:
-dalvik-cache wipe is done when Android does not run in every device I've layed my hands on (samsung i5700, htc desire, prestigio multipad 3384 and android hardware belonging to my friends)
-if dalvik-cache is not present system creates it during system boot
-supercharger wipes dalvik-cache also during system boot so there is a possibility of conflict between wiping and creating processes
Modified init wipes dalvik-cache before Android starts to boot so it is 100% safe, and djnilse created a nifty script to create wipe-dalvik.update file without pc access

New version in the first post
Should work good on HDD models also

How long is a long time?
I have had mine on the Archos logo for around an hour now, and just a little worried that it is not going through.
EDIT: I use the HDD model

thefunkaygibbon said:
How long is a long time?
I have had mine on the Archos logo for around an hour now, and just a little worried that it is not going through.
EDIT: I use the HDD model
Click to expand...
Click to collapse
Should be not more than a minute before bootanimation kicks in.
Did you boot to SDE with card inserted?

gen_scheisskopf said:
Should be not more than a minute before bootanimation kicks in.
Did you boot to SDE with card inserted?
Click to expand...
Click to collapse
There is no card reader on the HDD model, so I have it on the root of the HDD (I think I have understood that right, but maybe not.)
Do I need a USB card reader and do it through the 3G port?

thefunkaygibbon said:
There is no card reader on the HDD model, so I have it on the root of the HDD (I think I have understood that right, but maybe not.)
Click to expand...
Click to collapse
Sorry, I didn't know that there is no SD slot.
Give me 5 minutes.

Corrected version of initramfs and updated instructions in the first post.
Sorry for trouble, Archos says that all G9 devices have SD card slot.
EDIT:
Bug fixed, please redownload (same link)

gen_scheisskopf said:
Corrected version of initramfs and updated instructions in the first post.
Sorry for trouble, Archos says that all G9 devices have SD card slot.
EDIT:
Bug fixed, please redownload (same link)
Click to expand...
Click to collapse
You sir, are a genius! Working brilliantly (so far)
Thanks.

Another stupid bug fixed, please update
http://dl.dropbox.com/u/14106051/archos/kernel_hdd_test7.zip

i seem to have the file ext4 on my hdd and somwhere in my internal storage my internal storage has dropped by500mb
i know i should keep the one on my hdd but how do i get rid of the one in my internal storgage i would like to reclaim that space
i think its here /data/local/archos.ext4 but i cannot see it in astro or file manager
250gb hdd model

philmein said:
i seem to have the file ext4 on my hdd and somwhere in my internal storage my internal storage has dropped by500mb
Click to expand...
Click to collapse
It's normal (as expected)
philmein said:
i know i should keep the one on my hdd but how do i get rid of the one in my internal storgage i would like to reclaim that space
i think its here /data/local/archos.ext4 but i cannot see it in astro or file manager
Click to expand...
Click to collapse
The one on HDD is a backup file (in case of wiping data).
You can't delete the one from flash- that is system image.
I can try to modify init so system file runs from HDD (not internal flash) but this may deplete your battery very fast

if its normal thats fine i still have 500mb free
i have hdd test 3 on mine is that ok do i just updat to hdd test 7 when a new rom comes out?
regards phil

philmein said:
if its normal thats fine i still have 500mb free
i have hdd test 3 on mine is that ok do i just updat to hdd test 7 when a new rom comes out?
regards phil
Click to expand...
Click to collapse
Flash test7- it is updated version (cleaner work)

[Dualboot Patcher]Full Guide For How To DualBoot Your Note 4 (EXY/SD)

Dualboot patcher 101
Device : Galaxy Note 4
Difficulty level : Easy
This is a full guide to understand and use Dualboot Patcher App​
Download latest app snapshot from : Noobdev
Files » DualBootPatcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
Latest as of Jan 8 2017
Install it like a normal apk
Dualbooting begins here ---
Main things to do are
Setup Dualboot boot enviroment
Setup Dualboot files
Flashing
Switch between roms
App sharing
Part 1
Setting up for first time use
-Open dualboot patcher app and do the following
-Go to Roms tab then click the 3 dot menu on "Primary"
-Press Set Kernel {if it didnt ask you at the beginning}
-Then press "Update RamDisk"
Part 2
Patching Files for dualboot
-Download the rom you want to dualboot / any mods for it / xposed or whatever flashableZIP you want to install on your secondary rom
-Go to "Patch Zip File" Press the + and click "Add Flashable Zip"
-Select your ROM Zip
-Select your Device (Trelte For exynos or Trlte For Snapdragon)
-Select "Data slot" in Partition Configuration
-The ID is your parition name , basicly SAME ID for zips = Same flash location, Type rom1 for example [No caps]
-Do the same for any other zips (making sure the ID is the excat same)
Part 3
Flashing
Once you are done patching files , you will end up with a duplicate collection of your original files, but they end with _data-slot-[ID].zip suffix
-Grab those files and go flash them in your recovery
-in the recovery screen you will see [Multiboot] prefix behind most scripts, that means you are flashing a patched zip
-Once you are done flashing just hit reboot from the recovery
Part 4
Switching
You will be greated with your new rom , do the first setup and you are now running your secondary rom
Now, to switch roms do the following
-Install your dualboot patcher app on your secondary rom
-Open it and go to "Roms" Section
-Suprise, you will see Primary and below it [ID] (Data Slot)
-Press the primary and reboot , thats it
Part 5
App Sharing
Lets say you want your app data to be available on all your roms , Whatsapp data , telegram data , game data etc
-Open the app on your primary rom , go to "App Sharing" Section and enable " Share Individual applications"
-Press "manage shared applications"
-Click on an app "whatsapp for example"
-Tick "Use shared data"
-Hit ok then Then go back after selecting all your apps
-It must show a toast saying "The changes will take effect next reboot"
-Reboot your device to the secondary rom and do the same thing for the same apps
App data is now shared across both roms,
F.A.Q please read before attempting this
1- Faild to set kernel due to unrecognized device
-Common issue with custom roms, you can fix it by editing your Buid.prop , changing device name , code etc and ro.patcher
2- Flashing files via recovery , will it affect my primary rom ?
- No , all the files are directed to your new rom enviroment , the only things that can affect dualboot is kernel changes
3- How to change primary / secondary kernel ?
-To change primary , just flash the new kernel , then follow " Part 1 " of the guide again
-To Change Secondary , Follow " Part 2 " of the guide to patch the Kernel zip then flash in recovery
4- Where are the files located ?
-your secondary system can be found under /data/multiboot/data-slot[ID]/System (only seen when you are using primary rom or Recovery file manager)
-Your shared app data can be found under /data/multiboot/_Appsharing
5- Enabling app sharing, my data for the app is gone.
-When you enable app sharing it changes the data location, so whatever data you had need to be moved with it, best thing to do is to backup the app you want to share with titaniumbackup (before enabling shared data for it) then restore it when you enable data sharing and rebooting
6- How many roms can i "dualboot"
-As much as you like aslong as you have storage in your data partition i had 4 roms dualbooted at one point
7- How much storage does it consume ?
-CM roms are usually around 1GB for system + few GBs for data (total of 3GB-4GB For normal user with some apps)
-TW roms are heavier around 2-3GB for system (most bloated AF roms) and same for data
8- My secondary rom broke due to a mod or something, how can i switch roms in recovery ?
-Download dualboot utilites
-Files » Utilities : DualBootUtilities-9.1.0.r80.gd5920b2.zip
-Flash in recovery and it will give you an aroma installer enviroment to select your roms
9- Switch roms without aroma
-In TWRP select flash IMG option instead of zip
-Navigate to /internalmem/Multiboot/[ID]/boot.img
-select flash boot
-swipe to flash then reboot
10- Can i install a rom with aroma installer ?
-Yes , just make sure that the aroma does NOT reboot your device after completion as the dualboot script needs to run after the rom script is done to set the new kernel etc
—---------------------------
Hope this helps whoever wants to use this app , its very simple ,it might look complicated but its easy, GL and have fun
This guide can be used for other devices , Dont forget to hit thanks and reply if it helped.
All thanks for the original devoloper and poster @Anik_khan

First here
Will give it a try ASAP and post my feedback soon

I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?

the\downslash\ said:
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
Click to expand...
Click to collapse
If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Here is screenshot of my dualboot testing list

webmaster750 said:
If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Here is screenshot of my dualboot testing list
Click to expand...
Click to collapse
Very nice configuration, thank you

the\downslash\ said:
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
Click to expand...
Click to collapse
F.A.Q number 2 : Common issue with Dooola roms , and DN7 roms due to changes in codename
ro.patcher.device=hltedalvik.vm.dex2oat-filter=speed
This line needs to be fixed in doola build.prop
Changing it to
ro.patcher.device=treltexx Used to work for me But some people reported bootloops , so take a back up first just in case

I have the n910v im running red dragon rom and its showing gracelte and its not compatible ive asked for the correct line for the build.prop and havent gotten an answer as wbat line to change and what to change it to ... can anyone help me?

happy2472 said:
I have the n910v im running red dragon rom and its showing gracelte and its not compatible ive asked for the correct line for the build.prop and havent gotten an answer as wbat line to change and what to change it to ... can anyone help me?
Click to expand...
Click to collapse
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.

BluePhnx said:
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
Click to expand...
Click to collapse
ro.patcher.device=trlte ?

BluePhnx said:
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
Click to expand...
Click to collapse
This is what i get

happy2472 said:
This is what i get
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2447534&page=1099
This is the thread I got my info. Go to page 644.
That is what I used.
ro.patcher.device=trlte
Search for that thread for your model but I think it's the same.

BluePhnx said:
Tthttps://forum.xda-developers.com/showthread.php?t=2447534&page=1099
This is the thread I got my info. Go to page 644.
Click to expand...
Click to collapse
Nope still no good ... let me reboot and see

New

happy2472 said:
New
Click to expand...
Click to collapse
Are you on the latest version?

Wow im usually pretty good at doing this stuff ... is there a more simple set of i structions?

happy2472 said:
Wow im usually pretty good at doing this stuff ... is there a more simple set of i structions?
Click to expand...
Click to collapse
look for ro.product.device= instead of ro.patcher.device=
This worked for me -> ro.product.device=trlte

happy2472 said:
This is what i get
Click to expand...
Click to collapse
Sorry for late response. Your issue is due to your custom Rom changing treltexx names in prop to graceltexx. Usually renaming the changed text to treltexx must work. Use a file editor and search for any grace mention and make sure it says treltexx. Specially the device codename
And update the app It seems old
Sent from my SM-G935F using Tapatalk

Unable to access Roms after a Nandroid Restoration
After doing a nandroid back up in twrp... I restored with my 4 roms with the dualboot patcher....
Only one Rom boots and works the others dont work... whats causing this.... is there anyway to fix this because I have many good data on those roms....plus I would like to feel safe I can do a backup of my roms.

ananjaser1211 said:
F.A.Q number 2 : Common issue with Dooola roms , and DN7 roms due to changes in codename
ro.patcher.device=hltedalvik.vm.dex2oat-filter=speed
This line needs to be fixed in doola build.prop
Changing it to
ro.patcher.device=treltexx Used to work for me But some people reported bootloops , so take a back up first just in case
Click to expand...
Click to collapse
You mentioned making a back up... I have not been sucessfull in making a back up of this app roms... I used twrp and None of the Roms work after restoring the back up.

I got error while flashing zip file from recovery on my device... Seems like it does not support for "trltechn".
Help Please
Thanks a lot