Develop Bugs

[Solved] is there full rom 4.1.1 for i747

can any one provide me with full rom 4.1.1(many files ROM include bootloader ) for i747 as the device was bricked

toni.50 said:
can any one provide me with full rom 4.3 for i747 as the device was bricked
Click to expand...
Click to collapse
If it is on AT&T you need to find a custom... If you have a Canadian or Mexican SGH-I747M then you can flash via Odin.
What exactly is your definition of bricked? What is the phone doing what is the phone not doing, please be specific on what you did to "brick" your phone.
Once you verify which model phone you have and a description of what it is doing and how it got that way we might be able to point you in the right direction.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

sorry if my post is not clear , i have i747 AT&T on rom 4.1.1 (I747UCDLK3) I TRY TO root and unlock boot loader i used motochopper for root and EZ-unlock 1.2 for unlock bootloader but after restart nothing work !!! no boot no odin no no ,,, i try to use the sd card with debrick.img and yes it is workking but i have to keep the card... now i need the full rom with bootloader to fix this if any one have the 4.1.1 it will be better but i need the full version with bootloader, any help please ???

Maybe you can try using Odin to flash a pre-rooted AT&T 4.1.1 ROM from here: http://forum.xda-developers.com/showthread.php?t=1739426

toni.50 said:
sorry if my post is not clear , i have i747 AT&T on rom 4.1.1 (I747UCDLK3) I TRY TO root and unlock boot loader i used motochopper for root and EZ-unlock 1.2 for unlock bootloader but after restart nothing work !!! no boot no odin no no ,,, i try to use the sd card with debrick.img and yes it is workking but i have to keep the card... now i need the full rom with bootloader to fix this if any one have the 4.1.1 it will be better but i need the full version with bootloader, any help please ???
Click to expand...
Click to collapse
EZ- unlock is for the T999 it is what bricked your phone. Our bootloader is unlocked up to the 4.3 MJB bootloader. As long as your phone has never been on the MJB bootloaders go to www.sammobile.com and go to the firmware tab in the search box enter "i747" Then find the rom you want download it, insert your debrick card get into odin/download mode and flash your heart out.
Use the stickies guide for rooting your phone cf autoroot works well before 4.3, do not flash anything if you're unsure if it is for your phone, ask if it supports your model. Not all galaxy s3's are created equal.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Thanks every one i find soultion by myself yestrday thanks all >>> :laugh::laugh::laugh:

[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.

[Q] Help!! ROM flashing problems

Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/

dreammaster252 said:
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
Click to expand...
Click to collapse
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486

Larry2999 said:
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help

dreammaster252 said:
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
Click to expand...
Click to collapse
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991

Larry2999 said:
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?

dreammaster252 said:
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
Click to expand...
Click to collapse
just to confirm, you re on ucuemjb bootloader, and installed/running Task650 4.4.4 rom 7.21.2014 (at this writing thats the latest update for the rom)
right?
sorry last time i tried to flash task650 rom, i got errors concerning the bootloader, went back to CM11 which has been my go-to-go rom and everything works fine, after you respond i will flash and get back to you on the network issues
thanks

Sending 8$ on pp for de-brick on Teamviewer

Title says all, i have an att SGH-I747 and i tried to install a custom rom without the phone being rooted (didnt know that was a requirement) and the original stock was 4.3 and i was trying to get it to 4.1 . after doing extensive research ive tried countless different files and such to restock the phone but nothing has helped because on odin, when i hit start, it goes unsuccessful to do auth being bad or something like that. so if someone wants to help a fellow brother out please dont hesitate. add me on skype godlypk101

Can you get into download mode or recovery?
FYI: if you were on stock 4.3 bootloader, trying to get back to stock 4.1.1 can brick your phone.

yes i can

Here's what I would do to at least get a working ROM on the phone:
1) copy the latest version of d2lte cm11 to your external SD card: https://download.cyanogenmod.org/?device=d2lte;
2) flash the latest tar.md5 version of Philz Touch from here: https://goo.im/devs/philz_touch/CWM_...Edition/d2lte/ in the PDA box of Odin;
3) reboot to recovery and flash CM11.

ok, now what if i dont have an ext sd card :S

You had the stock 4.3 ROM on your phone before attempting to downgrade to 4.1.1, correct?
If that's the case, this may help: http://forum.xda-developers.com/showthread.php?t=2722660

yes, will try that method to see if it fixes anything.

in that pack theres 5 files and they start with, AP, BL, CP, CSC, D2 (Pit) where i put these on odin?

UPDATE: Put all the files in the correct spot, started the fix in odin and lets hope it works

ok so now that the phone is working, what are the steps im supposed to take in order to unlock this bad boy? should i refer to a method on xda on custom roms or should i go buy a code from a third party website?

So your phone booted on stock 4.3?
If the phone ever had the 4.3 bootloader, you cannot unlock the phone for free. You will have to purchase an unlock code.

I haven't tried but I think of your rooted then use cm boot loader then mount all partition and wipe then use cm to load new or old system. Think of it like a pc format then install. Simple

Bricked my S4 SGH-M919 :( Please help?

Hi all,
I've kind of backed myself into a corner here after a bit of "experimenting"
I just purchased an S4 SGH-M919, came with stock 4.2.2 Jellybean.
- Opened it up and rooted it via auto-root + Odin.
No issues.
Then instead of manually flashing a rom, I downloaded a play store app called 'Recovery Tools', and tried to flash TWRP onto the phone.
-Stuck at Samsung screen with blue 'booting recovery...' forever.
I then (stupidly?) tried to flash 4.4.2 onto the phone. *not sure if this is stupid because I read T-Mobile has an unlocked bootloader?
So flashing 4.4 T-Mobile Galaxy S4 Stock Firmware (4.4.2 - M919UVUFNB4) PASSES with odin, but the phone is still 'messed up'.
I can access recovery mode, but the phone will not boot past the 'Samsung' logo, and even after a factory data reset and deleting users.
I've also tried flashing back to 4.2.2, and odin fails.
Please help I can't afford another device and I'm now phoneless. Not sure where to go from here and could really use some direction..

Just adding that I think this happened because I accidentally flashed the most recent version of TWRP which doesn't work on the s4.
At this point I can't get any stock ROM to load.
Any idea folks? Any guidance greatly appreciated here..

You might want to try installing one of the cm or aosp based jflte roms. they seem to load easier. After that you can try another rom if you need to. Make sure you are giving it enough time to boot up the first time after a flash. It can commonly take 10 minutes for a stock touchwiz rom to load first time around. Edit: or just odin the stock nk2 firmware from here and start over. http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508

ultrafta said:
You might want to try installing one of the jflte roms. they seem to load easier. After that you can try another rom i you need to. Make sure you are giving it enough time to boot up the first time after a flash. It can commonly take 10 minutes for a stock touchwiz rom to load first time around.
Click to expand...
Click to collapse
Screen just goes black, IF it gets past 'Samsung' logo, depending on what build I'm flashing. I was once able to get all the way into setup, then the phone completely went black again. Pretty sure it's not a hw issue because the phone was working fine until I started all of this.
Can I just load a jflte rom via Odin? That's about all I'm able to do currently.

At this point I would odin nk2 firmware. after that odin twrp.

ultrafta said:
At this point I would odin nk2 firmware. after that odin twrp.
Click to expand...
Click to collapse
Okay Ultra, appreciate your advice - I'll try this now.
To confirm - after flashing nk2, should the phone be able to fully boot? Or will I have to twrp first before I can expect it to fully boot?
Thanks again

It will boot without twrp
---------- Post added at 11:06 PM ---------- Previous post was at 11:02 PM ----------
Make sure you are using a very good condition usb cable. I've had some serious odin frustrations due to a poor usb cable

ultrafta said:
It will boot without twrp
Click to expand...
Click to collapse
That worked. Thanks so much!
Now I've already rooted with cf-auto once again, I shouldn't have any problem loading TWRP now right?

Right. Should be good to go

Stay away from twerp, use CWM it's more reliable and it won't brick phones. Those extras cooked into twrp make it flaky.
Pp.

VeryHappySlug said:
Hi all,
I just purchased an S4 SGH-M919, came with stock 4.2.2 Jellybean.
...[...]...
So flashing 4.4 T-Mobile Galaxy S4 Stock Firmware (4.4.2 - M919UVUFNB4) PASSES with odin, but the phone is still 'messed up'.
I can access recovery mode, but the phone will not boot past the 'Samsung' logo, and even after a factory data reset and deleting users.
I've also tried flashing back to 4.2.2, and odin fails.
Click to expand...
Click to collapse
Would anyone confirm if to flash via Odin from 4.4.X to 4.2.2 would require the OP to first flash the bootloader from a 4.4.X bootloader to a 4.2.2 bootloader?

XDAUserWork said:
Would anyone confirm if to flash via Odin from 4.4.X to 4.2.2 would require the OP to first flash the bootloader from a 4.4.X bootloader to a 4.2.2 bootloader?
Click to expand...
Click to collapse
Guys.. my battery was dead the entire time.
All is resolved.
*Slithers away*

XDAUserWork said:
Would anyone confirm if to flash via Odin from 4.4.X to 4.2.2 would require the OP to first flash the bootloader from a 4.4.X bootloader to a 4.2.2 bootloader?
Click to expand...
Click to collapse
No. That is not how it works

ultrafta said:
No. That is not how it works
Click to expand...
Click to collapse
Would you please elaborate on the reason for how it does not work that way?
Specifically, would you recommend what way you would go about it?

XDAUserWork said:
Would anyone confirm if to flash via Odin from 4.4.X to 4.2.2 would require the OP to first flash the bootloader from a 4.4.X bootloader to a 4.2.2 bootloader?
Click to expand...
Click to collapse
XDAUserWork said:
Would you please elaborate on the reason for how it does not work that way?
Specifically, would you recommend what way you would go about it?
Click to expand...
Click to collapse
Read the first post. He odined 442 to it. You cant go backwards. After that point it is best to just update to the latest complete firmware bootloader and all, just as he did and succeeded.
---------- Post added at 02:26 PM ---------- Previous post was at 01:45 PM ----------
Everthing over 4.3 has knox bootloader. and prevents downgrading. However i don't know why anyone would want to run 422 these days. The phones run smoothest with the latest nk2. And everyone overreacts about the m919 knox bootloader.

ultrafta said:
Everthing over 4.3 has knox bootloader. and prevents downgrading. However i don't know why anyone would want to run 422 these days. The phones run smoothest with the latest nk2. And everyone overreacts about the m919 knox bootloader.
Click to expand...
Click to collapse
Indeed, however if someone strongly preferred to downgrade from 4.4.2 (M919UVUFNB4) to 4.2.2 (M919UVUAMDL) would they need to first flash the 4.4.2 bootloader with the 4.2.2 bootloader, thereby replacing the 4.4.2 bootloader with the 4.2.2. bootloader, in order to then allow Odin to successfully flash from 4.4.2 (M919UVUFNB4) to 4.2.2 (M919UVUAMDL) - is that correct?