Related
I've found only one instance of this so far in the development forum by user malickie but they seem to have just returned the phone and I don't believe it's unfixable.
It all started by my trying to update while retaining root without flashing a stock 2.3.5. I tried the "three lines of code method", editing from within the phone using either FX or ES explorer (one initially wouldn't paste back into /system/bin after I made a backup on the sd card).
When I tried to update it got as far as the recovery image, the android with the folder and arrow, and eventually crashed telling me I had invalid this and that; CDROM, SYSTEM, WEBTOP. Sorry, I don't remember the specifics. I shut it down and it bootlooped as far as the AT&T logo droplet thing.
I launched into forum scrounging mode, got RSD Lite 5.6, the FXZ, the update.zip, and flashed back to 2.3.5. The first time I shut down after this it bootlooped again. So I flashed it again, so far so good, so I figured I'd go ahead and update to 2.3.6. More bad luck as it tells me "insufficient memory please factory reset". I try this, and it goes into fastboot telling me "Invalid CG (cg: recovery)".
So, I've been scrounging all day trying to figure out if this issue has been solved to no avail Does anyone have any suggestions?
ri4naire said:
I've found only one instance of this so far in the development forum by user malickie but they seem to have just returned the phone and I don't believe it's unfixable.
It all started by my trying to update while retaining root without flashing a stock 2.3.5. I tried the "three lines of code method", editing from within the phone using either FX or ES explorer (one initially wouldn't paste back into /system/bin after I made a backup on the sd card).
When I tried to update it got as far as the recovery image, the android with the folder and arrow, and eventually crashed telling me I had invalid this and that; CDROM, SYSTEM, WEBTOP. Sorry, I don't remember the specifics. I shut it down and it bootlooped as far as the AT&T logo droplet thing.
I launched into forum scrounging mode, got RSD Lite 5.6, the FXZ, the update.zip, and flashed back to 2.3.5. The first time I shut down after this it bootlooped again. So I flashed it again, so far so good, so I figured I'd go ahead and update to 2.3.6. More bad luck as it tells me "insufficient memory please factory reset". I try this, and it goes into fastboot telling me "Invalid CG (cg: recovery)".
So, I've been scrounging all day trying to figure out if this issue has been solved to no avail Does anyone have any suggestions?
Click to expand...
Click to collapse
I hate to say it, but it sounds like you might have a bad phone.
But you can try using the beginner thread and use the directions there to flash the fxz, but try unzipping the fxz and then go into RSD lite and click on the "..." button, and then select the xml file and start flashing.
If that does not work, there is another way, but you have to be VERY careful, because this can hard-brick your phone.
Last ditch, but ONLY if the others don't work, do this:
Make sure your have the android sdk installed:
http://developer.android.com/sdk/index.html
Then go grab this, and put in the same directory as the SDK installed to, under platform-tools:
http://forum.xda-developers.com/attachment.php?attachmentid=890596
Then open a command line in the directory that you saved and unzipped the fxz in, then;
put your phone in fastboot mode, connect the USB cable, and:
Code:
[FONT=monospace]
[/FONT]fastboot erase userdata
fastboot erase cache
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash preinstall preinstall.img
fastboot reboot
No guarantees this will work
The first two work fine, returning "OKAY". However, if I try any type of flashing from the cmd prompt I get a "FAILED".
Code:
C:\*\InlineFlashing_etc>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.355s]
finished. total time: 0.356s
C:***>fastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.020s
C:***>fastboot flash system system.img
sending 'system' (491264 KB)...
OKAY [ 17.982s]
writing 'system'...
(bootloader) Preflash validation failure
FAILED (remote: )
finished. total time: 18.212s
I realize we have a locked bootloader so is there a step I might have missed? I flashed back the updated fxz (that's now 18 steps instead of 20, and PS. this renders me with a functional phone, just not one that can update) and luckily I can seem to get back to at least this state consistently.
Ok, so I tried rooting in this state and used the ADB method from the Beginners' Guide to attempt to retain root through the update. This time there was nothing about insufficient memory, it just downloaded the update and then tried to reboot for the install but instead of going to unzip the package it goes straight back to fastboot flash mode with another failure.
Code:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.65
Battery OK
OK to Program
Connect USB
Data Cable
On the bright side it's not taunting me with invalid partitions but then again it won't boot normally either. I'm stuck on this screen.
Try pulling the battery and then booting into boot selection mode. (Press+hold volume buttons, then power button) and select "normal boot".
If that doesn't work then flash the fxz... again.
Did you do manual or one-click root?
Sent from my MB865 using Tapatalk
Ok, I had to plug it in overnight, making sure not to press the power button because it would go into "AP Fastboot", because my battery ran low. I'm flashing the updated FXZ again right now.
I've only ever done the One-Click Root. The first time I tried to retain root, what started all this, was using only the phone. This last time I used the ADB method and it didn't demand I factory reset.
Interestingly, when I tried that factory reset that's when it told me my recovery image wasn't good. I've noticed that the FXZ doesn't flash recovery.img but it does flash system, boot, and preinstall. So, is it possible I could manipulate that file to perform the steps you, Jim, suggested? I should just need to create an MD5 sum and follow the template of the rest of the time, right?
Hi,
so yeah... I got two fatal problems that completely block me from doing anything on my phone.
It started when suddenly my phone's screen turned black, and after a restart it keeps taking me to a screen when it asks for a password to decrypt my data, blocking me from reaching my phone.
So I wanted to recover the phone to fix it, but when i enter fastboot and choose recovery, after a few seconds it shows a picture of the android logo with an exclamation mark on it, and I cannot get into the recovery screen.
Each problem prevents me from fixing the other one, any ideas of how can I save my phone?
Download a custom recovery for crespo. Get your phone into fastmode mode and flash the recovery image.
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Then select recovery in fastboot menu.
Encrypt problem is reported in this thread earlier. You may have to do a full wipe and flash a new ROM.
I downloaded the google factory image, but when i run fastboot -w update image-soju-jzo54k.zip (tried two different ones), it fails when trying to write to the system partition (FAILED remote: Write fail).
the other partitions work, but something prevents me from updating the system partition no matter what zip i use, tried many.
any ideas?
Please provide complete log messages shown on PC and phone.
Which phone did you have? soju is for i9020t, and sojua for i9020a.
Try to format data/cache/system via clockworkmod recovery first.
_android_ said:
Please provide complete log messages shown on PC and phone.
Which phone did you have? soju is for i9020t, and sojua for i9020a.
Try to format data/cache/system via clockworkmod recovery first.
Click to expand...
Click to collapse
I wasn't able to find the exact model of my phone, but since soju failed flashing and sojua succeeded, i assume it's i9020a.
Anyway, I tried to format data/cache/system via cwm recovery, and after system succeeded, the phone starts "restoring data...", and after a few minutes it stops with the message "Can't mount /data!"
perhaps the reason i he can't mount/restore /data is the reason I'm getting the encryption problem in first place, is there any way around it?
loliori said:
I wasn't able to find the exact model of my phone, but since soju failed flashing and sojua succeeded, i assume it's i9020a.
Anyway, I tried to format data/cache/system via cwm recovery, and after system succeeded, the phone starts "restoring data...", and after a few minutes it stops with the message "Can't mount /data!"
perhaps the reason i he can't mount/restore /data is the reason I'm getting the encryption problem in first place, is there any way around it?
Click to expand...
Click to collapse
Model is printed on IMEI sticker at back of phone under battery.
Format data/cache/system before flashing sojua image. Skip format system if giving problem.
Code:
fastboot -w update image-sojua-jzo54k.zip
Or try running the batch file as is, and it will update bootloader and radio to latest version as well.
flash-all.bat or flash-all.sh (linux)
_android_ said:
Model is printed on IMEI sticker at back of phone under battery.
Format data/cache/system before flashing sojua image. Skip format system if giving problem.
Code:
fastboot -w update image-sojua-jzo54k.zip
Or try running the batch file as is, and it will update bootloader and radio to latest version as well.
flash-all.bat or flash-all.sh (linux)
Click to expand...
Click to collapse
ok so soju is the right one for me.
I followed your instructions and now, and it fails writing the system image, the cmd window pretty much looks like that:
checking product...
OKAY
...
... (more ok checks)
sending 'boot'
OKAY
more OK sendings
sending 'system'
OKAY
writing 'system'
FAILED (remote: Write Fail)
I also tried using the batch file and although the window closes before i can see if any error happened, i get the same "FAILWrite Fail" error in my fastboot screen status, so I assume the same problem occurs.
What about formatting system partition via cwm? Failed too?
no, formatting system partition works. every partition format works, but i still can't update through fastboot.
It might be worth mentioning that I cannot even erase partitions on fastboot (fastboot -w fails, fastboot erase userdata, fastboot erase system etc fails, giving me a FAILED remote: erase fail error)
loliori said:
no, formatting system partition works. every partition format works, but i still can't update through fastboot.
It might be worth mentioning that I cannot even erase partitions on fastboot (fastboot -w fails, fastboot erase userdata, fastboot erase system etc fails, giving me a FAILED remote: erase fail error)
Click to expand...
Click to collapse
How about flashing a new ROM say CM10.0 + gapps-jb-20121011 via CWM?
_android_ said:
How about flashing a new ROM say CM10.0 + gapps-jb-20121011 via CWM?
Click to expand...
Click to collapse
flashing gapps seems to finish but when i flash CM i'm not sure wether it was installed correctly. it just says
finding update package...
opening update package...
installing update...
and then goes back to the cwm recovery menu, as if it finished.
anyway, i tried rebooting after flashing both and my device gets stuck right after starting, i get the google logo and then the screen just turns black and seems to process forever, and nothing happens afterwards, it's just a black screen.
loliori said:
flashing gapps seems to finish but when i flash CM i'm not sure wether it was installed correctly. it just says
finding update package...
opening update package...
installing update...
and then goes back to the cwm recovery menu, as if it finished.
anyway, i tried rebooting after flashing both and my device gets stuck right after starting, i get the google logo and then the screen just turns black and seems to process forever, and nothing happens afterwards, it's just a black screen.
Click to expand...
Click to collapse
You should Install CM then gapps.
_android_ said:
You should Install CM then gapps.
Click to expand...
Click to collapse
yeah I flashed CM and then gapps.
Interestingly tho, none of the google factory images manages to flash through CWM. they just say update failed without any informative error, while CM and gapps seem to succeed flashing
loliori said:
yeah I flashed CM and then gapps.
Interestingly tho, none of the google factory images manages to flash through CWM. they just say update failed without any informative error, while CM and gapps seem to succeed flashing
Click to expand...
Click to collapse
Google factory images are only flashable via fastboot. But there may be CWMed (cooked) versions available in XDA.
It seems like no matter what rom i flash, it either gets stuck while the phone is loading, or the phone loads and i get this "type password to decrypt" window.
Is there a way to like hard-format my phone, or a way to fix my fastboot flashing problems?
Phone: Moto X / KitKat 4.4
Carrier: AT&T (XT1058)
Problem: Mysteriously stopped booting.
Good News: Fastboot is recognized.
Bad News: (bootloader) Flash write failure
Taking this guide as my playbook - http://forum.xda-developers.com/moto-x/moto-x-qa/kitkat-update-crashed-moto-x-t2535150 I tried to flash on a stock OS. Here's the main spot from the thread I'm working from-
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
The mission objective is simple: retrieve files off of sdcard and factory reset.
So with my mfastboot (not the android one), I'm trying to flash my stock OS back on so I can get a drive in windows and retrieve sdcard files. Actually, ANY OS back on at this stage of the game will be nice.
Things I have NOT done:
1. rooted the phone, or
2. unlocked the boot loader
If doing these will help, let me know.
So I get my download from sbf.droid-developers.org for 4.4.2 & ATT carrier and unpack the files.
flashing for 'partition' in gpt.bin actually works (yay), but I get the above error ("Flash write failure") for system.img and recovery.img
uh-oh
It seems others with this problem changed cables and USB ports, so I tried that. No dice.
Someone said something about permissions, so I started my command window with administrator privileges, also no luck.
Unless, of course, they meant permissions on the phone side of things? Would that actually help?
So at this juncture if my SDCard died I can go for warranty because I never did any unlocking.
However, if the SDCard can be saved, I am willing to void the warranty and unlock. The data on it is valueable to me and yes a lesson I learned here is I should start using dropbox or equivalent service. Noted.
Should I unlock the phone and try mfastboot flash system system.img, or am I already dead?
Factory reset doesn't even work, I get "no valid piv block in sp for system"
I just ran mfastboot erase cache and at the command prompt I get:
(bootloader) Failed to erase partition
FAILED: Remote failure
The phone screen says, 'Failed to erase partition cache'
This doesn't sound good.... Is there anyway can get this thing booted?
Ah, nevermind, it just keeps getting errors flashing everything. Something with the phone itself is seriously wrong.
I've decided to return it. I think my data is lost.
Hello guys I need some help. I'm stuck in fastboot mode with no recovery or OS too l, let me retrace my steps.
I had my px3 rooted on stock but I was bored with stock and tried to flash bootleggers rom and followed instructions to wipe "everything" but internal storage, so I did including storage under internal storage and flashed the ROM and twrp with it. After it just rebooted back to recovery every time I tried normal boot. (I'm assuming I F'd up by wiping storage). So I googled what to do about looping recovery and one suggestion was to factory reset so I did; I can no longer access recovery. I've tried flashing factory image, flashing the twrp zip, trying to boot straight to twrp, I can't get to adb sideload and it says "no valid slot to boot" on fastboot screen any suggestions?
Got another on fastboot, "error booting boot.img"
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
wergrun said:
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
Click to expand...
Click to collapse
You need to get back to fastboot, and run the flash all bat file from the full factory image.
TonikJDK said:
You need to get back to fastboot, and run the flash all bat file from the full factory image.
Click to expand...
Click to collapse
I tried that but I keeps giving me an error, I'll post it when I get the chance
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
I have the same issue, except my computer will not recognize the device in fastboot. I tried two different computers, Windows 10 and laptop running Linux.
wergrun said:
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
Click to expand...
Click to collapse
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
SS823 said:
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
Click to expand...
Click to collapse
I did get that too but it was because I forgot to put a space after "bootloader_a ", are you Stuck at around the 9 minute steps?
Yes, right around the end at 9 minutes. Everything works fine - bootloader, radio, etc. When I get to the end of the img zip file I get this message:
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s
I am at a loss.
I'm trying to downgrade my Pixel back to 9. Few reasons - unimportant.
I have the latest platform tools, adb and fastboot both find the phone fine.
I've downloaded the latest stock image from the Google site.
But I get a very odd error
Sending 'bootloader' (8493 KB) OKAY [ 0.199s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Everything is in the same folder, I've tried using the full path and not relative paths. Tried different cables and even different stock images. I've also got older versions of platform tools so tried earlier versions of fastboot.
I'm lost. What else is there to try/do?!
teapea said:
I'm trying to downgrade my Pixel back to 9. Few reasons - unimportant.
I have the latest platform tools, adb and fastboot both find the phone fine.
I've downloaded the latest stock image from the Google site.
But I get a very odd error
Sending 'bootloader' (8493 KB) OKAY [ 0.199s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Everything is in the same folder, I've tried using the full path and not relative paths. Tried different cables and even different stock images. I've also got older versions of platform tools so tried earlier versions of fastboot.
I'm lost. What else is there to try/do?!
Click to expand...
Click to collapse
Out of curiosity, which variant is this? Vzw? Google? Have you done updates in this way before? Or maybe only OTA updates?
cheers
Google stock image, using Google drivers, platform tools from full SDK. Done many many flashes this way - although never "downgraded" before. I stupidly hit update on my Pie stock image and it went to 10 so trying to go back.
I did read it needed have no "pending installs" in order to flash - but that doesn't make much sense, but currently OTAing to latest 11 version.
I did have Magisk root on my original 9, and the OTA to 10 obviously killed this.
Happy to kill all data and start again, I just need 9 back on this phone!
Only thing I've not tried is a different computer - will need to wait until I get back from the office to try another one though, but I've used my own laptop many times before which is why it's so confusing!
And to confirm - another laptop, totally fresh image - same problem...
teapea said:
And to confirm - another laptop, totally fresh image - same problem...
Click to expand...
Click to collapse
I know it seems simple but bootloader is unlocked and usb debugging is enabled? Also, are file extensions visible? That could cause problems too
Here's how I downgrade once in fastboot:
fastboot --slot=all flash bootloader bootloader.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=all flash radio radio.img(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(current slot) --skip-reboot update image.zip(or drag and drop to cmd window)
fastboot reboot bootloader
fastboot --slot=(other slot) --skip-reboot update image.zip(or drag and drop to cmd window)
Then you enter recovery and wipe/format data and reboot to system after
Yeah - well I found the problem.
I was launching fastboot via "adb reboot fastboot" - which then put the phone in a screen which said "fastbootd" in red at the top. I'd never seen it before, but said fastboot so thought it was OK.
As soon as I remembered to reboot into fastboot with the volume down key - we're all good!
Never seen the fastbootd screen before - no idea what that was all about - I assume after installing Android 10/11 this was the new fastboot screen but clearly not!
Either way - I'm back on 9 and getting things back to normal. Systemless hosts is causing my grief with adblocker at the moment, but not investigated that too much.
So I guess the error message wasn't the right one, but just a generic one based on me not being in the right fastboot mode!
Thanks all for looking and offering advice, appreciate it - but I guess you'd never guess the issue with that error message!
the adb command is adb reboot bootloader. There may be others not sure, but that's the one I've used if the phone was on and booted.