Database Develop

Nexus 6 soft brick help

I flashed android m preview last night. i needed root so i flashed it and that flash failed, which seems to have corrupted the rom. Im hoping i can get my nexus back but im having some issues.
Recovery- i didnt flash twrp, its stock android m recovery
factory reset- all this does is erase and my rom still is corrupted
fastboot- computer reads it, i can see it in device manager as "android bootloader interface, however adb wont read. no devices in adb devices
ive uninstalled and reinstalled the google drivers several times to no avail. ive tried it on a different pc and same no dice.
ideas?

adb commands will not work in fastboot mode.
read this. it shall set you free
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
ingnore relock bootloader part!!

1. Boot into bootloader 2. fastboot flash system [system.img from preview 3 rom] 3. Wipe caches 4. Reboot

I admit i was trying to use adb to see if the phone was connected... bad habit i guess. The connect to adb in recovery option was not working at all. I blame this all on the MM bootloader. I have a bad taste in my mouth. In the end wugs saved me. I guess that day i needed the process simplified. Sorry for late response.
Anyway, phones fixed, this matter is complete. Both you folks are amazing. Im sending virtual hugs to all.

No PC connection with adb/sync, fastboot works.

Hi guys,
I am trying to help out a mate and unfortunately dont have much experience with HTC's.
This is where i stand...phone wont be recognized in normal boot, nor in TWRP, so adb is not working at all. FASTBOOT works.
i have been circling around with locking and unlocking the bootloader to try out all the methods of updating the system, RUU fails with error 155. when unlocking, supercid fails with some java error.
To get S-OFF, i definitely need adb to load the "much talked for" file, but that is impossible right now.
RUU normal way fails as i said above, so does FUU with rom.zip (found away to get it out of exe, so it is untouched) as soon as it "updates signatures" it'll fail, I even use the fastboot command with the renamed file firmware.zip ends up saying it cannot verify partition ...adding zip after flash command says file is out of size
I am on 4.20.651.10, and trying to get the latest package, and am out of ideas. I found out the hard way that if i lock back the phone, it wont boot to TWRP and nor on a modified system.
I am really not sure what to do, having adb on would've spared me a lot of trouble. Friend says the USB port has been changed twice, it is so odd to have fastboot and not even a single refresh in Device Manager when i plug the damn phone on...

There are more replies to question threads outside the Help section then in here...
Anyway, i lost fastboot too, and no idea why. tried in two pc's, one of them with 3 different os's, tried two macs, tried even an OTG cable with my other android phone, nothing.
I cant even relock the phone so i can update through the RUU ZIP in the sdcard, but that's a scratched off solution if no USB connection is delivered.
I even tried the S-Off unlocking file on /data/local/tmp, but it doesnt seem to execute from TWRP terminal, and ofc it wont through a booted system either...
I managed to install a custom rom since i have no OS, and tried the "AndroidHtcSync.apk" solution to no avail
i seriously hope anyone has the will to help me...
EDIT: port is definitely fine, as the phone charges from the charger, and fastboot shows "fastboot ac".
EDIT2: fastboot is back... renamed the zip in sdcard, now it fails flashing there too with "Device halted due to large image update fail"

Le 2 (SD one) doesn't feel like letting me do anything in fastboot

Title
Before that I couldn't even get it to enter fastboot(it just stood on the boot screen before the emui logo) before I manually updated the stock emUI, now that I managed to actually get to fastboot the connection basically vanishes as soon as I do adb reboot bootloader.
Have tried with both adb-setup-1.3.exe and adb-setup-1.4.3.exe, same problem on both, Windows 10.
It doesn't even detect adb, much less fastboot in Windows 8.
So.. yeah, stuck with the stock ROM until I can figure out what the hell is Windows doing with the drivers.
Any ideas?

dnad said:
Title
Before that I couldn't even get it to enter fastboot(it just stood on the boot screen before the emui logo) before I manually updated the stock emUI, now that I managed to actually get to fastboot the connection basically vanishes as soon as I do adb reboot bootloader.
Have tried with both adb-setup-1.3.exe and adb-setup-1.4.3.exe, same problem on both, Windows 10.
It doesn't even detect adb, much less fastboot in Windows 8.
So.. yeah, stuck with the stock ROM until I can figure out what the hell is Windows doing with the drivers.
Any ideas?
Click to expand...
Click to collapse
Well, after almost killing myself I just realized that Windows is once again being a gigantic ***, with the driver signing and outdated/too new ADB drivers, after fumbling a bit I managed to enable it, finally.
Mod can close this.

Can't Re-lock bootloader

I've been an android developers for years and years now and even have made my own ROMs, but this phone....this phone is testing me. I unlocked it months ago to install an original Android 11 ROM, but it was awful and lacked support for even the most basic functionality, so I flashed the stock image back. That alone was a nightmare and I don't remember how I managed it. That being said, the Asus Android 11 update is rolling out OTA and can be downloaded directly from their site. I downloaded it and put it in the root directory, where it is found on start-up, but when I tell it to install, it fails after a few seconds and doesn't give me any explanation for it. I thought it may be that the bootloader is unlocked, so I've been trying to re-lock it for weeks with no success. I managed to get the damn fastbootd mode recognised by my computer and it sees the phone, but when I give it any relock command I receive this error:
"FAILED (remote: Command not supported in default implementation)"​I have no clue what to make of that or what it even means. My only guess is that the commands I'm using aren't supported in the latest version of the tools. I've tried the following commands:
fastrboot oem asus-lock​
fastboot oem lock​
fastboot oem asus_csk_lk​
fastboot flashing lock​
fastboot oem relock (I don't think that's a real command, but I was irritated and figured it was worth a shot)​
I'm at a total loss. All I want is to get Android 11 to the damn thing and the OTA isn't coming through to my phone. The phone itself is an international model I bought from China back before it was released in the US. IDK if that's causing a problem, but at this point I'm out of ideas. I'd also note that normal fastboot, found by going to the bootloader instead of "adb reboot fastboot" doesn't even allow the computer to recognise the phone and when I try to install the fastboot driver via device manager, it outright refuses to install it. There's no apparent way to get it to install the driver anyway. I AM able to get it to install the driver and see the phone while in fastbootd mode.
Anyone got any ideas?

fastrboot oem asus-lock
This worked for me on tencent phone converted to ww firmware. I had no troubles with updating to 11 from 10 as well. I had also no troubles to flash raw firmware with bootloader unlocked.
Waiting now for new ww firmware as CN has been already released couple days ago.. If they didn't fix thing I'm annoyed with I going back to 10!
Try different cable. Had guy from reddit with same problem like yours and simple new cable sorted everything

fastboot oem asus_csk_lk should do it.
I think you may be in the wrong fastboot mode You need to be in the bootloader. Try powering off and boot with Vol UP + Power until you land on the bootloader page (don't navigate to Fastboot from the bootloader menu, just stay on the bootloader menu. Doing 'fastboot reboot bootloader' should also do the trick but suggest trying with the physical buttons.

Question [Fixed] ASUS logo stucks on recovery, only access to bootloader

Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.

Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.

To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.

From the bootloader you should be able to flash the raw image again, it should flash everything

Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.

semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason

Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).

semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.

Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.

Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?

I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.