Hi Everyone. So I took a nose dive into my first rooting experience and now I think I may have lost my phone. I'm not technically savvy enough to be screwing around with this stuff anyway so I should have stayed out but I'm hoping someone may be able to help me get my phone back. I don't care if everything is deleted.
I have a Verizon Galaxy S4 Sch-I545 which was updated to Android Version 4.3 I believe. Things went haywire when I applied the most recent update which I'm assuming was android 4.4. I'll explain what I did in hopes that someone might see where I went wrong.
I went into the Super User App and deleted root thinking if I'm going to apply the next update, I need to get rid of root. I did this and then started installing the new update.
After this, the phone was working fine but I decided I wanted to Flash the stock firmware to my phone and get back to square 1 in hopes I could speed things up and save battery life.
I followed the directions in a youtube video which i can't link because I'm a new member.
Now I'm stuck between 2 screens. I can still get into ODIN onto the downloading screen. The other screen says a problem was encountered and mentioned something about trying to restore via Kies.
This is what I get on ODIN if it helps:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also if it helps the phone itself says sw rev check fail fused 5 binary 1
Any help would be greatly appreciated,
Sounds like you are going to try the no wipe mj7 Odin file. If that doesn't work you are going to have to use the full wipe versions.
Sent from my SCH-I545 using xda app-developers app
SKELLY022782 said:
Hi Everyone. So I took a nose dive into my first rooting experience and now I think I may have lost my phone. I'm not technically savvy enough to be screwing around with this stuff anyway so I should have stayed out but I'm hoping someone may be able to help me get my phone back. I don't care if everything is deleted.
I have a Verizon Galaxy S4 Sch-I545 which was updated to Android Version 4.3 I believe. Things went haywire when I applied the most recent update which I'm assuming was android 4.4. I'll explain what I did in hopes that someone might see where I went wrong.
I went into the Super User App and deleted root thinking if I'm going to apply the next update, I need to get rid of root. I did this and then started installing the new update.
After this, the phone was working fine but I decided I wanted to Flash the stock firmware to my phone and get back to square 1 in hopes I could speed things up and save battery life.
I followed the directions in a youtube video which i can't link because I'm a new member.
Now I'm stuck between 2 screens. I can still get into ODIN onto the downloading screen. The other screen says a problem was encountered and mentioned something about trying to restore via Kies.
This is what I get on ODIN if it helps:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also if it helps the phone itself says sw rev check fail fused 5 binary 1
Any help would be greatly appreciated,
Click to expand...
Click to collapse
Look like you tried to odin stock MDK, it wouldn't work. You have to odin stock mj7 4.3 since your phone was on 4.3 MJ7, just download stock 4.3 MJ7 tar and odin it, you should be fine.
urcboss07 said:
Look like you tried to odin stock MDK, it wouldn't work. You have to odin stock mj7 4.3 since your phone was on 4.3 MJ7, just download stock 4.3 MJ7 tar and odin it, you should be fine.
Click to expand...
Click to collapse
Yeah, MDK is the first software it shipped with. Its the one with the exploit that bypasses the bootloader. Its what we all want to flash but samsung made sure we could not go back.
You first had MJ7 which is 4.3, the update was not 4.4 (we wont get that for a while) it was a maintenance release for 4.3 called MK2. MJ7 may still work but if it does not you will need the MK2 file for odin
Sent from my SCH-I545 using Tapatalk 2
Related
I rooted on VRUAME7 I am now trying to do a reset/restore. When I did a factory reset in the system, it rebooted and is now stuck on a yellow exclamation mark and says:
I tryed to put CWM on my phone. I didnt do my research so I had no idea I couldnt with ME7.. I have followed multiple forum guides that have the same exact problems as mine. also all ME7 specific. At this point... ODIN is non responsive.. and I am at the mercy of all yall haha
Odin Failed and says:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone says:
Start [224,1440]
SW REV. CHECK FAIL: FOUND: 3, Binary: 1
Once you're on ME7 you cannot Odin back to MDK. Find the ME7 Odin file and you'll be good.
Sent from my badass Galaxy S4 using Tapatalk
spc_hicks09 said:
Once you're on ME7 you cannot Odin back to MDK. Find the ME7 Odin file and you'll be good.
Sent from my badass Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2301259
I have followed this one.. downloaded the ME7 file...
It still is not working. This is not the only ME7 file I have downloaded and they have all not worked.
I have used multiple cables on the phone and multiple versions of odin.
They are all doing the same thing... I have been at this for HOURS.
I am seriously stumped....
spjohnson08 said:
http://forum.xda-developers.com/showthread.php?t=2301259
I have followed this one.. downloaded the ME7 file...
It still is not working. This is not the only ME7 file I have downloaded and they have all not worked.
I have used multiple cables on the phone and multiple versions of odin.
They are all doing the same thing... I have been at this for HOURS.
I am seriously stumped....
Click to expand...
Click to collapse
I would verify the md5 to.make sure your not getting corrupted downloads. Its pretty common, but ya like hicks said you cant go backwards in firmware which is what you tried to do the first time around. It has to be an me7 image or ml1.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
spc_hicks09 said:
Once you're on ME7 you cannot Odin back to MDK. Find the ME7 Odin file and you'll be good.
Sent from my badass Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
This is with the ME7 file...
hexitnow said:
I would verify the md5 to.make sure your not getting corrupted downloads. Its pretty common, but ya like hicks said you cant go backwards in firmware which is what you tried to do the first time around. It has to be an me7 image or ml1.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
I am now trying to use the ml1 file on http://forum.xda-developers.com/showthread.php?t=2301259
I didnt know I could do that...
How do I verify the Hash?
spjohnson08 said:
I am now trying to use the ml1 file on http://forum.xda-developers.com/showthread.php?t=2301259
I didnt know I could do that...
How do I verify the Hash?
Click to expand...
Click to collapse
Google md5 checker or md5 verifier. Its a straight forward process. The correct md5 should be posted in the thread.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ALL HELP IS MUCH APPRECIATED!!:good:
Are you sure you were on ME7? You might need to flash a newer firmware.
Sent from my NCC-1701 using Tapatalk.
Definitely need to flash newer firmware
degradedtree69 said:
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ALL HELP IS MUCH APPRECIATED!!:good:
Click to expand...
Click to collapse
This has happened to me about four times with my phone. I was able to fix through a process of Kies and Odin. It seems that if you do all that you can in Kies, as far as attempting to re-install the stock firmware. Kies has the drivers you need in order for Odin to work. You will need to run through the Kies process (it will fail), but you will get the drivers you need. You will then need to boot into download mode and do the Odin flash process. This is all assuming you have the correct files for Odin. You will need to flash the stock build afterwards unless you have a backup and are able to access safestrap which i doubt you will have.
First, apologies if this has been solved somewhere on the forum, as I haven't been able to find it.
My rooted Verizon S4 became unstable a few weeks ago; random re-starts, bizarre battery draining, inability to re-start unless connected to a charger, etc.. I did a factory reset and the problems persisted. I installed Kies and downloaded the original stock ROM, but Kies was unable to connect to my device. After poking around online, I ran Odin and tried to flash the stock ROM that way. Here's how that went:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now when I start the phone, I get the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message. Only Kies won't connect to my phone so I have no idea how to proceed.
If anyone has any suggestions, please help! I'm sure I left out some pertinent details, so let me know what else I need to tell you...
Had your phone been updated with any of the OTAs? It appears that you attempted to flash the original MDK firmware. You cannot downgrade to MDK, if the phone had been updated.
Actually I do think it got the latest update after I'd done the factory reset.
Are you saying I have the wrong tar.md5 file?
so I tried this, based on another recommendation: http://forum.xda-developers.com/showthread.php?t=2735172
the phone is at least operational again. however it's still re-starting randomly, but will not stay on after a re-start unless plugged in to a charger (battery at 80+%). not sure how the OS can still be corrupted if I just re-installed it; could something else be causing it to be so unstable?
I attempted to root my phone through Odin pushing superuser and twrp onto it as tutorials told me to do, and my phone literally goes to the boot logo and then stops. I have tried a million times to flash a stock rom back onto it but it won't push through either Odin or TWRP without error messages. It lets me flash a cyanogenmod rom through TWRP but the screen just goes back when I boot it up. Is my phone done for? Can I fix this somehow?
If you aren't able to reflash the phone with Odin, most likely, you aren't using the correct firmware. Please post your model number, the name of the file you are using, which version of Odin, and what the error you are getting is.
es0tericcha0s said:
If you aren't able to reflash the phone with Odin, most likely, you aren't using the correct firmware. Please post your model number, the name of the file you are using, which version of Odin, and what the error you are getting is.
Click to expand...
Click to collapse
I have tried using both Odin3_v3.10.6 and Odin3 v3.12.3. The files I have attempted to flash are XSG-J700HXXU2BPF9-20160629164434, CAU-J700HXXU1APA3-20160106083224, SM-J700H_J700HXXU1AOK5_J700HOLB1AOK1_5.1.1-MYM, and J700FXXU1AOL2_J700FODD1AOL1_INS_(by_firmwarefile.com).
My phone's model number is J700H/DS. The error I am receiving is <ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> J700HXXU1APA3_J700HOXY1AOL1_J700HXXU1AOL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cm.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
from Odin and
"sw. rev. check fail. device:2, binary:1" on my phone's screen
Thank you for your reply, I am actually incredibly stupid and left the DS out of my model number and was therefore getting the wrong firmwear. I fixed it.
my s3(i9305) is stuck in download mode with stock recovery on it and ive got odin, but i cant get any stock roms booted on it, cant get onto the phone, and it dont have any working firmware on it...i just want to put it back to stock asap and get the dam thing working again.
any help would be great!!
What output are you getting in odin?
Beamed in by telepathy.
shivadow said:
What output are you getting in odin?
Beamed in by telepathy.
Click to expand...
Click to collapse
the bar is blue
No, there is a 'window' on the bottom left of the app with text in it. What does that text say when you've attempted to flash the phone?. Need all of it, not just the result at the end.
The blue bar means the flash completed successfully but doesn't give any more info than that.
Beamed in by telepathy.
shivadow said:
No, there is a 'window' on the bottom left of the app with text in it. What does that text say when you've attempted to flash the phone?. Need all of it, not just the result at the end.
Beamed in by telepathy.
Click to expand...
Click to collapse
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGPE1_I9300AMNGPF1_I9300BVUGNB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sboot.bin is the bootloader so I presume that it is either locked or corrupt. I'm not sure if that is a pit error or not. You could try to find another file and hope it works but if you're absolutely sure the one you have is good then there's no point. You could try finding a stock rom that doesn't include the bootloader. Also flashing a pit file (only as a very last step) is an option but make sure it is the correct one for your specific model and region etc.
I hate recommending pit file flashing but in this case it could be viable from other reports around the site. Flashing a pit file is a last resort only, I cannot stress this enough.
Beamed in by telepathy.
shivadow said:
Sboot.bin is the bootloader so I presume that it is either locked or corrupt. I'm not sure if that is a pit error or not. You could try to find another file and hope it works but if you're absolutely sure the one you have is good then there's no point. You could try finding a stock rom that doesn't include the bootloader. Also flashing a pit file (only as a very last step) is an option but make sure it is the correct one for your specific model and region etc.
I hate recommending pit file flashing but in this case it could be viable from other reports around the site. Flashing a pit file is a last resort only, I cannot stress this enough.
Beamed in by telepathy.
Click to expand...
Click to collapse
where might i find a stock rom without a bootloader? dont fancy the pit file tbh!!
Try using different USB cables and USB 2.0 ports.
audit13 said:
Try using different USB cables and USB 2.0 ports.
Click to expand...
Click to collapse
ive only got the 1 usb port on my tablet
The sboot.bin is not flashing because the bootloader on the phone is newer than the bootloader in the ROM you are flashing, the ROM is not for your phone, and/or you need to try another computer.
It's unlikely that the bootloader is locked as AT&T and Verizon are the only two carriers I know of who lock down the bootloader.
i'm totally out of my knowledge zone here....i did do thison 1 of my old phones a few years back and some one wrote on a comment exactly how to make it stock again....but i'm buggered if i can find that post again....or thats even if the site still has that thread...can anyone point me in the right direction here please?
Ok this is what i get when i try and flash this:I9300XXUGNB5_I9300EVRGML2_EVR
which i got from sam pass and selected my exact model of phone from my country(uk) and the network i'm using....with odin v3.10
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB5_I9300EVRGML2_I9300BVUGNB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
can someone please tell me what i'm doing wrong??
so this is what i'm getting when i'm using odin v3.10 trying to install the correct firmware for my phone from sam pas and selecting the country/network
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB5_I9300EVRGML2_I9300BVUGNB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
can someone please point me in the right direction??
Your original post says the phone is a 9305 and you are flashing a 9300 ROM?
yea i'm trying to download I9305XXUFOC1 now but every site i go to its giving me a 5 hour wait time.....is there a faster way i can get it downloaded?
audit13 said:
Your original post says the phone is a 9305 and you are flashing a 9300 ROM?
Click to expand...
Click to collapse
Well spotted, didn't even occur to me..
Beamed in by telepathy.
In use sammobile.com. The download speed for free accounts is not great but I usually start the download and do something else for a while.