Long story short:
EDIT: I somehow magically (after 2 hours of trying) got into recovery, cleaned and wiped everything and booted into MIUI. Switched to CM 12.1, leaving this thread for anyone that experiences the same problem.
1. I was running CM11-R24, with an early version of the Xcelerate kernel. All was fine and well but today it restarted on its own a couple of times. It would enter a bootloop that I managed to get out of by going into recovery and rebooting from there.
2. Bootloop happened again, couldn't get into recovery.
3. Installed newest twrp recovery via fastboot. No change.
4. Managed to hardbrick my phone by installing a wrong .img of a global version.
5. Managed to revert back to a softbrick by installing the right (hopefully) global version of my mobile phone.
6. I did manage to read a logcat inbetween and I remember there being something about the kernel settings being nulled to default, because there was a failed boot 2 times in a row.
Links:
Hard-brick to soft-brick procedure I followed - http en.miui.c o m thread-54139-1-1.html
Used global version: Singapore 50? Going to try other versions
Settings in MiFlash tool (using 2014.11 version). - http postimg.o r g /image/hh122e54j
Current problems:
1. When powering up the phone, it will not go beyond the Mi logo.
2. When trying to enter recovery (volup+power) I enter another loop. It is normally 10-15 seconds of Mi logo, power down, 3-5 seconds of Mi logo, power down. Repeat. I do not stop holding the recovery combination while this happens.
3. I have installed via fastboot all of these recoveries - TWRP 2830, TWRP 2860, Philz latest recovery. After installing each of them, I can not enter recovery mode again. Flashing a new recovery doesn't seem to change that.
I have access to fastboot, currently I installed the stable fastboot rom version "armani_images_JHCCNBH45.0_4.3_cn_e7e373f319".
I can not get adb to recognize the device, only fastboot. Can't get a logcat because of it. If you think I might be doing it wrong, please walk me through the process.
How do I get it back to working condition? The phone was bought in Bulgaria from a retailer, but I don't know which country it was originally shipped from, only that it's a WCDMA version.
Throw it away and get your self some reliable phone unlike redmi , it's a crap lots of issue ... I prefer Motorola .
ford.sushil said:
Throw it away and get your self some reliable phone unlike redmi , it's a crap lots of issue ... I prefer Motorola .
Click to expand...
Click to collapse
Oh oh oh don't be rude everyone has his own priorities and financial limitations
Bootloop
Dude, I have the same problem, can you help plus?
Redmi Note 8 Pro - The Megathread
Background
Xiaomi sent many of us the Redmi Note 8 Pro (Indian variant - begoniain) back in November 2019. Development started out great, but came to an abrupt halt, when at one point all of us were bricked. A little bit of caution and a bit more of tinkering, and we're back!
Long story short, yes this device does brick, and yes there IS a method to avoid it! I request you to take out some time and read the entire post, before you proceed. Following instructions is crucial, if you want to save yourself trips to the service center.
begonia? begoniain? what's happening?
There are 2 variants of the Redmi Note 8 Pro. "begonia" is the global variant whereas "begoniain" is the Indian variant. The only difference between the 2 is NFC. The Indian Variant has no NFC. And no, it's not as if it's disabled, the hardware is just not present. The TWRP and ROM builds target both, so you do not have to worry about a thing. Irrespective of where you bought the phone, all custom software is the same, and will run on both variants.
Unlocking the bootloader and gaining root
This has been covered by other threads in the past, so I won't dive into too much detail here. You need to unlock your device using the Unlock Tool that Xiaomi provides and wait for almost a week (168 hours) to gain unlock permissions. There's no way to get around this. Please follow any other guides for installing a recovery, flashing Magisk, disabling AVB and booting up.
Custom ROMs and bricking
Regarding bricks, yes this device will get bricked if you do stupid things or don't follow instructions. Feel free to ask if you ever have a doubt. Do NOT spam on ROM threads. Ask here, and use search before you do. Chances are, someone has asked the same thing in the past.
Now, doing things like:
- Tripping AVB
- Flashing an incompatible boot and dtbo
- Flashing a weird boot image
- ???
will result in a brick. You won't have fastboot, you won't have anything in such cases. Only Boot ROM download mode, which requires a Mi Authorized Account. In such cases, you will need to visit a service center.
PLEASE NOTE: I do NOT recommend online services that promise to unbrick your device. Not only are they highly overpriced, but could result in you getting scammed, or have your data stolen. If you have a Mi Authorized Account and are willing to help us out, feel free to PM me. Any online service ads for the same will NOT be entertained.
Now, there is a way to prevent bricks entirely. However, it does not work with the MIUI 11 Android 10 China build that surfaced a few months ago. The factory firmware for begonia was leaked, @Xakep1993 discovered that the factory had a lot of security checks disabled, and compiled in engineering mode.
Before we go any further, know that there is no way for you to unbrick a phone that's already bricked and is running the MIUI preloader. (Visit a Service Center in such a case) The following applies only to devices that are in a good, working state and will prevent bricks.
Okay so how does that help?
Glad you asked. Every MediaTek device has 2 download connections. Boot ROM (aka BROM) and Preloader. Boot ROM is burnt onto the SoC and is the first program to run. Preloader is loaded after. Boot ROM implements security measures against attacks, which includes flashing improper or malicious firmwares. This is "SLA" and "DAA", that is "Serial Link Authentication" or "Download Agent Authentication". This happens server side and requires the Mi Authorized Account, that only service centers have.
What's so different with this firmware?
Preloader runs after BROM, and does not require any security verification to write partitions. MIUI's preloader has download disabled. When you brick, you have Preloader starting and rebooting constantly. (And holding volume up gets you to BROM download). There's no way to talk to the MIUI Preloader. The Factory Preloader on the other hand, has download enabled. So, if something goes wrong, as long as the Factory Preloader is present you CAN unbrick!
How to install it?
If you are on MIUI 11 - Android 10, you WILL need to downgrade to Android 9! This method will not work if you're on Android 10. Use MiFlashPro or fastboot to flash all partitions to a compatible MIUI 10 or 11 Android 9 build.
I will add a zip that can be flashed from TWRP, soon. Until then, you can flash it via Fastboot.
1. Download preloader_begonia.bin and lk.img from attachments
2. Execute
Code:
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
(LK = Little Kernel = Bootloader)
You can now use SP Flash Tools to restore your "bricked" phone!
This will also make the bootloader append certain debug flags to the kernel cmdline. So you may see some interesting behavior while Android is running!
You can find the full factory build here. This is a barebones MTK-Android build. We don't recommend using it xD
Where are my Custom ROMs? ETA PL0Z BRO!!!
They're almost ready now, you should see threads popping up in a few more days.
Okay, thanks for the "anti-brick" factory preloader! I'm gonna flash another MIUI build!
Hol' up, fam. You need to check whether the MIUI OTA you're installing contains Preloader and LK or not. If it does, remove it manually. Another method could be to install the OTA and then flash the factory Preloader and LK image again via fastboot.
Flashing ROMs
Once ROMs are out, the install process is very simple and much like any other device:
- Download ZIP
- Push ZIP to device
- Flash using TWRP
- Install GApps (optional)
- Reboot
- Profit!
Unbricking
Assuming you have the factory preloader installed,
- Disconnect device from PC if connected
- Load SP Flash tool
- Load firmware of choice
- Press download, SP Flash tool will now wait for the device
- Connect device and don't hold any keys
- If the device doesn't detect, hold power for a 8-10 seconds
- It should start flashing right away without any authorization prompt!
Building ROMs (Developers only)
Things are still under development. Things may be broken, may or may not boot at all. Current code can be found below:
Device Tree - branch android-10
Vendor Tree - branch android-10
Kernel - branch master
DTBO Patch
Info about the patch: many partitions of the device (including DTBO) are signed using private keys. We don't have access to these keys, and thus our generated dtbo images don't boot. I managed to strip out the certs, write a simple Python script and write custom dtbo generation rules that append the required certs.
Things may be missing here, more information will be added as necessary
XDA:DevDB Information
The go-to modding guide for the Redmi Note 8 Pro (begonia/begoniain), ROM for the Redmi Note 8 Pro
Contributors
Agent_fabulous
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2020-02-24
Last Updated 2020-10-26
CFW and CFW builds and recoveries
CFW[SIZE="+1"]What is a CFW?[/SIZE]
The A10 Custom Firmware, or CFW for short, is a combination of multiple Xiaomi firmware packages.
[SIZE="+1"]Why do I need it?[/SIZE]
You are probably aware of the leaked factory firmware for the Redmi Note 8 Pro. This firmware contains a preloader which was compiled with the download code.
Since the preloader does not need to setup platform security it allows us to unbrick without an authorized account.
Unfortunately, the MIUI bootloader do not run on the factory preloader - only the factory bootloader does, which works just fine with A9 kernels.
Furthermore, the A10 kernel source released by Xiaomi does not work with the factory bootloader/preloader, which was the reason I worked on a new kernel source based on Android 9 (A9) with several Android 10 (A10) drivers to work nicely with the A10 blobs.
In short, the CFW enables you to use the new builds without worrying about bricks while running newer proprietary vendor software.
[SIZE="+1"]What's special about the new builds?[/SIZE]
New builds, tagged "[CFW]", come with their own vendor images. These builds are unified for all variants of the Redmi Note 8 Pro and have pretty much all issues fixed at this point. They ship with the new modified A10 kernel I mentioned earlier.
NOTE: While the builds are unified, the CFW is not. Please flash the correct version of CFW, for your variant
While flashing the wrong CFW is not catastrophic, it may lead to issues such as poor reception.
[SIZE="+1"]What really is inside this CFW?[/SIZE]
The CFW contains firmware files from the latest A9 and latest A10 firmware image. Along with this, the CFW also installs the factory preloader and bootloader (LK) to make sure you're safe when modifying your device.
[SIZE="+1"]How do I install the CFW and builds?[/SIZE]
CFW is a recovery-flashable package. You WILL HAVE TO downgrade to MIUI A9 to flash this since there are no recoveries which work nicely with MIUI A10.
Even though the CFW does install factory preloader and LK, I do highly recommend flashing preloader and LK from fastboot first and then the CFW.
Once you are sure you are running the CFW, simply flash a CFW compatible build. You may also need to update your recovery after installing CFW. See next post for full step-by-step instructions.
[SIZE="+1"]Recoveries? How do those work with CFW?[/SIZE]
Since recovery images also contain their own kernel, there are also CFW compatible recovery images. After installing a CFW, reboot to fastboot and flash any CFW enabled recovery image.
Trying to run a non-CFW recovery on CFW will make it reboot to system or recovery itself after a few seconds of entering recovery. Should you find yourself in a situation like this: as soon as recovery loads, hit [reboot] > [bootloader]. If you cannot do this, flash the new recovery image from SP Flash tools (or wait for your device to drain it's battery out )
See next post for full step-by-step instructions.
[SIZE="+1"]Do I need to flash the CFW everytime?[/SIZE]
Nope. If you flashed CFW once, you're good. Just make sure the ROM you're flashing does not install any firmware images. Ask your ROM developer before installing a zip.
ALL MIUI ZIPS CONTAIN FIRMWARE IMAGES. DO NOT FLASH ON TOP OF CFW
[SIZE="+1"]I'm on CFW and rocking a custom ROM. How do I go back to MIUI?[/SIZE]
Flash a full MIUI Fastboot ROM, or use SP Flash tools to install the flash all MIUI partitions. Again, do not flash a recovery package for switching to MIUI.
See next post for full step-by-step instructions.
[SIZE="+1"]What would happen if I install a non-CFW build on CFW?[/SIZE]
Again, nothing catastrophic. It'll make the device reboot itself a few seconds into the bootanimation. All current non-CFW builds run the A9 kernel code. The new kernel is based on the A9 kernel code as well; some drivers just don't like the new firmware images included in the CFW So, save yourself the trouble and check what you're installing. CFW supported builds are listed in the next post.
[SIZE="+1"]Where can I download the CFW?[/SIZE]
Please see the next post, below.
While the whole CFW thing may seem a bit overwhelming to some, remember, it's something to protect your device in the long run! Take out a few minutes and please read through this post properly.
Reserved
CFW Migration Steps
Coming from MIUI
Method 1
- Downgrade to MIUI Android 9 if not already, or try using Method 2
- Flash preloader and lk as mentioned in first post
- Flash any non-CFW Android 9 recovery
- Boot into recovery
- Wipe system, cache, dalvik
- Flash CFW, CFW compatible ROM (flash GApps mods later! )
- Format data (not wipe, select "Format Data", you'll lose all userdata)
- Reboot to bootloader
- Flash CFW recovery
- Reboot! You're now on CFW!
Method 2 Try at own risk!*
- Flash a non-CFW A10 recovery from fastboot (such as LR TWRP for MIUI A10)
- Boot directly into recovery by holding [Volume +] after flashing and rebooting
- (Optional) For safety sake, select Advanced option "Close AVB 2.0"
- Take a full nandroid backup (IMPORTANT! Will be helpful if lost IMEI)
- Turn off "Reboot after installing ROM" from TWRP settings
- Wipe system, dalvik and cache
- Flash CFW and a CFW compatible ROM (flash GApps and mods later! )
- Format data (not wipe, select "Format Data", you'll lose all userdata)
- Reboot to bootloader from the Reboot menu
- Flash CFW recovery
- Reboot! You're now on CFW!
*NOTE: This method has worked for each everyone who has tried it and followed correctly, so far. The idea for this method was mine, but I personally have not tried it myself. It will particularly be useful if you're using MIUI A10 and are on a limited data plan
Coming from non-CFW Custom ROMs
- Make sure preloader and LK are installed (see first post)
- Boot into recovery
- Wipe system, cache, dalvik
- Flash CFW, CFW compatible ROM (flash GApps here if necessary, flash any extra mods later! )
- Format data (not wipe, select "Format Data", you'll lose all userdata)
- Reboot to bootloader
- Flash CFW recovery
Updating CFW-enabled builds on CFW
Since you're already on CFW, just install the update and reboot like any other device:
- Remove lockscreen if any
- Reboot to recovery
- Wipe data, system, cache, dalvik
- Flash ROM (+ GApps if necessary)
- Reboot!
Going back to MIUI from CFW
- Flash full MIUI firmware from SP Flash Tools or fastboot
Android 11
Changes
- Update to MIUI 12 blobs and fw images
- Prebuilt vendor image for A11
- Fully enforced and vendor isolation enabled
Coming from A10 CFW
- Flash "CFWv3+vendor" package followed by the ROM.
Note: You don't need to flash the "CFWv3+vendor" package more than once when switching to other A11 ROMs, unless you have gone back to A10.
Coming from MIUI
- Follow instructions above to CFW, just use A11 CFW and A11 ROM instead
Going back to A10 CFW
- Flash CFWv2 along with your A10 ROM.
Going back to MIUI
- Fastboot flash full MIUI ROM
Note 1: Do not wipe vendor on A11. If you do, you'll have to reflash the "CFWv3+vendor" package to have a functional device.
Note 2: On VNDK30 A11 builds, you may wipe vendor, since the builds ship with a vendor image.
CFW Downloads
Android 11 (CFWv4) For VNDK-30 builds only! (is the same as CFWv2.1, but version changed to avoid confusion )
- begoniain: https://sourceforge.net/projects/begonia-oss/files/CFW/begoniain-A11-CFW_20210105.zip/download
- begonia: https://sourceforge.net/projects/begonia-oss/files/CFW/begonia-A11-CFW_20210105.zip/download
Android 11 (CFWv3+vendor)
- begoniain: https://sourceforge.net/projects/be...egoniain-A11-CFW-vendor-20201026.zip/download
- begonia: https://sourceforge.net/projects/begonia-oss/files/CFW/begonia-A11-CFW-vendor-20201026.zip/download
Android 10 (CFWv2)
- begoniain: https://sourceforge.net/projects/begonia-oss/files/CFW/begoniain-A10-CFW_20200823.zip/download
- begonia: https://sourceforge.net/projects/begonia-oss/files/CFW/begonia-A10-CFW_20200823.zip/download
CFW Supported Recoveries
- Unofficial TWRP
- Anything else marked with "[CFW]"
CFW Supported ROMs and kernels
- Pretty much everything active, at this point lol
The latest non-CFW Unofficial TWRP can be found on AFH, on my thread (see last line on post) and in the Telegram group as note "#twrp-non-cfw-for-roms"
Troubleshooting
IMEI lost (requires full TWRP backup of MIUI when IMEI was present!):
From a full TWRP backup, restore the following partitions:
- nvcfg
- nvdata
- nvram
- persist
- protect_f
- protect_s
Reboot and check! IMEI should be back :highfive:
ROM Reboots to recovery after boot logo (no bootanimation):
Usually, this indicates that the device isn't able to setup encryption. You'll also see randomly named files and folders in TWRP. In this case, just Format Data (not wipe), and reboot.
Rescuing the device:
Since CFW is always running factory preloader and bootloader (LK), you can use SP Flash in case something should go wrong.
Assuming you're stuck in some sort of loop/brick while on factory preloader/CFW, here are the EDL modes:
There are 2 modes of "EDL":
- Preloader: Factory preloader will always advertise a download mode when the device is starting, right before the Redmi logo (You may not get a logo if you're bricked, only a blinking LED). You do not need to hold ANY buttons. Just plug in the device and it'll show up on your computer periodically. Load any Android 9 firmware in SP Flash, uncheck preloader, lk and lk2, connect your device and hit Download in SP Flash.
- BootROM: If you don't have factory preloader, you will have to flash via BootROM. This requires an authorized account. Unless you have one yourself, you will need to head to a service center to get your device fixed. If you do need to load BootROM download, hit download in SP Flash with the Authorized Account logged in, hold volume up and plug in the device while holding the key. Release the key as soon as your computer recognizes it. SP Flash will start the download.
If you are able to enter this mode yourself, and the service center quotes something like a "motherboard replacement", show them this section of the post and tell them it's a software issue. Given the nature of such a new and unique device, often even the best make mistakes! If you're a XIaoMi Service Center and a customer has showed this to you, PLEASE try this. The phone will enter BootROM if you hold the keys at the correct time. You do not need to take the phone apart to short any pins. Just login and bind to your special account, hit "Download" in SP Flash and hold the keys for 5-15 seconds with the device plugged in. The software will recognize the device and start flashing.
If you as the technician are wondering why you should trust a random person on the internet, here's why: I received the device from XiaoMi India, as part of their developer program and have been reversing things on it for the past 6+ months. I have been through 3 hard-bricks and have helped multiple service centers diagnose the device correctly and having them fix my own device too.
The following "Booting different modes" is obsolete in CFWv2! Latest CFW menus behave like MIUI.
Booting different modes:
The key combinations on factory bootloader are a little different:
- Power + Vol Up:
This loads a menu. You can change between different boot modes with volume up and select the mode with volume down.
- Power + Vol Down:
Unlike MIUI, this loads a factory testing menu. Do not open this. If you do load it by accident, hold power button to force reboot.
Use The Power + Vol Up menu for Fastboot
According to a user on Telegram, here's what the menu translates to:
Code:
The title is Factory Mode
The first is automatic testing
The second is manual test
The third is a single test
The fourth is the test report
The fifth is debugging test items
The sixth is to clear emmc
The seventh is version information
The eighth is to restart the mobile phone.
Wow!!! Thanks man! Does it work with custom firmware such as xiaomi.eu or miuipro based on China builds?
Nice!
Remember only ANDROID 9 Rom !!
DAMN!
P.S: Snapdragon ftw
Oh thanks @Agent_fabulous you are the best
Great thread
Great thread. I'm super excited.
I haven't flashed any thing on my phone before, can i flash this preloader??
This thread explains greatly. Thanks!
Great work!!!
Is there a preloader for Xiaomi Redmi 6? It's also on the mediatek, but it has a different processor. Unfortunately, it's hard bricked
Thank you for all the info and work!
1. Download preloader_begonia.bin and lk.img from attachments
2. Execute
Code:
Code:
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
Click to expand...
Click to collapse
Just for clearrefining. Do we need to flash TWRP first? Or is it safer to use the factory firmware first?
Thanks
Dan
Thank you very much, we are looking forward to more custom ROMs coming!
Super excited.. We're going to be busy next week
Great news. So if we remove lk.img, preloaded.img, preloader_emmc.img, preloader_ufs.img from (original) image / rom, we should be safe to flash without permanent brick right?
Looks like this is the good news we've all been waiting for.
Danmann said:
Just for clearrefining. Do we need to flash TWRP first? Or is it safer to use the factory firmware first?
Thanks
Dan
Click to expand...
Click to collapse
Greetings @Danmann.
From what I can read in the Original Post, quoted bellow for reference:
Agent_fabulous said:
[...]
Before we go any further, know that there is no way for you to unbrick a phone that's already bricked and is running the MIUI preloader. (Visit a Service Center in such a case) The following applies only to devices that are in a good, working state and will prevent bricks.
Click to expand...
Click to collapse
This thread/measures are therefore PREVENTIVE and certainly not CURATIVE.
Knowing probably 99% of people who bricked their devices did it trying to flash TWRP, I think it is safe to assume by all means, it is highly recommended to flash this BEFORE you attempt to flash TWRP.
That said I never had issue with the few releases of TWRP either from OP or LR team, but what I would do is probably first getting stock image of your current MIUI (NOTE: ANDROID 9 ONLY AS SAID BY OP) to get the original files you are about to replace just in case.
You still have to unlock your bootloader if not done already.
First of all, hurray Agent and Xakep1993!!
Second. Feeling stupid, but I don't see any atachments to post:/.
Agent_fabulous said:
1. Download preloader_begonia.bin and lk.img from attachments
Click to expand...
Click to collapse
jumper047 said:
First of all, hurray Agent and Xakep1993!!
Second. Feeling stupid, but I don't see any atachments to post:/.
Click to expand...
Click to collapse
Just bellow the thread Tittle, you have a black bar with tabs you can click on. One of them being Download
Don't feel stupid I was also feeling dumb yesterday before I found that bar lol
Hope this helps.
Regards,
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:
I guess the title already says it all, but just in case:
I tried to put LineageOS on this used XZ2 I bought a few days ago, everything went fine until side loading the Lineage image. Appaerently there as some data corruption and the installation failed halfway through... unfortunately the phone dropped out of recovery mode and has been stuck in a boot-loop ever since.
I can still access the phone via fastboot after the battery runs out and before it goes into its bootloop again, even managed to flash the recovery image (in boot_b if that's important) - but somehow seem unable to actually boot into recovery... given that I have still access via fastboot, the situation might still be salvageable?
also tried booting the phone-specific twrp via fastboot boot <twrp>.img but that sadly also sent me back into the boot loop.
fastboot reboot recovery also sends me to the bootloop
any other ideas?
Did you format (not wipe!) /data before booting LOS?
Thanks for the reply!
I followed these instructions but something failed at the end:
Install LineageOS on xz2c | LineageOS Wiki
wiki.lineageos.org
but later yesterday I was able to find somewhat of a work around. Since from browsing this forum many people seemed to have had similar issues, here is what worked for me:
- break out of the reboot-loop and shut down the phone by pressing and holding volume up + volume down + power button
- the phone should vibrate about 3 times to confirm
- download your phones standard firmware via xperifirm
[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.6.5]
[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.6.5] NOTE: This thread is the only official source of XperiFirm! Websites like xperifirm.com and xperifirmtool.com were not authorized to redistribute my software! XperiFirm... Allows you to...
forum.xda-developers.com
- download new flasher
[TOOL] Newflasher (xperia command line flasher)
Disclaimer: newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick...
forum.xda-developers.com
- put the phone into flashmode - press and hold volume down, connect the usb cable, and then also press and hold power, the phone should go into flash mode indicated by a green led
- follow the instructions (basically put the newflasher executable into the firmwarefolder created by xperifirm and execute
if everything goes well you should recieve a functioning (but wiped) device. still better than a paper weight
---------------------------------------------------------------
edit: tried to flash LOS again, but same error as first time (Error applying update: 28 (kdowloadoperationexecutionerror)
which prevents me from successfully installing LOS... I only found this:
[GUIDE][HOW TO FIX] 28 (ErrorCode::kDownloadOperationExecutionError) | 5 (ErrorCode::kPostInstallRunnerError)
In this short guide, I will explain to you how to easily fix the recovery error, the name of which can be found in the title. This guide is only a collection of information found on the Internet and a simple explanation of the problem. It was...
forum.xda-developers.com
which kinda explains the issue, but not how to fix it in my case on my device... any suggestions?
edit2:
tried over 10 different firm wars ranging from the latest 18.1 to some older 17.1, tried via the official lineageos recovery image and also via twrp.. always the same result... installation failed
I have been trying for over 3 hours now... but I just can't find (nor fix) the issue)
Hey so I was having this same issue and seem to have resolved it by doing a firmware upgrade using the oxygen firmware located here. I already have twrp installed and had no issues logging into the recovery, but i could never get logged into the system. Using twrp i just moved the oxygen file onto the phone and flashed it directly from the recovery. I then switched to the partition i installed it to and it booted up. It looks like i had everything right except for the firmware. Good luck!
[Download] Stable OxygenOS 11 For OnePlus 6/6T Based on Android 11
Stable OxygenOS 11 For OnePlus 6 and 6T just rolled out for OnePlus 6 and 6T. Download Android 11 based on OxygenOS 11 for OnePlus 6/6T.
www.androidsage.com
iitzzMalice said:
Hey so I was having this same issue and seem to have resolved it by doing a firmware upgrade using the oxygen firmware located here. I already have twrp installed and had no issues logging into the recovery, but i could never get logged into the system. Using twrp i just moved the oxygen file onto the phone and flashed it directly from the recovery. I then switched to the partition i installed it to and it booted up. It looks like i had everything right except for the firmware. Good luck!
[Download] Stable OxygenOS 11 For OnePlus 6/6T Based on Android 11
Stable OxygenOS 11 For OnePlus 6 and 6T just rolled out for OnePlus 6 and 6T. Download Android 11 based on OxygenOS 11 for OnePlus 6/6T.
www.androidsage.com
Click to expand...
Click to collapse
Hmmm.. I just realized you're using a different phone than me. My bad. Hopefully it helps that i had the same issue and resolved it by using oxygen firmware. Good luck to you!
thanks for the response
I think I identified the issue, which might be very much firmware related.
Essentially because my phone has the wrong stock firmware and LOS refuses to install on that despite being the same hardware as the "supported" firmware.
so what I probably need is a way to install H8314 firmware on an SO-05K model... there's a thread about that, but so far I have not been successful
(alternatively altering the LOS firmware itself to install on the SO-05K...)
Hi Guys,
I hope every one is doing well. I have been on the latest Paranoid Android Sapphire Beta 1 build for the last few days. I have been liking the rom so far but I would need to go back to stock OOS for now. Aside from using MSM tool is there another way to flash back stock OOS zips via recovery? I tried sideloading via AOSPA's recovery but it failed (no worries, as I am still able to boot to AOSPA just fine).
Kind regards!
You can try this,,https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Salilsarkar said:
You can try this,,https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Click to expand...
Click to collapse
Many thanks! I was having issues downloading the stock firmware files needed for the MSM tool. I do have the downgrade zip and ota signed zip for my model, but extracting with payload dumper gives me only 7 image files so I think it's incomplete, and I would still need to download the full firmware files to be able to flash via fastboot.
If you try using fastboot to downgrade, you're very likely going to brick and have to use the MSM anyway.
blitzkriegger said:
Hi Guys,
I hope every one is doing well. I have been on the latest Paranoid Android Sapphire Beta 1 build for the last few days. I have been liking the rom so far but I would need to go back to stock OOS for now. Aside from using MSM tool is there another way to flash back stock OOS zips via recovery? I tried sideloading via AOSPA's recovery but it failed (no worries, as I am still able to boot to AOSPA just fine).
Kind regards!
Click to expand...
Click to collapse
I was able to flash to oos11 using twrp. Well, I was on crdroid and there are custom ROMs that require oos12 before It will work. So I went crdroid 8.6 to oos11 to oos 12 and then lineage 19
Well it was a ride for me lol. Took me a few hours to realize I can gain fastboot access via long pressing power button+volume up and volume down altogether. I was then able to reflash the modded magisk boot image to regain access to AOSPA.
The fun part came after trying to flash back to stock via MSM. First I figured out that instead of using the "vol up+vol- button approach then connect usb" way of trying to get MSM tool to connect to the EDL mode of the phone, an easier method is to use "ADB reboot edl" command.
Now as I previously used global stock OOS, I mistakenly used the MSM tool for the global region. However, this got me in a SHA-256 mismatch in the flashing process, causing a flash error which got me back to getting stuck at the bootloader again. Turns out the global MSM tool does not work for LE2120 model.
So at this point I had 2 options - either find a MSM tool that works, or try flashing back to stock via fastboot. The fastboot way would have worked but I ran into a problem - you have to flash to .img files partly via fastboot, then partly via fastbootd. And when on fastbootd my phone is not recognized by the PC (this is why trying to flash back AOSPA also failed, it can't continue the fastbootd part of the install as for some reason my pc loses connection with the phone on fastbootd).
My saving grace was I found out that for LE2120, the EU version of the MSM tool works. So long-story short I got back to stock OOS 12 again. It was a fun yet nerve wracking experience, and I learned a lot.
So the lesson of the story is, for anyone tinkering with this device, to learn the basics, from knowing your correct model number, knowing the proper button combinations to boot to fastboot/edl/recovery, knowing which tools to use, to knowing how to setup/troubleshoot your pc to ensure the phone communicates properly at every step!