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..
Related
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
Full touch supported Clockworkmod Recovery v5 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]
Full Touch Panel support for menu navigation
Touch gesture support added for Go back and page up/down actions
ICS like menu buttons as an added option for menu navigation
All harware keys functionality retained.
Advanced Backup option for backing up in either TAR or IMG format. (Might be useful for Custom ROM developers using dsixda's kitchen)
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
[ Downloads]
Full Touch supported CWM based recovery v5.0.2.7
CWM based recovery v5.0.2.7
[Installation Instructions][Using CWM recovery]
Copy CWM recovery-fb0-v5_signed.zipin sdcard
Boot into recovery (Steps are given below for how-to-boot-into-recovery)
Use "install zip from sdcard" option
Locate and choose CWM recovery-fb0-v5_signed.zip from sdcard for instllation
After installation reboot into recovery (advanced > Reboot recovery)
[Using USB cable]
Extract recovery.img from CWM recovery-fb0-v5_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]
[Touch inputs]
Use touch panel buttons at the bottom of screen for navigations.
Hover finger over menu buttons on screen and lift your finger on desired selection when it gets highlighted.
Use touch panel's back or device key's back button for return action.
Check out this video to know how about.
[Device keys]
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]
Currently gesture support is not included for menu navigation.
Same issue with using "USB Safely remove" option. Please refer to this thread for possible solutions. [Unofficial][Recovery][Ideos X6] CWM Recovery 4.0.1.4 [Update]
Beware, some of your earlier Backups might just show md5sum mismatch. [happened with me] So just keep earlier recovery update.zip in /sdcard, just in case.
The backup format for this recovery is .tar and not .img, this is done [not by me, by koush and CWM developers ] to reduce size of each backup. So, backup generated by using this version are not supported by earlier Recovery releases. But this release can use earlier releases' backup.
[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.
k1chy for testing this touch based CWM recovery on his ideosX6 device. (Since my device is bricked right now, I can not test it )
P.S.: I have purposefully kept same format as for my older post of CWM Recovery v3, so that it will be helpful for any new user to grasp everything at single place.
wats the change log
bandukia said:
wats the change log
Click to expand...
Click to collapse
Well I am not the right person to tell that, as I am not the developer of CWM recovery. Its Koush.
I have just ported it to our device.
Anyway to tell you few points that I found out:
Major change for our device is support for backup in tar format. (Size reduction of the backup files)
Support for firmware update check and its installation. (If you did ota update and phone restarted in recovery for the same, I guess) - NOT for our device
Support for zip installation from internal SDcard. (Avalable in few devices) - NOT for our device
Few comsetic changes during backup and recovery that you might have noticed.
And few changes in recovery log file.
You can find these out by yourself by looking at sources modifications at: https://github.com/CyanogenMod/android_bootable_recovery/commits/gingerbread/
Initial Test
Ok...set this up on my device:
1. Backup works fine (in tar format now)
2. Restore Works fine
3. Format/Wipes work fine
4. Didnt see much difference from functionality standpoint though...
Will definitely update if something fails or creates a problem
Thanks a lot for this....
cant mount the sdcard from recovery and get it available on windows
adb support ? what it means as i couldnt get the "adb devices" to show the device yet
may be am doing something wrong
i made a back up with this recovery and Tj sirs recovery failed to restore ?? is that normal ?
thanks
zailer said:
cant mount the sdcard from recovery and get it available on windows
adb support ? what it means as i couldnt get the "adb devices" to show the device yet
may be am doing something wrong
i made a back up with this recovery and Tj sirs recovery failed to restore ?? is that normal ?
thanks
Click to expand...
Click to collapse
This recovery's backup is in tar file format for non boot partitions, as its mentioned in few posts before. So the backup created by this re overy can not be used with earlier versions of recovery.
And for adb, is your device detected when it is booted into any ROM. I mean have installed drivers correctly.
For USB mounting, select mount USB storage in mounting menu. And remain in that menu untill you are done with USB usage.
Sent from my CSL-MI410 using XDA App
OK that was one info i might have missed .. about the .tar format! thanks for stressing it again
but about the other two advices .. i have my phone detected by all other roms ..yes ...thats how i could fix its looping at corrupted boot animation yesterday?(mentioned in another post ) so i guess its some other issue .. since its not worked with the combined recovery version too (stock and v5.0.x.x) ..any guess whats happening ??
about mounting and unmounting .. i stayed in the "mounted" state for 10 minutes and still it didnt show up on the pc. but with other clockwork i guess its again urs 0ne with orange colour i get this working so easily .
thanks for immediate response and thanks for these great releases i really like the details shown (each file name its backing up and restoring ) really cool
zailer said:
but about the other two advices .. i have my phone detected by all other roms ..yes ...thats how i could fix its looping at corrupted boot animation yesterday?(mentioned in another post ) so i guess its some other issue .. since its not worked with the combined recovery version too (stock and v5.0.x.x) ..any guess whats happening ??
about mounting and unmounting .. i stayed in the "mounted" state for 10 minutes and still it didnt show up on the pc. but with other clockwork i guess its again urs 0ne with orange colour i get this working so easily .
Click to expand...
Click to collapse
I really dont know the reason behind the problem. Try re-installing any of the latest recovery.
Sent from my CSL-MI410 using XDA App
Released new version of CWM recovery with touch support for menu navigations.
A brief intro:
Napstar said:
Released new version of CWM recovery with touch support for menu navigations.
A brief intro:
Click to expand...
Click to collapse
Its really good.
Thx for update....!!
Sent from my CSL-MI410 using xda premium
Napstar said:
Released new version of CWM recovery with touch support for menu navigations.
A brief intro:
Click to expand...
Click to collapse
hi
very nice and interesting uv been missing for a long time welcome back buddy
ur back with a bang buddy
Really good programming, much easier to use. My only suggestion is to make the bars wider. I have big fingers.
Sergekarol said:
Really good programming, much easier to use. My only suggestion is to make the bars wider. I have big fingers.
Click to expand...
Click to collapse
My changes are developer friendly. What i mean by that is, if you know how to extract and re-pack recovery.img file for our device then you can just replace button.png and button-sel.png to your choice. Graphical menu will adjust itself.
Anyway, i will release a separate version too, so as to make this process more friendly.
Sent from my CSL-MI410 using XDA App
this is really great.. this really solves the problem if one wants / needs to navigate thru CWM recovery in low light or no light conditions. bcoz in recovery mode the soft buttons do not glow. great man Napster!!!
Hi Napstar... Good work! Hows about your dual recovery using recovery menu, stock and this new one.
CacingKalung said:
Hi Napstar... Good work! Hows about your dual recovery using recovery menu, stock and this new one.
Click to expand...
Click to collapse
Recovery menu and Boot Menu are next in line.
But before that I am working on adding this touch support for Samsung Galaxy SL I9003 device that I have.
GreAt done napstar! But how about usb disk in recovery do? and if I install this cwm update there is the way to back to previous version of cwm to flash my old backups?
dtbang721 said:
GreAt done napstar! But how about usb disk in recovery do? and if I install this cwm update there is the way to back to previous version of cwm to flash my old backups?
Click to expand...
Click to collapse
Sorry, I did not follow what you meant by "usb disk in recovery".
Regarding restoring old backups, this recovery supports any backup from last releases. (backward compatibility).
Anyway, just for the sake of convenience I have retained older release in my first post attachments. So anyone can revert back to older release if they want.
dtbang721 said:
GreAt done napstar! But how about usb disk in recovery do? and if I install this cwm update there is the way to back to previous version of cwm to flash my old backups?
Click to expand...
Click to collapse
Just retain / copy (if you have a backup on your computer) clockworkmode folder in your SD card along with the old ROM backups. This cwm will simply take the backup and restore. Worked for me !
hihihi changed the pngs to one i liked bt gesture got disturbed sorry was jst try to mess it up lolz back to ur build
nd thank got it didnt get bricked this time ... i dont think they gonna replace it for this time (actually if it gets bricked it will be 3rd time )
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
Hey Guys,
first off i had this issue once before, but in that case i could restore a cwm backup from sd card and after sometime the problem fixed itself,
this time, i switched to bacon and i wanted to prepare the p880 for my sister to use, i downloaded zaiben, formatted my external sd card and put the rom on it, i rebooted to recovery wiped( i used the clean to install new rom in philz recovery if i remember correctly) everything and flashed the rom and exactly as last time, the flash seems to go way too fast and ofc i cant boot into android. now as i formatted my sd i have no backup to restore to. kdz flashing seems hopeless as well, as none of the tools recognize the phone when i put it in s/w upgrade mode,
for proof: i checked /system with aromafm and found it being empty after flashing a rom, i even tried extracting the rom zip on sd and moving the content from the zip to /system manually but after a recovery reboot, /system was empty again( only empty "bin" folder)
is somebody able to explain me why i have this issue and maybe how to fix it, or upload a clean cwm backup of whatever rom for me to use?
thx
Thanks for the help until now, really.......
In Further investigation i could find out that Roms ARE actually flashing properly, but /system and probably other partitions are not being mounted
At Boot or in recovery(manually mounting works Here) which is why aromafm reports an empty /system, after a manual Mount in either recovery itself of Aroma console i can See /system being filled with Rom files, now i will change the thread title accordingly, and now ASK: can i force /system to be mounted at Boot somehow? Someone pls answer this time
Okay this is ridicoulous.... why am i getting no help AT ALL?, thank you srsly.....
i investigated even further and suspected that something with fstab might be wrong, but fstab file looks fine to me:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 rw
if someone bothers to answer: what do you think?
pls help........
bump
please help
What recovery are you using? Are you sure your partitions aren't formatted to F2FS? (which would explain why the (F2FS-) recovery can mount the partitions but the system cannot as it expects an ext4 formatted partition rather than a F2FS formatted one)
i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions
~MaX~ said:
i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions
Click to expand...
Click to collapse
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?
laufersteppenwolf said:
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?
Click to expand...
Click to collapse
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
{
"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"
}
~MaX~ said:
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
Click to expand...
Click to collapse
hmm, can you please grab me a kmsg? (from when it is stuck)
laufersteppenwolf said:
hmm, can you please grab me a kmsg? (from when it is stuck)
Click to expand...
Click to collapse
could you give me a quick how to on using adb in recovery from pc? i put the phone in sideload mode and tried "adb shell dmesg" but the output just was "error close" and using the command in aromafm terminal gave me an endless stream of log
(Also currently need to charge the phone a bit)
EDIT: NVM kmesg incoming....
okay next question, how can i dump the output into a file and how do i know where it hangs? time in recovery is not correct anymore(i set it once but after reboot it was wrong again, also in kmesg the time again seems to be different)
does that part help? i think it has to do with boot
~MaX~ said:
does that part help? i think it has to do with boot
Click to expand...
Click to collapse
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site
laufersteppenwolf said:
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site
Click to expand...
Click to collapse
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?
~MaX~ said:
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?
Click to expand...
Click to collapse
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..
laufersteppenwolf said:
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..
Click to expand...
Click to collapse
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does
~MaX~ said:
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does
Click to expand...
Click to collapse
1) yeah, I know, easiest way to fix that is to simply pull the battery and then boot into recovery
2) if the bootanimation shows up, it means the kernel as well as the ramdisk have booted properly. So in this case, you should be able to grab a last_kmsg as well as a logcat
hi
today I installed that application " LG-Optimus-4XHD-Recovery-v1.0.apk "
I have selected ClockworkMod Custom Recovery.
It showed that Operation is successful.
than i clicked on "Boot Recovery" to restart my Phone in CloclworkMod Custom Recovery.
since then I am getting only Starting animation. (LG LOGO).
nothing happens.
My battery was full when i performed this procedure
any help please
ARE YOU SEARCHING TO ROOT YOUR REDMI 2 ?
DISCLAIMER:DO THIS ON YOUR OWN. I'M NOT RESPONSIBLE FOR ANYTHING HAPPENS TO YOU AND YOUR DEVICE.PLEASE DONOT MIRROR THE LINKS
CLICK HERE FOR NATIVE ROOT
IF YOU ARE GETTING STOCK RECOVERY EVEN AFTER FLASHIN CWM, SEE THIS POST
STEP 1- FLASHING CWM ON YOUR PHONE
1.At first, you'll need the "adb" and "fastboot" tools. Get them HERE
2.Extract them into a folder, let's name it "Redmi2" (You can give your own name to the folder. That doesn't matter here.)
3.Now get the CWM .img file from HERE
You can use Philz Touch recovery also. Get HERE
4.Rename cwm.img or philz.img you downloaded above and as "recovery.img" and place it in the Redmi2 folder.
Now the folder will look like this-
{
"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"
}
5.Press and hold "shift" button and right click in the blank area of the folder and click on "open command promt window here". The command prompt will open.
6.Now turn off your Redmi2. Wait until it vibrates. After it's vibrated press and hold "Volume down and Power" keys together until it boots into "fastboot mode". Now connect the Redmi2 to your PC/Laptop through USB cable in fastboot mode itself.
7.Get to the command prompt now.
Now type: " fastboot devices " (without these- " " )
Like this-
8.Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command
9.Now enter the next command: " fastboot flash recovery recovery.img "
Like this-
10. Now this ends...
Type the last command: " fastboot reboot "
Like this-
11.Now your phone will reboot with ClockWorkMod(CWM) installed. CHEERS...
STEP 2- ROOTING YOUR PHONE
1. Firstly get the SuperSU.zip from HERE
2. Now copy the downloaded zip to your sdcard (not in any folder just in sdcard)
3. Boot into CWM recovery by turning off the phone and pressing "Volume UP and Power" button together after the phone vibrates.
4. Once CWM main menu is displayed, select "Install from zip" and browse to the zip that you downloaded earlier and select it.
5. Install the zip. If you get any warning, ignore and proceed.
6. After the installation is complete, reboot your device. (I think you can do that)
7. VOILA..!!! YOU ROOTED YOUR REDMI2
PLEASE HIT THANKS
JOIN OUR FACEBOOK GROUP HERE
CREDITS:
1. I don't claim any credit for "adb and fastboot tools" and the "recovery.img" and "SuperSu.zip"
2. Thanks to @subhrajiNath on Miui english forums who wrote the original guides.
Thread link is here and here
I cannot connect to device using adb on ubuntu.
Any Idea ?
I have opened a thread about this issue here
postadelmaga said:
I cannot connect to device using adb on ubuntu.
Any Idea ?
I have opened a thread about this issue here
Click to expand...
Click to collapse
I'm really sorry man..I've never used ubuntu But I wish to...
Join the FB group and ask there...Maybe it can be helpfull
? not flashing ?
noobpremium said:
I'm really sorry man..I've never used ubuntu But I wish to...
Join the FB group and ask there...Maybe it can be helpfull
Click to expand...
Click to collapse
Ok my fault, It looks I miss the notification MIUI that ask me to allow my pc to dev mode...
Now I have another issue:
After I flash the recovery with flashboot I reboot into recovery but I still have the default one ... not CWM any idea what could be wrong ?
( I have already did this procedure on another phone, same issue but after doing it a couple of time something make the difference )
postadelmaga said:
Ok my fault, It looks I miss the notification MIUI that ask me to allow my pc to dev mode...
Now I have another issue:
After I flash the recovery with flashboot I reboot into recovery but I still have the default one ... not CWM any idea what could be wrong ?
( I have already did this procedure on another phone, same issue but after doing it a couple of time something make the difference )
Click to expand...
Click to collapse
get "Flashify" app from playstore and first take backup of stock recovery and then flash the cwm with it. Thats it..
Actually I didn't knew this method before i made this guide..
Anyway, fastboot gives us a different feel, doesn't it? :v
wait I don't know flashify but it looks it needs root to flash the recovery ... but I think I need cwm to root ... so I think this is not gonna work ...
Ok got it, this may be useful to anybody face the issue with recovery:
I discovered you can workaround the issue in this way:
Temporary boot into CWM:
HTML:
fastboot boot recovery.img
Root the device using CWM
Flash CWM using flashify
[ CWM when you log out ask you for root so maybe it is not necessary to use the zip file ( but I'm not very expert so maybe I'm wrong)]
You can install GAPPS with CWM `gapps-kk-20140606-signed .zip` but be careful, whenever you update MIUI you will look all software installed using CWM. ( superSu and GAPPS for example )
thanks
thanks!
eienkisu said:
thanks!
Click to expand...
Click to collapse
Pleasure
Okay bro :good:
I'll update the OP
I confirm #postadelmaga the CWM recovery does not stay, the only way to do access it is the fastboot boot recovery.img Here's how I succeeded with two phones now.
power on, start wifi, do Miui updates
install ADB or the files above on PC
reboot to fastboot with voldown+pwr
now comes fastboot boot recovery.img
in CWM, sideload SuperSu and Gapps
connect you preferred VPN (if in China)
install and update all Google apps needed
delete most Chinese apps
hey i m unable to flash recovery plzz help
Device version 2014818
Sent from my 2014818
Hi buddy could you plz port touchwiz from galaxy prime?
The simpler solution is to use the xiaomi update tool and flash a developer rom that has builtin root.
http://xiaomi.eu/community/threads/5-4-10.27429/
howto & root from permissions menu:
https://watchpage.wordpress.com/201...redmi-note-4g-developers-roms-version-miui-6/
But to have the cwm running on the phone is always a safe bet for some recovery actions.
not working.
I tried this method. its stuck with flashing the recovery image. always showing flashing the recovery image.... that's all.
godwintgn said:
I tried this method. its stuck with flashing the recovery image. always showing flashing the recovery image.... that's all.
Click to expand...
Click to collapse
Are you on win7? I got this same issue on my win7... try on win8 it works flawlessly
Please hit thanks if done
Ya bro I am using Windows 7. I don't have Windows 8. Thanks for the info.
Shrihari007 said:
Hi buddy could you plz port touchwiz from galaxy prime?
Click to expand...
Click to collapse
TW sucks man.. why do you want it :/ anyways I'll try
leuk_he said:
The simpler solution is to use the xiaomi update tool and flash a developer rom that has builtin root.
http://xiaomi.eu/community/threads/5-4-10.27429/
howto & root from permissions menu:
https://watchpage.wordpress.com/201...redmi-note-4g-developers-roms-version-miui-6/
But to have the cwm running on the phone is always a safe bet for some recovery actions.
Click to expand...
Click to collapse
Thanks to you bro.. I'll update the OP for those who are facing some issues with my guide's precedure..
OP Updated
I've updated the OP with the other guide's link.. please check it out if you're having some issues with this one
godwintgn said:
Ya bro I am using Windows 7. I don't have Windows 8. Thanks for the info.
Click to expand...
Click to collapse
Try on some friend's PC or something