Database Users

[GUIDE] Fix an unflashable or soft bricked GSII (I9100G/M/P/T VERSION INCLUDED)

Hello everyone!
This is a guide dedicated to noobs, so if you're not one, I would advise to stop reading now! (altough feedback would be great! )
Yes, there have been quite a few threads about fixing a soft brick. But what I'm writting now is another solution to a different kind of problem : unflashable GSII (which also works with a soft brick of course ), which is a soft brick and a corrupted NAND rw (read/write) function.
Just in case you don't know, a soft brick occurs when you flash a ROM or Kernel, and it doesn't go your way, thus bricking the "soft part", aka Software, of your phone. Therefore, it is easy to recover from. Now, regarding NAND rw (NAND's read and write function being the corruption) it means that it is an issue deeper than a soft brick.
It is obvious when you can flash a kernel, but you can't flash a ROM, because it can't properly read the NAND, but can flash a kernel. But you ask, why the kernel? Because flashing a kernel is a bit deeper than flashing a ROM. When you flash a kernel, you're changing/putting new instructions to the hardware, and when flashing a ROM, the instructions that are drewn are different and more "simple", so when flashing, ODIN will say "FAIL" instead of "PASS", or suddenly stopping the flash out of nowhere.
__________________________________________________
IF YOU ONLY HAVE A BOOTLOOP​
Wipe data/factory reset and wipe cache. IF THAT DOESN'T WORK, MOVE ON WITH THE GUIDE
__________________________________________________
VERY IMPORTANT ANNOUNCEMENT​
I would like to first apologize for my absence. My past months have been super busy, and they don't seem to be ending anytime soon. And "anytime soon" meaning in a couple of years. And I'm actually glad that this is happening, since I've been working pretty hard to achieve the state I'm in.
This thread has evolved into something I've never imagined. Only because of YOU guys, we managed to turn a normal thread into a pretty popular and well used Guide, and it made me so happy and joyous of being apart of the XDA community. I feel proud in being a XDA nut. This whole success is just because of YOU guys.
As painful as it is to say this... I believe that I will be dropping support on this thread after the New Year, because a) I lost my Galaxy S2 in Paris in a taxi with no hope of getting it back when I went there 3 weeks ago and b) I'm probably getting a Galaxy Note 2 in the New Year, so this thread will be most likely ported and maintained over at the Note 2 forums.
I'm extremely sorry it has come this way, and I hope you guys will understand. In the following days I'll be updating the files to their latest versions, and will try to find new bootloaders and kernels, but without sources, I'm unable to do so. I'll update whatever I'll be able to
Regards and thanks to all of you that have supported me,
Rafael K.​
Click to expand...
Click to collapse
__________________________________________________
IMPORTANT ANNOUNCEMENT #2
Please welcome neerajganga, your new thread maintainer (along with me)! He has been of great help, so I think he deserves this kind of announcement!​__________________________________________________
Okay, so apparently people that come from ICS and try to recover it with the GB files make their phones nearly unrecoverable. So, now I've divided the guide in 2 sections : the GINGERBREAD VERSION and the ICS VERSION.
Due to popular demand, I have also added an I9100G Version, which is here!
I have also added the I9100 M/P/T versions. Now I support ALL I9100 variants.
But for the moment, I do not have the G/M/P/T .PIT, kernels or Bootloader, so if you have any of those version, only flash what is in the provided package.​
__________________________________________________
Let's start with the basic files, downloads and requirements​
GINGERBREAD VERSION
1) You have to know the basics of ODIN and flashing (duh )
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II
4) Download the necessary files : the Recovery Package/ROM (password is samfirmware.com), the Kernel (password is [email protected]) and the Bootloader.
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano
ICS VERSION
1) You have to know the basics of ODIN and flashing (duh )
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II
4) Download the necessary files : the Recovery Package/ROM [THIS PACKAGE ALREADY INCLUDES THE BOOTLOADER] (password is samfirmware.com) and the Kernel.
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano
I9100G VERSION
1) You have to know the basics of ODIN and flashing (duh )
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II
4) Download the necessary ROM (they are Gingerbread 2.3.6) : Africa (Iraq), Asia (Malaysia), Europe (Open Austria), Middle East (Saudi Arabia). (password is samfirmware.com)
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano
I9100M VERSION
1) You have to know the basics of ODIN and flashing (duh )
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II
4) Download the necessary files : the Recovery Package (Open Canada) (password is samfirmware.com).
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano
I9100P VERSION
1) You have to know the basics of ODIN and flashing (duh )
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II
4) Download the necessary files : the Recovery Package (UK - Orange) GINGERBREAD VERSION / Recovery Package (UK - Orange) ICS VERSION (password is samfirmware.com).
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano
I9100T VERSION
1) You have to know the basics of ODIN and flashing (duh )
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II
4) Download the necessary files : the Recovery Package (Australia - Telstra) GINGERBREAD VERSION / Recovery Package (Australia - Three/Vodafone) ICS VERSION (password is samfirmware.com).
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano
And that is it! Let's get down to business
__________________________________________________
If your GSII has the folowing symptoms :
Bootloop
Stuck on GSII logo, but already removed the battery to try to fix it
Enters Download mode and Recovery mode
It means that you are soft bricked and is easy to solve.
But if your symptoms are the mentioned above, PLUS the symptoms below
Enters Download mode but does NOT enter recovery mode (usually means a NAND rw corruption)
Doesn't flash
Bad flash in odin (FAIL after flashing, or the flashing suddenly stops)
Then it means that you have a bigger issue, such as the aforementioned NAND rw corruption.
It's time to open up ODIN and start reviving your phone!
__________________________________________________
First of all, let's just have a quick glance of how ODIN looks like, and where we should put the files :
{
"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"
}
As the picture clearly shows, the green rectangle is where you can tick. Those 2 which are ticked must remain that way. And the red one is well... Where you SHOULDN'T touch
ONLY FLASH WITH RE-PARTITION TICKED AND A PIT FILE IF YOU ARE SURE
THAT THE FLASH WILL SUCCEED.
Which means that you CANNOT have a damaged USB, corrupted drivers and such.
​
When recovering from a soft brick, it is recommended, not mandatory, to have Re-partition ticked with a .PIT file. So you must be extra careful when you are using a .PIT and Re-Partition. And obviously, the red box is the one where you can't and don't want to mess with
But where are the files going, you say?
.PIT -> PIT
APBOOT -> BOOTLOADER (or PDA if flashed alone)
CODE -> PDA
MODEM -> PHONE
CSC -> CSC
***If you have a 1 file .tar package, then flash it in PDA***​
There is only 1 way to recover a soft bricked phone. How to recover from a NAND corruption? We'll get on that later on
__________________________________________________
Recovering a soft bricked phone​
1) Grab the Recovery Package, and you'll see a bunch of .tar files. Take a look at the names. You'll see CODE, MODEM, CSC and .PIT. Put each one in its place.
2) Turn off your phone. Enter Download mode by presing Volume Down + Home + Power button.
3) Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9)
Now here, take a breath​
First try flashing WITHOUT the .PIT and re-partition. And only if it DOESN'T WORK OR FIX then you flash with the .PIT and Re-Partition ticked.
4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5 minutes to flash.
Have you done everything correctly until now? Then...
Congratulations on recovering your phone!​
You deserve some cake afterwards, and some rest
Now, if your problem is the NAND rw coruption, and wasn't fixed by the above fix, then follow these steps :
5) Download the Kernel. Flash it in PDA. Without ticking Re-Partitioning
6) Successful? Nice, hope is still present.
7) Flash the recovery package, following steps 1-4 This should fix your issue. If it does not, then :
WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.
8) Download the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partitioning
9) Flash the Kernel, as in step 5
10) Flash the recovery package, like in steps 1-4 And that will fix any of your issues
I hope that this guide was helpful, and if it was, hit the thanks button!
Credits mainly go to Intratech, for his amazing gallery of ROMS and files
_______________________
Disclaimer
This is to be used as educational information. I am not liable of any damage that may occur to your phone.

Awesome guide! Thanks for taking the time to put this together!

Download mode is Volume Down. I think you miswrote that. Thanks for the write up.

interfreak said:
Awesome guide! Thanks for taking the time to put this together!
Click to expand...
Click to collapse
Thanks! I think I'll post this in Q&A... I feel it's more appropriate there.
@Robotapocalypse Thanks for the headsup!

Good work, should be stickied.
Our Mutual Friend should thank you, but he'll probably rant at you for not posting this before

Thanks a lot. Very good post.

very nice! was looking for this to post to our threads on my home country...
btw...may i suggest 7zip as well...i guess its the best unzipper for packages from xda
---------- Post added at 07:26 PM ---------- Previous post was at 07:26 PM ----------
B3311 said:
Good work, should be stickied.
Our Mutual Friend should thank you, but he'll probably rant at you for not posting this before
Click to expand...
Click to collapse
nyahahaha...i think it makes the 3 of us...was that the tool?

jermitano said:
very nice! was looking for this to post to our threads on my home country...
btw...may i suggest 7zip as well...i guess its the best unzipper for packages from xda
---------- Post added at 07:26 PM ---------- Previous post was at 07:26 PM ----------
nyahahaha...i think it makes the 3 of us...was that the tool?
Click to expand...
Click to collapse
He was, is and always will be
Good call for 7zip.

B3311 said:
Good work, should be stickied.
Our Mutual Friend should thank you, but he'll probably rant at you for not posting this before
Click to expand...
Click to collapse
Thanks! I'm gonna post this in Q&A section, because it's where I've found that this would be of bigger use, and so I'd like to have it stickied
Our mutual "friend"... lol, that guy...
jermitano said:
very nice! was looking for this to post to our threads on my home country...
btw...may i suggest 7zip as well...i guess its the best unzipper for packages from xda
---------- Post added at 07:26 PM ---------- Previous post was at 07:26 PM ----------
nyahahaha...i think it makes the 3 of us...was that the tool?
Click to expand...
Click to collapse
Alright, adding 7zip to the OP

Where is the OP?!?!

Apparentltly, I overwritten the OP somehow... fail lol.
Thankfully it was saved in my email...

Hopefully this thread will save a lot of questions.
Feedback:
This is a really dangerous advice:
When recovering from a soft brick, it is recommended, not mandatory, to have Re-partition ticked with a .PIT file. So you must be extra careful when you are using a .PIT and Re-Partition. And obviously, the red box is the one where you can't and don't want to mess with
Click to expand...
Click to collapse
Sometimes people can't flash because they have a damaged usb cable, corrupted drivers etc. When they use .pit and re-partition, they have a great chance of really bricking their device. People should never use those, unless they are certain the flash will succeed! And the problem is, noobs won't know if they can flash or not. I think you should delete that part because people that come here, have no idea what they are doing.

Lennyz1988 said:
Hopefully this thread will save a lot of questions.
Feedback:
This is a really dangerous advice:
Sometimes people can't flash because they have a damaged usb cable, corrupted drivers etc. When they use .pit and re-partition, they have a great chance of really bricking their device. People should never use those, unless they are certain the flash will succeed! And the problem is, noobs won't know if they can flash or not. I think you should delete that part because people that come here, have no idea what they are doing.
Click to expand...
Click to collapse
I see. Then, I can add this :
ONLY FLASH WITH RE-PARTITION TICKED AND A PIT FILE IF YOU ARE SURE
THAT THE FLASH WILL SUCCEED.
Which means that you CANNOT have a damaged USB, corrupted drivers and such.​
What do you think? Or is a delete better?
Thanks for the feedback tho!

Phistachio said:
I see. Then, I can add this :
ONLY FLASH WITH RE-PARTITION TICKED AND A PIT FILE IF YOU ARE SURE
THAT THE FLASH WILL SUCCEED.
Which means that you CANNOT have a damaged USB, corrupted drivers and such.​
What do you think? Or is a delete better?
Thanks for the feedback tho!
Click to expand...
Click to collapse
Didn't do me any harm. I realised I had a duff USB cable that wouldn't flash. Swapped for a new one and all ok. I've also had damaged drivers too. Big thanks to the OP phistachio for helping me out at Xmas this year by bringing my phone back from the dead!

Sorry guys, forgot to add the password... Added!

password?
Thanks for the perfect guide, i'm a semy noob with a soft bricked s2 and everything worked perfect. However i wanted to download the file's for a futere insurance so to say but the password "samfirmware.com" is rejected? 7zip simply says wrong paswoord. This is however only on the Kernel file, the others extracted without an password needed.
Maybe something to look into?
other than that, iw worked great and my phone is back to life again.
thnx

Good work OP!
Sent from my GT-I9100 using Tapatalk

Helpfully Work...thanks for this!
kR didi

.You Say
It is obvious when you can flash a kernel, but you can't flash a ROM, because it can't properly read the NAND, but can flash a kernel. But you ask, why the kernel? Because flashing a kernel is a bit deeper than flashing a ROM. When you flash a kernel, you're changing/putting new instructions to the hardware, and when flashing a ROM, the instructions that are drewn are different and more "simple", so when flashing, ODIN wkll say "FAIL" instead of "PASS", or suddenly stopping the flash out of nowhere.
A query on that statement a kernel is deeper than a rom
But a rom contains a kernel are you in effect claiming that flashing a rom the kernel goes to x depth but flashing a kernel on its own the kernel goes deeper .
Sorry it does not make sense looks like you are confusing something here ROM = firmware that nearly always includes a kernel .
jje

Panzertand said:
Thanks for the perfect guide, i'm a semy noob with a soft bricked s2 and everything worked perfect. However i wanted to download the file's for a futere insurance so to say but the password "samfirmware.com" is rejected? 7zip simply says wrong paswoord. This is however only on the Kernel file, the others extracted without an password needed.
Maybe something to look into?
other than that, iw worked great and my phone is back to life again.
thnx
Click to expand...
Click to collapse
The kernel+bootloader password is [email protected] I believe.

Made a mistake, will pay someone to help me fix. {Fixed}

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:

[GUIDE] Baseband/Radio "stuck" and not updating? Here's how to fix it!

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.

[Q] SM-T530NU Android version 5.0.2

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

Flashing a Note3, asking for help...

First, I have installed a ROM on my phone before and I followed very specific instructions. I am a developer in the land of microsoft so I recognize I am very much a newbie here.
Now, on to what I have now and what I want to do.
1. I have a Note 3. The SM-N9005. The baseband version is: N900W8.... suffice to say it is a canadian phone. If the rest of the baseband numbers are important I will post them, just ask.
2. I want to install the Alliance ROM, it seems to have what I am looking for.
3. When I rooted and ROMed my phone years ago I used the following thread: http://forum.xda-developers.com/show....php?t=2614772
4. Currently my phone is running a Jedi ROM from the vintage of that thread. However I must have made a mistake back then because the Hotspot feature does not work. Making the hotspot feature work again is my primary reason for undertaking this operation. The 4G works, I can use the Internet on the phone just fine. The wireless works I can connect to a wireless signal and use the internet that way (I confirmed this was working with mobile data off). The hotspot will allow a connection from a device (such as my laptop), but no data passes between the 4G connection and the connected computer.(yes, I turned on Mobile Data On) I have tried this using different computers connected to the hotspot to confirm it is the fault of the Note3.
Back when I did this flashing thing before I had to be careful to get the right CSC file and modem file and a few other steps. I had to specify the correct CSC file in addition to the rom I wanted to flash.
With that background, my questions are below (if you need any more info to point me in the right direction, just ask):
One last note... I will be performing any and all instructions from a macbook pro Mid 2012 with no other devices on the usb host controller running a near virgin copy of windows 7.
-----------------------------------------------------------
Do I need to worry about CSC files, modem files and so on to Flash to Alliance ROM and still have everything work? I ran across a thread that said that some ROMs have all the CSC files in them, but I cannot find any direct information (or I missed it) about the Alliance ROM with regards to CSC files and the like.
I thought I had TWRP installed, but when I boot to recovery the top two lines read
line1: Android system recovery <3e>
line2: KOT49H.N9005XXUENB4
Is this TWRP? Should I download the latest TWRP for my device and flash it using the AP button from Odin 3.10? If there is a different technique I should use, I will try it.
The instructions say that if I am not installing from stock 4.4.2 or stock 5.0 that I should install stock first, then install the alliance rom. I visited the sammobile website and there are no ROMs for the USA or Canada there... am I missing something or should I just use the UK ROM from that website? I guess I am not sure how to identify the correct ROM for Canada.
I did load the Alliance ROM 8.2 onto my SD card and attempted to use the option apply update from external storage and it failed. Nothing happened at all and the phone eventually rebooted and the ROM never installed.
Thanks in advance for any help you can provide me on this endeavour. I am largely looking for resources that I have not been able to find up until now. I am okay with help such as Read This Post! and so on.

If the phone is an n9005, not sure how the baseband can be n900w8 as the n9005 was never sold by Canadian carriers as far as I know.
Here's a link to the stock n900w8 firmware: http://www.sammobile.com/firmwares/database/SM-N900W8/

wizengamot said:
Thanks in advance for any help you can provide me on this endeavour. I am largely looking for resources that I have not been able to find up until now. I am okay with help such as Read This Post! and so on.
Click to expand...
Click to collapse
First of all, you should detect what device you own. You can install this APP and add some screenshots for avoid problems and give us more info about your device (IMEI not necessary).
We will try to detect if you own a clone, a SM-N9005 or SM-N900W8.

Additional Info as requested
Here are the screenshots that were requested. Thanks for your help. Yes, I will and continue to use the thanks button as well.

wizengamot said:
Here are the screenshots that were requested. Thanks for your help. Yes, I will and continue to use the thanks button as well.
Click to expand...
Click to collapse
I think you should flash the stock rom first via ODIN. Coz your baseband don't fit with your bootloader and your PDA either.
PS: You can use MEGA mirror as well :highfive:

I have the stock ROM from SamMobile. I am set to flash the phone. I have everything set but I searched the forum as a final check to make sure I am doing the right things and I found a post that says I need a PIT file. I can find a PIT file for HLTE verizon phones but I do not know if that PIT file works with the image I downloaded from sammobile. Of course I am connecting the dots from the info program I ran where is says on the general tab that the phone is of type hlte.
When I click on PIT in Odin it says this function is for engineers only. As a programmer myself I would put a message like that for a function I don't want people using needlessly but it does give me pause to ask about it. As they say Flash in Haste...Cry at Leisure..

Many thanks to you all. I have installed the stock ROM and it works. I can make phone calls, wifi works, 4g works, and hotspot works.. YAYA... Now, I would do the alliance rom but I can honestly say I am not sure I want to mess with it. I want the phone call recording feature but that is all I want...It would be the only reason to do the alliance rom. And it appears as though that rom is not done the same way as the stock rom as there is no md5 file.
anyhow.. thanks again to all who helped. I have thanked each post as well. If you have some tips based on my above info, I would be very grateful.

There are quite a lot of call recording apps which work well as far as I know, ACR being one of the example.

Only tar or tar.md5 files are flashed in Odin. Any non-stock ROMs are flashed using a custom recovery.
You can flash a custom recovery to your phone using Odin in the PDA/AP box from here: https://twrp.me/Devices/ Just use the latest tar file.
Once you have a custom recovery on the phone, you can create a backup of your existing ROM, then flash a custom ROM.