Related
Hello,
Can someone explain what do Open Recovery ?
Thank you
It install a temporaly recovery system on your XT720. You can perform backups and restore with nandroid on it
I have a problem, when I reboot on open recovery (volume up key) I just have a yellow triangle and I cannot select anything. Do you know how to use open recovery ?
Zachary57 said:
I have a problem, when I reboot on open recovery (volume up key) I just have a yellow triangle and I cannot select anything. Do you know how to use open recovery ?
Click to expand...
Click to collapse
it is normal system recovery screen. press volume up + camera key and you'll get the menu.
to use open recovery, you need to boot normally, then open the System Recovery app and click Recovery Reboot. then it will reboot to OpenRecovery menu.
spiderx_mm said:
it is normal system recovery screen. press volume up + camera key and you'll get the menu.
Click to expand...
Click to collapse
Thank you it's work.
The best reason to do it is to allow you to access the phone via ADB shell in case something gets mucked up in the installation process (e.g. modification of mot_boot_mode by various applications to SD apps).
Having that actually allowed me to make more experimentations on the startup scripts with apps2sd. I have made an optimized version of the app2sd startups so that mot_boot_mode is kept as is, I am using /system/sd/install-recovery.sh myself.
Hi all.
A few days ago I entered the Xoom forum asking about how to modify an "unaltered" Spanish/European Xoom (Wifi Only, MZ604) running stock Android Honeycomb (3.2) and flash a custom ROM with Android 4.1.1 (JellyBean), so that I don't have to wait Motorola to release the updates (still in Honeycomb in Europe, while in US they're enjoying JB), and to enjoy the extras that custom ROMs offer (root, overclocking, etc).
Xda users "wesamothman" and "Cubanluke88" answered quickly to my question and this allowed me to unlock my Xoom bootloader, install TWRP Recovery and flash EOS3 ROM (JellyBean for Xoom from TEAM EOS). The results are awesome; the change from Honeycomb to Jellybean, plus the totally stable overclocking at 1.2 and even 1.4 Ghz is worth the fact that you void the Xoom warranty by doing this procedure. It's like having a brand new tablet.
As I found some problems/mistakes in the procedure I was given, I've created a new "Guide for Noobs" (based on wesamothman's) so that anybody can reproduce the same steps and convert an European Xoom (Wifi Model, MZ604) into a modern EOS3-powered Xoom.
NOTE: I initially wrote this tutorial using the EOS-RECOVERY-6.IMG as the CWM Recovery software to install in the Recovery Partition. The recommended recovery software now is TWRP so I've updated the tutorial replacing the download links and filename.img to flash. The procedure remains the same, although I really tested and executed it with eos-recovery-6, not with TWRP. Anyway, it is supposed to be flashed and work the same way than I initially described it.
NOTE THAT THIS PROCEDURE IS FOR EOS3 - (EOS NIGHTLY <= v155).
EOS4 (nightly >= v156) requires a slightly different procedure!!!
Please, remember that by unlocking the bootloader (and flashing non official software) you're voiding the device warranty and that I'm not responsible of any damage that your device can suffer. I'm just explaining how I did the unlocking+flashing to convert my SLOW XOOM in a fully working JellyBean system. Remember also that this procedure is for WIFI ONLY Xooms. 3g xooms need a different rom/procedure.
So, sumarizing, that's what we are going to do:
a.- Unlock the "bootloader" of the Motorola Xoom so that we can "install" custom software in both the "recovery" and the "data" partitions. Please notice that by unlocking the bootloader you void the device warranty.
b.- Flash TWRP software into the recovery partition, (I was flashing EOS-Recovery-v6 software initially but now is deprecated and TWRP must be used) so that we can launch this software pressing a combination of keys during power-on. This software will allow us to make full backup/restore of the device memory, and to install any ROM (EOS2, EOS3, cyanogenmod, EDGE, etc) in the system. Thanks to this recovery we are safe against problems in the O.S. (even if we break it), because we can always recover from backup or flash a new ROM (including the "stock" ROM, I mean, the ROM shipped oficially with the device) and solve the situation.
c.- Once recovery is installed, do a NANDROID backup of the NAND of our device, to have a copy of the "stock" system.
d.- From Recovery, flash the desired ROM (EOS3 in my case) and the Google Apps applications (they can't be included inside the ROM for legal reasons, so they are flashed separately) to the "data" particion.
e.- Restart and enjoy our new system (you can also made another NANDROID backup to save this "working point" for the future).
Steps a). and b). need a working computer with Linux, Windows or Mac. After doing b).- you can do everything from the Xoom itself and you don't need the computer anymore. After doing b)., you'll be able to download ROM images directly under your Xoom in the uSD card and reflash any new ROM directly rebooting the tablet into recovery-mode.
Steps a) and b) can be done from Linux, Windows and Mac. Although I have Linux in my laptop, I found that almost all the tutorials in Internet explain the procedure under Windows so I installed temporary a Windows system to do the "PC dependant" steps, because I didn't want to experiment with the "risky" actions in both steps.
So, let's start with the "PC dependant" actions, which includes steps a). and b).
I'll try to update the thread with screenshots in the future, as I didn't take photos/screenshots of the procedure, I'll check images.google.com to find something that fits the text, and add the later to the tutorial if they are really needed.
PART 1 .- HOW TO INSTALL TWRP RECOVERY:
Here we are going to unlock our Xoom and install a custom recovery software into the recovery partition. The recovery software is launched when you start your Xoom in recovery mode, and this is achieved by pushing Power, VolUP and VolDown key combinations when you power-on the tablet (we'll see how later).
So we'll replace the original "recovery" software by a custom one that allows us to flash NON OFFICIAL software to the data partition.
To do that, first we have to download all the required software in the Xoom enternal uSD card and prepare our PC system to recognize and work with the Xoom. We have to download:
Get the Motorola USB drivers for your system: http://developer.motorola.com/docstools/USB_Drivers/ . This step is only needed under Windows, so that the Windows System recognizes the Xoom and the Android SDK binaries (adb and fastboot) can send data to the tablet. Check that you're downloading the right drivers (32 or 64 bits) for your 32 or 64 bits System, and install them. If the Android SDK in your Linux system can recognize the Xoom, you're ready to use Linux also to do the following steps.
Download and Install in your PC the lastest JavaSE JDK from Oracle's website: http://www.oracle.com/technetwork/java/javase/downloads/index.html.
Download and install the Android SDK for your system: http://developer.android.com/sdk/index.html .
Download the EOS v155 ROM and GoogleAPPS for that version. My final choose was EOS3 ROM Wingray (Jellybean for Xoom), and installed v155 from the nightly compilations (which is the latest nightly in Android 4.1, being v156+ Android 4.2). "Nightly" means that as the software is still not "final version" (it's still in development) a new version is released almost everyday, correcting bugs or adding new features. I personally didn't found any bug in v155 but you can check the EOS3 thread in XDA to check that the latest version has no bugs reported by people in that thread.
ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ (as of date September-2012 - I recommend v141 )
GAPPS: Latest: http://teameos.org/gapps/wingray (I used http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120802-eos-signed.zip for v155).
EOS3 THREAD: http://forum.xda-developers.com/showthread.php?t=1764751
And the most important, download TWRP the "recovery software" that will allow you to work without the need of the PC (I was using Team Eos Recovery 6 initially, but now is deprecated and TWRP must be used):
Team Win Recovery Project 2.x, (TWRP): http://forum.xda-developers.com/showthread.php?t=1782235
You should download the IMG file (example: R.A.H.v3_TWRPv2.5.0.img). Check that the size of the downloaded file matches the size that is shown in the above link. This is the most important file because it will allow to install the recovery system and it's CRITICAL that the file is not corrupted..
Steps:
a.- Install in your PC the Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
This will download and install the packages needed so that we can access the Xoom from the PC for "flashing" data purposes; mainly "adb" and "fastboot". Adb allows us to work with the xoom started in the Android System, and fastboot allows us to work with the xoom started in fastboot mode, which is the mode we'll use to "flash" the recovery software.
b.- Enable USB debugging in the XOOM (in settings, development), so that we can use adb with the tablet.
c.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
d.- Plug the Xoom to your PC.
e.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices". You should see that the system identifies your Xoom with a long numbers+letters string. If you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device, so that the system can bind the right USB drivers we installed to that concrete device.
After a While, Windows will fix it and re-executing "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
Now, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup. Fastboot mode is a special bootmode in the xoom that allows the PC to send data to the Xoom and "write" to Recovery and Data partitions. You can also enter that mode starting the Xoom with "Power+Volume Up" pressed simultaneously.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
{
"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"
}
(Photo: fastboot mode, taken from google images)
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because Windows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot".
Issue the following command to unlock the Xoom (you'll void the warranty). If you don't unlock the xoom, data and recovery partitions will be "read only" and you can't send the "new software" to them.
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option. The device will ask you twice if you are sure that you want to unlock the device and void the warranty, and then it will make a "factory reset" of the O.S. .
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc. Enable again "USB debugging" and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the recovery file (the name may vary, with something like R.A.H.v3_TWRPv2.5.0.img) to the android-sdk/platform-tools/ folder with name "recovery.img" and execute:
Code:
fastboot flash recovery recovery.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery recovery.img
sending 'recovery' (XXXXX KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
Now disconnect the USB cable and enter recovery mode with:
- When the Motorola logo appears, tap Volume Down (not press, tap) repeteadly until "Android Recovery" is displayed in the screen.
- In this moment, pressing Volume Up will send you to Recovery Mode.
- If you press by mistake again Volume Down, you'll enter DRS mode. You can leave it with VolUP+VolDown+Power and try again (Xoom is powered off).
And you'll start the TWRP Recovery recovery system. If you see the standard Android recovery system instead of TWRP recovery, you can repeat the above "fastboot flash recovery recovery.img". You don't have to unlock the bootloader again, just flash the recovery software and reboot again in recovery mode with "fastboot reboot" and "adb reboot recovery".
(Photo: my Xoom in EOS6 recovery mode, TWRP is different, with better controls and more features )
You can start recovery mode also manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE TWRP RECOVERY
How to enter in recovery mode:
A.- Manually:
- Turn Xoom off.
- Press Power to turn Xoom on.
- When the Motorola logo appears, tap Volume Down (not press, tap) repeteadly until "Android Recovery" is displayed in the screen.
- In this moment, pressing Volume Up will send you to Recovery Mode.
- If you press by mistake again Volume Down, you'll enter DRS mode. You can leave it with VolUP+VolDown+Power and try again (Xoom is powered off).
b.- From "adb" in a PC system with Android running on the tablet connected to that PC:
Executing "adb reboot recovery"
c.- With a custom ROM, selecting "reboot" will ask you if you want a normal reboot or a recovery-reboot.
How to use recovery mode:
Use the Volume Up and Volume Down keys to move between options and Power button to select an Option:
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
Available options for a basic CWM / recovery are:
Reboot system now -> exit Recovery mode.
install zip from sdcard -> allows to install ZIPs to data partitions such as ROMs.
wipe data/factory reset -> delete all the contents in the data partition (needed before flashing a ROM)
wipe cache partition -> delete cache partition.
backup and restore -> allows doing "nandroid" backups and restore of our system (FULL MEMORY BACKUPS).
mounts and storage -> allows to mount aditional media to save/read data.
advanced -> extra options.
(Photo: Nandroid backup)
NOTE: TWRP is newer than the OLD EOS-recovery-6, the above capture and options may differ.
PART 3 .- HOW TO INSTALL EOS3 ROM:
Now we've installed recovery, so we don't need the PC anymore. We can enter in recovery mode at any moment and do backup/restores, flash new roms, flash updates, etc.
To install EOS3 ROM (or any other "full install" -not update- ROM, do):
Start the Xoom in recovery mode.
Backup/restore -> backup the current system to our external SD.
Wipe data/factory reset -> remove partition contents
Wipe cache -> delete the cache
Advanced -> Wipe Dalvik Cache
Advanced -> Wipe Battery Stats
Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
Reboot
Install gmail, youtube, etc from Market (not included anymore in gapps).
Enjoy your new rom!
PART 4 .- HOW TO UPDATE EOS3 ROM or install a new different ROM:
Start the Xoom in recovery mode.
Backup/restore -> backup the current system to our external SD.
Wipe data/factory reset -> remove partition contents
Wipe cache -> delete the cache
Advanced -> Wipe Dalvik Cache
Advanced -> Wipe Battery Stats
Install ZIP from SDCARD -> /sources/ -> the new rom .zip file.
Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
Reboot
Enjoy your new rom!
I hope this can help people to unlock their xooms.
Thanks to "wesamothman" and "Cubanluke88" for the initial support given and specially to EOS Team and the people that created ClockWorkMod for sharing their time, work and knowledge with us. They've converted my "slow xoom" in a very powerfull and fully functional tablet.
Couldn't expect less from you. Super great guide...
Sent from my MZ601 using Tapatalk 2
Post reserved for updates in case the initial post gets too large...
I wish all new Android users would do the level of research the OP did prior to making his initial question thread. We guided you a bit but if I remember right, your first post showed quite well that you had done your homework. If more people committed themselves to understanding what they're doing prior to doing it, I'd imagine there'd be a lot less "bricks" in the android world. Great work dude and nice job entering the forums with a bang.
Sent from my Xoom using Tapatalk 2
Thanks for your words...
In this thread I've tried not only to give a procedure (the forums and lots of websites are full of procedures) but also explain the concepts themselves (oem unlock, adb, fastboot, recovery mode, gapps, etc).
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime".
Thanks.
--
Sent from my Xoom with EOS3 ROM using Tapatalk 2
Updated with some pictures
Updated with links to v141...
eos 6 recovery.img not available
the recovery image file is not available in the link..could you update the link. Thank You !
Great tutorial
kakrikakri said:
the recovery image file is not available in the link..could you update the link. Thank You !
Great tutorial
Click to expand...
Click to collapse
Hi.
According to this URL, EOS6 RECOVERY.IMG has been deprecated:
http://forum.xda-developers.com/showthread.php?t=1604014
Now you can use Team Win Recovery Project 2.2, (TWRP):
http://forum.xda-developers.com/showthread.php?t=1782235
Flashing is almost similar to EOS6 recovery method described above, just check the last link.
NoP_Compiler said:
Hi.
According to this URL, EOS6 RECOVERY.IMG has been deprecated:
http://forum.xda-developers.com/showthread.php?t=1604014
Now you can use Team Win Recovery Project 2.2, (TWRP):
http://forum.xda-developers.com/showthread.php?t=1782235
Flashing is almost similar to EOS6 recovery method described above, just check the last link.
Click to expand...
Click to collapse
wow that was a quick reply.. THANKS (Y)
kakrikakri said:
wow that was a quick reply.. THANKS (Y)
Click to expand...
Click to collapse
Anyway, I have the eos-recovery-r6.img.zip file in my desktop, I can send you via email if you want to use it instead of TWRP (but you should not, as Team Eos recommends their new recovery system).
I'm going myself to update to TWRP this evening (they have a .zip file that you can flash from an existing recovery like my current "EOS6 recovery").
Same method for stock ics?
Sorry I am a bit paranoid..but will this same unlocking bootloader and flashing recovery method work for stock ics on my xoom?
Thanks !
Help !!! In a lot of trouble
I flashed the twrp recovery and then it rebooted..everything was perfect till that point
then i rebooted into recovery..and when i selected to install zip from usb drive..it said mount to sdcard failed (at this point the roms were downloaded in my internal storage) and it does not detect any zip files.
I tried putting the zip files on a proper micro sdcard and then rebooted into recovery..but still no luck.. it just says it failed to mount sdcard.
Special note:- and btw.. when i reboot into recovery and after pressing the vol up button there is a droid icon on my screen, but no 'recovery' menu shows up.. then i pressed volup+power button, this action popped up the list of menus of the recovery screen... (do u think this might be a problem?)
please help me i am panicking here..is there anyway i can flash a different recovery..like the eos recovery or the cmw?
HELP !!!!
kakrikakri said:
I flashed the twrp recovery and then it rebooted..everything was perfect till that point
then i rebooted into recovery..and when i selected to install zip from usb drive..it said mount to sdcard failed (at this point the roms were downloaded in my internal storage) and it does not detect any zip files.
I tried putting the zip files on a proper micro sdcard and then rebooted into recovery..but still no luck.. it just says it failed to mount sdcard.
Special note:- and btw.. when i reboot into recovery and after pressing the vol up button there is a droid icon on my screen, but no 'recovery' menu shows up.. then i pressed volup+power button, this action popped up the list of menus of the recovery screen... (do u think this might be a problem?)
please help me i am panicking here..is there anyway i can flash a different recovery..like the eos recovery or the cmw?
HELP !!!!
Click to expand...
Click to collapse
Twrp recovery doesnt mount external sdcard by default, you need to mount it first thru recovery. Just go to mounts and check the box to mount external sdcard
wesamothman said:
Twrp recovery doesnt mount external sdcard by default, you need to mount it first thru recovery. Just go to mounts and check the box to mount external sdcard
Click to expand...
Click to collapse
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?
kakrikakri said:
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?
Click to expand...
Click to collapse
First time ROM flashing is longer than normal booting, like 5 min ,
If you got stuck in boot loop, reboot into recovery using the power and sound keys combination and clear cache and dalvik and reboot again
kakrikakri said:
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?
Click to expand...
Click to collapse
Did you finally succeded "booting" EOS3?
NoP_Compiler said:
Did you finally succeded "booting" EOS3?
Click to expand...
Click to collapse
Yes it did and it works perfectly
Thank you NoP_Compiler and wesamothman
Sent from my Xoom using xda app-developers app
Just to say thanks for 1 of the best tutorials I have ever found,from stock ICS to eos 3 wingray nightly 151 in less than 20 mins. Only prob I had was android SDK wouldn't find x64 java on win had to install 32bit version on top but only hiccup
dead android in step 2
Hi,
Thanks for the great tutorial.
I got thru Step 1, using the image "openrecovery-twrp-2.3.1.0-wingray.img"
In Step 2, when I enter in recovery mode, I get a screen with a "dead droid" image.
Any idea about what I might be missing?
thanks!
Salutations folks,
Just posting some preview screenshots of some work I've been doing on the Alpha2.
CyanogenMod9 (ICS) and ClockWorkMod Recovery 6.0.1.1
It's still a work in progress as I fix various issues and bugs I've come across, but it's
slowly but surely getting to the point of being stable and usable for daily use. When
it gets stable enough, I will post the rom and install files for public consumption/testing.
Running:
CM9 ICS 4.0.4
3.0.36 custom kernel w/modules specific to alpha2 and feature testing usb gadgets (bluetooth, etc.)
NOTE: currently working on upgrading to 3.0.38/3.0.39 kernel
CWMR 6.0.1.1 (koush's latest) w/fully working menu options, backup/restore, key use for menus
NOTE: currently working on implementing touch menu control
Tested/Working:
Camera (stills, video)
Microphone
Rotation sensor
Wi-fi
Hardware keys (VOL+, VOL-, POWER)
Video (software accelerated, 720p)
Touchscreen
Internal/External sdcards
USB Storage mounting
ADB access/control
Bugfixing:
Camera Zoom controls
Video (hardware acceleration possible on cedarx?)
Touchscreen capacitive buttons (MENU, BACK, HOME)
USB Storage Mounting in CWM6 (adb works fine tho)
Screenshots (click to zoom):
custom compiled CWMR 6.0.1.1 (latest) with custom background, menu colour and clockwork icon
CM9 info menu - little fuzzy, sorry about that
in-UI screenshot of CM9 info menu
CLOCKWORKMOD RECOVERY
(Updated to 6.0.1.2), Install scripts updated to Version 1.1
As mentioned in another post, I'm releasing the CWM install for public consumption. Please be aware that due to the issues with my SSA2, that
I will probably not be updating this much. This CWM install is mainly for nandroids, etc. Support will be LIMITED, but this recovery mode should
work fine as is. I will NOT be taking requests for features or my CM9/CM10 roms until I can get my SSA2 working 100% again or another one
falls in my lap. (sorry). BUT, github access to the kernel, recovery and CM9 is publicly available. Get coding, if you want it.
The ClockworkMod recovery install files are located below: (hosted via Dropbox)
7zip (.7z) of ClockworkMod Recovery Install files - 6.6MB
MD5: 5cd49a048ce941d478a84343b228ec18
Ver1.1 MD5: 0e225bc31c5fc523a210753744b19834
7zip executable extracter (.exe) of ClockworkMod Recovery Install files - 6.76MB
MD5: ab74d12fe6a48e877c52cad8cad606d8
Ver1.1 MD5: aa9e75ef70d39aa18cf916b3455f657d
README/Install Instructions:
ClockWorkMod-based Recovery by [email protected]
[ DISCLAIMER ] --------------------------------------------------------------------
First and foremost, please note that by using or installing these files that
you will not hold me ([email protected]) responsible if you brick/ruin
your device in any way. Although every attempt has been made to prevent
this from happening, there is always a chance something can go wrong.
(Luckily, if something does go wrong Livesuite reflashing can usually
fix it, although you will most likely lose any data/settings stored on your
device).
[ CHANGELOG ]--------------------------------------------------------------------
1.0 - 11/03/2012 - Initial CWM install release
1.1 - 11/04/2012 - Add Version A/B script.bins since there are gyro differences
- Consolidate batch install files/add a little choice logic too
- Menu system for install, backups, reboot
[ INTRODUCTION ]-----------------------------------------------------------------
These are simple install scripts and files to install ClockworkMod Recovery
into your SSA2 (Skytex Skypad Alpha2). If you don't know what CWM is for,
please do NOT proceed; you don't need it then (except for maybe nandroid
backups.. but seriously.. if you don't know what it's for. STOP)
This recovery requires the following things:
1. You have USB drivers properly installed for accessing your SSA2
2. You have already upgraded to Skytex's ICS (4.0) via Livesuite
Upgrading your SSA2 to Skytex's ICS will cover both #1 and #2.
If you have not already upgraded, you MUST do so now or the recovery
install will FAIL and/or screw with your SSA2 settings. If you have not
already done so, go to: http://goo.gl/WqZTi
(that's just a shortened link.. if you don't trust it.. go to skytex's site
yourself and go to the firmware download area for the SSA2
and install the appropriate 4.0 firmware/livesuite for your device)
PLEASE NOTE: Upgrading your SSA2 to ICS is beyond the scope of this
document and something YOU need to take care. Have fun!
IF YOU DO NOT HAVE SKYTEX ICS INSTALLED, STOP! YOU CANNOT USE THIS!
Rule of Thumb: Backup your settings/files using TitaniumBackup or some
other app before starting big installs like this!
[ INSTRUCTIONS ]---------------------------------------------------------------
Firstly, settle on WHERE you want to install everything. You have a choice of
the internal SDcard or the external (removable) SDcard. Please be aware that
if you install to the internal SDcard, there's a chance you might have to
reinstall everything if you wipe/reflash your device as the internal SDcard is
usually wiped too. The external SDcard is usually left untouched. I'd
recommend the external SDcard if you have a removable card installed.
Based on that choice, run the following:
Note: The install process is fairly documented and verbose, please note
any errors that may arise if something goes wrong.
1. Run the "INSTALL-RECOVERY.bat" batch script
a. Select the appropriate menu options and submenu options.
That's it!
HOW TO ACCESS CWM RECOVERY
-------------------------------------
Please note that ADB REBOOT RECOVERY command will NOT work with
Skytex's ICS (sorry).. it should work fine with AOSP, AOKP, CM9 and CM10 tho.
From ADB (your PC):
With your SSA2 on, Open up a command prompt, if you don't have adb installed globally,
adb has been provided with the install scripts, just go to that directory and run:
adb shell sh /system/bin/reboot-recovery.sh
From a Terminal (your SSA2):
With your SSA2 on, Open up a command prompt (must be in root, su):
sh /system/bin/reboot-recovery.sh
Hardware Keys access (if installed via install scripts):
With your SSA2 OFF (and recommended unconnected to power or usb, as being in charge
mode sometimes disrupts the recovery mode boot process when using the hardware keys.
Otherwise.. if you are in charge mode (shows big battery icon in middle of screen), just
hold down the POWER button until it goes off/away)
1. Hold down the VOL UP key for 5 seconds
2. While holding the VOL UP key, hold down the POWER button for 5 seconds.
3. While still holding the VOL UP key, release the POWER button. Keep holding the VOL UP
key for 5 more seconds.
4. Release the VOL UP key.
Your SSA2 should already be or should start booting into recovery mode shortly thereafter.
If you SSA2 boots back into ICS, it did not succeed (duh), try again.
[ FEATURES ]---------------------------------------------------------------
Current version: 6.0.1.2
- Menu traversal using VOL UP and VOL DOWN, POWER button to select
- install rom/update zip files
- data wipe/factory reset
- cache wipe
- basic/advanced nandroid backup/restore (to internal or external sd [default])
- partition mount/access/format
- usb mount access via CWM
- dalvik cache wipe
- battery stats wipe
- key testing
- permission fix
[ CONTENTS ]---------------------------------------------------------------
adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll - Easy adb access files
install-recovery-ext/int.sh - android shell script for recovery load
INSTALL-RECOVERY.bat - windows batch script for recovery install
README.txt - this file (duh)
reboot-recovery.sh - android system script to reboot into recovery mode
recovery.img - the actual recovery image
versa/versb-ics-script.bin - uboot settings for bootloader to enable recovery mode access keys
Click to expand...
Click to collapse
Looking good, anyway we can get involved?
Yes... I have an Alpha2 sitting right here just dying for some CM9 goodness...
rosehipzero said:
Looking good, anyway we can get involved?
Click to expand...
Click to collapse
Anyone still interested in doing some dev work on this. I bought two of them last night.
i would love to collaborate with someone on this.
Me me me me!!!
PM sent and the alpha2 is out and on the charger....
Sent from my SAMSUNG-SGH-I717 using xda premium
Sorry for the lack of updates on this one folks.
I ran into an issue with my alpha2 where I somehow flushed the ft5x (touchscreen) EEPROM and was not able to to get a proper firmware flashed in there to get it working 100% again. Tried contacting Skytex and Focaltech with no luck. (even disassembled the alpha2 to get full model info on the chips in there.. have lots of pics if anyone is interested in seeing the insides of the alpha2). Finally got touchscreen back using a firmware designed for another model of the touchscreen controller in the alpha2, but having issue with needing to calibrate it properly since all touches are showing up 50 degrees off. Focaltech and their docs don't have any info on calibration so I'm kinda stuck for now til I get a chance to hack through the ft5x kernel drivers. Since I'm kneedeep in college studies and exams, I haven't had time. Compounded with the fact that I also have an Acer Iconia Tab a500 now, development on the alpha2 will probably grind to a slow drip.
In the meantime, I've updated all my github repo's (http://github.com/thesawolf) with the device setup for cm9, specific cm9 build stuff as well as working kernel. So if someone is willing, you can "easily" work off of that. I'm hesitant to release the cm9 rom I put together as it is unfinished and in a very functional, but still raw form (need lots of framework tweaks and some more build.prop tweaks) but the cwm recovery works fine and fully functional and a good place to start working from (and if anything for the nandroid backups). I can put that up on dropbox later if anyone interested. Please be aware that there are LOTS of good guides and writeups for compiling your own cm9 roms. Please don't ask me to tell you how. Search and Google is your friend.
Anyways, good luck folks. Hopefully I'll have some better news for everyone once I have more time to goof around on my alpha2 (when I'm not working on my a500 too)
CLOCKWORKMOD RECOVERY
(Updated to 6.0.1.2)
As mentioned in another post, I'm releasing the CWM install for public consumption. Please be aware that due to the issues with my SSA2, that
I will probably not be updating this much. This CWM install is mainly for nandroids, etc. Support will be LIMITED, but this recovery mode should
work fine as is. I will NOT be taking requests for features or my CM9/CM10 roms until I can get my SSA2 working 100% again or another one
falls in my lap. (sorry). BUT, github access to the kernel, recovery and CM9 is publicly available. Get coding, if you want it.
The ClockworkMod recovery install files are located below: (hosted via Dropbox)
7zip (.7z) of ClockworkMod Recovery Install files - 6.6MB
MD5: 5cd49a048ce941d478a84343b228ec18
7zip executable extracter (.exe) of ClockworkMod Recovery Install files - 6.76MB
MD5: ab74d12fe6a48e877c52cad8cad606d8
README/Install Instructions:
ClockWorkMod-based Recovery by [email protected]
[ DISCLAIMER ] --------------------------------------------------------------------
First and foremost, please note that by using or installing these files that
you will not hold me ([email protected]) responsible if you brick/ruin
your device in any way. Although every attempt has been made to prevent
this from happening, there is always a chance something can go wrong.
(Luckily, if something does go wrong Livesuite reflashing can usually
fix it, although you will most likely lose any data/settings stored on your
device).
[ INTRODUCTION ]-----------------------------------------------------------------
These are simple install scripts and files to install ClockworkMod Recovery
into your SSA2 (Skytex Skypad Alpha2). If you don't know what CWM is for,
please do NOT proceed; you don't need it then (except for maybe nandroid
backups.. but seriously.. if you don't know what it's for. STOP)
This recovery requires the following things:
1. You have USB drivers properly installed for accessing your SSA2
2. You have already upgraded to Skytex's ICS (4.0) via Livesuite
Upgrading your SSA2 to Skytex's ICS will cover both #1 and #2.
If you have not already upgraded, you MUST do so now or the recovery
install will FAIL and/or screw with your SSA2 settings. If you have not
already done so, go to: http://goo.gl/WqZTi
(that's just a shortened link.. if you don't trust it.. go to skytex's site
yourself and go to the firmware download area for the SSA2
and install the appropriate 4.0 firmware/livesuite for your device)
PLEASE NOTE: Upgrading your SSA2 to ICS is beyond the scope of this
document and something YOU need to take care. Have fun!
Rule of Thumb: Backup your settings/files using TitaniumBackup or some
other app before starting big installs like this!
[ INSTRUCTIONS ]---------------------------------------------------------------
Firstly, settle on WHERE you want to install everything. You have a choice of
the internal SDcard or the external (removable) SDcard. Please be aware that
if you install to the internal SDcard, there's a chance you might have to
reinstall everything if you wipe/reflash your device as the internal SDcard is
usually wiped too. The external SDcard is usually left untouched. I'd
recommend the external SDcard if you have a removable card installed.
Based on that choice, run the following:
If you chose Internal SDcard, run: INSTALL-RECOVERY-INTSD.bat
If you chose External SDcard, run: INSTALL-RECOVERY-EXTSD.bat
1. Run your preferred installation batch script
Note: The install process is fairly documented and verbose, please not
any errors that may arise if something goes wrong.
That's it!
Please note that ADB REBOOT RECOVERY will NOT work with Skytex's ICS
(sorry).. it should work fine with AOSP, AOKP, CM9 and CM10 tho.
HOW TO ACCESS CWM RECOVERY
-------------------------------------
From ADB (your PC):
With your SSA2 on, Open up a command prompt, if you don't have adb installed globally,
adb has been provided with the install scripts, just go to that directory and run:
./adb shell sh /system/bin/reboot-recovery.sh
From a Terminal (your SSA2):
With your SSA2 on, Open up a command prompt (must be in root, su):
sh /system/bin/reboot-recovery.sh
Hardware Keys access:
With your SSA2 OFF (and recommended unconnected to power or usb, as being in charge
mode sometimes disrupts the recovery mode boot process when using the hardware keys.
Otherwise.. if you are in charge mode (shows big battery icon in middle of screen), just
hold down the POWER button until it goes off/away)
1. Hold down the VOL UP key for 5 seconds
2. While holding the VOL UP key, hold down the POWER button for 5 seconds.
3. While still holding the VOL UP key, release the POWER button. Keep holding the VOL UP
key for 5 more seconds.
4. Release the VOL UP key.
Your SSA2 should already be or should start booting into recovery mode shortly thereafter.
If you SSA2 boots back into ICS, it did not succeed (duh), try again.
[ FEATURES ]---------------------------------------------------------------
Current version: 6.0.1.2
- Menu traversal using VOL UP and VOL DOWN, POWER button to select
- install rom/update zip files
- data wipe/factory reset
- cache wipe
- basic/advanced nandroid backup/restore (to internal or external sd [default])
- partition mount/access/format
- usb mount access via CWM
- dalvik cache wipe
- battery stats wipe
- key testing
- permission fix
[ CONTENTS ]---------------------------------------------------------------
adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll - Easy adb access files
install-recovery-ext/int.sh - android shell script for recovery load
INSTALL-RECOVERY-EXTSD/INTSD.bat - windows batch script for recovery install
README.txt - this file (duh)
reboot-recovery.sh - android system script to reboot into recovery mode
recovery.img - the actual recovery image
script.bin - uboot script settings for bootloader to enable recovery mode access keys
Click to expand...
Click to collapse
Install scripts and files have been updated to acommodate the fact that the SSA2's have a Version A and Version B difference that was resulting in an issue with gyroscope use on VersB boards with the VersA-based bootloader settings. Have corrected it and created a menu system for the install scripts to handle backup, internal vs. external install options, rebooting into recovery, etc. with the new bootloader settings too. Please re-download the newer version of the install scripts if you are having any issues (and just to have them handy). Enjoy. (updating main post)
Great work. Installed it on this old tab!
So I changed from CM11 to Omni. With omni twrp got installed automatically... Then I didn't like omni and flashed CM11 again. But then my Xperia Z didn't get any cellular signal, so I couldn't do phone calls, receive phone calls etc... Then I thought about flashing CWM again. It worked, flashed CM and everything was working perfectly! But then after reboot into CWM, it booted into twrp.
No matter what I do, twrp gets it way through somehow. I wiped everything, even formatted data (twice)...
The problem with twrp is, that after updating the CM the cellular thingy doesn't work (sorry don't know what it's called in englisch)
TWRP doesn't work with CM11 on my xperia z, CM 10.2 was just fine... but I want CM 11
I installed CM11 on my nexus aswell, there I haven't got any problems at all. The updates work just fine, and no twrp is being installed.
Ohh
I am a real noob... formulate your help as easy as possible
EDit:
I am using philz version of cwm. But that's not the problem, is it?
success (hopefully)
I think I figured out myself...
Will update this post if so
So everything works fine again.
This is what I did:
1. Flash stock rom by using flashtool
2.
Installing CyanogenMod on Sony Devices
Note:
Some devices do not have removable SD cards. Regardless, there should still be a partition on the device named "/sdcard" that can be used for flashing purposes, even though the contents of /sdcard may actually be in internal storage.
Download the prebuilt release of CyanogenMod you wish to install. (Or if you've built CM yourself, look in the $OUT directory for the .zip.)
Optional: Download any supplemental 3rd-party applications packages for the device you wish to use. (You have to install a 3rd-party app to get the Google apps, like Gmail, Play Store, and Youtube.)
Extract the boot.img from the zip to your computer, you will need this file for fastboot.
Place the CyanogenMod rom .zip file on the root of the SD card.
Optional: Place any supplemental packages' .zip file on the root of the SD card.
Put the phone into fastboot mode:
With the device powered down, hold Volume Up and connect the USB cable. The notification light should turn blue to indicate you are in fastboot mode.
Open a terminal on the PC and enter the following:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
While the device reboots, press the Volume rockers a few times to load recovery.
Once the device boots into the ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm your selection, although for some devices the power button is used as a "back" button to go up one level, in which case the home button is used to confirm the selection.
Optional/Recommended: Select backup and restore to create a backup of the current installation on the Xperia Z.
Select the option to wipe data/factory reset.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod file you placed on the sdcard. You will then need to then confirm that you do wish to flash this file.
Optional: Install any additional packages you wish using the same method.
Once the installation has finished, return back to the main menu, and select the reboot system now option. The Xperia Z should now boot into CyanogenMod.
Click to expand...
Click to collapse
http://wiki.cyanogenmod.org/w/Install_CM_for_yuga
Click to expand...
Click to collapse
3. update via Cyandelta updater (Takes less time)
4. Checked if twrp hasn't been installed
5. got happy
6. checked if cellular thingy is working
7. happy^2
I tried to flash MIUI core module using magisk. But MIUI security keeps stopping. Any idea how to fix? Using k33a42. On custom rom (AOSP Extended V4.6)
Hey Bash,
Disclaimer:- once you root your mobile you will lose warranty ad support from the respective companies product you use.
Steps how to install MIUI core in android 7
Download MIUI ROM
Power off your device and restart it into recovery mode.
To turn the phone into recovery mode, press & hold Volume up + Home button (middle button) + Power button simultaneously.
Touch won’t work in Clockworkmod recovery mode (unless you’ve installed touch recovery).
Hence, use the Volume keys for navigation and use the Home button for selection.
In recovery, take a Nandroid backup of your current ROM.
Now, select the ‘wipe data/factory reset option using volume keys.
On the next screen press the Yes option to start the wiping process.
Return to the main menu and select the Advanced option.
On the next screen select the Reboot Recovery option.
This will restart your (x)andorid phone back into recovery.
Click on the ‘install zip from SD card option from the main menu.
Furthermore, select the ‘choose zip from SD card option.
This will display the data present on your mobile.
Simply select the downloaded MIUI 7.zip file.
On the next screen select the ‘Yes’ option to start the ROM flashing process.
Similarly, flash the Google Apps zip file as you have installed the MIUI ROM.
Do not wipe data and cache partitions after installing the GApps file.
Finally, click on the ‘reboot system now option to restart your device.
Enjoy your phone has been successfully installed MIUI7. In my opinion, you should move with the latest android and MIUI version it will fix your all bugs and the newly updated android has many new features that 7 does not have. If you have still an issue then you need to talk with a mobile developer or you should visit your nearest mobile service shop. Try to contact a web app development company that is also an expert in various mobile fields.
Thanks
Katherine272 said:
Hey Bash,
Disclaimer:- once you root your mobile you will lose warranty ad support from the respective companies product you use.
Steps how to install MIUI core in android 7
Download MIUI ROM
Power off your device and restart it into recovery mode.
To turn the phone into recovery mode, press & hold Volume up + Home button (middle button) + Power button simultaneously.
Touch won’t work in Clockworkmod recovery mode (unless you’ve installed touch recovery).
Hence, use the Volume keys for navigation and use the Home button for selection.
In recovery, take a Nandroid backup of your current ROM.
Now, select the ‘wipe data/factory reset option using volume keys.
On the next screen press the Yes option to start the wiping process.
Return to the main menu and select the Advanced option.
On the next screen select the Reboot Recovery option.
This will restart your (x)andorid phone back into recovery.
Click on the ‘install zip from SD card option from the main menu.
Furthermore, select the ‘choose zip from SD card option.
This will display the data present on your mobile.
Simply select the downloaded MIUI 7.zip file.
On the next screen select the ‘Yes’ option to start the ROM flashing process.
Similarly, flash the Google Apps zip file as you have installed the MIUI ROM.
Do not wipe data and cache partitions after installing the GApps file.
Finally, click on the ‘reboot system now option to restart your device.
Enjoy your phone has been successfully installed MIUI7. In my opinion, you should move with the latest android and MIUI version it will fix your all bugs and the newly updated android has many new features that 7 does not have. If you have still an issue then you need to talk with a mobile developer or you should visit your nearest mobile service shop. Try to contact a web app development company that is also an expert in various mobile fields.
Thanks
Click to expand...
Click to collapse
Thank you so much! But there is no miui custom rom for Lenovo k33a42. Do you have any link?
Btw, I saw in GitHub that we can use miui apps by flashing miui core from magisk. I did flash and also Flashed miui security zip. After reboot app appears but it crashes automatically..