Related
hello,
I tried to flash twrp to my p605 but when I boot to recovery I get this message " Recovery is not Seandroid Enforcing".
The only solution is to reflash twrp checking autoboot to fix problem. I have tried various versions of twrp. how I could fix this problem?
I am not rooted and I attach some info of my device.
thanks a lot.
any idea please?
Two ways to fix this error
georgew2 said:
any idea please?
Click to expand...
Click to collapse
It is likely you used the wrong TWRP for your Note (LTE version for P605). Be sure to use this xda forum for version and instructions. Sadly I have also made this error on various devices I have owned over the years. lol
https://forum.xda-developers.com/showthread.php?t=2515656
The first method is to boot into recovery and wipe data and reset to factory. The drawback here is you lose (probably) all your data, and it may not work then you have to try the second method anyway.
1: Power off your Samsung Galaxy Note 10.1. Make sure that it's completely turned off, this is the tricky part because of the bootloop. It takes patience and timing.
2: Now press; power, home and volume up to enter the recovery mode
3: Hold the buttons for at least 5 seconds until the android logo appears on the screen
4: The screen will be redirected to the recovery mode of your Samsung Galaxy Note 10.1
Use the volume button to navigate between the options and power button to select the highlighted option.
The second method, especially if that does not work, is to use ODIN to re-flash stock firmware onto your device. That is a process that using search will get you great detailed instructions, much better than I can describe.
Linuxmon
(search is your friend)
thanks for your time to help me. i downlaod twrp files from here: https://twrp.me/devices/samsunggalaxynote1012014qcom.html
I wonder if the new security udpate of february 2017 causes problems of installing twrp.
i will consider if i will try one of these methods.
Hello everyone, I am in a bit of a pickle. I'm new when it comes to rooting the new generation of Samsung phones. I have a Hong Kong Note 10+ in my hands and I have the OEM unlock toggle greyed out (having unlocked my bootloader). I've tried searching for guides but they only pertain to the Exynos version since that's the more common version to be rooted either that or they are confusing in terms of the steps involved. I'm stuck and just want to make sure I'm following the right steps in order to get Magisk installed on my phone. I have the proper firmware on my computer, I just need to know what to do when it comes to using Odin since things have changed so much over the years.
Edit: I've figured things out enough to the point I was able to at least patch the AP (firmware).tar file in Magisk, then flashed it along with the BL, CP and HOME CSC in Odin. I wiped the phone in the stock recovery after I got the pass in Odin. I had to redownload Magisk Manager and opened it to find it didn't go through. Currently stuck at the moment.
Edit #2: I followed the steps found on Topjohnwu's github page found here install.html but when it comes to getting into recovery after getting the Pass in Odin, I can't figure out the button combination with the volume up and side key. Upon rebooting out of download mode, how long to hold down the button until the stock recovery screen shows up? Immediately after the bootloader splash screen that reads in Mandarin? This the part that I'm stuck on now.
Up
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,
Hi there,
first of all, sorry for my bad english.
I want to remove the Stock ROM from my Tablet (Samsung Galaxy Tab S4 | SM-T830) and install something else (https://www.getdroidtips.com/android-12samsung-galaxy-tab-s4/).
For some Reason Samsung forced me to do a factory reset to unlock the bootloader (maybe I did it wrong, but now it happened, so it is how it is). Now the OEM Unlock Options says "Bootloader is already unlocked", but when I go into Download mode, I have multiple Problems:
1.: When I enter download mode by Booting into Recovery (adb reboot recovery) and choose "reboot to bootloader", OR by entering it directly using "adb reboot bootloader", I dont get the Warning Screen so I get into download mode directly.
2.: When entering Dowload mode as descibed in problem 1, I also dont get the informations at the Top left, I only see the Download Icon on a blue background but when restarting the tablet and holding Volume Up and Volume Down simuntainuasly, it will show the warning (in the correct cyan colors) and in the next step it shows me those status informations at the top left.
3.: However, regardless to how I get into download mode, the colors of the download mode screen will change to a blue filter version after one second. but I did never activate any blue filter on the device, and on any other device, the colors are displayed correctly.
4.: Any instalation with Odin3 failed on the device, regardless to how i got into download mode
In any online article I read, noone has any problems with installing something when in download mode.
Also, the KG-Status is displayed as "checking, I dont know if this is good or not.
What am I doing wrong, why can't I install anything on the device?
what is wrong with download mode? post a picture.
drivers installed correctly? check in windows device manager.
what does not work with Odin? what error message?
First of all, thank you for your reply!
1.: The Picture shows that the is something wrong with the Download mode of the Tab S4, because the Colors are not being displayed correctly (as you can see, the colors of the other devices are much more cyan), and I would not have mentioned that if the device would just be unable to show colors correctly, but in the Warning before the Download mode, the Colors are displayed as they are on the other devices, so the eventually the device wants to tell me something, but I dont know what.
2.: Well, I am pretty sure that the drivers are installed Correctly, because Flashing a Galaxy Tab S2, Galaxy S8 and Galaxy S5 worked perfectly with the same driver.
3.: I'l attach a Screenshot of Odin.
ALso, what does "KG STatus: Checking" mean? Is it the reason for the problem, or is it good? On the Web I could only find "Kg Status: Locked" and "KG Status: Unlocked". should I unlock it? If yes, how?
you say any installation with Odin3 failed. you are trying to flash TWRP.
try to flash something different.
https://topjohnwu.github.io/Magisk/install.html#instructions
not sure about the display, though.
Well, I have a porblem with the Program that is mentioned in the Guide you linked, Frija asks for a CSC, and I dont know what I have to enter there, I only know that the device is a SM-T830/gts4lwifi.
CSC is region code
Rooting, ODIN, Firmware, CSC Information And Myths Debunked / Noob's Guide To Samsung Devices
Since a lot of people will have their Galaxy S22 Ultra soon and I myself am thinking about either getting an S21 Ultra or S22 Ultra, I wanted to summarise a lot of information I found out during researching as Samsung devices are quite different...
forum.xda-developers.com
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Well, if RMM/KG state is prenormal you would see message "Only official released binaries are allowed to be flashed"
Anyway, try to flash official ROM and wait for KG state while device is connected to internet.
you can download according to your region from https://samfw.com/firmware/SM-T830
T830Guy said:
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Click to expand...
Click to collapse
Setting the 7 days back works
T830Guy said:
Okay, maybe I am an Idiot or so, but it does not work, Frija does not find any Firmware for the SM-T830, flashing a custom build of TWRP also does not work, folowing other Guides to install Magisk doesn't work, and using Odin to Flash a System Imagge (in the Guide I saw this was how they did it) also does not work.
Also "adb sideload" does not work using the Stock Recovery, so I really need TWRP to do so.
When searching for the KG Status, I found out that Samsung devices are checking themselves for a Week or so before accepting any Unofficial images, since I factory reseted the Tablet two days ago, the device may check itself. So should I eventually wait a Week before trying it again?
I dont know what I could do, so that seems logical for me, do you think that might solve the Problem?
Click to expand...
Click to collapse
try this: https://forum.xda-developers.com/t/...-twrp-and-magisk.4059227/page-2#post-88134465
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 :/