Develop Bugs

Warning: Non-noobs get it wrong too - bricked SGS3

Although I wouldn't term myself a pro at all, I am not a noob when it comes to rooting and installing other ROMs. I have rooted many of my Android phones over the years and have diligently read and re-read posts when it comes to rooting and installing ClockworkMod recovery and other ROMs.
Last week, I made a big boo-boo!
I searched for "Sprint SGS3 alternate ROMs" and found a CNet article (http://reviews.cnet.co.uk/mobile-phones/top-5-samsung-galaxy-s3-custom-roms-50009440/) listing the different ROMs. I downloaded a couple (Hawkish and Energy) and promptly tried to install them. I got some error message in CWM. I then rebooted after cleaning caches, dalvik etc.
My phone wouldn't start at all!!!
I tried all the keypresses to get things working but absolutely nothing. The unit wouldn't turn on even with a separately fully charged battery. I tried to borrow a USB Jig from a user in this post (http://forum.xda-developers.com/showthread.php?t=1869203) but no-one was able to help. As the phone was my only phone (no landline) I was readying myself to pay the $60 that one of the other sites charged to JTag the unit.
Before I did that, I decided to take it in to Sprint, and told the technician I made a mess up. They didn't ask anything about what I did and took it to the back for about half an hour. They weren't able to do anything as the unit didn't switch on, but said that I could get a replacement for $50.
I did that and a few days later they swapped out the non-working unit for a working one. I was expecting to pay a whole lot more.
I learned the lesson the hard way: even if I search for "Sprint" the results aren't necessarily going to be for my unit. I should have read (and re-read!) the posts a whole lot more clearly about the other ROMs - they were not for the Sprint unit.
I hope my hard lesson will help others be a wee bit more cautious - even if you have been customizing a long time!

This is about the 100th post this month of people flashing roms for other carriers on a Sprint S3. A simple search in the Q&A would have probably alerted you to the facts.
Transmitted with a portable device using Xparent Blue Tapatalk 2

I *do* realize that I flashed the wrong ROM. The point of my post was to illuminate that it's not only noobies who get things wrong.
Even though I read what I thought was for Sprint, my presumption got in the way and I didn't realize until it was too late that it was not the ROM in the Sprint section of Http://www.xda-developers.com/ that I thought I was reading about.
I took responsibility for my mistake and paid the money to rectify my error.
I am hoping that my misfortune with be a cautionary tale for others to double (and triple) check.
Just because we've done things successfully many times before doesn't mean we're avert to the same errors as noobies.

IconBoy said:
I *do* realize that I flashed the wrong ROM. The point of my post was to illuminate that it's not only noobies who get things wrong.
Even though I read what I thought was for Sprint, my presumption got in the way and I didn't realize until it was too late that it was not the ROM in the Sprint section of Http://www.xda-developers.com/ that I thought I was reading about.
I took responsibility for my mistake and paid the money to rectify my error.
I am hoping that my misfortune with be a cautionary tale for others to double (and triple) check.
Just because we've done things successfully many times before doesn't mean we're avert to the same errors as noobies.
Click to expand...
Click to collapse
If you would've read more carefully you wouldn't have made that mistake... noob! Jk
SPRINT GS3 FAQ

Feel bad but at the same time I dont. You should know a bit better to be sure that you can use that ROM/kernel/zip etc. If you doubt yourself ask in the thread or forum. We all don't know everything there is to rooting and flashing
http://i1202.photobucket.com/albums/bb374/TexasEpic/ThePeoplesROM-KennyGlass123/daniel4653.png
Odexed Blue by Strong Steve + Ktoonz w/ Team Kernelizers tweaks

In the cnet article it had this in the "getting started section"
Just bear in mind that if your S3 handset is not version number I9300 -- and it almost certainly is if you bought it in the UK -- then bad things can happen. So it's worth quickly checking your phone's settings before proceeding.
Click to expand...
Click to collapse
Discuss...
Sent from my SPH-L710 using xda app-developers app

I have to give you credit Iconboy for taking responsibility and paying for a new phone. Even though you messed up you admitted it. A lot of people that have done the same thing have posted things like "can I throw my phone in a river" or "can I just tell sprint that the OTA broke my phone". Thanks for doing it right.

metalfan78 said:
I have to give you credit Iconboy for taking responsibility and paying for a new phone. Even though you messed up you admitted it. A lot of people that have done the same thing have posted things like "can I throw my phone in a river" or "can I just tell sprint that the OTA broke my phone". Thanks for doing it right.
Click to expand...
Click to collapse
Yeah I agree. I don't know why people are bashing him. He maned up and payed for a replacement phone and now he is just letting other people know what can happen.
Sent from my SPH-L900 using xda premium

I did the same thing with my S3 about a month ago, Was on a flashing frenzy and didn't read enough about the rom i was flashing. After the flash my phone wouldn't do anything at all, just a paperweight. Took it into sprint and paid for a new one. Mistake learned, its part of being human.

musclehead84 said:
Yeah I agree. I don't know why people are bashing him. He maned up and payed for a replacement phone and now he is just letting other people know what can happen.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
No one is bashing him, just having some fun at his expense, but you're right, thanks for doing the right thing op!
SPRINT GS3 FAQ

Like others have said, props for owning your mistake. However, the "noob" label applies to you, whether you think so or not. There were so many signs you were walking down the wrong path (including an explicit warning on the very page) the very first being that you were on a .uk website. I'm not posting this about that though, I just don't seem to understand why so many people feel the need to venture away from xda to acquire ROMs, this site if full of great ROMs made by great devs, not sure what more people need to end up flashing things they find on international news sites. Yes, there are other established sites, but usually they overlap with this site. That is to say, if there's something awesome happening somewhere else, you'll hear about it here (with a few exceptions).

Whether I am classified as a "noob" or not ... I have flashed custom ROMs on four or five different Android phones over the years.
The Motorola Photon was one where I thought I had a paperweight (nope...not an int'l ROM that time - Ha! Ha!) but because of XDA, I was able to get it working again after many errors. Decent little phone that one.
My error, my expense, my fault on the SGS3. Thankfully I have a working unit and can put the old EVO in the drawer as a backup - it is sloooow!

IconBoy said:
Whether I am classified as a "noob" or not ... I have flashed custom ROMs on four or five different Android phones over the years.
The Motorola Photon was one where I thought I had a paperweight (nope...not an int'l ROM that time - Ha! Ha!) but because of XDA, I was able to get it working again after many errors. Decent little phone that one.
My error, my expense, my fault on the SGS3. Thankfully I have a working unit and can put the old EVO in the drawer as a backup - it is sloooow!
Click to expand...
Click to collapse
Glad you got it worked out. Its not easy admitting (and on the internet to say the least) that you had made a mistake even as a seasoned flasher. Its never easy to admit an error, at all
I agree with metalfan above and I applaud you, you made a mistake and you paid for it, lesson learned

Well... Don't re-read is for noobs. Sorry if that hurts you.
Sent from my SPH-L710

IconBoy said:
Whether I am classified as a "noob" or not ... I have flashed custom ROMs on four or five different Android phones over the years.
The Motorola Photon was one where I thought I had a paperweight (nope...not an int'l ROM that time - Ha! Ha!) but because of XDA, I was able to get it working again after many errors. Decent little phone that one.
My error, my expense, my fault on the SGS3. Thankfully I have a working unit and can put the old EVO in the drawer as a backup - it is sloooow!
Click to expand...
Click to collapse
You may not be a "noob" in the technical sense of that term, but as you already know, the mistake you made was an amateurish one. For one, you were on a .uk website, and second, the very article mentions that you have to be mindful of your model number and specifically mentions buying in the UK. There were at least 3 checkpoints in that article that should have prompted further scrutiny on your part. I do commend you for taking responsibility for your actions and for you PSA to be careful about what you flash, and I do understand how you got tripped up. This is probably the first Android phone that was released to multiple carriers worldwide. Also, what I would like to see from devs is a conspicuous message in the OP of their ROM about specifically which carrier/version their ROM is for. Often that is not mentioned.

So let me prose this question to everyone calling him a noob (including our devs) - why don't devs write their install scripts to read the current build.prop to check for the correct model before the wipe & install begins? If this is happening hundreds of times per month, a pretty small amount of scripting could probably stop this from happening 99% of the time.
Sent from my SPH-L710 using xda app-developers app

rocket321 said:
So let me prose this question to everyone calling him a noob (including our devs) - why don't devs write their install scripts to read the current build.prop to check for the correct model before the wipe & install begins? If this is happening hundreds of times per month, a pretty small amount of scripting could probably stop this from happening 99% of the time.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Good point. Bad code leads to bad problems. And its actually a very simple line of code in the updater-script that would abort, but increasingly people are dropping that habit and changing to a no-check install
Code:
assert(getprop("ro.product.device")=="DEVICE_NAME" && getprop("ro.product.board")=="DEVICE_NAME")

IconBoy said:
Although I wouldn't term myself a pro at all, I am not a noob when it comes to rooting and installing other ROMs. I have rooted many of my Android phones over the years and have diligently read and re-read posts when it comes to rooting and installing ClockworkMod recovery and other ROMs.
Last week, I made a big boo-boo!
I searched for "Sprint SGS3 alternate ROMs" and found a CNet article (http://reviews.cnet.co.uk/mobile-phones/top-5-samsung-galaxy-s3-custom-roms-50009440/) listing the different ROMs. I downloaded a couple (Hawkish and Energy) and promptly tried to install them. I got some error message in CWM. I then rebooted after cleaning caches, dalvik etc.
My phone wouldn't start at all!!!
I tried all the keypresses to get things working but absolutely nothing. The unit wouldn't turn on even with a separately fully charged battery. I tried to borrow a USB Jig from a user in this post (http://forum.xda-developers.com/showthread.php?t=1869203) but no-one was able to help. As the phone was my only phone (no landline) I was readying myself to pay the $60 that one of the other sites charged to JTag the unit.
Before I did that, I decided to take it in to Sprint, and told the technician I made a mess up. They didn't ask anything about what I did and took it to the back for about half an hour. They weren't able to do anything as the unit didn't switch on, but said that I could get a replacement for $50.
I did that and a few days later they swapped out the non-working unit for a working one. I was expecting to pay a whole lot more.
I learned the lesson the hard way: even if I search for "Sprint" the results aren't necessarily going to be for my unit. I should have read (and re-read!) the posts a whole lot more clearly about the other ROMs - they were not for the Sprint unit.
I hope my hard lesson will help others be a wee bit more cautious - even if you have been customizing a long time!
Click to expand...
Click to collapse
I'd say your a noob. Title is wrong. Lol.
.co.uk <----- not even us website.
Did you see "sprint" or d2spr any where? No.
Derp.
Sent from my SPH-L710 using xda premium

rocket321 said:
So let me prose this question to everyone calling him a noob (including our devs) - why don't devs write their install scripts to read the current build.prop to check for the correct model before the wipe & install begins? If this is happening hundreds of times per month, a pretty small amount of scripting could probably stop this from happening 99% of the time.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
How about a counter point, if the noobs would read before flashing, it would stop this from happening 100% of the time! If you don't have time to read before trying to mod your device, you shouldn't be doing it in the first place...

Will always wonder why people find the right place just a second after they turn theirs phones into a fully functional brick.
Sent from my SPH-L710

Invasion of privacy

I was recently contacted by an old friend to help with an issue. He was a victim of privacy invasion on his S4, hidden instances of webcam and phone cameras, exporting of personal information, etc. Now he has come to me for help. I have looked at his logs and whatnots, but nothing really stands out. So, I am wondering if any of you have experienced the same problem? If yes, please provide me a complete list of all the apps you have installed on your device. Since I do not own an S4, it is hard for me to create the issue. The only answer is to get this community to pool together and get me the device (which would allow me to dev for the S4 and bring the greatness of the Lightning Zap! kernel), or for you guys that have experienced it, to help me find a common link.

thomas.raines said:
I was recently contacted by an old friend to help with an issue. He was a victim of privacy invasion on his S4, hidden instances of webcam and phone cameras, exporting of personal information, etc. Now he has come to me for help. I have looked at his logs and whatnots, but nothing really stands out. So, I am wondering if any of you have experienced the same problem? If yes, please provide me a complete list of all the apps you have installed on your device. Since I do not own an S4, it is hard for me to create the issue. The only answer is to get this community to pool together and get me the device (which would allow me to dev for the S4 and bring the greatness of the Lightning Zap! kernel), or for you guys that have experienced it, to help me find a common link.
Click to expand...
Click to collapse
Is there any more info you can give about it? I haven't noticed anything personally, but I also haven't been looking.
Would be nice to see you here on the S4 there, pal.

lordcheeto03 said:
Is there any more info you can give about it? I haven't noticed anything personally, but I also haven't been looking.
Would be nice to see you here on the S4 there, pal.
Click to expand...
Click to collapse
Hey man! How goes it? I would love to have an S4 but it's just not in my budget right now...but at about 600 bucks (with no contract) who can afford it...lol
Although, I am up for my new every 2 upgrade... but it is for AT&T, and I'm not sure of the compatibility between the i9500, and the AT&T model (not sure of the exact model number).
As for the invasion of privacy issue, I'm trying to get more details on it. But I'm really thinking the malicious code started on his PC and drifted to his phone. And if it's the trojan I am thinking, then it attacks usb devices by making all the contents of that device hidden and appearing as if everything was deleted. Easy to get rid of, and easy to fix provided you have admin level access. Oh, and it was specifically made to attack Windows 7, but can leak out to other versions of Windows. Reason #1 to switch to Linux: Hackers HATE Windows and Bill Gates! lol

thomas.raines said:
Hey man! How goes it? I would love to have an S4 but it's just not in my budget right now...but at about 600 bucks (with no contract) who can afford it...lol
Although, I am up for my new every 2 upgrade... but it is for AT&T, and I'm not sure of the compatibility between the i9500, and the AT&T model (not sure of the exact model number).
As for the invasion of privacy issue, I'm trying to get more details on it. But I'm really thinking the malicious code started on his PC and drifted to his phone. And if it's the trojan I am thinking, then it attacks usb devices by making all the contents of that device hidden and appearing as if everything was deleted. Easy to get rid of, and easy to fix provided you have admin level access. Oh, and it was specifically made to attack Windows 7, but can leak out to other versions of Windows. Reason #1 to switch to Linux: Hackers HATE Windows and Bill Gates! lol
Click to expand...
Click to collapse
I mean, what were the indications? Like, what made your friend say "Man, I do believe my privacy is being invaded." You say nothing suspicious showed up in logs, the instances of camera and data exports, etc were all hidden... what gave the indication that it was happening?

A friend of mine recently had a very similar problem with his iPhone.
We quicly determined that the answer was that his phone was cloned using a scanner, which gave the bad guy power to hack into the device at the ESN level. Very hard to trace in any kind of logs, especially since the bad guy would have the ability to purge logs.
Your buddy might have someone similar. My friend was in Russian when this happened though, much less common in the US.

Skipjacks said:
A friend of mine recently had a very similar problem with his iPhone.
We quicly determined that the answer was that his phone was cloned using a scanner, which gave the bad guy power to hack into the device at the ESN level. Very hard to trace in any kind of logs, especially since the bad guy would have the ability to purge logs.
Your buddy might have someone similar. My friend was in Russian when this happened though, much less common in the US.
Click to expand...
Click to collapse
I asked him for more info and specifically what led him to believe this has happened. I am waiting for his reply. Here is th main snippet from his initial email:
I have been the victim of a very discreet but maddening invasion of privacy through my phone and also my PC and laptop computers via key logging, hidden instances of webcam and phone cameras, exporting of personal information, etc. I believe it to be a reoccurring problem via persistent data, local and cloud based storage, and corruption of my MBRs on most of my storage media. I know enough to be dangerous, but have yet to find any significant marker that points to faulty reflash process at least on my telephone.
Click to expand...
Click to collapse
He gave me some good logs, but I really don't have much to go on. With the statement about his MBR's, I think his computer was actually attacked and subsequently, his phone and possibly other usb devices have been compromised...

He has MBRs on most of his storage devices?
But I think he probably got Ratted on his computer, the guy controlling the computer saw he had an android phone and installed an android rat onto it when he plugged it in next.
Sent from my SGH-M919 using xda app-developers app

[Q] Successfully booted to TMobile SIM from AT&T ... now what?

I am S-On, AT&T 1.58 stock rooted (from Miller_kid's upload deodexed dated 5/15/2014). It took me close to 3 weeks just to get the SIM to recognize (eye-rolling expected here).
I guess my primary question is: can I install a Tmobile 5.02 mod (of course after doing a backup and wipe).
My secondary question is: does the bootloader need to be relocked for normal operation?
Sorry to sound so clueless, but I'm horrified at the prospect of the phone giving me that HTC ONE white screen blank stare and not doing anything else! All suggestions are greatly appreciated.

its such a lovely feeling to realize that you're not quite as clueless as you once thought you were.
I figured "what the hell ... the phone's been a brick for three weeks ... why should i give a **** what else i do to it now anyway?" And went to town with InsertCoin's incredibly reliable and stable mods ... Wow you guys are terrific and extremely responsive. $$$$ coming ur way!
so F - U At&T .... (and actually TMob can suck my ballz too, but what the hell ... they are carrying me at the mo, so ... )
It amazes me that after 15 years AT&T doesn't even bother to ask why I might be just cancelling my 2 line account ... maybe they actually realize they've been violating me without my permission every month for that long. I suggest that everyone tired of the rates they're being charged -- when u get ready to drop the carrier, go in person. That way you can at least have some fun and tell them that now that there is a person shaking your hand representing the company, you could (if you really wanted to be nasty) call the police and say you had been raped. there was physical contact, afterall.
Oh my what fun that could start!! The looks on faces would be utterly priceless. (see what kind of lunacy all this phone tension creates? madness. geez)

need help with this damn phone

I'll just put this simply. I've got a splitting headache and I've been staring at various web pages for hours trying to (unsuccessfully) unlock the bootloader on my g4 so I can install twrp and root the thing. I'm about ready to kill someone. don't know who, nobody is around.
anyway.. I need a guide on how to transform my LG G4 US99120c US Cellular mobile device running Android 6.0 Marshmallow from a battery-draining eyeball-paining bright white piece of techno-trash into a rooted device with custom recovery that I can use on a regular basis without experiencing severe migraines because I can't delete stuff off the SD card due to carriers being pricks about released phones.
yes, I've tried google. Yes, I've tried searching the forums. If I hadn't done that already I wouldn't be posting here. please don't waste my time with "try the search feature".. I'm here because this is my last viable option for getting the damn thing working right. Please don't just link me to some random instruction manual either. I have bad luck with links.
If anyone does write me with help, write it for an idiot. Normally I'm pretty good at picking things up quickly but I seem to have come down with something the past couple days so I'm also a bit under the weather.. right around the idiot quotient.
I don't want to downgrade, I don't want to install half a dozen things or flash my whatchamacallit (got arrested last time I did that). I want to root the device, and possibly install xposed so I can change everything thats sharp white to a dull black. I do not want to do anything else at all but make calls, text, watch vids, listen to music and play the occasional game.
Thank you very much for your time, and a colossal chunk of gratitude for anyone who wants to take up this task.
FTR: I'm a former samsung user, so if you need to make comparisons I suggest using those. I'll understand 'em.

Jofreidr said:
I'll just put this simply. I've got a splitting headache and I've been staring at various web pages for hours trying to (unsuccessfully) unlock the bootloader on my g4 so I can install twrp and root the thing. I'm about ready to kill someone. don't know who, nobody is around.
anyway.. I need a guide on how to transform my LG G4 US99120c US Cellular mobile device running Android 6.0 Marshmallow from a battery-draining eyeball-paining bright white piece of techno-trash into a rooted device with custom recovery that I can use on a regular basis without experiencing severe migraines because I can't delete stuff off the SD card due to carriers being pricks about released phones.
yes, I've tried google. Yes, I've tried searching the forums. If I hadn't done that already I wouldn't be posting here. please don't waste my time with "try the search feature".. I'm here because this is my last viable option for getting the damn thing working right. Please don't just link me to some random instruction manual either. I have bad luck with links.
If anyone does write me with help, write it for an idiot. Normally I'm pretty good at picking things up quickly but I seem to have come down with something the past couple days so I'm also a bit under the weather.. right around the idiot quotient.
I don't want to downgrade, I don't want to install half a dozen things or flash my whatchamacallit (got arrested last time I did that). I want to root the device, and possibly install xposed so I can change everything thats sharp white to a dull black. I do not want to do anything else at all but make calls, text, watch vids, listen to music and play the occasional game.
Thank you very much for your time, and a colossal chunk of gratitude for anyone who wants to take up this task.
FTR: I'm a former samsung user, so if you need to make comparisons I suggest using those. I'll understand 'em.
Click to expand...
Click to collapse
ill lay it on wasy for you......... you cant unlock bootloader. you cant install twrp and you cant root MM. not unless bootloader unlocked. wich your phone cant be unlocked..
root only on locked bootloader on LP.
there isnt a way and there will never be one.. to bypass and be able to install twrp..

well that explains why fastboot refuses to acknowledge the existence of the phone. I guess.
never say never tho m8, geohot should be proof enough of that for you. looks like I can't downgrade either.
guess I'll have to stick with my s5.

Jofreidr said:
well that explains why fastboot refuses to acknowledge the existence of the phone. I guess.
never say never tho m8, geohot should be proof enough of that for you. looks like I can't downgrade either.
guess I'll have to stick with my s5.
Click to expand...
Click to collapse
there was a bounty of like 3000 dollars to whoever unlock it.. no one did it.. i said i might never be one.. thats waht everyone says samething.

Last_kmsg: IOMMU DebugFS Support Enabled

Hello everyone,
Long time mystified lurker, first time poster.. before you jump my arse please know that I have searched the forums to the best of my abilities. I am only able to find answers regarding custom kernels/unrelated posts. I have an unrooted completely stock out of the box ATT carrier locked S20 Ultra 5g (SM-G988U) with the Snapdragon 865. Please forgive me because I am learning and doing my best to provide relevant information. But within my recovery logs for last_kmsg I get a big NOTICE stating tace_printk() is allocating extra memory and that IOMMU DebugFS has been enabled. I cannot seem to figure out why this notice is appearing and I cannot get any explanation from ATT or Samsung. I recent called ATT via 611, after being connected to a manager and laying out my question, I was hung up on and my sim card was no longer recognized. I tried putting my sim into a carrier unlocked moto g7 play and it also does not think I have inserted the sim. I had to go into the ATT store to purchase a new simcard and the new one works perfectly. My data was never turned off in my account and my sim card was supposedly still active according to the store employee.
Again guys, so sorry for the dummy talk... thanks for sticking with me so far!
This may or may not sound stupid but it appears I may have a virtual machine running on top of my android system?? I ran a GPU Benchmark and my GPU Load never increased from 0% and my CPU seemed to have been doing all the work.
I cannot get answers from XDA forum searches,, Googling, ATT, Samsung, employer and I am genuinely concerned because I work for a financial institution and at one point had my work email configured on this device. I handle lots of PII so I have been taking unpaid vacation to try to figure this out without much luck.
I have not and could not possibly cover everything I have tested/searched/noticed. I am basically either a lot dumber than the average bear or my internet searches are being filtered to make this troubleshooting extremely difficult. At this point I am going out of my comfort zone to post online for the first time ever on any forum so please be gentle with me. Also, I could literally talk for days about what I've done and what I have figured out these past couple weeks so PLEASE ask me questions if you have any. You can mock me and call me stupid, please just do so in a manner that details where I am going wrong.
Sorry for the crappy sentence structure and grammar... I was a sailor and not a college student for a reason! Thanks for any support you can provide!
Much love

so you went looking into device kmsg logs and found something u dont understamd and assume thats what killed ur sim card?
lol
thats normal output on many samsung devices.. its not anything nefarious.. not sure what u mean about a virtual machine running lol.. i suppose if u installed and set one up maybe ones running?
either way it sounds like ur device is fine/normal and ur just looking into stuff u dont quite understand.. and i can guarantee att or sammy reps etc know less than most ppl lol
that being said, sim cards can fail sometimes and need to b replaced.. ive had a few die randomly over the years.. it happens. It also indicates bad sim seeing as how it didnt work in ur other device eithet.

Bootsie needs help said:
Hello everyone,
Long time mystified lurker, first time poster.. before you jump my arse please know that I have searched the forums to the best of my abilities. I am only able to find answers regarding custom kernels/unrelated posts. I have an unrooted completely stock out of the box ATT carrier locked S20 Ultra 5g (SM-G988U) with the Snapdragon 865. Please forgive me because I am learning and doing my best to provide relevant information. But within my recovery logs for last_kmsg I get a big NOTICE stating tace_printk() is allocating extra memory and that IOMMU DebugFS has been enabled. I cannot seem to figure out why this notice is appearing and I cannot get any explanation from ATT or Samsung. I recent called ATT via 611, after being connected to a manager and laying out my question, I was hung up on and my sim card was no longer recognized. I tried putting my sim into a carrier unlocked moto g7 play and it also does not think I have inserted the sim. I had to go into the ATT store to purchase a new simcard and the new one works perfectly. My data was never turned off in my account and my sim card was supposedly still active according to the store employee.
Again guys, so sorry for the dummy talk... thanks for sticking with me so far!
This may or may not sound stupid but it appears I may have a virtual machine running on top of my android system?? I ran a GPU Benchmark and my GPU Load never increased from 0% and my CPU seemed to have been doing all the work.
I cannot get answers from XDA forum searches,, Googling, ATT, Samsung, employer and I am genuinely concerned because I work for a financial institution and at one point had my work email configured on this device. I handle lots of PII so I have been taking unpaid vacation to try to figure this out without much luck.
I have not and could not possibly cover everything I have tested/searched/noticed. I am basically either a lot dumber than the average bear or my internet searches are being filtered to make this troubleshooting extremely difficult. At this point I am going out of my comfort zone to post online for the first time ever on any forum so please be gentle with me. Also, I could literally talk for days about what I've done and what I have figured out these past couple weeks so PLEASE ask me questions if you have any. You can mock me and call me stupid, please just do so in a manner that details where I am going wrong.
Sorry for the crappy sentence structure and grammar... I was a sailor and not a college student for a reason! Thanks for any support you can provide!
Much love
Click to expand...
Click to collapse
I have noticed this same thing. The warning message obviously states that it is unsafe for production use therefore how is this supposed to be normal? I am just as concerned with this warning message as you are. I hope someone that knows something more about it will come forward and provide an answer that actually offers some kind of real explanation as to what is going on here.