Question Root ROG phone 5 tencent - can't check bootloader status - ASUS ROG Phone 5 / 5s

I know that there's a guide on how to root the rog phone 5 and I tried that but it doesn't work for my phone and I guess it's because I upgraded to the Version WW-18.0840.2103.26 which is the latest released on 4/26. Is there any way that I can root my device with this version?

VinceDoop said:
I know that there's a guide on how to root the rog phone 5 and I tried that but it doesn't work for my phone and I guess it's because I upgraded to the Version WW-18.0840.2103.26 which is the latest released on 4/26. Is there any way that I can root my device with this version?
Click to expand...
Click to collapse
Either pull the boot image from the phone or extract it from the payload
Copy it to the sdcard and run Magisk Manager to select the image file
Copy the modified image file back to the computer and flash it with fastboot

twistedumbrella said:
Either pull the boot image from the phone or extract it from the payload
Copy it to the sdcard and run Magisk Manager to select the image file
Copy the modified image file back to the computer and flash it with fastboot
Click to expand...
Click to collapse
Thank you for your effort on trying to help me out, I've been trying so many method on the phone with payload and termux but when I put in the code on termux to get python it doesn't work and I assume that it because of the version that I got. I also try to get the boot.img on computer with the latest ROG 5 firmware version using python, payload and the payload.bin file but not working when put in code.
One last thing I forgot to mention is the phone is tencent version, I tried to check if the bootloader is unlocked with the dial phone method and on computer method but nothing happened. Tried to download the app to unlock the bootloader from the link on the guides but the tab close instantly nothing happen.
Sorry if it's too long for reading

You may want to try using payload dumper on the computer instead of the phone. It sounds like the issue is trying to do everything through the phone.
There shouldn't be a popup to download the bootloader unlock tool.
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/AsusUnlock_1.0.0.7_210127_fulldpi.apk

twistedumbrella said:
You may want to try using payload dumper on the computer instead of the phone. It sounds like the issue is trying to do everything through the phone.
There shouldn't be a popup to download the bootloader unlock tool.
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/AsusUnlock_1.0.0.7_210127_fulldpi.apk
Click to expand...
Click to collapse
Thanks a lot! Finally I got a link for bootloader unlock app that work but havn't try it out yet.
I followed a tutorial that using the computer too, what I did is downloaded the Python, firmware zip and payload dumper. After that I extract and copied the payload dumper and payload.bin to python folder by following the steps from here: https://www.droidwin.com/extract-payload-bin-stock-boot-image/
Just to the step that using the first command in cmd I get error.
If there's any other link or forum on how to extract the boot.img of this firmware Version WW-18.0840.2103.26 please tell me. Thank you!

Related

[Request] How to Create Patched Boot Image

I am looking to learn how to extract a boot image to patch. The last source for patched boot images has not updated since 9.5.10. I would like to be less dependent and be able to do it on my own.
Can someone put together a quick tutorial on how to extract a boot.img so I can run it though Magisk and create a patched one?
https://forum.xda-developers.com/showpost.php?p=79548858&postcount=6
I have the current rooted AA boot image in the guide in my signature. I extract them directly from the phone.
ozfive said:
I am looking to learn how to extract a boot image to patch. The last source for patched boot images has not updated since 9.5.10. I would like to be less dependent and be able to do it on my own.
Can someone put together a quick tutorial on how to extract a boot.img so I can run it though Magisk and create a patched one?
Click to expand...
Click to collapse
1)Download payload dumper.
2)Extract payload file from rom zip.
3)Put payload file in payload_input folder.
4)Run exe file.
5)After process complete check payload_output folder. All extracted there.
Download payload dumper from here :- https://forum.xda-developers.com/attachment.php?attachmentid=4760222&d=1558078935
Patched boot images are irrelevant and only necessary for devices without a working TWRP recovery. If you want to root, either boot TWRP once or boot and install TWRP (recommended) and then install the magisk zip from there.
larsdennert said:
I have the current rooted AA boot image in the guide in my signature. I extract them directly from the phone.
Click to expand...
Click to collapse
How do you extract the boot.img from the phone? I have the tmo version and would like to say on the stock room with root.
Sent from my GM1915 using Tapatalk
You need root to extract a partition, but if you have root then you have no need for it except to share it so someone else can get root.
In other words are you rooted already? If not, you'll need to use the other instructions or get a rooted or non rooted image from someone with a T-Mobile phone.
I'm going to guess you could fastboot boot boot.img to any rooted boot image for the one plus 7 pro, have root and then install magisk.
larsdennert said:
You need root to extract a partition, but if you have root then you have no need for it except to share it so someone else can get root.
In other words are you rooted already? If not, you'll need to use the other instructions or get a rooted or non rooted image from someone with a T-Mobile phone.
I'm going to guess you could fastboot boot boot.img to any rooted boot image for the one plus 7 pro, have root and then install magisk.
Click to expand...
Click to collapse
Not rooted yet, but everything I have read so far is that you need a patched boot.img to root, or you can create one from the boot.img in an oos package with magisk manager. The problem is, there isn't a tmo oos package out there yet, so it looks like rooting the tmo software isn't possible at the moment. Is this correct?
Sent from my SM-T550 using Tapatalk
Is your bootloader unlocked? That would be step one. Read up on the thread for that.
Not yet, but will be....trying to get my research done before I go for it... don't want to mess it up, been a few years since I rooted a phone.
Sent from my GM1915 using Tapatalk

[REQUEST] TWRP or Stock boot.img

I want to install the Magisk but not achieved yet because of TWRP is not available and the stock boot.img not found.
Now OTA is coming(1.02.709.7), so I tried to obtain boot.img from the OTA image by the following steps but didn't succeeded.
Download the OTA image by checking the system update on the device.
The image will be stored on /sdcard/Download/OTA_1.01.709.1-1.02.709.7.zip
Copy the OTA image to PC and extract the file "payload.bin".
Use the payload dumper(Thanks to vm03), dump the boot partition from payload.bin but failed with the following error.
Processing boot partition.Unsupported type = 9
* Type of 9 is IMGDIFF according to what I found (no further info).
* I modified "payload_dumper.py" to dump only the boot partition.
Could someone please share the stock boot.img or TWRP for this device?
or tell me another way to achieve this.
Thanks.
I'm looking for it, too. :crying:
Did you get the 1.03.709.1 version boot.img file?
I don't think OTAs contain the whole boot.img, only the binary diff of the new version.
so far nobody has found a boot.img ? the device is around for some months now...
Is there still nothing? Not even a boot.img?
I will post my stock boot.img, recovery.img, and SW version # once I get to my computer.
Should be able to extract it with ADB/commands.
I'm not able to get anything using ADB/fastboot and no root method is working for me. I wish I had an OTA file to work with so I could patch the boot.img and try that but OTAs have already been done on this phone.
The only thing I've managed to do is unlock the bootloader.
Here is a copy of the OTA zip I'm running on
https://drive.google.com/file/d/122ky9if8FqTKz0tvqVi_8-FkA-GjHX9A/view?usp=drivesdk
And here is the payload.bin from that OTA
payload.bin
drive.google.com
So far I haven't managed to get the boot.img and I have a long day tomorrow. Maybe you guys can come up with something?
Well I downloaded the automated script version of payload dumper located here:
How to extract payload.bin from OTA update or firmware
In a few rare cases, you may need to extract the payload.bin that is part of firmware and OTA update files from some OEMs to get the stock boot and system images. This helps when you are looking un…
nerdschalk.com
And that payload.bin seems to only contain abl.img. Nothing else which is unfortunate.
like i've written before, the OTA simply does not contain the whole boot.img - only the binary difference from the previous build.
with only the difference it is not possible to reconstruct a whole boot.img
the only options i see is wait for a RUU or the kernel source to be published
Another OTA came through 227MB, extracted and only thing in there is abl.img again.
is this will work
HTCdev - HTC Kernel Source Code and Binaries
www.htcdev.com
can we find boot.img
Did you get the 1.00.468.1 version boot.img file?
I'll try to port twrp this week.
Just wait for the good news
4096abcd said:
I'll try to port twrp this week.
Just wait for the good news
Click to expand...
Click to collapse
please make one also for htc u20 5g if possibile
lostic-b said:
please make one also for htc u20 5g if possibile
Click to expand...
Click to collapse
Still there's no way to unlock the bootloader of U20

Root and Update

I got a 5 ii and will root soon after playing with stock for a few days. Currently on 58.0.A.10.3 and received 58 0.A.28.51 update notification.
Would it be better to root / update by flashing per guide, or can I update the rom and root using the same method?
mtshure said:
I got a 5 ii and will root soon after playing with stock for a few days. Currently on 58.0.A.10.3 and received 58 0.A.28.51 update notification.
Would it be better to root / update by flashing per guide, or can I update the rom and root using the same method?
Click to expand...
Click to collapse
Make the latest update normally if you're not rooted yet (Make a backup before continue)
Unlock your bootloader, and enable developer option & USB debugging
Download the latest firmware of your device with the tool xperifirm to have the flash_boot.sin
Use Unsin to make a patchable boot.img for Magisk and put it in your device
Download Magisk manager (use the beta or canary only)
Click "Select patch target file" and select the boot.img you just made
Then put the magisk_patched file to your computer and put your phone into fastboot mode
and flash magisk_patched both slots A&B
Reboot.
flyl0 said:
Make the latest update normally if you're not rooted yet (Make a backup before continue)
Unlock your bootloader, and enable developer option & USB debugging
Download the latest firmware of your device with the tool xperifirm to have the flash_boot.sin
Use Unsin to make a patchable boot.img for Magisk and put it in your device
Download Magisk manager (use the beta or canary only)
Click "Select patch target file" and select the boot.img you just made
Then put the magisk_patched file to your computer and put your phone into fastboot mode
and flash magisk_patched both slots A&B
Reboot.
Click to expand...
Click to collapse
I asked because I didn't see any post saying that the phone can be rooted using the same method on 58.0.A.28.51 firmware. Are you saying the same method will work on the new firmware version?
mtshure said:
I asked because I didn't see any post saying that the phone can be rooted using the same method on 58.0.A.28.51 firmware. Are you saying the same method will work on the new firmware version?
Click to expand...
Click to collapse
if you take the boot.sin file and create a patchable img of each updates and patch this file with magisk after flashing the update with newflasher then yes. Just don't forget to remove userdata.sin & persist.sin to keep your data.
The method to root will never change.
flyl0 said:
if you take the boot.sin file and create a patchable img of each updates and patch this file with magisk after flashing the update with newflasher then yes. Just don't forget to remove userdata.sin & persist.sin to keep your data.
The method to root will never change.
Click to expand...
Click to collapse
I haven't rooted my device yet, but given that the method to root is the same, it looks like it will be better to update first then root because it will reduce the number of steps needed. Thank you for the reply.
mtshure said:
I got a 5 ii and will root soon after playing with stock for a few days. Currently on 58.0.A.10.3 and received 58 0.A.28.51 update notification.
Would it be better to root / update by flashing per guide, or can I update the rom and root using the same method?
Click to expand...
Click to collapse
I am having some difficulties rooting the phone. I have the bootloader unlock code, but each time I try to unlock the bootloader (https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/) it doesn't work. I am able to get into recovery mode on the phone, but plugging it i, and running "fasboot devices" yields nothing via the Android SDK. I have another thread open, and am willing to give you a $100 USD gift card for the assistance! "
"Sony Xperia 5 II XQ-AS62 root"
Thank You!

Can't find boot.img for my phone

Hello, I'm trying to root my phone again. I have my bootloader unlocked and was able to find TWRP-3.5.0-9-0-guacamole (image and installer).
But in every tutorial they say you need to have a boot.img. I tried looking for Oneplus 7 Pro OOS 10.0.11 GM21BA but I can't find anything and I am scared to try it with the wrong files.
Does anyone know where I can find it? Or is it safe to flash Magisk only and not the TWRP recovery because I saw somewhere that that would patch your boot.img and it would be safe.
I would like to keep all the files I have on my phone currently so I am asking before I am going to attempt anything lol.
Here is some info about my phone:
Model: GM1913
Build: Oxygen OS 10.0.11.GM21BA
Android: 10
I am trying to follow this tutorial: https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
In the written tutorial it doesn't say anything about needing a boot.img but in the video the guy is talking about it.
I also was wondering if I have the correct files so far.
with "payload dumper" it can be extracted from the full OTA update file
ghost323 said:
with "payload dumper" it can be extracted from the full OTA update file
Click to expand...
Click to collapse
Yeah I also saw something like this but I can't find how to find the payload.bin file OR the full OTA update file xD
I found a full OTA when putting my build into Google and then limiting search results to only this month.
Then I used payload_dumper to successfully extract the boot.img and now I can follow the tutorial again.
ƪ(ړײ)‎ƪ

Question Nord 2T 5G Full Factory ROM/Firmware with Scatter file for Unbricking

After successfully rooting my Nord 2T by backing up and then patching the stock boot.img I proceeded to patch the inactive slot within Magisk (it was unecessary of me..) and after rebooting entered a loop. Anyone know where I can get the factory ROM? I was on the May patch. Thanks in advance!
I am also looking for the factory OTA image.
How did you get the boot.img exactly?
jolaviska said:
I am also looking for the factory OTA image.
How did you get the boot.img exactly?
Click to expand...
Click to collapse
Good ol SP Flash but I think the backed up images are corrupted hence the need of factory firmware to use it to restore my device.
Apologies I did not realise you still needed the firmware. I have mirrored it here if you still need it May Patch Full ROM
garylawwd said:
Apologies I did not realise you still needed the firmware. I have mirrored it here if you still need it May Patch Full ROM
Click to expand...
Click to collapse
So extracting boot. img from your file won't be enough to do Root right?
Riski3Run said:
So extracting boot. img from your file won't be enough to do Root right?
Click to expand...
Click to collapse
You can't extract from the firmware. You must use spflash tool to pull the boot.img from the device (mediatek devices are a bit different to Snapdragon devices)
I'm going to do it today but I had to bring my daughter to the hospital after a fall she had which required stitches.
Once I have it extracted I might write a guide on how to do it with links to all firmware needed and have a thread where we will have both the stock and magisk patched boot.img's available.
Been like 6 weeks and no root on my device, this is the longest I have went without rooting in almost 7 years
garylawwd said:
You can't extract from the firmware. You must use spflash tool to pull the boot.img from the device (mediatek devices are a bit different to Snapdragon devices)
I'm going to do it today but I had to bring my daughter to the hospital after a fall she had which required stitches.
Once I have it extracted I might write a guide on how to do it with links to all firmware needed and have a thread where we will have both the stock and magisk patched boot.img's available.
Been like 6 weeks and no root on my device, this is the longest I have went without rooting in almost 7 years
Click to expand...
Click to collapse
Thanks. I rooted mine within a day but went too far with patching the inactive slot via Magisk and now phone is soft bricked. If you are still interested in extracting the boot image for patching then use this tool. I tried to use it to flash the payload.bin but phone still not booting. I even flashed all the extracted images manually in fastbootd. I guess the OTA file doesn't contain all the files needed to restore the device back to its factory state.
Anyone with the full firmware containing the SP Flash Scatter file please share it. You'll be saving everyone else. I bought my phone on a trip and there are no OnePlus repair centers over here so won't be using my phone until I can restore it myself
garylawwd said:
Apologies I did not realise you still needed the firmware. I have mirrored it here if you still need it May Patch Full ROM
Click to expand...
Click to collapse
Hello
Can't you upload this zip file somewhere else?
Each time download is not finished.
Riski3Run said:
Hello
Can't you upload this zip file somewhere else?
Each time download is not finished.
Click to expand...
Click to collapse
Saw you were able to fully extract the payload.bin so could you mirror the files as well..
Issue is now resolved Thanks @Riski3Run and @garylawwd
Alternatively extracting and flashing the payload.bin ALSO works. No need to extract the images just use this beautiful tool
garylawwd said:
Apologies I did not realise you still needed the firmware. I have mirrored it here if you still need it May Patch Full ROM
Click to expand...
Click to collapse
Hi Garylawwd, when I click on the link it displays an empty folder. Can you perhaps reupload the firmware? My device is bricked and I'm unable to find the stock rom and scatter file for CPH2399 :/
woodiewood3 said:
Hi Garylawwd, when I click on the link it displays an empty folder. Can you perhaps reupload the firmware? My device is bricked and I'm unable to find the stock rom and scatter file for CPH2399 :/
Click to expand...
Click to collapse
Were you on the latest June security patch?
garylawwd said:
Were you on the latest June security patch?
Click to expand...
Click to collapse
Yes I was on the June patch, but I completely messed up my Phone.. can't boot into recovery or fastboot, screen stays black.
When I plug in the phone my computer recognizes it as Mediatek usb port.
When I try to use mtk_gui it is able to connect but it freezes after DA extension and thus I'm unable to read or write anything from or to the device via mtk_gui.
I hope that I can flash the stock firmware via SP flash tool, otherwise I will probably need to send it to OP repairs centre.
But to flash via SP flash tool I do need the firmware + scatter file. ATM I'm unable to find them.
I am unable to create the scatter file via MTKDroid it says --- Unknown ROM structure, backup NOT possible!

Categories

Resources