Revamped the entire OP to make it relevant for current roms.
Many users of the Epic 4g Touch have reported various GPS inconsistencies. While this seems to happen more frequently on AOSP-based ROMs (CyanogenMOD, PAC-man, Evervolv, AOKP, etc), it has been reported on TouchWiz-based ROMs as well. Below are a few tips and tricks to help fix your GPS.
FIRST: You will need the necessary tools to troubleshoot the problem.
Google Maps - The app we will use to determine if GPS works properly or not.
GPS Status (Optional) - Provides additional information about GPS performance. This shows how many satellites are in view, coordinates, heading, and other useful information as well. This can help to confirm wether you have a GPS problem or are just in an area without GPS reception.
SECOND: You will need the tools to fix the problem.
- Root-capable file browser (ES File Explorer is my personal preference)
- Mobile ODIN (Free version is available on XDA, but Pro is well worth it, as well as supporting Chainfire, one of the most respected devs in the Android community)
THIRD: You will need some files saved to your sd card. These will be flashed in recovery or Mobile ODIN.
- The EL26+CWM recovery kernel.
- Any Jellybean ROM you want to run.
***For TouchWiz ONLY* Agat's 0.3.0 GB27 Kernel with tREC custom recovery.
- A working GPS.conf (explained later)
- Goddly's ComaDose tweaks (not required if you use a standalone GPS.conf, but highly recommended. See his thread for details.)
FOURTH: You will need these files on your sdcard to temporarily return to stock if needed.
- The EL29 CWM5 Directboot Kernel
- The EL29 Tempboot ROM
METHODS:
I will post each method of fixing GPS, in order of time investment. Test GPS with Google Maps (and optionally GPS Status) after EACH METHOD. Please provide feedback on which method worked for you so that I may improve this guide further.
Method 1 - GPS Toggle
Try this first. It only takes about 10 clicks to do the whole thing, and it saves you from having to flash anything if it works.
1. Close Maps and any other location aware apps. Make sure to clear them from Recents to ensure that they are fully closed.
2. Go the your Location tab under Settings. Toggle GPS satellites off and on, then toggle Location as well (System Settings>Location Access>Access to my Location). This should result in a popup asking if apps can have your permission to use GPS.
Method 2 - New GPS.conf
All thanks to Goddly for allowing me to use his gps.conf.
Sometimes, the GPS.conf file on your phone can become corrupted or otherwise unusable. This will prevent you from locking on to any satellites, even though you may have one (or several) in view.
1. Make sure you have a working GPS.conf on your phone. This can be a standalone GPS.conf like the one attached to this post (extract the zip first!), or it can be one contained in a tweak package such as Goddly's ComaDose v1.4
2. Copy & paste the working gps.conf into /System/App using your root file browser.
3. Set permissions to the gps.conf to 0777 (rwxrwxrwx)
4. Reboot.
5. After booting, toggle Location (triggering the popup).
Method 3 - Lock on Stock
This is a tried-and-true method that was most frequently used in the early days of CM10. It is usually not needed anymore, but I am keeping it in just in case.
1. In Mobile ODIN, flash the EL29 CWM5 Directboot kernel.
2. Reboot, you should automatically wind up in recovery. If you do not go to recovery, pull the battery, wait 10-15 seconds, replace the battery, and hold vol+ and power.
3. Flash the EL29 Tempboot ROM (This will be in the Multiboot folder on your SD card, assuming you followed the instructions in the link above.)
4. You should automatically boot into stock EL29 Gingerbread.
(Optional) 4 1/2. Update Profile and PRL (if desired, you can't do this on AOSP so you might as well do it now)
5. Open Google Maps and get a GPS lock (you will likely need to be outside to get a good lock). Sometimes it helps to navigate to a random place.
6. ***WHILE YOU STILL HAVE A GPS LOCK***, power down the phone, then hold vol+ and power until you boot to recovery.
7. In recovery, Wipe Cache, Wipe Dalvik Cache.
8. Flash your ROM of choice.
9. Reboot.
Please reply to this thread with any questions/issues/feedback.
Thanks....will try it.
I havent multibooted this device.... Do u just make a folder on internal sd or do i need to..... Nevermind i guess i should google first
Sent from an Apple killing JellyBean
moparfreak426 said:
I havent multibooted this device.... Do u just make a folder on internal sd or do i need to..... Nevermind i guess i should google first
Sent from an Apple killing JellyBean
Click to expand...
Click to collapse
Detailed instructions are in the tempboot link in the OP.
ok... i read up on it and stuff.... i cant mount phone to pc... idk why so i put multiboot on sd card and moved it to root of device..... its froze moving the system.ext4.img......... should i be worried? phone is so laggy... hit power button to turn on off screen... response = roughly 10 seconds later
---------- Post added at 11:57 PM ---------- Previous post was at 11:43 PM ----------
Phone completely froze and reset.... So no gps lock for me:/
Sent from an Apple killing JellyBean
moparfreak426 said:
ok... i read up on it and stuff.... i cant mount phone to pc... idk why so i put multiboot on sd card and moved it to root of device..... its froze moving the system.ext4.img......... should i be worried? phone is so laggy... hit power button to turn on off screen... response = roughly 10 seconds later
---------- Post added at 11:57 PM ---------- Previous post was at 11:43 PM ----------
Phone completely froze and reset.... So no gps lock for me:/
Sent from an Apple killing JellyBean
Click to expand...
Click to collapse
if you didnt get a good copy your multiboot wont work. Try downloading the file directly to your phone, and unzip it to the root of your internal with zarchiver.
Edit: apparently zarchiver can't extract to the root, or the system.IMG won't copy to the multiboot folder correctly. Try copying it again with your computer. Make sure it's on the root of your internal, not in /sdcard/ or on your external.
Failing that, nandroid your cm10, flash a tw-based gingerbread ROM with cwm5 recovery, get a GPS lock, reboot to recovery, flash cm10, reboot recovery, then restore your nandroid while on cwm6
Edit 2: what ROM are you on when trying to mount USB storage? It won't work on tw ICS or jb, and it might be disabled on aosp (Settings>storage > menu > USB computer connection > USB mass storage)
I was wanting to try this, but had a couple questions before I tried it:
Is the wipe of /data really necessary, or does it just help things run better?
Will this work on CWM6?
Also, with the PACman builds after 1/12, you don't have to flash Paranoid Preferences seperately.
Lt_data said:
I was wanting to try this, but had a couple questions before I tried it:
Is the wipe of /data really necessary, or does it just help things run better?
Will this work on CWM6?
Also, with the PACman builds after 1/12, you don't have to flash Paranoid Preferences seperately.
Click to expand...
Click to collapse
1: Technically no, but a /data wipe is always recommended. If you have issues after this procedure, wiping /data is your first step to fixing them.
2: You start out on the cwm6 included in our AOSP kernel. You flash the el29 cwm5 directboot kernel with mobile odin, then flash the el29 multiboot (which requires the el29 kernel). When you are done with your prl updates/gps fix/dialer codes, you then reboot recovery and flash your AOSP 4.1 again, which puts you back on the AOSP kernel that includes cwm6.
Updated OP.
Does it matter that AOSP ROMS now use /sdcard instead of /emmc for the internal card? I tried the steps (without any clearing of cache or data, doh) and it just bootlooped. I was just wondering if that would be a factor?
Re: [FIX][JB]GPS Workaround for AOSP-Based 4.1.2
Lt_data said:
Does it matter that AOSP ROMS now use /sdcard instead of /emmc for the internal card? I tried the steps (without any clearing of cache or data, doh) and it just bootlooped. I was just wondering if that would be a factor?
Click to expand...
Click to collapse
Talking about the multi boot I assume? It goes in /sdcard/. This is the root of the phone's internal storage when mounted as USB mass storage via PC.
I don't even remember when AOSP last used /emmc/...July I think? Alpha CM9 I think. Before Chris41g started releasing like 5 test builds a day. At any rate, long before jellybean, which is what this guide is for.
And don't forget to wipe the things, or you will have problems.
Sent from my SPH-D710 using xda app-developers app
Adreaver said:
Talking about the multi boot I assume? It doesn't go in /sdcard or /emmc. It goes on the root of your internal storage.
And don't forget to wipe the things, or you will have problems.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
/sdcard IS the internal storage. The actual SD card mounts to /external_sd. I realized this after 45 minutes of trying to make a multiboot folder in / unsuccessfully.
Lt_data said:
/sdcard IS the internal storage. The actual SD card mounts to /external_sd. I realized this after 45 minutes of trying to make a multiboot folder in / unsuccessfully.
Click to expand...
Click to collapse
*facepalm* You are correct. My mistake.
I was thinking root of internal storage when phone is mounted via USB. I could never get the multiboot to extract entirely on the phone, it would just freeze for a while, then force close ES, then eventually reboot.
The correct path (when flashing) is /sdcard/multiboot/EL29/Boot_EL29.zip. So make sure your install matches this, or you will have problems.
Tried it again, this time via Mobile Odin instead of desktop Odin and it worked great! Updated my modem to FL24 and then updated PRL and profile. Thanks for the instructions and the help!
Hello, I have tried fixing my gps lock with this method three times. I even "one clicked" back to EL29 rooted for a fresh(er?) start. While in the EL29 temp boot, I can get either a 9/9 or 10/10 GPS lock( all three attempts), power down while in the lock (using google navigation), and follow the rest of the steps. Once I flash back to my CM10.1, or a clean install of 10.1, I start up GPS Status, and it tells me 0/2 sattelites locked. What is odd is that the two it tries to connect to changes every second or so to another random sattelite. So I see something like 21->03->18->12->30->14->22->32 etc. Any tips? Would flashing a new modem help? I originally had FL24 (i think) when I tried this method the first two times, and EL29 the third time (because Odin One Click reset it back to EL29).
EDIT: oh I realize this method works for 4.1.2, but would it also work for CM10.1, which is 4.2?
chaosacolyte said:
Hello, I have tried fixing my gps lock with this method three times. I even "one clicked" back to EL29 rooted for a fresh(er?) start. While in the EL29 temp boot, I can get either a 9/9 or 10/10 GPS lock( all three attempts), power down while in the lock (using google navigation), and follow the rest of the steps. Once I flash back to my CM10.1, or a clean install of 10.1, I start up GPS Status, and it tells me 0/2 sattelites locked. What is odd is that the two it tries to connect to changes every second or so to another random sattelite. So I see something like 21->03->18->12->30->14->22->32 etc. Any tips? Would flashing a new modem help? I originally had FL24 (i think) when I tried this method the first two times, and EL29 the third time (because Odin One Click reset it back to EL29).
EDIT: oh I realize this method works for 4.1.2, but would it also work for CM10.1, which is 4.2?
Click to expand...
Click to collapse
sorry for the delayed response. This method should work for CM10.1, but I have not tested it personally. Post your results and let everyone know if it works for you.
Re: [FIX][JB]GPS Workaround for AOSP-Based 4.1.2
I did OP fix with el29 with no success. (Used to work for me)
However..
After trying a few ROMs. I noticed I could update prl/profile in jellyverse v.4 (FL26) and get a lock. At this point curiosity struck so I Mobil Odin cwm el26, wiped data/cache/dalvik **skipped format all zip** and I flashed a JB aosp ROM and ICS modem. Long behold I can get GPS locks on my favorite ROM now.
So if el29 doesn't work for you (It did at one point for me but not anymore) try this method. It worked for me. :thumbup:
GL
Sent from my SPH-D710 using Tapatalk 2
Re: [FIX][JB]GPS Workaround for AOSP-Based 4.1.2
Gazzuk said:
I did OP fix with el29 with no success. (Used to work for me)
However..
After trying a few ROMs. I noticed I could update prl/profile in jellyverse v.4 (FL26) and get a lock. At this point curiosity struck so I Mobil Odin cwm el26, wiped data/cache/dalvik **skipped format all zip** and I flashed a JB aosp ROM and ICS modem. Long behold I can get GPS locks on my favorite ROM now.
So if el29 doesn't work for you (It did at one point for me but not anymore) try this method. It worked for me. :thumbup:
GL
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Never use a format all script with this fix. It will cause problems.
Better yet, never use a format all script ever, unless specifically directed by the OP.
Sent from my Epic 4g Touch on PAC-man v19.3
Re: [FIX][JB]GPS Workaround for AOSP-Based 4.1.2
Adreaver said:
Never use a format all script with this fix. It will cause problems.
Better yet, never use a format all script ever, unless specifically directed by the OP.
Sent from my Epic 4g Touch on PAC-man v19.3
Click to expand...
Click to collapse
Thanks for the tip, I was using it as a shortcut... whoops
sent from my ET4G on Paranoid Android using XDA Premium HD in hybrid mode
Adreaver said:
sorry for the delayed response. This method should work for CM10.1, but I have not tested it personally. Post your results and let everyone know if it works for you.
Click to expand...
Click to collapse
sorrry for my late reply too, . The problem seems to be in the CM10.1 rom itself, because there are others in the thread (edit: the "wild for the night CM10.1 thread) that have the same situation as me. Actually the gps is locking correctly, with an error of 3 meters, its just GPS Status and other gps apps (like Ulysse) can not report correct lock information. Instead it shows spazzing attempts to lock to different sattelites. Hope this info works!
tl;dr: GPS locks even though apps dont report it locking in CM10.1
Re: [FIX][JB]GPS Workaround for AOSP-Based 4.1.2
chaosacolyte said:
sorrry for my late reply too, . The problem seems to be in the CM10.1 rom itself, because there are others in the thread (edit: the "wild for the night CM10.1 thread)... tl;dr: GPS locks even though apps dont report it locking in CM10.1
Click to expand...
Click to collapse
That would explain why I hadn't heard... I haven't been checking that one, I was on phantom's cm10 and hadn't been following WftN
Sent from my SPH-D710 using xda app-developers app
Related
Since Spacemoose has a GSM release approaching, I'm going to remove the download links here. (Also because apparently people are still attempting to flash this...) If and when I am contacted by DiP7 I will reopen this thread and add any links he wants me to add.... Or it can stay closed and he can start a new one (which is what I would hope he does.) I'm leaving the rest of the content here for reference only.
**READ ENTIRE FIRST POST BEFORE FLASHING**
This is an Alpha build. Almost nothing works at the moment. Don't expect a golden daily driver... This aint it. If you find a download link throughout this thread, don't flash it, as I can't promise anyone will help you un(soft)brick your device.
Let's start this with : I take zero, zilch and no responsibility for anything you do to your device using anything from this thread.
If space alien ninja cows come down and eat it because they want to taste honeycomb, your fault, sorry.
There have been zero reports of anyone "hard bricking" their device, but again, I'm not responsible if you become the first.
I also take no credit for any of the work, I've only compiled what I have found so far.
I also can't stress this enough... This is a VERY EARLY STAGE of the port. ALMOST NOTHING WORKS. Any updates that take place will need to be documented within this post. I'm willing to keep track of all this, but *I AM NOT A DEV.* The original dev of this port is from another website, dsf767 seems to be in contact with him however. here at XDA!
**Please see bottom of this post for change log**
Various vidoes have been made, but the quality of this one is really nice. Thanks museboy!
This is a direct port of Spacemoose's Alpha v.040211 release. Not much works.
In Spacemoose's thread, credit is given to
[*] A russian-language GSM port attempt based on this project. (Thanks, dsf767.)
Click to expand...
Click to collapse
It appears as though someone DiP7 is attempting to port Spacemoose's project to a GSM device. They also appear to have had mild success in doing so, and I'd like to start a thread to track and follow any progress anyone else may be having with flashing this rom/kernel.
[*] System must already be converted to EXT4. This can be done by various methods, flashing the Overcome rom/kernel will do it.
[*] Tab confirmed to charge while off and reports of lockscreen charging have been made.
I'm unsure if anyone has had any success other than the OP Cal-El has gotten it to boot! Directions appear to be as follows:
BACKUP EVERYTHING. Everything? EV-ER-Y-THING. Especially your internal SD card. There have been reports (that I've experienced) of your internal SD card getting wiped in either going to or coming from Honeycomb. (It usually requires a repartition to go back... so yeah, that'd do it.)
Did you back everything up? You will loose any information on your internal SD card coming back to normal from this build.
Download Rom to EXTERNAL SD:
Download Kernel to EXTERNAL SD:
Did you back up your internal SD card? What about external? Last warning. Next person to complain about their internal SD card get's the bonk.
Wipe Data/Factory restore
Wipe Cache Partition
Wipe Delvik Cache
Flash honeycomb rom using CWM (This seems to have only been tested and confirmed from the Overcome modified CWM, although any should work in theory.)
Reboot into new RED CWM.
Flash kernel using RED CWM
Reboot into new ORANGE CWM.
Wipe data/Factory reset
Wipe both caches.
Flash honeycomb rom using the ORANGE CWM.
There is no boot screen after the Galaxy Tab logo screen, just a black screen. Wait at least 5 minutes for it to boot. If it doesn't after 10, something went wrong.
If this fails, attempt to go back to stock by flashing p1_hidden.pit and any of Roto's stock roms/firmwares. From here it has been confirmed to work if you flash the Overcome rom/kernel before moving to the Android 3.0 rom/kernel. (Thanks Cal-El!)
This process must also be used to coming back from this
Honeycomb build. You will loose all information on your internal SD card.
I told you to back it up.
Taken from Alterbridge's Overcome Rom posting (which should fix any hangups while flashing to/from this Honeycomb)
alterbridge86 said:
IF your Tab does not boot after flashing the kernel and hangs at the Samsung Galaxy Tab screen, you must follow the following procedure
Get a stock rom package (any of Rotohammer's firmwares will work)
Get P1_add_hidden.zip from this post and extract the P1_add_hidden.pit file
Using Odin 1.7, put stock rom (Roto-JME-Full-v4.tar for example) in PDA slot.
Put P1_add_hidden.pit in Pit slot
Check repartition box
Put Tab in download mode by holding Volume Down and Power, connect to the computer, and press start.
After this, the Tab will reboot normally. Shut it down and return to download mode.
Open Odin 1.7 and reconnect the Tab.
In the PDA slot, choose the Overcome Kernel v2.0 tar file for use with Odin. Press start
It will flash the kernel then reboot. Upon reboot, you should hear the sexy robot voices informing you of the status of the EXT4 conversion.
Once done, the Tab will boot normally. At this point you can load Overcome Rom (or any other Rom of your choosing)
Click to expand...
Click to collapse
[*]Remember, No wi-fi, no 3g, no phone calls, nothing. This is a test port. YOU HAVE BEEN WARNED OVER 5 TIMES NOW, no complaining about it later.
[*]If your internal SD card reads ~220 MB after coming from this ROM to anything else, you didn't read my post... Try again.
[*] Mirrors :
*Update on driver work for wi-fi (4/12): http://forum.xda-developers.com/showpost.php?p=12816258&postcount=224 (Thanks DemonGloom for translating)
*Also added video to OP (Thanks to museboy!)
the wife is russian. may attempt tonight when I get home. thanks for the heads up
Just try to make sure that any actual changes to the base system build are reported in the other thread as well so we can all stay on the same page.
This is a brilliant find! Downloading now to test this baby out
Is the rom and kernel in the zip or are there 2 different files to download?
Sent from my GT-P1000 using XDA Premium App
I tried flashing this using the mothod above and the methon on the russian site but I can't get it to work.
It keeps messing up my /data partition. After flashing the ROM CWM always fails to mount the /data partition.
I'm going back to overcome .
I already got a blank screen and then a broken internal sdcard error. Had to find an odin flash that repartitioned.
Ill be willing to do it all again as soon as there is wifi. At least this time I'll make sure to back up my internal sdcard.
-RioT- said:
I already got a blank screen and then a broken internal sdcard error. Had to find an odin flash that repartitioned.
Click to expand...
Click to collapse
Just trying to keep track of this all... Are you saying you got it to run successfully but had to repartition to go back? Or did you have to repartition to get it to run?
Adding in the hidden_pit to the process seems simple enough.
-RioT- said:
Ill be willing to do it all again as soon as there is wifi. At least this time I'll make sure to back up my internal sdcard.
Click to expand...
Click to collapse
Step #1
GANJDROID said:
This is a brilliant find! Downloading now to test this baby out
Is the rom and kernel in the zip or are there 2 different files to download?
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
They both appear to be contained within the same zip file, much like the Overcome rom. Best guess, can't verify as I'm on a work mac at the moment.
btyork said:
They both appear to be contained within the same zip file, much like the Overcome rom. Best guess, can't verify as I'm on a work mac at the moment.
Click to expand...
Click to collapse
Yeah, my mistake. Got confused about the reflash with new kernel/cwm.
So we:
Backup
Wipe everything
Flash
Wipe
Flash
Reboot
Sent from my GT-P1000 using XDA Premium App
There Directions are directly from DiP
Originally Posted by DiP7
- the first step (the file system should already be ext4) - flash honeycomb (Android3.0_by_DiP_signed _narod.yandex.ru/disk/9317202001/Android3.0_by_DiP_signed_040411_235124.zip
- the second step (to flash my kernel dl.getdropbox.com/u/937719/Recovery_install_pda1.4Ghz_CWR_v_2.1.0.zip) go to the recovery and make the wipe data/factory reset
- The third step - go to recovery and flash again android 3.0
GANJDROID said:
Yeah, my mistake. Got confused about the reflash with new kernel/cwm.
So we:
Backup
Wipe everything
Flash
Wipe
Flash
Reboot
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
So far that's what I've gathered, I have yet to actually test this process.
The poster above appears to have mentioned something about repartitioning, which isn't a big deal, just flash the hidden_pit.
My best guess is to flash that pit after the second wipe with Odin. But I CAN NOT verify that.
It seems obvious you would need to repartition to go back though.
I would try and flash it all via cwm, but I'm unable to download the kernel. Can anyone mirror it please?
Away from my laptop for the next few hours so I'm unable to try with Odin.
GANJDROID said:
I would try and flash it all via cwm, but I'm unable to download the kernel. Can anyone mirror it please?
Away from my laptop for the next few hours so I'm unable to try with Odin.
Click to expand...
Click to collapse
Recommendations as to a site to mirror it on? I don't do a lot of hosting.
Here are some Mirrors you can put them in the OP of the Rom and Kernel
ROM: http://www.megaupload.com/?d=RC6WF2PG
Kernel: http://www.megaupload.com/?d=GP58GAOE
Anyone have luck getting HC port running o the tab yet and if so can we get a clear how to in place ?
Thanks in Advance =)
btyork said:
Recommendations as to a site to mirror it on? I don't do a lot of hosting.
Click to expand...
Click to collapse
I'd say Mediafire or Megauload are the best, IMHO.
Big thanks for the mirrors.
For now, FML. Now got 8% battery left *sigh* Ill have to wait for some Honeycomb love.
Sent from my GT-P1000 using XDA Premium App
Updated with Kernel and Mirror(s) for both Rom and Kernel.
clockedtouch said:
Anyone have luck getting HC port running o the tab yet and if so can we get a clear how to in place ?
Thanks in Advance =)
Click to expand...
Click to collapse
The clear "how to" is in the first post... If you can't understand those directions, you really shouldn't be flashing this.
btyork said:
The clear "how to" is in the first post... If you can't understand those directions, you really shouldn't be flashing this.
Click to expand...
Click to collapse
Thats why i dont post much simple remarks like that make members not want to contribute ...
You could of simply stated that the "how-to" was updated .. but thanks for your quick response anyway
clockedtouch said:
Thats why i dont post much simple remarks like that make members not want to contribute ...
You could of simply stated that the "how-to" was updated .. but thanks for your quick response anyway
Click to expand...
Click to collapse
I actually haven't updated the how-to since the original post... It wasn't meant to be rude, it's just how it is. I don't want people bricking a 600 dollar tab because they think this is a fully functional honeycomb port.
You'd also be surprised how many people post that kind of question without any understanding of what ADB even is.
I have a stock glide on gingerbread and want to test out the CM10 in the development section.
If anyone could help with a step by step guide it would really be appreciated. I know there are
other posts which describe each part but I am having trouble find them. Thank You.
EGGrollBEAST said:
I have a stock glide on gingerbread and want to test out the CM10 in the development section.
If anyone could help with a step by step guide it would really be appreciated. I know there are
other posts which describe each part but I am having trouble find them. Thank You.
Click to expand...
Click to collapse
Odin stock ics leak
Odin CWM recovery
wipe data
wipe cache
wipe dalvik cache
format data
format cache
format system
choose zip and flash
Flash Gapps!
from http://forum.xda-developers.com/showthread.php?t=1940677 OP
Thank you for your reply. I am a total noob. how do I use Odin??
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
BEFORE YOU START. I AM NOT RESPONSIBLE FOR ANY DAMAGE OR DATA LOSS ANY OF THESE STEPS MAY CAUSE. ALWAYS FLASH AT YOUR OWN RISK.
Note: Suggestions, comments & questions are welcome. Will improve as much as needed.
1. BACKUP. There are many apps you can find to backup any data. Backup all data you'll want to keep until you're 100% satisfied then move it to a folder on your PC. Personally, I use Titanium Backup Pro and backup everything to Google Drive.
2. DOWNLOAD. A GB kernel, rooted AT&T ROM/Rogers ROM, stock ICS leak, CWM, and then go to the CM10 thread and grab the latest build of the ROM & Gapps. So you should have 6 files total. To make your life easier, put them all in 1 folder.
3. ROOT. Turn off your phone. Hold the top part of the volume rocker and turn on the phone. It should boot into download mode if done correctly. Connect phone to PC via USB. On your PC, install & open Odin. Click on PDA and locate your GB kernel. Then click start & wait. If successful, you should see green and you'll be rooted. I believe whenever you use ODIN, it is called a 'flash.' I hope someone will correct me if I'm wrong. Anyway, go back into download mode and now place the rooted ROM in the PDA section followed by clicking start again. When the phone is done booting, go to the Play store and get Superuser app. This allows you to give permission to operations that require root. Make sure it is updated!
4. CLEAN. Now you'll want to wipe your phone to minimize the chances of anything going wrong. Instead of holding the top part of the volume rocker, you'll hold the bottom. Then hold it as you start the phone. This is the stock recovery menu. I don't remember precisely what the options are called but you will want to wipe cache, dalvik, data and system.
5. UPDATE OS. Time to open up that stock ICS leak. When open, it should appear similar to Odin. Make sure your phone is in download mode again, connected via USB and click start again. You'll notice that your phone might take a while to boot up. It'll be updating files and apps so be patient.
6. CWMR. After it's all booted up, time to go back to download mode again. In ODIN, you'll want to click on PDA again and this time flash the CWMR file. Click start and you're done in no time.
7. CLEAN AGAIN. Now you'll want to turn off your phone and boot the phone holding the bottom of the rocker. You'll boot into CWMR. Time to wipe and format again. You'll find the first 2 wipe options on the first page. The wiping of dalvik cache will be in the ADVANCED menu. Then you'll want to go into the MOUNTS AND STORAGE menu. Format system, cache & data.
8. CM10. Now while still in CWMR, you'll need to go into the MOUNTS AND STORAGE menu and select MOUNT USB STORAGE. You'll want to connect your phone to your PC with the USB. Place the CM10 and Gapps files in the main directory of your PHONE'S INTERNAL STORAGE. Select UNMOUNT on your phone, disconnect from USB and now you'll want to go to the option INSTALL ZIP FROM SDCARD.. then go to the CHOOSE.. option and select the final fruit of your labor, CM10. When it's done doing it's thing, REBOOT SYSTEM. Be patient and let everything load.
9. GAPPS. After everything has loaded, you want to turn off the phone and boot into CWMR one last time. Go to INSTALL ZIP FROM SDCARD, CHOOSE ZIP and flash that Gapps file. Then REBOOT SYSTEM.
10. RESTORE. Reinstall the app you used to backup your stuff, move your backup files you put on the PC back to it's rightful place and restore. You should be good to go.
rogernizzLe said:
BEFORE YOU START. I AM NOT RESPONSIBLE FOR ANY DAMAGE OR DATA LOSS ANY OF THESE STEPS MAY CAUSE. ALWAYS FLASH AT YOUR OWN RISK.[/SIZE]
If any of the more experienced people find errors in this "guide", please let me know.
1. BACKUP.
.
.
.
Click to expand...
Click to collapse
Thank you for doing this!
Just checking - is there not a thread / guide for this elsewhere already? (Or am I confusing versions - not for the first time, with xda-developers!)
Suggestions:
- move this to the start of a new thread where you can reserve the first 3 posts, you can update/edit it, etc.
1. BACKUP:
- it would be useful to mention CWMR backup. (i.e. Botch it, restore the image, try again.)
- I like not leaving people hanging and at least mentioning TB as you have so they have a search path to follow. It would be worth mentioning that TB Free will be 'good enough' to keep them safe (one time) through this process. [But long term / good app / scheduling makes TB Pro worthwhile.]
- Making TB and CWMR a link would be useful, and not just a link to the 'product' page, but link to a thread that describes how to do so. 'Product' links will be contained within them. It's all very well to get a link to what a beastie is, but frequently knowing what it is, and how to put it into practice are two different things. Linking to a thread of the latter type would be the useful one.
3. ROOT
- one of the problems when talking about ODIN is the perception left that it is a single thing. So saying 'ODIN (PC)' would be useful here. Whether you point out that it talks to the ODIN (client?) already built in to the PDA is up to you.
4. UPDATE OS:
- don't you want to be talking about the alpha/beta dudejb version here?
5. CWMR
- wouldn't you want to do this first? See Backup comments, above.
- is this even necessary? It's a VERY GOOD IDEA, but is CWMR needed to run the phone 'stock' (CM10)?
7. CM10
- links / explanations are going to be useful here.
- e.g. There's a lot of talk of subsequent steps, such as backlight fix. You might want to note such is already built in, or not. (As people read they come across these additional fixes, and it's not always apparent that months later someone built the fixes in already. It's easy to go in circles trying to get a coherent, whole, current, view of the world.)
SD Card management - first you TB Backup, then you wipe the SD Card (or so a quick glance appears). I know you haven't actually said that, but some explicit clarity may be helpful.
Thanks for the suggestions and good question. I don't think there are any guides out there.. but this is just from how I did it. Tried to make it as simple as I could without adding branching steps. Also, it's very narrow because I can only speak on behalf of the what worked for me. If there's a big need for this to be in a thread of it's own, I'll gladly make one.
-I didn't mention CWMR backup for two reasons. I didn't use it and I don't rely on it. Perhaps I should mention it anyway though regardless.
-Never used dudejb's version so I didn't list it.
-Needed CWMR at that point to install CM10 & Gapps zips. I think you can also use Odin but doing it via CWMR gives him a chance to familiarize himself with what he'll be using to flash future versions.
-Didn't put links to CM10 since he already knows where it is and can most likely read the fixes & not-fixed list himself.
Thanks RogerNIZZLE I appreciate the guide and I believe a lot of other ppl will too.
There is one hiccups i'm coming across. After I wipe, data, cache, dalvik cache,
I **format data, format cache, format system** then when it reboot and it just stays at the
start up screen that shows SAMSUNG. I let it sit for 5 but nothing happens, its still
on SAMSUNG. I've repeated the steps a few times? Is there any suggestions on what I can do?
Hm. Do steps 4, 5, 7, 8, 9. Sorry! All hope is not lost.
rogernizzLe said:
Hm. Do steps 4, 5, 7, 8, 9. Sorry! All hope is not lost.
Click to expand...
Click to collapse
Do steps 4,5 and then copy the cm10 and gapps to you phone internal memory. Then follow step 6. Lastly install cm10 and gapps together and reboot you phone.
Sent from my SGH-I927
@roger:
You should start a thread, and I'll request to get it stickied. This could help a lot of new users.
One thing I would add - before flashing ICS, wipe system data cache dalvik (either with stock recovery or cwmr). Then boot into download and flash ICS.
Okie dokie, I will do this after work.
EGGrollBEAST said:
I have a stock glide on gingerbread and want to test out the CM10 in the development section.
If anyone could help with a step by step guide it would really be appreciated. I know there are
other posts which describe each part but I am having trouble find them. Thank You.
Click to expand...
Click to collapse
i suppose u already know that you need a rooted phone before rom flashing is possible. what i did was to flash ics leak using clockwork recovery and then cm10.
IS ANYBODY AWARE THAT THERE IS NO OFFICIAL CM10 NIGHTLY ON GET.CM??? Please stop telling people to look there!
bs27975 said:
Thank you for doing this!
4. UPDATE OS:
- don't you want to be talking about the alpha/beta dudejb version here?
Click to expand...
Click to collapse
How did I get a version? Not sure what is meant by that?
JB
C3LLxM8 said:
IS ANYBODY AWARE THAT THERE IS NO OFFICIAL CM10 NIGHTLY ON GET.CM??? Please stop telling people to look there!
Click to expand...
Click to collapse
Did you know you don't have to tell at us... once you learn that. I'd like to say there won't be an official cm10 because the official cm secs think our phone runs on different hardware than it actually does and thinks they can get the phys. keyboard working. You should thank dman for even getting cm9 and beta cm10 where they are.
Sent from my SGH-I927 using xda app-developers app
Rawr0w0 said:
Did you know you don't have to tell at us... once you learn that. I'd like to say there won't be an official cm10 because the official cm secs think our phone runs on different hardware than it actually does and thinks they can get the phys. keyboard working. You should thank dman for even getting cm9 and beta cm10 where they are.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Yes dman should be thanked, so hard his thanks gland fails.
Official CyanogenMod is not being made because -we- have different hardware than the other SGSII range of phones.
So yeah. No use pointing at get.cm
In other news, these instructions, amazing.
Sent from my SGH-I927 using xda premium
I take to credit for the work on the various links i'll post. (I WONT BE HELD RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE)
1. In order to get CM10, first get instructions on rooting(if you have root,SKIP) via http://forum.xda-developers.com/showthread.php?t=1378082
2. When you have gotten root, flash CWMR via http://forum.xda-developers.com/showthread.php?t=1458153 or http://forum.xda-developers.com/showthread.php?t=2007198
(MAKE SURE YOU DO A NANDROID BACKUP AFTER YOU SUCCESSFULLY FLASH CWMR)
3. Next step is to flash ICS leak UCLG9 via http://forum.xda-developers.com/showthread.php?t=1841502 (could not find thread for CWM flashable UCLJ3)
4. Once you are now on UCLG9, you can now flash CM10 by Dman.
If i helped, please hit thanks.
Sent from my super SGH I927(Flashed almost all custom Roms). Currently on Dmans CWM flashable UCLJ3
I maybe JM but really XPerienced.
BEFORE YOU START. I AM NOT RESPONSIBLE FOR ANY DAMAGE OR DATA LOSS ANY OF THESE STEPS MAY CAUSE. ALWAYS FLASH AT YOUR OWN RISK.
Note: Suggestions, comments & questions are welcome. Will improve as much as needed.
1. BACKUP. There are many apps you can find to backup any data. Backup all data you'll want to keep until you're 100% satisfied then move it to a folder on your PC. Personally, I use Titanium Backup Pro and backup everything to Google Drive.
2. DOWNLOAD. A GB kernel, rooted AT&T ROM/Rogers ROM, stock ICS leak, CWM, and then go to the CM10 thread and grab the latest build of the ROM & Gapps. So you should have 6 files total. To make your life easier, put them all in 1 folder.
3. ROOT. Turn off your phone. Hold the top part of the volume rocker and turn on the phone. It should boot into download mode if done correctly. Connect phone to PC via USB. On your PC, install & open Odin. Click on PDA and locate your GB kernel. Then click start & wait. If successful, you should see green and you'll be rooted. I believe whenever you use ODIN, it is called a 'flash.' I hope someone will correct me if I'm wrong. Anyway, go back into download mode and now place the rooted ROM in the PDA section followed by clicking start again. When the phone is done booting, go to the Play store and get Superuser app. This allows you to give permission to operations that require root. Make sure it is updated!
4. CLEAN. Now you'll want to wipe your phone to minimize the chances of anything going wrong. Instead of holding the top part of the volume rocker, you'll hold the bottom. Then hold it as you start the phone. This is the stock recovery menu. I don't remember precisely what the options are called but you will want to wipe cache, dalvik, data and system.
5. UPDATE OS. Time to open up that stock ICS leak. When open, it should appear similar to Odin. Make sure your phone is in download mode again, connected via USB and click start again. You'll notice that your phone might take a while to boot up. It'll be updating files and apps so be patient.
6. CWMR. After it's all booted up, time to go back to download mode again. In ODIN, you'll want to click on PDA again and this time flash the CWMR file. Click start and you're done in no time. CWMR replaces stock recovery with the same options plus extra goodies.
7. CLEAN AGAIN. Now you'll want to turn off your phone and boot the phone holding the bottom of the rocker. You'll boot into CWMR. Time to wipe and format again. You'll find the first 2 wipe options on the first page. The wiping of dalvik cache will be in the ADVANCED menu. Then you'll want to go into the MOUNTS AND STORAGE menu. Format system, cache & data.
8. CM10. Now while still in CWMR, you'll need to go into the MOUNTS AND STORAGE menu and select MOUNT USB STORAGE. You'll want to connect your phone to your PC with the USB. Place the CM10 and Gapps files in the main directory of your PHONE'S INTERNAL STORAGE. Select UNMOUNT on your phone, disconnect from USB and now you'll want to go to the option INSTALL ZIP FROM SDCARD.. then go to the CHOOSE.. option and select the final fruit of your labor, CM10. When it's done doing it's thing, REBOOT SYSTEM. Be patient and let everything load.
9. GAPPS. After everything has loaded, you want to turn off the phone and boot into CWMR one last time. Go to INSTALL ZIP FROM SDCARD, CHOOSE ZIP and flash that Gapps file. Then REBOOT SYSTEM.
10. RESTORE. Reinstall the app you used to backup your stuff, move your backup files you put on the PC back to it's rightful place and restore. You should be good to go.
Credits in no special order:
dman3285 (CM10)
CarpeNoctem (Root Guide)
ardatdat (Kernel)
designgears (Stock ICS Leak)
utkanos (CWMR 5.0.2.7)
Someone said doing this is a good idea so..
rogernizzLe said:
Someone said doing this is a good idea so..
Click to expand...
Click to collapse
You've made the same mistake as in your previous post. Step 6 for cleaning up the phone should be after you copy the cm10 and gapps to internal storage or otherwise from cwmr you'll have to mount storage and then copy the files from your comp. If you format system then you won't be able to boot at all.
And after the copy you can do all the format and cleaning and install cm10 and then gapps together and reboot finally.
This guide would be a good help to the new users. Hopefully you can incorporate the changes to correct it.
Sent from my SGH-I927
ninthsense said:
You've made the same mistake as in your previous post. Step 6 for cleaning up the phone should be after you copy the cm10 and gapps to internal storage or otherwise from cwmr you'll have to mount storage and then copy the files from your comp. If you format system then you won't be able to boot at all.
And after the copy you can do all the format and cleaning and install cm10 and then gapps together and reboot finally.
This guide would be a good help to the new users. Hopefully you can incorporate the changes to correct it.
Sent from my SGH-I927
Click to expand...
Click to collapse
Sorry, really wanted to play AC3. Fix'd the cleaning stage. I realized I actually did mount the storage. Looks okay, I hope?
Hey, I followed these steps and it worked.
Didn't run into any major problems, except for having to download the CM10 file using my phone itself, I couldn't download it from my computer (found this out in the CM10 post, pg 29).
It really helps to follow OPs instructions, but also read up on all of the individual threads he links to before actually doing anything.
Thanks rogernizzLe!
Glad it helped. Enjoy!
So all the features of the phone works? Physical keyboard, 3G, GPS, WiFi?
Do you have to use the 1 click?
I have ICS installed via CLock work Mod and Have the Lite Kernel.
Should I not just be able to install JB from Clock work mod? I have never used the 1 click installer but I am on ICS with an ICS Kernel.
Waiting for everything to work before I flash JB. Heard there were still issues with the camera.
r0bot said:
So all the features of the phone works? Physical keyboard, 3G, GPS, WiFi?
Click to expand...
Click to collapse
For a list of what works in the CM10 ROM, check it's thread's OP. dman updates it as bugs are being fixed/found.
dudejb said:
Do you have to use the 1 click?
I have ICS installed via CLock work Mod and Have the Lite Kernel.
Should I not just be able to install JB from Clock work mod? I have never used the 1 click installer but I am on ICS with an ICS Kernel.
Waiting for everything to work before I flash JB. Heard there were still issues with the camera.
Click to expand...
Click to collapse
The method is how I got to JB. There's probably other ways but this worked for me. And yes, currently camera doesn't work.
If I may suggest ... some post updates would be useful ...
Post #1:
rogernizzLe said:
... and then go to the CM10 thread ...
Click to expand...
Click to collapse
- could you update with a link to the thread? (There are so many!)
Post #2:
rogernizzLe said:
Someone said doing this is a good idea so..
Click to expand...
Click to collapse
- didn't and don't understand this at the time.
- perhaps a "(reserving a message slot)" in the middle would clarify.
- my guess was, this post was saying doing the things in post 1 was a good idea.
- only later did I realize you were probably referring to the reservation of the message slot.
Post #9:
rogernizzLe said:
... For a list of what works in the CM10 ROM, check it's thread's OP. dman updates it as bugs are being fixed/found. ...
Click to expand...
Click to collapse
- a link to the thread you mean, for later readers, would also be useful here.
thx so much
it's really helpful for a fisher like me
When the update file downloads then it verifies but when it goes to install, it errors out and stops [see attached image]. There is also mention of Gmail.apk but when I go and look for it, it's not there. I have deleted the file and downloaded several time but wind up with the same result. I have put a copy in the ext sd card and tried from there but it will not install. Any ideas on how to do the upgrade?
Thanks, Dave
Correct me if I'm wrong, but it sounds like you're trying to do an ota when you're rooted (with a custom recovery). This won't work. Please read through this thread by CNexus about otas:
http://forum.xda-developers.com/showthread.php?t=2209418
It should give you everything you need to know.
Sent from my SPH-L710 using xda app-developers app
topherk said:
Correct me if I'm wrong, but it sounds like you're trying to do an ota when you're rooted (with a custom recovery). This won't work. Please read through this thread by CNexus about otas:
http://forum.xda-developers.com/showthread.php?t=2209418
It should give you everything you need to know.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Wow! I went through over 30 pages looking for a step by step and am quite confused as to the proper process. I am currently on 4.1.1 with LJ7 and have downloaded MD4 both DeOdex and Odex plus the MD4 kernal. The only thing I did when I got the phone was root it enough to make the hot spot app work.
JOB Dave said:
Wow! I went through over 30 pages looking for a step by step and am quite confused as to the proper process. I am currently on 4.1.1 with LJ7 and have downloaded MD4 both DeOdex and Odex plus the MD4 kernal. The only thing I did when I got the phone was root it enough to make the hot spot app work.
Click to expand...
Click to collapse
Thanks for reading all of it. Most people would just look at the first page and the last page and say "Oh, it's not there!" That being said, I hope you have a better understanding of what's going on when you get an OTA notification.
Now that's been said, I had written a post on another thread that covers the steps A-Z. I've linked it and quoted it below.
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, it should have gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
JOB Dave said:
The only thing I did when I got the phone was root it enough to make the hot spot app work.
Click to expand...
Click to collapse
I don't think there's a way to be "just a little rooted"
:silly:
Follow topherk's directions to a tee, and you'll be fine.
As a noob, I was scared to death knowing that I was rooted and I was going to get an OTA!
xda-developers has everything you need. The files, the guides, the support from senior members.
Relax and have fun...
---------- Post added at 06:11 PM ---------- Previous post was at 05:54 PM ----------
BTW, I flashed freeza's md4 odexd rom (cause a stock sg is odex), the md4 firmware, and the optimized kernel. Flashed (installed) them in that order. Just download them from the site onto your phone, and boot into recovery to flash each. Probably too paranoid, but i rebooted after each flash *just* to be sure). Cleared dalvik cache after installing the rom. Ummm, and ran checksum on my files before I installed them (I use md5 checker app).
Thanks, that got me started. now I have to figure out which rom and kernal I want to install.
ROMs come with kernels already, so if you're unsure ATM, just flash a ROM and then later you can check out kernel switching. Just make sure that the kernel you are flashing is for your ROM version (4.1.2, 4.2.2, etc) and for your type (AOSP, Touchwiz).
Since you are just starting out, I would suggest TPR (The Peoples ROM) or MOAR (Mother of All ROMs). Both in Android Dev section (as opposed to Original Android Dev).
TPR also has AROMA installer, so it lets you pick what apps, kernel, and other goodies you want to flash and basically on-the-spot customization.
Downloaded the file MD4_update_FULL_Odex.zip and followed the instructions above and got zip signature failure, see photo. I am wondering if it worth doing the upgrade.
~Dave
In twrp, under settings, you can uncheck the zip file verification option. Most of the time it gives you that error, even though the zip is fine.
Sent from my SPH-L710 using xda app-developers app
topherk said:
In twrp, under settings, you can uncheck the zip file verification option. Most of the time it gives you that error, even though the zip is fine.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That worked!! Thanks for all your help.
Am looking at the About screen and the build says I'm on MD4 but the Baseband is still LJ7, do I need to be concerned about that?
JOB Dave said:
That worked!! Thanks for all your help.
Am looking at the About screen and the build says I'm on MD4 but the Baseband is still LJ7, do I need to be concerned about that?
Click to expand...
Click to collapse
Baseband has to do with what modem/radio you are on. This is independent of your ROM, so the two can be different version numbers.
The modem impacts your mobile data coverage and speeds. What you wanna do (if you wanna find the best modem for your area) is to switch modems and run each one for a week. Then switch. After you've gone through a couple modems, single out the ones that qork best and test those out till hou find the best and/or fastest one for your area and the places you frequent.
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