Related
Ok so I bricked my Evo yesterday. The goal of this thread is to find out possible reasons why it bricked so I can avoid any future incidents. What I was doing was simply flashing a new rom. I had reflashed my clockwork from version 3.0 to version 2.5 which worked fine. I was able to flash between a couple of roms using it. I did this because of the issue with not being able to flash certain zip files with the new recovery. So I downloaded Warm Z RLS 1; the 2-23-11 version. So I flashed the zip the process went as normal. The installation completed normally. Then, I flashed the radio file. That also installed successfully as expected. Then, I backed out and went to "reboot system now." When I clicked that It went to a black screen showing a picture of an open box with an arrow coming out of it pointing to the little android guy outside the box. So, after trying to hit the power button to turn it off and return to the bootloader, it remained at that screen. Next, I removed the battery to restart it that way. Where it finally rested in peace. The phone would not even attempt to boot up nor attempt to enter the bootloader. The charger light wouldn't even turn on when plugged in. It was as bricked as can be.
Now here is my question. Does anybody have any theories as to why this happened? I want to remain a "rooter" when I get my next Evo. I want to know what went wrong so I can avoid bricking another phone.
Thank you in advance to those who can offer any advice or help. Also, sorry in advance if I'm posting a repetitive topic.
P.S. Sprint is replacing my phone for FREE. I didn't mention anything about rooting. Without asking questions, the sprint rep simply said that they would order a replacement, which will arrive in a couple of days.
errie806 said:
Ok so I bricked my Evo yesterday. The goal of this thread is to find out possible reasons why it bricked so I can avoid any future incidents. What I was doing was simply flashing a new rom. I had reflashed my clockwork from version 3.0 to version 2.5 which worked fine. I was able to flash between a couple of roms using it. I did this because of the issue with not being able to flash certain zip files with the new recovery. So I downloaded Warm Z RLS 1; the 2-23-11 version. So I flashed the zip the process went as normal. The installation completed normally. Then, I flashed the radio file. That also installed successfully as expected. Then, I backed out and went to "reboot system now." When I clicked that It went to a black screen showing a picture of an open box with an arrow coming out of it pointing to the little android guy outside the box. So, after trying to hit the power button to turn it off and return to the bootloader, it remained at that screen. Next, I removed the battery to restart it that way. Where it finally rested in peace. The phone would not even attempt to boot up nor attempt to enter the bootloader. The charger light wouldn't even turn on when plugged in. It was as bricked as can be.
Now here is my question. Does anybody have any theories as to why this happened? I want to remain a "rooter" when I get my next Evo. I want to know what went wrong so I can avoid bricking another phone.
Thank you in advance to those who can offer any advice or help. Also, sorry in advance if I'm posting a repetitive topic.
P.S. Sprint is replacing my phone for FREE. I didn't mention anything about rooting. Without asking questions, the sprint rep simply said that they would order a replacement, which will arrive in a couple of days.
Click to expand...
Click to collapse
Yes, I can tell you why that happened. It's because you pulled the battery during the Radio Flash!!! (almost a guaranteed brick by doing that...) After you flash the radio update in recovery, it brings you back to the recovery screen, and you have to hit reboot. Upon rebooting, the radio flash completes (that is the black screen with the box and the arrow....) That part can take from 20 seconds to 10 minutes, and you have to be patient. If you disturb the phone (battery pull) during that process, you'll brick it. That is one of the only ways to surefire brick an Evo. So, to prevent it from happening again, all you need to do is be sure that if/when you ever flash a radio update, that you follow all of the instructions, and never, ever pull the battery during a radio flash. You need to remember that when you flash a different radio, it reboots and then does the important stuff, while showing you that screen with an arrow and a box, or an arrow and a phone. Once that part completes, it takes you back to the recovery screen, and then at that point you select reboot, and it'll boot normally into the OS.
Oh, I see. Thanks a lot. I had never seen that screen before. I had flashed radio update before but I didn't see that screen. I thought it froze. I feel like an idiot. But, I learned a lesson. Thanks again! Can't wait to get my replacement evo to start rooting/flashing again.
errie806 said:
Oh, I see. Thanks a lot. I had never seen that screen before. I had flashed radio update before but I didn't see that screen. I thought it froze. I feel like an idiot. But, I learned a lesson. Thanks again! Can't wait to get my replacement evo to start rooting/flashing again.
Click to expand...
Click to collapse
Yea, we all make mistakes. That is definitely one that you'll learn from though! And sometime's that screen, when the radio is flashing, varies a bit. I know when I flash a radio, it's a screen with a picture of an Evo that has a circle around it with an arrow facing down. I believe it is the hboot version or the recovery (amon ra or clockwork) that determines what that screen will be. Either way, that is what to expect during a radio flash. It has happened to many people, where they flash a radio, and get to that screen that they've never seen before, and then think that something's wrong so pull the battery. You're not the first, for sure. Anyways, good luck on getting your new Evo. Take it easy.
Patience is the key with all things root. Not every dev reminds you that you have to wait a while for things so it's easy to forget it. On the Samsung Fascinate, development can be a fragmented mess so most devs explain everything l.e.t.t.e.r.b.y.l.e.t.t.e.r. I rooted my girlfriend's phone and they always remind you that reboot/reflashes can take up to 20 minutes so when my Evo did that on a recent flash I knew I just had to leave it alone.
Great to know info. Thanks for bringing this out for us newbs to know.
Yeah as said above those radio flashes can be a learning process. Seemed like a few people did exactly as you when flashing radio's on Myn's RLS 5. Even after people were warned in the thread it still happened. I put my phone down and sat on the throne a while. Felt better to drop bricks, than turn my phone into one. patience is a virtue.
Yep, whenever I do any flashing I just set it down next to me and try to keep myself busy with other stuff so I don't get impatient.
BTW, what did you tell then Sprint store had happened to your phone, just that it wouldn't turn on?
Hey all,
This is my official "first" post. I rooted the A100 while it was on Honeycomb. Everything was fine. I got an ota update and updated to 3.2.1. Rooted it again and everything SEEMED fine. I got the ota ICS update and the tab would hang at the green android and give me a "!" after about 5 seconds. I fiddled with the update for a while and took it to a friend that knows more about this than I. He proceded to try and unlock the bootloader with the ICS unlock, while it was on Honeycomb. Now my tab is bricked with the green Acer logo, it will not boot. I have no access to recovery, fastboot, adb, bootloader. I can get it to APX mode. I tried to NVflash it, but when I use any NVflash commands, device manager just kicks my device off and the command doesnt execute. I cant use the EUU, because it keeps telling me my CPU ID is wrong, even though I KNOW its correct. I have searched the forums and sent PM's to everyone that has experienced this and fixed it, but no one has answered. Could SOMEONE, ANYONE, PLEASE help!!!!!!
Thank you in advance!!!!!
Cory
Really
No one out there has any insight into this? Ive seen that there are a couple people in the forums that have fixed this issue, but in their posts it doesn't really describe how because they were being PM'd. PLEASE, any info would be GREATLY appreciated!!!!
cooki3monst3r77 said:
No one out there has any insight into this? Ive seen that there are a couple people in the forums that have fixed this issue, but in their posts it doesn't really describe how because they were being PM'd. PLEASE, any info would be GREATLY appreciated!!!!
Click to expand...
Click to collapse
Try using the search on the forums, it's been discussed several times and the only way to fix it currently is to send it in to acer for repair and hope they replace it with a different board that the euu works with. Please stop posting this same question when its been asked repediatly already there are 4 separate posts with this same question being asked by 3 different people
Sent from my MB860 using XDA
OK
I have searched the forums for the past I cant tell you, how many hours. I have looked and looked and in one forum, it looks as though someone fixed this issue because they were able to somehow get to fastboot. I would not just post this on here without my resources having been exhausted. The problem is, in EVERY FORUM I CHECK, the answers and such are PM'd to each other! I have even PM'd the people that seemed to get something working.......to which I have received no reply. Ive seen the posts on this, Ive tried NVflash, I tried to boot holding EVERY combination of buttons, EUU doesnt work, because of the CPUID being "wrong". I have done my research, sir. Please PM me if you think I have wronged you in some way by posting something in a forum meant for helping others, instead of putting me on blast because you think Ive been lazy and not searched the forums.
cooki3monst3r77 said:
No one out there has any insight into this? Ive seen that there are a couple people in the forums that have fixed this issue, but in their posts it doesn't really describe how because they were being PM'd. PLEASE, any info would be GREATLY appreciated!!!!
Click to expand...
Click to collapse
can you boot into fastboot mode?
dunno
Im not sure if I can get to fastboot. There are a couple of people that, it seems, could get to fastboot and APX. Could you direct me on the ways of getting to fastboot? Adb doesn't work for me. Only APX mode. It boots to the green Acer logo. When I try to get to recovery (VOL+PWR), it hangs and will not go to recovery.
Sorry for being short earlier, Im just so frustrated with this. Ive been researching this issue for DAYS. (NVflash, APX, bootloaders, adb, etc....) No progress on it. I even have a DEV friend who may try to decompile the EUU and see if he can force push it to the tab....he just has to find the time. lol
done
At this point Im willing to use the tablet for target practice. If anyone wants it, to mess around with or whatever, you can pay for shipping and keep it.
cooki3monst3r77 said:
At this point Im willing to use the tablet for target practice. If anyone wants it, to mess around with or whatever, you can pay for shipping and keep it.
Click to expand...
Click to collapse
Well that is a hard offer to pass up...
Sent from my LG-P999 using Tapatalk 2
If you and orient fastboot and has the bootloader on the A200 prepare to unlock and install cwm recovery and is saved
hard-resset first try with the buttons
1 tablet off completely its
2 lock button on the screen is right
3 hold down power and volume - that is left
4 when the tablet vibrate release the power button and quickly move the screen lock button to the right and left without releasing the volume -
5 your tablet should start
but it works I say and try fastboot
I dont know if the boot loader is locked or not. I cant flash cwm because I cant get to recovery/adb/fastboot/etc. I tried the hard reset and the tablet hangs on the green Acer screen after reboot. NVflash doesnt work because ???, device manager just drops it when I try to send commands and nvflash says something about not being able to write to usb. And yes, I have the Nvidia apx drivers installed.
peporras said:
1 tablet off completely its ( holding it in landscape)
2 lock button on the screen is right
3 hold down power and volume - that is left
4 when the tablet vibrate release the power button and quickly move the screen lock button to the right and left without releasing the volume -
5 your tablet should start in fastboot mode
are you able to get fastboot going?
if so try to flashing a custom recovery from thor 17 ( google it)
i had a problem like this and was able to fix it by flashing the leak isc rom through this recovery. it might be worth a try.
Click to expand...
Click to collapse
just bought it for $30. it worked great. so i download rom manager and flash the clockwork recovery because i am really dumb.
i think it still gets into software update or emergency mode, the screen is blank but the buttons light up and in KD500 i CAN flash a bin file to 95% but then it cuts out saying phone disconnected, as the phone reboots it just hangs on LG logo.
ive tried lgpnst but it claims at 0% MASTERBIN DOWNLOAD "NUMBER OF BAD BLOCKS EXCEED LIMIT. PLEASE REPLACE FLASH"
i have spent 16 hours now trying to fix a $30 phone. please stop me guys. either give me a solution or tell me to shove this up my... ahem nevermind
It sounds like there's something wrong with the flash memory in the phone. If that's the case then it's not really your fault, it would've gone anyway. Have you tried booting into recovery and flashing something?
By the way, you posted in the wrong forum, this belongs in Q&A
bluespoon4 said:
It sounds like there's something wrong with the flash memory in the phone. If that's the case then it's not really your fault, it would've gone anyway. Have you tried booting into recovery and flashing something?
Click to expand...
Click to collapse
it wont go into recovery, it just pops up the LG logo and sits there
at first, right after i flashed the bad recovery, i could do the emergency boot sequence (hold backspace and vol down, insert usb). up would pop the SW update mode.
so i did that, and tried the stock LG updater, but it wouldnt keep talking. so i tried the KD500 method, and it appreared to work but thats where im at now. even if i boot into SW update mode, its just a blank screen now, but it will still connect to KD500 and seemingly flash a bin just fine. however when the phone reboots at the end it just lights up the dumb lg logo and sits there.
its just frustrating. i know its not the end of the world, just man. ugh maybe its the wrong cabs? ive tried LS670ZVC_11.SC_11.P60674.cab and such... 75, 70...they all do the same thing
I'm not sure about the KD500, so you may have already done this, but have you tried what is says here? http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=30798348
bluespoon4 said:
I'm not sure about the KD500, so you may have already done this, but have you tried what is says here? http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=30798348
Click to expand...
Click to collapse
thats a wrong link. it just links to a reply for this thread
oh, sorry, I have no idea how that happened, I meant this one. http://forum.xda-developers.com/showthread.php?t=883314
yeah, and it seems i can get that mode to work, however i do not believe i have the right kdz.
thing is, when i try to follow the links to download the original firmware from lg, i cant get anywhere....
ill keep trying. i really think if i just had the right kdz it will work
AAAAAAAAAnnnnnnnnnnnd thats a wrap.
i finally found the right cab i think. i used an LG firmware update app found here on xda.
but i guess the firmware gods did not want this phone alive. during the update, i left for the store. came back, and my laptop wasnt charging, sending it to sleep during the update.
total brick now. no emergency mode. no lg logo. just buttons light up thats it. no communication with the pc at all.
its dead. rip little optimus.
**Update. Just bought a Sanyo Zio for $19.98 shipped off the bay. lets see how fast i can screw this one up!
ha! trying to get my droid x off ics this morning.
BRICKED as well
at least i still got the bootloader!
i forgot then when you do the ota .621 update you NEVER go back. no matter what you flash, youll always be a .621 phone. SO USE .621 CUSTOM ROMS YOU IDIOT
and youre lucky you didnt fry this droid by trying to program it with a dead battery!
sheesh! idiots! (me!) :cyclops:
OK. one last thing.
i had another droid X that has been sitting around for months. i couldnt get it out of bootloader. everything i tried made it worse. it wouldnt even take the linux sbf .621 flash that worked on my other dx's. i really thought it was toast.
but today, i ran across the signed and verified moto stock rom for .621 while i was trying to fix my everyday DX. so i said, "WTF". i flashed the old dx in windows rsd because thats supposedly supposed to flash the radio too.
well, whatever it did, IT WORKED. i am almost in tears right now. this phone is MINT. like brand new, bought it for $40 because the last guy couldnt get it to flash either.
the whole time, it just wanted a verified moto rom!
one more sbf flash to a rooted .621 rom, and bingo. i have a like new fully rooted dx!!!!!!! I cant help but brag! i spent so many hours on this thing!
I could jump through the roof right now!:good::good::good: two droid x phones for less then $80 total! just hours and hours of pulling hair too hahaha
I should have seen this before.. I know a good place for optimus s.
Here
rr0yy said:
I should have seen this before.. I know a good place for optimus s.
Here
Click to expand...
Click to collapse
no i said STOP me!
guess what? i had the battery on an external charger the other day. one last time, i put it in the phone and hooked it up to my laptop. BUH BUM! it connected!
so i quick tried to flash the verified verizon rom. it seemed to take, but again it does not boot up.
HOWEVER, i do now have the S/W upgrade screen back! i dont think this phone is dead yet! its such a joke to keep trying for a $30 phone, but man it bugs me that a simple software problem is keeping this thing from being at least a good mp3 player!
edit- ive seen most of those links though. my problem is i dont have the stock recovery on this phone, and to flash that you need to adb into it... which i cant! I truly believe if i could find the right KDZ file for my phone it would work! all the links i find are for optimus V's! i have an optimus S, model US670 which is VERY hard to find roms for.
i used the LG update app found on xda here, and it downloads an SBF file. even if i change the extension to KDZ it doesnt work! file extract error every time. i need to find my KDZ for this phone and i just know it will work!
So I recently rooted my phone with this tutorial:
http://www.youtube.com/watch?v=nkkcCCjeUpI
Everything went great and I was rooted. So next I decided I wanted to flash a rom. So I decided this one:
http://forum.xda-developers.com/showthread.php?t=1817345
I looked over it and followed its instructions. So I flashed it. I also flashed the google apps.
This is where the problems started. I rebooted my phone, and It never would show the boot logo. I kept pulling the battery and it would not start. I thought the battery might be dead so I charged it, and still nothing. I noticed when I plug it into my computer and it makes the little connection noise. (Like my computer is reconising the device) But still nothing on the screen. I tried to connect it to odin and it does not show the device.
So I have looked all over the internet (including these forums) and have found no help. Sounds like I might have bricked my device.
So my last question, If I did indeed brick my device will this fix it? (I mean will it atleast get it into download mode?)
http://www.ebay.com/itm/NEW-Samsung...369526?pt=PDA_Accessories&hash=item3a77c2f8b6
Please let me know if you have any ideas.
Thanks, Griffsbrown
Boot into recovery and restore the nandroid you made before you flashed.
Man sure sounds like most the people having problems are cause they are rooted/modded. Hope its a simple fix for you. GL.
You flashed a rom for a different phone, its dead pretty much. research jtag I read its about 60-100$ read more in the future.
Sent from my SGH-T999 using xda premium
You flashed a ROM for a different phone. That is why you can not boot. Are you able to get into download mode? from the power off state, press and hold the volume down and home bottons and the power button. This should bring you into download mode. IF you can get there then you should be able to recover.
always be careful when flashing roms if you can get into download mode like the above poster said then your lucky and can odin a root66 and you will be back to before you installed the wrong ROM.
If you cant ........... your bricked my friend time to learn a lot more about jtag (which is a lot more difficult than odin READ READ READ
The only thing is people have been installing ATT roms for some reason their phones are not bricking but unless the dev says it works i wont try it.
ONLY USE ROMS FOR YOUR PHONE im really new and one of the first things to know.
Bricked! Search for mobile tech videos jtag fix.
Sent from my SGH-T999 using xda app-developers app
Guys I'm desperate,
Helping my friend with his new GS3, I got root easy and downloaded JellyBAM 5.1 without realizing the bootloop issues over there. Anyway, I took the advice in that forum and did a full wipe to get past the bootloop... didn't work. Thought I'd just restore a nandroid and it was on that was in there previously from some unknown source (he's since confirmed that it was a ROM from his old VZW thunderbolt).
Suffice to say now I cannot get into recovery, I ONLY have access to the downloading screen (down + middle + power). My attempts with ODIN and whatever other suggestions in the forums have been unsuccessful. The Toolkit is the closest I've come but the issue with that its constantly waiting for USB debugging. Anyway, at this point the USB connection to the phone doesn't show any files on my PC. I can't figure out a way to connect to it and push an img or any kind of fix. I'm hoping the community can help me with this one, I promise I'll read better next time around. Any thoughts/advice?
Well, first off... Let's hear why your Odin attempts have been unsuccessful first so we have a better idea of what you have done exactly.
Sent from my SPH-L710 using Tapatalk 2
Try http://forum.xda-developers.com/showthread.php?t=2017470 while you are in download mode.