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>
Related
Hello.
I rooted my phone using Kingo Root and then installed the chinese recovery. However, I uninstalled a system app without realizing it and then the system began to malfunction. I flashed the stock recovery backup which I had, and, that is when my phone became useless.
The status quo:
1. The phone switches on, shows the gionee logo and then proceeds to the stock recovery.
2. When I choose to reboot, it just returns to the same screen.
3. I can enter fastboot mode (the logo screen with "fastboot mode" written in the bottom left corner") but, "fastboot devices" returns blank and any other command results in a <waiting for device>.
I have no idea how to proceed further and, without any help this phone is doomed for the drawer. I'm researching online but, so far I haven't been able to come up with a solution. I updated the fastboot+adb drivers but, the fastboot command line still doesn't work. The adb sideload command line is working but, I don't know of any way in which a custom recovery may be installed by using the sideload command in stock recovery.
Any and all help will be greatly appreciated.
Material Particulars:
H/W version: E7 Mainboard 1.3.2
S/W version E7 0301 V5636
16 GB
India
Hi all!
Fairly new to rooting & flashing on Android - but I've done so successfully in the past on an older device.
Not fully happy with OxygenOS (wanted to flash a Cyanagen ROM) - but I'm having some trouble getting everything to work.
Here are the steps I followed and results:
Put OP2 into Developer Mode & enabled USB debugging
Connected OP2 to MacBookPro via USB
Opened Terminal on Mac & ran "adb reboot bootloader" to reboot the device into fastboot mode
One in Fastboot Mode, ran "fastboot devices" via Terminal to ensure it was readying my OP2 (everything is fine here)
In Terminal, ran "fastboot flash recovery recovery.img" (I had previously downloaded a copy of TWRP into the same folder as ADB & Fastboot & renamed the TWRP image to "recovery.img")
In Terminal, next ran "fastboot boot recovery.img"
Once it booted into TWRP, I navigated to the SuperSu .ZIP file saved on my OP2 and ran through the install process...and rebooted the device.
This is where it hangs on the boot screen - It's a red dot with 2 white dots circling around it.
(I tried to add an image of the screen to this post, but it says I'm too much of a newb to be able to post images
It's been on this screen for at least 30 minutes now - and I'm thinking it shouldn't take this long at this point (but I could be wrong).
Can anyone please help me?
Thank you much in advance!
just one more step
here you go:
http://forum.xda-developers.com/oneplus-2/help/oneplus-2-bootloop-flashing-supersu-t3424834
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.
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.
I unlocked the bootloader, the FRP too.
Now I need to flash the TWRP image with the command "fastboot flash recoery_ramdisk twrp.img" because it is a partition A only.
Those are the steps I take:
1) connect USB the device
2) enable USB debugging
3) adb reboot bootloader
4) the phone boots with the fastboot screen
(it says PHONE unlocked, FRP unlocked)
5) I put the command: "fastboot flash recoery_ramdisk twrp.img" (I have twrp.img in the same folder as the adb)
6) the console gives me <waiting for the device>
I red around a lot, and in a lot of threads even here on XDA it says it's adriver issues, so I isntalled Universal ADB driver, then 15 seconds adb drivers, the n tried to downlowad the Hi Suite but it doesn't even start (I have Win 10)
Additional info:
The boot loader is unlocked, also in the settings (I used potatoNV method)
I have EMUI 5.0.3
Android version 7
Number model PRA-LX1
What to do guys?
cocclina said:
I unlocked the bootloader, the FRP too.
Now I need to flash the TWRP image with the command "fastboot flash recoery_ramdisk twrp.img" because it is a partition A only.
Those are the steps I take:
1) connect USB the device
2) enable USB debugging
3) adb reboot bootloader
4) the phone boots with the fastboot screen
(it says PHONE unlocked, FRP unlocked)
5) I put the command: "fastboot flash recoery_ramdisk twrp.img" (I have twrp.img in the same folder as the adb)
6) the console gives me <waiting for the device>
I red around a lot, and in a lot of threads even here on XDA it says it's adriver issues, so I isntalled Universal ADB driver, then 15 seconds adb drivers, the n tried to downlowad the Hi Suite but it doesn't even start (I have Win 10)
Additional info:
The boot loader is unlocked, also in the settings (I used potatoNV method)
I have EMUI 5.0.3
Android version 7
Number model PRA-LX1
What to do guys?
Click to expand...
Click to collapse
Hi There.
change you rcovery image file name to "twrp.img" and move them to c:/ partition.
then enter the command bellow : fastboot flash recovery c:/twrp.img
NOTICE : Of course, I installed twrp custom recovery on my huawei p8 gra-ul00 phone and im very regretted.
And you're doing this at your own risk.
Regards,