Related
All,
Long time lurker, first time poster. I've been doing a bunch of reading for the past few hours, I think my phone isn't completely f***, I'm just missing something simple.
So basically, I started with a stock HTC One XL with Telstra. Updated to the latest firmware version (3.17) and bootloader 2.14.
1. I unlocked the bootloader using htcdev. Installed CM10.1 smoothly, booted into the ROM and realised the touch screen didnt work (now I realise that's the new firmware problem).
2. Booted back into recovery (TWRP 2.4.1) and accidently wiped my SD card along with everything else (including backups).
3. Mounted SD card, and formatted it with FAT32. Put Viper 3.2.7 on it and installed it via recovery ---> Stuck in a boot loop. Phone boots to the Viper screen, does a bit of loading, and then re-boots. (I have also tried this with various other sense based ROMs, with the same problem).
4. After a bit of reading, I tried to manually load the boot.img file via fastboot. I get the following error message: FAILED: <remote: signature verify fail>.
So now I turn to you for help! After 3 years with Android, I have never had trouble flashing new ROMs following the instructions on this awesome site. I hope you guys can help me out on this one. All my phone content is backed up on my PC, so my only concern is getting a working ROM again.
So in summary, what I am able to do is:
- Boot to bootloader (which is unlocked)
- I DO NOT have s-off
- I can boot to TWRP recovery and mount my SD to copy any file across
I have not tried running RUU yet, leaving that as a last resort.
brad.cap said:
All,
Long time lurker, first time poster. I've been doing a bunch of reading for the past few hours, I think my phone isn't completely f***, I'm just missing something simple.
So basically, I started with a stock HTC One XL with Telstra. Updated to the latest firmware version (3.17) and bootloader 2.14.
1. I unlocked the bootloader using htcdev. Installed CM10.1 smoothly, booted into the ROM and realised the touch screen didnt work (now I realise that's the new firmware problem).
2. Booted back into recovery (TWRP 2.4.1) and accidently wiped my SD card along with everything else (including backups).
3. Mounted SD card, and formatted it with FAT32. Put Viper 3.2.7 on it and installed it via recovery ---> Stuck in a boot loop. Phone boots to the Viper screen, does a bit of loading, and then re-boots. (I have also tried this with various other sense based ROMs, with the same problem).
4. After a bit of reading, I tried to manually load the boot.img file via fastboot. I get the following error message: FAILED: <remote: signature verify fail>.
So now I turn to you for help! After 3 years with Android, I have never had trouble flashing new ROMs following the instructions on this awesome site. I hope you guys can help me out on this one. All my phone content is backed up on my PC, so my only concern is getting a working ROM again.
So in summary, what I am able to do is:
- Boot to bootloader (which is unlocked)
- I DO NOT have s-off
- I can boot to TWRP recovery and mount my SD to copy any file across
I have not tried running RUU yet, leaving that as a last resort.
Click to expand...
Click to collapse
FAILED: <remote: signature verify fail> means your bootloader is locked.
exad said:
FAILED: <remote: signature verify fail> means your bootloader is locked.
Click to expand...
Click to collapse
But it says **** UNLOCKED **** (as well as **** TAMPERED ****) at the top of the bootloader?
brad.cap said:
But it says **** UNLOCKED **** (as well as **** TAMPERED ****) at the top of the bootloader?
Click to expand...
Click to collapse
what is the command you used to load the boot.img and where did the boot.img come from?
on an unrelated note. flash twrp 2.3.3.1 instead every version above has issues wiping leading to issues not unlike yours.
after flashing 2.3.3.1 dont forget to do fastboot erase cache.
exad said:
FAILED: <remote: signature verify fail> means your bootloader is locked.
Click to expand...
Click to collapse
exad said:
what is the command you used to load the boot.img and where did the boot.img come from?
on an unrelated note. flash twrp 2.3.3.1 instead every version above has issues wiping leading to issues not unlike yours.
after flashing 2.3.3.1 dont forget to do fastboot erase cache.
Click to expand...
Click to collapse
I use "fastboot flash flash boot.img", the boot.img is extracted from the zip of the Viper ROM that is installed on my phone.
Will do! Will this help with the situation at hand? I'd rather keep as many factors static as possible. I'll flash twrp 2.3.3.1 once everything is resolved (unless it can help now?)
brad.cap said:
I use "fastboot flash flash boot.img", the boot.img is extracted from the zip of the Viper ROM that is installed on my phone.
Will do! Will this help with the situation at hand? I'd rather keep as many factors static as possible. I'll flash twrp 2.3.3.1 once everything is resolved (unless it can help now?)
Click to expand...
Click to collapse
Flash it now then try flashing again after wiping everything on 2.3.3.1
Sent from my HTC One X using xda app-developers app
brad.cap said:
I use "fastboot flash flash boot.img", the boot.img is extracted from the zip of the Viper ROM that is installed on my phone.
Will do! Will this help with the situation at hand? I'd rather keep as many factors static as possible. I'll flash twrp 2.3.3.1 once everything is resolved (unless it can help now?)
Click to expand...
Click to collapse
the command is fastboot flash boot boot.img btw.
but yes flash 2.3.3.1 first then fastboot erase cache then the boot img.
if you experience bugs that are not discussed in the ROMs op do a fresh wipe everything and reflash the rom because wiping with 2.4 probably wasn[t a clean wipe.
exad said:
the command is fastboot flash boot boot.img btw.
but yes flash 2.3.3.1 first then fastboot erase cache then the boot img.
if you experience bugs that are not discussed in the ROMs op do a fresh wipe everything and reflash the rom because wiping with 2.4 probably wasn[t a clean wipe.
Click to expand...
Click to collapse
Thanks. Will try that now.
Edit: Yep. That worked. Viper booted up fine and everything is working!
I'm going to make a back-up of this working ROM now, and have another go at getting CM10.1 to work.
Thanks for your help guys, really appreciate it. Especially exad.
So I got a pixel recently. I unlocked the bootloader, installed TWRP, and rooted it. However, it's been a few years since I had an unlocked and rooted phone so I forgot that the OTA updates can't be applied. So I decided to go back to the factory image. A quick google search lead me to an article where they said I could select the Full Unroot option in the settings of SuperSU and it would attempt to restore the stock boot image and recovery image. So I did that, and ended up in a boot loop.
Well, then I decided to try flashing the entire factory images from google, using the flash-all.bat file they provide. It seems to flash the bootloader and the radio fine, but when it comes to the part where it flashes everything in the "image-sailfish-nde63l.zip" (I picked this build because it was the one I was on when the pixel arrived) folder it says "Error: failed to load 'image-sailfish-nde63l.zip': not enough space."
I can still get to the TWRP recovery, and I can get to the bootloader, but currently nothing else seems to work. Please, can anyone help me?
UPDATE: The issue was outdated adb and fastboot. I had 1.0.32, once I had the latest versions (1.0.36 right now) I could fix everything.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.
Did you try flashing the stock boot.img to both slots before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure your download is not corrupt or something. https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F
Evo_Shift said:
Did you try flashing the stock boot.img to both partitions before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure you download is not corrupt or something.
Click to expand...
Click to collapse
No, I didn't do any flashing myself before going back to stock. I selected the "Full unroot" option in SuperSU, based on the first result when googling "unroot pixel".
As soon as I did that I was stuck in a bootloop and I tried to restore the factory images according to the google webpage, but that's when I get the error.
Doing what you said doesn't work either, not even redownloading the image.
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.
th3p3r50n said:
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
Click to expand...
Click to collapse
This happened to me too. That's my current situation. Have adb and fastboot still but can't figure out what steps to fix it.
I think you should focus on why the flash all didn't work. Do you have the latest fastboot? Did you check the md5 of the downloaded rom image? What OS it's your computer running?
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
fracman said:
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
Click to expand...
Click to collapse
The commands <adb version> and <fastboot --version> seem to return version numbers. My setup returns:
Android Debug Bridge version 1.0.36
Revision fd9e4d07b0f5-android
and
fastboot version fd9e4d07b0f5-android
respectively
Thank you cntryby429. I assumed I was using the latest versions because I had just installed them through the SDK Manager, turns out I was using version 1.0.32. I found the latest version of Minimal ADB and Fastboot and the flash-all script worked fine. I still had a few issues though, so I did a factory reset and then ran the flash-all script again. Now everything works perfectly again. Thanks so much!
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:
Do you have the Verizon model?
samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03
spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.
The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?
I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?
What if fastboot boot twrpname.img
It's really weird anyway...
enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...
if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.
I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!
Hi everyone, I have the mha-l29 and successfully updated to the latest Oreo for the US version. I then unlocked the bootloader, flashed TWRP, flash Superuser and everything was working fine. I then got an error message while doing a backup in TWRP and foolishly edited a file which caused the system to not boot. I then Flashed the hwoa7 instead of 8 to fix it and now my phone is bricked. The only thing I can do is get into fastboot. Everything else throws an error. Is ee a func no: 11 error. Please see attached pictures. Please let me know how I can fix it. I've already tried reflashing the ramdisk as well as TWRP bet I can't boot into TWRP.
Thanks so much
C:\>fastboot oem lock-state info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.008s]
finished. total time: 0.012s
Do you mean you flashed RECOVERY_nocheck from Nougat to Recovery of Oreo?
If so you should only need to flash recovery_ramdisk.
I guess you could extract ramdisk, recovery_ramdisk and kernel and flash to the partitions of the same name.
See what error it gives after you flash back stock recovery_ramdisk
Thank you for your help ante. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
saw this to late , TWRP caused this i had the same thing earlier and reinstalled different TWRP
seti007 said:
Thank you for your help ante. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
Click to expand...
Click to collapse
DC-Unlockr allowed you to use adb to flash twrp? How were you able to do that exactly?
I was able to flash the entire update package using DC Unlocker. That should have gotten me up fully but it did not. Before using DC unlocker, I was not able to even boot into TW RP or erecovery. I was able to get into fastboot but could not install anything. I did not get any errors in ADB and installations were successful but I could not boot into TWRP. After using DC Unlocker, I went back into fastboot and used ADP to install TW RP. I was then able to boot into TW RP. So the difference that DC unlocker made was that it allowed me to use ADB to successfully install TWRP.
I had the very same issue previously with another device. It was running an old version of TWRP. Regardless of what I flashed, it would give errors, etc.
However, using ADB, I flashed the very latest recovery and voila! Flashed a rom successfully as well as other apps without any issues.
It's always best to use the latest possible recovery to avoid issues with flashing.
Glad you solved your problem
Wirmpolter said:
DC-Unlockr allowed you to use adb to flash twrp? How were you able to do that exactly?
Click to expand...
Click to collapse
Good sir, can you link me to a working twrp? I tried several twrps, but i cant seem to boot into recovery. TIA
marktheripper said:
Good sir, can you link me to a working twrp? I tried several twrps, but i cant seem to boot into recovery. TIA
Click to expand...
Click to collapse
Were you running Android Nougat or Oreo? I've just used the TWRP's found here on the xda forums. However, I didn't use TWRP nor dc-unlockr to fix my issue. Have you tried the hardware button combo of volume up And power to boot into it?
Oreo. I tried using the twrps available, but i cant seem to boot into twrp. It goes directly to error mode. Im using the power + vol up btw.
So I've had quite of a rough evening today, first of all: I'm not a rooting newbie, so I really thought I could work out all errors on my own.
Haven't rootet my GM1910 yet, so I wanted to do that. Downloaded the latest TWRP, unlocked the Bootloader, and after "flashing" the recovery, nothing worked anymore. Normally it just jumped into the recovery, now I only got the OnePlus logo with the Text "Fastboot Mode"
this was the errormessage:
"downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)"
After some trying around and not getting it to work, I tried using this to get the device working again:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
tried both flashall.zip and flash-all-partitions.zip.
Now I'm in the QUALCOM CRASHDUMP again with the message
"dm-verity device corrupted Force Dump
kernel_restart"
I've been looking through forms for hours but nothing seems to work for me (mainly the things I wrote above)
I'd really appreciate any help, kind of getting sweaty palms now
Maybe this? It's what I used to unbrick mine but I'm tmobile GM1915....
https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Yup, thanks for the reply, that worked! I'm not trying to root my device anymore though :laugh:
Thanks for making my night sleepable today
If you're trying to root your device.. and you have a pc.. just patch the boot.img of your latest rom using magisk.. then flash it via adb.. ???
thaiten said:
Downloaded the latest TWRP, unlocked the Bootloader, and after "flashing" the recovery, nothing worked anymore. Normally it just jumped into the recovery, now I only got the OnePlus logo with the Text "Fastboot Mode"
this was the errormessage:
"downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)"
Click to expand...
Click to collapse
What are the exact commands/steps did you us to flash TWRP? And why is "flashing" in quotes? You either boot TWRP.img and can just flash Magisk for root without flashing TWRP; or you boot TWRP.img, flash the TWRP installer zip, flash Magisk.
And why does it say "boot.img"? What file are you trying to boot exactly? You should be booting the TWRP.img
I suspect the condition may be due to wrong fastboot command or flashing the wrong file. But we'd need to know the details requested above to figure out what went wrong. What root guide were you following?
In any case, going to fastboot mode, the phone is most likely not bricked. Just stuck in a state that it can't boot into OOS. Probably can recovery using a fastboot ROM, or flash back to stock boot.img.
failed to load authenticate boot image load error twrp
Hi there,
This problem happened to me exactly to days ago and I'm struggling with it.
My last version of Oxygen OS was 10.3.0
Please people, tell us your Oxyygen OS version before the incident.
@redpoint73 as you may see in my attachment, this isn't an error or a mistype. It seems to be a real nasty problem
solid.snake said:
This problem happened to me exactly to days ago and I'm struggling with it.
My last version of Oxygen OS was 10.3.0
Please people, tell us your Oxyygen OS version before the incident.
@redpoint73 as you may see in my attachment, this isn't an error or a mistype. It seems to be a real nasty problem
Click to expand...
Click to collapse
Did you try changing the twrp img file name to "twrp.img" (or similar, just something less complicated) and copying into your fastboot folder?
I agree the error message that it is looking for a file "boot.img" is strange and disconcerting. My suggestion may not fix this, but it is worth a try.
redpoint73 said:
Did you try changing the twrp img file name to "twrp.img" (or similar, just something less complicated) and copying into your fastboot folder?
I agree the error message that it is looking for a file "boot.img" is strange and disconcerting. My suggestion may not fix this, but it is worth a try.
Click to expand...
Click to collapse
Already done, please look at my 1rst screenshot : twrp74.img
solid.snake said:
Already done, please look at my 1rst screenshot : twrp74.img
Click to expand...
Click to collapse
But in the same folder as fastboot.exe, so you don't need to give a path in the command? I know this shouldn't change anything (the way you did it should work). But just an idea. The command would simply be:
fastboot boot twrp74.img
Might be a quirk with 10.0.3 (as you seem to already be eluding) or the TWRP build (maybe try another, slightly older?). But again, just throwing out some ideas to try.
redpoint73 said:
But in the same folder as fastboot.exe, so you don't need to give a path in the command? I know this shouldn't change anything (the way you did it should work). But just an idea. The command would simply be:
fastboot boot twrp74.img
Might be a quirk with 10.0.3 (as you seem to already be eluding) or the TWRP build (maybe try another, slightly older?). But again, just throwing out some ideas to try.
Click to expand...
Click to collapse
Okay, i'll give a try and tell you.
redpoint73 said:
"flashing" in quotes?
Click to expand...
Click to collapse
Because I'm just booting into TWRP first and then install it I thought. And because it didnt work lol
redpoint73 said:
And why does it say "boot.img"? What file are you trying to boot exactly? You should be booting the TWRP.img
Click to expand...
Click to collapse
I am, not sure why it says boot.img
redpoint73 said:
I suspect the condition may be due to wrong fastboot command or flashing the wrong file.
Click to expand...
Click to collapse
I used
Code:
fastboot boot twrp.img
and
Code:
fastboot flash recovery twrp.img
If I'm not mistaken. Was a few days ago now
solid.snake said:
Please people, tell us your Oxyygen OS version before the incident.
Click to expand...
Click to collapse
Was on the latest OOS Beta. But since using the freshly installed ROM with the MSM Tool, my device feels way smoother and the FPS works way faster. I don't know if thats because I bought the Chinese Version of the phone and there where a lot of trojans running in the background /s
But seriously though, way smoother. Probably partly caused by the longer animation duration set by default, but no idea about the FPS
redpoint73 said:
But in the same folder as fastboot.exe, so you don't need to give a path in the command? I know this shouldn't change anything (the way you did it should work). But just an idea. The command would simply be:
fastboot boot twrp74.img
Might be a quirk with 10.0.3 (as you seem to already be eluding) or the TWRP build (maybe try another, slightly older?). But again, just throwing out some ideas to try.
Click to expand...
Click to collapse
Same result here