I've flashed everything correctly and I've tried dirty and clean flashing, but it always gets stuck at the Samsung boot screen, it dims a little and then doesn't do anything else, it does this with every custom rom and i have no clue how to fix it, can anyone help?
Related
The setup: Galaxy S3 (d2att SGH-I747) running Slim Kat 4.4.4. Bootloader is I747UCUFNJ1 and the recovery is TWRP v2.8.6.0. The phone already rooted with a custom ROM on it. At one point in the past, somebody had tried to install CyanogenMod, but I don't know what they did.
The issue: When I boot my phone, if flashes a "Samsung" logo briefly, then the SlimKat logo, then the SlimKat boot animation in that order. But, when I boot the phone into recovery, it flashes the "Samsung" logo, then a logo that says "Samsung Galaxy SIII" with the cyanogen guy logo below it, then the TWRP splash screen. I am not running Cyanogenmod and am wondering why the second logo appears and how to get rid of it. This has not affect on the performance of the phone, but is something I would like to figure out to better understand how the phone works. Before you tell me to Google this, I have spent countless hours researching this issue and have found only one thread on another forum that mentions this problem with no replies. I cannot find anything about boot logos for recovery, how they get there, how they are changed, where they reside. Keep in mind, I am NOT talking about the system logo or the system boot animation.
What I have tried: When I got the phone, it was on MJB bootloader and have have since upgraded it using Odin and instructions/files from enewman17 and postings on this site. I have flashed his stock rooted ROMS (both MJB and NJ1). I have installed several custom Roms (Cyanogen, SlimKat, Stock_rooted), several recoveries using both the app and Odin (CWM, TWRP, and philz_touch), and at least one Kernel (Majestic 1.0.9). This boot logo remains. The only success I had in getting it to disappear was by flashing progressively older TWRPs and it took back until 2.5.0.0 before it dissapeared. TWRP 2.5.0.0 doesn't even use a logo, so it was probably still there, just not used. The phone works great with everything I have done, it is just this logo that remains.
Any thoughts or suggestions?
Here is what I believe you are encountering. If I am not mistaken Slimroms uses pretty much the stock CM kernel but they have replaced the splash screen to be of Slimroms design. However when you boot into recovery I'm guessing there is a different splash screen that is accessed which is still what cyanogenmod put in the kernel.
Could be wrong but I believe that is the case.
Possibly, but I think I have ruled that scenario out. I have flashed a different kernel and a stock ROM but the CM recovery boot logo remains.
Hi guys, relatively new here.
To start of I wouldn't say that I'm a complete noob when it come to this sort of stuff but I'm at a bit of a loss here.
To sum up my issue real quick;
My Galaxy Tab 3 SM-t210r running 4.1.2 stock that I rooted a while back started acting strange. Google services begun to unexpectedly shut off or stop working and I was getting annoying os popups so I decided to install a new custom, debloated rom.
After a few quick google searched ended up downloading StockROM-Ultimate Edition for the t210r.
Launched into TWRP 2.8.0.0 recovery, did a wipe and installed said zip of rom.
Now the issue that arose here is that I can't seem to boot into the os at all. Upon restarting or powering off and on I am greeted with the Samsung Galaxy Tab 3 splash screen, it hangs there for about 10-20 seconds, reboots(screen goes black?) that same splash screen shows up and I'm booted back into TWRP.
After countless googles searches I decided to unroot and go back to stock FW.
I've found the correct 4.1.2 stock rom on sammobile. Opened up Odin 3.07 and flashed. Everything goes good, Odin says RESET, tablet reboots, same two Samsung Galaxy screens and I'm back into TWRP. Odin indicating PASS! after a few seconds in twrp. Whether I reset to factory setting in TWRP or not, after flash, I'm always ending up in TWRP with the os never booting.
tldr; stuck in TWRP boot loop after custom rom and even stock rom flash.
Any assistance would be great
-Dan
The phone will boot, but I can see a semi-transparent logo (Samsung Galaxy S III, then under it is the Cyanogenmod icon) in the background, it's everywhere and it's like someone took a permanent marker to my screen...
Device model: SPH-L710
Rom: Exodus version 5.1-20151224-NIGHTLY
The android version is 5.1 lollipop
I have tried 4 different roms, I can't remember all the names but the roms are obviously not the problem, I believe it has something to do with the twrp recovery I flashed to the phone. This started after the phone would no longer boot past the logo that is now in the background, at the time it was using Resurrection Remix OS, I had flashed it after I bricked the previous rom (Cyanogenmod 13) from updating to 14.1 and ever since then it has had the Cyanogenmod logo at boot, but ever since the phone had been soft bricked for the second time, the logo stays even after boot. Help please, this is all the information I can come up with off the top of my head
mispelt said:
The phone will boot, but I can see a semi-transparent logo (Samsung Galaxy S III, then under it is the Cyanogenmod icon) in the background, it's everywhere and it's like someone took a permanent marker to my screen...
Device model: SPH-L710
Rom: Exodus version 5.1-20151224-NIGHTLY
The android version is 5.1 lollipop
I have tried 4 different roms, I can't remember all the names but the roms are obviously not the problem, I believe it has something to do with the twrp recovery I flashed to the phone. This started after the phone would no longer boot past the logo that is now in the background, at the time it was using Resurrection Remix OS, I had flashed it after I bricked the previous rom (Cyanogenmod 13) from updating to 14.1 and ever since then it has had the Cyanogenmod logo at boot, but ever since the phone had been soft bricked for the second time, the logo stays even after boot. Help please, this is all the information I can come up with off the top of my head
Click to expand...
Click to collapse
have you tried flashing a stock tar.md5, rerooting, re-TWRPing and reROMming?
mispelt said:
The phone will boot, but I can see a semi-transparent logo (Samsung Galaxy S III, then under it is the Cyanogenmod icon) in the background, it's everywhere and it's like someone took a permanent marker to my screen...
Device model: SPH-L710
Rom: Exodus version 5.1-20151224-NIGHTLY
The android version is 5.1 lollipop
I have tried 4 different roms, I can't remember all the names but the roms are obviously not the problem, I believe it has something to do with the twrp recovery I flashed to the phone. This started after the phone would no longer boot past the logo that is now in the background, at the time it was using Resurrection Remix OS, I had flashed it after I bricked the previous rom (Cyanogenmod 13) from updating to 14.1 and ever since then it has had the Cyanogenmod logo at boot, but ever since the phone had been soft bricked for the second time, the logo stays even after boot. Help please, this is all the information I can come up with off the top of my head
Click to expand...
Click to collapse
It sat on the boot screen with the logo on it too long. It's burned into the screen. It's permanent.
madbat99 said:
It sat on the boot screen with the logo on it too long. It's burned into the screen. It's permanent.
Click to expand...
Click to collapse
cant really fully diagnose it as burn in without knowing if its always there no matter what screen its on, but thats what i was hoping it wasnt. If madbat is right, then your amoled is toasty. Thats why i was suggesting to flash the stock tar to see if its always there
As the title says, I flash an image, don't even get to boot screen, just goes black after bootloader warning then reboots, occuring on havok 2 , and a few more (can't remember the ones I tested) anyone else have this issue?
Came from a fresh reinstall of B368, to get rid of custom kernel, so I can't see any issues there.
Hi guys
I have the chinese version with global rom.
Successfully installed TWRP and crDroid 10.0 rom but the google first time setup kept freezing (everything else worked perfect) so I decided to reflash the rom.
When I reflashed the rom it keeps getting stuck on the crDroid boot screen, have left it overnight and same.
Tried reflashing vbmeta, firmware and then crDroid with various wipes but same result.
I would appreciate any advice.
Mubs