Hello,
I recently successfully installed Windows Phone 7 rom onto my HTC HD2. The phone was working fine and would charge the battery when connected to a dedicated charger on the wall plug as well when it was plugged into another computer. I recently attempted to plug the phone into the computer via USB only to find it wouldn't recognize it ,no prompts on the computer or the orange light on the phone. I turned off the phone, removed the battery for several minutes, I started the phone up again and it would boot into Windows Phone 7 normally without any errors but still it would not be recognized by the computer or allow itself to be charged by an external battery power. I had read somewhere that if I where to select Mass Storage option off the bootloader that it would charge the battery and create a partition on the computer. Huzzah! the computer recognized the partition, but the battery still wasn't charging. Going through multiple threads I have read that it might Magldr others say it's the windows phone 7 rom not being fully stable yet and messing with the battery settings, I don't know where to go from here, i'm hoping someone can help. Here are the direct steps that I took since I got the phone:
Phone: HTC HD2 T Mobile
1. Unlock the phone (successfully)
2. installed HSLP3
3. Flashed Radio leo 2.15.50.14
4. Installed/Flashed MAGLDR113
5. Using USB Flasher installed the LEO70_ROM
That's all no settings afterwards were messed with, and Windows phone 7 came up normally and worked perfectly.
Side note: I have tried multiple micro USB cords and different Socket Wall Chargers.
Any assistance is greatly appreciated.
Thanks,
Mr_Pickles
I've yet to find out why it does this, or a step by step guide to fix it, however it is fixable, it will charge battery if you boot to magldr mode, no light will come on but it does charge, mine done this before and came out of it seemingly by its self, or more likely by a combo of things I did, anyhow, charge it up in magldr first, also try using usbdview to list all your USB devices, delete them all, windows can get confused some times
well fancy that, just happened to me again there, ok, so was at work, and my phone wouldnt take a charge via the socket or USB port on a working PC, like i said before it does charge via magldr
anyhow, just got home and plugged it in to my PC that i know it syncs with and all was fine.
So for you i'd definitely suggest deleteing your USB devices to make sure there is no conflicts, charge up your phone via a wall charger in magldr, then get it working with your PC, perhaps then you will get it working,
Thanks, it still isn't charging when it's on MAGLDR, i'm starting to think the battery might be dead. Either way I've ordered an external battery charger and an extra battery, hopefully that solves my issue. Although it still perplexes me why when attempted to connect to a computer it doesn't recognize it.
Unfortunately at this point the battery is completely drain so I can't do anything until the charger and the extra battery comes, but until then i'll keep digging for the answer.
Cheers,
Mr_Pickles
Mr_Pickles said:
Thanks, it still isn't charging when it's on MAGLDR, i'm starting to think the battery might be dead. Either way I've ordered an external battery charger and an extra battery, hopefully that solves my issue. Although it still perplexes me why when attempted to connect to a computer it doesn't recognize it.
Unfortunately at this point the battery is completely drain so I can't do anything until the charger and the extra battery comes, but until then i'll keep digging for the answer.
Cheers,
Mr_Pickles
Click to expand...
Click to collapse
ah yes that is a problem, youve got the charger coming so its a bit late now but that happened to me once, if its just a bit too dead to get you to magldr to charge then i found if you pop it out, wrap it in a cloth and warm it up, do not place it directly on a heat source, by warming it up a bit it helps give it a wee nudge with its chemical reactions inside, potentially enough to get in to magldr.
there is no way of knowing if its charging via magldr other than it not turning off. but with an external on the way you will be fine.
as for it having issues
im guessing its because the battery controller on the HD2 isnt the same as the controller from where the ROM was pulled, meaning whilst its compatible, its not ideal, the not connecting thing could be a symptom of this, im just guessing here but if lets say the battery controler forgets what its doing could that knock out the who USB connection, the USB ports on the computer will have com ports connected whilst the charger will only have the power ports connected, perhaps a combo of all of these things is the reason
but what id do is get it charged first, use the program USBDVIEW (google it) and remove all USB devices associated with a connection to a HUB reboot and connect the HD2 (fully charged) to a different port than usual. it should install drivers and away you go!
Ok! So i got the charger and did all the steps below but still nothing, the computer won't recognize the phone through USB unless I go to Mass Storage option off of MAGLDR. Any thoughts?
The Windows 7 OS runs just fine. It's the connection to the computer/charger through USB that is the problem. Even when loading the boot loader (multi color screen) and then connecting the USB it won't recognize it, the bottom stays on "Serial".
Any help would be much appreciated.
Thank you,
Mr_Pickles
righty, this could be a challenge,
so usb storage mode IS detected when you plug it in with magldr
therefore we can rule out hardware issues
So physically it will connect, that leaves several different possible issues
first things first, you didnt mess about with USB tethering did you? i really hope you didnt and if you did you better start praying your phone is still unlocked and will allow unsigned apps, and that you still have the USB tethering app installed!
next, WP7 software issue, something is buggered stopping it for connecting,
unlikely if you cant connect via the SPL
Desktop Driver issue.
if there is any USB conflict on your PC it can create many problems for you did you try uninstalling all USB devices using USBDVIEW in admin mode, then try plugging it in again?
ok some other questions, does MAGLDR allow you to go to and use USB flasher mode, as if you where updating you WP7 ROM? does your PC connect and install a device driver when you plug it in? (make sure you deleted all USB devices before hand)
lastly, do you have access to another computer that has NOT had this phone plugged in to?, purely to see if it will get detected in SLP mode or ideally in WP7 itsself? this would obviously rule out your whole PC and would help pinpoint the issue!
Hi Dazza,
Here are the answers to your questions:
Q: first things first, you didnt mess about with USB tethering did you? i really hope you didnt and if you did you better start praying your phone is still unlocked and will allow unsigned apps, and that you still have the USB tethering app installed!
A: I did not mess with the USB tethering, my phone is still unlocked.
Q: Desktop Driver issue.
if there is any USB conflict on your PC it can create many problems for you did you try uninstalling all USB devices using USBDVIEW in admin mode, then try plugging it in again?
A: Yes I did, it still did not connect to the device, not allowing to view it as a storage device or charge the phone. The phone also does not recognize that it has been plugged in to the computer.
Q: ok some other questions, does MAGLDR allow you to go to and use USB flasher mode, as if you where updating you WP7 ROM? does your PC connect and install a device driver when you plug it in? (make sure you deleted all USB devices before hand)
A: Yes it does, it installs the drives and the phone shows the connection has been made through USB.
Q: lastly, do you have access to another computer that has NOT had this phone plugged in to?, purely to see if it will get detected in SLP mode or ideally in WP7 itsself? this would obviously rule out your whole PC and would help pinpoint the issue!
A: Yes I have. I tried 3 different computers and none of them recognize the phone.
Side notes:
- I have flashed an Android ROM to see if that would fix the error so I can switch back to WIN 7, but even with the android ROM the computer still does not recognize the phone being plugged in, nor does the phone recognize it has been plugged into the computer.
- When I have gone to the bootloader (multi color screen) in my attempts to bring back the phone to it's orginal state, it still does recognize the phone and won't let me install the base OS and radios for the phone.
I hope this info helps, man i'm really starting to regret getting this phone.
Thanks,
Mr_Pickles
ok, think we need to start again, its sounding all a bit dodgy, MAGLDR is working but the bootloader and WP7 itsself isnt....
you tried reflashing android to no effect
the only common denominator is the SPL/HSPL and the Radio
However because bootloader isnt working in USB mode you cant flash....
SO, next attempt is.....
Format a small SD card, format it as FAT32 or if that fails try FAT16 (512MB card) this is the tricky bit because some cards will not work.
Downloaded the original ROM for your device, usually a .exe file
Open the exe with a zip/rar program,
Extracted RUU_signed.nhb,
Move ruu-signed.nbh to your sd card,
Rename ruu_signed.nbh to leoimg.nbh
Then power phone off,
pop your small SD card with leoimg on in your HD2
Press and hold volume down, tap power but contiue to hold vol down.
The phone should boot into bootloader mode, and it "should" automatically discover there is a leoimg.nbh file on your sd card and ask you to flash.
If it is the wrong image, you should get a failed install message, but if you phone does nothing at all then either the sd card is faulty or the sd card reader is faulty (unlikely if WP7 was using it), or the nbh file is corrupt.
Faulty SD cards could be format issues, ideally you would format the card in the device itsself but you dont have that option unless android will let you do it, which is always an option!
Righty, hopefully that will reset your device SPL radio and all to the original state, if it works and you can get 6.5 working again see how you get it, its a hunch but i reckeon the SPL got buggered up, i cant see any other logical reason for it not to work, think of the SPL as a BIOS on your PC, if you turn USB off in your BIOS you dont have usb working in the OS.
Just to add to the topic here. If you can still transfer data but not charge or receive power via USB does not mean it is not a hardware issue. It just means the pins for data transfer in the USB port are working. A standard USB port has 5 pins in it (this includes micro and mini USB ports) only 2 of the pins are for power transfer the other 3 are for data transfer.
Also if you do not have ActiveSync or WMDC installed on the computer you connect to via USB while in bootloader you will not get the HTC USB sync (USB in white bar of bootloader) connection because these programs have the USB drivers for the HTC USB sync connection, they are not preloaded on the HD2. Therefore the do not auto install when you plug your USB cable in and are in bootloader. I learned this thechard way.
The OP had posted in the HD2 General forum too and I had advised them to try to use a multi meter to test the battery pins while the charger is plugged into the HD2 to comfirm voltage is getting to the battery. I also advised them to try and flash back to a Windows Mobile ROM to see if charging was possible. Both of these things would rule out a hardware issue.
MAGLDR still has this charging bug, it will let you charge while in USB Mass Sty bit it is not charging the battery correctly and this why, quoted straight from the first post inthe MAGLDR thread.
Battery controller inside LEO needs runtime control during charge, it implemented in OS.,
Click to expand...
Click to collapse
The runtime control means that MAGLDR can not control the rate at which the battery is charged which is not good for 2 reasons. One too little (too slow) of a charge rate or too much (too fast) of a charge rate is detramental to your battery life and battery chargeablity. The secound is to much voltage going to the battery can cause the Li-Ion battery in the HD2 to explode. Now reason number 2 is a very unlikely senerio as all common USB type wall chargers only put out 5.0v to 5.1v and that is safe for Li-Ion batteries, but there is still the risk. But as the quote says the "run time control" is implamented by the OS so when you charge with your HD2 booted into the OS it is safe and not harmful to your battery.
I hope the OP gets their charging issue worked out and I hope it is not a hardware issue.
indeed, the power pins as you pointed out could be the issue, im trying not to complicate things at the moment because even if it was, it should still commence coms to the computer, it does connect via magldr so we can assume that firstly the cable is ok on the data lines, secondly the PC is able to detect the device meaning the device itsself is working
We can also assume that if all USB devices have been removed and no ActiveSync or WMDC is installed then Windows would still detect new hardware but will fail to install it, if the drivers were present and it connected we'd have fixed half the problem!
physically it can connect (magldr proven) but something is prohibiting it in bootloader and the OS, the PC isnt detecting it at all. I dont understand why magldr works and bootloader doesnt unless magldr is able to run its own form of bios, i dont know how it works so i couldnt be sure, so im running with a hunch that the HSPL/SPL is buggered as it wont connect to the pc in bootloader.... if we can flash via SD it will help rule that out.
aye the charger thing on magldr is concerning, but it will be ok to give it a short amount of juice to get to windows, overcharging is the issue, could potentially blow up but its unlikely, the plug charger should have a built in IC to knock it down to a trickle charge when it detects its reversing the polarity....should! lol
Thanks everyone, i'm planning on trying this out tonight when I get home and using the SD to bring it back to stock. Hopefully this solves the problem otherwise I'm thinking that T-Macgnolia is correct and one of the Pins in the USB is broken and would need to be fixed.
I really do appreciate all the effort you guys have given in your response.
Mr_Pickles
Mr_Pickles said:
Thanks everyone, i'm planning on trying this out tonight when I get home and using the SD to bring it back to stock. Hopefully this solves the problem otherwise I'm thinking that T-Macgnolia is correct and one of the Pins in the USB is broken and would need to be fixed.
I really do appreciate all the effort you guys have given in your response.
Mr_Pickles
Click to expand...
Click to collapse
its possible that the bootloader or the OS needs the power to be connected in order to function, you did say that you have tried different USB ports and a number of cables, the only other posibility would be that the pin on the phone its self is broken, thats going to be difficult to test.
do the SD thing first, if that doesnt work boot to android, note the battery level, get it to around 50%, then turn off the phone and boot to MAGLDR, you do not need to have it in USB storage mode or anyother mode, just leave it plugged in at the MAGLDR menu.
now the USB port on a PC will provide no more than 500mAh, so if you had 50% charge that would be about 600mAh in the battery, leave the phone plugged in to your PC in MAGLDR menu for an hour, that should give it no more than 1100mAh of juice, (it will actually be less than that as your screen will still be sucking juice)
if you use the 1A wall charger then only charge it for 30min, just to be on the safe side. (if you can i would recomend this one as it rules out any issues with data pins) and if its not working it wont completely drain your battery sitting there with the screen on
anyhow, boot back in to android and see what the battery level is indicating, if its gone up you know its charging, if its gone down you know it isnt, which may indicate a broken phone.
Good luck and keep us posted!
Success! Loading the stock ROM through the SD and finally my computer recognizes the phone! Thank you so much everyone for your help, I can't tell you how much I appreciate it.
Mr_Pickles said:
Success! Loading the stock ROM through the SD and finally my computer recognizes the phone! Thank you so much everyone for your help, I can't tell you how much I appreciate it.
Click to expand...
Click to collapse
no probs mate, thats why XDA dev is here!
i think its almost certain its a SPL issue, possibly got corrupted somehow, least you know its not hardware, i know this sounds a bit much after all you just went through but dont give up on WP7
Hi Guys,
I had exactly the same problem as Mr_Pickles.
I had tried reflashing the stock rom using the SD card method.
Everything installed normally, but after the flashing the HTC logo appears followed by the Radio version and other info shown in the bottom of the screen in red text.
Then the mobile reboots and keeps doing the same thing again and again.
Could someone help me on this please?
nvenon said:
Hi Guys,
I had exactly the same problem as Mr_Pickles.
I had tried reflashing the stock rom using the SD card method.
Everything installed normally, but after the flashing the HTC logo appears followed by the Radio version and other info shown in the bottom of the screen in red text.
Then the mobile reboots and keeps doing the same thing again and again.
Could someone help me on this please?
Click to expand...
Click to collapse
did you install HSPL? before doing anything or is it doing this restart after you reflashed your Stock ROM via the SD card
nvenon said:
Hi Guys,
I had exactly the same problem as Mr_Pickles.
I had tried reflashing the stock rom using the SD card method.
Everything installed normally, but after the flashing the HTC logo appears followed by the Radio version and other info shown in the bottom of the screen in red text.
Then the mobile reboots and keeps doing the same thing again and again.
Could someone help me on this please?
Click to expand...
Click to collapse
Hey Guys,
I experienced the same problem with the installation of wm6.5 stock rom (with having hspl 2.0 installed) as nvenon and couldn't find a solution.
dazza9075 said:
did you install HSPL? before doing anything or is it doing this restart after you reflashed your Stock ROM via the SD card
Click to expand...
Click to collapse
HSPL 2.0 installed, Stock rom installed via sd card method, still the same problem.
The point is that I read somewhere to just keep on flashing wp7, which works fine until operating XBmod-Yuki Rom Build 7004:
- While the wp7 works fine, the phone can't be recognized by any PC via USB, so i can't update the build via update cab sender
- But: The phone is detectable and chargable in bootloader mode, so now hardware issue?
I would appreciate any help.
Thanks in advance!
Hello,
I have had this problem in the past and it stumped me for a bit of time until I looked very carefully at how I was resetting the device. If you are not careful and with flashing etc you will be ripping the battery out all the time.
Look at the device with the battery out and you will see those 3 little pins. They need to be in a line for the battery to make decent contact with it. Over time if you are constantly taking out your battery it will bend them... you can just use your finger to straighten them.
That should do it. It got to a point I always take out my battery carefully now and make sure these pins are aligned before putting it back in.
okay, this is my time to post here.
using h2owner's wp7.8 rom I got a problems with sudden stop charging till once my battery dead completely.
after that I have (quoting my post from h2o thread):
"
it's not to abuse as we know all the risks we take testing roms, just asking for your advice:
1. I did install your latest rom
2. after some time it stopped charging at all
3. the problem is the phone got unable to charge under sd android as well.
4. at the end of story battery got dead - can't load magldr.
5. managed to direct power on it via red/black cables of usb to +/-
6.but the problem still the same - I can't charge battery via phone
7. and even more - can't enable usb via bootloader (tricolor) - serial only:
- usb flasher works only with wp7 rom install;
- magldr, hspl, task29 flash via usb flasher fails with critical error 0000001;
- naturally, can't flash winmo;
- usb storage works well."
1. nbh of the default os flashed fine
2. pins are aligned
3. issue is still here
please, help if you can
dimdimdim said:
okay, this is my time to post here.
using h2owner's wp7.8 rom I got a problems with sudden stop charging till once my battery dead completely.
after that I have (quoting my post from h2o thread):
"
it's not to abuse as we know all the risks we take testing roms, just asking for your advice:
1. I did install your latest rom
2. after some time it stopped charging at all
3. the problem is the phone got unable to charge under sd android as well.
4. at the end of story battery got dead - can't load magldr.
5. managed to direct power on it via red/black cables of usb to +/-
6.but the problem still the same - I can't charge battery via phone
7. and even more - can't enable usb via bootloader (tricolor) - serial only:
- usb flasher works only with wp7 rom install;
- magldr, hspl, task29 flash via usb flasher fails with critical error 0000001;
- naturally, can't flash winmo;
- usb storage works well."
1. nbh of the default os flashed fine
2. pins are aligned
3. issue is still here
please, help if you can
Click to expand...
Click to collapse
okay, now I got "00028002 not allow" error trying flash stock original rom from sd...
still no sd in bootloader, which changed to 1.42...
completely lost.
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.
I installed this rom https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 on the same ROM but rooted now my phone does not support turbo charging and if I plug my phone to the pc is not displayed, before that clean the micro usb port of my phone, I do not know if it damaged it or does not support turbo charge for having flashed wrong.
Could you tell me what the problem is? if it is wrong flashed as I flash it back if I can not connect it to the pc? or is it the micro usb port and do I have to change it?
megasjuan said:
I installed this rom https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 on the same ROM but rooted now my phone does not support turbo charging and if I plug my phone to the pc is not displayed, before that clean the micro usb port of my phone, I do not know if it damaged it or does not support turbo charge for having flashed wrong.
Could you tell me what the problem is? if it is wrong flashed as I flash it back if I can not connect it to the pc? or is it the micro usb port and do I have to change it?
Click to expand...
Click to collapse
No rom affects turbo charging in any way. Check the temperature of your phone and the connection/cable. Reflashing may be an option to.
@megasjuan turbo charging is hardware feature and has nothing effect even of wrong flash (many one did wrong flashing and lost one imei of slot-2 and with model number, in your case it seems to be fine, right? )
You said you cleaned usb port, it may be damaged that while, or may be not.
Turn your phone off and plug it to charging, then see what that charging screen says.
For computer connection, try updating driver / remove and install again / change usb cable or different usb slot of computer.
Then you can conclude what's wrong.
Thaks
____Mdd said:
@megasjuan turbo charging is hardware feature and has nothing effect even of wrong flash (many one did wrong flashing and lost one imei of slot-2 and with model number, in your case it seems to be fine, right? )
You said you cleaned usb port, it may be damaged that while, or may be not.
Turn your phone off and plug it to charging, then see what that charging screen says.
For computer connection, try updating driver / remove and install again / change usb cable or different usb slot of computer.
Then you can conclude what's wrong.
Click to expand...
Click to collapse
I sold my phone, i use it a lot, and i need a fast charge phone, thaks for your answer
I have a note 3 that has always worked flawlessly until today. The phone has a stock ROM, is rooted and has a custom recovery. I am selling the phone so I wanted to go into recovery and clean the phone for sale.
When I tried to go into recovery, the phone looked like it was going in, but after a minute or so, the phone rebooted. The Samsung Galaxy Note 3 logo appears and on the upper left corner it says, "Recovery Booting, Set Warranty Bit: recovery", then it reboots.
I installed Samsung USB drivers, went into download mode to flash the original ROM, but Odin doesn't recognize the phone. There isn't any sim in the phone, but I doubt that makes a difference.
Any help would be great, thanks,
Ian
Tried using different usb cables and usb ports?
Where did you get the custom bootloader?
What model Note 3 ??
audit13 said:
Tried using different usb cables and usb ports?
Where did you get the custom bootloader?
Click to expand...
Click to collapse
Sorry, I meant to say the phone has a custom recovery (TWRP) and it's been on the phone a couple of years. I used the phone up until February when the screen cracked and I got a new digitizer for it. it's been sitting since. Yes, I tried 2 different cables and 2 different USB ports
JJEgan said:
What model Note 3 ??
Click to expand...
Click to collapse
SM-N900W8, the phone was bought from Telus, but has been unlocked.
Ian
If Odin doesn't recognize the phone, there is no way I know of to flash a stock ROM.
Is it possible the USB port is damaged?
audit13 said:
If Odin doesn't recognize the phone, there is no way I know of to flash a stock ROM.
Is it possible the USB port is damaged?
Click to expand...
Click to collapse
I replaced the USB port, just in case. I think it's the mainboard though. The phone will only turn on if I plug the USB cable in, then it goes through the recovery then shutoff routine again. The battery measures 4.3 volts, is this too low? Maybe the battery is too low and when it is plugged in it starts to boot, but shuts down due to a low battery? How can I charge the battery if when I plug the phone in it turns on and wont charge?
Ian
iskolnick said:
I replaced the USB port, just in case. I think it's the mainboard though. The phone will only turn on if I plug the USB cable in, then it goes through the recovery then shutoff routine again. The battery measures 4.3 volts, is this too low? Maybe the battery is too low and when it is plugged in it starts to boot, but shuts down due to a low battery? How can I charge the battery if when I plug the phone in it turns on and wont charge?
Ian
Click to expand...
Click to collapse
The phone will not charge in recovery mode or download mode so it could be a battery problem. The battery voltage may be too low. Do you have access to another battery to try?