Develop Bugs

unbrick Nokia 3.2

Hello together,
after many tries to get my nokia 3.2 rooted, i end up now with a black screen.
Only the Qulacomm mode is working.
Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread?
I always end up with "sahara fails".
Every help is welcome!
Thanks!!!!

After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!

page1875 said:
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
Click to expand...
Click to collapse
please do, i encountered a similar problem.

HowTo Flash STOCK 00WW
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!

page1875 said:
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
Click to expand...
Click to collapse
Thank you for your reply, it seems that your problem is more complicated than mine.
I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that.
Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem.
I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.

Normally you can use the EDL Mode every time.
My phone only showed black screen and it was always possible to connect in EDL Mode and flash again.
Did you try to flash again? What happens then?

Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
Click to expand...
Click to collapse
What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ?
My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.

Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.

page1875 said:
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
Click to expand...
Click to collapse
@update:
Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing.
Remove them from the XML file and try again!

@update
Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now

Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader

I also had this problems for many many times and don't know what went wrong when this happens.
The only thing that helped was flashing the complete firmware again in EDL-mode.
You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread.
I uploaded this files for you, because you don't will find the europe files in internet yet.
Here is the link:
https://transfernow.net/81iti7q21s0s
Good luck!

Hi,
Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?

Yes, that also happens sometimes with my phone.
No, that are not all firmware files, which you need to do a full EDL-Flash.
But with this files you can first try a fastboot flash!
If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206.
Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.

Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them

hello
i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me.
thank you very much

thanks so much i was able to put my phone back to life. i had almost given up.

smure said:
thanks so much i was able to put my phone back to life. i had almost given up.
Click to expand...
Click to collapse
Hello to ervery one
how you flashed your phone. can you please guide?
i am also stucked in fastboot mode after rooting.

damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.

RN8P unknown baseband version

Love (how the hell can you love a machine??? - sorry, I guess I have NO imagination, maybe you can ...) this phone. BUT!! After backing up and restoring using LR TWRP a number of times, then using fastboot to flash_all the original ROM a number of times when I got into flashing problems, my cavalier approach backfired in one of these repetitive actions. Surprisingly, at least to me, I have both IMEI's listed on the status page, but a constant "unknown baseband" version. SIM setting is grayed-out, and I am only on WiFi. Flashing the original ROM (V 10.4.2.0) fixed nothing. Tried V 10.4.1.0, but I can't downgrade: luckily the phone wasn't bricked. Flashed Havoc V 2.9, hoping all partitions would be overwritten, then flashed MIUI V 10.4.2.0, but no change.
Have found no solution from Hovatek (stated flashing original ROM usually repairs the unknown baseband issue), or other sites searched from Google. Any procedure to solve this MTK issue on this phone would be most appreciated.

fastboot flash_all IS already deleting & overwriting all partitions, but I found sth interesting going on both my RN8P:
1. Sometimes both of the bluetooth MAC is gone on normal reboot, replaced by generic one 00:00:46:00:00:01 (yes, both got identical MAC).
2. One of the phone can't recognize SIM card after reboot, need another reboot to fix it.
Turned out that somewhere in upgrading to MIUI 11 Android 10 ver, it's corrupting some partitions: nvcfg, ncdata, nvram, vendor, persist, misc, cust.
Here's my fix:
1. Boot to TWRP
2. Mount those partitions then go to Advanced > Terminal, issue: mount to list the ID of the partitions
3. Unmount all partitions
4. Back to terminal, issue: e2fsck -fy /dev/block/sdcX where X is the parition ID corresponding to the list of mount above
5. It'll show that some partition is getting fixed, if done, just issue: sync
6. Reboot to MIUI, let it sit for 5 minutes, then reboot to TWRP again, redo all steps & you'll see it's still getting some errors, it's normal. Redo for 2 more times, it'll get fixed for good.
Something in the systems doesn't right, it kinda needs to readjust all the fixed partitions but in the process it also corrupting it again, therefore needing 2 - 3 more e2fsck as I said above.
Oh, if you're rooted & using AdGuard, NEVER USE Move Certificate module in the Magisk, it's the one contributing to those corruption.

Wow!! Thank you so much! I will follow each step and report what I've found.
So impressed with the detail you have given; thanks to have experts such as you willing to share.
Later ....

Crescendo Xenomorph said:
fastboot flash_all IS already deleting & overwriting all partitions, but I found sth interesting going on both my RN8P:
1. Sometimes both of the bluetooth MAC is gone on normal reboot, replaced by generic one 00:00:46:00:00:01 (yes, both got identical MAC).
2. One of the phone can't recognize SIM card after reboot, need another reboot to fix it.
Turned out that somewhere in upgrading to MIUI 11 Android 10 ver, it's corrupting some partitions: nvcfg, ncdata, nvram, vendor, persist, misc, cust.
Here's my fix:
1. Boot to TWRP
2. Mount those partitions then go to Advanced > Terminal, issue: mount to list the ID of the partitions
3. Unmount all partitions
4. Back to terminal, issue: e2fsck -fy /dev/block/sdcX where X is the parition ID corresponding to the list of mount above
5. It'll show that some partition is getting fixed, if done, just issue: sync
6. Reboot to MIUI, let it sit for 5 minutes, then reboot to TWRP again, redo all steps & you'll see it's still getting some errors, it's normal. Redo for 2 more times, it'll get fixed for good.
Something in the systems doesn't right, it kinda needs to readjust all the fixed partitions but in the process it also corrupting it again, therefore needing 2 - 3 more e2fsck as I said above.
Oh, if you're rooted & using AdGuard, NEVER USE Move Certificate module in the Magisk, it's the one contributing to those corruption.
Click to expand...
Click to collapse
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.

ppthom said:
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
Click to expand...
Click to collapse
it is indeed not possible to mount an NVRAM partition, maybe the one referred to is the Mount System, you must first check the mount system to restore or backup.
for TWRP files you can adjust to your current Android Version, please check the following post.
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695

Coffeemi said:
it is indeed not possible to mount an NVRAM partition, maybe the one referred to is the Mount System, you must first check the mount system to restore or backup.
for TWRP files you can adjust to your current Android Version, please check the following post.
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
Click to expand...
Click to collapse
I always find out something new. Thank you. No mount NVRAM partition. As far as mount, I thought that SYSTEM partition was always auto-mounted. Not so, it is DATA and CACHE. I have backed-up and restored with this understanding. My bad, again.
Also LR. TWRP is the 1104 version, my goto recovery, as I am always able to get out of trouble using it, except now with no baseband version. However, after using Flash_all, I have to boot into the basic system to make changes before I can restore one of my backups. In this default setup, the status lists no baseband and no IMEI. It is only on restore to my latest backup that both IMEI's are also restored, but not the baseband.

ppthom said:
I always find out something new. Thank you. No mount NVRAM partition. As far as mount, I thought that SYSTEM partition was always auto-mounted. Not so, it is DATA and CACHE. I have backed-up and restored with this understanding. My bad, again.
Also LR. TWRP is the 1104 version, my goto recovery, as I am always able to get out of trouble using it, except now with no baseband version. However, after using Flash_all, I have to boot into the basic system to make changes before I can restore one of my backups. In this default setup, the status lists no baseband and no IMEI. It is only on restore to my latest backup that both IMEI's are also restored, but not the baseband.
Click to expand...
Click to collapse
if you have properly saved a backup file of all modem and IMEI partitions, all modem data will definitely be restored, I'm sure not all of the modem partitions have been successfully backed up.
for the modem partition, sensor and IMEI, here are the names of the partitions.
- nvcfg
- nvdata
- nvram
- persist
- protect_f
- protect_s
make sure all the partition names are in your TWRP backup file.
Sent from my Redmi Note 8 Pro using XDA-Developers Legacy app

You should be able to do a DD if=/image.bin of=/dev/block/sdcX to fix if you don't have a TWRP backup
- nvcfg is sdc7
- nvdata is sdc8
- nvram is sdc18
- persist is sdc10
- protect_f is sdc11 labelled protect1
- protect_s is sdc12 labelled protect2
I assume protect_f and protect_s is protect1 and 2 but hopefully someone can confirm.

Coffeemi said:
if you have properly saved a backup file of all modem and IMEI partitions, all modem data will definitely be restored, I'm sure not all of the modem partitions have been successfully backed up.
for the modem partition, sensor and IMEI, here are the names of the partitions.
- nvcfg
- nvdata
- nvram
- persist
- protect_f
- protect_s
make sure all the partition names are in your TWRP backup file.
Sent from my Redmi Note 8 Pro using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have NOT "properly saved a backup file" with the modem partitions, and that is where my trouble lies. I am also not being reminded to set the SIM card info when booting up after flashing the stock 10.4.2.0 ROM, which is strange, because a week ago I was able to go back-and-forth between my restored backed-up files and the stock ROM. On first booting the stock ROM, I was reminded every 10 seconds that my SIM card was not correct (my card is only 3G and the default SIM setup was for LTE), interferring with setting up my WiFi for authenticating my Xiaomi account. Now, with an unknown baseband, the SIM is not recognised by the stock ROM, I can enter my WiFi account without interference; and there no entry for the baseband and nothing for the IMEI numbers.
As soon as my "not proper backup" is restored, the IMEI numbers are set correctly, but no baseband.
My goodness, I will see if anyone online can flash the stock zip file remotely and see if that corrects the problem.
Hey, thank you for paying attention to my problem, and I very much appreciate your time on this.

wang1chung said:
You should be able to do a DD if=/image.bin of=/dev/block/sdcX to fix if you don't have a TWRP backup
- nvcfg is sdc7
- nvdata is sdc8
- nvram is sdc18
- persist is sdc10
- protect_f is sdc11 labelled protect1
- protect_s is sdc12 labelled protect2
I assume protect_f and protect_s is protect1 and 2 but hopefully someone can confirm.
Click to expand...
Click to collapse
Thank you fellow Canadian :good:; I will try this as well. So great to have all these suggestions from people who know a hell of a lot more than I do. Thank you both Coffeemi and wang1chung.

ppthom said:
Okay,
No luck here:
I have not upgraded to MIUI 11 Android 10. Still on MIUI 10 Android 9.
LR. TWRP has no mount for NVRAM or for MISC. What version of TWRP do you have?
No error messages for the other remaining sdc's - sync after each e2fsck commands. Reboot to system and still unknown baseband - repeated procedure twice, after waiting 5 and 7 minutes.
Thanks for the heads-up on the Move Certificate module and AdGuard - never installed it as it seemed to be not for Xiaomi.
Click to expand...
Click to collapse
Better to use LR TWRP, it's the best for Xiaomi phone.
Sadly it's only available for Android 10 version. Better upgrade as Android 10 still way better than their 9 (too much bug).
Link to A10 LR-TWRP: https://mega.nz/file/Ad4TUTTA#_xT16vOzYK-O8qaWEHPYxfdi4wNpK5Ang9maN5iO_-U
If no error being corrected then sadly I dunno more except for hardware issue (baseband chip is broken, I saw one case in Mi Community forum). Hope not this case. :crying:
You're welcome friend. The Move Certificate module is for AdGuard actually, its to clear those network being monitored notification when you use AdGuard's HTTPS filtering.

Thank you Coffeemi, wang1chung and of course Crescendo Xenomorph. You've all paid attention to this problem, and it is very much appreciated.

Ok, ok. Not sure how I did not stumble accross this before, or, more likely, not paid attention to this procedure .
I choose to use RN8P with Miui V10.4.2.0 ROM. Gives me the most flexibility. Later Android versions restrict my wants, including using TWRP - just a personal opinion; yours may vary ...
Erased NVRAM and nvdata in this ROM, after having flashed it and rooted it, then installing X-plore File Manager apk (most other rooted file managers would work as well, if not better).
Rebooted, and the unknown baseband problem was solved, at least for me.
Then restored my latest TWRP backup of Data, Boot, System image, Vendor image and Cust image.
All seems well. No more unknown baseband, IMEI's listed as well as Bluetooth. Whew. So many good people out "there", and so many experts to thank. Thank you:good:.

ppthom said:
Ok, ok. Not sure how I did not stumble accross this before, or, more likely, not paid attention to this procedure .
I choose to use RN8P with Miui V10.4.2.0 ROM. Gives me the most flexibility. Later Android versions restrict my wants, including using TWRP - just a personal opinion; yours may vary ...
Erased NVRAM and nvdata in this ROM, after having flashed it and rooted it, then installing X-plore File Manager apk (most other rooted file managers would work as well, if not better).
Rebooted, and the unknown baseband problem was solved, at least for me.
Then restored my latest TWRP backup of Data, Boot, System image, Vendor image and Cust image.
All seems well. No more unknown baseband, IMEI's listed as well as Bluetooth. Whew. So many good people out "there", and so many experts to thank. Thank you:good:.
Click to expand...
Click to collapse
Can you provide me the steps. Because I'm having the same vesion but with IMEI Invalid. My phone accidently got update to MIUI 11 and the Baseband got ruined.!!!

Somehow Android 10 in this phone will corrupt something in nvdata if you do modification on the fly (somehow like they unable to load it properly, thus no baseband with corrupted BT MAC).
How to know if your BT MAC is corrupted? It'll default to 00:00:46:00:00:01.
BT MAC should be one step above WIFI MAC (if your WIFI MAC is AC:1C:05:AC:43:01, your BT should be AC:1C:05:AC:43:02).

Found the culprit: any Magisk version greater than 20.3 will cause this error on MTK devices.
Solution: use Magisk 20.3 stable, it's the only fix till the devs come up with the fix.

Urgent help for my A5 2017 (A520W model)

I tried using the XDA Discord server to get a quick response, but apparently, some people just ignore me or don't even know how to help me. So I will try here...
I was following that tutorial so that I can use Joycon Droid on my phone. I installed TWRP Recovery and gone in his recovery mode. I wiped what the tutorial asked to wipe and began the flash process. Unfortunately, I mistakenly downloaded the flash files on the computer. I tried removing my SD Card and putting inside it the files I need, but TWRP was not able to read any data for the SD Card. So I tried to find a way to cancel the recovery menu, and I did by clicking Reboot System. Since then, my phone was locked in the logo screen. After many attempts, I've gone from the charging screen and finished by the "An error occurred while updating the device software.". I can enter the download mode, but nothing else. My phone is an A520W and I think the root was not properly installed. I researched everywhere without any solution, so I came to this discord server, hoping someone would save my phone. I tried flashing the official A520W OS, but Odin always does a FAIL message or freezes. I later tried to use another firmware file, reinstalled the Samsung USB driver and Odin, and know it says on the Download Mode screen:
SV REV. CHECK FAIL(BOOTLOADER) DEVICE: 9, BINARY 7. (it failed)
Can someone help me? I really need help!

Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)

matkali said:
Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)
Click to expand...
Click to collapse
Kay I'll try the easy-jtag, but if it doesn't work, who is an expert at emmc programming stuff?

Is there a way to fix the crushed partition table without buying stuff?

Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop

Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
better than the error screen right? the program name is fonepaw

Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
It is dangerous for your phone, because every phone have different partition table and different architecture!
Pit file in a520w stock firmware have partition table structures information. (use PIT_Magic.exe to see)
In old architecture of Samsung(e.g. s3) when partition table cleaned from emmc (phone internal storage), they use micro sdcard to boot from it! (to identity correct info for Odin) (same boot from USB when you are installing windows.) then by going to download mode they flash stock Rom!
But I suggest to you find one knows enough information and requirements stuffs.

Question Gapps error 70, resize System Partition.

Hello.
After I received my new Poco f3, the first I've done was unlocking the bootloader. 7 days later, everything was done and I flashed lineageos.
>Fastboot boot twrp.img>advanced>flash current twrp.
After that I've wiped and format data. Then I flashed lineageos. After that I've tried to flash gapps, but that results in "error 70 Not enough space. I've tried pico and nano package. The question is now, how am I able resize the system partition ? I googled to find solutions but what I've found, just scared the sh*it out of me. Some people experimented with gparted and hardbricked their device, because they destroyed their bootloader.
In twrp>wipe>advanced wipe there is no system partition shown. Dunno why.
I didn't dare to >Fastboot erase system (Or Fastboot format system) before I flash los. Is this safe and could be a possible solution? I also don't understand how this "a/b" partitions Work. My old Poco f1 didn't had those.
would be really grateful for help.

Yeah this phone is really tricky to mod. I rooted mine and for some reason still didn't have write permissions on root folders.
Tried to delete lockscreen keys just for testing purposes and it messed up the phone. After that even twrp restore couldn't fix it. So I flashed the stock firmware via mi flash tool and locked the bootloader for good.
I find that what you get from rooting this phone is just not worth the risk with its tendency to mess things up really bad at the slightest mistakes, especially because the EDL is locked.
It used to be so simple with older phones. But unfortunately google is trying their best to make phones impossible to modify. And they're getting pretty close now.

user0u said:
I rooted mine and for some reason still didn't have write permissions on root folders.
Click to expand...
Click to collapse
I had the same problem. I've read that just flashing magisk.apk in twrp isn't supported well anymore. You have to modify boot.img in magisk app, and then flash the modified boot.img with Fastboot. For me, that solves the problem (see Instructions. To extract the boot.img from rom.zip I used Payload dumper ).
Long story short, I still didn't managed to resize the system partition

I got an other idea! Is it possible to "inject" gapps into the system.img before I flash it ?!

Did you ever figure it out?

According to installation guide by lineageOS, MindTheGapps is the recommended Gapps for android 11
Google apps | LineageOS Wiki
wiki.lineageos.org
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
if you are gonna download MindTheGapps, then use the arm64 version

Fandroid Tech said:
Did you ever figure it out?
Click to expand...
Click to collapse
No, I just jused arrowos with the integrated gapps package. Maybe I will try the "mindthegapps" version in the next weeks and give feedback

I'm using orange fox recovery, bugged by this error when I flash opengapps after flashing lineage0s 18.1.
Following is what fixed the issue for me.
1. download latest firmware for the device
2. update zip from ofox recovery- with vendor partition mounted.
3. reboot to recovery and then flashed opengapps nano (this time check the flag for unmount vendor)

Question Rooting with Magisk failed (FAILED (status read failed (Too many links)))

Hello everyone,
I have a new Xiaomi 11T EEA device, tried rooting it with the following steps, but failed:
- Updated to the latest official MIUI version (13.0.9.0)
- Unlocked bootloader with MiUnlock (shows the unlocked padlock at boot, and also in developer options)
- Downloaded the latest ROM with the updater app in phone (also tried from c.mi.com, same files, checked checksums)
- Used payload dumper at PC to extract the boot.img from the ROM
- Installed latest Magisk Manager (25.2) to the phone
- Pached the boot.img with Magisk
- Installed latest adb and drivers to my PC (restarted it after the install)
And then I tried booting the phone to the patched boot.img (fastboot boot patched_boot.img), but failed (even tried with the stock boot.img, same result):
downloading 'boot.img'...
OKAY [ 3.188s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 11.135s
I tried with my PC, with another notebook, 3 different USB A to C cable, 2 different USB C to C cable (different orientations too), all of the USB ports on the devices, but I got the exact same result.
So far I succeeded with these steps with 3 other Xiaomi phones (Redmi Note7, Mi 9T, Poco F3), but not with this one, and I have no idea what else I can do.
I suspected it has something to do with MediaTek SOC, that's the only meaningful difference I can think of.
Does anyone have any idea what else I can try, or maybe have a working patched boot.img?
Thanks for reading it, have a nice day!

Once the boot modify install with Fastboot, use fastboot reboot.

NOSS8 said:
Once the boot modify install with Fastboot, use fastboot reboot.
Click to expand...
Click to collapse
Maybe I understand it wrong, but I didn't install the boot.img, and don't really want to install it until I am sure I don't soft brink the phone.

s-zoli said:
Maybe I understand it wrong, but I didn't install the boot.img, and don't really want to install it until I am sure I don't soft brink the phone.
Click to expand...
Click to collapse
Obviously if you don't flash the modified boot.img, the phone won't be rooted.
See here (different device but same method).
https://forum.xda-developers.com/t/root-xiaomi-11t-pro-on-latest-miui-13-working.4450535/

NOSS8 said:
Obviously if you don't flash the modified boot.img, the phone won't be rooted.
See here (different device but same method).
https://forum.xda-developers.com/t/root-xiaomi-11t-pro-on-latest-miui-13-working.4450535/
Click to expand...
Click to collapse
It will be rooted until reboot, which is fine for a temporary root and testing things before making it permanent.
From my understanding it should be working either way, booting to it, or flashing right away. Previously I tested the patched boot.img just by booting into it, and worked every time. At the Redmi phone when I tried to flash the boot.img (that was used to boot into and worked), it didn't boot and got stuck to fastboot, and had to flash back the original boot.img.
I read the mentioned thread, it's the same steps I did, except the last booting vs flashing with fastboot.
Am I missing some key information how the booting mechanism works?

s-zoli said:
It will be rooted until reboot, which is fine for a temporary root and testing things before making it permanent.
From my understanding it should be working either way, booting to it, or flashing right away. Previously I tested the patched boot.img just by booting into it, and worked every time. At the Redmi phone when I tried to flash the boot.img (that was used to boot into and worked), it didn't boot and got stuck to fastboot, and had to flash back the original boot.img.
I read the mentioned thread, it's the same steps I did, except the last booting vs flashing with fastboot.
Am I missing some key information how the booting mechanism works?
Click to expand...
Click to collapse
Newer devices have A/B partitions unlike old ones.

NOSS8 said:
Newer devices have A/B partitions unlike old ones.
Click to expand...
Click to collapse
So you are saying that flashing the boot.img replaces both A and B partition and will most probably work, even if booting into it doesn't?

s-zoli said:
So you are saying that flashing the boot.img replaces both A and B partition and will most probably work, even if booting into it doesn't?
Click to expand...
Click to collapse
The .img boot never replaces the partitions, I was answering that you had already rooted other but old devices, that is to say without A/B partitions.
And why do you want to root this model with soc MTK(No or few development for Xiaomi with Mediatek processors)?

NOSS8 said:
The .img boot never replaces the partitions, I was answering that you had already rooted other but old devices, that is to say without A/B partitions.
And why do you want to root this model with soc MTK(No or few development for Xiaomi with Mediatek processors)?
Click to expand...
Click to collapse
The Poco F3 is a newer phone, and I just checked with Treble Check app, that it has seamless system update, therefore A/B system partitions (and so does the 11T).
The reason is the same as for every other phone... customization, automations, battery management... etc.
The things that should be available for power users, not just in fancy gaming phones.
It just happens to have MTK instead of QC (like the 11T Pro).
Do you have any information if this SOC difference can affect the booting and therefore rooting it?

s-zoli said:
The Poco F3 is a newer phone, and I just checked with Treble Check app, that it has seamless system update, therefore A/B system partitions (and so does the 11T).
The reason is the same as for every other phone... customization, automations, battery management... etc.
The things that should be available for power users, not just in fancy gaming phones.
It just happens to have MTK instead of QC (like the 11T Pro).
Do you have any information if this SOC difference can affect the booting and therefore rooting it?
Click to expand...
Click to collapse
MTK=MediaTek
QC=Qualcomm
Change nothing at the root level.
Everything you want to optimize is possible without rooting, moreover you will have to install modules which themselves consume battery.
Except for personalization.

NOSS8 said:
MTK=MediaTek
QC=Qualcomm
Change nothing at the root level.
Everything you want to optimize is possible without rooting, moreover you will have to install modules which themselves consume battery.
Except for personalization.
Click to expand...
Click to collapse
Sure, you're right, but I already started the rooting process, the bootloader is unlocked, so I already lost a few things (Google Pay, Netflix... etc).
The only way out is re-lock the bootloader or find a way to install Magisk and modules for it.
We deviated a bit from the original question...
I haven't found any source of information what does "Too many links" error means?
Also I didn't find any information if I can easily get back to original state if flashing the supposedly good pached boot.img doesn't work. (bootloop, stuck at fastboot... etc)
My way of being somewhat sure it works was first booting to it, but that doeasn't work now, and it's suspicious for me that the flashing won't work either.

To have the play store certified, use Magisk + zygisk.
https://topjohnwu.github.io/Magisk/
https://www.droidwin.com/fix-status-read-failed-too-many-links/
Once the boot modify install with Fastboot, use fastboot reboot.

Long story short... I just went for it and flashed the patched boot.img, and it's working just fine.
I don't know why it didn't want to boot, but flashing worked and now I have root access.

NOSS8 said:
Obviously if you don't flash the modified boot.img, the phone won't be rooted.
See here (different device but same method).
https://forum.xda-developers.com/t/root-xiaomi-11t-pro-on-latest-miui-13-working.4450535/
Click to expand...
Click to collapse
thats snapdragon, and this is mediatek
will this work with mediatek? without specifying a/b partitions?
Code:
fastboot flash boot patched_boot.img

bluviper said:
thats snapdragon, and this is mediatek
will this work with mediatek? without specifying a/b partitions?
Code:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
Check:
https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/
getprop ro.build.ab_update
Then you will know which command to choose.

NOSS8 said:
Check:
https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/
getprop ro.build.ab_update
Then you will know which command to choose.
Click to expand...
Click to collapse
i have the a/b partition

bluviper said:
i have the a/b partition
Click to expand...
Click to collapse
So,use
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
or
fastboot flash boot_ab patched_boot.img
fastboot reboot

I just flashed without _a _b or _ab and it flashed still to both slots