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...
Related
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
joshnichols189 said:
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
Click to expand...
Click to collapse
I've tried all the latest kernels. Every kernel I've tried is compatible with the ROM I've tried it on.
isikh said:
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
Click to expand...
Click to collapse
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
TheAxman said:
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
Click to expand...
Click to collapse
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
isikh said:
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
Click to expand...
Click to collapse
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
TheAxman said:
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
Click to expand...
Click to collapse
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Use this kernel it works perfectly on CM10
http://forum.xda-developers.com/showthread.php?t=1845836
EDIT: nvm use this one http://forum.xda-developers.com/showpost.php?p=31025930&postcount=1152
isikh said:
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Click to expand...
Click to collapse
Now I am a tad confused, you have UVALH2 on the phone already, and you want to flash UVALH2? or did you typo? I am no dev, but from what I have been seeing, the radio should not matter at the moment, if I am wrong, someone please set me straight, also, I will be on the web all night and tomorrow, so I will help where ever I can, I will check here for your progress. Good luck my friend.
BTW, I do not like stock roms, so to me CM10 is for sure better. Faster also.
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
joshnichols189 said:
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
Click to expand...
Click to collapse
Yeah, I know all this, but I wanted to ask in case I may have missed something. Even when you're pretty Android savvy when it comes to rooting and whatnot, you do miss things on occasion. In this instant I didn't, but I was hoping I did because a bunch of custom kernels won't work on my phone with CM10! Trinity worked well, so I'm waiting for those. It must be some specific chip related issue because I'm not the only one. Anyways, thanks everyone!
So building and flashing ROMs is nothing new to me. I've been doing this since the Captivate days and have done this with all of my Android devices including my new Kindle Fire 2 (which is running 4.2) but for the life of me, I cannot get a 4.2 ROM running smoothly on my GS3.
Here's the deal. When flashing any 4.2 ROM, I get the same issues. Most times, it takes several (as in at least 8) presses of the Power button or home button to wake the screen. When it finally wakes, the animation on the "unlock" button freezes. I can sometimes still swipe it to unlock but most times, the button itself doesn't move. The phone typically runs fine once unlocked.
I know there are some camera issues still but mine make it totally unusable. I can open the camera but rotating it typically screws the orientation up on screen and no other screen presses work afterward. If I tap to open settings or flash settings, the options show up on screen but then again, screen presses are no longer working. I have to exit camera and start over which typically results in a couple Gallery FCs before it finally opens again.
What I've done to no avail. I've tried multiple combinations of wiping cache, system, dalvik, internal SD card, all within TWRP as well as checking MD5 on the ROMs after they've been copied to my SDCard and am running the latest TWRP available for my phone. I have also tested this without restoring ANY data and using the packaged launchers and I get the same behavior. If I go back to a 4.1.1 ROM, everything is perfectly fine. This ONLY happens on the 4.2 ROMs available.
I'm looking for any help on getting this sorted not because it's a big deal but because it's driving me friggin' insane!
Re: [Q] ALL 4.2.2 ROMs hate my phone. Help thread.
Have you tried CWM Recovery yet? It's what I use and have literally tried every rom put there with no problems ever.
Sent from my SGH-I747 using xda premium
Jirv311 said:
I've tried multiple combinations of wiping cache, system, dalvik, internal SD card, all within TWRP
Click to expand...
Click to collapse
You don't mention it, but did you use the wipe option that is at the bottom left of the TWRP wipe menu screen? The scary looking one that says it's probably not needed?
I do that one every time.
I would restore to stock 4.1.1. Then flash TWRP's latest again and try one more time by flashing something mainstream like CyanogenMod 4.2.2.
Flashing stock ROM's has fixed a couple weird issues for me lately.
I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.
I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.
EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?
Jirv311 said:
I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.
I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.
EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?
Click to expand...
Click to collapse
Have you tried a different kernel? I run ktoonsez KT747 with Task's AOKP with awesome results. Nothing against Task's underwear kernel, but maybe the 4.2 version just doesn't like your phone.
Jirv311 said:
I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.
I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.
EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?
Click to expand...
Click to collapse
yes if you flash the 4.1.1 stock file through the desktop odin you will upgrade the bootloader , with the new boot loader everythime you reboot the phone with a custom recovery like cwm or twrp it will raise the flash counter. Here is what I would do. reboot to twrp , wipe data/factory reset , wipe cache wipe dalvic and wipe system. then go to advanced and reboot into bootloader/download mode. once in downlaod mode flash the rooted ics 4.0.4 rom with desktop odin, I was going to link the thread by mrrobinson but it seems someone un-stickied it so your going to have to try and find it.either go back to stock from sammobile.com and root it or get a pre-rooted file. once your back on stock rooted ics download goomanager from the play store. inside the goomanager click install open recovery script. this will install twrp on your phone. after that put the rom you want back on your and follow the op for that rom. do it exactly as it states.I reccomend task650's rom. If you still have a problem try a different kernel. Not all phones are the same, some phones wont even boot up with certain kernel's. hope this helps
edit here is the link http://forum.xda-developers.com/showthread.php?t=1739426
Intub8 said:
yes if you flash the 4.1.1 stock file through the desktop odin you will upgrade the bootloader , with the new boot loader everythime you reboot the phone with a custom recovery like cwm or twrp it will raise the flash counter. Here is what I would do. reboot to twrp , wipe data/factory reset , wipe cache wipe dalvic and wipe system. then go to advanced and reboot into bootloader/download mode. once in downlaod mode flash the rooted ics 4.0.4 rom with desktop odin, I was going to link the thread by mrrobinson but it seems someone un-stickied it so your going to have to try and find it.either go back to stock from sammobile.com and root it or get a pre-rooted file. once your back on stock rooted ics download goomanager from the play store. inside the goomanager click install open recovery script. this will install twrp on your phone. after that put the rom you want back on your and follow the op for that rom. do it exactly as it states.I reccomend task650's rom. If you still have a problem try a different kernel. Not all phones are the same, some phones wont even boot up with certain kernel's. hope this helps
edit here is the link http://forum.xda-developers.com/showthread.php?t=1739426
Click to expand...
Click to collapse
I just did exactly this just now and the same exact symptoms occur. Even after flashing ktoonz kernel. This is the weirdest thing I've ever dealt with.
Jirv311 said:
I just did exactly this just now and the same exact symptoms occur. Even after flashing ktoonz kernel. This is the weirdest thing I've ever dealt with.
Click to expand...
Click to collapse
yes that is very odd. If it works fine on stock or 4.1 rom's then it definatly not a hardware issue with the button. Im sorry man , I have no idea what it could be.
Yeah I'm confused as well. I just flashed the last CM10.0 4.1.2 and it runs flawlessly. Definitely a head scratcher.
I have downloaded the G2 V3 update.zip to my phone and have tried installing the zip via CWM. I followed instructions stating factory default first, then flash the update.zip, install the SU add-on 1, then factory default. When I reboot my phone I get the LG boot screen, afterwards my indicator lights both flash on, my phone vibrates and the backlight stays on but I get a blank screen. I left it like this for 20 minutes but it never continues. I have tried rebooting but it does the same thing. I have loaded my previous CM 10.2 Rom since. Tried repeating this process, get same results. Adding to this, when I load the add-on it does say there was a problem with Loki at the end.
Please help.
Are you coming from stock or were you on CM?
I always return to stock before changing roms,, I've heard of people having trouble going from CM to V3....
_________________
Beavers & Ducks!
Always wipe system, cache and dalvik-cache before flashing. I'd also suggest wiping the internal sd card as well. Always gives me the best results. I've jumped from ROM to ROM this way with no problems. :3
Sent from my LG-E988 using XDA Premium 4 mobile app
That has to be what it is, I am going from CM10.2 to this mod. I am going to try to go to stock and then message again my results. Thank you for replying to my message.
tobias87 said:
That has to be what it is, I am going from CM10.2 to this mod. I am going to try to go to stock and then message again my results. Thank you for replying to my message.
Click to expand...
Click to collapse
Yup, that is the issue. Those ROMs do not have stock kernel bundled and hence they do not boot when you come from CM or Carbon or Vanir to V3.
You have to go back to stock and then flash that.
Or there might be another way which might work and will spare you hassles of going back to stock and rerooting. Give it a go.
1. Download this kernel : http://forum.xda-developers.com/showthread.php?t=2363330
This kernel is for stock based ROMs.
2. Install V3 by following the procedure. After second factory reset, before rebooting, flash this kernel. And then reboot.
See if that is successful. It should be. (it will still take 4-5 minutes for first boot )
If not , you can always go back to CM and then go through whole going back to stock thing.
Got The thing to work by flashing the CWM recovery files in three parts. Then updated to V4 and SU. The only thing I can't seem to get working is the wireless reefer devices can connect but the receive no data.
Funkym0nkey said:
Yup, that is the issue. Those ROMs do not have stock kernel bundled and hence they do not boot when you come from CM or Carbon or Vanir to V3.
You have to go back to stock and then flash that.
Or there might be another way which might work and will spare you hassles of going back to stock and rerooting. Give it a go.
1. Download this kernel : http://forum.xda-developers.com/showthread.php?t=2363330
This kernel is for stock based ROMs.
2. Install V3 by following the procedure. After second factory reset, before rebooting, flash this kernel. And then reboot.
See if that is successful. It should be. (it will still take 4-5 minutes for first boot )
If not , you can always go back to CM and then go through whole going back to stock thing.
Click to expand...
Click to collapse
Swype decided to fill in an odd word for what I meant sorry. I meant wireless tether.
tobias87 said:
Got The thing to work by flashing the CWM recovery files in three parts. Then updated to V4 and SU. The only thing I can't seem to get working is the wireless reefer devices can connect but the receive no data.
Click to expand...
Click to collapse
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
Everytime I install a 4.4.2 ROM it works fine until I power-off completely. When I turn it back on the microphone and speakers stop working.
I can restart the phone and reboot to recovery and everything is fine.
Of course my phone is a d2att. I only seem to get it working again is when I restore a Nandroid backup of the stock ROM then reinstall the custom ROM.
Can someone tell me a permanent way to solve this problem so I can power off with my custom ROM?
diando said:
Everytime I install a 4.4.2 ROM it works fine until I power-off completely. When I turn it back on the microphone and speakers stop working.
I can restart the phone and reboot to recovery and everything is fine.
Of course my phone is a d2att. I only seem to get it working again is when I restore a Nandroid backup of the stock ROM then reinstall the custom ROM.
Can someone tell me a permanent way to solve this problem so I can power off with my custom ROM?
Click to expand...
Click to collapse
You really haven't given any information that would help to diagnose your issues. Without information it's pretty much impossible to help you.
1.) What ROM?
2.) Fully wipe?
3.) Have you made any modifications that could conflict?
4.) Ect...
task650 said:
You really haven't given any information that would help to diagnose your issues. Without information it's pretty much impossible to help you.
1.) What ROM?
2.) Fully wipe?
3.) Have you made any modifications that could conflict?
4.) Ect...
Click to expand...
Click to collapse
I've installed Validus, C-ROM, CM11, AOKP.
None of them seem to have sound working on restart. I've tried re-flashing 4.1.1 stock via Odin then reinstall those ROMs but it never seem to work. Still have that problem after it is turned off.
I've fully wiped the phone clean every time.
Sound on the stock ROM works fine.
Not really sure what to tell you as you seem to be one of the only users posting this type of issue as far as I can see. Maybe someone that has the same issue will chime in here.
task650 said:
Not really sure what to tell you as you seem to be one of the only users posting this type of issue as far as I can see. Maybe someone that has the same issue will chime in here.
Click to expand...
Click to collapse
Also other notes
Using the Google Experience Launcher when I use the hotword "OK Google" the beep sound is scratchy.
Made another discovery, @task650, I flashed the stock recovery while running C-ROM and wiped the cache and it restored sound every time - though wiping the cache in CWM did nothing. I'm going to try TWRP now.
EDIT
--
TWRP wipe doesn't work but it does seems like there's a problem with how the cache works on my phone. Hopefully 4.4.3 based roms won't have the same issues but I will stick to stock recovery for now.
Is there any way to get a CWM flashable zip of the stock recovery or nandroid file?