I`m having problems with booting into recovery on my OnePlus2.
This started after I did an update to OxygenOS 3.0 (beta) from my previously working TWRP.
OS itself is working, but I noticed that phone must be rerooted.. and here I found that Power + VolDown is not working anymore (phone is just stucked on 1+ logo).
OKay... I decided to reflash TWRP (who knows what may happened with it after update) but nothing helped. I tried different versions, even original OP2 recovery.. but result is always the same.
How I was trying to reflash:
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (31700 KB)...
OKAY [ 0.702s]
writing 'recovery'...
OKAY [ 0.248s]
finished. total time: 0.950s
but booting is always giving DTB error:
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.713s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.781s
I saw in other posts that dtb means broken image/etc, but I tried several and all were with the same result.
What else I can try? Please note that regular booting is working with no problems. The only problem I have is booting into recovery (with buttons and with fastboot).
Posted in wrong section. Should be in Q&A.
However to answer your question.
This has the same bootloader as H2OS Marshmallow. So, please TWRP users flash the way as mentioned below. Else you won't be able to boot into old twrp.
DOWNLOADS :-
recovery.img :- https://www.androidfilehost.com/?fid=24459283995297945
Step 1 :- Clean flash the ROM with new boootloader.
Step 2 :- From TWRP,go to Install Menu,click on Images button.
Step 3 :- Select the recovery.img you just downloaded.Select Recovery.Swipe to flash.
Step 4 :- From TWRP Home,reboot to recovery.
Step 5 :- Clean flash ROM with new bootloader again.
Step 6 :- Reboot into system !!!
Thanks and sorry for the wrong section.
Can you please give a bit more info on step 1 ? what rom to flash and how (current recovery is not working) ?
taha198 said:
Posted in wrong section. Should be in Q&A.
However to answer your question.
This has the same bootloader as H2OS Marshmallow. So, please TWRP users flash the way as mentioned below. Else you won't be able to boot into old twrp.
DOWNLOADS :-
recovery.img :- https://www.androidfilehost.com/?fid=24459283995297945
Step 1 :- Clean flash the ROM with new boootloader.
Step 2 :- From TWRP,go to Install Menu,click on Images button.
Step 3 :- Select the recovery.img you just downloaded.Select Recovery.Swipe to flash.
Step 4 :- From TWRP Home,reboot to recovery.
Step 5 :- Clean flash ROM with new bootloader again.
Step 6 :- Reboot into system !!!
Click to expand...
Click to collapse
Follow guide this guide
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Now it is clear. you gave me an instruction to what I should do to avoid the situation where I am now. but there is also another instruction how to fix my problem.
Thanks one again!
taha198 said:
Follow guide this guide
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
It seems you are flashing the wrong version of TWRP. The version you are flashing isn't going to work on OOS 3.0 Beta. You need specifically the H2-MM TWRP 3.0.0-1 version, which, like the previous posters listed can be downloaded here:
https://www.androidfilehost.com/?fid=24459283995297945
If you are flashing a version that you downloaded direct from TWRP's website, it won't work.
I tested different versions, including 3.0.x mentioned by you. all of them gave the same result.
Btw, the recovery tool in the link above already fixed my problem.
madferretx said:
It seems you are flashing the wrong version of TWRP. The version you are flashing isn't going to work on OOS 3.0 Beta. You need specifically the H2-MM TWRP 3.0.0-1 version, which, like the previous posters listed can be downloaded here:
https://www.androidfilehost.com/?fid=24459283995297945
If you are flashing a version that you downloaded direct from TWRP's website, it won't work.
Click to expand...
Click to collapse
Delphir said:
I tested different versions, including 3.0.x mentioned by you. all of them gave the same result.
Btw, the recovery tool in the link above already fixed my problem.
Click to expand...
Click to collapse
Could you describe exactly what did you do? At the link that you mention there is 3 methods and different recovery tools.
I followed "Method 1" from the link and then flashed TWRP recovery on top of it - this way it worked with no problems. Flashing TWRP (different versions) without this recovery tool was always unsuccessful.
Well, as long as you flash the chinese HydrogenOS version of TWRP you should get a bootable recover system.
Best regards
Peter
I recently rooted my OnePlus 2.
The bootloader is unlocked.
The twrp recovery was working fine till I flashed to oxygen os 2.0.0
Now the OnePlus2 is not booting into recovery.
There is a oxygen os update (3.5.8) available which shows in the system updates section in settings.
Can I update to this without the recovery??!
Will that help to go back to twrp recovery?!
Please help
Nandish C said:
I recently rooted my OnePlus 2.
The bootloader is unlocked.
The twrp recovery was working fine till I flashed to oxygen os 2.0.0
Now the OnePlus2 is not booting into recovery.
There is a oxygen os update (3.5.8) available which shows in the system updates section in settings.
Can I update to this without the recovery??!
Will that help to go back to twrp recovery?!
Please help
Click to expand...
Click to collapse
Flashing stock firmware will overwrite twrp, so always flash OOS and twrp after it in case you want to keep it, twrp can flash the twrp.img file, not only zips, I never used OOS2 but actually you should have stock recovery back by flashing OOS, it seems that something went wrong. Just flash twrp again, like the first time you did it, if you want to go back to stock including recovery flash OOS full zip again and reboot...
Only OOS will overwrite twrp, custom roms won't
Sent from my OnePlus 2 using XDA Labs
Related
So guys basically, I wanted to give F2FS a shot, I downloaded the recoveries that the thread told me to, flashed either of them using the fastboot flash boot filename.img
With both of them, and even the latest official TWRP I get this:
sending 'boot' (8182 KB)... OKAY [ 1.056s]
writing 'boot'... OKAY [ 0.182s]
finished. total time: 1.238s
and on my Bootloader screen I get the message FASTBOOT STATUS OKAY
So, you'd think all went fine.
Rebooting into recovery reveals that I have the exact same recovery as before, I've tried like 10 times and the result is always the same one
Are you sure the one you flashed is different to the previous one? Which recovery do you have now and which do you want to flash?
XxM4tzexX said:
Are you sure the one you flashed is different to the previous one? Which recovery do you have now and which do you want to flash?
Click to expand...
Click to collapse
I have TWRP 2.7.0.1 and I'm trying to flash either KT recovery or the latest TWRP 2.7.1.0, I'll try flashing CWM and then change back to one of those to see if I can manage to do that
fastboot boot filename.img worked and I managed to change my filesystems, I'll try creating the zip as the recovery keeps going reverting and 2.7.0.1 isn't able to read my partitions now, I'll update with the results and so far I just booted up and everything seems to be going well.
Edit: Ok, I DL'ed an official TWRP 2.7.1.0 zip and flashed it, my recovery updated successfully, however it isn't able to read my /cache or /data partitions, next, I replaced the recovery.img with the exact same img I used to convert to F2FS (the one provided here) and again booted into the functional recovery through fastboot boot filename.img, I flashed the new zip file and everything seemed to be fine, rebooting to recovery shows that the original TWRP 2.7.1.0 wasn't replaced as I'm unable to mount the data or cache partitions.
Also worth mentioning that using the TWRP manager from the playstore to try to flash .imgs does not work either
The fastboot method listed above is to flash a kernel not recovery, if your trying to flash a new recovery you run
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Fidelator said:
So guys basically, I wanted to give F2FS a shot, I downloaded the recoveries that the thread told me to, flashed either of them using the fastboot flash boot filename.img
Click to expand...
Click to collapse
fastboot flash recovery filename.img
uDude
When I try to flash TWRP (via "fastboot flash recovery twrp.img" then "fastboot boot twrp.img") I receive the following error:
Downloading 'boot.img'
OKAY [1.477s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.534s
I've tried manually booting it into recovery with power button and volume down but it just freezes on the oneplus logo where I have to turn off and on again.
Any help is greatly appreciated!
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
that link just saved me!
I tried this recovery (I had the same problem as the OP) but although I can boot into twrp, I get stuck on the oneplus logo if I try a normal boot?
Sent from my Nexus 9 using XDA-Developers mobile app
I managed to get it working by flashing CM after flashing the recovery.
Sent from my Nexus 9 using XDA-Developers mobile app
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
pitrus- said:
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
Click to expand...
Click to collapse
Actually, fastboot boot twrp.img boots the TWRP image without flashing it.
fastboot flash recovery twrp.img flashes the TWRP image to the recovery partition.
Both are valid commands and have their uses.
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.
Spannaa said:
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.
Click to expand...
Click to collapse
That's exactly what I meant to convey.
Similar problem while flashing recovery
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
bhanuodin said:
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
Click to expand...
Click to collapse
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
pitrus- said:
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
Click to expand...
Click to collapse
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
bhanuodin said:
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
Click to expand...
Click to collapse
The bootloader (also called fastboot) comes with the original ROM. In your case you're already on the newer bootloader since you flashed OOS3 which means you will have to flash recoverys and ROMs compatible with this newer bootloader.
This TWRP should be compatible
https://dl.twrp.me/oneplus2/twrp-3.0.2-1-oneplus2.img.html
Also you can't run ROMs not compatible with this newer bootloader (which means pretty much any ROM that's not using the official Cyanogenmod source tree for building). That is except for OOS3 or newest HOS of course since these are made for the newer bootloader.
However I would say the error message you get might be caused by bad cable, faulty driver setup, faulty fastboot tool version or in worst case damaged partition layout on phone. The last one can be fixed by the Qualcomm OOS2 factory restore solution.
Hi, i am having the same problem.
some background: I was on Oxygen OS 2.x.x, i wanted to upgrade to Exodus 6. I had the older version of TWRP. So I tryed to install the new twrp image within twrp. When i rebooted i couldnt boot into twrp, receiving the same error message as in OP title, when using fastboot.
Using the tool all in one toolkit I was able to flash stock recovery.
But I still cant flash Twrp.
I can still boot into system though.
Any advice? Thanks.
That explains why you're having problems. You're doing it the wrong way.
First you must upgrade the bootloader by either flashing the convert to Marshmallow zip file which also installs the correct TWRP for the new bootloader (easiest way). Or you could flash the latest official OOS3, then fastboot flash the latest TWRP and from there format system and flash the ROM that's using the newer bootloader.
Does that Link work with oneplus x also? Having same problem as Higgings when trying to install twrp and cyanogenmod.
thnx a lot for sharing
:good:
Higgings said:
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
Click to expand...
Click to collapse
So for some background, I was on EMUI 4.1 and successfully flashed to EMUI 5.
Then, I wanted to rollback so I flashed recovery again and stock firmware. I tried flashing with fastboot and didn't work. I tried using Huawei recovery 3-button method, no luck either.
Errors using fastboot flashing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system "F:\SYSTEM.img"
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445721 KB)...
OKAY [ 17.780s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 17.822s
Click to expand...
Click to collapse
Error with 3-button method:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Click to expand...
Click to collapse
When I was booting into Revolution recovery, I could not mount SD card and some other partitions so maybe that has something to do with the 3-button method problem... Furthermore, I don't know how to check which version exactly my phone is, all I know is that it was VNS-L31.
Now I'm stuck with a phone that is constantly rebooting so how do I proceed?
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Schlengge said:
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Click to expand...
Click to collapse
Have just solved the problem with the steps from here.
From my understanding, it seems that I lost almost everything, device info, OEM info, recovery... So no technique was working.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
As you say Schlengge, it is a matter of using the right files! Thanks. Problem solved.
I saw where someone said you could flash B20 bootloader and flash TWRP on Nougat, is this true? Is anyone working on a guide for Nougat TWRP and root. On another note I thought that I read that ZTE would be bringing Wifi calling for Nougat with carries such as T-Mobile? I was unable.to find it under options and assume that it is not possible, anyone have any idea about this.
Thanks
I have an unlocked BL and recently upgraded to Nougat, but when I try to reinstall TWRP via fastboot flash method, it fails. I have tried two different versions of TWRP 3.0.3-1 & 3.0.4-1. This is the message I get.
PS C:\adb> fastboot flash recovery twrp-3.0.4-1-a7.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.332s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.363s
Any ideas?
jim262 said:
I have an unlocked BL and recently upgraded to Nougat, but when I try to reinstall TWRP via fastboot flash method, it fails. I have tried two different versions of TWRP 3.0.3-1 & 3.0.4-1. This is the message I get.
PS C:\adb> fastboot flash recovery twrp-3.0.4-1-a7.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.332s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.363s
Any ideas?
Click to expand...
Click to collapse
I got TWRP 3.0.4 installed (as well as 3.0.3-1)... It installed sucessfully via Fastboot for me, I even flashed SU, but I couldn't get my phone to boot into the OS (tried with and without SU).......It just hung at the boot pre-boot screen (where it warns you the bootloader is unlocked). I'd restart it, and it always hangs at that screen..... Only way to fix it was to boot back into TWRP, revert back to B29 (using DrakenFX guide) and then update to Nougat again. I spent about 16 hours straight working on this on Tuesday, before I gave up and decided to keep it stock until a custom ROM comes out, soon (Z.A.D. v.4), hopefully?
I have an issue where I installed B15 but whenever I boot my phone, it hangs on the Linux Tux logo. Any fix?
xDaDeevellopar said:
I have an issue where I installed B15 but whenever I boot my phone, it hangs on the Linux Tux logo. Any fix?
Click to expand...
Click to collapse
You probably pushed the power button to "Start"? Try letting it sit there about 10-15 seconds, if it won't boot...This is the exact same problem I had. I had to go back to B29, then do the update again. There is now a B15 "return to stock" walk-through, that may be the quicker route.....But I know returning to B29, turning on OEM Unlock in Dev options and then taking the update via your SD card was what I did (3 times in one day).
Flash signed TWRP with tennear's tool (axon7tool):
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
https://we.tl/dv78KwQZCY
and then follow this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
3 files and 10 minutes of your time for TWRP + unlocked bootloader
bornlivedie said:
Flash signed TWRP with tennear's tool (axon7tool):
https://forum.xda-developers.com/axo...overy-t3514254
https://we.tl/dv78KwQZCY
and then follow this guide:
https://forum.xda-developers.com/axo...-stay-t3461165
3 files and 10 minutes of your time for TWRP + unlocked bootloader
Click to expand...
Click to collapse
Those 2 XDA links don't work, take me to a generic XDA 404 error page (on both)...the WeShare page worked.
tele_jas said:
Those 2 XDA links don't work, take me to a generic XDA 404 error page (on both)...the WeShare page worked.
Click to expand...
Click to collapse
That's because I copypasted lol
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
bornlivedie said:
That's because I copypasted lol
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Click to expand...
Click to collapse
If my bootloader is already unlocked, can I skip that part (the 2nd link)?? Or is it necessary?
tele_jas said:
If my bootloader is already unlocked, can I skip that part (the 2nd link)?? Or is it necessary?
Click to expand...
Click to collapse
Those steps are meant to unlock the bootloader.
You don't need any of it. You already have TWRP (skip step 1) and bootloader unlocked (skip step 2) so yeah...
What do you want exactly?
bornlivedie said:
Those steps are meant to unlock the bootloader.
You don't need any of it. You already have TWRP (skip step 1) and bootloader unlocked (skip step 2) so yeah...
What do you want exactly?
Click to expand...
Click to collapse
My bootloader is unlocked (back when ZTE actually provided the unlocking)....adb fastboot works on my phone as well and I've flashed TWRP (3.0.4 and 3.0.3-1) and it's booted into TWRP, but I cannot boot into the actual OS...My phone goes all black and just hangs there, I think this may be booting directly into EDL mode and not the OS? I can plug my phone into the computer and my computer makes noises as if a USB device has been attached, but my screen is completely black. If I push the start button while the phone is booting (to bypass the bootloader is unlocked warning screen), I boot to a small penguin screen.
The only thing I can do from there is revert back to stock B29, then update back to stock B15.
I want to be able to install TWRP, root my phone, on Nougat, and be able to use my phone too?
tele_jas said:
My bootloader is unlocked (back when ZTE actually provided the unlocking)....adb fastboot works on my phone as well and I've flashed TWRP (3.0.4 and 3.0.3-1) and it's booted into TWRP, but I cannot boot into the actual OS...My phone goes all black and just hangs there, I think this may be booting directly into EDL mode and not the OS? I can plug my phone into the computer and my computer makes noises as if a USB device has been attached, but my screen is completely black. If I push the start button while the phone is booting (to bypass the bootloader is unlocked warning screen), I boot to a small penguin screen.
The only thing I can do from there is revert back to stock B29, then update back to stock B15.
I want to be able to install TWRP, root my phone, on Nougat, and be able to use my phone too?
Click to expand...
Click to collapse
Then follow this:
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
and flash this:
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I think I know what happened to you... did you by any chance allow system modifications in TWRP? That makes the OS bootloop if you have Nougat.
bornlivedie said:
Then follow this:
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
and flash this:
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I think I know what happened to you... did you by any chance allow system modifications in TWRP? That makes the OS bootloop if you have Nougat.
Click to expand...
Click to collapse
The MiFlash program found my phone, but failed every time I ran it.. So, I just bit the bullet and downloaded the latest TWRP 3.0.4-1 and flashed that.....And it worked! I then flashed SU, my fonts and changed my Emoji's....I'm about there with customization, and it's all booting up just fine!
But, yes the first few times I did allow system modifications......But I also did this last time too and it's working fine?
Hello
I have OrangeFox recovery on my phone and whenever I try to flash a custom rom then after rebooting to system it always brings me back to recovery. I tried this with MIUI Global ROM, Pixel Experience but the results are same.
I also tried through TWRP but still. After flashing a custom rom, it acts like the rom isn't flashed at all.
Any help will be appreciated.
Thank you.
Dartanw said:
Hello
I have OrangeFox recovery on my phone and whenever I try to flash a custom rom then after rebooting to system it always brings me back to recovery. I tried this with MIUI Global ROM, Pixel Experience but the results are same.
I also tried through TWRP but still. After flashing a custom rom, it acts like the rom isn't flashed at all.
Any help will be appreciated.
Thank you.
Click to expand...
Click to collapse
You read the how to from which rom? Maybe the only problem that you have to format not data. Maybe firmware?
Test this steps with your rom
[ROM][lavender][12L] VoltageOS 1.7 [OFFICIAL]
VoltageOS 12.1|L for Redmi Note 7/7S ABOUT Greetings, interested users! You have reached the gateway of a simplistic, no-frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences, with...
forum.xda-developers.com
Easier then write.
And flash magisk after the first boot
Long time ago it happens to me too and solution was to flash latest firmware
I flashed newest firmware and then custom ROM. Still it boots to recovery.
Sorry got no idea to help, but what about trying the OrangeFox Recovery Project: https://forum.xda-developers.com/t/official-recovery-orangefox-recovery-project-r11-1.3941822/
I managed to flash newest orangefox without any problems, newest firmware and so on. I just don't get why it doesn't wanna boot to system.
Dartanw said:
I managed to flash newest orangefox without any problems, newest firmware and so on. I just don't get why it doesn't wanna boot to system.
Click to expand...
Click to collapse
Magisk, gapps? What u flash after the rom and you wipe and or format what before and or after? Make the steps right. Never had problem with my Redmi 5 plus, Note 7 and Mi Note 10 last.
joke19 said:
Magisk, gapps? What u flash after the rom and you wipe and or format what before and or after? Make the steps right. Never had problem with my Redmi 5 plus, Note 7 and Mi Note 10 last.
Click to expand...
Click to collapse
Nope. After flashing Pixel Experience or Global Xiaomi ROM I always reboot to system but it brings me back to recovery.
What i did step-by-step on newest OrangeFox
1, Wiped Cache, System, Internal Storage, Dalvik, Vendor
2. Flashed newest MIUI firmware
3. Flashed Pixel Experience
4. Reboot to system
And it brings me back to recovery.
Dartanw said:
Nope. After flashing Pixel Experience or Global Xiaomi ROM I always reboot to system but it brings me back to recovery.
What i did step-by-step on newest OrangeFox
1, Wiped Cache, System, Internal Storage, Dalvik, Vendor
2. Flashed newest MIUI firmware
3. Flashed Pixel Experience
4. Reboot to system
And it brings me back to recovery.
Click to expand...
Click to collapse
After flash not wipe format
joke19 said:
After flash not wipe format
Click to expand...
Click to collapse
Data
I have a similar problem:
fastboot oem device-info shows:
Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
Finished. Total time: 0.001s
trying to
Code:
fastboot flash recovery twrp / orange *.img shows:
Sending 'recovery' (33804 KB) OKAY [ 1.148s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Device Error')
fastboot: error: Command failed
Phone is now stuck on fastboot. Rebooted once in redmi recovery but i can no longer. I am now downloading the official fastboot img to see if i can fix this.
If anyone has a solution let me know. Thanks.