[Q] (Q) - running custom ROM but recovery is Stock - Nexus S Q&A, Help & Troubleshooting

[Q] (Q) - running custom ROM but recovery is Stock - Nexus S Q&A, Help & Troubleshooting

Dear NS forum - my colleague has crespo work phone.Last year I rooted and installed custom ROM for all my co-workers. The Nexus S user came to me with a problem; lately has many force closures and is very slow. I booted it into recovery & got the Android on its back with red triangle --> this is Stock recovery, right?
Not sure how CWM disappeared and got replaced by stock recovery.. but that seems the case. Am I correct that -
1. I need to load my PC with Samsung USB drivers to communicate with phone while in fastboot/download mode?
2. I need to install ADB SDK on my pc too?
3. I need to enter fastboot/download mode and flash a custom recovery?
Kindly help confirm the steps required, am I missing a vital step? Which recovery is best suited ... I have no preference over TWRP / CWM.
Lastly, I am very much out of touch with latest ROMs, appreciate any advice on a simple ROM, maybe 4.2 is best...
appreciate any help, I used to know all this stuff but I moved to Note 2 a year ago. Cheers.

Hey, I just read about Wug toolkit, is this a suitable tool for my issue ?....seems I could use it to flash a recovery for this phone which magically reverted to stock recovery .
http://www.wugfresh.com/nrt/

Hey folks, here I look forward to guide the Google Nexus S users of the XDA Community to go custom with their Samsung Nexus S. I shall try to put forth the most prevailing steps to make my way to your minds. Also I will use the fastboot method to accomplish custom during this entire guide. Before we put our hands on the device and begin with the instructions, I would like to state some general terms, for your ease. :good:
Terms & Understanding
* What is Bootloader and Why do we need to Unlock?
A bootloader is a boot initializing component which is generally locked by the device manufacturer to avoid any messing around with the OS. We need to unlock it for the same reason. Once unlocked it will allow us to change the boot sequence and modify the OS in accordance of our needs.
* What is Rooting?
It is a process of gaining root privileges over an Android subsystem. Rooting an Android device is easy in most cases. If you will to Install custom ROMs, kernels, other patches or addons to your Android device, rooting is what you will need. It can be achieved in two ways; either by manual method (using fastboot) or by automatic method (using toolkit or software) . Here, I am going to follow the manual method by using fastboot commands.
* ClockworkMod, what is it?
In short, CWM; It is a secondary recovery system created by Koush (Koushik Dutta), which adds enormous features like wiping partitions, flashing flash able .zip files like ROMs, kernels, patches etc to the stock AOSP recovery. Visit ClockworkMod website for more.
* What does Custom ROM means?
These are the aftermarket Android firmware which are not official supported by the OEM (Original Equipment Manufacturer). They are made available to the Android public by Android developers and contributors all around the world. Custom ROMs are either built from Google’s source code i.e AOSP (Android Open Source Project) or are modified versions of the device manufacturer’s ROM (Stock ROMs or Factory ROMs) with additional tweaks and extend functions which are not delivered with the Stock ROMs. Some of the popular Custom ROMs include CyanogenMod (CM), Android Open Kang Project (AOKP), MIUI, Codename Android (CNA), Oxygen, ParanoidAndroid and many more.
* What is Custom Kernel?
A Kernel is a bridge between the applications and the actual data processing done at the hardware level, In simple words, it is the communication between the hardware and software of an Operating System. In Android world, Custom Kernels play a vital role since they provide the users with several features including changing CPU frequencies, modifying the boot sequence and boot scripts and other features too.
* What are Google Apps (Gapps)? The name speaks for itself. Gapps are Google apps for Android available in flash-able zip format. Most of these applications can now be found and updated via the Google Play Store.Some of the apps include the Google Play Store itself, Google Talk, Google Sync (for adding and synchronizing Google accounts), Google Backup Transport, Car Home, Gmail, Google Maps, YouTube, Google Search, Google Voice Search, Google Music, and Google Docs. In some Custom ROMs, the Google Apps are included. These are usually stock ROMs, smaller or less-common ROMs, or those from areas where intellectual property laws are less commonly obeyed. But many AOSP ROMs, most famously CyanogenMod and AOKP, do not include the Google Apps due to licensing issues. They are after all proprietary code owned by Google and not included in the Android Open Source Project.
Disclaimer
Early necessary requirements
* At least 60% of battery to ensure no random shutdowns due to low battery.
* Backup your storage manually. Also your text messages and contacts using some backup app.
* Install Google and Samsung USB drivers from here
* A compatible USB data cable for undisturbed connection between PC and device.
* Enable USB Debugging in your device’s settings [Settings > Developer Settings > USB Debugging].
* A PC with Windows OS.
* Download Required files
* Extract the downloaded NexusS_files.zip to the desktop. So now you will have a folder named "NSFiles" on your desktop which beholds all the needed files during the process.
Please make sure to follow every single instruction mentioned during the guidelines. This will resist you from any mishaps during the process. Lets begin!
Unlock Bootloader
NOTE: Unlocking the bootloader will erase all the data on the phone as well as SD storage. So be sure to back everything up.
1. Reboot your Nexus S into bootloader mode by pressing volume up + power buttons simultaneously until you see the bootloader screen.
2. Connect your device to the PC via the USB data cable.
3. Open the extracted folder "NSFiles" that we have have on the desktop. On an empty space inside the folder, press shift and right click and then select "Open command prompt here". This will execute a new CMD window which is already cd'ed to the folder's location.
4. Type in CMD:
5.
6. You will now receive a message on the screen. Use the volume keys to highlight "Yes" and select it using the power button.
7. Your bootloader is now unlocked.
8. Highlight and select "Reboot" to reboot your device.
9. You have successfully unlocked your Nexus S bootloader.
Installing Custom Recovery
1. Reboot your phone into bootloader mode by pressing volume up + power buttons altogether.
2. Connect it to the PC via USB data cable.
3. While in the "NSFiles" folder on your desktop, press shift + right click on an empty space and go to "Open command promopt here". This will execute a command window which is already cd'ed to your current location.
4. To Install ClockworkMod touch 6.0.1.0
Type in CMD:
5. To Install ClockworkMod non-touch 6.0.1.0
Type in CMD:
6. To Install TWRP 2.3.1.0
Type in CMD:
7. The CMD prompt will indicate when the flashing is complete, it barely takes a few seconds.
8. Do not exit the bootloader mode, since this is the way to boot into recovery.
9. Now to boot into your new custom recovery, highlight "RECOVERY" and select it using the power button.
Rooting the Nexus S
If you plan to use the stock (factory) ROM, it is preferable to root. Otherwise, all the Custom ROMs out there already have root access.
The mentioned process is recommended to carry out using ClockworkMod Recovery.
1. Download the latest SuperSU flash-able root package. [Chainfire's SuperSU Thread]
2. Power off your device and boot into the bootloader mode by pressing volume up + power buttons simultaneously until you see the bootloader screen. Highlight"RECOVERY" using the volume buttons and select it using the power button.
3. Now, your Nexus S is in recovery mode.
4. Go to "mounts and storage" > scroll to the very last and select "mount USB storage".
5. This will mount your device's storage to the PC.
6. Drag the downloaded "CWM-SuperSU-v0.98.zip" to the root of your storage.
7. Select "unmount" to exit the USB storage mode.
8. Go to "install zip from sdcard" > "choose zip from sdcard" > select the "CWM-SuperSU-v0.99.zip" you placed in the storage and flash it.
9. Once flashed, select "reboot system now"
.
You now have your device rooted. You can officially declare yourself as the true master of your device.
Install Custom ROMs
Installing a ROM is quiet a simple process, you can say that it is the easiest of all.
1. First, you need to choose a suitable ROM that meets your requirements.
2. Once you have chosen, download the ROM's .zip (flash able zip file) as provided by the Author/ Developer .
3. Also make sure to download specific Gapps and other add-on if provided by the developer himself. [If not, download generic Gapps from here]
4. Put the downloaded files to your SD storage either by using USB mass storage directly or by mounting USB storage in recovery mode.
5. Reboot your Nexus S into Recovery mode. Power off your device and boot into the bootloader mode by pressing volume up + power buttons simultaneously until you see the bootloader screen. Highlight"RECOVERY" using the volume buttons and select it using the power button.
* Using CWM:
wipe data/factory reset.
Go to "mounts and storage" > "format /system".
Go to "install zip from sdcard" > "choose zip from sdcard" > select your ROM .zip file that you placed in step #6. Flash it.
Gapps are the next to be flashed just after flashing the ROM. So, flash Gapps following the same way as the ROM. further if your are provided any add-on in a flash able zip format you can flash it the same way after flashing the ROM and Gapps successfully.
Once everything has flashed successfully, select "reboot system now".
* Using TWRP:
Go to "Wipe" > "System" and "Factory Reset".
Go to "Install" > choose the ROM .zip file and flash it.
Gapps are the next to be flashed just after flashing the ROM. So, flash Gapps following the same way as the ROM. further if your are provided any add-on in a flash able zip format you can flash it the same way after flashing the ROM and Gapps successfully.
When flashed, go to "Reboot" > "System".
Your phone will now boot into the custom ROM.
Install Custom Kernels
1. Download the flashable zip package of your desired Custom Kernel.
2. Connect your device to PC via USB cable in USB Storage Mode.
3. Drag the downloaded kernel zip package to the root of your device's storage.
4. Disconnect the device from PC.
5. Power off, now press the volume up button and the power button altogether until you see the bootloader screen. Use the volume keys to highlight "Recovery" and select it using the power button.
6. Your device shall now be in recovery mode.
* Flash using CWM:
"advanced" > "Wipe Dalvik Cache"
"install zip from sdcard" > choose zip from sdcard" > now browse and select the kernel zip package that you placed in your storage root during step #3.
Select "Yes".
Your Kernel will now flash to your OS and replace your current kernel.
When it has successfully flashed, select "reboot system now".
* Flash using TWRP:
"Wipe" > "Dalvik Cache"
"Install" > now browse and select the kernel zip package that you placed in your storage root during step #3.
Your Kernel will now flash to your OS and replace your current kernel.
When it has successfully flashed, go to "Reboot" and select "System".
You now have Custom Kernel installed on your Nexus S.
NOTE: Before choosing any Custom Kernel, do verify that the Kernel is meant to be flashed on your present Android OS version.
Congratulations! You shall now enjoy the full packed potential of your wonderful Nexus S.
If you have got any questions/ queries or you're stuck anywhere in the mid process, comment here. I will try my best and provide you an helping hand.
Sent from my Nexus S using XDA Premium 4 mobile app

Related

N00b tutorial: Flashing EOS3 to MZ604 Xoom (Wifi)

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!

[HOW TO] Beginner's Guide to Flashing & Fun on the A700 (Root, ROMs, Etc.)

Installing ROMS & Such on the A700/701
For Extreme A700/Android Neophytes
Read It All BEFORE Beginning!
Important Links:
http://forum.xda-developers.com/showthread.php?t=1710755 ← Unlock Bootloader
http://forum.xda-developers.com/showthread.php?t=1791165 ← CWM
http://forum.xda-developers.com/showthread.php?t=1806980 ← CM10 Official Thread
http://forum.xda-developers.com/showthread.php?t=2056964 ← CM10.1 Official Thread
http://forum.xda-developers.com/showthread.php?t=2489708 ← CM10.2 Official Thread
-----http://get.cm/?device=a700 ← CM10 Download
-----http://goo.im/gapps ← Google Apps 4.1.2
http://forum.xda-developers.com/showthread.php?t=1995981 ← AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=1952124 ← iconiaN
http://forum.xda-developers.com/showthread.php?t=1953917 ← Vorbeth’s EasyRoot ← Do This to Root!
http://forum.xda-developers.com/showthread.php?t=2004441 ← Vorbeth’s OC GPU Kernel
http://forum.xda-developers.com/showthread.php?t=1994294 ← CoolOne700
http://forum.xda-developers.com/showthread.php?t=2196266 ← IcOdiv for A701 & A700 based on CyanogenMod 10.1
http://forum.xda-developers.com/showthread.php?t=2219575 ← Evil Alex Purgatory A701
http://forum.xda-developers.com/showthread.php?t=2232411 ← 7comp based on RootBox
http://forum.xda-developers.com/showthread.php?t=2510004 ← Official PAC-man 4.3
Software You Will Use/Need (depending on your root method):
http://support.acer.com/us/en/product/default.aspx?tab=1&modelId=4318 ← Acer USB Drivers
http://developer.android.com/sdk/index.html ← Android SDK
General Information:
First off, this was never made adequately clear for new users (without going through a hundred different posts with hundreds of replies): You will be using the Android SDK and the Windows Command Prompt. When installing the Android SDK, change the directory to something easy like C:\SDK because you will be typing it a lot. The directory in that folder you will be using exclusively for this process is the “platform-tools” directory. This is where adb and fastboot are found.
In addition, you will need to activate ADB Debugging on your tablet. This is found by going to Settings -> Developer Options -> USB Debugging. If this isn’t done, you will get nothing accomplished. Yes, you will need to have your tablet connected through USB to your PC for this to work. I know there are other ways, but I’m writing this with brand new users in mind.
After you’ve got that set, you should go ahead and install the Acer USB Drivers. None of my computers could properly identify the tablet without the drivers. Speaking of quirks, 64GB microsd cards are not generally very friendly with CM10 or CWM even when formatted as Fat32. There are lots of issues I can’t find a workaround to. Consider using a 32GB until the kinks are worked out.
I’m also assuming you are currently running the JB OTA that was pushed worldwide in October 2012. If you are not, then there are a few extra steps when installing IconiaN. Although I compiled the instructions you’re reading, I had nothing to do with anything else. In fact, I didn’t write the codes used to install things through the command prompt….I just compiled all the information into one easy-ish to follow paper.
As usual, if anything in this causes a brick to your tablet, it was your decision. I’m just providing the information that has worked for me (repeatedly). Also, as I’m not a developer, nor am I very handy with editing files or trouble shooting things without actually handling them…….Ask your specific questions directly to those people in charge of the files (pawitp, Vorbeth, Moscow Desire, meier2009, odiv81 and alx5962). They’re the gurus at this..I am a plebe in their shadow.
TL;DR:
Install Android SDK to an easy directory.
Install Acer USB Drivers.
Unlock Your Bootloader: (codes from alx5962)
1. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
2. Plug your tablet into your computer through USB. It should automatically mount because you’ve installed the Acer USB Drivers and didn’t skip that step above. J
3. At the command prompt, enter the following:
Code:
adb reboot-bootloader
-- Allow the device to reboot.
4. Type Code:
Code:
fastboot oem unlock
5. Press the + Volume button to select Unlock then - Volume button to confirm.
6. Restart :
Code:
fastboot reboot-bootloader
----- I had issues on step 6. I tried that, and it rebooted to the bootloader screen. To be on the safe side without hard rebooting (not knowing what was going on), I used the command from Step 3. to reboot. This works for ICS and for JB bootloaders, I confirm I used the above steps on both.-----7. Confirmation of your unlocked status will be seen in the upper left hand corner of the screen.
Install Clockwork Mod Recovery: (all work & codes from pawitp)
Somehow I wasn’t able to install this properly (permanently) until last night (11/09/12). I’m still not entirely sure what I did differently, but I’ll try to document it here. The safest version of CWM is 6.0.1.5. Don’t attempt anything without that version or better. I’ve heard that at this time the touch version isn’t working properly, so be sure to download the original style CWM.
To navigate CWM, the following bit of information will come in handy (especially if you’ve never used it before.) Use the ‘Vol-‘ and ‘Vol+’ buttons to navigate up and down and the ‘Power’ button to select your choice. When you have made a choice it will sometimes give a screen with a ton of “NO” options with only one “YES” option (usually near the bottom). Like any good video game, if you scroll upwards, you can get to the bottom of the screen faster.
1. Place the CWM file you downloaded into your “platform-tools” directory. For the sake of being easy to install, I changed the file name to ‘recovery.img.’
2. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
3. Plug your tablet into your computer through USB.
4. At the command prompt, enter the following:
Code:
fastboot flash recovery recovery.img
5. At this point, you have flashed CWM to the system, BUT you will now need to boot into CWM using :
Code:
fastboot boot recovery.img
The caveat here is that you will need to install either a custom ROM or unencumbered boot.img (kernel) NOW. If you do not install one, flashing CWM was pointless because stock recovery will overwrite it at next reboot. When prompted at reboot (leaving CWM after flashing a ROM) you should choose to keep CWM. This was sort of a miscommunication between the devs and myself, but meier2009 and Moscow Desire cleared it up.
-----Step 5. does NOT install recovery, but forces your system to boot into CWM by pushing the file to your A700 from your ‘platform-tools’ directory.-----
For Future Reference: Enter recovery…(JB):
a. With system powered off, press and hold ‘Power’ and ‘Vol -‘
b. When the system vibrates, release the ‘Power’ button.
c. When the system vibrates a second time, slide your finger from ‘Vol-‘ to ‘Vol+.”
d. When the system vibrates a third time, release that button.
Install pawitp’s CM10.1 OR IcOdiv (A701): (all work & codes from pawitp)
Download the CM10 nightly from the official Cyanogen page and grab the Google Apps file (optional, but you won’t have market without it) listed in the links section. Despite what people say, I have always been unable to install from my external SD card. Instead, I save the zip files to the root/main directory of the internal SD. Save BOTH FILES to internal SD at this time. This has always worked for me, but your mileage may vary. You do this at your own risk, blah, blah, blah.
1. Boot your A700 into CWM using the steps outlined in Step 5. (or 6) from “Install Clockwork Recovery Mod.”
2. Backup your system by navigating to “backup and restore” by using the ‘Vol-‘ and ‘Vol+’ buttons to navigate up and down and the ‘Power’ button to select your choice.
3. At this point, there are two options for you. “backup” and “backup to external_sdcard”…. I have never been able to mount my 64GB Fat32 external_sd in CWM. Try a smaller card if you have one available (I don’t). If you can backup to external, that is probably necessary when coming from stock. I would only backup to internal if you are just updating from an older nightly or previous rom.
4. On the main screen, assuming you’re coming from stock JB or ICS, you will need to do a couple of wipes. I’m positive the first is necessary, and have read in other parts of threads and other forums that the other two wipes are needed, but as they’re both called “cache,” I went ahead and did both (with no ill effects).
Select “wipe data/factory reset”
Select “wipe cache partition”
Select “advanced” and navigate to “wipe dalvik cache”
Go back to the main menu.
5. From the main menu, select “install zip from sdcard”.
6. Select “choose zip from sdcard” and scroll down to the CM10 zip file. Press the ‘Power’ button to select and confirm.
After this has successfully installed, you can choose to install Google Apps or not. I’m assuming you will want to install them because…well…who doesn’t?
7. To install Google Apps, follow Steps 3 and 4 from above, but this time you will choose the gapps zip file instead of the CM10 zip.
8. Reboot Device & Enjoy well sorted Jelly Beans.
Install iconiaN: (all work & codes from Vorbeth)
At the moment this is my favorite. It is one version number (4.1.1) behind CM10 (4.1.2), BUT it is compatible with my SD card, and is similar to the stock experience …. only faster and without the bloatware. The only reason it is second in this guide is because of the alphabet (C before I & P before V).
The latest updates to the ROM bring the latest GAPPS and firmware. meier2009’s 4Way Reboot Mod is also included (and rocks).
1. Boot your A700 into CWM.
2. Follow Steps 2-6 from above if coming from stock JB (or CM10, or CoolOne700) with the exception that you’re installing the iconiaN zip (not CM10, duh). Also, iconiaN comes with v4.2 Google Apps pre-installed, so no need for Step 7.
-----2.a. If coming from stock ICS, you will need to install the Jelly Bean Firmware (Found in the Aroma Setup of the ROM)
3. If coming from an older version of iconiaN, you shouldn’t need to do the wipes, but go ahead and do the backup just to be safe.
4. Reboot Device & Enjoy well sorted Jelly Beans.
-----On a side note, I went ahead and installed BusyBox (https://play.google.com/store/apps/details?id=stericson.busybox) not sure if this was necessary, but I am suffering no ill effects from having it running on my tablet. -----
Install Vorbeth's OC GPU Kernel: (all work & codes from Vorbeth)
This is a custom kernel (as of this writing available only for the A700) that overclocks the Tegra 3 from 1.3Ghz to 1.5Ghz. There has been a noted improvement in gaming performance using this kernel.
1. Boot your A700 into CWM.
2. From the main menu, select “install zip from sdcard”.
3. Select “choose zip from sdcard” and scroll down to the iconiaN Kernel zip file. Press the ‘Power’ button to select and confirm.
4. Reboot Device PLAY SOME GAMES! WEE!
Install Vorbeth’s EasyRoot: (all work & codes from Vorbeth)
If for some reason you’re happy with stock and just want a very simple way to ROOT, then this is for you. Using this kernel will cause OTA to stop working (or you will have to edit the updater-script) and remove all the file checks. The latest update has made all previous instructions null, and it is now exceedingly easy to install ROOT on your A700. Awesome! Still, this does require an unlocked bootloader.
1. Download and extract the EasyRoot ZIP on your computer.
2. Locate and double click the file 'easyroot.bat'.
3. Follow all onscreen instructions.
4. Profit.
CoolOne700: (all work & codes from meier2009)
This is the new kid on the block. meier2009 has included three different install options in this ROM including Full (rooted stock), Small (all the Acer bloatware removed), and Custom (Choose what you want.) It’s definitely one to keep an eye on. Custom install is very handy. He’s also got his 4Way Reboot Mod which adds all our favorite reboot/recovery features. Sweet! Also, BusyBox and SuperSU are included on install, so you don’t need to worry about that.
1. Boot your A700 into CWM.
2. Follow Steps 2-6 from CM10 Install if coming from stock JB (or CM10, or iconiaN) with the exception that you’re installing the CoolOne700 zip (not CM10, duh). Also, CoolOne700 comes with Google Apps pre-installed, so no need for Step 7.
-----2. a. If coming from stock ICS, you will need to install the Jelly Bean Firmware (Found in the Aroma Setup of the ROM)
3. If updating from an older version of CoolOne700, you won’t need to do any of the wipes, but it is always a great idea to do the backup.
4. Reboot Device & Enjoy well sorted Jelly Beans.

Code:
6. If upon reboot, you hit the old system recovery, you will need to reflash the recovery.img OR just work around it by doing:
Code:
fastboot boot recovery.img
-----Step 6. does NOT install recovery, but forces your system to boot into CWM by pushing the file to your A700 from your ‘platform-tools’ directory. I had to use this method to install CM10 because I was never able to get CWM to install. Your luck may be different.-----
THAT´s the Trick my Friend !
Install recovery with
Code:
fastboot flash recovery recovery.img
AND THEN
Code:
fastboot boot recovery.img
Install any ROM and if you´re rebooting and asked to FIX Recovery, answer YES, then it will be leaved there !!!
With this way your also able to start CWM Recovery temporary
only use
Code:
fastboot boot recovery.img
then CWM will start, you can flash anything and after that CWM is gone, because the Stock Recovery is always inside the Recovery Partition

Makes sense then how I finally ended up with CWM actually installed on my tablet. Were the original instructions from pawitp mistaken, or just incomplete?

ExtremeRyno said:
Makes sense then how I finally ended up with CWM actually installed on my tablet. Were the original instructions from pawitp mistaken, or just incomplete?
Click to expand...
Click to collapse
Lost in translation...

ROFLMAO

Added more info last night and have now included the AOSP 4.2 to the links. Keepin' this bumped & updated.

Thanks for posting this excellent How To! I used it to install CM10.
I can confirm the backup to external backup functionality does work with a 8 GB MicroSDHC card. One thing you could do to bypass the external vs internal SD card discussion is to use sideloading. I used it to both install CM10 and the Google Apps and it works nicely. Just select Update through sideload in CWM and then enter 'adb sideload <filename>' on the command line and everything works nicely.
Also for the real beginner you could may be suggest backing up all user applications using Titanium Backup in order to easily restore them after flashing a mod.

Bumping thread back near the top. Lots of people got an A700 for the holiday and it seems many of them are bricking or at least screwing things up using outdated methods or strange new forms of CWM from other forums.
Also, thanks for the info, SanjuroE. Appreciated, and I can honestly say I never knew how to do the sideloading thing. I didn't actually realize that was what it was as on my old tablet (three years ago) sideloading was always in reference to installing from the external SD.

This guide was awesome. Many thanks for this.

I flashed CWM 6.0.3.1 via fastboot.
After that I tried fastboot boot recovery.img but it doesn't work.
On the display:
Booting downloaded image.
But nothing happens ??
Can anyone help me ??

schlex2010 said:
I flashed CWM 6.0.3.1 via fastboot.
After that I tried fastboot boot recovery.img but it doesn't work.
On the display:
Booting downloaded image.
But nothing happens ??
Can anyone help me ??
Click to expand...
Click to collapse
Loot at
http://forum.xda-developers.com/showthread.php?t=1791165
Post #166 to end of thread.

cfgh said:
Loot at
http://forum.xda-developers.com/showthread.php?t=1791165
Post #166 to end of thread.
Click to expand...
Click to collapse
Thanks mate!
I tried another recovery.img and than everything went fine!! :good:

USB driver link is not working.

papars said:
USB driver link is not working.
Click to expand...
Click to collapse
Check this : http://forum.xda-developers.com/showpost.php?p=58172023
Many files available, including Drivers

I can't connect my iconia a700 to PC (Windows 10) is say: device not found. Any help?
I install USB Driver, but in Device managers shows Acer Iconia Tab a700 with yellow worming sign.

Driver Issues WIN10
goralpm said:
I can't connect my iconia a700 to PC (Windows 10) is say: device not found. Any help?
I install USB Driver, but in Device managers shows Acer Iconia Tab a700 with yellow worming sign.
Click to expand...
Click to collapse
Hi,
I have the same issue and it took me hours to even find a driver from ACER. But even after the installation I cannot get the tablet to work stable. I installed general MTP drivers which gave me access to the "adb reboot-bootloader" command but during the reboot the tablet gets stuck on the Acer logo screen and does not boot into the bootloader. I have to unplug the tablet and only then I get the white text in the top left corner of the screen saying "starting Fastboot USB download protocol". But that is it. I assume that fastboot would use the Acer drivers to access the tablet but I don't have any for windows 10.
My question: Could somebody post drivers for Windows 10 for the A700/A701?
Thanks
realshadow

realShadow said:
Hi,
... ...
My question: Could somebody post drivers for Windows 10 for the A700/A701?
Thanks
realshadow
Click to expand...
Click to collapse
I had exactly the same problem. The solution was give here: https://forum.xda-developers.com/showthread.php?p=48915118
You don not need Acer driver.
- Wayne

A2107A-H Firmware update, Custom Rom and CWM Recovery (calling feature - unlocked)

Finally it happend, NEW CUSTOM ROM (CWM Backup Mode) made by me.
screenshots
https://www.dropbox.com/sh/yc7z5904i0e1ua6/6FSVniszMM#/
Just see it in action: http://www.youtube.com/watch?v=joeJtkw-85c
- CWM Recovery
- Firmware version S314
- Calling feature
- Fully working google service
- Fully Roted
- Titanum Backup
- TouchPal Keyboard
- Stock Browser
- Full synchronization with google service
- Radio without headphones
and many more
The installation is very simple and will take about 5 minutes if you already have a CWM Recovery
I spend nearly whole week to build this customisation, so I decide to ask you guys for some support for my work. So if you like the job I done so far and want to see a new improvements in a future including a Jelly Bean on Lenovo A2107A-H please support me. In this case I made a auction on a EBAY for this modiffication and it will cost just a £5. Please respect my work and don't distribute my mod behind my back. If you not agreed with this, I waiting for your coments guys. Thank you.
http://www.ebay.co.uk/itm/221163148...l?_sacat=0&_from=R40&_nkw=221163148891&_rdc=1
I will send you a link to a firmware and manual after a payment
Enjoy!!!
OLD MANUAL (no files on a server)
Manual and files for installation Custom ROM + CWM Recovery + IMEI repair + ROOT + Calling Feature on IdeaPad A2107A-H
Password for archive:"xdadevpemergency"
Firmware
1. CWM Recovery ROM.
https://rapidshare.com/files/3358458529/CWM Firmware.zip
2. A2107A-H v9 ROM in a zip format for install by CWM Recovery.
https://rapidshare.com/files/241044528/A2107A-H v9.zip
3. Google apps for google store and account sync (installation by CWM Recovery)
https://rapidshare.com/files/2713449644/gapp-ics.zip
Tools
1. SP Flash Tool for formating device NAND FLASH.
https://rapidshare.com/files/1465167471/SP_Flash_Tool_v3.1206.01.zip
2. Smarthphone Multiport for Flash the CWM REcovery ROM.
https://rapidshare.com/files/2880421726/SP_MDT_src_v3.1216.02_A2012.05.22.zip
3. MTK Droid Tools for easy IMEI repair and easy ROOT install.
https://rapidshare.com/files/3431631170/MTKdroidTools.zip
Manual
Device formating
1. Open SP Flash Tool
2. Choose a "Scatter-loading" file from "CWM Recovery ROM" folder
3. Press "Format" in a left top corner of SP Flash Tool
4. Choose "Auto Format Nand Flash" -> "Format whole flash" and press "OK"
5. Connect device to PC, press "reset" button on a back of your device
Your device should be formated on this point.
6. Close SP Flash Tool
Installing CWM Recovery ROM
1. Open Smartphone Multiport
2. Press the "Scatter File" button and choose this file from a CWM Recovery ROM folder
3. Tick to both "Sel All"
Settings for Smartphone Multiport:
Type: Firmware upgrade
Baud rate: 921600
DA download all: High speed
USB Port: BootRom --->DA
4. Press Start all
On this point firmware should be downloaded on your decive, if nothing happend press the "reset button" on a back of your device.
After this operation you will have a CWM Recovery, but not a main firmware!!!
Installing main firmware
1. Copy A2107A-H v9.zip and gapp-ics.zip to sd card.
2. Boot in to CWM Recovery mode by:
- Press the "reset" button on your device
- Press and hold for a 3 sec. "power" button on your device (after 3 sec. releas the buton)
- When you see "lenovo" logo press and hold vol+ and vol- untill you will boot in to CWM Recovery mode
In a CWM Recovery Mode
Menu down = vol-
Menu up= vol+
accept= power button
1. Choose "wipe data/factory reset"
2. Choose "wipe cache partition"
3. Choose "Advanced" -> "Wipe Dalvik Cache"
4. Go to main menu of CWM Recovery mode
5. Choose "install zip from sdcard"
6. Choose "choose zip from sdcard"
7. Find the A2107A-H v9.zip file.
8. Choose "Yes - Install A2107A-H v9.zip"
Do the same think with gapp-ics.zip and reboot your device.
IMEI repair and ROOT installation
1. Connect your device to the PC (device must be turned on and connected as "USB debugging" and "Media device)
2. Start MTK Droid Tools
3. Press Replace IMEI (fill up IMEI 1 and IMEI 2) and save
4. Reboot device
On this point you should have a IMEI working, if not repeat IMEI repair from point 3.
5. Press ROOT button if the program ask for anythink press "YES" (your device will reboot 2 or 3 times and it will be ready to go).
Click to expand...
Click to collapse

Reupload Please

Please reupload the tools section.
Thank you in advance

I will but I dont know where, they was on rapidshare, Blocked already, on a dropbox, blocked already. Any ideas where to upload them?

pemergency said:
I will but I dont know where, they was on rapidshare, Blocked already, on a dropbox, blocked already. Any ideas where to upload them?
Click to expand...
Click to collapse
Hi there,
Can you try http://uploaded.net/ ?
I used it for many files so far and seems to work OK.
Thank you.

re
yesterday on Chinese side get everything.
flashed - rom (lots of Chinese garbage) does - only Chinese and English.
English also very buggy - phone goes.
sorry ... google translator

.................................................

german language ?

Yes for settings and all stock app. All apps added by myself are not translated
Sent from my GT-N7000 using xda app-developers app

brief assessment of the costum rom "pemergency" mod = which must be paid
- Setup / flash -> OK
- IMEI must be corrected manually by terminal as tool does not work
- Constant error message "simcard failed" (slot2) although only 1 slot has
- "apex launcher" can not uninstall, then stops at the boot process lenovo screen -> I would also like to use but "default / original" surface.
- Spoke only Russian / English / chinese integrated as standart
- Morelocale2 indeed is an alternative but not "original"
ok, first feedback - hope the rom is modified?

mrbonsen said:
brief assessment of the costum rom "pemergency" mod = which must be paid
a) Setup / flash -> OK
b) IMEI must be corrected manually by terminal as tool does not work
c) Constant error message "simcard failed" (slot2) although only 1 slot has
d) "apex launcher" can not uninstall, then stops at the boot process lenovo screen -> I would also like to use but "default / original" surface.
e) Spoke only Russian / English / chinese integrated as standart
f) Morelocale2 indeed is an alternative but not "original"
ok, first feedback - hope the rom is modified?
Click to expand...
Click to collapse
a) no comment
b) IMEI must be corrected and it is mentioned in a manual, it doesnt need to be done by terminal, you can simple generate a file and swap with a root explorer
c) This Rom is for A2107a-h which is a 2 slots device, so I dont see a problem on this point
d) I said as this is modiffication, I decide to remove a stock launcher, you can install any other one of your choice
e) I also answered to your question as for german language only original apps are translated and the main system, on other threeead is clearlly said as this rom using more locale 2 for translation.
f) and as a last one, why you expecting anything original in a modiffied ROM?
I stoping to doing anything with this ROM for a simple reason:
- FREE ROM = 900 downloads,
- PAID ROM FOR £5 = 5 downloads - embarrassing
Why?
and one more thing...
My correspondence with mrbonsen, when I tried to help him out with the installation process is also interesting. About 10 emails with instructions to mrbonsen and also 10 emails of insults from mrbonsen. That means something....
So conclusion is simply... go back to your original firmware and I will give you your £5 back

and also 10 emails of insults from mrbonsen.
Click to expand...
Click to collapse
I would, at least at three mail the conversation ended :victory:
b) IMEI must be corrected and it is mentioned in a manual, it doesnt need to be done by terminal, you can simple generate a file and swap with a root explorer
Click to expand...
Click to collapse
if you tool mitsendest + description for the correction of the IMEI, it should work well. not every user knows another solution
But no matter now - can only recommend not to use this rom :good:
ask no insult but (as in the mails) what's wrong on the screen, apex launcher bug or "bug mrbonsen" - display does not turn or apex

mrbonsen said:
I would, at least at three mail the conversation ended :victory:
if you tool mitsendest + description for the correction of the IMEI, it should work well. not every user knows another solution
But no matter now - can only recommend not to use this rom :good:
ask no insult but (as in the mails) what's wrong on the screen, apex launcher bug or "bug mrbonsen" - display does not turn or apex
Click to expand...
Click to collapse
Hehe, ok, this is all my fault, I just should expecting as this ROM could be installed by a persona like you, my bad
BTW I using this ROM from a weak or more and have no problem at all. Waiting for comment from other users ...
Sent from my IdeaTab A2107A-H using XDA Premium HD app

And one more thing, what model do you have? if anything was wrong you could always ask, you didn't so....
Sent from my IdeaTab A2107A-H using XDA Premium HD app

pemergency said:
And one more thing, what model do you have? if anything was wrong you could always ask, you didn't so....
Sent from my IdeaTab A2107A-H using XDA Premium HD app
Click to expand...
Click to collapse
You did a great job and 900 downloads are impressive. i have a A2107A-H 1GHz 1GB RAM 16GB Flash - how come nobody is providing feedback or helping out in this development? Could there be a way to update.zip just the standard factory ROM? maybe that could be possible by doing a diff on the chinese and european source code? sorry i'm just a lamer looking to help out. any news from lenovo developers on the 4.1 release?
today is your cwm rom accessible for download for trial?

Ofcourse it is possible to get back the standard ROM just ask someone who still have a European ROM to do a copy by nandroid backup and you can restore this by centeCWM. So after that you will have a stock ROM with CWM but without calling feature.
I nearly finish another ROM with calling feature but this will be based on Russian ROM. I just need to get European system backup to do it same thing with European ROM.
Sent from my IdeaTab A2107A-H using XDA Premium HD app

Password for CWM Firmware : xdadevpemergency
NEW MANUAL AND FILES (discontinued project)
For both option's copy "clockworkmode/backup/modpemergency" folder to sdcard internal or external!!!
OPTION 1: For CWM Recovery devices:
Downloads:
Pemergency MOD custom firmware https://hotfile.com/dl/182755080/f7d30b5/07122012.rar.html
1. Unpack archive 07122012.rar
2. Copy whole folder clockworkmode to your internal storage or external sdcard.
It should looks like this one:
/sdcard/clockworkmode/backup/modpemergency (nandroid.md5 and system.ext4.tar inside this folder)
Boot in to CWM Recovery:
1. switch off dfevice
2. Hold Power Button for 3 sek, release and hold vol+ and - together untill you will boot in to recovery mod
In CWM Recovery:
1. Choose "backup and restore"
2. Choose "advanced restore from internal sdcard" or "advanced restore" in a case of using external card
3. Choose "modpemergency/"
4. Choose "Restore system"
5. Choose "Yes - Restore System"
After update choose
1. "wipe data/factory reset"
2. "wipe cache partition"
4. "advanced/wipe dalvik"
5. reboot.
It will take a while to boot for a first time so no worries
OPTION 2: For non CWM recovery devices
Copy clockworkmode/backup/modpemergency to your external card, it should looks like this:
/sdcard/clockworkmode/backup/modpemergency (nandroid.md5 and system.ext4.tar inside this folder)
downloads:
1. CWM Recovery https://hotfile.com/dl/182805290/fe4ac19/CWM_Firmware.zip.html
2. Flash Tools https://hotfile.com/dl/182820835/8dd3c06/Tools.rar.html
3. New Flash Tool without error (replacement for the one from Tools.rar package https://hotfile.com/dl/183057140/692cbbb/SP_MDT_src_v3.1216.02_A2012.05.22.zip.html
4. Pemergency MOD custom firmware https://hotfile.com/dl/182755080/f7d30b5/07122012.rar.html
5. USB Driver
For windows xp https://hotfile.com/dl/182950442/360c725/USB_VCOM_Driver.zip.html
For windows seven https://hotfile.com/dl/182950251/0c9ee3d/usb_driver.zip.html
Install CWM Recovery:
Device formating
1. Open SP Flash Tool
2. Choose a "Scatter-loading" file from "CWM Recovery ROM" folder
3. Press "Format" in a left top corner of SP Flash Tool
4. Choose "Auto Format Nand Flash" -> "Format whole flash" and press "OK"
5. Connect device to PC, press "reset" button on a back of your device
Your device should be formated on this point.
6. Close SP Flash Tool
Installing CWM Recovery ROM
1. Open Smartphone Multiport
The "Data source file" and "Da file name" should have assigned path from SP_MDT_src_v3.1216.02_A2012.05.22 folder. If is not assigned properly please do the folowing steps:
- File/Open Download Agent File and choose file MTK_DATABASE.mdb from SP_MDT_src_v3.1216.02_A2012.05.22 folder
and
- Factory database/Setup data source file and choose file MTK_AllInOne_DA.bin from SP_MDT_src_v3.1216.02_A2012.05.22 folder
2. Press the "Scatter File" button and choose this file from a CWM Recovery ROM folder
3. Tick to both "Sel All"
Settings for Smartphone Multiport:
Type: Firmware upgrade
Baud rate: 921600
DA download all: High speed
USB Port: BootRom --->DA
4. Press Start all
On this point firmware should be downloaded on your decive, if nothing happend press the "reset button" on a back of your device.
After this operation you will have a CWM Recovery, but not a main firmware!!!
Install pemergency custom ROM
1. Unpack archive 07122012.rar
2. Copy whole folder clockworkmode to your external sdcard.
Boot in to CWM Recovery:
1. switch off dfevice
2. Hold Power Button for 3 sek, release and hold vol+ and - together untill you will boot in to recovery mod
In CWM Recovery:
1. Choose "backup and restore"
2. Choose "advanced restore"
3. Choose "modpemergency/"
4. Choose "Restore system"
5. Choose "Yes - Restore System"
After update choose
1. "wipe data/factory reset"
2. "wipe cache partition"
4. "advancedwipe dalvik"
5. reboot.
It will take a while to boot for a first time so no worries
After that sometimes it is nessesary to repair IMEI
IMEI repair
1. Connect your device to the PC (device must be turned on and connected as "USB debugging" and "Media device)
2. Start MTK Droid Tools
3. Press Replace IMEI (fill up IMEI 1 and IMEI 2) and save
4. Reboot device
Good Luck...

NEW ROM on the way. Will be posted on the end of this week.
- oryginal multilanguage for most of languages like in a stock european ROM (not more locale)
- fixed most bugs from the previous pemergency mod
- stock launcher
- Battery life incresed to 30% more then oryginal ROM
- Battery status in a settings
- Downloading all apps from google store (no incompatibility problem)
- Quick Boot
- Better sim management
- All options for synchronisation, like in oryginal european stock ROM
and many many more...
Finished in 98%
Anyone would like to pay for this £5?
Free update for everyone who bought the previous version!!!

ok, I certainly update :good:
may inform some user from the German forum.
pretty much at the end of the page
http://www.android-hilfe.de/lenovo-ideapad-a2-forum/341347-a2107a-root-cwm-custom-rom-5.html

[ROM][A51] HAVOC OS for Samsung Galaxy A51 [CUSTOM ROM]

Hey Guys,
Before you dive in, irrespective of your reading speed read this carefully and slowly for better understanding but if you cannot focus and read it slowly then you better give up music for a few weeks.
About the Device
Before you jump in and get your hands dirty.. you should know that what you will be installing is Generic System Image, It is not specifically made for your device so if you are going to install some other GSI other than this, you might face some issues.
If you are a beginner, you should Go Through Project Treble, just for the sake of knowledge.
Also Galaxy A51 has A/B partition and Supports Project Treble though remember that Treble Devices are not same as A/B devices and Vice Versa.
Things You’ll Need
A Computer (not an iPad)
Internet [requirement around 6 gigs (4.8 gigs optional, for downloading stock Firmware, Highly Recommended)]
Samsung Galaxy A51 (will not work on A50)
Patience and a madcap attitude.
Resources
Download Odin from the link given below and extract it in a folder.
https://odindownload.com/download/Odin3_v3.13.3.zip
Adb and Fastboot Drivers
https://gsmusbdrivers.com/download/adb-fastboot-drivers/#
Samsung Drivers
https://developer.samsung.com/mobile/file/68b2dc40-3833-4a8b-b58e-32f7aca25c00
Havoc OS GSI
Havoc-OS - Browse /arm64-ab at SourceForge.net
Don’t forget to check that there is “arm64” and “ab” written on the name of the file
Other option is with Gapps (it means the rom will come with Google Play services built in
otherwise it is Vanilla Android.
GSI Flasher
(It is used for converting your img file into flashable Zip)
https://drive.google.com/file/d/1J8OlI2CCXpvAJ5FhFlR2b_y58eHQERGs/view?usp=sharing
Extract it you’ll find three folders gsi, META-INF, scripts, keep all of them inside the GSI
Flasher extracted folder.
Twerp Recovery
twrp-a51-3.5.0_10-1_ianmacd.tar | by androidhowto for Utilities (androidfilehost.com)
Do not use any other in this case you might get mounting errors.
Encryption Disabler
Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip | by androidhowto for Utilities (androidfilehost.com)
Its Show time
1. Go to settings and go to about phone, tap build number 7 times and a dialog will appear, you are now a developer.
2. Go to additional setting or search developer options in the settings search bar
3. Once in the developer settings find OEM unlock and turn in on, scroll down and also turn on USB debugging, your phone will ask the permission for accessing the data by your computer.
4. Turn off your device. Get a usb cable and connect it to your computer.
5. While phone is off first press Volume UP and Volume Down together, and then then insert the usb cable into the phone while holding the buttons wait for two seconds. a blue screen will come up telling you about consequences and life choices.
6. Long press the Volume Up Button and a new blue screen will show up asking you for unlocking the bootloader. Press Volume Up to confirm. You device will erase everything and reset itself ( Don’t forget to take backup of your Data).
7. After the setup screen appears skip everything in the setup and enable developers option and enable USB debugging in the developer options.
8. Turn off your device again and Repeat step 5.
9. Press Volume up for entering the download mode
10. Now in your computer, Install Odin and open Odin.exe you’ll find your device as comm: xx
Now click on the AP button and select the twerp you downloaded.
Press start and twerp will be installed in your device. Your device will reboot don’t let it boot to one ui, press all three buttons together and hold, as soon as the screen goes black release only the volume down button. Keep holding the Volume UP and power buttons for 3 seconds and then release, you find yourself in twerp. If you miss it repeat the process again but don’t let it boot to One Ui.
In twerp press wipe => format data =>type yes. Press home button and again go to wipe advanced select Data, Cache and Dalvik and swipe to clear.
Press home again. Go to reboot and select recovery, twerp wil reboot. Once it reboots transfer the encryption disabler to your phone and in twerp press install select the storage, sdcard or internal storage, where you have stored the file, select it and swipe to install.
Now in your computer extract the Havoc os image and rename it as “system.img”.
Extract the GSI flasher, copy system.img and paste it in the gsi folder of the GSI Flasher.
Select gsi, Meta-inf, scripts and compress them into a zip and transfer into the phone.
Now in twerp Press install, select the zip file and swipe to install. Also install Gapps or Magisk if you want (though normal magisk will have problem try install phh_magisk, discussed later).
Reboot and KABLAMO You have installed Havoc OS.
Bugs
A small random issue in Auto Brightness
If you root with magisk and install modules, after you reboot your phone will get into a bootloop. Use Phh_Magisk but I aint sure if it’ll work or not Your call madcap.
NONE OF THE FILES IN THIS TUTORIAL HAVE ANYTHING TO DO WITH ME. If SOMETIHING HAPPENS I AM NOT RESPONSIBLE. ONLY DO IT AT YOUR OWN RISK.
Troubleshooting.
If you find errors in twerp, such as unable to mount vendor or system_root, or data. Then you got to install the stock One Ui Back again, therefore it is highly recommended to keep with yourself the stock firmware. You will need It. And it is 4.78 gigs. You can download it from
Model : SM-A515F - Galaxy A51 — Samfrew.com
To reinstall the stock firmware first extract it and the open odin and repeat steps 8 and 9, once your device is detected in Odin press the respective buttons and select the respective files such as for BL button select the file With BL in the name. Do it for buttons, BL, AP(once you select the file it will take long for it load into odin so do not panic and let it load, it might become unresponsive but use patience and wait.)CP , CSC. Click on start and you’ll have ONE Ui back on your device.
To Lock the bootloader repeat steps 5 and 6.
If you still want more stability and Control You can install a different Kernel NDataX from (@Hendamanu) https://forum.xda-developers.com/m/hendramanu.11224917/

Thanks for your contribution

Can someone help me to understand this custom ROM installation?

Hello, I'm new here, I've been dealing with certain ROM mods for a little while. My test device is an old Samsung Galaxy S4 mini (GTI9195). Now I've been sitting for a few days trying to figure out how to bring my device up to date as best as possible. Lineage OS seemed the best to me. Unfortunately there is no officially confirmed software for my device directly from Lineage, which is why I looked elsewhere. I came across this thread on XDA: https://forum.xda-developers.com/t/...520-r890-unofficial-11-0-0-lineageos-18-1-for -s4-mini.4189967/ . The user arco68 is, so to speak, the boss among S4 mini modifications. Unfortunately, I can't find exact instructions anywhere (especially for the recovery) on how to install all the packages correctly. That's why I researched. I was able to record various steps, but cannot determine if they are correct. Can someone on this forum please help me? My steps:
1. Turn on developer options
2. Turn off OEM encryption (if available)
3. USB debugging on.
4. Download and install Android platform tools in Path
5. Download and zip Magisc
7. Put the phone in bootloader/fastboot/download mode (volume down + home)
8. Flash Team Win Recovery Project (or other custom recovery).
9. Restart phone and boot into recovery mode (volume up + home + power)
10. Erase all data
11. Copy Google Apps to Phone (Optional)
12. Copy Lineage OS (or other custom rom) to phone
13. Install packages one by one (OS first)
14. Reboot device
15. Wait and set up

Okay, First of all requirement-
A portable sd card- Because after flashing twrp, you might face issue where you can't access internal storage from twrp. That's because the phone might be encrypted. You have to decrypt it by flashing a "disable dm verity- forceencrypt.zip". In this case, you might not be able to transfer files from pc when booted into twrp. So, It's a smart move to insert a sd card containing all required files before to avoid these problems.
Another requirement is samsung drivers installed in pc. I will attach that file.
Follow these steps -
1/Unlock bootloader -Go to developer options. Turn on oem unlocking. It will tell you that you're going to loss all data. Proceed. If it doesn’t tell you anything, then there is definitely some extra process to unlock bootloader of your device.(search on internet)
2/Download your phone's official firmware in pc- it will help you if anything goes wrong. Search " Sm fw" on google. Go to first site. Create an account. Search the model number, Download a firmware that matches with all your device's information in "About phone".
3/ Download the lineageos rom and twrp recovery for your model. Then install device info hw from play store to check bits(32/64). Search open gapps. Go to the website. "arm" is for 32 bit & "arm64" is for 64 bit. Select which matches to your device’s bit. Then select the android version of the custom rom. Then select "Pico". Download the file. Next, download latest magisk 25.2 from github page. Rename the apk file to "magisk.zip" Move rom,gapps, magisk.zip to SD CARD. Keep twrp in pc.
4/In pc, download latest odin software. It's an special software for samsung download mode. (There is no fastboot mode in samsung)
5/Boot your device into download mode. And connect with pc.
6/In pc, extract the twrp file(If It's in zip format). Open odin software, Go to options, turn off auto reboot. Now select "AP" & select that extracted twrp file. Click open. Then hit start button.
(Note that most of the samsung devices can't boot stock rom after flashing twrp. So you have to flash custom rom to boot your device. Follow the next step)
7/Boot into twrp wipe>format data>type "yes". Press home button. Install>Select storage>SD card>select the rom.zip. Then add more zips> select the gapps.zip. Again, add more zips> select magisk.zip. After all, swipe to flash.
After installation, reboot device.
What if anything goes wrong?
Extract the stock firmware that you downloaded from sm fw. Connect device in download mode. Open odin, select AP,BL,CP,CSC file one by one. Start flashing. You device will be alive again.

Database Info

welcome