Ok so i was trying to root my dream but i failed really bad.
Before i applied the update.zip in fastboot i could get into fastboot and reset my phone, but now i cant. i was following the "root rogers htc dream guide" and could not continue as i needed to get into fastboot to load the boot.img file.
Can anyne help me out with this?
So if you hold camera+power you can get in to the SPL or fastboot? If you can't, you've bricked.
OH really dam.. ok well then i think i might have bricked my phone.
Is there any chance of getting out of brick or am i screwed?
There is currently no way to recover a brick. You could take it back to Rogers, just play dumb and say that it won't turn on anymore, do not use any words that imply you're tach savvy
Just to make sure, try booting holding power+home too and try taking the battery out a few times, but chances are you've bricked :-/
yeah no i have tried every thing i think i might be bricked.
Ill take it back to rogers, haha funny thing i have an omnia i910 and there are no roms for bell to flashed it with a telus rom, i took it back they look at the phone then looked at me and gave me a new one.
Will try it with this one.
The same thing happened to me yesterday. There must be something wrong in the guide. It should be taken down before this happens to others.
Actually, many guides are not incorrect, its just that many new phones have the DVT board and many older guides does not address that issue -> read about it here. I am not saying that rogers guide doesn't(because I didnt use that guide) but thats normally the case.
See http://forum.xda-developers.com/showpost.php?p=4402225&postcount=292
Related
hi i need help plz after rooting i don spl . the device now on g1 logo i try meny things home+power - cmera+power ..... nothing
First of all, you've officially murdered the English language. The only way I sort of understood what you were saying was by copy and pasting your post to Google Translate.
Secondly, I still can't understand it. So you rooted but didn't flash an SPL but flashed the radio, and now your stuck at G1 logo? Hmmm, I could only presume you've successfully entered Bricksville (Population: Noobs*Infinite).
Try pulling out the battery and boot into Recovery (Home + Power) Mode, FastBoot (Back + Power) Mode, or Bootloader (Volume Down/Camera + Power) Mode.
Or plug in USB adapter into device and setup ADB. After you've successfully setup ADB, get back to me so I can give you the commands and needed nbh files to pull you out of your predicament.
I mean, after change recovery img I done spl but the device freeze on G1 logo and it doesnt respond . what you mean setup ADB ???????
dude you are basically f'ed. you didnt update your radio did you. you just flashed a spl. welcome to BRICKSVILLE. population...YOU. and countless others who probably didnt READ AND RE READ THE ENTIRE POST AND READ WHILE YOU ARE DOING THESE PROCEDURES. these CAN AND WILL BRICK YOUR PHONE IF YOU DO NOT KNOW WHAT YOU ARE DOING.
It's quite amazing that the population of "Bricksville" continues to grow. There is plenty of literature out there about rooting your device but it still seems to elude some. Just awesome. And how true.. Noobs*Infinite... I lol'd.
nolimit78 said:
It's quite amazing that the population of "Bricksville" continues to grow. There is plenty of literature out there about rooting your device but it still seems to elude some. Just awesome. And how true.. Noobs*Infinite... I lol'd.
Click to expand...
Click to collapse
Very true, it's impossible to brick unless you have trouble reading that means you need to go back to elementary.
Ace42 said:
Very true, it's impossible to brick unless you have trouble reading that means you need to go back to elementary.
Click to expand...
Click to collapse
+1. This is true.
Meh, it's probably just a troll.
Lol these posts are quite funny
bricksville... I'll keep that in mind... lol
I think I asked for help, not a silly jokes
majed2001 said:
I think I asked for help, not a silly jokes
Click to expand...
Click to collapse
you got help. the jokes were for our amusement. its not our fault you bricked your phone, we are allowed to "chuckle" when other people mess up, because we know that we are smart enought to keep our very expensive phones up and running.
Hello all,
I think I may have bricked my nexus one. It is completely my fault for attempting things that I knew little about, so flame away But after the flaming, if anyone is willing to help I would be sooooo thankfull...
I successfully rooted my phone following the instructions on this page: (all links edited with a double asterisk as I don't believe I can post links)
h**p://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Then successfully installed cyanogenmod (which is awesome!) following this page:
h**p://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
All was well, I even got the modaco desire rom up and running, and was happily switching back and forth using the recovery screen. I had nand backups for specific setups, etc.
Then I decided it would be good to know how to go back to stock, and found this page:
h**p://**w.androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
I followed the instructions to the letter (I think) except for erasing userdata (it said "failed: remote not allowed"). I thought that things would be ok, since I'd recently wiped, so I followed the page till the end.
The phone rebooted, and I got the original nexus boot animation - but it's in an endless loop! What's worse, it that now when I try to go to the bootloader or recovery mode, I get the exclamation triangle with the little android.
Is there any way through a command prompt (or other method) that I can fix this? I tried to re-flash the RA recovery image through the command prompt, but the response was, "waiting for device."
ANYTHING that anyone can suggest to help, I would be so thankful! I've been loving the nexus, and hate to think that I crippled it
Thanks in advance,
Randy
I doubt its bricked.
Noticed you didnt mention that fast boot doesnt work? (power button+trackball) try it.
Once you get to fastboot you can flash any ROM back. (fastboot flash **** commands from a command shell)
Did you ever perform a Nand Backup from Recovery?
It's not bricked, the only way to brick is to interrupt power when flashing a Radio image
Connect phone to PC. Open command prompt.
adb reboot recovery
Wipe, reflash.
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
nexus5894 said:
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
Click to expand...
Click to collapse
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Paul22000 said:
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Click to expand...
Click to collapse
............................
It worked!!!!!
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Randy Malkoski said:
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Click to expand...
Click to collapse
Glad to hear it. You learn the most by trial and error.
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
revonomics said:
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
Click to expand...
Click to collapse
Tell me what i need to download again and how to go about it...i really need my phone working again ((((
I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Call ahead of time and see what they say on the phone?
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)
I don't know what the policy is.... most likely, as soon as they see where you're at, the tech will figure out that you were trying to root your phone, and you'll be SOL.
Have you tried booting your phone via ADB? Maybe you can go into recovery via adb shell and see if you can go from there....
if you can get it to power up all is not lost, try pushing AMON's recovery via fastboot
Fastboot
Copy recovery-RA-evo-v1.8.0.img in your android-sdk-windows\tools\ folder
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)
Since your phone turns on and you can boot into fastboot. Bricked would mean nothing happens period. There's still hope. Try this thread: http://forum.xda-developers.com/showthread.php?t=780141. There's a video walk-through showing you how to unroot and return to s-on. Then you may be able to start over.
Good Luck!
-kp
Edit: Try GMan's suggestion above 1st.
Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks
Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.
indagroove said:
Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.
Click to expand...
Click to collapse
Sprint Insurance right? I don't... I might do that but that's my last resort.
josh4trunks said:
Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks
Click to expand...
Click to collapse
If you can boot into the hboot just run a ruu and restore the factory Rom, if all fail pm me your number and I will walk you thru it
Sent from my PC36100 using XDA App
shameless bump - completely changed opening post
I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week.
What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.)
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!
haplo1818 said:
I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week. What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!
Click to expand...
Click to collapse
Tried this multiple time with different PC36IMG.zip, always get Failed-PU
Partition Update Error, I might try the 3.30 version though just to make sure.
Won't like my opinion but, you knew the risks of rooting. If you can't fix your phone then you should add the insurance and suck up the deductible fee. You don't deserve (or anyone for that matter) a free replacement for ****ing up your phone. It sucks but that's the risk. They'll normally have you one the next day.
Your phone is definitely not bricked and is fixable. Do you have adb drivers installed on your PC? If not find them and install them then try this: http://forum.xda-developers.com/showthread.php?t=829045?
Since you are already s-off you won't have to do all the steps, but by reading the entire OP you could figure out where to start and what to do. Just to be on the safe side you may want to start at the beginning using HBOOT USB from this screen you posted ftp://eto.homeip.net/shared/IMAG0004.jpg and start completely over. you are not bricked. Just hang in there and someone here will get you hooked up. You are in the right place my friend.
Evo's are really not that easy to fully brick.
I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode
Have you tried using a different SD card? Is it possible that something is corrupt with it? I also hear that you need to have at least 1GB of free space on the card when your trying to flash it.....
Let me just say myself and this guy stayed up late last night working on this phone trying every possible root/unroot method you can think of.
The pc he is using has adb drivers installed but the computer wont recognize his device as a adb device. Fastboot on renders certain commands and we tried all with various recoveries. I hit up a dev and we went thru different things and cant seem to figure this one out
As I told the Josh it can not be bricked because we get the bootloader and fastboot screen, I think its not even the partition but the recovery. Also he has a modified hboot by someone on xda (josh please post the link) which I believe that pc36img is whats causing all the problems.
If anyone could help it would be appreciated!!
Jbcarrera said:
I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode
Click to expand...
Click to collapse
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
I'm sure he thought you needed the engineering SPL to be able to flash roms. When I rooted mine back in June with toast's method, that was the way to do it. I rooted my girl's new Evo last month using Unrevoked, and I also downgraded the hboot because I thought I had to in order to flash a custom rom. Fortunately, I was able to do so with no issues.
Cleared all the caches?
craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
The partition table is screwed but there has to be a way to reset it I knew that method was risky told my friends to stay away from it
Sent from my EVO at the edge of hell
I've been teaching my girl about the whole rooting and running other roms thing. I've been messing with Android Devices for a while, But never messed with a G1, I currently own a DINC and GS.
she got it rooted and running the newest CWM. But we hit a snag getting any sort of custom rom working. One of the roms required the DangerSPL... lol since that, it will not pass the G1 screen and will not boot into Recovery.
I need help getting this phone back. Any thing anyone can think of?
Did you try flashing the proper radio first?
One of my Schnauzers posted this.
We followed all instructions given, Radio, SPL, and Rom. I made sure she followed the instructions given by the dev that made the specific roms.
The problem is still the same. only the G1Logo, No Recovery or Bootloader starts. You attempt to, and just that logo pops up.
lol stupid "how to fix your bricked g1" threads, every single one of them can easily get into the boot loader or recovery and they call it bricked.
Android G1 mobile software required (urgent)
hi,
My mobile set does not proceed after G1 logo. I need mobile software and method to do that.
i shall be grateful.
Regards,
Khurram
khurramsarwar, Press and hold the Camera Button and while holding, press the power. What happens? Try Home+Power. What happens?
See a real brick is when these things don't work. Like what I'm trying to fix.
You have a lovely new paperweight.
Your only option is the following...
http://forum.xda-developers.com/showthread.php?t=591048
Yeah I know. I told her to get another, we have already found like 3 or 4 for around 25 bucks! Just waiting for her to get it so I can do it right this time. I told her to be patient and wait for me to do it. But she is anything but.
So buy four G1's for a cool hundo...and split them. Let her do two and you do two. I'm sure she's capable of a second chance alone. If she wants it...shell get 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.