Hello,
I've been using Mido over one year, never faced such a weird problem.Whenver I flash Pie Based Roms the whole screen goes blank when the Rom boots up.I've followed each & every instructions as per OP,still same result but everything works fine on Oreo/Nougat based Roms.I've used TWRP by warabhishek/Pitchblack TWRP/OrangeFox TWRP,I'm on latest 8.9.6 firmware. Tried almost every pie based roms/GSI for Mido.
Can anyone provide a fix for this issue?
Edit : So I've fixed it myself after researching on the MIUI forum.Some people got this issue on various xiaomi devices after updating MIUI,After they did a Factory reset everything went normal.So I decided to test this,I did things,which are mentioned below.
1.I was on Oreo Rom so I flashed a fastboot miui rom.(Don't lock the bootloader)
2.After the Miui rom booted,Turned on the usb debugging
3.Booted into MIUI Recovery, Performed a factory reset (I know it sounds strange,but stay sure it's going to work)
4.Flashed Treble-TWRP by abhishek
5.Once again format data from advanced wipe (Need to remove the encryption)
6.Wipe system>data>cache>vendor
7.Flash any Pie Rom & Gapps
8.Reboot
Now you won't face that strange black screen issue anymore.
Thanks
flash boot.img extracted from the rom.zip file after flashing rom via TWRP. When flashing finished, don't restart to System, select Restart to Bootloader then type below command.
Go to fastboot then type fastboot flash boot boot.img
yawarniazi said:
flash boot.img extracted from the rom.zip file after flashing rom via TWRP. When flashing finished, don't restart to System, select Restart to Bootloader then type below command.
Go to fastboot then type fastboot flash boot boot.img
Click to expand...
Click to collapse
Are you sure this will work? cause I've wasted many hours in flashing these Roms but no success. If you're quite sure about this I will definitely try this
yawarniazi said:
flash boot.img extracted from the rom.zip file after flashing rom via TWRP. When flashing finished, don't restart to System, select Restart to Bootloader then type below command.
Go to fastboot then type fastboot flash boot boot.img
Click to expand...
Click to collapse
And another thing is, when Rom boots up, If I press volume buttons, I can see volume sliders but nothing more.Everything else is black.
Try...
To flash stable firmware 9.6.2! Gcam work in my case.
Alfonso13 said:
To flash stable firmware 9.6.2! Gcam work in my case.
Click to expand...
Click to collapse
I'm pretty sure bro,this isn't related with Firmware.It's something else
Rocky said:
And another thing is, when Rom boots up, If I press volume buttons, I can see volume sliders but nothing more.Everything else is black.
Click to expand...
Click to collapse
I think yor phone is Encrypted.My mido whas doing this thing when it was encrypted.
Sent from my [device_name] using XDA-Developers Legacy app
hiey said:
I think yor phone is Encrypted.My mido whas doing this thing when it was encrypted.
Click to expand...
Click to collapse
Nope I already decrypted while flashing
have you fixed it already? I'm waiting for few months for Pie roms to be stabled.
RebornCheiko said:
have you fixed it already? I'm waiting for few months for Pie roms to be stabled.
Click to expand...
Click to collapse
No fix yet ?
Update : I've fixed it,Read the Original Post to get the solution
Rocky said:
Update : I've fixed it,Read the Original Post to get the solution
Click to expand...
Click to collapse
I tried your method, it doesn't work for me on 10. I am using CrDroid 10. I faced the same issue with some ROM in Pie also. Please advice.
Arifcatalyst said:
I tried your method, it doesn't work for me on 10. I am using CrDroid 10. I faced the same issue with some ROM in Pie also. Please advice.
Click to expand...
Click to collapse
Did you performed a factory reset from MIUI Recovery?
Rocky said:
Did you performed a factory reset from MIUI Recovery?
Click to expand...
Click to collapse
Yes, I booted in Recovery and then wiped the data.
Arifcatalyst said:
Yes, I booted in Recovery and then wiped the data.
Click to expand...
Click to collapse
Idk what's happening with you but I found this useful, while nobody had idea about this problem. You can try flashing older miui fastboot rom, like miui9/10 then perform a factory reset with miui default recovery.then try switching to other custom roms.Let me know the update.
Related
TL;DR: Nexus 9 bootloops with every ROM other than stock.
My Nexus 9 will bootloop whenever any custom ROM is installed on it. I follow the usual steps in TWRP (downloading ROM and Gapps, wiping factory reset, flashing the zips and wipe dalvik/cache) will not get any error during installation and regardless of the ROM, I will get my nexus stuck on Google logo. Then I will have to unroot and install stock again and it'll work.
Ive also tried Wugfresh Nexus Root Toolkit and it won't work either. As long as Im on stock, I can root as well and everything is fine.
Any idea what could be happening? I wanna get rid of the damn lag. Have tried Cyanogenmod, Slimrom6 and Pure Nexus Project. All with their recommended gapps and will always end up with my tablet stuck in the Google logo.
Any help is very appreciated.
Sounds like you are doing everything right..
How long are you waiting for the device to start up ? Is it possible you aren't simply waiting long enough ? I'd give it a good 10 - 20 minutes on 1st boot before deciding it's hung in a boot loop.
I am having the exact same problem. I have tried so many roms that install correctly and then when flashing gapps and rebooting it is stuck on the Google logo. And I left my tablet on for a few hours so its definitely bootlooping.
The only thing that comes to mind is bootloader... If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
yup, happening to me too. so, how can i flash the factory image now? thanks.
It's in the stickies. http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Sent from my Nexus 5X using XDA-Developers mobile app
links to 7.x compatible bootloader where?
maelfilk said:
If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
Click to expand...
Click to collapse
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
nexacan said:
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
Click to expand...
Click to collapse
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
bootloader flashing process: enough to "fastboot flash bootloader boot*.img"?
maelfilk said:
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
Click to expand...
Click to collapse
I assume i need the latest 7.0.0 (NRD91N, Nov 2016) bootloader which is inside the latest build?
Then i will need to go through the process like:
Code:
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
Or do i have to do more like described here (Steps 8-9)?
Your help is appreciated, thanks again!
ps: for others who got stuck in the bootloop and don't know how to stop it or turn off the device:
1. reboot into recoverymode in case you have twrp
2. open a terminal
3. type in
Code:
poweroff
an hit enter
Yes, NRD91N
Well , all i did was simple
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
once complete
fastboot reboot-bootloader
That's it
Still not booting...
maelfilk said:
Yes, NRD91N
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
fastboot reboot-bootloader
...
That's it
Click to expand...
Click to collapse
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
ps: trying with cm-14.1-20161027-UNOFFICIAL-flounder.zip now, but boot seems to hang too and the upper part
of the Nexus 9 is getting really warm. I will leave it for 15 more minutes to wait and see what happens.
nexacan said:
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
Click to expand...
Click to collapse
Hmm sorry i don't knwo why this is happening.
Currently i reverted back to marshmallow roms, i find them more stable.
Do you have twrp? After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
maelfilk said:
Do you have twrp?
Click to expand...
Click to collapse
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
maelfilk said:
After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
Click to expand...
Click to collapse
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
nexacan said:
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
Click to expand...
Click to collapse
About 10-15 minutes
It works now!
Thank you maelfilk, i got i running now.
CM boots properly now - though i cannot configure it. During the Setup process
in the first step of selecting the language it crashes. I am sure this will be fixed
with a later version of CM-14.1.
Does someone know any other source for CM-14.1 for flounder?
Meanwhile i will try AOSP again.
Edit: AOSP boots properly but unfortunately WLAN does not work in the AOSP_flounder_11-18-2016.zip build.
I guess this is why you stick to the 6.x builds maelfilk.
большое спасибо
nexacan said:
большое спасибо
Click to expand...
Click to collapse
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
link to the "vendor"
maelfilk said:
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
Click to expand...
Click to collapse
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
nexacan said:
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
Click to expand...
Click to collapse
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions in the link you gave. If you have trouble with wlan or camera it usually means that vendor is outdated.
Black bootscreen and hanging after flashing vendor.img (only vendor.img)
maelfilk said:
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions...
Click to expand...
Click to collapse
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
nexacan said:
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
Click to expand...
Click to collapse
Are you sure you chose to flash vendor.img in vendor partition in twrp?
Hi Friends i flashed miui firmware by stinx when i was on lineage rom to update the rom without any error.Then after flashed no mi logo no recovery no fastboot tooo Anyone pls tell solution for this to recover my device back
The Game 370 said:
Hi Friends i flashed miui firmware by stinx when i was on lineage rom to update the rom without any error.Then after flashed no mi logo no recovery no fastboot tooo Anyone pls tell solution for this to recover my device back
Click to expand...
Click to collapse
Are you able to see led blinking as red when you connect it to PC?
gulshanstrider said:
Are you able to see led blinking as red when you connect it to PC?
Click to expand...
Click to collapse
Yes but pc is not recognising
The Game 370 said:
Yes but pc is not recognising
Click to expand...
Click to collapse
Go to device manager and tell which Port it Is connected on ?
900E or 9008
gulshanstrider said:
Go to device manager and tell which Port it Is connected on ?
900E or 9008
Click to expand...
Click to collapse
Hi its not showing anything sorry if i am wrong
Do you have MiFlash tool ?
gulshanstrider said:
Do you have MiFlash tool ?
Click to expand...
Click to collapse
YES
The Game 370 said:
YES
Click to expand...
Click to collapse
Check if it is getting listed there.
If not try test point method
gulshanstrider said:
Check if it is getting listed there.
If not try test point method
Click to expand...
Click to collapse
No its not showing my device
The Game 370 said:
No its not showing my device
Click to expand...
Click to collapse
what is the current state of yr phone?
tell in details.
is it charging?
is mi logo appears when power button is pressed?
did u try pressing "vol down+power button"?
and what exactly did u do before the phone was dead?
any error occured during flashing?
Same with me
Try accessing fastboot, then reunlock your bootloader
Simoom Sadik said:
what is the current state of yr phone?
tell in details.
is it charging?
is mi logo appears when power button is pressed?
did u try pressing "vol down+power button"?
and what exactly did u do before the phone was dead?
any error occured during flashing?
Click to expand...
Click to collapse
No mi logo,no fastboot,no recovewry nd not charging too
Only red light blinking when connected to usb
I was on lineage rom nd tried to update that rom nd flashed miui 7.5.4 firmware by the stinx to get rid of error while flashing newer build of lineage rom
auliamaster74 said:
Same with me
Try accessing fastboot, then reunlock your bootloader
Click to expand...
Click to collapse
I am unable to access fastboot
The Game 370 said:
I am unable to access fastboot
Click to expand...
Click to collapse
try pressing power + vol down untill it boots into fastboot
at first, I thought I can't access fastboot, turns out I could
try it
auliamaster74 said:
try pressing power + vol down untill it boots into fastboot
at first, I thought I can't access fastboot, turns out I could
try it
Click to expand...
Click to collapse
Thanks i tried deep flash cable method but it didnt worked nd tried test point method Finally it worked
Also Fixed,but FW Flash is a problem
HI,
I just wanted to comment on this, in the hope that some more experienced member, or even TheStrix would see it.
I've had the exact same problem over the last few days, but have been able to fix it each time by reflashing recovery from miFlash in edl mode;
Flashing the firmware from TheStrix (Latest, kenzo) without fail, bricks the Redmi Note 3, only being able to get to FastBoot. I'm able to switch to EDL on the PC with that batch file that's floating about, and flash recovery through miflash. I've been on LineageOS14 for the past few weeks, but my phones been barely usable with lag. Switched to AOSPX the other day by first flashing the FW;
1. Reboot to recovery
2. Backups
3. Wipe everything except for sd
4. Flash FW
5. Flash AOSPEx
6. Flash Gapps
7. Clear Cache
8. Reboot
That was the first time, and brick... as described above, back to recovery- tried missing out GAPPS- same result..
I went through a few different combinaitons, so have gotten quite used to the EDL mode miFlash...
Back through EDL.. flash recovery.. JUST AOSPEx, booted fine. Setup, etc, back to recovery, GAPPS, reboot, setups, etc.All working good- Except no power button
So I once again went back to recovery and flashed just the FW (Fully expecting it might fail)- Sure enough.. BRICK... So just, I've gone back through the miFlash, installed recovery, but then just decided to try rebooting from recovery into my existing AOSPEx- All works fine- Even the power button now- Was that fixed by the FW? And the bigger thing I'm wondering, since everytime I've flashed the FW it's resulted in a brick-does that mean the FW's not working? When I re flash the recovery, am I back to original FW?
Am I now on the new FW?
Only other thing is I don't have root... I'll see if I can find a supersu to flash, I guess.
So tl;dr- I'm all up and working- but flashing the latest FW form TheStrix appears to brick the Note 3 every time. I can only get a rom to install by NOT first flashing the FW. Flashing the FW after a rom still bricks. And I don't know if it is actually flashed with the new fw after re-installing recovery.
Edd.
Edmundajw said:
HI,
I just wanted to comment on this, in the hope that some more experienced member, or even TheStrix would see it.
I've had the exact same problem over the last few days, but have been able to fix it each time by reflashing recovery from miFlash in edl mode;
Flashing the firmware from TheStrix (Latest, kenzo) without fail, bricks the Redmi Note 3, only being able to get to FastBoot. I'm able to switch to EDL on the PC with that batch file that's floating about, and flash recovery through miflash. I've been on LineageOS14 for the past few weeks, but my phones been barely usable with lag. Switched to AOSPX the other day by first flashing the FW;
1. Reboot to recovery
2. Backups
3. Wipe everything except for sd
4. Flash FW
5. Flash AOSPEx
6. Flash Gapps
7. Clear Cache
8. Reboot
That was the first time, and brick... as described above, back to recovery- tried missing out GAPPS- same result..
I went through a few different combinaitons, so have gotten quite used to the EDL mode miFlash...
Back through EDL.. flash recovery.. JUST AOSPEx, booted fine. Setup, etc, back to recovery, GAPPS, reboot, setups, etc.All working good- Except no power button
So I once again went back to recovery and flashed just the FW (Fully expecting it might fail)- Sure enough.. BRICK... So just, I've gone back through the miFlash, installed recovery, but then just decided to try rebooting from recovery into my existing AOSPEx- All works fine- Even the power button now- Was that fixed by the FW? And the bigger thing I'm wondering, since everytime I've flashed the FW it's resulted in a brick-does that mean the FW's not working? When I re flash the recovery, am I back to original FW?
Am I now on the new FW?
Only other thing is I don't have root... I'll see if I can find a supersu to flash, I guess.
So tl;dr- I'm all up and working- but flashing the latest FW form TheStrix appears to brick the Note 3 every time. I can only get a rom to install by NOT first flashing the FW. Flashing the FW after a rom still bricks. And I don't know if it is actually flashed with the new fw after re-installing recovery.
Edd.
Click to expand...
Click to collapse
It's because you haven't unlocked officially. TheStrix's firmware contains MM bootloader which relocks your bootloader if you're in LP bootloader(which is your bootloader if you've unlocked unofficially). If you've already unlocked officially then flash the latest MIUI dev ROM(which relocks your bootloader) then unlock again, TheStrix's firmware will now work.
Or you can just unzip the Firmware then remove emmc_appsboot.mbn(MM bootloader) then rezip it again. You'd still get problems flashing the latest LineageOS Roms if you don't update your bootloader though. So my advice is unlock officially.
Try This guide http://en.miui.com/thread-235865-1-1.html and this guide make a deep flash cable and download the latest fastboot rom and follow the first link http://en.miui.com/thread-380827-1-1.html
Download:
A1 Oreo Firmware: Google Drive
A1 Nougat Firmware: Google Drive
5X Nougat Firmware: Google Drive
FAQ:
Which one should I install?
If you plan to use Android One rom on the 5X, you should flash A1 firmware.
If you come back from Android One to MIUI, you should flash 5X firmware.
If you are going to use Android One Oreo, install A1 Oreo Firmware.
When should I install it?
You should only install it whenever you switch from A1 roms to 5X roms and viceversa. If you update your A1/5X rom, there is no need to reflash it.
Where does they come from?
A1 Oreo firmware is extracted from January fastboot image (8.1.10)
A1 Nougat firmware is extracted from the December fastboot image.
5X Nougat firmware is extracted from China Stable 9.0.3.0 fastboot image.
How do I install it?
- Backup your EFS
- Extract zip file on your computer
- Reboot your phone into fastboot (Power + Vol Down)
- Connect your phone to your computer with an USB cable
- Double click on "flash_only_firmware" file.
- Wait until it finishes.
- Reboot into TWRP, wipe cache and dalvik and then reboot to system
How do I backup my EFS?
- Install my TWRP.
- Boot into TWRP
- Tap on Backup
- Check EFS and uncheck rest of checkboxes
- Swipe to backup
Is there any way to flash this without a computer?
At the moment there isnt any other way to flash it without a computer.
Does it give me an ability to install OTAs when flashed to A1?
thanks for the nice roms:good:
As any kowned issues for A1 rom ?
It is not working, when I click on "flash_only_firmware" it opens close quickly and nothing happens.
halbercone said:
It is not working, when I click on "flash_only_firmware" it opens close quickly and nothing happens.
Click to expand...
Click to collapse
Same for me. Is it possible to flash the images manually?
halbercone said:
It is not working, when I click on "flash_only_firmware" it opens close quickly and nothing happens.
Click to expand...
Click to collapse
I tried moving fastboot, adb and "those files" to the same folder and then it flashed.
gurex said:
I tried moving fastboot, adb and "those files" to the same folder and then it flashed.
Click to expand...
Click to collapse
As any kowned issues for A1 rom ?
How long should it take to boot after flashing, I'm sitting at the boot screen (blue-red-yellow-green line with no animation for a while now?
BluNoze said:
How long should it take to boot after flashing, I'm sitting at the boot screen (blue-red-yellow-green line with no animation for a while now?
Click to expand...
Click to collapse
Try to reboot it by long press the power button, it would be sooner if you reboot
小蚊 said:
Try to reboot it by long press the power button, it would be sooner if you reboot
Click to expand...
Click to collapse
Thanks I did that too, but couldn't get it to work, ended up installing the MiA1 port on MiUI via TWRP flahable zip which worked pretty much instantly, I will probably try again later
BluNoze said:
Thanks I did that too, but couldn't get it to work, ended up installing the MiA1 port on MiUI via TWRP flahable zip which worked pretty much instantly, I will probably try again later
Click to expand...
Click to collapse
emmmmm, I think you should wait, , , It may take longer time if you flash through PC.
小蚊 said:
emmmmm, I think you should wait, , , It may take longer time if you flash through PC.
Click to expand...
Click to collapse
Thanks I'll try again tonight, but I waited over 20 mins and it was still in the initial boot screen.
BluNoze said:
Thanks I'll try again tonight, but I waited over 20 mins and it was still in the initial boot screen.
Click to expand...
Click to collapse
It seems like these firmwares is not a full system, have you flashed a rom before you flash these firmwares?
Twrp?
Hi i bought MI 5X the Shop send it to me with Android One Rom but there is No recovery or when i want to Recovery the Phone Just reboot i want to ASK you now which twrp should i flash for Mi 5X or A1 and after this can i flash the 5X Firmware?
Hi all, am i reading the original post wrong if i conclude that if i'm already on the A1 nougat rom there is no need to flash the A1 Oreo firmware if i want to flash the Oreo rom ? And that i can Just flash Oreo rom with twrp ?
Hi guys. Could any of you help me out with flashing this firmware? Clicking the flash-firmware file does nothing - a command prompt window opens and closes in a second and nothing happens. Any tips on how to get it to work? Thanks!
Kumczak said:
Hi guys. Could any of you help me out with flashing this firmware? Clicking the flash-firmware file does nothing - a command prompt window opens and closes in a second and nothing happens. Any tips on how to get it to work? Thanks!
Click to expand...
Click to collapse
I couldn't get the original Nougat one to install either at first. The only way to install it was what I mentioned in this thread:
https://forum.xda-developers.com/showpost.php?p=74946333&postcount=25
BluNoze said:
I couldn't get the original Nougat one to install either at first. The only way to install it was what I mentioned in this thread:
https://forum.xda-developers.com/showpost.php?p=74946333&postcount=25
Click to expand...
Click to collapse
thanks, bro. i will try that tomorrow!
Kumczak said:
thanks, bro. i will try that tomorrow!
Click to expand...
Click to collapse
The firmware file in the OP should be unzipped in the same folder as the fastboot program in your PC.
Hello,
Since MIUI 10.3.1.0 (PEIMIXM) was launched, I tried to update my device. After the update, when the smartphone rebooted it kept stuck in Mi logo sreen (Android loading wasn't also appearing). I tried to use MiFlash to reflash the ROM and the same happended.
Thinking it was a random problem of MIUI I decided to move to Pixel Experience because I had used it before and I liked. In the same day of MIUI 10.3.1.0 (PEIMIXM) launch, Pixel Experience also launched a new whyred version (in the beggining of June, i think).
I did what was needed to successfully install the ROM according to the dev's thread:
-I downloaded all the needed files (MIUI 10.3.1.0 PEIMIXM firmware, Pixel Experience ROM, recommended modified TWRP version of the developer);
-Initially, I installed TWRP via fastboot mode;
-I flashed the firmware;
-I wiped the partitions Cache Dalvik / ART, System, Cache, Data, vendor;
-I flashed Pixel Experience ROM;
-I wiped Internal Storage;
-I rebooted the device.
After those steps, I couldn't get access to my "homescreen". Basically, my phone stays stuck at the Mi logo screen. And nothing happens.
Considering it could be a recovery problem, I tried to use Pitch Black Recovery (the latest version available for whyred) that supports Oreo and Pie. I used TWRP to flash this one, and after that I made all the steps above again and the same happened.
I'm now only available to flash MIUI (if it is Android 8.1). I can only flash Pixel experience versions that were released before the MIUI Pie stable for this device.
I really appreciate if you could help me!
Hi,
Copy:
- the full name of the firmware file you used
-The full name of the rom file you use
-The full name of the recovery file you use/intend to use.
The name and version of current recovery installed.
Cheers,
htchd2sucks said:
Hi,
Copy:
- the full name of the firmware file you used
-The full name of the rom file you use
-The full name of the recovery file you use/intend to use.
The name and version of current recovery installed.
Cheers,
Click to expand...
Click to collapse
Firmware file: fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0
ROM: PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL
Recovery I wanna use: PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL
Recovery I have installed to install the previous one: twrp-3.3.1-0-whyred.img
floater3 said:
Firmware file: fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0
ROM: PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL
Recovery I wanna use: PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL
Recovery I have installed to install the previous one: twrp-3.3.1-0-whyred.img
Click to expand...
Click to collapse
You have a problem because of the firmware (likely).
The order was supposed to be something like this, from an OREO recovery and OREO FW:
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom (PixelExperience_whyred-9.0-20190604-1615-OFFICIAL.zip at time of writing). Do not reboot
Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip. It will automatically reboot into recovery again.
I would:
-Flash the orange fox recovery from here (OrangeFox-R10.0_1-Stable-whyred.zip):
https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
It's supposed to support both oreo and pie. It should reboot in recovery again after flashing.
-Flash the FW (fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0.zip), hit reboot to recovery
-Flash your PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL.
Reboot into system and check.
If not, I would try reflashing the recovery with a proper OREO firmware and then
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom. Do not reboot
Flash Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip (pie) or V10 which is supposed to be oreo/pie. It will automatically reboot into recovery again.
Based on whatever mess it is now, you might have to do some wipes, try first the above then report.
htchd2sucks said:
You have a problem because of the firmware (likely).
The order was supposed to be something like this, from an OREO recovery and OREO FW:
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom (PixelExperience_whyred-9.0-20190604-1615-OFFICIAL.zip at time of writing). Do not reboot
Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip. It will automatically reboot into recovery again.
I would:
-Flash the orange fox recovery from here (OrangeFox-R10.0_1-Stable-whyred.zip):
https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
It's supposed to support both oreo and pie. It should reboot in recovery again after flashing.
-Flash the FW (fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0.zip), hit reboot to recovery
-Flash your PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL.
Reboot into system and check.
If not, I would try reflashing the recovery with a proper OREO firmware and then
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom. Do not reboot
Flash Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip (pie) or V10 which is supposed to be oreo/pie. It will automatically reboot into recovery again.
Based on whatever mess it is now, you might have to do some wipes, try first the above then report.
Click to expand...
Click to collapse
Hummm. it's happening a suspect thing! I made all the steps above, and I'm now flashing the ROM itself, and recovery is stuck at "Unpacking the original boot image".
floater3 said:
Hummm. it's happening a suspect thing! I made all the steps above, and I'm now flashing the ROM itself, and recovery is stuck at "Unpacking the original boot image".
Click to expand...
Click to collapse
Wait a bit maybe.
Just to make sure, verify the checksum of your downloaded files or redownload them again and compare the size. Just to be sure you have the proper files and they are completed.
htchd2sucks said:
Wait a bit maybe.
Just to make sure, verify the checksum of your downloaded files or redownload them again and compare the size. Just to be sure you have the proper files and they are completed.
Click to expand...
Click to collapse
It's everything right with files.
I'm still waiting... And it's strange because it's stuck on "Unpacking boot image" and the problem I was facing was associated with booting the system.
floater3 said:
It's everything right with files.
I'm still waiting... And it's strange because it's stuck on "Unpacking boot image" and the problem I was facing was associated with booting the system.
Click to expand...
Click to collapse
Can you check /tmp/recovery.log? ideally copying that in a pastebin.
We should look into doing the proper cleaning from recovery as well, (wipe, advanced wipes).
Do you have any data to save or can you clean flash all without problem?
htchd2sucks said:
Can you check /tmp/recovery.log? ideally copying that in a pastebin.
We should look into doing the proper cleaning from recovery as well, (wipe, advanced wipes).
Do you have any data to save or can you clean flash all without problem?
Click to expand...
Click to collapse
I can flash all. The need files are on the SD card. How do I check /tmp/recovery.log?
floater3 said:
I can flash all. The need files are on the SD card. How do I check /tmp/recovery.log?
Click to expand...
Click to collapse
You're supposed to adb pull /tmp/recovery.log.
Might not be needed, if you can simply do a wipe/advanced wipe, and a format of /data.
Note: it might not be necessary and you will delete things, it's just " the fastest way".
then you have to go through the flashing, again, I would even redo the fw as described earlier.
htchd2sucks said:
You're supposed to adb pull /tmp/recovery.log.
Might not be needed, if you can simply do a wipe/advanced wipe, and a format of /data.
Note: it might not be necessary and you will delete things, it's just " the fastest way".
then you have to go through the flashing, again, I would even redo the fw as described earlier.
Click to expand...
Click to collapse
I could flash the ROM but, still in bootloop... But it's curious! If I let my smartphone turned off for 10-15 minutes and then turn it on, Pixel Experience works and boots successfully but after some minutes of using, starts crashing, and reboots, again in bootloop
floater3 said:
I could flash the ROM but, still in bootloop... But it's curious! If I let my smartphone turned off for 10-15 minutes and then turn it on, Pixel Experience works and boots successfully but after some minutes of using, starts crashing, and reboots, again in bootloop
Click to expand...
Click to collapse
Hm it is indeed strange, as if something is corrupted...
What's the status now?
Any changes?
htchd2sucks said:
Hm it is indeed strange, as if something is corrupted...
What's the status now?
Any changes?
Click to expand...
Click to collapse
Still the same.... I tried again, with other recoveries.... Always the same thing! Bootloop.
But if I let it turned off for some time I can boot it (but after some minutes it automatically restarts and gets in bootloop again )
floater3 said:
Still the same.... I tried again, with other recoveries.... Always the same thing! Bootloop.
But if I let it turned off for some time I can boot it (but after some minutes it automatically restarts and gets in bootloop again )
Click to expand...
Click to collapse
It's clearly not related to recovery, at least, not directly.
-Check what "wipes" you have done, and ideally do all of them + format data (you can always reencrypt later). Then, reboot, and redo the flashing of everything.
-Another option would be to flash with "miflash" which I think will also restore some boot things. In that scenario, you are on your own because I don't know about ARB in your case and all potential issues.
I can only say that I did a "miflash" when I used to have ARBv3, and it went fine (I had to redo the recovery, etc... after).
I have been using xiaomi.eu beta rom for 6 months but after i updated to 9.9.3 phone first wiped all app permissions and day later it rebooted to twrp when i tried to reboot it said no os installed i rebooted anyway but it didnt booted so i go back to twrp to clear data then it said something with the unable to wiped with red text so i looked it up on google find out changing file system works but then last week it happened again so this time i decided to try if pixel experience rom does the same so i flashed latest android 9 rom and today it didnt wiped permissions but first froze and then stuck on bootanimation i dont know whats the problem please help
bdlkdrz said:
I have been using xiaomi.eu beta rom for 6 months but after i updated to 9.9.3 phone first wiped all app permissions and day later it rebooted to twrp when i tried to reboot it said no os installed i rebooted anyway but it didnt booted so i go back to twrp to clear data then it said something with the unable to wiped with red text so i looked it up on google find out changing file system works but then last week it happened again so this time i decided to try if pixel experience rom does the same so i flashed latest android 9 rom and today it didnt wiped permissions but first froze and then stuck on bootanimation i dont know whats the problem please help
Click to expand...
Click to collapse
Download the latest version of Global Stable - Fastboot images. Flash them in fastboot mode using the 'flash_all_...' script file that is included in the downloaded files. Be sure not to lock the bootloader. After it flashes successfully, flash the latest TWRP recovery. Boot to recovery and FORMAT data, then reboot and let the system setup. This should take care of any missing files/structure issues.
Agimax said:
Download the latest version of Global Stable - Fastboot images. Flash them in fastboot mode using the 'flash_all_...' script file that is included in the downloaded files. Be sure not to lock the bootloader. After it flashes successfully, flash the latest TWRP recovery. Boot to recovery and FORMAT data, then reboot and let the system setup. This should take care of any missing files/structure issues.
Click to expand...
Click to collapse
when i try to flash them fastboot mode doesnt confirm device is dipper so it doesnt start and if i try to use xiaomitool or fastboot command device gets out of fastboot mode and says press any button to shut down how can i fix that
bdlkdrz said:
when i try to flash them fastboot mode doesnt confirm device is dipper so it doesnt start and if i try to use xiaomitool or fastboot command device gets out of fastboot mode and says press any button to shut down how can i fix that
Click to expand...
Click to collapse
Don't use USB 3.0
mar.ur said:
Don't use USB 3.0
Click to expand...
Click to collapse
all my laptops ports are 3 is there any other way to fix that
bdlkdrz said:
all my laptops ports are 3 is there any other way to fix that
Click to expand...
Click to collapse
Use a hub USB