Related
Hello devs,
I upgraded my Realme X to android 10 using OTA.
Although there are no serious bugs, the UI has minor glitches now and then. But the camera has lost its quality significantly. It is taking comparatively bad photos now when compared to Android 9.
Can You kindly write a guide on how to downgrade to Android 9? It will be really appreciated.
Thank You in advance.
@SagarMakhar @gritik95 @indroider
Download Stock rom released on 19th Feb and flash it manually if your bootloader is unlocked or if you have custom recovery
rupeshmaurya35 said:
Download Stock rom released on 19th Feb and flash it manually if your bootloader is unlocked or if you have custom recovery
Click to expand...
Click to collapse
Bootloader is locked. Can't I flash older versions?
I have the same query. Any help would be highly appreciated.
Bootloader is locked. I just purchased the phone and upgraded to Realme UI. Now I want to downgrade to colorOS so I can either use it or flash the phone to other ROM(s) which is completely impossible as of now in Realme UI.
U can unlock bootloader using In depth test app and adb but u can't use TWRP because TWRP is not supported in android 10.
What about fastboot? Can we flash Android 9 using fastboot? Have you successfully downgraded?
ShattrdChain said:
Hello devs,
I upgraded my Realme X to android 10 using OTA.
Although there are no serious bugs, the UI has minor glitches now and then. But the camera has lost its quality significantly. It is taking comparatively bad photos now when compared to Android 9.
Can You kindly write a guide on how to downgrade to Android 9? It will be really appreciated.
Thank You in advance.
@SagarMakhar @gritik95 @indroider
Click to expand...
Click to collapse
Hi
I've bricked my realme x and that lead me to start searching ow to unbrick it, and with that i can tell you there's a way to make a downgrade of the android version.
The first thing you need to have is the .ofp file of the software version you want (if you have the india/global version you will not have any problem finding it, but if you have the chinese version you probably could not find it *i've been searching a lot for this file, if you find it, please let me know*)
once you have the ofp file you need the flashing tool of oppo, known as msmdownload tool, the issue with this is the tool will ask you for username and password, because its for oppo workers, and a lot of patched versions don't reconize the file.
If you made this far its pretty simple, select the ofp file, connect the device pressing volumen + and volumen -, and push in the icon of flash.
you can do it in another way, unlocking the bootloader (theres a tutorial in this forum), and then flashing a recovery (you migth flash a custom rom first via adb/fastboot) a zip file with the twrp, and then using the flashable zip of color OS
I hope this help you, but if you're not very mastered in this i reccomend u let realme work of improving the rom or using a gcam
Irvinukis said:
Hi
I've bricked my realme x and that lead me to start searching ow to unbrick it, and with that i can tell you there's a way to make a downgrade of the android version.
The first thing you need to have is the .ofp file of the software version you want (if you have the india/global version you will not have any problem finding it, but if you have the chinese version you probably could not find it *i've been searching a lot for this file, if you find it, please let me know*)
once you have the ofp file you need the flashing tool of oppo, known as msmdownload tool, the issue with this is the tool will ask you for username and password, because its for oppo workers, and a lot of patched versions don't reconize the file.
If you made this far its pretty simple, select the ofp file, connect the device pressing volumen + and volumen -, and push in the icon of flash.
you can do it in another way, unlocking the bootloader (theres a tutorial in this forum), and then flashing a recovery (you migth flash a custom rom first via adb/fastboot) a zip file with the twrp, and then using the flashable zip of color OS
I hope this help you, but if you're not very mastered in this i reccomend u let realme work of improving the rom or using a gcam
Click to expand...
Click to collapse
But how can u flash custom recovery in android 10. As i know TWRP or any other custom recovery are not fully developed for android 10 .
rupeshmaurya35 said:
But how can u flash custom recovery in android 10. As i know TWRP or any other custom recovery are not fully developed for android 10 .
Click to expand...
Click to collapse
you have to flash the recovery after flashing another rom
thats why i suggest you flashing a custom rom via ADB and then flashing the color os rom
Irvinukis said:
you have to flash the recovery after flashing another rom
thats why i suggest you flashing a custom rom via ADB and then flashing the color os rom
Click to expand...
Click to collapse
It is very simple if you say "I DON'T KNOW"
I'm curently running the latest stock rom and I wanted to downgrade to firmware 10.0.13.0 so I could try some custom roms that don't support the latest stock Q.
How do I do that? I've seen a lot of threads talking about dowgrading from Pie to Oreo but still haven't seen anything on the process of going from Q to Pie.
Denkki said:
I'm curently running the latest stock rom and I wanted to downgrade to firmware 10.0.13.0 so I could try some custom roms that don't support the latest stock Q.
How do I do that? I've seen a lot of threads talking about dowgrading from Pie to Oreo but still haven't seen anything on the process of going from Q to Pie.
Click to expand...
Click to collapse
Downgrading to pie is d same as loading the os using miflash. U jus go to fastboot and run d process or enter EDL mode & run d process.
Try this link:
https://forum.xda-developers.com/sho...php?p=79365091
Lets know how it goes
What I've done:
Install adb drivers
unlock bootloader(fastboot oem unlock) in platform tools
I used this process:https://www.youtube.com/watch?v=1pjs5wakBCg&t=
*use mi 2 lite files but same process*
download mi flash tool( install in drive C
go fastboot mode
download and extract .tgz fastboot images you want from here:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
then flash using mi flash tool.
harbinx said:
What I've done:
Install adb drivers
unlock bootloader(fastboot oem unlock) in platform tools
I used this process:https://www.youtube.com/watch?v=1pjs5wakBCg&t=
*use mi 2 lite files but same process*
download mi flash tool( install in drive C
go fastboot mode
download and extract .tgz fastboot images you want from here:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
then flash using mi flash tool.
Click to expand...
Click to collapse
Thank you! I didn't know it was the exact same process.
Just donwgraded and I'm now using a custom rom, everything seems to be working well!
I am not responsible for any brick.
I tested this guide myself and decided to share it.
Make a backup before this guide because you will lose your data!
The unlock method has been updated and now you can unlock the bootloader more easily without the risk of bricking after an OTA and without changing the bootloader.
Now you can safely unlock the bootloader using mtkclient.
Link: https://github.com/bkerler/mtkclient
TWRP can be installed via mtkclient or manually from rooted Android.
TWRP Download link: https://github.com/XRedCubeX/twrp_meizu_m5c/releases
IF you unlocked the bootloader with the old method you can follow these steps:
1) Download the attached package.
2) Download OTA zip from flyme, link: http://www.flymeos.com/firmwarelist?modelId=70&type=1
3) Download the latest version of SP Flash Tool.
4) Download MTKClient and follow the instructions to install it.
5) Power off the phone and keep unplugged it from PC.
6) Open SP Flash Tool, select the downloaded package and select all partitions, then press the download button, don't plug phone for now.
7) Boot to recovery with vol +, plug the phone on PC, depending on recovery, TWRP or stock, use adb sideload or put update.zip in internal memory and install the zip.
8) Let the phone reboot or reboot it manually.
9) Now start the flash from SP Flash tool automatically, let it finish.
10) After the flash, unplug the phone and reboot into recovery.
11) Paste the update.zip in the phone and flash it.
12) After reboot, let your phone reboot into android and power off.
13) You can follow the guide to unlock bootloader with mtkclient.
FAQ:
A) But will I lose the data with this guide?
Yes.
Make sure to back up your data in any case!
B) But this guide is a bit different than usual, where is "fastboot oem unlock"? Or "fastboot flashing unlock"?
Meizu has not implemented an unlock command and in this case to unlock the bootloader we have to use a tool that makes us change the unlock status.
C) Are there Custom ROMs?
There is only one custom ROM for this device, the Lineage OS 14 but I advise against using it because it has a bit of a bug but I haven't had more time to work on it yet.
D) But wasn't the guide different?
It has been updated with a better method with more advantages.
E) My device is in Hard Brick! How can I solve?
There are various types of Hard Brick and it depends from situation to situation.
F) I have installed Lineage OS 14 but I am not satisfied, I want to go back to Flyme!
Flash update.zip from official website.
G) Can I relock the bootloader?
From MTKClient readme:
for relocking use:
python mtk da seccfg lock
Click to expand...
Click to collapse
H) TWRP? I am interested in Device Tree, where is the link?
Here: https://github.com/XRedCubeX/twrp_meizu_m5c
I) I have a Meizu A5 (Chinese M5c) will it work on it?
I can't assure you anything but it could work, the only way to be sure is to test on a Meizu A5.
J) Can I flash twrp from fastboot?
Fastboot refuses to flash partitions, strangely, I don't know if downgrade or anything changes the situation but for now I was able to flash it with mtkclient.
I can remove the FlameOs from the Meizu M5c and install a custom rom. So far I haven't found any rom for this device?
Mortaux said:
I can remove the FlameOs from the Meizu M5c and install a custom rom. So far I haven't found any rom for this device?
Click to expand...
Click to collapse
Im working on a Lineage OS 14 for this device.
I tried the procedure and it failed. Apparently it just formatted it but couldn't finish the process, returned an error. Then I tried to reinstall the stock ROM and it generated the error S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004). Now my phone is off and I can't turn it on anymore.
I tried this method but it didn't work:
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES FIX FOR SP FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) AND (2004) Follow the following steps: 1. Get SP flash tools (Latest version) 2. Download your...
forum.xda-developers.com
I know it's my responsibility, but I don't know what else to do. Could someone please help me?
thiagosousa777 said:
I tried the procedure and it failed. Apparently it just formatted it but couldn't finish the process, returned an error. Then I tried to reinstall the stock ROM and it generated the error S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004). Now my phone is off and I can't turn it on anymore.
I tried this method but it didn't work:
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES FIX FOR SP FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) AND (2004) Follow the following steps: 1. Get SP flash tools (Latest version) 2. Download your...
forum.xda-developers.com
I know it's my responsibility, but I don't know what else to do. Could someone please help me?
Click to expand...
Click to collapse
You unplugged the device while it was formatting, consequently it no longer has the bootloader, that error means that the device needs an authorization file that unfortunately only meizu has, shortly if I can try to release a tool to unbrick it in cases similar to these
XRed_CubeX said:
You unplugged the device while it was formatting, consequently it no longer has the bootloader, that error means that the device needs an authorization file that unfortunately only meizu has, shortly if I can try to release a tool to unbrick it in cases similar to these
Click to expand...
Click to collapse
It's a shame .. I hope you can really release this tool, so I can revive my phone. Thank you.
You can make a video on youtube showing the procedure on the Meizu M5c. Installing Twrp and LineageOs 14? Just to make sure it works
Mortaux said:
You can make a video on youtube showing the procedure on the Meizu M5c. Installing Twrp and LineageOs 14? Just to make sure it works
Click to expand...
Click to collapse
For now I can't make the video because I can't release the Lineage because I'm fixing some bugs and I want to do some checks before releasing it publicly
thiagosousa777 said:
It's a shame .. I hope you can really release this tool, so I can revive my phone. Thank you.
Click to expand...
Click to collapse
Ok i found a working guide, tried on my M5c and it works:
Search on YouTube: flash mtk without da ,
You will find a video called, just exactly as I write here: "How to flash MTK secure boot devices without a custom DA" and follow the video tutorial for unbrick your device.
P.S:Obviously when the guide ends you flash the ROM from SP flash tool as you normally would
XRed_CubeX said:
Ok i found a working guide, tried on my M5c and it works:
Search on YouTube: flash mtk without da ,
You will find a video called, just exactly as I write here: "How to flash MTK secure boot devices without a custom DA" and follow the video tutorial for unbrick your device.
P.S:Obviously when the guide ends you flash the ROM from SP flash tool as you normally would
Click to expand...
Click to collapse
I'll try that, thanks a lot!
thiagosousa777 said:
I'll try that, thanks a lot!
Click to expand...
Click to collapse
Did you finally manage to fix the device?
Were you able to get on with the guide?
XRed_CubeX said:
Did you finally manage to fix the device?
Were you able to get on with the guide?
Click to expand...
Click to collapse
I haven't had time to do it yet. When I have time I will follow the tutorial and tell you if it worked.
thiagosousa777 said:
I haven't had time to do it yet. When I have time I will follow the tutorial and tell you if it worked.
Click to expand...
Click to collapse
Ok good luck
XRed_CubeX said:
Ok good luck
Click to expand...
Click to collapse
XRed_CubeX, I followed the tutorial from start to finish. I used the SP Flash Tool to install the M5c stock ROM, the ROM was flashed 100%, but after disconnecting the USB cable the phone did not turn on.
thiagosousa777 said:
XRed_CubeX, I followed the tutorial from start to finish. I used the SP Flash Tool to install the M5c stock ROM, the ROM was flashed 100%, but after disconnecting the USB cable the phone did not turn on.
Click to expand...
Click to collapse
Have you flashed the Stock ROM or the Engineering ROM? I remind you that even if you have flashed the eng rom only once previously, you can no longer return to the flyme bootloader so use the normal stock ROM but you will have to flash the Engineering rom
XRed_CubeX said:
Have you flashed the Stock ROM or the Engineering ROM? I remind you that even if you have flashed the eng rom only once previously, you can no longer return to the flyme bootloader so use the normal stock ROM but you will have to flash the Engineering rom
Click to expand...
Click to collapse
Well, I flashed the stock ROM a second time, using the Firmware Upgrade option, and it worked. My phone turned on and I'm in the initial setup screen.
By the way, this Engineering ROM is the ROM you shared above? Do you think it is stable enough to be used? Maybe another day I'll install it, with care to not do anything wrong again
thiagosousa777 said:
Well, I flashed the stock ROM a second time, using the Firmware Upgrade option, and it worked. My phone turned on and I'm in the initial setup screen.
By the way, this Engineering ROM is the ROM you shared above? Do you think it is stable enough to be used? Maybe another day I'll install it, with care to not do anything wrong again
Click to expand...
Click to collapse
Yes, the ROM in this thread is ROM engineering, about the stability I can't tell you why I haven't tested it, the main purpose FOR ME was to get the bootloader unlock with this ROM, if you want to switch to ROM engineering you CAN install the flyme after installed the Engineering ROM but you must always modify the OTA zip so that some partitions do not flash but if you are interested I will talk about it in more detail and maybe I will give you a hand to flash flyme safely on bootloader engineering
XRed_CubeX said:
Yes, the ROM in this thread is ROM engineering, about the stability I can't tell you why I haven't tested it, the main purpose FOR ME was to get the bootloader unlock with this ROM, if you want to switch to ROM engineering you CAN install the flyme after installed the Engineering ROM but you must always modify the OTA zip so that some partitions do not flash but if you are interested I will talk about it in more detail and maybe I will give you a hand to flash flyme safely on bootloader engineering
Click to expand...
Click to collapse
Actually, the ROM I installed with SP Flash Tools was not the update.zip from the official Flyme OS website. I downloaded the stock rom from needrom.
I have done this several times before.
But now, strangely I can no longer update to the latest version. The version I'm running is Flyme 6.0.2.0G. I tried to download the update.zip file and install it manually by clicking on it, and it appeared "corrupted file". I also tried to use the Update application and "network error" appeared. But everything else is working perfectly.
XRed_CubeX said:
if you are interested I will talk about it in more detail and maybe I will give you a hand to flash flyme safely on bootloader engineering
Click to expand...
Click to collapse
I would like to know how to install the latest version of Flyme OS via TWRP. If you can tell how to do this..
XRed_CubeX said:
can't release the Lineage because I'm fixing some bugs and I want to do some checks before releasing it publicly
Click to expand...
Click to collapse
Are you working on a custom Lineage OS ROM for this device? I'm interested, when you can publish it.. Do you have a prediction of when you will be able to release that ROM?
thiagosousa777 said:
I would like to know how to install the latest version of Flyme OS via TWRP. If you can tell how to do this..
Are you working on a custom Lineage OS ROM for this device? I'm interested, when you can publish it.. Do you have a prediction of when you will be able to release that ROM?
Click to expand...
Click to collapse
Ok, I'll explain in detail how it works: In the guide you will have read that you cannot return to the flyme using the stock rom or an unmodified OTA. This is a tip because once you flash the Engineering ROM, the engineering bootloader (which is essential for unlocking) will also be flashed, but the problem is that if you flash the stock bootloader (the flyme one, the one you surely have when you get the phone), the device for a reason unknown to me, probably the Engineering ROM modifies something in the device (?) and then goes into brick if you try to return to the flyme bootloader. To flash an OTA flyme on TWRP, you must first have some precautions: you must take the OTA on your computer (or a file explorer capable of editing zip files) and remove the following files: lk.bin preloader.bin (it will have a name longer but you still have to remove that) and tz.bin / trustzone.bin. Done like this, now the OTA becomes safe to install, you install it from TWRP, at the end of the flash it will give you an error but it is because it does not find the files we have removed but we can safely ignore it because it will have successfully installed the flyme on the device.
Regarding lineage: I'm still working on it a bit and gradually I'm discovering bugs. I already warn you that the camera will not work in the Lineage, I have tried in every way to try to make it work but it does not want to go, I have asked for help everywhere but no one has been able to answer so I do not know what to do, for the rest I want to keep a little longer the ROM under test to fix the remaining bugs
Can we root Oppo F17 Pro which comes with color OS 7 bootloader locked and fastboot disabled. SP Flash tool is not reading the scatter file that was extracted from stock rom (.ozip file), so I could flash the patched boot.img.
Anyone any luck rooting Oppo F17 Pro.
You can use TWRP and super user.
Copy SU on Oppo mobile.
Start mobile in recovery mode.
Use TWRP to install SU on mobile.
Restart mobile.
I can go to recovery mode but Fastboot is disabled by Oppo and boot loader as well locked. Is there any other way I can flash TWRP on the device without Fastboot? I am very new to this stuff trying to learn more
1. Is it possible to modify the original "StockRom" file (ozip) by replacing the patch_boot.img file which was able to generate using Magisk. It says it keep the signature unchanged so hoping there won't be signature issue.
2. I was able to extract the Stock Rom (ozip file) using python script but the scatter file that I found in that is not working in SP Flash Tool so not able to flash the boot.img. Is there a way we can find the working scatter file? I tried using MTK Droid tool to generate scatter but it doesn’t recognize the device.
3. Other option that I was thinking was after replacing the original boot.img with patched boot.img in extracted zip file is there a way we can convert it back to ozip file and the using the stock recovery we can flash the rom.
On the latest fw enable developer options and there you will see "unlock bootloader" option.
HI,
did you found "deep test apk" belonging to your phone in official coloros forum?
if not, this phone may not support bootloader unlock.
p.s. mine is OPPO R17 Pro, and it has "deep test apk"
my oppo f17 is fully locked and password protected. i dont remember the password.
cant do the hard reset it also requires password. is there any way i can unlock or flash my phone???
caihuach said:
HI,
did you found "deep test apk" belonging to your phone in official coloros forum?
if not, this phone may not support bootloader unlock.
p.s. mine is OPPO R17 Pro, and it has "deep test apk"
Click to expand...
Click to collapse
Im download deep test apk but i have a problem "app not installed" how i solve it in my oppo f17pro
well you may ask supports in your forum, cuz my phone is explicitly supported and meets no problem ...
caihuach said:
well you may ask supports in your forum, cuz my phone is explicitly supported and meets no problem ...
Click to expand...
Click to collapse
I want to root my phone but fastboot mod is disabled how i root my phone oppo f17pro
Is it possible to install lineage os in my Oppo F17 Pro ? Tell full steps specific to this phone model please
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!