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.
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
I'll cut right to the chase, I've soft-bricked my Note 3 (sm-9005). I bought it off Newegg and received it Friday. I proceeded to use Chainfire's root, and then installed TWirp which worked without incident. My problem started after I installed X-Note. My system was unstable, had no sound and would make calls but not receive them. (I'm in USA, on AT&T network).
I know I should have made a backup but I didn't. (Im a Samsung fan, have owned the Note 1, Galaxy 3, and now the International Note 3). I went to sammobile and the started to realize I was in trouble. (I don't know the original CSC) It was not printed on the box, and on the back of the phone my info is the same as The guys in this thread: http://forum.xda-developers.com/showthread.php?t=2628435.
Long story short. I've tried multiple stock recoveries. Some are stuck in a bootloop (at the Samsung screen). Some will appear to work but have no sound, camera doesn't work, etc. I can still get iinto Download mode, can even reflash Twirp after screwing up. When I try other custom roms they either bootloop or half way work (no sound, crashes, etc.)
I know NewEgg won't take this phone back, and honestly since i'm still able to access it via odin I dont want to send it in IF someone here can help me get it back, and I'll pay someone $100.00 via PayPal if they can.
I have TeamViewer / Skype, or will get whatever you need to help me Via / video call, over the phone, etc.
It is 10:00am (CST) right now. I will be back here at 12:30pm (2.5 Hours) I hope someone is willing to help me with this issue. 2 days working with this and i'm at my end.
If anyone is willing to help please let me know I'll keep this page open and will be refreshing it often, in the mean time I'll keep searching forums.
Was it JB or KK when got it?
Maybe you're trying to run a KK rom when you have a JB bootloader still?
Is the knox tripped?
MystaMagoo said:
Was it JB or KK when got it?
Maybe you're trying to run a KK rom when you have a JB bootloader still?
Is the knox tripped?
Click to expand...
Click to collapse
Is on KK 4.2.2 Bootloader from Factory. I'm sure Knox was / is tripped because I had used ChainFire's root Friday night after getting the phone. Things went bad when I tried to flash X-Note yesterday.
I have reinstalled a Polish Rom (N9005XXUEND3_N9005XEOEND2_N9005XXUENC2_HOME), and it's booting up, but no sound at all, camera, etc. Also just checked, No modem, (IMEI or BaseBand) even though I flashed the above file thru Odin 3.7 [But WiFi, GPS works]
Edit #2: Downloading UK recovery firmware now.
Not that this will help, I do NOT remember anything about the country code, but /I can tell you the sticker on the back has some spanish on it, and when I started the welcome screen Friday I had to change the language from Spanish to English.
Heres a picture of the Sticker, sorry for the bad quality.
{
"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"
}
What do you mean by no modem / IMEI. If it doesn't show any IMEI number with Sim card inserted than it's probably due to corrupt EFS. Do you have a backup of EFS?
Envoyé de mon GT-N5120 en utilisant Tapatalk
LuMe96 said:
What do you mean by no modem / IMEI. If it doesn't show any IMEI number with Sim card inserted than it's probably due to corrupt EFS. Do you have a backup of EFS?
Envoyé de mon GT-N5120 en utilisant Tapatalk
Click to expand...
Click to collapse
No I didn't make an EFS backup When I had my Note 1 there was never any mention about EFS on any rom I flashed and they all worked without issue, but i'm having a heck of a time.
Right it's showing Unknown BaseBand / or Imei under system / about.
With the UK rom it seems stable / not crashing, wifi works and I can surf, but No Cellular service, or sound, or camera.
hello there, as far as i know , csc is just customer service code or something like that, just bloatware and other stuff loaded for a specified region, an example, my device is for UAE, csc is xsi or something like that, but whats installed on the device is the polish firmware and the device is functioning properly
from what you stated that you had no idea which firmware version was installed prior to flashing the custom rom,
the following steps (may) be helpful for you
search the forums for these separate files and flash them separately, start with the modem/baseband as this is more important than sound and camera at the current time being
modem:
http://www.4shared.com/file/4YUQQVkYce/REPACK_DXUENE3_MODEM.html (credit goes to @SERGiooooo and those who extracted to files)
to flash modem go into download mode on the device and in odin select CP and unselect autoreboot, then reboot manually again to download mode and repeat and select autoreboot this time (flash it twice)
then you need to search for a compatible or recommended bootloader for your rom and flash it
and finally do a standard wipe and reinstall a rom of your choice which is compatible with your device
please keep in mind that you should only flash roms which are made for your variant( n9005 rom for n9005 and n900 for n900 and so on)
also keep in mind that some roms from sammobile.com wont be compatible (eg: hong kong nf1 is not compatible with other n9005's because of the diffrent pit )
make sure your device is 32gb n9005 and re download the rom again
finally, may i suggest to try this rom (stock based de-odexed based on ne4 and all the extra files like bootloaders and modems are included separately) and hope it solves the sound and other issues as well
http://forum.xda-developers.com/showthread.php?t=2649176
apologies for the details, this is just a suggestion coz I had the same issue with the IMEI and baseband problem
and always always do backups
I flashed singapore (NE4) stock rom (supposed to be international) from sammobile. After that, when I tried to go back to older modem my imei would be unknown, sound was messed up, and dialer would take a long time to start, but after flashing singapore modem back my imei would be there again.
It looks like that samsung is trying to block flashing of older versions of anything... Try that singapore rom (which is almost the latest available, and should flash latest everything bl, pda, csc, phone) and see if it works.
ciribic said:
I flashed singapore (NE4) stock rom (supposed to be international) from sammobile. After that, when I tried to go back to older modem my imei would be unknown, sound was messed up, and dialer would take a long time to start, but after flashing singapore modem back my imei would be there again.
It looks like that samsung is trying to block flashing of older versions of anything... Try that singapore rom (which is almost the latest available, and should flash latest everything bl, pda, csc, phone) and see if it works.
Click to expand...
Click to collapse
Downloading Now. IF you are my savior give me your PayPal Address and you'll be $100 richer. Quck question, first time I flash using Odin, just put .tar in PDA then flash, right? If I need to just flash the modem back, how do I do that?
jb0nd38372 said:
Downloading Now. IF you are my savior give me your PayPal Address and you'll be $100 richer. Quck question, first time I flash using Odin, just put .tar in PDA then flash, right? If I need to just flash the modem back, how do I do that?
Click to expand...
Click to collapse
Yes ap/pda for the whole rom, cp for modem, bl for bootloader
Good luck
Bnjalal said:
Yes ap/pda for the whole rom, cp for modem, bl for bootloader
Good luck
Click to expand...
Click to collapse
Sent you A PM, you fixed it, Just need your PayPal address. Do you have any ideas why I can't flash other roms? X-Note got me in this mess, and from what I understand it's supposedly a great rom.
You fixed it!!!!
Bnjalal said:
Yes ap/pda for the whole rom, cp for modem, bl for bootloader
Good luck
Click to expand...
Click to collapse
PM Sent, your $100 is waiting.
Easy with the money and carefully with flashing.
Yes, put it in pda, make sure that only auto reboot and f.reset time are checked, nothing else. Modem is included in the rom. If you are flashing only modem you put it in phone field. The thing is I'm not sure You'll be able to go back to old modem after you flash this one (NE3), when I tried flashing my old modem it messed up things, and flashing whole older ROM would skip flashing modem because it would detect newer already there.
Put your phone in download mode (make sure that battery is at least 60%)
Start Odin and open tar file in pda, wait a minute or two till md5 is checked when it says it's checked an ok connect your phone. I'll assume you installed samsung drivers previously. Wait a few moments here because windows might install drivers (if you have never connected your phone while in dl mode). Now there shoud be device added in ID:COM field in Odin and it should be blue/green. now you can press start.
jb0nd38372 said:
PM Sent, your $100 is waiting.
Click to expand...
Click to collapse
Sir i believe that @ciribic is the one who suggested to download the ne4 singapore stock international rom and i replied instead of him on which selection to choose in odin please verify that as i dont want to take credit on other persons work
And please accept my apologies if I caused any confusion as i was only trying to help you through the process in any means possible
Sorry
Bnjalal said:
Sir i believe that @ciribic is the one who suggested to download the ne4 singapore stock international rom and i replied instead of him on which selection to choose in odin please verify that as i dont want to take credit on other persons work
And please accept my apologies if I caused any confusion as i was only trying to help you through the process in any means possible
Click to expand...
Click to collapse
ciribic said:
Easy with the money and carefully with flashing.
Click to expand...
Click to collapse
You both helped me. I am thankful to have it back up and working. I don't understand why on my Note 1 (AT&T locked), I was able to flash every rom on that forum with no issues; Every Rom on this forum gives me BAD issues, could I have got a bad phone or something? (It was new in box, ordered from Newegg.com), but could it be defective somehow?
@ciribic I sent you a PM,
OP allow me to clear any misunderstanding with fellow members and please give all credit to him as I did nothing
now back to your question , you probably flashed roms based on recent stock TW roms and those require you to be on recent bootloaders and modems, reason for this difference is that rom builders take into consideration that the user does not want to trip his KNOX flag and may use other methods to flash the rom without using custom recovories like TWRP/CWM (ex mobile odin, safestrap) so most custom roms come without modems and bootloaders and if you unzip the x-note rom you will see that there are no bootloaders and modems included if im not mistaken
Now to get rid of any OCD related to the your device whether its faulty or not, try flashing back x-note <after> you make a complete backup in TWRP(my personal favorite) and im 95% sure that you will not have these issues anymore
ciribic said:
I flashed singapore (NE4) stock rom (supposed to be international) from sammobile. After that, when I tried to go back to older modem my imei would be unknown, sound was messed up, and dialer would take a long time to start, but after flashing singapore modem back my imei would be there again.
It looks like that samsung is trying to block flashing of older versions of anything... Try that singapore rom (which is almost the latest available, and should flash latest everything bl, pda, csc, phone) and see if it works.
Click to expand...
Click to collapse
ciribic said:
Easy with the money and carefully with flashing.
Yes, put it in pda, make sure that only auto reboot and f.reset time are checked, nothing else. Modem is included in the rom. If you are flashing only modem you put it in phone field. The thing is I'm not sure You'll be able to go back to old modem after you flash this one (NE3), when I tried flashing my old modem it messed up things, and flashing whole older ROM would skip flashing modem because it would detect newer already there.
Put your phone in download mode (make sure that battery is at least 60%)
Start Odin and open tar file in pda, wait a minute or two till md5 is checked when it says it's checked an ok connect your phone. I'll assume you installed samsung drivers previously. Wait a few moments here because windows might install drivers (if you have never connected your phone while in dl mode). Now there shoud be device added in ID:COM field in Odin and it should be blue/green. now you can press start.
Click to expand...
Click to collapse
Bnjalal said:
@ciribic I sent you a PM,
OP allow me to clear any misunderstanding with fellow members and please give all credit to him as I did nothing
now back to your question , you probably flashed roms based on recent stock TW roms and those require you to be on recent bootloaders and modems, reason for this difference is that rom builders take into consideration that the user does not want to trip his KNOX flag and may use other methods to flash the rom without using custom recovories like TWRP/CWM (ex mobile odin, safestrap) so most custom roms come without modems and bootloaders and if you unzip the x-note rom you will see that there are no bootloaders and modems included if im not mistaken
Now to get rid of any OCD related to the your device whether its faulty or not, try flashing back x-note <after> you make a complete backup in TWRP(my personal favorite) and im 95% sure that you will not have these issues anymore
Click to expand...
Click to collapse
Making that Twirp Backup as I type this, got an SD card just for that purpose now. TBH, I could care less about warranty because it won't cover Water damage, drops, misuse and that's where 99% of my past problems have happened. Knox is annoying to no end, I just got through running System Uninstaller to pull all the knox libraries / apk's and modules out.
I think i'll just stick a better optimized / open kernel on it and launcher, and call it quits. I'm 42, after these past 2 days, I feel 82.
good decision and hope u enjoy your new phone :good:
Update 10/30/2014
There's no need to go back to the "B3" version any longer. The T900UEUANI1 is available on SamMobile, to be flashed w. Odin.
The cf-auto-root listed as "B3" on chainfire's site will work.
Note, I have not created any of this, please thank the original developers in their posts. This is simply a compilation of available info needed to have the most complete and working SM-T900, Samsung Galaxy Tab Pro 12.2.
The sole purpose is to make you save time. However, I'm not saying this will work, and it might even brick your device, but that risk is yours to take. However, it worked for me, so why shouldn't it... Trust the steps, there's a reason for this madness. Believe me when I say it; I've learned the hard way, and it has not been a pleasant journey.
If your SD cards looses necessary rw privileges it seems like not even a backup will correct them, even after wiping the SD cards and formatting data.
If you haven't yet upgraded from B3 to D4, I recommend you to do this first! There are major improvements between the two versions.
1. Rooting:
First flash the P900XXUANB3-RecoveryImg (forgetting this will create a softbrick, and you will have to start over, also use the Odin 3.07, supplied, I have not tested with the later 3.09)
then flash CF-Auto-Root-v2wifi-v2wifixx-smt900
for detailed method and files see: http://androidcentral.us/2014/05/root-galaxy-tab-pro-12-2-sm-t900/
I forgot, it's important to use original cables directly connected to the PC, a docking station connection, or an EOM cable might be a reason for flash failure.
2. install TWRP:
Flash openrecovery-twrp-2.7.1.0-v1awifi
link: http://forum.xda-developers.com/showthread.php?t=2679825
3. disable Knox:
Open SuperSU and answer yes to disabling KNOX
4. fix SD-card issue in KitKat 4.4:
Download and run JRummy's "SD KitKat Fixer" from market. I had no luck with any other comfortable fixing apps.
5. important!:
reboot into recovery and wipe both External and Internal SD, as well as Formatting Data. Don't forget to backup all files you want to keep onto your PC! for later re-installation. I know this must feel hard, but I sincerely advice you you follow this step. Most apps are not KitKat ready, as of now, and won't allow you to download or access the data if you haven't prepared your SD's in advance.
6. init d support:
Download and install Stericson's BusyBox from market
Download and install Uni-init v1.0
link: http://forum.xda-developers.com/showthread.php?t=1933849
7. Flash Player support:
Download and install fixed AdobeFlashPlayer 11.1
link: http://forum.xda-developers.com/google-nexus-5/help/guide-how-to-play-flash-video-android-4-t2548001
If you're using Dolphin Browser, also install the Dolphin JetPack, and modify Settings/Web Content/Flash Player/ to Always On.
8. ADBlocking:
Dowload and flash LATEST_MoaAB_ADBlocking_Super
link: http://forum.xda-developers.com/showthread.php?t=1916098
9. De-bloating:
for de-bloating at a maximum you can disable numerous of the Samsung apps, by pushing the three dots, upper right corner, while in the apps-screen mode.
Also, don't forget to un-check the de-bloated apps from auto-update in Play Store, as well as in the Samsung update if you signed up for this service.
10. (Re)-nstall your apps
You're done, and it's time to restore or download all the apps you need and it will work in KitKat 4.4
None of the modified stock ROM's currently available seem to mount correctly. If something goes wrong, you will most likely loose your SD card privileges. The original T900UEUAND4 stock ROM can be found here: http://www.sammobile.com/firmwares/3/?download=29102. Just unzip and flash with Odin, then start again with step 1.
Also, due to lack of time, I will not be able to monitor this post. I hope you will help one another out with clarifications, or anything I might have missed.
Best of luck,
Delete
Very nicely laid out. I've already done all this, but it's great to see a guide for new comers that may not know what to do. Thank you.
Thank you for the guide and gathering everything together. I just wanted to throw this out there, I followed the directions exactly....and I could not get mine to root. It would continually soft brick and a screen full of odd colors would come up every time. I read on the CF Auto Root thread that others had the same issue. One determined individual said he did it 10 times and it finally worked. Soooo....I continued to do it. And it finally worked, trying nothing different each time.
I tried 2 different computers, a win7 and win8, installed Kies to make sure drivers were there. Used official and another cable. I tried everything I could think of. In the end I would say as long as you're following the directions just keep trying.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
That's a link to the P900XXUANB3-RecoveryImg that my friend and I both used before getting root. Thanks again for the guide arcadia2uk!
So I was able to root and install TWRP but after an app caused some issues I went to wipe cache and brick. Flashed stock and had to do factory reset. However, I learned that attempting to restore a backup or wipe cache or do factory reset via twrp causes brick. Have to use Odin to flash back to factory. I also had to use the German region and lost my symbols on keyboard.
................edit..............
I updated kies and reinstalled all the drivers and flashed the cellular south firmware...All is well and current. Rooted, twrp, having fun.
Hi,
I followed all instructions but Flashing was successfully only after USB driver update. This is my story:
My Tab Pro 12 has ND4 stock.
Downgrade P900XXUANB3-RecoveryImg with Odin.
Then flash CF-Auto-Root-v2wifi-v2wifixx-smt900.
All Odin task stucked at Cache and after a few minutes screen got attached frightening picture
{
"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"
}
.
Then tab not booted.
Tried this http://forum.xda-developers.com/showpost.php?p=54576936&postcount=63
and tried different usb ports, cables.
But no success.
Then I installed latest Kies3 (started only the usb driver in tools menu) then restart Win7 and after then all right.
Odin flashed CF root.
Best wishes I hope this helps!
deleted
robert1968 said:
Hi,
I followed all instructions but Flashing was successfully only after USB driver update. This is my story:
My Tab Pro 12 has ND4 stock.
Downgrade P900XXUANB3-RecoveryImg with Odin.
Then flash CF-Auto-Root-v2wifi-v2wifixx-smt900.
All Odin task stucked at Cache and after a few minutes screen got attached frightening picture
.
Then tab not booted.
Tried this http://forum.xda-developers.com/showpost.php?p=54576936&postcount=63
and tried different usb ports, cables.
But no success.
Then I installed latest Kies3 (started only the usb driver in tools menu) then restart Win7 and after then all right.
Odin flashed CF root.
Best wishes I hope this helps!
Click to expand...
Click to collapse
The fix is actually put the m
Sent from my HTC One_M8 using Tapatalk
I don't know if it will help anyone else, but I just flashed TWRP 2.8 on my Galaxy Tab Pro 12.2 wifi with "D4" firmware using odin and it worked and I was able to make successfully a backup. Below is a link to the recovery I flashed. Of course your mileage may vary so do it at your own risk.
http://teamw.in/project/twrp2/244
The easiest way to debloat it is probably via titanium backup's batch mode actually.
Oh boy I just mess up my Tab.... It's stock in the firmware error screen. Will try to flash stock firmware as soon as I get WiFi, reflashing stock via Odin should fix it as I read right?
Fingers crossed: say yes please!
Edit: it boots with stock fw now is back to normal except that can't access or boot into recovery mode. Any help or a working recovery file? Thanks in advance
Sent from my HTC One using Xparent BlueTapatalk 2
saruba said:
Oh boy I just mess up my Tab.... It's stock in the firmware error screen. Will try to flash stock firmware as soon as I get WiFi, reflashing stock via Odin should fix it as I read right?
Fingers crossed: say yes please!
Edit: it boots with stock fw now is back to normal except that can't access or boot into recovery mode. Any help or a working recovery file? Thanks in advance
Sent from my HTC One using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
try flashing the latest TWRP 2.8.1.1 with Odin. You can also download Quick Boot (Reboot) from Play Store, that will facilitate the booting process.
arcadia2uk said:
try flashing the latest TWRP 2.8.1.1 with Odin. You can also download Quick Boot (Reboot) from Play Store, that will facilitate the booting process.
Click to expand...
Click to collapse
Yey! U R the man! Thanks so much it works flawlessly!
I think I have 2 different recovery files and they both doesn't work I don't know why I got them from twrp site... Anyways just to let you know I've done every thing with Odin 3.09 so yeah I'm confirming that it works fine.
Sent from my HTC One using Xparent BlueTapatalk 2
There does not seem to be any recent onfo on my partner phone, nor very clear if the 5360 rom is compatible
So here is the question. Is there a minimalist rom with equally good battery life. Her phone is much better than my ace
on battery life. but is full of samsung garbage.
bwizz60 said:
There does not seem to be any recent onfo on my partner phone, nor very clear if the 5360 rom is compatible
So here is the question. Is there a minimalist rom with equally good battery life. Her phone is much better than my ace
on battery life. but is full of samsung garbage.
Click to expand...
Click to collapse
As far as I'm aware the 5363 is the o2 variant of the 5360
You might be able to just unlock the phone if not already unlocked (use galaxy toolbox) & flash 5360 firmware and use 5360 roms
Anything you do you do at your own risk - neither myself or xda are responsible for damage caused
I have rooted and unlocked phone ready to install reincarnation rom. I can't boot into clockwork recovery as I get the "error in sideload zip 7 message" I have tried installing clockwork from rom manager but still same. Think it is because the GTs 5363 bt number is not recognised.
can I get around this issue? I did a google search and found a cwm clockwork bla bla that seems to work.
but I will wait for any comments/imput before I go ahead
bwizz60 said:
I have rooted and unlocked phone ready to install reincarnation rom. I can't boot into clockwork recovery as I get the "error in sideload zip 7 message" I have tried installing clockwork from rom manager but still same. Think it is because the GTs 5363 bt number is not recognised.
can I get around this issue? I did a google search and found a cwm clockwork bla bla that seems to work.
but I will wait for any comments/imput before I go ahead
Click to expand...
Click to collapse
Why would you install cwm from rom manager? It's not supported - please do some searching and some reading else you will damage your device
There are two ways to get cwm on galaxy y
1- Flash temporary cwm zip in stock recovery - see http://d-h.st/u2m
2- Flash a kernel with cwm built in
If neither work on your variant you will need to flash 5360 firmware via odin at your own risk
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
bwizz60 said:
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
Click to expand...
Click to collapse
Hi.
Here is the CWM link: http://forum.xda-developers.com/showthread.php?t=2649475
Please do some digging first before asking.
Also, ROM Manager is not supported on our phones, so do not use it.
bwizz60 said:
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
Click to expand...
Click to collapse
Don't know what you are clicking on as it's a zip file
Make sure you are clicking on the right download button & not an ad - Install ad blocking software on pc or an app on phone if required
I never post exe files - all my files on dev host are Flashable zips/tars unless otherwise stated
See below Screenshot - Just press the download button as shown in Screenshot
{
"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"
}
Also you should take note of what you are reading, where you are reading it & what device it relates to - rom manager has never been a compatible way of flashing cwm on a galaxy y
The reading re my device is quite confusing. but I got the CWM installed thanks. In the interim I have soft bricked the phone. When it boots it still reads gts 5363 in the boot screen. I was expecting it to now read 5360? would it be a good idea to flash a standard 5360 onto the phone via odin .
and maybe work forward from that
bwizz60 said:
The reading re my device is quite confusing. but I got the CWM installed thanks. In the interim I have soft bricked the phone. When it boots it still reads gts 5363 in the boot screen. I was expecting it to now read 5360? would it be a good idea to flash a standard 5360 onto the phone via odin .
and maybe work forward from that
Click to expand...
Click to collapse
It would only say 5360 if you flashed 5360 firmware via odin
Iv kept telling you if you want to use 5360 kernels you will probably have to flash 5360 firmware
Feel free to do what you want at your own risk
Sorry bad info on my part I was trying to use CWM via galaxy toolbox. I hit a snag with the CWM as I it was faulty and I could not go back out of the advanced screen. to follow the rom suppliers step by step. Only way out was to reboot, and hence brick
bwizz60 said:
Sorry bad info on my part I was trying to use CWM via galaxy toolbox. I hit a snag with the CWM as I it was faulty and I could not go back out of the advanced screen. to follow the rom suppliers step by step. Only way out was to reboot, and hence brick
Click to expand...
Click to collapse
With respect Iv told you both ways to get into cwm
With the temp zip I provided by Flashing in stock rom or by Flashing a kernel with cwm built in
You have chosen to ignore all what I'm telling you & trying to do things in unconventional ways - Therefore I can no longer offer you support
Just flash stock rom via odin
I was using the cwm downloaded from the the link that kindly supplied. I was using galaxy toolbox as suggested by yourself. There is lots of reading on the XDA site !.I am sure it is your prerogative to dismiss me as an idiot but I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
bwizz60 said:
I was using the cwm downloaded from the the link that kindly supplied. I was using galaxy toolbox as suggested by yourself. There is lots of reading on the XDA site !.I am sure it is your prerogative to dismiss me as an idiot but I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
Click to expand...
Click to collapse
I said to use galaxy toolbox to unlock your phone - ie remove network sim lock if your phone is locked to a specific network
At no point did I say use it to flash cwm
If you can't get into recovery you need to flash stock rom via odin
I do have alot of patience but I find it annoying when people don't read things properly especially when the answers have already been written for them
I do appreciate your help. I am now following the odin info "supplied by yourself on the site"
Ta
bwizz60 said:
I am now following the odin info "supplied by yourself on the site"
Ta
Click to expand...
Click to collapse
That sounds sarcastic...
FYI, this Odin info can be found in his signature. It is also a sticky in the Android dev section.
Search, search, search.
bwizz60 said:
I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
Click to expand...
Click to collapse
u wot m8
If you don't know what you're reading when it's filled with seemingly bizarre terminology (we've been at that stage one time or another), you do three things:
1) Read on and/or use Google.
Usually definitions will pop out after a while. If I'm not mistaken there are a few threads outlining terminology definitions and usage.
2) Follow everything that they say. And when I say follow, I mean follow 100%, by the book. Reread the instructions over and over to make sure you are actually doing it right.
3) PM another more well-informed member, and don't be afraid to ask.
As for patience, well...
He has dealt with countless people that were in about the same situation as you: thinking that they knew what they were doing and eventually getting into deep s**t with no way out. He has always tried helped them out. Problem is, some of them simply don't want to listen, even if he was correct (which he most likely was). Even then, he tries his best.
Trust me, he knows what he's doing.
Take a deep breath, reread EVERYTHING on this thread, and restart from square one: stock ROM.
If you're too lazy to find (I hope you're not) here is the link for Odin:
http://forum.xda-developers.com/showthread.php?t=2568853
Risky, but everything here is a risk, isn't it? I rarely hear of 5363 users getting stuck here, so this should be fine.
Good luck.
Why would I be sarcastic? there is volumes of stuff on the site all done by this guy.! I show appeciation of this . I can assure you I do spend hours trying to follow information. Some of the links don't work ,sometimes my Firefox security stops progress . very frustrating at times;.
Thanks Mr Smith, now unbricked. I could not find odin 3.184 "spent over an hour trying" 1.85 worked ok . Phone now wakes up as 5360! If the rom is less bloated than the 02 one .I might leave well alone! Stress level falling!
What he meant was Odin3 v1.84.
But, its nice to see things sorted out with your partner's phone.
I 've had time to have a look at the standard rom Iinstalled. Glad the phone is working etc but I still have not achieved anything .
I still need to get rid of the samsung bundled stuff and be able to use the sd card storage. I am still unable to use CWM 5.0.26 "I get the code 7 error and the phone has re un rooted . Update ,Ive now re rooted it!
bwizz60 said:
I 've had time to have a look at the standard rom Iinstalled. Glad the phone is working etc but I still have not achieved anything .
I still need to get rid of the samsung bundled stuff and be able to use the sd card storage. I am still unable to use CWM 5.0.26 "I get the code 7 error and the phone has re un rooted . Update ,Ive now re rooted it!
Click to expand...
Click to collapse
Root phone
Use Link2sd (playstore) to uninstall system apps
Use the temp cwm I posted a few pages back - place on root (not in any folder) of sd card & flash in stock recovery to get to cwm
Or use a custom recovery that has cwm built in eg hells fusion #50 for stock based roms
Can't give you any more support with this as I'm just repeating what Iv already said
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?