BRICKED! sbf made it worse! Please Help!
OK so I am pretty much pissed at whoever created Tranquility....
backed up using Titanium Backup...
followed Tranquility directions (install the .zip in clockwork)...
[this led to a boot loop of Tranquility]
tried to install update.zip...fail...
tried many mnay other things i read online...
[this is where i think things got messed up]
i went stupid and thought holding the up button while booting made it boot into bootloader. it doesnt, what it does do is freeze at the M and allows RSD Lite to access the device. So i thought it was working and tried to flash - it tried a few things and failed....
tried a few more things...even loading a backup of my old DX that the problematic one was supposed to be replacing....
then performed a proper flash via RSD Lite and things seemed to be going well...until the DX rebooted, now it reads
I have tried to flash it about 4-5 times and get this everytime. Am I screwed? Is it toast? Is there a way I can get Verizon to replace the phone?
Please any help is appreciated.
- 10-06-2010, 07:47 AM #2
reboot with the backup in your Koush recovery folder.
Had similar experience with mine.
SBF may have not been a great idea in your situation ???
You may be going to VZW . Hope i'm wrong try to boot into recovery with the Bootstrap program you have use the saved backup to bring you back.
- 10-06-2010, 08:53 AM #3
I hope for everyone elses sake that VZW tries to flash your phone, and not give you a new one unless you pay for it.
Mod'ing comes with certain risks. I dont want to pay higher rates because lower level wannabees brick their phones and then con VZW into a new phone (not addressing you as a wannabee, just saying for all others, you might have a great tech background. but I dont know you, so this isnt personal, just business)
- 10-06-2010, 11:27 AM #4
maybe then moto will learn the benefit of not locking our phones to hell. and at the very least giving us the proper tools to recover them on our own if we do mess it up.
- 10-06-2010, 12:19 PM #5
- 10-06-2010, 12:29 PM #6
- 10-06-2010, 12:31 PM #7
- 10-06-2010, 03:34 PM #9
- 10-06-2010, 03:39 PM #10
I have heard of people taking it in to Verizon and playing dumb and saying that the 2.2 OTA update caused it. Not saying that will work but I have heard success stories.
- 10-06-2010, 03:49 PM #12
So again, I'd recommend playing completely dumb or waiting it out for the full .sbf if/when that gets leaked.
Phew! That was easier than I thought. Told them I did the 2.2 update and it froze at the m then " I held some buttons together while booting and it got really messed up". Now I am getting a new phone and not doing anything to it until I know exactly what I am doing lol.
- 10-06-2010, 06:04 PM #14
- 10-07-2010, 04:26 AM #15
Well I probably have the record for bricking a X, I had the phone 3 days and messed up with the 2.1 file and bricked it. Played stupid at the local Verizon store and got another new phone no charge. So now I am very very careful with what I do.
I dont see enough of a difference in some of the Roms to even bother with them. I have tried a couple of the themes on the new phone with no issue. I did do the one click Root thing and everything is working just fine now. So until someone cracks the 2.2 brick routine I wont be doing much to my phone.Craig
BB Convert and Not Looking Back !