After updates around 5.1.* my phone started playing up and was taking longer and longer to boot, eventually getting stuck with the four coloured dots swirling around.
Time to root the phone which I duly achieved with chainfires CF-Auto-Root via fastboot (since the phone wouldn't boot up/start). I then installed TWRP and sideloaded via adb the Cataclysm ROM (both the last Lollipop and the new Marshmallow versions), performing a full factory reset first, then for good measure making sure to wipe cache and dalvik cache again (should have wiped during factory reset).
All looks good, but on booting after optimizing the applications it hangs on "Cataclysm is installing... Starting apps" and will not progress any further. I left it five hours and no progress. Powered off and rebooted and back to where I started, hangs with the four coloured dots swirling around. This was with the Lollipop version of Cataclysm so I decided to give Marshmallow a go, same result, currently stuck on "Starting apps" now for 40 minutes.
Wiping cache and dalvik cache again just results in the the applications needing to be optomised each time.
Any thoughts, advice, suggested ROMs, kernels, tricks to try or ideas on how to recover the phone would be very much appreciated.
Thanks in advance,
enilkcals
Wipe from TWRP and Install just the Rom but do not install GAPPS. There may be problem with your GAPPS package. If the ROM boots perfectly, download and install different GAPPS package.
NEXUSg4 said:
Wipe from TWRP and Install just the Rom but do not install GAPPS. There may be problem with your GAPPS package. If the ROM boots perfectly, download and install different GAPPS package.
Click to expand...
Click to collapse
Cataclysm includes Gapps so I've had a go at flashing MinimalOS (5.1.1) which doesn't (after wiping Cache, Data and Dalvik Cache of course). Still hangs on boot animation and I left it half an hour just to make sure.
Tried with XenonHD without Gapps and it too just hangs at the boot animation.
Pretty stumped now as to whats going on or how to solve it.
Try flashing a factory image. That should return it to complete stock.
This guide tells you how: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
You should download the image from here though since the one in the guide is outdated. https://developers.google.com/android/nexus/images
theminikiller said:
Try flashing a factory image. That should return it to complete stock.
This guide tells you how: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
You should download the image from here though since the one in the guide is outdated. https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I'll give it a go, but it was on stock when the problem first arose and wiping cache/dalvik/data didn't help.
I'm slightly confused as to which to download though. There are only "occam" for Nexus 4 listed, so I guess its one of those (likely 5.1.1 (LMY48T) as its the most recent). But for the other ROMs I've been installing they've all been for "mako" and when I boot into Fastboot the display reads...
Code:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 8GB
HW VERSION - rev_10
BOOTLOADER VERSION - MAKOz30f
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1701.07
CARRIER INFO - None
SERIAL NUMBER - 002fff0a560d4e29
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Wary of flashing the wrong ROM and screwing up the bootloader, as the instructions you linked (and on the image page itself) suggest the bootloader will be flashed and if I get that wrong there seems a high chance it will brick the phone.
How do I go about reconciling the device I have with the images available?
Occam is the right one. There is just several names for the device for some reason.
theminikiller said:
Occam is the right one. There is just several names for the device for some reason.
Click to expand...
Click to collapse
Thanks for the confirmation/sanity check.
Code:
# fastboot devices -l
002fff0a560d4e29 fastboot usb:2-2
occam-lmy48t # fastboot flash bootloader bootloader-mako-makoz30f.img
sending 'bootloader' (2264 KB)...
OKAY [ 0.080s]
writing 'bootloader'...
OKAY [ 0.332s]
finished. total time: 0.413s
occam-lmy48t # fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
occam-lmy48t # fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.07.img
sending 'radio' (45537 KB)...
OKAY [ 1.445s]
writing 'radio'...
OKAY [ 2.540s]
finished. total time: 3.986s
occam-lmy48t # fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
occam-lmy48t # fastboot -w update image-occam-lmy48t.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 6189744128
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 23612
Label:
Blocks: 1511168
Block groups: 47
Reserved block group size: 375
Created filesystem with 11/378256 inodes and 50366/1511168 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.07
Serial Number........: 002fff0a560d4e29
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6448 KB)...
OKAY [ 0.211s]
writing 'boot'...
OKAY [ 0.337s]
sending 'recovery' (7008 KB)...
OKAY [ 0.237s]
writing 'recovery'...
OKAY [ 0.401s]
erasing 'system'...
OKAY [ 0.813s]
sending 'system' (834934 KB)...
OKAY [ 28.409s]
writing 'system'...
OKAY [ 47.296s]
erasing 'userdata'...
OKAY [ 1.400s]
sending 'userdata' (98413 KB)...
OKAY [ 3.401s]
writing 'userdata'...
OKAY [ 5.233s]
erasing 'cache'...
OKAY [ 0.056s]
sending 'cache' (10984 KB)...
OKAY [ 0.377s]
writing 'cache'...
OKAY [ 0.629s]
rebooting...
finished. total time: 88.871s
Rebooted and sitting on the booting screen with four coloured dots swirling around. Off to bed, will see if anything has happened tomorrow. Thanks again.
I think when this happened to be I had the wrong modem radio , I flash a new one appropriate for 5.1 and I was working after that.
Left it over night and still stuck on the boot animation.
Any more suggestions/ideas of things to try would be very welcome, but its looking like this phone has given up the ghost which is a bit of a shame as it would have made a nice backup.
Sadly, I don't have any other ideas.
In any case, good luck fixing it!
Thanks for your suggestions and help, appreciated.
cloneman1 said:
I think when this happened to be I had the wrong modem radio , I flash a new one appropriate for 5.1 and I was working after that.
Click to expand...
Click to collapse
Do you happen to have details of which modem radio you used? Not much for me to go on otherwise.
I've tried the official stock ROM from Google as theminikiller suggested and would expect that to have the correct modem radio included within it (which for 5.1.1 was the file radio-mako-m9615a-cefwmazm-2.0.1701.07.img that was bundled in with occam-lmy48t-factory-416938f1.tgz).
enilkcals said:
Thanks for your suggestions and help, appreciated.
Click to expand...
Click to collapse
hi i too had a similar issue.it was somewhat similar.my battery was dying.i tried installing stock rom.it never gotten past optimising apps screen.i tried some custom rom without gapps which booted fine. i used it a few days without gapps then the battery eventually died.it couldnt get past bootanimation.it can however stay in stock/twrp recovery.
so if you can try booting up the phone with a charger connected then the battery may be the issue. if it still didnt bootup go to a local service center ask them to open up nd remove battery and connect it directly to a power source in battery terminals.if the phone boots up fine you can order a new oem battery.[emoji3]
Sent from my Nexus 4 using Tapatalk
jaison thomas said:
hi i too had a similar issue.it was somewhat similar.my battery was dying.i tried installing stock rom.it never gotten past optimising apps screen.i tried some custom rom without gapps which booted fine. i used it a few days without gapps then the battery eventually died.it couldnt get past bootanimation.it can however stay in stock/twrp recovery.
so if you can try booting up the phone with a charger connected then the battery may be the issue. if it still didnt bootup go to a local service center ask them to open up nd remove battery and connect it directly to a power source in battery terminals.if the phone boots up fine you can order a new oem battery.[emoji3]
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for the suggestion, I have already tried booting with the charger plugged in (both USB from cable and a micro-USB charger from the mains).
I sent the phone back to LG last year and had the battery replaced under warranty then (just checked and last email communication was 2014-10-22) having bought the phone 2013-08-17. I guess since thats about a year its not unreasonable to think the battery could be worn out again. Not sure whether LG will replace under warranty and wary of throwing cash down the drain, but might see if can find one and replace it.
Thanks for the idea.
slackline
Hi,
Had a very similar thing happen to me. Turned out the radio was dying - something basic about loading firmware to it during very early hardware boot up.
Figured this out after a long process - and solution was to keep on soft rebooting it until the firmware loaded successfully - then Android booted ok - otherwise it would hang at starting apps.
James
enilkcals said:
Hi,
Thanks for the suggestion, I have already tried booting with the charger plugged in (both USB from cable and a micro-USB charger from the mains).
I sent the phone back to LG last year and had the battery replaced under warranty then (just checked and last email communication was 2014-10-22) having bought the phone 2013-08-17. I guess since thats about a year its not unreasonable to think the battery could be worn out again. Not sure whether LG will replace under warranty and wary of throwing cash down the drain, but might see if can find one and replace it.
Thanks for the idea.
slackline
Click to expand...
Click to collapse
Related
I think i may have bricked my nexus 10.. I was trying to install the chainfire3d application from the market, and when it rebooted, it wouldnt go past the X logo. waited for a long time, so i tried a hard reset, and still nothing. So i figured i would try using the toolkit to help fix. tried to relock, flash, and re-unlock, and it wouldnt work..after the step where you go into factory reset/wipe, it woudlnt go further. I cant get a custom recovery to install, it wont save the file. tried doing that step separately, and it seems to stick on sending the file over. this seems to be a common issue with anything i try.
The screen says:
"sending TWRP touch recovery..
sending 'recovery' (7246 KB) ...
and is just stuck there. this seems to happen in several places, with a few different things ive tried. When trying to flash the stock image, it will get stuck in similar places, perhaps not with the recovery step, but with a portion of the stock image. Been at this for a couple of hours... any help would be greatly appreciated!.
Also, as of now... it wont boot past the google logo. I can get it into fastboot by holding down the buttons, and I can get it into the stock recovery, but thats it. I don't even think adb is detecting the device. I have a feeling that may be a major roadblock to getting this thing fixed. Does anyone know how I can get the tablet to be detected by adb if i cant even get past the google logo screen at boot?
Update 1:
Still cant unbrick my device. any time i try to transfer or flash files to it... it stalls, and if i disconnect the device, i get this error:
FAILED (data transfer failure (too many links)).
Your Device will now boot into Android and detect ADB mode.
problem is, it doesnt reboot, and even if it did, it wouldnt be able to boot into android, since it wont go past the google logo when the device turns on. in fact, i cant even turn it off. only way to turn it off would be to wait for the battery to drain.
If this helps, here is what it says on the fastboot screen:
Device Information
Product Name: manta
Variant: wifi
H/W version : 8
Bootloader Version: MANTALJ12
Carrier Info: none
Serial Number: *********** (not going to publish that, lol)
LOCK STATE: Unlocked
Reboot Mode Flag: none.
anyone have any ideas at all how I can salvage this thing? Im kindof embarrassed honestly. Ive had 5 android devices prior to this one, and have rooted, flashed, and reflashed each of them countless times, and never, ever ran into this before. I could really use the help.
Quick note:
I just noticed that when i try to flash anything to the tablet, the following appears under the rest of the info i listed above.
FASTBOOT STATUS - DATA00713800 (this text is highlighted in light blue)
Update 2:
ok, so i tried to do the factory restore, and am running into the same wall as always. here is the text from the window, perhaps that may clue you into the problem:
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.tg
z
Extracting mantaray-jop40c-factory-0d641789.tar
Everything is Ok
Size: 329369600
Compressed: 326396069
Now extracting flashable Images
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.ta
r
Extracting mantaray-jop40c
Extracting mantaray-jop40c\image-mantaray-jop40c.zip
Extracting mantaray-jop40c\flash-base.sh
Extracting mantaray-jop40c\bootloader-manta-mantalj12.img
Extracting mantaray-jop40c\flash-all.sh
Extracting mantaray-jop40c\flash-all.bat
Everything is Ok
Folders: 1
Files: 5
Size: 329358105
Compressed: 329369600
Factory Images extracted. Starting Flash Process.
Now Flashing Bootloader Image..
sending 'bootloader' (1280 KB)... OKAY [ 0.232s]
writing 'bootloader'... OKAY [ 0.113s]
finished. total time: 0.345s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
Now Flashing Factory Image: Boot, Cache, Recovery, System and Userdata..
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.002s]
sending 'boot' (4606 KB)...
Its just stuck on that last part, sending 'boot' (4606 KB)...
and under all the info on the fastboot page, the following appeared while this was happening:
FASTBOOT STATUS - DATA0047f800 (this line is highlighted in light blue)
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
can you link it?
cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
trying that....
so far so good... dont want to get my hopes up though... below is what ive got so far in the cmd screen:
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
Its been about 30 minutes now... and its still stuck on "sending 'system' (528847 KB)..." in the cmd window.... not sure what that means... it did take about a minute for the recovery to get sent over, and its about 100x larger in size, so i guess i will leave it connected like this for the next hour or so... and hope that it is just going REALLY slowly. Got my fingers crossed...
Battery died while waiting.... this is the complete text of the CMD screen while i was waiting.. forgot that it doesnt charge while in fastboot. got it plugged into an outlet for faster charging while its off.... hopefully when its charged up, i can try again and ill continue to progress
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3941.094s
Press any key to exit...
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
jodvova said:
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
Click to expand...
Click to collapse
I cant get it to load a custom recovery! any advice on how to get that going?
ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
Dumb question, if using a desktop PC are you using the front or rear USB ports? I had a similar issue where it would just get stuck on the "sending system" message. Switched the USB from front port to back port on my linux box and it solved my problem.
Sent from my Nexus 10 using Tapatalk 2
jodvova said:
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
Click to expand...
Click to collapse
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
ltracte said:
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
Click to expand...
Click to collapse
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
jodvova said:
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
Click to expand...
Click to collapse
couldnt get the command to work via adb, so i tried it using terminal inside TWRP, and this what it spit back at me:
/dev/block/platform/dw_mmc.0/by-name/system: clean. 11/51296 files. 6651/204800 blocks
i have no idea what that means, nor what else to do....
Fixed it!!!!
ltracte said:
Fixed it!!!!
Click to expand...
Click to collapse
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
mskip said:
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
Click to expand...
Click to collapse
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Whew! So glad you finally had success & thanks for sharing. I'm reading up, research, etc. I received my N10 yesterday. I'm getting ready to unlock/root today.
Sent from my Nexus 7 using Tapatalk 2
ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
Hmm, did you try the flash-all.bat file that comes with the factory image? It does those 3 commands, + erases all partitions automatically.
ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
That's exactly what I did. Just followed the factory image flashing instruction on google's page(where you download the image file for N10). Did you figure out why it wassnt able to transfer the first time?
Everytime I install TWRP and boot into it. It shows Zero internal storage and when I reboot it outlines there isnt an OS installed.
The system OS isnt wiped (although I thought that the first 50 times). When I enter fastboot again TWRP inst installed.
No idea what going on... tried latest and previous TWRP files.
thanks in advance
Heres the Log
-------------
Z:\NewNexus7Root\platform-tools>adb reboot bootloader
Z:\NewNexus7Root\platform-tools>fastboot flash recovery twrp-2.8.7.0-flo.img
sending 'recovery' (8956 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.271s]
finished. total time: 0.564s
Z:\NewNexus7Root\platform-tools>adb reboot recovery
error: device not found
error: device not found
Got it working after I found the MultiRom fix on this site.
Seems I had one of those unique "locked down" Nexus's 2013; mines from Amazon.
FIXED
Hi all! Been a member of XDA for a few years now, but only just had the pleasure of becoming a nexus user. Yesterday I decided to install the Android N preview to try it out, but decided I didn't want it on my phone. So when I got home, I wiped the phone and proceeded to flash the factory image, but no matter which image I flash it, it says "error: update package missing system.img". I have tried manually flashing each file in fastboot as I have seen in many threads, but nothing is working. I have tried restoring old TWRP backups and flashing custom ROMs in TWRP, but nothing is working. Help!
This is what the Command Prompt is saying:
sending 'bootloader' (3526 KB)...
OKAY [ 0.106s]
writing 'bootloader'...
OKAY [ 0.206s]
finished. total time: 0.314s
rebooting into bootloader...
OKAY [ 0.118s]
finished. total time: 0.119s
< waiting for device >
sending 'radio' (48600 KB)...
OKAY [ 1.151s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.327s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1733501396 bytes
error: update package missing system.img
Press any key to exit...
Did you download the right image from here?
Are you following THIS guide, TO THE LETTER?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Specifically step 10
irule311 said:
Did you download the right image from here?
Click to expand...
Click to collapse
Yep, straight from the Angler section. I've tried the latest one, as well as a few older ones. Nothing.
Soulfly3 said:
Are you following THIS guide, TO THE LETTER?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Specifically step 10
Click to expand...
Click to collapse
Hi, I followed the steps exactly, before updating my 6P to N developer preview, I had previously flashed the factory image. Thanks!
Unzip it yourself and flash em each manually.
Make sure you have the lastest fastboot tools. Im going to go out on a limb and say yours are out of date
Rxpert said:
Unzip it yourself and flash em each manually.
Make sure you have the lastest fastboot tools. Im going to go out on a limb and say yours are out of date
Click to expand...
Click to collapse
Tried that as well. Everything flashes, except the system.img.
g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
Had the same problem when ai first got it.
Wugs toolkit fixed me up!
http://forum.xda-developers.com/nexus-6p/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258493
The logs make me feel like the file you downloaded is corrupted. Check the md5 maybe?
Sent from my Nexus 6P using Tapatalk
g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
Probably a corrupt download, did you check the MD5 after downloading?
g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
It looks like you are not in the directory with the boot.img, et al. (your post shows no boot.img,, ... ) Make sure you unzipped the image. There are 2 files you need to unzip, the one containing the bootloader and radio. In that unzipped folder will be another zip. Unzip that second folder and you'll see the boot.img, cache.img, et al. The change in to that folder from your terminal or move those files into the folder you created (if following Heisenberg's guide), then proceed.
g4slyness said:
Hi all! Been a member of XDA for a few years now, but only just had the pleasure of becoming a nexus user. Yesterday I decided to install the Android N preview to try it out, but decided I didn't want it on my phone. So when I got home, I wiped the phone and proceeded to flash the factory image, but no matter which image I flash it, it says "error: update package missing system.img". I have tried manually flashing each file in fastboot as I have seen in many threads, but nothing is working. I have tried restoring old TWRP backups and flashing custom ROMs in TWRP, but nothing is working. Help!
This is what the Command Prompt is saying:
sending 'bootloader' (3526 KB)...
OKAY [ 0.106s]
writing 'bootloader'...
OKAY [ 0.206s]
finished. total time: 0.314s
rebooting into bootloader...
OKAY [ 0.118s]
finished. total time: 0.119s
< waiting for device >
sending 'radio' (48600 KB)...
OKAY [ 1.151s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.327s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1733501396 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
I think you are using an old version of fastboot. Update it and try again. Problem was fastboot couldn't allocate enough system ram to hold the whole image or something. In the newer fastboot the file transfer was broken in to several segments.
Maybe try another USB port too won't hurt.
Gytole said:
Had the same problem when ai first got it.
Wugs toolkit fixed me up!
http://forum.xda-developers.com/nexus-6p/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258493
Click to expand...
Click to collapse
Thanks!!! It actually worked. Not sure what was wrong before, seemed as though every file I downloaded off of the google website was corrupted. Cheers!
g4slyness said:
Thanks!!! It actually worked. Not sure what was wrong before, seemed as though every file I downloaded off of the google website was corrupted. Cheers!
Click to expand...
Click to collapse
You're welcome!
Like I said I had the same problem back in November. It ended up being an outdated version of fastboot like others have stated. I coyld flash my friends Moto X Pure but not my Nexus 6P..mit was awful and brain racking. Glad all is good!
This morning my phone (with a recent lineage nightly) was off when I got up and when I tried to turn it on it said my password was wrong, which I am positive it was not. For some reason I decided to "solve" the problem by going into TWRP and wiping/formating everything (including system) and then installing a fresh copy of lineage, and flashing the bootloader and vendor. Once I did that it started bootlooping, I could get into bootloader but not recovery. After some playing with it I found that the 4 cores modified twrp would work, so I tried installing some roms from there with no luck. Then tried flashing a variety of factory images, none of which work, including the 48C 7.12 image with the 4 cores boot image, as well as the same with the ex4.12 kernel flashed over it.
Is there anything I can do, or is it just time to shop for a new phone?
Dacull said:
This morning my phone (with a recent lineage nightly) was off when I got up and when I tried to turn it on it said my password was wrong, which I am positive it was not. For some reason I decided to "solve" the problem by going into TWRP and wiping/formating everything (including system) and then installing a fresh copy of lineage, and flashing the bootloader and vendor. Once I did that it started bootlooping, I could get into bootloader but not recovery. After some playing with it I found that the 4 cores modified twrp would work, so I tried installing some roms from there with no luck. Then tried flashing a variety of factory images, none of which work, including the 48C 7.12 image with the 4 cores boot image, as well as the same with the ex4.12 kernel flashed over it. Is there anything I can do, or is it just time to shop for a new phone?
Click to expand...
Click to collapse
Have you tried the workaround of disabling big cores with EX Kernel? There is an XDA thread dedicated to it. From your post I'm not sure if you disabled the cores or not.
v12xke said:
Have you tried the workaround of disabling big cores with EX Kernel? There is an XDA thread dedicated to it. From your post I'm not sure if you disabled the cores or not.
Click to expand...
Click to collapse
I didn't, I thought it has already been done. But now even the 4 core twrp just gives me a splash screen followed by a momentary page of text and then crash.
Edit: Nevermind, I misunderstood you. I installed the EX kernel from this thread.
I also just managed to somehow override whatever was crashing twrp by pushing the power button right when the text screen was showing. Flashed the EX kernel again, but still not working. I'm thinking the problem is something more than/other than the regular bootloop issue, but it is odd that only the 4 cores twrp will work.
Did you flash boot?
ItsMason said:
Did you flash boot?
Click to expand...
Click to collapse
In the most recent effort I flashed the entire n2g48c factory image but substituted the 4 cores boot image and 4 cores twrp recovery, then once I managed to get into twrp I installed the EX kernel from the thread listed above. Now, after that, it will bootloop once and then try to boot twrp which still crashes after showing the splash screen.
Dacull said:
In the most recent effort I flashed the entire n2g48c factory image but substituted the 4 cores boot image and 4 cores twrp recovery, then once I managed to get into twrp I installed the EX kernel from the thread listed above. Now, after that, it will bootloop once and then try to boot twrp which still crashes after showing the splash screen.
Click to expand...
Click to collapse
Try to fastboot FORMAT Boot, System and Userdata to see if they will format without errors. You may have a hardware issue (eg. bad eMMC). If so, the formatting process will not complete and give you a specific error code. If these 3 all complete, then flash a full image using flash-all.bat.
v12xke said:
Try to fastboot FORMAT Boot, System and Userdata to see if they will format without errors. You may have a hardware issue (eg. bad eMMC). If so, the formatting process will not complete and give you a specific error code. If these 3 all complete, then flash a full image using flash-all.bat.
Click to expand...
Click to collapse
This is what I got, I'm guessing the response on "boot" might be related to the problem?
Code:
[[email protected] angler-n2g48c]$ sudo fastboot format boot
[sudo] password for cullen:
Formatting is not supported for file system with type ''.
[[email protected] angler-n2g48c]$ sudo fastboot format system
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
Creating filesystem with parameters:
Size: 3221225472
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 12288
Label:
Blocks: 786432
Block groups: 24
Reserved block group size: 191
Created filesystem with 11/196608 inodes and 25785/786432 blocks
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.557s]
sending 'system' (52216 KB)...
OKAY [ 1.941s]
writing 'system'...
OKAY [ 0.732s]
finished. total time: 3.231s
[[email protected] angler-n2g48c]$ sudo fastboot format userdata
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
target reported max download size of 494927872 bytes
erasing 'userdata'...
OKAY [ 0.640s]
sending 'userdata' (141002 KB)...
OKAY [ 5.181s]
writing 'userdata'...
OKAY [ 2.109s]
finished. total time: 7.930s
Dacull said:
This is what I got, I'm guessing the response on "boot" might be related to the problem?
Click to expand...
Click to collapse
Something is up with boot. Have you tried manually flashing just the Boot.img? Sorry I meant format System, Cache & Userdata. Did you then flash a full image with flash-all.bat? Was there any error on the Cache partition? If you still can't successfully enter Recovery, you could try to fastboot boot TWRP it rather than fastboot flashing. If you can access a stable Recovery you then have ADB and can sideload, etc.
v12xke said:
Something is up with boot. Have you tried manually flashing just the Boot.img? Sorry I meant format System, Cache & Userdata. Did you then flash a full image with flash-all.bat? Was there any error on the Cache partition? If you still can't successfully enter Recovery, you could try to fastboot boot TWRP it rather than fastboot flashing. If you can access a stable Recovery you then have ADB and can sideload, etc.
Click to expand...
Click to collapse
I cache formated ok. I have been flashing everything manually, including boot, since flash-all.sh ends on an error, but manually flashing seems to work fine.
Here's the output from flash-all.sh
Code:
[[email protected] angler-n2g48c]$ sudo ./flash-all.sh
target reported max download size of 494927872 bytes
sending 'bootloader' (3544 KB)...
OKAY [ 0.152s]
writing 'bootloader'...
OKAY [ 0.209s]
finished. total time: 0.361s
rebooting into bootloader...
OKAY [ 0.022s]
finished. total time: 0.072s
target reported max download size of 494927872 bytes
sending 'radio' (48728 KB)...
OKAY [ 1.862s]
writing 'radio'...
OKAY [ 2.164s]
finished. total time: 4.026s
rebooting into bootloader...
OKAY [ 0.022s]
finished. total time: 0.072s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
W/ziparchive( 3437): Zip: unable to allocate 2860210996 bytes at offset 0 : No space left on device
failed to extract 'system.img': I/O Error
I was able to get a stable twrp using the 4 cores twrp and fastboot boot twrp, what would I want to sideload in this situation? The ota for the whatever version I just flashed?
Dacull said:
I cache formated ok. I have been flashing everything manually, including boot, since flash-all.sh ends on an error, but manually flashing seems to work fine.
I was able to get a stable twrp using the 4 cores twrp and fastboot boot twrp, what would I want to sideload in this situation? The ota for the whatever version I just flashed?
Click to expand...
Click to collapse
Have you updated fastboot/adb recently? I don't use the whole SDK, just the stand alone binaries. Some older versions weren't able to handle the multiple system packages.... but..... I/O error sounds like bad memory to me. The current versions were published 12-May-17. On the adb, I was just going to suggest flashing SU because it modifies boot and if it found something it wasn't expecting you may receive a better error message. Now sounding more like bad onboard memory. I don't think you have a valid system partition so maybe why it's not booting. Just a guess. Many ppl with BLOD have reported manually flashing completes with no error yet the OS won't boot.
Ok, I was running a slightly older version of fastboot, but I get the exact same results after switching to the latest binary, so it looks like the phones just toast. Huge thanks for all the help, even if it didnt end up working.
Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>adb reboot bootloader
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.017s]
writing 'vbmeta'...
OKAY [ 0.036s]
finished. total time: 0.073s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot erase system
erasing 'system'...
OKAY [ 37.155s]
finished. total time: 37.169s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash system system.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 13.484s]
writing 'system' 1/4...
OKAY [ 4.426s]
sending sparse 'system' 2/4 (456612 KB)...
OKAY [ 14.049s]
writing 'system' 2/4...
OKAY [ 3.476s]
sending sparse 'system' 3/4 (460796 KB)...
OKAY [ 13.959s]
writing 'system' 3/4...
OKAY [ 3.582s]
sending sparse 'system' 4/4 (173628 KB)...
OKAY [ 5.140s]
writing 'system' 4/4...
OKAY [ 1.580s]
finished. total time: 59.786s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.711s]
finished. total time: 1.719s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot reboot
rebooting...
finished. total time: 0.043s
Click to expand...
Click to collapse
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!
Traijan said:
Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!
Click to expand...
Click to collapse
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson
Supplement...the Part with the vbmeta is not necessary as far as i know.
solong
speedson
speedson said:
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson
Click to expand...
Click to collapse
Hey, I used the default rom installed on my huawei p10 lite.
I did a complete clean install yet.
Before that I used twrp to install it (because I thought it worked with .img) and after that I startet from a clean install of the default rom again and did the linked tutorial.
I'm not root on this device, I just have a unlocked bootloader.
I also didn't encrypted my internal storage. Do I have to do it?
What you mean with not reboot to bootloader? I did the commands in the link on fastboot (holding vol - and connect to pc)
Do you have an idea what I can do? I really would like to test android 12.
A good place to start when figuring out why no rom install's in my system-as-root...
Back to stock it is...