Develop Bugs

Dtb not found

While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.

Samir 120 said:
While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.
Click to expand...
Click to collapse
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".

Neon丶 said:
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".
Click to expand...
Click to collapse
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.

Samir 120 said:
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.
Click to expand...
Click to collapse
No, not flash. Just boot.
Sounds like you are not running the command from the folder with the patched boot file. Or the file has a different name.

How do I extract a boot image from a GSI rom without TWRP.

I recently bought a Chinese phone from a relatively unknown manufacturer, so I was unable to find any TWRP images that match the device, I was wondering if it was possible to extract the boot image directly from a GSI ROM. My end goal is to install Magisk so if there is a better way to go about this please let me know.

can you tell model and brand

Hsnmastoor said:
can you tell model and brand
Click to expand...
Click to collapse
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.

XDA-Developer30 said:
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
Click to expand...
Click to collapse
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter

Hsnmastoor said:
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Click to expand...
Click to collapse
Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek
If you wish to root your Mediatek Android phone, we'd dropped a guide on rooting using Magisk and stock boot.img at https://www.hovatek.com/forum/thread-21427.html , no custom recovery is required. Se
forum.hovatek.com

Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!

LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
Thank you for the reply, I forgot to mention that I used Hsnmastoor's method successfully.

LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?

elmapq said:
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
Click to expand...
Click to collapse
And your device is...???

LinhBT said:
And your device is...???
Click to expand...
Click to collapse
Tecno Spark 6 ke7

LinhBT said:
And your device is...???
Click to expand...
Click to collapse
I have a Vortex V22 MTM6761 There is no stock rom. It has unofficial GSI Pixel experience plus 13.0 running on it. I too would like to root. How can I retrieve the boot.img file from the GSI rom? Or how can I pull it from the phone via terminal and fastboot? All help is greatly appreciated! Happy Saint Patricks Day!

For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device

LinhBT said:
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
Click to expand...
Click to collapse
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?

defcondoc said:
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
Click to expand...
Click to collapse
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!

.

LinhBT said:
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
Click to expand...
Click to collapse
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!

defcondoc said:
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
Click to expand...
Click to collapse
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.

LinhBT said:
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
Click to expand...
Click to collapse
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?

I have 2 models I cannot find stock ROM's for:
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB - manufacture date year 2022
Moxee M2160 Model MH-T6000 2APQU-MH-T6000 Q6006_V1.0 - manufacture date year 2022
Can anyone find anything? I have scoured the web for months!
I can't believe there is nothing available for these phones.
Please let me know if you can find a stock ROM. I would love to learn where and how you found them. As I've have found nothing for months and months.
Thank you!!!

defcondoc said:
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
Click to expand...
Click to collapse
You CAN extract the boot.img via terminal ONLY IF you're on a ROOTED devices!

How do I root my phone?

What are the steps to rooting my phone safely?
I'm on MIUI 12.5.7.
I've done a lot of research but I'd like to confirm on here before doing anything just in case, I can provide any other information needed, thanks!

You want confirmation ? Then list what are the steps and we will approve or disapprove.

Fytdyh said:
You want confirmation ? Then list what are the steps and we will approve or disapprove.
Click to expand...
Click to collapse
I'd like a definitive list of what to do lmao, I've seen lots of different ways to do it so there's confusion on what to do.
from what I can tell the basic steps are to unlock bootloader, flash custom recovery then flash magisk?

yes those are the basic steps. do go on. you said that you ve made a lot of "research" but so far i have not seen any. dont be lazy or you will hard brick your device.

Fytdyh said:
yes those are the basic steps. do go on. you said that you ve made a lot of "research" but so far i have not seen any. dont be lazy or you will hard brick your device.
Click to expand...
Click to collapse
Eh hard-bricks are not a big deal anymore.
As for rooting:
1)Unlock your bootloader using MiUnlock (or mtkclient if you are impatient)
This will wipe your data unless you are using mtkclient. (which to my surprise doesnt wipe data)
2)Disable Android Verified Boot (causes soft-brick if u dont)
Extract vbmeta.img from the ROM zip file then flash it using this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2)Install TWRP
MIUI 12.5 TWRP:https://sourceforge.net/projects/be...rp-3.5.2_11-0-UNOFFICIAL-begonia.img/download
3)Download Magisk, rename .apk to .zip then flash it.
That's it. Now you have a rooted phone.

Canny1913 said:
Eh hard-bricks are not a big deal anymore.
As for rooting:
1)Unlock your bootloader using MiUnlock (or mtkclient if you are impatient)
This will wipe your data unless you are using mtkclient. (which to my surprise doesnt wipe data)
2)Disable Android Verified Boot (causes soft-brick if u dont)
Extract vbmeta.img from the ROM zip file then flash it using this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2)Install TWRP
MIUI 12.5 TWRP:https://sourceforge.net/projects/be...rp-3.5.2_11-0-UNOFFICIAL-begonia.img/download
3)Download Magisk, rename .apk to .zip then flash it.
That's it. Now you have a rooted phone.
Click to expand...
Click to collapse
hihi, sorry for the late reply, I would've written out what I knew but this pretty much it, my main questions were which TWRP files to use and about MiUnlock, well now specifically mtkclient. Is it completely safe to use? I'd prefer not to wipe my files

Luxetrixx said:
hihi, sorry for the late reply, I would've written out what I knew but this pretty much it, my main questions were which TWRP files to use and about MiUnlock, well now specifically mtkclient. Is it completely safe to use? I'd prefer not to wipe my files
Click to expand...
Click to collapse
I've watched a few videos about it and some of them were formatted, some of them were not.
Try at your own risk.
When unlocked using mtkclient it may throw a dm-verity error or fastboot may refuse to work. Both of these are normal.

Question Locked bootloader while in download mode boot loop

Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks

Am i doomed?

cheen11 said:
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Click to expand...
Click to collapse
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country

BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.

cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
Shouldn’t be a big deal unless there’s something Carrier specific required by your phone. Just make sure you don’t lock your bootloader again while using custom binaries or you might soft brick your device again. To bypass the camera lock you can use a SafetyNet fix module for Magisk which will spoof the bootloader status to the camera HAL

cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
You can try also the NEE for Nordic Countries...

BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.

cheen11 said:
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
Click to expand...
Click to collapse
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.

BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
Ah, once choosing all the files it worked, thanks a bunch

BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.

cheen11 said:
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
Click to expand...
Click to collapse
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.

BlackMesa123 said:
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
Click to expand...
Click to collapse
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened

cheen11 said:
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
Click to expand...
Click to collapse
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.

BlackMesa123 said:
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
Click to expand...
Click to collapse
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO

cheen11 said:
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
Click to expand...
Click to collapse
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces

BlackMesa123 said:
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
Click to expand...
Click to collapse
Oh yeah good catch, i renamed the folder and didnt consider that it might not be updated it odin. It finally worked, thanks again for the help very much appreciated

Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.

cheen11 said:
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
Click to expand...
Click to collapse
As mentioned in the TWRP thread guide, you must format your data partition in TWRP in order to be able to boot back in the OS.

Question GSI with DSU sideloader?

Hello, I wanted to know if there is any way to install a gsi rom with the DSU sideloader app, the truth is that I have been trying it with quite a few and none have worked for me, I am not an expert in this, so I decided to stop before I regret it and better ask people with more experience.

DSU seems more like a testing feature I wouldnt recommend using it for general use but i think you need to disable Android Verified Boot by flashing vbmeta.img (from the stock rom) with some new arguments like so:
Code:
fastboot flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
Also make sure you unlocked the bootloader!
(You should have known this but I feel like I need to say this)
And if you are goind trough all this trouble
you might as well flash the GSI directly but hey you do you!
Keep in mind you should do your own research as I dont guarantee it will work but thats what i would do.