Related
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!
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:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
My Galaxy Note II has been stuck on this for a while. I was trying to recover it via kies but it never worked so i tried out the Odin and this happened..
Please show me to any tutorial or post below a tutorial.
Katrxc said:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
My Galaxy Note II has been stuck on this for a while. I was trying to recover it via kies but it never worked so i tried out the Odin and this happened..
Please show me to any tutorial or post below a tutorial.
Click to expand...
Click to collapse
You working???
Lots of info is missing for anyone to help you....
Who is your network carrier? What did you try to flash? What version of ODIN....
If you are on ATT this may help
http://forum.xda-developers.com/showthread.php?t=2589891
Redownload the rom file. The cheesy sites developers use to host their roms are sketchy at best, and at worst they give you an incomplete file.
rangercaptain said:
Redownload the rom file. The cheesy sites developers use to host their roms are sketchy at best, and at worst they give you an incomplete file.
Click to expand...
Click to collapse
But he's using ODIN.... So he's flashing firmware.
Every ROM is firmware amigo. If the firmware is in a zip file set up for TWRP or CWR, good. If its in the tar format we use Odin3.
If you look inside the zip file it has a tar file in it.
rangercaptain said:
Every ROM is firmware amigo. If the firmware is in a zip file set up for TWRP or CWR, good. If its in the tar format we use Odin3.
If you look inside the zip file it has a tar file in it.
Click to expand...
Click to collapse
:
Uh yea,,,,
Senior Member
Thanks Meter 682
Posts: 1,584
Join Date: Sep 2010
I may be slightly familiar with the process and the difference.
I was pointing out the fact that it is failing while flashing with ODIN...
So your comment that
"The cheesy sites developers use to host their roms are sketchy at best, and at worst they give you an incomplete file."
was probably not relevant in this case, since 99.969% of the free ROMs that devs freely build and graciously host on free sites, are not flashed in ODIN.
Only 682? Thats pretty weak amigo. Since 2010? You're so new you glow! I don't know what your malfunction is.
Samsung is a ROM/firmware developer. And Samfirmware.com (or whatever its called) is a sometimes spotty site.
The advice is still the same:
1. Redownload
2. Use the factory cable
3. Use the powered usb port
4. Use another version of Odin3.
rangercaptain said:
Only 682? Thats pretty weak amigo. Since 2010? You're so new you glow! I don't know what your malfunction is.
Samsung is a ROM/firmware developer. And Samfirmware.com (or whatever its called) is a sometimes spotty site.
The advice is still the same:
1. Redownload
2. Use the factory cable
3. Use the powered usb port
4. Use another version of Odin3.
Click to expand...
Click to collapse
No problem here slick. Yep having a life is rough.
I guess I would have to agree that a download of the stock ROM firmware from sammobile.com (which is not actually associated with the ROM/firmware developer Samsung) (http://www.sammobile.com/about-us/) would be a good idea, and then flash via ODIN.
Vice a download of a Dev ROM that perhaps an XDA developer posted on a cheesy site, which I mistaken thought you were implying.
That is why I posted the simple glowing statement, but it's an ODIN flash. Didn't expect a ROM flash 101 class.
Attack the OP's problem, not members who contribute solutions.
All you have done here was try to show everyone you're the smartest guy in the room.
Run along now.
rangercaptain said:
Attack the OP's problem, not members who contribute solutions.
All you have done here was try to show everyone you're the smartest guy in the room.
Run along now.
Click to expand...
Click to collapse
Respectfully, that's what I was trying to do, by asking questions. Like what were they trying to flash.
Then you jumped in and suggested to redownload, Without ensuring they were even flashing the right thing.
I have seen you give out great advice. That's why this seemed odd.
99% of the times a flash fails in Odin3 or recovery its because of a file error. If it was the wrong file for the phone it would flash and brick or it would stop immediately. But since he got most of the way through the process, I concluded correct file but likely corrupt download.
But you already know this.
---------- Post added at 01:49 PM ---------- Previous post was at 01:44 PM ----------
I actually made up the 99%, but its most of the time.
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
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!