What is the difference between ABG366 and ADB796? I have 796 and is working OK, so just to check if I should go thru flashing 366 if there is no real difference. I might skip it if there is nothing new or fixed between those two.
What is the difference between ABG366 and ADB796? I have 796 and is working OK, so just to check if I should go thru flashing 366 if there is no real difference. I might skip it if there is nothing new or fixed between those two.
Sep patch instead of July.
But there seems to be a leapfrog pattern here. I suspect the BBB100-1 devices to get Oct soon. The rest might have to wait until Nov. ¯\_(ツ)_/¯
But there seems to be a leapfrog pattern here. I suspect the BBB100-1 devices to get Oct soon. The rest might have to wait until Nov. ¯\_(ツ)_/¯
I hope so. I tried both abg366 and abg044, and with each one my device shows as not certified in the play store. I tried doing thing like signing out, 32 seconds reboot, reinstalling Play Store app, etc. But the same result on both patches, device is not certified. As a result, Google Pay is completely toast as I can no longer add any payment cards.
So, the automatic update on our BE KEYone German T+mobile showed ABG 366. Now we have done the update with the autoloader from the first post, no wipe, and all works perfectly fine, so thanks for the effort put in the autoloaders. We had had no issues like lag or such before either, just as a side note.
Now, I need to ask - as it is our first autoloader since BB10 - will it show any future updates now, or not? I've read somewhere that under certain circumstances updates will not be shown anymore? Thanks for now..
EDIT: the device was bought in Switzerland BBB 100-2, PRD-63117-036
So, the automatic update on our BE KEYone German T+mobile showed ABG 366. Now we have done the update with the autoloader from the first post, no wipe, and all works perfectly fine, so thanks for the effort put in the autoloaders. We had had no issues like lag or such before either, just as a side note.
Now, I need to ask - as it is our first autoloader since BB10 - will it show any future updates now, or not? I've read somewhere that under certain circumstances updates will not be shown anymore? Thanks for now..
EDIT: the device was bought in Switzerland BBB 100-2, PRD-63117-036
You'd only have an issue with updates if you installed an OS that your variant would otherwise not get.
PRD-63316-701. Autoloader installed with wipe. Only issue is that the convenience key is borked. I go into settings under gestures/shortcuts to assign actions but it only shows advanced settings and I can't assign any action to the convenience key. I have run a hardware diagnostic and the key itself passes the test.
That is not because of Autoloader.
I updated from the official announced update from my phone and faced the same issue. but It can be solved easily.
go to the gestures/shortcuts menu (advanced setting), just turn on normal profile, then tap exactly on the phrase "normal profile". you can now set what you want from convenience key.
Autoloader for testing. ABG366 Oreo 8.1 for KeyOne. Don't use if you are in China (and should already have it anyway). Don't use if you are on AT&T or sprint. I haven't tested this personally yet but should work on most KeyOne. Don't recommend the no-wipe script but you can try if you desire. As always, use at your own risk and let me know if you have any questions. Thanks! This appears to have issues on Verizon but that is likely due to the fact that Verizon hasn't whitelisted Oreo just yet (and may never)
Remove any screen lock from your device first.
Download the zip file in the OP. Extract it. Turn off your phone. Press and hold power and volume down until you see the blackberry bootloader screen. Plug in your phone to your computer. Open a command prompt in the folder you extracted the downloaded file (In the folder, hold ctl, shift, then right click and you should see "open command prompt (or powershell) window from here). Then type flashall.bat and press enter.
This is all presuming you are using Windows. This will do a wipe (if you selected wipe script) and install the new version. Let me know if you have any questions. If you are on a mac/linux run the .sh scripts in terminal (make sure you are running as admin and again that your screen lock passwords are completely removed).
hello guys! I have some issues with my keyone. The story is something like that: i purchase a keyone last year, after a update, my sim doesnt work. no service / service for one sec and so on... after i realize that its about ABG366 go to guarantee and today i go to the shop and he change my phone. well, good... but after i instal the updates on android i have the same problem. on new device. its a problem with that update... what can i do?
Blackberry key one PRD 63117- 039 MODEL : BBB100-2
hello guys! I have some issues with my keyone. The story is something like that: i purchase a keyone last year, after a update, my sim doesnt work. no service / service for one sec and so on... go to guarantee and today i go to the shop and he change my phone. well, good... but after i instal the updates on android i have the same problem. on new device. its a problem with that update... what can i do? Os: ABG 366 The network is Vodafone Romania.
Model: BBB100-2
Hi all,
I have just finished the update, but when rebooting, the phone stuck at boot menu (the one which green writings). It cannot launch the OS. And the led blinks twice rapidly avery 5 seconds.
My model is BBB100-7.
Any hint there ?
Thanks guy.
After check it is from Indonesia... unfortunately.
I can read on the docs that * denotes specially-signed OS builds (can't use a universal autoloader)
The problem is I have already upgraded via the Mobile Upgrade tool, it works for a few hours and the symptoms reappear, phone becomes VERY slow, windows stop responding, the SIM is not recognized, and the phone reboots again and again. Same like before the update.
Anyone has encountered the same issue here?
Thanks
Thanks guy.
After check it is from Indonesia... unfortunately.
I can read on the docs that * denotes specially-signed OS builds (can't use a universal autoloader)
The problem is I have already upgraded via the Mobile Upgrade tool, it works for a few hours and the symptoms reappear, phone becomes VERY slow, windows stop responding, the SIM is not recognized, and the phone reboots again and again. Same like before the update.
Anyone has encountered the same issue here?
Thanks
Try using the Mobile Upgrade Tool, but do not install any apps or restore any information.
I've already tried this... upgrade with mobile Upgrade Tool. Same behaviour after fresh upgrade, without any app installation nor configuration.
Maybe a hardware problem ?
Sometimes the device becomes responsive but this does not last long. I'm wondering if there is any way to check thoroughly the hardware components to detect any failure. Or any possibility to get kernel messages or diag/debug file, like the command dmesg or journalctl on linux ?
Thx
I've already tried this... upgrade with mobile Upgrade Tool. Same behaviour after fresh upgrade, without any app installation nor configuration.
Maybe a hardware problem ?
Sometimes the device becomes responsive but this does not last long. I'm wondering if there is any way to check thoroughly the hardware components to detect any failure. Or any possibility to get kernel messages or diag/debug file, like the command dmesg or journalctl on linux ?
Thx
It seems to be a hardware issue. You've done what you can.