Posted in the general thread, but no replies.
I seem to have softbricked my phone by rooting then applying the OTA update. I've tried re-rooting, wiping cache, factory resetting, etc., and nothing seems to work. Following the steps in http://forum.xda-developers.com/zenf...d-zf2-t3127835 I can get to step 7, but when I submit any of the commands I get this:
Code:
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14822 KB)...
OKAY [ 0.666s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.839s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.545s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 0.716s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11868 KB)...
OKAY [ 0.522s]
writing 'boot'...
FAILED (remote: Permission denied
)
finished. total time: 0.694s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Permission denied)
finished. total time: 125.564s
It wasn't clear if it was a windows permission error or an android permission error, so I tried an admin command prompt but that didn't change anything.
Any suggestions? Thanks in advance
Bump in hopes of a solution
And another bump, any help would be greatly appreciated
I'm wondering if it has to do with having a bootloader installed being over a certain version. I had 2 Asus Zenfone 2s and I get the same error messages. I can't remember what my first ZF2 had for firmware to start, but I was a dummy and updated it all the way to 2.20.40.90 stock. Everytime I tried to write via fastboot, Permission Denied. My new ZF2 on 2.20.40.59 also has the same problem. I feel like Asus patched the ability to fastboot these files or something. Running CMD as Administrator doesn't help the situation.
bumping because I'm having the same issue, coming back to stock after having CM12.1
As easy as it sounds, the solution was just flashing the newest software from the ASUS website, using adb sideload UL-Z00A-WW-2.20.40.97-user.zip
I can't imagine why I wouldn't have done that sooner, but it fixed it. Whether that worked due to something else I did, i have no idea, but my phone is now working
I had that before but fortunately I was able to fix it.
Get a microsd, but a firmware from Asus website, make sure that it is the correct one if you have WW then download WW, download it from Asus website or it will not work.
Then put the micro sd on the phone., rename the file MOFD_UPDATE don't put zip cause it will be doubled.
Boot to bootloader then boot to recovery. Automatically the phone will restore itself.
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
I was also unable to mount the SD card, might have something to do with MOFD not being mapped.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
KylarBStern said:
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
ebanreb37 said:
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
I already tried it, I wrote in my post that I tried it. And it didn't work.
KylarBStern said:
I already tried it, I wrote in my post that I tried it. And it didn't work.
Click to expand...
Click to collapse
SD card MUST be FAT32 or 32gb or less. If you are using anything else it won't detect the sd card.
Cheers...
Ok it's been a while since I've tried anything with this phone and just now I did what you said, copied the firmware file which I downloaded from ASUS to a 2GB sd card formatted in fat32, rebooted to recovery phone applied the update sucessfully and restarted but I am still stuck in bootloop ? I tried every method so I asume the phone is ****ed and I should send it back for RMA ?
Related
Hi,
I have a serious problem. My phone for some reason was working fine, but all the sudden is now stuck in HBOOT.
i have tried recovery but the phone would just shut itself down. i couldn't not use adb even though before the phone went into this state, i turned the USB debugging mode on
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
please help , many thanks
Bump, I'm having the same problem on my tmobile m8
mmmgosu said:
Hi,
I have a serious problem. My phone for some reason was working fine, but all the sudden is now stuck in HBOOT.
i have tried recovery but the phone would just shut itself down. i couldn't not use adb even though before the phone went into this state, i turned the USB debugging mode on
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
please help , many thanks
Click to expand...
Click to collapse
raphi809 said:
Bump, I'm having the same problem on my tmobile m8
Click to expand...
Click to collapse
What versions of the M8 do you have?
EddyOS said:
What versions of the M8 do you have?
Click to expand...
Click to collapse
I have a t-mobile m8, I actually started a thread over there http://forum.xda-developers.com/tmobile-htc-one-m8/help/m8-bricked-soloution-t2818678 but so far no answers either
raphi809 said:
I have a t-mobile m8, I actually started a thread over there http://forum.xda-developers.com/tmobile-htc-one-m8/help/m8-bricked-soloution-t2818678 but so far no answers either
Click to expand...
Click to collapse
In which case stick to your thread as opposed to jumping on to others, makes it easier to follow
EddyOS said:
In which case stick to your thread as opposed to jumping on to others, makes it easier to follow
Click to expand...
Click to collapse
Yes, if you have already started a thread asking for help, don't jump around.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
mmmgosu said:
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
Click to expand...
Click to collapse
What response do you get for:
fastboot devices
If it returns the device ID, than try:
fastboot erase cache
Then try to flash recovery again.
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
when i tried fastboot devices it returns an ID
but when i tried
fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
i have at&t
Maybe try to flash one of the modded hboots?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hawkysoft said:
Maybe try to flash one of the modded hboots?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do i do that?
fastboot oem rebootRUU
fastboot flash zip name_of.zip
fastboot reboot-bootloader
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hard to help you if you do not even bother to answer all the questions posed to you. As I asked earlier:
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
redpoint73 said:
Hard to help you if you do not even bother to answer all the questions posed to you. As I asked earlier:
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
Click to expand...
Click to collapse
I tried factory reset but it doesn't seem to be doing anything, just a white screen with android picture.
what do you mean by " corrupts the internal memory on modded devices?"
i tried
fastboot oem rebootRUU
but it says ...
(bootloader) [DEBUG] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(560): error 2
(bootloader) Start Verify: 3
(bootloader) [DEBUG] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.018s]
finished. total time: 0.018s
question, can i flash TWRP with 0p6bimg.zip?
If yes, can anyone provide the file?
Thanks
mmmgosu said:
I tried factory reset but it doesn't seem to be doing anything, just a white screen with android picture.
what do you mean by " corrupts the internal memory on modded devices?"
Click to expand...
Click to collapse
It means you should never ever do that (factory reset in bootloader) if bootloader unlocked, rooted, etc.. Only within the OS Settings or in recovery.
What this means, is that on a stock device, factory reset in bootloader works normally; but on a modded (rooted, etc.) device this corrupts the internal memory and renders it unable to be read or written to. This is probably why can't wipe cacher, install custom recovery, reboot RUU, etc (all are giving you errors reading data; and I think this is the reason why).
Connect the phone to a Windows PC (sorry if that is not what you use, its all I know) and use Device Manager to format the phone's internal memory. Once its formatted try again to wipe cache and flash custom recovery again.
This is great info to tuck away for future reference. How should the memory be formatted? FAT32 or exFAT?
Sent from my Nexus 10
bruce7373 said:
How should the memory be formatted? FAT32 or exFAT?
Click to expand...
Click to collapse
FAT32.
redpoint73 said:
It means you should never ever do that (factory reset in bootloader) if bootloader unlocked, rooted, etc.. Only within the OS Settings or in recovery.
What this means, is that on a stock device, factory reset in bootloader works normally; but on a modded (rooted, etc.) device this corrupts the internal memory and renders it unable to be read or written to. This is probably why can't wipe cacher, install custom recovery, reboot RUU, etc (all are giving you errors reading data; and I think this is the reason why).
Connect the phone to a Windows PC (sorry if that is not what you use, its all I know) and use Device Manager to format the phone's internal memory. Once its formatted try again to wipe cache and flash custom recovery again.
Click to expand...
Click to collapse
How exactly does one format the phone's internal memory via Device Manager?
adriankeith said:
How exactly does one format the phone's internal memory via Device Manager?
Click to expand...
Click to collapse
Couldn't actually tell you "exactly" myself as I haven't personally had to do it. But I know its been given as advice many times, and reported to work (at least for some instances of corrupted internal memory or can't mount memory).
In brief, open Device Manager, browse to the device/internal memory, and try to find the option to format FAT32.
Ok, I'm in the same pickle as person above. Let me just post the state the phone was in before everything happened. Unlocked bootloader, s-on, Android revolution HD installed (4.4.3). Friend tried to get back to stock and now the phone is stuck in hboot. Things done to phone: bootloader relocked, tried to change tampered flag without success, flashed stock recovery and boot image. Fastboot devices returns Id, storage is not recognized, adb commands do not work. I think he also tried to do factory reset while in hboot. Just stumbled upon this format memory thing, will do it once I get home. What are the steps after, can I just flash the correct ROM.zip or some moded hboot? If you can just point me in right direction I would very much appreciate it, thanks. Also if you need any additional info just ask for it
Similar problem here also,
I could really use some help guys! The new GPE 6.0 images are out on XDA. http://forum.xda-developers.com/htc...uu-m8-google-play-edition-5-1-lmy470-t3226765
I did a full wipe then I put on the rom using the zip file first through TWRP and it did install but the radio drivers failed.
So I then downloaded the system img file ruu and renamed it to 0P6BIMG.zip and now it is just stuck in a loop and will not boot into the Operating system. It will just freeze at the White HTC logo.
I press the power button and the volume up button to reset the device then push the power button and volume down button to get into the bootloader the bootloader instantly selects Hboot and starts loading up the 0P6BIMG.zip. The phone then procedes to give me the highlighted HBoot option and the message "Press <POWER> to reboot." Which then reboots right into the White HTC loading screen.
The phone is unlocked and has s-on. I have tried using ADB commands but cannot get an ID with ADB devices command.
Can someone help a brotha out?
Hi guys, posted this under the TWRP thread but realised it might be a more general problem
ISSUE: I believe I bricked the phone or bootloop (sorry not familiar with terminology). After the splash screen the word ASUS shows with a never ending circle loading sign under it. I can't enter recovery using Power + Vol down
BACKGROUND: I am having some issues after doing the Tethered Recovery. I am rooted and have bootloader unlocked. Once I used cai_dat_CWM.bat and was in recovery, I tried to flash the clean rom HarfainX, but before I did, I did a wipe of Cache and it said formatting cache but after 10 minutes didnt load. So I turned off the phone, now it hangs on the ASUS screen. I can enter fast boot, but I cant enter recovery mode.
Can anyone help me in getting it back running again?
Update:
Tried doing a wipe through fastboot -w
and got the following results:
Erasing 'userdata' OKAY
Sending 'userdata' OKAY
Writing 'userdata' FAILED (remote: flash_cmds error!)
Thanks
You should've waited.
Posted using my phone.
jose makalolot said:
You should've waited.
Posted using my phone.
Click to expand...
Click to collapse
I did wait it just didn't do anything for about 10 minutes.
I'm trying to sideload using ADB the stock rom from ASUS / Garbage free ROM by Harfain X and I am getting:
adb.exe sideload update.zip
loading: update.zip
error: device not found
fastboot update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
Anyone can offer suggestions?
...Flashed untethered TWRP... fixed the problem .. thanks TheSSJ for creating it
Hi all,
My nexus 7 2013 wifi edition got stuck in bootloop. The tablet just crashed when I went in the apps section in the settings menu. Since then it is stuck in a bootloop and can't boot anymore. The tablet was running a kitkat version of android and was rooted.
I tried wiping cache/dalvik/data, nothing works and nothing is able to mount. It also shows the 0mb internal memory. Wiping doesn't work so I can't get rid of the 0mb. With the nexus toolkit it doesn't let me flash anything or return it to stock
I had TWRP 2.6.3 installed and tried updating it to 2.8.4 but the flashing failed.
It was able to send the recovery file to the tablet but then I got a "remote: flash write failure".
I am running out of options here. What can I do. TWRP flash seems to have failed and if I try to enter recovery now it also gets stuck in the bootlogo.
I hope someone can help me further.
Hello, and thanks for using XDA Assist.
There is a one click factory restore tool that you can find here, that has helped me in the past when I hard bricked my Nexus 7 a couple of years ago. It should work for you too.
Good luck!
Thank you for your reply. I tried the tool.
What I get, when using the bricked NEXUS.bat:
Code:
08e80e7d fastboot
sending 'bootloader' <3911 KB>...
OKAY [ 0.202s ]
writing 'bootloader'...
FAILED <remote: flash write failure>
finished. total time: 90.748s
rebootin into bootloader...
OKAY [ 0.009s ]
finished. Total time: 0.011s
erasing 'system'...
It will stick on erasing system.
Also after performing these steps, I can not boot into recovery anymore. TWRP does not start and there is also no android puppet on its back
Wrong advice. Emmc problem for which there is no remedy yet.
Th same issue happened to me tonight using my 7. I'm getting the same message when I try to flash the stock image isingbthe "flash-all" command.
Rick
Memke said:
Thank you for your reply. I tried the tool.
What I get, when using the bricked NEXUS.bat:
Code:
08e80e7d fastboot
sending 'bootloader' <3911 KB>...
OKAY [ 0.202s ]
writing 'bootloader'...
FAILED <remote: flash write failure>
finished. total time: 90.748s
rebootin into bootloader...
OKAY [ 0.009s ]
finished. Total time: 0.011s
erasing 'system'...
It will stick on erasing system.
Click to expand...
Click to collapse
I copied your log to my thread as an example of symptoms of failed, unwritable eMMC flash memory.
Today I contacted Asus and was given an RMA #. I believe this to be a hardware failure also because it happened out of no where on me. I was watching a video fine, went to reboot the tablet and it went to bootloader loop.
C5Longhorn said:
Today I contacted Asus and was given an RMA #. I believe this to be a hardware failure also because it happened out of no where on me. I was watching a video fine, went to reboot the tablet and it went to bootloader loop.
Click to expand...
Click to collapse
May I ask you to post eMMC brand when you get a replacement from ASUS?
Yes, I will if I go through with it and get it back.
Sent from my Nexus 6P using Tapatalk
k23m said:
May I ask you to post eMMC brand when you get a replacement from ASUS?
Click to expand...
Click to collapse
I posted in the other thread, but I got a tablet back from ASUS this week. I got the following chip info from SD Insight.
Hynix
HBG4e
31 GB
Jun 2013
Finally Found a Fix
So Basically below are the steps that I have followed to fix this issue on my TAB.
**NOTE: Replace ****?? with www
Hardware fix (In case due to internal wire contact issues .. this may happen due to drops )
Fix 1: (Temp)
- Follow the instructions provided by ****??.youtube.com/watch?v=0C5tpeNA4xg
Fix 2: ( Depend on analysis from Fix1.. this could be a more permanent fix)
- Is Fix 1 works then there is a high probability that you had dropped the device @ least once. I guess build quality by ASUS is kind of dodgy for Nexus 7 2013 Model.
For me this was caused due to Touchscreen Digitizer Cable, this could be due to frequent drops of Tab (Refer: ****??.ifixit.com/Store/Parts/Nexus-7-2nd-Gen-Wi-Fi-LCD-Screen-and-Digitizer-Assembly-/IF235-039-1 The Cable is Silver Color)
Power off the TAB, Disconnect and reconnect the cable (this also fixed other issue for me... gyro was not working properly in my device) . Now power ON the device.
Software Fix
Fix 3( If the issue is not related to HW, Note, Following below instruction will wipe your device Data)
- Download the latest Rom image from ****??developers.google.com/android/images#razor (for Wifi Version)
- Follow the Steps ****??developers.google.com/android/images#instructions
PS: There are many tutorials in youtube for flashing ROM/Recovering Data from TAB. Please search and Refer . Please add Https for all the link as I can post full link here.
HOPE This works for you
I keep getting this error when flashing the stock image, anyone knows what this is about? Cant reflash the image, I am on stock everything..
Flashing boot separately works..
I am on the V build..
Also, cant change active slot from fastboot.. But booted twrp and changed the slot fine...
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boota' (26405 KB)...
OKAY [ 0.731s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.186s
when flashing system image getting this..
C:\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'systema' 1/3 (521974 KB)...
OKAY [ 13.026s]
writing 'systema' 1/3...
FAILED (remote: partition table doesn't exist)
finished. total time: 13.119s
Update your ADB/fastboot drivers from Android SDK Manager.
xocomaox said:
Update your ADB/fastboot drivers from Android SDK Manager.
Click to expand...
Click to collapse
Still the same error..
siddhesh.raikar said:
Still the same error..
Click to expand...
Click to collapse
Are you using the minimal fastboot and adb
Yeah, definitely get the 1.6gb package as it has the correct files.
Also make sure you are using the correct fastboot executable as you can have multiple instances of it on your computer. If you have edited the PATH system variable make sure to change it to the new location if you installed the SDK suite.
Yeah I had so many different toolkits and adb folders on my PC, it wouldn't work till I deleted all of them then download the Android SDK from Google, and installed platform tools. All the quick answer, dummy proof adb files on the internet do not work for this phone
Lost Storage Capacity after flashing Stock
My available storage fell from 128 to 112 after flashing the stock image. I imagine it has to do with failed partition_a flashing at some step. But was curious if anyone else had this problem? I'm currently going through the recommendations above (as I shamefully also {though cmd prompted from Platform_Tools} have the minimal adb set on my comp as well)... I have deleted all that I was aware of - and am still completing a successful flash (as I previously had been) but still have not been able to regain that lost 16 gigs of space. Next step will be to dig through the comp to see if there are any leftovers from the minimal packages hiding around on my computer.
I have been flashing from google sdk package; thought I had gotten rid of all minimal adb tools, but still missing internal storage. Any advice?
I can provide (though not at the moment) the terminal command-line history - if that would be any help.
Thanks.
federalitamale said:
I have been flashing from google sdk package; thought I had gotten rid of all minimal adb tools, but still missing internal storage. Any advice?
Click to expand...
Click to collapse
You'll probably have to factory reset to recover the lost space, if nothing else works.
Thanks. I will try that. For clarity sake, I should have said earlier, my 128 pixel is showing an available 110 gigs of a possible 112. Not 112 free of a possible 128. 16 gigs just seem to have vanished off the card.
cam30era said:
You'll probably have to factory reset to recover the lost space, if nothing else works.
Click to expand...
Click to collapse
Unfortunately that did not recover the missing internal drive space. I attempted both from the settings, and from recovery mode.
I've attached a .txt of everything that succeeded and failed during the flash.
Oh - and I should have been looking at my phone rather than Windows. It's still missing - but it's actually:
Used: 8.22 GB of 119 GB - so only 9 GB missing. Sorry.
It's like rather than erasing and formatting the original system when I flashed the stock image - it just repartitioned it to unusable space; and set up a new partition of the system I was then flashing.
federalitamale said:
Used: 8.22 GB of 119 GB - so only 9 GB missing. Sorry.
Click to expand...
Click to collapse
This is exactly as it should display, the 'missing' 9GB is the operating system itself, which is not reported in storage settings.
Its that way on every phone.
uicnren said:
This is exactly as it should display, the 'missing' 9GB is the operating system itself, which is not reported in storage settings.
Its that way on every phone.
Click to expand...
Click to collapse
But wouldn't that mean there is 17.2 GB of "system" on it? Storage shows as 8.2 GB of system installed on the device, and the phone is factory reset (I haven't put any apps or data on it). Yet it still only shows like 111 GB free after that. So 111 GB free plus the 8.2 system still doesn't add up to 128. So what/where is that remaining 9?. Sorry if I'm being dense.
Before I stupidly flashed TWRP on it, it showed 119 GB free of 128 GB. That's why I flashed the stock on it to fix my dumb mistake and run TWRP read only on it to do the systemless root, to keep OTA updates.
So I reflashed the stock image, then I successfully ran, Read only TWRP, flashed chain fire's SU. I have root status, have confirmed I only have the stock recovery. Yet my total storage (used plus free) only shows as 119 GB. As well, I discovered this morning, OTA updates will not install.
Reflashed stock again, stopped there. Still 119 GB, still can't install OTA updates.
Thanks for the advice.
Hey everyone,
So my Pixel 2 XL is kinda stuck at the moment. I'm having problems getting stock back up on my Pixel 2 XL, When I click onto flash-all command it does the job till it gets near the end of the process and then comes up with the error as 'Target didn't report max-download-size' I've used other factory images for the Pixel 2 XL CMD and the phone isn't having it at all. I really don't know what to do at this point. I need some kind of fix to this. Any advice would be really great.
** NEW ERROR **
target reported max download size of 536870912 bytes
sending 'bootloader' (36356 KB)...
OKAY [ 0.799s]
writing 'bootloader'...
OKAY [ 0.370s]
finished. total time: 1.169s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.341s]
writing 'radio'...
OKAY [ 0.570s]
finished. total time: 1.911s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: failed to load 'image-taimen-pq2a.190405.003.zip': Not enough space
Press any key to exit...
When you say you flashed others and all was ok, what month are those images from? What I'm wondering is if you have out dated fastboot. Did you already update your platform tools? If not, do that and see if it works.
I usually run into this issue if I don't have enough free space on my C drive (at least 4 GBs; the system partition image is around 2 GBs...). And if it's not the free space issue, usually it's merely just a change/re-initialization of the USB cord. Make sure you have the latest platform-tools (r28.0.2 is the most up-to-date version) as well as using a USB-C to USB-A cord (USB-C to USB-C seems to cause endless amount of issues and is usually the root cause for random unknown reasons...)...it usually sets things up right to work the next time around.
But, if making sure of all the previous things, and you restarted your phone and computer already, then you might try re-downloading the Full Factory image and extracting it once again (don't forget to re-edit the .bat/.sh file to not include the "-w" attribute); and consider even going through the trouble of comparing checksums to make sure you are getting/using the exact proper copy of the factory image...
good luck to you and hope this helps...
Fe Mike said:
When you say you flashed others and all was ok, what month are those images from? What I'm wondering is if you have out dated fastboot. Did you already update your platform tools? If not, do that and see if it works.
Click to expand...
Click to collapse
I uninstalled and reinstalled fastboot, re-downloaded platform tools and reinstalled all drivers. I downloaded the factory file straight from google which was the android 9.0 April 2019 update. Yet I'm still having this problem. It was working fine yesterday as I went to reboot it, it just went straight into a bootloop. The phone was rooted via magisk.
So I got a new error now and fastboot is telling me that there is not enough space to load the zip file. Everything is extracted out of the image zip file and moved into the adb folder
Finally Solved the problem! So I booted the phone into its stock recovery and pushed the adb zip file through and then after waiting for 20 minutes I rebooted the phone and its booted into its stock rom. Thanks everyone!
Knxed_ said:
Finally Solved the problem! So I booted the phone into its stock recovery and pushed the adb zip file through and then after waiting for 20 minutes I rebooted the phone and its booted into its stock rom. Thanks everyone!
Click to expand...
Click to collapse
You can boot twrp and flash the ota as well