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"
I just rooted my note 3, went all OK. Installed CWM recovery, said it worked.
however, when i try to boot into recovery, it just brings me into the stock one.
ive heard something about it flashes the default recovery on boot?
how do i fix this? thanks
I flash the stock firmware on the phone.
Installed root and safestrap recovery.
Booted into safestrap, wiped stock slot and installed Goldeneye by selecting all of the safestrap options.
Unselected reboot option and installed NB1 modules.
Rebooted into system
After this when it boots up, it shows safestrap disabled. If I wait, it goes to a black screen for a while and then reboots again into stock recovery. If I reboot again, it repeats the same thing over again. Yesterday, I got it to work using this same steps if I remember correctly, but the wifi wasn't working, so I needed to flash to stock again and try again making sure to install the modules.
UPDATE: I tried again, but with the GE-XXUGNK4-49.2 rom. I first tried to flash it to stock slot, but it didn't work. Then, I tried again by creating a new slot, flashing the rom to there. It didn't work, so I deleted it and tried the stock slot again. It worked this time. Now I'm going to try this again, but with the GE-XXUHOD7-53 rom.
UPDATE2: It didn't work. I'm not sure what's going on. It flashed just fine yesterday. I'm going to try again, but without wiping stock slot before installing.
UPDATE3: Didn't work. I'm so tired of this. Does anyone have any idea what's happening with this?
UPDATE4: I got it to work! I followed the safestrap instructions for GE EXACTLY. The thing that was throwing me off was that I thought I had to install the NB1 kernel and not the OC3 since I have NB1, but I did everything OC3. Also, I have no idea how I got it to work yesterday. I'm pretty sure all I did was just install and run.
I am on 6.0.1 CyanogenMod13. I haven't done a whole lot root-wise but just today I was looking to get something from xposed and it turned out I didn't even have it installed, so I downloaded it and installed it but needing to flash the .zip I tried to boot into TWRP recovery. Somehow it got uninstalled or something because I could only get into the LG stock screen asking if I wanted to wipe everything. So I tried to install TWRP using Flashify, I installed and on the reboot it gave me a "Can't Enter Recovery Or Update" and some more things about it on the top left above the boot logo. I can't do anything recovery-wise. I'm looking to sell my G2 but I want to make it stock or at least a clean install and I can't do any of that. What can I do??
NinjaChachi said:
I am on 6.0.1 CyanogenMod13. I haven't done a whole lot root-wise but just today I was looking to get something from xposed and it turned out I didn't even have it installed, so I downloaded it and installed it but needing to flash the .zip I tried to boot into TWRP recovery. Somehow it got uninstalled or something because I could only get into the LG stock screen asking if I wanted to wipe everything. So I tried to install TWRP using Flashify, I installed and on the reboot it gave me a "Can't Enter Recovery Or Update" and some more things about it on the top left above the boot logo. I can't do anything recovery-wise. I'm looking to sell my G2 but I want to make it stock or at least a clean install and I can't do any of that. What can I do??
Click to expand...
Click to collapse
Same happened to me still cant fix it but you could try going back to stock (wouldn't work for me driver problems on windows 10)
http://forum.xda-developers.com/showthread.php?t=2432476
bump
homegrown1982 said:
Same happened to me still cant fix it but you could try going back to stock (wouldn't work for me driver problems on windows 10)
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
This got me down to 4.4.2 but when trying to install TWRP it gives me the same Boot certification error and I can't
EDIT: I used AutoRec on 4.4.2 and I have TWRP working!
Hi!
EDIT: Never mind, problem solved. Sorry.
I have finally decided to root my G900F (6.0.1). I flashed TWRP through Odin without problems, booted to TWRP to make it permanent, booted normally to check that all is well. After that I made a full backup in TWRP and flashed the BETA-SuperSU-v2.49.zip. After that, my phone no longer boots (hangs on the Galaxy S5 screen with a blue indicator LED).
I can still boot to TWRP.
How can I fix my phone? Please help. What did I do wrong?
I did try wiping the cache partition but nothing else.
Hopefully the solution does not require a full wipe.
EDIT: I see what I did wrong. I have accidentally flashed an old SuperSU.
Can I use a backup I made with a TWRP?
EDIT2: Luckily the restore did work! Will try to flash a more recent SuperSU.
flash it again but with latest version of supersu. It will work
Spawnknight said:
flash it again but with latest version of supersu. It will work
Click to expand...
Click to collapse
Yup, it did work beautifully. Lucky for me that I remembered to make a backup before rooting.