Team Win Recovery Project 2.1, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
I don't own any LG phone,so my support will be limited,I don't even know if this recovery boots
If you want more informations and/or you want to donate,please go to this page
Phone look:
{
"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"
}
DOWNLOAD:
Version 2.2.0 - My goo.im mirror
INSTRUCTIONS:
If you want to do it manually
Download recovery.img and place it on root of your sdcard
Make sure your phone is rooted
Open a terminal(Terminal Emulator from market works perfectly)
Type
Code:
su
cd /sdcard
dd if=recovery.img of=/dev/block/mmcblk0p5
Reboot in recovery and enjoy
You can use also This oneclick flasher by mustangtim49
CHANGELOG:
On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
Numerous small bug fixes and improvements
BUGS:
If you have found a bug, please consider posting it here,possibly with a recovery.log. It's very hard to keep up with multiple threads for multiple devices. Please search the issues list first. Your issue may have already been reported.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link
If none answers there,please join #neopeek on Freenode.
DISCLAIMER:
I don't own this phone,and I don't have a tester,I take no responsability for bricked devices,nuclear wars or such things
I'm porting it just because this phone is similar to P990,and I've got TWRP working on it successifully
CREDITS:
TeamWin for making the recovery
TeamKang for the device tree
E3D for the hosting
Works great.
tahahawa said:
Works great.
Click to expand...
Click to collapse
Thanks for confirming I didn't brick any device,yet.
helicopter88 said:
Thanks for confirming I didn't brick any device,yet.
Click to expand...
Click to collapse
The great thing about the g2x is its like unbrickable... with nvflash or the g2x batch cleaner we can get out of dang near any sticky situation... just fyi...
da-pharoah said:
The great thing about the g2x is its like unbrickable... with nvflash or the g2x batch cleaner we can get out of dang near any sticky situation... just fyi...
Click to expand...
Click to collapse
I don't even know how does a G2X look like
My Evo 3D is pretty easy to brick,that's why i'm worrying
helicopter88 said:
I don't even know how does a G2X look like
My Evo 3D is pretty easy to brick,that's why i'm worrying
Click to expand...
Click to collapse
haha no worries bro. thanks again for your efforts tho!
If everything works,tonight or tomorrow might tell Dees_Troy to add this device to the official list
Thanks for the app. Is this an alternative to cwm or an addition to it? Can both work in sync?
Sent from my LG-P999
cricketAC said:
Thanks for the app. Is this an alternative to cwm or an addition to it? Can both work in sync?
Sent from my LG-P999
Click to expand...
Click to collapse
It's not an app,it's a recovery,it replaces CWM,so them can't work together
Currently it doesn't support restoring from CWM backups,but in the future it might work
Hey guys, don't do the install with terminal, flashes recovery on wrong partition. I'm working on putting the new recovery in a one-click package. I'll post it in here when I'm done. Less than a hour.
mustangtim49 said:
Hey guys, don't do the install with terminal, flashes recovery on wrong partition. I'm working on putting the new recovery in a one-click package. I'll post it in here when I'm done. Less than a hour.
Click to expand...
Click to collapse
What partition should I use?
Looking at fstab it says that 0p5 is recovery..
helicopter88 said:
What partition should I use?
Looking at fstab it says that 0p5 is recovery..
Click to expand...
Click to collapse
That's the boot partition. I'm wondering the same thing as well
Off hand, I don't know which partition. I know that we in a sense CAN run 2 recoveries, one on the true persistent partition and one on the "fake" rom manager recovery partition. I'm working on the one-click package right now.
OK, I'm done with the one-click flasher, works great. OP, PM me if you want this in your op. Thanks!
I took TGA_gunnman's one-click flasher and Modded it to flash this recovery. All instructions are the same as original, just select cwm5020 and this recovery will flash.
DOWNLOAD:http://db.tt/nrxulELJ
helicopter88 said:
What partition should I use?
Looking at fstab it says that 0p5 is recovery..
Click to expand...
Click to collapse
0p5 is the boot but also its the recovery as well..
Edit:
looks like the xda app wigged out... here is the info:
Code:
Starting recovery on Fri Jun 29 17:19:01 2012
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.0.2.8
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p5 (null)
2 /boot emmc /dev/block/mmcblk0p5 (null)
3 /cache ext3 /dev/block/mmcblk0p2 (null)
4 /data ext3 /dev/block/mmcblk0p7 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /emmc vfat /dev/block/mmcblk0p8 (null)
7 /system ext3 /dev/block/mmcblk0p1 (null)
Sent from my LG-P999 using xda premium
Pharoah, gtalk me please, OP, I'm done with that one-click flasher
yeap i flashed using terminal and got twrp bootloop
the only gripe i have so far is that the recovery does not see folders and zip files on external sdcard nor its not mounting sdcard via twrp
EDIT: I made a nvflasher version based on Russ' NVFlash Recovery Flasher, all credit goes to rusty, it should work both for linux and windows (linux you have to make the .sh file Executable)
steps:
1. Make sure you make a nandroid backup
2. Extract contents in zip to a desired location
3. Make sure you have apx drivers
4. Run TWRP.bat as Admin
5. Have sexy time
Click here for Download
I can see my zip files on my external sdcard.
Sent from my LG-P999 using xda premium
ayysir said:
yeap i flashed using terminal and got twrp bootloop
the only gripe i have so far is that the recovery does not see folders and zip files on external sdcard nor its not mounting sdcard via twrp
EDIT: I made a nvflasher version based on Russ' NVFlash Recovery Flasher, all credit goes to rusty, it should work both for linux and windows (linux you have to make the .sh file Executable)
steps:
1. Make sure you make a nandroid backup
2. Extract contents in zip to a desired location
3. Make sure you have apx drivers
4. Run TWRP.bat as Admin
5. Have sexy time
Click here for Download
Click to expand...
Click to collapse
I Had the same issue. Figured it out by going to mounts and use external SD then reflashed rom and gapps without wiping.
Sent from my LG-P999 using xda app-developers app
mustangtim49 said:
I can see my zip files on my external sdcard.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
what did you do to be able to
ultma75 said:
I Had the same issue. Figured it out by going to mounts and use external SD then reflashed rom and gapps without wiping.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
ill try this out now, went back to cwm atm so ima reflash it thru my bat file
EDIT: AHHHH THAT WORKED THANKS MAN
Related
{
"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"
}
You are looking for a special modded Clockworkmod recovery?
Clockworkmod Recovery v4.0.0.5
removed downloadlinks cause of issues with the new unity kernel.
please use this very special recovery
Just have a look on this site: 4EXTRecovery v1.1.1 | STAY @EXT4 | Convert EXT4 without losing data | Advanced Backup
Clockworkmod Recovery v3.2.0.0
downloadlink:
PG88IMG-RECOVERYIMG-3.2.0.0.zip
Clockworkmod Recovery v3.1.0.1
downloadlink:
PG88IMG-RECOVERYIMG-3.1.0.1.zip
or visit my blog dev page: lbc mod android development - custom recovery
Install Instructions:
download the zip package
rename it to PG88IMG.zip
put that file on the root of your sd card
start you phone in bootloader (hboot not fastboot)
the bootloader will ask you if you want to install recovery.img
confrim
reboot
rename the file again into something else (cause bootloader will always try to flash if a PG88IMG.zip file is on your sd card
loveboatcaptain said:
Hey Guys,
just have the first booting version of ClockworkMod Recovery v.3.0.2.4 on my phone.
View attachment 575564
a full working beta will come in the next days.
Install instructions will follow, too.
CREDITS: this is basicly the work of HCDR.Jacob how helped my to build this, cause my macbook sucked at building from source. so give him a big tanks too ;-)
see you later with a download for everyone with s-off
regards
Click to expand...
Click to collapse
woohoo
you are great
Ah mr mac user succeeded gratz
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
Ah mr mac user succeeded gratz
Click to expand...
Click to collapse
Yeah, with a little help from my friends ;-)
Jacob is fixing the last bugs and than i think were done and can do some tests before release.
regards
Maybe ours work for you to, koush made ours public today. Ill give u the info tomorrow, should be all the same
Sent from my HTC Incredible S using XDA Premium App
the beta tests have finished...
we talked to koush and he put it into ROM MANAGER just in this minute...
so happy flashing for all with s-off and root.
regards
p.s. don´t forget to thank HCDR.Jacob. He build it together and fixed the bugs and of course koush for pushing it so quick to ROM MANAGER.
thx to this great community
loveboatcaptain said:
Hey Guys,
[ROMmanager]
regards
Click to expand...
Click to collapse
Cool - working, thanks!
running backup now - so let the de-sense begin - I always brake some things when playing around to strip sense, so great to have full backup...
dont know said:
Cool - working, thanks!
running backup now - so let the de-sense begin - I always brake some things when playing around to strip sense, so great to have full backup...
Click to expand...
Click to collapse
feel free to test my first rom ;-)
this would be easier to "de-sense" cause it´s allready deodexed. so you needn´t delete so much stuff ;-)
a light version will follow the nexts days, which will be "de-sensed" and have a custom launcher like ADW or LP
regards
loveboatcaptain said:
feel free to test my first rom ;-)
this would be easier to "de-sense" cause it´s allready deodexed. so you needn´t delete so much stuff ;-)
a light version will follow the nexts days, which will be "de-sensed" and have a custom launcher like ADW or LP
regards
Click to expand...
Click to collapse
It's a very light desense I want (only get rid of the ad-ware inkluded and some others like twitter..)
I'm on ADW because of the cool themes available.
THANKS for the possibility of real rooting (unsecure and clockwork) again..
Hi, how can I root my desire s save
Sent from my Desire S using XDA Premium App
M0ng0 said:
Hi, how can I root my desire s save
Sent from my Desire S using XDA Premium App
Click to expand...
Click to collapse
Hey, today i unlocked mine with an xtc clip.
Then I flashed the unsecured Boot Image. I hope it is called so .
After that worked successful, i rooted it with SuperOneKlick.
Maybe this works for you too.
Any chance you can get in touch with the developer of this as there seems to be a very annoying bug.
Everytime i include:
format CACHE or
format("ext4", "EMMC", "/dev/block/mmcblk0p27", "/cache");
the recovery will not flash the ZIP. It will always give a STATUS 1 error.
So i have to manually format cache and run my ZIPS.
Thanks.
anybody successfully tried to revert on stock recovery?
fastboot says "FAILED (remote: not allowed)", and with cwm recovery it's impossible to try new OTA...
MarylandCookie said:
Any chance you can get in touch with the developer of this as there seems to be a very annoying bug.
Everytime i include:
format CACHE or
format("ext4", "EMMC", "/dev/block/mmcblk0p27", "/cache");
the recovery will not flash the ZIP. It will always give a STATUS 1 error.
So i have to manually format cache and run my ZIPS.
Thanks.
Click to expand...
Click to collapse
hey dude,
i ported the recovery together with a friend. so i´m your man ;-)
i never noticed that there is a problem with formating cache partition, cause i don´t touch it with my updater-script.
so first question:
why you will add that to your updater-script? me for myself prefere the way of wiping my phone manually. and that works very well with CMR. i also tested it in the mount/partition menu.
i would not like it, when a script wipes stuff and i did not know about.
i only use format for system in my full update.zip´s. in updates for my rom i did not wipe anything.
second question: did you know that cache partition is always mounted when recovery starts? perhaps thats the problem.
regards
mih_ said:
anybody successfully tried to revert on stock recovery?
fastboot says "FAILED (remote: not allowed)", and with cwm recovery it's impossible to try new OTA...
Click to expand...
Click to collapse
those fastboot commands only works with an ENG S-Off bootloader. which we dont have. we have SHIP S-Off... there are differences between those both.
our bootloader can everything the ENG can with fastboot commands. we have to use a zip file to flash things like recovery or splash.
you have to add your recovery backup img into my PG88IMG-unsecured_bootimg.zip file from this post [BOOT] Root for S-Off with unsecured Boot Image rename it to PG88IMG.zip and add your recovery.img into that zip file and remove the boot.img file.
than put the file on the root of your sdcard and reboot into bootloader.
the file will be flashed automaticly.
after reboot your phone, rename the file again to something else, cause every time you are in bootloader and this file is named PG88IMG.zip on your sdcard thhe bootloader will try to flash it.
just a little tipp at the end: you can add every img file into this zip. system and data img files from nandroid backups are working too ;-)
regards
Thank you!
I'll try it next time, i'll need it
But i've managed to flash it through flash_image from this link:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#HBOOT_partition_map
with recover.img from OTA downloaded.
After OTA i've lost the root, but gingerbreak still works...
mih_ said:
Thank you!
I'll try it next time, i'll need it
But i've managed to flash it through flash_image from this link:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#HBOOT_partition_map
with recover.img from OTA downloaded.
After OTA i've lost the root, but gingerbreak still works...
Click to expand...
Click to collapse
Could you PLEASE give me a short (or long ) description how to install the ota?
No idea what to do with the linked code...
EDIT Extracted the boot.img from ota and copoed it to PG88IMG.zip - restart - run ota-update -> fail
EDIT2 I'm an idiot: instead of boot.img it is a great idea to try it with recovery.img *LOL*
You just have to replace clockworkmod ecovery with stock one.
I've taken it from OTA downloaded.
It contains file firmware.zip inside, which contains recovery.img as well.
You can flash it with tool flash_image (http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/vision_utilities/flash_image.zip)
Just put it somewhere to device, where you can run it (for instance/data/local/bin/, /system/bin/ if remounted to rw, /sdcard if remounted to exec)
and run from device or adb shell like%
su
flash_image recovery /sdcard/recovery.img
after that, you can reboot to hboot, check out that you do not have cwm recovery anymore, boot to android and install OTA as usual from menu...
does the recovery also do a backup of the radio?
(my wifi is broken sinve ota update - and I'm an stock recovery now, so can't test at the moment)
Cache being mounted or unmounted isnt the issue.
I can wipe cache manually but automatting it in the script seems the break the whole process.
Its good for testing and having a fresh install.
Lets android re-build everything.
Take from Clockworks How to:
wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery
Click to expand...
Click to collapse
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
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
{
"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"
}
Are you tired of scrolling through huge lists of files in ClockworkMod with the volume rocker?
Don't you wish there was a recovery with a graphical interface and controlled using the touchscreen?
Team Win Recovery is just that!
Built by TeamWin from the ground up based on AOSP recovery, it has a themeable GUI with touch interface, file manager, keyboard, terminal emulator and much much more...
NEW VERSION 2.3.2.1!
Note: A few devices experience random reboots/shutdowns in recovery with the latest version. If this is the case for you, use version 2.2.1 which is completely stable.
Features
Graphical touchscreen interface with buttons and drag-to-scroll!
Compressed backups that can save you up to 50% disk space
Ability to choose which partitions to back up and which to restore
Custom names for backups, rename and delete backups inside recovery
Integrated Terminal Emulator
Install queues allow you to install multiple zips in one go (e.g. CM9 zip together with gapps zip)
Easy one-button cache & dalvik cache clearing after an installation
Recovery settings are saved to the sdcard and persist through reboots
File Manager that allows you to move, copy, delete and rename files and change their permissions
Battery percentage indicator, charging indicator and clock (set your timezone in settings!)
Reboot into download mode (bootloader)
ADB support
Sideloading for automated ROM install: http://teamw.in/ADBSideload
Detailed logfile
Themeable
Download
2.3.2.1 as installable zip
http://www.mediafire.com/?6i91q2lvez9bj9p
Click to expand...
Click to collapse
Install by copying the zip file to your sdcard, booting into recovery (VolumeUp+Power) and then using "install zip from sdcard" ("apply update form sdcard" on stock recovery) to install it.
2.3.2.1 as flashable image file
http://www.mediafire.com/?ji7z7yznh25zjjp
Click to expand...
Click to collapse
Flash using broodplank's Quickflasher. Connect phone via USB, start sgsflasher_x86.exe, activate "Flash a new Recovery", select the twrp2.2.1-recovery.img and press "Start Now".
Please pay particular attention to this:
Some zips may no longer work in TWRP 2.3 if the developer is using an out-of-date update-binary. If this is a problem for you, please use TWRP 2.2.1 (download link in post below)! Zips can be fixed by replacing their old update-binary with this one.
Click to expand...
Click to collapse
FAQ
I installed this but my phone keeps booting into recovery over and over again.
You need to re-flash your bootloader as described here.
Click to expand...
Click to collapse
Can I use TWRP to restore my CWM backups?
No. The only way is to convert your uploads like this: flash CWM, restore a backup, flash TWRP, create new backup, repeat.
Click to expand...
Click to collapse
Where is my external SD card?
The external SD is under /emmc (as is standard for all CyanogenMod-based ROMs). The internal SD is under /sdcard.
Click to expand...
Click to collapse
What is the size vs speed tradeoff for compressed backups?
For my test, compression shrunk the total backup size by 43% and took 1.4 times longer.
Click to expand...
Click to collapse
Can I use this to flash CyanogenMod9?
Yes!
Click to expand...
Click to collapse
Can I use this to flash XYZ ROM?
Yes!
Click to expand...
Click to collapse
The clock shows the wrong time!
You need to set your timezone under Settings -> Time Zone. The setting is saved in a config file on your sd card so you only have to do this once.
Click to expand...
Click to collapse
My .zip file won't install!
Turn off signature verification!
Click to expand...
Click to collapse
Can I mount my SD cards on my PC in recovery?
Yes, but only one at a time. Go into the Mount menu and select which card to mount with the "Use external SD" or "Use internal storage" radio buttons. Connect your USB cable and press "Mount USB storage".
Click to expand...
Click to collapse
How can I restore single apps (and/or their data) from a TWRP backup?
Use TitaniumBackup, it supports TWRP! In Titanium Backup, open up the menu and select "Extract from Nandroid backup...". It will list all your TWRP and CWM backups and allow you to restore as many apps and their data as you want.
Even though all TWRP backup files carry the extension .win, they are either tar archives or filesystem images. System, data, cache and .android_secure are backed up as tar archives or gnu-zipped tar archives if compression is enabled. You can rename those .win files to .tar (.tar.gz if compressed) and extract them like a regular archive. Boot and recovery partitions are backed up as .img files using dd.
Click to expand...
Click to collapse
I have tried to test all recovery features and they all seem to work. I successfully flashed several different ROMs and performed backups and restores. However, there could still be bugs lurking somewhere - if you find one please report it!
Screenshots
Credits
TeamWin - Everything here is their work, I only provide a precompiled binary for our device. Particular thanks to Dees_Troy from TeamWin for his help.
arco - For the config files for our device.
Disclaimer
Do not install this if you don't know what you are doing. Incorrect flashing of a recovery can lead to a hard brick! Bugs in the recovery could result in data loss so always have a backup! I am in no way responsible for anything you do to your phone and offer no guarantees.
For Developers
TWRP has an optional companion app called GooManager. It offers a frontend for the goo.im archive which hosts ROMs and the gapps. Unlike CWM and ROM Manager, it is completely free, developers can upload their ROMs to goo.im and users can easily flash them with GooManager. It would be awesome if developers started uploading their ROMs there!
To take screenshots inside the running recovery, use adb to dump the framebuffer and then use ffmpeg to convert the raw image to a jpeg like this:
adb pull /dev/graphics/fb0
ffmpeg -vframes 1 -vcodec rawvideo -f rawvideo -pix_fmt rgba -s 480x800 -i fb0 -f image2 -vcodec mjpeg fb%d.jpg
Click to expand...
Click to collapse
Sources:
- TWRP2 github
- arco github with BoardConfig.mk etc. for I9001/ariesve
- Configuration parameters for TWRP in BoardConfig.mk:
Code:
DEVICE_RESOLUTION := 480x800
TW_INTERNAL_STORAGE_PATH := "/sdcard"
TW_INTERNAL_STORAGE_MOUNT_POINT := "sdcard"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"
TW_DEFAULT_EXTERNAL_STORAGE := true
TW_FLASH_FROM_STORAGE := true
This is a straight, unmodified compile of TWRP2 sources. TWRP2 is made available under the Apache License 2.0.
Over 27000 downloads as of November 17th! Rock on!
Changelog:
2.3.2.1
- Small bugfixes
2.3.1.1
- Fixed keyboard not working for backup rename bug
2.3.0.3
- Faster boot
- Much faster permission repair
- Charging indicator (only updates once a minute)
- Major code rewrite to C++ and Jelly Bean base
- ADB Sideload functionality - for automated ROM installs, see http://teamw.in/ADBSideload
- USB storage mounting now mounts both internal and external sd cards simultaneously
2.2.1
- Small bugfixes
- Trying to fix the random shutdown bug that happens on some devices
2.2.0
- Integrated Keyboard
- Set custom backup name
- Terminal emulator
- Rename files in file manager
- Set file permissions using octal notation in file manager
- Rename and delete backups
- Restore menu has switch for internal/external SD
- Fixed timezone names
- Wipe external SD option
- Wipe battery stats and rotation data options removed (Google says it's unnecessary. You can still do it manually/with apps if you want.)
- Fixed themes not loading bug
2.1.8-fix
- Fixed USB storage mounting
2.1.8
- Initial release for the Galaxy S Plus
Old Downloads:
2.3.1.1 as installable zip
http://www.mediafire.com/?l78dskdap2xghd7
2.3.1.1 as flashable image file
http://www.mediafire.com/?hhqmgmqq3a37q7s
2.3.0.3 as installable zip
http://www.mediafire.com/?ld9iupspojsdmq2
2.3.0.3 as flashable image file
http://www.mediafire.com/?zqwou2f353n945p
2.2.1 as installable zip
http://www.mediafire.com/?0ufe8dcv5kkajay
2.2.1 as flashable image file
http://www.mediafire.com/?aknf6rjpxj16wrv
2.2.0 as installable zip
http://www.mediafire.com/?6nb6clnwn9w1247
2.2.0 as flashable image file
http://www.mediafire.com/?7afs5n39nbkop22
2.1.8 as installable zip
http://www.mediafire.com/?9bh66rw6uqbt9tm
2.1.8 as flashable image file
http://www.mediafire.com/?km077vhodky7rsb
Cm9 compatible ?
UpGado said:
Cm9 compatible ?
Click to expand...
Click to collapse
Yes!
no problem in cm9？ example.. wifi .BT....because arco recovery fixed some problem in cm9
Sent from my GT-I9001 using XDA
Ezekiel1998 said:
no problem in cm9？ example.. wifi .BT....because arco recovery fixed some problem in cm9
Click to expand...
Click to collapse
This is a Recovery, not a ROM!
A recovery is a small bootable operating system on a seperate partition on your device. Changing your recovery does not in any way affect your running system. And when booted in the recovery you don't have access to WiFi or Bluetooth anyway.
The reason FeaMod does not work with CM9 is because it was compiled with a wrong list of partition sizes. I compiled this using arco's CM9 repository, so it has exactly the same settings, kernel config etc. as the CM9-compatible CWM that arco compiled.
looks awssum shall try flashing an xperimental.zip
Sent from my GT-I9001 using Tapatalk 2
Is this somewhat related to cmw touch recovery ?
Awsome work!!!
Sent from my GT-I9001 using XDA
In restore it is showing nothing....can anybody else confirm it?
Sent from my GT-I9001 using Tapatalk 2
You must make a backup with teamwin recovery. Maybe you can copy your CWM Backup into the Teamwin recovery folder for restore your backup.
Sorry for my english.
Gesendet von meinem GT-I9001 mit Tapatalk
Awesome thanks for your work
Sent from my GT-I9001 using Tapatalk
wow...nice recovery... thanks for your work!!
This is RECOVERY it has nothing to do with any of the ROMS !!! RESTORING BACKUP from other RECOVERIES is not recommended, it will end up bricking your phone! NEVER RESTORE BACKUP WITH DIFFERENT VERSIONS OF RECOVERY, EVEN IF IT IS MADE FROM SAME SOURCE.
RECOVERY cannot be "compatible" or "incompatible" with ANY of ROM distro's.
Restoring someone's nandbackup (CM9 with arco recovery, for example) on own phone is other story.
BzArEx said:
Is this somewhat related to cmw touch recovery ?
Click to expand...
Click to collapse
No, it was developed from scratch by TeamWin. It is also open source and completely free unlike CWM touch which you have to buy.
You can read more at the official project website: http://teamw.in/project/twrp2
F**k the system . AMAZING WORK!!!!!!
Yay!
Awesome work! I was waiting for a touch recovery!
btw, can we flash CWM over this afterwards, just in case i want to restore a CWM backup later on?
Awesome work bro....
Sent from my GT-I9001 using xda premium
sidsweb said:
btw, can we flash CWM over this afterwards, just in case i want to restore a CWM backup later on?
Click to expand...
Click to collapse
Yes, you can change recoveries without a problem.
For arco's CWM flash this zip file and then reboot the recovery. Later in CWM you can just flash the TWRP zip, reboot recovery and you're in TeamWin Recovery again.
This is also how I suggest people migrate their backups (if really necessary): Install and reboot into CWM, restore a CWM backup, install and reboot into TWRP, perform a backup, repeat.
Works great, just installed Arcos build 4 with your Recovery.
Awesome!
Greetings this is my first post here, so here we go
We all know that This phone has a tiny userdata partition size from the 4Gb Internal Size, about weeks ago i started to make that partition larger by Repartitioning it. So, after read some way from Android One thread, finally i did it, by resized the 3 partitions (system, cache & data) and made the userdata bigger. And now, imade the recovery script to install them easily
MAKE SURE YOU HAVE BACKED UP YOUR INTERNAL STORAGE AS WELLI WILL NOT BE RESPONSIBLE IF YOUR PHONE DIESPROCEED AT YOUR OWN RISKIF YOU MESS UP, USE FLASH TOOLS TO FLASH ROM AND FIX ALL PROBLEM
I made them by 3 Different Size, cause some ROM have different size and use way different size of System partition, so choose one of them that fit with the rom that you are about to flash after it Some zip make some ROM cannot be flashed via fastboot mode (e..g Lineage OS can only installed via fastboot when u are using stock or the third preset)
1. 760Mb System // 100Mb cache // 2,7Gb+ Userdata (Fit for any CM11 based Rom, Pico-Gapps, and some System Customization)
{
"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"
}
Click to expand...
Click to collapse
2. 1,3Gb System // 50Mb cache // 2,2Gb+ Userdata (Fit for any CM11 based Rom, Gapps, and more System Customization) (Fit for Stock Rom too with more Internal Storage )
Click to expand...
Click to collapse
2. 1,6Gb System // 200Mb cache // 1,7Gb+ Userdata (Just in case you want to revert it back without using Flashtool, this preset zip is close to stock partition )
Click to expand...
Click to collapse
Instruction to Install:
- Download the parted_binary_arm.zip and one of the repartition zip in the Attachment based on your choice
- Backup your data and internal sdcard as well (cause everything inside it will be destroyed!)
- Install the parted_binary_arm.zip first, then
- Install the Repartition zip file
- Then it will automatically reboot to recovery
- If you see some red lines in the TWRP logs (which happens sometime) just reformat system, cache and data partition by using the wipe option in the TWRP. (you can format it to any desired format as well. For e.g f2fs, ext4 and make sure the rom you will going to install is support those filesystem)
- And then to make sure everything is fine, reboot your phone to recovery once more and try to mount these partitions and look at the size
- After that, just flash the new ROM that fit with your system partition size and boot your phone as well
- See the difference :fingers-crossed:
Contributors
big thanks to @vinay for tester and helped me for everything
thanks @out386 for the original parted guide via adb
thanks to @forumber2 for the original repartition script via TWRP :highfive:
Feel free to ask, or PM me if you having some trouble :highfive: i also available at telegram :highfive:
Hit thanks if this helped :good:
Thank u! But i am using Lineage OS, how to install via fastboot?
PjKay said:
Thank u! But i am using Lineage OS, how to install via fastboot?
Click to expand...
Click to collapse
I am not sure, but you can try the 2.2gb internal repartion and take backup the /system of your lineage rom via backup option of your twrp before installing the repartition (Make sure you change the backup location to your external sdcard). And then restore it after finish the repartition
is that just for D2202??
otakuyasser1 said:
is that just for D2202??
Click to expand...
Click to collapse
It is meant for any 22xx. (2203, 2243, 2202, 2212 and 2206) I made a modification on @elmaleek03 script. It has a new scheme that is good for me. It has 2.5GB on /data, 1GB on /system and 50MB on /cache (cache cannot be shrinked more )
Original script by @forumber2 and modifications by @elmaleek03 (on OP)
and another mod by @jpzex (attached file)
EDIT: Just found that LineageOS didn't flash with 1GB on /system only. Do not use it if you want to use Lineage. It may be okay if you use CM11
Running in 2203, perfect !! Thank you!!!
otakuyasser1 said:
is that just for D2202??
Click to expand...
Click to collapse
I am using d2202 an its worked on me. Tester did it successfully on their d2212 and d2203. I haven't tried it on 2243 etc. U should try that so we all can know it ?
jpzex said:
It is meant for any 22xx. (2203, 2243, 2202, 2212 and 2206) I made a modification on @elmaleek03 script. It has a new scheme that is good for me. It has 2.5GB on /data, 1GB on /system and 50MB on /cache (cache cannot be shrinked more )
Original script by @forumber2 and modifications by @elmaleek03 (on OP)
and another mod by @jpzex (attached file)
EDIT: Just found that LineageOS didn't flash with 1GB on /system only. Do not use it if you want to use Lineage. It may be okay if you use CM11
Click to expand...
Click to collapse
Cool! U are learned the script well thx for ur participation should i add ur 2.5gb preset to the op?
Yeah, the lineage os only can flashed with stock / original (unmodified) internal partition scheme unless thomas share the flashable zip of lineageos for our device so we won't need using fastboot again for install the lineage
birdsilver said:
Running in 2203, perfect !! Thank you!!!
Click to expand...
Click to collapse
Yess, urwell glad to hear that
elmaleek03 said:
Cool! U are learned the script well thx for ur participation should i add ur 2.5gb preset to the op?
Yeah, the lineage os only can flashed with stock / original (unmodified) internal partition scheme unless thomas share the flashable zip of lineageos for our device so we won't need using fastboot again for install the lineage
Click to expand...
Click to collapse
Why ? Becaus :https://forum.xda-developers.com/showpost.php?p=73479700&postcount=169
And pleas my name is @infus38 (Thomas )
elmaleek03 said:
Cool! U are learned the script well thx for ur participation should i add ur 2.5gb preset to the op?
Yeah, the lineage os only can flashed with stock / original (unmodified) internal partition scheme unless thomas share the flashable zip of lineageos for our device so we won't need using fastboot again for install the lineage
Click to expand...
Click to collapse
NOTICE: Only "/system" partition needs to have its original size, for now. "/cache" can be shrinked to give its space to "/data". Probably on later builds it may change. The team is working on it. The goal is to use a 1,4GB "/system" partition and the rest is for "/cache" with 50MB and "/data" with 2.0GB.
Can you explain the procedure very clear.. Because im confused after flashing the zip files...i dont know what.is next?..
.
After installing the zip file
Reflash the stock rom via falshtool or just reboot after flashing the zip file...
And how to do the mounting thing in TWRP
.
So confused
Can it work on 4.4.4 firmware of d2212
rs130301 said:
Can it work on 4.4.4 firmware of d2212
Click to expand...
Click to collapse
Definitely
Repartition revert script
Hello guys! I made a repartition revert script thanks to GGonDue , @elmaleek03 and @forumber2. It may revert partition sizes to factory defaults. It must be used according to the OP post by @elmaleek03, you download parted-binary-arm.zip and then use the attached zip later.
Remember, it wipes /data, /cache and /system. You WILL need to restore from a backup or install a ROM afterwards.
jpzex said:
Hello guys! I made a repartition revert script thanks to GGonDue , @elmaleek03 and @forumber2. It may revert partition sizes to factory defaults. It must be used according to the OP post by @elmaleek03, you download parted-binary-arm.zip and then use the attached zip later.
Remember, it wipes /data, /cache and /system. You WILL need to restore from a backup or install a ROM afterwards.
Click to expand...
Click to collapse
Thanks for the Updates,,
Which ROM is stable for now on Sony Xperia E3 D2203????
Admin, Can't you make the system to be 1GB and increase the userdata?
because am using 4.4 stock ROM, and my system is almost 1GB.
9jabasewap said:
Thanks for the Updates,,
Which ROM is stable for now on Sony Xperia E3 D2203????
Click to expand...
Click to collapse
CM11 by FreeXperia works almost everything.
All wireless connections work. (I don't know about NFC)
Camera works
If you can't find, I have a link to it. Good luck
9jabasewap said:
Admin, Can't you make the system to be 1GB and increase the userdata?
because am using 4.4 stock ROM, and my system is almost 1GB.
Click to expand...
Click to collapse
There is one experimental repartition I made to use on my phone on CM11 ROM, as it is not that big, lots of space can be given to /data. But you can only use /data and /cache as ext4, f2fs cannot partition /cache because it is too small for it. Flashable is atrached.
Scheme is:
936MB /system
48MB /cache
2887MB /data
jpzex said:
There is one experimental repartition I made to use on my phone on CM11 ROM, as it is not that big, lots of space can be given to /data. But you can only use /data and /cache as ext4, f2fs cannot partition /cache because it is too small for it. Flashable is atrached.
Scheme is:
936MB /system
48MB /cache
2887MB /data
Click to expand...
Click to collapse
Thanks, Can it work on stock ROM. because am current stock ROM system back it 1GB plus.
{
"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?