{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Greetings!
This is a general how-to thread (similar to my S3 mods, tips & tricks) and will offer help, guides, mods and even software.
I will do my best to answer any questions regarding OnePlus One, or Android in general. Feel free to contact me with your feedback (questions/praises/critics), either here or through pm.
GUIDES
[HOW-TO] Boot KitKat, LolliPop and MarshMallow roms in MultiROM
For discussion on MultiROM, how to install and use it, please visit the original thread here.
As you already know, since their arrival Lollipop roms require you to flash the a new version of firmware. This is regulary updated with CM nightly releases and without it you get bootloops. However, if you use CM11 roms and flash the new firmware, your proximity sensor gets broken, resulting in a Screen of Death during calls. Other issues may appear as well. This can be fixed by flashing latest CM11 modem (contains only NON-HLOS.bin).
When you have your MultiROM up and running, you will need three things: updated CM12.x/CM13 firmware, CM11 modem and the proximity sensor fix. All files will be attached to this post and regulary updated. So download and transfer them to your device.
Make sure you are using TWRP MultiROM Recovery v2.8.6.0, otherwise modem/firmware will not install! Flash on primary ROM and reboot Recovery.
CM12.x/CM13 firmware (05-15-2015) - - - AndroidFileHost /// Dev-Host
CM11 modem (radio) only - - - AndroidFileHost /// Dev-Host
Proximity sensor fix for CM12.x/CM13 Roms* - - - AndroidFileHost /// Dev-Host
Now, depending on which rom you are running as primary and which one(s) as secondary/-ies, do the following in one recovery session:
1. flash CM12.1/CM13 firmware from Install menu in TWRP Recovery
2. flash CM11s modem from Install menu in TWRP Recovery
3a. if you are running CM12.x/CM13 rom as primary, flash proximity sensor fix from Install menu in TWRP Recovery
3b. if you are running CM12.x/CM13 rom(s) as secondary/-ies, flash proximity sensor fix from MultiROM menu in TWRP Recovery
4. reboot
NOTICE 1: After flashing CM11 modem, baseband version in CM13 roms will be unknown, but calls and connectivity should work without problems.
NOTICE 2: To revert my proximity sensor fix (restore original sensors.msm8974.so), flash this on primary or secondary CM12.x/CM13 (depends on where you have it) - - - AndroidFileHost /// Dev-Host
If you cannot install modem as zip in recovery, feel free to use my cmd program attached below.
Extract this zip to your PC, then extract NON-HLOS.bin from CM11s modem zip and put it in the ModemFastbootFlash folder. Finally run INSTALL.bat and follow instructions.
Seperate commands are:
Code:
adb reboot bootloader
fastboot flash modem NON-HLOS.bin
fastboot reboot
*flashable zip contains old blob sensors.msm8974.so, from SlimSaber LP Jan.08.
Credits
@KINGbabasula and @Tasssadar for MultiROM Mod/Recovery and Manager
@Natakranta for pointing out the proximity sensor fix
SOFTWARE
Cyanogen OS 12.1.1 (YOG7DAS2K1) Stock Kernel
If you flashed the wrong custom kernel (phone won't boot) or simply want to revert back to stock, flash this in Recovery.
Download
md5: 12f390ae56395aa4e611a5de736023bc
Fastboot-flashable Cyanogen OS 12.1.1 ROM (YOG7DAS2K1)
Extract the zip to your desktop and follow INSTRUCTIONS.txt and INSTALL.bat program.
Download
md5: 5acdcbc9792c3e7ea4dbf9d37430d73d
Recovery-flashable Cyanogen OS 12.1.1 ROM (YOG7DAS2K1) Rooted!
ROM is completely stock with added SuperSU root.
Download
md5: 247d06e4853866dbee7b75058c0e6ff4
=== Older versions ===
Cyanogen OS 12.1 (YOG4PAS3JL) Stock Kernel md5: 7b20c4b5759410117f2ee7ad8d289794
Fastboot-flashable Cyanogen OS 12.1 ROM (YOG4PAS3JL) md5: bc40efee3a12f0da6bd2866fb3127e76
Recovery-flashable Cyanogen OS 12.1 ROM (YOG4PAS3JL) Rooted! md5: 2c80f700e700ee557865c7acd6476fd4
Cyanogen OS 12.1 (YOG4PAS2QL) Stock Kernel md5: 7753b852a06d3bbd46359647513f753d
Fastboot-flashable Cyanogen OS 12.1 ROM (YOG4PAS2QL) md5: cb3f528099a6bd46c7450ff44c8939a4
Recovery-flashable Cyanogen OS 12.1 ROM (YOG4PAS2QL) Rooted! md5: 813121c52ce12e76fc5bdc6bdd0c1103
Cyanogen OS 12.1 Stock Kernel (YOG4PAS1N0) md5: 0c137df35edc41ea35d3111bd62a6210
Fastboot-flashable Cyanogen OS 12.1 ROM (YOG4PAS1N0) md5: 8037e519874afe9fd9db320c30d0b6d1
Recovery-flashable Cyanogen OS 12.1 ROM (YOG4PAS1N0) Rooted! md5: 1a7a971d643920f7106f14e9591b69ee
Cyanogen OS 12 Stock Kernel (YNG1TAS2I3) md5: 27a93d38906eac3efadf8568a0ba195d
Fastboot-flashable Cyanogen OS 12 ROM (YNG1TAS2I3) md5: 5c10792f845d7d42e69b900ffedfa1e2
Recovery-flashable Cyanogen OS 12 ROM (YNG1TAS2I3) Rooted! md5: f11392490e0d4e56d0a850147adbb8df
MODS
Bypass Xposed for Lollipop bootloop
DEPRICATED: Please use official Xposed uninstaller http://forum.xda-developers.com/showthread.php?t=3034811
Incompatible Xposed modules and SELinux set to Enforcing will make your phone bootloop. I couldn't find a flashable zip, so I made one myself. It disables Xposed Installer and system boots normally. Once you've found the problematic module, simply wipe data for Xposed Installer and boot again.
Source guide
MMWolverine said:
As you already know, since their arrival Lollipop roms require you to flash the a new version of firmware. This is regulary updated with CM12 nightly releases and without it you get bootloops. However, if you use CM11(s) roms and flash the new firmware, your proximity sensor gets broken, resulting in a Screen of Death during calls. Other issues may appear as well. This can be fixed by flashing CM11s modem (contains only NON-HLOS.bin).
When you have your MultiROM up and running, you will need three things: updated CM12 firmware, CM11s modem and the CM12 proximity sensor fix. All files will be attached to this post and regulary updated. So download and transfer them to your device.
CM12 firmware
CM11s modem
CM12 proximity sensor fix*
Now depending on which rom you are running as primary and which one(s) as secondary/-ies, do the following in one recovery session:
1. flash CM12 firmware from Install menu in TWRP Recovery
2. flash CM11s modem from Install menu in TWRP Recovery
3a. if you are running CM12 rom as primary, flash CM12 proximity sensor fix from Install menu in TWRP Recovery
3b. if you are running CM12 rom(s) as secondary/-ies, flash CM12 proximity sensor fix from MultiROM menu in TWRP Recovery
4. reboot
*flashable zip contains old blob sensors.msm8974.so, from SlimSaber LP Jan.08.
Click to expand...
Click to collapse
thank you sir.i was looking for this.
Good work wolverine, how about cm11 as primary, latest 05Q and cm12 second, cm 11 has proximity issues, cm12 works fine
I have the latest cm12 firmware flashed otherwise it will always reboot cm12
Sent from my Darkside of 1+1
xanthrax said:
Good work wolverine, how about cm11 as primary, latest 05Q and cm12 second, cm 11 has proximity issues, cm12 works fine
I have the latest cm12 firmware flashed otherwise it will always reboot cm12
Sent from my Darkside of 1+1
Click to expand...
Click to collapse
Just 05Q modem on primary and the proximity fix on your cm12 secondary.
Thank you very much. Solved my proximity sensor problem. Running cm11s as primary with cm12 blisspop as secondary.
hi, but in cm12 firmware static_nvbk.bin is 0 byte so if flash this zip overwitre partition static_nvbk with 0???
static is about 10MB
no problem to flash this partition on primary rom?
Thanks for noticing, but since there were no reports so far, I think it wouldn't cause major problems. static_nvbk.bin wasn't even part of firmware since 44S.
Correction, I've checked tobitege's and darkobas's firmaware zips, static_nvbk.bin is 0b in both. Latest cm12 nighlty the same. So all ok.
Thanks Wolverine it works like a dream. Many thanks for putting this thread together.
I have wiped the device clean using mutirom custom twrp recovery and installed CM12 Rom.
I'm using mutirom v30 with CM12 as primary and cm11s as secondary.
I have never installed the firmware update.
I do not get boot loops with cm12 nor cm11s, do I have to still install the firmware?
I face the issue with proximity issue while answering calls on cm12
I should flash firmware update on CM12 ROM and then install proximity fix that's all right?
I don't know if I should flash the cm11 modem fix on cm12 rom or cm11 rom.
Excuse me for being a noob :silly: , have been using android only from the past 90 days or so
Well you can try only proximity sensor fix on cm12. But to avoid possible issues, I would advise you to flash cm12 firmware, cm11s modem and the proximity sensor fix, all three on primary partition t.i. cm12 rom.
Should you flash only the firmware update, the prox. sensor on cm11s wouldn't work. And the fix is for lollipop roms running with the older modem.
I have installed proximity fix only, didn't work.
Installed cm12 firmware update and proximity fix, didn't work.
In fact those made it worse. I had screen locked only for incoming calls and unlocking would still allow me to answer. Now I have blacked out screen for incoming and outgoing calls too. Even the unlock button would unlock the screen. Will try installing all three else I'm restoring.
Edit: The steps you provided had worked
Thanks.
Looking for the 11S firmware
Hey. Looking to try out CM12 roms. But the first one I tried out (crDroid) failed to flash in recovery (TWRP).
So I want a stock firmware I can flash in case flashing something breaks something.
The link you posted. Is that the one I'd want?
Lastly, your post is awesome. I'd like to multi boot. But it's a little over my head. Any chance of making a simpler to read version?
Hey,
the link you're looking for is at the end of 2nd post "To revert back CM11s firmware, flash from Install menu in TWRP Recovery."
File is named as "CM11s_XNPH05Q_modem_firmware.zip", from the latest stock OTA update.
Before flashing any LolliPop rom you need to install CM12 firmware. As per your request I'll simplify the MultiROM guide.
1. use MultiROM Manager app to install MultiROM v32, Recovery 2015-03-05 (0) and Kernel
Note: the CM12 AK Kernel from this app is outdated (v.010), it will boot, but please visit http://ak.hiddenbytes.org/ to upgrade
2. now boot into MR TWRP recovery and in the Advanced section under MultiROM add, manage or remove secondary roms
For example: to install gapps on a secondary rom, press "List ROMs", select it and press Flash ZIP.
3. if you plan on multi-booting CM11 and CM12 roms, you have to flash CM11s modem (2nd link in 2nd post) + the proximity sensor fix (see points 3a-3b)
I hope the rest is self-explanatory, should you have any further Q, feel free to ask.
Hi @MMWolverine ! Great Guide !
I am dual booting CM11S and CM12 (primary) using the following step
I had a rooted stock CM11S with latest AK Kernel installed
I just added the CM12 as a secondary ROM and once it finished installing, I swapped it with CM11S
The only problem I face on the CM11S now is that once I turn off the screen, it simply refuses to turn back on
Note: CM12 works without any problems
Any help is appreciated. Thanks in advance.
EDIT: I was able to fix the problem in CM11S by unchecking the "check proximity sensor for accidental screen unlock" option under Display & Lights
Ok, so let me double check this:
I have CM12 (Blisspop) as primary ROM. Works without problems.
I have CM11 (stock rooted) as secondary ROM. I have the proximity problems during calls, but by unchecking the 'accidental wakeup' option at least I can turn the screen on.
Shoud I now:
Flash CM12 proximity sensor fix and CM11 modem only (so only follow steps 2 and 3a) or should I flash CM12 modem firmware too?
1. flash CM12 firmware from Install menu in TWRP Recovery
2. flash CM11s modem from Install menu in TWRP Recovery
3a. if you are running CM12 rom as primary, flash CM12 proximity sensor fix from Install menu in TWRP Recovery
3b. if you are running CM12 rom(s) as secondary/-ies, flash CM12 proximity sensor fix from MultiROM menu in TWRP Recovery
4. reboot
Click to expand...
Click to collapse
rajesh261092 said:
Hi @MMWolverine ! Great Guide !
I am dual booting CM11S and CM12 (primary) using the following step
I had a rooted stock CM11S with latest AK Kernel installed
I just added the CM12 as a secondary ROM and once it finished installing, I swapped it with CM11S
The only problem I face on the CM11S now is that once I turn off the screen, it simply refuses to turn back on
Note: CM12 works without any problems
Any help is appreciated. Thanks in advance.
EDIT: I was able to fix the problem in CM11S by unchecking the "check proximity sensor for accidental screen unlock" option under Display & Lights
Click to expand...
Click to collapse
Flash CM11S modem as primary (in twrp from "Install") and CM12 proximity sensor fix on CM12 rom as secondary (from MultiRom menu). I'm not a big fan of swapping roms, had some issues in the past. But the feature is there so you can use it of course.
dio62000 said:
Ok, so let me double check this:
I have CM12 (Blisspop) as primary ROM. Works without problems.
I have CM11 (stock rooted) as secondary ROM. I have the proximity problems during calls, but by unchecking the 'accidental wakeup' option at least I can turn the screen on.
Shoud I now:
Flash CM12 proximity sensor fix and CM11 modem only (so only follow steps 2 and 3a) or should I flash CM12 modem firmware too?
Click to expand...
Click to collapse
You most likely already flashed CM12 firmware, otherwise you would already have problems on BlissPop. So only CM11s modem and proximity sensor fix.
Related
Hi XDA Team and developers!
I have been following XDA-developers from as long as i couldn't remember and every time i needed help I was able to find solution from one or another thread, but this this time it turned out diffrently. So I created an account on XDA with a hope of getting reply.
Basically I am having a LG G2 LS980 [sprint] , I am not in USA and I wanted to use 3G [WCDMA :2100] on my LG g2 but I was unable to do so. I got a hint on internet that installing any other rom can help me using 3G internet, So i decided to install Cyanamogen 11 nightly build. I did following steps and it resulted into a bootloop:
1. Rooted it correctly with Ioroot.
2. Installed Custom Recovery TWRP correctly, it is still sccesible.
3.then i downloaded " cm-11-20150106-NIGHTLY-ls980.zip " and " gapps-kk-20140606-signed " form official links on Cyanamogen website.
4.Booted into TWRP and went into wipe and did a factory reset.
5.then installed " cm-11-20150106-NIGHTLY-ls980.zip " first
6.then i installed " gapps-kk-20140606-signed "
7. I rebooted it from TWRP to system
8. I got a booloop and i was like "meh i got it messed up "
9. Then i tried to follow some threads. I tried to recover it to stock recovery. but unable to do any thing right.
10. I downloaded LG flash tool, LS980ZVC_12.tot, a dll file named Megaload and a dll file specific to LS980.
11. then when i tried to flash stock recovery through LG Flash tool after several tries of 6 hours every thing went alrigh but when at the final step it had to be installed I got error " Download error" " USB port mapping " i guess it was something like this. i choosed the dll file in ls980 folder on the link mentioned below. chose manual method, chose this rom " LS980ZVC_12.tot" and tried both " board dll " and " upgrade dll " . but got same error.
12. Then on XDA i read that i should try to install the a .laf file. he said to do so with the help of fastboot, but i am unable to use fastboot. [ if someone could guide me, it will be real pleasure].
Ok now a lot of ancient history. coming to the point in some simple questions.
What I want : I want the phone in a working condition. If there is possible to run 3g [wcdma 2100] on it then i have no issue if any custom rom get installed with some minor issue.
or flash it back to stock rom.
What I can access: I can access ADB sideload, Adb push, TWRP , and download mode of lg g2.
What i am having in stock for lg g2: LS980ZVC_12.tot , cm-11-20150106-NIGHTLY-ls980.zip , gapps-kk-20140606-signed , LG flash tool, adb, fast boot, and some other stuff.
Please help me, and i will really post the complete method , how i figured my problem.
Some of the links i have been trying to get help form.
http://forum.xda-developers.com/showthread.php?t=2432476
http://forum.xda-developers.com/showthread.php?t=2477595
http://forum.xda-developers.com/showthread.php?p=47831752#post47831752
http://forum.xda-developers.com/showthread.php?t=2590528
So wait you are trying to install CyanogenMod 11? Mate CyanogenMod 12 came out for the ls980!
You must first do your thing in lgflash tool. After that install root with towelroot and install twrp or philz touch. Finally, in twrp or philz install the newest build and bravo it should be done!
When you installed custom recovery, did you use autorec?
Evnul000 said:
So wait you are trying to install CyanogenMod 11? Mate CyanogenMod 12 came out for the ls980!
You must first do your thing in lgflash tool. After that install root with towelroot and install twrp or philz touch. Finally, in twrp or philz install the newest build and bravo it should be done!
Click to expand...
Click to collapse
But i Guess cyanogen 12 is not stable right now, it has e some major bugs.
so i went out for cyanogen 11.
but how to do my thing with lg flash tool?
[HOW-TO]Restore Sprint LG G2 to Stock [TUT 1/3]: http://youtu.be/NRwlxeUprZE
Watch that video it should help you.
Hi Friend,
First thing, do not panic. You are not hard bricked, you have access to the recovery so we can fix your phone.
Can you please tell me how you installed the TWRP, have you used FreeGee for this?
You need to downgrade aboot for installing flash, so if you have used FreeGee then we have one less thing to worry about.
So the files you need to get Cyanogenmod are,
1. Recovery
2. CM11 and GAPPS zip files
3. ZV8 modem file ( "downloads.codefi.re/autoprime/LG/LG_G2/G2_modems" and the file name is "LGLS980_ZV8_RADIO.zip" ).
You have recovery and zips so only thing to donwload will be ZV8 radio.
Once you have it follow below steps in given sequence( if you do not know how to do the steps then please ask me ),
1. Wipe dalvik,cache, system and data ( DO NOT wipe Internal Storage ).
2. Flash CM11 zip.
3. Flash Gapps ( optional )
4. Flash ZV8 radio which you will download from mentioned link above.
5. Reboot.
If you still are bootlooped then I would suggest to clean dalvik and cache and try to reboot.
The above steps are given considering you are having LG G2 LS980, else the step 4 mentioned for ZV8 will not be applicable and may be removed or replaced based on your version.
If you still have a problem then let me know. I will be happy to help.
avinash.sarnaik said:
Hi Friend,
First thing, do not panic. You are not hard bricked, you have access to the recovery so we can fix your phone.
Can you please tell me how you installed the TWRP, have you used FreeGee for this?
You need to downgrade aboot for installing flash, so if you have used FreeGee then we have one less thing to worry about.
So the files you need to get Cyanogenmod are,
1. Recovery
2. CM11 and GAPPS zip files
3. ZV8 modem file ( "downloads.codefi.re/autoprime/LG/LG_G2/G2_modems" and the file name is "LGLS980_ZV8_RADIO.zip" ).
You have recovery and zips so only thing to donwload will be ZV8 radio.
Once you have it follow below steps in given sequence( if you do not know how to do the steps then please ask me ),
1. Wipe dalvik,cache, system and data ( DO NOT wipe Internal Storage ).
2. Flash CM11 zip.
3. Flash Gapps ( optional )
4. Flash ZV8 radio which you will download from mentioned link above.
5. Reboot.
If you still are bootlooped then I would suggest to clean dalvik and cache and try to reboot.
The above steps are given considering you are having LG G2 LS980, else the step 4 mentioned for ZV8 will not be applicable and may be removed or replaced based on your version.
If you still have a problem then let me know. I will be happy to help.
Click to expand...
Click to collapse
Thanks a lot avinash. Well it was my mistake i gues problem was due to some drivers and reboot needed.
now i am having a working LG G2 Ls980. But the funny thing is that all i wanted to was enable 3g[wcdma 2100] on my phone. however 2g [gsm] was working fine on it.
But after i restored it to orignal stock rom succesfully. It is not detecting any sim card, instead i am getting a sim card icon along my battery in header. it is with a " X " sign in red. If I am not wrong , It is now factory unlocked.
Just wanna know that will installing a custom rom like cyanogen will sim unlock it, and is 3g[wcdma 2100] is supported by this model, i mean is its hardware capable of running that network, Because i read that it support UMTS 2100 and i think WCDMA 2100 is same as UMTS 2100. so will it be able to run 3g if i flash Cyanogen 11?
I am not a die hard fan of cyanogen , if it is possible to unlock its stock rom, then having no issue.
Waiting for reply
avinash.sarnaik said:
Hi Friend,
First thing, do not panic. You are not hard bricked, you have access to the recovery so we can fix your phone.
Can you please tell me how you installed the TWRP, have you used FreeGee for this?
You need to downgrade aboot for installing flash, so if you have used FreeGee then we have one less thing to worry about.
So the files you need to get Cyanogenmod are,
1. Recovery
2. CM11 and GAPPS zip files
3. ZV8 modem file ( "downloads.codefi.re/autoprime/LG/LG_G2/G2_modems" and the file name is "LGLS980_ZV8_RADIO.zip" ).
You have recovery and zips so only thing to donwload will be ZV8 radio.
Once you have it follow below steps in given sequence( if you do not know how to do the steps then please ask me ),
1. Wipe dalvik,cache, system and data ( DO NOT wipe Internal Storage ).
2. Flash CM11 zip.
3. Flash Gapps ( optional )
4. Flash ZV8 radio which you will download from mentioned link above.
5. Reboot.
If you still are bootlooped then I would suggest to clean dalvik and cache and try to reboot.
The above steps are given considering you are having LG G2 LS980, else the step 4 mentioned for ZV8 will not be applicable and may be removed or replaced based on your version.
If you still have a problem then let me know. I will be happy to help.
Click to expand...
Click to collapse
I am pretty sure that i am holding a lg g2 ls980 , but i am not sure about these " ZVs" versions. Currently i am having a sprint locked ls980 which i flashed to a ZVC but you are saying to flash a ZV* radio file, are you sure it will not brick my phone, because i read somewhere on XDA that if a wrong software build is flashed then i can brick my phone. I dont remember which version was installed when it arrived. so shall i proceed with the procedure mentioned above?
plus also tell me whether bootloop after flashing cyanogen is due to not installing ZV8, [yes i tried installing cyanogen again.]
Hi,
Good to know that your phone is alive again.
The LS980ZVA and LS980ZVC from sprint patch the Loki support and hence break the ROM compatibility of the device.
So to answer your question, YES the bootloop is due to not having a proper modem for the ROM to function.
You need to have the ZV8 radio for rom to bootup properly.
So I would suggest you go forward with the steps I have given. I do it all the time. Just take the backup of current system before you proceed further.
Also for the other question regarding the unlocking the SIM, so NO the custom rom will not lock/unlock your sim. You have to do the things like APN copy and carrier folder replace etc to unlock your SIM.
Also the only thing you will miss from stock is Stock camera, you can get it from
"forum.xda-developers.com/showthread.php?"p=57931628#post57931628"
Happy flashing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ls980 cm12 Install Help
Hi Friend,
Looking fwd for your help i tried to put CM12 on my LG LS980 and got stuck in BOOT LOOP
Currently im using
SOFT : CloudyG2 2.2
BUILD : KOT491
KERNEL : 3.4.102
ANDROID 4.4.2
BASEBAND : M8974A-AAAANAZM-2.0.20046
I'm not an expert in flashing and just followed the steps as mentioned in XDA form to update it to CM 12
i recovered by re flashing cloudyg2 suggest what i missed that caused BOOT LOOP
thanks
parnsh said:
Hi Friend,
Looking fwd for your help i tried to put CM12 on my LG LS980 and got stuck in BOOT LOOP
Currently im using
SOFT : CloudyG2 2.2
BUILD : KOT491
KERNEL : 3.4.102
ANDROID 4.4.2
BASEBAND : M8974A-AAAANAZM-2.0.20046
I'm not an expert in flashing and just followed the steps as mentioned in XDA form to update it to CM 12
i recovered by re flashing cloudyg2 suggest what i missed that caused BOOT LOOP
thanks
Click to expand...
Click to collapse
What steps did you do? You flashed ZV8 modem right? Wiped system?
hi, i'm running cm 12, twrp 2.7.0.0, and when i wanted to flash cm 12.1 i got the following error:
"error executing updater binary in zip"
i tried:
1. wipe
2. updating to twrp 2.8.7 (and then came back to 2.7.0.0)
3. installing few cm nightlies
well, nothing worked. iv'e read a lot on line, and what i did came from there, the only thing i didnt try is to flash a different bootloader because i couldn't find a straight forward answer what to install (and i'm scared to brick the damn thing)
what should I do?
THANK YOU!!!!!!
Do not use 2.7.0.0, use at least version installed by Autorec v2.
Flash LP bootstack. Nemax bootloader changer or Daniel Stuart's or dgravy's for example. Bumped version except for Resurrection Remix.
MB525 said:
Do not use 2.7.0.0, use at least version installed by Autorec v2.
Flash LP bootstack. Nemax bootloader changer or Daniel Stuart's or dgravy's for example. Bumped version except for Resurrection Remix.
Click to expand...
Click to collapse
First of all, thank you so much!! now, ive looked at the nemax bootloader changer thread and it some posts there says that a KK bootloader is needed. so should i use contrary to the nemax thread?
Nearly all those stacks include the same kk bootloader. They are ZIPs, you can look into them with WinRAR for example and compare CRCs of the aboot.bins. Do you have a D802?
followup question - if i want to go back to cm 12 - can i undo the bootstack flash? if not, what should i do to go back?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
Click for feature list
Flashing Instructions:
Pre-installation:
TWRP (Shrp)
gapps (Opengapps)
Magisk 20.0 or newer for root (after first boot) - (Magisk)
First time installing crDroid to your Redmi 5A, or coming from another ROM:
<!-- ** Make sure you're running the latest TWRP Treble Recovery-->
Copy crDroid zip, gapps zip to your device
Boot into Recovery
Wipe cache, system, & data (or just cache & system for a dirty flash).
Flash ROM
Flash gapps
Flash Magisk ( optional )
Reboot System
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
Sources:
ROM: https://github.com/crdroidandroid
Kernel:
https://github.com/agustk404/kernel_xiaomi_msm8917
Download:
ROM https://crdroid.net/riva
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/10.0/changelog_riva.txt
Known issues:
- You Tell Me
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks To :
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Contributors:
@agustk404
@sunnyraj84348
ROM OS Version: 10.0 Q
ROM Kernel: Linux 3.18.x
ROM Firmware Required: Unlocked Bootloader
Based On: Lineage OS
Version Information
Status: Stable
Stable Release Date: 08-06-2020
@agustk404 If i am currently on miui 11.0.2 ,how do I downgrade to miui 10.1.1 using the firmware that has been provided without flasing the full rom via edl or fastboot mode.
When installing linease os 17.1 I flashed that firmware via twrp then wiped the system,data and cache and then flashed linease os and gapps. But every time sim and wifi didn't work. Restoring persist backup did nothing.
Only way it worked was to flash full rom (10.1.1) via fastboot then let it go upto android setup screen and then restart to recovery, wipe and flash the rom. If i just flashed the fastboot rom and then without restarting wiped and flashed the linease os rom either wifi or sim didn't work. I think something similar may happen here.
So what is the proper use of the miui 10.1.1 firmware that you have provided if I am currently on miui 11.0.2?
Nougat firmware flashing is necessary?
Kernel?
currently in MIUI 11 and TWRP 3.2.3.2. it always boot loop when try to boot into SHRP recovery,
And I also can't install the ROM with TWRP either.
Have installed it from MIUI 11, I downgraded to Nougat with flashable zip O to N from Indian Youtube.
Recovery : orange fox 9
Installed after made everything wiped, cache, dalvik, data, system and vendor, rhen formatted. The only problem i have so far are bad mic and audio quality. I compare it with other phone with miui 10 installed. I don't know if it caused by the kernel, because i can't install the kernel linked above, or it is had been installed along the rom itself.
Thank you dev, this rom is amazing. Hope it can be better.
Partha Dip said:
@agustk404 If i am currently on miui 11.0.2 ,how do I downgrade to miui 10.1.1 using the firmware that has been provided without flasing the full rom via edl or fastboot mode.
When installing linease os 17.1 I flashed that firmware via twrp then wiped the system,data and cache and then flashed linease os and gapps. But every time sim and wifi didn't work. Restoring persist backup did nothing.
Only way it worked was to flash full rom (10.1.1) via fastboot then let it go upto android setup screen and then restart to recovery, wipe and flash the rom. If i just flashed the fastboot rom and then without restarting wiped and flashed the linease os rom either wifi or sim didn't work. I think something similar may happen here.
So what is the proper use of the miui 10.1.1 firmware that you have provided if I am currently on miui 11.0.2?
Click to expand...
Click to collapse
Just look on yt, there are easy downgrade tutorial from indian channel youtube. com/watch?v=tAp5emSaJz8 easy downgrade tutorial. I'm not Indian but can understand it. I'm not Indian but can understand it.
rom has been updated to 6.8 version
is nougat firmware needed?
Camera not working after trouble installing ERROR: 7
agustk404 said:
rom has been updated to 6.8 version
Click to expand...
Click to collapse
Sorry to post my issue as answer since i did not find a button on the page to post a new issue.
Camera not available
Android Camera App crashes ... no message
Simple Camera App from f-droid displays follow message on start:
"Es ist ein Fehler aufgetreten: Open camera android.hardware.camera2.CameraAccessException: CAMERA_DISCONNECTED(2): Camera service is currently unavailable"
I am using crDroidAndroid-10.0-20200709-riva-v6.8.zip
I used cdDroidAndroid-8.1-20181211-riva-v4.7 for 1,5 years with camera working.
Installing crDroidAndroid-10.0-20200709-riva-v6.8.zip was tricky:
1. attempt installing with newest twrp-3.4.0-0-riva displays:
Warning: No file_contexts assert failed: riva.verify_trustzone("TZ.BF.4.0.5-157266") == "1"
Updater process ended with ERROR: 7
I found a workaround there: lineageosdownloads . com / fix-error-7-lineage-os
basically i edited updater-script in the zip file; in file updater-script i removed the assert line
Then installation worked fine. Everything else seems to work fine
Is there a way to get the camera working?
andro-try said:
Sorry to post my issue as answer since i did not find a button on the page to post a new issue.
Camera not available
Android Camera App crashes ... no message
Simple Camera App from f-droid displays follow message on start:
"Es ist ein Fehler aufgetreten: Open camera android.hardware.camera2.CameraAccessException: CAMERA_DISCONNECTED(2): Camera service is currently unavailable"
I am using crDroidAndroid-10.0-20200709-riva-v6.8.zip
I used cdDroidAndroid-8.1-20181211-riva-v4.7 for 1,5 years with camera working.
Installing crDroidAndroid-10.0-20200709-riva-v6.8.zip was tricky:
1. attempt installing with newest twrp-3.4.0-0-riva displays:
Warning: No file_contexts assert failed: riva.verify_trustzone("TZ.BF.4.0.5-157266") == "1"
Updater process ended with ERROR: 7
I found a workaround there: lineageosdownloads . com / fix-error-7-lineage-os
basically i edited updater-script in the zip file; in file updater-script i removed the assert line
Then installation worked fine. Everything else seems to work fine
Is there a way to get the camera working?
Click to expand...
Click to collapse
2hours later:
I tried to flash a new firmware because this should update low-level driver
fw_riva_miui_HM5AGlobal_V11.0.2.0.OCKMIXM_b247c0c04e_8.1.zip
After that the device is nearly bricked.
No TWRP, No Android, only fastboot
flashing TWRP again does not change things. Only some blue stripes on the screen after short time with "mi" logo.
How can i go now to find out what i can do. The only thing working is fastboot on device and fastboot command on linux PC.
Looks like not much chance of repair
Can i flash this without downgrading to MIUI 10 with TWRP treble?
kenzahem said:
Can i flash this without downgrading to MIUI 10 with TWRP treble?
Click to expand...
Click to collapse
No. You must on last nougat firmware.
dnisp said:
No. You must on last nougat firmware.
Click to expand...
Click to collapse
Okay thanks, i will flash this soon.
Sorry guys , now i drop this official support because now i already move to new device. Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
<!-- change according to your needs -->
Backup your data to PC, OTG flash drive
Now reboot to recovery
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Flash crDroid zip
Flash recovery from the download link
Reboot to system
Update installation:
<!-- change according to your needs -->
Boot to recovery
Flash a zip with crDroid
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm710
Download:
ROM https://crdroid.net/sirius>
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/12.0/changelog_sirius.txt
Known issues:
[*]None
Visit official website @ crDroid.net
crDroid sirius Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
thanks for you great work.
Is the face unlock work?
Yes it is.
-----
Love thise ROM thanks for you great work.
Only thing it miss is buld in call record.
Could anybody get OP's twrp from https://t.me/uixdessDrive/20 and upload to here?
I use latest official TWRP, this ROM installs and works like charm. but I can't boot into twrp ever after, it stuck at TWRP's logo screen forever.
I guess it's because this ROM flashes new keymaster partition which crashes official twrp.
Anyway I should try TWRP posted by OP but can't download from that link. Could anyone help?
NexusRunner said:
Could anybody get OP's twrp from https://t.me/uixdessDrive/20 and upload to here?
I use latest official TWRP, this ROM installs and works like charm. but I can't boot into twrp ever after, it stuck at TWRP's logo screen forever.
I guess it's because this ROM flashes new keymaster partition which crashes official twrp.
Anyway I should try TWRP posted by OP but can't download from that link. Could anyone help?
Click to expand...
Click to collapse
I tried to attach it here but not uploaded i don't know why.
yamabokra01 said:
I tried to attach it here but not uploaded i don't know why.
Click to expand...
Click to collapse
Could you upload it to MEGA?
NexusRunner said:
Could you upload it to MEGA?
Click to expand...
Click to collapse
Don't use it.
I just flash it then I got bootloop + no recovery + no bootloader.
Now I'm trying to open the back of the device to put it in edl mode
yamabokra01 said:
Don't use it.
I just flash it then I got bootloop + no recovery + no bootloader.
Now I'm trying to open the back of the device to put it in edl mode
Click to expand...
Click to collapse
omg wish your device recovered soon
I flashed the ROM using official twrp. It went OK but no longer boot into twrp.
I managed to install magisk without recovery (by patching and fastboot flash boot.img), but can't install gapps without a working recovery.
Maybe I should start over again and try the other A12 ROM with built in gapps. But for now I feel good with this ROM. I think maybe I will try it without gapps for a little longer.
NexusRunner said:
omg wish your device recovered soon
I flashed the ROM using official twrp. It went OK but no longer boot into twrp.
I managed to install magisk without recovery (by patching and fastboot flash boot.img), but can't install gapps without a working recovery.
Maybe I should start over again and try the other A12 ROM with built in gapps. But for now I feel good with this ROM. I think maybe I will try it without gapps for a little longer.
Click to expand...
Click to collapse
I payed 30$ and recovered my mobile.
Then i flashed a rom and for the second time i flashed the recovery again and my mobile again dead
UIxDess said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
<!-- change according to your needs -->
Backup your data to PC, OTG flash drive
Now reboot to recovery
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Flash crDroid zip
Flash recovery from the download link
Reboot to system
Update installation:
<!-- change according to your needs -->
Boot to recovery
Flash a zip with crDroid
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm710
Download:
ROM https://crdroid.net/sirius>
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/12.0/changelog_sirius.txt
Known issues:
[*]None
Visit official website @ crDroid.net
crDroid sirius Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Click to expand...
Click to collapse
Dear, I flashed the rom 3 times and followed the instructions, but I get loopboot + no rom + no recovery + no bootloader, meaning dead device. The from edl flash China Rom.
Do I have to be in certain FW? Or do I have to flash something before I start the process for this ROM??
yamabokra01 said:
Dear, I flashed the rom 3 times and followed the instructions, but I get loopboot + no rom + no recovery + no bootloader, meaning dead device. The from edl flash China Rom.
Do I have to be in certain FW? Or do I have to flash something before I start the process for this ROM??
Click to expand...
Click to collapse
I don't encouter anything special except I can't boot back to recovery after boot into this ROM
I flash FW from sirius_images_V12.5.1.0.QEBCNXM_20210625.0000.00_10.0_cn_0969fb8c9f.tgz (which is the latest stable stock ROM)
And use twrp-3.6.1_9-0-xmsirius.img (which is the latest official twrp from https://twrp.me/) to install crDroidAndroid-12.0-20220226-sirius-v8.2.zip
NexusRunner said:
I don't encouter anything special except I can't boot back to recovery after boot into this ROM
I flash FW from sirius_images_V12.5.1.0.QEBCNXM_20210625.0000.00_10.0_cn_0969fb8c9f.tgz (which is the latest stable stock ROM)
And use twrp-3.6.1_9-0-xmsirius.img (which is the latest official twrp from https://twrp.me/) to install crDroidAndroid-12.0-20220226-sirius-v8.2.zip
Click to expand...
Click to collapse
I will try now and report. Thanks bro
NexusRunner said:
I don't encouter anything special except I can't boot back to recovery after boot into this ROM
I flash FW from sirius_images_V12.5.1.0.QEBCNXM_20210625.0000.00_10.0_cn_0969fb8c9f.tgz (which is the latest stable stock ROM)
And use twrp-3.6.1_9-0-xmsirius.img (which is the latest official twrp from https://twrp.me/) to install crDroidAndroid-12.0-20220226-sirius-v8.2.zip
Click to expand...
Click to collapse
Appreciate it bro. at least I update the device and finished my 3 day fighting with this device
Bro this rom is amazing.
I have found a bug.
Double Tap Screen Wake doesn't work after when screen goes sleep about 10+ second later.
Screen doesn't wake up bro.
God bless you.
Edit
When pocket mode is on, it works fine.
Sure you can highly customize settings with this ROM. But experiences are not good enough. One Setting may collapse another; the number in the battery icon is hard to be recognized...It needs a product manager. If mobile phones get more standardized one day, it may be less hard to mantain a unified UI, just like gnome desktop on PCs.
yamabokra01 said:
I payed 30$ and recovered my mobile.
Then i flashed a rom and for the second time i flashed the recovery again and my mobile again dead
Click to expand...
Click to collapse
my problem is same as yours, how to fix it? I am a student currently I am having difficulty. Help me please.
12
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Evolution X 7.1 for the Xiaomi Mi Note 10 Lite [toco]
Keep Evolving
Pixel UI, customization, and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
You tell me
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
- Have the latest Global stable MIUI v13.0.2.0 installed
- Make sure you're running TWRP or OrangeFox for Android 13
- Boot into recovery
- Copy Rom
- Flash Rom
- Format data
- Reboot to system & #KeepEvolving
Update / Dirty Flash
- Boot into recovery
- Flash Rom
- Wipe Dalvik Cache & Cache
- Reboot to system & #KeepEvolving
Download
Donate me! / Official Chat / Device Support​
Android version: 13.0.0_r6
Evolution version: 7.1
Security patch level: September 2022
Build Author: AndroidHQ254
ROM Source: [URL]https://github.com/Evolution-X[/URL]
Kernel Source:: VantomKernel
ROM Developer: Joeyhuab
XDA:DevDB Information
Evolution X, ROM for the Xiaomi Mi Note 10 Lite
Contributors
AndroidHQ254, @NeoArian
Source Code: https://github.com/Evolution-X
ROM OS Version: Android 13
ROM Kernel: Linux 4.14.292
ROM Firmware Required: Latest Stable MiUI v13.0.2.0 (Android 12)
Based On: AOSP
Version Information
Status: Stable
Created 2020-09-22
Last Updated 2022-09-22
Dirty flash is available/possible when I'm update from A.12.1 of evoX?
kavillock said:
Dirty flash is available/possible when I'm update from A.12.1 of evoX?
Click to expand...
Click to collapse
NO. This requires a clean flash
i wanted to ask befor i upgrade from omega is it stable and dose it have ay removed features , especially the spoofing for free google photos , i wish to daily this rom and thats why i want to know about the experience
I have evox Snow, but I do not remember the latest installed miui. Is there a way to check it?
i flashed it and it boots but i get a black screen the os is on i belive cause holding the pwoer button makes my phone slightly vibrate so idk whats hapening
Alenett said:
I have evox Snow, but I do not remember the latest installed miui. Is there a way to check it?
Click to expand...
Click to collapse
You need Global MIUI 13.0.2.0 and this is specified in the post
Fox_it3 said:
i wanted to ask befor i upgrade from omega is it stable and dose it have ay removed features , especially the spoofing for free google photos , i wish to daily this rom and thats why i want to know about the experience
Click to expand...
Click to collapse
It would not be shared here if it were not stable
Fox_it3 said:
i flashed it and it boots but i get a black screen the os is on i belive cause holding the pwoer button makes my phone slightly vibrate so idk whats hapening
Click to expand...
Click to collapse
Ensure you perform a proper clean flash on the right base and make sure you are formatting data using the specified TWRP or OrangeFox for Android 13
AndroidHQ254 said:
Ensure you perform a proper clean flash on the right base and make sure you are formatting data using the specified TWRP or OrangeFox for Android 13
Click to expand...
Click to collapse
I've installed the orange fox for Android 13 roms and had a bug that caused the data partition not being able to mount and it wouldn't flash any rom so i had to downgrade , but ill try it again in the near future, so i need to update my orange fox then clean install the android 13 rom
Fox_it3 said:
I've installed the orange fox for Android 13 roms and had a bug that caused the data partition not being able to mount and it wouldn't flash any rom so i had to downgrade , but ill try it again in the near future, so i need to update my orange fox then clean install the android 13 rom
Click to expand...
Click to collapse
If you are on Android 13, you should not have any mounting issues unless you have something messed up. Keep in mind that the recoveries are tested extensively before posting
I am on Android 12 as for this moment, i have the Evo x 6.5 omega.
AndroidHQ254 said:
You need Global MIUI 13.0.2.0 and this is specified in the post
Click to expand...
Click to collapse
I know that, but it is not the question i did. Simply i can avoid to reflash the original MIUI if i know the version i have already installed previously. Anyway i reflashed the original firmware before installing evox 7.1 to be sure.
Fox_it3 said:
I am on Android 12 as for this moment, i have the Evo x 6.5 omega.
Click to expand...
Click to collapse
There is a separate recovery for each Android version. So I don't understand why you are using an OrangeFox for Android 13 on Android 12. Stick to the specifications and follow instructions
Alenett said:
I know that, but it is not the question i did. Simply i can avoid to reflash the original MIUI if i know the version i have already installed previously. Anyway i reflashed the original firmware before installing evox 7.1 to be sure.
Click to expand...
Click to collapse
Just flash the latest firmware if you are not sure what you have. You don't need to flash the entire MIUI 13.0.2.0 stock rom
AndroidHQ254 said:
Just flash the latest firmware if you are not sure what you have. You don't need to flash the entire MIUI 13.0.2.0 stock rom
Click to expand...
Click to collapse
It is what i did.
Alenett said:
It is what i did.
Click to expand...
Click to collapse
All working great I hope
Fox_it3 said:
I am on Android 12 as for this moment, i have the Evo x 6.5 omega.
Click to expand...
Click to collapse
- Install latest TWRP you can find in the other thread (using fastboot).
- Flash the lastest MIUI via adb sideload and perform a format data (backup your data before this).
- Reboot to system and let the MIUI to run.
- When the MIUI is ready (on the welcome page), reboot the phone in fastboot.
Then:
- Flash the TWRP again via fastboot (the MIUI restore the standard boot).
- Reboot in recovery mode (TWRP).
- Flash the new evox via adb sideload
- Format data
Reboot to system.
There is nothing else to do or explain. It must works.
Evox 7.1 works a lot better then 6.5. I have a good improvement in performance and battery life.
If you want to root when you have configured the phone and it is ready to be used:
- install root explorer from google play store
- download and install magisk app downloading the apk from github and installing it by root explorer (i recommend to not allow the browser to install apks).
- on the pc, extract the boot.img from the evox zip.
- attach the phone to the pc and transfer the boot.img to the phone.
- run magisk and patch the boot.img
- transfer the patched image to the pc
- reboot the phone in fastboot
- flash the patched boot.img via fastboot
- reboot to system
Enjoy!
Alenett said:
- Install latest TWRP you can find in the other thread (using fastboot).
- Flash the lastest MIUI via adb sideload and perform a format data (backup your data before this).
- Reboot to system and let the MIUI to run.
- When the MIUI is ready (on the welcome page), reboot the phone in fastboot.
Then:
- Flash the TWRP again via fastboot (the MIUI restore the standard boot).
- Reboot in recovery mode (TWRP).
- Flash the new evox via adb sideload
- Format data
Reboot to system.
There is nothing else to do or explain. It must works.
Evox 7.1 works a lot better then 6.5. I have a good improvement in performance and battery life.
If you want to root when you have configured the phone and it is ready to be used:
- install root explorer from google play store
- download and install magisk app downloading the apk from github and installing it by root explorer (i recommend to not allow the browser to install apks).
- on the pc, extract the boot.img from the evox zip.
- attach the phone to the pc and transfer the boot.img to the phone.
- run magisk and patch the boot.img
- transfer the patched image to the pc
- reboot the phone in fastboot
- flash the patched boot.img via fastboot
- reboot to system
Enjoy!
Click to expand...
Click to collapse
Thanks i must have missed this for sure , im pretty basic at this custom rom stuff thanks a lot
Double tap to wake does not work after ~5 seconds after screen off (after the always on display dims down)
* Might be related to a broken screen replacement.
* I DID verify that the problem is a software problem - flashed xiaomi.eu rom and it DOES work there.
* I'm NOT at all sure it worked even with original screen (screen was fully functional, just a few cracks in the glass)
Update:
Tried derpfest and project elixir, same problem.
also found this on pixel-experience github issue tracker...
exactly the same issue - AOD becomes too dim and tap to wake stops working.
seems it's a known problem.