Just ran into a problem which took me some time to solve. Thought I would share it to save other people some frustration.
After an adb reboot the i5800 got stuck in "modem" mode. i.e. android booted fine but gave a modem and a serial port over usb rather than adb. Reboots did not solve the problem.
The solution is to enter recovery screen:
reboot recovery
OR
press proper buttons to get into recovery mode
And then perform a reboot from there
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
miki.antena said:
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
Click to expand...
Click to collapse
Thanks so much for this!!!! After helping hack a friends build.prop to enable Apparatus compatibility in the Market, I found USB wasn't working properly anymore. Resetting changes in the phone didn't help (I had to do this via the phone terminal) although I at least managed to buy Apparatus before the sale ended.
After initially getting confused due to a lack of drivers and the occasional 'nH' showing up devices without drivers which made me think something was borked, I worked out from the VID & PID it was just the lack of drivers making (well I'm not sure why it did the 'nH' sometimes it got serial something instead), once I installed the drivers all was fine.
Except still mass storage wasn't showing and the Samsung connect manager didn't show up on my phone when I connected USB, nor did ADB work at all. In fact, it didn't even show up in the phone menu as debugging mode if I didn't start phone with it connected (or something like that). Funnily enough when I did get it the debugging to show up I did get the USB mass storage to show up in the phone, but it didn't help (it just unmounted the card which I think is all it ever does).
Anyway after a bit more fooling around I eventuall came across http://forum.xda-developers.com/showthread.php?t=1215103 and the stuff about modem and mkasick's post which sounded a lot like it could be my problem. The code for that Samsung phone didn't work so I searched for the 5800 and came across this giving me the right code. Sure enough UART (but not USB) was set to modem instead of PDA. I was unsure whether that was wrong but changed it anyway and yep that fixed it!
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times. In fact most of the stuff except install a superuser update has been more or less repeated. I guess it was just some strange rare occurence that it somehow got changed. I did have to reconnect the USB while working the first time, not sure why but ADB lost connection then I found couldn't connect. Perhaps that's somehow related. Now that I know what to do, it's trivial but very annoying when I didn't. I still don't get why Samsung decided to make the connect manager (my phone doesn't have that) only to have some hidden option where it can be set to modem or USB.
Partially because of this, I never got to get Tilestorm HD become compatible in time for the sale although my friend wasn't so interested in that. (Eventually I worked out using the THC Tattoo modded market which reports a fake resolution enables it. Well, I also modified the build.prop but I don't know if that was necessary. I wasn't able to do it solely by the build.prop. But it was way too late by then to buy Tilestorm HD cheap.)
Nil Einne said:
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times.
Click to expand...
Click to collapse
This may sound like crazy idea, but is your USB port/connector clean?
(The USB port allows for dozens of different phone functions when using very specific resistance between data pins.)
i bought a LG D802 32gb last night as i was using a 16 gb before i wanted to flash cloudy g3.. so i tried to install custome recovery twrp...
now i am in fast boot mode..
it says :
[880]fastboot mode started
[910]udc_start()
when i attach usb cable
[1100]-reset-
[1110]-portchange-
[1120]-reset-
[1130]-portchange-
[1140]-fastboot: processing commands
i tried holding volume + and and attaching the usb cable but no luck ... so now i have NO RECOVERY, NO DOWNLOAD MODE, AND MY WINDOWS PICKING UP MY PHONE AS "USB MODEM PHONE ADB PORT"
please help
A couple of weeks ago my N4 decided that it didn't want connect to my computer. I tried windows xp, 7, and osx. I tried 5 different usb cables that worked with other android phones just fine. I tried all usb ports on said computers. I've uninstalled and re-installed all drivers, using all the known methods. Then I noticed that I was getting terrible battery life. Like 5% gone in 20 minutes with all radios turned off and leaving it in my pocket. I was on the latest verison of PA with the latest verion of franco.kernel and I've had no previous problems with my phone.
So I thought maybe I did something to it like a bad flash, so i downloaded a stock 4.2.2 zip and flashed it (with gapps). The problem persisted. So I proceeded to wipe the phone in cwm in an act of desperation, and lo and behole I was then stuck with the same problem as before, but this time with no working os to boot to, and no way of connecting it to fastboot or adb in order to put any files on the sdcard/ flash it back to stock. I am, however, still able to boot into cwm and the bootloader. Then, thinking it might be a problem with the usb daughter board as whenever I tried to plug my phone into a computer it gave me this:"windows has stopped this device because it has reported problems. (code 43)", I ordered a replacement. Replacement came, I swapped them out, and absolutely nothing has changed. I tried uninstalling/deleting drivers and re-installing them just to make sure, but same results as before. Also, the N4 DOES charge when plugged into a power source like normal.
So the way I see it, I can either keep trying to replace parts, or one of you wonderful people know some crazy fix to my problem. If not, then I could go the other way, and attempt to brick the N4 even further in order to get it replaced (I.e. it's not possible to see whether or not it's unlocked/has a custom recovery). Also, I can enter "download mode" by holding down the volume buttons and connecting a usb cable, but windows still doesn't recognize the device.
It's NOT a bad cable. I'm confident it's a software issue caused by my bad idea.
THE BAD IDEA:
I tempted fate by installing AVAST on my Nook Color running CM 10.1.2 from an SD card. That was dumb. It spazzed out trying to run in the background and before I knew it the Nook in my hands went from charging (orange light) to NOT charging (green light).
I uninstalled AVAST! and shut down. The green light turned orange and resumed charging. I rebooted to CM and as soon as the bootloader activated the CM startup screen the orange light turned green again. I shut down = orange again. I removed the SD card and rebooted to stock NC 1.4.3. It continued to charge uninterrupted... orange.
More importantly, Windows 7 + Ubuntu 12.04 LTS are not recognizing the device at all.
I TRIED A FEW THINGS:
CWM restore did nothing. I tried uncheck/check menu settings options like USB connection and USB debugging aimlessly. Nothing helped.
Eventually it stopped charging during stock NC 1.4.3 operation as well.
Completely wiping EVERYTHING was not a concern for me, so I reinstalled stock 1.4.3 from the official B+N .zip archive with CWM emmc recovery mode. This didn't help.
I wiped/formatted/reinstalled CM 10.1.2 to a fresh SD card. This didn't help.
From reading threads i gather anything I try next requires ADB wireless (can't USB) but I'm out of my depth re: command line stuff.
Anything I'd do with advanced options in CWM would be stabbing in the dark.
Can anybody point me to relevant threads or offer advice?
MY DETAILS:
I made an SD card using LeapinLar's CM 10.1 guide. I successfully upgraded to CM 10.1.2 using the Cyandelta app + ClockworkRecoveryMod. Nook Color OS is stock 1.4.3
My PC OS is Windows 7. I have an Ubuntu 12.04 LTS "trial" .img on a USB stick.
Another option is a DVD boot disk running TAILS 0.19 from TorProject -- a Debian GNU/Linux based interface that runs off RAM then wipes itself clean after every reboot (maybe useful, maybe not).
(TAILS wikipedia page)
I'll try anything... at least until the battery runs out and i have to shut it down to recharge. Bleah.
verytired said:
It's NOT a bad cable. I'm confident it's a software issue caused by my bad idea.
THE BAD IDEA:
I tempted fate by installing AVAST on my Nook Color running CM 10.1.2 from an SD card. That was dumb. It spazzed out trying to run in the background and before I knew it the Nook in my hands went from charging (orange light) to NOT charging (green light).
I uninstalled AVAST! and shut down. The green light turned orange and resumed charging. I rebooted to CM and as soon as the bootloader activated the CM startup screen the orange light turned green again. I shut down = orange again. I removed the SD card and rebooted to stock NC 1.4.3. It continued to charge uninterrupted... orange.
More importantly, Windows 7 + Ubuntu 12.04 LTS are not recognizing the device at all.
I TRIED A FEW THINGS:
CWM restore did nothing. I tried uncheck/check menu settings options like USB connection and USB debugging aimlessly. Nothing helped.
Eventually it stopped charging during stock NC 1.4.3 operation as well.
Completely wiping EVERYTHING was not a concern for me, so I reinstalled stock 1.4.3 from the official B+N .zip archive with CWM emmc recovery mode. This didn't help.
I wiped/formatted/reinstalled CM 10.1.2 to a fresh SD card. This didn't help.
From reading threads i gather anything I try next requires ADB wireless (can't USB) but I'm out of my depth re: command line stuff.
Anything I'd do with advanced options in CWM would be stabbing in the dark.
Can anybody point me to relevant threads or offer advice?
MY DETAILS:
I made an SD card using LeapinLar's CM 10.1 guide. I successfully upgraded to CM 10.1.2 using the Cyandelta app + ClockworkRecoveryMod. Nook Color OS is stock 1.4.3
My PC OS is Windows 7. I have an Ubuntu 12.04 LTS "trial" .img on a USB stick.
Another option is a DVD boot disk running TAILS 0.19 from TorProject -- a Debian GNU/Linux based interface that runs off RAM then wipes itself clean after every reboot (maybe useful, maybe not).
(TAILS wikipedia page)
I'll try anything... at least until the battery runs out and i have to shut it down to recharge. Bleah.
Click to expand...
Click to collapse
Might have messed up your mac address, on the second partiton of nook holds wifi and mac address of device, if you try to find someones dump online of dev/block/mmcblk0p2 you should try to overright or edit yours to copy it, that is the only thing I can think of I had a problem similar to this awhile back reformatted and rand factory stock zip from the 3rd partition and the nooks stock recovery, after that The problem seemed to resolve itself, I am now on 10.1.2 and dont have many problems other than they took away the ability to manually mount an sdext with
echo /dev/block/mmcblk1p1 > /sys/devices/platform/usb_mass_storage/lun0/fileecho /dev/block/mmcblk1p2 > /sys/devices/platform/usb_mass_storage/lun1/file
if you try what I said and it works let me know, if not I am sorry
Hello XDA, my virtual phone heros, i appreciate your good work, i am reading here for a few years as a ghost and today i signed up because i am lost with a serious problem on my Note4 N910C (English is not my native language)
THE CONDITIONS AND ENVIRONMENT:
My Phone was first running on stock Lollipop 5.1.1 when i rooted it over ODIN 3.10.6 with space X kernel and CF Autoroot, SuperSU then i flashed the latest TWRP...
After that i flashed a Custom Rom: Sweet_ROM_V17.1_COJ2_N910C...
Everything was running flawlessly for about 2 weeks...I installed Titanium Backup, Xposed, Xprivacy Pro, Busybox and a lot more and made a complete TWRP Backup then, it was running like a charme...The backup is fine because when i messed up my phone through trying harder xprivacy parameters and other tweaking i needed to set it back by TWRP into the old state...
Nothing happened after that, it was running 100% for over a week of heavy usage...
THE PROBLEM:
The one morning i took it from the charger with 100% Battery and went to work...
Before the error occured I did some searching on the internet, used chats. movies, nothing special this day, USB Debugging was On, i remembered something messed up my chrome browser like this ad hijackers, i set it back by erasing data,cache of chrome in the app menu, then there was nothing else strange i remembered, my AF Firewall was closed, only Whatsapp and Browser were allowed to going through...
The same day in the afternoon i tried to use my car charger to recharge my Note 4 as usual, but this time it wasnt recognizing the charger and my first thought was that the charger is faulty or the cable, so i turned off the phone by the androids power menu...I retried loading my battery In the phones off state but when i plug in the charger, the battery symbol came up for short and then it remained dead, it s the same scenario until today, so i used my powerbank to try charging, because the powerbank has an indicator to show the loading state and everytime i plugged it in, it came up for short, battery symbol shows up for a few seconds, but no percentage or animation is showing as usual and no red LED, then its switching off, the powerbank LED indicator stops the loading state after a few seconds, so the loading current stops...
At home i tried the stock charger and it remained the same, since that, i have to charge the battery outside the phone...
The strange thing is:
The Rom is still booting fine, TWRP is booting, but its not going into download mode from Androids Power Menu like before, its always just rebooting back into android if i choose download mode and i have to take the battery out and back in and hit the download mode pattern Vol- Home Power, to enter Download Mode and even the booting into Download mode from TWRP gives the same strange results:
On my Laptop i started the device manager to see the USB hardware string parameters after a windows popup was telling me something like "Device not recognized"
The USB Driver ID dont fit the old right driver ID, it seems to be empty and the port is not communicating anymore
since the charging bug occured,( Everything worked fine the day before.)
I tried my Laptop to narrow down the bug with the same driver i used for flashing phones (S6,910F,910C) over ODIN and my Lappy has USB 2.0 and USB 3.0 ports.
I always used the same USB 2.0 port for ODIN and other MTP stuff, but since the bug showed up the 910C is not recognized at the USB 2.0 Port anymore, seems to be dead in the devices manager table, only the USB 3.0 Port shows it as unknown device with a strange empty ID --> I tried the other devices like the N910F and G920F that are still recognized by ODIN on the same USB2.0 and 3.0 Ports both with the same USB hardware strings, its just the N910C that isnt recognized anymore, in no mode, no ADB, MTP, no download mode, everywhere the same, USB is bricked! Windows finds no driver and says its no info avaiable on this device so I tried to force the right driver to run with the wrong buggy driver ID but its not communicating, ODIN indicator and log remains unchanged...So it seems to be the same situation like other people getting from killing the bootloader by bad flashing, the only difference is that my phone is still booting fine into recovery and even Android but with no charging. My USB Port is totally useless now, its like if Samsung or Google OTA update has overwritten my bootloader or something hidden in the rom that woke up to kill my mods i dont know and now.
PS: Things i tried so far with no results on fixing my issue....
1. Complete fresh reinstall of Sweetrom, 2. Flashing another kernel...
3. Roll back to my TWRP Backup of perfect running ROM but with no USB support anymore:
The Phone remains in unknown state, not affecting ODIN to switch into flash mode
I am sure its the bootloader, since its battery bug is still occuring while the phone is in off state...
Unable to tell the charger the right ID without USB communication...
i was wondering if there is a solution to make a bootloader hotflash from out of Android or something like getting me back on stock first with download mode, forcing the USB ID or communication with a tool out of android, SD card boot image like on note 3 whatever, please tell me! I cant find something related to my USB and Charging ISSUE
PLEASE HELP ME, I am lost
Still the same. It's booting fine, USB2.0 no reaction on the laptop in Fastboot/Adb/Mtp ... On USB 3.0 Device remains unknown with strange Device ID String in windows 10 hardware Manager... Forced the old formerly working driver, but Odin can't find it anymore... Adb, Mtp, fastboot don't work, no communication... USB Cid is hard bricked, Charging never works in no state, just showing up for a few seconds in off state while plugging it in for short.... Bootloader must be damaged, fastboot and twrp can be started with dead USB... So is there a way to run a boot image to fix my bootloader from SD card, Aroma, or like OTA Updates are flashing? If Samsung and Google apply bootloader updates over OTA and simply restart, why we can't do that??? I need a new bootloader, is there any way without USB?
Greetings,
Thank you for using XDA Assist.
I have moved your question to your device's Q&A forum. You'll receive expert advice here. Good luck!
Fixed!
The problem is the USB Connector Port itself, figured it out after bending the inner contacts up with a flat screwdriver and cleaned them. Before that i always tried the same gently with no change, but please do it at your own risk only. After searching for many hours about possible reasons for the problem, I came to the conclusion to even compromise the Port and heavy bending it up, now it's charging! I will exchange the port soon and change the frame too to have it back like as new... OK, if anyone in the future have problems with the bootloader or USB hardbrick n910c, feel free to ask me, I upgraded my knowledge on many causes now
Thank you very much
My 2cents stick to one charger. Do not share that charger with others.
The worst culprit are the cheap china car chargers.
I went thru two USB ports on my first phone to figure this out.
Ever since I have adopted the policy of using only one cable. Never had this issue.
So yesterday I installed TWRP alongside CM13.
After that I got some problems with the ROM (rebooting, slow charging) so I decided to return to stock. To flash the stock .kdz I needed to go into download mode, that however did not work my phone just booted normally into CM when I tried to use the method to get into download mode (vol+ & USB). I even tried to force download mode through adb on PC however that also only rebooted the phone.
Then I did a wipe in TWRP (everything except Internal Storage) and shut off the phone.
Now I have the problem that I can not boot (because I obviously have no ROM installed anymore) but I also can't get into recovery anymore.
Also my phone seems to be in "only charge" mode from CM so my PC does not even recognize it correctly. I can't even see it in device manager and neither adb, nor the flash tool nor anything recognizes it.
When I connect my phone to the PC it just shows the CM battery icon that you see when you charge your phone while it's turned off and the LED is glowing yellow.
All of this are things that were new with CM so I guess there is still something left from CM that does prevent my G2 from acting as MTP.
Please tell me there is still hope...