Related
Up until today I never did anything to my droid x as far as rooting and roms. I kept everything completely factory and android was at its latest version which is gingerbread 2.3.3 and system version 4.5.605.MB810.Verizon.en.US.
My goal today was to finally experiment this and install Liberty Rom. I completely failed because of all the version complications and plenty of other errors. Before I describe my final problem I should backtrack and let you know exactly what I did today so you can possibly get me out of this mess.
1. The very first thing I did was follow all of the steps at a forum on droid-life "How To: Get Rooted Gingerbread On DROID X" sorry it won't let me post the link.
After all of this I ended up with gingerbread again, but I guess a rooted version. No idea why this was the tutorial I followed when trying to install liberty. Throughout the tutorial I ended up buying "Droid X BootStrapper" because the tutorial had me use it.
Right after this tutorial I bought an app called Rom Toolbox for $5.00 downloaded Liberty through it and was trying to install through it. Every time it rebooted I would get a black screen. Never worked so many issues probably because I flashed the wrong sbf or something.
Here are the programs that I ended up buying today:
z4root (free), DroidXBootStrapper ($2.00), Rom Toolbox ($5.00).
That is everything I have done and all of the apps I own. Can someone please start fresh and give me short instructions to start from scratch on how to get the latest and greatest version of Liberty on my droidx from where I'm stuck at now. I want to completely start over and I am willing to do anything. I hope the apps I bought help and I also want to assume 2 of them probably do the same thing and I didn't need them.
Buying those tools will at least help support 2 members of the community (Koush & JRummy).
I'm pretty sure Z4Root does not work on the GB versions of DX firmware. That's probably why nothing is working. You aren't actually getting root.
you are on the .605 version of GB (when you see references to .602, .605, etc ...)
To get root, start here:
http://forum.xda-developers.com/showthread.php?t=1258599
You may also want to download the Droid2 recovery rather than the DX. The D2 version is a little newer and I think avoids a slight bug on later kernels when Debug is on. The D2 version works just fine on the DX. It can be downloaded free from here:
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Once you are rooted and have recover properly working, you should be able to use the Rom Toolbox to download and install Liberty. Just make sure you read carefully about the 'version' requirements on any ROM.
Oh ok so I was rooting it wrong.
I easily rooted the phone using Pete's Motorola Root Tools. I realized that Rom Toolbox Pro accesses clockwork recovery when the phone is rebooted instead of the phone just restarting fully. But, I still want to start fresh and do everything from the start again. Please let me know if you have any suggestions in the way or order I am doing things. My phone is currently up rooted at 4.5.596 and rooted by Pete's Motorola Root Tools but I want to start over from the beginning so here is what I am going to do:
Note: Before I do anything I am going to format my SD card for a fresh start.
1. Use RSD_Lite 4.9 to Flash my phone back to 2.3.340 using a file called VRZ_MB810_2.3.34_1FF_01.sbf. I always do this part with no problem.
2. Do a hold power+home then search and do a system wipe/restore. Then Activate service, sign into gmail etc.
3. Now that the OS is loaded (the old version with the grey bars 2.3.340) I am going to root my phone using Petes Root Tools. (I hope I can root it with this tool when the firmware is this version.)
4. Put the 3 zip files I have on my SD card to upgrade to GB 588. Also put my GB 596 file on here.
5. I will download 1 app. D2BootStrapper. Bootstrap recovery, reboot into recovery. Install all 3 zip files from SD card. Now I boot up in GB 588.
6. Now I go right back into D2BootStrapper. Bootstrap recovery, reboot into recovery. Install GB 596. Now I have GB 596 rooted and loaded.
7. After this, shouldn't I be able to download Rom Manager Premium and Rom Toolbox Pro and test as many roms as I want? always reverting back to my original backup.
I noticed after installing liberty I was getting all kind of force close popups. And the phone wouldn't connect to service. But then I just held power + home then hit the up/down arrows and did a wipe/restore and it loaded liberty and everything works. Is this normally what has to be done when installing roms?
If there is anything wrong with my process please let me know. Whew I can't believe all that I learned in 1 day.
You've got a lot of steps there that really aren't necessary. When you install a ROM like Liberty, it replaces EVERYTHING in /system. Thus, about all that is left from a .596, .588, .602, etc install is the kernel. The Kernel doesn't change very often in Motorola builds. The last change was on .602. Thus, for your purposes there is no difference between .602 and .605 (FYI, .605 was just a keyboard fix over .602).
So, if you search around, you should find an SBF or AIO flash file to get you to .602.
Or you can simply take the OTA update from VZW after SBF'ing to .340
Once you've flashed your Rom, be sure to clear data/factory reset. You should then start with a clean system.
Alright, if you don't mind can you please let me know what steps I can avoid.
I didn't think it was possible to have a rooted .605 but I guess I was wrong.
So my goal should be to get to .605, then root it. Then install roms from there?
On your first post you said you were on .605. I'm assuming that is still the case.
If so, then root it with pete's tool (I think you've already done that).
Install D2bootstrap, then ROM Toolbox and install your rom from there.
I have to be honest, in that I've not used Liberty in a while, nor have I used Rom Toolbox. It shouldn't be a problem, just make sure that the version of Liberty you are using is for the GB kernel. Some of the older versions of Liberty (Which I did use, and like) were for the Froyo kernel (in that case, stay on .340 and do your upgrades).
Make sure you wipe data in recovery after installing the ROM. Lots of 'Boot Loops' are due to not wiping data after flashing a new rom.
Yeah
Yeah I read up on all of that. I actually might not end up going with Liberty. Going to try others like ICX. But before I do any of this I need to get to .605.
No I am not at .605 I believe that's where my phone was before I started all of this.
Right now I am flashing back to 2.3.34
Once I am back up and running there. Can you please recommend the easiest way to get to .605 and that will be my final question.
.605 should update automatic. If not you can disable the updater using titanium backup by freezing system updater.
1. Use petes tools install cwm as well
A. Droid x bootstrap get this
B. Titanium backup. Backup your apps
2. Make a backup using cwm and backup apps with tb
3. Put the rom zip files on the sd card.
4. Reboot to recovery. Reformat system data etc
DO NOT REFORMAT THE SD CARD.
5. Wipe cache davik etc.
6 flash rom. And reboot.
7 run tb for your apps
Should be a smooth and clean install. The roms are already rooted so no need to worry about that. Hope this helps
Sent from my MyTouch 4G Slide using xda premium
We aren't supposed to link to other forums, so expect this link to get removed.
http://rootzwiki.com/showthread.php?399-UPDATED-GUIDE-LINKS-DX-SBF-s
I would point you to a link here, but couldn't find a quick/easy link to what I wanted.
In this list is an SBF file for .602. Since you seem comfortable with doing SBF's, I would just SBF straight to .602 and root it from there.
Don't know much about ICX, but would encourage you to look at the CM7DXGB thread over at Rootzwiki as well.
ohh, well I just went to Settings > About Phone and its auto updating to .605
Am I not going to be able to root it after this update or should it be fine.
HunterT said:
ohh, well I just went to Settings > About Phone and its auto updating to .605
Am I not going to be able to root it after this update or should it be fine.
Click to expand...
Click to collapse
Pete's Root tool should root .605 just fine.
One last thing
As far as Clockwork recovery goes.
Should I always be in the latest version 5.0.2.0 (the blue version)
Or the old version 2.something (the green version)
Why is there 2 version and why would I ever want to flash back to the old version 2.something?
Zaphod-Beeblebrox said:
Pete's Root tool should root .605 just fine.
Click to expand...
Click to collapse
Pete's will work on .605 I did two the other day
Sent from my MyTouch 4G Slide using xda premium
HunterT said:
As far as Clockwork recovery goes.
Should I always be in the latest version 5.0.2.0 (the blue version)
Or the old version 2.something (the green version)
Why is there 2 version and why would I ever want to flash back to the old version 2.something?
Click to expand...
Click to collapse
Couple things most of the updates are to add support fix minor bugs etc.
I run the one from petes all the time I forget which version. I haven't had problems.
On my mt4g slide I had to flash a modified verson of clockwork due to my phone being newer and not as much support
With that said its not a difficult process to get a new recovery image. You would need terminal emulator and root explorer. Couple of great guides on here on how to do so. Also other methods as well.
All in all the ones that pete's give you should suffice. Unless your one of the extreame types of people who want the newest or like messing around.
Just remember backups can make the process and hassle of soft bricking your phone much easier to fix and takes a few mins to do.
Look around the forums lots of great information from the devs, experts, etc
Sent from my MyTouch 4G Slide using xda premium
HunterT said:
As far as Clockwork recovery goes.
Should I always be in the latest version 5.0.2.0 (the blue version)
Or the old version 2.something (the green version)
Why is there 2 version and why would I ever want to flash back to the old version 2.something?
Click to expand...
Click to collapse
The newer version changes the way backups are stored. The new format is smaller and quicker.
Among other issues/bug fixes as mentioned before, but the backup issue is important as the new version will not restore the old style backups.
Hi everyone. I had a few questions about flashing new roms on my kindle and was hoping to get some help
1. If I flash a new rom, like cm7, will i need to use titanium back up to save my apps and data. I remember doing this when i flashed a rom for my phone.
2. will flashing to cm7 prevent me from receiving OTA updates that amazon sends out. They just recently sent one a few days ago and the update unrooted the kindle. I wanted to see if I this is something I would have to worry about if i flash to cm7
3. once i do flash to cm7 and say another rom comes out, can i flash straight to the new rom or do i need to flash back to stock then perform the flash for the new rom.. again i remember having to do this when i was changing roms with my phone.
4. does the battery need to be fully charged before flashing
5. If i flash to cm7 then want to go back to back up (amazon stock software with root and gapps) will this make me loose my root access and twrp 2.0
Thanks
babbabooey97 said:
Hi everyone. I had a few questions about flashing new roms on my kindle and was hoping to get some help
1. If I flash a new rom, like cm7, will i need to use titanium back up to save my apps and data. I remember doing this when i flashed a rom for my phone.
2. will flashing to cm7 prevent me from receiving OTA updates that amazon sends out. They just recently sent one a few days ago and the update unrooted the kindle. I wanted to see if I this is something I would have to worry about if i flash to cm7
3. once i do flash to cm7 and say another rom comes out, can i flash straight to the new rom or do i need to flash back to stock then perform the flash for the new rom.. again i remember having to do this when i was changing roms with my phone.
4. does the battery need to be fully charged before flashing
5. If i flash to cm7 then want to go back to back up (amazon stock software with root and gapps) will this make me loose my root access and twrp 2.0
Thanks
Click to expand...
Click to collapse
1. If you are coming from another rom, then yes. But if you are updating your CM7, then you should probably backup your apps
2. I have had CM7 on my Kindle for like 2 weeks, and have not received an update. So I don't think so.
3. Like I said above in number 1. For example: If you are coming from Cm7 and want to try to flash ICS, then you would first backup your system, then wipe system, data, cache and Dalvik-cache, just to make sure. But if whistlestop releases a new version of Cm7 that fixes the MAC adress, then you would boot into recovery, A backup is optional but is recommended., then wipe cache and Dalvik-cache only, then flash the updated rom on top of it.
4. It says that it is recommended to have a full battery, but I have not yet flashed a rom with a full battery, and I have not occured problems.
5. I think if you get an OTA update after flashing back to stock, then you will probably loose root access again and TWRP. But don't worry, after you get TWRP back, you will still have all your backups.
AWESOME! Thanks for all your help.
one more for you. so i just rooted and installed twrp and did a system back up. then i want to flash cm7. now i am running cm7 and decide to try ics so i do another back up before i flash to ics, will the cm7 override the original back up that i did before flashing cm7 or will i now have 2 different back ups i can restore if i wanted too.
babbabooey97 said:
AWESOME! Thanks for all your help.
one more for you. so i just rooted and installed twrp and did a system back up. then i want to flash cm7. now i am running cm7 and decide to try ics so i do another back up before i flash to ics, will the cm7 override the original back up that i did before flashing cm7 or will i now have 2 different back ups i can restore if i wanted too.
Click to expand...
Click to collapse
There will be 2 different choices when you go to restore. But the problem is that when you make 2 backups the same day, its hard to tell which is which. So when I make a backup I mount USB with the option and rename the 12-27-11... file to something like CM7-12-27 or something of the sort.
Sent from my LG-VM670 using Tapatalk
Thank you sir
Hi guys,
I have a Bravo AT&T unlocked (Android 2.1 v1) and there are a lot of apps that simply don´t work (radio, market, etc).
I decided to install a custom ROM (Kobe 2.2.10) and following the instructions I have to wipe dalvik cache. I cannot find that option when I boot, there are only wipe data and wipe cache partition.
AS you may see, I´m new to Android environment so your suggestions would be much appreciated.
Another question: do I need to upgrade to gingerbread or this is made by simply installing the ROM?
dsafdie said:
Hi guys,
I have a Bravo AT&T unlocked (Android 2.1 v1) and there are a lot of apps that simply don´t work (radio, market, etc).
I decided to install a custom ROM (Kobe 2.2.10) and following the instructions I have to wipe dalvik cache. I cannot find that option when I boot, there are only wipe data and wipe cache partition.
AS you may see, I´m new to Android environment so your suggestions would be much appreciated.
Another question: do I need to upgrade to gingerbread or this is made by simply installing the ROM?
Click to expand...
Click to collapse
The wipe data/cache will work -- dalvik cache is stored on the /data partition; but you'll lose all installed apps as well. If you're rooted, use Titanium Backup or similar to back up any apps as needed. I posted my app backup method at the bottom, but its a bit complicated and requires using adb and modifying the updater-script of what ever rom you're going to flash -- well, noob complicated anyways.
You need to flash the 2.2 sbf first since ALL our roms are based on it and the Froyo kernel. 2.1 is Eclair and afaik, no roms are made for it.
Then I'd skip that 2.2.10 rom since it's out dated. For stability, the roms go as follows -- CM7 -> Pikachu MIUI\2.4.20 MIUI -> MS2 Ginger (no camera\tethering) -> CM9 -> BravoX -> Stock. That said, CM9 will soon be at the top of the pack in the next month or two... I'd start off with CM7 if I were you, just to get the hang of how everything works and then go from there. MS2 also has very good battery, but no camera or tethering -- which doesn't matter if you use US ATT since it does an entitlement check to see if you pay for tethering. (Pisses me off since I only tether my home WI-FI, never 3g. Why should that cost me $20 a month???)
From the what you typed, it sounds like you're trying to flash a rom from the stock bootmenu which will not work. You first have to install Defy 2nd-Init, then install the rom from that bootmenu.
There is no "real" gingerbread for the Bravo, only GB roms built for the Froyo kernel. While the Bravo is fully capable of running GB, ICS, and probably Jellybean as well (Android 4.1.0, not released yet), Motorola would rather us buy new phones then update our software -- the crux of all but maybe 3 or 4 Motorola phones due to us having locked bootloaders.
Link to tutorial on sbf flashing
Link to Defy 2nd-Init
Here's my app backup method
adb pull /data/app ~/Documents/data/app
Open updater-script of rom you're going to flash (/META-INF/com/android/google/updater-script)
add the following 3 lines right before the final line
Code:
package_extract_dir("data/app", "/data/app");
set_perm(1000, 1000, 0771, "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
add the pulled /data/app/ to the root directory of the zip so it looks like
data
META-INF
system
and flash the zip with all you're apps preinstalled and working -- you lose app data this way (settins, passwords, etc), but latent app data from one rom to the next can be bad news.
A trick is to do the above with a TB backup, then use TB to restore the app data for select apps that have a ton of settings to configure, but that can be dangerous if you go from say romA 1.0 to romB 1.0. RomA 1.0 to romA 1.1 is safer for restoring app data.
Not dangerous as in brick, more like the app will just FC on opening up. Its best to just ignore app data and just reconfigure everything.
I should add, if you don't require tethering or camera, then MS2 could be at the top of the list. Its an awesome rom with great battery life and stability.
thanks for the tips, I´ll try to implement them this weekend.
Since the phone is new and I don´t have any personal apps that I particularly use, do I need to make any backups? Do they come with CM7?
dsafdie said:
thanks for the tips, I´ll try to implement them this weekend.
Since the phone is new and I don´t have any personal apps that I particularly use, do I need to make any backups? Do they come with CM7?
Click to expand...
Click to collapse
No, CM7 pretty much has it covered, unless you use the ATT or Blur Apps. You may need to find a market replacement for those.
If you do use the ATT\Blur Apps, then you could install MS2Ginger, but the camera and data tethering doesn't work with it -- its still one of the most stable\battery efficient roms out there. If it wasn't for the fact that I tether my wifi daily (I am right now) and sometimes the Bossman needs pictures from the job, I'd probably run MS2 as my primary stable; but CM9 works well enough now -- except yesterday when my baseband quit working out of nowhere, all I did was install a theme and reboot....Ended up restoring my Pikachu Backup since I on the way to work and needed stable.
Why wait till the weekend -- its a 15 minute process, and I'm including flashing the sbf and rooting the device.
As far as mods and all that goes, I'd stay away from the Touch Recovery. Reasons -- it doesn't like big Aroma Installer roms (wouldn't even start my 450mb Wiui I was working on), sometimes it just doesn't work, and data wipe also wipes sd-ext (where I store data I don't want being fragmented by vfat). It'll be awesome once its a bit more stable; just not noob friendly yet.
I suspect the Aroma not working with Touch is because /tmp is mounted to ram, and it just can't extract a 450mb rom in to ram and have the system fully working as well.
What sucks, is with little modification, the system will run the sdcard as ext3; except that mediaserver actually checks to see if the card is vfat and will fc when it isn't. And you cant make a 10mb vfat partition and symlink it to sd-ext either since vfat doesn't support symlinking. None of that really matters to you, but the Touch part reminded me of my most hated Android requirement -- vfat as the only filesystem of sdcard primary partition.
HELP
Installing SBF I`m stuck at step 10: the red M logo appears but the phone doesn`t respond to anything. Trying to wipe data in stock recovery but no buttons /button combination seem to work.
dsafdie said:
Installing SBF I`m stuck at step 10: the red M logo appears but the phone doesn`t respond to anything. Trying to wipe data in stock recovery but no buttons /button combination seem to work.
Click to expand...
Click to collapse
Whit the phone off press volume down button and power button, when you are in recovery mode where you see the android logo with exclamation, press both volume buttons at the same time.
thanx, I`ve just done that in a desperate move and it worked!
Alright... I have been running CM7 on my Defy (MB525 red lens) for years without any issues, but recently I decided it was about time to wipe the thing and start from scratch, and I figured, if I was going to do that, why not install the latest (CM11) and see how it works for a bit before (if necessary) downgrading to a more stable version.
So, after reading up I figured what I should do is:
1. Flash SBF with RSD Lite.
2. Root phone (easy with Framaroot 1.7)
3. Install custom recovery/bootloader (easy with SndInitDefy 2.0)
4. Flash to CM10.0 latest (android 4.1)
5. Reboot, check if it runs, then reboot into recovery
6. Flash to CM10.1 latest (android 4.2)
7. Reboot, check if it runs, then reboot into recovery
8. Flash to CM10.2 latest (android 4.3)
9. Reboot, check if it runs, then reboot into recovery, follow Quarks instructions for 4.4/CM11
I thought that would be easy enough, but I have attempted this about 20 times by now and am running into the same problem time and time again... after flashing to CM10.0, 10.1, or 10.2 and booting up, my phone turns out to have lost access to its internal storage. As a consequence, bootloader/cwm/twrp becomes inaccessible, installing anything becomes impossible, and any settings changes you make are lost again whenever you reboot the phone. I would expect it to be a corrupt ROM I am installing, except for the fact that this seems to be happening randomly on one of the 3 flashes, not consistently on the same flash. Whenever it happens though, the only thing I seem to be able to do is flash the SBF again and start from scratch... and where I do occasionally get as far as having CM10.1 running and functioning, I have not yet had a single run through where I ended up with a functioning version of CM10.2.
Am I missing some important step I should be taking inbetween my steps somewhere? I read some stuff about custom kernels, but if I understood things right, they are included in the CM zip installs, so I shouldn't need to do that manually... or am I mistaken about that? Or am I not missing a step in my process, but is there an easy fix for this issue that I have overlooked? I imagine that this is either a problem that everyone runs into but is very easy to fix (and therefore not allover these forums) or it is a problem I am bringing upon myself by doing something wrong in my upgrading steps.
Help would very much be appreciated.
P.S.: I have no difficulties using adb or anything like that, I originally rooted my phone using ADB too, so any solutions involving ADB or anything like that shouldn't be an issue. I am fairly confident in my use of computers and programming where it concerns computers, but I am somewhat new to the whole android modding scene, hence my need for some assistance.
Try a full wiper (either defy full wiper or aroma wiper or even TJKVs safe wipe) to wipe to ext4.
Sent from my Nexus 7 using Tapatalk
Hi
I have installed CM11 (4.4.2) on Defy and it is working fine except the battery.
This entailed installing TWRP
Earlier I had MIUI Pikachu edition.
Questions
1. How do I install or restore my MIUI backup again.
2. Also I would like to downgrade to CM 7/9 which is more stable
Any links or step by step suggestions would be appreciated
Thanks
Ninad
ninadb said:
Hi
I have installed CM11 (4.4.2) on Defy and it is working fine except the battery.
This entailed installing TWRP
Earlier I had MIUI Pikachu edition.
Questions
1. How do I install or restore my MIUI backup again.
2. Also I would like to downgrade to CM 7/9 which is more stable
Any links or step by step suggestions would be appreciated
Thanks
Ninad
Click to expand...
Click to collapse
please do not post questions in the development section
post moved to the Q&A
No reply for this? I Also want to chahge from CM11 to MIUI on Defy, but just flashing the zip in the TWRP does noting and the phone always start the CM11.
Thanks a lot!
evilinheaven said:
No reply for this? I Also want to chahge from CM11 to MIUI on Defy, but just flashing the zip in the TWRP does noting and the phone always start the CM11.
Thanks a lot!
Click to expand...
Click to collapse
Probably you need to flash sbf to get an old bootstrap.
Sent from my HTC One using Tapatalk
I wan to downgrade as well, preferrably w/o sbf. But I flashed so often by now, searching for the fastest way w/o: 1-sbf, 2-reroot, 3-custom recovery and 4-flashing cm7 would take more time, than the flashing process itself.
So that's what I'm gonna do. Hope it gets snappier then. CM11 with just about 9-10 apps (facebook, messenger, whatsapp, gmail, gcal, aero control, battery stats, es file explorer) is already torture for my defy.
erdnuesse said:
I wan to downgrade as well, preferrably w/o sbf. But I flashed so often by now, searching for the fastest way w/o: 1-sbf, 2-reroot, 3-custom recovery and 4-flashing cm7 would take more time, than the flashing process itself.
So that's what I'm gonna do. Hope it gets snappier then. CM11 with just about 9-10 apps (facebook, messenger, whatsapp, gmail, gcal, aero control, battery stats, es file explorer) is already torture for my defy.
Click to expand...
Click to collapse
I have an idea, and its a possibility for you. I have a Atrix 4G which also is on CM11, and like you guys on the Defy, has a bigpart mod. For us to downgrade, its flash an old recovery, boot to recovery, factory reset, wipe all partitions (system, data, cache, boot (that should be the ones you have too)), flash desired ROM/restore backup. Not sure if that will work for you, but its worth a shot. If it doesn't work, i'd try sbf'ing (someone posted an sbf lately if i remember correctly
Sent from my ATRIX HD using XDA Free mobile app
Unfortunately I don't know what sbf to take - it might be irrelevant, since i accidentally flashed to bl7 long ago and since I wanted to reroot again, twrp and cm7 it might not matter which one to flash. I am trying to speed things up a bit, and struggle with twrp atm, because safewipe.zip might no longer be safe (unable to enter twrp) or the version was not meant for my configuration.
Now i trimmed all part's and try amplifying services, but it's been a while since i tuned my defy.
OT: I switched to Moto G and E2 (but lost both ones - or they've been stolen) and now I want to reactivate my old pal before switching to anything new again. It's getting expensive...
So don't wait, maybe I'll get CM11 to work good enough again, but if not, I'll try to provide a checklist.
palmbeach05 said:
I have an idea, and its a possibility for you. I have a Atrix 4G which also is on CM11, and like you guys on the Defy, has a bigpart mod. For us to downgrade, its flash an old recovery, boot to recovery, factory reset, wipe all partitions (system, data, cache, boot (that should be the ones you have too)), flash desired ROM/restore backup. Not sure if that will work for you, but its worth a shot. If it doesn't work, i'd try sbf'ing (someone posted an sbf lately if i remember correctly
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse