Related
So this morning I was checking out the new choices in my Froyo leak - rooted Captivate, I clicked on every one of them to see what it is and then I clicked on one that said something like user accounts, well ever since then my phone has been a black screen only displaying the top clock and a no signal bar. What should I do next? Unfortunately Im stuck at work with no programs. So Im wondering what would you do, which Odin should I use? Ill be checkin in cause at least I can do this and plan fixing my phone for later
Im guessing you tried pulling the battery?
Sent from my SAMSUNG-SGH-I897 using XDA App
sure did tried the reboot screen.
and the other thing, now the phone wont go into sleep mode so my battery is slowly dying too
try to boot into recovery and clear out the cache...
I did that too and it clears and then i reboot then it goes right back to black screen
The same thing happened to me, but I wasn't digging around in the settings. Like previously mentioned, I booted into recovery, and cleared cache/factory wipe, and it booted back fresh. Luckily, I had a Titanium Backup from a few hours before it happened, so I didn't really lose anything.
I had something like this too. Can you get into Download mode and use Odin to return to stock rom? It took me several tries before Odin worked.
Well I still haven't heard anyone who has completely bricked there samsung captivate yet so I think you'll be alright. Just to be the 1 click Odin when you get home.
I'm pretty new myself at this But I think the only way were really screwed Is if we kill the bootloader.
Sent from my SAMSUNG-SGH-I897 using XDA App
i will try when i get home, im stuck at work unfortunately, at least i know im not the only one, i was also fooling with settings
thank you
Theres been a few people that have fully bricked their captivates... Including me.
If you got your captivate within the last couple weeks be careful using odin with a froyo kernel. Check the Q&A thread for a post titled "phone-pc something" (Using my phone otherwise I'd provide a link)
loserskater said:
Theres been a few people that have fully bricked their captivates... Including me.
If you got your captivate within the last couple weeks be careful using odin with a froyo kernel. Check the Q&A thread for a post titled "phone-pc something" (Using my phone otherwise I'd provide a link)
Click to expand...
Click to collapse
Well that sucks.
Sent from my SAMSUNG-SGH-I897 using XDA App
theMaginator said:
Well I still haven't heard anyone who has completely bricked there samsung captivate yet so I think you'll be alright. Just to be the 1 click Odin when you get home.
I'm pretty new myself at this But I think the only way were really screwed Is if we kill the bootloader.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I had one. OTA update. And I wasn't the only one. I couldn't even get into download mode.
yeah, bricked here too trying to go to Froyo. Sent to Samsung, they fixed it.
theMaginator said:
Well I still haven't heard anyone who has completely bricked there samsung captivate yet so I think you'll be alright. Just to be the 1 click Odin when you get home.
I'm pretty new myself at this But I think the only way were really screwed Is if we kill the bootloader.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
lol its happened to many people, myself included.
he said he bricked it trying to upgrade to ICS.
is the sticky at the top still the way to unbrick it? i noticed that a couple links were dead in the first post. granted i didn't go through all 17 pages, just wanted to make sure there wasn't anything newer then whats already been posted.
edit: he did say that the screen is showing s/w if that matters
Was it bricked by flashing a o2x rom? I think that may be the hardest brick I have heard of but still fixable. I believe if that is the case than following the sticky should restore the baseband and everything else.
Honestly though I would first try just reflashing CWM via nvflash, boot into recovery and load a stable GB rom. If that works, great.
LurkerRWO said:
Was it bricked by flashing a o2x rom? I think that may be the hardest brick I have heard of but still fixable. I believe if that is the case than following the sticky should restore the baseband and everything else.
Honestly though I would first try just reflashing CWM via nvflash, boot into recovery and load a stable GB rom. If that works, great.
Click to expand...
Click to collapse
he just said things went haywire when trying to flash ICS. i've been messing around with the sticky but can't get anything to work....yet!
im on windows 7 if that matters
and after i boot into recovery the screen is just flashing black. any ideas?
everything i do with flashing it just sits at the prompt saying "flashing" and nothing else happens.
blackbeasst said:
he just said things went haywire when trying to flash ICS. i've been messing around with the sticky but can't get anything to work....yet!
Click to expand...
Click to collapse
You apparently you did not even read the first post. XP only, will not work with Windows 7.
"As many have stated, pushing the v21E_00.kdz via the KDZ_FW_UPD program does work. It's just touchy.
This is a step by step guide to get you back in to working shape.
Note: You MUST do this via a PC running Windows XP. Running Vista/7 in compatibility mode is not going to work, period.
Edit: As an alternative, a virtual environment running XP will do the job. Those steps are up to you."
That's not true. I updated the baseband using win7 on my first try. No need for comparability mode.
Sent from my LG-P999 using XDA App
LurkerRWO said:
That's not true. I updated the baseband using win7 on my first try. No need for comparability mode.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Can confirm that too. Was working fine on 32 bit win7, using the method from the stickies upgrading wind's June baseband.
Sent from my LG-P999 using xda premium
duple and lurker, thanks for the confirmation that it works with 7
when i try and push the kdz i get the dreaded phone not found.
ok im on my xp machine here at work and heres what i got:
Part 1: Download the files you will need below.
V21E_00.kdz
KDZ_FW_UPD_EN
One-Click-G2x-recovery-flasher-06-16.rar
LG USB Drivers G2x
Part 2:
1) Install the LG G2x USB drivers to your WinXP machine.
2) Extract the entire contents of the One-Click recovery in to a folder and keep it handy.
3) Remove the battery from the phone. Hold both volume buttons and plug in the USB cable. If you are asked for a driver, look in the APX folder where you extracted the One-Click recovery archive.
4) Run OneClickRecoveryFlasher.exe and flash the stock recovery. Wait for the process to finish and close all windows and unplug the phone.
no problems with above steps. after that nothing works. when i put the battery back in and turn on thats when i get the flashing black screen, not back to the s/w screen.
5) Put the battery back into the phone and turn it on. You will be back at the S/W Upgrade screen. This is where you want to be! Now plug the USB cable back in to the phone. If everything is up to snuff you should have no driver problems at this point.
6) Extract KDZ_FW_UPD_EN.7z in to a folder. Inside is a msxml.msi. You need to run and install this first!
7) Run KDZ_FW_UPD.exe.. Leave the type set to CDMA and the phone mode set to DIAG. DO NOT CLICK ON "Read phone information"
8) Click the folder icon and load the V21E_00.kdz
9) Click launch software update (and pray!)
ok just for craps and giggles i tried booting into recovery and actually got the box with arrow and android! but it then reboots back to the lg screen and then flashing black screen
WOOT! finally able to get into CWM recovery!
is all that needs to be done now is install a stable rom?
double WOOT! back up and running. time to test the functionality of if though!
edit: can't find the sim and no service.
blackbeasst said:
double WOOT! back up and running. time to test the functionality of if though!
Click to expand...
Click to collapse
Delighted to hear that. So, another confirmation of the "old" folks stating it's 99.9% un-brickable.
Sent from my LG-P999 using xda premium
DupleX01 said:
Delighted to hear that. So, another confirmation of the "old" folks stating it's 99.9% un-brickable.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
and im a tard. sim was inserted bass akwards
blackbeasst said:
and im a tard. sim was inserted bass akwards
Click to expand...
Click to collapse
Congrats man.
Sent from my LG-P999
wifi seems to be flaky. keeps scanning and dropping work and home network
also it appears that the market wasn't on that version of the rom. is that a quick fix?
Now you have the recovery and baseband sorted, start from scratch and do a full wipe(including system internal/external SD). Then flash a stable ROM Weapon/EB to make sure everything is good. Just my 2 cents
Sent from my LG-P999 using xda premium
DupleX01 said:
Now you have the recovery and baseband sorted, start from scratch and do a full wipe(including system internal/external SD). Then flash a stable ROM Weapon/EB to make sure everything is good. Just my 2 cents
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
im was lucky to get it up and running, so im still a flashing noob! but what is considered a stable rom for this phone?
i grabbed one from cyanmod earlier today. i think it was from around 3/13?
blackbeasst said:
im was lucky to get it up and running, so im still a flashing noob! but what is considered a stable rom for this phone?
i grabbed one from cyanmod earlier today. i think it was from around 3/13?
Click to expand...
Click to collapse
You were lucky, indeed!
A CM nightly can be stable too, however I would flash either Weapon or Eagles Blood for a couple of days to have a piece of mind that everything is working cool. The most important would be a proper full wipe (cache, dalvik, system under mounts and storage, battery stats and imho internal and external SD too) too get rid of the previous mess caused by the unsuccessful flash, etc.
Sent from my LG-P999 using xda premium
I tried going back to gingerbread using Heimdall 1 click and it gives me a kernel error and failed. Now phone won't boot past the rogers logo. Any suggestions? No samsung screen. No green battery indicator when plugged in. Heimdall does detect the phone, and I've tried all USB ports and cords at my disposal. I use a mac so no access to odin. This is the first brick I haven't been able to get myself out of. Any help you would be appreciated
I am a gt i9000 owner, but can you get into download mode?
Sent by Santa Clause
If you can get download mode, then flash a gingerbread stock rom, even if it means you will lose root still do it, then flash a new rom of your choice, if you can get into download mode then you haven't got a brick
Sent by Santa Clause
Been bricked more than once...you have?
Embarking on a fresh new ROM without educating oneself can be very frustrating....since your on a Mac..with in the one click you say it reading your phone...can you get to download mode?
Pull battery
Plug in USB to phone
Hold both volume button
Pop battery back in
Do you see...the yellow Android digging?
http://forum.xda-developers.com/showthread.php?t=1293751
bigjoe2675 said:
Been bricked more than once...you have?
Embarking on a fresh new ROM without educating oneself can be very frustrating....since your on a Mac..with in the one click you say it reading your phone...can you get to download mode?
Pull battery
Plug in USB to phone
Hold both volume button
Pop battery back in
Do you see...the yellow Android digging?
Click to expand...
Click to collapse
I can get into download mode.heimdall detects my phone. I tried both qksters and adam outlers 1 click. neither would take. If I upgrade heimdall version (as it tells me its out of date) it wont get through the initial connection to the phone. if I use with out upgrade it continues to fail on kernel download.
This is my second brick (first one was when trying to root it on my mac) First brick was fixed through odin at my work. Unfortunately I don't want to wait till monday to have a functioning phone
teknhard said:
I can get into download mode.heimdall detects my phone. I tried both qksters and adam outlers 1 click. neither would take. If I upgrade heimdall version (as it tells me its out of date) it wont get through the initial connection to the phone. if I use with out upgrade it continues to fail on kernel download.
This is my second brick (first one was when trying to root it on my mac) First brick was fixed through odin at my work. Unfortunately I don't want to wait till monday to have a functioning phone
Click to expand...
Click to collapse
Hummmm..ok
Let's step back here does out prompt you for drivers?
....you might have to make a stop at your office..
Try different USB ports, I used heimdall yesterday to go back to gingerbread (so I could get the boot loaders) and I had the same problem as you, I finally got it to work with a different USB port and even then it kept failing...but I just kept trying and eventually it went through
(Pull battery, place battery back in, hold volume up and down, plug USB in-should put you in download mode...even if you can't see anything on your screen you can still enter download mode)
Sent from my SGH-I997 using XDA
DOesnt prompt me for drivers. It detects my phone and says ready to flash. I see the download mode screen. so its not completey screwed. Just can't get past the rogers logo.. I only have two USB on my macbook.. tried both quite a few times guess i'll mess with it some more. see if I can get it going. Thanks for the tips. ANy others ideas would also be appreciated
Alright, here it is:
I encountered the same problems yesterday, heimdall doesn't work when flashing back to stock from ics, from what I've found, you must use gtg's ultimate unbrick, the pit repartitions everything and also resets your binary counter (cha-ching! ). Once completed, your phone will reboot and be stuck at "...installing default apk files..." for a few minutes, don't panic, let it run its course. From there on, you can do the usual root/flash cwm deal. .
Sent from my SGH-I997 using Tapatalk 2 Beta-5
theROMinator said:
Alright, here it is:
I encountered the same problems yesterday, heimdall doesn't work when flashing back to stock from ics, from what I've found, you must use gtg's ultimate unbrick, the pit repartitions everything and also resets your binary counter (cha-ching! ). Once completed, your phone will reboot and be stuck at "...installing default apk files..." for a few minutes, don't panic, let it run its course. From there on, you can do the usual root/flash cwm deal. .
Sent from my SGH-I997 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Funny I just did that yesterday using qkster heimdall after running the ics for the day....no issues utilizing it...so i say it does work...
theROMinator said:
Alright, here it is:
I encountered the same problems yesterday, heimdall doesn't work when flashing back to stock from ics, from what I've found, you must use gtg's ultimate unbrick, the pit repartitions everything and also resets your binary counter (cha-ching! ). Once completed, your phone will reboot and be stuck at "...installing default apk files..." for a few minutes, don't panic, let it run its course. From there on, you can do the usual root/flash cwm deal. .
Sent from my SGH-I997 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I went back to stock from ics yesterday using heimdall...just took a long time and a lot of tries
I really think it depends on the computer though, for some Odin works best...for others heimdall works best
Sent from my SGH-I997 using XDA
bigjoe2675 said:
Funny I just did that yesterday using qkster heimdall after running the ics for the day....no issues utilizing it...so i say it does work...
Click to expand...
Click to collapse
I did not mean to be misleading, as you both have said, either or may work, I simply wanted to share my experience
mg2195 said:
I went back to stock from ics yesterday using heimdall...just took a long time and a lot of tries
I really think it depends on the computer though, for some Odin works best...for others heimdall works best
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
Sent from my SGH-I997 using Tapatalk 2 Beta-5
mg2195 said:
I went back to stock from ics yesterday using heimdall...just took a long time and a lot of tries
I really think it depends on the computer though, for some Odin works best...for others heimdall works best
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
Agreed. On my desktop (quad core 6 gb ram, watercooled blablablabl) can't run heimdal nor Odin to save its life.
My netbook (single core atom) took me back from CM9 with Odin like it was nothing.
My 7 year old laptop (running Ubuntu) works great using Heimdal (just run the .jar file as an executable)
theROMinator said:
I did not mean to be misleading, as you both have said, either or may work, I simply wanted to share my experience
Sent from my SGH-I997 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
No ... understood..no worries...there are some many that have never flashed or much less read anything regarding flashing are having so many prob`s...when this ics it's still bring birthed...for the infuse.
Instead of going to the dev section and doing some home work...understanding the basic info....they see ICS and have pictures of Sunday treats....in their mind...having no clue about the current ROM they are on now...Then the questions pop up...from individuals...after wards yelling SOS...But hey it's their phone.
bigjoe2675 said:
No ... understood..no worries...there are some many that have never flashed or much less read anything regarding flashing are having so many prob`s...when this ics it's still bring birthed...for the infuse.
Instead of going to the dev section and doing some home work...understanding the basic info....they see ICS and have pictures of Sunday treats....in their mind...having no clue about the current ROM they are on now...Then the questions pop up...from individuals...after wards yelling SOS...But hey it's their phone.
Click to expand...
Click to collapse
I've flashed lots of roms and never had any issues. Also looked through the forum and know the basics about getting back to stock. I'm no expert, but I have a decent idea what I'm doing. I do appreciate a forum you can ask questions though and have people help out when your stumped. I did what i could from the tools I have at my disposal here, and ran into some problems. I'm not yelling SOS, just asking for some tips as what I have tried hasn't worked. All the same I do appreciate everyones opinions and help they provide. THat's what makes this forum great.
why would you need to heimdall if you are on a rogers infuse? Isn't that for AT&T phones only?
teknhard said:
I've flashed lots of roms and never had any issues. Also looked through the forum and know the basics about getting back to stock. I'm no expert, but I have a decent idea what I'm doing. I do appreciate a forum you can ask questions though and have people help out when your stumped. I did what i could from the tools I have at my disposal here, and ran into some problems. I'm not yelling SOS, just asking for some tips as what I have tried hasn't worked. All the same I do appreciate everyones opinions and help they provide. THat's what makes this forum great.
Click to expand...
Click to collapse
I apologize wasn't directed to you just in general and your correct this forum is great...
Then reflash ics lol
Sent from my SGH-I997 using xda premium
threi_ said:
why would you need to heimdall if you are on a rogers infuse? Isn't that for AT&T phones only?
Click to expand...
Click to collapse
Because I don't have access to a PC for Odin, and the at&t should work to get me out of brick state. I currently can't get past rogers boot screen
GoSooners345 said:
Then reflash ics lol
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I don't have recovery.. otherwise I certainly would have
MODS: Please lock this thread. And delete it if I can keep the thanks stats, Thanks.
If your looking for an improved version, see here.
thanks!!!
tcf38012 said:
OK, so finally I recovered my phone from flashing an unsigned system.img on the 67.21.125 ICS (The second version).
I'll go into detail later but here is what I did:
First, I flashed everything included in my fxz minimal.fastboot files.
Second, I flashed the 2.3.6 boot, system, and webtop partition (DON'T FLASH ANY OTHERS RATHER THAN THE boot,system, and grfs img's or you will hard brick your device).
Third, I entered recovery and applyed the first ICS leak, then it went into fastboot and complained about recovery and cdt so I flashed it from the minimal fxz's. And then I re-applyed the ics leak and then Something unreal happened, it booted :laugh::laugh::laugh:.
Last, I OTA'ed to the .125 leak again and everything was back to %100 normal.
And thats the end of the story, someone can write a tutorial from there .
Cheers!!!
PS: I'm not responsible if you bricked your device for good becuase of this, SO DON'T BLAME ME!!!
PSS: If this helped, then please hit the THANKS button below.
Click to expand...
Click to collapse
Nice job!!!
So to make this clear, you found a way to go back to 2.3.6 from the second ics leak? Im not really understanding this.
Sent from my MB865 using xda premium
That is huge! Thank you..
Sent from my phone's mind
tmease1 said:
So to make this clear, you found a way to go back to 2.3.6 from the second ics leak? Im not really understanding this.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Accually, It is not downgrading to gb but getting ics working again. If you try to boot gb instead of going to recovery, then you would boot loop.
So if your bricked, then this is the solution to fix it.
tcf38012 said:
Accually, It is not downgrading to gb but getting ics working again. If you try to boot gb instead of going to recovery, then you would boot loop.
So if your bricked, then this is the solution to fix it.
Click to expand...
Click to collapse
Ya i got it after reading it again, thanks.
Sent from my MB865 using xda premium
Wow...this is EXACTLY what I need...I'm not sure as to how exactly you did this. The wording confuses me I guess...feel like a noob lately :/ But excellent work either, Hope I can get this down. I nees to get back to stock ICS but am only able to get into stock ICS recovery/fastboot. Awesome...I hear hope!
Sent from my MB870 using xda premium
DX2Trip said:
Wow...this is EXACTLY what I need...I'm not sure as to how exactly you did this. The wording confuses me I guess...feel like a noob lately :/ But excellent work either, Hope I can get this down. I nees to get back to stock ICS but am only able to get into stock ICS recovery/fastboot. Awesome...I hear hope!
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Yes his wording confused me a well, don't feel bad. I'm still not sure how he did this.
Sent from my MB865 using xda premium
DX2Trip said:
Wow...this is EXACTLY what I need...I'm not sure as to how exactly you did this. The wording confuses me I guess...feel like a noob lately :/ But excellent work either, Hope I can get this down. I nees to get back to stock ICS but am only able to get into stock ICS recovery/fastboot. Awesome...I hear hope!
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
tmease1 said:
Yes his wording confused me a well, don't feel bad. I'm still not sure how he did this.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Well, a few things are not so clear yet - give us a little while to try and come up with a more direct way - or for tcf to put together a guide - but this is my understanding (please correct me or add if necessary, tcf):
He's talking about the minimal fxz package he put together from here: http://forum.xda-developers.com/showthread.php?t=1912035 (which only has a linux script I believe - but you could flash them one by one through the command prompt in windows - or, we could get a batch file made up also).
Then, the system.img, recovery.img, and grfs.img only from 2.3.6 (found in the 2.3.6 fxz from here or the same are in the leak#1 2.3.6 fxz).
Then he applied the leak#1 ota package.
Got thrown back into fastboot.
Flashed the cdt.bin again from the minimal fxz package (which is actually from ICS leak#2/soak package) -- but not sure if he flashed recovery.img from there again also..
Then he re-applied the leak (#1?) again - and it booted to ICS.
So, I am not sure about the timing of things or how it exactly worked out yet, but I notice the linux script for the minimal fxz package doesn't have a reboot-bootloader before the cdt.bin flash - also there should probably be a pause after the reboot-bootloader lines to allow it to reboot completely before attempting to flash the next file. That may be partial reason for the multiple flashings of the cdt.bin.. but, again, maybe not - maybe it's all in some magical order... though a few of us will be digging a bit deeper into this I'm sure.
Thanks again to tcf38012 for pushing this thought of upgrading back to the leak - we were on that path at one time, but the pieces of the puzzle weren't fitting together..
alteredlikeness said:
Well, a few things are not so clear yet - give us a little while to try and come up with a more direct way - or for tcf to put together a guide - but this is my understanding (please correct me or add if necessary, tcf):
He's talking about the minimal fxz package he put together from here: http://forum.xda-developers.com/showthread.php?t=1912035 (which only has a linux script I believe - but you could flash them one by one through the command prompt in windows - or, we could get a batch file made up also).
Then, the system.img, recovery.img, and grfs.img only from 2.3.6 (found in the 2.3.6 fxz from here or the same are in the leak#1 2.3.6 fxz).
Then he applied the leak#1 ota package.
Got thrown back into fastboot.
Flashed the cdt.bin again from the minimal fxz package (which is actually from ICS leak#2/soak package) -- but not sure if he flashed recovery.img from there again also..
Then he re-applied the leak (#1?) again - and it booted to ICS.
So, I am not sure about the timing of things or how it exactly worked out yet, but I notice the linux script for the minimal fxz package doesn't have a reboot-bootloader before the cdt.bin flash - also there should probably be a pause after the reboot-bootloader lines to allow it to reboot completely before attempting to flash the next file. That may be partial reason for the multiple flashings of the cdt.bin.. but, again, maybe not - maybe it's all in some magical order... though a few of us will be digging a bit deeper into this I'm sure.
Thanks again to tcf38012 for pushing this thought of upgrading back to the leak - we were on that path at one time, but the pieces of the puzzle weren't fitting together..
Click to expand...
Click to collapse
Thanks for trying to clarify this. It seems like it would be time consuming for me to try since I'm a windows user. I am glad that he did find a way to get some of our soft bricked users back on track.
Sent from my SAMSUNG-SGH-I997 using xda premium
thanks for good job, waiting your instructions....
Yeah, this great man! I got an A2 that is stuck at the boot logo from a screw up on the second leak. I have a Samsung skyrocket now, so I'm the perfect guinea pig to try out what you need! Eagerly awaiting further instructions!
Sent from my SAMSUNG-SGH-I727 using xda premium
Did Anyone tested this?
I'll write a tutorial after school which I'm about to go to (High School). I get home at 3:45 - 4:30 and I get done my homework at 5:00 - 5:30 so I'll try to write it at 5:45.
Just hang in there!
Cheers!!!
I'm pretty sure i screwed myself here, but hopefully there might be a chance to fix it. I was flashing my phone back to stock gingerbread by using RSD, my phones data cord wiggled itself out when i bumped my desk, now its bricked. :\ any possibility of fixing this?
TinnuiN said:
I'm pretty sure i screwed myself here, but hopefully there might be a chance to fix it. I was flashing my phone back to stock gingerbread by using RSD, my phones data cord wiggled itself out when i bumped my desk, now its bricked. :\ any possibility of fixing this?
Click to expand...
Click to collapse
Can you still get into AP fastboot?
Sent from my MB865 using xda premium
There's totally still hope
It takes some pretty bad luck for this to actually kill it
just needs to run again, maybe manually
BUT, we need more detail to help. what version of the phone (ATT, SEARET, etc), what os version were you on before (ICS leak 1, 2, ota, GB, etc), what step was it on when it failed, what does the phone do now (totally dead, white light only, can turn on into fastboot with boot failure, etc.)
also, how much battery did you have when you tried to flash.
be specific, and we can help, do not lose hope quite yet.
lkrasner said:
There's totally still hope
It takes some pretty bad luck for this to actually kill it
just needs to run again, maybe manually
BUT, we need more detail to help. what version of the phone (ATT, SEARET, etc), what os version were you on before (ICS leak 1, 2, ota, GB, etc), what step was it on when it failed, what does the phone do now (totally dead, white light only, can turn on into fastboot with boot failure, etc.)
also, how much battery did you have when you tried to flash.
be specific, and we can help, do not lose hope quite yet.
Click to expand...
Click to collapse
I can still boot to AP fast boot, in fact thats all it boots from, i was running SVC6, so 2.3.6 and i was trying to roll back to 2.3.5 so i could update to ota ICS. when i turn the phone on all it does is boot to AP fast boot.
Its an AT&T atrix 2, the battery was at 70% when flashing, and i was on step 6, i tried re running it, it stayed on step 1 for hours.
Did you make sure to patch the fxz?
Sent from my MB865 using xda premium
Axis_Drummer said:
Did you make sure to patch the fxz?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
after it was to late.
TinnuiN said:
after it was to late.
Click to expand...
Click to collapse
If you can still access fastboot, you're still ok. Just try it again. Once you patch the file, you shouldn't have to do it again.
If it's not playing well try a different computer.
If you can't access fastboot, and no lights at all will come on, you may be out of luck man..
Sent from my MB865 using xda premium
TinnuiN said:
I'm pretty sure i screwed myself here, but hopefully there might be a chance to fix it. I was flashing my phone back to stock gingerbread by using RSD, my phones data cord wiggled itself out when i bumped my desk, now its bricked. :\ any possibility of fixing this?
Click to expand...
Click to collapse
Have you tried this????
http://forum.xda-developers.com/showthread.php?t=1539167
Sent from my MB865 using xda premium
Okay, now i have a new problem, the battery is to low to program, if i plug the phone into the wall then i can get it to boot to the AP menu, and if i plug it into my computer i can get it to show a white solid light. any ideas?
TinnuiN said:
Okay, now i have a new problem, the battery is to low to program, if i plug the phone into the wall then i can get it to boot to the AP menu, and if i plug it into my computer i can get it to show a white solid light. any ideas?
Click to expand...
Click to collapse
You need to charge your battery somehow if you don't have wall charger try Mcgrubber method...
Sent from my MB865 using xda premium