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.
Related
So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.
Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.
To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.
Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement
GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)
My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.
You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.
Hi All -
First time posting! I am very new to this and I'm in dire need of help! I will write as many details of my situation as I can!
So, I have been running a recent nightly of Cyanogenmod 11 on my d2att/i747 Samsung Galaxy S3 for the past few weeks. I decided to try out the encryption feature (first mistake). I noticed that things weren't running smoothly as they were before and decided to try flashing a new ROM (latest AOKP nightly). NOW, I am in trouble.
First, before installing AOKP, I loaded the ROM and gapps to my external SD. I then did these steps: wipe data/factory reset, then
format /data, then format /system, finally Wipe Dalvik Cache. I then installed AOKP and gapps from the external SD. Halfway through the install I noticed on the screen "E: Can't mount SDCard". However, the install appeared to go through well so I thought it might have been in error.
I then rebooted as per normal, at which point I was shocked to still see the cyanogenmod encryption unlock screen! I plugged in the password, and then watched the AOKP boot screen perpetually load. It never did fully load.
Would any of you be able to help me resurrect my phone? Thank you so much in advance!!!
What version of the AT&T ROM were you running before installing CM11?
audit13 said:
What version of the AT&T ROM were you running before installing CM11?
Click to expand...
Click to collapse
That was ages ago. MAYBE 4.1.1.
I Think I may have to try to do a stock recovery...
As long as you were not on 4.3, flashing via Odin should restore the phone to complete stock everything (ROM, Radio, bootloader).
audit13 said:
As long as you were not on 4.3, flashing via Odin should restore the phone to complete stock everything (ROM, Radio, bootloader).
Click to expand...
Click to collapse
It doesn't seem to be working when I try to flash through ODIN. It says "succeed 0/failed 0". Could that be because of running CM11 (android 4.2.2)? Or the encryption?
Possibly. You're flashing a stock AT&T rom from samfirmware?
audit13 said:
Possibly. You're flashing a stock AT&T rom from samfirmware?
Click to expand...
Click to collapse
not samfirmware. i'll try downloading one from them.
Samfirmware has the official ROM releases.
Link here: http://www.sammobile.com/firmwares/1/?model=SGH-I747&pcode=ATT#firmware
ARGH. So, in theory ODIN worked. However, after booting up again, I'm getting the same request to enter a code to get past encryption. Even better, that code is no longer working!!!
Any ideas?
doorstop25 said:
ARGH. So, in theory ODIN worked. However, after booting up again, I'm getting the same request to enter a code to get past encryption. Even better, that code is no longer working!!!
Any ideas?
Click to expand...
Click to collapse
I take it back!!! I did another factory wipe and everything turned on!!! WHOOO!!! Thanks for the help!
My I747 is currently running Carbon Rom nightly 20131102 (4.3.1), it's quite old and I want to upgrade to 4.4.
So last night I nandroid backup , format system, data, flashed Carbon KK on it, then gapps, data, cache, delvik, reboot. But it stayed at the CM alien. I reflashed several times but still stuck at there. But I can nandroid back so I'm kind of fine now. But anyone know why?
Second, I notice my \0\ folder is under sdcard\download\0\ than usual sdcard\0\, I must have done something wrong when I first flash the carbon but I don't know what it is. I usually put my .zip in download, could that be why? Could that cause the bricking I have with KK?
Last, I know there's a flash counter and when I first root/flash last year, I went thru many things to avoid that&IMEI, instead of directly flashing a recovery. I think that could be the source of the problems above??? Now 1 year is up and my warranty is already over so I don't have to worry about the counter anymore. If I want to redo everything, and have to noobiest/simpliest method to flash to KK, what should I do?
Sorry if I lack any essential information. I'd be happy to find it to help.
Did you update to the latest CWM before flashing the ROM? Is your current bootloader supported by the ROM?
Not the latest but 6.0.4.3
I'll update it to 6.0.4.7 and try again.
Unfortunately I don't know if my bootloader is supported. I don't really know how to find mine.
I would update to the latest CWM and then try to flash a 4.4.2 custom ROM. If it doesn't install, it should generate an error message.
Most custom ROMs will look for a particular bootloader. If the bootloader is not found, CWM will give you get prop errors.
audit13 said:
I would update to the latest CWM and then try to flash a 4.4.2 custom ROM. If it doesn't install, it should generate an error message.
Most custom ROMs will look for a particular bootloader. If the bootloader is not found, CWM will give you get prop errors.
Click to expand...
Click to collapse
Thanks, I'll try when I get home.
I installed the ROM fine last night without any error. So I believe the bootloader is supported then.
afyaff said:
Thanks, I'll try when I get home.
I installed the ROM fine last night without any error. So I believe the bootloader is supported then.
Click to expand...
Click to collapse
To be sure, look at the bootloaders mentioned in the ROM's updater script.
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.
Greetings,
I was attempting to install a ROM through CWM 6.0.4.7 recovery and it failed during the installation. More like crashed as I did not get an error message or have the robot fall over. After this happened my galaxy s3 started bootlooping. During the bootloop I could still see the cyanogen mod icon present which I thought was strange as I had done a full wipe/factory reset/system format before attempting to install the other ROM. I have been flashing ROM's for over a year but am still learning. Anyway I got back into CWM recovery and attempted to wipe user data/factory reset again to make sure I had a clean install before making a 2nd attempt and I was able to wipe both caches no problem but when I attempt to do factory reset it crashes. I thought maybe it was the recovery so I flashed TWRP through ODIN and tried to factory reset and it also crashes.
I am still able to access download mode and get into custom recoveries but I am not sure what to do now. I have attempted to flash back to CM 11 and Task 650 4.4 but I receive status 7 errors. I have not been able to locate stock restore tar files for 4.3 as all I have read is that 4.3 was an OTA and there is no tar file for it. Any thoughts? Thanks in advance.
ladd76 said:
Greetings,
I was attempting to install a ROM through CWM 6.0.4.7 recovery and it failed during the installation. More like crashed as I did not get an error message or have the robot fall over. After this happened my galaxy s3 started bootlooping. During the bootloop I could still see the cyanogen mod icon present which I thought was strange as I had done a full wipe/factory reset/system format before attempting to install the other ROM. I have been flashing ROM's for over a year but am still learning. Anyway I got back into CWM recovery and attempted to wipe user data/factory reset again to make sure I had a clean install before making a 2nd attempt and I was able to wipe both caches no problem but when I attempt to do factory reset it crashes. I thought maybe it was the recovery so I flashed TWRP through ODIN and tried to factory reset and it also crashes.
I am still able to access download mode and get into custom recoveries but I am not sure what to do now. I have attempted to flash back to CM 11 and Task 650 4.4 but I receive status 7 errors. I have not been able to locate stock restore tar files for 4.3 as all I have read is that 4.3 was an OTA and there is no tar file for it. Any thoughts? Thanks in advance.
Click to expand...
Click to collapse
Are you using the AT&T i747 or the i747M? Looks like your phone does not have a working OS. Please see the post below for a similar problem. If you have the AT&T version, you may try the same recommended solution to get your phone back to working condition via stock restore which you can do from custom recovery ...
http://forum.xda-developers.com/showthread.php?t=2743241
Larry2999 said:
Are you using the AT&T i747 or the i747M? Looks like your phone does not have a working OS. Please see the post below for a similar problem. If you have the AT&T version, you may try the same recommended solution to get your phone back to working condition via stock restore which you can do from custom recovery ...
http://forum.xda-developers.com/showthread.php?t=2743241
Click to expand...
Click to collapse
yes i747 thanks
Try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
Try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
That is actually what i was flashing when I encountered my problem. I was finally able to get one of my old ROM's to install after re-flashing the newest CWM through ODIN and reinstalling my bootloader. I am not sure what the problem was as the stock rom 4.3 shouldnt have downgraded it? Perhaps a random crash which corrupted something. The developer on the stock rom has provided a tar file which I may try this time around. Thank you all for your help.