I have a Tab 3 T210, yesterday I updated the tab with kies to 4.4.2. The problem is the tablet closes the process, settings, systemui, touchwiz... and several times the tablet reset. I tried to install several roms, kernels and recoveries... and nothing. The rom that is more "stable" is cyanogen 11 but It has a bugs with the wifi and sometimes also It close the process.
I need help, I don't know how do.
Sorry for the language.
Related
So I've recently been having an issue with my phone that I haven't been able to fix through various standard fix methods. I've tried searching for this exact issue but the only thing that seems to work for other people (albeit they were on different devices when they had this problem) hasn't fixed my issue.
Long story short, I went from SlimROM 2.2 (and many other 4.3 based ROMS) to ForkMyLife 4.4.2 to try out KitKat, and I eventually wanted to go back to SlimROM.
I always full wipe (System/Data/Cache/Delvik) and then flash my ROM (in this case it was Slim), a reboot netted me a bootloop/boothang on the bootanimation. Wiping Cache+Delvik cache will get me to Optimizing Apps, but then it hangs at Starting Apps. At which point I can battery pull, restart, and it will restart just fine (typically, I did have one time where this didn't work). But I'd have to do this series of events every single time I reboot. I've tried multiple ROMs, multiple kernels, but everything ends up doing the same thing after a reboot. I've even done a full Stock 4.2.2 Image flashing (full SDCARD/DATA wipe an everything) using mskip's Toolkit, re-rooted and re-did my entire phone to Liquid 2.37 booted up the first time no problems, but the boothang was back on the very first reboot.
What is somewhat odd to me, is that I can run a 4.4 based ROM with no boot issues though. I ran FML 4.4.2 for a few days and numerous reboots, and the same for OmniMetal 4.4.2 to see if it would lead to any boothangs and I had no problems with either.
Any ideas or thoughts from anyone on why reverting back to 4.3 after a 4.4 ROM would cause so many issues?
Hello guys,
I have some issues while using the latest 4.4.2 DN3 ROMs. Before installing DN3 4.2 I flashed MJ5 bootloader, and it was running for a couple of weeks fine, then the phone started to freeze and reboot several times a day. I thought DN3 v5+ would fix these freezes and reboots but it was no good. I was really disappointed, as I really liked the look and feel of DN3. Now I'm using Revolution HD 31, it's stable (more or less, a couple of freezes and reboots for two weeks) and fast, but I really liked the looks of the latest DN3...
So the question is - what can I do to avoid these freezes and reboots and will upgrading the bootloader to a newer one will help me?
I don't think bootloader has anything to do with it. I was on MJ5 with 4.3 creikelo and NEVER had a reboot or force close. DN3 just freezes after 1-3 days. I had the same experience. It started getting laggy, or better said, the CPU was doing something, hence the lag, and then it just restarted by itself. And I did clean install. It is enough to reat the DN3 topic and see how many people have problems with it - and most still consider it the best ROM... I just went away to another ROM, and will post results in a week hope it doesn't behave the same as DN3
Thanks for the reply!
What ROM did you install? Is it stable?
I had a problem with mj5, my phone froze on the boot and i had to reinstall the ROM.
I think mj5 is for 4.4.2 ROMs, is a older bootloader.
brainstormer911 said:
Thanks for the reply!
What ROM did you install? Is it stable?
Click to expand...
Click to collapse
I tried JellyKat 6.7, but seems I have same issue... at first it was getting high CPU usage after a day or two, then phone became so overloaded it reacted to nothing and I had to pull battery out. Then all of a sudden I started getting SOFT reboots (that means only from the point of boot animation, no samsung screen) and I installed Xposed module Samsung Crash Fix and will see if it helps... I dunno, I am begining to believe there's something wrong with all 4.4.2 ROMs Because I never ever had FC, crash or reboot with 4.3 Criskelo....
Hi,
After upgrading OTA to kitkat (australia version) one of my favourite apps stopped working and caused constant reboots to my tab3.
I tried to downgrade with odin to the stock 4.2.2 (auatralia, from sammobile) but I could not. After flshing, the "samsung galaxy tab 3" logo appeared but the tab never turned on, it kept rebooting and rebooting from ours. I tried the same with other 4.2.2 roms with the same results. However I was able to flash any 4.4.2 rom from sammobile.
After that I tried to flash some 4.2.2 roms using twrp and bindroid, I had the same rebooting problems. However, with twrp I can flash 4.4.2 based roms as pimpdroid.
So, I do not why, apparently my tab only accepts 4.4.2 roms... Any suggestions about what should I do to go back to 4.2.2?
Thanks for your time,
A.
Bootloop in P5210
Hi I'm trying to get back to 4.4.2 to 4.2.2 works because although there are excellent applications like Facebook that are causing me problems. But in trying to make the retoroceso as I usually do with ODIN stock form and I was left in a permanent reboot and does not pass the SAMSUNG logo .... solution? Thank you!:crying:
@planinsky, Have you tried a firmware for another region in the world? I live in the United States but have found firmware for the United Kingdom or Canada works best when I flash. There should not be any difference in the firmwares except for regionalization, but it seems some work and some don't work for me. Regional settings can always be tweaked in the Settings panel after install. Do you have a nandroid backup made in TWRP? Those usually always recover a device. I too had a problem having anything flash when I first started making my rom. 3 weeks I had a device that would not boot. So it is recoverable. Odin will save your device.
@planinsky and @MDCB try to download this firmware from Sammobile. This is for the UK 4.2.2 version. http://www.sammobile.com/firmwares/download/28243/P5210XXUANB4_P5210BTUANB1_BTU.zip/
I usually use ODIN 3.07. I assume you know the following but just in case. Remember to flash it in the PDA slot. Only have "Auto reboot" and "F. Reset time" checked.
Using Odin will reset anything the 4.4.2 builds have done to the partitions. If it doesn't work, I can only suggest to try again. When it comes to flashing, sometimes the TWRP builds for our device can be a little goofy in writing. I have not investigated completely. In the 4.2.2 roms I have flashed pimpdroid and cagrom, they seem to flash good with Moonbutt77's philz recovery with very little problems. I however cannot get 4.4 roms to flash in philz but only in TWRP. So sometimes the recovery itself seems to have a problem with the android version, or so it seems.
The above is only written from my experience on this device and cannot predict every situation.
Good luck.
Hi! Thanks for the tips.
Ufortunately, I have already tried 4.2.2 ROMS from different countries (from Sammobile): Australia (the original country of my Tab), UK, New Zealand, Belgium and US. None of them worked. I'm still downloading other ROMS but I'm startin to lose the faith... The custom ROMS I have tried, neither work and get into the bootloop.
The backup I have from TWRP is from a 4.4.2 so it's not a solution.
On the other hand, I can flash almost any 4.4.2 ROM with odin and/or TWRP. So I'm afraid I'll soon give up and I will accept that my Tab will not longer run the app I loved (Movistar TV)... Hopefully with the arrival of lollypop the developers will update the app and the bug which causes the crash will disappear.
Hi all!
First of all thanks for your work..it's awesome!!thanks to you i enjoyed my s plus until some days ago it has broken..very sad day
However i decided to move on with a more modern cel, so i decided for a s4 mini.
But since the beginning i've had lot of problems..
My phone after an original update from samsung started to freeze and reboot..more and more often..i read it could be an issue with original update so i decided to mod my phone since i've had great improvements with my old s plus..
first i installed cm11 but the phone keep rebooting and rebooting ..so i installed cm12 with android l..but the problem is still here!!
the more my phone became hot the more it reboot..it's unusable and i don't know what to do..i'm also begin to doubt it's a hw problem
my warranty is gone with all this mods..so what to do? any others has this kind of problem?
thanks if yo want to answer
People encountering this should perform a factory reset and wipe everything from the phone.
Then, perform a clean install of whichever rom you wish to use, without any additional apps.
I recently encountered an issue with Apex Launcher and a recent update. Android keep crashing and soft rebooting often.. only after a few days did I realise the launcher was the issue. Since I uninstalled the app the phone hasnt restarted once!
Mine restarts after i turn on Mobile Data + GPS for navigation..
It works for a minute and restarts.
I don't know where the problem is either. I tried to flash cm10, 11.. stock 4.2 / 4.4 and nothing seems to get me rid of the problem
Hello everyone I'm Italian and I have problems with my stock galaxy tab 3 7.0 T211.
Often when I turn on the tablet the process systemui crash, then while using, many other app randomly lock, and I must open them 2-3 times to be used in normal way.
It happens also that the tablet will block for a couple of seconds and restart it automatically, but restart is not normal but is much faster.
I tried to do a factory reset from recovery, I installed with odin before the stock firmware 4.1.2 (XXAMK6) and then the 4.4.2 (XXBNI1), but in all cases nothing, the tablet gave me the same problems, particularly the problem of the process are terminated .
It also happened that during the first configuration (language, time, wifi network password, etc.) the configuration process crash, and I had to start all over again. All this even though I had just installed the firmware with odin.
I do not know what to do, it seems to me absurd that despite I start from a clean base and I use odin to flash a stock rom the tablet gives these problems, I do not understand what could depend.
I hope you can help me, any help or advice is welcome.
Many thanks to all!
Been there, done that
midnighteight said:
Hello everyone I'm Italian and I have problems with my stock galaxy tab 3 7.0 T211.
Often when I turn on the tablet the process systemui crash, then while using, many other app randomly lock, and I must open them 2-3 times to be used in normal way.
It happens also that the tablet will block for a couple of seconds and restart it automatically, but restart is not normal but is much faster.
I tried to do a factory reset from recovery, I installed with odin before the stock firmware 4.1.2 (XXAMK6) and then the 4.4.2 (XXBNI1), but in all cases nothing, the tablet gave me the same problems, particularly the problem of the process are terminated .
It also happened that during the first configuration (language, time, wifi network password, etc.) the configuration process crash, and I had to start all over again. All this even though I had just installed the firmware with odin.
I do not know what to do, it seems to me absurd that despite I start from a clean base and I use odin to flash a stock rom the tablet gives these problems, I do not understand what could depend.
I hope you can help me, any help or advice is welcome.
Many thanks to all!
Click to expand...
Click to collapse
This happened with me too but only after updating to KitKat 4.4.2 with Odin, I tried a couple of times and even used firmwares for other regions (mine is international version unlocked so it should work with no problems), I then Initialized the device using Kies 3 to the latest firmware available for my region for the SM-T211, it went OK, I still get crashes, I mean the problem hasn't totally been solved, but it's much much less crashes now than before when device was flashed with Odin (may I say that it was the same stock rom with the same build number from both Odin and Kies 3, still the one from Kies 3 was much more stable)