i dont know what is this problem
i am trying to flash img files that i already tried before and worked
but now it always gaves me failed
what do think this problem fix is?
Start twrp and flash without fastboot. If you get the failed message i would wipe data
Gesendet von meinem HUAWEI NXT-L29 mit Tapatalk
EGOiST1991 said:
Start twrp and flash without fastboot. If you get the failed message i would wipe data
Gesendet von meinem HUAWEI NXT-L29 mit Tapatalk
Click to expand...
Click to collapse
same eror with twrp
but tried flasher from google play and worked fine
so why flasher did the job and fastboot.twrp did not?
Says twrp by internal storage 0mb left?
Gesendet von meinem HUAWEI NXT-L29 mit Tapatalk
EGOiST1991 said:
Says twrp by internal storage 0mb left?
Gesendet von meinem HUAWEI NXT-L29 mit Tapatalk
Click to expand...
Click to collapse
No it sayes faild
I already formated data
How can i flash system.img with twrp?i cant find option to flash system
Only recovery and boot
rowihel2012 said:
No it sayes faild
I already formated data
How can i flash system.img with twrp?i cant find option to flash system
Only recovery and boot
Click to expand...
Click to collapse
Did you try restore your backup with twrp? I had this problem before I couldn't fastball system but could restore from twrp
Sent from my HUAWEI NXT-L29 using Tapatalk
somboons said:
Did you try restore your backup with twrp? I had this problem before I couldn't fastball system but could restore from twrp
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
i cant flash any img with fastboot any more
J:\adb>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (29752 KB)...
OKAY [ 0.877s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.887s
:crying:
cant do any thing with fastboot any more
C:\adb>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
C:\adb>
Try to reformat data and system in twrp. Wipe - advanced wipe - data - repair - change format - from ext4 to exfat and back to ext4, the same with system. Then wipe Cache, dalvik, data, system, cust, internal storage and format data. Boot from twrp to bootloader and try fastboot again.
Gesendet von meinem HUAWEI NXT-L29 mit Tapatalk
dlorean said:
Try to reformat data and system in twrp. Wipe - advanced wipe - data - repair - change format - from ext4 to exfat and back to ext4, the same with system. Then wipe Cache, dalvik, data, system, cust, internal storage and format data. Boot from twrp to bootloader and try fastboot again.
Gesendet von meinem HUAWEI NXT-L29 mit Tapatalk
Click to expand...
Click to collapse
i dont have twrp
i have the stock
what should i do ?
i tried every img but alwaye failed
fastboot was working fine
what happend
rowihel2012 said:
i tried every img but alwaye failed
fastboot was working fine
what happend
Click to expand...
Click to collapse
Please Google to find command format system and data. I used to see.
Sent from my HUAWEI NXT-L29 using Tapatalk
somboons said:
Please Google to find command format system and data. I used to see.
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
I tried that to
Not working
Fastboot stoped working.
Same error
FAILED (remote: Command not allowed)
rowihel2012 said:
Same error
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
I have no idea. Does your phone unlock boot loader ?
rowihel2012 said:
I tried that to
Not working
Fastboot stoped working.
Click to expand...
Click to collapse
Sent from my HUAWEI NXT-L29 using Tapatalk
rowihel2012 said:
Same error
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Im 99% sure your bootloader is not unlocked.
m3dd0g said:
Im 99% sure your bootloader is not unlocked.
Click to expand...
Click to collapse
it is unlocked
and i had twrp
i tried to relock but failed
i tried to unlock again but sayes it is already unlocked
As i understand you was at twrp recovery and tried to lock the bootloader in fastboot. YOU MUST BE COMPLETELY STOCK when you lock the bootloader otherwise you brick your device. The same happend to some guys on Nexus devices.
m3dd0g said:
As i understand you was at twrp recovery and tried to lock the bootloader in fastboot. YOU MUST BE COMPLETELY STOCK when you lock the bootloader otherwise you brick your device. The same happend to some guys on Nexus devices.
Click to expand...
Click to collapse
no i tried to lock bootloader now with stock not twrp
but i cant relock too
i wanna try relock and unlock again but sayes
C:\adb>fastboot oem relock 1341946577872432
...
FAILED (remote: root type is risk)
finished. total time: -0.000s
rowihel2012 said:
no i tried to lock bootloader now with stock not twrp
but i cant relock too
i wanna try relock and unlock again but sayes
C:\adb>fastboot oem relock 1341946577872432
...
FAILED (remote: root type is risk)
finished. total time: -0.000s
Click to expand...
Click to collapse
But you are in the bootloader screen of your phone ?
Related
My Xt925 has "Encrytion Unsuccessful" when I boot up. I have tried to flash a recovery img but all I get is this message.
C:\Documents and Settings\Admin\Desktop\Fastbootxt925\Fastboot>fastboot flash re covery twrp-hdrecovery.img
sending 'recovery' (6678 KB)... OKAY [ 0.844s]
writing 'recovery'...
INFOFailed to erase partition INFOFailed to flash partition recovery
FAILED (remote failure) finished. total time: 1.000s
Click to expand...
Click to collapse
Motorola XT925
Android 4.2
AF Fastboot flasmode (s)
10.9B (Sha-5b608bc, 2012-12-20 16:55:20)
eMMC info: size 16gb
Device is unlocked, status code: 3
Its Bricked isn't it?
I have tried getting some help so I hope someone reads this..
"Partition signed?"
is0lde said:
My Xt925 has "Encrytion Unsuccessful" when I boot up. I have tried to flash a recovery img but all I get is this message.
Motorola XT925
Android 4.2
AF Fastboot flasmode (s)
10.9B (Sha-5b608bc, 2012-12-20 16:55:20)
eMMC info: size 16gb
Device is unlocked, status code: 3
Its Bricked isn't it?
I have tried getting some help so I hope someone reads this..
Click to expand...
Click to collapse
I have also tried reflashing rom using RSD Lite, and get a the Following error
Failed flashing process. 2/22 Flash parition "partition signed" -> Phone returned FAIL.
Click to expand...
Click to collapse
is0lde said:
I have also tried reflashing rom using RSD Lite, and get a the Following error
Click to expand...
Click to collapse
Delete the partition signed line from the Xml and try flashing again!!!!
Al the best!!!!
Sent from my C6802 using Tapatalk
Same problem
Hey man, having the same problem, excluded the line (actually many), and it installed 14. Now the reboot is in process and nothing happens.
kumeipark said:
Delete the partition signed line from the Xml and try flashing again!!!!
Al the best!!!!
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse
mari18cf said:
Hey man, having the same problem, excluded the line (actually many), and it installed 14. Now the reboot is in process and nothing happens.
Click to expand...
Click to collapse
flash the partition file with "Mfastboot", then re-flash the stock file with only the partition, tz, and getvar(you may not have this) removed.
guys i lost root after the ota update .. and after many hours of reading i understand that i need to update the recovery and su binary..
BUT i am not able to do that.. after flash TWRP 2.7.1.1 i still get a dead looking android(i assume this is stock recovery part)..
please suggest adb/fastboot command methods over toolkits.. i am comfortable with the commands..
The following suggestion is not just working for me..
http://forum.xda-developers.com/showpost.php?p=53600578&postcount=32
Please help..
MEkANiK said:
guys i lost root after the ota update .. and after many hours of reading i understand that i need to update the recovery and su binary..
BUT i am not able to do that.. after flash TWRP 2.7.1.1 i still get a dead looking android(i assume this is stock recovery part)..
please suggest adb/fastboot command methods over toolkits.. i am comfortable with the commands..
The following suggestion is not just working for me..
http://forum.xda-developers.com/showpost.php?p=53600578&postcount=32
Please help..
Click to expand...
Click to collapse
There's only one fastboot command to flash recovery.. What exactly are you doing to flash? What happens when you press volume up at the dead android. Please be as descriptive as possible.
Sent from my Nexus 5 using Tapatalk
rootSU said:
There's only one fastboot command to flash recovery.. What exactly are you doing to flash? What happens when you press volume up at the dead android. Please be as descriptive as possible.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
following is what i tried:-
Vinays-MacBook-Pro:Android vinayprabhakar$ fastboot flash recovery openrecovery-twrp-2.7.1.1-hammerhead.img
sending 'recovery' (13586 KB)...
OKAY [ 0.630s]
writing 'recovery'...
OKAY [ 1.071s]
finished. total time: 1.701s
Vinays-MacBook-Pro:Android vinayprabhakar$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
Vinays-MacBook-Pro:Android vinayprabhakar$ fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.001s
this is what i tried.. and yet it gives dead android when i try to boot into recovery mode..
What happens when you press volume up at the dead android ?
Sent from my Nexus 5 using Tapatalk
rootSU said:
What happens when you press volume up at the dead android ?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i was going to try this but looks everything is back to normal that is the twrp is now accesible .. i have not trying same commands again and again for past 4 hours it never did and after i tried the above steps it just worked..
sorry for the trouble.. but its back to normal.. thanks..
Hi!
I am trying to flash my Xperia L which is already rooted.
I got my "unlock bootloader key" and not when I try to unlock it with the key it says-
FAILED <Command did not succeed.>
Second time try the same statement again and it says OK!
After that when I try to flash a recovery it says-
F:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash recovery
philztaoshan.img
sending 'recovery' (12452 KB)...
OKAY [ 0.397s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.402s
It is able to write a kernel's boot image however, but then it doesn't not even boot. (Even the screen doesn't turn on)
I will be thankful to any help!
srishabhiitk said:
Hi!
I am trying to flash my Xperia L which is already rooted.
I got my "unlock bootloader key" and not when I try to unlock it with the key it says-
FAILED <Command did not succeed.>
Second time try the same statement again and it says OK!
After that when I try to flash a recovery it says-
F:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash recovery
philztaoshan.img
sending 'recovery' (12452 KB)...
OKAY [ 0.397s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.402s
It is able to write a kernel's boot image however, but then it doesn't not even boot. (Even the screen doesn't turn on)
I will be thankful to any help!
Click to expand...
Click to collapse
Is you're phone bootloader unlockable?
Yes!
Lazynestor said:
Is you're phone bootloader unlockable?
Click to expand...
Click to collapse
Yes, Unlockable and unlocked!
Actually I was using Cyanogenmod 12 by Varun Chitre and when I wanted to switch to Nightly version this error came and I couldn't find a s loution.
srishabhiitk said:
Yes, Unlockable and unlocked!
Actually I was using Cyanogenmod 12 by Varun Chitre and when I wanted to switch to Nightly version this error came and I couldn't find a s loution.
Click to expand...
Click to collapse
Did you try to flash it with Flashtool?
Also try right click on cmd and open as administrator
Fabulous_Pancake said:
Did you try to flash it with Flashtool?
Also try right click on cmd and open as administrator
Click to expand...
Click to collapse
Yes, I've tried flashtool and it gives same error. I didn't try running cmd as administrator but I doubt it would change anything..
hmm you have this problem with other kernels? also try fastboot flash boot philztaoshan.img
You can't use fastboot with recovery command.
Xperia doesn't have recovery partition
Fabulous_Pancake said:
hmm you have this problem with other kernels? also try fastboot flash boot philztaoshan.img
Click to expand...
Click to collapse
Yeah! I couldn't flash anything after that error started coming.
underd0g said:
You can't use fastboot with recovery command.
Xperia doesn't have recovery partition
Click to expand...
Click to collapse
I guess that may be the problem because everything was working fine. Until I had to flash a custom recovery like Philz through fastboot.
I didn't know the command so I searched for a general one. I used "fastboot flash recovery recovery.zip".
But there is one other thing that when I tried to install Thunderzap Kernel through Flashtool my phone even stopped showing SONY splash screen and just vibrated trying to boot!
Please tell me the correct procedure to flash custom recovery through fastboot in Xperia Phone.
As far as I know there are 2 recovery that can be flashed to FOTAKernel partition.
TWRP compiled by rohan.purohit and Phil ported by sdt.
The only method to flash FOTAKernel (recovery) is via adb shell or terminal emulator.
See TWRP thread at Original Dev section
just flash thunderzap 4.14 and cm12. extract boot.img from tz zip and go into fastboot mode on your device than simply flash extracted boot img with flashboot
Fabulous_Pancake said:
just flash thunderzap 4.14 and cm12. extract boot.img from tz zip and go into fastboot mode on your device than simply flash extracted boot img with flashboot
Click to expand...
Click to collapse
I tried to install thunderzap using Flashtool, the device stopped booting. I had to flash stock ftf!
underd0g said:
As far as I know there are 2 recovery that can be flashed to FOTAKernel partition.
TWRP compiled by rohan.purohit and Phil ported by sdt.
The only method to flash FOTAKernel (recovery) is via adb shell or terminal emulator.
See TWRP thread at Original Dev section
Click to expand...
Click to collapse
I will try that and get back to you!
srishabhiitk said:
Hi!
I am trying to flash my Xperia L which is already rooted.
I got my "unlock bootloader key" and not when I try to unlock it with the key it says-
FAILED
Second time try the same statement again and it says OK!
After that when I try to flash a recovery it says-
F:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash recovery
philztaoshan.img
sending 'recovery' (12452 KB)...
OKAY [ 0.397s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.402s
It is able to write a kernel's boot image however, but then it doesn't not even boot. (Even the screen doesn't turn on)
I will be thankful to any help!
Click to expand...
Click to collapse
your command is just wrong... even if you flash recovery you have to flash it as kernel in xperia devices
fastboot flash boot boot.img
is the correct command eg:
fastboot flash boot c:\recovery.img
Sent from my C2105 using XDA Free mobile app
---------- Post added at 12:55 PM ---------- Previous post was at 12:55 PM ----------
srishabhiitk said:
I will try that and get back to you!
Click to expand...
Click to collapse
you cant flash fota recovery ob stock...
Sent from my C2105 using XDA Free mobile app
SdtBarbarossa said:
your command is just wrong... even if you flash recovery you have to flash it as kernel in xperia devices
fastboot flash boot boot.img
is the correct command eg:
fastboot flash boot c:\recovery.img
Sent from my C2105 using XDA Free mobile app
---------- Post added at 12:55 PM ---------- Previous post was at 12:55 PM ----------
you cant flash fota recovery ob stock...
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
Should I simply try flashing Philz Recovery with command-
fastboot flash boot c:\recovery.img
srishabhiitk said:
Should I simply try flashing Philz Recovery with command-
fastboot flash boot c:\recovery.img
Click to expand...
Click to collapse
if recovery is in c then yes
maybe its / not \
Sent from my C2105 using XDA Free mobile app
SdtBarbarossa said:
if recovery is in c then yes
maybe its / not \
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
I guess it is, because it has already worked before using just normal commands.
srishabhiitk said:
I guess it is, because it has already worked before using just normal commands.
Click to expand...
Click to collapse
lol you mean you are not knowing where your file is? crazy xD
Sent from my C2105 using XDA Free mobile app
SdtBarbarossa said:
lol you mean you are not knowing where your file is? crazy xD
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
Oh! You meant recovery on my PC.. I thought the partition on my phone
srishabhiitk said:
Oh! You meant recovery on my PC.. I thought the partition on my phone
Click to expand...
Click to collapse
and did it work
Sent from my C2105 using XDA Free mobile app
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..
ttps://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
OPENBETA3 I installed this module magiskden to my oneplus 6 device installed in rom. I installed the system backup from twrp (bluspark v9.85) before installing.
When I set up the module and restart it, the screen was opened and closed, it was not possible to enter magisk manager.
Twrpye and I said 'restore system'. When the Restore process was completed, I said reboot system and went into fastboot mode.
I can't boot to the phone and write twrp. Fastboot is entering mode every time I restart.
I need to save my data. I don't want to flash fastboot rum.
I think there is no way without msmtool. I had the same problem when I tried to restore backup.
Kollachi said:
I think there is no way without msmtool. I had the same problem when I tried to restore backup.
Click to expand...
Click to collapse
fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.609s
have you received such an error?
This isn't related to the module and seems to happen whenever I try to restore /boot or /system using TWRP. This is easily fixable by flashing the original boot.img
Is there any other solution than flashing the factory rum? At least if I twrp, I would back up internal storage.
DevrimSeven60 said:
fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.609s
have you received such an error?
Click to expand...
Click to collapse
Yes I had the same error
Kollachi said:
Yes I had the same error
Click to expand...
Click to collapse
what is the solution? Bluspark twrp flash I do not get error, but twrpye can not enter, although it is completed.
DevrimSeven60 said:
Is there any other solution than flashing the factory rum? At least if I twrp, I would back up internal storage.
Click to expand...
Click to collapse
You can try flash the boot.img like paphonb said. I didn't knew that and used msmtool. But I saved my data before restoring in twrp so I didn't lose anything just a lil bit time
paphonb said:
This isn't related to the module and seems to happen whenever I try to restore /boot or /system using TWRP. This is easily fixable by flashing the original boot.img
Click to expand...
Click to collapse
open beta 3 i have downloaded full rom zip. Is there an img I can use in zip?