I have my phone rooted and BSR/busybox/superuser installed. How do I flash it and actually put the rom on the phone?
(P.S. Its eclipse 2.1)
Well you have a lot of reading to do but let me give you a few important tips:
1) Before doing anything else make sure to go into your BSR and make a nano back up of your stock system. If you do not know how to do nano back ups then read up on that. You will be doing that for different roms. http://forum.xda-developers.com/showthread.php?t=1318083
2) Make sureyour kernal matches the version of the rom. For example you want to flash eclipse 2.0+ this is made for 2.3.5 update. If you are stock you are probably 2.3.4 Some have flashed eclipse 2.0+ and had no issues but it is not recommended.http://forum.xda-developers.com/showthread.php?t=1313103
this thread should help you out a lot also.
3) Once you get your stock Rom backed download the rom of your choice onto your sd card. Go back into BSR and first wipe data factory reset, wipe partion cache, go into advance and wipe Dalvik cache. Once you wiped the big 3 go to install from sd. Locate the rom using your volume buttons and power button to select. Sit back and let the rom run. Once it is done you can reboot now or flash one more safety step. It is the rerecovery zip. This actually allows you to restore your phone easy in the case of something bad happens. If you boot loop or something goes wrong then you just pull your battery and give it about 30 seconds. Put the battery back in and leave the phone off and just plug it into the wall charger. This will bring you straight to BSR. Here is that link http://forum.xda-developers.com/showthread.php?t=1426062
Also remember as long as you can get into BSR you can restore your nano backup of choice. Good luck and have fun. If you run into trouble we can help you out. The phone is pretty easy to fix.
I have made my recovery but was told it is ok to install Eclipse 2.1 on 2.3.4. I have the file downloaded but am I going to have to reprogram my phone for service?
If I'm not mistaken, flashing eclipse 2.1 on Android 2.3.4 can cause some Wi-Fi and data problems, so I highly recommend sbf-ing android 2.3.5 before flashing eclipse. Ill link a comprehensive sbf guide at the end of this post. To answer your question, though, you shouldn't have to activate your phone again if you havent sbf-ed or updated android. If you do decide to use 2.3.5, you will have to activate your phone again, though it only takes about 30 seconds in my area (could take more or less time depending on your signal strength).
http://forum.xda-developers.com/showthread.php?t=1317707
Hope I could be of assistance. If you need help, feel free to ask. I have no life so ill be here all day.
theredvendetta said:
If I'm not mistaken, flashing eclipse 2.1 on Android 2.3.4 can cause some Wi-Fi and data problems, so I highly recommend sbf-ing android 2.3.5 before flashing eclipse. Ill link a comprehensive sbf guide at the end of this post. To answer your question, though, you shouldn't have to activate your phone again if you havent sbf-ed or updated android. If you do decide to use 2.3.5, you will have to activate your phone again, though it only takes about 30 seconds in my area (could take more or less time depending on your signal strength).
http://forum.xda-developers.com/showthread.php?t=1317707
Hope I could be of assistance. If you need help, feel free to ask. I have no life so ill be here all day.
Click to expand...
Click to collapse
I have managed to softbrick my phone. No it is stuck on the "dual core technology" screen and I can't do anything
Spanks906 said:
I have managed to softbrick my phone. No it is stuck on the "dual core technology" screen and I can't do anything
Click to expand...
Click to collapse
Have you pulled you battery and tried it again? If you have I'd sbf back to 2.3.4 and then update to 2.3.5 then root it, and then install BSR and go into recovery and like said above, wipe the "big 3," install the ROM and then reboot and see if that helps.
Spanks906 said:
I have managed to softbrick my phone. No it is stuck on the "dual core technology" screen and I can't do anything
Click to expand...
Click to collapse
I tried installing it just now... It gets past the dual core but sticks on the ECLIPSE loading screen... wtf? any idea how to load the original os?
GaryMcDroid said:
I tried installing it just now... It gets past the dual core but sticks on the ECLIPSE loading screen... wtf? any idea how to load the original os?
Click to expand...
Click to collapse
Sbf back to 2.3.4....its not too hard. Search for it.
Sent from my MB870 using xda premium
Related
I was trying about 10 days to install any 2.3.4 based rom on my AT&T atrix!
Everytime i trying to flash some rom (mostly i've tried Alien's and Cherry) i see bootloop: red circle with "M" >at&t logo >"M">"M">"M"... I have an unlocked bootloader, can see the sign "Unlocked" ot top of the screen, Rooted And CWM Recovery by tefnar installed, BUT EVERY TIME i flashing some rom i stucking on that bootloop. I was trying to search on xda a lot of time, still cannot find the answer. That makes me real sick of it, i'm not sleeping at nights, pleeeaseeee heeeelp!!!
How long are you waiting for your phone to boot. It can take a while. 10+ minutes.
I waited until yesterday to update to 2.3.4 because I was on call.
Things I did.
1) Made sure that I had the lastest CWM.
2) Made sure I had the latest pudding.
3) I installed 2.3.4 pudding first. Note: I had to re-install CWM after this. Not a huge deal since it installed from fast boot.
4) Followed the ROM install steps here
5) Installed the recommended radio.
6) After that it should work. I had to install the webtop and the ad block but have had no problems since.
I am now trying to decide what Kernel to mess with.
First install rom racers recovery. Two. Make sure youre wiping everything before and after you flash, unless youre upgrading the same rom, you dont have to but still recommended. Three, be patient on initial boot of a fresh flash. Sometimes it can take awhile and might reboot still.
I voided my warranty.
lemortede said:
How long are you waiting for your phone to boot. It can take a while. 10+ minutes.
I waited until yesterday to update to 2.3.4 because I was on call.
Things I did.
1) Made sure that I had the lastest CWM.
2) Made sure I had the latest pudding.
3) I installed 2.3.4 pudding first. Note: I had to re-install CWM after this. Not a huge deal since it installed from fast boot.
4) Followed the ROM install steps here
5) Installed the recommended radio.
6) After that it should work. I had to install the webtop and the ad block but have had no problems since.
I am now trying to decide what Kernel to mess with.
Click to expand...
Click to collapse
I was waiting approx. 5 minutes, but is that suppose to be like that? I mean flashing screen on a bootloop? Because fading screen, when reboot looks like if i take battery out everytime. Besides, i've installed any of gingerblur or greyblur easily, but when trying to install 2.3.4, see that crap again.
I'm using all latest (CWM, Divers, RSD...)
Are you wiping both the system cache and dalvik cache before you flash the rom?
Sent from my MB860 using XDA App
iRobby said:
Are you wiping both the system cache and dalvik cache before you flash the rom?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I Do. Maybe here some thing i've missed before. Now I have 4.1.83 on board, and can install any of 2.2.x, but NOT 2.3.4 Why?
Is the OTA update only wayout??
thread still actual. UP
There is probably some ridiculous, overwhelmingly simple reason for the answer to this question, but take into account that its coming from the guy who has been trying install a ROM for a week unsuccessfully, Anyway, enough personal degradation for the moment, and on to business. It seems to me that every time I have to .spf it gets easier and faster(imagine that). RSDlite is such a perfect format flashing, so why has no one thought of a way to flash ROMS via RSDlite? I understand that getting your proverbial elbows greasy is the fun of this, but for the helpless and hopeless, such as myself, there should be a super simple segue into cool techy stuff for us too!! I'm kidding, I'm not that buried.....I think.
Why would you sbf a rom when it only only takes a couple of minutes to flash a rom?
1, are you rooted?
2, do you have tenfar bar installed?
3, is the rom of choice on SD card?
Where are you having your trouble what rom? How are you trying it? It is pretty simple.
MathiasKnight said:
There is probably some ridiculous, overwhelmingly simple reason for the answer to this question, but take into account that its coming from the guy who has been trying install a ROM for a week unsuccessfully, Anyway, enough personal degradation for the moment, and on to business. It seems to me that every time I have to .spf it gets easier and faster(imagine that). RSDlite is such a perfect format flashing, so why has no one thought of a way to flash ROMS via RSDlite? I understand that getting your proverbial elbows greasy is the fun of this, but for the helpless and hopeless, such as myself, there should be a super simple segue into cool techy stuff for us too!! I'm kidding, I'm not that buried.....I think.
Click to expand...
Click to collapse
Okay, looks like you created a new thread about the same issue...but moving on.
RSD Lite is a Motorola tool, that was initially just supposed to be used by retailers (like VZW and Radioshack) so that they could reset people's phones rather than having to ship the to Moto and send them back to the customer, or for VZW and others to wipe devices and resell them as "refurbished" units. The reason we can't use RSD to create ROM's is the SBF files are signed by Motorola. So if we were to modify them in anyway or try to make our own, it would refuse the files and not flash the device.
Now, from your other thread you posted this:
MathiasKnight said:
Sorry about that, I must have been excited. Unfortunately I spoke too soon. Either that or I'm not meant for this, which I hope is not the case seeing that I'm getting my degree in IT. I finally get bootloader, with ROM and GAPPS placed accordingly(I opted for Eclipse). When the zip is finished uploading and I see confirmation that all was installed correctly, I begin the reboot......and it takes new to an unactivated Droid X2. I've created nandroid after nandroid, with different methods and different ROMS, and I either land there or with a signature error, even in bootstrap. I'm gonna try one more time before I hang up my guns. Maybe.....
Click to expand...
Click to collapse
Could you please outline everything you do, step by step? After you SBF you should have to activate your phone anyway, so that after you root, install bootstrap and then boot into that and apply the ROM and GAPPs the phone should already be activated.
Travisdroidx2 said:
Why would you sbf a rom when it only only takes a couple of minutes to flash a rom?
1, are you rooted?
2, do you have tenfar bar installed?
3, is the rom of choice on SD card?
Where are you having your trouble what rom? How are you trying it? It is pretty simple.
Click to expand...
Click to collapse
The only time I have gotten any response that remotely resembled success was the first time I used System Recovery, but the status bar was incredibly slow, like not moving basically, so I figured after about 25 minutes something was amiss...again. Yes I'm rooted, don't know what a tenfar bar is yet but I'm on it now, and I've got a variety of .zip's that are supposed to be compatible with 2.3.4, and I'm sure they are. I was really kind of joking about the .sbf, but I still think it would be a viable alternative.
MathiasKnight said:
The only time I have gotten any response that remotely resembled success was the first time I used System Recovery, but the status bar was incredibly slow, like not moving basically, so I figured after about 25 minutes something was amiss...again. Yes I'm rooted, don't know what a tenfar bar is yet but I'm on it now, and I've got a variety of .zip's that are supposed to be compatible with 2.3.4, and I'm sure they are. I was really kind of joking about the .sbf, but I still think it would be a viable alternative.
Click to expand...
Click to collapse
Okay, so you've SBF'd to 2.3.4. Rooted using whatever method, and you have the BootStrap recovery installed yes? Then you boot into recovery, wiped data, wiped cache and wiped dalvik cache, then tried installing a zipped ROM from you sd card, and upon restarting you get stuck at the moto M screen?
A couple things. First, when you wipe the dalvik cache (for roms or any mods) the phone has to rebuild that before it can actually boot into Android. This can take anywhere from a few minutes to 5 minutes or upwards. If you've gone 10 minutes and still nothing, all you need to do is pull the battery (so the phone powers off), reinstall the battery, DONT TURN THE PHONE ON, and then plug your phone into your wallcharger. After you plug in your phone, it'll turn itself on, go to the M screen and then go back into the BootStrapRecovery. From there you can redo the steps, wipe everything and then reinstall. However, IF you boot into the stock Android Recovery and wipe cache and data from there, you mucked it up and you'll have to SBF and restart the process.
ALSO, from your previous thread you said you were trying to install Eclipse. What version are you trying? 1.xx eclipse will work on 2.3.4, but Eclipse 2.xx will only work on 2.3.5, which could be another reason you are having issues.
I have been runnig CM9 for about two weeks. Really liked it.
Thought I would flash the build.props mashup. After I did I started getting the following message:
process com.android.phone is not responding. Couldn't do anything but pull the battery.
Plugged into power strip.
Went into CM7 Patched Recovery recovery. Wipe Cache and Dalvik. No change.
Wipe Data. No change.
Also ran Fix Permissions. No change.
Don't ask me why but I ran Key Test.. BAD MOVE. Couldn't get out of Key Test.
Pulled battery again.
Still plugged into power strip. Now I am stcuk at the red Motto M and can't get past it.
If I unplugged and reboot CM9 will start but again I get process com.android.phone is not responding.
Any help would be greatly appreciated.
The reason it messed up is because the mash up is already built into CM9 and probably has different tweaks by dragonzkiller. If you can still get into the recovery, try flashing the CM9 ROM zip again. It should overwrite the problem.
EDIT: Actually if you already wiped data, you may not be able to get into BSR. So if you cant get into the system, you may have to SBF. Unless you can use ADB to push BSR to the phone which I dont know how to do or even if it will work. I've never used that but read people talking about stuff like that.
If you cant fix it, follow the instructions here to reset your phone:
http://forum.xda-developers.com/showthread.php?t=1317707
Thanks - nnow on the root!
SBF worked fine. Thanks.
Back on 2.3.4. On to root, except my employer has blocked to down site..
and then on to CM7 and CM9.
Thanks again JS
jsgraphicart said:
The reason it messed up is because the mash up is already built into CM9 and probably has different tweaks by dragonzkiller. If you can still get into the recovery, try flashing the CM9 ROM zip again. It should overwrite the problem.
EDIT: Actually if you already wiped data, you may not be able to get into BSR. So if you cant get into the system, you may have to SBF. Unless you can use ADB to push BSR to the phone which I dont know how to do or even if it will work. I've never used that but read people talking about stuff like that.
If you cant fix it, follow the instructions here to reset your phone:
http://forum.xda-developers.com/showthread.php?t=1317707
Click to expand...
Click to collapse
Glad you got it back to working condition. Next time you have a problem like that, flashing the ROM again should take care of it. If not, try to always have a ROM backup on hand.
And also, stay away from mashup when on CM9 as well as the Test Keys function in CM7 recovery.
If I hadn't foolishly done Test Keys my next step was to flash the ROM again.
Thanks again.
jsgraphicart said:
Glad you got it back to working condition. Next time you have a problem like that, flashing the ROM again should take care of it. If not, try to always have a ROM backup on hand.
Click to expand...
Click to collapse
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737
So I got bored and decided to start messing with my old X2. It is rooted with Eclipse V2.3 ROM. All I did was change the theme a couple times. Worked perfect for the first two or three but then I found one that caught my eye.
This one here.
http://forum.xda-developers.com/showthread.php?t=1380719
It installed fine, liked the look, but had two problems right off the bat. First was that Eclipse Tools kept force closing so there was no way to get into bootstrap recovery. Second was when I pressed the power button, it would only reboot the phone, nothing else. So I decided to do a factory data reset on it to see if that would fix it...
It did the reset, but now it is stuck in the bootscreen. It gets past the red M, but that's it. Is it bricked or is there something I can do to get it back? I wouldn't mind doing a SBF and/or totally rerooting it again, but I need to find out how to do this while stuck in the boot screen with no way to get into recovery. Can anyone help me out?
if you are on eclipse 2.3, blue neon steel is for 1.3, not the version you are on. this is why youre having problems. 1.3 is based on 2.3.4, and 2.3 is based on 2.3.5 , so themes are not backwards compatable. or any compatable, it should be made specifically for your version of eclipse. ble neon is also my favorite theme, but an update for 2.3 seems unlikely, as i have tried to contact kevin about it before. everyone has moved on to other phones. a strong few still deal with this beast.
Well crap... Didn't even think about that. I have the other themes on my SD card, all I need to do is get into Bootstrap Recovery so that I can install the zip file. Is there a way to get into Bootstrap Recovery from a power off state?
ramthis9501 said:
Well crap... Didn't even think about that. I have the other themes on my SD card, all I need to do is get into Bootstrap Recovery so that I can install the zip file. Is there a way to get into Bootstrap Recovery from a power off state?
Click to expand...
Click to collapse
Try the Motorola system recovery by holding down volume down and power button. Wipe data and cache partition.
Did you ever install the bootstrap recovery? If so, try plugging in your charger with phone off to see if it will boot into bsr. Try this step first, then if that doesn't work try system recovery. If neither of these work you will more than likely need to sbf.
Sent from my Droid X2 using Tapatalk 2
Just plugged it in and it's stuck on the red M. I tried using stock recovery earlier and it didn't fix the problem either so hopefully SBF will be my rescue. Thanks for the help
give cm10 a try while youre on 2.3.4 :good: