Hey everyone, i got a neat little problem with my one X.
I wanted to install Resurrection Remix LP v5.5.0 according to this Thread.
So first of all I flashed twrp 2.6.3.0 to my phone and tried to install RR 5.5.0., which threw me an error (because of layout differences).
I moved on by flashing another recovery twrp2811.BiG to my phone and booted into it, np. So i wiped everything, I think it was the advanced wipe option, I ticked every checkbox and swiped to wipe.
After a short time my phone blackscreened back into the bootloader and when I tried to enter recovery again, it displays the twrp logo for a short time, then crashes and reboots.
Since theres no Android to boot, it repeats it's bootloop. I tried flashing twrp2853-BiG, twrp-2.6.3.0-endeavoru,twrp-2.6.1.0-endeavoru. Fastboot flashes the recoveries and right before my phone restarts it even shows the correct "recovery splash screen" according to the current recovery image flashed.
When I flash recovery-clockwork-touch-6.0.4.8-endeavoru and boot into recovery everythin works, but I can't manage to mount my USB storage anymore.
But that almost doesn't matter since I need twrpXXXXBiG to flash the latest Resurrection Rom, but I cant get any twrp recovery back to work (erase cache didn't help at all).
Lip0ly said:
Hey everyone, i got a neat little problem with my one X.
I wanted to install Resurrection Remix LP v5.5.0 according to this Thread.
So first of all I flashed twrp 2.6.3.0 to my phone and tried to install RR 5.5.0., which threw me an error (because of layout differences).
I moved on by flashing another recovery twrp2811.BiG to my phone and booted into it, np. So i wiped everything, I think it was the advanced wipe option, I ticked every checkbox and swiped to wipe.
After a short time my phone blackscreened back into the bootloader and when I tried to enter recovery again, it displays the twrp logo for a short time, then crashes and reboots.
Since theres no Android to boot, it repeats it's bootloop. I tried flashing twrp2853-BiG, twrp-2.6.3.0-endeavoru,twrp-2.6.1.0-endeavoru. Fastboot flashes the recoveries and right before my phone restarts it even shows the correct "recovery splash screen" according to the current recovery image flashed.
When I flash recovery-clockwork-touch-6.0.4.8-endeavoru and boot into recovery everythin works, but I can't manage to mount my USB storage anymore.
But that almost doesn't matter since I need twrpXXXXBiG to flash the latest Resurrection Rom, but I cant get any twrp recovery back to work (erase cache didn't help at all).
Click to expand...
Click to collapse
Just had an similar issue,
Try flashing first boot.img from the rom you will flash
then flash the recovery twrp big
then do the wipes ..
then flash boot.img and then rom
I thought this worked for me. (i flashed with the unboxed rom)
Just tried it, didn't work for me.
Bump
Yesterday I decided to root my Nexus 7 2013 Wifi running stock 6.0.1 (build MOB30X). I first unlocked the bootloader, then immediately after that I flashed TWRP (twrp-3.0.2-0-flo.img). When I booted up, it would got stuck on a loop with TWRP running OpenRecoveryScript, saying something about unable to mount /data and renaming something, then reboot into TWRP again.
I did some research and it seemed I had to use a multirom TWRP version instead, so I went ahead and flashed it. Now I can go into TWRP, but when booting up I got stuck in the booting animation (the four spinning circles)
How can I fix this?
chinhodado said:
Yesterday I decided to root my Nexus 7 2013 Wifi running stock 6.0.1 (build MOB30X). I first unlocked the bootloader, then immediately after that I flashed TWRP (twrp-3.0.2-0-flo.img). When I booted up, it would got stuck on a loop with TWRP running OpenRecoveryScript, saying something about unable to mount /data and renaming something, then reboot into TWRP again.
I did some research and it seemed I had to use a multirom TWRP version instead, so I went ahead and flashed it. Now I can go into TWRP, but when booting up I got stuck in the booting animation (the four spinning circles)
How can I fix this?
Click to expand...
Click to collapse
Just run these two commands:
Code:
fastboot format cache
fastboot format userdata
Don't worry, you have lost all your data already while unlocking it.
The first boot and the booting animation will be initially longer than usual.
Incidentally, no need to use multirom-TWRP anymore because TWRP v3+ has been properly updated.
I actually solved this myself before k23m's reply by flashing the stock rom (MOB30X), then completed the initial setup, then reflashed TWRP (twrp-3.0.2-0-flo.img, not the multirom version). After that I booted up then restarted into recovery but then realized that TWRP had been wiped (only the android with the red triangle showing). So I re-flashed TWRP again and this time rebooted directly into recovery, and renamed the file recovery-from-boot.p into recovery-from-boot.backup. Then I flashed su and all went well.
k23m said:
Just run these two commands:
Code:
fastboot format cache
fastboot format userdata
Don't worry, you have lost all your data already while unlocking it.
The first boot and the booting animation will be initially longer than usual.
Incidentally, no need to use multirom-TWRP anymore because TWRP v3+ has been properly updated.
Click to expand...
Click to collapse
Thank you for the hint!
Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.
goatlad said:
Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.
Click to expand...
Click to collapse
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer
crzykiller said:
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer
Click to expand...
Click to collapse
tried official twrp 3.1.1-0, did these steps only, maybe I've missed something:
installed twrp 3.1.1-0 then went into fastboot and typed fastboot format userdata
rebooted into TWRP, i was promted whether to keep system read only, I tried first swiping to allow mods, and also keep read only then proceeded:
changed data to F2FS (didn't wipe or factory reset anything else)
rebooted system
copied lineage and gapps zip files to phone
installed latest lineage then gapps 7.1 arm64
rebooted system, back into twrp
Used the search, used google, couldn't find any concrete answers
I am on Android N - unlocked bootloader - rooted via magisk, One Plus 3.
Could I do the following?
use TWRP to make a Nandroid Backup (System+Data+Boot) of my current set-up
then, manually flash (using twrp) Android O
find out I don't particularly like it
Go back to TWRP and Nandroid Restore back to Android N, as if no update ever happened
Or will there be issues?
Thanks
I do that with freedomos. 2.17(N)>3.1(O)>2.17. I restore nandroid and reflash rom
xGOGI said:
I do that with freedomos. 2.17(N)>3.1(O)>2.17. I restore nandroid and reflash rom
Click to expand...
Click to collapse
Should have mentioned I'm using stock rom.
So I'd restore the nandroid via twrp, and I should be good to go?
arthritis said:
Used the search, used google, couldn't find any concrete answers
I am on Android N - unlocked bootloader - rooted via magisk, One Plus 3.
Could I do the following?
use TWRP to make a Nandroid Backup (System+Data+Boot) of my current set-up
then, manually flash (using twrp) Android O
find out I don't particularly like it
Go back to TWRP and Nandroid Restore back to Android N, as if no update ever happened
Or will there be issues?
Thanks
Click to expand...
Click to collapse
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Thank you for the detailed procedure.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Thank you
Hi @maxs8007
thanks for the instructions. I did all that to get back to my nougat rom (PureFusion) and all seem good and phone booted fine. But i am stuck on login screen after booted up. I tried my correct password several times but to no avail. anyway reset my password without factory resetting again?
Thanks for the advise.
sqlpro said:
Hi @maxs8007
thanks for the instructions. I did all that to get back to my nougat rom (PureFusion) and all seem good and phone booted fine. But i am stuck on login screen after booted up. I tried my correct password several times but to no avail. anyway reset my password without factory resetting again?
Thanks for the advise.
Click to expand...
Click to collapse
Go to twrp - advanced - file manager - go to root folder - data - system - and delete files with .key extension. There will be 2 files delete both and reboot.
maxs8007 said:
Go to twrp - advanced - file manager - go to root folder - data - system - and delete files with .key extension. There will be 2 files delete both and reboot.
Click to expand...
Click to collapse
Thank you very much and that worked. I am back in the system.
BTW in your original instructions I had to re flash rom after restoring twrp backup otherwise it didn't boot and stuck at rom animation.
sqlpro said:
Thank you very much and that worked. I am back in the system.
BTW in your original instructions I had to re flash rom after restoring twrp backup otherwise it didn't boot and stuck at rom animation.
Click to expand...
Click to collapse
Thanks for pointing out, I must have forgot to add it. I'll update again.
Hi @maxs8007
I ran into this issue again today! after unlocking as per instructions yesterday and am back into phone and re-set the pin and all good. But today i had to reboot the phone and same issue again , cant login on the lock screen!! i tried deleting those files again but to no avail!!
any ideas before factory reset and loose my data ? Thanks.
sqlpro said:
Hi @maxs8007
I ran into this issue again today! after unlocking as per instructions yesterday and am back into phone and re-set the pin and all good. But today i had to reboot the phone and same issue again , cant login on the lock screen!! i tried deleting those files again but to no avail!
any ideas before factory reset and loose my data ? Thanks.
Click to expand...
Click to collapse
This should not have happened, anyways delete all those files which I've highlighted in the image below. This will reset the lock settings.
Oh sorry I forgot to attach the file. Here it is.
maxs8007 said:
There won't be any issue. You are alright with the procedure. Just make sure you use the correct twrp recovery for oreo coz if you use the non compatible recovery then you won't be able to boot into recovery once the oreo is flashed and you are forced to go with the stock recovery
Process I followed when I tried oreo last week
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Do factory reset(wipe everything except internal storage) then flash oreo twrp image. Perform reboot. (no OS warning on reboot option screen will appear) just ignore it. It will boot to recovery even without the OS.
Once booted back to new recovery(oreo twrp)
Flash oreo stock zip and again flash oreo twrp image and reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu. Reboot to OS
Enjoy oreo
To go back to nougat
Reboot to recovery.
Perform factory reset as mentioned above.
Restore everything except bootloader, cache and dalvik cache
Flash nougat twrp recovery. Reboot to system.
Happy flashing.
Edit : use blu sparks recovery for nougat backup.
Click to expand...
Click to collapse
Hi, OP here. Thanks for this guide.
Unfortunately, it did not work out for me.
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Done
Do factory reset(wipe everything except internal storage)
Wiped fine although I got an error of not being able to wipe 'USB-OTG' or whatever it's called. I ignored it and moved on.
then flash oreo twrp image.
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Then I rebooted and went back to recovery.
Flash oreo stock zip
flash oreo twrp image
Done
reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu.
This is where it ends. I get stuck at the OnePlus loading screen and forced reboot into twrp and flashed magisk. Once I boot up the OS, I get stuck at the OnePlus logo and that's it.
I actually re-did ALL of the steps again (in case I made a mistake) and still, the same issue. No progression.
Once I gave up on Oreo, I decided to go restore my nandroid
Reboot to recovery. Perform factory reset as mentioned above.
Wiped
Restore everything except bootloader, cache and dalvik cache
Here's the issue:
I press Restore (I uncheck both bootloader and cache, but there's no option for a specific dalvik cache- unless I'm not looking hard enough?) and I get the 255 Error.
Flash nougat twrp recovery. Reboot to system.
I tried to ignore that error and flash the twrp recovery.
Rebooted and it took me to fastboot. Regardless of I keep trying to reboot system it won't work.
I actually made two separate nandroid backups (the same 'everything except system image' as you've described) in case one of the backups was corrupted. Both backups ended up with the same error.
I got too tired of all these errors and just found a stock recovery and ROM and flashed it back. Now, all my apps and settings are gone. To be honest, I just want my phone back to where it was with Nougat.
Can anyone assist me?
@maxs8007, Like I said I did that already but nope still same issue. It wouldn't let me do matter what I did.
---------- Post added at 04:59 AM ---------- Previous post was at 04:54 AM ----------
arthritis said:
Hi, OP here. Thanks for this guide.
Unfortunately, it did not work out for me.
Take nandroid of all options available except system image. (system, data, bootloader, firmware, efs, etc.) on nougat twrp.
Done
Do factory reset(wipe everything except internal storage)
Wiped fine although I got an error of not being able to wipe 'USB-OTG' or whatever it's called. I ignored it and moved on.
then flash oreo twrp image.
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Then I rebooted and went back to recovery.
Flash oreo stock zip
flash oreo twrp image
Done
reboot to recovery(this time the device will get stuck with a black screen and white LED). Don't panic, just force reboot the device and go to recovery again to flash magisk/supersu.
This is where it ends. I get stuck at the OnePlus loading screen and forced reboot into twrp and flashed magisk. Once I boot up the OS, I get stuck at the OnePlus logo and that's it.
I actually re-did ALL of the steps again (in case I made a mistake) and still, the same issue. No progression.
Once I gave up on Oreo, I decided to go restore my nandroid
Reboot to recovery. Perform factory reset as mentioned above.
Wiped
Restore everything except bootloader, cache and dalvik cache
Here's the issue:
I press Restore (I uncheck both bootloader and cache, but there's no option for a specific dalvik cache- unless I'm not looking hard enough?) and I get the 255 Error.
Flash nougat twrp recovery. Reboot to system.
I tried to ignore that error and flash the twrp recovery.
Rebooted and it took me to fastboot. Regardless of I keep trying to reboot system it won't work.
I actually made two separate nandroid backups (the same 'everything except system image' as you've described) in case one of the backups was corrupted. Both backups ended up with the same error.
I got too tired of all these errors and just found a stock recovery and ROM and flashed it back. Now, all my apps and settings are gone. To be honest, I just want my phone back to where it was with Nougat.
Can anyone assist me?
Click to expand...
Click to collapse
Buddy from my experience the whole thing too finicky and am thinking just factory reset and stick with stock rom. I wasted so much time already. Everytime I get different error, probably recoveries still not fully compatible with Oreo.
sqlpro said:
@maxs8007, Like I said I did that already but nope still same issue. It wouldn't let me do matter what I did.
---------- Post added at 04:59 AM ---------- Previous post was at 04:54 AM ----------
Buddy from my experience the whole thing too finicky and am thinking just factory reset and stick with stock rom. I wasted so much time already. Everytime I get different error, probably recoveries still not fully compatible with Oreo.
Click to expand...
Click to collapse
Could you please tell me what error you get on the lock screen? Could you post an image so that I can get a better idea of what's happening with your device? Also could you please confirm which files have you deleted? This time you need to delete 5 files which are related to lock screen setting and those are the only files responsible for lock settings on the device. I'm somewhat confused because I never ran into such issue while I did the oreo thing
If you have decided to flash stock then just make a backup of data partition so that you won't loose your data and you can easily restore it via twrp.
---------- Post added at 01:06 AM ---------- Previous post was at 12:42 AM ----------
arthritis said:
I googled oreo twrp image and got an img file with filename "TWRP-Oreo-OnePlus-3-3T". When I installed the img, it asked the options to choose Boot, System, or Recovery - so I chose System.
Click to expand...
Click to collapse
I read the entire post and here what I've to say. The above quoted steps is where you went wrong. The recovery needs to to be flashed as a recovery and not as system.
In your case the nougat recovery was never replaced with the oreo recovery because you flashed it as a system. This is where it went wrong. Sorry for the dalvik cache and USB - otg, I didn't mentioned about them. Those are the least important points in flashing though I should have mentioned that already
The next thing you mentioned is you went back to recovery which at that moment was nougat recovery and not oreo recovery. I'll link the modded recovery I used for oreo below
The next thing you did is you flashed oreo zip and again flashed the oreo recovery but as you flashed the recovery as system, the oreo stock rom was automatically replaced with recovery because you flashed it as system and the device didn't boot because there was no android OS to boot up
You got stuck on oneplus boot up screen. (this was going to happen because of the same flashing error at your end).
You were unable to boot back to nougat as well because of the same issue.. Never flash the recovery as system. This won't let you boot the device.
To restore your nandroid backup just follow the steps below
As you confirmed you booted to stock rom with a stock recovery.
Flash nougat twrp via fastboot
Boot back to the twrp recovery and restore the nandroid backup and you are good to go
---------- Post added at 01:18 AM ---------- Previous post was at 01:06 AM ----------
I'll make a video in my free time to help you guys with the steps that I've followed to flash oreo rom and how i came back to nougat successfully.
Hello @maxs8007
Sorry I didn't have any screen shots of the prompt and finally I was fed up with the whole process and had to switch back to oreo stock rom.
Login prompt I was referring to was standard pin required load android. Black background with only pin entry.
BTW I tried blu twrp recovery oreo version and nougat version.
What's interesting is, after several failed attempts it said I got 10 more tries before phone wiped out but after 10 attempts it started counting backwards from zero, - 1,-2 etc., finally I had to flash stock recovery via fastboot and selected forgot password option which reset my phone.
BTW I have deleted all those files from data/system I found another thread but no dice.
Thank you for trying to help us all.
@maxs8007 followed your steps. Booted to oreo, didn't felt as stable as nougat then booted back to nougat. You saved me. Thanks.
sqlpro said:
Hello @maxs8007
Sorry I didn't have any screen shots of the prompt and finally I was fed up with the whole process and had to switch back to oreo stock rom.
Login prompt I was referring to was standard pin required load android. Black background with only pin entry.
BTW I tried blu twrp recovery oreo version and nougat version.
What's interesting is, after several failed attempts it said I got 10 more tries before phone wiped out but after 10 attempts it started counting backwards from zero, - 1,-2 etc., finally I had to flash stock recovery via fastboot and selected forgot password option which reset my phone.
BTW I have deleted all those files from data/system I found another thread but no dice.
Thank you for trying to help us all.
Click to expand...
Click to collapse
I'm sorry that I was unable to help you. The thing is I never used the pin prompt to load android because I reboot too often to flash things via recovery and its too much of a hassle to enter the pin everytime the device is booted and I think it's too much to a security for a android device when there's already a lock screen present once booted to secure the device.
Please don't put the pin entry to load android next time if you flash stuff regularly. It will save you the hassle of going back to stock rom and recovery when something like this ever happens again. The files which I told you to delete in the image I posted above remove the lock screen protection completely
The login pin at the boot to load android was implemented to avoid unauthorized access to the device in case it gets stolen or lost.
maxs8007 said:
I'm sorry that I was unable to help you. The thing is I never used the pin prompt to load android because I reboot too often to flash things via recovery and its too much of a hassle to enter the pin everytime the device is booted and I think it's too much to a security for a android device when there's already a lock screen present once booted to secure the device.
Please don't put the pin entry to load android next time if you flash stuff regularly. It will save you the hassle of going back to stock rom and recovery when something like this ever happens again. The files which I told you to delete in the image I posted above remove the lock screen protection completely
The login pin at the boot to load android was implemented to avoid unauthorized access to the device in case it gets stolen or lost.
Click to expand...
Click to collapse
Frankly no clue why deleting those files didn't reset my pins and I even deleted gatekeeper files too.
Maybe these are lock screen key files and android boot prompt stored somewhere else. Not sure though.
Hi
After sitting on xiaomi.eu for a while I decided to change things up and go back to Paranoid Android Quartz 4. I flashed Global fastboot rom (V11.0.6.0.QFBEUXM which I had from a while ago) via MiFlash, booted the phone, went back to fastboot, flashed twrp and booted into it. Twrp didnt decrypt data on the phone, but I didn't think much of it and just formatted data. Then I flashed shrp, formatted cache, dalvik, system, data and internal storage, and using shrp I flashed firmware that was included with the rom, and then the rom itself. After that I tried booting the system, but after showing Mi logo it justs boots info fastboot. Even if I try to flash recovery and boot into it, it still reboots to bootloader. I don't really know what am i doing wrong.
Does anyone know what might be wrong?
Thanks in advance
fejlip said:
Hi
After sitting on xiaomi.eu for a while I decided to change things up and go back to Paranoid Android Quartz 4. I flashed Global fastboot rom (V11.0.6.0.QFBEUXM which I had from a while ago) via MiFlash, booted the phone, went back to fastboot, flashed twrp and booted into it. Twrp didnt decrypt data on the phone, but I didn't think much of it and just formatted data. Then I flashed shrp, formatted cache, dalvik, system, data and internal storage, and using shrp I flashed firmware that was included with the rom, and then the rom itself. After that I tried booting the system, but after showing Mi logo it justs boots info fastboot. Even if I try to flash recovery and boot into it, it still reboots to bootloader. I don't really know what am i doing wrong.
Does anyone know what might be wrong?
Thanks in advance
Click to expand...
Click to collapse
Hi
Try flashing vbmeta it might help you to boot
Sounds like you will have to start from scratch and flash the fastboot ROM and proceed from there.
However, after formatting data in TWRP, reboot into recovery before flashing SHRP and PA.
If after this it reboots into recovery rather than system, you can try flashing vbmeta.
Peace
---------- Post added at 01:37 PM ---------- Previous post was at 01:32 PM ----------
Also, TWRP won't ask for a password to decrypt data if you went straight back to fastboot after flashing the stock ROM as you won't have set up a decryption password without setting up the phone.
Also, I'm not sure that you have to format any other partition other than data, just a wipe should be enough. But definitely reboot recovery after formatting data. The PA thread should say whether partitions need to be formatted or simply "wiped"
Peace.
I tried doing it again a few more times but with no luck. So instead I tried to flash xiaomi.eu weekly rom, but that also doesn't work for me. I downloaded newest Global Fastboot Rom (V12.0.1.0.QFBMIXM), flashed it with MiFlash and then proceeded to set up the phone as a new device. After setup I turned on usb debugging, went into fastboot and flashed redispade TWRP 3.3.1 (rebooted into TWRP and got asked for decryption password). Then I wiped data, cache and dalvik and flashed xiaomi.eu. After I flashed the rom, I installed magisk (without rebooting the device). Then when I tried to boot into system I got stuck in recovery bootloop (files where encrypted, did not get asked for password). I also tried to flash vbmeta after that but the phone was still bootlooping. I honsetly have no clue what I am doing wrong at this point
Edit: I tried it again this time without flashing magisk and the results are exactly the same - twrp bootloop even after flashing vbmeta
I personally don't use miflash to flash fastboot ROMs, I prefer to do it via fastboot. Could miflash be causing issues? Have you replicated the steps you took to originally flash xiaomi.eu ROM?
Peace.