Related
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...
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
fargonaz said:
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
Click to expand...
Click to collapse
Thanks for taking the time to the reply mate, sorry to hear about your M3.
I tried fastboot flash ramdisk ramdisk.img and it said flashed successfully but the device is still not booting. Nothing else seems to have changed either.
Let me know if I misunderstood what you wanted to try or if you have any other ideas.
Cheers
etheberge said:
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Click to expand...
Click to collapse
I think I am in a similar spot. I went from a custom ROM back to stock, but now all attempts at installing full OTAs fail. Did you ever figure this out how to fix it?
Thanks
hey! i accidentally deleted a backup for my device and now i have no system to boot off of
are there any roms available for mya-l11? all the ones i see on this sub are for the 2015 models. thanks
lbxda said:
hey! i accidentally deleted a backup for my device and now i have no system to boot off of
are there any roms available for mya-l11? all the ones i see on this sub are for the 2015 models. thanks
Click to expand...
Click to collapse
I could not find any custom Roms for your device.
I could find an stock Rom for the Mya-l41 trough.
Here is an link: https://mega.nz/#!wKpT1ZaS!CV-2E4sNnUwIurskAdqCDpDawWlZD2UeABtSELk_ffc
That should be an update.app or an flashable zip.
You may get Huawei Update Extractor and extract the system.img and boot.img of the update.app
After that flash system.img and boot.img from fastboot.
Warning. This may soft brick your device.
Good luck.
If i helped press the Thanks button
Thespartann said:
I could not find any custom Roms for your device.
I could find an stock Rom for the Mya-l41 trough.
That should be an update.app or an flashable zip.
You may get Huawei Update Extractor and extract the system.img and boot.img of the update.app
After that flash system.img and boot.img from fastboot.
Warning. This may soft brick your device.
Good luck.
If i helped press the Thanks button
Click to expand...
Click to collapse
i was able to flash the boot and recovery image, but i couldnt flash the system image
lbxda said:
i was able to flash the boot and recovery image, but i couldnt flash the system image
Click to expand...
Click to collapse
Does it show an error or anything?
Fastboot flash system system.img
ok, so i found what i thought was a stock rom for my device on some spanish forum and used sp flash tool to install it
problem is, sp flash tool formatted my phone, but encountered an error trying to install the firmware and now my phone wont boot and windows says its not recognised
is there any fix to this? or is my phone bricked?
hey again! i know this post has been a wild ride of me doing stupid stuff and bricking my phone, but i got the firmware back!
only catch is that i'm receiving some nvram error (which i got on my previous phone too. i swear this is the last time im going mediatek), so if anybody has a method that can fix this it'd be highly appreciated
thanks
Hi, Ibxda.
Can you please share with us where you found the stock rom, what went wrong with flashing, and how you managed to get the firmware back?
I have a running system, but I rooted it and cannot apply official upgrades. I'd like to go back, upgrade and root again. I would appreciate the info on your progress.
ifrag_svk said:
Hi, Ibxda.
Can you please share with us where you found the stock rom, what went wrong with flashing, and how you managed to get the firmware back?
I have a running system, but I rooted it and cannot apply official upgrades. I'd like to go back, upgrade and root again. I would appreciate the info on your progress.
Click to expand...
Click to collapse
You should root with Magisk, it's systemless and it should not affect updates. If you want to update you should flash stock recovery. After you updated you are free to flash Twrp again if you want. If you are rooted with SuperSU you should uninstall SuperSU and install Magisk
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Edit: I can flash system, I did flash kernel, I can flash recovery too, but when I try to flash anything else, it gives me that error
Edit2: can someone tell me which files do I need to extract via huawei update extractor to flash? I know that system.img is one of them
konopla4 said:
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Click to expand...
Click to collapse
Check if you're still FRP unlock in Fastboot.
ante0 said:
Check if you're still FRP unlock in Fastboot.
Click to expand...
Click to collapse
Both bootloader and from are unlocked
konopla4 said:
Both bootloader and from are unlocked
Click to expand...
Click to collapse
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
You could use HWOTA for Mate 10 Lite if you can get into stock recovery, as it will flash the full update.app rather than the limited partitions fastboot can flash.
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
Click to expand...
Click to collapse
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
konopla4 said:
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
Click to expand...
Click to collapse
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
Click to expand...
Click to collapse
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
konopla4 said:
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
Click to expand...
Click to collapse
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
ante0 said:
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
Click to expand...
Click to collapse
Waaaait it, I can update from TWRP?
Or is it a specialized one?
konopla4 said:
Waaaait it, I can update from TWRP?
Or is it a specialized one?
Click to expand...
Click to collapse
It's a script, but it needs a TWRP that's compatible. The one by Catuva21 is (or so I've heard).
Hey guys,
I've tried to update my Nord 2 to the newest software (A.12) but every time I try it, it just reboots after a couple seconds and displays an error message:"Verification error". I've tried rebooting it multiple times, without any success. It is rooted with magisk and the bootloader is open, but I don't have TWRP installed. Could you guys hook me up with a solution?
Regards
Take a look: https://forum.xda-developers.com/t/...rooted-nord-2-any-incremental-update.4347813/
Thanks for your reply, I really appreciate it! I've looked at it, but I haven't found a specific update from a.11 to a.12, I just didn't want to take the risk to update with the indian variant from a.11 to a.13.
AdamBarath said:
Thanks for your reply, I really appreciate it! I've looked at it, but I haven't found a specific update from a.11 to a.12, I just didn't want to take the risk to update with the indian variant from a.11 to a.13.
Click to expand...
Click to collapse
No need to download the update file from third parties. If you downloaded it from settings, you can find it in your internal storage at android/data/com.oneplus.ota/files
For the boot file instead, you can find boot files both for indian and Eu in that post
Raygen said:
No need to download the update file from third parties. If you downloaded it from settings, you can find it in your internal storage at android/data/com.oneplus.ota/files
For the boot file instead, you can find boot files both for indian and Eu in that post
Click to expand...
Click to collapse
Thank you, I really appreciate your help! I'm going to try it as soon as possible, do I have to flash the vbmeta.img, if I use my own update.zip file? (Sorry, I have literally zero knowledge)
AdamBarath said:
Thank you, I really appreciate your help! I'm going to try it as soon as possible, do I have to flash the vbmeta.img, if I use my own update.zip file? (Sorry, I have literally zero knowledge)
Click to expand...
Click to collapse
Yup, the order is:
Backup EVERYTHING.
Flash stock boot image for your current version (A.11)
Flash update.zip via recovery
Flash patched vbmeta via fstboot
Re flash TWRP via fastboot
Reflash magisk:
Flash the .zip it via recovery (not reccomended). OR,
Download and flash an already patched boot image for the updated version (A.12). OR,
Extract your stock updated boot image (A.12) with adb shell and dd (or download it), boot into system, patch the image with the magisk app, flash the patched boot image in recovery.
If during one of these steps you get back the stock recovery, just boot into fastboot and reflash twrp. Without magisk installed the rom tends to restore the stock recovery by itself.
Thank you for your help!
Worked like a charm!