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.
Related
Is it safe to wipe everything (including system and internal and so forth) using TWRP, then reboot into TWRP, and then flash only image-hammerhead-krt16m.zip? I ask because the stock .tgz file has a radio image, and I'm wondering if I'll need to flash that as well. I don't want to do flash-all.bat because I want to keep TWRP recovery.
.psd said:
Is it safe to wipe everything (including system and data and so forth) using TWRP, then reboot into TWRP, and then flash only image-hammerhead-krt16m.zip? I ask because the stock .tgz file has a radio image, and I'm wondering if I'll need to flash that as well. I don't want to do flash-all.bat because I want to keep TWRP recovery.
Click to expand...
Click to collapse
No you can't flash that zip in recovery. You can flash the individual files in fastboot though. Just don't flash the recovery.img if you want to keep twrp. I haven't tried this but it should work, if it doesn't you can also flash a twrp.img file after running the bat file.
Edit, if you do flash the bat file, remember you will wipe the device so backup what you want to keep on your pc beforehand.
.psd said:
Is it safe to wipe everything (including system and internal and so forth) using TWRP, then reboot into TWRP, and then flash only image-hammerhead-krt16m.zip? I ask because the stock .tgz file has a radio image, and I'm wondering if I'll need to flash that as well. I don't want to do flash-all.bat because I want to keep TWRP recovery.
Click to expand...
Click to collapse
jd1639 said:
No you can't flash that zip in recovery. You can flash the individual files in fastboot though. Just don't flash the recovery.img if you want to keep twrp. I haven't tried this but it should work, if it doesn't you can also flash a twrp.img file after running the bat file.
Edit, if you do flash the bat file, remember you will wipe the device so backup what you want to keep on your pc beforehand.
Click to expand...
Click to collapse
+1 on what jd says.
OP, you're mixing up 2 completely different processes. i would suggest a little more reading and searching to increase your knowledge and familiarity with fastboot/recovery procedural techniques on this device. cheers
jd1639 said:
No you can't flash that zip in recovery. You can flash the individual files in fastboot though. Just don't flash the recovery.img if you want to keep twrp. I haven't tried this but it should work, if it doesn't you can also flash a twrp.img file after running the bat file.
Edit, if you do flash the bat file, remember you will wipe the device so backup what you want to keep on your pc beforehand.
Click to expand...
Click to collapse
What about the radio image? If I wipe everything in TWRP (dalvick cache, system, data, internal storage, cache, and data), will I lose the radio and therefore need to re-flash it? Or do none of those wipe the radio, so it's safe to wipe all and then only flash image-hammerhead-krt16m.zip?
.psd said:
What about the radio image? If I wipe everything in TWRP (dalvick cache, system, data, internal storage, cache, and data), will I lose the radio and therefore need to re-flash it? Or do none of those wipe the radio, so it's safe to wipe all and then only flash image-hammerhead-krt16m.zip?
Click to expand...
Click to collapse
What are you trying to accomplish? Wiping in twrp will not wipe the radio. But you can't flash the hammerhead.zip. You can extract the files in it and flash them in fastboot.
jd1639 said:
What are you trying to accomplish? Wiping in twrp will not wipe the radio. But you can't flash the hammerhead.zip. You can extract the files in it and flash them in fastboot.
Click to expand...
Click to collapse
Just want to wipe my device as clean as possible and hopefully learn a little in the process. When I got my MacBook the first thing I did was wipe it and then reinstall OS X and the AppleCare people were like "why though?" Because I'm a nerd.
So does it follow the same convention as flashing a recovery? So...
1. ./fastboot flash cache cache.img
2. ./fastboot flash boot boot.img
3. ./fastboot flash system system.img
4. ./fastboot flash userdata userdata.img
?
Or are the commands different for each image? Does the order matter?
.psd said:
Just want to wipe my device as clean as possible and hopefully learn a little in the process. When I got my MacBook the first thing I did was wipe it and then reinstall OS X and the AppleCare people were like "why though?" Because I'm a nerd.
So does it follow the same convention as flashing a recovery? So...
1. ./fastboot flash cache cache.img
2. ./fastboot flash boot boot.img
3. ./fastboot flash system system.img
4. ./fastboot flash userdata userdata.img
?
Or are the commands different for each image? Does the order matter?
Click to expand...
Click to collapse
Yes that all looks correct for the Mac. Order doesn't matter
jd1639 said:
Yes that all looks correct for the Mac. Order doesn't matter
Click to expand...
Click to collapse
Thank you very much.
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.
yeah I need to flash stock rom because because my current rom is kinda buggy I downloaded the stock rom from a site and it contains these: boot.img, dtbo.img, metadata.img, recovery.img, super.img, userdata.img, vbmeta.img, vbmeta_samsung.img and fota.zip
I'm guessing it's either super.img or userdata.img because they are the biggest files please let me know
A Stock ROM typically comes as ZIP-file and gets flashed by ADB Sideload method: TWRP isn't needed for this.
jwoegerbauer said:
A Stock ROM typically comes as ZIP-file and gets flashed by ADB Sideload method: TWRP isn't needed for this.
Click to expand...
Click to collapse
don't have a pc with me rn that's why I gotta do it with twrp lolq
itsukii said:
don't have a pc with me rn that's why I gotta do it with twrp lolq
Click to expand...
Click to collapse
Flash each individual IMG file by selecting it and selected which partition is for the IMG file eg: vbmeta goes to vbmeta_a if ur on a/b and youre on slot a
areallydumbperson said:
Flash each individual IMG file by selecting it and selected which partition is for the IMG file eg: vbmeta goes to vbmeta_a if ur on a/b and youre on slot a
Click to expand...
Click to collapse
so I gotta flash everything before the os would work at all?
I suggest you to flash using fastboot.
Safe and secure.
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
now they have a proper 12S Ultra section!
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to "Advanced" and "flash this twrp."
edit: the recovery image file is too large to be flashed directly via fastboot, so you need to boot first then flash using twrp!
edit2: backup and restore function may not be working properly on this version of twrp! I get boot loops everytime I do a full system backup and full restore after bricking the device, especially on the data partition. Clean installing rom then restoring data only still get boot loops. so use it with caution.
I suggest you to use 3rd party backup apps to do backups on apps and data, and stick to the flashing and other functions only for twrp.
original source unofficialtwrp.com
Nabicook said:
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to Advanced and flash this twrp.
original source unofficialtwrp.com
Click to expand...
Click to collapse
Awesome thanks. But why not Fastboot flash recovery recovery.img?
No. You must type fastboot flash boot recovey. img
dungnghien said:
No. You must type fastboot flash boot recovey. img
Click to expand...
Click to collapse
No I'm pretty sure it's:
fastboot flash recovery twrp.img
However my question was why the method outlined by @Nabicook vs this method. Is it because of the dual partition?
GodKingKnight said:
Awesome thanks. But why not Fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
Because not only it is the method unofficialtwrp suggested, but also the size of the recovery img file is too large to be flashed via fastboot.
I already tried
fastboot flash recovery recovery.img
fastboot flash recovery_a recovery.img
and so on, but all failed.
only way to properly install this version of twrp is to boot first then let twrp to install itself to both a/b partitions.
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
joiliko said:
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
Click to expand...
Click to collapse
are you sure you did
fastboot boot (your recovery file name).img
it should automatically boot into twrp without touching anything from fastboot mode.
then install twrp through the advanced option in twrp
Nabicook said:
are you sure you did
fastboot boot (your recovery file name).img
Click to expand...
Click to collapse
Great many thanks! I was actually doing flash boot
Nabicook said:
then install twrp through the advanced option in twrp
Click to expand...
Click to collapse
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
yeah you can try flashing stock boot img, and if that doesnt work, you can download fastboot rom and flash stock rom using flash all without wiping data(there is .bat file that says something like install without formatting).
That will fix any kind of brick issues of xiaomi device, and you just redo the twrp part.
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
How to Extract payload.bin and get stock boot image file
To extract the payload.bin file from Android stock firmware and get stock boot image file, you should refer to the instructions given in here.
www.droidwin.com
My idea worked!
I used the method above to extract boot.img & flashed it successfully
Can someone tell me why wipe data and settings dosent work on my 12s ultra every time reboots the twrp after i press the icon... Im try at 7.5 version the same and on 7.2
Flashes unpatched int.boot.img file, then got attached message cannot start device. Can anybody help? Thanks!
Did you flash it to the init_boot partition or the boot partition?
Annie the Eagle said:
Did you flash it to the init_boot partition or the boot partition?
Click to expand...
Click to collapse
Thank you for your reply. I flashed by below command: flash boot unpachedname
Did i do things wrong? Sorry im realy a newbie
Yeah you can't flash init_boot.img to boot partition.
init_boot.img must go to the "init_boot" partition.
Thankfully, there is extracted IMGs here: https://forum.xda-developers.com/t/...xtracted-images-how-to.4505061/#post-87566815
Click the SourceForge link to the FASTBOOT IMAGES.
Then make sure you repair your boot partition by flashing over the boot.img to boot partition and the init_boot.img to init_boot partition.
Usual disclaimer: No warranty, I haven't tested any of these images but give it a try.
Annie the Eagle said:
Yeah you can't flash init_boot.img to boot partition.
init_boot.img must go to the "init_boot" partition.
Thankfully, there is extracted IMGs here: https://forum.xda-developers.com/t/...xtracted-images-how-to.4505061/#post-87566815
Click the SourceForge link to the FASTBOOT IMAGES.
Then make sure you repair your boot partition by flashing over the boot.img to boot partition and the init_boot.img to init_boot partition.
Usual disclaimer: No warranty, I haven't tested any of these images but give it a try.
Click to expand...
Click to collapse
Really apprexiate your reply let me try rhen cime back witj my result
I dlowlaoded and flashed. Now got a new ereor as attached. Any way to conletely reflash all things ?
Thanks!
Did you flash the both init_boot.img to init_boot and boot.img to boot? Make sure you do both.
flashboot flash boot boot.img
flashboot flash init_boot init_boot.img
bosox284 said:
Did you flash the both init_boot.img to init_boot and boot.img to boot? Make sure you do both.
flashboot flash boot boot.img
flashboot flash init_boot init_boot.img
Click to expand...
Click to collapse
Really appreciate ur support. Looks im in big trouble: did one again then it is keeping show this screen
Now rhe device is keeping rebooting l. Then this screen showed
Cannot even turn on. Stuck on the screen now ...
No offense, but if you are a "newbie" as you say, then why in the world would you want to risk a $900.00+ device that is so new to the modding world? What possible benefit could there really be even if you were successful? Remember, it IS possible to completely brick your phone and no warranty in the world will help. SMH
Are you using the stock images? I recommend doing a --slot=all to be safe. Reboot bootloader manually (Vol Down + Power), then run the same commands as before with --slot=all.
flashboot flash boot --slot=all boot.img
flashboot flash init_boot --slot=all init_boot.img
If that still fails, wait another 40 minutes or so until Google hopefully drops the factory images and just flash those. I don't think you're hard bricked just yet.
bosox284 said:
Are you using the stock images? I recommend doing a --slot=all to be safe. Reboot bootloader manually (Vol Down + Power), then run the same commands as before with --slot=all.
flashboot flash boot --slot=all boot.img
flashboot flash init_boot --slot=all init_boot.img
If that still fails, wait another 40 minutes or so until Google hopefully drops the factory images and just flash those. I don't think you're hard bricked just yet.
Click to expand...
Click to collapse
Thank you for your patience. I will try this tomorrow it is really late in japan. Appreciate your kind help. Wish you a nice day.
Keep you informed.
bosox284 said:
Are you using the stock images? I recommend doing a --slot=all to be safe. Reboot bootloader manually (Vol Down + Power), then run the same commands as before with --slot=all.
flashboot flash boot --slot=all boot.img
flashboot flash init_boot --slot=all init_boot.img
If that still fails, wait another 40 minutes or so until Google hopefully drops the factory images and just flash those. I don't think you're hard bricked just yet.
Click to expand...
Click to collapse
Tried only boot.img i can do. Ini_boot showed no sucj file
Flashed as you instructed but still saying corrupt. Btw i downloaded this file,is it correct ? Thanks!
That just means you don't have an init_boot file with that exact name in the folder. At this point I'd suggest waiting until Google drops the factory images so you can start fresh. Without knowing your version number you're basically going in blind flashing files that may or may not be relevant to your build.
When you run flashboot flash init_boot init_boot.img, the 'init_boot.img' needs to be the exact file name in your folder. So if your patched file is magisk_init_patched-25205_EfWOu.img, you're going to run fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
In the future, I suggest downloading the stock boot/init_boot files for your build number so that if something goes haywire then you can recover. I also would suggest holding off until factory images are available, especially if you're not sure what you're doing. That'll also give you a way to recover in a worst case scenario where nothing seems to work.
bosox284 said:
That just means you don't have an init_boot file with that exact name in the folder. At this point I'd suggest waiting until Google drops the factory images so you can start fresh. Without knowing your version number you're basically going in blind flashing files that may or may not be relevant to your build.
When you run flashboot flash init_boot init_boot.img, the 'init_boot.img' needs to be the exact file name in your folder. So if your patched file is magisk_init_patched-25205_EfWOu.img, you're going to run fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
In the future, I suggest downloading the stock boot/init_boot files for your build number so that if something goes haywire then you can recover. I also would suggest holding off until factory images are available, especially if you're not sure what you're doing. That'll also give you a way to recover in a worst case scenario where nothing seems to work.
Click to expand...
Click to collapse
Thank you very much. I will wait for the dactory images. Appreciate your support massively.
The factory images are now live: https://developers.google.com/android/images#cheetah
Download the file, extract the zip, and run flash-all at a command prompt. It should give you a fresh start.
bosox284 said:
The factory images are now live: https://developers.google.com/android/images#cheetah
Download the file, extract the zip, and run flash-all at a command prompt. It should give you a fresh start.
Click to expand...
Click to collapse
thank you. I flashed the fiemware and now it is back!
I was having the same issues; "fastboot flash init_boot_a <patched magisk.img>" worked for me.