Database Users

OXYGEN OS(Download link ,installation guide & Issues)

Download OxygenOS http://oxygenos.oneplus.net/oxygenos_1.0.0.zip
DO UNZIP your ZIP before flashing!!! installation ZIP is in ZIP file provided
Plain Aosp Rom
Download Feedback App https://s3.amazonaws.com/oxygenos.oneplus.net/Feedback_v1.0.2.apk
Note: You’ll need to enable installations from unknown sources (settings > security) in order to install the feedback app on OxygenOS.
Please make sure all your data and files are backed up before commencing. Flashing OxygenOS onto CM does require a system wipe, so you will lose all of your data. We are actively working on an easier, more automated solution soon to be available, but for now the build must be flashed manually.
Please proceed only if you are confident in your abilities to flash a custom ROM. This guide exists to help you flash OxygenOS, but things can still go wrong if not followed correctly. While rooting and flashing will not void your OnePlus warranty, any damage caused by improper flashing is not covered under warranty.
The following instructions assume you have Fastboot and ADB installed.
Step 1
You first need to flash a recovery onto your device. We recommend using TWRP. Please download the recovery image to your computer. You can follow their instructions to flash recovery, or you can reference these steps:
Boot into fastboot mode. You can do this on your OnePlus One by holding down the power button and the volume up button. When you see the fastboot logo, connect your device to your computer.
In your terminal window, find the folder where you put the recovery image and run the following commands:
fastboot oem unlock (You can skip this step if your phone’s bootloader is already unlocked).
fastboot flash recovery <recovery.img>. Image file should be the TWRP recovery image.
fastboot reboot
You should now have the recovery installed.
Step 2
Copy oxygenos_1.0.0.flashable.zip to your phone. On a Mac, you can use Android File Transfer.
Step 3
Boot into recovery. You can do this on your OnePlus One by holding down both the volume down key and the power button.
Step 4
Once you are in the recovery interface, the first thing you want to do is a factory reset. Again, you will lose all your data so please make sure you have backed up everything before doing this.
Step 5
After the wipe, go to install and find oxygenos_1.0.0.flashable.zip. Confirm flash. This will flash OxygenOS onto your device.
Step 6
After the flash succeeds, you can reboot the device, which will take you to the new OxygenOS. Enjoy!
List of known issues:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes

manishsharma17 said:
Download OxygenOS http://oxygenos.oneplus.net/oxygenos_1.0.0.zip
Download Feedback App https://s3.amazonaws.com/oxygenos.oneplus.net/Feedback_v1.0.2.apk
Note: You’ll need to enable installations from unknown sources (settings > security) in order to install the feedback app on OxygenOS.
Please make sure all your data and files are backed up before commencing. Flashing OxygenOS onto CM does require a system wipe, so you will lose all of your data. We are actively working on an easier, more automated solution soon to be available, but for now the build must be flashed manually.
Please proceed only if you are confident in your abilities to flash a custom ROM. This guide exists to help you flash OxygenOS, but things can still go wrong if not followed correctly. While rooting and flashing will not void your OnePlus warranty, any damage caused by improper flashing is not covered under warranty.
The following instructions assume you have Fastboot and ADB installed.
Step 1
You first need to flash a recovery onto your device. We recommend using TWRP. Please download the recovery image to your computer. You can follow their instructions to flash recovery, or you can reference these steps:
Boot into fastboot mode. You can do this on your OnePlus One by holding down the power button and the volume up button. When you see the fastboot logo, connect your device to your computer.
In your terminal window, find the folder where you put the recovery image and run the following commands:
fastboot oem unlock (You can skip this step if your phone’s bootloader is already unlocked).
fastboot flash recovery <recovery.img>. Image file should be the TWRP recovery image.
fastboot reboot
You should now have the recovery installed.
Step 2
Copy oxygenos_1.0.0.flashable.zip to your phone. On a Mac, you can use Android File Transfer.
Step 3
Boot into recovery. You can do this on your OnePlus One by holding down both the volume down key and the power button.
Step 4
Once you are in the recovery interface, the first thing you want to do is a factory reset. Again, you will lose all your data so please make sure you have backed up everything before doing this.
Step 5
After the wipe, go to install and find oxygenos_1.0.0.flashable.zip. Confirm flash. This will flash OxygenOS onto your device.
Step 6
After the flash succeeds, you can reboot the device, which will take you to the new OxygenOS. Enjoy!
List of known issues:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
Click to expand...
Click to collapse
OMG!!! Is this a Dream???? Is this real?

CM version?

manish.kumar86 said:
CM version?
Click to expand...
Click to collapse
its not based on Cm its based on AOSP its 5.0.2

Yash Kanchhal said:
So when we are factory resetting the phone in recovery is it the same thing like wiping the other thing (cache, dalvik cache etc). I'm new in this so I'm not able to understand that please help me in this & when is the CM12S coming anyone knows?????
Sent from my A0001
Click to expand...
Click to collapse
TWRP has an option for factory reset ...

There's already a thread for this here:
http://forum.xda-developers.com/showthread.php?t=3072259
Transmitted via Bacon

Yash Kanchhal said:
Ohk thnx mate it means wiping is every thing????? Right ????
Sent from my A0001
Click to expand...
Click to collapse
yes sir ..use the option of factory reset in twrp and you should be good

timmaaa said:
There's already a thread for this here:
http://forum.xda-developers.com/showthread.php?t=3072259
Transmitted via Bacon
Click to expand...
Click to collapse
When i created the thread the thread was not there in present form

manishsharma17 said:
When i created the thread the thread was not there in present form
Click to expand...
Click to collapse
Unfortunately it looks like he created his first.
Transmitted via Bacon

Nice spam indeed. Three threads, three posts, three times begging for thanks. Bah.

Can you add my guide thread to the OP please?
http://forum.xda-developers.com/oneplus-one/general/guide-how-to-install-oxygenos-t3072500

Word of caution! I backuped on the internal sd. Had all my backups of os's and app data completely wiped. Never checked the wipe internal sd box. Use and external backup.

Is anyone with SuperSU 2.46 having issues with WIFI not turning on and also having screen artifacts that force to do a hard reboot?

cyberon said:
Is anyone with SuperSU 2.46 having issues with WIFI not turning on and also having screen artifacts that force to do a hard reboot?
Click to expand...
Click to collapse
Getting neither of those. Main problem I'm having is major Google Play Services drain. It's the same bug we had on CM12 nightlies some time ago and my phone is permanently awake
Sent from my A0001 using Tapatalk

Hello, due to having a similar topic here http://forum.xda-developers.com/oneplus-one/general/oxygen-os-released-download-t3072259, I will have to close this thread.
Please continue the discussion in the one linked.
Regards

[FIX][OP3/OP3T] DM-Verity warning fix. Works on 4.1.0!!

Hi, i discovered a fix for this problem and made 2 flashable zips. Follow the steps.
If you have 4.0.2 or older just do steps 3 and 4.
1- Download the 4.0.2 firmware and the firmware of your current version:
OP3T files:
Oxygen 4.1.1:https://drive.google.com/open?id=0Bzko1towAti5XzNCRVVwUVYzRms
Oxygen 4.1.0:[url]https://drive.google.com/open?id=0Bzko1towAti5WW1rUThrb3lHUWs[/URL]
Oxygen open beta 3:[url]https://drive.google.com/open?id=0Bzko1towAti5d3BtOEtXdk9hVTA[/URL]
Oxygen 4.0.3:[url]https://drive.google.com/open?id=0Bzko1towAti5NzU5b3lDaEZfZ3M[/URL]
Oxygen 4.0.2:[url]https://drive.google.com/open?id=0Bzko1towAti5NGVsTUtfd2VUY2M[/URL]
OP3 files:
Oxygen 4.1.1:https://drive.google.com/open?id=0Bzko1towAti5eXpXOXRUcXRoeXc
Oxygen 4.1.0:[url]https://drive.google.com/open?id=0Bzko1towAti5WEtoYXd0NW1qUVk[/URL]
Oxygen open beta 12:[url]https://drive.google.com/open?id=0Bzko1towAti5aVVvNkIwTURjaE0[/URL]
Oxygen 4.0.3:[url]https://drive.google.com/open?id=0Bzko1towAti5SW5FdE1EczQybUU[/URL]
Oxygen 4.0.2:[url]https://drive.google.com/open?id=0Bzko1towAti5eDFmZzZPQVI2OXc[/URL]
2- Flash in TWRP the 4.0.2 firmware zip.
3- Reboot to bootloader and connect your phone to the pc.
4- Use this commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
5- Reboot to recovery
6- Flash in TWRP the firmware of your current OOS version.
And you are done! :highfive:

Migdilu said:
Hi, i discovered a fix for this problem and made 2 flashable zips. Follow the steps.
1- Download the two files:
[url]https://drive.google.com/open?id=0Bzko1towAti5Uld0cWp1YWdfLXM[/URL]
[url]https://drive.google.com/file/d/0Bzko1towAti5LXFUbEJwYUFFbGc/view?usp=sharing[/URL]
2- Flash in TWRP the 4.0.2 firmware zip.
3- Reboot to bootloader.
4- Use this commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
5- Reboot to recovery
6- Flash in TWRP 4.0.3 firmware zip.
And you are done! :highfive:
Click to expand...
Click to collapse
thanks for the fix
but 4.0.3 firmware says 3.5.3 firmware for 3t.Is that a updater script error??

kunal1540 said:
thanks for the fix
but 4.0.3 firmware says 3.5.3 firmware for 3t.Is that a updater script error??
Click to expand...
Click to collapse
Exactly, I'm uploading a new file correcting that. But don't worry, you flashed the 4.0.3 firmware. Thanks for the report!

Worked for me as well. Thank you.

thanks worked at my 1+3T.

working for me also on A3010.
thanks.

Please add
Code:
getprop("ro.display.series") == "OnePlus 3T" || abort("E3004: This package is for \"OnePlus 3T\" devices; this is a \"" + getprop("ro.display.series") + "\".");
as first line in your updater-script which prevents bricked devices.

Nice to see it's working!
sniperle said:
Please add
as first line in your updater-script which prevents bricked devices.
Click to expand...
Click to collapse
I'll check that later, thanks!

I just flashed 4.0.2 firmware zip.
Then choose Reboot to bootloader.
Phone just goes off.
Now wont power at all. Even if I plug in to power it up, the light doesnt lit up.
It's comepletly dead now
Oh, god, I just killed my phone beacouse that verity thing! I should leave it alone.

done it with 4.0.2 rooted and without succes

Is this only for OnePlus 3T?
I fuc..d my device beacouse I flashed this on my OnePlus 3?
I didn't look the topic name before. And in post it didnt stated taht its for OP3T only.

nitramcek said:
I just flashed 4.0.2 firmware zip.
Then choose Reboot to bootloader.
Phone just goes off.
Now wont power at all. Even if I plug in to power it up, the light doesnt lit up.
It's comepletly dead now
Oh, god, I just killed my phone beacouse that verity thing! I should leave it alone.
Click to expand...
Click to collapse
You did something wrong. Do you have 3 or 3t?

nitramcek said:
Is this only for OnePlus 3T?
I fuc..d my device beacouse I flashed this on my OnePlus 3?
I didn't look the topic name before. And in post it didnt stated taht its for OP3T only.
Click to expand...
Click to collapse
Its on oneplus 3t forum.. Can you boot to booloader?

madmax28011980 said:
done it with 4.0.2 rooted and without succes
Click to expand...
Click to collapse
Just do step 3 and 4 if you are on 4.0.2 or older. Now flash 4.0.2 firmware and then do 3 and 4 and you are done.

off topic I know, but can someone explain why people are getting this error? If you root correctly you don't this error.

Migdilu said:
Its on oneplus 3t forum.. Can you boot to booloader?
Click to expand...
Click to collapse
No. It's compleatly dead.
I got in this forum thru link on other forum about DM-verity and didnt really look on what forum I landed until i bricked device.

nitramcek said:
No. It's compleatly dead.
I got in this forum thru link on other forum about DM-verity and didnt really look on what forum I landed until i bricked device.
Click to expand...
Click to collapse
I'm sorry. Make a thread on oneplus 3 forum explaining that you accidentally flashed 3T firmware, maybe someone has a solution for this.
EDIT: Take a look at the unbrick guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

Snappiestjack said:
off topic I know, but can someone explain why people are getting this error? If you root correctly you don't this error.
Click to expand...
Click to collapse
Not sure what/if I've done wrong TBH... still, I had the message

I reflashed op3t recovery i then reflashed oxygen 4.0.2 but still getting the error then i flashed twrp 3. and then the su after that i have flashed your 4.0.2. Img and gave the fastboot commands still the error is there maybe i do something wrong! The weird is that when i enter twrp it asks me for a pattern... Should i remove security locks from oxygen 4.0.2 and try again! Anyway.. Goodnight for now.

It's worked!!!
thx a lot!!!

rr 7.1.2 without gapps/ recovery mode not possible

Hello xda developers this is my second thread sorry for the first one that i made yesterday, I am having a problem with my lenovo k4 note a7010a48
after rooting successfully I proceed to flash rr 7.1.2 but did not flash the gapps now my problem is how to go back on recovery mode to start over again
I already used the power button followed by the volume up down buttons but it is not working like before it is nougat. I only need to get to recovery mode. Please help and thankyou in advance. More power

Does u have root access now and which version of rr u flashed

yes the phone is rooted already and flashed with rr 7.1.2 only need to open recovery mode which is I have no idea

Contact in telegram app 9032015333 I will tell u

i dont know that or how to do that can you teach me please thank you

I have the same issue. Can't enter into recovery and the phone is unable to start.

Same Issue || Don't Know How To Fix
Hi,
I am searching for a possible solution from a day. But could not find a working solution.
After successfully flashing RR-N-5.8.5 (Android N)
Unable to go into recovery.
PROBLEM DESCRIPTION:
1. When Press Vol Up + Vol Down + Power Up
2. Recovery is not loading up
3. Instead it goes in boot loop
4. Normal boot mode and fast boot mode are working perfectly fine
SOLUTIONS TRIED:
1. Flashing recovery again using fastboot mode
2. Flashing different recovery, i.e updated version of recovery
As all recoveries which were available were for marshmallow version. I am not sure but have doubt as android version is updated so the kernel so do recovery also become obsolete in this case ?
Any help is welcome and appreciated
Thanks
---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------
jaineshjain said:
Contact in telegram app 9032015333 I will tell u
Click to expand...
Click to collapse
Whole concept of this platform is sharing your knowledge
Don't you think it would be better if you discuss here itself ?

jaineshjain said:
Contact in telegram app 9032015333 I will tell u
Click to expand...
Click to collapse
Whole concept of this platform is sharing your knowledge
Don't you think it would be better if you discuss here itself ?

for fastboot mode and for recovery mode yes i tried it also but thats the problem no recovery mode. I will wait for the solution when it comes i will just store my phone for a while.

Hi Developers,
Is it possible to reset the phone at hardware level? I can't even connect the phone to PC as it keeps on rebooting.
Please note: upgraded to Nougat and wanted to do the second recovery as suggested by mohancm in the post. When the phone rebooted (before flashing the second recovery), the problem started.
Please let me know if any one has a fix/workaround for the issue.
Thanks,
Srihari

1.Download TWRP recovery unzip files.
https://drive.google.com/file/d/0B1CKVcdcbHFPUzFCODVMN0ZfTW8/view
2.Now in folder TWRP\img\ there is the file recovery.img.
3.Download the second recovery for nougat recovery-Nougat.img and put in the TWRP\img folder.
https://androidfilehost.com/?fid=673368273298981920
4.Rename it as the original, recovery.img and replace it.
5.Then connect your phone to usb and select the 3th option from usb debugging message
"Transfer photos(ptp)"
6.run TWRP_Install.bat from TWRP folder
And you are done, had the same problem and I figure this solution, hope it will help.

I cannot locate the transfer photos(ptp)

ok I already done the part I am now on the recovery mode thanks. new problem of mine is after flashing the rom gapps and recovery after reboot it goes back to recovery mode did I miss something on flashing?

ok so i already passed this problem thanks for the help xda community thank you very much but I have this bootloop problem maybe I did a mistake flashing before rebooting sorry i am a noob in this kind of upgrade specially in mobile phones. I will be careful next time after I passed this problem I hope you will help me once again, my phone in bootloop is killing me.

I have same issue... I flashed gapps and my phone is working smoothly... The issue is i can't go into recovery mode... I tried some one tap reboot to recovery apps but all whats happening is phone restarting normally.

For those who can't access recovery mode. You were supposed to flash updated recovery image after flashing rrn rom.
Enter into fastboot mode by using adb shell.
Flash the updated recovery image
Now try rebooting into recovery.
Should work.
Worst case, restore by flashing stock rom using SP flash tools. And then start all over again.
If you face any issues ping me. Even I had faced this issue and fixed it after a lot of struggle. I can try to help you.

Or you could download Official Twrp App directly from play store, then find A3000 (Air Row) in 'select device' and flash that to recovery, (if your phone is rooted) then you are good to go, go to recovery mode and thats all, your twrp is now has been flashed.
Thank me later??

MisledMew said:
Enter into fastboot mode by using adb shell.
Flash the updated recovery image
Now try rebooting into recovery.
Click to expand...
Click to collapse
This really worked for me. Many thanks man.
Well it got me some time to find the right recovery image for my ROM so I decided to give you link for anyone going through the same.
My configuration at that time was: DotOS 1.2 and TWRP 3.1.1 (or so).
On the DotOS thread was enclosed link to wrong recovery image file (or its version was changed as of 28.12.2018) but after small investigation I found this file recovery-mohan-N.img.
Note: This recovery worked for TWRP and Android Nougat and I'm not an expert to suggest this will work for your case either.
Thank you again and have a nice time

firelmnt said:
This really worked for me. Many thanks man.
Well it got me some time to find the right recovery image for my ROM so I decided to give you link for anyone going through the same.
My configuration at that time was: DotOS 1.2 and TWRP 3.1.1 (or so).
On the DotOS thread was enclosed link to wrong recovery image file (or its version was changed as of 28.12.2018) but after small investigation I found this file recovery-mohan-N.img.
Note: This recovery worked for TWRP and Android Nougat and I'm not an expert to suggest this will work for your case either.
Thank you again and have a nice time
Click to expand...
Click to collapse
Glad it helped

Fix for WIERD LOCKSCREEN BUG on Android 8 and + custom roms

How to Fix for WIERD LOCKSCREEN BUG on Android 8 and + custom roms
Many of them are facing this Bug after setting up Lockscreen, after few reboots we face System UI FC when entering Unlock code or pattern. This bug is faced when using Oreo, Pie and 10. And this bug is not present on Nougat.
Warning You will loss your all data including your device internal storage and i will be not responsible for any bricks if it happens on your device
Steps :-
Step 1 :- First of all Download MIUI global stable FASTBOOT ROM from the link http://bigota.d.miui.com/V10.2.1.0....XM_20190114.0000.00_6.0_global_8a48e54fe3.tgz
Step 2 :- download mi flashtool and install on your pc and extract fastboot_rom.tgz to a folder.
Step 3 :- Important to have Official Unlock, if you are Unofficially unlocked try this method :- https://forum.xda-developers.com/re...icially-unlock-bootloader-redmi-note-t4009799
Step 4 :- Now copy userdata.img and persist.img from images folder to minimal adb and fastboot folder.
Step 5 :- Now open command window and write following commands -
fastboot erase persist
fastboot erase userdata
fastboot flash persist persist.img
fastboot flash userdata userdata.img
Step 6 :- Now "clean" flash a custom rom 8 or above it. And check whether this bug is still present of not. If you still face the bug then once flash full MIUI through Mi flash tool and repeat Step 5. Note :- After repeating Step 5 don't boot back into MIUI. After performing Step 5 quickly flash twrp and wipe MIUI and flash Custom rom.
Step 7 :- The bug will be gone.
I have made it easy.
If you guys have any Problem regarding this Pm or contact me on telegram my account @sk_ik_27400
Enjoy Flashing:fingers-crossed:

How many days have you checked? Actually after clean flash it happens after roughly one and a half day
One more thing, I am not officially unlocked, I use twrp with locked bootloader, should I try this?

arnabbandopadhyay said:
How many days have you checked? Actually after clean flash it happens after roughly one and a half day
One more thing, I am not officially unlocked, I use twrp with locked bootloader, should I try this?
Click to expand...
Click to collapse
i can 100 percent guarantee it will work i tried about 2 to 3 weeks no issues.
if u are unofficially unlocked then then i would recommend unlock officially using china dev fastboot rom because for many global dev or stable doesnt work
by the way u can if u flash with unofficialy unlocked bootloader then u will be stuck simply do is first of all flash all clean and lock then but remember use that fastboot rom which is recommended for unlocking unofficially rather than latest. then unlock its bootloader then on bootloader flash same image files i have said in above thread simple. also kindly check thread for unnoficial unlocking. http://en.miui.com/thread-345728-1-1.html
tap thanks if helped

Ishaan Kaushal said:
i can 100 percent guarantee it will work i tried about 2 to 3 weeks no issues.
if u are unofficially unlocked then then i would recommend unlock officially using china dev fastboot rom because for many global dev or stable doesnt work
by the way u can if u flash with unofficialy unlocked bootloader then u will be stuck simply do is first of all flash all clean and lock then but remember use that fastboot rom which is recommended for unlocking unofficially rather than latest. then unlock its bootloader then on bootloader flash same image files i have said in above thread simple. also kindly check thread for unnoficial unlocking. http://en.miui.com/thread-345728-1-1.html
tap thanks if helped
Click to expand...
Click to collapse
after doing all, should I wipe all dalvik, system, data, cache, internl before flashing oreo rom?

arnabbandopadhyay said:
after doing all, should I wipe all dalvik, system, data, cache, internl before flashing oreo rom?
Click to expand...
Click to collapse
yes after flashing image files from bootloader simply flash twrp and wipe everything and flash any oreo rom but remember once check in twrp recent screen that there is no warning regarding encrption

It was probably magisk issue
nathanchance said:
also @D-m-x (and everyone else), please try this Magisk build (it can be installed in the modules tab in Magisk Manager)
https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
It includes a commit that should fix all of the weird issues with Magisk like the PIN not being accepted after a reboot or the phone getting stuck at the Google logo with the progress bar. The root cause is services crashing during the boot chain and either causing deadlock or lack of functionality. It's entirely possible that a service crashed during boot and started causing issues.
Click to expand...
Click to collapse
Please refer to this post if you have magisk installed. thanks to @nathanchance

Ishaan Kaushal said:
yes after flashing image files from bootloader simply flash twrp and wipe everything and flash any oreo rom but remember once check in twrp recent screen that there is no warning regarding encrption
Click to expand...
Click to collapse
No decryption related message in twrp. I did all qnd will report you back after couple of days, whether is it fixed or not.

arnabbandopadhyay said:
No decryption related message in twrp. I did all qnd will report you back after couple of days, whether is it fixed or not.
Click to expand...
Click to collapse
ok :good:

Dims_Camper said:
Please refer to this post if you have magisk installed. thanks to @nathanchance
Click to expand...
Click to collapse
ok i tried all magisk version but i was fed up with this bug i dont know whether ur method works or not but i know this bug happens due to encryption on userdata. i dont think ur method will because magisk is universal and if problem is related to magisk then it should have happened with many devices not kenzo only
by the way thanks if ever faced again that bug i will try your method:laugh:

Ishaan Kaushal said:
ok :good:
Click to expand...
Click to collapse
On 1st reboot device asking " enter your password to start android", I tried to enter twrp, same thing happens, asking for password.

arnabbandopadhyay said:
On 1st reboot device asking " enter your password to start android", I tried to enter twrp, same thing happens, asking for password.
Click to expand...
Click to collapse
do u use telegram? if yes pm tag mentioned above in thread else send a screenshot of it

Ishaan Kaushal said:
do u use telegram? if yes pm tag mentioned above in thread else send a screenshot of it
Click to expand...
Click to collapse
I use but coudn't start my phone now, I am uploading pic

Ishaan Kaushal said:
ok i tried all magisk version but i was fed up with this bug i dont know whether ur method works or not but i know this bug happens due to encryption on userdata. i dont think ur method will because magisk is universal and if problem is related to magisk then it should have happened with many devices not kenzo only
by the way thanks if ever faced again that bug i will try your method:laugh:
Click to expand...
Click to collapse
i'm referring a post on pixel 2 thread, it's not only kenzo things apparently.

arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
i am not able to see any screenshots attach again

Dims_Camper said:
i'm referring a post on pixel 2 thread, it's not only kenzo things apparently.
Click to expand...
Click to collapse
ok:good:

arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
which rom u flashed?
before doing the method i suggested did u had your set a lockscreen password?
if yes simply enter that password and check else from boot loader enter followimg commands from cmd fastboot erase persist
the again flash persist using fastboot and then reboot to rom

Ishaan Kaushal said:
which rom u flashed?
before doing the method i suggested did u had your set a lockscreen password?
if yes simply enter that password and check else from boot loader enter followimg commands from cmd fastboot erase persist
the again flash persist using fastboot and then reboot to rom
Click to expand...
Click to collapse
I flashed cardinal. I never set any lockscreen password or pin, only a set a pattern.
I couldn't flash persist from fastboot, as I am unofficially unlocked, I need to flash only using mi flash in edl mode.
Unlocking bootloader officially is a harrassment, always getting "couldn't add your account: error 20075" something like that

arnabbandopadhyay said:
I flashed cardinal. I never set any lockscreen password or pin, only a set a pattern.
I couldn't flash persist from fastboot, as I am unofficially unlocked, I need to flash only using mi flash in edl mode.
Unlocking bootloader officially is a harrassment, always getting "couldn't add your account: error 20075" something like that
Click to expand...
Click to collapse
bro its better u contact me on telegram it will better to help Your there

arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
Your device is encrypted!!!
Format data through recovery.

nilesh8343 said:
Your device is encrypted!!!
Format data through recovery.
Click to expand...
Click to collapse
doing this only produces lock screen bug

[Solved]MiA1 shutdown after Booting UP

Hello guys,
I am providing Log-cat(Removed) for issue present.
Only thing I am think of is that I have restored EIS,Modem,Android Secure,persist from TWRP recovery than this started
For current situation this is stock Rom flashed with Mi Flash tool.
Also lineage OS 15.1 shutdown before showing Bluetooth stopped.
Any idea how to solve this?
or I have to visit Mi Service store?
In last few line in logcat there is something related to Bluetooth.

Abhaysinh said:
Hello guys,
I am providing Log-cat for issue present.
Only thing I am think of is that I have restored EIS,Modem,Android Secure,persist from TWRP recovery than this started
For current situation this is stock Rom flashed with Mi Flash tool.
Also lineage OS 15.1 shutdown before showing Bluetooth stopped.
Any idea how to solve this?
or I have to visit Mi Service store?
In last few line in logcat there is something related to Bluetooth.
https://drive.google.com/file/d/1TWCzAFWQzNAfDi3xQN16M3AlpYowlz6E/view?usp=sharing
Click to expand...
Click to collapse
It's never a good idea to restore data because the stock rom has encrypted data, so once you restore stock rom with twrp you'll end up in a bootloop (happened to me). All I could think of is for you to reflash with mi flash tool.

WhatzIt2Ya said:
It's never a good idea to restore data because the stock rom has encrypted data, so once you restore stock rom with twrp you'll end up in a bootloop (happened to me). All I could think of is for you to reflash with mi flash tool.
Click to expand...
Click to collapse
Yes bro, I have done it, It's just unfortunate that it didn't work in my case.

this might help you
Abhaysinh said:
Yes bro, I have done it, It's just unfortunate that it didn't work in my case.
Click to expand...
Click to collapse
I have encountered that same problem last June as i returned to stock in preparation of android 9, this is what i did
1. using MiFlash to flash - tissot_images_V9.5.4.0.ODHMIFA_20180226.0000.00_8.0_5773957dcd.tgz - in fastboot
2. i followed Method 2: (skipping to step 3) as described in this link - https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restrore-persist-partition-t3765643
3. i used this persist.img instead - https://drive.google.com/open?id=1SyzQsyCv_dfxrOUYetG-dtx3RW_4p9H6
4. reboot - hoping that your device will not restart again
5. flash your desired rom as you wish
Hope this helps - it took me almost 2 weeks to crack this case. This could help you also
After that incident I continued to flash other roms - right now im on liquidremix
Goodluck

charlesco29.cc said:
I have encountered that same problem last June as i returned to stock in preparation of android 9, this is what i did
1. using MiFlash to flash - tissot_images_V9.5.4.0.ODHMIFA_20180226.0000.00_8.0_5773957dcd.tgz - in fastboot
2. i followed Method 2: (skipping to step 3) as described in this link - https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restrore-persist-partition-t3765643
3. i used this persist.img instead - https://drive.google.com/open?id=1SyzQsyCv_dfxrOUYetG-dtx3RW_4p9H6
4. reboot - hoping that your device will not restart again
5. flash your desired rom as you wish
Hope this helps - it took me almost 2 weeks to crack this case. This could help you also
After that incident I continued to flash other roms - right now im on liquidremix
Goodluck
Click to expand...
Click to collapse
Thanks bro.
I directly flash persist.img from latest global firmware.
It's worked.:good:

Abhaysinh said:
Thanks bro.
I directly flash persist.img from latest global firmware.
It's worked.:good:
Click to expand...
Click to collapse
Glad I can help