Related
Hello
I have the problem that I cannot update my i9000 from CyanogenMod 10.1.3 to 10.2.0. After the update, Cyanogenmod doesn’t start anymore. It gets stuck at the boot animation: The blue CyanogenMod-mascot within the round rotating arrow. I waited 15min for it to start, then I left the phone for 2h and it still didn’t start.
I did the update as follows:
First, I tried to update with the automatic updater from CyanogenMod, but that didn’t work. It aborted and restarted CyanogenMod 10.1.3.
So I tried it manually with ClockworkMod (v6.0.3.6):
- wipe data / factory reset
- wipe cache partition
- advanced -> wipe dalvik cache
This message was shown: E:unknown volume for path [/sd-ext]
Dalvik cache wiped.
- install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
It aborted and the following message was shown:
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
- Did it again: install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
Now the zip-file was installed completely.
- reboot system now
The result was that the phone got stuck at the boot animation.
Remarks:
- I didn’t do a backup of apps and data, because I didn’t have important data on the phone.
- I didn’t have root-rights in CM 10.1.3.
I tried it again with the stable version of CM 10.2.0. I didn’t have to install the zip twice anymore, but the phone still gets stuck at the boot animation. Wiping cache and dalvik cache again didn’t make it start.
I can still boot into ClockworkMod and it was also possible to go back to CM 10.1.3. Just CM 10.2 doesn’t start up.
What do I have to do to make CM 10.2 start up?
Thank you very much for your help.
Best regards
Tomy
@Tomy_Delmar
Tomy, CyanogenMod is already custom ROM, there is always root access on it
Try it this way:
download Gapps for CM10.2x (Android 4.3.x) and paste them on your external SD card
put the card in your phone
run it in recovery mode
wipe cache and dalvik cache
flash Gapps for 4.3
wipe again cache and dalvik cache.
reboot
Post if it worked.
Tomy_Delmar said:
Hello
I have the problem that I cannot update my i9000 from CyanogenMod 10.1.3 to 10.2.0. After the update, Cyanogenmod doesn’t start anymore. It gets stuck at the boot animation: The blue CyanogenMod-mascot within the round rotating arrow. I waited 15min for it to start, then I left the phone for 2h and it still didn’t start.
I did the update as follows:
First, I tried to update with the automatic updater from CyanogenMod, but that didn’t work. It aborted and restarted CyanogenMod 10.1.3.
So I tried it manually with ClockworkMod (v6.0.3.6):
- wipe data / factory reset
- wipe cache partition
- advanced -> wipe dalvik cache
This message was shown: E:unknown volume for path [/sd-ext]
Dalvik cache wiped.
- install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
It aborted and the following message was shown:
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
- Did it again: install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
Now the zip-file was installed completely.
- reboot system now
The result was that the phone got stuck at the boot animation.
Remarks:
- I didn’t do a backup of apps and data, because I didn’t have important data on the phone.
- I didn’t have root-rights in CM 10.1.3.
I tried it again with the stable version of CM 10.2.0. I didn’t have to install the zip twice anymore, but the phone still gets stuck at the boot animation. Wiping cache and dalvik cache again didn’t make it start.
I can still boot into ClockworkMod and it was also possible to go back to CM 10.1.3. Just CM 10.2 doesn’t start up.
What do I have to do to make CM 10.2 start up?
Thank you very much for your help.
Best regards
Tomy
Click to expand...
Click to collapse
As the partition layout is different in cm10.2, you should flash it at least 2 times and wait for system to be stable for about 15-20 minutes
Tetakpatak and Rohitdahiya, thanks for the reply and advice!
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
I tried again the update from CM 10.1.3 to 10.2:
- I downloaded cm-10.2.0-galaxysmtd.zip again and copied it to the internal SD-card of the phone.
- Restarted the phone into ClockworkMod recovery.
- wipe data / factory reset
- wipe cache partition
- wipe dalvik cache
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
(Did it twice. Don’t know if necessary.)
Didn’t install Gapps.
- wipe cache partition
- wipe dalvik cache
- reboot system now
Unfortunately CM still gets stuck at the boot animation. The arrow has been rotating for over an hour now.
To my knowledge the Gapps are not mandatorily required to install CM. I could install CM 10.1.3 without the Gapps without any problems.
Could a full-wipe solve my problem?
ClockworkMod -> mounts and storage -> format /system …?
I have never done this before.
Or is there something else I can do?
Regards
Tomy
Tomy_Delmar said:
Tetakpatak and Rohitdahiya, thanks for the reply and advice!
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
I tried again the update from CM 10.1.3 to 10.2:
- I downloaded cm-10.2.0-galaxysmtd.zip again and copied it to the internal SD-card of the phone.
- Restarted the phone into ClockworkMod recovery.
- wipe data / factory reset
- wipe cache partition
- wipe dalvik cache
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
(Did it twice. Don’t know if necessary.)
Didn’t install Gapps.
- wipe cache partition
- wipe dalvik cache
- reboot system now
Unfortunately CM still gets stuck at the boot animation. The arrow has been rotating for over an hour now.
To my knowledge the Gapps are not mandatorily required to install CM. I could install CM 10.1.3 without the Gapps without any problems.
Could a full-wipe solve my problem?
ClockworkMod -> mounts and storage -> format /system …?
I have never done this before.
Or is there something else I can do?
Regards
Tomy
Click to expand...
Click to collapse
First of all, don't forget to quote the user whom you want to contact, because he don't get any notification until you quote. I was just checking around the questions and thus I saw this.
Sometimes, there is requirement of g-apps for the core system to be working ( Not sure in case of cm10.2). Try with g-apps (you may choose light package).
In my opinion, it should work. If not, try from the start ( flashing gingerbread with Odin with repartition ticked, then its root and finally cm10.2 from recovery)
Also make sure your handset is i9000 and you are using cm10.2 for the same.
And finally, All the best
CM doesn't neccesarily need Gapps to boot up. In fact most custom roms don't - they are still usable, just that everything Google-related doesn't work.
Its a bit odd seeing as how you've pretty much done what I would have done if I was installing CM to a Galaxy S. I can't think of any reason why it wouldn't work.
As far as I know as well, formatting /system is more of a last-resort method, not something you'd immediately do.
However, I had a similar problem installing a rom onto my tablet - different device, I know, but try this anyway and see if you get anywhere:
1.) Go back into recovery if its still bootlooping
2.) Wipe data, cache, Dalvik (and this is after you've flashed the CM10.2 zip twice like you did)
3.) Reboot device without flashing Gapps - this is to see if it boots up.
Let us know what happens.
Sent from my GT-P7510 using Tapatalk
Tomy_Delmar said:
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
Click to expand...
Click to collapse
Tomy, now it is getting clear- of course, I tought you already had Gapps on your CM10.1.3 installed so in such case they would definitely need to be updated to 4.3
Yes, the ROM shouold work perfectly fine also without Gapps
Your workflow sounds correct, but just to make sure: after first attempt to flash CM10.2 build, there should be a warning that all your data will be wiped, right? After that you must again choose the option "install zip" and install CM10.2. It will work this time.
If it doesn't work, download again the CM10.2 zip as it may be corrupted file. BTW, I didn't like that build for several reasons and returned to RC version.
If nothing helps, flash back your CM10.1.3 and restore your nandroid backup if important files were there. If the downgrade won't work for different partition of the /system, use my unbricking guide and revert to stock, then to CM10.1.3, then to CM10.2.
Keep step by step on the guide if you use it, it has important points to control before flashing. Flashing with re-partition needs always a PIT file, or with other words: without that file re-partition option mustn't be checked. Doing it simply by clicking the re-partition (like @Rohitdahiya adviced you to) without a PIT file checked under "PIT" would brick your i9000.
Soryuu said:
However, I had a similar problem installing a rom onto my tablet - different device, I know, but try this anyway and see if you get anywhere:
1.) Go back into recovery if its still bootlooping
2.) Wipe data, cache, Dalvik (and this is after you've flashed the CM10.2 zip twice like you did)
3.) Reboot device without flashing Gapps - this is to see if it boots up.
Let us know what happens.
Click to expand...
Click to collapse
Unfortunately, Wiping data, cache and Dalvik cache again after I had flashed CM 10.2 didn’t make it start.
tetakpatak said:
Tomy, now it is getting clear- of course, I tought you already had Gapps on your CM10.1.3 installed so in such case they would definitely need to be updated to 4.3
Yes, the ROM shouold work perfectly fine also without Gapps
Your workflow sounds correct, but just to make sure: after first attempt to flash CM10.2 build, there should be a warning that all your data will be wiped, right? After that you must again choose the option "install zip" and install CM10.2. It will work this time.
If it doesn't work, download again the CM10.2 zip as it may be corrupted file. BTW, I didn't like that build for several reasons and returned to RC version.
If nothing helps, flash back your CM10.1.3 and restore your nandroid backup if important files were there. If the downgrade won't work for different partition of the /system, use my unbricking guide and revert to stock, then to CM10.1.3, then to CM10.2.
Keep step by step on the guide if you use it, it has important points to control before flashing. Flashing with re-partition needs always a PIT file, or with other words: without that file re-partition option mustn't be checked. Doing it simply by clicking the re-partition (like @Rohitdahiya adviced you to) without a PIT file checked under "PIT" would brick your i9000.
Click to expand...
Click to collapse
When I tried to flash CM 10.2 the first time – at that time RC1 was the newest version – I was asked to flash it a second time, which I did. To be precise, the following message was shown:
This ROM uses an incompatible partition layout
You /data will be wiped upon installation
Run this update.zip again to confirm install
This message hasn’t been shown again since then. I flashed CM 10.1.3 again and tried to flash 10.2 a second time, but the message wasn’t shown again.
Going back to CM 10.1.3 worked without any problem.
------------------------------------------
Now I have CM 10.2 on my phone and it starts normally
I flashed Stock-Android 2.3.6 with Odin (v1.82). Tetakpatak, thank you for the excellent guide and the video! As written in the guide, I used "s1_odin_20100512.pit" as PIT-file.
(I executed Odin on an old computer with Windows XP 32bit, as the guide says Odin 1.82 works better with Win XP.)
Then I installed CM 10.2 over Stock-Android 2.3.6. I followed the official instructions:
http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd?setlang=en
(I executed Heimdall on my new computer with Windows 7. Heimdall 1.4RC2 doesn’t work on Win XP. If one executes Odin and Heimdall on the same PC, I could imagine this could lead to confusion, because Odin needs the Samsung-USB-drivers and Heimdall needs WinUSB. I’m not sure if this really leads to problems. But one should keep that in mind.)
I didn’t flash CM 10.1.3 before 10.2, because I didn’t need to restore a nandroid backup previously made with CM 10.1.3. There were no important data on the phone.
Many thanks to all who gave me advice and helped my solving the problem!
Tomy
HELP MEEE
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Pure_Android said:
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Click to expand...
Click to collapse
This is the forum for the original Galaxy S, not the Nexus 5, sorry mate
However I think your problem can be fixed by doing a full data/cache wipe so it might be worth a shot
Flash Boot.Img. This might solve the bootloop!
I think, You just need to flash the boot.img (available in the Cynogen Bundle Zip Folder) after installing Cynogen Mod. Me too got stuck on the animation part for a long time. Then I found out this:
CyanogenMod builds for endeavoru currently do NOT support any bootloader version number below: HBOOT 1.28. As the device is S-ON (security-on bootloader), for a working installation you must extract the boot.img from the installer zip and run fastboot flash boot boot.img from fastboot mode.
Source: Cynogen Mod Wiki
Pure_Android said:
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Click to expand...
Click to collapse
Which version of CyanogenMod are you using?
Hi Guys,
Lot of peoples had experienced trouble while enabling TDB for flashing two separate ROMs in MI3 ( Even me too ). But this thread will explain as an easy way to flash both ROM's without having any trouble.
I hope everyone knows about the CWM recovery installation and how it can be used for backup and restore processes. And those who don't know these process, then i would request them to check the xiaomi mi3 Q&A thread. you will get
Just to add some note before going into the flashing process, There are two system partition in MI3, System 1 and System 2.By default, TDB( True dual boot) is disabled and one common data partition is available for both two's systems.
Once you enabled TDB( True dual boot ) then the common data partition will split into two data partitions such as data1 and data 2. System 1 will use data1 and system 2 will use data2 contents. The data is meant to be user data such as installed apps,contacts etc
Why MIUI have been using a common data partition for both two system's?:silly:
Because the developers or beta testers can use the stable MIUI as well as beta MIUI ROMs in a single device without any trouble. Also no need to install each app on both rom's while switching. Because stock recovery will share the user data since they have a common user data partition.
But TDB, it doesn't share the user data ( data partitions ). it will say like system1 must use data1 and system2 must use data2. Hence we can install Aosp, CM or other source build in system1 and MIUI on system2 without any trouble.
The below steps will explain how to do this,
1) Take a CWM backup of your current MIUI ROM and copied to somewhere else ( your pc or sd card etc )
2) Go to recovery , wipe data/factory reset
3) Wipe cache and Wipe dalvik cache
4) Format System1 and System 2
5) Format data
6) After that, Enable TDB from the advanced section inside the recovery (Select wipe when it asked)
7) Once it is finished, then Select the Reboot recovery option and wait for few seconds for the recovery area.
8) Choose install ZIP then select the CM package and flash it to the System1 when it asked ( IT IS IMPORTANT THAT AOSP OR CM BUILD MUST BE IN SYSTEM 1 AND MIUI ON SYSTEM2, else it will ended up with boot loop). Also flash Google apps into the same system
9) After that , reboot the recovery again
10) Go to restore -> select CWM backup of your previous MIUI ROM -> Restore to system 2
11) Once it is restored, select the active system which one you need to boot. you can choose either system1 or system2 from the advanced active system option.
12 ) Reboot the device and do fun with both builds without having any trouble or force closed. .:good:
ALSO NOTE THAT I AM NOT RESPONSIBLE FOR ANY BRICKED DEVICE , TRY IT YOUR OWN RISK . I HAVE TESTED THIS WITH LATEST CM BUILD AND MIUI5..IT IS WORKING GREAT
Don't just go away after reading this and do click on thanks button If I helped you :laugh::laugh::fingers-crossed:
uuuhhmm...well explained Thnxx
RIPPER said:
uuuhhmm...well explained Thnxx
Click to expand...
Click to collapse
Nice.
I wish this thread existed a week ago
I understood stuff the hard way
What about mi4?
kottyz said:
What about mi4?
Click to expand...
Click to collapse
Who cares? Mi3 forum here.
@OP: you said "miui 5". So this doesn't work with miui6?
reneftw said:
Who cares? Mi3 forum here.
@OP: you said "miui 5". So this doesn't work with miui6?
Click to expand...
Click to collapse
Cm for mi3 is compatible with mi4 too as everything else released for mi3 because they use the same base.
reneftw said:
Who cares? Mi3 forum here.
@OP: you said "miui 5". So this doesn't work with miui6?
Click to expand...
Click to collapse
I haven't tested this with miui6 as I don't want to keep both beta ROM in a single device. Stable and beta that's a good choice for me.
According to the theory , it should work with Miui6. Remember to take a cwm backup first and try .:thumbup:
Sent from my MI 3W using XDA Free mobile app
Hi guys, I found this guide on the MIUI thread. There are few differences as for when to enable TDB and whipes. Does it make any difference?
1. Take a CWM backup of your current MIUI V6 system.
2. Disable TrueDualBoot in CWM (choose wipe) and reboot recovery
3. Do a factory reset on both systems (system1 & system2)
4. Clear cache
5. Clear Dalvik Cache of both systems (system1 & system2)
6. Format both system partitions (system1 & system2)
7. Format both data partitions (data1 & data2)
8. Flash CM 11 zip in SYSTEM1
9. Flash GAPPS in system1 (optional)
10. Enable TrueDualBoot in CWM (choose wipe) and reboot recovery
11. Restore CWM backup of your previous system to SYSTEM2
12. Voila!! Now choose your default system. (System1 for CM & System2 for MIUI). Have fun with CM11 guys
Pallmalli said:
Hi guys, I found this guide on the MIUI thread. There are few differences as for when to enable TDB and whipes. Does it make any difference?
1. Take a CWM backup of your current MIUI V6 system.
2. Disable TrueDualBoot in CWM (choose wipe) and reboot recovery
3. Do a factory reset on both systems (system1 & system2)
4. Clear cache
5. Clear Dalvik Cache of both systems (system1 & system2)
6. Format both system partitions (system1 & system2)
7. Format both data partitions (data1 & data2)
8. Flash CM 11 zip in SYSTEM1
9. Flash GAPPS in system1 (optional)
10. Enable TrueDualBoot in CWM (choose wipe) and reboot recovery
11. Restore CWM backup of your previous system to SYSTEM2
12. Voila!! Now choose your default system. (System1 for CM & System2 for MIUI). Have fun with CM11 guys
Click to expand...
Click to collapse
Please do compare both thread and gather all the information that you need. Here I have explained a little bit about how TDB works and their concept. Hope it will give a better understanding to other fellows while using TDB
Sent from my MI 3W using XDA Free mobile app
Miui6 and AICP ROM working
Hi all.
I finally be able to enable TDB in MI3 with miui 6 and AICP ROM without any reboot so far (36 hours). Even when i wipe data, cache, system and Dalvik cache the phone experienced force closes on miui6 and reboots on CM11 and others.
But 2 days ago i discovered a folder on the SD partitation with the name 0 (zero) with all the information and packages of the CM11 ROM and erased it.
I did a clean install on both systems and put miui6 on system2 and AICP ROM on system1 and so far is working fine without FC in Miui and without reboots on AICP ROM.
Will installing cm 11 on mi 3 could void warranty??
when i go cwm recovery it shows system1 and system2
so my question is from should i start doing this method???
reneftw said:
Who cares? Mi3 forum here.
@OP: you said "miui 5". So this doesn't work with miui6?
Click to expand...
Click to collapse
MIUI 6 doesn't support TDB yet...I faced some awesome lag in the MIUI 6 ROM, to the point when I couldn't open any apps or do anything...Hadta disable TDB...
need expert advice
I may be asking vary basic or newbie question .. but looking for below solution and need someone advice..
I have MI3 with MIUI v34 STOCK ( I have not rooted or installed CWM).
What I want to achieve. I want to enable TrueDualBoot and once enable I want to install MIUI 6 developer rom on second partition (whichever partition is free for installation) and I will be using it as Primary ... and if anything goes wrong with MIUI6 I want to use the original/STOCK rom from 2nd partition.
How I can achieve ?
I have Question as below.
1. by default Stock rom is in which partition ?
2. Can I simply install CWM and install MIUI on other partition (i..e if Stock ROM is on partition then MIUI v6 on Parition 2 OR vice a varsa)
3. Or I must have to format system1 and system2 after enabling "TrueDualBoot" and must have to install STOCK ROM also ??
4. Also I should take Backup of Stock rom through CWM first OR should enable TrueDaulBoot and then should Take Backup ..?
Thanks in advance.
rbdudani said:
I may be asking vary basic or newbie question .. but looking for below solution and need someone advice..
I have MI3 with MIUI v34 STOCK ( I have not rooted or installed CWM).
What I want to achieve. I want to enable TrueDualBoot and once enable I want to install MIUI 6 developer rom on second partition (whichever partition is free for installation) and I will be using it as Primary ... and if anything goes wrong with MIUI6 I want to use the original/STOCK rom from 2nd partition.
How I can achieve ?
I have Question as below.
1. by default Stock rom is in which partition ?
2. Can I simply install CWM and install MIUI on other partition (i..e if Stock ROM is on partition then MIUI v6 on Parition 2 OR vice a varsa)
3. Or I must have to format system1 and system2 after enabling "TrueDualBoot" and must have to install STOCK ROM also ??
4. Also I should take Backup of Stock rom through CWM first OR should enable TrueDaulBoot and then should Take Backup ..?
Thanks in advance.
Click to expand...
Click to collapse
First you need to understand that MI3 can hold two Roms either Miui or CM based or Aosp using TDB. But the aosp and cm based ROM should be in system 1. Else you will end with bootloop. So, now going to your question,
once you installed CWM, you will be able to see which system is currently active ( for eg : it will show like system 1 (active) then it will be the running system )
So first take the backup of active system then keep it. Then, format data and system after enabling TDB. So, Now the current status is no Roms on 2 system partitions. At this time you can choose which one you need to install or not. And which backup you would like restore to system 1 or system 2 .But keep in mind that cm or aosp should be in system 1. Also you can keep two miui ROM on both these system like miui5 on system 1 and miui6 on system 2. The thing is MI3 can handle two Roms whatever it is but aosp or cm based ROM should be in system 1 if you trying to install it.
Hope it helps
Sent from my MI 3W using XDA Free mobile app
Thanks mate..Well explained.. i did TDB AOSP and MIUI..till now without any problem such as FC and lag..thanks again
Awesome guide...
When we Enable TDB in CWM doesn't it ask for an option to copy data 1 to data 2?
In that case can I just copy data1 to data2 and then flash MIUI ROM on system2?
Edit: Did exactly that and now I have Xenon HD lollipop on system1 and MIUI 6 on system2.
Thanks.
Hey,
All my steps:
1. Root device: LINK
2. Install TWRP: LINK
3. Install new CyanogenMod by this LINK
After installing CyanogenMod 13 and boot.img my device just in boot loop.
I've tried install 12 CM, but no luck.
So ... what I need to do ?!
Thank you for your HELP !
Okay, to install the cm there athe this steps:
1 - Open TWRP (I don't know what you used, but i assume you used this one https://dl.twrp.me/klte/twrp-3.0.0-0-klte-klte.img.tar.html )
2 - Wipe Dalvik / ART Cache, Cache, Data and System (do not wipe Micro SDCard or Internal Storage, you need your zips)
2.5 - Wipe System is the only one you probably doens't HAVE to do, but i recommend to do. The other 3 are 101% necessary, because old apps or app caches WILL bootloop you.
IF YOU WIPED SYSTEM, DO NOT REBOOT
3 - Install the Rom Zip file (Extracted from the post https://download.cyanogenmod.org/get/klte-latest.zip )
4 - Install Open Gapps or (anything) Gapps for 6.0 (Again, extracted form the post http://opengapps.org/?api=6.0&variant=nano )
4.5 - As you know, the korean rom is kind different, it requires te boot.img for some reason, well, flash it. (This one, of course http://forum.xda-developers.com/attachment.php?attachmentid=3823989&stc=1&d=1469502182 )
5 - Reboot and enjoy
If you did anything different or in any different order, i suggest you try again, and just a detail, this is the S5 Mini section, not the S5, DO NOT USE files you found here, they WILL bootloop your device
I've recently purchased Galaxy S5 SM-G900T, Marshmallow, not rooted. Would like to flash Lineageos 17.1. Here is my plan and list of questions. I would be greatly appreciate your comments and suggestions.
1. Flash TWRP version 3.1.0-1 *.tar.md5 file (Use Odin 3.12.3 or 3.11.1?).
2. Make Nandroid backup of the Android phone and save it on SD card. Partitions: System, System.img, Data/user data (excl. storage?), Boot, Vendor, Vendor.img, Cache, Recovery, EFS, Persist, Logo.
3. Copy LOS 17.1 (zip), Magisk 18.1, Magisk uninstaller and Magisk manager.apk (latest stable 7.5.1) to microSD.
4. Reboot in TWRP (deny to install TWRP app) and make clean install of LOS 17.1:
Wipe> Adv. wipe> System, Data, Cache, Dalvik.
Flash LOS 17.1 (zip), Kernel. Install Magisk 18.1, Magisk manager.apk
5. Reboot from TWRP to the System.
6. Root with Magisk, install BusyBox and Substratum modules.
Android 6.0.1 (Marshmallow) probably was installed OTA. Should I first downgrade to the Lollipop or even KitKat or it is OK to go with Marshmallow? Or may be it is better to make a factory reset?
It is not clear for me if Bootloader is unlocked in my Galaxy SM-G900T from T-mobile (see attached pic). If it is locked can I still flash TWRP with Odin?
Are the versions of the Odin, TWRP, Magisk I've listed before OK and safe to flash on Samsung galaxy S5 SM-G900T?
Lineage OS flashing: Is it enough just to wipe System/Data/Cache or I must to Format it? Should I also wipe/format internal storage?
should I install kernel along with LOS or I can do that later?
Kltetmo, Qualcomm Snapdragon 801, Qualcomm MSM8974PRO-AC
ARMv7 Processor rev 1
Bootloader G900TUVU1GQC2
Build MMB29M.G900TUVU1GQC2
Not rooted
OK, you should know that you are wanting to jump to the most Beta builds for the S5!
(Meaning, you might find that some things don't work, or may be a bit buggy on your phone) Now, if you agree to that, then ... (Only IMHO....)
First, if I was in your shoes (...just purchased a used Galaxy S5 SM-G900T) I would actual get the most up to date Stock Rom (Android 6.0.1 for you phone, ( can be found here on XDA, as well as Sammobile could really take a lot of time to download there)) Reason- So you know that you are 100% safe at Stock with all the
Seems that your on the right path, just missing some minor, changes. i just might do it a little different.. could just be me though...
1- Get Stock Rom for your phone
2 - Get Recovery- well TWRP 3.1.0-1 can work, the 3.3.1 seems to have issues to Android 10 Roms
3 - Odin 3.10 seems to work well (IMHO) but can use 3.12 or 3.11
4 - Yes, put the 17.1 image on your Micro SD Card...like in your Lineage Folder, also put any other files you may need or want IN the Micro SD card (i.e. latest Magisk 20.4 and Magisk Manager 7.5.1 9at time of writing)
5 - Flash the latest Stock Rom, (have the Reboot box checked-so it Reboots when done flashing) unplug the phone
6 - Flash your recovery (when doing so, make sure that you do not have the Reboot checked, so you can boot into recovery after powering off the phone, when done flashing, Boot to Recovery
7- True, when in Recovery, DON'T install their darn App! But also, go into settings, and set up Your Recovery... then all should be fine from this point
8 - Make your Backup (Check every box in the list, can even change the Name if you want) It will put it in the TWRP Folder in Internal Storage
9 - Clean up Stock, Wipe System, Data, Cache and Dalvik Cache. (I would format system to ext4 as well as Data Just to make sure nothing is there from Stock) (check out Clean Flashing for the S5)
10 - Flash your 17.1 image, (it will ask to wipe cache and dalvik cache after flashing, DO SO) then in your case flash your Kernel, wipe, flash Magisk, wipe, flash Magisk Manager, wipe
11 - Boot to system after flashing the Rom and all the goodies. Relax... it will take several minutes to boot.
Just a reminder, Make sure that you have charged battery! Don't want any issues with power
hopefully you can see the minor changes I made from your steps 1 - 6 ! Just my 2 cents, but like I said you seem to be on right track.
Now, another good idea that I do, is, I actually Copy my TWRP folder in the Internal SD card to my External Micro SD Card ( So I don't lose my back ups, in case of an issue with the phone)
Hope this helps you out
Hi. I wanted to share with you this guide so you can flash newer Retrofit Dynamic Partitions on Redmi 7A/8A/8 devices.
These kind of ROM's can be found on SDM Mi439 Telegram group as well. Here are the instructions.
You will also need to use newer recoveries. For flashing Android 12+ rom I recommend official TWRP 3.7.0 for Mi439.
Download TWRP 3.7.0 here: CLICK ME!
Download OrangeFox here: CLICK ME!
(Note for OrangeFox: Use A11 version for Android 11 Roms, and A12 version for Android 12 and 13)
Instruction to flash newer ROMs with Retrofit Dynamic Partitions:
(Please Ignore recovery errors at the first installation, because every system partitions are blank at the moment)
(If you proceed with using old unsupported recoveries, You'll surely ending up getting errors)
First time installation of Retrofit Dynamic Partitions ROMs:
1. Flash recovery with Retrofit Dynamic Partitions support (Download Here)
2. Enter the newly flashed recovery
3. Flash Retrofit Dynamic Partitions Converter (Download Here)
4. Wipe metadata partition
5. Flash the ROM
6. Factory Reset (Format data is recommended) if you're coming from a different ROM
7. Reboot and Enjoy
Update ROM from Standard Partitions to Retrofit Dynamic Partitions:
Follow without Factory Reset step
Update ROM from Retrofit Dynamic Partitions to Retrofit Dynamic Partitions:
1. Enter recovery
2. Flash the update
3. Reboot and Enjoy
Switch to another Retrofit Dynamic Partitions ROM:
1. Enter recovery
2. Flash the ROM
3. Factory Reset (Format data is recommended)
4. Reboot and Enjoy
Revert back to standard partition ROM:
1. Enter recovery
2. Untick "Settings > Unmount System before installing a ZIP"
3. Do "Advanced > Unmap Super Devices"
4. Flash the ROM
5. Factory Reset (Format data is recommended)
6. Reboot and Enjoy
Warning! You can't flash static partition ROM on dynamic partitions and vice versa!
All ROMs that I post here are RDP (Retrofit Dynamic Partitions)!
works perfekt
thank you!
I rebooted after step 3 ( Flash Retrofit Dynamic Partitions Converter )
Now i am trapped in bootloader and installing twrp in boot or recovery didn't work.
How do i get back into recovery?
I think you need to reflash your ROM and try again.
Use same rom you have and download from this site https://xiaomifirmwareupdater.com/miui/pine/
You need to use fastboot on your pc.
But... Keep in mind I can be wrong. I have same problem restoring system partition with 12.5.3 miui using pbrp on my redmi 7a.
You could probably flash only recovery partition using CMD command on pc as well.
I hope it will help you.
lee99 said:
You could probably flash only recovery partition using CMD command on pc as well.
Click to expand...
Click to collapse
I tried to flash recovery using Terminal (Linux , the same way like i flashed twrp before installing the dynamic partitions, but it didn't work.
lee99 said:
I think you need to reflash your ROM and try again.
Use same rom you have and download from this site https://xiaomifirmwareupdater.com/miui/pine/
Click to expand...
Click to collapse
Yeah that was my solution, too.^^
After that i was more carefully and made exactly what the instructions told me and after wiping and formating data lineageos started =)
Thanks for your help =)
I am glad I could help
Do you have a video on how to install it on redmi 7a since I have a problem that gives me an error in everything I try in twrp 3.7.0
certerox said:
Do you have a video on how to install it on redmi 7a since I have a problem that gives me an error in everything I try in twrp 3.7.0
Click to expand...
Click to collapse
Hey I would like some help^^ I came from the stock MIUI rom and tried to flash it with the guide, went well with the help of the video but rebooted after step 3 and now the phone is stuck into fastboot and I cannot unbrick it.. I tried to flash TWRP again but still stuck, so now I'm trying to reinstall the stock MIUI rom.
The xiaomi website offers me two files, one "fastboot" and one "recovery". I tried to use MiFlash with these files but the app run like crap and keep giving me errors..
So I have the recovery zip file, inside there is a boot.img : I tried to flash that the same way I flashed TWRP with fastboot but the phone still is stuck in fastboot.
The fastboot file is a .tgz, inside there is a .tar and inside there is .bat files with the image but I cannot run the flash_all.bat with fastboot commands. I tried various all returned errors. I think I don't know the proper command to write as I'm noobish here : first time trying to flash
Any help appreciated I can't even turn the phone off lol I fear that the battery die and loose my phone
Edit : So it manage to unbrick it with the MiFlash app, just downloaded again and it worked fine this time ^^
Had to use the fastboot file, extracted and flash_all_lock option to make it work if someone face the same problem as me.
Hello
Nem1x said:
Hi. I wanted to share with you this guide so you can flash newer Retrofit Dynamic Partitions on Redmi 7A/8A/8 devices.
These kind of ROM's can be found on SDM Mi439 Telegram group as well. Here are the instructions.
You will also need to use newer recoveries. For flashing Android 12+ rom I recommend official TWRP 3.7.0 for Mi439.
Download TWRP 3.7.0 here: CLICK ME!
Instruction to flash newer ROMs with Retrofit Dynamic Partitions:
(Please Ignore recovery errors at the first installation, because every system partitions are blank at the moment)
(If you proceed with using old unsupported recoveries, You'll surely ending up getting errors)
First time installation of Retrofit Dynamic Partitions ROMs:
1. Flash recovery with Retrofit Dynamic Partitions support (Download Here)
2. Enter the newly flashed recovery
3. Flash Retrofit Dynamic Partitions Converter (Download Here)
4. Wipe metadata partition
5. Flash the ROM
6. Factory Reset (Format data is recommended) if you're coming from a different ROM
7. Reboot and Enjoy
Update ROM from Standard Partitions to Retrofit Dynamic Partitions:
Follow without Factory Reset step
Update ROM from Retrofit Dynamic Partitions to Retrofit Dynamic Partitions:
1. Enter recovery
2. Flash the update
3. Reboot and Enjoy
Switch to another Retrofit Dynamic Partitions ROM:
1. Enter recovery
2. Flash the ROM
3. Factory Reset (Format data is recommended)
4. Reboot and Enjoy
Revert back to standard partition ROM:
1. Enter recovery
2. Untick "Settings > Unmount System before installing a ZIP"
3. Do "Advanced > Unmap Super Devices"
4. Flash the ROM
5. Factory Reset (Format data is recommended)
6. Reboot and Enjoy
Warning! You can't flash static partition ROM on dynamic partitions and vice versa!
All ROMs that I post here are RDP (Retrofit Dynamic Partitions)!
Click to expand...
Click to collapse
Hello, the (to) retrofit dynamic partitions converter ROM doesn't work with [pine] - Redmi 7A. It is signed with [olive]. So this thread should be renamed or updated. THX
olivier_b said:
Hello
Hello, the (to) retrofit dynamic partitions converter ROM doesn't work with [pine] - Redmi 7A. It is signed with [olive]. So this thread should be renamed or updated. THX
Click to expand...
Click to collapse
You clearly didn't read the whole thread and it's title.
Men i really dont understand what is retrofit dynamic partition, when i used to install roms was with xiamitool v2 or flashing wiping data and thats it but this i really dont get it can you help me?
Nem1x said:
You clearly didn't read the whole thread and it's title.
Click to expand...
Click to collapse
That's true because this time I've read the guide and it works! Thx
Nem1x said:
Hi. I wanted to share with you this guide so you can flash newer Retrofit Dynamic Partitions on Redmi 7A/8A/8 devices.
These kind of ROM's can be found on SDM Mi439 Telegram group as well. Here are the instructions.
You will also need to use newer recoveries. For flashing Android 12+ rom I recommend official TWRP 3.7.0 for Mi439.
Download TWRP 3.7.0 here: CLICK ME!
Download OrangeFox here: CLICK ME!
(Note for OrangeFox: Use A11 version for Android 11 Roms, and A12 version for Android 12 and 13)
Instruction to flash newer ROMs with Retrofit Dynamic Partitions:
(Please Ignore recovery errors at the first installation, because every system partitions are blank at the moment)
(If you proceed with using old unsupported recoveries, You'll surely ending up getting errors)
First time installation of Retrofit Dynamic Partitions ROMs:
1. Flash recovery with Retrofit Dynamic Partitions support (Download Here)
2. Enter the newly flashed recovery
3. Flash Retrofit Dynamic Partitions Converter (Download Here)
4. Wipe metadata partition
5. Flash the ROM
6. Factory Reset (Format data is recommended) if you're coming from a different ROM
7. Reboot and Enjoy
Update ROM from Standard Partitions to Retrofit Dynamic Partitions:
Follow without Factory Reset step
Update ROM from Retrofit Dynamic Partitions to Retrofit Dynamic Partitions:
1. Enter recovery
2. Flash the update
3. Reboot and Enjoy
Switch to another Retrofit Dynamic Partitions ROM:
1. Enter recovery
2. Flash the ROM
3. Factory Reset (Format data is recommended)
4. Reboot and Enjoy
Revert back to standard partition ROM:
1. Enter recovery
2. Untick "Settings > Unmount System before installing a ZIP"
3. Do "Advanced > Unmap Super Devices"
4. Flash the ROM
5. Factory Reset (Format data is recommended)
6. Reboot and Enjoy
Warning! You can't flash static partition ROM on dynamic partitions and vice versa!
All ROMs that I post here are RDP (Retrofit Dynamic Partitions)!
Click to expand...
Click to collapse
Hi, i tried to flash the "Retrofit Dynamic Partitions Converter" but its shows me the "ERROR: This package is for device: pine, olives, mi439; this device is olive.
Updater process ended with ERROR: 7" / <image>. How to fix this.
iotzbruhh said:
Hi, i tried to flash the "Retrofit Dynamic Partitions Converter" but its shows me the "ERROR: This package is for device: pine, olives, mi439; this device is olive.
Updater process ended with ERROR: 7" / <image>. How to fix this.
Click to expand...
Click to collapse
Open twrp terminal and type mi439, then hit enter. Try to flash again.
For better experience use ofox recovery.
Nem1x said:
First time installation of Retrofit Dynamic Partitions ROMs:
1. Flash recovery with Retrofit Dynamic Partitions support (Download Here)
2. Enter the newly flashed recovery
3. Flash Retrofit Dynamic Partitions Converter (Download Here)
4. Wipe metadata partition
5. Flash the ROM
6. Factory Reset (Format data is recommended) if you're coming from a different ROM
7. Reboot and Enjoy
Click to expand...
Click to collapse
NOT WORK FOR PINE !
Used recommended TWRP 3.7.0
itmasen1 said:
NOT WORK FOR PINE !
Used recommended TWRP 3.7.0
Click to expand...
Click to collapse
Try using orangefox. And read guide again!