Related
When there's a new image next month I want to update to can I just use fastboot and flash everything except recovery then reboot and keep.twrp and ha e the newest image without losing data ?
Fastboot flash
Bootloader
Modem
System
Syatem_other
Vendor
Skipping the others then reboot and still have TWRP ? Right now my goal is just to use a stock image, ElementalX kernel and root with TWRP. Just passing on the custom ROMs right now
There's a lot of . img files.
This is more complex than my Nexus 5x which just had a few . img
I don't understand which is which
mikeprius said:
There's a lot of . img files.
This is more complex than my Nexus 5x which just had a few . img
I don't understand which is which
Click to expand...
Click to collapse
You can't do what you want to do because recovery is located in the boot.img file on the Pixel. There is no dedicated recovery partition like on other phones. The only way to do it would be to flash everything but the boot.img file. That may work but if you did do that, you'd miss out on any security updates or whatever other updates there may be to the kernel. I'd recommend just flashing it all. It doesn't take very long to flash TWRP again. A minor inconvenience if you ask me.
I think THIS can help. Follow method 2 - manual.
But skip recovery.img and cache.img (also because there aren't those files) and the userdata.img
robocuff said:
You can't do what you want to do because recovery is located in the boot.img file on the Pixel. There is no dedicated recovery partition like on other phones. The only way to do it would be to flash everything but the boot.img file. That may work but if you did do that, you'd miss out on any security updates or whatever other updates there may be to the kernel. I'd recommend just flashing it all. It doesn't take very long to flash TWRP again. A minor inconvenience if you ask me.
Click to expand...
Click to collapse
Ok thanks for the info. I've been flashing for awhile, but the set up here is very different than prior phones.
So pretty much just run the flash-all.bat, TWRP.img, TRWP.zip, the SuperSU ?
Can I modify the flash-all to prevent wiping, or is it just best to re-do everything fresh ?
TENN3R said:
I think THIS can help. Follow method 2 - manual.
But skip recovery.img and cache.img (also because there aren't those files) and the userdata.img
Click to expand...
Click to collapse
Have you tried this ? I read this article earlier and that's what's confusing:
So here's the process:
bootloader-xxx-xxx.img
radio-xx-xx-xx.img
boot.img
system.img
system_other.img
vendor.img
modem.img
but then later in the article it says:
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot flash userdata userdata.img
it appears there are many other files included beyond this list.
mikeprius said:
Ok thanks for the info. I've been flashing for awhile, but the set up here is very different than prior phones.
So pretty much just run the flash-all.bat, TWRP.img, TRWP.zip, the SuperSU ?
Can I modify the flash-all to prevent wiping, or is it just best to re-do everything fresh ?
Click to expand...
Click to collapse
Modify it, remove the -w
Been doing it that way back to my Nexus 6. No issues.
TonikJDK said:
Modify it, remove the -w
Been doing it that way back to my Nexus 6. No issues.
Click to expand...
Click to collapse
Can I do this dirty ? Basically just flash the stock images over the old, remove -w, then reboot, everything updated ? I don't mind booting the TWRP image and re-flashing superSU, just having to restore from scratch is a pain in the ass
mikeprius said:
Can I do this dirty ? Basically just flash the stock images over the old, remove -w, then reboot, everything updated ? I don't mind booting the TWRP image and re-flashing superSU, just having to restore from scratch is a pain in the ass
Click to expand...
Click to collapse
There's no need to wipe anything. Just make sure to remove the -w from the flashall.bat (dont forget to save it after doing so). If you do it this way, you'll end up with an updated phone with all your data in tact. Same as if you took an OTA.
robocuff said:
There's no need to wipe anything. Just make sure to remove the -w from the flashall.bat (dont forget to save it after doing so). If you do it this way, you'll end up with an updated phone with all your data in tact. Same as if you took an OTA.
Click to expand...
Click to collapse
Cool cool thanks. Will try this next month's update.
mikeprius said:
Can I do this dirty ? Basically just flash the stock images over the old, remove -w, then reboot, everything updated ? I don't mind booting the TWRP image and re-flashing superSU, just having to restore from scratch is a pain in the ass
Click to expand...
Click to collapse
Just to reinforce the post above, I always flash dirty. No issues.
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'
so as the title suggests, my oneplus 7 pro is now stuck at fastboot and my only hope is on the img files from the unpacked payload.bin. but now after I extract it, i heard some of the img files are used to clear the user, data etc, can someone tell me which one is which?
The guide I followed:
https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
the first link seem to be outdated since most of the img files it talked about don't exist but although the third link isn't, it told me how to flash each file, but my problem is that I don't want to lose my data, can someone tell me which img file is used to erase data? thanks a lot
shuaiouke said:
so as the title suggests, my oneplus 7 pro is now stuck at fastboot and my only hope is on the img files from the unpacked payload.bin. but now after I extract it, i heard some of the img files are used to clear the user, data etc, can someone tell me which one is which?
The guide I followed:
https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
the first link seem to be outdated since most of the img files it talked about don't exist but although the third link isn't, it told me how to flash each file, but my problem is that I don't want to lose my data, can someone tell me which img file is used to erase data? thanks a lot
Click to expand...
Click to collapse
userdata.img will override your internal storage with zero bytes.
matze19999 said:
userdata.img will override your internal storage with zero bytes.
Click to expand...
Click to collapse
is that the only file? thanks
Edit:There don't seem to be a file called userdata.img it's a ONEPLUS 7 PRO rom
Right click and edit flash all.bat and remove the -w and save then u can run flash all.bat using the fastboot Rom, ur 3rd link
thank you and it lets me get into recovery in a boot loop but recovery only, I can't flash TWRP, what should I do next?
Bradl79 said:
Right click and edit flash all.bat and remove the -w and save then u can run flash all.bat using the fastboot Rom, ur 3rd link
Click to expand...
Click to collapse
thank you and it lets me get into recovery in a boot loop but recovery only, I can't flash TWRP, what should I do next?
shuaiouke said:
thank you and it lets me get into recovery in a boot loop but recovery only, I can't flash TWRP, what should I do next?
Click to expand...
Click to collapse
is your bootloader locked?
shuaiouke said:
thank you and it lets me get into recovery in a boot loop but recovery only, I can't flash TWRP, what should I do next?
Click to expand...
Click to collapse
We're you coming from a custom Rom, or stock. You might have to format data.
Bradl79 said:
is your bootloader locked?
Click to expand...
Click to collapse
it's kinda obvious, flash-all is flashing after all if ur bootloader is locked, how do u flash?
Note: This is for soft bricks only.
soft brick = can access fastboot or recovery
hard brick = no boot, black screen boot. etc.............
I found myself on OB4, tried to sideload another build and got stuck. Tried to boot into TWRP, no bueno, now what? I didn't want to use MSM tools and go though that whole process again. I've saved many of my devices with Linux, by just flashing the img files through fastboot commands. So if your comfortable with the command line this is easier then using the flash tools that relock your bootloader. This also works with Widows, so I remembered the files the fastboot flasher flashed, and just flashed them manually, you just need flash to the correct partition. So, if it's a boot img, then flash boot, and system flash system, and so on. List of files that I flashed.
First you'll need payload dumper, to extract files from payload.bin file inside whatever OTA, you want to flash. It will extract to a folder called payload_output, from there you can click and drag to command line.
https://androidfilehost.com/?fid=818070582850510260
I also provided a copy of my script, you'll need to edit to your files path. And save as .bat, .cab, or .exe...........
Commands I run before flash
fastboot format system
fastboot format userdata
1. boot.img
2. dtbo
3. modem
4. odm
5. qupfw
6. storsec
7. system
8. vbmeta
9. vendor
10. fastboot reboot
If device boots to recovery which should be stock, just wipe everything and you should boot into system without a problem.
can anyone tell why some youtuber using "boot" and "vendor boot" to flash recovery and then sideload the custom rom?
the official site of pixel experience has recovery.img and rom.zip file, so cant i just flash the recovery image? (why i need to flash boot and vendor boot?)
and i don't know about other custom roms. do each rom have different boot and vendor boot for this device?
Because on some new devices the recovery is stored in boot.img so u need first to flash boot.img then voala u have recovery then through pc sideload the rom, i sont know if i explain correctly but do what they say or use these steps
Step 1 :---Download two files :--
1). boot.img
Click to expand...
Click to collapse
2). vendor_boot.img
Click to expand...
Click to collapse
After Downloading :--
Step 2 :---Flash following commands in that terminal.
1). fastboot flash boot (drag and drop boot.img file )
Click to expand...
Click to collapse
2). flastboot flash vendor_boot (drag and drop vendor_boot.img file )
Click to expand...
Click to collapse
I've created a patched boot.img with Magisk and flashed that with Fastboot but after rebooting Magisk still shows that it's not rooted. So I tried flashing the boot.img in Recovery but again after rebooting it's not rooted.
What am I doing wrong?
doveman said:
I've created a patched boot.img with Magisk and flashed that with Fastboot but after rebooting Magisk still shows that it's not rooted. So I tried flashing the boot.img in Recovery but again after rebooting it's not rooted.
What am I doing wrong?
Click to expand...
Click to collapse
The boot.img to patch must be the same as the rom you are using.
Try renaming magisk.apk and magisk.zip and flashing it with Twrp. (You may need to flash vbmeta and use "fastboot flash --disable-verity --disable-verification vbmeta images\vbmeta.img").
NOSS8 said:
The boot.img to patch must be the same as the rom you are using.
Try renaming magisk.apk and magisk.zip and flashing it with Twrp. (You may need to flash vbmeta and use "fastboot flash --disable-verity --disable-verification vbmeta images\vbmeta.img").
Click to expand...
Click to collapse
Yeah, I downloaded the correct ROM (miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip) and extracted the boot.img from that.
Renaming magisk.apk to magisk.zip and flashing it just installs the app doesn't it, it doesn't root the phone as far as I'm aware.
I followed the instructions here, which say that you should only tick the "Patch vbmeta in boot image” option when patching the boot.img in Magisk if the device does NOT have a separate vbmeta partition. The Poco X3 does have a separate vbmeta partition,, so I didn't tick that option.
Installation
The Magic Mask for Android
topjohnwu.github.io
I've tried the "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img" command with four different versions of fastboot that I've got, dating from 2016 to 2020, and they all reject the "--disable" switches as an "unknown option".
I tried it without those options, so I flashed the patched boot.img and then did "fastboot flash vbmeta vbmeta.img" but after rebooting Magisk still shows that root is not installed.
https://xiaomifirmwareupdater.com/miui/surya/stable/V12.5.4.0.RJGEUXM/
Type: Fastboot
Size: 5.3 GB
Release Date: 2021-11-09
Package Name: surya_eea_global_images_V12.5.4.0.RJGEUXM_20211109.0000.00_11.0_eea_e9805977c3.tgz
NOSS8 said:
https://xiaomifirmwareupdater.com/miui/surya/stable/V12.5.4.0.RJGEUXM/
Type: Fastboot
Size: 5.3 GB
Release Date: 2021-11-09
Package Name: surya_eea_global_images_V12.5.4.0.RJGEUXM_20211109.0000.00_11.0_eea_e9805977c3.tgz
Click to expand...
Click to collapse
OK, I see that the one I downloaded was the 2.7GB recovery version rather than the 5.3GB fastboot version, but isn't the boot.img the same in both?
doveman said:
OK, I see that the one I downloaded was the 2.7GB recovery version rather than the 5.3GB fastboot version, but isn't the boot.img the same in both?
Click to expand...
Click to collapse
Yep, normally, in the current recovery there is only a "payload.bin" file but maybe on old phones the boot.img is present (I don't remember).
Maybe download it and check the imgs in the img folder.
Have you tried with an older or beta version of Magisk?
In case the cmd posted above is generic, the real cmd is:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta vbmeta.img
Check:
https://forum.xda-developers.com/t/...n-vendor-dynamic-partition-enable-rw.4238807/
https://forum.xda-developers.com/t/q-h-safety-way-to-unlock-bootloader-flash-recovery-root.4198719/
NOSS8 said:
Yep, normally, in the current recovery there is only a "payload.bin" file but maybe on old phones the boot.img is present (I don't remember).
Maybe download it and check the imgs in the img folder.
Have you tried with an older or beta version of Magisk?
In case the cmd posted above is generic, the real cmd is:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Yeah, in the "miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" recovery version, there's a boot.img in the root folder and vbmeta.img (and vbmeta_system.img) in the firmware-update folder.
In the fastboot version, the boot.img is in the images folder but it's the same size (134,217,728) as is vbmeta.img (4,096).
I realised I made a stupid mistake as I was trying to do it in Powershell and it was saying "unknown option -- disable-verity" so it was adding a phantom space between -- and disable-verity. I reflashed the patched boot.img and vbmeta.img using those switches from a command prompt and it flashed them OK, but after rebooting Magisk still says it's not rooted!
doveman said:
Yeah, in the "miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" recovery version, there's a boot.img in the root folder and vbmeta.img (and vbmeta_system.img) in the firmware-update folder.
In the fastboot version, the boot.img is in the images folder but it's the same size (134,217,728) as is vbmeta.img (4,096).
I realised I made a stupid mistake as I was trying to do it in Powershell and it was saying "unknown option -- disable-verity" so it was adding a phantom space between -- and disable-verity. I reflashed the patched boot.img and vbmeta.img using those switches from a command prompt and it flashed them OK, but after rebooting Magisk still says it's not rooted!
Click to expand...
Click to collapse
What happens if you try to root from the Magisk app?
NOSS8 said:
What happens if you try to root from the Magisk app?
Click to expand...
Click to collapse
The only option in the Magisk app is to root by patching the boot.img, which you then have to flash in fastboot.
I know it used to have an option to root in situ but I think that was removed some time ago.
doveman said:
The only option in the Magisk app is to root by patching the boot.img, which you then have to flash in fastboot.
I know it used to have an option to root in situ but I think that was removed some time ago.
Click to expand...
Click to collapse
No functional TWRP for this device.?
NOSS8 said:
No functional TWRP for this device.?
Click to expand...
Click to collapse
Yeah, I've got TWRP installed. I tried booting into that after flashing in fastboot, as I recall there was an issue once (probably on a different device) where the root wouldn't "stick" if you didn't do that, but it didn't help.
doveman said:
Yeah, I've got TWRP installed. I tried booting into that after flashing in fastboot, as I recall there was an issue once (probably on a different device) where the root wouldn't "stick" if you didn't do that, but it didn't help.
Click to expand...
Click to collapse
Strange case as strange as the number of threads has this subject for this device.
NOSS8 said:
Strange case as strange as the number of threads has this subject for this device.
Click to expand...
Click to collapse
I tried flashing the patched boot.img in TWRP, followed by the vbmeta.img, then I went to Advanced and did the "Fix AVB (vbmeta)". Now the System can't boot at all and it just boots into TWRP every time, so I guess that "Fix AVB (vbmeta)" has screwed something up.
doveman said:
I tried flashing the patched boot.img in TWRP, followed by the vbmeta.img, then I went to Advanced and did the "Fix AVB (vbmeta)". Now the System can't boot at all and it just boots into TWRP every time, so I guess that "Fix AVB (vbmeta)" has screwed something up.
Click to expand...
Click to collapse
This phone is rootable, surely an oversight or an error somewhere.
NOSS8 said:
This phone is rootable, surely an oversight or an error somewhere.
Click to expand...
Click to collapse
I've tried reflashing the patched and the original boot.img and vbmeta.img but it still says "System is destroyed" if I try to boot to System. I don't know what the "Fix AVB" did but it's not good!
doveman said:
I've tried reflashing the patched and the original boot.img and vbmeta.img but it still says "System is destroyed" if I try to boot to System. I don't know what the "Fix AVB" did but it's not good!
Click to expand...
Click to collapse
In case you can always flash a recovery or use Miflash to recover the phone.
To see:
https://www.gizmochina.com/2020/10/13/how-to-unlock-bootloader-and-root-poco-x3-nfc/
NOSS8 said:
In case you can always flash a recovery or use Miflash to recover the phone.
To see:
https://www.gizmochina.com/2020/10/13/how-to-unlock-bootloader-and-root-poco-x3-nfc/
Click to expand...
Click to collapse
I've already got TWRP recovery flashed. I guess I'll have to flash the ROM again and start from scratch.
I tried flashing super.img but that didn't fix it. In the end, going into ADB Sideload mode in TWRP and flashing the 2.7GB recovery version of the ROM with
"adb sideload miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" fixed it without losing any data.
I still can't root it though. I've tried the "install Magisk (root)" option in TWRP and renaming magisk.apk to magisk.zip and installing that in TWRP, but it still shows "Installed N/A" in Magisk and Root Verifier says "Root permission not granted or Superuser App Missing" but then it says "Superuser App: 25.25:MAGISKSU", so it's the root permission that isn't granted.
Surely that is the problem.
https://techshift.net/what-is-disable-verity/
NOSS8 said:
Surely that is the problem.
https://techshift.net/what-is-disable-verity/
Click to expand...
Click to collapse
I thought so but I've reflashed the patched boot.img and done
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
and
"fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img"
in case it needed that too, but Magisk still shiows "Installed N/A"
I tried installed SR5-SuperSU-2.82 zip from TWRP to see if that would get it rooted,, but it couldn't even install that, it just gave some error.