Related
i have a T989, rooted, Clockwork Mod, and installed some stock Android (sans bloatware) MOD.
i had updates set to automatic and am now being bugged to install the new TMobile update, which doesn't seem to be able to install with Clockwork, and i can't turn off the persistent Update prompts.
i've already bricked one GS2, and obviously fear doing it again. I wouldn't get another chance, i don't think. (i do have insurance on the phone, not sure if it would cover a rooted phone?)
what can someone tell me about the TMobile update and Clockwork, or whatever i need to do, go with the update or stop it somehow...?
thanks for your help.
Ota update requires stock recovery.
Grab one of the updated stock roms and flash via cwm. Then Odin the new baseband.
Sent from my SGH-T989
i think i have one of those stock roms - i chose one that was just 'the same thing but without some of the standard apps'. how can i check to see what rom i have...?
and what do you mean by baseband? the new update? is it already dl'd to my phone? i've searched through the phone's dirs (rooted File Explorere, i guess) and could not find anything...
sorry to be a pain - i can't brick another one, of course... (
is this what you mean by a 'stock updated rom':
http://forum.xda-developers.com/showthread.php?t=1312736 ?
glennnall said:
sorry to be a pain - i can't brick another one, of course... (
is this what you mean by a 'stock updated rom':
http://forum.xda-developers.com/showthread.php?t=1312736 ?
Click to expand...
Click to collapse
No, look for the KL1 release.
Baseband is your radio btw. Don't worry about the radio for now, just work on getting the rom flash.
Sent from my SGH-T989
ok, found Deodexed_KL1_T989 (T989UVKL1 by Whitehawkx) is that what i'm looking for? -
couple of questions:
he says on the post:
"DONT FLASH - add files to the zip in the app folder, then flash. Or usb connect drag to sd the use some rooted file explorer to place in system/app then reboot."
Flash or don't Flash? I'm transferring the zip to sd now, then i need to move it to system/app...?
once i've 'flashed' what do you mean "Odin the baseband"? i have Odin, used it last time...
thanks
GideonX said:
No, look for the KL1 release.
Baseband is your radio btw. Don't worry about the radio for now, just work on getting the rom flash.
Sent from my SGH-T989
Click to expand...
Click to collapse
I flashed the ROM, now i have 2.3.6, and now i'm stuck with 2 OTA notifications, one states postponed, and choosing START for the update does nothing.
help?
I had the base load on mine with a bunch of stuff frozen and Clockwork on it (plus root)
I first unfroze all the stuff I had frozen, then ODIN'd back the stock recovery. Didn't touch anything else, then told the OTA to go ahead.
It updated just fine -- removed root of course. I then ODIN'd back the clockwork recovery and re-installed SU, then re-froze all the boatware.
Done in about 15 minutes -- no muss, no fuss, didn't lose anything.
Genesis3 said:
I had the base load on mine with a bunch of stuff frozen and Clockwork on it (plus root)
I first unfroze all the stuff I had frozen, then ODIN'd back the stock recovery. Didn't touch anything else, then told the OTA to go ahead.
It updated just fine -- removed root of course. I then ODIN'd back the clockwork recovery and re-installed SU, then re-froze all the boatware.
Done in about 15 minutes -- no muss, no fuss, didn't lose anything.
Click to expand...
Click to collapse
ok, thanks - this is what i didn't understand - i can Odin back to Stock recovery?
for some reason Odin doesn't recognize my phone in download mode, but it does when i'm connected and the phone is on... any reason for this? i don't use odin in any means but download mode, right?
glennnall said:
I flashed the ROM, now i have 2.3.6, and now i'm stuck with 2 OTA notifications, one states postponed, and choosing START for the update does nothing.
help?
Click to expand...
Click to collapse
You can probably clear this up by formatting /system in CWM. Then wiping cache and dalvik. Then flash the FL1 update. Hit advance, fix permissions and then reboot.
GideonX said:
You can probably clear this up by formatting /system in CWM. Then wiping cache and dalvik. Then flash the FL1 update. Hit advance, fix permissions and then reboot.
Click to expand...
Click to collapse
did all this, nothing's changed. i'm unable to get Odin to see my phone in DL mode. when i boot into DL mode, the device manager shows an alert on my phone. in normal, the drivers work fine and Odin sees the phone.
damn.
Howto: Flash back to GB after ICS Update on the Captivate Glide
Needed Files:
Clockworkmod Recovery (CWMR): ---TOUCH--- or ---NON-TOUCH---
Odin: ---DOWNLOAD HERE---
CWMR Flashable GB Rom: ---INCEPTION ROM---
Samsung Stock Rom: ---I927UCKL1--- or ---I927UCKI3---
NOTE: If you just want to go back to GB and are happy with just the Inception rom, only download cwmr, odin, and the inception rom, otherwise, download all files.
INSTALL CWMR
first you will need to install CWMR onto your phone. to do this you need to connect your phone into download mode (power on + hold volume up, and follow prompts) via usb, start up odin, make sure only reboot is checked (uncheck F. Reset Time) and click PDA. select the unzipped cwmr (.md5 file) file you downloaded and then click start.
Congratulations, your phone now has clockwork mod recovery installed!!!
INSTALL INCEPTION ROM
the next step in the downgrade process is to install the inception rom. to do this, copy over the inception rom zip you your phones internal memory (not the external microsd) and boot into recovery (power on + hold volume down). as a precaution make a backup then do a wipe/factory reset, wipe cache, go to mounts and storage and format system (for good measure). then go back to the main menu, then install zip from sdcard, then find the zip you put on your sdcard. scroll down to yes and let the magic happen.
Congratulations, you now have the inception rom installed on your phone.
Now you can stop here, but if you want to go back to pure stock so that you can get the OTA/KIES updates again go on to the next step.
INSTALL STOCK ROM
the final and optional step is to install the stock rom back onto the phone. to do this put your phone back into download mode, fire up odin, make sure only reboot is checked. then select PDA and select the stock firmware (unzipped), this will be a .md5 file. click start in odin, and let it do its thing. it will wipe and load the stock rom back on your phone and you will be back to pure ATT stock rom goodness...
Hope this helps those out that are having trouble going to back to gingerbread
NOTE: MYSELF OR ANY OTHER PERSON ON XDA IS RESPONSIBLE FOR YOUR PHONE BREAKING, YOU AND ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS. IF YOU DO NOT KNOW WHAT YOU ARE DOING FIND SOMEONE THAT DOES
SIDENOTE: i take no credit for any of the files/links provided. if this post helped, make sure to thank those that developed the files provided for they are your saving grace here.
thanks a lot
You're a life saver! I followed these directions and it worked perfectly.
Why uncheck F. Reset time?
Sent from my SAMSUNG-SGH-I927 using Tapatalk 2
LiquidXed said:
Why uncheck F. Reset time?
Sent from my SAMSUNG-SGH-I927 using Tapatalk 2
Click to expand...
Click to collapse
every other howto involving oding with out phone says to... i dont even know what it does...
inthepit said:
every other howto involving oding with out phone says to... i dont even know what it does...
Click to expand...
Click to collapse
I guess its supposed to reset the flash counter, I need that bein how crappy my luck is with this phone incase I have to send back in for warranty
Sent from my SAMSUNG-SGH-I927 using Tapatalk 2
thank you man, it works
whats the difference between:
I927UCKL1 and I927UCKI3 ?
I put on I927UCKI3 and send the phone to my mom, when she put in her SIM card the voice and text work fine, but she is not seeing data.
Is this the software or maybe she needs a new SIM card or hopefully the phone isnt busted. Any ideas?
I927UCKI3 = 2.3.5
I927UCKL1 = 2.3.6
is you mother on AT&T? if not, you would have to enter the correct APN info...
I see, thanks for that!
I sent her into the ATT store and all they had to do was "turn on" the 3G for her and everything is fine now. She doesn't know the first thing about gingerbread or ICS so I just wanted to get her off the problematic ICS build and back onto gingerbread where she can do her simple emailing and web browsing. Should I upgrade her to 2.3.6 or do you think 2.3.5 is perfectly fine and stable for "non-power users"? Thanks again for all the help!
michaelsanfrancisco said:
I see, thanks for that!
I sent her into the ATT store and all they had to do was "turn on" the 3G for her and everything is fine now. She doesn't know the first thing about gingerbread or ICS so I just wanted to get her off the problematic ICS build and back onto gingerbread where she can do her simple emailing and web browsing. Should I upgrade her to 2.3.6 or do you think 2.3.5 is perfectly fine and stable for "non-power users"? Thanks again for all the help!
Click to expand...
Click to collapse
2.3.5 is fine not much different from 2.3.6 I do not recall the changes from 1 to the other but very minor.
dudejb said:
2.3.5 is fine not much different from 2.3.6 I do not recall the changes from 1 to the other but very minor.
Click to expand...
Click to collapse
the main reason to have 2.3.6 is if you want to have video chat with google talk or google+ hangouts. 2.3.5 doesnt let you from what i remember.
thanks a lot for this downgrade guide, didn't know downgrading needs GB kernel..
But does anybody know where we can get "real" stock rom? Mine is i927R unlocked. I downloaded GB stock from sammobile but it turns out to be rooted & has some Rogers apps preinstalled. Same thing I got with AT&T version.
Before upgrading to ICS, my stock was really clean, well just Rogers logo at start up, but the rest is just standard samsung's android thing..
Is this some kind of differences between locked & unlocked i927R?
Unlocked Captivate Glide ICS
if i am unloked i can still do this?? or my phone will be locked again?
I did this exactly, but when trying to flash back to stock, my phone still fails when trying to mount /preload (trying to update application)
Same here. I used inception rom couple of days, after that i tried downgrade to stock and it fails when trying to mount /preload (trying to update application). How to resolve it?
Sorry to bump an old thread, but whats the difference between the Inception ROM and the stock 2.3.6 ROM? I had 2.3.6 for about a year and I loved it before someone broke my phone. I bought a new Glide but it came with 4.0.4, and I hate it more every day. I'd like to downgrade but I'm concerned with the guys above me who said they had problems loading the stock 2.3.6 ROM. What are the main differences in case it doesnt work, or is there a way to fix it?
Please, any help would be appreciated. Much thanks
inc3ption link to downgrade to gingerbread
Hi, I cannot find here and in google a working link to download it. Can I use another gingerbread custom rom?
remone said:
Hi, I cannot find here and in google a working link to download it. Can I use another gingerbread custom rom?
Click to expand...
Click to collapse
Yes. You can use any CWM flashable rom to revert back to GB and then fash Odin to get to stock. If you don't, you will hang at the boot screen.
Kudos for searching!
If you have issues getting your hands on a GB rom sent me a PM i can google drive it to you.
many thanks: with the custom and stock roms I have problems. and when I don't have problems they drain the battery
who has this file
CWMR Flashable GB Rom: ---INCEPTION ROM---
Hey, does anyone have the inc3ption_v1.zip file?
The links in the op are dead.if you have the file could you upload it somewhere?
Alright so I'm new at this and haven't managed to brick my phone yet so that's a good sign.
As far as I've learned the process is Root>Recovery>Rom Flash, at least generally.
I rooted it successfully, but when I try to install recovery with ROM Manager it lists only one S3 with a bracketed cell phone provider I don't think I have. So I ditched CWM and went to Goo Manager but when I try to install that, it just hangs on some download page telling me its about to start.
So I'm going to assume the recovery thing is pretty easy to sort out and move on to my next question.
My S3 is unlocked, but I am under Koodo, which is an extension of Telus. My phone model is a I747M, not an I747. As far as I can see they are identical in hardware and software, but I'm really wondering what ROMs I can install. I've researched but didn't find much, and I don't want to blindly flash a i747 rom onto a potentially different phone, and risk anything.
Oh and PS any ROM with the vanilla android (like on the google phones) will do.
Thanks.
Czaran said:
Alright so I'm new at this and haven't managed to brick my phone yet so that's a good sign.
As far as I've learned the process is Root>Recovery>Rom Flash, at least generally.
I rooted it successfully, but when I try to install recovery with ROM Manager it lists only one S3 with a bracketed cell phone provider I don't think I have. So I ditched CWM and went to Goo Manager but when I try to install that, it just hangs on some download page telling me its about to start.
So I'm going to assume the recovery thing is pretty easy to sort out and move on to my next question.
My S3 is unlocked, but I am under Koodo, which is an extension of Telus. My phone model is a I747M, not an I747. As far as I can see they are identical in hardware and software, but I'm really wondering what ROMs I can install. I've researched but didn't find much, and I don't want to blindly flash a i747 rom onto a potentially different phone, and risk anything.
Oh and PS any ROM with the vanilla android (like on the google phones) will do.
Thanks.
Click to expand...
Click to collapse
Hello Noob (I mean that kindly, I used to be one)
I'll help you with what ever you need. I'm Canadian and on Bell i747M. Feel free to ask me any questions and I'll reply as soon as I can. Hopefully I wont be too confusing. I'll just try to break down all your questions in a point form.
First, i747 and i747M are almost identical. With the latest 4.3 ROMS there are differences in the bootloader that will make data not work on your phone. For now, stay away from any stock 4.3 ROM. AOSP ROMs (CM10, Task650) are fine.
Recovery: Through Rom Manager you will want to download the recovery titled "Samsung Galaxy S3 (ATT) " The AT&T version of the S3 is commonly shown as D2ATT(i747). This recovery will work for you. I have had a problem with TWRP myself recently being stuck on the download page. There is another way to install TWRP, but it is a bit more difficult. Try CWM first and if you like I will give you instructions for TWRP.
ROMs: If you want the most common and most stable Vanilla ROMs for your phone you are gonna want Cyanogenmod or Task's ROM. They are very similar with a few different features. Beware, if you ask questions in Task's thread you will be told it is an ATT ROM only. It does work on the i747M though.
Latest Cyanogen: http://download.cyanogenmod.org/?device=d2att
Latest Task : http://forum.xda-developers.com/showthread.php?t=1766684
You will of course lose Touchwiz on these ROMs.
Touchwiz Roms:
STAY AWAY FROM 4.3 ROMS!!!!!!
These ones will do as is. Watch that they are still 4.1.2
http://forum.xda-developers.com/showthread.php?t=1766684 This one has a white theme and is my favorite.
http://forum.xda-developers.com/showthread.php?t=2176793 This one has tons of options.
As always be sure to read the OP in every thread. You will learn lots there. If you want any more info reply and I will try and help.
BCSC said:
Hello Noob (I mean that kindly, I used to be one)
I'll help you with what ever you need. I'm Canadian and on Bell i747M. Feel free to ask me any questions and I'll reply as soon as I can. Hopefully I wont be too confusing. I'll just try to break down all your questions in a point form.
First, i747 and i747M are almost identical. With the latest 4.3 ROMS there are differences in the bootloader that will make data not work on your phone. For now, stay away from any stock 4.3 ROM. AOSP ROMs (CM10, Task650) are fine.
Recovery: Through Rom Manager you will want to download the recovery titled "Samsung Galaxy S3 (ATT) " The AT&T version of the S3 is commonly shown as D2ATT(i747). This recovery will work for you. I have had a problem with TWRP myself recently being stuck on the download page. There is another way to install TWRP, but it is a bit more difficult. Try CWM first and if you like I will give you instructions for TWRP.
ROMs: If you want the most common and most stable Vanilla ROMs for your phone you are gonna want Cyanogenmod or Task's ROM. They are very similar with a few different features. Beware, if you ask questions in Task's thread you will be told it is an ATT ROM only. It does work on the i747M though.
Latest Cyanogen: http://download.cyanogenmod.org/?device=d2att
Latest Task : http://forum.xda-developers.com/showthread.php?t=1766684
You will of course lose Touchwiz on these ROMs.
Touchwiz Roms:
STAY AWAY FROM 4.3 ROMS!!!!!!
These ones will do as is. Watch that they are still 4.1.2
http://forum.xda-developers.com/showthread.php?t=1766684 This one has a white theme and is my favorite.
http://forum.xda-developers.com/showthread.php?t=2176793 This one has tons of options.
As always be sure to read the OP in every thread. You will learn lots there. If you want any more info reply and I will try and help.
Click to expand...
Click to collapse
Awesome, I appreciate the writeup. So I flashed recovery successfully (ROM Manager doesn't seem to have d2att anymore so I used ODIN).
I'll probably go for Cyanogen mod tommorow, I'll post again if I have any questions.
Thanks.
Czaran said:
Awesome, I appreciate the writeup. So I flashed recovery successfully (ROM Manager doesn't seem to have d2att anymore so I used ODIN).
I'll probably go for Cyanogen mod tommorow, I'll post again if I have any questions.
Thanks.
Click to expand...
Click to collapse
CM is a good ROM. There should soon be Kitkat versions available. You will be seeing nightly updates when it does come around. Before you start flashing, you should learn what a 'Nandroid' is. You can take a Nandroid backup in CWM or TWRP. Always save these to an External SD card. If anything ever goes wrong with your ROM, you can just re flash the Nandroid backup and be back to where you were the day you did the backup. The farther you get into flashing the more likely you will need these. Before doing your first Flash, do an Nandroid and copy your photops and stuff off of the phone. When jumping between Stock and AOSP roms, you will need to do a full wipe and will lose what you have not backed up. Be sure to sync contacts to Google....this is the one that has screwed me the most.
BCSC said:
CM is a good ROM. There should soon be Kitkat versions available. You will be seeing nightly updates when it does come around. Before you start flashing, you should learn what a 'Nandroid' is. You can take a Nandroid backup in CWM or TWRP. Always save these to an External SD card. If anything ever goes wrong with your ROM, you can just re flash the Nandroid backup and be back to where you were the day you did the backup. The farther you get into flashing the more likely you will need these. Before doing your first Flash, do an Nandroid and copy your photops and stuff off of the phone. When jumping between Stock and AOSP roms, you will need to do a full wipe and will lose what you have not backed up. Be sure to sync contacts to Google....this is the one that has screwed me the most.
Click to expand...
Click to collapse
Alright, so I have CWM v5.5.0.4, which from what I understand is pretty outdated. It was probably just me following an outdated guide and forgot to look up an updated version. Will I need to update of will it cause any problems? I already backed up my phone on 5.5.0.4 with Nandroid.
Also I feel like I'm misunderstanding the procedure of flashing a new rom. So I downloaded a cm-10.1.3 zip which is is the latest stable build on android 4.2.2. This has an .img inside so this is the rom. I use CWM to flash this onto my phone correct? (Once I figure out if I need to update CWM)
Lastly whats the deal with Gapps? I downloaded the CM Gapps for 10.1 from their wiki. Is this the only way to get Gmail, Maps, and the Google Play Store onto the phone?
From what I understand I think I can just use odin to flash, correct? If so I'd probably prefer that because its the most familiar and noob friendly.
Czaran said:
Alright, so I have CWM v5.5.0.4, which from what I understand is pretty outdated. It was probably just me following an outdated guide and forgot to look up an updated version. Will I need to update of will it cause any problems? I already backed up my phone on 5.5.0.4 with Nandroid.
Also I feel like I'm misunderstanding the procedure of flashing a new rom. So I downloaded a cm-10.1.3 zip which is is the latest stable build on android 4.2.2. This has an .img inside so this is the rom. I use CWM to flash this onto my phone correct? (Once I figure out if I need to update CWM)
Lastly whats the deal with Gapps? I downloaded the CM Gapps for 10.1 from their wiki. Is this the only way to get Gmail, Maps, and the Google Play Store onto the phone?
From what I understand I think I can just use odin to flash, correct? If so I'd probably prefer that because its the most familiar and noob friendly.
Click to expand...
Click to collapse
I wouldn't use Odin. It really will only become necessary if you want to flash back to complete stock.
You do want the latest version of CWM installed or you will run into problems flashing. You can get this 2 ways.
1: through Rom Manager. You will find your specific CWM with these steps. a-Recovery Setup b-ClockworkMod Recovery c-Hit menu button to left of home and pick 'Show All Devices' d- Here scroll until you get 'Samsung Galaxy S3 (AT&T)' D2ATT. e- Click Flash ClockworkMod Recovery. Allow permissions for root. Ignore the touch option unless you want to pay for it. I can teach you the free way.
You will now have the latest CWM
You can download the latest CM-10.2, it is in release candidate stage and is extremely stable. They have been working on it for months. It will give you 4.3 (The good kind, not the one I warned against). After downloading a ROM, you leave it zipped exactly like it is. Do not extract it, just move it to your SD card. You will also want Gapps. Gapps is necessary because it is Google's own software that is legally not allowed to be built into ROMs. It must be installed separately. You can find those here. They help you know which to use with chart depending on which Cyanogen you use http://wiki.cyanogenmod.org/w/Gapps. Again just move the zip over to your internal.
With these 2 zips transferred to your phone you are ready to start. Before you do, make sure you have transferred all your pics and stuff off of the phone. Also be sure to save your contacts. You can now boot into recovery. You should notice recovery version 6.0.4.3. Volume button scrolls menu, Power button selects. You will want to do a Nandroid backup in case anything goes wrong. I know you did one with CWM 5.5 but should do another just to be sure it is with current CWM. You can delete the other one later.
Goto - backup and restore
Goto - backup to external or /storage/sdcard1 (i put both because im already on 4.4 and may have different menu than you.
Let this work and when done continue to flashing ROM
Go to 'choose zip from /sdcard'
Select CM-10-xxxxxxx.zip
After this completes you will do the same with Gapps.zip
After completion of both files you will need to factory reset your phone. Flashing AOSP over Stock will cause boot loops if you do not.
Go back to CWM main menu and select wipe data/factore reset
After completing this go to wipe cache partition and select this.
Finally you want to wipe Dalvik cache. you will find this in CWM under main menu /advanced/wipe dalvik cache.
Upon completion of this you should have CM10 4.3 running. Just exit CWM reboot phone and when booted follow setup instructions.
Let me know if you get stuck somewhere.
BCSC said:
Upon completion of this you should have CM10 4.3 running. Just exit CWM reboot phone and when booted follow setup instructions.
Let me know if you get stuck somewhere.
Click to expand...
Click to collapse
Alright cool. So through Mod Manager, there was not d2att, there was only S3(Metro PCS) which I thought was a bit odd. I found a way to flash an updated recovery via terminal emulator so that went well.
And your steps were very well written and concise. I'm now running CM without a problem.
Thanks for your help!
Czaran said:
Alright cool. So through Mod Manager, there was not d2att, there was only S3(Metro PCS) which I thought was a bit odd. I found a way to flash an updated recovery via terminal emulator so that went well.
And your steps were very well written and concise. I'm now running CM without a problem.
Thanks for your help!
Click to expand...
Click to collapse
Cool terminal emulator was that other way to do it. Hope all is well for you with this. Welcome to flashing. As another tip, if you are going to flash a lot, there is an app called Titanium backup that is well worth the $5 it costs. It saves all your apps and data and after a clean wipe you can just reinstall all your apps in one step. For example after a wipe you will not lose your Angry Birds levels if you restore your titanium data. It's worth a look.
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
For the past 3 days i've gone through hell and back with this phone.
To start off I rooted the phone, and that was working fine, my buddy was downloading something (idek what it is and I have no way to get ahold of him to ask him) and after that it busted. Then I somehow deleted my whole operating system.
Since then I have downloaded a 4.3 stock rom (os?) and I have successfully unbricked my phone. Now I have no service, and i'm 99% sure it's because all of my IMEI things are unknown. Now I figure that is an easy fix by downloading a modem?
Before I look into fixing my IMEI problems I would like to get back to 4.4.2 (Kit-Kat I think it was?)
I've downloaded countless ROMs, IMG files (converted to tar.md5), and many versions of Odin.
I've messed with Samsung Kies but I can just tell that this is a garbage program, and I have no clue what i'm doing.
What i'm asking here is help to getting me back to stock 4.4.2 (WITHOUT A ROOT) and possibly fix my IMEI problem and the problem I can't get 3g/mobile data working (snapchat/instagram did not work) (APN maybe?) (I haven't looked into these problems yet, could be super hard, could be fairly easy)
Samsung Galaxy S3 AT&T SGH-i747 is the phone i'm currently working with.
The last thing I tried to do is flash with a boot.tar.md5 and system.tar.md5, it did NOT work, as I was not sure where to put those files at in odin. Boot = Bootloader and System = AP/PDA?
Sorry if I come off as a complete noob, this is literally last resort for me (I've been doing this for 3 days....) as I can probably suspect you guys are very tired of all of these help requests.
Thank you to everybody who reads this, and am looking forward to having a normal phone again.
Edit: First post here
Does the phone boot into download mode? Sounds like it does since you can use Odin.
To get the phone running, copy the latest cm11 or cm 12 to an sd card, copy cm11 Gapps or cm12 Gapps (download the version that matches the ROM you intend to flash), flash a custom recovery (I prefer CWM for the d2lte or Philz Touch for the d2lte), boot into recovery, do a full wipe, flash cm, flash Gapps, boot the phone.
audit13 said:
Does the phone boot into download mode? Sounds like it does since you can use Odin.
To get the phone running, copy the latest cm11 or cm 12 to an sd card, copy cm11 Gapps or cm12 Gapps (download the version that matches the ROM you intend to flash), flash a custom recovery (I prefer CWM for the d2lte or Philz Touch for the d2lte), boot into recovery, do a full wipe, flash cm, flash Gapps, boot the phone.
Click to expand...
Click to collapse
sick thanks for the response homie.
i'm not exactly sure which CM to download, I went to the d2ltes since that's the closest thing to my device I found in that list.
I also went to cwm rom managers and downloaded the recovery setup, i'm guessing I convert that and flash it using odin and voila, I have cwm?
and for the cm11 gapps I went to this website and downloaded the zip file, going to just put that on my sd card with the CM (when I figure out which one to download)
am I headed in the right direction?
edit: okay I got cwm recovery on my phone... thats good
edit 2: alright downloading cm12 and alreayd have cmgapps in a zip ready to be put in my sd card. i'll let you know how installing it with cwm goes. thank you for your help man I really appreciate it.
edit 3: how would I go about installing it via owm? everytime I install from sd card it resets my phone, just go back into recovery and install the second zip? or is there a way I can install both at once?
Boot into cwm, wipe cache, wipe data, wipe dalvik, install cm1 from sd card, install gapps, reboot.
The i747 is also known as the d2lte so anything designed for the d2lte is good.
audit13 said:
Boot into cwm, wipe cache, wipe data, wipe dalvik, install cm1 from sd card, install gapps, reboot.
The i747 is also known as the d2lte so anything designed for the d2lte is good.
Click to expand...
Click to collapse
alright! couldn't thank you enough. like I said i'll keep you updated!
edit: i'm in the cwm recovery or w.e and there is a different keyboard as i'm doing this, does this transfer over to be my real keyboard after the cwm recovery stuff? if not, how do I get this keyboard?
edit 2: wow this is totally different, sick.. let me play around with it, i'm sure i'll have some questions.
alright, phone number is still not available, imei and imei sv is still not available, same with everything in the SIM status.
going to try and find a modem for my model.
no luck so far, if someone could help search for a MODEM for SGH-i747 AT&T s3 that would be great..
sorry for being so needy.. thanks for hanging in here and helping me out.
edit: I found this link but it's for 4.4.2... it says do not use it if you're on 4.3.... is it okay if i'm at like 5.1.1 cwm?
well, I cannot post the link and I do not want to find a way around to post the link incase a mod shuts this thread down. if you want the link you may PM me..
edit 2: okay so google play services does NOT work, and I need that in order to open skype.. so that's on another thing on the list of **** to fix. However I just downloaded an apk and I need to put it in system/apps but i'm not sure where to find that... i'll probably end up downloading it on the phone and dropping it in with a file manager.
edit 3: none of this worked, I still need google play services to get installed..
Does the phone boot to the desktop? Which rom did his try? Try the latest cm10.2 for the d2lte.
Are you able to install a terminal app or Samsung phone info app?
Try and find the apk version of the app and just install it from the file browser.
audit13 said:
Does the phone boot to the desktop? Which rom did his try? Try the latest cm10.2 for the d2lte.
Are you able to install a terminal app or Samsung phone info app?
Try and find the apk version of the app and just install it from the file browser.
Click to expand...
Click to collapse
It tells me "It cannot be installed". I will find 10.2 for d2lte... assuming I find the corresponding GApps.
I also could have ran all of the other google apps... "google +, playstore, youtube, etc"
edit: I cannot find cm 10.2, lowest I can find for d2lte is 11. should I try that instead?
These are all the zips i'm installing with cwm when I wipe/reset my phone totally:
Calkulin's Google Play Service modded (so google play services works)
cm-11
gapps-kk-20140606
and I am currently messing with modem files to get my service back, i'm about to try my second one.. wish me luck!
edit: I can't get my baseband model to show, nor my imei numbers to come, they all stay unknown.. if someone would like to do some sort of 1 on 1 that would be awesome.
You could also try the cm for the d2att.
audit13 said:
You could also try the cm for the d2att.
Click to expand...
Click to collapse
trying it now! should I use a specific gapps? maybe for 5.1.1? cause 12.1 uses 5.1.1 if i'm not mistaken.
There are separate gapps for cm10.2, cm11, and cm12.
It sounds to me like there is a problem with the modem and bootloader combination on the phone.
What specific bootloader version is on the phone?
audit13 said:
There are separate gapps for cm10.2, cm11, and cm12.
It sounds to me like there is a problem with the modem and bootloader combination on the phone.
What specific bootloader is on the phone?
Click to expand...
Click to collapse
so after I download cm12.1 and cm12gapps, I should look further into the bootloader/modem problem?
i've tried a few modems for i747 and i've had no luck so far unfortunately, if someone else reading this has had experience or knows someone who has experiences null baseband / imei numbers let me know!
edit: oops, my mistake.. just saw the last part of your post now. i'm not sure how to find out my bootloader.
Use the terminal app and type getprop ro.bootloader.
audit13 said:
use the terminal app and type getprop ro.bootloader.
Click to expand...
Click to collapse
i747ucufnj1
i'm certain the only problem I have now is the IMEI (no sim service) besides that everything is good now!
farkas3 said:
i747ucufnj1
i'm certain the only problem I have now is the IMEI (no sim service) besides that everything is good now!
Click to expand...
Click to collapse
Alright I've now figured out that I do NOT have ANY efs files for samsung galaxy I747UCUFNJ1.
I have the imei number from the back of my phone.
I tried the EFS pro method and when I click "backup" an error pops up and says "Block device does NOT exist"
I'm so confused and I need help lol
wow, I fixed it! I installed the correct modem corresponding to my baseband / bootloader something like that.. wow. most stressful 4 days of my life
ty so much
Glad you got it working. This is why I kept asking about the modem and suggesting that the modem doesn't match the bootloader.