Hi people
Yesterday I updated my phone to CyanogenMod(CM)13.0 which went fine. However when I rebooted the phone a popup came up the entire time telling me that google play services stopped working. In an attempt to fix it, I accidently removed google play services, causing a bunch of trouble at the moment.
I went to the CM Wiki and first I downloaded the "nano" variant of the GAPPS, trying to fix everything in the end. I put the file on my phone and tried to install it via recovery. This message came up however:
Insufficiënt storage space available in system partition. You may want to use a smaller GAPPS package or consider removing some apps using GAPPS-config ( bla bla) Error code 70.
As far as I can see, it is able to mount /system and /data, but the partition does not seem to have enough space left, at least so it says.
After that I tried the same with the "pico" variant, which also gave the same result. Pretty strange for a package that small.
So after taking a backup of important files I tried to wipe data/factory reset (was going to reinstall everything), to which I got an error "data wipe failed", which is correct since I can still boot in CM13 after that.
So I'm a bit in trouble here. I cannot seem to wipe my phone entirely, nor am I able to reinstall GAPPS due to this error 70.
Could this be a permissions problem somehow?
Things I have done so far to check what the problem could be:
- I've checked the space left on the /system partition which is 501 MB. Should be enough I guess?
- I've checked the /system partition for errors via adb shell while the phone was in recovery mode, which came out clean.
Below a picture of output of "mount", "df -h" and "uname -a" for extra information.
{
"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"
}
Thanks
Was the phone dirty flashed from an older cm13 rom or was it dirty flashed over a non-cm13 rom?
What do you mean with dirty flashed?
i got this Phone from a friend and the Original stock rom was installed. I installed Cyanogenmod together with gapps and everything went fine back then.
Dirty flashing is referred to as the installation of a new rom without wiping the previous rom prior to installation of the new rom.
If the stock rom was LP or kk and cm13 is installed via dirty flash, it is likely, based on my on experience, that the phone will hang at the boot screen.
audit13 said:
Dirty flashing is referred to as the installation of a new rom without wiping the previous rom prior to installation of the new rom.
If the stock rom was LP or kk and cm13 is installed via dirty flash, it is likely, based on my on experience, that the phone will hang at the boot screen.
Click to expand...
Click to collapse
The Phone is working perfectly on its own, except for the google-applications.
That is the reason I only need GApps, to repair the initial problem.
Would it be a solution to format /data and /system and start all over? Although i'm worried that I will still not be able to install GApps due to error 70...
I agree that it may be simpler to start over by flashing a stock Mm rom, erasing userdata in fastboot, flash userdata.img in fastboot, make sure it boots, install twrp, install cm13, no then gapps.
Which recovery do you use? TWRP or CWM?
Which build date of open gapps have you tried? The latest one?
audit13 said:
I agree that it may be simpler to start over by flashing a stock Mm rom, erasing userdata in fastboot, flash userdata.img in fastboot, make sure it boots, install twrp, install cm13, no then gapps.
Click to expand...
Click to collapse
It started installing after I initiated the flash-all command. This is the output. i downloaded the correct image and searched the net to know how I had to work with fastboot and such.
W/ ( 6228): Zip: unable to truncate file to 1044902952: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
The full log:
D:\temp\Hammerhead>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.314s]
writing 'bootloader'...
OKAY [ 0.536s]
finished. total time: 0.852s
rebooting into bootloader...
OKAY [ 0.107s]
finished. total time: 0.110s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.733s]
writing 'radio'...
OKAY [ 3.121s]
finished. total time: 4.858s
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.046s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
W/ ( 6228): Zip: unable to truncate file to 1044902952: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
So, again something about the file being to large. I locked and unlocked the lock state of my phone to make sure it would remove data, to get more space. I guess it did not really work.
Anything else I can do?
Here's the output when I flash mmb29s t0 my 16 GB Nexus 5:
D:\Downloads\Nexus 5\Nexus 5 Stock 6.01\hammerhead-mmb29s-factory-6bfcdfa4\hamme
rhead-mmb29s>flash-all
sending 'bootloader' (3120 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.542s]
finished. total time: 0.849s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (45425 KB)...
OKAY [ 1.640s]
writing 'radio'...
OKAY [ 3.122s]
finished. total time: 4.762s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........: 050db890002e8xxx
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.774s]
sending 'recovery' (10012 KB)...
OKAY [ 0.565s]
writing 'recovery'...
OKAY [ 0.824s]
sending 'system' (1020413 KB)...
OKAY [ 32.200s]
writing 'system'...
OKAY [ 68.826s]
erasing 'userdata'...
OKAY [ 8.696s]
erasing 'cache'...
OKAY [ 0.630s]
rebooting...
finished. total time: 113.718s
Press any key to exit...
I noticed your commands do not include the phone's installed baseband, bootoader, or serial number. Were these edited out before you posted the results?
audit13 said:
Here's the output when I flash mmb29s t0 my 16 GB Nexus 5:
D:\Downloads\Nexus 5\Nexus 5 Stock 6.01\hammerhead-mmb29s-factory-6bfcdfa4\hamme
rhead-mmb29s>flash-all
sending 'bootloader' (3120 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.542s]
finished. total time: 0.849s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (45425 KB)...
OKAY [ 1.640s]
writing 'radio'...
OKAY [ 3.122s]
finished. total time: 4.762s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........: 050db890002e8xxx
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.774s]
sending 'recovery' (10012 KB)...
OKAY [ 0.565s]
writing 'recovery'...
OKAY [ 0.824s]
sending 'system' (1020413 KB)...
OKAY [ 32.200s]
writing 'system'...
OKAY [ 68.826s]
erasing 'userdata'...
OKAY [ 8.696s]
erasing 'cache'...
OKAY [ 0.630s]
rebooting...
finished. total time: 113.718s
Press any key to exit...
I noticed your commands do not include the phone's installed baseband, bootoader, or serial number. Were these edited out before you posted the results?
Click to expand...
Click to collapse
Non, they were not edited out. They just did not show up.
Ok, I got the Android stock rom installed on the phone, but now something else is wrong. here is what i did:
Code:
D:\temp\Hammerhead>fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.632s]
sending 'system' (1020413 KB)...
OKAY [ 33.134s]
writing 'system'...
OKAY [ 68.970s]
finished. total time: 102.738s
D:\temp\Hammerhead>fastboot flash data data.img
error: cannot load 'data.img'
D:\temp\Hammerhead>fastboot flash data userdata.img
target reported max download size of 1073741824 bytes
sending 'data' (137318 KB)...
OKAY [ 4.556s]
writing 'data'...
FAILED (remote: partition table doesn't exist)
finished. total time: 4.745s
D:\temp\Hammerhead>fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.489s]
sending 'cache' (13348 KB)...
OKAY [ 0.647s]
writing 'cache'...
OKAY [ 1.074s]
finished. total time: 2.215s
D:\temp\Hammerhead>fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [ 0.481s]
writing 'boot'...
OKAY [ 0.774s]
finished. total time: 1.260s
I first erased the partitions "system", "data" and "cache". After that I flashed "system", "userdata", "cache", and lastly "boot"
The phone booted into the rom, I entered my PIN, after which it complained my data was corrupt. It makes sense because of this:
"D:\temp\Hammerhead>fastboot flash data userdata.img
target reported max download size of 1073741824 bytes
sending 'data' (137318 KB)...
OKAY [ 4.556s]
writing 'data'...
FAILED (remote: partition table doesn't exist)
finished. total time: 4.745s"
It prolly needs the data partition to write stuff to.
Somehow the partition table of data seems to be gone.
So, the plot thickens! Is there a way I can recreate this partition table, or am I supposed to do something else?
fastboot flash userdata userdata.img
btw, nothing is wrong with your partition table, there is simply no partition on the phone called data. Data is part of userdata partition.
The commands are:
fastboot erase userdata
fastboot flash userdata userdata.img
The img file has to be extracted from the mmb29s zip file.
Damn, stupid I didn't see that.
I'll try again tonight and see how that goes.
GTCG said:
Damn, stupid I didn't see that.
I'll try again tonight and see how that goes.
Click to expand...
Click to collapse
Ok, I got it working again. Back on stock rom atm. Thanks for help everyone!
Related
Hey all,
My Nexus S i9020a started getting into a bootloop. I went into the stock recovery and performed the wipes (multople times), but it still did the same thing when booting back up. It didn't remove my data either (I can see my widgets on the home screen before it goes into the reboot) even though I did a factory reset which is suppose to wipes out everything.
I decided to try a factory restore with a Google Image, but the two that I tried (4.0.4 and 4.1.2) both make it to the same part and failed. My bootloader is already unlocked (Lock State - Unlocked)
For 4.0.4
> fastboot -w update image-sojua-imm76d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKL1
Baseband Version.....: I9020UCKJ1
Serial Number........: 303356BD009100EC
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3444 KB)...
OKAY [ 0.538s]
writing 'boot'...
OKAY [ 0.506s]
sending 'recovery' (3776 KB)...
OKAY [ 0.591s]
writing 'recovery'...
OKAY [ 0.547s]
sending 'system' (282194 KB)...
OKAY [ 44.149s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 46.397s
For 4.1.2
> fastboot -w update image-sojua-jzo54k.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020UCLH1
Serial Number........: 303356BD009100EC
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.621s]
writing 'boot'...
OKAY [ 0.606s]
sending 'recovery' (4308 KB)...
OKAY [ 0.655s]
writing 'recovery'...
OKAY [ 0.628s]
sending 'system' (337599 KB)...
OKAY [ 53.689s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 56.368s
Any ideas?
How about
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and format /system partition via CWM before updating?
_android_ said:
How about
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and format /system partition via CWM before updating?
Click to expand...
Click to collapse
Installed 5.0.2.0, did the wipes and even picked fixed permissions, then tried to flash 4.1.2 factory image again but still failed at the same spot
EDIT: Tried with 6.0.2.5 also, did wipes, fix permissions. tried cm10
was able to push it to sd card, but when I selected it from the menu i get
set_perm: some changes failed
E:Error in /sdcard/cm-10.0.0-crespo.zip
(Status 7)
Installation aborted.
Looks like flash drive, system partition or partition table is corrupted.
Not sure if this will help [HOWTO] "Partitioning" your Nexus S using LVM
Does root need to be installed to flash a ROM from clockwork recovery?
primal2005 said:
Does root need to be installed to flash a ROM from clockwork recovery?
Click to expand...
Click to collapse
No. Root not required to flash ROM. Just CWM.
Hi,
my NSdoesnt boot and I cant flash another ROM because my NS cant mount SD anymore, so I tryed to restore it back to stock and flash the .imgs with fastboot. Boot.img, recovery.img, userdata.img, without problems, but the system.img gives me the message "write failed" or something. Tryed it multiple times with the Gingerbread system.img, and ICS system.img, same problem.
I can boot into recovery, but the phone doesnt recognize the SD and also the system partition.
Any solutions?
Sorry for my english.
What recovery you using?
Sent from my Nexus S using xda app-developers app
Tried 2 different CMW Recoveries, it's not a recovery problem. My System and SD storage is corrupt or something, I think.
It can't be all that corrupt as you are able to install boot loader and recovery. Try and adb sideload CyanogenMod 10.1. Once you got a booting phone, things tend to play nicely.
Sent from my Nexus S using xda app-developers app
Just tried the adb sideload method.
"Installing update..." for 5 Minutes now. I think it cant write on /system.
I've also tried to erase /system partition via fastboot it gives me also the "failed" message.
system.img write fail error
I have the same problem, can't write a system img to the phone
FASTBOOT STATUS - FAILWrite Fail
I have TWRP but it would not do anything to the system partition.
I tried to flash the stock rom
soju-jzo54k
I ran the flash-all.bat
this is the output
sending 'bootloader' (1536 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
OKAY [ 0.385s]
finished. total time: 0.601s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 1.919s]
finished. total time: 3.520s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 33304BC024EC00EC
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.542s]
writing 'boot'...
OKAY [ 0.587s]
sending 'recovery' (4308 KB)...
OKAY [ 0.567s]
writing 'recovery'...
OKAY [ 0.638s]
sending 'system' (337443 KB)...
OKAY [ 43.476s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 45.956s
Press any key to exit...
I've had a similar experience when installing stock ROMs after installing cwm and cm 10. Can you guys not even install cm10?
Sent from my Nexus S using xda app-developers app
Deus Tempestas said:
I have the same problem, can't write a system img to the phone
FASTBOOT STATUS - FAILWrite Fail
I have TWRP but it would not do anything to the system partition.
I tried to flash the stock rom
soju-jzo54k
I ran the flash-all.bat
this is the output
sending 'bootloader' (1536 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
OKAY [ 0.385s]
finished. total time: 0.601s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 1.919s]
finished. total time: 3.520s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 33304BC024EC00EC
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.542s]
writing 'boot'...
OKAY [ 0.587s]
sending 'recovery' (4308 KB)...
OKAY [ 0.567s]
writing 'recovery'...
OKAY [ 0.638s]
sending 'system' (337443 KB)...
OKAY [ 43.476s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 45.956s
Press any key to exit...
Click to expand...
Click to collapse
Same problem here! Did u find solution?
Hi, I've tried flashing but my phone keeps restarting.
CMD gives me this:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.033s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.444s]
finished. total time: 0.483s
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.539s]
finished. total time: 1.657s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.347s]
writing 'boot'...
OKAY [ 1.097s]
finished. total time: 1.450s
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.365s]
writing 'recovery'...
OKAY [ 1.118s]
finished. total time: 1.490s
target reported max download size of 536870912 bytes
sending 'system' (260606 KB)...
OKAY [ 8.202s]
writing 'system'...
(bootloader) Invalid signed image
OKAY [ 14.050s]
finished. total time: 22.259s
target reported max download size of 536870912 bytes
sending 'system' (239692 KB)...
OKAY [ 7.569s]
writing 'system'...
OKAY [ 14.513s]
finished. total time: 22.089s
target reported max download size of 536870912 bytes
sending 'system' (222205 KB)...
OKAY [ 7.007s]
writing 'system'...
(bootloader) Failed to validate sparse image
OKAY [ 23.327s]
finished. total time: 30.342s
target reported max download size of 536870912 bytes
sending 'modem' (47484 KB)...
OKAY [ 1.540s]
writing 'modem'...
OKAY [ 2.384s]
finished. total time: 3.930s
erasing 'modemst1'...
OKAY [ 0.069s]
finished. total time: 0.072s
erasing 'modemst2'...
OKAY [ 0.115s]
finished. total time: 0.119s
target reported max download size of 536870912 bytes
sending 'fsg' (721 KB)...
OKAY [ 0.116s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.228s
erasing 'cache'...
OKAY [ 0.119s]
finished. total time: 0.122s
erasing 'userdata'...
OKAY [ 0.282s]
The error I get on Moto G is :
Code:
hab check failed for boot
hab check failed for recovery
hab check failed for system
Invalid PIV signed system
Motorola Driver tells me my firmware is: But I've used this firmware and same error !!
{
"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"
}
Thanks In advance!
That image is 4.4.2. Maybe try the 4.4.3 Retail US image here:
http://sbf.droid-developers.org/download.php?device=14&file=928
This worked for me - http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Took additional step and loaded Blur_Version.174.44.1.falcon_umts.Retail.en.US from sbf.droid-developers.org/phone.php?device=14
This will get you a usable device again with 4.4.2 or use the 4.4.3 as mentioned by lost101
Good luck.
e.martin.howell said:
This worked for me - http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Took additional step and loaded Blur_Version.174.44.1.falcon_umts.Retail.en.US from sbf.droid-developers.org/phone.php?device=14
This will get you a usable device again with 4.4.2 or use the 4.4.3 as mentioned by lost101
Good luck.
Click to expand...
Click to collapse
Should I go to the first page of the guide or to the comment?
Canuckfan101 said:
Should I go to the first page of the guide or to the comment?
Click to expand...
Click to collapse
Sorry. First page.
http://forum.xda-developers.com/moto-g/help/guide-recover-xt1032-gpe-4-4-4-t2824377
Once back to 'base' you can update to 4.4.4 OTA or flash another ROM. And if you get stuck again, re-run this process. Three downloads, a few scripts to run; double-click easy.
Good luck.
I took the phone to my repair shop and they said it couldn't be repaired because of physical damage to the circuit board. But I believe that is not the case as the phone is in mere perfect condition
First of all, are you sure of the model?
If XT1032, try again, this time with the EU Retail 4.4.4 image. It doesn't matter where you are in the world.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
If XT1034 (AWS), here is a compatible 4.4.4 image:
http://forum.xda-developers.com/showpost.php?p=54855457&postcount=354
Hi, i checked my customer agreement and it says TXT1032, I sent it in for repair but they said it can't be fixed. Maybe due to the fact its unlocked.
Is there anyone who can help please!!
Have you followed the guides above?
Canuckfan101 said:
Is there anyone who can help please!!
Click to expand...
Click to collapse
Using a 4.4.4 firmware image, follow this post:
http://forum.xda-developers.com/showpost.php?p=56123205&postcount=8
Yes I have and I either get errors or it does not work.
Did you erase userdata? Erase everything, flash stock firmware, erase userdata and cache after and boot after that.
Hi,
I got a notification today that the 5.0 OTA update is available for my Nexus 5. I tried doing the update and Clockwork Mod complained and the update didn't work. I decided to try doing a manual install. I downloaded the 5.0 stock image, adb executable and fastboot executable. I ran flash-all.sh script included with the stock image. It seemed the ROM installed fine but I was stuck on the boot animation for over an hour. I decided this was too long and tried flashing 4.4.4 with the same problem (downloaded the 4.4.4 stock image and ran it's flash-all.sh script), boot animation kept going.
I tried installing a TeamWin as a recovery because some googling told me that the Dalvik Cache may not have been wiped correctly. I tried wiping Dalvik (and everything else) but they all errored out. I completely formatted everything (had the type "yes" for TeamWin to let me). Once again I tried installing 5.0 and had the same problem.
I did some more googling and some people suggested using ClockworkMod. I flashed ClockworkMod, wiped everything (user data, cache and dalvik) and am now stuck on the boot animation of 4.4.2. I'm running out of ideas and I hope someone else knows what's going on.
Every time that I tried running the flash-all.sh script of any of the stock images I get output very similar to the following:
ERROR: could not get pipe properties
sending 'bootloader' (2508 KB)...
OKAY [ 0.191s]
writing 'bootloader'...
OKAY [ 0.478s]
finished. total time: 0.669s
ERROR: could not get pipe properties
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
ERROR: could not get pipe properties
sending 'radio' (42049 KB)...
OKAY [ 1.427s]
writing 'radio'...
OKAY [ 2.891s]
finished. total time: 4.317s
ERROR: could not get pipe properties
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
ERROR: could not get pipe properties
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 0489450843835f19
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8628 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.745s]
sending 'recovery' (9210 KB)...
OKAY [ 0.535s]
writing 'recovery'...
OKAY [ 0.773s]
sending 'system' (702500 KB)...
OKAY [ 22.241s]
writing 'system'...
OKAY [ 48.088s]
erasing 'userdata'...
OKAY [ 14.391s]
erasing 'cache'...
OKAY [ 0.550s]
rebooting...
Also, for what it's worth, when trying to figure out my problem with TeamWin I noticed that a message to the effect of "full SELinux support is present".
Does anyone happen to know what's going on?
EDIT: I'm doing this on OS X 10.9
Did you try turning it on and off again?
Quit using custom recoverys and root, in fact, dont even try to root after you install Lollipop. If you are in Fastboot mode/bootloader and it isnt working then you should verify the integrity of the file and try a better USB cable that is dedicated for file transfer, not the cheap stock one. I flashed mine in 2 mintues no problem 5 mintues to load
EDIT: You also have to update your fastboot drivers and adb, there is a new one
Well...I fixed it. I can't say for sure but I think I may have had a bad fastboot executable. I followed this guide and installing 4.4.2 worked perfectly.
Try extracting the .img files and use fastboot to flash them manually. It installed fine for me without errors.
This phone is totally stock other than unlocked bootloader.
I was in the middle of using the web browser when out of the blue it rebooted and now no longer gets past the initial "Google" screen, it doesn't even get to the animated screen.
I tried flashing the latest software hammerhead-mob30h from within fastboot, everything worked fine and flash seems to have been successful ..still it will not go past "Google" screen.
I already tried wiping cache, it was the first thing I tried.
Any suggestions?
PS F:\android\nexus 5\hammerhead-mob30h> ./flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.272s]
writing 'bootloader'...
OKAY [ 0.524s]
finished. total time: 0.798s
rebooting into bootloader...
OKAY [ 0.100s]
finished. total time: 0.101s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.544s]
writing 'radio'...
OKAY [ 3.122s]
finished. total time: 4.667s
rebooting into bootloader...
OKAY [ 0.103s]
finished. total time: 0.104s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
--------------------------------------------
Bootloader Version...: HHZ20f
Baseband Version.....: M8974A-2.0.50.2.29
Serial Number........: 03518dc5213ea9a2
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.099s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (9146 KB)...
OKAY [ 0.509s]
writing 'boot'...
OKAY [ 0.777s]
sending 'recovery' (10004 KB)...
OKAY [ 0.563s]
writing 'recovery'...
OKAY [ 0.824s]
erasing 'system'...
OKAY [ 1.486s]
sending 'system' (1020577 KB)...
OKAY [ 32.513s]
writing 'system'...
OKAY [ 69.708s]
rebooting...
finished. total time: 107.206s
Press any key to exit...
PS F:\android\nexus 5\hammerhead-mob30h>
Verify the checksum of the factory image - just to be sure that the downloaded file isn't corrupted. For MOB30H the official checksum is
Code:
MD5: e44f4b7b25f918c8ab011ddf8d08b5a5
SHA-1: 66d165e6643366a89287414f11c247ef626ed930
However, if the checksum is fine I assume it's a hardware-related issue.
Yeah they match, damn I really wanted to wait for the next Nexus.
Damn.. maybe someone else can hop in! I'm sorry...
If memory was messed up wouldn't the flash fail?
Did you flash the userdata.ing file too?
audit13 said:
Did you flash the userdata.ing file too?
Click to expand...
Click to collapse
Was holding off on that in hopes of recovering the data.
But, could userdata affect the initial boot up? I would think the other partitions would be the ones that are used so early in boot process.
Yes, I have found that, in some cases, flashing userdata.img and immediately performing a factory wipe will allow the phone to boot.
Made some progress...
Used NRT to launch a custom recovery, do a backup of data and wipe the phone. It now has gone past "Google" screen for the first time and is on animation ....hopefully I'm back in business.
YES!
It booted back up clean, I then used NRT again to get back into custom recovery and did user data restore, booted back up and everything is as if nothing had happened
Thought she was a gonner for sure.