Hi! As the title says I tried to flash a debloated version of the stock ROM for my galaxy tab 3 10 (The one found on this forum). But after wiping Dalvik and regular cache and installing my tablet just gets stuck on the samsung logo. I left it for half an hour sinve usually it takes some time to finally start but it remained like that. I tried turning it on and off I even took out the battery but nothing seems to work. I tried to wipe again and re-install, I went as far as to judt get a regular Stock and flash that. In the end it's still stuck. I didn't made a backup since I am a dumb dumb so any ideas are welcome, thanks.
You have a backup of efs partition?
Related
The problem only happens when I reboot or turn on the phone. When it boots up, I get multiple results. A: It boots up normally (not a problem) B: When it gets to the samsung screen, it freaks out and reboots itself again and again. It's like it's struggling to boot up. One time it got to the gs 3, but then it looped back. C: This just happened today. I booted up and it went pass the samsung screen but when it got to the gs 3 screen, the screen turned a faint pink and it stayed on that screen.
This just happened right after version 8. I know 10 was messed up but on 9 and 11, this problem persisted. Also,I don't think the issue is the phone, since I don't have this problem on other Roms. If I'm wrong please let me know .
Any suggestions, advice, help, etc is welcomed.
Please... i really need help.
I suggest you start over, this will remove any corruption and gremlins you have klinging to your phone..
http://forum.xda-developers.com/showthread.php?t=1904099.. Then re root and flash anew.
Naddict said:
I suggest you start over, this will remove any corruption and gremlins you have klinging to your phone..
http://forum.xda-developers.com/showthread.php?t=1904099.. Then re root and flash anew.
Click to expand...
Click to collapse
I unrooted, went back to stock, it did a factory reset so no bugs should have been alive. I re-rooted, made a backup, did a factory reset and wiped dalvik, then I flashed the rom zip and rebooted. It gets stuck on the Gs III screen. I waited like 5 minutes and it didn't move. My battery was at 50% so I just put it on the charger and tried to boot up and it went through to the set up screen for gmail.Just to see if it was coincedental, I did another reboot but this time it got stuck again. It sounds like a system problem but i'm not sure.Like i said earlier, this only happens on Jellybomb.
Any other ideas?
Edit: I've tried switching recoveries but it doesn't fix it.
Sigh.
Hi Guys.
So i flashed a few roms lately. started with EmotionMiUi then CM10, Omega, Alliance and well a few more.
i did a full wipe and cleared all caches each times and only had a few minor problems with the different ROMS that i was able to fix.
So i now returned to MiUi and have had it running for about a week. Tried some DPi modding yesterday, and did notice that it took longer time to boot and boot into recovery. i flashed the Xpose DPi remover, and continued using my phone. i have rebooted about 3 times today. And the last reboot caused the phone to enter the eternal "Samsung Galaxy Note II - N7100" boot static "animation".
Now i have tried pulling the battery several times, tried booting into recovery and the only thing that will let me boot into anything is power + home + volume down.
i have obtained the official samsung firmware ROM for my phone.
is my way ahead to "just" flash it using Odin, and i will have my good times back ?
Maybe try to clear Data and Cache partitions first?
mat9v said:
Maybe try to clear Data and Cache partitions first?
Click to expand...
Click to collapse
Just to clear you're stuck at the start screen( the screen it shows Note 2 and model number)?
If so, then i have no clue
If your phone goes in a bootloop ( startscreen then samsung logo animation, blank screen, start screen, samsung logo animation...) I have faced this issue while flashing Stock ROMs and you can clear this by doing a factory reset though i have no clue whether this is the correct one for MIUI ROM.
prabukannappan said:
Just to clear you're stuck at the start screen( the screen it shows Note 2 and model number)?
If so, then i have no clue
If your phone goes in a bootloop ( startscreen then samsung logo animation, blank screen, start screen, samsung logo animation...) I have faced this issue while flashing Stock ROMs and you can clear this by doing a factory reset though i have no clue whether this is the correct one for MIUI ROM.
Click to expand...
Click to collapse
i was stuck at the very first startscreen that just stayed there. i had been messing around with some DPi and a lot of tweaks.
i used Odin from my PC to flash the official firmware, then i used Philz recovery to format and clean before flashing my MiUi V5 ROM.
ALL works great.
I've been running a rooted pm-600 with clean rom for a week now. I decided to try the new megablast rom and after carefully following install instructions (all wiping done and zip install via twrp2.6.3.3.) I was stuck at the Samsung screen in the boot mode. After giving it some time and not getting past the Samsung screen, I tried restarting and the same thing happened. I used was able to go to download mode and used odin on my pc to flash back the stock rom, but I am still stuck at the Samsung screen. I get the galaxy note 10.1 2014 splash screen, the start up music, blue circle, but then it just hangs at 'samsung'. I have tried restoring stock twice now with the same results. Any ideas :crying:
tmord1 said:
I've been running a rooted pm-600 with clean rom for a week now. I decided to try the new megablast rom and after carefully following install instructions (all wiping done and zip install via twrp2.6.3.3.) I was stuck at the Samsung screen in the boot mode. After giving it some time and not getting past the Samsung screen, I tried restarting and the same thing happened. I used was able to go to download mode and used odin on my pc to flash back the stock rom, but I am still stuck at the Samsung screen. I get the galaxy note 10.1 2014 splash screen, the start up music, blue circle, but then it just hangs at 'samsung'. I have tried restoring stock twice now with the same results. Any ideas :crying:
Click to expand...
Click to collapse
The only avialable option for you now is getting into stock recovery, wiping data , cache & dalvik., you will loose your data on your internal card, but no other choices.
Thanks for the advice. I discovered that this was in part triggered/or perhaps caused by the failure of a brand new Samsung micro sdxc card. Very frustrating, had just gotten it the day before and all my recent nandroid backups were on it Appreciate the help
Sent from my SM-P600 using xda app-developers app
Back story was basically I went to use my phone that was running dicksteele buttnaked and it was frozen so I did a battery pull and that just froze up at Samsung screen and wouldn't let me into twrp. Sorry if this is a bit all over the place but if you are stuck like I was it may offer some help or at least get you thinking that you may not have tried absolutely everything.
@terpin32 got it back up, thanks for the help and all the suggestions from my post and the others I read here. Read all the suggestions for stuck at Samsung posts. Flashed via Odin all the param tz files I could find no luck. Still couldn't get it to boot normally or into recovery. So I flashed twrp via Odin still couldn't get into recovery. So I tried Phillz via Odin and bam got into recovery.
Now the issue was I had no backups via Phillz. So I tried wipes of cache and davlik still no normal reboot. Then I tried to do a full wipe to load a new ROM and the phone locked up and rebooted again. So I got back into recovery and began just trying to flash ROMS since my options were getting more limited.
First tried Buttnaked and it wouldn't boot same thing as before. Went back into Phillz and tried a full wipe for new ROM again. Froze before it finished and rebooted again. So I tried zens 4.3 and it froze on bootup. Tried to full wipe same result. Thought hey I will give a Aosp Rom a go. Dirty unicorns and everything looked like it was going to boot because it didn't freeze but it also never booted and just hung. Back into Phillz and tried a full wipe again and it frikn worked. Now I was getting somewhere. So I flashed twrp back and wiped everything again. Went to my last backup of DickSteeles ButtNaked and it booted back up just like nothing happened. My sound issue I was also having is fixed since my save was before it went goofy.
Not sure if this will help anyone but thought I would share. I do troubleshooting a lot at work and sometimes it's extreme. I came to the realization that I might need a new phone so I tried everything I could think of. My wifi is a little wonky probably because of the tz files I flashed but I will take that over the stuck bootup.
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
AussieMouse said:
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
Click to expand...
Click to collapse
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
It worked! Thank you so very much!
And I'm not a huge fan of updating my Android devices due to past experiences, but if this happens again, I might just update it to Marshmallow.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
@ashyx
i love you man...this worked for me too...thank you...now i need to reinstall TWRP again and see what's cooking......
I had this problem recently too, with the added complexity that the "Factory Reset" option in recovery wasn't working -- it would say something like "MDM does not allow factory reset" and then just reboot.
Fixed it by directly flashing TWRP with heimdall, then booting into the new TWRP recovery, performing a factory reset, and then rebooting the OS. This time it got pass the bootloop.
i flashed new twrp for T700 it's bootloop cannot enter the twrp menu keep bootlooping ...what's the solution for this?please help
Help ME!
What are "stock firmware" and "MM"? and where to get it?
I've replaced the power button thinking it was a hardware issue but now I'm not sure. I've also installed a few different stock roms but still have the same problem. Does anyone have any insight as to what could be going wrong and what I can try to get it fixed? Thanks for any help you can give. The device is a Samsung SM T-800