No way out (bricked) - OnePlus 2 Q&A, Help & Troubleshooting

I was on oxygen 3.0.2, so i decided to root my phone, first of all i unlocked my bootloader, but after the install of the root zip file, i got stuck in a bootloop, no way out i can't sideload or mount storage, i can access to recovery and fastboot so.. if u may help me to flash any another rom or just turn back to stock i'll be glad!
recovery: ok
fastboot: ok
no adb
bootloop
EDIT:
when the device is off, with command "adb devices" says:
<serialnumber> unauthorized

tried qualcomm usb mode?

Related

[Q] Can't boot. Stuck on Google logo

Hi,
I really need some help on this one. I wiped everything using TWRP recovery in preparation of installing a custom ROM.
I then realised I forgot to transfer the custom rom to my phone! When I went to reboot the system it says "No OS installed! Are you sure you want to reboot?"
No it's stuck on the google logo.
Is there a way to see if any Rom is still installed on on my phone or if it deleted my stock rom also?
I tried to push the rom through adb but it says error read only.
Also USB debugging is not enabled but I can't boot to enable it.
Please help.
Thanks
Go into fastboot and ensure your fastboot devices command shows your s/n. If so then grab the stock image from xda and flash it.
fastboot flash bootloader BOOTLOADERNAME.img
fastboot reboot-bootloader
fastboot flash radio RADIONAME.img
fastboot reboot-bootloader
fastboot -w update IMAGENAME.zip
Alternatively, using ADB.
from command prompt: adb remount
adb push <FILE PATH> /sdcard/0/
Boot into recovery (I use CWM) and then install it.
Thanks for the quick reply.
I managed to solve it by using the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2010312
It's all in fastboot so I had no problems
Problem solved.

[Q] NOT BOOTING HELP A noob please!!

OK so phone was rooted with twrp installed. decided to update to latest ota 30b only I wiped and just flashed boot file and supersu without the actual rom. I know. now the phone goes straight into fastboot mode... I would think twrp is still installed but dont seem to be able to boot into it. I had adb and fastboot on my pc from before but havent used this in some time. if I try to open either of these the command window pops up and quickly closes.. What can I do ?.
new info: fadtboot is working in fact i have wrote a twrp recovery but still cant boot out of fastboot... adb device not listed. i reinstalled minimal adb and fastboot. help

adb device unauthorized

Hey, I'm on A2017U stock B19 bootloader unlocked,
I want to backup my stock recovery and boot using axon7tool (I want to flash twrp after that),
When I type: "adb devices" I get my device number and next to it: "unauthorized",
And when I type "adb reboot edl" I get: "error: device unauthorized."
USB debugging enabled.
What am I missing?
(also when I try to go to edl mode (vol up + vol down + power) nothing happens...)
Thanks
I think u need to be root in order to backup those files using adb and you have to have the bootloader unlocked in order to root even tho theres a thread showing how to root without bootloader unlocked
Thanks,
My bootloader is unlocked...
Is there any other way to backup stock recovery and boot before flashing twrp?
Hello, do you have the proper drivers installed for the phone usb wise and in edl mode it won't do anything, that's normal.
Hi, Thanks,
I think so, as I say, it does recognize my phone number on "adb devices" , and I successfully unlocked my bootloader using fastboot

[ZE00ED] ERROR: Cant load invalid boot image

Hey, i was trying to downgrade my phone but insted of this i think i messed it up really badly.
Exact things i did:
I used adb (adb reboot bootloader, fastboot boot stockboot.img)
and after reboot this error appeared.
I have no root on my phone. So i have stock recovery mode.
Please any magical help?
I can get into fastboot mode and android recovery, even twrp but i cant copy files from computer.

Can't flash via TWRP, "failed mount system", twrp sideload not working either.. stuck

Can't flash via TWRP, "failed mount system", twrp sideload not working either.. stuck
I need my phone for work tomorrow so any help would be greatly appreciated.
I'm on TWRP 3.2.3-1 and was using the latest stock oreo rom from here: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
My phone suddenly didn't have a reception today, after rebooting I regained reception but couldn't make calls. I rebooted to recovery and tried to dirty flash the same stock twrp flashable oreo rom that I was using and it failed. Apparently the OS got corrupted. I tried repeatedly to flash the ROM and then noticed I was getting an error : failed to mount system , invalid argument. I couldn't mount system via the Mount tab in TWRP and I couldn't find anything helpful to resolve this error.
I did some more research downloaded the fastboot flashable ROM from here : https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 and tried to flash the rom via adb using adb sideload in twrp but twrp doesn't seem to load that function correctly. In the elevated command prompt in the adb directory I type adb sideload filename.zip and it just freezes up my PC. My device does show up with the adb devices command and shows " *Serial Number* RECOVERY ".
I don't understand what to do with the instructions in the fastboot flash stock thread I posted above and I'm at the limit of my knowledge. No idea how to proceed... any help is greatly appreciated.
I tried extracting the xml.zip into the adb folder and rebooted to bootloader/AP Fastboot Flash Mode and was going to try the commands in the fastboot Rom thread but my device only shows up in adb devices when I load twrp. uhhhhgggghhhhhh guess I'll have to buy a backup phone tomorrow while I try to get this one working
Holy hell.... I didn't realize since I was in the fastboot/bootloader I had to use "fastboot devices" command to see the device. Tried that and saw the device listed, so I created a .bat file using the commands in the fastboot roms thread above and I have a functional device again. Whohoooooo!
Did you try to format /System/ as EXT4?

Categories

Resources