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 .
Related
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
I REALLY hope anyone can help. I am desperate. I have been trying to unbrick my phone since last night. I have tried everything... I have been all over this forum.
I had a rooted Canadian Rogers S4 (I337M) with a google edition 4.3 rom.
I tried to flash the default rogers stock rom, however got an odin fail. I have been unsuccessful trying to restore the phone.
I have tried MF3.tar and MK2.tar (as per Ted's posts), however keep getting odin fail.
Can anyone help or suggest something?
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Go to sammobile.com and download the firmware for the Rogers i337m. You'll have to register but it's free
Edit, make sure you're using the cable that came with your phone. Use the usb ports in the back of your pc, usb 2.0 not 3.0. And keep trying. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Go to sammobile.com and download the firmware for the Rogers i337m. You'll have to register but it's free
Edit, make sure you're using the cable that came with your phone. Use the usb ports in the back of your pc, usb 2.0 not 3.0. And keep trying. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Downloading now...
n3gkiwi said:
Downloading now...
Click to expand...
Click to collapse
You'll download a zip file. Use 7-zip to extract a .tar.md5. Use that in Odin, PDA slot
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Still failed. Is it my modem.bin?
<OSM> I317MVLALJ2_I317MOYAALJ2_I317MVLALJ2_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> modem.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Odd, I tried odin 3.07, 3.09, and 1.85.... keeps failing. Any ideas?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
I think you need to install your modem first. Extract the modem.bin file from the tar.Md5 file you downloaded from sammobiile.
Make a copy of .tar.md5 file. Rename it to .tar. open with 7zip, extract modem.bin file. flash this modem.bin file twice using odin. put it in phone slot and uncheck autoreboot in odin.
After successful flashing of modem in odin flash the firmware tar.md5 by putting it in pda slot of odin.
Try using Odin 3.07. I had the same prob when I was going back from goldeneye to stock firmware.This did the magic.
Good Luck
So i go it working finally however when the phones restarted however android.process.acore keeps stopping?
Phones says "Unfortunately, the process android.process.acore has stopped."
Any ideas?
Edit: Went into recovery and did a wipe/factory reset. Hopefully that works
n3gkiwi said:
So i go it working finally however when the phones restarted however android.process.acore keeps stopping?
Phones says "Unfortunately, the process android.process.acore has stopped."
Any ideas?
Edit: Went into recovery and did a wipe/factory reset. Hopefully that works
Click to expand...
Click to collapse
Did you wipe your data/cache and dalvik before you flashed the stock image? If you continue to have problems try that before you flash again, if you google the statement about infortunately, there is lots of posts about your data....
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNF1_I9505OXAGNF1_I9505XXUGNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Are you sure you have the right .tar image for your device?
Did you try downloading it again and trying with a fresh copy?
help
what i must do now my phone is in download mode at end stuck what now?
SchawanHD said:
what i must do now my phone is in download mode at end stuck what now?
Click to expand...
Click to collapse
A LOT more detail about what you are trying to do, what you started with, etc etc etc would be helpful.
Was the phone working before?
Are you just trying to update it?
What ROM did you have before? Stock or custom?
Give us the bigger picture here.
If your phone was working before then what you've done shouldn't have killed anything. Pull the battery and reboot and it should start up as normal.
The next thing I'd try (After the 2 things I've already suggested that you didn't check yet) is to uncheck REBOOT AUTOMATICALLY in Odin. When it fails, immediately run the update again. See what happens then.
HELP!
i have before make this Cyanogen mod 10.2 and then i decided to flash to stock rom
now i make an Fullwipe per CWM and then i took The tar of the firmware of my old stock version.
now my phone stuck at end of downloadmode (i'm too scared to pull off battery)
and odin says fail blablabla
CMOD had android 4.3.1 and i took I9505jtexx... 4.4.2
Skipjacks said:
A LOT more detail about what you are trying to do, what you started with, etc etc etc would be helpful.
Was the phone working before?
Are you just trying to update it?
What ROM did you have before? Stock or custom?
Give us the bigger picture here.
If your phone was working before then what you've done shouldn't have killed anything. Pull the battery and reboot and it should start up as normal.
The next thing I'd try (After the 2 things I've already suggested that you didn't check yet) is to uncheck REBOOT AUTOMATICALLY in Odin. When it fails, immediately run the update again. See what happens then.
Click to expand...
Click to collapse
i fullwiped the phone per CWM and try in downloading mode flashing the stock FW via ODin
Do the thing about unchecking auto reboot that i said earlier
Skipjacks said:
A LOT more detail about what you are trying to do, what you started with, etc etc etc would be helpful.
Was the phone working before?
Are you just trying to update it?
What ROM did you have before? Stock or custom?
Give us the bigger picture here.
If your phone was working before then what you've done shouldn't have killed anything. Pull the battery and reboot and it should start up as normal.
The next thing I'd try (After the 2 things I've already suggested that you didn't check yet) is to uncheck REBOOT AUTOMATICALLY in Odin. When it fails, immediately run the update again. See what happens then.
Click to expand...
Click to collapse
ok now what to do phone is in downloadmode stuck ?
Skipjacks said:
Do the thing about unchecking auto reboot that i said earlier
Click to expand...
Click to collapse
but if i pull off battery what will hapen? before flash i fullwiped phone!!!!
SchawanHD said:
but if i pull off battery what will hapen? before flash i fullwiped phone!!!!
Click to expand...
Click to collapse
As long as Odin isn't actively writing to the device, nothing will happen with a battery pull.
You shouldn't have full wiped the phone prior to this.
And please don't make multiple threads to discuss the same thing.
Just try the things I've suggested so far.
I've been rooting and stuff since 2012. I got a S4 AT&T I337. I rooted with Geohots app. I don't know what its called, but you just tap "make it rain" and then you install SuperSu. All that worked fine, it rooted and I took off the bloatware with TBK. And after that I tried installing TWRP. I downloaded the TWRP app and chose the right phone and model I have and flashed the TWRP recovery. Then I rebooted and It booted into download mode and I got a message in red at the top saying "stuck in odin mode". I then took the battery out and booted into download mode by holding volume Down and power and then pressed down to restart the phone. The phone works fine it's just when I boot into recovery mode It boots into this download mode thing with a message in red saying 'Stuck in odin Mode'
I installed safestrap and now when I restart the phone from the Device options. Power Off, airplane mode and restart. it gives me the option to continue and boot normally or go into recovery mode. But at the top off safestrap in says safestrap Disabled I don't know what that means.
What did I do wrong? How can I fix this? And did I make a big mistake?
I have a I337 NI1 running 4.4.2 Stock. I just got this phone off ebay so I know for a fact it probaly hasn't been messed with.
I also tired uning triangle away but that didn't fix my problem. I'm thing about just getting a Stock NI1 odin .tar and doing an emerency flash.
Do you have an i337 our an i337m? I'm not clear on that. Twrp won't work on the i337
Sent from my Nexus 5 using XDA Free mobile app
I got the normal S4
You're most likely gonna have to use the Odin to stock thread in the general section. Sounds like you meant 1337 on NI1 baseband, which can't use twrp. You're right to use safestrap but it sounds like you might have mucked your phone up a bit.
I tried that but it didn't work out to well. odin almost finished but I got an error at the very very end of the flash. But I can still get into download mode. I'm thinking about flashing the MLD since the NI1 didn't work out.
How bad do you think I messed my phone up? what would you do to fix it? This is my first time working with the s4. Every other phone I had and rooted and messed with worked fine. But this s4 is something different. Do you think you can tell me the do's and don'ts on the s4. Thanks! I need to get it fixed by Friday.
Odin log file
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> persdata.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!!
It took less than 10 seconds to get this.
TylerMarshall256 said:
How bad do you think I messed my phone up? what would you do to fix it? This is my first time working with the s4. Every other phone I had and rooted and messed with worked fine. But this s4 is something different. Do you think you can tell me the do's and don'ts on the s4. Thanks! I need to get it fixed by Friday.
Odin log file
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> persdata.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!!
It took less than 10 seconds to get this.
Click to expand...
Click to collapse
Try different usb ports (use the ones in the back of the pc) and cables. Odin can be finicky. You're flashing the right file
Sent from my Nexus 9 using XDA Free mobile app
Murasakiii said:
You're most likely gonna have to use the Odin to stock thread in the general section. Sounds like you meant 1337 on NI1 baseband, which can't use twrp. You're right to use safestrap but it sounds like you might have mucked your phone up a bit.
Click to expand...
Click to collapse
jd1639 said:
Try different usb ports (use the ones in the back of the pc) and cables. Odin can be finicky. You're flashing the right file
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
That's what I figured it was. I'm on a little Acer laptop right now. I'm about to go use my cousins desktop. I hear those are better than laptops. I'll keep you updated man just stick with me.
ALRIGHT! All I did was go to my cousins house, install the USB driver! NOT KIES! And use his factory USB cable and it fixed it just FINE!!
I tried to upgrade my GT-I9500 to Official Lollipop firmware using Odin. It showed a FAIL and when I tried to restart the device, it shows, Firmware upgrade encountered an issue. Please select recovery mode in Kies. I tried entering into recovery mode in Kies by entering the Model Number and Serial Number (S/N). But, it shows, GT-I9500 can't be initialized. I tried on Kies and Kies3. I tried using different USB cables and USB ports. The phone is not going into Recovery mode. Please help me!!!
I tried using Odin v7, v9 and v10. Odin showed this message:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNH2_I9505PLSGNH1_I9505XXUGNH2_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> 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> 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)
Please help me!!
v4vyshakh said:
I tried to upgrade my GT-I9500 to Official Lollipop firmware using Odin. It showed a FAIL and when I tried to restart the device, it shows, Firmware upgrade encountered an issue. Please select recovery mode in Kies. I tried entering into recovery mode in Kies by entering the Model Number and Serial Number (S/N). But, it shows, GT-I9500 can't be initialized. I tried on Kies and Kies3. I tried using different USB cables and USB ports. The phone is not going into Recovery mode. Please help me!!!
I tried using Odin v7, v9 and v10. Odin showed this message:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNH2_I9505PLSGNH1_I9505XXUGNH2_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> 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> 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)
Please help me!!
Click to expand...
Click to collapse
Hi,
You can try flashing firmware with a .pit file.
v4vyshakh said:
I tried to upgrade my GT-I9500 to Official Lollipop firmware using Odin. It showed a FAIL and when I tried to restart the device, it shows, Firmware upgrade encountered an issue. Please select recovery mode in Kies. I tried entering into recovery mode in Kies by entering the Model Number and Serial Number (S/N). But, it shows, GT-I9500 can't be initialized. I tried on Kies and Kies3. I tried using different USB cables and USB ports. The phone is not going into Recovery mode. Please help me!!!
I tried using Odin v7, v9 and v10. Odin showed this message:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNH2_I9505PLSGNH1_I9505XXUGNH2_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> 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> 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)
Please help me!!
Click to expand...
Click to collapse
Why are you flashing I9505XXUGNH2 on a I9500?? You CANNOT flash I9505 firmware on a I9500.
Lennyz1988 said:
Why are you flashing I9505XXUGNH2 on a I9500?? You CANNOT flash I9505 firmware on a I9500.
Click to expand...
Click to collapse
oops! I pasted the wrong log by mistake. The pasted log was for I9505. But, the issue is the same when I tried flashing the correct firmware for I9500. Can you please find out a solution? I'm totally stuck!
krasCGQ said:
Hi,
You can try flashing firmware with a .pit file.
Click to expand...
Click to collapse
Hey, thankyou for your reply. Will you please elaborate about the actual process? I don't have proper knowledge about .pit file. Please help!
v4vyshakh said:
oops! I pasted the wrong log by mistake. The pasted log was for I9505. But, the issue is the same when I tried flashing the correct firmware for I9500. Can you please find out a solution? I'm totally stuck!
Click to expand...
Click to collapse
It's still a drivers/pc/port/cable problem.
You are not using a virtual machine are you?
I tried using different USB cables and on different USB ports. Drivers are correctly installed. Other phones are getting detected without any issues.
I'm not using a Virtual Machine. Thanks!
I had the same problem, try to use different pc like i did.
Shall I try using the .pit file? Can that be useful by any means?
Sent from my SM-G900H using XDA Free mobile app
Did you use .pit file? Or, just changed the computer? Thanks!
Sent from my SM-G900H using XDA Free mobile app
Lennyz1988 said:
Why are you flashing I9505XXUGNH2 on a I9500?? You CANNOT flash I9505 firmware on a I9500.
Click to expand...
Click to collapse
A good catch! My mistake...
v4vyshakh said:
Hey, thankyou for your reply. Will you please elaborate about the actual process? I don't have proper knowledge about .pit file. Please help!
Click to expand...
Click to collapse
v4vyshakh said:
I tried using different USB cables and on different USB ports. Drivers are correctly installed. Other phones are getting detected without any issues.
I'm not using a Virtual Machine. Thanks!
Click to expand...
Click to collapse
v4vyshakh said:
Shall I try using the .pit file? Can that be useful by any means?
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
v4vyshakh said:
Did you use .pit file? Or, just changed the computer? Thanks!
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
.pit file contains information about partition sizes of System, Cache, and your Internal storage.
I'm personally using .pit file only if I have found broken partition when I was on custom recovery and custom ROM.
.pit file will be useful when you have broken your partition or soft bricked your phone and you want to recover back manually without go to Samsung Service Center. No need to change your computer, except all of your USB ports are dead.
Thankyou for the information. So, shall I proceed to flash the .pit file?
Sent from my SM-G900H using XDA Free mobile app
- Try another pc first.
- Try JOdin (web odin) https://builds.casual-dev.com/jodin3/
- Try Heimdall.