Hello guys I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command". So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img". Everything ok, the screen resumes, 3 minutes later it died. This is hard brick?
FrancescoPtr said:
Hello guys I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command". So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img". Everything ok, the screen resumes, 3 minutes later it died. This is hard brick?
Click to expand...
Click to collapse
You are not supposed to flash the image. Make sure you have the latest version of sdk tools. AND if you are new to this kind off stuff READ careful before executing random commands not specific to your device. You might be better advised asking in twrp thread. That would also help keeping the forum clean.
Related
Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
FrancescoPtr said:
Hello guys
I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command".
So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img".
Everything ok, it restarts the screen, 3 minutes then it is turned off and remains in the initial screen where it says that the bootloader is unlocked, it does not go in fastboot mode not in recovery
Tips?
Click to expand...
Click to collapse
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
ImmorTaLGiLL said:
Use the Msm tool to recover if your phone is bricked.
https://forum.xda-developers.com/on...-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
Click to expand...
Click to collapse
I tried but didn't see it
Sadistic_Loser said:
When it comes to A/B slot phones (Like the OnePlus 6T), you're not suppose to use the fastboot flash recovery twrp.img command. The reason why is because that command doesn't apply to A/B slotted phones, you need to use the fastboot boot twrp.img command to boot into TWRP and then flash the TWRP flasher for OnePlus 6T which can be found here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Make sure to download the flasher zip and the latest img for TWRP.
Drag the .img into the fastboot folder and use fastboot boot twrp-3.3.1-8-fajita.img. Then once it boots into TWRP, drag and drop the installer zip onto your phone's storage and flash it. Reboot into recovery and you should have TWRP on your phone.
Click to expand...
Click to collapse
ok but it does not go into fastboot mode or in recovery mode
FrancescoPtr said:
I tried but didn't see it
Click to expand...
Click to collapse
Make sure the device is off,Press volume up + volume down button then connect it to the computer.
If your device still doesn't show up,try pressing volume up+volume down+power button and then connect it.
This worked for me in many cases.
When I connect my phone via USB it shows up in the device manager as Qualcomm HS-USB.... But when I try using MSM it shows the phone connected on port 16 and I hit start and it fails after 16 seconds because it can't do a download. My question is is the download external via internet or is it a file in the MSM folder? I might be blocked by firewall at work if external.
EDIT: Looks like I found my issue. I couldn't tell if my phone was on or off since I had no display after trying about 20 more times I guess I got it ON.
Hello everyone,
It's my first time on a forum like this, I hope i'm doing it right and that you'll be able to help me
So, I followed Samuel Ridosko's tutorial to install Android on lumia 520. I followed every step with success until I ran uefi2lk.cmd.
It happened very fast, i think with success, but the tool closed by its own before I had time to see anything. But what I did notice is that my phone didn't reboot in TWRP. My phone is found under device manager, in Kedacom USB - Android Bootloader Interface. No error message there.
Fastboot does find my phone. I tried to re-install android drivers, and restart the system. But the command "adb devices" still doesn't show anything at all, contrary to fastboot.
I read the comments below the tutorial and tried to flash things manually, like so :
fastboot boot DATA\gptflasher.img
fastboot format system
fastboot format userdata
fastboot format cache
fastboot flash TZ DATA\TZ.img
fastboot flash modem DATA\modem.img
fastboot flash recovery DATA\twrp.img
fastboot oem reboot-recovery
The phone reboots, vibrates, i see the nokia logo and.... nothing more. Still detected in "fastboot devices", not "adb devices".
I can't perform the adb sideload step.
I do have a backup, but since adb doesn't recognize my phone, I have no idea of what to do to fix things.
I tried getting help under the video tutorial, but no one replied, so, i really hope someone here might try to give me a hand ! and sorry if my English is a little odd, I'm french (and new at developer's stuff, i'm actually a webdesigner girl, so it's not easy )
Thank you in advance for taking the time to read and help, and sorry if I posted at the wrong place or anything !
This particular model is a LGMS550. It is currently on stock firmware at Android 7.0, and it is just not making it's way to TWRP.
I've tried the method where you do the factory reset prompt that supposedly takes you to TWRP, however this only brought it to the screen that read "Erasing" and rebooted like normal.
I made extra sure the bootloader was unlocked.
Trying "fastboot boot (twrpfilename).img" only gave me "FAILED (remote: unknown command)" from the command prompt.
I tried 2 different versions of TWRP. The 64-bit version linked here, along with the official version (3.3.1 currently).
Using "adb reboot recovery" with USB debugging brings me to the "no command" screen that I've seen talked about all over the forums with no good answers. Even looked around on other forums to no avail.
Also tried the awful answer I read that just said "keep trying the factory reset method until it works". Did it 5 times to no success.
What a strangely common issue that has no solution. Does anybody have anything or am I SOL for no apparent reason?
EDIT: Got a quick, fast answer from the lovely person from this post.
No idea the circumstances of what caused this, but hope this will prevent some headaches for you all in the future. Also just to future-proof in case of the post being deleted or something:
1. Go back into fastboot (easy way is just to hold volume down while powering on with the USB plugged in)
2. Re-lock the bootloader with "fastboot oem lock" and unlock it again with "fastboot oem unlock".
3. Erase the recovery partition with "fastboot erase recovery" and then flash TWRP with "fastboot flash (file).img"
4. Reboot and do the hard reset method (reboot while holding power+volume down, let go and press back down instantly when the LG logo shows up, and factory reset by pressing Yes on the prompt twice)
5. Hopefully you're in TWRP by now.
No idea why this works, but it's the only thing that ended up working. Hope it works for you.
Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover.
Suggestions please??
Note 1: I'm pretty bad with this kind of stuff, need step-by-step instructions.
Note 2: rom is AOSP 7.1.2 but I guess is irrelevant, as even TWRP does not load.
Thanks in advance!!
Can you fastboot boot the TWRP recovery?
Hmmm dont know exactly what that means sorry; I mean I havent tried connecting it to the laptop and using thr ADB toolkit, but I can reset via Power+VolDown to the bootloader menu (? the android layind down and giving the option to StartSystem/ SwitchOff/ Restart/ RecoveryMode), and choosing RecoveyMode it tries to launch TWRP (it even shows the logo) but stays there on the splashscreen, doesn't quite manage to give me the TWRP menus
Someone?
AndDiSa said:
Can you fastboot boot the TWRP recovery?
Click to expand...
Click to collapse
let's see... I set in recovery mode, connect to the PC (does not recognise it), and with "fastboot boot twrp.img" it just sends/writes the file, the tab shows the Google logo with open lock, and then tries to launch Twrp, but as before, it just get stuck in the splashscreen "TeamWin Recovery Project 3.3.1.0" , so just the same.
Command "fastboot flash boot twrp.img" the same
Command "fastboot flash recovery twrp.img" the same
Command "adb devices" returns the list empty
Command "adb reboot recovery" returns "error: no devices / emulators found"
Command "fastboot oem unlock" returns "(bootloader) bootloader is already unlocked"
I tried running a tool called FirstAid (https://forum.xda-developers.com/devdb/project/dl/?id=16684) but does nothing for me
I'm lost, please help
Video and photos of the issue (device, not adb)
video: https://photos.app.goo.gl/GrFrmQhbyQeHVFZN7
Well, looking at your video it seems that there is no bootable ROM installed and also the recovery (for what ever reason) has some issues to start.
The fact, that you are able to boot into bootloader shows that at least it's not completely bricked ... but there's still the chance that the flash memory has some issues.
I would connect the device via usb with a PC and try to do a
fastboot boot <twrp-3.3.1-grouper.img>
to whether in that case the recovery is booting.
If this is successful, the next step would be re-flashing the recovery into the recovery partition and booing into recovery mode from the bootloader.
If this is successful, too, wiping and flashing a new ROM would be the last step.
Hello. I'm a newbie to these kinds of things. This secondhand phone that I bought has a HavocOS, so I've been meaning to change it. I successfully got ArrowOS 12.1 for my phone, but then I couldn't access TWRP (screen remains at the TWRP 3.23 logo). I assumed that perhaps I should reinstall the TWRP, so I tried to follow the guide in https://twrp.me/asus/asuszenfonemaxprom1.html. My phone successfully entered into fastboot mode, but when I enter the "fastboot flash recovery twrp.img" command, it says <waiting for any devices> . Where did I go wrong and how do I fix this?
Thank you in advance.
Oh, and I followed this https://forum.xda-developers.com/t/...ng-up-in-fastboot-mode-windows-10-11.4194491/ and "android" showed up in my device manager, but cmd still says <waiting for any devices>