Related
Oneplus has Screwed a lot of things between 3.5.2 AND 3.2.6..!! I wanted to try newest version of RR released by Blackjubel. But had issues.
Took me 5 minutes figure out things and decided to share it here:
IMPORTANT POST..!!! READ..!!! Credit for firmware files to @davidxantos
For people coming from 3.5.2 or 3.2.6
I am making a very important post. This is meant for all those who are using latest community build of Oneplus 3 and want to try another rom. You will not be able to do so as the twrp you are using will not flash roms completely and the firmware of community build will not let you flash the latest build of twrp. So here is what you need to do.
READ CAREFULLY:
STEP 1 : Grab firmware for 3.2.6 from this link and flash. flashing this will BREAK your fingerprint sensor. WAIT read on.
https://drive.google.com/…/0ByD3oqJ_...0;/view…
STEP 2: Now flash latest twrp 3.0.2.1 . Now you are on the latest twrp.
STEP 3: Now Flash firmware for 3.2.4 from this link. YOU HAVE your finger print sensor back..!
https://drive.google.com/…/0ByD3oqJ_...0;/view…
Now you have the latest twrp again and also can flash anything you want to..!!
Thanks to Oneplus for screwing this..!
Thanks but 3. 2.6 files do not found
No link works!
Just go find another link if these here don't work ...
There is a thread with all official firmwares. Or just use Google.
Sent from my OnePlus 3 using Tapatalk
3.2.4 https://drive.google.com/file/d/0ByD3oqJ_uj0VWjVMbmZoZS1kejg/view
3.2.6 https://drive.google.com/file/d/0ByD3oqJ_uj0VZUFjblBSbEVNRGs/view?usp=sharing
XDA app screwed the links
I tried but i bricked the phone. I cani only restore with the Qualcomm tool but now im stuck on the oxygen 3.1.2 and every time that flash any rom or OTA i brick the phone
gelomc said:
I tried but i bricked the phone. I cani only restore with the Qualcomm tool but now im stuck on the oxygen 3.1.2 and every time that flash any rom or OTA i brick the phone
Click to expand...
Click to collapse
This is strange..
gelomc said:
I tried but i bricked the phone. I cani only restore with the Qualcomm tool but now im stuck on the oxygen 3.1.2 and every time that flash any rom or OTA i brick the phone
Click to expand...
Click to collapse
Could it be that your bootloader is now locked again after using the unbrick tool?
DavidXanatos said:
Could it be that your bootloader is now locked again after using the unbrick tool?
Click to expand...
Click to collapse
No it's unlocked i checked
---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
geekynoob said:
This is strange..
Click to expand...
Click to collapse
I know...
I was on 3.2.6 after the OTA. I installed TWRP 3.0.2.1 and re-rooted it. I then took a backup and proceeded to flash RR 5.7.4. Broken fingerprint scanner/home button.
First, does anyone know why this happens? Can it be fixed?
In the meantime, do we need to revert to 3.2.4 to be able to install other roms and not break the the fps/hb?
Can anyone point me to a TWRP flashable version of 3.2.4? <-- Got this, Thanks.
Thanks in advance.
Edit to add below
I did what was detailed in the OP from stock rooted 3.2.6. I flashed the 3.2.6 firmware from TWRP. Rebooted to bootloader. Flashed TWRP 3.0.2.1 via fastboot. Flashed 3.2.4 firmware from TWRP. FPS/HB broken.
Did I miss something?
Reflashed 3.2.6 firmware on a hunch. FPS/HB working again.
My goal is to get to RR 5.7.4 with a working FPS/HB. Any ideas?
Thanks again.
EdHicks said:
I was on 3.2.6 after the OTA. I installed TWRP 3.0.2.1 and re-rooted it. I then took a backup and proceeded to flash RR 5.7.4. Broken fingerprint scanner/home button.
First, does anyone know why this happens? Can it be fixed?
In the meantime, do we need to revert to 3.2.4 to be able to install other roms and not break the the fps/hb?
Can anyone point me to a TWRP flashable version of 3.2.4? <-- Got this, Thanks.
Thanks in advance.
Edit to add below
I did what was detailed in the OP from stock rooted 3.2.6. I flashed the 3.2.6 firmware from TWRP. Rebooted to bootloader. Flashed TWRP 3.0.2.1 via fastboot. Flashed 3.2.4 firmware from TWRP. FPS/HB broken.
Did I miss something?
Reflashed 3.2.6 firmware on a hunch. FPS/HB working again.
My goal is to get to RR 5.7.4 with a working FPS/HB. Any ideas?
Thanks again.
Click to expand...
Click to collapse
It's easy mate..
Flash rr and then flash the 3.2.4 fw.. As u have a good twrp now.. Simple..
geekynoob said:
Oneplus has Screwed a lot of things between 3.5.2 AND 3.2.6..!! I wanted to try newest version of RR released by Blackjubel. But had issues.
Took me 5 minutes figure out things and decided to share it here:
IMPORTANT POST..!!! READ..!!! Credit for firmware files to @davidxantos
For people coming from 3.5.2 or 3.2.6
I am making a very important post. This is meant for all those who are using latest community build of Oneplus 3 and want to try another rom. You will not be able to do so as the twrp you are using will not flash roms completely and the firmware of community build will not let you flash the latest build of twrp. So here is what you need to do.
READ CAREFULLY:
STEP 1 : Grab firmware for 3.2.6 from this link and flash. flashing this will BREAK your fingerprint sensor. WAIT read on.
https://drive.google.com/â?¦/0ByD3oqJ_...0;/viewâ?¦
STEP 2: Now flash latest twrp 3.0.2.1 . Now you are on the latest twrp.
STEP 3: Now Flash firmware for 3.2.4 from this link. YOU HAVE your finger print sensor back..!
https://drive.google.com/â?¦/0ByD3oqJ_...0;/viewâ?¦
Now you have the latest twrp again and also can flash anything you want to..!!
Thanks to Oneplus for screwing this..!
Click to expand...
Click to collapse
In short, we cannot flash official twrp via modified twrp? Can't we just flash 3.2.4 without flashing 3.2.6 firmware?
z31416 said:
In short, we cannot flash official twrp via modified twrp? Can't we just flash 3.2.4 without flashing 3.2.6 firmware?
Click to expand...
Click to collapse
Nice u will get a black screen..
geekynoob said:
Nice u will get a black screen..
Click to expand...
Click to collapse
Thanks for this. I'm about to flash 3.2.4 fw only.
Good thing I saw this thread.
So step by step procedure if we wamt to flash other roms are:
-reboot to recovery (modifoed twrp)
-wipe
-flash 3.2.6 fw via modified twrp
-flash/install official twrp.img
-flash 3.2.4 fw
-flash rom etc
-finally reboot?
i'm using multi rom with FOS 1.5.1 as primary and whenever i flash RR(Flashing 3.2.4 firmware before and after too) and custom rom, FPS/home button not recognised.
what am i doing wrong, although multirom does have individual space why cant the older firmware doesnt work. everything except the home button is working fine.
can anyone explain how it works.
z31416 said:
Thanks for this. I'm about to flash 3.2.4 fw only.
Good thing I saw this thread.
So step by step procedure if we wamt to flash other roms are:
-wipe
-flash 3.2.6 fw via modified twrp
-flash/install official twrp.img
-flash 3.2.4 fw
-flash rom etc
-finally reboot?
Click to expand...
Click to collapse
Modded twrp can be used to flash 3.2.6 or 3.5.2 oos.. Now if u want to go back.. Using the modded twrp flash the 3.2.4 files.. Just reboot recovery now flash non modded twrp as u have 3.2.4 files official twrp will work.. And then flash any rom u want..
green. said:
i'm using multi rom with FOS 1.5.1 as primary and whenever i flash RR(Flashing 3.2.4 firmware before and after too) and custom rom, FPS/home button not recognised.
what am i doing wrong, although multirom does have individual space why cant the older firmware doesnt work. everything except the home button is working fine.
can anyone explain how it works.
Click to expand...
Click to collapse
Multi rom cannot distinguish firmware files.. They are core files.. So fp won't work..
geekynoob said:
Multi rom cannot distinguish firmware files.. They are core files.. So fp won't work..
Click to expand...
Click to collapse
okay, so the developer have to include the firmware in their roms in future build, thats how it works, right?
and while experimenting i flashed OOS 3.2.4 firmware but FPS working fine in FOS 1.5.1. how come it is?
z31416 said:
Thanks for this. I'm about to flash 3.2.4 fw only.
Good thing I saw this thread.
So step by step procedure if we wamt to flash other roms are:
-reboot to recovery (modifoed twrp)
-wipe
-flash 3.2.6 fw via modified twrp
-flash/install official twrp.img
-flash 3.2.4 fw
-flash rom etc
-finally reboot?
Click to expand...
Click to collapse
This will do it. It's how I got going. I went from stock rooted 3.2.6 OOS to RR 5.7.4.
Thanks for putting to words for others.
green. said:
okay, so the developer have to include the firmware in their roms in future build, thats how it works, right?
and while experimenting i flashed OOS 3.2.4 firmware but FPS working fine in FOS 1.5.1. how come it is?
Click to expand...
Click to collapse
I've done a bit of Dev.. But i am not sure about ur statement.. .. And cm based roms don't have fw files.. Feel like a noob lol..
Update: A working solution is listed below for reference.
A detailed tutorial for encrypted and rooted Nougat OOS users on how to flash Oreo OxygenOS without running into the infamous boot loop issue.
Step 1: Remove all fingerprint & pin from the device
Step 2: Backup everything on your PC/Laptop
Step 3: Reboot the device to TWRP bootloader
Step 4: Using a PC/Laptop, flash Blu_Spark TWRP via ADB command
Step 5: Reboot device to TWRP
Step 6: Wipe dalvik, cache, system & internal partition
Step 7: Format device
Step 8: Copy Oreo Rom & no_verity_mod file onto your device
Step 9: Flash Oreo under TWRP
Step 10: Flash TWRP again
Step 11: Reboot to recovery again
Step 12: Flash Magisk Beta for root (I used Magisk beta 14.5)
Step 13: Flash no_verity_mod file
Step 14: Reboot into Oreo Oxygen OS
Your device is now decrypted, rooted and running the latest stable Oreo OxygenOS build.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Seeing as a couple of forum members have messaged me regarding the official update of Android Oreo, I would like to make a proper discussion thread for it.
I just want to make it clear that HatRiGt has made an outstanding effort by making a tutorial thread. -> ([OFFICIAL] [Stable Oreo 8 ] Oxygen OS 5.0 Update [Tutorial-Root] [Mirror] by HatRiGt)
With that said, I believe the title is somewhat misleading. Since a lot of members are under the impression that this Oreo update will be a simple and straightforward process like all previous Nougat updates, except for it's not.
Stock OxygenOS
Rooted with Magisk v14
TWRP Recovery
Device already encrypted
Almost everyone with the device configuration listed above has run into some sort of serious issues, such as boot loop, file system decrypted/corrupted, or a complete data loss.
So far, it seems like the few groups of members that have managed to update their device without any data loss are either users that have flashed the Oreo Beta rom, or users with a non-rooted & stock recovery device. Almost everyone else is facing some form of issues.
I understand that some people have suggested that rooted users should first format the internal storage, before proceeding with the Oreo update. I personally feel that it is an inconvenient method of OS update, since many of us have a huge collection of photos, media files and app settings etc... to worry about.
The purpose of this thread is to address the aforementioned problem for rooted OOS users and to come up with a solution, so that everyone can enjoy this latest stable release of Android Oreo.
Any comments or thoughts are welcomed.
Maybe a stupid idea, but I am a bit noobish in this. Running stock 4.5.15, rooted, K2 TWRP and Magisk.
Is it not an option to just flash stock recovery (via ADB or Root Toolcase), then remove/deinstall Magisk and use the OTA update? After that flash Blue Spark via ADB, reflash Magisk and be good to go?
Unfortunately this is my daily driver company phone so I haven't the time to experiment with it at the moment.
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Malcol13 said:
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Click to expand...
Click to collapse
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
DionysosD said:
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
Click to expand...
Click to collapse
I saw the same thing. Unable to copy the zip file until I did the full wipe, which means no chance of recovering what was on it, but I'm cutting my losses.
I'm now stuck on the configuration stage, it's just sitting on "Just a sec..." for forever it would seem. Trying to update on Christmas day was a bad decision.
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
fards said:
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I had the same idea, encrypted, rooted (no system modifications) and running twrp, I flashed stock OP5 recovery, and updated through the ota and ended up in a bootloop.
I did a nandroid to a usb before updating, but I still lost all internal storage files
so...the no verity is only for decrypted users right?
fards said:
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
igoorsoouza said:
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
Click to expand...
Click to collapse
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Are you sure flashing Open beta2 won't compromise the internal storage? I bet no one affords to loose previous photos, apps, settings, etc without full backup.
I've triyed this. All good till i flash 5.0 & Magisk & no verity....
Hello there and Merry Christmas.
I faced to this issue too, fortunately before to update to Oreo. I made a full backup of my data.
My OP5 was running under Oxygen OS 4.5.15 Nougat 7.1.1
Rooted with Magisk V14.5
TWRP Blue_Spark 3.1.1
First I have updated my TWRP to Blue_Spark 3.2
And then I've installed Oreo Oxygen OS 5.0 from TWRP with the full zip.
After the update, my op5 has been bricked and locked on blank black screen with a blue led.
To unbrick my phone I used a tiers softwate to install Hydrogen OS first.
After that I could installed TWRP Blue_Spark 3.2 and then flash to the full zip Oreo Oxygen OS 5.0
My OP5 works as well but...
Right now I'm blocked, Google who usually sends an SMS, does not offer me. Only the authentificatorator or the security code. : /
Be careful, print a Google code to access your account when you go to install Oreo.
I'm waiting for Google to do the right thing.
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
1) What is that "no-verity" file?
2) Isn't the regular TWRP 3.2.0 good with Oreo?
MadCow809 said:
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Click to expand...
Click to collapse
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
BenSow said:
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
Click to expand...
Click to collapse
I think it's possible to flash the Oreo Beta without a full wipe. And yeah, I've got way too much stuff on my device, so I can't afford to wipe my storage.
MadCow809 said:
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
Click to expand...
Click to collapse
I never suggested either.
Oneplus don't test using twrp or using root.
Their prescribed ota route, as pretty much every other OEM, is unmodified system partition using stock bootloader.
Twrp or root will affect those and can cause bootloops.
Obviously there's a chance with so much diversity in installs that there can be an issue arises.
raboliot said:
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5/how-to/guide-restore-data-stuck-bootloop-n-o-t3724515
Read it all.
I have a Encrypted phone and I was able to recover all.
Actually I was able to restore my Nandroid backup.
Hey guys, i am on miui global 10 8.9.20 beta and i have already unlocked the bootloader. (I just want some tips because i bootlocked my santoni at the first attempt )
So.. what recovery and method i should use as i only want magisk and audio mods.
NFS420 said:
Hey guys, i am on miui global 10 8.9.20 beta and i have already unlocked the bootloader. (I just want some tips because i bootlocked my santoni at the first attempt )
So.. what recovery and method i should use as i only want magisk and audio mods.
Click to expand...
Click to collapse
I suppose you mean bootlooped not "bootlocked" because it is already unlocked, right?
A custom recovery with official MIUI requires a boot image fix and you'd better simply install this https://xiaomi.eu/community/threads/8-9-20.46616/ as it works without any issues and you'll be able to easily mod it any way you want.
:good:
Use Official twrp recovery, download it from here -> https://twrp.me/xiaomi/xiaomiredmi4x.html
Magisk manager -> https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
there are several audio mods available, i do not use any so can not suggest any.
k23m said:
I suppose you mean bootlooped not "bootlocked" because it is already unlocked, right?
A custom recovery with official MIUI requires a boot image fix and you'd better simply install this https://xiaomi.eu/community/threads/8-9-20.46616/ as it works without any issues and you'll be able to easily mod it any way you want.
:good:
Click to expand...
Click to collapse
yup it bootlooped not locked(my bad), the bootloader is unlocked.
And would i lose all my data if i flashed this on top of my global rom and can i restore my data via restore from a backup in twrp ?
NFS420 said:
yup it bootlooped not locked(my bad), the bootloader is unlocked.
And would i lose all my data if i flashed this on top of my global rom and can i restore my data via restore from a backup in twrp ?
Click to expand...
Click to collapse
You will not lose anything if you try a "dirty flash". Wipe only advanced-cache/dalvik (don't wipe data!) and everything should work if you use "xiaomi.eu_multi_HM4X_8.9.20_v10-7.1.zip" which is exactly the same MIUI version as the official.
A "dirty flash" while preserving data/setup may not be always successful but you can restore your backup later should something go wrong.
Normal flash is recommended but you'd have to deal with app re-installations.
Hello mi6x user, here I share direct link last ROM 10.2.3.0 for Mi6x
This is China build android 8.1, flash with TWRP or Miui recovery. You can use this for bootloop device.
Download:
V 10.2.3.0.ODCCNXM:good:
may it help, thanks :victory:
Alvian_P said:
Hello mi6x user, here I share direct link last ROM 10.2.3.0 for Mi6x
This is China build android 8.1, flash with TWRP.
Download:
V 10.2.3.0.ODCCNXM:good:
may it help, thanks :victory:
Click to expand...
Click to collapse
is it possible to flash that being arb 4?
stevedat said:
is it possible to flash that being arb 4?
Click to expand...
Click to collapse
Yes. My phone also Arb4.
Alvian_P said:
Yes. My phone also Arb4.
Click to expand...
Click to collapse
After flashed this stable version via twrp, is it possible to flash miui dev zip via miui recovery of updater. especially miui pie beta dev and get rid of twrp, become a mi6x instead
stevedat said:
After flashed this stable version via twrp, is it possible to flash miui dev zip via miui recovery of updater. especially miui pie beta dev and get rid of twrp, become a mi6x instead
Click to expand...
Click to collapse
Is possible I think, before change to pie, make sure .zip file of pie must include kernel. I guess recommend flash via miui recovery / TWRP and wipe data. Because update different version of Android, 8.1 to 9.0
I never try Pie because my Arb=4. U can try, if bootloop you can flash this stable version again
Alvian_P said:
Hello mi6x user, here I share direct link last ROM 10.2.3.0 for Mi6x
This is China build android 8.1, flash with TWRP or Miui recovery. You can use this for bootloop device.
Download:
V 10.2.3.0.ODCCNXM:good:
may it help, thanks :victory:
Click to expand...
Click to collapse
Help, Do you have stock boot.img of this rom ?
Because my phone get bootloop when uninstal magisk.
Saud Salomo said:
Help, Do you have stock boot.img of this rom ?
Because my phone get bootloop when uninstal magisk.
Click to expand...
Click to collapse
Its include in .zip files
Seeing as someone finally created a forum with some relevance to miui does anyone know ruffly when xiaomi will be releasing stable update for miui 10 pie , because as we know the beta has arrived for many devs
Quantumkk123 said:
Seeing as someone finally created a forum with some relevance to miui does anyone know ruffly when xiaomi will be releasing stable update for miui 10 pie , because as we know the beta has arrived for many devs
Click to expand...
Click to collapse
There's a miui 10 v9.3.14 in the forum, I'm using it and everything is working fine, very smooth.
I have a mia2 converted to mi6x.. i had xiaomi. eu miui 10 and everything was fine.. i try to update to pie, delete firmware folder but i had bootloop.. so i flash it with firmware file and now i have arb4... in the past i had forgot to delete 1-2 times but arb was stayed at arb2... so.. if some moment i want fo go back to android one, is there a way to do it.. (only for warranty reasons, or to sell tbe phone)
ktlk21 said:
I have a mia2 converted to mi6x.. i had xiaomi. eu miui 10 and everything was fine.. i try to update to pie, delete firmware folder but i had bootloop.. so i flash it with firmware file and now i have arb4... in the past i had forgot to delete 1-2 times but arb was stayed at arb2... so.. if some moment i want fo go back to android one, is there a way to do it.. (only for warranty reasons, or to sell tbe phone)
Click to expand...
Click to collapse
Yes there is a way you need to wait for mi a2 to release an arb 4 rom only way
What will be ARB level after installing this MIUI 10.2.3 or 10.2.5 ODCCNXM ROM?
Currently I have MIUI stable stock ROM 9.6.6.0. If I upgrade it to 10.2.5.0, than can I downgrade to MIUI stable 9.6.60 again?
Thanks
coolman7 said:
What will be ARB level after installing this MIUI 10.2.3 or 10.2.5 ODCCNXM ROM?
Currently I have MIUI stable stock ROM 9.6.6.0. If I upgrade it to 10.2.5.0, than can I downgrade to MIUI stable 9.6.60 again?
Thanks
Click to expand...
Click to collapse
Yeah
---------- Post added at 08:43 PM ---------- Previous post was at 08:43 PM ----------
Quantumkk123 said:
Yeah
Click to expand...
Click to collapse
Oh wait no lol because of arb 4
Quantumkk123 said:
Yeah
---------- Post added at 08:43 PM ---------- Previous post was at 08:43 PM ----------
Oh wait no lol because of arb 4
Click to expand...
Click to collapse
My current ARB level is 4 with MIUI 9.6.6. Will I get brick if I will downgrade from 10.2.5 to 9.6.6?
ktlk21 said:
I have a mia2 converted to mi6x.. i had xiaomi. eu miui 10 and everything was fine.. i try to update to pie, delete firmware folder but i had bootloop.. so i flash it with firmware file and now i have arb4... in the past i had forgot to delete 1-2 times but arb was stayed at arb2... so.. if some moment i want fo go back to android one, is there a way to do it.. (only for warranty reasons, or to sell tbe phone)
Click to expand...
Click to collapse
You can I found the method in a Russian website, but the Bootloader will remains on 6X. But technically you can install AndroidONE again, btw for updating you need to use alternative ways. ( Due to the 6X Bootloader)
Are there any TWRP that can decrypt storage of MIUI 10.2.5 stock China ROM?
coolman7 said:
Are there any TWRP that can decrypt storage of MIUI 10.2.5 stock China ROM?
Click to expand...
Click to collapse
Format data on twrp
Alvian_P said:
Format data on twrp
Click to expand...
Click to collapse
I tried but did not help. When I reboot system, MIUI 10 formats storage with encryption again. I tried following scenarios:
1) Opened TWRP and format data. Reboot system
2) Opened TWRP and format data. Reboot to TWRP again. Reboot to system
3) Opened TWRP and format data. Reboot to TWRP again. Flash magisk. Reboot to system
All has same affect. and TWRP asks password again and again.
coolman7 said:
I tried but did not help. When I reboot system, MIUI 10 formats storage with encryption again. I tried following scenarios:
1) Opened TWRP and format data. Reboot system
2) Opened TWRP and format data. Reboot to TWRP again. Reboot to system
3) Opened TWRP and format data. Reboot to TWRP again. Flash magisk. Reboot to system
All has same affect. and TWRP asks password again and again.
Click to expand...
Click to collapse
Your Data partition can mount in TWRP?
if TWRP ask password, probably because install TWRP with active password lockscreen in system. When install recovery make sure deactive lockscreen pasword first
Try this recovery: https://sourceforge.net/projects/pitchblack-twrp/files/wayne/
Alvian_P said:
Your Data partition can mount in TWRP?
if TWRP ask password, probably because install TWRP with active password lockscreen in system. When install recovery make sure deactive lockscreen pasword first
Try this recovery: https://sourceforge.net/projects/pitchblack-twrp/files/wayne/
Click to expand...
Click to collapse
I can't mount data partition in TWRP. TWRP asks for password. I did not flash TWRP. I just boot TWRP from fastboot when I need with fastboot boot twrp.img command. I tried pitchblack recovery but the result is same.
{Mod edit}
All sources gonna be linked here within two days
We will share all ours sources for team win as contribution to development on XDA
SOURCES: SOON
Is Decrypt working in oxygen os with this recovery?
Jackass94 said:
Is Decrypt working in oxygen os with this recovery?
Click to expand...
Click to collapse
No, sorry. Its still work in progress. Decryption is working only on custom roms for now
Does this TWRP stick once flashed, or device defaults back to stock recovery once flashing is over?
elmor0 said:
Does this TWRP stick once flashed, or device defaults back to stock recovery once flashing is over?
Click to expand...
Click to collapse
Depends on what your flashing
Custom ROMs
I will install in OOs Stock 10.0.8... Thanks.
jotha.dx said:
I will install in OOs Stock 10.0.8... Thanks.
Click to expand...
Click to collapse
It doesnt work with stock OOS AFAIK
EugenStanis said:
It doesnt work with stock OOS AFAIK
Click to expand...
Click to collapse
Afh... Thank you... I won't even try then....
Sent from my OnePlus7TPro Global using XDA Labs
I am waiting the custom oos
ricky886 said:
I am waiting the custom oos
Click to expand...
Click to collapse
What is that supposed to mean?
this doesn't decrypt SDcard aka "Data" iam on Resurrection remix any solution? i want to remove a magisk module that caused a bootloop
mastrok said:
this doesn't decrypt SDcard aka "Data" iam on Resurrection remix any solution? i want to remove a magisk module that caused a bootloop
Click to expand...
Click to collapse
Use the stock recovery with adb shell enabled.
Or flash the stock boot.img, enable adb debugging and flash the Magisk patched boot.img.
If adb debugging is enabled skip the upper part, use a PC and enter:
Code:
adb wait-for-device shell magisk --remove-modules
Done.
mastrok said:
this doesn't decrypt SDcard aka "Data" iam on Resurrection remix any solution? i want to remove a magisk module that caused a bootloop
Click to expand...
Click to collapse
alright i needed to have working system for this to decrypt. i installed the stock boot image system worked. then restarted now it decrypts
i can confirm this really works like back in the days when i used it in samsung galaxies
I van confirm that this works. It's installed and I made a backup with it. Nice work!!
EugenStanis said:
It doesnt work with stock OOS AFAIK
Click to expand...
Click to collapse
It does work
I have flashed the OOS 10.0.8 BA on OnePlus 7T PRO
I have cleared the phone with TOOL ALL IN ONE
I was in a bootloop when I have flashed the stock image
Then I have tried to wipe cache/data and it hasn't worked
Then I have made a full wipe through TOOL ALL IN ONE
In a magical way its worked. But I would like to test it to see what are the full steps to make it work. But I am sure that this has worked and I have now an operated Oneplus 7t Pro.
I think that its something about having 2 different OS in one smartphone and you have to clear it to delete the old.
But It is working
Alexisd1 said:
It does work
I have flashed the OOS 10.0.8 BA on OnePlus 7T PRO
I have cleared the phone with TOOL ALL IN ONE
I was in a bootloop when I have flashed the stock image
Then I have tried to wipe cache/data and it hasn't worked
Then I have made a full wipe through TOOL ALL IN ONE
In a magical way its worked. But I would like to test it to see what are the full steps to make it work. But I am sure that this has worked and I have now an operated Oneplus 7t Pro.
I think that its something about having 2 different OS in one smartphone and you have to clear it to delete the old.
But It is working
Click to expand...
Click to collapse
It DOES WORK but decryption is not working so it is useless
EugenStanis said:
It DOES WORK but decryption is not working so it is useless
Click to expand...
Click to collapse
Decryption isnt working in any TWRP right now. The official TWRP when will be out( I dont know when) it will have decryption. But in this TWRP i am focusing to the way of installing a stock OOS.You can just simply boot the twrp and not flash it. After flashing the stock OOS you can use the stock recovery that will be encrypted and you will not have any problem. Now we have these solutions or the harder solutions like flashing with adb commands etc.
Alexisd1 said:
Decryption isnt working in any TWRP right now. The official TWRP when will be out( I dont know when) it will have decryption. But in this TWRP i am focusing to the way of installing a stock OOS.You can just simply boot the twrp and not flash it. After flashing the stock OOS you can use the stock recovery that will be encrypted and you will not have any problem. Now we have these solutions or the harder solutions like flashing with adb commands etc.
Click to expand...
Click to collapse
You are wrong, decrpytion is working for me on this TWRP.