Related
Im sorry if this is being repeated, but I'm relatively new to flashing custom ROMs and up until now haven't really had any issues.
I recently flashed the latest PACman rom 4.3 and I'm not sure what went wrong. I'm coming from 4.2. I did everything the same as usual, wiped cache and dalvik, installed the zip. As soon as the phone rebooted, I started getting error messages. "Acore has stopped working, blame tyler", same thing for the system UI. So I decided to do a wipe and restore. Well now my restore wont work. I've had to go back to a PAC version from back in February because none of my other restore files will work. I'm not sure what to do. Even on this restore file, I'm getting "insufficient storage" messages when I havent even uploaded all my apps yet.
Please help!
justxan said:
Im sorry if this is being repeated, but I'm relatively new to flashing custom ROMs and up until now haven't really had any issues.
I recently flashed the latest PACman rom 4.3 and I'm not sure what went wrong. I'm coming from 4.2. I did everything the same as usual, wiped cache and dalvik, installed the zip. As soon as the phone rebooted, I started getting error messages. "Acore has stopped working, blame tyler", same thing for the system UI. So I decided to do a wipe and restore. Well now my restore wont work. I've had to go back to a PAC version from back in February because none of my other restore files will work. I'm not sure what to do. Even on this restore file, I'm getting "insufficient storage" messages when I havent even uploaded all my apps yet.
Please help!
Click to expand...
Click to collapse
I had similar problems going to 4.3 as well. Mine kept getting frozen at the boot screen, and wouldn't restore any of my backups. I tried flashing back to previous versions of android and nothing was really making any difference. Finally I ended up flashing the whole phone back to stock. From there I flashed the new 4.3 stuff on top of that and now everything is working flawlessly like it should again. I still have no idea what caused the issues, it's gotta be something in the new 4.3 stuff that's trickling in.
Here's what I did:
Download the most recent complete firmware file (which is UCDLK3 for d2att)
Download the pit file for my phone
Flash stock image and pit file with repartition through ODIN
Flash custom recovery back through ODIN (CWM, TWRP, etc)
Download and flash latest UCDMG2 bootloader (for d2att)
Download and flash your choice of ROM, kernel & gapps
and optionally -
Update modem to latest UCDMG2
Now you should be back to a fresh install of 4.3 which works the way it should! Hopefully you had your apps backed up with titanium or something similar which can be restored now as well.
exodus454 said:
I had similar problems going to 4.3 as well. Mine kept getting frozen at the boot screen, and wouldn't restore any of my backups. I tried flashing back to previous versions of android and nothing was really making any difference. Finally I ended up flashing the whole phone back to stock. From there I flashed the new 4.3 stuff on top of that and now everything is working flawlessly like it should again. I still have no idea what caused the issues, it's gotta be something in the new 4.3 stuff that's trickling in.
Here's what I did:
Download the most recent complete firmware file (which is UCDLK3 for d2att)
Download the pit file for my phone
Flash stock image and pit file with repartition through ODIN
Flash custom recovery back through ODIN (CWM, TWRP, etc)
Download and flash latest UCDMG2 bootloader (for d2att)
Download and flash your choice of ROM, kernel & gapps
and optionally -
Update modem to latest UCDMG2
Now you should be back to a fresh install of 4.3 which works the way it should! Hopefully you had your apps backed up with titanium or something similar which can be restored now as well.
Click to expand...
Click to collapse
Thank you for responding and providing details. I guess I'm not understanding where to find these files. I have the firmware downloaded. The pit file, I can't seem to find no matter what I search for. I can find help on creating my own, but I'm afraid I'll screw something up if I start messing with things. The stock image, bootloader and modem...no idea where to find those either. I've never had to do any of this before. Are these files within the rom I'm trying to flash??
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.
I'm sorry to make my first post so noobish, but I've been trying for a day now to get CM 11 onto my phone, and the installation keeps failing, something about the signature failing. I tried miui just to see if the rom iteself was the issue, and i had the same result. I have the phone rooted via odin(CF-Auto-Root-d2can-d2vl-sghi747m). I found a rom (cm-11-20140217-NIGHTLY-d2att) and dropped the zip on my sd, popped that in, put the phone in recovery. I formatted and cleared cache. Then tried to install the rom from external. I see it there but the installation fails every time.
Where am I going wrong? do i need something else on the phone?
thanks for any help.
1. You need to root and disable Knox (I saw you rooted but did you disable knox?)
2. You need a custom recovery. A quick way todo this is download this http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.7.0.0-d2att.tar (its the newest TWRP) and flash it using Odin.
3. then you should be able to flash which ever rom you want, BUT be careful because I think some can mess up the i747m. (PS cm11 isnt that great, still very buggy and battery life is not as good as stock.)
Oh one more thing. the CM11 file you have is old since it says d2att, cm renamed the device to d2lte which supports all north american galaxy s3's I believe.
I did disable Knox. does this matter though? I mean once you reset the phone in recovery mode and clear the cache? is CM10 any better? im not too concerned with battery life (7200mah battery)
Do you have the 4.3 bootloader on your phone? I assume you do since you mentioned that you disabled knox.
For a custom recovery, I recommend Philz Touch for the d2lte which is based on the latest CWM which can be flashed through Odin.
The best ROM I have used on the s3, and other Android phones, is Validus 13 Ground Zero ROM.
Hey Guys,
I just got a new Samsung Galaxy S3 SGH-I747 in the mail and I immediately started to install Cyanogenmod. I have installed it on two S3's in the past, but this time I had no idea about the new bootloader problems after Android 4.3 (I think?). I got CWM touch installed with no problems via Odin, but when I tried to use the Unified Android Toolkit thing to root and stuff I got stuck in a boot loop. The phone would not boot past the Samsung logo, not the animated one with the purple light, but the one that shows the phone model.
I have tried everything I could think of and all that I tried to google for the past couple hours to no avail. I stupidly did not make a backup of my stock ROM, and I couldn't find a stock 4.4.2 ROM except this one that says it is stock but with root. I flashed that ROM and then it booted past the Samsung logo and the animated one, but is now stuck on the AT&T logo. I looked up that problem and couldn't find any real information on that problem except one thread where it said I should install Kies and let it do the Firmware Upgrade and Initialisation option. That failed and then my phone would only turn on straight to download mode.
I reflashed CWM and that worked so I thought that if I tried to install Cyanogenmod 11 it might work because that ROM is 4.4.1 or higher (Again, I think?). Now it's back into the loop where it makes it past the samsung stuff but then gets stuck on the AT&T logo. Is there anything I can do?
Thanks,
Jemimacakes
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
audit13 said:
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
Click to expand...
Click to collapse
Yes, I have tried clearing stuff in both CWM and stock recovery. Im not sure about the Dalvik one though, unless that is cleared when you do factory reset and clear cache I didnt do it. I can try flashing CM10.2 ( which I would prefer to have over 11), but my understanding is that my boot loader will not let me install anything that uses any lower versions of android, but I'll give it a shot and let you know.
Ok guys,
I tried to install Cyanogenmod 10.2 and when I put it on my sd card and tried to install it with CWM It threw and ton of errors that look like this.
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG3" || etc etc.
Im not super experienced with programming, but im guessing that CM10.2 can find any bootloader it can use? Im not sure what my bootloader is if that is the case, but I can boot into recovery so I must have something, right?
Anything I can do?
Thanks
Jemimacakes
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Hey,
I did have the latest version of CWM, but I tried it on TWRP and got the same errors
audit13 said:
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Click to expand...
Click to collapse
Hey,
I have now tried both custom recoveries and gotten the same errors on both, and I made sure I had the latest version of each. Can I flash the firmware from 4.3 and then install CM10.2? Will that work? I really don't want to hard brick my phone.
EDIT: I installed ADB to find out what my bootloader was, and it returned that I had the NE4 version. Is there a way to get the MJB version safely so I can install 10.2?
At this point I just want it to boot up to anything, so if that is easier to do than get CM to work then im completely open.
You cannot go back to MJB from NE4.
How did you try to install CM the first time? Did you use the install manager or a custom recovery?
The last time I installed CM on a i747 was back when the phone was on 4.1.1. The second phone I installed it on was the international version of the phone, also on 4.1.1. I used a custom recovery both times. I bet if I would have used the new installer on this phone it would have worked, but I was trying some other stuff because I was curious and ended up breaking it.
IT BOOTED!
I reflashed the stock firmware + root, reinstalled stock recovery and wiped everything I got it to boot into its stock ROM. From this point, where do I go? Will the CM installer work or will it just brick it again?
Thanks
Jemimacakes
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
audit13 said:
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
Click to expand...
Click to collapse
Which version of CM11 should I get. On the site I see that the last version of CM11 for the I747 (d2att) was released on feburary 16, is this one based on 4.4.2?
EDIT: Also, I should copy CM11 to both the internal and external storage? Why is this?
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
audit13 said:
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
Click to expand...
Click to collapse
Alright, but I have the at&t version of the phone. Are they both compatible with one another?
EDIT: OK, correct me if im wrong, but my new understanding is that CM now has releases for general versions of phones, so the most recent update of CM for my phone is the d2lte, not d2att?
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
audit13 said:
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
Click to expand...
Click to collapse
Hello again,
Thanks a ton Audit, my phone is up and running with the latest cyanogen nightly! A recap for anyone who might come across with a similar problem.
1. I installed a ROM using an older version of android onto a phone with the new bootloader (NE4), softbricking it.
2. I installed the stock ROM + root from this link using Clockworkmod
https://www.androidfilehost.com/?fid=23501681358550126
3. Installed the stock Recovery from this link and did wiped my data and both caches
https://www.androidfilehost.com/?fid=23681161096070493
4. I rebooted the phone and waited at the AT&T logo for a while, and it booted up normally!
5. I installed the most recent version of Philz Touch Recovery for the d2lte, made a nandroid for safety, and then install the latest nightly of CM11 for the d2lte.
6. It works!
Thanks again to Audit for helping me out!
Jemimacakes
I'm glad it all worked and I was able to help in some way.
It's great that you posted your solution in case it helps other people in a similar situation.
I think i'm in a similar place - a few questions. You used cwm to install the stock ROM? I thought you needed to use odin. Also, why did you need to install the stock recovery (and did you just flash the .zip in cwm)? Also, that stock rom you linked to is 4.4, right? Would that work if I was on 4.3?
Before flashing anything, I suggest you confirm your bootloader and modem. Flashing the wrong combination of modem and bootloader could hard brick your phone.
If your phone does not boot, try flashing Philz Touch for the d2lte and flash the latest cm11. Hoepfully, this will get your phone running so you can confirm the bootloader and modem. CM11 does not flash a modem or bootloader.
So I was messing around with some ROMs to see which one I liked. But when I installed the SlimLP Rom my phone started acting weird. First it would just shut down and then I couldn't even get into recovery. I finally got into recovery after using ODIN and now I want to get rid of this ROM and im getting an error message that says this phone is an sghi727, MY PHONE IS DEFINATELY A sght989. Help me. Im so confused. This is all new to me.
akumar94 said:
So I was messing around with some ROMs to see which one I liked. But when I installed the SlimLP Rom my phone started acting weird. First it would just shut down and then I couldn't even get into recovery. I finally got into recovery after using ODIN and now I want to get rid of this ROM and im getting an error message that says this phone is an sghi727, MY PHONE IS DEFINATELY A sght989. Help me. Im so confused. This is all new to me.
Click to expand...
Click to collapse
Did you try going into your recovery and wiping data/factory reset, cache, and dalvick. Then flashing a new rom or did you just dirty flash?
Restore to stock rom is one option.
See this thread : http://forum.xda-developers.com/showthread.php?t=2541783
The reason it might have that model number in build.prop is because most ROMs from the AT&T S2 work just fine on the T-Mobile S2 and the ROM dev doesn't make two ROMs with the only difference being the model number. If you can get into recovery, you can do a full wipe and install another ROM. Make sure you are using the latest recovery. I recommend TWRP, as it is touch screen and very user friendly.
jrc2