Develop Bugs

[Q] Need Assistance, I brick my Galaxy Nexus

Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!

So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?

cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!

Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.

RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks

I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.

To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!

To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)

The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.

To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )

you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)

Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.

silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed

cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!

To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!

What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.

To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?

To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?

What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App

[Q] Trouble with flashing new recovery

Hey everyone,
Alright so I have been trying to root my phone for the past 4 hours. I have unlocked it and flashed a custom recovery using adb. Or at least I thought I did. I tried flashing the clockworks recovery and when I would reboot it into the recovery, I would get an icon of a phone and an exclimation point. I assumed a bricked the phone and freaked out. A minute later the phone rebooted out of recovery and works fine afterwards. So I assume that the problem is the recovery. Something went wrong and I am not sure what.
Here are the steps I followed:
I was fine up until step four when I was trying to flash superuser.
No idea what to do from here.
HTC Unlocked = Bootloader is unlocked?
Not to take away from the OP, but i created a guide for a guy here at work and thought others might benefit from it.
Unlock Bootloader and Root
Unlocking your bootloader will wipe all data from your phone. Meaning you will loose everything make a backup.
Step 1: ADB Installation Instructions. NOTE:You must have ADB installed on your PC even if you use method 2b to unlock the bootloader. You will need adb to install recovery in Step 4.
1. Go to http://developer.android.com/sdk/index.html and download the sdk.
2. Follow installation instructions found here. Note: This is not a forum for this device DO NOT do anything but the adb installation on your system.
Step 2a: Download software from HTC to allow your bootloader to be unlocked.
1. Go to http://www.htcdev.com/
2. Login to the website. NOTE: Register for an account if you haven’t already. You must provide a valid email address.
3. Select “All Other Supported Models” from the drop down list and click “Begin Unlock Bootloader”
4. Follow online instructions.
1. SuperUser http://androidfiles.org/securekey.ph.../superuser.zip - Copy this file you phone. Special thanks to jmztaylor his link.
2. Recovery of your choice TWRP Recovery http://forum.xda-developers.com/show....php?t=2161702 or CWM Recovery http://forum.xda-developers.com/show....php?t=2161706. Put this file in the ADB Tools folder. NOTE: You must type the name of this file perfectly when using adb to flash it in step 4.
Step 4: Using ADB to install recovery
1. Open command prompt ( shift + right click, then choose “Open command window here”) and type “ADB devices” you should see you phone listed, if you do not start over at Step 1. NOTE: Phone must be plugged in and USB Debugging must be checked in settings.
2. Type “ADB flash recovery recovery.img” without the quotes. NOTE: the red is actually the title of the recovery file that you copied in step 3. If it’s different substitute your files name instead.
3. Once complete type “ABD reboot recovery”.
4. You should at this point backup your device
5. Once you create a backup, Choose install and navigate to the SuperUser file you put on your phone in Step 3.
6. If all goes well you are now rooted. Select reboot system to restart phone.
There is some very good information here but its spread out pretty thin. Guides IMHO are very usefull to fill the gap between devs/powerusers and the newbs.Most people that come here have a hard time with the things we take for granted such as adb commands, or adb its self (most will be setting it up for the first time). I tried my best to put it in a knowledge base that everyone can understand if for some reason you do not understand what i was trying to say please ask. I don't own this phone, just helped a friend root his, but if you need to get ahold of me pm me. I'll get back to you as soon as possible.
Any help? Just trying to get rid of the bloatware -_-

Did you copy superuser to your phone? And are you sure you are using the correct file location for adb in the command prompt? You must make sure you are and that all files you want to flash are also in the same folder as adb. Please respond if you have superuser on your phone and if you are positive you are using the correct adb folder location for the command prompt. I'm not the best at this however, I read up a lot on it just to root my phone. Took me 4 hours about as well, but that was before the recoverys came out. I suggest trying to flash twrp recovery, it's a bit buggy (for me) but I find it easier to use.
Sent from my HTC One VX using xda app-developers app

Code:
ADB flash recovery recovery.img
that is your problem to start with its not "ADB flash"
boot your phone into bootloader with usb connected to PC, Phone should read "fastboot"
Go the your adb directory in command prompt.
ex.
Code:
C:\PcUser\Master\Androidsdk\adb\
Make sure all drivers are installed, from CMD prompt window type "fastboot devices" to check your phone is showing.
if you see your device then you can type
fastboot flash recovery [drag your recovery image into cmd window] and hit enter and it should flash
once recovery is flashed you can either "fastboot Reboot" or on the phone use the Vol rockers to navigate to menu and hit bootloader then from there choose recovery

Hi,
I have the same issue about 2 days, I install TWRP Recovery and all it's ok, and flash in fastboot mode with adb like ilostchild tolds You.

It seems that I met the same problem.
My issue is the phone only boot into CMW mode, although I tried to restart it many times. When connect to usb cable, lappy did not recognize the phone so I can use adb command.
Please help me.

I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.

zeratos said:
I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.
Click to expand...
Click to collapse
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img

spooky_ghosty said:
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img
Click to expand...
Click to collapse
I already tried all those things you mentioned, I have been looking for 3 days for a solution for this problem on google without any luck, the device doesn't recognize any command either and I already set up a virtual machine and tried on that machine as well. u_u

Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.

Johann12911 said:
Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.
Click to expand...
Click to collapse
Already tried uninstalling HTC Sync, after that I deleted every trace of it. USB Debugging WAS ON before the phone crashed but I can't activate it now because the phone keeps looping between reboots.

Try to flash it via htc sync. Download the update and rewrite everything!
Sent from my HTC One VX using xda app-developers app

HELP! LGOG F180S, No OS installed T_T

Hi everyone!
I was trying to install Cyanogenmod on my LGOG F180S, Im new to everything T_T
I already installed TWRP/freegee... but I forgot to insert the custom rom ZIP on the internal storage... And then the back ups I made was took out, and there is no backup currenty on the internal storage. And also the system folder was erased, the main reason why there is no OS....
How do I access the internal storage so I can put in the ZIP for custom rom? I can still boot to recovery for TWRP by pressing vol up+down.
PLEASE HELP! Thanks for all the reply. I just need a tool to access the internal storage to put the custom ROM zip file into the internal storage.

lancelotconquista said:
Hi everyone!
I was trying to install Cyanogenmod on my LGOG F180S, Im new to everything T_T
I already installed TWRP/freegee... but I forgot to insert the custom rom ZIP on the internal storage... And then the back ups I made was took out, and there is no backup currenty on the internal storage. And also the system folder was erased, the main reason why there is no OS....
How do I access the internal storage so I can put in the ZIP for custom rom? I can still boot to recovery for TWRP by pressing vol up+down.
PLEASE HELP! Thanks for all the reply. I just need a tool to access the internal storage to put the custom ROM zip file into the internal storage.
Click to expand...
Click to collapse
I'm also new to android but i believe the only option you have now is to restore to stock and then re-root and put zip in storage.
see if you can go into download mode
----> turn off your phone, press both "Volume Up and Volume Down" button simultaneously
then plug in the usb cable into your phone n computer.
Sent from my LG-F180K using Tapatalk

lancelotconquista said:
How do I access the internal storage so I can put in the ZIP for custom rom? I can still boot to recovery for TWRP by pressing vol up+down.
Click to expand...
Click to collapse
If you are able to ge to TWRP recovery, then the easiest thing for you is to use ADB. Two options: adb push, and adb sideload. Learn about it - there is a lot of info here on XDA on how to set up and use it. This is not specific to a particular phone; it's a very handy tool you can use with any Android device.
Another option would be to flash a stock KDZ, and start the whole process all over again.

kt-Froggy said:
If you are able to ge to TWRP recovery, then the easiest thing for you is to use ADB. Two options: adb push, and adb sideload. Learn about it - there is a lot of info here on XDA on how to set up and use it. This is not specific to a particular phone; it's a very handy tool you can use with any Android device.
Another option would be to flash a stock KDZ, and start the whole process all over again.
Click to expand...
Click to collapse
Thanks very much I'll try the sideload method first, but if worst comes to worst ill try to flash it.
This will be a veeeery steep learning curve for me :v

kt-Froggy said:
If you are able to ge to TWRP recovery, then the easiest thing for you is to use ADB. Two options: adb push, and adb sideload. Learn about it - there is a lot of info here on XDA on how to set up and use it. This is not specific to a particular phone; it's a very handy tool you can use with any Android device.
Another option would be to flash a stock KDZ, and start the whole process all over again.
Click to expand...
Click to collapse
tried to use adb sideload / push:
http://forum.xda-developers.com/showthread.php?t=2317986 <-for HTC One, but the idea is the same
to be sure I also followed this: http://forum.xda-developers.com/showthread.php?t=2272266
When I try to connect ADB sideload on cmd, and type 'adb device', its saying 'List of Devices Attached' but its not displaying my device
I have all the latest drivers for my F180S, including LG United Mobile Drivers... etc etc.
But when I check my device manager, it says 'LG-180S' (no F, weirdly) so its being detected
When I saw that its not working, I tried to re-flash it with official ROM, I followed instructions here:
http://forum.xda-developers.com/showpost.php?p=44874388&postcount=36
it says to 'press vol up+down then connect to computer'
when I try to do it, nothing happens, first its showing that its charging, then it flashes 'LG logo' for 0.5 sec, then its showing a fully charged battery, then a blank screen (the screen is lit up, but theres nothng, just black)
HELP T_T

lancelotconquista said:
tried to use adb sideload / push:
http://forum.xda-developers.com/showthread.php?t=2317986 <-for HTC One, but the idea is the same
to be sure I also followed this: http://forum.xda-developers.com/showthread.php?t=2272266
When I try to connect ADB sideload on cmd, and type 'adb device', its saying 'List of Devices Attached' but its not displaying my device
I have all the latest drivers for my F180S, including LG United Mobile Drivers... etc etc.
But when I check my device manager, it says 'LG-180S' (no F, weirdly) so its being detected
When I saw that its not working, I tried to re-flash it with official ROM, I followed instructions here:
http://forum.xda-developers.com/showpost.php?p=44874388&postcount=36
it says to 'press vol up+down then connect to computer'
when I try to do it, nothing happens, first its showing that its charging, then it flashes 'LG logo' for 0.5 sec, then its showing a fully charged battery, then a blank screen (the screen is lit up, but theres nothng, just black)
HELP T_T
Click to expand...
Click to collapse
Reboot to TWRP and connect your device to your PC.
Open device manager.
Right click at the unknown device (LG-180S), choose "update driver software"
Choose "Browse my computer for..."
Click "Let me pick from a list..."
Choose "ADB Interface", click next
Choose "Android Sooner Single ADB Interface"
continue until the driver installation complete.
Now you can use adb push, or sideload to fix your phone.
When you check using adb devices, it will list your device as recovery

kt-Froggy said:
If you are able to ge to TWRP recovery, then the easiest thing for you is to use ADB. Two options: adb push, and adb sideload. Learn about it - there is a lot of info here on XDA on how to set up and use it. This is not specific to a particular phone; it's a very handy tool you can use with any Android device.
Another option would be to flash a stock KDZ, and start the whole process all over again.
Click to expand...
Click to collapse
arasyi said:
Reboot to TWRP and connect your device to your PC.
Open device manager.
Right click at the unknown device (LG-180S), choose "update driver software"
Choose "Browse my computer for..."
Click "Let me pick from a list..."
Choose "ADB Interface", click next
Choose "Android Sooner Single ADB Interface"
continue until the driver installation complete.
Now you can use adb push, or sideload to fix your phone.
When you check using adb devices, it will list your device as recovery
Click to expand...
Click to collapse
Thanks! Now another question...
Ive pushed the TWRP backups back (The TWRP folder, which includes a file named ".twrps" and then a folder named backups. But when i click restore on TWRP recovery, theres nothing displayed on restore :/ How can I restore it at least?
EDIT: nevermind, I put a name on the .twrps file (changed it to test.twrps) and it worked
Thanks anyway for the device manager trick! I would have not done it witout your help T_T Thanks thanks!

Help I cannot install CWM anymore

Hi there,
First I have installed CWM with the method I had to use the codes "adb reboot bootloader"... and so on and It worked perfectly.
I wanted to install the Envi ROM and on the tutorial there was said I first should install the Base ROM and then after restarting I should install the Envi ROM. After installing the Base ROM my CWM was gone. Now I can't install it anymore. I tried the following install methods:
-The one I've mentioned already <- Doesnt work because my PC says it does not know the command abd
-The install.bat method <- Does not work because my phone does not get recognized, despite I have all the drivers installed.
-The RecoverX method <- Does not work because my phone does not get recognized, despite I have all the drivers installed.
-The RecoverX app <- The says that installing CWM worked normally, but still I have no CWM
-The install.bat method directly on my phone <- SManager does not run the .bat even I ran it with the proper rights and adjustments

domiankrey said:
Hi there,
First I have installed CWM with the method I had to use the codes "adb reboot bootloader"... and so on and It worked perfectly.
.....
-The one I've mentioned already <- Doesnt work because my PC says it does not know the command abd
...
Click to expand...
Click to collapse
Did You try flashing a kernel with pre installed recovery? You can flash it using fastboot directly or flashtool.
Also, the command is adb, not "abd". Plus if windows doesn't recognize adb command, then the adb.exe is not in the folder from where You are running the command prompt from.

Mirhawk said:
Did You try flashing a kernel with pre installed recovery? You can flash it using fastboot directly or flashtool.
Also, the command is adb, not "abd". Plus if windows doesn't recognize adb command, then the adb.exe is not in the folder from where You are running the command prompt from.
Click to expand...
Click to collapse
How can I flash a Kernel with a pre Installed Recovery
Where do I get the adb.exe?

domiankrey said:
How can I flash a Kernel with a pre Installed Recovery
Where do I get the adb.exe?
Click to expand...
Click to collapse
You can install the DoomKernel, it has pre installed recovery. You can flash it via flashtool fastboot. But do note, You have to be on stock ROM.
adb.exe is usually in the flashing files.

Mirhawk said:
You can install the DoomKernel, it has pre installed recovery. You can flash it via flashtool fastboot. But do note, You have to be on stock ROM.
adb.exe is usually in the flashing files.
Click to expand...
Click to collapse
I have my phone connected in fastboot mode and the fastboot.exe and the kernel are in the same directory.
When I type: fastboot flash boot kernel.elf it only says "waiting for device"...

domiankrey said:
I have my phone connected in fastboot mode and the fastboot.exe and the kernel are in the same directory.
When I type: fastboot flash boot kernel.elf it only says "waiting for device"...
Click to expand...
Click to collapse
To connect Your phone in fastboot, You have to switch off Your phone. Then press & hold volume up and then connect the phone to Your PC.

Mirhawk said:
To connect Your phone in fastboot, You have to switch off Your phone. Then press & hold volume up and then connect the phone to Your PC.
Click to expand...
Click to collapse
I know that and I did that, but still my device cannot be detected.
I started Ubuntu (Live CD) installed adb und fastboot and tried it there... same result?
Is something wrong is my phone?

I don't think the drivers have been installed properly. Install fastboot and flash mode drivers from flashtool, it has drivers in it's folder. Else if even that doesn't work, install "Sony Update Service", and it will install required drivers.
Edit: I'm giving You instructions for Windows, are You using Ubuntu or was that just a trial?

Mirhawk said:
I don't think the drivers have been installed properly. Install fastboot and flash mode drivers from flashtool, it has drivers in it's folder. Else if even that doesn't work, install "Sony Update Service", and it will install required drivers.
Edit: I'm giving You instructions for Windows, are You using Ubuntu or was that just a trial?
Click to expand...
Click to collapse
I am using Windows. I installed from flashtool and I did not work, I am gonna try Sony Update Service now.
I tried Ubuntu because somebody said me that Ubuntu will detect all the drivers automaticly and there would be no detection problem...
Edit: After INSTALLING Update Service, I still get the same Message "Device not found" Should I run my phone through update Service too?
Why did it not work on my phone with smanager?

domiankrey said:
I am using Windows. I installed from flash tool and I did not work, I am gonna try Sony Update Service now.
I tried Ubuntu because somebody said me that Ubuntu will detect all the drivers automatically and there would be no detection problem...
Edit: After INSTALLING Update Service, I still get the same Message "Device not found" Should I run my phone through update Service too?
Why did it not work on my phone with s manager?
Click to expand...
Click to collapse
I suppose your phone is Xperia S.
If you have unlocked the boot loader , then Sony Official Softwares wont work. If your boot loader is still locked and this error is occurring then its mistake from your side.
I guess by Base ROM you meant official ROM. So if you were on official ROM, did you check for Root Privileges, Busy Box is installed etc ??
Im using Xperia Ion so the steps might be different but results all are same.
Try different methods, it will work.

Captain Droid said:
I suppose your phone is Xperia S.
If you have unlocked the boot loader , then Sony Official Softwares wont work. If your boot loader is still locked and this error is occurring then its mistake from your side.
I guess by Base ROM you meant official ROM. So if you were on official ROM, did you check for Root Privileges, Busy Box is installed etc ??
Im using Xperia Ion so the steps might be different but results all are same.
Try different methods, it will work.
Click to expand...
Click to collapse
By Base Rom I mean the following; I wanted to use the Envi Rom and for this Rom a Base Rom should be installed first.
I have unlocked Bootloader. Busybox is installed and Root Priviliges are given. Before installing the Base ROM I used the APP "Smanager" and I ran the install.sh with the app and then the CWM was there. But now that doesnt work anymore and DeliverX does also not work.
And all methods which require connection to PC won't work because those methods say my device is not detected or connected. I installed CWM on my phone and on other phones several times and never I had thode problems...

domiankrey said:
... After INSTALLING Update Service, I still get the same Message "Device not found" Should I run my phone through update Service too?...
Click to expand...
Click to collapse
Do one thing, check Your Device Manager. Disconnect Your phone, Open Device Manager, then connect Your phone again. See if the Device Manager gets refreshed. If it does, Your device is being connected to the PC. Then check for Xperia S or anything related to Sony under "Other Devices" or other similar areas. Then right click on it to install drivers.

Mirhawk said:
Do one thing, check Your Device Manager. Disconnect Your phone, Open Device Manager, then connect Your phone again. See if the Device Manager gets refreshed. If it does, Your device is being connected to the PC. Then check for Xperia S or anything related to Sony under "Other Devices" or other similar areas. Then right click on it to install drivers.
Click to expand...
Click to collapse
I just did that.
My phone is getting showed under "Tragbare Geräte" which means portable devices. When I right click on it says:
-Update drivers
-Deactivate
-Uninstall
-Looking for changed hardware
-Properties
If I click on Update drivers the message shows, that the best driver is already installed.

domiankrey said:
I just did that.
My phone is getting showed under "Tragbare Geräte" which means portable devices. When I right click on it says:
-Update drivers
-Deactivate
-Uninstall
-Looking for changed hardware
-Properties
If I click on Update drivers the message shows, that the best driver is already installed.
Click to expand...
Click to collapse
There should be a device like the highlighted one in attachment.

Mirhawk said:
There should be a device like the highlighted one in attachment.
Click to expand...
Click to collapse
This is how it looks on my PC.
Since (I was told in an other Android Forum it is like this) that on Ubuntu, Ubuntu recognizes my phone automaticly and still I installed the drivers there and it didnt not work and since neither RecoverX on my phone nor smanager on my phone dit install CWM I think the problem is my phone not the PC...

domiankrey said:
This is how it looks on my PC.
Since (I was told in an other Android Forum it is like this) that on Ubuntu, Ubuntu recognizes my phone automaticly and still I installed the drivers there and it didnt not work and since neither RecoverX on my phone nor smanager on my phone dit install CWM I think the problem is my phone not the PC...
Click to expand...
Click to collapse
Could You translate what the yellow mark text is? I think the device is recognized wrongly or wrong drivers were installed for it. Unfortunately, I don't know much about Ubuntu.

Mirhawk said:
Could You translate what the yellow mark text is? I think the device is recognized wrongly or wrong drivers were installed for it. Unfortunately, I don't know much about Ubuntu.
Click to expand...
Click to collapse
What do you mean with yellowk mark text? I see no yellow text...
If you mean the 3 devices which have a yellow sign:
- Ethernet Controller should be clear.
- Teredo Tunneling Pseudo-inferface - I do not know what that is.
- Basissystemgerät - means somehting like basic system device

With other ROMS I was able to install a CWM from my phone (with the deliverx app or a script manager app), but for this rom this doesnt work anymore.
So is there a way to install an other ROM without CWM (and when I have this ROM I would try if installing CWM directly with an app works again)?

domiankrey said:
With other ROMS I was able to install a CWM from my phone (with the deliverx app or a script manager app), but for this rom this doesnt work anymore.
So is there a way to install an other ROM without CWM (and when I have this ROM I would try if installing CWM directly with an app works again)?
Click to expand...
Click to collapse
Unfortunately Your device is not being detected as an adb device. The problem would be solved if somehow it is detected in adb or if You are able to install recovery from cell. I will try to check out more. Say, did You try the goo manager app, twrp manager or rom maanager to install recovery?

Mirhawk said:
Unfortunately Your device is not being detected as an adb device. The problem would be solved if somehow it is detected in adb or if You are able to install recovery from cell. I will try to check out more. Say, did You try the goo manager app, twrp manager or rom maanager to install recovery?
Click to expand...
Click to collapse
I will Try Goo and TWRPG Manager. Rom Manager does not work with Xperia S I already tried it.
EDIT:
1. Goo Manager does not work. I installed the Open Recovery.img and then I tried to install the ROM (eXistenZ V2 Black) but it only restarts my phone <- Does not work
2. TWRPG Manager does not even the TWRPG Recovery.
3. Previously I used this App to install CWM and it worked. Now I used the App and the App said installed CWM worked but There is no CWM on my phone (or it can't get started neither manually by pressing up nor automatically with an App which reboots me into CWM). <-Does no work.
4. On other time I used this App to run the cwm-install.ch on my phone. It worked and CWM was on my phone. Now the script does not run and therefore CWM also cannot be installed with this method. <- Does not work.
5. After all that, today I tried to install an official Rom with Sony PC Companion (and then starting from 0 with an other ROM, to try all the other stuff again) but It says I cannot install the official ROM Update. because, I do not have the official ROM installed, <- Does not work
I dont know what to do anymore.

ADB under TWRP

I am using Windows 8.1
I can connect my Xperia S throught ADB under USB debugging mode.
But I cannot do the same thing in TWRP.
Anything wrong?

I hope my reply helps you
microming said:
I am using Windows 8.1
I can connect my Xperia S throught ADB under USB debugging mode.
But I cannot do the same thing in TWRP.
Anything wrong?
Click to expand...
Click to collapse
It is because the TWRP version which you use doesn't seem to support ADB. Try the same using CWM

rockstar.dj364 said:
It is because the TWRP version which you use doesn't seem to support ADB. Try the same using CWM
Click to expand...
Click to collapse
or perhaps you need to install the drivers. download flashtool, install flashtool, boot to disabling driver signature in win8 (google how to do this), install flashtool's driver (i chose everything that has xperia s in it ), reboot your phone to twrp, plug your phone to pc. open device manager, then you'll see that there's exclamation mark in xperia s device, choose install/update driver, choose browser my computer, choose let me pick, choose android adb (sony adb). then simply type adb devices in cmd to test it.
that's all. perhaps there are some steps that arent necessary, but that's how i remember i done it.
good luck