Related
Due:
Please help me.
my kindle fire Unbricking,i need kindle fire system.img to fastboot IT.
i have Factory Cable.
so i need system.img.who can help me ?
THX.a
http://www.megaupload.com/?d=7QY56FGA system.img
Do you made this cable by yourself?
Do you made this cable by yourself?[/QUOTE]
THX.I just buy it.i'm chinese.
DUE:
system.zip Unexpected end of archive:
This system.img was posted somewhere on the forum ... There are no instructions recovery device using fastboot mode. No experience of successful recovery Kindle Fire.
It would be nice if someone made a instructions on how to restore the unit if you have access to Fastboot.
Not sure, but I believe it would be:
fastboot update <filename.zip> -w
You should be able to download the entire update from Amazon.com, rename it update.zip, then run that, effectivly reloading the entire system, boot, and recovery. the -w at the end wipes all user data, so use at own risk.
Fastboot Commands
Here are the commands you can run on your host after fastboot has been started on a device connected via USB. This is a paste directly from the fastboot binary's "--help" command:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
MayfairDROID said:
Not sure, but I believe it would be:
fastboot update <filename.zip> -w
You should be able to download the entire update from Amazon.com, rename it update.zip, then run that, effectivly reloading the entire system, boot, and recovery. the -w at the end wipes all user data, so use at own risk.
Fastboot Commands
Here are the commands you can run on your host after fastboot has been started on a device connected via USB. This is a paste directly from the fastboot binary's "--help" command:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
Click to expand...
Click to collapse
Tried it yesterday. Returns:
archive does not contain 'android-infor.txt'
archive does not contain 'android-product.txt'
archive does not contain :android-info.txt"
Although I suppose I could create dummy txt files and see what happens...
MayfairDROID said:
Not sure, but I believe it would be:
fastboot update <filename.zip> -w
You should be able to download the entire update from Amazon.com, rename it update.zip, then run that, effectivly reloading the entire system, boot, and recovery. the -w at the end wipes all user data, so use at own risk.
Click to expand...
Click to collapse
Yeah IN RECOVERY yes, if fastboot no. You cannot go and flash the update.zip from amazon in recovery. You need to create a system.img and flash that properly in fastboot. If you go google the directions for fastboot, it will tell you how.
yareally said:
Yeah IN RECOVERY yes, if fastboot no. You cannot go and flash the update.zip from amazon in recovery. You need to create a system.img and flash that properly in fastboot. If you go google the directions for fastboot, it will tell you how.
Click to expand...
Click to collapse
Yes but that's the problem, at least with with my level of expertise. This is kind of a catch 22 situation. We really need someone with a rooted and operable device to make available a backup of a stock system.img. Once that's avail. it's as simple as plugging in the factory cable to enable fastboot and entering the command.
kfuller said:
Yes but that's the problem, at least with with my level of expertise. This is kind of a catch 22 situation. We really need someone with a rooted and operable device to make available a backup of a stock system.img. Once that's avail. it's as simple as plugging in the factory cable to enable fastboot and entering the command.
Click to expand...
Click to collapse
No you don't.
You just need to grab the update file from amazon
Create a system.img from the /system folder
flash in fastboot
done
yareally said:
No you don't.
You just need to grab the update file from amazon
Create a system.img from the /system folder
flash in fastboot
done
Click to expand...
Click to collapse
Thanks. I've had the update file for some time and I do understand that it can be done, but the creation of the system.img from files seems quite involved for my level of skills and a windows box. I have googled it. On the other hand, the task appears much simpler on a working android machine and I was hoping that someone had already done it in this forum and could ease the pain. But, I'll get there if not. Sooner or later.
kfuller said:
Thanks. I've had the update file for some time and I do understand that it can be done, but the creation of the system.img from files seems quite involved for my level of skills and a windows box. I have googled it. On the other hand, the task appears much simpler on a working android machine and I was hoping that someone had already done it in this forum and could ease the pain. But, I'll get there if not. Sooner or later.
Click to expand...
Click to collapse
Need to do it in linux because it has to be ext4.
I would do it, but I don't have time right now (packing for a trip this weekend).
I'm running ubuntu, so could do it if someone posts up instructions.....
Sent from my Kindle Fire using Tapatalk
MayfairDROID said:
I'm running ubuntu, so could do it if someone posts up instructions.....
I see this tool that may work http://android.podtwo.com/romdump/ but looking for a tut that shows more detail of what you get..
OK, this looks most promising. Here is a link showing using the rkdump utility: http://wiki.archosfans.com/index.ph...m_rom#Dump_partitions_the_easy_way_via_rkdump
Dump partitions from your Home Tablet
You can't dump partitions the normal way with cat/dd command as you might be used to on linux/unix/macOSX. The /dev/mtd/mtd* is useless on RK28xx devices.
You can use the /dev/block/mtd* devices, but in this case you can read beyond the end of the partition if you set the blocksize too large (or you can read not enough if you set it too small).
For the next steps you need to be rooted. A softrooted device is sufficient.
To softroot your device download z4root and some terminal apk and install them.
In the terminal you first issue the command "su" to get to superuser mode. note: as mentioned above: all numbers and sizes, partitions and partition sizes are based on the original 1.0.0 firmware of the A7 HT Version 2.
To get a list of the available partitions type:
# cat /proc/mtd
dev: size erasesize name
mtd0: 00002000 00000010 "misc"
mtd1: 00004000 00000010 "kernel"
mtd2: 00002000 00000010 "boot"
mtd3: 00004000 00000010 "recovery"
mtd4: 00030000 00000010 "system"
mtd5: 0003a000 00000010 "backup"
mtd6: 0003a000 00000010 "cache"
mtd7: 00100000 00000010 "userdata"
mtd8: 00cbc000 00000010 "user"
mtd9: 00020000 00000010 "pagecache"
mtd10: 00020000 00000010 "swap"
The update.img to restore your A7HT is identical to the backup partition.
With this information we can dump our original update.img or create dumps from e.g. the system.img. There are 2 ways to do this:
- The easy way via the rkdump utility.
- The hard way via dd (in case you really want to know the ins and outs).
Dump partitions the easy way via rkdump
The rkdump utility is an Android command line utility and needs to be run from your tablet. Unzip the rkdump utility from the downloaded zip file. Copy it to your tablet, either via the "normal" USB copy way or via ADB push. Copy it onto your /data partition and not on your /sdcard partition or the SD-card itself (it needs to be run from an ext3 partition, not a vfat partition). If neccessary do a "chmod 771 rkdump" to give it the correct attributes. Now from a rooted terminal you can dump the update.img. Our update.img is equal to the backup.img which, in this case, is located on mtd5. To get our update.img we now type in the (rooted) terminal.
# /data/rkdump /dev/block/mtdblock5 /sdcard/update.img
This will dump the update.img to the internal memory of the tablet. It will immediately save it in the correct size. There are no "post dump" actions required to the image as it has the right size and the 4-byte crc set.
Sooo, looks like you can simply substitute system.img in the above tutorial to create the system.img which can then be pulled off the kindle with adb. Does this sound ok?
Click to expand...
Click to collapse
I command you to rise from your grave and rescue my... Kindle. (10 points if you can name the reference).
I'm suffereing the same issue. I've managed to get my SD Card, recovery, boot, and boot loader partitions working, but I need a system.img and any other img files I haven't listed. I thought there was another one, but I cant't find my notes on it. I would be indebted to you. Thanks.
vampyrex13 said:
I command you to rise from your grave and rescue my... Kindle. (10 points if you can name the reference).
I'm suffereing the same issue. I've managed to get my SD Card, recovery, boot, and boot loader partitions working, but I need a system.img and any other img files I haven't listed. I thought there was another one, but I cant't find my notes on it. I would be indebted to you. Thanks.
Click to expand...
Click to collapse
Well... since nobody else answered you... Is there a reason you are trying to do it this way? If you have access to recovery and SD Card, you can just flash whatever you want in recovery.
kinfauns said:
Well... since nobody else answered you... Is there a reason you are trying to do it this way? If you have access to recovery and SD Card, you can just flash whatever you want in recovery.
Click to expand...
Click to collapse
I have an issue with the mmcblk0 partition not having a label (gpt). I tried yaff'ing up the current Kindle Fire update and fastbooted it over, but that didn't work. I even deleted mmcblk0 and then fastbooted the update over and it recreated the partition, but had the same issue still. My only other avenues available are to try an actual stock img (in case I was missing something when I yaff'ed my copy) or completely recreate all the partitions from scratch. I would much rather fastboot the system image though.
vampyrex13 said:
I have an issue with the mmcblk0 partition not having a label (gpt). I tried yaff'ing up the current Kindle Fire update and fastbooted it over, but that didn't work. I even deleted mmcblk0 and then fastbooted the update over and it recreated the partition, but had the same issue still. My only other avenues available are to try an actual stock img (in case I was missing something when I yaff'ed my copy) or completely recreate all the partitions from scratch. I would much rather fastboot the system image though.
Click to expand...
Click to collapse
Whoah.... You'd better be careful with those partitions. If something goes bad with the first two partitions, you might be looking at opening up your case. If you need to write your partition table back to stock, it's much easier and safer to use "fastboot oem format" in FFF 1.1 or later. It will write a stock partition table for you.
Even if you did manage to make a system.img (I think I looked into this before, but couldn't find a good reference), I doubt fastboot will flash it for you. I think I tried this too and it was too big for fastboot to hold it in memory before it attempted to write it out to the partition.
I think your best bet is to download the software update from Amazon, rename it as a zip file, then use TWRP to flash the whole thing. The only bad thing about it is that you will lose your custom bootloader and recovery and you'd have to jump through some hoops to get them back again.
Alternatively, I've been experimenting with the idea of using "adb push" to copy the /system directory from the software update package over onto the device. I've "ported" the set of commands in the updater-script that creates the symbolic links and changes owner/permissions of all the files over to a shell script that can be run through adb. It should pretty much be equivalent to how the system files get installed through recovery. If you want to give it a try, send me a PM.
Ofastboot oem format fails and i've already opened the case to do the usb trick.
vampyrex13 said:
Ofastboot oem format fails and i've already opened the case to do the usb trick.
Click to expand...
Click to collapse
You're probably using an older version of FFF... you need v1.1 or later. If you used the shorting method, that probably means you have Firekit somewhere. I believe the u-boot.bin in there is FFF v1.2 or search the development section for one of the later versions. Flash one of them and try again.
I am unable to flash the factory image for 5.1 for my lte tablet, I tried redownloading the factory image several times:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 846100724 bytes
error: update package missing system.img
Press any key to exit...
You can try to unpack the factory image, up to the point where you find eg. boot.img, system.img.
I guess that you know how to use ADB and FASTBOOT and already have everything you need inside your eg. Android folder.
1) copy the bootloader, boot.img , system.img inside your "Android folder" ( the folder which contains ADB, FASTBOOT )
2) flash the bootloader ( make sure to type in the right name )
3) flash boot.img , system.img
Restart the device and have fun :good:
So.... I manually flashed the 5.1 for my wifi Nexus 7 2013 and it the first boot is going on 15 minutes with the swirling color dots. I know the first boot I was told will be long... But 15 minutes or more? When should I start to think something is wrong?
Sent from my VS985 4G using XDA Free mobile app
First of all, this guide expects you to have some basic knowledge how to use fastboot, have working ADB/fastboot connection on your computer and understand the fact that this may brick your phone if you mess up.
I am NOT responsible for anything! This will wipe everything on your phone, so get backups if needed.
This guide is written for X720 and supplied files are ONLY for X720. Same procedure will work on X727, but you will have to get right files yourself.
All files are from stock 23S, just extracted, converted and repacked for your convenience.
Read the whole guide before doing anything. If you're unsure about anything, don't do it.
Here we go:
1. Download .zip containing files from Mega: https://mega.nz/#!5boxDYrL!_O-oD05yhiU5FbCmYuf47VH4Qar5RhV5LKwyHa39bWM
2. Extract files to path where you are able to flash them using fastboot (ie. same folder with fastboot)
3. Boot your phone to bootloader (Vol- & Power)
4. Flash everything:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format data <-- THIS WILL WIPE YOUR PHONE INCLUDING INTERNAL STORAGE
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash ddr ddr.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash hyp hyp.mbn
fastboot flash pmic pmic.elf
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash xbl xbl.elf
fastboot flash keymaster keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash bluetooth BTFM.bin
fastboot flash devinfo devinfo.bin​5. Reboot, and let it boot up (takes some time)
6. Flash TWRP, wipe everything and install ROM (you have done this before, won't write a guide)
Credit for this guide goes to @darkobas
get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.
Presterin said:
I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.
Click to expand...
Click to collapse
thx
i will try again.
Does anyone know which ones are safe to flash over the existing rom? I do not wish to wipe or break current rom.
I flashed everything except system and boot on top of Omni rom. Everything works great.
Does anyone know where I can get all of the files for my x727, I considered using the files from these OTA zips but I think some of the files are missing like the modem firmware and system.img.
On x720 some of the files were divided into scatter files, had to do some research to get them sorted.
Which fastboot is compatible with system.img? Because of me too :"target reported max download size of 536870912 bytes
Invalid sparse file format at header magi". minimal fast boot 1.42
Edit: ok..as long as the post I wrote started installation
Should/Can we install the latest fastboot? Mine is on shop altered 17s from over a year a go, which to be fair runs great; i just fancy a change.
Thanks
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Any solution?
Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
Stuck here as well
Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished
Great guide Thanks.
It saved me from a system wipe and a nightly not recognized by TWRP...:crying:
tsongming said:
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished
Click to expand...
Click to collapse
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.
jackpollard said:
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
amdol said:
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
Click to expand...
Click to collapse
Thank you! My flaw was looking on https://lineageos.org/ and not on here.
ajegile said:
get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
get the same. iam not shure if i have the x722 or x720. they look same
So today I tried to flash Pie over my rooted 8.0. I used partition DL mode and first selected everything but ABL_A/B, userdata, and all my A partitions, hoping to preserve that slot just in case. When I tried to boot into my B slot with 9.0, it just went into fastboot. Alright, whatever, I can keep 8.0, no biggie. I fastboot --set-active=a but this time it got stuck decrypting on the open lock icon with the rotating ring after entering my PIN. Okay, fine, I'll flash again. Enter Firmware Update mode, use partition DL mode, select everything except ABL_A/B, flash. Now I'm stuck in fastboot. Android won't boot, and attempting to enter Firmware Update mode and get a red triangle with the message "your device has failed a routine safety check and will not boot". I then used fastboot to flash my previous 8.0 backed up laf.img over my laf_b partition. Now, when I attempt to enter Firmware Update mode, I get the normal blue progress bar briefly, but then it just goes back to fastboot.
Which is where I am now. Any ideas? I'm thinking maybe if I "complete" the upgrade and flash a stock 9.0 ABL partition it might work, but I don't have one of those, LG Firmware Extract only produces an .elf file, kdztools gives an error when trying to extract the .dz:
F:\backup\LGV35\kdztools-master>undz.py -f tmp/V35020d_00_OPEN_US_0612.dz -l
[!] Warning: extraneous data found IN version
Traceback (most recent call last):
File "F:\backup\LGV35\kdztools-master\undz.py", line 1069, in <module>
dztools.main()
File "F:\backup\LGV35\kdztools-master\undz.py", line 1035, in main
self.dz_file = UNDZFile(cmd.dzfile)
File "F:\backup\LGV35\kdztools-master\undz.py", line 901, in __init__
self.loadChunks()
File "F:\backup\LGV35\kdztools-master\undz.py", line 622, in loadChunks
g = gpt.GPT(self.chunks[0].extract())
File "F:\backup\LGV35\kdztools-master\undz.py", line 221, in extract
buf = dctx.decompress(zdata, max_output_size=200000000)
zstd.ZstdError: error determining content size from frame header
I'd prefer not to have to hire an Octoplus owner to fix it since I still have an unlocked bootloader and still have fastboot, but I'm out of ideas. Oh, yeah, I also did "fastboot erase userdata", and attempted to do "fastboot format userdata", but the format failed. I also tried "fastboot -w" but got
F:\backup\LGV35>fastboot -w
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
Update: I flashed my backup 8.0 xbl partition. That, along with my 8.0 laf, has let me back into firmware update mode. I then flashed Pie again in partition DL mode, deselecting my abl_b, xbl_b, and laf_b. Seems it automatically switched my active slot back to A. At least I hope so, and my engineering abl_b with fastboot is still there.
I have successfully unlocked the Pixel 2 XL and installed the official release 8.0.0 / OPD1.170816.010 from Sep 2017. I downloaded Magisk and transfered the image to the phone and extracted the files on the phone.
According to the official guide, I have to patch the boot.img, but the image only contains a bootloader.img. When I use the "fastboot flash boot boot.img" command, it also tells me "No such partition".
How do I properly patch the official file and root the Pixel 2 XL without bricking it? Am I doing something wrong?
Venomiz said:
I have successfully unlocked the Pixel 2 XL and installed the official release 8.0.0 / OPD1.170816.010 from Sep 2017. I downloaded Magisk and transfered the image to the phone and extracted the files on the phone.
According to the official guide, I have to patch the boot.img, but the image only contains a bootloader.img. When I use the "fastboot flash boot boot.img" command, it also tells me "No such partition".
How do I properly patch the official file and root the Pixel 2 XL without bricking it? Am I doing something wrong?
Click to expand...
Click to collapse
Are you unzipping the second folder as well?
Factory Image .zip > unzip to factory image folder > unzip to 2nd factory image folder > boot.img
Curious as to why you're flashing 8x instead of android 10?
If you still hit a wall, check out the step by step instructions linked in my sig, near the bottom is an upgrade from os to os section ( 9x to android 10).
Az Biker said:
Are you unzipping the second folder as well?
Factory Image .zip > unzip to factory image folder > unzip to 2nd factory image folder > boot.img
Curious as to why you're flashing 8x instead of android 10?
If you still hit a wall, check out the step by step instructions linked in my sig, near the bottom is an upgrade from os to os section ( 9x to android 10).
Click to expand...
Click to collapse
Thanks for the reply. In the folder are the following files:
bootloader-taimen-tmz10n.img
flash-all.bat & .sh
flash-base.sh
radio-taimen-g8998-.....
And I overlooked the image-taimen-opd1.170816.010.zip
So, I patched with magisk the wrong file but it was successful (at least if I trust the onscreen text). I will now transfer the boot.img to the pixel, patch it, transfer it back, and flash. I will reply after doing so
PS: Android 8 is easier to use if you do something you should not in Pokemon Go... :silly:
And the
Why patch the boot image manually, flashing magisk via TWRP as it works fine. Ive never used the patch boot image method ever on any of the devices ive owned.
1) Flash ROM
2) Boot TWRP
3) Flash TWRP (optional)
4) Flash Magisk
5) Reboot
Hi folks, this is the current status.
I patched the boot.img and tried the following:
fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boota' (25632 KB)...
OKAY [ 0.542s]
writing 'boota'...
FAILED (remote: No such partition.)
finished. total time: 0.548s
What did I miss here?
Venomiz said:
Hi folks, this is the current status.
I patched the boot.img and tried the following:
fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boota' (25632 KB)...
OKAY [ 0.542s]
writing 'boota'...
FAILED (remote: No such partition.)
finished. total time: 0.548s
What did I miss here?
Click to expand...
Click to collapse
Let's start over from scratch because you're not following the instruction being posted, so maybe you are trying to accomplish something else.
What state is your device currently in and what are you trying to accomplish? I was under the impression you simply want to flash the last 8x factory image to your device, is that correct?
Az Biker said:
Let's start over from scratch because you're not following the instruction being posted, so maybe you are trying to accomplish something else.
What state is your device currently in and what are you trying to accomplish? I was under the impression you simply want to flash the last 8x factory image to your device, is that correct?
Click to expand...
Click to collapse
Uhm not really. As I said in the title, I want to root the Pixel 2 XL with Android 8 and Magisk.
So what I did so far is:
- Unlocked the bootloader and applied the Android 8 image
- Downloaded and installed magisk
- Unzipped the original rom wice to get the boot.img, transfer it to the phone, patched it with magisk and transfered it back to the PC.
When now trying to flash it with fastboot, the output above showed up.
Venomiz said:
Uhm not really. As I said in the title, I want to root the Pixel 2 XL with Android 8 and Magisk.
So what I did so far is:
- Unlocked the bootloader and applied the Android 8 image
- Downloaded and installed magisk
- Unzipped the original rom wice to get the boot.img, transfer it to the phone, patched it with magisk and transfered it back to the PC.
When now trying to flash it with fastboot, the output above showed up.
Click to expand...
Click to collapse
In fastboot do the following:
flash your factory 8 image (leave the -w intact to wipe your device, remove the -w to keep your data)
after your device boots up, get back to bootloader and fastboot the TWRP img from platform folder
once booted into TWRP, flash TWRP.ZIP to install cust recovery
in twrp flash cust kernel (optional)
reboot and allow the OS to fully settle in ( 1-2 minutes after bootup)
boot into TWRP and install magisk
reboot
These same instructions are found in much more detail in the link in my sig. I use this method every month for the latest update, and it's never failed. No patching images, no booting to diff slots, just follow the simple steps.
Az Biker said:
In fastboot do the following:
flash your factory 8 image (leave the -w intact to wipe your device, remove the -w to keep your data)
after your device boots up, get back to bootloader and fastboot the TWRP img from platform folder
once booted into TWRP, flash TWRP.ZIP to install cust recovery
in twrp flash cust kernel (optional)
reboot and allow the OS to fully settle in ( 1-2 minutes after bootup)
boot into TWRP and install magisk
reboot
These same instructions are found in much more detail in the link in my sig. I use this method every month for the latest update, and it's never failed. No patching images, no booting to diff slots, just follow the simple steps.
Click to expand...
Click to collapse
It worked perfectly, thank you!