(TL;DR available)
I have a Zenfone 2 (Z00A) and I used to have LineageOS (Android N 7.1) installed, however after some time I noticed the SIM Card wasn't getting detected anymore. At first I tought it was Lineage, so I updated it to the latest experimental, still, nothing. Then I decided to test the SIM in another phone with the same version of Lineage, with my old Zenfone 5, and the SIM still worked. So I reset my Zenfone 2 back to stock ROM, stock Bootloader, stock everything, and the SIM worked. Still thinking it was Lineage, I installed Ressurection Remix, which also requires the MM Bootloader, and the SIM didn't work once again.
*** TL;DR ***
I believe the MM Bootloader is causing the phone to not read the SIM card. It only happens with this provider, since other providers' cards are still recognized. It's very weird. Any help is fairly appreciated.
(This is my first thread and english is not my primary language so sorry for any mistakes.)
1) Which stock ROM does it work with , surely its MM bootloader ?
2) Which TWRP did you have installed.
3) Depending on Which TWRP you do have and what stock ROM (answers from 1&2 above) , you back up stock rom which works , back up in TWRP and simply restore it, a two minute job .
Depending on all answers above...
Try slim7 ROM till linos is fixed . RR is based on linos.
Latest linos does take approx 5 mins to register sim after reboot, don't touch device , leave screen / display setting to half hour and watch it connect without touching the phone.
This question should be answered in thread of ROM development you had trouble with , reading related threads is also wise .
https://forum.xda-developers.com/showpost.php?p=71270877&postcount=25
timbernot said:
1) Which stock ROM does it work with , surely its MM bootloader ?
2) Which TWRP did you have installed.
3) Depending on Which TWRP you do have and what stock ROM (answers from 1&2 above) , you back up stock rom which works , back up in TWRP and simply restore it, a two minute job .
Depending on all answers above...
Try slim7 ROM till linos is fixed . RR is based on linos.
Latest linos does take approx 5 mins to register sim after reboot, don't touch device , leave screen / display setting to half hour and watch it connect without touching the phone.
This question should be answered in thread of ROM development you had trouble with , reading related threads is also wise .
https://forum.xda-developers.com/showpost.php?p=71270877&postcount=25
Click to expand...
Click to collapse
1) I am currently running SuperZen which is based on Android L, works fine.
2) 3.0.2 and I tried with older 2.x.x versions too, no success.
3) Can you specify a little more? A bit confused with what you mean.
I will try LineageOS once again, and shall also try Slim7.
I posted this here since I didn't, and still don't, beleive this has to do with the ROM, but with the Bootloader itself.
I read a lot of threads, including the one you sent me, tried everything without success.
Thank you for now!
kronkraken said:
1) I am currently running SuperZen which is based on Android L, works fine.
2) 3.0.2 and I tried with older 2.x.x versions too, no success.
3) Can you specify a little more? A bit confused with what you mean.
I will try LineageOS once again, and shall also try Slim7.
I posted this here since I didn't, and still don't, beleive this has to do with the ROM, but with the Bootloader itself.
I read a lot of threads, including the one you sent me, tried everything without success.
Thank you for now!
Click to expand...
Click to collapse
Backed up, completely wiped, installed MM Bootloader and flashed Slim7. No SIM. Set Sleep Timer to 30 minutes, rebooted, unlocked screen and left the phone for 10 minutes. No SIM. Did it again but this time didn't even unlock the phone, no SIM. Completely wiped and flashed LineageOS, same process, no SIM. Even went further and tried CM13 (Android M), same process and still no SIM. At this point I am 99.9% sure it is the MM Bootloader that is causing the issue, because as soon as I fallback to the L Bootloader and flash any L ROM, like Stock ASUS or Super ZEN the SIM works fine.
Try stock M , there's been about 6 stock updates in stock M
timbernot said:
Try stock M , there's been about 6 stock updates in stock M
Click to expand...
Click to collapse
Not sure where I can find Stock M, but I found an update on ASUS' Website, Firmware version UL-4.21.40.144 that is Brazil specific, wonder if it has something to do with the SIM not working.
kronkraken said:
Not sure where I can find Stock M, but I found an update on ASUS' Website, Firmware version UL-4.21.40.144 that is Brazil specific, wonder if it has something to do with the SIM not working.
Click to expand...
Click to collapse
are you from Brazil ?
It shouldn't by rights , yes there was probs with Brazilians receiving signal but jrior dev , incorporated those fixes for Brazilians into CM which should be carried through lineageOS.
I don't have anytime right now but will help you update.
Watch you don't brick doing anything daft.
:crying::crying:
timbernot said:
are you from Brazil ?
It shouldn't by rights , yes there was probs with Brazilians receiving signal but jrior dev , incorporated those fixes for Brazilians into CM which should be carried through lineageOS.
I don't have anytime right now but will help you update.
Watch you don't brick doing anything daft.
:crying::crying:
Click to expand...
Click to collapse
Okay, for now I will just restore my backup! Thanks!
kronkraken said:
Okay, for now I will just restore my backup! Thanks!
Click to expand...
Click to collapse
I was able to get the Official MM Bootloader installed, and SIM works fine. Not being able to install any MM-based ROMs tho, they all give Error 7: "This package supports Ifwi Versions: %2; 0094.0183;this device has Ifwi version ."
Hi guys,
I have been having issues with my Australian Moto Z PLay. I have been Romming for a while now and tried to first return the phone to stock using the adb method. Which didnt work (I cant remember why, I think I finished it all and it would only boot to bootloader or recovery). Then tried updating only the modem using this method https://forum.xda-developers.com/moto-z-play/how-to/update-bootloader-modem-to-flash-stock-t3818253 then I tried flashing a few ROM's
The issue now is that the phone turns itself off and on a few times a day. I have launcher crashed quite often and the battery seems to have less life in it.
In short I'm not too sure what I have done wrong. Maybe a few things. Can anyone help me get back to a point where I can install custom ROM's like before relatively safely and reliably? I have tried a few different rom's and had lots of similar issues with each.
ROM - AOSP Extended v5.8 Official
Android - 8.1.0
Baseband version - M8953_10238.63.04.83.01R
Kernel Ver - 3.18.71-OPN28.49-2-g04699f27af49
SELinux Permissive
Hardware - Moto Z Play purchase in Australia retail from Harvery Norman
Boot messages
"There's an internal problem with your device. Contact manufacturer for details" (appears twice, once before needing password, once after. Never needed pin code before)
Thakn you in advance!
....also lots of lag. I'm going someone can guide me to the modem etc settings that should be in my device
Hey guys I recently flashed stock ZUI 3.5 to get to the new baseband. Then I flashed AEX 6.2 and was using a root explorer to chance the U-touch options. After making some changes and rebooting the "fpc1020tp.kl" file, was not there in the folder anymore. I tried clean flashing again but the problem still persisted for some reason, tried multiple roms, still doesn't show up. Please help.
Even after flashing with QFIL and back to AEX the files still cannot be seen.
wantei said:
Hey guys I recently flashed stock ZUI 3.5 to get to the new baseband. Then I flashed AEX 6.2 and was using a root explorer to chance the U-touch options. After making some changes and rebooting the "fpc1020tp.kl" file, was not there in the folder anymore. I tried clean flashing again but the problem still persisted for some reason, tried multiple roms, still doesn't show up. Please help.
Even after flashing with QFIL and back to AEX the files still cannot be seen.
Click to expand...
Click to collapse
Which zui you flash Indian or Chinese.
Haider** said:
Which zui you flash Indian or Chinese.
Click to expand...
Click to collapse
Chinese. I managed to find it in system/vvendor/usr/keylayout.
Now my problem is, my phone only detects 16GB of storage instead of 64GB. I need help.
So i have come across a strange problem.
I was using AEX 6.6 on my z2 for almost 15 days now and wanted to switch to AOSIP , so i boot in twrp try flashing and get ERROR 7 (very strange , because i had flashed that before) , so i try to revert back to AEX and still get ERROR 7 (it says failed to flash system img or something like that), ended up QFILing ZUI 2.5.
After booting that up the IMEI was missing and sim card was not detected (thought maybe that was the reason for ERROR7 , but turns out it wasn't) ,so i look around threads and finally fix it .
Now IMEI is back and sim cards working as expected , so i flash TWRP and still end up with ERROR 7 , so QPST again ,this time ZUI 3.5 , repeatedthe same process again and still ERROR 7.
Tried downloading zui again and trying everything again , still ERROR 7 .
Tried old TWRPs and Nougat and still the same thing .
I am not sure what's causing it because ZUI is working totally fine.
Tried experimenting with several roms , v2f and f2v , still the same .
Tried flashing zui 1.9 , all the way to zui 3.5.
Tried unlocking bootloader on all zui versions and trying flashing Roms.
Still the same Error 7 .
Anyone has any idea what the hell is wrong with my device ?
I don't understand how zui works totally fine ,if it is somehow a hardware problem .
BTW i have taken my device apart several times , but i don't think that's the cause .
All help would be really appreciated
Most probably vender to factory or vice versa error. It happens when you flash different treble/non treble custom roms. I see you tried most of the stuff butt I was stuck having exactly same error for a week and through hit and trial i somehow fixed it, happened a while back almost a year ago.
Use all in one tool on pc, go to edl mode format everything. EVERYTHING! don't relock, instead reflash twrp by Kuber it's hosted on android file host than reboot and set up twrp settings and reboot again format cache and data etc (since there is no os) it should have no problems. If there are no errors. You are good to go.
Hey all
I recived the miui 12.5 enchanced [ALIOTHEEAGlobal_V12.5.3.0.RKHEUXM] (2.9 GB & 466 MB) Update a few days ago via ota. My rom is stock - no root or custom Recovery. The download and installing process work fine, but then the Phone need to restart. While restarting the Phone stuck at poco Logo. Only with a few reboots (or leave it alone for a long time) the Phone comes alive again. Then there is the Info miui update failed after reboot. I also tried to Update manually the Full and increment Rom over the three dots menue. No Chance. Even if i install my current rom version [ALIOTHEEAGlobal_V12.5.3.0.RKHEUXM] again - the same problem
I searched the whole Internet and couldn't find someone with the same problem.
Please help.. Thank yo all!
FYI: I cannot do a full reset / wipe with data loss, because i have so much banking apps and accounts. I need a full day of restoring my current status and i don't have the time at the moment.
No one?
Hmm... I don't know if it possible with locked BL but try boot from B partitions? Are they for cases like this one, aren't they?
I dont know this option. How will this work?
I backed up my phone as good as possible und tried to flash with "XiaoMitTool V2" my currend rom and the 12.5.6.0 and it always endet in "miui sideload failed". WTF is here going wrong .. While sideloading it stops at 4.99% on phone screen.
Have you tried with 12.5.6 via stock recovery? (full rom ofc, not OTA). It doesn't erase your data.
I also tried ToolV2 with my F3 and no luck too.
isnt 12.5.6 eea enchanced? 12.5.3 is older update in eu
I tried to update through stock recovery and MIAssistant but no success. Like @crysus said, it stops to 4,99 on phone screen, no error but it boots to the old ROM. Maybe because is a stable beta version.
Mine updade went all good without hassles. I updated it via stock recovery but first I use 3 dots menu in system updater app just to show where update file is. (full recovery fw used, not just OTA).
The fastboot version of 12.5.6_EEA has been available for a few days now, it can be Flash with miflash.
Here the link:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com