Database Users

Tried to install Liberty on my Droid X, messed up, stuck in a hole, plz dig me out

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.

[HOLY CRAP][SPRINT P100] Stock to CM10 JellyBean - Complete Walkthrough

*********************************************
CM10 is now available.
Requirements: Root
From rooted stock or a custom rom, just download and install updated Rom Manager from the Play Store and download CM10 Nightly and GAPPS. Reboot into ClockWorkMod, factory wipe, disable signature check, flash CM10 twice. The first time partitions our tabs and reboots. Flashing a second time is for good measure. Then flash GAPPS. Done.
Note: I am not sure if Rom Manager can flash ClockworkMod directly. I personally updated from ICS > CM10 by downloading CM10 and GAPPS through GooManager and flashing manually in ClockWorkMod.
Its been reported that you can go directly from rooted stock to CM10. I've actually completed everything below to get to ICS first (Stock > ICS > CM10 JB).
CM10 is a much better experience. The tab works much better, doesn't freak out, lasts longer, plays better.
*********************************************
Wow. Lots of different, confusing, and scattered information about how to go from stock Gingerbread to the latest CM9 build. It is all very confusing and honestly most of the useful information isn't even on this site. So I figured I would help myself (and others) in creating a very detailed walkthrough of the process required to successfully get from GB to CM9 Build 7.
**This specifically outlines the methods to take a COMPLETELY STOCK Sprint Galaxy Tab 7" SPH-P100, unrooted, to a ICE CREAM SANDWICH rom. I "think" it might also work for the Verizon CDMA and a few others. I think the ROM itself is a general overall generic build for all 7" Gtabs. So heads up that if you have a different version, you might want to use this as a guide rather then a step-by-step.**
BACKUP EVERYTHING YOU MAY NEED BECAUSE OBVIOUSLY THIS PROCESS WILL FORMAT YOUR GALAXY TAB
GET CONNECTED!
We need to download Heimdall's App and his Drivers (Main URL). This is the first confusing steps as everyone suggests using an older version, but the included drivers don't work on newer Windows OS's. So you have to mix and match a few different versions to get it working. I've already compiled an archive with everything you need: Heimhall Mixture /w zImage & ClockWorkMod 5.0.2.7
1. Extract everything to a simple folder [ex. C:\GTABICS ]
2. Turn off Gtab. Hold VolDown+Power until you get to a downloading screen
3. C:\GTABICS\Drivers\zadiag.exe to load drivers [try running as Administrator]
4. C:\GTABICS\heimdall-frontend.exe to start the process
5. Kind of confusing. Focus on the "BROWSE" buttons. Look for "Kernel(zImage)" on the left and "Recovery" on the right. Hit browse for each one and select the appropriate file from C:\GTABICS. Obviously "Kernel(zImage)" = "zImage" and "Recovery" = "recovery.bin".
6. Make sure Kernel(zImage) and Recovery both have files selected and a checked box. While GTAB is at the black Downloading screen: Hit "START".
7. The process is pretty fast. Don't rush. At this point your tab will probably just bootloop anyway.
LET'S GET THIS SHOW ON THE ROAD
Now you have ClockWorkMod installed and a proper kernel, most flashers will feel really at ease right now. But there are a few little quirks that will cause this to go bad. You have to install 2 versions of ICS to get to the latest; One using the existing partition table, and a second that will update to a newer format. You obviously have to install GAPPS like always with a CM rom, but not so fast, you have to manually "MOUNT /SYSTEM" in CWM before it will even take. And there is the fact that you have to manually open and edit the CM9 Build7 update and remove code....[holy crap].
But it is pretty easy once you go through it once.
REQUIRED FILES
JT1136 CM9 V5
JT1136 CM9 V7 UPDATE
GAPPS
Prepare CM9 v7 Update
1. On your PC, open "update-cm-9.0.0-RC0-galaxytab7c-KANG-BUILD7.zip" and browse to META-INF\com\google\android
2. Copy "updater-script" to your desktop and open with Notepad and remove the first 3 lines or just Download it.
3. Drag and drop the update-script back into the META-INF\com\google\android folder, overwriting the existing one.
If all goes well, you are now done with the PC.
COPY FILES AND FLASH
1. Copy Build5, the new Build7, and GAPPS to your microSD card.
2. Boot into ClockWorkMod: Power off. Hold VOLUP + POWER
3. Factory Reset / clear cache / wipe Dalvik Cache / Breathe
4. Flash zip from SDCard: locate Build5 and Flash
5. Factory Reset / clear cache / wipe Dalvik Cache / Breathe
5.5 [OPTIONAL] You should be able to boot into ICS at this point if you want to make sure build5 flashed properly before upgrading to build7
6. Flash zip from SDCard: locate Build7 and Flash
At this step, my GTab rebooted in the middle of the process the first time. It freaked me out but I assume (now) that since it changed the partition tables, it needed to reset. So I did it a second time just to be safe:
7. Flash zip from SDCard: locate Build7 and Flash
8. Factory Reset / clear cache / wipe Dalvik Cache / Breathe
Congrats. You should have a working bootable CM9 build. But lets flash GAPPS so we have our Google services. This is tricky.
9. Mounts and Storage > Mount /System
10. Flash zip from SDCard: locate GAPPS and Flash.
11. Finally [!] reset device and prepare for boot.
Now you are on the latest CM9 build [7] and have the latest GAPPS installed. Hopefully you are booting now and see the famous ICS Boot Animation. Have fun. In the future you should be able to simply download new roms as they are available and flash normally like you would any other device.
RECAP:
Drivers and Flash Tool
Pre-Edited updater-script
UPDATES
Convert to Sprint
The above procedure will set your Tab as a Verizon version. If you plan on using the Sprint cellular service or just want everything to match, then flash this via ClockWorkMod.
****************************************​
I didn't do any development work. All credit goes to Heimdall for his fantastic Recovery Flasher and jt1136 for his great stills porting this awesome rom over to our Galaxy Tabs. All I did was bump and grind my way through to see a successful working flash. I figured if I didn't post a walkthrough here, I would hate myself in 6 months when I boink something up and have to do this all over again. I would recommend you keeping all of the files safe somewhere to prevent this headache again.
DONATE TO JT1134
DONATE TO HEIMDALL
MAIN HEIMDALL URL
MAIN ROM URL

player911
i have been thinking about moving up to ICS with my sprint sph-p100
just not sure if i should jump now or wait till more things are working ?
do the things working out number those not , is it ready to be a daily driver yet?

Camera fully works but is flaky sometimes. Video out isn't working yet but he's working on it.
Other then that, its golden. Very fast and works well. Really worth it. Feels much better... like an actual tablet vs a large phone.
Iffy Camera and video out aren't worth holding back. One of the benefits is now Wiimotes and PS3 controllers will pair up using their respective apps now.
Sent from my Galaxy Nexus using xda premium

Thanks for the input ill be movin up to ICS soon
Sent from my SPH-P100 using Tapatalk

flashed sprint Tab
Hello all,
Thanks for the files and instructions! Here is my situation/question:
I bought my Gtab off of ebay flashed to work on Boostmobile's 3G network. It works great, and had no problem with the official OTA upgrade to Gingerbread.
Now I'm dying to upgrade to ICS but am worried that this would mess with my 3G connection. I can't provide any details of what went into the flashing (its not a process I understand), but I'm hoping that someone out there will.
So, if I follow the instructions in this thread will I still be able to use my Tab with the boost 3G it connects to now?
Many, many thanks for any help with this!!

Great Thanks! The first complete step-to-step instruction for installing ICS on Sprint p100.
One note- if you have Error 12 - delete all SAMSUNG USB drivers on PC, rebut and instal drivers from first archive.
At least!!! Thanks a lot!

I don't use the cellular network (sprint) but it does come up and show signal. I don't use it as a phone or anything like some people (supposedly you can install phone.apk and make calls over a voice plan).
I just use the tab as a tab. I just wanted to confirm that it appears to see the cellular network fine.
Sent from my Galaxy Nexus using xda premium

just made the plunge had some issues with the drivers for heimdall and after that i got a fail when flashing hit start again and it flashed
followed all the steps and im on cloud 9 now wow
gonna take a few to get used to ICS

Well I found a sprint patch and flashed it all is well now
Sent from my SPH-P100 using Tapatalk 2

LivnDream said:
Well I found a sprint patch and flashed it all is well now
Sent from my SPH-P100 using Tapatalk 2
Click to expand...
Click to collapse
Sprint patch for what? Mind linking? No offense but posts like these without links or more information is what creates confusion.
I haven't used a patch at all and everything seems to be working. I also never heard of a patch to fix anything.
Sent from my Galaxy Nexus using xda premium

scabrerautexas said:
Hello all,
Thanks for the files and instructions! Here is my situation/question:
I bought my Gtab off of ebay flashed to work on Boostmobile's 3G network. It works great, and had no problem with the official OTA upgrade to Gingerbread.
Now I'm dying to upgrade to ICS but am worried that this would mess with my 3G connection. I can't provide any details of what went into the flashing (its not a process I understand), but I'm hoping that someone out there will.
So, if I follow the instructions in this thread will I still be able to use my Tab with the boost 3G it connects to now?
Many, many thanks for any help with this!!
Click to expand...
Click to collapse
you have nothing to worry about, 3g will still work.. i have flashed many roms on mine including ics ones and 3g still worked.
well i shouldn't say many roms...i've flashed it many times to ics and back to gb.

player911 said:
Sprint patch for what? Mind linking? No offense but posts like these without links or more information is what creates confusion.
I haven't used a patch at all and everything seems to be working. I also never heard of a patch to fix anything.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
its a sprint patch on the rootzwiki fourm for this rom ill get you a link
i got a post there with a link to the patch someone there posted
it changes the wireless from showing veirson to sprint and the tab to sph-p100
wasnt tryin to cause any confusion
http://rootzwiki.com/topic/11697-rom-cdma-aosp-ics-cm9-build7-0304/page__st__1040#entry613901

Do I need to be on stock gb or could I do this while rooted? Sorry I'm noob with hiemdall.
Sent from my SPH-P100 using xda premium

As soon as I flash version 5 I get an error that installation was aborted, what did I do wrong?

dog44 said:
As soon as I flash version 5 I get an error that installation was aborted, what did I do wrong?
Click to expand...
Click to collapse
Try re-downloading the version 5 zip again. Make sure you don't edit anything within the zip before you put it on your SD card. This happened to me when I edited the version 7 zip as instructed above.

Ok. Got it working. What is the newest ver.? I'm on 4.03
Sent from my SPH-D700 using XDA

I think 4.0.3 is the latest ported over. I have a Galaxy Nexus and 4.0.4 was just released... so I would expect delays in porting that over to unofficial devices.
The patch, I've found, is just cosmetic. Once you upgrade to ICS using this method, the build.prop has everything setup as a Verizon Device (name, settings, etc). They can all be manually changed but there is a patch that you can flash via ClockWorkMod that does everything for you.
The link was posted a few posts up.

What is DTI? I may just leave it as verizon since I get more signal. LOL

Hey what's up guys I just threw this on my sprint tab... I had a few quirks with it early... when I first flashed the clockwork mod on it, the screen was discombobulated... the capacitive touch orientation was in landscape mode while the actual screen was in portrait.
So when I had to put the files back on the tab after modifying build 7 zip. I had to figure how to unlock the screen and then and also to choose "connect USB to storage"
Then I got a little nervous while doing the wipe because it took long. I thought it froze..
Just a heads up of what could happen to other guys .
Also now after full install, I find that my ram is usually pretty low and my CPU usage is almost always @ 100 percent .
Taking away from the fluidity... any suggestions ?
I restored my email from titanium back up and also my browser bookmarks, now they don't open up or close immediately. This happens with a lot with system data restored things....
Sent from my SPH-P100 using Tapatalk

Whenever my tab starts it says encryption unsucessful, how can I get past this screen?

I went through the thread thoroughly, but didnt find a solution

So, I posted before about wanting to flash a custom rom to my newly bought Milestone2. Sadly, no replies.
My problem now is that I have rooted, did the droid2bootstrap and then flashed Bootmenu via CWM, downloaded the MS2GINGER 4.0 with the kernel update and baseband switcher and the blur apps.
I boot into recovery fine, wipe/factory reset works. Clears the cache. But when I try to restore the system of the Ms2ginger, it says that the md5's dont match. Can anyone tell me what to do to get this rom working on my Milestone2?

Darin_Ram said:
So, I posted before about wanting to flash a custom rom to my newly bought Milestone2. Sadly, no replies.
My problem now is that I have rooted, did the droid2bootstrap and then flashed Bootmenu via CWM, downloaded the MS2GINGER 4.0 with the kernel update and baseband switcher and the blur apps.
I boot into recovery fine, wipe/factory reset works. Clears the cache. But when I try to restore the system of the Ms2ginger, it says that the md5's dont match. Can anyone tell me what to do to get this rom working on my Milestone2?
Click to expand...
Click to collapse
You can try this fix: http://forum.xda-developers.com/showthread.php?t=714114
Works in linux, if you have windows, you're gonna have to find md5sum somewhere else.
Hope it helps :good:

Thank you!!!!!!!
Lean946 said:
You can try this fix: http://forum.xda-developers.com/showthread.php?t=714114
Works in linux, if you have windows, you're gonna have to find md5sum somewhere else.
Hope it helps :good:
Click to expand...
Click to collapse
Thanks man! I appreciate it. I have one more question though, for the ms2ginger, the kernel update cant be downgraded to froyo afterwards?
I've been reading but I havent really tried anything. I just (literally, 5 minutes ago) flashed the CM7 on the phone.

Darin_Ram said:
Thanks man! I appreciate it. I have one more question though, for the ms2ginger, the kernel update cant be downgraded to froyo afterwards?
I've been reading but I havent really tried anything. I just (literally, 5 minutes ago) flashed the CM7 on the phone.
Click to expand...
Click to collapse
Yes, I think you can, by flashing your original rom's sbf.
Check here: http://and-developers.com/sbf:milestone2 and if the links are down, download the sbf from here: http://sbf.droid-developers.org/umts_milestone2/list.php (check the build numbers and the carriers)
Regards

I'll look into it.
Hmm... I'll have to look into that. I'm not sure about it, I just got the phone 2 days ago. Lmfao

Can you put a guide up here for me to follow? Cause, I really like the ms2ginger rom. I might even flash it today, assuming I get the files

Darin_Ram said:
Can you put a guide up here for me to follow? Cause, I really like the ms2ginger rom. I might even flash it today, assuming I get the files
Click to expand...
Click to collapse
I never really tried this rom ever, but i'll try to explain the flashing steps more clearly.
It's well explained on the rom's thread though: http://forum.xda-developers.com/showthread.php?t=1169038
OK, you need these files:
The rom itself: https://docs.google.com/folder/d/0B...p1T0U/edit?docId=0B3OovGFEtCdnajgyRHV5dXg3SG8
The motoblur apps (if you want them): https://docs.google.com/folder/d/0B...p1T0U/edit?docId=0B3OovGFEtCdnNHA0dERlSFVxLUU
Patch for milestone 2: it's at the end of the roms thread
Gingerbread kernel (in case you are coming from stock froyo, cm7, or miui): http://forum.xda-developers.com/showpost.php?p=26889742&postcount=843
RSD Lite, at least version 5.0 (google it, should come right up) and the motorola drivers (if you don't have them): http://rootzwiki.com/topic/3216-roo...click-added-for-windows-linux-osx/#entry74495 If you rooted your phone with superoneclick or similar, you should have them already.
Steps:
0) Unzip the rom's folder from the zip to /sdcard/clockworkmod/backup and put the other 2 zips (motoblur and the ms2 patch) on the root of the sdcard.
1) Get into custom recovery (vol. down on the blue led)
2) Wipe data/factory reset, Wipe cache.
3) Go to nandroid -> restore and select MS2Ginger.
4) Go to install zip from sd card -> and select the MS2 patch. Repeat with motoblur.
5) Reboot, it will get stuck on a black screen. Remove the battery, wait 10 seconds and put it back. Hold the vol down, camera (all the way down) and the power button at the same time for 10 secs, let them go, you should see a black screen with "bootloader" at the top.
6) Plug in your phone to your pc, fire up RSD Lite (at least version 5.0) and flash the GB kernel's sbf. The phone will reboot.
7) That should do it
Good luck :good:

Still nothing
I still get the m5dsums mismatch. I'll have to do a little more looking for that file Too bad, I wanted something stable like that with working 720p

I'm reading here that I need to flash a fixed sbf file. I assume I need to do this with rsd lite the same way I'd have to if I bricked my defy?

[Q] Defy Bricked. Really bricked.

- So I was updating to Quarx's 5th Nov build (2ndboot) and in the middle the flash my phone turned off and decided not to start up. (The battery WAS NOT drained)
- I started with this guide in order to get it back to life:
http://forum.xda-developers.com/showthread.php?t=1807899​(I used the exact same files, even the sbf. I live in India and I couldn't find India's sbf in this list: http://sbf.droid-developers.org/umts_jordan/list.php)
- Everything went as excepted and I was back on 2.2.2, so I tried to flash Quarx's build again. (I installed gapps, and cleared everything twice, thrice). However, the phone stuck on a bootloop:
red Motorola logo -> blue led -> greend led -> blank screen -> repeat.​I cleared the cache's, factory reset, etc etc. No use.
- So i followed the original method again to get back to 2.2.2 and then flashed ICS from Cyano's website. It worked! So I tried again to flash a CM10 release, but this time a PRE-2ndboot build - 24th Sep.
It didn't work either. So JellyBean is the evident problem, but it doesn't make any sense, right?
- I started agin and tried to flash a different sbf, I got to this thread:http://forum.xda-developers.com/showthread.php?t=1093352 and tried the sbf provided (they claim it to be the one for SEA, including India). However, even after doing a factory reset from the stock recovery and flashing this sbf, I got a brick. The phone won't start whatsoever. No bootloader, no recovery - zilch. Dead.
- I again went back to my original method and got back to ICS...Flashed JB -> Same bootloop as before.
- Somethings I have noticed:
1. On flashing, the internal memory shrinks to only 128MB. I tried a factory reset from within the phone, from custom recovery and from the stock recovery. The memory was still 128MB with about 40MB free.
2. When I return to stock, the phone is somehow pre-rooted. On running superOneClick it shows that it;s already rooted but I continue nonetheless.
3. I think MAYBE the low internal storage might be at fault since JB Gappa require a lot of space.. I have tried it with minimal gapps too.
4. I have flashed every sbf available for Asian countries...but the only one that works is the one from the first link provided.
5. The only thing I can do right now is get to 2.2.2 or ICS...So if someone can help me out, that's my current status.
PS - I have been at it for 3 straight days, so yea, I have tried just about everything and read every thread regarding this. I even had to jump start by battery once as it ran out in the middle of a sbf flash.

There s a chance you didn't installed JB the right way. Also you ca install it without Gaaps. Does 2nd boot got enabled in Bootmenu? Did you flashed the kernel accordingly?

if you have bl4 try one of my fixed sbf with 2ndboot
ex. 28.11JB.Quarx+jellyX.kernel
than make a data and cache format fom bootmenu
bootmenu/ CPU settings/ system tools/ format data and cache to ext3
reboot
hve the link in my signature

I think you need bl. 4 from an 2.3.4 sbf for defy
In my country there was as an official update to GB
Users posted prblems with bootloader 3 and 7 @ quarx cm10 2ndboot roms
MB525 red lense

Hi,
You can take one more try (if you wanna ) to flash 12.09 JB build - it shall work
If so then flash Nordic retail 2.2.2 or WE retail (U3_3.4.2-177 or 179 from here)and try again 2ndboot builds (for some sbfs the last pre 2ndboot, 24/09 was the first not working)
Flash then 5/12 and jb gapps, wipe dalvik cache and cache after flashing.
Concerning 128 MB free memory - I suppose you are talking about data partition, not a system. Of course it is too small - the same as prerooted phone - try another sbf

Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.

vinu.shukl said:
Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.
Click to expand...
Click to collapse
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions

corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Click to expand...
Click to collapse
These are the sbf's I found pertaining tp your specifications:
http://i.imgur.com/muQdT.jpg
EDIT: But they are all in the DEFY-PLUS repository...can I flash them?
So I can use anyone of them?
Also, I don't know much about BL versions...So should I just download one of the above sbf's and flash it using RSD? Do I need a nandroid backup to go with it too?
The procedure I would follow would be:
1. Factory reset, clear cache's
2. Go into bootloader menu
3. Flash above sbf using RSD
4. Reboot ??
Should that suffice?

First: if you are red lense it is ok to flash BL6
If you are green lense, to have your camera working, you will need 2ndboot builds (CM9, 10 or 7)
You will probably need red lens battery fix to show correct percentage, no matter you have green or red lense then.
You can flash it even later, after flashing CM10 and gapps and checking how it works
I would choose Nordic retail
Sometimes you can have problems with rooting with SuperOneClick (version 2.3) - force close Motorola Portal before rooting and it shall work ok then
And nandroid backup is not very useful when changing BL version, at least you will not be able to restore all

I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)

vinu.shukl said:
I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)
Click to expand...
Click to collapse
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see

corrinti said:
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see
Click to expand...
Click to collapse
Okay!
Gonna flash it tonight...Finger's crossed. =D

UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?

vinu.shukl said:
UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?
Click to expand...
Click to collapse
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting

corrinti said:
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting
Click to expand...
Click to collapse
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.

vinu.shukl said:
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.
Click to expand...
Click to collapse
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life

corrinti said:
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life
Click to expand...
Click to collapse
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.

vinu.shukl said:
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.
Click to expand...
Click to collapse
The ramdisk zip is to be installed in a standard way, like any other zip, probably doesn't require wiping caches, but probably
I usually use zRam (18%) - I didn't notice any bigger battery drain.
KSM off
WiFi - change to never when screen is off - you can have wifi on all the time without special battery drain
And choose proper baseband for you region
And CPU settings are ok as above

Defy on BL6
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas
---------- Post added at 06:03 PM ---------- Previous post was at 05:48 PM ----------
corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions
Click to expand...
Click to collapse
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas

@Vycas
The problems might be several, unfortunately even hd problem, but try this:
- try different USB cable, different computer, different USB socket - the problem can arise when signal transmission is poor. Sometimes reinstalling of motorola drivers also helps
- if above does not help try Linux computer instead of Windows one
Regarding sbf - well, as you received error after each sbf flashing there could be a hope that you still may have BL4 (but also you may have BL6) - start your above mentioned trials with BL4 sbf, which will give you camera also with CM7

[Q] Questions regarding Engle_Mars' MM2 CM10.1 port installation

Hello everyone, this is my first post on XDA and it is about Engle_Mars' CM10.1 port for MM2 (http://forum.xda-developers.com/showthread.php?t=2128318). I have a rooted MM2 (A953) running Android 2.2 Froyo, kernel version 2.6.32.9 and I wanted to try JB on my device, I installed Droid2Bootstrap (CWMRecovery is working just fine) and got his ROM on the SD card. My questions are:
A) Even though the ROM is based on the 2.6.32.9 Kernel, will it still run on my device? I am from Argentina and I purchased my phone at Personal S.A so it's running their custom Froyo Rom (System Version: Version.3.13.0.A953.Personal.en.AR)!
B) My phone's USB port is broken and the PC won't recognize it (Yes, I have tried a bunch of USB cables and other pcs as well), having this said, if I try the installation and end up in a boot loop will I be able to recover my device without RSDLite or a PC at all?
C) I have backed up my current ROM with CWMRecovery, will I be able to restore this backup if I want to downgrade or if the installation goes wrong?
Any help is very much appreciated, I am a complete noob as far as Android is concerned so sorry if I made any stupid questions, but I couldn't find any help on Google or other Forums. Thanks in advance!

matii2639 said:
Hello everyone, this is my first post on XDA and it is about Engle_Mars' CM10.1 port for MM2 (http://forum.xda-developers.com/showthread.php?t=2128318). I have a rooted MM2 (A953) running Android 2.2 Froyo, kernel version 2.6.32.9 and I wanted to try JB on my device, I installed Droid2Bootstrap (CWMRecovery is working just fine) and got his ROM on the SD card. My questions are:
A) Even though the ROM is based on the 2.6.32.9 Kernel, will it still run on my device? I am from Argentina and I purchased my phone at Personal S.A so it's running their custom Froyo Rom (System Version: Version.3.13.0.A953.Personal.en.AR)!
B) My phone's USB port is broken and the PC won't recognize it (Yes, I have tried a bunch of USB cables and other pcs as well), having this said, if I try the installation and end up in a boot loop will I be able to recover my device without RSDLite or a PC at all?
C) I have backed up my current ROM with CWMRecovery, will I be able to restore this backup if I want to downgrade or if the installation goes wrong?
Any help is very much appreciated, I am a complete noob as far as Android is concerned so sorry if I made any stupid questions, but I couldn't find any help on Google or other Forums. Thanks in advance!
Click to expand...
Click to collapse
A) Yep, new ROMs have custom kernels running with 2ndboot, that means that the running froyo kernel get replaced with a custom jb kernel on the fly. I'd recommend you flash the bootmenu v1.1 (from here http://forum.xda-developers.com/attachment.php?attachmentid=1183672&d=1341699135 , it's a newer (v5 versus v2), permanent recovery, you flash it using the "volatile" recovery in the bootstraper)
B) Nope, but remember to wipe data/factory reset on recovery so you don't get stuck. If you can't get to the custom recovery, stock recovery can be used to wipe.
C) Yes, but it's recommended yo do another backup with the newer recovery on the bootmenu, this is because CWM 5 has a newer backup format.
Remember most of the stuff has been already discussed here on xda. Some of the stuff for the defy applies to the MS2 as well (they're almost the same hardware-wise).
Good luck, and welcome to the milestone 2's rom scene

Lean946 said:
A) Yep, new ROMs have custom kernels running with 2ndboot, that means that the running froyo kernel get replaced with a custom jb kernel on the fly. I'd recommend you flash the bootmenu v1.1 (from here http://forum.xda-developers.com/attachment.php?attachmentid=1183672&d=1341699135 , it's a newer (v5 versus v2), permanent recovery, you flash it using the "volatile" recovery in the bootstraper)
B) Nope, but remember to wipe data/factory reset on recovery so you don't get stuck. If you can't get to the custom recovery, stock recovery can be used to wipe.
C) Yes, but it's recommended yo do another backup with the newer recovery on the bootmenu, this is because CWM 5 has a newer backup format.
Remember most of the stuff has been already discussed here on xda. Some of the stuff for the defy applies to the MS2 as well (they're almost the same hardware-wise).
Good luck, and welcome to the milestone 2's rom scene
Click to expand...
Click to collapse
Thanks a lot man! Glad to know people from Argentina actually care about technology! Gracias denuevo che

Launched a new version of the ROM today, I installed it in my M2 and it was much better without the Pdroid.

How i can root it?

My milestone entered in bootloop a few days afters the roms was installed, is this normal?

tioogu said:
My milestone entered in bootloop a few days afters the roms was installed, is this normal?
Click to expand...
Click to collapse
I really don't think it's normal, but if you haven't fixed it yet maybe you can do a restore wiping the cache and the partition (something like that). Like I said, I'm new to Android, not much I can help you with, sorry.

tioogu said:
My milestone entered in bootloop a few days afters the roms was installed, is this normal?
Click to expand...
Click to collapse
wipe data! bootloop stop...