To my understanding (which isn't much) is there no way to fix a bricked phone? yes i mean bricked. no power, notta...
dyefalcon1 said:
To my understanding (which isn't much) is there no way to fix a bricked phone? yes i mean bricked. no power, notta...
Click to expand...
Click to collapse
no power = bricked
give us details on what happened
and btw questions like these go in general and is not dev related
Do you know for sure that it is bricked? I assume youve done a battery-pull?
What event preceded the bricking?
EDIT: DS36 beat me to it
i was gonna try the new updated radio just posted so i powered off to do a nand backup and there was just an android on the screen. pulled battery out now the phones dead. i flashed droid does 1.1 last night...
leave the battery out for 10-15 minutes and try again.
ban_dover said:
leave the battery out for 10-15 minutes and try again.
Click to expand...
Click to collapse
+1
and maybe pop-out the SD card, boot without it or at least make sure its seated properly.
Have you tried to boot into recovery (VOL-UP + power)? I know this wont work if its truly bricked, but just try everything.
Oh and if you do get it to boot, perhaps wait on flashing that new radio -- admonishments in other threads re:flashing the radio discuss the real (albeit small) risk of bricking after a bad radio flash.
I want to give that new radio a try to, but I will probably give a bit more time.
dyefalcon1 said:
i was gonna try the new updated radio just posted so i powered off to do a nand backup and there was just an android on the screen. Pulled battery out now the phones dead. I flashed droid does 1.1 last night...
Click to expand...
Click to collapse
aaahhhhhh !
You pulled the battery while flash the radio ???????
Fyi never ever pull a batter while flashing anything son
droidJW said:
+1
and maybe pop-out the SD card, boot without it or at least make sure its seated properly.
Have you tried to boot into recovery (VOL-UP + power)? I know this wont work if its truly bricked, but just try everything.
Oh and if you do get it to boot, perhaps wait on flashing that new radio -- admonishments in other threads re:flashing the radio discuss the real (albeit small) risk of bricking after a bad radio flash.
I want to give that new radio a try to, but I will probably give a bit more time.
Click to expand...
Click to collapse
I HAVE THE NEW RADIO TOO
ITS WORKS JUST FINE
dont be scared
DS36 said:
I HAVE THE NEW RADIO TOO
ITS WORKS JUST FINE
dont be scared
Click to expand...
Click to collapse
HA ! I need that pep talk.
I downloaded the radio earlier and was about to flash when I saw this thread ( I know the radio isnt the issue here, but made me second-guess).
I am the guy that routinely flashes BIOS updates on my PCs, in spite of the "dont fix it if aint broke" warnings on BIOS updates. I have done 100+ BIOS flashes on various PCs -- never had an issue. Funny, my PCs are all worth more than my Eris...and yet, I hesitate on flashing this radio. I'll get to it !
droidJW said:
HA ! I need that pep talk.
I downloaded the radio earlier and was about to flash when I saw this thread ( I know the radio isnt the issue here, but made me second-guess).
I am the guy that routinely flashes BIOS updates on my PCs, in spite of the "dont fix it if aint broke" warnings on BIOS updates. I have done 100+ BIOS flashes on various PCs -- never had an issue. Funny, my PCs are all worth more than my Eris...and yet, I hesitate on flashing this radio. I'll get to it !
Click to expand...
Click to collapse
Thats the spirit
and befefit from a faster wifi
ha thats how I bricked my phone got the little android guy on my phone and pulled the battery. To get off that screen so just for future ref. if that happens when flashing a radio what should I do? Wasnt too big of a deal since under warranty but just curious if I should have just waited before pulling the battery and all would have been fine?
Yeah when the little android guy comes up wait cuz after a bit it will reboot and go jnto recovery then just reboot again then u good
Sent from my Eris using XDA App
I guess I should have waited instead I freaked out instantly all is good though new eris re-rooted no problems I will have more patience next time flashing a radio though.
edgeupgx said:
I guess I should have waited instead I freaked out instantly all is good though new eris re-rooted no problems I will have more patience next time flashing a radio though.
Click to expand...
Click to collapse
Yep just be pantient, everything with flashing be patient lol good to hear ur back up and going
Sent from my Eris using XDA App
yeah idk whats going on but its still under warranty so ill just send it in for a new one
Related
Hi, I know I F** up so Im sending my G1 to tmo today but I just want to share my problem with yall so that I wont F** up in the future.
I am super dumb so spare the shotouts please..
I have a G1 that does the following:
Power button = stays booting with Tmo image for ever....
Camera+power = Flashscreen but when I try to flash image it shows not allow...with red numbers 0007002 I think..
Home + Power = 3 options --> 1. Reboot (works) 2. Update (won`t work it says cache/recovery/command not found) 5,215,715 etc files not known. 3. Wipe (works as far as I know).
Also combination Home + back button = back to fabric installation works says press send to go further. But when it restarts does nothing my phone stays loading the tmo image till battery is empty.
The story: I tried to update a zip for hero from youtube and after that nothing worked anymore.
(I did not follow all the steps- bcuz I am stupid!)
What kind of mule am I??????? A big one!
What have I done wrong and is there any point in sending the device to tmo or should I trow it in the trashcan?
Peace and thanks for the laughs
dizzydix said:
Hi, I know I F** up so Im sending my G1 to tmo today but I just want to share my problem with yall so that I wont F** up in the future.
I am super dumb so spare the shotouts please..
I have a G1 that does the following:
Power button = stays booting with Tmo image for ever....
Camera+power = Flashscreen but when I try to flash image it shows not allow...with red numbers 0007002 I think..
Home + Power = 3 options --> 1. Reboot (works) 2. Update (won`t work it says cache/recovery/command not found) 5,215,715 etc files not known. 3. Wipe (works as far as I know).
Also combination Home + back button = back to fabric installation does nothing my phone stays loading the tmo image till battery is empty.
The story: I tried to update a zip for hero from youtube and after that nothing worked anymore.
(I did not follow all the steps- bcuz I am stupid!)
What kind of mule am I??????? A big one!
What have I done wrong and is there any point in sending the device to tmo or should I trow it in the trashcan?
Peace and thanks for the laughs
Click to expand...
Click to collapse
What was the update you were trying to flash and what were the steps you took prior to that?
Hi Supremeteam
I took all the files from youtube link
http://www.youtube.com/watch?v=_dxB_qvM2KU&feature=related
VIDEO NAME: Hero Rom on G1---Jachero 2.3.6-----There is a difference between Theme and Rom.
I DID NOT FOLLOW ALL STEPS!
I think it went dead after I updated the radio or spl. I read somewhere on xda that you must radio first before spl. Maybe that is the problem that I have. BUt I am not sure as I was flashing all day long just to get a hero theme. So I dont know all the steps I did (stupid again)
Thanx
Download THIS reformat sd card to FAT32 using your computer and sdcard reader. put the file on the sdcard. boot using camera+power.
Hi there Fingerlickin
Fingerlickin said:
Download THIS reformat sd card to FAT32 using your computer and sdcard reader. put the file on the sdcard. boot using camera+power.
Click to expand...
Click to collapse
I did this a copple of times but it says: not allow ... (and then the red numbers above somthing like 0072008 etc.)
I also tried RC7 but still same error.
I tried to make a goldcard, but I won`t flash, same error.
I dont want to spil anyone`s time so I dont think we can repair the G1 but what I want with this thread is to get the cause of this all.
Is it because I did not follow all the steps?????
Bcuz then I hope every dumbass like me reads this thread before they crush their G1 also.
I knew there was a chance of F**ing up so I took a risk and I`m not crying but I just want tips for the future and to prevent more people of doing such a dumb thing.
Thanx guys
Well if you can get into recovery and bootloader your not bricked. Is your phone rooted? What have you done to it so far? This can prolly be fixed if you can provide us the info we need.
supremeteam256
supremeteam256 said:
Well if you can get into recovery and bootloader your not bricked. Is your phone rooted? What have you done to it so far? This can prolly be fixed if you can provide us the info we need.
Click to expand...
Click to collapse
Ok, 2 days ago was the first time I changed anything from Tmo to custom.
My first modification was: http://www.youtube.com/watch?v=cfskzfjOMgc
How To Root Android in 1 Click
This worked like a charm and was perfect.
After that I installed
http://forum.xda-developers.com/showthread.php?t=538762
[THEME] HE-AERO v1.6 - 4.0.4/4.1.11.1*Now with Stericson Lockscreen*[9/20]
I had a black panel above my screen and was very happy. Because that is all I wanted.
Then I got greedy and wanted the rom from POST 1.
And then I got all the errors from Post 1.
So really, that is all I can think of I did.
dizzydix said:
Ok, 2 days ago was the first time I changed anything from Tmo to custom.
My first modification was: http://www.youtube.com/watch?v=cfskzfjOMgc
How To Root Android in 1 Click
This worked like a charm and was perfect.
After that I installed
http://forum.xda-developers.com/showthread.php?t=538762
[THEME] HE-AERO v1.6 - 4.0.4/4.1.11.1*Now with Stericson Lockscreen*[9/20]
I had a black panel above my screen and was very happy. Because that is all I wanted.
Then I got greedy and wanted the rom from POST 1.
And then I got all the errors from Post 1.
So really, that is all I can think of I did.
Click to expand...
Click to collapse
I'm on my work computer so I can't see whats in the youtube link. What version radio do you have? What version spl do you have? Did you format your sd card in 3 partitions?
supremeteam256
supremeteam256 said:
I'm on my work computer so I can't see whats in the youtube link. What version radio do you have? What version spl do you have? Did you format your sd card in 3 partitions?
Click to expand...
Click to collapse
I will provide you with the right information if I still can.
Im also at work, and my G1 is in the car. But I dont know if it has enough power bcuz Im going to drop it at the store after work.
But I will try to open the flash screen and note down the specs.
*** Did you format your sd card in 3 partitions? --- That doesn`t ring a bell.
I formated FAT32 but I never heared of 3 partitions, that is new to me.
Peace
dizzydix said:
I will provide you with the right information if I still can.
Im also at work, and my G1 is in the car. But I dont know if it has enough power bcuz Im going to drop it at the store after work.
But I will try to open the flash screen and note down the specs.
*** Did you format your sd card in 3 partitions? --- That doesn`t ring a bell.
I formated FAT32 but I never heared of 3 partitions, that is new to me.
Peace
Click to expand...
Click to collapse
You need to have the new radio and spl for hero to fit so if you didn't do that then that could be part of your problem. You card should be in 3 partitions (fat32, ext2/3, and linux-swap). There are several different ways to partition your card. You can do it in Ubuntu (tut in my sig), or you can do it in parted, and couple other ways.
supremeteam256
supremeteam256 said:
You need to have the new radio and spl for hero to fit so if you didn't do that then that could be part of your problem. You card should be in 3 partitions (fat32, ext2/3, and linux-swap). There are several different ways to partition your card. You can do it in Ubuntu (tut in my sig), or you can do it in parted, and couple other ways.
Click to expand...
Click to collapse
Haha, ok
Know what`s Ironic.. I left Ubuntu one week ago for Vista.
But I will put a disk in and try you method.
(that is after I send it to the store, it`s always easier to let them do it for you .
I will keep an update..
Peace
dizzydix said:
Haha, ok
Know what`s Ironic.. I left Ubuntu one week ago for Vista.
But I will put a disk in and try you method.
(that is after I send it to the store, it`s always easier to let them do it for you .
I will keep an update..
Peace
Click to expand...
Click to collapse
What are you going to have them do?
supremeteam256
supremeteam256 said:
What are you going to have them do?
Click to expand...
Click to collapse
I don`t know I just go to the store that I bought it from and I will send it for reparation. They will send it to tmo.
If it can`t be repaired I will get it back and then I will try it myself on sundays when I have nothing to do.
Why?
dizzydix said:
I don`t know I just go to the store that I bought it from and I will send it for reparation. They will send it to tmo.
If it can`t be repaired I will get it back and then I will try it myself on sundays when I have nothing to do.
Why?
Click to expand...
Click to collapse
Just want to make sure you don't say what you were doing to it. And they won't send it to T-Mobile they would send it to HTC for repair. But to be completely honest with you, I wouldn't do that. Your phone does not need to be sent off. As soon as you have the phone in front of you and you have time to mess with it, it can be fixed. As long as you can get into bootloader and recovery your good. Its your phone and you can do what you want with it, but it should be an easy fix. Let us walk you thru it first before going.
supremeteam256
supremeteam256 said:
Just want to make sure you don't say what you were doing to it. And they won't send it to T-Mobile they would send it to HTC for repair. But to be completely honest with you, I wouldn't do that. Your phone does not need to be sent off. As soon as you have the phone in front of you and you have time to mess with it, it can be fixed. As long as you can get into bootloader and recovery your good. Its your phone and you can do what you want with it, but it should be an easy fix. Let us walk you thru it first before going.
Click to expand...
Click to collapse
Woww, that is a major offer man.
Ok you know what I keep it one more day bcuz I appreciate your help.
I just lost hope bcuz I tried everything I could find on forums and google so I did my research but I couldent get it trough and spend yesterday 12 whole hours on trying to flash and got tired. (thats how much I love my phone).
So once at home I will post a foto or specs of the flash page.
I didnt know someone would really be this kind and helpfull.
dizzydix said:
Woww, that is a major offer man.
Ok you know what I keep it one more day bcuz I appreciate your help.
I just lost hope bcuz I tried everything I could find on forums and google so I did my research but I couldent get it trough and spend yesterday 12 whole hours on trying to flash and got tired. (thats how much I love my phone).
So once at home I will post a foto or specs of the flash page.
I didnt know someone would really be this kind and helpfull.
Click to expand...
Click to collapse
There are several of us that are helpfull and don't mind helping. It's just the repeated dumb questions and people that want there hand held for the simplest thing (not saying you). Then thats when we can get ruthless, but yea we will help you out. You will prolly realize after the fact that it was prolly something simple and prolly want to slap yourself for wanting to take it back. lol.
supremeteam256
supremeteam256 said:
There are several of us that are helpfull and don't mind helping. It's just the repeated dumb questions and people that want there hand held for the simplest thing (not saying you). Then thats when we can get ruthless, but yea we will help you out. You will prolly realize after the fact that it was prolly something simple and prolly want to slap yourself for wanting to take it back. lol.
Click to expand...
Click to collapse
Hahaha, Im already laughing. I hope I will smack myself.
I hope if its ok to also post some pictures I will make at home in about an hour.
And I may load a video to youtube of the flash screen, maybe it helps.
Who knows.
dizzydix said:
Hahaha, Im already laughing. I hope I will smack myself.
I hope if its ok to also post some pictures I will make at home in about an hour.
And I may load a video to youtube of the flash screen, maybe it helps.
Who knows.
Click to expand...
Click to collapse
Yea thats cool to post whatever. Just post when you get settled in.
supremeteam256
supremeteam256 said:
Yea thats cool to post whatever. Just post when you get settled in.
Click to expand...
Click to collapse
HI,
Here is the update:
My screen shows (in rainbow screen):
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
Sep 2 2008
Serial10
dizzydix said:
HI,
Here is the update:
My screen shows (in rainbow screen):
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
Sep 2 2008
Serial10
Click to expand...
Click to collapse
Ok I'm gonna have you start from the begining so we are on the same page. First thing I want you to do is download this http://www.megaupload.com/?d=EMY1HIVU that is RC29. Also is your card already partitioned to fat32?
I was updating my Nexus One and it gave me an error that looked like an Android being taken out of a box it was at this screen for atleast 30 mins before I decided to pull the battery and restart. Tried to turn on and it wouldn't do anything at all. I've tried charging it,pulling battery out overnight, soft and hard resets nothing at all no signs of life. Any other methods I can try or is it a brick?
Can you boot into fastboot or recovery?
Were you trying to flash a recovery.img?
None can't do anything no boot no nothing
sty3x said:
None can't do anything no boot no nothing
Click to expand...
Click to collapse
I believe it was in the process of flashing the radio maybe, if you pulled the battery during this process then I think your N1 is done.
I think the last thing I saw was writing radio.img then it gave me an error that looked like a box with an Android coming out with a arrow pointing to the Android
I don't think that was an error icon. It was showing you it was installing something. Taking out of the box onto your android phone. But it shouldn't have taken that long...
did you flash the wrong radio?
sty3x said:
I think the last thing I saw was writing radio.img then it gave me an error that looked like a box with an Android coming out with a arrow pointing to the Android
Click to expand...
Click to collapse
Yeah that explains it. Sometimes it takes awhile when updating. It wasn't an error it was going through the process of flashing the radio. It is water under the bridge now, but in the future never pull the battery while it is flashing the radio. Almost certain that you will brick your phone if you do.
Ah, anything I can do to it?
Hum.....let me buy it for $100 or send it to HTC For a new motherboard for $200 of they determine its not under warrenty
What is HTC warranty phone number I'm only getting there technical support
So I've apparently, effectively bricked my phone. Under bootloader it is listed as S-OFF. Is there any way I can return my evo in and stay under warranty?
Note: I can not reach recovery.
What happens when you rename a recovery to PC36IMG.zip and try to update via bootloader?
I go into a boot loop no matter what i do, no matter what I flash. I have flashed 10+ PC36IMGs with everything from bootloaders to recoveries, to every img that can be on the phone... there is a thread still on the first page if you want to look at that.
Anyways, it doesn't look like I'm going to be able to fix it, so this is more about what options are available to me in getting a new phone, if you having any suggestions though on what I can do to fix mine, please be my guest and comment on my thread below, I'm still trying to fix it!
Just report the phone lost or stolen and pay $100 deductible.
Sent from my PC36100 using XDA App
I would try one last time to flash Amon's recovery.
Download this: http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
Rename it to "PC36IMG.zip"
put it on the root of your sd card via a card reader if you have one or someone elses phone.
then update via bootloader.
Other than that I'm out of ideas. The good news is I'm not as savvy as 95% people on here, which means someone much smarter than me might know the answer. Good luck.
Hmm, yeah I may just have to pay the 100 then... but is that an insurance thing or a warranty thing? I don't have insurance
Do you think Sprint will even check for the S-ON?
thanamesjames said:
Hmm, yeah I may just have to pay the 100 then... but is that an insurance thing or a warranty thing? I don't have insurance
Do you think Sprint will even check for the S-ON?
Click to expand...
Click to collapse
i dont think its a warranty thing its insurance and i think your screwed
What happens when you put a pc36img.zip file on the root of your SD card and start up in bootloader?
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
So you cleared all the caches?
thanamesjames said:
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
Click to expand...
Click to collapse
What did you do that caused this issue? Or what were you trying to do? Also what hboot version do you have?
I've done "clear storage" I don't see a place to clear anything other than that in hboot.
thanamesjames said:
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
Click to expand...
Click to collapse
Pretty much. If you haven't tried yet, try re-rooting via toast's method.
http://forum.xda-developers.com/showthread.php?t=690762
Try going through the whole process. If successful make sure you have a nice stock ROM like the current Sprint Lovers ROM to flash.
Unfortunately my phone isn't getting listed as a device under adb, and thats part of the toast tutorial I have tried his eng-PC36IMG.zip, and it didn't work
woah woah woah....
take your phone to wal-mart and slide it over the demagnetizer at the register a couple times.
THAN take it in.
_MetalHead_ said:
What did you do that caused this issue? Or what were you trying to do? Also what hboot version do you have?
Click to expand...
Click to collapse
I had nightlies of CM7 they would reboot fairly often, but I just figured they were unstable. Out of nowhere it rebooted, and lost all my texts, and desynced my google account. I decided to switch to CM6. When i switched to CM6, soon after it rebooted out of nowhere, and then staid in an endless loop and never came out. I currently have hboot .76, for more fastboot commands.
Try this PC36IMG.zip. If it doesn't work the first time then try it again. If it doesn't work the second time, then I would say you're SOL. I know you said you've tried a bunch but they aren't all the same. It's the sprintlover's full update ROM.
_MetalHead_ said:
Try this PC36IMG.zip. If it doesn't work the first time then try it again. If it doesn't work the second time, then I would say you're SOL. I know you said you've tried a bunch but they aren't all the same. It's the sprintlover's full update ROM.
Click to expand...
Click to collapse
Is it from here? http://forum.xda-developers.com/showthread.php?t=830153
If so I've tried it
thanamesjames said:
Is it from here? http://forum.xda-developers.com/showthread.php?t=830153
If so I've tried it
Click to expand...
Click to collapse
Yep :/ I don't know what to tell you then man, sorry.
I guess I'm going to Sprint and playing stupid!
Has anyone done this successfully?
It sucks because as soon as I started having these problems, all the experts would be frustrated and say "*sigh* you're not bricked, you can get into bootloader" and so I was so sure it was fixable... but apparently not. Every time I mention it I have a thousand people yell at me "FLASH PC36IMG!!" Anyways thanks for the help!
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.
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.