Related
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Nobody got the same problem? Maybe phone is damaged?
messiahxavier said:
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Click to expand...
Click to collapse
messiahxavier said:
Hi Guys,
since few days I try to install a custom rom on my eu xt1635-02.
I opended the bootloader offical way and installed the latest twrp. 3.2.0.1,all went fine,but factory reset deletes not all data and when I try to install a custom rom ( tried several) I always got an error 7 from twrp? So not possible to install something.
I come from latest offical Nougat 7.1.1 rom with february patch.
There are so many theads I was reading,but I think I need help. Also I can't find a definetly method how to root without risk of brik.
Sorry für my bad english, my german is better.
Click to expand...
Click to collapse
1. It's always hard to help without logs. Error codes are too unspecific
2. Check the mount settings, under the partition list there is an option for mounting /system as read only. It has to be disabled for installing custom ROMs.
Found something intresting,when I flash twrp without any problem and boot to system...then again tomorrow recovery via hardbuttons over bootloader there comes stock recovery????what ist that? Not able to go to twrp,only after new flash in fastboot.
Then you didn't flash it but just boot it
Hi bro.
I did face same problem here.
Follow the below steps:
Take download a nougat firmware, currently the "NPNS26.118-22-1"
Enter fastboot mode and type these comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
You can do on any rom. For example: You are on AEx nougat, enter fastboot mode and type the comands above.
I hope that helped you.
tiago1966 said:
Hi bro.
I did face same problem here.
Follow the below steps:
Take download a nougat firmware, currently the "NPNS26.118-22-1"
Enter fastboot mode and type these comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
You can do on any rom. For example: You are on AEx nougat, enter fastboot mode and type the comands above.
I hope that helped you.
Click to expand...
Click to collapse
Current firmware is 118-22-2-17! Older builds could lead to downgrade issues!
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.
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!
This is a noob question only.
SUPPOSE
Supposing I have a treble enabled Snapdragon phone(Xiaomi China rom), and it one day updates and removes Google with a device-bricking rollback protection, so it is a paperweight, but I can still access Dev options, and unlock bootloader.
So what can I do to flash a custom rom? I had heard to disable vertified boot 2.0 by flashing vbmeta with the disable Verity command. Which vbmeta.img should I flash with disable Verity, that from stock ROM(they say I need an empty vbmeta so I doubt it works), or those floating around on the web(maybe not signed so I also doubt it works)? If it fails to disable vertified boot I cannot flash any custom rom so I probably have to salvage the screen and casing , sell it on ebay, and shred my motherboard.
Again this is only a supposed worst case scenario BUT my current phone is a Xiaomi with China phone so once it updates itself for no reason, I will be in this scenario. This is for reference if that happens. Thanks.
Well verified boot can be disabled by flashing a patched vbmeta.img
Thats to my knowledge rn
Pretty sure if you provide the make and model of the said xiaomi phone I could find something on here related to disabling verified secure boot.
Kenora_I said:
Well verified boot can be disabled by flashing a patched vbmeta.img
Thats to my knowledge rn
Pretty sure if you provide the make and model of the said xiaomi phone I could find something on here related to disabling verified secure boot.
Click to expand...
Click to collapse
Magisk patch you mean?
My phone (redmi k30)is not yet bricked, but I have to provide some background information.
From my mi security app, if I click on optimization, the auto update options will be enabled, and my device will be remotely rendered useless.
By the way can I safely disable mi security app Via adb?(I can't disable miui update app so...)
Kenora_I said:
Well verified boot can be disabled by flashing a patched vbmeta.img
Thats to my knowledge rn
Pretty sure if you provide the make and model of the said xiaomi phone I could find something on here related to disabling verified secure boot.
Click to expand...
Click to collapse
Fast boot does this
fastboot —disable-verity flash vbmeta path-to-vbmeta-from-stock-rom
So to sum up:
1. Find vbmeta.img from stock ROM.
2. If I can't find it maybe flash Google official vbmeta: https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
3. Flash with fastboot --disable-verity flash vbmeta vbmeta.img command.
LR7875 said:
So to sum up:
1. Find vbmeta.img from stock ROM.
2. If I can't find it maybe flash Google official vbmeta: https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
3. Flash with fastboot --disable-verity flash vbmeta vbmeta.img command.
Click to expand...
Click to collapse
yep
also if you want to be a bit extra add the --disable-verification flag
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.