Database Users

MAC address changing after reboot...

Just got my Nexus 10 back from RMA for the constant buzzing sound, but now my Mac address keeps changing after every reboot -_-
I use a WiFi Mac filter.

Anyone ?

That sounds nuts, and kinda cool - can you post a couple screen shots?

bigmatty said:
That sounds nuts, and kinda cool - can you post a couple screen shots?
Click to expand...
Click to collapse
BEFORE:
{
"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"
}
AFTER:

That is insane!
Its like a "super hacker" tablet!
But in interest of fixing it, have you tried either facory wipe or complete re-install of the OS?

bigmatty said:
That is insane!
Its like a "super hacker" tablet!
But in interest of fixing it, have you tried either facory wipe or complete re-install of the OS?
Click to expand...
Click to collapse
I did more research on the matter, and some people said it was the kernel which could be fixed by placing a code somewhere. I don't know how lol.
Also the guy I did research on was saying that his MAC address started with 00:90:4c then random string every reboot!
I tried the factory wipe, and the same thing keeps happening.
How do I do a re-install of the OS? I think that will do it.

This actually should not be possible, given the MAC address is a physical attribute (although ofc you could use software to mask it). Guess your kernel must be reading it wrong. To my knowledge, it's not like 2.4GHz/5GHz have separate MACs.

Rirere said:
This actually should not be possible, given the MAC address is a physical attribute (although ofc you could use software to mask it). Guess your kernel must be reading it wrong. To my knowledge, it's not like 2.4GHz/5GHz have separate MACs.
Click to expand...
Click to collapse
I know this already lol, so how do I fix it?

Chocobo87 said:
I know this already lol, so how do I fix it?
Click to expand...
Click to collapse
Depends. Nothing stock should be acting up like that, so you could try a backup/factory reset, or if you're en route to root, then flashing a different kernel would probably help.

Rirere said:
Depends. Nothing stock should be acting up like that, so you could try a backup/factory reset, or if you're en route to root, then flashing a different kernel would probably help.
Click to expand...
Click to collapse
Yeah I did a back/factory reset already. I don't really like rooting because I don't know how to maximize the benefits.
Send back to RMA? lol
OR maybe root and unroot back to stock?

Let me dig up the correct links on how to re-install the OS. Its not the same as just a wipe...
Be back soon....
---------- Post added at 03:18 PM ---------- Previous post was at 02:42 PM ----------
bigmatty said:
Let me dig up the correct links on how to re-install the OS. Its not the same as just a wipe...
Be back soon....
Click to expand...
Click to collapse
Ok, here is a post I did that should contain or link you to everything you need to know. If there's problems let us know!
http://forum.xda-developers.com/showpost.php?p=38995903&postcount=2

bigmatty said:
Let me dig up the correct links on how to re-install the OS. Its not the same as just a wipe...
Be back soon....
---------- Post added at 03:18 PM ---------- Previous post was at 02:42 PM ----------
Ok, here is a post I did that should contain or link you to everything you need to know. If there's problems let us know!
http://forum.xda-developers.com/showpost.php?p=38995903&postcount=2
Click to expand...
Click to collapse
Thanks!

bigmatty said:
Let me dig up the correct links on how to re-install the OS. Its not the same as just a wipe...
Be back soon....
---------- Post added at 03:18 PM ---------- Previous post was at 02:42 PM ----------
Ok, here is a post I did that should contain or link you to everything you need to know. If there's problems let us know!
http://forum.xda-developers.com/showpost.php?p=38995903&postcount=2
Click to expand...
Click to collapse
So am I only doing the 2nd link? Just download the SDK then reload it?

Chocobo87 said:
So am I only doing the 2nd link? Just download the SDK then reload it?
Click to expand...
Click to collapse
The first link in that post really is just saying to make sure you have the most recent updates to the drivers and SDK, as these are the tools with which to perform the task. Some people had old versions already installed, so its also a reminder to make sure they are updated. Some aspects of the SDK prompt people to update, but running the SDK manager to force the update check is the best bet.
Then yeah, the second link has most of the true steps/content to do the re-install.

bigmatty said:
The first link in that post really is just saying to make sure you have the most recent updates to the drivers and SDK, as these are the tools with which to perform the task. Some people had old versions already installed, so its also a reminder to make sure they are updated. Some aspects of the SDK prompt people to update, but running the SDK manager to force the update check is the best bet.
Then yeah, the second link has most of the true steps/content to do the re-install.
Click to expand...
Click to collapse
Well I'm somewhat sure that the SDK is the latest because I just got it back from RMA, and they put a new MOBO in it.
Thanks!

Chocobo87 said:
Well I'm somewhat sure that the SDK is the latest because I just got it back from RMA, and they put a new MOBO in it.
Thanks!
Click to expand...
Click to collapse
A little confusion - the SDK is the software development kit, so its just the software you have on your PC. (Not related to the firmware or anything on your tablet its self.)
For example, if you never had it on your PC you'd get it at http://developer.android.com/sdk/
But then people don't realize you should still run the updater for that title, because it can have very recent updates.
You have to use a Windows executable in the process called fastboot.exe
Some old versions of fastboot.exe don't have all the features that the newer fastboot.exe's do...
:good:

bigmatty said:
A little confusion - the SDK is the software development kit, so its just the software you have on your PC. (Not related to the firmware or anything on your tablet its self.)
For example, if you never had it on your PC you'd get it at http://developer.android.com/sdk/
But then people don't realize you should still run the updater for that title, because it can have very recent updates.
You have to use a Windows executable in the process called fastboot.exe
Some old versions of fastboot.exe don't have all the features that the newer fastboot.exe's do...
:good:
Click to expand...
Click to collapse
Yeah I'm not that good when it comes to these things. I know this is kind of asking a lot, but could you make a step by step to what I need to do? For example, 1. download SDK tool, 2. update tool, 3. stop being a noob lol
Thanks
EDIT: I downloaded the tool, and I don't know what I am supposed to do...
I'm looking at the 2nd steps from styckx, and I don't know where the tool comes into play
EDIT2: https://www.youtube.com/watch?v=b7W3bFNdJ8I Followed this video, and my MAC address still is a shape shifter -_-

Chocobo87 said:
Yeah I'm not that good when it comes to these things. I know this is kind of asking a lot, but could you make a step by step to what I need to do? For example, 1. download SDK tool, 2. update tool, 3. stop being a noob lol
Thanks
EDIT: I downloaded the tool, and I don't know what I am supposed to do...
I'm looking at the 2nd steps from styckx, and I don't know where the tool comes into play
EDIT2: https://www.youtube.com/watch?v=b7W3bFNdJ8I Followed this video, and my MAC address still is a shape shifter -_-
Click to expand...
Click to collapse
Glad you made it through the process - bummer it didnt fix it though! It is a pretty cool error, but certainly a lotcooler just to read about and not actually be the owner of! Good luck!

bigmatty said:
Glad you made it through the process - bummer it didnt fix it though! It is a pretty cool error, but certainly a lotcooler just to read about and not actually be the owner of! Good luck!
Click to expand...
Click to collapse
Thanks for everything! I'm going to RMA it again I guess lol.

Chocobo87 said:
Thanks for everything! I'm going to RMA it again I guess lol.
Click to expand...
Click to collapse
Have you checked out on the network to see if it really is changing? Most wifi routers will report the mac addresses of connected devices.
Alan

This is oh so true..............

{
"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"
}

True indeed and worth a thanks. When I had the S3, the very first thing I made sure I had beside a nandroid, was an EFS backup.

I flash the BTU rom when it was still using the old Radio version.. I let it update using KIES.. and when I saw.. I was running the new version.. and had no backup of my EFS..
now I have several backups of it.. so I believe I'm ok.. but I can never go back..
and this was not caused by a lack of reading the stick posts :crying:

DiReis said:
this was not caused by a lack of reading the stick posts :crying:
Click to expand...
Click to collapse
Well it's discussed at length in the sticky posts, so if it wasn't for lack if reading, you must have been one of the "early adopters" to flash MG* rom.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

Glad I'm not on Samsung anymore and have to deal with the EFS drama lol

rootSU said:
Well it's discussed at length in the sticky posts, so if it wasn't for lack if reading, you must have been one of the "early adopters" to flash MG* rom.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Like I said, I updated it using KIES.. I was not even reading XDA when I did it.. there was no warning.. I flashed an old, from 2012, ROM on the BTU CSC and after that started to update it using KIES, no custom recovery, no ODIN, nothing.
It was when I decided to use a modified touchwiz rom that I found this.. but that would be too late for me.. anyway.. my phone is working.. I have no problem with it and now I have several EFS backups..
---------- Post added at 02:35 PM ---------- Previous post was at 02:29 PM ----------
Theshawty said:
Glad I'm not on Samsung anymore and have to deal with the EFS drama lol
Click to expand...
Click to collapse
I wish I could do the same.. but.. compared to other ROMs we see floating around on other devices.. the modified ones we have here are pretty good..

DiReis said:
Like I said, I updated it using KIES.. I was not even reading XDA when I did it.. there was no warning..
Click to expand...
Click to collapse
There wouldn't need to be warnings. KIES is the official method to update the phone and KIES does not go backwards. Anything outside of KIES or official OTA is unofficial and not supported.
DiReis said:
no custom recovery, no ODIN, nothing.
Click to expand...
Click to collapse
I'm not sure of the relevancy of that.

rootSU said:
There wouldn't need to be warnings. KIES is the official method to update the phone and KIES does not go backwards. Anything outside of KIES or official OTA is unofficial and not supported.
I'm not sure of the relevancy of that.
Click to expand...
Click to collapse
I had no warning from the Forums.. that's what I meant.. gimme a break man.. It's almost like you want to say: you are stupid.. you earned this.. anyway..
also, regarding Odin and custom recovery.. usually those who uses that comes here.. and.. sometimes.. they READ.. like I did when I started flashing custom ROMs on my S3
peace man..

If Kies didn't throw out any warnings, then OP really isn't to blame.

DiReis said:
I had no warning from the Forums.. that's what I meant.. gimme a break man.. It's almost like you want to say: you are stupid.. you earned this.. anyway..
Click to expand...
Click to collapse
Not at all. If you're using KIES, none of this is relevant. That's all I'm saying. You wouldn't need warning because it doesn't affect you.
DiReis said:
sometimes.. they READ
Click to expand...
Click to collapse
Only sometimes. ...and that's what this thread is about.
DiReis said:
peace man..
Click to expand...
Click to collapse
Peace. I still don't understand your argument though.

rootSU said:
Not at all. If you're using KIES, none of this is relevant. That's all I'm saying. You wouldn't need warning because it doesn't affect you.
Only sometimes. ...and that's what this thread is about.
Peace. I still don't understand your argument though.
Click to expand...
Click to collapse
I totally agree with OP and with you.. my arguments are: I was not aware of this issue because I was running the stock rom and it updated without I knowing that this was going to happen, just that
and I wish I was following XDA forums, because I would be able to predict that and make a backup.. just that
I believe I might not be the only user on that position here on the forums.. we started modding after the stock ROM was installed by Sammy on our phones..

When I bought my phone and it supposed to deliver at my office after 2 days. within 2 days I learned and downloaded almost everything which was necessary. I was able to do that ONLY BECAUSE OF this good forum. and I have never had any problems with my phone. I am keep flashing my phone every time someone will release new ROM with good features. and kernels as well.
So I also totally agree with OP...:laugh::angel:

I literally just got an ATT OTA for 6.0.1.

I will install when it is convenient and report back.

Can you grab a copy and host it somewhere?

{
"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"
}

gollito said:
Can you grab a copy and host it somewhere?
Click to expand...
Click to collapse
really not sure how to do that and time is not on my side. lol

below is the changelog:
http://www.att.com/esupport/article.html#!/wireless/KB425950
Upgrade Device Software for the Motorola Nexus 6 (XT1103)
Instructions :
Update summary
Effective January 13, 2016 Motorola / Google released an Android (6.0.1) update for the Nexus 6 (XT1103) via a rolling Google Over the Air (GOTA) download. A Wi-Fi connection is not required.
What's changing?
OS upgrade to Android 6.0 Marshmallow
https://www.android.com/versions/marshmallow-6-0/
Performance Improvements
What to expect after the update
Although there should be no impacts to settings or data, we recommend that you back up your media files to a PC or using a favorite application (from the Play Store), prior to upgrading the software.
How to update
Google will use a "slow roll" GOTA campaign that starts with 5% of the ELIGIBLE users on day one and ramps up availability to 100% by the end of the first week.
If a user checks for the update via settings before their device is eligible for the rolling GOTA campaign they will see the message that indicates the device software is currently up to date. Users cannot pull the update via Settings.
Once eligible and in Wi-Fi coverage, the download will take place automatically and the user will then prompted to install the update.
Upon receipt of the GOTA notification the customer should:
Ensure the device is sufficiently charged
Connect to Wi-Fi
Select "Install"
How to verify the update
Select Settings from application tray or pull down menu.
Select the More box in the top right corner
Select About Device.
The following information displays:
Software Version: MMB29K
Upgrade file size: 755MB

gammite said:
really not sure how to do that and time is not on my side. lol
Click to expand...
Click to collapse
http://ausdroid.net/howto/capture-ota-update/
It requires computer access and adb installed and working so if you have that it would be a pretty quick thing (time not being on your side and all that is)
---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------
Whoo hoo! Just did a manual check on mine and have the notification too... let me see if I can pull the URL.

gollito said:
http://ausdroid.net/howto/capture-ota-update/
It requires computer access and adb installed and working so if you have that it would be a pretty quick thing (time not being on your side and all that is)
---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------
Whoo hoo! Just did a manual check on mine and have the notification too... let me see if I can pull the URL.
Click to expand...
Click to collapse
yeah, not gonna happen for me this time. i would have to download the sdk and its one gig.

LMY48Z -> MMB29K Link: https://android.googleapis.com/pack...igned-shamu-MMB29K-from-LMY48Z_full_radio.zip
---------- Post added at 06:24 PM ---------- Previous post was at 06:19 PM ----------
gammite said:
yeah, not gonna happen for me this time. i would have to download the sdk and its one gig.
Click to expand...
Click to collapse
No sweat. Since I happened to be at my computer I was able to pull it. Link is in my other post.

started the upgrade and the stupid att intro screen tone is still ear shattering loud. how could they not fix that???
stuck on optimizing apps for the time being.

It's about time they did it. They literally skipped the entire 6.0 update. Felt sorry for att users lol.

My phone had been running fine but felt sluggish at times. This feels so much snappier. Not sure if it is the cache flush or the upgrade.... Or both. Either way it feels nice. Curious how the battery life is after a full day running it.

Anyone getting another OTA for MMB29S after receiving MMB29K?

gammite said:
started the upgrade and the stupid att intro screen tone is still ear shattering loud. how could they not fix that???
stuck on optimizing apps for the time being.
Click to expand...
Click to collapse
No idea. It drove me to unlock the bootloader, root, remove etc. Then revert to stock, factory image of 6.0.1.

@gammite @gollito
They using the 32R baseband?

gollito said:
LMY48Z -> MMB29K Link: https://android.googleapis.com/pack...igned-shamu-MMB29K-from-LMY48Z_full_radio.zip
---------- Post added at 06:24 PM ---------- Previous post was at 06:19 PM ----------
No sweat. Since I happened to be at my computer I was able to pull it. Link is in my other post.
Click to expand...
Click to collapse
hi guys, i have AT&T Nexus 6 XT1103 running stock LP 5.1.1 (LMY48Z) atm, rooted and TWRP'ed, i have some problem, i want to update to MM 6.0.1, already download the OTA above, but seems can't update via TWRP, what should i do? please be kind to help me, thanks in advance

Mine has been at Waiting to Download for a while now (like 30 minutes). Should I be worried?

ecko no yaro said:
hi guys, i have AT&T Nexus 6 XT1103 running stock LP 5.1.1 (LMY48Z) atm, rooted and TWRP'ed, i have some problem, i want to update to MM 6.0.1, already download the OTA above, but seems can't update via TWRP, what should i do? please be kind to help me, thanks in advance
Click to expand...
Click to collapse
Would have to be a flashable zip to use with TWRP and that isn't.

Does this have the Dec or Jan security update? I have an unlocked Google version on AT&T. I was able to get the 6.0.1 and Dec security update before installing my ATT sim. No updates since even if I remove the SIM and stay on Wifi. Don't understand why I can't pull the Jan security update since I thought Google pushed those. I have a friend on 5X on ATT that has received it.

Only December update.
Good news is you can sideload the January update however!

Tab 4 SM-t337a Lollipop 5.1.1 Brick Problem?

Hello all - I have spent the last several days searching the web for a solution and I fear I may be stuck. From what I can gather, there is no stock firmware image of 5.1.1 that I can use on my t337a Tab to restore to factory. I installed KingoRoot from the play store and then tried to install Xposed Framework. This is when all hell broke loose. I am not familiar with android as I am an ios guy and admittedly did not spend enough time researching. I now must defer to the world and accept the flaming that will almost certainly ensue. Here is the info I have:
Lollipop 5.1.1 was the starting point.
SM-t337a tab 4 8"
Knox Warranty 0x0 (not sure if that matters)
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Qualcomm Secureboot: Enable (csb)
RP AWREV: s1, t2, r1, a2, p1
Secure Download: Enable
UDC Start
Sorry if that means nothing but I want to be thorough if anyone is willing to help. I have tried the LP Boot Fix with no luck. I boot to the AT&T logo and after a few secs it locks up and sits there. I have attempted to downgrade to KK but the write failed (auth). I believe I need to flash a pit file? but before I jump back in, I thought I would consult some people more educated than I am. My understanding is there may be a way to take it to a retailer and have them reflash but that would be admitting defeat.
Thanks in advance for any help offered. If more info is needed, I will get it promptly.
This may be in the wrong place. Can a mod move it where it should be? Sorry

Man, I must be screwed! I really thought I would be able to get out of this one. Is there not an expert out there that can point me in the right direction?

I had the same exact problem basically.
Here is how I fixed it:
I found a stock rom here: http://forum.xda-developers.com/tab-4/general/links-galaxy-tab-4-official-lollipop-5-t3102844
And I used this guide here: https://androidmtk.com/flash-samsung-stock-rom-using-odin.
This will require a PC, and a way to connect your device to it.

grupey said:
Here is how I fixed it:
I found a stock rom here: http://forum.xda-developers.com/tab-4/general/links-galaxy-tab-4-official-lollipop-5-t3102844
And I used this guide here: https://androidmtk.com/flash-samsung-stock-rom-using-odin.
This will require a PC, and a way to connect your device to it.
Click to expand...
Click to collapse
Awesome! You have a SM-T337A as well? My biggest issue is AT&T locking it down.

restore back to stock rom
I have a t337a also and restoring back to stock rom fixed mine. I really wish there were a way to root and install rom on this thing. I have now been searching for another tablet that I can root. Seems like such a waste. I like this device so it's really frustrating at thus point and not an easy conversation with the wife why I need amother tablet.

RoadwarriorsLive said:
I have a t337a also and restoring back to stock rom fixed mine. I really wish there were a way to root and install rom on this thing. I have now been searching for another tablet that I can root. Seems like such a waste. I like this device so it's really frustrating at thus point and not an easy conversation with the wife why I need amother tablet.
Click to expand...
Click to collapse
Did that link to the stock rom? I thought that was an ota that I could not use. Do you have a link to the stop rom you used?

He must have never updated to Lollipop. Once you do that, your screwed. There IS NO OFFICIAL FIRMWARE FOR THIS DEVICE RUNNING LOLLIPOP!!!! You can bring it to a Samsung Service Center in Best Buy but once they see the custom lock on your boot screen, they will know that you messed around with it, and they will not flash it. From what they told me, once your tablet goes into custom kernel status, their software will not be able to restore the firmware. Not sure if this last part is true, but what is true is that there is NO FIRMWARE ONLINE ANYWHERE FOR THIS DEVICE RUNNING LOLLIPOP. I've been screwed for several months now over this same issue. I went on E-bay and bought the unlocked T-mobile version of the Tab 4 which does have the software available. I will NEVER EVER BUY ANOTHER AT&T DEVICE EVER!!!!! I will have AT&T service but I will use a T-mobile device.

This is what I see when I try that method.
{
"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"
}

That's a update file and you must be on stock unrooted Kit Kat to flash that. That's why you are getting the status 7 error. Like I said, you are screwed like everyone else. Your only hope is bringing it to best buy and u have better luck than I did.
---------- Post added at 02:49 AM ---------- Previous post was at 02:48 AM ----------
jmack420 said:
This is what I see when I try that method.
Click to expand...
Click to collapse
That's a update file and you must be on stock unrooted Kit Kat to flash that. That's why you are getting the status 7 error. Like I said, you are screwed like everyone else. Your only hope is bringing it to a best buy store and maybe u will have better luck than I did.

help
i have same exact problem after nkingo root please any pro xda menber help us i like that tab plus im poor ty in advance

jorgiepr said:
i have same exact problem after nkingo root please any pro xda menber help us i like that tab plus im poor ty in advance
Click to expand...
Click to collapse
I have created a new thread here: http://forum.xda-developers.com/tab-...-4-sm-t3439252 OFFICIAL FIRMWARE FOR THE AT&T TAB 4.
---------- Post added at 11:27 PM ---------- Previous post was at 11:19 PM ----------
I have deleted the other files from my Google Drive and replaced it with one file. I have created a new thread here: http://forum.xda-developers.com/tab-...-4-sm-t3439252 OFFICIAL FIRMWARE FOR THE AT&T TAB 4.
---------- Post added at 11:45 PM ---------- Previous post was at 11:27 PM ----------
I have deleted the other files from my Google Drive and replaced it with one file. I have created a new thread here: http://forum.xda-developers.com/tab-...-4-sm-t3439252 OFFICIAL FIRMWARE FOR THE AT&T TAB 4.

I am proud to present the official firmware for the AT&T Tab 4. I have created a new thread here: http://forum.xda-developers.com/tab-...-4-sm-t3439252 OFFICIAL FIRMWARE FOR THE AT&T TAB 4.

MichaelSaya said:
I am proud to present the official firmware for the AT&T Tab 4. I have created a new thread here: http://forum.xda-developers.com/tab-...-4-sm-t3439252 OFFICIAL FIRMWARE FOR THE AT&T TAB 4.
Click to expand...
Click to collapse
So where is it now?

jmack420 said:
So where is it now?
Click to expand...
Click to collapse
Sorry, my bad. It's located here: http://forum.xda-developers.com/tab-4/general/official-att-lollipop-firmware-tab-4-sm-t3439252

it loaded but I'm still stuck at AT&T logo on boot. did I do something wrong?
nvm, it finally came up. Thanks so much for the help!

jmack420 said:
it loaded but I'm still stuck at AT&T logo on boot. did I do something wrong?
nvm, it finally came up. Thanks so much for the help!
Click to expand...
Click to collapse
Yeah, when you do a factory reset or flash firmware, it will take longer to boot. Its like a new device, booting for the first time.

I am Tickled
MichaelSaya said:
Yeah, when you do a factory reset or flash firmware, it will take longer to boot. Its like a new device, booting for the first time.
Click to expand...
Click to collapse
Most excellent finally it worked perfectly.Your the Man thank you Thank you.

Possible modem problems?

Hi,
I've tried a few different roms and almost all of them I've had random reboots. Sometimes once a day and sometimes several times a day. I don't understand those logs but I've saved a few of them to my Dropbox after random reboots. One common thing is that every log has some lines at the end that says modem fatal error. Since I still got warranty left I would like to know are these signs of broken modem or if someone could say what is causing those random reboots.
I'm running almost stock roms always. Only rooted, no greenify or different kernels etc.
Also I haven't noticed any similarities when those random reboots happen. Might be when phone is unused on the table or when scrolling Facebook or using browser. Totally random in my opinion.
Here's the link for Dropbox folder. There's a few logs and I really appreciate it if someone has time to check those.
https://www.dropbox.com/sh/twh4u437qfva518/AADuK5u9UEmEal-VzkdIK0oMa?dl=0

Try a factory reset.

Thanks for the tip. Done that too few times though and the random reboots still continues.

dont know if this is related or not but I have had problems with selecting a different network manually on all roms apart from OOS. I suspect this is something to do with the modem.

demongokul said:
Try a factory reset.
Click to expand...
Click to collapse
dude read first.
He said he has tried various ROM's. He has obviously done factory resets more than once.
this customer care like approach is not acceptable here.
have you worked at a call centre? seems highly likely.
Sorry OP for going off- topic.

control freak said:
dude read first.
He said he has tried various ROM's. He has obviously done factory resets more than once.
this customer care like approach is not acceptable here.
have you worked at a call centre? seems highly likely.
Sorry OP for going off- topic.
Click to expand...
Click to collapse
Never worked in a call center. Overlooked the message from OP.
---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------
NoobMonkey said:
Thanks for the tip. Done that too few times though and the random reboots still continues.
Click to expand...
Click to collapse
Strange.. Sorry I have no idea.

More logs added to op link. Latest from today and running cm14 1710 build with Pico open gapps.
All ideas are welcome.

I'm having similar reboot issues with CM14. I don't have any issues with CM13 so I just reverted back to that. I was hoping it would just get ironed out as the ROM developed, but I'll try and save a log after the next CM14 update to see if they have the same error (not that I would know what to do with that information).

I have the same problem.
http://forum.xda-developers.com/oneplus-2/help/random-reboots-overclocked-kernels-t3446631
I posted a method I did to try to solve it. It did work. But now its kinda messed up again.
My theory is that it has to do with the battery not pushing out enough amount of voltage for the processor. If you're not running on a overclocked kernel I would still try it.
Best of luck!
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
Also, just for the sake of asking.
Did your phone at any point mess up that you had to use the Qualcomm flashing tool?
When did you buy your OP2?
Have you done any kinda hex-editing to the bootloader?

macymagiska said:
I have the same problem.
http://forum.xda-developers.com/oneplus-2/help/random-reboots-overclocked-kernels-t3446631
I posted a method I did to try to solve it. It did work. But now its kinda messed up again.
My theory is that it has to do with the battery not pushing out enough amount of voltage for the processor. If you're not running on a overclocked kernel I would still try it.
Best of luck!
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
Also, just for the sake of asking.
Did your phone at any point mess up that you had to use the Qualcomm flashing tool?
When did you buy your OP2?
Have you done any kinda hex-editing to the bootloader?
Click to expand...
Click to collapse
I have stock kernel and haven't done any editing on bootloader. At least I am aware of. And no, I didn't have to use Qualcomm flashing tool.
If I remember correctly, I bought my phone just over a year ago. Have to try tomorrow that link u posted.

Well, if the logs are saying fatal_modem. Have you tried to flash the latest modem available from OOS 3.1.0?
Also you must realize that CM 14 is still under development, so it might be prone to bugs.

Would flashing a different modem fix random shut downs and crashes? My phone does the random rebooting thing except it doesn't reboot on its own, which others have seemed to experience too. I am also unable to manually select a network, as previously mentioned in this thread. Where could I find a new modem to flash? Here's an image of my about screen with my modem version.
{
"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"
}