I successfully flashed to att ICS using Jim's method. Then I decided to roll back to 2.3.6 and used Jim's ICS back to 2.3.5 fxz fix zip file. The RSD stopped at 5/19 reboot bootloader for a long time and the screen was off. I hit the power button trying to turn on the screen without thinking. Then I realized that I was flashing! It was too late and I saw FAILED on RSD. My A2 cant turn on anymore. I did not unplug or pull the battery. Any help would be appreciate!
qtqt710 said:
I successfully flashed to att ICS using Jim's method. Then I decided to roll back to 2.3.6 and used Jim's ICS back to 2.3.5 fxz fix zip file. The RSD stopped at 5/19 reboot bootloader for a long time and the screen was off. I hit the power button trying to turn on the screen without thinking. Then I realized that I was flashing! It was too late and I saw FAILED on RSD. My A2 cant turn on anymore. I did not unplug or pull the battery. Any help would be appreciate!
Click to expand...
Click to collapse
DId you replace ALL of the files and then point the RSD to the xml?
Can you boot into fastboot by holding power button and vol down.If can you just reflash it using rsd lite.Tell me more detail about your atrix 2 current rom and which version of rom you are flash with rsdlite.
Sent from my MB865 using xda premium
Exact same problem has occurred to me as well.
I did replaced the files Jim created to FXZ back to 2.3.6 from ICS
My Battery was fully charged at the time of flashing. Flashing stopped at 5/19 reboot bootloader for 15 mins then tried rebooting it manually but it didn't started.
Now I've tried everything but it is not even starting in Fastboot
Please help me with this, I don't want to start any new thread so posted my problem here.
EDIT: I think this is a common problem as the OP here also have the same problem
http://forum.xda-developers.com/showthread.php?t=1781045
http://forum.xda-developers.com/showthread.php?t=1700775
I only flashed ICS when Jim confirmed that it was possible to revert back to 2..3.5
I think there is a problem in reverting back to 2.3.5 once applied ICS update and people should be aware of that.
Everyone should stop flashing ICS leaks otherwise they might end up bricking their phone forever.
100% same to me.
Up to ICS ok, back to Fxz with RSD and stuck at 5/19 reboot-bootloader step, I disconnected cable and phone black forever.
A lot of people they failed when flash with RSD but no problem, just take battery out and return, boot again to fastboot to re-flash. I think wrong file in Fxz not makes this problem, main cause I still don't know ! Maybe we are unlucky man ?
FXZ is not wrong one as I did used it when I had to flash back to stock from lithium Rom last week. I think phone is dead because it is not even booting into fastboot.. I've tried even booting to our stock recovery by pressing 3 buttons but no luck so far.
Its just very bad few hours back I was running ICS and now my phone is not even booting up.
OMG man!! I should have make a thread about this yesterday, but maybe nobody would of paid attention. I didn't really want this to happen to anyone, when flashing from 4.0.4 back to 2.3.5 it will get stuck at 5/20, something like that saying "rebooting loader". Now my phone with a blackscreen is getting hot when I insert the battery and when I plug it without a battery into my laptop or wallcharger and I dont have warranty. I call it white LED of death, when I plug it in to my laptop without a battery hehe , so I guess i'll be paying maybe 200$ dollar for it to be repaired, well if they repair it though, they charge so much here.. But i'm still trying to look what I can do, before I take it to a repair shop.
I heard about this problem when leak ICS for China/HK market 1 month ago, from xda man, and Jim he warned everybody here take care when coming back GB from ICS leak should make your phone bricked.
Now ATT ICS leak was released and all trusted Devs here confirmed that we can turn back to GB without problem, so I thought that it was safe to do with. Next day Jim posted new thread with new patch file. So sad ... I'm too late, we're too late ...
vinamilk said:
I heard about this problem when leak ICS for China/HK market 1 month ago, from xda man, and Jim he warned everybody here take care when coming back GB from ICS leak should make your phone bricked.
Now ATT ICS leak was released and all trusted Devs here confirmed that we can turn back to GB without problem, so I thought that it was safe to do with. Next day Jim posted new thread with new patch file. So sad ... I'm too late, we're too late ...
Click to expand...
Click to collapse
I didn't even flashed ICS leak first day, I did it second day when Jim confirmed and uploaded a link for new replace files.
prasannapmv said:
I didn't even flashed ICS leak first day, I did it second day when Jim confirmed and uploaded a link for new replace files.
Click to expand...
Click to collapse
So this is the point that I'm very confused, I think that even failed flashing phone still powered on normally : wrong boot.img --> just jamed at boot logo, wrong bootloader --> screen turn on and shows errors; need to be flashed again by RSD or script. Some man here even not flashed anything, just root then reboot and phone dead without any reason.
vinamilk said:
So this is the point that I'm very confused, I think that even failed flashing phone still powered on normally : wrong boot.img --> just jamed at boot logo, wrong bootloader --> screen turn on and shows errors; need to be flashed again by RSD or script. Some man here even not flashed anything, just root then reboot and phone dead without any reason.
Click to expand...
Click to collapse
I guess it has something to do with our bootloader, maybe it's stuck or not even working.
darkmixta said:
I guess it has something to do with our bootloader, maybe it's stuck or not even working.
Click to expand...
Click to collapse
I just talked to a Motorola service person he was saying in some rare cases a inbuilt ROM(read only memory) chip which stores bootloader files gets corrupted and in that case it might not even be possible to boot into fastboot.
I don't know how far he is right but one ting we are sure that our hardware was perfectly ok before flashing FXZ.
For me I even made sure that my battery was fully charged before starting FXZ.
prasannapmv said:
I just talked to a Motorola service person he was saying in some rare cases a inbuilt ROM(read only memory) chip which stores bootloader files gets corrupted and in that case it might not even be possible to boot into fastboot.
I don't know how far he is right but one ting we are sure that our hardware was perfectly ok before flashing FXZ.
For me I even made sure that my battery was fully charged before starting FXZ.
Click to expand...
Click to collapse
Same here I had like 90% battery or more, is you're phone becoming hot? When you plug it in or insert the battery?
darkmixta said:
Same here I had like 90% battery or more, is you're phone becoming hot? When you plug it in or insert the battery?
Click to expand...
Click to collapse
yes its getting heated when connected to a wall socket or on a battery.
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
prasannapmv said:
yes its getting heated when connected to a wall socket or on a battery.
Click to expand...
Click to collapse
Hahaha, what should we do? Yesterday I felt like throwing my phone into the wall man and just %$#@ Motorola, this is like the biggest failure ever!! Hard bricked without doing something wrong.. Wish I could go back in time sometimes and I don't even have warranty which sucks, what are you gonna do?
Really hard to hard brick? http://forum.xda-developers.com/showpost.php?p=28324515&postcount=10
We hard bricked so easy..
jimbridgman said:
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I was already using RSD 5.7
jimbridgman said:
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I did not. It is 5.6. That may be the reason. I got my A2 from att in Nov 2011, so I guess it is the same earlier version, right?
To those with the issue, can you not get back into ap fast boot? Either hold both volume buttons down with power, then select it from the menu, or i have found that holding up with power will boot you right into fastboot.
Sent from my MB865 using xda premium
Fall of Enosis said:
To those with the issue, can you not get back into ap fast boot? Either hold both volume buttons down with power, then select it from the menu, or i have found that holding up with power will boot you right into fastboot.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Nope they can not even power on anymore. This is what we all feared. The hk leak had this same thing in it...
Looks like moto will be warrantying a bunch of phones.
I am just not sure why I can still do it...
We have had way too many of these now for it to be user error or an accident.
Sent from my SAMSUNG-SGH-I747 using xda premium
Related
Hello Everyone,
I have a rogers captivate. I was trying to update to 2.3 android using Odin . I followed the whole process as stated. After rebooting, I got AT&T logo??? and the phone will not boot, go into recovery mode, or connect to my computer. Have I messed up my phone. Please advice.
how did you get an AT&T logo if it doesnt boot?
also what part of the process were you at? gingerbread shouldnt give the white ATT screen
it should give the "i9000" screen with gingerbread.
or were you flashing stock ATT first?
there is nothing wrong with having the wrong boot screen AND A FIX WAS RELEASED LAST NIGHT FOR GB
the fix for stock ATT has been out for a while. AND MY STOCK ROM FIXES IT TOO!
did you read the part about the button combos changing with gingerbread? or if you are on the ATT stock, use old button combos. Also you should have found my stock rom link before flashing, info there too!, its in my sig,
you have to give us more information to help you.
I beleive I was installing it to stock ATT first. That is when this happened. I was on Odin one click install. I remember the phone saying "do not disconnect the target". then all the installation was done from odin. This phone had 2.2 from samsung.Right now all that happens is that the phone starts and a flashing att logo on white background stays..
please let me know what other info is needed. i will post it all to the best possible
boot into download mode and flash ATT stock again. something messed up
are you using the "one click odin" or the other odin?
and what gingerbread are you trying after?
how do i do that. i have tried vol up+down+power combo. still the same flashing logo with no menus. i was using one click odin. and i was still on installing stock android. never got the chance to go to 2.3
If you can't get into download mode through the 3 button way you might need the jig. You got lucky since you're still able to boot up some have perma brick so try the jig and flash back to stock
Sent from my SAMSUNG-SGH-I897 using XDA App
HOLD VOL UP + DOWN
the plug in USB to PC.
keep buttons held until screen comes on!
i asked which gingerbread you were going to do AFTER
What is the build number on your phone, 4 numbers printed under the battery, mine is a 1010 for example, which mean oct. Of 2010 is when it was built. Some phones 1010 and after will not accept the one click odin rom and cause a bootloop like you are having, Try an odin package from TRusselo's sig instead.
my packages dont have the bootloaders. that might be whats screwed up with blinking att boot.
need download first before anything. i do have a GB bootloader package separately
something else:
try removing battery,
plug in USB to PC and Phone
Hold both Volume buttons
put battery back in.
should get you download mode
I really have noidea about what gingerbread i was after, i guess i wanted just the stock android without any custom software from samsung. I am total noob here as far as androids go.
the number on the battery say 2010.12.20 and the last forr nos under the battery at s/n are 11.02.
what is a jig. how do i use it. My phone cannot connect to the computer.
When I try to reset my device by any method, whether usb or power combos, it goes into either a. ATT logo flashing every few secs. or b. battery charging logo with nothing happeining.
Also my phone cannot be seen on my computer
gingerbread isnt for noobs
NOT THE DATE ON the battery
UNDER the battery ON THE PHONE
4 digit number
if you dont know what a jig or gingerbread or any of this stuff is,
you shouldnt have touched your friggin phone!
My apologies. the number is 1102. I understand I have screwed up. Any chance of having a working phone again.
GO GOOGLE A CAPTIVATE JIG AND BUY ONE
you wont be able to make one if you cant follow instructions.
that is your only hope. if not your phone is F'ed up perminantly.
your ONLY HOPE AFTER, is if your phone *somehow stops* turning on *forever*
and you send it back for warranty, and play dumb! ..... ..... ... .. .
PROGRAMMING a phone cant be learned it 5 minutes.
HELL you cant even read the friggin instructions (written for experienced users) in 5 minutes
this was an expensive lesson on researching and learning before doing
hitechchef said:
My apologies. the number is 1102. I understand I have screwed up. Any chance of having a working phone again.
Click to expand...
Click to collapse
Sorry for stepping in..
Yes there is. Might be a little complicated tho. You have some reading to do my friend.
Tru, I'll let you handle it but HiTechChef, you might've to go in for waranty and exchange it saying it did that after you tried to update through Kies. They'll check it and give you another one.
Thanks I will try this method
BWolf56 said:
Sorry for stepping in..
Yes there is. Might be a little complicated tho. You have some reading to do my friend.
Tru, I'll let you handle it but HiTechChef, you might've to go in for waranty and exchange it saying it did that after you tried to update through Kies. They'll check it and give you another one.
Click to expand...
Click to collapse
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
TRusselo said:
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
Click to expand...
Click to collapse
Oh right.. Wow..
Yep, go read about a JIG (it's pretty simple to use). You can either build it or buy one from mobiletechvideo or ebay.
TRusselo said:
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
Click to expand...
Click to collapse
Lol That kind of subtly is lost here... noone is picking up on your suggestion...
and thats how its going to stay,
ive said it before with almost the same words.
ive laid out all the tools....
correction of the original problem is necessary,
research is salvation,
resistance is futile.
there it is... i laughed... all is good again...
Phone : unlocked AT&T
What was done : used multiple ways to get back to GB including "A2_go_bak_win". at i ended up in boot loop.... then i used RSD lite to do the same this it failed in between .... (battery was 50%)
After this the phone's screen is absolutely blank ... no powering up... just one catch if i put battery into the phone it starts getting warmer....
Any suggestions.....
sanatan said:
Phone : unlocked AT&T
What was done : used multiple ways to get back to GB including "A2_go_bak_win". at i ended up in boot loop.... then i used RSD lite to do the same this it failed in between .... (battery was 50%)
After this the phone's screen is absolutely blank ... no powering up... just one catch if i put battery into the phone it starts getting warmer....
Any suggestions.....
Click to expand...
Click to collapse
When you flashed through RSD did you use the ICS patch? The patch skips the mbmloader which is the file that bricks your phone. Also Jim's script usually has to be run twice before the phone boots (first time it just hangs on Moto Logo).
If you didn't use the patch your phone is gone. Nothing you can do besides get a replacement....
farshad525hou said:
When you flashed through RSD did you use the ICS patch? The patch skips the mbmloader which is the file that bricks your phone. Also Jim's script usually has to be run twice before the phone boots (first time it just hangs on Moto Logo).
If you didn't use the patch your phone is gone. Nothing you can do besides get a replacement....
Click to expand...
Click to collapse
exactly.
farshad525hou said:
When you flashed through RSD did you use the ICS patch? The patch skips the mbmloader which is the file that bricks your phone. Also Jim's script usually has to be run twice before the phone boots (first time it just hangs on Moto Logo).
If you didn't use the patch your phone is gone. Nothing you can do besides get a replacement....
Click to expand...
Click to collapse
I would also like to know if you tried to use the patch for ics in rsd.
Sent from my MB865 using xda premium
It looks like he tried to use my script, but got the odd flash that 1 in 10 people seem to get. All the OP needed to do was rerun the script, that is posted in my thread about the return to GB thread. If it fails the second time, all you need to do is use RSDlite, and point it to the XML file that came within my script.
I hate to tell the OP, but you are bricked.
This is why im still scared to downgrade back to GB.
Sent from my MB865 using xda app-developers app
bsballkingben99 said:
This is why im still scared to downgrade back to GB.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
lol, I know
bsballkingben99 said:
This is why im still scared to downgrade back to GB.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Look, as with everything on this board, read WHOLE threads before you attempt anything... most times people post an issue and then there are ways posted on how to get around it.
If you follow the directions and have an issue post in the thread and one of us have most likely encountered it, and give you fix... DON'T do as the OP did and just start trying things. One of us devs or Sr. members will get you you taken care of fairly quickly, but panicing and just starting to try things is the easiest way to brick.
I wouldn't want to downgrade either.. to scared I might mess up
Sent from my MB865 using xda app-developers app
jangeles323 said:
I wouldn't want to downgrade either.. to scared I might mess up
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
I've done it like 8 times already... It's not too bad as LONG AS YOU FOLLOW DIRECTIONS!
Went to Motorola Service Center .... motherboard need to be changed.... INR-6800 ~ 122 USD...
I ll get it tomorrow...
sanatan said:
Went to Motorola Service Center .... motherboard need to be changed.... INR-6800 ~ 122 USD...
I ll get it tomorrow...
Click to expand...
Click to collapse
Aww that sucks? Why don't they give you a replacement? Aren't you under warranty?
It is under warranty but i bought it from US and now i am in India.... the IMEI no will change too
sanatan said:
It is under warranty but i bought it from US and now i am in India.... the IMEI no will change too
Click to expand...
Click to collapse
$122 is cheap for a motherboard replacement. Consider yourself lucky it did not cost you more.
Hey guys I didn't find any useful posts for this device with the same problem.So I started a new thread. Well I was googling and texting and all of a sudden my phone reboots. I thought well it's nothing and put my phone down, 15 minutes later I was hoping for it to be on and ready to be used and all I saw was Dual Core Technology. I rebooted it countless times to see if it'll come alive and no luck. I did root the phone awhile back and never had any problems with it until now.
I did try to go to recovery and all it shows is the android with an exclamation mark. I can get into fast boot and everything but I am a noob with fast boot so I don't exactly know how to wipe the phone by using that.
So I am counting on you guys to help me out. I don't even know if my phone is charging atm I just have it plugged into my power port and all it shows is Dual Core Technology and the battery is dead for letting it sit on that screen for about 30 minutes. I hope you guys can help.
Thanks,
Mike
Have you tried to fxz back to stock using RSD Lite? If not make sure your battery is charged before doing so. That should do the trick. If you have a back up try the recovery. When the Android with the exclamation comes up hit both the up and down volume keys at the same time.
Sent from my MB865 using xda app-developers app
MaTrixJ said:
Hey guys I didn't find any useful posts for this device with the same problem.So I started a new thread. Well I was googling and texting and all of a sudden my phone reboots. I thought well it's nothing and put my phone down, 15 minutes later I was hoping for it to be on and ready to be used and all I saw was Dual Core Technology. I rebooted it countless times to see if it'll come alive and no luck. I did root the phone awhile back and never had any problems with it until now.
I did try to go to recovery and all it shows is the android with an exclamation mark. I can get into fast boot and everything but I am a noob with fast boot so I don't exactly know how to wipe the phone by using that.
So I am counting on you guys to help me out. I don't even know if my phone is charging atm I just have it plugged into my power port and all it shows is Dual Core Technology and the battery is dead for letting it sit on that screen for about 30 minutes. I hope you guys can help.
Thanks,
Mike
Click to expand...
Click to collapse
Couple things we need to know mate. What firmware are you running? 2.3.5? 2.3.6? Or ICS?
These all play into how you are going fix your phone. And frankly your stock recovery is not going to do you any good with this issue. You WILL have to FXZ back, UNLESS you have a backup made in a different recovery system, IE: bootstrap, or bootmenu. Once again all dependent on what firmware you are on. If you can answer those questions, we can help you with the right procedure.
A good thread to start with is this one: Noobs guide to Android and the Atrix 2
It will give you all the info you need on the FXZ and fastboot.
More info and we can fix ya! :highfive:
EDIT: just saw your battery issue. Pull your battery until you are ready to flash in Fasboot. You need to conserve. How much battery do you think you have? Or is it dead? Flashing in FB and having your phone die due to low battery is a SURE way to hard brick your A2.
Fall of Enosis said:
Couple things we need to know mate. What firmware are you running? 2.3.5? 2.3.6? Or ICS?
I am running 2.3.6 stock
These all play into how you are going fix your phone. And frankly your stock recovery is not going to do you any good with this issue. You WILL have to FXZ back, UNLESS you have a backup made in a different recovery system, IE: bootstrap, or bootmenu. Once again all dependent on what firmware you are on. If you can answer those questions, we can help you with the right procedure.
A good thread to start with is this one: Noobs guide to Android and the Atrix 2
It will give you all the info you need on the FXZ and fastboot.
More info and we can fix ya! :highfive:
EDIT: just saw your battery issue. Pull your battery until you are ready to flash in Fasboot. You need to conserve. How much battery do you think you have? Or is it dead? Flashing in FB and having your phone die due to low battery is a SURE way to hard brick your A2
I have a way to charge the battery up without the phone so that's fine ill let it charge tonight and do it in the morning..
Click to expand...
Click to collapse
Axis_Drummer said:
Have you tried to fxz back to stock using RSD Lite? If not make sure your battery is charged before doing so. That should do the trick. If you have a back up try the recovery. When the Android with the exclamation comes up hit both the up and down volume keys at the same time.
I'll definatly try holding both volume keys at the same time next time, thanks!
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Oh and do you guys know what exactly caused this to happen?
Mike
It could've been caused by a number of things. The A2 is an unpredictable phone. Somethings that happen to one person may not happen to others. From my experience.
Did you make any changes to any system files or anything of the such? I see you was rooted, but did you have a custom ROM or custom recovery? I'm assuming since you tried to get to recovery and got the android on its back, that that you didn't have a custom recovery installed..
If someone knows the exact reason this happened, let us know. This is twice I've come across someone with this problem.
FXZ should work for sure though. All is well.
Sent from my MB865 using xda app-developers app
No I don't think I modified anything except rooting and installing cheesecake but I didn't use it. I don't remember having a recovery installed either.
What I did was use android recovery by pushing vol up and down and I reset it. Works fine now I lost root though so I'm going to reinstall it and reset my server on cheesecake because I can't add a motoblur account right now then uninstall it again Lol.
I really appreciate the help. I almost hate the A2. 2 phones 2 unique problems, like you said some people experience a issue that no one else has.
Sent from my MB865 using xda app-developers app
Okay, so here's a long story short. I flashed AT&T ICS leak #2 when I first got my replacement due to a brick. I ran SCV7 for a week or so and decided to try out CM10. I restored my backup of stock/rooted backup. Uninstalled highjacks, packages and app (bootmenu) itself. I then installed our OG A2 bootstrap, installed fine, installed CM10, played around with it for awhile. Realized I didnt reinstall the OG A2 Bootstrap so went ahead and did that. (without booting into recovery yet) I then later in the day decided to REBOOT my phone to only find me stuck on the CM10 boot animation. I battery pulled, plugged in to see if any recovery would show, none, just the battery charge percentage. I then battery pulled again, got into stock recovery, tried a data and cache wipe to no effect. My problem is, there is NO FXZ for the AT&T leak #2, I have no recovery besides stock and the only thing I can do is take my 32GB SD card out and add/delete files/everything. I saddly did not make a copy of the system.img but was wondering if anyone else possibly did? This would be greatly appreciated as I am stuck with a soft brick until then or a new FXZ to work with AT&T leak #2. Any suggestions or help is very much appreciated. Thanks all for reading and I'm praying for a miracle in my phone right about now lol!
DX2Trip said:
Okay, so here's a long story short. I flashed AT&T ICS leak #2 when I first got my replacement due to a brick. I ran SCV7 for a week or so and decided to try out CM10. I restored my backup of stock/rooted backup. Uninstalled highjacks, packages and app (bootmenu) itself. I then installed our OG A2 bootstrap, installed fine, installed CM10, played around with it for awhile. Realized I didnt reinstall the OG A2 Bootstrap so went ahead and did that. (without booting into recovery yet) I then later in the day decided to REBOOT my phone to only find me stuck on the CM10 boot animation. I battery pulled, plugged in to see if any recovery would show, none, just the battery charge percentage. I then battery pulled again, got into stock recovery, tried a data and cache wipe to no effect. My problem is, there is NO FXZ for the AT&T leak #2, I have no recovery besides stock and the only thing I can do is take my 32GB SD card out and add/delete files/everything. I saddly did not make a copy of the system.img but was wondering if anyone else possibly did? This would be greatly appreciated as I am stuck with a soft brick until then or a new FXZ to work with AT&T leak #2. Any suggestions or help is very much appreciated. Thanks all for reading and I'm praying for a miracle in my phone right about now lol!
Click to expand...
Click to collapse
Hey, and sort of welcome back...
But I hate to be the bearer of bad, bad news... you have a softbrick, and there is NOTHING you can do.
Next time, read everything in an OP... LOL, look who I am telling this to....
The CM10 installs come with their own CWM built in, and flashing bootstrap is what bootlooped you, so after you get another warranty replacement (yes, you HAVE to do this), I would install leak #1 ONLY, then flash cm10 with bootstrap, then do not reinstall any boot hijacks or CWM "like" recovery (bootmenu), because all you have to do it hit the vol down button right as you see the blue led flash during the M dual core logo.
Or enter the CM10 recovery menu and so on and so forth.
This is how I got out of a cm10 boot-loop.
I just restored from bootmenu backup via adb.
tcf38012 said:
Or enter the CM10 recovery menu and so on and so forth.
This is how I got out of a cm10 boot-loop.
I just restored from bootmenu backup via adb.
Click to expand...
Click to collapse
he can't, he installed bootstrap while on cm10m, so he can't get to cwm anymore.
Scratch that ----- Deleted
Well, thanks everyone. Specially you jim. Anyone wanna throw me an fxz they think MIGHT work for the second ICS leak? I'm willing to take the risk since I have nothing else to lose. Ill be most likely calling AT&T tomorrow and give some excuse. Soft brick or hard brick...Ill get a replacement...
Sent From My Eclipsed DROID X2!
DX2Trip said:
Well, thanks everyone. Specially you jim. Anyone wanna throw me an fxz they think MIGHT work for the second ICS leak? I'm willing to take the risk since I have nothing else to lose. Ill be most likely calling AT&T tomorrow and give some excuse. Soft brick or hard brick...Ill get a replacement...
Sent From My Eclipsed DROID X2!
Click to expand...
Click to collapse
I will get with alteredlikeness and see if we can possibly think of something together on this one. The first thought would be to try an mearet/searet fxz for 2.3.6 since they can fxz back with out any mods to thier 2.3.6 or 2.3.5 fxz from thier ICS leaks, but I am thinking that will still brick you, but interested to see anyhow.
So I will see if alteredlikeness and I can think of some other way to try. He or I will PM you either way.
jimbridgman said:
I will get with alteredlikeness and see if we can possibly think of something together on this one. The first thought would be to try an mearet/searet fxz for 2.3.6 since they can fxz back with out any mods to thier 2.3.6 or 2.3.5 fxz from thier ICS leaks, but I am thinking that will still brick you, but interested to see anyhow.
So I will see if alteredlikeness and I can think of some other way to try. He or I will PM you either way.
Click to expand...
Click to collapse
he can flash just a system. img from ics though, And that should recover it
Sent from my MB865 using xda premium
lkrasner said:
he can flash just a system. img from ics though, And that should recover it
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
You know, I was seeing in recovery how youbcan flash an update through sd AND system which has a lost and found folder and recovery folder. Dont know if this is of any info but either way because I wouldnt know how to put anything in system since I cant seem to get adb to recognize or moto-fastboot...I'm in a very confused state of mind and almost came to the point of hard brick but I refuse. I'll leave it up to ya devs. Thanks againg everyone.
Sent from my MB870 using xda premium
i have same issue , any way to flash system img, and where whould i get system img from? i have preiviously backed up thru cwm
justdrew said:
i have same issue , any way to flash system img, and where whould i get system img from? i have preiviously backed up thru cwm
Click to expand...
Click to collapse
Try following this:
http://forum.xda-developers.com/showthread.php?t=1926873
First Softbrick it seems In Trouble
jimbridgman said:
Try following this:
http://forum.xda-developers.com/showthread.php?t=1926873
Click to expand...
Click to collapse
Guys need your urgent help i am into a trouble what is it called technically may be a Soft brick but this is what has happened.
I was trying the Magic mod the installation went superb booted the phone it worked properly and then i used the bootstrap :silly: and tried starting the phone in recovery after which my phone is now stuck at magic mod boot animation. PLEASE HELP.
I am upto a point where have installed drivers latest rsd lite 6.0 ready with the extracted fxz 6.7.2_EDEM-18-SEARET_cfc.xml but phone is not showing up in rsd lite so that i can flash my phone. Phone says USB connected in AP Fastboot mode have a look at the attachment of my desktop. Please HELP guys....
Thanks & Regards,
Beginner Android (Ravi D)
havent you just posted this in the any question answered here thread and getting help there ??
Wow, almost forgot I made this thread lol. But sounds like your drivers need a good updating. Reboot PC after updating and try again is all I can say. Hope this helps.
Sent from my MB865 using xda premium
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