Related
Hello people. Recently i got my first qualcomm device redmi-4x (v8.2.12.0) global (previously i used/worked-for mtk devices), and from past few days i have been reading/learning about this qualcomm device.
I have checked almost all redmi-4x forums (miui, xda, 4pda etc) and still have some questions in my mind.
Q1:
I want to backup my redmi-4x before unlocking/rooting/FlashingTWRP. I know in mtk devices, even if the device is unrooted/untouched we can easily backup firmware/complete-emmc (each and every partition) by readback methods using SP-FlashTool/Miracle-Box etc...
i read somewhere, we can do same thing, i.e readback qualcomm device's emmc in edl-mode but unfortunately, xiaomi has disabled fastboot edl mode in new devices and the only way left to open edl mode is test point method which requires disassembly. though i can but i don't want to disassemble it (warranty will be void). Another solution i saw was Deep Flash Cable, which isn't working either, personally tested... Now, having no other option, i decided to unlock it to make stock rom backup using TWRP. Actually i wanted to make backup with minimum changes to original firmware, so if anyone here knows any other solution to make backup without unlocking bootloader, (or unlocked_bootloader + no_other_changes, i.e without TWRP) please share... Thanks!
Q2:
From what i have learned so far, i think MiUI bootloader unlock tool doesn't work with non-miui firmwares, right? so the question is, if we manually relock our redmi 4x using fasboot when there is some non-miui rom installed in the device. what can be the possible solution to unlock it again? (except reflashing miui by test point method and then unlocking bootloader). Thanks!
EnerJon said:
i wanted to make backup with minimum changes to original firmware, so if anyone here knows any other solution to make backup without unlocking bootloader, (or unlocked_bootloader + no_other_changes, i.e without TWRP) please share... Thanks!
Click to expand...
Click to collapse
Hi, I do it this way:
- unlocked bootloader
- copy http://www.mediafire.com/file/pj0qh1ccj4h2a2a/p0.zip to FAT32 flash drive
- fastboot boot twrp.img (TWRP is not flashed, boots from RAM, not eMMC, so no_other_changes)
- attach the flash drive to R4X on OTG adapter
- in TWRP "install" p0.zip
- entire eMMC will be compressed and saved on the flash drive
My new R4X 32GB was compressed down to 2GB within around half an hour. Later I mounted the disk image on a PC and erased OS/data partitions: system, cache, userdata, cust, recovery, boot, and now the entire 32GB with bootloader, support and firmware is 80MB compressed.
Have you tried QPST backup in EDL mode?
k23m said:
- unlocked bootloader
- copy http://www.mediafire.com/file/pj0qh1ccj4h2a2a/p0.zip to FAT32 flash drive
- fastboot boot twrp.img (TWRP is not flashed, boots from RAM, not eMMC, so no_other_changes)
- attach the flash drive to R4X on OTG adapter
- in TWRP "install" p0.zip
- entire eMMC will be compressed and saved on the flash drive
My new R4X 32GB was compressed down to 2GB within around half an hour. Later I mounted the disk image on a PC and erased OS/data partitions: system, cache, userdata, cust, recovery, boot, and now the entire 32GB with bootloader, support and firmware is 80MB compressed.
Click to expand...
Click to collapse
Thanks for The Guide, it Will Surely be Helpful for New R4X Users :good: Just Wondering Why No One Made Such a Guide For R4X Earlier... Or Did i Missed it Somewhere?
k23m said:
Have you tried QPST backup in EDL mode?
Click to expand...
Click to collapse
No, But i Used another Tool Which i Think Uses Same Technique as QPST in EDL Mode. i Unlocked My R4X and Then Booted into EDL Mode, Used This Tool (With "prog_emmc_firehose_8937_ddr.mbn" From R4X Fastboot Firmware) To Take Complete EMMC Backup, it Also Converted The Backup into Fastboot ROM...
EnerJon said:
Thanks for The Guide, it Will Surely be Helpful for New R4X Users :good: Just Wondering Why No One Made Such a Guide For R4X Earlier... Or Did i Missed it Somewhere?
Click to expand...
Click to collapse
I made the guide and script for Nexus 7'13 but it works well on R4X too. There is no known method of QPST backup on the Nexus but Xiaomi always had more options thanks to freely available "firehose" files. Thank you for the emmcdl link, it is a very simple and convenient tool.
We could use emmcdl for unlocking. I found some pre-patched "persist" partitions here http://blog.regenerationmm.com/2017/03/emmc-dl-အသုံးျပဳျပီး-mi-account-bypass-ျပဳလုပ္/
:highfive:
k23m said:
I made the guide and script for Nexus 7'13 but it works well on R4X too. There is no known method of QPST backup on the Nexus but Xiaomi always had more options thanks to freely available "firehose" files. Thank you for the emmcdl link, it is a very simple and convenient tool.
We could use emmcdl for unlocking. I found some pre-patched "persist" partitions here http://blog.regenerationmm.com/2017/03/emmc-dl-အသုံးျပဳျပီး-mi-account-bypass-ျပဳလုပ္/
:highfive:
Click to expand...
Click to collapse
Hello. Do you have more information on this? I have a Redmi 4x that I really want to unlock the bootloader, but the official method doesn't work for me.
I found this site showing a method for the redmi 4a that uses the emmcdl tool:
Rolex Instant UBL (Unofficial Unlock Bootloader for Redmi 4A) Tested! - OmBob Opreker
Complete Tutorial how to bypass your Redmi 4A (rolex) lock bootloader, the unofficial way. tested And Work for all rolex version
ombob.my.id
Is this what you mentioned?
unluckyuser said:
Hello. Do you have more information on this? I have a Redmi 4x that I really want to unlock the bootloader, but the official method doesn't work for me.
I found this site showing a method for the redmi 4a that uses the emmcdl tool:
Rolex Instant UBL (Unofficial Unlock Bootloader for Redmi 4A) Tested! - OmBob Opreker
Complete Tutorial how to bypass your Redmi 4A (rolex) lock bootloader, the unofficial way. tested And Work for all rolex version
ombob.my.id
Is this what you mentioned?
Click to expand...
Click to collapse
Hi, I have files from the defunct link, but never tested them as my R4X is unlocked officially.
The R4A is indeed using the unlock method I speculated about.
k23m said:
Hi, I have files from the defunct link, but never tested them as my R4X is unlocked officially.
The R4A is indeed using the unlock method I speculated about.
Click to expand...
Click to collapse
I would like to have the files and experiment, thank you.
I already messed up my phone and I'm trying to flash the stock rom via edl first.
A simple guide to installing custom GSI's on Motorola G50.
This works only on Qualcomm models that are from G series of Motorola.
Recomended flashing stock android 12 to your phone to get NFC functionality back and for bluetooth disconecting there is a workaround by going to Phh's treble settings and enabling "Force Disable A2DP offload"
What will you need?
Motorola's fastboot tools (attached to thread.) Update these don't work now. Use latest version of fastboot.
Unlocked bootloader
blank vbmeta (Included with Fastboot.)
Generic System Image of your choice.
Unlocking bootloader will void your warranty and erase your data (If you have any important data you can backup in System settings or using LMSA tool, I am NOT responsible for any damage that you make. If you **** up you can always restore to stock by using LMSA tool from Motorola.
Click to expand...
Click to collapse
Download your GSI image. Because there isn't any TWRP recovery for G50 (ibiza) yet. We need to download GSI image with gapps like Pixel Experience or Lineage OS 19 with GMS.
Download fastboot and adb tools from Motorola. Since some features like "fastboot oem get_unlock_data" dosen't work
Unlock bootloader (If you have unlocked bootloader skip this step.). There's a guide on motorola site to help you unlock your bootloader. Here you have the guide https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/
After unlocking bootloader we can go to installing our GSI.
Boot to bootloader. You can do it by turning off your phone and pressing at the same time Power + Volume down or using adb by "adb reboot bootloader"
After doing that you need to reboot to fastbootd. You can do it by typing in fastboot "fastboot reboot fastboot"
If you boot to a screen with bold red text written "fastbootd" we can go to erasing data and system partitions. But after we can do that we need to flash vbmeta.
Flash vbmeta.img to bypass AVB (Android Verified Boot.) : "fastboot --disable-verification flash vbmeta vbmeta.img" and wait until it says OK
If we did that we can erase system partition by typing in fastboot "fastboot erase system" If it says OK we can go to the next step
If we get "CANNOT RESIZE SYSTEM PARTITION" do this: "fastboot delete-logical-partition product_a" and "fastboot delete-logical-partition product_b"
Now it's time to flash our GSI. To do that just type "fastboot --u flash system *name of your gsi*.img
And wait until it flashes and DO NOT REBOOT!!!
After successful flash we need to type "fastboot -w"
And now you can reboot.
If you did everything and your device boots then congrats you did it. If you have questions or issues reply to this thread and I will do my best to help you!
And this is my first guide and I was scratching my head how to do that so yeah that took some time.
What roms are working?
As for midrangers some roms dosen't work fully, like HavocOS or AncientOS but i made a little list of compatible roms at current date (18.01.2022)
Pixel Experience 11
Pixel Experience 12
DotOS 5.2
AncientOS
CorvusOS
Phh's AOSP
Lineage OS
And other roms, list of these roms that work on this phone is available here
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Tested but not booting:
HavocOS (GSI discontinued.)
(Updating list until i'll get my phone back from repair.)
Known Issues
- All GSI that runs under Phh NFC does not work (Status: fixed check begining of the thread.)
Hello which GSI is the best
I'm thinking about lineageos a64 vb.
Is it ok?!
walidmerdji said:
Hello which GSI is the best
I'm thinking about lineageos a64 vb.
Is it ok?!
Click to expand...
Click to collapse
If you wanna clean Ui and smooth experience dotOS should be good for you.
Currently im using Pixel Experience 12 alpha and it works good. And im still working on nfc fix. If you have more questions feel free to ask me.
Also if you want to choose GSI you need an A/B version "arm64-ab".
TwelwePL said:
If you wanna clean Ui and smooth experience dotOS should be good for you.
Currently im using Pixel Experience 12 alpha and it works good. And im still working on nfc fix. If you have more questions feel free to ask me.
Also if you want to choose GSI you need an A/B version "arm64-ab".
Click to expand...
Click to collapse
fastboot reboot fastboot
Error unknown target fastboot!
There is no such command on fastboot!
walidmerdji said:
fastboot reboot fastboot
Error unknown target fastboot!
There is no such command on fastboot!
Click to expand...
Click to collapse
If your device is on turn it off.
Press Power + Volume down and hold till you get an android bot laying and then type fastboot reboot fastboot
TwelwePL said:
If your device is on turn it off.
Press Power + Volume down and hold till you get an android bot laying and then type fastboot reboot fastboot
Click to expand...
Click to collapse
Hi
I flashed 100s of phones using fastboot
I'm aware of how to boot to fastboot and using cmd
The thing is there is no such command for fastboot
Fastboot reboot bootloader takes you to the same window
However I managed to boot to fastbootd
Using phone terminal
su reboot fastboot
But again my phone is rooted (magisk) so I don't think if I can flash a GSI on a rooted phone
walidmerdji said:
Hi
I flashed 100s of phones using fastboot
I'm aware of how to boot to fastboot and using cmd
The thing is there is no such command for fastboot
Fastboot reboot bootloader takes you to the same window
However I managed to boot to fastbootd
Using phone terminal
su reboot fastboot
But again my phone is rooted (magisk) so I don't think if I can flash a GSI on a rooted phone
Click to expand...
Click to collapse
I forgot to add that booting to fastbootd mode and flashing gsi with Magisk it will just simply bootloop. By flashing stock boot image gsis run flawlessly but HavocOS dosen't want to boot. I'll make a quick video how to do this if you need more context.
walidmerdji said:
Hi
I flashed 100s of phones using fastboot
I'm aware of how to boot to fastboot and using cmd
The thing is there is no such command for fastboot
Fastboot reboot bootloader takes you to the same window
However I managed to boot to fastbootd
Using phone terminal
su reboot fastboot
But again my phone is rooted (magisk) so I don't think if I can flash a GSI on a rooted phone
Click to expand...
Click to collapse
Hi, again.
I've made a video that could help you flash gsi on your Moto G50
If you have more issues you can dm me on xda.
Thomas, TwelwePL.
Hello, can I use this guide and the file provided to flash my Chinese version of this phone (ibiza_retcn). It has 8gb if ram, 128gb of storage and no NFC. Everything else seem the same (CPU is snap)
dynia said:
Hello, can I use this guide and the file provided to flash my Chinese version of this phone (ibiza_retcn). It has 8gb if ram, 128gb of storage and no NFC. Everything else seem the same (CPU is snap)
Click to expand...
Click to collapse
Yeah! Fastboot and vbmeta are correct for the ibiza-retcn. But if you mess something up you can revert back to stock using motorola's tool LMSA. Currently I have my moto g50 in repair center because i forgot that you cannot relock bootloader on motorola phones. And please be careful, if you'll be stuck on bootloop when you flashed some gsi, it isn't bricked just flash another. Some gsis dosen't always work on this phone. Tommorow I will prowide list of compatible gsis that will work on this phone.
TwelwePL said:
Hi, again.
I've made a video that could help you flash gsi on your Moto G50
If you have more issues you can dm me on xda.
Thomas, TwelwePL.
Click to expand...
Click to collapse
Nice language in Your device
Thx for the guide, lacking TWRP or any custom recovery, could be a pain... However old-school methods are still 'a gold skills'.
See U around!
Hello,
Just a small FYI - Pixel Experience A12 boots and so far works OK as well
If I manage to implement root solution, I will stay with it for a little bit longer.
Wish U all good day!
Voytec83 said:
Hello,
Just a small FYI - Pixel Experience A12 boots and so far works OK as well
If I manage to implement root solution, I will stay with it for a little bit longer.
Wish U all good day!
Click to expand...
Click to collapse
Thanks u too,
Currently my motorola is in repair because i bricked it. Now waiting for them to call me and pick my phone up. I'm happy that my guide worked for you!
For root like Magisk I had almost done Magisk but with "Task Failed Succesfully" by making to bootanimation and not booting. About In Februrary or March magisk should be working.
After texting motorola they release their MyUX A12 on Februrary If you're interested.
Wish that your phone with PE12 will work without any issues (only nfc
Update 14.02.2022
- Magisk is working with Pixel Experience 12 V401
TwelwePL said:
Update 14.02.2022
- Magisk is working with Pixel Experience 12 V401
Click to expand...
Click to collapse
Thanks very much for the guide. I now have Pixel Experience 12 V402 working.
I tired to get magisk working (patched boot.img in the magisk app then back to fastbootd and "fastboot flash boot magisk_boot.img" but it boot loops. I also tried flashing to both boot_a and boot_b.
Can you tell me how you got this working?
bejam said:
Thanks very much for the guide. I now have Pixel Experience 12 V402 working.
I tired to get magisk working (patched boot.img in the magisk app then back to fastbootd and "fastboot flash boot magisk_boot.img" but it boot loops. I also tried flashing to both boot_a and boot_b.
Can you tell me how you got this working?
Click to expand...
Click to collapse
When PE12 v401 got released the Magisk app appeared in app drawer and it just needed to reboot to setup magisk so i did that and Magisk worked flawlessly. It also worked on my A50 so i didn't patched the boot.img
TwelwePL said:
[cut]
Click to expand...
Click to collapse
many many many thanks for this thread. I was very suprised to see that this cheap smartphone had so little support from the bigger custom roms (like, for instance lineageos). I will try pixelexperience - can you please provide some help identifying which "codename" is hould download to flash my Motog50?
Thanks again
Any Degoogled ROMs for this device? Currently I am on stock rooted with magisk but with many problems like GPS not working correctly and some motorola update reminders popping out. Any help Highly appreciated
You can try Phh's AOSP with FLOSS variant degoogled and open source apps.
TwelwePL said:
You can try Phh's AOSP with FLOSS variant degoogled and open source apps.
Click to expand...
Click to collapse
Thank you. Can you provide any link? Got this: https://github.com/phhusson?tab=repositories but can't fiuguere ot which repo is the right one
I successfully flashed my European oneplus 10 pro using the instructions - see link below.
Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.
Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.
All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.
This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
and this is where I CRUSHED down by running this:
The rootingget you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
THANK YOU FOR YOUR HELP !!!
This should work for you
Note: You are already in FastbootD (Recovery).
Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
yedashare said:
I successfully flashed my European oneplus 10 pro using the instructions - see link below.
Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.
Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.
All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.
This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
and this is where I CRUSHED down by running this:
The rootingget you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
THANK YOU FOR YOUR HELP !!!
Click to expand...
Click to collapse
Savio Dantes said:
This should work for you
Note: You are already in FastbootD (Recovery).
Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
Click to expand...
Click to collapse
Thank you Savio, but this is my main issue, I cannot enter fastbootD.
Whether using the tool "fastboot enhance" or using the command line. I cannot reach FastboodD.
When I try to reach this using the tool, it's looping with no error log.
And when I try from CMS:
C:\Users\me\Downloads\from dumper> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
It also still sounds like your recovery.img and/r boot.img still may be corrupted.
this needs to MATCH in BOTH slots A & B
Try this:
https://forum.xda-developers.com/t/...e-rom-root-and-recovery.4525451/post-87806713
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
yedashare said:
and this is where I CRUSHED down by running this:
The rootingget you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Click to expand...
Click to collapse
This is where your fatal mistake was.... the red line above is incorrect !
It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"
you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.
The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.
Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.
When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.
hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.
cheers
u can try to fix sms mms problem using this thread
xiaomi 12/moto edge x30(or any device with sm8450) sms＆ims error · Issue #2246 · phhusson/treble_experimentations
Now gsi is able to boot on devices with sm8450.But sms doesn't work.And ims settings shows "not supported" .I tried to install q-ims.apk or ims.apk from the stock rom.Still ,ims does work at all. A...
github.com
@yedashare
@dladz maybe we can share it groups ?
beatbreakee said:
This is where your fatal mistake was.... the red line above is incorrect !
It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"
you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.
The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.
Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.
When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.
hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.
cheers
Click to expand...
Click to collapse
Thank you, BB, for the clear explanations about respecting the structure of the partitions and not messing directly with the boot partition using a modified img.
Do I need to reach the conclusion that my phone is broken forever and there is nothing I can do to fix it?
I thought that as long as I reach the recovery mode, I can still fix it.
If you have a brilliant solution just as brilliant as your teaching, could you please help me restoring my phone to a functional state?
And BTW, it was a TRIPLE FLAW, because I had a wonderful lineageos 19 working like a charm with GAPS and I just wanted to root it for no reason.
Many thanks for your efforts.
Damn. Nice to know Lineage works well on this phone with extensive tweaking. GSI's can be pretty unstable from what I've seen, missing cell reception and the like.
Yeah, flashing that image killed the phone. I've seen some people recover by flipping their boot slot to the other one and forcing the phone to boot the stock boot there. But if you've flashed to both slots, you're most likely SOL and need a MSM flash. In which case, you could try flashing the complete stock boot image for your OOS version you were on before moving to GSI to both slots as sort of a last resort, but even then I've only seen minimal success.
Savio Dantes said:
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
Click to expand...
Click to collapse
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use
Savio Dantes said:
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
Click to expand...
Click to collapse
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use MSM.
I understand that MSM is no longer available.
Any other direction how I can just fix the booting process?
And this is another error I received which gets closer to the source of the problem:
FAILED (remote: 'Failed to load/authenticate boot image: Bad Buffer
I’m assuming Adb does not work?
why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.
Arealhooman said:
I’m assuming Adb does not work?
Click to expand...
Click to collapse
Yes right, adb doesn't work, only fastboot is still alive
TuLy2702 said:
why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.
Click to expand...
Click to collapse
Thanks for taking time to answer.
Could you be more specific?
I SAVED MY PHONE
BACK ONLINE
THANKS TO THIS POST:
[TOOL] Oppo/Realme Flash .OFP File on Bootloader
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool. THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED Features soft unbrick install stock firmware switch device region Credits...
forum.xda-developers.com
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!
One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.
A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
yedashare said:
I SAVED MY PHONE
BACK ONLINE
THANKS TO THIS POST:
[TOOL] Oppo/Realme Flash .OFP File on Bootloader
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool. THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED Features soft unbrick install stock firmware switch device region Credits...
forum.xda-developers.com
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!
One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.
A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
Click to expand...
Click to collapse
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS
yedashare said:
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS
Click to expand...
Click to collapse
you make me laugh
yedashare said:
EoS
Click to expand...
Click to collapse
Damn. I think what happened is you lost your persist.img when initially flashing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.
Prant said:
Damn. I think what happened is you lost your persist.img when initially flaahing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.
Click to expand...
Click to collapse
It's okay to spend a little money. It's very risky to do it yourself
Did you managed to get fingerprint working on gsi ?
Hello everyone. Can You please explain how to install GSI to SM-X205? I'm new to fastboot methods. I can't find proper TWRP for this particular model. I have achieved to unlock bootloader which took two steps (In old Android phone it was just easy with switch in developer options). I have installed TWRP from SM-X200 but it's not working. Restored everything by flashing Official Firmware. The main reason why I'm going to this is shortage of storage. I want to format external SD Card as Internal which is not allowed in new Andoirds. Thank you before hands and respect for ones who contribute their knowledge for community.
If TWRP is not available for your device, you can try using this to enable fastbootd. It won't have any TWRP specific features though.
As far as installing a GSI, you simply flash the system.img to /system. It's that simple. Make sure you wipe data.
SukhrobR said:
Hello everyone. Can You please explain how to install GSI to SM-X205? I'm new to fastboot methods. I can't find proper TWRP for this particular model. I have achieved to unlock bootloader which took two steps (In old Android phone it was just easy with switch in developer options). I have installed TWRP from SM-X200 but it's not working. Restored everything by flashing Official Firmware. The main reason why I'm going to this is shortage of storage. I want to format external SD Card as Internal which is not allowed in new Andoirds. Thank you before hands and respect for ones who contribute their knowledge for community.
Click to expand...
Click to collapse
SM-X205 installs the same as SM-X200 - I've followed all the instructions for any TWRP, root, GSI, etc and it all works as others X200's. I've not lost anything on the X205.
Piggybacking on this thread to drop some much needed general resources. I installed LineageOS on my s5e last year but struggled to find resources w/ GSI.
I appreciate all the hard work that the devs do, and typically documentation is not their strong suit, so in the future, maybe those of us who benefit from their work can create clearer documentation to spread around the burden a bit:
FAQ that covers topics like what is Treble, what is GSI, what is the naming conventions for GSI files: https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
Where as example of a GSI I can download : https://github.com/phhusson/treble_experimentations/releases/tag/v416
What should I know going in: Android 13 versions of GSI still have a few compatibility issues as per the first post in this thread. Android 12 is functioning 100% correctly.
Where can I see a more complete list of the GSI options available to me: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
w00tnezz said:
SM-X205 installs the same as SM-X200 - I've followed all the instructions for any TWRP, root, GSI, etc and it all works as others X200's. I've not lost anything on the X205.
Click to expand...
Click to collapse
I have followed all the instructions. But I'm stuck at stage where rebooting to fastboot from TWRP. Touchscreen stops to respond and I can't enable ADB.
SukhrobR said:
I have followed all the instructions. But I'm stuck at stage where rebooting to fastboot from TWRP. Touchscreen stops to respond and I can't enable ADB.
Click to expand...
Click to collapse
You don't need to enable ADB. When the screen says "Entering fastboot mode" then you are connected. You can check this by entering "fastboot devices" from your PC.
lewmur said:
You don't need to enable ADB. When the screen says "Entering fastboot mode" then you are connected. You can check this by entering "fastboot devices" from your PC.
Click to expand...
Click to collapse
Device list is empty after entering fastboot mode in twrp
SukhrobR said:
Device list is empty after entering fastboot mode in twrp
Click to expand...
Click to collapse
Do you have the latest version of the Samsung USB drivers? Earlier versions don't have the fastboot driver.
lewmur said:
Do you have the latest version of the Samsung USB drivers? Earlier versions don't have the fastboot driver.
Click to expand...
Click to collapse
Yes I do. I think it dependable on firmware version.
w00tnezz said:
SM-X205 installs the same as SM-X200 - I've followed all the instructions for any TWRP, root, GSI, etc and it all works as others X200's. I've not lost anything on the X205.
Click to expand...
Click to collapse
Does this allow me to use this (https://forum.xda-developers.com/t/...0-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691) for my SM-X205?
Recently I got kinda frustrated with MIUI14 and it's limitations, due to the lower RAM capacity of my Redmi. Trying to install CorvusOS, ArrrowOS and PixelExp, i got a warning, stating that my "system"'partition is too small, but cant be resized. So I'm trying to get TWRP to work, so i can try to resize it and if this doesn't work, at least use it in MIUI to install Magisk.
I've followed the steps from this question thread and this thread by skkk for TWRP, and what I've got to the moment is:
1. If i try to boot the TWRP image by using 'fastboot boot twrp.img', it spits out an error saying that it couldn't send the image to the device, because "file too large", which I think is due to the fact that my device is a 4GB RAM model, but even then, the image is about 200MB (which shouldn't be a problem, imo)2. If I try to (don't ask why) to flash the image using 'fastboot flash boot_a', it says that the file is too large for the partition, or something like this, I don't remember.3. Trying to flash the boot image (haven't tried the Rec image, and I don't need to) using 'fastboot flash recovery' spits an error, that the partition doesn't exist. I could try using the 'rescue' partition, but I'm kinda scared to do so.It's a good time to mention, that I've tried booting the partition in both the bootloader, and in FASTBOOTD mode.
Also, if there isn't a way for me to install TWRP in any way on my device, is there a 'fastboot' command to resize my partition, and if not, how do I deal with this problem?
My device: Redmi Note 10 5G, Camellian with 4GB RAM, running MIUI 14.0.1 EU based on A13.
Just found out that the 2nd thread states, that the flash partition is 'recovery_ab', not 'recovery'. Didn't make a difference tho...
mm just get one of the roms here:
[ROM][12][Camellia/Camellian] PixelExperience [AOSP] (Unofficial)
PixelExperience for Redmi Note 10 5G/Redmi Note 11SE/Redmi Note 10T 5G/POCO M3 Pro 5G (camellia/camellian) What is this? PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts...
forum.xda-developers.com
[ROM][12.1][UNOFFICIAL][Camellia/Camellian] crDroid v8.14 [14.04.2023]
***Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com
once you flash boot.img (fastboot flash boot boot.img), reboot into recovery and do factory reset / clear data
ThePhoneUser0 said:
mm just get one of the roms here:
[ROM][12][Camellia/Camellian] PixelExperience [AOSP] (Unofficial)
PixelExperience for Redmi Note 10 5G/Redmi Note 11SE/Redmi Note 10T 5G/POCO M3 Pro 5G (camellia/camellian) What is this? PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts...
forum.xda-developers.com
[ROM][12.1][UNOFFICIAL][Camellia/Camellian] crDroid v8.14 [14.04.2023]
***Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com
once you flash boot.img (fastboot flash boot boot.img), reboot into recovery and do factory reset / clear data
Click to expand...
Click to collapse
do not do 'fastboot flash boot_a boot.img'. just 'fastboot flash boot boot.img'
Or get MIUI again to fix the things you've done with MiFlash then try installing Pixel Experience or CrDroid
Thanks a lot, but even without testing I'm positive that the problem WILL remain.
From the first pictures u can see that I've made a folder (on my ext HDD, G: ) with all the Android tools, drivers and every firmware for my device. I've tried and I'm not a fan of crDroid, that's why I was trying Corvus and PE. The links u sent me point to the version I already tried. I could download another one, but frankly speaking, I don't want to, if I can just flash TWRP, and install the latest version. And as we speak of TWRP, I tried flash boot, flash boot_a and boot_b. None of them worked. Booting also didn't work. About the MIUI, I've bricked my device about 2-3 months (i don't remember) and used MiFlash to fix it. From them the only other thing I've done, is upgrade to MI14 and root w/ Magisk. So that shouldn't be a problem either, imo.
What I'm gonna try these days is, I think RedWolf or something, an alt for TWRP. They are all based of of TWRP and are for Note 10 or 10 Pro, but I think that they (at least that image for Note 10) should work.
Edit: the Recoveries I'm gonna try are OrangeFox and PitchBlack. I forgot that the RedWolf (if that's the name) is based up to like Mi 6.
OK, I've tried OrangeFox and now every time I try to boot of of it, it says, and I quote: (Status read failed(too many links)). What does that mean? I tried different cable, different port, checked everything, and it still wouldn't boot. Is it just because of the incompatibility of RN10/10 Pro recovery with 10 5G?
bg0169 said:
1. If i try to boot the TWRP image by using 'fastboot boot twrp.img', it spits out an error saying that it couldn't send the image to the device, because "file too large", which I think is due to the fact that my device is a 4GB RAM model, but even then, the image is about 200MB (which shouldn't be a problem, imo)
Click to expand...
Click to collapse
bg0169 said:
2. If I try to (don't ask why) to flash the image using 'fastboot flash boot_a', it says that the file is too large for the partition, or something like this, I don't remember.
Click to expand...
Click to collapse
camellian boot images are 64MB, thats why the 'partition' cant be flashed with an 200MB image
bg0169 said:
3. Trying to flash the boot image (haven't tried the Rec image, and I don't need to) using 'fastboot flash recovery' spits an error, that the partition doesn't exist. I could try using the 'rescue' partition, but I'm kinda scared to do so.
Click to expand...
Click to collapse
bg0169 said:
Just found out that the 2nd thread states, that the flash partition is 'recovery_ab', not 'recovery'. Didn't make a difference tho...
View attachment 5935395
Click to expand...
Click to collapse
since you tried to flash into the “recovery” partition and it wasn’t present, it’s because the camellian is an A/B slot device, which led to its removal and to the implementation of the recovery into the “boot.img” or "boot" partition.
just as ThePhoneUser0 said, use the "boot.img" images referred in those ROMs. *they work perfectly fine and were made for our device.
[ROM] > https://forum.xda-developers.com/f/poco-m3-pro-redmi-note-10-5g.12315/?prefix_id=33
bg0169 said:
Thanks a lot, but even without testing I'm positive that the problem WILL remain.
Click to expand...
Click to collapse
bg0169 said:
OK, I've tried OrangeFox and now every time I try to boot of of it, it says, and I quote: (Status read failed(too many links)). What does that mean? I tried different cable, different port, checked everything, and it still wouldn't boot. Is it just because of the incompatibility of RN10/10 Pro recovery with 10 5G?
Click to expand...
Click to collapse
about TWRP and your doubt that it will remain, TWRP may work and boot on our device, yes, but it is not recommended to use them.* most of them dont work, and the community has probably dropped it, alternatively using the recoveries from AOSP ROMs here that work like a charm. you just use the recovery for that specific ROM every time to avoid any issues
[ROM] > https://forum.xda-developers.com/f/poco-m3-pro-redmi-note-10-5g.12315/?prefix_id=33
bg0169 said:
What I'm gonna try these days is, I think RedWolf or something, an alt for TWRP. They are all based of of TWRP and are for Note 10 or 10 Pro, but I think that they (at least that image for Note 10) should work.
Click to expand...
Click to collapse
if you are telling that youre going to flash stuff from other devices... ffs dont, and never
the Redmi Note 10 is a complete different device with an completely different socket
bg0169 said:
OK, I've tried OrangeFox and now every time I try to boot of of it, it says, and I quote: (Status read failed(too many links)). What does that mean? I tried different cable, different port, checked everything, and it still wouldn't boot. Is it just because of the incompatibility of RN10/10 Pro recovery with 10 5G?
Click to expand...
Click to collapse
please stop trying to install custom recoveries, they wont work.
bg0169 said:
OK, I've tried OrangeFox and now every time I try to boot of of it, it says, and I quote: (Status read failed(too many links)). What does that mean? I tried different cable, different port, checked everything, and it still wouldn't boot. Is it just because of the incompatibility of RN10/10 Pro recovery with 10 5G?
Click to expand...
Click to collapse
at this point, flash MIUI back with miflash and redo the process, although dont flash random recoveries that you just find on other devices because it wont work.
Thanks, again, @1lopes, you've saved my butt from a lot of problems so far... .
1lopes said:
camellian boot images are 64MB, thats why the 'partition' cant be flashed with an 200MB image
Click to expand...
Click to collapse
Yea, I found out after flashing the twrp.img it said that the partition is some 100-200k bytes or so and when i converted, was about 65MB in total. Hella lot smaller than the image.
1lopes said:
just [email protected] ThePhoneUser0 said, use the "boot.img" images referred in those ROMs. *they work perfectly fine and were made for our device.
[ROM] > https://forum.xda-developers.com/f/poco-m3-pro-redmi-note-10-5g.12315/?prefix_id=33
Click to expand...
Click to collapse
I'm gonna try those later, but does these recovery images have those TWRP-like features, or are they like the MIUI Recovery - just Restart, Halt, Bootloader? I'm also curious, cuz the image i tried for PE was unofficial camellia/camellian for A13 from 18th Feb 2022 and it refused to install, die to the "small system partition size". I'ma try those, you've pointed to, but I'm still skeptical some of them might not work, because of this problem.
1lopes said:
about TWRP and your doubt that it will remain, TWRP may work and boot on our device, yes, but it is not recommended to use them.* most of them dont work, and the community has probably dropped it, alternatively using the recoveries from AOSP ROMs here that work like a charm. you just use the recovery for that specific ROM every time to avoid any issues
Click to expand...
Click to collapse
1lopes said:
if you are telling that youre going to flash stuff from other devices... ffs dont, and never
the Redmi Note 10 is a complete different device with an completely different socket
Click to expand...
Click to collapse
Why is using TWRP so scary? Why isn't it recommended? Also about the RN10, yea, after you said it, I searched on gsmarena.com and found that both devices were using a SD chipset, not a MediaTek. Didn't think of that...
ThePhoneUser0 said:
please stop trying to install custom recoveries, they wont work.
Click to expand...
Click to collapse
ThePhoneUser0 said:
at this point, flash MIUI back with miflash and redo the process, although dont flash random recoveries that you just find on other devices because it wont work.
Click to expand...
Click to collapse
OK, OK, I wont, don't worry. Also I've reinstalled MIUI from fastboot flash commands, w/o MiFlash, cuz it was easier. I'm gonna try those recoveries from the ROMs for camellian.
Quick update: just installed PE for camellian on my phone. Gonna see everything works and send some screenshots when i log on it!
Also to mention to anybody trying this: REMEMBER TO FACTORY RESET! I forgor and had to force restart and go to recovery again... Tho when I first booted up w/o reset, it showed my old wallpaper. I think becausethe recovery updatekeeps the user data untouched.
bg0169 said:
does these recovery images have those TWRP-like features
Click to expand...
Click to collapse
they have useful functions, similiar to MIUI's recovery, those being that you only need. they work like TWRP, but TWRP is more advanced with more functions and options available to the user.
i suppose that you have seen those after flashing PE on your device, those important being ADB sideload, update from SD card, some partitions to wipe and factory reset, probably more that I dont remember
bg0169 said:
Why is using TWRP so scary? Why isn't it recommended? Also about the RN10, yea, after you said it, I searched on gsmarena.com and found that both devices were using a SD chipset, not a MediaTek. Didn't think of that...
Click to expand...
Click to collapse
scary for possibly hard bricking your device. since the recovery image is now implemented into the boot partition, a bad boot image will make your device unbootable.
not recommended due to it having almost no functionality, touch screen not working in every build that has been tried here, and other issues, like limitations/errors to flashing, backups, etc.
bg0169 said:
die to the "small system partition size".
Click to expand...
Click to collapse
for some reason, i also have the same issue from nowhere too after I was trying to flash a GSI last week. this could be with an update Xiaomi did to their firmware, but im completely clueless.
anyways, after you reflashed the firmware, has it been solved? (due to you mentioning that you successfully flashed PE)
Sorry for the late reply. I had some things going on.
Yea, the recovery had features, like reboot to bootloader, apply update, enable adb, and stuff. A bit richer than the MIUI stock one, but still not as advanced.
I'm not sure, if you're asking about the flashing GSI problem, but PE worked absolutely fine, and I haven't tried reflashing something else over.
I won't be trying that very soon, because I wanna keep it as is for some time and see if PE satisfies my needs of service.
all twrp builds for camellia cause a camellian hard brick. even without permanent flash. so it's very important for all users that ure curious to test: DONT DO THIS!!!