Database Users

NEED HELP - Android 2.3.7 don't boot anymore

Hi Guys,
I got into a problem here, and I need help! I have a milestone 2 with the latest Endlees CyanogemMod, Android 2.3.7.
I was trying to follow the steps into using the internal memory as a SD card (link http://forum.xda-developers.com/showthread.php?t=948887), but I wasn't successful.
Here cames what I did:
First I tried to follow the steps:
​1- create a file image in /data and a folder in /sdcard
​mkdir /sdcard/storage
​su
​dd if=/dev/zero of=/data/storage.img bs=1024 count=5242880 (1024x1024x5 --> 5Gb)
​busybox mkfs.vfat /data.storage.img
But that didn't work, the terminal emulator just said that the directory couldn't be found.
Then I downloaded Busybox from Android Market, and installed it. But when I executed the program, the installation wasn't done because it was insisting that Busybox wasn't able to access the folder, and didn't have superuser access to root. Even with the permission on Superuser OK!
So after that, I tried to reboot my milestone 2, and now it won't even get to the boot screen of android (screen with the rotating square)
I tried to use the boot recovery tool, and wipe all system data, and reboot, mas it isn't working. Something I noticed on Recovery Tool is that apear a messagem saying "E: Can't Open /cache/recovery/command" and "E: Can't Open /cache/recovery/caller.
Even the battery light won't turn on. If turn off the cell and try to recharge it, appears a image of the battery with a "?" on it... I tried to connect the cellphone to the PC with the usb cable, but it isn't recognized...
I hope someone can help me, I just can't afford to lose this phone.... Thanks

Look in this topic http://forum.xda-developers.com/showthread.php?t=1344740 it should help you solve this problem
in general: firstly you need to charge your battery in another working Milestone 2 or in some universal battery charger (because bricked Milestone 2 is not able to charge battery) and then you need to flash SBF and it should be ok

Anonymous_ said:
Look in this topic http://forum.xda-developers.com/showthread.php?t=1344740
in general: firstly you need to charge your battery in another working Milestone 2 or in some universal battery charger (because bricked Milestone 2 is not able to charge battery) and then you need to flash SBF and it should be ok
Click to expand...
Click to collapse
I read somewhere else that even if the MS 2 is bricked the battery charges. Very very slowly, but it charges.

thanks for your tip... I read the entire topic, but there is a problem. My battery must be around 30% or something, but when a connect the milestone 2 with the pc via usb cable, the lateral light won't even lit... And the pc won't even recognize it...
edit: when I connect the cellphone to the pc, the light lit for 30s more or less, the appear the Motorola logo with the rabbit on the side, but then the light turn off and I get stuck in the same situation...

carpet55 said:
I read somewhere else that even if the MS 2 is bricked the battery charges. Very very slowly, but it charges.
Click to expand...
Click to collapse
I don't know, maybe it is possible, but I as far as I know, everyone, who had bricked M2, charged the battery outside his phone...
So he can try it in the bricked phone, but he can't be 100% sure it will charge, right?
colucci.ti said:
thanks for your tip... I read the entire topic, but there is a problem. My battery must be around 30% or something, but when a connect the milestone 2 with the pc via usb cable, the lateral light won't even lit... And the pc won't even recognize it...
edit: when I connect the cellphone to the pc, the light lit for 30s more or less, the appear the Motorola logo with the rabbit on the side, but then the light turn off and I get stuck in the same situation...
Click to expand...
Click to collapse
Yes, thats why I said here and even in the topic I referred to, you have to charge battery in another non-bricked Milestone 2 or in universal battery charger. When your M2 is bricked, it wont charge any battery (or maybe it will, but very very slow according to carpet55's post ).
So now you have to get some universal charger or working M2 (or another battery).. This is your step no. 1. Then you can flash it via RSDLite by SBF file.

ok Anonymous_!
I'm going to find a way to charge the battery and do what are you saying.
But RDS Lite can flash the android even if windows it isn't recognizing the cell phone on the usb?
thanks again! I'll return with more info when I get my battery fully charged..

After you will have charged battery, you will have to boot into bootloader by holding Power+Volume Down+Camera button, then windows should recognise it (maybe you will have to install drivers too) and then you can use RSDLite (don't forget to run it with administrator rights).

Anonymous_,
final question of the day... Where do I get the SBF file?
I'm from Brazil, so should be the brazillian version of this link?
and-developers.com/sbf:milestone2

You are on the right path
Grab Brazil 2.2 version from http://and-developers.com/sbf:milestone2 and it should be ok.

I can confirm that no, the battery does not charge when bricked. I left mine going for over 24 hours and nothing -_-. So ended up using a universal ac adapter set to 5 volts and some wires directly to the + and -. This didn't work after half an hour so I upped it to 7v and about ten minutes later, all good.
During my research to find how to fix it, someone was saying the charge sequence software in in the system or boot data, and since it was all corrupt - no charge.
But you perhaps allready have enough juice in there to load up bootloader successfully, so try what anon said and hold d-pad up and power on until the screen flashes blackish grey and let go. Then it'll tell you if the battery has enough charge to flash a sbf
Sent from my A953 using xda premium

Guys,
I'm thankful to everyone who tried to help me, especially Anonymous_!
Yesterday, in the same day I bricked my phone, I flashed it even without charging to 100%... and everything has gone well, but it was a close call, because my battery had only 5% left when the milestone returned to live!

Good to hear!
Sent from my A953 using xda premium

Red light - dead z3 plus E6533

first sorry my english
I tried to restore my TA partition my bootloader again and simply my xperia Z3 plus/Z3 + dual - E6533
It does not turn on anymore, it does not vibrate, when I connect it in the charging it blinks red light, when it is on the computer it blinks a red light too and there is no driver
only red light all the time
Any solution ?
:crying::crying::crying:

Any solution ?[/QUOTE said:
try to reflash stock rom with flashtool
0.-google the ftf file for your device or use flashtool>xperifirmware built in to download it
1.- turn off your phone (or keep it off in your case)
2.-install xperia companion to have the latest drivers and reboot your pc
3.-run flashtool by androxide ver 0.9.25
4.- flash stock rom via flashmode, follow the steps
and done.
Click to expand...
Click to collapse

d_g_m_2000 said:
try to reflash stock rom with flashtool
0.-google the ftf file for your device or use flashtool>xperifirmware built in to download it
1.- turn off your phone (or keep it off in your case)
2.-install xperia companion to have the latest drivers and reboot your pc
3.-run flashtool by androxide ver 0.9.25
4.- flash stock rom via flashmode, follow the steps
and done.
Click to expand...
Click to collapse
impossible ... the computer does not recognize the cell phone
When I put USB driver does not appear
and the cell phone only flashes a red light
I can not get into flashmode and fastboot anymore
no blue light and no green light only flashing red light
This looks like sudden death. =/
I'm so sad
:crying::crying::crying:

deidshin said:
impossible ... the computer does not recognize the cell phone
When I put USB driver does not appear
and the cell phone only flashes a red light
I can not get into flashmode and fastboot anymore
no blue light and no green light only flashing red light
This looks like sudden death. =/
I'm so sad
:crying::crying::crying:
Click to expand...
Click to collapse
well, you can see this like an oportunity to (with a little effort) buy some android one device to get years of google's support. right now there's a lots of devices within the android one program and for any type of budget.

deidshin said:
first sorry my english
I tried to restore my TA partition my bootloader again and simply my xperia Z3 plus/Z3 + dual - E6533
It does not turn on anymore, it does not vibrate, when I connect it in the charging it blinks red light, when it is on the computer it blinks a red light too and there is no driver
only red light all the time
Any solution ?
:crying::crying::crying:
Click to expand...
Click to collapse
I've got almost the same symptoms with the same phone.
It didn't boot while disconnected from a charger.
Being connected to the charger, it tried to boot and almost immediately failed. It also blinked 3 times with red on every my attempt to turn it on.
I've remembered about battery and background surface replacement, that had happened before.
Verifying the background surface i found out, that it's not sealed tightly to the phone body. Inspecing internals i've disconnected and tightly connected the battery.
Also, i've firmly installed the background phone body surface and heated it for better coupling.
As a result, i was able to charge and boot the phone after this procedure.
P.S.
From my point of view, you need to disassemble the background phone body surface and re-connect the battery wire to the phone internal socket.

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

Need some help interesting problem

Phone won't turn on
Bootloder mode is running
Fastboot mode rom loading
After rebooting, the leeco is waiting for 15s on the boot screen, and then the black screen and the notification light turn blue.
The same applies in EDL mode
Loading recovery with Fastboot
blackboard and blue notification light are on again
(sorry for my bad english)
(computer phone with black screen and blue led light
qualcomm hs-usb diagnostics 900e)

ceylin45 said:
Phone won't turn on
Bootloder mode is running
Fastboot mode rom loading
After rebooting, the leeco is waiting for 15s on the boot screen, and then the black screen and the notification light turn blue.
The same applies in EDL mode
Loading recovery with Fastboot
blackboard and blue notification light are on again
(sorry for my bad english)
(computer phone with black screen and blue led light
qualcomm hs-usb diagnostics 900e)
Click to expand...
Click to collapse
Try putting the phone into fastboot and use the All in One tool to check to see if the boot loader is still unlocked, sometimes you can flash something that will relock the bootloader and you will get the blue light, which can also mean that the battery is almost dead.
if you can unlock or it shows that it is unlocked, try flashing recovery with All In One tool. If successful Reboot to power off and fully charge phone then wipe and reinstall your rom etc.
Edit:
I just browsed your history, you flashed Jui and the recent Miui roms ( Pie) Anybody else reading stay away from those roms they are poorly made As is the JUI rom that @ceylin45 flashed.
I am pretty sure that the Jui rom or maybe even the Miui Rom uses the S1 bootloader, and that your issue is because you now have a locked S1 bootloader on your phone,
If I am remembering correctly, another XDA user had this exact issue. Caused by flashing a JUI rom.
If you can not unlock it or flash the correct EUI bootloader your only option will be using EUI for the S1, and unfortunately you will never be able to flash a custom rom again, you will be permanently stuck with EUI. This happened a few months ago to a user named Noel, he sold his phone as is.

Thank you very much for your interest.
do you know s1 eui connection i can use
Thank you...

ceylin45 said:
Thank you very much for your interest.
do you know s1 eui connection i can use
Thank you...
Click to expand...
Click to collapse
Unfortunately I don't have the guys details, (The guy who flashed the S1 version of EUI) He had the exact same issue that you are now having and he was able to get EUI working, that is what he told us.
I will look around and get back with you
Okay I am back
I found the conversation with that guy on Telegram, but I don't think he uses telegram anymore.You can go here and read his posts : https://t.me/leecolepro3roms/67347
He posted an image, of the files that he extracted from a S1 fastboot rom and pasted those into the leeco Qfil ( If I am remembering correctly. ) A few days later he told me that he got the phone working again by flashing RUI for the S1 which can be found on 4PDA here : http://4pda.ru/forum/index.php?showtopic=819125
Use Google translate and search this thread and you should find some discussions about using the S1 EUI to resolve your issue. Quite a few people apparently had that exact issue a couple of years ago. Again this is all from memory, and I didn't write anything in my notes because I don't have a coolpad. However, I am pretty sure that this will probably help you with at least getting EUI working.
Good luck.
@ceylin45
I updated what I wrote, so I am pinging you in case you didn't see it.

Thank you
I will search

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