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.
Related
Hello,
This is going to come off as noob-ish:
How can I flash a 4.3 TW-based ROM onto my rooted Canadian (Bell) Note 2?
I was running CeanROM5 for a while, flashed SlimKat 4.4 last weekend but I'd like to go back to TW.
I'm usually pretty familiar with rooting and flashing ROMs (Desire Z, Note 10.1, Nexus 7...etc.), but I've read too many horror stories of people loosing their modems, IMEI going wrong...etc. with the Note 2, especially since there's a few variations of the device, so I want to be careful.
I was going to flash the stock firmware from Sammobile via Kies but my phone is being detected as a i317 and not a i317m and I'm wondering if that's a problem? (I know I could use ODIN, but again, I'm worried about screwing up the modem with what little I know right now) I was then going to use CF-Auto-Root (as I'm sure I'll lose root) to clean things up.
TL;DR I've got a Canadian (Bell) Note 2 running SlimKat, how to get onto a TW-based 4.3 rom without screwing anything up?
Thanks guys!
So, after waiting hours for the stock 4.3 firmware to download from Sammobile - it was corrupt, so I'm re-downloading, therefore I can't flash via odin just yet (apparently I still have another 2 hours on this download).
Kies won't recognize my phone either (I suspect this might be due to the whole i317 vs i317m thing?). I've tried uninstalling and reinstalling kies on my PC, using different USB ports, and rebooting my phone...etc.
Again, any help would be super appreciated! Thanks!
Alright, so I'm running 4.3 and everything is working (wifi, modem...etc) but I can access superSU.
I used CF-Auto Root and it looked like it flashed the stock recovery. I have superSU installed but I can only open (not uninstall) it from the Play Store.
However, every time I do try to open it I get the pop up window "unfortunately, SuperSU has stopped".
So what am I doing wrong?
I guess this thread can be deleted as I seem to have sorted things out.
Philz recovery is very nice BTW.
So i tried flashing the pa_n7100-4.6-BETA4-20141009 rom as well as cm-11-20141008-SNAPSHOT-M11-n7100 onto what i'm sure is my note 2 n7100. While installing, at the start, the recovery says the rom is meant for a t03g while mine's a t0ltetmo. There is no way in hell my phone's a t-mobile : firstly , i live in india, a country free from the tyranny of t-mobile, and secondly, it says gt-n7100 on bootup from stock rom. I tried removing the version checking part in the rom, hoping to force install it anyway, but it just popped up 'error'. Then i tried flashing one of the few roms available for the t0ltetmo, the Slim-t0ltetmo-4.4.4.build.8.0-OFFICIAL-6945 rom. After a successful installation, it was just stuck on the boot screen. I'm not saying i dont like the shiny slimkat logo twirling around, but i would eventually like to use my phone too. I'm now back to my stock rom after flashing my friend's n7100 recovery image, and then factory resetting, because cwm 'lost' my backup file. Anyway, i'd love to have the new 5.0 cm12 alpha, but i'm apprehensive now. Help me? :crying:
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)
Hi!
So i have a weird situation with Tab 3 P5200.. It belongs to one of my friends and it just got to bootloop with no reason. No root or custom roms installed, not even developer mode on. So i tried to flash official rom with odin but still the same. And weird thing is that sometimes it starts normally but then in minutes it starts the bootloop again.
Then i flashed 4.2.2 china variant with all the four files, pit, csc,pda etc.. And it runs normally. But there is no play store and my friend need finnish language. So now i tried install again that china variant and after that nordic 4.2.2 variant. And it works now.. And finds system update too, don't know will it install it but let's see. And before it started bootloop again after reboot so...
Do you guys have any suggestions..? Or any idea where to find full rom with all 4 files in it for nordic countries?
Hi all, I have a note 2 shg-i317 that was originally on Bell in Canada. It was unlocked and the aws mod done to it, I use freedom mobile, aka T-mobile in the states.
I was running a Rom for the past 3 years Slimfast 4.4 and liked it. I had tried Nugat on another phone, thought I would try the [ROM][7.1.2][OFFICIAL] LineageOS for N7105
I did the upgrade, broke the root, could not get a few things working, so I decided to restore the Slimfast backup I had just made (complete including modem etc) and everything works except the GPS.
GPS for me is huge, I use it a lot. I cannot lock on to 1 satellite now. Before i was able to lock onto a minimum of 16 in about 30-45 seconds, if outside.
I really dont care if I can get to 7.1 at the moment. I need my GPS back - any troublshooting for getting GPS to work on this phone?
James
I would try to flash the original stock for your phone and country from sammobile. com
Gps should work normaly then. If not your hardware is broken. If it works you can always flash your data back from your Slimfast rom.
Verstuurd vanaf mijn SM-N910C met Tapatalk
Crap, I am posting here, because I did it again. Again not sure how. I tried to run Reserection, and I guess that messed up the GPS.
To put the original stock rom on.. I have to do that through ODIN? I dont remember how I fixed this last year.. Sorry.
Hope somone can help I need the GPS.
James
ps. Used odin 3.09 to flash the original rom... still no GPS
You flashed the latest 4.4.2 room?
audit13 said:
You flashed the latest 4.4.2 room?
Click to expand...
Click to collapse
The Rom that I flashed to try and restore the GPS was I317MVLUDNF1_I317MOYADNF1_BMC (mine was an originally BELL phone)
But that did not repair the GPS from me flashing resurection.. I THINK did it. I flashed an android 6 and an android 7 rom. (Mokee) but tried to go back to my Slimfast.. and the GPS was now broken.
Basically what I did a year ago.. somehow I fixed it then.. but cannot remember at all how I did it.
James
The note 2 sold by Rogers, Bell, and Telus are exactly the same model and stock roms from these carriers can be cross flashed.
Try flashing the stock ROM twice in Odin with a factory reset in between each flash.
audit13 said:
The note 2 sold by Rogers, Bell, and Telus are exactly the same model and stock roms from these carriers can be cross flashed.
Try flashing the stock ROM twice in Odin with a factory reset in between each flash.
Click to expand...
Click to collapse
Do you mean boot up the rom.. run the reset in the rom? or flash.. - load TWRP back in.. WIPE.. then FLASH again with odin?
Thanks for helping btw.
James
I have backups (complete all partitions) of my rom.. Slimfast 4.4 from 2-3 days ago.. when I tried this. SO.. if I can get the Factory rom to restore the GPS.. how can I restore the backup.. I saw somewhere that the EFS partition could be left out and that might help? dont restore the modem? how??
James
I meant flash with Odin, boot into stock recovery, factory reset, flash again with Odin, boot into stock recovery, factory reset, and boot into the stock ROM.
Nope, still no GPS lock.. I have the flashing circle (always had) and it will not lock.. I read about where people go into a service mode and rebuild the NV? .. I assume this is something that Mokee or Reserection did.. not sure how.
Any other ideas?
James
what about using Odin or TWRP to put different modems in? does the modem effect the GPS?
tried this.. does not seem to. grrrrr wish I knew how I fixed this.
James
I assume there are no loose wires. Does it get a lock when using wifi? Not sure what else to suggest.
Not sure about rebuilding NV.
No.. I broke it with playing with custom roms.. Liniage was last year.. I did not try that this year.. but tried both android 6 reserection and android 7 Mokee.. and I am pretty sure they messed it up.. I am also pretty sure there was something I did .. easy like load an old STOCK rom and it fixed it.. I was then able to put my slimfast 4.4 back over it and it was fine. Unfortunatly .. not enough people still using this device.. I will have to have patience I guess.
James
So I have tried differenct stock roms, but I think the issue is ODIN will not restore code from a rom image that is HARDWARE based. I wanted to use Samsung smartswitch but they disabled the part of it that allowed you to factory reset the phone, this seemed to work for several people. Many have also reported entering a code and going into a service mode.. there you can do to a menu that will rebuild hardware modules back to default. But I have not been able to get into that mode because it seems to be a touchwiz only option, and I cannot find a factory rom that is touchwiz based for this model.
What needs to be done is a true FACTORY ROM image.. that would revert all software and hardware back to original, but I cannot seem to find that anywhere.
James
The only factory roms that I know of come from places like sammobile.com and they are all based on TouchWiz which is Samsung's launcher.
So guess what? put Ressurection back on.. and the GPS is back.
I cannot get it to work in any KitKat based rom.. but now anything Marshmellow up.. works.. HMMMMMM
James