Hello together,
after 3 Days of reading and searching and testing solutions, I have to ask you if you can solve my problem.
I can't find the reason by myself, because I'm new with this topic. I want to install a Custom ROM on my Huawei P 8 Lite Alice from 2015, but everytime I flash any Custom ROM which should match, it ends in a bootloop (huawei logo, then logo custom rom, then huawei logo etc....).
My device:
Huawei P8 Lite ALE L21 from 2015 - Alice
Built number before start this "project": ALE-L21C432B634
Android 6
Emui 4.0.3
Bootloader unlocked with code generated by dc-unlocker
No Root
My prefered Custom ROM is Lineage OS 14.1 and I tried to flash it following the steps in this thread:
[url]https://forum.xda-developers.com/p8lite/development/rom-lineageos-14-1-p8-lite-t3824247[/URL]
1. step - Flash TWRP
First Problem was to install the TWRP 3.1.1 linked in this thread:
[url]https://forum.xda-developers.com/p8lite/orig-development/twrp-t3583180[/url][/URL]
To flash the TWRP image with adb caused no problem. When I boot into recovery, TWRP starts, but when I touch anything on the screen (like swipe to unlock) the System boots (With OS installed it boots the OS and without it stucks at huawei logo). Booting again into TWRP is no Problem.
I solved this problem with a TWRP image 3.1.0-1 from this forum:
[url]https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-p8-lite.2476/huawei-p8lite-neues-inoffizielles-twrp-3-1-0-1-von-surdu_petru-xda.826139.html[/URL]
The thread references on the same XDA thread mentioned above, but it is linked to another version of TWRP image. This Version 3.1.0-1 is working good.
2. step - flash EMUI 4.1
I flashed the EMUI Update B896 with TWRP. In the thread to the Lineage OS 14.1 mentioned above, it is described that you need this update. I used the linked .zip.
Steps:
1. Wipe Data, internal storage, system, Dalvik Cache, Cache (all except micro sd card).
2. Format Data
3. Reboot into TWRP
4. flash .zip from SD card
5. Wipe Davlik Cache and Cache
5. Reboot System
After that :
Android 6
Build number: ALE B896
EMUI: 4.1
The updated ROM works good.
3. Step - Flash Lineage OS 14.1
Steps:
1. Wipe Data, internal storage, system, Dalvik Cache, Cache (all except micro sd card).
2. Format Data
3. Reboot into TWRP
4. flash .zip from SD card
5. Wipe Davlik Cache and Cache
5. Reboot System
Result Boot Loop :victory:
Trouble shooting:
I tried to install different TWRP versions, but only the TWRP 3.1.0-1 works.
I useb adb sideload to flash the Lineage
I flashed the EMUI 4.03. I had before and than Lineage 14.1 (EMUI works, but Lineage doesn't)
I wiped dalvik cache and data, cache after flashing Lineage, to fix the bootloop
I flashed versions of Lineage OS 14.1 from different dates and different download websites
I flashed different Custom ROMS - all the same Problem except Lineage 13.0. Lineage 13.0 boots till it is ready to "preparing" apps and than boots again.
Now I don't know what do do and would be very thankful to get some new ideas to try or perhaps a solution
Thank you! :highfive:
The ROM needs Emui 4.1 B895/B896 update to be installed first
Then unlock bootloader, flash twrp then flash ROM
Thank you for your help. I'll try this. So I have to lock bootloader again first?
No. You flash the update with twrp
Go to step 6 in the first post on this thread
https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Keran_3066 said:
No. You flash the update with twrp
Go to step 6 in the first post on this thread
https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Click to expand...
Click to collapse
Maybe I described it not so good in my first post but I think I did it already exactly like that.
1. Unlock bootloader
2. Flash TWRP
3. Flash Emui 4.1 update B896 ( its working on my phone now)
4. Flash TWRP again
5. Flash Custom Rom ( evertime the result is a bootloop)
Or did I overlook anything?
Sorry I didn't read that part where you flashed emui 4.1
Lineage os 14.1 works for me.
Did you try Resurrection Remix OS
https://forum.xda-developers.com/p8lite/development/rom-t3606568
Keran_3066 said:
Sorry I didn't read that part where you flashed emui 4.1
Lineage os 14.1 works for me.
Did you try Resurrection Remix OS
https://forum.xda-developers.com/p8lite/development/rom-t3606568
Click to expand...
Click to collapse
Thank you very much, that you tried to help me Im happy about all suggestions.
Yes I tried RR and Paranoid, but its the same Problem. I'm wondering that the EMUI Roms which are not officially from Huawei work and any custom rom does not. Maybe there is a Problem with the structure of my system but I dont know anything about this stuff and how to find out the reason for my Problem:laugh:
Maybe you know a command for adb or android terminal app to check if everything is ok?
Jaba Wup said:
Maybe you know a command for adb or android terminal app to check if everything is ok?
Click to expand...
Click to collapse
I'm kinda out of ideas
Keran_3066 said:
I'm kinda out of ideas
Click to expand...
Click to collapse
I feel like you:laugh: thanks and have a nice evening:good:
Related
I have HM2014818 model (variant of HM2014811) and had the latest MIUI ROM 7.2 (developer). I decided to flash CM 13 first which resulted in bootloop then I flashed Resurrection remix which also ended in error. Now the procedure which i followed is.
1. Enter recovery mode TWRP 3.0.2-0-wt88047
2. Wipe data, system, cache , dalvik cache (formatted user data as well for last resort)
3.Flashed The ROM
4. FLashed GAPPS (Tried without flashing as well)
5. Wipe cache/dalvik cache (tried without it also)
6. Reboot System results in boot loop or boot stuck (with MI logo)
Here what I have done so far to correct it.
Downloaded stock ROM for Redmi 2 (latest developer version 6.4.14) unzipped it extracted boot.img file, replaced the resurrection remix boot.img file with stock boot.img file. The system booted, the only problem is the resurrection remix logo takes 15 minutes to change its animation sequence, it is not at all smooth. It is laggy. How to fix this can anyone give the appropriate boot.img image for faster boot keeping in mind my phone only boots from stock Boot.img file.
Restore to kitkat partitions (instructions from here).
Then wipe all data, reboot to recovery, and then flash again.
zeomal said:
Restore to kitkat partitions (instructions from here).
Then wipe all data, reboot to recovery, and then flash again.
Click to expand...
Click to collapse
What is the error ? And how is this method gonna correct it ?
nrdnandan said:
What is the error ? And how is this method gonna correct it ?
Click to expand...
Click to collapse
I have no idea of what the error per se is, but I remember having faced a similar problem and this is how I corrected it. I'm no developer.
nrdnandan said:
What is the error ? And how is this method gonna correct it ?
Click to expand...
Click to collapse
U can't flash cm13 or other mm ROMs if u r on miui lollipop bootloader.. Just downgrade to KitKat.
U can use this guide http://forum.xda-developers.com/redmi-2/how-to/rom-stock-kitkat-miui-6-fastboot-rom-t3375693
Sent from my 2014818 using XDA-Developers mobile app
Hi,
So I have created this thread just because I can see many people creating new threads as after flashing CM 14.1, their phone doesn't boot up. So for all those who are going to flash CM 14.1 or have already flashed it and can't get it working, this thread is for you.
What you will need:
1. Rooted OnePlus X (Obviously)
2. Custom Recovery (TWRP recommended)
3. Latest CM 14.1 build
4. Arsenic Kernel or BlackReactor Kernel
So this is how you get CM 14.1 working on your OPX (make sure your battery is above 80% just to be sure that nothing will go wrong considering battery's point of view)
Make sure you have backed up everything before performing the following steps as the process will wipe your data completely. (I would recommend to take a Titanium backup of all user apps and then taking a nandroid backup of system and data)
1. Download the required files and place them in your SD Card or internal storage
2. Reboot your device into recovery
3. Go to wipe, and swipe to factory reset (Note! This will completely wipe all the data from your device including app data and SMS! This won't wipe the contacts but just to be safe, have a backup of all your contacts)
4. Go to Wipe again, and go to Advanced wipe, select the following partitions - System, Cache, Dalvik cache. Swipe to wipe (Note! Make sure you have a backup of the System as this will wipe the Operating System from your phone!) Although this step isn't necessary, I like to do it.
5. Go to install, and direct to the location where you have saved the CM 14.1 zip file and the kernel. Select the files, and swipe to flash.
6. If you want anything else in your system, direct to that location, select the zip file, and swipe to flash. (Note! You need not flash the SuperSU zip file as CM offers Root access in developer options)
7. Reboot your system and wait for it to boot.
Viola! Your device is now running official CM 14.1 nightly.
Hope this helps! ?
Downloads:
1. Latest CyanogenMod nightly - found here https://download.cyanogenmod.org/?device=onyx
You can have any version of the nightly as long as it is CM 14.1
2. Arsenic Kernel R32 (or R31) - http://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Open the above thread and follow the guide
OR
Black Reactor kernel v1.0 - http://forum.xda-developers.com/oneplus-x/development/kernel-blackreactor-kernel-oneplus-x-t3460989
-Reserved-
Good Evening, @aamodjoshi23 THX a Lot. You are my Hero. Finally it works.
greetings
If you're facing some Error 7 while trying to flash cm 14.1, you can try updating the bootloader following this
http://forum.xda-developers.com/showpost.php?p=69267239&postcount=2560
I used the Oxygen OS 3.13 full ROM as recommended, edited updater-script (following those instructions)
Immediately after flashing the OOS 3.13 rom, you don't have to reboot.
I immediately flashed twrp 3.0.3 original from https://dl.twrp.me/onyx/
I then rebooted into twrp 3.0.3 (using the reboot button in twrp, then bootloader)
Then I installed (in this order):
cm 14.1 (https://download.cyanogenmod.org/?device=onyx)
arsenic kernel (as recommended above)
opengapps
Not sure if this step is necessary, but I wanted to let twrp patch the rom to not overwrite twrp so I rebooted into twrp again (using reboot --> bootloader in twrp)
Then I used reboot --> system
First boot took a while, but now I have nougat!!
kenel zip every time
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
allons-y said:
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
Click to expand...
Click to collapse
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
aamodjoshi23 said:
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
Click to expand...
Click to collapse
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
shashanksachdeva said:
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
Click to expand...
Click to collapse
First of all we need more info about your current ROM recovery etc.
Fap4k said:
First of all we need more info about your current ROM recovery etc.
Click to expand...
Click to collapse
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
shashanksachdeva said:
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
Click to expand...
Click to collapse
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Fap4k said:
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
This is because you flashed wrong recovery twrp 3.0.3 is for new bootloader and you are on old bootloader..that's why it all happened..so you just need to flash old recovery..then follow given link to upgrade bootloader and recovery.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
I've got a good news and bad news for you.
The bad news is, no one has the older 2.8.x TWRP image files and there are no threads that have the download links for the older version of TWRP. So you're stuck and you have lost your recovery. You have lost everything... Having no recovery means you can't do a lot of things like factory reset, any wipe of a partition, you won't be able to update your system, you won't be able to flash zip files to enhance your experience and many more... I'm sorry my friend...
The good news is, I've got you covered. I had saved the older TWRP so that if anyone one day would need that recovery image, I would be able to help them.
Download the older TWRP from here : https://drive.google.com/file/d/0B2Ms-zaNd3SiTmpxX0UtYUV2R1k/view?usp=drivesdk
Flash it. You should get back your recovery.
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Fap4k said:
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Click to expand...
Click to collapse
using resurrection remix marshmallow 6.0...
Plush suthar said:
using resurrection remix marshmallow 6.0...
Click to expand...
Click to collapse
Did you ever updated bootloader?
If not than update your bootloader and install latest recovery!!
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
By stuck on boot, I didn't know you meant that it showed only the OnePlus logo and not even powered by Android.
In that case, follow this guide to update your bootloader :
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Hello guys, this is my first guide here. So as the title says, I will show you how to install Lineage OS on your Redmi Note 3 device (kenzo).
So before following the guide, your device should have a unlocked bootloader and TWRP recovery.
I will also tell you how to fix in calls audio issue if you are facing it after installing Lineage OS 14.1
So let's begin.
First download the rom (refer to the official thread).
Download Cm14.1 firmware for kenzo (you can find it in the same rom thread)
Download Gapps (any package like micro or nano)
Procedure:-
1- Boot to TWRP recovery.
2- Go to wipe menu. Wipe system, data, dalvik cache and cache.
3- Now go to mount, and mount cust and persist.
4- Go to install. Select the firmware zip file you had downloaded. Install it. (This fixes in call audio problem)
5- After installing it you can unmount cust and persist from the mount menu.
6- After it flash the official Lineage OS rom which you had downloaded. (Install menu, zip)
7- After rom is flashed, flash Gapps package. (Install menu, zip)
8- After flashing Gapps, go to wipe and wipe cache, dalvik cache.
9- Reboot your device
10-Enjoy!
First Reboot will take a while so don't panic... Download Google camera if you want a more stable camera (since stock is quite buggy).. Also you can use Umang's Flashlight fix for the buggy Flashlight button.
Just in case you want to root the device, just download root add-on (found in official thread)
Enjoy the experience.. ?
xzy99 said:
Hello guys, this is my first guide here. So as the title says, I will show you how to install Lineage OS on your Redmi Note 3 device (kenzo).
So before following the guide, your device should have a unlocked bootloader and TWRP recovery.
I will also tell you how to fix in calls audio issue if you are facing it after installing Lineage OS 14.1
So let's begin.
First download the rom (refer to the official thread).
Download Cm14.1 firmware for kenzo (you can find it in the same rom thread)
Download Gapps (any package like micro or nano)
Procedure:-
1- Boot to TWRP recovery.
2- Go to wipe menu. Wipe system, data, dalvik cache and cache.
3- Now go to mount, and mount cust and persist.
4- Go to install. Select the firmware zip file you had downloaded. Install it. (This fixes in call audio problem)
5- After installing it you can unmount cust and persist from the mount menu.
6- After it flash the official Lineage OS rom which you had downloaded. (Install menu, zip)
7- After rom is flashed, flash Gapps package. (Install menu, zip)
8- After flashing Gapps, go to wipe and wipe cache, dalvik cache.
9- Reboot your device
10-Enjoy!
First Reboot will take a while so don't panic... Download Google camera if you want a more stable camera (since stock is quite buggy).. Also you can use Umang's Flashlight fix for the buggy Flashlight button.
Just in case you want to root the device, just download root add-on (found in official thread)
Enjoy the experience..
Click to expand...
Click to collapse
it this a joke? this looks like a chinese copy of a guide posted 1 week ago and is only 2 posts under this:
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
what is your intention?
@massan1 I hope you have eyes through which you can read properly. No offence brother. Well, I didn't copy it. Plus that guide is made for those who have locked bootloader. Second, I am posting this for those who want to clean install Lineage OS with the call audio fix. So, if you believe I have copied it , just keep believing it.
Keep burning.. I'll get ice packs for you. Thanks.
I was on cm 13 before flashing lineage OS 14.1..Now the issue iam facing is that while making calls without headphones the both myself and other person won't hear a thing. On reverting back to cm 13 everything works fine. Currently on nightly 07.02.2107
r28 said:
I was on cm 13 before flashing lineage OS 14.1..Now the issue iam facing is that while making calls without headphones the both myself and other person won't hear a thing. On reverting back to cm 13 everything works fine. Currently on nightly 07.02.2107
Click to expand...
Click to collapse
just flash upgraded firmware or change build.prop:
https://forum.xda-developers.com/re...stall-lineage-os-locked-t3546154/post70826457
Raaj52 said:
This is not a build.prop issue!! In order to work with the old firmware (patched one) you have to make fluence to none, this is done when you use patched VoLTE. If you make fluence to none the latest MM firmwares won't give sound in call, many are getting no sound because they are using the old patched firmware. Since the native VoLTE is fixed no need of the old firmware and you don't need to change fluence to none. Just flash the latest firmware and you are good to go.
Still doubt? OK then I need to tell you one more thing, The first patch for VoLTE for MIUI MM was made by me (you can check that in MIUI Global forum) and sudeep made a firmware.zip with my NON-HLOS.bin and I can see that the same is copied in the firmware.zip, in order to get fluence working in the patched firmware it should have used with the correct adspso.bin.
Many are thinking that changing firmware is useless but in reality it comes with lot of stability fixes, so I recommend everyone to update your firmware to the latest one instead of all this build.prop editing craps.
What is the problem if I edit build.prop? --> You have to edit your build.prop whenever you flash a ROM, you can't avoid it unless you flash the latest firmware.
Why I am so confident? --> Because I know what is firmware and How does it work!
If you have "no sound in calls" issue even after you change the firmware I recommend a clean mi flash tool flashing with the latest MIUI ROM (because it will fix all your partition related stuffs, instability issues)
@abhishek987 @akhilnarang could you please add the "solution for no sound in calls is to flash the latest firmware" in your first post?
Click to expand...
Click to collapse
i'm a newbie in the A/B partitions system previously i have installed many roms on many Android phones but all of them are below android 6.0. now i moved to Mi A1 and i flashed TWRP and rooted my phone with Magisk18 now i have tried to flash lineageOS 16 on stock Pie but when i tried to flash it asks for slot_a or slot_b and i dont know anything about a/b partitions so i quit installation and write this thread pls help.
iamranjodh said:
i'm a newbie in the A/B partitions system previously i have installed many roms on many Android phones but all of them are below android 6.0. now i moved to Mi A1 and i flashed TWRP and rooted my phone with Magisk18 now i have tried to flash lineageOS 16 on stock Pie but when i tried to flash it asks for slot_a or slot_b and i dont know anything about a/b partitions so i quit installation and write this thread pls help.
Click to expand...
Click to collapse
there you go
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
1. Flash or update to lastest stock rom
2. Boot twrp (don't flash TWRP, just boot) from:
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
3. Wipe to factory
4. Install LOS16
5. Reboot to bootloader and boot TWRP again
6. Flash gapps and magisk if you need it
That's what I did and works like a charm but I prefer RR.
Cheers!
ccalixtro said:
1. Flash or update to lastest stock rom
2. Boot twrp (don't flash TWRP, just boot) from:
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
3. Wipe to factory
4. Install LOS16
5. Reboot to bootloader and boot TWRP again
6. Flash gapps and magisk if you need it
That's what I did and works like a charm but I prefer RR.
Cheers!
Click to expand...
Click to collapse
This method is not working. We have to use a special bootable TWRP for LOS 16 Official builds.
Sent from my Mi A1 using XDA Labs
---------- Post added at 09:52 PM ---------- Previous post was at 09:33 PM ----------
iamranjodh said:
i'm a newbie in the A/B partitions system previously i have installed many roms on many Android phones but all of them are below android 6.0. now i moved to Mi A1 and i flashed TWRP and rooted my phone with Magisk18 now i have tried to flash lineageOS 16 on stock Pie but when i tried to flash it asks for slot_a or slot_b and i dont know anything about a/b partitions so i quit installation and write this thread pls help.
Click to expand...
Click to collapse
Try following these steps:
1. Download and boot this TWRP. Only boot it, don't flash it. https://drive.google.com/file/d/1LtLrNnL0h7alZaaOWADvc2Sf5aNkNukM/view
2. Wipe system, data, cache and dalvik. If you are encrypted, make a Format Data.
3. Go to Reboot and select other slot. (For example, if you are on Slot A, select Slot B)
4. Boot TWRP again.
5. Wipe system, data, cache and dalvik. Make a format data again.
6. Install latest LineageOS 16 Official nightly. You can select A or B.
7. Reboot to bootloader.
8. Boot TWRP again.
9. Flash GApps and Magisk (if you want root).
10. Reboot to system and enjoy Lineage!
Sent from my Mi A1 using XDA Labs
hi guys
i need a patch for z3 dual that would be able to run z3 single-sim roms on z3 dual in android 9 pie
can any develpoer make it for me?please
thanks
please
somebody help meeeeeee
I found some patch on old oreo Z3 thread.
Also, I read the LOS 15 thread today. You need a specific TWRP for D6633. But I can't find this file.
This patch only tested on oreo ROMs so I don't know if it will work on pie.
Anyway, there you go.
You'll need a clean flash. The steps are:
- Flash TWRP 3.3.1 (if you want to install LOS 16.0, flash the boot.img from the .zip)
- reboot to TWRP, wipe everything (system, cache, dalvik, data, internal storage. BUT if you store the ROM and gapps file on internal storage, DO NOT wipe internal storage)
- flash ROM, Gapps, reboot to TWRP
- flash this dualsim patch, reboot to system
Good luck.
Zerikwan said:
I found some patch on old oreo Z3 thread.
Also, I read the LOS 15 thread today. You need a specific TWRP for D6633. But I can't find this file.
This patch only tested on oreo ROMs so I don't know if it will work on pie.
Anyway, there you go.
You'll need a clean flash. The steps are:
- Flash TWRP 3.3.1 (if you want to install LOS 16.0, flash the boot.img from the .zip)
- reboot to TWRP, wipe everything (system, cache, dalvik, data, internal storage. BUT if you store the ROM and gapps file on internal storage, DO NOT wipe internal storage)
- flash ROM, Gapps, reboot to TWRP
- flash this dualsim patch, reboot to system
Good luck.
Click to expand...
Click to collapse
thanks man appreciate that
problem still exist
ive got another problem too
after flashing a rom i want to boot to recovery but recovery doesnt load i mean it just reboots again and again
i tried many wayz but still cant go to TWRP after flashing rom
foli2 said:
thanks man appreciate that
problem still exist
ive got another problem too
after flashing a rom i want to boot to recovery but recovery doesnt load i mean it just reboots again and again
i tried many wayz but still cant go to TWRP after flashing rom
Click to expand...
Click to collapse
Sorry, I forgot to mention that.
The TWRP 3.3.1 from the link is only work on LOS 16.0. If you flash another ROM with TWRP 3.3.1, the TWRP will break.
In other word, you must flash the correct TWRP for the ROM. Also, in the past, there is a specific TWRP for Z3 dual but the link is dead.
Zerikwan said:
Sorry, I forgot to mention that.
The TWRP 3.3.1 from the link is only work on LOS 16.0. If you flash another ROM with TWRP 3.3.1, the TWRP will break.
In other word, you must flash the correct TWRP for the ROM. Also, in the past, there is a specific TWRP for Z3 dual but the link is dead.
Click to expand...
Click to collapse
i got frustrated completely