Related
Hi, I need your help....
Where can I find ROM with system.img, boot.img, userdata.img etc ?
for some reasons, mainly because i'm a dumb, i erased the entire partition of the OPO64.
Now, the only things I can do is to boot into :
- Fastboot Mode
- TWRP (that I installed just before doing silly things, like wiping everything out...)
I am wondering how to reinstall any OS on my phone, LineageOS or RR or anything else to get this phone working again. As there is no physical SDcard slot, I can't put a ROM on it to flash it from TWRP.
the only ROM I've found is CM13.x found here : https://www.androidsage.com/2016/08...anogen-os-13-1-2-znh2kas3p0-update-cm-13-1-2/
is it possible to get some other ROM with all the .img files ?
adb commands do not work.
The only thing I ca do is using fasboot commands.
As far as I understood, I could use there commands :
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
BUT : when I unzip all the ROMs I've found so far, there is always a boot.img file (and the fastboot flash boot boot.img works), but there is no other IMG file in the ZIP. No system.img, no userdata.img etc
Where can I download a ROM providing these files ?
is it mandatory to flask recovery.img ? I still want to use TWRP
Many many thanks
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot-76d803f730
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot-76d803f730 - FLASH it through BRT - Bacon Root Toolkit
flyjodel said:
Hi, I need your help....
Where can I find ROM with system.img, boot.img, userdata.img etc ?
for some reasons, mainly because i'm a dumb, i erased the entire partition of the OPO64.
Now, the only things I can do is to boot into :
- Fastboot Mode
- TWRP (that I installed just before doing silly things, like wiping everything out...)
I am wondering how to reinstall any OS on my phone, LineageOS or RR or anything else to get this phone working again. As there is no physical SDcard slot, I can't put a ROM on it to flash it from TWRP.
the only ROM I've found is CM13.x found here : https://www.androidsage.com/2016/08...anogen-os-13-1-2-znh2kas3p0-update-cm-13-1-2/
is it possible to get some other ROM with all the .img files ?
adb commands do not work.
The only thing I ca do is using fasboot commands.
As far as I understood, I could use there commands :
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
BUT : when I unzip all the ROMs I've found so far, there is always a boot.img file (and the fastboot flash boot boot.img works), but there is no other IMG file in the ZIP. No system.img, no userdata.img etc
Where can I download a ROM providing these files ?
is it mandatory to flask recovery.img ? I still want to use TWRP
Many many thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
It's not mandatory to flash recovery.img.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
It's not mandatory to flash recovery.img.
Click to expand...
Click to collapse
thank you !
flyjodel said:
thank you !
Click to expand...
Click to collapse
Instead hit the "thanks button "... Just sayin'
Hello usaully I flash my rom by fastboot and miflash software.I saw that inside the images folder there ace vbmeta.img and recovery.img.
I can replace recovery.img with twrp recovery.img file? It might work?
Hello guys my phone is stuck in a bootloop because I tried to install twrp from fastboot.
I unlocked bootloader and started Fastboot.
Then I connected my phone to my mac via USB.
Then I ran this commands:
./fastboot flash recovery recovery.img
./fastboot flash vbmeta vbmeta.img
(The mistake I think I made was that I flashed recovery before vbmeta).
Then I restarted my phone and I could not get into android or fastboot.
Please I need help.
This is the tutorial which I used.
Thanks in advance.
Apart from the wrong order of flash commands, it should be noted that
Code:
fastbbot flash vbmeta vbmeta.img
absolute is meaningless: stupidly overwriting an existing vbmeta.img MUST brick any Android device.
The correct Fastboot command should have been
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
what makes the necessary change in supplied vbmeta.img before it gets flashed.
My recommendation: Try to re-flash phone's Stock ROM.
jwoegerbauer said:
Apart from the wrong order of flash commands, it should be noted that
Code:
fastbbot flash vbmeta vbmeta.img
absolute is meaningless: stupidly overwriting an existing vbmeta.img MUST brick any Android device.
The correct Fastboot command should have been
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
what makes the necessary change in supplied vbmeta.img before it gets flashed.
My recommendation: Try to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
I will try to Flash the stock ROM using SP Flash Tool.
I won't try to install twrp anymore if this stock ROM flashing works.
I'll kill my dreams of rooting my phone and installing android 12.
(I hope it works because am not getting a new phone until next 3 years)
jwoegerbauer said:
Apart from the wrong order of flash commands, it should be noted that
Code:
fastbbot flash vbmeta vbmeta.img
absolute is meaningless: stupidly overwriting an existing vbmeta.img MUST brick any Android device.
The correct Fastboot command should have been
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
what makes the necessary change in supplied vbmeta.img before it gets flashed.
My recommendation: Try to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
Please do you know how to get the build number of my bricked phone?
mikkyboy said:
I will try to Flash the stock ROM using SP Flash Tool.
I won't try to install twrp anymore if this stock ROM flashing works.
I'll kill my dreams of rooting my phone and installing android 12.
(I hope it works because am not getting a new phone until next 3 years)
Click to expand...
Click to collapse
It's not hard to install TWRP to this device
GSI flashing guide for mediatek uplaoded- checkout
Rooting Realme Narzo 30 Pro:
New Method (Android 10 and above)
Go to this link
Also checkout how to flash stock rom if you face any problems such as bootloop:
link
Old Method (Android 11 and below)
Prerequisite :
Unlocked Bootloader
How to unlock bootloader: Phone will be formatted
Backup your data.
Install deeptesting.apk
Open the app and click start applying
Wait for application to be summited and processed
Minimize the app and head over to developer settings and turn on OEM Unlock and USB Debugging
Open deeptesting again and click on start in-depth test, the phone will reboot to bootloader
Connect phone to PC. Open platform-tools folder and type cmd in address bar
Type fastboot flashing unlock
Use volume and power button to select unlock the bootloader
Phone will format and reboot.
Realme Narzo 30 Pro (C.12) :
How to root ? Can cause bootloop or even brick your device
Download boot.img and vbmeta.img
Patch only the boot.img using this version of Magisk
Connect your phone to PC via USB Cable open cmd in platform-tools folder type adb command : adb reboot bootloader
Now your device is in fastboot mode
Firstly flash vbmeta.img file
Command for flashing vbmeta.img : fastboot --disable-verity --disable-verification flash vbmeta drag and drop vbmeta file
Now flash patched boot.image file
Command for flashing boot.img : fastboot flash boot drag and drop patched boot image file
Reboot your device with command : fastboot reboot
Your device is rooted now ╰(*°▽°*)╯
You can uninstall this version of magisk after rebooting and install the latest version
Other Files (C.12) :
Recovery.img
For rooting older versions :
Follow the same procedure, using the files, boot.img and vbmeta.img for specific version.
Extras:
Scatter file :
MT6853 Scatter.txt
Please Share Boot.img Of C.09
Files required for C.09 have been uploaded please check
I think the end command is : fastboot reboot
Ignacius57294 said:
I think the end command is : fastboot reboot
Click to expand...
Click to collapse
Yup
NinjaChunks said:
Yup
Click to expand...
Click to collapse
Ohh nice man you corrected it...
NinjaChunks said:
Files required for C.09 have been uploaded please check
Click to expand...
Click to collapse
Please share files boot.img of c11
please share boot.img of c.11
KIRANKEJITON said:
please share boot.img of c.11
Click to expand...
Click to collapse
It will be posted soon
NinjaChunks said:
Realme Narzo 30 pro (C.011) :
How to unlock bootloader Phone will be formatted :
Backup your data.
Install deeptesting.apk.
Open the app and click start applying.
Wait for application to be summited and processed.
Minimize the app and head over to developer settings and turn on OEM Unlock and USB Debugging.
Open deeptesting again and click on start in-depth test, the phone will reboot to bootloader.
Connect phone to PC. Open platform-tools folder and type cmd in address bar.
Type fastboot flashing unlock.
Use volume and power button to select unlock the bootloader.
Phone will format and reboot.
How to root Can cause bootloop or even hardbrick your device :
Download boot.img and vbmeta.img.( Credit : ashkir05)
Patch only the boot.img using this version of Magisk other versions of Magisk doesn't seem to be working.
Connect your phone to PC via USB Cable open cmd in platform-tools folder type adb command : adb reboot bootloader
Now your device is in fastboot mode
Firstly flash vbmeta.img file.
Command for flashing vbmeta.img : fastboot --disable-verity --disable-verification flash vbmeta drag and drop vbmeta file.
Now flash patched boot.image file.
Command for flashing boot.img : fastboot flash boot drag and drop patched boot image file.
Reboot command: fastboot reboot.
Your device is rooted now ╰(*°▽°*)╯
You can uninstall this version of magisk after rebooting and install the latest version
Other Files (C.011) :
MT6853 Scatter.txt
Recovery.img
For rooting older versions :
Follow the same procedure, just use the files provided for specific version.
Realme Narzo 30 pro (C.09) :
Download boot.img and vbmeta.img.
Other Files (C.09) :
MT6853 Scatter.txt
Recovery.img
Realme Narzo 30 pro (C.08) :
Download boot.img and vbmeta.img.
Other Files (C.08) :
MT6853 Scatter.txt
Recovery.img
Click to expand...
Click to collapse
after flashing boot.img , phone is not booting but it is getting looped into bootloader.
Please help
rizwanp880 said:
after flashing boot.img , phone is not booting but it is getting looped into bootloader.
Please help
Click to expand...
Click to collapse
Go to bootloader and flash stock boot.img
You would used other version of Magisk maybe
Bro how about realme 8 5g?
Please share img files for UI 3.0
It worked very well for c12 and I was also able to flash twrp/pwrp. But UI3.0 ota was not installing thus forced me to revert to stock.
TOPDOG3518 said:
It worked very well for c12 and I was also able to flash twrp/pwrp. But UI3.0 ota was not installing thus forced me to revert to stock
Click to expand...
Click to collapse
Stock boot.img is required for ota. Flash stock boot image then update.
To root again, get the boot.img for the software version your phone is running on and patch with magisk. Flash the patched boot.img and voila you have rooted.
Glad that you did. Any idea about custom rom on Narzo 30 Pro? as Realme excluded this device in her Android 14 update.
I am using Realme 3.0. Any good way to root and unlock bootloader without getting bricked?
Oops! We broke the matrix. Someone call Neo!
getting this error while try to download any file
I have realized that there isn't a guide to root the G91 PRO (not the max, for whatever reason that got rooted before the pro...) anyway, I figured out how to do it, and I'm probably not the first one. Since I haven't been able to find the stock rom on the internet, I strongly advise you backup your stock rom with mtkclient.
This is an A/B device, so we need to flash to both slots.
First, dump your stock rom with this tool: https://github.com/bkerler/mtkclient
This is mtkclient. It reverse engineers BROM or Preloader mode so that we can pull down the flash. Once you put your phone in BROM mode, use this command to back up the whole flash. (To put your phone in BROM mode, power off your phone and hold down volume up, down, and power and the same time while plugging in a USB-C cable)
python3 mtk rf flash.bin
Now that we've made a backup, we can start screwing around with the phone. If you ever need to restore your backup then all you need to do is:
python3 mtk w flash.bin
Inside of that flash bin you can find all the partitions inside of it. I use 7zip to look inside of the archive. Look for boot_a.img. After you find it, use magisk manager to root the stock boot.img.
If you don't want to look inside of the archive and would prefer to just dump the boot images, then just run these commands instead.
python3 mtk r boot_a boot_a.img
python3 mtk r boot_b boot_b.img
Now we can also use this mtkclient software to unlock the bootloader. We don't have to use mtkclient, we could use bootloader mode after enabling oem unlocking in developer options, but we can do this too.
We first have to erase metadata, userdata, and md_udc.
python3 mtk e metadata, userdata, md_udc
Now we can unlock the bootloader.
python3 mtk da seccfg unlock
After unlocking the bootloader, you can now flash partitions. Flash your patched boot.img in bootloader mode.
fastboot flash boot_a (patched boot.img)
fastboot flash boot_b (patched boot.img)
Inside of the mtkclient folder, you will find a file called vbmeta.img.empty. This is a patched vbmeta (its blank haha) so that we can disable verified boot. we need to flash it to both slots.
fastboot flash vbmeta_a (vbmeta.img.empty)
fastboot flash vbmeta_b (vbmeta.img.empty)
That's all!
Edit: I decided to attach my rooted and non rooted boot img for those who want to do it quickly. You can flash magiskboot_a.img to both slots, as they are the same. I caution you though, only flash my provided boot.img if your build number and custom build number matches the one in the screenshot I provided. Build number can be checked in Settings>About Device>Build Number and Custom Build Info. Make sure to also flash the empty vbmeta so you don't have any dm verity errors!
is build id same as build number?and can i flash that boot_a.img in bugjaeger app?
ziyad45 said:
View attachment 5620469is build id same as build number?and can i flash that boot_a.img in bugjaeger app?
Click to expand...
Click to collapse
This is not the same phone. You can't flash the boot.img. However, the specs are identical. You could probably follow the method I used to root this phone.
dtingley11222 said:
I have realized that there isn't a guide to root the G91 PRO (not the max, for whatever reason that got rooted before the pro...) anyway, I figured out how to do it, and I'm probably not the first one. Since I haven't been able to find the stock rom on the internet, I strongly advise you backup your stock rom with mtkclient.
This is an A/B device, so we need to flash to both slots.
First, dump your stock rom with this tool: https://github.com/bkerler/mtkclient
This is mtkclient. It reverse engineers BROM or Preloader mode so that we can pull down the flash. Once you put your phone in BROM mode, use this command to back up the whole flash. (To put your phone in BROM mode, power off your phone and hold down volume up, down, and power and the same time while plugging in a USB-C cable)
python3 mtk rf flash.bin
Now that we've made a backup, we can start screwing around with the phone. If you ever need to restore your backup then all you need to do is:
python3 mtk w flash.bin
Inside of that flash bin you can find all the partitions inside of it. I use 7zip to look inside of the archive. Look for boot_a.img. After you find it, use magisk manager to root the stock boot.img.
If you don't want to look inside of the archive and would prefer to just dump the boot images, then just run these commands instead.
python3 mtk r boot_a boot_a.img
python3 mtk r boot_b boot_b.img
Now we can also use this mtkclient software to unlock the bootloader. We don't have to use mtkclient, we could use bootloader mode after enabling oem unlocking in developer options, but we can do this too.
We first have to erase metadata, userdata, and md_udc.
python3 mtk e metadata, userdata, md_udc
Now we can unlock the bootloader.
python3 mtk da seccfg unlock
After unlocking the bootloader, you can now flash partitions. Flash your patched boot.img in bootloader mode.
fastboot flash boot_a (patched boot.img)
fastboot flash boot_b (patched boot.img)
Inside of the mtkclient folder, you will find a file called vbmeta.img.empty. This is a patched vbmeta (its blank haha) so that we can disable verified boot. we need to flash it to both slots.
fastboot flash vbmeta_a (vbmeta.img.empty)
fastboot flash vbmeta_b (vbmeta.img.empty)
That's all!
Edit: I decided to attach my rooted and non rooted boot img for those who want to do it quickly. I caution you though, only flash my provided boot.img if your build number and custom build number matches the one in the screenshot I provided. Build number can be checked in Settings>About Device>Build Number and Custom Build Info. Make sure to also flash the empty vbmeta so you don't have any dm verity errors!
Click to expand...
Click to collapse
My g91 pro doesn't seem to work with mtk client it but I have the same build as you.
To root my phone I need to have boot image a and b? I noticed just image a is attached and I can't find a rom download for the g91 pro anywhere.
Did you use img a for both?
Any help would be great.
Thanks
Longdelayecho said:
My g91 pro doesn't seem to work with mtk client it but I have the same build as you.
To root my phone I need to have boot image a and b? I noticed just image a is attached and I can't find a rom download for the g91 pro anywhere.
Did you use img a for both?
Any help would be great.
Thanks
Click to expand...
Click to collapse
You might not be entering brom correctly. The rom is not available on the internet. You only need boot_a because the boot imgs are the same for both slots. You can flash it to both a and b with no issue.
Hey do you think this would work on the G61S?