I know there are a lot of newbies out there trying to cook with the ROM kitchens and running into problems--wanted to provide a little advice to save you from yourselves. But first, my story:
This weekend I was playing around with Faria's ROM Kitchen. Wasn't really paying attention to what I was doing, and forgot to load the Start Addresses and Image Names in nb2nbf before flashing. Guess what? Got myself a brick. Wouldn't go past the initial boot screen, and I couldn't reset it to save my life. Mustering my calm I set out to fix it...popped out the battery to reset the device...entered bootloader mode (hold camera button after soft reset)...follow Dr Puttingham's outstanding tutorial to reCIDunlock...flashed a few ROMs to get back to IPL/SPL 2.x and I was back in business.
Point of all this is not to blame others, learn about what you're doing and fix your own mistakes. Pointing fingers and someone's ROM won't get you there. Paying attention to what you're doing would also help (still gotta learn that one myself obviously!) Most importantly, before digging into these advanced topics, learn how to save yourself if something goes wrong. Know enought about your device (G3/G4, etc) to know if you should even be doing what you're about to do!
</rant></down from soapbox>
And yes I know this is a non-technical post in a technical forum, but maybe it will help cut down on the chatter and keep the other threads on topic!
nice. beautifully written my friend.
Your device was never bricked.
People do need to know how to recover from a failed flash and not create a new thread for something that was already said!
great
maybe one thing that is not said here is luck... in your case you know what to do and have found solutions
Agreed, not really ever a brick. I've had my computer simply turn off in the middle of flashing before. Just reset to the "flag" screen and reflash. A brick is where you flash the _WRONG_ ROM and it won't even go to the tri-color screen.
im in a panic
need a solution:
I have successfully flashed many roms before. Today i was flashing BlackDiamond 1.1 ROM and i was at 92%, My PC restarted (this is my prob). I have done nothing yet on Phone and its still showing 92%(with blue bar). I tried to run update again biut its giving connection error 264. Does this means im bricked (plz. dont say yes). Im in a desperate need of quick help.
Out Of panic. Done flashing using bootloader help http://forum.xda-developers.com/showthread.php?t=294107 . Running fine
Pastamancer said:
Agreed, not really ever a brick. I've had my computer simply turn off in the middle of flashing before. Just reset to the "flag" screen and reflash. A brick is where you flash the _WRONG_ ROM and it won't even go to the tri-color screen.
Click to expand...
Click to collapse
Does a brick give light? NO. Then that phone was never a brick
Sometimes good intentions can mislead others and set hopes high... (maybe changing topic's title)
Wow, didn't think I was digging in to the metaphysical meaning of the term's exact definition...Don't think it changes the original intent that people should spend a little more time reading about what they are doing before doing it!
Fab stuff. I did exactly the same. It's most times we fail to read and are so eager to get going, we miss minute details which make a big difference.
I made a mistake using Dr. Puttingham's guide while only pressing S button and restarting and not doing the C (CID unlock) button and had myself a brick.
Related
i originally had faria's wm6 on my phone, but then i wanted to try xplore core 2.0. i flashed it, but when it finished it would start. it wouldnt go past the second splash screen. i tried a hard reset using the hard keys, but when i try it, it says format failed. i have tried to reflash using bootloader using the OEM carrier roms from both t-mobile and cingular. i am having the same issue no matter what i do. if there is anything i can do to fix this.. please help me because i constantly use my wizard and i don't no what i can do without it. i really appreciate any input. thanks
im not sure what to do but i figured i'd respond just so you know people are trying to help. I've heard of the format failed problem, but im not sure what the solution was. Good luck!
What device do you have ? A G3 ?
How I fixed my Format failed problem...
This is a quote from thread
http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
I followed these steps with an SD card fresh from the package...
Drug_Store said:
...
2- Get a clean SD card (in qtek 9100 / Htc Wizard case is MiniSD) with 128MB (some people say 64MB, but I personally used a 128MB, maybe a 64MB is enough)
3- Kill (task manager) wescomm.exe (this is related with activesync installed on your PC). Insert the blank SD card on the phone.
4- Get your phone in bootloader mode. Like this : Phone powered off, press Camera button + Power On, will enter in bootloader mode (RGB screen).
5- Now connect your USB cable to your phone. And start MTTY_updateROM.exe (http://wiki.xda-developers.com/uploads/romupdate.rar). After open, on Port selection, choose \\.\WCEUSBSH001 and press OK. A window will open with a blank sheet.
6- Type "r2sd all" and hit enter... wait to the end (at end shows "cmd>"). On your phone screen u can follow backup progress... small bar will appear down the RGB screen.
7- Power off the phone (or remove battery), enter bootloader mode (camera button + power on) and this time RGB won´t appear right away. Will ask if u want to "download SD image", press voice dial button to agree, and writting will begin. Wait to the end. Power off and power on normally. Now your phone should be working ok. Not even needed to reflash the phone after this.
Thanks to all and hope this helps more people with this problem
Click to expand...
Click to collapse
thanks guys... im going to try that.. and just so all of you know, its a g3
thanks everyone who helped me out. my wizard is working perfectly again. i appreciate all the help
wow that's awsome
idd, mtty is last chance weapon.
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
GldRush98 said:
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
Click to expand...
Click to collapse
yes, i edited it.
I believe operator error isnt something to blame on the rom. Anyone that openly drops the "F" bomb when discussing a cell phone really should get a life.
GldRush98 said:
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
Click to expand...
Click to collapse
anichillus said:
You are an asshole, pardon my language. My rom doesn't **** systems up, mabe you just don't know what you are doing.
I won't release any more roms. I am just tired of all this SH**. I stay calm and watch people who only know how to complain and don't give a F*** about all the work that's put up just for free, but this does it. I am giving up.
I can't afford to brick my Wizard for people like you who are simply here as ignorant sharks.
Click to expand...
Click to collapse
You sound like Faria...LOL!
Really, that's why I put what I did in my thread about saying "My phone is stuck in bootloader..." (remember the fillet knife?) ROM's DO NOT MESS UP A PHONE UNLESS THEY ARE CID LOCKED, THE FLASHING PC HAS ISSUES, OR BECAUSE OF OTHER OPERATOR ERRORS.
Don't let it get you down. You're doing a good work and if one or two people out of a thousand can't get it right, then they need to be running carrier ROMs, and you can stay calm and happy helping those who really need it.
See, that's not so bad now is it?
GldRush98 said:
woah...
Guess I'll post this...
For the record, the Core 2.0 rom ****ED my phone up too. When I tired to flash back a different rom because of all the changed **** in Core 2.0 my phone flipped out. I had to flash it 3 or 4 times to get it to even boot.
I recommend anyone thinking of tyring Core 2.0 to stay away from it unless they don't plan on changing roms after going to it.
Click to expand...
Click to collapse
i went form core 2.0 back to the tmobile rom and then to the core 2.0n and it worked fine. did you lose connection during the flash or somthing?
anichillus said:
You are an asshole, pardon my language. My rom doesn't **** systems up, mabe you just don't know what you are doing.
I won't release any more roms. I am just tired of all this SH**. I stay calm and watch people who only know how to complain and don't give a F*** about all the work that's put up just for free, but this does it. I am giving up.
I can't afford to brick my Wizard for people like you who are simply here as ignorant sharks.
Click to expand...
Click to collapse
Boy, I know more about what I'm doing then most people here put together.
Your rom ****ed my phone right in the ass.
Luckily I recovered from it.
You call your Rom "stock" yet YOU CHANGED ALL KINDS OF STUPID STUFF IN IT.
Like the alignment screen graphic?
Why the hell would you do that.
Or putting on 3 different boot screens. wtf?
Oh yeah, not to mention it runs like **** before even loading any more software on it since you used the OLD WM6 build.
Don't release any more.
You're terrible at it.
kthx bye.
jawnsixteen said:
i went form core 2.0 back to the tmobile rom and then to the core 2.0n and it worked fine. did you lose connection during the flash or somthing?
Click to expand...
Click to collapse
Nope, flash went to 100% then the phone tried to reboot and nothing happened.
I do all my flashing on that machine because it's stable and I have never had a problem flashing until the Core 2.0 rom. That is the first and only rom I have had any trouble with.
golfernutnflorida said:
I believe operator error isnt something to blame on the rom. Anyone that openly drops the "F" bomb when discussing a cell phone really should get a life.
Click to expand...
Click to collapse
OMG, he used a naughty word.
Like you don't hear it daily?
Get real.
GldRush98 said:
Boy, I know more about what I'm doing then most people here put together.
Your rom ****ed my phone right in the ass.
Luckily I recovered from it.
You call your Rom "stock" yet YOU CHANGED ALL KINDS OF STUPID STUFF IN IT.
Like the alignment screen graphic?
Why the hell would you do that.
Or putting on 3 different boot screens. wtf?
Oh yeah, not to mention it runs like **** before even loading any more software on it since you used the OLD WM6 build.
Don't release any more.
You're terrible at it.
kthx bye.
Click to expand...
Click to collapse
I do my rom as I please, you can't question that.
For YOU to know all roms have 3 (boot =NOT) splash screens You're just too SMARTass to notice.
You can quote multiple post in same message, in case that slipped your soo full-of-knowledge mind.
I used old WM6 build ? Please explain to me what you mean ...i am not that wize
I did not called my rom STOCK ! I called it Core . But you are probably too smart to actually even read anything.
In case you don't understand the word "CUSTOM", then let me explain it to you : I can change whatever i want in it. All of it if I like to.
Ah yeah, and i almoust forgot ... please read this
http://forum.xda-developers.com/showpost.php?p=1241040&postcount=1
It's been there from day 1, just made it bigger now, so that you can see too
And next time, keep your opinions to yourself. No need for public -> "Ooh, look at me how tough I am ! " stunts.
....
whether you like it or not...
I'm confused by people who choose to post cooked ROMs in a public forum, invite people to use and comment, but them complain if the feedback it not all roses and accolades.
You may have done this for free, and many if not most, appreciate your time and effort. That being said, some have legitimate complaints and are posting them because they have experienced problems with your ROM. I’ve been reading your reaction to any negative feedback and you are highly defensive, never conceding that there may be issues to address.
All cooks say that you are not responsible if the ROM bricks someone’s device or if they have problems, and no one has asked for you to pay for their repairs or replace their devices.
There is no place for foul language or insults in such a forum. It's childish and may simply help support the complainant’s point.
If this is your reaction to complaints, then yes do us all a favor and stop posting and keep your work for your personal enjoyment and benefit.
If you can't stand the heat, then get out of the kitchen. No pun intended.
Well if it doesn't work for you then try a different ROM. I tried all the ROMs and pretty much gonna stay with Faria The Real Thing
I tried Xplore 1.0 and i had alot of troube so I dont think im gonna try 2.0. If it works dont change
Funny thing is I have flashed this ROM to my wizard 6 times, and each time something else didn't work. But let me explain...
I want a stripped version of windows, I don't do any messaging at all. And since the Explorer ROMS are known for their stability, it seemed a logical choice. So I have been using package tools, to create packages with option.XML files for each package so you can choose, what parts of the OS get installed.
But back to the point...
Each time I flashed something went wrong... Something I did, a "tmail not found warning when activesync starts", to once I got a 260(?) error once when flashing at 63% so I started it while holding the voice command button. It booted into Bootloader, I flashed it to Cingular 2.25.11 and immediately flashed back to the same ROM successfully.
There are hundreds of people Ecstatic with the Xplorer ROMs, for each one of you here complaining. I for one would think it a travesty, for a few unappreciative people to ruin it for hundreds of others. By pissing off one of our cookers. Maybe had you posted your problems here we would have been able to help you.
But please don't be so accusing, just read, and if you can't find an answer. Then ask nicely, and thank the cook for the time he spends cooking for us! If you don't like the answer you get or you decide you don't like this ROM try one of the many others...
Hi all,
Does anyone know of any ill effects that ROM Flashing may have on the 8925? Specifically, is there any issue with continually flashing the device -- any possibility of corrupting anything and not being able to flash any ROM?
Just curious as I've been testing quite a few ROMs and I'm thinking of start testing my own ROMs just for the learning process.
Appreciate any feedback.
-Mike
ecltech said:
Hi all,
Does anyone know of any ill effects that ROM Flashing may have on the 8925? Specifically, is there any issue with continually flashing the device -- any possibility of corrupting anything and not being able to flash any ROM?
Just curious as I've been testing quite a few ROMs and I'm thinking of start testing my own ROMs just for the learning process.
Appreciate any feedback.
-Mike
Click to expand...
Click to collapse
For what i know, you can do till 100.000 write operations to NAND flash, so don't care about the number of flash you make
The real risk if not having the HardSPL...
Cheers.
jcepsi2005,
Just wanted to make sure.
Thanks for the reply.
-Mike
Every time you flash a device, a baby kitten dies. Please do it sparingly.
Perhaps the biggest effect of flashing comes from the amount of time we all waste playing with our toy phones!
^^ for sure
What about a black out during flashing.... on a desktop with out ups ???
Is bootloader a real protection?
I'm pretty sure there's a way around flashing a device that's had the power cut half way through. You can still get to the bootloader and flash again. Something to do with MTTY...if I remember rightly.
Could be wrong though.
Besides the increasing addiction to this site, you're probably OK. Personally I'd suggest that anyone using a PC to flash anything should consider using a UPS, a power bump is never a good thing and UPS's are pretty cheap insurance.
Since I like to cook and flash alot (as you may know if you've been hanging around the Kaiser upgrade forums ), I've managed to disconnect my device more than a couple of times while flashing. I also managed to cause a short in my USB cable that caused my laptop to reboot every time ActiveSync began transferring files, which was *REALLY* fun when flashing until I figured out what was causing it...
Getting back on topic, as long as you installed OliPro/Pof's HardSPL there is nothing to fear. All you have to do is press the reset button with the camera button to bring up the boot menu and re-flash.
There are other 'advanced' cases of flash failure which I have not encountered, which will require the use of mtty.
goestoeleven said:
Perhaps the biggest effect of flashing comes from the amount of time we all waste playing with our toy phones!
Click to expand...
Click to collapse
AMEN......wife looks at me suspicious everytime I get on this site!
^^ Your's too.
Your wives only shoot you a look? Lucky bastards...
the rom can take all the flashing...flashing your life away, thats a different story.
Holy crap! I thought I was the only one that was having issues with being on this site and the wifey getting all moody!
Maybe it was my response to her when she said to me "well since you spend so much time on that site and flicking and flashing that stupid phone then why don't you go live with it since you're always playing with it"
My response: "Maybe I will!...if only dutty can make a ROM for women then I would have more fun playing with you! Every time I get tired of you I would just flash a new ROM and have a totally different girl on the inside but the same beautiful exterior on the outside"
That comment landed me on the couch hence the reason why I'm posting at 2:20am...haahhah
jb
jbmorales said:
Holy crap! I thought I was the only one that was having issues with being on this site and the wifey getting all moody!
Maybe it was my response to her when she said to me "well since you spend so much time on that site and flicking and flashing that stupid phone then why don't you go live with it since you're always playing with it"
My response: "Maybe I will!...if only dutty can make a ROM for women then I would have more fun playing with you! Every time I get tired of you I would just flash a new ROM and have a totally different girl on the inside but the same beautiful exterior on the outside"
That comment landed me on the couch hence the reason why I'm posting at 2:20am...haahhah
jb
Click to expand...
Click to collapse
If I didn't know better I'd say we married the same woman.
goestoeleven said:
Perhaps the biggest effect of flashing comes from the amount of time we all waste playing with our toy phones!
Click to expand...
Click to collapse
And how many times our significant others scold us doing so.
tsadek said:
If I didn't know better I'd say we married the same woman.
Click to expand...
Click to collapse
haha you know how they always say theres always another you on the other side of the world somewhere.
I currently have the AT&T original WM 6.0 Rom (minus bloatware). I want to upgrade to a WM 6.1 ROM but don't want to spend alot of time reinstalling software. If I backup with Sprite Backup, should it be relatively smooth? Does it matter if I go with a "plain" WM 6.1 ROM or one with alot of programs already on the ROM which I may or may not have on the Backup file? Thanks...
I think most of our wives have the same SPL Locked boot loader (Un flashable) Mine used to tease me about having some buttons installed before she finally gave up and left me to my toys..
Hey guys I like this community and would love to get more involved. I was wondering if some of you could help me understand some of the lingo around here so I can get better acquainted with what I am doing. I would like to load a cooked rom onto my HTC Touch I have the sprint version, but I went to the touch section on the forum and it feels like I am trying to read another language >.< so if anyone could help me understand some of this I would be greatly thankful, thanks in advanced
cooked roms are custom roms. your provider locks your device to only ve able to load roms that they provide... therefore you need to unlock your phone to be able to flash it (through hard spl.)
here is a link on flashing your first rom.
Just follow directions and you will be fine (BUT MAKE SURE YOU FOLLOW THEM OR YOU WILL TURN YOUR PPC INTO A VERY EXPENSIVE PAPER WEIGHT)
Wow thank you tons for the quickness of the reply
no prob
Everything went fine when I was going through the steps, and everything seemed to be going right through the HardSPL step three, but when my phone restarted itself, I got nothing but a backlight I hope I dont have an expensive paper weight >.< Is there anything I can do to fix it?
what phone are you using
Im using the HTC Touch by sprint, but now instead of black it is The HTC smart Mobility screen
The thread i gave you earllier was for a refrence on how to flash....
I'm guessing you tried to install something from that page. (that page was for the kaiser)
You can only flash things made for your device.
Here is a such thread with some refrences to the correct things you will need
http://forum.xda-developers.com/showthread.php?t=458449
PS: if you think you bricked your device here is some info on unbricking
http://forum.ppcgeeks.com/showthread.php?t=24906
Yeah no it's completely bricked now I cant even get it to turn on :/
If you can get to the bootloader on your device by following the instructions here you can save your device:
http://forum.xda-developers.com/showthread.php?t=362768
"hold the end key and the side camera key and stick the stylus into the hole"
you will need to hold the buttons till after the screen comes up (if you can get it to come up)
Yeah I cant even get my phone to turn on now Im guessing its done for good :/
I think i bricked theHTC fuze that i bought yesterday I tried to do the Hard SPL but i was getting an error message, error 244 invalid model ID so i used a program to change the .nbh (a radio file) file so it bypassed the error message (by changing DIAM***** to RAPH*****, since my phone is raphael). I even got a message that the process was successfully finished but it turned out not to be true because the screen went black and now i cant turn it on, and i cant even get it into the bootloader mode. If i could at least get it into to tricolor screen i would be able to flash back the original radio and that would solve the problem because ive already done it a few times. Please let me know if there is a chance to get it fixed, even i had to send it to a professional but as long as it could be fixed, im really desperate. Thank you
brick, htc fuze, diamond, raphael, hardspl
You only get that error when your trying to flash the wrong device... Did you use the file "Raphael_CDMA_HSPL_037.zip" to unlock..?? Sound's to me like you used the Diamond Unlocker... Shouldn't be that hard to fix, hold the volume down button, power button, and insert stylus into the hole on the bottom to soft reset to try and open up BL screen... LMK if that works...
Why didn't you just follow the instructions for flashing? You aren't even security unlocked, so why were you trying to flash a diamond radio? That makes no sense at all. Also, if you are security unlocked, you need to get diamond radios from the raphael forum, because they're patched to flash onto raphaels. It sounds like you got yours from the diamond forum, which is the wrong way to go (especially if it's a cdma radio-that would kill your phone for sure). Did hard spl work? If not, why on earth did you forge ahead? YOU CAN'T DO ANYTHING UNTIL YOU FLASH HARD SPL!!!!!
Try pulling the battery for a while, the see if it will start up. It's hard to tell what you did, but since you went down such a wrong path, I wouldn't be surprised if the phone is a giant brick.
komar808 said:
by changing DIAM***** to RAPH*****
Click to expand...
Click to collapse
this should've been clue #1. If you have to change it because of the device ID, it's the wrong thing to flash. The Diamond and Raph look alike on the front, but are almost totally incompatible ROM-wise.,
I even got a message that the process was successfully finished but it turned out not to be true because the screen went black and now i cant turn it on
Click to expand...
Click to collapse
You are wrong there, it did flash successfully. The tools worked EXACTLY as they were designed. It's not the tools fault
Please let me know if there is a chance to get it fixed, even i had to send it to a professional but as long as it could be fixed, im really desperate. Thank you
Click to expand...
Click to collapse
You might contact olipro, I hear he's got the "magic touch" with devices. No guarantees. I've heard that it's almost impossible to unbrick a device like this after an incorrect/bad radio flash.
I really hope it works out for you. Read dude, the stickies are everywhere for your benefit. Best of luck to you.
brick, htc fuze, diamond, raphael, hardspl
I run into things like this DAILY. Been a service rep for over 30 years. If people would ONLY follow the instructions, I'd have less follow up work to do.
Unfortunately they make these phones too easy to hack (good for us) but sometimes noobs make it hard for the rest of us.
lol
This is what happens when you don't follow directions, don't read enough, and are monkeying with things you obviously shouldn't be monkeying with.
When you got the device ID error, you should have stopped right there and thought "gee, maybe I should go over these instructions again and see what I did wrong" instead of trying to force a radio that will never work on your device.
Hope you can get it in to bootloader, otherwise enjoy your shiny new brick.
Well, hope you get it solved and otherwise you learned a lesson in a very expensive way I'm afraid...
Farmer Ted said:
Why didn't you just follow the instructions for flashing? You aren't even security unlocked, so why were you trying to flash a diamond radio? That makes no sense at all. Also, if you are security unlocked, you need to get diamond radios from the raphael forum, because they're patched to flash onto raphaels. It sounds like you got yours from the diamond forum, which is the wrong way to go (especially if it's a cdma radio-that would kill your phone for sure). Did hard spl work? If not, why on earth did you forge ahead? YOU CAN'T DO ANYTHING UNTIL YOU FLASH HARD SPL!!!!!
Try pulling the battery for a while, the see if it will start up. It's hard to tell what you did, but since you went down such a wrong path, I wouldn't be surprised if the phone is a giant brick.
Click to expand...
Click to collapse
I did hard SPL first with 1.90OliNex (because the one that was in the unlocking package originally didnt work beacuse of the invalid model ID message) and i thought thats what security unlocked the phone and then i tried to put a costume radio that would allow me to unlock the phone but the radio wouldnt flash. So i went back to the SPL from the unlocking package (HARD SPL 1.34) and i changed the .nbh file from DIAM***** to RAPH***** and then it bricked... The reason i did this is beacuse of the following link :
http://forum.xda-developers.com/archive/index.php/t-427305.html
I just hope something can still be done otherwise this is just a good warning for all others not to do this. Thank you for the replies
jdmsohc22 said:
You only get that error when your trying to flash the wrong device... Did you use the file "Raphael_CDMA_HSPL_037.zip" to unlock..?? Sound's to me like you used the Diamond Unlocker... Shouldn't be that hard to fix, hold the volume down button, power button, and insert stylus into the hole on the bottom to soft reset to try and open up BL screen... LMK if that works...
Click to expand...
Click to collapse
No I used a gsm unlocker, HARD SPL 1.34... There is a more detailed explanation in the post above
Hard spl 1.34 is either cdma or diamond gsm-I don't know which. I do know that it will brick a gsm touch pro. Flashing the wrong hard spl is the guaranteed way to kill a phone. If you actually flashed it, the phone is dead. Try pulling the battery for a day.
You need to run the gsm raphael unlocker to security unlock your phone. You need to pay for it, too. Hard spl doesn't security unlock your phone-it only CID unlocks it.
Farmer Ted said:
Hard spl 1.34 is either cdma or diamond gsm-I don't know which. I do know that it will brick a gsm touch pro. Flashing the wrong hard spl is the guaranteed way to kill a phone. If you actually flashed it, the phone is dead. Try pulling the battery for a day.
You need to run the gsm raphael unlocker to security unlock your phone. You need to pay for it, too. Hard spl doesn't security unlock your phone-it only CID unlocks it.
Click to expand...
Click to collapse
I used the GSM one. Ok i just pulled out the battery and hopefully the phone allows to get it into the bootloader...
Worst case scenario, smash it and pay $100 for ur insured replacement... That is, if you have insurance...
jdmsohc22 said:
Worst case scenario, smash it and pay $100 for ur insured replacement... That is, if you have insurance...
Click to expand...
Click to collapse
Hahahaha !
Good one !
But dude no offense but u deserve a black shiny 600$ brick because YOU DIDN'T FOLLOW THE INSTRUCTIONS ! THEY ARE THERE TO BE FOLLOWED UNLESS AND UNTIL YOU ARE SO RICH THAT YOU CAN WASTE 600$ OR YOU ARE A SUPER CHEF AT XDA AND ARE SURE OF WHAT YOU ARE DOING !
Anyways Best of luck hope you can unbrick it !
otherwise smash it
Bye.
LoL yeah a $600 paper weight may also come in handy..?? Or like previously stated, take your anger out on it for not doing it right the first time lol...
I now this might be a little too late to answer,but i want to give my two cents to this brick posts. Maybe someone will need it. This is for anyone that might be where I was for over 2 weeks. I though my Fuze/ Raphael / touch pro was history. My phone will get into restart loops when ever he wanted. It was very anoying. After replacing every possible software from Radio, Hard Spl, different rooms and even start up splashes, and almost getting "ORD" in the process. I finally took my phone apart, since there was no warranty. Once open I saw that the reset bottom inside was too close to the rubber reset bottom from outside. Guess what ?? That as all it was..... Good luck to all. : )
Soft Break :
I wanted to experience myself a few times when handling or replacing flash ROM to your good friends Mvbaylstany Aftadrv occurred to me that I let it hit you , maybe you can help the better
You know the Galaxy series Samsung yen Skvndry called a backup boot boot the phone I put it that if I install the update ROM or flash or blink
Problems such as power outages or power fluctuations Kampyvtrfrymvr Detachable USB cable or wrong, or ... Did you get your phone before Btvnyd easily restore the so-called semi-break or break your soft individuated it easy to tell if it was on the phone with your high Mvajh:
I still have boot Skvndry break and a good stock kernel with the previous ROM version can download your phone and the PDA Odin villages
Start up and you see all my phone now Jyha than "a few Faya-ROM with your phone, your phone, you must download the bit file" set partition Ray Vtyk I stir and stir all flash phone: the phone was right.
Are you drunk?
Greetz, Unr3aL67
Sent from my Defy via Tapatalk
might be a retarded robot.
is he using his elbow to type? joke
Maybe just a bad Google-Translation.
But seriously, there are hundreds of threads like that, where nobody's able to tell what the OP wants. I'm not willing to read any more of this bulls**t, because there are more important things to do.
Even though I haven't got my 10 Posts full yet, I am very active at the German Android-Hilfe.de-Board and most of the people there know that they have to address their problems properly and they also sometimes use the search engine.
Reading through the threads of XDA sometimes gives me a headache after 10 minutes, even though im not a native speaker and have in fact no right to be a grammar nazi...
From what I can tell, the OP wants to tell us something about his yellow triangle- problem. At least the picture he posted tells me.
I'm not gonna answer that, use the goddamn search engine mahdidanesh91...
There are hundreds of threads about that...
Sorry for my hard words, but everyone here thinks the way I do, even if they don't tell...
By the way, take a look at this, maybe it solves your problem: http://www.youtube.com/watch?v=JmvCpR45LKA
Greetz, Unr3aL67
info
hello every body,
do any one know,whats meaning of this pic ? (attached file)