After I flashed the atrix alien port to my X2 my phone no longer recognizes my battery and will not charge it. Is anyone else having this problem? Are there any fixes to address this problem? If this has been addressed somewhere else I apologize I couldnt find it. Any help is appreciated, dont want to have to sbf back to stock.
Thanks
AW
atcbrownie said:
After I flashed the atrix alien port to my X2 my phone no longer recognizes my battery and will not charge it. Is anyone else having this problem? Are there any fixes to address this problem? If this has been addressed somewhere else I apologize I couldnt find it. Any help is appreciated, dont want to have to sbf back to stock.
Thanks
AW
Click to expand...
Click to collapse
Are you on v0.2 or v0.2.2?
when it happened to me I'd made the mistake of installing the rom over froyo
dragonzkiller said:
Are you on v0.2 or v0.2.2?
Click to expand...
Click to collapse
using v0.2.2. I just sbf'ed to 2.3.3 and am letting the batt charge again and am going to try to wipe the battery stats and see if that works. Thanks for the help, I will post my results.
Well just finished sbf'ing and flashing v0.2.2 again making sure to wipe dalvik, battery, cache, and data factory reset. Still get the battery message that says battery not recognized wil not charge.
If there are not any other ideas by tomorrow morning when I get up I will sbf again and try to download again and re-flash v0.2.2. Maybe a file was corrupt or something, I dunno.
Has anyone else had this problem?
Are you using a Motorola battery? Sometimes generics don't play well with custom roms.
Sent from my DROID X2 using xda premium
yep stock battery.
Well i have other issues other than the battery. The phone randomly goes crazy and just starts acting like I am hitting buttons, opening programs and typing random letters. I tried re-downloading the rom and re-flashing but still the same issues with the battery. I guess I will sbf back to stock and wait for another update. who knows it may be an issue with my phone since no one else seems to have this problem.
Thanks
AW
I've been using this ROM version since I released it and have yet to run into any problems you described. Is there any other information you can give me?
Sent from my DROID X2 using XDA App
Yes this happend to me. What you did was probally flashed oved 2.2. Thats a no.no. Heres the fix. RSD flash the official verizon 2.2. then root with gingerbreak. Then install custom recovery. Enter recovery mode. Wipe all. You must do this for it to work.Flash P3's pre rooted gingerbread. After install then go into recovery, wipe again then flash alien rom. It worked for me. You cant cross flash roms, they have to go into this order. 2.2, 2.3.3, 2.3.4.
Sent from my DROID X2 using, wait is that a Gorilla?
Furioustylez said:
Yes this happend to me. What you did was probally flashed oved 2.2. Thats a no.no. Heres the fix. RSD flash the official verizon 2.2. then root with gingerbreak. Then install custom recovery. Enter recovery mode. Wipe all. You must do this for it to work.Flash P3's pre rooted gingerbread. After install then go into recovery, wipe again then flash alien rom. It worked for me. You cant cross flash roms, they have to go into this order. 2.2, 2.3.3, 2.3.4.
Sent from my DROID X2 using, wait is that a Gorilla?
Click to expand...
Click to collapse
I appreciate your effort to help but this is not what happened. I flashed from the official Verizon 2.3.3, then used red lite to she back and tried again. I have tried this rom at least 4 times now everytime I get the same results.
Dragon, thanks for your willingness to help. Basically what happens is the rom v0.2.2 flashes with no errors. When the phone boots I immediately get a message saying that my battery is not recognized and that I need to install a moto battery. After I hit the ok button the phone acts like a pc when you mash on the keyboard all different apps open up, random keys get typed, when I hit the home button the programs just open back up like ten at a time. Its kinda hard to explain. When I get off work tomorrow I will try to reflash ATRIX alien and post a video of what is going on.
atcbrownie said:
When the phone boots I immediately get a message saying that my battery is not recognized and that I need to install a moto battery. After I hit the ok button the phone acts like a pc when you mash on the keyboard all different apps open up, random keys get typed, when I hit the home button the programs just open back up like ten at a time. Its kinda hard to explain. When I get off work tomorrow I will try to reflash ATRIX alien and post a video of what is going on.
Click to expand...
Click to collapse
I have seen videos of x2s doing this on youtube, probably need a new phone
Sent from my DROID X2 using XDA App
atcbrownie said:
I appreciate your effort to help but this is not what happened. I flashed from the official Verizon 2.3.3, then used red lite to she back and tried again. I have tried this rom at least 4 times now everytime I get the same results.
Dragon, thanks for your willingness to help. Basically what happens is the rom v0.2.2 flashes with no errors. When the phone boots I immediately get a message saying that my battery is not recognized and that I need to install a moto battery. After I hit the ok button the phone acts like a pc when you mash on the keyboard all different apps open up, random keys get typed, when I hit the home button the programs just open back up like ten at a time. Its kinda hard to explain. When I get off work tomorrow I will try to reflash ATRIX alien and post a video of what is going on.
Click to expand...
Click to collapse
Unfortunately, there appears to be no real solution to this. I hate to say that, but no one else is having these issues, then it must simply be a problem with your phone. I wish you luck, but there's not much I can do if your phone is acting up. I wish there was more I could do to help.
dragonzkiller said:
Unfortunately, there appears to be no real solution to this. I hate to say that, but no one else is having these issues, then it must simply be a problem with your phone. I wish you luck, but there's not much I can do if your phone is acting up. I wish there was more I could do to help.
Click to expand...
Click to collapse
Thanks for your help I don't know what the issue is, it doesn't happen on stock gingerbread just on the ATRIX rom. Thanks anyway. I will keep an eye on your dev thread and will try again when the next patch comes out.
when i was on the alien port i did not have any battery problems. did the same thing as you sbf'ed to the official verizon 2.3.3 rooted and then onto the alien rom. my friend was having some issues however and what helped him was sbf'ing to 2.2.2, then rooting, then flashing p3's pre-root gingerbread onto that. after that his phone accepted the alien rom just fine. not sure what if any difference there is between the methods but it helped him.
Yeah like I said you cAnt do that . You have to flash 2.2 first
Sent from my DROID X2 using XDA Premium App
Related
I couldnt post this there, so im posting it here
I've flashed 2 other versions of this rom successfully in the past. The only difference is this time is factory reset it first. Then attempted to flash the rom. the Rom gave me an error, and thats when the bootlooping started.
I tried factory resetting, deleting cache, leaving battery out for 30 seconds.
Im stuck at the Moto screen
SO, what do i do? is there any pertinent information im leaving out?
Your going to want to flash the sbf, full instructions are in a thread in the development section, don't have access to the link at the moment I'm mobile, sorry mate.
Sent from my DROID X2 using XDA App
ok.
Is there any way to make sure this doesnt happen again? This is such a process
You could also try plugging the phone into a wall when its off to see if you can get into BSR and either restore a backup or try to flash again.
Sent from my DROID X2
lacross said:
Is there any way to make sure this doesnt happen again? This is such a process
Click to expand...
Click to collapse
It IS a bit of a process to go thorough. Part of the price to pay if you're gonna modify, I guess. If the suggestion above about trying the BSR program (Bootstrap Recovery program, also called "System Recovery" in app drawer) doesn't work for you, then SBF to stock, which should get you back live, then flash P3 rooted Gingerbread, then Eclipse. That will work. All the links with instructions and downloads have been graciously provided here by our Moderator, The Clown.
As you already know, Eclipse has loaded fairly easily in the past, and wiping data is the recommended procedure. While not absolutly necessary, it has helped others resolve problems they had after loading Eclipse in the past, so I wouldn't be afraid to do it. It's hard for anyone to say for sure why this happened to you this time. The process is a bit touchy, reqireing you to follow the instructions exactly - including, for example, plugging in the phone to a wall charger while using the System Recovery program. Perhaps you inadvertently left out some step along the way.
I dont THINK i did, but hey, i wouldnt doubt it.
Anywho, just for an update, im now pre-rooted GB, waiting for nitro to update the eclipse rom.
Problem is now, i dont have 3g. i tried *228 multiple times
Robin M said:
...the links with instructions and downloads have been graciously provided here by our Moderator, The Clown.
Click to expand...
Click to collapse
Thats MR. Clown to you!
lacross said:
I dont THINK i did, but hey, i wouldnt doubt it.
Anywho, just for an update, im now pre-rooted GB, waiting for nitro to update the eclipse rom.
Problem is now, i dont have 3g. i tried *228 multiple times
Click to expand...
Click to collapse
Whenever I have had to sbf back to froyo, I have always done the *228 before I installed the GB update.
nitwit said:
Thats MR. Clown to you!
Click to expand...
Click to collapse
Opps.
lacross said:
I dont THINK i did, but hey, i wouldnt doubt it.
Anywho, just for an update, im now pre-rooted GB, waiting for nitro to update the eclipse rom.
Problem is now, i dont have 3g. i tried *228 multiple times
Click to expand...
Click to collapse
Reflash the sbf, activate the phone, reflash P3Droids update, wipe data/cache/dalvik from custom recovery, flash Eclipse v0.3/4 wichever now that he has a newer release.... I had to do this yesterday as I wiped when I didnt get a homescreen after flashing Eclipse.
When I am flashing eclipse for some reason I am getting a abort error for line 294?? I have downloaded the zip file twice and same problem. Any ideas??
Edit. Something is wrong Liberty X3 is showing same thing. failure at line 398 set_perm_recursive 0 0 0755 system
This sucks so bad. I can restore back to my stock 2.3.4 nano backup. Shouldn't that be as good as a fresh start like a sbf? Or will I need to try a sbf to fix what I have going on here? Ah man stock sucks!!
I was able to flash the sd flip flop and battery fix with no issues to the stock 2.3.4 But when I try to flash a rom I get errors.
I would just SBF (no biggie) unless someone with more experience with this issue replies.
X0dus said:
I would just SBF (no biggie) unless someone with more experience with this issue replies.
Click to expand...
Click to collapse
If I dont get a answer I will sbf tomorrow morning. I have a stock back up I always save. I was on Eclipse and also had back up of liberty and eclipse. However I was reading the post about custom roms do not need v6 supercharge. So I deleted my recovery of elipse and liberty and went back to stock. When I went to try and flash the roms I get errors. I can flash other things but not the rom.
I will probably sbf later tonight or first thing in the morning. Weird I swap between roms all the time never had this issue.
So did you try flashing Eclipse and/or Liberty after flashing your stock backup?
X0dus said:
So did you try flashing Eclipse and/or Liberty after flashing your stock backup?
Click to expand...
Click to collapse
Ya I tried both eclipse and liberty and they both get line errors. Hopefully the sbf does it I will have to do it tonight. I am missing eclipse with ics theme.
FIXED... I SBF to stock 2.3.4 and rooted again. Flashed the same Eclipse 1.3 zip and everything is good again. Thanks Xodus for your help!
Travisdroidx2 said:
FIXED... I SBF to stock 2.3.4 and rooted again. Flashed the same Eclipse 1.3 zip and everything is good again. Thanks Xodus for your help!
Click to expand...
Click to collapse
Good deal. np (really didn't do much)
Not the best solution, but fixed nonetheless. I tried to Google those errors and unfortunately this thread was the first to show up. Not much luck with following results given. Say, you wanna add [Solved] to the title? Helps with others with a similar issue..assuming they search and read first.
Sent from my DROID X2 using xda premium
X0dus said:
Good deal. np (really didn't do much)
Not the best solution, but fixed nonetheless. I tried to Google those errors and unfortunately this thread was the first to show up. Not much luck with following results given. Say, you wanna add [Solved] to the title? Helps with others with a similar issue..assuming they search and read first.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Got it thanks. Sorry for freaking out. I hope this can help someone else.
Still having this issue!!
So after last time I did a sbf I was able to flash Eclipse 1.3 and also Liberty X3 both and was smart enough to get them nano back up saved. Today I wanted to try another rom and had the line error again. So I went ahead and did a sbf again. After that I rooted again and then had a clean start to flash Molten 2.1 It did the same thing again. I am not sure why this is happening but luckily my back up that I saved work still. So I am going back to stock then going back to eclipse. I am puzzled now I thought the fact that I sbf and also wiped data 3 times with cache I would be good to go but not the case. I am getting scared that I will not be able to flash future roms.. I removed solved from the title since I still have the problem even after I sbf this time.
I made it back to my saved eclipse 1.3 but I really wish I knew what was going on.
I'm sorry if the answers to my question have been answered but I can't find them after searching for a few days.
I need to send my Atrix in for a repair or replacement. It is unlocked and rooted running Turl's CM9 right now. Obviously I can't send it back as is, so how should I go about everything?
Flash an SBF, flash a fruitcake rom, or something else that I haven't stumbled upon?
The only threads I could find are from a year ago and so much has changed since then. I just want to be sure I go about this the correct way. And should I go through ATT or Motorola? I know my phone is still under warranty with both.
Thanks for any help! It is much appreciated!
"Always have an exit strategy"
You can flash a fruitcake but the "unlocked" text will remain so you can hope for the best.
Or you can try an SBF (Disclaimer: at your own risk).
How long have you had it? Usually if you have had it for more than 30 days AT&T won't help but if you are still under "warranty" with them I would try AT&T first.
If you can't find a way to return your phone back to stock you can try Motorola, they might just overlook the modifications you have done.... or they might charge you a service fee...... or they might just send the phone back to you. It really depends on who ever is processing your claim and the mood they're in.
Also, please don't start multiple threads on the same topic.
http://forum.xda-developers.com/showthread.php?t=1549599
scarbutt11 said:
I'm sorry if the answers to my question have been answered but I can't find them after searching for a few days.
I need to send my Atrix in for a repair or replacement. It is unlocked and rooted running Turl's CM9 right now. Obviously I can't send it back as is, so how should I go about everything?
Flash an SBF, flash a fruitcake rom, or something else that I haven't stumbled upon?
The only threads I could find are from a year ago and so much has changed since then. I just want to be sure I go about this the correct way. And should I go through ATT or Motorola? I know my phone is still under warranty with both.
Thanks for any help! It is much appreciated!
Click to expand...
Click to collapse
OK thanks. I had read that if I use the Motorola Software Update tool it will erase the "unlocked" text. I don't know how true that is though.
And sorry about the multiple threads, its just annoying not being able to use half my keyboard in portrait. Just was hoping for some quick answers.
Thanks again for the quick response
Sent from my MB860 using XDA
I had restored a few times to stock.
I do that:
Reboot in fastboot mode and fastboot - w, fastboot erase system, fastboot erase cache, fastboot erase preinstall.
Turn phone off and pull out sim card and sd card.
Reboot in rsd mode (olding vol+ at boot) and flash your sbf with rsd lite.
That's all.
Sent from my xda premium
LeroyVold said:
I had restored a few times to stock.
I do that:
Reboot in fastboot mode and fastboot - w, fastboot erase system, fastboot erase cache, fastboot erase preinstall.
Turn phone off and pull out sim card and sd card.
Reboot in rsd mode (olding vol+ at boot) and flash your sbf with rsd lite.
That's all.
Sent from my xda premium
Click to expand...
Click to collapse
Ok, you don't happen to have a stock sbf file? I can't find one anywhere.
Also, why is it that we shouldn't flash sbf files? It seems that people have success with them but everyone keeps saying not to do that. But I can't find a stock flashable zip and the fruitcake links are dead so sbf seems to be my last resort.
I'm just stuck scratching my head because of all this confusion?
scarbutt11 said:
Ok, you don't happen to have a stock sbf file? I can't find one anywhere.
Also, why is it that we shouldn't flash sbf files? It seems that people have success with them but everyone keeps saying not to do that. But I can't find a stock flashable zip and the fruitcake links are dead so sbf seems to be my last resort.
I'm just stuck scratching my head because of all this confusion?
Click to expand...
Click to collapse
Look in the firmware superthread, in the last pages someone have a link in his sign to a page of many stock sbf files. I found there my updated one.
I always got succes with rsd lite but only with a full wipe with fastboot before it say "pass" at the end. Otherwaise it say to 'manually reboot'.
Don't know why people say "do not use sbf", probably there is a reason, but i think it is the only way to remove the 'Unlocked'
Here links to froyo sbf
and to GingerBread sbf
also you need to delete any folder about apps that need root to work and su folder and anything that presume you have rooted your phone
Sent from my MB860 using xda premium
Depending on what build you are currently on you do not want to "downgrade". So if you are on a Gingerbread build (4.5.91 or 4.5.141) do not flash the Froyo SBF. And probably if you are on the 4.5.141 build (2.3.6), it is not recommended to flash the ".91" build. That is where the issues can occur.
I have also used RSD Lite to flash back to stock (a few times) but always use caution. So, for @scarbutt11, do you happen to remember what build you were on before you unlocked the bootloader and flashed a custom ROM?
LeroyVold said:
Look in the firmware superthread, in the last pages someone have a link in his sign to a page of many stock sbf files. I found there my updated one.
I always got succes with rsd lite but only with a full wipe with fastboot before it say "pass" at the end. Otherwaise it say to 'manually reboot'.
Don't know why people say "do not use sbf", probably there is a reason, but i think it is the only way to remove the 'Unlocked'
Here links to froyo sbf
and to GingerBread sbf
also you need to delete any folder about apps that need root to work and su folder and anything that presume you have rooted your phone
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Yeah, I was running stock 4.5.91/2.3.4. I'm on a cm9 build now. I'm not sure if that will matter at all for flashing back to GB? I know I tried cm7 to see if it was just cm9 causing the problems, but it seems it is hardware related.
Sent from my MB860 using XDA
Yeah, it depends on what "Official" build you were last on. Since you were on "4.5.91" then I would just use that SBF. Like someone else mentioned, it is possible to use RSD Lite, just use caution.
scarbutt11 said:
Yeah, I was running stock 4.5.91/2.3.4. I'm on a cm9 build now. I'm not sure if that will matter at all for flashing back to GB? I know I tried cm7 to see if it was just cm9 causing the problems, but it seems it is hardware related.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Thanks so much for the help. I'll go ahead and give it a shot. I'll let y'all know the outcome.
Sent from my MB860 using XDA
Took a little pulling of my hair while I waited but fastboot wipe and then flashing the stock sbf worked like a charm. I am back on stock GB, the unlocked text is gone and now I can hopefully get my phone fixed or replaced.
Thank you so much @live4nyy and @LeroyVold!!! Without you guys I would have been still scratching my head. I owe you both big time
No problem man, i need to do the same.
my touchscreen is more and more often unresponsive, so i'm flashing my stock sbf as i write.
Finally got a chance to swing by the AT&T store. They replaced the phone no problem thanks again guys!
Sent from my MB860 using XDA
i need to do the same. im sending this phone in and already got my new atrix sitting here.
Freaking Motorola phones, they break without you even touching them. I gotta figure out how to send mine to att as well.
u need to do a write up in here of how u did it. it might be redudant to some but to others like myself, it will be like having my hand held doing a scary process...your guidance as having it done yourself would help...with a how to..
scarbutt11 said:
Finally got a chance to swing by the AT&T store. They replaced the phone no problem thanks again guys!
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Free or did you have to pay?
LeroyVold said:
I had restored a few times to stock.
I do that:
Reboot in fastboot mode and fastboot - w, fastboot erase system, fastboot erase cache, fastboot erase preinstall.
Turn phone off and pull out sim card and sd card.
Reboot in rsd mode (olding vol+ at boot) and flash your sbf with rsd lite.
That's all.
Sent from my xda premium
Click to expand...
Click to collapse
this isnt working for me. and i need to send my phone in within a day.
Atrix_Owner said:
Free or did you have to pay?
Click to expand...
Click to collapse
For free, I bought the phone through them less than a year ago. All I said was that the screen was unresponsive and they looked at it for less than 10 minutes and then said they would replace it for me.
jahizen said:
u need to do a write up in here of how u did it. it might be redudant to some but to others like myself, it will be like having my hand held doing a scary process...your guidance as having it done yourself would help...with a how to..
Click to expand...
Click to collapse
Thats not a bad idea. I have never done one before but now that I'm thinking about it I am sure there are others that need to do what I just did. I will try to write one up in the next few days. Thanks for the idea!
live4nyy said:
Depending on what build you are currently on you do not want to "downgrade". So if you are on a Gingerbread build (4.5.91 or 4.5.141) do not flash the Froyo SBF. And probably if you are on the 4.5.141 build (2.3.6), it is not recommended to flash the ".91" build. That is where the issues can occur.
I have also used RSD Lite to flash back to stock (a few times) but always use caution. So, for @scarbutt11, do you happen to remember what build you were on before you unlocked the bootloader and flashed a custom ROM?
Click to expand...
Click to collapse
hello i guess you could help me with a doubt i have..i used to be on stock 4.5.141 Gb 2.3.6 atrix 4g..im new on this things..and i installed succesfully cm7.2 but its not stable as i expected..i wanna go back to stock rom but im not sure what to do...i tried to go back using CWM restore...¨yes i made my backup before everything¨ but the restore didnt work...its stuck on moto booting logo..then i had to install again cm7 but the ba2tf wich its a bit more stable but not enough comparing to stock i had.. then my question its...
should i flash my phone with sbf 4.5.141?? or what do you recommend me..i dont wanna make a downgrade just be at 4.5.141 again
thanks
Okay, so I was going to install the new cm9 alpha rom that was released. But every time I try to BSR; superuser denied the permission. Even though I have it set to allow it.
But what I though was weird was that if I powered my phone off. Then plugged it into a charger, that the BSR screen appeared. So I made a nandroid recovery of my 2.3.5 OS and then tried to flash cm9. But then it started to give me errors. So I then was gonna just recover the nandroid backup since I factory reset and clear cache. but then it froze trying to recover.
Then I though that I should just power back on my phone then try it again. So I did that and now the BSR screen won't appear it just shows the motorola logo and stays there. HELP!!
I think we will need clarification of your abbreviations before we can help you. Do you mean, SBF or BSR. SBF means you use RSDLite to re-flash your phone to a stock state, and BSR is your Boot Strap Recovery. Unless I'm missing something.
Sent from my DROID X2 using XDA
BSR sorry...
Have you tried holding down the volume button when you power up, plugged into the wall? That should get you into Android Recovery. I believe you may see a lil Droid with a triangle. Then press both volume up and down at the same time. Your menu should appear.
The first problem I saw when reading the OP was that you need to be on 2.3.4 to flash CM9.
jsgraphicart said:
The first problem I saw when reading the OP was that you need to be on 2.3.4 to flash CM9.
Click to expand...
Click to collapse
Totally... right...
You will throw so many errors running 2.3.5 kernal ( which only goes back to 2.3.4 with an sbf)
Sent from my MB870 using Tapatalk 2
6Flip9 said:
Totally... right...
You will throw so many errors running 2.3.5 kernal ( which only goes back to 2.3.4 with an sbf)
Sent from my MB870 using Tapatalk 2
Click to expand...
Click to collapse
Yeah i sbf back to 2.3.4 and had to re-root my phone and start all over. So everything is working fine. I think the problem was that I updated to 2.3.5 and it unrooted me but still had the superuser.apk installed but not let me have su permission. eather way I fixed it.
I am posting this here since I have under 10 posts and cannot post in the dev section.
I have a Droid X2 that is rooted and flashed to Eclipse 2.2.1
I have a nandroid backup on my SD card, but cannot get into a screen to restore it.
I have had it flashed and working for a few days now. The phone turned off in my pocket, and when I turned it back on, it loads up to the Eclipse animation but never goes any further.
I have searched Google and cannot find an exact scenario. I have found people who fixed by going back to stock SBF, but this did not work for me.
I have tried both 2.3.3 and 2.3.4 and am using RSD Lite 5.4.4.
The phone will reboot after it "finishes" and get stuck in the Eclipse animation again.
I have done a data/cache wipe through Android Recovery with no result. I have cleared it more than once just to be sure.
Wow, sounds like you tried about everything and I'm shocked nothing has worked. I would try the 2.3.5 ota sbf (in development section) but that may not work either.... If it were me I would at least try it. I would also try re downloading the rsd lite program. Are you unzipping before flashing the sbf file?
Sent from my MB870 using xda premium
alittlex said:
I am posting this here since I have under 10 posts and cannot post in the dev section.
I have a Droid X2 that is rooted and flashed to Eclipse 2.2.1
I have a nandroid backup on my SD card, but cannot get into a screen to restore it.
I have had it flashed and working for a few days now. The phone turned off in my pocket, and when I turned it back on, it loads up to the Eclipse animation but never goes any further.
I have searched Google and cannot find an exact scenario. I have found people who fixed by going back to stock SBF, but this did not work for me.
I have tried both 2.3.3 and 2.3.4 and am using RSD Lite 5.4.4.
The phone will reboot after it "finishes" and get stuck in the Eclipse animation again.
I have done a data/cache wipe through Android Recovery with no result. I have cleared it more than once just to be sure.
Click to expand...
Click to collapse
Not for nothing, but keeping your phone in your pocket in summer heat could have possibly damaged some internal hardware.
Just to keep this simple, I would let the phone sit, perform an sbf to 2.3.4 following any of the guides here. Also try tee downloading the sbf file. When you power off your device...plug it in...then hold volume down and power button what happens?? It should say Fast boot on the to of the screen of your phone....I'm reading as I'm typing and thinking something else is wrong, I would not want to steer you wrong, but sbf works...always, like more then a thousand times....so it may be hardware that is the issue.
Sometimes when SD cards are corrupt they cause issues also, but that you would see in cwr...
Do you have insurance?
Inserted 20¢ for the first three minutes
Maybe a different sbf method could work? You could try the ez sbf http://www.droidxforums.com/forum/droid-x2-hacks/41697-tool-ezsbf-dx2.html
Sent from my MB870 using Tapatalk 2
I am unzipping the sbf file. I have had previous experience with RSDLite since the the days of the Razr flip phone.
I don't think it could be a corrupt download, because the SBF does unzip. Not to mention the fact that I've tried 2.3.3 AND 2.3.4... to completely different files.
In my pocket in the summer heat doesn't really apply when I'm inside all day. I did not have my otterbox on the phone when this happened.
I can hold the buttons and get into the menu for RSD/fastboot/recover.
The android recovery will clear the data and cache, but it just gets stuck in the boot animation and doesn't progress. I let it sit trying to load for over an hour with no luck.
I have also tried booting without an SD card.
There is no insurance on the phone. I bought it off Craigslist for $100 and I use it on Cricket.
This is the first time I've had a problem with the phone, and it's such a weird problem, I had to sign up and get input.
I will try to SBF again now that I have had the phone off for a few hours.
EDIT: Did not fix. Even SBF to 2.3.5 still keeps the eclipse boot animation.
raymond513 said:
Maybe a different sbf method could work? You could try the ez sbf
Sent from my MB870 using Tapatalk 2
Click to expand...
Click to collapse
I tried running the ezSBF through USB boot, it went through the whole process (CQ60 and CQ65 took a long time). When the phone boots up, it still shows the eclipse animation and just loops it.
I held down power and vol-down, I can still get into the Android Recovery to wipe data and cache... but it doesn't help.
Did you ever get anything to work? I wonder if you could push something using adb? I am not familiar enough with it to help and not sure it would help. I feel like there has to be a solution to this but don't know what it could be? Bump.....
Sent from my Xoom using xda premium
You keep saying that after an SBF, you get the eclipse animation. When you SBF you should get the droid animation since it is putting it back to stock. If you are still getting the Eclipse animation then it didnt work right and didnt SBF. Did the SBF actually say it completed successfully?
There enlies the problem. It will go through every stage and go to reboot and get stuck in the eclipse boot animation. It will tell me to manually power up my phone, and when I do, it will say finished.
SBF is supposed to overwrite everything, but it just doesn't. I have tried it using the RSDLite app and the Linux boot.
I have never read about anyone else having this problem, and I have been looking for a solution since Tuesday afternoon.
I am not familiar with ADB, but I will read into it.
I use linux all the time never used rsd of any kind on it I have the files you will need on linux if you need them just let me know.
http://db.tt/pvs1M7vx
Link above for the flash tool
Here is a guide of how your suppose to use ithttp://forum.xda-developers.com/showthread.php?t=1321061
Let me know if this works for you or if you need help.
I just read your post again thought you said that you were using rsd in linux. My bad. Hopefully you get everything figured out. I would delete and redownload everything including rsdlite and try again. I've flashed at least a hundred sbfs in linux and never had a problem yet
I run Windows 7. I used the Linux DroidX2 boot disk. It went through all the stages, but still no dice. I tried it twice.
Im sad for you. Other than redownloading all your files and trying again I don't know what other options there are for you. Maybe you could find a way to flash something using fastboot?
Sent from my DROID X2 using xda premium
Would someone let you sbf from their computer? Maybe your pc and phone aren't getting along?
Sent from my MB870 using xda premium
try a different usb cable, even if it works for other devices, it could be the problem
Sent from my DROID2 using xda premium
I would assume the original Motorola eco cable would be the one that works.
I have another data cable that I can use, I just haven't tried it.
There is not a whole lot of information out there on how fastboot works. It's always RSD support and SBF flashing.
alittlex said:
I would assume the original Motorola eco cable would be the one that works.
I have another data cable that I can use, I just haven't tried it.
There is not a whole lot of information out there on how fastboot works. It's always RSD support and SBF flashing.
Click to expand...
Click to collapse
Yeah I did some digging couldn't find a fastboot file for dx2. But you can wipe data and cache with it. I would suggest the same try different computer, cable, and files. Probably your only hope. Have you sbfed the phone successfully before?
Sent from my DROID X2 using xda premium
I'm wondering if more than just turning off happened in the pocket? Too bad we'll never find out.
My DX2 was rooted and running eclipse. I've SBFed it to do that. Before that, I was running stock 2.3.5 with all the edits to put it on Cricket instead of Verizon.
I can't figure out what happened inside my pocket. I was using it one minute, put it in my pocket and went outside for a smoke, took it back out and it was turned off.
I don't get any boot error messages. It just won't erase Eclipse when it SBFs.
I can still hold power + volume down and scroll through all the menus.
I hooked it up to my laptop and it sees the ADB.
Unfortunately, the go-to is always SBF and nobody says anything about flashboot.
Try a different computer yet? What happens when you pull the battery and plug into the wall?
Sent from my DROID X2 using xda premium
I only have one computer.
And what do you mean, pull the battery and plug it in the wall? Leave the battery out and plug it in?