01-07-12 11:48 PM
170 12345 ...
tools
  1. BourneID's Avatar
    Is the browsere working for you in this version?
    What do you mean?

    If you mean if the webbrowser is working on my rooted 6149. Then yes. The webbrowser is working.

    If you are still 4869 and your browser is not working it could be that you need to install the browser from 4869. To do this download the sys.browser.bar from 4869 (previously on this thread) and install it using DDPB. I did not try browsing 4869 since it was only a step for rooting for me.

    Whoever wants to use 4869 for more than rooting should exchange ALL bar files after they are downloaded. The 4869 bar files can be found as rapidshare links in this thread.
    Last edited by BourneID; 12-28-11 at 02:29 PM.
    12-28-11 02:24 PM
  2. collapsed's Avatar
    oh so I should update to 6149

    it shows the "dead battery or turned off" thingie when I connect it to DM...Should I press Update or will it take me to os1?
    Last edited by collapsed; 12-28-11 at 02:30 PM.
    12-28-11 02:28 PM
  3. BourneID's Avatar
    I am not sure about this. My device successfully connected to DM and DM recognized i had 4869 is installed. It offered me to upgrade to 6149. That is what i did.

    Did you enable the Developer mode?
    Do not forget to root it while you are on 4869!
    collapsed likes this.
    12-28-11 02:34 PM
  4. collapsed's Avatar
    It wasn't in dev mode. It worked. You're awesome <3
    And yeah, I rooted it already. Tried to install an app via android market. I'll try to update and get it to work in 6149 too. Too bad they don't appear in the APPs list. Oh well running the launcher is also ok
    12-28-11 02:38 PM
  5. Datdoodted's Avatar
    The downgrade worked, but I'm still getting the /tmp/setuidgid cannot execute error. Can anybody help?
    12-28-11 03:25 PM
  6. collapsed's Avatar
    Go to BBDM, forget the device, do the jailbreak again, restore the .bbb file(created by dingleberry), you'll get an error, ignore it, restart the PB, do the SSH stuff
    Datdoodted likes this.
    12-28-11 03:28 PM
  7. Datdoodted's Avatar
    When ever I forget device, it tells me to reconnect, and I can't restore dingleberry.bbb without doing reconnecting.
    12-28-11 03:49 PM
  8. collapsed's Avatar
    Is your playbook in dev mode?
    Datdoodted likes this.
    12-28-11 03:58 PM
  9. Datdoodted's Avatar
    Is your playbook in dev mode?
    I got in, thank you so much. You don't know how hard I'm smiling right now.
    Wait, what's going to happen after Developer mode ends in ten days?
    Last edited by Datdoodted; 12-28-11 at 04:14 PM.
    12-28-11 04:07 PM
  10. BourneID's Avatar
    I got in, thank you so much. You don't know how hard I'm smiling right now.
    Wait, what's going to happen after Developer mode ends in ten days?

    Developer mode disables itself after a restart. You can enable and disable it as often as you want. After each reenable it will be on for 10 days (except if you restart)
    Datdoodted likes this.
    12-28-11 04:27 PM
  11. aburrobb's Avatar
    Hello all,

    thank you for your support. I did a little fooling around myself and i successfully flashed my Playbook to 2.0.0.4869.

    This is what i did:
    • Download the "qcfm.os.com.qnx.coreos.qcfm.os.sdk.4869.79475.sig ned.bar" and "sys.andoid.bar" from the link earlier in this thread.
    • Rename "qcfm.os.com.qnx.coreos.qcfm.os.sdk.4869.79475.sig ned.bar" to "qcfm.os.com.qnx.coreos.qcfm.os.sdk.6149.92203.sig ned.bar"
    • On 6149. Do a complete Backup of you Device (For later) with the Desktop Manager Software
    • Downgrade to 1.0.8.6067. (Switch off the device, use Desktop Manager Software)
    • Sign up at the Blackberry page for OS2.0 Beta.
    • IMPORTANT! User the Desktop Manager Software to update your device to 2.0.0.6149. During Step1 (Downloading) your Desktop manager will download the files to C:\Users\<USERNAME>\AppData\Roaming\Research In Motion\BlackBerry Desktop\Loader Cache. Now to the important part
    • RIGHT AFTER the Desktop Manager Software downloaded the file "qcfm.os.com.qnx.coreos.qcfm.os.sdk.6149.92203.sig ned.bar" and "sys.android.bar" copy your renamed "qcfm.os.com.qnx.coreos.qcfm.os.sdk.6149.92203.sig ned.bar" from above and the "sys.android.bar" to the Local Cache folder. (Do not wait untill all bar files are downloaded, switch with 4869 files right after the individual bar file is completely downloaded)
    • Now wait untill the download is completed. The Installer will install your 4869 bar files onto the device.
    • Voila. You are on 4869. Now you can root with dingleberry.


    This worked for me on two devices. I am still on 4869 on these devices.
    I used Desktop Software 6.1.0.36 and did it on Win7-32bit.
    I did not upgrade to 6149 yet. But if i do i would patch the backup with dingleberry before restoring.

    I cannot guarantee it will work, but it worked for me twice.

    Hope this helps.

    Regards.
    Perfect. Worked like a charm.
    Thanks a lot.
    12-28-11 04:31 PM
  12. Datdoodted's Avatar
    I updated to .6149.
    Correction- I did break it. Going to retry and stay on .4869.
    Last edited by Datdoodted; 12-28-11 at 05:09 PM.
    12-28-11 04:59 PM
  13. collapsed's Avatar
    You can fix it. I also upgraded and fixed it. It's posed on the 3rd page.
    12-28-11 05:23 PM
  14. nammerdude00's Avatar
    Hello all,

    thank you for your support. I did a little fooling around myself and i successfully flashed my Playbook to 2.0.0.4869.

    This is what i did:
    • Download the "qcfm.os.com.qnx.coreos.qcfm.os.sdk.4869.79475.sig ned.bar" and "sys.andoid.bar" from the link earlier in this thread.
    • Rename "qcfm.os.com.qnx.coreos.qcfm.os.sdk.4869.79475.sig ned.bar" to "qcfm.os.com.qnx.coreos.qcfm.os.sdk.6149.92203.sig ned.bar"
    • On 6149. Do a complete Backup of you Device (For later) with the Desktop Manager Software
    • Downgrade to 1.0.8.6067. (Switch off the device, use Desktop Manager Software)
    • Sign up at the Blackberry page for OS2.0 Beta.
    • IMPORTANT! User the Desktop Manager Software to update your device to 2.0.0.6149. During Step1 (Downloading) your Desktop manager will download the files to C:\Users\<USERNAME>\AppData\Roaming\Research In Motion\BlackBerry Desktop\Loader Cache. Now to the important part
    • RIGHT AFTER the Desktop Manager Software downloaded the file "qcfm.os.com.qnx.coreos.qcfm.os.sdk.6149.92203.sig ned.bar" and "sys.android.bar" copy your renamed "qcfm.os.com.qnx.coreos.qcfm.os.sdk.6149.92203.sig ned.bar" from above and the "sys.android.bar" to the Local Cache folder. (Do not wait untill all bar files are downloaded, switch with 4869 files right after the individual bar file is completely downloaded)
    • Now wait untill the download is completed. The Installer will install your 4869 bar files onto the device.
    • Voila. You are on 4869. Now you can root with dingleberry.


    This worked for me on two devices. I am still on 4869 on these devices.
    I used Desktop Software 6.1.0.36 and did it on Win7-32bit.
    I did not upgrade to 6149 yet. But if i do i would patch the backup with dingleberry before restoring.

    I cannot guarantee it will work, but it worked for me twice.

    Hope this helps.

    Regards.
    can u or someone make a short video showing how to do this if u cant i will try my best reading this.... i suck at technology
    12-28-11 05:55 PM
  15. danny3838's Avatar
    When I try to update my playbook through Desktop manager there are no updates for 2.0 that appear, even though I registered for beta 2.0. It only appears through the actual playbook device.
    Can someone please help me asap?
    12-28-11 06:07 PM
  16. Datdoodted's Avatar
    Yea, this just happened to me. How recently did you upgrade to 2.0?
    12-28-11 06:19 PM
  17. Bawlls's Avatar
    I for some reason receive a fatal error right after it begins the installation process. Desktop Software 6.1 current PB OS 1.0.8. Following the instructions and using the files listed above. Any ideas?

    Edit: I've gotten this error twice in a row.
    12-28-11 06:53 PM
  18. Datdoodted's Avatar
    Did you switch the files after they were downloaded, or during the installation period? Make sure you renamed the file and also moved over sys.android.
    12-28-11 07:05 PM
  19. Bawlls's Avatar
    I copied them both over right after I saw the second file finish downloading. There was approx 15 minutes before it switched to installing I believe. It asked me to overwrite them both so I'm guessing I renamed everything correctly. Trying once more right now.
    12-28-11 07:08 PM
  20. makaman's Avatar
    thank you, it seems to work!!
    12-28-11 08:12 PM
  21. danny3838's Avatar
    i downloaded the new 2.0.0.6149 about 30 min ago through my playbook device
    12-28-11 08:29 PM
  22. Datdoodted's Avatar
    @danny3838 you'll have to wait until tm then.
    12-28-11 08:33 PM
  23. danny3838's Avatar
    Hello all,

    thank you for your support. I did a little fooling around myself and i successfully flashed my Playbook to 2.0.0.4869.

    This is what i did:
    • Download the "qcfm.os.com.qnx.coreos.qcfm.os.sdk.4869.79475.sig ned.bar" and "sys.andoid.bar" from the link earlier in this thread.
    • Rename "qcfm.os.com.qnx.coreos.qcfm.os.sdk.4869.79475.sig ned.bar" to "qcfm.os.com.qnx.coreos.qcfm.os.sdk.6149.92203.sig ned.bar"
    • On 6149. Do a complete Backup of you Device (For later) with the Desktop Manager Software
    • Downgrade to 1.0.8.6067. (Switch off the device, use Desktop Manager Software)
    • Sign up at the Blackberry page for OS2.0 Beta.
    • IMPORTANT! User the Desktop Manager Software to update your device to 2.0.0.6149. During Step1 (Downloading) your Desktop manager will download the files to C:\Users\<USERNAME>\AppData\Roaming\Research In Motion\BlackBerry Desktop\Loader Cache. Now to the important part
    • RIGHT AFTER the Desktop Manager Software downloaded the file "qcfm.os.com.qnx.coreos.qcfm.os.sdk.6149.92203.sig ned.bar" and "sys.android.bar" copy your renamed "qcfm.os.com.qnx.coreos.qcfm.os.sdk.6149.92203.sig ned.bar" from above and the "sys.android.bar" to the Local Cache folder. (Do not wait untill all bar files are downloaded, switch with 4869 files right after the individual bar file is completely downloaded)
    • Now wait untill the download is completed. The Installer will install your 4869 bar files onto the device.
    • Voila. You are on 4869. Now you can root with dingleberry.


    This worked for me on two devices. I am still on 4869 on these devices.
    I used Desktop Software 6.1.0.36 and did it on Win7-32bit.
    I did not upgrade to 6149 yet. But if i do i would patch the backup with dingleberry before restoring.

    I cannot guarantee it will work, but it worked for me twice.

    Hope this helps.

    Regards.
    @Datdoodted : According to above instructions I have to wait until tmw to downgrade to 1.0.8.6067 correct? Then after I Sign up at the Blackberry page for OS2.0 Beta, an update should pop up on my desktop manager?
    12-28-11 08:41 PM
  24. congopr's Avatar
    how about if i install the two renamed files using ddpb tool having the 2.0.0 6149 installed all ready?
    12-28-11 08:41 PM
  25. Bawlls's Avatar
    I rebooted the PB and it seemed to solve the fatal error I received just in cased anyone else encounters this. Thanks a lot for this method. I'll post back after I'm finished with results.
    12-28-11 08:45 PM
170 12345 ...
LINK TO POST COPIED TO CLIPBOARD
";