Related
3/3/2011 - I've been away for several weeks, sorry about that. I've also moved on and will be futzing with my shiny new Xoom. I will not be working on Tab projects for the immediate future, it at all.
Been fun
There seems to be a genuine lack of activity on the Sprint version of the Tab. Hopefully this will allow folks to start making themes and ROM's for the Sprint flavor of the tablet.
This package was created via the "Rotobackup" Method pioneered by Rotohammer and maniac3389.
As far as I can tell, I'm the only one who has done this on the Sprint-flavor of the Tab, so this is all beta and VERY RISKY. I do not recommend using this unless you are VERY familiar with flashing Android devices.
NOTE: This is ALMOST STOCK. The Rotobackup process did not dump the modem.bin file properly. To address this, I used the modem from the Epic 4G (SPH-D700-DK28-8Gb-REL). This modem effectively disables GPS. There is no known fix yet.
Updates:
12/13/2010 - Looks like the package borks GPS. You cannot acquire satellites after flashing.
12/29/2010 - GPS is still broke if you use the package containing the modem. Looks like we will need to wait until an update is released. Feel free to keep troubleshooting the issue, I'll update the OP if somebody figures it out.
12/29/2010 - Uploaded package WITHOUT the modem
12/29/2010 - Introduced Zypher, a fully deodexed updater.
WARNING!!! YOU CAN BRICK YOUR DEVICE VERY EASILY.
THESE ARE FOR SPRINT VERSIONS OF THE TAB.
Instructions:
Backup your settings with Titanium Backup
Do a factory reset: Settings>Privacy>Factory Data Reset
Turn on USB debugging: Settings>Applications>Development>USB debugging
Extract the RAR archive
Open "Odin3 v1.31.exe"
Reboot into Download Mode (adb reboot download)
Do not check Re-Partition option
Click PIT, select pit.pit
Click PDA, Select .tar file
Click Start
Downloads
Download 1 - Stock, no modem - Sprint Only! Use this if you want to get back to stock (rooted). ALL USERS SHOULD TRY THIS PACKAGE FIRST! If you still have problems, then you need to use the modem package which kills GPS (Download 2).
Download 2 - Stock, with modem - Sprint Only! Includes modem from Epic 4G - Only use if your Tab will not boot, this package will kill GPS
THERE IS NO WAY TO GET THE STOCK MODEM BACK AFTER YOU FLASH!!
Download Zypher v1 - Sprint Only! Deodexed\zipaligned. I recommend running a factory reset before applying the package. Settings>Privacy>Factory Data Reset
Zypher Details:
Based off DJ30
Deodexed and zip aligned
Removed startup/shutdown sounds
Added Busybox installer
Added Titanium Backup
Added Z4Root
Added AD-Free hosts file
To do list:
Work in the full screen fix (via Spareparts)
Replace launcher with LauncherPro
Theme everything
Nice work, not that Sprint would allow it, but did this enable dialer functions since it is using an alternate modem file?
Awesome, thanks!
Now who's got a busted Tab to try this on!
Not sure if this is any help, but here's a system dump someone posted....
http://forum.androidcentral.com/galaxy-tab/44323-us-galaxy-tab-sprint-system-dump.html
Dunno. There is no dialer installed and it gives the standard engrish statement "Cannot make or take a call using Galaxy Tab"
I did some comparisons between the sprint tab and the epic, and the modems are identical. I just flashed this and it worked flawlessly.
Thanks again man I appreciate it. You have ressurected my tab.
Wow, maybe I can finally root
infamousjax said:
I did some comparisons between the sprint tab and the epic, and the modems are identical. I just flashed this and it worked flawlessly.
Thanks again man I appreciate it. You have ressurected my tab.
Click to expand...
Click to collapse
Excellent, glad it worked for you.
Nevermind.
I am going to try this now... I had terminal emulator crash on me and it messed up the filesystem or something. My Sprint Galaxy Tablet just says "Samsung" and glows after the intro animation.
I did manage to get the tablet into downloading mode by:
1) turning tablet off
2) holding Volume UP key and power key at the same time until it turns on
and I get little android man with a shovel that says "Downloading... Do not turn off Target!!!"
wish me luck
Why dont you just wipe it and see if that works first?
infamousjax said:
Why dont you just wipe it and see if that works first?
Click to expand...
Click to collapse
how would I do that? It won't actually boot up.. Just shows the samsung into screen and says on a screen that has samsung glowing. It will blink after a while and vibrate, then go back to glowing at me.
HOLY CRAP that worked!!!!! I was just about to give up! Notice the many hours between my last post and now.. (6:50am now LOL)
I had to do some other things not outlined in this thread to get my computer to see the Galaxy Tablet in the Device Manager. Basically I tried these things, (try them all if you have trouble, I'm not sure what or which actually worked):
tried to wipe from boot up (turn off, hold volume up and power until it turns on and release buttons)
that didn't work
install Kies and Samsung(android) SDK and JDK (java developer kit)
that didn't seem to work
install Samsung PC Studio 7
ah hah! I see you there in the device manager now!
power tablet off and get to download menu (hold volume down and power until you see the android holding a shovel at the download menu)
Load up Odin, YAY It connects and detects the COM!!
Select the PIT and TAR, start, it downloads and reboots and tab loaded right up!!
Best of all I think it also got rid of the Sprint Activation nag notice screen. It hasn't popped up yet and it has been a good 10 min or so! That would be a nice bonus
You saved me so much time and $$ thanks a TON!!
((side note, Odin loads up and displays GT-1000 not my SPH-P100... I edited my odin.ini to reflect the correct model. not a big deal at all, but I was getting confused at first as to why Odin was saying wrong model, thinking it was doing a detection when it was really just blindly echoing info from the ini file))
Good stuff.
You'd think Sprint would want to leak the firmware to keep people from exchanging/RMA'ing devices. One thing is certain with Android, people will hack the hell out of it.
My bad on the label. The top title in Odin is just that, a title. It doesn't doesn't affect the reload process at all. I'd change it, but uploading another 200MB file isn't on my list of activities today
ZoinksS2k said:
Good stuff.
You'd think Sprint would want to leak the firmware to keep people from exchanging/RMA'ing devices. One thing is certain with Android, people will hack the hell out of it.
My bad on the label. The top title in Odin is just that, a title. It doesn't doesn't affect the reload process at all. I'd change it, but uploading another 200MB file isn't on my list of activities today
Click to expand...
Click to collapse
I want to add that you might need to update your profile after running this.
What do you mean?
THANK YOU!
Same thing happened to me this morning as ManaKill described...I had terminal emulator crash on me and it messed up the filesystem or something. My Sprint Galaxy Tablet endlessly glowed "Samsung" after the intro animation - thought I was DONE. Tried wiping but no go. I followed ZoinksS2K directions and it worked flawlessly just as infamousjax described. Thank you!!! No telling how many Tabs have been ressurected thanks to this post.
Have you guys been able to get a gps lock since doing this? I can't get one worth ****.
Congratulations & ty...a step in the right direction.i will help once I can make a proper nandroid.
infamousjax said:
Have you guys been able to get a gps lock since doing this? I can't get one worth ****.
Click to expand...
Click to collapse
Nope, no gps either. I didn't notice because I don't use it on my tab.
Sent from my SPH-P100 using XDA App
No. Now what?
Sent from my SPH-P100 using XDA App
I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.
Dantenios said:
I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.
Click to expand...
Click to collapse
You will need to update to the latest bootloader (which is different from modem).
If you're on T-Mobile, you'll want UVDMD5: http://forum.xda-developers.com/showthread.php?t=2282603
If you're on WindMobile (or SGH-T999V), you'll want VLDLL1: http://forum.xda-developers.com/showthread.php?t=1949687 (you'll have to ODIN)
re: error 7 - odin flash
Dantenios said:
I'm not sure if my issue is complex or not. It's just a matter of me not being able to update my phone. Well, my phone was and is still working fine, but after an update, I believe it was CM 10.1 april 20th nightly build, or near that day. I started getting issues with my phone, where it would randomely reboot, and do it much more often when music was playing. That's when i guess i did the stupid thing, I went and downloaded the April 11 Experimental M3 update and updated using that, which worked fine. After that my phone was good as new. And still is right now, not really having any issues. But ofcourse, usually newer nightly builds come with bettered features, so i thought i would update. Here's the problem, when i update, I would get an assert failed and three lines of getprop ("ro.bootloader") T999UVDLJA and the 2 other versions the T999 models, then my model number i believe, followed by Status 7 installation aborted. Any help would be greatly appreciated.
Click to expand...
Click to collapse
This guide will get your phone back up and running properly, doing anything else will just prolong your problem.
Easy and sure way to fix error 7 and other issues or problems - Here is the step by step guide:
After doing this you will end up with a stock-pre-rooted T999 Tmobile Touchwiz 4.1.2 rom which works properly.
You will not loose any of your pictures, videos or music by doing this.
Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5
After downloading make a folder on your computer's desktop and unzip the
file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download and extract Odin into the same folder you made containing the TAR file
Here is the link for Odin: http://d-h.st/Q14
Download ODIN which is required for flashing the stock rooted firmware (a windows app)
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!
to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this.
re: jellybeans
Dantenios said:
to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this.
Click to expand...
Click to collapse
I never said you should be running JB Touchwiz roms, all I was trying to explain is the best and easiest way to get
your phone back up and running whichever way you like it to run.
If you follow the step by step instructions and the phone is working normally then you can re-flash whichever rom
CM10.1 or any others without any issues unless their is something wrong with the rom you are trying to flash.
The main thing is that it's best to start fresh when someone is having issues like you are having with your phone.
Doing anything else besides what I suggested will only prolong all those issues you are having now.
People will be telling you that your cwm or twrp recovery is not the latest one and you need to update it,
other people will tell you that you must have had some error downloading the cm10.1 rom and they will
tell you to re-download it, then others will tell you to check the MD5 checksum of the download and all
kinds of other things which will just prolong the problems you are having.
None of those things I just wrote will help you to fix the error 7 and other issues you are having.
That's why I posted the step by step which works each and every time to fix errors such as yours and
give you or anyone else a clean and fresh start.
Good luck!
*please ignore*
re: you are right
GenericAsianGuy said:
You need to ODIN the latest TouchWiz JB in order to update all the inner-parts of your phone.
I did this yesterday:
ODIN to the latest pre-rooted firmware (DLL1 in my case (SGH-T999V), MD5 for SGH-T999)
Let it boot into TouchWiz
Install Android Terminal Emulator and the latest ClockworkModRecovery
Boot into Recovery
Factory Reset
Install the latest CM 10.1 Nightly
Reboot
Profit (and spend a few hours re-installing and re-configuring everything again).
Click to expand...
Click to collapse
U R so right! I could not have said it better!
---------- Post added 19th May 2013 at 12:00 AM ---------- Previous post was 18th May 2013 at 11:18 PM ----------
Dantenios said:
to Be honest, I'd rather keep using CM 10.1 and not the TouchWiz JB. And what would be the latest bootloader? Apologies, i'm some what new to this.
Click to expand...
Click to collapse
I forgot to mention, since you are kind of new to this you should not even think of or mention anything
about bootloaders if don't want to end up with a shiny brick.
This has happened hundreds of times in these XDA forums when people mess around with bootloaders.
Flashing bootloaders intentionally or by trial and error is the number one way to end up with a bricked phone.
Alright, I understand now, thank you. Just curious, this will probably trip the flash counter right? Or does following that method allow to reset the flash counter? Or is that just something i need to worry about if i'm going to send the phone in for repairs (which i hope I wouldn't need to)
re: flash counter
Dantenios said:
Alright, I understand now, thank you. Just curious, this will probably trip the flash counter right? Or does following that method allow to reset the flash counter? Or is that just something i need to worry about if i'm going to send the phone in for repairs (which i hope I wouldn't need to)
Click to expand...
Click to collapse
The odin flash to stock rooted will trip the flash counter, but then each time you flash any rom trips the flash counter too.
You can get the "Triangle away" app to reset the flash counter at the play store.
Actually there is no need to reset the flash counter at all unless you need to
exchange a defective phone which is still under warranty.
Good luck!
Apologies but one more thing, your post was a link to a pre-rooted JB for T999, My phone is the T999V, if you'd happen to have the pre-rooted version for that would be greatly appreciated.
Dantenios said:
Apologies but one more thing, your post was a link to a pre-rooted JB for T999, My phone is the T999V, if you'd happen to have the pre-rooted version for that would be greatly appreciated.
Click to expand...
Click to collapse
All of these roms are stock pre-rooted roms, I am not certain which one is for your
T999v phone. Perhaps the "V" stands for videotron so select that one.
Mobililicity_VLDLL1
Updated JB Firmware
Mobililicity_VLALH2
Updated ICS Firmware
Wind_VLDLL1
Updated JB Firmware
Wind_VLALH2
Updated ICS Firmware
Videotron_VLDLL1
Updated JB Firmware
Videotron_VLALH2
Updated ICS Firmwar
Misterjunky said:
Mobililicity_VLDLL1
Updated JB Firmware
Wind_VLDLL1
Updated JB Firmware
Videotron_VLDLL1
Updated JB Firmware
Click to expand...
Click to collapse
Great post Misterjunky!
One of these; it depends on what carrier you're with.
I just finished using Odin to the Mobilicity VDLL1 with the pre-rooted JB. Just waiting on my phone to boot up. I have the tab open to install CWM Touch via the terminal emulator. After that I can install the latest CM 10.1 update correct?
re Ok
Dantenios said:
I just finished using Odin to the Mobilicity VDLL1 with the pre-rooted JB. Just waiting on my phone to boot up. I have the tab open to install CWM Touch via the terminal emulator. After that I can install the latest CM 10.1 update correct?
Click to expand...
Click to collapse
Yes, once odin is done and you flash custom recovery the phone will be ready to be flashed any compatible cwm/twrp custom rom zipfile.
You would be much better off if you go to the playstore and download "Goomanager" which is a free app.
After its installed, open it and press the menu key and select "installopenrecoveryscript".
Doing that will flash the latest TWRP recovery.
When Goomanager is done flashing, reboot the phone into recovery mode and go from there.
TWRP has a built-in file manager and terminal, plus an option for ADB sideloading.
It has all the options which CWM has and more.
Give it a try, you can always flash the cwm back if you like.
Sure, though i'm having a new issue now haha My phone has been stuck on the Samsung loading screen ever since after Odin said pass. How long does this usually take, right now for me it's been almost half an hour...And i know i followed the instructions to the T
re: reboot
Dantenios said:
Sure, though i'm having a new issue now haha My phone has been stuck on the Samsung loading screen ever since after Odin said pass. How long does this usually take, right now for me it's been almost half an hour...And i know i followed the instructions to the T
Click to expand...
Click to collapse
reboot the phone into recovery and do a "Factory reset" then restart the phone.
Chances are excellent that it will boot normally if you flashed the correct rom.
Don't wipe anything in recovery.
Good luck!
Thanks a Bunch, It worked! Now to install the recovery, then i may try using Touchwiz JB for a bit, but to be honest, I still think i like CM 10.1 better haha this one feels..some what clunky to me.
Dantenios said:
Thanks a Bunch, It worked! Now to install the recovery, then i may try using Touchwiz JB for a bit, but to be honest, I still think i like CM 10.1 better haha this one feels..some what clunky to me.
Click to expand...
Click to collapse
It would probably be best to edit your title with SOLVED in italics or something so other users are aware and can revert to this thread for assistance rather than starting up a whole new one
Sent from my SGH-T999 using xda premium
Done. I just wanted to ask, I installed the latest CM 10.1 update, and wondering, when i facotry reset it, it didn't take me through the welcome procudure and under my Mobile network options, i didn't see any LTE options, just EvDO and Global and other GSM/WCDMA ones which even after selecting didn't change the one selected by default.
Dantenios said:
Done. I just wanted to ask, I installed the latest CM 10.1 update, and wondering, when i facotry reset it, it didn't take me through the welcome procudure and under my Mobile network options, i didn't see any LTE options, just EvDO and Global and other GSM/WCDMA ones which even after selecting didn't change the one selected by default.
Click to expand...
Click to collapse
If you don't see the Gmail app (and other Google apps) installed, you may need to flash the latest Gapps: http://goo.im/gapps/gapps-jb-20130301-signed.zip
After several hours of trial and error, I found a way that worked for me. It will trip the Knox counter though. Also, what worked for me may not work for everyone else. If you brick your device that's not my fault in any way, so good luck
Using this guide, flash back to the stock TAR (not the UVUAMDL TAR). This restores 4.2.2, which allows access to the menu. However, this alone is not enough, as it won't give you access to the perso functions. Attempting to flash the UVUAMDL TAR will result in an error (at least, it did for me).
Second, extract the modem.bin from the UVUAMDL file, and flashed it to the phone using Odin. It's similar to the guide above, but instead of using PDA, you use phone. This gives you access to the perso functions, as it forces the baseband back to UVUAMDL from UVUEMK2. It may be possible to flash the UVUAMDL.tar modem files found in other threads, I haven't tried this out myself though.
Now, at this point you can follow the instructions in this thread, as every option should now be available. If they're not, make sure your Android version is 4.2.2 and that the baseband is UVUAMDL.
If it works at this point, great, go on to the next step (you may have noticed by now that your sound is not working). If not, use RegionLock Away to fully unlock the phone. At this point, your phone should be fully unlocked and you can see it connected to the network. However, dialing/calling lags significantly, and there is no sound.
The next step is to use Odin to fully restore UVUEMK2, which would restore full functionality. You can download the file from here, and flash using the same steps above. This will restore full sound and phone functionality, while your device remains unlocked. If it gets stuck during the boot animation, you simply need to do a factory wipe from recovery (not sure if this works, haven't tested it myself), or just install your recovery of choice from Odin and install whatever ROM you want to use (what I did, which still required a full factory reset from recovery). Skipping restoring UVUEMK2 and installing your ROM of choice does not work, however. You will still have no sound and the phone function will lag considerably.
If everything goes well, you should have a fully unlocked T-mobile Galaxy S4.
Better guide by kali323:
kali323 said:
1. Download MDB Tar. Extract from 7zip file and then rename the file (remove the .md5) so the filename should be "SGH-M919-UVUAMDB-k0nane.tar"
http://www.hunterspad.com/Domains/S...ir=Xda/Galaxy+S4/T-Mobile+S4/Return+To+stock/
2. Odin the MDB Tar in the PDA slot and once it finish go to recovery and factory reset.
3. It will take forever to reboot and it will be stuck at the boot up screen for awhile with this error "Kernel is not seandroid enforcing set warranty bit: Kernel". In about to 5-10 mins it will boot up.
4. Now youre in MDB 4.2.2 with MK2 modem.
5. Odin the .bin file below. Use the PHONE slot in odin and not PDA. Again it will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"
https://mega.co.nz/#!S9AjUAYA!GOOIp2B4z5dIZy2RFxwQBsMz_v7nRJiOypoAjkuAwtc
6. Now you have MDB Rom with MDL modem
7.Odin CF AutoRoot with the link below in the PDA Slot. It will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"
http://download.chainfire.eu/328/CF-Root/CF-Auto-Root/CF-Auto-Root-jfltetmo-jfltetmo-sghm919.zip
8.Download RegionLock Away 1.3 App either in the thread below or buy it at the google play store to support the developer
http://forum.xda-developers.com/showthread.php?t=2470551
9. Run RegionLock Away and click reboot now. It will take another 5-10 mins to boot up and if you dont ask you for an unlock code with a non tmobile or non tmobile mnvo sim then youre are unlocked.
10. Odin 4.3 or 4.4 and youre done
Click to expand...
Click to collapse
Some additional info:
blu422 said:
This method works the only problem I encountered is while flashing the modem i couldn't make it flash, i would flash it but then in settings my baseband would stay mk2 so the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.
edit: just kidding this method did not work for me, the unlock prompt no longer shows up, but an at&t sim card still will not work, although it does tell me i have five voicemails that i cannot listen to. no texts no calls no data, where it should say at&t in the notification panel it says no service... :/ any ideas? I havent yet updated back to 4.3/4.4 yet could that be the problem?
when I try to call it just says "not registered on network"
turns out that it is just because i havent updated back yet, not even a t-mobile sim works. turns out I have a blacklisted imei! but i think I am unlocked hopefully this (at least the first part) answers a few questions aroused during this process, may be the op could get updated with a couple key peices in this post. also huge kudos for this!
Click to expand...
Click to collapse
hello,
i tried to flash the stock tar as you said, but i get an error.
it says:
write protection: enable
secure magiccode check fail : boot
what can i do in this case?
thank you!
ionutul said:
hello,
i tried to flash the stock tar as you said, but i get an error.
it says:
write protection: enable
secure magiccode check fail : boot
what can i do in this case?
thank you!
Click to expand...
Click to collapse
I'm not too sure actually, I didn't run into that error, and I don't have other S4s I can try it out on.
There were several things I did do before trying to flash back though, that may have had an effect. The first is rooting through motochopper's method. The second was installing and running regionlock away. Try rooting first and then flashing. Otherwise, I might have to chalk it up as something unique with my phone I'm not aware of.
Tsumi said:
After several hours of trial and error, I found a way that worked for me. It will trip the Knox counter though. Also, what worked for me may not work for everyone else. If you brick your device that's not my fault in any way, so good luck
Using this guide, flash back to the stock TAR (not the UVUAMDL TAR). This restores 4.2.2, which allows access to the menu. However, this alone is not enough, as it won't give you access to the perso functions. Attempting to flash the UVUAMDL TAR will result in an error (at least, it did for me).
Second, extract the modem.bin from the UVUAMDL file, and flashed it to the phone using Odin. It's similar to the guide above, but instead of using PDA, you use phone. This gives you access to the perso functions, as it forces the baseband back to UVUAMDL from UVUEMK2. It may be possible to flash the UVUAMDL.tar modem files found in other threads, I haven't tried this out myself though.
Now, at this point you can follow the instructions in this thread, as every option should now be available. If they're not, make sure your Android version is 4.2.2 and that the baseband is UVUAMDL.
If it works at this point, great, go on to the next step (you may have noticed by now that your sound is not working). If not, use RegionLock Away to fully unlock the phone. At this point, your phone should be fully unlocked and you can see it connected to the network. However, dialing/calling lags significantly, and there is no sound.
The next step is to use Odin to fully restore UVUEMK2, which would restore full functionality. You can download the file from here, and flash using the same steps above. This will restore full sound and phone functionality, while your device remains unlocked. If it gets stuck during the boot animation, you simply need to do a factory wipe from recovery (not sure if this works, haven't tested it myself), or just install your recovery of choice from Odin and install whatever ROM you want to use (what I did, which still required a full factory reset from recovery). Skipping restoring UVUEMK2 and installing your ROM of choice does not work, however. You will still have no sound and the phone function will lag considerably.
If everything goes well, you should have a fully unlocked T-mobile Galaxy S4.
Click to expand...
Click to collapse
HELP...!
Ok, I've been reading many many articles for the past few days and finally have mustered enough energy to attempt the unlock my T-Mobile SGH-M919 running MK2 firmware. Since I was unable to get into the service menu and input keys using the many directions on this site.... I attempt to flash to old older firmware, following this guide.
I followed each direction 1 step at and time and followed it to the "T". Anyway, long story short... I tried and it soft bricked my phone. I get the warning screen that the firmware was unsuccessful and that I need to run recovery using Samsung Kies. I download the software and attempt recovery. It got to roughly 90% and then it failed too. I reverted back to Odin and reflash using MK2. It too got to about 90% and fails. What is going on?
Any more tips to get this thing working again?? Help.
Got to only 93% via Kies... two times!
Um I'm almost sure once you are on mk2 your not able to go back to mdl. Do to the boot loader...
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 08:52 PM ---------- Previous post was at 08:51 PM ----------
If your rooted you can try region Loa away by chain fire see if it works.
Sent from my SGH-M919 using xda app-developers app
egren58 said:
Um I'm almost sure once you are on mk2 your not able to go back to mdl. Do to the boot loader...
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 08:52 PM ---------- Previous post was at 08:51 PM ----------
If your rooted you can try region Loa away by chain fire see if it works.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
wwwhheeew.... finally got it to unbrick. Took 4 hours to get this thing operational again. I thought the guide specifically says it can downgrade from MK2 to MDL? I already ran the Regionlock app and it appears to be done right, but it's still not sim unlocked.!
dyangster said:
wwwhheeew.... finally got it to unbrick. Took 4 hours to get this thing operational again. I thought the guide specifically says it can downgrade from MK2 to MDL? I already ran the Regionlock app and it appears to be done right, but it's still not sim unlocked.!
Click to expand...
Click to collapse
same problem, RLA does not work on MK2, flashing MDL modem and going through the motions also does NOT sim unlock...cant seem to get this thing working.
funny thing is it wont even register on the network with a GoSmart sim, GoSmart being a TMO MVNO.
i hate sammy...
I flashed to the stock firmware first, which I believe is the MDB firmware. It doesn't work attempting to go to MDL. Going to MDB gets you 4.2.2, but you would still be locked because it keeps the MK2 modem.
The second step was to extract the MDL modem.bin from the TAR, and then flash that on Odin via the phone method. That was how I was able to downgrade the modem from MK2 to MDL, but that screws up sound, but allows you access to the unlock functions.
Odin MDB and factrory reset in recovery. I was stuck at "Kernel is not seandroid enforcing set warranty bit: Kernel" at the boot up screen. I thought it didnt work and wasnt going to boot up and was looking MK2 tar and then out of nowhere after 5 mins I hear the tmobile boot up sound and this **** actually boot it. Im in MDB 4.2.2 with mk2 baseband. Just need to downgrade baseband and Ill let you know if it works guys. Ill post all files as well that I use
---------- Post added at 10:34 PM ---------- Previous post was at 10:07 PM ----------
I have successfully unlocked and I was at 4.3. Huge props to Tsumi. Ill post an updated guide of Tsumi unlocked method of all the files I used
---------- Post added at 10:58 PM ---------- Previous post was at 10:34 PM ----------
How to Unlocked M919 on MK2 4.3. This method has no been tested on the new MB4 4.4.2 update
Huge Props to Tsumi. Is his method and thank/donate to him. i use his guide but it wasnt clear enough so I went searching to internet for links for all the correct files.
Im not responsible for any bricks but if you follow carefully then you shouldn't
This method will trip KNOX
1. Download MDB Tar. Extract from 7zip file and then rename the file (remove the .md5) so the filename should be "SGH-M919-UVUAMDB-k0nane.tar"
http://www.hunterspad.com/Domains/S...ir=Xda/Galaxy+S4/T-Mobile+S4/Return+To+stock/
2. Odin the MDB Tar in the PDA slot and once it finish go to recovery and factory reset.
3. It will take forever to reboot and it will be stuck at the boot up screen for awhile with this error "Kernel is not seandroid enforcing set warranty bit: Kernel". In about to 5-10 mins it will boot up.
4. Now youre in MDB 4.2.2 with MK2 modem.
5. Odin the .bin file below. Use the PHONE slot in odin and not PDA. Again it will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"
https://mega.co.nz/#!S9AjUAYA!GOOIp2B4z5dIZy2RFxwQBsMz_v7nRJiOypoAjkuAwtc
6. Now you have MDB Rom with MDL modem
7.Odin CF AutoRoot with the link below in the PDA Slot. It will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"
http://download.chainfire.eu/328/CF-Root/CF-Auto-Root/CF-Auto-Root-jfltetmo-jfltetmo-sghm919.zip
8.Download RegionLock Away 1.3 App either in the thread below or buy it at the google play store to support the developer
http://forum.xda-developers.com/showthread.php?t=2470551
9. Run RegionLock Away and click reboot now. It will take another 5-10 mins to boot up and if you dont ask you for an unlock code with a non tmobile or non tmobile mnvo sim then youre are unlocked.
10. Odin 4.3 or 4.4 and youre done
ionutul said:
hello,
i tried to flash the stock tar as you said, but i get an error.
it says:
write protection: enable
secure magiccode check fail : boot
what can i do in this case?
thank you!
Click to expand...
Click to collapse
I'm curious, how come you didn't trip the Knox counter?
Help
Hey I Have A Tmobile Galaxy s4 and it says my sim isn't registered on the network i was just wondering if there was anyway to get this running, i tried the above method and it completed but i still can't use a tmobile sim on my phone.
JerkLife said:
Hey I Have A Tmobile Galaxy s4 and it says my sim isn't registered on the network i was just wondering if there was anyway to get this running, i tried the above method and it completed but i still can't use a tmobile sim on my phone.
Click to expand...
Click to collapse
If you have a T-mobile S4 and a T-mobile sim, and it says sim is not valid, then you need to contact T-mobile about your sim card. Either that, or your phone has a bad IMEI (not sure what error message would pop up if you have a bad IMEI). Either way, it's not an unlocking problem. Either your sim or your phone is invalid on the T-mobile network.
This method works the only problem I encountered is while flashing the modem i couldn't make it flash, i would flash it but then in settings my baseband would stay mk2 so the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.
edit: just kidding this method did not work for me, the unlock prompt no longer shows up, but an at&t sim card still will not work, although it does tell me i have five voicemails that i cannot listen to. no texts no calls no data, where it should say at&t in the notification panel it says no service... :/ any ideas? I havent yet updated back to 4.3/4.4 yet could that be the problem?
when I try to call it just says "not registered on network"
turns out that it is just because i havent updated back yet, not even a t-mobile sim works. turns out I have a blacklisted imei! but i think I am unlocked hopefully this (at least the first part) answers a few questions aroused during this process, may be the op could get updated with a couple key peices in this post. also huge kudos for this!
blu422 said:
This method works the only problem I encountered is while flashing the modem i couldn't make it flash, i would flash it but then in settings my baseband would stay mk2 so the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.
edit: just kidding this method did not work for me, the unlock prompt no longer shows up, but an at&t sim card still will not work, although it does tell me i have five voicemails that i cannot listen to. no texts no calls no data, where it should say at&t in the notification panel it says no service... :/ any ideas? I havent yet updated back to 4.3/4.4 yet could that be the problem?
when I try to call it just says "not registered on network"
turns out that it is just because i havent updated back yet, not even a t-mobile sim works. turns out I have a blacklisted imei! but i think I am unlocked hopefully this (at least the first part) answers a few questions aroused during this process, may be the op could get updated with a couple key peices in this post. also huge kudos for this!
Click to expand...
Click to collapse
As I have only done this on one phone, I am not sure what issues you were encountering. Also, like I said in my post, YMMV, different phones may behave differently.
What do you want to see updated?
wrong
the 2nd link is not a link to the files. it's a link to internet browsers..
BoloVon said:
the 2nd link is not a link to the files. it's a link to internet browsers..
Click to expand...
Click to collapse
All links are working for me...
Tsumi said:
As I have only done this on one phone, I am not sure what issues you were encountering. Also, like I said in my post, YMMV, different phones may behave differently.
What do you want to see updated?
Click to expand...
Click to collapse
That message pops up when its blacklisted so it won't work regardless if you unlock it
Sent from my SGH-M919 using Tapatalk
No wifi
i was able to flash stock tar to my s4. now i cannot get wifi to work.. i tried turning it on but the signal comes back off.
help please..
Tsumi said:
What do you want to see updated?
Click to expand...
Click to collapse
That \/ maybe just add a link to my post saying if you have problems with the .bin part then see here or not its whatever you see fit
blu422 said:
the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.
Click to expand...
Click to collapse
---------- Post added at 10:17 PM ---------- Previous post was at 09:52 PM ----------
BoloVon said:
i was able to flash stock tar to my s4. now i cannot get wifi to work.. i tried turning it on but the signal comes back off.
help please..
Click to expand...
Click to collapse
Which stock are you referring to? The 4.4.2 one?
I present the latest stock ODIN firmware directly from Samsung. The current latest is G925TUVU1AOCG. These are for the T-Mobile Galaxy s6 Edge (SM-G925T) ONLY! DO NOT flash this on any other device.
Instructions:
1.) Make sure you have ODIN 3.10 setup (there are many tutorials on xda and youtube for this).
2.) Download the latest firmware zip from below.
3.) Extract the tar.md5 file from the zip.
4.) Add the tar.md5 file to the AP section of ODIN.
5.) Under Options make sure to ONLY select "Auto Reboot" and "F. Reset Time". DO NOT select repartition (or really anything else)!!!
6.) Click start and let it flash.
(Again there are plenty of tutorials on how to use ODIN)
This won't wipe your data (probably). (It didn't during my test but always make backups just in case.)
Downloads:
G925TUVU1AOCG SHA256 (of zip): 70146cbcf5fe157ca1691085db15e8ffaa7cbdeaa16a6043567a1c5796a6cb93
Flashing anything is dangerous and I am not responsible for anything you do to any of your devices!
jamcar said:
I present the latest stock ODIN firmware directly from Samsung. The current latest is G925TUVU1AOCG. These are for the T-Mobile Galaxy s6 Edge (SM-G925T) ONLY! DO NOT flash this on any other device.
Instructions:
1.) Make sure you have ODIN 3.10 setup (there are many tutorials on xda and youtube for this).
2.) Download the latest firmware zip from below.
3.) Extract the tar.md5 file from the zip.
4.) Add the tar.md5 file to the AP section of ODIN.
5.) Under Options make sure to ONLY select "Auto Reboot" and "F. Reset Time". DO NOT select repartition (or really anything else)!!!
6.) Click start and let it flash.
(Again there are plenty of tutorials on how to use ODIN)
This won't wipe your data (probably). (It didn't during my test but always make backups just in case.)
Downloads:
G925TUVU1AOCG SHA256 (of zip): 70146cbcf5fe157ca1691085db15e8ffaa7cbdeaa16a6043567a1c5796a6cb93
Flashing anything is dangerous and I am not responsible for anything you do to any of your devices!
Click to expand...
Click to collapse
Thanks been looking for this
Ahahahahahahaha! I believe roms can be crafted!
jamcar said:
I present the latest stock ODIN firmware directly from Samsung. The current latest is G925TUVU1AOCG. These are for the T-Mobile Galaxy s6 Edge (SM-G925T) ONLY! DO NOT flash this on any other device.
Instructions:
1.) Make sure you have ODIN 3.10 setup (there are many tutorials on xda and youtube for this).
2.) Download the latest firmware zip from below.
3.) Extract the tar.md5 file from the zip.
4.) Add the tar.md5 file to the AP section of ODIN.
5.) Under Options make sure to ONLY select "Auto Reboot" and "F. Reset Time". DO NOT select repartition (or really anything else)!!!
6.) Click start and let it flash.
(Again there are plenty of tutorials on how to use ODIN)
This won't wipe your data (probably). (It didn't during my test but always make backups just in case.)
Downloads:
G925TUVU1AOCG SHA256 (of zip): 70146cbcf5fe157ca1691085db15e8ffaa7cbdeaa16a6043567a1c5796a6cb93
Flashing anything is dangerous and I am not responsible for anything you do to any of your devices!
Click to expand...
Click to collapse
Appreciate the first downloadable tar. Maybe a better place would be in the Android Development section. Just a thought. (Or original android development. ) Not sure which would be more appropriate but I'm sure a lot more users would see this. Just my 2c. Thanks for the post.
Docmjldds said:
Appreciate the first downloadable tar. Maybe a better place would be in the Android Development section. Just a thought. (Or original android development. ) Not sure which would be more appropriate but I'm sure a lot more users would see this. Just my 2c. Thanks for the post.
Click to expand...
Click to collapse
Unmodified stock ROMs do not belong in the android development section so general seemed like the better choice. Any mod, please correct me and move this thread if I am wrong.
Always seem to remember them being in general or Q and A.
Word
THANK YOU for upload to MEGA. I'm getting really sick of the rapidgator spam.
Just when I think I'm getting well versed in rooting, etc. I ask a question like this:
What is the reason to install the stock firmware? I'm rooted with stock recovery flashed.
Thanks!
ShermCraig said:
Just when I think I'm getting well versed in rooting, etc. I ask a question like this:
What is the reason to install the stock firmware? I'm rooted with stock recovery flashed.
Thanks!
Click to expand...
Click to collapse
Lets says the rooting process borked your phone (or maybe you installed some experimental ROM/kernel, etc.). You can still get into download mode but can't get anything else to work right. Flash back to stock and start again.
See how it's useful?
Yep that helps! So, aside from that, if I am up and running - albeit very slowly and with significant battery drain - is there any reason for me to flash this firmware?
jamcar said:
Lets says the rooting process borked your phone (or maybe you installed some experimental ROM/kernel, etc.). You can still get into download mode but can't get anything else to work right. Flash back to stock and start again.
See how it's useful?
Click to expand...
Click to collapse
ShermCraig said:
Yep that helps! So, aside from that, if I am up and running - albeit very slowly and with significant battery drain - is there any reason for me to flash this firmware?
Click to expand...
Click to collapse
Those TWO reasons are exactly why you should try this. MANY, including myself have had the battery drain, lag, and overheating Cured by flashing the stock ROM Firmware.
SuperSport said:
Those TWO reasons are exactly why you should try this. MANY, including myself have had the battery drain, lag, and overheating cured by flashing the stock ROM.
Click to expand...
Click to collapse
@SuperSport - you said you flashed the stock ROM - @jamcar is talking about flashing the firmware. Two completely different things. Can someone clarify? FWIW, I did flash the stock ROM a few days ago, but after reinstalling everything, I'm back to being laggy and battery drain.
Thanks all!!
ShermCraig said:
@SuperSport - you said you flashed the stock ROM - @jamcar is talking about flashing the firmware. Two completely different things. Can someone clarify? FWIW, I did flash the stock ROM a few days ago, but after reinstalling everything, I'm back to being laggy and battery drain.
Thanks all!!
Click to expand...
Click to collapse
Yes, I said that wrong. I meant Firmware. There are many reports that the issues go away after flashing the Stock Firmware back on. I was using Smart Switch to do it, but Odin is a great alternative if Smart Switch does not work for you. I'm not sure why your issues returned, maybe the Root is bringing it back, or maybe an incompatible app. I've found a few apps that Force Close on me that never used to on my Galaxy S4 (ie: 'dji-vision' app for the Phantom Drone), so it is possible other apps are drawing too much power, etc...
Okay, that makes sense. I have been having Amazon FC's since rooting. Frustrating but not as bad as it was at its worst. Using Clean Master for the lag issues and Greenify for the battery. Not sure if they counter each other though. Anyway, I will try flashing the Firmware and report back. Thank you again for clarifying.
SuperSport said:
Yes, I said that wrong. I meant Firmware. There are many reports that the issues go away after flashing the Stock Firmware back on. I was using Smart Switch to do it, but Odin is a great alternative if Smart Switch does not work for you. I'm not sure why your issues returned, maybe the Root is bringing it back, or maybe an incompatible app. I've found a few apps that Force Close on me that never used to on my Galaxy S4 (ie: 'dji-vision' app for the Phantom Drone), so it is possible other apps are drawing too much power, etc...
Click to expand...
Click to collapse
SuperSport said:
Yes, I said that wrong. I meant Firmware. There are many reports that the issues go away after flashing the Stock Firmware back on. I was using Smart Switch to do it, but Odin is a great alternative if Smart Switch does not work for you. I'm not sure why your issues returned, maybe the Root is bringing it back, or maybe an incompatible app. I've found a few apps that Force Close on me that never used to on my Galaxy S4 (ie: 'dji-vision' app for the Phantom Drone), so it is possible other apps are drawing too much power, etc...
Click to expand...
Click to collapse
@SuperSport correct me if I'm wrong but aren't there two reasons for @ShermCraig issues? First would be the outdated build and second would be the recovery deep sleep issue if they're rooted.
jamcar said:
@SuperSport correct me if I'm wrong but aren't there two reasons for @ShermCraig issues? First would be the outdated build and second would be the recovery deep sleep issue if they're rooted.
Click to expand...
Click to collapse
Yes, and Yes. But I have heard some report that they Rooted after flashing the Firmware that has the OCG update included and they did not have the deep sleep issue anymore. Although, I believe they replaced the recovery with the original again. I myself have not rooted, so I'm not speaking from experience, just what I've been reading.
SuperSport said:
Yes, and Yes. But I have heard some report that they Rooted after flashing the Firmware that has the OCG update included and they did not have the deep sleep issue anymore. Although, I believe they replaced the recovery with the original again. I myself have not rooted, so I'm not speaking from experience, just what I've been reading.
Click to expand...
Click to collapse
So, I cannot access Mega from my office - can anyone possibly put it in either dropbox or drive? DISREGARD - I am getting it by tethering off of my shiny S6 Edge!
ShermCraig said:
So, I cannot access Mega from my office - can anyone possibly put it in either dropbox or drive? DISREGARD - I am getting it by tethering off of my shiny S6 Edge!
Click to expand...
Click to collapse
I've now rooted, and flashed the Stock Recovery back to my phone. Deep Sleep is working fine. I'll monitor it over the next few days to see what the battery life is like.
Here is the Stock Recovery for T-Mobile Edge SM-G925T.
https://drive.google.com/file/d/0B3nX3DCjdq6MWS00NHFqRVhOVlk/view?usp=sharing
jamcar said:
Lets says the rooting process borked your phone (or maybe you installed some experimental ROM/kernel, etc.). You can still get into download mode but can't get anything else to work right. Flash back to stock and start again.
See how it's useful?
Click to expand...
Click to collapse
This is exactly the the situation that I am in. I am glad OP posted the stock firmware.
Does anybody know why my phone gets stuck in a boot loop when I try to root. I used the S6 version as was suggested in the root tutorial, everything goes smoothly but then it just bootloops.
Where are the roms at guys I'm trying to build one as soon as I finish fixing my pc
I'm really hoping someone can bail me out here before I...
I have made a mess of my new (to me) Note 4. I bought it as an Unlocked GSM. It arrived booting with a Sprint screen. I have Safelink BYOP service. When I switched from my Note2 to Note4, yesterday, an ATnT sim card was used to activate it with Tracfone. Everything seemed to work EXCEPT for MMS - I could not send nor receive pictures. I read -what I thought was- clear instructions here on the forum, I started downloading and attempting to root my phone, hoping that would solve the problem, since tech support had no answers.
I followed the instructions in this post - https://forum.xda-developers.com/note-4-sprint/help/rooting-sprint-note-4-pj1-t3495306 . Now the phone will only boot to download mode, or I can use the up volume button to get to the program to install, restore, etc. I have tried several times - with a couple of different .tar files. This last attempt - I tried to restore it - that also failed. My old eyes can not really see the tiny text but I did see in Odin3 that 1) No MDS found 2) Systemless mode Boot img support required 3) Boot Image Patcher Failed. When I attempt to install the SuperSU, from the thread, it gives me similar errors 1) NO MDS file found 2) (under Boot Image patcher it says FAILURE / Abort after extracting Ramdisk.
If anyone could help me out, I would be most grateful.
JadenEllis said:
I'm really hoping someone can bail me out here before I...
Click to expand...
Click to collapse
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Once you get phone back on stock. I'll show how to root!
Thank You
Thank you so much for the reply. I have downloaded the files you put in my post. I will attempt to do these things now, but I have a question. I stayed up fighting with the phone all night. I probably did some things I shouldn't have? I realized that I was getting stupid and quit, but I did (maybe) put some other stuff on the phone that night. Should I use the Clean or wipe function in TWRP before I do anything else???
Yes, I can boot to downloader or to TWRP. The phone (on its own) is now stuck trying to load with the Note 4 splash screen - but I can boot to either with the vol +/- buttons.
SamFirm did not work. It said Unable to fetch... please check data or enter manually.
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
First - THANK YOU all for the assistance.
Yesterday, none of the suggestions were working, but I kept at it. I was finally able to install the most current Stock tar that I could find. This phone had updated to the most current version available for the phone - it had Marshmallow 6.01. NOW, the red and yellow tamper errors appear to be gone from the Note4 splash screen - BUT, it boots to Sprint Activation so it won't fully load to OS. I read a post about removing the Sprint Hands Free Activation, but it gives two ways of doing so. 1 requires having a rooted phone (I am assuming it is not rooted now?) and the other uses ADN Connect, and I am not sure what that is.
I'm not really sure what to do from here? Any assistance appreciated. Can I start from step 1 of the original post to install SuperSU now?
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
Well, the sun is about to come up - again - but I think I got it! This has been a learning experience to say the least. I wasn't really planning a crash course in Android, but thank you to all who responded. And to :Samep too!
I think I get it
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.
JadenEllis said:
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.
Click to expand...
Click to collapse
Sorry bud. I'm so busy. Haven't been online since i message you. Glad you got it.
Rookie messed up..
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.
meBn360 said:
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.
Click to expand...
Click to collapse
Sorry I don't get on here much lately. Just seen your post.
Without knowing exactly what you did. I'd say you lost your unlock. If you had an unlocked sprint phone. And tried nougat. I believe i remember that upgrading to nougat was messing up people's EFS partition. And that's where the unlock happens. Did you make a backup?
I always tell everyone, the most important thing you can do is have a full working backup of every partition.
Hope that sheds some light