Develop Bugs

Problems after flashing

Hello everyone , until yesterday I had 0 problems with flashing ROM's ... Last night i tried to flash the newest Xylon and after i flashed it and it booted up, problems started ... My phone became so UNUSABLE that I had to pull battery out and boot into recovery - wipe - restore and continue ... Today the same thing happened when I tried to flash the newest Atom - and the same thing over again ... My recoveries are working great, since whenever I restore to them I have 0 problems ... Any1 has an idea? My recovery is purity ROM v4.4 + AK kernel purity v021. and it's working awesome ...

I had a issue with the latest version of xylon. GSM Gnex. It flashed fine then on reboot the phone kept restarting on the boot animation. Sometimes it wouldnt even make it to the boot animation. It would just restart on the google screen. Tried factory reset. Wiping the phone completely. I tried going back to stock but nothing worked. So i relocked the bootloader did a complete wipe. And now its on on its way back to samsung.
Sent from my Nexus 4 using Tapatalk 2

Thx for the answer, but my problems aren't quite like yours ... Seems that, whenever I want to flash a new ROM it slows down like hell, it takes like 3 - 5 secs to register a touch, and then another 3 - 5 secs till my phones DOES what I've pressed on ... I've got like 7.5 GB of free storage, so that shouldn't be the problem ... I've also heared about that problem with a certain "chip" - the phone gets so slow ( not really remember what the problem was ) - but my chip isn't the one that actually HAS that problem, so it's not that either ...

sgh-i317 wont power up past sgn2 screen without being plugged into outlet

Hi...I've searched everywhere and I haven't seen anything close to my issue. But if there is and I missed it I apologize in advance and I appreciate any help/advice.
Well I rooted my phone from 4.3 with no issues. I used safe root so it wouldnt trip knox. I flashed sokp's 4.4.2 ROM with the proper gapps and agni kernel. My issue started after I tried updating my camera with photosphere 4.3. I went to use the 3d feature and it shut my phone off and started to loop. Also flashed the camera fix zip but that didn't help either. I got into recovery using cwm and wiped everything from the cache to data, almost to the point of no service. So i flashed beanstalk 4.3 rom hoping it would solve problem but it didn't. I even did a factory reset (didnt work) and found a rooted stock ROM I flashed thru Odin then back to beanstalk, all to no avail. Now I have to keep my phone plugged into a power source in order for my phone load past "sgn2" screen. And if I unplug it then it resets phone and loops. I also noticed that with beanstalk I have no kernel(well it reads unavailable). I was thinking that maybe after the camera failed that some data or something maybe corrupted. Is there a way to wipe everything to the beginning, like fresh from at&t, so It will stop looping and I don't have to keep my phone plugged into the wall?
Also with mean bean I can uplug my phone for a few min before it resets but if I try to open any apps it resets. It seems as though my phone isn't getting enough power.
Again all help is greatly appreciated

[Q] Phone randomly freezing

Please bare with me, I'm trying to think of every possible detail for anyone to help me with this....
My brother gave me his Note 2 to "fix" because it was stuck in a boot loop and would randomly freeze. It was 100% stock, unrooted and less than a year old. The problem started when the phone auto-updated to 4.4.2. After investigating and tinkering around, I got it out of the boot loop (I just wiped the cache). Upon reboot, the phone would function normally for up to 90 seconds (approx) then freeze. The only way to unfreeze was to battery pull, holding the power button down didn't work. After repeating the reboot process several times I realized that each time it attempted to do a system update. I looked for a way to disable the auto-update feature and was unable to find it.
My next thought went to rooting and flashing a custom ROM. After all, if the problem was with the stock, flashing would fix that. I have rooted, installed philz recovery and flashed the Alliance ROM. I wiped all cache and booted her up. To my dismay, it's still freezing. I've gotten past the boot screen and am now freezing in different places on the "android is upgrading" screen. Each freeze causes me to have to battery pull and start over.
I am out of ideas. I would like to be able to fix this phone and put service on it. Thank you in advance for all help!
-Amy

Nerdmom3 said:
Please bare with me, I'm trying to think of every possible detail for anyone to help me with this....
My brother gave me his Note 2 to "fix" because it was stuck in a boot loop and would randomly freeze. It was 100% stock, unrooted and less than a year old. The problem started when the phone auto-updated to 4.4.2. After investigating and tinkering around, I got it out of the boot loop (I just wiped the cache). Upon reboot, the phone would function normally for up to 90 seconds (approx) then freeze. The only way to unfreeze was to battery pull, holding the power button down didn't work. After repeating the reboot process several times I realized that each time it attempted to do a system update. I looked for a way to disable the auto-update feature and was unable to find it.
My next thought went to rooting and flashing a custom ROM. After all, if the problem was with the stock, flashing would fix that. I have rooted, installed philz recovery and flashed the Alliance ROM. I wiped all cache and booted her up. To my dismay, it's still freezing. I've gotten past the boot screen and am now freezing in different places on the "android is upgrading" screen. Each freeze causes me to have to battery pull and start over.
I am out of ideas. I would like to be able to fix this phone and put service on it. Thank you in advance for all help!
-Amy
Click to expand...
Click to collapse
Make sure you are using philz recovery (6.07.9 recommended). You will need to wipe the internal sdcard. Go under mounts option and select wipe /data /data/media option then go to reboot menu and reboot recovery. Now install rom and see how if that works.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
Make sure you are using philz recovery (6.07.9 recommended). You will need to wipe the internal sdcard. Go under mounts option and select wipe /data /data/media option then go to reboot menu and reboot recovery. Now install rom and see how if that works.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you!
I wiped the internal SD. That enabled me to format the phone then install the Liquid Smooth ROM. So far so good. It's been 48 hours with no problems.
Thanks again for your help!

Frozen on Samsung Logo

Hi. I was trying out Blisspop on this tablet and decided I preferred CM11 so decided to restore a backup. After rebooting, nothing turned on, only download mode worked so I just flashed stock firmware using Odin (which I had used successfully previously). Now it boots but gets stuck at the Samsung Logo. I can still get to download mode, but nothing else. I've read that if factory reset in the stock recovery, it'll work itself out but I can't even get to it. Any suggestions? Thanks.

jalchemyst said:
Hi. I was trying out Blisspop on this tablet and decided I preferred CM11 so decided to restore a backup. After rebooting, nothing turned on, only download mode worked so I just flashed stock firmware using Odin (which I had used successfully previously). Now it boots but gets stuck at the Samsung Logo. I can still get to download mode, but nothing else. I've read that if factory reset in the stock recovery, it'll work itself out but I can't even get to it. Any suggestions? Thanks.
Click to expand...
Click to collapse
Dont panic really common problem happened to me.
1. Boot into recovery, if not flash one with odin coz your gonna need something...like philz touch or team win or whatever.
2. Wipe cache and dalvik, reboot and wait, samething might appear to happen but it should boot.
Basically ive noticed a few times now on my t805 that the cache wouldnt format propperly and became corrupt and caused this.
I knew this because in the recovery a bunch of errors appeared saying couldnt acces log from cache/blah zt each time i navigated the menu of revoveryand so i wiped cache and they stopped
Booted and viola...if you see any other errors in recovery tell us here.
Good luck m8.

pdolton2000 said:
Dont panic really common problem happened to me.
1. Boot into recovery, if not flash one with odin coz your gonna need something...like philz touch or team win or whatever.
2. Wipe cache and dalvik, reboot and wait, samething might appear to happen but it should boot.
Basically ive noticed a few times now on my t805 that the cache wouldnt format propperly and became corrupt and caused this.
I knew this because in the recovery a bunch of errors appeared saying couldnt acces log from cache/blah zt each time i navigated the menu of revoveryand so i wiped cache and they stopped
Booted and viola...if you see any other errors in recovery tell us here.
Good luck m8.
Click to expand...
Click to collapse
The problem was that I couldn't even get into recovery. But found thread on xda that mentioned if you turn off the tablet from download mode (pressing power and volume down) then you can use the normal three button method to get to recovery. And then yes, I wiped everything I could and it finally booted back up. Thanks for the help mate.

jalchemyst said:
The problem was that I couldn't even get into recovery. But found thread on xda that mentioned if you turn off the tablet from download mode (pressing power and volume down) then you can use the normal three button method to get to recovery. And then yes, I wiped everything I could and it finally booted back up. Thanks for the help mate.
Click to expand...
Click to collapse
No worries pal glad all went well in the end m8

Samsung Galaxy Tab S stuck in bootloop after flashing official ROM and factory reset.

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