Develop Bugs

[Q] Program Samsung Galaxy Nexus SC-04D without USB connection

Hello to all,
this is my first post here, please be comprehensive.
I have a Galaxy Nexus, which I bought in the USA, but its IMEI corresponds to a Japanese
version, NTT Docomo SC-04D . The phone came with the unlocked bootloader and it has not been rooted yet.
It has several problems :
1) The phone turns off whenever the screen goes into sleep mode after some inactivity. If the sleep mode is trigger by a short push of the
power button instead the phone is not turned off and it can be made available gain by a subsequent short push of the power button, before
the time for sleep mode has passed.
2) The phone turns off immediately every time it is connected to a computer via USB cable. This happens both with the stock cable that with many other, even if the same cables works fine when the phone is connected to a wall charger.
3) Trying to access the fastboot mode at boot by holding Vol. Up+Vol. Down+ Pwr results in the Androind logo being shown with info about the phone - like build number and Unlocked bootloader. Upon releasing of the buttons however, the phone turns off and no option can be selected.
The phone is less than one year old but Samsung is not willing to repair it, even outside of warranty, because of the foreign IMEI .
This is just ridicolous, because the phone is otherwise identical in hardware to phones sold in the US.
I also already tried several other repair centers, but as soon as I explain that there is no way to connect to the phone via USB , they refuse to service it.
I am writing here hoping that somebody could help/suggest me possible solutions to this problems, which appears to be a firmware one.
I am open to try other ROM or to root the device, but the problem 2) above prevents me from trying most of the solutions I have been reading about in this forum. I also read about adb commands over wifi, so I was wondering if that could be a viable option.
Many thanks.

Maybe you have a bad hardware button / one that is sticking? Can you narrow it down by releasing the buttons one at a time once booted to fastboot screen? If you cannot get fastboot to work via usb command line, its time to get a new phone. Mobile odin by chainfire may be of help to you, but it's not highly recommended. Again, no fastboot means i'd be looking for another device. I did see that negri electronics was replacing docomo phones they sold, which may also be helpful. And as far as adb over wifi, it will work, but again NO fastboot.

bodh said:
Maybe you have a bad hardware button / one that is sticking? Can you narrow it down by releasing the buttons one at a time once booted to fastboot screen? If you cannot get fastboot to work via usb command line, its time to get a new phone. Mobile odin by chainfire may be of help to you, but it's not highly recommended. Again, no fastboot means i'd be looking for another device. I did see that negri electronics was replacing docomo phones they sold, which may also be helpful. And as far as adb over wifi, it will work, but again NO fastboot.
Click to expand...
Click to collapse
Thanks for taking the time to answer. No, it has nothing to do with the hardware button, releasing them in any combination will result in the android screen being show until the last is released, after that the phone just turns off.
Unfortunately the device was not bought by Negri, but by HassleFreeCell.com. I already contacted them repeatedly because the problem manifested when the device was still under the 1 year manufacturer warranty, but they refused to help and now don't even answer my email or phone calls any longer. Caveat Emptor.
Also trashing the phone is not a solution I'm looking for, since it came for 500$ less than one year ago and apparently it has only a firmware problem.
Does anybody has experiences on rooting/modding a Galaxy Nexus via adb wireless commands ? Can you suggest a easy-to-follow guide ?

ADB wireless requires ROOT access. you wont be able to do anything to it over the wifi unless its already rooted with bootloader unlocked

It's probably a hardware issue, since normal rom and fastboot are loaded from separate partitions. So if fastboot doesn't work then flashing a rom has no chance of fixing that.
I'd first check and clean the usb port. Then try to get into fastboot to flash twrp or cwm recovery.

[Q] bricked device

Hi There all,
I bricked my device!
I installed multi window manager and ran the patch.
I should have not done this.
After one last message (something like copy binary from SD card) the device was dead.
Any help is highly appreciated

HANSB57 said:
Hi There all,
I bricked my device!
I installed multi window manager and ran the patch.
I should have not done this.
After one last message (something like copy binary from SD card) the device was dead.
Any help is highly appreciated
Click to expand...
Click to collapse
Can you access recovery or download mode?

sefrcoko said:
Can you access recovery or download mode?
Click to expand...
Click to collapse
No I cant.
All combinations (power, volume home etc.. failed)
Removed back cover, disconencted battery
No result.

How did you remove the back cover?
I've been able to get mine out of pickles not involving the /boot partition by holding down the volume down, home and power keys simultaneously. Shortly after the model 5110 message displays, I release power and am asked if I really want to put the device into update mode.
I use Odin to write in the firmware I downloaded from samfirmware a few weeks ago.
I needed to do this last night after trying to disable a few system apps. I'm not sure which, probably a thing called "bubble," but as soon as I had, the device froze. A reboot went all the way through but then locked up after my startups finished.
I also needed to do this after something much closer to a soft brick involving trying to use the Xposed framework to change lcd density.
I reflashed and was able to defrost and I was back in business.

roustabout said:
How did you remove the back cover?
I removed it by gently prying the white back cover of.
I would recommend agains it because its delicate.
But I think you would advice me agains bricking my device. :angel:
I cant get it in download mode.
It wont show the charging again when charging.
It seems dead
Anybody might have a clue??
Click to expand...
Click to collapse

something just occurred to me - you've pulled out your sdcard and set it aside? sometimes a bodgy sdcard can get in the way of boot up, though it seems unlikely here.
It doesn't seem that patching the framework, even if it keeps you from booting past the model # screen, should be able to keep the device from at least powering on.
If you connect it to your PC and try holding in power for ~30 seconds, does any USB device or android device activity occur at all, even if a device appears and disappears again?
I did find that I had a "konawifi" device attached to my PC and needed to update its driver to access the device in CWR mode.

roustabout said:
something just occurred to me - you've pulled out your sdcard and set it aside? sometimes a bodgy sdcard can get in the way of boot up, though it seems unlikely here.
It doesn't seem that patching the framework, even if it keeps you from booting past the model # screen, should be able to keep the device from at least powering on.
If you connect it to your PC and try holding in power for ~30 seconds, does any USB device or android device activity occur at all, even if a device appears and disappears again?
I did find that I had a "konawifi" device attached to my PC and needed to update its driver to access the device in CWR mode.
Click to expand...
Click to collapse
I pulled the SD card
This afternoon I will try your tip (connecting it to the PC)
I also will try a jig although I think this is useless
My last resort is back to Samsung. I have 2 choices, repair or make a frisbee out of it. I prefer the first option especially beacause I was rather pleased with the device

I tried making a jig when I bricked my Galaxy Media Player, and it did not work. Samsung repaired it, eventually.

roustabout said:
I tried making a jig when I bricked my Galaxy Media Player, and it did not work. Samsung repaired it, eventually.
Click to expand...
Click to collapse
Just brought it back to shop. Will sent it back to Samsung.
will take 3 weeks. Luckely I have my trusted tab 10.1 to use.

HANSB57 said:
Hi There all,
I bricked my device!
I installed multi window manager and ran the patch.
I should have not done this.
After one last message (something like copy binary from SD card) the device was dead.
Any help is highly appreciated
Click to expand...
Click to collapse
Its totally impossible that patching the FlashBarService.apk could completely brick your device... A Boot loop is possible, but not a brick.
Sent from my GT-N8013 using Tapatalk HD

Flashed the wrong recovery!
Hi there, Ive soft bricked my Note 8.0 by accidentally flashing Note 2 recovery. Anyone know how I can fix this? Stuck in boot screen. I can get to download mode and Odin recognizes it, but I have no idea what to do from there.
Any advice/help would be greatly appreciated..

no problem flash the note 8 recovery with odin

Sorry but I am new to soft brick. Have 3 rooted devices and never brick before. Can put device in download mode as kennielsen but I'm lost after that. Details on what to do and how to do it would be very nice, please!
Sent from my SM-N900V using XDA Premium 4 mobile app

Bootloader unable to boot ROM, recovery. Computer not detecting fastboot presence

My latest configuration was:
Bullhead 32 GB board,
PureNexus (6.0.1): July build
PureNexus Gapps
Stock kernel
TWRP
SuperSU
Situation/problem: One day, the phone went off in my pocket, and I thought it accidentally got powered off or something. When I tried to boot it, it would load the Google screen, but not the boot process (this is not a bootloop as it won't even start the boot process). So I went to the BL, tried to boot from there, no luck.
Then I tried to get into recovery from BL, still it would freeze for a few seconds, load the google screen, and back to BL.
So I realized it was time to clean flash, I connected in fastboot mode, but my computer (Linux, Ubunutu 16.04) won't detect the device fastboot mode (I have done everything before on the same computer). Just to be sure, I tried connecting in 3 different computers so that it wasn't a driver problem, but to no avail.
I am now stuck with a device that won't go past the bootloader and won't even let me flash a new system.
Possible problems I think this may be a problem with the USB port and I had just not realized it, because I had dropped the phone from 1m high just a week ago.
When I called the LG service, they said they'd have to replace motherboard and that it can't have been the USB port.
I am perplexed now, as to what to do. I had saved up loads to buy the latest flagship Nexus just this January, and now it's going away...
Another observation: I was having problems with the phone as it was randomly rebooting every once in a while for a month, but I ignored flashing a new build because I was busy with studies. I don't know if this is related but just putting it out there.
Possible things that I could do? Appreciate your help in advance.

zakoda said:
My latest configuration was:
Bullhead 32 GB board,
PureNexus (6.0.1): July build
PureNexus Gapps
Stock kernel
TWRP
SuperSU
Situation/problem: One day, the phone went off in my pocket, and I thought it accidentally got powered off or something. When I tried to boot it, it would load the Google screen, but not the boot process (this is not a bootloop as it won't even start the boot process). So I went to the BL, tried to boot from there, no luck.
Then I tried to get into recovery from BL, still it would freeze for a few seconds, load the google screen, and back to BL.
So I realized it was time to clean flash, I connected in fastboot mode, but my computer (Linux, Ubunutu 16.04) won't detect the device fastboot mode (I have done everything before on the same computer). Just to be sure, I tried connecting in 3 different computers so that it wasn't a driver problem, but to no avail.
I am now stuck with a device that won't go past the bootloader and won't even let me flash a new system.
Possible problems I think this may be a problem with the USB port and I had just not realized it, because I had dropped the phone from 1m high just a week ago.
When I called the LG service, they said they'd have to replace motherboard and that it can't have been the USB port.
I am perplexed now, as to what to do. I had saved up loads to buy the latest flagship Nexus just this January, and now it's going away...
Another observation: I was having problems with the phone as it was randomly rebooting every once in a while for a month, but I ignored flashing a new build because I was busy with studies. I don't know if this is related but just putting it out there.
Possible things that I could do? Appreciate your help in advance.
Click to expand...
Click to collapse
Here's your solution for it not being detected in fastboot mode.......in fastboot mode, connect your phone to your computer. go to your device manager and find your device. double click on your device, right click on the second option and select update driver. than select browse my computer and than select pick from a list of drivers and manually install the driver for fastboot mode.....hope this helps :good:

dominoeflux said:
Here's your solution for it not being detected in fastboot mode.......in fastboot mode, connect your phone to your computer. go to your device manager and find your device. double click on your device, right click on the second option and select update driver. than select browse my computer and than select pick from a list of drivers and manually install the driver for fastboot mode.....hope this helps :good:
Click to expand...
Click to collapse
I have mentioned in my post: It is not a driver problem

zakoda said:
I have mentioned in my post: It is not a driver problem
Click to expand...
Click to collapse
if its not being detected in fastboot mode, than that means it's a driver problem since the same thing happened to me. you have to manually install the fastboot driver for fastboot mode. I've read your post and I understood exactly what you were talking about. have you even tried to check the driver? have you tried flashing back stock? if you've checked other computers that you have mentioned and it's still not detecting it in fastboot mode with the other computers, than the driver for fastboot mode needs to be updated manually, seeing that if it was detected by the other computers that you have, you wouldn't be asking for help right now because your device would already be up and running. hey i'm just trying to help u here. it doesn't hurt to double check your driver. I may be a junior member, but I know plenty seeing that I've been through the same situation myself. if it's not the driver as you say it's not, what version TWRP were you running and did you restore a backup with the EFS checked?

Hey, I can confirm it's not a driver problem.
I got the phone to boot up yesterday, flashed the latest PureNexus (7.x) and after a short while it again went into reboot cycles.
I tried TWRP, there also mid-flashing it randomly rebooted. I think it is rebooting after even small amount of activity. Maybe the thermal sensors are damaged causing it to flag warning with slightest heating. Or maybe some other circuitry is damaged, causing the temperature to actually rise in short while, and it is not being felt due to the plastic body. In any case I think this is a hardware damage, though I have no clue why. I will try contacting Google to see if they can replace it.
By the way, how long is the warranty valid? I had bought the device in Dec 2015.

zakoda said:
Hey, I can confirm it's not a driver problem.
I got the phone to boot up yesterday, flashed the latest PureNexus (7.x) and after a short while it again went into reboot cycles.
I tried TWRP, there also mid-flashing it randomly rebooted. I think it is rebooting after even small amount of activity. Maybe the thermal sensors are damaged causing it to flag warning with slightest heating. Or maybe some other circuitry is damaged, causing the temperature to actually rise in short while, and it is not being felt due to the plastic body. In any case I think this is a hardware damage, though I have no clue why. I will try contacting Google to see if they can replace it.
By the way, how long is the warranty valid? I had bought the device in Dec 2015.
Click to expand...
Click to collapse
In the most country, the warranty is 12month so maybe gone because now it's 21th of december

Fire TV1 bricked no lights

This FireTV has never been opened. I blocked updates per Aftvnews guide. ALso from AFTVnews serial conversion to software showed version 51.1.01 or 51.1.02. Unfortunately, I did not recall these version will not get past update screen if you are blocking updates. I had let sit at the update screen for over 30 minutes, then pulled plug. Now no lights, nothing. Tried ALT-PrtSCr-i and ALT-SysRq nothing. I bought USB A-A cable and windows shows QUB-xxxxx(or close to this from memory). Downloaded Ubuntu LiveCD and it shows 6 partitions from 17MB, 6.1GB, 2x 805MB, 2 x 8.4MB.
So not unlocked bootloader, no CWM, no TWRP nothing becasue this was A Virgin AFTV 1.
I have searched, requested help in other threads and no response and do not know what else can be done.
I do not know linux, but can follow steps and have updated 2 AFTV1 with rbox methods.
Is there anyway to save this Virgin AFTV1?

Im in the exact same boat.. But in deeper waters.. Fire Tv is only recognized as Qualcomm com port (Qualcomm HS QDLoader 9008) without showing the partitions, either in windows or linux... Never tried to install a recovery like Twrp, to unlock the bootloader, just had root since day one. But suddenly, when installing the last update something happened after the "Optimizing system storage and applications" menu. A bricked fire tv. Unfortunatelly i cant find a single trick to work... And yes.. I looked everywhere for a solution..

jj^2 said:
This FireTV has never been opened. I blocked updates per Aftvnews guide. ALso from AFTVnews serial conversion to software showed version 51.1.01 or 51.1.02. Unfortunately, I did not recall these version will not get past update screen if you are blocking updates. I had let sit at the update screen for over 30 minutes, then pulled plug. Now no lights, nothing. Tried ALT-PrtSCr-i and ALT-SysRq nothing. I bought USB A-A cable and windows shows QUB-xxxxx(or close to this from memory). Downloaded Ubuntu LiveCD and it shows 6 partitions from 17MB, 6.1GB, 2x 805MB, 2 x 8.4MB.
So not unlocked bootloader, no CWM, no TWRP nothing becasue this was A Virgin AFTV 1.
I have searched, requested help in other threads and no response and do not know what else can be done.
I do not know linux, but can follow steps and have updated 2 AFTV1 with rbox methods.
Is there anyway to save this Virgin AFTV1?
Click to expand...
Click to collapse
Was it a refurb? I had a refurb that had no power out of the box. Sent it back.

cancelyourcable said:
Was it a refurb? I had a refurb that had no power out of the box. Sent it back.
Click to expand...
Click to collapse
No, brand New.
Does the update work thru the usb?

walkabouts said:
Im in the exact same boat.. But in deeper waters.. Fire Tv is only recognized as Qualcomm com port (Qualcomm HS QDLoader 9008) without showing the partitions, either in windows or linux... Never tried to install a recovery like Twrp, to unlock the bootloader, just had root since day one. But suddenly, when installing the last update something happened after the "Optimizing system storage and applications" menu. A bricked fire tv. Unfortunatelly i cant find a single trick to work... And yes.. I looked everywhere for a solution..
Click to expand...
Click to collapse
Yes, I thought we would get some responses from somebody. Possibly even @rbox and @aftvnews.

I wish i was in your situation... You can always dd the partitions again, and eventually fix the brick... In my case (QDLoader 9008) there is nothing i can do. Eventually i could theoretically reprogram the emmc chip, but.. not going to happen. I presume you are in stuck in the Qualcomm HS QDLoader 9006, that should be fixable, since you can write to the partitions. There is a post from Rbox where he tells in detail what to do. Best of luck!

Since your FTV its still showing its partitions (unlike me!) you should be successful with these instructions. https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676

walkabouts said:
Since your FTV its still showing its partitions (unlike me!) you should be successful with these instructions. https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676
Click to expand...
Click to collapse
Thanks for the idea, but i did not have any chance to unlock my bootloader. So, this will not help.

jj^2 said:
Thanks for the idea, but i did not have any chance to unlock my bootloader. So, this will not help.
Click to expand...
Click to collapse
You're absolutely right... Unfortunately.. Perhaps someone in a near future discover a way to bring it to life. But for now we're holding useless bricks..

walkabouts said:
You're absolutely right... Unfortunately.. Perhaps someone in a near future discover a way to bring it to life. But for now we're holding useless bricks..
Click to expand...
Click to collapse
Has anyone been able to download update files and put on usbdrive and have the AFTV read the usb?
Please Help

jj^2 said:
Has anyone been able to download update files and put on usbdrive and have the AFTV read the usb?
Please Help
Click to expand...
Click to collapse
From my experiences, won't work. The fire tv don't read the update.zip. Without access to a workable recovery, a unlocked bootloader, or functional ADB, there is no way to revive this thing. I would love to be wrong, though..

walkabouts said:
From my experiences, won't work. The fire tv don't read the update.zip. Without access to a workable recovery, a unlocked bootloader, or functional ADB, there is no way to revive this thing. I would love to be wrong, though..
Click to expand...
Click to collapse
Walkabout,
Thanks for the feedback. Really disappointed of the lack of responses from the XDA Community

jj^2 said:
Walkabout,
Thanks for the feedback. Really disappointed of the lack of responses from the XDA Community
Click to expand...
Click to collapse
To be honest, me too. But probably, since they all have hardware in working conditions, they aren't facing the same problems as us. Perhaps one of this days Rbox bricks his AFTV, and we get a way to solve our problem..

Any news on your brick? Just had an idea, although don't know if it works, and I don't have another working fire TV. But if a backup is made on QPST from a working fire TV, and then restore that same backup on the bricked unit (using again QPST) it might restore the unit. Mmmm.. Eventually! Damn, unfortunately I don't have a good unit to backup!

walkabouts said:
Any news on your brick? Just had an idea, although don't know if it works, and I don't have another working fire TV. But if a backup is made on QPST from a working fire TV, and then restore that same backup on the bricked unit (using again QPST) it might restore the unit. Mmmm.. Eventually! Damn, unfortunately I don't have a good unit to backup!
Click to expand...
Click to collapse
Still bricked, put in box hoping later someone could find a way. Ido have a workingAFTV1, but is rooted and updated to OS5. IF you have any idea how to do this I may entertain.
jj^2

Thanks for the reply! After thinking better about my approach, its pretty much pointless, since to make a backup via QPST we have to enter in EDL mode. And there is no way to make a healthy fire TV enter service mode, not even via fastboot. My bricked fire TV is just like yours, sitting in a drawer. But I haven't given up. At least my mind is busy!

Hey guys I've tried to install https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286,
I did the steps for the locked bootloader and I didn't notice that there were errors.
It is rooted and busybox is installed. But it's stuck at the amazon logo while booting.
Do you think it's possible to unbrick it when I buy an USB-A to USB-A cable?
Version is: 51.1.5.0 30720
Thanks for your help!
Update: Ok I was able to open the stock recovery mode and it was reseting but it still won't boot.
I've waited six hours still didn't boot.

Need help
I messed up with amazon fire tv first generatio, it's now not booting up, no light nothing... when i put male-male usb cable i see its storage but that's all. adb can't find device etc.. any help will be appreciated.

Bricked 55c6us after updates attempts

Hi guys, first of all I'm sorry if is there a threat about this already. I've looked around before I started this new one.
I was having problems with Netflix rebooting my TV in the last entire month, so I downloaded myself the update in tcl Brazil website, and flashed the latest version. The problems persist, so I contacted TCL support to start procedures to have my problems solved and maybe have my TV replaced once I have one year warranty. By email the support team gave me a link to download another version of the update firmware, claiming the one I got from their website was out of date. Well, I flashed the new firmware once, factory resetet again and problems kept coming!
then I cam here in the forum and found this link support.tclelectronics.com.au/software-version
from tcl Australia, so downloaded the indicated version to my TV model 55c6us and tryed to flash it.
Well, now I'm stuck in a black screen, with no tcl boot logo, no android logo, nothing... Ive turned off and on several times holding the power button, doing all the steps to flash from USB but can't reach any boot or recover screen!
Is there a way to flash using and male to male USB cable connected to my pc? if yes, please link me. Don't know what to do =(
Thanks a lot!

had the exact same problem when trying to update to the new version. did you figured it out?

atualization: seems like the usb 3.0 port, not the service usb port now is flashing(it changed), but seems like the android OS is being built in the pendrive, by mistake. unfortunatly in the service port the firmware is not recognized anymore, i think changing the firmwere messed with a lot of things. would love if someone could help me a little. thanks

update ' i have found that i can update with .pkg files and when i do try they kind of crash but always generate some android files inside the pendrive. now i could du it on the service usb, but without video. just realized too that the tv actually turns on and enters a menu with aprox 25 options. i can hear the scroll trough the options when pressing down on the remote. but no video at all.

update ' found that the menu was the fresh installation menu, choose language and etcetera.
could configure the tv. but NO IMAGE AT ALL.
i was able to send a youtube video to the tv, the audio worked perfectly. the backlight is lit but looks like the lcd is off.
just cant figure out what did happened with the image. even in a factory reset there is no image at all. tomorrow will try t do a shop reset as last resort. if someone could help me it would be very appreciated. thank you

Hi guys, i need help with my TCL 55C6US, when the power on, it's freezes in the logo and won't do anything

gogokoko said:
Hi guys, i need help with my TCL 55C6US, when the power on, it's freezes in the logo and won't do anything
Click to expand...
Click to collapse
Semp - Download de drivers e manuais - SEMP TCL
www.semptcl.com.br

stasiof said:
Semp - Download de drivers e manuais - SEMP TCL
www.semptcl.com.br
Click to expand...
Click to collapse
Downloded it, but didn't work, message saying " no available update package. System update stopped "

gogokoko said:
Downloded it, but didn't work, message saying " no available update package. System update stopped "
Click to expand...
Click to collapse
I think must unzip and .pkg file flashed, when TV is Off.

stasiof said:
I think must unzip and .pkg file flashed, when TV is Off.
Click to expand...
Click to collapse
That what i did