- 02-13-2013, 07:39 PM #51
- 02-13-2013, 07:56 PM #52
req: Netflix bar
Yea it probably wasn't a good idea to post the video if he wasn't going to say or show how he did it.
This is a new CrackBerry indeed. What happen to being one Nation under crack?...a Team? Lol honestly I think if it were possible for us average Joe to do then they would show us how.
There is something else going on that can't be shared is my guess.
Sent from my BlackBerry by Choice using TapatalkI waited...It launched...Im still waiting...
- 02-13-2013, 11:44 PM #55
Re: req: Netflix bar
something custom must be going on. lots of very smart forum members have been trying every version they can find with no luck. a h3ll of a lot more than 30 versions have been tried. Bla1ze must know how to "trick" the file into thinking it was on a different device or somethingSprint Q10
- 02-14-2013, 03:35 PM #56
does anyone know if the playbooks android runtime is the same as a certain android device? there were a lot of modded apks that worked on certain devices. If we knew which device was like the playbook maybe we could narrow it down.
- 02-14-2013, 04:08 PM #57
No, it's not "the same as a certain device". Any APK with the device check removed should work on all devices. I am quite certain that the reason it doesn't work on the PB is the lack of support for native code in the PB's Android runtime. Netflix needs native code, so without support for it, there's no way it could work. (i.e. if it works on the Z10, the Z10 must support native code...)
EDIT: BTW, apparently the version Bla1ze was running was 1.8.0. (Current version is 2.1.2)
- CrackBerry Newbie
02-24-2013, 04:02 PM #60
- 1 Posts
Hello all, newbie here. Just signed up and got my Blackberry keys and downloaded what I believe to be the 1.8.0 Netflix APK and converted it to a BAR and then signed it and it loads up on my Playbook to a black screen and that's it. :/
Just as an FYI, I've converted and signed a dozen APK's and most work but some do not so I "Think" I know what I'm doing.
- 02-24-2013, 04:21 PM #61
- 02-27-2013, 05:15 AM #64
- 02-28-2013, 05:45 AM #66
Modding APKs is usually for small things e.g. replacing resources (images etc.) to change the look/layout of an app, or removing checks such as device checks or checks for root (a few apps refuse to work on rooted phones, so the APK is modded to work on rooted phones). Big changes aren't usually possible.
- 03-04-2013, 04:18 PM #69
EDIT: Had a closer look at that BAR; there is nothing special about it. The APK within it is exactly the same as an Instagram v3.1.0 APK I found online:
C:\Users\Downloads>fciv -add "com.instagram.android-310.apk" -both // // File Checksum Integrity Verifier version 2.05. // MD5 SHA-1 ------------------------------------------------------------------------- f68a6b0a2fd6c11424dba7f9be875f0d a9bdccdf73e1e29b12e2d163b904949266fb26b5 com.instagram.android-310.apk C:\Users\Downloads>fciv -add "Instagram_3.1.0.apk" -both // // File Checksum Integrity Verifier version 2.05. // MD5 SHA-1 ------------------------------------------------------------------------- f68a6b0a2fd6c11424dba7f9be875f0d a9bdccdf73e1e29b12e2d163b904949266fb26b5 instagram_3.1.0.apk
There is no special trick going on hereEDIT:Well, maybe something a bit different (see below), it's just a case of the regular APK was converted by someone, and it worked. This would seem to imply that BB10 supports native code in Android apps, which would also explain why Netflix functions there (provided device checks are disabled etc.). Until such functionality is added to the Playbook, it will run neither app.
(Not that it really matters, but for the record the first APK above is the one from the BAR posted on the CB blog, the second APK is one I found online having seen the version number of the one from the BAR)
EDIT: Analysis continued below: #73
Last edited by SifJar; 03-07-2013 at 05:17 PM.
- 03-04-2013, 06:58 PM #70
- 03-07-2013, 12:14 PM #73
I was looking at the Instagram BAR posted a few days ago again, and I noticed something interesting: There is an additional line in the MANIFEST.MF file.
I compared the BAR to a BAR I converted myself from the exact same APK. The only significant difference (beyond different signatures due to using my keys instead of the keys used to sign the BAR posted on CB) is the addition of the following line:
Entry-Point-Name: Instagram Entry-Point-Icon: android/res/drawable-mdpi/icon.png Entry-Point-Type: Qnx/Android Entry-Point: android://com.instagram.android?activity-name=com.instagram.android.activity.MainTabActivity Entry-Point-User-Actions: access_shared,play_audio,post_notification,access_internet,use_camera,read_geolocation
I cannot say for sure, but perhaps this line has some importance?
EDIT: I'll also note here that this page states that native code is still unsupported on BB10; I can't see how this could be true following the evidence of Instagram and Netflix both functioning.
(I realise that all this has little to do with Netflix on the Playbook, but I started my analysis of the Instagram BAR here, so I figured I would continue it here too. If you can think of a more appropriate place, feel free to link to this post and/or the one above)
EDIT: A little more investigation shows that the author of this BAR is Jason Loustel, who according to a quick Google search is a software developer for RIM (I guess he never updated his Google+/LinkedIn after the name change). I figured that was interesting/noteworthy; looks like an "inside job" so to speak. [I considered not posting this part, but it was very easy to extract this info from the BAR file posted on CB, so I don't think it's a big secret. If I'm wrong and this is sensitive info, mods please remove this part]
Last edited by SifJar; 03-07-2013 at 05:19 PM.
- CrackBerry User
03-11-2013, 08:36 PM #74
- 22 Posts
LOL... I had noticed the same thing in the Manifest file... curious.
Edit... should clarify that I meant I noticed this in the manifest file of the working Netflix .apk, I haven't looked at the instagram .apk
Last edited by bill-ns; 03-11-2013 at 10:28 PM.