Today I was facing a 4.4.3 issue so I've thought about doing a factory reset to see if this fixes it. So I've gone into Recovery and run a factory reset. Strangely this was taking so long, so after 2 hours I've decided to stop it. I know that stopping this process is not recommended, but I've considered it was getting out of the reasonable range. I've rerun it and same problem, so after 3 hours I've stopped it. And I've thought about restoring the factory image. Unfortunately the process get stuck in the "erasing cache" step:
Code:
# ./flash-all.sh
sending 'bootloader' (2508 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
OKAY [ 0.452s]
finished. total time: 0.749s
rebooting into bootloader...
OKAY [ 0.131s]
finished. total time: 0.132s
sending 'radio' (45409 KB)...
OKAY [ 1.614s]
writing 'radio'...
OKAY [ 3.102s]
finished. total time: 4.716s
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...: HHZ11k
Baseband Version.....: M8974A-2.0.50.1.13
Serial Number........: 063b7fa3f0d88342
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8700 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.740s]
sending 'recovery' (9284 KB)...
OKAY [ 0.540s]
writing 'recovery'...
OKAY [ 0.776s]
erasing 'system'...
OKAY [ 1.074s]
sending 'system' (721400 KB)...
OKAY [ 23.132s]
writing 'system'...
OKAY [ 49.064s]
erasing 'userdata'...
OKAY [ 13.622s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
sending 'userdata' (139109 KB)...
writing 'userdata'...
OKAY [ 13.895s]
erasing 'cache'...
I'm afraid that even if I let it work for hours it'll be stuck forever. What can I do? What could be happening? Any suggestions? Thank you!
Just fastboot flash the cache image manually without erasing it.
fastboot flash cache cache.img
Sent from my Nexus 5 using Tapatalk
Thank you, the command works well:
Code:
# fastboot flash cache image/cache.img
erasing 'cache'...
OKAY [ 0.513s]
sending 'cache' (13348 KB)...
OKAY [ 0.640s]
writing 'cache'...
OKAY [ 1.075s]
finished. total time: 2.228s
[email protected]:/home/jpabloae/Descargas/hammerhead-ktu84m# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
After that and following this tutorial for flashing the factory image (Method 2) I select "Recovery" and then press Power Button + Volume UP when the small Android appears. When I do that the small Android gets grey and it outputs "Formatting /data...", but it doesn't finish. I'm not sure what could be happening, any ideas?
What is your ultimate goal?
Sent from my Nexus 5 using Tapatalk
rootSU said:
What is your ultimate goal?
Click to expand...
Click to collapse
To boot a fresh stock 4.4.3.
To be unrooted forever?? What about bootloader?
Sent from my Nexus 5 using Tapatalk
rootSU said:
To be unrooted forever?? What about bootloader?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well, as a first step I'd like to at least have the phone functional.
These are all the steps I've followed (the bootloader is unlocked):
Code:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.13.img
fastboot reboot-bootloader
sleep 5
fastboot flash system image/system.img
fastboot flash userdata image/userdata.img
fastboot flash boot image/boot.img
fastboot flash recovery image/recovery.img
fastboot flash cache image/cache.img
And then what I said before: select "Recovery" and then press Power Button + Volume UP. And it get stuck on "Formatting /data...".
I don't know what the recovery is doing. Try and flash a custom recovery like philz or twrp. Then fast boot flash it
Then fastboot flash the system, boot, cache and userdata and then see what happens.. If it boots etc
By boot,, I mean kernel
Sent from my Nexus 5 using Tapatalk
I've been able to recover the phone back to stock with TWRP. You've been really helpful, thank you!
One last question: how does one manage to return to a stock image, stock recovery, locked and untampered device? Following these steps I'm able to do it all except for the recovery.
jpabloae said:
I've been able to recover the phone back to stock with TWRP. You've been really helpful, thank you!
One last question: how does one manage to return to a stock image, stock recovery, locked and untampered device? Following these steps I'm able to do it all except for the recovery.
Click to expand...
Click to collapse
Those steps are for someone who has returned to stock and forgotten to reset the tamper flag, so the recovery they are flashing is a custom one.
Full normal instructions are linked in my signature
rootSU said:
Full normal instructions are linked in my signature
Click to expand...
Click to collapse
I might be missing something, but on the signature's guide, in the last step (Locking your bootloader+ Resetting the tamper flag) it uses TWRP to install the zip file that resets the temper flag, and this process lockes the bootloader as well. I mean, after doing this you don't end up with the stock recovery but with TWRP.
jpabloae said:
I might be missing something, but on the signature's guide, in the last step (Locking your bootloader+ Resetting the tamper flag) it uses TWRP to install the zip file that resets the temper flag, and this process lockes the bootloader as well. I mean, after doing this you don't end up with the stock recovery but with TWRP.
Click to expand...
Click to collapse
In the steps he doesn't flash TWRP. He boots to it.
fastboot boot recovery.img
as opposed to
fastboot flash recovery recovery.img
That means you have stock recovery already installed at that point and you do not replace it.
There is also an app called BootUnlocker, which resets the taper flag from within android (With root) so you can just use that. I use that and mine is constantly showing as not tampered
rootSU said:
In the steps he doesn't flash TWRP. He boots to it.
Click to expand...
Click to collapse
You're absolutely right, I took it for granted it was necessary to flash it before using it. My phone is now 100% recovered, thank you so much!
jpabloae said:
You're absolutely right, I took it for granted it was necessary to flash it before using it. My phone is now 100% recovered, thank you so much!
Click to expand...
Click to collapse
No probs
Related
Hi guys,
I know it sounds like one of many threads already created here.
I have read a bunch of them and the information sounds a bit contradictory or at least I'm unsure.
My Nexus S i9020 has sunk in salt water. I washed it in distilled water then gave it two weeks in a dry, warm environment.
When I try to turn it on I see a menu which is asking do I want to unlock a bootloader or not.
While on Power + Volume Up I can get into recovery menu. When I choose reboot I can see a Google logo with no progress. Pressing the Power button doesn't turn the phone off so I have to take the battery out. But power off through the menu works fine.
I installed necessary drivers / bits of SDK on Windows 7. ADB doesn't see the phone but fastboot does, so I can turn the phone off or can try to reboot it from PC. Looks like USB debugging is off.
Now the question is: can I actually turn it on without unlocking a bootloader? Can I _run_ CWM without unlocking a bootloader?
If not are there other options to turn USB debugging on?
If there are no options and I have to unlock a bootloader, would it 100% kill the data on memory card?
If it will is there any chance to restore it afterwards? If so, how can I do that?
Or should I just forget about it?
Thank you!
First try to flash the factory system.img and boot.img through fastboot, don't wipe and only flash these, you may be able to get in and recover data this way.
If not and you want to try a custom recovery to the best of my knowledge you will need to unlock bootloader which will erase all data
There is a chance that you can still recovery some though, there are apps in the market (disc digger?)
But know that more than likely you won't get anything back
Best of luck though!
demkantor said:
First try to flash the factory system.img and boot.img through fastboot, don't wipe and only flash these, you may be able to get in and recover data this way.
If not and you want to try a custom recovery to the best of my knowledge you will need to unlock bootloader which will erase all data
There is a chance that you can still recovery some though, there are apps in the market (disc digger?)
But know that more than likely you won't get anything back
Best of luck though!
Click to expand...
Click to collapse
Hi demkantor,
Thanks a lot for reply!
Before I kill it completely... :cyclops: How do I find out which image I need to download?
I obviously need 4.1.2 one but do I need "soju" for Nexus S (worldwide version, i9020t and i9023) or "sojua" for Nexus S (850MHz version, i9020a)?
The phone I have is the UK version, as far as I remember (I'll double check it later) there was just i9020 on the phone, no other index.
Any ideas about this? Can device ID help here?
And after that the only thing I have to do would be:
> fastboot flash system system.img
> fastboot flash boot boot.img
> fastboot reboot
Am I right?
https://developers.google.com/android/nexus/images?csw=1
More than likely soju, since you can't get to about phone to check maybe it will say under battery or if you have original box?
And yes those are the correct commands
Best of luck!
Hi demkantor,
This is what I see in fastboot mode:
PRODUCT NAME - HERRING
HW VERSION - REW 11
BOOTLOADER VERSION - I9020XXLC2
BASEBAND VERSION - I9020XXKI1
CARRIER INFO - EUR
According to android-info.txt from soju-jzo54k-factory-36602333.tgz everything is fine so i downloaded it, extracted system.img and boot.img and tried to flash them with fastboot.
Unfortunately I got this:
C:\android-sdk-windows> fastboot flash system system.img
sending 'system' (337443 KB)... OKAY [ 53.034s]
writing 'system'... FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 53.035s
C:\android-sdk-windows> fastboot flash boot boot.img
sending 'boot' (3964 KB)... OKAY [ 0.621s]
writing 'boot'... FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.622s
Looks like whatever I want to flash I still have to unlock the bootloader. Any other ideas?
Can I boot into CWM without flashing and turn USB debugging on from there?
You can try to just boot the recovery but its unlikely
fastboot boot nameofrecovery.img
That will probably fail too, my guess is you'll end up having to unlock bootloader or run the flashall.bat but either way will do a full wipe, there is the slight chance there are apps in the play store that can recover some stuff if you run them right away but I can't recall if unlocking the bootloader is a format or a wipe (format being much less likely to recover)
demkantor said:
You can try to just boot the recovery but its unlikely
fastboot boot nameofrecovery.img
That will probably fail too, my guess is you'll end up having to unlock bootloader or run the flashall.bat but either way will do a full wipe, there is the slight chance there are apps in the play store that can recover some stuff if you run them right away but I can't recall if unlocking the bootloader is a format or a wipe (format being much less likely to recover)
Click to expand...
Click to collapse
Yep looks like it is very unlikely that I will be able to do it without unlocking. I've seen a thread somewhere where the guy was in the same situation and he had to unlock the bootloader but after that was able to restore the data.
Okay then, I'll dig on this a bit more and then try it out. Thanks a lot!
Okay. So finally I had to try unlocking a bootloader and flashing the phone with flash-all.bat script.
The log looks like this
Code:
c:\android-sdk-windows\soju-jzo54k>flash-all.bat
sending 'bootloader' (1536 KB)... OKAY [ 0.241s]
writing 'bootloader'... OKAY [ 0.355s]
finished. total time: 0.597s
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)... OKAY [ 1.925s]
writing 'radio'... OKAY [ 1.740s]
finished. total time: 3.665s
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'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: SERIAL
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.001s]
checking version-baseband... OKAY [ 0.001s]
sending 'boot' (3964 KB)... OKAY [ 0.620s]
writing 'boot'... OKAY [ 0.520s]
sending 'recovery' (4308 KB)... OKAY [ 0.674s]
writing 'recovery'... OKAY [ 0.565s]
sending 'system' (337443 KB)... OKAY [ 52.764s]
writing 'system'... OKAY [ 37.667s]
erasing 'userdata'... OKAY [ 0.185s]
erasing 'cache'... OKAY [ 1.999s]
rebooting...
finished. total time: 95.001s
After rebooting the phone I got the same problem i.e. it's stuck on Google logo. The same result I get when I insert the battery while the phone is unplugged from PC. But if I press Volume Up + Power (while disconnected from PC) I get a yellow triangle and the text "Downloading... Do not turn off the target".
Data is lost. Fine. Any ideas what could be done in order to make the phone bootable?
Try wiping through fastboot and then flashing the images one by one (instead of the flash all.bat)
This may help
http://forum.xda-developers.com/showthread.php?t=2277112
I seem to be having a ton of issues after getting my phone back from my wife. I can't get /data/ to mount unless I format it as FAT, but it won't format as ext4 or anything else. I tried flashing stock, but no dice. I did manage to get PA and CM up and running but I get a message telling me my storage is encrypted, and I definitley don't have a password. Factory resets dont help because if it tries to format /data/ it'll never finish. I let it run for hours even.
Is there any creative ideas I can try? I really can't afford a new phone, so I need to get this fixed, and I was defintley under the impression that if you can get into bootloader/recovery, then it is not bricked .
Zarilenth said:
I seem to be having a ton of issues after getting my phone back from my wife. I can't get /data/ to mount unless I format it as FAT, but it won't format as ext4 or anything else. I tried flashing stock, but no dice. I did manage to get PA and CM up and running but I get a message telling me my storage is encrypted, and I definitley don't have a password. Factory resets dont help because if it tries to format /data/ it'll never finish. I let it run for hours even.
Is there any creative ideas I can try? I really can't afford a new phone, so I need to get this fixed, and I was defintley under the impression that if you can get into bootloader/recovery, then it is not bricked .
Click to expand...
Click to collapse
fastboot flash userdata userdata.img
It'll wipe data and internal storage but it's the easiest way.
Lethargy said:
fastboot flash userdata userdata.img
It'll wipe data and internal storage but it's the easiest way.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata.img
erasing 'userdata'...
OKAY [ 2.031s]
sending 'userdata' (137318 KB)...
OKAY [ 4.547s]
writing 'userdata'...
OKAY [ 8.884s]
finished. total time: 15.494s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I tried it and then tried fastboot update image-hammerhead-lpv79.zip and now it is hanging at erasing 'system'
Zarilenth said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata.img
erasing 'userdata'...
OKAY [ 2.031s]
sending 'userdata' (137318 KB)...
OKAY [ 4.547s]
writing 'userdata'...
OKAY [ 8.884s]
finished. total time: 15.494s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I tried it and then tried fastboot update image-hammerhead-lpv79.zip and now it is hanging at erasing 'system'
Click to expand...
Click to collapse
Close and just try running flash-all.bat/sh
Lethargy said:
Close and just try running flash-all.bat/sh
Click to expand...
Click to collapse
Now it is hanging at erasing 'cache'
< waiting for device >
sending 'bootloader' (2508 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
OKAY [ 0.484s]
finished. total time: 0.781s
rebooting into bootloader...
OKAY [ 0.078s]
finished. total time: 0.078s
sending 'radio' (45505 KB)...
OKAY [ 1.563s]
writing 'radio'...
OKAY [ 3.114s]
finished. total time: 4.693s
rebooting into bootloader...
OKAY [ 0.078s]
finished. total time: 0.078s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-2.0.50.2.08
Serial Number........: 0651fd67006b5ff4
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
OKAY [ 0.094s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (8754 KB)...
OKAY [ 0.484s]
writing 'boot'...
OKAY [ 0.750s]
sending 'recovery' (9412 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.781s]
erasing 'system'...
OKAY [ 1.250s]
sending 'system' (683564 KB)...
OKAY [ 21.820s]
writing 'system'...
OKAY [ 46.359s]
erasing 'userdata'...
OKAY [ 2.125s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
sending 'userdata' (137318 KB)...
writing 'userdata'...
OKAY [ 14.092s]
erasing 'cache'...
Zarilenth said:
Now it is hanging at erasing 'cache'
Click to expand...
Click to collapse
Try taking cache.img out of the zip and flash it separately?
Lethargy said:
Try taking cache.img out of the zip and flash it separately?
Click to expand...
Click to collapse
This sounded genius, I would have never thought to try this. I took it out and rezipped the folder, but it still tried to erase the cache and stopped there. Is there any way to stop it from trying to erase the cache?
Zarilenth said:
This sounded genius, I would have never thought to try this. I took it out and rezipped the folder, but it still tried to erase the cache and stopped there. Is there any way to stop it from trying to erase the cache?
Click to expand...
Click to collapse
When you flash something using fastboot it'll always erase. Try erasing cache without flashing, "fastboot erase cache"
Lethargy said:
When you flash something using fastboot it'll always erase. Try erasing cache without flashing, "fastboot erase cache"
Click to expand...
Click to collapse
I erased it and formatted it.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
< waiting for device >
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.637s]
finished. total time: 0.651s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format cache
erasing 'cache'...
OKAY [ 0.526s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 2.118s]
finished. total time: 2.669s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Zarilenth said:
I erased it and formatted it.
Click to expand...
Click to collapse
Reflash and see if it works?
Lethargy said:
Reflash and see if it works?
Click to expand...
Click to collapse
No still stuck at erasing 'cache'
Zarilenth said:
No still stuck at erasing 'cache'
Click to expand...
Click to collapse
Lg flashtool? Check my signature.
Zarilenth said:
No still stuck at erasing 'cache'
Click to expand...
Click to collapse
Weird then. Try using LG Flashtool. You can find it in the first link of my signature
---------- Post added at 07:28 AM ---------- Previous post was at 07:24 AM ----------
bitdomo said:
Lg flashtool? Check my signature.
Click to expand...
Click to collapse
Damn. xD
Lethargy said:
Weird then. Try using LG Flashtool. You can find it in the first link of my signature
---------- Post added at 07:28 AM ---------- Previous post was at 07:24 AM ----------
Damn. xD
Click to expand...
Click to collapse
I followed the steps very closely it got to 6% and then froze saying userdata erase fail
Zarilenth said:
I followed the steps very closely it got to 6% and then froze saying userdata erase fail
Click to expand...
Click to collapse
Try locking your bootloader:
fastboot oem lock
Then reboot it with:
fastboot reboot-bootloader
If it still shows as unlocked after the reboot, then your eMMC is dead/damaged and there isn't much you can do other than RMA or motherboard replacement
Lethargy said:
Try locking your bootloader:
fastboot oem lock
Then reboot it with:
fastboot reboot-bootloader
If it still shows as unlocked after the reboot, then your eMMC is dead/damaged and there isn't much you can do other than RMA or motherboard replacement
Click to expand...
Click to collapse
I am able to oem lock and unlock no problem. Should I be locked or unlocked for lg flashtool?
Zarilenth said:
I am able to oem lock and unlock no problem. Should I be locked or unlocked for lg flashtool?
Click to expand...
Click to collapse
I haven't had to use it myself yet so I'm not sure. Just go with unlocked anyways. Try it once more, if it doesn't work then I'm not sure whats up with your device.
Lethargy said:
I haven't had to use it myself yet so I'm not sure. Just go with unlocked anyways. Try it once more, if it doesn't work then I'm not sure whats up with your device.
Click to expand...
Click to collapse
I tried locked and unlocked and no go. I guess it's actually unfixable. What a waste of time.
I would ask Google for a replacement, but I am guessing that's not going to be free with all the tampering I did, and plus I live in Canada now, after buying it in the States.
Zarilenth said:
I tried locked and unlocked and no go. I guess it's actually unfixable. What a waste of time.
I would ask Google for a replacement, but I am guessing that's not going to be free with all the tampering I did, and plus I live in Canada now, after buying it in the States.
Click to expand...
Click to collapse
If you bought from the Play Store they'll replace it regardless any tampering, if its a real hardware fault. If you know anybody in the US you should be able to send it to them to RMA. Not sure if you can give Google a call from Canada if you bought it in the US, though
Wow. Google was so nice when I called. They're going to replace it for free and do shipping to and from Canada, because I did buy it from the US Play Store. Thanks for your help Lethargy. So glad to not have to try anything anymore.
I have a Moto G (XT1032) running Android 5.0.2 that went out of charge one day. It then decided to boot into a black screen - i.e. I can see the Motorola splash screen (animation) but all I get after that is a black (grey) screen, not responsive to touch.
I tried a few things and they didn't work -
Fastbooted and selected 'Recovery' option - The Motorola logo (first screen of startup splash screen) appears briefly. Then the device returns to fastboot menu saying 'Boot Up failed'
Fastbooted and selected 'Factory' - The Motorola splash screen appears, boots into same black (grey) screen again.
The fastboot menu says "Device is LOCKED. Status Code: 0". I did not enable USB debugging before my phone stopped working.
How do I get my phone working again?
You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Is there important data on the phone? Then do not use the command: mfastboot erase userdata
lost101 said:
You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Is there important data on the phone? Then do not use the command: mfastboot erase userdata
Click to expand...
Click to collapse
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash partition gpt.b
in
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.084s]
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.330s]
finished. total time: 0.418s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash motoboot motobo
ot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.151s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.957s]
finished. total time: 1.112s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.095s]
writing 'logo'...
OKAY [ 0.035s]
finished. total time: 0.132s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.447s]
writing 'boot'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash recovery recove
ry.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.446s]
writing 'recovery'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 9.591s]
writing 'system'...
OKAY [ 7.728s]
finished. total time: 17.323s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.955s]
writing 'system'...
OKAY [ 8.082s]
finished. total time: 17.042s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 9.657s]
writing 'system'...
OKAY [ 8.179s]
finished. total time: 17.843s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 6.347s]
writing 'system'...
OKAY [ 6.282s]
finished. total time: 12.635s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash modem NON-HLOS.
bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.943s]
writing 'modem'...
OKAY [ 0.780s]
finished. total time: 2.727s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.022s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.090s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.279s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot reboot
Click to expand...
Click to collapse
Thats all that i got... i don't know what else to do...
Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2
pradeeppk said:
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2
Click to expand...
Click to collapse
i do it, but i get the same message, "No Command"
lost101 said:
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
Click to expand...
Click to collapse
I see something wierd now, looks like the memory of the phone dosent save anything... sometimes, when the boot animation stops, i see the message of "1 of 1 Updates, android its updating" and then go to the black screen again... but, if i flash the phone, i shouldn't see that message, rigth? so, why i can still see it? how can i erase all the memory for sure???
Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img
lost101 said:
Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img
Click to expand...
Click to collapse
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja
Joncillo said:
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja
Click to expand...
Click to collapse
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/
lost101 said:
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/
Click to expand...
Click to collapse
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?
Joncillo said:
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?
Click to expand...
Click to collapse
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip
lost101 said:
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip
Click to expand...
Click to collapse
when i wipe the device, i get some errors.
E: MTP already enable
Formatting data using mkfs.f2fs...
Done
E: Unknown MTP message type 1:
You may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to stat '/data/data/com.google.android.gms/app_sslcache/www.googleapis.com.443'
E: Unable to stat '/data/data/com.google.android.calendar/databases/timelydata.db-shm'
...done
but don't wipe anything...
i try ADB Sideload but get an error too.
Starting ADB sideload feature... (After 10 minutes)
FAILED ADB Sideload complete.
and the CMD on windows says "Error: device not found"
also i try to install TWRP as zip, but when i restarted, enter into recovery and then i have the same android with error "No Command".
@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
lost101 said:
@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Click to expand...
Click to collapse
ahhhhhhhhh... i see... so, i have a dead phone... well, i'm going to try what you said in that post, thanks for all your help!!!
Hi,
A friend asked me to look at his Nexus 5.
It seemed as though his son was trying to flash a custom rom but somewhere along the way things went wrong and it got stuck on the boot animation.
I tried resetting it to factory using this thread.
Followed method 2 and finished it up with "Wipe data/factory data" reset. I did not however relock the boot loader.
I used the factory image 6.0.1 (MMB29S).
Everything went well, no errors, but even after doing all that the phone is still stuck on the boot animation. I tried redoing the "Wipe data/factory data" reset, but the phone is still stuck on boot animation.
I left for around 20 minutes with no change.
All the other threads I have read seem to indicate doing the "wipe data/factory data" reset should correct this issue but it hasn't seemed to help.
I also found this thread. The last post could possibly be another option.
Is there anything I can try? or is there a log I can look?
Any suggestions would be greatly appreciated.
Cheers
Boot the phone into fastboot and flash the userdata.img from the stock rom to the phone using the following command: fastboot flash userdata userdata.img. After flashing, boot into stock recovery using the volume and power button, wipe data and cache, reboot.
audit13 said:
Boot the phone into fastboot and flash the userdata.img from the stock rom to the phone using the following command: fastboot flash userdata userdata.img. After flashing, boot into stock recovery using the volume and power button, wipe data and cache, reboot.
Click to expand...
Click to collapse
Thanks for the reply.
I did as you suggested, unfortunately I am still stuck on boot animation.
Output from command
Code:
c:\image-hammerhead-mmb29s>fastboot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 8.014s]
sending 'userdata' (137318 KB)...
OKAY [ 4.510s]
writing 'userdata'...
OKAY [ 9.149s]
finished. total time: 21.673s
I was just looking at the contents of the zip I downloaded from the developer site. The data stamps on the images seem old. Most date back to 2009. Perhaps I have downloaded the wrong files?
Did the userdata.img file come from the mmb29s ROM? After flashing, did you immediately boot into recovery and perform a factory wipe?
audit13 said:
Did the userdata.img file come from the mmb29s ROM? After flashing, did you immediately boot into recovery and perform a factory wipe?
Click to expand...
Click to collapse
Yes the userdata.img did come from the mmb29s ROM. I have no other ROM files downloaded.
Yes I did I believe, if I recall correctly, these were my steps:
Booted phone into fastboot by pressing the power and down volume key
flashed the userdata.img using the command provided
Used the volume rocket to select "Recovery"
When the dead Android appeared I pressed the power button and up volume rocker to display the menu
Proceeded to the option to wipe and reset data
Rebooted the phone
I am pretty sure those were the steps I used.
Should I have rebooted first before going directly into Recovery?
Yup, those are the proper steps.
When you wiped in recovery, did you see a line at the bottom that said something like "invalid format" or "could not mount" just before the data and cache partitions were formatted?
audit13 said:
Yup, those are the proper steps.
When you wiped in recovery, did you see a line at the bottom that said something like "invalid format" or "could not mount" just before the data and cache partitions were formatted?
Click to expand...
Click to collapse
No I didn't notice any error messages unfortunately.
And I don't recall seeing any error messages during any of the other steps I have performed.
The commands all seem to successfully execute with no errors.
Does it at all make sense for me to go back and completely redo all the steps from the tutorial in my first post?
I can post the outputs from all the commands if you think that would at all be helpful?
I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.
audit13 said:
I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.
Click to expand...
Click to collapse
Okay perfect. I will give method 1 a try tonight (I am unfortunately at work right now).
I will report back tonight... hopefully with good news
audit13 said:
I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.
Click to expand...
Click to collapse
Sorry for the late reply on this.
I got around to doing the steps above.
Unfortunately I am still stuck on the boot animation screen.
Here is the output from the commands I ran
Code:
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.297s]
writing 'bootloader'...
OKAY [ 0.500s]
finished. total time: 0.797s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.078s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.540s]
writing 'radio'...
OKAY [ 3.125s]
finished. total time: 4.665s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.063s
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'
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
OKAY [ 0.109s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.781s]
sending 'recovery' (10012 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.828s]
erasing 'system'...
OKAY [ 1.297s]
sending 'system' (1020413 KB)...
OKAY [ 32.163s]
writing 'system'...
OKAY [ 69.508s]
erasing 'userdata'...
OKAY [ 8.326s]
sending 'userdata' (137318 KB)...
OKAY [ 4.500s]
writing 'userdata'...
OKAY [ 9.138s]
erasing 'cache'...
OKAY [ 0.672s]
sending 'cache' (13348 KB)...
OKAY [ 0.625s]
writing 'cache'...
OKAY [ 1.078s]
rebooting...
finished. total time: 130.775s
Press any key to exit...
////// -------- AFTER COMPLETE POWER OFF AND REBOOT -------- \\\\\\\\
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.625s]
finished. total time: 0.641s
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.384s]
finished. total time: 8.399s
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 8.220s]
sending 'userdata' (137318 KB)...
OKAY [ 4.516s]
writing 'userdata'...
OKAY [ 9.156s]
finished. total time: 21.892s
Everything seemed to go okay.
Does everything in the output above look okay?
Everything looks fine. Did you boot into recovery and perform a factory wipe after flashing userdata.img?
audit13 said:
Everything looks fine. Did you boot into recovery and perform a factory wipe after flashing userdata.img?
Click to expand...
Click to collapse
Yes I did do that and did the clear of the cache as well since it posted that error message like you said it would.
So I did both as you explained.
I took a picture of the phone itself after the userdata wipe.
https://www.dropbox.com/s/k05s06avrha1lfv/IMG_20160206_153435.jpg?dl=0
Hmm, I'm not sure what is wrong because you did exactly what I do every time I need to fix a bootloop.
audit13 said:
Hmm, I'm not sure what is wrong because you did exactly what I do every time I need to fix a bootloop.
Click to expand...
Click to collapse
Well that sucks!
I had read that in some cases this can be caused by a hardware issue. Any chance it could be that?
Btw, the links I provided to the stock Google images, were they the correct images?
These are the stock images: https://developers.google.com/android/nexus/images#hammerhead
Did you try flashing a stock 4.4.2 or 5.01 image too?
audit13 said:
These are the stock images: https://developers.google.com/android/nexus/images#hammerhead
Did you try flashing a stock 4.4.2 or 5.01 image too?
Click to expand...
Click to collapse
hi,
sorry for my late reply. I got sick and just didn't have it in me to try anything new.
I tried flashing 5.0.1 tonight and unfortunately wound up in another boot loop. I will have to try the steps again where you manually reflash userdata. Hopefully I will have time tomorrow!
Hi
My phone has the exact same problem as stated by OP. I even tried flashing kitkat and lollipop but the problem persist. The phone still stuck at boot animation screen. PLS help.
Boot into ffastboot, relock the bootloader, and then reboot into fastboot. Does the bootloader remain unlocked?
audit13 said:
Boot into ffastboot, relock the bootloader, and then reboot into fastboot. Does the bootloader remain unlocked?
Click to expand...
Click to collapse
The bootloader is now locked. Still, I can't boot the phone completely. stuck at Google boot animation.
At this point, I would conclude that something is wrong with the memory chip.
Hi all,
I recently rooted my Pixel and was plagued by the 15% battery issue. I found in the Pixel XL forum to fix it i should flash boot_a boot.img but that erased all my data.
I figured I'd start fresh and looked up a few websites who had instructions (androidcentral being one of them) and it seems like any other google phone, except i started getting FAILED to flash. so i ended up doing the following and now my device is encrypted.
fastboot flash bootloader bootloader-img
fastboot reboot bootloader
fastboot flash radio radio-img
fastboot reboot bootloader
fastboot flash boot_a boot.img
fastboot flash system_a system.img
fastboot flash userdata userdata.img
fastboot flash vendor_a vendor.img
fastboot format userdata (have to do this in order to get phone to read as 128GB)
---
so now when i boot up, it goes through the setup but it's encrypted.
I guess my question is, with the way Pixel's will be handling updates, what are all of the extra .img files from the factory image and should i be flashing them in a particular order?
here are the contents:
aboot.img
apdp.img
boot.img
bootlocker.img
cmnlib32.img
cmnlib64.img
devcfg.img
hosd.img
hyp.img
keymaster.img
modem.img
pmic.img
rpm.img
system_other.img
system.img
tz.img
userdata.img
vendor.img
xbl.img
Any assistance would be greatly appreciated!
Thanks!
EDIT #1: I just locked and then unlocked the bootloader to see if that allows me to setup as unencrypted. It's taking a while to boot so I doubt it.
EDIT #2: Still encrypted after set up.
Wellp... i wonder what flashing these after the initial order above will do...
EDOT#3:
lock / unlock botloader
fastboot flash system_a system.img
fastboot flash system_b system_other.img
... still encrypted, it booted up a bit quicker (or maybe i'm going nuts)
EDIT #4:
lock / unlock botloader
fastboot flash system_a system.img
fastboot flash system_b system_other.img
fastboot flash keymaster_a keymaster.img
andddd.... still encrypted... can anyone help out?
updating android sudio/sdk
So on the newest SDK, the fastboot flash system system.img will automatically detect and erase system_a.
probably a good idea to be on the latest sdk platform-tools
lockd / unlocked bootloader
bash update-all.sh
CRUD... still encrypted.
here's the output if anyone would like:
Code:
Marcs-MacBook-Pro:sailfish-nde63p root# bash flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32820 KB)...
OKAY [ 1.404s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
OKAY [ 1.040s]
finished. total time: 2.444s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
sending 'radio_a' (57048 KB)...
OKAY [ 2.457s]
writing 'radio_a'...
OKAY [ 0.869s]
finished. total time: 3.326s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: NOPE :)
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (25073 KB)...
OKAY [ 0.982s]
writing 'boot_a'...
OKAY [ 0.600s]
erasing 'system_a'...
OKAY [ 1.201s]
sending sparse 'system_a' 1/4 (518936 KB)...
OKAY [ 29.084s]
writing 'system_a' 1/4...
OKAY [ 5.336s]
sending sparse 'system_a' 2/4 (506887 KB)...
OKAY [ 28.523s]
writing 'system_a' 2/4...
OKAY [ 13.352s]
sending sparse 'system_a' 3/4 (491777 KB)...
OKAY [ 28.733s]
writing 'system_a' 3/4...
OKAY [ 6.808s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 1.732s]
writing 'system_a' 4/4...
OKAY [ 0.619s]
erasing 'system_b'...
OKAY [ 1.181s]
sending sparse 'system_b' 1/4 (517263 KB)...
OKAY [ 30.183s]
writing 'system_b' 1/4...
OKAY [ 4.555s]
sending sparse 'system_b' 2/4 (513954 KB)...
OKAY [ 25.261s]
writing 'system_b' 2/4...
OKAY [ 5.386s]
sending sparse 'system_b' 3/4 (523846 KB)...
OKAY [ 33.335s]
writing 'system_b' 3/4...
OKAY [ 4.485s]
sending sparse 'system_b' 4/4 (88422 KB)...
OKAY [ 7.907s]
writing 'system_b' 4/4...
OKAY [ 1.348s]
erasing 'vendor_a'...
OKAY [ 0.520s]
sending 'vendor_a' (234137 KB)...
OKAY [ 7.342s]
writing 'vendor_a'...
OKAY [ 6.647s]
Setting current slot to 'a'...
OKAY [ 0.400s]
erasing 'userdata'...
OKAY [ 28.688s]
sending 'userdata' (145102 KB)...
OKAY [ 4.998s]
writing 'userdata'...
OKAY [ 2.393s]
rebooting...
finished. total time: 282.030s
Marcs-MacBook-Pro:sailfish-nde63p root#
tried factory reset and flashing some of the other images... no luck, still encrypted. guess i'll need to wait for TWRP to come out and figure out how to decrypt :-/
spunks3 said:
tried factory reset and flashing some of the other images... no luck, still encrypted. guess i'll need to wait for TWRP to come out and figure out how to decrypt :-/
Click to expand...
Click to collapse
Thanks friend!:laugh:
Modifiy the kernel
omegear said:
Modifiy the kernel
Click to expand...
Click to collapse
How?
Hey spunks, I'm in the same boat with you. Cant decrypt. I don't even remember encrypting in the first place!
Oface82 said:
Hey spunks, I'm in the same boat with you. Cant decrypt. I don't even remember encrypting in the first place!
Click to expand...
Click to collapse
I think it'll just be a waiting game... This happened to me when I flashed the original boot image using an out of date SDK.
Can you point me in the direction of the factory images? I need to start over
Why are you so desperate to decrypt? It's encrypted by default, and stops you from nothing at this moment, and likely won't be a road block in the future either.
Sent from my Pixel using Tapatalk
I had a similar issue. I tried to unroot in order to install the new OTA, because it failed. So I tried to flash the factory boot image via
Code:
fastboot flash boot boot.img
fastboot flash boot_b boot.img
After the next boot I got the nice "erasing" screen...
My phone was unencrypted before (dunno why) and now all my data is gone and it is encrypted... Maybe there are some devices, which are not encrypted by default and factory resetting after updates...