Related
Ok, so I was running a custom ROM (I don't even recall which specific one at the moment....one of the Cromi ROMs). I tried to wipe it and install a new version, and the install didn't go as smoothly as planned. I can still load the TWRP recovery system, and begin attempting to install any ROM, but when it gets to the point where it says it's installing, the bar across the bottom that should show progress disappears almost instantly and the next button becomes available. When I go to reboot, it warns that there is no OS installed. Of course if I continue anyway, it won't boot beyond the Asus splash screen. There are errors in multiple places saying that it can't mount /system. I saw this error in the log file generated, I saw it during reboot, and there was some point in the TWRP screens where I saw it, but can't recall where at this moment. If I go into the Mounts section, System is not checked and I cannot check it.
I tried following the instructions on the unbricking thread and got stuck. I fear this has likely only made matters worse.
Following these steps:
Code:
fastboot erase boot
fastboot erase staging
fastboot format system
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery.img
fastboot reboot-bootloader
I was able to successfully erase the partitions mentioned, then when I tried to flash the first time, I actually screwed up and didn't have the blob file I needed, so now I go back, and obviously I can't re-erase the other files, but formatting system still works, so I know I'm getting good communication with the device. Then trying to flash the blob to staging, I get:
sending 'staging' (1379 KB)...
FAILED (command write failed (No such device or address))
Any thoughts or suggestions would be greatly appreciated. I've currently got an expensive paperweight.
So i was flashing manually ATT 5.1 Zip firmware(Source) with cmd, but i'm stuck on flashing system.img :crying:
E:\Bootloader Tool Kits>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1482130164 bytes
error: cannot load 'system.img': Not enough space
Click to expand...
Click to collapse
And after trying several times and it gives same result, i decided to skip that one. And then i tried to flash TWRP, it successful. I tried to restore my CM12 backup, it's going though but i can't reboot to system. When i reboot to system it keep going back to fastboot :crying:
How i can flash system.img or at least restore my CM12 backup?
EDIT:Now i can reboot to system with CM12 installed (backup) but it could not recognize my sim card
EDIT2:Now it can recognize my sim card. so for now, i ended up just updating my bootloader version hahaha
Solution to "cannot load 'system.img': Not enough space"
LuthfiKun said:
...
Click to expand...
Click to collapse
SOLUTION
I had the same issue using the official 5.1 from Motorola and KidJoe's guide. I saw in the options section that -P "enable parallel loading for multi-flash if there is no [sic] enough memory on host to load whole image."
Thus, using mfastboot flash system system.img -P loaded it in 256MB chunks which worked. It did sit on the moto logo for just long enough to strike fear, but is running beautifully now.
This was on a system with 13.9GB free of 16GB RAM....
I faced this issue just the last day, when I was trying to flash through mfastboot. I tried to flash with rsdlite and it worked fine. I guess the -P switch must be automatic in rsdlite!
-P worked thank you very much
Where I can find official ROM for asus me375cl based on android 5.1.1?
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
little_pindos said:
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
Click to expand...
Click to collapse
Thank you so much for posting where you found this, this is exactly what I needed!!! You saved my tablet, it is much appreciated! :good:
Flashing Factory Image
The following instructions worked for me when trying to reflash the factory firmware for the ATT Asus MemoPad 7 LTE (ME375CL). I did originally try using the Asus Flash Tool and the raw firmware file (link below) but the tool said it could not unzip the package for some reason or another. So the steps below show how I did it using ADB with fastboot.
I ASSUME NO LIABILITY SHOULD THIS GO WRONG FOR YOU! However, it probably shouldn't matter if you are bricked, I doubt it will make it any worse Either way, I will not replace your tablet or be responsible for troubleshooting it should you mess it up more...
This scenario is based on the tablet stuck on the Asus boot screen and not going any further. I was trying some in depth rooting attempts and bricked it badly. I was then trying to install a custom recovery and that is why I could not reset it and bricked it.
PRE-REQS:
1. ADB installed - Download: https://drive.google.com/open?id=0B0fKccJIuWsna04wMjY1eG9YREU
2. Asus Drivers installed
3. Firmware - Download: https://drive.google.com/open?id=0B0fKccJIuWsnWGhwYzA0Vkluc2s (file is 1 Gb + in size, may take a bit)
SETUP:
If you already have a working ADB setup, do not download the one above. If you are using the one above, I extracted the folder into my C: drive, so the path for ADB would be C:\adb (to keep it simple and less typing).
MAKE SURE THE ASUS DRIVERS ARE INSTALLED! If you have plugged the tablet in to a pc before, they should already be there. Otherwise search, download and install the appropriate drivers.
INSTRUCTIONS:
Extract the firmware zip file to somewhere easily accessible like your desktop. In there, you should see the boot.img, recovery.img and system.img files, copy/paste those files to your ADB folder (for easier typing later on). There are also additional files like these but start with "unsigned_", do NOT use those!
1. Ensure you probably have at least 30% battery charge, I would still recommend more though.
2. Put the tablet in Fastboot mode by ensuring the tablet is completely powered down and then press/hold the VOLUME UP and POWER keys at the same time. When the Asus screen appears, let go of the POWER button but continue to hold the VOLUME UP button. Let go of the VOLUME UP button when the fastboot screen appears.
3. Plug the tablet in to the computer and then open a CMD prompt as administrator.
4. The following uses the ADB downloaded and placed in the folder as listed above, you may need to adjust the location path as needed if you already have ADB installed or located in a different path.
Type in the following without the quotes: "cd c:\adb" (this will change the path to the ADB files for the CMD prompt)
Type in the following without the quotes: "fastboot devices" (you should then see a device listed)
Type in the following without the quotes: "fastboot flash recovery recovery.img" (flashes the factory recovery image)
Type in the following without the quotes: "fastboot flash system system.img" (flashes the factory system image, may take a while to flash)
Type in the following without the quotes: "fastboot flash boot boot.img" (flashes the factory boot image)
5. Once those 3 images have been flashed, you should have seen a message that says "OKAY" after each one. You should be fine as long as you do not have any red error messages on your tablet.
Type in the following without the quotes: "fastboot reboot" (reboots device normally)
6. If all goes well, it should now boot to the Asus screen and then go to the ATT screen. If so, it will stay on the ATT screen for a while, just wait it out. Mine took about 12-15 minutes and then it opened to the new setup screen to set the tablet up as if its new!
This is how I was able to recover my bricked tablet, hopefully it can help someone else that may run into this.
John, thank you for the write-up. Just bought my ME375CL with 4.4.4.4.
When I try to flash the recovery partition, I get the following error:
C:\Users\Myself\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11312 KB)...
OKAY [ 1.047s]
writing 'recovery'...
(bootloader) Official image.
FAILED (remote: flash_cmds error!
)
finished. total time: 2.344s
Click to expand...
Click to collapse
and on the tablet's screen:
FASTBOOT CMD WAITING...
RECEIVE DATA...
E:recovery flash failed!
FLASH FAILED!
RESULT: FAIL(flash_cmds error! )
Click to expand...
Click to collapse
I haven't tried the other commands for system.img or boot.img as I don't want to do anything out of order from the write-up. Ever run into this?
The firmware in the download is 5.1.1, not 4.4.4. That is probably the issue. If you are running good on that, I would try rooting it instead. If you are just wanting to upgrade, you will need to have an active AT&T SIM in the tablet to upgrade over the air. I am not sure if there is a flashable upgrade or not somewhere.
Oh ok John. I misread the title of the thread. I thought it was for updating from 4 to 5.
Quick question then: Is it possible, using the adb / fastboot tools, to backup the current 4.4.4.4 before I allow the tablet to update to Lollipop? After reading around, I understand that Lollipop can't be rooted but I have no real concern for it. But just in case I need the tablet to do something else in the future, I'd like to be able to return it to kit kat to be able to root.
Once you upgrade to lollipop, there is no downgrading for this tablet. There really is not much development for this device. I have kind of been working on a lollipop root when I can. Between my limited time and knowledge of android, I can't promise anything.
Overcoming red messages?
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool:
https://drive.google.com/open?id=0B0fKccJIuWsndXJUa1FEbXVzTjA
johnkirchner said:
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool: ]
Click to expand...
Click to collapse
As a follow up on your question above, Tab restart stalled at a screen (after the Asus logo), presenting some options to do recovery, reboot, factory reset, etc. (factory reset did not help), and red error messages at bottom.
To the GOOD news for anyone interested. I used the Asus Flash Tool and the firmware zip for 5.1.1 (many thanks for the advice).
Note: Tool did not install correctly on Win10 pc, citing error in installing some devcon.exe or similar file (guess that may be a firewall/antivirus issue).
Flash tool took some 15 or so mins unzipping firmware, after which I saw some action on the tab. Another 15 mins, and it rebooted to the At&t logo, stayed here for another 15 mins and unraveled a whole new device on Android 5.1
Glad to hear it worked for you and that I guess you can use this to flash upgrade from kitkat!
There is working way to root our device on lollipop! It is for the other Asus model, but it works for our
http://4pda.ru/forum/index.php?s=&showtopic=640814&view=findpost&p=53047686
I will check this out!
The root works, installed without any issues and verified with a root checker!
Here is a direct download from my Drive folder: https://drive.google.com/open?id=0B0fKccJIuWsnN21ZbnZpc2F6b1E
1. Download the file above.
2. Extract the zip contents.
3. Plug your ME375CL tablet in to pc via usb cable.
4. Make sure you have enabled Developer Mode and allowed USB Debugging first!
5. Open the folder you extracted and double click the "Root-One-Click.cmd" file.
6. It should reboot to fastboot mode and flash the needed files and then reboot again.
You should now have root access. Verify this by installing a root checker app from the play store. Keep in mind, it may say root not installed on the first run. Sometimes it will take a moment for superuser to initially run or prompt for access.
Side note: the root uninstall did not seem to work, got an error...but oh well, the point is to have root!
Thanks go to @little_pindos for finding this file...you are a rockstar!
Anyone get xposed on LP?
ATT Boot Up Sound
Tired of the ATT boot sound? If you used the rooting method above, then you can get rid of the annoying ATT startup sound by doing the following:
1. Install a Root Browser app (I recommend Rom Toolbox Pro, it has a built in file manager)
2. Navigate to the following path:
root/system/media
3. Find the file named "powerup.wav"
4. Simply rename the file by adding .bak to the end (ex - powerup.wav.bak)
5. Make sure it took the name change (some file managers have issues with that)
6. Reboot and see if it got rid of the sound!
You can also use your own startup sounds as long as they are in a .wav format, I believe. Make sure that the name of the file is powerup.wav.
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
TimmyP said:
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
Click to expand...
Click to collapse
I'll have to try that!
AT&T no longer has updates in system for this tablet
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
AT&T removed the last update for this tablet months ago and no longer supports it. ASUS states AT&T has all the updates. Total cluster.
Per https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery installing Magisk as recovery due to No RAMDISK on my Moto E6.
"If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition.
Click to expand...
Click to collapse
The phone was successfully unlocked per Motorola Unlock Your Bootloader.
Magisk_Manager generated magisk_Patched Img. Recovery_Image was extracted on PC with WinRAR from Get Droid Tips, Moto E6 Stock Collection, current download matches my Moto E6 build#, PPB29.73-81. My model is XT2005-5. To avoid corruption, I used ADB, not MTP to transfer files. ADB pushed WinRAR Extracted recovery image, and ADB pulled magisk_Patched image.
However, the Execution of ADB Fastboot flash recovery was "Image not signed or corrupt" per the following log:
Code:
C:\adb>fastboot flash recovery C:\adb\magisk_patched_k54ii.img
target reported max download size of 535822336 bytes
sending 'recovery' (16341 KB)...
OKAY [ 0.533s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.285s]
finished. total time: 0.820s
Why am I getting a corrupt image? Does anyone recommend a better Stock Recovery-Image source, perhaps where I can confirm the hashtag of the download and image extraction? TWRP does not seem to be an option for MotoE6/ No-RAMdisk devices.
I don't recommend images from Get Droid Tips, Moto E6 Stock Collection while they have the build numbers for the downloads, they did not show that there are various model numbers for the Moto E6. My guess is this is the likely cause of the "corrupt" image message from my flash recovery attempt.
I will use a stock image from https://mirrors.lolinet.com/firmware/moto/surfna/official/
kem827 said:
Per https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery installing Magisk as recovery due to No RAMDISK on my Moto E6.
The phone was successfully unlocked per Motorola Unlock Your Bootloader.
Magisk_Manager generated magisk_Patched Img. Recovery_Image was extracted on PC with WinRAR from Get Droid Tips, Moto E6 Stock Collection, current download matches my Moto E6 build#, PPB29.73-81. My model is XT2005-5. To avoid corruption, I used ADB, not MTP to transfer files. ADB pushed WinRAR Extracted recovery image, and ADB pulled magisk_Patched image.
However, the Execution of ADB Fastboot flash recovery was "Image not signed or corrupt" per the following log:
Code:
C:\adb>fastboot flash recovery C:\adb\magisk_patched_k54ii.img
target reported max download size of 535822336 bytes
sending 'recovery' (16341 KB)...
OKAY [ 0.533s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.285s]
finished. total time: 0.820s
Why am I getting a corrupt image? Does anyone recommend a better Stock Recovery-Image source, perhaps where I can confirm the hashtag of the download and image extraction? TWRP does not seem to be an option for MotoE6/ No-RAMdisk devices.
Click to expand...
Click to collapse
I don't know why this occurs, but it's "normal". What the installer guide doesn't tell you is:
- when you flash the patched recovery, you can't then use fastboot to get to recovery mode (well, you can...but it doesn't work). Instead, you MUST use the fastboot navigation keys (vol up/down and power) to go to recovery. When you do that, you'll boot the whole system into a rooted state (you won't see a recovery menu of any kind).
- at least on my phone, when you do this you are rooted for exactly one session. Next time you boot, the recovery image you flashed will be replaced with the "factory" original one. There is a work-around for this, but that's the behavior.
- if you are trying to install EdXposed, I don't believe you can do so just with the recovery-image method. You have to install the whole of Magisk (many MB) and I haven't figured out how to do this yet. (many, many false starts...)
dav0dav0 said:
I don't know why this occurs, but it's "normal". What the installer guide doesn't tell you is:
- when you flash the patched recovery, you can't then use fastboot to get to recovery mode (well, you can...but it doesn't work). Instead, you MUST use the fastboot navigation keys (vol up/down and power) to go to recovery. When you do that, you'll boot the whole system into a rooted state (you won't see a recovery menu of any kind).
- at least on my phone, when you do this you are rooted for exactly one session. Next time you boot, the recovery image you flashed will be replaced with the "factory" original one. There is a work-around for this, but that's the behavior.
- if you are trying to install EdXposed, I don't believe you can do so just with the recovery-image method. You have to install the whole of Magisk (many MB) and I haven't figured out how to do this yet. (many, many false starts...)
Click to expand...
Click to collapse
Ok, Thanks. Looks like my attempt to flash ( from Get Droid Tips, Moto E6 Stock Collection, ) was not the correct Moto E6 model. Phone boots still to the factory, and not rooted, but has a "bad key" error.. Boot to Recovery just responds "no command"
I did find now download the correct image from https://mirrors.lolinet.com/firmware/moto/surfna/official/ (matched by the Correct Moto E6 XT2005 model and build) but now ADB does not want to push or pull files. Unsure how to proceed.
I got my "stock ROM" by using Moto's "Rescue and Smart Assistant" tool -- it interrogates the phone, and lets you download the correct ZIP file automatically. Obviously, you do'nt want to actually install the ZIP -- you just want it downloaded. It puts the ZIP into a location it discloses, so you can find it. ;-)
Was ADB pushing/pulling files before? That's really weird if it did...but in any case, when the phone is booted to the normal system you can just copy the files over to the phone via the standard USB file sharing connection. If that's not working, you may need to reainstall the USB drivers on your PC. Don't forget to enable USB file sharing on the phone!
dav0dav0 said:
I got my "stock ROM" by using Moto's "Rescue and Smart Assistant" tool -- it interrogates the phone, and lets you download the correct ZIP file automatically. Obviously, you do'nt want to actually install the ZIP -- you just want it downloaded. It puts the ZIP into a location it discloses, so you can find it. ;-)
Was ADB pushing/pulling files before? That's really weird if it did...but in any case, when the phone is booted to the normal system you can just copy the files over to the phone via the standard USB file sharing connection. If that's not working, you may need to reainstall the USB drivers on your PC. Don't forget to enable USB file sharing on the phone!
Click to expand...
Click to collapse
ADB was pushing and pulling. I found the XDA posting that might help solve this official-tool-windows-adb-fastboot-and-drivers-15-seconds-ADB-installer-v1-4-3.2588979/. I'll update my drivers per the video found here, and try again.
While deleting some old Samsung Drivers was probably necessary, the error remained. Searched and found that the directory "/SD Card" is incorrect, even though topjohnwu.github failed to explain that "SD Card" is not the same folder as seen in the windows USB Link. It is the Internal SD Card which the ADB uses, which I find on windows at "Internal Shared Storage/Download". Once I moved the file on my phone to that folder , I was able to Pull the file using the command "ADB Pull \Sdcard\download.."
Reflashed my patched majesk recovery image. But, I can not boot recovery. Fastboot gives me a "no command" message. Screen always displays "bad key" on any boot. Holding power and tapping upkey does nothing in attempt to Boot to Recovery.
kem827 said:
Reflashed my patched majesk recovery image. But, I can not boot recovery. Fastboot gives me a "no command" message. Screen always displays "bad key" on any boot. Holding power and tapping upkey does nothing in attempt to Boot to Recovery.
Click to expand...
Click to collapse
I believe that the "bad key" message will occur whenever you have an unlocked bootloader. There is a way to hide it (search within XDA forums, you'll find several posts), but I leave it as is so I get a positive indicator of where I really am.
You say "Fastboot gives me a 'no command' message": I think what you mean is "when I go from Fastboot to Recovery mode, a get a 'no command' message." -- because the only time I've ever seen that message is under the Android-robot icon, which indicates "you're in stock recovery mode." When you are there, you should be able to get to the command menu by clicking power-on and volume-up simultaneously. If you don't, do a power cycle and try again.
You'll know you've booted the root mode when you don't see the "bad key" message, but instead see something like "Unsigned or corrupt image" when you go into recovery mode (and you won't see the normal Android icon or "no command" message).
In my experience with this phone, if you are in bootloader and use your PC to get you to recovery mode (fastboot reboot recovery from the command line), it may not work. The only way to reliably get into real recovery mode is to do a power cycle on the phone, go into fastboot, and then use the phone's buttons to get to recovery.
Also note that if all that you have done is the Magisk modify-recovery-image strategy, you get one (and only one) attempt to run as rooted. Any time you go thru a power-on reset of the phone, your modded-recovery image will be erased and replaced with the factory one.
In my various runs, I've determined that once you've achieved root access you can soft-reboot the phone and remain in root. Anything you install there will survive soft-reboots. But if you do a hard reboot, next time you go into root you may have to reinstall EdXposed and supporting libraries, and reactivate stuff for everything to work.
Sadly, the Xposed module I was doing all this for doesn't seem to work under EdXposed, even though it's supposed to. So it was a days-long wild goose chase.
dav0dav0 said:
I believe that the "bad key" message will occur whenever you have an unlocked bootloader. There is a way to hide it (search within XDA forums, you'll find several posts), but I leave it as is so I get a positive indicator of where I really am.
You say "Fastboot gives me a 'no command' message": I think what you mean is "when I go from Fastboot to Recovery mode, a get a 'no command' message." -- because the only time I've ever seen that message is under the Android-robot icon, which indicates "you're in stock recovery mode." When you are there, you should be able to get to the command menu by clicking power-on and volume-up simultaneously. If you don't, do a power cycle and try again.
You'll know you've booted the root mode when you don't see the "bad key" message, but instead see something like "Unsigned or corrupt image" when you go into recovery mode (and you won't see the normal Android icon or "no command" message).
In my experience with this phone, if you are in bootloader and use your PC to get you to recovery mode (fastboot reboot recovery from the command line), it may not work. The only way to reliably get into real recovery mode is to do a power cycle on the phone, go into fastboot, and then use the phone's buttons to get to recovery.
Also note that if all that you have done is the Magisk modify-recovery-image strategy, you get one (and only one) attempt to run as rooted. Any time you go thru a power-on reset of the phone, your modded-recovery image will be erased and replaced with the factory one.
In my various runs, I've determined that once you've achieved root access you can soft-reboot the phone and remain in root. Anything you install there will survive soft-reboots. But if you do a hard reboot, next time you go into root you may have to reinstall EdXposed and supporting libraries, and reactivate stuff for everything to work.
Sadly, the Xposed module I was doing all this for doesn't seem to work under EdXposed, even though it's supposed to. So it was a days-long wild goose chase.
Click to expand...
Click to collapse
Thanks for you help. I finally got a correct flash and boot to a rooted recovery. Looks like Top Johns' Magisk Instruction Page needs some corrections: Like explaining that "SDCard" shows as [internal storage] on the PC and that the external Storage is the [SD Card] directory. He fails to tell to rename the magisk_patched file to "recovery. img" before flashing it. (An obvious error but easy to overlook when you are following an unfamiliar command syntax) . The "bad key" message and "corrupt signature" message explanation is useful info too. He fails to let you know how to even check for a successful root
kem827 said:
Thanks for you help. I finally got a correct flash and boot to a rooted recovery. Looks like Top Johns' Magisk Instruction Page needs some corrections: Like explaining that "SDCard" shows as [internal storage] on the PC and that the external Storage is the [SD Card] directory. He fails to tell to rename the magisk_patched file to "recovery. img" before flashing it. (An obvious error but easy to overlook when you are following an unfamiliar command syntax) . The "bad key" message and "corrupt signature" message explanation is useful info too. He fails to let you know how to even check for a successful root
Click to expand...
Click to collapse
And to add to the fun...Magisk Manager has/had a bug where it will tell you that your phone *doesn't* have a RAMdisk but it actually does....sometimes. So you might try to do the boot.img patch instead of the recovery.img one--that would give you a permanent root, rather than a transitory one. I didn't bother to check that out, as the whole reason I was rooting was to use an Xposed module that doesn't seem to work.
Let me know if you try that strategy out and it works...
kem827 said:
Thanks for you help. I finally got a correct flash and boot to a rooted recovery. Looks like Top Johns' Magisk Instruction Page needs some corrections: Like explaining that "SDCard" shows as [internal storage] on the PC and that the external Storage is the [SD Card] directory. He fails to tell to rename the magisk_patched file to "recovery. img" before flashing it. (An obvious error but easy to overlook when you are following an unfamiliar command syntax) . The "bad key" message and "corrupt signature" message explanation is useful info too. He fails to let you know how to even check for a successful root
Click to expand...
Click to collapse
The instructions assume that you are somewhat familiar with Android, adb and fastboot. There's plenty of info and guides on that around the web, so it would be redundant for John to add that too (and the instructions would become way too long).
There are also many devices specific things that he's never gonna be able to cover. The fractured nature of Android is just too much for that...
If you have suggestions though, you can always open a PR on GitHub with your proposed changes and clarifications.
dav0dav0 said:
Magisk Manager has/had a bug where it will tell you that your phone *doesn't* have a RAMdisk but it actually does....sometimes
Click to expand...
Click to collapse
That's not a bug with Magisk, but yet another issue with Android's fractured ecosystem. John actually covers that in his documentation. Check this page, and in particular the last paragraph:
https://topjohnwu.github.io/Magisk/boot.html
I have pixel 4 xl in stock rom.
No matter what i do one partition stays corrupted.
I have flashed rom on partition A with wiping out whole device hoping it would restore but partition B was still corrupted. So i change partition in fastboot mode and tried to flash stock rom with flash all.sh without any kind of modification Hoping it would fix it and device booted but while doing so it corrupted partition A. Than i tried using googles online flashing tool with wiping my device but still experienced same issue. Anyone have any idea what might have gone wrong or how to restore both partition.
I can not use magisk update on inactive partition because i dont see that option, maybe because of this I'm also unable to use viper4android for some reason. Please if anyone have same issue or had same issue let me know how to solve it
Scytherblack said:
I have pixel 4 xl in stock rom.
No matter what i do one partition stays corrupted.
I have flashed rom on partition A with wiping out whole device hoping it would restore but partition B was still corrupted. So i change partition in fastboot mode and tried to flash stock rom with flash all.sh without any kind of modification Hoping it would fix it and device booted but while doing so it corrupted partition A. Than i tried using googles online flashing tool with wiping my device but still experienced same issue. Anyone have any idea what might have gone wrong or how to restore both partition.
I can not use magisk update on inactive partition because i dont see that option, maybe because of this I'm also unable to use viper4android for some reason. Please if anyone have same issue or had same issue let me know how to solve it
Click to expand...
Click to collapse
Without cat logs, errors, pics, or system clarity on what was done to the partitions to land you here, we cant really help. I suspect tho, you may have tried Android 12 preview, and you are stuck now?
If not, and 12 wasnt used, explain what's been done and how you feel the partition is broken.
GROOVYJOSHCLARK said:
Without cat logs, errors, pics, or system clarity on what was done to the partitions to land you here, we cant really help. I suspect tho, you may have tried Android 12 preview, and you are stuck now?
If not, and 12 wasnt used, explain what's been done and how you feel the partition is broken
Click to expand...
Click to collapse
GROOVYJOSHCLARK said:
Without cat logs, errors, pics, or system clarity on what was done to the partitions to land you here, we cant really help. I suspect tho, you may have tried Android 12 preview, and you are stuck now?
If not, and 12 wasnt used, explain what's been done and how you feel the partition is broken.
Click to expand...
Click to collapse
I was not using any other rom but i was trying to install twrp recovery by first booting into it, first thing i noticed was i couldn't decrypt my phone even though i put the right password, so i went back to bootloader and tried to flash stock boot img to see if i could get into twrp but same thing happened so i thought let me change to boot partition and try, but it wasn't even booting into partition B it shows me google logo and than boot back to bootloader and than no matter what i restart or power off it goes straight back to bootloader, unless i change back to partition A.
So i left twrp behind thinking i can still flash whatever i like using commands but to repair partition B i used command "fastboot --set-active=b" and than i flashed latest og stock file with flash-all.bat.
And phone booted into partition B but just to make sure i rebooted back to bootloader and tried changing partition again to A using "fastboot --set-active=a" and it booted into google logo and went back to bootloader and stuck.
So as you can see doen here i dont see option of updating using inactive partition,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So please let me know what logs so i can provide em here.
Thanks
Scytherblack said:
I was not using any other rom but i was trying to install twrp recovery by first booting into it, first thing i noticed was i couldn't decrypt my phone even though i put the right password, so i went back to bootloader and tried to flash stock boot img to see if i could get into twrp but same thing happened so i thought let me change to boot partition and try, but it wasn't even booting into partition B it shows me google logo and than boot back to bootloader and than no matter what i restart or power off it goes straight back to bootloader, unless i change back to partition A.
So i left twrp behind thinking i can still flash whatever i like using commands but to repair partition B i used command "fastboot --set-active=b" and than i flashed latest og stock file with flash-all.bat.
And phone booted into partition B but just to make sure i rebooted back to bootloader and tried changing partition again to A using "fastboot --set-active=a" and it booted into google logo and went back to bootloader and stuck.
So as you can see doen here i dont see option of updating using inactive partition, View attachment 5298203
So please let me know what logs so i can provide em here.
Thanks
Click to expand...
Click to collapse
Wait, back up, what are you trying to do now? Install MAGISK, or fix the partitions?
You noted the partition and slot issues, but then went into MAGISK. You do not need to select anything in MAGISK for boot or slots, you simply need to patch the boot.img (in the pic you posted), then patch the boot.img with magisk, then:
fastboot flash boot magisk_patched.img --> (whatever is saved to your download folder) FROM MAGISK app patching it.
You must use the patched boot.img (now renamed with MAGISK and the string it adds) and fastboot it, then boot normally and you are ROOT'd. Do not mess with slots when doing this process, just use the command I laid out once you patch it. MAGISK patching isnt the same as installing GAPPs and a ROM, you do not switch slots to install.
This is all assuming you are only trying to ROOT the device and not fix your issues with the partitions. If you want to fix the partition layout, use the flash-all with the -W left intact on both slots (I force it to reboot after it erases userdata), then boot into fastboot and change to slot B (first flash-all was done to slot A). Afterwards both slots are refreshed and you can go for it. Back EVETYTHING up first as you will lose everything but it will get you back in shape.
Dont bother installing TWRP, but I dont think its ready for 11 yet anyways (decryption) but I havent used TWRP in months. Fastboot it instead of installing it:
fastboot boot twrp-BLAHBLAHBLAH.img
GROOVYJOSHCLARK said:
Wait, back up, what are you trying to do now? Install MAGISK, or fix the partitions?
You noted the partition and slot issues, but then went into MAGISK. You do not need to select anything in MAGISK for boot or slots, you simply need to patch the boot.img (in the pic you posted), then patch the boot.img with magisk, then:
fastboot flash boot magisk_patched.img --> (whatever is saved to your download folder) FROM MAGISK app patching it.
You must use the patched boot.img (now renamed with MAGISK and the string it adds) and fastboot it, then boot normally and you are ROOT'd. Do not mess with slots when doing this process, just use the command I laid out once you patch it.
This is all assuming you are only trying to ROOT the device and not fix your issues with the partitions. If you want to fix the partition layout, use the flash-all with the -W left intact on both slots (I force it to reboot after it erases userdata), then boot into fasttboot and change to slot B (first flash-all was done to slot A). Afterwardss both slots are refreshed and you can go for it. BackEVETYTHING up first as you will lsoe everything but it iwll get you back in shape.
Dont bother installing TWRP, but I dont think its ready for 11 yet anyways (decryption) but I havent used TWRP in months. Fastboot it instead of installing it:
fastboot boot twrp-BLAHBLAHBLAH.img
Click to expand...
Click to collapse
I'm trying to fix my partition, but i show magisk because before this partition problem i had third method for monthly patch update for os NAMED INSTALL IN INACTIVE BOOT SLOT which have disappeared from my magisk
Scytherblack said:
I'm trying to fix my partition, but i show magisk because before this partition problem i had third method for monthly patch update for os NAMED INSTALL IN INACTIVE BOOT SLOT which have disappeared from my magisk
Click to expand...
Click to collapse
you are way past that now, when you flashed the boot.img manually from stock, you overwrote MAGISK TWRP and anything else you had in the boot partition. Patch the boot.img for your ROM (MAGISK), then fastboot it. Its the only way to get ROOT back with what you have done.
You F'd up the A partition when you tried to install TWRP, failed, then overwrote the boot partition manually.
To fix the partitions now, force SLOT A, factory firmware with -W left, then after A completes when erasing USERDATA, interrupt the boot (before SLOT A goes into OS), and switch to slot B, and redo.
GROOVYJOSHCLARK said:
Wait, back up, what are you trying to do now? Install MAGISK, or fix the partitions?
You noted the partition and slot issues, but then went into MAGISK. You do not need to select anything in MAGISK for boot or slots, you simply need to patch the boot.img (in the pic you posted), then patch the boot.img with magisk, then:
fastboot flash boot magisk_patched.img --> (whatever is saved to your download folder) FROM MAGISK app patching it.
You must use the patched boot.img (now renamed with MAGISK and the string it adds) and fastboot it, then boot normally and you are ROOT'd. Do not mess with slots when doing this process, just use the command I laid out once you patch it. MAGISK patching isnt the same as installing GAPPs and a ROM, you do not switch slots to install.
This is all assuming you are only trying to ROOT the device and not fix your issues with the partitions. If you want to fix the partition layout, use the flash-all with the -W left intact on both slots (I force it to reboot after it erases userdata), then boot into fastboot and change to slot B (first flash-all was done to slot A). Afterwards both slots are refreshed and you can go for it. Back EVETYTHING up first as you will lose everything but it will get you back in shape.
Dont bother installing TWRP, but I dont think its ready for 11 yet anyways (decryption) but I havent used TWRP in months. Fastboot it instead of installing it:
fastboot boot twrp-BLAHBLAHBLAH.img
Click to expand...
Click to collapse
I've been rooting my devices for 4-5 years amd been using magisk for last 3 years at least i remember how to do that but i just put magisk as example to show that there's something wrong with my boot partitions
GROOVYJOSHCLARK said:
you are way past that now, when you flashed the boot.img manually from stock, you overwrote MAGISK TWRP and anything else you had in the boot partition. Patch the boot.img for your ROM, then fastboot it. Its the only way to get ROOT back with what you have done.
Click to expand...
Click to collapse
So there is no way to get both of my partition back up and running??
Because now what happens is i cant update my phone with built in system update like normal phone, my phone always download the whole file of update like 2 GB instead of just the patch of few MBs.
Scytherblack said:
I've been rooting my devices for 4-5 years amd been using magisk for last 3 years at least i remember how to do that but i just put magisk as example to show that there's something wrong with my boot partitions
Click to expand...
Click to collapse
I am telling you exactly what happened and how to fix it, its not about how long anyone has been rooting anything. Pixels use A/B, so its much different than ever before. There is no recovery partition anymore, it now lives in the BOOT.
Redo the factory firmware on BOTH slots, and start over. Then you will be golden.
Scytherblack said:
So there is no way to get both of my partition back up and running??
Because now what happens is i cant update my phone with built in system update like normal phone, my phone always download the whole file of update like 2 GB instead of just the patch of few MBs.
Click to expand...
Click to collapse
No idea, because I have no idea what you truly did. I would redo both partitions, you mis-stepped with the manual flashing of the boot.img during the TWRP process so I have no idea how damaged it is now.
I also have no idea what ROM you are using, or if official, or even what internal updater you are using so its lacking info.
GROOVYJOSHCLARK said:
I am telling you exactly what happened and how to fix it, its not about how long anyone has been rooting anything. Pixels use A/B, so its much different than ever before. There is no recovery partition anymore, it now lives in the BOOT.
Redo the factory firmware on BOTH slots, and start over. Then you will be golden.
Click to expand...
Click to collapse
I have tried that in past so here's what i have tried to fix step by step.
1. I downloaded the latest Android 11 factory images from google developer site, unzip, connected my phone copied adb files to unzipped factory images and than used flash-all.bat
2.it flashed it on active slot A, since everything was wiped clean i had to boot device and enable developer options for adb support than rebooted back to bootloader.
3. Used command fastboot --set-active=B to change the boot slot and than install the factory images.
4. Booted enable developer options and rebooted back to bootloader to see if both boot A/B works and used command fastboot --set-active=A. tried to reboot it went to google logo for once and back to bootloader. Now whatever i do reboot or power off when it turns on it goes back to bootloader unless i switched back to Boot slot B
Now if i flash everything again on slot A it will work just fine but after slot A works fine slot B will be bricked or corrupted.
So i was thinking if i could manage to find EDL files for pixel 4 XL it would probably fix everything .
Scytherblack said:
I have tried that in past so here's what i have tried to fix step by step.
1. I downloaded the latest Android 11 factory images from google developer site, unzip, connected my phone copied adb files to unzipped factory images and than used flash-all.bat
2.it flashed it on active slot A, since everything was wiped clean i had to boot device and enable developer options for adb support than rebooted back to bootloader.
3. Used command fastboot --set-active=B to change the boot slot and than install the factory images.
4. Booted enable developer options and rebooted back to bootloader to see if both boot A/B works and used command fastboot --set-active=A. tried to reboot it went to google logo for once and back to bootloader. Now whatever i do reboot or power off when it turns on it goes back to bootloader unless i switched back to Boot slot B
Now if i flash everything again on slot A it will work just fine but after slot A works fine slot B will be bricked or corrupted.
So i was thinking if i could manage to find EDL files for pixel 4 XL it would probably fix everything .
Click to expand...
Click to collapse
Thats not how I laid it out. You are booting BEFORE doing slot B so its not repairing it to factory.
Why Emergency Download Mode? You replace the fastboot and all files needed to run and boot Android WITH the factory image. You do not need EDL, you are overthinking this a lot.
ALL you need to do is to successfully flash the FACTORY firmware with -W on BOTH slots before booting and its back to factory fresh. Do not use the web (chrome) version at all, that wont work to fix your issue, and do not use an OTA. ONLY use the factory firmware and reset both slots BEFORE the OS. Once slot B completes, let it boot, go through the OS, then prepare it for a ROM, or use ROOT with the stock OS.
Enabling ADB in dev options ONLY enables you to use ADB from a PC. You do NOT need to enable ADB in dev options to flash a firmware/TWRP/ROM.
Everything changed with A/B partitions, so a lot is different than how it used to be.
GROOVYJOSHCLARK said:
Thats not how I laid it out. You are booting BEFORE doing slot B so its not repairing it to factory.
Why Emergency Download Mode? You replace the fastboot and all files needed to run and boot Android WITH the factory image. You do not need EDL, you are overthinking this a lot.
ALL you need to do is to successfully flash the FACTORY firmware with -W on BOTH slots before booting and its back to factory fresh. Do not use the web (chrome) version at all, that wont work to fix your issue, and do not use an OTA. ONLY use the factory firmware and reset both slots BEFORE the OS. Once slot B completes, let it boot, go through the OS, then prepare it for a ROM, or use ROOT with the stock OS.
Enabling ADB in dev options ONLY enables you to use ADB from a PC. You do NOT need to enable ADB in dev options to flash a firmware/TWRP/ROM.
Everything changed with A/B partitions, so a lot is different than how it used to be.
Click to expand...
Click to collapse
Okay I'll try this Tonight thank you, I'll post the result
Scytherblack said:
Okay I'll try this Tonight thank you, I'll post the result
Click to expand...
Click to collapse
Trust me when I tell you this, I was VERY confused when I first got my Pixel 2XL with A/B (coming from an older HTC 10 that was a single slot). I was so used to having a recovery partition, single slot, and system (not system-less), that I knew all the ins and outs of Android, writing code / ROMs, ROOT, ETC., so I could advise from memory.
When A/B came along, I didn't have it until my 2XL, then 3XL, and now my 4XL so I had to learn it.
At first, I kept screwing up the device (almost exactly the scenario you are in). 1 slot worked, the other slot was F'd. It wasn't until I figured out how they actually worked, then it all made sense and why I kept damaging one or the other (or both slots). The slots are great for updates, but terrible for ROM development, and firmware flashing due to issues like this. It is no longer a simple, easy peasy process that is once was, BUT there is a light at the end of tunnel. Once you familiarize yourself with the A/B partitions, and how to recover from mistakes, or failed updates, or ROM install issues, you will become an Android A/B genius. It will make sense the more you use it, but there is a decent amount of changes to re-learn if/when coming from an older device so don't give up. You can recover from this with a factory firmware (assuming BOOTLOADER is truly unlocked which it sounds like it is), so keep at it.
I have had my 2XL and 4XL so bad, it wouldn't boot at times, but eventually you will figure it out and fix it. Factory images are a saving grace, they will undo the damage. My 3 XL is a verizon piece of junk (LOCKED BOOTLOADER) so it doesnt get used and sits brand new in the box waiting to be off lease and sold for the garbage it is. My 2XL/4XL were both bought outright from Google, my 3XL was a lease package my wife needed to sign up her daughter so I got a free 3XL I dont use (and wont use). I REFUSE to use anything from verizon with a locked BL. Its the main reason for Android, so why cripple it? F verizon, I hate them!
GROOVYJOSHCLARK said:
Trust me when I tell you this, I was VERY confused when I first got my Pixel 2XL with A/B (coming from an older HTC 10 that was a single slot). I was so used to having a recovery partition, single slot, and system (not system-less), that I knew all the ins and outs of Android, writing code / ROMs, ROOT, ETC., so I could advise from memory.
When A/B came along, I didn't have it until my 2XL, then 3XL, and now my 4XL so I had to learn it.
At first, I kept screwing up the device (almost exactly the scenario you are in). 1 slot worked, the other slot was F'd. It wasn't until I figured out how they actually worked, then it all made sense and why I kept damaging one or the other (or both slots). The slots are great for updates, but terrible for ROM development, and firmware flashing due to issues like this. It is no longer a simple, easy peasy process that is once was, BUT there is a light at the end of tunnel. Once you familiarize yourself with the A/B partitions, and how to recover from mistakes, or failed updates, or ROM install issues, you will become an Android A/B genius. It will make sense the more you use it, but there is a decent amount of changes to re-learn if/when coming from an older device so don't give up. You can recover from this with a factory firmware (assuming BOOTLOADER is truly unlocked which it sounds like it is), so keep at it.
I have had my 2XL and 4XL so bad, it wouldn't boot at times, but eventually you will figure it out and fix it. Factory images are a saving grace, they will undo the damage. My 3 XL is a verizon piece of junk (LOCKED BOOTLOADER) so it doesnt get used and sits brand new in the box waiting to be off lease and sold for the garbage it is. My 2XL/4XL were both bought outright from Google, my 3XL was a lease package my wife needed to sign up her daughter so I got a free 3XL I dont use (and wont use). I REFUSE to use anything from verizon with a locked BL. Its the main reason for Android, so why cripple it? F verizon, I hate them!
Click to expand...
Click to collapse
i got error saying failed! partition should be flash in fastbootd
and now my phone is stuck on bootloop
Scytherblack said:
i got error saying failed! partition should be flash in fastbootd
and now my phone is stuck on bootloop
Click to expand...
Click to collapse
Again, we need more info. You did something wrong because it automatically reboots into fastboot during the process to update the firmware.
We need to find out why it didn't it reboot into fastboot so if you prevented that from happening, don't. Start over and let it go through the process. The batch file automatically reboots to fastboot during the system image push (so if it didnt do that), then its your reason for the boot failure.
GROOVYJOSHCLARK said:
Again, we need more info. You did something wrong because it automatically reboots into fastboot during the process to update the firmware.
We need to find out why it didn't it reboot into fastboot so if you prevented that from happening, but don't. Start over and let it go through the process.
Click to expand...
Click to collapse
Update i did manage to get it all installed without me interfering. But still the same issue only one partition works.
And you did both slots A/B with the firmware? Can you confirm you are on the absolute latest ADB and drivers? Also run this command to see if you are stuck in a snapshot update and cant write:
fastboot snapshot-update cancel
Then try to redo the slot thats failing. I have had something like this happen a long time ago but not quite the same. It was due to the snapshot. I cant remember if this needs to be run after switching slots so try it, and if it doesnt do anything, then switch to A, run it, switch to B, and run it, then try the firmware over again on the failed slot.
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8833 KB)...
OKAY [ 0.327s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version c2f2-0.3-7062597
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition logfs
OKAY [ 0.269s]
finished. total time: 0.597s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.071s
target reported max download size of 268435456 bytes
sending 'radio_a' (82708 KB)...
OKAY [ 2.127s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g8150-00082-210106-B-7065218
(bootloader) Flashing partition modem_a
OKAY [ 0.487s]
finished. total time: 2.617s
rebooting into bootloader...
OKAY [ 0.070s]
finished. total time: 0.071s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.396s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.040s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (782 MB) to disk... took 8.684s
archive does not contain 'system.sig'
extracting system_other.img (23 MB) to disk... took 0.162s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.006s
archive does not contain 'vbmeta.sig'
extracting vendor.img (730 MB) to disk... took 7.530s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: c2f2-0.3-7062597
Baseband Version.....: g8150-00082-210106-B-7065218
Serial Number........: 9A231xxxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.070s]
checking version-bootloader...
OKAY [ 0.069s]
checking version-baseband...
OKAY [ 0.069s]
sending 'boot_a' (65536 KB)...
OKAY [ 1.549s]
writing 'boot_a'...
OKAY [ 0.336s]
sending 'dtbo_a' (8192 KB)...
OKAY [ 0.292s]
writing 'dtbo_a'...
OKAY [ 0.107s]
sending sparse 'system_a' 1/4 (262140 KB)...
OKAY [ 5.982s]
writing 'system_a' 1/4...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 8.839s
this is what i get when i tried to install factory images using flash-all.bat
GROOVYJOSHCLARK said:
And you did both slots A/B with the firmware? Can you confirm you are on the absolute latest ADB and drivers? Also run this command to see if you are stuck in a snapshot update and cant write:
fastboot snapshot-update cancel
Then try to redo the slot thats failing. I have had something like this happen a long time ago but not quite the same. It was due to the snapshot. I cant remember if this needs to be run after switching slots so try it, and if it doesnt do anything, then switch to A, run it, switch to B, and run it, then try the firmware over again on the failed slot.
Click to expand...
Click to collapse
fastboot: usage: unknown command snapshot-update this is what i got for snap shot