Actually I flashed MIUI 10 pie beta yesterday and now because of battery drain issues and bugs I want to go to another ROM which is masik 3.3 which is based on Oreo.
I am not sure what to do.
Should I directly install masik 3.3 by doing clean flash over Miui Pie beta or should I first go to Developer/Stable Oreo based MIUI 10 ROM and then clean flash Masik 3.3?
What abour ARB/firmware?Thanks!
First oreo latest stabil miflash to flash. After install twrp and masik 3.3 clean flash
Second option (I did it already). Flash via Mi Flash latest stable.
The first option will soft brick your device.
Letrix said:
Second option (I did it already). Flash via Mi Flash latest stable.
The first option will soft brick your device.
Click to expand...
Click to collapse
I tried using mi flash but device id not showing.
To confirm I type adb devices in command prompt. List of devices attached is showing empty. After that i tried installing new updates drivers but nothing helped. I am on windows 10. ADB drivers are also installed. Platform tools too. I did all but list of devices is showing empty in fastboot mode. Though I can see adb devices when in recovery or in system. I don't know what to do. can you help please?
Vivi_31 said:
I tried using mi flash but device id not showing.
To confirm I type adb devices in command prompt. List of devices attached is showing empty. After that i tried installing new updates drivers but nothing helped. I am on windows 10. ADB drivers are also installed. Platform tools too. I did all but list of devices is showing empty in fastboot mode. Though I can see adb devices when in recovery or in system. I don't know what to do. can you help please?
Click to expand...
Click to collapse
You have installed pie rom u cant go back to masik 3.3 cause its oreo based rom. I sent you a meassage just check.
Vivi_31 said:
I tried using mi flash but device id not showing.
To confirm I type adb devices in command prompt. List of devices attached is showing empty. After that i tried installing new updates drivers but nothing helped. I am on windows 10. ADB drivers are also installed. Platform tools too. I did all but list of devices is showing empty in fastboot mode. Though I can see adb devices when in recovery or in system. I don't know what to do. can you help please?
Click to expand...
Click to collapse
Install Pie and MIUI Pie Recovery. Then, from recovery, boot to bootloader and check in PC if it's listed.
thewhitewolf89 said:
You have installed pie rom u cant go back to masik 3.3 cause its oreo based rom. I sent you a meassage just check.
Click to expand...
Click to collapse
Yes that's why
Letrix said:
Install Pie and MIUI Pie Recovery. Then, from recovery, boot to bootloader and check in PC if it's listed.
Click to expand...
Click to collapse
Well I tried it but didn't work.
Instead now I am flashing Pixel Experience and then after going to pixel experience, I will go to latest MIUI stable ROM available on Xiaomi website and then never go to Miui beta Pie update unless stable version comes. Too much headache. lol
But thank you all who responded
Is it possible to return to Oreo 10.2.2.0 from Pie beta 9.3.28?
I have unlocked bootloader and orangefox recovery for pie.
umair42 said:
Is it possible to return to Oreo 10.2.2.0 from Pie beta 9.3.28?
I have unlocked bootloader and orangefox recovery for pie.
Click to expand...
Click to collapse
I returned to Oreo from Xiaomi.eu Pie Beta. It's described above
Vivi_31 said:
Actually I flashed MIUI 10 pie beta yesterday and now because of battery drain issues and bugs I want to go to another ROM which is masik 3.3 which is based on Oreo.
I am not sure what to do.
Should I directly install masik 3.3 by doing clean flash over Miui Pie beta or should I first go to Developer/Stable Oreo based MIUI 10 ROM and then clean flash Masik 3.3?
What abour ARB/firmware?Thanks!
Click to expand...
Click to collapse
I recovered my phone by flashing Stock ROM "miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip" via TWRP. It will overwrite TWRP with Stock Recovery, You have to reflash TWRP via fastboot.
After that you will be able to flash any Custom ROM successfully.
yawarniazi said:
I recovered my phone by flashing Stock ROM "miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip" via TWRP. It will overwrite TWRP with Stock Recovery, You have to reflash TWRP via fastboot.
After that you will be able to flash any Custom ROM successfully.
Click to expand...
Click to collapse
Does it softbrick ur whyred? The safety way is flash thru mi flasher
yawarniazi said:
I recovered my phone by flashing Stock ROM "miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip" via TWRP. It will overwrite TWRP with Stock Recovery, You have to reflash TWRP via fastboot.
After that you will be able to flash any Custom ROM successfully.
Click to expand...
Click to collapse
Won't it brick(ARB) phone if I go back to stable?
Are you sure about ROM you flash? because on xiaomi official website its saying latest stable is V10.2.20 and not V10.2.1.0.
Can you confirm it plz? Thanks!
Kuato said:
Does it softbrick ur whyred? The safety way is flash thru mi flasher
Click to expand...
Click to collapse
Do you know anyother way which doesnt require pc? Actually my device is not getting recognized in adb devicess...I tried all but nothing helped.
Vivi_31 said:
Do you know anyother way which doesnt require pc? Actually my device is not getting recognized in adb devicess...I tried all but nothing helped.
Click to expand...
Click to collapse
I was tried to direct flash with TWRP and softbrick my whyred, but I figured out when I was done flash miui 8.1, I should flash Redwolf recovery which is capable to flash persist partition to fix some of bugs acquired from downgrade. Its work for me, first I tried direct flash to miui 10.2.2.0 and its boot fine, but when I reboot, It doesnt boot up and on my pc detected as 9008 (softbrick?). Then I flash pie twrp thru fastboot and booting to twrp, flash miui beta pie and let it booting,
Second try. Now im on miui pie again LOL. then I flash miui 10.2.2.0 thru TWRP, and flash redwolf recovery, then reboot to redwolf, then flash persist.img. then boot up fine and no bug.
Kuato said:
I was tried to direct flash with TWRP and softbrick my whyred, but I figured out when I was done flash miui 8.1, I should flash Redwolf recovery which is capable to flash persist partition to fix some of bugs acquired from downgrade. Its work for me, first I tried direct flash to miui 10.2.2.0 and its boot fine, but when I reboot, It doesnt boot up and on my pc detected as 9008 (softbrick?). Then I flash pie twrp thru fastboot and booting to twrp, flash miui beta pie and let it booting,
Second try. Now im on miui pie again LOL. then I flash miui 10.2.2.0 thru TWRP, and flash redwolf recovery, then reboot to redwolf, then flash persist.img. then boot up fine and no bug.
Click to expand...
Click to collapse
I flashed latest stable rom on miui pie beta through twrp. Now i cannot boot into recovery mode at all (softbrick?)
When I boot into miui, we have to setup things but when we are adding account google services stops and i see black screen , I cannot go ahead, i think zip file was not good. I dont know what to do now. I cant go to twrp neither to system and cannot flash through fastboot becuz it doent recognize adb devices
Vivi_31 said:
I flashed latest stable rom on miui pie beta through twrp. Now i cannot boot into recovery mode at all (softbrick?)
When I boot into miui, we have to setup things but when we are adding account google services stops and i see black screen , I cannot go ahead, i think zip file was not good. I dont know what to do now. I cant go to twrp neither to system and cannot flash through fastboot becuz it doent recognize adb devices
Click to expand...
Click to collapse
Does fastboot recognized?? If its recognized. U can fix it easily.
I was on same problem as you, but I can flash thru mi flasher. At my second try (to make my phone in same condition as before I fix it), I flash oreo recovery without reboot the device after flashing miui oreo. And then flash the persist img thru advance-terminal and its work and no softbrick anymore.
Kuato said:
Does fastboot recognized?? If its recognized. U can fix it easily.
I was on same problem as you, but I can flash thru mi flasher. At my second try (to make my phone in same condition as before I fix it), I flash oreo recovery without reboot the device after flashing miui oreo. And then flash the persist img thru advance-terminal and its work and no softbrick anymore.
Click to expand...
Click to collapse
Well I went to service centre and they flashed it. I am on Stable ROM now. I couldn't through my computer because it's not recognising adb devices but recognising fastboot devices. I can't boot into any recovery other then stock even through fastboot devices. You know why? I can't find any reasons for that.
Vivi_31 said:
Well I went to service centre and they flashed it. I am on Stable ROM now. I couldn't through my computer because it's not recognising adb devices but recognising fastboot devices. I can't boot into any recovery other then stock even through fastboot devices. You know why? I can't find any reasons for that.
Click to expand...
Click to collapse
Have u flash antirbpass before flashing ?
Kuato said:
Have u flash antirbpass before flashing ?
Click to expand...
Click to collapse
Idk much ab it but what I do is :
fastboot devices
fastboot flash antirbpass dummy.img
fastboot flash recovery recovery.img
after that it says error : Can't target recovery.
and stuck on mi logo if i boot into any other recovery
Good morning. I can't install Arrow rom update on whyred, it appears "modem firmware from MIUI V10.3.1.0. PEIMIXM or newer stock ROMs is prerequisite to be compatible with this build.updater process ended with ERROR: 7"
How can I solve the problem? Mount Arrow pie, Magisk and bootloader unlocked. I apologize for bad English
Flash miui1 10.3 recovery file with twrp and than lazy flasher zip file after successfully bootup
Flash twrp 3.3x pie based recovery than flash Arrow os
Wipe data, system, cache,dalik is recommended...
Is enough to flash the zip here and then you can proceed in your flashes
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, havoc, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.
edit: I tried to lock and relock bootlander, still geting the same error. I'm stuck on Oreo
bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, havoc, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.
edit: I tried to lock and relock bootlander, still geting the same error. I'm stuck on Oreo
Click to expand...
Click to collapse
I think that i figured out something, I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
Did you try reflash twrp latest version?
After flashing MIUI 11 beta I decided to go back to crDroid. Restored backup via twrp but it wouldn't boot, just booted into recovery, but twrp wouldn't decrypt data. I've seen this before and solved it by adb sideload crdroid rom (maybe because it includes vendor?). I tried this and now it just boots straight into fastboot. I tried fastboot boot twrp.img and that says "failed to load/authenticate boot image". What should I do?
Edit: After using miflash I can get back to stock, and then use fastboot to flash twrp. Twrp still doesn't ask for password to decrypt data. Every time I try to adb sideload crdroid.zip i end up stuck with fastboot again and have to miflash!?
Full wipe in TWRP and format data partition
reboot in recovery
flash crdroid and flash magisk
flash vmbeta after rom
I tried full wipes including data and flashing crdroid. I've also tried flashing vbmeta at multiple points.
Even after flashing back to stock miui with miflash android wouldn't boot, instead it just loaded miassistant (miui recovery). I'd have to flash twrp again, try flashing a new system and it would always reboot to fastboot.
The only solution has been to flash back to miui 11 beta (android 10) which boots fine. I'm still not sure whats going on but I'm ok with miui for now.
Deleted due to double post
briandarrel said:
I tried full wipes including data and flashing crdroid. I've also tried flashing vbmeta at multiple points.
Even after flashing back to stock miui with miflash android wouldn't boot, instead it just loaded miassistant (miui recovery). I'd have to flash twrp again, try flashing a new system and it would always reboot to fastboot.
The only solution has been to flash back to miui 11 beta (android 10) which boots fine. I'm still not sure whats going on but I'm ok with miui for now.
Click to expand...
Click to collapse
Solution mil kya bhai
After trying to install a custom ROM (PixelExperience for OnePlus 7T [hotdogb]) via fastboot, the installation flashing ended with errors with "no such partition" for odm, product and system I tried everything to get out of the fastboot screen loop. After finding a bat file with IMG files which got me on the Android 11 Beta 1. build (still no WiFi)
What can I do to fix the partition error to get on the Pixel Experience ROM or even get back to the stable build - I did try MSM but it isn't listing the phone even after pressing ENUM.
Please help...
Context (can skip): The latest stable build OOS for my 7T had issues with the microphone not working and so I decided to do a factory reset which resulted in having a clean install but now, WiFi doesn't connect for some reason. After trying some fixes I decided to install a custom ROM.
U need to flash stock recovery (fastboot flash recovery recovery.img) as twrp prevents fastbootD entry. Then type fastboot reboot fastboot to enter fastbootD. Then flash your rom. Personally, I just flash roms via Chinese twrp or 3.5.10 twrp
HueyT said:
U need to flash stock recovery (fastboot flash recovery recovery.img) as twrp prevents fastbootD entry. Then type fastboot reboot fastboot to enter fastbootD. Then flash your rom. Personally, I just flash roms via Chinese twrp or 3.5.10 twrp
Click to expand...
Click to collapse
that was my process for the first try - entered fastbootD for the flashing process which ended with the mentioned partition error and the fastboot loop. I realised that TWRP version I got from TOOL ALL IN ONE wasn't going to work as it couldn't access data no matter what.
No twrp can decrypt oos or a11 custom roms data. Chinese twrp can access data only on a10 custom roms if u remove screen lock before booting into twrp for backup
What do you reckon I try this time then?
itssata said:
What do you reckon I try this time then?
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com