Related
The ziraat bank application does not open after installing twrp
can you help me
How to make the z5 premium custom recovery
or
how to find the z5 premium custom recovery
Or
How to delete twrp?
The final and out build for Z5p came Nov2017 32.4.A.1.54
modded kernels are here
https://forum.xda-developers.com/z5...oted-kernel-e6833-e6853-e6883-32-4-1-t3686024
on Unlocked bootloader [ UB ]
simply
1. flash stockrom ftf using Flashtool
2. boot till welcome screen and poweroff
3 connect device in fastboot mode and flash modded kernel given in the post and flash TWRP
4. from Twrp, flash MAGISK (instead of supersu) + SELinux zip (permissive) + safteynet cleaning tools.zip
5. reboot,
6. install Magisk Manager 5.8.1 APK
7. install that app which fails to work,
8. from hide magisk, select that app, this will hide root access,
9. try the APP, it should work!
however , if it still fails to work and twrp is the reason
then
power off device
10 . connect device in fastboot mode and in minimal adb window type " fastboot wipe recovery " and enter, this will wipe the recovery
11. boot up and try the app now!
12 if again it doesnt work! then
13. FLASH FOTAKERNEL only! from ftf, don't flash anything else! skip all others in the flashtool! this will flash the Original FOTA Kernel and that bank app should work!
so i gave you 3 scenarios
please be careful!
Advice needed
Hi guys,
I am still looking for how to root my xperia Z5P e6883, and I have found this thread which seems different (hopefully in a better way) from what I had read before.
My boot loader is unlocked, Developer Options activated, USB Debugging activated and also Unknown Sources on. I have done three attempts to root it so far but all of them failed. The last two have displayed the "installing error 1" almost at the very end of the Magisk (v.17 or v.19) flashing process.
Now, reading the above thread, I noticed that I should flash "SELinux zip" but I am unable to spot that .zip file in order to download it. Is anyone willing to help/advise?
Thank you!
hi i am using note 5 ai 6/64 gb with stable chinese rom miui 10.2.1..now i want to shift to global rom..after unlocking bootloader what are the steps i should follow?
download the global rom version of 10.2.1 from
https://forum.xda-developers.com/redmi-note-5-pro/how-to/received-9-5-17-ota-update-t3813192
if you boot is unlocked (finally) (after many days of waiting period)
put the 1.6gb rom in sdcard or otg
then using any good recovery ( i am using orange fox 8.3-2) https://sourceforge.net/projects/orangefox/files/whyred/
extract it and there will be recovery.img file
connact Rn5p in fastboot mode and boot recovery from minimal adb and fastboot window
fasboot boot (& drag drop recovery.img in the terminal window from extracted folder) and press enter ,
device will show MI logo, if your 1.6gb rom is in OTG drive then NOW is the time to connect you OTG before ORANGEFOX logo appear, otherwise it won't read properly.
for clean flash wipe /data /system /cache /internalstorage /delvik etc
then come back to install and from sdcard' or OTG flash the 1.6gb globalrom of 10.2.x once done
reboot atleast till MIUI setup screen
if you wana ROOT
boot back into recovery ( same steps) and
1. take BACKUP OF YOUR BOOT SECTOR, it may backup in your sdcard or OTG drive
and now flash the following
1. lazyflasher.zip (search for Redmi5 / note5A / Note5Pro on XDA) (its a small zip file)
2. flash magisk 17.1 (i dont recomend 18.0 since they have changed the script, and later no rcovery can extract RAMDISK folder from boot sector unless you RE-FLASH the whole rom.
first couple of boots may goto reboot but it should come to miui setup again.
if anything goes wrong,
reboot in to recovery again! and restore the BOOT sector, it will UNDO the lazyflash and Magisk
now, magisk 17x does say that it tries to disable DMvarity so try flashing ONLY MAGISK. for root.
Hi there.
I screwed up my MediaPad M5 Lite (Wifi edition: BAH2-W19, EMUI 8 installed. It's a treble compatible device) yesterday and need help.
I did the following steps before it all went down the gutter:
1. I successfully unlocked the bootloader using the DC Unlocker method
2. I downloaded the latest a-only AOSP release of "phhusson AOSP 9.0 v119": system-arm64-aonly-vanilla-nosu.img.xz (https://github.com/phhusson/treble_experimentations/releases)
3. I rebooted into bootloader and flashed the unzipped .img file to the device. The flash was successful as all 4 steps of copieing stuff tot he system partition said "OKAY"
4. now I used "fastboot reboot" and the trouble started. The tablet froze in fastboot mode. It just didn't restart.
5. I turned it of using a long push on the power button. Then it restarted and got stuck at the start screen. I'll attach a screenshot so you know what I am seeing.
6. From now on I was only able to boot into fastboot mode and into the stock recovery. There I did factory reset and cache formatting several times but with no effect.
7. Only thing that still worked was the eRecovery function in the EMUI stock recovery. With this I was able to download some official firmware from Huawei automatically and the tablet was back to stock
8. This night the OS did an auto update to v215.
9. So this morning I repeated the step 2. from above but with a different a-only custom rom and again it didn't work out
10. I tried to use the eRecovery function to get back to stock, but now the recovery is broken and throws an error "Getting package info failed".
I also tried to download older firmware from https://androidhost.ru/ and flash it with the dload method. Without success of course. While doing it I receive an error "Software install failed!". I will attach a screenshot.
Can anybody give me a hint what I could do next to approach the problem?
Best
rob
Well, you didn't had TWRP as recovery, so no nandroid backup available. From one of my experiences with flashing a stock rom for acer, I had to delete some lines of code from the meta inf folder relating the version of the phone, in order to successfully flash it. Maybe the stock ROM you are trying has some lines of code detecting if bootloader unlocked.
Im also having trouble getting a good tutorial for getting rid of the os or just to have magisk on the tablet
You dowoad latest rom and flash stock via hru and. Twrp search xda
unbrick Huawei MediaPad M5 Lite
r0b said:
Hi there.
I screwed up my MediaPad M5 Lite (Wifi edition: BAH2-W19, EMUI 8 installed. It's a treble compatible device) yesterday and need help.
I did the following steps before it all went down the gutter:
1. I successfully unlocked the bootloader using the DC Unlocker method
2. I downloaded the latest a-only AOSP release of "phhusson AOSP 9.0 v119": system-arm64-aonly-vanilla-nosu.img.xz (https://github.com/phhusson/treble_experimentations/releases)
3. I rebooted into bootloader and flashed the unzipped .img file to the device. The flash was successful as all 4 steps of copieing stuff tot he system partition said "OKAY"
4. now I used "fastboot reboot" and the trouble started. The tablet froze in fastboot mode. It just didn't restart.
5. I turned it of using a long push on the power button. Then it restarted and got stuck at the start screen. I'll attach a screenshot so you know what I am seeing.
6. From now on I was only able to boot into fastboot mode and into the stock recovery. There I did factory reset and cache formatting several times but with no effect.
7. Only thing that still worked was the eRecovery function in the EMUI stock recovery. With this I was able to download some official firmware from Huawei automatically and the tablet was back to stock
8. This night the OS did an auto update to v215.
9. So this morning I repeated the step 2. from above but with a different a-only custom rom and again it didn't work out
10. I tried to use the eRecovery function to get back to stock, but now the recovery is broken and throws an error "Getting package info failed".
I also tried to download older firmware from https://androidhost.ru/ and flash it with the dload method. Without success of course. While doing it I receive an error "Software install failed!". I will attach a screenshot.
Can anybody give me a hint what I could do next to approach the problem?
Best
rob
Click to expand...
Click to collapse
Unbrick using Huawei Multi tool .
---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------
r0b said:
Hi there.
I screwed up my MediaPad M5 Lite (Wifi edition: BAH2-W19, EMUI 8 installed. It's a treble compatible device) yesterday and need help.
I did the following steps before it all went down the gutter:
1. I successfully unlocked the bootloader using the DC Unlocker method
2. I downloaded the latest a-only AOSP release of "phhusson AOSP 9.0 v119": system-arm64-aonly-vanilla-nosu.img.xz (https://github.com/phhusson/treble_experimentations/releases)
3. I rebooted into bootloader and flashed the unzipped .img file to the device. The flash was successful as all 4 steps of copieing stuff tot he system partition said "OKAY"
4. now I used "fastboot reboot" and the trouble started. The tablet froze in fastboot mode. It just didn't restart.
5. I turned it of using a long push on the power button. Then it restarted and got stuck at the start screen. I'll attach a screenshot so you know what I am seeing.
6. From now on I was only able to boot into fastboot mode and into the stock recovery. There I did factory reset and cache formatting several times but with no effect.
7. Only thing that still worked was the eRecovery function in the EMUI stock recovery. With this I was able to download some official firmware from Huawei automatically and the tablet was back to stock
8. This night the OS did an auto update to v215.
9. So this morning I repeated the step 2. from above but with a different a-only custom rom and again it didn't work out
10. I tried to use the eRecovery function to get back to stock, but now the recovery is broken and throws an error "Getting package info failed".
I also tried to download older firmware from https://androidhost.ru/ and flash it with the dload method. Without success of course. While doing it I receive an error "Software install failed!". I will attach a screenshot.
Can anybody give me a hint what could do next to approach the problem?
dnrob
Click to expand...
Click to collapse
You can install these roms only if you can downgrade to update v177 and lower
Like me you need to Unbrick your mediapad m5 lite
First place need to go back in Fastboot mode.
So UNPLUG , turn off , wait a second and turn on with volume Down , when screen blink release power button and keep volume down pressed a second until Fastboot mode
Or, try to boot in Fastboot with volume down + power AND USB plugged in goes into fastboot, or TWRP if you flashed TWRP to RECOVERY2 instead to RECOVERY.
If doesnt work try the same plug or unplug cuz we have Recovery_ramdisk , eRecovery and eRecovery2
WHEN its okay and you can turn on fastboot mode
Second prepair the img's for unbricking
The LEGIT methods its come back stock rom , then you'll be able to do what you want.
Download Huawei Multi-Tools , Huawei Update Extractor and update.zip of your stock ROM and update_data_full
Then use Huawei Update Extractor to extract
system.img ramdisk.img recovery_ramdisk.img From update.app\update.zip and
Cust.img from update.app\update_full_public.zip.
If you have backup of your userdata.img its the time to put all together in the same directory before go futher.
If all its good , you just need to click unbrick.
Maybe i'll soon do a guide for unbrick and prevent brick , and how install twrp without losing data or encryption data
helmuth said:
And just for the complete list:
Volume up + power AND USB plugged in goes into eRecovery (or TWRP, if you flashed TWRP to RECOVERY2 instead to RECOVERY)
Volume up and down + power and USB plugged in forces update via USB (indicated by a little USB-like icon in the recovery circle. The progess bar goes to 5% and waits for input from your PC)
Click to expand...
Click to collapse
RAMDISK238.img, Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip and twrp8.img you will find at
android-hilfe.de->forum huawei-mediapad-m5-lite -> custom-roms-mediapad page-5
Theese custom roms should work:
Andy Yan's LineageOS 17 (Android 10) -> lineage-17.0-20191231-UNOFFICIAL-treble_arm_avN.img.xz
Pierre-Hugues Husson AOSP 10.0 v209 -> system-quack-arm64-aonly-vanilla.img.xz
Following this guide you will loose all your data so be sure to have a backup
This should work for a Mediapad M5 lite BAH2-W19OCEC432-238
Precondition: Unlocked Bootloader / OEM Unlocked / USB Debugging active
1. if you brick your device don`t blame me
2. check, if the version B238 is installed
3. back up your data
4. copy Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip on SD card
Fastboot:
5. boot into Fastboot Mode.
6. flash TWRP -> fastboot flash recovery_ramdisk twrp8.img
7. fastboot reboot recovery (the first time booting should show up the twrp menu)
if the boot message "2. Press Volume up for 3 seconds" appears must do a Factory Reset in the Stock Recovery. After a reboot the TWRP menu shows up. In lineageos you can activate advanced reboot in developer settings to boot in TWRP menu by pressing recovery mode
TWRP:
8. Wipe -> Advanced Wipe -> select data + cache + dalvik-cache -> Swipe to wipe -> back to start menu
9. Install -> Select Storage -> select Mircro SD card -> OK -> select Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip -> Swipe to confirm Flash
10. Reboot -> Bootloader (not System!!!)
Fastboot:
11. fastboot flash ramdisk RAMDISK238.img
12. fastboot flash system lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img
(or AOSP 10.0 v209)
13. fastboot reboot
LineageOS should start.
other custom roms could work as well.......
Edit:
There´s a new version of LineageOS available:
https:######sourceforge.net###projects###andyyan-gsi###files###lineage-17.x###lineage-17.1-20200111-UNOFFICIAL-treble_arm64_avN.img.xz###download
replace ### with /
It works well on my m5lite
It did not work on B239
I am trying now to get back to the stock rom.
I think the problem is with RAMDISK238.img :/
Do you know how to get one for 239?
Thanks !
BesterTrainer said:
RAMDISK238.img, Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip and twrp8.img you will find at
android-hilfe.de->forum huawei-mediapad-m5-lite -> custom-roms-mediapad page-5
Theese custom roms should work:
Andy Yan's LineageOS 17 (Android 10) -> lineage-17.0-20191231-UNOFFICIAL-treble_arm_avN.img.xz
Pierre-Hugues Husson AOSP 10.0 v209 -> system-quack-arm64-aonly-vanilla.img.xz
Following this guide you will loose all your data so be sure to have a backup
This should work for a Mediapad M5 lite BAH2-W19OCEC432-238
Precondition: Unlocked Bootloader / OEM Unlocked / USB Debugging active
1. if you brick your device don`t blame me
2. check, if the version B238 is installed
3. back up your data
4. copy Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip on SD card
Fastboot:
5. boot into Fastboot Mode.
6. flash TWRP -> fastboot flash recovery_ramdisk twrp8.img
7. fastboot reboot recovery (the first time booting should show up the twrp menu)
if the boot message "2. Press Volume up for 3 seconds" appears must do a Factory Reset in the Stock Recovery. After a reboot the TWRP menu shows up. In lineageos you can activate advanced reboot in developer settings to boot in TWRP menu by pressing recovery mode
TWRP:
8. Wipe -> Advanced Wipe -> select data + cache + dalvik-cache -> Swipe to wipe -> back to start menu
9. Install -> Select Storage -> select Mircro SD card -> OK -> select Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip -> Swipe to confirm Flash
10. Reboot -> Bootloader (not System!!!)
Fastboot:
11. fastboot flash ramdisk RAMDISK238.img
12. fastboot flash system lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img
(or AOSP 10.0 v209)
13. fastboot reboot
LineageOS should start.
other custom roms could work as well.......
Edit:
There´s a new version of LineageOS available:
https:######sourceforge.net###projects###andyyan-gsi###files###lineage-17.x###lineage-17.1-20200111-UNOFFICIAL-treble_arm64_avN.img.xz###download
replace ### with /
It works well on my m5lite
Click to expand...
Click to collapse
sasuke988 said:
It did not work on B239
I am trying now to get back to the stock rom.
I think the problem is with RAMDISK238.img :/
Do you know how to get one for 239?
Thanks !
Click to expand...
Click to collapse
https://
pro-teammt.ru/
en/
online-firmware-database/
?firmware_model=BAH2-W19&firmware_page=0
Check out your model (C432C431/...)
Use the huawei extractor to extract the images
Can someone check if this is legit? https://romprovider.com/2019/09/9-1-0-151-b151-firmware-jordan2-l09b/amp/
Raresh T said:
Can someone check if this is legit? https://romprovider.com/2019/09/9-1-0-151-b151-firmware-jordan2-l09b/amp/
Click to expand...
Click to collapse
It's for the 8" screen variant. It won't work on our 10.1"
is there any current custom house for this model because no links work. And on the stock, I have a problem with 5ghz Wi-Fi
You'd better install TWRP,flash FBE-disabler and format data partition
Anyway,firmware can be found at professorjtj.github.io and I recommend you rebrand and update it to EMUI9 to get better treble compatibility
SkipM4 said:
You'd better install TWRP,flash FBE-disabler and format data partition
Anyway,firmware can be found at professorjtj.github.io and I recommend you rebrand and update it to EMUI9 to get better treble compatibility
Click to expand...
Click to collapse
thats an interesting suggestion. could you post some guides on how could someone rebrand their device ?
Today the unlock time for bootloader to unlock will complete and I Intend to install TWRP. I have found the latest officially supported twrp-3.6.1_11-0-alioth.img at https://eu.dl.twrp.me/alioth/. How does it compare to TWRP-3.5.1 https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-1-20210702.4300189/.
Can anyone guide me what are the pros and cons of using twrp-3.6.1_11-0-alioth.img and its limitations as compared to TWRP-3.5.1 as I can not find any documentation on twrp-3.6.1_11-0-alioth.img. Any help will be appreciated.
Also does the following limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0-alioth.img ?
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
hofi01 said:
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
Click to expand...
Click to collapse
I know where the lastest TWRP for Poco F3 is and how to install it as I have already installed it. That was not the question. The question was that "does limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0'? Limitattions like being forced to reboot TWRP after flashing a every single zip file and other limitations like it as mentioned above. Thanks for your reply anyways.
so for me, TWRP does not start again, after installing a file.
I install TWRP, boot into TWRP again and install Magisk. after that I boot into the ROM.
TWRP does not restart itself
So, still no decryption on A12?
I wanted to test new custom roms but i dont want to have to reinstall everything from scratch if i go back to my current rom (.EU).
Can twrp make a full backup and restore it despite not having decryption?
If it cant, can I make a full back up of my phone from cmd in fastboot mode? (so i can just flash it from fastboot to restore everything as it is now)
Code:
Code:
/*
* Your warranty is now void!!!
*
* If sh!t happens, i am not responsible for your bricked device.
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications,
* Do at your own risk!!!
*/
Version and device Information:
Status: Testing
Device: Samsung m33
Codename: m336BU
Android version: android-12 (M336BUXXS4BWB1)
Release Date: April 15, 2023
INSTALLATION
Connect to pc and boot into stock recovery
Factory reset
Reboot into download mode.
flash twrp.tar into the ap slot
reboot to recovery
After that flash samsung multidisabler zip
Reboot to recovery from main menu (not just reboot)
(optional) Backup boot, data, super and dtbo
Reboot to system
Downloads:TWRP Image: twrp-12.1_3.7.0-v000-m33-20230408.tar.md5
Multidisabler: multidisabler-samsung-3.1.zip
wud u also be interested to look into working custom roms for m33 cuz my phone overheats really bad even with optimization and root
ok so i tried to flash with odin but didnt reset phone cuz its custom recovery and people say it shudnt be a problem. anyway when i tried to flash the ap file odin just crashes so i dunno what to do. so now im gonna try to uninstall magisk, then patch the firmware back to stockwith home_csc, then install twrp and then reinstall magisk again and hopefully my data doesnt get wiped but i have the pics saved so its just a huge hassle if that happens.
im very happy to say that my data has been wiped and the recovery file keeps crashing odin. pls offer help if theres any to offer asap cuz i dont wanna lose progress again when i installed everything again
fluffyball21 said:
im very happy to say that my data has been wiped and the recovery file keeps crashing odin. pls offer help if theres any to offer asap cuz i dont wanna lose progress again when i installed everything again
Click to expand...
Click to collapse
Okey, i will fix the isuue asap.
Shibu Shaji said:
Okey, i will fix the isuue asap.
Click to expand...
Click to collapse
hey so i just had to rename the img file inside tar to recovery.img and pack it back to tar.md5 and it flashed. But the phone goes into bootloop after that and cannot be used unless i flash my old recovery file. also im on custom gsi rom android 13 with patched recovery for fastbootd
GitHub - Johx22/Patch-Recovery: CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd.
CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd. - GitHub - Johx22/Patch-Recovery: CI service that patches recovery.img of Dyn...
github.com
hey btw im also trying to make my own twrp for the phone but mine also bootloops after installation. i also tried other twrp for phones with exynos 1280 like a33 and a53 and they both recognize my device as a33 or a53 on pc when flashed but twrp shows black screen i dunno what else to do at this point
There is really so much need of a custom Rom for this device.
fluffyball21 said:
wud u also be interested to look into working custom roms for m33 cuz my phone overheats really bad even with optimization and root
Click to expand...
Click to collapse
Please could you tell me the steps to install twrp.. and also share me working twrp and gsi for this Device I'm really tired of this buggy One Ui
sunnypoddar1919 said:
Please could you tell me the steps to install twrp.. and also share me working twrp and gsi for this Device I'm really tired of this buggy One Ui
Click to expand...
Click to collapse
There's no working twrp as of now but u can patch the recovery IMG of ur device with the patch recovery link I pasted above. Then u can use fastbootd on ur device then download a working gsi from this list then flash it
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
Keep in mind if u don't know what ure doing and don't have backup then if bootloop happens u wud have to reset the device and flash stock firmware through bootloader so continue at ur own risk
fluffyball21 said:
There's no working twrp as of now but u can patch the recovery IMG of ur device with the patch recovery link I pasted above. Then u can use fastbootd on ur device then download a working gsi from this list then flash it
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
Keep in mind if u don't know what ure doing and don't have backup then if bootloop happens u wud have to reset the device and flash stock firmware through bootloader so continue at ur own risk
Click to expand...
Click to collapse
could you tell me how can i patch my device recovery because it's first time i'm dealing with samsung for custom roms..i have rooted an another samsung device but for that TWRP was already available
sunnypoddar1919 said:
could you tell me how can i patch my device recovery because it's first time i'm dealing with samsung for custom roms..i have rooted an another samsung device but for that TWRP was already available
Click to expand...
Click to collapse
U need to have stock firmware for ur device then extract the ap file from that zip file. Then extract recovery.img.lz4 from ap file then follow the tutorial in this guide and do as it says. After all that's done ull get a zip file and u can flash that via odin by putting it in ap file slot
GitHub - Johx22/Patch-Recovery: CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd.
CI service that patches recovery.img of Dynamic Samsung devices launched with Android 10 and above to enable fastbootd. - GitHub - Johx22/Patch-Recovery: CI service that patches recovery.img of Dyn...
github.com
i have flashed the patched recovery by doing all these steps, could you tell me now how can i flash gsi next by the way i have downloaded pixel experince plus (unofficial from your link that you have provided)
sunnypoddar1919 said:
i have flashed the patched recovery by doing all these steps, could you tell me now how can i flash gsi next by the way i have downloaded pixel experince plus (unofficial from your link that you have provided)
Click to expand...
Click to collapse
Follow this guide
How to Flash a GSI on an Android Device
Follow this guide to flash a GSI on your Android device.
www.makeuseof.com
To get into fastbootd u need to go to recovery mode then select enter fastbootd
fluffyball21 said:
Follow this guide
How to Flash a GSI on an Android Device
Follow this guide to flash a GSI on your Android device.
www.makeuseof.com
To get into fastbootd u need to go to recovery mode then select enter fastbootd
Click to expand...
Click to collapse
When ever i use adb reboot bootloader device boot into download mode and fastboot commands are not working there so i simply can't access fastboot even also adb reboot fastboot or adb reboot fastbootd not working when giving these commands device simply just reboots , please can you tell me how you got into recovery and then into fastboot mode after flashing patched recovery in brief ...And also i think my recovery isn't patched or did not worked after patching may be the script is not working or i made any mistake while using the script so will it work if you attach the patched recovery of your m33 5g device if i flash that using odin?
sunnypoddar1919 said:
When ever i use adb reboot bootloader device boot into download mode and fastboot commands are not working there so i simply can't access fastboot even also adb reboot fastboot or adb reboot fastbootd not working when giving these commands device simply just reboots , please can you tell me how you got into recovery and then into fastboot mode after flashing patched recovery in brief ...And also i think my recovery isn't patched or did not worked after patching may be the script is not working or i made any mistake while using the script so will it work if you attach the patched recovery of your m33 5g device if i flash that using odin?
Click to expand...
Click to collapse
Reboot to recovery from phone then choose enter fastbootd option if it is there. If it is not then u need to patch the recovery again and download that then flash that with Odin. I don't have the patched file with me now so in the meantime try again
fluffyball21 said:
Reboot to recovery from phone then choose enter fastbootd option if it is there. If it is not then u need to patch the recovery again and download that then flash that with Odin. I don't have the patched file with me now so in the meantime try again
Click to expand...
Click to collapse
tried , tried and tried and now i'm tired i think for me it's not possible
U just need extract it then flash it with odin in ap slot also while having auto restart off in options
fluffyball21 said:
U just need extract it then flash it with odin in ap slot also while having auto restart off in options
Click to expand...
Click to collapse
if auto restart has to be off then how would i restart into recovery from download mode means which button combination i have to press
sunnypoddar1919 said:
if auto restart has to be off then how would i restart into recovery from download mode means which button combination i have to press
Click to expand...
Click to collapse
U gotta press volume down and power after it finishes flash then immediately switch to volume up and power key combination when the screen turns black. If u failed to get fastbootd u need to do it again by either reboot to bootloader from recovery or pressing volume down and power on bootscreen then pressing volume up and down while USB is connected to computer and reflash. Once u do it successfully I think it wud be there for the next time without issues