Question Zenfone 8 bricked.

Question Zenfone 8 bricked. - ASUS ZenFone 8

I bricked a brand new Zenfone 8. I wanted install LineageOS, but something went wrong. Now the phone was like this:
Code:
[[email protected] tmp [j0]#>>> fastboot devices
MCAIGF004584Z9E fastboot
Code:
[[email protected] tmp [j0]#>>> adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
[[email protected] tmp [j0]#>>>

FastBoot fllsh stock A12

pjk11 said:
I bricked a brand new Zenfone 8. I wanted install LineageOS, but something went wrong. Now the phone was like this:
Code:
[[email protected] tmp [j0]#>>> fastboot devices
MCAIGF004584Z9E fastboot
Code:
[[email protected] tmp [j0]#>>> adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
[[email protected] tmp [j0]#>>>
Click to expand...
Click to collapse
Which OS version was installed before? Which LineageOS version did you install (which image file)?
I assume you installed LineageOS according to the installation instruction from the LineageOS Website (vendor, boot)?
In principle you can repeat the installation again using the same instructions and see if it works this time. If not reinstall the raw image for the Android OS - see:
https://www.asus.com/Content/Android-13-Beta/
(search for How to opt-out and revert back to Android 12 at the bottom of the page)
After reinstalling the raw image from ASUS you can reinstall the LineageOS 19 again.
regards
Bernd

Related

CID-T-MOB101 to SuperCID

I have tryed almost everything but I just can't supercid my damn phone. I already have S-OFF and i'm on HBOOT 1.44
This is the problem:
Code:
C:\ADB>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\ADB>fastboot oem readcid
< waiting for device >
I does not show the device when in the bootloader. But when Android it booted is shows
Code:
C:\ADB>adb devices
List of devices attached
HT35FW914921 device
C:\ADB>
Is it a driver issue? I'm running Windows 8.1 64-bit

SOLVED!
Damn Microsoft. Here is the fix http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337

ADB Connection Troubleshooting

Hi Guys,
Been having a bit of trouble connecting phone via ADB. I can get the connection to work, but it takes a bit of TLC and sometimes a sledgehammer.
Thought we could compile a list of ADB troubleshooting techniques?
If you have any further suggestions, please share.
c:\Fastboot>adb reboot recovery
* daemon not running. starting it now *
* daemon started successfully *
error: device offline
Click to expand...
Click to collapse
Resolution: Reboot device
c:\Fastboot>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Resolution: Reboot device
c:\Fastboot>adb reboot recovery
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Click to expand...
Click to collapse
Resolution: Kill all adb.exe processes from task manager and rerun the command. May need to do this a few times.
Edit: I should mention that I'm using adb.exe on Windows 8.1

[Q] adb shell - device not found

Hello,
I have following problem. maybe someone has a solution.
Using CM12 -Temasek Builds on D405n.
When i start adb shell always get following error:
Code:
C:\ADB>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[COLOR="Red"]error: device not found[/COLOR]
On stock image 5.0.2 this working fine.

Is there a way too root the Amazon Fire 5.1.1?

I tried this one. But it says it only works for 5.0.1 (extreme noob)

http://forum.xda-developers.com/amazon-fire/general/psa-information-regarding-firmware-t3264224

Or in short, not yet

Yes you can.
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695

pappasmurfsharem said:
Yes you can.
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
Click to expand...
Click to collapse
I just tried the supertool method on 5.1.1 and it doesn't appear to work. Drivers work fine, batch file boots to fastboot, but when the device restarts, the normal lock screen appears, and the batch file is unable to find the device. I opened another shell window and ADB DEVICES lists the device.
Anyone had any luck on 5.1.1?
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
--------------------------------------------------------------------------------
[*] Big thanks to k4y0z from XDA
[*] Make sure USB Debugging is enabled on your tablet
[*] this tool will boot you into fastboot and root your device.
[*] device will reboot a couple times during this process.
--------------------------------------------------------------------------------
press a key to reboot the device in fastboot mode
< waiting for device >
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.007s]
finished. total time: 0.008s
resuming boot...
OKAY [ 0.003s]
finished. total time: 0.004s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
error:
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
4703 KB/s (5904943 bytes in 1.226s)
adb server is out of date. killing...
* daemon started successfully *
error: device offline
adb server is out of date. killing...
* daemon started successfully *
error: device offline
adb server is out of date. killing...
* daemon started successfully *
error: device offline
< waiting for device >

mistermick said:
I just tried the supertool method on 5.1.1 and it doesn't appear to work. Drivers work fine, batch file boots to fastboot, but when the device restarts, the normal lock screen appears, and the batch file is unable to find the device. I opened another shell window and ADB DEVICES lists the device.
Anyone had any luck on 5.1.1?
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
--------------------------------------------------------------------------------
[*] Big thanks to k4y0z from XDA
[*] Make sure USB Debugging is enabled on your tablet
[*] this tool will boot you into fastboot and root your device.
[*] device will reboot a couple times during this process.
--------------------------------------------------------------------------------
press a key to reboot the device in fastboot mode
< waiting for device >
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.007s]
finished. total time: 0.008s
resuming boot...
OKAY [ 0.003s]
finished. total time: 0.004s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
error:
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
4703 KB/s (5904943 bytes in 1.226s)
adb server is out of date. killing...
* daemon started successfully *
error: device offline
adb server is out of date. killing...
* daemon started successfully *
error: device offline
adb server is out of date. killing...
* daemon started successfully *
error: device offline
< waiting for device >
Click to expand...
Click to collapse
I got root and xposed working on 5.1.1
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362/page5

Same problem here. no luck with 5.1.1. Supertool doesn't work.

ongogo said:
Same problem here. no luck with 5.1.1. Supertool doesn't work.
Click to expand...
Click to collapse
Works perfectly fine.
post in that thread if you need support.

mistermick said:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
error:
Click to expand...
Click to collapse
This indicates you've got some out of date adb drivers installed. Make sure nothing else that uses adb is running (emulator, sync software?) Try taskkill adb in task manager. If that doesn't work you'll need to track down the old drivers and uninstall.

DoLooper said:
This indicates you've got some out of date adb drivers installed. Make sure nothing else that uses adb is running (emulator, sync software?) Try taskkill adb in task manager. If that doesn't work you'll need to track down the old drivers and uninstall.
Click to expand...
Click to collapse
I like how the thing that it said to me 8 or 9 times was the one thing I didn't pay attention to. I'm pretty sure I already had adb installed from when I rooted my TF101. That's probably the issue. I'll give it a shot when I get home.
*Edit: I uninstalled all of the HTC crap I had, whatever old version of minimal adb and fastboot was running, and reinstalled the platform-tools from the sdk, and the supertool finally was able to complete successfully. Now I have a $35 android tablet that is actually usable!

SuperSU breaks ADB

Hey.
I'm trying to root my brand new BQ Aquaris U to use it as my new development platform, since the Samsung Galaxy Nexus (i9250), which has served as my development device for the last five years, is rapidly breaking down on the hardware side.
The Aquaris runs on the latest firmware, Android 6.0.1, Kernel 3.18.24, Build 1.5.0_20170217-1219.
My host computer is running on Fedora 25 with the lastest Android SDK.
As long as the device is stock, I can connect to it via ADB, but of course, I cannot obtain root.
Code:
$ ./adb start-server
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
$ ./adb shell
[email protected]:/ $ exit
$
I then boot the device into Fastboot mode and install TWRP.
Code:
$ ./adb reboot bootloader
$ ./fastboot flash recovery ../../BQ/twrp-3.1.0-0-chaozu.img
target reported max download size of 535822336 bytes
sending 'recovery' (16676 KB)...
OKAY [ 0.528s]
writing 'recovery'...
OKAY [ 0.416s]
finished. total time: 0.944s
$ ./fastboot reboot
rebooting...
finished. total time: 0.203s
$ ./adb reboot recovery
$
Then I back up the "boot" and "system" partitions and transfer the backup over to my computer via MTP.
I then transfer "SuperSU-v2.79-201612041815.zip" to my phone and install it via TWRP.
After I boot into Android again, ADB is no longer working.
Code:
$ ./adb shell
error: no devices/emulators found
$
There seems to be nothing I can do to get ADB access when the device is rooted. The device will show that "USB debugging is connected", but will not be recognized by ADB. Resetting debugging permissions on the device does not help. Neither does changing the USB connection mode (e. g. from "File transfer (MTP)" to "Charging only") on the device or adding the device's USB ID (2a47:901b) to "~/.android/adb_usb.ini". When the device is returned to stock via an OTA update, ADB will start working again. Restoring the backup via TWRP will probably make it functional as well. However, of course both will un-root the device.
Is there any way to get ADB working on this device while it's rooted? Since it's pretty obvious that SuperSU breaks ADB on this device, can I somehow contact the developers of SuperSU to help them track the issue down? Or is there a known workaround?
Any help is appreciated.

Database Develop

welcome