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?
Related
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
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
My X2 starting losing signal. Today I did a hard reboot and when the phone comes back on it makes it to the black screen with the Motorola logo and says Modem did not power up (2) starting RSD protocol support. Verizon is sending me a warranty replacement. I have already done a factory reset. Phone was rooted would the factory reset erase the root so that it's safe to send back.
Phone was rooted with Pete's root tool.
redfish10 said:
My X2 starting losing signal. Today I did a hard reboot and when the phone comes back on it makes it to the black screen with the Motorola logo and says Modem did not power up (2) starting RSD protocol support. Verizon is sending me a warranty replacement. I have already done a factory reset. Phone was rooted would the factory reset erase the root so that it's safe to send back.
Phone was rooted with Pete's root tool.
Click to expand...
Click to collapse
try dialing *228 option 2 This will reconfigure your signal from cell towers
http://support.verizonwireless.com/faqs/Wireless%20Service/faq_prl_preferred_roaming_list_update.html
I tried that. The phone will not make it past the black screen with the Motorola logo. And I get the modem message across the top.
Sounds like the radio is burned out. No fix for that unless you want to break out the soldering iron
That's what I figured. I have another phone on the way. I was able to do a factory reset. Would this remove the root. Phone was rooted with Pete's one click root tool.
Sending phone back so I have to make sure root is removed.
redfish10 said:
Sending phone back so I have to make sure root is removed.
Click to expand...
Click to collapse
I think there's an app for that
I know but my phone is useless right now. I can't see anything but the black boot screen.
Sbf and send it in. Problem solved
Sent from my GT-P3113 using xda premium
SBF = wipe everything. This is like doing a total factory reset; it clears and re-writes almost every partition. Root access would be wiped out from it.
****@Reddish****
Try resetting ur super user
Go to app manager and clear data I found that to be my problem in the past and then turn off ur x2, not reset your phone. Than repower.
Hope it works.
What are you running?
Sent from MB870 W/ Cm7.2 Rc1 MASHUP V2
SUCESS I THINK YES...
Dudes stuck @ red m. No way to reset superuser. Have to SBF.
Sent from my MB870 using Xparent Cyan Tapatalk 2
Omega360 said:
SBF = wipe everything. This is like doing a total factory reset; it clears and re-writes almost every partition. Root access would be wiped out from it.
Click to expand...
Click to collapse
Not ENTIRELY true.
While flashing a sbf file using RSDlite, you are setting all the system and proprietary things back to completely stock. It will remove root access, and all that junk, along with all, the things that came from mods/tweaks/hacks/roms
BUT flashing sbf BY ITSELF alone will NOT wipe away ANY user data. You MUST data wipe from stock recovery to do that. This is why sometimes you boot loop,after sbf flash , and you need to data wipe to cure those boot loop blues, cuz sometimes there are things left over that you tweaked that didn't get wiped out after flashing the sbf, but they get removed from a data wipe from stock Android recovery.
To sum up:
For a TRUE OUT OF BOX FACTORY CONDITION(i.e. You just bought and opened the box) MUST flash sbf file using RSDlite with a computer. AND THEN after that, you wipe data/cache from stock Android recovery.
I'm willing to bet that would have also fixed you issues with not being able to boot past Motorola screen as well. Cant hurt to get a new one, but if you can compare them to see which is in better working order, then it couldn't hurt to do.
Either way, if youre going to send it in, and want to erase traces of root and such, then you need to do more than just data wipe. You NEED to sbf AND data wipe.
From my nexus tappin the talk
<edit post successful>
That's why I said ALMOST every partition
Just do recovery...
Pull your battery/replace
And plug it in... to the wall that is
Screw an sbf
Sent from MB870 W/ Cm7.2 Rc1 MASHUP V2
SUCESS I THINK YES...
Modem Did Not Power Up (2)
ashclepdia said:
I'm willing to bet that would have also fixed you issues with not being able to boot past Motorola screen as well. Cant hurt to get a new one, but if you can compare them to see which is in better working order, then it couldn't hurt to do.
Either way, if youre going to send it in, and want to erase traces of root and such, then you need to do more than just data wipe. You NEED to sbf AND data wipe.
<edit post successful>
Click to expand...
Click to collapse
This is absolutely true. The error "Modem did not power up (2)" is something that I have been dealing with as well. I'd love to work with someone to figure out the problem, but it is probably not hardware. I encountered this error for the first time 2 weeks after installing Eclipse 2.2.1. I solved it by SBF to Stock. Once I had re-installed a stock ROM the error went away and the phone operated normally. I just had this error pop up again almost exactly 2 weeks after installing CM7 RC1. When I get home I'm going to SBF to stock and hopefully that will correct the issue (again). I tried clearing my cache and then clearing my data through stock recovery, but that won't correct the error - and unfortunately the error happens before BSR boots so I can't Nandroid back to a healthy setup and see where the problem is. Both times I lost signal on the phone, re-booted, and then got stuck at the Red M with the Modem error. :crying:
I'm going to try to load CM7 again, but it's pretty awful to have this happen at work and suddenly be without a functional phone. (Maybe I have to install RSD Lite on my work computer ...)
Any thoughts on this would be appreciated but I can tell you that ashclepdia is right, it is probably not a hardware problem. It seems to be a problem with rooting/flashing on certain handset builds.
okay i have an mx2 2.3.6 rooted and rerecovery installed flashed miui 4 everything was fine until i played around with motomizer and adjusted the lcd density now the miuihome has stopped and will not let me get to my apps i can use sms somewhat and get to the browser using the statistics opt in message i have tried to recover but it doesnt boot into it even though i flashed rerecovery i have done a fatctory data reset in android recovery nothing helps i even tried to sbf back to 2.3.5 and the flash fails any ideas how to fix it. this is my 2nd one already warranted it out once.
okay i have tried everything i know with no luck. i can use the phone to receive calls and texts just cannot send either. can use the voice search to get to the browser. still cannot load the screens just get miuihome has stopped message. i somehow lost the recovery and cannot get back into it to do anything. i used the android recovery to wipe data and cache with no luck. ive tried to use adb and fastboot to flash things with no luck. im really at my wits end. no sbf files will work
flash fails either it wont enumerate or product id fails im using rsd lite. i love this phone and miui but this sucks and i know its my fault for tweaking stuff but there doesnt seem to be an answer. any help is greatly appreciated.
if there is no solution oh well.....:crying:
ionicone said:
okay i have an mx2 2.3.6 rooted and rerecovery installed flashed miui 4 everything was fine until i played around with motomizer and adjusted the lcd density now the miuihome has stopped and will not let me get to my apps i can use sms somewhat and get to the browser using the statistics opt in message i have tried to recover but it doesnt boot into it even though i flashed rerecovery i have done a fatctory data reset in android recovery nothing helps i even tried to sbf back to 2.3.5 and the flash fails any ideas how to fix it. this is my 2nd one already warranted it out once
Click to expand...
Click to collapse
If you can boot into RSD try sbf for 2.3.4 or even back to 2.3.3. I had issues before with 2.3.4 not performing a clean sbf. It would say it was completed but it would not wipe the phone. But when I would sbf 2.3.3 it would work fine. Worth a shot.
bump
bump for help
ionicone said:
bump for help
Click to expand...
Click to collapse
Can you only see part of the screen? If you hit your home button, what do you see?
Sent from my MB870 using xda premium
Travisdroidx2 said:
If you can boot into RSD try sbf for 2.3.4 or even back to 2.3.3. I had issues before with 2.3.4 not performing a clean sbf. It would say it was completed but it would not wipe the phone. But when I would sbf 2.3.3 it would work fine. Worth a shot.
Click to expand...
Click to collapse
Mx2 brother
DROID DOES, Apple did...like I forgot when
try this power down your phone then hold the power and volume down buttons until fast boot shows up on the top of the screen then push the volume down button down 7 times to android recovery then reflash miui 4 then factory restore and all that
Shpoople said:
try this power down your phone then hold the power and volume down buttons until fast boot shows up on the top of the screen then push the volume down button down 7 times to android recovery then reflash miui 4 then factory restore and all that
Click to expand...
Click to collapse
This should work. Reflash the from and it should cancel out you dpi settings.
Sent from my MB870 using xda premium
CadenH said:
This should work. Reflash the from and it should cancel out you dpi settings.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
I thought you could only install signed packages in the stock recovery. Is this different with the MX2?
nothing works
cant flash anything from stock recovery other than signed packages. is there anyway to flash a recovery from adb or fastboot. i can get to both of them along with rsd but cannot sbf as i have found out i have an mx2 stock with 2.3.6 and cannot sbf down to anything else. im reeally stuck here.
ionicone said:
cant flash anything from stock recovery other than signed packages. is there anyway to flash a recovery from adb or fastboot. i can get to both of them along with rsd but cannot sbf as i have found out i have an mx2 stock with 2.3.6 and cannot sbf down to anything else. im reeally stuck here.
Click to expand...
Click to collapse
You cant flash anything using the stock recovery. You need a custom recovery. I dont know what the milestone x2 uses, but if its the same as the Droid X2, its the bootstrap recovery.
i cant get to my apps to run the recovery app. i really dont know what to do at this point, but i can use the phone to receive calls and text just cant make any because i error saying phone or messaging has stopped. can i flash the bootstrap in fastboot or adb i have tried but not real proficient with either.
okay done some reading im using rsd lite 5.4.4 and have been trying to flash the zips, just read the i must extract it first. is this so....
ionicone said:
i cant get to my apps to run the recovery app. i really dont know what to do at this point, but i can use the phone to receive calls and text just cant make any because i error saying phone or messaging has stopped. can i flash the bootstrap in fastboot or adb i have tried but not real proficient with either.
Click to expand...
Click to collapse
Someone else chime in if its different for the Milestone X2.
ionicone, bootstrap is not a flashable zip. it is an .apk file (app). Put it on your sd card and install it like a normal app. Then open it and follow the directions. I don't know how different the Milestone X2 is from the Droid X2 but thats how what we use and thats how we do it.
I may be misunderstanding but if nothing else works, SBF and start over.
---------- Post added at 12:13 PM ---------- Previous post was at 12:10 PM ----------
And SBF should work as long as you can get into the normal recovery mode. I dont know why else SBF files wouldnt work for you.
i may not be very clear on my problem, but i cant install anything on the phone because of the error message it wont go away just says miuihome has stopped. everything i try to sbf through rsd lite fails but im in the process of extracting and trying that one has already failed trying another now.
ionicone said:
i may not be very clear on my problem, but i cant install anything on the phone because of the error message it wont go away just says miuihome has stopped. everything i try to sbf through rsd lite fails but im in the process of extracting and trying that one has already failed trying another now.
Click to expand...
Click to collapse
What exactly did you change to make this happen in the first place?
If it was just the LCD density, try pushing the original build.prop file into the system folder. Since, I believe thats where the DPI is controlled. Or if you can get into with root explorer or something, change it back manually.
it was the lcd density property. can i rip this from the backup i have stored on my pc and push it through adb.
as far as sbfing this is what my phone says
SVF:106:2:3
sec_exception: b655, eddc, eb
thanks for replying btw
ionicone said:
it was the lcd density property. can i rip this from the backup i have stored on my pc and push it through adb.
as far as sbfing this is what my phone says
SVF:106:2:3
sec_exception: b655, eddc, eb
thanks for replying btw
Click to expand...
Click to collapse
You should be able to. Just make sure the permissions are rw-r--r--
You can get it from your backup or pull it from the ROM you flashed
Why don't you just factory restore and cache then reboot from the menu and it should be fixed
Sent from my MB870 using xda premium
tried that it does nothing, and now after trying to flash stuff through fastboot i may have bricked it. going to cspire today to see if i can warranty this one out.
update
cspire will let me warranty this one out, i will not root again until things are more stable as in an unlocked bootloader. thanks to everyone that tried to help.
They won't unlock the bootloader for a long time so don't get your hopes up and wasn't this your own fault?
Sent from my MB870 using xda premium
ionicone said:
cant flash anything from stock recovery other than signed packages. is there anyway to flash a recovery from adb or fastboot. i can get to both of them along with rsd but cannot sbf as i have found out i have an mx2 stock with 2.3.6 and cannot sbf down to anything else. im reeally stuck here.
Click to expand...
Click to collapse
http://www.droidxforums.com/forum/droid-x-help/5581-lcd-density-changer-problems-droid-2.html
maybe this helps " If your rooted go into root explorer and open System > Build.prop in text editor. Find the line labeled ro.sf.lcd_density= and change it to 240." from: Doahh droidx forums
It's the first response to the thread.
Good luck!
Edit-------------
Looks like Im a bit late
Since the last time I flashed CM7, RSD (any version) with any SBF file doesn't wipe my phone the way it used to. It's gotten to the point I can no longer flash custom ROMs. If I don't wipe data/cache first, it will flash a new SBF yet leave the apps that were on it before hand. And when I try to flash a custom ROM, I get an error every time. Did I mess up something down in the locked areas that can never be fixed? Is there another way to wipe the phone to a more original or basic point? Right now I'm completely wiping the int and ext sd-cards, wiping data/cache/dalvik, SBFing to 2.2.2, and OTAing back up to see what happens, though I'm doubting it will help.
edit: Didn't work. Still can't flash a custom ROM. I can run rooted stock 2.3.5 though, guess that's what I'm stuck with. Better than nothing.
Performing an SBF does not wipe any user data from the phone. Wipe the phone using the stock recovery before performing the SBF. There are many threads on here on how to SBF, root, and install your favorite ROM.
RyanThaDude said:
Performing an SBF does not wipe any user data from the phone. Wipe the phone using the stock recovery before performing the SBF. There are many threads on here on how to SBF, root, and install your favorite ROM.
Click to expand...
Click to collapse
It doesn't matter if I wipe everything or not, I still can't flash a custom ROM. Get an error every time, and have to SBF to get it bootable again. I had weird issues the first time I ran CM7 and tried to SBF back to stock. Took multiple battery pulls and random button pushing while rebooting before I could get it back into RSD mode. This last time let me SBF back fine, but I get the PASS result instead of the REBOOT PHONE MANUALLY now and can't flash anything.
Scur827 said:
It doesn't matter if I wipe everything or not, I still can't flash a custom ROM. Get an error every time, and have to SBF to get it bootable again. I had weird issues the first time I ran CM7 and tried to SBF back to stock. Took multiple battery pulls and random button pushing while rebooting before I could get it back into RSD mode. This last time let me SBF back fine, but I get the PASS result instead of the REBOOT PHONE MANUALLY now and can't flash anything.
Click to expand...
Click to collapse
Try this a files sometimes corrupt.
Download all new. Perform the sbf, while the phone reboots do the volume down power button thing to get into Android Recovery. Once there wipe data and cache....
I have about 10 cables in my house...only two or three work for flashing and such...try a different cable....
DROID DOES, Apple did...like I forgot when
Pixelation said:
Try this a files sometimes corrupt.
Download all new. Perform the sbf, while the phone reboots do the volume down power button thing to get into Android Recovery. Once there wipe data and cache....
I have about 10 cables in my house...only two or three work for flashing and such...try a different cable....
DROID DOES, Apple did...like I forgot when
Click to expand...
Click to collapse
I have a couple good cables that always work, tried them both. Wiped data and cache on SBF reboot, too. Rooted with One click and Pete's both. So far, nothing works.
are you sure, sbf is flashing correct?
try different version like 2.2.3 or 2.3.5
and check system info after to verify
then update.zip or flash 2.3.4 sbf
or try ezsbf to flash and/or root
Sent from my MB870 using xda premium
i've seen usb cables work with one device and not another, can be hard to tell
Sent from my MB870 using xda premium
sd_shadow said:
are you sure, sbf is flashing correct?
try different version like 2.2.3 or 2.3.5
and check system info after to verify
then update.zip or flash 2.3.4 sbf
or try ezsbf to flash and/or root
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
I've tried 2.2.2, 2.3.3, and 2.3.4 all, then updated. I've tried 3 different versions of RSD. Exact same result. Haven't heard of ezsbf though, I'll check it out.
http://www.droidxforums.com/forum/droid-x2-hacks/41697-tool-ezsbf-dx2.html
it's an iso file you burn to cd or thumb drive, reboots pc to a Linux os
with options to flash sbf and root with zergrush
works for some, when rsd lite or rooting failed
Sent from my MB870 using xda premium
... Have you thought that maybe the recovery your using is corrupted? Download that apk again (the plain one not the patched cm7/9 version) and give that
Sent from my MB870 using xda app-developers app
Scur827 said:
Since the last time I flashed CM7, RSD (any version) with any SBF file doesn't wipe my phone the way it used to. It's gotten to the point I can no longer flash custom ROMs. If I don't wipe data/cache first, it will flash a new SBF yet leave the apps that were on it before hand. And when I try to flash a custom ROM, I get an error every time. Did I mess up something down in the locked areas that can never be fixed? Is there another way to wipe the phone to a more original or basic point? Right now I'm completely wiping the int and ext sd-cards, wiping data/cache/dalvik, SBFing to 2.2.2, and OTAing back up to see what happens, though I'm doubting it will help.
edit: Didn't work. Still can't flash a custom ROM. I can run rooted stock 2.3.5 though, guess that's what I'm stuck with. Better than nothing.
Click to expand...
Click to collapse
The reason why you can't flash custom ROMs such as CM7 or CM9 is that you keep going to 2.3.5 or maybe even trying on 2.2.2 or 2.3.3. I have a check to prevent you from using any version besides 2.3.4. Restoring a nandroid won't cut it either. You must SBF back to 2.3.4, wipe data/cache, root (using zergRush or Pete's Root Tools), install the unpatched BSR, and flash CM7 or CM9.
As for why your apps show up still after an SBF, like you said, you didn't wipe data/cache and the apps are stored in the data directory on your phone. An SBF does not wipe data or cache.
LordRalh3 said:
... Have you thought that maybe the recovery your using is corrupted? Download that apk again (the plain one not the patched cm7/9 version) and give that
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
That's the only thing I haven't tried I think, I'll give it a try. Good idea.
Droid X2 > Eclipse 2.2.1 > Tapatalk
dragonzkiller said:
The reason why you can't flash custom ROMs such as CM7 or CM9 is that you keep going to 2.3.5 or maybe even trying on 2.2.2 or 2.3.3. I have a check to prevent you from using any version besides 2.3.4. Restoring a nandroid won't cut it either. You must SBF back to 2.3.4, wipe data/cache, root (using zergRush or Pete's Root Tools), install the unpatched BSR, and flash CM7 or CM9.
As for why your apps show up still after an SBF, like you said, you didn't wipe data/cache and the apps are stored in the data directory on your phone. An SBF does not wipe data or cache.
Click to expand...
Click to collapse
I haven't tried to flash CM7 or CM9 since the last time I came off of it. I really like having the camcorder around my daughter. That was my only problem with either. they worked great when they were on. I've mostly been trying to get Eclipse back on.
I think that CM7 had something to do with my problem, though. I've flashed it twice before. The first time was hell coming back to stock, I thought my phone was bricked for about an hour. It took multiple boot attempts, battery pulls, and button mashing before I finally could get back to RSD mode to flash a SBF.
Everything seemed fine for a couple months, until I tried CM7 once again. When I tried to come back off of it the second time, RSD gave it a PASS at the end instead of hanging on REBOOT PHONE MANUALLY like it always did before, and has every time since then (was hit and miss before). Now I can still flash a SBF and update an OTA (but only after doing a *228 to download and install it, can't flash an OTA file from recovery), but if I try to flash any ROM (and I've tried a half dozen of them) while using any root method, I get an error while flashing, and have to wipe everything possible to be able to SBF back to stock. I've tried flashing ROMs at least 20 times over the past few days. Either something got messed up, somewhere in an area that both RSD and recovery don't touch, or it's a hardware issue. That's the only thing I can come up with.
Now, I don't believe it's CM7's fault. At all. There are just too many people who enjoy. I simply believe there was something odd or wrong about my phone.
Its like you know the words but not which ones go with what things... Flashing and sbfing are two completly different things, and there is no button mashing involved pull your battery one time, hold power and volume up at the same time, that puts you in rsd mode to sbf, to get over a bootloop just go to android recovery (power button and volume down then cycle to recovery) you don't flash roms in this recovery just wipe data/cache. If you grabbed the right sbf file (check your android version in about phone should be 2.3.4 ) you can root with motorola one click and install the bootstrap recovery program NOT THE CM7 VERSION, Plug phone into the wall bsr WIPE DATA/CACHE and flash cm7, its a standard process and your phone is not special
Sent from my MB870 using xda app-developers app
LordRalh3 said:
Its like you know the words but not which ones go with what things... Flashing and sbfing are two completly different things, and there is no button mashing involved pull your battery one time, hold power and volume up at the same time, that puts you in rsd mode to sbf, to get over a bootloop just go to android recovery (power button and volume down then cycle to recovery) you don't flash roms in this recovery just wipe data/cache. If you grabbed the right sbf file (check your android version in about phone should be 2.3.4 ) you can root with motorola one click and install the bootstrap recovery program NOT THE CM7 VERSION, Plug phone into the wall bsr WIPE DATA/CACHE and flash cm7, its a standard process and your phone is not special
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
Fine, I don't FLASH an SBF file. But I've flashed ROMs on the X2 alone at least a hundred times, I know what's what. I know the difference between stock recovery and BSR. I know the difference between BSR and the CM7 version, and when to switch over. I know what wiping data does, what wiping cache does, what the Dalvek cache is and what wiping it does, what fixing permissions really does.
When I say I couldn't SBF out of CM7, I mean after flashing CM7 the first time, I ran RSD Lite and used SBF 2.3.4-380 to get back to stock. RSD gave me an error, and stopped. I couldn't reboot the phone, it just hung up on the red M. Holding vol down+power hung up on the red M. Holding vol up+power hung up on the red M. So I would pull the battery and try it again. And again. And again. No buttons, every button. Letting it sit on the red M for 30 mins. Eventually I got a weird RSD message at the top (and no, not the vol up+power RSD message), different from the others, and I could SBF again. I still got an error, but could vol down+power into the regular menus, so once I got into the standard RSD mode the next SBF went fine, except I got a pass at the end instead of having RSD hang up on the reboot phone manually message it always got before. And since then I don't get the boot loops after it reboots like it used to, though the pass message is hit and miss. I've SBFed dozens and dozens of times since then, used fresh downloads and different versions of everything, and I've never seen another boot loop afterwards. Something, somewhere, is definitively different. I have a few good cables that have always worked, and I've switched them out. I've wiped and formatted everything possible on the phone several times. It's just not the same as it was before CM7. And after coming off of CM7 the second time, I've gotten a pass at the end of the SBF every single time. Another new thing after a CM7 flash.
Like I said, I don't think it's a CM7 issue, I just think there is something wrong with my phone on a level I can't touch, and it really didn't like CM7. It isn't operator error. Give me any instructions you like for getting me on, say, Molten (since it's 2.3.4-380 and the simplest to flash). I'll follow them to the T, but it won't work. I can't *228 anymore, so I can't download a system update, and I get a file signature error if I try to flash an update from stock recovery. I'm stuck on stock 2.2.2, 2.3.3, 2.3.4, or 2.3.5. I can still root them using any method, except 2.3.5 since it requires carrying root over with OTA Rootkeeper from 2.3.4.
Sorry if i came off too negatively btw its just that this phone is SOOOOO close to indestructible programming wise... Your next step is to burn ezsbf and head to someone elses computer and try that
Sent from my MB870 using xda app-developers app
LordRalh3 said:
Sorry if i came off too negatively btw its just that this phone is SOOOOO close to indestructible programming wise... Your next step is to burn ezsbf and head to someone elses computer and try that
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
Me too, just woke up.
I tried ezsbf yesterday on a laptop, no change. Tried a fresh copy of BSR from a different source this morning, no luck there either. I'm completely out of ideas now, there's nothing I haven't tried alternatives to. But I have a fully functional phone rooted on 2.3.4, and sometime in the near future I'll be getting something new and shiny, so it could be worse. When I do get a new one, this one will be perfect to have GrooVe IP on it for my 8 yr. old daughter, and the big screen is nice for games.
Droid X2 > Eclipse 2.2.1 > Tapatalk
Scur, I uploaded a nandroid of eclipse 2.3
don't know if that will work any better
but who knows, it just might work for you
http://www.mediafire.com/?7b71gn1j3r2dwrj
edit: if you problem is kernel related, it's not going help
also have you been checking the kernel,
System version:
1.3.418
Android version:
2.3.5
Baseband version:
N_03.13.31P
Kernel version:
[email protected]#2
sd_shadow said:
Scur, I uploaded a nandroid of eclipse 2.3
don't know if that will work any better
but who knows, it just might work for you
http://www.mediafire.com/?7b71gn1j3r2dwrj
edit: if you problem is kernel related, it's not going help
also have you been checking the kernel,
System version:
1.3.418
Android version:
2.3.5
Baseband version:
N_03.13.31P
Kernel version:
[email protected]#2
Click to expand...
Click to collapse
Here's where I am now. With a method to root 2.3.5, I can SBF it and root. It will let me flash Eclipse 2.3, but will lose root when it flashes. So I can get Eclipse 2.3, but it's unrooted and I haven't found a way to root it after flashing yet. Odd there. I have a couple abd tips to try to get it going, but I'm going to try your nandroid first. Much thanks.
Droid X2 > Rooted 2.3.5 > Tapatalk
The nandroid worked like a charm, I thank you good sir.
Droid X2 > Eclipse 2.3 > Tapatalk