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.
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.
I am thinking of just going on stock android but i like adblock. So i will end up rooting my phone, i was wondering if there is a way to update Lollipop rooted without having to restore. I dont mind loosing my root after every update, i can always re root
thanks guys
rolgar20 said:
I am thinking of just going on stock android but i like adblock. So i will end up rooting my phone, i was wondering if there is a way to update Lollipop rooted without having to restore. I dont mind loosing my root after every update, i can always re root
thanks guys
Click to expand...
Click to collapse
Download new factory images
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
reboot into your custom recovery
flash the latest SuperSU (http://download.chainfire.eu/supersu)
Elluel said:
Download new factory images
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
reboot into your custom recovery
flash the latest SuperSU (http://download.chainfire.eu/supersu)
Click to expand...
Click to collapse
Wouldn't that wipe my data?
rolgar20 said:
Wouldn't that wipe my data?
Click to expand...
Click to collapse
The only things that will wipe your data:
unlocking the bootloader (which I assume you already have unlocked due to having root access)
flashing userdata.img (if you read my previous post, I left this out)
wiping the data partition in recovery
factory reset option in Android (which really just boots into recovery and wipes data from there)
Elluel said:
The only things that will wipe your data:
unlocking the bootloader (which I assume you already have unlocked due to having root access)
flashing userdata.img (if you read my previous post, I left this out)
wiping the data partition in recovery
factory reset option in Android (which really just boots into recovery and wipes data from there)
Click to expand...
Click to collapse
Wonderful, thanks!
Guys, tired of waiting for Nougat update on my Moto X Pure I took a route and never regretted. I converted my Pure edition to Style RETEU.en and went all the way to Nougat, without any hiccup.. Phone is as smooth as was with Marshmallow version. Below I will describe all the steps for successful update to Nougat. Skipping the details that we all know of. REMEMBER: You do at your own risk and I am not responsible for any of your mistake (Complete each step exactly. They are simple)
1. Get your bootloader unlocked as we will require it once, to take a nandroid backup for safety.
2. Install TWRP 3.1.1.0 to make a nandroid backup on phone.
3. Once backup is done copy it from phone to PC to make it safe. It will take some time as mine was 6GB in size.
4. Before rebooting into fastboot select "Do not install TWRP" in recovery.
5. Now using fastboot start flashing components from Official stock ROM of Motorola downloaded from dl.prazaar.de which is XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5. This is Android Marshmallow base at 6.0.1. Not to flash components is boot, partition, Modem, fsk and recovery files. Make sure you flash rest of files including all the sparsechunks. Commands can ne found elsewhere on the forum.
6. Reboot into recovery and clear cache and userdata partitions. Reboot normal now.
7. Phone will start the setup like after factory reset. Just skip restoring your personal data by answering No to save time. But let it complete whatever else it do. Now "About phone" will say device is Moto X Style and build is MM 6.0.1 RETEU.en. This is just fine. Phone converted (No GSM signal is no worry at this time).
8. Try System Update. If update is available fine, otherwise we do it manually to take it to MPHS24.107-58-13 (required as Nougat pre-requisite).
9. Download Blur_Version.24.221.5.clark_reteu.reteu.en.EU from dl.prazaar.de. This is MPHS24.107-58-13 update. Copy it to root of Phone memory and reboot to recovery and pick Apply update from SDcard. The update will happen smoothly.
10. Again boot and skip Android setup. About phone will say your current build version.
11. Now download and copy Blur_Version.24.231.13.clark_reteu.reteu.en.EU from dl.prazaar.de into root directory of your phone.
12. Boot into recovery and choose Apply the file from SDCard. WOW this is Nougat update. It will successfully complete the update.
13 Download Last official Clark MM stock ROM from Motorola website and open the zip file to extract NON-HLOS.bin and fsk.mbn and flash it from fastboot in the standard way.
14. Go into recovery and clean cache and userdata partitions
15. Boot normally to be greeted by Nougat firsttime setup.
16. Congratulations. You have Nougat and Moto X Style.
No links to files?
You have not read it completely. I have mentioned download source which is dl.prazaar.de for all the files. Since each file is Stock ROM or blur version and greater than 1GB. What is the purpose to attach them here? The site is well know to carry Style firmware.
What about ota?
Bart_UA said:
What about ota?
Click to expand...
Click to collapse
There are two files I mentioned that starts with the name "Blur_Version". These are always OTAs!!! You apply through Wifi or SDCard, what is the difference?
This is my About Phone screen after the update.
jaffers said:
This is my About Phone screen after the update.
Click to expand...
Click to collapse
You can do backup with twrp and upload it for them.
Boot(before root)+system only.
Root is not required in my steps and TWRP not installed permanently (See my steps).
I know. I have xt1572, don't need.
For others you can do backup and upload it. All what they need: boot+system partitions.
For Backup & restore:
fastboot boot twrp.img
Anyone who want restore should do own backup and copy yours into the same folder.
Into twrp works MTP.
GOOD LUCK FOR ALL.
Out of curiosity... why go through this when its "easier" to just root and flash DU or LineageOS? Is the "stock" nougat running that much more smoothly? Its 7.0 with an old security path right? The latest versions of DU and Lineage are 7.1.2 and have up to date security patches.
Bwangster12 said:
Out of curiosity... why go through this when its "easier" to just root and flash DU or LineageOS? Is the "stock" nougat running that much more smoothly? Its 7.0 with an old security path right? The latest versions of DU and Lineage are 7.1.2 and have up to date security patches.
Click to expand...
Click to collapse
Very simple. people like me don't want to loose Moto Action, Moto Display and Moto Voice. You loose all that in custom roms. I tried Lineage in my wife's Moto X 2014 a month ago. Frequent reboots, crash and reboot during video recording etc. This after several months of constant updates. Stock ROM do not have this type of issues. Atleast in the last decade not once any of my phone ever rebooted on its own. So I don't approve custom roms. If you don't mind, go ahead.
dzidexx said:
I know. I have xt1572, don't need.
For others you can do backup and upload it. All what they need: boot+system partitions.
For Backup & restore:
fastboot boot twrp.img
Anyone who want restore should do own backup and copy yours into the same folder.
Into twrp works MTP.
GOOD LUCK FOR ALL.
Click to expand...
Click to collapse
I debloated Stock Nougat before setting up my phone. If I give them my image then they will loose confidence of my steps cause several apps are not present. It is better to take standard update route.
jaffers said:
I debloated Stock Nougat before setting up my phone. If I give them my image then they will loose confidence of my steps cause several apps are not present. It is better to take standard update route.
Click to expand...
Click to collapse
Yes. Now you shouldn't.
Bwangster12 said:
Out of curiosity... why go through this when its "easier" to just root and flash DU or LineageOS? Is the "stock" nougat running that much more smoothly? Its 7.0 with an old security path right? The latest versions of DU and Lineage are 7.1.2 and have up to date security patches.
Click to expand...
Click to collapse
Stock Nougat is getting August security patch rigth now!
Dual sim
Is it dual sim supportable after updating?
NahuelMS said:
Stock Nougat is getting August security patch rigth now!
Click to expand...
Click to collapse
Blueborne is fixed in September security fix.
jaffers said:
Guys, tired of waiting for Nougat update on my Moto X Pure I took a route and never regretted. I converted my Pure edition to Style RETEU.en and went all the way to Nougat, without any hiccup.. Phone is as smooth as was with Marshmallow version. Below I will describe all the steps for successful update to Nougat. Skipping the details that we all know of. REMEMBER: You do at your own risk and I am not responsible for any of your mistake (Complete each step exactly. They are simple)
9. Download Blur_Version.24.221.5.clark_reteu.reteu.en.EU from dl.prazaar.de. This is MPHS24.107-58-13 update. Copy it to root of Phone memory and reboot to recovery and pick Apply update from SDcard. The update will happen smoothly.
11. Now download and copy Blur_Version.24.221.5.clark_reteu.reteu.en.EU from dl.prazaar.de into root directory of your phone.
Click to expand...
Click to collapse
Hi, downloading the necessary files to upgrade my phone and I see you show the same file to download in steps 9 and 11. Is this file being installed twice?
5. Now using fastboot start flashing components from Official stock ROM of Motorola downloaded from dl.prazaar.de which is XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5. This is Android Marshmallow base at 6.0.1. Not to flash components is boot, partition, Modem, fsk and recovery files. Make sure you flash rest of files including all the sparsechunks. Commands can ne found elsewhere on the forum.
Click to expand...
Click to collapse
I completed the steps up to this one. I want to make sure I don't accidentally flash everything.
So noob question, what files do I not fastboot? I know boot and recovery. Appreciate the help.
NON-HLOS.bin
fsg.mbn
BTFM.bin
flashfile.xml
servicefile.xml
slcf_ref_d_default_v.1.0.nvm
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
any possibility to flash custom recorvery/root on android 7? When im flashing recorvery via fastboot it says "permission deined"
nvm im dumb, misswrite a single letter in fastboot
I find this post a bit hard to read.
1). You are not really clear on exactly what to flash. You are close but not precise. If you are going to provide instruction like this you might need to be a bit more granular.
2). You mention the same file twice for both the pre-requisite patch and the nougat update. Are then both one in the same? This doesn't make sense.
I followed these instructions up to step #7. I flashed the following files:
logo.bin
BTFM.bin
fastboot flash bootloader bootloader.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
I left out the following:
boot.img
fsg.mbn
gpt.bin
NON-HLOS.bin
recovery.img
My phone is showing Moto X Style however my build # is MPHS24.107-58-5 and not MM 6.0.1 RETEU.en
System version is reporting 24.221.5.clark_reteu.reteu.en.EU retus
If I try to move forward with the MPHS24.107-58-13 update I get a digital signature error.
jaffers said:
You have not read it completely. I have mentioned download source which is dl.prazaar.de for all the files. Since each file is Stock ROM or blur version and greater than 1GB. What is the purpose to attach them here? The site is well know to carry Style firmware.
Click to expand...
Click to collapse
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.
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.