installing lollipop factory image question - Nexus 5 Q&A, Help & Troubleshooting

I tried installing factory image of android 5.0 on my Nexsus 5. Then after i execute flash-all.bat I get .sig errors but it did not fail, It did install android on my device even i got some errors
Is my installation is good? does the errors will affect my device? or my installation is corrupted?

These errors have always happened

Related

[Q] Writing system FAILED but flash successful ?

Hello, i just flashed Lollipop 5.0.1 with the factory image method.
When running flash-all.bat everything worked fine but the last step, " Writing System " (Just after " Sending System " ) failed.
So i exit .cmd, unplug the Nexus 5, force reboot it.. And it boots just normally to Lollipop. So the flash is successful.. Even with " Writing system " failed ?
Is it ok like that now or should i do it all over again ? (The Nexus is running lollipop fine now but idk if it could have corrupted some things)
The problem for many people is the flash scripts give errors. You could try and fastboot flash the system.img manually if you're worried. I never use these scripts
I had this problem when I was going back and forth from KitKat to lollipop and I had to extract the factory image and flash each portion one at a time then it was fine in my case system would fail and every thing else would say it went threw but when booting it would boot kitkat there is a guide some were I had found about this but can't recall were I found it.

Moto G XT1033, flashed 5.1 but reboots on 5.0.2

Hello everyone, I got an Indian XT1033 on Lollipop 5.0.2 which is not working properly.
I unlocked the bootloader and tried to flash the stock 5.1, but after the process finishes and the device reboots, it goes again into the old system; basically, looks like it doesn't install the OS and doesn't wipe the device.
In recovery, I get errors when I try to wipe and when I attempted to flash the gpt file alone for cleaning the partitions, it gave me errors as well.
Any suggestions? I tried everything and read many posts here, but none of them worked so far. Can you help me?
slimhunter said:
Hello everyone, I got an Indian XT1033 on Lollipop 5.0.2 which is not working properly.
I unlocked the bootloader and tried to flash the stock 5.1, but after the process finishes and the device reboots, it goes again into the old system; basically, looks like it doesn't install the OS and doesn't wipe the device.
In recovery, I get errors when I try to wipe and when I attempted to flash the gpt file alone for cleaning the partitions, it gave me errors as well.
Any suggestions? I tried everything and read many posts here, but none of them worked so far. Can you help me?
Click to expand...
Click to collapse
have u tried to fastboot flash starting from Kitkat Again ?? (4.4.4>5.0.2>5.1.1)...
Actually yes, I tried all the steps: upgrading, staying on the same version and downgrading...always with the same result, when the process finishes and the phone reboots, it's still not wiped. If I try to flash single files, this is very weird, it returns errors. Basically it's like it doesn't write anything into the NAND.
slimhunter said:
Actually yes, I tried all the steps: upgrading, staying on the same version and downgrading...always with the same result, when the process finishes and the phone reboots, it's still not wiped. If I try to flash single files, this is very weird, it returns errors. Basically it's like it doesn't write anything into the NAND.
Click to expand...
Click to collapse
did you notiched fastboot console showing "success" or "writing failed" while flashing?
Are you flashing the 5.1 Factory Firmware Image?
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
What you describe sounds like a classic case of corrupt read-only emmc. One solution may be to try flashing CyanogenMOD.
Quick update after many attempts, following all your suggestions: I gave up as none of them worked...to be more precise, when flashing single files it gave various errors, while flashing the whole bunch with the script it went through every step without giving errors; no "success" info came up though.
I flashed the 5.1 image as well, but it didn't solve the issue...I sent it for repair, we can close this thread. Thanks for your kind suggestions!

adb sideload fails - can't mount anything

I have a Boost 1031 and I unlocked bootloader and rooted with no issues. Phone was 4.4.1 and auto-updated to 4.4.4. I installed TWRP and tried flashing CM13 which indicated 1031 was compatible. Couldn't install due to outdated bootloader version so followed post saying edit text out of rom to bypass and it will update automatically. I did, and it worked, but I just got the CM13 logo bootloop. Thought maybe I could go back to stock and take it slower with a stock 5.1 or GPE but can't "downgrade" now since CM13 did successfully flash.
via command in fastboot I am on bootloader version 411A.
I have tried:
adb sideloading factory image for Boost Falcon - failed due to partition error.
adb sideloading 5.1 optimized rom, CM12 and CM13 - failed due to not able to mount anything.
extracted and via fastboot:
4.4 stock factory image - successfully installed w/initial errors relating to downgrade as warned, stuck on 'unlocked bootloader' screen
5.1 optimized rom - successfully installed, stuck on loop of sad broken android on his side.
CWM recovery
3 versions of TWRP
Is there anything else I can try? I can still get into fastboot and the custom recovery.
Thanks!
static.chaos73 said:
I have a Boost 1031 and I unlocked bootloader and rooted with no issues. Phone was 4.4.1 and auto-updated to 4.4.4. I installed TWRP and tried flashing CM13 which indicated 1031 was compatible. Couldn't install due to outdated bootloader version so followed post saying edit text out of rom to bypass and it will update automatically. I did, and it worked, but I just got the CM13 logo bootloop. Thought maybe I could go back to stock and take it slower with a stock 5.1 or GPE but can't "downgrade" now since CM13 did successfully flash.
via command in fastboot I am on bootloader version 411A.
I have tried:
adb sideloading factory image for Boost Falcon - failed due to partition error.
adb sideloading 5.1 optimized rom, CM12 and CM13 - failed due to not able to mount anything.
extracted and via fastboot:
4.4 stock factory image - successfully installed w/initial errors relating to downgrade as warned, stuck on 'unlocked bootloader' screen
5.1 optimized rom - successfully installed, stuck on loop of sad broken android on his side.
CWM recovery
3 versions of TWRP
Is there anything else I can try? I can still get into fastboot and the custom recovery.
Thanks!
Click to expand...
Click to collapse
Try to flash the 5.1 Factory Firmware Image:
http://forum.xda-developers.com/showthread.php?t=2542219
http://forum.xda-developers.com/moto...mware-t3110795
From that point you can move on to custom ROMs if you wish
satanas17 said:
Try to flash the 5.1 Factory Firmware Image:
http://forum.xda-developers.com/showthread.php?t=2542219
http://forum.xda-developers.com/moto...mware-t3110795
From that point you can move on to custom ROMs if you wish
Click to expand...
Click to collapse
Yes I have tried that. The problem is that I can't flash anything because there is no recognized system. No matter what rom it is, it can't mount sd card, data, /dev/block/platform etc. After more research I think I may need to reformat the partitions but in adb I get an error of no superuser. I'm trying to see if I can do it in fastboot instead.
static.chaos73 said:
Yes I have tried that. The problem is that I can't flash anything because there is no recognized system. No matter what rom it is, it can't mount sd card, data, /dev/block/platform etc. After more research I think I may need to reformat the partitions but in adb I get an error of no superuser. I'm trying to see if I can do it in fastboot instead.
Click to expand...
Click to collapse
OK, finally got it working! I used fastboot to partition with the gpe image of the rom I was trying to flash, then fastboot to format. Then I went into recovery and tried to mount data/system/cache. Data was still not available, so I used recovery to format data and got it mounted. I tried a few different roms and finally was able to get cyanpop marshmallow to load up and run. I'm going to try and figure out what the difference is because I want CM13 nightly eventually. I tried to downgrade back to 4.4 stock but never could get past the downgrade errors when flashing in recovery, and flashing via fastboot or adb sideload would just fail.
Anyway, thanks for your help!
You seem to be making things more complicated than necessary. You should be aware Firmware Images can only be flashed via Fastboot. Flashing the GPE firmware image formatted userdata (/data) to EXT4. Stock ROMs will not boot if you have an EXT4 /data partition. See the FAQ in my Stock ROM collection thread.
lost101 said:
You seem to be making things more complicated than necessary. You should be aware Firmware Images can only be flashed via Fastboot. Flashing the GPE firmware image formatted userdata (/data) to EXT4. Stock ROMs will not boot if you have an EXT4 /data partition. See the FAQ in my Stock ROM collection thread.
Click to expand...
Click to collapse
OK that makes sense. I will read through your FAQ before attempting to flash anything else. Thank you for the information!

My Moto G XT1033 Hard Bricked

I was having a problem with my Moto G XT1033 yesterday as most apps get closed automatically at launch. this morning i installed AVG to do a scan, i also used Root file manager to clean up some files (junks, duplicates etc)
I then did a restart after which my phone will not boot to home screen again.
It boots up showing the boot animation bout after that i get a black blank screen which back light on.
Things i have tried
did cache partition wipe
did wipe/restore
all to no avail
I then downloaded a stock ROM from Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
downloaded minimal ADB and fastbook.
- put the phone to fastboot
- on android system recovery mode i clicked apply update from ADB
then on PC i confirmed it can see my phone by typing adb devices, my phone get listed.
I then do adb sideload Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
Finding update package.........
Opening update package........
Verifying update package........
Installing update..........
Then i get Package expects build fingerprint of motorola/falcon_asia_ds/falcon_umtsds:5.0./LXB22.46-28/30:user/release-keys or motorola/falcon_asia_ds/falcon_umtsds:5.1/PB23.13-56:user/release-keys; this device has motorola/falcon_asia_ds/falcon_umtsds:5.1/LPBS
E:Error in /sodeload/package.zip (status 7)
Install aborted.
Device Details
Moto G
XT1033
build LPBS23
Indian version
running Android 5.1.1 (running latest android for the device, i only do OTA updates/upgrades)
Not rooted
no custom OS
I will really appreciate any help to get the device up again
wasconet said:
I was having a problem with my Moto G XT1033 yesterday as most apps get closed automatically at launch. this morning i installed AVG to do a scan, i also used Root file manager to clean up some files (junks, duplicates etc)
I then did a restart after which my phone will not boot to home screen again.
It boots up showing the boot animation bout after that i get a black blank screen which back light on.
Things i have tried
did cache partition wipe
did wipe/restore
all to no avail
I then downloaded a stock ROM from Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
downloaded minimal ADB and fastbook.
- put the phone to fastboot
- on android system recovery mode i clicked apply update from ADB
then on PC i confirmed it can see my phone by typing adb devices, my phone get listed.
I then do adb sideload Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
Finding update package.........
Opening update package........
Verifying update package........
Installing update..........
Then i get Package expects build fingerprint of motorola/falcon_asia_ds/falcon_umtsds:5.0./LXB22.46-28/30:user/release-keys or motorola/falcon_asia_ds/falcon_umtsds:5.1/PB23.13-56:user/release-keys; this device has motorola/falcon_asia_ds/falcon_umtsds:5.1/LPBS
E:Error in /sodeload/package.zip (status 7)
Install aborted.
Device Details
Moto G
XT1033
build LPBS23
Indian version
running Android 5.1.1 (running latest android for the device, i only do OTA updates/upgrades)
Not rooted
no custom OS
I will really appreciate any help to get the device up again
Click to expand...
Click to collapse
Firstly, I would like to point out that your phone is merely soft-bricked. Hard bricks are much more serious and happen when your phone does not turn on at all. So, in future, please do not complain about a hard brick where there is none.
Onto the actual issue, it appears to be an easy fix. The problem was simply that you were attempting to sideload an OTA update, as opposed to flashing full firmware, which will not work. So all you need to do is flash the full factory firmware using fastboot flash, not adb sideload. To do this, flash factory firmware from here using the fastboot commands linked on that thread.
Professor Gibbins said:
Firstly, I would like to point out that your phone is merely soft-bricked. Hard bricks are much more serious and happen when your phone does not turn on at all. So, in future, please do not complain about a hard brick where there is none.
Onto the actual issue, it appears to be an easy fix. The problem was simply that you were attempting to sideload an OTA update, as opposed to flashing full firmware, which will not work. So all you need to do is flash the full factory firmware using fastboot flash, not adb sideload. To do this, flash factory firmware from here using the fastboot commands linked on that thread.
Click to expand...
Click to collapse
im sorry for the false alarm.
Thanks! :good:

Google Pixel - No apply update from ADB in recovery and other strange things

Hello everyone,
The starting situation is the Google Pixel of my mother was stuck on android 8.0. While showing there was an update available, the update would always fail to install after the reboot in the process. I found advice to factory reset the phone and then update, but this didn't help.
So my first thought was, if the update won't install the normal way I will do it manually. Google OTA installation guide says, get file (latest), reboot to recovery, plug in to USB, choose apply update by adb.
At this point the guide loses me, because the recovery screen I get to only lists reboot, reboot bootloader, simlock tool and device info tool (see picture). The device info will only tell "failed to update device info". The simlock tool just says "failed to enable simlock". Further while on this screen the phone isn't visible as an ADB device any more.
Next thing to try cause this didn't work was getting the image file (latest) from Google and flashing it through fastboot flash all, which led to a boot loop and the phone not starting at all. So I went and flashed back to the android 8 that was on it before and the phone booted again, but I'm still not any step further.
Next idea was maybe the recovery is broken somehow, so I went to install TWRP. Following the instructions I copied the latest version zip onto the phone and booted the img through fastboot. So far everything is fine, but when I install the zip I will get several errors about "can't mount /persist". And the installation won't work.
At this point I am out of ideas, so maybe someone here can tell me if and how this can be fixed? I wasn't able to find any information on this issue, aside from some xiaomi phones can show similar errors with the /persist partition and TWRP.
Any help would be welcome.

Categories

Resources