Database Users

I'm Screwed!

I have to return my Vibrant to T-Mo and need to unroot. But I don't think I'm really rooted in the first place. I downloaded the RyanZas lagfix app. I clicked on root phone. I went into recovery and reinstalled packages. My phone says it's rooted, but there is no update.zip file anywhere. I can't even find a "download" file in Astro. I have the Superuser icon in my apps, but can't delete that either. I just want to get this phone to where I can send it back to T-Mo without voiding my warranty. Also in the lagfix app, it says I am rooted. I don't even have the option to root, only to unroot. When I try that, it just reboots my phone, but never "unroots".
Another thing...when I look at my free space, I have 1754 mb out of 1917 mb available. If I was rooted, would I have less space available?
I'm sure it's VERY obvious that I'm a newbie to all this, so if you have any ideas for me, please talk to me like I'm a 1st grader ;-)

Well if you unroot.. the superuser icon will disappear

hospo said:
I have to return my Vibrant to T-Mo and need to unroot. But I don't think I'm really rooted in the first place. I downloaded the RyanZas lagfix app. I clicked on root phone. I went into recovery and reinstalled packages. My phone says it's rooted, but there is no update.zip file anywhere. I can't even find a "download" file in Astro. I have the Superuser icon in my apps, but can't delete that either. I just want to get this phone to where I can send it back to T-Mo without voiding my warranty. Also in the lagfix app, it says I am rooted. I don't even have the option to root, only to unroot. When I try that, it just reboots my phone, but never "unroots".
Another thing...when I look at my free space, I have 1754 mb out of 1917 mb available. If I was rooted, would I have less space available?
I'm sure it's VERY obvious that I'm a newbie to all this, so if you have any ideas for me, please talk to me like I'm a 1st grader ;-)
Click to expand...
Click to collapse
if it bothers you that much why dont you use odin and go back to stock jfd?
http://forum.xda-developers.com/showthread.php?t=734475
Seems a bit extreme but that will do it for you, its easy also

Well, like I said, I'm totally new to this and that thread is like trying to read Chinese for me. It doesn't bother me to be rooted. I just need to unroot because I have to send it in to T-Mo for my warranty replacement.
I never flashed any ROMs. I only rooted and applied the lag fix. But now the update.zip file is gone and my phone still says it's rooted.
When I go into the terminal on the phone and try to remove Superuser.apk it tells me it can't because it's a read-only file.
Again, I don't mind that these things are there, I just don't want to have to pay for my phone...again.

hospo said:
Well, like I said, I'm totally new to this and that thread is like trying to read Chinese for me. It doesn't bother me to be rooted. I just need to unroot because I have to send it in to T-Mo for my warranty replacement.
I never flashed any ROMs. I only rooted and applied the lag fix. But now the update.zip file is gone and my phone still says it's rooted.
When I go into the terminal on the phone and try to remove Superuser.apk it tells me it can't because it's a read-only file.
Again, I don't mind that these things are there, I just don't want to have to pay for my phone...again.
Click to expand...
Click to collapse
I sent in a phone with bionix final on it rooted and they didn't charge me for it I was having problems with other people not being able to hear me but once I sent it in and got my new one I was not charged any additional fees I'm not even sure they really check the phone they probably just reprogram everything back to stock hell they might not even be looking at the screen you never know, but this is my third vibrant and ive had something on all of the ones I've sent back never heard anything about it you could always try to claim it was refurbished and there was something wrong with it already best of luck anyway
Times never wasted when your getting waisted

seriously, using odin is really very simple, i used odin 1.7 ( no it dont have a virus before anyone says it) only a couple of nights ago after flashing one of eugenes kernels, long story short i was stuck at the boot animation, hadnt backed up like a noob and was stuck, i followed that thread and the hardest part for me was download mode on the phone and thats really simple, seriously if you need it back to total stock have a go at odin

I'd love to have a go at odin, except seriously, when I say I have no idea what I'm doing...I REALLY mean it! Someone has given me all the steps to use odin, but quite frankly, I still don't know where to start. Do I download part on my computer, then move it onto the phone? Where do I put it on the phone? How do I get in download mode? See...NO CLUE. I really shouldn't have ever rooted for the mere fact that I have no idea what I'm doing, lol.
I think I may just go back to factory reset (again) and roll the dice hoping they don't charge me.

hospo said:
Well, like I said, I'm totally new to this and that thread is like trying to read Chinese for me. It doesn't bother me to be rooted. I just need to unroot because I have to send it in to T-Mo for my warranty replacement.
I never flashed any ROMs. I only rooted and applied the lag fix. But now the update.zip file is gone and my phone still says it's rooted.
When I go into the terminal on the phone and try to remove Superuser.apk it tells me it can't because it's a read-only file.
Again, I don't mind that these things are there, I just don't want to have to pay for my phone...again.
Click to expand...
Click to collapse
Can't you root it again and then unroot it...
The thread that has the Odin instructions is only 6 steps...well 5 steps since the last says "wait for it to complete". It's not as daunting as it seems...
I'd love to have a go at odin, except seriously, when I say I have no idea what I'm doing...I REALLY mean it! Someone has given me all the steps to use odin, but quite frankly, I still don't know where to start. Do I download part on my computer, then move it onto the phone? Where do I put it on the phone? How do I get in download mode? See...NO CLUE. I really shouldn't have ever rooted for the mere fact that I have no idea what I'm doing, lol.
I think I may just go back to factory reset (again) and roll the dice hoping they don't charge me.
Click to expand...
Click to collapse
You download Odin to your computer with the .pit & the .tar file then run it from there. There's a video tutorial in the Vibrant Bible sticky in the Dev forum.
~SB

You don't understand because you aren't TRYING to understand. Odin is as simple as a few mouse clicks. Seriously.
Sent from my SGH-T959 using XDA App

video how to odin...
http://forum.xda-developers.com/showthread.php?t=810130
video how to download mode
http://www.youtube.com/watch?v=rqxearzXrVY

okay, I sucked it up, got over my fear, got everything downloaded. Phone was in download mode, then went black. Now all I can get on it is a picture of a cell phone, then an exclamation point, then a pic of a computer.
I really am trying to understand. I did get the files needed and the phone in download mode. Opened odin, put the files in while my phone was in download mode and plugged in. Then the above happened.

OMG!!!!!! I think it is finally working!!!! Thank you for your help!!!
Even after all this, I'm sure I won't stop tinkering, lol.
Who knows, maybe I won't have to trade in my phone after doing this? I was really worried about getting the refurb. I'm supposed to get it today, but I'm going to mess around with mine to see if it truly is back to its old beautiful self!
Thanks again everyone!!

That is SUPPOSED to happen. Now click "Start."
Edit: I see you got it now. Congrats.

hospo said:
OMG!!!!!! I think it is finally working!!!! Thank you for your help!!!
Even after all this, I'm sure I won't stop tinkering, lol.
Who knows, maybe I won't have to trade in my phone after doing this? I was really worried about getting the refurb. I'm supposed to get it today, but I'm going to mess around with mine to see if it truly is back to its old beautiful self!
Thanks again everyone!!
Click to expand...
Click to collapse
it worried me using odin at first, but when you actually use it, its really very simple, now im hooked on flashing roms lol and using odin to go back when i stuff something up lol

kangxi said:
You don't understand because you aren't TRYING to understand. Odin is as simple as a few mouse clicks. Seriously.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
yeah exactly, i was a totally new to odin and thought it was some hard thing to use, it was so simple, i couldnt believe it, get your pantys out of a wad and actually look it up

Successfully bricked my Vibrant

So I just wanted to share with you guys that I successfully bricked my Vibrant. Getting a new one on Thursday or Friday. You know what they say. That you learn the best way when you failed in something. So I have learned today what not to do to keep the phone up and running.
UPDATE:
Followed instructions kizer at http://forum.xda-developers.com/showthread.php?t=741027&highlight=bricked+download+mode&page=5 and it took me to download mode.

How did you brick it?

Segnaro said:
How did you brick it?
Click to expand...
Click to collapse
I was putting Eugene's leaked froyo on my vibrant. Been having problems with the SD card so I decided I was going to reflash it again. So I clicked on the re-partition in Odin as I tried doing it without repartitioning. For some reason it stopped in the middle of the process, I got impatient (waited only like 5 minutes) and decided to restart it. Was having problems with the computer at the time as well. To many things running.
I think that the controller for the keys got wiped as nothing responded afterward this happened. It would not even recognized being connected to the computer.

how did you explain it to t-mobile?

iynfynity said:
how did you explain it to t-mobile?
Click to expand...
Click to collapse
Just told them that their JI6 update crashed it with an incomplete installation. I know they guy that put in the warranty exchange for me. And as he hadn't got the update to his phone yet he figured that it makes sense. Heard about the update doing weird stuff.
I just figured they would take the phone and reflash it when they get it.

swehes said:
I was putting Eugene's leaked froyo on my vibrant. Been having problems with the SD card so I decided I was going to reflash it again. So I clicked on the re-partition in Odin as I tried doing it without repartitioning. For some reason it stopped in the middle of the process, I got impatient (waited only like 5 minutes) and decided to restart it. Was having problems with the computer at the time as well. To many things running.
I think that the controller for the keys got wiped as nothing responded afterward this happened. It would not even recognized being connected to the computer.
Click to expand...
Click to collapse
so another person messes up their phone and fraud's the warranty, great post.
Next are you SURE it's bricked? I've had many failed ODIN's and I've never ever bricked one.

rsfaze said:
so another person messes up their phone and fraud's the warranty, great post.
Next are you SURE it's bricked? I've had many failed ODIN's and I've never ever bricked one.
Click to expand...
Click to collapse
Hmmmm. Found one last post of how to get into download mode, and it took it in. Greatly surprised and happy as I am quite fond of this phone. Odin new Froyo to it. Quite remarkable.
MOD. Can you please remove this thread as I managed to undo my mistake?

swehes said:
Hmmmm. Found one last post of how to get into download mode, and it took it in. Greatly surprised and happy as I am quite fond of this phone. Odin new Froyo to it. Quite remarkable.
MOD. Can you please remove this thread as I managed to undo my mistake?
Click to expand...
Click to collapse
You didn't manage to undo your mistake.. You managed to fraud t-mobile on YOUR mistake.
Glad you "Fixed" your phone.

Lol so who doesn't have insurance?
Sent from my SGH-T959 using XDA App

The insurance doesn't cover bricking your phone by way of flashing unofficial firmwares anyways does it? So what's the point?
Sent from my SGH-T959

catchy subject header, and what a turn around like mine. I now know for sure the Vibrant is 100% bullet proof figuratively lol.

[Q] CWM Recovery Errors

I understand that there are similar threads out there but I still can't seem to figure it out. I apologize ahead of time for any wrong terminology, I'm pretty new to all of this. To give a background on what happend, I started my day off by rooting my phone with the following link (I had tried a different method with visionary plus and terminal but it wouldn't work)
http://forum.xda-developers.com/showthread.php?t=858996
this method worked just fine and gave me s=off, currently what I have is as followed:
Glacier PVT ENG S-OFF
HBOOT-0.85.2007 (pd1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
After gaining my root I was excited to try and flash a new rom. I installed the clockwork rom manager from the market, flashed the recovery then backed up my current in case of future problems.
Next step for me was to flash a new rom. for this I followed
http://forum.xda-developers.com/showthread.php?t=1070444
everything seemed to be going fine, phone restarted and I sat waiting (since I read the first boot could take 10min or so) after at least an hour I began to worry. Nothing happened, just stayed on the mytouch 4g startup screen and never changed.
I rebooted into recovery to try again, I can get into my hboot and into clockwork Mod Recovery v3.0.2.4 just fine. but there are a whole bunch of errors I cant fix. When clockwork starts I get the errors
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
If I try to format anything (cache, system...) it will say
Formatting /cache... (or system depending on what I am trying)
Error formatting /cache! (or system)
If I try to restore to a previous time it will start to do the restore, it will first do the boot which goes fine, but when it tries to format the system during the restore it fails just like if trying to format it individually.
At this point I would just like to get my phone working, any help would be much appreciated. (please try and use details so I can follow... still trying to learn alot)

I hate to be the bring of bad news, and remember don't kill the messenger, but it sounds as if your phone is truly bricked. There have been several threads on this already. As i know you are aware of. And very few, if any, have recovered.
There is a thread Posted here that boils down to the fact if the VISIONary.apk & root.sh method do not work then you have a bad eMMC.
Since it appears your phone does have a bad eMMC, hope you have insurance on it.

neidlinger said:
hope you have insurance on it.
Click to expand...
Click to collapse
neidlinger- i happen to have bought the insurance for 6 bucks a month or whatever it was - they said it extends the mfr warranty another year and then it gives you drop-in-toilet etc insurance with around a 120$ deduc.
I'm with t-mobile and got the phone thru the mail. If I take this back to a local TMO store for warranty claim, there's no difference is there? (i.e. you dont have to follow the mail route just because that's how you got it originally)
also- would these cache mount or failed -pu errors, essentially beyond repair - are we getting these to be recognized as hardware failure (i.e. no deductabel and counted as a mfr defect) or are these coming up as TMO insisting on counting them as some user fault, requiring the deductable to be paid??

acsi007 said:
neidlinger- i happen to have bought the insurance for 6 bucks a month or whatever it was - they said it extends the mfr warranty another year and then it gives you drop-in-toilet etc insurance with around a 120$ deduc.
I'm with t-mobile and got the phone thru the mail. If I take this back to a local TMO store for warranty claim, there's no difference is there? (i.e. you dont have to follow the mail route just because that's how you got it originally)
Click to expand...
Click to collapse
9/10 times if you buy a phone through the mail you will have to exchange it through the mail they will not allow you to walk into a store and do the exchange. I ran into that with my blackberry 9700.
acsi007 said:
also- would these cache mount or failed -pu errors, essentially beyond repair - are we getting these to be recognized as hardware failure (i.e. no deductabel and counted as a mfr defect) or are these coming up as TMO insisting on counting them as some user fault, requiring the deductable to be paid??
Click to expand...
Click to collapse
nope there is not way around it. once the eMMC fails it's down for the count.

neidlinger said:
I hate to be the bring of bad news, and remember don't kill the messenger, but it sounds as if your phone is truly bricked. There have been several threads on this already. As i know you are aware of. And very few, if any, have recovered.
There is a thread Posted here that boils down to the fact if the VISIONary.apk & root.sh method do not work then you have a bad eMMC.
Since it appears your phone does have a bad eMMC, hope you have insurance on it.
Click to expand...
Click to collapse
Is there any way to tell if the eMMC is bad. the visionary install went fine, just using the terminal to do the sh root.sh command wouldnt work, it would just keep saying failed (function not implemented) which is why I switched to visionary and adb gfree method... which worked like a charm, not a single hickup with it. the problems didnt start coming until after the rom instillation didnt work

hiddentalnt said:
Is there any way to tell if the eMMC is bad. the visionary install went fine, just using the terminal to do the sh root.sh command wouldnt work, it would just keep saying failed (function not implemented) which is why I switched to visionary and adb gfree method... which worked like a charm, not a single hickup with it. the problems didnt start coming until after the rom instillation didnt work
Click to expand...
Click to collapse
i see you didn't read the thread i posted.
The link i posted is to a thread here @ XDA, called "Post your eMMC serial number". It has alot of information regarding this very subject, including how to tell if your eMMC is indeed a faulty one [ by serial number ].
it really doesn't matter when the problem happens. it just matters that it happened.
./gfree is basically forcing the rooting process to happen while the root.sh is asking for it to happen. If the root.sh process doesn't allow you to proceed, then you may have a faulty eMMC. you forced the phone to root and opened up a bee hive in the process.

yeah sorry, I posted and then was just reading that forum as you replied... sorry about that.

hiddentalnt said:
yeah sorry, I posted and then was just reading that forum as you replied... sorry about that.
Click to expand...
Click to collapse
no need to tell me your sorry, . If you want to make me mad tell me Popeye's Chicken is out of business. we all start out somewhere. Just be willing to read prior to doing anything or asking anything. Chances are there is an answer somewhere. Sometimes we like what we read and sometimes we don't either way it's out there.

Hiddentalnt, please post your eMMC serial. We need people who have recovery errors to post what serial they have so we can actually pinpoint the problem being the chip. Thanks. The instructions are posted in the thread neidlinger posted above. Thanks

xdviper said:
Hiddentalnt, please post your eMMC serial. We need people who have recovery errors to post what serial they have so we can actually pinpoint the problem being the chip. Thanks. The instructions are posted in the thread neidlinger posted above. Thanks
Click to expand...
Click to collapse
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know

hiddentalnt said:
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
Click to expand...
Click to collapse
after you got ADB installed and you punch in adb devices does it give you a serial number?

hiddentalnt said:
I just tried to run that command but nothing comes up after it. I dont know if im inputing it in wrong but im currently trying to figure it out... Ill post once I find it. if any advice on why after running the command it just repeats the line, then nothing let me know
Click to expand...
Click to collapse
nevermind... just got it M4G2DE
so from what Im reading...theres no coming back from this, the chip is dead?

hiddentalnt said:
nevermind... just got it M4G2DE
so from what Im reading...theres no coming back from this, the chip is dead?
Click to expand...
Click to collapse
pretty much.
I do know one guy was able to via flashing an older recovery image via the hBoot, but you have to have the .85 engineering screen. Which you do not have.

neidlinger said:
pretty much.
I do know one guy was able to via flashing an older recovery image via the hBoot, but you have to have the .85 engineering screen. Which you do not have.
Click to expand...
Click to collapse
what is the .85 engineering screen, i do have hboot - 0.85.2007 but im assuing thats different.
So its time to call up TMO and have them send me out a new phone? do I need to unroot first so they dont find it?

hiddentalnt said:
what is the .85 engineering screen, i do have hboot - 0.85.2007 but im assuing thats different.
So its time to call up TMO and have them send me out a new phone? do I need to unroot first so they dont find it?
Click to expand...
Click to collapse
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.

neidlinger said:
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
Click to expand...
Click to collapse
sorry for asking so many questions. but you really have been a great help. do you have any idea where i can find the 2.5.x.x recovery image, I've been trying to look but I cant find it, just didn't know if you already knew of a forum that had it.

hiddentalnt said:
sorry for asking so many questions. but you really have been a great help. do you have any idea where i can find the 2.5.x.x recovery image, I've been trying to look but I cant find it, just didn't know if you already knew of a forum that had it.
Click to expand...
Click to collapse
I've got it store on my Lunix computer at home. I do not have it on my phone or on my work computer.
sorry. I can post it later on tonight.

neidlinger said:
I've got it store on my Lunix computer at home. I do not have it on my phone or on my work computer.
sorry. I can post it later on tonight.
Click to expand...
Click to collapse
Thanks, I appreciate it. I'm off to class anyways so I have to put a pause on trying to fix it till then.

neidlinger said:
Well you need to flash the 2.5.x.x recovery image for the mytouch4g from the hBoot, then reboot then navigate to the recovery and pray that it works. If it loads you might be able to load a new ROM but i only know of one case where that worked.
Click to expand...
Click to collapse
I would be that ONE case where this option did work. And the difference I have seen between the first time when flashing CWM worked and the second time (when it DIDN'T work) is the COMMAND error. If your CWM says anything about COMMAND error then flashing the old CWM isn't gonna work.
Here is a link to a post I made with a download for the old CWM
http://forum.xda-developers.com/showthread.php?p=14069400#post14069400
have any questions PM me if needed. Hit the Thanks button to if any of us have helped you at all.
Good luck man, I have a 450 dollar batter charger right now, so you'll need it :/

dcwiker05 said:
I would be that ONE case where this option did work. And the difference I have seen between the first time when flashing CWM worked and the second time (when it DIDN'T work) is the COMMAND error. If your CWM says anything about COMMAND error then flashing the old CWM isn't gonna work.
Here is a link to a post I made with a download for the old CWM
http://forum.xda-developers.com/showthread.php?p=14069400#post14069400
have any questions PM me if needed. Hit the Thanks button to if any of us have helped you at all.
Good luck man, I have a 450 dollar batter charger right now, so you'll need it :/
Click to expand...
Click to collapse
I'm not sure I fully understand your directions in the other thread. So when i download the zip, i get inside it and go all the way to recoveries to get out one of the disc image files. which one do I want, there is a 2.5.1.3 and 2.5.1.4 and a 3.0.0.5 but I'm assuming thats not it... but once I get one of those I rename it recovery.img then i use abd to push it... what is the command to push it? and i have to be in hboot then fastboot to push it?

Might buy boot-looping Xoom, questions

Hello,
So I bought my Xoom over the weekend when I never heard back from a Craigslister about a Xoom they have that is bootlooping.
Finally got back to me today and I am looking to fix it, and make a little profit.
Guy explained he knows it can get into Fastboot and mentioned RSD lite so I know he has done some research but ultimately he said he is not good at computers and cannot fix it.
My question is what do I need to consider? If I can access hboot ( from power off wait til see M and hit Vol - right?) I should be good to go is my understanding. Is there any way to run a diagnostic and see if there is hardware issues going on?
What would you do I guess lol
He said I could tinker with it first. I am familiar with ADB and rooting / custom roms on Android but have only had my Xoom for about 3 days.
Thanks

If you can definitely get into fastboot, you can recover it; simple as that. Whether there are hardware issues is another matter.

MoreGone said:
Hello,
So I bought my Xoom over the weekend when I never heard back from a Craigslister about a Xoom they have that is bootlooping.
Finally got back to me today and I am looking to fix it, and make a little profit.
Guy explained he knows it can get into Fastboot and mentioned RSD lite so I know he has done some research but ultimately he said he is not good at computers and cannot fix it.
My question is what do I need to consider? If I can access hboot ( from power off wait til see M and hit Vol - right?) I should be good to go is my understanding. Is there any way to run a diagnostic and see if there is hardware issues going on?
What would you do I guess lol
He said I could tinker with it first. I am familiar with ADB and rooting / custom roms on Android but have only had my Xoom for about 3 days.
Thanks
Click to expand...
Click to collapse
The question is, how much are you willing to pay if you can't fix it, then if you can you will be happy, if not you should stay happy.
Bootloop can be software but they can easily be hardware too so better be safe than sorry

take a laptop with you and do "fastboot devices' on the spot.
If the computer can see it then it can be wiped clean and fixed

It's $300 and it wouldn't kill me, obviously wouldn't be ideal but not the end of the world either.

ydaraishy said:
If you can definitely get into fastboot, you can recover it; simple as that. Whether there are hardware issues is another matter.
Click to expand...
Click to collapse
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.

P00r said:
The question is, how much are you willing to pay if you can't fix it, then if you can you will be happy, if not you should stay happy.
Bootloop can be software but they can easily be hardware too so better be safe than sorry
Click to expand...
Click to collapse
At what point would I be able to run that command? When powering up, at the M etc?

Zargon335 said:
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.
Click to expand...
Click to collapse
Stock images?

Zargon335 said:
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.
Click to expand...
Click to collapse
That's certainly a concern

ydaraishy said:
Stock images?
Click to expand...
Click to collapse
Yes.
10chars

@OP
If seller knows about Fastboot & RSD Lite, he's probably on this forum. Might even be in this thread.
HEY SELLER just let me figure this out and I'll buy it right off ya, OK?

If you CAN get out of it that certainly a very good price. Most cases I think I have seen have been recoverable. Maybe ask the seller how he got into this situation in the first place, might give you a better understanding of how to fix it.

HELP! Failed to boot! Can't start RSD or Fastboot support

I am currently unable to boot into anything, no RSD, no Fastboot nothing. I try holding down up volume and down volume. Here's what it says when i try to power up.
SVF 105:1:2
Failed to boot 0x1000
Here's what i did.
I followed the steps exactly to install the stock 2.3.4 ATT update. Everything was fine. Then i decided to start over and install kennethpenn's custom rom. So i tried to flash the 1.8.3 sbf.
i foolishly started surfing other websites and didn't pay any attention to my phone. then when i looked back it was completely black screen and RSD lite said:
Failed flashing process. Failed flashing process. Phone {0000}: Error switching phone to BP Pass through mode (0x70BE); phone disconnected
Thats it. now i can't do anything. Please help.

It's called "bricked". Now search for that term and you'll find answers!

Yeah, I think you're screwed their man... Kennethpenn had the same issue with his Atrix I think.... $600 brick

doesnt sound good...
where in the process exactly did you decide to start over and install kenneths custom rom?

i know its bricked. i'm just wondering how bricked...
i was in the process of starting over to install kennethpenn's ROM. i was flashing the full 1.8.3 sbf.
do you think ATT will take it back under warranty if i play dumb?

b3nman said:
i know its bricked. i'm just wondering how bricked...
i was in the process of starting over to install kennethpenn's ROM. i was flashing the full 1.8.3 sbf.
do you think ATT will take it back under warranty if i play dumb?
Click to expand...
Click to collapse
Well you got nothing to lose.

i
i have the same problem gonna play dumb and get a new one today under warranty

yokozuna82 said:
i have the same problem gonna play dumb and get a new one today under warranty
Click to expand...
Click to collapse
Nice. Tell us how it works out, good luck!

yokozuna82 said:
i have the same problem gonna play dumb and get a new one today under warranty
Click to expand...
Click to collapse
What did you do to cause it? Same thing as OP?

I'm tellin ya I think there is something wrong with that damn 1.83 sbf itself! The older ones never had any problems! I'm done with it!

LayzeeEyez said:
What did you do to cause it? Same thing as OP?
Click to expand...
Click to collapse
yeah, has anyone else tried to flash back to 1.83?

b3nman said:
i know its bricked. i'm just wondering how bricked...
Click to expand...
Click to collapse
If it does not go to the moto logo screen that means something messed up your IPL/Bootloader, which means you are pretty screwed.
b3nman said:
i was in the process of starting over to install kennethpenn's ROM. i was flashing the full 1.8.3 sbf.
do you think ATT will take it back under warranty if i play dumb?
Click to expand...
Click to collapse
You could just say that you never got around to updating to 1.8.3 (kind of a long shot since it reminds you every hour), and when you installed the update it would not restart. If you have a backup phone, you could just wait till the new update releases and use the same excuse.
If you hard bricked, there is most likely no way they can check if you were messing around with anything. It is worth a shot, but like you said just play dumb

http://forum.xda-developers.com/showthread.php?t=1160408 <- For future reference

im sorry this happend to you guys, i hope everything goes well with insurance and what not. i made a warning on the guide for people not to flash back until a safe method is found!

i had ur problem a few seconds ago!
rsd stoped at " switching phone to BP Pass through mode " at 33%.
and after a hour nothing happend!
i decided to disconnect the phone but after that i lost RSD,fastboot,.....
i removed the battery for a while and after that i powerd the phone up but it was the same as before.
i left it on moto red logo and after a few second it said:
failed to boot 4
starting RSD mode
and now its working!
but i didnt get " Failed flashing process " like you!

i got one coming through warranty be here no later then tuesday

i guess i didn't understand the warnings. now i see them, only too late. it seems like att will send me a new one.

b3nman said:
i guess i didn't understand the warnings. now i see them, only too late. it seems like att will send me a new one.
Click to expand...
Click to collapse
anyone have a cwm backup pre 2.3.4 they can try?

att is sending a new one. it was easy since i'm still within the 30 days of opening my account. lesson learned:
THOROUGHLY READ ALL WARNINGS!!! I hope my fail can prevent others from going through it. THANKS EVERYONE!

is this 4.5.91 specific? I flashed between 4.5.40 and 1.83 sbf a few times without problem.