does anyone can use Blackberry Balance after the autoload? switching work and personal feature thingy...
does anyone can use Blackberry Balance after the autoload? switching work and personal feature thingy...
I upgraded my Dev Alpha A to 10.0.09.2372 and everything works great with exception of Mobile Radio. At the end of setup i saw a message about my SIM card not being recognized. I connected using WiFi instead, but now when no matter what I do with the SIM card (remove, reinsert, reboot, etc) it just wont let me turn on the mobile radio. The SIM card worked just fine before the upgrade.
Also I lost all my camera photos!!! I didnt realize this flash process does complete wipeout not like OTA OS upgrade.
Go it i have my dev alpha A up n running with the 10.0.09.2372 version personally think that the Twitter and Facebook apps are very poor shame
Notes.
I have the watermark.
Cant download BB Bridge
Did you insert your SIM card and does it work? Mine cannot detect the SIM card even though the card is 100% working. I am in process of reloading to see if that helps.
I re-ran the autoloader image again and it the radio is back on !!!!! Back in business!
Not to be offensive in any way, but is this not illegal? BlackBerry hasn't officially provided the full OS image to developers, and also has not made BB10 open source meaning its proprietary software owned by them which should not be released by anybody. If I am wrong, feel free to correct me.
Update.
I've just installed the 10.0.10.261 version in Dev alpha A and is working fine too.. So both work.
Sideloaded WhatsApp works fine for me with 10.0.10.261 on my Dev Alpha B.
I am thinking the other way. Leaking this ROM benefit RIM more than hurting them.
If you take one step back from all the excitement here and reread what we have now. The key is these 2 leaked ROM are loader "specifically make for the Dev Alpha by Device ID". There is another ROM linked for 2372 that is made for the real Z10 device ID and that one DOES NOT work on the Dev Alpha (check post back on page 6 or so when this all started).
So I am pretty sure there won't be a lot more of these new ROM being made anyway in the future; so even if someone else is keen to leak more there won't be much else to leak anyway.
And most of the Dev Alpha will be returned/exchanged. Those left on the street will be stuck with these leaked ROM IF they don't brick it in the first place. Even if they let you keep using it you will soon give up anyway because of the 1GB RAM (new app will only tax your RAM more). So these Dev Alpha will be extinct pretty soon by itself anyway.
The benefit right now that RIM needs is for us to show as much people as possible how great BB10 is .... and without a Full BB10 OS is it impossible to do.
If I am RIM I will be smiling right now. They need all the help they can get for tomorrow.
the same with the 2nd one :-((((
any ideas ?! :((
RIM Wireless Device Command-Line Auto-Programmer Version 3.10.0.15 (Win32) [Dec
20 2012 22:31:59]
Copyright 2012 Research In Motion Limited
Connecting to Bootrom: Connected
[ Uploading RAM Image 0x80130230 ] [############## 100 ##############]
QCFMv1/v2 Hybrid File
containing: Radio
Header Version: 2.0
Num Chunk Headers: 3
Headers Length: 65312
Chunk Header:
Type: 0x0C
Chunk Header:
Type: 0x8C
Chunk Header:
Type: 0x0A
Signature Trailer:
EC521_512 Signer: 0x48584E51 (QNXH-OS-1)
EC521_256 Signer: 0x4C584E51 (QNXL-OS-1)
[ Writing 0x0066C000 ] [############## 100 ##############]
QCFMv1/v2 Hybrid File
containing: IFS, OS, User File System
IFS/OS Version: 10.0.10.261 DEV
Hardware ID: 0x06001A06 RIM BlackBerry Device
Metrics Version: 3.18
Build Date: Jan 27 2013
Build Time: 16:42:10
Build User: ec_agent
STP Protocol Ver: 0.0.4 (release OS)
Header Version: 2.0
Num Chunk Headers: 6
Headers Length: 65120
Chunk Header:
Type: 0x06
Chunk Header:
Type: 0x08
Chunk Header:
Type: 0x06
Chunk Header:
Type: 0x05
Chunk Header:
Type: 0x09
Chunk Header:
Type: 0x89
Signature Trailer:
EC521_512 Signer: 0x48584E51 (QNXH-OS-1)
EC521_256 Signer: 0x4C584E51 (QNXL-OS-1)
[ Writing 0x0001570A ] [############## 99 ###############]
Error: Failed to load images.
Error: Security error.
i got it working too...seems like a few reboots got it to work or just some time? im not sure why...or how.
You think there will be another update tomorrow? Since they must've, could've, lets hope....made some bug fixes and major additions since last week?
If we proceed with this leaked version, are we able to rollback to original?
Just loaded up the Dev Alpha A build and everything looks like it's working (haven't tried any Android apps yet). Weird thing is that I can't download Linkedin from App World....
Do we can reverse engineering the .exe file to make it able to wipe watermarks and do more customization stuff?
Wow, I'm impressed with this OS build. I was expect something slow and laggy, but it's not much different from the current dev alpha OS currently. Imagine it with 2gb RAM in the Z10 and the LE device....
Ok for me it just sits there 'Connecting to Bootrom:' and nothing ever happens. Help?
Note that I followed the instructions about turning it off, pressing vol + - and power. It starts up but nothing ever happens...
Unfortunately still nothing. Guess this is another one of those things that works for everyone except me. I have that kind of curse on me...
TheMarco, disable password if you have one, after disconnect the device, reboot and reconnect, white for the driver to install and try again.
Mine fired the loader quickly after that
Posted using CrackBerry App on BB10
for developer, it is not illegal.. we will try as much as possible to 'abuse' the dev alpha ;)
Download the Autoloader.
Turn off your BlackBerry 10 Dev Alpha device.
Run the file Autoload.exe.
When prompt shows �Connecting to Bootrom�, connect your device to your computer and turn it on.
If you have a password set on your device, type your password when prompted.
After your device restarts, complete the set up wizard.
.261 doesn't have watermarks (none that I can see anyway) but I am using it on a Dev Alpha B, so I don't know if it'll work on yours.
Yes! Finally. Thanks guys. Removing the password did it. Booting up the OS now :D
I have watermarks with the .261 build. Will try a security wipe and reload .261