Related
This is not for the OTA, this is for the prior cheesecaked build
####BACKUP your current system with BSR before doing anything!####
1. SBF or nand restore to stock 2.3.4 (if on completely unmodified and fully bloated stock 2.3.4 skip to step 2)
2. Apply 2.3.5 (412 build) in stock recovery after placing on external sd card root and renaming update.zip (reboot phone and hold down volume, press down arrow until you see android recovery, press up volume button, when on next screen press both volume buttons at same time. Wipe cache and flash update.zip)
3. Root using zergrush (with phone unpluged unzip and open zergrush program....make sure unknown sources in applications is checked and that debuggung is checkmarked. I also checkmark stay awake as zergrush recommends setting screen timeout for ten minutes. Connect your phone and then check it is connected as charge only. Hit spacebar and then the phone will reboot after the zerglings lol find a way in and your rooted)
***Rootkeeper has caused issues with some roms aborting install.***
4. Install & then boot into bootstrap
5. Wipe data, cache and dalvik
6. Flash 2.3.5 based custom rom from removable sd card & reboot when done.
http://www.mediafire.com/?nt4ixu5hx55t9cu RSD Lite 5.4.4
http://depositfiles.com/files/spvcfjb4w 2.3.4 SBF
(Outdated build)http://depositfiles.com/files/95u3zw9k6 2.3.5 update (412 build) Eclipse 2.1 and GingerBread Phone 7 are based off this build
Zergrush V3 is here http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
Boot Strap Recovery http://www.mediafire.com/?k4ooqa7keblzqso and install from root of sd after rooting phone with zergrush.
They are the actual links the devs made.
(Outdated but works)http://eclipserom.com/mods/click.php?id=84 look here for nitro's direct Eclipse 2.1 download.
Outdated but works)http://www.mediafire.com/?ngv8aeq1745wrqn
peper's direct GingerBread Phone 7 download
Rootkeeper has caused some failed Eclipse 2.X.X installs. This method is the safest bet.
For icing on the cake here is the SBF Tutorial link if you dont know how to SBF http://forum.xda-developers.com/show....php?t=1175300
Thanks this will help many including myself. Had to sbf 2 times last night and no luck. However I was using rootkeeper. I will try again tonight with zergrush.
There are now a newer set of updates to 2.3.5 to be applied over... if your gonna do it might as well do a full set..
I would put at the very beginning of the post to do a backup. People should know, but you know how that goes. lol
mastafunk said:
There are now a newer set of updates to 2.3.5 to be applied over... if your gonna do it might as well do a full set..
Click to expand...
Click to collapse
I know you can update via cheese cake to newer versions. I know Eclipse is off of the linked 2.3.5 which is 412 and I believe pepper's is the same. Please correct me if I am wrong.
There might be unknown issues if everyone starts flashing roms desinged for one build over other updates....is that what your refering to? Am I wrong about this?
Changed Eclipse link to Nitro's 2.0.2 12-15-11
Thanks a lot for posting this!
Eclipse 1.3 RC
mine keeps getting stuck at zegruths rooting method on "waiting for device" it has gotten farther than that before but only to "dsomething has been started"
///::
You have the usb debugging checked and it connected as charge only?
Sent from my DROID X2 using xda premium
Bump for changes
from my X2 with 2.0.1 probably while driving down the road with my knee at the helm
Also make sure u have unknown sources allowed in managage applications b4 u start this root method
Sent from my DROID X2 using xda premium
Kevin3328 said:
Also make sure u have unknown sources allowed in managage applications b4 u start this root method
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
OP updated with more rooting instructions Thanks for the suggestion Kevin3328
motcher41 said:
OP updated with more rooting instructions Thanks for the suggestion Kevin3328
Click to expand...
Click to collapse
Bump
Sent from my DROID X2 using xda premium
Bump....eclipse 2.0.3 link added 2.0.2 link removed
Sent from my DROID X2 using Xparent Blue Tapatalk
Fixed bad bootstrap link
Sent from my DROID X2 using Xparent Blue Tapatalk
Glad this got stickied, it's a good help
Im trying to help a friend with his droid x2. We rooted it with dooms v4 zergrush before doing anything else, hadnt seen this tutorial yet. When trying to update to 2.3.5 it aborts, last line said E:Error in /tmp/sideload/package.zip. Do we need to unroot to do this then root again? I did this because for eclipse rom it sais it needs rooted gingerbread, but step 3 of install is to root, so it confused me, I chose to root it first.
I tried unrooting and starting over, still wont work. Its wierd that it the OP it sais to do a BSR backup before starting but then step 4 sais to install bootstrap, Ill assume BSR is BootStrapRecovery, so if you need to have it to backup before starting why would you need to install it? Im a bit confused here. I have 2 rooted, unlocked bootloader x10s with MIUI so Im not a newbie but this is frustrating.
Bugly Astard said:
Im trying to help a friend with his droid x2. We rooted it with dooms v4 zergrush before doing anything else, hadnt seen this tutorial yet. When trying to update to 2.3.5 it aborts, last line said E:Error in /tmp/sideload/package.zip. Do we need to unroot to do this then root again? I did this because for eclipse rom it sais it needs rooted gingerbread, but step 3 of install is to root, so it confused me, I chose to root it first.
I tried unrooting and starting over, still wont work. Its wierd that it the OP it sais to do a BSR backup before starting but then step 4 sais to install bootstrap, Ill assume BSR is BootStrapRecovery, so if you need to have it to backup before starting why would you need to install it? Im a bit confused here. I have 2 rooted, unlocked bootloader x10s with MIUI so Im not a newbie but this is frustrating.
Click to expand...
Click to collapse
I have never used V4 zerg...use v3 as in instructions. You dont need to unroot. Are you flashing the 412 buil update in android stock recovery? After you install the 412 update you will need to reroot....DONT USE ROOTKEEPER...If you fallow the instructionas as wrote you will have no issues that also includes using the mentioned rooting program as well.
I would suggest at this point SBF and start from step one and/or unroot 2.3.4 and start from step one using everything in the OP as instructed to the T.
If you cant get it your not following the instructions.
Bugly Astard said:
Im trying to help a friend with his droid x2. We rooted it with dooms v4 zergrush before doing anything else, hadnt seen this tutorial yet. When trying to update to 2.3.5 it aborts, last line said E:Error in /tmp/sideload/package.zip. Do we need to unroot to do this then root again? I did this because for eclipse rom it sais it needs rooted gingerbread, but step 3 of install is to root, so it confused me, I chose to root it first.
I tried unrooting and starting over, still wont work. Its wierd that it the OP it sais to do a BSR backup before starting but then step 4 sais to install bootstrap, Ill assume BSR is BootStrapRecovery, so if you need to have it to backup before starting why would you need to install it? Im a bit confused here. I have 2 rooted, unlocked bootloader x10s with MIUI so Im not a newbie but this is frustrating.
Click to expand...
Click to collapse
The last time I tried this it would not work once rooted. Had to sbf, apply the update, then root.
BrianKLV said:
The last time I tried this it would not work once rooted. Had to sbf, apply the update, then root.
Click to expand...
Click to collapse
Which is how the directions say to do it althoughit does work if your rooted on stock...completely stock no unbloating done. Ota updates need the bloat to install correctly
sent from my cyanocrack
Multiupload links gone changed to new site
So I have a bit of a problem. I will explain the timeline of events. Any assistance anyone can give would be greatly appreciated.
Roughly a week ago I rooted my stock 2.3.4 X2 using the one click method. Click Here for Example.
No issues with that.
Yesterday I decided I wanted to install the CM7 rom This method.
I began flashing the 2.3.4 SBF using my Windows 7 64-bit machine with RSD 5.4.4. It completed flashing groups through the G65. It then attempted to switch to bypass mode. I received this error "Error switching phone to BP Pass through mode(0x70BE)" and it failed.
I have since updated the QHSUSB Driver and tried again. Still no luck.
Tried multiple computers and it still kept failing.
I have also tried booting into Ubuntu and was supposedly able to load the SBF using SBF_FLASH successfully. I say supposedly because the terminal acts as though there were no issues and it completes, but the phone still doesn't work.
When I boot up the X2 now, I get the error "Modem did not power up (1) Starting RSD protocol support".
I have the ability to get to the recovery menu and such so I am hoping there is some avenue I can take to get back to a functioning phone. Please let me know if you can help!
Thanks!
So are you saying you tried flashing cm7 with rsd? if so that's where you went wrong. You have to use the BSR. have you tried to sbf the stock 2.3.4?
Sent from my DROID X2 using xda premium
03civicdx said:
So are you saying you tried flashing cm7 with rsd? if so that's where you went wrong. You have to use the BSR. have you tried to sbf the stock 2.3.4?
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
No, I was trying to flash the stock 2.3.4 SBF with RSD before rooting and flashing CM7 with BSR. The error occurred while trying to flash to stock.
I am also able to boot into the android OS by using the Boot Android (No BP) option on the boot menu. Everything in the actual OS seems fine, just no signal.
Attempt to use fastboot
I've been trying to get CM7 on my X2 unsuccessfully for about two hours, here's the process I took.
I saved all my stuff, and erased everything on the phone using the Android Recovery. I went back to 2.3.4 using RSDlite, then Root using Pete's Tool and installed OTA Protect. I then installed Bootstrap, installed recovery, went to recovery mode, installed CM7, and then GAPPs. Now, I wipe data, clear the cache, clear the davlik cache, and reboot. Now, this is where I just get stuck at the M Dual Core Technology Screen.
I searched the forum for answers, but I couldn't really my problem. It seems CM7 just isn't booting for me. I have tried this 2-3 times already, please help me out!
Why did you install ota protect? And make sure you are properly rooted and that the sbf worked... check your about phone screen to make sure... all I know is to sbf again and start from the beginning.
Edit: also did you install the patched bsr.apk for cm7?
Sent from my DROID X2 using xda app-developers app
GoClifGo05 said:
Why did you install ota protect? And make sure you are properly rooted and that the sbf worked... check your about phone screen to make sure... all I know is to sbf again and start from the beginning.
Edit: also did you install the patched bsr.apk for cm7?
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
TRY #5 IT WORKS!
thanks anyway!
Awesome.... did I help or did it just decide to work the 5th time? Haha.
Sent from my DROID X2 using xda app-developers app
GoClifGo05 said:
Why did you install ota protect? And make sure you are properly rooted and that the sbf worked... check your about phone screen to make sure... all I know is to sbf again and start from the beginning.
Edit: also did you install the patched bsr.apk for cm7?
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
I've had to sbf more thwn once to get my X2 to get up and running. I would say to try and sbf again and instal the patched CM7 BSR. If u have any other questions, u can always pm me and ill do my best to help u outout
STEEL BLUE CM9X2
SBF 2.3.4
Root phone
Install regular BSR
Flash CM and Gapps
Wipe data (not cache DATA)
Boot CM
Load BSR for CM7
You CAN NOT boot CM with regular BSR loaded , hence the wipe Data before booting.
Sent from my MB870 using Tapatalk 2
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
Hi everyone,
I've been having some serious issues and I am stumped on what to do so I'm turning to you smart guys here at XDA...
I'm using a Droid X2 flashed to Cricket, running CM7.2. I read through the CM10 Jelly Bean thread and really wanted to give it a try because of all the neat features it has in it. I did a Nandroid backup, installed the zip and gapps, wiped data/cache and booted into CM10. Everything went good, got CM10 configured, but had a non-relevant issue with CM10 and figured it was probably just a bad install. I tried to restore my Nandroid and it froze up halfway through and sat at "Restoring .android_secure" for OVER an hour. So I made the dumb mistake of pulling the battery which resulted in a bootlooping soft-brick. I then did an SBF back to 2.3.5 which naturally wiped my flash to Cricket. So I rooted and re-flashed to get my network working again which went perfectly fine. Then I restored my Nandroid and went back to CM7.2....and now my Wi-FI says "Error" and will not even attempt to connect. I figured the Nandroid probably got botched so I restored it again and had the same issue. I tried to reflash CM7.2 and also tried to reflash CM10 and get the "assert failed: run_program (tmp/kernel_check) ==0 (status 7)" error on both. I have tried repeatedly redownloading both zip files and attempted reflash with the same error. Obviously rebooting the phone and trying Wi-Fi fixer do absolutely nothing. I would either like to stay on CM7.2 OR give CM10 another try but cannot flash either zip with the CM7 patched BSR. If I can have the Wi-Fi fixed on CM7.2 then great, if I can be on CM10 with working Wi-Fi even better, but I would like to be able to get this fixed WITHOUT having to do another SBF...flashing it to Cricket is a PITA and I can only do the flash on 2.3.5 since that is the only version that gives the "PC Mode" option for USB connection. Factory Reset is not an issue with me, I just want things working properly. Any and all help is as usual GREATLY appreciated. Thanks in advance.
Err, you couldn't have been on 2.3.5 and CM7 before. That and CM10 are 2.3.4 ROMs. If you sbf'd to 2.3.5 then your only options are stock ROM or eclipse 2.3
Sounds like you need to sbf back to 2.3.4
Sent from my DROID X2 using xda app-developers app
three west said:
Err, you couldn't have been on 2.3.5 and CM7 before. That and CM10 are 2.3.4 ROMs. If you sbf'd to 2.3.5 then your only options are stock ROM or eclipse 2.3
Sounds like you need to sbf back to 2.3.4
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
You are correct, they are ROMS that need to be flashed from 2.3.4, but I didn't flash, I restored a Nandroid backup. I started on 2.3.4, flashed CM7, used that for a while, then flashed CM10 over CM7, then did SBF to 2.3.5 and then restored a Nandroid back to my CM7. As I stated above, I can only get my phone onto Cricket from 2.3.5 as that is the only version of android that has the "PC Mode" option when connecting to computer with USB, that is the ONLY connection mode that can be used to network flashing. If I SBF back to 2.3.4 I might be able to flash a new ROM but then I won't be able to do the network flash myself, I will have to take it to cricket which I would prefer not to have to do.
d34thbl00m said:
You are correct, they are ROMS that need to be flashed from 2.3.4, but I didn't flash, I restored a Nandroid backup. I started on 2.3.4, flashed CM7, used that for a while, then flashed CM10 over CM7, then did SBF to 2.3.5 and then restored a Nandroid back to my CM7. As I stated above, I can only get my phone onto Cricket from 2.3.5 as that is the only version of android that has the "PC Mode" option when connecting to computer with USB, that is the ONLY connection mode that can be used to network flashing. If I SBF back to 2.3.4 I might be able to flash a new ROM but then I won't be able to do the network flash myself, I will have to take it to cricket which I would prefer not to have to do.
Click to expand...
Click to collapse
You can not restore a nandroid from one kernel to another without having problems even with wiping. You can try to flash the Mx2 versions they don't ask for the kernel check but you might still have problems on 2.3.5.
appl3mac said:
You can not restore a nandroid from one kernel to another without having problems even with wiping. You can try to flash the Mx2 versions they don't ask for the kernel check but you might still have problems on 2.3.5.
Click to expand...
Click to collapse
Yeah I started to think that that could have been the issue, that it was still running the 2.3.5 kernel. Well I saw no other option so I decided to SBF back to 2.3.4, and it somehow now has the PC Mode option, so I can do the Cricket flash on that now. Weird that it didnt have that option the last time I did the SBF. Guess it should work now, will post a final update once I get the Cricket flash and CM10 reflashed.
Stick with 2.3.4 for Cm7, definitely if that is what your Nandroid is from. 2.3.5 is so limited as to what is developed for it.
tallyforeman said:
Stick with 2.3.4 for Cm7, definitely if that is what your Nandroid is from. 2.3.5 is so limited as to what is developed for it.
Click to expand...
Click to collapse
Yeah I got it all figured out, gonna run CM9. I've reflashed to Cricket so many times by now I can do it in 5 minutes or less lol. Thanks for the input guys.
CM9 is full of bugs.... you sure?
Sent from my DROID RAZR HD using Xparent Cyan Tapatalk 2
GoClifGo05 said:
CM9 is full of bugs.... you sure?
Sent from my DROID RAZR HD using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Yeah, I've been using it for 2 solid days now and other than a little battery drain and the very occasional random reboot I would say it's running really good. I'm just sick of Gingerbread and after trying CM10 I decided I won't be going that route until a couple more alphas are released.