Database Develop

Odin flash twrp boot loop

I followed the steps in this guide attempting to flash a rom. https://forum.xda-developers.com/tm...lopment/rom-stock-debloated-deodexed-t3423387
I was able to flash the BL and modem no problem. I proceeded to flash twrp and have been stuck at boot since. I can only go back into DL mode. Read a few places that said to reinstall rom. How do i go about installing a rom via odin? Any help is greatly appreciated.

jleed88 said:
I followed the steps in this guide attempting to flash a rom. https://forum.xda-developers.com/tm...lopment/rom-stock-debloated-deodexed-t3423387
I was able to flash the BL and modem no problem. I proceeded to flash twrp and have been stuck at boot since. I can only go back into DL mode. Read a few places that said to reinstall rom. How do i go about installing a rom via odin? Any help is greatly appreciated.
Click to expand...
Click to collapse
Okay. Here's what you do...
First, boot to DOWNLOAD MODE. Once in Download Mode, press the keys again like you are booting to Download Mode (VOLUME DOWN + HOME + POWER)
Watch the screen while holding the keys. When the screen goes blank, switch to the key combination for booting RECOVERY (VOLUME UP + HOME + POWER) and hold them until the TWRP screen appears. If the TWRP screen does not appear then we know TWRP didn't stick when you flashed it via Odin.
If the TWRP screen appears, release the keys and let it continue to boot to TWRP.
If TWRP does not boot, then I'd suggest flashing the stock firmware for your device. You can download the stock firmware for your device from www.sammobile.com or from www.updato.com
Sammobile.com is a very slow download unless you pay for a premium account. Updato is much faster. Make sure to select the correct region for your device before downloading the firmware.
Which version of Odin are you using? I've been using 3.12.3 and haven't had any problems at all with this version.
Once you habe downloaded the stock firmware, open Odin. Boot your device to Download Mode and then connect your USB cable. Make sure Odin shows you are connected.
Next, click the OPTIONS TAB in Odin and un-check
AUTO REBOOT. Then, select the AP TAB in Odin and navigate to the firmware file you have downloaded. Let Odin do its thing to verify the file and click START to begin the flash. Once the flash is complete, disconnect the USB Cable and press the key combination for booting to Download Mode again. Once the screen goes black, switch to the key combination for booting RECOVERY. Once in recovery you can select the reboot option to boot your device normally and start fresh from there and attempt to flash TWRP again.
Also, which Note 5 do you have?

fast69mopar said:
Okay. Here's what you do...
First, boot to DOWNLOAD MODE. Once in Download Mode, press the keys again like you are booting to Download Mode (VOLUME DOWN + HOME + POWER)
Watch the screen while holding the keys. When the screen goes blank, switch to the key combination for booting RECOVERY (VOLUME UP + HOME + POWER) and hold them until the TWRP screen appears. If the TWRP screen does not appear then we know TWRP didn't stick when you flashed it via Odin.
If the TWRP screen appears, release the keys and let it continue to boot to TWRP.
If TWRP does not boot, then I'd suggest flashing the stock firmware for your device. You can download the stock firmware for your device from www.sammobile.com or from www.updato.com
Sammobile.com is a very slow download unless you pay for a premium account. Updato is much faster. Make sure to select the correct region for your device before downloading the firmware.
Which version of Odin are you using? I've been using 3.12.3 and haven't had any problems at all with this version.
Once you habe downloaded the stock firmware, open Odin. Boot your device to Download Mode and then connect your USB cable. Make sure Odin shows you are connected.
Next, click the OPTIONS TAB in Odin and un-check
AUTO REBOOT. Then, select the AP TAB in Odin and navigate to the firmware file you have downloaded. Let Odin do its thing to verify the file and click START to begin the flash. Once the flash is complete, disconnect the USB Cable and press the key combination for booting to Download Mode again. Once the screen goes black, switch to the key combination for booting RECOVERY. Once in recovery you can select the reboot option to boot your device normally and start fresh from there and attempt to flash TWRP again.
Also, which Note 5 do you have?
Click to expand...
Click to collapse
Hey, thanks for your response. So I was able to get my System back to working. I had to downoad the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.

jleed88 said:
Hey, thanks for your response. So I was able to get my System back to working. I had to downoad the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
Click to expand...
Click to collapse
What you have to do is this...
Flash TWRP, swipe to allow system modifications and then flash the no_verity_opt_encrypt_5.1.zip available from
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
This zip will disable dm-verity and forced encryption in the fstab and allow you to boot normally.
Once this had been done you can flash the root zip of your choice and go to town with debloating, custom ROM's and custom kernels.

jleed88 said:
Hey, thanks for your response. So I was able to get my System back to working. I had to download the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
Click to expand...
Click to collapse
fast69mopar said:
What you have to do is this...
Flash TWRP, swipe to allow system modifications and then flash the no_verity_opt_encrypt_5.1.zip available from
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
This zip will disable dm-verity and forced encryption in the fstab and allow you to boot normally.
Once this had been done you can flash the root zip of your choice and go to town with debloating, custom ROM's and custom kernels.
Click to expand...
Click to collapse
When i flashed TWRP i unchecked the Auto-Reboot option. did a key combo to get to twrp but it didnt ask me to swipe to allow system modification. So i went ahead and flashed no_verity_opt_encrypt_5.1.zip with success. Proceeded to flash SuperSU-v2.66 and it got stuck at -Creating paths. I rebooted to recovery and found this guide https://forum.xda-developers.com/galaxy-s6/general/root-s6-nougat-supersu-t3570740
Coming from sickmade 6.0.1 and through all the struggles i am now at stock ROOTED firmware EQG3 andriod 7.0! I just had to take my time and search around a bit. You guys are all amazing. Hopefully if someone has this problem they will find this thread.

jleed88 said:
When i flashed TWRP i unchecked the Auto-Reboot option. did a key combo to get to twrp but it didnt ask me to swipe to allow system modification. So i went ahead and flashed no_verity_opt_encrypt_5.1.zip with success. Proceeded to flash SuperSU-v2.66 and it got stuck at -Creating paths. I rebooted to recovery and found this guide https://forum.xda-developers.com/galaxy-s6/general/root-s6-nougat-supersu-t3570740
Coming from sickmade 6.0.1 and through all the struggles i am now at stock ROOTED firmware EQG3 andriod 7.0! I just had to take my time and search around a bit. You guys are all amazing. Hopefully if someone has this problem they will find this thread.
Click to expand...
Click to collapse
Glad it's working for you. Good job. Now you can make your Note 5 your own. I'm an S6 Edge Plus user. We use the exact same ROM as the Note 5. We just use a different kernel. Happy flashing. If you run into any issues don't hesitate to ask me or anyone else here at XDA. This is a great place to read and learn especially with your Note 5. If a problem has occurred before you can bet that someone has posted about it and you will find a solution.

the phone initially booted up normally. and i power off try to enter recovery mode but i got bootloop , is there any way to get into odin mode , recovery mode is broken ( i flashed recovery with odin it took 15 minutes so i click stop and it crashed ) my phone is sm m20

Honor 9 Lite Disastrous Brick - Unrecoverable?

I managed to brick my Honor 9 Lite while attempting to root it, and it seems that all recovery methods have failed. Is there any way to restore back to stock firmware, or should I just give up and put it through a shredder? Here's what happened:
1. Set up as a new device and successfully unlocked the bootloader
2. Installed unofficial TWRP build via fastboot
3. Attempted to install SuperSU, which failed at decompression stage
4. Flashed a "System-Mode" SuperSU, which appeared to succeed
5. When rebooting, the device hangs at the "Honor" boot logo and never successfully enters the home screen
There are a few things to note at this point:
- The TWRP build may have been faulty, as none of the user preferences would save properly
- Before attempting to root, I tried to make a TWRP backup multiple times, and every time it failed with error 255, probably because TWRP itself was faulty, hence I have no backup to restore to
Here's what I've tried to recover the system:
- Entered eRecovery, connected to Wi-Fi but it could not gather package info from their servers
- Downloaded the stock firmware package and saved it to the correct location on the micro SD card, attempting to install it via the "three-button" mode would begin the process but fail at 5%, with an "install failed" message
- Connected to HiSuite in fastboot mode, attempting to recover results in a "your device is not supported" message
- Visited the URLs displayed on the device in each of the recovery mode failure screens, they're all dead links (Huawei reorganising their website?)
- Used TWRP to wipe cache, Dalvik cache before repeating above steps
- Attempted a factory reset, still stuck at the boot animation
- Re-locked the boot loader and retried the above steps
- Flashed LineageOS via TWRP, it just stays at the Lineage boot animation for 10 minutes before automatically rebooting to eRecovery
- Copied the stock update.zip to the SD card and attempted to flash via TWRP, it just fails
- Extracted the parts from update.app and manually flashed each to the device via fastboot, still gets stuck on the boot animation
Is there anything else I should try before giving up and tossing it in the trash?
Edit:
I bought this thing yesterday, it lasted a grand total of less than 12 hours before bricking. There's no important data on it whatsoever, so I don't care if anything needs to be formatted.

My guess: if You can flash los than do it and flash stock recovery after that. Worked for me.

Info needed :
- Bootloader unlocked
- FRP unlock
- What's your Build ( example: LLD-L31C432B131 / LLD-L31 8.0.0.131/C432) )
If bootloader and FRP unlock and you can boot to bootloader : it's a little problem
You need your Build FULL-Update.
Extract with "UpdateExtractor" : ramdisk.img + recovery_ramdis.img + system.img
Extractor do automatic for all *.img the *.img.header / you have now 6 files
copy this 6 files in your "adb"-folder / boot to bootloader / go to your "adb"-folder
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot
if this work : your phone have now stock-ROM and boot as "new"-phone (format data, initial-settings ...)
if this not work (recovery stop at 5%) you have chance "2"
look this : https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085
reed the instruction
if you understand and can do this it's the same result : at the end your phone boot with stock-ROM
with this way i have my Honor 9 Lite reset to stock-ROM

JamesBott said:
Info needed :
- Bootloader unlocked
- FRP unlock
- What's your Build ( example: LLD-L31C432B131 / LLD-L31 8.0.0.131/C432) )
If bootloader and FRP unlock and you can boot to bootloader : it's a little problem
You need your Build FULL-Update.
Extract with "UpdateExtractor" : ramdisk.img + recovery_ramdis.img + system.img
Extractor do automatic for all *.img the *.img.header / you have now 6 files
copy this 6 files in your "adb"-folder / boot to bootloader / go to your "adb"-folder
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot
if this work : your phone have now stock-ROM and boot as "new"-phone (format data, initial-settings ...)
if this not work (recovery stop at 5%) you have chance "2"
look this : https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085
reed the instruction
if you understand and can do this it's the same result : at the end your phone boot with stock-ROM
with this way i have my Honor 9 Lite reset to stock-ROM
Click to expand...
Click to collapse
Thanks for your response, my device is both FRP and bootloader unlocked, build LLD-L31C432B127.
I have already tried manually flashing ramdisk, ramdisk recovery, and system, however it is still bootlooping.
I have also tried the HWOTA method, however there is no su. I am also not able to access adb, only fastboot. Previously adb would work at the boot animation, however now nothing appears when I type adb devices.

You have to be in TWRP to use adb, if I remember right.

I think, you ar the same problem as i for many week.
If you can - check following : download this TWRP https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
flash TWRP, boot to recovery "USB-Wire out phone, press and hold Vol-Up and Power, if phone restart less Power, on bootscreen less Vol-Up.
now start TWRP.
if you setting PIN for screen-unlock TWRP write on start "input code for decrypt" : you can now over-step
in TWRP go to reboot, boot system.
now 2 possibility : 1= system boot, 2= phone boot to TWRP
check this please and give answer, what phone doing

JamesBott said:
I think, you ar the same problem as i for many week.
If you can - check following : download this TWRP https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
flash TWRP, boot to recovery "USB-Wire out phone, press and hold Vol-Up and Power, if phone restart less Power, on bootscreen less Vol-Up.
now start TWRP.
if you setting PIN for screen-unlock TWRP write on start "input code for decrypt" : you can now over-step
in TWRP go to reboot, boot system.
now 2 possibility : 1= system boot, 2= phone boot to TWRP
check this please and give answer, what phone doing
Click to expand...
Click to collapse
Thank you so much!
While a direct boot from TWRP did not work, completely migrating the HWOTA files and then booting into the "no-check" recovery successfully forced an update, and the system was properly restored. The device is now up and running and I was able to root it. Sadly, TWRP still doesn't make backups properly, so I will have to be careful.

ok : now you have 99% stock-ROM
the last 1% is "encrypted data".
if your data is "encrypted" is a little security for you (is phone lost)
i hope you use the TWRP from Pretorian80
first now set PIN for screen-unlock (no fingerprint, no other)
check this : tap on power, phone go stand-by, tap on power, phone wake up and need PIN
next do : flash stock-recovery, boot to recovery and wipe data AND recovery do low-level format data
flash TWRP, boot to TWRP and this write "give me the PIN for decrypt"
if this - your data now encrypted
if this not - other way : boot to bootloader
fastboot flash stock-recovery
fastboot erase userdata
reboot phone, stock-recovery format data low-level
flash TWRP and check
now give answer what work and what NO
only stock-recovery can format data WITH encryption - i do not know another way
on a brand new phone with NO PIN setting the TWRP write "i use the standard code for decrypt"
is a PIN set the TWRP write "give me the PIN for decrypt"
the best on this "little" bootloop : you learning your phone understanding

I found this useful tool, just in case someone need to recover his device.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
You only need to be able to access TWRP and have aN update.zip with a full OTA

twrps not installing

is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance

leerh said:
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
Click to expand...
Click to collapse
Okay ?
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue

IamRdw said:
Okay
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
Click to expand...
Click to collapse
if you want OTA(over the air) updates you need to lock bootloader. otherwise the updater will say something like phone has been rooted and they cant provide you an update
https://forum.xda-developers.com/z5-pro-gt/how-to/installing-ota-update-11-5-141-via-twrp-t4050027

http://anago.2ch.sc/test/read.cgi/sm...ne/1577014188/ theres a lot of information on this link here are some highlights for me
_____________________________________
>> Crash dump loop of 113 ROM burnt Z5PROGT can be restored by burning CNROM for the time being,
Even if I tried it again, it was useless, so if I look at the syntax at the time of batch execution, it seems that vbmeta.img is not burned.
It says unrecognised option `--disable-verification '.
This time, the boot loader loop only started, and TWRP couldn't start.
This time it may be packed
__________________________________________
>> 117
I'm sorry I want to confirm.
Where did you use the fastboot command?
①fastboot --disable-verification flash vbmeta vbmeta.img
②fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It is ① that I instructed, but it looks like there are two kinds when I check it on the net.
He seemed to have hit it without knowing it.
Excuse me, can you hit both again?
________________________________________
>> 150
>> I burned 113 ZUI11 version Gro ROM.
I re-added TWRP, but when I started it, it was usable normally, so I could add Magisk,
After that, it only seems to be unavoidable that it only starts up in normal recovery mode.
It is troublesome to do it every time you want to use TWRP, but it can't be helped.
__________________________________________________ _______
this helped Solved

Question HELP : Boot Loop and can't enter recovery / download

Hi All...
i unlocked my Samsung A8 2021 bootloader, patched the AP file with magisk and flashed it with odin.
i am now in bootloop without any way to go into recovery or download mode.
tried all buttons combinations with pluging ang nnpuging the device.
i now sww posts regarding pathing only the boot.img and the entire AP file but the damage has been done...
anything i can do to make my device working again?
thank you!

ok i managed to enter download and went back to stock with odin.
what did i miss?
should i now patch only the boot.img in magisk and do it again?
will that work?
thanks

Hey @tlccksww , how did you get back into Download Mode? I botched my update with Odin and can't get Download Mode to launch. I can get to the recovery, can also run ADB commands, but can't get back into the bootloader.

Having 'Trouble' Flashing Recovery -- SM-G973F [ Beyond1LTE ]

_______________________________________________
Model: SM-G973F [Beyond1LTE]
One UI: v4.1
Android: v12
Baseband: G973FXXSGHWB3
Build: G973FXXSGHWC1
Security Patch: 01 March 2023
Bootloader: Unlocked
(Verified through "Developer Options"
--> 'OEM Unlocked - On' (Greyed out)
_______________________________________________
I am having trouble flashing a Recovery file on this Galaxy S10.
I used Odin v3.13.3 and v3.14.1 ,
and in both times, Odin detects the phone is connected
but when I tried to flash the
• recovery.tar (in "AP")
• vbmeta.tar (in "CP")
Odin does not show that it flashed any of the files,
ie. there is no progress.
I'm waiting for about 1+ minutes, with no activity to show flashing is in progress.
Should it take longer than that?
I have also tried to patch the recovery through Magisk,
ie. after installing Magisk.apk on the phone,
and I directly patch the recovery.img file through Magisk.
Then, tried flashing this patched recovery.tar through Odin,
and there's still no progress in Odin to show me it's flashing.

I've figured out my problem.
I was able to flash the recovery file successfully today.
The solution was that the filename MUST be named exactly:
--> recovery.img (inside recovery.tar )
It must be spelt exactly that way: " recovery . img "
I only renamed my .tar file, as " recovery "
So, everyone ... don't repeat my mistake !

I have a weird issue now, on my S10 [Beyond1LTE].
I installed TWRP recovery and a LineageOS-based ROM,
and it was working fine for a few hours.
Through the ROM, I clicked to reboot to recovery,
and then, now my phone is in some kind of bootloop.
It does not go into recovery either.
I simply cannot get the phone to enter Recovery,
so I need help with this now.
Is it true that if the "USB Debugging"
in 'Developers Options' is switched on,
then I cannot enter the Recovery mode ?

Anyone got any tips or tricks, on how to get the S10 phone,
to enter into "Download" mode ?
Whatever I do, the phone just goes straight to booting ROM
(which itself does not load & hangs),
so I am trying to get into 'Download' mode,
to flash a new recovery, etc... and try again.