Related
I was trying to sbf to install the Affinity ROM but during the sbf it stopped n my phone says " failed to boot 4, starting rsd mode. " What is this and how can it be fixed.......or can it?
mrstone77 said:
I was trying to sbf to install the Affinity ROM but during the sbf it stopped n my phone says " failed to boot 4, starting rsd mode. " What is this and how can it be fixed.......or can it?
Click to expand...
Click to collapse
You did something wrong during the SBF process (of course). You have to make sure that your phone was in RSD mode (which it now is in) and use RSD Lite (on windows) or SBF_flash (linux and mac) to flash the SBF onto the phone.
Also, MAKE SURE YOUR PHONE IS DULLY CHARGED. I got an error the first time I SBF'd cuz I didn't do that. Had to get a new battery and then flash.
Hope this helped.
Sent from my DROID X2 using XDA App
mrstone77 said:
I was trying to sbf to install the Affinity ROM but during the sbf it stopped n my phone says " failed to boot 4, starting rsd mode. " What is this and how can it be fixed.......or can it?
Click to expand...
Click to collapse
I know what the problem is.
You were trying to install the Affinity ROM...
(*drum gets hit - man walks off with satisfied look on face*)
Sent from my DROID BIONIC using xda premium
mrstone77 said:
I was trying to sbf to install the Affinity ROM but during the sbf it stopped n my phone says " failed to boot 4, starting rsd mode. " What is this and how can it be fixed.......or can it?
Click to expand...
Click to collapse
Shouldn't that be flashed in recovery?
EDIT: Duh...I didnt see that he was sbf'ng then installing the rom...sorry.
Sent from my DROID X2 using XDA App
Try downloading the file with Firefox or chrome and extract the .gz file with 7zip
Also there is a 2.3.3 and a 2.2.2 sbf file, try them both
Sent from my DROID X2 using XDA App
Ignore.
10char.
If one wants to return to stock after running a custom ROM, is it as simple as flashing the latest SBF with RSD Lite or should the bootloader be re-locked first? Anything else needed?
All you need is to flash the SBF but only after replacing CWM if installed with the stock recovery.
Doesn't flashing the SBF automatically reinstall the stock recovery?
To return to stock use the following ;
1. Menu/Settings/Privacy/Factory Data Reset
2. Flash the sbf using RSD lite
3. Done
If you do not do a Factory Data Reset via menu/settings your installed apps/launcher/etc do not get wiped and can cause issues. Also, RSD lite may give you a "failed" error during the final reboot phase. Don't worry this bug in RSD and you should be fine.
I keep having problems getting RSD lite to recognize my phone. The drivers installed fine, I get into "starting RSD protocol"... plug the phone into my computer and nothing. If I sit and wait for the phone to do anything after starting protocol nothing happens.
Also can't get RSD to recognize the phone if its in recovery mode or from android with or without USB debugging turned on.
Wondering what else I can do to get it to work?
Sent phrom my Mo-Pho
unlocked mopho-need to update sbf
Hey i have doubt n not clear about this...
i have unlocked mopho ,im from india so using one of indian gsm carrier so if update my sbf version will it lock my phone??
and i read somewhere that we need to activate mopho after update what do we mean by that??
try and let us know
daddymikey1975 said:
I keep having problems getting RSD lite to recognize my phone. The drivers installed fine, I get into "starting RSD protocol"... plug the phone into my computer and nothing. If I sit and wait for the phone to do anything after starting protocol nothing happens.
Also can't get RSD to recognize the phone if its in recovery mode or from android with or without USB debugging turned on.
Wondering what else I can do to get it to work?
Sent phrom my Mo-Pho
Click to expand...
Click to collapse
Hey man which version of rsd are you using? I find that 5.5 works well. Try reinstalling the drivers, reinstalling rsd, and plug the phone in..be patient as your computer installs the drivers to the phone. It should recognize it.
Sent from my MB855 using xda premium
KTT16 said:
Hey man which version of rsd are you using? I find that 5.5 works well. Try reinstalling the drivers, reinstalling rsd, and plug the phone in..be patient as your computer installs the drivers to the phone. It should recognize it.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
I'll check when I get home and report back. This is the one thing keeping me from installing CM7 ... the inability to flash back to stock lol.
Thanks for the heads up.
Sent phrom my Mo-Pho
KTT16 said:
Hey man which version of rsd are you using? I find that 5.5 works well. Try reinstalling the drivers, reinstalling rsd, and plug the phone in..be patient as your computer installs the drivers to the phone. It should recognize it.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
all the drivers installed. I installed RSD 5.5... i shut the phone down and booted into RSD.. "starting RSD protocol support"... then i plugged the phone in (w/ RSD open/running)... the computer installed the driver "SE sunfire flash" (or something like that)... but RSD would not recognize the phone. It never showed a device connected no matter how many times I hit the 'show device' button.
Any ideas ?
updating sbf query....
Posting this once again reply if anyone knows.....
Hey i have doubt n not clear about this...
i have unlocked mopho ,im from india so using one of indian gsm carrier so if update my sbf version will it lock my phone??
and i read somewhere that we need to activate mopho after update what do we mean by that??
Tried RSD 5.5 and 5.3 with no luck.
My computer makes the sound of a device connecting but RSD fails to see it.
Sent phrom my Mo-Pho
I had this issue with my first Photon, I think that you're screwed.
You have no way to SBF your phone...
WAIT A MINUTE....
WAIT --- How did you unlock your bootloader the first time without SBFing???
deedscreen said:
I had this issue with my first Photon, I think that you're screwed.
You have no way to SBF your phone...
WAIT A MINUTE....
WAIT --- How did you unlock your bootloader the first time without SBFing???
Click to expand...
Click to collapse
I'm not unlocked.. only rooted stock. Nothing more, nothing less..
Part of the reason I haven't unlocked bootloader or installed CWM or CM7 is because I can't SBF anything yet.. I want to make sure I can do a successful return to stock before I do anything else (When I had my Epic I got very good w/ Odin.. it's Samsung's computer recovery tool.. similar to using RSD w/ sbf file)
Would you be willing to factory reset and wipe data and start over?
Sent from my MB855 using xda premium
KTT16 said:
Would you be willing to factory reset and wipe data and start over?
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
I've tried that.. no worky either.. but I'm down for anything..
(by the way, I just installed wubi so I can try the sbf_flash command to see if that works LMFAO) ... I'll report back in the morning after I try it.
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
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