Where do I start? - T-Mobile Samsung Galaxy S 4

Hi everyone, I just upgraded to the SGS4(M919) from the LG G Stylo.
I haven't been a part of an active development community in awhile, coming from the Stylo where there was 0 development for my variant(No Unlock for Bootloader). I haven't developed anything nor really done anything with samsungs since the SDX-Days when the Captivate was popular.
So my question is where the heck do I start?
Model: M919
OS: 4.4.2
BB: M919UVUFNB4
The in Call screen really bothers me and my husband got a s5(the only one they had) that's 1000 time better ascetically.
TIA, Kristi

Also I see that some have bootloader lock. I have a m919 but it is NOT T-mobile My phone is a unbranded factory unlocked. I bought I brand new from aarons

The m919 does not have a locked bootloader.
To confirm the exact model #, boot the phone into download mode.
If it is an sgh-m919. I would run OTA updates until the phone is running a stock 4.4.4 ROM. This will ensure the modem and bootloader are up to date.
Next, I would flash TWRP via Odin. Once TWRP is up and running, select a custom ROM and use TWRP to flash a custom ROM of your choice.

audit13 said:
The m919 does not have a locked bootloader.
TO confirm the exact model #, boot the phone into download mode.
If it is an sgh-m919. I would run OTA updates until the phone is running a stock 4.4.4 ROM. This will ensure the modem and bootloader are up to date.
Next, I wuld flash TWRP via Odin. Once TWRP is up and running, select a custom ROM and use TWRP to flash a custom ROM of your choice.
Click to expand...
Click to collapse
Thank you for the help.
Download mode, sticker, and settings confirms SGH-M919 however it says at 4.4.2 is the latest version

I believe 4.4.4 is the latest: http://www.sammobile.com/firmwares/database/SGH-M919/

audit13 said:
I believe 4.4.4 is the latest: http://www.sammobile.com/firmwares/database/SGH-M919/
Click to expand...
Click to collapse
Will download that and install TWRP. Thanks for the help.

No problem. We're here to help and learn from each other. Let us know how it goes.

audit13 said:
No problem. We're here to help and learn from each other. Let us know how it goes.
Click to expand...
Click to collapse
Are there any recovery images/boot image with sgs5 off line charging screen? I have cm13 and cwm touch recovery but when I flashed cwm charging animation looks like something from a palm pilot from 2002

What is the model # for the s5? I would not recommend using CWM as it has not been updated for a long time. Try TWRP. I believe the charging animation is based on the ROM.
What happened with flashing the s4?

audit13 said:
What is the model # for the s5? I would not recommend using CWM as it has not been updated for a long time. Try TWRP. I believe the charging animation is based on the ROM.
What happened with flashing the s4?
Click to expand...
Click to collapse
I did flash the s4. I have cm13 my husband has the s5(g900m) and his power off charging screen is pretty.

You could try flashing an s5 or Note 4 port to your phone.

audit13 said:
The m919 does not have a locked bootloader.
To confirm the exact model #, boot the phone into download mode.
If it is an sgh-m919. I would run OTA updates until the phone is running a stock 4.4.4 ROM. This will ensure the modem and bootloader are up to date.
Next, I would flash TWRP via Odin. Once TWRP is up and running, select a custom ROM and use TWRP to flash a custom ROM of your choice.
Click to expand...
Click to collapse
Question, is Odin the only way to install TWRP?
I have some down time at work

Odin is not the only way to flash twrp but I find it to be the easiest and most efficient way.
I think other methods require a rooted phone with and some sort of rom manager app.

Related

[Q] Stuff is harder to find for sgh i747m

Hi im new on this forum and I would like to have some tricks and tips cause I just rooted my phone yesterday and it seems more difficult to find information for my phone I have a galaxy s3 on 4.3 sgh i747m with Rogers .... Is it me or there is just a lot more stuff made for the i9300... I have tried to find ROM'S and tricks to put CWM recovery but it's harder to find information !!
to put CWM recovery I saw a lot of stuff saying download rom manager and install CWM recovery with this app but they offer me a version of CWM recovery for a galaxy s3 (metro cps) they doesn't say if it's made for a sgh i747 so im really scared to do something wrong if I install this version of CWM recovery ..
Could some one help me maybe with website limks or a guide for beginers noob like me or this forum seem's to be really good with some people with knowledge
Before my galaxy s3 I had a Jailbreak Iphone 3gs a year ago but Rooting an Android and putting stuff on it is not really the same thing it's far away from it!
And does it matter if put some stuff on my phone made for at&t sprint etc.... even if those are sgh i747
Hey,
I am running CM11 d2att and CWM d2att on my i747m and it works perfectly. It has been so long since I did it that I can't remember the exact steps that I took, so I would do some more research. Everything I needed to know was on these forums somewhere.
I believe the rough steps I took were:
- Root
- Install CWM (d2att)
- Update bootloaders (i747m)
- Flash d2att rom
But I can't remember exactly, so do some research before you go ahead!
You can install pretty much whatever you'll find in these forums except for bootloaders and modems.
There are specific bootloaders/modem for the i747m vs. i747.
The rest, unless explicitely specified otherwise, is 100% compatible between i747 and i747m.
As for your recovery script, I would suggest installing TWRP instead of CWM.
TWRP is more user friendly for people that are new to Android and both are usually supported.
For this, go to the Play Store, download and install the "Goo manager" application.
Once installed, open up the app, hit the menu button and select the "install recovery script" option.
It will automatically select/download/install the correct recovery for your phone and ask you to confirm before doing so.
HiKsFiles said:
You can install pretty much whatever you'll find in these forums except for bootloaders and modems.
There are specific bootloaders/modem for the i747m vs. i747.
The rest, unless explicitely specified otherwise, is 100% compatible between i747 and i747m.
As for your recovery script, I would suggest installing TWRP instead of CWM.
TWRP is more user friendly for people that are new to Android and both are usually supported.
For this, go to the Play Store, download and install the "Goo manager" application.
Once installed, open up the app, hit the menu button and select the "install recovery script" option.
It will automatically select/download/install the correct recovery for your phone and ask you to confirm before doing so.
Click to expand...
Click to collapse
Ok thank you thats what I was wondering it doesn't matter if it's an at&t, bell or rogers... but it have to be the right model !!
Your talking about bootloader ... when I rooted my phone I have unlock my bootloader right ?? What is the advantage of changing your bootloader ....do you have to change it when you put a custom rom's?? Maybe my question have no sense at all because im new to this but I keep reading a lot of stuff on android !
carlosQC said:
Ok thank you thats what I was wondering it doesn't matter if it's an at&t, bell or rogers... but it have to be the right model !!
Your talking about bootloader ... when I rooted my phone I have unlock my bootloader right ?? What is the advantage of changing your bootloader ....do you have to change it when you put a custom rom's?? Maybe my question have no sense at all because im new to this but I keep reading a lot of stuff on android !
Click to expand...
Click to collapse
I recommend not updating your phone to any stock 4.3 ROM. A stock 4.3 ROM will install a 4.3 bootloader which cannot be downgraded and may cause problems when trying to root or get back to stock.
Some newer ROMs require an updated bootloader in order to install and boot. I am running a 4.1.2 bootloader on my i747m and don't have any problems installing 4.4.2 ROMs.
Rooting gives you access to the system files and does not unlock you bootloader.
For installing custom ROMs, I use Philz Touch which is based on CWM. I have tried TWRP and I was getting errors when flashing custom ROMs. I was able to flash the same ROM using Philz Touch without a problem. TWRP is more user friendly but doesn't work as well for me.
audit13 said:
I recommend not updating your phone to any stock 4.3 ROM. A stock 4.3 ROM will install a 4.3 bootloader which cannot be downgraded and may cause problems when trying to root or get back to stock.
Some newer ROMs require an updated bootloader in order to install and boot. I am running a 4.1.2 bootloader on my i747m and don't have any problems installing 4.4.2 ROMs.
Rooting gives you access to the system files and does not unlock you bootloader.
For installing custom ROMs, I use Philz Touch which is based on CWM. I have tried TWRP and I was getting errors when flashing custom ROMs. I was able to flash the same ROM using Philz Touch without a problem. TWRP is more user friendly but doesn't work as well for me.
Click to expand...
Click to collapse
what do you mean when you say I recommend not updating your phone to any stock 4.3 ROM (when a custom rom is based on 4.3?) and can you explain me the bootloader thing in details how can I fix that or how can I unlock it ?
what is d2att ?
carlosQC said:
what do you mean when you say I recommend not updating your phone to any stock 4.3 ROM (when a custom rom is based on 4.3?) and can you explain me the bootloader thing in details how can I fix that or how can I unlock it ?
what is d2att ?
Click to expand...
Click to collapse
Your post says youhave 4.3 on your phone. Is it a stock 4.3 ROM?
d2att (i747) is the AT&T version of the s3. Canada has the i747m.
The bootloader does not need to be unlocked in order to install a custom recovery or to root like Motorola phones.
The bootloader is software that an OS works with in order to function as a phone.
audit13 said:
Your post says youhave 4.3 on your phone. Is it a stock 4.3 ROM?
d2att (i747) is the AT&T version of the s3. Canada has the i747m.
The bootloader does not need to be unlocked in order to install a custom recovery or to root like Motorola phones.
The bootloader is software that an OS works with in order to function as a phone.
Click to expand...
Click to collapse
yes its the 4.3 jelly bean stock rom
but can I put any custom rom for my model the i747 or 747m ? The carrier doesn't have any importance ?
Any warranty left on your phone? Installing a custom ROM will void your warranty.
If you want to install a custom rom, copy the ROM you want to the internal or external SD card, install Philz Touch recovery, boot into recovery, wipe cache, Dalvik, install the ROM, and reboot.
You can install any ROM for the d2att as long as the ROM supports the phone's bootloader.
How I know which bootloader I got? If I have the 4.3 jelly bean I have a 4.3 boot loader?
Sent from my SGH-I747M using xda app-developers app
audit13 said:
Any warranty left on your phone? Installing a custom ROM will void your warranty.
If you want to install a custom rom, copy the ROM you want to the internal or external SD card, install Philz Touch recovery, boot into recovery, wipe cache, Dalvik, install the ROM, and reboot.
You can install any ROM for the d2att as long as the ROM supports the phone's bootloader.
Click to expand...
Click to collapse
How I know which bootloader I got? If I have the 4.3 jelly bean I have a 4.3 boot loader?
carlosQC said:
How I know which bootloader I got? If I have the 4.3 jelly bean I have a 4.3 boot loader?
Click to expand...
Click to collapse
Of you loaded a stock 4.3 ROM, you'll have the 4.3 bootloader.
audit13 said:
Of you loaded a stock 4.3 ROM, you'll have the 4.3 bootloader.
Click to expand...
Click to collapse
thank you for your help
Since you have TWRP installed, you not flash custom ROMs. Look around for a ROM you like, download it to your phone's SD card, boot into recovery, wipe cache, Dalvik, flash ROM, reboot.
audit13 said:
Since you have TWRP installed, you can not flash custom ROMs. Look around for a ROM you like, download it to your phone's SD card, boot into recovery, wipe cache, Dalvik, flash ROM, reboot.
Click to expand...
Click to collapse
He meant you CAN flash custom roms.
As long as the rom isn't packaged with a modem or bootloader you can flash any AT&T rom as you please.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
He meant you CAN flash custom roms.
As long as the rom isn't packaged with a modem or bootloader you can flash any AT&T rom as you please.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for catching my error. I edited my original post.
audit13 said:
Thanks for catching my error. I edited my original post.
Click to expand...
Click to collapse
No problem hope you would do the same for me.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] downgrading to cyanogenmod 10.2

hey guys,
i recently rooted my galaxy s3 i747 and installed cm11 on it. the whole process was done automatically using one of those cm installers. however, i recently learned that cm11 is not stable yet. so i want to downgrade to 10.2 which is the most recent stable cm.
i did try that, using manual methods, such as flashing it via recovery, however a picture of a dead android with a red warning triangle popped up saying it couldn't be done.
my question is, why would this happen? i know official android doesn't allow downgrade, but rooted ones should allow installation of any custom rom no matter which verison, right?
another question, how do i downgrade to 10.2, or install any other stable custom rom? i am afraid that the phone might become bricked due to my inexperience, but i want stability in my phone.
also, if my phone is indeed hard bricked, would it be possible to get it fixed under $100?
P.S. i am quite new to xda, so sorry if i posted this in the wrong area.
Are you using the most up to date custom recovery for your phone? Are you wiping system, Dalvik, and cache before installting the new ROM?
audit13 said:
Are you using the most up to date custom recovery for your phone? Are you wiping system, Dalvik, and cache before installting the new ROM?
Click to expand...
Click to collapse
used goo manager to install recovery, and wiped system, dalvik cache and cache. you see, i was following a video tutorial, and the custom recovery on that one was an older version. so, although i wiped them all, it was a bit different. you think that might be the problem?
user9560 said:
used goo manager to install recovery, and wiped system, dalvik cache and cache. you see, i was following a video tutorial, and the custom recovery on that one was an older version. so, although i wiped them all, it was a bit different. you think that might be the problem?
Click to expand...
Click to collapse
I would start over by flashing the tar version of Philz Touch via Odin 3.07 from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att.
Copy CM10.2 to your phone or external SD card, boot into recovery, wipe cache, Dalvik, data, and system. Then install CM10.2, boot into the OS, set things up, boot into recovery, and flash Gapps.
I prefer doing everything via recovery mode.
thanks! aah i'm a little scared though. do you think if i follow the instructions correctly, there'll be little chance of a hard brick? i know nothing's full proof tho.... what do you think? is it worth it? is 10.2 better than cm11 nightly as of yet?
You're using an AT&T s3 i747? What ROM was on the phone before you installed a custom ROM?
If it was any stock 4.3, don't touch the bootloader.
audit13 said:
You're using an AT&T s3 i747? What ROM was on the phone before you installed a custom ROM?
If it was any stock 4.3, don't touch the bootloader.
Click to expand...
Click to collapse
yup s3 i747 with bell. i think its the same as att. the phone came with 4.2 then i updated to 4.3 jelly bean.
also, isn't odin like a software on the computer? could you perhaps point to a tutorial? sorry ^_^' i'm not so familiar with android and there r so many tutorials out there, i wouldnt know which one i should follow in this case.
user9560 said:
yup s3 i747 with bell. i think its the same as att. the phone came with 4.2 then i updated to 4.3 jelly bean.
also, isn't odin like a software on the computer? could you perhaps point to a tutorial? sorry ^_^' i'm not so familiar with android and there r so many tutorials out there, i wouldnt know which one i should follow in this case.
Click to expand...
Click to collapse
The model # for the Bell s3 is i747m. The AT&T version is an i747. Make note of the difference when posting and looking solutions.
Do you have any warranty left on your phone? If you do, installing the 4.3 update will install the 4.3 bootloader and Knox. Once you have upgraded to the 4.3 bootloader, any attempts to downgrade the bootloader will brick the phone. Any reason you updated to 4.3?
Since you have Knox on your phone, installing a custom recovery will trip the knox counter and void your warranty. If you have no warranty left, tripping the counter isn't a problem.
audit13 said:
The model # for the Bell s3 is i747m. The AT&T version is an i747. Make note of the difference when posting and looking solutions.
Do you have any warranty left on your phone? If you do, installing the 4.3 update will install the 4.3 bootloader and Knox. Once you have upgraded to the 4.3 bootloader, any attempts to downgrade the bootloader will brick the phone. Any reason you updated to 4.3?
Since you have Knox on your phone, installing a custom recovery will trip the knox counter and void your warranty. If you have no warranty left, tripping the counter isn't a problem.
Click to expand...
Click to collapse
hmm when i look at my about phone it just says SMASUNG-SGH-I747... so i'm not sure where i747m comes in... i assume there's no warranty for my phone anymore since it's been rooted already. i just updated to 4.3 because i assumed that a reputable company like samsung would give out a good and better performance update. after i updated however, the phone started going haywire. it became laggy and slow. not that noticable, but still bothered me. the main reason i ditched iphone was because of it's sluggy behavior. so i had nothing to do but root. cm11's great, but some features are unstable, like random reboots and stuff. so i wanted to try cm10.2 or miui v5. hmm. i'm still thinking about how to figure out odin..
user9560 said:
hmm when i look at my about phone it just says SMASUNG-SGH-I747... so i'm not sure where i747m comes in... i assume there's no warranty for my phone anymore since it's been rooted already. i just updated to 4.3 because i assumed that a reputable company like samsung would give out a good and better performance update. after i updated however, the phone started going haywire. it became laggy and slow. not that noticable, but still bothered me. the main reason i ditched iphone was because of it's sluggy behavior. so i had nothing to do but root. cm11's great, but some features are unstable, like random reboots and stuff. so i wanted to try cm10.2 or miui v5. hmm. i'm still thinking about how to figure out odin..
Click to expand...
Click to collapse
The Bell, Rogers, and Telus version of the s3 is sgh-i747m. The AT&T version is sgh-i747. Did you get the phone from one of the Canadian carriers?
If you're running a custom ROM, this may be the reason it just shows sgh-i747. Custom ROMs on XDA are designed for the d2att but are compatible with the Canadian version of the s3.
Updating to 4.3 would have loaded a 4.3 bootloader and Knox. Once your phone has the 4.3 bootloader, do not attempt to downgrade the bootloader as it will brick your phone.
Knox software can interfere when trying to root your device.
You updated to 4.3, then installed CM?
audit13 said:
The Bell, Rogers, and Telus version of the s3 is sgh-i747m. The AT&T version is sgh-i747. Did you get the phone from one of the Canadian carriers?
If you're running a custom ROM, this may be the reason it just shows sgh-i747. Custom ROMs on XDA are designed for the d2att but are compatible with the Canadian version of the s3.
Updating to 4.3 would have loaded a 4.3 bootloader and Knox. Once your phone has the 4.3 bootloader, do not attempt to downgrade the bootloader as it will brick your phone.
Knox software can interfere when trying to root your device.
You updated to 4.3, then installed CM?
Click to expand...
Click to collapse
ah i understand now. i got the phone from bell. thanks for clarifying that.
i installed cm after the update, unfortunately. but when i went into recovery mode, i did not see anything related to knox. does it show up on the phone or in recovery mode? as of this moment, i was not thinking about the bootloader. because we're just tyring to downgrade the os, right? or is it something like previous os would not run on an updated bootloader?
user9560 said:
ah i understand now. i got the phone from bell. thanks for clarifying that.
i installed cm after the update, unfortunately. but when i went into recovery mode, i did not see anything related to knox. does it show up on the phone or in recovery mode? as of this moment, i was not thinking about the bootloader. because we're just tyring to downgrade the os, right? or is it something like previous os would not run on an updated bootloader?
Click to expand...
Click to collapse
Go into download mode and look at the screen. What does it say? It will probably have the model #, warranty bit, and whether it is running custom or official software.
Are you running TWRP or CWM?
audit13 said:
Go into download mode and look at the screen. What does it say? It will probably have the model #, warranty bit, and whether it is running custom or official software.
Are you running TWRP or CWM?
Click to expand...
Click to collapse
ok sir, this is what it says:
-ODIN MODE
-PRODUCT NAME: SGH-I747M
-CUSTOM BINARY DOWNLOAD: Yes (2 counts)
-CURRENT BINARY: Custom
-SYSTEM STATUS: Official
-QUALCOMM SECUREBOOT: ENABLE
-Warranty Bit: 1
-BOOTLOADER RP SWERV: 1
This screen tells you that your phone is an i747m, you have knox installed, any warranty on your phone has been voided, and you're loaded 2 custom ROMs.
Since you have a custom recovery, you can wipe data, cache, Dalvik, and install cm10.2.
audit13 said:
This screen tells you that your phone is an i747m, you have knox installed, any warranty on your phone has been voided, and you're loaded 2 custom ROMs.
Since you have a custom recovery, you can wipe data, cache, Dalvik, and install cm10.2.
Click to expand...
Click to collapse
ok now that you mentioned cwm and twrp, i noticed my phone resembles cwm when i boot into recovery. the tutorial i followed was in what looked like twrp. but why would that happen? i followed his instructdions and updated the recovery the same way he did via goo manager. he is using twrp, i am using cwm. is that the problem?
user9560 said:
ok now that you mentioned cwm and twrp, i noticed my phone resembles cwm when i boot into recovery. the tutorial i followed was in what looked like twrp. but why would that happen? i followed his instructdions and updated the recovery the same way he did via goo manager. he is using twrp, i am using cwm. is that the problem?
Click to expand...
Click to collapse
As long as you have a custom recovery, you can try flashing cm10.2.
audit13 said:
As long as you have a custom recovery, you can try flashing cm10.2.
Click to expand...
Click to collapse
i did try it before. booted into recovery, tried to flash rom zip and gapps. but it failed to flash. are you suggesting i do it in DOWNLOAD MODE with the new tar file you have mentioned? would you be able to link me to a place which would give me instructions? i am quite new to this. thanks
user9560 said:
i did try it before. booted into recovery, tried to flash rom zip and gapps. but it failed to flash. are you suggesting i do it in DOWNLOAD MODE with the new tar file you have mentioned? would you be able to link me to a place which would give me instructions? i am quite new to this. thanks
Click to expand...
Click to collapse
What error are you getting when you try to flash a ROM?
audit13 said:
What error are you getting when you try to flash a ROM?
Click to expand...
Click to collapse
it gives me a dead android with a red warning triangle. the one that says rom cannot be flashed.
user9560 said:
it gives me a dead android with a red warning triangle. the one that says rom cannot be flashed.
Click to expand...
Click to collapse
Are there any RPM error messages? What custom recovery do you have on your phone? It should say at the very top.

[Q] Flashed the stock rom but it is still showing cm 11 splash screen. . .

So, I'm not a complete noob to flashing roms/rooting devices. I flashed cm 11 to my s3, and decided I wanted to go back to stock via Odin. For some reason when I tried to turn on my device it was still showing the cm 11 splash screen and wouldn't proceed any further. It isn't technically bricked. I guess this would be classified as a boot loop to the nth degree. I tired to boot in recovery mode and wipe the cache partition and all user data to the same cm 11 robot taunting me. When I tried the process (flashing stock vi Odin) again to possibly fix whatever might have been a miss, I got the error message on the download screen "secure check fail: sb12." On the download mode screen it also says I am running the official system rom. I don't know what steps I need to take from here to get my phone to actually boot via the stock rom. Has anybody else had this issue or similar? Any help in resolving this would be greatly appreciated.
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
audit13 said:
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
Click to expand...
Click to collapse
I was under the impression the rom I was attempting to flash was indeed intended for Odin. It is the SGH-I747.
The download screen states,
Product Name: SGH-I747
Custom Binary: Custom
System Status: Official
Qualcom Secure Boot: Enable
Warranty Bit: 1
Bootloader AP SWERV: 2
Here is an added bit of fun, in the midst of the process I accidentally checked "Nand erase all," in Odin at one point.
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
My next question would be how can I move the zip files I download to the internal storage of my phone to flash them through Philz Touch?
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
sjthuss said:
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
I did. It said the the device couldn't be updated, or something to that effect.
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
audit13 said:
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
Click to expand...
Click to collapse
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So, I know there is a "thanks," button but I feel like that would be a little too informal for how much I appreciate your help! I downloaded ADB to move the rom (I went with AOKP because it was the first one that worked) to my phone, flashed it using TWRP and...BAM! We are back in business. Thanks for the direction, I thought I had a nice, new, shiny brick on my hands for about two days.
sjthuss said:
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
Click to expand...
Click to collapse
Canadian carriers use the i747m while att users get the i747.
The Canadian carriers did release a full 4.3 ROM unlike att who did not.

Downgrading from Android 5.1.1 to Android 4.1

I have Pac Rom Android 5.1.1 installed on my rooted sg3 and I need to do a carrier unlock. I contacted ATT to get the unlock code and the code they provided didn't work. Now I want to downgrade to Android 4.1 and try the UMTS menu trick as described here http://forum.xda-developers.com/showthread.php?t=2176719
I have tried Odin many times (with many versions, different computers, USB cables, etc) and every time Odin fails to flash Android 4.1. with a Fail AUTH error. I have used Odin successfully in the past many times with this phone but am unable to get it to work this time around.
Does anyone know how to downgrade the sg3 from 5.1.1 to 4.1? Or even better does anyone how to carrier unlock the sg3 when it has 5.1.1 installed on it?
Thanks!
Odin is probably failing because you have a 4.3 or 4.4.2 bootloader on your phone. I recommend you not flash anymore ROMs using Odin as repeat attempts to flash the 4.1.1 ROM via Odin may hard brick the phone.
Once a phone is running and 4.3 or 4.4.2 bootloader, you cannot use the free/hidden menu method to unlock the phone.
You cannot use a custom ROM to enter an unlock code. You'll have to go back to a stock ROM, enter the code, and return to a custom ROM.
Thanks for the reply. Do you know how I can go back to stock 4.1.1 without using Odin?
You need the 4.1.1 bootloader in order to use the free method. Once a phone is on 4.3 bootloader or higher, you can't go back to 4.1.1. Don't try because attempts to do so could brick the phone.
A stock 4.1.1 rom on a 4.3 bootloader will not work.
So you're saying once the sg3 is on a version above 4.3 there is no way to go back to 4.1.1?
slipnslider said:
So you're saying once the sg3 is on a version above 4.3 there is no way to go back to 4.1.1?
Click to expand...
Click to collapse
Once it is on the 4.3 or higher bootloader, there is no going back to an older bootloader and it is the older 4.1.1 bootloader and stock 4.1.1 ROM that is required to unlock using the free method.
Since you have the code, you can flash a stock ROM from recovery.
audit13 said:
Once it is on the 4.3 or higher bootloader, there is no going back to an older bootloader and it is the older 4.1.1 bootloader and stock 4.1.1 ROM that is required to unlock using the free method.
Since you have the code, you can flash a stock ROM from recovery.
Click to expand...
Click to collapse
Thanks. What do you mean by free method?
Also you suggesting if I put the 4.1.1 stock rom .zip on my sg3 I can flash it via CWM just like I would the latest 5.1.1 Pac Rom release?
The free method is the method you linked in your original post. This is the only free method available and it requires a 4.1.1 bootloader that your phone doesn't have. Installing 4.1.1 via cwm is not going to help you unlock it.
Since you have the code, you can flash a stock ROM from recovery.
Click to expand...
Click to collapse
How would I do this? Do I just flash 4.1.1 from cwm?
Flashing 4.1.1 onto your phone will not allow you to enter the code.
Before flashing anything, you need to verify the bootloader that is running on your phone. Until you do that, I would not flash any bootloaders or modems. An incompatible modem/bootloader combination can also brick your phone.
Sorry, one last question.
You'll have to go back to a stock ROM, enter the code, and return to a custom ROM.
Click to expand...
Click to collapse
How can I go back to the stock rom?
You can flash a stock rom from the general thread using twrp or cwm.
Awesome, thanks again. I was worried about going that route since I'm on 5.1.1 but I'll give it a shot
slipnslider said:
Awesome, thanks again. I was worried about going that route since I'm on 5.1.1 but I'll give it a shot
Click to expand...
Click to collapse
When you pick a stock ROM, make sure you pick one with the same bootloader and modem that are currently on your device. You probably have either the NE4 or NJ1 bootloader and modem pair. You DO NOT have a 5.1.1 bootloader and modem, they do not exist for the SGS3. Check your versions from a Terminal Emulator app or check them with the Phone Info - Samsung - app from the PlayStore.
Both NE4 and NJ1 stock ROMs are available in the forum. enewman17 posted them form image dumps, they have been used successfully by many.
The Terminal Emulator commands are:
Code:
getprop ro.bootloader
getprop | grep version.baseband
Thanks, I did this and both the bootloader and modem ended with NJ1 so I downloaded UCUFNJ1_Rooted.zip from enewman17's thread using CWM 6.0.4. The flash was successful but now the phone is frozen at the AT&T logo when I turn it on.
Any thoughts as to why its stuck booting up?
slipnslider said:
Thanks, I did this and both the bootloader and modem ended with NJ1 so I downloaded UCUFNJ1_Rooted.zip from enewman17's thread using CWM 6.0.4. The flash was successful but now the phone is frozen at the AT&T logo when I turn it on.
Any thoughts as to why its stuck booting up?
Click to expand...
Click to collapse
More than once I have seen reports of this happening when going from a 5.x.x ROM back to 4.4.x. The most common solution has been to include formating the internal sdcard before flashing the stock ROM.
If I flash the sd card as well I will lose the UCUFNJ1_Rooted.zip file. So in that case should I use adb via CWM to flash it?
slipnslider said:
If I flash the sd card as well I will lose the UCUFNJ1_Rooted.zip file. So in that case should I use adb via CWM to flash it?
Click to expand...
Click to collapse
Put the zip file on the external sdcard and then flash it with your recovery.
I actually didn't have an external SD card. I wound up taking it to the ATT store that had an ATT repair shop inside it and they reset it back to stock 4.4 for me and now everything works great! After unlocking the carrier on the phone I did have to manually enter the t-mobile APN to get the data connection working but that was simple (the info is listed on t-mobile's site)
slipnslider said:
I actually didn't have an external SD card. I wound up taking it to the ATT store that had an ATT repair shop inside it and they reset it back to stock 4.4 for me and now everything works great! After unlocking the carrier on the phone I did have to manually enter the t-mobile APN to get the data connection working but that was simple (the info is listed on t-mobile's site)
Click to expand...
Click to collapse
Glad to see you are up and running. Also glad to hear the AT&T guys helped out.

Can somebody help me? Do not start roms

Could someone help me? Every time I install a rom, I get the following message after the dribble. Process system is not responding it comes out absolutely with all the roms, less with the stock (currently I want to put lineage os) and sorry if something is wrongly written I speak Spanish .. thank you all :crying:
Which recovery are you using to flash the phone? Provide an example of a ROM that won't start. You confirmed that the phone model is sgh-i747 in download mode? Phone is running the latest 4.4.2 bootloader and modem?
.
audit13 said:
Which recovery are you using to flash the phone? Provide an example of a ROM that won't start. You confirmed that the phone model is sgh-i747 in download mode? Phone is running the latest 4.4.2 bootloader and modem?
Click to expand...
Click to collapse
Yes, it's a sgh-i747 recovery that I use is twrp 2.8 (with 3.0 pass the same) example of roms lineageos RR CM12.1. 13 and 14 I do not know what version of bootloader I have
Was 4.4.2 the last stock ROM running on the phone? If it was, the phone would be running the latest bootloader and modem. You can also confirm the bootloader and modem by installing the Samsung Phone Info app from the Play store.

Categories

Resources