Database Users

[Q] [L7] Swapping/Overclocking issues

This morning, my phone will not boot. Black screen, no lights, no vibration, no logo.
I suspect it had something to do with me using mmcblk0p3 as a swap partition via Swapper2 the night before, or the Purity kernel I installed for overclocking (although it was stable with overclock for several boots).
The former was the most likely cause.
I searched for what the purpose of mmcblk0p3 was for, but I was sure it was used as Linux swap.
I couldn't even boot into recovery nor fastboot.
Any help guys?

Hi!
Try to connect your phone (without battery) via a USB cable to the KDZ Flash Tool by pressing volume + and power. Appears on the screen Emergency Mode with a yellow background. Install new software. If you don't know how to install new software, this guide will help you.
http://forum.xda-developers.com/showthread.php?t=2167344

Poland_Developers said:
Hi!
Try to connect your phone (without battery) via a USB cable to the KDZ Flash Tool by pressing volume + and power. Appears on the screen Emergency Mode with a yellow background. Install new software. If you don't know how to install new software, this guide will help you.
http://forum.xda-developers.com/showthread.php?t=2167344
Click to expand...
Click to collapse
I've already tried that, doesn't work.
Oh, I forgot to list my phone's specs.
LG P705G
Cyanogenmod 10 with 4cyl Turbo Engine/Crossbreeder and AC!D audio engine
Swap enabled

Probably motherboard is defective... The battery is charging at all?

Checked battery level manually with a voltmeter.
Fully charged, and the phone is plugged in anyways right now.
The charging animation doesn't show, though.

Maybe give him the guarantees...

[Q] Overheating & Baterry Draining & Hang After about 1 minute

Sorry but i'm just a newbie here. Plz help me ... I'm having someproblem with my SS4 I9500 GSM only model. Just bought it a few days ago and yesterday after I root it with Kingroot everything still ok until I download the TWRP recovery on CHPlay. It show some kind of warning that could affect my SD but I ignore and have it done something to install the TWRP on my phone. After one time reboot my phone started to run real slow , super hot until hang itself and extremely battery draining ( about 25 - 30 % for one time boot till it hang and reboot ). I've tried to reinstall an Original Firmware but couldn't because I can't connect my phone with the PC everytime I tried to connect the cable my PC show the Code Err 23. Device not recognized. . I tried the factory reset but it still operated like that and there's no TWRP but the original recovery of android. Changed the cable , changed the PC , still nothing happened. Someone plz help !!!

Lenovo A3500-HV Bricked while flashing ROM ( Cable disconnected )

OS : Windows 8.1 (With drivers successfully installed ) X64
Also tried on Windows 7 (With drivers successfully installed ) X86
Using SP flash tool
The device had this ROM : A3500HV_A442_01_37_140920_ROW
and it is the same I was trying to flash
Hi all , My lenovo A3500-HV went crazy and I had to re-install the rom ..
but while flashing using SP ( all drivers are OK ) the goddamn cable disconnected at about 15% - 20% from total progress
CURRENT STATE :
DEAD :'(
can't power up , nothing happens after pressing power button
can't go into recovery mode or download mode ( nothing happens when pressing VOL UP & Power , VOL UP & DOWN & Power or any other sequence )
it is not charging when I put it on the charger or the USB
is not being recognized when I plug it in ( see attachments please ) !!
device manager screen shot attached please have a look
-----
any hope it can revive ?? , how ??
or just go to the warranty ( really few days left ) .. note that it was rooted device .. ( ( will they ever detect the root if the device is dead ? ) )​

up

up

Help my update
ebram96 said:
up
Click to expand...
Click to collapse
I Have same problem. Did you have ANY SOLVE ?:angel:

I have same problem too,,Did you find any solution??

p.m.6 said:
I have same problem too,,Did you find any solution??
Click to expand...
Click to collapse
Look the device was stuck at boot but showing nothing on screen .. so I waited till it has 0% battery and re-flashed the rom successfully .. if you still having problems text me I may help

i have the samy problem
i have the same problem but i dont know how to fix it

ebram96 said:
Look the device was stuck at boot but showing nothing on screen .. so I waited till it has 0% battery and re-flashed the rom successfully .. if you still having problems text me I may help
Click to expand...
Click to collapse
is it really works? but i cant even see the screen backlight is turned on. was it the same with yours? how would you know when the battery level is 0%?
then after (we believe) the battery level is 0% you just connect your tab to your computer to make it show up with COM X connection, correct?
hope it really works and not a coincident (':

kakung said:
is it really works? but i cant even see the screen backlight is turned on. was it the same with yours? how would you know when the battery level is 0%?
then after (we believe) the battery level is 0% you just connect your tab to your computer to make it show up with COM X connection, correct?
hope it really works and not a coincident (':
Click to expand...
Click to collapse
YES , the tab backlight was off and there was not any sign of it working and then I lost hope and left it for a while and then I tried the charger and it was recharging so I tried flashing and it worked just fine

Lenovo A3500 bricked, "USB device not recognized"
ebram96 said:
YES , the tab backlight was off and there was not any sign of it working and then I lost hope and left it for a while and then I tried the charger and it was recharging so I tried flashing and it worked just fine
Click to expand...
Click to collapse
Lenovo A3500FL_A422 bricked, "USB device not recognized" when connected to windows, could not flash it using SP Flash Tool.
After disconnected the battery, flash process begun and was OK.
Thanks !

i have the same problem as yours
after i disconnect battry and flash rom it gets error while flashing on 20%
what should i do ?
:crying:
error : S_FT_DOWNLOAD_FAILD (4008)

arshiyah53 said:
i have the same problem as yours
after i disconnect battry and flash rom it gets error while flashing on 20%
what should i do ?
:crying:
error : S_FT_DOWNLOAD_FAILD (4008)
Click to expand...
Click to collapse
i'm manage to get on 40%
but it stuck in that.
error : S_FT_DOWNLOAD_FAILD (4008)
show up.
change the cable, change pc to laptop,
noting happen.
any sugestion?

Help - (N9002) Charges Only When Phone's OFF (and Download Mode Works)

Edit: flashed most recent stock firmware (Android 5.0 based, dated back in early 2017) and charging/file transfer is possible again. So I'd speculate that it comes down to incompatible kernel from the later version of ROM.
I would still love to have Lineage OS 16 on this though, so any help/pointer is still appreciated.
--------- Original Situation Below ---------
I recently took a very old Galaxy Note 3 (N9002), and successfully flashed TWRP (N9005/HLTE) build, and the equivalent Lineage OS 16 build (official nightly).
I was very pleased to see that the 6-yr old device runs the Android 9 based ROM very smoothly, and had all the fun getting re-acquainted with Android in general, until the moment I plugged in the charging cable and Samsung official adapter -- nothing.
I reconfirmed this by turning on Developer Mode - ADB debugging, and connected to the computer that I used to flash in the recovery earlier, with 3 different working USB cables. No charging, no file transfer, no devices attached when doing
Code:
adb devices
.
Turned the phone off, reconnected cable and it'd charge, but vibrates every now and then with different battery icon shows (one with a huge empty battery, along with warranty bit set to Kernel/void; the other with smaller battery that seems to have the juice go up every now and then indicating it's charging up). The back of the phone, especially toward the top (around camera) gets mildly heated.
Turned the phone back on in Download Mode, and confirmed that it's still detected by Odin3 (and even flashed an HLTECHN TWRP and back to HLTE one successfully). Both prove that the cable, the charging, and the transfer mechanism should work.
This becomes pretty inconvenient in terms of day-to-day use, so any help and suggestion would be greatly appreciated.
Thanks.

Exactly the same issue
woozyking said:
Edit: flashed most recent stock firmware (Android 5.0 based, dated back in early 2017) and charging/file transfer is possible again. So I'd speculate that it comes down to incompatible kernel from the later version of ROM.
I would still love to have Lineage OS 16 on this though, so any help/pointer is still appreciated.
--------- Original Situation Below ---------
I recently took a very old Galaxy Note 3 (N9002), and successfully flashed TWRP (N9005/HLTE) build, and the equivalent Lineage OS 16 build (official nightly).
I was very pleased to see that the 6-yr old device runs the Android 9 based ROM very smoothly, and had all the fun getting re-acquainted with Android in general, until the moment I plugged in the charging cable and Samsung official adapter -- nothing.
I reconfirmed this by turning on Developer Mode - ADB debugging, and connected to the computer that I used to flash in the recovery earlier, with 3 different working USB cables. No charging, no file transfer, no devices attached when doing
Code:
adb devices
.
Turned the phone off, reconnected cable and it'd charge, but vibrates every now and then with different battery icon shows (one with a huge empty battery, along with warranty bit set to Kernel/void; the other with smaller battery that seems to have the juice go up every now and then indicating it's charging up). The back of the phone, especially toward the top (around camera) gets mildly heated.
Turned the phone back on in Download Mode, and confirmed that it's still detected by Odin3 (and even flashed an HLTECHN TWRP and back to HLTE one successfully). Both prove that the cable, the charging, and the transfer mechanism should work.
This becomes pretty inconvenient in terms of day-to-day use, so any help and suggestion would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
I'm facing exactly the same issue after flashing with the same Lineage OS 16 on the mobile model Galaxy Note sm-n9002 HLTECHN
No charging, no file transfer, no devices attached when doing
Turned the phone off, reconnected cable and it'd charge, but vibrates every now and then with different battery icon shows (one with a huge empty battery, along with warranty bit set to Kernel/void; the other with smaller battery that seems to have the juice go up every now and then indicating it's charging up). The back of the phone, especially toward the top (around the camera) gets mildly heated.
Will greatly appreciate if someone can help
Thanks

valteg said:
I'm facing exactly the same issue after flashing with the same Lineage OS 16 on the mobile model Galaxy Note sm-n9002 HLTECHN
No charging, no file transfer, no devices attached when doing
Turned the phone off, reconnected cable and it'd charge, but vibrates every now and then with different battery icon shows (one with a huge empty battery, along with warranty bit set to Kernel/void; the other with smaller battery that seems to have the juice go up every now and then indicating it's charging up). The back of the phone, especially toward the top (around the camera) gets mildly heated.
Will greatly appreciate if someone can help
Thanks
Click to expand...
Click to collapse
here's the script that can fix the usb problem for n9002 on oreo or pie rom: just flash it without wipe the cache; but unfortunatly it doesn‘t work on android 10 and im looking for solution
https://drive.google.com/open?id=1G1...K7y1HwQbd4LN20

sm-n9002
pigliang said:
here's the script that can fix the usb problem for n9002 on oreo or pie rom: just flash it without wipe the cache; but unfortunatly it doesn‘t work on android 10 and im looking for solution
Thanks, Pigliang for the quick help
But I can't open the link, I keep receiving the following ERROR message from Google.
"404. That’s an error.
The requested URL was not found on this server. That’s all we know."
Please can you check and send the script again
Thanks
Click to expand...
Click to collapse

pigliang said:
here's the script that can fix the usb problem for n9002 on oreo or pie rom: just flash it without wipe the cache; but unfortunatly it doesn‘t work on android 10 and im looking for solution
https://drive.google.com/open?id=1G1...K7y1HwQbd4LN20
Click to expand...
Click to collapse
The link is not working, can you uplode it again?

Recently I've been to coolapk and find a one seemed to be working right (not tested yet):
Google Drive

Corvus os and Evolution x stops booting midway unless phone is plugged in to a power source.

Hello, recently I came across this strange issue on my Redmi note 7 ( Lavender ) where certain custom roms will just literally stop their boot process midway and the device shuts down inspite of having a fully charged battery. The roms will only boot up normally when my device is connected to a wall adapter or via the usb cable plugged in to my computer. Lineage os v18.1 was the only custom rom as of now which booted normally. Can anybody tell me why is this issue happening and if there is any fix for this strange issue ?
Thanks
Edit
Lineage os v18.1 shuts down all of a sudden without any warning. Even stock MIUI won't boot unless I connect a power source to the device. Also I tried all the known ways of decrypting after flashing Orange fox recovery but no matter what I do, the encryption stays there and I have to format 'data' once or twice to boot up. Lazy flasher dm-verity-opt-encrypt doesn't work. I flashed the latest one from here . Magisk works but doesn't disable force encryption. OTA and dm-verity options from Orange fox recovery doesn't work. This issue is really big. I searched google for possible fixes but none of them were properly related to the issues i am having and not all of the options are specific to my device. Any help will be appreciated !!
Thanks

[email protected] said:
Hello, recently I came across this strange issue on my Redmi note 7 ( Lavender ) where certain custom roms will just literally stop their boot process midway and the device shuts down inspite of having a fully charged battery. The roms will only boot up normally when my device is connected to a wall adapter or via the usb cable plugged in to my computer. Lineage os v18.1 was the only custom rom as of now which booted normally. Can anybody tell me why is this issue happening and if there is any fix for this strange issue ?
Thanks
Edit
Lineage os v18.1 shuts down all of a sudden without any warning. Even stock MIUI won't boot unless I connect a power source to the device. Also I tried all the known ways of decrypting after flashing Orange fox recovery but no matter what I do, the encryption stays there and I have to format 'data' once or twice to boot up. Lazy flasher dm-verity-opt-encrypt doesn't work. I flashed the latest one from here . Magisk works but doesn't disable force encryption. OTA and dm-verity options from Orange fox recovery doesn't work. This issue is really big. I searched google for possible fixes but none of them were properly related to the issues i am having and not all of the options are specific to my device. Any help will be appreciated !!
Thanks
Click to expand...
Click to collapse
That means your battery is done for, even if your battery show good health there's limit on how much Amp. your battery can produce while booting which is insufficient, so better replace battery