CID-T-MOB101 to SuperCID - One (M7) Q&A, Help & Troubleshooting

CID-T-MOB101 to SuperCID - One (M7) Q&A, Help & Troubleshooting

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

Related

Can't install black rose

I have a rooted and unlocked bootloader on my N1 running CM7.2, I'm trying to install black rose, but every time I time I try and do so, I keep getting the error "adb server is out of date... killing". Also another message that it can't connect to the device. I've read that some people are suggesting I get the adb fix for users with HTC Sync, but I have NEVER installed HTC Sync. I'm not sure how to get around this. I've update my SDK so I'm not sure what to do.

pm2gonzales said:
I have a rooted and unlocked bootloader on my N1 running CM7.2, I'm trying to install black rose, but every time I time I try and do so, I keep getting the error "adb server is out of date... killing". Also another message that it can't connect to the device. I've read that some people are suggesting I get the adb fix for users with HTC Sync, but I have NEVER installed HTC Sync. I'm not sure how to get around this. I've update my SDK so I'm not sure what to do.
Click to expand...
Click to collapse
Apparently that error is most commonly seen when there is another version of ADB on that machine. Are you running HTC Sync?
EDIT -- Sorry, i re-read your OP and you've already stated you aren't running HTC Sync. In any case that error still suggests another version of ADB is around somewhere.

pm2gonzales said:
I have a rooted and unlocked bootloader on my N1 running CM7.2, I'm trying to install black rose, but every time I time I try and do so, I keep getting the error "adb server is out of date... killing". Also another message that it can't connect to the device. I've read that some people are suggesting I get the adb fix for users with HTC Sync, but I have NEVER installed HTC Sync. I'm not sure how to get around this. I've update my SDK so I'm not sure what to do.
Click to expand...
Click to collapse
Hmm... Even though you don't have HTC Sync, there must be another instance of adb running around in your system.
Are you using tools for other android phones on your system? If they are installed, then they could be running a version of adb which could cause your problem. So if that's the case, find those processes and kill those.
Check your SYSTEM PATH (Environment variable) to see if there is another path to your adb.exe ( Just use one )

I probably should have mentioned, but I am running Windows 7 64-bit. Also, I've tried uninstalling and reinstalling the android SDK and I got the same result. To visualize, there is a screenshot of the error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have USB Debugging enabled, the phone says FASTBOOT USB. So the phone recognizes the connection at least.

Are you able to run adb commands? Again, are there SDKs for other android phones in your PC?
If you want, try putting adb and fast boot in a fresh directory, add that you path as an env variable, remove the other adb env variable paths(if any), and try again.
Reboot system too just to be sure
Sent from my Nexus One using xda app-developers app

pm2gonzales said:
I probably should have mentioned, but I am running Windows 7 64-bit. Also, I've tried uninstalling and reinstalling the android SDK and I got the same result. To visualize, there is a screenshot of the error:
I have USB Debugging enabled, the phone says FASTBOOT USB. So the phone recognizes the connection at least.
Click to expand...
Click to collapse
You're doing it wrong. You need to be booted into android, not fastboot.

race55 said:
You're doing it wrong. You need to be booted into android, not fastboot.
Click to expand...
Click to collapse
I'm still getting issues. I'm booted in to the system, USB debugging is enabled. I can use adb commands, like if I do adb devices, it shows my device connected. But throughout the installation, it keeps showing errors:
Code:
-------------------------------
| Nexus One BlackRose 120421 |
| Made by Lecahel(XDA-dla5244) |
| Dok-Do belongs to KOREA |
-------------------------------
Do at your own risk
Don't flash any unsigned radio image
Don't flash eclair rom(eg.EPF30), if you are SLCD Nexus One user
If you are using sense rom, please install HTC Sync and turn off that now
Your N1(USB Debugging ON) should be connected to PC
If your device has already installed latest BlackRose, it will enter into Blac
ose menu
Otherwise, BlackRose will be installed or updated automatically
* Waiting for device...
adb server is out of date. killing...
* daemon started successfully *
* Getting device information...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
remote object '/data/local/tmp/ro.build.version.release_tmp' does not exist
adb server is out of date. killing...
* daemon started successfully *
1 KB/s (10 bytes in 0.007s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
* Installing BlackRose
adb server is out of date. killing...
* daemon started successfully *
1461 KB/s (4194304 bytes in 2.802s)
adb server is out of date. killing...
* daemon started successfully *
638 KB/s (26172 bytes in 0.040s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error opening /data/local/tmp/go.lol: No such file or directory
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
< waiting for device >
At which point it boots in to recovery (4EXT).

pm2gonzales said:
I'm still getting issues. I'm booted in to the system, USB debugging is enabled. I can use adb commands, like if I do adb devices, it shows my device connected. But throughout the installation, it keeps showing errors:
Code:
-------------------------------
| Nexus One BlackRose 120421 |
| Made by Lecahel(XDA-dla5244) |
| Dok-Do belongs to KOREA |
-------------------------------
Do at your own risk
Don't flash any unsigned radio image
Don't flash eclair rom(eg.EPF30), if you are SLCD Nexus One user
If you are using sense rom, please install HTC Sync and turn off that now
Your N1(USB Debugging ON) should be connected to PC
If your device has already installed latest BlackRose, it will enter into Blac
ose menu
Otherwise, BlackRose will be installed or updated automatically
* Waiting for device...
adb server is out of date. killing...
* daemon started successfully *
* Getting device information...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
remote object '/data/local/tmp/ro.build.version.release_tmp' does not exist
adb server is out of date. killing...
* daemon started successfully *
1 KB/s (10 bytes in 0.007s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
* Installing BlackRose
adb server is out of date. killing...
* daemon started successfully *
1461 KB/s (4194304 bytes in 2.802s)
adb server is out of date. killing...
* daemon started successfully *
638 KB/s (26172 bytes in 0.040s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error opening /data/local/tmp/go.lol: No such file or directory
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
< waiting for device >
At which point it boots in to recovery (4EXT).
Click to expand...
Click to collapse
open terminal, in which you run a random adb command. keep that window open and now try running the installer
Verstuurd van mijn GT-I9000 met Tapatalk

race55 said:
open terminal, in which you run a random adb command. keep that window open and now try running the installer
Verstuurd van mijn GT-I9000 met Tapatalk
Click to expand...
Click to collapse
Same result :/. I don't understand what the problem could be, I can push apps and run adb commands just fine.

pm2gonzales said:
Same result :/. I don't understand what the problem could be, I can push apps and run adb commands just fine.
Click to expand...
Click to collapse
Blackrose installer is terrible. Try using the manual method, worked for me back in the day
Verstuurd van mijn GT-I9000 met Tapatalk

race55 said:
Blackrose installer is terrible. Try using the manual method, worked for me back in the day
Verstuurd van mijn GT-I9000 met Tapatalk
Click to expand...
Click to collapse
With the manual method, I get this:
Code:
C:\blackrosemanual>fastboot flash hboot hboot_blackrose.nb0
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.229s
C:\blackrosemanual>
To confirm, I am in Fastboot mode as per README instructions.

pm2gonzales said:
With the manual method, I get this:
Code:
C:\blackrosemanual>fastboot flash hboot hboot_blackrose.nb0
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.229s
C:\blackrosemanual>
To confirm, I am in Fastboot mode as per README instructions.
Click to expand...
Click to collapse
Did you fastboot boot the .lol file?
Verstuurd van mijn GT-I9000 met Tapatalk

race55 said:
Did you fastboot boot the .lol file?
Verstuurd van mijn GT-I9000 met Tapatalk
Click to expand...
Click to collapse
Yes, received the EXACT SAME error message.

Okay, I finally got it to work. I just kept trying and trying repeatedly until it actually worked. I think it had something to do with my android sdk or maybe the adb drivers because adb commands only work like 50% of the time. The 50% that it doesn't work, I keep getting those "adb server out of date" errors. But I finally got it at least.

try running Blackrose with other ROM, or you should install HTC Sync for your PC, i can't run Blackrose with CM7.2 too

[Q] adb devices = error: device not found

When i make in cmd adb devices . List of devices attached but no device.
I give adb reboot bootloader and comes: Error: device not found
What is wrong?
I can not booting. i make this in the fastboot mode

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

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!

Question Zenfone 8 bricked.

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

Database Develop

welcome