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.
Related
Well i want to put a HTC Hero rom on my T-mobile MT3G 32b device. I came across http://theunlockr.com/. I watched the rooting video here and the rom installation here.
Well i know that my device is the exact same as in the video so i pretty much can't mess up the procedure unless i am completely useless as a human being.
Well i just want to know even if i do the procedure correctly if i can brick my phone? My GF was kind enough to buy me the phone for our anniversary about a week or 2 ago and yeah i love it but would like a hero rom. I just don't want to make my gift into a paper weight and get the misses angry at me for ruining a 250 dollar phone that lasted about 3 weeks.
Thank you for your time it is much appreciated.
its well worth it to go ahead and do it i actually hated the phone in stock form and wanted to get rid of it but after i installed the HERO Rom i actually love the phone, FYI i traded a iphone 3g for this phone and hated it with the original t-mobile software and wanted my iphone back but after the HERO rom upgrade i love it.
there are only two steps in the rooting process that can brick your phone that i know of.
the first one is while updating the SPL and the second one is while updating the RADIO.
once you get those two things to the right versions then you cannot brick your phone. you can install/uninstall as many roms as you want as long as you don't mess with the SPL or RADIO.
also, if your doing the one-touch root just make sure your phone doesn't turn off or the battery die while its working, then you could brick your phone.
and its definitely worth rooting to put the hero rom on there.
alright thanks for your replies they are much appreciated yeah i think i will go ahead and do this then and will make sure my battery is fully charged =D.
One More question how often do you have to update the spl and radio. or are they one time only things? I am new to this so just wanna make sure i don't mess anything up.
Warsyndicate said:
alright thanks for your replies they are much appreciated yeah i think i will go ahead and do this then and will make sure my battery is fully charged =D.
One More question how often do you have to update the spl and radio. or are they one time only things? I am new to this so just wanna make sure i don't mess anything up.
Click to expand...
Click to collapse
Since you are on the MT3G you do not have to worry about changing the SPL or radio. Just perform the one-click and then load the rom of your choice.
If you plan to run Hero then be sure to get a class 6 microsd and use the rav recovery image (part of the rooting process) to format it with 3 partitions. It will be an option when you go to recovery mode. I actually recommend a 128mb linux swap but that requires some manual partitioning and I'm not sure if you are prepared for something like that.
I have loaded just about all the roms and I still have the original spl and radio.
Oh alright ill be sure to look into that. Thanks again for all your help.
I've had it rooted, and flashed many roms to it.. then tonight it all went to sh!t.
I was trying to put a froyo rom onto it(i think it was called extreme froyo), and i got the boot loops, and on the download page it said i needed the newest radio/spl if that happened...
So i ended up flashing some sapphire SPL, and it got stuck on the "HTC MAGIC" bootscreen.... then I tried flashing this:
http://code.google.com/p/android-roms/downloads/detail?name=splhard1_update_signed.zip&can=2&q=
and now it wont even power....
Is it done for?
Yeah u need to be careful, flashing new radios and spls are very dangerous and best flashed from fast boot. Sorry but you sir are ****ed
Sent from my HTC Magic using XDA App
****in ****.. thats lame, and Tmobile is saying they won't warranty it.. ridiculous.
Ridiculous they won't warranty a phone you bricked? Sounds just fine to me...all the rooting stuff does say it voids the warranty...
Yea, but if you cant tell, then whats the big deal. it just doesn't turn on.
th1rt3en said:
Yea, but if you cant tell, then whats the big deal. it just doesn't turn on.
Click to expand...
Click to collapse
tell them u reccieved an ota update and when it finished it wouldnt work
That's what you get for not reading up about something which could harm your phone. I don't mean to add insult to ingury, but chances are you didn't even need HardSPL.
It if you can't get into Fastboot or anything, you're screwed. But you shouldn't be flashing new radios or SPLs if you don't know if they are compatible with your phone.
There has been no OTA updates for the fender/mytouch 1.2. They won't believe that line...
NetrixTardis said:
There has been no OTA updates for the fender/mytouch 1.2. They won't believe that line...
Click to expand...
Click to collapse
First you go about it very dumb like..... and then you start by saying that you was out and phone was all most dead. by the time you got home it was turned [email protected]@h...........new phone. But by no-means do i support this action nore do I believe in any act of theft by deception!!! This can get you in trouble big time.
First of all, if you're going to flash a rom that clearly states that you need the newest radio and SPL, you want to update those BEFORE you flash the rom. More than likely, that's what caused your boot loop. Second, do a little research before you start flashing things, if you had, you would know that you always update your radio before your SPL. That's where you went wrong, and that's what bricked your phone. Of course T-mobile isn't going to replace a phone that you bricked. Rooting your phone voids the warranty and a bricked device is definitely no exception.
Do you have insurance on your phone? You're better off taking it outside, running it over with you car and making an insurance claim. Problem solved.
this thread was for help.. not for everyone to chime in about whether its ethically right for me to try and warranty.
If its helpful to me trying to get this thing going again, post, if not, just go to the next thread.
Ethically speaking, I personally could care less if you CAN actually get your phone replaced under warranty. If you can, do it! As far as getting your bricked phone up and running again, its not going to happen. Like I said, you obviously flashed the SPL before updating the radio which bricked your phone, there's no turning back. So basically, you have three options.
1. Don't replace your phone and use it as a nice paper weight.
2. Lie your ass off to T-Mobile and get your phone replaced under warranty and cross your fingers they don't find out and tack additional charges to your account for voiding your warranty. Who cares about ethics or what anyone else says, its your call. Honestly, as long as your hardware is ok, they can reflash your device and will end up reselling your phone to someone else, so who cares.
3. If you have insurance, smash you phone, drop it in the toilet, throw it at the wall, anything. That's what insurance is for, of course then you're still stuck with pay some cash.
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.
I want to demonstrate to someone how the phone can get stuck on something like bootloader or failed rom installations.
I currently have a nexus one with the bootloader still locked (but rooted). I dont want to try anything and render the phone dead. So I want to know if there is a for sure way t put the phone in a mode where it looks as if it doesn't work, yet be able to recover from it easily. Asking for opinions first.
I still want to have my phone maintained such that the bootloader stays locked.
Thanks
C
Turning the phone off makes it look likes it doesn't work.
P.S why are you doing this though? Really? Is it to make someone think their phone is broken so you can buy it cheap then fix it and keep it?
cymru said:
Turning the phone off makes it look likes it doesn't work.
P.S why are you doing this though? Really? Is it to make someone think their phone is broken so you can buy it cheap then fix it and keep it?
Click to expand...
Click to collapse
Didn't think of that. Maybe i should.
No, to make someone understand the process that I go through in updating the phone so that they can stop bothering me while Im doing it.
Edit:
I just realized that your post was so condescending. I asked a question and phrased it accordingly, to "demonstrate."
Don't you just love it when people express their opinion not knowing the entire story.
Try opinionating for the better, the next time.
And yeah, don't forget to help out people every now and then.
Thanks for your HELP!
C
haha no worries
If i understand what you are asking, try backing up your rom, then flash completely different rom without wiping. That should by all accounts give you a bootloop.
Might be easier to have them watch some youtube vid's of flashing, rooting, unlocking, etc. They then should get the idea...
I would just nandroid and wipe my phone (I dunno how well that'd go I've never tried it but I don't see how it could totally brick your phone, who knows!)
I don't know if you've got anything flashed on your phone, but if not flash a recovery then yeah, flash any different rom without wiping and you should get boot loops.
Format /system
That should do it... xD
liam.lah said:
If i understand what you are asking, try backing up your rom, then flash completely different rom without wiping. That should by all accounts give you a bootloop.
Click to expand...
Click to collapse
I think this is what I will do... thx again.
galaxys said:
Might be easier to have them watch some youtube vid's of flashing, rooting, unlocking, etc. They then should get the idea...
Click to expand...
Click to collapse
yeah but I need them to see me cuz they ultimately have to stop bothering me... lol
KAwAtA said:
I would just nandroid and wipe my phone (I dunno how well that'd go I've never tried it but I don't see how it could totally brick your phone, who knows!)
Click to expand...
Click to collapse
not sure i get what you mean, "wipe" is a loose term here, wipe is generally associated with "data" wipe so it wont matter, it would just reset my phone to factory settings
ThudButt said:
I don't know if you've got anything flashed on your phone, but if not flash a recovery then yeah, flash any different rom without wiping and you should get boot loops.
Click to expand...
Click to collapse
yeah i have blandroid at the moment, will try flashing some cm7 without wiping
danger-rat said:
Format /system
That should do it... xD
Click to expand...
Click to collapse
how?
It's an option in Clockwork recovery
Rusty! said:
It's an option in Clockwork recovery
Click to expand...
Click to collapse
Cool, i should pay more attention to the CWM recovery options thx
Telling people to not bother you isn't enough?
cymru said:
Turning the phone off makes it look likes it doesn't work.
P.S why are you doing this though? Really? Is it to make someone think their phone is broken so you can buy it cheap then fix it and keep it?
Click to expand...
Click to collapse
For the record, I think this is a fair question, and not particularly condescending.
OP: You are asking a legit question, but you have to admit it's a bit of a strange request. You can't blame people for wondering what you're up to, I thought the same thing. Not that you were scamming someone, but couldn't understand why you'd want to do this (I get it now... sort of). It's an impersonal forum, so there shouldn't be any hard feelings.
One thing that constantly caused bootloops in the CyanogenMod forum was to flash the Froyo gapps with a Gingerbread install. Bootloop every time.
You could probably flash a theme that wasn't designed for Gingerbread. I'd bet that would give you a bootloop (especially the further you go back... flash a cupcake theme for a G1 onto an N1 )
Maybe I'm just being cynical but it seems to me that the OP is doing something shady here. He wants to do something that makes no sense and then immediately jumps down the throat of someone who basically calls him for it. His reasoning for why he wants to do this nonsensical thing is also pretty nonsensical. I'd guess he's trying to scam something from someone.
Wylker said:
Maybe I'm just being cynical but it seems to me that the OP is doing something shady here. He wants to do something that makes no sense and then immediately jumps down the throat of someone who basically calls him for it. His reasoning for why he wants to do this nonsensical thing is also pretty nonsensical. I'd guess he's trying to scam something from someone.
Click to expand...
Click to collapse
Yes, I completely agree with your first statement. YOU ARE BEING CYNICAL!!!
Ok as an avid lover of my phone (nexus one), I have the right to ask the means of breaking this phone if i'm going to root it and install a ROM which is only supported by the community that helps develop it (that includes primarily folks over at XDA). If you think I'm upto no good, too bad. Assume the worst, do whatever the F*** you want. All I'm trying to do is show my cousin what a bootlooped phone looks like. And apparently each time I am in the process of doing it, he wants to use the pc. He likes killing all the running apps when he's on the PC, and i need to stop him from screwing up something that can potentially f*** up my phone. I often switch from Stock N1 to CM7 to blandroid, and thankfully i follow directions which is why my phone hasn't boot looped til date.
Yes I jumped throat on the 1st person who responded, but look at my response before jumping throat. I didn't really think of the response as condescending, until had posted my answer, hence the edit.
Don't bother posting such crappy posts unless you want to feel like you're getting scolded by the DA's office for wrongful accusation.
C
Well you cannot blame people for coming up with these various speculations. My 2 cents, but you just redirect your energy towards your cousin more rather then get angry over forum post.
The way I see your situation is this. The PC used to flash your phone, who is the owner? If you own it, tell him to wait like a good little boy or he can GTFO of your computer, ban him. Or if the PC belongs to him, maybe it's time you suck it up and respect when and how he wants to use his PC, and flash your phone using another instead. Or maybe get a job and buy your own?
Time to man up. Either you tell him to GTFO of your PC, or you GTFO of his. Simple solution to what I see to a simple matter. No need to complicate things by semi-bricking your phone.
Sent from my Nexus One using XDA App
Either show him http://www.youtube.com/watch?v=3I5XaDAuiEs
OR
Stop trying to make your cousin think he's broken you phone in order to ..
a) get him to pay for a replacement and/or
b) scare the crap out of him
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.