Related
Is it specific for each device? Or does it depend only on finding the correct partition/block to be extracted?
Could you point me to further readings about that?
Thanks.
It is at least device specific, for extracting the bootimage, check this http://forum.xda-developers.com/showthread.php?t=1951426
Sent from my Acer Cloudmobile S500
IF YOU THINK I MADE SOME SENSE, PLEASE HIT THE THANK BUTTON !!!
What if everything is an illusion, and nothing exists?
In that case, I definitely overpaid my carpet....!
DopeyTheOne said:
It is at least device specific, for extracting the bootimage, check this http://forum.xda-developers.com/showthread.php?t=1951426
Sent from my Acer Cloudmobile S500
IF YOU THINK I MADE SOME SENSE, PLEASE HIT THE THANK BUTTON !!!
What if everything is an illusion, and nothing exists?
In that case, I definitely overpaid my carpet....!
Click to expand...
Click to collapse
Well, that link is to proceed AFTER you have boot.img at hand. I want to find a way to extract it from my phone (assuming default.prop can be changed in there).
Thanks.
When you make a back up with CWM, you have a copy of your bootimage in the clockworkmod map, not?
That's the thing ... I am trying to figure out how to get that backup in hand at first.
Currently, following the method in http://droidcore.blogspot.com.br/2012/12/how-to-edit-initrc-in-android.html
It seems to use the same scripts as cited in your link.
Will post results afterwards.
Don't make things more complicated as they are. If you just install CMW recovery (or TWRP for that matter) for your device, you have your full backup in minutes, including one of your bootimage, then use the script from my first post.
I managed to find boot.img, made the necessary changes, sent it back to device (used MPK Rom Studio and SP Flash Tool).
The problem is, the reason I want to change boot.img is to root my device. I thought that disabling ro.secure, I would be able to do so. But I couldn't.
I believe cmw recovery, or twrp, both need my phone to be rooted, no?
MrCabana said:
I managed to find boot.img, made the necessary changes, sent it back to device (used MPK Rom Studio and SP Flash Tool).
The problem is, the reason I want to change boot.img is to root my device. I thought that disabling ro.secure, I would be able to do so. But I couldn't.
I believe cmw recovery, or twrp, both need my phone to be rooted, no?
Click to expand...
Click to collapse
I used a CWM image to root my device. Booted up with that image, and flashed SU....after that you can use su, and apparantly, with the changes you made with your bootimage...you'll be like God on your phone
Sent from my S500 using xda app-developers app
I have the same problem, I need the boot image of my device to root it using magisk manager, but I can't find it.
Help!!!!!
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
I think this only possible when you have root..
It is also not possible with adb without root...so
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Edit:- If your device is Mediatek, using SP Flash Tool you can readback. If you have Snapdragon, then bkerler's edl tool can readback. (No need of root)
HemanthJabalpuri said:
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Click to expand...
Click to collapse
Do you mean the stock firmware on the device, where is this located? or do you mean from the vendors web page?
bromeara said:
Do you mean the stock firmware on the device, where is this located? or do you mean from the vendors web page?
Click to expand...
Click to collapse
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
Alright thank you. I'm fairly new to the android ecosystem and to boot I'm working on a Fire tablet so its running fireos and amazon doesn't really make it easy to touch their code
think he is facing the same situation as mine, for hk version of htc u12+, its hard to find the proper RUU or firmware from internet. Just wanna know the method of ...pulling the boot.img directly from device. Thanks in advance for any assistance.
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
Vita.T said:
Just wanna know the method of ...pulling the boot.img directly from device. Thanks in advance for any assistance.
Click to expand...
Click to collapse
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
I think this only possible when you have root..
It is also not possible with adb without root...so
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Edit:- If your device is Mediatek, using SP Flash Tool you can readback. If you have Snapdragon, then bkerler's edl tool can readback. (No need of root)
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
It's not that simple though, firmware comes in KDZ extension..have to extract using Extraction tool & even then extracted files are in .BIN extension..Boot.img is not available immediately after DZ extraction
dano.556 said:
It's not that simple though, firmware comes in KDZ extension..have to extract using Extraction tool & even then extracted files are in .BIN extension..Boot.img is not available immediately after DZ extraction
Click to expand...
Click to collapse
Ok....
I am assuming that the op has a samsung device....
Same Problem
Loku_kika said:
I have the same problem, I need the boot image of my device to root it using magisk manager, but I can't find it.
Help!!!!!
Click to expand...
Click to collapse
The Boot Image for oppo ax7 isn't available so i am trying to find aswell, OR i need help: taking the boot.img off my unrooted, non bootloader unlocked phone. Or extracting it from the stock ROM, unfortunately i'm not ble to open oppo's OFP file.
Lloydster said:
The Boot Image for oppo ax7 isn't available so i am trying to find aswell, OR i need help: taking the boot.img off my unrooted, non bootloader unlocked phone. Or extracting it from the stock ROM, unfortunately i'm not ble to open oppo's OFP file.
Click to expand...
Click to collapse
just google "Latest Software Version for OPPO OPPO AX7" and go to the Software Updates page on oppo-uk.custhelp.com. Download 2.4GB ozip file (like CPH1903EX_11_OTA_0210_all_oStq7F7jxqfF.ozip) and unpackit with 7zip program. You'll find boot.img inside .ozip file.
I do not have root, there is no recovery or rom for my phone, Can I extract the boot.img from my phone storage, to patch it with Magisk?
Before moving forward, you must understand that if anything happens with your device, I'm not to be blamed on, you choose to flash this
Hey guys, so a friend of mine bricked his OnePlus2 to a state that his recovery wasn't working (wiped) and also his ROM was bootlooping. So I thought of this little trick to convert the latest full OTA zip file into fastboot flashable stock ROM files by converting the system.new.dat into system sparse image. Though my friend recovered his phone by flashing recovery and sideloading zip. I still think it would be a good idea to share here
Download: OOS 3.5.8
Requirements: must have fastboot
Must have fastboot drivers
Must have knowledge on how to use these commands
Note: this is not rooted or tampered with, with this system firmware you should be able to get OTAs
Happy unbricking!
Nice, might become useful
Thanks
MZO said:
Before moving forward, you must understand that if anything happens with your device, I'm not to be blamed on, you choose to flash this
Hey guys, so a friend of mine bricked his OnePlus2 to a state that his recovery wasn't working (wiped) and also his ROM was bootlooping. So I thought of this little trick to convert the latest full OTA zip file into fastboot flashable stock ROM files by converting the system.new.dat into system sparse image. Though my friend recovered his phone by flashing recovery and sideloading zip. I still think it would be a good idea to share here
Download: OOS 3.5.8
Requirements: must have fastboot
Must have fastboot drivers
Must have knowledge on how to use these commands
Note: this is not rooted or tampered with, with this system firmware you should be able to get OTAs
Happy unbricking!
Click to expand...
Click to collapse
Got a
no file in this folder
Click to expand...
Click to collapse
when clicking the link.
casual_kikoo said:
Got a
when clicking the link.
Click to expand...
Click to collapse
Try again, the file seemed to be removed because something happened to the backend servers of AFH
Hey man. Can I still do this if my device is locked. Whenever I try to flash twrp recovery it will display unable to patch image device is locked.
Hope you can help me Bro. Thank you! ?
conqueror_25 said:
Hey man. Can I still do this if my device is locked. Whenever I try to flash twrp recovery it will display unable to patch image device is locked.
Hope you can help me Bro. Thank you! [emoji4]
Click to expand...
Click to collapse
No you can't flash images while you're locked, use fastboot oem unlock to unlock your bootloader
Thank you for your prompt response mate.
Please allow me to post my problem here with my phone.
* Hi everyone. Hope somebody can help me restore my phone again. I have successfully unlocked the bootloader of my phone but I cannot boot to Rom. Every time I power on the phone it will boot to CM stock recovery. Tried to flash TWRP recovery but unable to write image. Device is locked. Did some research and found out the reason behind this is I did not unable update to CM Recovery in Developer Options.
What is the best way to resolve this issue? I still have access to Fastboot and can do ADB commands but device is locked.
Will sideloading a stock CM OP2 Rom will fix the issue? I'm also concerned with the draining of the battery, if I cannot turn on because no more charge already.
I'm using Mac computer but I can borrow a windows laptop to fix this.
Any help will be highly appreciated..
Thank you very much in advance guys!
God bless!
conqueror_25 said:
Thank you for your prompt response mate.
Please allow me to post my problem here with my phone.
* Hi everyone. Hope somebody can help me restore my phone again. I have successfully unlocked the bootloader of my phone but I cannot boot to Rom. Every time I power on the phone it will boot to CM stock recovery. Tried to flash TWRP recovery but unable to write image. Device is locked. Did some research and found out the reason behind this is I did not unable update to CM Recovery in Developer Options.
What is the best way to resolve this issue? I still have access to Fastboot and can do ADB commands but device is locked.
Will sideloading a stock CM OP2 Rom will fix the issue? I'm also concerned with the draining of the battery, if I cannot turn on because no more charge already.
I'm using Mac computer but I can borrow a windows laptop to fix this.
Any help will be highly appreciated..
Thank you very much in advance guys!
God bless!
Click to expand...
Click to collapse
This is weird. You should start a new thread about ut
I already did. Thanks man. Appreciate your reply. ?
Where is the fastboot command it is not visible
niteshnandi said:
Where is the fastboot command it is not visible
Click to expand...
Click to collapse
You have to install fastboot and adb from
https://forum.xda-developers.com/showthread.php?t=2588979
[TOOL] [WINDOWS] ADB, Fastboot and Drivers -… | Android ...
Hi @MZO,
After downloading https://androidfilehost.com/?w=files&flid=169179, the file seemed corrupted, since it seems that the file could not be fully extracted.
Please kindly verify it.
Thanks.
Thanks to serajr here - https://forum.xda-developers.com/showpost.php?p=75505302&postcount=2973 Go directly to that post and give thanks.
You need:
Stock O ftf (best to use Flashtool/Xperifirm)
Modded boot img for 34.4.A.2.19 - https://mega.nz/#!AgtQ2Sob!JjLRcUVjuy6FNanjGY49g-YYmkcda04witfHp4hwvmo
Modded boot img for 34.4.A.2.32 - https://mega.nz/#!Z1tzEJbZ!e9ET_RtUpKjXRwnJa_TDsMrVwvT-hPxmk06KtryHOuc
Modded boot img for 34.4.A.2.85 - https://mega.nz/#!p5UwAabR!_ofmr_WdId9RdH48Xb3cZtSIzsQ6qcTJTAFYcKHFWJE
Kernel elf file to use with rootkernel [34.4.A.2.85] - https://mega.nz/#!M102lYTZ!9bj2KE-vbNWlej3Dw0NuiXJcfpgiy16svSHud73bLfw
Modded boot img for 34.4.A.2.107 - https://mega.nz/#!Nls0EQBR!Cc4lVcA85f8YeNTo8nMqsuwLzveW5duSbyeZDlI5kDE
Kernel elf file to use with rootkernel [34.4.A.2.107] - https://mega.nz/#!Zp10CASK!iGLE94Tj1SSk1U2p4KLpVrcGmD68C3YvqKMXD6VPFjI
Modded boot img for 34.4.A.2.118 - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA
Kernel elf file to use with rootkernel [34.3.A.2.118] - https://mega.nz/#!Ylcm1SwA!GuX9dfd2HAqLXy1jom-C6mgP0s4jYXl9qSySkvb_mtA
TWRP - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
1. Flash stock ftf from Xperifirm via Flashtool
2. After flash, connect in fastboot (before booting phone) and type in command line 'fastboot flash boot boot.img' (this assumes that your modified boot img is in the current directory,and is named 'boot.img'; otherwise, you need to edit the command accordingl)
3. Then type 'fastboot flash recovery twrp-3.2.1.img' (same note as above)
Done
Now, you can flash Magisk, (or whatever), and have root access.
If you want Drm fix, flash serajr's zip here - https://forum.xda-developers.com/attachment.php?attachmentid=4404527&d=1517335127
If you want to restore your own ta with munjeni tool, you will need to patch boot img yourself with rootkernel tool here - https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
How to get stock kernel elf and patch your boot img with rootkernel:
1. Download and build stock ftf from Xperifirm via Flashtool
2. Go to Flashtool > tools > sin editor, and navigate to stock kernel sin file, in the downloaded firmware folder. Click on sin file and choose 'exrract data', and it will create a kernel elf.
3. Follow the guide by serajr. You need only to put the kernel elf into rootkernel folder, then open a command prompt there and run 'rootkernel kernel.elf boot.img'. Answer all questions 'yes', unless you want to skip drm fix and restore your own ta, (if that's the case, you need your target file in that folder renamed to TA.img). After script runs, you will have a new boot img that you can use to follow the guide.
Done...
Magisk, MicroG, and Xposed tested... (update - I haven't tried yet, but I've read that Xposed not working on ...85; update 2 - confirmed, bootloop; update 3 - Xposed fix now available here - https://forum.xda-developers.com/x-compact/themes/xposed-fix-118-t3870673)
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Can confirm the above method worked for me. I used the TA.img instead of drm fix, and i get root and security test still have widefine and fidokeys enabled.
Just slight reminder for linux user, you need to add execute permission on both `rootkernel` and `bootimg`, otherwise rootkernel tool will fail with permission issue.
levone1 said:
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Click to expand...
Click to collapse
With which options is your modified boot image prepared?
maluus said:
With which options is your modified boot image prepared?
Click to expand...
Click to collapse
Dm-verity disable - yes
Force encrypt disable - yes
Drm fix - yes
For Drm fix you still have to flash serajr zip. If you want to restore ta with munjeni tool, you will need to patch boot yourself.
Op updated for 3-click root...
SuperSU,Xposed
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
...
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
I was able :laugh::good: Xposed release link
levone1 said:
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
Click to expand...
Click to collapse
Oh, well. Thank you! It's working now.
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Stephenhs said:
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Click to expand...
Click to collapse
Can you try running the tool and creating the boot.img yourself? I use the singapore ftf and doesn't have problem booting the system (with the boot img I created myself). I do not put twrp on boot img though. I boot twrp from fastboot when needed
I created boot.img and everything works Thanks a lot!
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Kianush said:
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Click to expand...
Click to collapse
Post linked in op has special instructions for us with Xc - skip that part.
https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
hello guys, i've created a boot.img whit the tool of rootkernel whit my ta.backup but it does not work. the boot it's ok but if i chek my drm keys they say not provisioned. my ta.backup load 2.097.152 byte like the post shows. can someone help me? thanks
update:
sorry guys, i've done again the kernel patch whit my ta backup and this time goes perfect. i don't know why the first time didn't work but now it's ok!
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Wxfdswxc said:
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Click to expand...
Click to collapse
Twrp - https://forum.xda-developers.com/x-compact/development/twrp-3-2-1-decryption-t3751998
As for rebooting to system, can't say for sure... Root method involves only changing boot img, so shouldn't affect system. Any errors in fastboot, etc?
Original flash should be clean flash official stock ftf from Xperifirm. First boot could be 10 minutes...
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.
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