Related
Solution to GPS loss after flashing this modem with some other ROMs:
1. Download the latest CM10.1 nightly for T999 and the lastest GAPPs for the CM10.1 (both files can be found in cyanogenmod.com)
2. Odin Stock Deodexed Official T999UVDLJA +Root
http://forum.xda-developers.com/show....php?t=1991255
3. Odin recovery (TWRP)
Note- do not make phone make a full reboot after odin twrp. The stock recovery might write over the flashed twrp. So remove battery of phone when rebooting.
4. Manually reboot to recovery by pressing simutaneously the home, volume up and on button. Release on button and keep pressing home and volume up button when phone vibrates.
5. In recovery (twrp), wipe cache, factory wipe, system and dalvik.
6. Flash CM10.1 nightly then GAPPs.
7. Reboot phone.
8. Turn on GPS and turn on navigation. A flashing GPS icon should appear on the navigation bar of your phone. This means your GPS has been fixed.
You can now flash whatever ROM you like. I flashed my favorite Frosty.
Thank button please it this helps..
kusgan said:
Solution to GPS loss after flashing this modem with some other ROMs:
1. Download the latest CM10.1 nightly for T999 and the lastest GAPPs for the CM10.1 (both files can be found in cyanogenmod.com)
2. Odin Stock Deodexed Official T999UVDLJA +Root
http://forum.xda-developers.com/show....php?t=1991255
3. Odin recovery (TWRP)
Note- do not make phone make a full reboot after odin twrp. The stock recovery might write over the flashed twrp. So remove battery of phone when rebooting.
4. Manually reboot to recovery by pressing simutaneously the home, volume up and on button. Release on button and keep pressing home and volume up button when phone vibrates.
5. In recovery (twrp), wipe cache, factory wipe, system and dalvik.
6. Flash CM10.1 nightly then GAPPs.
7. Reboot phone.
8. Turn on GPS and turn on navigation. A flashing GPS icon should appear on the navigation bar of your phone. This means your GPS has been fixed.
You can now flash whatever ROM you like. I flashed my favorite Frosty.
Thank button please it this helps..
Click to expand...
Click to collapse
This should be stickied, so many people having problems with GPS loss, mainly because people flash a 4.2.x ROM and flash back to a 4.1.x ROM.
Also for step number 1, it can be a ROM of your choice, at least that what I did and GPS worked perfectly fine.
Number 8 has a typo, the flashing GPS icon will appear in the status bar.
Thanks for this, should have a mod sticky this, its very helpful!
|When Emotion Goes Up, Logic Goes Down|
Nice info to have.
In some of my recent posts I helped someone that lost the use of their gps.
I've cut down the steps for myself now as all I have to do is backup my current custom rom, wipe cache/dalvik/system/factory, flash a cm10 rom, boot up and make sure gps works, boot back into recovery then restore the custom rom i was using.
That worked for me and 3 friends 100% of the time now. Sucks but 2 of them just about took their phone in for warranty work for gps issues but my short method fixed em right up.
Regardless it's nice to have options to fix these stupid gps problems so thanks
For question #3, may I ask why stock recovery would overwrite the custom recovery with a full reboot? I wouldn't recommend telling people to pull their battery at all while using Odin. While it seems obvious to most when to pull the battery, it's just a disaster waiting to happen.
Is this to only get GPS back on 10.1? I'm confused lol. I flashed the LJC modem and still have GPS, just installed a TouchWiz rom and still have GPS working... I'm confused.
mt3g said:
Is this to only get GPS back on 10.1? I'm confused lol. I flashed the LJC modem and still have GPS, just installed a TouchWiz rom and still have GPS working... I'm confused.
Click to expand...
Click to collapse
I think he's saying it's a general guide for losing GPS with any rom.
To OP: your time and effort are definitely appreciated, I'm just curious how far this method was tested. For example, did you try using Odin to go back to stock to see if that helped? What methods did you eliminate in the process? I'm wondering if it was more of a coincidence that it worked after going to AOSP, because there really isn't anything different from TW roms that would "fix" GPS. I'm not saying you're wrong by any means, I'm just a little confused as well
Towle said:
I think he's saying it's a general guide for losing GPS with any rom.
To OP: your time and effort are definitely appreciated, I'm just curious how far this method was tested. For example, did you try using Odin to go back to stock to see if that helped? What methods did you eliminate in the process? I'm wondering if it was more of a coincidence that it worked after going to AOSP, because there really isn't anything different from TW roms that would "fix" GPS. I'm not saying you're wrong by any means, I'm just a little confused as well
Click to expand...
Click to collapse
Exactly, from what I've read (why I'm confused) is that the issue is flashing a 4.2 rom then going back to a 4.1 rom, GPS is borked... not using 4.2 then going back to 4.2... Is there another issue at hand that I'm not aware of?
mt3g said:
Exactly, from what I've read (why I'm confused) is that the issue is flashing a 4.2 rom then going back to a 4.1 rom, GPS is borked... not using 4.2 then going back to 4.2... Is there another issue at hand that I'm not aware of?
Click to expand...
Click to collapse
There's no other issue that I'm aware of. Being that 4.2 and 4.1 have very different structures, I always odin root66 before going backwards, and have never experienced GPS issues.
Towle said:
There's no other issue that I'm aware of. Being that 4.2 and 4.1 have very different structures, I always odin root66 before going backwards, and have never experienced GPS issues.
Click to expand...
Click to collapse
I see the GPS thing, it isn't pin pointed, it gets me about 50ft off. ODIN it is, love boring nights like these.
mt3g said:
Is this to only get GPS back on 10.1? I'm confused lol. I flashed the LJC modem and still have GPS, just installed a TouchWiz rom and still have GPS working... I'm confused.
Click to expand...
Click to collapse
Towle said:
I think he's saying it's a general guide for losing GPS with any rom.
To OP: your time and effort are definitely appreciated, I'm just curious how far this method was tested. For example, did you try using Odin to go back to stock to see if that helped? What methods did you eliminate in the process? I'm wondering if it was more of a coincidence that it worked after going to AOSP, because there really isn't anything different from TW roms that would "fix" GPS. I'm not saying you're wrong by any means, I'm just a little confused as well
Click to expand...
Click to collapse
That's what I commented on earlier. It doesn't have to be cm 10.1, just flash the ROM of your choice.
I've actually tried this, but instead of flashing a stock ROM with root, I went back to complete stock without root and my GPS started working as it did before the issue occurred, I the rooted my s3 once again and flashed a custom ROM of my choice (Darthstalker) and my GPS was still working.
I think the problem is going from 4.2.x down to 4.1.x. At least that seems to be the issue. But I'm not sure if GPS would work again if you were to go from 4.2.x to 4.1.x back to 4.2.x.
|When Emotion Goes Up, Logic Goes Down|
707BeastMode707 said:
That's what I commented on earlier. It doesn't have to be cm 10.1, just flash the ROM of your choice.
I've actually tried this, but instead of flashing a stock ROM with root, I went back to complete stock without root and my GPS started working as it did before the issue occurred, I the rooted my s3 once again and flashed a custom ROM of my choice (Darthstalker) and my GPS was still working.
I think the problem is going from 4.2.x down to 4.1.x. At least that seems to be the issue. But I'm not sure if GPS would work again if you were to go from 4.2.x to 4.1.x back to 4.2.x.
|When Emotion Goes Up, Logic Goes Down|
Click to expand...
Click to collapse
Tried from 4.2.x to 4.1.x to 4.2.x. Did not fix...
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919
aLdaRiS said:
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919
Click to expand...
Click to collapse
Interesting.
I was about to try odin'ing back to stock and reflashing twrp.
The only thing I wonder if may be related is when you restore a backup with TWRP it gives options of all sorts of partitions besides system/data/cache etc... preload etc. It's possible it doesn't like mucking with those.
Interesting to note: If I install a CM nightly, it will allow me to reboot. Wickedv2 or my backup of wickedv2 no go.
Testing further.
Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.
saldebot said:
Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.
Click to expand...
Click to collapse
Righto. Sounds like a valid idea.
Unfortunately, the download links in konane's thread are timing out for me mid download. Tragic.
Managed to snag it from another location. Flashed back to stock firmware/recovery via odin.
Letting it boot to see what it does.
EDIT:
That did it.
Restored my backup and most everything is working correctly (restoring my titanium backup of all apps now.)
Few things were messed up (swiftkey was missing a language pack etc?)
But looks like AOSP/AOKP roms do something to the partition table as you said that requires flashing back the original.
Good to know and thanks for the help!
Don't wipe system in twrp.
makomek said:
Don't wipe system in twrp.
Click to expand...
Click to collapse
Does this cause issues? Didn't know.
I found that only CM nightlies would reboot fine. restoring via odin stock official then going back and putting on wicked again seemed to work to fix it and I can now reboot in a touchwhiz based rom.
re: stuck
bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
If you want a 95% sure way of fixing it so it boots completly,
then try this, it usually always works.
Get the phone into recovery mode twrp/cwm does not matter.
Then simply do a "factory reset" and I am fairly certain that it
will boot completly, I have seen this issue so many times
already not just here in the S4 thread but also in the S3.
The factory reset will not delete any of your music, videos and pictures.
Good luck!
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Do you by chance have a refurbished s2?
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app
es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.
es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...
I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.
DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.
Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte
OK, so I went into TWRP 2.6.0.0 and tried to flash CM 10.2. It came up with an error so I restored using the backup I had made, and after the restore it told me that root permissions had been lost, and asked if I wanted to fix it. I swiped to rix root permissions, and now it doesn't seem to be able to boot up.
It gets through the boot animation fine, bu gets stuck on the final screen where it flashes SAMSUNG across the screen. I can boot back into TWRP and have tried wiping data and starting fresh, installing a different ROM, everything I can to try to get it to start fresh, but the phone always gets stuck at the same screen flashing SAMSUNG.
Any ideas of what I should do to remedy this problem??
BlackHayze said:
OK, so I went into TWRP 2.6.0.0 and tried to flash CM 10.2. It came up with an error so I restored using the backup I had made, and after the restore it told me that root permissions had been lost, and asked if I wanted to fix it. I swiped to rix root permissions, and now it doesn't seem to be able to boot up.
It gets through the boot animation fine, bu gets stuck on the final screen where it flashes SAMSUNG across the screen. I can boot back into TWRP and have tried wiping data and starting fresh, installing a different ROM, everything I can to try to get it to start fresh, but the phone always gets stuck at the same screen flashing SAMSUNG.
Any ideas of what I should do to remedy this problem??
Click to expand...
Click to collapse
Start fresh again but this time in TWRP goto wipe/system that will rid all old rom files which sounds like your issue, worth a shot
SGSIIIJB said:
Start fresh again but this time in TWRP goto wipe/system that will rid all old rom files which sounds like your issue, worth a shot
Click to expand...
Click to collapse
Hopefully I can get a fast response here, I did that, but got a warning "No OS installed" before rebooting. Is that just telling me no ROM installed or does that literally mean that there is not an OS on the phone anymore? The second option seems unlikely but I don't want to risk it and mess things up even further.
BlackHayze said:
Hopefully I can get a fast response here, I did that, but got a warning "No OS installed" before rebooting. Is that just telling me no ROM installed or does that literally mean that there is not an OS on the phone anymore? The second option seems unlikely but I don't want to risk it and mess things up even further.
Click to expand...
Click to collapse
well after you wipe everything including system you need to install a rom. IF your NOT currently OTA updated to 4.3 use billard's zip:::::
[ROM/RESTORE][!MD4 OTA!](5-10)Quick Return to UNROOTED STOCK WITH FLASH COUNT RESET
Wipe everything :/system
Flash billards zip
Flash root.zip to keep root
Flash recovery zip to keep custom recovery
reboot
SGSIIIJB said:
well after you wipe everything including system you need to install a rom. IF your NOT currently OTA updated to 4.3 use billard's zip:::::
[ROM/RESTORE][!MD4 OTA!](5-10)Quick Return to UNROOTED STOCK WITH FLASH COUNT RESET
Click to expand...
Click to collapse
OK, I'll try to find a ROM to install really quickly just in case, but the problem comes in somehow I get an error on every single ROM I try to install, still don't know the issue, as I have installed many ROMs on my One without issue (this is my mom's S3, she just wants tethering to be a native feature on her phone.)
BlackHayze said:
OK, I'll try to find a ROM to install really quickly just in case, but the problem comes in somehow I get an error on every single ROM I try to install, still don't know the issue, as I have installed many ROMs on my One without issue (this is my mom's S3, she just wants tethering to be a native feature on her phone.)
Click to expand...
Click to collapse
If that's the case, I'd recommend this ROM: http://forum.xda-developers.com/showthread.php?t=2549136 I installed the SPHL710_ALLINONE_MK3_ODEX_12-04-2013_1030pm.zip which includes the latest stock 4.3 without all the KNOX stuff and with native tethering.
It also wipes the system partition for you.
Good luck!!
BlackHayze said:
OK, I'll try to find a ROM to install really quickly just in case, but the problem comes in somehow I get an error on every single ROM I try to install, still don't know the issue, as I have installed many ROMs on my One without issue (this is my mom's S3, she just wants tethering to be a native feature on her phone.)
Click to expand...
Click to collapse
Shouldnt be getting any errors installing/switching roms if your wiping correctly, If native tether is all your after then most if not all custom roms come with it enabled or you can keep stock rom and just flash the hotspot mod [MOD][Deodex][Odex][MB1][MC3][MD4][MK3]Hotspot Mod - Working 4G
BAReese said:
If that's the case, I'd recommend this ROM: http://forum.xda-developers.com/showthread.php?t=2549136 I installed the SPHL710_ALLINONE_MK3_ODEX_12-04-2013_1030pm.zip which includes the latest stock 4.3 without all the KNOX stuff and with native tethering.
It also wipes the system partition for you.
Good luck!!
Click to expand...
Click to collapse
Thank you! I will give this one a shot!
SGSIIIJB said:
Shouldnt be getting any errors installing/switching roms if your wiping correctly, If native tether is all your after then most if not all custom roms come with it enabled or you can keep stock rom and just flash the hotspot mod [MOD][Deodex][Odex][MB1][MC3][MD4][MK3]Hotspot Mod - Working 4G
Click to expand...
Click to collapse
I'm just as confused as anyone as to why I'm getting errors. The phone has proper root access and is running on TWRP, the same recovery I use on my One, and I have done at least 50-60 flashes of ROMs on that phone, without issue. I keep getting virtually the same error, something wrong with executing the updater binary in zip.
BAReese said:
If that's the case, I'd recommend this ROM: http://forum.xda-developers.com/showthread.php?t=2549136 I installed the SPHL710_ALLINONE_MK3_ODEX_12-04-2013_1030pm.zip which includes the latest stock 4.3 without all the KNOX stuff and with native tethering.
It also wipes the system partition for you.
Good luck!!
Click to expand...
Click to collapse
The ALLINONE worked! Thank you so much for the help guys! I appreciate it!
Hi All
I've been having such trouble flashing custom ROMs on my Samsung Galaxy Tab Pro 10.1 WiFi SM-T520. I was sucessfully able to flash TWRP 2.8.7 via odin on the device. However, I've tried several ROMs (CM11, 12, 12.1, Unofficial Liquidsmooth) each with their own issues but whichever is able to be flashed always ends up with random startup reboots. I cannot for the life of me figure out why or what is the reason. If I flash back to stock Samsung firmware, everything is fine, works perfectly but no custom firmware.
CM12.1 out right hangs during install in TWRP. The only way I was able to install it is via Cyanogen Recovery which I flashed via odin then attempted to install the rom but even still ends up in random reboots during first bootup and a few times during optimizing apps.
Just a note, I have been doing full wipes (cache, data, system) prior to flashing the ROMs. I don't know what else to do. CM12.1 works really great and smooth but cannot use it because of these random reboots. Can anyone shed some light so I can have a successful flash?
ALSO, I would like to note one suspicion I have and that is my tablet came preloaded with KOT49H.T520UEUAOD1 (T520UEUAOD1_T520XARAOD1_XAR) Samsung Firmware Build. I wonder if perhaps something with this latest build shipped is causing my troubles but am not sure.
Thanks in advanced!
Try booting back to recovery immediatly after new rom flash and perform factory reset and it ahould fix it in most cases.
Sent from my LG-D800 using XDA Free mobile app
I tried the factory reset suggestion but unfortunately did not make a difference.
Are you restoring any backups after flashing? I have been having the same issue, since flashing back to stock. I didn't like stock so I went back to CWM 12.1, which worked flawlessly before. now having random reboots, and the longer I leave it on my system, it's takes longer and longer to wake each time. The only difference between now and the first time I flashed, is, this time I restored a backup! I to, wipe before and after flashing!
Mossey said:
Are you restoring any backups after flashing? I have been having the same issue, since flashing back to stock. I didn't like stock so I went back to CWM 12.1, which worked flawlessly before. now having random reboots, and the longer I leave it on my system, it's takes longer and longer to wake each time. The only difference between now and the first time I flashed, is, this time I restored a backup! I to, wipe before and after flashing!
Click to expand...
Click to collapse
No backup/restores involved for me. Are you still experiencing this issue with CM12.1 or was restoring the backup the problem in your situation?
I am wondering if perhaps the bootloader version that is based off of the latest official stock ROM that was released in April/May 2015 has something to do with my issues. Is there anyone that was on the latest stock Samsung ROM that has been able to successfully flash a custom ROM and use it in a stable way (short of minor CM bugs)?