Problems with security tab after restore - OnePlus 2 Q&A, Help & Troubleshooting

Recently I made a backup before installing a ROM on my oneplus 2. When I was doing it I selected the Boot, System, Data partitions. Then after I restored it everything was working fine except when I was trying to type in my password(not SIM password) it seemed to just restart the UI, but the strange thing was that the Finger print sensor was working I could unlock it that way. So I tried to go in to security setting after that and that also made my UI restart and just threw me back to the home screen. So my question is what mistake did I make when making the backup and how not to make it again?

Perhaps your persistant-partition (where fingerprint data and other security stuff is stored) is damaged. There's an persistant.img which you can flash in fastboot to restore it somewhere here on the op2 forum which you can find if you search.
Best regards
Peter

pitrus- said:
Perhaps your persistant-partition (where fingerprint data and other security stuff is stored) is damaged. There's an persistant.img which you can flash in fastboot to restore it somewhere here on the op2 forum which you can find if you search.
Best regards
Peter
Click to expand...
Click to collapse
But when I install oxygen OS image it works, it just doesn't work when I restore it from a backup.

winVIP said:
Recently I made a backup before installing a ROM on my oneplus 2. When I was doing it I selected the Boot, System, Data partitions. Then after I restored it everything was working fine except when I was trying to type in my password(not SIM password) it seemed to just restart the UI, but the strange thing was that the Finger print sensor was working I could unlock it that way. So I tried to go in to security setting after that and that also made my UI restart and just threw me back to the home screen. So my question is what mistake did I make when making the backup and how not to make it again?
Click to expand...
Click to collapse
Were you on CM13 and installed the H2OS MM firmware? If so, I ran into a similiar thing. You'll may need to flash the Revert2Lollipop to fix.

unremarked said:
Were you on CM13 and installed the H2OS MM firmware? If so, I ran into a similiar thing. You'll may need to flash the Revert2Lollipop to fix.
Click to expand...
Click to collapse
No, I was making a backup of oxygen OS 2.2.1 before installing Resurrection Remix.

Related

Network Solution grayed out/solved

Hi good fellas, so a week back, I flashed mokee build everything was perfect until I received a WhatsApp message from my friend asking me why the hell am I not picking call when it's ringing. I was like what ? Dude send me screenshot and I got roasted. So I tried finding the root cause and got to know sim selection was grayed out.
Issues were,
1. Not able to select sim selection for calls as nothing happens when you click on the selection area. Data works fine for both Sims, I have not tested with SMS.
2. First sim slot works fine for both incoming and outgoing however on the top it shows the second sim name. For example, in my case I'm using Vodafone (first slot) and Tata DoCoMo, so when I make or get a call to Vodafone, it shows me Tata Docomo.
3. There is no way of making calls from second sim.
What did I do?
1. Downloded NucleaRom latest 1.4.1 did a Clean flash (wipe data, cache, dalvik and system) - Did not work.
2. My saviour in flashing, TWRP backups.
Restored NucleaRom 1.3.5 (which was working fine before) - did not work.
3. Restored NucleaRom MM final version 3.0. did not work.
4. Flashed COS 12.1, Bingo got the selection back ( Damn, it has good battery backup) so used it for couple of days.
7. I couldn't take COS Anymore, so downloded last nightly of cm13, clean flash- success
8. Since I'm so addicted to Nougat I wanted to try my luck, tried lates mokee, NucleaRom, RR, sudamod, Cr Droid but it didn't work in any ROM.
9. Back to COS, clean flash, flashed MM Firmware, then Nougat Roms - did not work.
10. Got some update on Nougat ZUI in its XDA post (thanks to developer), downloded both zip and OTA update,clean flashed. Bingo- selection is back. However ZUI still has force close issues
11. Clean flashed NucleaRom, bingo - selection came back.
Not sure what exactly is the root cause since it persists even after clean flash of other ROMS (which were working before) and also backups. If it happens in one ROM, it happens in most or all the Roms. Even in China based ROM.
So, this is the only solution I found, it worked for me. Let me know if it works or if you have any questions.
Thanks to all the developers of Z1. ?
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
Could be. I had tried with Pico and super. Did not work for me
Sent from my Zuk Z1 using XDA Labs
None of the above two mentioned solutions worked.... can anybody tell me any other way???? i am too disappointed with this problem...
Fahad305 said:
None of the above two mentioned solutions worked.... can anybody tell me any other way???? i am too disappointed with this problem...
Click to expand...
Click to collapse
Is sim selection working on COS, cm13 nightly? What happened when you have flashed zui?
Sent from my Zuk Z1 using XDA Labs
SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
I tried to flash Gapps Stock but it didn't work, Sim selection was still grayed out.
Flashed zui 2.5 Nougat and then clean flashed other Los Nougat ROMs and now Sim selection is working fine.
Thanks for the solution.
SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
I've a same problem haunting me in LOS 14.1, I'll try your solution first...will let you know...
Sent from my ZUK Z1 using Tapatalk
Narasimha12 said:
Is sim selection working on COS, cm13 nightly? What happened when you have flashed zui?
Sent from my Zuk Z1 using XDA Labs
Click to expand...
Click to collapse
my file was corrupt i downloaded it again and bingo. working fine.
thanks
Narasimha12 said:
Hi good fellas, so a week back, I flashed mokee build everything was perfect until I received a WhatsApp message from my friend asking me why the hell am I not picking call when it's ringing. I was like what ? Dude send me screenshot and I got roasted. So I tried finding the root cause and got to know sim selection was grayed out.
Issues were,
1. Not able to select sim selection for calls as nothing happens when you click on the selection area. Data works fine for both Sims, I have not tested with SMS.
2. First sim slot works fine for both incoming and outgoing however on the top it shows the second sim name. For example, in my case I'm using Vodafone (first slot) and Tata DoCoMo, so when I make or get a call to Vodafone, it shows me Tata Docomo.
3. There is no way of making calls from second sim.
What did I do?
1. Downloded NucleaRom latest 1.4.1 did a Clean flash (wipe data, cache, dalvik and system) - Did not work.
2. My saviour in flashing, TWRP backups.
Restored NucleaRom 1.3.5 (which was working fine before) - did not work.
3. Restored NucleaRom MM final version 3.0. did not work.
4. Flashed COS 12.1, Bingo got the selection back ( Damn, it has good battery backup) so used it for couple of days.
7. I couldn't take COS Anymore, so downloded last nightly of cm13, clean flash- success
8. Since I'm so addicted to Nougat I wanted to try my luck, tried lates mokee, NucleaRom, RR, sudamod, Cr Droid but it didn't work in any ROM.
9. Back to COS, clean flash, flashed MM Firmware, then Nougat Roms - did not work.
10. Got some update on Nougat ZUI in its XDA post (thanks to developer), downloded both zip and OTA update,clean flashed. Bingo- selection is back. However ZUI still has force close issues
11. Clean flashed NucleaRom, bingo - selection came back.
Not sure what exactly is the root cause since it persists even after clean flash of other ROMS (which were working before) and also backups. If it happens in one ROM, it happens in most or all the Roms. Even in China based ROM.
So, this is the only solution I found, it worked for me. Let me know if it works or if you have any questions.
Thanks to all the developers of Z1. ?
Click to expand...
Click to collapse
COS 12.1 sim selection was working out of the box.
CM 13 selection was working
LOS 14.1 selection stopped working
Flashed ZUI selection is back
& then clean flashed LOS again selection keeps working
Thanks a lot.
It must be radio baseband issue.
Sent from my ZUK Z1 using Tapatalk
Suggestion
Simply I tried this at my own,
And it worked!
Steps :
1. Install Lineage OS ROM from TWRP. (don't install Gapps)
2. Restart your android.
3. Skip all the startup steps after booting-up.
4. Now go to SIM settings and you see, you are able to select SIM for calls.
5. Select any SIM of your choice.
6. Reboot again into TWRP & install Gapps.
7. Reboot into system.
Now you see, you are able to select any SIM of your choice. :good:
Well...try updating kernel...it worked for me...try radioactive kernel(Radioactive reborn acuicultor) for nougat....here is the process
1)Go to twrp/cwm recovery
2)Perform factory reset and wipe dalvik,data,cache,system
3)first install any nougat rom then install any gapp package for nougat and finally the radioactive reborn kernel for nougat
4)reboot
Bam you are there...should work fine
https://forum.xda-developers.com/zuk-z1/help/network-solution-grayed-solved-t3545218
Can anyone help me in camera issue on nougat....after the clean flash when i open default camera app it works fine in auto mode but when switched to hdr mode then it crashes and says unknown error or cannot connect to camera this error occured in all the nougat rom excpet for los 14.1...Now for los 14.1 camera app works fine for few hours then it lags lije hell touch focus doesnt respond....plzz help
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
happyflyingipis said:
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
Click to expand...
Click to collapse
To access the Recovery you have to press the three buttons at the same time (vol+ / vol- / power).
Enviado desde mi ZUK Z1 mediante Tapatalk
happyflyingipis said:
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
Click to expand...
Click to collapse
Just use "adb reboot recovery" in CMD with USB debugging enabled. Won't have to bother with key combinations. ZUI is installed on system, boot partition, and updates modem partition. Doesn't touch the recovery partition.

Fingerprint hardware not available

Hi,
When I try to register my fingerprint it says continuously fingerprint hardware not available,
Now, I know that my fingerprint sensor is working beacause it was woking ok but I wanted to add more fingerprints to make it more accurate, and when I tried that it kept saying that hardware not... So I deleted all the exisiting fingerprint and now I cant register any.
Did wipe cache partition and tried to clear data from com.ztefingerprints.service but it's greyed out.
I want to avoid factory reset, or clearing the phone data.
Any solution?
Edit: stock b32
Thanks
Which rom, dirty flash the ROM !
Stock b32
I'm with g model on custom rom, just reflash the ROM from sdcard, your data should stay.
Hi, which version are your phone in, A2017 or A2017U? Seems same problem with my phone......Have you tried flash your phone?
A2017U stock b32, not custom rom.
What do mean flash my phone, can I do that with stock rom?
Will it delete all my data?
I hade that problem before I ota update to b32, and still have it..
Thanks for your answer! You can back up your personal data to your phone'account,then try to factory reset.
I am having issues with the fingerprint sensor reading my finger but I was able to add a new finger.
Thank u guys,
I've found a fix!
For some reason "don't keep activities" on developer mode was "on", turn it "off" fixed the issue.
Glad to hear that, good luck!
Thanks for the tip, I had the same problem, but thanks to you it is solved.

Can't pull down quick settings

Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
rzarectha said:
Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
Click to expand...
Click to collapse
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Choose an username... said:
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Click to expand...
Click to collapse
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
rzarectha said:
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
Click to expand...
Click to collapse
Yeah, I just didn't know what you meant. I guess it might be a root app or something. I used Material Notification Shade on stock but it had a couple of problems that i didn't figure out until some time ago (it was pretty obvious though)
And for something physical, have you fitted a screen protector lately? I had one that interfered with pull down.

Fingerprint Scanner Null after Pie ROM Flash - Custom ROM won't fix. Stock Only

Fingerprint Scanner Null after Pie ROM Flash - Custom ROM won't fix. Stock Only
Ok, the story.... Moto G5+ retail, running 8.1 Oreo, Bootloader Unlocked, rooted using Magisk 16.7 and was able to backup my Stock Oreo ROM once rooted, or I'd be dead in the water.
So wanting to stay ahead, I tried my hand at RR v7's Pie version, which, after some troubleshooting, was able to install successfully; but I don't much care for the google bar and other hard-coded "pure android" features. Same thing with Pixel Exp. Not to mention that Pie disallows call recording among a few other things Google decided to stifle its customers with. Deal breaker. So - moving on...or back for that matter.
I proceeded to download RRv6, which is btw running nicely on a 2nd G5+, same GApps, installs perfect except - FingerPrint Reader is not acknowledged. Period. No Security settings, No RR Config to access it, Nada. No matter what ROM I flash outside of the StockROM I backed up, it won't recognize the fp reader upon boot up. Whether I clear Dalvik/Cache, All DATA, do a full Wipe, DATA WIPE, REPAIR, FORMAT, nothing allows me to install RR v6.0 or any other flavor, Oreo or Pie, even while trying a dirty flash over Stock Oreo on this Moto G5+. Tried with several SD Cards, downloading fresh zip files from RR. I even went so far as to image the working G5+, then copy into the 2nd G5's SN folder, and do a restore, just loops - even after repairing the partition. I managed to work around that, Restored the image, but still no FP recognized by the initial Google startup/setup. It's almost as if the phone's been "firmwared" or "tagged".
Any ideas what could be lingering from Android Pie that would survive a F2FS/exT Format? Because something updated some kind of firmware on the phone during a Pie ROM flash, that now won't let me go back to anything below Pie, with a working fingerprint reader. The only difference between the G5 that works and this one is the working one has never seen Android 9. And it's staying that way til we come up with a way to hack the google crap.
Any help would be - awesome to say the least.
Thanks for looking.
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
sharan.nyn said:
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
Click to expand...
Click to collapse
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
DJScribe said:
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
Click to expand...
Click to collapse
Yeah, give it a try. And yes it's to be flashed via TWRP.
[SOLVED]
sharan.nyn said:
Yeah, give it a try. And yes it's to be flashed via TWRP.
Click to expand...
Click to collapse
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
DJScribe said:
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
Click to expand...
Click to collapse
Crap - so turns out this solution was short-lived. FingerPrint Scanner is back to inactive and FPzip isn't fixing it. Only StockOreo brings it back. Tried a plethora of ROMs from Nougat to Oreo, nothing but Pie and stock Oreo. Symptoms say it's the ROM, but a ROM that is currently working on the 1st G5 won't work either. Still looking for solutions, anyone...

"Android setup isn't responding" and reboot by itself

Hi,
I have strange problem, used 9T come to me with wiped system (factory reset) but when MIUI loaded system i have notification "Android setup isn't responding". I can't accept it or anythink, configuration screen isn't loaded only black screen with status bar and navigation buttons. I can go to settings by the notifiaction bar, but after 10 seconds phone freezing and rebooting by itself.
I flash new system without errors, but it wont fix the problem
I had the same problem, I spent all the roms and the only one that worked was davinci_global_images_V10.3.5.0.PFJMIXM_20190528.0000.00_9.0_global_4222a49ff1
good that the phone is working again but now i'm facing other problems because i can't update the phone otherwise it goes back to loop and with this rom no sensor is working as a presence sensor, gyroscope and also problems with the front camera that is not it is working correctly.
crt-shadow said:
Hi,
I have strange problem, used 9T come to me with wiped system (factory reset) but when MIUI loaded system i have notification "Android setup isn't responding". I can't accept it or anythink, configuration screen isn't loaded only black screen with status bar and navigation buttons. I can go to settings by the notifiaction bar, but after 10 seconds phone freezing and rebooting by itself.
I flash new system without errors, but it wont fix the problem
Click to expand...
Click to collapse
crt-shadow said:
Hi,
I have strange problem, used 9T come to me with wiped system (factory reset) but when MIUI loaded system i have notification "Android setup isn't responding". I can't accept it or anythink, configuration screen isn't loaded only black screen with status bar and navigation buttons. I can go to settings by the notifiaction bar, but after 10 seconds phone freezing and rebooting by itself.
I flash new system without errors, but it wont fix the problem
Click to expand...
Click to collapse
i have the same problem do you have the solution right now? :<
Same problem here. I also can't turn on the wifi and sim cards aren't detected
crt-shadow said:
Hi,
I have strange problem, used 9T come to me with wiped system (factory reset) but when MIUI loaded system i have notification "Android setup isn't responding". I can't accept it or anythink, configuration screen isn't loaded only black screen with status bar and navigation buttons. I can go to settings by the notifiaction bar, but after 10 seconds phone freezing and rebooting by itself.
I flash new system without errors, but it wont fix the problem
Click to expand...
Click to collapse
same here, keep rebooting, u solved it?
Factory reset does not mean to Wipe System but Data.
Gyroscope and other sensors not working are the result of wiping Persist, Vendor and other partitions
Proper procedure to switch the ROM/install custom ROM requires:
- Format Data (option in TWRP, exactly as that "Format Data")
- Wipe Cache
- Do not Wipe any other partition !!!!!!!
- Flash your custom ROM
Unfortunately, there are noobs who don't know/understand, and they Wipe System, Vendor, Persist and who knows what other partitions they think off.
The result is the phone behaving as described
To recover, try flashing the TGZ stock ROM from Mi Flash (not just the ZIP ROM from TWRP).
Anyway, if Persist was wiped, you will never, ever recover DRM L1
zgfg said:
Factory reset does not mean to Wipe System but Data.
Gyroscope and other sensors not working are the result of wiping Persist, Vendor and other partitions
Proper procedure to switch the ROM/install custom ROM requires:
- Format Data (option in TWRP, exactly as that "Format Data")
- Wipe Cache
- Do not Wipe any other partition !!!!!!!
- Flash your custom ROM
Unfortunately, there are noobs who don't know/understand, and they Wipe System, Vendor, Persist and who knows what other partitions they think off.
The result is the phone behaving as described
To recover, try flashing the TGZ stock ROM from Mi Flash (not just the ZIP ROM from TWRP).
Anyway, if Persist was wiped, you will never, ever recover DRM L1
Click to expand...
Click to collapse
The same problem remains even after your method.
pranav1201 said:
The same problem remains even after your method.
Click to expand...
Click to collapse
What exact problem, with which ROM, what did you previously do with the phone?
Hello @zgfg
I'm having the same error as the OP with my Mi 8 (dipper).
I done goofed up, as I had the official 12.0.3.0 stock ROM installed, and then I wanted to go with the 12.5.2.0 EU ROM. I installed it no problem, but then in my infinite wisdom I tried to lock the bootloader via fastboot while having the EU ROM installed. Everything went to hell after that.
After that, I cannot make the phone work properly regardless of the ROM I try to install. With MIUI (both stock and EU), I cannot get the WiFi to work properly (Ino networks are shown), and the "Android Setup isn't responding" error does not let me finish the setup of the device. I also tried lineage, where I also cannot find any networks, so the setup pretty much stops there.
It is obvious I effed up something with lower-level files, I definitely just erased everything from TWRP at one point when I was panicing.
I tried flashing the stock ROM using Mi Flash as you said, but it did not work. Can you provide me a way of checking what is going wrong or a general way to fix this?
Fjolfrin said:
Hello @zgfg
I'm having the same error as the OP with my Mi 8 (dipper).
I done goofed up, as I had the official 12.0.3.0 stock ROM installed, and then I wanted to go with the 12.5.2.0 EU ROM. I installed it no problem, but then in my infinite wisdom I tried to lock the bootloader via fastboot while having the EU ROM installed. Everything went to hell after that.
After that, I cannot make the phone work properly regardless of the ROM I try to install. With MIUI (both stock and EU), I cannot get the WiFi to work properly (Ino networks are shown), and the "Android Setup isn't responding" error does not let me finish the setup of the device. I also tried lineage, where I also cannot find any networks, so the setup pretty much stops there.
It is obvious I effed up something with lower-level files, I definitely just erased everything from TWRP at one point when I was panicing.
I tried flashing the stock ROM using Mi Flash as you said, but it did not work. Can you provide me a way of checking what is going wrong or a general way to fix this?
Click to expand...
Click to collapse
Sorry, I would never go to relock BL while having the custom ROM (I thought it would instantly brick the phone)
Not sure could I help but I'm also curious:
- You relocked the Bootloader by fastboot oem lock or by fastboot flashing lock?
- It locked BL, did Factory reset but kept Xiaomi.eu ROM?
- After that you unlocked BL again (otherwise how would you continue flashing the other ROMs)?
- Did you then unlock BL by Mi Unlock tool or by fastboot flashing unlock?
- Did you then you flash Fastboot/tgz version of the stock MIUI?
And with that the phone does not work properly (network, etc)?
- What version of MIUI you flash, MIUI 12.1 (Global, EEA)?
- Did you try with CN 12.5.2.0, Fastboot/TGZ version (closest Fastboot MIUI version to your previous Xiaomi.eu)?
Un-gzip, unutar, find inside bat scripts (I think 3 of them) choose one that makes Factory reset but does not relock BL.
Edit the script to remove first 3-4 lines that check against downgrading (not having the script in front of me to tell you exactly but you will see when you open the script), and run the bat from Fastboot
zgfg said:
Sorry, I would never go to relock BL while having the custom ROM (I thought it would instantly brick the phone)
Not sure I could help but I'm also curious:
- You relocked the Bootloader by fastboot oem lock or by fastboot flashing lock?
- It locked BL, Factory reset but kept Xiaomi.eu ROM?
- After that you unlocked BL again (otherwise how would you flash the other ROMs)?
- You unlocked BL by Mi Unlock tool or by fastboot flashing unlock?
- Then you flashed Fastboot/tgz version of the stock MIUI?
And with that the phone does not work properly (network, etc)?
- What version of MIUI you tried to flash, MIUI 12.1 (Global, EEA)?
-Did you try with CN 12.5.2.0, Fastboot/TGZ version?
Un-gzip, unutar, find inside bat scripts (I think 3 of them) choose one that makes Factory reset but does not relock BL.
Edit the script to remove first 3-4 lines that check against downgrading (not having the script in front of me to tell you exactly but you will see when you open the script)
Click to expand...
Click to collapse
Thanks for the reply! Here we go:
1. By fastboot oem unlock.
2. I am not sure I remember. I think it could not boot at all.
3. Yes I unlocked it.
4. I have always used the Mi unlock tool to unlock the bootloader.
5. Yes I flashed it this way and it did not work. To be precise, I completely extracted the tgz, I opened Mi flash, selected the final extracted folder, and I flashed this way.
6. With Mi flash I have used the official rom, meaning 12.0.3.0 global (in case you did not read it, this is all for a Mi 8, I just found this thread and though to ask). When I install the EU rom, I use twrp.
7. No I haven’t tried Chinese roms, should I?
I have also tried directly running the bat scripts from the extracted folder as you said, but it didn’t work. Same thing.
Fjolfrin said:
Thanks for the reply! Here we go:
1. By fastboot oem unlock.
2. I am not sure I remember. I think it could not boot at all.
3. Yes I unlocked it.
4. I have always used the Mi unlock tool to unlock the bootloader.
5. Yes I flashed it this way and it did not work. To be precise, I completely extracted the tgz, I opened Mi flash, selected the final extracted folder, and I flashed this way.
6. With Mi flash I have used the official rom, meaning 12.0.3.0 global (in case you did not read it, this is all for a Mi 8, I just found this thread and though to ask). When I install the EU rom, I use twrp.
7. No I haven’t tried Chinese roms, should I?
I have also tried directly running the bat scripts from the extracted folder as you said, but it didn’t work. Same thing.
Click to expand...
Click to collapse
1) Should have been "lock", not "unlock"
7) If I understood correctly, you had Xiaomi.eu 12.5.2.
Hence I think you should try the closest MIUI version (Fastboot, not Recovery - Fastboot flashes more deeply), and that could only be CN 12.5.2 (Global, EEA are 12.0.3 for your device)
The best would be Fastboot version of Xiaomi.eu 12.5.2 but AFAIK, there is no such thing
Hence after the CN 12.5.2 try then (Recovery) Xiaomi.eu 12.5.2
zgfg said:
1) Should have been "lock", not "unlock"
7) If I understood correctly, you had Xiaomi.eu 12.5.2.
Hence I think you should try the closest MIUI version (Fastboot, not Recovery - Fastboot flashes more deeply), and that could only be CN 12.5.2 (Global, EEA are 12.0.3 for your device)
The best would be Fastboot version of Xiaomi.eu 12.5.2 but AFAIK, there is no such thing
Hence after the CN 12.5.2 try then (Recovery) Xiaomi.eu 12.5.2
Click to expand...
Click to collapse
1) Yeah lol, mistyped.
7) Ok! I’ll give it a try. I have an early wake tomorrow tho and I have already spent too much time for this, so it’ll be a while before I come back with news.
Thank you!
You can use MIUI Downloader:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
to easily locate the download link for eg your Fastboot CN 12.5.2 - screenshot
zgfg said:
You can use MIUI Downloader:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
to easily locate the download link for eg your Fastboot CN 12.5.2 - screenshot
Click to expand...
Click to collapse
Good morning!
So I installed the china ROM (12.5.2.0 QEACNXM) using mi flash, and I'm having similar issues. I did not get the "android setup stopped working", however WiFi is still not responding as before, and I got two "Security stopped working" and "Settings stopped working" errors.
Edit: WiFi cannot actually be turned on at all.
Fjolfrin said:
Good morning!
So I installed the china ROM (12.5.2.0 QEACNXM) using mi flash, and I'm having similar issues. I did not get the "android setup stopped working", however WiFi is still not responding as before, and I got two "Security stopped working" and "Settings stopped working" errors.
Click to expand...
Click to collapse
Sorry, no other idea but that you try now again Xiaomi.eu 12.5, with Factory reset
zgfg said:
Sorry, no other idea but that you try now again Xiaomi.eu 12.5, with Factory reset
Click to expand...
Click to collapse
Got it, will try that, adn if it doesn't work I'll see whether I can do something else to fix this.
Anyway, thanks a lot!
Fjolfrin said:
Good morning!
So I installed the china ROM (12.5.2.0 QEACNXM) using mi flash, and I'm having similar issues. I did not get the "android setup stopped working", however WiFi is still not responding as before, and I got two "Security stopped working" and "Settings stopped working" errors.
Edit: WiFi cannot actually be turned on at all.
Click to expand...
Click to collapse
Btw, Bluetooth, NFC, GPS, do they work?
And first, not least, do SIM cards work (voice and mobile data)?
And did you try switching now from CN 12.5 back to Xiaomi.eu 12.5 (they are based on CN, but made to work internationally)
zgfg said:
Btw, Bluetooth, NFC, GPS, do they work?
And first, not least, do SIM cards work (voice and mobile data)?
And did you try switching now from CN 12.5 back to Xiaomi.eu 12.5 (they are based on CN, but made to work internationally)
Click to expand...
Click to collapse
I didn’t try these tbh, but I did go back to the 12.5 EU ROM.
This time I can get inside the phone normally, however Wi-Fi is still sketchy.
I managed to connect to a network, but manually, it still wont scan for network, and the connection is dropped after some minutes. I didn’t try gps, bt, or nfc, as I was trying to troubleshoot Wi-Fi, and this all came to a halt as the phone reboots on its own after 5-10 minutes of operation.

Categories

Resources