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.
So my learning experience started when I decided to do Ryanza's "unlagfixme". It ran completely fine until it decided to restart itself. Once it restarted, it got to my "S" booting screen and then my screen turned black, and nothing else happened, but my bottom buttons would light up when i touched my screen. So i took the battery out and put it back in and restarted. Same thing over and over.
Here's where it was time to research. Only way i knew about getting to nandroid to do a restore was through rom manager. So after a little research, i found out about booting into recovery with adb (adb reboot recovery). Did that, and clicked reinstall packages, great! got into nandroid and was able to restore.
Then I got the crazy Idea to flash Vibrant6 from Eugene. Did that succesfully through nandroid then wanted a lag fix, so i flashed Ryanza's lag fix again to vibrant6. Phone hosed again! now it would only pop the vibrant screen and hang there. Time to do research again; this time i didnt have nandroid flashed so it was a little more difficult than before.
after hours of research to fix my phone I came across a post of how to use odin step by step. learned to boot into download mode, set up odin, flash...Did that, and odin would hang on cache.rfs, onto more RESEARCH...turns out i could install without a pit and that did the trick. after i was able to flash that ROM i was then able to get rom manager, boot into nandroid and backup my most recent backup (right after installing vibrant6) and then restore all my apps through titanium backup.
I feel today aside from the ****less scares...it has been a blessing day because I have learned: How to boot into recovery with adb, boot into download, use adb, use odin, flash a rom through odin and clockworkmod, restore TB backups, etc. After having the phone a little over 2 weeks and not knowing anything about android, i think these are great improvements and are things i didn't know how to do.
Today has been a great newb learning day. I guess you force yourself to learn things when you most need them huh! All the tools needed are here, more than likely whatever is happening to you has happened to someone else before. Search is your best friend. However, if I can help some of the other newbs to get up to speed, I'd be glad to. We have all been there right?
I'm so happy to be a part of this community!
Congrats, sounds like it was fun and nerve wracking. Having come from a G1, I was a little surprised at how relatively hard it is to flash a new rom to this phone, I guess the G1 spoiled me. I'm pretty sure I'm going to have to take the same journey that you've been through at some point, but for now I'm just gonna enjoy it.
dcontrol said:
Congrats, sounds like it was fun and nerve wracking. Having come from a G1, I was a little surprised at how relatively hard it is to flash a new rom to this phone, I guess the G1 spoiled me. I'm pretty sure I'm going to have to take the same journey that you've been through at some point, but for now I'm just gonna enjoy it.
Click to expand...
Click to collapse
Aboslutely, it was both! I loved it so much though because i came out as a winner and learned so much while at it. I enjoy this kind of stuff though, troubleshooting, debugging, etc. Hence being a VB/C# programmer for a living!
What a great post! Glad you were able to learn all that. Yeah, it was forced, but it still all worked out for the best.
Now off, and learn how to MetaMorph, and build your own Themes! :cracks whip:
WilliamStern said:
What a great post! Glad you were able to learn all that. Yeah, it was forced, but it still all worked out for the best.
Now off, and learn how to MetaMorph, and build your own Themes! :cracks whip:
Click to expand...
Click to collapse
hahaha...That sounds like whole different world that I haven't even looked into
Will definitely get on that next!
Without reading your post, I was tempted to be a troll and say "cool story", but I read it and my hat's off to you. Good on you for learning the basics. Keep up the good work!
XfooYen said:
Without reading your post, I was tempted to be a troll and say "cool story", but I read it and my hat's off to you. Good on you for learning the basics. Keep up the good work!
Click to expand...
Click to collapse
Thanks! I can only look up to some of geniuses in here and hope to be at their level one day!
Thank goodness I did my hours of reading pre scares and I was already in the know on what I had to do to flash back to what I was before and try again, but I def feel for your situation and applaud your using the search feature instead of just making a "help me!" Post like you usually see for a topic that's already been covered....
Btw post final vibrant 6 flash did you ever get your lag fix correctly setup?
Pooped from my Samsung Vibrant using XDA app...
Dont mind the skidmarks...
awesome! forums have been a godsend. Now i can get information from the actual users rather than corporate generalities for whatever question i might have.
Holy twinner batman! I had almost the EXACT SAME EXPERIENCE YESTERDAY! Although I skipped the part about adb and went straight into the ODIN download. THIS is exactly why I will NEVER own a JobsPhone!
Your not a newb anymore. Having gone through all that heart sinking, palm sweating, stomach churning, experiences.
p()()pypants said:
Thank goodness I did my hours of reading pre scares and I was already in the know on what I had to do to flash back to what I was before and try again, but I def feel for your situation and applaud your using the search feature instead of just making a "help me!" Post like you usually see for a topic that's already been covered....
Btw post final vibrant 6 flash did you ever get your lag fix correctly setup?
Pooped from my Samsung Vibrant using XDA app...
Dont mind the skidmarks...
Click to expand...
Click to collapse
I did not. I tried all three ryanza fixes (update.zip, batch, one-click) and none of them worked for me. Couldn't get the script on modaco to work for me. And everytime i undid the lagfix it crapped my phone out. So i nand'd back to pre lag fix and I'm still debating whether I will backup to stock+lag fix (really liked the snapiness, aside from quadrant scores), or to play with Vibrant6 for a while and see if it is as snappy as stock with the lagfix or better. still debating.
ConceptVBS said:
Your not a newb anymore. Having gone through all that heart sinking, palm sweating, stomach churning, experiences.
Click to expand...
Click to collapse
Hahaha there's sooo much to learn about these phones that I feel i will be a newb for a long while yet
achild said:
after hours of research to fix my phone I came across a post of how to use odin step by step. learned to boot into download mode, set up odin, flash...
Click to expand...
Click to collapse
Where is this post?
I had the same thing happen to me. It sucked, thank god for the support here at xda. You guys made it so easy to fix. Thanks
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Don't know sorry but it's so fun
We spend so much time to avoid that happen ...
Sent with my GT-P7500 CM10
corybantic said:
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Click to expand...
Click to collapse
Try flashing recovery in odin and disconnect it in the middle
...
Flash a rom with odin and use repartition.
This will brick your device.
Sent from my GT-P7500 using XDA Premium HD app
Flash a rom from another device works, too.
corybantic said:
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Click to expand...
Click to collapse
Well, the other ones pretty much covered your query. I want to ask what happens if your program fails? And you mean soft or hard brick?
Sent from my amazing 10.1 galaxy tab
Like all the folks before me, flashing wrong rom from other device probably would brick it... BUT to really, really brick it messing up the bootloader is always a good way to go.
Can you short it out?
Ooops,I guess I should've been clearer! I'm trying to brick it without rooting it, i.e., perhaps some code that I could input at the bootloader?
Panos_dm said:
Well, the other ones pretty much covered your query. I want to ask what happens if your program fails? And you mean soft or hard brick?
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
Well if it fails, then I guess I gotta try - or come up with - a different program. The thing is, I had two SGT 10.1, one recently went back to Best Buy after the ICS update started freezing up my internet (not tripping tho, I was able to get a raincheck for the Note 10.1! Good thing I got the Product Replacement Plan!: victory, so I have literally a spare SGT 10.1 to mess around with. I've already rooted it and flashed different roms as well as unrooted it back to factory settings. So, to be honest, I simply have a tablet for having a tablet's sake right now.
I'm actually trying to "hard" brick it. The thing is my little program works on a "soft" brick palette so it has (usually) been able to unbrick an inadvertantly bricked phone as well as the SGT 10.1. I'm trying to see if I can brick it without rooting it to see if I can resuscitate it back to working condition.
"hard"brick it means you'd have to produce an hardware faillure, You wouldn't be able to fix an hardware failure unless you change the part that failed.
IE: Your memory chip has fried, your CPU overheated FUBAR, this kinda things
Well mine is pretty screwed. Wish I knew how it happened so I can tell you, but I don't. Yesterday I watched a movie on it and put it on the table. Later when I wanted to use it, nothing happens.
If I plug it into my PC I can get it into APX mode, but thats all. The backlight doesn't even go on. On NVflash I get the rcm version = 0x4, which means I got a locked bootloader.
When on charge, also nothing happens. The camera flash just flashed about every 2 seconds. Same thing when I keep the power button held in.
I could try your app for you on mine if you want...
sigh let's start the horror story. So I rooted my verizon LG G2 (VS980) phone yesterday using this guide:
http://theunlockr.com/2013/10/25/root-lg-g2-versions-video/
I found that pretty easy so i decide to then be more adventurous and load cyanogenmod 10.2 on my phone since I heard it was officially on nightly release for verizon phones. So then i came across this youtube video explaining how to do this:
http://www.youtube.com/watch?v=_s3eO-jvNWk
I make 3 mistakes in this process:
1. i don't do the settings part
2. i don't wipe the phone
3. and most importantly i download the wrong cyanogenmod 10.2 version. I put the 802 international version on it instead of the verizon version.
Now my phone is stuck with fastboot with a black screen.
I can go into download mode and have tried the following guides:
http://forum.xda-developers.com/showthread.php?t=2432476
In this one it gets stuck at 49% loading when i use the verizon version
the second:
http://forum.xda-developers.com/showthread.php?t=2448960
here when i start to load it says my device is the wrong model because i loaded the wrong cyanogenmod
Now that i know why my phone wouldn't load the verizon rom (because i had cyanogenmod 802 international). I have successfully loaded the stock 802 rom on my phone. the bad part is the touch screen is all wacky and i can't get into setting to go into developer mode and finally fix my phone.
Any ideas on where i can go from here? If i could just get into developer mode i can restore everything by loading TWRP then loading the cyanogenmod for verizon.
Just an idea, but maybe you could use a mouse via OTG in the meantime.
Abnovitas said:
Just an idea, but maybe you could use a mouse via OTG in the meantime.
Click to expand...
Click to collapse
thanks i didnt know i could use a mouse. I will try to find a cable that will allow me to do that.
I was able to help a few peeps with the same prob get back to stock. Pm me if you need help.
some updates.
I didn't get the mouse to help me around the touch screen. I just memorized where all the new locations where for example the middle of the screen clicked the bottom left
I have been able to get this european 820 stock ROM running on my verizon phone and have it in debugging mode.
All the other flash methods are failing me because i get "different model" error.
I'm currently trying to update my build.prop file so i can get the other flash methods to work since this is the file they are looking at to see if it's ok to flash with the rom you have select. Personally i find that kinda silly. I mean i'm flashing the thing give me an option that say "are you sure you want to do this? you are about to flash your phone with an compatible rom". Yes i'm aware i put the wrong rom on the thing now flash my phone with this one.
Oh it would be great if someone out there could post me their verizon build.prop. Would really appreciate that.
update
don't change the build.prop model number to VS-980. my phone is now in a reboot cycle.
I can get into download mode but i fear that i still won't be able to flash with the right rom because that build.prop is wrong. can i skip this verification step?
I also have twrp running but again it's the European version so the touch screen doesn't work properly. i can't swipe across to do anything even if i wanted to.
I would just do this and start over...http://forum.xda-developers.com/showthread.php?t=2448960
WHY?
elseif said:
update
don't change the build.prop model number to VS-980. my phone is now in a reboot cycle.
I can get into download mode but i fear that i still won't be able to flash with the right rom because that build.prop is wrong. can i skip this verification step?
I also have twrp running but again it's the European version so the touch screen doesn't work properly. i can't swipe across to do anything even if i wanted to.
Click to expand...
Click to collapse
I can't help myself, I have to speak up..
nothing against the OP BUT this is exactly why I DO NOT try to do this stuff. There's really no benefit that the stock ROM on this phone cannot do...and more...and I read so many reports of people turning their beautifully working phones into little black plastic paper weights. Simply not worth the trouble, time, and possible money :silly: to get a little more screen space, or a smaller NAV bar, or whatever.
And then so many people want KIT-KAT...WHY? Will it REALLY be that much better than what this thing can do now? Or will it just introduce BUGS like every other update always does to an android device? If, and when this phone gets an update to KIT-KAT or whatever version they decide upon, and it actually works without new bugs, then I will be pleasantly surprised. Here we have what just might be the best android phone to land on earth so far, and people want to "improve" it??? My $0.02
jaseman said:
I can't help myself, I have to speak up..
nothing against the OP BUT this is exactly why I DO NOT try to do this stuff. There's really no benefit that the stock ROM on this phone cannot do...and more...and I read so many reports of people turning their beautifully working phones into little black plastic paper weights. Simply not worth the trouble, time, and possible money :silly: to get a little more screen space, or a smaller NAV bar, or whatever.
And then so many people want KIT-KAT...WHY? Will it REALLY be that much better than what this thing can do now? Or will it just introduce BUGS like every other update always does to an android device? If, and when this phone gets an update to KIT-KAT or whatever version they decide upon, and it actually works without new bugs, then I will be pleasantly surprised. Here we have what just might be the best android phone to land on earth so far, and people want to "improve" it??? My $0.02
Click to expand...
Click to collapse
Totally unnecessary to make this post. Unless you have something to contribute regarding the prob at hand, please keep your opinion to yourself. The point of these forums is to ask questions and provide help when possible. If you wish to voice you're opinion, I suggest you start your own thread.
My why
jaseman said:
I can't help myself, I have to speak up..
nothing against the OP BUT this is exactly why I DO NOT try to do this stuff. There's really no benefit that the stock ROM on this phone cannot do...and more...and I read so many reports of people turning their beautifully working phones into little black plastic paper weights. Simply not worth the trouble, time, and possible money :silly: to get a little more screen space, or a smaller NAV bar, or whatever.
And then so many people want KIT-KAT...WHY? Will it REALLY be that much better than what this thing can do now? Or will it just introduce BUGS like every other update always does to an android device? If, and when this phone gets an update to KIT-KAT or whatever version they decide upon, and it actually works without new bugs, then I will be pleasantly surprised. Here we have what just might be the best android phone to land on earth so far, and people want to "improve" it??? My $0.02
Click to expand...
Click to collapse
I can't speak to everyone else's why but I do it because I'm an engineer and here is what i mean by that. Ever since I was a little kid I would mess around with stuff even though I had no clue what i was doing. I remember the first time I took apart a stereo was because our living stereo broke (the CD player wouldn't play anymore and that's what it was used for mostly). I told my mom not to throw it away so I could see if I could fix it. I was maybe 10 at the time so of course she knew i couldn't possibly fix but she let me. In the end I couldn't fix it (hell i had screws left over) but it was just fun looking around and exploring. As I grew I still kept doing the same thing, taking things apart and explore. Sometimes I can improve the thing I took apart other times I completely break it but most of the time I can just put it back the way it was originally. That's my why.
elseif said:
I can't speak to everyone else's why but I do it because I'm an engineer and here is what i mean by that. Ever since I was a little kid I would mess around with stuff even though I had no clue what i was doing. I remember the first time I took apart a stereo was because our living stereo broke (the CD player wouldn't play anymore and that's what it was used for mostly). I told my mom not to throw it away so I could see if I could fix it. I was maybe 10 at the time so of course she knew i couldn't possibly fix but she let me. In the end I couldn't fix it (hell i had screws left over) but it was just fun looking around and exploring. As I grew I still kept doing the same thing, taking things apart and explore. Sometimes I can improve the thing I took apart other times I completely break it but most of the time I can just put it back the way it was originally. That's my why.
Click to expand...
Click to collapse
Sounds like my childhood and I'm an engineer aswell.
Software to me is pure magic, but I'm very happy there's people that can code Roms.
Good luck mate.
Once you fix your phone and it's back to stock it will feel better than sex.
Keep stock for a couple of days and that itching feeling of "i need to do something with this" is gonna come creeping back
elseif said:
I can't speak to everyone else's why but I do it because I'm an engineer and here is what i mean by that. Ever since I was a little kid I would mess around with stuff even though I had no clue what i was doing. I remember the first time I took apart a stereo was because our living stereo broke (the CD player wouldn't play anymore and that's what it was used for mostly). I told my mom not to throw it away so I could see if I could fix it. I was maybe 10 at the time so of course she knew i couldn't possibly fix but she let me. In the end I couldn't fix it (hell i had screws left over) but it was just fun looking around and exploring. As I grew I still kept doing the same thing, taking things apart and explore. Sometimes I can improve the thing I took apart other times I completely break it but most of the time I can just put it back the way it was originally. That's my why.
Click to expand...
Click to collapse
I feel you pal. But i also got the point of the other guy. But is in OUR vines to mess things around and turn in back. lol. Bout your concern, i think there is a thread here that got it working. Just try searching in Q & A thread. Maybe search "brick"? Read everything you can read. I'll help and comeback when i see it.
Try here http://forum.xda-developers.com/showthread.php?t=2534511&highlight=brick
Same issue. Fastboot mode.
Also here its a guide
http://forum.xda-developers.com/showthread.php?t=2471370&page=2
jaseman said:
I can't help myself, I have to speak up..
nothing against the OP BUT this is exactly why I DO NOT try to do this stuff. There's really no benefit that the stock ROM on this phone cannot do...and more...and I read so many reports of people turning their beautifully working phones into little black plastic paper weights. Simply not worth the trouble, time, and possible money :silly: to get a little more screen space, or a smaller NAV bar, or whatever.
And then so many people want KIT-KAT...WHY? Will it REALLY be that much better than what this thing can do now? Or will it just introduce BUGS like every other update always does to an android device? If, and when this phone gets an update to KIT-KAT or whatever version they decide upon, and it actually works without new bugs, then I will be pleasantly surprised. Here we have what just might be the best android phone to land on earth so far, and people want to "improve" it??? My $0.02
Click to expand...
Click to collapse
I am horribly confused as to why you are an XDA member. :-/
Support your Devs......
I'm having the same problem and haven't been able to get it to work. As soon as I flash the stock d802 (my phone is really d803 but I had a d802 custom rom on it before) the touch screen goes all weird and my phone keeps restarting.
Hey folks! I have an Acer A500 that I have been working on "with" dibb_nz over the past week. I have no idea what was on it originally, it came to me nearly dead. After a TON of attempts and hard work from dibb, I now have Skrilax's bootloader and recovery installed. I flashed CM10-10 Flex_V6 ROM from Civato onto the device successfully. Here is the problem: no matter how I boot up, it either goes directly into "Power off - Shutting down" then vibrates and blanks out or, after a fresh install, it will say "Android is upgrading", "Optimizing apps", "Starting Apps", then on to the Power Off-shutting down thing.
Does anyone have any clue what may be going on here? I have tried earlier ROMS, all from Civato, but with the same Power OFF result.
Any help would be MUCH appreciated!
Thanks in advance,
Sharkguy
hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile
dibb_nz said:
hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile
Click to expand...
Click to collapse
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.
Well, that sounds complicated. I should have the new battery by the weekend so let me at least try that before anyone gets all technical. Unfortunately I dont know anyone with another a500 to test batteries...
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Moscow Desire said:
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.
Click to expand...
Click to collapse
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna
Yeah Dib, the eec thing. Just couldn't remember. Usually we just removed that command from the install script as usually once it was flashed at the factory, rarely did you ever have to flash it again. I will have to look and see in the next couple of days. Worth a shot though. Might be able to put it in a CWM install.
Oh, forgot to add @sharkguy
As with a damaged partition, if the memory got hosed in that particular partition, whichever, there's not a whole lot that can be done. Could try running babsector, but not sure if it would fix it or not. There's been success running it before, but only about 30% as I can tell. Devblks can get physically damaged. Usually the partitions are large enough to mark the bad spots as bad, and still be able to install things. That's what babsector did I think as near as I can tell.
A faulty chip "could" cause a shutdown, especially if it couldn't create the dalvak which is kind of the next step when "starting applications" If I guess right, although I would think it would bootloop rather than shut down. As you say, I've never heard of a power off before, unless the eec was bad and it thinks the battery is dead.
I'm just curious if the OP has done a full format on internal memory via CWM? Before installing. Not the usual wipes, but going into advanced, and triggering the full format. I used it after running that CM stuff awhile back, as it messed up everything (lots of testing). Needed a clean sweep of the internal memory.
As you see, I am still around Just with being a senior mod, not a lot of time for messing with things.
I'm still leaning towards eec pwr. (I'm using beer logic at this point)
Bear with me on this. Let's say the eec got hosed somehow. It happens on occasion. And you install several custom roms, which of course don't have eec pwr in the install script as we removed it. Here's what I know.
1) Battery won't charge and is always going to shut down
2) No response on the touch screen if indeed the OS starts.
3. Tab shuts down after OS start.
So you see why I am leaning towards this.
MD
EDIT: The reason why we removed eec from the custom roms to begin with, primarily as it really wasn't needed, but it "could" cause an issue if the flash went bad. But considering the OP has UID and NVFlash, that isn't an issue now.
dibb_nz said:
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna
Click to expand...
Click to collapse
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Always works in recovery, as it is independent of the OS...
Righto. I figured it didnt matter in this case. But yes, the rest of the facts are as you understand them.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
The FULL wipes as stated in the guide m8 or via fastboot erase.
@Moscow Desire _bab sector was run and successfully, boot loader and recovery installed with no errors.
As far as the eec thing I do have a copy of that in my stash if that's any help, but no idea how to apply it????
Sent from my HTC_PN071 using Tapatalk
Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app
sharkguy said:
Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
Well m8 I dunno if u made the right choice there, I guess only time will tell...there is this thread http://forum.xda-developers.com/showthread.php?t=2617196. I cannot recommend it but then my tab has never been in that state...and I'm not sure I could bring myself to put it in the oven lol...u nut wanna take a look at it any way
Sent from my HTC_PN071 using Tapatalk
Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Well, you'll be in your element then,lol...Yeh, your issue is rather unique...with babsector not returning any error its out of my area of expertise!!! But I do know that Acers build quality isn't the best....from power buttons falling out to the memory chip failure and their dodgy soldering techniques, i'm leaning towards a hardware fault 'somewhere'....
But then, it does seem strange the tab powers off during "updating apps" that points to software doesn't it???? Have look in the guide for fastboot commands (if you still have the unlocked bootloader on there) I'd erase all partitions, /system, /data, /cache etc....then run babsectot again to repartition -flash a rom and see what happens...or use tdv4 to do the same, but no rom flash needed for that as it comes with HC 3.2.1 rooted and cwm.
Anyways m8 keep us updated - and fingers crossed you end up with a positive resolution
rgds Donna
One of the last things I think I did was tdv4 without a rom flash. It still came up with the same issue. I did notice that when I took the battery out to charge on the equipment at work (closely monitored of course) to see if there was an issue with the charging circuit, that I could still do all of the same things as before with just the AC plugged in. No battery. This is why I bought a battery to try that out. The Galaxy 3 guy realized what a steal he was offering me and bumped up his price so it looks like I'm stuck woth the A500.
Thanks for the crossed fingers!!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
sharkguy said:
Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Soz m8 been full on at work to even check emails let alone reply...phew!!!!
As MD pointed out above, the EEC file thing, devs have dealt with that particular issue, but b/c yours is a relatively unique issue I guess it can't be ruled out...
Have you managed to take a look at fastboot and using the erase command to delete EVERYTHING - at least u can be sure its as clean as can be, then using babsector with an appropriate rom and see what happens there.
In that "tab flu" thread there are links to another thread (somewhere) re: eec thing - If you find it can link it here in this thread and I'll track down the file -
Oh, just to be clear - when it boots into to the OS and powers off - is it completely shutting down i.e. power led is off or is it actually booting to apx mode, black screen power lite on...whats the chances of a vid so we can see exactly what it does???
rgds dibb
Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Ok, so new development, so to speak. As you can see from the crappy video I shot just now, I can boot the tablet into the start of the OS, but it hangs at Powering Down. The new part is that I had to manually shut it off, it did not do that itself this time. I showed you the power light (orange) and when I press it again, it does power on, but is still hung up on the same screen. I don't know if that helps any, but now you can see it. By the way, sorry it is upside down, it was the only way to show you the power button after it booted.
http://youtu.be/pG_efbq6DZg