Related
Alright, I was running CM9 v13 until last night, but needed my camera for work(nothing portrays an accident scene better than a picture!), so I decided to reflash 198.7. Something terribly went wrong.
Read so many different threads and flashed so many different sbf's my head is spinning. I do know that when I power up and press up I get RSD, and if I power up and press down I can go through the menu. I even tried fastboot and attempted to follow some of these steps with fastboot. http://www.atrixforums.com/forum/rescue-squad/5358-alien-install-gone-bad-bricked-recovered-still-screwed-up-4.html
I am thinking that the bootloader isn't fried since I can get into the menu system, but even after flashing 198.7 if it doesn't fail it cycles through the never ending bootloop. When it does fail I get the following error on the device screen: SVF:106:1:2 sec_exception:b655, eddc, eb
Luckily I have seen Gman floating around here, so since he assisted big time with the atrix issue, I am hoping that he can assist me.
I don't have skype though...
I will have internet access tomorrow, but can't install anything to my work computer(toughbook, locked down like a fiend!)
Ideas? Not looking for a beatdown. Asking for help, from the community.
EDIT: Just saw this. http://forum.xda-developers.com/showthread.php?t=1394982For some odd reason I think this is what I did. Now it appears as though I am royally screwed!
Thank you,
Medic
You didn't have a nandroid backup of a blur rom you could have used? That would have been better than sbfing back to stock.
Sent from my MB855 using Tapatalk
When I got stuck in moto logo loop with no backup available I had to boot into recovery and factory reset then reboot. If you can use menu with power + down. On 154 sbf, then flashed 198.7 after booting again
Sent from my MB855 using XDA App
You need to factory reset or wipe before flashing a sbf. However all you need to do to get a camera is flash a blur rom like skinny or rocko, or even cm7. When you're done you can wipe and flash back. I do it all the time
Sent from my MB855 using XDA App
Grrr, I must have flashed the Electrify ROM. It boots into it, but has to make the phone call to activate. Can't bypass it. The Electrify has a locked bootloader?
Fastboot, RSD, and ASR work, or at least I can access them. Tried wiping date/factory reset, but it boots back into the Electrify ROM.
Not thinking my local rep will be able to help me out on this one!
Any other ideas?
Edit* Bypassed using the no bp option. Unable to root using Shabby's aio. Goes through the process, reboots, but when I attempt to launch system recovery it reminds me that I don't have root privs.
jokersax, why in your post for CM9 do you tell people that if they want to switch off of CM9 they have to sbf? I've nandroid'ed back without problems to stock, and it's a lot safer than flashing sbf's since everyone seems to temporarily brick.
it actually say just to wipe and flash a different rom. The sbf is to return to stock
mrinehart93 said:
jokersax, why in your post for CM9 do you tell people that if they want to switch off of CM9 they have to sbf? I've nandroid'ed back without problems to stock, and it's a lot safer than flashing sbf's since everyone seems to temporarily brick.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Okay, now I am rooted and have bootstrap installed.
Looked in the about phone section, and duh, I am running 45.1.190 for the Electrify.
Any idea how to get this off of my phone?
medic233 said:
Okay, now I am rooted and have bootstrap installed.
Looked in the about phone section, and duh, I am running 45.1.190 for the Electrify.
Any idea how to get this off of my phone?
Click to expand...
Click to collapse
I had a similar issue. Unlocking the boot loader I used the Sbf for the Electrify by mistake and not the Pudding.sbf. Only it bricked my phone sticking it on the moto bootup and just giving me some errors and going nowhere from their. Now I'm just spit balling here, but I have a prediction on how you can fix, do some research to make sure this may work and not brick your phone:
1) Unlock your bootloader using Pudding.sbf
2) Use Bootstrap to Install CWM for Photon
3) goto the mounts and storage menu select format system
4) Once that finishes go back and select wipe data/factory reset and then wipe dalvik cache and cache partition
5) After wiped go to the advanced menu select reboot recovery
6) Once it goes back to recovery Power off
7) Go into RSD (hold power nd Volume up+)
8) Flash the stock sbf
9) boot up
10) I would recommend using Sdk tools Fastboot command -W to erase all user data and cache after everything if it boots up
I would assume this would do the trick, the only thing I'm uncertain of is if you'll be able to unlock. (If it goes through a long method then says failed right at the end then it probably worked) If it doesn't work you can continue the rest of the steps using bootstrap, but If it were me I would want to try to get as much Photon on the phone and Electrify off the phone as possible
FanBoy_Hunter said:
I had a similar issue. Unlocking the boot loader I used the Sbf for the Electrify by mistake and not the Pudding.sbf. Only it bricked my phone sticking it on the moto bootup and just giving me some errors and going nowhere from their. Now I'm just spit balling here, but I have a prediction on how you can fix, do some research to make sure this may work and not brick your phone:
1) Unlock your bootloader using Pudding.sbf
2) Use Bootstrap to Install CWM for Photon
3) goto the mounts and storage menu select format system
4) Once that finishes go back and select wipe data/factory reset and then wipe dalvik cache and cache partition
5) After wiped go to the advanced menu select reboot recovery
6) Once it goes back to recovery Power off
7) Go into RSD (hold power nd Volume up+)
8) Flash the stock sbf
9) boot up
10) I would recommend using Sdk tools Fastboot command -W to erase all user data and cache after everything if it boots up
I would assume this would do the trick, the only thing I'm uncertain of is if you'll be able to unlock. (If it goes through a long method then says failed right at the end then it probably worked) If it doesn't work you can continue the rest of the steps using bootstrap, but If it were me I would want to try to get as much Photon on the phone and Electrify off the phone as possible
Click to expand...
Click to collapse
Alright, completed 1-8. Phone won't reboot, stuck in the Dual Core screen.
I did notice a bunch of "Failed to Boot 2" messages, but last I had looked the battery was full.
Attempting fastboot stuff now.
moto-fastboot devices works, lists my device.
moto-fastboot erase recovery fails. remote: (00180001)
moto-fastboot flash recovery stock_recovery.smg works, sends and write recovery
moto-fastboot reboot works
medic233 said:
moto-fastboot reboot works
Click to expand...
Click to collapse
So where are you now?
It is just sitting there with the dual core screen. Still.
Tried turning it off so the battery could charge, won't turn off.
Menu is still accessible.
medic233 said:
It is just sitting there with the dual core screen. Still.
Tried turning it off so the battery could charge, won't turn off.
Menu is still accessible.
Click to expand...
Click to collapse
This is obvious, but I have to ask, did you do a battery pull and let it sit for a couple seconds and then try to reboot? also it's stuck on mogo, is it showing error 2,3 or 4? Or any error for that matter?
Did a few battery pulls.
No error, just the Moto Dual Core Screen.
I contacted one of my friends who is a rep, and he will strip the phone, and exchange it. Helps that his boss has a Mopho and he is getting one in a few days.
Thank you for the help FanBoy_Hunter. Greatly appreciated.
I pick up my new mopho tomorrow.
I am going to leave it stock(sigh).
Was not going to reactivate my crackberry.
Grrrr!
so i try to turn on wifi and ses error and hard resets and then just randomly does it so i tried flashing a different rom well 4 of them actually and none of them fixed it then i tried to sbf with 183 with pudding then it wouldnt even loadn up it would get to the att logo then reboot and go off with the red light flashing finally i had to fast boot to get clockwork mod then flashed another rom and its still doing it any one got an answer to this crap
Engrish Prease?
If I'm getting that right, you bootlooped, tried flashing 4 roms without wiping, then decided to sbf?
Well... Fastboot wipe, try flashing any rom using the latest romracer recovery, and hope that you didn't HARD BRICK YOUR PHONE BECAUSE YOU USED AN SBF.
omni_angel7 said:
Engrish Prease?
If I'm getting that right, you bootlooped, tried flashing 4 roms without wiping, then decided to sbf?
Well... Fastboot wipe, try flashing any rom using the latest romracer recovery, and hope that you didn't HARD BRICK YOUR PHONE BECAUSE YOU USED AN SBF.
Click to expand...
Click to collapse
i would say that is english! i decided not to use punctuation, my bad you cant read that sorry let me include i wiped each and everytime before i flashed i am not a newb at this so if your not going to help then don't post!!! simple enough right.???
somthing new now when i plug my charger in to charge it it reboots and stays at the moto screen.
shadowscreation said:
i would say that is english! i decided not to use punctuation, my bad you cant read that sorry let me include i wiped each and everytime before i flashed i am not a newb at this so if your not going to help then don't post!!! simple enough right.???
somthing new now when i plug my charger in to charge it it reboots and stays at the moto screen.
Click to expand...
Click to collapse
Still don't know whether you're on the latest recovery (romracer's or CWM touch). That could be an issue. If you aren't getting failed to boot message, then it's almost certainly a software issue. Were it my atrix, I would ask myself:
Am I still getting the white unlocked text after that SBF?
1. If not, then unlock, wipe, and flash a rom using the latest recovery, and NEVER touch another SBF
2. If so, try a more thorough wipe if possible. Use every fastboot erase and make sure that your downloaded ROM isn't corrupted. Then do the rest of 1. minus unlocking, of course.
I have the latest rom racer recovery and the sbf I flashed was 1.83 with pudding I got it mostly functional again by restoring a backup I had. but still if I try to turn on wifi it will say error and the bootlooping starts all over again . That seems to be what is causing it. And yes the unlocked is still at the top of the moto logo.
Sent from my MB860 using XDA Premium App
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.
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?
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