[RECOVERY] j_r0dd-mb501-v2.0 (2.7.11)

[RealPariah]

Hello, I'm sorry I'm new to all of this so please bear with me...
I rooted my Cliq XT about 4 months ago using this guide [ROOT] Cliq XT. I've had a lot of issues trying to root it but I finally did it.

I'm lost at the beginning of step 4 since I don't even know where to run the commands from...

If I run the command on on ConnectBot (using local) it reads: $ adb shell I get an error: "adb: permission denied".

If I run the same command on the command prompt in the computer, using USB debugging and when I connect I've tried Charge Only and USB drive and get error: device not found If I use the command adb devices it just shows List of devices attached and then a blank space... Please Help!!

adb is a program you use on your computer search google for android sdk and when downloaded run that and download the USB drivers portion then make sure you go to motorola's site and grab their USB drivers for your phone and whn connected you should see an extra device install called the motorola composite device [adb] once this extra install happens that gives you the conduit between your machine and the phonme and if you have not done this your phone most likely is not FULLY rooted [you have to run commands from your computer to finish the process]. once you have android sdk and go through the download manager process go to the folder [usually c:\androidsdk or c:\program files sdk in command prompt [windows key [on keyboard] +r and type cmd in the box]] once this comes up use cd to move to directories and do a cd c:\androidsdk [you may need to search to find the folder] once in you will then need to cd platform-tools and adb is there [type dir ,enter. and that will list files in dir [this dir is hidden in explorer go to control panel>folders> and check the box under view tab labeld show hidden and system file] and you will then see platform-tolls under your google sdk folder so back in command prompt when in platform-tools now type adb shell and you should see either a # or some text stating adb is starting then adb is connecting then the # once you get the # with flashing cursor this is your phone and commands you type are run off the phone [type exit when done to return to c:\androidsdk\platform-tools [or wherever it is stored for you] or you could use reboot or restart [forget which actually closes the connection AND causes phone to restart]. hope this help if not check here: [How TO] Simple Root and Custom Recovery Installation and Install ROM - WINDOWS - Android Forums

[Paddy464]

I can't seem to get the trackpad to work to navigate through the recovery menu list. It does work to select something, but all I can select is reboot. I was able to find the 1.7.6 recovery and use the volume up/down buttons to navigate through the menu. Any ideas how to resolve the trackpad navigation issue?

[turl]

Does your trackpad work fine on the system itself? Can you go through lists on android apps, for instance, using it?

[xJAYEMMx]

similarly, mine recently goes berserk sometimes. when i move up, it twitches down + up or when i move down, it twitches up+down

[Paddy464]

Turl - Yep, I have no problem using the trackpad otherwise. In fact, now that I have the clockwork recovery re-installed, I am able to use the trackpad within that app.

[adlx]

Ok I get this when I am flashing this recovery.img

# flash_image recovery /sdcard/j_r0dd-mb501-v1.7.6.img
flash_image recovery /sdcard/j_r0dd-mb501-v1.7.6.img
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x000a0000
mtd: not writing bad block at 0x000c0000
mtd: not writing bad block at 0x000e0000
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x000a0000
mtd: not writing bad block at 0x000c0000

Forgot what that means again.

OK TOO WEIRD...it worked and I got the recovery installed...when I hit the volume down key it lists a bunch of lines starting with BB<hex code> and then goes into recovery...how strange....doing a nand backup now....guess it works despite the anomalies....only thing different than from when I did this before is that I flashed via rdslite the 1.32.20 rom with new radio. ah well it works.

I've made a mod of latest CWM 5.0.1.0 to make it a bit smaller (from 3392Kb to 2876KB). Hopefully people with bad block issues may now be able to flash it.

Here it is:

http://www.crackflashers.com/Adumont...in-XS-adlx.img

It's also available for flashing though my 1-click Recovery Flasher (on the Market).

[josuearisty]

I've made a mod of latest CWM 5.0.1.0 to make it a bit smaller (from 3392Kb to 2876KB). Hopefully people with bad block issues may now be able to flash it.

Here it is:

http://www.crackflashers.com/Adumont...in-XS-adlx.img

It's also available for flashing though my 1-click Recovery Flasher (on the Market).

Excellent, you the best man!

[Saurus]

I've made a mod of latest CWM 5.0.1.0 to make it a bit smaller (from 3392Kb to 2876KB). Hopefully people with bad block issues may now be able to flash it.

Nope. Still get the bad blocks on my #2 XT 00-18 by twosies, same as before - (#1 no prob; of course IT'S the one still in warranty). Appreciate the effort, though.

<EDIT>

Previous attempt was performed during earth-shattering brain fart. Short version: I did it wrong.

Flashed adlx's new .img - still got same list of bad blocks (10 of them) but listed twice...and without the 'out of memory' message at the end.
On this promising note, I removed /system/recovery.img and rebooted. OH FOR JOY! I am now looking at the CWM Recovery screen!!! Thank you, [MENTION=3081367]adlx[/MENTION]! (Insert applause, accolades, hugs & kisses, etc. here...)

[Pepsi274]

I got mtd: not writing bad block at 0x0000000 then i got error writing recovery: no space left on device
do i just leave it be and cant rom the phone is that the safe thing to do

[turl]

I got mtd: not writing bad block at 0x0000000 then i got error writing recovery: no space left on device
do i just leave it be and cant rom the phone is that the safe thing to do

Try with the ultra small recovery adlx did, if you still get 'no space left on device' with it, I guess you won't be able to do much to your phone unfortunately