(Edited 8/1/11)
Gingerbread update for the droid x2 is now available to soak testers (2.3.3) !
Non-Rooted (stock) Gingerbread update file
Pre-Rooted Gingerbread Update file
(Links are from p3Droid's website, you'll need to create an account there, which you should do anyway- he's the one that did all the work pre-rooting!)
Thanks to P3Droid for his work on pre-rooting the gingerbread update!
Instructions:
Download Either one of the aforementioned links (the prerooted if you want root, the stock if you don't)
Rename whichever file you choose to "update.zip" and place it in the ROOT of your external SDCard.
-----
If you downloaded the pre-rooted:
Your phone needs to be in complete stock for the update to work. SBF it if you debloated or rooted.
After SBFing, do a factory reset. Reactivate your phone, and reroot it using Gingerbreak. (Credits go to their respective developers)
Install Tenfar Lin's recovery. (Credits go to their respective developers)
Boot into system recovery and install update from sdcard. Select update.zip and install! It should automatically perform another factory reset, but if it doesn't, perform another manually.
Start up, reactivate, and you're done!
----
If you downloaded the non-rooted:
Your phone needs to be in complete stock for the update to work. SBF it if you debloated or rooted.
Power off your phone, and enter stock recovery. Select "Install from SDcard:update.zip" or whatever the command is called.
Once finished, reboot and you should be set!
-----
If you are unsure on how to SBF your phone:
Download daywalker04's SBF leak file and extract it.
Download and install the latest moto drivers from Motorola's website itself.
Download and install RSDLite 5.3 here. Reboot your computer.
Start RSDLite and select the downloaded SBF file.
Power your phone off. Turn it back on, and as soon as you see the "DualCore" screen, hold the power button and the volume down button.
Once you see text at the top, use the volume down button until you see "RSD" and hit the up-volume button.
Plug your phone into your computer.
RSDLite should detect a Daytona device - select it and hit start. Once completed, your phone should reboot and be at complete stock.
Photo?
Sent from my DROID X2 using XDA Premium App
Are you rooted? I'm wondering if I need to unroot.
Sent from my DROID X2 using XDA App
Its rolling now. Just updated! Good luck kids.... I couldn't grab the update, so hopefully someone else does.
Off to play now!
I am indeed rooted- but the update is only downloading, not installing. So I don't know if it'll install on rooted and debloated phones. I'll post back when I find out.
Sent from my DROID X2 using XDA App
Powered off my phone, turned it back on, tried a manual pull and voila! Off to the races.
Rooted, debloated, and running custom rom- failed
Sent from my DROID X2 using XDA App
Got nothing here but I'm on the west coast. Are you guys on eastern time? Hope I don't have to wait 3 more hours. Anyone tried gingerbreak yet? What version is it?
3UR0TR45H said:
Got nothing here but I'm on the west coast. Are you guys on eastern time? Hope I don't have to wait 3 more hours. Anyone tried gingerbreak yet? What version is it?
Click to expand...
Click to collapse
Yep, I'm in NC
I also have no notice and it says my device is up to date in About phone > System updates, even after a phone reboot.
Somebody post the file!
Post The File(s)!
I got it too! I am downloading on wifi now, 10% done!
P3Droid should have the zip soon. I am still wondering how this is going to work out since there is a new GB kernel. Will a pre-rooted rom with a signed kernel be able to be flashed with the bootstrap?
No time for any review per say, but its fast, and feels solid compared to Froyo on this thing. A lot of new icons too. Anyhow, off to bed.
70%, going MUCH faster on WIFI then 3G.. (Obviously).
Now i did not SBF, i just unfroze everything with BloatFreezer.. I am rooted too.
I'd love to post the file if icould find it, but I can't..
Sent from my DROID X2 using XDA App
Download done, Installing.. (Phone just rebooted).. Just incase i have 100% battery but I'm on the AC Adapter.. Its on the package installer screen now
Hmm dunno if it didn't go, cause about 1/2 way they the package screen it stopped with a Yellow Exclamation mark, rebooted and it and I'm back to froyo i think.. Looks like i am gonna have to sbf it just to make sure and repudiate it.
Never mind this post
Sent from my DROID X2 using XDA App
did you guys sbf to stock? If so, I may ggo do that now even tho its 1am
Related
So a long time ago I rooted my cousins phone and installed gingerblur. And haven't touched the phone sense. Now he wanted to go to gingerbread and I borked his phone. It's working again but am on old 1.26 firmware stock. I've been reading a lot all day and I'm just confused flabbergasted I am plain lost this is way harder then my HTC and Samsung. Well basically could someone tell me or link me to the easiest fastest way to get to gingerbread?
Use the sticky in development to download the 1.8.3 firmware. Use RSD to flash to that. Make sure it is the full and not the service. Root the phone then with gingerbreak. After that there is a sticky in Dev called pudding. Flash that using RSD. Your phone will be unlocked .Then you can flash any rom.
Sent from my MB860 using XDA Premium App
dalrym05 said:
So a long time ago I rooted my cousins phone and installed gingerblur. And haven't touched the phone sense. Now he wanted to go to gingerbread and I borked his phone. It's working again but am on old 1.26 firmware stock. I've been reading a lot all day and I'm just confused flabbergasted I am plain lost this is way harder then my HTC and Samsung. Well basically could someone tell me or link me to the easiest fastest way to get to gingerbread?
Click to expand...
Click to collapse
First do the ota updates to 1.83 then root it using gingerbreak. Next:
1. Unlock your bootloader here:http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
2. instal cwm http://forum.xda-developers.com/showthread.php?t=1138541
2a. MAKE SURE YOU USE THIS CWM: http://forum.xda-developers.com/attachment.php?attachmentid=641508&d=1309404399
3. Mount your phone and put whatever rom you choose that can be installed through .zip on the sd card i suggest kens :http://bandbinnovations.com/xda/gingerbread/Gingerbread-Atrix-Beta-4-5.zip
4. boot into cwm by holding volume down button while powering on and then scroll through until you see android recovery on your phone right under where it says unlocked.once boote...
5. choose instal zip and go to where you saved it
6. install the zip
7. do not reboot yet.
8. clear cache and dalvik(found in advanced) and finally do a wipe data restore.
9. reboot!
Hope this helps!
Great thanks guys I got his phone up and running.
dalrym05 said:
Great thanks guys I got his phone up and running.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1179506
i made a video in case you run into this issue again
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
Major newbie here, so i've gotten up to step 4. but I'm stuck at that.
Q: How do I install Eclipse?
1. sbf to 234
2. Root using MotorolaOneclick
3. Install Voodoo OTA rootkeeper and protect root but temp unroot
4. Apply 235 update in stock recovery
5. Restore root in Voodoo rootkeeper and delete backup (make sure root is restored before deleting!)
6. Install bootstrap
7. Reboot into bootstrap recovery
8. Wipe data
9. Flash eclipse
10. Profit from its beauty
How do I apply the 235 update in stock recovery, and how do I get that? And also, how do you do number 8 and 9, sorry if this is too much to ask. I'm new to this and don't want to go without directions, but sadly to a newbie, this aren't very helpful.
You can look into he droid x2 android development forum forum here or just dl 2.3.5 as if you were updating from your provider, by going to: settings/about phone/system updates.
8 and 9 are options in bootstrap recovery after you perform step 7
Sent from my Xoom using xda app-developers app
Yea take the update they way mombof told you, then open Voodoo OTA rootkeeper and restore root. It is IMPORTANT that after you restore the root you delete the SU Backup in the program or Eclipse install will fail.
Then download Boostrap Recovery from here: http://forum.xda-developers.com/showthread.php?t=1318083
Once it is installed Enter BSR following the directions in the link above and you will see "Wipe Data/Factory Reset" Select it
Then still in BSR you will see "Install zip from sd card" Select it then select "Sd Card" and find The eclipse Zip you should have downloaded and placed on your external sd card. And that's it.
EDIT: By the way 2.3.5 is rootable, I don't know why anyone would do the long method anymore. Just saying. http://forum.xda-developers.com/showthread.php?t=1818758
GoClifGo05 said:
Yea take the update they way mombof told you, then open Voodoo OTA rootkeeper and restore root. It is IMPORTANT that after you restore the root you delete the SU Backup in the program or Eclipse install will fail.
Then download Boostrap Recovery from here: http://forum.xda-developers.com/showthread.php?t=1318083
Once it is installed Enter BSR following the directions in the link above and you will see "Wipe Data/Factory Reset" Select it
Then still in BSR you will see "Install zip from sd card" Select it then select "Sd Card" and find The eclipse Zip you should have downloaded and placed on your external sd card. And that's it.
EDIT: By the way 2.3.5 is rootable, I don't know why anyone would do the long method anymore. Just saying. http://forum.xda-developers.com/showthread.php?t=1818758
Click to expand...
Click to collapse
Alright so, I followed the directions up to where you get into the Bootstrap recovery, once I go into recovery mode from the app, it shows the "Dual Core Technology" screen and nothing else.
Did you press install recovery from within the app before pressing recovery mode? And are you plugged in to a wall charger? You must be plugged in. Just pull your battery and put it back to reboot your phone. If you did press install recovery first then once you pull your battery and put it back in just leave your phone off and plug it into a wall charger and it will boot in to recovery.
Sent from my DROID X2 using xda app-developers app
GoClifGo05 said:
Did you press install recovery from within the app before pressing recovery mode? And are you plugged in to a wall charger? You must be plugged in. Just pull your battery and put it back to reboot your phone. If you did press install recovery first then once you pull your battery and put it back in just leave your phone off and plug it into a wall charger and it will boot in to recovery.
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
That's exactly what I did. If it matters, when I first pressed install recovery and Recovery mode, it never went to the battery screen in the first place, it went to the dual core screen.
And also, I'm on 2.3.4 if that matters anything.
Um ok a couple things. ***Do not install eclipse because it is for 2.3.5. You should have backed up root in Voodoo, Temp unrooted, gone to Settings-->About Phone-->System Update and taken the 2.3.5 update. Opened Voodoo OTA rootkeeper, restored root, deleted SU backup and then installed bootstrap recovery.
When you download the zipped BSR on your computer you should have unzipped it, placed it on your external sd card, Used file manager on your phone to find it, press it, package install. Then open "System Recovery" app and pressed install recovery. Plug your phone into the stock wall charger that came with your phone and then pressed "recovery mode" leaving it plugged in.
It doesnt matter that BSR is installed now, take the 2.3.5 update following the steps above and then once you are rooted again and SU backup is deleted press install recovery again, and press recovery mode. It wont boot to a battery screen, it will shut off and restart into the recovery menu, but you will see the red dualcore screen first for a few seconds. Leave it plugged in and wait a minute.
GoClifGo05 said:
Um ok a couple things. ***Do not install eclipse because it is for 2.3.5. You should have backed up root in Voodoo, Temp unrooted, gone to Settings-->About Phone-->System Update and taken the 2.3.5 update. Opened Voodoo OTA rootkeeper, restored root, deleted SU backup and then installed bootstrap recovery.
When you download the zipped BSR on your computer you should have unzipped it, placed it on your external sd card, Used file manager on your phone to find it, press it, package install. Then open "System Recovery" app and pressed install recovery. Plug your phone into the stock wall charger that came with your phone and then pressed "recovery mode" leaving it plugged in.
It doesnt matter that BSR is installed now, take the 2.3.5 update following the steps above and then once you are rooted again and SU backup is deleted press install recovery again, and press recovery mode. It wont boot to a battery screen, it will shut off and restart into the recovery menu, but you will see the red dualcore screen first for a few seconds. Leave it plugged in and wait a minute.
Click to expand...
Click to collapse
First of all, thanks a ton for helping me.
So I backed up my root, and temp un-rooted my phone and went into my system update but it was grayed out. I tried the *#*#checkin#*#*, where you call that and it should force the update to 2.3.5, but it still didn't put me into 2.3.5. I factory restored my phone, SBF'd to 2.3.5 as directed by the root guide you gave to me a couple posts back, rooted my phone, downloaded BSR onto my phone, gave it superuser permission. I then plugged my phone into the wall outlet, installed recovery, and then went into recovery mode and it's showed me the dual core screen for about 5 minutes or so, still being plugged into the wall outlet.
I then pulled the battery from the back, and unplugged the phone. I put the battery back in, and plugged the phone back in and it went straight to the dual core screen.
Has this ever happened to people before me? Or am I just doing something terribly wrong and I don't even know it.
Something is not right. However if you rooted your phone using Magic root method bsr should have already been installed on your phone. You're not using the CM7 patched BSR for any reason are you? Do me a favor and try something. In system recovery app click charge mode, turn off your phone and plug it in, tell me if you see the battery icon again.
Are you 100% sure you are rooted and busybox is installed before trying to install BSR? Download rootchecker or android terminal emulator to make sure root worked.
Try uninstalling the bootstrap you added then reinstalling it. Or do a data wipe in stock recovery and reinstall it after.
when using magic md5 root, be careful not to click continue, until phone has completed reboot
or you will skip steps
If you're still having trouble, I strongly recommend Pete"s Motorola Root Tools. It has a one click root option as well as an un-root option, and its very easy to use. I've used it at least 6 times after sbf-ing without problem.
you can't root 2.3.5 with pete's
edit: motorola one click is pete's
Sent from my DROID X2 using xda premium
sd_shadow said:
you can't root 2.3.5 with pete's
edit: motorola one click is pete's
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Whoops, my bad. Assumed he was going back to 2.3.4.
unnecessary, as 2.3.5 is rootable now
and if you are flashing eclipse, you need to be on 2.3.5
E:signature verification failed during Eclipse install
sd_shadow said:
unnecessary, as 2.3.5 is rootable now
and if you are flashing eclipse, you need to be on 2.3.5
Click to expand...
Click to collapse
Read your great advice to the previous posts. I am having trouble installing the Eclipse ROM as well. Recently replaced a Droid X with a Droid X2 running stock GB 2.3.5. Rooted phone and tried to install Eclipse, but the installation failed twice with error of: "e:signature verification failed".
I have been searching forums for the past two days trying to find the problem, but have not had any luck.
I have ROM Manager and ROM Toolbox installed, if that info helps.
Thanks for your help!:good:
Rom manager doesn't work on x2
If you used ota root keeper remove su backup
Sent from my MB870 using xda premium
sd_shadow said:
Rom manager doesn't work on x2
If you used ota root keeper remove su backup
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Thanks for the reply.
I rooted using a self extracting batch file off of the Droid X forum, and I don't think OTA Rootkeeper was any part of that, (Don't see it in my app folder)
Not sure if there is a super user backup, could not find it anywhere..
Any ideas would be appreciated!
Thanks
Could try re downloading eclipse
Sent from my MB870 using xda premium
sd_shadow said:
Could try re downloading eclipse
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Dude, you are my hero! Sometimes the the easiest solutions are best. Downloaded a new copy of the eclipse zip file, (noticed that the file size was different from the old one. Hmmm!), Performed another nandroid and titanium back up, reinstalled eclipse...tada! No error!
Thanks!
That's why you should compare md5 checksums on every download
Md5 checker is in my list
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
Sent from my MB870 using xda premium
I'm having trouble finding a specific answer to my question so please allow me to be a noob...
I have an X2 running Android 2.3.5 / System Version 1.3.418. I rooted my phone using the automatic method and I've installed system recovery. My question is, can I wipe and flash Eclipse 2.3 directly from recovery on this phone now or do I need to drop back to 2.3.4 like the directions say? Is that out of date?
Also, do I need to get Gapps or is that packaged with Eclipse?
Thanks for the help. I've flashed my Galaxy Tab 10.1 with AOKP, but this is the first time I've dealt with Moto.
Yes you should be able to if you have recovery/bootstrap installed and superuser .if I remember right it has gapps baked in.
don't be scared it's only a phone
ogd x d2g x2 sg3
old ladies ^
Bad Bone, thanks for your reply.
I just did it and everything worked great. Flashing Eclipse is like having a new phone. FYI to other newbs, the instructions in the Eclipse 2.3 thread are wrong if you have 2.3.5. Just use the latest root for that version, install the recovery program once you have root and then boot into recovery to flash the .zip.
It's working perfectly and it's totally awesome. Glad I took the plunge.
Nice
don't be scared it's only a phone
ogd x d2g x2 sg3
old ladies ^
The directions were before we had magic md5 so rootkeeper on 2.3.4 before update to 2.3.5 was the only way to root. Now we can root after update.
Sent from my DROID X2 using xda app-developers app
now that you have suceeded...maybe you can help me?
circuitloss said:
Bad Bone, thanks for your reply.
I just did it and everything worked great. Flashing Eclipse is like having a new phone. FYI to other newbs, the instructions in the Eclipse 2.3 thread are wrong if you have 2.3.5. Just use the latest root for that version, install the recovery program once you have root and then boot into recovery to flash the .zip.
It's working perfectly and it's totally awesome. Glad I took the plunge.
Click to expand...
Click to collapse
I have the exact same situation, have root, but a little lost on the eclipes installation procedure..I don't get the boot into recovery part i think..?
download Droid X2 BSR
may have to unzip with 7 Zip
move MOTODX2_Bootstrap_signed.apk and rom's zip(do not unzip rom) to sd card
using phones file manager, find MOTODX2_Bootstrap_signed.apk and tap on it, select installer, close file manager, go to app drawer, open 'system recovery' app,
tap the "Install Recovery" ,allow root, connect wall charger, tap the "Recovery Mode" button to reboot the phone into recovery
create a backup, wipe data, wipe cache, install zip from sd card (not install update.zip) select rom's zip (X2-Eclipse-v2.3.zip), select reboot, done....
How to video's. sbf, root, nandroid backup, and restore
ok....i'll give it a try..
Thank you very much. will be going for it soon...
it worked!
Thanks to you it works and I am a more experienced Noob!
HELP!!!!
I'm a semi-amateur at rooting, and I'm worried I bricked my wife's Droid Razr MAXX. Here's what happened:
A year ago, I rooted her Razr and installed safestrap, which came with its TWRP interface. It had been running slow, so yesterday I said I'd put her on a new ROM. I installed CM 10.1.3 and everything seemed to go smoothly. After I'd finished the install of the ROM, using safestrap and TWRP, I reinstalled all her apps and everything.
Then I reinstalled SuperSU, VooDoo OTA Rootkeeper, and Safestrap v2.11. I ran safestrap and noticed it said it didn't have custom recovery installed, even though I knew it did. I don't know why, but I hit the button to install custom recovery.
Well, her phone was being screwy so she reset it at work. It then began to bootloop, and she turned it off (power + vol up + vol down). I turned it on, the safestrap splash screen showed, and I hit "menu" to boot into recovery.
Instead of TWRP, I am getting the green and black stock recovery screen. Uh oh, right? So I don't know what to do now. I wiped cache and dalvik to see if it'd reboot, but still, it bootloops.
Do I hit "Disable Safestrap (if stuck in recovery)"? I'm afraid to do anything at this point, out of fear of bricking her device. Any help would be greatly appreciated!!!
Download RSD Lite 5.7 and download the 4.1.2 firmware here
http://sbf.droid-developers.org/cdma_spyder/list.php make sure you have a good charge on the phone, (it won't charge in fastboot) then open the firmware in RSDlite extract, put your phone in fastboot mode (Vol+ Vol- power select fastboot) plug the phone into your computer using your micro USB that came with the phone. Wait for files to extract then flash. Hope this helps. Any further questions you can send me an IM at [email protected]
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 01:29 AM ---------- Previous post was at 01:27 AM ----------
This will bring you back to stock but you can easily re root.
Sent from my DROID RAZR HD using xda app-developers app
eolsgaard said:
HELP!!!!
I'm a semi-amateur at rooting, and I'm worried I bricked my wife's Droid Razr MAXX. Here's what happened:
A year ago, I rooted her Razr and installed safestrap, which came with its TWRP interface. It had been running slow, so yesterday I said I'd put her on a new ROM. I installed CM 10.1.3 and everything seemed to go smoothly. After I'd finished the install of the ROM, using safestrap and TWRP, I reinstalled all her apps and everything.
Then I reinstalled SuperSU, VooDoo OTA Rootkeeper, and Safestrap v2.11. I ran safestrap and noticed it said it didn't have custom recovery installed, even though I knew it did. I don't know why, but I hit the button to install custom recovery.
Well, her phone was being screwy so she reset it at work. It then began to bootloop, and she turned it off (power + vol up + vol down). I turned it on, the safestrap splash screen showed, and I hit "menu" to boot into recovery.
Instead of TWRP, I am getting the green and black stock recovery screen. Uh oh, right? So I don't know what to do now. I wiped cache and dalvik to see if it'd reboot, but still, it bootloops.
Do I hit "Disable Safestrap (if stuck in recovery)"? I'm afraid to do anything at this point, out of fear of bricking her device. Any help would be greatly appreciated!!!
Click to expand...
Click to collapse
Did you try to install SS from within CM? SS is intended to be installed and managed on stock. Did you install CM on a new slot in recovery?
Also, the latest SS version is 3.60.
For future reference, your actions should've been these:
1. Uninstall custom recovery using whatever SS you have installed on stock.
2. Uninstall SS and install newest SS version.
3. Install custom recovery using the newly installed SS.
4. Reboot into TWRP, create NEW slot and flash ROM.
Right now, I'd recommend what nickmoogo said above - start fresh, and do everything in order this time around, good luck!
CruxHumanus said:
Did you try to install SS from within CM? SS is intended to be installed and managed on stock. Did you install CM on a new slot in recovery?
Also, the latest SS version is 3.60.
For future reference, your actions should've been these:
1. Uninstall custom recovery using whatever SS you have installed on stock.
2. Uninstall SS and install newest SS version.
3. Install custom recovery using the newly installed SS.
4. Reboot into TWRP, create NEW slot and flash ROM.
Right now, I'd recommend what nickmoogo said above - start fresh, and do everything in order this time around, good luck!
Click to expand...
Click to collapse
That's exactly what I did. I have no idea why I did it either. Since I was on v2.11, clearly it's been a while since I touched her phone. So there's no way other than starting over from stock firmware, huh? If I could just get back to the TWRP interface I'd be much more comfortable, but I know SS's version of TWRP is unique. If starting fresh is the safest bet, that's what I'll do. Thanks guys!
eolsgaard said:
That's exactly what I did. I have no idea why I did it either. Since I was on v2.11, clearly it's been a while since I touched her phone. So there's no way other than starting over from stock firmware, huh? If I could just get back to the TWRP interface I'd be much more comfortable, but I know SS's version of TWRP is unique. If starting fresh is the safest bet, that's what I'll do. Thanks guys!
Click to expand...
Click to collapse
Someone more knowledgeable than myself could maybe advise more in this case. Start fresh is what *I* would've done.
Flashing stock is not that hard of a procedure, and after installing some roms and finding the one that works the best for you, you won't be seeing much of stock anyways, I know I don't.
dead link
nickmoogo said:
Download RSD Lite 5.7 and download the 4.1.2 firmware here
http://sbf.droid-developers.org/cdma_spyder/list.php make sure you have a good charge on the phone, (it won't charge in fastboot) then open the firmware in RSDlite extract, put your phone in fastboot mode (Vol+ Vol- power select fastboot) plug the phone into your computer using your micro USB that came with the phone. Wait for files to extract then flash. Hope this helps. Any further questions you can send me an IM at [email protected]
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 01:29 AM ---------- Previous post was at 01:27 AM ----------
This will bring you back to stock but you can easily re root.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
i know that post is 2years old but am in the same mess here. can i get a working link
SwayMontana said:
i know that post is 2years old but am in the same mess here. can i get a working link
Click to expand...
Click to collapse
Links in the index, but you need to use correct version
Bootloader version must match, or at least it cannot be downgraded.
http://forum.xda-developers.com/showthread.php?t=3023837
[INDEX] Motorola Droid Razr Development (2015)
Sent from my XT912 using Tapatalk