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.
Related
Hello everyone!
Okay, so I'll try to keep it as short as possible but with the most information I can give ofc.
So here's what I did with my Oneplus 2:
- unlocked bootloader
- flashed custom recovery (twrp)
- flashed superSU.zip
- flashed xposed.zip
- used it for about half a year if not even longer
everything on Lollipop 5.1 stock rom so xposed would work.
Everything was fine but some day when I wanted to enter twrp recovery it didn't work. (I swear, this is the most illogical thing ever but I DID NOT CHANGE A THING!)
I tried to enter recovery via fastboot but that didn't work either.
So I reflashed latest TWRP recovery.img for OP2 via fastboot.
When I pressed power + vol. down to see if it'd work nothing happened.
When I tried to enter recovery when my system was booted via power button->restart->recovery my phone got stuck in a bootloop.
I had to go in fastboot mode to enter "fastboot continue" in order to get my phone booting normal again.
Then, one night when my phone was in my pocket it vibrated and got stuck in the bootloop again, even though it was booted into system and locked last time I used it (minutes before that).
I had no access to a computer at that moment so I had to wait for a few days.
Now when I boot my phone in fastboot mode and try to enter "fastboot continue" on my cmd nothing happens with my phone and cmd says "(command write failed (Unknown error))" even though "fastboot devices" shows that my device is connected properly.
I also tried:
- the FirstAidKit, copied the Win Files in my fastboot directory and started the firstaid.bat but it stops on "fastboot flash boot boot.img" (I waited for like two hours).
- a different USB port (USB 3 and USB 2)
I am kinda depending on my phone so yeah..
If someone knows how to fix this I would be very grateful.
Have a good day/night
SoulSnatcher
Do you have a backup??
If yes, download the latest official OS from Oneplus and the stock recovery. Flash the stock recovery. Try rebooting into stock recovery. If it succeeds, wipe everything and flash OS via adb sideload.
Honestly, I can't guess what went wrong with your device. Maybe it could've been some app which crashed the entire system.
AJay27 said:
Flash the stock recovery.
Click to expand...
Click to collapse
Same problem as with the FirstAidKit:
"fastboot devices" does display the device but "fastboot flash recovery recovery.img" doesn't do anything (I waited for 1h just to make sure).
I'll try this Mega Unbrick Guide for A Hard Bricked OnePlus 2 next, even though I can get into fastboot but since it doesn't do s**t I'll have to give it a try. I mean, what's the worst thing that could happen? That my phone gets bricked?!
Haha.... hmm.
I'll keep the person(s) updated who care to know what's happening.
Cheers
fml
After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
CanIHelp said:
After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-p9lite/how-to/unified-help-thread-huawei-p9-lite-t3649152
Post 5. Unbricking EMUI 5. Don't take for granted it will work, but considering FRP is locked, this is the only way not needing a unlocked bootloader.
Doesn't work. It's still stuck at the "Your device is booting now..." under the vmall link screen.
Isn't the 3-button method counting on the original recovery being in the recovery partition?
I only have the second recovery working (that eRecovery which only lets you "download and install the latest recovery and system"...and doesn't do anything).
Is there a way to override the frp lock? I saw a couple of tools online claiming to do that, but none worked. I haven't tried DC-Unlocker. If I'm gonna pay for it, might as well go to a service
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Plug your phone on computer.
You see yellow advice? Appears automatically.
Juste after this advice, tip "fastboot reboot bootloader".
After, unlock your bootloader again "fastboot oem unlock YOUR_OEM_CODE"
Ok now shutdown and hold buttons for boot to TWRP recovery, if not appears, flash it on "fastboot flash recovery recovery.img"
Warning command not allowed on fastboot is 90% time du at bootloader unlocked (even if he says it's good)
dariomrk said:
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Click to expand...
Click to collapse
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
CanIHelp said:
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
Click to expand...
Click to collapse
No problem mate, nice to hear you did it without problems.
Hello,
Can anyone assist me in fixing my issue? My phone couldn't boot to recovery mode, i see the TWRP bluescreen and it immediately enters the boot loop. I can boot to fastboot&rescue mode but adb is not detecting my devices. I tried reinstalling the driver and also restart the adb server, but no luck. Tried different USB ports \cable\laptop, but no luck.
Need some assistance or direction to address this issue.
Regards
sri1225 said:
Hello,
Can anyone assist me in fixing my issue? My phone couldn't boot to recovery mode, i see the TWRP bluescreen and it immediately enters the boot loop. I can boot to fastboot&rescue mode but adb is not detecting my devices. I tried reinstalling the driver and also restart the adb server, but no luck. Tried different USB ports \cable\laptop, but no luck.
Need some assistance or direction to address this issue.
Regards
Click to expand...
Click to collapse
adb does not work in the bootloader (Fastboot mode)
in bootloader use
fastboot boot twrp.img
just be sure twrp has the correct name and is in the same folder as adb / fastboot
@sri1225,
Adding to clsA post:
If the phone is in fastboot mode, "fastboot devices" should work to confirm PC connection is good and produces a similar response as "adb devices" does when in adb mode.
What led up to the phone getting broken? You said it's bricked - so it won't boot up to normal operating mode?
clsA said:
adb does not work in the bootloader (Fastboot mode)
in bootloader use
fastboot boot twrp.img
just be sure twrp has the correct name and is in the same folder as adb / fastboot
Click to expand...
Click to collapse
divineBliss said:
@sri1225,
Adding to clsA post:
If the phone is in fastboot mode, "fastboot devices" should work to confirm PC connection is good and produces a similar response as "adb devices" does when in adb mode.
What led up to the phone getting broken? You said it's bricked - so it won't boot up to normal operating mode?
Click to expand...
Click to collapse
I tried to flash with the B180+Stock+Rom, after that I cannot go back to TWRP or in recovery mode.
When I do the "fastboot boot twrp.img", in the fastboot&rescue mode, the phone reboots to twrp screen and goes back to the boot loop again. I have tried both the twrp images available in the forum for this device.
Regards
sri1225 said:
I tried to flash with the B180+Stock+Rom, after that I cannot go back to TWRP or in recovery mode.
When I do the "fastboot boot twrp.img", in the fastboot&rescue mode, the phone reboots to twrp screen and goes back to the boot loop again. I have tried both the twrp images available in the forum for this device.
Regards
Click to expand...
Click to collapse
The B180 stock rom replaces TWRP with stock recovery
If you want TWRP again flash it from the bootloader
fastboot flash recovery twrp.img
when you enter TWRP
goto Wipe/Format Data/ and type yes
now you can root the phone or leave it as is
Fwiw, the 'boot' command only boots twrp, it doesn't flash it. Thats useful for testing that twrp works. The proper command to flash is immediately above this post. Take it from me - always test first. If it boots, it works.
clsA said:
The B180 stock rom replaces TWRP with stock recovery
If you want TWRP again flash it from the bootloader
fastboot flash recovery twrp.img
when you enter TWRP
goto Wipe/Format Data/ and type yes
now you can root the phone or leave it as is
Click to expand...
Click to collapse
Tried flashing TWRP but didn't work. Couldn't get to TWRP screen at all.
sri1225 said:
Tried flashing TWRP but didn't work. Couldn't get to TWRP screen at all.
Click to expand...
Click to collapse
Try the command 'fastboot devices', what does it output..? Are you sure you are in fastboot mode, with the screen and the Android with its chest popped open..?
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. 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>