Develop Bugs

[Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!

I tried to get help through reddit to no avail. My GS3 can only start up in download mode and nothing else works. I have the proper drivers installed on my computer, yet every time I try to flash a stock rom (which I've made sure are for the T-999 model) Odin fails at the NAND write start! part. I tried using the GS3 Toolkit to flash a stock rom but it says I need USB debugging enabled, which I can't enable because my phone doesn't start up in anything but download mode. What do I do?

Pakarido said:
I tried to get help through reddit to no avail. My GS3 can only start up in download mode and nothing else works. I have the proper drivers installed on my computer, yet every time I try to flash a stock rom (which I've made sure are for the T-999 model) Odin fails at the NAND write start! part. I tried using the GS3 Toolkit to flash a stock rom but it says I need USB debugging enabled, which I can't enable because my phone doesn't start up in anything but download mode. What do I do?
Click to expand...
Click to collapse
What was the last thing you did before this happened? Any idea what caused it to not be able to boot normally? How about recovery? Can you get that?
Are you using the USB cable that came with the phone? Try other cables?

DocHoliday77 said:
What was the last thing you did before this happened? Any idea what caused it to not be able to boot normally? How about recovery? Can you get that?
Are you using the USB cable that came with the phone? Try other cables?
Click to expand...
Click to collapse
I have this problem after unrick phone by JTag, can not flash stock rom on T999 after repair boot vby Jtag.
Odin Log:
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Set PIT file..
<ID:0/017> DO NOT TURN OFF TARGET!!
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> aboot.mbn
<ID:0/017> NAND Write Start!!
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

DocHoliday77 said:
What was the last thing you did before this happened? Any idea what caused it to not be able to boot normally? How about recovery? Can you get that?
Are you using the USB cable that came with the phone? Try other cables?
Click to expand...
Click to collapse
I was trying to get CWM on the phone but it didn't work, and I was stuck with only being able to boot in download mode. I have tried other cables and other computers, no luck. I can't get into recovery mode, only download.

How did you attempt to install cwm? Try flashing only recovery in Odin.
Sent from my SGH-T999L using XDA Premium 4 mobile app

DocHoliday77 said:
How did you attempt to install cwm? Try flashing only recovery in Odin.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My phone is T999 hard bricked but after repair boot loader by jtag phone able to boot up into Download mode only.
Not able boot into recovery, i tried Flash stock firmware with pit file, it is fail the Odin log said like that.
I tried to flash TWRP succeed but still can not go into TWRP to flash custom rom.
I tried to flash stock kernel and stock recovery after succeed with Odin phone still like that.
Only Boot into Download mode. can not go into recovery or TWRP or OS.
T-Mobile lock bootloader T999 via OTA update like I337 with OTA MF3 update ?
Thanks for help.

DocHoliday77 said:
How did you attempt to install cwm? Try flashing only recovery in Odin.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Forgive me, I'm new but what do you mean flash only recovery? Please specify.

nguyento1986 said:
My phone is T999 hard bricked but after repair boot loader by jtag phone able to boot up into Download mode only.
Not able boot into recovery, i tried Flash stock firmware with pit file, it is fail the Odin log said like that.
I tried to flash TWRP succeed but still can not go into TWRP to flash custom rom.
I tried to flash stock kernel and stock recovery after succeed with Odin phone still like that.
Only Boot into Download mode. can not go into recovery or TWRP or OS.
T-Mobile lock bootloader T999 via OTA update like I337 with OTA MF3 update ?
Thanks for help.
Click to expand...
Click to collapse
Please just post in the thread you created. No need to post the same thing here too.
Pakarido said:
Forgive me, I'm new but what do you mean flash only recovery? Please specify.
Click to expand...
Click to collapse
You said you tried to install cwm. Cwm is a custom recovery. How did you try installing it? I suggested trying to flash it in Odin by itself.
First, please tell me where you got the cwm recovery, and how exactly did you try to install it?
If your inability to boot normally started after trying to get cwm, ill need to know where you got it and how you tried installing it if I am going to be able to help. Please include a link to the file and any instructions you used.
Sent from my SGH-T999L using XDA Premium 4 mobile app

DocHoliday77 said:
Please just post in the thread you created. No need to post the same thing here too.
You said you tried to install cwm. Cwm is a custom recovery. How did you try installing it? I suggested trying to flash it in Odin by itself.
First, please tell me where you got the cwm recovery, and how exactly did you try to install it?
If your inability to boot normally started after trying to get cwm, ill need to know where you got it and how you tried installing it if I am going to be able to help. Please include a link to the file and any instructions you used.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried to flash it in Odin, and then it broke. I cant link because I'm a new user but if you copy paste this into Google "CF-Root 6.4 — It’s the New Samsung Galaxy S3 Root Package, Includes CWM 5.5, SuperSU and CWM Manager App" it's the first result, the website is theandroidsoul.com.

Pakarido said:
I tried to flash it in Odin, and then it broke. I cant link because I'm a new user but if you copy paste this into Google "CF-Root 6.4 — It’s the New Samsung Galaxy S3 Root Package, Includes CWM 5.5, SuperSU and CWM Manager App" it's the first result, the website is theandroidsoul.com.
Click to expand...
Click to collapse
Ohh boy!
Did you not read the entire page there? This is mentioned in the main body and also in large italic letters immediately following the article,
"This hack and the guide below are compatible only and only with Galaxy S3, model number i9300. It’s not compatible with other devices. Check your device’s model number in: Settings » About phone."
That is the international model. Ours is not an I9300. Ours is SGH-T999. Flash anything for the I9300/I9305 and you are destined for a hard brick. Yours, while not a total brick due to the fact you can get into download mode, is pretty much in the same boat as the other guy who posted in this thread and started his own. Basically, you probably flashed cwm recovery to a non-recovery partition, and system apps to a non-system partition. The trick is figuring out what partitions you overwrote. Probably ones that are not included in the stock firmware.
You need to find out what partitions hold the System and Recovery on the I9300. (ex. on our phones, System is on mmcblk0p14 and recovery is on mmcblk0p18). if their system is on p7, for example, then you would have flashed apps to our boot/kernel partition. If their Recovery is on p2, then you would have flashed CWM to our SBL1 partition which is not available in the stock firmware. It is possible to also mess up the partion layout this way as well.
If I get the time tonight, I will try to look up some of this for you and the other guy, but I may not be able to help much with this as I've never had to actually perform this kind of fix. I know what needs to be done, just not positive I know how to go about it. I can make very educated guesses, but with stuff like this, if I guess wrong, it could end up a little worse!
I suggest you take the info I just gave to you and do a lot of research. If you want guaranteed results, go to www.mobiletechvideos.com and see what they offer. They are the only ones I have ever seen anyone on this forum report using, and everyone who did was always very happy with their service. There are other shops you can find online that do this type of work, but Ive not seen any others mentioned around here. Not sure about prices either, so its up to you to research all of that type stuff.
In all honesty, I would look into a repair service to see what they can offer price-wise. If its cheap enough, I would seriously consider using them.
Good Luck man! If I can come up with anything, Ill let you know. And if you want me to try to help with actually fixing it after we have more info, I can do my best, but keep in mind you may have to wait until I am freed up enough to focus on it and I will not promise any kind of positive results! Others may reply with more info during the day tomorrow too, so you may also want to wait to see if anyone else has anything to add.

DocHoliday77 said:
Ohh boy!
Did you not read the entire page there? This is mentioned in the main body and also in large italic letters immediately following the article,
"This hack and the guide below are compatible only and only with Galaxy S3, model number i9300. It’s not compatible with other devices. Check your device’s model number in: Settings » About phone."
That is the international model. Ours is not an I9300. Ours is SGH-T999. Flash anything for the I9300/I9305 and you are destined for a hard brick. Yours, while not a total brick due to the fact you can get into download mode, is pretty much in the same boat as the other guy who posted in this thread and started his own. Basically, you probably flashed cwm recovery to a non-recovery partition, and system apps to a non-system partition. The trick is figuring out what partitions you overwrote. Probably ones that are not included in the stock firmware.
You need to find out what partitions hold the System and Recovery on the I9300. (ex. on our phones, System is on mmcblk0p14 and recovery is on mmcblk0p18). if their system is on p7, for example, then you would have flashed apps to our boot/kernel partition. If their Recovery is on p2, then you would have flashed CWM to our SBL1 partition which is not available in the stock firmware. It is possible to also mess up the partion layout this way as well.
Click to expand...
Click to collapse
Jesus I'm lost. I have no idea how to even start going about this. I would greatly appreciate if you can offer any help in your free time, and thank you very much for what you've given me already. Please don't forget about me :crying:

SW REV CHECK FAIL : Fused 1 > Binary 0

I am trying to install the stock ROM for my T-Mobile Galaxy S3. When I use ODIN to flash a stock ROM, I get the following:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDMD5.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also, the error message appears in download mode:
Code:
SW REV CHECK FAIL : Fused 1 > Binary 0
I tried the root66_TMO_T999UVDMD5.tar and T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar roms. My phone is useless right now because I deleted /system. Is there a solution to restore my phone?

What version of ODIN are you using ? More importantly, is your phone in Download mode ? (I suspect not to be)

Perseus71 said:
What version of ODIN are you using ? More importantly, is your phone in Download mode ? (I suspect not to be)
Click to expand...
Click to collapse
Odin 3.07
I held down the volume down + home button + power button. Then the warning message comes up about how a custom OS can cause critical problems in phone and installed applications. Then I press volume up. Finally the Android logo appears with a few lines of small text at the top left of the screen. Below the Android logo, it shows "Downloading... Do not turn off target!!!"
I think that is download mode.

Hypersonic1 said:
Odin 3.07
I held down the volume down + home button + power button. Then the warning message comes up about how a custom OS can cause critical problems in phone and installed applications. Then I press volume up. Finally the Android logo appears with a few lines of small text at the top left of the screen. Below the Android logo, it shows "Downloading... Do not turn off target!!!"
I think that is download mode.
Click to expand...
Click to collapse
What is current Rom & Android version ? Are you on Stock 4.3 update ?
Yes that is download mode. Connect to the pc with that mode. Let the drivers install completely. Then Launch Odin.

Perseus71 said:
What is current Rom & Android version ? Are you on Stock 4.3 update ?
Yes that is download mode. Connect to the pc with that mode. Let the drivers install completely. Then Launch Odin.
Click to expand...
Click to collapse
Right now nothing is on this phone because I deleted system. I was using Cyanogenmod 10.2. Then I decided to sell the phone, so I wanted to restore my phone to stock. I downloaded the stock Android 4.3 ROM, and flashed it. It worked fine, but then I wanted to use Triangle Away to reset the binary count, so I had to root the phone. However, I could not root the phone because SuperSU would keep crashing because of some security protection in Samsung's 4.3 that would block that application.
So I never could root the phone. I also tried flashed Cyanogenmod again and then running Triangle Away from there, but I have been unsuccessful installing Cyanogenmod ever since.

Hypersonic1 said:
Right now nothing is on this phone because I deleted system. I was using Cyanogenmod 10.2. Then I decided to sell the phone, so I wanted to restore my phone to stock. I downloaded the stock Android 4.3 ROM, and flashed it. It worked fine, but then I wanted to use Triangle Away to reset the binary count, so I had to root the phone. However, I could not root the phone because SuperSU would keep crashing because of some security protection in Samsung's 4.3 that would block that application.
So I never could root the phone. I also tried flashed Cyanogenmod again and then running Triangle Away from there, but I have been unsuccessful installing Cyanogenmod ever since.
Click to expand...
Click to collapse
The problem is that once you install the 4.3 update you cannot use Odin to flash a downgrade ROM even an official Samsung ROM. You will need to install a custom recovery then flash a rooted rom, then use triangle away then Odin back to the 4.3 ROM.
Unfortunatley The warranty bit will not go away it will remain at 1 until a dev finds a way to get it back to 0 or a way to load an older bootloader.

toeshot said:
The problem is that once you install the 4.3 update you cannot use Odin to flash a downgrade ROM even an official Samsung ROM. You will need to install a custom recovery then flash a rooted rom, then use triangle away then Odin back to the 4.3 ROM.
Unfortunatley The warranty bit will not go away it will remain at 1 until a dev finds a way to get it back to 0 or a way to load an older bootloader.
Click to expand...
Click to collapse
When I use the volume up + home + power combination, I enter ClockworkMod Recovery v6.0.4.3. Is this a custom recovery? How do I use this to flash a rooted rom? What rooted rom should I use for triangle away?

Hypersonic1 said:
When I use the volume up + home + power combination, I enter ClockworkMod Recovery v6.0.4.3. Is this a custom recovery? How do I use this to flash a rooted rom? What rooted rom should I use for triangle away?
Click to expand...
Click to collapse
See my post here
http://forum.xda-developers.com/showpost.php?p=48012926&postcount=8

Hypersonic1 said:
Right now nothing is on this phone because I deleted system. I was using Cyanogenmod 10.2. Then I decided to sell the phone, so I wanted to restore my phone to stock. I downloaded the stock Android 4.3 ROM, and flashed it. It worked fine, but then I wanted to use Triangle Away to reset the binary count, so I had to root the phone. However, I could not root the phone because SuperSU would keep crashing because of some security protection in Samsung's 4.3 that would block that application.
So I never could root the phone. I also tried flashed Cyanogenmod again and then running Triangle Away from there, but I have been unsuccessful installing Cyanogenmod ever since.
Click to expand...
Click to collapse
Stock Rom is notorious for such issues which is why I asked for your Rom and version. I suspected this to be the case. Now your best option is to
Sell it as is and forget Triangle away. Provided the phone works fine as is.
Hypersonic1 said:
When I use the volume up + home + power combination, I enter ClockworkMod Recovery v6.0.4.3. Is this a custom recovery? How do I use this to flash a rooted rom? What rooted rom should I use for triangle away?
Click to expand...
Click to collapse
Yes CWM is Custom Recovery. If you really want to root, you can try and flash the ATT Insecure Kernel from Docholiday's thread. After that, flash Superuser Zip from its thread.

toeshot said:
See my post here
http://forum.xda-developers.com/showpost.php?p=48012926&postcount=8
Click to expand...
Click to collapse
I successfully did step 1, but I don't know what adb is. How am I suppose to do step 2 without an OS?
2. Use adb to reboot recovery (adb reboot recovery)

Okay, I am trying to do step 2.
Code:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Am I suppose to be in Download mode to do this? I don't know any other modes to try this in. It is not finding the device.

Hypersonic1 said:
I successfully did step 1, but I don't know what adb is. How am I suppose to do step 2 without an OS?
2. Use adb to reboot recovery (adb reboot recovery)
Click to expand...
Click to collapse
you need to have the android sdk installed on your pcand use the adb command. If you can use the Volume up and Home button while you powerup, you can get into recovery mode also and you won't need use adb

toeshot said:
you need to have the android sdk installed on your pcand use the adb command. If you can use the Volume up and Home button while you powerup, you can get into recovery mode also and you won't need use adb
Click to expand...
Click to collapse
Thank you very much. I just copied those two ROM files to an external SD card, and pressed the install button in twrp. Then I restarted the phone and it is booting Android once again.
However, after I install and ran Triangle Away, I get the following message:
Could not locate magic header. This may be because you are not rooted, or your device is not supported. On many devices you need to be running Android 4.0 or newer.
If your device is not yet supported (but you are rooted), a dump file can be made that might help bring support to your device. Create a dump file?
Click to expand...
Click to collapse
Then I tapped Create Dump, and the next message:
A file called "TriangleAway.zip" has been created on your internal storage (or sdcard). Please attach it to a post in the Triangle Away thread on XDA, with details about your device.
Click to expand...
Click to collapse
I attached the file.

Hypersonic1 said:
Thank you very much. I just copied those two ROM files to an external SD card, and pressed the install button in twrp. Then I restarted the phone and it is booting Android once again.
However, after I install and ran Triangle Away, I get the following message:
Then I tapped Create Dump, and the next message:
I attached the file.
Click to expand...
Click to collapse
look in your app drawer and see if you have SU (Superuser) and see if it runs.
also make sure you installed the kernel I had posted in the instructions.
If you didn't install that kernel PM me and I will give you my FTP server to download it.

toeshot said:
look in your app drawer and see if you have SU (Superuser) and see if it runs.
also make sure you installed the kernel I had posted in the instructions.
If you didn't install that kernel PM me and I will give you my FTP server to download it.
Click to expand...
Click to collapse
Yes SuperSU is installed. It runs, and Triangle Away is listed in the Apps list of SuperSU. Access for Triangle Away is set to Grant.
I did install that kernel.

Hypersonic1 said:
Yes SuperSU is installed. It runs, and Triangle Away is listed in the Apps list of SuperSU. Access for Triangle Away is set to Grant.
I did install that kernel.
Click to expand...
Click to collapse
I installed the kernel again, and this time Triangle Away worked. Last time I added two zips to be installed. I assume I was suppose to install them separately.

Hypersonic1 said:
I installed the kernel again, and this time Triangle Away worked. Last time I added two zips to be installed. I assume I was suppose to install them separately.
Click to expand...
Click to collapse
Yes installed separately or make sure ROM installs first then the Kernel

Now I am trying to use ODIN to flash to a stock ROM that is unrooted.
I tried installing T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar but ODIN is still failing just like it was in the beginning. I don't know if this ROM is Android 4.3. Does it have to be? If so, then I will need an Android 4.3 stock ROM, but host hotfile is down.

Hypersonic1 said:
Now I am trying to use ODIN to flash to a stock ROM that is unrooted.
I tried installing T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar but ODIN is still failing just like it was in the beginning. I don't know if this ROM is Android 4.3. Does it have to be? If so, then I will need an Android 4.3 stock ROM, but host hotfile is down.
Click to expand...
Click to collapse
Yes since you had the original 4.3 all you can odin back to an older ROM. It is because of the 4.3 bootloader and KNOX. Samsung will not let you download to an older ROM or wipe the Bootloader. Just the way it is right now.
I can put the ROM on my FTP server but it will take an hour or more to download (sorry I have a slow line until I get a new router)
Did you try and download the ROM from SamMobile.com?

toeshot said:
Yes since you had the original 4.3 all you can odin back to an older ROM. It is because of the 4.3 bootloader and KNOX. Samsung will not let you download to an older ROM or wipe the Bootloader. Just the way it is right now.
I can put the ROM on my FTP server but it will take an hour or more to download (sorry I have a slow line until I get a new router)
Did you try and download the ROM from SamMobile.com?
Click to expand...
Click to collapse
I just checked on SamMobile.com.
Hotfile has been shudown. A download link to Terafile.co will be presented as soon as the firmware is uploaded. We are busy uploading all files to the new host. We apologize for the inconvenience.
Click to expand...
Click to collapse
The new link has not been posted yet. Downloading it from your FTP server will be fine. I am not in a hurry. Thank you.

NEW Firmware FOH3

Still 4.4.4 though, apparently it's still just too much effort to update to 5.0.1.
Probably just the stagefright patch...

Beginning August 31, the Samsung Galaxy S 4 will have a optional software update to Android version 4.4.4/ Baseband M919UVUFOH3 via OTA or Samsung Kies. This update provides
New Features______________________Improvements
N/A______________________________Stagefright fix

Anyone know if this can be applied to an S4 with custom, rooted ROM & custom kernel? Or does it only work with a stock phone?

hella356 said:
Anyone know if this can be applied to an S4 with custom, rooted ROM & custom kernel? Or does it only work with a stock phone?
Click to expand...
Click to collapse
It would replace your installed ROM; if you're just looking for the new modem, there's a thread that has it posted in it (sorry, I'm on mobile, or I'd dig it up for you).
Sent from my SGH-M919 using XDA Free mobile app

So, I downloaded the new firmware from SamMobile, since I was using TWRP and the OTA wouldn't have worked.
Link is here: http://www.sammobile.com/firmwares/download/54333/M919UVUFOH3_M919TMBFOH3_TMB/
I had to restart my download several times to get it to finally download completely. Luckily, Firefox would restart where it failed each time, so didn't have to restart from beginning each time. But, it took quite a while - several hours.
BTW, I did a full NAND backup with TWRP before I started this.
Used ODIN 3.09
Flashed once, but the bootloader and modem didn't take, so I did the double flash, and it worked.
To double flash:
Unchecked AutoReboot in ODIN
Flash the firmware once
Pull battery
Boot holding down Vol-Down button to get back to Download mode
Flash again
The problem with the single flash was my WiFi wouldn't turn on, and when I checked out the versions of the ROM, bootloader, modem using Samsung PhoneInfo from the Play Store, I saw the dreaded mis-matched versions.
Some of my partitions were still NH7. Evidently Samsung keeps a backup of some of the partitions and restores them when the phone is rebooted. Double flashing flashes overwrites this backup.
I rooted with CF-AutoRoot again, installed SuperSU, and was back to where I was.
UPDATE:
Only issue so far is that I had to clear the cache on the Play Store. Was getting a services error.
Rob

Thanks for the update. My own download from Sammobile completed successfully (miracle!) And I am considering doing a phone wipe/double flash/rebuild. May choose stock ROM and freeze the junk. I'm on MDL bootloader at the moment and a fairly old LTE modem.
Before I do anything i have to figure out how to back up my texts (in Slimkat messenger app) such that I can restore them properly into the new environment.
Sent from my SGH-M919 using Tapatalk

rlichtefeld said:
So, I downloaded the new firmware from SamMobile, since I was using TWRP and the OTA wouldn't have worked.
Link is here: http://www.sammobile.com/firmwares/download/54333/M919UVUFOH3_M919TMBFOH3_TMB/
I had to restart my download several times to get it to finally download completely. Luckily, Firefox would restart where it failed each time, so didn't have to restart from beginning each time. But, it took quite a while - several hours.
BTW, I did a full NAND backup with TWRP before I started this.
Used ODIN 3.09
Flashed once, but the bootloader and modem didn't take, so I did the double flash, and it worked.
To double flash:
Unchecked AutoReboot in ODIN
Flash the firmware once
Pull battery
Boot holding down Vol-Down button to get back to Download mode
Flash again
The problem with the single flash was my WiFi wouldn't turn on, and when I checked out the versions of the ROM, bootloader, modem using Samsung PhoneInfo from the Play Store, I saw the dreaded mis-matched versions.
Some of my partitions were still NH7. Evidently Samsung keeps a backup of some of the partitions and restores them when the phone is rebooted. Double flashing flashes overwrites this backup.
I rooted with CF-AutoRoot again, installed SuperSU, and was back to where I was.
UPDATE:
Only issue so far is that I had to clear the cache on the Play Store. Was getting a services error.
Rob
Click to expand...
Click to collapse
please.. can you tellme about this:
right now I am on a T-Mobile rooted so this its features on my cell:
SGH-M919
Version: 4.4.2
Band: M919UVUFNB4
Kernel: 3.4.98-KT-SGS4-KK4.4-TW-TMO-07.12.2014-ktoonsez #1
hadware version: REV0.7
Software version: MDF v1.0 Release 2
Click to expand...
Click to collapse
---can my cell update directly to this firmware using ODIN ?
---or I need to be unroot first and then install this firmware?
---or I need to upgrade my modem to the last and then install this firmware via Odin?
please can you tellme about this ? ... thanks

boni7010 said:
please.. can you tellme about this:
right now I am on a T-Mobile rooted so this its features on my cell:
---can my cell update directly to this firmware using ODIN ?
---or I need to be unroot first and then install this firmware?
---or I need to upgrade my modem to the last and then install this firmware via Odin?
please can you tellme about this ? ... thanks
Click to expand...
Click to collapse
If you flash this firmware from SamMobile. It will overwrite your modem to the newest. It will un-root your phone. And, yes you can go directly to this version from your NB4 version.
So, after you flash this firmware you will have the newest modem. And, you will have to root your phone again.
ROM = ROM
Firmware = Modem + bootloader + ROM
Rob

rlichtefeld said:
If you flash this firmware from SamMobile. It will overwrite your modem to the newest. It will un-root your phone. And, yes you can go directly to this version from your NB4 version.
So, after you flash this firmware you will have the newest modem. And, you will have to root your phone again.
ROM = ROM
Firmware = Modem + bootloader + ROM
Rob
Click to expand...
Click to collapse
Muchas Gracias!
Many, many thanks... ok.. I have a tutorial from this site to flash via Odin a old firmware...
Please can any tellme if need a new tutorial or can use the same? ( check and uncheck some options on Odin before flashing ) ...
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app

frustrated foh3
This morning OTA pushed the new update to my phone and I accepted thinking there was a lollipop update finally. I had juke woken up and didn't bother to check first.
Anyway, I'm now on FOH3 and am just trying to install custom recovery on my otherwise un-molested phone. I've tried the heimdall option as well as the cf-auto root with odin 3.09 (even attempted the double flash) either I'm doing something wrong with Odin or missing a step because when I hit start I end with 0 succeeded/0 failed and it stays in download mode. When I attempt to reboot to recovery mode, I get the blue text stating booting recovery and then black screen which eventually just goes back to stock.
Is there some other method I need to try when rooting/installing trwp for FOH3?
[edit: I'm an idiot. assumed I already had debugging turned on. I did not. *facepalm*]
-thanks in advance
I haven't flashed a phone since my galaxy s blaze 4g.

any other link other than from sam mobile??

DMD567 said:
any other link other than from sam mobile??
Click to expand...
Click to collapse
Look here:http://forum.xda-developers.com/gal...mware-firmware-kernel-modem-recovery-t3193835

rlichtefeld said:
So, I downloaded the new firmware from SamMobile, since I was using TWRP and the OTA wouldn't have worked.
Link is here: http://www.sammobile.com/firmwares/download/54333/M919UVUFOH3_M919TMBFOH3_TMB/
Rob
Click to expand...
Click to collapse
I download this file from the link .... so I get a zip file in my pc called "M919UVUFOH3_M919TMBFOH3_TMB" its a 1.56 gb... did I need to open this zip file? or take this zip file and put on Odin 3.09 in AP / PDA ?
because I open the zip file in my pc and have two files:
- SS_DL.dll
- M919UVUFOH3_M919TMBFOH3_M919UVUFOH3_HOME.tar.md5 ( 2.5 gb )
Click to expand...
Click to collapse
I think the one what I need to put on Odin its the last file "M919UVUFOH3_M919TMBFOH3_M919UVUFOH3_HOME.tar.md5" right?
but the other file " SS_DL.dll " for what reason came inside the zip file ?
I read need double flash... with " Unchecked AutoReboot" in Odin... but please can you tellme what more choices I need to check or unchecked in Odin to start flash this firmware ?
and if I need to uninstall kies from my laptop and install another Samsung drivers... or with the drivers came in Samsung Kies its ok to start flash this firmware?
thanks thanks thanks ....

boni7010 said:
I download this file from the link .... so I get a zip file in my pc called "M919UVUFOH3_M919TMBFOH3_TMB" its a 1.56 gb... did I need to open this zip file? or take this zip file and put on Odin 3.09 in AP / PDA ?
because I open the zip file in my pc and have two files:
I think the one what I need to put on Odin its the last file "M919UVUFOH3_M919TMBFOH3_M919UVUFOH3_HOME.tar.md5" right?
but the other file " SS_DL.dll " for what reason came inside the zip file ?
I read need double flash... with " Unchecked AutoReboot" in Odin... but please can you tellme what more choices I need to check or unchecked in Odin to start flash this firmware ?
and if I need to uninstall kies from my laptop and install another Samsung drivers... or with the drivers came in Samsung Kies its ok to start flash this firmware?
thanks thanks thanks ....
Click to expand...
Click to collapse
Just flash the md5 file via Odin. That's all!

boni7010 said:
I download this file from the link .... so I get a zip file in my pc called "M919UVUFOH3_M919TMBFOH3_TMB" its a 1.56 gb... did I need to open this zip file? or take this zip file and put on Odin 3.09 in AP / PDA ?
because I open the zip file in my pc and have two files:
I think the one what I need to put on Odin its the last file "M919UVUFOH3_M919TMBFOH3_M919UVUFOH3_HOME.tar.md5" right?
but the other file " SS_DL.dll " for what reason came inside the zip file ?
I read need double flash... with " Unchecked AutoReboot" in Odin... but please can you tellme what more choices I need to check or unchecked in Odin to start flash this firmware ?
and if I need to uninstall kies from my laptop and install another Samsung drivers... or with the drivers came in Samsung Kies its ok to start flash this firmware?
thanks thanks thanks ....
Click to expand...
Click to collapse
Yes, you unzip the file to your computer. The .tar.md5 file is the one that you browse to and select in Odin.
Uncheck everything in Odin. Then, flash this firmware twice, with out letting your phone boot into the system. After the first flash is finished. Pull the battery. Put the battery back in and hold the Volume Down button while you power on the phone. This will put you back in Download mode. Then, flash the same firmware again.
After that second flash, you can boot your phone into the system normally.
Rob

rlichtefeld said:
Yes, you unzip the file to your computer. The .tar.md5 file is the one that you browse to and select in Odin.
Uncheck everything in Odin. Then, flash this firmware twice, with out letting your phone boot into the system. After the first flash is finished. Pull the battery. Put the battery back in and hold the Volume Down button while you power on the phone. This will put you back in Download mode. Then, flash the same firmware again.
After that second flash, you can boot your phone into the system normally.
Rob
Click to expand...
Click to collapse
"Uncheck everything in Odin".. "Auto Reboot , and F. Reset Time" unchecked ?
and on the second flash, the same or check this two ?

boni7010 said:
"Uncheck everything in Odin".. "Auto Reboot , and F. Reset Time" unchecked ?
and on the second flash, the same or check this two ?
Click to expand...
Click to collapse
If you really wanted to, you could leave those two checked on the second flash.
However, leaving them unchecked on both flashes will work, and are the easiest instructions to follow.
Rob

Oh no.. show this :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFOH3_M919TMBFOH3_M919UVUFOH3_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
on the blue corner say "failed"
any wrong ???

boni7010 said:
Oh no.. show this :
on the blue corner say "failed"
any wrong ???
Click to expand...
Click to collapse
Read this http://forum.xda-developers.com/showthread.php?t=1622790. If that doesnt work try DIFFERENT usb cables (official works best), verisions of odin and different usb ports. Make sure usb debugging checked and power down and pull battery, then put battery back and (while its off) hold just vol down then plug it in to the computer while odins open. If this stuff doesnt work it could be motherboard (its probably not though, dont worry). Good Luck, keep trying.

rlichtefeld said:
So, I downloaded the new firmware from SamMobile, since I was using TWRP and the OTA wouldn't have worked.
Link is here:
I had to restart my download several times to get it to finally download completely. Luckily, Firefox would restart where it failed each time, so didn't have to restart from beginning each time. But, it took quite a while - several hours.
BTW, I did a full NAND backup with TWRP before I started this.
Used ODIN 3.09
Flashed once, but the bootloader and modem didn't take, so I did the double flash, and it worked.
To double flash:
Unchecked AutoReboot in ODIN
Flash the firmware once
Pull battery
Boot holding down Vol-Down button to get back to Download mode
Flash again
The problem with the single flash was my WiFi wouldn't turn on, and when I checked out the versions of the ROM, bootloader, modem using Samsung PhoneInfo from the Play Store, I saw the dreaded mis-matched versions.
Some of my partitions were still NH7. Evidently Samsung keeps a backup of some of the partitions and restores them when the phone is rebooted. Double flashing flashes overwrites this backup.
I rooted with CF-AutoRoot again, installed SuperSU, and was back to where I was.
UPDATE:
Only issue so far is that I had to clear the cache on the Play Store. Was getting a services error.
Rob
Click to expand...
Click to collapse
tried double and even quad flash, but wifi and 4g still doesn't work, I think it's about kernel, it remains same old

My Samsung S3 I747 is stuck on the logo when booting onto phone, tried using Odin..

I got my S3 from my brother since my Nexus 5 is currently broken, and with the S3 he installed CyanogenMod though it doesn't have root. So I decided to try and root it, but probably messed something up and now I'm stuck on the Cyanogen loadup screen, been waiting there for a solid 3 hours, and finally decided to try to fix it. I've tried using Odin3 3.0.7, trying to flash stock rom but I'm currently getting this error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_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> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Does anyone know what to do at this point? I've tried multiple different stock roms in case one of the stock roms had a problem. However, I flashed TWRP no problem, and I have that working for my recovery. What should I do at this point to get my phone back to Stock ROM?

Do you know what bootloader it is running? After 4.3 you cannot downgrade. Use the terminal emulator in TWRP and enter this if you're not sure:
getprop ro.bootloader
If it returns a 4.3 build number you can only flash the same or newer builds. Look for enewman17's threads in the General section for how to return to stock on those builds.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Do you know what bootloader it is running? After 4.3 you cannot downgrade. Use the terminal emulator in TWRP and enter this if you're not sure:
getprop ro.bootloader
If it returns a 4.3 build number you can only flash the same or newer builds. Look for enewman17's threads in the General section for how to return to stock on those builds.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I can't access the terminal emulator since I get stuck on the Samsung logo when trying to boot my phone.

The error happens when trying to flash aboot.mbn because, as @DocHoliday77 noted, LK3 cannot be flashed if the phone is running a 4.3 or newer bootloader.
I advise flashing TWRP and a custom ROM. This will allow you to boot the phone and determine the phone's bootloader version.

Flinze said:
I can't access the terminal emulator since I get stuck on the Samsung logo when trying to boot my phone.
Click to expand...
Click to collapse
I thought you said you had TWRP installed and working? Are you able to boot recovery at all?
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
I thought you said you had TWRP installed and working? Are you able to boot recovery at all?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yes, I am able to access recovery with TWRP working, I just don't know where the terminal emulator is. (sorry i'm not very experienced w/ TWRP)

Also one thing to note, I can't install any sort of ROMS or can't flash anything through TWRM for some reason. When I swipe to flash a rom, what happens is that it just automatically goes back to the TeamWin logo page thing, and then I'm back on the home screen of TWRM (which shows all the buttons like install, wipe, backup, restore, mount, etc.) So I can't flash through TWRM, and if possible can someone link me a custom rom that supports md5, .tar, with those file extensions since the roms I've tried all are zips of .img files. (unless there is a way to convert it to md5, .tar, etc. extentions so that I can use ODIN on my computer to flash it)
edit: what I mean by md5, .tar is a PDA file so that I can use ODIN. if possible I just want my phone to run again w/ any roms... I've been phoneless for a few days now

You can find the terminal through twrp's advanced menu. Select the root folder and go from there.
Look in enewman17's NJ2 thread. He has a recovery flashable stock recovery. Try flashing that, then factory resetting from the stock recovery.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
You can find the terminal through twrp's advanced menu. Select the root folder and go from there.
Look in enewman17's NJ2 thread. He has a recovery flashable stock recovery. Try flashing that, then factory resetting from the stock recovery.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Okay, when I typed the command getprop ro.bootloader what is get is:
I747MVLDLK4
I've tried flashing the stock recovery through TWRP, but it just again doesn't work as I explained in the previous post. So I tried using ODIN to flash it after converting it into a md5 file so that ODIN can read it and now when I try to enter recovery my screen is just black.

Looks like an i747m bootloader, not i747.
http://www.sammobile.com/firmwares/download/15321/I747MVLDLK4_I747MOYADLK4_MTA/

audit13 said:
Looks like an i747m bootloader, not i747.
http://www.sammobile.com/firmwares/download/15321/I747MVLDLK4_I747MOYADLK4_MTA/
Click to expand...
Click to collapse
Oh my gosh! Thank you!!! I just followed the instructions after the download and this recovery worked! It looks like I thought my phone was i747, but it was actually i717M, thanks!!!

Glad you got your phone back.
I can't take the credit because @DocHoliday77 helped you determine the phone's bootloader.

Flinze said:
Oh my gosh! Thank you!!! I just followed the instructions after the download and this recovery worked! It looks like I thought my phone was i747, but it was actually i717M, thanks!!!
Click to expand...
Click to collapse
Glad to hear you got it going!
audit13 said:
Glad you got your phone back.
I can't take the credit because @DocHoliday77 helped you determine the phone's bootloader.
Click to expand...
Click to collapse
Don't even worry about cred on this stuff man! You do plenty enough to be just as deserving! @dawgdoc too!
And tbh, I'm really glad you chimed in on that one! Since I'm not as familiar with which variant has which build number for the I747/I747M, (and since I'm usually used to just glancing at the last 3 characters), it probably would've taken me another 2 or 3 posts to have realized that was the problem. I Definately didn't catch it that first time!
So in the spirit of giving credit where it's due, you do deserve it here and in many, many other threads! Thanks!
Sent from my SGH-T999 using Tapatalk

Play store problems after dev conversion and successful root.

When I try to add my Gmail to sign in to the play store it says couldn't sign in there was a problem communicating with google play servers. I have found the correct google play services apk and reinstalled it. Still no luck. Anyone else have this problem?

HollowKyo said:
When I try to add my Gmail to sign in to the play store it says couldn't sign in there was a problem communicating with google play servers. I have found the correct google play services apk and reinstalled it. Still no luck. Anyone else have this problem?
Click to expand...
Click to collapse
I'm thinking about factory reset. Would I lose root and unlocked bootloader or brick possibly? But I've also seen factory reset doesn't help in most cases. I've fixed this before by downloading the correct apk on my note 2. And I'm 100 percent certain I have the right one this time. I've also cleared the caches and things. I'm a techy person. I've tried all the things.
Edit:
Actually I've been looking for a performance increasing rom without losing too many features. There's a lot I don't care about. Anyone know of a good one for this dev converted retail verizon one yet?

HollowKyo said:
I'm thinking about factory reset. Would I lose root and unlocked bootloader or brick possibly? But I've also seen factory reset doesn't help in most cases. I've fixed this before by downloading the correct apk on my note 2. And I'm 100 percent certain I have the right one this time. I've also cleared the caches and things. I'm a techy person. I've tried all the things.
Edit:
Actually I've been looking for a performance increasing rom without losing too many features. There's a lot I don't care about. Anyone know of a good one for this dev converted retail verizon one yet?
Click to expand...
Click to collapse
Are the date & time & timezone correct on your phone? Can you get to google.com from the phone's browser?
If the date & time settings are correct, try just uninstalling all updates and clearing data for Google Play Services, Google Play Store, and Google Services Framework. Make sure nothing Google related has been disabled or uninstalled.
Factory reset is safe, you won't lose dev status that way. Flashing factory firmware that contains an aboot.mbn will lose your dev status, and you'll have to go through the conversion again.

blindmanpb said:
Are the date & time & timezone correct on your phone? Can you get to google.com from the phone's browser?
If the date & time settings are correct, try just uninstalling all updates and clearing data for Google Play Services, Google Play Store, and Google Services Framework. Make sure nothing Google related has been disabled or uninstalled.
Factory reset is safe, you won't lose dev status that way. Flashing factory firmware that contains an aboot.mbn will lose your dev status, and you'll have to go through the conversion again.
Click to expand...
Click to collapse
The phone does connect to the internet. I've done all the things in the list aside from factory reset. Would you retain root? And nothing google has been disabled.

If you can retain root after a reboot, you should retain root after a factory reset. If a factory reset doesn't work, you can try flashing one of the safe upgrade packages in Odin and re-rooting.

blindmanpb said:
If you can retain root after a reboot, you should retain root after a factory reset. If a factory reset doesn't work, you can try flashing one of the safe upgrade packages in Odin and re-rooting.
Click to expand...
Click to collapse
Edit: double posted for some reason

blindmanpb said:
If you can retain root after a reboot, you should retain root after a factory reset. If a factory reset doesn't work, you can try flashing one of the safe upgrade packages in Odin and re-rooting.
Click to expand...
Click to collapse
Factory reset did nothing. Now it doesn't even let me try to sign in. Just straight to the can't connect error.

I found a Google Apps package that has all the Google Apps in it but when I tried to flash the zip it said I had the wrong one. Could someone point me in the right direction? Would reinstalling the gapps package even do anything? Any help is greatly appreciated. Until I fix this my phone is practically unusable.

The gapps package said it couldn't install when I tried the zip from twrp. I'm really in need of some help. I can't use my phone at all since I've factory reset it and the play store won't work.
Edit: I tried wiping the cache and dalvik cache in twrp and now my phone is boot looping. Yay

HollowKyo said:
The gapps package said it couldn't install when I tried the zip from twrp. I'm really in need of some help. I can't use my phone at all since I've factory reset it and the play store won't work.
Edit: I tried wiping the cache and dalvik cache in twrp and now my phone is boot looping. Yay
Click to expand...
Click to collapse
Is this a custom rom that you're on or official build, and if so, which build are you on? If you're on the latest official build 5.1.1 (BPA1), then like someone else suggested above, I'd suggest making sure that you have Samsung USB drivers installed on your PC, putting your phone in Downlode Mode, connecting it to the PC and using Odin to flash hsbadr's N910VVZW2BPA1 Stock Restore (Incremented) (your unlocked bootloader will be preserved) and twrp-2.8.5.0-trltevzw.img.tar, then using recovery to flash a permissive kernel such as MultiSystem kernel for TouchWiz 5.1.1. and then BETA-SuperSU-v2.71-20160331103524.zip to reroot. That should at least get your device booted up and working again.

livinxtreme2114 said:
Is this a custom rom that you're on or official build, and if so, which build are you on? If you're on the latest official build 5.1.1 (BPA1), then like someone else suggested above, I'd suggest making sure that you have Samsung USB drivers installed on your PC, putting your phone in Downlode Mode, connecting it to the PC and using Odin to flash hsbadr's N910VVZW2BPA1 Stock Restore (Incremented) (your unlocked bootloader will be preserved) and twrp-2.8.5.0-trltevzw.img.tar, then using recovery to flash a permissive kernel such as MultiSystem kernel for TouchWiz 5.1.1. and then BETA-SuperSU-v2.71-20160331103524.zip to reroot. That should at least get your device booted up and working again.
Click to expand...
Click to collapse
Thanks. I'll try this now.

I had that problem when i installed jasmine rom, what i did was boot in to recovery,wipe data and cache and install jasmine rom again and now is fine.

livinxtreme2114 said:
Is this a custom rom that you're on or official build, and if so, which build are you on? If you're on the latest official build 5.1.1 (BPA1), then like someone else suggested above, I'd suggest making sure that you have Samsung USB drivers installed on your PC, putting your phone in Downlode Mode, connecting it to the PC and using Odin to flash hsbadr's N910VVZW2BPA1 Stock Restore (Incremented) (your unlocked bootloader will be preserved) and twrp-2.8.5.0-trltevzw.img.tar, then using recovery to flash a permissive kernel such as MultiSystem kernel for TouchWiz 5.1.1. and then BETA-SuperSU-v2.71-20160331103524.zip to reroot. That should at least get your device booted up and working again.
Click to expand...
Click to collapse
When I try I get,
SW REV CHECK FAIL : [tz]Fused 2 > Binary 1
On my phone and,
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910VVRU2BPA1_StockRestore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> NON-HLOS.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> cache.img.ext4
<ID:0/008> modem.bin
<ID:0/008> recovery.img
<ID:0/008> rpm.mbn
<ID:0/008> sbl1.mbn
<ID:0/008> sdi.mbn
<ID:0/008> system.img.ext4
<ID:0/008> tz.mbn
<ID:0/008> RQT_CLOSE !!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In odin.

HollowKyo said:
When I try I get,
SW REV CHECK FAIL : [tz]Fused 2 > Binary 1
Click to expand...
Click to collapse
Then your bootloader version most likely doesn't match the file you're flashing. Do you know the last official build that you were on, and which file that I linked you to did you attempt to Odin flash just now, the Stock Restore one or the Stock Restore Incremented? If you at any point accepted the official OTA to Lollipop, then your bootloader has been incremented, meaning you'll need to flash the Stock Restore Incremented file. However, if you stayed on Kit Kat, then flash the plain Stock Restore file.

livinxtreme2114 said:
Then your bootloader version most likely doesn't match the file you're flashing. Do you know the last official build that you were on, and which file that I linked you to did you attempt to Odin flash just now, the Stock Restore one or the Stock Restore Incremented? If you at any point accepted the official OTA to Lollipop, then your bootloader has been incremented, meaning you'll need to flash the Stock Restore Incremented file. However, if you stayed on Kit Kat, then flash the plain Stock Restore file.
Click to expand...
Click to collapse
I did take the ota. Now it boots straight to odin mode and says to use verizon software repair assistant.
I was on 5.1.1 I see what I need. I'll try this right now.

HollowKyo said:
I did take the ota. Any chance you could link me the download I need? Now it boots straight to odin mode and says to use verizon software repair assistant.
Click to expand...
Click to collapse
That's okay, it'll do that when ever there has been a flash fail. We can fix it. If you accepted the official OTA to Lollipop then your bootloader has been incremented, meaning you'll need to flash the N910VVRU2BPA1_StockRestore_Incremented.tar.md5.7z file. Be sure and visit the original post and give hsbadr thanks for his restore file though.

livinxtreme2114 said:
That's okay, it'll do that when ever there has been a flash fail. We can fix it. If you accepted the official OTA to Lollipop then your bootloader has been incremented, meaning you'll need to flash the N910VVRU2BPA1_StockRestore_Incremented.tar.md5.7z file. Be sure and visit the original post and give hsbadr thanks for his restore file though.
Click to expand...
Click to collapse
Followed your instructions. I am now back up and running at 100% and rooted. Thank you so much.

HollowKyo said:
Followed your instructions. I am now back up and running at 100% and rooted. Thank you so much.
Click to expand...
Click to collapse
That's awesome. Glad I could help you out, brother.

livinxtreme2114 said:
That's awesome. Glad I could help you out, brother.
Click to expand...
Click to collapse
That was some fantastic assistance you gave there. way to represent the community well :good::good::good:

sudermatt said:
That was some fantastic assistance you gave there. way to represent the community well :good::good::good:
Click to expand...
Click to collapse
I really appreciate that!