Database Develop

Stuck on Samsung logo bootscreen after flashing TWRP through Odin (N920CD)

I have SM-N920CD variant and on stock Android M 6.0.1, Region:THR CSC:N920COJV2BPBA
I tried to flash TWRP through Odin in order to root and flash SkyHigh kernel but got stuck on Samsung logo bootscreen after flashing, I re-flashed my stock firmware to revive my phone and got it back working. I tried two different versions of Odin "Odin3 v3.10.7 and Odin3_v3.10.6" but still same results, I also used different PCs and downloaded TWRP twice.
Am I doing anything wrong or it is just me?

Did you try booting back to recovery and cleaning cache and rebooting. Sounds a little too basic I know but it has worked for me often enough. Just a thought.
Sent from my SM-N920G using Tapatalk

MSAKK said:
I have SM-N920CD variant and on stock Android M 6.0.1, Region:THR CSC:N920COJV2BPBA
I tried to flash TWRP through Odin in order to root and flash SkyHigh kernel but got stuck on Samsung logo bootscreen after flashing, I re-flashed my stock firmware to revive my phone and got it back working. I tried two different versions of Odin "Odin3 v3.10.7 and Odin3_v3.10.6" but still same results, I also used different PCs and downloaded TWRP twice.
Am I doing anything wrong or it is just me?
Click to expand...
Click to collapse
Try flashing again - this time ensure keep system as "read-only" option when you first flash TWRP. Then in TWRP recovery mode (straight after flashing & before rebooting), ensure that "system" is ticked/selected in the "Mount" option in TWRP menu - now reboot to system (you will need to tick/select "system" in Mount option each time if you boot into TWRP recovery mode).

swarup.siddharth said:
Did you try booting back to recovery and cleaning cache and rebooting. Sounds a little too basic I know but it has worked for me often enough. Just a thought.
Sent from my SM-N920G using Tapatalk
Click to expand...
Click to collapse
I can't even get to recovery, I can either get to download mode or stuck on bootscreen. I think it is the recovery getting messed up.

elmor0 said:
Try flashing again - this time ensure keep system as "read-only" option when you first flash TWRP. Then in TWRP recovery mode (straight after flashing & before rebooting), ensure that "system" is ticked/selected in the "Mount" option in TWRP menu - now reboot to system (you will need to tick/select "system" in Mount option each time if you boot into TWRP recovery mode).
Click to expand...
Click to collapse
I tried to enter recovery before rebooting and after flashing but with no luck. I assume to use the typical method (power+up+home). Am I missing something?

MSAKK said:
I tried to enter recovery before rebooting and after flashing but with no luck. I assume to use the typical method (power+up+home). Am I missing something?
Click to expand...
Click to collapse
Start all over again by re-flashing back to stock ROM/stock recovery and try again via Odin to flash TWRP - Make sure to go into recovery (TWRP) mode away straight away by 'power+vol up+home' buttons rather than booting into system.
Then mount system on in TWRP before rebooting to system - This worked for me, no probs since.
Also, ensure you have the correct TWRP .tar for your model (and ??maybe try an older Odin version for flashing TWRP).

Flash this TWRP through Odin:
https://dl.twrp.me/noblelte/twrp-3.0.0-0-nobleltezt-nobleltezt.img.tar.html

elmor0 said:
Start all over again by re-flashing back to stock ROM/stock recovery and try again via Odin to flash TWRP - Make sure to go into recovery (TWRP) mode away straight away by 'power+vol up+home' buttons rather than booting into system.
Then mount system on in TWRP before rebooting to system - This worked for me, no probs since.
Also, ensure you have the correct TWRP .tar for your model (and ??maybe try an older Odin version for flashing TWRP).
Click to expand...
Click to collapse
I tried that but nothing happened, it kept me on download mode otherwise system is booting.
Is it possible to enter recovery directly from download mode without power off?
Battlehero said:
Flash this TWRP through Odin:
https://dl.twrp.me/noblelte/twrp-3.0.0-0-nobleltezt-nobleltezt.img.tar.html
Click to expand...
Click to collapse
That is the download link I have been using.
Sent from my SM-N920C using XDA Free mobile app

I don't think you can go from download mode directly to TWRP recovery mode without power off.......... Try re-booting from download mode but before it re-starts quickly hold 'power+vol up+home'.
Have you tried starting from scratch i.e back to stock recovery, and tried flashing with an older version of Odin?

elmor0 said:
I don't think you can go from download mode directly to TWRP recovery mode without power off.......... Try re-booting from download mode but before it re-starts quickly hold 'power+vol up+home'.
Have you tried starting from scratch i.e back to stock recovery, and tried flashing with an older version of Odin?
Click to expand...
Click to collapse
I tried from scratch but with same results. Could it be ROM related?

elmor0 said:
Start all over again by re-flashing back to stock ROM/stock recovery and try again via Odin to flash TWRP - Make sure to go into recovery (TWRP) mode away straight away by 'power+vol up+home' buttons rather than booting into system.
Then mount system on in TWRP before rebooting to system - This worked for me, no probs since.
Also, ensure you have the correct TWRP .tar for your model (and ??maybe try an older Odin version for flashing TWRP).
Click to expand...
Click to collapse
i have tried that, and got an issues related to mount the storage as well, but able to overcome all that
and now the phone went from stuck on "Samsung" logo, into a loopboot
all this with the Samsung Stock ROM
but at the moment i install Lineage ROM, it works immediately
tried my best to make it work with samsung stock rom, but i couldn't

Maybe I bricked my A2

Hi, after the installation of official TWRP my phone was stuck into the loading bar. I tried recover it following a guide but now when I turn it on it asks to perform a factory reset, maybe I didn't use the right rom version, I don't know. I think that this issue is fixable but I don'w know how. I can go into fastboot and recovery. I also unlocked the phone. Please help me, thanks.

On what version of ROM were you?
Download stock ROM of your version, extract boot.img from images folder, and flash boot.img via fastboot.

Did you flash twrp to the active partition? to the inactive partition? Do you know?
If you can get to fastboot, it's not bricked. I'd suggest, as you indicate you have the option to reset to factory, go ahead and do that. Trying to fix it when yer not sure what you've done so far, **may** end up with it actually being bricked.

T719 UK

Hello. I have a Samsung tab S2 T719 that is perma stuck in bootloop. Originally the recovery mode was working but i probally messed that up aswel by flashing some TWRP custom recovery.. it now bootloops even when i turn it on in recovery mode. I am not sure if the tablet has USB debugging on.. also, I just tried to flash another stock nougat firmware on to it via odin and it passed but when i turn it on it has the same bootloop issue. Is there anything i can do to it ? the tablet is in brilliant condition physically and it would be a shame to sell it for parts or bin it >_< Regards

You need the correct recovery mode before ROM. After flashing TWRP, go to TWRP, backup EFS, format data, then flash ROM. Don't boot after flashing TWRP, just go directly from download mode to recovery mode

sarjarim said:
You need the correct recovery mode before ROM. After flashing TWRP, go to TWRP, backup EFS, format data, then flash ROM. Don't boot after flashing TWRP, just go directly from download mode to recovery mode
Click to expand...
Click to collapse
I flashed a working TWRP now and thats all dandy and it works and then i followed ur steps and after i flashed the rom i tried to turn it on and it continues the endless bootloop after it says ''installing applications''... it did exactly the same with all roms i tried.

Could u try another ROM, if it's still bootloop then maybe hardware problem.

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

Recovery Bootloop

So I successfully unlocked my bootloader and flashed custom ROM and recovery, first boot it was okay, I was able to setup Android and installed apps, now when I rebooted it, it only boots to recovery. Phone can still be detected by my PC, can also get detected in fastboot when in bootloader. So I think there's really a workaround for this I just didn't know how and I am now hesitant to follow web tutorials if it isn't an official forum just like this.
Things I already did:
Reinstall ROM
Reflashed custom recovery
Cleared Data/Dalvik/Cache
Factory Reset

Flash the stock firmware by SP Flash Tool, it'll help to revert back to stock and stop boot loop!