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
Related
Ok... so apparently i did something wrong. I posted earlier that i had issues after i rooted my mobile coz i was getting blocked by knox and i was unable to update in future. So i tried Unrooting it.
I got to know from samsung kies 3 that my cell was from Germany (DBT). And when i bought it i believe i had 4.2.2 in it. so i downloaded a stock firmware. i downloaded Triangle Away and i downloaded Odin3.
I enabled USB debugging. Launched Triangle away, asked me to confirm if it was GT-I9505 (Hit yes). Tapped Reset flash whatever as per video. it said danger, i proceeded, then it asked me to make sure i was using a stock Kernel (no idea if i was or not) but i hit yes... it rebooted into odin mode (download mode). connected it to PC and odin.. i saw the blue bar there and the message saying Added... clicked PDA, added the firmware and hit start... AND IT FAILED... the error is below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH5_I9505OXADMH5_I9505XXUDMH5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<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> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Now when i start it.. i only get the warning saying " FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES AND TRY AGAIN"
the counter for knoxx warranty void is 0x1 by the way... doesnt matter as long as i can get my cell to operate again... SO where did i go wrong? and how can i save it? i tried connecting to Samsung Kies but i dont get any selection for recovery either.
FIXED!
Okay! I somehow managed to reinstall the firmware. I got my cell working again.. it was what i believe you term as Soft Brick.
Anyways... Now it is still rooted. I tried opening the Superuser.. it says that apparently some binaries are not installed. i tried opening Triangle Away. Wont work since Superuser permission isnt granted. Do i have to root it again and then unroot? or is there a way to unroot it completely without going through the fuss again?
samsung galaxy S4: GT-I9505
Android: 4.3
Baseband Version: I9505XXUEMJ5
Kernel: 3.4.0-1869009
Help much appreciated
P.S: I dont care if the data is lost... the cell is pretty much empty!
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,
Hello from the UK!
I saw on SamMobiles website that they had 4.4.2 for my Note 3 (SM-N9005) with Vodafone... My phone is a Vodafone so I downloaded it used Odin 3.09 to flash it onto the phone... That didnt work it failed on system.img.ext4 with this
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1
This was the file
N9005XXUENB4_N9005VFGENA4_N9005XXUENB1_HOME.tar.md5
I can post a link but im not sure if thats allowed here!
I then tried again with Odin 3.07 after reading the Note 3 doesnt like 3.09... Again it failed, below is what it had on there.... 3.07 actually got futher than 3.09...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005VFGENA4_N9005XXUENB1_HOME.tar.md 5 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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Ive tried downloading Jelly Bean 4.3 again and using odin to re install it but as soon as I click start it fails...
Kies will not recognise the phone either...
Ive attached the screens I am able to get on my phone... This is it, it will not boot and I get no other things on screen but these...
Does anyone have any advice? How can I fix it? Im expecting calls over the weekend that are really imporant so desperately need this working.
Thanks Jono
JonoWilliams said:
Hello from the UK!
I saw on SamMobiles website that they had 4.4.2 for my Note 3 (SM-N9005) with Vodafone... My phone is a Vodafone so I downloaded it used Odin 3.09 to flash it onto the phone... That didnt work it failed on system.img.ext4 with this
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1
This was the file
N9005XXUENB4_N9005VFGENA4_N9005XXUENB1_HOME.tar.md5
I can post a link but im not sure if thats allowed here!
I then tried again with Odin 3.07 after reading the Note 3 doesnt like 3.09... Again it failed, below is what it had on there.... 3.07 actually got futher than 3.09...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005VFGENA4_N9005XXUENB1_HOME.tar.md 5 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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Ive tried downloading Jelly Bean 4.3 again and using odin to re install it but as soon as I click start it fails...
Kies will not recognise the phone either...
Ive attached the screens I am able to get on my phone... This is it, it will not boot and I get no other things on screen but these...
Does anyone have any advice? How can I fix it? Im expecting calls over the weekend that are really imporant so desperately need this working.
Thanks Jono
Click to expand...
Click to collapse
Well, first of all, your bootloader has been upgraded to Kitkat's.
So you can't flash a JB ROM.
Keep trying different Kitkat ROMs.
Try the leaked one.
And if you are willing to trip knox, you can use a custom ROM.
Got it working! What I did was
Download the Firmware you require, in my case for the UK Vodafone Version for the SM-N9005 4.4.2 I used this
http://www.sammobile.com/firmwares/3/?download=25990
I then downloaded Odin 3.07 as 3.09 wouldnt work for me!
http://www.android.gs/download-odin-3-07/
Now this alone wouldnt work for me then I found a similar thread that provided some info.
http://forum.xda-developers.com/showthread.php?t=2662373
On this thread they link to a .pit file to flash with the stock ROM, I used this along with the Firmware I downloaded earlier.
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
So now it would work and I am succesfully on 4.4.2, now once its all running and I got the the Samsung Logo I took the battery out, booted in recovery mode, cleared the cache and the performed a factory reset... Once the phone resarted I went through the normal process of setting it up and viola...
Ill add that although it says it was UK Vodafone mine was spanish? I dont know wether that was because of the .pit file? Ill let the experts decide on that one..
Simple thing though, change the language and remove the vodafone app that came with it in spanish...
Hope its of some help to people.
JonoWilliams said:
Got it working! What I did was
Download the Firmware you require, in my case for the UK Vodafone Version for the SM-N9005 4.4.2 I used this
http://www.sammobile.com/firmwares/3/?download=25990
I then downloaded Odin 3.07 as 3.09 wouldnt work for me!
http://www.android.gs/download-odin-3-07/
Now this alone wouldnt work for me then I found a similar thread that provided some info.
http://forum.xda-developers.com/showthread.php?t=2662373
On this thread they link to a .pit file to flash with the stock ROM, I used this along with the Firmware I downloaded earlier.
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
So now it would work and I am succesfully on 4.4.2, now once its all running and I got the the Samsung Logo I took the battery out, booted in recovery mode, cleared the cache and the performed a factory reset... Once the phone resarted I went through the normal process of setting it up and viola...
Ill add that although it says it was UK Vodafone mine was spanish? I dont know wether that was because of the .pit file? Ill let the experts decide on that one..
Simple thing though, change the language and remove the vodafone app that came with it in spanish...
Hope its of some help to people.
Click to expand...
Click to collapse
Exactly the same thing happened to me tonight.
What can I say - Thank you SO much for bothering to take to the time to write how you fixed it. It fixed it for me as well - I'm so relieved now!
JonoWilliams said:
Got it working! What I did was
Download the Firmware you require, in my case for the UK Vodafone Version for the SM-N9005 4.4.2 I used this
http://www.sammobile.com/firmwares/3/?download=25990
I then downloaded Odin 3.07 as 3.09 wouldnt work for me!
http://www.android.gs/download-odin-3-07/
Now this alone wouldnt work for me then I found a similar thread that provided some info.
http://forum.xda-developers.com/showthread.php?t=2662373
On this thread they link to a .pit file to flash with the stock ROM, I used this along with the Firmware I downloaded earlier.
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
So now it would work and I am succesfully on 4.4.2, now once its all running and I got the the Samsung Logo I took the battery out, booted in recovery mode, cleared the cache and the performed a factory reset... Once the phone resarted I went through the normal process of setting it up and viola...
Ill add that although it says it was UK Vodafone mine was spanish? I dont know wether that was because of the .pit file? Ill let the experts decide on that one..
Simple thing though, change the language and remove the vodafone app that came with it in spanish...
Hope its of some help to people.
Click to expand...
Click to collapse
I have spent 24 hours trying to sort this out. Thanks so much
thx ! I'll try it now
A long time ago I sent my phone in for repairs (screen). I factory reset it and lost root. I don't even remember how I rooted it, it was an automated tool. After it came back from repairs, it still had 4.2.2 and MDL (it was a repair shop not Samsung).
Whenever I reset/turn phone off and back on, I get an error about com.android something, but only then, it works normally after. Due to this error, my phone tries to upgrade but fails (thankfully). I want to root my phone but I'm afraid it will fail because of that error. What exactly should I do next? I asked in another thread and I was told Motochopper was the best tool to root on 4.2.2. I just want to get rid of this error then root, that's it, what should I do next?
Moto chopper should work. I'm guessing towelroot would too. https://towelroot.com
Sent from my Nexus 5 using XDA Free mobile app
But do you think I can just use it the way my phone is now? Someone told me to do a Factory Reset with Odin, but I have no idea how to do that. All the tutorials I find mention downloading something (apart from Odin itself), why would I need to do that if I'm just resetting?
This is the error I get "com.android.phone has stopped working".
I think I've already tried factory resetting with the physical buttons method and I still keep getting that.
SRCP said:
But do you think I can just use it the way my phone is now? Someone told me to do a Factory Reset with Odin, but I have no idea how to do that. All the tutorials I find mention downloading something (apart from Odin itself), why would I need to do that if I'm just resetting?
This is the error I get "com.android.phone has stopped working".
I think I've already tried factory resetting with the physical buttons method and I still keep getting that.
Click to expand...
Click to collapse
Odin flashes the factory firmware, it does a lot more than a factory reset. You need to download the mdl firmware and flash that in Odin. You can get it at sammobile.com. It's a zip file, you need to extract it using 7-zip or win rar. After it's extracted you end up with a .tar.md5 file. That's what you use in Odin.
If you do flash it, the phone will want to update via the ota. You should make sure it doesn't do that by rooting it and freezing out deleting the update apps. There are three files and I don't remember their names
Edit, read this http://forum.xda-developers.com/showthread.php?p=42320391
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Odin flashes the factory firmware, it does a lot more than a factory reset. You need to download the mdl firmware and flash that in Odin. You can get it at sammobile.com. It's a zip file, you need to extract it using 7-zip or win rar. After it's extracted you end up with a .tar.md5 file. That's what you use in Odin.
If you do flash it, the phone will want to update via the ota. You should make sure it doesn't do that by rooting it and freezing out deleting the update apps. There are three files and I don't remember their names
Edit, read this http://forum.xda-developers.com/showthread.php?p=42320391
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you. Last question. Do you think I should flash first or try to root right away?
SRCP said:
Thank you. Last question. Do you think I should flash first or try to root right away?
Click to expand...
Click to collapse
Rooting isn't going to do you any good at this point. Flash first
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Rooting isn't going to do you any good at this point. Flash first
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks.
jd1639 said:
Rooting isn't going to do you any good at this point. Flash first
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Odin failed.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!
What next? I'm trying to find more info.
SRCP said:
Odin failed.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!
What next? I'm trying to find more info.
Click to expand...
Click to collapse
This looks bad. The blue bar on phone moved a bit then stopped and it's stuck there. I tried Odin again and now I get this:
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Try a different port on the PC. Use one that is attached to the motherboard. Usually the USB ports on the back of the PC. Then try again
RockRatt said:
Try a different port on the PC. Use one that is attached to the motherboard. Usually the USB ports on the back of the PC. Then try again
Click to expand...
Click to collapse
I restarted the phone and now I'm on the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I did have it connected to a rear usb port, let me change it.
RockRatt said:
Try a different port on the PC. Use one that is attached to the motherboard. Usually the USB ports on the back of the PC. Then try again
Click to expand...
Click to collapse
It worked. Tried a different cable and port. I have all my apps, is that normal? I thought this did a factory reset.
Thanks guys. It worked, I'm rooted .
To start out, I will say that I am not the best with this kind of stuff and do not know THAT much about rooting/flashing ROMs and what not. I have read many posts about how to go about doing this and here is what I tried. I downloaded Odin 3.11.1 and the most recent Android 4.4.4 version (USA) from SamMobile. I turned my phone off and put it into download mode. After this, I started Odin, and pressed VOL up on my device to continue. Odin said "Added". I selected the file to flash in the AP section (G900VVRU1ANK2_G900VVZW1ANK2_G900VVRU1ANK2_HOME.tar.md5) and hit start. This is what came up in Odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1101)..
<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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried this many times with all the USB slots on my PC and with 3 different cords. I have also tried different versions of Odin. I'm not sure if any of that would change anything, like I said, I do not really know what I am doing. Am I doing something wrong here? Any help is greatly appreciated! Thanks, Hunter.
geezlaweezuz said:
I have tried this many times with all the USB slots on my PC and with 3 different cords. I have also tried different versions of Odin. I'm not sure if any of that would change anything, like I said, I do not really know what I am doing. Am I doing something wrong here? Any help is greatly appreciated! Thanks, Hunter.
Click to expand...
Click to collapse
You cannot downgrade from BOE1, BOG5, BOK3, BPB1, DPD1, or DPF4. As of BOE1, the bootloader was fused to prevent downgrading.
If you do have a downgrade-able firmware still installed on your phone, then the most likely remaining problem is that the file you're trying to flash is corrupt or incomplete: compare the md5 hash
You can do a partial downgrade to kk 4.4.2 you will still have pb1 bootloader but it does work in s5 verizon general there is a thread by brens123 called I booted into ncg on pb1 bootloader you might be able to subsitute the nk2 firmware instead of ncg firmware using his guide