Related
Day 3 after purchasing, I managed to twrp, root and installed RR custom ROM. Went well. Next day, I wanted to try AICP ROM, I flashed it, but it was shutting down often so I moved to LOS 14. After that I saw PARANOID on the list by team Open Kirin, never did use it before so I jumped on it. I got my hands on PA- browser for the 1st time however I missed the flexibility of RR and decided to head back to RR. And that's where I met Mr.Bootloop. I took turns on shifting to LOS, AICP, RR, PA but
nothing worked. so I finally flashed Carbon ( which looped too).
* tried to went back to stock "update.zip +2 more zips" : didn't worked
* wipe data+ cache+vendor +cust + system* reflashed twrp recovery and didn't worked.
I asked few dev, but they seem busy for now. I feel stupid and really need some help.
I know it make no sense flashing n testing all.
If I come could get system, boot, recovery IMG of Duk-L09 (Asia), I think I could flash em with twrp adb sideload.. maybe?
Help this poor fellow please.
I've been using my honor 8 pro 2 months + , 1 month stock and 1 month with RR. i like the RR speed but it just drain too much battery when gaming so i decide to go back to stock b flashing update.app. Everything seems ok and manage to setup the phone to stock. But after i restart the phone here where the problem come, it stuck at error mode and i'm unable to go to fastboot mode nor recovery mode, it just stuck at the error mode screen even when power it off, it will auto power on again. Tried draining the battery and connect the phone to pc while holding vol - method but no success. End up i send my phone to the service centre. They have confirm my phone mobo died and they will replace it with a new 1. Hope your's not the mobo problem.
If you still able to go to fastboot mode with bootloader unlock and frp unlock, i think you're still able to flash your phone back to stock.
Can you boot to erecovery?
Sent from my Honor 8 Pro using XDA Labs
yes, I can boot on erecovery & twrp. flashing any ROM ends me up in bootloop. tried "dload" method with update.zip.
watched a youtuber's method of adb sideload. but still not booting up with the ROMs that worked before.
back on my old phone still looking for better XDA instruction
wyldemdd said:
I've been using my honor 8 pro 2 months + , 1 month stock and 1 month with RR.....
If you still able to go to fastboot mode with bootloader unlock and frp unlock, i think you're still able to flash your phone back to stock.
Click to expand...
Click to collapse
I didn't backed up, I was thinking I would be going back there. stupid me.
xdasith said:
yes, I can boot on erecovery & twrp. flashing any ROM ends me up in bootloop. tried "dload" method with update.zip.
watched a youtuber's method of adb sideload. but still not booting up with the ROMs that worked before.
back on my old phone still looking for better XDA instruction
Click to expand...
Click to collapse
Did you try extracting the update.zip and manually flash boot.img, vendor.img, system.img ? i remember i too have a bootloop when flashing RR the 1st time just because i wipe the vendor in twrp. flashing the vendor.img or zip fix the problem.
wyldemdd said:
Did you try extracting the update.zip and manually flash boot.img, vendor.img, system.img ? i remember i too have a bootloop when flashing RR the 1st time just because i wipe the vendor in twrp. flashing the vendor.img or zip fix the problem.
Click to expand...
Click to collapse
I have extracted "update.app" n tried "dload" folder update method only yet. I try to extract as you said from update.app.
New to huwaii device. to extract boot.IMG/system.img/vendor.IMG from update.app I hope there is a method for that or an app perhaps?
xdasith said:
yes, I can boot on erecovery & twrp. flashing any ROM ends me up in bootloop. tried "dload" method with update.zip.
watched a youtuber's method of adb sideload. but still not booting up with the ROMs that worked before.
back on my old phone still looking for better XDA instruction
Click to expand...
Click to collapse
xdasith said:
I have extracted "update.app" n tried "dload" folder update method only yet. I try to extract as you said from update.app.
New to huwaii device. to extract boot.IMG/system.img/vendor.IMG from update.app I hope there is a method for that or an app perhaps?
Click to expand...
Click to collapse
After extract the update.app from the update.zip, use huawei update extractor to extract system.img , boot.img , vendor.img from the update.app
step how to do that can be found here : https://forum.xda-developers.com/showthread.php?t=2315547
try to flash the vendor.img 1st, boot to twrp wipe data and re-flash your desire custom ROM. reboot to system and see does that fix the problem.
wyldemdd said:
After extract the update.app from the update.zip, use huawei update extractor to extract system.img , boot.img , vendor.img from the update.app
step how to do that can be found here : https://forum.xda-developers.com/showthread.php?t=2315547
try to flash the vendor.img 1st, boot to twrp wipe data and re-flash your desire custom ROM. reboot to system and see does that fix the problem.
Click to expand...
Click to collapse
vendor flashing failed. other than that system recovery boot all were executed fine.
if booted into the system, it say loads an empty screen.
if flashed custom : loops.
xdasith said:
vendor flashing failed. other than that system recovery boot all were executed fine.
if booted into the system, it say loads an empty screen.
if flashed custom : loops.
Click to expand...
Click to collapse
i remember in RROS thread you can download the flashable vendor..zip. try download it and flash thru TWRP and flash RROS.
wyldemdd said:
i remember in RROS thread you can download the flashable vendor..zip. try download it and flash thru TWRP and flash RROS.
Click to expand...
Click to collapse
yeah. I flashed vendor.zip from RR thread. after the failed attempt from flashing Vendor.IMG from update.app( after extraction).
still no good.
wyldemdd said:
i remember in RROS thread you can download the flashable vendor..zip. try download it and flash thru TWRP and flash RROS.
Click to expand...
Click to collapse
I tried that vendor.zip with RROS before. it worked really fine. but since loop with trying to go back after flashing 1 custom after another. I can't go back with any of those .
I replaced vendor zip first with RR too it didn't not seem to work.
I tried with two update.zip (L09 asia) I got from the net. didn't worked yet.
if any of you have gone back to stock n work. please guide me to it.
if I can go back I can go to LOS,again.
the link they shared in a YouTube "Dhananjay way" do stuck at 42%.
"dload" method by DroidTh might do good. but link expired.
The stock link by Morph= has No C6. section. the other update link shared here in XDA tagged " Indian link here" is the one which is giving me vendor.IMG failure.
In order to go back to stock, what I did is I flash the 2 stock recovery which is recovery.img and recovery2.img from extracted update.app. then flash boot.img, system.img, vendor.img. please don't lock bootloader while you don't have a working OS running or else you will stuck with a brick phone.
xdasith said:
I tried that vendor.zip with RROS before. it worked really fine. but since loop with trying to go back after flashing 1 custom after another. I can't go back with any of those .
I replaced vendor zip first with RR too it didn't not seem to work.
I tried with two update.zip (L09 asia) I got from the net. didn't worked yet.
if any of you have gone back to stock n work. please guide me to it.
if I can go back I can go to LOS,again.
the link they shared in a YouTube "Dhananjay way" do stuck at 42%.
"dload" method by DroidTh might do good. but link expired.
The stock link by Morph= has No C6. section. the other update link shared here in XDA tagged " Indian link here" is the one which is giving me vendor.IMG failure.
Click to expand...
Click to collapse
Why Indecisive flashes ? n ultimately landed on unusable brand new device?
(for me), cons+pros with CuSTomOS
i get with RROS/LOS: .
customized the "recent" to" grid view" . ( multi taskin+ ultra Customization)
though default settings drains power +abit more ram comparatively, but if tweak a lil : can optimized.
yet no dual sim disable hotkeys n WiFi hotkey turns on even if u put in no-scan mode.
AICP : is faster boot+ sided LOS addons + micro Gapps.
light, by default it doesn't consume much ram+CPU.
+ browser has "dev chrome dark with adblock + privacy "
Carbon is good too. neat. fast. but Both Carbon+AICP sacrifice some customizations tweaks
PA (non extended) .
it was last flashed till my me n my device parted. worked. n after that it died.
I'm like em all n new on Huwaii Honor, and stupid.
its been a week already. if unfixable I would like to sale it. but I still wanna know the problem. I will try Anything with Oreo/ LOS 15 available device.
wyldemdd said:
In order to go back to stock, what I did is I flash the 2 stock recovery which is recovery.img and recovery2.img from extracted update.app. then flash boot.img, system.img, vendor.img. please don't lock bootloader while you don't have a working OS running or else you will stuck with a brick phone.
Click to expand...
Click to collapse
I'll try this.. this post was more missing earlier. weird.
I haven't get back my phone from huawei service centre. After i've send for motherboard replacement, they broke my display with a burn mark on the screen, took out my screen protector i just bought few days back before the motherboard failed, with the reason my screen protector is a bit scratch. It's been 11 days now i'm without my Honor 8 pro. I end up buying a new phone which is OP5
wyldemdd said:
I haven't get back my phone from huawei service centre. After i've send for motherboard replacement, they broke my display with a burn mark on the screen, took out my screen protector i just bought few days back before the motherboard failed, with the reason my screen protector is a bit scratch. It's been 11 days now i'm without my Honor 8 pro. I end up buying a new phone which is OP5
Click to expand...
Click to collapse
its normally 14 days time they take..hope you get your device back.
wyldemdd said:
I haven't get back my phone from huawei service centre. After i've send for motherboard replacement, they broke my display with a burn mark on the screen, took out my screen protector i just bought few days back before the motherboard failed, with the reason my screen protector is a bit scratch. It's been 11 days now i'm without my Honor 8 pro. I end up buying a new phone which is OP5
Click to expand...
Click to collapse
hey! my device is back on stock and running after tweaked update.app, as divided in two "dloads" , and 1st "dload" without huwaii built in apps & account verification, and 2nd one with proper modules. now as good as new. No SRK tool, no flashing. just dumped modifed payloads in "SDcard/ dload"..1 after another. Il upload those files. after testing a lil more. its now ( after 700:+mb) updation. un-softbricked ! B150 September 5 patched version.
sorry to hear about ur late delivery. asked em to give a Samsung S8 as interest of borrowing n trolling delivery your kustomised H8pro.
xdasith said:
vendor flashing failed. other than that system recovery boot all were executed fine.
if booted into the system, it say loads an empty screen.
if flashed custom : loops.
Click to expand...
Click to collapse
xdasith said:
hey! my device is back on stock and running after tweaked update.app, as divided in two "dloads" , and 1st "dload" without huwaii built in apps & account verification, and 2nd one with proper modules. now as good as new. No SRK tool, no flashing. just dumped modifed payloads in "SDcard/ dload"..1 after another. Il upload those files. after testing a lil more. its now ( after 700:+mb) updation. un-softbricked ! B150 September 5 patched version.
sorry to hear about ur late delivery. asked em to give a Samsung S8 as interest of borrowing n trolling delivery your kustomised H8pro.
Click to expand...
Click to collapse
Good to hear that bro, yeah partial dload method works too, didn't know why i didn't suggest that at the 1st place . Well i'm demanding huawei to make a 1 to 1 exchange since i can't accept a scratch phone which is not there when i send it in. Hopefully i get my exchange soon
wyldemdd said:
Good to hear that bro, yeah partial dload method works too, didn't know why i didn't suggest that at the 1st place . Well i'm demanding huawei to make a 1 to 1 exchange since i can't accept a scratch phone which is not there when i send it in. Hopefully i get my exchange soon
Click to expand...
Click to collapse
I know why u didn't tell at first. You wanted me to miss my phone. Good job. Haha. Anyways, if they give S8 in exchange,u can get 1H8Pro + 256GB SDcard+headstone+another non-explosive MazeAlphaGama device by trading the S8. Btw S8+ battery last for long 3-hr max if used my way.
What's the status?Did They deliver u yet?
Hello!
Today I finally received permission to unlock my bootloader, after waiting a long 15 days (360 hours). After solving some MiFlash Unlock issues, I finally unlocked my phone. I flashed TWRP and Magisk, and then afterwards I flashed Xiaomi.eu's stable whyred ROM, which worked (including camera sensors), but was terribly slow and clearly very unoptimized. For this reason, I decided to flash the leaked official Global ROM, 9.5.6 from Xiaomi. All was well, and I was presented with the initial set-up screen. After selecting my language (English [United Kingdom]), I was forced to select China as my region on the next page. Seconds after selecting it, my phone reboot and opened the system again, only to reboot within seconds. This process would probably repeat endlessly if I didn't have it in fastboot mode. I can still access TWRP recovery, and my phone still shows that it's unlocked on the boot screen. I've tried doing another clean wipe, and then installation of the global ROM with no success (same error occurs, even when I tried English (United States)).
I've tried to use the MiFlash tool (2017.4.25) but my device isn't detected when I click Refresh, and the fastboot mode displays "press any key to shutdown...". I've tried many different drivers as I thought it was a driver issue, but now I'm not sure.
Any suggestions? Thanks!
Flash with fastboot rom. Follow my thread
devcon69 said:
Flash with fastboot rom. Follow my thread
Click to expand...
Click to collapse
I tried that, same issue. Also tried with the new 9.5.11 global rom update.
FIrst Flash MIUI Nougat Rom
http://bigota.d.miui.com/V9.2.7.0.NEIMIEK/miui_WHYREDGlobal_V9.2.7.0.NEIMIEK_b6ab1f7b5b_7.1.zip
after flashing this Rom and setup complete then flash the leaked official Global ROM, 9.5.6. Otherwise you won't be able to pass the setup screen in latest Oreo Rom.
Trewyy said:
I tried that, same issue. Also tried with the new 9.5.11 global rom update.
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...dmi-note-5-china-ai-to-leaked-global-t3782175
This one? Fastboot ROM will probably fix that as the bootloop is caused by a conflict with the remaining partitions from the last rom.
Flashing with MIFLASH Tool and selecting CLEAN ALL will clear that issue. Check Troubleshooting at end of the tutorial, it's already answered there. My first tutorial was to downgrade to nougat but that is not needed anymore as the fastboot rom for 9.5.6 is already available.
devcon69 said:
https://forum.xda-developers.com/re...dmi-note-5-china-ai-to-leaked-global-t3782175
This one? Fastboot ROM will probably fix that as the bootloop is caused by a conflict with the remaining partitions from the last rom.
Flashing with MIFLASH Tool and selecting CLEAN ALL will clear that issue. Check Troubleshooting at end of the tutorial, it's already answered there. My first tutorial was to downgrade to nougat but that is not needed anymore as the fastboot rom for 9.5.6 is already available.
Click to expand...
Click to collapse
Ah thank you, I was flashing through recovery. With that being said, MiFlash doesn't detect my phone in fastboot, even if I can normally flash to it through fastboot if I were to open a terminal. Clicking "Refresh" in MiFlash Tool just disables fastboot. I realize its unrelated to your own tutorial, as its probably some fault on my computer. Thanks for your replies!
hello xda friends!
after a very long time i've got my old xiomi a2 lite display repaired
the phone boots to twrp 3.3.1
beyond that my phone is completely empty
now i would like to give this phone away so i want to return it to stock
but it has been quite a while, i have no idea how to proceed anymore
so far all attempts at following several guides failed with red errors installing the zipped roms
can someone walk me through the process of returning my phone back to stock android
maybe even with some working links (since many of those i found were sadly dead), please?
tHISiSfINE said:
hello xda friends!
after a very long time i've got my old xiomi a2 lite display repaired
the phone boots to twrp 3.3.1
beyond that my phone is completely empty
now i would like to give this phone away so i want to return it to stock
but it has been quite a while, i have no idea how to proceed anymore
so far all attempts at following several guides failed with red errors installing the zipped roms
can someone walk me through the process of returning my phone back to stock android
maybe even with some working links (since many of those i found were sadly dead), please?
Click to expand...
Click to collapse
Download Official ROMs for Xiaomi Mi A2 Lite - Xiaomi Firmware
After the success of Xiaomi’s Mi A1 smartphone, it was very much expected that soon or later we’ll get its updated version. We already have a lot of fastboot and full OTA ROM updates available for download from official MIUI website. For your convenience we’ve collected the full list of the...
xiaomifirmware.com
You can download RECOVERY ROM (this is for flashing the rom via recovery)
or you can get FASTBOOT ROM ( this is for flashing the stuff via fastboot mode)
If you go with Recovery ROM then u will just have to download the zip file (latest preffered) to your laptop/pc. Then plug in your phone to your pc with an usb and transfer the zip file to your mobile device. Then go to INSTALL section and navigate to the directory where you transferred the file to and Flash it.
For installing the rom via fastboot first download one of the FASTBOOT ROM from the link i gave you (latest is preffered). After this extract the zip file on your pc. Go to the extracted folder. Now plug ur phone to the pc with usb and go to the fastboot mode (VOL DOWN + POWER BUTTON to go to fastboot. Or if you are on TWRP just go to the Reboot section and reboot the Bootloader/Fastboot from there) .Double click on the flash_all.bat (if on windows) or flash_all.sh (if on linux) it should flash all the stuff you need into it's place. Make sure u are on Fastboot Mode before running the flash_all file.
sorry, i suck at explaining
thank you.
it worked with fastboot and i am back to stock android!
tHISiSfINE said:
thank you.
it worked with fastboot and i am back to stock android!
Click to expand...
Click to collapse
no problem :good:
TLDR below
Some of the backstory of this device:
This is my girlfriend's first android device, tried so hard to convince her to switch from iPhone to Android, I finally managed to convince her, but... this happened...
So since this is not my device and I wanted a pure Android 12 experience (which I bragged about), I installed Pixel Extended Android 12 Beta to the device. (Only android 12 experience that I got during that time)
This is what I did,
Unlocked the bootloader after 7 days ( using Miunlocktool )
With the phone still in factory firmware, I used pixel extended's recovery image which is located here https://sourceforge.net/projects/pex-alioth/files/1-11-21/
Steps that I did ( fastboot flash boot boot.img > fastboot flash vendor_boot vendor_boot.img > fastboot reboot recovery > Format data > adb sideload PEX.zip > Reboot )
After rebooting, the phone is now in PEX4.0 beta and she proceed to use the devices for several months after PixelExperience released their stable ROM for OTA updates and zero maintenance from my side.
When PixelExperience released their stable ROM, took her phone, trying to shut down the phone so I can go into fastboot and I realized that the phone isn't powering on at all which no display, plugged into my PC, no USB indicator as well.
The phone is dead from a shutdown which shocked me. My guess initially is some kind of electric damage that ruined the motherboard. So I sent this to Xiaomi's service center to get this fixed.
After picking up the phone from the service center yesterday, I have been told that the phone is hard bricked and not some kind of faulty hardware. I am pretty sure they reflashed the firmware with Xiaomi flash tool and it is now running on the global ROM 12.5, with an unlocked bootloader
Feeling weird at the hard brick, I thought I messed up somewhere.
On my second attempt to install PixelExperience, I managed to go into fastboot and sideloaded the zip into ADB. This is the command I used.
( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
With the sideload showing success message Total xfer: 1.00x I restarted the device and found that the device is now hard bricked once again.
Super confused, I double-checked the recovery img and ROM to make sure that the files aren't corrupted. Prior to installing, I also made sure to update my ADB and fastboot to the latest version.
----
TLDR
After getting phone hard bricked for the first time, on my second attempt to load a custom rom, the phone hard bricked again.
( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
Click to expand...
Click to collapse
What could go wrong here?
Upon typing here I think I forgot to do a wipe data before reboot, will this cause the phone to hard brick?
I guess I am sending this phone to the service center tomorrow again, made this thread to know what can I do to make sure this doesn't happen again.
Will I be better off using TWRP instead of their custom recovery image?
Am I messing up something here that caused the phone to hard brick? This image is also the exact image my POCO f3 is currently running which I sideloaded successfully and still running fine.
Should I do an update on MiUI before proceeding to install a PixelExperience?
Should I do a reflash after recovering the phone from Xiaomi's service center?
Could this be some kind of hardware problem?
I ordered my phone online but purchased her phone in the store, are there any differences here?
Any help or input is really appreciated, I have been doing this for quite a while now and never faced such an issue before.
I don't know a lot about bricks in general but i think you are supposed to format data after you flash the recovery because that's what i did after installing arrow os but i don't know how would that cause a hard brick.
PE a12 rom is busted that's why that thread is closed.
Your device is in EDL mode. Contact authorized users to unbrick your phone. Will cost you around $25-$30
regedit12345 said:
PE a12 rom is busted that's why that thread is closed.
Your device is in EDL mode. Contact authorized users to unbrick your phone. Will cost you around $25-$30
Click to expand...
Click to collapse
The problem is I have another exact device which is running the latest version of PE fine.
jylee1997123 said:
The problem is I have another exact device which is running the latest version of PE fine.
Click to expand...
Click to collapse
Yeah i know. your device got bricked because it got updated via the OTA and the pixel firmware got flashed on your device that why your device is in EDL mode.
regedit12345 said:
Yeah i know. your device got bricked because it got updated via the OTA and the pixel firmware got flashed on your device that why your device is in EDL mode.
Click to expand...
Click to collapse
I think there is some confusion here.
Are you referring to the first hard brick? No OTA update is performed because it is running PEX which does not support OTA updates.
If you are referring to the second hard brick, the phone is never in PE firmware at all. The moment I tried to flash PE rom, the phone got hard bricked with these steps. ( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
2 Devices
1) My personal device (POCO F3 Alioth) - Working fine with current latest stable PE
2) Her device (POCO F3 Alioth) - HardBricked, EDL when flashing with these steps ( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
jylee1997123 said:
TLDR below
Some of the backstory of this device:
This is my girlfriend's first android device, tried so hard to convince her to switch from iPhone to Android, I finally managed to convince her, but... this happened...
So since this is not my device and I wanted a pure Android 12 experience (which I bragged about), I installed Pixel Extended Android 12 Beta to the device. (Only android 12 experience that I got during that time)
This is what I did,
Unlocked the bootloader after 7 days ( using Miunlocktool )
With the phone still in factory firmware, I used pixel extended's recovery image which is located here https://sourceforge.net/projects/pex-alioth/files/1-11-21/
Steps that I did ( fastboot flash boot boot.img > fastboot flash vendor_boot vendor_boot.img > fastboot reboot recovery > Format data > adb sideload PEX.zip > Reboot )
After rebooting, the phone is now in PEX4.0 beta and she proceed to use the devices for several months after PixelExperience released their stable ROM for OTA updates and zero maintenance from my side.
When PixelExperience released their stable ROM, took her phone, trying to shut down the phone so I can go into fastboot and I realized that the phone isn't powering on at all which no display, plugged into my PC, no USB indicator as well.
The phone is dead from a shutdown which shocked me. My guess initially is some kind of electric damage that ruined the motherboard. So I sent this to Xiaomi's service center to get this fixed.
After picking up the phone from the service center yesterday, I have been told that the phone is hard bricked and not some kind of faulty hardware. I am pretty sure they reflashed the firmware with Xiaomi flash tool and it is now running on the global ROM 12.5, with an unlocked bootloader
Feeling weird at the hard brick, I thought I messed up somewhere.
On my second attempt to install PixelExperience, I managed to go into fastboot and sideloaded the zip into ADB. This is the command I used.
( enable USB debugging > adb reboot bootloader > fastboot flash boot PE_recovery.img > adb sideload PE.zip > Reboot )
With the sideload showing success message Total xfer: 1.00x I restarted the device and found that the device is now hard bricked once again.
Super confused, I double-checked the recovery img and ROM to make sure that the files aren't corrupted. Prior to installing, I also made sure to update my ADB and fastboot to the latest version.
----
TLDR
What could go wrong here?
Upon typing here I think I forgot to do a wipe data before reboot, will this cause the phone to hard brick?
I guess I am sending this phone to the service center tomorrow again, made this thread to know what can I do to make sure this doesn't happen again.
Will I be better off using TWRP instead of their custom recovery image?
Am I messing up something here that caused the phone to hard brick? This image is also the exact image my POCO f3 is currently running which I sideloaded successfully and still running fine.
Should I do an update on MiUI before proceeding to install a PixelExperience?
Should I do a reflash after recovering the phone from Xiaomi's service center?
Could this be some kind of hardware problem?
I ordered my phone online but purchased her phone in the store, are there any differences here?
Any help or input is really appreciated, I have been doing this for quite a while now and never faced such an issue before.
Click to expand...
Click to collapse
dont use pixel extended ive too had motherboard bricking issues with it pixel experience works perfectly for me with no issues
Zainullahk1234 said:
dont use pixel extended ive too had motherboard bricking issues with it pixel experience works perfectly for me with no issues
Click to expand...
Click to collapse
That is what I thought initially as well. However, PE disappointed me as well with the 2nd hard brick. Did I miss any step that caused this? Or this is PE related?
Try flashing aospa.
jylee1997123 said:
That is what I thought initially as well. However, PE disappointed me as well with the 2nd hard brick. Did I miss any step that caused this? Or this is PE related?
Click to expand...
Click to collapse
hmm i dunno then pe works perfectly on my x3 pro
are you sure your using the correct firmware?
try flashing miui firmware over it and booting (cause mabye the oss vendor is the issue)
or just sell your f3 and get the f4 once it comes out (looks to have snapdragon 8 gen 1!)
Try installing CrDroid, follow their installation steps, they work very well
I think most stable Aosp rom for poco f3 is Arrow Os don't use PE again
usmanjavid said:
I think most stable Aosp rom for poco f3 is Arrow Os don't use PE again
Click to expand...
Click to collapse
You definitely haven't tried PPUI
regedit12345 said:
You definitely haven't tried PPUI
Click to expand...
Click to collapse
LOL
dont mention that buggy mess
regedit12345 said:
You definitely haven't tried PPUI
Click to expand...
Click to collapse
i tried installing this instead of arrow os and i couldn't even boot into it it would just go back to miui
Zainullahk1234 said:
LOL
dont mention that buggy mess
Click to expand...
Click to collapse
I have tried all the A12 roms including syberia and arrow and by far this is the best rom. The maintainer of the rom is dev himself and very active and responsive on the telegram grp.
[Discontined][12.0][alioth/aliothin] Pixel Plus UI Poco F3 / Xiaomi Mi 11X / Redmi K40
This tread was discontined as far as I dropped support of PixelPlusUI Project. Thanks to all users and supporters who was Interested to project. Future Development for Poco F3 will be according to own new project - VoidUI Project Github...
forum.xda-developers.com
Well, thank you all for the suggestion. But I am not trying to find a rom that suits me or has fewer bugs. I am trying to figure out what goes wrong during my installation or if I missed something.
Is PE really that bad? I have been using them for quite a while now though
i have seen pixel extended that got his thread closed because at shutdown the phone bricked so it really is the roms fault
jylee1997123 said:
Well, thank you all for the suggestion. But I am not trying to find a rom that suits me or has fewer bugs. I am trying to figure out what goes wrong during my installation or if I missed something.
Is PE really that bad? I have been using them for quite a while now though
Click to expand...
Click to collapse
Pixel extended= bad
pixel experience= amazing
jylee1997123 said:
Well, thank you all for the suggestion. But I am not trying to find a rom that suits me or has fewer bugs. I am trying to figure out what goes wrong during my installation or if I missed something.
Is PE really that bad? I have been using them for quite a while now though
Click to expand...
Click to collapse
That's why I suggest using CrDroid, mostly because I haven't failed any installation following their installations steps, the ROM being stable and having good customizations is a perk that comes with it
Hi all,
I hope someone will be able to guide me as how to recover from this.
So today I tried flashing my POCO F3 with MIUI 14 (xiaomi.eu_multi_HMK40_POCOF3_V14.0.4.0.TKHCNXM_v14-13) from the stock version MIUI 12.
I first successfuly unlocked the bootloader using MiUnlock. I then unlocked the developer options , usb unbugging etc. again on the fresh phone.
I also had USB / ADB and fastloader drivers installed.
I downloaded xiaomi.eu_multi_HMK40_POCOF3_V14.0.4.0.TKHCNXM_v14-13 , phone was already in fastboot and connected to the computer so run 'windows fastboot first install with data format' as an administrator which opened the cmd , after agreeing it started flashing the first few files successfully but when it gets to " Sending 'cmnlib64_ab' (504 KB) " the process just stopped there and it has been like this for around 30 mins - no error ...simply stuck on this step .....
I am not sure on what to do now to avoid bricking my phone, should I leave it connected ? Disconnect it and try flashing it again ? Download an older version of Xiaomi.Eu ROM (e.g MIUI 13 ) ?
Leave it connected for about 1 hour or so until you get success or error confirmation. If failed just reboot to system. If system failed to show up then go to fastboot again and install xiaomi.eu a12 version.
This is exactly why I hate fastboot method and always install rom from twrp
Flash 14.0.5 via orangefox recovery.
I left it overnight and nothing happened . I disconnected the phone and it rebooted ok. I am kind of worried about trying again. Is the twrp method safer ?
Just discovered that I stupidly set the "USB debugging (Security settings) on but I forgot to turn on "USB debugging" which is a few lines above in settings. Could that be what has stopped the process?
Phone should flash fine even if debugging is off. I would recommend you to make sure that the cable doesnt even move an inch during the whole flashing process as that sometimes interrupts it especially if you have a loose port.
I just switched the usb port from the back of the pc (which I think are USB 3.0) to the front panel of the PC (I suspect USB 2.0 ) and tried flashing the MIUI 14 from yesterday again - It worked !!!!
*Deleted
Hi,
You could check out my post,
Fastboot not working in Windows 11 [Resolved]
Hello! I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this? It shows up as 'Android' in device manager. I've also attempted to install a drivers manually...
forum.xda-developers.com
I hope it might help for the future
Hi...
Is it possible to flash a ROM that says "...V12.0.6....V12-10" for example, on a device that shipped with MIUI 11 Android 10, directly, without first updating the device to MIUI 12 normally?
Carl_OX said:
Hi...
Is it possible to flash a ROM that says "...V12.0.6....V12-10" for example, on a device that shipped with MIUI 11 Android 10, directly, without first updating the device to MIUI 12 normally?
Click to expand...
Click to collapse
you can do if you flash the fastboot version by mi flash tool, and your bootloader is unlocked.
mogamycool said:
you can do if you flash the fastboot version by mi flash tool, and your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks... I really appreciate the early reply.
But can't I do this using the recovery method? And also must the android and miui versions of both the global stock rom and custom rom be the same?
Nevermind...thanks for your help
if you want to flash specific version of android, then you need unlocked bootloader and mi flash tool, otherwise make updater app do its job. and no need for the global stock rom and custom rom be the same. just put in your mind to backup your data .
mogamycool said:
if you want to flash specific version of android, then you need unlocked bootloader and mi flash tool, otherwise make updater app do its job. and no need for the global stock rom and custom rom be the same. just put in your mind to backup your data .
Click to expand...
Click to collapse
Thanks boss