Database Users

Stock on Samsung Logo with Custom Lock Image

I had Mint Jelly2.1 installed and everything was working fine.
it started when I had used the APK Hide It Pro. I was in the process of hiding videos and I noticed that my phone got rebooted and got stock in the Samsung boot up image with the Custom Lock image.
I tried nandroid restore, 2 images, but both also failed to restore / bootup.
I tried re-installing ROM and it was successful but during reboot, it will still get stock on the boot image.
Last step.
I used ODIN to restore the stock ROM and ODIN was able to install and reset. And my phone rebooted but still got stock on the Samsung Logo with CUstom Lock Screen.
What else can I do to fix this?
Thank you.

Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.

scott14719 said:
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
Click to expand...
Click to collapse
I had tried to restore/flash from recovery before ODIN and it all Failed.
Anyway, the last step ODIN restore and it was still stock at the Samsung Logo with Lock image.
I left the phone to charge the whole night and this morning when I turned it on, it was able to start properly with ODIN stock ROM.
I tried to go to recovery, and can only be done manually, and it was not the TWRP recovery but the stock one, with very small characters.
I tried to install Mint Jell2.1 right away but just reboots.
I realized that I might need to root it again and downloaded the Tool and re-loki'ed/rooted and installed TWRP.
Now, I am able to install Mint Jelly 2.1 and restoring all my apps.
I appreciate the comment.
Thank you.

scott14719 said:
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
Click to expand...
Click to collapse
Yeah, every single time I ODIN back to stock, I get stuck at the splash screen also. And rebooting to 3E (factory) recovery and "restore factory defaults" works great.

CZ Eddie said:
Yeah, every single time I ODIN back to stock, I get stuck at the splash screen also. And rebooting to 3E (factory) recovery and "restore factory defaults" works great.
Click to expand...
Click to collapse
I can confirm this works happened to me yesterday.

leoj85 said:
I can confirm this works happened to me yesterday.
Click to expand...
Click to collapse
I am running out of options. I thought I am already out of this stuck on Samsung Logo with Custom Lock icon.
I had ODIN to stock I337UCUAMDL and reset, Ran Loki patch / installed TWRP, intermittently it will get stuck.
I flashed Shoshock 1.9, was able to reboot and setup basic settings.
I manually reboot to check if it was able to fix the problem, but no.
I am stuck again and don't know what is the next step for trouble shooting it.
any advise will be appreciated.
Thank you.

I got stuck to 1st boot image of Samsung with Lock Custom Icon.
I did format data/factory reset/clear cache/dalvik.. all of the wipe ootions.
I flashed a new ROM, successful, rebooted pass the logo and booted fine. I did not change any settings yet and I rebooted to check if it will get stuck again and sure after reboot, it got stuck again on the 1st image that shows up : Samsung Logo with the Lock Custom Icon.
qwer43 said:
I am running out of options. I thought I am already out of this stuck on Samsung Logo with Custom Lock icon.
I had ODIN to stock I337UCUAMDL and reset, Ran Loki patch / installed TWRP, intermittently it will get stuck.
I flashed Shoshock 1.9, was able to reboot and setup basic settings.
I manually reboot to check if it was able to fix the problem, but no.
I am stuck again and don't know what is the next step for trouble shooting it.
any advise will be appreciated.
Thank you.
Click to expand...
Click to collapse

IMPORTANTwhen using*twrp*recoverydo not choose "format data"(that option will ask you to type "yes")what if i did?rom will not boot past "padlock" boot screen orrom will not boot on second reboot*help!! I did, I did*1. sigh2. d/l odin3. d/l odin stock restore MDL4. let it do its thang5. after its complete it will be stuck at padlock6. should have "rtfm" huh?*7. pull battery8. hold home button, vol-up, power at same time9. when phone vibrates, release power, while still holdingvol-up, and home button10. you will now be in "stock recovery"11. wipe factory reset then wipe cache12. reboot*13. swear you will never "ignore instructions"

TWRP wont install

I flash twrp-3.0.0-0-hero2lte.img.tar using ODIN..than phone reboots automatically than i turn off and boot in recovery. It tries to install than displays android logo and a yellow triangle (fail) and stock recovery loads..i think when phone boots automatically replaces twrp - just a guess. What can it be and how to fix it?

FIXED: didnt allow phone to reboot. Directly booted to recovery as soon as it was flashed
P.S.: Now whatever i try to do in twrp (backup,install) it gives me errors

i had the same issue format data in twrp.and you will be able to backup and restore

I am new to this and want twrp on my AT&T S7 Edge could you please send me a tar file or something that i can do..... i really want twrp recovery.

harleyusa59 said:
I am new to this and want twrp on my AT&T S7 Edge could you please send me a tar file or something that i can do..... i really want twrp recovery.
Click to expand...
Click to collapse
Lolz. American phones can't
Sent from my Blackberry Bold

Samsung Note 3 N9005 - ODIN TWRP but still boots into stock recovery

I downloaded odined TWRP to my Samsung Note 3 N9005, but the phone still doesn't boots into custom recovery.It goes to stock recovery. I have attached the TWRP odin log for reference. I have flashed roms and rooted phones earlier, but with Note 3 this is my first attempt.

Flash again but don't check auto reboot. When you see the word reset in the status window, remove USB cable from the phone, remove battery, wait about 5 seconds, replace battery, boot to recovery using the buttons.

audit13 said:
Flash again but don't check auto reboot. When you see the word reset in the status window, remove USB cable from the phone, remove battery, wait about 5 seconds, replace battery, boot to recovery using the buttons.
Click to expand...
Click to collapse
I did that. But it says cannot boot into recovery mode and goes to download mode. So I did it auto reboot checked again and now it's normal, but didn't solve the issue. By reset in the status do you mean I pull off the USB as soon as it says "RES OK!"? and not wait for Completed?

Try a newer version of Odin. Wait for it to complete the flash.
Sure you have the right twrp file?
https://dl.twrp.me/hlte/

audit13 said:
Try a newer version of Odin. Wait for it to complete the flash.
Sure you have the right twrp file?
https://dl.twrp.me/hlte/
Click to expand...
Click to collapse
I tried a cwm recovery instead worked for me. Can now boot into the custom recovery. I installed Dark Lord Room, stuck at Samsung for more than 2 mins. Should I wait or is this a boot loop?
Update: I wiped dalvik cache, cache partition and factory storagr and then tried Phronesis with a Full Wipe in Aroma, still stuck at SAMSUNG Logo for more than 5 mins.

pavitar said:
I tried a cwm recovery instead worked for me. Can now boot into the custom recovery. I installed Dark Lord Room, stuck at Samsung for more than 2 mins. Should I wait or is this a boot loop?
Update: I wiped dalvik cache, cache partition and factory storagr and then tried Phronesis with a Full Wipe in Aroma, still stuck at SAMSUNG Logo for more than 5 mins.
Click to expand...
Click to collapse
After the wait it worked and booted the Phronesis. So my solution was to odin the CWM.
Best Regards!

I don't recommend cwm as it is hasn't been updated for years.

Help PLEASE - Phone Won't Boot, Ive Tried EVERYTHING

My N910G that wont boot!
If I flash the latest TWRP I can access recovery mode and flash any ZIP however when the phone reboots after the installation of the new ROM, it always eventually gets suck on the NOTE 4 Logo after booting onto the Samsung Logo. I can access the the partitions in TWRP when I go to individually wipe them. I've noticed sometimes the phone doesn't remember when tick the checkbox for "dont show this message again" the first time you've booted into TRWP.
Things I've tried:
Full restore using the latest N910G firmware. (XSA-N910GDTS1DPH1-20160728112745)
Using the PIT file for a N910G and restoring the full original firmware
Clicking "NAND Erase All" in Odin and using the PIT file for a N910G and restoring the full original firmware.
Every time I do anyone of the above options the phone reboots then goes into stock recovery where it works for a little bit then restart and eventually gets stuck on the Samsung logo or reboots and gets stuck on the Note 4 Logo.
Any help would be MUCH MUCH appreciated, if anyone can help me get the phone working again I will gladly buy them one month to samsung-firmware.org or pay them the equivalent into palpay.

SudoBen said:
My N910G that wont boot!
If I flash the latest TWRP I can access recovery mode and flash any ZIP however when the phone reboots after the installation of the new ROM, it always eventually gets suck on the NOTE 4 Logo after booting onto the Samsung Logo. I can access the the partitions in TWRP when I go to individually wipe them. I've noticed sometimes the phone doesn't remember when tick the checkbox for "dont show this message again" the first time you've booted into TRWP.
Things I've tried:
Full restore using the latest N910G firmware. (XSA-N910GDTS1DPH1-20160728112745)
Using the PIT file for a N910G and restoring the full original firmware
Clicking "NAND Erase All" in Odin and using the PIT file for a N910G and restoring the full original firmware.
Every time I do anyone of the above options the phone reboots then goes into stock recovery where it works for a little bit then restart and eventually gets stuck on the Samsung logo or reboots and gets stuck on the Note 4 Logo.
Any help would be MUCH MUCH appreciated, if anyone can help me get the phone working again I will gladly buy them one month to samsung-firmware.org or pay them the equivalent into palpay.
Click to expand...
Click to collapse
This information has something to do? Can it help you?
http://forum.xda-developers.com/note-4/general/emmc-bug-fix-tried-sm-n910g-sm-n910p-sm-t3468721

After installing a new Rom, remove and put back battery. Then go to Recovery and do Wipe data/factory reset and Wipe cache. Reboot and wait, it will take a few minutes before rebooting.
This will erase though all your previous data from your old Rom.

ruicc said:
This information has something to do? Can it help you?
http://forum.xda-developers.com/note-4/general/emmc-bug-fix-tried-sm-n910g-sm-n910p-sm-t3468721
Click to expand...
Click to collapse
Thanks for your help I tired it on two different versions of Odin and every time it fails (from all my flashing on this phone this is the only time I've seen it fail). So we might be on the right track or the phone is beyond software repair

GrippingSphere said:
After installing a new Rom, remove and put back battery. Then go to Recovery and do Wipe data/factory reset and Wipe cache. Reboot and wait, it will take a few minutes before rebooting.
This will erase though all your previous data from your old Rom.
Click to expand...
Click to collapse
I've tried doing that

HELP! Phone stuck in boot cycle, cannot flash rom

Hi everyone! Surfed the forums in the past for some minor help but never needed to register till now. I've tried everything and can't get my phone to boot.
So last night while camping my phone started boot cycling out of nowhere. I let it try a few times and then removed the battery and went to sleep. This morning I woke up and tried a few more times, replaced the battery with a non-stock double-capacity one I have, and still cycled. Sometimes it restarts on the Galaxy Note 4 logo, and sometimes on the Sprint logo. It will do this indefinitely. At one point It finally booted and said it was updating apps (like from an Android update, not the regular app updates.) Before I could do anything else with it though, the battery wiggled loose and it started power cycling again. Because of this one boot I think the root cause is related to an Android update that decided to run without my permission.
So I gave up and drove hoe from camping. Tonight I had tried everything I could find from factory reset to the toolkit to Odin and nothing has had any effect. The toolkit didn't see the device, and Odin failed to flash. Can anyone help me? I can boot to recovery and I can get into download mode, but nothing seems to work. The phone isn't hard bricked, but everything I can find on soft brick solutions hasn't worked. Thanks in advance!
~Evan

Oh also, when I boot into recovery mode it says "installing system update" with the android open chest logo, and then goes to a dead android and says "no command" before getting into the recovery mode menu.

ekuest said:
Oh also, when I boot into recovery mode it says "installing system update" with the android open chest logo, and then goes to a dead android and says "no command" before getting into the recovery mode menu.
Click to expand...
Click to collapse
If you able to go download mode then flash twrp recovery in odin and go to twrp recovery for your specific model and do clean wipe system then flash any rom for your model.then wait 10 to 15 minuts until phone boot.

Trex888 said:
If you able to go download mode then flash twrp recovery in odin and go to twrp recovery for your specific model and do clean wipe system then flash any rom for your model.then wait 10 to 15 minuts until phone boot.
Click to expand...
Click to collapse
Ok thanks that worked! I got into TWRP by setting Odin to not reboot. If I let it reboot then it just restarted after the TWRP flash and kept power cycling like before. If I uncheck auto reboot in Odin then after the flash I can pull the battery (can't figure out any other way to turn the phone off) and then when I restart in recovery mode it goes into TWRP. From there I tried a factory reset (wipe data, cache, and dalvik) and that didnt fix the power cycling. Do I have to flash TWRP and then immediately flash a rom right after? Or should I try an advance wipe in TWR, or maybe "repair or change file system" from the advanced wipe menu?

Bump? I still can't boot my phone. Got into TWRP but no idea what to do from there. I can't flash any rom successfully in Odin and I can't get the phone to boot. Now it just hangs on the "Samsung Galaxy Note 4" splash screen, doesnt even go to the "Samsung" screen or the "Sprint" screen like it used to.

Trex888 said:
If you able to go download mode then flash twrp recovery in odin and go to twrp recovery for your specific model and do clean wipe system then flash any rom for your model.then wait 10 to 15 minuts until phone boot.
Click to expand...
Click to collapse
how do you do the "then flash any rom" part? i have no idea how to do that since Odin doesn't seem to work.

ekuest said:
how do you do the "then flash any rom" part? i have no idea how to do that since Odin doesn't seem to work.
Click to expand...
Click to collapse
1,Flash twrp recovery in odin
2,press volume up+home+power button and boot into twrp
3,in twrp go to wipe/advance wipe and wipe system/cache/data/dalvik cache
4,Flash any custom rom for your model from twrp recovery
If you allready have twrp installed then skip 1 and download any rom like cm12 and gapps
Then flash from twrp

Trex888 said:
1,Flash twrp recovery in odin
2,press volume up+home+power button and boot into twrp
3,in twrp go to wipe/advance wipe and wipe system/cache/data/dalvik cache
4,Flash any custom rom for your model from twrp recovery
If you allready have twrp installed then skip 1 and download any rom like cm12 and gapps
Then flash from twrp
Click to expand...
Click to collapse
Do I just go to install in TWRP and then select the zip file on my microSD card? I tried that with N910PVPU3BOF5_N910PSPT3BOF5_SPR.zip and if says "Could not find 'META-INF/com/google/android/update-binary' in the zip file. Error installing zip file '/external_sd/N910PVPU3BOF5_N910PSPT3BOF5_SPR.zip'" Then I tried with a CM called cm-12.1-20161016-NIGHTLY-trltespr.zip and it seemed to work, and showed a little blue android face but then it still wouldnt boot. Now when I try to start the phone it says "KERNEL IS NOT SEANDROID ENFORCING Set Warranty Bit: Kernel" in tiny text on the top right of the Galaxy Note 4 splash screen, then boots to the blue android face and then powers off after about 2 seconds. After that, I cant even recovery boot the phone until I remove and reinstall the battery. Then the same thing happens, boot to blue android face and then shut down. I'll try some more android zips I found but I think there is a deeper problem with the phone here.

ekuest said:
Do I just go to install in TWRP and then select the zip file on my microSD card? I tried that with N910PVPU3BOF5_N910PSPT3BOF5_SPR.zip and if says "Could not find 'META-INF/com/google/android/update-binary' in the zip file. Error installing zip file '/external_sd/N910PVPU3BOF5_N910PSPT3BOF5_SPR.zip'" Then I tried with a CM called cm-12.1-20161016-NIGHTLY-trltespr.zip and it seemed to work, and showed a little blue android face but then it still wouldnt boot. Now when I try to start the phone it says "KERNEL IS NOT SEANDROID ENFORCING Set Warranty Bit: Kernel" in tiny text on the top right of the Galaxy Note 4 splash screen, then boots to the blue android face and then powers off after about 2 seconds. After that, I cant even recovery boot the phone until I remove and reinstall the battery. Then the same thing happens, boot to blue android face and then shut down. I'll try some more android zips I found but I think there is a deeper problem with the phone here.
Click to expand...
Click to collapse
Which android version you ware running last time before this issues start happning ? 5.1.1 or 6.0.1 ?
And i think you are trying to flash firmware file from twrp thats not possible you will require a custom rom.
If you are on 5.1.1 then try any lojjipop n910p based roms like cm 12
If you are on 6.0.1 then try n910p marshmallow based rom like cm13

Trex888 said:
Which android version you ware running last time before this issues start happning ? 5.1.1 or 6.0.1 ?
And i think you are trying to flash firmware file from twrp thats not possible you will require a custom rom.
If you are on 5.1.1 then try any lojjipop n910p based roms like cm 12
If you are on 6.0.1 then try n910p marshmallow based rom like cm13
Click to expand...
Click to collapse
I always run the updates so I'm pretty sure I was on 6.0.1. I tried again with CM13 with and without GApps and same thing always happens. No matter what I do, the phone always hangs and shuts off when it gets to the CM splash screen. I will upload a video soon. Do you know why the phone says that SEANDROID thing?
I am using CM13 from here: https://www.androidfilehost.com/?w=files&flid=44727
I am using GApps from here: http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico

ekuest said:
I always run the updates so I'm pretty sure I was on 6.0.1. I tried again with CM13 with and without GApps and same thing always happens. No matter what I do, the phone always hangs and shuts off when it gets to the CM splash screen. I will upload a video soon. Do you know why the phone says that SEANDROID thing?
I am using CM13 from here: https://www.androidfilehost.com/?w=files&flid=44727
I am using GApps from here: http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico
Click to expand...
Click to collapse
Seandroid thing is normal if you are running custom rom. Cuz any custom comes with root and custom kernel so nothing to worry.
Did you tried another battery?
And how long did you wait to phone boot after flashing cm13 ?
Go to sprint note 4 xda forum and try different roms and be patient and wait atleast 20min to phone boot
You cannot flash cm13 without gapps and make sure gapps is for 6.0.1 marshmallow.
Once your phone boot normal go to download mode and flash 6.0.1 firmware in odin and after finish flash immediately go to stock recovery and do factory reset your phone will be normal.
Make sure your battery is not damaged maybe it is causing shut off. Issue.

Well since I can't flash CM13 with TWRP and I can't flash a stock rom with Odin, what other options do I have? Is there any way to get a bcakup file that someone else has made on their Note 4 in TWRP and try restoring from that? I've also read about ADB sideloading and another recovery called CWM or something and I don't know if those will be any different or just more failed flashes. I think the problem is deeper in the phone since it wouldn't boot with the stock rom and now it won't boot with CM13.
EDIT: Just saw your last post. I have 2 batteries, one samsung stock and one aftermarket TechOrbits double capacity. The phone does the same thing with either one so I ruled out the battery a while ago. Think there's any chance theyre both bad and I should order a new one? I don't really want to invest more money into a dead phone. I don't think I waited that long after installing CM13. I'll try it again and give it a half hour. I doubt that will change anything though.
EDIT2: Also when I go to download mode (says "ODIN MODE <HIGH SPEED>" at the top) it has some red text at the bottom I think might mean something. Does this mean anything to you or is it typical?
UDC START
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 1
[1]eMMC write fail: ABOOT