Database Develop

Nokia 4.2 Bricked, but can still enter FastBoot

Hello everyone :laugh:!
Tried rooting the Nokia 4.2, did not know which img to use exactly so I tried one from some other shady site and messed up. Luckily, the recovery partition was still working. After trying to boot lots of images, I got tired and accidentally even flashed a Nokia 6.2 TWRP image to my recovery partition. Then I completely messed up. The phone only gets into fastboot now. May I please ask some help of you? I've been trying for days to fix things. I just wanted to root the original firmware. Now when I try to flash TWRP, it even says that the 'recovery' partition has no partition table! I can still write to boot_a and boot_b though. The phone originally had the October patch level, but before bricking it I upgraded it to the December level.
Kind regards,
Alexander47u

Search on google and try do download and flash the stock firmware (unrooted)

Phone does not get detected by QFIL
thegamingcat13 said:
Search on google and try do download and flash the stock firmware (unrooted)
Click to expand...
Click to collapse
I have tried this using QFIL, however the phone is not detected. The phone also goes into fastboot as soon as the cable is plugged in, even when the phone is off.
Have also installed appropiate drivers for QFIL, but no luck.

Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot

Works, Thank you!
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Thank you! This worked flawlessly.

#metoo
Haha, I have done the EXACT same thing as you. Now I can only enter fastboot mode and when I try to flash anything I have downloaded I get an error about missing partitions. I have looked everywhere for details on the partition sizes, mount points and so on but nobody has uploaded the information. In the end I went and purchased a second device in order to dump the entire stock ROM in order to fix the first phone. I've got the second phone running in ADB-mode but I can only backup to an .ab file so now I am back at square one. All of the guides I can find on how to dump the ROM involves flashing TWRP recovery but THERE IS NONE FOR THE 4.2 :crying: And after researching Android forensics I have found a guide to dumping the ROM but it needs root access in the phone shell. All I wanted was root (and LineageOS). Does anyone feel like patching the stock ROM and making a zip-file containing the img-files from all of the partitions?

Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.

alexander47u said:
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
Click to expand...
Click to collapse
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!

You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.

alexander47u said:
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
Click to expand...
Click to collapse
I was able to succesfully patch boot.img with magisk, then I copied the patched boot image to my computer with linux. Fastboot flash boot boot.img worked but upon reboot I got an error message saying "corrupt data" and offered to do a factory reset. Any chance you can upload your patched boot image so I can use yours?

Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129

Posted

alexander47u said:
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Click to expand...
Click to collapse
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?

Oslokalle said:
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Click to expand...
Click to collapse
Up to March. I used the stock rom that is floating around on the internet. Not sure if I am allowed to post stock roms.
I was able to update to April using Magisk but not any further than that.

thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Tried this using a user_update.zip file from www[.]getdroidtips[.]com/stock-rom-nokia-4-2-firmware/. My phone boots again, but Wi-Fi doesn't work. My model # is TA-1133. What should I do?
Edit: tried to install the latest security OTA from t[.]me/nokiarepoen/379, V2.29C, but I get
Code:
E:Package is for source build 00WW_2_29B but expected 00WW_1_17I
. Is there a base user_update for build 00WW_2_29B floating around?

Oslokalle said:
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
Click to expand...
Click to collapse
Kindly provide me that zip too.

OOS stable boot image and patched magisk boot image both for 11.1.1.1.

Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.

I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.​

235anders15 said:
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
Click to expand...
Click to collapse
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D

sam_htc_touch said:
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
Click to expand...
Click to collapse
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot

235anders15 said:
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
Click to expand...
Click to collapse
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well

sam_htc_touch said:
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
Click to expand...
Click to collapse
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process

sam_htc_touch said:
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
Click to expand...
Click to collapse
Just for the benefit of all (if it matters), noticed that Magisk wasn't passing the Safety Net check and was showing failed for all 3. Used this fix and all is well now (Used the Sept 13 update on the page)

previously patching with stable 11.1.1.1 and broke some major functionality (eg: wifi crash, mess up video player and codec), now try to patch with magisk version, will update later

abhi0039 said:
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.​
Click to expand...
Click to collapse
stable.img from there (and the other ones) dont fastboot boot on my OSS 1.1.1.1 fastboot mode.

I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!

F5:ed said:
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
Click to expand...
Click to collapse
Press and hold vol up, down , power at the same time for a while it will boot to fastboot.

I got boot loop after updating to 11.1.2.2
Any new boot img?

izik.avi said:
I got boot loop after updating to 11.1.2.2
Any new boot img?
Click to expand...
Click to collapse
Haven't tested yet but here you go

rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
This one works great. Thank you.

The attached file in #13 above worked, thank you!
In case someone would like to now "How to do it" until next time this is how I did it:
How to install OOS update and root via created patch.img file in the Magisk app
1. Download the full version eg the OOS 11.x.x.x.zip file on the computer, and copy the file to the phone's internal memory as well.
2. Run the payload_dump program (https://androidfilehost.com/?fid=1899786940962605222) to extract a boot.img from the computer. You have to extract the payload.bin file from the OOS 11.x.x.x.zip file and place it in the Input folder, then run the exe-file and wait for payload to complete, then copy over the boot.img file found in the Output folder to the phone.
3. Go to Magisk app on the phone, click on the top install "Magisk", click "Select and patch a file", search for the boot.img file you created.
4. Now, Magisk will create a patched magic.img file from the boot.img file (can be called eg magic_patched-23000_xt8QR.img)
5. Copy the magisk_patched-xxxxxxx.img to your computer's "Root folder" where you have stored ADB files, etc
6. Now install the OOS 11.x.x.x zip file (should be in the mobile's Internal memory) via Settings> System> System updates and the "gear"> Local upgrade
7. When done, DO NOT reboot but go directly to Fastboot mode + connect cable to the computer
8. On the computer, type from your "Root folder":
fastboot flash boot magisk_patched-xxxxxxx.img
9. Reboot the phone - you are rooted!

rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?

raymund08 said:
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
Click to expand...
Click to collapse
Yes

rippledrums said:
Yes
Click to expand...
Click to collapse
Thank you

Can confirm OP fastboot commands and patched boot img are working for 11.1.1.1.​​I uninstalled magisk by mistake and could regain root, quick and painless​

Can anyone help me? flashed patched boot to A and B Slot. But Magisk is N/A. Any idea?

Samsung A30 Stuck in Donwloading... (Download Mode)

Tried to download TWRP onto my unrooted device (Galaxy A30 exynos) with Odin and now my phone is stuck on "downloading" screen. When I try to cancel (restart phone) it goes to the startup/booting screen for less than a second and then jumps back to "downloading". It says this at the top left corner of the screen:
recovery: Error validating footer (6) CUSTOM RECOVERY VBMETA A305F D0S60UD3. 38308538R
The bootloader is unlocked.
Using Odin 3.14
and downloaded twrp from the official website.
SO what can I do now to fix it like either go back to how it was or successfully flash twrp. I have tried flashing stock firmware doesn't work I get error on ODIN. I tried to flash only the vbmeta.tar from an earlier twrp.img I found on XDA that didnt work as well. How can I fix this? Or maybe go back to how it was. Thanks in advance.

Looks like vbmeta is preventing you to boot your device. It's responsible for checking the integrity of your phone and it's detecting that you have flashed an unofficial recovery.img
I'm surprised that no guides mention about disabling vbmeta. I don't know if flashing a blank vbmeta and flashing a disabled vbmeta are the same thing though. I usually patch my AP_ file with the Magisk app and inside there's always a patched vbmeta to prevent this type of situation.
Maybe someone with the actual device can share an actual disabled vbmeta.img
OR, you can just install your stock recovery and flash TWRP later

Hi,
Just ran into this one...
Thnx @ShaDisNX255
Here's a packed tarball of official TWRP 3.6.1_9-0 (latest at time of writing) with patched vbmeta.img
original vbmeta.img from stock A305FDDU6CVG2 Android 11 (latest at time of writing)
Patched with magisk 23
Just boot into recovery and flash magiskv23.zip as usual to get root

ShaDisNX255 said:
Looks like vbmeta is preventing you to boot your device. It's responsible for checking the integrity of your phone and it's detecting that you have flashed an unofficial recovery.img
I'm surprised that no guides mention about disabling vbmeta. I don't know if flashing a blank vbmeta and flashing a disabled vbmeta are the same thing though. I usually patch my AP_ file with the Magisk app and inside there's always a patched vbmeta to prevent this type of situation.
Maybe someone with the actual device can share an actual disabled vbmeta.img
OR, you can just install your stock recovery and flash TWRP later
Click to expand...
Click to collapse
How do I solve this if I can't get out of this bottom menu? Do you know where to get BL AP CP for SAMSUNG A305FN

DamDmaJoe said:
How do I solve this if I can't get out of this bottom menu? Do you know where to get BL AP CP for SAMSUNG A305FN
Click to expand...
Click to collapse
This is roughly what the error looks like only I don't have anything at the end in green like in the video -

Question [Updated] This is ENG binary Please Use USER binary after stock flash with Odin

New update to topic:
I decided to repair the software of my Galaxy S21 (Exynos) by flashing official firmware from Samfirmware, same version as I was running. It was in a bootloop before, so there was nothing esle to do. Phone was rooted with magisk, stock recovery.
I found what my firmware is from the recovery, found the exact same file, with the correct CSC.
Downloaded that firmware from Samfirmware, downloaded patched Odin from XDA.
Added, flashed, used HOME_CSC in order to preserve my data.
Reboot and immediately before I even get the boot logo or the charging animation, I get this error:
This is ENG binary Please Use USER binary
Allegedly this is what happens when you flash an engineering build, not an official one. But how? I downloaded and flashed official stuff? It's the exact same version my phone is already running. Where did I go wrong and how can I fix that?
I've attached the Download screen of my phone.
Thanks!
Old news:
Hello,
Hope this is the right place to ask for this kind of help.
I have a Galaxy S21 5G (SM-G991B), rooted with Magisk back in March 2021. Phone is bootloader unlocked, not encrypted, but the recovery is stock. Version currently running is Android 11. USB Debugging is enabled, but my computer is listed as unauthorised.
Yesterday my phone died due to low battery, so I plugged it and after it charged a bit I switched it on, only to be greeted with a constant bootloop. The bootloop is "soft", meaning only the system crashes, it doesn't go all the way to the initial boot screen (as if the battery was unplugged). The phone crashes about 1-2 seconds after the initial lockscreen is displayed.
Is there any way to help me recover this and save my phone? My entire life is there, from photos that can't be recovered, to authenticators I need for work and bank logins I need to be able to pay rent.
I thought about flashing TWRP and just doing a backup from there, but would it be as simple as that? All the tutorials talk about requiring to flash some extra zips and wiping the data, but those tutorials are combo root+twrp tutorials, and I've already done those steps. so no wiping should be needed to put TWRP on?
I'd be very grateful if anyone is profficient enough to help me recover the data, I already gave the phone to a data recovery company but they say it's unlikely anything will come out of it. If you manage to help me get my phone working as it was (or at least get my data back somehow), I'd gladly pay you the money for your efforts.
Help me XDA, you're my only hope.
Click to expand...
Click to collapse

Flashing TWRP = having to delete data (to be able to access the internal storage)
I am pretty sure (wait for confirmation before doing it) that if you flash the HOME_CSC file instead of the CSC on Odin it keeps your data.
This is why we need to vote with our wallets and buy phones with sd cards. I dont really care, because I never keep anything important on my phone, but I feel for you buddy.
EDIT: from here: https://www.droidviews.com/difference-between-csc-and-home_csc-samsung-firmware/
CSC – If you flash the CSC file, it’ll perform a factory reset of your Galaxy device and wipe all data while installing a new firmware to bring your device to the same state as it was when you purchased it. Go with CSC if you want a clean installation.
HOME_CSC – On the other hand, if you want to keep your Samsung phone’s data and settings even flashing the stock firmware, you can select the HOME_CSC file.
At your own risk, pls dont blame me if it doesnt work!

Flash a patched vbmeta again

GeeAyeZee said:
Flash a patched vbmeta again
Click to expand...
Click to collapse
Hi, what do you mean? Flash both TWRP and vbmeta, as if I'm doing it for the first time?
I think the phone was already decrypted while following the Magisk root tutorial, so these two steps should be the only thing necessary for the phone to boot to TWRP, right? I know how to rescue everything once I'm in there.

Try entering safe mode and disable all magisk modules:
Power on your Galaxy phone or tablet in Safe mode
We’ll walk you through how to start your Samsung Galaxy phone or tablet in Safe mode. This mode prevents third-party apps from running on your device.
www.samsung.com
You can access adb when on recovery mode or download mode so you can also enter safe mode via one of these commands:
setprop persist.sys.safemode 1
or
echo "1" > /data/property/persist.sys.safemode

dikime said:
Hi, what do you mean? Flash both TWRP and vbmeta, as if I'm doing it for the first time?
I think the phone was already decrypted while following the Magisk root tutorial, so these two steps should be the only thing necessary for the phone to boot to TWRP, right? I know how to rescue everything once I'm in there.
Click to expand...
Click to collapse
Flash the vbmeta file in odin

shaharofir said:
Try entering safe mode and disable all magisk modules:
Power on your Galaxy phone or tablet in Safe mode
We’ll walk you through how to start your Samsung Galaxy phone or tablet in Safe mode. This mode prevents third-party apps from running on your device.
www.samsung.com
You can access adb when on recovery mode or download mode so you can also enter safe mode via one of these commands:
setprop persist.sys.safemode 1
or
echo "1" > /data/property/persist.sys.safemode
Click to expand...
Click to collapse
The phone auto-enters safe mode after a few bootloops, so I guess that's beat. When the phone is in stock recovery, doing any adb commands tells me the device is recognized, but "unauthorized".

dikime said:
The phone auto-enters safe mode after a few bootloops, so I guess that's beat. When the phone is in stock recovery, doing any adb commands tells me the device is recognized, but "unauthorized
Click to expand...
Click to collapse
So you can enter download mode and flash stock (just super)

You gonna have to get authorized again. Check youtube for help. I had that issue a couple months ago. Think it had to delete the android folder and reinstall adb

Alright, decided to flash stock firmware with Odin. Found my files from Samfirmware, and since I want to keep my data, flashed HOME_CSC. Now the phone won't boot at all, giving the error:
This is ENG binary, please use USER
Now why did this happen and can I do anything to change that? I would really like to not flash CSC and wipe my phone, but it's looking more and more likely.
I used the patched 3.14.1 Odin, could that be the issue? Shouldn't matter.
The Download mode screen says:

Question Fixed - Root help

It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!

jcunwired said:
It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!
Click to expand...
Click to collapse
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.

lewmur said:
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.
Click to expand...
Click to collapse
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip

jcunwired said:
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip
Click to expand...
Click to collapse
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?

lewmur said:
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?
Click to expand...
Click to collapse
Because I was in ADB and like you said, what difference does it make?

jcunwired said:
Because I was in ADB and like you said, what difference does it make?
Click to expand...
Click to collapse
The difference is that your post said you installed Magisk and used it to patch the boot.img and it didn't work. Then the edit said you solved it by using adb to sideload magisk and that solved the problem. I'm still trying to understand how it did.