Related
can anyone tell me why I get a bootloop condition every time i do a factory reset in CWM?
I have to RSD back to 1.26 every time I do a factory reset
Nevermind wrong thread sorry
SolidHelix said:
can anyone tell me why I get a bootloop condition every time i do a factory reset in CWM?
I have to RSD back to 1.26 every time I do a factory reset
Click to expand...
Click to collapse
Well if you're on Bell I don't think flashing to 1.26 would work because it's an AT&T SBF. I may be wrong, but that could be what's causing your bootloop. If you're on Bell, I would suggest flashing 2.1.1, and then installing CWM over that. That's what I have and it's been flawless. Hope this helps.
thegregulator said:
Well if you're on Bell I don't think flashing to 1.26 would work because it's an AT&T SBF. I may be wrong, but that could be what's causing your bootloop. If you're on Bell, I would suggest flashing 2.1.1, and then installing CWM over that. That's what I have and it's been flawless. Hope this helps.
Click to expand...
Click to collapse
Its an unlocked ATT phone. Guess I should have stated that. I have no problem installing anything. Just finished the whole process going from 1.26->1.57->1.83->GINGERBREAK->CWM->webtop mod->gingerblur->steelbue theme. Lol. I wanted to know about the hard reset because I flashed a 1.83 sbf that didn't wipe. I didn't want to go all the way back to 1.26. I needed to be odexed to install the webtop mod.
Anyway, its all done now after a couple hours. Just wanted to know why does a hard reset in cwm always put me in a bootloop
Sent from my MB860 using XDA Premium App
Are you doing a factory reset before or after you install gingerblur? I've read that doing a factory reset before you install gingerblur can cause a bootloop.
Sent from my MB860 using XDA Premium App
After.... I read that too. So I did wipe right after flashing gingerblur without rebooting first. It would boot right to homescreen but after 5 or 6 seconds it dies and boots again. Cwm is unable to load after that point. Red is the only way out
Sent from my MB860 using XDA Premium App
SolidHelix said:
After.... I read that too. So I did wipe right after flashing gingerblur without rebooting first. It would boot right to homescreen but after 5 or 6 seconds it dies and boots again. Cwm is unable to load after that point. Red is the only way out
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
That's weird. I have a Bell Atrix and have never had a problem like that. And because gingerblur is designed for the att atrix I have no idea why you be getting any of these issues.
Sent from my MB860 using XDA Premium App
Yep it weird for sure. Still waiting for the elites to chime in. It doesn't make sense to me. I have everything back, I would just like to know why it happens
Sent from my MB860 using XDA Premium App
ok so im confused. i just got my photon and i have unlocked it and rooted it and got cwm on it fine. but now i need to update to 198-7 for jokers rom, now im not sure where to find the sbf's and do i just go straight to 198-7 from my 154-5??? "as these are based on 198-7 you need to have sbf'ed 198-7 first (it doesnt flash updated radio)" and i just flash with rsd? like i had to for root on the unlocked boot loader? and finaly where do i get the sfb? thanks for all the help. im just new to photons.
thanks
You need to install RSD LITE and flash to 198-7 before applying the jokers locked 4g via bootstrap.
Read everything in this thread first for info on doing this.
http://forum.xda-developers.com/showthread.php?t=1202666
Then since the links are dead you can get the files from
http://www.holylivingfuck.com/ACS/SBFs/
Before flashing make sure your battery is greater than 50percent full. 100percent is better.
There is a quick instruction list I posted earlier for someone with a bricked phone. Dont care to rewrite it so here you go.
http://forum.xda-developers.com/showthread.php?t=1412153
So read , read read, copy and paste **** in a cheat sheat document and dont skip any steps... Good luck and know if you messup and you think the phone could be bricked you can always flash back via RSD lite... Long as you have plenty of battery.
Just thought i should say- im that fool with the bricked phone haha this worked perfect but i did get an error about "BD" or something at the end, i dont remember the exact error but i ignored it and sure enough it worked just fine!
Sent from my MB855 using xda premium
Joker's ROMs are based on 198_7, so you will need to flash it. ShabbyPenguin's holylivingfuck site has the 198_7 ROM. I flashed 198_7 first before unlocking, so I'm not sure, but I'm guessing the 198_7 ROM will re-lock the bootloader in which case you will have to unlock again.
It will also unroot the phone.
Yep flashing the sbf with rsd lite will restore the stock bootloader.
---------- Post added at 07:14 PM ---------- Previous post was at 07:08 PM ----------
Good to hear you got it back.. The phone is a bit more resilient than we think.
It is nice to have a fallback incase something doesnt work right.. Start using titanium backup for quick restorations or partial restorations and you wont lose anything text conversations etc..
TheChronicDroid said:
Just thought i should say- im that fool with the bricked phone haha this worked perfect but i did get an error about "BD" or something at the end, i dont remember the exact error but i ignored it and sure enough it worked just fine!
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
The reason for flashing 198-7 is to ensure everything non-flashable is up to date and to know you have read enough to save your self in an emergency. Sbf's are our master reflashes that fix screw ups. It is possible to flash joker roms on 198-6(latest ota) but i want people to have a consistent experience along with the tools to fix problems already in place.
It may not be as easy as other phones but we are working on that.
Also the dev section has a great sticky by loki with links and instructions to nearly everything
Sent from my MB855 using XDA App
Makes sense. I thought it was to do with the deodexing of 198-7. Good to hear more into it from the man himself.
jokersax11 said:
The reason for flashing 198-7 is to ensure everything non-flashable is up to date and to know you have read enough to save your self in an emergency. Sbf's are our master reflashes that fix screw ups. It is possible to flash joker roms on 198-6(latest ota) but i want people to have a consistent experience along with the tools to fix problems already in place.
It may not be as easy as other phones but we are working on that.
Also the dev section has a great sticky by loki with links and instructions to nearly everything
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
thanks for all the replys guys. i might do this later. it just takes so long you have to have a long time when you know you wont use your phone. haha =) thanks for the help guys.
OK now I'm confused,
I'm on 198-6
Rooted via torpedo
Installed bootstrap apk
Wiped all user data
Wiped dalvic cache x3
Installed skinny4g
Rebooted wiped dalvic cache x3
installed black out theme
I'm thinking skinny4g is deoxidized because i have flashed multiple themes?
Haven't had a hiccup or reboot yet
Running smooth
Am i missing something???
Sent from my MB855 using Tapatalk
Reason he would like everyone on a standard platform is for control over the testing.. Rhetorics but 198_6 may have force close and 198_7 may not. No need to diagnose problems that aren't on the approved platform..
He is not saying you cannot use 198_6 but it makes it easier if everyone use 198_7 for testing his rom's.
ttkyles said:
OK now I'm confused,
I'm on 198-6
Rooted via torpedo
Installed bootstrap apk
Wiped all user data
Wiped dalvic cache x3
Installed skinny4g
Rebooted wiped dalvic cache x3
installed black out theme
I'm thinking skinny4g is deoxidized because i have flashed multiple themes?
Haven't had a hiccup or reboot yet
Running smooth
Am i missing something???
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
ScottieRotten said:
Reason he would like everyone on a standard platform is for control over the testing.. Rhetorics but 198_6 may have force close and 198_7 may not. No need to diagnose problems that aren't on the approved platform..
He is not saying you cannot use 198_6 but it makes it easier if everyone use 198_7 for testing his rom's.
Click to expand...
Click to collapse
Oh OK
So 198-7 wont become available OTA from Motorola?
And [email protected]## links for 198-7 are dead.
Ooooops mad bad Opera mobile downloads fine
Sent from my MB855 using xda premium
ttkyles said:
Oh OK
So 198-7 wont become available OTA from Motorola?
And [email protected]## links for 198-7 are dead.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Links just worked for me.
http://www.holylivingfuck.com/ACS/SBFs/
6bowmans said:
Links just worked for me.
http://www.holylivingfuck.com/ACS/SBFs/
Click to expand...
Click to collapse
Yea thanks just swiched to Opera
Sent from my MB855 using xda premium
Quick question. Can I do a nandroid restore after wiping data, cache and dalvik?
If you chose to put it in your external SD card when you made it, yes. wiping the big 3 doesn't wipe the SD card
Sent from my MB870 using XDA App
IDMA.DROID.X2 said:
If you chose to put it in your external SD card when you made it, yes. wiping the big 3 doesn't wipe the SD card
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
So i will be able to go back to my original ROM just as I left it even after wiping the big 3?
Yup! I've got a back ulbof every ROM except MIUI, haven't flashed it yet! Haha
Sent from my MB870 using XDA App
EDIT: Make sure its on the external SD card though. Not sure weather it will be there on the SD card if you put it there then wiped the big 3
IDMA.DROID.X2 said:
Yup! I've got a back ulbof every ROM except MIUI, haven't flashed it yet! Haha
Sent from my MB870 using XDA App
EDIT: Make sure its on the external SD card though. Not sure weather it will be there on the SD card if you put it there then wiped the big 3
Click to expand...
Click to collapse
I have a nandroid on my internal that has endured several data wipes and sbf's. It is a backup of my stock phone before flashing anything. I backed it up in both places just in case.
Sent from my cm7dx2 using XDA App
litetaker said:
So i will be able to go back to my original ROM just as I left it even after wiping the big 3?
Click to expand...
Click to collapse
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
iBolski said:
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
Click to expand...
Click to collapse
Good to know! I missed the tests done, I thought it backed up everything.
Sent from my MB870 using XDA App
iBolski said:
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
Click to expand...
Click to collapse
So if MIUI is saying that it is running Android 4.0.3, and CM7 is Android 2.3.7, then is it not ok to nandroid back to CM7 from MIUI?
jsgraphicart said:
So if MIUI is saying that it is running Android 4.0.3, and CM7 is Android 2.3.7, then is it not ok to nandroid back to CM7 from MIUI?
Click to expand...
Click to collapse
No, it should be fine. 4.0.3 is STILL using the same kernel. 4.0.3 is the OS version, not necessarily the kernel version.
Since the bootloader is still locked, flashing the DX2 MIUI still keeps the 2.3.4 kernel. All that gets replaced are the system files. So, nandroiding back to CM7 (which is what I did) is fine because you are still running the same kernel.
At least, that's how I read it when I researched a little on this and with some other people posting their explanations as well.
The reason you shouldn't flash 2.3.4-based ROMs over 2.3.5 is because the kernel version was changed. Remember, the kernel can ONLY be updated via a Verizon-approved OTA. The 2.3.5 update is not an official release, but it DID come from Motorola servers, so it has the signature in it that the X2 is looking for when the kernel is attempted to be upgraded. Hence, that is why flashing a 2.3.4-based ROM over a 2.3.5 image is not a good thing. Same goes with flashing a 2.3.5 ROM over a 2.3.4 image. It's just not a good idea and could pose problems down the road.
iBolski said:
No, it should be fine. 4.0.3 is STILL using the same kernel. 4.0.3 is the OS version, not necessarily the kernel version.
Since the bootloader is still locked, flashing the DX2 MIUI still keeps the 2.3.4 kernel. All that gets replaced are the system files. So, nandroiding back to CM7 (which is what I did) is fine because you are still running the same kernel.
At least, that's how I read it when I researched a little on this and with some other people posting their explanations as well.
The reason you shouldn't flash 2.3.4-based ROMs over 2.3.5 is because the kernel version was changed. Remember, the kernel can ONLY be updated via a Verizon-approved OTA. The 2.3.5 update is not an official release, but it DID come from Motorola servers, so it has the signature in it that the X2 is looking for when the kernel is attempted to be upgraded. Hence, that is why flashing a 2.3.4-based ROM over a 2.3.5 image is not a good thing. Same goes with flashing a 2.3.5 ROM over a 2.3.4 image. It's just not a good idea and could pose problems down the road.
Click to expand...
Click to collapse
Ok, that makes sense. I figured it would be fine but didnt know the technical details.
I've flashed my 2.3.4 backups over 2.3.5 quite a bit since my cheesecake backup is 2.3.5 and I've never had any issues. Do we really know if the kernel changed? I never really looked at the kernel version on 2.3.5.
Sent from my MB870 using XDA App
T3HBR1AN said:
I've flashed my 2.3.4 backups over 2.3.5 quite a bit since my cheesecake backup is 2.3.5 and I've never had any issues. Do we really know if the kernel changed? I never really looked at the kernel version on 2.3.5.
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
Back in December, I asked the question about nandroiding and if it replaced the kernel. Motcher (and ashclepdia) helped out with this one. Motcher SBF'd to 2.3.4 and then nandroided back to Eclipse 2.0.3 (which is 2.3.5) based and the kernel version came up as 00005 which is the 2.3.4 kernel. So, Nandroiding does NOT replace the kernel.
Here's the posted that he posted about this:
http://forum.xda-developers.com/showpost.php?p=20808392&postcount=20
It may be that the differences are minor enough that it won't cause issues, but if the official 2.3.5 ever comes out, it might be best to always SBF back to 2.3.4 if you have to just to be on the safe side. I guess the moral of the story is, do this at your own risk.
Ok I tried to nandroid back to cm7 from Miui and I got a md5-sum mismatch message, and I wasn't able to go back. Do I need to wiped the big 3 every time I nandroid ?
Sent from my DROID X2 using XDA App
bandit1224 said:
Ok I tried to nandroid back to cm7 from Miui and I got a md5-sum mismatch message, and I wasn't able to go back. Do I need to wiped the big 3 every time I nandroid ?
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
No. That means the md5-sum hash key that was generated after the backup was created isn't matching with your nandroid backup. It means possibly your backup is corrupted.
Wiping the big three has nothing to do with nandroiding.
Uninstall bsr -either cm7 or orig. Then reinstall cm7 bsr. It worked for me On cm7. BTW Be sure not to use any spaces when renaming.
failed restore
So im trying to reload my backup from my sd card. I have made 2 thus far and neither work.
I am on the Rogers network on a i747 with the dlk4 baseband. CWM, rooted, stock rom. When i try to restore it loads a few things (ie. system), and starts loading the DATA portion. Which at this point i get an error message. I reboot it, and my phone gets hung up at the samsung loading screen.
I have tried wiping the big 3 and also under mount and unmount i formated system before restoring as well with no success.
Could it be that my version of CWM is 5.5.0.4.. And, from my understanding I dont think it would be the cause, but maybe because i made the backup after being rooted and flashing cwm
Sykotyk said:
So im trying to reload my backup from my sd card. I have made 2 thus far and neither work.
I am on the Rogers network on a i747 with the dlk4 baseband. CWM, rooted, stock rom. When i try to restore it loads a few things (ie. system), and starts loading the DATA portion. Which at this point i get an error message. I reboot it, and my phone gets hung up at the samsung loading screen.
I have tried wiping the big 3 and also under mount and unmount i formated system before restoring as well with no success.
Could it be that my version of CWM is 5.5.0.4.. And, from my understanding I dont think it would be the cause, but maybe because i made the backup after being rooted and flashing cwm
Click to expand...
Click to collapse
this is a thread for the motorola droid x2.
oops
Lorenzo VonMatterhorn said:
this is a thread for the motorola droid x2.
Click to expand...
Click to collapse
i've been searching threads with search tool....guess i wasn't paying attention.
Cheers
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