Related
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?
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,
rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?
therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?
heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,
Bump!
Does anyone have any other suggestion please?
Thanks,
Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!
Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.
I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?
I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..
Hey guys. Today I tried to update my Moto G XT1039 EU version from CM12.1 to CM13. Firstly I tried to update my recovery... after some time i made it with problems. To open recovery i had to use command "fastboot boot recovery.img" and then it opened (I occured Boot up failed problem). Once I made it i went straing to erase any necessary data and I tried to install newest ROM which is CM13 and new gapps file. CM13 installed properly but gapps didnt. But i tried to turn on phone and see if it works anyway. Well... since then now i cant turn on phone becasue the only thing works is fastboot flash mode. I cant install any recovery file becasue i have Boot up fail problem, yet i cant open it via command prompt because Failed (Remote Failure). When i type "fastboot devices" my PC sees it. My bootloader version is 41.1A.
Is there any chance i can have that CM13 installed properly or at least to have it working at all?
Hello guys I need some help. I'm stuck in fastboot mode with no recovery or OS too l, let me retrace my steps.
I had my px3 rooted on stock but I was bored with stock and tried to flash bootleggers rom and followed instructions to wipe "everything" but internal storage, so I did including storage under internal storage and flashed the ROM and twrp with it. After it just rebooted back to recovery every time I tried normal boot. (I'm assuming I F'd up by wiping storage). So I googled what to do about looping recovery and one suggestion was to factory reset so I did; I can no longer access recovery. I've tried flashing factory image, flashing the twrp zip, trying to boot straight to twrp, I can't get to adb sideload and it says "no valid slot to boot" on fastboot screen any suggestions?
Got another on fastboot, "error booting boot.img"
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
wergrun said:
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
Click to expand...
Click to collapse
You need to get back to fastboot, and run the flash all bat file from the full factory image.
TonikJDK said:
You need to get back to fastboot, and run the flash all bat file from the full factory image.
Click to expand...
Click to collapse
I tried that but I keeps giving me an error, I'll post it when I get the chance
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
I have the same issue, except my computer will not recognize the device in fastboot. I tried two different computers, Windows 10 and laptop running Linux.
wergrun said:
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
Click to expand...
Click to collapse
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
SS823 said:
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
Click to expand...
Click to collapse
I did get that too but it was because I forgot to put a space after "bootloader_a ", are you Stuck at around the 9 minute steps?
Yes, right around the end at 9 minutes. Everything works fine - bootloader, radio, etc. When I get to the end of the img zip file I get this message:
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s
I am at a loss.
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