how to upgrade patched v12 to v13?

[Ivan]

hi, how to upgrade to v13 if we have used jailbreak that breaks updates?
is there an existing way (out to re-flashing it with a clean /system)?

or exists a way to get only essential parts for upgrading to a patched one v13 without touching /data or init scripts modifications?

thanks

[AdvancedHACKERniV1]

1 Sec..

I'm creating a zip for that.

But you should find a clean system.img and put at the root of your sdcard.

And you should modify the Nokia ota package to not flash recovery as doing so will change your keys.

You can find the ota package at "/data/fota/downloaded/update.zip" I think.

On Saturday, December 29, 2018 at 11:22:58 PM UTC+5:30, Ivan wrote:

An answer please?

[AdvancedHACKERniV1]

Here is the zip:

[AdvancedHACKERniV1]

Before flashing, ask anyone to verify if I've properly created the zip.

[AdvancedHACKERniV1]

Copy the ota package before flashing RestoreSystem.zip

[Ivan]

hi, thank you for the answer.

i have understand what prevent the v12 to use whatsapp:
the telephonic part works well (SMS,add contacts) but the app don't see any internet connection.
i think that we have to modify a part into the build.prop file in /system because the app don't see the device as a whatsapp capable.
i'm not sure but i think the problem is there.

[Ivan]

we need to compare the build.prop files from v12 and v13 and seeing the differences

[Ivan]

is there someone with the v13 that could give me his build.prop file?

adb shell pull /system/build.prop

thank you

[Three]

Please find attached.

I think you will be best off by downloading the update.zip, patching it not to update the /system partition, only all other partitions, and add a patched /system v13 from someone else. [like I did :-) ]

[Peter Knight]

can someone please tell me how to get the update.zip patched and a patched v13 thanks and how do i flash it i am on a patched v12

[Ivan]

thank you PuriSnit. i'd like to know what parameters prevents the whatsapp client to connect the internet on v12.
i hope the answer is there and not belongs to a new driver version.
in this way the app could work on the phone without update the firmware.

[speeduploop]

No... I think it's just missing features/depencies.

I assume that whatsapp for Jio was so needed that they include some additional/private 'extensions' in their version of KaiOS - just to make WhatsApp work like it should. Now - to make it work on Nokia 8110 - they had to backport those added apis/binaries and included them in v13.

(this would mean that whatsapp will never work completely on v12 -- and that they have to wait with official launch of WA on Nokia until enough users updated to v13)

After updating to v13/rooted I will 'diff' both filesystems -- to see what was changed...

[AdvancedHACKERniV1]

We can upgrade from v12 to v13 without a clean system image.

We can convert "system.new.dat" into an image file with a tool called "sdat2img" which is a python tool.

Then we can remove the recovery and system patch and the lines in updater-script that install the patches from the update package.

After installing the update, we can manually flash the new system image file via dd.

You can use the package that I've uploaded above (RestoreSystem.zip) which writes system.img from the root of your sdcard to the system partition.

[Ivan]

thank you speeduploop,
it can be interesting to know what that 25 mb of update effectively changes/adds.

could it be possible to enlight the zip with the essential parts needed,and eventually could it be installed through recovery?

there must be a solution for this mistake :/

[Three]

@AdvancedHacker,

I haven't yet seen that sdat2img tool, however, the system.new.dat file only contains the new patch parts for the system, so I assume this tools needs the old system.img where he places the patches as required & then creates a new image, does this not require the old system to be untouched?

[speeduploop]

The sda2img tool does exactly the same as the upgrade/patch function of the recovery -- only it does it on your PC.

So yes, you need an unchanged image of the v12-system. (v12 + patch = v13)

And you would also need to patch the other updated images (wlan/lte...) manually...
So I think it's just easier to reflash a original system and use the normal ota-update.

(but if you want to keep root you have to patch the system before reboot or recovery will be replaced on first boot)

[Ivan]

Then is not so simple for who have made the hard patch to v12, I wont loosing modifications on my phone (and I'm too lazy to repeat all again)

[speeduploop]

Yes - both ways will reset the system-partition. But if you bootstrapped to /data/opt most mods will stay (init-script / swapfile) you only have to set the invocation-line in the init-script on /system again.

And you have to either edit the update.zip to not update recovery or the system-partition after update / before reboot.

(the ota-update will not update recovery directly - it just sets a patch-file and a script in system which updates recovery on first boot)

[Ivan]

 Is there possible to revert the omnijb-final.zip?

I'm trying to uderstand if there is a possible way to revert the installation, this is theomnirun.sh:

#!/tmp/busybox sh

# OmniJB package

# SMITH-omnirun by Luxferre

SETTINGSFILE='/system/b2g/defaults/settings.json'

PREFFILE='/system/b2g/defaults/pref/user.js'

OMNIJA='/system/b2g/omni.ja'

WEBAPPS='/system/b2g/webapps/webapps.json'

# mount /system and /sdcard

/tmp/busybox mount -t ext4 -o rw /dev/block/bootdevice/by-name/system /system

/tmp/busybox mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard

# create backup files on memory card

TIMESTAMP=`date +%s`

/tmp/busybox cp $SETTINGSFILE /sdcard/b2g-settings-backup.${TIMESTAMP}.json

/tmp/busybox cp $PREFFILE /sdcard/b2g-pref-backup.${TIMESTAMP}.json

/tmp/busybox cp $OMNIJA /sdcard/b2g-omni.${TIMESTAMP}.ja

/tmp/busybox cp $WEBAPPS /sdcard/b2g-webapps-backup.${TIMESTAMP}.json

# unmount /sdcard after creating the backup

/tmp/busybox umount /sdcard

# replace the developer menu setting entries

/tmp/busybox sed -i 's/"developer.menu.enabled":false/"developer.menu.enabled":true/g' $SETTINGSFILE

/tmp/busybox sed -i 's/"debug.console.enabled":false/"debug.console.enabled":true/g' $SETTINGSFILE

echo "pref('developer.menu.enabled', true);" >> $PREFFILE

echo "pref('debug.console.enabled', true);" >> $PREFFILE

# try to unpack current omni.ja version

/tmp/busybox mkdir /tmp/omnipatch

/tmp/busybox cp /system/b2g/omni.ja /tmp/omnipatch

cd /tmp/omnipatch

/tmp/unzip -q omni.ja

/tmp/busybox rm omni.ja

# patch the ImportExport module

/tmp/busybox sed -i 's/_openPackage(appFile,meta,false);/_openPackage(appFile,meta,true);isSigned=true;devMode=true;/g' modules/ImportExport.jsm

# try to repack omni.ja file

/tmp/zip -qr9XD omni.ja * > /sdcard/zip_logs.txt

# replace omni.ja with the jailbreak-patched version

/tmp/busybox cp omni.ja $OMNIJA

# place OmniSD package into system installation

/tmp/busybox cp -r /tmp/omnisd.831337.xyz /system/b2g/webapps/omnisd.831337.xyz

# patch webapps.json registry

MANCONT=$(/tmp/busybox cat $WEBAPPS)

echo -n ${MANCONT%?} > /tmp/webapps.json

/tmp/busybox cat /tmp/webapps.json /tmp/decl.patch > $WEBAPPS

# unmount /system

/tmp/busybox umount /system

echo "Changes applied"

[speeduploop]

It's possible to revert the changes.... but it won't allow you to update normally.

The reason is, that even if you revert all changes 'per-file' -- the system-partition on the bit-level keeps changed.

(if you modify a file, a copy with the new content will be saved on another location - revert the changes --> additional copy on additional location....)

For the normal update-patch to work the system-partition have to be original down to the bit-level.

I think I will find time this week to do my update to v13 --> I'll post my zips then. (eventually even a pre-rooted v13)

[Three]

I actually have a v13 patched-system partition (credits: 4pda.ru), meaning:

1. The recovery auto-installer is already removed.
2. Telnet localhost root is implemented.
3. OmniSD installer included in system.

I can share it on the group later.

Then you would just need to:

1. Patch the updater-script from your update.zip to not verify & update the system partition, by removing from:
"ui_print ("Verifying system partitions...
till where it starts:
"ui_print ("Patching boot image...
[Then, re-sign the zip with test-keys].

2. Flash the patched zip, which will update all partitions besides system. (Recovery will also not be updated, as mentioned earlier).

3. Power off the phone, reboot in recovery, and now flash the patched v13 system. (Can be done by using AdvancedHacker's RestoreSystem.zip, and having the patched system image placed in the root of the SD card).

Then, you're fully updated to v13, but still have telnet root access & test-keys for recovery :D

Last, but not least. I take no responsibility on anything I suggest & share. :/

[Pavel Melnik]

Why don't you patch it at once? Why you two times apply patch?

--
You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bananahacker...@googlegroups.com.
To post to this group, send email to banana...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/1680aca55f8.274f.4d0fbcba59d3df19bf8cde900231fc8a%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[PuriShnit]

You are right...

 The reason why I do it in 2 steps:

1. Because if adding it in the zip, it increases the time for signing + verifying (+ extra syntax for larger memory in Java during signing)

2. the updater-binary HMD uses doesn't support some commands,

so it was difficult for me to add command to run bash file that will make dd from scdard.

however, here's the link for the v13system.img:

https://drive.google.com/file/d/1kBn_rwNoeOJ7OgTj5N4wOt0Y4Wv9rJzf/view?usp=sharing

(if using RestoreSystem.zip, rename and place as appropriate).

[Ivan]

thank you!

how I can flash the phone from xubuntu?

[speeduploop]

The updater-binary HMD uses is quite recent - some commands were replaced by 'better' alternatives ;)

(set_perm is now set_metadata and has more power...)

And updater-binary is capable of writing images to flash -- you don't need bash/dd :D

(with updater-binaries >= android-5)

Complete command set of updater-binary used in KaiOS is here in source (with edify-examples)

--> https://github.com/kaiostech/platform_bootable_recovery/blob/LF.BR.1.2.8/updater/install.c

Just for fun I added my 'template' for zips -- complete with my keys and my 'create' script...

(create uses 'signapk' -- you need to adjust if you use another signing-tool)

[Ivan]

I don't understan what I must do with this.

With this I can download and install the v13?

[speeduploop]

No - not directly... it's my template for zips. And was an answer to PuriShnit...

(on the other hand: one could use it as a base for the flash script --> image in it's tmp-folder, flash-command in updater-script)

[Ivan]

1. So...througt an useful tool from Luxferre that made recovery of all the v12 I've succesful recovered my system with all the demo games preinstalled but without removing my apps (out of omnisd).
   I've downloaded the v13 but it gaves me an error.
2. Then I've made a factory reset and I've re-downloaded the update to v13....installing....I've the same error.
   
3. Now I've made again a factory reset and reinstalled onmisd-final.zip (because some apps are important for me tomorrow at work)
   
   
   

as you can see I've downloaded the update without install it. Is someone already have the zip it can be useful to made a custom update from it and for all....if no tell me where I can extract that package.

[Ivan]

PS: I've failed to made the installation of the update because I've touched boot files (I think using telneton.zip and bootstrapon.zip). If other havent used other tools out the smith.zip or omnisd-final.zip the methods before with that tool could work successfuly.

[Ivan]

this is the error I have:

E0005: "EMMC:/dev/block/bootdevice/by-name/boot:15084828:67037923f483507d059ca20c0cee5d6e2f47de83:15084828:660159b1224d00b74818ca9f21f0bc44515fce4e" has unespected contents:

E:Essor in /data/fota/downloaded/update.zip

Error 7

Installation aborted

[speeduploop]

Absolutly NO.

telneton.zip and bootstrapon.zip are only modifying /system -- nothing else.

[Ivan]

If no....how I've touched boot files? I've read that telneton breaks OTA updates on XDA. If no...is better. 

So...is not important now, if we can  bypass the check of the OTA update with a patch it can be perfect, we cam flash it on recovery by sdcard.

adb pull /data/fota/downloaded/update.zip

doesn't work.

[speeduploop]

I can't say why your boot-hash isn't correct. My root-zips break ota-update because they modify /system.

(but I haven't checked what exactly OmniJB/SD or the repair-zip modifyes)

About the v13-update: try -->

adb shell
busybox telnet localhost
cp /data/fota/downloaded/update.zip /data/local/tmp/update.zip
exit
exit
adb pull /data/local/tmp/update.zip

-- you can't pull from a root-only directory so copy as root to a directory from where you can pull...

[Ivan]

I've already done this,the update.zip is on my sdcard...i can't sent you the package because the Kaios file manager have no pick function,and now i'm going to work. i'll not come home before 13 hours from now.

[Three]

@Ivan

You probably didn't make any changes to your boot.img.

But if you replaced all partitions with a dump you received from Luxferre, this might be the cause. (the boot.img verification is the first on the list).

The update.zip you get, is matching to 'your' firmware (maybe country-specific), but not to a different.

Have you ever tried installing the update.zip before installing any other orignial v12 firmware? Did you then also get a boot.img error? You probably didn't, but only got stuck @ system partition verification.

So, if you restore all 'your' partitions, (hopefully you have a dumpall.zip backup from yours), then the only mismatching partition would be the 'system', so you can skip that part, and instead flash the ready v13 patched system.

I can't wait to finally hear that you're on v13 & enjoying WhatsApp :D

[Hossain Mohammed Shoaib]

If ivan have any problem with boot.img file
i have my own clean boot.img

[Ivan]

Hi guys, I'm back! This is my v13-update.zip

I hope there is a solution for it.

[Peter Knight]

Do we just flash this in normal recovery mate

[Hossain Mohammed Shoaib]

Hi ivan
Today i am just checking the 12repair_signed.zip is it working on my phone but that's a big mistake by me after downloading the update i am just clicked install and no way to back and now i am crying ,
I am on v13 with just three installed app file manager,facebook,whatsapp by omnisd
But a good thing v13 gives you smooth and faster navigation
But i loose omnisd, what i should do?

[Ivan]

I'm using your system.bin image instead of the sistem.bin into the v12packagebackup of luxferre...afther I'll say if I have success

[Ivan]

"signature verification failed"

Il giorno sabato 29 dicembre 2018 10:42:23 UTC+1, Ivan ha scritto:

hi, how to upgrade to v13 if we have used jailbreak that breaks updates?
is there an existing way (out to re-flashing it with a clean /system)?

or exists a way to get only essential parts for upgrading to a patched one v13 without touching /data or init scripts modifications?

thanks

[Ivan]

E:footer is wrong

E:signature verification failed

Installation aborted 

[Three]

What exactly are you trying to do?

My system.img is v13, what will you gain by inserting it into v12?

The reason you got this error, is probably because you have to sign the zip again after changing any of its files. Did you sign it again?

[Ivan]

Ok, is the first time I do this...I've undestand what I'm doing now...I have to edit the /META-INF/MANIFEST.MF with the right key

OK....where is the key? :P

[Luxferre]

Hossain,

Here are the instructions of reinstalling OmniSD that work on v13: http://omnijb.831337.xyz/ - under "Alternative (and safer) way" section.

I'm only on this soft-jailbreak now and it's fine.

[Hossain Mohammed Shoaib]

Dear luxferre
I am honored i'll try it
Thanks a lot:)

[Ivan]

sorry but i leave.
i've no real interest about whatsapp, is not what i was aspect from my device when i brought this phone, i was just curious about this app to write an article on the Italian blog Nokioteca.net to let know to Italy about the bananahackers reality and hard work,to take us success.
more people know about us and more we early can get support and attention.
it can made our work more easy for implementing new apps and functionality.
whatsapp is the only app that requires firmware update/changes.
browser speed,emulators,more complete functions into the single apps can be implemented without system and hardware's instructions change.

i only hope that every other future app for this devices (as a possible Skype,discord or hangouts client) can work on every device without version,country or brand limits.
i sincerely hope that whatsapp could be the only absolute case of useless app for some devices.

i hope on universality of all the functions on Kaios, the same for Alcatel/Jio/CAT/Doro users, like the Linux heart must be.

CLOSED

[speeduploop]

Sorry to hear that... I now had time to update (v12-rooted --> v13-rooted) -- and if your phone has the same product-key (mine has TA1059-AAROW1DS03ROW1) I could create a complete update zip which then ignores changes of your partitions.

(I dumped my v13-partitions)

I myself now use 13.00.17.01 -- but with v12-recovery.

(v13 is really snappier)

[Ivan]

before dumping my phone i've enlightened /system from some apps,at the first boot after flashing i've seen a strange and unusual speed. and after i've reconfigured swapfile with your bootstrapon.zip....i don't say you :)
now i'm ok,trying to update have already steal too much time for me. now stop...i prefer to increasing single apps and working on the already existent ones.
really i don't need whatsapp.
i'm just now hypnotized from my phone to talk with the forum.
i can't imagine with whatsapp on my phone what could be the results.
after all...is always Kaios 2.5 with Firefox 48 the update...what is the real change? whatsapp support?
ok,i don't care about it.
thank you :)

[speeduploop]

I don't use whatsapp either... never did - never will... I would never use an IM forcing me to leak my phone number ;)

But v13 is an improvement: the device is snappier (keyboard input for example) - but yes, without release-notes I will need some time to see where other changes are.

[speeduploop]

I found some additional changes:

-- WLAN: nearby networks now works... (in v12 - if you scan you will kick your connected network)

-- it seems there are new options when managing sounds and ringtones

-- radio (wlan/lte... whatever) firmware is updated - I'll see if it's better than before... I had frequently really short wlan-disconnects - would be cool when they were gone.

[Ivan]

whatsapp installation stucks on "initializing..." on the v12.

contacts can be added from the app on the Contacts app on v12. then only the network part doesn't works.
but a friend of mine and my girlfriend have seen my number activated on their whatsapp for android on their smartphones.
then the only change needed comes from the network part. we must seen what was changed with the update.
the os version is the same for all the firmware versions.

[Hossain Mohammed Shoaib]

No you need to exit and re enter when see  "initializing..."

--
You received this message because you are subscribed to a topic in the Google Groups "comp.mobile.nokia.8110" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bananahackers/q3eW1IXKtDY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bananahacker...@googlegroups.com.
To post to this group, send email to banana...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/a5532a59-e4d4-486a-b6bb-72e84468267f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Hossain Mohammed Shoaib]

it also happened on v13!

[Hossain Mohammed Shoaib]

Dear Ivan they can see you on whatsapp

but you can't see them on Nokia 8110 V12

because whatsapp need some essential binaries to work perfect 

so KaiOS and HMD Global added these binaries on v13 update

and you're  right we must seen what was changed with the update.

the os version is the same for all the firmware versions.

sorry 
if i gave wrong information to you

[Ivan]

it's useles downloading and installing the full parts of an official update when there can be implemented only some parts,like the single apps pre-installed and updated.
the ffos default browser (gui) was faster more than the Kaios default version.
the same for the apps keyboard, system, settings, contacts etcetera etcetera...is not an hardware's property the usability of single functions in this case.

ps: i've said time ago in this thread that /system/build.prop files in the 2 firmware versions are different. i'm sure that changing something in that file could made the difference!

[Hossain Mohammed Shoaib]

you're right:)

--
You received this message because you are subscribed to a topic in the Google Groups "comp.mobile.nokia.8110" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bananahackers/q3eW1IXKtDY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bananahacker...@googlegroups.com.
To post to this group, send email to banana...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/7d88da83-f41a-43c4-8c3d-96fcb9f93399%40googlegroups.com.

[Hossain Mohammed Shoaib]

v13 comes with pre-installed twitter app but why?

i don't understand that what are doing hmd and KaiOS

we need just updated browser firefox v52 up

[Ivan]

browser is not updateable...geko is the old engine of Firefox, now Firefox is based on "quantum". geko is obsolete,but not bad.

[Hossain Mohammed Shoaib]

yea that's bad

because we need hangouts google+

you notice that all KaiOS device without nokia 8110 has built in file manager why?

On Sat, Jan 5, 2019 at 8:27 PM Ivan <ivan1...@gmail.com> wrote:

browser is not updateable...geko is the old engine of Firefox, now Firefox is based on "quantum". geko is obsolete,but not bad.

--
You received this message because you are subscribed to a topic in the Google Groups "comp.mobile.nokia.8110" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bananahackers/q3eW1IXKtDY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bananahacker...@googlegroups.com.
To post to this group, send email to banana...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/1fb62a80-e3f5-40f0-b021-c2d787cac71f%40googlegroups.com.

[Ivan]

about build.prop

search on google "unlock all bands on Qualcomm device"

if you look,for example, the line:

ro.telephony.default_network=5

5 seems that the device is able to use to the 2g/edge network. higher is the value and higher is the network. in the Alcatel go flip this value is 10,that seems all the bands are enabled (2g/3/4g).
in both the firmware versions this parameter is the same (5). it can be useful to know more about this file and his options.

[speeduploop]

So... I did a 'diff' on the /system-partitions -- so you get a picture...

Happy reading and reading and reading... :D

[Ivan]

thank you

[Hossain Mohammed Shoaib]

awesome speeduploop

On Sat, Jan 5, 2019 at 8:43 PM speeduploop <marcus_...@web.de> wrote:

So... I did a 'diff' on the /system-partitions -- so you get a picture...

Happy reading and reading and reading... :D

--

You received this message because you are subscribed to a topic in the Google Groups "comp.mobile.nokia.8110" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bananahackers/q3eW1IXKtDY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bananahacker...@googlegroups.com.
To post to this group, send email to banana...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/d7b601b8-9800-4f8d-aeb6-efe4824bcbaa%40googlegroups.com.

[Ivan]

it is too big for textr app, i'll read this at home. thank you again :)

[speeduploop]

Luxferre pointed out that in his region the TA-1048 is the only certified version...

And I rechecked -->

While on my box and phone-label it says TA-1048 (dual-sim / europe) the update-script/-log uses TA1059-AAROW1DS03ROW1 as the request-ID on my phone...

TA-1059 would be dual-sim / other countries...

That's strange.

(probably all dual-sims are handled as 'other-countries' internally -- but it's hard to guess how many diferent firmware-versions are out there)

[Hossain Mohammed Shoaib]

Mine is also TA-1059

--

You received this message because you are subscribed to a topic in the Google Groups "comp.mobile.nokia.8110" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bananahackers/q3eW1IXKtDY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bananahacker...@googlegroups.com.
To post to this group, send email to banana...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/abf04c5d-3405-40c8-b457-67e29737562f%40googlegroups.com.

[Pavel Melnik]

All is the same TA1059-AAROW1DS02ROW1

I write it in thread "What is your Nokia 8110 model?"

More interesting is why are somebody is got v14.

С уважением, Павел.

> --
> You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bananahacker...@googlegroups.com.

> To post to this group, send email to banana...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/abf04c5d-3405-40c8-b457-67e29737562f%40googlegroups.com.

[speeduploop]

So the region-specific differences like WLAN-channels and LTE-frequencies are runtime-decisions?

That would make things easier....

The request is quite comprehensive... they could send every single phone or sim-card an other fw-version.

(I really can't say why they send my IMSI to the server - don't like it)

But it's possible that different regions or even providers get different versions.

On Saturday, January 5, 2019 at 5:01:57 PM UTC+1, Gluck666 wrote:

All is the same TA1059-AAROW1DS02ROW1

I write it in thread "What is your Nokia 8110 model?"

More interesting is why are somebody is got v14.

С уважением, Павел.


On Sat, Jan 5, 2019 at 6:35 PM speeduploop <marcus_...@web.de> wrote:
>
> Luxferre pointed out that in his region the TA-1048 is the only certified version...
> And I rechecked -->
>
> While on my box and phone-label it says TA-1048 (dual-sim / europe) the update-script/-log uses TA1059-AAROW1DS03ROW1 as the request-ID on my phone...
> TA-1059 would be dual-sim / other countries...
>
> That's strange.
> (probably all dual-sims are handled as 'other-countries' internally -- but it's hard to guess how many diferent firmware-versions are out there)
>
> --
> You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to bananahackers+unsubscribe@googlegroups.com.

[Pavel Melnik]

Yes, that strange... And there is complicated software update procedure. "check","download_request",download, "notify".

Hopefully they don't use https :)

С уважением, Павел.

On Sat, Jan 5, 2019 at 7:18 PM speeduploop <marcus_...@web.de> wrote:

So the region-specific differences like WLAN-channels and LTE-frequencies are runtime-decisions?

That would make things easier....

The request is quite comprehensive... they could send every single phone or sim-card an other fw-version.

(I really can't say why they send my IMSI to the server - don't like it)

But it's possible that different regions or even providers get different versions.

On Saturday, January 5, 2019 at 5:01:57 PM UTC+1, Gluck666 wrote:

All is the same TA1059-AAROW1DS02ROW1

I write it in thread "What is your Nokia 8110 model?"

More interesting is why are somebody is got v14.

С уважением, Павел.


On Sat, Jan 5, 2019 at 6:35 PM speeduploop <marcus_...@web.de> wrote:
>
> Luxferre pointed out that in his region the TA-1048 is the only certified version...
> And I rechecked -->
>
> While on my box and phone-label it says TA-1048 (dual-sim / europe) the update-script/-log uses TA1059-AAROW1DS03ROW1 as the request-ID on my phone...
> TA-1059 would be dual-sim / other countries...
>
> That's strange.
> (probably all dual-sims are handled as 'other-countries' internally -- but it's hard to guess how many diferent firmware-versions are out there)
>
> --
> You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to bananahacker...@googlegroups.com.

> To post to this group, send email to banana...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/abf04c5d-3405-40c8-b457-67e29737562f%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bananahacker...@googlegroups.com.

To post to this group, send email to banana...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/bae7e380-9d24-4d2e-841b-2692410c10d7%40googlegroups.com.

[Hossain Mohammed Shoaib]

yea you are right

pavel

To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/CAMCoCCwTOJ8GTj4AZMdQ0WhwNyCmZwpzcmjyk6WKgz4TReFCqg%40mail.gmail.com.

[speeduploop]

Sems they use plain-text GET

GET /check.php?id=35341909xxxxxx&curef=TA1059-AAROW1DS03ROW1&fv=13.00.17.01&type=FIRMWARE&mode=2&cltp=10&cktp=2&pcard=0&rtd=1&sdtd=2&cktd=0&chnl=2&imsi=262032441xxxxxx&id2=353419090xxxxxx&vend=QUALCOMM&mdnu=Nokia81104G&mdna=qcom&clvs=2018062112&osvs=KaiOS2.5&dvid=30694257-2249-43ed-a53f-4f53d6xxxxxx&mccs1=262&mncs1=03&mccn1=262&mncn1=03&cktd=0 HTTP/1.1

User-Agent: KaiOS FOTA Client v1.4.7 

Date: 2019/01/05 01:03:10 GMT+1

Cache-ontrol: no-cache

Accept: */*

HOST: mst.fota.kaiostech.com

(edited)

On Saturday, January 5, 2019 at 6:05:23 PM UTC+1, Gluck666 wrote:

Yes, that strange... And there is complicated software update procedure. "check","download_request",download, "notify".

Hopefully they don't use https :)

С уважением, Павел.

On Sat, Jan 5, 2019 at 7:18 PM speeduploop <marcus_...@web.de> wrote:

So the region-specific differences like WLAN-channels and LTE-frequencies are runtime-decisions?

That would make things easier....

The request is quite comprehensive... they could send every single phone or sim-card an other fw-version.

(I really can't say why they send my IMSI to the server - don't like it)

But it's possible that different regions or even providers get different versions.

On Saturday, January 5, 2019 at 5:01:57 PM UTC+1, Gluck666 wrote:

All is the same TA1059-AAROW1DS02ROW1

I write it in thread "What is your Nokia 8110 model?"

More interesting is why are somebody is got v14.

С уважением, Павел.


On Sat, Jan 5, 2019 at 6:35 PM speeduploop <marcus_...@web.de> wrote:
>
> Luxferre pointed out that in his region the TA-1048 is the only certified version...
> And I rechecked -->
>
> While on my box and phone-label it says TA-1048 (dual-sim / europe) the update-script/-log uses TA1059-AAROW1DS03ROW1 as the request-ID on my phone...
> TA-1059 would be dual-sim / other countries...
>
> That's strange.
> (probably all dual-sims are handled as 'other-countries' internally -- but it's hard to guess how many diferent firmware-versions are out there)
>
> --
> You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to bananahackers+unsubscribe@googlegroups.com.

> To post to this group, send email to banana...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/abf04c5d-3405-40c8-b457-67e29737562f%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bananahackers+unsubscribe@googlegroups.com.

[Ivan]

How I thinked some apps are modifyed:

/system/b2g/webapps/system.gaiamobile.org/application.zip

• the system app from v12
  

• the same app but from v13
  

this is an example, surelly there are other things to know

[Pavel Melnik]

Don't tell anyone :)

Change to fv=11.00.17.03 and you get to next level :)

С уважением, Павел.

> To unsubscribe from this group and stop receiving emails from it, send an email to bananahacker...@googlegroups.com.

> To post to this group, send email to banana...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/abf04c5d-3405-40c8-b457-67e29737562f%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bananahacker...@googlegroups.com.

To post to this group, send email to banana...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/bae7e380-9d24-4d2e-841b-2692410c10d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bananahacker...@googlegroups.com.

To post to this group, send email to banana...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/89184b7e-4c86-4cc5-b0af-0c46f8e6fcf7%40googlegroups.com.

[speeduploop]

What do you mean?

I'm already on v13-rooted...

I used 3 zips:

-- 1. reflash v12-system

-- 2. normal fota-zip

-- 3. my adjust-zip --> dump v13-system, replace recovery-install-script with no-op, delete recovery-patch, adjust expect.recovery-id

(NO reboot in between step/zip 2+3!)

I used 3 steps because that way it's reusable when the next update arrives...

[Pavel Melnik]

Yes, I have almost the same. But I created v13-system on PC. So when it came v14, I update my original v13  to v14 on PC and disable new recovery and update same way...

In Linux there is multiple way to do same thing.

С уважением, Павел.

--

You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bananahacker...@googlegroups.com.
To post to this group, send email to banana...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/4aa08ed8-3813-4796-a135-8e19bbe61721%40googlegroups.com.

[Ivan]

how have you done?

[speeduploop]

There is a Linux-tool for patching Android images with an ota-update --> https://github.com/erfanoabdi/imgpatchtools

The result is a complete image  ready for flashing...

[Hossain Mohammed Shoaib]

hi how can it work?

--
You received this message because you are subscribed to a topic in the Google Groups "comp.mobile.nokia.8110" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bananahackers/q3eW1IXKtDY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bananahacker...@googlegroups.com.

To post to this group, send email to banana...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/0f9a1858-32ed-4752-9d8d-f65c1ac4277b%40googlegroups.com.

[speeduploop]

There is a thread on XDA... https://forum.xda-developers.com/android/software-hacking/dev-img-patch-tools-sdat2img-ota-zips-t3640308

(I never tried this -- did the whole update / modify on my phone... but others succeeded with this tools)

[Hossain Mohammed Shoaib]

Speeduploop can go to hangout i've a problem invitation sent

--

You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bananahacker...@googlegroups.com.

To post to this group, send email to banana...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/656c2044-bc06-4d66-acf1-6693551fe388%40googlegroups.com.

[Ivan]

Hi all, for the chronicle:

I've tryed to install the system.img of the v13 with the two scripts available

RestoreSystem

4bash

in both the cases the execution was faster and "without errors (that seems)", but at the startup I was stocked on the "Powered by KaiOS" bootlogo before restartinga again and again, and again.....

then I have re-installed my personal system.img (v12) and restored all like before. Noway people...it seems I must be on v12

[PuriShnit]

The v13 system might be dependent on the boot.img.

So, staying with v12 boot and updating to v13 system, is probably not going to work...

[Ivan]

uhm...I understand that if I risk to uploading the boot.img and something goes whrong...I can say goodbye to a restore and to my phone :\

[speeduploop]

yes.... v13 updates some quite low-level thingies...

so the cleanest way would really be to reflash /system to a clean state, then install the normal update -- and before reboot deactivate the update of the recovery...

(if you have the fota-update.zip for your device/region - I could give you my zips for the first and last step if you are brave enough to try...)

I also have a v13-recovery with test-keys to flash at the end.

(but I think you could also use the recovery Luxferre provided -- that's v13 with test-keys and adb)

[Ivan]

what do you advise me to do?

if the phone dies, I can not dedicate myself to the forum projects (I do not know where to start).

Should I wait for the release of GerdaOS?

[speeduploop]

If you do a clean reflash of v12-system and then update there isn't a risk to kill your phone - only a small risk to loose test-keys...

(if you accidently do a full reboot after fota-update - before patching out the recovery-update - the test-keys are lost)

I did this with 3 zips - installed one after another without reboot to the system.

But I had to reboot to recovery between the steps so there was a risk of accidently booting full.