Related
Hi everyone, i would need some help with my s3...
I have a mobilicity galaxy s3 (sgh-t999v) and it appears that it is now bricked...
I had the latest stock version, 4.3, but wanted to try out paranoid android 4.0. My phone was rooted and working, having the latest twrp installed. I then used the recovery to do a nandroid backup on my sd card (2 actuallly) and did a factory reset. Then i flashed the rom, and it failed (saying it was not the right phone variant, so nothing installed). I did a restore of my backups, but it is now stuck in a boot lloop, even after i did another factory reset.
I tried to use odin to flash the stock firmware (the 4.1 version, the 4.3 is downloading) but it gave my an error
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
I don't know what too do, do i have a brick in my possession?
(and is it all the fault of knox, that new "feature" ??)
anyway thank you in advance
Since you had the 4.3 before, you should not have tried a 4.1 version via Odin. That will hard brick your phone.
What you should do instead is to take the Root66 of 4.3 as before and flash it via Odin. Needless to say, your phone should be in Download mode before you plug it into pc.
Galaxy s3 sgh-i747m firmware update issue
GALAXY S3 SGH-I747M virgin mobile canada
FIRMWARE UPDATE ISSUE
IT GIVES ME THAT ERROR AND stays on the screen
i used odin to restore my phone :
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
it fails everytime
plz adivse
Where did you get the firmware? I don't see where it checked the md5sum. The firmware should have the .tar.md5 extension.
Are you certain you are using the correct firmware? There are several carriers, each with their own firmware for their I747M. I don't see one specifically for Virgin Mobile though. Where did the device come from, or which carrier did it originally belong with? And which carriers firmware are you trying to flash? (As an example, Rogers firmware will not work on a Telus device.)
What firmware is currently on your phone? The error message after the aboot.mbn line tells me that you are trying to overwrite the existing bootloader with an invalid bootloader.
You probably have the 4.3 bootloader and you are trying to load a 4.1.1 or 4.1.2 bootloader. I would not try to flash the firmware again as it may brick your phone.
Boot into download mode and let us know what it says on your screen.
The i747m from Virgin would use the same firmware as the Bell version.
audit13 said:
What firmware is currently on your phone? The error message after the aboot.mbn line tells me that you are trying to overwrite the existing bootloader with an invalid bootloader.
You probably have the 4.3 bootloader and you are trying to load a 4.1.1 or 4.1.2 bootloader. I would not try to flash the firmware again as it may brick your phone.
Boot into download mode and let us know what it says on your screen.
The i747m from Virgin would use the same firmware as the Bell version.
Click to expand...
Click to collapse
in the boot mode screen:
odin mode
product name sgh-i747m
current binary: custom
system status : official
qualacomm secureboot : enable
warrantry bit: 1
bootloader ap swrev:2
the provider of the phone is virgin mobile
i tryed using the bell firmware but nothing in odin....
sw1980 said:
in the boot mode screen:
odin mode
product name sgh-i747m
current binary: custom
system status : official
qualacomm secureboot : enable
warrantry bit: 1
bootloader ap swrev:2
the provider of the phone is virgin mobile
i tryed using the bell firmware but nothing in odin....
Click to expand...
Click to collapse
Were you ever on stock 4.4.2? You have at least the 4.3 bootloader since your warranty bit is set to 1 from 0.
audit13 said:
Were you ever on stock 4.4.2? You have at least the 4.3 bootloader since your warranty bit is set to 1 from 0.
Click to expand...
Click to collapse
im not sure a 100% but i did have the latest update on the phone ...
what can i do?
Since you were on the latest stock update, you can try loading the stock Bell Mobile 4.4.2 (http://www.sammobile.com/firmwares/3/?download=31062) onto your phone using Odin.
If don't want stock, you can load a custom recovery such as Philz Touch in Odin and load a custom ROM.
audit13 said:
Since you were on the latest stock update, you can try loading the stock Bell Mobile 4.4.2 (http://www.sammobile.com/firmwares/3/?download=31062) onto your phone using Odin.
If don't want stock, you can load a custom recovery such as Philz Touch in Odin and load a custom ROM.
Click to expand...
Click to collapse
is there anyway i can get the file for free?
sw1980 said:
is there anyway i can get the file for free?
Click to expand...
Click to collapse
It's free to download. You may have to register but that is also free.
audit13 said:
It's free to download. You may have to register but that is also free.
Click to expand...
Click to collapse
it tells me bad gateway
Strange since it works for me.
Did you try a custom ROM?
You can also download firmware from http://samsung-updates.com
Its slower imo, but it is an option.
audit13 said:
It's free to download. You may have to register but that is also free.
Click to expand...
Click to collapse
thanks it worked...
sw1980 said:
thanks it worked...
Click to expand...
Click to collapse
now thanks for all your help ... now how can i root the phone so i can put custom roms on it ?
sw1980 said:
now thanks for all your help ... now how can i root the phone so i can put custom roms on it ?
Click to expand...
Click to collapse
No need to root. You can load Philz Touch via Odin and flash away. Root is required to gain administrative access to system files.
Download the latest tar version from here and flash it in Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Make sure nothing in Odin is checked except F.Reset and Audot Reboot. Place the file in the PDA box and flash it.
Hello,
I want to replace the boot loader from the stock firmware file with mj5 boot loader, so I can flash using PC Odin (don't want to use mobile Odin).
In the flashable mj5 boot loader I see 3 files: param.bin, sboot.bin and tz.img
Do I need to copy only the sboot.bin and repack the stock firmware (ignoring the param.bin and tz.img)?
Or what is the right way to flash the latest firmware without changing the bootloader using pc Odin?
Thank you!
What is the right way to flash any stock firmware and keep MJ5 bootloader using pc Odin?
bump
This is the same question that I would like to ask. Or one of them.
I am now on mj5 bootloader running custom 4.4.3 ROM (Dr.Ketan V14). I'd like to go for stock kitkat, but keep the mj5? If I flash the official 4.4.3 firmware with ODIN, I will also flash the new know bootloader right? Is it enough to flash the official firmware and bootloader ath the same time in ODIN? Will this result with official 4.4.3 with mj5 bootloader and without knox? Will I be able to root it?
Thanks,
Cheers,
estu
Hi everyone, looking for some guidance here. Ive checked different solutions but I think I've got a unique combination of "dun goof'd"
History:
I have a Canadian (Bell) SGH-I747M that is rooted and was running the latest cyanogen.
Wanted to lend it to a friend who lost his job and needed a phone but he had a deal through rogers and my phone was locked to Bell.
I tried a few of the unlock code steps but I needed to be 4.1.2 or lower for it to work I heard so I tried installing 4.1.2 and thats where it went wrong. I did a firmware update to back it down and mid update it failed.
I can get it into download mode but not recovery. Letting it boot normally gives the message "Firmware upgrade encountered an issue. Please select recovery mode in Keys and try again" I don't think Keys works with cyanogen and even if it did, there is no serial # sticker behind the battery and since I can't boot into settings, I don't know the SN.
When I put it in download mode and try Odin using stockROMS.net oldest or newest image, Odin fails and the phone message is:
ODIN SW REV CHECK FAIL : Fused 2 > Binary 0
So long story short, any help is sincerely appreciated, my ideal state would be a working phone thats unlocked so my buddy can use it. IF that means an older OS, all good. Can I even fix this?? If you need more info I'll keep checking in... THANKS!
You cannot downgrade if your phi e has ever had the 4.3 or higher bootloader.
Fix the phone by booting into download mode and flashing the latest stock rom from sammobile.com.
I can boot into download mode but Odin is erroring out.
I tried the sam mobile stock rom and another, I tried another usb cable and different port.
SGH-I747M (Canada) Bell 4.4.2 KitKat I747MVLUFNH2 2014 July
The error on ODIN is:
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
Error on the phone is SW REV CHECK FAIL : FUSED 2 > Binary 0
You must be flashing an older bootloader because it fails when it gets to aboot.mbn.
Im following this thread... Odin still errors out and I'm using the most current bootloader (I think) for the S3 I747M on Bell
http://forum.xda-developers.com/showthread.php?t=2549068
Are your trying to flash a 4.1.1 or 4.1.2 rom? Can't be done if you have a 4.3 or newer bootloader.
audit13 said:
Are your trying to flash a 4.1.1 or 4.1.2 rom? Can't be done if you have a 4.3 or newer bootloader.
Click to expand...
Click to collapse
4.3 ROM, newest one.
The newest ROM is 4.4.2.
What bootloader version is on your phone?
How do I tell??
Try flashing a stock 4.3 ROM from sammobile.com for your i747m.
If Odin fails when flashing aboot.mbn, it's probably because the 4.3 ROM you are trying to flash has an older bootloader that the one currently on your phone.
If flashing the 4.3 ROM via Odin fails, copy the latest CM11 ROM and the corresponding Gapps to your internal or external memory, flash the latest Philz Touch recovery for the d2lte via Odin, boot into recovery, flash CM11, Gapps, boot, install Samsung Phone Info App, run app, look for the bootloader and modem version.
audit13 said:
Try flashing a stock 4.3 ROM from sammobile.com for your i747m.
If Odin fails when flashing aboot.mbn, it's probably because the 4.3 ROM you are trying to flash has an older bootloader that the one currently on your phone.
If flashing the 4.3 ROM via Odin fails, copy the latest CM11 ROM and the corresponding Gapps to your internal or external memory, flash the latest Philz Touch recovery for the d2lte via Odin, boot into recovery, flash CM11, Gapps, boot, install Samsung Phone Info App, run app, look for the bootloader and modem version.
Click to expand...
Click to collapse
I tried Philz and I can boot into recovery now Progress!
That being said the CM11 is stuck on the boot logo animation, tried re-installing as well as the CM Nightly same result.
Did full wipe etc still stuck.
Are you wiping the cache, system, and data before flashing CM11 for the d2lte? Are you running the latest version of Philz?
Try CM12 if CM11 doesn't work.
hey guys
im trying to update my s3 firmware from 4.1 to 4.3 using odin
i followed this guys tutorial
https://www.youtube.com/watch?v=eJkHx0zb-Bc
i literally have the exact same tech except i didnt start with 4.3, i started with 4.1
i used the odin to flash on the 4.3 thing, and when my phone restarted it showed an andoid robot with its chest open with blue circles and a blue progress bar
then after that just nothing. its completely black and no matter what i do it doesnt turn on or do anything
the only activity i can sense is that when i plug in the USB into the phone, the computer detects it
please help!!
heres the odin log thing
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img.ext4
<ID:0/005> NON-HLOS.bin
<ID:0/005> recovery.img
<ID:0/005> rpm.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> system.img.ext4
<ID:0/005> tz.mbn
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
You have the i747m or i747? Where did you get the 4.3 ROM?
audit13 said:
You have the i747m or i747? Where did you get the 4.3 ROM?
Click to expand...
Click to collapse
Im not sure how to determine that
i got the 4.3 ROM from the youtube guide
I747UCUEMJB_2024954_REV04_user_low_ship
this is the file
Does your computer detect the phone in device manager as "qusbload" or something similar? If it does, you will need to try and debrick your phone using a debrick image and an sd card (http://forum.xda-developers.com/showthread.php?t=2549068).
Were you running stock 4.1.1 before you flashed?
Under the battery is a label attached to the phone. What is the model #? Is your s3 from AT&T?
audit13 said:
Does your computer detect the phone in device manager as "qusbload" or something similar? If it does, you will need to try and debrick your phone using a debrick image and an sd card (http://forum.xda-developers.com/showthread.php?t=2549068).
Were you running stock 4.1.1 before you flashed?
Under the battery is a label attached to the phone. What is the model #? Is your s3 from AT&T?
Click to expand...
Click to collapse
SGH I474
it IS from At&t
i dont remeber specifically which version
but it WAS 4.1
yes it says
qusbload
The phone is bricked because something seems to have gone wrong during the flash process. Most likely, something to do with the bootloader.
I read the comments on YouTube and it looks like a few people hard bricked their phone using this method.
Your phone is probably hard bricked since it does not boot at all. I assume you tried pulling and re-inserting the battery and charging the battery.
A USB jig, Odin, or Kies will probably not help. You will have to try the debrick method I linked or have it repaired via jtag.
audit13 said:
The phone is bricked because something seems to have gone wrong during the flash process. Most likely, something to do with the bootloader.
I read the comments on YouTube and it looks like a few people hard bricked their phone using this method.
How is your phone detected in Windows device manager?
Click to expand...
Click to collapse
it says qusbload
which guide do you recommend following to update my firmware correctly?
You can try this: http://forum.xda-developers.com/showthread.php?t=2549068 or this: http://forum.xda-developers.com/showthread.php?t=2660566
I have never used a de-brick method because I have never had to de-brick an s3.
I found this on youtube: https://www.youtube.com/watch?v=-RTAbLBVfMI
audit13 said:
You can try this: http://forum.xda-developers.com/showthread.php?t=2549068
I have never used a de-brick method because I have never had to de-brick an s3.
Click to expand...
Click to collapse
Can you explain to me what you think happened?
i mean i thought you werent supposed to go from 4.3 to 4.1 i thought i was going up
also im asking how you UPgrade fro 4.1 to 4.3 correctly
Thanks
Did you confirm the bootloader on your phone before upgrading? Maybe the phone needed to have a particular bootloader before applying the update.
Some people did brick their phones according to the youtube comments. Also, it looks like the 4.3 file that was on xda has been pulled because of possible bricking.
Try the debrick method as it is the only choice available unless you want to pay and have it repaired via jtag.
audit13 said:
Did you confirm the bootloader on your phone before upgrading? Maybe the phone needed to have a particular bootloader before applying the update.
Some people did brick their phones according to the youtube comments. Also, it looks like the 4.3 file that was on xda has been pulled because of possible bricking.
Click to expand...
Click to collapse
i dont know what "confirming bootloader on phone before upgrading" means
ahhh im so lost, someone save me T_T
im reading the link you sent me but the its not organized well in a way i know what is i474m or i474
The i747 is the AT&T version of the s3. The i747m is the Canadian version of the s3.
You need debrick images for the AT&T i747.
Before flashing anything to the s3, it is important to know the bootloader version of your phone. If the bootloader on your phone before the flash was newer than the 4.3 mjb version you flashed, this will brick the phone.
The debrick threads can be confusing which is why it is important to read and understand how your phone works with its software components.
Follow the instructions for the AT&T i747.
audit13 said:
The i747 is the AT&T version of the s3. The i747m is the Canadian version of the s3.
You need debrick images for the AT&T i747.
Before flashing anything to the s3, it is important to know the bootloader version of your phone. If the bootloader on your phone before the flash was newer than the 4.3 mjb version you flashed, this will brick the phone.
The debrick threads can be confusing which is why it is important to read and understand how your phone works with its software components.
Follow the instructions for the AT&T i747.
Click to expand...
Click to collapse
so the debrick brought my phone back to download mode! yay!
next i have to put the 4.3 bootloaders, a 4.3 rom, a 4.3 kernel and a 4.3 modem
im not sure how i should do this
Find the tar version of mjb bootloader and mjb modem in the general section of this forum and flash them using Odin.
Bootloader: http://forum.xda-developers.com/showthread.php?t=2321310
Then flash the latest TWRP custom recovery for the d2lte. Then flash the latest cm11 for your phone via TWRP.
This will hopefully get your phone up and running with a custom ROM.
audit13 said:
Find the tar version of mjb bootloader and mjb modem in the general section of this forum and flash them using Odin.
Bootloader: http://forum.xda-developers.com/showthread.php?t=2321310
Then flash the latest TWRP custom recovery for the d2lte. Then flash the latest cm11 for your phone via TWRP.
This will hopefully get your phone up and running with a custom ROM.
Click to expand...
Click to collapse
im following the instructions for the link you gave me
im stuck on this step:
When I first got mine booting again it would only boot with the micro SD card that has the .IMG file on it in the phone and only after a battery pull. What I did was boot back to recovery, remove my SD card and I had a spare SD card I used to flash the files with, I inserted it told TWRP to mount the new SD card, flashed the bootloader again and it seems to have cured my phones malfunctions. It now boots on its own like nothing ever happened. It may not happen like this for you???
my phone wont boot without the debrick SD card.
im not sure what this is trying to tell me to do
whats your take on it?
also in recovery mode, there is a option for factory reset.
is factory reset going to help at all with this?
I would not think that a factory reset would help since it only wipes the data and cache partitions.
So everything works again? Sounds like it was a bootloader issue.
audit13 said:
I would not think that a factory reset would help since it only wipes the data and cache partitions.
So everything works again? Sounds like it was a bootloader issue.
Click to expand...
Click to collapse
hey so i did the phones software update in about devices and it put me up to 4.4.1 kitkat
so im where i want to be.
if i want to install cyanogen mod, do you think following this link is good?
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
Thanks for the help
The latest is 4.4.2.
The easiest way would be to install a custom recovery usi Odin, backup the existing rom, wipe cache, data, system, install cm and gapps.
Use ROMs for the d2lte.
audit13 said:
The latest is 4.4.2.
The easiest way would be to install a custom recovery usi Odin, backup the existing rom, wipe cache, data, system, install cm and gapps.
Use ROMs for the d2lte.
Click to expand...
Click to collapse
can you give me a reputable URL that shows me how to do this?
Hopefully, the links still work: http://forum.xda-developers.com/showpost.php?p=60813687&postcount=3