yashsingh1/xdaforums huggingface dataset:
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Thanks for sticking with me [MENTION=3924647]bigrammy[/MENTION], this goes way above and beyond what I expected from anybody - if I am ever as far North as Huddersfield then I am certainly gonna buy you a drink!

Here is where I am at: Managed to get the phone back on stock 7.1.1 boot and recovery (any attempts at loading 8.0 always fail). Boots to Orange State message and stops. Can get into recovery then bootloader, but any command at all with fastboot results in "..." (3 dots) and nothing else - so I cannot even boot to TWRP anymore.

Currently downloading the rom that you posted, not the fastest speed atm. No Windows here, just a Linux user like you, and using SP_Flash_Tool_v5.1828_Linux as recommended.

When I was in TWRP previously I had edited updater-script, simply flashing what I needed, no idea why it failed as definitely the same variant: "[ro.product.name]: [TA-1020_00WW]".

Shall keep you posted, but this is doing my head in and need to walk away from it from time to time...
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Smegging hell [MENTION=3924647]bigrammy[/MENTION], it's only bloody worked!!! The flash completed and the phone has booted to Oreo July 2018 patch! How great is that!?!

So I am now going to attempt to unlock the bootloader. Two things that I noticed: the bootloader is locked and the phone serial number has changed - how bizarre.

Correct me if this is wrong:

- enable developer options

- enable oem unlocking and usb debugging

- reboot to bootloader

- fastboot oem dm-verity; flash lk; reboot-bootloader; oem key; oem unlock; boot twrp

- install magisk

- finally purge and nuke anything google from the device

- get some sleep zzzz

It's a shame that I cannot add more thanks to your posts!
[Nokia 3 Guides, News, & Discussion] bigrammy:
No problem just glad you managed to recover the phone :good:

You need really to get SP_Flash_Tool working though if at all possible as I find it invaluable for mediatek devices.

Sony did away with it on their MediaTek devices and when you mess up with those it's a paperweight as many C4/C5 owners found out :crying:

If you manage to Flash ALL the 8.0 your Orange State should be gone as this is like a factory update.

It's not really necessary to flash "Para" because your not in a recovery boot loop but I will leave that up to you.

HERE is the No Para scatter file.zip Just swap it for the one in the ROM download.

I have also included the "Read Back by scatter" options.ini which you can replace in the root of the SP_Flash_Tool folder.

This will load all the partitions automatically so you can place a X in the box of the ones you want to back up in the Read Back tab

It will name them ROM0 ROM1 etc etc these align with the sys0 sys1 of the scatter file.

For Example:

In the scatter file sys0 is = to the preloader

ROM0 is = to sys0 which is = to the preloader

ROM0 which will be in the root of the SP_Flash_Tool folder after the Read Back is complete

should be renamed according to it's "File-Name" in the scatter eg "preloader_ne1.bin"

If that make sense :laugh: :eek:

When your back running 8.0 give me a shout and we will go through getting it rooted and hopefully not trip the orange state.

In the meantime I will look at trying to improve TWRP so It can mount data correctly. :eek:
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Hey [MENTION=3924647]bigrammy[/MENTION], looks like we cross posted and missed each other. I could not wait and ran through the fastboot commands. They all worked successfully and I can boot into the system and developer options now says that my bootloader is unlocked. But I have got the Orange State message back which you previously said is not a problem, at least it still boots.

The thing now is that I cannot boot into TWRP. I go to bootloader and issue the "fastboot boot twrp.img" command but the phone just reboot normally. Hmm, what have I forgotten?
[Nokia 3 Guides, News, & Discussion] bigrammy:
Slow down a bit :laugh:

We need to use SPFlashTool so you can pretty much forget fastboot for now.

Regarding the serial:

:eek: Was panicking for a minute then but just checked mine and it's different to my mates sn number unless Para has something to do with it :eek:

Can you give me the last 2 digits of your SN and the last 2 digits of your imei just need to double check you ain't inherited my mates.

I will work on the rooting and recovery in the morning it's late now. ZZZZZZZZZZZZZ
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Sorry [MENTION=3924647]bigrammy[/MENTION], slowing down now - was just excited at having a working phone again.

IMEI: XXXXXXXXXXXXX22

Serial: NE1XXXXXXXXXXX57

Just checked para with a hex editor and it's all zeros apart from text that reads "ENV_v1 off-mode-charge=1" so it's not there.

If I need to flash the whole rom again then just shout, that way I can get rid of the orange state and check if serial changes again.

I need sleep too - shall try to sneak doing more on this while at work tomorrow.
[Nokia 3 Guides, News, & Discussion] bigrammy:
Cool me too.

Our SN and IMEI differ pheww :D

PS: Yes flash it all again except para the Idea is not to have Orange State! ;)
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Update [MENTION=3924647]bigrammy[/MENTION]: Just noticed that in the about section, my phone is now a TA-1032, before it was a TA-1020.

From getprop before:

[ro.product.model]: [TA-1020]

[ro.product.name]: [TA-1020_00WW]

and after:

[ro.product.model]: [TA-1032]

[ro.product.name]: [TA-1032_00WW]

This is probably why the serial number has been interpreted differently with this rom.

According to specifications, they are identical except that TA-1020 is a single sim unit and the TA-1032 is dual sim.
[Nokia 3 Guides, News, & Discussion] bigrammy:
I can assure you those have not come from this rom it's 100% TA-1020 and has never been anything else so I can only guess it's from one of your previous flashes. :confused:

I flash my own phone with the exact same ROM to test it and mine says TA-1020.

Anyway now rooted with no Orange State so we can probably fix that id.

Will upload it tomorrow.

BTW You did flash ALL parts didn't you?? normally these id's are set in cda and hidden if I remember correctly that is.
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Yep, all parts flashed, again. No more orange state. Wonder if phone is actually dual sim and it came misconfigured when I got it. Would explain problems. Can you explain your method of unlocking and rooting without orange state?
[Nokia 3 Guides, News, & Discussion] bigrammy:
I posted a explanation some where in this Nokia forum about the bootloader unlock surviving once done but they can and have disabled fastboot to some extent it seems I will find the post later as too late to go into it again.

More likely a hangover of a previous flash. It should do a region check then assign it's TA-xxxx but it needs wifi to do this I think unless some data did not get wiped or some protected partition like frp or some place else is holding on to it. :eek:

Do not do anything except flash the below with SPFlashTool.

No unlocks no fastboot etc etc simply flash and go.

Download:

patched boot.img is here and Magisk Manager is Here

Flash the boot with SPFlashTool

Copy the MM.apk to your sdcard click on it and install.

Done!!

TWRP will take a little longer :eek:
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Sorry for the delayed reply but (drumroll....)

Woohoo - success!!! Wow, what a journey. I see what you did; I did not know that MagiskManager could patch an offline boot image file.

I can live without TWRP for now, but it would be nice to have - do you have the device tree details? I may try to compile something in the next few weeks.

[MENTION=3924647]bigrammy[/MENTION] thank you very much for investing your time and effort into getting this done - hopefully this thread will help others too.
[Nokia 3 Guides, News, & Discussion] bigrammy:
Magisk doesn't and I don't want to say too much for the reasons below. :o

I don't think It's insecure really :confused:

See my post HERE which gives you my "theory's"

I really don't like taunting Nokia (FIH) as I am sure they read these forums too and they could if they choose lock this device down for ever very simply.

Remember Nokia are still pushing security updates it seems so ssshhh or they may well cut us off by the ****

These Phones are far from been "Nokia" or pure Android and are almost identical to my "Infocus M808" I even had the firmware they (FIH) sent to Nokia for approval (Android v6.0) some months before the device was released because the same Dev for the M808 was assigned the Nokia 3 it would seem because the M808 stopped getting updated and the Nokia 3 firmware's started appearing on his/her cloud (leaked) instead. :cyclops:

Needless to say and probably due to reading these forums the leaked firmware link went dead and the dev probably got it in the neck off FIH :eek:

This device needs a custom OS 100% as there is far far too much logging some would even call it spying by Nokia/FIH :eek:

Still lots more to do and I will keep you posted but for now root will have to be enough. (More data wipes may be required so don't build up too much :laugh: )

EDIT: Forgot to say I would probably Use the Device Tree for Moto E4 (woods) and (nicklaus) as plenty of development LineageOS etc etc. and same specs as this device.
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Hear, hear!
[Nokia 3 Guides, News, & Discussion] bigrammy:
[MENTION=5588897]JonnyTech[/MENTION] and [MENTION=8005568]SkaboXD[/MENTION]

DOWNLOAD HERE

Hi here is the latest TWRP with working mtp :victory: and a few clean up's.

Sadly I can't fix the decryption of data just yet so you will need to run un-encrypted for now.

Oreo TWRP builds are too large for the partition and I do not think the LK supports LAZMA compression which would bring it down in size. :rolleyes:

Another thing is Magisk does not disable forceencrypt and verity it seems and I posted in the Magisk help thread about this so maybe it will get fixed later. :rolleyes:

So for now you will need to copy/replace the fstab.mt6735 (Included) to /system/vendor/etc

Instructions:

Flash TWRP using SPFlashTool You MUST boot the recovery the very first time else it's replaced very very early in the boot process and the flash must be repeated. :(

Booting into recovery is a art in it's self which I would advice you to be well practised in first. :laugh:

(Note booting to recovery via adb does not seem to work so a manual boot to recovery is required unless some app will work like quickboot??)

Once in TWRP Format data and then from the TWRP Reboot > recovery

Once back in TWRP go to Mounts and tick system and toggle MTP Disable/Enable your sdcard's should now show up on the PC with data correctly mounted at /data/media/0 :good:

Copy the stock boot.img, Magisk 17.x.zip and the fstab.mt6735 to your sdcard.

Now flash the boot.img to boot then flash the Magisk .zip and copy the fstab.mt6735 to /system/vendor/etc replacing the original one then reboot.

First boot and the setup is very delayed/glitchy but once done (google configuring etc) reboot a couple of times and everything is smooth again.

End Result is TWRP 99% working, ROM rooted, data un-encrypted and No Orange State WARNING. :D
[Nokia 3 Guides, News, & Discussion] SkaboXD:
:clap: :clap: really nice, keep up with development, and for removing encryption, we need to modify fstab.mt6735 and another fstab to remove encryption or just use f2fs, encryption with it is automatically removed.
[Nokia 3 Guides, News, & Discussion] bigrammy:
Yes f2fs is the next thing to test out in a few days so lets just hope the kernel supports it and nothing trips the Orange state warning. :fingers-crossed:
[Nokia 3 Guides, News, & Discussion] SkaboXD:
If kernel supports f2fs on /data, then it will support /cache in f2fs too which means more performance.
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Excellent work, thank you [MENTION=3924647]bigrammy[/MENTION]. I was worried with the glitchy startup but eventually it booted. Well done, clear and simple instructions!

A system update just popped up: "Update Google Security Patch 2018-08". I am on the July 2018 version. Should I update?
[Nokia 3 Guides, News, & Discussion] JonnyTech:
OK [MENTION=3924647]bigrammy[/MENTION], I am up for further testing so shall hold off updating for now (or forever if a custom ROM comes along!).

I have seen that multi-stage update sequence on other devices before, seems to be their way of ensuring that everything gets done completely and thoroughly.

If you have MagiskManager installed then you don.t need a third-party reboot app, simply use the reboot menu in the "Modules" section - it works.
[Nokia 3 Guides, News, & Discussion] bigrammy:
[MENTION=8005568]SkaboXD[/MENTION]

(Download Removed until we can find out why the radio is tripping!!!!)

Here is the fully up to date (5th September) ROM for the TA-1020

All partitions that were updated by the OTA's are included in SPFlashTool flash-able ROM.

Note: All are stock unmodified .bin's and .img's

Be sure to exclude the recovery from the flash.

Be sure to re-run Magisk on the newly installed boot.img

Replace the fstab.mt6735 in /system/vendor/etc with the one included in the download.

Remember If you fail to boot to recovery after flashing with SPFlashTool first time the TWRP will be replaced and data will be encrypted so you will need to re-flash TWRP and the userdata.img from the previous ROM.

This update Seems not to be as glitchy but still takes a while to boot up :rolleyes:

F2FS seems not to work so will probably need a custom kernel built :rolleyes:

Final note using Magisk patched boot.img's breaks offline charging probably due to the Magisk "init" so there is very little can be done about that. :( Just make sure the battery never runs totally flat or you will need to re-flash the stock boot.img with SPFlashTool once thats done offline charging will work again.

It maybe time to see just how much debloating this ROM can take before breaking something so all experimentation's would be appreciated. :D
[Nokia 3 Guides, News, & Discussion] SkaboXD:
Tnx but i preffer Nougat, I'm still on Nougat December patch.

i have a thread of which apps you can safely remove from system so maybe that can help.
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Nice one [MENTION=3924647]bigrammy[/MENTION], I prepatched the new boot file and flashed that along with the rest of the ROM files. Seems OK, although it now wants me to update to the October release! Bah! I do keep debloating and breaking it, but not had time to work out why cos I never have enough time! Good work :)
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Help [MENTION=3924647]bigrammy[/MENTION], my phone no longer sees the SIM card. I tried factory resets and also the last ROM. It still thinks that it is a TA-1032 even though it is a TA-1020. No amount of rebooting or reflashing does anything. I have tried several SIMs from different networks. Any suggestions?
[Nokia 3 Guides, News, & Discussion] bigrammy:
Hmm not sure does your IMEI show up ok??

When did the sim detection break??

CDA and Hidden Normally set the device id I think.

Did you use OST (Nokia update Tool) or whatever it's called at some point as I think this writes stuff to the device and not sure if the device id is one of those :eek:

Or Did you flash the /nvdata from a TA-1032 at any time see below?

EDIT: Just done some digging around and found reference to the device id and firmware version in /nvdata/md/NVRAM/FIH_CUST/MCFG/HostPara

Viewed with HEX it says

Nokia TA-1020 Nokia 3 8.0.0 00WW_3_38D

so It maybe worth checking what yours says too.

note the FIH interference here :rolleyes:

Here is mine if you need to change it but make sure your on that firmware version "38D". HostPara

I also noticed a un-edited copy of the fstab.mt6735 and a fstab_ftm.mt6737 under /nvdata so I just edited those to see if that improves the reboot time or bricks the phone :laugh:
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Dialing #*06# shows a white box with text "IMEI" and nothing else. I have not had a SIM in it for a few days but it worked last week. Never used OST (I think that is a Windows app and I only use Linux) just SPFT and TWRP. Should I reflash specific partitions? Would love to know why it thinks that it is a dual SIM device too.
[Nokia 3 Guides, News, & Discussion] bigrammy:
Please re-read above I just edited it.

Sounds like nvdata or nvram got wiped please tell me you have a backup of these. :fingers-crossed:

EDIT My IMEI is gone too !!!!

EDIT 2: Seem like the September update disables the radio no baseband info either not sure how they have done that ?

I may need to flash the stock updates and see if it gets restored but I doubt it some how.

I think this has been done on purpose so thanks a lot nokia.

I will see if it can be fixed without a restore of the NVRAM and /nvdata
[Nokia 3 Guides, News, & Discussion] JonnyTech:
My HostPara file matches yours but the about page shows TA-1032. I do not have a backup of nvdata or nvram but I did note my IMEI (saved getprop output). You have no IMEI too but can your phone see the SIM? Do you still think that cda and hidden are to blame?
[Nokia 3 Guides, News, & Discussion] bigrammy:
I can't just work out what happened with my devices as I was sure it was ok but I tried flash a port and it didn't go too well. :laugh:

I even lost WiFi and had baseband unknown in settings so this may all just be a coincidence.

Anyway the device is now fully recovered without restoring any NVRAM or nvdata so here is what i did.

ROLL BACK TIME!! :cowboy:

Download this NE1-Oreo-TA1020.zip although I think you may already have it.

Side note: ( You can skip this part. I FORMATTED /nvdata only and manually with spflashtool on the September ROM but It made no difference on that ROM still no IMEI and no baseband or WiFi. :rolleyes: )

So just try the above ROM but use "Firmware Upgrade" instead of "Download" mode in SPFlashTool.

After this everything is working again. :victory:

Note you must flash ALL partitions so do not un-tick any

UPDATE: Ok while on the stock ROM above I just took all the available OTA's and I am now on the 5th October 2018.

SIM is detecting fine, IMEI # is present and correct, IMEI SV shows 41 which goes up by 1 with each update btw, WiFi works with full MAC address and Baseband shows date as 2018/09/26

So now I will see if rooting breaks it all again.
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Yes! My phone can detect a SIM again! Woohoo! It still thinks that it is the wrong model but at least it works. Thank you. I shall do the OTA updates now and post feedback on the results...

---------- Post added at 13:27 ---------- Previous post was at 12:45 ----------

I too am on the October update and the SIM still works. Also going to root it. Am about to flash TWRP. Is there an easy way to retrieve the boot image in order to patch it?
[Nokia 3 Guides, News, & Discussion] bigrammy:
Pheww! Glad you got the imei back :victory:

With regard to the boot image it's time to breakout your trusty SPFlashTool again and do a "Read Back" of the boot partition.

I gave you the read back by scatter modified option.ini with instructions already in one of the previous posts. :D

With regard to the PM I have no idea why your device persists to be a TA-1032 perhaps a search for the hw.id file mentioned in the hex code of the updateCDA once rooted maybe in order. :confused:

Not had time to re root just yet but will have a go this evening. Then I am back on shift so will go quite for a few days.

PS: Maybe a good time to grab a read back of the NVRAM and nvdata too just incase. :D

EDIT: I wonder if your "metadata" could be giving you the TA-1032 id

Looking and my metadata readback with HEX I see "SystemLocale en-GB" which I think has something to do with the device id also I notice in the OTA's /META-INF/com/android/metadata I see

ota-required-cache=324522496
ota-type=BLOCK
post-build-incremental=00WW_3_38F
post-timestamp=1538577343
pre-build-incremental=00WW_3_38D
pre-build=Nokia/TA-1020_00WW/NE1:8.0.0/O00623/00WW_3_38D:user/release-keys
post-build=Nokia/TA-1020_00WW/NE1:8.0.0/O00623/00WW_3_38F:user/release-keys
pre-device=NE1

So when you first setup after a factory reset is the default language English (United Kingdom) like mine??

I am thinking you maybe getting the TA-1032 OTA's because of a previous flash of a TA-1032 ROM :confused:
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Update: installed TWRP and patched boot.img and rebooted. All good, SIM card recognised. Realised that I forgot about the fstab file. Went back to TWRP, formatted data, did factory reset, copied new fstab file, rebooted. No SIM card detected, no IMEI. What is going on???

I am going to go back to the September release and try rooting again to double check if the SIM card works there.
[Nokia 3 Guides, News, & Discussion] bigrammy:
Edited my post above please re read that regarding the id.

Re-flash the recovery ROM to fix imei then root etc and capture the OTA when it arrives and see what device it's for in the /META-INF/com/android/metadata as above.

I think we need a oreo TWRP to work with unencrypting data seems like they built in a radio fuse which blows if unencrpted is detected :crying:
[Nokia 3 Guides, News, & Discussion] JonnyTech:
I think that it is even more basic than that:

- use SPFT to "firmware upgrade" September ROM >> reboot >> all ok

- use SPFT to "download only" patched boot and TWRP >> reboot >> no SIM

- use SPFT to "download only" stock boot and recovery >> reboot >> all ok

At no stage did I boot to recovery/TWRP or decrypt/format data

Retried above flashing just boot and leaving recovery at stock >> all OK

So any change to recovery triggers the SIM/IMEI block. I cannot remember, is there another way to boot TWRP without flashing it?

About the model mismatch, I am not too bothered - and have not investigated doing SPFT readback (never done it).
[Nokia 3 Guides, News, & Discussion] SkaboXD:
yes, with fastboot command "fastboot boot [recovery name].img" but it needs unlocked bootloader.
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Thanks [MENTION=8005568]SkaboXD[/MENTION] that is what I thought, but it does not work:

$ sudo fastboot boot my-twrp-v5.img
downloading 'boot.img'...
OKAY [ 0.368s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.370s

Ah, unlocked bootloader, of course. But last time I unlocked it, the "Orange State" message appears and does not boot...
[Nokia 3 Guides, News, & Discussion] bigrammy:
Well that's very interesting indeed so it's a deliberate crippling of the device rather than a simple replacement or refusal to boot. :crying:

Ooh well I guess it's back to the original Oreo as I cant live without TWRP

Well Done Nokia! aka (FIH) :laugh:

I told you they watch these forums. :eek:

I will have a pick through what I have and PM you if I find anything useful. :highfive:

EDIT: See post #180 below
[Nokia 3 Guides, News, & Discussion] JonnyTech:
Thanks [MENTION=3924647]bigrammy[/MENTION], do you think that it will boot it I unlock the bootloader?
[Nokia 3 Guides, News, & Discussion] bigrammy:
[MENTION=5588897]JonnyTech[/MENTION]

Well you can scrub all whats just been said :D

I just tested it on the October security patch ROM and I am now Fully rooted with TWRP installed and running un-encrypted with fully working SIM, WiFi etc etc. :victory:

Notice in the image below it say's "Encrypt Phone" :D

Think I know the problem so will PM you the details.

PS: No BL Unlocking so no Orange State.
[OnePlus 5T  Questions & Answers] nadiration:
Hello

I hate the white background in Google app is there a way to change the background to dark or just something other than white?