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,
Related
Hi everybody,
I try to root my Blackview BV9500 by installing first TWRP recovery. I use fastboot mode on a linux laptop to do that.
I successfully flash the twrp recovery image, but after that, the phone don't boot in recovery anymore.
It try to boot into recovery, but it reboot in normal mode a few second after.
I tried also with the cmd "fastboot boot recovery.img".
When i flash back the original recovery image, it work, i can boot the original recovery without any problem.
Does anyone have the problem?
Some one can help me to find a solution?
I, too, am trying to do this. I have not yet flashed it... I was going to use the fastboot boot command to boot the recovery kernel before permanently flashing it, to make sure it would work, and in my googling I stumbled across this post. Serendipity! [Edit 3: Although, reading your post again, I see you tried that as well and it didn't succeed for you. For me, it simply tells me remote: command not found, so how were you able to even get that to work?]
All that said... I have the BV9500 Pro, specifically for the two-way radio, so I'm going to try to keep that little tidbit of hardware working in the process. I mainly just want to tweak the menus a bit, tweak the quick settings, get root, delete the Google crapps I won't be using...
On to your problem, though, I can't help much but maybe if we post back and forth our successes and failures we might be able to stumble through it together?
First, I assume you already have unlocked your bootloader? [Edit: Honestly, I'm not sure flashing the recovery would be allowed without first unlocking the bootloader]
[Edit 2: Perhaps this thread might be of help. Different model, but often the hardwares used by manufacturers are similar enough that the same steps generally work. ]
Thank you for the link, maybe i need to flash the complete rom with the twrp recovery with spflash tools, and it will work.
I will try and let you know, but i will make a backup of my rom before flashing it!
For your problem with fastboot, maybee it's because you need to install it. You can use the command "sudo apt-get install fastboot" on a terminal window if you are on linux.
If you want to enter the recovery mode, you don't need to use fastboot, you can simply enter it by pressing Volume Up and Power buttons together for a couple of seconds when your phone is off.
When Boot Mode appears release all keys.
To flash recovery with fastboot, you need first to enable the developer mode on your phone (go to "Settings > About phone" and make 7th tap on the build number, the Developer options will be unlocked and available), and unlock the bootloader of course.
here what is the process i made to flash the recovery :
- i use the command "adb devices" to check if the phone is well connected. (response is like "BV9500S320001179 device")
- then i enter in fastboot mode with "adb reboot bootloader" (phone reboot and ask confirmation for fastboot mode)
- check with command "fastboot devices"
- unlock the bootloader with the command "fastboot oem unlock" or "fastboot flashing unlock".
- flash the phone with the twrp recovery with "fastboot flash recovery recovery.img"
- reboot the phone in recovery mode with "fastboot boot recovery.img"
Normally the phone boot in twrp recovery.
Hope that will help you too.
I am too facing this problem. In case you got any solutions please let me know too.
Yves596 said:
For your problem with fastboot, maybee it's because you need to install it. You can use the command "sudo apt-get install fastboot" on a terminal window if you are on linux.
Click to expand...
Click to collapse
Yup. Already had fastboot installed for the LG G5 this phone replaced, the Galaxy Note 4 the LG replaced, the MyTouch 4G Slide the Galaxy replaced, my wife's old Galaxy S5 I used in the interims... LOL, I've got a working install. No, the "Remote: command not found" was returned from within.... Whether fastboot or adb, I forget now, but I was able to get the file to flash eventually, after reading your first post, but unfortunately the phone would not boot to it (nor Android). I thought I'd bricked it. Twice this happened. Each time, after about 5 minutes, it eventually booted to Android.
I flashed the recovery from the ROM in the link Blackview sent me and was able to boot their recovery just fine, so there's something in the TWRP that my particular phone doesn't like.
If you want to enter the recovery mode, you don't need to use fastboot, you can simply enter it by pressing Volume Up and Power buttons together for a couple of seconds when your phone is off.
When Boot Mode appears release all keys.
Click to expand...
Click to collapse
Thanks, I keep forgetting which keys to hold for recovery versus bootloader, so I use the adb command to be sure without having to keep a notepad nearby.
Clearly I don't do this as often as I used to.
(snip)
- flash the phone with the twrp recovery with "fastboot flash recovery recovery.img"
- reboot the phone in recovery mode with "fastboot boot recovery.img"
Normally the phone boot in twrp recovery.
Hope that will help you too.
Click to expand...
Click to collapse
Now that was something I haven't done since the T-Mobile G1 days. My understanding was that you CAN boot a recovery without flashing it first if you"fastboot boot {image filename}" but that didn't work for me either. I'm also assuming that the filename to flash can be anything because the device stores it to a partition, so it shouldn't have to be specifically "recovery-verified.img".
The recovery you have... Were you ever able to boot to it? If so, would you be willing to share a link to its download source, please?
I've got to run for a prior engagement, I'll check back later.
Thanks!
veronicadavis said:
I am too facing this problem. In case you got any solutions please let me know too.
Click to expand...
Click to collapse
I guess i find the reason why the modified recovery image won't boot.
I find an interesting information in a post of osm0sis (https://forum.xda-developers.com/showthread.php?t=2073775) were he say : "some newer MediaTek (MTK) devices use special image signing that adds a "BFBF" pre-header signature, so images will unpack/repack but most likely won't boot unless run through their internal signing tool."
After more search, i find an interesting publication (http://www.lieberbiber.de/2015/07/04/mediatek-details-partitions-and-preloader/) witch confirm that.
They say in conclusion of the publication :
"Yes, I can confirm that SignTool is able to add digital signature information to firmware images. Signed images have an additional header “BFBF” and some fluff which SP Flash Tool checks on a secure device. Apparently some manufacturers merely used the default MTK key for signing the images, making them no better off than a typical insecure MTK device."
So we have to find another way to install magisk to root it.
Root 9500/pro
Mine rooted already....you guys can check on 4pda russian forum
Note : do not use the 17.1 version of magisk there because after reboot the device will freeze if you resboot after twrp 1st install...instead flash 17.3+ or 18+ right after first install of twrp...
EDIT : dont mind the russian language in TWRP as you can change it to english once there
Yves596 said:
Hi everybody,
I try to root my Blackview BV9500 by installing first TWRP recovery. I use fastboot mode on a linux laptop to do that.
I successfully flash the twrp recovery image, but after that, the phone don't boot in recovery anymore.
It try to boot into recovery, but it reboot in normal mode a few second after.
I tried also with the cmd "fastboot boot recovery.img".
When i flash back the original recovery image, it work, i can boot the original recovery without any problem.
Does anyone have the problem?
Some one can help me to find a solution?
Click to expand...
Click to collapse
Hello I have same problem... Do you have that original recovery file? I don't have and I would like to get that back. Thanks.
DL this:
needrom. com/ download/bv9500pro- bv9500-root/ (delete spaces)
- Copy Magisk-v18.0.zip and disable_encryption_9500.zip to external SD-Card or OTG device
- backup your data from internal SD-Card
- do a factory reset and turn off phone without entering the setup guide after reboot, or wipe via recovery and power off
- Flash recovery.img using scatter.txt with SP Flash Tool
- boot into recovery with hold down vol + and power
- switch TWRP to your language and install Magisk-v18.0.zip and disable_encryption.zip
- reboot and update or install MagiskManager-v6.1.0.apk
Thanks to Jemmini from 4pda.ru
kanadali said:
DL this:
needrom. com/ download/bv9500pro- bv9500-root/ (delete spaces)
- Copy Magisk-v18.0.zip and disable_encryption_9500.zip to external SD-Card or OTG device
- backup your data from internal SD-Card
- do a factory reset and turn off phone without entering the setup guide after reboot, or wipe via recovery and power off
- Flash recovery.img using scatter.txt with SP Flash Tool
- boot into recovery with hold down vol + and power
- switch TWRP to your language and install Magisk-v18.0.zip and disable_encryption.zip
- reboot and update or install MagiskManager-v6.1.0.apk
Thanks to Jemmini from 4pda.ru
Click to expand...
Click to collapse
Thank you for your help and Jemmini help too, it work fine.
But on the firmware version 20180629.
Yves596 said:
Thank you for your help and Jemmini help too, it work fine.
But on the firmware version 20180629.
Click to expand...
Click to collapse
you can just download latest firmware and simply backup NVRAM etc with sp flash tool also flash with sp tool, you will have then working twrp with disabled encryption. there are tons of post regarding using sp flash tool on this forum
im using same phone and did these actions on first day and did not have any problem with twrp or magisk
Hi,
I've bought this phone in Pro version. I rooted my phone using needrom.com/download/bv9500pro-bv9500-root/ and adb after unlocking bootloader. Then I failed with errors. Then I used SPFlashTool in root mode with official 2018092919_s32v63c2k_jk_pro.rar rom (I don't find it anymore on the net but 1) I got it on Blackview official forum and 2) I have the file on my own PC) with format+Download and replace recovery with TWRP from Jemmini from 4pda.ru before flashing. OK.
Then I rooted again: format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally.
Beware: TWRP is in Russian language at first boot, so to get it in English, first slide the first slide (allowing writing), then select 'Настройки', then the globe on top, then English, then 'Установитъ Язык'.
Hope this helps.
Then, this is my first rooted phone, so I plan to make a custom rom without Gapps (then maybe without Mediatek Ones and agold too) and remake all functionning with apps from Fdroid. Help needed on a manner of removing a system/vendor app properly. Help needed too to add V4A, as I could see max version supported is Nougat. I announce this here as my first post, but my project will be a full post. If someone want help please ask here or MP me
Note: an update of magisk is out (official 18.1), I installed it and my phone tells me a message that facial recognition was not working anymore then it only boots on TWRP... I reflashed it and my phone boots normally again. Wait and see...
Thanks to Jemmini from 4pda.ru again.
Bests Regards
nr0000000 said:
Hi,
I've bought this phone in Pro version. I rooted my phone using needrom.com/download/bv9500pro-bv9500-root/ and adb after unlocking bootloader. Then I failed with errors. Then I used SPFlashTool in root mode with official 2018092919_s32v63c2k_jk_pro.rar rom (I don't find it anymore on the net but 1) I got it on Blackview official forum and 2) I have the file on my own PC) with format+Download and replace recovery with TWRP from Jemmini from 4pda.ru before flashing. OK.
Then I rooted again: format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally.
Beware: TWRP is in Russian language at first boot, so to get it in English, first slide the first slide (allowing writing), then select 'Настройки', then the globe on top, then English, then 'Установитъ Язык'.
Hope this helps.
Then, this is my first rooted phone, so I plan to make a custom rom without Gapps (then maybe without Mediatek Ones and agold too) and remake all functionning with apps from Fdroid. Help needed on a manner of removing a system/vendor app properly. Help needed too to add V4A, as I could see max version supported is Nougat. I announce this here as my first post, but my project will be a full post. If someone want help please ask here or MP me
Note: an update of magisk is out (official 18.1), I installed it and my phone tells me a message that facial recognition was not working anymore then it only boots on TWRP... I reflashed it and my phone boots normally again. Wait and see...
Thanks to Jemmini from 4pda.ru again.
Bests Regards
Click to expand...
Click to collapse
It'd be great to have another rom but I'm facing a problem with battery life. Basically mobile network standby drains 5000mah battery every day i turned off from developer option but still problem is there. I have checked every single post on Google but nobody has solution for this. U guys face this problem too?
kanadali said:
It'd be great to have another rom but I'm facing a problem with battery life. Basically mobile network standby drains 5000mah battery every day i turned off from developer option but still problem is there. I have checked every single post on Google but nobody has solution for this. U guys face this problem too?
Click to expand...
Click to collapse
New update has been released today. It solves some battery issues, but be very careful.
I installed it, having TWRP and now I'm stuck in TWRP. I've tried to wipe everything but I'm still in TWRP.
I'll try SPFlashTool ... hope it works.
Everything restored & updated.
Using SPFlashTool I flashed all files included in 2018092919_s32v63c2k_jk_pro.rar (including original recovery instead of TWRP).
After that, Android booted and then, using OTA, I updated to latest version.
Reflected_God said:
New update has been released today. It solves some battery issues, but be very careful.
I installed it, having TWRP and now I'm stuck in TWRP. I've tried to wipe everything but I'm still in TWRP.
I'll try SPFlashTool ... hope it works.
Click to expand...
Click to collapse
Could you please send me the link? Can't find it on blackview forum
kanadali said:
Could you please send me the link? Can't find it on blackview forum
Click to expand...
Click to collapse
The latest version is not on the forum. I installed via OTA.
But if you mean the previous firmware, there is one link on the blackview forum: http://bbs.blackview.hk/viewtopic.php?t=480235#p795494
SP Flash tools are well documented here: https://forum.xda-developers.com/showthread.php?t=1982587
And a complete list of blackview bv9500 / bv9500 pro files and instructions (in russian): https://4pda.ru/forum/index.php?showtopic=931296
Hope you find what you are looking for.
@kanadali,
for the moment I'm not facing battery drain because there is not simcard in it at this state of my modifications, sorry.
@Reflected_God,
I think this is the link I used, I use the 2018092919_s32v63c2k_jk_pro.rar rom for base.
For all others who faces big problems like me (facial recognition not working then reboot on twrp only, I could reflash my phone with SPFlashTool, the rom and twrp from Jemmini/4PDA in russian only (others don't work for me). I used Format + Download in root mode on Linux. Then format /data with TWRP, then install disable_encryption.zip, wipe dalvik, reboot on TWRP, then install Magisk, wipe dalvik, reboot normally. Do other things. To remove gapps I disabled/force stop it before remove with TWRP. Others apps I can't disable simply remove with TWRP. I test if I encounter bugs but none for the moment. If someone wants to know what I do I've made a LibreOffice Calc sheet log, which evolve when I have time
Hope this helps
Bests Regards
Need Files or a GOOD guide. bv9500 NOT PRO.
If someone could upload the exact files that they used, and the exact same steps, that would be great. Please mention what stock version you have and a link to the image if possible as well. I've followed numerous different guides, with multiple different rom versions, multiple different recovery imgs, used sp flash tool and adb/fastboot multiple times, tried making sure everything was unlocked before each try, have all the necessary drivers, and the closest I get to a functional twrp recovery is a green line that appears at the top of the boot screen before it reboots. Ive tried going to the source, the russian site, but all of the links are 404ed. if not for me, then it would be great to just have this all in one place. Thank you please future hero.
Please include exact program versions (ex SP Flash) as well if not zips of them. I am sorry to be asking so much in one post however I truly didn't know what else to do. And I am typically very good with my google fu xD
I currently have build number BV_BV9500_V1.0_20181026. That seems to matter I believe.
I second the notion.
I have the pro model. I have considered rooting it, but honestly, the phone works well enough as-is without root (for me). However, I'd LOVE to be able to play with different ROMs on this device **AS LONG AS I CAN MAINTAIN THE TWO-WAY UHF TRANSCEIVER FUNCTIONALITY** (i.e. not some "needs-a-network-of-some-kind" "walkie talkie app" like Zello but the real UHF two-way), and I'd LOVE the ability to play with the files associated with the radio to really explore the hardware's capabilities.
Unfortunately, this phone seems more popular in [North]eastern Asia than anywhere else so I don't think we're likely to get much on this forum regarding it unless and until BV become a popular name in the western hemisphere.
So I was experimenting with aosp gsi roms last month and I thought of going back to stock ROM.
I tried beta flashy, it didn't work
So I flashed the images from UPDATE.APP file to their respective partitions through TWRP.
--Rebooting.. --
--Black Screen--
Nothing works -
1. It doesn't boot to fastboot by usb cable method
2. It doesn't boot to recovery by power button, volume button combinations
3. The phone doesn't even give the usual buzz when power button is held for a few seconds
4. Of course ADB won't work
5. The device is now a paperweight
I have resorted to my laptop for whatsapp and online classes but I miss my Honor 7x BND AL10, I even had a dream that it got fixed last week
Any suggestions on how to fix this would be highly appreciated
Uk, generally any problem like this arose on my mediatek devices, I would flash them using SP Flash Tools which just need a working RAM to flash the firmware
no important data?
IDT 2.0 and flash board firmware, can find it here mabye
Huawei Board Software | Easy Firmware
easy-firmware.com
that website charges money but you can search the name of the firmware
HL1BNDMAA001064 for example
this will most definetly get you device booted, from here you have to install stock rom with matching CUST from original
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...)
Just this day, November 23, 2021, I have been trying to flash a custom rom named Syberia OS for daisy(Mi A2 Lite variant). As I have done booting up the device to fastboot(thru cmd command since my power button is jammed), I installed the twrp after booting the image to the device, making it as my recovery.
Now I am set and excited to install the rom, so I went to fastboot again and tried to flash the rom, but it always errors and not installing the rom. It is said "to flash multiple zips, reboot recovery before..." (correct me if I'm wrong), so I rebooted to recovery thru the twrp (since its in fastboot). Now, I did the same, I installed the rom again and experienced the same error so I dont know what to do, I did wiped system, data, dalvik and internal storage (a lot of times and tried to install the rom again), but I get the same error.
Then since I cant install the rom, I went to reboot to system thru twrp, and then I forgot, that I have no OS installed.
So now I'm stuck with the "Your device software can't be checked for corruption. Please lock the bootloader. Please visit this link..." plus arriving to the AndroidOne logo, and it turns off and turns on again with the message and logo, repeats until the battery is completely empty.
Is there anything I could do to go to fastboot again for a clean install of the stock rom? (I promise to not unlock the bootloader and experiment on custom roms again)
(I am sorry if you find it hard to understand, I am willing to edit this thread for better understanding if there are things you dont understand.)
This is what I see after all that happened...:
Your browser is not able to display this video.
Any form of response and acknowledgements will be much appreciated )
@hachi_eight
Please read the guidances that are stuck on top of every forum prior to your next posting like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator
hachi_eight said:
Just this day, November 23, 2021, I have been trying to flash a custom rom named Syberia OS for daisy(Mi A2 Lite variant). As I have done booting up the device to fastboot(thru cmd command since my power button is jammed), I installed the twrp after booting the image to the device, making it as my recovery.
Now I am set and excited to install the rom, so I went to fastboot again and tried to flash the rom, but it always errors and not installing the rom. It is said "to flash multiple zips, reboot recovery before..." (correct me if I'm wrong), so I rebooted to recovery thru the twrp (since its in fastboot). Now, I did the same, I installed the rom again and experienced the same error so I dont know what to do, I did wiped system, data, dalvik and internal storage (a lot of times and tried to install the rom again), but I get the same error.
Then since I cant install the rom, I went to reboot to system thru twrp, and then I forgot, that I have no OS installed.
So now I'm stuck with the "Your device software can't be checked for corruption. Please lock the bootloader. Please visit this link..." plus arriving to the AndroidOne logo, and it turns off and turns on again with the message and logo, repeats until the battery is completely empty.
Is there anything I could do to go to fastboot again for a clean install of the stock rom? (I promise to not unlock the bootloader and experiment on custom roms again)
(I am sorry if you find it hard to understand, I am willing to edit this thread for better understanding if there are things you dont understand.)
This is what I see after all that happened...:
View attachment 5466081
Any form of response and acknowledgements will be much appreciated )
Click to expand...
Click to collapse
Hey brother, I had the same situation a few months ago. My device - Redmi 6 (Cereus).
So, I was trying to install TWRP in Redmi 6 and then after trying many times TWRP successfully got installed. But when I tried to boot the device, It stuck in bootloop (Going to fastboot and again booting...). So, the answer is that you first boot into fastboot mode of your device and then download the fastboot Rom of your device, (link of fastboot rom of your device - https://xiaomifirmware.com/download/18010/ ) . Then go to your PC and then extrac
the fastboot file, then connect your phone to pc and go to fastboot mode then open the extracted folder and then click on flash-all (The batch file) and then a new command window will open automatically and flashing process will start. After it's done your phone will reboot automatically. For reference, go ahead. Best of luck!
hachi_eight said:
Just this day, November 23, 2021, I have been trying to flash a custom rom named Syberia OS for daisy(Mi A2 Lite variant). As I have done booting up the device to fastboot(thru cmd command since my power button is jammed), I installed the twrp after booting the image to the device, making it as my recovery.
Now I am set and excited to install the rom, so I went to fastboot again and tried to flash the rom, but it always errors and not installing the rom. It is said "to flash multiple zips, reboot recovery before..." (correct me if I'm wrong), so I rebooted to recovery thru the twrp (since its in fastboot). Now, I did the same, I installed the rom again and experienced the same error so I dont know what to do, I did wiped system, data, dalvik and internal storage (a lot of times and tried to install the rom again), but I get the same error.
Then since I cant install the rom, I went to reboot to system thru twrp, and then I forgot, that I have no OS installed.
So now I'm stuck with the "Your device software can't be checked for corruption. Please lock the bootloader. Please visit this link..." plus arriving to the AndroidOne logo, and it turns off and turns on again with the message and logo, repeats until the battery is completely empty.
Is there anything I could do to go to fastboot again for a clean install of the stock rom? (I promise to not unlock the bootloader and experiment on custom roms again)
(I am sorry if you find it hard to understand, I am willing to edit this thread for better understanding if there are things you dont understand.)
This is what I see after all that happened...:
View attachment 5466081
Any form of response and acknowledgements will be much appreciated )
Click to expand...
Click to collapse
Check in the guides section for mi a2 lite. Do a little search before asking. This one
user-001 said:
Check in the guides section for mi a2 lite. Do a little search before asking. This one
Click to expand...
Click to collapse
i fixed it, i opened the back of the phone and managed to fix the power button, and used the combo to get to fastboot mode, and reinstalled the stock OS. so, now I fixed it!
hachi_eight said:
i fixed it, i opened the back of the phone and managed to fix the power button, and used the combo to get to fastboot mode, and reinstalled the stock OS. so, now I fixed it!
Click to expand...
Click to collapse
I am having same issue. What did you do fix the power button?
Steps I've done:
1. Unlocked bootloader, OEM unlock is enabled
2. Downloaded and installed Samsung Drivers
3. Download TWRP / SHARP Recovery
4. Downloaded Odin
5. Got my phone into Download mode (KG State - Checking, FRP - off, OEM LOCK - off)
6. Ran Odin, device detected in Odin
7. Put the tar file into the AP
8. Clicked "Start" in Odin, passed successfully
9. Holding Volume Down, Volume Up & Power Button
10. Released Volume Down on black screen
11. Released Power Button on Samsung logo
12. Still holding Volume Up button
That's how far I was able to come. The device just bootloops itself and I can't get it to open TWRP / SHARP. Got it into download mode again and flashed it with the stock firmware, but want to install custom ROM through the TWRP / SHARP. First time trying to flash custom rom, am I doing something wrong? Any help appreciated.
Reference:
[RECOVERY][Official] TWRP 3.7.0_11 for Galaxy A50
*** Disclaimer I am not responsible for any damage you made to your device You have been warned Features: Android 11, 12 and 13 support Supported Devices: A505F A505FN A505G A505GN A505GT Downloads...
forum.xda-developers.com
GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI.
Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI. - GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP r...
github.com
You need to connect type c cable to boot into twrp.
Connect your phone to computer or laptop or tv with cable , then use key combination to boot to twrp.
Press power key and volume up at the same time when your phone connected to pc with cable.
Sharath Mane said:
You need to connect type c cable to boot into twrp.
Connect your phone to computer or laptop or tv with cable , then use key combination to boot to twrp.
Press power key and volume up at the same time when your phone connected to pc with cable.
Click to expand...
Click to collapse
Type C cable has been connected from pc to the phone since booting into download mode, as it is required. Even after exiting the download mode and trying to boot to TWRP the phone is still connected onto it, but it just boot loops.
but it just boot loops
Click to expand...
Click to collapse
You see some red text... something like only official crap allowed...
Then maybe try other Firmware.... because """funny""" Bootloader...
IMHO similar problem like in this thread...
can't flash with odin even though bootloader being unlocked
i've got an a50 that i want to install TWRP on so i won't have to use the abomination that download mode is. i've unlocked bootloader, yet when i try to flash the TWRP .tar in odin it fails and the phone gives the following error code: "Only...
forum.xda-developers.com
Only idea....
I can not see your device nor I have Crystal Ball.
Best Regards
EQuak said:
Steps I've done:
1. Unlocked bootloader, OEM unlock is enabled
2. Downloaded and installed Samsung Drivers
3. Download TWRP / SHARP Recovery
4. Downloaded Odin
5. Got my phone into Download mode (KG State - Checking, FRP - off, OEM LOCK - off)
6. Ran Odin, device detected in Odin
7. Put the tar file into the AP
8. Clicked "Start" in Odin, passed successfully
9. Holding Volume Down, Volume Up & Power Button
10. Released Volume Down on black screen
11. Released Power Button on Samsung logo
12. Still holding Volume Up button
That's how far I was able to come. The device just bootloops itself and I can't get it to open TWRP / SHARP. Got it into download mode again and flashed it with the stock firmware, but want to install custom ROM through the TWRP / SHARP. First time trying to flash custom rom, am I doing something wrong? Any help appreciated.
Reference:
[RECOVERY][Official] TWRP 3.7.0_11 for Galaxy A50
*** Disclaimer I am not responsible for any damage you made to your device You have been warned Features: Android 11, 12 and 13 support Supported Devices: A505F A505FN A505G A505GN A505GT Downloads...
forum.xda-developers.com
GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI.
Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI. - GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP r...
github.com
Click to expand...
Click to collapse
I had the same issue. If u are on the newest binary flash that stock https://samfw.com/firmware/SM-A505FN/DCO/A505FNXXS9CUF1 after set it up w wifi u dont need to log in to a google account and flash ur recovery and it will work
EQuak said:
Steps I've done:
1. Unlocked bootloader, OEM unlock is enabled
2. Downloaded and installed Samsung Drivers
3. Download TWRP / SHARP Recovery
4. Downloaded Odin
5. Got my phone into Download mode (KG State - Checking, FRP - off, OEM LOCK - off)
6. Ran Odin, device detected in Odin
7. Put the tar file into the AP
8. Clicked "Start" in Odin, passed successfully
9. Holding Volume Down, Volume Up & Power Button
10. Released Volume Down on black screen
11. Released Power Button on Samsung logo
12. Still holding Volume Up button
That's how far I was able to come. The device just bootloops itself and I can't get it to open TWRP / SHARP. Got it into download mode again and flashed it with the stock firmware, but want to install custom ROM through the TWRP / SHARP. First time trying to flash custom rom, am I doing something wrong? Any help appreciated.
Reference:
[RECOVERY][Official] TWRP 3.7.0_11 for Galaxy A50
*** Disclaimer I am not responsible for any damage you made to your device You have been warned Features: Android 11, 12 and 13 support Supported Devices: A505F A505FN A505G A505GN A505GT Downloads...
forum.xda-developers.com
GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI.
Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI. - GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP r...
github.com
Click to expand...
Click to collapse
I got exactly the same problem....no I am facing a bootlooping device.....jay! ... :-(
@EQuak did you read the Stickies before posting in Development?
Your post does not qualify for Development and has been moved to Questions and Answers.
You are REQUIRED to read and follow the Forum Rules!
15. Keep threads / posts on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.
General Forums - For news and announcements relating to your device.
Q&A Help & Troubleshooting Forums - For all question / request threads and posts. If there is no Q&A Help & Troubleshooting forum, use the General Forum of the relevant device
Accessories Forum - For posts related to accessories relevant to the device
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Themes and Apps Forums - For the posting of Themes and / or Apps as well as announcements & discussions including modifications made to Themes and Apps.
Click to expand...
Click to collapse
TabletopDock9 said:
I had the same issue. If u are on the newest binary flash that stock https://samfw.com/firmware/SM-A505FN/DCO/A505FNXXS9CUF1 after set it up w wifi u dont need to log in to a google account and flash ur recovery and it will work
Click to expand...
Click to collapse
Did it, still boot loops...
EQuak said:
Did it, still boot loops...
Click to expand...
Click to collapse
Hmmm. What twrp version u use?
TabletopDock9 said:
Hmmm. What twrp version u use?
Click to expand...
Click to collapse
Originally I've used the version 3.7.0_11 (reference: https://forum.xda-developers.com/t/...-7-0_11-for-galaxy-a50.4581017/#post-88552901) but have tried also one more version from 1 youtube vid (saddly don't know the version of twrp), but they both failed. I've also tried to use a different recovery called "SHRP" but it failed again.
EQuak said:
Originally I've used the version 3.7.0_11 (reference: https://forum.xda-developers.com/t/...-7-0_11-for-galaxy-a50.4581017/#post-88552901) but have tried also one more version from 1 youtube vid (saddly don't know the version of twrp), but they both failed. I've also tried to use a different recovery called "SHRP" but it failed again.
Click to expand...
Click to collapse
I use this https://t.me/androidhowto2020/126453
TabletopDock9 said:
I use this https://t.me/androidhowto2020/126453
Click to expand...
Click to collapse
Just tried it and it boot loops. I'm gonna try and record a step-by-step video of my process to see if you could spot any mistakes I make during the process, because I'm really at my wits' end.
EQuak said:
Just tried it and it boot loops. I'm gonna try and record a step-by-step video of my process to see if you could spot any mistakes I make during the process, because I'm really at my wits' end.
Click to expand...
Click to collapse
Did you solved this yet? Im facing same problem, Ive tried about 4 different TWRP and SHRP also but non of them worked. Also first time doing this. Only option I could now do is to flash back some random stock ROM to atleast have functioning phone. But I cannot set up Gpay anymore because it says the device is rooted - And in reality it is not, even system says state of phone as Official. I dont know what to do.
DracieVajko said:
Did you solved this yet? Im facing same problem, Ive tried about 4 different TWRP and SHRP also but non of them worked. Also first time doing this. Only option I could now do is to flash back some random stock ROM to atleast have functioning phone. But I cannot set up Gpay anymore because it says the device is rooted - And in reality it is not, even system says state of phone as Official. I dont know what to do.
Click to expand...
Click to collapse
No, I haven't found any solution so far to it since the problem occurred. Guessing It may be caused by a CSC code since we are both form Slovakia? Really don't know...
EQuak said:
No, I haven't found any solution so far to it since the problem occurred. Guessing It may be caused by a CSC code since we are both form Slovakia? Really don't know...
Click to expand...
Click to collapse
I was thinking about it too. Like, my phone is from Orange, so probably there is something which is blocking the whole thing. Only way I was able to install system was through Odin. But for Odin Ive found only stock roms, custom roms work only with TWRP...
EQuak said:
No, I haven't found any solution so far to it since the problem occurred. Guessing It may be caused by a CSC code since we are both form Slovakia? Really don't know...
Click to expand...
Click to collapse
Maybe I found something now. I had one old Galaxy J3 2016, Also from Orange operator as my A50. And it did worked perfectly on the first try and only thing I've did was enabling USB debugging in developer options, which I've forgot on my A50 before. So maybe this could be the problem at least in my scenario? But yet I didn't got time to try it on A50 again.
DracieVajko said:
Maybe I found something now. I had one old Galaxy J3 2016, Also from Orange operator as my A50. And it did worked perfectly on the first try and only thing I've did was enabling USB debugging in developer options, which I've forgot on my A50 before. So maybe this could be the problem at least in my scenario? But yet I didn't got time to try it on A50 again.
Click to expand...
Click to collapse
You're a lifesaver, just tried it with the A50 and I successfully booted into TWRP. Definitely works!
Edit: Another thing that may fixed the issue is just not updating the software. I just went through the process of setting it up but right after I booted into the android, I just turned it off and got it into download mode and flashed it with TWRP.
EQuak said:
You're a lifesaver, just tried it with the A50 and I successfully booted into TWRP. Definitely works!
Edit: Another thing that may fixed the issue is just not updating the software. I just went through the process of setting it up but right after I booted into the android, I just turned it off and got it into download mode and flashed it with TWRP.
Click to expand...
Click to collapse
Im happy it worked. But sadly for my A50 it still bootloops and nothing, I have no idea why so Im stuck with stock OS on which Google Pay and few Samsung apps wont work cause "phone is rooted" (no it isnt, its on official rom) and since I cant flash TWRP I cant do anything Ive also tried your method to quickly set up fresh android (without wifi) and right after I went to reboot and flashing :/