First off, sorry if this post is in the wrong section. I thought this was the best place for it.
So, I am about to get a Cingular 8125, aka HTC Wizard or whatever.
Now, before I start the flashing roms deal, I wanna ask a few questions.
Before that let me tell you that I have a lot of experience with Windows Mobile 5 on a Cingular 2125. I've had that for about 2 years, until a water incident. Luckily I can get a 8125 because of my 2 year contract. Also, I'm not computer literate. I'm actually quite intelligent when it comes to computer type questions. This might not affect my knowledge with ROMS, but computer terms won't be hard for me to understand.
Okay, this is coming in the mail tomorrow afternoon. My questions are:
1. Can I ruin a warranty by flashing a rom?
2. What does "brick" a device actually mean. I know it means ruin it, but do you mean cause it to become unbootable?
I had a few questions but they slipped my mind. I'll post more questions if I can think of more.
Thanks for the support!
The term brick is used to describe a pda that is entirely unusable. A bricked wizard refers to a wizard that is unable to enter bootloader mode, and hence unable to be flashed with anymore roms.
Flashing roms is generally considered a void of warranty. It is often a good idea to flash back your original idea prior to submitting your device for warranty claims.
stuff said:
1. Can I ruin a warranty by flashing a rom?
Click to expand...
Click to collapse
CID Unlocking and flashing a custom rom voids the warranty. Period. But, they have to look to see that you've done this for them to hold that against you. So if something happens and you need to do a warranty replacement, then flash it back to an official rom (hopefully whatever happens doesn't render it unflashable). There are some that won't flash for this reason (or use the thread on how to flash without CID Unlocking that the G4's use. But I've heard some G3's have been bricked by this process).
2. What does "brick" a device actually mean. I know it means ruin it, but do you mean cause it to become unbootable?
Click to expand...
Click to collapse
A Brick is a term used to describe how useful the phone is after something went wrong and the IPL/SPL (like a PC's BIOS) has been hosed so its no longer bootable. Some have raised their phones from the dead (brick state) but using a process to flash rom the SD card (read the wiki as it has a pointer to how this can be done) or via JTAG (I only know of the process, not how or where to do it, but it involves opening the phone and soldering wires as I understand it).
Understand though that a lot of people here throw around the term "Brick" to describe when the phone just doesn't boot normally. IMO that is not a brick as the phone is "easily" recoverable.
So basically the only way I can "brick" the phone is by doing something completely wrong?
The first thing you should do is determine if your phone is a G3 or G4. You use different techniques with each one. Then read and ensure you fully understand the unlocking/burning directions for your particular model (G3 or G4). Also ensure you accomplish each and every step, don't skip anything.
calouro said:
The first thing you should do is determine if your phone is a G3 or G4. You use different techniques with each one. Then read and ensure you fully understand the unlocking/burning directions for your particular model (G3 or G4). Also ensure you accomplish each and every step, don't skip anything.
Click to expand...
Click to collapse
Will do. I'm hoping it a G3, that way I can have an easier experience and people can help me out easier.
Related
First of all I just want to say WOW what an insightful and creative community you guys got going on around here. A lot of smart people on these boards. Thanks for the resources you guys provide to make having a cell phone into a hobby.
I have just successfully rooted my phone after hours of deduction and have flashed RC33 and a radio ending with 1.1. I've spent about 4 hours getting to this point and still feel behind the game. What motivated me to do this was the Official Hero Rom in the Android Development Thread and that is my ultimate goal insofar.
However, now that I've done this I don't want to take any unnecessary risks. I've used the dandy search feature and done hours of research as well as lurk on here since the launch of the G1 when I picked up the phone on launch day. I know about all of the informative links and they're great and I've reviewed them thoroughly but am still fuzzy on a few things.
I've read that there are different types of SPL's some brick and some don't. Please correct me if I'm wrong but my understanding of an SPL is that it is basically the update.zip file in my SD card. Currently that is a build of RC33 in my card along with recovery.img. For some reason I feel that this is not all as far as an SPL is concerned. If someone can concisely clarify this for me that would be great.
Also before I jump on Hero, what is a good cupcake ROM around here that is stable and not lacking many features that can easily be blinged out with one of the awesome themes you've got floating around here. I'm open to all enthusiastic suggestions. What tips do you guys have for me to move up to one of those?
I have not even begun to delve into App2SD or Nandroid but am getting a clearer image as to what they are and how they function. Any helpful tidbits on the two subjects would also be greatly appreciated, however they are not my main concern immediately.
Again thanks guys I've got work in about three hours now lol so I'm going to get some shut eye however I'll be back tomorrow. Soon, I hope to contribute to what you guys have got going on.
Unfortunately your hours of deduction did not lead you to this thread. Which has a link to this thread. Which has definitions, two I am posting here:
Bootloader – the SPL and IPL of a flash based device. See jashu’s description here.
SPL (Secondary Program Loader) - You get to the SPL by holding the camera button while powering on your phone. This is where you flash NBH images. See bootloader above.
Click to expand...
Click to collapse
Which links you to a greater explanation of what the SPL is.
Personally, I don't think the Hero builds compare with Cyanogen's Scary Experimental builds. I believe you sacrafice a lot of speed to gain very little (if any) functionality. Don't let the misnomer of "Scary Experimental" throw you off. His latest 3.5.3 blows everything else away. It's within a build or two of being declared stable. And most of the tiny little issues with 3.5.3 can usually be fixed with instructions being posted in that thread.
Moving over to Cyanogen's 3.5.3 is braindead simple too. Don't rush, follow the recommended upgrade path, and you'll be set. It does all the work for you, and it doesn't require the sometimes dreaded new SPL (which, BTW, is not nearly as risky as some will lead you to believe ... you just have to properly follow the required steps). Still, will this being your first attempt at any of this, you'll find it much less taxing on your nerves by sticking with a more straightforward upgrade. Cyanogen's is a great way to get your feet wet. And in the end, you'll end up with a blazing fast phone with all the bells and whistles too. Your phone will impress the moment it first boots. There are themes available now, and more will be coming once it hits stable. Apps2SD are automatically done for you if you have your sdcard formatted correctly. There are a myraid of ways to get the correct partitions on the sdcard, so do that before anything else. It will increase your chances of making this successful on the first attempt. Remember that a wipe is not necessarily a bad thing, it's usually that a failure to wipe is what caused your problem in the first place. Wipe if it's recommended. Read the comments to determine when it required, when it's just a recommendation, or when it's not necessary.
Be methodic. Since this is your 1st attempt at this, you'll be doing yourself a huge favor if you grab everything you need all at once. Don't try to take any shortcuts, follow the steps or instructions to the t. Make sure you have the latest radio installed (and the new SPL should you pick a build that requires it). Although they usually list the latest builds in the 1st post of a particular topic, occasionally they will release in intermediate fix within the thread itself. Check the last few 10 or so pages of comments for your build of choice to see what build is recommended at the time. Usually, you'll want to grab the latest build, but that's not always the case. Bleeding edge is not always best (althought with C's Scary Experimental, I've eagerly awaited each and every update because it's only gotten better each time).
Since you've done your research, go back and outline the entire upgrade path. Write it down for reference. Make sure your Windows driver are up-to-date, have the latest ADB installed on your computer (it makes things much easier if you use ADB if possible), don't do anything until you can devote a couple of uninterrupted hours to the upgrade process, and I cannot emphasize enough to WIPE as necessary. Hell, don't install any programs or fiddle with any settings. WIPE each step along the way until you get the final build installed. If something doesn't seem right any step along the way, don't proceed to the next step. WIPE again and re-flash. See if that fixes your problem. If it does, the proceed. If it doesn't, see if it's an issue that fixed with the next build you'll be flashing. If so, proceed. If not, look for another solution. Proceeding at that point _might_ be okay, just be aware that you might get yourself into a situation that requires re-rooting your phone.
Make sure that before you do anything else that you have one of the modified recovery images flashed to your phone. They're modified for a good reason.
If things go bad, don't panic and start posting that you've "bricked" your phone. Chances are you haven't. Very few phones get "bricked" to a point you can't fix it yourself. When people around here see the term "bricked" as a subject in a post's topic, it's a red flag that becomes a red herring for you. You may get into a boot loop or something, but it's usually fixable with a WIPE and an update.
Also, keep DREAIMG.img in the root of your sdcard at all times. Don't move it, don't delete it, don't rename it. It can, and will, save your ass if any of this hits the crapper. Carry it with you at all times. If you have DREAIMG in the root directory, you'll always be able to get your phone back to an operating condition, wherever you are, whenever you might need it, without the need for a computer. Yes, it would be starting all over again, but it would give your phone basic functionality if all goes to hell and you're not near a computer or don't have a USB cable or something.
None of this requires a PH.D. It's actually quiet simple. Most people that run into problems have simply missed or skipped a step, or failed to wipe as required. Knowing recovery proceeds in advance will be helpful, but even that is pretty straightforward and easy to follow. I've done all these flashings, re-flashings, recoveries, etc., so much that I --think-- I have the terminal commands etched in my memory. And I do. But I still refer to the on-screen steps to make 100% sure I'm typing things correct. I hit enter only after I'm confident I didn't type a 0 when it should be O (hehe). I look at the screens during the whole process for indications of success or failure. And I make sure that I am not distracted by anything when I upgrade. Lock yourself in a room by yourself after you've emptied your bladder. If you do get interrupted or have to take a bathroom break, write down the next step. Don't assume you'll remember. And don't even think of making or taking phone calls until you've finished this whole thing.
Read in advance.
Search as necessary.
Ask, in the appropriate forum and thread, when all else fails.
You'll do fine.
Good luck.
Found this over at the HD2 forum but it's relevant here!
Here are the top ways to screw up your Streak. If you are a non techie, pls read this!
1. Installing apps/apk's that are not meant for your Streak. This i think is the most common issue. Check the thread on apps list to ensure its safe. When in doubt, read the info or Check with others
2. Playing around with Rom. (installing 2.1 if you don't have a clue what you're doing) If you don't know how then don't do it. If you are game to test out new rom, read the step by step instruction CAREFULLY, if in doubt still DON'T do it.
3. Rooting. Falshing a boot.img This is highly risky if you don't know what it changes
When any of the above happens and nothing seems to work right, the most likely thing to do is do a hard reset.
The good news is after hard reset your phone might work again!
this is kinda redundant info since we are very lucky with the streak as right now there is no way to permanently damage your streak. unlike other devices which totally brick when a flash goes wrong.
Only number 3 has any chance of screwing up your streak, and even so, it would be a very easy fix.
To start off with I have had my phone rooted since my g1 in 2009. I did not hesitate to root my mytouch earlier this month and it was successful. Unfortunately, my phone would no longer boot (not turn on at all) after a week of being rooted. I am not sure if rooting caused the error but now I am afraid to root my replacement. I wanted to at least flash my backup but I am afraid to even root for that. Also I should add that I root to flash roms not because I think it's "cool". Can anyone give me advice on if I should root again?
What did you flash right before the phone would not boot or turn on at all? Perhaps it is not the root but the roms that you are flashing. I certainly am not an expert but perhaps you might just try rooting and than wait a few days before trying to flash any roms. Also all that I have read states that you should read up on all the procedures and follow them to the letter. I have had that brought to my attention in a couple of instances. I just received my replacement (screen issues) and have rooted it again and so far things seem okay. I am going to wait and read and learn more before I flash a rom again. Good luck!!
tenbeau said:
What did you flash right before the phone would not boot or turn on at all? Perhaps it is not the root but the roms that you are flashing. I certainly am not an expert but perhaps you might just try rooting and than wait a few days before trying to flash any roms. Also all that I have read states that you should read up on all the procedures and follow them to the letter. I have had that brought to my attention in a couple of instances. I just received my replacement (screen issues) and have rooted it again and so far things seem okay. I am going to wait and read and learn more before I flash a rom again. Good luck!!
Click to expand...
Click to collapse
Yeah, I had flashed the hd port after using the z port and that's when the issues started. I think I will root again and just try to be more careful even though i am pretty sure I followed all instructions.m
Sounds like to me it was just timing between phone hardware and your flashing. Unless you are screwing around with with the ROMs prior to flashing without knowing what your doing you should have no issues. If it was ROM related you would see these boards all lit up with people having the same issues...and you simply dont see that.
Hey, I have 2.1 (Eclair) Wildfire here. Never updated.
Before I root with unrEVOked, I'd like to ask about one thing.
It it possible for it to brick the phone? And if so, at which stage exactly and how can I prevent it?
Could anyone give me an answer?
Rooting and flashing is allmost save. If you follow the guides for rooting / flashing you will go a very save way.
Okay, there is also a liitle chance to brick it. You get a bluescreen while flashing = good chance of a brick (but if this happens there is still a chance to get it back to life). Your cat plays with the usb cable while flashing = also nice way to brick it. Or you just didnt follow the rules of flashing.
If I got this blue screen, how would I go about fixing it?
how to fix your phone or computer?
your computer... dunno.
your Phone...
If you try to flash a custom rom and your pc crashes or something and it fails, try to reflash with a standart www-ruu rom from shipped roms.com.
NEVER use a stock-froyo rom for reflashing!
You have to root again but mosttimes it will work.
I though you meant bluescreen on a phone... I haven't used windows for ages, I got confused.
Bump......
still waiting for goood answer too
Don't root it if you are so paranoid. :/ It doesn't brick the phone at all (Can't see any reports anywhere that Unrevoked bricked 2.1 Wildfires while rooting.)
Obviously, as no thing is 100% certain, there has to be disclosures that "Use it properly else it will be bricked... etc", but, if you follow the proper procedure and use some common sense, its next to impossible.
It's technically possible... Writing the recovery is the dangerous part... But it only lasts 5 seconds..? Something like that, so if the connection breaks (Phone dies, computer dies, usb dies, battery explodes, all of the above) WITHIN that five seconds then you're sc00d. If you're paranoid, don't, and miss out.
---snip---
Howdy. Tried to root my OnePlus 8 Pro. First time trying such a thing... Having now bricked my phone into a boot loop, I'm pretty sure that the guide I followed missed an important step. It said to download the latest patch, extract it, then use magisk to patch it and flash it. I'm pretty sure that the part I missed was actually updating to that patch before flashing. So I have whatever latest patch that I didn't have the foresight to write down, but my original build was IN2025_11_C.33 . Am I boned completely and thoroughly or is there any hope of recovering? Thanks either way.
LOL, welcome. Wisely, you've chosen a phone that supports EDL, with known ROMs. EDL will allow you to reflash to factory, no matter how badly you've messed up, assuming you didn't brick the hardware (which, unfortunately, is actually possible with this phone- there's two different RAM voltages and you can flash something that writes the wrong one and literally fry the phone... sigh)
All the stuff you need is covered in other threads here, and in other OnePlus forums on XDA... too tired to summarize them all (sorry). Search for the MSM tool (I think the one you want is here but please double check) and how to use it. Happy flashing, and welcome to the best phone mfr to mod! (Note EDL requires a Qualcomm chipset, there are other OP phones that do NOT have them... so not EVERY phone is bailable-outable...)
SomeRandomGuy said:
LOL, welcome. Wisely, you've chosen a phone that supports EDL, with known ROMs. EDL will allow you to reflash to factory, no matter how badly you've messed up, assuming you didn't brick the hardware (which, unfortunately, is actually possible with this phone- there's two different RAM voltages and you can flash something that writes the wrong one and literally fry the phone... sigh)
All the stuff you need is covered in other threads here, and in other OnePlus forums on XDA... too tired to summarize them all (sorry). Search for the MSM tool (I think the one you want is here but please double check) and how to use it. Happy flashing, and welcome to the best phone mfr to mod! (Note EDL requires a Qualcomm chipset, there are other OP phones that do NOT have them... so not EVERY phone is bailable-outable...)
Click to expand...
Click to collapse
thanks!
dimlu said:
thanks!
Click to expand...
Click to collapse
In case you haven't sorted it yet - this is a great MSM guide which also links to the Windows drivers you need and the MSM tools for your device.
Good luck