Database Info

[Q][NS4G] Bricked? - Device Not Recognized in OS X, Windows or Ubuntu

Hey all, I had a botched ICS upgrade on my Nexus S 4G today using Google's factory images. I can get into TWRP and into the bootloader, but my device is not recognized by any operating system that I have tried to connect it to. Swapping USB cables hasn't made a difference. My other NS4G can connect with no problems to any of these operating systems with any USB cable. While the phone does charge over USB while connected to a computer, I can't mount the SD card in TWRP and I can't use fastboot in the bootloader. With fastboot, the only message I get is "waiting for device."
Should I just cut my losses and jettison the phone? Any suggestions on how to remedy the situation?
Thanks in advance for your help.

Pitiful bump.

Which factory image did you flash? What's the exact model of your phone? See the sticker beneath the battery.
Can you boot the mobile?
What was the problem through fastboot update?
Boot into bootloader/fastboot mode. What does it display?
Please provide a lot more details about the problem.

anglergab said:
Which factory image did you flash? What's the exact model of your phone? See the sticker beneath the battery.
Can you boot the mobile?
What was the problem through fastboot update?
Boot into bootloader/fastboot mode. What does it display?
Please provide a lot more details about the problem.
Click to expand...
Click to collapse
Thanks for the reply. Pretty sure I'm bricked unless I can get JTAG. I wasn't paying attention and it was super late at night when I was flashing for my wife (who was over custom roms). I mixed up bootloaders and sent the GSM version to my CDMA Nexus. I can't boot into Android. I can get into TWRP, but can't mount USB to get any files onto the device.

Connect the phone to a Linux PC, then please post in this thread the output of the following commands:
Code:
tail /var/log/messages
Code:
lsusb
By the way you can reflash baseband/radio firmware image from recovery through ADB.

anglergab said:
Connect the phone to a Linux PC, then please post in this thread the output of the following commands:
Code:
tail /var/log/messages
Code:
lsusb
By the way you can reflash baseband/radio firmware image from recovery through ADB.
Click to expand...
Click to collapse
Thanks for the reply. I'll give it a shot in a few hours when I can get to a linux box. Part of the problem is that I get no recognition that the device is connected from any OS. I tried accessing the phone while it was in download mode through Heimdall running on Ubuntu and it couldn't see the phone.
I'll give the commands a try though and let you know. Should the phone be at the bootloader or in recovery?

You can try connecting the phone first in bootloader and then recovery. Run the above commands in both modes. Connect the phone directly, without hubs, preferably with its own cable.

anglergab said:
You can try connecting the phone first in bootloader and then recovery. Run the above commands in both modes. Connect the phone directly, without hubs, preferably with its own cable.
Click to expand...
Click to collapse
This is my output both times. The computer can't see the phone.
[email protected]:~$ tail /var/log/messages
tail: cannot open `/var/log/messages' for reading: No such file or directory
[email protected]:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 04f2:0841 Chicony Electronics Co., Ltd
Bus 001 Device 004: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
Bus 001 Device 005: ID 0781:5530 SanDisk Corp. Cruzer U3 4gb SDCZ36
Bus 001 Device 006: ID 0461:4d0f Primax Electronics, Ltd
Bus 002 Device 003: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)
Bus 002 Device 004: ID 148f:3573 Ralink Technology, Corp.
[email protected]:~$
Click to expand...
Click to collapse

IF stuck between roms Tutorial (Linux walkthrough, Windows one on the way)

This is for if you have flashed a rom and it boot loops and when you try and restore and it stays in a bootloop,
I had this issue during the week and freaked out but thanks to termleech who created this http://forum.xda-developers.com/showthread.php?t=1699535 rom I was able to get my tablet back in working order.
This Tutorial is for Ubuntu/Linux (ill try and get one for windows but I wasnt able to do this through windows) for this im also guessing that you have a custom recovery flashed.
Step one:
go to http://source.android.com/source/initializing.html and go down to the section that says configure usb access the file will be saved in this location in /etc/udev/rules.d/51-android.rules
follow that section for all the lines that say "<username>" replace <username> with the account name that you are using,
in my case each of those it was changed to "aaron".
Step two:
Open terminal and type sudo lsusb this will display everything that is connected through usb. you should get something looking like this
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0c45:641d Microdia 1.3 MPixel Integrated Webcam
Bus 002 Device 003: ID 0b05:4d03 ASUSTek Computer, Inc.
Bus 002 Device 004: ID 0bda:0159 Realtek Semiconductor Corp. Digital Media Card Reader
Bus 002 Device 005: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 002 Device 006: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
Bus 002 Device 007: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics]
Bus 002 Device 008: ID 413c:8160 Dell Computer Corp. Wireless 365 Bluetooth
Now in the File you created from step one create a new line and replace the values with the values you just got from lsusb
so the line for me looked like this when I pasted it back into the file.
# usbboot protocol on asus (Asus Transformer TF300T)
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", ATTR{idProduct}=="4d03", MODE="0600", OWNER="Aaron"
Step three:
Setting up the Android SDK
This is where I had the most trouble.
So you need to open the market place on Ubunto and download openJDK7, let that install then go to the android site and download the the android tools
http://dl.google.com/android/android-sdk_r20-linux.tgz
extract that to your desktop.
Then in terminal navigate to the folder called tools in the sdk and open it.
then type sudo ./android
that will install the tools and open android sdk manager.
when that opens all you will need to do is tick the tools box and it will install everything you need.
Once that is installed you will need to navigate to the platform-tools folder in the root of that folder.
What I did was also copy the rom that I wanted to flash into the folder just to make it easier on myself.
On your tablet boot it into the custom recovery but by powering the tablet it on and holding the volume down and power button then pressing the volume up.
YOu can leave you tablet in the home screen for the recovery for the next bit.
Step four:
Copying the rom to the tablet.
On terminal you will need to navigate back to the platform-tools folder.
and copy the rom you want to use into it (for this i will call the rom fix.zip this is just for this tutorial)
make sure your tablet is connected now and in the recovery sceen not{/B] fastboot!!!!!
on terminal type sudo ./adb push fix.zip /sdcard
It will look like its doing nothing that pop up saying that it copied it 33 seconds.
Step five:
factory reset x3
then wipe cache and dalvik
then flash + gapps (if not included with rom)
then wipe cache + davlik again
then reboot, on first boot it can take between 2-5minutes to start.
Now you have a working tablet again
Hope this helps those who are stuck! ill try get a guide together for windows and maybe a video if many people end up using this.
if you need to get in touch fast im always on twitter @d_crossfader
I am not responsible if anything goes wrong

How do you give root to a user in ubuntu? Thanks for the help by the way have ubuntu installed made rule but cant transfer because im not root user?
Sent from my HTCEVOV4G using xda premium

lukethepainter said:
How do you give root to a user in ubuntu? Thanks for the help by the way have ubuntu installed made rule but cant transfer because im not root user?
Sent from my HTCEVOV4G using xda premium
Click to expand...
Click to collapse
Just use sudo. There is no root user in Ubuntu-based distros.

almost got it
i followed all steps and when i go to push the rom i get
[email protected]:/media/sdk/platform-tools$ ls
aapt adb.vol03+04.par2 aidl fix.zip source.properties
adb adb.vol07+08.par2 api lib
adb.par2 adb.vol15+16.par2 dexdump llvm-rs-cc
adb.vol00+01.par2 adb.vol31+32.par2 dx NOTICE.txt
adb.vol01+02.par2 adb.vol63+35.par2 fastboot renderscript
[email protected]:/media/sdk/platform-tools$ sudo ./adb push fix.zip /sdcard
sudo: ./adb: command not found
[email protected]:/media/sdk/platform-tools$
any suggestions?

Hey could you enable root by following these steps https://help.ubuntu.com/community/RootSudo then try again as su
Sent from my Transformer Pad TF300T using XDA Premium HD app

On vacation this week will try it when I get home and thank you for helping me your the best
Sent from my HTCEVOV4G using xda premium

No worries, when it happened to me last week I freaked out
Sent from my Transformer Pad TF300T using XDA Premium HD app

usb connection non functional, after changing data partition

hi,
maybe some of you already know, that i am working on a dualboot solution for the note2.
it is almost functional now, but i have no idea anymore, where to search for a solution for the last bug, mentioned in the titel.
the commits in question are this, for cm-10.1:
https://github.com/DerTeufel/androi...mmit/5dc8b0e77cb21562aa41981fdea65fef6945270e
and this, for samsung based roms:
https://github.com/DerTeufel/androi...mmit/a57b6da843d0b6b47071e947008bb5665099163f
both commits are similar to the changes, gokhanmoral has made to his i9300 dualboot initramfs. i could not (edit: fixed typo here, this word was missing before) see anything related (if he had similar issues) in his commits/code
as you can see in the commis, i only have switched the data partition at this point.
basically it's like this:
mounted another partition at /data
created a new data folder at data/media (now mounted in /.secondrom)
bind mount /.secondrom/media/data into the deafult /data partition
create media folder in the new /data
bind mount /.secondrom/media into the new /data/media
everything is working as expected, just connecting to usb fails. phone is going into charging mode, without usb connection notification, usb debugging/adb is also not working.
do i just reboot into primary rom, usb is working again.
could oneone give me a hint, what could be causing this?
edit: the changes don't depend on the kernel used with the initramfs. if you want to try yourself, you should be fine by just applying the changes to your initramfs.
switching between roms is done by:
echo primary > /cache/.secondaryboot
and then reboot
echo secondary > /cache/.secondaryboot
reboot
it is going to be changed by recovery normally, but i need to do some more changes, before pushing it to github

AW: usb connection non functional, after changing data partition
Just a little update, without any change to the problem.
I thought, maybe mounting the sdcard by using fuse is causing the issue. Well, it is not. I have commented it out, exported storage/sdcard0 as storage, and bind mounted data/media into it.
USB still isn't working after this.
Any other ideas are highly welcome.
Gesendet von meinem GT-N7105 mit Tapatalk 2

after some more testing, i realized, that the device gets recognized by ubuntu, running in a vm. i now can adb to it
mounting the sdcards to it, does still not work

i am still stuck at the same thing...no one an idea?
today i have realized, that my vm is recgnizing my phone as different devices, if i am using another data partition...if this isnt weird enough, it also tells me, it is a galaxys 2 (i never owned a s2, and never installed drivers for it).
this is, when it is working normally (/data unchangend):
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 052: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
this is the same device, same kernel, same rom, 5 minutes later, just mounted the other /data partition:
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 058: ID 18d1:d002 Google Inc.

Nexus 5 with CM13 bootloop

Yesterday my phone just switch off and won't be powered on. After whole night on chager i am stuck on CM boot animation. I am able to get in recovery (TWRP), but after entering pin i am getting:
Code:
Updating partition details...
E:Unable to mount '/persist'
...done
E:Unable to mount storage
Full SElinux....
Data succesfully decrypted, new block device: '/dev/block/dm-0
.. and stuck here... Thank you for advices!

Samgarr said:
Yesterday my phone just switch off and won't be powered on. After whole night on chager i am stuck on CM boot animation. I am able to get in recovery (TWRP), but after entering pin i am getting:
Code:
Updating partition details...
E:Unable to mount '/persist'
...done
E:Unable to mount storage
Full SElinux....
Data succesfully decrypted, new block device: '/dev/block/dm-0
.. and stuck here... Thank you for advices!
Click to expand...
Click to collapse
Maybe this will help... http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576

Thank you, now trying mentioned howto, but things going complicated...
Fastboot detect my device:
Code:
[[email protected] sam]# fastboot devices
04e16ffbf0dc07b5 fastboot
adb does not:
Code:
[[email protected] sam]# adb devices
List of devices attached
Code:
[[email protected] sam]# lsusb
Bus 004 Device 003: ID 0bdb:1911 Ericsson Business Mobile Networks BV
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 04f2:b221 Chicony Electronics Co., Ltd integrated camera
Bus 001 Device 007: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 012: ID 18d1:4ee0 Google Inc. Nexus 4 (bootloader)
Bus 001 Device 006: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D / OP-620D
Bus 001 Device 004: ID 17ef:100a Lenovo ThinkPad Mini Dock Plus Series 3
Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Code:
root ~ $ cat .android/adb_usb.ini
0x0bdb
0x18d1
I am using Nexus tools in Arch Linux, i am getting same result with adb and fastboot utils from distribution packages. Thank you for advices.

Adb commands won't work with the phone in fastboot mode.
Have you tried flashing a stock kk, LP, or mm rom?
I don't know Linux so I can't comment on the logs.

@Samgarr
Some ROM's are not adb debuggable during boot.
You need to have three lines in ramdisk's default.prop for ROM to be able to be debugged in adb on userdebug type of builds.
If your phone is on and still adb is not working, then better flash a different ROM.
IF you're still in bootloop and are looking for a way to go out of it, since you're in fastboot,
Download nexus factory images and flash them in fastboot mode
Hope I helped

Thank you guys for your time, i think my phone have fried eMMC memory.
After i'm succesfull boot (fastboot boot recovery.img) recovery from stock ROM i tried wipe cache/data or flash stock recovery but i am constantly getting read/write errors from cache and recovery partition. Formating and recreating filesystem won't help. I bought this phone as a second hand and after removing backcover i see marks of water damage corrosions. So water damaged eMMC it is .

adb devices: device offline

Hi, I have recently flashed the Evolution X (Android 11) ROM to my previously bricked device. I'm trying to install some APKs but I get the device offline error:
Code:
~ $ adb install ~/usr/local/Downloads/sh.ppy.osulazer.apk
Performing Push Install
adb: error: failed to get feature set: device offline
This hasnt happened in LineageOS or Pixel Experience.
And if you ask, yes the laptop is detecting the device
Code:
~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:5521 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 025: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I tried adding the /etc/udev/rules.d/51-android.rules file with the following contents:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", GROUP="adbusers"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_fastboot"
Then restarted my computer, reloaded udev rules but it still doesnt work. Yes, my user is part of the adbusers group. Also tried as root user but same thing. I'm on Arch Linux btw.
Is there any way to fix this or do I just go back to PixelExperience/LineageOS?

rogerpanza said:
Hi, I have recently flashed the Evolution X (Android 11) ROM to my previously bricked device. I'm trying to install some APKs but I get the device offline error:
Code:
~ $ adb install ~/usr/local/Downloads/sh.ppy.osulazer.apk
Performing Push Install
adb: error: failed to get feature set: device offline
This hasnt happened in LineageOS or Pixel Experience.
And if you ask, yes the laptop is detecting the device
Code:
~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:5521 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 025: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I tried adding the /etc/udev/rules.d/51-android.rules file with the following contents:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", GROUP="adbusers"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_fastboot"
Then restarted my computer, reloaded udev rules but it still doesnt work. Yes, my user is part of the adbusers group. Also tried as root user but same thing. I'm on Arch Linux btw.
Is there any way to fix this or do I just go back to PixelExperience/LineageOS?
Click to expand...
Click to collapse
Restart your device.

SubwayChamp said:
Restart your device.
Click to expand...
Click to collapse
I've done that tons of times

rogerpanza said:
I've done that tons of times
Click to expand...
Click to collapse
Well, you didn't mention it, it looks like all is fine with Linux, it could be an error on the ROM side anyway check that you killed ADB server previously, and you don't have many devices attached to the PC. You should try running a terminal from user space like Desktop or Downloads (moving the app there) and not from the root directory to see if something change.

SubwayChamp said:
Well, you didn't mention it, it looks like all is fine with Linux, it could be an error on the ROM side anyway check that you killed ADB server previously, and you don't have many devices attached to the PC. You should try running a terminal from user space like Desktop or Downloads (moving the app there) and not from the root directory to see if something change.
Click to expand...
Click to collapse
I only have my phone plugged into my laptop, tried moving /usr/bin/adb to another folder as you said but same thing. And yeah it's most probably a ROM problem :/