Database Develop

[Q] Neeed Halp with rooting samsung galaxy s vibrant on bell

I was wondering if i was the only one who's a noob on this site because i have been trying (with no success) to root my using some good directions which i have posted below. The problem is... i only speak noob. I am so new to this stuff that i really dont know what to do. What i have already done is downloaded the update.zip and the SDK i dunno if i installed it properly but i know i have to go into my cmd and type something... from then on there i have no clue what to do. ANY HELP IS GREATLY APPRECIATED ^_^
Originally Posted by AllGamer View Post
Step 1. root your phone
Bell's I9000M is slightly different than the regular I9000
most of the root methods mentioned on other topics will not work.
Even the 3 button recovery mode has been disabled
After some experimentation this is the working method
download the update.zip from this topic (Thanks to jentech)
then you need to run adb devices to make sure your phone is listed
(ADB is part of Android SDK, download it from the source
if you get something like
Code:
adb.exe devices
List of devices attached
900098c722a9 device
(if you run adb.exe devices and comes back with an empty list, then make sure you have set the phone into debugging mode Application > Settings > Development > USB Debugging)
then you are can execute
adb.exe reboot recovery
this will take you to the recovery screen
now if your device works with the Power + Volume Up + Home button, then you can skip that, however in my case the 3 button mode didn't work
select the update.zip with the volumen up down button, then hit home screen, it should say installing in yellow, then you are done, it reboots back to normal, and now you can install Busy Box

Before you begin get some important info from the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series
just glance through it, and look at the pretty pictures.
then to Root you phone follow this topic, which is also linked on the Wiki
Self Unlock SGS tutorial
http://forum.xda-developers.com/showthread.php?t=747235
which starts from the basic, to root, all the way to unlocking the phone
post back if you have any question or get stuck at any point
just in case you missed it, make sure your 3 buttons Recovery Mode is working, else keeps all your finger crossed for good luck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the update.zip that you seek is attached to the link of the rooting/unlocking topic linked above

if the 3 button recovery mode doesn't work
using the Android SDK you installed run the ADB.EXE command
it is inside one of the folders after you unzip the Android SDK package

k so the 3 button thing was a no go :/ do you think you could walk me thru (slowly) how to do the whole abd thing properly? Also the link you reffered me to is exactly what is on this thread and i just dont have enough experience to understand each of the steps, if u can just give me the main pointers in noob talk then i think ill be albe to figure out the rest

yeap, you need to copy the update.zip into the phone internal SD card
you can do that by simply connecting the phone to the PC on the USB cable
instead of USB debugging mode, just choose USB Kies mode
make sure Kies is installed

AllGamer said:
yeap, you need to copy the update.zip into the phone internal SD card
you can do that by simply connecting the phone to the PC on the USB cable
instead of USB debugging mode, just choose USB Kies mode
make sure Kies is installed
Click to expand...
Click to collapse
Can i do that while im on recovery mode or will that eff evrything up?

So i now have no idea how to put the update.zip file onto my internal sd card there is nothing on the phone i checked all the settings and i disabled the debug...

does the windows explorer shows the drive letters?
just copy and paste the update.zip file into the Internal SD card of your phone
when you connect via Kies mode to your PC
the windows explorers automatically pops up too

Bell root is not possible!
i may try samsung keys however i dont see how that helps you put the update.zip on your internal memory card or allows you to access anything in adb.exe in command promp.....my main question is acctually how the heck do you root the samsung vibrant with bell??? I have tried the thread in xda developers forum for bell saying it is the only way to get it to work....well it willl not work along with the million other ways i have tried, except 1clickroot it bricks alot of phones. Has anyone successfully rooted vibrant with bell! If so how?! I have even tried Z4Root which is the preferable method, well maybe i will just have to wait until some figures out a way that works. Boot with 3 button method "up vulume +menu+power" then apply sdcard:update.zip
E:signature verification failed
Installation aborted.
It says this everytime no matter what way i try!!! please someone have a solution!

Here you go...
This worked well for me.
http://forum.xda-developers.com/showthread.php?t=803682
Read all instructions carefully!

Rooted!
Thanks worked like a charm good thing only way I had left to root my phone. Any ideas how to apply the lag fix? One click lag fix will not work "error installing device busy" I tried moving all Apps to external and still wont work? Is there another way?

aub_pro said:
Thanks worked like a charm good thing only way I had left to root my phone. Any ideas how to apply the lag fix? One click lag fix will not work "error installing device busy" I tried moving all Apps to external and still wont work? Is there another way?
Click to expand...
Click to collapse
For my first phone, I tried RyanZA's OCLF (search for oclf in the app market). I did have it installed and working pretty decent but ran into some issues in the beginning trying to apply the lagfix.
On my new phone, I applied Darky's ROM 9.2 with SpeedMod Kernel. You can enable or disable lagfix from recovery mode using CWM (ClockWorkMod) Personally, I just left the lagfix disabled and my phone now is performing way better then my first phone when I had lagfix enabled. (Mind you, my first phone was bricked).

I have downloaded darkys rom 9.2 and cwm recovery in rom manager also downloaded darky configurator from market for 9.2 and enabled speed work kernal in the configurator .do I flash rom with that app or use the flash rom from SD in rom manager? I will read more and try and figure this out....thanks a million for everything but if you could help me with this confusion that would be great lol

aub_pro said:
I have downloaded darkys rom 9.2 and cwm recovery in rom manager also downloaded darky configurator from market for 9.2 and enabled speed work kernal in the configurator .do I flash rom with that app or use the flash rom from SD in rom manager? I will read more and try and figure this out....thanks a million for everything but if you could help me with this confusion that would be great lol
Click to expand...
Click to collapse
Do you have a Bell phone?
- In any case, I had flashed my kernel using odin first.
- Copied the ROM(the entire zip file. don't extract it) over to the root folder of my phone.
- Boot into CWM and selected install zip from sdCard
- Select "choose zip from sdCard
- find the ROM that you downloaded to your phone and select it.
- let the phone do its thing and your good to go.
That was probably the long way but I now see that you can apply the ROM through Darky's Configurator...
- Open up Darky's Configurator
- Select Wipe the device if you want a clean install
- Select your Kernel preference
- Select Modem options (this is why I asked if you were Bell user. Apparently there has been an issue where you loose 850 band if your flashing a new ROM using JL2. So in this option, I selected "no modem")
- Check Alternative WiFi driver
- For the rest of the options you can see you can choose for yourself.
Once you are done with the selection process, press the menu key button on your phone, then choose "Select Zip and Flash".
Follow instructions on phone and you are good to go.

awesome those are much less confusing instructions then others....im stuck on the kernal part download it and extract it and there is no .tar file it is just zimage....file.....i have tried downloading it ten times same result....its the recommended odin 500 kernal
i have tried mounting that file in odin pda and it must not be a .tar cuz it doesnt even see the file....

aub_pro said:
awesome those are much less confusing instructions then others....im stuck on the kernal part download it and extract it and there is no .tar file it is just zimage....file.....i have tried downloading it ten times same result....its the recommended odin 500 kernal
i have tried mounting that file in odin pda and it must not be a .tar cuz it doesnt even see the file....
Click to expand...
Click to collapse
No need to extract that file. Once it is downloaded on to your PC, use Odin and navigate to where the file is downloaded.
I will have to verify the kernel I downloaded when I get home but I'm certain that I did not extract anything.

kernel installed
ok speedmod kernel is installed but when i load up darkys config the wipe all is greyed out and i cant click it.....im assuming that i use boot phone into recovery and whpe/factory data reset from there? wont i lose the darky 9.2 rom then being as it is on the root of the internal card?
the bold parts below are confusing me....so on the internal sd i should have the update.zip and darky rom 9.2 or is it just refurring to darky rom everytime it mentions zip?
Now turn off your phone, and wait for it to shutdown completely. Then, boot into Recovery Mode. Press and hold Volume-UP + Home + Power at the same time, and let go of the buttons when the screen turns on (and says Galaxy S GT-I9000/I9000M Samsung), to enter Recovery.
7. Then using the volume keys to navigate and the Power button to select, do the following:
Select 'wipe data/factory reset', and then select 'Yes'. Important!
Select ‘Install zip from sdcard’.
Then select ‘choose zip from sdcard’.
Now navigate to the ROM zip, then select it.
Then choose ‘Yes’.
8. The ROM will now be installed. After it says install complete, select ‘Go Back’ twice, then select 'Reboot System now'.
There you go, Darky's ROM is now installed!

k i figured it out im at the last step installing update.....been at this screen for about 10 mins but im sure thats normal.?

k it was hanging way to long on the installing updates screen and appeared to be frozen so i press menu + vol up + power and after a few time of it hanging at the galaxy s screen it finally brought me to clockwork recovery....so i rebooted normally and now i have the speed kernal still installed still rooted but the phone is original hardware? what do i do now?

Hey
....when you go to the menu settings about on your phone, what does the build number say?
Do you have Darkys Configurator app installed? Use that to flash the new rom. If you have nothing on your phone I would choose wipe. Choose the itmes that you want in the configurator. Select the menu button on your phone then select the option Save zip and exit... the second button in the bottom right.
Then choose Darkys rom where you saved it on your phone.
Sent from my GT-I9000 using XDA App

[Unofficial][Recovery][Ideos X6] CWM Recovery 4.0.1.4 [Update]

Clockworkmod Recovery for Huawei U9000 Ideos X6 phone
which is also known as CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410Basically, its an update to the latest version of CWM recovery released by tj_style
[Features Working]
Backup
Restore
Install From Zip
ADB recovery support
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mounting sd card as USB storage device from recovery
[Requirements]
One of these mobiles: CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410etc. (with any ROM installed, rooted / un-rooted)
USB data cable
[Installation Instructions]
(This is not an update.zip, please extract zip content and follow these instructions carefully)
Extract recovery.img from cwm-recovery-fb0-v3.zip
Power off your phone. Now press Volume UP + Power button to enter in Download mode (Please keep Volume UP button pressed for a second before pressing Power button)
Connect your phone to PC via USB and wait until USB-Storage device appears on your PC (In Linux, you might see loads of new devices being mounted. But we are concerned about the device with name as 'FIH')
Replace file recovery.img inside the folder image (In windows, X:\image\, where X is drive letter for new USB device)
Safely remove USB device to ensure complete file copy
Disconnect phone from PC
Remove battery of your phone to power off and then start it again.
[Instructions to boot into recovery][Using ADB]
If your phone is up and running then connect it to PC
Issue following command through terminal / Command prompt
Code:
adb reboot recovery
​[Without PC - Using your phones hardware keys]
Power off your phone
Now press Volume UP + Volume DOWN + Power (As said before, please press Volume keys for a second before pressing Power button)
The phone will take few seconds (5 - 10 secs) to boot into recovery mode (It will show splash screen before booting into recovery)
[Navigation]
Select = Power & Search
Move Up = Home & Vol-Up
Move Down = Menu & Vol-Down
Back = Back
Please refer to his post and image for for more details.
http://forum.xda-developers.com/showpost.php?p=16248065&postcount=426
Originally Posted by tj_style
​
[Problems]
When you mount sdcard as USB storage device then do not "Safely remove" it from your computer.
Currently this action disables the usb_mass_storage property and hence you may not be able remount sdcard as USB mass storage device.
[Possible solution]
Instead of safely remove on PC, use 'Disconnect' option from CWM recovery
If you have already used 'Safely remove' option from PC then,
In terminal issue following commands
Code:
[SIZE=2]adb shell[/SIZE][SIZE=2]
# echo 0 > /sys/class/usb_composite/usb_mass_storage/enable[/SIZE][SIZE=2]
# echo 1 > /sys/class/usb_composite/usb_mass_storage/enable[/SIZE]
​
OR Reboot into recovery
[Disclaimer]
I am not to be held liable/responsible if you damage your phone by following/not following this thread.
[Acknowledgement]
tj_style because this CWM recovery is an update to his CWM_recovery_fib0_v2
DooMLoRD for helping me out with my doubts and for familiarizing me with the development
All of you who will test it and give me feedback.

Extra info
Few advantages that I can think of for having
[ADB support in recovery]
As in recovery mode you get SU access, whether your phone is rooted or not, you can issue root level commands like mount, chmod, chown, fdisk
You can read, write to, move, modify, replace any system files (at your own risk)
Many more possible features which you can find by exploring this forum.
[USB support in recovery]
If you are playing with trying out new boot.img, boot-animation.img, splash.img which you are developing side by side, this will prevent all the hassle for rebooting phone just for adding new updated files to sd card (that you have just created)
Though you can use adb push feature in recovery, but I prefer copy / paste using computer as it checks for complete file transfer before ejecting the drive
[Disclaimer]
I am not to be held responsible for any damage to your phone after following this post.

Napstar said:
If you have already used 'Safely remove' option from PC then,
In terminal issue following commands
Code:
adb shell
# echo 0 > /sys/class/usb_composite/usb_mass_storage/enable
# echo 1 > /sys/class/usb_composite/usb_mass_storage/enable​
Click to expand...
Click to collapse
While doing this your adb connection might be lost.
So issue
adb shell
after each disconnection.

thanks dude

Working great!

mysteriousboy87 said:
thanks dude
Click to expand...
Click to collapse
Pip_X said:
Working great!
Click to expand...
Click to collapse
Thanx for testing!!

Thanks & one question
hi
thanks adding CWM to this phone is the easiest i have done it was real pain doing it on my other phones
now my question is i have added CWM and i have taken a nand back up of the original Stock rom if i wana go back to the orignal for some warranty purpose in the future
if i do this is it ok
1.do a nand restore with CWM
2.go to down load mode & replace the CWM recovery with the original phones recovery which i have saved on my PC
is this good enough just in case i need to give phone to service for warranty purpose
thanks in advacne

haree said:
hi
thanks adding CWM to this phone is the easiest i have done it was real pain doing it on my other phones
now my question is i have added CWM and i have taken a nand back up of the original Stock rom if i wana go back to the orignal for some warranty purpose in the future
if i do this is it ok
1.do a nand restore with CWM
2.go to down load mode & replace the CWM recovery with the original phones recovery which i have saved on my PC
is this good enough just in case i need to give phone to service for warranty purpose
thanks in advacne
Click to expand...
Click to collapse
Yes you can do this infact all of us does this but keep your nand backup in a safe place, I know u will
Swyped from my MI 410 using XDA App

haree said:
hi
thanks adding CWM to this phone is the easiest i have done it was real pain doing it on my other phones
now my question is i have added CWM and i have taken a nand back up of the original Stock rom if i wana go back to the orignal for some warranty purpose in the future
if i do this is it ok
1.do a nand restore with CWM
2.go to down load mode & replace the CWM recovery with the original phones recovery which i have saved on my PC
is this good enough just in case i need to give phone to service for warranty purpose
thanks in advacne
Click to expand...
Click to collapse
Yes, that will surely do!
Also, as paarkhi has suggested you could also flash original Spice Gingerbread Update file ("nb0" file) using SUTL, since "nb0" files have all original files (bootanimation.zip, recovery.img, boot.img-which includes original kernel) and your phone is already registered for Spice Gingerbread upgrade.
[Though this is single step - easy option but it requires PC, I have one more option which you could use if your on the go and PC is not accessible]
I have posted steps to restore stock recovery at Restoring Recovery - An easy way (CWM / Stock)
and then you can flash any original "nb0" file.

Napstar said:
Clockworkmod Recovery for Huawei U9000 Ideos X6 phone
which is also known as CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410Basically, its an update to the latest version of CWM recovery released by tj_style
[Features Working]
Backup
Restore
Install From Zip
ADB recovery support
Mounting sd card as USB storage device from recovery
[Requirements]
One of these mobiles: CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410etc. (with any ROM installed, rooted / un-rooted)
USB data cable
[Installation Instructions]
(This is not an update.zip, please extract zip content and follow these instructions carefully)
Extract recovery.img from cwm-recovery-fb0-v3.zip
Power off your phone. Now press Volume UP + Power button to enter in Download mode (Please keep Volume UP button pressed for a second before pressing Power button)
Connect your phone to PC via USB and wait until USB-Storage device appears on your PC (In Linux, you might see loads of new devices being mounted. But we are concerned about the device with name as 'FIH')
Replace file recovery.img inside the folder image (In windows, X:\image\, where X is drive letter for new USB device)
Safely remove USB device to ensure complete file copy
Disconnect phone from PC
Remove battery of your phone to power off and then start it again.
[Instructions to boot into recovery][Using ADB]
If your phone is up and running then connect it to PC
Issue following command through terminal / Command prompt
Code:
adb reboot recovery
​[Without PC - Using your phones hardware keys]
Power off your phone
Now press Volume UP + Volume DOWN + Power (As said before, please press Volume keys for a second before pressing Power button)
The phone will take few seconds (5 - 10 secs) to boot into recovery mode (It will show splash screen before booting into recovery)
[Navigation]
Select = Power & Search
Move Up = Home & Vol-Up
Move Down = Menu & Vol-Down
Back = Back
Please refer to his post and image for for more details.
http://forum.xda-developers.com/showpost.php?p=16248065&postcount=426
Originally Posted by tj_style
​
[Problems]
When you mount sdcard as USB storage device then do not "Safely remove" it from your computer.
Currently this action disables the usb_mass_storage property and hence you may not be able remount sdcard as USB mass storage device.
[Possible solution]
Instead of safely remove on PC, use 'Disconnect' option from CWM recovery
If you have already used 'Safely remove' option from PC then,
In terminal issue following commands
Code:
[SIZE=2]adb shell[/SIZE][SIZE=2]
# echo 0 > /sys/class/usb_composite/usb_mass_storage/enable[/SIZE][SIZE=2]
# echo 1 > /sys/class/usb_composite/usb_mass_storage/enable[/SIZE]
​
OR Reboot into recovery
[Disclaimer]
I am not to be held liable/responsible if you damage your phone by following/not following this thread.
[Acknowledgement]
tj_style because this CWM recovery is an update to his CWM_recovery_fib0_v2
DooMLoRD for helping me out with my doubts and for familiarizing me with the development
All of you who will test it and give me feedback.
Click to expand...
Click to collapse
Sent from my GT-I9003 using XDA Free mobile app

[RecoveryMenu] CWM based Recovery menu to enter stock or CWM recovery

CWM based Recovery menu for Huawei U9000 Ideos X6 phone
[which is also known as CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Features Working]
Boot into Clockworkmod recovery [stably ]
Boot into stock recovery [stably ]
ADB recovery support
[Requirements]
One of these mobiles: CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410etc. (with any ROM installed, rooted / un-rooted)
USB data cable / Working CWM recovery
[Installation Instructions][Using CWM recovery]
Copy recovery_menu_v2.0.0.1_signed.zip in sdcard
Boot into recovery (Steps are given below for how-to-boot-into-recovery)
Use "install zip from sdcard" option
Locate and choose recovery_menu_v2.0.0.1_signed.zip from sdcard for instllation
After installation reboot into recovery (advanced > Reboot recovery)
[Using USB cable]
Extract recovery.img from recovery_menu_v2.0.0.1_signed.zip
Power off your phone. Now press Volume UP + Power button to enter in Download mode (Please keep Volume UP button pressed for a second before pressing Power button)
Connect your phone to PC via USB and wait until USB-Storage device appears on your PC (In Linux, you might see loads of new devices being mounted. But we are concerned about the device with name as 'FIH')
Replace file recovery.img inside the folder image (In windows, X:\image\, where X is drive letter for new USB device)
Safely remove USB device to ensure complete file copy
Disconnect phone from PC
Remove battery of your phone to power off and then start it again.
[Instructions to boot into recovery][Using ADB]
If your phone is up and running then connect it to PC
Issue following command through terminal / Command prompt
Code:
adb reboot recovery
​[Without PC - Using your phones hardware keys]
Power off your phone
Now press Volume UP + Volume DOWN + Power (As said before, please press Volume keys for a second before pressing Power button)
The phone will take few seconds (5 - 10 secs) to boot into recovery mode (It will show splash screen before booting into recovery)
[Navigation]
(Same as CWM recovery)
Select = Power & Search
Move Up = Home & Vol-Up
Move Down = Menu & Vol-Down
Back = Back
[Releases]
recovery_menu_v1.0.0.1 (Options for Android System recovery <3e> and CWM based recovery 4.0.1.4) [Download Link1] [Download link2 for MIUI/CM]
recovery_menu_v1.0.0.2 (Fixed support for ext4 filesystem - problems related to MIUI and CM ROM releases) [Download link]
recovery_menu_v2.0.0.1 (Options for Android System recovery <3e> and CWM based recovery 5.0.2.3) [Download link]
[Problems]
Not that I know of.
[Disclaimer]
I am not to be held liable/responsible if you damage your phone by following/not following this thread.
[Acknowledgement]
DooMLoRD for patiently helping me out with all my doubts
koush for his CWM bootable recovery sources.
[For developers]
I will push my sources on github soon. ​

reserved for future use

thanks..
pls port newer cwm 5.xx to our phone its already available for some devices..and ask koush to add our existing cwm to cwm manager... for easy flashing

flashing possible??
i dont think it is possible to flash the recovery image to where it needs to be and also these are built very similar to samsung and how they built the stock recovery in the /system partition

Napstar said:
CWM based Recovery menu for Huawei U9000 Ideos X6 phone
[which is also known as CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410]
[Features Working]
Boot into Clockworkmod recovery [stably ]
Boot into stock recovery [stably ]
ADB recovery support
[Requirements]
One of these mobiles: CherryMobile Magnum, Wellcomm A99, Spice CSL Mi 410etc. (with any ROM installed, rooted / un-rooted)
USB data cable / Working CWM recovery
[Installation Instructions][Using CWM recovery]
Copy recovery_menu_v1.0.0.1_signed.zip in sdcard
Boot into recovery (Steps are given below for how-to-boot-into-recovery)
Use "install zip from sdcard" option
Locate and choose recovery_menu_v1.0.0.1_signed.zip from sdcard for instllation
After installation reboot into recovery (advanced > Reboot recovery)
[Using USB cable]
Extract recovery.img from recovery_menu_v1.0.0.1_signed.zip
Power off your phone. Now press Volume UP + Power button to enter in Download mode (Please keep Volume UP button pressed for a second before pressing Power button)
Connect your phone to PC via USB and wait until USB-Storage device appears on your PC (In Linux, you might see loads of new devices being mounted. But we are concerned about the device with name as 'FIH')
Replace file recovery.img inside the folder image (In windows, X:\image\, where X is drive letter for new USB device)
Safely remove USB device to ensure complete file copy
Disconnect phone from PC
Remove battery of your phone to power off and then start it again.
[Instructions to boot into recovery][Using ADB]
If your phone is up and running then connect it to PC
Issue following command through terminal / Command prompt
Code:
adb reboot recovery
​[Without PC - Using your phones hardware keys]
Power off your phone
Now press Volume UP + Volume DOWN + Power (As said before, please press Volume keys for a second before pressing Power button)
The phone will take few seconds (5 - 10 secs) to boot into recovery mode (It will show splash screen before booting into recovery)
[Navigation]
(Same as CWM recovery)
Select = Power & Search
Move Up = Home & Vol-Up
Move Down = Menu & Vol-Down
Back = Back
[Problems]
Not that I know of.
[Disclaimer]
I am not to be held liable/responsible if you damage your phone by following/not following this thread.
[Acknowledgement]
DooMLoRD for patiently helping me out with all my doubts
koush for his CWM bootable recovery sources.
[For developers]
I will push my sources on github soon. ​
Click to expand...
Click to collapse
do we need to copy META INF FOLDER TOO?

Napstar said:
reserved for future use
Click to expand...
Click to collapse
Now that's what i call a really useful tool thanx a ton

nitindeck said:
thanks..
pls port newer cwm 5.xx to our phone its already available for some devices..and ask koush to add our existing cwm to cwm manager... for easy flashing
Click to expand...
Click to collapse
I will post it today if I am successful!

bandukia said:
do we need to copy META INF FOLDER TOO?
Click to expand...
Click to collapse
[Complete zip file for CWM based installation]
I guess here everyone must have working CWM recovery on their device. In that case just place the downloaded recovery_menu_v1.0.0.1_signed.zip file in your sdcard and install it using CWM recovery's "install zip from sdcard" option.
[Only recovery.img file for USB based instalation]
Otherwise just extract recovery.img from the zip file and replace it from /image folder that you will find in USB device that gets loaded when you conect your phone to PC in download mode.

snakebitezz said:
i dont think it is possible to flash the recovery image to where it needs to be
Click to expand...
Click to collapse
Do you mean flashing using CWM recovery. In that case, I have not flashed recovery.img like we do for boot.img
I have just extracted it to FIH partition. You can check my updater script in META-INF/google/android/updater-script file from zip
snakebitezz said:
and also these are built very similar to samsung and how they built the stock recovery in the /system partition
Click to expand...
Click to collapse
Sorry, I did not understand what you wanted to say. Can you please elaborate?

napstar you still havent replied my pm

huh this is a thing which deserve THANX more then eating my food ,,, guys before u download first thank the person who is behind it ... Jai ho Napstar Hats off to u

kshitij_bhatt said:
huh this is a thing which deserve THANX more then eating my food ,,, guys before u download first thank the person who is behind it ... Jai ho Napstar Hats off to u
Click to expand...
Click to collapse
Thanx for your complement!!

I have one bug to report. On latest MiUi your latest CWM will not mount /system.

Sergekarol said:
I have one bug to report. On latest MiUi your latest CWM will not mount /system.
Click to expand...
Click to collapse
Well, any ROM / FW should not bother CWM's activity. They function independent of each other.
Anyway, I will try new MIUI tomorrow as I cant download it now at my home with low bandwidth.
By the way can you send me the log files for recovery. (/cache/recovery/).
And also what exactly were you trying to do when this error occurred?

Napstar said:
Well, any ROM / FW should not bother CWM's activity. They function independent of each other.
Anyway, I will try new MIUI tomorrow as I cant download it now at my home with low bandwidth.
By the way can you send me the log files for recovery. (/cache/recovery/).
And also what exactly were you trying to do when this error occurred?
Click to expand...
Click to collapse
No problems Here is the zipped file. Its strange that mounting /data has no issues. I was installing an update zip that needed /system mounted. BTW It wouldn't make a backup either. I am restoring my old Andro-id RC2 and starting over tomorrow. I can help you then. After I restored the old backup it started working again. Maybe it was a phone issue.

Sergekarol said:
No problems Here is the zipped file. Its strange that mounting /data has no issues. I was installing an update zip that needed /system mounted. BTW It wouldn't make a backup either. I am restoring my old Andro-id RC2 and starting over tomorrow. I can help you then. After I restored the old backup it started working again. Maybe it was a phone issue.
Click to expand...
Click to collapse
Sorry to quote myself but I have a workaround to post. It seems to be a common MIUI issue and here is a workaround. Hook up your usb cable and using adb devices to start up server issue this command while in the CWM menu
Code:
adb shell mount /dev/block/mmcblk0p7 /system
The system then is mounted and you can backup you MiUi system. or install updates that need the /system mounted. perhaps you can figure out why it failed using this info.

There must be some issue with fstab...
Or u can always use ensure partition mount OR _system

Sergekarol said:
Sorry to quote myself but I have a workaround to post. It seems to be a common MIUI issue and here is a workaround. Hook up your usb cable and using adb devices to start up server issue this command while in the CWM menu
Code:
adb shell mount /dev/block/mmcblk0p7 /system
The system then is mounted and you can backup you MiUi system. or install updates that need the /system mounted. perhaps you can figure out why it failed using this info.
Click to expand...
Click to collapse
DooMLoRD said:
There must be some issue with fstab...
Or u can always use ensure partition mount OR _system
Click to expand...
Click to collapse
As rightly pointed out by DoomLoRD, there is a problem with fstab for MIUI OS.
Since Cyanogenmod and MIUI releases for our devices support ext4 filesystem and has there /system partition formatted with ext4 type, it prevents CWM to mount /system partition.
This is because our stock/official ROMs have /system partition of ext3 type and CWM is designed by keeping that in mind.
I have uploaded a modified CWM based recovery menu for MIUI and CM users in the first post. Please use it when you are on those ROMs. And make sure to install appropriate recovery_menu immediately after installing any type of ROM.
P.S. The update.zip that you were trying to install was not supported for our device. Please make sure compatibility of any softwares/apps before installing if you are not using Android market. I have attached a modified version of it (ESRight.v4-1.9.9.zip) with this post.

Napstar said:
As rightly pointed out by DoomLoRD, there is a problem with fstab for MIUI OS.
Since Cyanogenmod and MIUI releases for our devices support ext4 filesystem and has there /system partition formatted with ext4 type, it prevents CWM to mount /system partition.
This is because our stock/official ROMs have /system partition of ext3 type and CWM is designed by keeping that in mind.
I have uploaded a modified CWM based recovery menu for MIUI and CM users in the first post. Please use it when you are on those ROMs. And make sure to install appropriate recovery_menu immediately after installing any type of ROM.
P.S. The update.zip that you were trying to install was not supported for our device. Please make sure compatibility of any softwares/apps before installing if you are not using Android market. I have attached a modified version of it (ESRight.v4-1.9.9.zip) with this post.
Click to expand...
Click to collapse
Yea I knew it wasn't compatable but I knew a workaround but the workaround failed. Sorry Thanks for fixing

Sergekarol said:
Yea I knew it wasn't compatable but I knew a workaround but the workaround failed. Sorry Thanks for fixing
Click to expand...
Click to collapse
One more fix on its way.
Features included:
No need of switching between two different Recovery_menu. (Compatible for all ROMs)
Newer version of CWM Recovery v5.0.2.3 included
In testing stage...
Will upload in some time..

[HOW-TO] Real DUAL BOOT for O2X V2 [Inc. Video Tutorial]

DUAL BOOT for LG O2X v2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
This is a guide to get Real Dual boot on O2X, please be careful because this may brick your phone if you don´t know what you are doing. The method is based on a method i found on a Chinese forum but i moded it to have more space on system and data partition and fixed some bugs i found on it.
V2 Changelog:
Increased System partition size, now we have around 370 MB for each ROM, so we don´t need to reduce the size of the ROMs
No need to download ROM for nvflash by Homero, instead i made a NVFlash Partition resizer with a smaller size ( 14 MB)
Better fix for Internal SD corruption
Included Touch CWM Recovery ( important for Internal SD)
Reduced several steps in this guide to make the process shorter and easier
To update to V2 from V1, make a nand backup and backup your internalSD, then do the resizing process and use the new DUAL-ROM... process.
What is this usefull for?
Devs: you can have one ROM configured and ready for use in one partition and a second partition to test your ROMs without touching your daily ROM, so you won´t need to wipe or backup any thing.
Users: you can have a stable ROM, lets say a stock ROM with everything working and configured and you can have a second partition to test ROMs ( for example a new miui v4 or a CM10 beta..) so you won´t need to do backups and wipes.
How Dual boot works?
There are three important file:
Dual-Enabler.zip: this file enables Dual boot by splitting system partition into two.
Dual-ROM-1-to-XX.zip: this file have to be flashed after flashing ROM 1, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting change, the phone will reboot and start the ROM 2.
Dual-ROM-2-to-XX.zip: this file have to be flashed after flashing ROM 2, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting change, the phone will reboot and start the ROM 1.
Note: It may look long and complex but when you understand the process it is very easy.​
Installation
Video tutorial that shows how to install and how it works, please first read the steps below to understand the process
The video is made by Ajsh big thanks to him
Click here if you are not able to watch the video
​--> Resizing partitions:
First we need to resize the system partition to have enough space for any ROM and more space in data partition ( only can have 2GB on data due to CWM limitation, so we have 2GB for two ROMs , data partition won´t be split, that is to say both roms will save their data in the same partition ). This will reduce your internal SD available space.​
Before continue, it is recommended to have an external SD just in case( the size does not mind).​ATTENTION: The resize operation will format all memory, including the Internal SD, so backup your Internal SD. The external SD is not affected.​
Download the NVFlash_Partition-resizer.zip - 14.23 MB and extract it with winrar or similar, it includes the APX driver (folder driver).
Download Dual boot O2x - v2.zip - 5.31 MB and unzip it to any folder
Power off and remove the battery of your phone.
While holding volume up and down, connect the USB cable to the device - screen will stay black but Windows will add a new 'APX' device, go to Control panel on your PC->System-> Devices manager you will see a device with yellow exclamation, right click->update driver->search in this system then browse to ..\NVFlash_Partition-resizer\Drivers which is the folder you extracted in step 1, now click next and it will install the device Nvidia boot.....
Now go the the folder NVFlash_Partition-resizer and click on flash.bat and wait until it finish the process.
Now unplug the USB cable, put the battery back.
Power on the phone and by pressing power button + vol down you will enter the recovery
Go to mounts and storage -> mount USB storage, your PC will ask you to format the InternalSD, so select yes.
Let the phone on this state and continue reading....
--> Preparing the ROMs: We need the two roms you want to use, lets call them ROM1 and ROM2 in this guide.​
Open the ROM1 with winrar o similar and drag the boot.img from the zip to a folder and rename it to boot1.img , then open Dual-ROM-2-to-XX.zip and add the boot1.img to \system\boot, overwrite the existing one.
Open the ROM2 with winrar o similar and drag the boot.img from the zip to a folder and rename it to boot2.img , then open Dual-ROM-1-to-XX.zip and add the boot2.img to \system\boot, overwrite the existing one.
Now return to your phone which is on recovery mode, go to mount and storage and select mount usb storage.
Now copy ROM1, ROM2, Dual-Enabler.zip, Dual-ROM-1-to-XX.zip, and Dual-ROM-2-to-XX.zip to your SD
Flash Dual-Enabler.zip, the phone will reboot, so when you see black screen, quickly press and hold Power button + vol down to enter recovery again, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
Make a full wipe to avoid boot-loops.
Now flash ROM1 and without rebooting flash Dual-ROM-1-to-XX.zip and reboot.
When the phone completely boots, you will find an app called SystemChanger, launch it and click Switching, i will asks you for root rights, click yes, the phone will reboot so quickly press and hold Power button + vol down to enter recovery, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
Now flash ROM2 and without rebooting flash Dual-ROM-2-to-XX.zip and reboot.
And that is all, if you want to switch to ROM1, as before, run SystemChanger and click Switching.
Note: Only if the internal SD is not available or still corrupt when you finish the process, you can fix it by doing the following: flash any stock Gb ROM and when it completely booted, you will have the option to format the InternalSD.
​
Tips and advices:
What ROMs can i use?
You can use any combination of ROMs for dual booting ( CM roms, MIUI roms, non wipe stock ROMs...), the only ROMs you should not use are Auto-wipe ROMs because they will delete your data partition and with it ROM1 and ROM2 save files, of course if you are an advanced user, you can open the wipe rom and modify the updater-script to remove the auto wipe lines.​What about ROMs size?The system folder of any ROM should not be bigger than 370MB extracted, so if it is bigger you should reduce it by deleting apps you do no use from system/app.​I want to change ROM1 or ROM2 with a new ROM, what sould i do?
Lets suppose you want to change ROM2. Open the new ROM with winrar o similar and drag the boot.img from the zip to a folder and rename it to boot2.img , then open Dual-ROM-1-to-XX.zip and add the boot2.img to \system\boot, overwrite the existing one. Then transfer the new ROM and Dual-ROM-1-to-XX.zip to your SD.
Then you have to be on the ROM you don´t want to change, for example if i want to change ROM2, then i have to be in ROM1. The reason of doing this is because we need to delete some files on data partition used by ROM2 because those files may wont be compatible with your new ROM, of course you won´t need to do this if ROM2 and the new ROM are compatible and do not need a wipe to flash new rom.
While we are on ROM1, we need an explorer with root rights like root explorer or solid explorer.then we go to /data/ and delete these folders: dalvik-cache-2, app-2, data-2, lgdrm-2, misc-2 and system-2 , basically are the folder with a -2 (or -1 if you are changing ROM1) in the name. This is equivalent to a full wipe because we delete all folder where ROM2 saves its data. Alternative Only for advanced users: There is a easier way, you can be on ROM2, enter recovery (mount DATA) and with a PC software like Android commander you can delete those folders or via ADB shell.
Now we run Systemchanger and click Switching, the phone will reboot so quickly press and hold Power button + vol down to enter recovery and flash the new ROM and without rebooting flash Dual-ROM-2-to-XX.zip and reboot, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
When the phone boots it is recommended to switch to ROM1 and flash Dual-ROM-1-to-XX.zip to have the kernel of the new ROM so when we switch again to ROM2(the new ROM), it will boot correctly.
I want to update ROM1 or ROM2, what should i do?
You have to be on the ROM you want to update
Enter Recovery
Flash the ROM update and flash Dual-ROM-1-to-XX.zip if you are updating ROM1 or flash Dual-ROM-2-to-XX.zip if you are updating ROM2.
What about backups?
If you do a nand backup, it will backup the system partition of the ROM you are in( ROM1 or ROM2) and all data partion with the data of both ROMs, so if you restore that backup, you will be able to boot correctly the ROM you were on when you made the backup, to boot the other ROM, you have to run Systemchanger and swithc to the other ROM, but quicly enter to recovery and flash again the other rom and its Dual-ROM-x-to-XX.zip.
huy_gm said:
Can i use this without losing my current running rom?.
Click to expand...
Click to collapse
Easy, first make a nand backup of your current ROM, then follow my guide to get dual boot, when finished, just restore that nand backup while on ROM1 for example. of course make sure your system partion size is smaller than 370MB.
Whats the way to rollback to one ROM system and original partition sizes?
Flashing a nvflash rom or any stock rom via smartflasher will do the trick .
Some notes:
As i said before, both roms share the 2GB of space, so you should use that space smartly, for example do no install a lot of apps on the test ROM, instead use is your main rom to install all the apps you need, for big apps, move them to SD.
As i said, you have to take the kernel (boot.img) from ROMx to put it in Dual-Rom-xxx, this is true if you are going to use the default kernel that comes with ROMx, if you flashed another kernel independent from ROMx, you should take the boot.img from that kernel and put it on Dual-Rom-xxx. if there is no boot.img on kernel.zip installer, you can use terminal emulator from play store or adb shell to extract a boot.img from the rom with the independent kernel already installed by this code:
su
dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
Click to expand...
Click to collapse
Example: If the kernel is in boot.img format, simply put it on dual-rom as i say on 1st post, if not, then first install cm7 +kernel+gapps and when it boots use terminal emulator to extract boot.img from your phone.
For better ROM changing: i have several Dual-ROM-x-to-XX.zip, for example: Dual-ROM-1-to-CM7.zip, Dual-ROM-2-to-CM9.zip Dual-ROM-1-to-stock.zip.... so that way i change ROMs easily. Of course this is valid if you always use ROM default kernels, if not, you should put the right bootX.img into the right Dual-ROM-x-to-XX.zip
Thanks to:
The creator of the scripts and System changer ChinaGB.
Homero for its nvflash ROM.
Modaco for Nvflash method
Owain for the partition resize guide
Ajsh for the great video tutorial
If you like my work, please hit the Thanks button.

Wow, sounds amazing, thanks for this. I will try it later and report back !
One thing:
8. Now flash ROM2 and without rebooting flash Dual-ROM-1-to-XX.zip and reboot.
Click to expand...
Click to collapse
Am I wrong or should it be Dual-ROM-2-to-XX.zip ?

d1dd1 said:
Wow, sounds amazing, thanks for this. I will try it later and report back !
One thing:
Am I wrong or should it be Dual-ROM-2-to-XX.zip ?
Click to expand...
Click to collapse
yes, corrected it.

Wow,been waiting for such options D ,greatly appreciated
Just curious,have you seen multiboot tread on motorola defy? Its made so you can install several roms on sd card.....if not you should check it out,new challenge

SuperSkill said:
Wow,been waiting for such options D ,greatly appreciated
Just curious,have you seen multiboot tread on motorola defy? Its made so you can install several roms on sd card.....if not you should check it out,new challenge
Click to expand...
Click to collapse
yes i saw it, but i don´t like that method because the phone get very slow and laggy due to sdcard speed, my method is better because it uses the nand memory on both roms. Also i think we do not need more than two roms really.

The bad thing is it uses system changer not some boot loader screen menu, so if one OS gets corrupt, you'll be stuck?

Ferrum Master said:
The bad thing is it uses system changer not some boot loader screen menu, so if one OS gets corrupt, you'll be stuck?
Click to expand...
Click to collapse
no, if one OS gets corrupt, enter to recovery and flash it again or flash other ROM, and to delete the corrupted OS data files, you can use Android commander pc program to delete them or you can also use aroma file manager which is a file explorer that can be started from recovery.

bihariel said:
no, if one OS gets corrupt, enter to recovery and flash it again or flash other ROM, and to delete the corrupted OS data files, you can use Android commander pc program to delete them or you can also use aroma file manager which is a file explorer that can be started from recovery.
Click to expand...
Click to collapse
By meaning stuck... I meant the fact you'll have to do some recovery stuff in order to boot at least one OS and fast, as it always needed.
But for playing around OK, I got the Idea... not as smooth as in my N9 but still nice

Please redownload this file Dual boot O2x.zip again, the other one has a bug.

I waited very long for Dual Boot and now I can have ICS and CM7 on my Device.
thanks mate

It sounds like Christmas, Eastern and Birthday in my ears *___*
If that works, it will be on the same level as a 100% working ICS/JB ROM !!

What doesn't work? If there isn't problem it's fantastic! Thank you
Inviato dal mio Optimus 2X con Tapatalk 2

Thanks so much for this. I wonder if i can use this without losing my current running rom?
Is there a way to modify nandroid backup for it to be compatiple with new boot method?

huy_gm said:
Can i use this without losing my current runningrom? What if we modify nand backup for it to compatiple with new boot method.
Click to expand...
Click to collapse
esay, first make a nand backup of your current ROM, then follow my guide to get dual boot, when finished, just restore that nand backup while on ROM1 for example. of course make sure your system partion size is smaller than 310MB.

i have a problem.
After replace the cfg file and run the batch the phone is stuck in the epgrade software screen.
If i pull the battery and press the power + volume down button the phone doesn't boot.
If i don't replce the cfg file everything is fine and the phone boots normally.
I've redownloaded the zip and the problem persist.

Cice96 said:
i have a problem.
After replace the cfg file and run the batch the phone is stuck in the epgrade software screen.
If i pull the battery and press the power + volume down button the phone doesn't boot.
If i don't replce the cfg file everything is fine and the phone boots normally.
I've redownloaded the zip and the problem persist.
Click to expand...
Click to collapse
that is strange, i repeated the process again and it boots. just unplug the cable, put back the battery and power on + vol down.
anyone else has the same problem?

Cice96 said:
i have a problem.
After replace the cfg file and run the batch the phone is stuck in the epgrade software screen.
If i pull the battery and press the power + volume down button the phone doesn't boot.
If i don't replce the cfg file everything is fine and the phone boots normally.
I've redownloaded the zip and the problem persist.
Click to expand...
Click to collapse
i detected the problem.sorry i reupload again.

I also detected it. just edit the cfg file.

Cice96 said:
I also detected it. just edit the cfg file.
Click to expand...
Click to collapse
ok, smart boy, heheh

Now it works

[Recovery][UCTR] Team UtterChaos' Touch Recovery with Full Touch panel support

Team UtterChaos' Touch Recovery based on Clockworkmod Recovery v6 for Nexus 4 device​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​[Features Working] ​
Full Touch Panel support for menu navigation
Touch gesture support added for Go back and page up/down actions
Lower panel menu buttons as an added option for menu navigation
All hardware keys functionality retained.
[Requirements]​
Nexus 4 (considering it's demand)
USB data cable(optional)
Any custom recovery (optional)
[ Downloads]​
[UCTR][Nexus4] Team UtterChaos' touch recovery image based on CWMR v6
[UCTR][Nexus4] Team UtterChaos' touch recovery - permanent update zip for installation
[UCTR][Nexus4] Team UtterChaos' touch recovery - temporary update zip for other recoveries
[Installation Instructions]
​
[Permanent installation through fastboot]
Download and place UCTR-Nexus4.img at some place on your computer
Boot into bootloader mode (Hold Volume down and Power key while switching on your device)
Issue following command in terminal/command prompt (Note: You should change your directory to place where you have downloaded the img file)
In order to try, boot into UCTR via,
Code:
fastboot boot UCTR-Nexus4.img
In order to flash UCTR permanently use,
Code:
fastboot flash recovery UCTR-Nexus4.img
[Permanent installation through custom recoveries]
Download and place UCTR-Nexus4-perm-signed.zip in internal sdcard
Boot into any custom recovery (Steps are given below for how-to-boot-into-recovery)
Use "install zip from sdcard" option
Locate and choose UCTR-Nexus4-perm-signed.zipfrom sdcard for installation
After installation reboot back into recovery (advanced > Reboot recovery)
[Temporary installation through custom recoveries - for Trial purpose]
Download and place UCTR-Nexus4-temp-signed.zip in internal sdcard
Boot into any custom recovery (Steps are given below for how-to-boot-into-recovery)
Use "install zip from sdcard" option
Locate and choose UCTR-Nexus4-temp-signed.zipfrom sdcard for installation
After installation, it will automatically execute UC-Touch Recovery for trial experience.
When you reboot into recovery, you will still find older installed recovery intact.
[Instructions to boot into recovery]​[Using ADB]
If your phone is up and running then connect it to PC
Issue following command through terminal / Command prompt
Code:
adb reboot recovery
[Without PC - Using your phones hardware keys]
Power off your phone
Now press Volume DOWN + Power (Please press Volume keys for a second before pressing Power button)
The phone will take few seconds (5 - 10 secs) to boot into bootloader mode
Now select recovery mode using Volume keys and press Power key to select
[Navigation]​
[Touch inputs]
Use touch panel menu buttons at the bottom of screen for navigations.
For full panel touch inputs select any entry by clicking withing its boundary.
Use touch panel's back from menu or swipe from right to left (leftwards) on screen for return action.
When in a multi-page case, like scrolling through Int. sdcard content, light green partial entry will appear as final entry. In such case swipe left to right (rightwards) for Page Up action and from right to left (leftwards) for Page Down action.
Check out this video to know how about.
[Device keys]
Select = Power
Move Up = Vol-Up
Move Down = Vol-Down
[Problems]​
Let me know!
[Disclaimer]
​ I am not to be held liable/responsible if you damage your phone by following/not following this thread.
[Acknowledgement]
​
koush for his CWM bootable recovery sources.
Steam recovery sources by SteamMOD for touch input related modifications.
DoomLoRD for continuously nudging me into building this

reserved

reserved

First
Sent from my Nexus 4 using xda app-developers app

Nice recovery thank you...
Gesendet von meinem Nexus 4 mit Tapatalk 2

Beautiful recovery well done!
Thanks

I think I'll try this now...
Sent from my Nexus 4 using Tapatalk 2

Looking good, thanks for giving us more options :thumbup:
Sent from my Nexus 4

napstar: nice recovery bravo
is it possible to add black wallpaper only because your wallpaper is nice but not readable when we navigate in folder

pixiebob said:
napstar: nice recovery bravo
is it possible to add black wallpaper only because your wallpaper is nice but not readable when we navigate in folder
Click to expand...
Click to collapse
we will later add capability to customize the recovery by allowing users to choose their own background image/etc...

pixiebob said:
napstar: nice recovery bravo
is it possible to add black wallpaper only because your wallpaper is nice but not readable when we navigate in folder
Click to expand...
Click to collapse
We will try to find some solution, like DoomLoRD suggested in future builds.

I know this is CWM based but using this would we be able to restore our original CWM backups? And would CWM be able to restore the backups created but this recovery?

Firstly, thanks for this recovery.
Just one question; does adb sideload works? (actually adb sideload is broken in CWM 6.0.2.3, just works in CWM 6.0.2.0)
Thanks and best regards.

gqukyo said:
I know this is CWM based but using this would we be able to restore our original CWM backups? And would CWM be able to restore the backups created but this recovery?
Click to expand...
Click to collapse
Yes, they should work. UCTR's backend is CWM only.
VivaErBetis said:
Firstly, thanks for this recovery.
Just one question; does adb sideload works? (actually adb sideload is broken in CWM 6.0.2.3, just works in CWM 6.0.2.0)
Thanks and best regards.
Click to expand...
Click to collapse
It is broken, there is a problem with adb daemon binary. It will be replaced/corrected in next build.
Edit:
Till then there is a small workaround,
Install "UCTR-Nexus4-temp-signed.zip" from within recovery
Doing this will take you too UCTR only, but with functional sideloading

awesome, glad to see you two around! haven't played with anything from napster or doomlord since he built blind for the kindle fire and used my device over teamviewer lol. gonna take this for a test drive!

Nicely done:good:

Will definitely try when the background is changed. Right now it's hard to read.
Sent from my Nexus 4 using Tapatalk 2