this is not troll, i just forgot command, but i understand where is problem, i just need help in issuing command, and also keeping TWRP after booting in system
okay, this is not usuall getting stuck in twrp after flashing it via fastboot.
i just need help how to boot , system
because way i installed it, is via fastboot:
' fastboot flash recovery twrp.img '
done good
but i mistakenly followed tutorial , and executed what they said should be okay (i mean it is okay, to boot it into recovery, but my phone manufacturer is stupid and don't include proper fastboot)
so i typed command
' fastboot boot recovery '
which it booted into recovery, and when i reboot into 'system' from twrp it boots into system. i had same issue, but i forgot command how to do this (and link to that solution also)
i just know that, last command, my phone misinterpret it , to boot recovery as boot way. instead of kernel, boot.img
------------------------------------------
because we have beautifull documentation on fastbood issued by google, i don't know how to make it boot system, i mean, boot.img
and, i want it to keep twrp installed, suprisingly, when i go power + volume up , sometimes it brings stock recovery and sometimes twrp.
for now, help me how to issue command, to boot kernel and not recovery
- and phone is: Allview Viva H801 , android 5.0
yea, some no name, that's why i'm asking for help
---------------
EDIT:
i think i managed to permamently flash TWRP, which was purpose, because now I can, use power on + volume up , and it always brings up TWRP (yay)
but now, i don't know how i can access bootloader (fastboot) , if i need to issue commands you instruct me to issue. i can use only twrp
kraken-gz said:
this is not troll, i just forgot command, but i understand where is problem, i just need help in issuing command, and also keeping TWRP after booting in system
okay, this is not usuall getting stuck in twrp after flashing it via fastboot.
i just need help how to boot , system
because way i installed it, is via fastboot:
' fastboot flash recovery twrp.img '
done good
but i mistakenly followed tutorial , and executed what they said should be okay (i mean it is okay, to boot it into recovery, but my phone manufacturer is stupid and don't include proper fastboot)
so i typed command
' fastboot boot recovery '
which it booted into recovery, and when i reboot into 'system' from twrp it boots into system. i had same issue, but i forgot command how to do this (and link to that solution also)
i just know that, last command, my phone misinterpret it , to boot recovery as boot way. instead of kernel, boot.img
------------------------------------------
because we have beautifull documentation on fastbood issued by google, i don't know how to make it boot system, i mean, boot.img
and, i want it to keep twrp installed, suprisingly, when i go power + volume up , sometimes it brings stock recovery and sometimes twrp.
for now, help me how to issue command, to boot kernel and not recovery
- and phone is: Allview Viva H801 , android 5.0
yea, some no name, that's why i'm asking for help
---------------
EDIT:
i think i managed to permamently flash TWRP, which was purpose, because now I can, use power on + volume up , and it always brings up TWRP (yay)
but now, i don't know how i can access bootloader (fastboot) , if i need to issue commands you instruct me to issue. i can use only twrp
Click to expand...
Click to collapse
Connect to adb while booted into TWRP and type the command:
adb reboot bootloader
That "should" boot into fastboot
For future reference, when flashing TWRP via fastboot, immediately after you flash the TWRP.img, enter the command:
adb reboot recovery
That should boot straight into TWRP and keep TWRP. If you let the device boot into any other mode than recovery, it will revert back to stock recovery, you have to boot directly into TWRP immediately after flashing it in order to keep TWRP.
Related
Hello! I've tried to root my phone (Moto G XT1541 Europe 1GB) but failed. I got an error when trying to flash the custom recovery. Unfortunately, it has overwritten the stock recovery and it didn't install. So, now I have a phone without recovery and I can't do a factory reset because of that (I think).
So, this is my question: how can I re install the default Android 6.0 recovery mode for my phone?
Also, my phone boots automatically on bootloader mode and I can't re-lock the bootloader because I can't flash anymore either; I got an error because the pre flash validation failed when trying to flash with adb fastboot, but this is minimal issues that doesn't really bother me, but they could be helpful and if someone knows how to get rid of them, I want to know!
I hope someone will help me!
Azyreal said:
Hello! I've tried to root my phone (Moto G XT1541 Europe 1GB) but failed. I got an error when trying to flash the custom recovery. Unfortunately, it has overwritten the stock recovery and it didn't install. So, now I have a phone without recovery and I can't do a factory reset because of that (I think).
So, this is my question: how can I re install the default Android 6.0 recovery mode for my phone?
Also, my phone boots automatically on bootloader mode and I can't re-lock the bootloader because I can't flash anymore either; I got an error because the pre flash validation failed when trying to flash with adb fastboot, but this is minimal issues that doesn't really bother me, but they could be helpful and if someone knows how to get rid of them, I want to know!
I hope someone will help me!
Click to expand...
Click to collapse
The bootloader cannot be relocked in the Moto G 2015, the best you can do is hide the warning screen. Find the stock image and fastboot flash the recovery from there, or better yet, flash the entire image so you are in a known working state
If you are in Pre-Flash validation, you do not have the correct image for your device... I suggest you post in the "How to flash factory images" thread about returning to stock, if it is possible. You MUST factory default before flashing factory images, if you can't, try 'fastboot erase userdata' and try again.
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system,
reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Rename twrp recovery as only twrp in fastboot folder in your pc , not as twrp.img,
But cmd as fastboot flash recovery twrp.img , then no errors ( are you unlocked bootloader ?)
acejavelin said:
The bootloader cannot be relocked in the Moto G 2015, the best you can do is hide the warning screen. Find the stock image and fastboot flash the recovery from there, or better yet, flash the entire image so you are in a known working state
If you are in Pre-Flash validation, you do not have the correct image for your device... I suggest you post in the "How to flash factory images" thread about returning to stock, if it is possible. You MUST factory default before flashing factory images, if you can't, try 'fastboot erase userdata' and try again.
Click to expand...
Click to collapse
drmuruga said:
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system,
reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Rename twrp recovery as only twrp in fastboot folder in your pc , not as twrp.img,
But cmd as fastboot flash recovery twrp.img , then no errors ( are you unlocked bootloader ?)
Click to expand...
Click to collapse
Hey! Thank you! I've been able to flash the TWRP recovery and now I can do a factory reset (and also send sms, which I couldn't do anymore for some reason).
I still have the issue where the bootloader screen appears everytime I turn my phone on, and I still can't re lock my device because I can't flash anything either. I've recovered all of my data, so I think I'm going to stick with that for a moment but maybe I'll try what you said some day.
Again, really thank you for helping me!
drmuruga said:
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system, reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Click to expand...
Click to collapse
Now I understand why my flashing TWRP did not take. I simply rebooted to system and still have stock recovery installed. I was successful booting twrp via fastboot and successfully flashed supersu 2.62.3. Is this step in listed in any faq? I must have missed it.
So after flashing TWRP, do you then power down device prior to manually booting to recovery?
MrTooPhone said:
Now I understand why my flashing TWRP did not take. I simply rebooted to system and still have stock recovery installed. I was successful booting twrp via fastboot and successfully flashed supersu 2.62.3. Is this step in listed in any faq? I must have missed it.
So after flashing TWRP, do you then power down device prior to manually booting to recovery?
Click to expand...
Click to collapse
Don't power down, already you are in fastboot mode, you can just enter recovery from that. I forget the reference, but i will search and post.
---------- Post added at 04:41 PM ---------- Previous post was at 04:18 PM ----------
I get this from twrp official page
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
In our phone press simultaneously volume down + power button to enter recovery.
whenever i try to go into recovery mode, it takes me to the default one even after i flashed twrp. my bootloader is unlocked and i flashed twrp several times. even when i use the command prompt from fastboot mode it still takes me to the default recovery. any ideas to what's wrong?
Asafbzm said:
whenever i try to go into recovery mode, it takes me to the default one even after i flashed twrp. my bootloader is unlocked and i flashed twrp several times. even when i use the command prompt from fastboot mode it still takes me to the default recovery. any ideas to what's wrong?
Click to expand...
Click to collapse
This could be a solution or a workaround:
"Hello i just had a personal experience with my Asus zenfone selfie Z00T Stock recovery kept replacing TWRP. (Boot loader already unlocked)
This is how i got around it i downloaded the latest TWRP for my device and placed directly in minimal adb and fastboot app folder then i renamed it to recovery .
then i put my device in fastboot mode using the buttons on the phone and After i ran minimal adb and fastboot app as admin then i typed fastboot flash recovery recovery.img
once done i then i typed fastboot boot recovery.img. and my phone booted to twrp recovery then i selected reboot recovery directly on my phone and to finish reboot system (still in twrp) that's it.
(OEM commands to boot from fastboot to recovery do not work on some devices )
it only worked for me eventually because i downloaded the latest TWRP from the official TWRP website.
The idea is to flash the custom recovery and then booting from the custom recovery.img that you just used to flash (the one still on the pc) using minimal adb and fastboot app.
IT may not work on all devices as the commands may change from one device to another but the idea stays the same. (example for nexus fastboot -c "lge.kcal=0|0|0|x" boot recovery.img)
I hope this will help some people out."
sill not booting into twrp
Tiqqy said:
This could be a solution or a workaround:
"Hello i just had a personal experience with my Asus zenfone selfie Z00T Stock recovery kept replacing TWRP. (Boot loader already unlocked)
This is how i got around it i downloaded the latest TWRP for my device and placed directly in minimal adb and fastboot app folder then i renamed it to recovery .
then i put my device in fastboot mode using the buttons on the phone and After i ran minimal adb and fastboot app as admin then i typed fastboot flash recovery recovery.img
once done i then i typed fastboot boot recovery.img. and my phone booted to twrp recovery then i selected reboot recovery directly on my phone and to finish reboot system (still in twrp) that's it.
(OEM commands to boot from fastboot to recovery do not work on some devices )
it only worked for me eventually because i downloaded the latest TWRP from the official TWRP website.
The idea is to flash the custom recovery and then booting from the custom recovery.img that you just used to flash (the one still on the pc) using minimal adb and fastboot app.
IT may not work on all devices as the commands may change from one device to another but the idea stays the same. (example for nexus fastboot -c "lge.kcal=0|0|0|x" boot recovery.img)
I hope this will help some people out."
Click to expand...
Click to collapse
i've just tried this but the 'fastboot boot recovery' command just turn the phone back on from fastboot. thanks anyways!
Tiqqy said:
This could be a solution or a workaround:
"Hello i just had a personal experience with my Asus zenfone selfie Z00T Stock recovery kept replacing TWRP. (Boot loader already unlocked)
This is how i got around it i downloaded the latest TWRP for my device and placed directly in minimal adb and fastboot app folder then i renamed it to recovery .
then i put my device in fastboot mode using the buttons on the phone and After i ran minimal adb and fastboot app as admin then i typed fastboot flash recovery recovery.img
once done i then i typed fastboot boot recovery.img. and my phone booted to twrp recovery then i selected reboot recovery directly on my phone and to finish reboot system (still in twrp) that's it.
(OEM commands to boot from fastboot to recovery do not work on some devices )
it only worked for me eventually because i downloaded the latest TWRP from the official TWRP website.
The idea is to flash the custom recovery and then booting from the custom recovery.img that you just used to flash (the one still on the pc) using minimal adb and fastboot app.
IT may not work on all devices as the commands may change from one device to another but the idea stays the same. (example for nexus fastboot -c "lge.kcal=0|0|0|x" boot recovery.img)
I hope this will help some people out."
Click to expand...
Click to collapse
Work for me. Thanks buddy
This works, thumb up
Asafbzm said:
i've just tried this but the 'fastboot boot recovery' command just turn the phone back on from fastboot. thanks anyways!
Click to expand...
Click to collapse
i have suffered with the same problem for hours until i decided to come here and look for related article , it actually worked and made me wonder that it wasn't that hard to fix it , i just rebooted fastboot and flashed twrp and in the end typed 'fastboot reboot recovery.img
that solved my suffering within 5 seconds. thank you for sharing the knowledge
Tiqqy said:
This could be a solution or a workaround:
"Hello i just had a personal experience with my Asus zenfone selfie Z00T Stock recovery kept replacing TWRP. (Boot loader already unlocked)
This is how i got around it i downloaded the latest TWRP for my device and placed directly in minimal adb and fastboot app folder then i renamed it to recovery .
then i put my device in fastboot mode using the buttons on the phone and After i ran minimal adb and fastboot app as admin then i typed fastboot flash recovery recovery.img
once done i then i typed fastboot boot recovery.img. and my phone booted to twrp recovery then i selected reboot recovery directly on my phone and to finish reboot system (still in twrp) that's it.
(OEM commands to boot from fastboot to recovery do not work on some devices )
it only worked for me eventually because i downloaded the latest TWRP from the official TWRP website.
The idea is to flash the custom recovery and then booting from the custom recovery.img that you just used to flash (the one still on the pc) using minimal adb and fastboot app.
IT may not work on all devices as the commands may change from one device to another but the idea stays the same. (example for nexus fastboot -c "lge.kcal=0|0|0|x" boot recovery.img)
I hope this will help some people out."
Click to expand...
Click to collapse
I had the same issue on Poco F1 and this worked for me as well! Pleasant surprise. First result on google was this article and it worked, 2 minutes work.
Lamantin001 said:
I had the same issue on Poco F1 and this worked for me as well! Pleasant surprise. First result on google was this article and it worked, 2 minutes work.
Click to expand...
Click to collapse
Okay, I was a bit too early with that. The next time I turned off the phone and tried booting to recovery (Vol up+pwr), I got booted into factory recovery (mi-recovery 3.0) :/
Lamantin001 said:
Okay, I was a bit too early with that. The next time I turned off the phone and tried booting to recovery (Vol up+pwr), I got booted into factory recovery (mi-recovery 3.0) :/
Click to expand...
Click to collapse
Update:
I found the solution. I followed the steps in this article:
How can I keep MIUI from overwrite TWRP with stock recovery after a ROM flash?
I'm on fw Global 9.6.6.0. (Bought the phone 'bogus' unlocked with "fake" 9.6.4.0, bricked it while trying to restore chinese fw and re-lock bootloader using miflash - I'm not doing that again brought it back to life using the steps from...
forum.xda-developers.com
Asafbzm said:
whenever i try to go into recovery mode, it takes me to the default one even after i flashed twrp. my bootloader is unlocked and i flashed twrp several times. even when i use the command prompt from fastboot mode it still takes me to the default recovery. any ideas to what's wrong?
Click to expand...
Click to collapse
Try this:
when you are in fastboot mode type:
Code:
fastboot boot recovery.img
This command will boot your phone to twrp. Install twrp .zip file (there are 2 options when installing .img or .zip)
after this go to ADB/Sideload - This is in Advanced section
Then swipe to start a sideload. Now on your pc type:
Code:
adb sideload recovery.zip
This worked for me. I hope this works for you too
Hi guys.
I unlocked my bootloader, and installed the Global Beta Rom via TWRP.
Now, that I am finishing that, TWRP is not installed anymore. And I can't install it.
When I boot into fastboot, and install TWRP like usual, everything is ok. No error appears. But when I want to boot into TWRP via key-combination, nothing happens. When I boot MiUi again, then reboot and try to boot into TWRP again, the Mi-Recoverymenue appears. But not TWRP. Can anyone help here?
After ROM package installed, boot and setup everythings you need, reboot to fastboot mode.
You must install TWRP again, then boot to TWRP by using command, same as the first time you install TWRP. Full commands:
1. fastboot devices.
2. fastboot flash recovery twrp.img
3. fastboot boot twrp.img
DungHD said:
After ROM package installed, boot and setup everythings you need, reboot to fastboot mode.
You must install TWRP again, then boot to TWRP by using command, same as the first time you install TWRP. Full commands:
1. fastboot devices.
2. fastboot flash recovery twrp.img
3. fastboot boot twrp.img
Click to expand...
Click to collapse
Done that.
Device reboot, screen turns black. Then device reboot again, and MIUI will start.
After you install TWRP via fastboot command boot into TWRP via fastboot using the TWRP image on your computer. After TWRP comes up disconnect your phone from your computer, go into the TWRP reboot menu and select reboot into recovery. After you boot back into TWRP it should stick until you flash another ROM zip.
Same issue here.....please have a look at attached picture to see what I have done.
Even after a couple of minutes the screen remains black after trying to boot into TWRP.img with "fastboot boot twrp.img"
Is this a wrong command?
OK with rebooting the system is replacing TWRP, mens I need to go directly into TWRP without rebooting OS., but neither the command above nor ´"fastboot reboot" and simultaniously holding Vol+ and Power ware entering TWRP .....even more
Entering "fastboot reboot" afterwards, device is rebooting normally.
Would be great to explain how I can successfully get TWRP run.
Thx a lot!!
MIUI overwrites the recovery with each boot.
You'll have to get root access and adjust s few files (there is a guide somewhere here on xda) to get it to stay
flyingjack said:
Same issue here.....please have a look at attached picture to see what I have done.
Even after a couple of minutes the screen remains black after trying to boot into TWRP.img with "fastboot boot twrp.img"
Is this a wrong command?
OK with rebooting the system is replacing TWRP, mens I need to go directly into TWRP without rebooting OS., but neither the command above nor ´"fastboot reboot" and simultaniously holding Vol+ and Power ware entering TWRP .....even more
Entering "fastboot reboot" afterwards, device is rebooting normally.
Would be great to explain how I can successfully get TWRP run.
Thx a lot!!
Click to expand...
Click to collapse
Did you download wrong .img file for polaris?
All versions has capacity more than 46 MB. Latest version is 46788 KB.
DungHD said:
Did you download wrong .img file for polaris?
All versions has capacity more than 46 MB. Latest version is 46788 KB.
Click to expand...
Click to collapse
THx mate! actually I downloaded the wrong file. With the correct one evreythink is working fine!!!
hi
I would like to install twrp image, but adb says device not found, while on the list it sees, the serial nr is there..
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Hunter3U said:
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Click to expand...
Click to collapse
+1 for this.
Folks often mix up fastboot and adb. They are related, but different. Different operation requirements and functions.
adb:
- Only works in OS, or alternately in TWRP.
- Requires debugging toggled on in settings.
Fastboot:
- Only works in bootloader-fastboot mode.
- Does not require debugging to be toggled on.
Fastboot is typically what you want for unlocking bootloader, and booting TWRP (for root, etc.).
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
ii9 said:
adb says device not found
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
Click to expand...
Click to collapse
Not completely clear based on your description. But is sounds like you are trying to do "adb devices" and then "fastboot flash twrp.img"?
In fastboot, you want to do "fastboot devices" (no quotes) and should see the phone's ID number in response.
Then you want to do "fastboot boot twrp.img" to boot TWRP, then flash the TWRP installer zip within TWRP. This is per the recommended install guide from the TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Although it's hard to determine exactly what you did wrong, unless you provide a more detailed sequence of what you did, and with the exact commands.
And to be clear, your bootloader is unlocked, correct?
well, sorry for being noob, for me was never a problem with older phones. I always managed to root, put twrp, change rom without any pc, but this double slot system kills me
so I managed to wipe everything before, vendor, sytem.., all
I wanted to put the havoc rom after formatting, but there was 5 local disks when I opened the phone folder on the pc, and obviously didn't copy the files on it. Therefore I did reboot to recovery, since that I had only the fastboot screen.
After that I unbricked it, all was fine again on the stock
After opened again the bootloader (yes, also before it was) installed the twrp.img, Installed the twrp zip, reboot it.
I followed the steps from havoc, but it said error 7, few times I tried. I reboooted the recovery again, and now I'm again the fastboot only, doesn't even show the warning msg about open bl, and doesn't go anywhere again.
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
ii9 said:
*SNIP*
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
Click to expand...
Click to collapse
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
runningnak3d said:
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Click to expand...
Click to collapse
I guess I lost it, time to accept the stock rom :crying:
I' not that old, but I can understand now why my grandma doesn't know even what is a phone
At the end I managed to do the unbrick again, after I installed havoc, I get rid of the error 7, and it showed me st like qualcomm crashdump, I was about to give up, but I went back to twrp installed again, now it's fine. Such a pity that it's not stable yet, I don't dare to touch after this..
tHanks for the info, in case I'll ever need I'll try to read again another 100x maybe I'll find out.
Bradl79 said:
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
Click to expand...
Click to collapse
fastboot flash boot imagename
I did this
ii9 said:
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
Click to expand...
Click to collapse
I think you are doing something wrong.
boot.img is basically a kernel, not TWRP.
Booting TWRP and flashing a boot.img are two completely different things.
It would help if you cut/paste the actual command you typed, so we can see what you did.
The command should be: fastboot boot twrp.img
That isn't what you did.
---------- Post added at 11:55 AM ---------- Previous post was at 11:48 AM ----------
ii9 said:
fastboot flash boot imagename
I did this
Click to expand...
Click to collapse
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Seems similar, but this does something very different from the command you used. Syntax in fastboot/adb is absolutely ciritical. Always type fastboot and adb commands exactly as indicated, and double check everything before issuing the command.
fastboot boot twrp.img This boots the image file that is named. Note that you are not flashing anything with this command. Think of it as a remote boot of the TWRP file that is on your computer.
fastboot flash boot imagename This flashes the named file to the boot partition (basically the kernel)
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
redpoint73 said:
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Click to expand...
Click to collapse
Sorry, I messed up with the copy and paste, I didn't sleep too much in the last days for the hot, I'm a bit heavy in the head, pls exuse my bs. I also tried this one that you wrote, but didn't manage to boot still.. I have no clue what went wrong, but again, thanks, in case I can come back to read again.
Hunter3U said:
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
Click to expand...
Click to collapse
Not exactly, the end goal to have a clean rom, with basic custumization, that even stock should include in my opinion, like disable headups.., extended screen etc. Plus without google staff, for me it's too strict. As in this moment not so many choice, havoc looked the most near to my wishes, in fact very nice after these hours, I guess I'll be fine with it when the bugs will disappear.
Anyway 1-7 was always without problem. Today after 2 unbrick and bl opening what I did is, through fastboot I entered to the img, from there I flashed the zip, reboot recovery to make sure it stays. I put files on the phone, wiped dalvik and data, install rom+twrp and as it is written here and also on that thread, I rebooted recovery. And I wanted to repeat the flash, but I had the internal storage 0mb thing. So I needed to format data (that's the solition I found) and reboot again, put back files, flash, reboot, flash again, and after I got that qualcomm crashdump screen. I hold the up+power to get back to twrp (or down, not sure) and I flashed again, but only once, so after it worked finally. Since that I'm fine
But sure I need to learn this stuff, it cannot be that I always face st that nobody else does
I hope the managed soon the ota for custom roms and we can do it easy and quick without setting the phone over and over again with all the apps, settings.. (probably only me in the world need to do so, as I start to loose it with the tech staff)
Poor phone is just couple of weeks old, but already saw everything
Thanks for writing
If it means anything to you, I use stock OOS+TWRP+Magisk+Renovate ICE+Xposed (to ignore the secure flag, otherwise Netflix doesn't work over HDMI). Everything works, including Google Pay.
kk
kraken-gz said:
i managed to flash twrp via fastboot, with command:
fastboot flash recovery recovery.img
and then i applied:
fastboot boot recovery
and it booted into twrp (yay), but when i try to reboot it into system (or poweroff, and on), it boots into twrp. succesfully managed to replace stock recovery, but now i cant go into system. i got backup of system, but i don't know how to boot into system now.
phone is Allview Viva H801
I don't know how i can get into fastboot now via twrp. Is there way to communicate with twrp via PC. because twrp terminal , closes keyboard when i press key 'b', which makes it impossible to type any command (to get into fastboot )
can i fix this via twrp as i cant go into bootloader
Click to expand...
Click to collapse
TWRP don't have reboot bootloader option!?
Re-flash Stock ROM.
Thread closed as OP removed the content from the opening post.