Related
I created a spot on my website for the stock Odin Tar's that I use for the P600.
I posted the US / XAR Region Stock Odin. I also posted the ML1 Asian base I used as well.
As I gather newer ones I will put them up and updated this thread.
Although this guide is written for the p600 it would, in theory work on any P60x device so long as you have the proper Odin files!
Note: This will not "untrip knox"!!!!!!!!
Here is the download page on my site:
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Enjoy!
Currently Hosted:
P600UEUBMK1_P600XARBMK1_XAR (Shipped US ROM / XAR Region)
P600ZTUBML1_P600ZZTBML1_BRI (Asian Based ROM / BRI Region)
Other Odin Tar resources: Sammobile. Must be a member but they have tons of them.
How to Return to stock
This mini guide assumes the following...
You were able to root and or install a custom recovery or ROM therefore the drivers are installed on your PC for the tablet. So here we go...
Download Odin from the links in the OP
Extract the the .md5 file from the zip file you downloaded above.
Boot tablet into "Download" mode. You can do this by holding Power and Volume - (down) when the device is shut off. I note on this device it can be a little trickier so you may have to try a couple times. You should now see this on your tablet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Connect Tablet to PC using known good USB Cable
Start Odin and Press the "AP" button to load the tar.md5 file. This may take a minute as it is also calculating the MD5 to ensure you have a good file. A bad file means bad issues and it wont let you flash it (good fail safe).
Once Odin sees the Tar and loads it completely AND Odin sees the tablet press the Start button to begin. Can takes about 5 to 10 minutes so be patient. Do NOT check or uncheck mark ANY other Options in Odin unless you know what you are doing!
Once it complete you will have a factory image on your tablet. Yay!
But we are not done. You may also want to, at this point, reboot to recovery and do a full data wipe. This method of Odin leaves the SD card and user data intact. To get into recovery hold Power and Volume + until you see the stock Android recovery. Select format Data, reboot. Boom, your tablet is like brand new!
Guided added!
I am not the best technical writer so if you need help understanding what I am saying dont hesitate to ask!
Bumped so people can find this...
Mods moved it so no one looking will actually see it...
scrosler said:
Bumped so people can find this...
Mods moved it so no one looking will actually see it...
Click to expand...
Click to collapse
I'm glad you bumped it. I still haven't tried to install any custom ROM in this tablet, but this post will sure come in handy soon!
Vexelius said:
I'm glad you bumped it. I still haven't tried to install any custom ROM in this tablet, but this post will sure come in handy soon!
Click to expand...
Click to collapse
Indeed!
What happens if I failed to root (according to TWRP) and am stuck in the Samsung splash screen? I was obviously able to install TWRP so hopefully that is enough for Odin to get me back to stock
Will this work?
kaneelias said:
What happens if I failed to root (according to TWRP) and am stuck in the Samsung splash screen? I was obviously able to install TWRP so hopefully that is enough for Odin to get me back to stock
Will this work?
Click to expand...
Click to collapse
If you can see samsung screen you can odin back to stock.
The directions I posted should hold true about getting to Odin / Download Mode
Thanks for this guide, I agree, it should definitely be in the development section.
Hello
So will I get the OTA updates after this? How do I untrip knox?
thanks
Thanks for this Scott and a great ROM!!!!
Sent from my SAMSUNG-SGH-I317 using Tapatalk
tahrang said:
Hello
So will I get the OTA updates after this? How do I untrip knox?
thanks
Click to expand...
Click to collapse
Yes, this is returning you to stock like when you turned it on for the very first time.
No one knows how to untrip knox.
Is it Knox that blocks the ota updates, or is it the rooting itself?
starfall42 said:
Is it Knox that blocks the ota updates, or is it the rooting itself?
Click to expand...
Click to collapse
Not sure. Never tried to Ota with KNOX.
Maybe ask in the Q/A forums.
Just to be safe, and If I do this the tablet will be as if it was completely new, right? I'm going to exchange it for another one and I want to be sure it's as new. Are there any flash counters or stuff like that I should be worried about?
Sent from my Nexus 5
So when a system update comes out we could use these directions to flash the stock rom with out loosing data, apps, settings, etc? Then be able to get the stock OTA?
Coming from the Nexus world, This is a bit different. Google seems to have no interest in the 10 inch sector though, so here we are.
Never have we had a tablet so heavily defended with so many issues. 6 tablets and this one stands out.
Via my Note 3
Tripping out?
scrosler said:
Note: This will not "untrip knox"!!!!!!!!
Click to expand...
Click to collapse
I think I understand what you are saying, but I'm new to Android, and would appreciate a sanity check::cyclops:
1. Knox "trips" (i.e. opens a fusible link in the hardware) if you root the tab and (or?) boot with a non-factory ROM. Once it trips, it cannot ever be "untripped", even if you return to a factory ROM image. (Hence the emphatic statement in the quote.)
2. Question: If a tablet is currently, and has always been, unrooted and stock, will using Odin and these instructions with a factory ROM trip knox? For example, to upgrade to the factory KitKat image
3. Follow-up question: If I flash KitKat as above, can I return to the original release by following your guide, again without tripping knox?
Thanks for the guide and software, and for your help.
iTelegraph said:
I think I understand what you are saying, but I'm new to Android, and would appreciate a sanity check::cyclops:
1. Knox "trips" (i.e. opens a fusible link in the hardware) if you root the tab and (or?) boot with a non-factory ROM. Once it trips, it cannot ever be "untripped", even if you return to a factory ROM image. (Hence the emphatic statement in the quote.)
2. Question: If a tablet is currently, and has always been, unrooted and stock, will using Odin and these instructions with a factory ROM trip knox? For example, to upgrade to the factory KitKat image
3. Follow-up question: If I flash KitKat as above, can I return to the original release by following your guide, again without tripping knox?
Thanks for the guide and software, and for your help.
Click to expand...
Click to collapse
1. As far as anyone knows, Knox cannot be untripped.
2. If you Odin a FACTORY IMAGE it WILL NOT trip Knox. Only custom roms/rooting trips AFAIK.
3. I'm not 100% sure as I haven't tried, but I think I've seen discussions where the bootloader wasn't changed so you could go back. Again, I'm not 100% sure. Maybe we could get clarification from someone who tried.
Sent from my SM-P600 using Tapatalk
It all started with the plan to root the device Samsung Galaxy Note 3
I had rooted the device using Kingo Android root. This had gone successfully. Then I tried to install some apps which needs root access. I tried an app called EFS, I though I would back up EFS and NV_ *, When I clicked on backup NV_* (cant remember the whole name), thats when the problem started. It had been 2 days since I had been trying different things to recover the device.
I went into recovery mode and tried
Clear cache
Then Back up my data and did factory reset
Between boot loops I had the opportunity to uninstalled the EFS app
Then installed twrp and tried this blog http://forum.xda-developers.com/showthread.php?t=2471421
eventually, I thought of letting go of my data, so did the format of data
used ODIN to and flashed this ROM from this blog http://forum.xda-developers.com/showthread.php?t=2540822
Despite all these steps I cannot get it working.
Current phone behaviour
The phone keeps booting again, once the UI of the phone starts, I get a window of 1 min before the phone restarts again. I get a message saying "Process system isn't responding"
I am willing to try anything to get the device functional, if it means to build it from scratch. This is my first time venturing into this side of the world, I would be thankful if you can guide me with the steps to perform a build from scratch, or direct me to a blog where I can do this?
eagle909 said:
It all started with the plan to root the device Samsung Galaxy Note 3
I had rooted the device using Kingo Android root. This had gone successfully. Then I tried to install some apps which needs root access. I tried an app called EFS, I though I would back up EFS and NV_ *, When I clicked on backup NV_* (cant remember the whole name), thats when the problem started. It had been 2 days since I had been trying different things to recover the device.
I went into recovery mode and tried
Clear cache
Then Back up my data and did factory reset
Between boot loops I had the opportunity to uninstalled the EFS app
Then installed twrp and tried this blog http://forum.xda-developers.com/showthread.php?t=2471421
eventually, I thought of letting go of my data, so did the format of data
used ODIN to and flashed this ROM from this blog http://forum.xda-developers.com/showthread.php?t=2540822
Despite all these steps I cannot get it working.
Current phone behaviour
The phone keeps booting again, once the UI of the phone starts, I get a window of 1 min before the phone restarts again. I get a message saying "Process system isn't responding"
I am willing to try anything to get the device functional, if it means to build it from scratch. This is my first time venturing into this side of the world, I would be thankful if you can guide me with the steps to perform a build from scratch, or direct me to a blog where I can do this?
Click to expand...
Click to collapse
Flash THIS it'll fix your EFS issues and your bootloop -
Grab CWM/TWRP and flash via Odin
Run that zip from custom recovery
Job done
Stay away from EFS back up apps, they're notoriously unreliable and can brick your device
radicalisto said:
Flash THIS it'll fix your EFS issues and your bootloop -
Grab CWM/TWRP and flash via Odin
Run that zip from custom recovery
Job done
Stay away from EFS back up apps, they're notoriously unreliable and can brick your device
Click to expand...
Click to collapse
Sounds like a dumb question but How to I upload this zip file to my phone. Note3 does not come with external SD slot and I am not able to connect the phone through PC either by Kies or ADT, none of them are recognising?
Can I upload this zip file through ODIN? it only accepts .tar or .md5 files?
Any tips?
eagle909 said:
Sounds like a dumb question but How to I upload this zip file to my phone. Note3 does not come with external SD slot and I am not able to connect the phone through PC either by Kies or ADT, none of them are recognising?
Can I upload this zip file through ODIN? it only accepts .tar or .md5 files?
Any tips?
Click to expand...
Click to collapse
Ahh, you will need to find an ext SD card, then you'll have to transfer it across via your PC then insert into phone, boot into Recovery and flash it.
Not flashable via Odin atm I'm afraid
eagle909 said:
Sounds like a dumb question but How to I upload this zip file to my phone. Note3 does not come with external SD slot and I am not able to connect the phone through PC either by Kies or ADT, none of them are recognising?
Can I upload this zip file through ODIN? it only accepts .tar or .md5 files?
Any tips?
Click to expand...
Click to collapse
Yes it does comes with an ext SD card slot... Beside ur sim card slot. Put that file into it then put into ur phone. Boot into custom recovery and flash it.
Sent from my proudly temaseked +Yankied note 3.
Yeah SD Card slot is above the sim card slot, -- I read it wrong, thought you said -- "it doesn't come with an EXT SD Card"
radicalisto said:
Flash THIS it'll fix your EFS issues and your bootloop -
Grab CWM/TWRP and flash via Odin
Run that zip from custom recovery
Job done
Stay away from EFS back up apps, they're notoriously unreliable and can brick your device
Click to expand...
Click to collapse
radicalisto said:
Yeah SD Card slot is above the sim card slot, -- I read it wrong, thought you said -- "it doesn't come with an EXT SD Card"
Click to expand...
Click to collapse
I never knew there was a slot of SD card, else I would have backed up my data thanks!
But this solution didnt work for me. After the install of this script through twrp the phone behavior is unchanged.
Try flashing the stock rom for your phone. Then you can go back and root again....
99% of the time this will fix things...
eagle909 said:
I never knew there was a slot of SD card, else I would have backed up my data thanks!
But this solution didnt work for me. After the install of this script through twrp the phone behavior is unchanged.
Click to expand...
Click to collapse
The screenshot of the install. I suspect if there is something wrong with the install?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
eagle909 said:
The screenshot of the install. I suspect if there is something wrong with the install?
sorry too big of the picture
Click to expand...
Click to collapse
ultramag69 said:
Try flashing the stock rom for your phone. Then you can go back and root again....
99% of the time this will fix things...
Click to expand...
Click to collapse
downloading this Rooted Stock ROMs for Note 3 SM-N9005
http://galaxynote3root.com/rooted-stock-roms/
That screenshot looks OK to me. The Mount error is standard in TWRP. Reboot your device and see.. or as posted re flash stock as it pretty much fixes everything
Sent from my SM-N9005 using XDA Premium 4 mobile app
eagle909 said:
downloading this Rooted Stock ROMs for Note 3 SM-N9005
http://galaxynote3root.com/rooted-stock-roms/
Click to expand...
Click to collapse
I have just flashed this ROM and reran the fix, but with out any luck?
The phone keeps rebooting
eagle909 said:
I have just flashed this ROM and reran the fix, but with out any luck?
The phone keeps rebooting
Click to expand...
Click to collapse
You haven't flashed a stock rom... That is rooted and so is no longer a stock rom. Go to Sammobile.com to get a pure stock rom...
Just a note for you, whether it says stock is solely reliant on it being NOT tampered with. Rooting a stock rom no longer makes it stock, it is just a description that means no tweaks were applied or bloatware removed...
Remember that the bootloader must match the stock rom. If you are trying to flash a lower version rom onto an MJ3 or higher bootloader you will get bootloops.
The same applies if you have updated to Kitkat rom.
If you haven't updated to 4.4.2, then you should check this[first post]
http://forum.xda-developers.com/showthread.php?t=2540822
But this will trip your Knox counter
Sent from my SM-N9005 using Tapatalk
I checkout this post and did exactly as described. but the phone rebooting doesnot stop. Also when the phone is turned on I am not able to open Phone option and under settings I am not able to launch status option under about device? Could my EFS is lost/corrupted?
Dahdoul said:
If you haven't updated to 4.4.2, then you should check this[first post]
http://forum.xda-developers.com/showthread.php?t=2540822
But this will trip your Knox counter
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
eagle909 said:
I checkout this post and did exactly as described. but the phone rebooting doesnot stop. Also when the phone is turned on I am not able to open Phone option and under settings I am not able to launch status option under about device? Could my EFS is lost/corrupted?
Click to expand...
Click to collapse
Use This It'll fix it. - You have to install a custom recovery via Odin then flash that fix and you'll be alright, you EFS is warped is all.
I had already tried that fix, but with no luck. I flashed that fix with a lot of combinations like with fresh install of stock rom, with rooted rom etc. No luck
radicalisto said:
Use This It'll fix it. - You have to install a custom recovery via Odin then flash that fix and you'll be alright, you EFS is warped is all.
Click to expand...
Click to collapse
eagle909 said:
I had already tried that fix, but with no luck. I flashed that fix with a lot of combinations like with fresh install of stock rom, with rooted rom etc. No luck
Click to expand...
Click to collapse
Is the phone bootlooping constantly ? and crashing after around 1minute?
rtanceF seize
radicalisto said:
Is the phone bootlooping constantly ? and crashing after around 1minute?
Click to expand...
Click to collapse
When you mean "install a custom recovery via Odin", you meant to install something like TWRP to install the zip using recovery mode?
The phone keeps booting again and again, once the UI of the phone starts, I get a window of 1 min before the phone restarts again. I get a message saying "Process system isn't responding" before the phone restarts.
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Remember: This guide is specifically for those of you who have tried other methods and are still stuck on an old baseband. If you're just looking how to flash your radio, there are easier and less involved methods that don't require any wiping - I strongly advise you to try those first.
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Nice....it helped me :good:
Thanks :highfive:
neoKushan said:
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Click to expand...
Click to collapse
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
nforce4 said:
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
Click to expand...
Click to collapse
Thanks, but unfortunately that didn't work for me.
neoKushan said:
Thanks, but unfortunately that didn't work for me.
Click to expand...
Click to collapse
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
IzArsha said:
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
Click to expand...
Click to collapse
Believe me when I say that I tried that, I tried just about everything before it would finally stick. Removing battery, leaving it off for 10s+ (I did this numerous times as TriangleAway demands it due to the risk if bricking your phone and one time left it off/unplugged for a good 20mins to no avail). There was some kind of write protection in place, Mobile ODIN (yeah tried that as well) mentioned it when trying to flash the Radio - hence why TriangleAway is needed.
Before it got "Stuck", I had manually updated my Modem a few times without issue. I've had the Note 3 since launch and voided Knox within about 2 days of getting it - believe me, I've been there and done that
Nothing worked for me also until I tried this method...
Sent from my SM-N9005 using XDA Premium 4 mobile app
Here's what I don't like, and what I "Do" Like...
Like....
1) A post in the proper forum that seems to help a few people fix their issue when other methods didn't seem to work.
Dislike...
1) Somebody coming in touting their own method (which may or may not work for a particular user). This, believe it or not, only adds to confusion when a person looks for an answer. Now there are different methods in the same thread topic.
2) 2 pages of back and forth arguing as a result of the above ^^^
So, I'll delete all posts concerning this debate on procedures.
Folks, don't go poaching other users threads please. If they provide a solution that helps a few users, then that is GREAT!!! Not all normal solutions work for all users. Stick around long and you will discover this on your own one day.
Cleaned thread, please don't make me come back and do it again.
MD
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
neoKushan said:
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
Click to expand...
Click to collapse
Much better. I didn't mean to start an argument... But it happened somehow.
Good detailed guide however. See you around XDA.
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
neoKushan said:
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
Click to expand...
Click to collapse
I've done almost every method, but not yours. BTW I don't have any other triangle icon except the yellow triangle at the start of Download mode.
MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Unpack the tar file, and flash just the modem.bin into phone (not pda) in Odin.
not working on SM-N900w8
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
jsecruzvalencia said:
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53632129&postcount=1
In the first box.
Note: I did not make any of these root methods. Credits of the people who confirmed/ported cfautoroot is at the end of this post. I got permission to post these root methods here as most of the discussion happened in the General thread. I am not responsible for any damages done to your device. This will trip knox as always and this root method is only for the TMobile and Sprint Tab S 10.5! You've been warned!
Root is now available for these devices! Hope you enjoy and hopefully this should get some development going!
CFAutoRoot for SM-T807T(Tmobile)
Ripx88 confirmed T805 Cfautoroot works for SM-T807T, but you may have a broken recovery. He also confirmed that Twrp and Philz CWM for SM-T805 also works on the SM-T807T. Thanks to him!
Download: http://download.chainfire.eu/477/CF...-Auto-Root-chagalllte-chagallltexx-smt805.zip
CFAutoRoot For SM-T807P (Sprint)
Goriell ported Cfautoroot to this model. Props to him! Still awating for others to confim.
Download: https://mega.co.nz/#!eoB3TbxI!fdUUK-GJFfDx7ietfosnxxHHB2WN4tV0SGieQsdL9tA
Mirror: https://docs.google.com/file/d/0B5DZenb7A53cQldyRGw2TWhBeVk/edit?usp=docslist_api
Odin Download
http://forum.xda-developers.com/showthread.php?p=33970642
How to install
Make sure that in settings>general>security reactivation lock is OFF
edan1979 said:
Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA (AP in odin v3.x) button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, manually shutdown your device and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
Flashing with Odin
1. Put your phone into download mode. To do this turn the phone off and then press volume down+home button+power button at the same time. You will then get a warning saying press up to continue and down to cancel, press volume up and you are now in download mode
2. Start Odin
3.At this point please make sure that ONLY TWO OPTIONS TICKED are "Auto Reboot" and "F.Reset Time" (otherwise you could end up with a very expensive paperweight)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. If there was only one tar file when you extracted the firmware put it in the PDA section.This just means this file contains the PDA+PHONE+CSC all in one firmware
If there are three files they should have one of PDA/PHONE/CSC in their names look for this and put them in the corresponding section.
5. Plug your device into the computer, wait for the drivers to install and then wait for the ID:COM section to turn blue.
6.ONCE AGAIN CHECK YOU HAVE NOT TICKED RE-PARTITION OR PUT IN A PIT FILE
7.Press start and the flash will begin, once this has started do not remove the usb cable or turn of your computer or the device the phone will reboot once the flash has finished.
Click to expand...
Click to collapse
Thanks:
-Chainfire for Cfautoroot method
-Ripx88 for confirming root working on T807T. Helped ALOT!
-goriell for explaining how to port and porting it to SM-T807P. Helped ALOT!
-Samsung
-Samsung updates for firmware... took me 14 hours to download and mirror
-Many many more
-Tkkg1994 for help on somethings
Post from main thread.
CF-Auto-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root. In essence, it does nothing but install and enable SuperSU on your system, so apps can gain root access.
Donate
CF-Root and CF-Auto-Root have been available for many devices (over 50 different models !) and have clocked over 9 million downloads. This is not even counting custom ROMs that include CF-Root (non-Auto) kernels. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every user had donated me $1...
What's installed
- SuperSU binary and APK
- Stock recovery (note that any other recovery you may have installed will be overwritten !)
What's the difference between CF-Auto-Root and CF-Root, and/or other root solutions ?
CF-Root (non-Auto) are manually built rooted kernels and/or flashables that usually provide more than "just root". CF-Auto-Root is built on an automated system that I am constantly improving that takes a stock recovery image and returns an automated rooting packages. These packages are designed to install and enable SuperSU on your device, so apps can gain root access, and nothing more.
The difference with many other rooting solutions is that those will often install a custom recovery for you (I am personally moving away from custom kernels and recoveries, for various reasons), while with CF-Auto-Root you will end up with a stock recovery again.
Not included - custom recovery
A custom recovery like CWM or TWRP is not included.
Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
Bugs.
WIFI Bug Fix: In root explorer go into system/etc/dhcpcd/dhcpcd-run-hooks
It needs to have permissions fixed to "execute" by "user" "group" and "others" by using your favorite file explorer
this will fix your "obtaining ip address loop" without having to ever use static ip address- goriell
You know what.. here is the kernel and stock recovery for the SM-T807T.
Bop! https://mega.co.nz/#F!PwwT3JLQ!KHZNbb3ddgfStcdcB4rmlQ
Firmware to SM-T807T: https://mega.co.nz/#!ylYEBA4D!yWUPtuT60dLCIy_zCN_rqnN2L319oZYSCSFtOC_Pv6Q
Firmware for SMT807P: https://docs.google.com/file/d/0B5DZenb7A53caXhNQkhMb0NkMFU/edit?usp=docslist_api
Bop! Recovery and boot image for SMT807P: https://www.dropbox.com/sh/h5zw61wdn6rx319/AADS2Wb8OFDw3DxpuES7GI2Va?dl=0
Incase anything goes wrong Enjoy
Will look into this later this evening. I have been patiently waiting for a root method for my Sprint Tab S, so I'm really hoping this pans out. Thanks for posting the info!
wosiek said:
Will look into this later this evening. I have been patiently waiting for a root method for my Sprint Tab S, so I'm really hoping this pans out. Thanks for posting the info!
Click to expand...
Click to collapse
Please let me know if it works smoothly. I'm still in the process of tweaking it and looking for bugs.
Anyone have the firmware for the T807P? I see the T807T is up there, but think us Sprint users would need the correct firmware correct or we can run the TMo variant and be fine? Just want to confirm. If that is all we need. I'll go ahead with the process right now.
gorriel said:
Please let me know if it works smoothly. I'm still in the process of tweaking it and looking for bugs.
Click to expand...
Click to collapse
Hey do you have the firmware downloaded? If so can you mirror it for us? I dont have an extra 14 hours to download and upload the firmware
Tried to download the CFAutoRoot file (Sprint SM-T807P) from the link in the OP, but the webpage couldn't be found.
Anyone else experience similar behavior?
wosiek said:
Tried to download the CFAutoRoot file (Sprint SM-T807P) from the link in the OP, but the webpage couldn't be found.
Anyone else experience similar behavior?
Click to expand...
Click to collapse
Works fine for me. Are you on att? Mirror to google drive will be coming. Standby
Yeah, the WAN at the office is managed by ATT. Are they notorious for having issues with MEGA?
I'll try downloading again from home this evening - meant to do that last night, but it fell off my radar.
wosiek said:
Yeah, the WAN at the office is managed by ATT. Are they notorious for having issues with MEGA?
I'll try downloading again from home this evening - meant to do that last night, but it fell off my radar.
Click to expand...
Click to collapse
Att blocks mega because of the history of mega and copyright claims. Ill make another mirror with google drive.
For anyone having trouble with the T807P root please post information on what happened and I will try to troubleshoot it. It is suppose to be a quick and easy CFAutoRoot using ODIN. I will say that it doesn't work if you are trying to use Odin on a virtual machine. It will stop as it tries to upload the cache.img. There is something about virtual machines that blocks it or Odin just doesn't like.
Uploading Sprint firmware now Will also upload the boot.img amd recovery if a dev wants them.
CFAutoRoot For SM-T807P (Sprint)
Can you host the
CFAutoRoot For SM-T807P (Sprint) on something other than mega, Like Drive or Dropbox please. I have Time Warner and i can't download it for some reason.
kingakuma said:
Can you host the
CFAutoRoot For SM-T807P (Sprint) on something other than mega, Like Drive or Dropbox please. I have Time Warner and i can't download it for some reason.
Click to expand...
Click to collapse
Will do hold on
DUHAsianSKILLZ said:
Will do hold on
Click to expand...
Click to collapse
Thank you my good sir.
kingakuma said:
Thank you my good sir.
Click to expand...
Click to collapse
Here ya go https://docs.google.com/file/d/0B5DZenb7A53cQldyRGw2TWhBeVk/edit?usp=docslist_api
DUHAsianSKILLZ said:
Here ya go https://docs.google.com/file/d/0B5DZenb7A53cQldyRGw2TWhBeVk/edit?usp=docslist_api
Click to expand...
Click to collapse
Thank you worked great with Odin 3.09
I can only access odin download mode, i can't access any recovery, how can I flash back to stock?
I had my Tab 4 rooted with CF auto root and was happy!.
Over about 3 months it seemed there were some performance issues so I used super su to un-root, and went for a factory re-set.
I tried to do a software update once back up and running but, got the pop-up telling me it couldn't up-date b/c of knox (actually said system has been altered etc..)
So,,,,,
I plugged into my samsung keys and to update and next thing I knew I had gone from KitKat 4.4.2 to Android 5.0.2.
This also changed my build number, to LRX22G.T530NUUEU1BOE5.
I WANT MY ROOT BACK, , , question is HOW?
None of the numbers aside from model number (SM-T530NU) match up with the CF auto-root now, as they did before.
I'd like to be rooted before heading back to Lagos Nigeria on Monday 6/22/2015,, but I don't want to brick this thing prior to leaving and end up tab-less.
ANYONE HAVE TIME TO HELP?:fingers-crossed:
[email protected]
rnerger said:
I had my Tab 4 rooted with CF auto root and was happy!.
Over about 3 months it seemed there were some performance issues so I used super su to un-root, and went for a factory re-set.
I tried to do a software update once back up and running but, got the pop-up telling me it couldn't up-date b/c of knox (actually said system has been altered etc..)
So,,,,,
I plugged into my samsung keys and to update and next thing I knew I had gone from KitKat 4.4.2 to Android 5.0.2.
This also changed my build number, to LRX22G.T530NUUEU1BOE5.
I WANT MY ROOT BACK, , , question is HOW?
None of the numbers aside from model number (SM-T530NU) match up with the CF auto-root now, as they did before.
I'd like to be rooted before heading back to Lagos Nigeria on Monday 6/22/2015,, but I don't want to brick this thing prior to leaving and end up tab-less.
ANYONE HAVE TIME TO HELP?:fingers-crossed:
[email protected]
Click to expand...
Click to collapse
It's really easy to root 5.0.2 (I have the exact same model). What you need to do is flash TWRP through Odin and immediately boot into recovery and install superSU. Actually I think the download link is broken on that thread, so here is a working link. Download the tar file to your PC, and download the zip file from here and save to your tablet. I'll write more detailed instructions in a minute
---------- Post added at 11:09 AM ---------- Previous post was at 11:05 AM ----------
OK so once you have the files where they need to be, power off your tablet and boot it into download mode. Run Odin on your PC. Make sure to disable the auto-reboot option in Odin, this is crucial. Flash the recovery tar file with the AP button. Now when the flashing is done, your tablet will not automatically reboot (good), but just sit there, the only way to tell it's done is when Odin says it's done (Pass or Reset). Power off the tablet manually, then immediately boot into recovery (home, power, vol+). Install that superSU zip file. Boot system normally, run the superSU app and follow the prompts. Congrats, you're rooted on lollipop.
Sry to ask but, could you??? do a step by step?? for the worried
Or point me to the location of where something along a step by step is posted already. I'm not bad on computers but android I'm still a serious noob.
How to root a 10.1 Tab 4 also links for 8.0, 7.0
This should work provided you use the correct recovery for your model
Preparation: Read everything and make sure you understand. I attached Odin v3.09, v3.10.6, v3.10.7 and 3.11.1. Odin 3.11.1 is recommended. Download the one you want and extract the zip to PC desktop. Also on the tablet enable usb debugging and mock locations in developer settings. Make sure you have the proper USB drivers for your PC. A quick note on file names: development code names for the Tab 4 series are as follows: matisse = 10.1, millet = 8.0, degas = 7.0
Download the twrp-3.0.0.9_matisse_20160314-0843.tar file (this is a twrp recovery that works for wifi, 3g, and lte 10.1 models) and save to PC. Download the superSU zip file and save to tablet storage. Obviously save the files somewhere easy to remember, and easy to navigate to.
Power off tablet. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin. Connect tablet via USB. Hit AP button in Odin, select the TWRP tar file
Disable the "Auto-Reboot" and "Re-Partition" options in Odin, this is critical to success
Flash (click start). When it's done, the progress bar will be full and Odin should say something like "RESET!"
Hold the power button to power down the tablet. Then immediately hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!
Install the SuperSU zip file that is saved to your tablet (tap the install option in TWRP, navigate to the zip file).
Reboot system (normal reboot). When android is booted, run the superSU app and follow the prompts; i.e. update the binary if it asks you to, choose normal install, be patient while it installs (takes a while) and reboot if it tells you to
Accompanying screenshots:
Step 3:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 4:
Step 5:
Step 7:
Tab 4 8.0 TWRP: Tab 4 8.0 unified TWRP (remember millet = 8.0; matisse = 10.1)
Tab 4 7.0 TWRP: SM-T230/NU/T231 (credit to sub77), SM-T230NT (Philz), SM-T235/Y (credit to CTXz), SM-T237P use Philz
Credit of course goes to sub77 for the 10.1, 8.0, and 7.0 TWRP builds, CTXz for TWRP for degaslte moonbutt74 for Philz CWM, and to chainfire for all things superSU. I'm just trying to help and/or point people in the right direction
USB and Remote installation
Prior to getting started should USB debugging be enabled? As well as Allow mock installations??
rnerger said:
Prior to getting started should USB debugging be enabled? As well as Allow mock installations??
Click to expand...
Click to collapse
Yes
Double-checking
Hi and thanks for this info! This is my first post here.
I am seeking to root my SM-T530NU so that I can [attempt to] remote control the device using AirDroid for my business. Currently, I am stuck with TeamViewer which works reasonably well enough but comes with a *very* pricey license north of $60 a month which I am having a hard time stomaching. However- I need to have full mirror over the web, so I am stuck with TV unless I can find another option. (Open to suggestions here.)
Anyhow- I want to try and root the device, however I have never rooted before and am somewhat confused by the info I am finding. Your post here just says I need to match the model number, while others I have come across claim that I need to match the build number as well. In my case, the build number is: LRX22G.T530NUUEU1BOE5.
Please clarify on whether or not the method you posted above should work on this build. If you could also direct me to a good resource for what I need to do to back up my device in case root attempt bricks it, that would be much appreciated as well!
mcmarturano said:
Anyhow- I want to try and root the device, however I have never rooted before and am somewhat confused by the info I am finding. Your post here just says I need to match the model number, while others I have come across claim that I need to match the build number as well. In my case, the build number is: LRX22G.T530NUUEU1BOE5.
Please clarify on whether or not the method you posted above should work on this build. If you could also direct me to a good resource for what I need to do to back up my device in case root attempt bricks it, that would be much appreciated as well!
Click to expand...
Click to collapse
This method will root your device, it's intended for all 10.1 models, but I have the exact same model and firmware as you and this is how I rooted. Flash this file through Odin in case you somehow brick, but if you follow the directions you'll be fine and won't need it
Back up any files, media, etc you have stored on internal storage, but again, you shouldn't need this, it's just to be safe
Thanks for the link to the file! I've been trying to use Odin and so far... no go. I disabled Windows Defender, switched to a shorter stock USB cord from Samsung. When I hit "Start" it initiates, then just gets stuck on recovery.img and nothing happens.
I've also tried Heimdall and can't seem to get that to work either. When I go to save the PIT, it fails. I was also reading a recent thread on github about an issue with newer bootloaders,, so maybe that is the problem with Heimdall.
One thing that might be a problem..? I have an Asus Transformer and am using the USB port on the keyboard because I don't have a micro-to-micro cord. Could that be it?
I wish that Odin would just work... any thoughts on what else to try?
mcmarturano said:
One thing that might be a problem..? I have an Asus Transformer and am using the USB port on the keyboard because I don't have a micro-to-micro cord. Could that be it?
Click to expand...
Click to collapse
I don't know exactly what your setup here is but it sounds like you're doing something wrong. It should be tablet > USB cable > USB port on either laptop or PC:
Also Odin has been known to be finicky it's best to use the USB cable that came in the box with the tablet. That said, any usb to micro usb cable capable of transferring files to/from the tablet in normal android should theoretically be able to work with Odin, I've rarely had issues using different cables.
I've never needed to use Heimdall so unfortunately I can't help you there, although I can say it should not be needed for this task.
mcmarturano said:
Thanks for the link to the file! I've been trying to use Odin and so far... no go. I disabled Windows Defender, switched to a shorter stock USB cord from Samsung. When I hit "Start" it initiates, then just gets stuck on recovery.img and nothing happens.
I've also tried Heimdall and can't seem to get that to work either. When I go to save the PIT, it fails. I was also reading a recent thread on github about an issue with newer bootloaders,, so maybe that is the problem with Heimdall.
One thing that might be a problem..? I have an Asus Transformer and am using the USB port on the keyboard because I don't have a micro-to-micro cord. Could that be it?
I wish that Odin would just work... any thoughts on what else to try?
Click to expand...
Click to collapse
Hi . You must run guide from here http://androidxda.com/flash-samsung-stock-rom-using-odin Only instead stock rom you must to use this recovery http://android.comtek-wiebe.de/OpenRecovery/openrecovery-twrp-2.8.6.0-matisse_wifi_3g_lte.tar .
Download to device to external sdcard this file http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 .
Go to recovery and install tis zip from external sdcard .
Reboot .
Now you have root .
Meh nevermind
---------- Post added at 10:52 AM ---------- Previous post was at 10:38 AM ----------
mcmarturano said:
I wish that Odin would just work... any thoughts on what else to try?
Click to expand...
Click to collapse
It appears the tar file for version 2.8.7.0 is malfunctioning, did you try the 2.8.6.0 tar file?
I just flashed the 2.8.6.0 tar file through Odin successfully, I guess there just must be some problem with the 2.8.7.0 file unfortunately
TWRP 2870 fixed
Yes- That is my basic setup. I have the micro-USB port on the tablet connected to a regular USB port on the computer using the cord that came from Samsung. At first I tried another cord I had that was longer, then learned the length/quality of the cord could cause FAIL, so then I tried the stock cord. Unfortunately, that did not work either.
I was just wondering if the problem might be the USB port. First off, I had trouble at first getting the tablet to connect properly.... it kept connecting/disconnecting. What I tried to remedy this issue was to remove the port driver from Device Manager and reboot the computer to re-install it. After that, the tablet stayed connected... but still FAIL on flashing the recovery image.
The device I'm trying to flash from is a Asus Transformer Book... it has two USB ports- a regular 3.0 port connecting through the keyboard and a mini port on the screen/motherboard component. Since these two components can detach from one another, I'm just wondering if maybe the connection isn't good enough for Odin.
I have another laptop I can try to flash from, so I guess I will try that next. Unless you have any other thoughts/suggestions?
Thanks again for your help!
mcmarturano said:
Yes- That is my basic setup. I have the micro-USB port on the tablet connected to a regular USB port on the computer using the cord that came from Samsung. At first I tried another cord I had that was longer, then learned the length/quality of the cord could cause FAIL, so then I tried the stock cord. Unfortunately, that did not work either.
I was just wondering if the problem might be the USB port. First off, I had trouble at first getting the tablet to connect properly.... it kept connecting/disconnecting. What I tried to remedy this issue was to remove the port driver from Device Manager and reboot the computer to re-install it. After that, the tablet stayed connected... but still FAIL on flashing the recovery image.
The device I'm trying to flash from is a Asus Transformer Book... it has two USB ports- a regular 3.0 port connecting through the keyboard and a mini port on the screen/motherboard component. Since these two components can detach from one another, I'm just wondering if maybe the connection isn't good enough for Odin.
I have another laptop I can try to flash from, so I guess I will try that next. Unless you have any other thoughts/suggestions?
Thanks again for your help!
Click to expand...
Click to collapse
Setup is OK, were you using 2.8.7.0 or 2.8.6.0? Try 2.8.6.0 if you haven't already
repey6 said:
TWRP 2870 fixed
Click to expand...
Click to collapse
OK I will try that too. Thanks!
thisisapoorusernamechoice said:
Setup is OK, were you using 2.8.7.0 or 2.8.6.0? Try 2.8.6.0 if you haven't already
Click to expand...
Click to collapse
SUCCESS! 2.8.6.0 worked like a charm. Thanks a million!
Still have not done this but intend to soon. What about UN-root??
Is there a special way that I will have to go about UN-rooting ???
I just got the SM-T537A variant for my wife, will this procedure work for that model as well?
PDADoc said:
I just got the SM-T537A variant for my wife, will this procedure work for that model as well?
Click to expand...
Click to collapse
No, sorry, you can't have a custom recovery or custom kernel on that model because of the locked bootloader. I think people have been routing that model with towelroot or kingroot