I bought my SM-N900V a few weeks ago and rooted it using Root de La Vega as soon as I got it home. Everything worked perfectly on the first attempt and I hadn't messed with anything since. I was probably stupid at one point and took the first OTA update because I noticed one day that I no longer had root access. I reboot my device every few days without an issue. My problem began about a week ago when I rebooted it like I regularly do and had it come to the message at the top saying "set warranty bit: kernel" followed by the Verizon screen which says "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I rebooted into Odin mode a few times selected cancel to restart which got me back into the OS after a few attempts. A few days later I watched it restart itself into the same screen as before except that this time I haven't been able to get past it. I have the latest Samsung USB drivers installed, Odin 3.09, the MJE tar file from SamMobile, and the PIT file from these forums. No matter which cable or computer I use, I haven't been able to successfully flash the firmware, it consistently fails at boot.img. I can get into Odin/Download mode but not recovery mode. The only thing I ever did to the phone was root, nothing else. Please help me?
This thread had all you need to Odin back to mje
http://forum.xda-developers.com/showthread.php?t=2483380
sent from tapatalk....probably while pooping.
Thank you for the link but that thread was followed exactly prior to this post with no success.
This is what Odin shows every time that I try to flash any version firmware.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.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> aboot.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> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Did u use the pit file as well and the tar?
Sent from my SM-N900V using Tapatalk
Yes, I used both files.
Related
Help, Phone Says " Firmare Upgrade encountered an issue, Please use Software Repair
Hey Guys,
I have no clue what happened, Phone is stuck in ODIN Mode,
I am in odin 3.09, downloaded the pit file and the latest MJE firmware and i get to this step.
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help a lost soul...
Justin
Install pit by itself. Restart in recovery and factory wipe. Then install firmware
If I helped hit thanks!!
I did the pit file, not it stays locked at Samsung Galaxy Note 3 screen.
2swizzle said:
Install pit by itself. Restart in recovery and factory wipe. Then install firmware
If I helped hit thanks!!
Click to expand...
Click to collapse
Pit File - HLTE_USA_VZW_32G.PIT
PDA - MI9/MJ7/MJE (none work)
I am running odin as an administrator. I just can't get this thing to download to the phone... am i doing something wrong..
I put the phone in download mode.
Ive Done :
Download the MJE Stock Firmware 1.3 GB and extract it once...
Download latest ODIN 3.09...
In your device go into Download mode(Vol Down+Home Button+Power Button) and again Volume Up for Download mode...
Right click ODIN and open as administrator...
Now connect your device to PC and check the status in ODIN as Connected... (COM 5)
Make sure that only Auto Reboot and F.Reset Time are checked in ODIN...
Click on AP and select the extracted file from MJE firmware...
After checking the MD5 file...Click on START and wait I get the following error
-<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> 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> 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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
is there something I am missing?
Thanks in advance!
Looks like you are trying to install I9 in your second post. Unless you were on i9 to start with you cannot downgrade. At the top of your post you refer to MJE. That is probably the reason.
Sent from my SM-N900V using Tapatalk
ive tried them all.. still no luck... verizon is sending me a new phone... it should load through odin, it doesn't nothing..
Well the issue was I was running ODIN in my VMWare Windows 7 Virtual Machine. I got my new phone today from verizon, for ****s i hooked it up to my old Windows XP machine and it went with out a hitch. I unplugged it was 75% so they can have it showing ODIN MODE..
Thanks for all the help...
hello everyone
i rooted my s4 a while back, then unrooted by flashing XSA-I9505XXUEMK9-20131212101727 through odin
then i decided to root it again, it worked but this time the wifi stopped working so i flashed XSA-I9505XXUEMK9-20131212101727 (same firmware) again, except everytime i do it, odin gives me a fail
i used a pit file to flash with XSA-I9505XXUEMK9-20131212101727 (same firmware again), except during the middle of this process, the connection between my cable and phone broke
tried pit + XSA-I9505XXUEMK9-20131212101727 (same thing) on odin 3.09 after the first attempt, it gives me a fail and this
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505XSAEMK3_I9505XXUEMK9_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> 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> system.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!!
right now, when i try to boot my phone, it gives me "firmware upgrade encountered an issue. please select recovery mode in kies and try again", though i can't do anything in kies
all i can access is download mode, recovery mode doesn't work either (it never did, even when my phone was fine)
please help
chilifourloko said:
hello everyone
i rooted my s4 a while back, then unrooted by flashing XSA-I9505XXUEMK9-20131212101727 through odin
then i decided to root it again, it worked but this time the wifi stopped working so i flashed XSA-I9505XXUEMK9-20131212101727 (same firmware) again, except everytime i do it, odin gives me a fail
i used a pit file to flash with XSA-I9505XXUEMK9-20131212101727 (same firmware again), except during the middle of this process, the connection between my cable and phone broke
tried pit + XSA-I9505XXUEMK9-20131212101727 (same thing) on odin 3.09 after the first attempt, it gives me a fail and this
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505XSAEMK3_I9505XXUEMK9_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> 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> system.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!!
right now, when i try to boot my phone, it gives me "firmware upgrade encountered an issue. please select recovery mode in kies and try again", though i can't do anything in kies
all i can access is download mode, recovery mode doesn't work either (it never did, even when my phone was fine)
please help
Click to expand...
Click to collapse
Although this message your phone is in download mode
change usb port and try again
try different port
Fixed it somehow........
actually disregard all that, i flashed the pit file by itself in odin 3.09 and everything works again O_O
i'm missing an app which is weird...
i still can't reflash XSA-I9505XXUEMK9-20131212101727 through odin though, it still gives me a fail, which ends up ruining everything again, so i reflash the pit and now this happens
i did a factory reset, now samsung keyboard keeps crashing and the menu and back button do nothing
wth is happening ._.
chilifourloko said:
i still can't reflash XSA-I9505XXUEMK9-20131212101727 through odin though, it still gives me a fail, which ends up ruining everything again, so i reflash the pit and now this happens
i did a factory reset, now samsung keyboard keeps crashing and the menu and back button do nothing
wth is happening ._.
Click to expand...
Click to collapse
maybe wrong or corrupt firmware file try another
pda4g said:
maybe wrong or corrupt firmware file try another
Click to expand...
Click to collapse
which firmware should i use
does it matter ?
chilifourloko said:
which firmware should i use
does it matter ?
Click to expand...
Click to collapse
download firmware for your country
Your file may be damaged
download new
pda4g said:
download firmware for your country
Your file may be damaged
download new
Click to expand...
Click to collapse
redownloaded firmware, stopped antivirus and all kies processes, changed usb ports to one of the back ones, reflashed firmware from ~80 percent battery aaaaaaaaaaaaand...
IT WORKS !!!!!!!!!!!!!!!!!!!!!!!!!!!!
HALLELUJAH
chilifourloko said:
redownloaded firmware, stopped antivirus and all kies processes, changed usb ports to one of the back ones, reflashed firmware from ~80 percent battery aaaaaaaaaaaaand...
IT WORKS !!!!!!!!!!!!!!!!!!!!!!!!!!!!
HALLELUJAH
Click to expand...
Click to collapse
ok Good luck!
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!!
Hello guys... I have been at this for a few hours now. I own a Note 4 N910H. I had upgraded OTA to lollipop last month. I was reading some reviews on lollipop because I was experiencing a lot of bugs with the OS. A lot of people were having the same issues as me. So I decided to go back to kitkat. This is where my problem happens. I accidentely soft bricked my device.
Everything I've done:
Downloaded kitkat and tried to install via odin. (Didn't check developer settings prior, not sure if this was the problem)
Device soft bricked
Turned on my device and saw this message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Tried to access Kies, it said my device wasn't supported.
I googled around and saw an article saying I have to go back to lollipop.
I downloaded lollipop and tried to install via odin. It failed again with the same error when I turn on my device.
All help will be greatly appreciated. I really hope I don't have to send my phone back. I don't have a backup lol.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910HXXU1BOC5_N910HOXE1BOC5_N910HXXU1BOC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
drew92c said:
Hello guys... I have been at this for a few hours now. I own a Note 4 N910H. I had upgraded OTA to lollipop last month. I was reading some reviews on lollipop because I was experiencing a lot of bugs with the OS. A lot of people were having the same issues as me. So I decided to go back to kitkat. This is where my problem happens. I accidentely soft bricked my device.
Everything I've done:
Downloaded kitkat and tried to install via odin. (Didn't check developer settings prior, not sure if this was the problem)
Device soft bricked
Turned on my device and saw this message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Tried to access Kies, it said my device wasn't supported.
I googled around and saw an article saying I have to go back to lollipop.
I downloaded lollipop and tried to install via odin. It failed again with the same error when I turn on my device.
All help will be greatly appreciated. I really hope I don't have to send my phone back. I don't have a backup lol.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910HXXU1BOC5_N910HOXE1BOC5_N910HXXU1BOC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Just flash a custom recovery via odin and reboot and you are good to go
Abdl said:
Just flash a custom recovery via odin and reboot and you are good to go
Click to expand...
Click to collapse
Would that root my device? I don't want to void my warranty. If it doesn't void it, how do I go about doing those steps? This whole thing is driven me nuts.
Edit: THANK YOU!!! All is good now!
Use a pit file for it. Because your hidden partition fails. Or you can Flash your latest rom with no error. I think you re trying another rom from your latest.
So I've installed a custom ROM on this phone about 2 years ago. It's my girlfriends phone.
Every once in a while when she turns her phone on it would go into a boot loop several times, and eventually go into the system and function normally. It was very intermittent, but it wasn't a big deal. Yesterday the phone was stuck in a permanent boot loop. What was interesting is that i could not enter into a Recovery Mode, just download mode.
So i figured it was time to just simply flash the original stock ROM.
ODIN 3.12.7
ROM: FMC-G900W8VLS1DPF3-20160725152930 (Canadian Koodo Android 6.0.1)
Flash was completely successful (I've flashed and unbricked many phones so I am very familiar with the process). This is the ODIN log file
<ID:0/004> 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/004> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<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> cache.img.ext4
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Phone restarts with blue Recovery Booting message and is stuck in a boot loop again. Boot loop is always trying to go Into Recovery Mode (just like previously before flash). I know that flash was successful because I no longer have the yellow Warranty Bit message i did when custom ROM was installed, So then i figured maybe i need the PIT file. I found a pit file SM-G900W8_pit_16GB.
I've then re-flashed again with this PIT file (Auto-reboot, re-partition, and F. Reset Time checked) and got an error message
<ID:0/004> 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/004> Odin engine v(ID:3.1207)..
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't know what else to do. The phone has been dropped quite a few times which is obvious by its appearance. Does anybody have any suggestions?
srdjmor said:
So I've installed a custom ROM on this phone about 2 years ago. It's my girlfriends phone...
Click to expand...
Click to collapse
I don't have this specific device but, your best bet is to post this question within the following Discussion thread for your specific device.
https://forum.xda-developers.com/showthread.php?t=3228804
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE