Hello! I bought Chinese version of the note 7 with 6gb of RAM and 64gb of storage and unlocked my bootloader and flashed xiaomi eu miui ROM after that and rooted with magisk 19 and everything was working,but then I decided to try some gsi roms and didn't like them so much so decided to flash the latest xiaomi eu ROM again version 9.4.11 which I am on right now,since then the fingerprint section has been dissappeared and even if I set up screen pattern it won't accept it after I have drawn it the right way and also in twrp I can't seem to mount the vendor partition.I have a full backup made with everything working before I decided to play around with gsi roms,but it won't mount the vendor partition in twrp so right now I don't have any screen lock because if I set up the pattern lock it won't accept it after I have set it up anyone knows how to fix it or why my fingerprint has dissappeared?
I had this issue too while messing with GSI roms. I'm not sure what solved the issue, but my fingerprint returned after several clean flashs switching between miui.eu and PHH AOSP GSI
Okay.Sorry for the late reply,been busy,but ya it looks like clean flashing solves the problem,so anyone having the same problem as we did just clean flash the original firmware either thru miflash (didn´t use that personally) or by flash_all.bat which comes with the firmware zipped,in my case it was the chinese variant and I downloaded it from https://androidmtk.com/download-xiaomi-stock-rom-for-all-models that page.
Dice1212 said:
Okay.Sorry for the late reply,been busy,but ya it looks like clean flashing solves the problem,so anyone having the same problem as we did just clean flash the original firmware either thru miflash (didn´t use that personally) or by flash_all.bat which comes with the firmware zipped,in my case it was the chinese variant and I downloaded it from https://androidmtk.com/download-xiaomi-stock-rom-for-all-models that page.
Click to expand...
Click to collapse
The link you gave is for chinese stock rom? And this won't relock the bootloader?
Yes it's the stock chinese one and it won't relock the bootloader If you ise the flash_all.bat file included in the zip
Related
This is for people who have received their phone with a pre-installed Vendor ROM (MIUI Global Stable 8.0.8.0) and wants to switch to the Unofficial EU ROM. In my opinion, the EU ROM is currently the best ROM without any Chinese bloatware or popups until Xiaomi decides to release an actual Global ROM.
For those who are already on a China Stable ROM, there is already an excellent guide to install TWRP, ROOT, compiled by @underlines. This is only intended for switching from a Vendor ROM as I wasn't able to switch from a Vendor ROM to an official build using the previous guide. You need to be on an official build to be able to use TWRP and flash the EU ROM.
EDIT : The reason why I have mentioned to flash an official build at first is because, TWRP can be unresponsive with some Vendor ROMS. You'll be able to boot TWRP but touch would be frozen. I've tried with both versions of TWRP and it wouldn't work with the Vendor ROM installed on my device. TWRP over the Vendor ROM may work for some users.. For some builds like the one which came installed on my phone, it may not work. If TWRP works for you without being on an official build, you can skip the part where you have to flash an official ROM.
1. You need to have an unlocked bootloader. Please follow instructions on the other guide on how to do this.
2. You need the older version of MiFlash found on this link. Thanks to @Thorin78 for this link.
3. Download and extract fastboot Stable or Dev ROM and extract ROM folder to the C:\ Drive. This is because MiFlash may show a "cannot find file" error if you have a lot of subfolders. To avoid this, its best if the folder is C:\ROM Folder.
4.In the older version of MiFlash, click advanced and change the fastboot script location to the flash_all.bat in your unzipped rom folder.
5.Connect your phone in fastboot mode, click "Refresh" in MiFlash. Once your phone is detected, click "Flash" and it should now successfully flash the official ROM of your choice.
If you wish to be on a Xiaomi Official Stable or Dev ROM, Stop here! If you wish to continue installing the EU ROM proceed with the steps below.
6. Now that you have successfully flashed Official Stable or Dev ROM, use Minimal ADB and flash TWRP RC2 using the instructions in the other guide.
7. Once you are in TWRP, Swipe right to allow System Modifications and copy the forced encryption disabler using MTP. Flash this file to ensure that there are no bootloops.
8. After this step, go to WIPE, Format Storage, type "yes" and then Reboot Recovery. Copy SuperSU and EU ROM to storage and flash. Phone may take a few minutes to boot up and you will successfully boot the EU ROM.
For everything else, please follow the guide posted by underlines.
TWRP EU RC2 works with the China Dev ROM as well. Once you Swipe to Right to allow modifications, don't forget to flash the latest dm-verity and forced encryption disabler script from here. This is to prevent the device going into a bootloop.
These are the steps I followed and I am on EU ROM. Hope this helps people who wish to switch to the EU ROM from the Vendor ROM.
The link to miflash takes you DL minimal adb?
jazz452 said:
The link to miflash takes you DL minimal adb?
Click to expand...
Click to collapse
Corrected. Thanks for letting me know! Cheers!
satishp said:
Corrected. Thanks for letting me know! Cheers!
Click to expand...
Click to collapse
I managed to flash with latest miflash using your guide my bootloader was already unlocked check using:
boot your phone into fastboot and COMMAND PROMPT " fastboot oem device-info "
most are probably unlocked with vendor rom but not all.
Don't try to unlock with this method just check to save sometime.
guide: http://xiaomitips.com/guide/how-to-check-if-redmi-note-3-bootloader-is-locked-or-unlocked/
jazz452 said:
I managed to flash with latest miflash using your guide my bootloader was already unlocked check using:
boot your phone into fastboot and COMMAND PROMPT " fastboot oem device-info "
most are probably unlocked with vendor rom but not all.
Don't try to unlock with this method just check to save sometime.
guide: http://xiaomitips.com/guide/how-to-check-if-redmi-note-3-bootloader-is-locked-or-unlocked/
Click to expand...
Click to collapse
I guess it also depends on the Vendor ROM and customization which comes installed on your device. Not all Vendor ROMs for this device are the same. I tried everything under the sun with the latest miflash. It would detect device and even give a "success" output but the ROM was never actually flashed. The phone would still be on the Vendor ROM. Its as if some Vendor ROMs have some form of write protection baked in.
I could only get it working with the older miflash.
I'm not saying it was easy, the hard thing was making the unpack ING of the file. Sort of did it twice never had that problem before.
Why is it required to flash the official rom before flashing the EU rom?
nkatz565 said:
Why is it required to flash the official rom before flashing the EU rom?
Click to expand...
Click to collapse
This for people who don't want TWRP, root and dm-verify, just genuine Xiaomi rom with OTA updates and remove vendor rom.
QQ.
I did the following on my Mix and wondering if I am missing anything. I should say that everything "appears" to be working perfectly on the EU rom.
My Mix came with 8.0.8.0 Global (Vendor ROM) and I wanted to move onto the Xiaomi.eu rom. I loosely followed the above guide and did the following steps:
Applied for Unlock
Unlocked the device via MiUnlock
Used Minimal ADB and booted the device into FastBoot
Confirmed device was Bootloader unlocked
Flashed TWRP (latest non-eu build)
Booted to recovery
DID NOT swipe to edit system partition, left that read only
Flashed the latest Weekly Xiaomi.eu build
Wiped Dalvik/Cache
Booted phone
Performed a Factory reset.
All seemed a little too easy and I didnt need to go to an "Official" china ROM first. But I do have a few questions...
Should I have swiped Yes to enter Read/Write mode for the system partition and run a dm-verify? (I am not interested in Rooting the device at this stage)
Should I have performed a System clear in TWRP before installing Xiaomi.eu ontop of the Vendor ROM?
geubes said:
QQ.
I did the following on my Mix and wondering if I am missing anything. I should say that everything "appears" to be working perfectly on the EU rom.
My Mix came with 8.0.8.0 Global (Vendor ROM) and I wanted to move onto the Xiaomi.eu rom. I loosely followed the above guide and did the following steps:
Applied for Unlock
Unlocked the device via MiUnlock
Used Minimal ADB and booted the device into FastBoot
Confirmed device was Bootloader unlocked
Flashed TWRP (latest non-eu build)
Booted to recovery
DID NOT swipe to edit system partition, left that read only
Flashed the latest Weekly Xiaomi.eu build
Wiped Dalvik/Cache
Booted phone
Performed a Factory reset.
All seemed a little too easy and I didnt need to go to an "Official" china ROM first. But I do have a few questions...
Should I have swiped Yes to enter Read/Write mode for the system partition and run a dm-verify? (I am not interested in Rooting the device at this stage)
Should I have performed a System clear in TWRP before installing Xiaomi.eu ontop of the Vendor ROM?
Click to expand...
Click to collapse
Wouldn't worry about it the vendor ROMs aren't poison, not sure about dm-verify if you kept read only. I would of swiped then flashed dm-verify but didn't mean I know what I'm doing.
nkatz565 said:
Why is it required to flash the official rom before flashing the EU rom?
Click to expand...
Click to collapse
This is because some Vendor ROMS have some compatibility issues with TWRP. Touch screen wouldn't work on TWRP. I tried both TWRP versions and couldn't get touch to work.
Finally, I flashed the China Dev ROM and then used TWRP RC2 and touch functionality worked.
As some users below have pointed out that they could get to EU without flashing the one of the official builds, I guess it depends on the amount or type of vendor customizations applied on your device.
Which version do you own? I was wondering if this would work with the 6GB as well.
dbesada said:
Which version do you own? I was wondering if this would work with the 6GB as well.
Click to expand...
Click to collapse
This works with both versions. The ROM is compatible with both variants as the size of memory and storage doesn't affect compatibility.
I have the 6\256 variant.
satishp said:
This works with both versions. The ROM is compatible with both variants as the size of memory and storage doesn't affect compatibility.
I have the 6\256 variant.
Click to expand...
Click to collapse
Thank you. It worked. I fastboot twrp then factory reset the device and flashed the eu rom. All good. My bootloader was unlocked by the vendor.
Can someone please give me some advice? Just got the phone a couple hours ago. I took a picture of the info page. Based on the screenshot am I on the vendor ROM or official? I'm thinking I'm on Vendor because it has GAPPS already included.
If I'm on Vendor ROM and want to get to rooted EU Rom I can follow directions in the OP right?
How do I know is if my bootloader is already unlocked? Many thanks
SantinoInc said:
Can someone please give me some advice? Just got the phone a couple hours ago. I took a picture of the info page. Based on the screenshot am I on the vendor ROM or official? I'm thinking I'm on Vendor because it has GAPPS already included.
If I'm on Vendor ROM and want to get to rooted EU Rom I can follow directions in the OP right?
How do I know is if my bootloader is already unlocked? Many thanks
Click to expand...
Click to collapse
Vendor (there is no Global ROM for Mix). You should unlock your bootloader (check if it's already unlocked using "fastboot oem device-info"), flash TWRP, wipe and flash EU
Razorbacktrack5535 said:
Vendor (there is no Global ROM for Mix). You should unlock your bootloader (check if it's already unlocked using "fastboot oem device-info"), flash TWRP, wipe and flash EU
Click to expand...
Click to collapse
Do I have to do Power + Vol Down (that's bootloader mode right) in order to input the ADB code you gave me?
SantinoInc said:
Do I have to do Power + Vol Down (that's bootloader mode right) in order to input the ADB code you gave me?
Click to expand...
Click to collapse
Yes, you have to use Fastboot Mode
Razorbacktrack5535 said:
Yes, you have to use Fastboot Mode
Click to expand...
Click to collapse
I'm not unlocked right? Hope they approve my unlock request soon
SantinoInc said:
I'm not unlocked right? Hope they approve my unlock request soon
Click to expand...
Click to collapse
Yes, you have to wait
Hi everyone,
I have a little problem with fingerprint with these 2 roms.
Normally I could add 5 fingers but I can only 3 max. If I try to configure the last 2, all my fingerprints dont work at all.
Moreover I can't delete fingeprints. When I try, they come back.
That is an issue which not occur with 6.0 custom roms.
Someone know how to fx it?
Thanks.
I'd suggest flashing the stock nougat 93-11 or 93-14 firmware (e.g. from the guides section) to resolve your fingerprint issues. Once that's done, future installs of lineage and RR should have fingerprint support for more than 3 fingers.
Thanks for replying.
I have xt1642. Is there a stock firmware Nougat for this device? I didnt find it
Nicozyp said:
Thanks for replying.
I have xt1642. Is there a stock firmware Nougat for this device? I didnt find it
Click to expand...
Click to collapse
I've got an XT1642 (UK - retGB, EMEA baseband) and updated to Nougat 93-11 using the stock files on here okay (now running Lineage with 4 FPs set).
The ROM I used to upgrade was the one linked here: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-install-official-december-nougat-t3518262 This will bring you up to the official 93-11 update via installing from stock recovery - you need Marshmallow build 139-63/64 however.
However, you may like to try either of these guides as well: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
As long as you can successfully install a Nougat stock ROM onto your device, the updates should mean your fingerprint sensor works properly in the custom ROMs. Bear in mind that updating to Nougat may wipe your data and cause you to lose TWRP/root until you re-install them.
Last question: can I wipe system and internal storage before installing ressurection?
Nicozyp said:
Last question: can I wipe system and internal storage before installing ressurection?
Click to expand...
Click to collapse
Once you've installed Nougat (and I recommend installing TWRP too), if you wish to install Resurrection Remix, only wipe system, data, Dalvik and cache. Don't wipe internal storage, since that's where your ROM zip is stored!
Silesh's initial post on the RR version for Moto G4s has more information on this https://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-n-5-8-0-t3507275
Unable to flash stock recovery => "image not signed or corrupt"
Nicozyp said:
Unable to flash stock recovery => "image not signed or corrupt"
Click to expand...
Click to collapse
The image is flashed. Boot into recovery and you'll realize.
Nicozyp said:
Unable to flash stock recovery => "image not signed or corrupt"
Click to expand...
Click to collapse
Which file are you flashing? Does it end in OKAY after that error?
EDIT - zeomal is too quick for me
Indeed it's ok.
For the moment I upgrade MM, then gonna flash stock Nougat.
So problem solved.
I've flashed RR and configured fingerprint ==> it works fine
Thanks for ur help and advices
fingerprint option is not displayed in my zuk z1
Hey I have installed official lineage-os on my zuk z1 handset but still I can't find fingerprint option in my zuk
What to do help me
I explain my situation:
I was on fulmics 4.2 and everything ok.
Tried a flash oreo without format /data
Bootllop
Ok clean install
Still bottloop
Cleaned everything, installed fulmics + ota
Now all ok except the fingerprint, it is like it does not exist, no option in settings at all.
Does someone have a solution without flashing back a kdz?
Maybe a flashable fingerprint driver?
Same problem
siggey said:
I explain my situation:
I was on fulmics 4.2 and everything ok.
Tried a flash oreo without format /data
Bootllop
Ok clean install
Still bottloop
Cleaned everything, installed fulmics + ota
Now all ok except the fingerprint, it is like it does not exist, no option in settings at all.
Does someone have a solution without flashing back a kdz?
Maybe a flashable fingerprint driver?
Click to expand...
Click to collapse
Same problem with fingerprint with stock version after update.
I solved fkashing stock oreo zip after a full wipe + data.
siggey said:
I explain my situation:
I was on fulmics 4.2 and everything ok.
Tried a flash oreo without format /data
Bootllop
Ok clean install
Still bottloop
Cleaned everything, installed fulmics + ota
Now all ok except the fingerprint, it is like it does not exist, no option in settings at all.
Does someone have a solution without flashing back a kdz?
Maybe a flashable fingerprint driver?
Click to expand...
Click to collapse
with the oreo update there were also update files for the bootloader, you have to flash official nougat to recover the old version of the bootloader because the new bootloader is not compatible with nougat and created problems like the unrecognized fingerprint reader
Mindy07du44 said:
with the oreo update there were also update files for the bootloader, you have to flash official nougat to recover the old version of the bootloader because the new bootloader is not compatible with nougat and created problems like the unrecognized fingerprint reader
Click to expand...
Click to collapse
I have the same problem with lineage 15.1. Flashed Oreo zip to test and now my fingerprint is gone in Lineage. Do you mean flash Nougat kdz to recover old version of the bootloader? or just a nougat zip?
Flashing a Nougat Zip (Open EU)worked for me. No need to flash kdz.
schoeni11 said:
I have the same problem with lineage 15.1. Flashed Oreo zip to test and now my fingerprint is gone in Lineage. Do you mean flash Nougat kdz to recover old version of the bootloader? or just a nougat zip?
Flashing a Nougat Zip (Open EU)worked for me. No need to flash kdz.
Click to expand...
Click to collapse
yes the kdz or otherwise with the zip is possible but check if the files for the bootloader and in the zip
schoeni11 said:
I have the same problem with lineage 15.1. Flashed Oreo zip to test and now my fingerprint is gone in Lineage. Do you mean flash Nougat kdz to recover old version of the bootloader? or just a nougat zip?
Flashing a Nougat Zip (Open EU)worked for me. No need to flash kdz.
Click to expand...
Click to collapse
When you reinstalled lineage did you wipe anything?
Gobrel said:
When you reinstalled lineage did you wipe anything?
Click to expand...
Click to collapse
did a restore of my nandroid backup.
Please explain step by step
So last year i started learning a bit about roms as stuff like that so after searching i saw Fulmics Rom and i chose that one to flash on my device. On that day i was on Oreo. I did all the stuff (format data, wipe...) then flashed the Rom and it was ok But the fingerprint option was there sometimes and sometimes not... After a day or so it expired so i flashed again (after formatting etc) but no fingerprint. So i just gave up, i was happy that i didnt brick my phone so i just accepted it...But today it's kind of annoying i searched a lot and everyone talks about flashing stock Nougat and then the Rom or flash stock Oreo and then Nougat and then the Rom... Well i tried but with no success.
I hope someone can help me with that
Thank you
Device: ZB602KL 4gb
I was using the latest Liquid Remix 10.0.6 with the stock darkonah kernel for a wee after having just updated from LR 10.0.5 and Singh 2.7. When I noticed he released a stable update for his kernel to 2.8 I downloaded it and flashed it as normal. Upon booting into LR, the lockscreen no longer responded to my fingerprint. It wasn't even turning the screen on. After inputting my password, I noticed that my wifi wouldn't turn on. And later when I tried the stock gcam, it kept crashing. Cam2API Probe is completely blank.
Things I've done to try and fix this:
1. Rebooted multiple times.
2. Someone suggested wiping /system and /vendor only and dirty flashing the rom. Did that, dirty flashed LR, openGApps(wasn't sure I needed to, did it anyway), and Magisk 19.
3. Clean flashed stock 340, decrypt and magisk19.
4. Flashed fw_only-X00T-WW-16.2017.1902.037.zip. I had previously flashed fwpie050.zip(the one from opendesktop) when updating LR before all this happened.
5. Fully wiped phone including internal storage and flashed the latest HavocOS which I am on right now as I've given up and just need it to work as a phone for the meantime.
Camera seems to be working again on Havoc, though. Fingerprint is still missing from Security settings and WiFi will not turn on.
Any help would be appreciated. Thanks!
I also got bootloop by using magisk 19.0,use magisk 17.1 or 18.1.
How did you clean flash stock 340 ? If it was through TWRP then try fastboot ROM
Tianhe said:
How did you clean flash stock 340 ? If it was through TWRP then try fastboot ROM
Click to expand...
Click to collapse
Yes, through twrp. What are the adb commands to do it through fastboot? I used Avinash's modified stock340 btw.
I think the modem firmware is corrupted somehow. I cannot receive or make calls but can get 4g data connection and SMS. My wifi mac address sometimes is "Uknown" or 02:00:00:00:00:00.
defurious said:
Yes, through twrp. What are the adb commands to do it through fastboot? I used Avinash's modified stock340 btw.
I think the modem firmware is corrupted somehow. I cannot receive or make calls but can get 4g data connection and SMS. My wifi mac address sometimes is "Uknown" or 02:00:00:00:00:00.
Click to expand...
Click to collapse
Flash fastboot stock rom it will fix the issue.
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
Hit thanks if it helped
Flashing stock rom thru adb basically reverts your phone to factory state so everything should be fixed unless somehow your hardware is damaged
farhanshaikh671 said:
Flashing stock rom thru adb basically reverts your phone to factory state so everything should be fixed unless somehow your hardware is damaged
Click to expand...
Click to collapse
Yeah, i understand. I'm just a little confused because the steps in the linked post above are for 334. I don't know how to do it using 340. Should I just follow those steps then after relocking, manually update to 340, and then unlock bootloader again?
Is there any way to flash fastboot rom without relocking bootloader?
To me it seems that i'm having some problems with pie beta firmware. After flashing 339 and then LR 10.0.5 which is the last version before requiring pie beta firmware, everything is working normally again. But as soon as i try to update to 10.0.6 or latest Havoc with pie beta firmware, the wifi and fpsensor stop functioning. But the strange thing is, I was on LR 10.0.6 for a week before flashing Singh 2.8 kernel which then killed my hardware.
Now I'm wondering if I should just wait for official Pie release from Asus.
defurious said:
Yeah, i understand. I'm just a little confused because the steps in the linked post above are for 334. I don't know how to do it using 340. Should I just follow those steps then after relocking, manually update to 340, and then unlock bootloader again?
Is there any way to flash fastboot rom without relocking bootloader?
To me it seems that i'm having some problems with pie beta firmware. After flashing 339 and then LR 10.0.5 which is the last version before requiring pie beta firmware, everything is working normally again. But as soon as i try to update to 10.0.6 or latest Havoc with pie beta firmware, the wifi and fpsensor stop functioning. But the strange thing is, I was on LR 10.0.6 for a week before flashing Singh 2.8 kernel which then killed my hardware.
Now I'm wondering if I should just wait for official Pie release from Asus.
Click to expand...
Click to collapse
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)
And one more thing.
If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)
So flash decrypt.zip for pie on Pie Stock(Beta or Stable).
Tested personally and worked fine.:good:
Hit thanks if it helped,
akhil850 said:
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)
And one more thing.
If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)
So flash decrypt.zip for pie on Pie Stock(Beta or Stable).
Tested personally and worked fine.:good:
Hit thanks if it helped,
Click to expand...
Click to collapse
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?
Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks
defurious said:
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?
Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/as...w-to/decrypt-zip-asus-stock-pie-roms-t3923265
Hit thanks if i helped.
"antirollback" warned by miflash even when using the latest 11.0.4 Global ROM
Hi guys, I have made my decision to back to the stock firmware since Google fortified their detection for unlocked BL mobiles. However, I ran into a very strange situation when attempting to flash the stock ROM using miflash it stops to go further and displays "antirollback check error" under status.
Does anyone what could be the reason causing this?
I have checked the firmware files and redownloaded to confirm it is the latest version, no luck.
EDIT
NVM, I found the answer. It was the location of the miflash folder. It successfully flashed the stock ROM without any problem after putting miflash folder under C drive root directory.
What was your previously ROM? I'm on latest .EU weekly and also considering going back to stock Global.
In case you were on .EU ROM, how the Global ROM is comparing to .EU nowadays?
Now about Miflash, to go back to 100% stock I have to check that "clean and lock" option right? Or is there anything else to do?