Mi3 has a dual boot,it is useless on any other rom then miui and eats space
This is how to merge sys1 and sys2 without adb shell or without connecting to a PC
backup system partition as it will format(excluded sdcard)
1.download the zip file below
2.backup with cwm/twrp
3.flash it (tested on cwm/twrp)
4.advanced restore system partition from nandriod backup
5.flash full gapps modular or stock package gapps
You are done
Note:flashing stock gapps will replace your stock apps and will break ota
Credits:
PAgapps :http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
audahadi for zip : http://forum.xda-developers.com/showpost.php?p=58591075&postcount=29
Can i flash on twrp recovery?
enterome said:
Can i flash on twrp recovery?
Click to expand...
Click to collapse
Yes works fine with twrp/cwm
smh.saad said:
Mi3 has a dual boot,it is useless on any other rom then miui and eats space
This is how to merge sys1 and sys2 without adb shell or without connecting to a PC
backup system partition as it will format(excluded sdcard)
1.download the zip file below
2.backup with cwm/twrp
3.flash it (tested on cwm/twrp)
4.advanced restore system partition from nandriod backup
5.flash full gapps modular or stock package gapps
You are done
Note:flashing stock gapps will replace your stock apps and will break ota
Credits:
PAgapps :http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
audahadi for zip : http://forum.xda-developers.com/showpost.php?p=58591075&postcount=29
Click to expand...
Click to collapse
I don't see the point of this thread. It is right next to the original thread on extending partitions in Mi3 General section.
Please carry on your discussion in the thread that already exists and refrain from creating duplicate topics.
Thread closed.
Related
hi everyone am here to ask you for help
i need step by step insteractions on how to update my galaxy I19100 from android 4.1.1 into the latest available android 4.4.4 or above
here are info about my current phone status
i have the jellybam rom jellybam AOKP 20121009
android 4.1.1
kernal 3.2.0_rc8_siyah_dorimanx_V5.86B3_JB_Mali_sgii
please advice my step by step what i need to do to change to the latest version and advice me what is the best rom now to use which is stable graphically beautiful and fully function with s2
hope someone will care and help me
Download and flash Latest DorimanXv113 kernel.
-Advenced>> Reboot into recovery
-Flash rom nuke script
-flash kitkat ROM
-flash gapps
-reboot system now
You need to search because this information is easily found by doing same. And you also need to use a descriptive thread title. Why ? Because they're the forum rules.
Zile995 said:
Download and flash Latest DorimanXv113 kernel.
-Advenced>> Reboot into recovery
-Flash rom nuke script
-flash kitkat ROM
-flash gapps
-reboot system now
Click to expand...
Click to collapse
thx alot bro so will i need an external SD card? , i flash the kernel with oden right ?? after i do so there will be no rom no OS nothing just the recovery right ? so i need to download the KitKat Rom and the gapps downloaded before i flash the kernel ?
MistahBungle said:
You need to search because this information is easily found by doing same. And you also need to use a descriptive thread title. Why ? Because they're the forum rules.
Click to expand...
Click to collapse
believe me bro i tried search and every time i get more confused about do i need a new kernel or not and do i need external SD or not or even is it stable or i will get a very unstable phone after
Crypto00 said:
thx alot bro so will i need an external SD card? , i flash the kernel with oden right ?? after i do so there will be no rom no OS nothing just the recovery right ? so i need to download the KitKat Rom and the gapps downloaded before i flash the kernel ?
believe me bro i tried search and every time i get more confused about do i need a new kernel or not and do i need external SD or not or even is it stable or i will get a very unstable phone after
Click to expand...
Click to collapse
Do you have CWM recovery?
Zile995 said:
Do you have CWM recovery?
Click to expand...
Click to collapse
yes i have
CMW-based-recovery v6.0.1.2-siyah
Now download latest dorimanx 10.43 and flash it in CWM.
Install zip from sdcard and find your zip file in external or internal memory.
Reboot into recovery
-Flash rom nuke script
-flash kitkat ROM
-flash gapps
-reboot system now
Zile995 said:
Now download latest dorimanx 10.43 and flash it in CWM.
Install zip from sdcard and find your zip file in external or internal memory.
Reboot into recovery
-Flash rom nuke script
-flash kitkat ROM
-flash gapps
-reboot system now
Click to expand...
Click to collapse
so i will have access to the internal sd card all the time no need to have an external one and after the wipe/nuke script will it format the internal sd card ?
thank you mate i have installed cyanogenmod 11
hii,
My device is currently running on miui 8.5.4.0 global stable,i want to flash los 14.1,and planned some steps in order to revert back to miui safely.please correct me if i am wrong.
1.boot into twrp recovery.
2.Take full backup of current working rom including system.
3.clear data/system/cache/dalvik.
4.flash firmware-los rom-gapps-reboot.
Steps to revert back:-
1.boot into twrp recovery.
2.clear data/system/cache/dalvik.
3.restore full miui backup including system.
4.flash lazy flasher zip to disable dm-verity and forced encryption.
5.reboot.
i have just learnt basics completely but i had some doubts so i posted the entire procedure i thought to do.
thanks.
After taking backup first go to Wipe menu and "Format Data" , type yes and reboot recovery, it will remove encryption - then you can wipe data/system/cache etc..
/system wipe is never necessary .. You can skip that
Hollow6 said:
/system wipe is never necessary .. You can skip that
Click to expand...
Click to collapse
doesn't it mess up with firmware flash of custom rom?does a custom rom contains a system partition of its own to be flashed?or it just replaces or moves required system files to system partition of stock rom? help me to clear my concept!
k3lcior said:
After taking backup first go to Wipe menu and "Format Data" , type yes and reboot recovery, it will remove encryption - then you can wipe data/system/cache etc..
Click to expand...
Click to collapse
what is the difference between format data and wipe data? isn't it same?i am asking so because i havnt seen such option in recovery before.
sorabhsolanki said:
doesn't it mess up with firmware flash of custom rom?does a custom rom contains a system partition of its own to be flashed?or it just replaces or moves required system files to system partition of stock rom? help me to clear my concept!
Click to expand...
Click to collapse
Every ROM does contains its own system ..
When you flash any ROM (a full fledged ROM not OTAs) , the previous system is replaced by the later one ..
---------- Post added at 05:54 AM ---------- Previous post was at 05:50 AM ----------
sorabhsolanki said:
what is the difference between format data and wipe data? isn't it same?i am asking so because i havnt seen such option in recovery before.
Click to expand...
Click to collapse
You'll have to understand what Format Exactly we are here talking about .. When you go to TWRP/wipe , you are provided with 2 options , Format and Advanced wipe .
The format option is set to "wipe" the partitions, /data /cache /dalvik , that is generally what we require in order to flash ROMs , the wipe Option is hence the same as format , but I think the guy above is talking about Full fledged Wipe that includes the "internal storage" as well which can be selected by twrp/wipe/advanced wipe
Hollow6 said:
Every ROM does contains its own system ..
When you flash any ROM (a full fledged ROM not OTAs) , the previous system is replaced by the later one ..
Click to expand...
Click to collapse
thanks.one more question.
why dont i need to disable dm-verity and forced encryption after flashing custom rom?why kernel doesn't trigger it,because in that case there is a modification in system partition and dm-verity feature of kernel should prevent the rom from booting.
The "kernel" itself also gets replaced by a modified kernel .. But then again , I'm not sure as to why DM verity doesn't kick in , better ask the Developers (Y)
sorabhsolanki said:
hii,
My device is currently running on miui 8.5.4.0 global stable,i want to flash los 14.1,and planned some steps in order to revert back to miui safely.please correct me if i am wrong.
1.boot into twrp recovery.
2.Take full backup of current working rom including system.
3.clear data/system/cache/dalvik.
4.flash firmware-los rom-gapps-reboot.
Steps to revert back:-
1.boot into twrp recovery.
2.clear data/system/cache/dalvik.
3.restore full miui backup including system.
4.flash lazy flasher zip to disable dm-verity and forced encryption.
5.reboot.
i have just learnt basics completely but i had some doubts so i posted the entire procedure i thought to do.
thanks.
Click to expand...
Click to collapse
when you want to revert back you dont need to wipe anything or flash disable dm verify, just restore your previous nandroid backup and thats all
THREAD CLOSED!!!
[G531F] CS-Rom v3.2 (android 5.1.1) by Adi [FIXED ALL BUGS!]
Features:
-Pre-Rooted,
-Xposed Framework installed,
-Busybox installed,
-Customizable Status Bar,
-Customizable Notification Bar,
-Deodexed,
-Debloated,
-Deknoxed,
-Some Xposed Modules,
-Added SU.D Support,
-Added Custom Bootanimation,
-Now it's Zipaling,
-Added Init.D Support,
-Much more...
Installation:
Flashable Zip Version:
-Download ZIP,
-Move ZIP to SD Card or Internal Storage,
-Boot into TWRP,
-Wipe: Cache, Dalvik, Data, System,
-Flash ZIP,
-Reboot.
Backup Version:
-Download ZIP,
-Extract ZIP.
-Move TWRP folder to SD Card or Internal Storage,
-Boot into TWRP,
-Restore backup,
-Reboot.
DOWNLOAD:
-Flashable ZIP without TouchWiz (NougatLauncher):
https://drive.google.com/uc?id=0B2OyU1OLo9sjbmRuakExMXRrVGs&export=download
-Flashable ZIP with TouchWiz:
https://drive.google.com/uc?id=0B2OyU1OLo9sjc2xsSFh6RjdwX0E&export=download[/B]
-TWRP Backup without TouchWiz (NougatLauncher):
https://drive.google.com/uc?id=0B2OyU1OLo9sjQXFXa2ZSNEd4Q3M&export=download[/B]
-TWRP Backup with TouchWiz:
https://drive.google.com/uc?id=0B2OyU1OLo9sjNTJRZEZJcWFtaGs&export=download[/B]
Special Thanks to Imioł (XDA nick : Sh0peN) for lending the device.
FINALLY!
Perfect!
Hope it works fine, waiting so long..
You might need to flash GApps...
EDIT:Just flash the 5.1 GApps for OpenGApps, if it doesn't work.
does this rom have any issue
Destroyer08 said:
does this rom have any issue
Click to expand...
Click to collapse
Probably not.
At last...thank you very much
what version of recovery do you use?
melc70 said:
what version of recovery do you use?
Click to expand...
Click to collapse
TWRP 3.0.2-0
error
Destroyer08 said:
does this rom have any issue
Click to expand...
Click to collapse
error extractfork() process ended witherror 255
[email protected] said:
error extractfork() process ended witherror 255
Click to expand...
Click to collapse
idk whats wrong... do full wipe or something
[email protected] said:
error extractfork() process ended witherror 255
Click to expand...
Click to collapse
Now I'm working on 2.0 version...
adiJ5FN said:
TWRP 3.0.2-0
Click to expand...
Click to collapse
That version never existed for SMG-531F as far as I'm aware.
In addition, I followed all the instructions, but TWRP won't detect the backup.
Version : TWRP : 2.8.7
Any ideas about how to fix that ? I have been waiting for a custom ROM for two years now.
?
TWRP 2.8.7 Cant see the file when i press Restore
just create a boot backup, write the folder name and delete it if you want, rename the rom folder.
!
Perfect rom...thanks....
Can i get rid of FRP lock after flashing this rom?
Hi,
I'm new and amateur with this thing, but can someone tell me cause I own G531F with Android 5.1.1, if I do everything from this few steps posted in the first link, will I have Android 6 on my phone or do I need to do something more beside that?
Thanks!
Incognito493 said:
That version never existed for SMG-531F as far as I'm aware.
In addition, I followed all the instructions, but TWRP won't detect the backup.
Version : TWRP : 2.8.7
Any ideas about how to fix that ? I have been waiting for a custom ROM for two years now.
Click to expand...
Click to collapse
TWRP 3.0.2-0 Just flash via odin...
https://forum.xda-developers.com/attachment.php?attachmentid=3955426&d=1480666661
Important
I can't make this work, I don't have enough storage because it's too big, i got 8 gb internal and 2gb. Compress it or maybe do it as a install from twmp not restoring it.
Hey people,
this shall mainly be a fast way to navigate users to necessary steps for diverse situations.
Instead of repeating the procedures over and over in each thread, this can be cited.
I will suggest you what I always do, and what I find safe and what I have good experiences with.
Still, you do everything at your own risk! So don’t complain to me if you mess something up by following my steps.
This well known phrase also counts here: “YOU are choosing to make these modifications”.
*********************
Preparations
Recovery
Make sure you are on the latest TWRP version.
Currently this is 3.2.3-0.
Backups
Before any of these procedures you should make a backup of every partition and save it at an external place – an usb stick, your PC, but not on your phone! Also copy the content of your entire internal storage at such an external place.
This will not always be needed and I will add more details of what you will surely lose when applying each method, but sometimes things just go wrong and suddenly your whole storage may be lost out of nowhere (happened to me more than once already).
A nice app that helps you restoring your apps and app data in a very quick way is Titanium Backup (get it from the Play Store). If you use the Pro version, you can restore everything basically with one click, so think about this way of backing up things as well (external copies are also advised here for obvious reasons).
Firmware
Make sure you are on adequate firmware for your ROM. Which firmware that is, must be taken from the respective ROM thread.
Adequate firmware needs to be present at any time before the actual ROM installation,
otherwise installation will fail, as the ROM expects a certain minimum to be present.
You will not need to always flash firmware again, when installing other ROMs or ROM versions.
The one you flashed last time sticks until you flash another.
A nice alternative to always flashing whole MIUI Developer versions are the zips offered by the firmware updater tool (just search through the xda topics).
*********************
So here we go with methods you should know:
***************
* Dirty Flash *
***************
Note that:
This is not recommended if the ROM maintainer or developer suggested a clean flash
If you wanna solve weird issues, you may try this first, but a Clean Flash or a Complete Formatting will probably help better
Use-cases:
You wanna install an update for a ROM you are momentarily on
Benefits:
Only takes a few minutes
You will not lose Gapps, settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Wipe Dalvik and Cache
Flash ROM zip right on top of existing installation
(Optionally) Re-/flash root (re-flashing is not necessary for Magisk most of the time if you installed it before)
****************
* Clean Flash *
****************
Note that:
You will lose Gapps, settings, apps and app-data
Also recommended from time to time, even when a dirty flash would be sufficient
Some developers always prefer this method over a dirty flash
Use-cases:
You wanna flash a ROM from the same Android generation (e.g. both ROMs are from generation Nougat 7.1.2) you are currently on
You are experiencing issues after dirty flashing a ROM
Benefits:
Clean way of installation
Content on your internal storage will (/should) stay untouched
Procedure:
Wipe Dalvik, Cache, System, Data, (momentairly I also advise) Vendor
Flash ROM zip
(Optionally) Flash custom kernel
(Optionally) Flash Gapps package for Arm64*
(Optionally) Flash Gapps additions*
(Optionally) Flash root
***************************
* Complete Formatting *
***************************
Note that:
You will lose Gapps, settings, apps, app-data and the content on your internal storage – basically everything on your phone!
Use-cases:
You wanna flash a ROM of a different Android generation (e.g. switch from Nougat to Oreo)
You are experiencing weird issues, even a clean flash doesn’t solve
Benefits:
Clean way of installation
Good problem solver
Procedure:
Wipe Dalvik, Cache, System, Data, (momentairly I also advise) Vendor
Format data (the one where you need to type “yes”)
Reboot to recovery to access the Data partition correctly again
Flash ROM zip
(Optionally) Flash custom kernel
(Optionally) Flash Gapps package for Arm64*
(Optionally) Flash Gapps additions*
(Optionally) Flash root
****************************************
* Solve unable to mount Data error *
****************************************
Note that:
You will lose Gapps, settings, apps, app-data and the content on your internal storage – basically everything on your phone!
Use-cases:
TWRP suddenly shows the above error and even a Complete Formatting doesn’t help (or work)
Procedure:
Re-flash latest TWRP via fastboot (not from within TWRP)
Perform a Complete Formatting
********************
* Gapps Re-flash *
********************
Use-cases:
You want to change your current Gapps setup, but keep your current ROM installation
Benefits:
Only takes a few minutes
You will not lose settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Wipe Dalvik, Cache and System
Flash ROM zip
Flash Gapps package for Arm64*
(Optionally) Flash Gapps additions*
(Optionally) Re-/flash root
********************
* Kernel Change *
********************
Note that:
This works for almost every kernel, but if the developer suggests another method, follow his
Use-cases:
You want to change the kernel, but keep your current ROM installation
Benefits:
Only takes a few minutes
You will not lose Gapps, settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Extract the boot.img of your current ROM
Flash the boot.img by selecting “flash image” in TWRP
Reboot to System and let everything cool down for a minute or two
Reboot to TWRP
Flash new kernel
(Optionally) Re-/flash root
Wipe Dalvik and Cache
*******************************
* Stock Kernel Restoration *
*******************************
Use-cases:
You're on a custom kernel and want to switch back to stock one
Benefits:
Only takes a few minutes
You will not lose Gapps, settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Extract the boot.img of your current ROM
Flash the boot.img by selecting “flash image” in TWRP
(Optionally) Re-/flash root
Wipe Dalvik and Cache
********************************
* Splash Screen Restoration *
********************************
Note that:
A clean flash will not solve this
Use-cases:
Some kernel's or ROM's splash screen sticks and you wanna get rid of it.
Benefits:
Only takes a minute
You will not lose anything on your phone (except the splash screen ; ) )
Procedure:
Just re-flash your current firmware
*I usually go for Pico Gapps from opengapps.org, as they don't include anything I don't need or like, and add a couple of things from deltadroid by flashing them right after the Pico Gapps package. Some stock apps can be overwritten this way, so you don't have two for the same purpose (e.g. stock calendar and google calendar) and it results in a nice minimal Gapps configuration.
I’m open for corrections, questions or doubts! Please leave a comment in these cases!
last updated: 2018-08-20
Nice little guide!
Small note: rooting on f2fs with Magisk has been fixed recently if you didnt know yet.
HelpMeruth said:
Nice little guide!
Small note: rooting on f2fs with Magisk has been fixed recently if you didnt know yet.
Click to expand...
Click to collapse
Thanks!
And thanks for the info. So were these issues Magisk related only?
Phil_Smith said:
Thanks!
And thanks for the info. So were these issues Magisk related only?
Click to expand...
Click to collapse
iirc yes(there were SQL issues on the Magisk app), but I don't really follow superSU anymore since its been sold to some random company.
This is a very good guide.. Thanks mate
I have a SGP321 (Pollux LTE | Xperia Tablet Z) on unofficial LineageOS 14.1; the TWRP is the one built into the boot.img (v. 3.1.1).
I'd like to get to 16.0.
1.) Can I go from 14.1 to 16.0, or is there a reason 15.1 should be flashed first?
2.) Will any version ≥ TWRP 3.2.x.x official or unofficial work for both Oreo and Pie?
3.) Is this a correct order of operations:
a.) Boot into FOTA recovery
b.) Advanced Wipe: Dalvik + System + Cache + Data + Internal Storage (also, is there a difference between Format Data and Advanced Wipe > Internal Storage?)
c.) Install .zip for LoS from external SD card (or should I sideload via adb?)
4.) Installing gapps is listed as optional, so I can skip installing an opengapps .zip?
5.) Installing addonsu .zip can be done later?
Thank you!
remi_kamahl said:
I have a SGP321 (Pollux LTE | Xperia Tablet Z) on unofficial LineageOS 14.1; the TWRP is the one built into the boot.img (v. 3.1.1).
I'd like to get to 16.0.
Click to expand...
Click to collapse
Hello!
1. Yes, you can.
2. For Oreo and Pie 3.2.x.x and 3.3.x.x are optimal.
3a. Check FOTA recovery version, if <3.2.x.x i suggest updating first.
3b. The difference is, that formatting data doesn't wipe internal storage (as far as i remember).
3c. External SD is better (though it's your choice).
4. If you don't GAPPS you can skip it.
5. Yes it can be done later, but i see no reason to not installing it in 3c.
Also think of root management solution, suitable best for you. Will it be internal root manager of LOS (with the help of addonsu binary) or you will use Magisk, which is more complex and has it's benefits too.
Good luck with flashing!
Thank you for the info!
I'm getting dropped into TWRP after flashing the latest 16.0 .zip.
This is specifically what I did:
1. Pushed lineage-16.0-20200511-UNOFFICIAL-pollux.zip & twrp-3.3.1-0-pollux.img to external_sd via adb root
2. adb reboot recovery; verified md5sums via terminal
3. In terminal: # dd if=/external_sd/twrp-3.3.1-0-pollux.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
4. Reboot into FOTA recovery; made sure the version = 3.3.1-0
5. Wipe: Format Data
6. Advanced Wipe: Dalvik + System + Cache + Data + Internal Storage
7. Install the lineage .zip
8. Wipe Cache/Dalvik and reboot system
After the "Sony Xperia" logo pops up, the Lineage boot animation runs for about 2.5 minutes, then the tablet drops into TWRP (RescueParty).
I can restore a 14.1 backup I made before flashing, and the tablet will boot again successfully.
Not sure where to go from here/not sure which specific log file would be necessary—or even available—to diagnose the problem (dmesg, logcat, Console-ramoops).
remi_kamahl said:
Thank you for the info!
I'm getting dropped into TWRP after flashing the latest 16.0 .zip.
Click to expand...
Click to collapse
This happens sometimes. Try to wipe everything ones again and flash LOS via TWRP.
FYI lineage-16.0-20200609-UNOFFICIAL-pollux.zip build is available.