Develop Bugs

Removing the StageFright bug

I want to secure my phone from the recently discovered StageFright Android hack.
I want to remove the component/package that this bug is linked to.
I am running AT&T Rooted Stock (minus bloatware) 4.4.2 Baseband: I747UCUFNE4.
I want to remove the offending package with titanium backup until an Update can be issued.
Can someone let me know what package I need to remove?

You will be better off waiting for a xposed patch, stagefright (if you have been paying attention) is the media processor in android so if you take it out you loose most media playback
Sent from my Nexus 7 2013 using Tapatalk

crazymonkey05 said:
You will be better off waiting for a xposed patch, stagefright (if you have been paying attention) is the media processor in android so if you take it out you loose most media playback
Sent from my Nexus 7 2013 using Tapatalk
Click to expand...
Click to collapse
AT&T is never going to release an patch for my Device.

mrnapolean1 said:
AT&T is never going to release an patch for my Device.
Click to expand...
Click to collapse
No they're not, but CM apparently has stagefright patched.
Maybe it is time to give a custom ROM a shot. :good:

jason2678 said:
No they're not, but CM apparently has stagefright patched.
Maybe it is time to give a custom ROM a shot. :good:
Click to expand...
Click to collapse
I have CM on my Captivate up until my screen took a ****.
Do you know any good tutorials for installing CM on the SIII?

mrnapolean1 said:
I have CM on my Captivate up until my screen took a ****.
Do you know any good tutorials for installing CM on the SIII?
Click to expand...
Click to collapse
There are some guides linked to these forums, but the ones I know of are pretty old and out of date. Samsung pushed Knox with the newer firmware updates, and that really changed how we have to handle this phone. The information you're after has been written all over this forum by many members, myself included, but I can't seem to find a decent post to link to right now. The problem is there is a lot of information, it is all fragmented across thousands of posts, hard to search (hard to find what you're after anyway), and some of the old information can be a little dangerous with the newer bootloaders.
The key to not bricking this phone is to know what bootloader and modem you're on and never, ever try to downgrade it (if you're on a newer one). First thing to do is install the Samsung phone info app from the play store and check your bootloader and baseband. Alternately enter this in a terminal:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
If your bootloader ends in MJB, NE4, or NJ1 don't ever try to downgrade it. The result is a hard brick that is very difficult to recovery from. That means never Odin back to stock if you're on MJB, NE4, or NJ1. The only stock Odin package AT&T allowed to be released is the "ancient", new bootloader bricking LK3 Android 4.1.1 firmware.
If your bootloader or modem end in NE4 or NJ1 you're good to go. You can flash any newer ROM you want. If you're on MJB you're probably ok too. If you're on anything else your mobile data probably won't work with CM 12.1. You'll have to look into updating.
Another good thing to know is that the i747/d2att bootloaders are not locked and have never been locked. Do not attempt to unlock them. Any GS3 bootloader unlock procedure you come across is probably for the Verizon variant, and if you try it on a d2att you'll likely have a hard brick.
Also be aware that the i9300 was marketed as Galaxy S3 as well, but it is a totally different device on the inside. Never flash an i9300 ROM on a d2att phone.
Once you've verified what bootloader/modem you're on, and that it is good to go with CM 12.1, these are the basic steps I'd take if starting with an unmodded phone:
1) Download a SuperSU TWRP flashable zip and store it somewhere on your phone.
2) Use Odin to flash the latest version of TWRP for d2att. Uncheck everything but f.reset time so the phone doesn't auto reboot. Upon success pull battery.
3) Replace battery. Boot straight into recovery by holding vol up + home + power until you see some tiny blue text in the upper left then releasing. If you mess up and accidentally boot into your stock ROM your custom recovery will likely get overwritten with stock and you'll have to repeat step 2 and try again.
4) Flash SuperSU in TWRP.
5) Reboot to stock ROM. Use play store to update your SuperSU binary. You'll probably have to reboot once or twice, but eventually you'll get working root and Knox disabled.
6) In stock ROM open a terminal and enter:
Code:
su
reboot nvbackup
Your phone will reboot. It will seem like a pretty normal reboot, but you'll see some quick flashes of blue text in the upper left if your looking for it. This fixes a Samsung derp and makes sure you have a working EFS backup. This was the only reason we rooted your stock ROM; sorry about all that work just to do this but if your phone ever panics from a bad flash and triggers its autorestore function you'll be happy you did it.
7) Download ROM for d2att and matching gapps. Store them on external SD if you have one. Otherwise verify you can copy files from PC to phone via USB when your phone is booted into TWRP. With TWRP up an running you should just have to plug it in and phone will be recognized by PC as a media device you can transfer files to.
8) Reboot to recovery. Make a backup in TWRP. Store copies on external SD and somewhere off phone for safekeeping. In fact, always keep a nandroid backup or two, a ROM you know works, and a gapps package on an external SD - just in case.
9) Do wipe -> advanced wipe. Tick dalvik, cache, system, and data.
10) Do wipe -> format data. This is why your new ROM and gapps need to be on external SD. Otherwise you'll have a blank phone and you'll have to copy something over via usb or push it via adb to have something to flash. You don't need to do this every time you flash a ROM, but you do need to do it when switching from touchwiz to AOSP and vice versa.
11) Flash ROM
12) Flash gapps
13) Reboot - be patient. 1st boot might take 10 - 15 minutes on a lollipop ROM with this phone.
14) Profit
This probably isn't detailed enough to use as a walkthrough. It will give you an idea what to search and do more research and reading on, and I think I flagged most of the hard bricking pitfalls owners of this phone run into.. Make sure you understand the whole procedure before proceeding. Wouldn't want you to brick your phone trying to deal with a potential vulnerability there's a remote chance you might be targeted with.
Good luck. I made it sound a little scary, but as long as it is handled properly this phone is a flashing beast. If I haven't flashed mine dozens of times, then its in the hundreds. Never had anything go so wrong to the point that I could boot up into recovery and restore or flash my way out of it.

I have NE4 bootloaders

mrnapolean1 said:
AT&T is never going to release an patch for my Device.
Click to expand...
Click to collapse
I never said att, I meant Xposed framework. People release security patches on their all the time
Sent from my Nexus 7 2013 using Tapatalk

Wrong Test Keys - OTA update failed

Hi Guys,
so this morning my SW3 told me there was a system update, cool, so i said yes to the update and let it do its thing.
on coming back, the os version was still the same (LDZ22D) which i thought was odd.
I then did a search and found that there was indeed a new version out (LCA43) and thought something sus was afoot.
I got the twrp from this post http://forum.xda-developers.com/smartwatch-3/development/lwx49k-rooting-easy-t3107501 and booted from twrp
i then pushed the rom i downloaded form here http://www.xperiablog.net/2015/08/2...-update-lca43-intros-interactive-watch-faces/ and promptly tried to flash it like i would any custom rom i would normally flash on any of my other android devices.
I got an error, saying it was expecting "test keys" from a LAZ22D device or a LWX49K device, and that I had LRX22G test keys.
I also tried an ADB sideload which also didn't work.
Am i doing something wrong? Has anyone else ever encountered this?
Full disclosure, I also installed supersu a few months ago, but have had many factory resets since then (new roms on the paired fone) which i wouldn't have thought was an issue?
Cheers for any help you can give

That update only works on stock recovery. Go to my rollback thread and install the complete system of 5.0.1. I put links and directions to all the files. Then roll forward.

Thanks for that @lekofraggle, but I found an easier option, install Sony companion software, reflash "latest" firmware (apparently LAZ22D) then sideload the original update zip. Worked just fine. Just to clarify, I never flashed twrp, just hot booted from it, wondering if root did break ota...
Sent from my Nexus 7 WIFI using Tapatalk

Yes, root breaks most otas, but adb sideload usually works. Glad it was simpler than my doomsday thoughts.

[Q] Nexus 7 random reboots

I have recently traded in my old Nexus 7 2012 for a 2013 model and since day one its been rebooting (a lot) also struggling to boot up (most of the time), It is running android 6.0.1 and after rooting TWRP recovery is not sticking either it seems to revert to stock recovery. After browsing the internet im not sure if its suffering hardware or software problems any help would be much appreciated thanks.

Twrp issue is discussed a lot recently in several threads. Late manufactured N7-13's, the ones preloaded with LP and not JB, have other Emmc chip. Regular Twrp not compatible. But a multirom Twrp is.
Concerning the reboot and boot issue. If already done a factor reset I don't know. Normally Ota's to new version leave a mess with bugs and decreased battery life. I always factory reset before and after big updates. (And easy restore everything with Tiranium). Sometimes via recovery only wiping cache partition is sufficient. Try that first.

Thanks I got TWRP to stick using Flashify and have tried resetting and reflashing but am still suffering from reboots/not booting up im beginning to think its a hardware issue from what ive read online.
Could installing lollipop help maybe then updating to Marshmallow?

After a bit of poking around inside and applying some insulating tape on the ribbon connectors I now have a usable device. Reboots once or twice a day and suffering with issues when typing (getting ip instead of o in portrait mode) so still not 100%. Am now waiting for a replacement tab. Just out of curiosity does anyone know how to find the date of manufacture without the box?

Got a replacement yesterday and what a difference. 100% better than the last one so it was definitely a hardware issue, and I got a refund for the waiting so basically its been a straight swap - my 16gb 2012 for this 32gb 2013 ?

Nvidia Experience 5.2 ROM

I have not been able to update my shield tv 2015 16gb device to 5.2.
The device is rooted with latest 3.1.1 TWRP recovery. Each time I select upgrade with the stock settings it will reboot into recovery and won't update.
Does anyone have a link to the latest ROM or know where Nvidia stores the OTA file? I would rather flash the image my self if I can find get the ROM.
I'm sure this we'll help a few other people I can't be the only one with this issue. Need the 5.2 image not the 5.0.2 which is the previous version of Shield experience update.

you should not flash TWRP to your device reflash original recovery and remove su then try update again

BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)

Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
.)
Click to expand...
Click to collapse
i didnt know that :good:
but if he has TWRP installed couldnt he format data pation from TWRP thus saving hours of thumb twiddling

Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Click to expand...
Click to collapse
Obviously thats a much longer and worse route.
afgok said:
you should not flash TWRP to your device reflash original recovery and remove su then try update again
Click to expand...
Click to collapse
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?

On another thread looks like others are having this same issue with only this version 5.2.. ill just wait for the Dev Images to show up hopefully soon.

I unrooted but still got the same issue, it wont install. But I also have another issue, i can't restore my 2015 shield 16gb by using official recovery rom and official tutorials. It consistently fails to flash system.img and vendor.img by saying that the data is too large. The only way I got my system back was by flashing this file https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062 through twrp

Diehardshorty said:
Obviously thats a much longer and worse route.
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.

Ichijoe said:
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Click to expand...
Click to collapse
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0

If you're rooted, the right answer is to wait for Nvidia to release the 5.2 image.
If you absolutely need 5.2 right now for some reason, several people said that doing a factory restore worked. Just unrooting and restoring stock recovery won't do it, you need to do a full restore.

Diehardshorty said:
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
Click to expand...
Click to collapse
The Dev images are quite a bit different, and are also on an entirely different timeline to either the Preview, (Which I'm on), or the most current version.
But, yeah I could see how those would work. Alas mores the pitty that the rooted asspects of those Dev Images, only go as far as ADB, and not say a full /system wide root. Than again... It's probably for the best that way.
But, that doesn't really change the answer if you want / need to update (From root), than you are going to have to bite the big One, and run a Factory Reset. Which again, on the Pro, means a 2h+ reformating (zeroing out), of the /data Partition.

16gb version doesn't take as long to format but I've always remember flashing SuperSU.zip after ROM just incase. Short response for now at work.

Diehardshorty said:
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Use to be here:
/data/data/com.nvidia.ota/app_download
You obviously need root to reach that folder...
If i have time i will upload later this small OTA update to MEGA.

I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886

sammarbella said:
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
Click to expand...
Click to collapse
Sweet thanks I'll give that a try from the sounds of it it might not work but I'll give a shot after work. Thanks

No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS

Diehardshorty said:
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update

Cameron581 said:
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Click to expand...
Click to collapse
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.

Diehardshorty said:
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Click to expand...
Click to collapse
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.

Cameron581 said:
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Click to expand...
Click to collapse
Ahhhhh that missing point for "error 7".
So the new app bypass that problem!
Thanks for posting it. :good:

I need some advice on downgrading from MM, rooting etc

My T800 is in a right state. I was running one of the first MM roms to be released in the wild, with root and twrp. But a couple of months ago, I mistakenly installed the correct official MM rom, breaking everything. Now I can't root it, install twrp and adopted storage doesn't work.
So I was hoping I could downgrade to lollipop, root, install twrp and then update to one of the root-friendly MM roms on here. Is it possible to do that?

mickrick said:
My T800 is in a right state. I was running one of the first MM roms to be released in the wild, with root and twrp. But a couple of months ago, I mistakenly installed the correct official MM rom, breaking everything. Now I can't root it, install twrp and adopted storage doesn't work.
So I was hoping I could downgrade to lollipop, root, install twrp and then update to one of the root-friendly MM roms on here. Is it possible to do that?
Click to expand...
Click to collapse
I’ve flashed lollipop KitKat marshmallow upgrade downgrade without any issues. These are official firmware’s i been flashing via Odin SM-T705 my model is hope that answers your question..

mickrick said:
My T800 is in a right state. I was running one of the first MM roms to be released in the wild, with root and twrp. But a couple of months ago, I mistakenly installed the correct official MM rom, breaking everything. Now I can't root it, install twrp and adopted storage doesn't work.
So I was hoping I could downgrade to lollipop, root, install twrp and then update to one of the root-friendly MM roms on here. Is it possible to do that?
Click to expand...
Click to collapse
I'm not sure what you mean by break everything?
A few more specifics is required.

ashyx said:
I'm not sure what you mean by break everything?
A few more specifics is required.
Click to expand...
Click to collapse
By "broken" I mean, apps crashing, apps not installing, freezing, random rebooting, overheating. The sorts of things which drive you mental and, in effect, break everything.
I must have wiped and installed the OS a dozen times over the weekend. I was able to get the correct version of twrp and install it with odin, letting me wipe the system and data partitions in order to get a clean install. I restored all my apps, installed a system update. Then I installed twrp again, flashed the su zip and for some reason it would start freezing, reporting the sd card had been removed. So I eventually wiped, installed the rom, and then let Smart Switch install the correct version of MM for my tablet and just installed the really essential apps. Then twrp and finally su. I was even able to set half of my sd card up as adoptable storage (using root essentials app) and it is working perfectly now.
But I think its time I was looking out for a replacement tablet now. Although a great device at the time, and for a couple of years afterwards, it has become a bit long in the tooth lately.

In order to rule out any external issues, I'd use odin to flash the factory firmware (this of course will erase TWRP). Remove the sd card, and use the device for a while as is. If it works, then your past problems were some kind of software-related problem. If it still has issues, then there could be a hardware problem, like memory or the rest of logic board.

Akopps said:
In order to rule out any external issues, I'd use odin to flash the factory firmware (this of course will erase TWRP). Remove the sd card, and use the device for a while as is. If it works, then your past problems were some kind of software-related problem. If it still has issues, then there could be a hardware problem, like memory or the rest of logic board.
Click to expand...
Click to collapse
I think he's got it sorted now. Seems that's what he's already done.