Related
I was attempting to flash 2.x using behnaam and lox's rom.
Rom: http://forum.xda-developers.com/showthread.php?t=592596
Here is the HBoot info previous to my tinkering:
HERC XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-1.04.01.09.21
SEP 1 2009,19:18:45
Phone is rooted using adb.
I used unlockr's guide to flash a custom recovery image onto my CDMA hero and that worked fine, here is the guide I followed:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I first moved the radio recommended for the rom by the dev to root on the sd and renamed it update.zip. After, I used the recovery image to wipe, then apply update.zip from sdcard. It seemed to flash fine, as it said please select reboot to complete, which I did, and it completed and rebooted the phone.
Once rebooted it gave me the android installing software image without anything else for a while, then turned off. I cannot seem to awaken my phone with any combo of keys or by plugging it into its use cable. The charging led doesn't even light up anymore.
Well I seem at the moment to be SOL, unless someone can come by and throw me a bone. I really am at a loss as to what I did wrong, as I have always read to do radio first. Not to mention as I watched it install radio it said it was installing radio.
Thanks for the help everyone.
You attempted to flash a GSM ROM to your CDMA phone, this is why your phone is bricked. I'm not sure if its possible to recover, people with more experience than I have can help you there. The problem was flashing a GSM ROM to CDMA. You are not the first to have done it, we all mess up from time to time.
Uuuh Umm...that software was for the GSM hero's NOT THE CDMA Hero.............bless your heart.
Ah **** I thought it was CDMA, guess it was a bad idea jumping into roms while still a noob.
Yea I only got the radio installed, not the rom, although that probably doesn't make a difference.
I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.
Hmm well if worst comes to worst I'm going with what I read on another thread and saying that I was installing the update that it found when I went to phone details and halfway through the update the phone just turned off and won't turn on anymore.
According to the other thread once it is bricked beyond belief and you play stupid they can't prove you wrong.
Best case scenario they replace it, and I won't feel bad seeing as it was a defective phone that is allowing dust to enter under the screen. But that who ordeal is an entirely different rant...lol
Sigh
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
Go......Now......Move with haste...
gu1dry said:
I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.
Click to expand...
Click to collapse
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.
flipzmode said:
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.
Click to expand...
Click to collapse
All is lost!!!!
Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.
unfortunately, flashing the GSM radio on pretty much destroys the phone.
i think its got something to do with the voltage and electricity used by the GSM radios. probably higher than what the CDMA radios use, so you didn't really brick your phone, you 'fried' it in a sense.
sorry bout that... but if you have the equipment protection plan you can probably get it replaced real easily, since the sprint people probably won't really understand what's wrong.
again I am reminded why I dont screw with radios
willowmp said:
Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.
Click to expand...
Click to collapse
Once you do get it replaced and you want to put a custom ROM on it, look at the first page of this forum and you'll find sticky threads regarding four different ROMs you can put on your phone (two production release and two experimental betas).
I would suggest either MoDaCo's rom or Fresh rom. I use Fresh in mine and had no problems (although I have used MoDaCo's before and also had no issues).
Also, if you want to root the phone, there are also sticky threads that will tell you how to root your phone from Windows, Mac and Ubuntu.
Good luck.
Yep thanks everyone.
Yea I figured once no buttons would do anything and the leds wouldn't even light up for charging that it was pretty much fried. Definitely got that sinking feeling in the pit of my stomach.
I definitely should have come into this section specific to my phone and read this info instead of just doing tons of searches and getting mixed up.
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Once again thought, thanks for the help. Especially to a noob that made a real noob mistake lol.
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.
willowmp said:
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Click to expand...
Click to collapse
Well once you are retry the flashing on your new phone, just msg me & I'll give you my contact info & I'll walk you thru it.
willowmp said:
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.
Click to expand...
Click to collapse
while the attempted flash was boneheaded , this (what I quoted) was very smart. I've had them try to reverse the decision and noted on my account in the past. All ended well, but a hard copy of the convo between me and Corporate would have been nice to have.
props for a good idea.
if you don't want trouble with rooting and flashing new ROMs to your phone, try flipz's pre-kitchen. just to try it, i RUU'd my phone and re-rooted it through that app, and its simply amazing. you just sit back and watch, don't even have to do anything.
Ok so its pretty funny but whoever it was who says that once you flash for the first time its addictive, I do have to agree. I will be getting my phone tomorrow because they had to replace it and I will be flashing, although this time I will play it safe and triple check before I get click happy...lol
So what are the danger zones in flashing, like what can brick or kill your phone? I know playing with radios can kill it if the wrong one is flashed, and I know powering off or interrupting a flash will kill/brick, but what else.
I know people said firmware alone usually will not brick you.
willowmp said:
So what are the danger zones in flashing, like what can brick or kill your phone?
Click to expand...
Click to collapse
Well obviously it can brick your phone if you flash the Radio I kid, I kid
willowmp said:
I know playing with radios can kill it if the wrong one is flashed
Click to expand...
Click to collapse
With the CDMA Hero, you do not have to flash the Radio. So if your attempting to flash the Radio, you're doing it wrong.
willowmp said:
I know powering off or interrupting a flash will kill/brick, but what else.
Click to expand...
Click to collapse
Well if the custom recovery is installed (RA-heroc), if the phone looses power while flashing the firmware, you are usually still safe, because you (usually) still boot into the recovery without issues.
Like I already said, if you want I can walk you thru the entire process thru an IM client, Steam, or Skype.
Oh ok thanks, I'm actually headed up to PA for a little trip but definitely will hit you up on that offer when I get back.
I've been waiting patiently for my 2.2 OTA upgrade ... now my patience is running thin as hell with Samsung as well as t-mobile for not stepping in to remedy the problem. The worst part is that I just heard that Samsung pulled the 2.2 update from kies. So this is probably a bad sign for any one who is afraid to root or scared the void any warranty.
Im unfortunately one of the ones that hasent wanted to root cause im still paying off my phone. I know its easy, I just want the option to claim warrenty.
Im giving them until the new year to release an OTA for 2.2 or 2.3 if not that a date and then first deadline they miss in rooting.
Sent from my futuristic phone
I say go ahead and root. Then read a lot. Read some more. And then flash. Don't worry about the warranty. You can always flash back to stock and unroot. They'll never know or care.
Honestly, you're probably not going to get 2.2 by years end. Gingerbread is out and we're still running software that was released over a year ago. At this rate, we'll get Gingerbread (if we ever) couple months after Honeycomb is released..
edit: I also applaud your patience thus far. I couldn't even stand waiting more than a week for JI6 update (after it was reported it was being released OTA), which prompted me to root + flash.
anthonys2r said:
Honestly, you're probably not going to get 2.2 by years end. Gingerbread is out and we're still running software that was released over a year ago. At this rate, we'll get Gingerbread (if we ever) couple months after Honeycomb is released..
edit: I also applaud your patience thus far. I couldn't even stand waiting more than a week for JI6 update (after it was reported it was being released OTA), which prompted me to root + flash.
Click to expand...
Click to collapse
Actually I was one of the lucky ones with JI6. I got the update notification the same day it was announced.
If it wouldn't be too much to ask could some one point me in the direction of a n00bs guide to rooting and flashing
Sent from my futuristic phone
I would just go with the One click lag fix for rooting. I think the .apk that allowed you to root got pulled from the market. But if you search around here... you can still find it. Very simple, just install the app, click root, boom, start flashing away. Just search for One Click Lag Fix, gotta get one of the older versions though.
Root, read, learn, then install the Stock JL4 Froyo Rom some of us are running. It's pretty slick and practically perfect.
Go ahead and use ODIN and update to 2.2 FL4. You wont be disapointed, unless you talk about battery life. I lost an hour at least going to 2.2. However, the features/speed improvement is well worth it.
I will NEVER EVER EVER buy a phone again that has less than a 12h active battery life again. This looking for a place to charge like a crackwh** is getting old fast.
Haxel said:
Go ahead and use ODIN and update to 2.2 FL4. You wont be disapointed, unless you talk about battery life. I lost an hour at least going to 2.2. However, the features/speed improvement is well worth it.
I will NEVER EVER EVER buy a phone again that has less than a 12h active battery life again. This looking for a place to charge like a crackwh** is getting old fast.
Click to expand...
Click to collapse
I will definatly start doing my research for certain rom's.
I feel ya on the searching for a quickee charge lmao ... I bring my charger with me everywhere
Sent from my futuristic phone
Another question will I be able to install multiple rom's and freely switch between them
Sent from my futuristic phone
ironlood said:
Another question will I be able to install multiple rom's and freely switch between them
Sent from my futuristic phone
Click to expand...
Click to collapse
No. If you install another ROM, it will overwrite your previous.
Okay ... so what is a rom manager for ??
Sent from my futuristic phone
Haxel said:
Go ahead and use ODIN and update to 2.2 FL4. You wont be disapointed, unless you talk about battery life. I lost an hour at least going to 2.2. However, the features/speed improvement is well worth it.
Click to expand...
Click to collapse
I am in the same boat - except that I have rooted. I didn't flash a custom ROM since it's so much more difficult than on the G1 which had the excellent Amon Ra recovery to do BART backups in case something went wrong and a flash from a zip file side loaded on the phone.
Flashing ROMs on this is so much more convoluted with ODIN, kernels etc. Plus 2.1 was decent enough on the phone and I kept expecting Samsung to release 2.2. But this is now getting ridiculous and I'm getting pissed of as well. This is definitely the last Samsung phone I'm buying. My next phone is definitely going to be an HTC. HTC modding is stabler and more advanced for obvious reasons, not least of which is that HTC seems relatively okay with it.
What is 2.2 FL4?
FL4 is the latest "leak" of the 2.2 "final" rom for the Vibrant.
Dont listen to others that are saying to factory restore, after you are done with the flash, boot it into recovery (the volume button turn on) and just clear the cache, then reboot. You wont lose any data. (If you rooted 2.1 you will may have to factory restore, but it doesnt hurt to try the cache trick first. The method I'm referring to seems to work best if your a non-root user like me).
Haxel said:
FL4 is the latest "leak" of the 2.2 "final" rom for the Vibrant.
Dont listen to others that are saying to factory restore, after you are done with the flash, boot it into recovery (the volume button turn on) and just clear the cache, then reboot. You wont lose any data. (If you rooted 2.1 you will may have to factory restore, but it doesnt hurt to try the cache trick first. The method I'm referring to seems to work best if your a non-root user like me).
Click to expand...
Click to collapse
I seen or read about the cache trick somewhere on here before just can't remember where.
Sent from my futuristic phone
Can someone post a link to a good thread so I can research what I need to do or atleast provide me with the right word or phrases to search.
My first concerns are what everything is, like ODIN and OCLF (I finally figured out the OCLF thanks to this thread means one click lag fix ... I never put 1&1 together) Also they put the OCLF back in the market with all the tools just minus the ROOT option. Reading through the help file provided with the OCLF app he tells you what you can do to obtain root.
Sent from my futuristic phone
Haxel said:
FL4 is the latest "leak" of the 2.2 "final" rom for the Vibrant.
Dont listen to others that are saying to factory restore, after you are done with the flash, boot it into recovery (the volume button turn on) and just clear the cache, then reboot. You wont lose any data. (If you rooted 2.1 you will may have to factory restore, but it doesnt hurt to try the cache trick first. The method I'm referring to seems to work best if your a non-root user like me).
Click to expand...
Click to collapse
FYI just to clear up any confusion- it's JL4 not FL4
Sent from my SGH-T959 using XDA App
I'm giving them until the end of the year before I do the same.
All I want is wifi-calling =\
I was in the same boat. It's my wife's phone and she didn't want me screwing with it.
I finally gave up on samsung and installed stock jl4 yesterday and couldn't be happier.
Haven't really seen any bugs at all yet. It's running great.
I've been looking through a few rooting threads to gather information. I see people saying that there making backups and installing busybox or superuser. If acquiring root is as simple as a button press and a restart why make a backup. I understand that It's always good to make a backup when delving into the inner OS.
Also the OCLF, Super Oneclick, and Z4root, methods I've researched are a little less explanitory then i thought. They just say something like "INSTALL AND CLICK ROOT" nothing step by step or anything talking about safty precautions.
Sent from my futuristic phone
A titanium backup will allow you to restore your apps and more importantly your app data with just one click.
I work in a large company. We have 40 Wildfires (long story).
I want to build up what we want to have on one phone.. then image it and push to the rest..
Any ideas????
insanemal said:
I work in a large company. We have 40 Wildfires (long story).
I want to build up what we want to have on one phone.. then image it and push to the rest..
Any ideas????
Click to expand...
Click to collapse
Default or cm7
Sent from my HTC Desire using Tapatalk
Not sure yet. Both if possible. I would like to run CM7 but im not sure the warrenty will cover it.. at least if it was a modded stock rom they would have less case to clam we did something horrible to it. But if I have to have a custom rom I would want to keep the stock boot animations.
Your warranty will be lost in case you flash CM or any custom modded stock ROM.
Yeah probably,
But this is not the point.. I need to customise 40 of them...
If I can't use a modded stock rom, I don't care.. I just have no idea of the easyest way to get this done.
Build the ROM to your liking on on one phone, take a Nandroid backup of that, and provide that to the 40 other phones, and restore from it. It should work. I can't think of any method to 'Push' it yet.
Warranty should not be an issue. RUUs are always there if you mess something up. My screen got messed up, and with an RUU I made it completely factory (including the HBOOT - it replaces it) and gave it to HTC service, and they are replacing it under warranty now.
nhnt11 said:
Warranty should not be an issue. RUUs are always there if you mess something up. My screen got messed up, and with an RUU I made it completely factory (including the HBOOT - it replaces it) and gave it to HTC service, and they are replacing it under warranty now.
Click to expand...
Click to collapse
I hope they don't give it back to you with factory updated 2.2.1. This sort of thing happened to many around here.
Anyhow, I was only suggesting that because the OP seems to want his phones for business purposes, and, I thought, for such situations, warranty and productivity is the most important factor, and, terms like modding and customization take a back seat.
3xeno said:
I hope they don't give it back to you with factory updated 2.2.1. This sort of thing happened to many around here.
Anyhow, I was only suggesting that because the OP seems to want his phones for business purposes, and, I thought, for such situations, warranty and productivity is the most important factor, and, terms like modding and customization take a back seat.
Click to expand...
Click to collapse
I told the guy 3 times not to touch the software, and he assured me he won't lol.
Me: Will you update the software or anything?
Him: No problem. We'll do it for you if you want.
Me: I DON'T WANT IT OMG.
Him: Sure we won't update then.
They seem to know about root and stuff
I agree though, if it's for business then CM7 doesn't really seem appropriate, although it would make my respect for the business ++
nhnt11 said:
I told the guy 3 times not to touch the software, and he assured me he won't lol.
Me: Will you update the software or anything?
Him: No problem. We'll do it for you if you want.
Me: I DON'T WANT IT OMG.
Him: Sure we won't update then.
They seem to know about root and stuff
I agree though, if it's for business then CM7 doesn't really seem appropriate, although it would make my respect for the business ++
Click to expand...
Click to collapse
But they are giving you a new device ? Than it will have the updated Hboot lol ! Yeah offcourse they know, that's why they updated hboot!
h4oxer said:
But they are giving you a new device ? Than it will have the updated Hboot lol ! Yeah offcourse they know, that's why they updated hboot!
Click to expand...
Click to collapse
no only replace screen.
i meant the service center guys know about it. not HTC lol.
3xeno said:
Build the ROM to your liking on on one phone, take a Nandroid backup of that, and provide that to the 40 other phones, and restore from it. It should work. I can't think of any method to 'Push' it yet.
Click to expand...
Click to collapse
Cool, I didn't realise a Nandroid could be restored to other phones.
Also we got lucky, they are running HBOOT 0.80.0008
Seems the OTA updates didn't apply. So the hard part will be rooting them all... wow.. so slow.. I will prolly use CM7 as a base.. But I'm not sure.. I need a way to Have GMAIL but not Market. Can I add the GAPP's pack and then remove the market.apk? Also we want NONE of the stock 'bigpuddle' crap on the phones as the users only have small data allowances. Hmmm Also the GAPPS' pack is it gmail maps and Market? Because we are only 50/50 on having email on the phones.. if it is.. I might just leave it out all together.
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
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Ciclop said:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Click to expand...
Click to collapse
Just make sure anything u do you read the thread and defiantly the op and only flash stuff that made for the N4 u should be good. Read read read and learn. I've only bricked one phone and I know what I did wrong its very hard to brick a phone so long as u don't just go flash stuff u dont know what it is.
Oh yea don't over clock your phone and run benchmarks its stupid and has fried a few also. I'm onderclocked to 1134 and I still run smooth as butta.
Sent from my Nexus 4 using Xparent Blue Tapatalk 2
Ciclop said:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Click to expand...
Click to collapse
For a REAL hard brick on a Nexus device, you really have to do something wrong. Like I did with my Nexus S .
A real hard brick, one that isn't even repairable with a JTAG brick repair service, it never happens with a Nexus device. Well, ALMOST never. I made it happen. I don't even know what I did wrong, but apparently I screwed up the radio. Even the best of the best (Adam Outler) wasn't able to repair it. It happened the day after I installed a new ROM and a mod. The battery drained really fast. After it was dead, I plugged it in the charger, booted up my phone, started the browser, and BAM. Dead. Forever.
But I wouldn't worry about those things. Just don't do too much overclocking, because there are ways to screw up the hardware inside. Almost all bricks are fixable. If you can access fastboot mode you're okay. If you can't, there are still ways to fix it, but it might cost you some money. I don't know if Adam Outler's Unbrickable Resurrector tool works with the N4, but that's also an option if you think you really screwed up.
1) Make sure that you never flash a file that wasn't designed for the Nexus 4 (MAKO)
2) Make sure that you don't have empty batteries when you flash. 50% would be a safe minimum (though I personally frequently flash with much less than that)
3) Flashing radios / bootloaders is traditionally amongt the most dangerous operations that you can do. Make sure to check MD5 on all radios (you can check on every file if you want to be super careful)
Note: the reality is that with a nexus device, it's almost impossible to brick your device. Even if you do all of the things above wrong, you'r probably still safe. BUT, you were looking for advise--so follow those three points and you should be fine.
OP, read the link in my signature about toolkits and it will answer your question.
Sent from my Nexus 4 using xda premium
Thank you all for quick replies!
I only plan on flashing Franco's/Faux's kernel, hopefully everything will go well
unlocking the BL on a nexus is very easy. I am not sure if you need a toolkit for that.
but yeah use one if you feel more comfortable with it.
also as of now do not overclock the processor as that has been causing some bricks AFAIK.
Androyed said:
For a REAL hard brick on a Nexus device, you really have to do something wrong. Like I did with my Nexus S .
A real hard brick, one that isn't even repairable with a JTAG brick repair service, it never happens with a Nexus device. Well, ALMOST never. I made it happen. I don't even know what I did wrong, but apparently I screwed up the radio. Even the best of the best (Adam Outler) wasn't able to repair it. It happened the day after I installed a new ROM and a mod. The battery drained really fast. After it was dead, I plugged it in the charger, booted up my phone, started the browser, and BAM. Dead. Forever.
But I wouldn't worry about those things. Just don't do too much overclocking, because there are ways to screw up the hardware inside. Almost all bricks are fixable. If you can access fastboot mode you're okay. If you can't, there are still ways to fix it, but it might cost you some money. I don't know if Adam Outler's Unbrickable Resurrector tool works with the N4, but that's also an option if you think you really screwed up.
Click to expand...
Click to collapse
My N4 its bricked, I contact Google for RMA. Now, my history...
N4 bought 13/nov.
-Rooted with Nexus 4 Toolkit
- ROMS installed: 1- Stock (default) 2- Minco 3- Xylon (when i got bricked)
- Kernels:1- Stock (default) 2- Franco 3- Faux (when i got bricked)
In kernel Ops: (Last Faux beta kernel)
- Underclock: (YES, READ, UNDER): 1mgz at max
- Undervolt: -137 mv all freqs
- GPU Downgraded to 200mhz
- Screen settings changed
- Hapatic feedback downgraded to 50%
That was my config. Now comes the drama...
My phone was perfectly OK at less for 2 days with that kernel and ROM combination (because i've updated few days before got bricked) So, my phone even with the downgrade config was so smoth and everything was perfectly ok.... the night of new year, when I was taking a shower, my N4 was charging SO SLOW, i dont give a f*ck and continue my night so normal, then I went out to my gf house, i have like 30 % and decide to charge again, starts charging slow again, now im worried about it so i decide to restart the phone, and problem still there... but now the device was overheating so much and the phone got discharged because i got to go, when I come to my house in the morning, i put the charger, the only thing it do is blink red led, nothing else.
Conclusion:
When your phone got bricked doesn't mean you have the guilty, because mine was STABLE for at least 2 days, for my, it was an hardware prob.
Now, the only way, RMA.
So if I was you, I lock my bootloader again.