Database Users

[Q] Q about factory cable and miui rom/twrp

Ok so recently i fried my kinde,so for when i get a new one i need to know a few things...
1.Does a factory cable charge the battery.
2.When i had my kindle it shut down even when it was connected to the charger as if i was just using too much cpu power and the triagle flickered on and off because of no battery.If i am using a custom rom(miui.us) without a charger and it shuts down because it is out of batteries would it boot up with a normal charger?
3.if you use a factory cable am i stuck in fastboot till i use the computer to get out?
4.does cynagenmod have trouble charging while in use like miui.us?
Thank for the help

powerpoint45 said:
Ok so recently i fried my kinde,so for when i get a new one i need to know a few things...
1.Does a factory cable charge the battery.
2.When i had my kindle it shut down even when it was connected to the charger as if i was just using too much cpu power and the triagle flickered on and off because of no battery.If i am using a custom rom(miui.us) without a charger and it shuts down because it is out of batteries would it boot up with a normal charger?
3.if you use a factory cable am i stuck in fastboot till i use the computer to get out?
4.does cynagenmod have trouble charging while in use like miui.us?
Thank for the help
Click to expand...
Click to collapse
1) Other users have indicated that the battery will not charge while in fastboot mode, but it's been reported that the factory cable will boot the device even when the battery is flat or even disconnected.
2) It's possible, but if you read the posts from the other thread you started several days back, the user with a dead battery said he was only able to get his battery charging again with the stock software.
3) No, you can turn off the device, disconnect the cable, and reboot. It will revert to whatever bootmode was set before the factory cable forced it into fastboot mode.
4) I've never had problems with CM7. I've even had it shut off on me after some running app went nuts and drained the battery in a few hours. I don't have any experience with MIUI.

thank
kinfauns said:
1) Other users have indicated that the battery will not charge while in fastboot mode, but it's been reported that the factory cable will boot the device even when the battery is flat or even disconnected.
2) It's possible, but if you read the posts from the other thread you started several days back, the user with a dead battery said he was only able to get his battery charging again with the stock software.
3) No, you can turn off the device, disconnect the cable, and reboot. It will revert to whatever bootmode was set before the factory cable forced it into fastboot mode.
4) I've never had problems with CM7. I've even had it shut off on me after some running app went nuts and drained the battery in a few hours. I don't have any experience with MIUI.
Click to expand...
Click to collapse
Thanks... one more thing,did cynagenmod get hardware acceleration/flash/video working?

powerpoint45 said:
Thanks... one more thing,did cynagenmod get hardware acceleration/flash/video working?
Click to expand...
Click to collapse
Hashcode is working on a new kernel to get HWA working for CM9. It's still a work in progress.

where
kinfauns said:
Hashcode is working on a new kernel to get HWA working for CM9. It's still a work in progress.
Click to expand...
Click to collapse
Could you give me the link to the official cm9 thread for download?thanks

powerpoint45 said:
Could you give me the link to the official cm9 thread for download?thanks
Click to expand...
Click to collapse
Technically, there is no "official" CM9 for the Kindle Fire because the KF is not an officially supported Cyanogenmod device. With that said, this might be as close as you get...
http://forum.xda-developers.com/showthread.php?t=1411895

[Q] Battery Problem, Defy Briked?

Hi all,
I think I got a sourious Problem with my defy (green Lens).
I was aktually running on CM7.2 Stable as out of a sudden the call was aborted and the defy dead. But the Battery was at perhapse 20%.
At home I pluged it in and was schowing to charge.... (showing the flash in the Battery symbol at 5% and red LED)
Next day still at 5%. so nothing charged. So I changed the battery with my second defy (running on CM10) 100% loaded. But the Phone shows me still 5%.
Wenn phone is pluged in I can boot and work with it, I also can go into the Custom recovery and into the bootloader. But only when I pluged the phone and not when connected to the computer. Also bootloader shows battery low, even with a 100% loaded battery, so I can't Flash anything with RSD.
I tried everything I know, installing new roms (at the moment its at cm10)
Wiping everything... also Battery. Tried battery recalibration apps. and even some battery fixes for Defy+ but nothing changed something.
My only suggestion ist that it must be a hardware defekt..... anybody some other Ideas, what I could try?
Any Ideas how much it will cost to repair? Warrenty surely lost?
Thanks in advance. Andy

Nobody any Ideas?

maybe you should try to reflash with your stock SBF file you had b4 installing CM7 and see what happens... if the battery doesn't show right even then, I'm afraid it might be smth with your hardware...

pppprrrr said:
maybe you should try to reflash with your stock SBF file you had b4 installing CM7 and see what happens... if the battery doesn't show right even then, I'm afraid it might be smth with your hardware...
Click to expand...
Click to collapse
Problem ist, that i can install any custom roms using custom recovery. But I can't flash something over RSDLite, because Handy doesn't start without beeing plugged in (plugged into pc isn't enough) and even then it shows battery at 5% even if battery ist 100% Full (Witch I can test, because I got a second defy) So I wouldn't be able to Flash because Bootloder says, not enough battery.
I don't know how I should flash.....

Did you test to restore nandroid ? If you didn't make nandroid backup when all was good, it's an error...
If there is a PC on Linux near you, you can test sbf_flash (which works very well for me on my Salix OS), eventually with the -f (force) option.

Hi,
no I don't have a nandroid backup, from this phone.... Is ist possible to use a nandroid backup of another phone? As I said, I got a second defy, so I could take one from this.

just wipe data n reflash.
connect the phone to your pc/laptop tru the cable.. for a night.. then boot. wipe data and reflash, else there is a methid where u cut open the usb cable and give the red and black to the battery.

By now I own an HTC ONE S .... so it's not so important, but I would like to repair it anyway....
naga123 said:
connect the phone to your pc/laptop tru the cable.. for a night.. then boot.
Click to expand...
Click to collapse
No Problem, device boots, when on cable......
naga123 said:
wipe data and reflash,
Click to expand...
Click to collapse
No Problem I can Wipe an flash as much as I want.... device is working as long cable is pluged in..... but Battery will never charge
Or even worse..... the battery shows 5% even when full! And device is powered off, when I unplug the cable
naga123 said:
else there is a methid where u cut open the usb cable and give the red and black to the battery.
Click to expand...
Click to collapse
what do you mean with this? Don't understand? Link?
Thanks so far...

Does anybody know what Torx srewdriver I need to open the defy?
Thanks

Sordalong said:
Does anybody know what Torx srewdriver I need to open the defy?
Thanks
Click to expand...
Click to collapse
Hi
I have Same Problem.
1- Flash Froyo Kernel .
2- Flash Quarx CM10 2nd-boot (10-01-2013)
3- Flash Red Lens battery Fix
If These Not Worked Ur Battery Dead.
4- Buy New Battery

Sordalong said:
Does anybody know what Torx srewdriver I need to open the defy?
Thanks
Click to expand...
Click to collapse
Tx no 5
Your problems with Defy seems to be a hardware problem due to a fried condenser from power circuitry.

pgreed said:
Tx no 5
Your problems with Defy seems to be a hardware problem due to a fried condenser from power circuitry.
Click to expand...
Click to collapse
Thanks... but I resigned to open it by my self and sent it to dat repair.... I'm also sure that it have to be an hardware issue. I'll see if they will repair it on garanty or not...
Thanks

Yu yureka Charging issues

I updated my yureka to cm12.1 from the OTA i recieved. For a week it worked just fine . But lately i am facing a major issue with my phone , the device wont charge at all . Firstly it wont charge , and even if does , by chance it charges to 50-60% and starts to come down even if the charger is on . I need help regarding this issue . I have to constantly keep my device plugged in to the charger to keep it running .. Pls help .. I have no root access ..

Maybe your charging pin is loose.

same problem here friend. how did you fixed the issue plz advice me @ankur1296

just change the charging cable

Try to change your USB...problem lies in USB cable
Sent from my AO5510 using Tapatalk

ankur1296 said:
I updated my yureka to cm12.1 from the OTA i recieved. For a week it worked just fine . But lately i am facing a major issue with my phone , the device wont charge at all . Firstly it wont charge , and even if does , by chance it charges to 50-60% and starts to come down even if the charger is on . I need help regarding this issue . I have to constantly keep my device plugged in to the charger to keep it running .. Pls help .. I have no root access ..
Click to expand...
Click to collapse
Try flashing any Custom ROM. If it didn't work, try to use another charger or replace your device.

[Help pls] Note 3, not responding: Bricked? Installing Lineage OS

I just bought a BNIB Note 3.
Samsung Note 3: SM-N900W8
Symptoms: Won't turn on, no lights, no load screen, no recovery mode, no download mode.
When I hook the phone up to the PC via USB it does vibrate and sounds the connection ringtone
What I was doing when this happened:
I had just recently rooted using "KINGRoot" - checked root and it was successful
I installed "TWRP" and booted into recovery mode and it was a success as well(I didn't actually run here yet)
***I installed and opened "Flashfire" to Flash the LINEAGE OS to my Rom buuut I didn't actually select the Lineage pack and I accidently pressed FLash(insert expletive here) *****
So Flashfire went through it's loading and when it was done it shut off and then the symptoms started.
It's a Note3 from Bell with all of their bloatware on it and I wanted to clean it all off and run a clean/efficient Note 3 cell with Rogers. I'm not looking to keep any of the data currently on the phone as there isn't anything currently on it. I just want to be able to install Lineage and use my Note.
I've searched for 30 hours pretty solid so far and unfortunately I haven't come across a clear solution. Can anyone give me a diagnosis and a tutorial or a link to a fix.
I'm open to loading from MicroSD, USB Jig, Samsung Kies....anymore information you require from me as away and I'll get back ASAP

Dead battery would be first check .

JJEgan said:
Dead battery would be first check .
Click to expand...
Click to collapse
Battery - I did the "spin" test on the battery and it doesn't show any physical characteristics of an overheated(bulged) battery. I'm going to test fit my battery into another note3 and I'll respond asap.

JJEgan said:
Dead battery would be first check .
Click to expand...
Click to collapse
I tried the battery in another Note3 and my battery is 52% charged and had no issues booting the tester phone.
I have the phone being tested for any Hardware issues right now.
If it's not a hardware issue will I be able to force a Rom(whether OEM Firmware or other) to install via MicroSD or USB jig?

When the phone is connected to a Windows machine, does a new device appear in device manager?
Have you tried to force it into download mode with a USB jig?
For flashing ROMs to the sm-n900w8, the simplest method is to flash TWRP, boot to TWRP, wipe everything, and flash the desired ROM.
If nothing works, you could take it to a cell repair shop and hopefully have it repaired with a jtag cable or a similar method.

audit13 said:
When the phone is connected to a Windows machine, does a new device appear in device manager?
Have you tried to force it into download mode with a USB jig?
For flashing ROMs to the sm-n900w8, the simplest method is to flash TWRP, boot to TWRP, wipe everything, and flash the desired ROM.
If nothing works, you could take it to a cell repair shop and hopefully have it repaired with a jtag cable or a similar method.
Click to expand...
Click to collapse
No, the PC doesn't see the phone.
The USB jig or MicroSD force is something I'm researching to try next(feel free to provide any good links to set up a jig(I've done this with Ubuntu on my laptop but this has a more intimidating feel to it)). The Tech at the shop I took it to test the hardware says "the motherboard" is broken and he'll fix it for $60.
For future considerations I'll learn to use TWRP flashing ROMs.

If the shop is offering to fix it for $60, they may be just force-flashing the firmware with something like an Octopusbox.
The USB jig may force the phone into download. If it doesn't, I don't think you'll have a choice but to pay to have it flashed. Unfortunately, Samsung will not help as rooting would trip the knox counter.

USB jig ebay are the usual cheap source.

Nexus 7 2012 hard bricked (can't boot)

I don't know where to start with my problem.
Firstly my Nexus 7, 2012 , 5.1.1 android , nakasi- grouper version tablet was very slow. Tried all the known recovery mode options etc. but nothing really changed. So I decided to Root it .
In order to root it properly I download the wugfresh root toolkit. I knew that my USB port was quite unstable but I thought I could risk it, since I didn't have anything serious in there, and at the end of the day I was trying a clean re-installation.
Before doing anything I decided to flash the stock rom and unroot it (since I didn't know if the device was at a correct- clean factory state.... Just for the sake of it) Unfortunatelly I might also have chosen the 2013 version because I didn't really know the differences)...
Everything went well, up to the point that a cmd said that there was no device and stuck there. It was in the bootloader mode and couldn't move. I disconnected the device from the USB, pressed hard and for more than 30 secs the power button, it switched off. Then I pressed hard the power button for a long time (and after that many more times) but it never came back to life.
I tried to press any combination of buttons many times. Disconnected the battery. Actually measured it for voltage and current (everything's fine). Charged it in an alternative way. Reconnected it (several times). To no result. Dead device. I can call it hard-bricked, but to me, it's more like dead.
Any idea what went wrong and if there's any chance for this tablet to come back to life? Is it worth it? No serious data in there. Haven't backed up anything related to it.
Thanks in advance.

Take the back off of thr device and carefully disconnect the battery. Wait 5 minutes, then plug battery back in and replace the back.
If you can get a pogo cable you can charge without using the USB. Either way, kust let it charge for a few hours, then try to power up.
The Root Kit has a recover from boot loop option you should use. It will download the last official rom and flash it unrooting your system. Just make sure you choose the right model of nexus when you start.
Good luck
Sent from my LGLS992 using Tapatalk

psiphi said:
Take the back off of thr device and carefully disconnect the battery. Wait 5 minutes, then plug battery back in and replace the back.
If you can get a pogo cable you can charge without using the USB. Either way, kust let it charge for a few hours, then try to power up.
The Root Kit has a recover from boot loop option you should use. It will download the last official rom and flash it unrooting your system. Just make sure you choose the right model of nexus when you start.
Good luck
Sent from my LGLS992 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
No chance with solution number one.
As I said I 've left it charge for more than 10 hours. Measured the battery's poles.
Around4 volts, 2.7 amps. Everything's fine with the battery.
The tab won't boot at all. Can't enter bootloader, can't be recognised by the USB, can't use the Root Kit.

tedsorvino said:
I don't know where to start with my problem.
Firstly my Nexus 7, 2012 , 5.1.1 android , nakasi- grouper version tablet was very slow. Tried all the known recovery mode options etc. but nothing really changed. So I decided to Root it .
In order to root it properly I download the wugfresh root toolkit. I knew that my USB port was quite unstable but I thought I could risk it, since I didn't have anything serious in there, and at the end of the day I was trying a clean re-installation.
Before doing anything I decided to flash the stock rom and unroot it (since I didn't know if the device was at a correct- clean factory state.... Just for the sake of it) Unfortunatelly I might also have chosen the 2013 version because I didn't really know the differences)...
Everything went well, up to the point that a cmd said that there was no device and stuck there. It was in the bootloader mode and couldn't move. I disconnected the device from the USB, pressed hard and for more than 30 secs the power button, it switched off. Then I pressed hard the power button for a long time (and after that many more times) but it never came back to life.
I tried to press any combination of buttons many times. Disconnected the battery. Actually measured it for voltage and current (everything's fine). Charged it in an alternative way. Reconnected it (several times). To no result. Dead device. I can call it hard-bricked, but to me, it's more like dead.
Any idea what went wrong and if there's any chance for this tablet to come back to life? Is it worth it? No serious data in there. Haven't backed up anything related to it.
Thanks in advance.
Click to expand...
Click to collapse
Hi, tedsorvino...
I hate to be the bearer of bad news, but I suspect your Nexus 7's bootloader has become corrupted (possibly due to a faulty USB connection during your wugfresh reflash), or overwritten with an incompatible bootloader for your specific device type, vis-a-vis your reference to flashing the wrong ROM.
Either way, without a valid bootloader, your Nexus 7 will likely never boot again.
Or at least, not without a motherboard replacement, which is probably not worth the hassle or the cost for such an old device.
Flashing the bootloader (either on its own or as part of a full device reflash) was always one of the most risky aspects of reflashing the Nexus 7; it required a healthy battery charge and a solid, stable USB cable connection. It was something I approached with trepidation on my old Nexus 7, and if at all possible, it was something I tried to avoid.
The bootloader is a device critical component for booting the device and also for reflashing it with fastboot commands, because it's the bootloader that accepts and handles those fastboot commands, either directly via a Window's command prompt or with something like Wugresh's toolkit.
And when it gets corrupted or overwritten with something other than a valid bootloader image file, the Nexus 7 is hardbricked, and the only solution is a motherboard replacement.
Ged.

GedBlake said:
Hi, tedsorvino...
I hate to be the bearer of bad news, but I suspect your Nexus 7's bootloader has become corrupted (possibly due to a faulty USB connection during your wugfresh reflash), or overwritten with an incompatible bootloader for your specific device type, vis-a-vis your reference to flashing the wrong ROM.
Either way, without a valid bootloader, your Nexus 7 will likely never boot again.
Or at least, not without a motherboard replacement, which is probably not worth the hassle or the cost for such an old device.
Flashing the bootloader (either on its own or as part of a full device reflash) was always one of the most risky aspects of reflashing the Nexus 7; it required a healthy battery charge and a solid, stable USB cable connection. It was something I approached with trepidation on my old Nexus 7, and if at all possible, it was something I tried to avoid.
The bootloader is a device critical component for booting the device and also for reflashing it with fastboot commands, because it's the bootloader that accepts and handles those fastboot commands, either directly via a Window's command prompt or with something like Wugresh's toolkit.
And when it gets corrupted or overwritten with something other than a valid bootloader image file, the Nexus 7 is hardbricked, and the only solution is a motherboard replacement.
Ged.
Click to expand...
Click to collapse
Thank you. Even if the news are bad, it's a really valuable piece of information. At least now I know.