[conite]

-- off topic --

Btw, Ive donwloaded the Mobile Tool but its looks weird , the software seem not compatible with my windows version or currupted. Cant click next. any clue ? looks like that ... Im on Windows 7 Professional

Attachment 441181

2 things:

1- It won't work with a pre-production unit, as no other OS is available.

2- You have to use compatibility settings on the app to have it display properly when you are using zoom settings on your desktop.

[atov361]

2 things:

1- It won't work with a pre-production unit, as no other OS is available.

2- You have to use compatibility settings on the app to have it display properly when you are using zoom settings on your desktop.

So I cant upload the autoloader you recommend to my Key2 ?

[conite]

So I cant upload the autoloader you recommend to my Key2 ?

Yes. But it is not done via the tool.

You run it directly.

Remove device passwords, reboot to fastboot mode, download autoloader and unzip, plug in device, run flashall.bat.

[atov361]

Yes. But it is not done via the tool.

You run it directly.

Remove device passwords, reboot to fastboot mode, download autoloader and unzip, plug in device, run flashall.bat.

Thanks @conite !! Really appreciate lets see how it goes.

[Bla1ze]

1st. From what I read from @Bla1ze, my blackberry is doomed. Cant have a long term fix, only autoloaders am I correct?

As I said, even autoloaders will only take you so far. The one I have won't accept anything beyond the first official OS.

[YeahIgottheKey2]

I have a pre-release version of the K2 and still receive software updates. But I think your version of the K2 is different. My bootloader is locked.

I seem to be getting updates pushed out by a specific carrier which is different than the carrier I have a sim card from.

tl;dr I'm at the mercy of getting updates from a random carrier and I have another carrier's sim in my phone. The updates aren't even coming directly from BB/TCL.

[conite]

I have a pre-release version of the K2 and still receive software updates. But I think your version of the K2 is different. My bootloader is locked.

I seem to be getting updates pushed out by a specific carrier which is different than the carrier I have a sim card from.

tl;dr I'm at the mercy of getting updates from a random carrier and I have another carrier's sim in my phone. The updates aren't even coming directly from BB/TCL.

All updates come directly from BBMo.

What is your device PRD?

[YeahIgottheKey2]

All updates come directly from BBMo.

What is your device PRD?

If that was the case, I would have already received the October update as it got pushed out for devices sold directly by BBMo.

PRD-63825-801.

[conite]

If that was the case, I would have already received the October update as it got pushed out for devices sold directly by BBMo.

PRD-63825-801.

That's not how it works.

Updates are pushed by PRD number - and ALL from BBMo.

What OS build are you on?

[YeahIgottheKey2]

That's not how it works.

Updates are pushed by PRD number - and ALL from BBMo.

What OS build are you on?

That's not how it works.

Updates are pushed by PRD number - and ALL from BBMo.

What OS build are you on?

ABG900.

North America has received the October update.

Bell, Rogers and Telus have not.

I usually get the update when Bell devices receive theirs. I have a Rogers sim in it.

[conite]

ABG900.

North America has received the October update.

Bell, Rogers and Telus have not.

I usually get the update when Bell devices receive theirs. I have a Rogers sim in it.

It's possible your device serial number was added to a special list to test OTA updates for Bell - effectively tying it to 63825-004.

[YeahIgottheKey2]

It's possible your device serial number was added to a special list to test OTA updates for Bell - effectively tying it to 63825-004.

Suuuuucks. I'd rather have updates the same time NA gets theirs.

[Vistaus]

If that was the case, I would have already received the October update as it got pushed out for devices sold directly by BBMo.

PRD-63825-801.

Please don't spread misinformation. I'm on a KEY2 sold directly by BlackBerry and I still haven't received the October update.

[YeahIgottheKey2]

Please don't spread misinformation. I'm on a KEY2 sold directly by BlackBerry and I still haven't received the October update.

That's YOUR problem then.

It was pushed out for devices sold directly by BBMo in NA.

https://docs.google.com/spreadsheets...gid=1381535354

[Vistaus]

That's YOUR problem then.

It was pushed out for devices sold directly by BBMo in NA.

https://docs.google.com/spreadsheets...gid=1381535354

No, the spreadsheet says SOON for mine.

Edit: ah, you didn't make it clear in your original post that you were talking about NA.

[Golfdriver97]

I only skimmed the thread, not much experience with BB android, but have a fair amount of Android rooting experience in general, and these are my takes:

1. Given the screenshot, there is no evidence it's rooted; the bootloader is unlocked, yes, but not necessarily rooted.

2. Is it not possible to obtain the proper official build and flash that via Fastboot commands (now would be a good time actually since the BL is unlocked)?

[Bla1ze]

Is it not possible to obtain the proper official build and flash that via Fastboot commands (now would be a good time actually since the BL is unlocked)?

Only BlackBerry Mobile would have the capability to override the built-in OS cutoff.

[YeahIgottheKey2]

if the bootloader is unlocked, what's stopping someone from giving the device to XDA developers to develop a root?

[conite]

if the bootloader is unlocked, what's stopping someone from giving the device to XDA developers to develop a root?

You still can't install an OS that isn't signed by BlackBerry. So, you won't get very far.

[YeahIgottheKey2]

You still can't install an OS that isn't signed by BlackBerry. So, you won't get very far.

They can't reverse that with an unlocked bootloader?

[atov361]

They can't reverse that with an unlocked bootloader?

Yeah, thats what Im saying

Ok, my bootloader is unlocked ... so XDA might do whatever they want ? Im not that advance in rooting ... Ive done it several times ... they are pretty straight forward.

Tomorrow, Im going to post as SOLVED, my issues and Im going to explain it how I make it work. So other people can use it, as a parcial fix.
@conite thank you for all the help !! Autoloaders thumb up !!

[atov361]

Hey thank you for all the Help and Feedback

@conite u make it happen so, I really appreciate.

As you all know, I started this thread with some screnshots regarding I had issues with my K2.

- I thought it was Rooted
- It has a pre release OS
- DTEK issues (poor score, with Blackberry internal use only message)

After @conite help me, he recommended to download and install the ABI067 Autoloader. Usually, they use the Mobile Tool to install it, but as mine is a Pre-Release OS is not possible. So it has to be done directly.


First, I had to set my K2 into FASTMODE. Turn off, and turn on and volume down at the same time. At the begging I thouht I had to take one more step, but @conite told me THATS FASTMODE (newbie here).

So, I ran the .bat file in the Autoloader, follow and few indicated steps, and intalled it succefully in my K2.




After I restored my K2 with the backup, and everything was fine and running great (I even felt it faster)

So to answer all my inicial issues I discover this:

- My phone is not rooted, its just a pre-relase OS with Unlocked Bootloader (maybe it can be rooted or something in there with XDA developers) with that knowledge I answer my first two issues.
- About Dtek issue with Poor Rating, well as @Bla1ze said very clear, even with the Autoloader it will just be a temporary short term fix. And Im going to be cristal clear with this.



Dtek version 1.1.11.527 is the lastest version that works with my K2 (with ABI067 Autoloader installed) before that I can only use the version that I came with I dont really remember but it was version 1.1.9.XXX.

I said this because, when I upgrade DTEK to version 1.1.11.536 (lastest version in Play Store) I had the same issue again with Poor Rating and all that.

I hope this really works for other people with same issue, and hope that I explain myself as best.

[YeahIgottheKey2]

It's possible your device serial number was added to a special list to test OTA updates for Bell - effectively tying it to 63825-004.

Yes. The IMEI was added to the special list I'm pretty sure or so I was told!

[ElDesmenuzador115]

Does BB have official support channels in your country OP? Wondering if they would be interested in getting the device back and swapping you a production version.

They will not replace it.

[jcrutchvt2010]

Could you search your device using any file manager app for any files ending in .tkn? That original build should've been loaded with tcl_debug.tkn although I'm not sure where those get stored.