i was updating twrp when i flashed the latest image via twrp and selected the incorrect partition. Now no matter what i do i cannot connect via adb or fastboot , it reboots into bootloader with any other option.
real shame as i have had this device since new and i cant believe after all these years i manged to bugger it up. i tried wugs toolkit but it will not be detected by adb in windows or Linux and i have tried a few cables as well , really hope its not a brick.
Related
Hello All
I've rooted and installed TWRP recovery. And accidently wiped all partitions (system, data, caches...). Currently no OS installed.
Tried installing Cyanogen mods and also default ROMs via TWRP but getting error saying
====
Unknown command "screenshot"
E: Unable to mount /spare
====
Also tried flashing default ROMs...same error . No luck.
Tried wiping all partitions again.
connected to my linux lap
Device is connected and listed while running command "lsusb". (USB data connection working)
But not detecting under adb devices also not shown under fastboot mode. (So no luck to flash via PC).
All forums saying "check usb debugging" to show under adb devices. How can I ..if there is no ROM
Also TWRP is restarting after some time.
-------------------*******helppp******************************
Hi,
I have the same problem, few post below.
During my searching I found this post, but I get error during
fastboot erase spare
It hard to say what wrong is with this partition.
Maybe you will be have more luck
Elokwentnyemu said:
Hi,
I have the same problem, few post below.
During my searching I found this post, but I get error during
fastboot erase spare
It hard to say what wrong is with this partition.
Maybe you will be have more luck
Click to expand...
Click to collapse
In my case, the phone is not listed under fastboot devices But it's connected to computer in fastboot mode and we can see the device is listed when command lsusb is executed.
antoponline said:
In my case, the phone is not listed under fastboot devices But it's connected to computer in fastboot mode and we can see the device is listed when command lsusb is executed.
Click to expand...
Click to collapse
I checked on Manjaro and my phone is present under fastboot. Try reinstall drivers or use other PC to connect by fastboot.
so sad for both of you guys i've already encountered this before try this any of these.
- use adb sideload via TWRP using stock firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip
- if you have a back up restore it, then boot to fastboot and flash the fastboot, boot and recovery of this firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip then boot to recovery and side again using this firmware.
- try this link if it's work http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
sorry guys i forgot how i managed to solve this i will update this thread. just always remember use always this firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip and back your current rom even if it's stock or custom this is most important. if you can access bootloader just do the flashing fastboot, boot and recovery this would be easy if you can access bootloader.
so i feel like Ive tried everything.
tried to flash a rom and gapps in twrp and phone booted to warning screen with the yellow triangle.
passes that and then goes to google splash screen with unlock icon. and then repeats to the cycle.
i have tried multiple 6.x.x builds using skipsoft toolkit with no change.
i have installed twrp and tried to flash 6.x.x rom and 7.0.0 rom.
i have tried to flash stock NBD90X 7.0.0 using nexus root toolkit.
i have tried going into stock recovery and wipe data/factory reset
i have tried minimal ABD fastboot and running the commands manually.
All have failed to change the boot looping i experience.
my phone is unlocked.
computer can see it as fastboot devices
computer CANNOT see it under abd devices
i am able to install and get into TWRP using skipsoft tookkit.
i feel like i am running out of things to flash onto the device haha
any help is appreciated.
barrackOBAMA said:
i have tried multiple 6.x.x builds using skipsoft toolkit with no change.
i have installed twrp and tried to flash 6.x.x rom and 7.0.0 rom.
i have tried to flash stock NBD90X 7.0.0 using nexus root toolkit.
i have tried going into stock recovery and wipe data/factory reset
i have tried minimal ABD fastboot and running the commands manually.
All have failed to change the boot looping i experience.
Click to expand...
Click to collapse
First, I'd recommend staying away from Toolkits, as you can't really see what's happening and diagnose issues. Since you've used fastboot/ADB commands, you know they are faster anyway. When you say your PC can't recognize your device in ADB, was your device in recovery? Make sure you're in recovery and you're ready to receive ADB commands. If you CAN see your phone with fastboot that means you're in the bootloader, whereas you have to boot into recovery to see your device via ADB.
Also, you didn't outline anything else you may have done. Did you restore from a nandroid with a buggy version of TWRP? Your issue sounds like the TWRP EFS restore bug (3.0.2-2). It effectively bricks your device, but there is a thread here that discusses it. Effectively you need to be recovery ADB mode and run a couple commands to delete your EFS partition and that will fix the issue.
More info here: http://forum.xda-developers.com/nexus-6p/help/im-stuck-google-logo-stop-reboots-twrp-t3452842
Make sure you've also installed the updated 3.0.2-3 TWRP as it will work with encrypted data and doesn't have the EFS bug.
Please help!!!
I tried to update my rooted Nexus 6P to 8.0.0 (OPR5.170623.011, Nov 2017) using the Flashfire app and something went wrong!!! The phone is now stuck in bootloop and will not get past the 4 google coloured dots. I can boot the phone into the bootloader and then get into TWRP recovery from there but thats pretty much it.
I hoped I would be able to fix it by flashing the system image, bootloader etc using adb and fastboot but have had no luck. I have tried on both a PC and a Mac and neither seem to recognize the device. When using the commands "adb devices" or "fastboot devices" nothing shows up and when I try to flash anything it says "waiting for any device" yet when the phone is off it signals that it is charging from the laptop.
I have updated my rooted 6P multiple times before using both Flashfire and adb/fastboot from both a PC and a Mac and have never had problems before this. I have run out of ideas to try so any help would be greatly appreciated but I fear I might have bricked my beloved Nexus 6P.
MilkyOolong said:
Please help!!!
Click to expand...
Click to collapse
Weird. You should at least have fastboot when in bootloader mode, and MTP with TWRP. In bootloader mode, plug the device into your PC. The device is not detected at all? Have you tried wiping cache/dalvik? MTP not working in TWRP?
If you can boot into recovery then your device is not bricked. Make sure the adb and fastboot binaries on your computer are completely up to date. I'm pretty sure Google updated them for Oreo. You will need to flash the full stock image with flash-all.bat command when you get your computer to recognize your phone. Updating from Nougat to Oreo using Flashfire or Flashify is a bad idea because you are dealing with something way more extensive than an OTA update.
I was trying to root my phone, i got TWRP recovery for my device (i'm sure it is).
I opened odin and checked the OEM Unlocking in Dev Options , connected my device and everything worked fine. But when i boot into recovery it shows that i still use the stock one.
What's the problem?
In my opinon the bootloader is Locked i'm not sure. also i tried to see if it is locked or not but i couldn't because fastboot devices command didn't work for me although i'm sure i installed ADB and Fastboot And my devices drivers correctly.
Note: adb devices works for me only the fastboot.
Please guys i need your help!
Hi
I would like to ask for some advice.
I've recently soft bricked my MI2S. I can boot to recovery (TWRP 2.8.1) and fastboot. The phone isn't recognised by Windows or Ubuntu, so I can't flash anything with fastboot. Actually, fastboot, adb or MiFlash don't detect the phone. I've tried to use a USB stick with an OTG cable, but TWRP doesn't detect the USB stick. If I boot to system, it stays on the MI logo (I can wait a full night, it won't change).
My question is, do I have a problem with my USB port? I'm equipped to solder a new one, if necessary. Or is my connection problem due to another reason? I wouldn't want to go through soldering if it is for nothing. Especially, when I started to mess up with the phone, it was locked with a different MI account (it was my wife's account, but it took me a few days to connect the dots together), and I couldn't connect with MiFlash, adb or fastboot either.
The steps I did to get it soft bricked:
Flashed TWRP 2.8.1 with fastboot
Rebooted to recovery
Rebooted to MIUI (a few times)
Attempted to flash TWRP 3.5.0 (my memory fails a bit there, I think I did it via fastboot)
The last didn't work because I'm still on TWRP 2.8.1
And I can't add any more zip file to flash via recovery, nor can I use adb sideload or flash with fastboot.
Any advice or comments are more than welcome. You may just have an idea that I didn't think of.
Regards
Matt
Quick update:
I don't know if you would agree, but I can't see my issue to be a software one (the device not being recognised)
I've ordered a USB port directly from China and I'll see if I can unbrick the phone from that point.
It's great that you can still access to recovery and fastboot.
First, I advice you to back up your data.
If you cannot use adb sideload or flash with fastboot.
Try in fastboot mode
- fastboot erase cache;
- fastboot erase system;
- fastboot erase userdata.
See if that can solve your issue.