Related
First of all sorry for my english not good.
Start : with my HD2 have brick after task29 and not success to flash new ROM I'm take USB. cable out and try to open my HD2 in to boot loader by put volum down + power bottom but screen not show any image or 3 color my phone it only long vibration pull battery out waiting 30 minute and put battery in and try to open my phone to boot loader but is same only long vibration.
Now : can not do any think with it when try to plug power in my phone is auto startup and long vibration.
I'm search on google and in this forum not have some one face problem same as me please help me to fix this.
Any body please help me, I'm love it because now we can run both WM. and Android
Upppp waiting for your help
Did you try a long press of the reset-button?
You could try to put the original Stock Image from HTC onto the root-folder of your SD-Card, rename it to LEOIMG.nbh and Push Vol up + Vol down during start and follow the on-screen instructions if it works.
Otherwise use Search-Function in the forum.
ı have jtag HTC for samsung and HTC devices if u want send for repair to me..
www.sevgigsm.net/forum
admin..
I use ORT
Did you check to make sure your radio version was correct before flashing? This is probably the number one reason for bricking.
Check this thread it may help you if you did the flash properly:
http://forum.xda-developers.com/showthread.php?t=668347
i got same problem now...
no screen, no boot, vol down+ power oso same
no screen just a long vibration
anybody help?
I am using the correct radio so don't tell me I am using a wrong radio or something, I have been flashing for 4 months so I know EXACTLY how to flash.
now i can neither get into tri-color or hard reset so don't tell me to flash or smth like that, just tell me how to recover properly
Don't tell us to use search or something because seems like only 2 of us is encountering this problem in the internet
I'm exactly the same problem as TS coz it juz auto go vibrate when plug in battery
This problem actually started when I flash ROM halfway, it stucked and failed...
the device is already HSPL-ed!!!!
but why the F it cannot get into tri-color bootscreen now?
Also, I have to state that my device already got several problems before, my device was very hard to bootup as it will always stuck at HTC screen w/o red version number at bottom left corner, must keep on removing and reinstall battery and reboot until it can boot, not an issue with rom/radio/sim/sd as I tried flash proper rom and radio and remove sd and SIM.
my device also seems like got problem at the gps chip, because when using it for a few minutes, it will lost signal and never reconnects unless i soft reset, after use gps the device will also use battery VERY FAST(-100mA in standby, from -4mA).
now i cannot flash to stock completely, how do I get warranty it?
at the long vibrate, when i plug in to my pc, it will keep on got usb connected and disconnected sound
and dont know what device is connected as not shown in found new hardware and device manager
I also have been searching all possible keywords about what me and TS encountered but all linked to completely UNRELATED results(like search for long vibrations only link to people asking how to make vibration long and 1st result is this thread)
bountygiver said:
This problem actually started when I flash ROM halfway, it stucked and failed...
the device is already HSPL-ed!!!!
but why the F it cannot get into tri-color bootscreen now?
Also, I have to state that my device already got several problems before, my device was very hard to bootup as it will always stuck at HTC screen w/o red version number at bottom left corner, must keep on removing and reinstall battery and reboot until it can boot, not an issue with rom/radio/sim/sd as I tried flash proper rom and radio and remove sd and SIM.
my device also seems like got problem at the gps chip, because when using it for a few minutes, it will lost signal and never reconnects unless i soft reset, after use gps the device will also use battery VERY FAST(-100mA in standby, from -4mA).
now i cannot flash to stock completely, how do I get warranty it?
Click to expand...
Click to collapse
Silly question, but are you holding (and keep on holding) the Volume-Down button while you press the power button?
of course YES
i told you i have been flashing for so long
Leo from T-Mobile. Hi! I've got same problem. After flashing new (next) rom phone definetely died. Phohe is currently simfree and with HSPL. Only one reaction is short vibration after press power button. I searched everywhere. My phone has no bootloader but system see him as Qualcom CDMA Technologies MSM. Thats all, any ideas? Please and thanks for advice.
czaruch said:
Thats all, any ideas?
Click to expand...
Click to collapse
Yes, you flashed a non tmous stock rom that included a ..51.. radio and it destroyed your phone.
What rom? exact filename please.
thank you so much.
I bricked a Leo with the .51 radio. I think I read that is a European or otherwise foreign radio. Since your ROM has Euro in the name.......
czaruch said:
ROM_Leo_HTC_WWE_EastEurope_1-66.
Click to expand...
Click to collapse
The full filename for that rom is
RUU_Leo_HTC_WWE_EastEurope_1.66.479.2_Radio_CRC_Si gned_15.32.50.07U_2.07.51.22_2_Ship.exe
it comes with a version x.xx.51.x radio, and they do Not work on tmous (t mobile us) phones. They kill them
Your phone is dead, sorry. No known fix.
warranty or repair (or JTAG if you are brave and have the money)
a friend of mine bricked his phone. he then tried to microwave it, but that didn't work after that he took a power wire from an old computer, cut it and connected it directly to the phone's parts where the battery would go...this completely f-ed his phone up (he also used a lighter to fake a powersurge of the battery). Then he called htc and a few weeks later he got a new hd2!
GOOD LUCK
lol, he doesnt need to do any of that, its allready as dead as it can be. Loads of epople have had them replaced under warranty with this kind of brick. It wont start, so htc/tmo cant see that its been hacked.
Hi! I understand and realy sad. Somebody know where could I fix it in UK? And how much for this pleasure. Thanks.
i would contact htc, see what they have to say. (dont say you flashed it, it just stopped working")
hey guys
i bought a Galaxy s couple of weeks ago (GT-I9000M). i rooted the phone using "one touch root".....then install "Vibrant9 Eclair 2.1" rom by "eugene373".....then before i could do the lag fix and Kernel, as soon as i plugged in my USB cable, my phone would shut down and go into a cycle of showing an empty battery icon (the phone is fully charged) then a black screen ...this would happen whenever i plugged in the USB in to the phone (no matter using my PC or wall charger) , it would automatically turn the phone off and do the same ..... after a while since i couldn't find a stock Bell rom ,i installed the T-mobile one using the following guide :
http:/ip208-100-42-21.static.xda-developers.com/showthread.php?t=748074
and btw right now the volume bottoms are other way round....(up turns down the sound and Vice-versa)
i was hoping if someone can help me out with this problem...so i can get my phone to connect again.(and fix the sound control volume)
regrads
http://forum.xda-developers.com/showthread.php?t=741027&highlight=unbrick
hey
thanks for taking the time and answering .... but i have done the un-bricking thing as i mentioned .... i think i need a firmware that is not t-mobile cause my phone version is actually GT-I9000M not the SGH-T959 .... a firmware that i can use Odin and put on my phone using the download mode
cheers
Uh oh.. you're in loads of trouble because you're on the international phone and flashed a U.S. ROM.
I remembered when flashing the International leak of 2.2, it would cause a brick going back. Are you able to get into download mode? If you are, look in the I9000 forum for a Odin stock and try that.
Hi to everyone. I will describe here which are my problems with my SGS2.
My battery life is very lower, I think the battery is broken.
I've tried 3 different ROM to improve it but there isn't a difference. My battery is burned in about 10 hours. I don't hard use the phone in these hours, only about 10-15 minute of talking.
On all ROM's which I've tried the effect is the same. I've tried Lite'ning v1.5 too.
Another major issue of my phone is it doesn't stand in power off mode. If I try to turn off the phone, it will automatically turn on. Something happened with my phone, I've bought this one month ago, at the first, this issue wasn't.
So, I've decided to go with my SGS2 to quaranty.
Can you guide me how to make a full restore of SGS2 and put the default ROM on it? Some people told me that I've lost the quaranty if I install a rooted ROM like lite'ning. Is there any method to erase all my installed ROM's history?
P.S: I've wondering in Battery Status application from market a status of my battery: extra voltage when I take it from charging. I really think that this battery is broken.
Thanks you.
nobody can help me?
Search button would have helped .
Flash stock rom .
jje
Thanks but I need more details. If I flash stock rom they won't see the difference? They will know that I put another rooted rom?
puya4ever said:
Thanks but I need more details. If I flash stock rom they won't see the difference? They will know that I put another rooted rom?
Click to expand...
Click to collapse
Flash stock rom and reset counter with USB jig. Search for such keyword if you dont know what that is.
Okay, I've been driving myself crazy trying to find the answer to this little bootloop, and have been all over the place. So I apologize in advance if there is an elusive thread answer to this somewhere...
Here goes:
I downloaded and installed (properly) the [ [ROM] CM9 (ICS) for the Galaxy Player 5.0 USA ] by JackpotClavin. Now normally I would post my issue there, but due to me being a new member, it isn't allowed as you all know. So please bear with me.
Everything works fantastic, until I plug it in when the device is off. Then the screen and buttons light up, it shows the busy signal asterik, and gets to where it would NORMALLY show the battery next, but powers down. Now if I do something that stops the boot loop here (can't remember what right now; no internet at home) then when I plug it in, it actually boots up. But as soon as I unplug it, it kills itself as if it had no battery.
But if I plug in the device when it is already on, then it charges like normal. So I am REALLY confused here.
I already un-bricked it by myself at home when I did something dumb during the ROM restore (CWM). Set it back to stock, and it ran fine. As soon as I switch to the ICS ROM, issues
Now I did a little searching, and in the boot.log it references a "charging_mode_booting" I followed the file path, and found no file there. Now I am aware that I have little (none ) experience in android until now, so that may be normal. I would post the exact log here, but since the device is bootlooping as I type, this will have to wait until I get home again and can troubleshoot
Anyways, I hope I'm not wasting your time. Hope you can help me solve this!
Thank you for your time
N7_X
Samsung Galaxy Player 5.0 (US)
Are you charging your device (while it's shut off) via laptop, console, desktop, or anything else besides a wall charger?
Look under your /system/media
There should be a bunch of battery charging files. If they aren't there, find the files from another ROM and move it there.
Sent from my YP-G70 using xda app-developers app
Jistropy said:
Are you charging your device (while it's shut off) via laptop, console, desktop, or anything else besides a wall charger?
Click to expand...
Click to collapse
Ah thanks mate, that's what I did to get it to boot up while plugged in. Then it has the error here that if I unplug it, whole device shuts off as if the power was the only power source, but will reboot from the battery if I turn it back on.
iurnait said:
Look under your /system/media
There should be a bunch of battery charging files. If they aren't there, find the files from another ROM and move it there.
Click to expand...
Click to collapse
Good idea, I'll get right on it and see if I have any progress.
Thank you both, cheers!
EDIT: Just looked into my system/media folder, and have all "battery_charging_#" 5-100.
Also:
chargingwarning.qmg
Disconnected.qmg
LMprec_508.emd
PFFprec_600.emd
And of course the boot animation and folders
Strange boot loop too with YP-G70
iurnait said:
Look under your /system/media
There should be a bunch of battery charging files. If they aren't there, find the files from another ROM and move it there.
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
Hello everyone ,
first thank you for all your developments.
Secondly, excuse my English but I'm Portuguese.
I spent a lot of time to read all the topics related to this problem, and I have too with my Intl Player.
Since I installed the rj 's custom kernel (r14) if my player is turned off, as I branch as a wall charger or on USB in my MacBookPro , I boot loop load as described above.
So I installed a file explorer that allowed me to see that I had none of the files in the directory system / media.
Ok, I installed adb and fastboot on my Mac , and successful (despite the write permissions only one I managed to get around) to copy the files I found there.
I was sure now it was going to fix my problem, but unfortunately, I have always this kind of boot loop charge if my player is turned off.
Apart from that , everything seems to work well , I do not even know if this is really a problem , I did not let my battery run down lest I get stuck . As long as the player stays on, no worries, battery charging well. Of course I did all the basic wipe's (data/factory, cache, dalvik cache, battery stats).
Sorry for the long post, but I wanted to give as much information .
If someone has an idea of where it may come again, or at least tell me if it's serious in case my battery is fully discharged .
Thank you ! :good:
Edit : actualy I have installed the [ROM][4.3][YP-G70]CyanogenMod 10.2 - M1 Release whith the KKernel R2.1 by KOala888 (My YP-G70 run super fast...).
ToniOsX said:
Hello everyone ,
first thank you for all your developments.
Secondly, excuse my English but I'm Portuguese.
I spent a lot of time to read all the topics related to this problem, and I have too with my Intl Player.
Since I installed the rj 's custom kernel (r14) if my player is turned off, as I branch as a wall charger or on USB in my MacBookPro , I boot loop load as described above.
So I installed a file explorer that allowed me to see that I had none of the files in the directory system / media.
Ok, I installed adb and fastboot on my Mac , and successful (despite the write permissions only one I managed to get around) to copy the files I found there.
I was sure now it was going to fix my problem, but unfortunately, I have always this kind of boot loop charge if my player is turned off.
Apart from that , everything seems to work well , I do not even know if this is really a problem , I did not let my battery run down lest I get stuck . As long as the player stays on, no worries, battery charging well. Of course I did all the basic wipe's (data/factory, cache, dalvik cache, battery stats).
Sorry for the long post, but I wanted to give as much information .
If someone has an idea of where it may come again, or at least tell me if it's serious in case my battery is fully discharged .
Thank you ! :good:
Edit : actualy I have installed the [ROM][4.3][YP-G70]CyanogenMod 10.2 - M1 Release whith the KKernel R2.1 by KOala888 (My YP-G70 run super fast...).
Click to expand...
Click to collapse
The charging mode bootloop has been a problem since the first gingerbread custom kernels and has been a problem up until KitKat. It is solved in KitKat. There is no fixing this problem in pre-KitKat custom roms without recompiling the kernel.
Here is information about the fix:
https://github.com/Meticulus/nutell...mmit/2f7c4affa392c9d0603c23cd3a007ed91dfe62f0
I have answered this question before. Getting tired of explaining it.
Strange boot loop too with YP-G70
Meticulus said:
The charging mode bootloop has been a problem since the first gingerbread custom kernels and has been a problem up until KitKat. It is solved in KitKat. There is no fixing this problem in pre-KitKat custom roms without recompiling the kernel.
Here is information about the fix:
....
I have answered this question before. Getting tired of explaining it.
Click to expand...
Click to collapse
Thanks for your answer. I understand you be tired of answering this problem ... But everything I 've read (and I read for hours and hours , really), I thought it only happened when a USB connection to a computer, not to a wall charging.
If it's just a minor bug and I can use my YP-G70 like that, it's going well, I 'm just afraid to let the battery get to the end and did not do anything. (I also read an old post that says let the battery get to 5% and then moving into CWM mode, and let it discharge completely before reconnecting to a wall charger)...
Last question, is there an kitkat "light" version of that will go as fast as the YP-G70 I installed (4.3) ?, because really outside this bug, all is so good and speed all I 'm doing it (basic use) is really fast.
Strange boot loop too with YP-G70 (4.3)
So I try to install a kitkat to see if the speed is correct.
Thank you again. :angel:
ToniOsX said:
Thanks for your answer. I understand you be tired of answering this problem ... But everything I 've read (and I read for hours and hours , really), I thought it only happened when a USB connection to a computer, not to a wall charging.
If it's just a minor bug and I can use my YP-G70 like that, it's going well, I 'm just afraid to let the battery get to the end and did not do anything. (I also read an old post that says let the battery get to 5% and then moving into CWM mode, and let it discharge completely before reconnecting to a wall charger)...
Last question, is there an kitkat "light" version of that will go as fast as the YP-G70 I installed (4.3) ?, because really outside this bug, all is so good and speed all I 'm doing it (basic use) is really fast.
Click to expand...
Click to collapse
When I was running pre-KitKat ROMs, I let the battery drain completely a few times. It does charge, when it is bootlooping. I let it bootloop for a while, say 10 mins or so and then disconnected it and started it up. Then plugged it back in and let it charge the rest of the way...
:good:
Strange boot loop too with YP-G70 (4.3) --> 4.4
Meticulus said:
When I was running pre-KitKat ROMs, I let the battery drain completely a few times. It does charge, when it is bootlooping. I let it bootloop for a while, say 10 mins or so and then disconnected it and started it up. Then plugged it back in and let it charge the rest of the way...
:good:
Click to expand...
Click to collapse
Well, I installed a Kitkat's ROM ,apart from the start a little longer, everything seems to work well. (Perhaps the least stable wireless)...
I'll try to use it like that a few days and I'll see.
Thank you again. :good:
Hello, everyone!
As you might guess I don't know if my device is hard bricked.
It began when I rooted my Moto E, installed a ROM and then the battery started to discharge way too fast than normal.
I tried to calibrate the battery but it didn't work, at some point the battery only lasted a couple of hours until one day my device turned off and it didn't turn on again.
When I plug the original charger or any other, only the white led blinks, I have already changed the battery for a new one, but the same thing is happenning, only white led blinks.
It is possible to "suddenly" hard brick a device? Because the only thing I did was to unlock the bootloader and install a ROM (Cardinal AOSP 1st and then cm-13.0-20161108-NIGHTLY-condor)
(Sorry for the mistakes, not native english)
WAIFWAIF said:
Hello, everyone!
As you might guess I don't know if my device is hard bricked.
It began when I rooted my Moto E, installed a ROM and then the battery started to discharge way too fast than normal.
I tried to calibrate the battery but it didn't work, at some point the battery only lasted a couple of hours until one day my device turned off and it didn't turn on again.
When I plug the original charger or any other, only the white led blinks, I have already changed the battery for a new one, but the same thing is happenning, only white led blinks.
It is possible to "suddenly" hard brick a device? Because the only thing I did was to unlock the bootloader and install a ROM (Cardinal AOSP 1st and then cm-13.0-20161108-NIGHTLY-condor)
(Sorry for the mistakes, not native english)
Click to expand...
Click to collapse
Press and hold power button for 30 seconds, then release power button
Then connect your mobile with pc/laptop
Let it be charged for an hour
Then reboot it into fastboot and flash stock lollipop
WAIFWAIF said:
Hello, everyone!
As you might guess I don't know if my device is hard bricked.
It began when I rooted my Moto E, installed a ROM and then the battery started to discharge way too fast than normal.
I tried to calibrate the battery but it didn't work, at some point the battery only lasted a couple of hours until one day my device turned off and it didn't turn on again.
When I plug the original charger or any other, only the white led blinks, I have already changed the battery for a new one, but the same thing is happenning, only white led blinks.
It is possible to "suddenly" hard brick a device? Because the only thing I did was to unlock the bootloader and install a ROM (Cardinal AOSP 1st and then cm-13.0-20161108-NIGHTLY-condor)
(Sorry for the mistakes, not native english)
Click to expand...
Click to collapse
don't worry i'm here to help you, once i was also a noob
firstly i need to know your knowledge level do you know how to reboot you phone into fastboot mode
have you installed any custom recovery to you device if yes it'll be so easy to resolve your problem
so give me those info :good:
mklkumar4 said:
don't worry i'm here to help you, once i was also a noob
firstly i need to know your knowledge level do you know how to reboot you phone into fastboot mode
have you installed any custom recovery to you device if yes it'll be so easy to resolve your problem
so give me those info :good:
Click to expand...
Click to collapse
Hey, thanks for your help.
I know how to enter into fastboot mode and all that stuff... but when I try to turn on my device, nothing happen, and if I connect my Moto E to the PC the device manager detects it as: qhsusb_bulk
It appears that the boatloder corrupted itself for some reason, a lot of people have the same issue.
I think it is hardbricked, but if you have some info that could help me, I'd be grateful
1st try to unlock bootloader if you are not able to do that, try to flash stock firmware this may help you
And please send screenshots of all the stuff that you can access in ur bricked device...! It will be helpful for me to understand