Database Info

[Q] Two major problems combined completely block my phone

Hi,
so yeah... I got two fatal problems that completely block me from doing anything on my phone.
It started when suddenly my phone's screen turned black, and after a restart it keeps taking me to a screen when it asks for a password to decrypt my data, blocking me from reaching my phone.
So I wanted to recover the phone to fix it, but when i enter fastboot and choose recovery, after a few seconds it shows a picture of the android logo with an exclamation mark on it, and I cannot get into the recovery screen.
Each problem prevents me from fixing the other one, any ideas of how can I save my phone?

Download a custom recovery for crespo. Get your phone into fastmode mode and flash the recovery image.
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Then select recovery in fastboot menu.
Encrypt problem is reported in this thread earlier. You may have to do a full wipe and flash a new ROM.

I downloaded the google factory image, but when i run fastboot -w update image-soju-jzo54k.zip (tried two different ones), it fails when trying to write to the system partition (FAILED remote: Write fail).
the other partitions work, but something prevents me from updating the system partition no matter what zip i use, tried many.
any ideas?

Please provide complete log messages shown on PC and phone.
Which phone did you have? soju is for i9020t, and sojua for i9020a.
Try to format data/cache/system via clockworkmod recovery first.

_android_ said:
Please provide complete log messages shown on PC and phone.
Which phone did you have? soju is for i9020t, and sojua for i9020a.
Try to format data/cache/system via clockworkmod recovery first.
Click to expand...
Click to collapse
I wasn't able to find the exact model of my phone, but since soju failed flashing and sojua succeeded, i assume it's i9020a.
Anyway, I tried to format data/cache/system via cwm recovery, and after system succeeded, the phone starts "restoring data...", and after a few minutes it stops with the message "Can't mount /data!"
perhaps the reason i he can't mount/restore /data is the reason I'm getting the encryption problem in first place, is there any way around it?

loliori said:
I wasn't able to find the exact model of my phone, but since soju failed flashing and sojua succeeded, i assume it's i9020a.
Anyway, I tried to format data/cache/system via cwm recovery, and after system succeeded, the phone starts "restoring data...", and after a few minutes it stops with the message "Can't mount /data!"
perhaps the reason i he can't mount/restore /data is the reason I'm getting the encryption problem in first place, is there any way around it?
Click to expand...
Click to collapse
Model is printed on IMEI sticker at back of phone under battery.
Format data/cache/system before flashing sojua image. Skip format system if giving problem.
Code:
fastboot -w update image-sojua-jzo54k.zip
Or try running the batch file as is, and it will update bootloader and radio to latest version as well.
flash-all.bat or flash-all.sh (linux)

_android_ said:
Model is printed on IMEI sticker at back of phone under battery.
Format data/cache/system before flashing sojua image. Skip format system if giving problem.
Code:
fastboot -w update image-sojua-jzo54k.zip
Or try running the batch file as is, and it will update bootloader and radio to latest version as well.
flash-all.bat or flash-all.sh (linux)
Click to expand...
Click to collapse
ok so soju is the right one for me.
I followed your instructions and now, and it fails writing the system image, the cmd window pretty much looks like that:
checking product...
OKAY
...
... (more ok checks)
sending 'boot'
OKAY
more OK sendings
sending 'system'
OKAY
writing 'system'
FAILED (remote: Write Fail)
I also tried using the batch file and although the window closes before i can see if any error happened, i get the same "FAILWrite Fail" error in my fastboot screen status, so I assume the same problem occurs.

What about formatting system partition via cwm? Failed too?

no, formatting system partition works. every partition format works, but i still can't update through fastboot.
It might be worth mentioning that I cannot even erase partitions on fastboot (fastboot -w fails, fastboot erase userdata, fastboot erase system etc fails, giving me a FAILED remote: erase fail error)

loliori said:
no, formatting system partition works. every partition format works, but i still can't update through fastboot.
It might be worth mentioning that I cannot even erase partitions on fastboot (fastboot -w fails, fastboot erase userdata, fastboot erase system etc fails, giving me a FAILED remote: erase fail error)
Click to expand...
Click to collapse
How about flashing a new ROM say CM10.0 + gapps-jb-20121011 via CWM?

_android_ said:
How about flashing a new ROM say CM10.0 + gapps-jb-20121011 via CWM?
Click to expand...
Click to collapse
flashing gapps seems to finish but when i flash CM i'm not sure wether it was installed correctly. it just says
finding update package...
opening update package...
installing update...
and then goes back to the cwm recovery menu, as if it finished.
anyway, i tried rebooting after flashing both and my device gets stuck right after starting, i get the google logo and then the screen just turns black and seems to process forever, and nothing happens afterwards, it's just a black screen.

loliori said:
flashing gapps seems to finish but when i flash CM i'm not sure wether it was installed correctly. it just says
finding update package...
opening update package...
installing update...
and then goes back to the cwm recovery menu, as if it finished.
anyway, i tried rebooting after flashing both and my device gets stuck right after starting, i get the google logo and then the screen just turns black and seems to process forever, and nothing happens afterwards, it's just a black screen.
Click to expand...
Click to collapse
You should Install CM then gapps.

_android_ said:
You should Install CM then gapps.
Click to expand...
Click to collapse
yeah I flashed CM and then gapps.
Interestingly tho, none of the google factory images manages to flash through CWM. they just say update failed without any informative error, while CM and gapps seem to succeed flashing

loliori said:
yeah I flashed CM and then gapps.
Interestingly tho, none of the google factory images manages to flash through CWM. they just say update failed without any informative error, while CM and gapps seem to succeed flashing
Click to expand...
Click to collapse
Google factory images are only flashable via fastboot. But there may be CWMed (cooked) versions available in XDA.

It seems like no matter what rom i flash, it either gets stuck while the phone is loading, or the phone loads and i get this "type password to decrypt" window.
Is there a way to like hard-format my phone, or a way to fix my fastboot flashing problems?

Updating to 6.0....and bricked

Stock, unrooted xt1540. Got the update notification this morning, so excited. After updating, it's boot looping and the M logo is the furthest it can go.
Tried to fastboot flash back to old 5.1.1 factory image, "image validation failed". Maybe because boot loader got updated and won't roll back?
All I can think of now is to wait for the 6.0 factory image and try that again, but I may end up waiting for it too long.
Any suggestions? Thanks!

What about the images at http://forum.xda-developers.com/2015-moto-g/general/ota-moto-g3-marshmallow-ota-links-t3284308

Try in fastboot clear the cache and data ...

have you tried using twrp to just install a cm rom or something similar?
worst case scenario you can use twrp to force the soak test images onto their respective partitions. if your bootloader was updated the soak test will run...even if it bootloops for any reason, then at least you've taken one step forward again.

MrTooPhone said:
What about the images at http://forum.xda-developers.com/2015-moto-g/general/ota-moto-g3-marshmallow-ota-links-t3284308
Click to expand...
Click to collapse
I wish I could resume the OTA, even manually, but right now I can only go to bootloader, not even the stock recovery....Thanks for the idea, though! Really appreciate it.

hp420 said:
have you tried using twrp to just install a cm rom or something similar?
worst case scenario you can use twrp to force the soak test images onto their respective partitions. if your bootloader was updated the soak test will run...even if it bootloops for any reason, then at least you've taken one step forward again.
Click to expand...
Click to collapse
I just tried flash in the twrp.img, got declined by bootloader again...
Now is there factory images for the soak test? Thanks!!

lexer98 said:
Try in fastboot clear the cache and data ...
Click to expand...
Click to collapse
clearing cache went through, but clearing data failed. Rebooting to bootloader mode and try returning to stock again, still no go...

In fastboot mode, I can flast logo, fsg, NON-HLOS, bootloader, recovery -- all from 5.1.1 factory image, but when I tried to flash boot or system chunks, it says:
D:\Desktop\g\Mfastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 10.573s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.042s
Is my only option to wait for the MM factory image....

alvin612 said:
I just tried flash in the twrp.img, got declined by bootloader again...
Now is there factory images for the soak test? Thanks!!
Click to expand...
Click to collapse
Well....yes and no.
http://forum.xda-developers.com/201...-devs-moto-g3-xt1540-soak-test-files-t3255643
The images all flash in fastboot except the system one, which requires using adb shell while booted to twrp. You have to use a dd command to force the system.img into the correct partition.

Earlier today I had to give up on this osprey because of limited bandwith for fix.
Thanks again for everyone's help!!

My phone got bricked after trying to downgrade from MM to LP
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked.
Is there a way to bring my phone back to life? What can I do?

JulesSDK said:
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked.
Is there a way to bring my phone back to life? What can I do?
Click to expand...
Click to collapse
I contacted Motorola. Warranty covers my situation. Going to ask for a replacement.

JulesSDK said:
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked.
Is there a way to bring my phone back to life? What can I do?
Click to expand...
Click to collapse
Unlock the bootloader and then try flashing. I was in a similar situation once, was getting failed messages when trying to flash official signed factory images. Unlocked the bootloader and then tried to flash and voila, everything flashed smoothly. No harm in trying unless you are worried about warranty.

Honor View10 is stuck at 'Your device is booting now', cannot enter recovery.

My Honor View10 is stuck at 'Your device is booting now', cannot enter recovery. I tried rectifying my twrp that couldn't unmount anything and wiped up almost everything, but ended up with a boot loop.
Now my device is stuck at 'Your device has been unlocked and can't be trusted. Your device is booting now' screen. I tried using the dload method to restore everything back but the device won't go past this screen.
I tried flashing it using fastboot mode by flashing system, ramdisk and what not, did get a success every time, still, the device won't go past this.
I need genuine help on this, please. Anyone? @2WildFirE? @Einwod? @shashank1320 @oreopie
All this perhaps happened because I tried changing the file system of data and system from twrp.

ankan1993 said:
My Honor View10 is stuck at 'Your device is booting now', cannot enter recovery. I tried rectifying my twrp that couldn't unmount anything and wiped up almost everything, but ended up with a boot loop.
Now my device is stuck at 'Your device has been unlocked and can't be trusted. Your device is booting now' screen. I tried using the dload method to restore everything back but the device won't go past this screen.
I tried flashing it using fastboot mode by flashing system, ramdisk and what not, did get a success every time, still, the device won't go past this.
I need genuine help on this, please. Anyone? @2WildFirE? @Einwod? @[email protected]
All this perhaps happened because I tried changing the file system of data and system from twrp.
Click to expand...
Click to collapse
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there

2WildFirE said:
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
Because custom recovery wouldn't mount anything.
Had no idea that twrp isn't ready for pie.
For both stock and ereccovery, do I use ramdisk_recovery command?

2WildFirE said:
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
How exactly would one go about this?
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img for example only results in FAILED (remote: 'Command not allowed').
Bootloader is unlocked.

If I'm right, try fastboot flash erecovery erecovery.img

2WildFirE said:
If I'm right, try fastboot flash erecovery erecovery.img
Click to expand...
Click to collapse
Sadly there is no erecovery.img and if i try to flash either of the many erecovery files into what i assume would be their respective partitions i get the same error.
Which i thought was a good sign because that might have meant that i couldn't have ****ed them up. But maybe it isn't.

OK try erecovery ramdisk and erecovery kernel to flash

PHP:
fastboot flash erecovery_kernel ERECOVERY_kerne.img
Sending 'erecovery_kernel' (24576 KB) OKAY [ 0.587s]
Writing 'erecovery_kernel' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.614s
for example, the result is always the same.

2WildFirE said:
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
UPDATE: When I reboot the smartphone it displays "Data partition was damaged seriously! and you are recommended to format it to recover your phone".
Smartphone works, but even after a factory reset it still displays that message when it boots up it gets stuck at 'Booting up'.
What can I do @2WildFirE?

180190 said:
PHP:
fastboot flash erecovery_kernel ERECOVERY_kerne.img
Sending 'erecovery_kernel' (24576 KB) OKAY [ 0.587s]
Writing 'erecovery_kernel' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.614s
for example, the result is always the same.
Click to expand...
Click to collapse
Because this is not the right command to give. I am not sure what the right command would be though.

Okay, so I have recovered my phone after spending a sleepless night working on it.
Tried several combinations to see this resolved.
But, what really worked out for me was that I discharged my device twice and kept trying flashing stock rom and several relative recoveries.
After flashing stock recovery I discharged my device. Once it came back, it took me to erecovery.
From there, I started downloading the file from the recovery and did a reboot after the installation.
My Honor is working fine now.

ankan1993 said:
But, what really worked out for me was that I discharged my device twice and kept trying flashing stock rom and several relative recoveries.
After flashing stock recovery I discharged my device.
Click to expand...
Click to collapse
What exactly have you done?

Sinerty said:
What exactly have you done?
Click to expand...
Click to collapse
Flashed the 9.0 full ota files several times, flashed full otas of 8.0. Flashed a random recovery from an older ota. I then discharged my device as I was totally out of options. When I put it on charge it turned back on and after few minutes took me to erecovery.
And now I cannot root my device as twrp isn't there for pie yet. Honor sucks.

Thread closed since it's a duplicate.
Please read here: https://forum.xda-developers.com/honor-view-10/help/honor-view10-stuck-device-booting-enter-t3889376

How to change the red boot warning back to the normal unlocked bootloader start warn.

To be clear im trying to bring back the old "boot loader is unlocked and software integrity cannot be guaranteed" boot message from the red one that says "Your device is corrupt. It can’t be trusted and may not work properly." Now I no this topic has already been on the forums but I read them, and made several attempts to fix the issue but was unsuccessful. every time I end up losing my all my **** and as soon as i upgrade to the latest pie ota it goes right back to the red boot message. One time I even hard bricked my phone and had to use the msmdownloadtool to get me back to hydrogen os and still the same thing happend when I upgraded to pie. Can anyone point me in the right direction on how to fix this problem.
p.s. I know its not a "problem" really but its one of those things that’s been pestering me for over a month. thanks for your concern.

Did you use in-built updater or flashed pie via twrp?
If you flashed by twrp, you may need to flash twice for both a and b bootslots.
You may try to lock bootloader, use msm again then update pie.
After that try to unlock it may fix

Linux_fart_18.3 said:
To be clear im trying to bring back the old "boot loader is unlocked and software integrity cannot be guaranteed" boot message from the red one that says "Your device is corrupt. It can’t be trusted and may not work properly." Now I no this topic has already been on the forums but I read them, and made several attempts to fix the issue but was unsuccessful. every time I end up losing my all my **** and as soon as i upgrade to the latest pie ota it goes right back to the red boot message. One time I even hard bricked my phone and had to use the msmdownloadtool to get me back to hydrogen os and still the same thing happend when I upgraded to pie. Can anyone point me in the right direction on how to fix this problem.
p.s. I know its not a "problem" really but its one of those things that’s been pestering me for over a month. thanks for your concern.
Click to expand...
Click to collapse
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter

abasba said:
Did you use in-built updater or flashed pie via twrp?
If you flashed by twrp, you may need to flash twice for both a and b bootslots.
You may try to lock bootloader, use msm again then update pie.
After that try to unlock it may fix
Click to expand...
Click to collapse
unfortunate for me ive tried all the above except locking bootloader before msm which i have also tried both separtatly but not in that order.

ab123pro said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
ill give it a try thanks also do you know the command to switch partitions when in fastboot? im stuck on a partion and stuck only rebooting to fastboot cant flash twrp img or boot img id really appreciate it any know the command

Linux_fart_18.3 said:
ill give it a try thanks also do you know the command to switch partitions when in fastboot? im stuck on a partion and stuck only rebooting to fastboot cant flash twrp img or boot img id really appreciate it any know the command
Click to expand...
Click to collapse
Run "fastboot boot twrp-3.3.1-3-enchilada.img" in command line https://androidfilehost.com/?fid=6006931924117908950
then from within twrp flash twrp installer - https://androidfilehost.com/?fid=6006931924117908949
and magisk if you want root

ab123pro said:
Run "fastboot boot twrp-3.3.1-3-enchilada.img" in command line https://androidfilehost.com/?fid=6006931924117908950
then from within twrp flash twrp installer - https://androidfilehost.com/?fid=6006931924117908949
and magisk if you want root
Click to expand...
Click to collapse
sudo fastboot boot ./twrp-3.2.3-x_blu_spark_v9.91_op6.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.924s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.939s
every time. thats why im in need of a command to get me back to the (b) partition and also
fastboot –set-active=_b just get me "waiting for device" and nothing more.

Linux_fart_18.3 said:
sudo fastboot boot ./twrp-3.2.3-x_blu_spark_v9.91_op6.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.924s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.939s
every time. thats why im in need of a command to get me back to the (b) partition and also
fastboot –set-active=_b just get me "waiting for device" and nothing more.
Click to expand...
Click to collapse
looks like your boot partition got corrupted some how im not sure tho
maybe try to flash one of those fastboot roms - https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

[SOLVED] Android Recovery Factory Reset not effective (rooted, bootloader unlocked)

Hi,
I backed up my kernel using TWRP by fastbooting into the Pixel 3 blueline TWRP image. When I then tried to reboot the phone I get following error:
"Android Recovery
google/blueline/blueline
9/PI/gucheng0719045
userdebug/dev-keys
...
Can't load Android system."
I tried both options "try again" and "factory data reset" but both brought me back to this screen. I also tried booting into recovery mode and doing "Wipe data factory reset"; this also brought me back to the above error.
Finally, I tried installing OTA using sideload but the signature verification failed since I have an unlocked bootloader and had custom ROM running on the device.
How can I get the device into a usable state again? I don't care about keeping the data. Also note that I still have the TWRP kernel backup saved.

gardeimasei said:
Hi,
I backed up my kernel using TWRP by fastbooting into the Pixel 3 blueline TWRP image. When I then tried to reboot the phone I get following error:
"Android Recovery
google/blueline/blueline
9/PI/gucheng0719045
userdebug/dev-keys
...
Can't load Android system."
I tried both options "try again" and "factory data reset" but both brought me back to this screen. I also tried booting into recovery mode and doing "Wipe data factory reset"; this also brought me back to the above error.
Finally, I tried installing OTA using sideload but the signature verification failed since I have an unlocked bootloader and had custom ROM running on the device.
How can I get the device into a usable state again? I don't care about keeping the data. Also note that I still have the TWRP kernel backup saved.
Click to expand...
Click to collapse
Flash factory image with fastboot.

wangdaning said:
Flash factory image with fastboot.
Click to expand...
Click to collapse
Where can I get the factory image? And how do I use fastboot to flash the device? Like so?:
Code:
fastboot boot <image name>.img
I am able to fastboot boot into the blueline TWRP image. Selecting the "Fix bootloop" didn't work however

So I tried doing:
Code:
fastboot flash boot bootloader-blueline-b1c1-0.1-5578427.img
I got following error though:
Sending 'boot_a' (8493 KB) OKAY [ 0.130s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
FAILED (remote: '(boot_a) No such partition')
fastboot: error: Command failed
Any suggestions on how to proceed?

gardeimasei said:
So I tried doing:
Code:
fastboot flash boot bootloader-blueline-b1c1-0.1-5578427.img
I got following error though:
Sending 'boot_a' (8493 KB) OKAY [ 0.130s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
FAILED (remote: '(boot_a) No such partition')
fastboot: error: Command failed
Any suggestions on how to proceed?
Click to expand...
Click to collapse
That command flashes only the boot loader, not the factory image. The factory image and instructions for flashing are at https://developers.google.com/android/images
What android version were you on when you started? TWRP does not run on a Pixel 3 with Android 10.

Also, the boot partition is not the bootloader partition. Just run the flash-all script that google provides with the factory image download.

dcarvil said:
That command flashes only the boot loader, not the factory image. The factory image and instructions for flashing are at https://developers.google.com/android/images
What android version were you on when you started? TWRP does not run on a Pixel 3 with Android 10.
Click to expand...
Click to collapse
I was using Android 9. I tried running the flash-all script (i.e., follow the official instructions) but the fastboot commands would hang. Maybe I just didn't wait for long enough.
I wiped system,data,cache using TWRP following some online guide and now I can't boot into recovery mode. I can get into the bootloader menu though. When I try to boot into TWRP using:
Code:
fastboot boot twrp-3.3.0-0-blueline.img
I get the following error on the PC: Booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
When I try to enter recovery mode the screen turns black indefinitely.
I still have the TWRP .win files from my backup on my PC. Is there a way out of this?
EDIT:
Weirdly, after trying the flash-all.sh script again it worked basically instantly. Possibly it took so long the first time i ran it because it was wiping data (which i then did manually).
Was able to get the factory image on there. Thanks a lot!