Sent from my HTC Wildfire using XDA App-put out a post about half hour ago but I never stated my problems...got sim free,unlocked sgs I bricked it I could only d/load via jig,so I flashed it using odin but I must've done it wrong as I got no network connection, incoming + outgoing wasn't viable,I tried flashing it again (infinity),then it bricked again,as of now my galaxy is "dead",if any 1 can help me it would b appreciated,I do not have much knowledge apart from basics so please don't be smart as I am only asking for help here,oh I have to use a jig as I can't get 3 button mode,also I formatted my internal + external memory (8gb + 16gb)....that was the last advice I got + think this Is where my problem started from?thank you....
pmb6177 said:
Sent from my HTC Wildfire using XDA App-put out a post about half hour ago but I never stated my problems...got sim free,unlocked sgs I bricked it I could only d/load via jig,so I flashed it using odin but I must've done it wrong as I got no network connection, incoming + outgoing wasn't viable,I tried flashing it again (infinity),then it bricked again,as of now my galaxy is "dead",if any 1 can help me it would b appreciated,I do not have much knowledge apart from basics so please don't be smart as I am only asking for help here,oh I have to use a jig as I can't get 3 button mode,also I formatted my internal + external memory (8gb + 16gb)....that was the last advice I got + think this Is where my problem started from?thank you....
Click to expand...
Click to collapse
OK so if you can get into download? If you can then its a matter of getting Odin to see the phone - which really means getting windows to recognize the phone. This would mean that odin does not light up in one of the com ports.
If this assumption is right, make you have the latest drivers (see other posts - I had a link in another post so if you look for my posts you'll find it), reinstall kies (but do not have it open), clean the usb port/cable on the phone and computer with alcohol just to be sure (that was my old issue and it takes forever to troubleshoot), then put into download with jig (I assume you start with a battery pull?). If you've done the kies/drivers thing (good chance if your asking on this forum - just try the cleaning).
You can also try various different usb ports - the theory is the one at the back of a desktop work best but my laptop ones seem fine (now - see cleaning above).
I know this is not that step by step it sounds like your trouble is the connection not the steps as you have already attepted the flash.
If still not working , try to vary the connect order (odin first, then connect or reverse etc).
From there follow a good odin guide and flash a full stock firmware to start (presumably your official one).
I believe you are only truly dead when you cannot get to download mode.
Good luck!
Thank you for taking the time to send that post ; one last thing ... any thoughts on getting my sgs to "day 1" , like before all the trouble I was stock eclair 2.1,Vodafone,blah,blah ; how do I get back after formatting both my internal + external , I'm presuming I've erased my stock FW?
Sent from my HTC Wildfire using XDA App
I think you also got similar advice to mine on another post. Don't worry about going to day 1 with eclair. If you flash a stock froyo firmware with odin you'll have a phone like it came out yesterday. Now, it will also likely be unrooted and maybe locked (I'm not unlocked so I'm not sure about that part).
So once you get to the stock firmware you'll need to root again and maybe unlock (stock is stock after all). You may want to just try Darky's resurection rom (for Odin use)
, link here, which should make your phone faster and keep you rooted and unlocked.
If you don't care about root etc, then I think stock is fine as long as it doesn't lock the phone to another provider (use the search function in the forums). One warning is once you know how to change things (and recover) you might spend hours trying to play with the custom roms just because you can .
Good luck in the AM
I have a droid 4 that ended up with bad software. Simple issue is I got no bootloader, no power, no nada. When I connect a regular USB i get a green light in the corner but no activity and no detect. Needless to say, bootloader is corrupt at this point. Sent it back to Moto Repair and they claim physical damage (though I know for a fact there is none) so I'm looking to Flash the bootloader myself. I'm aware it's going to have to be a low level NAND flash. Anyone familiar with this process? Computer does not detect. Does anyone have the latest A.074 Bootloader file I can grab? Need to get this guy running. Any help would be greatly appreciated.
Thanks
Oh, and yes I have a factory programming cable if I can make use of it somehow......
queberican351 said:
I have a droid 4 that ended up with bad software. Simple issue is I got no bootloader, no power, no nada. When I connect a regular USB i get a green light in the corner but no activity and no detect. Needless to say, bootloader is corrupt at this point. Sent it back to Moto Repair and they claim physical damage (though I know for a fact there is none) so I'm looking to Flash the bootloader myself. I'm aware it's going to have to be a low level NAND flash. Anyone familiar with this process? Computer does not detect. Does anyone have the latest A.074 Bootloader file I can grab? Need to get this guy running. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
How did the bootloader get corrupted? I was under the impression the phone would not allow you to flash another bootloader unless it was signed... You should ask Moto what was physically damaged, if it was a simple flash they should be able to fix it easily for you.
NEED DD
That was my thoughts exactly. But they claim liquid damage. I've since then opened the phone and inspected all the stickers....no sign of liquid damage. I would think a 2 minute bootloader flash wouldn't constitute this much despair (on Motorola's part) but such is life. Now I'm just looking to get the first couple Mb in a device dump so I can write it to an sdcard and attempt to boot from there and repair the bootloader. It has to be a device dump from a D4 running the a.074 bootloader. Any takers?
You could try looking in the fastboot files, they're on the Droid 4 development boards, they have both Gingerbread ones
D4 6.16.215 MBM files
Here are the D4 6.16.215 mbm.bin and other low level boot files from the leaked OTA update.zip.
I don't think they are going to help you given that there is no way that I am aware of to boot from the sdcard on a Motorola device.
There is a USB boot option for loading a factory I/O image(pre firmware basic input/output interface), but I don't know how you would initialize it nor do I have the factory image for the D4.
It is most likely a touchpoint on the board that needs to be shorted while the factory cable is inserted and that would bypass the EMMC and initialize the USB boot.
I am just guessing here...good luck!
if you somehow unlock it too, let us know what you did
SD Card boot didn't work and couldn't get it to detect on my windows or linux pc's. Therefore OMAPboot was out of the question. So I parted it out. I've acquired another D4 and I'm curious as to what if any advancements have been made on getting them to work on US GSM carriers? If we're still stuck I'm more than willing to jump into Dev on this and open to suggestions. My new D4 is running bone stock GB. I'm going to keep looking into the SD or USB possible fix's for hardbricks.
Thanx for the replies and thanx to [mbm], Jonpry, PhareignQ (think I mightta spelled that wrong), and HashCode for their knowledge, help, and suggestions along the way.
Hey man! You're the second one with same issue. I'm looking to buy new motherboard for droid 4 with same crapped bootloader + broken cdrom partition
For those who is interesting in, motorola factory cable doesn't work with droid 4 for some strange reason.
I can attest to the fact that the factory cable does, indeed, work with the D4 just like the Razr and other Motorola models.
I am not sure why yours doesn't or what condition your phone is in at this point, but the factory cable will power the device directly, bypassing the battery/charging circuit and allow you to flash it as long as the bootloader and mbmloader are not corrupt.
In that case, when the mbmloader fails, then nothing happens on the device at all unless a factory cable is connected, then it will flash the LED white just once as the cable is inserted and then loop continuously trying to load an interface and fails. The screen does nothing and the device is dead except pressing all 3 hardware buttons will arrest then restart the cycle of failed interface initialization once released.
I have a Razr in this state that I unfortunately attempted to flash some unknown files we received that we foolishly believed may have been an OEM bootloader unlock.
If you flash a corrupt image to the mbmloader the device is toast, AFAIK, although I do believe they have ways to recover them and in the past those methods often involved shorting a set of pads on the board with a paperclip while inserting the factory cable, initializing a timed event where the EMMC was bypassed and and factory I/O file could be loaded via a USB boot option.
I don't know if any of these methods could actually save any of our phones in this state, but I would like to believe its possible!
I just wanted to clarify about the factory cable.
Yup, what @Cellzealot said. I've removed the battery from the D4 and the factory cable works as intended. To be frank I had a moment of ignorance. I had just gotten my D4 (used) and was attempting to try and find a solution for the US GSM band unlock. In reading through the post about the Bionic I found that there was alot of talk about needing to be on bootloader 0A.72 or something to the fact of having success with that. The kid I got it from had already installed the ICS leak. So I paid no attention to the fact that the bootloader on MY phone was 0A.74....so I opened RSD and attempted to send mbm and mbmloader from 0A.72. It failed and that was the last thing ever "sent" to that phone. As soon as I disconnected it the phone powered down and never did anything after that.......
So I pursued the Boot from SD theory to no success, though I believe it is plausible, however probably still required a short to enable it. And Linux and Windows wouldn't even detect the OMAP4430 (as I've heard some people had luck with). So OMAPboot (boot from usb) was out too.
Finally got another D4, and being the phone soldier I try to be, Went right back to town attempting to get this thing to run on AT&T. So far no luck. I've been trying radio's and rom's from different devices and brandings that are running 2.3.6 (I left this one on the stock Gingerbread)
Willing to undertake any suggestions as long as "bootloader" is nowhere in the equation,
queberican351 said:
Yup, what @Cellzealot said. I've removed the battery from the D4 and the factory cable works as intended. To be frank I had a moment of ignorance. I had just gotten my D4 (used) and was attempting to try and find a solution for the US GSM band unlock. In reading through the post about the Bionic I found that there was alot of talk about needing to be on bootloader 0A.72 or something to the fact of having success with that. The kid I got it from had already installed the ICS leak. So I paid no attention to the fact that the bootloader on MY phone was 0A.74....so I opened RSD and attempted to send mbm and mbmloader from 0A.72. It failed and that was the last thing ever "sent" to that phone. As soon as I disconnected it the phone powered down and never did anything after that.......
So I pursued the Boot from SD theory to no success, though I believe it is plausible, however probably still required a short to enable it. And Linux and Windows wouldn't even detect the OMAP4430 (as I've heard some people had luck with). So OMAPboot (boot from usb) was out too.
Finally got another D4, and being the phone soldier I try to be, Went right back to town attempting to get this thing to run on AT&T. So far no luck. I've been trying radio's and rom's from different devices and brandings that are running 2.3.6 (I left this one on the stock Gingerbread)
Willing to undertake any suggestions as long as "bootloader" is nowhere in the equation,
Click to expand...
Click to collapse
Any solution on black screen and broken bootloader?
Here I have black screen with AC adapter connected. If I connect the phone to PC, I have green led indicator, but still black screen. Buttons have no reactions.
Anything new? Two users on a German bulletin board do have the same issue. I will get one Droid 4 of them in the next few days to have a look at it. But this thread sounds like there is no solution?
http://db.tt/u31VG45D
http://forum.xda-developers.com/showthread.php?t=2055839
The first link is to the most recent level 4 bootloader repair kit that we have for the Maserati/Droid 4 which is 0a.6c from pre ICS builds.
It is possible you may be able to use the pbrdl.bin and brdl.bin from those files with the mbmloader.bin and mbm.bin from a more current build to restore your device.
Again, these files are a year old now and may not work but you have little to lose in trying.
Use the method in the second link in Linux to try to restore your bootloader with the omapflash-lnx binary from that thread.
This is very likely to fail if the device has a recent firmware build on it but we don't have any of these repair kits for the newer bootloaders.
Good luck!
Thanks.
I got one of these phones. But it isn't even recognized via USB So I can't use these tools...
Is there any way to flash it via JTAG/ISP/...? Maybe this is the last chance - or this phone is dead ^^
I-896, from the start USB was working in Lo-Speed mode when data transferring (1 Mb/s speed). I was too stupid to format /system from CWM and then reboot to Download mode which wasn't working (USB Device attached not recognized, blind ODIN and Kies). Can I somehow flash stock ROM? Is this an phone's MicroUSB-Female issue or deep hardware's one(processor, PCB)? Here are some photos of me trying to connect USB directly:
Did u see this sticky thread about Captivate - PC Connection Issues, etc? ...http://forum.xda-developers.com/showthread.php?p=33227541
Did u try a Jig to get into Download mode ?? Here is a thead on how to make a Jig...http://forum.xda-developers.com/showthread.php?p=9238587
Sent from my SAMSUNG-SGH-I747 using xda premium
Yes, I've seen this thread (and many others too, done a small research for about 1 hour). Tried all the solutions from the threads. My phone easily switches to Download mode, but it isn't recognized by PC. And it's not a driver/cable problem because my second Captivate works properly.
To be more concrete: code 43 in Device Manager, Device not recognized in tray.
since you've got the phone opened up, clean the micro usb connector and check resistance of each connector contact to test point on board. then check resistance between pins. if 2 and 3 are shorted, power chip wont pass data to phone.
also, if you enabled fast usb charging in kernel, that would be problem.
you want battery out, good contact cleaner. get completely dry and clean before applying power.
Have never using Fast Charging (only GB ROMs and kernels), bought a new captivate with broken screen, now trying to get the phone working.
Why isn't power chip allowing to pass data to phone? I haven't normal multimeter at the moment. Can you advise me how to flash Captivate w/o USB? Is there a way? And, maybe, this bug appeared because my Captivate was from Rogers, not the I-897 one?
Redhattler said:
Have never using Fast Charging (only GB ROMs and kernels), bought a new captivate with broken screen, now trying to get the phone working.
Why isn't power chip allowing to pass data to phone? I haven't normal multimeter at the moment. Can you advise me how to flash Captivate w/o USB? Is there a way? And, maybe, this bug appeared because my Captivate was from Rogers, not the I-897 one?
Click to expand...
Click to collapse
Well as far as I know, the Rogers one is an international phone, which is the i9000 not i879 (not 100% sure, correct me if I'm wrong) so that could have a lot to do with it.
As for flashing w/o usb, if you have an external SD card the phone can read yes it's possible but it's not advisable because you can completely screw yourself like I did . My phone currently won't boot besides Download Mode, Recovery Mode, and the bootscreen but since I don't have USB data connectivity I can't fix the phone (when I flashed speedmod kernel, everything went fine. But it doesn't read my external, so I can't flash my phone to fix it).
If you do choose to flash without a USB, please for the love of everything holy, MAKE SURE YOU ALSO PUT THE ROM .ZIP ON THE INTERNAL SD AS WELL
Redhattler said:
Have never using Fast Charging (only GB ROMs and kernels), bought a new captivate with broken screen, now trying to get the phone working.
Why isn't power chip allowing to pass data to phone? I haven't normal multimeter at the moment. Can you advise me how to flash Captivate w/o USB? Is there a way? And, maybe, this bug appeared because my Captivate was from Rogers, not the I-897 one?
Click to expand...
Click to collapse
x0ne215 said:
Well as far as I know, the Rogers one is an international phone, which is the i9000 not i879 (not 100% sure, correct me if I'm wrong) so that could have a lot to do with it.
As for flashing w/o usb, if you have an external SD card the phone can read yes it's possible but it's not advisable because you can completely screw yourself like I did . My phone currently won't boot besides Download Mode, Recovery Mode, and the bootscreen but since I don't have USB data connectivity I can't fix the phone (when I flashed speedmod kernel, everything went fine. But it doesn't read my external, so I can't flash my phone to fix it).
If you do choose to flash without a USB, please for the love of everything holy, MAKE SURE YOU ALSO PUT THE ROM .ZIP ON THE INTERNAL SD AS WELL
Click to expand...
Click to collapse
Actually the Rogers version is i896 and the other is i897. To my understanding the hardware is identical and shouldn't be a problem using stuff for the 897 with the 896.
Yes, I have now tested all the parts compatibility between I-896, I-897 motherboards and camera, part with cardreader, speaker, vibrator and sim-reader. All works properly.
How can I flash the ROM using my external SD card? I can't access it through CWM (can't even mount, I think mount binary was formatted with the /system partition). Is there a guide?
How can I flash the ROM using my external SD card? I can't access it through CWM (can't even mount, I think mount binary was formatted with the /system partition). Is there a guide?
Click to expand...
Click to collapse
I can't access it either, hence why my phone is bricked :\.
If you have no access to the internal SD, you're in the same boat as me lol. If you know for a FACT that the usb port is damaged, there's a website that will repair it for you for about $35. However, you can usually get a used cappy from ebay for around $80-$100, so if there's more issues might as well just buy a new one and use the current for spare parts.
EDIT: Excuse my last post, I forgot you had already not been able to use the phone to access the internal SD. Long day at work
Just bought I-897 with a broken screen for 33 USD. I'm wondering if I can flash my old PCB someway, even if I'll need to find a hardware tool for this. Will try checking USB port's resistance, especially 2, 3 pins as was mentioned above.
MicroUSB consists of 5 pins, and the place where USB-F port is connected to PCB has 7 (as can be seen on photo). Where can I find a pinout for this one?
Hi there.
I recently (2 days ago) ran into issues with my 17 months old Htc One M7. The issue was something a bit different and unusual: First thing was that charging stopped working somewhere between the charge itselt. I noticed that I got reports that "Charging is disabled in USB host mode", even without any cable inserted into micro USB connector. Next thing that was really annoying was that the screen suddenly got orientation changes available even for calls and desktop, including on-the-head rotation (180°), basically it could go in any of the 4 orientations. The most anoying thing however was, the speaker was automatically turned on when call started.
At that time, I still had installed app Dayframe, which supports to run at Car mode, so all I noticed along with the upper issues was the prompt to "Choose which app you want to use to run" dialog every now and then.
After removing Dayframe, stock app started automatically, so I finally knew what was it - it was the CAR MODE!!! -.-
So, this explained a bit where the issue could be, and unfortunatelly, I can confirm that it's my worst fear: the usb connector has gone bad!
Since kernel doesn't support usb charging in otg mode, I couldn't charge my phone anymore - unless it was turned off. So wsaid, It detects otg / car mode randomly - mot of the time, so I ahave quite a big issue hereh
The big problem though is that I have had my phone rooted last year, using TWRP recovery (still have S-ON and stock rom 4.3, all I've done was gain root access in order to run some apps that needed it. Never tweaked the ROM itself...) . Now, since TWRP supports OTG mode, I can't connect my phone to the computer in any way, as, again, the usb connection is dropped as soon as I get into recovery.
One more issue at the moment is that I did the wipe all command, and haven't noticed that I marked "system" as well, so I currently don't have any OS installed at all^^.
Anyway, 3 big questions at the moment are:
1) Is there any way to get TWRP recovery or any other recovery with OTG disabled, so that I could connect it to the computer in order to proceed with unrooting before I send it for repair? I'm willing to donate/pay to someone to mod the TWRP(or any other) and recompile it for me, if that's an option...
2) Is it even possible to install another recovery from the current one, since I can't do ADB...?
Note: I still can get files onto the phone right now (ironic: thanks to the OTG) via my microUSB stick, so I can read zips. The question is, if the install is even possible at all...?
3) Is there any other way / what's your suggestion to do in my case???
I did check the usb connector from the outside and cleared it with a needle and compression, and don't see any corrosion, so have no idea how/why this happened....
Any help is more than appreciated!!
Put TWRP or other recovery img file in internal memory flash it with flash image gui app root needed
yatindroid said:
Put TWRP img file in internal memory flash it with flash image gui app root needed
Click to expand...
Click to collapse
Sorry, but your post makes no sense. First: I already gave TWRP. Second: I don't have OS installed anymore. Third: How would your suggestion help with my case? I'm afraid you misunderstood my problem... :/
cucolino said:
Hi there.
I recently (2 days ago) ran into issues with my 17 months old Htc One M7. The issue was something a bit different and unusual: First thing was that charging stopped working somewhere between the charge itselt. I noticed that I got reports that "Charging is disabled in USB host mode", even without any cable inserted into micro USB connector. Next thing that was really annoying was that the screen suddenly got orientation changes available even for calls and desktop, including on-the-head rotation (180°), basically it could go in any of the 4 orientations. The most anoying thing however was, the speaker was automatically turned on when call started.
At that time, I still had installed app Dayframe, which supports to run at Car mode, so all I noticed along with the upper issues was the prompt to "Choose which app you want to use to run" dialog every now and then.
After removing Dayframe, stock app started automatically, so I finally knew what was it - it was the CAR MODE!!! -.-
So, this explained a bit where the issue could be, and unfortunatelly, I can confirm that it's my worst fear: the usb connector has gone bad!
Since kernel doesn't support usb charging in otg mode, I couldn't charge my phone anymore - unless it was turned off. So wsaid, It detects otg / car mode randomly - mot of the time, so I ahave quite a big issue hereh
The big problem though is that I have had my phone rooted last year, using TWRP recovery (still have S-ON and stock rom 4.3, all I've done was gain root access in order to run some apps that needed it. Never tweaked the ROM itself...) . Now, since TWRP supports OTG mode, I can't connect my phone to the computer in any way, as, again, the usb connection is dropped as soon as I get into recovery.
One more issue at the moment is that I did the wipe all command, and haven't noticed that I marked "system" as well, so I currently don't have any OS installed at all^^.
Anyway, 3 big questions at the moment are:
1) Is there any way to get TWRP recovery or any other recovery with OTG disabled, so that I could connect it to the computer in order to proceed with unrooting before I send it for repair? I'm willing to donate/pay to someone to mod the TWRP(or any other) and recompile it for me, if that's an option...
2) Is it even possible to install another recovery from the current one, since I can't do ADB...?
Note: I still can get files onto the phone right now (ironic: thanks to the OTG) via my microUSB stick, so I can read zips. The question is, if the install is even possible at all...?
3) Is there any other way / what's your suggestion to do in my case???
I did check the usb connector from the outside and cleared it with a needle and compression, and don't see any corrosion, so have no idea how/why this happened....
Any help is more than appreciated!!
Click to expand...
Click to collapse
quite a long post, but I justy have a couple of questions for you, first of all, which version of twrp are you using ?
when your phone is in the bootloader and plugged into the computer, does it say fastbootUSB on the screen or something like fastboot host, are you still able to issue fastboot commands ?
when the phone is in recovery and you plug into the computer, check device manager, see if you can see the phone in their anywhere, ive noticed a lot of people loosing the device in recovery lately, me for one, if it says one with a yellow exclamation mark in device manager then you need to force the driver.
Seanie280672 said:
quite a long post, but I justy have a couple of questions for you, first of all, which version of twrp are you using ?
when your phone is in the bootloader and plugged into the computer, does it say fastbootUSB on the screen or something like fastboot host, are you still able to issue fastboot commands ?
when the phone is in recovery and you plug into the computer, check device manager, see if you can see the phone in their anywhere, ive noticed a lot of people loosing the device in recovery lately, me for one, if it says one with a yellow exclamation mark in device manager then you need to force the driver.
Click to expand...
Click to collapse
Thank you for your reply. Yeah, I have this thing for writting too much :/
I'm using twrp 2.6.3.0 if I read the version correctly.
When the phone is in the bootloader and plugged into the computer, it says nothing. Same as if I pull the cable out. The computer doesn't even recognize it. Sometimes I can hear the sound of new device connected, but only for a second or so., and this only happens during entering the recovery, not in the bootloader...
With ADB or Fastboot tool, I get no devices connected anytime I try to list them....
Unfortunatelly for me, here it's not the driver issue itself. It used to work with no issues - note that I have the same PC as I used for rooting it in the first place...
cucolino said:
Thank you for your reply. Yeah, I have this thing for writting too much :/
I'm using twrp 2.6.3.0 if I read the version correctly.
When the phone is in the bootloader and plugged into the computer, it says nothing. Same as if I pull the cable out. The computer doesn't even recognize it. Sometimes I can hear the sound of new device connected, but only for a second or so., and this only happens during entering the recovery, not in the bootloader...
With ADB or Fastboot tool, I get no devices connected anytime I try to list them....
Unfortunatelly for me, here it's not the driver issue itself. It used to work with no issues - note that I have the same PC as I used for rooting it in the first place...
Click to expand...
Click to collapse
but then you say the USB otg cable is working from within recovery ?
your recovery is a bit too old for flashing a rom, you really need 2.6.3.3, have you tried a different cable ?
I have seen this issue before, it was an option in a kernel that someone selected by mistake but for a different device, a HTC One SV, just going back 2 years so I cant remember the cure, however as you say your device is seeing the OTG cable and still charging even though it requires you to power off to do it, id say the USB port is fine, you could try flashing a custom rom which will replace the kernel on their now.
Seanie280672 said:
but then you say the USB otg cable is working from within recovery ?
your recovery is a bit too old for flashing a rom, you really need 2.6.3.3, have you tried a different cable ?
I have seen this issue before, it was an option in a kernel that someone selected by mistake but for a different device, a HTC One SV, just going back 2 years so I cant remember the cure, however as you say your device is seeing the OTG cable and still charging even though it requires you to power off to do it, id say the USB port is fine, you could try flashing a custom rom which will replace the kernel on their now.
Click to expand...
Click to collapse
Yes. I can see the OTG partition in the recovery present...
Tried a few cables, even took a brand new one out of the packet. It's not the cable issue...
But I can't understand how would I "select an option" in the kernel. Note, that I had stock ROM 4.3 with Sense 5.5, only root access gained, and have this firmware for over a year on now. Not a single app was installed/uninstalled within the last month, nor updated (I do all updates manually, and mostly don't except if I need them...), and this started to happen all of a sudden, out of nowhere.
I've read that someone had this issue (Found only one single thread about similar issue on some other forum, with no further info provided, but the guy described the exact same issues that I have), and that after taking it to the Sprint service, his warranty was revoked as they found corrosion on the usb connector...
Also, if I move a little bit up/down/left/right the cable, every 100 try I did lose the sign of the OTG host present in the system, but as soon as I released it, or took the cable back out, the message reappeared in the notification dialog...
Also, from what I know about OTG, I don't really see if you could be correct with the "usb port is fine" based on the fact that it does see OTG and charge. Note that the only difference between having otg and not having otg is linking the fifth (5th) pin to the ground.
By that, the system detects it as OTG host port instead of regular USB port, and switches charging off (as it redirects the current draw from inputing to outputing into the otg device, my guess is this is to avoid possible drawbacks and to control the actual current that the phone is outputing - otherwise you could damage the battery,...? ), , as well as turns the data pins to read OTG device instead present the phone itself as the device.
From that perspective, I believe that if the usb port is defective in such a way that it triggers the OTG, the charging will work only in powered off mode (as it does), and when powered on disable it as it "sees" otg device...
Do you have different info about OTG and disagree at any point with me? (I'd actually be glad to hear you do, if you do... )
The fact is that currently I can't do anything with the PC, as I can't see the phone at all. So, if my recovery is too old to flash rom, can I reflash new recovery from the current one, or do I explicitly need fastboot / adb for doing so?
cucolino said:
Yes. I can see the OTG partition in the recovery present...
Tried a few cables, even took a brand new one out of the packet. It's not the cable issue...
But I can't understand how would I "select an option" in the kernel. Note, that I had stock ROM 4.3 with Sense 5.5, only root access gained, and have this firmware for over a year on now. Not a single app was installed/uninstalled within the last month, nor updated (I do all updates manually, and mostly don't except if I need them...), and this started to happen all of a sudden, out of nowhere.
I've read that someone had this issue (Found only one single thread about similar issue on some other forum, with no further info provided, but the guy described the exact same issues that I have), and that after taking it to the Sprint service, his warranty was revoked as they found corrosion on the usb connector...
Also, if I move a little bit up/down/left/right the cable, every 100 try I did lose the sign of the OTG host present in the system, but as soon as I released it, or took the cable back out, the message reappeared in the notification dialog...
Also, from what I know about OTG, I don't really see if you could be correct with the "usb port is fine" based on the fact that it does see OTG and charge. Note that the only difference between having otg and not having otg is linking the fifth (5th) pin to the ground.
By that, the system detects it as OTG host port instead of regular USB port, and switches charging off (as it redirects the current draw from inputing to outputing into the otg device, my guess is this is to avoid possible drawbacks and to control the actual current that the phone is outputing - otherwise you could damage the battery,...? ), , as well as turns the data pins to read OTG device instead present the phone itself as the device.
From that perspective, I believe that if the usb port is defective in such a way that it triggers the OTG, the charging will work only in powered off mode (as it does), and when powered on disable it as it "sees" otg device...
Do you have different info about OTG and disagree at any point with me? (I'd actually be glad to hear you do, if you do... )
The fact is that currently I can't do anything with the PC, as I can't see the phone at all. So, if my recovery is too old to flash rom, can I reflash new recovery from the current one, or do I explicitly need fastboot / adb for doing so?
Click to expand...
Click to collapse
Is your phone Sprint ? 2.6.3.0 was very popular on Sprint.
their are still old roms you can flash with that recovery look for insertcoin-m7-5.0-3 it will work on Sprint
cucolino said:
Yes. I can see the OTG partition in the recovery present...
Tried a few cables, even took a brand new one out of the packet. It's not the cable issue...
But I can't understand how would I "select an option" in the kernel. Note, that I had stock ROM 4.3 with Sense 5.5, only root access gained, and have this firmware for over a year on now. Not a single app was installed/uninstalled within the last month, nor updated (I do all updates manually, and mostly don't except if I need them...), and this started to happen all of a sudden, out of nowhere.
I've read that someone had this issue (Found only one single thread about similar issue on some other forum, with no further info provided, but the guy described the exact same issues that I have), and that after taking it to the Sprint service, his warranty was revoked as they found corrosion on the usb connector...
Also, if I move a little bit up/down/left/right the cable, every 100 try I did lose the sign of the OTG host present in the system, but as soon as I released it, or took the cable back out, the message reappeared in the notification dialog...
Also, from what I know about OTG, I don't really see if you could be correct with the "usb port is fine" based on the fact that it does see OTG and charge. Note that the only difference between having otg and not having otg is linking the fifth (5th) pin to the ground.
By that, the system detects it as OTG host port instead of regular USB port, and switches charging off (as it redirects the current draw from inputing to outputing into the otg device, my guess is this is to avoid possible drawbacks and to control the actual current that the phone is outputing - otherwise you could damage the battery,...? ), , as well as turns the data pins to read OTG device instead present the phone itself as the device.
From that perspective, I believe that if the usb port is defective in such a way that it triggers the OTG, the charging will work only in powered off mode (as it does), and when powered on disable it as it "sees" otg device...
Do you have different info about OTG and disagree at any point with me? (I'd actually be glad to hear you do, if you do... )
The fact is that currently I can't do anything with the PC, as I can't see the phone at all. So, if my recovery is too old to flash rom, can I reflash new recovery from the current one, or do I explicitly need fastboot / adb for doing so?
Click to expand...
Click to collapse
you could of flashed a new recovery if you still had a rom on your phone, all I can suggest is that you try and flash an old'ish rom now from your OTG and current recovery.
The reason I think it was the kernel is because of all the strange orientation changes you were getting and the USB host problems, maybe an app messed it up or its just got corrupt or something, the rom has gotta be worth a try.
clsA said:
Is your phone Sprint ? 2.6.3.0 was very popular on Sprint.
their are still old roms you can flash with that recovery look for insertcoin-m7-5.0-3 it will work on Sprint
Click to expand...
Click to collapse
No. Its Unlocked, if Im not mistaken. (Bought in Central EU, no carrier locked, not Google Play edition,.... ?)
I should go and find an old rom somewhere, I'm sure its there on the net. But what do I gain with it anyway? If its kernel issue for sure, does the rom flash (stock one) reinstall the kernel as well..?
Seanie280672 said:
you could of flashed a new recovery if you still had a rom on your phone, all I can suggest is that you try and flash an old'ish rom now from your OTG and current recovery.
The reason I think it was the kernel is because of all the strange orientation changes you were getting and the USB host problems, maybe an app messed it up or its just got corrupt or something, the rom has gotta be worth a try.
Click to expand...
Click to collapse
Still though, if I don't get the usb connection back, I guess theres no way to remove the flags and put it back on S-On for repairas, is it...?
Well, I assumed that the orientation "issues" were enabled since the Car dock mode supports that. Was I wrong on this one..?
Note: Only 2 apps on my phone had SU access. File browser (ES file manager), and MyBackupPro. So only these two were actually able to mess with the kernel, if I'm not mistaken..?
cucolino said:
No. Its Unlocked, if Im not mistaken. (Bought in Central EU, no carrier locked, not Google Play edition,.... ?)
I should go and find an old rom somewhere, I'm sure its there on the net. But what do I gain with it anyway? If its kernel issue for sure, does the rom flash (stock one) reinstall the kernel as well..?
Still though, if I don't get the usb connection back, I guess theres no way to remove the flags and put it back on S-On for repairas, is it...?
Well, I assumed that the orientation "issues" were enabled since the Car dock mode supports that. Was I wrong on this one..?
Note: Only 2 apps on my phone had SU access. File browser (ES file manager), and MyBackupPro. So only these two were actually able to mess with the kernel, if I'm not mistaken..?
Click to expand...
Click to collapse
yes the Rom will fix the kernel
whats the top line in your bootloader M7_U / M7_UL / M7wls
your old roms are here >> http://insertcoin-roms.org/category/devices/one_m7/one_sense5/page/3/
clsA said:
yes the Rom will fix the kernel
whats the top line in your bootloader M7_U / M7_UL / M7wls
Click to expand...
Click to collapse
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMC-boot 2048MB
Oct 17 2013, 23:06:14.0 (Interesting date... and its always the same time.. -> I rooted the phone in Nov 2013, if I remember correctly...)
cucolino said:
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMC-boot 2048MB
Oct 17 2013, 23:06:14.0 (Interesting date... and its always the same time.. -> I rooted the phone in Nov 2013, if I remember correctly...)
Click to expand...
Click to collapse
the roms in the link i posted will work fine on your phone IC 5.x = OS 3.x.401
clsA said:
the roms in the link i posted will work fine on your phone IC 5.x = OS 3.x.401
Click to expand...
Click to collapse
Thank you for that.
Downloaded, tried to install... seems like I have a bit of a more serious problem. Can't get to read the OTG drive anymore. Still shows as that some device is mounted, but the USB is not being recognized (tried 2 different, one directly OTG stick, and one via OTG cable..).
Looks like I'm totally f***ed.... :S
cucolino said:
Thank you for that.
Downloaded, tried to install... seems like I have a bit of a more serious problem. Can't get to read the OTG drive anymore. Still shows as that some device is mounted, but the USB is not being recognized (tried 2 different, one directly OTG stick, and one via OTG cable..).
Looks like I'm totally f***ed.... :S
Click to expand...
Click to collapse
Just a quick question, you said your phone was 17 months old, do you still have a warranty? I thought HTC's warranty was only valid for 1 year...
alray said:
Just a quick question, you said your phone was 17 months old, do you still have a warranty? I thought HTC's warranty was only valid for 1 year...
Click to expand...
Click to collapse
yep. theoreticallyninstill do. including the battery (since its integrated).
i dont know for foreign countries, at us, its 2 year...
Right now I have nothing to lose so i´ll give it a shot with our old twice-succeeded technique: 230V directly on the input to fry the board and usee have no idea why he woke up with a dead phone^^
cucolino said:
Sorry, but your post makes no sense. First: I already gave TWRP. Second: I don't have OS installed anymore. Third: How would your suggestion help with my case? I'm afraid you misunderstood my problem... :/
Click to expand...
Click to collapse
sorry Yes I misunderstood your problem
I attached a zip extract it you will find meta-inf + recovery.img (dummy file ) replace recovery file with whatever recovery you wanna flash with name recovery.img zip it flash it