Develop Bugs

baseband and build number error

My computer died in the middle of rom flash, which caused my T-Mobile SGS4 to nearly brick. I attempted several recoveries (CWM, TWRP, and OUDHS) and several custom & stock roms (including odin) before I was finally able to see some life in it. Because of this, the baseband is the official stock after the update (uvuamdl), and the build number is the official stock prior to the update (uvuamdb). I don't think this would normally be a problem, but now I am unable to flash a custom or stock rom so I think it may be the reason. The phone does not run very smooth, and a notification asking me to reboot because of errors keeps popping up. It is now rooted as well. Is there a way or method to bring everything back to stock?
Thanks,
Ant

ams77 said:
My computer died in the middle of rom flash, which caused my T-Mobile SGS4 to nearly brick. I attempted several recoveries (CWM, TWRP, and OUDHS) and several custom & stock roms (including odin) before I was finally able to see some life in it. Because of this, the baseband is the official stock after the update (uvuamdl), and the build number is the official stock prior to the update (uvuamdb). I don't think this would normally be a problem, but now I am unable to flash a custom or stock rom so I think it may be the reason. The phone does not run very smooth, and a notification asking me to reboot because of errors keeps popping up. It is now rooted as well. Is there a way or method to bring everything back to stock?
Thanks,
Ant
Click to expand...
Click to collapse
If you can get into Download Mode, use ODIN to bring everything back to stock.

ams77 said:
My computer died in the middle of rom flash, which caused my T-Mobile SGS4 to nearly brick. I attempted several recoveries (CWM, TWRP, and OUDHS) and several custom & stock roms (including odin) before I was finally able to see some life in it. Because of this, the baseband is the official stock after the update (uvuamdl), and the build number is the official stock prior to the update (uvuamdb). I don't think this would normally be a problem, but now I am unable to flash a custom or stock rom so I think it may be the reason. The phone does not run very smooth, and a notification asking me to reboot because of errors keeps popping up. It is now rooted as well. Is there a way or method to bring everything back to stock?
Thanks,
Ant
Click to expand...
Click to collapse
I had the same problem and all you need to do is Odin the new stock firmware again. You can get the firmware here in the android development area.

[Q] No Network or IMEI number, :-S

Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?

shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!

Gandicela said:
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Click to expand...
Click to collapse
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.

shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
Mate, firstly this is the hard way of recovering from "Unknown Baseband" issue. Finally the simple solution was only to download and install an app called SELinux Mode Changer from PlayStore. Then using that app, change SELinux from Enforcing to Permissive resolved everything related to IMEI, EFS, and Unknown Baseband. So hard way I did; i didn't know any better then.
By the way the link is correct. Start from the procedure from the line that says "Installation Instruction [Mobile odin is now have support for NOTE2]"
You must be in download mode (Vol Down, Home, & Power button all pressed together) to flash the Stock ROM using Odin. But where is your status now? If in recovery, can you re-install a ROM? If u r able to reboot back up to OMNI, just install the SELinux app and u will be good to go.
Cheers!

shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!

shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
karlonicolas said:
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
Click to expand...
Click to collapse
Nice, thanks!
For all others that might face "unknown baseband" with 4.3 to 4.4 flashing of ROMS, SELinux Mode Changer app from Playstore will fix that problem. Install the app and set SELinux from Enforcing to Permissive.

i hope your problem is fixed.
i'm not too familiar with CM roms, as i have been using stock since gingerbread. but you have to first do a full wipe before flashing from CM to stock. did you do that? perhaps you can go to recovery, do a full wipe, include Dalvik and Cache. Then go to bootloader and flash your rom.
by the way, my chipset is qualcomm yours may be exynos. if so, then i'm not confident about this solution because i have tried this several times, but only on note 2 LTE.
good luck!

Finding a TWRP EFS backup for Sprint Samsung SPH-L900 (Note 2), IMEI gone

First root and thought I had everything covered, but of course something hiccuped and now I have Unknown IMEI, Baseband, Hardware version, Software version and can't connect to the network. All my apps and wifi are working.
Before installing TWRP I looked for a way to backup my entire device and could find nothing that would work before rooting or flashing a recovery to replace the stock recovery. I finally just went ahead and flashed TWRP and created a backup with that. There were errors that had to do with the Samsung calendar app data that made the backup fail. I excluded data from the backup and was able to complete what was reported as a successful backup. I did not allow TWRP to install root access before reboot.
I then installed via Odin the Chainfire SuperSU successfully and thought was free and clear. When I rebooted everything worked fine, except the phone would not connect to network and reported "Searching for Service."
Upon investigation into that I discovered the other issues that all seem to be tied to the EFS partition. I tried restoring the EFS partition from the TWRP backup I created immediately after installing TWRP, but that fixed nothing. It seems that the TWRP installation itself was what killed the EFS partition data.
If I understand correctly, flashing the stock Sprint ROM L900VPUCOH3, should fix the problem, but then I would still have to restore the IMEI, which I can't do without a rooted device. Also, even if it worked, I couldn't backup the EFS partition only, without a rooted device. So my logic is that if I could get a functioning TWRP EFS only backup for my device, I could restore that, reset the IMEI and be back in the ballgame.
Before I started down this path my phone was lagging badly and freezing up. I did a soft reset and got the speed back, but then the apps began crashing randomly and intermittently, both the native ones and the downloaded ones. I then did a factory reset and everything worked right. I reinstalled my downloaded apps and kept my speed and stability. It took several days for me to download, configure and add all my accounts back manually and everything remained fast and stable. I would really hate to have to start from scratch all over again.
Any assistance would be appreciated. Below is what I looked like before I got maimed:
Software Version
L900VPUCOH3
Hardware Version
L900.09
Model number
SPH-L900
Android version
4.4.2
Baseband version
L900VPUCOH3
Kernel version
3.0.31-3084104
[email protected] #1
Mon Aug 24 17:13:18 KST 2015
Build number
KOT49H.L900VPUCOH3
SE for Android status
Enforcing
SEPF_SPH-L900_4.4.2_0033
Mon Aug 24 17:29:53 KST 2015
This is what I look like now:
Software Version
Unknown
Hardware Version
(blank)
Model number
SPH-L900
Android version
4.4.2
Baseband version
Unknown
Kernel version
3.0.31-3084104
[email protected] #1
Mon Aug 24 17:13:18 KST 2015
Build number
KOT49H.L900VPUCOH3
SE for Android status
Enforcing
SEPF_SPH-L900_4.4.2_0033
Mon Aug 24 17:29:53 KST 2015
If there is another approach that would rectify the situation then I am all ears. I can fix a computer, but phones are an entirely foreign animal to me. I'll be the first to tell you I don't know enough and welcome the learning experience, I just wish it it wasn't under life or death circumstances.
**UPDATE**
While still investigating possible solutions, something has come to my attention. I do not have the original IMEI info anywhere!! I have the MEID only. I was able to get the serial number from a Samsung registration email, and was able to use a converter to calculate the ESN from the MEID. I tried tap dancing with Sprint to get the IMEI, but all I could get from them was the MEID info I already had.

First of all, please keep away from TWRP since it causes many problems on the N2 from installation to flashing roms.
I suggest you to :
1- Flash with Odin a FULL restore image of stock rom (to restore partitions table, modem, and rebuild your IMEI).
2- Flash with Odin "Philz custom recovery", especially this version.
3- Flash SuperSU flashable Zip with Philz recovery.
Normally, everything should be fine (a working phone with root privilege).

Clarification of Stock ROM Version
zlazaar said:
First of all, please keep away from TWRP since it causes many problems on the N2 from installation to flashing roms.
I suggest you to :
1- Flash with Odin (...too new to even quote an outside url) a FULL restore image of stock rom (oh well...) (to restore partitions table, modem, and rebuild your IMEI).
2- Flash with Odin "Philz custom recovery", especially (...ditto) this version (ditto...).
3- Flash (...ditto) SuperSU flashable Zip (ditto...) with Philz recovery.
Normally, everything should be fine (a working phone with root privilege).
Click to expand...
Click to collapse
The stock ROM you linked to SPH-L900_NE2 causes me a bit of concern as my phone is on L900VPUCOH3. I was already up to 4.4.2 KitKat.
Unless there is some specific reason I should use the NE2 version, I am going to locate an OH3 version and work with that.
Thank you for your help, that was pretty much the route I thought made logical sense with the lack of a patch to my issue, to go back to stock and start over. I wasn't aware of any TWRP issues, so that was also a big help and I already have SuperSU.
While I wait for a response I am going to go and try to do my due diligence to find out more about Philz Recovery, so that I can move on and get back in the game. No phone for New Years Eve will suck a big fat one!!

zlazaar said:
First of all, please keep away from TWRP since it causes many problems on the N2 from installation to flashing roms.
I suggest you to :
1- Flash with Odin ... a FULL restore image of stock rom ... (to restore partitions table, modem, and rebuild your IMEI).
2- Flash with Odin "Philz custom recovery", especially ... this version[/URL].
3- Flash ... SuperSU flashable Zip ... with Philz recovery.
Normally, everything should be fine (a working phone with root privilege).
Click to expand...
Click to collapse
(This response took such a long time because between the holidays, typing the original reply which was lost due to a badly placed refresh touch-button on this keyboard and subsequent issues with the phone, I'm just getting back to it now. This one is much less detailed than the original that was lost.)
As per my previous reply regarding flashing NE2 instead of OH3, I couldn't find a source for the OH3 stock ROM that I was comfortable with, so I just went with your instructions and viola!, all was working again, with IMEI, MEID and everything else back to functioning. I had connection to the carrier network, and after 2 OTA updates, I was back to the OH3 version.
The installation of Philz Recovery and Chainfire's SuperSU went fine. So as far as my original issue, my phone was back to normal, with custom recovery and root added.
Thank you zlazaar for your assistance. Seeing that you were the only one that responded, you truly were a lifesaver for both me and my phone, and though I may have eventually gotten to the process you described by hit, miss or frustration, you save me a lot of time and angst since at that point my biggest concern was a working phone, not the root.
From there it went downhill because I ran into different issues, the only part that relates to this thread is this, should I have used the working TWRP to wipe the ROM before flashing the new stock NE2 ROM to the phone with ODIN? I flashed OVER what was there which might have caused the problems I had later on down the road.
I will post the problems I had after this in another thread when I have a chance and put a link to it here. That way I won't have to retype from the beginning, and anyone this might help can see other issues they may encounter.
On the up side, I think I'm pretty practiced in rooting the SPH-L900 and rooting it. Also, since Sprint couldn't fix or replace my Note 2 after I was done with it, I'm getting a Note 4 as a replacement. (I managed to brick it leaving a KIES error message as the only thing it would do besides Download Mode at power up or starting to recovery.) Worst case, if I brick the new Note 4
On the down side, now I'm going to have a phone I'm going to have to start from scratch learning what can and can't be done to it, as well as deal with the stronger KNOX...and now I have all these Note 2 ROMS (Funny enough, the tech at Sprint said he wanted to try more but they are so restricted on the internet he couldn't download the files he wanted. I said to myself, betcha I have the files he was looking for!!)

Softbrick cause buy Bootloader

Hello Everyone,
I've been up literally all night (I know, that old line) trying to fix what happened. I bought this phone last year. It was unlocked and rooted. I never updated because it was never giving me issues. But the lagging and battery has finally got to me. So I decided to upgrade to this new rom(http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423).
It looked clean and minimal bloat, just the way I like it. However, I didn't get past updating the Bootloader. As soon as I did in Odin it went into a bootloop. Try as I might I couldn't get into recovery. Luckily I can still get into download mode. So I read up and found that I should flash the original firmware. Unfortunately it failed because I tried to upload an older version. Is there anyway I can flash this rom via odin? Sorry for the noobish questions here but it's past 8am and I've just about given up. If I see recovery is not seandroid enforcing or rev check fail s6 device 3 binary 2 I'm going to lose my mind lol. I did have TWRP installed if that makes a difference. Just can't access it. Any help would be greatly appreciated. Thanks guys
P.S. I know I used buy instead of buy but can't fix it. It was really early in the morning haha

Ok I managed to download the stock MM version for my phone. I still have bootloop issues but I'm in recovery mode at least. However not TWRP though, if I try downloading a custom recovery it says the dreaded "recovery is not seandroid enforcing" also it says Device does not have DRK. Any guesses here?

Well, I've just about given up. I've searched extensively and it appears that the fix is to download a different kernel. However, the G925T has no support yet for any custom MM kernels. I made a backup of my phone via TWRP before this whole mess but the problem is I can't get to it. And to be honest I'm not entirely sure if it's still there. Here are the steps I have taken thus far.
1. Downloaded MM Bootloader: this was the start of my issues. Started bootloop, couldn't get into recovery.
2: Attempted to download original LP firmware: Odin denied it, there was another version I download from zidroid called "downgradeable". Obviously did nothing because I was still running MM bootloader and was effectively the same thing.
3. Downloaded stock MM firmware: Finally was able to boot into recovery but it was useless as it was the stock one. Also wouldn't boot up due to "Device does not have DRK" and boots straight into download mode. Tried to download recovery but none of them worked. Kicked me back to "Recovery not Seandroid enforcing".
So this is where I'm at, I just want to get back to my old device I honestly would rather have a clunky phone than one that doesn't work at all. Is it possible to downgrade back to LP and get back into TWRP and flash my backup? Do I still have root after taking all those steps? Any help would be greatly appreciated because this has officially ruined my weekend?

I guess I'm talking to myself here but if anyone ever encounters this issue at least it will be documented if I ever do fix it.
I managed to get into TWRP. Although arter doesn't have a kernel that supports our system yet. The twrp recovery he has does, ours is compatible with the fi variant. Again that's only the recovery no the kernel.
So I was at a cross roads, do I restore my backup or do I continue with the download. Unfortunately none of those options worked. When restoring the backup I get stuck on the samsung page with "kernel not enforcing" or whatever. Do be fair, before I did this with my device it had already said that. So I gave it some time, but alas no luck. And the same issue with the when I tried to continue the download. I'm a little lost as to how to continue now. I just want my device back.

try dd the mm firmware

Nickle60 said:
I guess I'm talking to myself here but if anyone ever encounters this issue at least it will be documented if I ever do fix it.
I managed to get into TWRP. Although arter doesn't have a kernel that supports our system yet. The twrp recovery he has does, ours is compatible with the fi variant. Again that's only the recovery no the kernel.
So I was at a cross roads, do I restore my backup or do I continue with the download. Unfortunately none of those options worked. When restoring the backup I get stuck on the samsung page with "kernel not enforcing" or whatever. Do be fair, before I did this with my device it had already said that. So I gave it some time, but alas no luck. And the same issue with the when I tried to continue the download. I'm a little lost as to how to continue now. I just want my device back.
Click to expand...
Click to collapse
Not sure what state your phone is in. To begin with, the not Seandroid message with recovery is normal, if you are on marshamallo. If you are on LP then you get the same with the Kernel message when it boots up. BOTH are normal depending on which Firmware you are on. But that said you shouldn't be trying to downgrade, if that's even possible. Have you tried smartswitch and the emergency software restore function. It will wipe out everything on your phone but at least will boot up with the latest MM. Then simply Odin the arter TWRP and then install XTRESTOL which I am using NO PROBLEMS on my TMobile 925T variant. NOT sure about the DRK root key problem. But when you install stock MM with smartswitch you should have also gone into settings and enable developer settings to make sure OEM unlock was enabled before doing anything else.
Lastly, the Arterkernel will actually work fine as far as booting up. The ONLY issue is call audio which we all are waiting for a patch, or a kernel that supports everything. But, I have TWRP installed that arter kernel, and the phone boots up just fine. You just do NOT have call audio. My suggestion at this point is smartswitch. Just know your serial number so that when asked you can plug that in to the menus smartswitch goes thru before wiping and restoring current MM latest and greatest.

Docmjldds said:
Not sure what state your phone is in. To begin with, the not Seandroid message with recovery is normal, if you are on marshamallo. If you are on LP then you get the same with the Kernel message when it boots up. BOTH are normal depending on which Firmware you are on. But that said you shouldn't be trying to downgrade, if that's even possible. Have you tried smartswitch and the emergency software restore function. It will wipe out everything on your phone but at least will boot up with the latest MM. Then simply Odin the arter TWRP and then install XTRESTOL which I am using NO PROBLEMS on my TMobile 925T variant. NOT sure about the DRK root key problem. But when you install stock MM with smartswitch you should have also gone into settings and enable developer settings to make sure OEM unlock was enabled before doing anything else.
Lastly, the Arterkernel will actually work fine as far as booting up. The ONLY issue is call audio which we all are waiting for a patch, or a kernel that supports everything. But, I have TWRP installed that arter kernel, and the phone boots up just fine. You just do NOT have call audio. My suggestion at this point is smartswitch. Just know your serial number so that when asked you can plug that in to the menus smartswitch goes thru before wiping and restoring current MM latest and greatest.
Click to expand...
Click to collapse
Thanks for the reply, I don't have the box for the phone and couldn't boot it up so that was a no go. But luckily for me I decided to give that rom one more go. I flashed bootloader and modem again, then flashed TWRP, and finally installed the rom. And boom! It worked, and it's better and faster than ever. I'm not sure what all that other mess was but I am going to say I have everything I need at the moment and won't be flashing anything anytime soon. I've learned a great deal through this process though. Thanks for everyone's help.

Help - Galaxy Tab S 10.5 Bootloop Out of Nowhere

So...
Last week, my wife's Tab S went into a bootloop. She runs complete stock, we haven't rooted, or anything. There had been a notification about an update, but she hadn't touched it. She'd updated to Lollipop at some point last year, but hadn't applied the absolute latest update. One day last week, she just turned it on, and it started bootlooping.
Because it was so stock, there were no backups, no nandroids, or anything like that. No Custom Recovery. I told her "well, we can just do a factory reset. You'll lose everything, but once we get you back up and running, it'll just re-download everything from the Goog." So we factory reset it. Looked good for a minute, booted into the first screen, enter in your Wi-Fi password, all that. As soon as we got the Wi-Fi password entered, however, it re-booted. And keep rebooting. Bootloop city. No problem. I walked her through (over the phone) using Odin to flash the latest Lollipop firmware. No dice. It appeared to flash successfully, but still bootlooped.
Over the weekend, I tried using Kies to flash the most official firmware I could find. Everything was successful -computer recognized the device, was able to download "direct from the source," as it were, but it got stuck at 69% twice before failing. I read somewhere that one had to run Kies in administrator mode to get it to successfully complete. So I did, and it got past 69%, successfully completing the flash. STILL NO LUCK. STILL WITH THE BOOTLOOPS.
Last night, I realized that I hadn't flashed in Odin using Administrator Mode. Tried it, using latest 5.0.2 (XAR-Cellular South). Flashed successfully, all appeared well. Still bootlooped.
So, I'm stuck. I can get into recovery, I can get into Download Mode, I can successfully flash. I just can't get the darn thing booted.
Thoughts, anyone? Should I try flashing a Custom ROM? How hard is that using Odin? Thanks in advance.

Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.

Nandr0idC0nsumer said:
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Click to expand...
Click to collapse
Thanks, I'll try these steps tonight when I get home, and report back!

All right, here's something interesting. Before I tried your first step, I remembered that the other night, I left it stuck at the Samsung logo -it was just kind of stuck there, and since the behavior was a little different than I'd seen before (not continuous bootlooping), I thought I'd boot into recovery and wipe. I did, I wiped (factory reset), and rebooted. The tablet booted into the first screen, Accessibility/Wi-Fi, blahblah. This was where it usually rebooted. On a hunch, I bypassed entering in my WiFi key. I then bypassed almost everything else (Samsung account, Google account, etc.), expecting that the tablet would reboot at any moment. But I made it to the front apps page, where it shows you the side-launcher, the Magazine-Flipboard thingie, and whatnot. Wi-Fi still not connected, though. I opened up the app drawer, and scrolled around. Looked really good for a moment. I even took a picture with the camera, and viewed it in Gallery! Feeling brave, I thought, "well, maybe it just needed a couple of minutes before firing up the radio." So I went into settings, and inputted my WiFi key. It connected. And rebooted into its bootloop. (getting so tired of that boot-sound).
Went ahead and flashed the most original stock firmware I could find. As always, flashed successfully. As soon as it booted, I made my way to recovery, and wiped, per your instructions. No luck. Bootloop again.
It's something in the WiFi is what I've come to think as a result of the above. Which I don't entirely understand, as I thought the radio got re-flashed with the firmware.
I'm ready to try flashing a Custom Rom. Can I do that through Odin, or should I try and flash TWRP, and do it through there? Will TWRP flash without a working (bootable) OS?
All right. Thanks for your response!

Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.

ashyx said:
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
Click to expand...
Click to collapse
Got TWRP installed. Won't backup. Fails at 16% (system partition, I think). Just powers down to battery indicator in the middle of the backup. Looks like it backs up the EFS, though, since it's the first one. And when I go into TWRP's Restore option, there's a backup there (though I don't dare try and restore it).
Now I have to figure out a way to get the Custom ROM and GAPPS I downloaded onto the tablet without a reliable boot... It's gotten to the front screen a time or two tonight, but starts looping even when I bypass the WiFi setup.

Entered adb/TWRP interface. Tried to push two files, a Custom ROM file, and a GAPPS file. The ROM failed, with some sort of "Error 7," incompatible data, blahblah... Just out of curiosity, I tried to push the GAPPS file, and that failed after about 6%, and the tablet powered off.
I'm running out of ideas.

copied a custom rom to a USB/OTG stick (thumbdrive), and plugged it in. Fired up TWRP, tried to install. Wouldn't. Wouldn't install GAPPS, either. Looks like the only way it wants to flash anything is through ODIN or KIES.

The Latest...
All right...
I remembered that sometimes the TWRP version mattered. When I installed TRWP last night, I installed the latest and greatest, 3.0.2. Last night after I gave up, I remembered that sometimes, the latest and greatest TWRP doesn't install things perfectly. So, this morning, I downloaded TWRP 2.8.6-ish onto the USB/OTG device, and re-flashed the recovery partition. To be honest, I was surprised that TWRP was even able to flash that (but the TWRP image is only like 9.8 MB, so...)...
Got TWRP 2.8.6.0 flashed, and rebooted into TWRP. Immediately decided to try and re-flash the custom ROM that I'd tried unsuccessfully to flash last night, since the thumbdrive was still plugged in. Resurrection Remix Lollipop. Lined up GAPPS in the queue, as well. The ROM *appeared* to flash better than it had in TWRP 3.0.2, but it was sort of hard to see... GAPPS failed, and I was prepared to watch another round of bootloops. It did bootloop, sort of. The RR splash screen appeared, said that it was installing (or preparing) xx out of XX apps. Then, it rebooted. I figured it was doing its bootloop thing. However, it got to the same screen, "installing xx out of XX apps. Except that XX number had gone down, and the xx number had gone up. It repeated this action about 4 times --the last time I saw it reboot, it was "installing 1 out of 2 apps." And then...?
It booted into the RR lockscreen.
Of course, there were no GAPPS. In fact, there are something like only 20 apps total on the tablet. But it appears somewhat stable at the moment. (See picture).
Afraid to try and connect WiFi, afraid that it'll just bootloop.
Speaking of bootloop. At one point, once we got it booted, my wife hit an option in the Settings. LCD Density, I believe. As soon as she hit it (she literally just placed her finger over the 320 default option), the tablet rebooted. No loop, though. Rebooted straight back to the RR lockscreen.
So I appear to have a somewhat stable OS flashed onto the tablet at the moment. No GAPPS, though. No WiFi.
Anybody have a suggestion on where to go from here? I have my doubts as to whether or not I can even back up this configuration.
Sorry about all the updates. I kind of figured that if *anyone* else ever goes through what I'm going through, they'll have some sense of all the different things that can be tried in resurrecting a bricked/bootlooping device. I appreciate everyone's efforts to date -thank you so much, @Lightn1ng and @ashyx.

All right, because I can't leave well enough alone....
I got WiFi up and working. Tablet still stable and working. Wheeeee.... No GAPPS, though.
Downloaded GAPPS, second-smallest package from opengapps- only 128M (5.1 ARM package). Downloaded it in Android, from the tablet! Tried to flash it in TWRP. Failed, tablet rebooted halfway (not even) through. Now it's bootlooping again...
I should've left well enough alone, and waited for someone. Have tried re-installing Resurrection Remix, but tablet keeps failing to flash. Might have to try and flash a different TWRP. I don't know...

Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?

Lightn1ng said:
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Click to expand...
Click to collapse
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!

daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
I'm running out of ideas!
Maybe somebody else with a T800 could backup their entire EMMC using
Code:
dd if=/dev/mmcblk0 of=/sdcard/full_nand_dump.bin
And you take the file on your tablet and do
Code:
dd if=/sdcard/full_nand_dump.bin of=/dev/mmcblk0
And restore YOUR efs folder using TWRP.
THIS IS A DANGEROUS OPERATION AND I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG!
---------- Post added at 08:01 PM ---------- Previous post was at 07:57 PM ----------
@ashyx Any more ideas before I go ahead with my evil world domination plan to recover this device?

I wouldnt carry out any risky operations until a full backup can be made with twrp or you may end up with an unrecoverable device.
If twrp cannot backup the system partition then there is an issue with the partition.
Try backup again and post the recovery log, it may contain some relative information.

I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.

Exactly the same issue on my LTE version.
Samsung support just asked me 230€ for a new motherboard.
I refused to repair. I think it is related to nand memory..

Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.

srfairhurst said:
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
Click to expand...
Click to collapse
Why not just update to Marshmallow? Absolutely no issues for me.

ashyx said:
Why not just update to Marshmallow? Absolutely no issues for me.
Click to expand...
Click to collapse
Now i figured out its the wifi thats causing the problem i will update to android 6.01 or if i can find a good custom rom il risk that.

daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
DrinkSlinger said:
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Click to expand...
Click to collapse
Hello,
and the rest of story??
i can flash TWRP in download mode, and i can intall zip by TWRP , the lineage rom,
but, cant odin flash official md5 file, it stucks on logo.