I've been holding off on unlocking my TF700 because I'm afraid of losing DRM, but I
don't really know what the effect will be.
I've been reading this forum for a few months, and I've seen a few bits, but
I'm hoping that people here can add to this.
Apps that lose ability to play HD videos as a result of unlock-caused DRM loss:
Google Play
Apps that lose ability to play HD, but there's a workaround:
Hulu+
Apps that are reportedly not negatively affected by unlock-caused DRM loss:
Netflix
Apps that I use that I'm hoping won't be affected by unlocking
HBO Go
Time-Warner Cable customer video/tv app
Can anyone provide any details on which other apps are affected/not affected
by this?
I am just getting started with the Infinity myself - flashing CROMI as i type, actually.
On flashing, CROMI does give the option to fix DRM specifically for the Hulu+ app. I can't say from personal experience whether it works, though I imagine that it would have come up in the threads if it did not.
bruinhoo said:
I am just getting started with the Infinity myself - flashing CROMI as i type, actually.
On flashing, CROMI does give the option to fix DRM specifically for the Hulu+ app. I can't say from personal experience whether it works, though I imagine that it would have come up in the threads if it did not.
Click to expand...
Click to collapse
He's interested in "HBO Go and Time-Warner Cable customer video/tv app'", CROMI will only works for Hulu+, Netflix and Google Play Movies(SD only, no HD). Since I don't HBO or Time-Warner Cable I can't test them.
Everyone, feel free to post about apps I didn't mention -- apps that depend on DRM that get broken by unlocking, apps that you might worry about that aren't affected. Even if I'm not interested, I'm sure others will find it useful, and it would be great if this thread turned into an exhaustive source of information on the subject, as there does not appear to be any other place with the info all in one place.
buhohitr said:
CROMI will only works for Hulu+, Netflix and Google Play Movies(SD only, no HD).
Click to expand...
Click to collapse
buhohitr: Does "SD only, no HD" apply to all three of Hulu+, Netflix and Google Play, or just Google Play?
bsammon said:
Everyone, feel free to post about apps I didn't mention -- apps that depend on DRM that get broken by unlocking, apps that you might worry about that aren't affected. Even if I'm not interested, I'm sure others will find it useful, and it would be great if this thread turned into an exhaustive source of information on the subject, as there does not appear to be any other place with the info all in one place.
buhohitr: Does "SD only, no HD" apply to all three of Hulu+, Netflix and Google Play, or just Google Play?
Click to expand...
Click to collapse
Just Google play. Everything else I mentioned worked as expected.
buhohitr said:
Just Google play. Everything else I mentioned worked as expected.
Click to expand...
Click to collapse
Okay. Based on my reading of other threads, it's my impression that to keep Hulu+ working after unlocking, you need to use a patched/hacked version. Is that correct?
If so, anyone got a link to good info about the patched Hulu+ to add to this thread?
bsammon said:
Okay. Based on my reading of other threads, it's my impression that to keep Hulu+ working after unlocking, you need to use a patched/hacked version. Is that correct?
If so, anyone got a link to good info about the patched Hulu+ to add to this thread?
Click to expand...
Click to collapse
No that's not correct. When you install CROMI, and during the installation, just select Hulu+. After boot up, you just go to the market and download Hulu+ and it will work as normal.
bsammon said:
Okay. Based on my reading of other threads, it's my impression that to keep Hulu+ working after unlocking, you need to use a patched/hacked version. Is that correct?
If so, anyone got a link to good info about the patched Hulu+ to add to this thread?
Click to expand...
Click to collapse
As Buhohitr says that was a previous way of using it. We figured out how to get the full market app working on CROMI a few versions back so now you just choose the option from the installer and it puts the correct files in place.
sbdags said:
As Buhohitr says that was a previous way of using it. We figured out how to get the full market app working on CROMI a few versions back so now you just choose the option from the installer and it puts the correct files in place.
Click to expand...
Click to collapse
What if you don't use CROMI? Is there a workaround that applies to other ROMs or (if you're weird enough) a stock ROM?
bsammon said:
What if you don't use CROMI? Is there a workaround that applies to other ROMs or (if you're weird enough) a stock ROM?
Click to expand...
Click to collapse
Go into /system/vendor and make sure the lib file is named as "lib.org" (without quotation). Should look like this
/system/vendor/lib.org
buhohitr said:
Go into /system/vendor and make sure the lib file is named as "lib.org" (without quotation). Should look like this
/system/vendor/lib.org
Click to expand...
Click to collapse
Where do we find this library file that needs to be named lib.org? There are no files under /system/vendor, only directories.
lunatic_fringe said:
Where do we find this library file that needs to be named lib.org? There are no files under /system/vendor, only directories.
Click to expand...
Click to collapse
It is the directory. Rename /system/vendor/lib to /system/vendor/lib.org if you want google play working. Leave it as lib if you want hulu+ working.
sbdags said:
It is the directory. Rename /system/vendor/lib to /system/vendor/lib.org if you want google play working. Leave it as lib if you want hulu+ working.
Click to expand...
Click to collapse
Thank you, I misunderstood. Does a symlink suffice to allow both to function? I don't use google play often but it would be good to know.
buhohitr said:
Go into /system/vendor and make sure the lib file is named as "lib.org" (without quotation). Should look like this
/system/vendor/lib.org
Click to expand...
Click to collapse
I had interpreted this as saying "lib.org" was for Hulu+
sbdags said:
It is the directory. Rename /system/vendor/lib to /system/vendor/lib.org if you want google play working. Leave it as lib if you want hulu+ working.
Click to expand...
Click to collapse
But this is saying that "lib" is for Hulu+.
Which is it?
bsammon said:
I had interpreted this as saying "lib.org" was for Hulu+
But this is saying that "lib" is for Hulu+.
Which is it?
Click to expand...
Click to collapse
lib is for hulu+ and lib.org is for Google play movies. After you made the change, you will need to reboot the device. Sorry for the confusion.
HBOgo on Comcast works. I found that flixter / Ultraviolet don't work. Do I just not realize that my tf700 isn't playing back the Google play movies in HD?
buhohitr said:
lib is for hulu+ and lib.org is for Google play movies. After you made the change, you will need to reboot the device. Sorry for the confusion.
Click to expand...
Click to collapse
Okay... didn't have access to my TF700 for a few days. Now that I do, I'm checking on this.
My ICS .26 stock install has "/system/vendor/lib/", but no "/system/vendor/lib.org/" .
So, if I unlock this, the stock system should still work with Hulu+, but I'd need to symlink /system/vendor/lib/ to /system/vendor/lib.org/ to get Google Play working as well? (but only in SD?)
bsammon said:
Okay... didn't have access to my TF700 for a few days. Now that I do, I'm checking on this.
My ICS .26 stock install has "/system/vendor/lib/", but no "/system/vendor/lib.org/" .
So, if I unlock this, the stock system should still work with Hulu+, but I'd need to symlink /system/vendor/lib/ to /system/vendor/lib.org/ to get Google Play working as well? (but only in SD?)
Click to expand...
Click to collapse
Not sure you can have them working at the same time. Google play doesn't like seeing the lib folder...... Hence you rename it you effectively hide the files inside.
I think there is still nobody who tested if making a backup of the DRM key before unlocking and restoring it afterwards leads to success.
In case anyone wants to try: The partition to backup and restore is /dev/block/mmcblk0p6. You must save its contents before unlocking (e.g. with dd) and then restore it.
_that said:
I think there is still nobody who tested if making a backup of the DRM key before unlocking and restoring it afterwards leads to success.
In case anyone wants to try: The partition to backup and restore is /dev/block/mmcblk0p6. You must save its contents before unlocking (e.g. with dd) and then restore it.
Click to expand...
Click to collapse
Hmm... tried this:
Code:
[email protected]:/ $ mkdir /mnt/sdcard/backups/
[email protected]:/ $ dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/backups/mmcblk0p6.bak
/dev/block/mmcblk0p6: cannot open for read: Permission denied
do I need to be rooted to do this, or did I get it wrong in some other way?
Also, I'm not sure how to verify that this worked, as I don't currently have any DRMed content that I use. I would need a pointer to a (preferably free and HD) known-DRM content that I could verify this with.
Related
The is an app in the market that I would like to get but it says it is incompatible with the transformer but I am 99 44/100% sure it will work.
Is there a way to fool the market place? I searched and found answers for other devices but none for the transformer.
Thanks in advance!!
DougP123
Hi
If you have another android device, like phone, download it to phone, make backup, transfer apk to TF and install. Works for me.
I have downloaded apps directly to my tf and after uninstalling them tried to get them from the market only to be listed as incompatible..think it had something to do with having a custom rom, some of them include older versions of market, some have the option to install the ics market app, while others have options to go back to the hc market app. AS poster before said, you can download on another compatible device and make a backup and just swap the apk over, but if you don't have a backup device many of the apps on the market can be found in the wild as the raw apk file, even some pay apps can be found in the wild, though i don't pirate apps because that is the sure way to kill or own market (who is going to design apps for android if they can be pirated so easily?).
Also, try to get the 'tablet market' app, that seems to have the tablet optimized versions of some apps that are hard to find via market.
stenc55 said:
Hi
If you have another android device, like phone, download it to phone, make backup, transfer apk to TF and install. Works for me.
Click to expand...
Click to collapse
After downloading to the compatbile device, how do you transfer it to the incompatible device can you explain?
cetindk said:
After downloading to the compatbile device, how do you transfer it to the incompatible device can you explain?
Click to expand...
Click to collapse
Like sent an email with attached apk to yourself and open it on the device were its needed on
batjuh said:
Like sent an email with attached apk to yourself and open it on the device were its needed on
Click to expand...
Click to collapse
Wait I dont get it. After downloading the app from Google Play, where do I find the apk for that app? And do I need a root for this?
God I hate sounding like a noob...
cetindk said:
Wait I dont get it. After downloading the app from Google Play, where do I find the apk for that app? And do I need a root for this?
God I hate sounding like a noob...
Click to expand...
Click to collapse
O didn't understand you had the apk from the market the first time. Thought you said you first downloaded it from another site then the google market.
Otherwise you need root for you transformer indeed. they are in /data/app folder
[ps] = I have downloaded apps directly to my tf and after uninstalling them tried to get them from the market only to be listed as incompatible <----this is why i thought you downloaded somewere else !!
So I spent a lot of time trying to get this working, and I finally did and I figured I'd share how I did it. It works for me, and a user of Google + confirmed it too. It's pretty simple. Thanks to Dustin Evans on Google+ (https://plus.google.com/u/0/108019745978944993252/posts) and XDA user garner.
first, find your build.prop in /system. Please use Root Explorer, I'm not sure if other file browsers save it correctly. Mount Read/Write and long press on build.prop and hit "Open in text editor".
Change the following lines to look like this:
ro.product.model=SPH-L710
ro.product.name=d2spr
ro.product.device=d2spr
reboot after.
after that head here http://forum.xda-developers.com/showthread.php?t=1965895 and download the wallet apk. (not all the gapps, just the wallet apk). It should work!
Im running cm 10.1 but it also worked on cm 10.
also this is my first post, feedback?
EDIT: I know that there are other posts describing how to do this but I found that they either didn't work for me or involved more complex steps. I'm sharing this because i found it to be easier and completely successful.
You should have used the search function on here. Would have saved you tons of time trying to get it to work. Also you should be able to download the apk from the market once you change these settings inyour build.prop file as well.
http://forum.xda-developers.com/showthread.php?t=1794727
Or you could just use this http://forum.xda-developers.com/showthread.php?p=34896632 and it will change build.prop for you and install wallet!
Sent from my SCH-I535 using xda premium
stearic said:
You should have used the search function on here. Would have saved you tons of time trying to get it to work. Also you should be able to download the apk from the market once you change these settings inyour build.prop file as well.
http://forum.xda-developers.com/showthread.php?t=1794727
Click to expand...
Click to collapse
thanks, but i knew that. i dont think you can just download it, as i did that and it didnt work so well. i know there are other methods, but those are sketchy and involve flashing a new recovery (the all in one installer). this is a more clean way that i got it to work.
just trying to share my experience
also this does not involve flashing anything
Nope, i changed the build.prop file, rebooted and it showed up in the market. Installed it and it works perfectly. The method i mentioned did say you to flash stuff, but that's with the touchwiz based roms. But it also does say pretty much do what you have said as well.
Insufficient privleges
I changed the build prop like shown and was able to download. But when app is ran it states that I have insufficient privileges for this system image. I am just running a rooted image of stock do I need to flash a new rom for it to work?
GSHARPE3 said:
I changed the build prop like shown and was able to download. But when app is ran it states that I have insufficient privileges for this system image. I am just running a rooted image of stock do I need to flash a new rom for it to work?
Click to expand...
Click to collapse
Yeah I got the same error, running rooted stock.
crazymadbaby said:
Or you could just use this http://forum.xda-developers.com/showthread.php?p=34896632 and it will change build.prop for you and install wallet!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Doesn't work.
It tells me i'm an unsupported device.
Santinelli said:
Yeah I got the same error, running rooted stock.
Click to expand...
Click to collapse
Yeah that just means you need to flash the Touchwiz libs zip file that's floating around the forums, then Wallet will work. I have the .zip file here: https://www.dropbox.com/s/lp7qj8odmhobwtu/D2VZW-Wallet-TW-JB-R81.zip
bogedy said:
So I spent a lot of time trying to get this working, and I finally did and I figured I'd share how I did it. It works for me, and a user of Google + confirmed it too. It's pretty simple. Thanks to Dustin Evans on Google+ (https://plus.google.com/u/0/108019745978944993252/posts) and XDA user garner.
first, find your build.prop in /system. Please use Root Explorer, I'm not sure if other file browsers save it correctly. Mount Read/Write and long press on build.prop and hit "Open in text editor".
Change the following lines to look like this:
ro.product.model=SPH-L710
ro.product.name=d2spr
ro.product.device=d2spr
reboot after.
after that head here http://forum.xda-developers.com/showthread.php?t=1965895 and download the wallet apk. (not all the gapps, just the wallet apk). It should work!
Im running cm 10.1 but it also worked on cm 10.
also this is my first post, feedback?
Click to expand...
Click to collapse
Can I change these values in build.prop back after google wallet is working, or no?
not for stock samsung
Santinelli said:
Yeah I got the same error, running rooted stock.
Click to expand...
Click to collapse
this is for cm 10/10.1
specialkcf said:
Can I change these values in build.prop back after google wallet is working, or no?
Click to expand...
Click to collapse
nope, but why would you need to? it basically makes it so that you able to get through any barriers verizon put in your way for any app
Device not Ready
I am getting the following error when trying to run Google Wallet.
Deviice Not Ready
Wallet is unable to proceed until this device is fully initialized. Make sure the device has network access and try rebooting if the problem persists.
I have rebooted to no avail. Any suggestions?
krmtdfrg said:
I am getting the following error when trying to run Google Wallet.
Deviice Not Ready
Wallet is unable to proceed until this device is fully initialized. Make sure the device has network access and try rebooting if the problem persists.
I have rebooted to no avail. Any suggestions?
Click to expand...
Click to collapse
sorry i didnt see this. if its still an issue, which im assuming its not, more details please?
Hello!
Did anybody allready found the way to integrate updates of system apps into rom? On 5.0.1 you have just simply copy app and lib folder from /data/app to /system/app, but it seems that this isn't work any more.
Any working solution is appreciated.
Regards, Zagor
@rootSU, @_MetalHead_, @Elluel, @jd1639, ..., maybe?
5.1 hasn't even been released for my device yet
I have a connected issue.
I cannot convert apps to system apps as it says there isn't enough space in \system. It worked fine on 5.0.1 so what they done???
mcnob said:
I have a connected issue.
I cannot convert apps to system apps as it says there isn't enough space in \system. It worked fine on 5.0.1 so what they done???
Click to expand...
Click to collapse
It's not about the space. You can get it by removing some unnecessary apps. The problem is, that if you integrate an app, system somehow woudn't recognize it anymore.
zagorteney said:
It's not about the space. You can get it by removing some unnecessary apps. The problem is, that if you integrate an app, system somehow woudn't recognize it anymore.
Click to expand...
Click to collapse
Sorry zagorteney, I haven't tried to do what you're asking.
Sent from my Nexus 5 using XDA Free mobile app
I'm still on 5.0.2 as I haven't merged 5.1 into my source yet.
I'm on 4.4.4 still so I can't really help you. Sorry.
What apps are you trying to integrate? Some app's lib files sometimes need to be on the /system/lib folder in order for them to work. 5.1 is also ODEX'ed.
I had issues doing it also. Didn't care enough to dig into it. Not a big deal, just execute the APK to update.
happiness4u said:
What apps are you trying to integrate? Some app's lib files sometimes need to be on the /system/lib folder in order for them to work. 5.1 is also ODEX'ed.
Click to expand...
Click to collapse
I'm trying to integrate all updated Google apps. About lib's files you mentioned: it was on 4.4.4, that you have to exctract apps and copy apk to /system/app and corresponding libs to /system/lib. You have also to give them correct permissions. Actually, you have to be carefull and copy libs from PrebuiltGsmCore (or Google Play Services, if you like) last one. Otherwise you got force closes.
On 5.0.1 it was much easier. You just have to move apk and Lib folder from /data/app/ to /system/app or /system/priv-app. Permissions is allready ok. Cleaned dalvik (ART) cache and voila. You have integrated system apps (no need to have them on phone two times).
On 5.1 there are some strange things, that I can't figure it out. For example: if you move updated apk to /system/app it's somehow not installed anymore. I try do all possible ways, one of attempt succeeded, but when I try to do exactly the same with another one, it fails.
Also, I think, that actually problem with Xposed is somehow related to this behavior.
Sorry I'm mentionig you folks again, but because you are profs, you can maybe use this info also on Xposed thread.
@rootSU, @jd1639, @Elluel, @_MetalHead_ -know that you are stuck in stone age, but anyway , @Aerowinder, @Primokorn
zagorteney said:
know that you are stuck in stone age, but anyway
Click to expand...
Click to collapse
Not my fault google decided to update the crappy Nexus 5 before the mega Nexus 6
rootSU said:
Not my fault google decided to update the crappy Nexus 5 before the mega Nexus 6
Click to expand...
Click to collapse
Come on. Now Nexus 5 is crappy. You show-off.
zagorteney said:
Come on. Now Nexus 5 is crappy. You show-off.
Click to expand...
Click to collapse
Mine was ,yes. Severe endfire / noise cancellation issues once lollipop dropped I couldn't make a call without editing the build.prop. Which means I cannot even sell the device to get money. Very annoyed.
rootSU said:
Mine was ,yes. Severe endfire / noise cancellation issues once lollipop dropped I couldn't make a call without editing the build.prop. Which means I cannot even sell the device to get money. Very annoyed.
Click to expand...
Click to collapse
But, this is not lollipop related. It must be something with hardware.
Likewise. Still on 5.0.2 atm. I can tell you that much.
zagorteney said:
But, this is not lollipop related. It must be something with hardware.
Click to expand...
Click to collapse
It's Nexus 5 related, hence my statement "crappy Nexus 5"
zagorteney said:
Also, I think, that actually problem with Xposed is somehow related to this behavior.
Sorry I'm mentionig you folks again, but because you are profs, you can maybe use this info also on Xposed thread.
Click to expand...
Click to collapse
Not sure why Xposed is relevant. Xposed involves so much more possible things that could break.
Elluel said:
Not sure why Xposed is relevant. Xposed involves so much more possible things that could break.
Click to expand...
Click to collapse
Of course you are wright. But till 5.1 Ive never noticed such a "strange" behavior of android system.
So this is just my humble opinion.
P.S. Further conclusions: You can simply make any other app as system one, but still no with updates.
@rootSU
Any news on this, now that you have got 5.1 too?
Hi
i know it of course is a Google Apps Fix, but can't find any info about it on Google. Is it just the app in the play store Gapps fix?
What exactly do it do? Just disable some services and such? I just see more and more people are talking about it and some developers have added it to their roms and such.
Just heard it makes Android Wear stop working and such.
Thanks in advance
its an int.d script that stops extra google services from running
Also can be found in some custom kernels
tlxxxsracer said:
its an int.d script that stops extra google services from running
Also can be found in some custom kernels
Click to expand...
Click to collapse
Any Idea where I find it? Can't find it on the play store anymore and neither on XDA.
Thanks in advance
Faspaiso said:
Any Idea where I find it? Can't find it on the play store anymore and neither on XDA.
Thanks in advance
Click to expand...
Click to collapse
Well, it's a script and those are not on play store. http://forum.xda-developers.com/showpost.php?p=62770519&postcount=1374
Either put it into init.d folder if your ROM supports it or run it a terminal.
davebugyi said:
Well, it's a script and those are not on play store. http://forum.xda-developers.com/showpost.php?p=62770519&postcount=1374
Either put it into init.d folder if your ROM supports it or run it a terminal.
Click to expand...
Click to collapse
So basically I could just disable the services myself with Disable Service?
davebugyi said:
Well, it's a script and those are not on play store. http://forum.xda-developers.com/showpost.php?p=62770519&postcount=1374
Either put it into init.d folder if your ROM supports it or run it a terminal.
Click to expand...
Click to collapse
Well just ran it in a terminal. It says they're disabled but can't see any new services as disabled in Disable Service. Reboot doesn't change that.
How do I know that it worked?
Faspaiso said:
Well just ran it in a terminal. It says they're disabled but can't see any new services as disabled in Disable Service. Reboot doesn't change that.
How do I know that it worked?
Click to expand...
Click to collapse
Unfortunately I can't help much, since I do not use this script (because I do not have any drain from the services). I only use DisableService.
This is for the Fire HD 8 8th generation rooted with xyz's exploit
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
I've seen a couple people run into problems with this so rather than have xyz's thread clogged I figured I'd
make a seperate thread just for this.
I've made an update to the debloat.zip so it can be flashed at any time rather than flashing after rooting
[seperate zip instead of a modifed finalize.zip ]
==Debloating==
DISCLAIMER : Per testing and input from other members, Amazon Apps will NOT be able to be reinstalled after flashing this. I've yet to figure out if this is a direct result of this script or due to the nature of xyz's exploit, either way
after rooting, do NOT expect to be able to use Amazon Apps (defeat's the purpose of this script anyways lol)
1. Download debloat.zip from here
2. Reboot to TWRP, and flash
3. Reboot to system and say goodbye to Amazon Bloatware
==Replacing FireLauncher==
1. Install a launcher of your choice (Tested with CPL and Nova Launcher)
2. Install Terminal Emulator
3. Run 'su' from terminal emulator and grant it root permissions, then type 'pm disable com.amazon.firelauncher'
4. Press the home button and your new launcher is ready to go !
Thanks to xyz for the amazing work :highfive:
delessio100 said:
This is for the Fire HD 8 8th generation rooted with xyz's exploit
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
I've seen a couple people run into problems with this so rather than have xyz's thread clogged I figured I'd
make a seperate thread just for this.
I've made an update to the debloat.zip so it can be flashed at any time rather than flashing after rooting
[seperate zip instead of a modifed finalize.zip ]
==Debloating==
1. Download debloat.zip from here
2. Reboot to TWRP, and flash
3. Reboot to system and say goodbye to Amazon Bloatware
==Replacing FireLauncher==
1. Install a launcher of your choice (Tested with CPL and Nova Launcher)
2. Install Terminal Emulator
3. Run 'su' from terminal emulator and grant it root permissions, then type 'pm disable com.amazon.firelauncher'
4. Press the home button and your new launcher is ready to go !
Thanks to xyz for the amazing work :highfive:
Click to expand...
Click to collapse
Thanks for this! Will flashing this debloat.zip allow me to install and use the Amazon Prime Video or the Alexa app from the Playstore later on or will it stop the app from working?
ryknow27 said:
Thanks for this! Will flashing this debloat.zip allow me to install and use the Amazon Prime Video or the Alexa app from the Playstore later on or will it stop the app from working?
Click to expand...
Click to collapse
Per my testing, the Play Store version of Amazon Apps are working (I've tested Alexa, Prime Video, and the Kindle App so far), so yes you should be able to
delessio100 said:
Per my testing, the Play Store version of Amazon Apps are working (I've tested Alexa, Prime Video, and the Kindle App so far), so yes you should be able to
Click to expand...
Click to collapse
Awesome, thanks for the reply. I'll give it a shot.
---------- Post added at 09:49 AM ---------- Previous post was at 09:38 AM ----------
delessio100 said:
Per my testing, the Play Store version of Amazon Apps are working (I've tested Alexa, Prime Video, and the Kindle App so far), so yes you should be able to
Click to expand...
Click to collapse
Sorry, one more question. When you tested the Amazon apps, did you also previously install the finalize.zip?
ryknow27 said:
Awesome, thanks for the reply. I'll give it a shot.
---------- Post added at 09:49 AM ---------- Previous post was at 09:38 AM ----------
Sorry, one more question. When you tested the Amazon apps, did you also previously install the finalize.zip?
Click to expand...
Click to collapse
Yes, xyz's finalize.zip only removes system apps related to OTA updates, so it prevents accidental / forced OTA updates from overwriting things modified by the exploit
delessio100 said:
Yes, xyz's finalize.zip only removes system apps related to OTA updates, so it prevents accidental / forced OTA updates from overwriting things modified by the exploit
Click to expand...
Click to collapse
Thank you
delessio100 said:
Yes, xyz's finalize.zip only removes system apps related to OTA updates, so it prevents accidental / forced OTA updates from overwriting things modified by the exploit
Click to expand...
Click to collapse
I followed the instructions for Tailborn form your post on xyz's thread except for installing Root Essentials and then followed the instructions from this thread and after installing several Amazon apps, they start to open and then force close. I could be wrong but I think it may be due to the finalize.zip because after the first time I successfully rooted with xyz's method it did the same thing. Since it works for you, do you know if you did anything different than what I did?
ryknow27 said:
I followed the instructions for Tailborn form your post on xyz's thread except for installing Root Essentials and then followed the instructions from this thread and after installing several Amazon apps, they start to open and then force close. I could be wrong but I think it may be due to the finalize.zip because after the first time I successfully rooted with xyz's method it did the same thing. Since it works for you, do you know if you did anything different than what I did?
Click to expand...
Click to collapse
What apps specifically aren't working ? I've only tested the Kindle App, Alexa, and Prime Video. Are these giving you errors? I haven't fully tested all Amazon apps as I don't really use them but if you can give me a list of the apps that aren't functional I can take a look when I get home. If you'd prefer I can modify my debloat script to not remove the Amazon apps you want to keep Also if you could provide a logcat from one of the apps that's crashing I can try to determine what's causing the crash. The instructions I provided for Tailborn were just to fix the error with his SD card
delessio100 said:
What apps specifically aren't working ? I've only tested the Kindle App, Alexa, and Prime Video. Are these giving you errors? I haven't fully tested all Amazon apps as I don't really use them but if you can give me a list of the apps that aren't functional I can take a look when I get home. If you'd prefer I can modify my debloat script to not remove the Amazon apps you want to keep Also if you could provide a logcat from one of the apps that's crashing I can try to determine what's causing the crash. The instructions I provided for Tailborn were just to fix the error with his SD card
Click to expand...
Click to collapse
Yes I did see that your instructions were to help him with his SD card issue. I was basically just using it as a guide to start over except for anything to do with the SD card since I didn't have that issue.
The main apps I'm wanting to work that I'm having an issue with is Alexa and Amazon prime video. It will be a little bit before I can attach a logcat. I've never created one before but it should not be that hard to figure out and I'm on my way to work right now.
ryknow27 said:
Yes I did see that your instructions were to help him with his SD card issue. I was basically just using it as a guide to start over except for anything to do with the SD card since I didn't have that issue.
The main apps I'm wanting to work that I'm having an issue with is Alexa and Amazon prime video. It will be a little bit before I can attach a logcat. I've never created one before but it should not be that hard to figure out and I'm on my way to work right now.
Click to expand...
Click to collapse
I'm on my way home from college (on the bus ) so I can guide you through it when I get home. Alexa worked without errors for me so I'm not sure why it wouldn't work for you but I'm sure we'll get it sorted it out soon
Getting Logcat (assuming you're on windows and running command prompt on the desktop)
1. Connect the kindle to your computer, run adb logcat -c (clears logcat)
2. Run adb logcat | findstr "com.amazon.dee.app" > logcat.txt (This will store the logcat for the Alexa app to a text file on your desktop)
3. Go back to your kindle, open the Alexa App and wait for it to crash
4. After it crashes, hit CTRL + C in command prompt (stops logging)
5. Copy and paste logcat.txt and send it in your reply
This will help me figure out what's causing the crash and from here I'll be able to fix it
delessio100 said:
I'm on my way home from college (on the bus ) so I can guide you through it when I get home. Alexa worked without errors for me so I'm not sure why it wouldn't work for you but I'm sure we'll get it sorted it out soon
Click to expand...
Click to collapse
Thanks
delessio100 said:
I'm on my way home from college (on the bus ) so I can guide you through it when I get home. Alexa worked without errors for me so I'm not sure why it wouldn't work for you but I'm sure we'll get it sorted it out soon
Getting Logcat (assuming you're on windows and running command prompt on the desktop)
1. Connect the kindle to your computer, run adb logcat -c (clears logcat)
2. Run adb logcat | findstr "com.amazon.dee.app" > logcat.txt (This will store the logcat for the Alexa app to a text file on your desktop)
3. Go back to your kindle, open the Alexa App and wait for it to crash
4. After it crashes, hit CTRL + C in command prompt (stops logging)
5. Copy and paste logcat.txt and send it in your reply
This will help me figure out what's causing the crash and from here I'll be able to fix it
Click to expand...
Click to collapse
Sorry, I've been really busy here at work this evening and unfortunately, the computers here will not let me retrieve a logcat through ADB. They have them locked down to where we can't use them for much except for work stuff.
I did get a logcat from an app called "aLogcat" from the Playstore but it is really long and I don't know if it will be good enough. I can attach it here or if it is best I can get one from adb later tonight after getting home. I'm in no rush
ryknow27 said:
Sorry, I've been really busy here at work this evening and unfortunately, the computers here will not let me retrieve a logcat through ADB. They have them locked down to where we can't use them for much except for work stuff.
I did get a logcat from an app called "aLogcat" from the Playstore but it is really long and I don't know if it will be good enough. I can attach it here or if it is best I can get one from adb later tonight after getting home. I'm in no rush
Click to expand...
Click to collapse
Id prefer you get one from adb as it'll make narrowing down the problem much easier :good: but I can just use grep on my PC to filter out the other things, so if you can send over what you have and attach the logcat from adb at your leisure when you get home, I'll take a look
delessio100 said:
Id prefer you get one from adb as it'll make narrowing down the problem much easier :good: but I can just use grep on my PC to filter out the other things, so if you can send over what you have and attach the logcat from adb at your leisure when you get home, I'll take a look
Click to expand...
Click to collapse
Hopefully I attach this right...lol.
I will get it from adb later tonight. Thanks again.
ryknow27 said:
Hopefully I attach this right...lol.
I will get it from adb later tonight. Thanks again.
Click to expand...
Click to collapse
I just skimmed through it and grepped for 'com.amazon.dee.app' but nothing crash related has come up. The only crash related thing I noticed in the logcat was related to Amazon's Device Metric's app which shouldn't be affecting the Alexa App ( as i have that app removed and Alexa functioned fine in previous tests). I think a regular adb logcat is gonna be our best bet to narrow the issue down. If you haven't done this already try these suggestions
1. Clear App Data & Cache from settings and try opening it
2. Clear App Data & Cache, then from Settings grant the app all requested permissions, then try opening it
3. Uninstall the app then repeat step 2 after installing (don't open the app before granting permissions)
I have a suspicion it's related to the removal of Amazon's Account Management App (if you go to settings -> My Account , settings crashes) yet only my debloat zip removes this app, and you said you experienced this before flashing it. I'm installing the Alexa app now and I'm going to see if i can reproduce the crashes. I won't be letting Amazon get the best of us
Edit : I was able to recreate the crash by uninstalling the app, reinstalling, and then i got it to crash after signing in, however, after opening the app again it went right to the main screen and hasn't crashed since
Edit 2 : Try uninstalling, installing, signing in, and after it crashes open the app (it will crash again) then open it again (it shouldn't crash this time and should bring you to the main screen)
It seems that there's permissions included in the app that are only allowed for system priv-apps (which might be causing the crash) so if after doing this you still aren't able to get into the main screen try moving the app to /system/priv-app
delessio100 said:
I just skimmed through it and grepped for 'com.amazon.dee.app' but nothing crash related has come up. The only crash related thing I noticed in the logcat was related to Amazon's Device Metric's app which shouldn't be affecting the Alexa App ( as i have that app removed and Alexa functioned fine in previous tests). I think a regular adb logcat is gonna be our best bet to narrow the issue down. If you haven't done this already try these suggestions
1. Clear App Data & Cache from settings and try opening it
2. Clear App Data & Cache, then from Settings grant the app all requested permissions, then try opening it
3. Uninstall the app then repeat step 2 after installing (don't open the app before granting permissions)
I have a suspicion it's related to the removal of Amazon's Account Management App (if you go to settings -> My Account , settings crashes) yet only my debloat zip removes this app, and you said you experienced this before flashing it. I'm installing the Alexa app now and I'm going to see if i can reproduce the crashes. I won't be letting Amazon get the best of us
Edit : I was able to recreate the crash by uninstalling the app, reinstalling, and then i got it to crash after signing in, however, after opening the app again it went right to the main screen and hasn't crashed since
Edit 2 : Try uninstalling, installing, signing in, and after it crashes open the app (it will crash again) then open it again (it shouldn't crash this time and should bring you to the main screen)
It seems that there's permissions included in the app that are only allowed for system priv-apps (which might be causing the crash) so if after doing this you still aren't able to get into the main screen try moving the app to /system/priv-app
Click to expand...
Click to collapse
Ok well, I tried everything you listed here and it still just closes right after opening. I do not get the chance to log in or anything. Also to clarify what I said originally because it may have been a little misleading, the first time I rooted it I did not actually install the Alexa app but I did try to log into the Amazon services within the Fire Launcher and it would crash. At that point, I re-did the root and did not install the finalize.zip and it would then let me log in to Amazon services but that leaves all of the OTA stuff in there. So I tried it all again and that's when I first messaged you about it.
ryknow27 said:
Ok well, I tried everything you listed here and it still just closes right after opening. I do not get the chance to log in or anything. Also to clarify what I said originally because it may have been a little misleading, the first time I rooted it I did not actually install the Alexa app but I did try to log into the Amazon services within the Fire Launcher and it would crash. At that point, I re-did the root and did not install the finalize.zip and it would then let me log in to Amazon services but that leaves all of the OTA stuff in there. So I tried it all again and that's when I first messaged you about it.
Click to expand...
Click to collapse
At this point I'd recommend talking to xyz as it doesn't seem to be an issue with my debloat script, he's going to have a much better understanding of the issue and is more knowledgeable. I'll look at your adb logcat when you get time to grab one but I've wiped my Kindle clean reflashed everything including finalize.zip and my debloat script and I'm still able to log in and use Amazon Apps
No problem and thanks for the assistance. I'll still get the adb logcat later tonight. [emoji3]
Sent from my HTC 10 using Tapatalk
ryknow27 said:
No problem and thanks for the assistance. I'll still get the adb logcat later tonight. [emoji3]
Click to expand...
Click to collapse
I'll take a look whenever you get time to send it :good:
delessio100 said:
I'll take a look whenever you get time to send it :good:
Click to expand...
Click to collapse
Sorry it took me a day to get back to you. I didn't get time to mess with it due to some stuff going on. I tried something different this time. I followed the directions from xyz's thread except I did not install the finalize.zip. I then did everything from this thread, then I used a root explorer and deleted all of the OTA stuff from system/priv-app. Now, the Alexa app will run just fine but the Prime Video app crashes. So, I tried doing what you said a couple of times using "com.amazon.avod.thirdpartyclient" but the .txt file would always be empty. So I just used adb logcat -v long > logcat.txt to catch the crash. Hopefully you can make sense of it...lol.