Develop Bugs

[q] Strange reboot and bootloops

Hi everyone!
A friend of mine tried to flash/destroy his n7100 (i don't know why!) so He gave it to me to "play" and try to recover it.
I think that He tried to flash a 4.4.2 stock rom taken somewhere, so I have the lastest bootloader
I recovered it with KIES (that installed android 4.3) and the phone (now) boot completely and works at 100%!
BUT
sometimes when I detach it from power cord it immediatelly reboot and remain stuck at the "samsung galaxy note n7100" screen and bootloops.
If I reattach the power cord at the next poweroff/poweron cycle the phone start correctly and works 100%!!
Actually I'm on a full stock with root and TWRP installed, but this reboots happens also on full stock
It's really strange and I don't know how to get rid of this!
Actually the custom flash counter report 9 and the knox warranty void is at 1.
Someone has any idea of to get rid of theese strange reboots?

aleritty said:
Hi everyone!
A friend of mine tried to flash/destroy his n7100 (i don't know why!) so He gave it to me to "play" and try to recover it.
I think that He tried to flash a 4.4.2 stock rom taken somewhere, so I have the lastest bootloader
I recovered it with KIES (that installed android 4.3) and the phone (now) boot completely and works at 100%!
BUT
sometimes when I detach it from power cord it immediatelly reboot and remain stuck at the "samsung galaxy note n7100" screen and bootloops.
If I reattach the power cord at the next poweroff/poweron cycle the phone start correctly and works 100%!!
Actually I'm on a full stock with root and TWRP installed, but this reboots happens also on full stock
It's really strange and I don't know how to get rid of this!
Actually the custom flash counter report 9 and the knox warranty void is at 1.
Someone has any idea of to get rid of theese strange reboots?
Click to expand...
Click to collapse
Reinstall correct bootloader for rrom using Odin.

Mufrad said:
Reinstall correct bootloader for rrom using Odin.
Click to expand...
Click to collapse
The actual bootloader is installed by kies... So which bootloader I have to install?
The only one that odin let me flash without problem is the one with 4.4.2 android from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
every other bootloader I tried give me a flash error and the screen show "incompatible version".
This will solve also the reboot part?

aleritty said:
The actual bootloader is installed by kies... So which bootloader I have to install?
The only one that odin let me flash without problem is the one with 4.4.2 android from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
every other bootloader I tried give me a flash error and the screen show "incompatible version".
This will solve also the reboot part?
Click to expand...
Click to collapse
Flash the bootloader then flash 4.4.2 rom, you can try this rom
forum.xda-developers.com/showthread.php?t=2672758
Should stop the sudden reboots.

Mufrad said:
Flash the bootloader then flash 4.4.2 rom, you can try this rom
forum.xda-developers.com/showthread.php?t=2672758
Should stop the sudden reboots.
Click to expand...
Click to collapse
Hello,
I have the same issues but I fear in my case these are early symptoms of a EEMC brick bug :crying:
I am on TWRP with Omega v24 and latest bootloader (i know because I have wifi, otherwise I would't have)
I got inconsistencies in the file system and today I had a UID mismatch message error at boot
I would like to format all the partitions (data/system/ecc) and flash a Rom via Odin just be sure...
Why are you sure that this rom should avoid reboot errors? Is there anyway to install this ROM or any other ROM via Odin so I can format all the partitions just to be sure?
Thanks!

Mufrad said:
Flash the bootloader then flash 4.4.2 rom, you can try this rom
forum.xda-developers.com/showthread.php?t=2672758
Should stop the sudden reboots.
Click to expand...
Click to collapse
Which bootloader? the latest from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
because I actually have it...
Is there anyway to install this ROM or any other ROM via Odin so I can format all the partitions just to be sure?
Click to expand...
Click to collapse
You can flash with odin and repartition with your pit (or another from xda but be careful with that) your same stock and then flash the indicated rom so you have a clean installation

aleritty said:
Which bootloader? the latest from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
because I actually have it...
You can flash with odin and repartition with your pit (or another from xda but be careful with that) your same stock and then flash the indicated rom so you have a clean installation
Click to expand...
Click to collapse
Sure go ahead and flash that bootloader.
SergioBigred said:
Hello,
I have the same issues but I fear in my case these are early symptoms of a EEMC brick bug :crying:
I am on TWRP with Omega v24 and latest bootloader (i know because I have wifi, otherwise I would't have)
I got inconsistencies in the file system and today I had a UID mismatch message error at boot
I would like to format all the partitions (data/system/ecc) and flash a Rom via Odin just be sure...
Why are you sure that this rom should avoid reboot errors? Is there anyway to install this ROM or any other ROM via Odin so I can format all the partitions just to be sure?
Thanks!
Click to expand...
Click to collapse
Do you have cwm? Then you can full wipe, then again you can format each partition separately, then go to android development thread, rom repository and download and flash stock rom, I suggested that specific rom because without the air command mod it's almost stock, without the Damned Knox.

Mufrad said:
Sure go ahead and flash that bootloader.
Click to expand...
Click to collapse
Ok thanks! I'll let you know how does it work!

Mufrad said:
Sure go ahead and flash that bootloader.
Do you have cwm? Then you can full wipe, then again you can format each partition separately, then go to android development thread, rom repository and download and flash stock rom, I suggested that specific rom because without the air command mod it's almost stock, without the Damned Knox.
Click to expand...
Click to collapse
I have TWRP, so I will do that from there.
Which STock rom do you suggest? I am on 4.3.2, I should use this?
http://forum.xda-developers.com/showthread.php?t=2536423
It seems it has Know anyway...
Should I use a pit file to repartition it?
Thanks!

aleritty said:
Ok thanks! I'll let you know how does it work!
Click to expand...
Click to collapse
Ok, I flashed bootloader (only sboot) from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
then flashed
n7100xxufnb4_unsecure.zip
from TWRP (and wiped everything before flashing of course)
The situation is the same of before, but the phone now doesnt boot completely, just remains at "samsung" logo.
Any idea?

aleritty said:
Ok, I flashed bootloader (only sboot) from
N7100XXUEMK9_N7100ITVEMK2_N7100XXUEMJ9
then flashed
n7100xxufnb4_unsecure.zip
from TWRP (and wiped everything before flashing of course)
The situation is the same of before, but the phone now doesnt boot completely, just remains at "samsung" logo.
Any idea?
Click to expand...
Click to collapse
Flash this bootloader www.mediafire.com/download/b59xde333z6q8pv/BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5

Mufrad said:
Flash this bootloader www.mediafire.com/download/b59xde333z6q8pv/BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5
Click to expand...
Click to collapse
Yes Sir! Flashing!

aleritty said:
Yes Sir! Flashing!
Click to expand...
Click to collapse
Flashed this bootloader, heimdall give me:
Code:
Uploading BOOTLOADER
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOTLOADER upload failed!
Ending session...
and on the phone in red appear: unsupported version.
When I reboot appear
"Firmware upgrade encountered an issue. Please select recovery mode in kies & try again.

i have the same issue my note 2 restarting rapidly after a vibrate in samsung logo and successfully start up only when charger is connected. it happen after i install 4.4.2 leaked and revert to 4.3

Bootloop on grey battery icon, doesnt power off and unable to flash custom roms

So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.

Tan9890 said:
So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.
Click to expand...
Click to collapse
Knox trigger can't be reversed.
Of course, it is a bootloader issue. Follow the procedure and it should work out well for you.
1. Use stock recovery to wipe cache and factory reset.
2. Don't use cf-auto root.
3. Download Philz recovery latest version and supersu zip file. (For Note 2 )
4. Flash Philz. Uncheck auto reboot option in ODIN. Once you get pass message, unplug. Don't start your phone yet. Boot directly into recovery.
5. Install supersu zip file
6. Reboot to check if you are rooted.
7. DN3 5.5 has given me a headache. But it must be something ---- looking at the number of people using it.
8. I prefer Dr. Ketan's V12 Touchwiz ROM.
With Aroma installer, it is almost impossible to go wrong. Support is amazing. Doc himself answers all queries as fast as he can. But choice is yours.
Press thumps up if you found this suggestion helpful.
Link to all the files: http://www.ibtimes.co.uk/root-galax...d-4-4-2-kitkat-install-philz-recovery-1447891
Sent from my GT-N7100 using Tapatalk

Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'

Tan9890 said:
Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'
Click to expand...
Click to collapse
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk

ceomaverick said:
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?

Tan9890 said:
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?
Click to expand...
Click to collapse
Very weird. Never heard of such a thing. Btw, which recovery you are using? TWRP or CWM. Also, chk if the version is latest. The latest versions are fixed for these very issues.
Probably, flashing N7100XXUFNI1 out of the box should solve your problem.
Beyond that I don't have answers.
Sent from my GT-N7100 using Tapatalk

Snippet taken from: http://mark.candleshoreblog.com/2013/06/13/tip-steps-to-prevent-clockwork-or-any-custom-recovery-from-being-overwritten-by-factory-stock-roms-at-android-system-reboot/:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run. All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again. Do the following:
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.
That’s all there is to it.

SGH-i317M TWRP Issues (unable to boot into OS, Loops Recovery)

Soo.. I decided to install Cynogen Mod 5.1.1 onto the Note 2. And, All worked fine....
But here is an issue. A while back I had to unlock the phone, which required me to install TWRP.. Now the issue is i think i installed it into the Boot instead of recovery.. So now whenever i select ANY power option in TWRP, the phone restarts into TWRP again.. Now, All i had to do was just do a battery pull and all was good.. Except for now..
I tried to update CM through TWRP, but it did something and now the phone boots into TWRP no matter what. I got the Android universal toolkit or whatever running and trying to fix the boot.img, But have been unsuccessful so far..
So, Any help that i can get would be appreciated.
Things I have done:
1. Reflashed boot.img with original.
2. Reflashed recovery with newer twrp
3. Factory reset, formated/
4. Installed backup with 4.4.2 installed still
5. Googled everything
Click to expand...
Click to collapse
AFTER 5 HOURS OF WORK I FIXED IT!
I reinstalled the Original recovery. Then rebooted, and it all worked.. 1:02 AM and tired as heck....

Can you tell me how you installed the original recovery? I did the same thing and now all my phone boots into is TWRP.

Alright.. It's a bit of a Google.. But you gotta find the original recovery for the phone on the web.. The recovery for the gt-n100 or whatever works. So look for that.

J.Naw said:
Alright.. It's a bit of a Google.. But you gotta find the original recovery for the phone on the web.. The recovery for the gt-n100 or whatever works. So look for that.
Click to expand...
Click to collapse
Okay thanks! I managed to find the one for my phone

Boot Stuck at Tmbile Logo

I need help get past the Tmobile logo at boot.
SM-N900T
Android 4.4.2
N900TUVUENK3
Performed CF-Auto-Root 2.5 years ago. Ran like a champ until last week when phone got boot stuck on white T-mobile logo.
will not start in Safe Mode - press power till Galaxy Note 3 logo shows up, then vol down. does not start in safe mode
Put in Recovery (power, home, vol up), wiped cache, reboot . still boot stuck at T mobile logo
Put in download mode (power, home, vol down), Re-flashed with Odin3-v3.07.exe CF latest SM-N900T (T-Mobile US): CF-Auto-Root-hltetmo-hltetmo-smn900t.zip , extracted to .tar.md5, still boot stuck
Put in Recovery (power, home, vol up), wipe data/factory reset, then reboot. got past Tmobile white boot screen.
Must keep phone on and not reboot otherwise , I will need to wipe data/factory reset each time to boot and get past Tmobile logo
JJEgan said:
Dont know why you are blaming ROOT .
Suggest you ask in your models forum .
I would wipe phone install stock rom and use SuperSu zip as root after flashing custom recovery .
Click to expand...
Click to collapse
The Latest CF-AUTO-ROOT flashed with Odin installed latest SuperSu v2.82 and has stock recovery with stock rom.
Why is phone stuck at boot? Why install custom recovery, I did not need it before? And if so, Which one? Why would SuperSu zip be needed if latest version is already installed?

My TMo Note3 did the exact same thing last week. (I was still on v4.4.2.) After fiddling with it a little bit, I decided to try a factory-reset. That worked, and then after signing into google, all my apps started to re-download and install. Once that completed, I rebooted and again got stuck at the white TMo screen. Eventually I just bit the bullet and flash-updated it to v5. I disabled auto-installing my apps, and carefully installed just the apps I really wanted, rebooting after a few at a time just to see if I could catch whatever was causing it. But after getting all my apps installed, it's working fine now with no reboot issues.
My personal guess (no direct evidence) is that one of the apps was breaking the bootup somehow.

Looks like I am not the only one having this problem. I don't think this would have suddenly happen. I think there must of have been something with a Samsung update that caused the boot to stick at the Tmobile logo. I am thinking I am just going to have to update from 4.4.2 to 5 and trip my knox. Unless someone else has any other ideas.

Thanks for replying. So you upgraded from 4.4.2 to 5.0. How? What does it matter if you trip Knox if phone is already rooted?

I think cfautoroot will always trip the Knox indicator if the phone is running a 4.3 or newer bootloader.
Tried flashing supersu from twrp to get root?

2Code said:
Thanks for replying. So you upgraded from 4.4.2 to 5.0. How? What does it matter if you trip Knox if phone is already rooted?
Click to expand...
Click to collapse
any ideas here?

2Code said:
any ideas here?
Click to expand...
Click to collapse
I used Samsung's Smart Switch PC. One of the "features" is that it will detect the older Android OS on your phone and offer to install the latest - albeit at the cost of a total wipe and re-flash. (Hence why it recommends you use the app to first back up your phone.) I my case, I had nothing to lose since I couldn't get out of the boot-up screen, and I had already done a factory-reset.
I don't know how this will affect the Knox flag. I never tripped that flag, so I can't say if this will reset it or not.

software_samurai said:
I used Samsung's Smart Switch PC. One of the "features" is that it will detect the older Android OS on your phone and offer to install the latest - albeit at the cost of a total wipe and re-flash. (Hence why it recommends you use the app to first back up your phone.) I my case, I had nothing to lose since I couldn't get out of the boot-up screen, and I had already done a factory-reset.
I don't know how this will affect the Knox flag. I never tripped that flag, so I can't say if this will reset it or not.
Click to expand...
Click to collapse
Thanks software_samurai.
so download the pc version, connect phone, and it will wipe and install Android 5.0
Phone was rooted with CF-autoroot , will phone stay rooted after android upgrade from 4.4 2 to 5.0 ? Or will I need to redo CF-autoroot?
Earlier post indicated that autpupdate of apps may be interfering with boot and is cause of boot stuck at Tmobike logo. Post suggests to install apps one at a time and disable autoupdate of apps. Has one app been identified as suspect app? What other steps should I take to prevent recurrance?
TWRP recovery. Do I need to install it to prevent boot stuck issue? How does it help prevent recurrance of boot stuck issue?

2Code said:
so download the pc version, connect phone, and it will wipe and install Android 5.0
Click to expand...
Click to collapse
yes. it will offer the "upgrade" and if you accept, it will wipe and re-flash with the stock OS.
2Code said:
Phone was rooted with CF-autoroot , will phone stay rooted after android upgrade from 4.4 2 to 5.0 ? Or will I need to redo CF-autoroot?
Click to expand...
Click to collapse
this will wipe the phone and install the stock OS, so no, it will not stay rooted after this.
2Code said:
Earlier post indicated that autpupdate of apps may be interfering with boot and is cause of boot stuck at Tmobike logo. Post suggests to install apps one at a time and disable autoupdate of apps. Has one app been identified as suspect app? What other steps should I take to prevent recurrance?
Click to expand...
Click to collapse
that was my attempt at recovering from a factory reset on 4.4.2. my guess was that one of the apps caused the boot-problem, but I can't be sure.
2Code said:
TWRP recovery. Do I need to install it to prevent boot stuck issue?
Click to expand...
Click to collapse
wiping the phone and re-flashing to stock OS is what I did to avoid the boot-problem. I've got no idea about using TWRP since I've never used it.
2Code said:
How does it help prevent recurrance of boot stuck issue?
Click to expand...
Click to collapse
again, wiping and re-flashing to stock OS should totally clear out any software-related problem.
if your phone has some hardware issue, you're out of luck.

software_samurai said:
this will wipe the phone and install the stock OS, so no, it will not stay rooted after this.
Click to expand...
Click to collapse
Many Thanks for replying.
have you rooted with CF-autoroot after using samsung smarts witch pic to install Android 5.0 and stock rom ? How did it go?

2Code said:
have you rooted with CF-autoroot after using samsung smarts witch pic to install Android 5.0 and stock rom ? How did it go?
Click to expand...
Click to collapse
nope. so far I haven't needed root. Android 5.0 has a (rather clunky) way to handle giving specific apps write access to the sdcard, thus eliminating the only reason I would need root.

Curious, Is installing Android 5.0 using Samsung switch PC same as flashing sambile latest SM-900T firmware https://www.sammobile.com/firmwares/galaxy-note3/SM-N900T/TMB/download/N900TUVSFPL1/120222/ ?

2Code said:
Curious, Is installing Android 5.0 using Samsung switch PC same as flashing sambile latest SM-900T firmware https://www.sammobile.com/firmwares/galaxy-note3/SM-N900T/TMB/download/N900TUVSFPL1/120222/ ?
Click to expand...
Click to collapse
Downloaded latest SM-N900T Android 5.0.1 stock Ron & Kernel and flashed with Odin v3.12. Did not wipe out personal data but lost root.
This,took care of the boot stuck at T-Mobile logo
Re-flashed CF-AUTO root to restore root access.
Hope these steps help somebody.

rooted galaxy s9 exynos stuck in download mode, vol down + Power doesnt work.

Hey
Im new to rooting and yesterday I decided to root my galaxy s9. I used Odin to flash twrp and flash ' Disable_Dm-Verity_ForceEncrypt_03.04.2020 ' and Magisk v20.4. All went well.
Used Magisk hide to bypass banking apps. but I encountered a few social apps like Instagram that kept on crashing. So I searched up what the problem could be and came to an article where it said the TWRP app may cause interference and delete it and wipe cache partition from recovery mode.
I didn't delete the TWRP app yet and decided to boot into recovery via magisk. But then my phone booted into download mode. that's where the issue started.
Its the downloading do not turn off target screen but strangely enough doesn't have the small system writings the top left side of the screen. All it says is Vol down + Power to cancel but when I do that,my phone boot into this download mode again. I panicked and flashed twrp, Disable_Dm-Verity_ForceEncrypt_03.04.2020, and magisk again and I did get into the Teamwin recovery. formatted and installed all the necessary things. But when I reboot from there it rebooted to download mode again. As of now its still in download mode and im waiting for the battery to run out and the turn on my phone normally. Please help

Have you try to flash the stock firmware? The latest one would be nice

B1nz said:
Have you try to flash the stock firmware? The latest one would be nice
Click to expand...
Click to collapse
I will try that and let you know soon

b1nz said:
have you try to flash the stock firmware? The latest one would be nice
Click to expand...
Click to collapse
thank you so much mannn it worked!

HaadiM2000 said:
thank you so much mannn it worked!
Click to expand...
Click to collapse
glad to hear that

Hello
I have Samsung Galaxy S9 exynos. I rooted it and flash android 12 beta GSI and it booted fine. I however could not boot TWRP as the phone is stack up at TWRP recovery animation. It is not even allowing me to boot download mode to go back to stock.
I really need help