Develop Bugs

[RESOLVED] Flashing SGH-T999 back to stock ROM [FAIL!]

So I decided I would flash back to stock ROM using this topic as a guide. I downloaded the ODIN stock file listed in the topic and started the process from the ODIN Mode and these were the messages I got in the Odin software on my machine:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDLJA_T999TMBDLJA_T999UVDLJA_HOME.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img.ext4
<ID:0/005> NON-HLOS.bin
<ID:0/005> recovery.img
<ID:0/005> rpm.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> system.img.ext4
<ID:0/005> __XmitData_Read ..
<ID:0/005> XmitData Fail..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It shows my Current Binary as: Samsung Official and System Status as Official, but it won't boot the phone. At this point I'm stuck without a working phone and I don't know what I can do from here. I know awhile ago I got some custom ROM to load on it a long time ago, but I wanted to go back to stock just so I could start from scratch.
Resolved By
Installing Clockwork Mod Recovery 6.0.3.0 using Odin v3.07.
Loaded a firmware update specifically for an US SGH-T999 onto my microSD card and booted into ClockWork Mod Recovery using the options to install via an external SDcard.
Brought phone back into download mode and used Odin to install STOCK ROM (T999_UVDLJA) for my phone found on this page here.

Try again
also download things from this thread http://forum.xda-developers.com/showthread.php?t=1949687 I've used it about 3 times in the last week while attempting to sell this phone I can not for the life stay stock for more than a day lol.

Havent run into this before, at least not that I remember.
It looks like everything flashes fine, but after flashing system.img it has
XmitData Read
XmitData Fail
Not sure what that means. Does it appear to completely flash the system portion? Or does it fail at the beginning, or middle of it?
If it finishes flashing system, then its failing at the start of tz.mbn. if that's the case, Can you boot into recovery? You could try flashing the LJC or MD5 firmware pkg available in the dev section. Then try to reboot. Ill try to find the link in a few. If it won't reboot go back in recovery and flash a stock rom and try that.
Does it happen every time at the same point? Maybe your computer is starting into a power saving mode and killing tge connection?
As mt3g said, try again after redownloading the firmware. Make sure you are using Odin 3.07. If kies is installed, get rid of it.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Havent run into this before, at least not that I remember.
It looks like everything flashes fine, but after flashing system.img it has
XmitData Read
XmitData Fail
Not sure what that means. Does it appear to completely flash the system portion? Or does it fail at the beginning, or middle of it?
Click to expand...
Click to collapse
It sits there on the last item <ID:0/005> system.img.ext4 and then about a few minutes Odin shows the rest and it displays FAIL in bright, pinkish red.
DocHoliday77 said:
If it finishes flashing system, then its failing at the start of tz.mbn. if that's the case, Can you boot into recovery? You could try flashing the LJC or MD5 firmware pkg available in the dev section. Then try to reboot. Ill try to find the link in a few. If it won't reboot go back in recovery and flash a stock rom and try that.
Click to expand...
Click to collapse
I have been about to boot into CWM Touch Recovery 5.8.4.7. or CWM v5.5.0.4.
DocHoliday77 said:
Does it happen every time at the same point? Maybe your computer is starting into a power saving mode and killing tge connection?
Click to expand...
Click to collapse
That's an excellent thought, I'm going to check that.
DocHoliday77 said:
As mt3g said, try again after redownloading the firmware. Make sure you are using Odin 3.07. If kies is installed, get rid of it.
Click to expand...
Click to collapse
Kies hasn't been on this machine in years, This is a clean install in which Kies has not been installed on it. I just finished downloading this firmware, so I'm going to see how that goes.

Hrres the thread with the recovery flashable firmware.
http://forum.xda-developers.com/showthread.php?t=2282603
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Hrres the thread with the recovery flashable firmware.
http://forum.xda-developers.com/showthread.php?t=2282603
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried this with CWM v5.5.0.4 and it threw the following error:
Code:
-- Installing: /sdcard/T999_UVDMD5_firmware_v4.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product" == "d2tmo"
E:Error in /sdcard/T999_UVDMD5_firmware_v4.zip
(Status 7)
Installation aborted.

Update your recovery. See my sig for downloads.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Update your recovery. See my sig for downloads.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I've updated to the most recent stock recovery listed in the links you noted. However during it's initial loading on the phone the following text appeared on the screen with the Android icon laying down and a triangle above it.
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
E:Error in /cache/recovery/sec_csc.zip
(Status 7)
Installation aborted.
I tried clearing user data and cache and then rebooted, message present is now:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
I attempted to update from external storage:
Code:
-- Install /sdcard ...
Finding update package...
Opening package...
Verifying package...
E:signature verification failed

That sounds like you have the stock recovery still installed.
Use Odin to flash the latest CWM to your phone. Flash exactly the same as you would the firmware in Odin. Just make sure you download the .tar file from my downloads page.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
That sounds like you have the stock recovery still installed.
Use Odin to flash the latest CWM to your phone. Flash exactly the same as you would the firmware in Odin. Just make sure you download the .tar file from my downloads page.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I mistook your suggestion as to mean to go with stock recovery, I will report back shortly with the correct recovery option.
I went with ClockworkMod Recovery v6.0.3.0. I installed that successfully and then I was able to access the external SD card and install the zip file, it came back as:
Code:
-- Installling: /external_sd/T999_UVDMD5_firmware_v4.zip
Finding update package...
Opening update package...
Installing update...
T999 UVDMD5 Firmware Upgrade (w/Modem)
Extracting files and setting permissions...
Verifying checksums...
Updating firmware...
Done!
Cleaning up...
Install from sdcard complete.

Ok good! Now try to flash a stock rom. Any rom should do, but I say stock just so the build.prop and everything is right for your model. Up to you if you want to try something different.
After that, if you want, try flashing the firmware with Odin again. If the problem was on your phone, hopefully all of what you just did will solve it.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Ok good! Now try to flash a stock rom. Any rom should do, but I say stock just so the build.prop and everything is right for your model. Up to you if you want to try something different.
After that, if you want, try flashing the firmware with Odin again. If the problem was on your phone, hopefully all of what you just did will solve it.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Ok, installed T999_UVDLJA found on this page. Odin was successful in its installation. Thanks for your help.

MistoRoboto said:
Ok, installed T999_UVDLJA found on this page. Odin was successful in its installation. Thanks for your help.
Click to expand...
Click to collapse
Awesome! Glad I could help! Theres often more than one way to get a desired result! :thumbup:
Sent from my SGH-T999 using xda premium

Bricked?
DocHoliday77 said:
Awesome! Glad I could help! Theres often more than one way to get a desired result! :thumbup:
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hello,
I had pretty much the same problem, couldn't install stock ROM through Odin. Followed these steps, installed latest CWM recovery, then flashed firmware update, it installed successfully. BUT after that my phone won't turn on.
Please help!

Won't turn on as on you get nothing? Bootloops? Vibration? Did you remove the battery?
Sent from my SGH-T999L using Tapatalk 4

Hi, I am in a similar situation and I am new in all of this.
Suddenly my SGH-T999 started to reboot in a loop. So I googled it and find this trend. I already tried to install a stock firmware using ODIN but always I get an 'aboot.mbn' error :crying:
I can enter in download mode but NOT in recovery, so I could done your first point (Installing Clockwork Mod Recovery 6.0.3.0 using Odin v3.07) but can't complete step 2 because I can't get into recovery.
Any help??
Thanks!

matiatucci said:
Hi, I am in a similar situation and I am new in all of this.
Suddenly my SGH-T999 started to reboot in a loop. So I googled it and find this trend. I already tried to install a stock firmware using ODIN but always I get an 'aboot.mbn' error :crying:
I can enter in download mode but NOT in recovery, so I could done your first point (Installing Clockwork Mod Recovery 6.0.3.0 using Odin v3.07) but can't complete step 2 because I can't get into recovery.
Any help??
Thanks!
Click to expand...
Click to collapse
Go the route of Cyanogenmod. They have an automated walk-through installer that will get you at least a clean OS to work from. Only caveat is that you'll need Windows to run that installer.

MistoRoboto said:
Go the route of Cyanogenmod. They have an automated walk-through installer that will get you at least a clean OS to work from. Only caveat is that you'll need Windows to run that installer.
Click to expand...
Click to collapse
Go the route of Cyanogenmod from my PC? And sorry, can you explain in more detail about the caveat thing. I just google it, but I didn´t know it.
Thanks!

matiatucci said:
I can enter in download mode but NOT in recovery, so I could done your first point (Installing Clockwork Mod Recovery 6.0.3.0 using Odin v3.07) but can't complete step 2 because I can't get into recovery.
Any help??
Thanks!
Click to expand...
Click to collapse
Have you tried flashing custom recovery and booting to it?

serio22 said:
Have you tried flashing custom recovery and booting to it?
Click to expand...
Click to collapse
I don´t know if I understand correct what do you mean. What I've done is download stock firmwares and tried to flash it with ODIN, but throws me an error (aboot.mbn error). I read that perhaps if I charge my battery to 100% I can enter in recovery mode, but I won´t charge it with my cellphone in this status.
Thanks!

[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:

[UPDATED 9/27] [ODIN] MetroPCS - M919N (UVUAMF2) STOCK ODIN Flashable

Hey there,
I know some people have been requesting this for quite some time! This couldn't have been possible without @techguy1214 so a huge thanks goes out to him!
This is the absolute STOCK M919N Firmware. (THIS IS NOT ROOTED!)
EXPERIMENTAL: This is UNTESTED by me, I compiled this ODIN tar file using the same structure the T-Mobile ODIN File has. I do not have the MetroPCS version of this phone, I have the T-Mobile version. But I figured enough people wanted it so I would try to make it happen.
CONFIRMED WORKING!
I will not be help responsible if you brick your device or flash this incorrectly and your phone ends up blowing up. You have been warned.
Click to expand...
Click to collapse
NOTE: Because this is not officially signed by Samsung, I believe your flash counter will go up, use Triangle Away to reset your counter!
Huge thanks goes out to @danyvw for picking up my slack, new instructions posted.
Link: https://docs.google.com/file/d/0BxJFwkvU-C2McW5zU0RWQ01hM2s/edit?usp=sharing
1. Download the above .zip file and extract the .tar file in the archive and save it somewhere
2. Reboot your phone to download mode.
To get download mode shut down the device. After it shuts off completely simultaneously press the Down volume key+ Home button + press the power button .
3. Start Odin
4. Click on the PDA button and browse to the .tar file that you extracted in step 1 and select it
5. DO NOT PUT .PIT FILE AND DO NOT TICK REPARTITION
6. Connect the USB cable and wait for the ID:COM section to turn blue
7. Click start to flash
8. Do not disconnect the cable or turn off the device once the flash has started, it’s going to take some time to flash, when finish exit Odin and disconnect USB.
9. Let the phone start and Voila!!!!!!

theexel said:
Hey there,
I know some people have been requesting this for quite some time! This couldn't have been possible without @techguy1214 so a huge thanks goes out to him!
This is the absolute STOCK M919N Firmware. (THIS IS NOT ROOTED!)
EXPERIMENTAL: This is UNTESTED by me, I compiled this ODIN tar file using the same structure the T-Mobile ODIN File has. I do not have the MetroPCS version of this phone, I have the T-Mobile version. But I figured enough people wanted it so I would try to make it happen.
AGAIN.. THIS MAY NOT WORK.
If it doesn't use the T-Mobile ODIN, it will work, but of course, you will have the T-Mobile Baseband and whatnot, but if it does not work, I will try to work on it again soon!
NOTE: Because this is not officially signed by Samsung, I believe your flash counter will go up, use Triangle Away to reset your counter!
Download the TAR file: https://copy.com/lyMNNbzjaNYm
Click to expand...
Click to collapse
i tired it it worked 100% thanks

techguy1214 said:
i tired it it worked 100% thanks
Click to expand...
Click to collapse
No, thank you @techguy1214.
Without you, we wouldn't have these files! :highfive:

What is STOCK M919N ?
Can you elaborate more about the different between this M919N & M919V (as an example):
Can we flash without root ?
Compatibility with what ROM or firmware ?
Report log or advantages...etc.?
Anything more...?

itzik_man said:
Can you elaborate more about the different between this M919N & M919V (as an example):
Can we flash without root ?
Compatibility with what ROM or firmware ?
Report log or advantages...etc.?
Anything more...?
Click to expand...
Click to collapse
M919N is the MetroPCS variant of the Galaxy S4.
M919V is the Wind / Mobilicity / Videotron variant of the Galaxy S4, I believe.
This is for people that maybe messed up flashing a ROM or simply want to go back to barebone OFFICIAL MetroPCS stock firmware due to any reason. (Most likely they broke something and want to send it to warranty, lol.)

techguy1214 said:
i tired it it worked 100% thanks
Click to expand...
Click to collapse
any 1 else confirm this....??

djlucklu said:
any 1 else confirm this....??
Click to expand...
Click to collapse
Seems not...

arocker said:
Seems not...
Click to expand...
Click to collapse
Did not work for me. I jumped the gun and flashed a tmo stock rom to see if I could unlock my phone for free. I am unable to flash back to this rom now and can't unlock using a tmo rom.
Can anyone confirm that the pit files are different between the M919 and M919N? I tried a lot of different things last night and I think I flashed the M919 pit file as well as the rom, which is most likely my problem. Odin fails as soon as it tries to write.

Doesn't work
I tried to flash many times with different downloads and always get the same flash error:
<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> NON-HLOS.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

I get the exact same error.

downloading now ill let you know

fatalfury said:
downloading now ill let you know
Click to expand...
Click to collapse
Any update fatalfury?

people with errors making sure kies is not open right ? also try the USB port on back of computer and test again

krazierokz said:
people with errors making sure kies is not open right ? also try the USB port on back of computer and test again
Click to expand...
Click to collapse
Is not with Kies, its with Odin. Kies does not have firmware support for the SGH-M91N.

Understood just stating that Odin and kies open together conflicts and Odin won't run right that's all I'm saying
sent from my t mobile S4

Fixing Issues an PLEAS!!!
zbennett15 said:
I get the exact same error.
Click to expand...
Click to collapse
For this you are going to need mobile Odin To Flash an you will need to flash twice after you flash it the first time!:laugh::fingers-crossed:

techguy1214 said:
For this you are going to need mobile Odin To Flash an you will need to flash twice after you flash it the first time!:laugh::fingers-crossed:
Click to expand...
Click to collapse
Same error with PC odin, and when trying to open with mobile odin - partition could not be found.
---------- Post added at 07:20 PM ---------- Previous post was at 06:50 PM ----------
techguy1214 said:
i tired it it worked 100% thanks
Click to expand...
Click to collapse
Hey! how you flashed it? Thanks in advance.

I made some changes to techguy file.Is Working flawlessly with Odin, posted on androidforums:
http://androidforums.com/metropcs-g...t/773372-unofficial-m919nuvuamf2-working.html

danyvw said:
I made some changes to techguy file.Is Working flawlessly with Odin, posted on androidforums:
http://androidforums.com/metropcs-g...t/773372-unofficial-m919nuvuamf2-working.html
Click to expand...
Click to collapse
Updated OP, thank you.

Exel said:
Updated OP, thank you.
Click to expand...
Click to collapse
Thank you! Without your file I wouldn't have done anything. :good:

Help! N7105 cant wipe cache or install

Hello everyone.
Phone Samsung Galaxy note 2 gt n7105 T mobile UK
So this morning my phone was working fine and while i was playing a game my phone literally just went dead, black screen and then stuck on galaxy note II screen.
So booted into recovery which is Philz touch 4 (had it on there for a few months so cant be more specific)
And i figured i would just do a wipe and reinstall.
But now i cant wipe cache just get error formatting /cache!
So i thought i would try just reinstalling a rom, i was using Jedi x2 rom previously so i went to try installing that, and it started to install then goes blank and reboots back to galaxy note II screen.
rebooted into recovery to check log and i get this.
I : Checking for extendedcommand & OpenRecveryScript..
I ; Skiping execution of extendedcommand. file not found
I : Using /data/media for /sdcard
w : Failed to mount /dev/block/mmcblk0p16 )invalid argument)
I :Skipping execution of OpenRecoveryScript, file not found
E : Cant't open /Cache/recovery/log
E : Cant't open /Cache/recovery/log
E : Cant't open /Cache/recovery/last_lo
E : Cant't open /Cache/recovery/log
So i thought i would just try and install stock rom via odin which failed
<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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
So now i dont know what to do, is my phone dead?
Please help, i tried to find info on the forums which lead me to try a few of the steps i have tried already and now im really stuck

Was your phone on updated bootloader ?
I notice your phone is N7105 what stock rom did you try to flash ?
Sent from my SGH-T889 using xda app-developers app

Can you attach screenshot with device reboot in download mod?
Sent from my SM-N900 using xda premium

dr.ketan said:
Can you attach screenshot with device reboot in download mod?
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
I have no way of taking a screen shot but ill type what it says there.
ODIN MODE
Product name : GT-N7105
Custom binary download: yes (17 counts)
Current binary: custom
System status : custom
(next 2 lines are in dark grey)
Knox warrenty void: 1
RP SWREV: A2

ciphercodes said:
Was your phone on updated bootloader ?
I notice your phone is N7105 what stock rom did you try to flash ?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Bootloader i think was fairly new, i dont know how often they update them (thats if you mean the philz touch thing?)
As for the rom, i got the lastest from SamMobile but they are classed as EE and not Tmobile ones so its possible thats why i have an issue?
Im a bit of a noob with the way Samsung and roms work. Was no problems with my old HTC.

You will have to download the exact firmware for your device N7105 and flash it using odin.
Sent from my SGH-T889 using xda app-developers app

ciphercodes said:
You will have to download the exact firmware for your device N7105 and flash it using odin.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Well i thought i already had what i needed, and since then i have tried a couple older versions too.
Unless im not even getting the correct roms/firmware.
I just get
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
In odin.

nollington said:
Well i thought i already had what i needed, and since then i have tried a couple older versions too.
Unless im not even getting the correct roms/firmware.
I just get
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
In odin.
Click to expand...
Click to collapse
Your phone is on the 4.3 bootloader, do not try to flash older 4.1.x firmwares they are going to fail.
Did you try emergency recovery using KIES ?
You can also try to flash the using ODIN v 1.85.
I see that stock ROMS for N7105 on sammobile are region specific, I am not sure if flashing a ROM of incorrect region with fail but try to download the one for your region.

ciphercodes said:
Your phone is on the 4.3 bootloader, do not try to flash older 4.1.x firmwares they are going to fail.
Did you try emergency recovery using KIES ?
Try ODIN v 1.85.
I see that stock ROMS for N7105 on sammobile are region specific, I am not sure if flashing a ROM of incorrect region with fail but try to download the one for your region.
Click to expand...
Click to collapse
I dont know anything about KIES to be honest.
Ill look for a download of an older odin and try that.
As for the Roms on sammobile, i have been using the UK ones but the ones for EE since EE took over t mobile / orange. It seems thay are the only ones available

So i just found this thread on Kies
http://forum.xda-developers.com/showthread.php?t=2261153
Is this what i should try? i dont want to try it without knowing its what i should be doing.

nollington said:
So i just found this thread on Kies
http://forum.xda-developers.com/showthread.php?t=2261153
Is this what i should try? i dont want to try it without knowing its what i should be doing.
Click to expand...
Click to collapse
Yes.
Remember if your phone can go in to download mode then it can still be recovered, just need to find the right firmware.

ciphercodes said:
Yes.
Remember if your phone can go in to download mode then it can still be recovered, just need to find the right firmware.
Click to expand...
Click to collapse
Ok well so far i cant get odin to install anything. I either get an error after NAND as mentioned previously, or it gets stuck on set up connection.
Possibly a ROM/Firmware issue? but i have tried 3 different ones from sammobile all for EE UK as i cant find specific tmobile anymore.
As for what my phone can do at the moment.
It can boot into Philz touch but will reboot if you do anything like format cache/system/factory reset etc.
And can also put it into download mode with menu + volume down + power.
So i guess ill try that KIES thing and then see what happens.
If you have any other advice for me i would appreciate it.
And also thank you for your help so far

nollington said:
Ok well so far i cant get odin to install anything. I either get an error after NAND as mentioned previously, or it gets stuck on set up connection.
Possibly a ROM/Firmware issue? but i have tried 3 different ones from sammobile all for EE UK as i cant find specific tmobile anymore.
As for what my phone can do at the moment.
It can boot into Philz touch but will reboot if you do anything like format cache/system/factory reset etc.
And can also put it into download mode with menu + volume down + power.
So i guess ill try that KIES thing and then see what happens.
If you have any other advice for me i would appreciate it.
And also thank you for your help so far
Click to expand...
Click to collapse
Since you were using Philz recovery did you take a full back up ? If yes, can you try to restore it ?
If Philz is not responding as it should then try flashing Philz via ODIN.

ciphercodes said:
Since you were using Philz recovery did you take a full back up ? If yes, can you try to restore it ?
If Philz is not responding as it should then try flashing Philz via ODIN.
Click to expand...
Click to collapse
I had made a back up previously (a few months ago) and tried to install that via philz but it wouldnt even read the file.
Also tried to reflash philz via odin and it fails.
And currenctly im having issues with KIES finding my device. It just doesnt seem to want to connect to it.

So i also just saw this while trying to get a backup to work.
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p13
Error formatting /system!
Im guessing something is pretty corrupt since i cant format cache or system

nollington said:
I had made a back up previously (a few months ago) and tried to install that via philz but it wouldnt even read the file.
Also tried to reflash philz via odin and it fails.
And currenctly im having issues with KIES finding my device. It just doesnt seem to want to connect to it.
Click to expand...
Click to collapse
ok if your trying to install via the KIES software you need to be i download mode not recovery . once your in recovery mode should start seeing your device and start installing drivers or drivers might already be installed and it will ask you for device model number and serial number and will download the current OS and install . i had the same issue as you did and recover my phone via KIES hope this helps

MERK77 said:
ok if your trying to install via the KIES software you need to be i download mode not recovery . once your in recovery mode should start seeing your device and start installing drivers or drivers might already be installed and it will ask you for device model number and serial number and will download the current OS and install . i had the same issue as you did and recover my phone via KIES hope this helps
Click to expand...
Click to collapse
I have been in download mode but KIES wont connect to my phone it just sits on connecting to device for about 10 mins and then says to reboot the device. And then does the same again.
Even tried a different cable and that didnt make any difference.

ciphercodes said:
Your phone is on the 4.3 bootloader, do not try to flash older 4.1.x firmwares they are going to fail.
Did you try emergency recovery using KIES ?
You can also try to flash the using ODIN v 1.85.
I see that stock ROMS for N7105 on sammobile are region specific, I am not sure if flashing a ROM of incorrect region with fail but try to download the one for your region.
Click to expand...
Click to collapse
I flashed an EE firmware 4.3 over H3G 4.1.2 using old Odin. Works fine but you lose all internal data
Sent from my GT-I9100 using XDA Premium HD app

Im thinking it is a storage problem.
Since im having issues with cache,storage,data formatting.
I read on a thread somewhere i could have to install some .PIT?
Is there anyway to do a kind of full wipe with odin or anything? and then be able to reinstall everything such as partitions?
Those could be really noob things to ask, but im not really much of a "pro" with the phone side of things, just thinking along the lines of regular storage systems being corrupt.

nollington said:
Im thinking it is a storage problem.
Since im having issues with cache,storage,data formatting.
I read on a thread somewhere i could have to install some .PIT?
Is there anyway to do a kind of full wipe with odin or anything? and then be able to reinstall everything such as partitions?
Those could be really noob things to ask, but im not really much of a "pro" with the phone side of things, just thinking along the lines of regular storage systems being corrupt.
Click to expand...
Click to collapse
The last ODIN log you posted shows that it failed while flashing sboot.bin which is the bootloader. I think that was when you tried to flash the older firmwares.
Here is the PIT file for N7105 but I cannot assure if it work or not as I have a different phone SGH-T889.
http://forum.xda-developers.com/showthread.php?t=2137008
I do not think the partition table is messed. I still think flashing the correct firmware via ODIN should get this fixed.
Few other things to try:
You can also flash CF-Autoroot for N7105, it comes with stock recovery and then you can wipe data and perform a factory reset from there.
http://download.chainfire.eu/255/CF-Root/CF-Auto-Root/CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip
You can try flashing TWRP or CWM via ODIN and use then wipe the cache.

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!