[thurask]

Newer loader: https://forums.crackberry.com/blackb...loader-1117851

DISCLAIMER: This is untested, and I have no guarantee if this will work. You have been warned.

https://mega.nz/#!rAdkRbDD!OOtKU_G8L...iS4i-zLtf1cQd0

Above is, hopefully, an autoloader for OS AAM481 for all KEYones. Thanks to TCL slipping up here and there, the raw files (radio, OEM partition, etc) for all KEYone variants, released or unreleased, have been made available. This 7z file consists of those raw files, plus hand-modified versions of the flashall scripts common to autoloaders, so that it can read the device details via fastboot and load the right files accordingly. Therefore, it shouldn't matter if you have a carrier version or an unlocked version, GSM or CDMA, black or silver, it should work.

Since I don't have a KEYone, and even if I had one it would only be one version, that's why I'm asking for those with KEYones and a bit of spare time to try loading this and see if it works. Especially welcome are contributions from those with Sprint KEYones, to see if I got the OEM partition checking right, and unlocked CDMA KEYones, since they're still on an OS from like three months ago.

The procedure should be the same as any other autoloader for a BB Android device, i.e. download, extract, plug in your phone (in fastboot mode), and run the .bat/.sh file. It will wipe your phone, of course; this is an autoloader after all.

Reply here and tell us if and how it works.

Edit: If you want to try this without wiping your phone (still, back up!), consider this:

If anybody tries this, please remove the line about the "securewipe" and the line about flashing "userdata" and try it like this first (dirty flash). It could probably make the update without erasing all userdata.

[bunky1971]

Thurask, it won't come across through text, but a HUGE thanks to you, Contite and the other coders that keep us berryheads up on the newest releases!!

[mbirth]

If anybody tries this, please remove the line about the "securewipe" and the line about flashing "userdata" and try it like this first (dirty flash). It could probably make the update without erasing all userdata.

[selimpusat]

[QUOTE=thurask;12981669]DISCLAIMER: This is untested, and I have no guarantee if this will work. You have been warned.

https://mega.nz/#!rAdkRbDD!OOtKU_G8L...iS4i-zLtf1cQd0

Above is, hopefully, an autoloader for OS AAM481 for all KEYones. Thanks to TCL slipping up here and there, the raw files (radio, OEM partition, etc) for all KEYone variants, released or unreleased, have been made available. This 7z file consists of those raw files, plus hand-modified versions of the flashall scripts common to autoloaders, so that it can read the device details via fastboot and load the right files accordingly. Therefore, it shouldn't matter if you have a carrier version or an unlocked version, GSM or CDMA, black or silver, it should work.

Since I don't have a KEYone, and even if I had one it would only be one version, that's why I'm asking for those with KEYones and a bit of spare time to try loading this and see if it works. Especially welcome are contributions from those with Sprint KEYones, to see if I got the OEM partition checking right, and unlocked CDMA KEYones, since they're still on an OS from like three months ago.

The procedure should be the same as any other autoloader for a BB Android device, i.e. download, extract, plug in your phone (in fastboot mode), and run the .bat/.sh file. It will wipe your phone, of course; this is an autoloader after all.

Reply here and tell us if and how it works.[/QUOTE @thurask
Please find a solution to the following notification problem

[thurask]

Please find a solution to the following notification problem

You'll have to wait for BlackBerry to fix it, it's present in any build AAL964 or newer. This isn't the thread for that regardless.

[thurask]

If anybody tries this, please remove the line about the "securewipe" and the line about flashing "userdata" and try it like this first (dirty flash). It could probably make the update without erasing all userdata.

Good idea. I'll edit the first post.

[citystars41]

@thurask downloading now. ill try it out shortly

[citystars41]

Good idea. I'll edit the first post.

What's a good backup app? Is there anything that backs up all apps instead of having to install them manually?

[thurask]

What's a good backup app? Is there anything that backs up all apps instead of having to install them manually?

Nothing can do a complete backup without root, unfortunately. If the app has developers that care and a recent enough API level it should hook into Google's automatic Drive-based app backup, if the app itself doesn't have a backup function. If it does connect to Drive, though, then installing apps should happen automatically once you log back in to your Google account.

[hoytbowhunter]

Do you just install it with the mega link?

[thurask]

Do you just install it with the mega link?

You'll need a computer, but at least you can use a Mac or Linux machine with Android loaders.

[jcrutchvt2010]

You'll need a computer, but at least you can use a Mac or Linux machine with Android loaders.

I'll give it a go with my cdma keyone. What was the trick for determining pull URL?

[thurask]

I'll give it a go with my cdma keyone. What was the trick for determining pull URL?

I didn't. AAM481 comes from someone running the TCL desktop updater and saving the zip file it downloads (h/t @citystars41).

[Kumba42]

If anybody tries this, please remove the line about the "securewipe" and the line about flashing "userdata" and try it like this first (dirty flash). It could probably make the update without erasing all userdata.

Can confirm that manually flashing each partition via flashboot, in the order specified, but without "oem securewipe" OR the "userdata" partition does work to go back a build. Am now running the AAM481 build. However, definitely still seeing the issue with Android dropping Exterminatus on my recent apps and their background processes. Anyone know where to find an AAL964 autoloader? That build definitely had a lot less issues for me.

[Kumba42]

Can confirm that manually flashing each partition via flashboot, in the order specified, but without "oem securewipe" OR the "userdata" partition does work to go back a build. Am now running the AAM481 build. However, definitely still seeing the issue with Android dropping Exterminatus on my recent apps and their background processes. Anyone know where to find an AAL964 autoloader? That build definitely had a lot less issues for me.

It looks like AAL093 is a total no-go on T-Mobile/GSM. It won't even detect the SIM card, see the baseband modem (reports as unknown), or find a working cell signal. In my attempt to fix that, I temporarily hard-bricked the phone (white LED blinks three times, pause, repeats; no screen power on or vibration). To break out of that, had to pry the back of the phone off, unscrew the battery connector, and de-energize it, then while holding PWR+VOL_UP (yes, up, not down), plug the USB cable in. That got me to a fastboot screen where I was able to flash back to AAM481.

So it looks like I am stuck with the notification bug now unless someone can find an AAL964 autoloader.

**Note: Did not wipe the device before backrevving to AAL093 -- could be something goofy in /data that prevents the SIM card from getting detected. Everything works fine on AAL964 and up, however.

[thurask]

An AAL964 autoloader would require the help of someone with a KEYone that has AAL964 as the latest OTA software, but I think that window has passed.

[jcrutchvt2010]

An AAL964 autoloader would require the help of someone with a KEYone that has AAL964 as the latest OTA software, but I think that window has passed.

FYI, CDMA owners AAM is working for me just modify the flashall script to flash USA modem, devcfg.mbn, and oem_common to be safe. I have had token issues so the flash all script as-is couldn't validate the loader so I took out that check. The full script I used is available in the keyone upgrade tool thread.

[thurask]

FYI, CDMA owners AAM is working for me just modify the flashall script to flash USA modem, devcfg.mbn, and oem_common to be safe. I have had token issues so the flash all script as-is couldn't validate the loader so I took out that check. The full script I used is available in the keyone upgrade tool thread.

There should only be two in vivo configurations for the BBB100-3:

1. devcfg.mbn, oem_common.img, NON-HLOS-usa.bin (unlocked)
2. devcfg.mbn, oem_sprint.img, NON-HLOS-usa.bin (Sprint)

If anyone here has a Sprint KEYone I'd appreciate the output of

fastboot getvar device
fastboot getvar variant
fastboot getvar subvariant
fastboot getvar hlos-sig-tag

from a phone in fastboot mode and a PC with ADB/fastboot set up.

[jcrutchvt2010]

There should only be two in vivo configurations for the BBB100-3:

1. devcfg.mbn, oem_common.img, NON-HLOS-usa.bin (unlocked)
2. devcfg.mbn, oem_sprint.img, NON-HLOS-usa.bin (Sprint)

If anyone here has a Sprint KEYone I'd appreciate the output of

fastboot getvar device
fastboot getvar variant
fastboot getvar subvariant
fastboot getvar hlos-sig-tag

from a phone in fastboot mode and a PC with ADB/fastboot set up.

Verizon CDMA output:
fastboot getvar device: bbb100
fastboot getvar variant: usa
fastboot getvar subvariant: no result (shows "subvariant: ")
fastboot getvar hlos-sig-tag: also blank

[thurask]

Verizon CDMA output:
fastboot getvar device: bbb100
fastboot getvar variant: usa
fastboot getvar subvariant: no result (shows "subvariant: ")
fastboot getvar hlos-sig-tag: also blank

Yeah, that's why loading the Verizon OEM image didn't work. That one requires your hlos-sig-tag and/or subvariant to be "vzw". The Sprint one should look the same except for "sprint" as hlos-sig-tag and/or subvariant.

[jcrutchvt2010]

Yeah, that's why loading the Verizon OEM image didn't work. That one requires your hlos-sig-tag and/or subvariant to be "vzw". The Sprint one should look the same except for "sprint" as hlos-sig-tag and/or subvariant.

Yeah full fastboot oem info out below. not much to be gained probably.

[RadioTech]

FYI, CDMA owners AAM is working for me just modify the flashall script to flash USA modem, devcfg.mbn, and oem_common to be safe. I have had token issues so the flash all script as-is couldn't validate the loader so I took out that check. The full script I used is available in the keyone upgrade tool thread.

If you have the VZW variant, do you just run the autoloader or is there some other work around you have to do to get it to work?

[thurask]

Yeah full fastboot oem info out below. not much to be gained probably.

What was the error that came up when running the script?

[jcrutchvt2010]

What was the error that came up when running the script?

Something like the loader could not be verified for your device. I will look up in the script the exact words.

[jcrutchvt2010]

If you have the VZW variant, do you just run the autoloader or is there some other work around you have to do to get it to work?

I posted the edited flashall.bat script I used in the keyone update tool thread.