yashsingh1/xdaforums huggingface dataset:
[Nokia 2.2] TheBeast941:
Wait, you loaded the altunlock scatter file into sp flash tool right? If the scatter file hasn't been loaded into the program it wouldn't know what files should be in the readback. If you have forgotten, switch to the Download tab, load it into the "Scatter-loading file" field then switch back to the Readback tab and attempt to read back again.
[Nokia 2.2] BobStrop:
Yes, as shown at about 0:46 on the Youtube video in the first post.
[Nokia 2.2] BobStrop:
So I guess the frequency of response has decreased should I assume its too difficult? Im just curious though because I have followed all the steps properly (as far as i can see) and been pretty clear in my questions.Would really like to learn more.

All i really want through rooting is to be able to remove all the apps which take up 60% of my phones internal memory. Is there another way?
[Nokia 2.2] TheBeast941:
Search for the error that pops up on this website, it may be that the drivers you have downloaded and installed are out of date.

List of sp flash tool error codes, meanings & how to fix (solution)

Smart Phone Flash Tool also known as SP Flash Tool is a Desktop application used to flash firmware to Mediatek (MTK) Android devices. Its a pretty easy tool to use but you're bound to encounter one er

forum.hovatek.com

(you may have to sign up/log in to access links on that website)
[Nokia 2.2] BobStrop:
Much appreciated!
[Nokia 2.2] BobStrop:
Now to use this Wwr MTK tool i need the PGPT file? What is that? Ha, this is very complicated.
[Nokia 2.2] TheBeast941:
You only have to follow the link in the original post for performing the readback, we don't need to use that tool for what we're doing. Once readback is finished return back to and carry on with this guide.
[Nokia 2.2] BobStrop:
That is what i thought also but for some reason i can not get the readback to work.

I keep getting that same error...I believe the issue must be in the address lengths?

Are the lengths unique to each phone or just the model? I would imagine on the model and therefore there should be a standard value for all Nokia 2.2?

I will have another go tomorrow.

Thanks again everyone!
[Nokia 2.2] TheBeast941:
Don't remember if we talked about this before, but leave adequate space for where you want to store the readback, not enough space means the readback fails. I'd say leave at least 16 GB free to be on the safe side.

If that didn't fix the problem (or you already have enough space) It's possible your USB cable/port could be malfunctioning: try a different cable or use a different USB port. Also shorter USB cables are more recommended since the readback process requires fast read speeds and read speed deteriorates the longer the cable is.
[Nokia 2.2] SB3P:
For me Magisk (tested 23.0, 22.1 and 23001 Canary) doesn't seems to work on Android 11 (it does bootloop), either by using this ROM or patching my own Android 11 stock boot image (that boots fine when flashing boot partition with `fastboot`). Moreover, by comparing MD5 checksums in both patched files (yours vs mine), they seems to be identical files. What could cause that and do I need to tweak something else?

Also, when trying to patch Android 9 boot image with Magisk everything seems to work alright...
[Nokia 2.2] TheBeast941:
That's because the device only boots when files are patched on Android 9 (such as Magisk or any Android 9 GSI), if you attempt to patch your device with modified files on Android 10 or 11 it won't boot.

That's why the procedure in the guide downgrades your device to Android 9.
[Nokia 2.2] SB3P:
Thank you for your answer!​

As of steps done to unlock bootloader, I did them all on Android 9 and I did an upgrade to Android 11 only after I finished the whole procedure of unlocking the bootloader. However, I did patched boot image with Magisk on Android 11, as I believe boot images are different between Android 9 and 11. So, in conclusion, bootloader was patched on Android 9 and boot image was patched on Android 11 (where I took this boot image after doing a readback on Android 11 of the boot_b partition only as I discovered OTA updates always install themselves on the other than active slot).

So, according to your answer, how should I use the boot image sent by ? I'm sure can't flash it on Android 9 as it is intended for Android 11 and it would cause the bootloop as well on Android 9. What have I done wrong here? If I need to downgrade to Android 9 again, I know how to do that with SP Flash Tool, but right now IDK why I should do that if I want to use this Android 11 patched boot image.

Also, I previously tested LineageOS 16 Unofficial GSI image on Android 9 and it didn't work for me as well (with both flashed vbmeta and wiped user data with fastboot -w).
[Nokia 2.2] TheBeast941:
You would have to downgrade to Android 9 if you want to root your device, you can do that by following the guide again, and then extracting the boot.img file from the firmware file, patching it with the Magisk Manager app and loading the firmware file with the mt6761 scatter file but replacing the boot img with your Magisk image.

Again, you would have to downgrade to Android 9 to be able to successfully flash and boot into GSIs. Upgrading to Android 10 or 11 then flashing an Android 9 GSI would not work (and it is recommended to flash the GSI with an unmodified boot image for the first boot and then reflash your Magisk image after).
[Nokia 2.2] SB3P:
I know root + Android 9 works, but are there any chances to use that (Android 11) image? Has anyone tested it and confirmed, or

@areallydumbperson just sent it there untested and not working? As I pointed, I was able to reproduce this image with Magisk on Android 11 as well, but unfortunelly I was unable to flash it.

As I said earlier:

However, I don't remember if I flashed Magisk then, so I would need to test that again to prove you more details about what could gone wrong.
[Nokia 2.2] TheBeast941:
As a matter of fact I have tried to use Android 10 GSI and Magisk on Android 10 - neither worked so I just refollowed the guide with my IMEI files to downgrade back to Android 9

And yes, he did patch and upload an Android 11 image but he didn't test it to see if it worked (which it didn't). The most probable cause of the mods failing is because the Android 10 and 11 update could have used an entirely different format as opposed to the one from Android 9, and so the same scatter files won't work.
[Nokia 2.2] SB3P:
Too bad, I just had a little of hope I did something wrong on my side.

> The most probable cause of the mods failing is because the Android 10 and 11 update could have used an entirely different format as opposed to the one from Android 9, and so the same scatter files won't work.

Does fastboot have anything in common with scatter files and SP Flash Tool? I don't think so, but I may be wrong as its my first phone I did flashing / modding on. As stock boot flashes fine via fastboot, I would rather say either Magisk produces the incompatible format of the boot partition (I don't know how to properly unpack / mount boot partition and check the changes, so I have no way to debug it further), as the boot image I got when doing readback on Android 11 fine when flashed back with fastboot (and I'm pretty sure it wouldn't work). Anyway, I personally believe something's blocking us from booting from other partitions after Android 11 update, probably by checking its checksum – but I may be wrong there.

The other thing is that I can't boot back to Android 9 after an update when changing the active slot to A – where A partition scheme shouldn't be touched at all when updating to make it possible to recover when update failed to flash correctly (at least from my understanding of A/B partition scheme). This could be the same case as of custom ROMs, where something else needs to be tweaked so boot verification isn't checked. Anyway, that's my opinion and I might be wrong, I'm complete novice in flashing, yet I have a basic understanding how most common OSes works.

As of Android 11, there's a little hope about being able to boot into any GSI image via DSU Loader (it will work without the need of flashing anything and maybe without the need of having the bootloader unlocked) – I still haven't checked if it is possible. If you're curious about my progress, just call me back and I'll be glad to share with you if that works. I'll use the method described in Android Developer website:

Dynamic System Updates (DSU) | Platform | Android Developers

Dynamic System Updates (DSU) lets developers install a GSI side by side with the device's system image on a DSU-supported device that runs Android 10 or higher.

developer.android.com

Anyway, I really appreciate you answered me, I'm glad at some point I didn't messed up anything and that's the current limitation everyone needs to deal with.
[Nokia 2.2] SB3P:
Oh, DSU is killed at some point by the OS (or crashes, there's nothing that would indicate that by the default) – I guess it is broken, at least on my current OS version.
[Nokia 2.2] SB3P:
Actually, you were not right about that – flashing Magisk on Android 11 is in fact possible (and I managed to have it working!), but you need to disable vbmeta first (where Magisk worked fine on Android 9 without disabling vbmeta anyway). So I believe I was right – this wasn't due to incompatible scatter file, but because of boot verification failing on checksum check (or at least AFAIK that's how boot verification). I've also succeed getting the same stock boot image (and vbmeta image) by extracting images from OTA update – so the Android 9 scatter file works fine on Android 11.

So basically to get Magisk working on Nokia 2.2 after Android 11 update, you just need to flash a patched image and disable boot verification in vbmeta (I did that by passing both --disable-verification and --disable-verity flags while flashing Android 11 stock vbmeta).

Here I shared a screenshot as a proof it really can work (at least on Magisk 23.0).

EDIT: Some minior changes in the text sense, it didn't showed correctly what I was meant about when writing the post, which could lead to misinterpretation.
[Nokia 2.2] AAditya846:
Do I need a newer patched boot image for Android 11 or the old one from Android 9 will work fine? And, what about TWRP? I've had a working TWRP on android 9 (thanks to a guy from this thread). Does that work?
[Nokia 2.2] SB3P:
Android 11 update contains new boot image. Also just to note, most security updates will contain a patches to the kernel, so boot image may differ after doing an OTA update (I believe that's how I broke the updates on my currently installed image).
[Nokia 2.2] BobStrop:
Thanks.

I made some more space on my hard drive and attempted readback with several shorter cables but it is as though there is no connection on the shorter connection. Perhaps those particular cables have a diferent use?

Could somebody confirm the readback address length and value for the Nokia 2.2.?
[Nokia 2.2] TheBeast941:
Is there any specific way you managed to get it working? Let's assume that you've just finished following the original guide and are now on Android 9 with an unlocked bootloader. Did the bootloader stay unlocked while installing the Android 11 OTA? If not, how did you go about installing the Android 11 update while being able to flash vbmeta with --disable-verification and --disable-verity flags? Are you using the same lk and/or preloader on Android 9 for Android 11 (because I'm comparing the ones from Android 9 and Android 11 and they are different sizes)?

If possible, please create a simple guide for how you managed to get it to work so that I can try it on my device too.

UPDATE: Successfully managed to update to Android 11 with Magisk, ty for mentioning about the vbmeta image and its flags
[Nokia 2.2] AAditya846:
Teach me senpai

Edit: Is your device's bootloader still unlocked? And if it is, can you successfully boot any android 11 GSI into your device now? (Even Android 10 Lineage OS would be great. Anything greater than 9). I'm assuming now that we have the Android 10 or 11 vendor already installed newer GSIs must boot. Please let us noobs know how to do it?
[Nokia 2.2] TheBeast941:
I just reverted any modifications I did so it's basically like how the device should be after you complete the guide, and then let the device install the Android 11 OTA. Then I waited for the device to first boot, flashed the Android 11 boot image with Magisk and flashed that and vbmeta (with its flags) in fastboot (yes bootloader does in fact stay unlocked) and rebooted and voila.

Nokia 2.2 Android 11 ROM:

https://android.googleapis.com/packages/ota-api/package/9cc8a92b01615939195dae4794614cac4119d82d.zip

https://android.googleapis.com/packages/ota-api/package/b582d98a7aee43730a6106679872b86ea2b2649d.zip (00EEA Variant)

Check which version you need from the build number in settings, extract the payload.bin and use payload dumper to extract the ROM files out of that. You'll just need the boot and vbmeta images.

I haven't tried to flash any GSI at the moment but I might try in the future.
[Nokia 2.2] SB3P:
Yea, just make sure if you did any of the security updates to use readback instead of boot OTA images if you want to be able to do updates after doing a flash (yes, most security updates won't break Magisk patching, unless some important changes would be made to the boot image like the kernel update to the new major version or/and changes within the ramdisk format).

PS: This is how I believe I broke it for myself + I got issues with fastboot, althrough that may not be the cause of wrong boot image...
[Nokia 2.2] areallydumbperson:
I am so sorry I forgot to take the images down

edit: wow u have a tutorial on getting magisk working kudos to you :)
[Nokia 2.2] areallydumbperson:
I had taken down and reposted magisk images for android 11 because it didn’t work but 2nd time did so I posted it I forgot how many more stages there was to flash it rip
[Nokia 2.2] areallydumbperson:
unrelated to magisk or anything in this thread but I had seen some work on the Xperia l1 with a boot menu that has a recovery mode and a normal mode option which seems cool and the ported it from an Amazon fire kernel boot menu which is crazy I tried to atleast do it and failed miserably lol
[Nokia 2.2] TheBeast941:
ngl I wouldn't care too much about the security patches (unless there was an important one) because we were using security patches that were two years old before updating to Android 11, at least updating to Android 11 itself would make the device more secure than it would have been before
[Nokia 2.2] areallydumbperson:
About android 11 (goes for 10 too maybe) I wanted to try port twrp for fun (yes I know I have weird obsessions to try and port stuff onto this phone :p) and I go into sbin in the boot image and the recovery is just gone I really wonder what magic is Nokia doing or google
[Nokia 2.2] AAditya846:
That means no recovery on android 11? Damn it! 😑

I just tried a few android 11 GSI (2 AOSP and 1 Andy Yann's LineageOS build). None of them booted. Reinstalled stock system.img extracted from payload and glad that everything went back like a time machine. The fact that there is no specific recovery partition to this device reallly gives me headache. Have to be seriously prepared everytime I have to do something.
[Nokia 2.2] AAditya846:
ANDROID 12 GSI: SUCCESSFUL BOOT 😍

UPDATE: MY OVER EXCITED SELF COMPLETELY OVERLOOKED THAT IT WAS NOT MEANT TO BE A DAILY DRIVER. PASS THIS ONE, IT'S NOT WORTH IT 🥱

Guys I was able to boot into android 12 GSI (AOSP)!

I was on Android 11, trying every single GSI I could find. Accidentally downloaded the only android 12 GSI on github , flashed it, then realised I made a mistake, but tried to see what happens if I try to boot and it booted in like 30 seconds.

--what works--​

I've tested WiFi, calls, 3G (I don't have 4G SIM, never needed it), camera (video quality is trash as it is in every non-stock system), sound from speakers and earpiece, gps. I also saw option to take scrolling screenshot.

--what doesn't works--​

headphone jack :(

Also there is no browser but the default Webview tester.

View attachment 5386901View attachment 5386903View attachment 5386905View attachment 5386907View attachment 5386909View attachment 5386911View attachment 5386913View attachment 5386917View attachment 5386919View attachment 5386921

I don't think there's much to test in Nokia 2.2

It's funny how absolutely no daily driver OS I tried booted successfully. Only this was successful which had 0 expectations and mattered the least...

Thanks to everyone on this thread for ebery bit of help. I guess I'll be going back to stock for while.

One more thing - I didn't flashed vbmeta after I flashed system. After which I did fastboot erase userdata since fastboot -w did nothing.
[Nokia 2.2] TheBeast941:
I might try to take the old Android 9 ported TWRP and update it to use the Android 11 boot image soon, just need the time to be able to do so
[Nokia 2.2] TheBeast941:
Seems like that is just a test image that was meant to be run on emulators, better to stick to a full version of Android 11 than use an experimental version of Android 12
[Nokia 2.2] TheBeast941:
I tried porting my old TWRP image to the new Android 11 Magisk patched boot image, magisk works fine but as soon as you reboot into recovery you get stuck at the boot logo :(

I guess I'll just have to make one for Magisk and one for TWRP, like before.
[Nokia 2.2] AAditya846:
You've done so much for this crappy device. I'm just thankful for the working TWRP man. 🤲🏼

Also, can you tell me one thing: If i'm installing a GSI, which is rooted (like those with 'su' in the name), can they cause system to not boot? I'm new to these things.

Also, I tried Installing Android 11 GSIs available at ci.android.com but those also didn't go as planned.

I'm thinking about modifying the system.img kind of how flashable zip ROMs were being made 3-4 years back. What do you say?
[Nokia 2.2] areallydumbperson:
Weird thing the phone boots into android 11 specific recovery
[Nokia 2.2] areallydumbperson:
Also imo gsi could be possible on a 11 but we haven’t found the right images
[Nokia 2.2] TheBeast941:
that's because the boot.img contains the recovery on A/B devices
[About XDA developers] augy:
To the Mods,

I know I am just a junior member so please don't rip me a new one if you don't like my suggestion.

I'm wondering if you think it might be a good idea to creat a sub-forum inside Development and Hacking for all of the Skins and Customizations such as Mobile Shell skins and mods for s2u2.

I know that a sticky was started by TheChampJT for skins but in my opinion taking a step further and creating a sub-forum and moving the sticky into it would be even better.

I know it's odd coming from a member with such a low post count, in fact this is my way of trying to contribute since all of the tech. stuff is so far over my head.

Thanks
[About XDA developers] Zoltair Wright:
My post count is pretty low too... but I for one agree. It seems like the Development forum has gotten a little bogged down in themes and skins - which are really good, don't get me wrong! I just think it might help the skinners concentrate on skinning and developers concentrate on developing if the two forums were seperate.
[About XDA developers] DaveShaw:
This has been discussed a few times before now:

http://xdaforums.com/showthread.php?t=395209

http://xdaforums.com/showthread.php?t=400854

I'm sure there's a third thread I can't find as well :)

Thanks

Dave
[General Questions and Answers] namdrop22:
Ok. Last year someone was able to tunnel into my network at home. Alot of crazy s*** went down. Long story short, I think there's something fishy going on again.. let me explain.

Everytime I get a new phone, laptop, desktop, etc. I start finding a ridiculous amount of hidden files and folders. The PC side is no longer the issue, now its moved to Android, I think?..

The question I want to know, is how can I compare my what my phone should be installing after a factory reset, file wise? I've looked for a list online to compare with and no luck so far. I also found that there is a partition of the internal storage, completely hidden and inaccessible. Like.. I can't see anything. Add that with permissions being changed randomly so I'm not able to take full control over these pesky little buggers.

In short, I'm either wayyyy to high off that last dab, or my phone is being tampered with. What can I do? Here's what I'm working with.

Samsung A21 (SM-S215DL) using Straight Talk. Attached is a screenshot of the SW mumbo jumbo. I really hope someone can help. TIA!
[General Questions and Answers] Deleted member 1890170:
IMO nobody can tell you what apps to install after a Factory Reset: it's alone your decision what apps you want to run.
[General Questions and Answers] namdrop22:
No no. You're missing the question here.
[General Questions and Answers] Deleted member 1890170:
May be. :)

A Factory Reset doesn't install anything, it wipes all user apps and data. A Factory Reset never touches Android OS itself.
[General Questions and Answers] SKELEKINETIC:
Look at the running apps and services, anything utilizating root or kernel or system privileges will not be in that list unless it's using a app to bootstrap but if you have a weird duplicate system app or an app with a strange name could help you narrow it down. if you have usb debugging enabled you may be able to run a logcat as well to see what messages the system is generating.

Does samsung offer any tools to read the boot log? You might find something In that too. Lastly, well you should do this first, check if there are any exploits or vulnerabilities with your phones software and hardware. Google search " chipset-or-software-name-here + escalate vulnerable cve exploit "

Check past software versions too, you could get hit while the vuln is unknown or lesser known then it patches the manufacturers patches.

Can u elaborate on these file systems or folders you say you have that are invisible?
[General Questions and Answers] blackhawk:
Unless you loaded malware, a trojan etc on to the phone either in data from the PC, email download, an app you installed or a download from the internet.

Even so it would die with a factory reset... so do another factory reset so if you think so.

Then be careful what you allow into it.

Don't let anyone use your phone or access any of your devices ie flashcards, PC etc.
[General Questions and Answers] Deleted member 1890170:
Run

SafetyNet Test - Apps on Google Play

SafetyNet device compatibility test

play.google.com

to check whether phone's Android got tampered or not
[Samsung Galaxy A7 (2018) Questions & Answers] eldon301:
Anyone knows the correct offset as

0x3000 is BL1 name> bl1

0x3000 ... 0x17000 is epbl

0x17000 ... 0x68000 is BL2

0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot

Dram_training do not need to be cut, it is not used in flashing

0x244000 ... 0x1BD000 is el3mon dram

can anybody please explain these files I have my Sboot.bin which was in the phone, I don't understand how to find correct offset/size. can some plz assist me, working on a750g. broke bootloader software version U1ARL3 for sboot

here is my sboot, can someone please create or show me how to. https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=drivesdk

I think I found bl1 bl2. So far multidownloader says transfer done bin 1 and bl2