Related
The title says it all.
After a number of successful flashes. the last one of which was to cleanrom 1.5 my wifi was not working.
I then went to use the lokifyed 3way to to return to stock and begin again.
The process died in mid download (1st time ever)
Then powered down. rebooted phone (no recovery... it is gone.)
I can get to download or "firmware upgrade encountered an issue"
tried 3 way tool again to return to stock
"no pit partition" a few times
now:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
Am I SOL?
about to try the CASUAL tool to see if that works...
SaltyFoam said:
The title says it all.
After a number of successful flashes. the last one of which was to cleanrom 1.5 my wifi was not working.
I then went to use the lokifyed 3way to to return to stock and begin again.
The process died in mid download (1st time ever)
Then powered down. rebooted phone (no recovery... it is gone.)
I can get to download or "firmware upgrade encountered an issue"
tried 3 way tool again to return to stock
"no pit partition" a few times
now:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
Am I SOL?
about to try the CASUAL tool to see if that works...
Click to expand...
Click to collapse
An emergency firmware recovery with KIES would fix it but then you'd have MF3. The recovery partition has been wiped. The ODIN flash succeeds, but the last step of booting into recovery to wipe doesn't happen because there is no recovery. Try flashing a recovery with ODIN. If you can access it, just flash a ROM.
Try flashing a recovery with ODIN.
repartition an option?
GiantBallSack said:
An emergency firmware recovery with KIES would fix it but then you'd have MF3. The recovery partition has been wiped. The ODIN flash succeeds, but the last step of booting into recovery to wipe doesn't happen because there is no recovery. Try flashing a recovery with ODIN. If you can access it, just flash a ROM.
Try flashing a recovery with ODIN.
Click to expand...
Click to collapse
Question:
Can I use ODIN to repartition with the "SGS-I337.pit" file? Would that fix the partitions and then I could rerun the 3way tool?
SaltyFoam said:
Question:
Can I use ODIN to repartition with the "SGS-I337.pit" file? Would that fix the partitions and then I could rerun the 3way tool?
Click to expand...
Click to collapse
Make that your last resort before Kies or JTAG. Try flashing a recovery in ODIN first.
Thanks. Off to find a odin'able recovery...
GiantBallSack said:
Make that your last resort before Kies or JTAG. Try flashing a recovery in ODIN first.
Click to expand...
Click to collapse
Thanks. Will search for a odin usable recovery.
Will report back later...
Do you think this will work?
GiantBallSack said:
Make that your last resort before Kies or JTAG. Try flashing a recovery in ODIN first.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2360859&page=2
Sound like a slightly similar situation...
maybe...
SaltyFoam said:
http://forum.xda-developers.com/showthread.php?t=2360859&page=2
Sound like a slightly similar situation...
maybe...
Click to expand...
Click to collapse
Don't mess with that, it's MF3
GiantBallSack said:
Don't mess with that, it's MF3
Click to expand...
Click to collapse
So is cleanrom 1.5 which is where this all started... i.e. cleanrom 1.5 wireless not working then 3 way tool to return to stock (mdl)...
SaltyFoam said:
So is cleanrom 1.5 which is where this all started... i.e. cleanrom 1.5 wireless not working then 3 way tool to return to stock (mdl)...
Click to expand...
Click to collapse
Yes but those files are the MF3 aboot, and sbl1, 2, and 3... It would be just like accepting the OTA...
Did you try ODIN a recovery?
Yeah. Tried odin recovery,
tried the pit file.
tried casual
tried several other things did a lot of reading.
All to no avail...
So in choosing between an expensive paper weight with a yellow triangle I am going the Keis way and hoping that is recovers the phone. I am confident that someone will find an exploit... if not then.. well it could be worse: I could be using a iphone...
Thanks for your help. I post the results of keis...
SaltyFoam said:
So is cleanrom 1.5 which is where this all started... i.e. cleanrom 1.5 wireless not working then 3 way tool to return to stock (mdl)...
Click to expand...
Click to collapse
GiantBallSack said:
Yes but those files are the MF3 aboot, and sbl1, 2, and 3... It would be just like accepting the OTA...
Did you try ODIN a recovery?
Click to expand...
Click to collapse
listen to GiantBallSack. an MF3-based rom or rooted-stock MF3 are completely different that OTA in that you still retain maneuverability/root
SaltyFoam said:
Yeah. Tried odin recovery,
tried the pit file.
tried casual
tried several other things did a lot of reading.
All to no avail...
So in choosing between an expensive paper weight with a yellow triangle I am going the Keis way and hoping that is recovers the phone. I am confident that someone will find an exploit... if not then.. well it could be worse: I could be using a iphone...
Thanks for your help. I post the results of keis...
Click to expand...
Click to collapse
It should fix it, I had to fix one an S3 ROM was flash to, and Kies did the trick.
i'm not sure what to think about a thread involving a GiantBallSack and SaltyFoam...
...
xBeerdroiDx said:
listen to GiantBallSack. an MF3-based rom or rooted-stock MF3 are completely different that OTA in that you still retain maneuverability/root
Click to expand...
Click to collapse
First off: I did a lot of reading of your knowledge share... a good education: Thanks.
Yes I understand. what you are saying except that I am out of ideas.
Tried a stock recovery (tar file) in odin...
tried original firmware.
Tried various tools.
Tried repartitioning
tried some other tools...
and as of 10 seconds ago keis also will not repair it...
So:
To sum up
I can go into download mode.
I can not go into recovery (I will try a few more times)
straight boot goes to firmware error...
Any other ideas?
Thanks for listening...
SaltyFoam said:
First off: I did a lot of reading of your knowledge share... a good education: Thanks.
...
So:
To sum up
I can go into download mode.
I can not go into recovery (I will try a few more times)
straight boot goes to firmware error...
Any other ideas?
Thanks for listening...
Click to expand...
Click to collapse
Flashing ODIN-CWN6.6.1.2.tar (through odin results in:
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ODIN of "I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5"
returns:
same as above...
I am at a lose... will keep reading...
Thanks.
SaltyFoam said:
Flashing ODIN-CWN6.6.1.2.tar (through odin results in:
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ODIN of "I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5"
returns:
same as above...
I am at a lose... with keep reading...
Thanks.
Click to expand...
Click to collapse
Do have the PIT? If so, put it in the PIT field and try again. If it fails, do the same with the PIT and check repartition.
---------- Post added at 02:47 AM ---------- Previous post was at 02:41 AM ----------
xBeerdroiDx said:
i'm not sure what to think about a thread involving a GiantBallSack and SaltyFoam...
Click to expand...
Click to collapse
If we made a ROM together it could be SaltyFoam from GiantBallSack
GiantBallSack said:
Do have the PIT? If so, put it in the PIT field and try again. If it fails, do the same with the PIT and check repartition.
---------- Post added at 02:47 AM ---------- Previous post was at 02:41 AM ----------
If we made a ROM together it could be SaltyFoam from GiantBallSack
Click to expand...
Click to collapse
ROTFL!!! :laugh:
In any case: with the pit file (re-partition check and unchecked) the result is the same...
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
SaltyFoam said:
ROTFL!!! :laugh:
In any case: with the pit file (re-partition check and unchecked) the result is the same...
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I can probably build the equivalent of that MF3 kies unbrick with MDL files... I'll need a little time, all I currently have is the aboot.mbn, and tz.mbn, both extracted from a stock ROM
hmmmm.
See the attached image... this makes me think that a odin flashable mf3 stock rom might work... does such a thing yet exist?
Interesting...
GiantBallSack said:
I can probably build the equivalent of that MF3 kies unbrick with MDL files... I'll need a little time, all I currently have is the aboot.mbn, and tz.mbn, both extracted from a stock ROM
Click to expand...
Click to collapse
What can I do to help?
Besides testing...
So I followed this thread exactly, for my rogers I337M
[SGH-I337M] CF-Auto-Root [CANADIAN MODELS ONLY]
http://forum.xda-developers.com/showthread.php?t=2293800&highlight=cf+auto+root
and after I started ODIN after selecting the .tar.md5
I got this.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltecan-jfltevl-sghi337m.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
And in it says fail on ODIN. And now when I boot up I can't get to my stock OS
only to a screen where it says, "Firmware upgrade encountered an issue. Please Select recovery mode in Kies & try again."
I Can't use my S4 any more . I was wondering if it was because I had a locked bootloader, but the I337M varient should be unlocked right?
I also had the new MG1 firmware before I tried all this, but I saw alot of other MG1 users used this method.
PLEASE HELP, I would be forever grateful.
Are you sure you used the correct version for your model and are you sure you didn't have "repartition" checked in ODIN?
scott14719 said:
Are you sure you used the correct version for your model and are you sure you didn't have "repartition" checked in ODIN?
Click to expand...
Click to collapse
Completely sure.
Can you boot into download mode? If so I would Odin stock firmware and see if that helps. I have used the auto root on a couple different devices and have had no issues.
Sent from my Nexus 10
mymusicathome said:
Can you boot into download mode? If so I would Odin stock firmware and see if that helps. I have used the auto root on a couple different devices and have had no issues.
Sent from my Nexus 10
Click to expand...
Click to collapse
ok so I got the latest firmware for my device.
Build Date: 01.07.2013 -> Region: RWC (Canada (Rogers)) PDA: I337MVLUAMG1 Changelist: 897376 Android: 4.2.2
I got it from this thread
http://forum.xda-developers.com/showthread.php?t=2269304&highlight=flash+stock+firmware
I got back into the download mode (VOLDOWN/HOME/PWR) with the android icon where it says. "Downloading... Do not turn off target!!" plugged in my device got into odin put the stock firmware in PDA and ran then got this.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMG1_I337MOYAAMG1_I337MVLUAMG1_HOME.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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
and my device still doesn't work.
Try it a few more times. I've used odin where I got "failed" and then after a few tries got it to work.
jd1639 said:
Try it a few more times. I've used odin where I got "failed" and then after a few tries got it to work.
Click to expand...
Click to collapse
I've tried it 10 times so far with different versions of ODIN just to be sure.. No change. Would me having a USB 1.0 have anything to do with it?
I really have no idea what to do.. I have 1 year warranty left with this phone, and me trying to CF-Auto root was the only thing I've done that could have voided my warranty, but it failed and now that I'm stuck would I still be okay if I took it in for warranty?
PromyD said:
I've tried it 10 times so far with different versions of ODIN just to be sure.. No change. Would me having a USB 1.0 have anything to do with it?
Click to expand...
Click to collapse
Try it on a different computer.
jd1639 said:
Try it on a different computer.
Click to expand...
Click to collapse
agreed. or at least a different usb port. are you using the cable that came with your device? i'm assuming you had usb debugging switched on.
So i've tried it on another computer, but since my device is in download mode it doesn't install any samsung drivers to properly identify and read the S4, so it doesn't work. Can anyone please give me some direct links to download the proper usb drivers on windows for my S4.
http://lmgtfy.com/?q=samsung+galaxy+s4+drivers
Thanks to everyone that helped me troubleshoot and gave me options in figuring out the next step. I used another computer and installed the drivers on to that computer ran odin and cf auto root method and it worked like a charm. :victory:
On the first computer I used, I'm almost completely sure I had the wrong S4 Drivers installed and thats why it didn't work.
Thanks to: scott14719, mymusicathome, jd1639, xBeerdroiDx
Lo
PromyD said:
Thanks to everyone that helped me troubleshoot and gave me options in figuring out the next step. I used another computer and installed the drivers on to that computer ran odin and cf auto root method and it worked like a charm. :victory:
On the first computer I used, I'm almost completely sure I had the wrong S4 Drivers installed and thats why it didn't work.
Thanks to: scott14719, mymusicathome, jd1639, xBeerdroiDx
Click to expand...
Click to collapse
You're welcome. Glad to have helped. It's good you got your phone working again.
Ps, nvm
SGH I337M Bricked as well
I tried to odin to stock firmware after installing wicked rom v7 and KT-SGS4 kernel. the reason I wanted to odin to stock was because wicked rom kept disconnecting my wifi so I gave up. so after flashing it failed (of course) and I couldnt boot into android: "firmware update has encountered an issue..."
here is what odin said after failure:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
This happens all the time for me when reodining to stock, but for some reason, THIS time, it didn't. tried 11 times and got pissed off.
someone PLEASE PLEASE HELP ME!!
Copy a rooted i337M rom to your SD card. Boot into recovery , wipe and flash.
Sent from my SGH-I337M using XDA Premium 4 mobile app
I cannot boot into recovery.
Hey Overclock,
Can you confirm whether your knox flag tripped? and what build are you on? I just want to make sure the knox doesnt trip when rooting
OverclockDaS4 said:
I tried to odin to stock firmware after installing wicked rom v7 and KT-SGS4 kernel. the reason I wanted to odin to stock was because wicked rom kept disconnecting my wifi so I gave up. so after flashing it failed (of course) and I couldnt boot into android: "firmware update has encountered an issue..."
here is what odin said after failure:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
This happens all the time for me when reodining to stock, but for some reason, THIS time, it didn't. tried 11 times and got pissed off.
someone PLEASE PLEASE HELP ME!!
Click to expand...
Click to collapse
Take a deep breath, and try another cable. I find a large portion of flash errors are caused by junky usb cables. If that fails, try another usb port and another pc entirely, if possible. Let us know some more info, someone has already asked, more details the better. Good luck.
Sent from my SGH-I337M
pyrexid said:
Hey Overclock,
Can you confirm whether your knox flag tripped? and what build are you on? I just want to make sure the knox doesnt trip when rooting
Click to expand...
Click to collapse
Knox does trip if you root.... not sure there is any method that doesn't...... guess if its important... do some research.. I couldn't find one when I did mine... used CF-auto..... on i337m
Hi guys,
Please help !
I have a I9505. My phone is stuck in boot with message "Firmware upgrade encountered an issue. Please select recovery mode in Kies ".
When I try Kies emergency recovery noting happens.
I tried to boot in custom recovery (I had TWRP) and no luck.
Download mod is working. I tried to install sock rom with odin (PDA - one tar.md5 file), but it fail.
chemarko said:
Hi guys,
Please help !
I have a I9505. My phone is stuck in boot with message "Firmware upgrade encountered an issue. Please select recovery mode in Kies ".
When I try Kies emergency recovery noting happens.
I tried to boot in custom recovery (I had TWRP) and no luck.
Download mod is working. I tried to install sock rom with odin (PDA - one tar.md5 file), but it fail.
Click to expand...
Click to collapse
If u hv nandroid backup. Try restoring it. It will return u to last stable condition of your phone
re: flash stock firmware
chemarko said:
Hi guys,
Please help !
I have a I9505. My phone is stuck in boot with message "Firmware upgrade encountered an issue. Please select recovery mode in Kies ".
When I try Kies emergency recovery noting happens.
I tried to boot in custom recovery (I had TWRP) and no luck.
Download mod is working. I tried to install sock rom with odin (PDA - one tar.md5 file), but it fail.
Click to expand...
Click to collapse
Most likely you tried to flash the wrong firmware/rom for your phone and that's why it failed.
Your best bet is to download the official stock firmware from http://SamMobile.com
and Odin flash it. Make 100% sure that the firmware you download is the right one
for your specific phone's model.
Good luck!
Tried everything
Misterjunky said:
Most likely you tried to flash the wrong firmware/rom for your phone and that's why it failed.
Your best bet is to download the official stock firmware from http://SamMobile.com
and Odin flash it. Make 100% sure that the firmware you download is the right one
for your specific phone's model.
Good luck!
Click to expand...
Click to collapse
I already tried to install sock rom (tar.md5) from SamMobile, but Odin starts and fail.
chemarko said:
I already tried to install sock rom (tar.md5) from SamMobile, but Odin starts and fail.
Click to expand...
Click to collapse
C`mon guys HELP PLEASE
[HELP] Please
chemarko said:
C`mon guys HELP PLEASE
Click to expand...
Click to collapse
Me again.
When I start ODIN with stock rom with PDA, this is message
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505TMTEMJ4_I9505XXUEMKF_HOME.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)
When add re-partition
> 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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 1992)
<OSM> All threads completed. (succeed 0 / failed 1)
chemarko said:
Me again.
When I start ODIN with stock rom with PDA, this is message
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505TMTEMJ4_I9505XXUEMKF_HOME.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)
When add re-partition
> 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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 1992)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What version of Android u had before flash and what are u trying to flash??
Maybe u can't flash because u had 4.3(KNOX) and u are trying to flash a 4.2 that is possible?
Ops sorry, Its older or newest this version of Android 4.3 that u had?
DefyUser89 said:
What version of Android u had before flash and what are u trying to flash??
Maybe u can't flash because u had 4.3(KNOX) and u are trying to flash a 4.2 that is possible?
Ops sorry, Its older or newest this version of Android 4.3 that u had?
Click to expand...
Click to collapse
I installed few days ago 4.4.2, and CP_I9505XXUFNA5 and BL_I9505XXUFNA5. It has to much bugs so I decided to go back.
I tried to install stock rom from SamMobile with PDA in Odin and got this error.
I flashed just now TWR and GSM_Modem_XXUEMFK_and_LTE_Modem_XXUMFK and some custom rom 4.3 (google edition).
It installed but system keep crashing. I tried couple of roms and same situation. It is crushing all the time.
Could it be problem with bootloader
chemarko said:
I installed few days ago 4.4.2, and CP_I9505XXUFNA5 and BL_I9505XXUFNA5. It has to much bugs so I decided to go back.
I tried to install stock rom from SamMobile with PDA in Odin and got this error.
I flashed just now TWR and GSM_Modem_XXUEMFK_and_LTE_Modem_XXUMFK and some custom rom 4.3 (google edition).
It installed but system keep crashing. I tried couple of roms and same situation. It is crushing all the time.
Could it be problem with bootloader
Click to expand...
Click to collapse
You can no longer downgrade to stock 4.3 mate,thats why your getting this error.. flash the 4.4.2 leak and that should fix your problem.
Sent from Hell ?
chemarko said:
I installed few days ago 4.4.2, and CP_I9505XXUFNA5 and BL_I9505XXUFNA5. It has to much bugs so I decided to go back.
I tried to install stock rom from SamMobile with PDA in Odin and got this error.
I flashed just now TWR and GSM_Modem_XXUEMFK_and_LTE_Modem_XXUMFK and some custom rom 4.3 (google edition).
It installed but system keep crashing. I tried couple of roms and same situation. It is crushing all the time.
Could it be problem with bootloader
Click to expand...
Click to collapse
Repulsa said:
You can no longer downgrade to stock 4.3 mate,thats why your getting this error.. flash the 4.4.2 leak and that should fix your problem.
Sent from Hell ?
Click to expand...
Click to collapse
Oh yes! I forget, I installed FNA1 not FNA5 and i could come back to 4.3 because FNA1 dont have new bootloader... I rode that FNA5 have new bootloader and u can go back to 4.3.
The best choice is how said @Repulsa , U must install FNA5 and after install Philz-touch, CWM or TWR and install any 4.4.2
I hope that we helped to you! :good:
Regards,
I have a Galaxy Note 3 SM-N9005 running stock Android 4.3 rooted and I cannot for the life of me figure out how to properly install TWRP. I booted into download mode, loaded up Odin3, and flashed openrecovery-twrp-2.6.3.0-hlte.img.tar under "PDA" but it failed.
I use to install TWRP easily through goomanager, but it doesn't seem to work on the Note 3.
How do I go with installing TWRP on N9005 running rooted stock 4.3?
TWRP Manager
Try to flash img via TWRP Manager
verny94 said:
Try to flash img via TWRP Manager
Click to expand...
Click to collapse
Downloaded the .img and selected it in the app. It tells me to choose a device but N9005 doesn't appear in the list.
Mine won't flash in Odin
Running Stock 4.3 rooted
Attempting to flash "openrecovery-twrp-2.6.3.0-hlte.img.tar" with PDA
Galaxy Note 3 N9005 in Download mode
<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> recovery.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
At the first of all you need Flash CWM via Odin and try to flash TWRP. If not ->
Try to flash Philz Touch in zip and via PT flash TWRP in zip.
Edit: Newest is 2.7.0.0
Colton127 said:
Mine won't flash in Odin
Running Stock 4.3 rooted
Attempting to flash "openrecovery-twrp-2.6.3.0-hlte.img.tar" with PDA
Galaxy Note 3 N9005 in Download mode
<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> recovery.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try to use Odin 3.0.7/3.0.9 if you used the old one. If not I could also recommend philz touch recovery... looks and works pretty nice
Colton127 said:
Mine won't flash in Odin
Running Stock 4.3 rooted
Attempting to flash "openrecovery-twrp-2.6.3.0-hlte.img.tar" with PDA
Galaxy Note 3 N9005 in Download mode
<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> recovery.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
why don't you try the latest TWRP, and choose for the android 4.3 one.
by right it should work. You can use odin any version, but for me personally I preferred to use 3.0.9.
I have try to flash back to stock but I get the same error every time. I have tried about 5 different flash.
About once a week it will get bricked. And I have to factory reset. That is why I want to flash back.
This is the error
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for the help
firehawk321 said:
I have try to flash back to stock but I get the same error every time. I have tried about 5 different flash.
About once a week it will get bricked. And I have to factory reset. That is why I want to flash back.
This is the error
Removed!!
Added!!
Odin engine v(ID:3.1203)..
File analysis..
SetupConnection..
Initialzation..
FAIL! Model dismatch fail
All threads completed. (succeed 0 / failed 1)
Thanks for the help
Click to expand...
Click to collapse
Does your Odin error really say FAIL!! Model Dismatch or did it say "md5 mismatch?" I wanted to make sure that was not a typo.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Does your Odin error really say FAIL!! Model Dismatch or did it say "md5 mismatch?" I wanted to make sure that was not a typo.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
it really says that. I copied and pasted that.
There was no failure on the phones boot loader screen either.
Im having the same issue. My phone has a sticker that says it is 930A and the rom im using file name is G930AATT1APB5_ATT1APB5_ATT_USA_v6.0.1_Repair_Firmware but yea its saying model mismatch
BrokenMessiah said:
Im having the same issue. My phone has a sticker that says it is 930A and the rom im using file name is G930AATT1APB5_ATT1APB5_ATT_USA_v6.0.1_Repair_Firmware but yea its saying model mismatch
Click to expand...
Click to collapse
well mine says model " dismatch " not model mismatch
I put a custom rom on it maybe that will fix it.
I got mine working. I used this rom and this odin
firehawk321 said:
I have try to flash back to stock but I get the same error every time. I have tried about 5 different flash.
About once a week it will get bricked. And I have to factory reset. That is why I want to flash back.
This is the error
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for the help
Click to expand...
Click to collapse
I had the same problem. I downloaded version 3.12.3 of Odin and used that instead and that worked.