Database Info

[Q] wont mount sd card battery wont charge anymore

HTC One S S4 16 GB
what I did:
1. Unlocked Bootloader
2. installed cwm
3. rooted
4. made backup
5. Factory Reset / Wipe before
6. Flashed http://forum.xda-developers.com/showthread.php?t=1701314
which resulted into a black screen
7. Tried to use my back up---> no back up available
8. SD Card wont mount
9. Tried to put new rom via usb mount--->not possible
10. Tried to repair recovery via fastboot---> still not reading sd card
Situation now:
Now Battery is getting low and wont load anymore, only a red light is blinking for the first minutes when I try loading, so I cant get into Bootloader anymore.
What I am thinking to do:
Open HTC One S and load the Battery separately, then I hope to get into the Bootloader again.
Then I will try to lock the Bootloader and to use a ruu.
Is there anybody who had similar problems? Any suggestions?
Thanks to Everybody in advance!

Yeah, leave it charging for a couple of hours, then unplug the charger and try to boot into bootloader again.
Once inside bootloader, plug in the usb cable and fastboot flash the boot.img.

Goatshocker said:
Yeah, leave it charging for a couple of hours, then unplug the charger and try to boot into bootloader again.
Once inside bootloader, plug in the usb cable and fastboot flash the boot.img.
Click to expand...
Click to collapse
It has been loading for about 12 hours now, still it wont load the bootloader. So I am assuming that it is not able to charge the battery.
Still thank you for your answer.

[Q] Do I need the USB cable to root?

Just got me new-to-me TF700 this afternoon. Trying to root it.
Unlocking was easy (all manufacturers should do it this way).
Now trying to root.
I've downloaded (and copied to /sdcard0) CWM touch for KK (recovery-kk-touch-6046.img)
Press [pwr] +[vol-down] gets me to what appears to be a fastboot screen. I have 3 options "RCK", "Android", and "Wipe data".
None of these lets me run recovery on the CWM image.
I'd just go into ADB and run from there, but the tablet came without the stock USB cable (the one that plugs in the keyboard port).
Is there another way to do this - of am I doing the wrong thing anyway?
Not a major deal if I need to order a cable and wait.
Thanks!
PS: tablet is on stock 4.2.1. There are a lot of instructions that say, basically, select 'USB' from the fastboot screen. That's not appearing.

bobkoure said:
I'd just go into ADB and run from there, but the tablet came without the stock USB cable (the one that plugs in the keyboard port).
Click to expand...
Click to collapse
Without that cable, how do you connect it to the charger?
bobkoure said:
There are a lot of instructions that say, basically, select 'USB' from the fastboot screen. That's not appearing.
Click to expand...
Click to collapse
There are also instructions updated for the current bootloader that tell you that fastboot is already active in the bootloader menu.
bobkoure said:
Also. What the heck is the port next to the headphone jack that looks mike a micro USB, but isn't?
Click to expand...
Click to collapse
Micro HDMI.
You could try if the recently released towelroot works for you until you get your cable.

It came with an aftermarket charger; charger and cable are a single piece. I'm not sure the separate chargers are available at all now.
I saw those instructions - and it looked like I was in fastboot. What I mostly wanted to do was install the CWM image. I think there's a way to do that as recovery, as well, but the img has to get packaged in a zip file with instructions and then named whatever recovery is looking for. Not something I'm going to be able to whack together.
Yeah, realized it was micro HDMI just as soon as I started looking at "tf700 cable". Duh! Removed it from my OP, didn't realize someone had already looked at it and was looking to save someone (you?) some typing. Didn't work.
Time to get a cable.

Found one of the OEM chargers. $55 + shipping. Not planning to buy.

bobkoure said:
Found one of the OEM chargers. $55 + shipping. Not planning to buy.
Click to expand...
Click to collapse
If Towelroot works (it probably will since it does work on the TF701) and you get root, you can use the dd command in terminal to flash the custom recovery. But better do some reading on that! One little typo and you could have yourself a brick.
You cannot flash a custom recovery using the stock recovery however - or did I misunderstand?
You can get by without a USB cable if you can get it rooted, but what if something goes wrong? What if you cannot enter recovery and only fastboot is available?
I would not flash custom software without a working ADB and fastboot connection! And for those you need the USB cable. Get it - you'll regret it if you don't.

berndblb said:
! And for those you need the USB cable. Get it - you'll regret it if you don't.
Click to expand...
Click to collapse
Oh, I got one. Just was itchin' to get a new ROM. Hoping KK's a bit speedier (it had ought to be) - and it's desperately slow now.
Towelroot, indeed, worked fine. Mixed feelings on that one. It working means basically any app that gets installed can get root. But I'm happy I got root to play with in the couple of days it took Newegg to get a cable to me

bobkoure said:
Oh, I got one. Just was itchin' to get a new ROM. Hoping KK's a bit speedier (it had ought to be) - and it's desperately slow now.
Towelroot, indeed, worked fine. Mixed feelings on that one. It working means basically any app that gets installed can get root. But I'm happy I got root to play with in the couple of days it took Newegg to get a cable to me
Click to expand...
Click to collapse
Good choice getting the cable.
Install SuperSU from the Play Store. That will allow you to control which apps get root.

berndblb said:
Good choice getting the cable.
Install SuperSU from the Play Store.
Click to expand...
Click to collapse
Did that immediately. Paid for pro ages ago
Now trying to get fastboot via USB.
power off (or reset)
power & [vol dn]
stock JB so it goes right into fastboot (3 selectable icons, no "USB" icon)
connect USB
on win pc cmd line go to adb/fastboot directory
"fastboot devices" gets me... nothing.
Not sure how to get CWM installed without fastboot (?)
Trying to figure out if I maybe have bad win drivers. adb works (e.g. "adb shell" works fine) - not when in fastboot mode, of course.
Any ideas? Pointers to the right drivers (win 64)?
Thanks!

bobkoure said:
Did that immediately. Paid for pro ages ago
Now trying to get fastboot via USB.
power off (or reset)
power & [vol dn]
stock JB so it goes right into fastboot (3 selectable icons, no "USB" icon)
connect USB
on win pc cmd line go to adb/fastboot directory
"fastboot devices" gets me... nothing.
Not sure how to get CWM installed without fastboot (?)
Trying to figure out if I maybe have bad win drivers. adb works (e.g. "adb shell" works fine) - not when in fastboot mode, of course.
Any ideas? Pointers to the right drivers (win 64)?
Thanks!
Click to expand...
Click to collapse
Windows is infamous for driver problems.....
Connect the tab in fastboot and open device manager. Near the top you should have an entry for Android device, bootloader mode or something similar, and probably a yellow ! next to it.
Right click it and choose "update driver", let Windows search for it.
If you're lucky it'll install the driver by itself.
If not: What Windows version are you running?

berndblb said:
If not: What Windows version are you running?
Click to expand...
Click to collapse
Win 7 Pro / 64.
If you don't mind, I'm going to re-ask this in the general forum - if it's like other forums, when the question changes tack, often people who might know the exact answer never read it because the title was about the original question.
I put it here
BTW, Got CROMBi-KK on there without fastboot (so without a USB cable ) as follows
towelroot - got root
installed supersu, loaded binaries, uninstalled towelroot
goo.im - open bootloader - installed TWRP
installed CROMBi-KK by copying zip to sdcard0, then install from TWRP.
Even without booting / using a fast external SD card, it's perceptibly faster than the stock JB ROM. I did kind'a like the way the stock JB screen was laid out to make it easy to use while attached to a keyboard (controls at L & R bottom corners where you can easily poke 'em with a thumb.) Ah, well.

Ah yes - forgot about Goo. For quite a while it didn't support flashing TWRP anymore, but it's back.
There's also TWRP Manager (which I haven't tried yet) and Flashify which I really like.
It does make flashing a recovery easier, but.....
Call me old-fashioned, but all of those require Android to run. What if you're stuck in a bootloop and need to flash a recovery, clear partitions in fastboot etc? To get drivers working when the tablet is already compromised can be a challenge - to say the least.
I wouldn't be surprised if we see more and more users here who went your route, never got ADB and fastboot going and find themselves stuck when Android does not boot....
That said, I'm glad you can experience KK goodness now and I'll head over to your new thread - maybe I have another idea

I had to install all the system after several flashs ! Help !

Hy friends,
I have problems.
So I have a nexus 5, and I flashed several times, to test cyanogenmod, to test the preview of Android M, to install kernel... Maybe more that 12 times.
And it's happen. My phone now won't turn on. When I charge it the red led twinkle several times and after nothing. I can go to the bootloader but when I want flash something nothing happen. On the cmd console it seems like the installation works well but in fact it's useless. Yesterday I tried and suceeded to install TWRP ! Furthermore my Nexus 5 can't turn on alone, when I flash the bootloader must turn off then turn on, my phone no, I had to press Volum Down + Power button.
So yes, now I have TWRP on my phone and the application shows me that my intern storage of my phone is empty, like completly empty.
So maybe I have the solution, I want a backup which is compatible with TWRP to install it on my phone !
Do you have other ideas or maybe my idea is a ****ing bull**** and my Nexus 5 is definetly dead :crying:
Thanks a lot !

xython said:
Hy friends,
I have problems.
So I have a nexus 5, and I flashed several times, to test cyanogenmod, to test the preview of Android M, to install kernel... Maybe more that 12 times.
And it's happen. My phone now won't turn on. When I charge it the red led twinkle several times and after nothing. I can go to the bootloader but when I want flash something nothing happen. On the cmd console it seems like the installation works well but in fact it's useless. Yesterday I tried and suceeded to install TWRP ! Furthermore my Nexus 5 can't turn on alone, when I flash the bootloader must turn off then turn on, my phone no, I had to press Volum Down + Power button.
So yes, now I have TWRP on my phone and the application shows me that my intern storage of my phone is empty, like completly empty.
So maybe I have the solution, I want a backup which is compatible with TWRP to install it on my phone !
Do you have other ideas or maybe my idea is a ****ing bull**** and my Nexus 5 is definetly dead :crying:
Thanks a lot !
Click to expand...
Click to collapse
1) Adb a twrp flashable rom to your internal.
2) Use OTG and usb stick

If the led flashes red when off and connected to a charger, the battery is cmpletely discharged. Leave it connected to the original charger and USB cable for a few hours.

wangdaning said:
1) Adb a twrp flashable rom to your internal.
2) Use OTG and usb stick
Click to expand...
Click to collapse
I used adb to put a twrp recovery in my phone and when I want to install it with twrp it's wrote : FAILED. Gonna be different with OTG and USB stick ?

xython said:
I used adb to put a twrp recovery in my phone and when I want to install it with twrp it's wrote : FAILED. Gonna be different with OTG and USB stick ?
Click to expand...
Click to collapse
You can adb push the zip (rom) to the phone and try fastboot boot (twrp.img) then use twrp to flash the rom on the phone.
If this does not work it seems you motherboard is fried.
If you have twrp and the otg cable, then put the rom on your usb stick and connect in twrp. Try flashing off the drive.
Again, I am getting the feeling this is hardware. Your memory or battery seem to be failing. It has nothing to do with prior flashing. My N5 has gone through way more than yours, and I am sure others have done more than me. We still have working phones.
Also consider the power button issue.
Try the steps though.

wangdaning said:
You can adb push the zip (rom) to the phone and try fastboot boot (twrp.img) then use twrp to flash the rom on the phone.
If this does not work it seems you motherboard is fried.
If you have twrp and the otg cable, then put the rom on your usb stick and connect in twrp. Try flashing off the drive.
Again, I am getting the feeling this is hardware. Your memory or battery seem to be failing. It has nothing to do with prior flashing. My N5 has gone through way more than yours, and I am sure others have done more than me. We still have working phones.
Also consider the power button issue.
Try the steps though.
Click to expand...
Click to collapse
Thanks !
Do you know where I can download a TWRP recovery for nexus 5 (hammerhead) ?

xython said:
Thanks !
Do you know where I can download a TWRP recovery for nexus 5 (hammerhead) ?
Click to expand...
Click to collapse
TWRP thread in original development.

OPO does not charge anymore (input current always 0mA)

Hey guys,
after I have got some problems with charging in the past (wallchargers are always recognized as USB, very slow loading) I upgraded my OPO to CM13.
Now my phone does not charge anymore at all, all animations and charging recognitions seems to work (except wallchargers are still shown as USB), but the input current is always 0 mA, now I am stuck at 2% battery with power-save mode
Powering off and loading seems not to work, after powering on after some time battery is not increased
Ampere shows, that I am still losing 10-40mA with status discharging, but usb charger plugged
At the beginning (or afterI had noticed) I had Boeffla kernel and app, which showed, that input current massively drops from 250-400mA to 0 mA after one second charger plugged in. I tried to increase from stock logic to 1500mA, but same problem
MV stuck at ~3620mV
Does anyone know this problem?

Get a new Battery

So a broken battery causes a wrong detection of charger type, for example?
I am really wondering, if this is just a battery problem
I could load battery over night in TWRP with about 7-10% per hour, device was now full and mV was about 4230
Now powered on, decreases again

Atleast for me and a friend, only the original OPO AC Charger + Cabel gets reconized as AC Charger. Everything else, no matter what, is only a USB Charger with around 600mAh-800mAh max (Samsung Fast Charge AC Adapter 2000mAh which works on S5)
I don't belive that your IC Power Circit Chip is broken, in normal cases it would lead into a complete board dead. But yours still working, so it should be allright.
If you lucky its just the battery, I in your position would replace it anyway. Secound part to set the focus on is the USB Port, it can be damaged or just corroded over the time. So if you plan to setup a order buy the two parts.

tt might software problem. when u flash a new kernel and u forgot to wipe cache and dalvik , it sometimes make ur phone take more time to charge. (srry bad english)

Traace said:
Atleast for me and a friend, only the original OPO AC Charger + Cabel gets reconized as AC Charger. Everything else, no matter what, is only a USB Charger with around 600mAh-800mAh max (Samsung Fast Charge AC Adapter 2000mAh which works on S5)
I don't belive that your IC Power Circit Chip is broken, in normal cases it would lead into a complete board dead. But yours still working, so it should be allright.
If you lucky its just the battery, I in your position would replace it anyway. Secound part to set the focus on is the USB Port, it can be damaged or just corroded over the time. So if you plan to setup a order buy the two parts.
Click to expand...
Click to collapse
Thanks I will change battery first I think
As said, i could load over night to 100% (4230+mV) in TWRP, vey strange, the charging symbol in TWRP (the "+") was shown, currently I am trying the same again, but it seems not to load anymore right now

MojoManagement said:
Thanks I will change battery first I think
As said, i could load over night to 100% (4230+mV) in TWRP, vey strange, the charging symbol in TWRP (the "+") was shown, currently I am trying the same again, but it seems not to load anymore right now
Click to expand...
Click to collapse
Okay nice to hear. I advice to replace both. The USB part is just 5$ more ~ and its not that difficult. As for the battery, u have to open the opo anyway.

did you use battery calibration to clear the battery file after flashing?

I changed the battery and the usb connector with flex cable. Same issue.
Btw in my car the phone loads sporadically, but with about 1500mA, very very strange. I checked it again with 4 wall chargers and different usb cables, here it does not work
So it seems that I have to load the phone in my car.
Oneplus support has not been writing back for over a week.

Only the original charger and cable gets recognized as AC charger

KuranKaname said:
Only the original charger and cable gets recognized as AC charger
Click to expand...
Click to collapse
No, I got a few chargers and some of them were recognized as AC already. Anyway, the original one is not recognized as AC either.
My OPO is also not recognized by any computer anymore.. so no fastboot flash

Anyone got another idea what I could try?

MojoManagement said:
Anyone got another idea what I could try?
Click to expand...
Click to collapse
Hi, by advance sorry for my poor English.
Since you changed the battery it doesn't seem to be a material issue.
I don't really think that this will solve your problem, and you may want to keep using cm13, but you could try this :
-Make a nandroid backup and save all your data.
-Flash TWRP(2.8.6.0 !), you could either flash it or just boot the image via your computer if you want to keep stock recovery.
-Clean Flash Oxygen OS (oxygen_1.0.0_flashable.zip)
-Don't forget to do a factory wipe via TWRP, and reboot.
Then try the "OPO charging current" app, and see if it is charging above 800mA or not.
If oxygen OS doesn't work, you can try Calkulin's_Stock_OPO_XNPH44S_ROM_v1.0.zip
I'm running cm13 (114) nightly and I also have some charging issues, tough they are not as serious as yours.
<!> EDIT <!> : Before flashing another rom, you can try this, it significantly improved my charging speed over cm13 :
-Go to Settings -> Gestures and disable everything. Then reboot and try OPO charging current app.

MethylHaine said:
Hi, by advance sorry for my poor English.
Since you changed the battery it doesn't seem to be a material issue.
I don't really think that this will solve your problem, and you may want to keep using cm13, but you could try this :
-Make a nandroid backup and save all your data.
-Flash TWRP(2.8.6.0 !), you could either flash it or just boot the image via your computer if you want to keep stock recovery.
-Clean Flash Oxygen OS (oxygen_1.0.0_flashable.zip)
-Don't forget to do a factory wipe via TWRP, and reboot.
Then try the "OPO charging current" app, and see if it is charging above 800mA or not.
If oxygen OS doesn't work, you can try Calkulin's_Stock_OPO_XNPH44S_ROM_v1.0.zip
I'm running cm13 (114) nightly and I also have some charging issues, tough they are not as serious as yours.
<!> EDIT <!> : Before flashing another rom, you can try this, it significantly improved my charging speed over cm13 :
-Go to Settings -> Gestures and disable everything. Then reboot and try OPO charging current app.
Click to expand...
Click to collapse
As said, my OPO is not anymore recognized by usb at every computer.
So in case of any error, I could not flash anything with fastboot.
I am wary about flashing Oxygen OS in TWRP, also I have cm13 and caf things at phone
Oxygen OS 2.4.1:
Also, do not try to flash this build through TWRP. You will most likely lose your radio and IMEI which means a trip to our customer support. It won't lead to thermonuclear war but just don't do it.
Click to expand...
Click to collapse
I have TWRP 2.8.6.0 installed already and my problem existed with latest cm 12.1 nightly, with temasek 5.1.1 and latest cm13 nightly.
Only with sultanxda caf cm 13 charging works with plug-in delay and very slowly

MojoManagement said:
No, I got a few chargers and some of them were recognized as AC already. Anyway, the original one is not recognized as AC either.
My OPO is also not recognized by any computer anymore.. so no fastboot flash
Click to expand...
Click to collapse
So u changed the USB port and the OPO is not recognized at all anymore?, then u made something wrong, or the part is broken

MojoManagement said:
As said, my OPO is not anymore recognized by usb at every computer.
So in case of any error, I could not flash anything with fastboot.
I am wary about flashing Oxygen OS in TWRP, also I have cm13 and caf things at phone
Oxygen OS 2.4.1:
I have TWRP 2.8.6.0 installed already and my problem existed with latest cm 12.1 nightly, with temasek 5.1.1 and latest cm13 nightly.
Only with sultanxda caf cm 13 charging works with plug-in delay and very slowly
Click to expand...
Click to collapse
I though it could be okay since you bought a new cable.
The version of oxygen OS you're supposed to flash is, as I said, 1.0.0, not 2.4.1, and via twrp 2.8.6.0. This ain't supposed to cause your phone any harm (At least, it didn't caused me any trouble).
Also, this may be a stupid question, but were all drivers correctly installed on the computers with which you tried to detect your phone while in fastboot mode ?

Traace said:
So u changed the USB port and the OPO is not recognized at all anymore?, then u made something wrong, or the part is broken
Click to expand...
Click to collapse
It was already broken before, but I dont know the exact date and reason
I replaced the complete usb dock with cable to board and battery, same issue
MethylHaine said:
I though it could be okay since you bought a new cable.
The version of oxygen OS you're supposed to flash is, as I said, 1.0.0, not 2.4.1, and via twrp 2.8.6.0. This ain't supposed to cause your phone any harm (At least, it didn't caused me any trouble).
Also, this may be a stupid question, but were all drivers correctly installed on the computers with which you tried to detect your phone while in fastboot mode ?
Click to expand...
Click to collapse
Of course all drivers are here, the phone is not recognized at all, no windows sound when plugging in or any new device in device manager. Every other phone works here. I also tried 3 different computers
I read so many issues with Oneplus RMA... so I try everything else before
Edit: forgot to mention again, charging does not work in TWRP, too, so I dont think its an OS issue

Any one know oneline market where can i order opo power ic chip?

Urgent mistake needs a fix..

Hi there people,
Well I did a big BS tbh. I was running AOSiP(20190407) but I was still having proximity issues now and there (doesn't matter what rom, I've got this for a while), so I flash a miui from time to time(maybe for a driver proximity fix).
Yesterday I remove the password(temporary), booted TWRP, flash miui 9.4.18(latest dev) and because I was in road, I've tried to flash AOSiP(20190407) back which stuck on the AOSiP logo, then I remember I did have the previous version 20190328? if I remember well, BIGGGGG mistake trying to flash that, phone can't boot and goes to TWRP recovery which is fine but when I see the data, well encrypted(scrambled that is) - doesn't asks for password of course
Tried to place a file via MTP(e.g. LineageOS latest or MIUI) without success ..tries to copy it but doesn't really do anything, my thought is to:
Buy a USB Type-C OTG cable or adapter and try to flash LineageOS or MIUI through that, if data are still encrypted then I'd try to put the very same password I had and maybe be lucky?
Any other thoughts? (of course deleting data would solve this but my latest backup is 1-2 months back which will make me very sad to lose 1-2 months of pictures, videos etc)
P.S. I've made a custom microusb OTG cable but using a usb type-c adapter doesn't make it work so I guess it's a pin-issue ..OTG microusb can't work with usb type-c that way, that's why I'm thinking of a usb type-c otg cable/adapter. I have a few microusb jacks laying around, that's why I tried that

Try to boot with latest twrp and see if it unscrabled partition...

AOSP roms do not boot with the latest vendor and firmware. If you flash an older version in twrp you should be good to go.

hocuspocus69 said:
Try to boot with latest twrp and see if it unscrabled partition...
Click to expand...
Click to collapse
I've got the latest TWRP for a while now
hmmm 3.3.0.0 is release but since I can't move the recovery in order to flash it I should do it via fastboot
EDIT: Can't do it via fastboot, doesn't work. I tried I see the device when I run the command well it does nothing hmmm I guess my only hope is with the solution I mention and MAYBE I'd be lucky
EDIT2: Tried again and again now it says "press any key to shutdown" when I issue the command ..maybe USB debugging issue? not sure, well if I can flash miui or something similar via OTG(I'll have the cable/adapter in a couple of days, no phone until then hhahahaha), if I keep trying it's either the first(doing nothing) or the second "change display black display with tiny letters on top left corner saying "press any key to shutdown" - oh well sht happen

M1chiel said:
AOSP roms do not boot with the latest vendor and firmware. If you flash an older version in twrp you should be good to go.
Click to expand...
Click to collapse
The part where I can't access data or write data in the internal memory is an issue so I can't do any "flash" ...I can try with OTG adapter/cable when I get my hands on it
Wish it will work as I'm out of options

I also got the tiny letters in fastboot mode. It turned out that fastboot commands only worked for one of the three usb ports of my laptop. I guess usb 3.0 didn't work.

M1chiel said:
I also got the tiny letters in fastboot mode. It turned out that fastboot commands only worked for one of the three usb ports of my laptop. I guess usb 3.0 didn't work.
Click to expand...
Click to collapse
Well different pc, original cable I flashboot recovery, now on 3.3.0.0 ...still data scrambled
Yeah, new recovery ...pretty same result
I guess I'll have to way an try the "OTG" method I was thinking about
P.S. Trying to move miui in internal storage still does nothing, well I tried. Now I only hope OTG would save me
Not sure if I could fastboot miui without losing data, it's been a while since I use fastboot

I tried with USB OTG adaptor, no luck. It doesn't work(can't see any usb stick) ..FML