Related
I was attempting to flash 2.x using behnaam and lox's rom.
Rom: http://forum.xda-developers.com/showthread.php?t=592596
Here is the HBoot info previous to my tinkering:
HERC XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-1.04.01.09.21
SEP 1 2009,19:18:45
Phone is rooted using adb.
I used unlockr's guide to flash a custom recovery image onto my CDMA hero and that worked fine, here is the guide I followed:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I first moved the radio recommended for the rom by the dev to root on the sd and renamed it update.zip. After, I used the recovery image to wipe, then apply update.zip from sdcard. It seemed to flash fine, as it said please select reboot to complete, which I did, and it completed and rebooted the phone.
Once rebooted it gave me the android installing software image without anything else for a while, then turned off. I cannot seem to awaken my phone with any combo of keys or by plugging it into its use cable. The charging led doesn't even light up anymore.
Well I seem at the moment to be SOL, unless someone can come by and throw me a bone. I really am at a loss as to what I did wrong, as I have always read to do radio first. Not to mention as I watched it install radio it said it was installing radio.
Thanks for the help everyone.
You attempted to flash a GSM ROM to your CDMA phone, this is why your phone is bricked. I'm not sure if its possible to recover, people with more experience than I have can help you there. The problem was flashing a GSM ROM to CDMA. You are not the first to have done it, we all mess up from time to time.
Uuuh Umm...that software was for the GSM hero's NOT THE CDMA Hero.............bless your heart.
Ah **** I thought it was CDMA, guess it was a bad idea jumping into roms while still a noob.
Yea I only got the radio installed, not the rom, although that probably doesn't make a difference.
I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.
Hmm well if worst comes to worst I'm going with what I read on another thread and saying that I was installing the update that it found when I went to phone details and halfway through the update the phone just turned off and won't turn on anymore.
According to the other thread once it is bricked beyond belief and you play stupid they can't prove you wrong.
Best case scenario they replace it, and I won't feel bad seeing as it was a defective phone that is allowing dust to enter under the screen. But that who ordeal is an entirely different rant...lol
Sigh
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
Go......Now......Move with haste...
gu1dry said:
I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.
Click to expand...
Click to collapse
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.
flipzmode said:
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.
Click to expand...
Click to collapse
All is lost!!!!
Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.
unfortunately, flashing the GSM radio on pretty much destroys the phone.
i think its got something to do with the voltage and electricity used by the GSM radios. probably higher than what the CDMA radios use, so you didn't really brick your phone, you 'fried' it in a sense.
sorry bout that... but if you have the equipment protection plan you can probably get it replaced real easily, since the sprint people probably won't really understand what's wrong.
again I am reminded why I dont screw with radios
willowmp said:
Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.
Click to expand...
Click to collapse
Once you do get it replaced and you want to put a custom ROM on it, look at the first page of this forum and you'll find sticky threads regarding four different ROMs you can put on your phone (two production release and two experimental betas).
I would suggest either MoDaCo's rom or Fresh rom. I use Fresh in mine and had no problems (although I have used MoDaCo's before and also had no issues).
Also, if you want to root the phone, there are also sticky threads that will tell you how to root your phone from Windows, Mac and Ubuntu.
Good luck.
Yep thanks everyone.
Yea I figured once no buttons would do anything and the leds wouldn't even light up for charging that it was pretty much fried. Definitely got that sinking feeling in the pit of my stomach.
I definitely should have come into this section specific to my phone and read this info instead of just doing tons of searches and getting mixed up.
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Once again thought, thanks for the help. Especially to a noob that made a real noob mistake lol.
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.
willowmp said:
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Click to expand...
Click to collapse
Well once you are retry the flashing on your new phone, just msg me & I'll give you my contact info & I'll walk you thru it.
willowmp said:
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.
Click to expand...
Click to collapse
while the attempted flash was boneheaded , this (what I quoted) was very smart. I've had them try to reverse the decision and noted on my account in the past. All ended well, but a hard copy of the convo between me and Corporate would have been nice to have.
props for a good idea.
if you don't want trouble with rooting and flashing new ROMs to your phone, try flipz's pre-kitchen. just to try it, i RUU'd my phone and re-rooted it through that app, and its simply amazing. you just sit back and watch, don't even have to do anything.
Ok so its pretty funny but whoever it was who says that once you flash for the first time its addictive, I do have to agree. I will be getting my phone tomorrow because they had to replace it and I will be flashing, although this time I will play it safe and triple check before I get click happy...lol
So what are the danger zones in flashing, like what can brick or kill your phone? I know playing with radios can kill it if the wrong one is flashed, and I know powering off or interrupting a flash will kill/brick, but what else.
I know people said firmware alone usually will not brick you.
willowmp said:
So what are the danger zones in flashing, like what can brick or kill your phone?
Click to expand...
Click to collapse
Well obviously it can brick your phone if you flash the Radio I kid, I kid
willowmp said:
I know playing with radios can kill it if the wrong one is flashed
Click to expand...
Click to collapse
With the CDMA Hero, you do not have to flash the Radio. So if your attempting to flash the Radio, you're doing it wrong.
willowmp said:
I know powering off or interrupting a flash will kill/brick, but what else.
Click to expand...
Click to collapse
Well if the custom recovery is installed (RA-heroc), if the phone looses power while flashing the firmware, you are usually still safe, because you (usually) still boot into the recovery without issues.
Like I already said, if you want I can walk you thru the entire process thru an IM client, Steam, or Skype.
Oh ok thanks, I'm actually headed up to PA for a little trip but definitely will hit you up on that offer when I get back.
I was installing the new Myn's Warm lastnight upgrading from the previous version. It did not install properly and COMPLETELY BRICKED my phone. It won't turn on, can't connect to computer via USB, nothing at all! Anyone else have this problem? OR any solutions other than taking to Sprint?
I doubt that your phone is bricked. Hopefully you DO have a rooted EVO though. I would plug it in and let it charge. Then take out the battery and put it back in and turn it on while holding down power and volume down keys to boot into recovery. Also hopefully you made a nandroid backup so restore that and go from there. I had no problems with flashing RLS5 at all. Hopefully this helps. Otherwise maybe someone with a little more knowledge can help you...
Sprint is DEFINITELY not the answer...
do a battery pull and try to get it to hboot. then try and run the RUU. if not you may have to take it to sprint.
The phone won't charge, won't turn on, can't hboot. I do have backups if I could get it to turn on I could restore it. Had no problems before. I will attempt to charge it as you have suggested but I even put a different fully charged battery in and the phone does not even make at attempt to turn on. I agree I doubt that Sprint is the answer
did you flash any radio updates? any prls, I've never heard of flashing a rom making a phone brick, but definitely heard of radio updates bricking devices.
Sent from my PC36100 using the XDA mobile application powered by Tapatalk
i really doing think his update bricked your phone
This means that while installing Warm you bricked your phone. Don't give his ROM a bad name.
I would recommend trying to charge it and maybe try a different battery, but then just run the RUU and go from that. I had the same problem with RLS 4.
Sent from my EVO using XDA App
If you used the package to update the pri, radio, etc then that may be the problem, hopefully you aren't bricked.
Sent from my PC36100 using XDA App
Are you sure that you didn't flash the radio? I flashed Myn's rom last night and I didn't run into any issues, in fact I've never heard of a rom bricking a phone, that usually happens when a radio flash goes terribly wrong. Anyhow, you can take it back to Sprint since it's still under warranty and they will replace it for $35.
CheesyNutz said:
i really doing think his update bricked your phone
Click to expand...
Click to collapse
ive heard several people say it has in fact jacked their phones up. hence why i have not upgraded to it yet.
I'm not trying to give his ROM a bad name. I've tried many of them and like his the best by far. I'm simply asking if anyone else ran into the same problem. From what some others are posting it may have been the radio update which I did also attempt to install, it was included in the package. So please don't overreact to the post. However my phone is completely bricked unless someone can figure out how to get it to boot up or even charge.
the radio update isn't included with the rom.
it's also been highly advised in the warm thread itself to flash just the radio, then just the wimax, then perhaps the nv/pri, because so many people have been having trouble with the pri update.
the radio combo pack isn't bundled with anything else and, right now, many think it should be avoided for reasons just like this.
not a solution, just clarification and friendly advice for anyone else who's curious about possible trouble with the upgrades.
I updated my radio/pri/wimax and all that jazz before the last Fresh update, so I had no need to this go around. I simply wiped data/dalvik/cache and flashed the RLS 5, with no problems. I did run into issues after I tried restoring my apps + data, but that was a Titanium Backup issue
arcurtis said:
I'm not trying to give his ROM a bad name. I've tried many of them and like his the best by far. I'm simply asking if anyone else ran into the same problem. From what some others are posting it may have been the radio update which I did also attempt to install, it was included in the package. So please don't overreact to the post. However my phone is completely bricked unless someone can figure out how to get it to boot up or even charge.
Click to expand...
Click to collapse
Just my 2 cent.. often times we flash before reading the thread and then complain about a kernel,ROM or theme.
After reading what you said I can only come to the conclusion that you and all the others complaining about the radio update are obviously impatience. All who have had problem with the update on the radio all stated their phone sat on the white screen and they did a battery pull.
Yet the radio update thread says it will/can take up to 30 min to flash. The best way to check your phone would be to use another battery. I have never heard a bricked phone that doesn't cut on. That's a battery issue.
What kernel were you using before flashing?
What ROM?
What's your hboot?
Sent from my PC36100 using XDA App
I'm not complaining on here. I am simply looking for a solution in which I've tried changing batteries and that doesn't do it either. If anything this is a post where others can learn not to make a possible mistake which has caused my phone not to work. I would think probably think the same thing if I were sitting back in your shoes. In hindsight yes I should have flashed everything seperately.
arcurtis said:
I'm not complaining on here. I am simply looking for a solution in which I've tried changing batteries and that doesn't do it either. If anything this is a post where others can learn not to make a possible mistake which has caused my phone not to work. I would think probably think the same thing if I were sitting back in your shoes. In hindsight yes I should have flashed everything seperately.
Click to expand...
Click to collapse
Does the phone attempt to charge when you plug it in?
Sent from my PC36100 using XDA App
I can confirm brick.
I had a rev 4 EVO, and planned on updating from myn's RLS 4 to 5 today...and experienced the "no power on" brick.
Here's what I did.
Update Rom Manager to current (as of 1/8/11)
reboot
Update Clockwork Mod Recovery to current (as of 1/8/11)
reboot
clear/format cache, wiped dalvik cache
Applied calkulin's Radio/Wimax combo linked directly of Myn's RLS5 thread - the one hosted on mediafire
applied Myn's RLS 5 .zip
rebooted
hung at screen where the little android guy is standing next to a box with an arrow...i've seen this before in playing with roms, but can't remember what it actually is
pulled battery, reinserted, tried to power on with no avail
attempted every combination of button and long button pressing, with and without adapters, and could not get phone to light up at all or even resemble a working device in any way shape or form
I took to the store, claimed ignorance, they swapped me out with little hassle to an exchanged Rev 3 EVO. I figured if the tech could get it booted to the point where they even saw s-off, then they could give the phone back to me and i could take it from there.
Nope the phone will not even charge. I've changed batteries and chargers. I am assuming I am one person who has just had extremely bad luck with a random flash. I was running Myn release and did a backup and wipe then phone would not reboot and completely shut down. I got the android guy with the arrow and then it went completely dead and won't turn back on.
dth4310 said:
I had a rev 4 EVO, and planned on updating from myn's RLS 4 to 5 today...and experienced the "no power on" brick.
Here's what I did.
Update Rom Manager to current (as of 1/8/11)
reboot
Update Clockwork Mod Recovery to current (as of 1/8/11)
reboot
clear/format cache, wiped dalvik cache
Applied calkulin's Radio/Wimax combo linked directly of Myn's RLS5 thread - the one hosted on mediafire
applied Myn's RLS 5 .zip
rebooted
hung at screen where the little android guy is standing next to a box with an arrow...i've seen this before in playing with roms, but can't remember what it actually is
pulled battery, reinserted, tried to power on with no avail
attempted every combination of button and long button pressing, with and without adapters, and could not get phone to light up at all or even resemble a working device in any way shape or form
I took to the store, claimed ignorance, they swapped me out with little hassle to an exchanged Rev 3 EVO. I figured if the tech could get it booted to the point where they even saw s-off, then they could give the phone back to me and i could take it from there.
Click to expand...
Click to collapse
That is almost exactly what happened to me. I considered doing the same thing but don't really want to chance getting busted for a rooted phone
i've never flashed a radio update, i'm too chicken lol.
the quickest way to brick any phone is a f'ed up radio flash. or pulling the battery while flashing a radio.
i would take it to sprint and tell them you accepted a over-the-air update and then your phone shut off and this is what happened.
Hey everyone,
I just put the cyanogenmod 7.0.2.1 on my HTC EVO 4G about a month ago. At first it was working fine, now it will just randomly restart not while I'm ever using it, but when it is sitting idle it will just restart at odd times. Has anyone else had this issue?
Everything else with the ROM is working awesome. Please Help.
No issues here, why don't you come up to date and flash the stable 7.0.3.1. Are you running any custom kernels by chance?
Here's the link to 7.0.3.1 just flash over your current rom and wipe dalvik-cache.
http://mirror.teamdouche.net/get/update-cm-7.0.3.1-Supersonic-signed.zip
Oh thanks, been really busy with work, and hadn't had time to check for any updates. I appreciate the help very much. DL'ing the new ROM now.
Upgrade to the newer version. Maybe it'll help? Definitely clear cache & dalvik when you update.
Evo 4G / CM 7.0.3.1 - Tiamat 4.0.2 SBC / XDA Premium
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
misterzeno said:
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
What ROM did you go to?
misterzeno said:
I was running CM7 and went to a different Rom because of the reboots and been fine since. Tried all the usual things but phone would still freeze and reboot. Last one I was on was nightly 65. There are also a few threads around about the ROM bricking phones that it makes crash. As usual, nandroid if things don't work out.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
dirkyd3rk said:
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
Click to expand...
Click to collapse
Yeah I like the CM7 ROM, but just can't take the restarts. I am going to upgrade to the newest stable release and see if that fixes it. I would like to stay with the CM7 if at all possible.
Swype
after the update I notice swype is gone, one of the stock features I like, anyone know where to find that again?
beaukincade said:
after the update I notice swype is gone, one of the stock features I like, anyone know where to find that again?
Click to expand...
Click to collapse
Its probably still there you just have to open a text window long press the text box and hit "input method". Once you hit input method swipe will still be there if it was installed.
dirkyd3rk said:
Its probably still there you just have to open a text window long press the text box and hit "input method". Once you hit input method swipe will still be there if it was installed.
Click to expand...
Click to collapse
no its gone and won't let me use titanium backup to reinstall it either
beaukincade said:
no its gone and won't let me use titanium backup to reinstall it either
Click to expand...
Click to collapse
Do you have the latest titanium backup version? If you can't get it going the swype apk is all over the place lol. *wink wink*
Get the latest version (beta) from their site.
http://swypeinc.com/
dirkyd3rk said:
That's non sense, bricking phones say whaaaaat. I've been running cyanogen roms since the G1 and I've never heard of cm bricking phone's. Don't let this person talk you out of cm lol.
If cm bricks your phone you're (1) an idiot, or (2) shouldn't be rooting your phone in the first place.
Click to expand...
Click to collapse
I have ran many different roms and CM7 was the ONLY one that caused my phone to reboot many times a day. A quick google search can show you threads about owners who had phones that bricked after running CM7. I never said it was gospel, I just dont need my phone rebooting multiple times during the day and it was way more often when I had wimax connected. CM is a great rom but its not the second coming of Android and not worth my phone rebooting during the day.
And I am running Smooth N Sexy V1.2 A sense ROM that looks like gingerbread.
Reboots
I've been through several ROMs now and the reboot problem appears to be not a ROM issue!
Here is the story. I had started with Baked Snack, very good, but I wanted more battery and to try CM and get away from Sprint messaging update nag.
CM worked great, I updated to 7, until the reboots started to happen during heavy use of Angry birds.
So I restored to early CM 6.x, and reboots continued off and on every few days, getting progressively worse.
So I tried Warm 2.2, same issues.
I went back to CM7 and still trouble.
I went to Fresh and It was fine for a week, and then on Friday, (I noticed that Friday was significant), reboots again.
So after a month of this the reboots are so bad that I can't use the phone. I called Sprint, de-provisioned the EVO, went back to my Palm, and then unrooted and went back to Stock ROM, but with no Cell access.
The phone is stable now. As long as it's off the Sprint Cellular network!!!
All of the reboots were related to cellular activity. Messages coming in, ads being updated, calls coming in, tower switching, roaming, or worse of all, no tower signals at all.
I will post back here if the phone remains stable without cellular. But all of the research I have done on the issue has pointed to cellular access. I am on wifi and all the apps and functions are working without issues so far. I am starting a dialog with HTC to see if there is a hardware problem.
The reboots also caused heat in the general area of the SD card...don't know what else is there but I do know the cellular antennas are on that side of the phone. Leaving the battery out all night, after an off state recharge would help stabilize the phone for a while, including cache wipes and factory resets.
But once the phone had been on for a while, or Friday morning would come, the reboots would continue.
I have been a computer nut for 30+years and I solve issues for a living. I strongly suspect the radio hardware or firmware as the culprit in this reboot issue. Every other account of this has had similar connections to the radio use.
Agreed 100% , I've been rooting since the day it first became available and never bricked my phone or got stuck in a boot loop by just flashing a "rom". If I get reboots its because I either flashed a kernel or a very unstable rom. It makes me laugh that you think "CM7" is causing the reboots. You say its CM7, I say it's idiots who probably don't follow directions.
dirkyd3rk said:
Agreed 100% , I've been rooting since the day it first became available and never bricked my phone or got stuck in a boot loop by just flashing a "rom". If I get reboots its because I either flashed a kernel or a very unstable rom. It makes me laugh that you think "CM7" is causing the reboots. You say its CM7, I say it's idiots who probably don't follow directions.
Click to expand...
Click to collapse
Dude its all good, no need to call anyone an idots because we all can have different experiences. Any ROM thread in the dev section has reboot posts some have resolutions, some go to another rom and some seem to be hardware issues. Just like you have been rooting since day one like I have doesnt mean that CM7 is NOT causing my phone to reboot when no other ROM does not.
Your welcome for me allowing me brighten up your day by making you laugh, dont take your personal experiences and spread them across every user like its the ONLY experience.
misterzeno said:
Dude its all good, no need to call anyone an idots because we all can have different experiences. Any ROM thread in the dev section has reboot posts some have resolutions, some go to another rom and some seem to be hardware issues. Just like you have been rooting since day one like I have doesnt mean that CM7 is NOT causing my phone to reboot when no other ROM does not.
Your welcome for me allowing me brighten up your day by making you laugh, dont take your personal experiences and spread them across every user like its the ONLY experience.
Click to expand...
Click to collapse
Im not saying cm roms make sense look like windows 95 lol, and I also don't think cm roms would keep me from jumping ship to a 4.3" iPhone 5 neither. I'm simply saying you're pointing the finger at cm being the cause I'm saying imo its 95% user error that's all. When do you hear of experienced users complain of cm (stable) causing reboots or boot loops? Don't worry ill wait....
dirkyd3rk said:
Im not saying cm roms make sense look like windows 95 lol, and I also don't think cm roms would keep me from jumping ship to a 4.3" iPhone 5 neither. I'm simply saying you're pointing the finger at cm being the cause I'm saying imo its 95% user error that's all. When do you hear of experienced users complain of cm (stable) causing reboots or boot loops? Don't worry ill wait....
Click to expand...
Click to collapse
Once more sir, I spoke from my own personal experience. Plain and simple CM7 was causing my EVO to reboot, and especially when it was on wimax or multitasking. Even from a clean install without restoring anything except for logging into google on the device. I spent 4 days troubleshooting the issue including trying different versions and nightlies. Oh yea..and before you ask the temps were normal on the device no higher than any other time.
But yet again another know it all here on XDA. Dam i must be dumb as **** to been flashing my phone since the froyo root method was released and never had another ROM give me that type of issue. The ROM is not worth me going back to the stock RUU and swapping hardware to since that seemed to be the the last variable after my troubleshooting. Not a big ****ing deal...my phone didnt agree with CM7 like I have seen a small number of other users out there. You dont see me around ROM threads always *****ing and moaning about issues when resolutions or known issues are posted on the first page or doing any other nonsense that I will guess others on here are doing that you may be referring to.
Obvious you are one of those XDA "experienced pros" that are quick think someone has no idea what they are doing with their phone. Post count doesnt mean everything bro.
misterzeno said:
Once more sir, I spoke from my own personal experience. Plain and simple CM7 was causing my EVO to reboot, and especially when it was on wimax or multitasking. Even from a clean install without restoring anything except for logging into google on the device. I spent 4 days troubleshooting the issue including trying different versions and nightlies. Oh yea..and before you ask the temps were normal on the device no higher than any other time.
But yet again another know it all here on XDA. Dam i must be dumb as **** to been flashing my phone since the froyo root method was released and never had another ROM give me that type of issue. The ROM is not worth me going back to the stock RUU and swapping hardware to since that seemed to be the the last variable after my troubleshooting. Not a big ****ing deal...my phone didnt agree with CM7 like I have seen a small number of other users out there. You dont see me around ROM threads always *****ing and moaning about issues when resolutions or known issues are posted on the first page or doing any other nonsense that I will guess others on here are doing that you may be referring to.
Obvious you are one of those XDA "experienced pros" that are quick think someone has no idea what they are doing with their phone. Post count doesnt mean everything bro.
Click to expand...
Click to collapse
You've been flashing since froyo I've been flashing since 1.5 G1 hmmmmm let me think. I will say this though
dirkyd3rk said:
You've been flashing since froyo I've been flashing since 1.5 G1 hmmmmm let me think. I will say this though
Click to expand...
Click to collapse
You win, you obviously have the bigger nerd e peen. I should go back to a flip phone. *Bowing to phone gawd*
You wouldn't be as much as an ass if you happen to suggest ONE resolution to the rebooting.
I'm new to this root/flash etc and it has been fairly difficult getting my head around what it all means. Guides such as Intratech's http://forum.xda-developers.com/showthread.php?t=1671969 are extremely helpful and much appreciated but still aren't really for noob's like me who don';t know all the acronyms or processes. (and where is the THANKS button - I see the thanks scores in the side bar but be buggered if I can find the way to thank someone)
As an example of what I mean, a guide such as siberian tiger's http://forum.xda-developers.com/showthread.php?t=1674286 clearly contains valuable info but I have no idea which ROM to choose or why there are so many different ones.
Also, where do you download them from?
I got often sidetracked while trying to find out things, and nowhere did I find a set-out process that didn't require considerable research to work out what was being said. But I eventually got to where, when my new SGS3 arrived, I was ready to try stuff on it.
First I rooted it. There was confusion here because it wasn't clear that CF Root was a part of a larger process that included CWM, but I found it in Chainfire's http://forum.xda-developers.com/showthread.php?t=1695238
Then my phone found an update - it's German market from Kogan so I went from i9300XXLEF to i9300XXLG8. I started in on removing the German stuff not vaild here but then realised I would be better doing what I originally wanted which was installing a stock Aussie ROM. First I tried out TriangleAway (with trepidation considering the rather dire warnings about bricks ) and it worked just fine, resetting my counter.
I then used CWM to run a backup of the system to my external SD.
So, using Odin I VERY carefully followed the process in Chainfire's guide.
All went well for a while...
Then the phone booted up and I got a message about Contacts not starting and then android.process.acore 'stopping'.
The heart missed a beat. I clicked OK, thinking (rather desperately ) 'it's OK, probably just a part of the set up process.'
Many clicks later, with the new system appearing in brief flashes in between 'acore' messages the gaps between heart beats became extremely long.
I forced it down (holding power for 10 secs) and started it again. 'It's better! It's going past the start up! it's...' BUGGER! there it is again!!!'
Searching frantically I found Faryaab's http://forum.xda-developers.com/showthread.php?t=1646610 thread with a lovely Youtube clip by TotallyDubbedHD (found at http://www.youtube.com/watch?v=_8Tga_yKywc&feature=player_embedded
In it he mentions wiping the data, cache and dalvik cache. So I followed the clip and wiped them all, then ran the Odin process again.
Same result. Looking for paddles for heart-starting machine at this point.
AND I couldn't seem to boot into download mode any more. AND the Recovery mode was different now, with far fewer options. I tried using Recovery to Restore my backup - it found it, started to run it, then failed.
I'm not sure what the issue was with the Download option for start up, maybe in my distraught state I wasn't holding the buttons down properly or something, but after using the truncated version of recovery to wipe data and cache again, I finally got back into the Download... I went back to Odin and ran the latest German ROM - my reasoning was (not good at this point ) that maybe the phone needed the German stuff, even though I'd seen nothing about such problems in my 4 days of research on XDA. I also wondered if the Aussie ROM was corrupted...
The German one installed and started, but after about 1 minute I got the 'acore' msg again. Wondering how I was going to tell the missus I had broken my phone after less than 12 hours, and getting increasingly concerned about the lateness of the hour (as a PC support person I learned early never to do anything major after 10PM :lol I used the now restored Recovery mode to wipe data, wipe cache, wipe dalvik, then, with a prayer to the gods I don't believe in, I ran the Aussie ROM onto it again.
10 minutes later it started, sweet and fast, no errors, and no German-only icons.
I have a brand new, Aussie phone! I did some downloading of Apps to get it al back how I had it and went to bed.
I can't seem to do Thanks in threads (or even post in some of them yet) but I wish to thank wholeheartedly all those who spend so much time trying to document all the confusing issues involved for those of us learning a new language. It's been a bit of a slog but I'm getting there...
(I got to bed and told the wife, rather proudly, 'I broke my phone, AND I fixed it...'
I didnt root my phone, but i got the acore message too. Got shot of tthat & still my stock messages are still screwed. 100% agree that for a newbie nothing is crystal clear. "Search for this" "download that" not ideal wthen you are fretting on wether u just your phone up. Resisted the root, route until i see something that makes perfect sense.
The frustrating thing though, nobody believes you followed it to the letter, no matter how many times you explain it, simple stock flash (hence why i did it), even the wife cooda done that, but still had problems...still Think the 3 network was the culprit.
Get used to that feeling.....
I've been flashing phones since my x8 (had a Samsung galaxy 5, galaxy S1, nexus s, galaxy nexus and now the S3)
I've had plenty "I've definitely f*cked it now" moments.
To be honest those moments are half the fun of flashing stuff to phones.
Crackflashing is an addiction and those moments and when you sort them are like a really good hit.
Best way to learn is to make mistakes.
Sent from my GT-I9300 using xda premium
I made a few mistakes and bricked my previous phone, an Xperia Pro MK16i, and learnt in the process. Haven't had a heart stopping moment on my S3 yet *touches wood*
Having said that, it is thanks to the tireless community at XDA that has ebbed me on to take the (minor) risks in order to reap the (humongous) benefits of tinkering with my phone. So thank you all.:thumbup:
Sent from my GT-I9300 using xda app-developers app
You reminded me the first time i tried to root my Galaxy S .
It was a disaster
The phone had stuck in the root screen(z4 root some will remember)
for over 20 minutes and i didn't know what to do.
I was searching the xda for an answer but nada.
I thought that's it you just spend 600e for a brand new phone and you destroyed it
I plugged the battery out went to bed and the other day with more clear mind i read all the guides for rooting from the start and voila i did rooted it my heart came again in the place where belongs
Don't hesitate to post in my thread your questions.I'll try to help as much as i can
Regards
Tiger
Sent from my GT-I9100
This is for those who has acore issue.
A little patience is require but basically you still can navigate around in the phone but very slowly as you can only navigate after you dismiss the force close message.
Go to your System Settings->Applications Manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select the All tab.
Look for Contacts
Click on Clear Data.
Restart the phone.
This help me last time when I had this issue.
Sent from my GT-I9300 using xda premium
My first trail with flashing and rooting was on my mum's galaxy tab, it was a horrific experience since i might brick it at that time but it went without a problem.
After that i started flashing phones s1, s2 , s3 . But to be honest, without the help from the guys in this form i would have deff bricked many phones.
I had a few of these moments on my LG GT540 what worried me was I had no replacement phone, you will get used to them and learn how to solve them in no time.
Sent from my GT-I9300 using xda premium
Happy flashing there mate!
Anything you need ask or pm me,i like helping!
First android phone i ever flashed was my Galaxy S1...(btw i absolutely loved this phone!)
I remember i had bricked mine and it stayed in SAMSUNG logo,we had issues with the 3 button combo back then!
The bootloader wouldn't let me go to download mode to use ODIN!
I was sooooo sc***ed! xD
It was the most expensive phone i had ever bought and i freaked out!
Thank god we built a homemade jig with my informatics proffesor back then and we revived the damn thing!
Great guy..
Point is if it's a software error it's 99% fixable,even imei can be fixed!
(happened with mine... thank god i had a backup!)
The worst thing as an effect would be...losing your apps/settings?
So don't worry...
Don't worry everyone has had their ups and downs and for me that's a part of the beauty of modding (rooting/unlocking/...)
I still remember the bootloader unlocking of my HTC legend.
You needed burn an iso CD and set your BIOS of your PC to boot from CD then run that cd and connect your phone.
Before the process begun it stated (about 10times) that you should NOT disconnect your phone in any case. The fact they mentioned it so much made me kida worried.
But I took a deep breath and continued. You had to follow some steps answer some y/n questions and then you needed to boot your phone in fastboot
And time it so that you hit enter on your PC about 2sec after it booted into fastboot...
which I did..... but the script was still stuck on waiting... And the warning message was still there visible in the top of the script.
I started hitting enter again and again but that obviously didn't help.
After 30 min I realized there was nothing else I could do then unplugging the USB and pulling the battery. At that point I was convinced I just bricked my €450 phone.
You can't imagine how happy I was when I found out it still booted. So I rebooted my PC did some more research and tried again. And finaly after 2days and 10 attempts I got my unlocked bootloader. That victory feeling was o so great!
I must say things are getting easier for the end user and because of that it's partly losing it's charm. But it's nice too read your stories and see that some of you still experience that victory feeling!
that heart stopping moment is the best part of this crazy debranding flashing rooting customizing "thing" we so love to do and my experience wouldn't be complete without it. been at it since windows phones came out and i really think i wouldn't stop hahaha!
btw bricked a couple but jtag is always there to save us ass
Sent from my GT-I9300 using Tapatalk 2
bonzai1888 said:
I didnt root my phone, but i got the acore message too. Got shot of tthat & still my stock messages are still screwed. 100% agree that for a newbie nothing is crystal clear. "Search for this" "download that" not ideal wthen you are fretting on wether u just your phone up. Resisted the root, route until i see something that makes perfect sense.
The frustrating thing though, nobody believes you followed it to the letter, no matter how many times you explain it, simple stock flash (hence why i did it), even the wife cooda done that, but still had problems...still Think the 3 network was the culprit.
Click to expand...
Click to collapse
OK, the difference between what I saw on the youtube and what was in the guide I used seems to have been the parts about (in Recovery) wiping the data and deleting cache and dalvik cache. I might be wrong and one of the gurus here could clear things up...
But deleting or changing Contacts was clearfly, in my case, not going to be a solution - Touchwiz was the first error and there were a couple of others.
Some history... I have been doing User Support and Desktop Help as well as Sysadmin since 1987. I am a noob to Android but definitely not to computers nor effing around with system partitions.I LIKED DOS and I can think my way through software issues with an aplomb that users have called for. In other words, I am not a nuff-nuff.
But the confusion generated by ST's Guide where I can just run CF-Root-SGS3-v6.4 or CF-SGS3-CWM-v5.5-v1.5 (forgive me if I am quoting the wrong poster for the thread) and then find threads telling me to install Android SDK so I can access ADB to root my phone is nothing short of awesome.
I rooted my phone. I tried to run the approved Aussie ROM on it, and then had to recover things so it would work. Did I miss a step? Was it that even though my PC recognised and allowed Odin access to my phone I should have first run Samsung USB drivers? Should I have found out what an 'Insecure kernel' is and installed one? WTF is an insecure kernel and what programs give you one if you DON'T want to run a DOS window and do command line commands?
In all the hundreds of ROMs, Kernels. and other installations presented here on site, what, as a Noob, should I be looking for? The version numbers don't mean much to me. I prefer to stay with an Aussie version but if there's a JB out there that makes my phone run better, longer, faster, I could give a flying eff when Telstra decides to update my phone... but apart from a thread offering 'buttery smooth' menu motions, none of the ROM's seem to have descriptions of WHY I should install them.
I have bought Titanium Backup and System Panel on recommendations of a thread about battery life that seems to have nothing to do with battery life but has some fascinating stuff in it anyway (see http://forum.xda-developers.com/showthread.php?t=471521&page=4 and I am backing up every time I make changes that I like, but some of these programs seem to duplicate what others do - e.g. there's a File Explorer download that offers rooting, kernel and ROM installs AND lots of file-type options, but given I have CF Root, CWM, Super SU, Titanium etc. why would I need another?
I am happy to learn. I don't mind paying for the work others have done. As the OP documents, I am willing to take a risk with my hardware to try things out.
But...
is there anywhere on here where anyone has done an Intro to Android systems?
Is there a Glossary somewhere to explain all the acronyms?
Has anyone done a step-by-step of what you replace and why to get a fully functional and fast phone?
Is there a location somewhere on site where the ROM's can be downloaded? (what I have seen is mostly references to ROM's with no links to how to find the MD5 file)
Is there somewhere on site where the features of particular ROM's is listed?
If I am rooted, what else do I need to be able to flash (say) the buttery smooth JB?
a good poem.
OP that was a good poem
you should commission a new book, 50 shades of rooting
nice read
I touch wood never hard bricked my phones. Toyed around with N900, installed android on maemo got in bit of a mess but thanks to maemo community got out of it.
Jailbroke both my iphone 4 and wife's 4S. Flashed few fws on Optimus 3D. Been installing custom FW on S3 since I got it in late May, thanks to indie who helped make the first custom rom for S3 and even not having S3 himself as world wide launch happened in June.
Anyway my worst moment came when i plugged my external 500 WD drive to S3 via OTG cable and drive was detected for little time but then disappeared. I plugged it in the pc to check it and it showed unrecognized usb device. I still thought it wasn't big deal and tried it on my NB and still same. After it didn't show up in any of my media players (a have a few) i got panicky. It had 2 years worth of data/movies/music/backups and was full to the brim.
I searched and searched on the net and the only solution some said was that the port might have got damaged and needs to be changed. Then found on youtube how to take it out of its casing and thought if i could just hook it to my pc with sata cable it will hopefully work.
I took it out and to my shock WD had soldiered some weird connector on it and it could only connect through it and the standard sata port wasn't there.
I had all but given hope and posted it on one website about this issue and found one nice old (self proclaimed) gentleman posted that i should try to put it in freezer overnight as i have nothing to lose. I thought what a joke but did put it in the freezer wrapped in thick plastic bag.
Next day i took it out and thought just might give it a try and plugged the drive in the pc and to my amazement and relief it came up with message of options of opening the device. WOW i must admit after 20+ years in IT, handling components biz, trading /selling of components, building PCs for others and myself I never heard about this tip. I can't thank that man enough and i did recover another drive by doing the same. Both are after 1+ months working fine
joshua3_ph said:
that heart stopping moment is the best part of this crazy debranding flashing rooting customizing "thing" we so love to do and my experience wouldn't be complete without it. been at it since windows phones came out and i really think i wouldn't stop hahaha!
btw bricked a couple but jtag is always there to save us ass
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
The heart-stopper is not the best thing - getting past it and fixing things is the best part. It may be that we wouldn';t enjoy the fixing as much without the previous heart-stopper but that 'oh, f**k' moment is still nothing to wish for...
@spaco22 - in 19876 I bought an XT PC so I could write my SciFi Novel. The pc took over my life and to this date I haven't done much more nthan occasional spurts of creativity in the writing field - did do some poetry though. :lol:
@Sak500 - the freezer trick has rescued a number of drives over my years. Including ones making the dreaded 'tick...tick...' noise. You were lucky - as a drive dies you get about 15 minutes to get the data off before it goes to god. And the freezer trick doesn't usually work twice... AND you need to put it in a sealed plastic bag... unlike a client of mine who sat it in their chest freezer and complained to me it didn't help and when I got there, there was still a small puddle of melt under the drive. :silly:
Mind you the best was a Manager who brought me his almost new laptop and told me it was warranty because it 'just stopped working' and when I took it out of the bag, and checked for physical case stress damage, found a car tyre track across the back of the case. Like Lenovo would warranty for running over the thing in a Territory... :lol:
In spite of my intro to all this, I am looking forward to the journey. Y'all could help by giving me reasons for my missus letting me flash her beloved GNote from United Emirates... *innocent look*
I've got a super pro tip: Backup the EFS partition!!!
Almost every other issue is solvable with a bit of digging on this forum. An EFS partition format would need the assistance of Samsung Service Centre personnel, and a good explanation as to how it came to be.
http://forum.xda-developers.com/showthread.php?p=18524176 works for me. This is the first thing I did after rooting using CF-ROOT. Also, CF-ROOT is the safest "first thing" as it only flashes a new recovery image and no kernel nor any ROM.
Guides can only be made so noob friendly, so I'm afraid some acronyms and finger crossing are inevitable. My advice would be to read, read and read some more before attempting any actions that may brick your phone. Remember nandroid is your friend and as long as you read the threads and follow the instructions help will always be there.
Sent from my GT-I9300 using Tapatalk 2
Erahgon said:
I've got a super pro tip: Backup the EFS partition!!!
Almost every other issue is solvable with a bit of digging on this forum. An EFS partition format would need the assistance of Samsung Service Centre personnel, and a good explanation as to how it came to be.
http://forum.xda-developers.com/showthread.php?p=18524176 works for me. This is the first thing I did after rooting using CF-ROOT. Also, CF-ROOT is the safest "first thing" as it only flashes a new recovery image and no kernel nor any ROM.
Click to expand...
Click to collapse
Great tip and one I'd like to follow up on but the server hosting it seems not to be available.(see screenshot below) I'll check back and maybe look on google-play as well. Thanks.
@ghostofcain - been doing that. Check the screen shot of my Chrome window :lol: But there comes a time when one must try some of the things one has been reading about and I'm enough of a sysadmin that I follow system instructions very precisely - had to rebuild a server once, unpaid, over the weekend, because I skipped a line in an upgrade process.
So when strange things happen, and you're trying to think without that reassuring 'thud-THUD' pulse that you don't miss until it isn't there, it isn't all that reassuring to know you've done all the right things, there's just a mad moment of internal panic when you second guess and try to blame and desperately, after long training in PC's, try NOT to touch ANYTHING until you understand what just happened. :lol:
Another question - can someone point me to the download area? It has been mentioned in a few threads and I have a PM telling me that is where ROM's etc can be found, but I can't seem to find a link to that page or server. Feel free to tell me I'm being dumb...
And weirdly, I found the thanks button in posts and I swear I looked there before and it wasn't there. Maybe you can't thank until you've posted or something?
I've often told my customers, 'if computers/windows behaved as they are meant to I wouldn't have had a job for the past 25 years...'
Hm... image doesn't show in preview... it's attached as well.
Trying HTML...
HTML:
<img src="http://farm9.staticflickr.com/8442/7890771458_f79f6a6635_z.jpg" width="640" height="357" alt="My Chrome Desk">
Nope, looks like attach is it...
Once you learn all the Voodoo tricks to fixing half of your problems with Roms and Kernels.. or soft bricked devices, you'll be smooth flashing..till then you must go thru a few bricks, a few data wipes, a few crashes, and a few replacements
YoungAceAtlanta said:
Once you learn all the Voodoo tricks to fixing half of your problems with Roms and Kernels.. or soft bricked devices, you'll be smooth flashing..till then you must go thru a few bricks, a few data wipes, a few crashes, and a few replacements
Click to expand...
Click to collapse
LOL... I can live with most of that - bricking and replacements I am trying to avoid. The missus will not look kindly on having to buy a new phone...:fingers-crossed:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Ciclop said:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Click to expand...
Click to collapse
Just make sure anything u do you read the thread and defiantly the op and only flash stuff that made for the N4 u should be good. Read read read and learn. I've only bricked one phone and I know what I did wrong its very hard to brick a phone so long as u don't just go flash stuff u dont know what it is.
Oh yea don't over clock your phone and run benchmarks its stupid and has fried a few also. I'm onderclocked to 1134 and I still run smooth as butta.
Sent from my Nexus 4 using Xparent Blue Tapatalk 2
Ciclop said:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Click to expand...
Click to collapse
For a REAL hard brick on a Nexus device, you really have to do something wrong. Like I did with my Nexus S .
A real hard brick, one that isn't even repairable with a JTAG brick repair service, it never happens with a Nexus device. Well, ALMOST never. I made it happen. I don't even know what I did wrong, but apparently I screwed up the radio. Even the best of the best (Adam Outler) wasn't able to repair it. It happened the day after I installed a new ROM and a mod. The battery drained really fast. After it was dead, I plugged it in the charger, booted up my phone, started the browser, and BAM. Dead. Forever.
But I wouldn't worry about those things. Just don't do too much overclocking, because there are ways to screw up the hardware inside. Almost all bricks are fixable. If you can access fastboot mode you're okay. If you can't, there are still ways to fix it, but it might cost you some money. I don't know if Adam Outler's Unbrickable Resurrector tool works with the N4, but that's also an option if you think you really screwed up.
1) Make sure that you never flash a file that wasn't designed for the Nexus 4 (MAKO)
2) Make sure that you don't have empty batteries when you flash. 50% would be a safe minimum (though I personally frequently flash with much less than that)
3) Flashing radios / bootloaders is traditionally amongt the most dangerous operations that you can do. Make sure to check MD5 on all radios (you can check on every file if you want to be super careful)
Note: the reality is that with a nexus device, it's almost impossible to brick your device. Even if you do all of the things above wrong, you'r probably still safe. BUT, you were looking for advise--so follow those three points and you should be fine.
OP, read the link in my signature about toolkits and it will answer your question.
Sent from my Nexus 4 using xda premium
Thank you all for quick replies!
I only plan on flashing Franco's/Faux's kernel, hopefully everything will go well
unlocking the BL on a nexus is very easy. I am not sure if you need a toolkit for that.
but yeah use one if you feel more comfortable with it.
also as of now do not overclock the processor as that has been causing some bricks AFAIK.
Androyed said:
For a REAL hard brick on a Nexus device, you really have to do something wrong. Like I did with my Nexus S .
A real hard brick, one that isn't even repairable with a JTAG brick repair service, it never happens with a Nexus device. Well, ALMOST never. I made it happen. I don't even know what I did wrong, but apparently I screwed up the radio. Even the best of the best (Adam Outler) wasn't able to repair it. It happened the day after I installed a new ROM and a mod. The battery drained really fast. After it was dead, I plugged it in the charger, booted up my phone, started the browser, and BAM. Dead. Forever.
But I wouldn't worry about those things. Just don't do too much overclocking, because there are ways to screw up the hardware inside. Almost all bricks are fixable. If you can access fastboot mode you're okay. If you can't, there are still ways to fix it, but it might cost you some money. I don't know if Adam Outler's Unbrickable Resurrector tool works with the N4, but that's also an option if you think you really screwed up.
Click to expand...
Click to collapse
My N4 its bricked, I contact Google for RMA. Now, my history...
N4 bought 13/nov.
-Rooted with Nexus 4 Toolkit
- ROMS installed: 1- Stock (default) 2- Minco 3- Xylon (when i got bricked)
- Kernels:1- Stock (default) 2- Franco 3- Faux (when i got bricked)
In kernel Ops: (Last Faux beta kernel)
- Underclock: (YES, READ, UNDER): 1mgz at max
- Undervolt: -137 mv all freqs
- GPU Downgraded to 200mhz
- Screen settings changed
- Hapatic feedback downgraded to 50%
That was my config. Now comes the drama...
My phone was perfectly OK at less for 2 days with that kernel and ROM combination (because i've updated few days before got bricked) So, my phone even with the downgrade config was so smoth and everything was perfectly ok.... the night of new year, when I was taking a shower, my N4 was charging SO SLOW, i dont give a f*ck and continue my night so normal, then I went out to my gf house, i have like 30 % and decide to charge again, starts charging slow again, now im worried about it so i decide to restart the phone, and problem still there... but now the device was overheating so much and the phone got discharged because i got to go, when I come to my house in the morning, i put the charger, the only thing it do is blink red led, nothing else.
Conclusion:
When your phone got bricked doesn't mean you have the guilty, because mine was STABLE for at least 2 days, for my, it was an hardware prob.
Now, the only way, RMA.
So if I was you, I lock my bootloader again.