I rooted my Nokia 3.2 - Nokia 3.2 Guides, News, & Discussion

Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
patched boot.img :
https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w

bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
Click to expand...
Click to collapse
Hi, might be a stupid question but where is the patched boot.img/how do I do it myself?

Craventoby said:
Hi, might be a stupid question but where is the patched boot.img/how do I do it myself?
Click to expand...
Click to collapse
I will upload it, i downloaded the new firmware with june security patch and extracted the boot.img from it, you can do the same or wait when i go home to upload it for you

https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w

Craventoby said:
Hi, might be a stupid question but where is the patched boot.img/how do I do it myself?
Click to expand...
Click to collapse
https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w
enjoy

bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
patched boot.img :
Click to expand...
Click to collapse
Hey, I did root my phone with that but the wifi doesn't seem to work anymore.. do you have the same issue or/and do you have the stock boot.img file that I can try to flash ?
Thanks !

Hironichu said:
Hey, I did root my phone with that but the wifi doesn't seem to work anymore.. do you have the same issue or/and do you have the stock boot.img file that I can try to flash ?
Thanks !
Click to expand...
Click to collapse
https://mega.nz/#!6nJhQKba!XylZfJqVyRCXdIzZnVbhwhQFs5arpPf6Cg36mR0L9_Q

Hironichu said:
Hey, I did root my phone with that but the wifi doesn't seem to work anymore.. do you have the same issue or/and do you have the stock boot.img file that I can try to flash ?
Thanks !
Click to expand...
Click to collapse
Small update on this, there was an Android update recently, and it fixes everything ??* so if someone else here has the same issues somehow, updating to July update fixes it

I've some questions:
-does Nokia release his kernel source and which version use? on their website there is only for 3.1 I don't know if are same thing.
-Does support treble?

hello, now there is a august update for nokia 3.2 Do u have the boot file for that.. or how can I find it??

I add this phone to the list of my amazon.it account to make some stuff like twrp and roms but didn't buy yet, I'm afraid that Nokia will not release kernel source soon so in case of taking one I can make a twrp with stock kernel extracted from boot.img see ya.
Edit: buying this phone has been cancelled after reading unlocking bootloader seems to be "impossible" shame on you dear Nokia

disy
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
patched boot.img 8LSD2fhKkw6nCvdOKcU1j0w"]https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w[/URL]
Click to expand...
Click to collapse
Good afternoon, I HAVE BY THIS METHOD THE PHONE IN THE LOADER HANGED, HELP TO RETURN TO THE OPERATIONAL CONDITION.

bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb
Click to expand...
Click to collapse
Can you tell what your current build number is?
I suspect there is more than one firmware flavor around.
Thanks!
.

JFDee said:
Can you tell what your current build number is?
I suspect there is more than one firmware flavor around.
Thanks!
.
Click to expand...
Click to collapse
i dont know coz i sold the phone months ago but i managed to root it without problems you have just to patch it by your self with your current build and then flash it using fastboot mode

bouyhy01 said:
i dont know coz i sold the phone months ago but i managed to root it without problems you have just to patch it by your self with your current build and then flash it using fastboot mode
Click to expand...
Click to collapse
Thanks for replying!
Unfortunately, I don't have my current build as a separate firmware file, and QFIL is not able to get the boot image from my phone because the communication stops right away.
My build number starts with 00EEA, whereas your boot image (and the full stock ROM on Mega that you linked) contains 00WW. I'm not sure this firmware is compatible with my Nokia 3.2 ...
.

JFDee said:
Thanks for replying!
Unfortunately, I don't have my current build as a separate firmware file, and QFIL is not able to get the boot image from my phone because the communication stops right away.
My build number starts with 00EEA, whereas your boot image (and the full stock ROM on Mega that you linked) contains 00WW. I'm not sure this firmware is compatible with my Nokia 3.2 ...
.
Click to expand...
Click to collapse
if you have a link for the whole firmware i can download it and extract the boot.img for you and then upload it i do have a gigabit internet speed

bouyhy01 said:
if you have a link for the whole firmware i can download it and extract the boot.img for you and then upload it i do have a gigabit internet speed
Click to expand...
Click to collapse
Thanks!
I've looked around and so far could not find the stock firmware for my phone.
If I had it, I'm sure I could manage to extract the boot.img and let Magisk patch it (I've done that before with other devices).

JFDee said:
Thanks!
I've looked around and so far could not find the stock firmware for my phone.
If I had it, I'm sure I could manage to extract the boot.img and let Magisk patch it (I've done that before with other devices).
Click to expand...
Click to collapse
i found it but its a .bin

bouyhy01 said:
i found it but its a .bin
Click to expand...
Click to collapse
Thanks for your efforts - I was able to solve the problem today.
It seems there are different versions of the same "programmer" around that is used in QFIL to extract your own boot image from the phone.
Originally, I used the one provided by @hikari_calyx in his unlock thread. Today I noticed that the programmer file in the stock firmware you provide here has a slightly different size. I tried this one and it worked.
So I could extract my "boot.img" from the phone. Rooting was easy after that.
I think it's always safer to use one's own boot image than trying to flash one that was lying around elsewhere.
Here is my post in the other thread for reference. Thanks again for your research and for providing the stock firmware!
.

Hello JFDee,
is it possible that you upload your original or modified boot image also?
Because i flashed the boot image that was given here and now i have the same problem, like said before.
WLAN is not working anymore and the Boot time is very long. Updating also don't work.
I also saw the differences in the build numbers.
My is like yours 00EEA....
This would be really nice, because i don'T find the stock image for this number.
Best regards!!!!
JFDee said:
Thanks for your efforts - I was able to solve the problem today.
It seems there are different versions of the same "programmer" around that is used in QFIL to extract your own boot image from the phone.
Originally, I used the one provided by @hikari_calyx in his unlock thread. Today I noticed that the programmer file in the stock firmware you provide here has a slightly different size. I tried this one and it worked.
So I could extract my "boot.img" from the phone. Rooting was easy after that.
I think it's always safer to use one's own boot image than trying to flash one that was lying around elsewhere.
Here is my post in the other thread for reference. Thanks again for your research and for providing the stock firmware!
.
Click to expand...
Click to collapse

Related

NVIDIA Shield TV 2017 Root with developers image and Magisk, OREO (Shield 7.0.2)

While I tried to root using TWRP and all the suggested ways i continued to get errors, bootloops, corrupted boot, etc. I downloaded the rooted developers OS Image, then used magisk to patch the boot image. If anyone has any interest in the Boot.img or the developers OS image, let me know i can post links and instructions if needed. This will require the bootloader unlocked (i have read you can unlock with a keyboard, but i never had any luck and used a controller). Please reply with requests if needed.
Just one question: When you install the NEXT developer image, how will you go about retaining Magisk and your boot.img patch? Don't need a step-by-step-- just in simple terms. Curious.
EDIT: Found my answer: https://forum.xda-developers.com/showpost.php?p=77162700&postcount=85
I have a question i dont want create a thread for this so with root its possible to use 2 usb drive ?because for only the one right on the HDMI cable Work
laharl_22 said:
I have a question i dont want create a thread for this so with root its possible to use 2 usb drive ?because for only the one right on the HDMI cable Work
Click to expand...
Click to collapse
I'm not sure, but i think its possible to use 2 USB drives now if you turn off adb debugging or use a hub.
Michajin said:
I'm not sure, but i think its possible to use 2 USB drives now if you turn off adb debugging or use a hub.
Click to expand...
Click to collapse
Thanks it work
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
samjoandco said:
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
Click to expand...
Click to collapse
What version are you on? I downloaded the full zip, put the unzipped file on a USB from a computer. Then Took the USB to my Shield ran magisk manager 6.0 and installed, selecting patch boot, selecting the file from the USB. Magisk places the patched boot into my download folder where i pulled back onto my computer the fastboot flash boot boot.img (or patched_boot.img whatever the file is called that got patched).
I have the patched 7.1 boot.img right now. I have the full developers files, with drivers and patch all in it for 7.1 with magisk manager if you want i can put it on my Google drive for the whole thing. It is 1.09 Gb for the full files.
samjoandco said:
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
Click to expand...
Click to collapse
Guess i Didn't read very well! Here is the Boot.img for magisk 7.1.
fastboot flash boot boot.img
Use 7-zip to unzip, had to make it a tar to upload here (12mbs)
How to fix a bootloader who not boot ? I have only bootloader IS unlocked warning screen and NVIDIA logo but no os and unable to boot bootloader or twrp
laharl_22 said:
How to fix a bootloader who not boot ? I have only bootloader IS unlocked warning screen and NVIDIA logo but no os and unable to boot bootloader or twrp
Click to expand...
Click to collapse
I am assuming you have a nvidia shield 2017
Download the full image from nvidia here
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20TV%202017%20Developer&tx=$additional,shield
Connect via fastboot (plug in controller press A - B and power on)
From fastboot connect with a computer via A-A usb cable
unzip the file from nvidia into the folder where your fastboot drivers are
run the flash-all.bat file
Michajin said:
Guess i Didn't read very well! Here is the Boot.img for magisk 7.1.
fastboot flash boot boot.img
Use 7-zip to unzip, had to make it a tar to upload here (12mbs)
Click to expand...
Click to collapse
Thanks Michajin, much appreciated, I will try it on the weekend! :highfive::good:
One question:
I am on the latest 7.1.0 but not on developer image, can i just unlock the bootloader and flash the boot image to get root ?
or i need to installed the developer version (nv-recovery-image-shield-atv-7.1.0-dev_rooted)?
I dont want to install everything again.
samjoandco said:
Thanks Michajin, much appreciated, I will try it on the weekend! :highfive::good:
One question:
I am on the latest 7.1.0 but not on developer image, can i just unlock the bootloader and flash the boot image to get root ?
or i need to installed the developer version (nv-recovery-image-shield-atv-7.1.0-dev_rooted)?
I dont want to install everything again.
Click to expand...
Click to collapse
As far as i know Unlocking erases data anyways. You unlock you have to reinstall everything anyways.
The boot image works only on developer image? Thanks
gas80 said:
The boot image works only on developer image? Thanks
Click to expand...
Click to collapse
I don't know what the differences are between the dev image and the regular version. I believe the dev version is just pre-rooted. I think it will work, but i have only tested on the dev image. Flash at your own risk.
Hi there,
I need help. Im looking for a ROM thats flashable with TWRP so i can install it. Previously I had Lineageos installed but it wasnt running smooth enough.
I cant install the rooted recovery file from Nvidia with TWRP.
The reason why im wanting to use TWRP is because i want to use Magisk with the Shield.
Ive allready patched a stock boot image with magisk version 17.1
my current Twrp version is 3.2.1-1
Thank you very much
cheers
[Edit]
I solved the problem by following this post
thanks
Michajin said:
What version are you on? I downloaded the full zip, put the unzipped file on a USB from a computer. Then Took the USB to my Shield ran magisk manager 6.0 and installed, selecting patch boot, selecting the file from the USB. Magisk places the patched boot into my download folder where i pulled back onto my computer the fastboot flash boot boot.img (or patched_boot.img whatever the file is called that got patched).
I have the patched 7.1 boot.img right now. I have the full developers files, with drivers and patch all in it for 7.1 with magisk manager if you want i can put it on my Google drive for the whole thing. It is 1.09 Gb for the full files.
Click to expand...
Click to collapse
Could you please upload it on google drive. That would be greatly appreciated. :good:
gambaaa said:
Could you please upload it on google drive. That would be greatly appreciated. :good:
Click to expand...
Click to collapse
I dont know if it sent, here is a link for the dev image with magisk installed on the boot.img. The original and patched boot.img are in the zip file., along with the magisk app.
Please flash at you own risk, i have the 2017 shield and it worked for me. I ran the flash-all.bat.
Here is a link to the file on my GDrive ( I will be blocking access after the weekend)
Goodluck,
Michajin
Michajin said:
I dont know if it sent, here is a link for the dev image with magisk installed on the boot.img. The original and patched boot.img are in the zip file., along with the magisk app.
Please flash at you own risk, i have the 2017 shield and it worked for me. I ran the flash-all.bat.
Here is a link to the file on my GDrive ( I will be blocking access after the weekend)
https://drive.google.com/open?id=15sJ6YFmwiAZX0mXQk_ANq5Nfvs9E8oJF
Goodluck,
Michajin
Click to expand...
Click to collapse
Great job! I will try it this week-end. So I just plug my nvidia shield via usb and run the flash-all.bat ? Also, do I need to unlock my bootloader before doing anything. I have stock 8.0 oreo
gambaaa said:
Great job! I will try it this week-end. So I just plug my nvidia shield via usb and run the flash-all.bat ? Also, do I need to unlock my bootloader before doing anything. I have stock 8.0 oreo
Click to expand...
Click to collapse
Yes, as far as i know you have to have an unlocked bootloader. You plug in your Sheild VIA a-a USB, you might have to install the sheild drivers. Press AB on your controller and power on. That will get you into fastboot. You have to run the unlock bootloader command WARNING this will wipe your DATA. All the drivers you need will be on this page available to download https://developer.nvidia.com/shield-open-source and for instructions on how-to goto here http://nv-tegra.nvidia.com/gitweb/?...;f=README_NEW_SHIELD;hb=rel-24-uda-r1-partner (the instructions tell how to do flash each file, i found it faster to do the flash-all.bat, but be patient, i think it takes about 30 minutes)
Michajin said:
Yes, as far as i know you have to have an unlocked bootloader. You plug in your Sheild VIA a-a USB, you might have to install the sheild drivers. Press AB on your controller and power on. That will get you into fastboot. You have to run the unlock bootloader command WARNING this will wipe your DATA. All the drivers you need will be on this page available to download https://developer.nvidia.com/shield-open-source and for instructions on how-to goto here http://nv-tegra.nvidia.com/gitweb/?...;f=README_NEW_SHIELD;hb=rel-24-uda-r1-partner (the instructions tell how to do flash each file, i found it faster to do the flash-all.bat, but be patient, i think it takes about 30 minutes)
Click to expand...
Click to collapse
Wonderful! Thanks for the explanation!

Root available ?

Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
cubano2031 said:
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
Click to expand...
Click to collapse
Sent from my LGE LM-X410.FGN using XDA Labs
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Rebel_X said:
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Click to expand...
Click to collapse
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
Thanks a lot!! And it was as simple as that. It works fine. :good:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
MAREK10747 said:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
Click to expand...
Click to collapse
Hi,me devie is I4293
I have unrar the rom , so i get the boot_X-FLASH-ALL-8F02.sin
would you mind to make the kernel for me?
the file is here :
https://drive.google.com/file/d/1sywqfBtELSTgRXtTBEvlI454K_1ul-1h/view?usp=sharing
my gmail is [email protected]
you can send it to me.
thank you.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
yishisanren said:
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
Click to expand...
Click to collapse
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Zaben said:
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Click to expand...
Click to collapse
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
yishisanren said:
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
Click to expand...
Click to collapse
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
wang4632 said:
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
Click to expand...
Click to collapse
older version can not patch boot.img, because when you click "install the zip",it will let you update the new verison.
Any news on the boot loop situation? I also encounterd this problem and back to running original boot.img. having an unlocked bootloader is useless without root ?
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Did you lose any feature like super vivid mode and camera focusing after unlocking the bootloader?
can't find the driver, the model is l421dual sim, can't rooting, have i already patched the boot img?
My I4293 stuck in bootloop~~help ~!
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
This phone cannot be rooted at this time due to the lack of the img.patch and no driever.
Zack_U said:
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
Click to expand...
Click to collapse
Are you still stuck? For all of the latest Sony phones try NewFlasher instead.
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
Flashtool doesn't support our phones. Magisk 19.1+ currently doesn't work with our phones. Hopefully 19.4 will fix that.

Galaxy A11 SM-A115 Need TWRP

I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Why not compile a matching TWRP by yourself?
Look inside here.
@ jwoegerbauer i can give a try but have no experiences when it comes to makin a custom recovery.
ᐯerified Developer said:
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Click to expand...
Click to collapse
Yea, im also looking for a way to get some sort of custom recovery on the exact same device. My advice is (if you cant build your own version of twrp) to just wait for some devs to release something for it. The galaxy a11 is a very new device so we'll just have to wait it out.
Edit: So I followed a tutorial here (https://www.youtube.com/watch?time_continue=40&v=MyxGZbCuxDQ&feature=emb_logo) and i created this (https://filebin.net/u3yww2cyajktm043). IT MAY OR MAY NOT WORK!!! USE IT AT YOUR OWN RISK!!!!
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
ninjakira said:
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
Click to expand...
Click to collapse
You can put the device into download mode and unlock the bootloader from there...
I'm currently stuck on this device trying to get it to unlock the boot loader. I've ticked OEM unlock but when I get into download mode (adb reboot download) I'm not getting any option to unlock the boot loader there. I'm also not able to get into download mode with any key commands. Any ideas here?
I've heard you power off, then hold volume up and down when you plug in a data cable. Haven't tried it yet, I'm on the a115u t-mobile variant. I can get to what it calls download mode, which looks to be fastboot and NOT the standard samsung blue screen download mode. Just boot to recovery and select reboot to bootloader. I do not have oem unlock in my dev settings, but I'll see if I can fastboot oem unlock when I get back to my laptop.
flash sm-a115u1 version firmware first. gives you oem unlock option. obviously toggle on and adb debugging. power off the phone. hold both volume buttons and insert usb cable. it will look like the normal blue download warning screen but read it carefully. it says long press volume up to unlock bootloader. it works. it will go black. release volume up and next it will ask you to confirm. choose yes. it will reboot and erase. after skipping thru set up enable dev options again and you will see oem toggle greyed out with a caption "bootloader already unlocked". thats as far as ive gotten. because now im like "what now?" i need a custom recovery file to flash to the device. any help with that out there? so now that the bootloader is unlocked can i install magisk to root and if so after that how can i network unlock? any help would be greatly appreciated. also looking for any custom roms that are available for this a11(2020). seems like a decent phone.thanks.
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Is there any updates that can be flashed with stock recovery
griha41 said:
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Click to expand...
Click to collapse
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
sdell said:
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
Click to expand...
Click to collapse
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
griha41 said:
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
Click to expand...
Click to collapse
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
sdell said:
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
Click to expand...
Click to collapse
Ahh I see. Sorry then.
You shall do that way. Find current fiware for your device, download it through fine software.
A result you will get 5 files with .zip extension.
You need to unpack file with AP_ prefix, i suggest you to use 7zip for that stuff. From file you need took off the boot.img.
Then boot.img you shall pack into archive.tar,
When you've done, down load the Magisk apk from github and install on your phone. Move your jew archive to phone memory/diwnload folder and start the Magisk, make patching of kenel, as result you'll receive the magisk_patched.tar, copy that file to your pc and start the Odin, place that archive in AP slot and flash it.
PROFIT!
But I want to warn you in android 10 and up there root and kernel system are different, now system is booting from super.img, and partition /,/system and etc are RO, so through the root you'll not able to change anything in system it would be wiped on next system restart.

How To Guide [root]XQ-BC72 (China) and boot.img

so i rooted device. here are images.
guide later
my version is 61.0.A.10.1.release-keys
Chinese Stock
the original image
boot_X-FLASH-ALL-4BA8.tar.gz
magisk patched image
magisk_patched-23000_clKca.tar.gz
guide:
!!!DATA WIPE AUTOMATE!!!
1. unlock the device
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code
2.download the firmware.
use xperiFirm. find it in xda.
downloading takes me 20hr.
3.unsin the boot image
use unsin. also find in xda.
4.install magisk. and push boot image to device storage.
magisk in xda. or https://github.com/topjohnwu/Magisk/releases
5.follow magisk guide
https://topjohnwu.github.io/Magisk/install.html#patching-images
Copy the boot image to your device
Press the Install button in the Magisk card
Choose “Select and Patch a File” in method, and select the stock boot image
The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.
Copy the patched image to your PC with ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].img
Click to expand...
Click to collapse
fastboot mode is volume up and plug cable when power off
====if your downloaded my magisk patched image, you start here.====
Flash the patched boot/recovery image to your device.
For most devices, reboot into fastboot mode and flash with command:
fastboot flash boot /path/to/magisk_patched.img or
Reboot and voila!
Click to expand...
Click to collapse
6.open magisk follow it to root your device.
7.done
Sorry, after that i have to use the phone further with unlocked bootloader to keep root ?
Is the phone loose something functionality after unlocking ?
DennisDD78 said:
Sorry, after that i have to use the phone further with unlocked bootloader to keep root ?
Is the phone loose something functionality after unlocking ?
Click to expand...
Click to collapse
Good question. I m sure DRM would gone.
But since Chinese is really just AOSP. I m havent lost any functionality.
To be Tested:
Pair dualshock 4 game pad
HDMI input as Display
Camera seems OK. And encrypt phone And encrypt tf card works fine.
So what feature Other?
Hello,is there any way I can unlock the /system partition?
Hellp there, I also use XQ-BC72 but when I try to unlock my phone, typing “fastboot oem unlock 0x<insert your unlock code>” into CMD it will back a weird message:"FAILED (remote: 'Command not supported in default implementation')". Did U had solution? Thx a lot.
I can not get into the step of download that get stuck by the unlock step......wtf is it
Unlock code is replace by mine correctly...... Confusing......
zzqstcc007 said:
Unlock code is replace by mine correctly...... Confusing......
Click to expand...
Click to collapse
fastboot mode is volume up and plug cable when power off
Click to expand...
Click to collapse
you may need to install the fastboot driver manually
Hi everyone, this is my first post here on Xda,
I seem to have committed a costly mistake since this is not available in India, in a hurry i bought the Japanese version of this phone, the S0-51B,which incidentally is a single sim variant. Is there anyway of I can flash this Chinese Rom and achieve Dual Sim?
I saw online that there is not much hardware difference between this and the Chinese version. Can anyone kindly confirm this?.
lxjsilver said:
Hello,is there any way I can unlock the /system partition?
Click to expand...
Click to collapse
Hi,
someone found a way?
i wan't to make a root for ios emoji
hanania said:
i wan't to make a root for ios emoji
Click to expand...
Click to collapse
Just for emojis come on...

How To Guide Relock bootloader and get stock recovery oneplus nord 2 Indian/EU: works for any MTK device

Note: This process is shown for OnePlus Nord 2 and work for any MTK device just replace files as per your model you need to Serch for that)
Credits @Raygen @TheWing
After relocking bootloader you can do safety net pass check to confirm by using following app:
https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettes
Download Re LiveDVD mtk. Client ( this is ready mtk client ubuntu os no need to Install python, drivers ready to go iso)
re_livedvdV3.iso
drive.google.com
Download Rufus for windows 32/64bit)
https://github.com/pbatard/rufus/releases/download/v3.17/rufus-3.17.exe
Note:Relocking has been done on OOS 11.1 v13 so stock boot img of v13, vbmeta from update zip of v13 is required, recovery must be given below.
Your need to replace files as per oxygen os version you are using.
FOLLOWING are images of DN2101 A13 OOS UPDATE IMAGES EXCEPT RECOVERY IMAGE IT WILL WORK IN ANY PHONE, U NEED YOUR AS PER YOUR REGION I WILL UPDATE THREAD AFTER COLLECTING ALL HERE
Boot img (This is stock A13 indian, other regions must use there current OOS version boot img)( other mtk devices must use there boot img here)
https://forum.xda-developers.com/attachments/boot-img.5460945/
Stock recovery(in zip unzip it you will get img file this will work for any region)( other mtk devices must use there recovery img here)
https://forum.xda-developers.com/attachments/recovery_stock-zip.5464685/
Vbmeta:must have correct vbmeta of current OOS Rom. Version (from stock A13 indian update.zip if U r using EU, OR GLOBAL region NORD replace it with the current OOS version you are for which you want to relock)(other mtk devices must use there vbmeta img here)
vbmeta.img
drive.google.com
All files for EU DN2103 ON A12 UPDTAE :
EU varient v12 files:
Boot. Img:
https://forum.xda-developers.com/attachments/boot_stock_a12-img.5461083/
Vbmeta. Img/
vbmeta.img
drive.google.com
Recovery same link for all)
recovery_stock.zip
drive.google.com
Terminal emulator commands :
1) BOOT TO FASTBOOT connect phone to pc in on condition)
adb reboot fastboot
2)to relock bootloader in terminal emulator connect phone to pc in fastboot mode and type)
fastboot flashing lock
MTK client commands:
1)Flash boot img:
python mtk w boot boot.img
2) Flash recovery img:
python mtk w recovery recovery.img
3) Flash Vbmeta :
python mtk w vbmeta vbmeta.img
wifi is not working. everything working after relock bootloader but wifi is not working
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
Factory reset u r phone and reboot see
pankspoo said:
Factory reset u r phone and reboot see
Click to expand...
Click to collapse
i did it. but it's not working
farhansaeeddnp3021 said:
i did it. but it's not working
Click to expand...
Click to collapse
Update yourbphone to latest v14
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
NetSoerfer said:
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
Click to expand...
Click to collapse
Your device will go in to boot img corrupt after that.......
PLEASE NOTE: This isnt working if you are on a custom rom! My Bootloader ist broken and locked and I have to figure out how to fix this ****.
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
7tyjupiter said:
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
Click to expand...
Click to collapse
Check YASNAC app from play store if it's showing safety net check passed your locked.
While installation of OTA what's errors u r getting.
After locking OEM unlock not grates off actually now it's available to unlock again with switchable tab
Sorry for crossposting a lot today, but I am really stuck and it seems that this may be the tool I need. I am on A15, cannot lock bootloader and cannot update.
So, to be sure, for this to work I need the boot.img, recovery.img and vbmeta.img for A15 stock rom? If yes, where can I get those files?
I found the files! Thank you for this guide! It worked perfectly. I really thought my phone was completely bricked. Coming from a Pixel, the root/restore process on this thing is a complete nightmare!!
https://forum.xda-developers.com/attachments/boot-img.5460945/
this link says like this
Oops! We broke the matrix. Someone call Neo!​You do not have permission to view this page or perform this action.
Ok. So I think if f-ed up big time! only message I get now is a big red "!" and: "the current image have been destroyed please flash te correct image....
HELP!
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
lachatol said:
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
Click to expand...
Click to collapse
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
exis_tenz said:
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
Click to expand...
Click to collapse
I want to lock the botloader, I don't want root anymore. I just need to be sure that if I service the phone for reinstallation to the original firmware, then the bootloader will be locked. Will be? thank you for answer
No worries, it'll be locked after a factory flash!
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
extranoob said:
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
Click to expand...
Click to collapse
If u gets wifi issue just flash boot image of OOS version u r using via fastboot

Categories

Resources