Database Info

Guide to make a2sd work in custom roms

hello.i open this thread to show you how to solve a2sd not working on custom roms so you people can use your favorite rom with all the features and rom developers can continue developing of their rom and make them more and more better.
First of all the reason why a2sd dont work and ext partition doesnt mount:
for these feautures and others that dev gives as with his rom,the kernel ramdisk is modified (by xda kitchen or "by hand").so if this boot.img is not flashed into your phone,those feautures wont work.every custom rom have her boot.img into the flashable rom.zip.the thing that our rom creators and devs dont know(cause all phones are not the same) is that the boot.img in the zip doesn flash!.our phone cant flash boot.img from recovery and the reason is because in this phone kernel and recovery are in the same partition and not separately partition like most phones.
The solution:
REMEMBER THAT YOU DO IT WITH YOUR OWN RISK!
its just very simple:the only thing you have to do is to flash the boot.img that comes with your rom and the only way to do that succesfull is with Odin.(this ofcourse will give the custom bin counter 1 up because its a modified and not stock kernel).also have in mind that you have to flash it once.if for any reason you want to reflash your rom,you just do wipe data etc and reflashing the rom.zip.its not necesary to reflash the kernel(boot.img) again.its still there and will only change if you flash another boot.img or stock firmware with Odin.
So i will give two options.
1.download my PDA_S5360_kernel.tar from TermaRomGR threadhttp://forum.xda-developers.com/showthread.php?t=1520167(the mods in all of these kernel are about the same).flash it with Odin in pda field (first try without wipe anything or reflashing stock firmware first.just boot in download mode,flash with odin and reboot,it should work ok.DONT FORGET TO BACKUP YOUR ROM FIRST!JUST IN CASE!).reboot may take more time dont worry.when phone is on your ext partition should be mounted.you can try with terminal simulator:
su
a2sd check
if everything is ok you can remove your dalvik cache to your sd if you want for more internal memory free space:
su
a2sd cachesd
the phone will reboot.it will late to reopen just be patient and then your internal memory will be almost empty.but have in mind that this partition is not as fast asthe internal memory so some apps or games maybe slow a bit.
2.the other option is to flash the kernel(boot.img) that come with your custom rom.how to do that (thanks to Doky):
copy the boot.img that is inside the zip of the rom you are using.
download my PDA_S5360_kernel.tar
find in web the program total commander for windows
open t commander and in left window navigate to my PDA_S5360_kernel.tar file and get into it.in the right window find the boot.img of your rom.drag it and drop it to the left window so it replace the boot.img into the .tar file with yours.its ready.just flash it with Odin.
Some important things too that i notice from my experiments:
with busybox 1.18 your rom will not boot after nove dalvik cache to sd
it will work nice with 1.17 but its not suitable for people who want to run v6 script.for those who want to run v6 you must download busybox instaler from market and install v1.19.2.if after that you have problems with wifi try another version (1.19.3 or 1.19.4).and report back what works ok and what not so all people together can find the best setup.
Please tell to the devs of your roms to read this thread so they learn about the solution to this problem so they can create even better and better roms

I love you. I'll try this tomorrow.
Sent from my GT-S5360 using xda premium

Why do i have SD Card Remove Problem then when i boot back i was in the Welcome Screen where my info of google account is being ask. I skipped it then check the settings, my account was just there still. Also having this Turning off by itself problems. This was just started when i begin using a2sd supported ROMS. But when i'm just on stock or non-a2sd roms it work fine. Maybe its the boot.img?

eyjay1991 said:
Why do i have SD Card Remove Problem then when i boot back i was in the Welcome Screen where my info of google account is being ask. I skipped it then check the settings, my account was just there still. Also having this Turning off by itself problems. This was just started when i begin using a2sd supported ROMS. But when i'm just on stock or non-a2sd roms it work fine. Maybe its the boot.img?
Click to expand...
Click to collapse
which boot.img you instal?mine?i dont think that this is the problem.for me and for others works ok.try wipe cache and if the same try wipe data/reset.

Thank you for the info bro!
Sent from my GT-S5360 using xda premium

bumslayer said:
I am interested to know what is so special about your boot.img and how you customized it. I am guessing you decompiled a stock boot.img to come up with your own
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
with xda kitchen.it doesnt has something xterme only a2sd, init.d support and ext mount on boot.

So this will happen?
before flashing ur 5360kernel.tar
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after flashing
is this correct?

ronnieryan said:
So this will happen?
before flashing ur 5360kernel.tar
after flashing
View attachment 926853
is this correct?
Click to expand...
Click to collapse
yes its succesfuly flashed and should working right

termagazis said:
with xda kitchen.it doesnt has something xterme only a2sd, init.d support and ext mount on boot.
Click to expand...
Click to collapse
Oh, so I can take a stock firmware from Doky73's thread and modify it thru xda kitchen and change the kernel to include just init.d support (I kind of hate a2sd at the moment)? What about ext4 file system support? Is this possible?
By xda kitchen you mean the one by dsixda, right?

just like to ask if a2sd's low memory setting would conflict with [email protected] scripts?
coz after installing a2sd in my phone with [email protected] script, i sometimes notice that memory usage would reach 240+?

bumslayer said:
Oh, so I can take a stock firmware from Doky73's thread and modify it thru xda kitchen and change the kernel to include just init.d support (I kind of hate a2sd at the moment)? What about ext4 file system support? Is this possible?
By xda kitchen you mean the one by dsixda, right?
Click to expand...
Click to collapse
dont know.just try it if you want.for ext4 suport we need a custom kernel that will suport that

ronnieryan said:
just like to ask if a2sd's low memory setting would conflict with [email protected] scripts?
coz after installing a2sd in my phone with [email protected] script, i sometimes notice that memory usage would reach 240+?
Click to expand...
Click to collapse
maybe they conflict.use one of them

I'm using hybrid2.1 ,
Qus 1: is it necessary to partition SD card if I wanna enable a2SD? If yes then when&how?
Qus 2: is the1St option stated above mint to flash only the tar file by Odin and other fields of Odin remain empty?
And please give a link to download Odin & a link for step by step tutorial on connecting to Odin(with phone preparation ).
Sent from my GT-S5360

a.m.muammar said:
I'm using hybrid2.1 ,
Qus 1: is it necessary to partition SD card if I wanna enable a2SD? If yes then when&how?
Qus 2: is the1St option stated above mint to flash only the tar file by Odin and other fields of Odin remain empty?
And please give a link to download Odin & a link for step by step tutorial on connecting to Odin(with phone preparation ).
Sent from my GT-S5360
Click to expand...
Click to collapse
1.yes its necesary to have an ext2 or ext3 partition.you can create it with skin1980 CWM recovery in advance/partition sdcard.a partition 500Mb is enough.(before do it backup everything from your sdcard to your pc because this procedure will erase everything in your sdcard.)
2.for Odin google it Odin3-v1.85.Here is how to do it:
1. you put my tar in pda field and the other remain empty(check only "Auto reboot" and "F.reset time")
2. Now turn off your Samsung Galaxy Y (just for make sure is completely off, remove the battery for a few sec and put that back)
3. Press Volume[-] + Home + Power to boot in Download Mode
4. Hold the buttons until a warning screen with choise show up.
5. Select Continue (Volume[+]), then it`s go to download mode
6. Connect the cellphone (via USB cable) to PC, wait until ODIN detect the device.
7. Click Start
8. Wait until ODIN give feedback respon PASS
it`s mean the flashing proccess is complete. Samsung Galaxy Y will auto reboot.
9. unplug the USB cable from PC/Laptop

Thanks bro, I have 2 questions more,
before flash your PDA is it necessary to go back to stock rom?
Currently I'm using V6 with busy box v1.18 on hybrid2.1, should I change it to v1.19.2?
Your link for v1.19.2 in terma rom thread is not working.
Sent from my GT-S5360

a.m.muammar said:
Thanks bro, I have 2 questions more,
before flash your PDA is it necessary to go back to stock rom?
Currently I'm using V6 with busy box v1.18 on hybrid2.1, should I change it to v1.19.2?
Your link for v1.19.2 in terma rom thread is not working.
Sent from my GT-S5360
Click to expand...
Click to collapse
its not necesary.flash it as it is.just dont forget wipe data and wipe cache.for busybox 1.19.2 just download from market

termagazis said:
its not necesary.flash it as it is.just dont forget wipe data and wipe cache.for busybox 1.19.2 just download from market
Click to expand...
Click to collapse
After which step I should wipe data and cache bro?
Sent from my GT-S5360

a.m.muammar said:
After which step I should wipe data and cache bro?
Sent from my GT-S5360
Click to expand...
Click to collapse
before flashing the rom zip

termagazis said:
before flashing the rom zip
Click to expand...
Click to collapse
You mint after flashing .tar file I have to reflash my hybrid rom?
Sent from my GT-S5360

a.m.muammar said:
You mint after flashing .tar file I have to reflash my hybrid rom?
Sent from my GT-S5360
Click to expand...
Click to collapse
**** i messed up!sorry.you just flashing pda file and reboot and install busybox.no wipe

[Detailed][Guide]Everything on Recoveries!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you've dealt with recovery software on your computer any, you probably already have a good idea of how this works and what it's all about. Out of the box, your phone comes with stock recovery software. It varies depending on the manufacturer, but all stock recoveries are essentially the same. They allow you to manually flash official updates and allow you to clear the cache on your phone. What they can do is very limited and in reality, not all that helpful.
Thanks to the genius Android developers out there, we have custom recoveries that replace the limited, unhelpful ones. These third-party, or aftermarket, recoveries add all sorts of functionality to the recovery software on your phone.
Types of recoveries available for pico:
TWRP TeamWin Recovery
ClockWorkMod Recovery 6.0.2.8
Explanation for all the recovery terms:
Reboot System:
It will reboot the device normally,you will boot into current ROM.
Apply Update from SD card:
Usually this option is used when,you got a official signed update,than u can flash it using this option.The update file must be named as "update.zip".It should be placed under the root of ur SD card i.e not under any folder,direct paste
Wipe Data/Factory Reset:
Factory resets your device,this will wipe off the /data partition.The /system & /sdcard partition won't be affected.It is always recommended to wipe data when you are flashing a custom rom. After yor factory reset,you will see startup wizards,which helps you to get started.
Wipe Cache Partition:
Wipes the cache partiton on your device.Cache files are those files which are stored by applications to speed up your phone(to loads games a bit faster) & to perform somewhat faster.You can clear up the cache to make your internal memory look better.
Install Zip from SD card:
This option allows you to flash any zip from your SD card.After you select this option,you will find a few more options,they are
-->Apply update.zip
It works same like apply update from sd card.
-->Choose zip from SD card
You can select the .zip file whichever you wanna flash.
-->Toggle Signature Verification
Ah,I too certainly dont know,what exactly it does.Well,recommended to keep it disabled(default=disabled)
-->Toggle Scripts asserts
Better leave it,if you don't know about recovery's search editfy scripts(same as I do :silly
Backup & restore:
Ah,Again you gonna get 3 more sub-options
-->Backup
If you have something heard about "nandroid" ,than its nothing but a system backup,known as nandroid!This will backup every single file present in your internal & external partition of your memory card(ext partition).The backup folder is stored on your sd card,path /sdcard/clockworkmod/backups.Recommended you copy the folder on your PC through USB~
If you wanna take nandroid,I have made a video over it here
-->Restore
Selecting the option will restore your backup uped ROM,the same as u backed it up!You,need to factory rest once before restoring the backup.
It is helpful when you are stucked on bootloops or soft bricked!
-->Advance Restore:
This is kinda for experts.It ask you to restore only the partition you want to.Suppose,youhave flashed a kernel,which aint booting up your device now ,you can restore /boot partition from your back uped ROM. And,enjoy booting it instead of reflashing the whole damn ROM.
Mounts & Storage
This option enabled you to mount/unmount any partition on your device.You can every format the partion(P.S one by one).The last option "Mount USB storage" allow you to transfer files from SD card to PC or a vice-versa.
Advance:
The most used option ! Gives you a few sub-options.
-->Reboot Recovery:
The phone will just reboot into recovery mode.Ah,this option is helpful,when the recovery doesn't do certain tasks,example,while u mount the data partition,it may happen that u wont able to unmount it again,so just reboot recovery,may help you at times(my personal experience)
-->Wipe Dalvik Cache:
Wipes the Dalvik Cache from your device,one deleted,it gets re-created,when u reboot your device,so booting it will take a more longer time than that of usual!So,don't panic!
-->Wipe Battery Stats:
Formats the file called batterystats.bin.In sort of calibrated your battery!Mainly done when you flash a new ROM!
-->Report Error:
Reports the error to the recovery team.
-->Key Test:
It tells you the number that has been allocated to any key on your phone.This is mainly used when u want to remap your hardware buttons,or just to check wetherthe system is registering the press of the button.Press the back button to exit the test.
-->Partition your SD card:
Creates second partition into your sd card.while one used for storing up the mediafiles,second partition can be used for increasing the RAM & internal memory.During this process it will ask you,how much space you are willing to give or internal memory that is ext size & RAM that is SWAP,SWAP works only if ROM supports it.
Note:The process formats everything on the sd card !
-->Fix Permission
It will fix permission gone wrong in internal stroage.It will fix some FC's(Force Closes) on the system apps or the the apps you converted into system apps but forgot to change the permissions!
Power off:
It will power off your mobile.

reserved

How to take screenshots on recovery mode
Special thanks to @vineethraj49 for teaching me with the help of portal on xda :good:
We,Just cant run the .bat file provided by wishley103 because it gives up errors,thats why we need to run these commands one by one
Steps to take screenshot on recovery mode through ADB:
Download this file --->http://www.mediafire.com/?xr1h6gb1z3cr3c5
Extract it over desktop
P.S Don't change the folder name!
Open cmd,direct it to the desktop folder(hope u know that,if don't,post is over),than type these comands :
Code:
adb shell
mount /data
exit
adb push fb2png /data/local
adb shell
chmod 755 /data/local/fb2png
/data/local/fb2png /data/local/fbdump.png
exit
adb pull /data/local/fbdump.png
What output you should get after taking the screenshot
Code:
bpp : 16
size : 307200
width : 320
height : 480
ARGB offset : 0 0 5 11
ARGB length : 0 5 6 5
Framebuffer Pixel Format: 1
Saved to /data/local/fbdump.png
Open the folder "screenshot",There you will find a file named "fbdump.png"! Voila,that is your screenshot!
View it through your image viewer!
So,here is the result!

Credits
Credits:
For the guide how to take screenshot in recovery mode @vineethraj49
For awesome work on screenshot zip @Whiskey103
For every blogger,I learned to write this thread :laugh:
legen_dary & Nihar.G for porting latest version of recoveries for our device !
None other XDA & Google :silly:

Thanks Rishik !
An extremely detailed and comprehensive guide
:good: :good:

red-devil said:
Thanks Rishik !
An extremely detailed and comprehensive guide
:good: :good:
Click to expand...
Click to collapse
Thanks,hope the real strugglers find it helpful! :victory:

Nice...
You could also add instructions on partitioning SD card, using ADB, Fix Permissions and other stuff too...
P.S.: Thanks for the credits

vineethraj49 said:
You could also add instructions on partitioning SD card, using ADB, Fix Permissions and other stuff too...
P.S.: Thanks for the credits
Click to expand...
Click to collapse
Yeah all done! :angel:

WOW! you deserve to be RC

russelldias said:
WOW! you deserve to be RC
Click to expand...
Click to collapse
Oh yeah? I feel too :silly:
Thanks,means a lot!

Couple of suggestions:
*Quick comparison of TWRP to CWM
*Brief description of installation proceedure
(You are probably planning on adding these anyway, but I figured I post them just in case...)

SifJar said:
Couple of suggestions:
*Quick comparison of TWRP to CWM
*Brief description of installation proceedure
(You are probably planning on adding these anyway, but I figured I post them just in case...)
Click to expand...
Click to collapse
Thanks for the suggestions..they are always welcomed by me! :victory:
Soon,gonnna work on it!

[twrp] 3.0.2.0-n [With Root Instructions!]

this Recovery is now depreciated go https://forum.xda-developers.com/showthread.php?p=71244945 instead​
What's new
MTP auto mount on boot fixed!
Data unmount after few seconds fixed.
Bugs
Battery Info doesn't work (due to M based sources)
Data decryption
Mount Loop devices (Kernel issue) can't be fixed atm
Credits: TWRP (Team win Recovery Project)
Huawei
@BadWolfYe for giving info on how he got MTP working.
Me
Current status: Stable
Created: 2016-11-20

Removed

LastStandingDroid said:
This was shared here for reasons that some P9 users came to our H8 thread so i decided to post it here as well.
Click to expand...
Click to collapse
Thank you so much for your hard work. When you say data works but requires reflash could you explain which part requires reflash?
Regards
Lee

Just to clarify, does this allow mounting and editting of /system partition, manually via TWRP terminal?

Atarii said:
Just to clarify, does this allow mounting and editting of /system partition, manually via TWRP terminal?
Click to expand...
Click to collapse
Yes you can mount cust, data, system, product, vendor
thel2dab said:
Thank you so much for your hard work. When you say data works but requires reflash could you explain which part requires reflash?
Regards
Lee
Click to expand...
Click to collapse
The properdata fix will flash a empty image to the phone which you'll have to resize after flash or I'll get 2.Gb of internal storage only.you might need repair data first or reboot recovery for it to be repairable.
Sent from my FRD-L09 using Tapatalk

U are best.
Does flashing ROM's work?
I whant to flash newest N emui 5.0 wihout roolback

I don't know why but my phone fails to boot after flashing the properdatafix.zip and resizing.
It resizes correctly but after it won't boot. I have to flash old firmware and upgrade to to 7.0 again.
Any help would be great.
Regards
Lee

richish said:
U are best.
Does flashing ROM's work?
I whant to flash newest N emui 5.0 wihout roolback
Click to expand...
Click to collapse
It flashes firmwares yes I've reflashed N and the hw_EU full package
thel2dab said:
I don't know why but my phone fails to boot after flashing the properdatafix.zip and resizing.
It resizes correctly but after it won't boot. I have to flash old firmware and upgrade to to 7.0 again.
Any help would be great.
Regards
Lee
Click to expand...
Click to collapse
Exactly what did you flash? AFAIK if it is a zip that mounts a image it will either bill the flash process with a reboot or make your device stuck on splash screen. What zip did u use?
If.u flashed N pack from M twrp u can install it again with this twrp. If it doesn't boot then it's probably due to a Img (ext4) that is being mounted and that's most likely is due to modified boot.img which will kill the boot procedure supersu package can make a modified boot but it won't boot due to su.img being mounted so it'll reboot to recovery
Sent from my FRD-L09 using Tapatalk

LastStandingDroid said:
Exactly what did you flash? AFAIK if it is a zip that mounts a image it will either bill the flash process with a reboot or make your device stuck on splash screen. What zip did u use?
Click to expand...
Click to collapse
I flashed the properdatafix.zip from the 1st post. Then rebooted in to twrp went to wipe - advanced wipe - data - resize partion - reboot - stuck on black screen.
fastboot flash, recovery, boot, system, from stock to get device booting again.
I must be doing something wrong. I know this is really cheeky to ask but could you make a video or something of the correct flashing procedure? The way I have tried is like this:
1 Fastboot flash your recovery.img
2. Boot into TWRP recovery.
3. Install properdatafix.zip
4. Reboot recovery.
5. Resize data partition.
6. Reboot and phone wont boot anymore.
Regards
Lee

thel2dab said:
I flashed the properdatafix.zip from the 1st post. Then rebooted in to twrp went to wipe - advanced wipe - data - resize partion - reboot - stuck on black screen.
fastboot flash, recovery, boot, system, from stock to get device booting again.
I must be doing something wrong. I know this is really cheeky to ask but could you make a video or something of the correct flashing procedure? The way I have tried is like this:
1 Fastboot flash your recovery.img
2. Boot into TWRP recovery.
3. Install properdatafix.zip
4. Reboot recovery.
5. Resize data partition.
6. Reboot and phone wont boot anymore.
Regards
Lee
Click to expand...
Click to collapse
You can install the firmware again after you resized the data partition if something goes wrong and report back if it helps. Maybe it is a block issue in fstab but it shouldn't be
Sent from my FRD-L09 using Tapatalk

@LastStandingDroid
I also will not boot in the system...
What file system (data) should be displayed in TWRP, ext4?

LastStandingDroid said:
You can install the firmware again after you resized the data partition if something goes wrong and report back if it helps. Maybe it is a block issue in fstab but it shouldn't be
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
How should I install the firmware again? Through flashable zip or through dload folder and hold vol up and down when restarting phone? Thank you for your patience, I know I am taking a lot of your time with this.
Regards
Lee

kep2008 said:
@LastStandingDroid
I also will not boot in the system...
What file system (data) should be displayed in TWRP, ext4?
Click to expand...
Click to collapse
The data should be ext4 format. Could u mount system and check if there's any file in system folder also u might need to resize system as well since u only have 19mb as well.
thel2dab said:
How should I install the firmware again? Through flashable zip or through dload folder and hold vol up and down when restarting phone? Thank you for your patience, I know I am taking a lot of your time with this.
Regards
Lee
Click to expand...
Click to collapse
Sent from my FRD-L09 using Tapatalk

thel2dab said:
How should I install the firmware again? Through flashable zip or through dload folder and hold vol up and down when restarting phone? Thank you for your patience, I know I am taking a lot of your time with this.
Regards
Lee
Click to expand...
Click to collapse
I'd use twrp to flash it.since u won't have to roll back again
Sent from my FRD-L09 using Tapatalk

LastStandingDroid said:
I'd use twrp to flash it.since u won't have to roll back again
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
Thanks. It seems to reflash ok in TWRP but after the flash completes. I need to factory reset but I am back to to stock recovery. It seems that flashing the update.zip overwrites the recovery. (I assume this is expected?)
Thanks again for your help. Is there is anything else I can try to get this to work?
Regards

laststandingdroid said:
the data should be ext4 format. Could u mount system and check if there's any file in system folder also u might need to resize system as well since u only have 19mb as well.
Sent from my frd-l09 using tapatalk
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Again install update.zip 7.0, but the system will not boot...

thel2dab said:
Thanks. It seems to reflash ok in TWRP but after the flash completes. I need to factory reset but I am back to to stock recovery. It seems that flashing the update.zip overwrites the recovery. (I assume this is expected?)
Thanks again for your help. Is there is anything else I can try to get this to work?
Regards
Click to expand...
Click to collapse
Yes the recovery is replaced after flash back stock. Did it boot after reflashed?
Strange are you having Vendor And product option available in Mount restore and backup? To see if they are properly flashed?
kep2008 said:
View attachment 3948500View attachment 3948501
Again install update.zip 7.0, but the system will not boot...
Click to expand...
Click to collapse
Did you get the data to work in TWRP? I think the boot.img is the issue here tbh. Since I neither can't boot unless I use a supersu fixed image.
Sent from my FRD-L09 using Tapatalk

Ok w8 I'll fix a twrp that will make the installation of su system less mode possible but u will be forced to remove su.img from /data/ else it won't boot
fastboot flash this: http://www21.zippyshare.com/v/7YNPp3AI/file.html
Before You Flash SuperSU-Systemmode you need to mount system & /vendor first since the Sepolicy is located in the "Vendor" Partition for reasons i won't bother to explain.
Once Flashed Mount Data again (if it gets unmounted, mount system) and navigate to /data and remove su.img
This will make N booting
Sent from my FRD-L09 using Tapatalk

LastStandingDroid said:
Yes the recovery is replaced after flash back stock. Did it boot after reflashed?
Strange are you having Vendor And product option available in Mount restore and backup? To see if they are properly flashed?
Did you get the data to work in TWRP? I think the boot.img is the issue here tbh. Since I neither can't boot unless I use a supersu fixed image.
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
/data is mounted only with /system, but the installation files still contain errors /data/media
mount -o bind /data/media /sdcard process ended with ERROR 255

kep2008 said:
/data is mounted only with /system, but the installation files still contain errors /data/media
mount -o bind /data/media /sdcard process ended with ERROR 255
Click to expand...
Click to collapse
Did u use the new recovery? If so that is for now common since it uses a different mount file rather than busbox version) that's why this message comes
In fact I copied over the "original" mount file from stock recovery but it isn't copying the compete file as it's only 6b so it'll stay until I try fix it.
Sent from my FRD-L09 using Tapatalk

[RECOVERY][MOD] MultiROM v33 + TWRP v3.1.1 for Xiaomi Mi MIX (lithium)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
To decrypt your device:
Backup ALL your data if you need to recover later (TWRP backup to USB or copy to your PC)
In fastboot mode:
Code:
fastboot format userdata
In TWRP: Flash Magisk (recommended) or SuperSU to avoid auto-encryption in next boot.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP). Flash it as usual TWRP (fastboot flash recovery, or any flasher app if you're rooted).
MultiROM. Install it as usual zip from modded TWRP once flashed.
Go into TWRP MultiRom settings and be sure that "Enable No-KEXEC Workaround" is enabled (enabled by default)
Your current rom will not be erased by the installation.​Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
MIUI ROM as Secondary <--- Latest versions fix this, so you shouldn't need it anymore
Install MIUI as secondary via MultiROM settings in TWRP
Boot into your (rooted) primary
Edit fstab.qcom file in /storage/emulated/multirom/roms//boot/ and add /cache partition entries:
Code:
/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait,check,formattable
/dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check,formattable
Alternatively you can use attached file "fstab.qcom.txt" (rename to: fstab.qcom without .txt ). Be sure to set proper permissions (copy from original fstab.qcom, after renaming to fstab.qcom.bak, don't delete it...)
DON'T FORGET to flash Magisk / SuperSU after flashing to avoid re-encryption if you're flashing stock (not modded).
Known issues
You must wait a few seconds (3-5) before you get touch screen responsiveness in TWRP and MultiROM. (fixed by 2017.08.01 build) -- USUAL WHEN SWITCHING FROM MIUI
Some FCs on some secondary ROMs: Try using multiromfix.zip, thx to @Startrek852 (to disable sdcardfs support in that secondary) -- USE MAGISK 13.5+
Issues with TWRP to boot on 4GB/128GB model... (Working on troubleshooting...) -- PRELIMINARY FIX HERE
Reporting issues
As you surely understand, a simply "it does NOT work" is not enough... so please, report your issue describing scenario as much as you can, try following this (as much as possible information is welcome, it's very tiring for me asking what this, what that, etc...):
Issue description (what, how, when, etc...)
Device model : 4GB or 6GB RAM
Decrypted? /cache and /data FSs ? (We assume IS decrypted becaues you're using MultiROM, and EXT4 FS for /cache and /data if you don't know or manually formatted to F2FS)
TWRP version + MultiROM version
Primary ROM (name, better with version)
Firmware version
Secondary ROM (the one with the issue, name and better version)
Custom kernel ? (name and version if so) <--- In theory, we shouldn't support scenarios with custom kernels.... (they can touch system stuff that make things more complex)
Xposed ? <--- Sorry we DON'T support MultiROM if you use Xposed
Google Apps (name, better with version)
Magisk / SuperSU (version and if you use it in Primary and/or Secondary and version)
Logs <--- This would be amazing great and helpful !!!! (you can get them via adb shell, terminal or using any tool)
*Original post and example in this post, please: ​
Download
You can download all stuff from here, where you can find latest TWRP and MultiROM. If you need to uninstall MultiROM, you can use this uninstaller.
MultiROM Manager (apk) available here.​
Source code
MultiROM - https://github.com/MultiROM-dev/multirom
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/BitOBSessiOn/android_device_xiaomi_lithium​
Special thanks to:
@Tasssadar for creating this awesome utility
@nkk71 for the No-KEXEC workaround
@AdrianDC and all MultiROM guys involved in its development
@jcadduono for TWRP port

We will have to try soon... It's the perfect set up for flashaholics

Great news [emoji847][emoji847]
Envoyé de mon MIX en utilisant Tapatalk

I can't make it work

fil0s0f0 said:
I can't make it work
Click to expand...
Click to collapse
The MultiROM app from market is only for official devices (I haven't updated the Android app, imo it's not very useful), So you must follow OP steps.
If you have some issue, please, describe your problem and we will try to help.
Keep in mind that you must have unlocked bootloader, decrypted device, etc...

Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback

fil0s0f0 said:
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
Click to expand...
Click to collapse
Yes, there are, please, revise OP, and describe which steps have you followed to find out what's your issue. Thx

provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output

Superb, I missed it in this great smarphone

acasmc said:
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Click to expand...
Click to collapse
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.

BitOBSessiOn said:
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
Click to expand...
Click to collapse
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.

acasmc said:
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
Click to expand...
Click to collapse
Too weird... I've just downloaded and flashed again with rashr and ok.
Which model do you own (128/256)? Primary rom...?
TWRP must work ok with encrypted /data (but you need decrypted for MultiROM).

I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.

acasmc said:
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
Click to expand...
Click to collapse
Can you try some of older versions in testing or backup folder in n AFH, please...?
Can you take a photo of error if it still occurs...?

there is only one TWRP in your folder. can you point me to another. I'll try no worries

acasmc said:
there is only one TWRP in your folder. can you point me to another. I'll try no worries
Click to expand...
Click to collapse
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564

Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]

Konsstantine34 said:
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Click to expand...
Click to collapse
Usually I don't start to develop for a device before I can use MultiROM....

BitOBSessiOn said:
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Click to expand...
Click to collapse
tried other two that are on that link. still the same. sadly don't have another phone with me, to take a picture.
guess gonna have to wait for an update. :/

BitOBSessiOn said:
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
Click to expand...
Click to collapse
About encrypting, Is it enough to flash the "no-verity-opt-encrypt-5.1".zip?, And if its not, Is there a guide of how to encrypt my device?

[ROM][BETA] OFFICIAL PIE from ASUS

I am not responsible if you brick your device.
UPDATE BETA PIE ROM
Direct link Download- https://drive.google.com/uc?id=1_r6zxR34q5aN72SPhAjMLkV4GxQcD4ff&export=download
Flash procedure for pie- https://www.asuswebstorage.com/navigate/a/#/s/A9A029F390A34806BED2A412E194C44D4
For BL unlocked phones
Recommended PBRP
PBRP has function to fix the encryption after flashing the ROM. You may choose to flash decrypt.zip for your own satisfaction.
PBRP worked like a charm for me.
* Use 7zip/WinRAR- Extract / Open Archive by right clicking the firmware zip and go to > META-INF > com > google > android
*open updater-script with a note editor
* Remove all the lines above the code
ui_print("Target: Android/sdm660_64/sdm660_64:X.X.X/XXXX/XX.20XX.XXXX.XXX-20XXXXXX:user/release-keys");
*Save it/rezip the firmware and copy it to sdcard
*Wipe System, data, cache / format DATA.
*Flash the ROM
Stock FULL ROM OREO 8.1
Stock Recovery & TWRP Flash-able
You have to flash full ROM if magisk is installed. Take backup & be very careful if device get encrypted after installing the ROM. (Flash decryption file- https://forum.xda-developers.com/asus-zenfone-max-pro-m1/how-to/mod-decrypt-data-t3787311 )
* Use 7zip/WinRAR- Extract / Open Archive by right clicking the firmware zip and go to > META-INF > com > google > android
*open updater-script with a note editor
* Remove all the lines above the code
ui_print("Target: Android/sdm660_64/sdm660_64:X.X.X/XXXX/XX.20XX.XXXX.XXX-20XXXXXX:user/release-keys");
*Save it/rezip the firmware and copy it to sdcard
*Wipe System, data, cache / format DATA.
*Flash the ROM
Official ROM link- https://www.asus.com/Phone/ZenFone-Max-Pro-M2/HelpDesk_BIOS/
One click Download - https://dlcdnets.asus.com/pub/ASUS/...995.844210030.1548823414-323285766.1546595187

so after installing latest 186 ROM continue installing decrypt.zip right?

rycroot96 said:
so after installing latest 186 ROM continue installing decrypt.zip right?
Click to expand...
Click to collapse
when i had installed December update (unlocked bootloader & magisk installed) i flashed the new rom, installed decrypt.zip yet the phone got encrypted on boot. Later i formatted data and flashed decrypt.zip and the phone booted normally.
Its kind of two way procedure. Try it. There is nothing wrong in experiment unless you haven't taken backup.
I'll flash as soon as i go home & let you know the status.

Ajeyvm said:
when i had installed December update (unlocked bootloader & magisk installed) i flashed the new rom, installed decrypt.zip yet the phone got encrypted on boot. Later i formatted data and flashed decrypt.zip and the phone booted normally.
Its kind of two way procedure. Try it. There is nothing wrong in experiment unless you haven't taken backup.
I'll flash as soon as i go home & let you know the status.
Click to expand...
Click to collapse
but when encrypted twrp doesn't disappear right? ok I am waiting I haven't updated since ubl + magisk. what is meant by twrp backup right? I have a system backup and booted. thanks a lot for the info bro

rycroot96 said:
but when encrypted twrp doesn't disappear right? ok I am waiting I haven't updated since ubl + magisk. what is meant by twrp backup right? I have a system backup and booted. thanks a lot for the info bro
Click to expand...
Click to collapse
backup means your personal data, apps, contacts, internal storage.
TWRP wont be gone after flashing. The phone works fine even after its encrypted. You need to flash decrypt.zip to get internal storage access in TWRP . And for overall smoothness of the device.

Ajeyvm said:
backup means your personal data, apps, contacts, internal storage.
TWRP wont be gone after flashing. The phone works fine even after its encrypted. You need to flash decrypt.zip to get internal storage access in TWRP . And for overall smoothness of the device.
Click to expand...
Click to collapse
thank you very much for the info

Guys ... Use PBRP Recovery.. It is based on TWRP...
It automatically patches forced encryption, after flashing the firmware file...
But just to make sure flash decrypt.zip too ...

So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
and my nandroid backup that I just make is on internal storage... so now it's already encrypted(or it isn't?) and no longer be able to use...
Is there any way I can decrypt back my phone?
my custom recovery/twrp encrypted as well
I got my nandroid backup few days ago on my computer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

watatara.102 said:
So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
and my nandroid backup that I just make is on internal storage... so now it's already encrypted(or it isn't?) and no longer be able to use...
Is there any way I can decrypt back my phone?
my custom recovery/twrp encrypted as well
I got my nandroid backup few days ago on my computer
Click to expand...
Click to collapse
I don't think there is a way to decrypt your phone without losing data...
Best way is restore from your nandroid backup...
watatara.102 said:
So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
Click to expand...
Click to collapse
I did exactly the same... But using PBRP recovery... Faced no issue at all...

Tyakrish said:
I don't think there is a way to decrypt your phone without losing data...
Best way is restore from your nandroid backup...
I did exactly the same... But using PBRP recovery... Faced no issue at all...
Click to expand...
Click to collapse
uh, the one that is encrypted is on /data I'm right?
my internal storage/internal SD which is on /data/media is not encrypted right? then I still can copy my NANDroid backup?

error displayed 7 in twrp.
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution

shivrajmalani said:
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution
Click to expand...
Click to collapse
Do not unzip the file.
Right click on the file, open archive. Edit the updater script. Save it. Better to use 7Zip.

watatara.102 said:
uh, the one that is encrypted is on /data I'm right?
my internal storage/internal SD which is on /data/media is not encrypted right? then I still can copy my NANDroid backup?
Click to expand...
Click to collapse
I am not sure exactly, which partitions are encrypted. But yes I think internal storage on /data/media is not encrypted...
But if you open TWRP then you will get a message to decrypt your device... DONT do this ! It will wipe your internal storage too, even if it is not encrypted...
If you want to copy your nandroid backup, then boot up your ROM and then transfer files using MTP to your computer..
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
shivrajmalani said:
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution
Click to expand...
Click to collapse
Did you use WinRAR ? Do one thing...
After extracting zip, and editing the script, go to the root of your firmware folder, select all files then add to archive. Select archive format as zip and keep the lowest compression possible...
While flashing, disable zip verification. This should work... Otherwise try the method by @Ajeyvm

I got this weird bug and it's will keep creating new log everytime reboot
here log file https://pastebin.com/wXHvcbDT

watatara.102 said:
I got this weird bug and it's will keep creating new log everytime reboot
here log file https://pastebin.com/wXHvcbDT
Click to expand...
Click to collapse
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version

Zahirpro2 said:
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version
Click to expand...
Click to collapse
Whenever i restart my phone i get that bug report. I clear it & use the device as usual. Evrything else is working fine. No need to revert back unless u r facing some major issue.

Zahirpro2 said:
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version
Click to expand...
Click to collapse
Oh so its not just me then, good to know

It looks good.
Edit, someone posted a review - https://youtu.be/_wli8M-71yI

Someone should really post a mirror of the official link

Official link is down does anyone has any other mirror link?