Database Info

[A511/A510] [01-07-2012] CWM Recovery - TESTING only (can cause bricks!!)

Hi all,
Well, it looks like it works now!
Touch is also available, built through the builder of CyanogenMod (turned out I used the wrong recovery, I now used boot.img from the 1.011 ROM). Use the power button to go back one step (up one level in the menu).
For the non-touch version you can use Volume+ (one dot) and Volume- (two dots) works and use power to select an option.
** WARNINGS **
My device is hard-bricked due to the restore function not working correctly... be careful what you do!
Extra WARNING - do not use:
WIPE DATA/FACT. RESET
FORMAT PARTITIONS
BACKUP/RESTORE
FOTA
1. Avoid FOTA (software update from Acer, directly on device), see update here
2. I have not tested each function yet!
3. Step 12 below seems to have a problem. Sometimes the recovery does get corrupted and needs to be reflashed.
4. Try to not use wipe/backup/restore features - only install from zip has been tested and works
** Downloads **
EDIT FROM THE ARCHANGELULLED LINKS TO AVOID BRICKING DEVICES
** Uninstall **
Uninstall has not been tested in most cases. Please let me know whether this is sufficient and whether it works.
A510
Install the A510 Stock Recovery using the batchfile in the following download:
{
"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"
}
A510-stock-recovery.zip (4.48 MB)
A511
Try the steps in the following post:
http://forum.xda-developers.com/showpost.php?p=29101012&postcount=108
If that doesn't work (for instance because the install-recovery.sh file does not exist), try installing the files from the following post:
http://forum.xda-developers.com/showpost.php?p=29217619&postcount=111
** Credits **
Dees-Troy for the versions of the BoardConfig.mk & recovery.fstab on his github
Cyanogenmod for their CWM-recovery-build-website
Koushik Dutta for his porting CWM guide
** Install instructions **
1. Boot your device
2. If it's already unlocked, skip to step 7
3. Type following in a DOS-prompt:
Code:
adb reboot bootloader
4. Wait till device is booted and reconnected to pc (ie. drivers loaded)
5. Type following in a DOS-prompt:
Code:
fastboot oem unlock
6. Be quick (it times out) to unlock the device. Use Volume- key to highlight the unlocked lock and press the Volume+ key to activate
7. Type following in a DOS-prompt
Code:
adb reboot-bootloader
8. Wait till bootloader is loaded and reconnected to pc
9. Type following in a DOS-prompt:
Code:
fastboot flash recovery XXX.img
(replace XXX with the image file name of your choice)
Remark: step 10 to 12 can be skipped if you'll also root your device with my root-cwm-zip. That already removes the same file, so you shouldn't experience this issue
10. Reboot the device and hold to Volume- button to load the recovery
Make sure to do this - if you do not, it will automatically overwrite your recovery
11. Try to mount system. Be carefull what buttons you press. You can use power to cancel any menu and go back one menu
12. When system is mounted type the following in a DOS-prompt:
Code:
adb shell
cd /system/etc
mv install-recovery.sh install-recovery.old
13. Reboot and see whether you can still use your system. Reboot again with Volume- and see whether you can still access recovery (or use the following command)
Code:
adb reboot recovery
I will make this all much simpeler with a dos script, etc., as soon as the recovery correctly works.
** RECOVERY-A51x-tools.zip **
For quick usage I added the tools that I use to write recovery (adb, fastboot for writing the recovery to the device - batchfiles are included with each recovery download).
Next step... if you're willing... is root: http://forum.xda-developers.com/showthread.php?t=1729432
Regards,
Nika.

Great news

It seems that I can't flash update.zip anymore (1.011 ROM or FOTA)
I desperately need a stock recovery.img because my system is not working anymore (I've installed this Recovery, and then tried to apply the FOTA update: when it reboot to recovery the flash seems to have had some errors. On system reboot the tablet is stuck on Acer logo). I can't flash the 1.011 ROM anymore

simoneser said:
It seems that I can't flash update.zip anymore (1.011 ROM or FOTA)
I desperately need a stock recovery.img because my system is not working anymore (I've installed this Recovery, and then tried to apply the FOTA update: when it reboot to recovery the flash seems to have had some errors. On system reboot the tablet is stuck on Acer logo). I can't flash the 1.011 ROM anymore
Click to expand...
Click to collapse
See attached recovery for A510. I'm quite sure it works for A511 too.
Did you try to enter recovery using "adb reboot recovery" or by power off, power on with Volume- and wait for recovery? And did you put the 1.011 ROM (update.zip) into the external sdcard?
Flash recovery with:
1. Reboot into bootloader with:
Code:
adb reboot bootloader
2. Enter the next command from the folder with the recovery.img:
Code:
fastboot flash recovery recovery.img
By the way, I've managed to get into bootloader mode by using Volume- and switch the rotation lock back and forward at the same time...not sure whether there's another way (other than booting the device and rebooting into bootloader with the adb command).
Regards,
Nika.

simoneser said:
It seems that I can't flash update.zip anymore (1.011 ROM or FOTA)
I desperately need a stock recovery.img because my system is not working anymore (I've installed this Recovery, and then tried to apply the FOTA update: when it reboot to recovery the flash seems to have had some errors. On system reboot the tablet is stuck on Acer logo). I can't flash the 1.011 ROM anymore
Click to expand...
Click to collapse
Maybe some more details from your side are good as well.
1. Why did you install the 1.011 update.zip using the recovery? See also next question
2. Did you try install update.zip (put in external sdcard and name it update.zip!) using the regular recovery? In my case it always first tries to do update.zip and then goes into the recovery
3. Make sure the update.zip is correct on the external sdcard. Maybe copy it back and unzip to see whether it's not corrupt
Yesterday I also tried installing another zip that I created myself (to see whether I can get root somehow) and running the zip works fine, so it definitely works!
Regards,
Nika.

OP changed. It works now. It's not touch recovery, but using Volume+ and Volume- works and use power to select an option.
** WARNINGS **
1. I have not tested each function yet!
2. Step 12 below seems to have a problem. Sometimes the recovery does get corrupted and needs to be reflashed.
Believe it or not, my first version of the recovery was very close. I just had some problems due to invalid BoardConfig.mk entries which I had used from the Dees-Troy recovery source. I have now used the ones that were generated automatically when using the CWM-recovery-build-website (which generated the touch recovery but seems to have the before mentioned issues)...

nikagl said:
Maybe some more details from your side are good as well.
1. Why did you install the 1.011 update.zip using the recovery? See also next question
2. Did you try install update.zip (put in external sdcard and name it update.zip!) using the regular recovery? In my case it always first tries to do update.zip and then goes into the recovery
3. Make sure the update.zip is correct on the external sdcard. Maybe copy it back and unzip to see whether it's not corrupt
Yesterday I also tried installing another zip that I created myself (to see whether I can get root somehow) and running the zip works fine, so it definitely works!
Regards,
Nika.
Click to expand...
Click to collapse
1. I've installed the 1.011 update.zip (via stock recovery) yesterday and all went fine. Then today I saw your recovery and I flashed it. Then I saw the FOTA alert, I've pressed "Update", but when it went to flash it I saw an Android with a red triangle, and on restart the tablet is stuck on Acer logo.
2. Yes, but it goes straightly to your recovery. And if I flash 1.011 update.zip with your recovery I see only an Android robot, it seems that it can't flash it for some strange reasons. And I can't see the bottom part of the recovery, it's zoomed so I can't know what's happening.
3. It's the same .zip that yesterday worked, so it's not corrupted
Now the situation got worse..I tried some other things (other recoveries for A510 like Thor's or TWRP) but didn't get to solve. Now I think that the battery is dead, and I'm charging the tablet from 1 hour (but it's not booting anymore: nothing happens when I press power button, the screen doesn't turn on...I hope it's not definitely dead ) so I can't try the above method

simoneser said:
1. I've installed the 1.011 update.zip (via stock recovery) yesterday and all went fine. Then today I saw your recovery and I flashed it. Then I saw the FOTA alert, I've pressed "Update", but when it went to flash it I saw an Android with a red triangle, and on restart the tablet is stuck on Acer logo.
2. Yes, but it goes straightly to your recovery. And if I flash 1.011 update.zip with your recovery I see only an Android robot, it seems that it can't flash it for some strange reasons. And I can't see the bottom part of the recovery, it's zoomed so I can't know what's happening.
3. It's the same .zip that yesterday worked, so it's not corrupted
Now the situation got worse..I tried some other things (other recoveries for A510 like Thor's or TWRP) but didn't get to solve. Now I think that the battery is dead, and I'm charging the tablet from 1 hour (but it's not booting anymore: nothing happens when I press power button, the screen doesn't turn on...I hope it's not definitely dead ) so I can't try the above method
Click to expand...
Click to collapse
When you only installed the recovery as recovery you should be ok. Bricks only happen when you flash a new boot record... I've also tried TWRP's but didn't have any issues so far, other than that they didn't work.
Remember the tablet doesn't charge when USB connected (unless using the charger). In my case that's one of the reasons I had to stop yesterday
When it runs again (hopefully) try my new recovery. Get into bootloader mode with the Volume-, Poweron, screenrotation lock method and flash it with "fastboot flash recovery recovery.img". If it's locked again (which happens after flashing roms, it will then complain when you try to install the recovery) run "fastboot oem unlock", reboot with "fastboot reboot" and try again to flash the recovery.
Good luck and keep me (us) posted
Regards,
Nika.

The tab is completely dead
I've charged 100% (white LED), but the screen won't turn on.
I only noticed that if I connect the tab to pc via USB there is a new device called "APX" in "Other devices".
Checked some A500 threads and it seems APX mode is to flash bootloaders
But nothing for A510\1...so it's dead

simoneser said:
The tab is completely dead
I've charged 100% (white LED), but the screen won't turn on.
only noticed that if I connect the tab to pc via USB there is a new device called "APX" in "Other devices".
Checked some A500 threads and it seems APX mode is to flash bootloaders
But nothing for A510\1...so it's dead
Click to expand...
Click to collapse
That's horrible also for others because it will make the choice to install this a little harder... although I honestly have not had any of your trouble, and I don't really understand what happened either
But.. definitely check on google. I have seen many successful recovery from APX-mode.
Good luck and keep us posted.
Regards,
Nika.

For others, still willing to play around with the device, here's a solution to get root:
http://forum.xda-developers.com/showthread.php?t=1729432

great job
any idea if it can fit in a510?

BENETNATH said:
great job
any idea if it can fit in a510?
Click to expand...
Click to collapse
root or cwm? I guess I can build CWM for A510 too, but you have TWRP and CWM already don't you (on other forums...)?

we have root but no working recovery..
Twrp first not allow the swipe to unlock
cwn release from EB launch but only backup works, not restore.
Any help would be appreciated

BENETNATH said:
we have root but no working recovery..
Twrp first not allow the swipe to unlock
cwn release from EB launch but only backup works, not restore.
Any help would be appreciated
Click to expand...
Click to collapse
Ok... will build it as soon as I can (takes some time to setup the env). I haven't tested restore btw, need to backup some more stuff (with titanium backup) to make sure I don't loose anything
Also, make sure you have a large enough external sdcard when making backups. Remember the internal sdcard is huge and backups can cause the external to be full
One more thing, also good to know, you can always backup using DD commands:
Code:
dd if=mountpoint of=/sdcard/filename.img
And here's a list of the mountpoints in the A510/A511:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/SOS /dev/block/mmcblk0p1 /recovery
/dev/block/platform/sdhci-tegra.3/by-name/LNX /dev/block/mmcblk0p2 /boot
/dev/block/platform/sdhci-tegra.3/by-name/APP /dev/block/mmcblk0p3 /system
/dev/block/platform/sdhci-tegra.3/by-name/CAC /dev/block/mmcblk0p4 /cache
/dev/block/platform/sdhci-tegra.3/by-name/MSC /dev/block/mmcblk0p5 /misc
/dev/block/platform/sdhci-tegra.3/by-name/FLX /dev/block/mmcblk0p6 /system/vendor /flexrom /flex
/dev/block/platform/sdhci-tegra.3/by-name/AKB /dev/block/mmcblk0p7 ?
/dev/block/platform/sdhci-tegra.3/by-name/USP /dev/block/mmcblk0p8 /aboot (bootloader.blob)
/dev/block/platform/sdhci-tegra.3/by-name/DE2 /dev/block/mmcblk0p9 ?
/dev/block/platform/sdhci-tegra.3/by-name/UDA /dev/block/mmcblk0p10 /data
So you can use these commands:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/mnt/sdcard/recovery.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/LNX of=/mnt/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/APP of=/mnt/sdcard/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/CAC of=/mnt/sdcard/cache.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/MSC of=/mnt/sdcard/misc.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/FLX of=/mnt/sdcard/flexrom.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/AKB of=/mnt/sdcard/AKB.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/USP of=/mnt/sdcard/bootloader.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/DE2 of=/mnt/sdcard/DE2.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/UDA of=/mnt/sdcard/data.img

Well... I tried making a backup in my CWM and it says "Error while making a backup image of /data". Not sure yet why... will first make some dd backups, titanium backups, wipe device and will then start testing from scratch...

BENETNATH said:
we have root but no working recovery..
Twrp first not allow the swipe to unlock
cwn release from EB launch but only backup works, not restore.
Any help would be appreciated
Click to expand...
Click to collapse
Sorry for spamming, please provide a boot.img of your device/rom-version so I can use that kernel for building the recovery.

Touch is now also available, built through the builder of CyanogenMod (turned out I used the wrong recovery, I now used boot.img from the 1.011 ROM). Use the power button to go back one step (up one level in the menu).
See first post

Problem with CWM
Great work. Only problem what I have is that my device is not recognized when entering CWM. In the device manager is just an unknown device. I have installed the drivers from the Acer support. Do I need somehting else, too?

Well, my A511 is stuck at "writing recovery".
Bootloader vICS-MR1-89805f0(UnlockMode) :
sending recovery 5268kb ...
OKAY 2,063s
writing recovery ...
FAILED status malformed 0 bytes
finished. total time 503.062s
Well its still booting without problems in unlocked bootloader, but i cant flash. It just stuck there even if i try it again and again.
A511 & NV Fastboot Driver are both recognized by my system, but can it cause an error that i run windows in a VB? Need to enable USB-Debugging to run adb.
I never had problems with my Arc before using fastboot in a VB.
EDIT: Same for the touch-CWM. It just stuck at writing recovery.
adb v1.0.29

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!

Cubot King Kong custom ROM or Android go?

Hi everyone,
First post here. I purchased a Cubot Kingkong. I liked the toughness and the price. Has Android Nougat, 2gb of Ram, 16gb ROM, MT 6580 quad core processor.
What I don't like is that it's slow, in my opinion. I tried to find a custom ROM, but couldn't find one.
Do you a custom ROM that can work? Thought about Android go, but it would need to be updated to Oreo first.
Thanks for your help.

Slow? I have this phone and I find it very reasonably snappy for its specs. The MT6580 is a 2016 entry-level processor. Not any great performer and no firmware will do miracles.
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say). And the 2 Gb of RAM are enough to run it correctly. Don't think Android One would make much of a change here.
Your expectations might be too high for a sub-100€ phone.

does anyone have a scatter file or custom recovery for this phone? how did you root?

CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
WARNING: You do a factory reset! all data lost! unlocking - warranty lost!
edit: With locked bootloader, you can not flash from fastboot. BUT - Yippee! - SP Flash Tool is able to flash twrp.img for encrypted device with locked bootloader (and FRP / OEM lock!) without data loss. TWRP is then able to decrypt data with default_password. Before you unlock bootloader, flash TWRP, Back up your /data from TWRP and manually copy Internal Storage (/data/media/0) via USB-MTP (not included in TWRP Backup). Backup is not described in this Tutorial, but feel free to ask
- first you need adb and fastboot, in Windows represented as adb.exe and fastboot.exe which run in command line terminal (cmd.exe) - (for adb and fastboot Windows XP click here)
- install MediaTek MT65xx USB VCOM Preloader USB Drivers for Windows
- this phone is locked. to unlock the bootloader, enable usb-debugging:
Settings -> About Phone -> tap Build number seven (7) times
Settings -> Developer options -> OEM unlocking -> Turn on
Settings -> Developer options -> USB debugging -> Ok
WARNING: You do a factory reset! all data lost!
- connect the phone to pc and type in command console:
- confirm with Yes (Volume UP)
Code:
adb reboot bootloader
fastboot oem unlock
Phone is now in Orange State - warranty lost!
(if you wanna get rid of the waiting time flash the 'Orange State disabler' see below)
- reboot the phone:
Code:
fastboot reboot
i have created a scatter file using this very cool program WwR MTK v2.30 from Ilya Aleksandrovich
then i have ported this TWRP v3.2.2-0 from S. M. Nahid Emon Generic TWRP v3.3.1-0 from Samad Segmane meanwhile
- on Phone, download SR3-SuperSU-v2.79-SR3-20170114223742.zip flashable zip
- on PC, download the scatter file and the twrp-3-3-1-0-recovery from this thread
flash recovery with MediaTek SP Flash Tool
- in SP Flash Tool, go to Download and select the following files:
Download-Agent: MTK_AllInOne_DA.bin
Scatter-loading File: MT6580_cubot_king_kong_7081c_scatter.txt
Flash Mode: Download Only
- uncheck all checkboxes
- double click on recovery.img and select twrp.img
- press Download
- type in command console:
Code:
adb reboot bootloader
(flashing starts as soon as phone is connected in download mode)
- after successfully flashing, press and hold Volume UP, disconnect the phone, connect again, wait until you see the Orange State message appears, then release the Volume UP Button
- you can start TWRP each time from command console:
Code:
adb reboot recovery
edit: Fixed! unfortunately, when flashed and booted from recovery, touch screen is not working unless someone will fix the kernel (Patryk did with IDA Pro but this tutorial drives me crazy) - at moment you can only boot as boot.img
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Download\twrp.img"
<-- see here
- from TWRP you can now install SuperSU.zip flashable zip
- if you want install Busybox binary, download Busybox-1.29.0-YDS-UNIVERSAL.zip from github and install this flashable zip from TWRP
- if you don't like SuperSU better use Magisk i have tested successfully too, it is easy to install, no TWRP required. MediaTek SP Flash Tool has a readback mode where you can make a backup of boot.img and copy to phone (or use the one attached). Then, all you have to do is install the Magisk Manager apk and patch the boot image, then flash the patched_boot.img and you are rooted
- this phone is encrypted by default - disable encryption may increase performance
WARNING: You do a factory reset! all data lost!
first install adb and fastboot, connect the phone and unlock the bootloader,
then follow instructions for disable encryption (do everything in TWRP):
- on Phone, download Disable Force Encrypt zip and SuperSU zip files
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- copy Disable Force Encrypt zip to cache partition
Advanced -> File Manager
navigate to /data/media/0/Download
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
press Copy File
navigate to /cache
confirm blue check mark on the right bottom
Swipe to Confirm
- repeat this copy SR3-SuperSU-v2.79-SR3-20170114223742.zip to /cache
go back to main menu
- Wipe -> Format Data -> type yes
if Format Data fails, reboot TWRP and try again:
go back to main menu
- Reboot -> Bootloader
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- Wipe -> Format Data -> type yes
go back to main menu
- flash Disable Force Encrypt zip and SuperSU zip files
Install -> (Up A Level) -> /cache
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
uncheck all checkboxes
Swipe to confirm Flash
go back
select file SR3-SuperSU-v2.79-SR3-20170114223742.zip
uncheck all checkboxes
Swipe to confirm Flash
Reboot System
- finish the initial android setup assistant
- enable usb-debugging (see above unlock bootloader)
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- clear cache partition
Wipe -> Advanced Wipe -> Cache -> Swipe to Wipe
instead of SuperSU you can flash Magisk after Disable Force Encrypt. The SuperSU v2.79 is the latest release from Chainfire and it is Pro-Version. Do not update to V2.82 from Coding Code (it is the same version)
- new: 'Orange State' disabler
if you wanna get rid of the waiting time flash the 'Orange State disabler'
WARNING: experts only! do not try this if you don't know how to unbrick your device
- make a backup of lk.bin (bootloader)
- install orange_state_disabler_v0.3.zip from TWRP
- flash lk.bin from SP Flash Tool (in case you bricked your device)
--- 'Orange State' disabler v0.3 ---
##### Created by XopmoH97 : ) #####
source: orange_state_disabler_v0.3.zip

aIecxs said:
Patryk did with IDA Pro but this tutorial drives me crazy
Click to expand...
Click to collapse
Please post here:
Result of:
Code:
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms | grep tpd_i2c_probe
Dump of:
Code:
cat /proc/kallsyms

Code:
CUBOT_KING_KONG:/ # echo 0 > /proc/sys/kernel/kptr_restrict
CUBOT_KING_KONG:/ # cat /proc/sys/kernel/kptr_restrict
0
CUBOT_KING_KONG:/ # cat /proc/kallsyms | grep tpd_i2c_probe
c07d2970 t tpd_i2c_probe
CUBOT_KING_KONG:/ #
see attachment
https://drive.google.com/file/d/1YmOF9IRJhOEHLFHXgjBcBi74kvKrna0s

What is the kernel architecture? (you can check that in CPU-Z) nevermind
Try this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2340.img (updated)
If it'll not work then this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2356.img

i have tested, both not booting. i think we should just give up. maybe this method does not working for MT6580. i have requested kernel source code from Cubot but they denied

Lannig said:
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say).
Click to expand...
Click to collapse
Cubot King Kong has data mining spy app in OTA updater
https://www.xda-developers.com/report-android-phones-transmit-data-to-adups-a-chinese-firm
dont expect any firmware updates (they wont provide Oreo for sure) - better disable OTA updater instead:
Code:
pm disable --user 0 com.adups.fota
pm disable --user 0 com.adups.fota.sysoper
edit: do not update to V24 battery drain increases dramatically. Just stay at V16

Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result

LosTigeros said:
Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result
Click to expand...
Click to collapse
the code in dialer did not work, but i could enter Service Mode with MTK Engineering Mode apk. unfortunately there is no device info in Others. is there another way to check, maybe dump some file?

Use an app from google play called Device Info HW

Hey,
thanks for your support and time! I have downloaded this app and this are the results. it shows Touchscreen gt1x (i2c 1-005d)

Will it boot up after just decompressing and compressing it again? Try: twrp-3.2.2.0-cubot_king_kong_7081c-20180902-2017.img (not patched).

Thanks a lot for providing a usable TWRP, even if only one you can boot from fastboot and not flash. It serves its purpose of installing SuperSU or Magisk, good enough for me.
I'm no Android kernel wizard but I fail to see how booting from a flashed partition or in-memory through fastboot makes a difference as far as the touch driver is concerned?
EDIT : wanted to provide the requested information but it's been done already.

In gt1x its because of this:

So get_boot_mode() returns a different value depending on how TWRP was started, from the recovery partition or in-memory from fastboot? and the touchscreen driver basically disables itself in the former case? I've learned something new today, thanks for enlightening us (and I'm impressed by your knowledge of this source code BTW).
EDIT: @aIecxs: unfortunately you're right. Dr. Web has spotted them as the infamous Downloader adware. Guess I'll have to take care of these once I have root.

And what about custom ROMs? Is it possible to build Lineage OS for this device?
I'm thinking of buying one, but if there won't be any OS updates it'll be much worse than I expected.

aIecxs said:
CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Android\Backup\Cubot King Kong\twrp-3-2-2-0-recovery-for-MT6580_cubot_king_kong_7081c.img"
Click to expand...
Click to collapse
I unlocked the bootloader and tried booting the recovery using this method, but the TWRP logo shows up and the phone is stuck in a bootloop (TWRP logo shows up and disappears over and over again) .
I have tried flashing with SPFlash tool with no results. Every other recovery in this thread simply does not boot at all. What can I do to debug it? I have tried every possible method to root this phone with no success (neither TWRP nor "one click root" apps work). If anyone knows something, please help. I really want to root this phone in order to remove the malware that is preinstalled on it (adups fota). Note that I am not a developer and don't know much about these things beyond flashing custom ROMs. Thank you in advance

please do a read back for boot.img and recovery.img with SP Flash Tool

[xt1920-15] [pettyl] stock firmware rooted latest ota updates fixed + 'badkey' fix

Just for the record, Motorola phones and normally quick and easy to ROOT however this is been a right pain in the ass. No guide on here has worked properly for the UK version anyway so soon after I found a working way i thought i would do this to help anyone else....
Requirements:
unlocked bootloader
THIS ZIP FILE
extract the files and open a cmd prompt in the ADB folder or run a cmd and us 'cd C:\adb\' [or location of the unzipped adb folder]
run 'fastboot boot recovery.img'
backup the cache partition so it creates the TWRP>BACKUPS>SERIAL>ROM folder
copy the rooted rom folder to TWRP>BACKUPS>SERIAL>*here* [ please note serial stands for the serial number of device and this will vary with each person]
hit restore, system + data + boot,
when finished reboot to recovery
you are now in the stock recovery so hold the power button and tap volume down to unlock the menu then you want to wipe data factory and just use data AND NOT the personalised content as well..
then reboot
do the initial set up.
then perform 2/3 system updates [security patches i believe? from the system settings > updates]
when all this is complete, afterwards click on magisk manager and let it update. It will then give you a warning error saying the version of magisk too old.
so power off your phone and then put it back into bootloader. [hold power + vol down from a powered off state]
use fastboot boot twrp_james.img [from cmd promt inside adb folder]
when the recovery loads in the same cmd prompt type adb push Magisk-v18.1.zip /sdcard/ [or u can just copy the zip file onto the storage if it shows up on ur pc]
install magisk 18.1 and then reboot to boot loader and use fastboot flash logo logo1.bin to remove bad key error
have been in a mad rush to get this done before i go work hopefully you can understand if there are any problems just msg me

TheLastAlphaUK said:
Requirements:
unlocked bootloader
THIS ZIP FILE
Click to expand...
Click to collapse
BACKUP MIRROR OF FILE [MEGA]

Hi there, im unable to backup the cache partition (showing as 0mb in cwm) think it may have something to do with encryption.
I have my phone in a somewhat usable state by restoring cwm backup i found on xda, but when booting custom recovery it will not mount /cache ,/data etc
Would love to follow your instructions, do you have any ideas

links are dead

I have unlocked the bootloader and flashed TWRP on this phone to root.
i have not found a live link for any LineageOS or other custom rom, but root still works on stock rom.
i have saved all the necessary files on my PC so if you need help just reply or message me

[GUIDE]Universal Rom , Recovery And Kernel Flashing Guide For All Roms , Recoveries , Kernels

TWRP Flashing GUIDE (Linux-Only)
{
"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"
}
Before following this guide, make sure you have followed the rom flashing guide below the post below or xiaomi.eu rom flashing guide.
If you have followed the flashing guide then you may continue.
Hello Amigos,
You can use this guide to install other recovery than TWRP also.(Other recoveries are listed in the guide itself)
Prerequisites:
Ubuntu/Debian/Ubuntu-Based Distros:
Open terminal
Type sudo apt install adb
Once that is installed.
Type sudo apt install fastboot.
Done.
Fedora:
Open terminal.
Type sudo dnf install android-tools.
Let it install and done.
OpenSUSE:
Download this official package from here according to your version :
https://software.opensuse.org/download.html?project=hardware&package=android-tools
(Use either one the add repository and install manually or grab binary packages directly options.)
Steps to install
Then go to your custom rom download thread and check the date of rom file (In this case derpfest) and choose the recovery version closest to the release date of your rom.
Download the latest platform-tools for linux from the Android developer site and extract the zip in an easily accessible folder
Download the recovery image file
Restart your device to fastboot mode
Method 1:
Using this adb command if you have USB debugging active on your device:
adb reboot bootloader
Method 2:
- Turn off your device
- After it has completely turned off, press and hold Vol - and the Power button at the same time until the word "FASTBOOT" comes out Method 3:- Turn off your device
- Press and hold Vol - button
- Connect the USB cable (previously connected to the PC) to the device and press and hold the button until the word "FASTBOOT" comes out
4. Connect your device to the PC
5. Open a terminal window in the folder where you extracted the binaries from the archive from step 1
Easy method: Open the folder, and open a terminal in the folder itself. Terminal will open a window directly in the folder location
6. Verify that your device is recognized by fastboot using this command:
fastboot devices
If your device has been detected (a serial number followed by the word fastboot), you can continue. Otherwise, check if the drivers are installed correctly, although if you used Mi Unlock and were able to unlock the device correctly on the PC you are using, you should not have problems with that.
7. Type this command in the terminal window, but don't press Enter yet, just type it and leave a space at the end:
fastboot flash recovery_
Don't write the "_". This only indicates the space you should leave at the end.
8. Now, drag the image file (yourrecoveryhere.img) to the terminal window and drop it above the window . This will make you copy your exact location for convenience.
fastboot flash recovery "home/user/location/to/your/file/yourrecoveryhere.img""
Quotation marks are only added if the entire location has spaces.
Otherwise, it is displayed without quotation marks.
9. Press Enter and wait a few seconds . Once it shows that it is successfully flashed hold the Vol Up + Power button , once the device restarts release the power button and keep the Vol Up button pressed , after a few seconds the TTWRP logo will show , release the Vol Up button now.
DONE! You've started perfectly in recovery
This guide applies to all recoveries:
NOTE:
If your rom mentions to use a specific recovery then use that instead
To flash shrp recovery you have to extract the .img from the zip file of the recovery that you downloaded ,then flash it in the same way as told above , make sure after booting in the recovery you flash the zip file of the shrp recovery from which you extracted the .img file in the recovery itself.
DO NOT USE ORANGE FOX RECOVERY ! It is deprecated and unmaintained so it wont be updated in future .
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Download Link
TWRP Download (If your rom mentions to use NSE TWRP then use the NSE TWRP with the closest android Version to your rom's android version or else if it doesn't specifically mention any twrp version then use the normal TWRP , the one without NSE in its name, with the closest android version to your rom's android version ):
https://www.pling.com/p/1346294/
SHRP Download:
https://sourceforge.net/projects/shrp/files/Beryllium/
Enjoy !
---------------------------------------------------------------------------------------------------------------------------
TWRP Flashing Guide (Windows-Only)
Before following this guide, make sure you have followed the rom flashing guide below the post below or xiaomi.eu rom flashing guide.
If you have followed the flashing guide then you may continue.
Hello Amigos,
You can use this guide to install other recovery than TWRP also.(Other recoveries are listed in the guide itself)
Steps to install
First of all unlock bootloader of your device . Search net for more info.
After this install adb drivers from here: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/
Choose skip install for adb and install google drivers.
Connect your device in fastboot mode to your pc.
Go into device manager , right click on unrecognized android device , choose update drivers , let me pick from a list of drivers , select adb drivers , android bootloader interface and click install.
Then go to your custom rom download thread and check the date of rom file (In this case derpfest) and choose the recovery version closest to the release date of your rom.
Make sure you have the bootloader unlocked before you start. There are many guides on the internet for that.
Download the latest platform-tools from the Android developer site and extract the zip in an easily accessible folder
Download the recovery image file
Restart your device to fastboot mode
Method 1:
Using this adb command if you have USB debugging active on your device:
adb reboot bootloader
Method 2:
- Turn off your device
- After it has completely turned off, press and hold Vol - and the Power button at the same time until the word "FASTBOOT" comes out Method 3:- Turn off your device
- Press and hold Vol - button
- Connect the USB cable (previously connected to the PC) to the device and press and hold the button until the word "FASTBOOT" comes out
4. Connect your device to the PC
5. Open a cmd window in the folder where you extracted the binaries from the zip from step 1
Easy method: Open the folder, and without leaving it, type "cmd" in the address bar of the file explorer and press enter. Command promt will open a window directly in the folder location
6. Verify that your device is recognized by fastboot using this command:
fastboot devices
If your device has been detected (a serial number followed by the word fastboot), you can continue. Otherwise, check if the drivers are installed correctly, although if you used Mi Unlock and were able to unlock the device correctly on the PC you are using, you should not have problems with that.
7. Type this command in the cmd window, but don't press Enter yet, just type it and leave a space at the end:
fastboot flash recovery_
Don't write the "_". This only indicates the space you should leave at the end.
This is how it should look when you write it:
8. Now, drag the image file (yourrecoveryhere.img) to the command window and drop it above the window. This will make you copy your exact location for convenience.
- The result should be this:
Code:
fastboot flash recovery "C:\location\to\your\file\yourrecoveryhere.img"
Quotation marks are only added if the entire location has spaces.
Otherwise, it is displayed without quotation marks.
9. Press Enter and wait a few seconds . Once it shows that it is successfully flashed hold the Vol Up + Power button , once the device restarts release the power button and keep the Vol Up button pressed , after a few seconds the TWRP logo will show , release the Vol Up button now.
DONE! You've started perfectly in recovery
This guide applies to all recoveries:
NOTE:
If your rom mentions to use a specific recovery then use that instead
To flash shrp recovery you have to extract the .img from the zip file of the recovery that you downloaded ,then flash it in the same way as told above , make sure after booting in the recovery you flash the zip file of the shrp recovery from which you extracted the .img file in the recovery itself.
DO NOT USE ORANGE FOX RECOVERY ! It is deprecated and unmaintained so it wont be updated in future .
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Download Link
TWRP Download (If your rom mentions to use NSE TWRP then use the NSE TWRP with the closest android Version to your rom's android version or else if it doesn't specifically mention any twrp version then use the normal TWRP , the one without NSE in its name, with the closest android version to your rom's android version ):
Recovery For Poco F1
Team Win Recovery ProjectWht Works : * EVERYTHINGS *BUG : * You Tell Me *
www.pling.com
SHRP Download:
https://sourceforge.net/projects/shrp/files/Beryllium/
Enjoy !
---------------------------------------------------------------------------------------------------------------------------
ROM Flashing GUIDE (Windows-Only)
First of all unlock bootloader of your device . Search net for more info.
After this install adb drivers from here: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/
Choose skip install for adb and install google drivers.
Connect your device in fastboot mode to your pc.
Go into device manager , right click on unrecognized android device , choose update drivers , let me pick from a list of drivers , select adb drivers and click install.
Then go to your custom rom download thread and check the date of rom file(In this case derpfest).
Check the date of file.
Then go to xiaomifirmwareupdater.com and select rom archive and select your device.
Then MIUI downloads page will appear. type fastboot in search and look for a MIUI global version released
as the same or very close to the Custom ROM date (in this case it is this)
Download the fastboot version according to the date.
Go into the stock rom folder and double click on flash_all.bat(all data will be lost) .
Or open cmd in the folder and type flash_all.bat in cmd and hit enter.(This method allows to look for errors)
A cmd window will popup with fastboot commands automatically and after complete flashing of rom will close automatically. (approx. 20-25 mins)
Let the device boot into MIUI.
Once it boots, power it off . Then press the vol down + power button until fastboot in orange letters appear.
Then follow the twrp flashing guide from here
Then flash the ROM according to the instructions.
NOTE:
Make sure to always extract and move the stock rom folder in root of C: drive (this helps avoid flashing errors)The path should look something like this:
C:\beryllium_global_images_YourVersionhere
Then flash the stock rom.
Clean Flashing a ROM:
I hope you have followed the entire guide above before doing this step.
Reboot to recovery.
Format data.
Flash ROM file.
Wipe Dalvik Cache.
Reboot and enjoy.
Everytime you do a clean flash, you must redo all the steps above.
If a rom does not include flashing instructions, it requires a clean flash.
If a rom mentions to wipe something in advanced wipe , then wipe ONLY that and nothing else.
If rom mentions clean flash and not wiping of anything else then dont be smart to wipe anything unecessary.
If your rom mentions to use a specific recovery then use that instead
Always flash magisk after the first boot of your rom
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Do not replace the recovery or try to update recovery that comes with roms. This can brick your device
Enjoy!
---------------------------------------------------------------------------------------------------------------------------
ROM Flashing GUIDE (Linux-Only)
Prerequisites:
Ubuntu/Debian/Ubuntu-Based Distros:
Open terminal
Type sudo apt install adb
Once that is installed.
Type sudo apt install fastboot.
Done.
Fedora:
Open terminal.
Type sudo dnf install android-tools.
Let it install and done.
OpenSUSE:
Download this official package from here according to your version :
https://software.opensuse.org/download.html?project=hardware&package=android-tools
(Use either one the add repository and install manually or grab binary packages directly options.)
First of all unlock bootloader of your device . Search net for more info.
Then go to your custom rom download thread and check the date of rom file(In this case derpfest).
Check the date of file.
Then go to xiaomifirmwareupdater.com and select rom archive and select your device.
Then MIUI downloads page will appear. type fastboot in search and look for a MIUI global version released
as the same or very close to the Custom ROM date (in this case it is this)
Download the fastboot version according to the date.
Go into the stock rom folder and right click in empty area then select open terminal here then type this command:
./flash_all.sh
A terminal window will popup with fastboot commands automatically and after complete flashing of rom will close automatically. (approx. 20-25 mins)
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
Then follow the twrp flashing guide from here
Then flash the ROM according to the instructions.
NOTE:
Make sure to always extract and move the stock rom folder in root of home directory (this helps avoid flashing errors)The path should look something like this:
home\beryllium_global_images_YourVersionhere
Then flash the stock rom.
Clean Flashing a ROM:
I hope you have followed the entire guide above before doing this step.
Reboot to recovery.
Format data.
Flash ROM file.
Wipe Dalvik Cache.
Reboot and enjoy.
Everytime you do a clean flash, you must redo all the steps above.
If a rom does not include flashing instructions, it requires a clean flash.
If a rom mentions to wipe something in advanced wipe , then wipe ONLY that and nothing else.
If rom mentions clean flash and not wiping of anything else then dont be smart to wipe anything unecessary.
If your rom mentions to use a specific recovery then use that instead
Always flash magisk after the first boot of your rom
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Do not replace the recovery or try to update recovery that comes with roms. This can brick your device.
Enjoy!
---------------------------------------------------------------------------------------------------------------------------
Kernel Flashing GUIDE:
Always Flash a custom kernel after the first boot of the device in a rom which was clean flashed.
Always take a backup of your rom's boot.img incase something goes wrong.
NGK Kernel:
Download the latest nse version (if your rom is nse rom)
Then store it somewhere in your internal storage
Boot to twrp
Flash NGK NSE kernel zip
Wipe Cache Dalvik
Reboot To Syste,
NOTE:
If your rom doesnt mention if it is a nse or se rom then you may download both nse and se versions of the kernel . Then boot into twrp and flash nse version as above . If your device gets bricked , bootlooping , restart to recovery or fastboot , Then boot into recovery again and flash se version as above . After this your problem should be fixed . Still if something goes wrong , boot into recovery and flash boot.img of your rom.
LawRun Kernel:
Download the kernel version according to this index:
10-11-12 in the name here mentions the android versions supported . Android Version supported in this version of kernel is android 10 ,11,12 or android q , android r and android s.
09 , P or Pie here in the name mentions android version supported . Android Version supported in this version of kernel is android 9 or android pie.
10 or Q in the name mentions android 10 is supported.
10-2-13 in the name here mentions that android 10 to android 13 roms are supported
Store the kernel zip somewhere in your internal storage
Boot into twrp
Flash LawRun Kernel Zip
Wipe Cache Dalvik
Reboot to System
If something goes wrong , boot into recovery and flash boot.img of your rom.
NOTE:
Do check the kernel version and description at the download page of the kernel to know whether it is overclocked or not.
Genos Kernel:
Download the kernel version according to this index:
If there is nothing in the name only R21 or Rxx or r17.1re or rXXre or r16.0_evol or rXX_evol or r11_evolution or rXX_evolution or r16.1_evo or rXX_evo (xx corresponding to the version of the kernel) then it supports MIUI , OOS (Oxygen OS) , AOSP (Custom Roms).
If there is r12_non_oos or rXX_non_oos in the name (xx corresponding to the version of the kernel) then it doesnt support OOS (Oxygen OS) and only supports MIUI,AOSP(Custom Roms)
If there is r12_oos or rXX_oos or r12_evol_oos or rXX_evol_oos in the name (xx corresponding to the version of the kernel) then it only supports OOS (Oxygen OS) and dosent support MIUI,AOSP(Custom Roms)
Store the kernel zip somewhere in your internal storage
Boot into twrp
Flash Genos Kernel Zip
Wipe Cache Dalvik
Reboot to System
If something goes wrong , boot into recovery and flash boot.img of your rom.
Enjoy !
---------------------------------------------------------------------------------------------------------------------------