[GUIDE]Universal Rom , Recovery And Kernel Flashing Guide For All Roms , Recoveries , Kernels - Xiaomi Poco F1 Guides, News, & Discussion

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 !
---------------------------------------------------------------------------------------------------------------------------

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!

Oukitel K6000 Plus Twrp, Root

Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted
Updates: ( All files from 4pda.ru )
Twrp Flashable zip Update to rom Version V9: https://yadi.sk/d/z8dbqfOM3Jk6w3
Twrp Flashable zip Update to rom Version V18 ( supersu integrated ) : https://yadi.sk/d/jlNSmqYN3L4xHK
I Flashed it over V9 without Wiping and it works for me lika a charm
Flashable Viper4Android : https://drive.google.com/file/d/0B5u-Eac1xV2CYUxqRmxFVkltNms/view?usp=sharing
If you dont need root you can flash V18 with SPflashtool:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
At this time there is no working twrp for V18
Custom Rom Doogee Shot (FreemeOS) : https://yadi.sk/d/YklP0V7b3LBFfV
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!
SPFlashtool FT V23:https://drive.google.com/file/d/0B1kz3pYtoOExemc0VkJtdXZRMVU/view
SPFlashtool FT V18:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
I also tried Magisk systemless on V9 and for me it works ( Working modules : Viper4android,dolby atmos,) but on V18 i cant install the new Magisk Framework and get bootloop
If Someone had Problems with SPFlashtool this is how i did it:
Install Spflashtool to C:
Copy flash file to C:
start spflashtool as Admin
select scatter file
{
"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"
}
BTW Sorry for my bad English XD
@Cheese-ass
Greetings and welcome to xda. All posts on xda must be in English, I have translated this one for you but please use google translate for all future post's
Regards
Sawdoctor
Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted
There is a way to connect a lan usb adapter?
fantastic work like a charm, but used recovery download from the german one and worked rooted oukitel k6000 plus yea
i follow every step ( iread many times before i do it)
But Phone dosent boot anymore
I got only this Message on Display :
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
But Nothing happend
When i try to flash stock rom with splash tool i got da brom error with 60002
Its bricked???
Worked fine. I had to download files from other websites, but this procedure was good.
After reboot, su was working fine in /system. I wanted to reset the device completely, and typed "fastboot oem unlock"; I thought it would wipe data. Now, phone only boots on TWRP, and it seems like the /data partition is broken. TWRP can mount /system, but not /data. Either the device node is missig, or the partition is not formated properly.
Code:
# cat /etc/fstab
/dev/block/mmcblk0p6 /nvdata ext4 rw 0 0
/dev/block/mmcblk0p8 /protect_f ext4 rw 0 0
/dev/block/mmcblk0p9 /protect_s ext4 rw 0 0
/dev/block/mmcblk0p26 /system ext4 rw 0 0
/dev/block/mmcblk0p27 /cache ext4 rw 0 0
/dev/block/dm-0 /data ext4 rw 0 0
/external_sd auto rw 0 0
/usbotg auto rw 0 0
Losetup-a gives nothing.
I tried all possible commands (adb reboot to everything), and press volume up or down ... always get back in TWRP. Can not even reach the factory menu (the one where there are tests).
After reformating /data i can reboot to bootloader (fastboot), but still not /system.
Stock ROM was looking fine; I would like to be able to keep it. I would like to avoid flashing to an other ROM.
In short, I have TWRP and flashboot, but /system launches TWRP.
I don't know how to get a working system. SPFlashTool does not seem to work with TWRP installed. TWRP does not like OUKITEL_K6000_Plus_V6.0_20170519.rar. I can't find any ZIP ROM for TWRP. And when I try individual .img files from the RAR, TWRP can install them, but it does notproduce a working phone.
I fear something could be wrong with the partition table, or at least /data. /system contains many files and this looks good.
---------- Post added at 01:30 PM ---------- Previous post was at 12:40 PM ----------
How I fixed it:
fastboot flash boot /tmp/OUKITEL_K6000_Plus_V6.0_20170519/recovery-verified.img (EDIT: this MUST be wrong, should be fastboot flash recovery /tmp/OUKITEL_K6000_Plus_V6.0_20170519/recovery-verified.img or fastboot flash boot /tmp/OUKITEL_K6000_Plus_V6.0_20170519/boot-verified.img )
then, perform again https://fvknl.pro/k6000-plus-v6-0-upgrade/
and now I have a working phone.
* Can't apply Android updates because of TWRP+SuperSU ?
Now that my phone works, and is rooted (i use the stock ROM version 6), may 19th, the system is telling me there are system updates to do. I have downloaded them (200MB), but after reboot, update fails, for obvious reasons: the update is designed to be installed by the stock recovery firmware; and that partition is overwritten by TWRP.
I was given a tip to work around this (wherer the img file is taken from the .rar archive of the stock ROM):
# fastboot boot /tmp/recovery-verified.img
and it worked: fastboot uploaded the recovery image to the phone, ran it, and that recovery firmware started to apply the update.
Started ... but failed before half of it ... PROBABLY because /system was HEAVILY modified while I asked TWRP to install UPDATE-SuperSU-v2.82-20170528234214.zip (read the installation log of SuperSU ... it alters many things).
How can I apply my android updates without erasing the whole phone each time I want to apply them ?
A: how to get the installation log, to see the failure point, and fix it manually
or
B: install the update manually without running the recovery, but extract the update file, and manually copy the new files at due place, one by one
or
C: how to undo installation of SuperSU, so that /system is in a state where the update can be applied.
I want to do this without erasing /data, or /system. I had this issue on my previous phone; since december 2014 I could not apply any Android update; so my phone is stuck to Android 4 from december 2014. There have been many changes and updates during 2015 and I could not apply them. After installing su, i had been able to perform two Android updates; updates broke after installing Xposed. I do not want my new K6000 to have the same issue; I want to find a way to apply updates. And I would like to keep the stock flavour because there are many features I would like to use (don't want to install misc ROMs).
Xposed for oukitel 6000plus root
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio
no xposed for k6000 plus
patpix75 said:
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio
Click to expand...
Click to collapse
sorry latest xposed is for sdk 25 and the latest firmware for this device is android 7.0 (Sdk 24)
patpix75 said:
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio
Click to expand...
Click to collapse
I have tried many random things; I forgot the details of it. The versions are not a problem; there are links around to download old installers. Even if latest Xposed is for Android 25, archives will let you download v24.
It also depends when you rooted your phone, and which updates you did on your ROM before rooting. Depends if you are using ROM v6, v9, or v18 ...
Also, even if Xposed is installed, it's not working properly; in particular, I wanted Xposed to NotifyClean, and this plugin could not be installed on the Xposed I have (download goes fine, but plugin complains I need reboot to activate it). So, in short, Xposed is useless for me for now. Some other plugins have installed correctly (Taskbar).
The Xposed I have NOW is version 87 by PurifyOS. ATM, Android API 24.
But I said I tried many random things, so, maybe having tried to installed other variations of Xposed by other people was important to have this one installed. I remember that at some point, trying to install this one (purify) failed, and then, worked later ... forgot why.
Error
When you try to upload a TWRP, a message pops up:
"error: cannot load 'recovery-twrp31jemini.img'"
Bootloader should be unlocked. I see a buzz when switching on "yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds"
Phone has a ROM v18
Application procedure on W10.
Does anyone find any solution?
You don't need to burn TWRP in FLASH to be able to use it. You just need to load and run it, this way:
fastboot boot recovery_TWRP-3.1.0.img
This way, if you have backup your whole phone, or downloaded and extracted a ROM, you can boot a stock recovery image:
fastboot boot /tmp/recovery-verified.img
According to your name jemini ... I thjink you have downlaoded the wrong TWRP. Boot and flash may fail if you grabbed a file for an other phone.
This should be ROM independant.
Since I rarely use TWRP, I now keep the stock recovery, and run TWRP from fastboot only when I need it; this way, stock recovery is available for Android updates.
Do you have links to ROM v18, so that I can download and install it directly, instead of having to burn v6, then update to v9 and v18 via update process ? I have issues with updates, and would like to flash directly using v18; but could not find a download link.
I got the phone today and unlocked it for root and everything.
After
Code:
fastboot oem unlock
the following showed up:
Code:
...
(bootloader) Start unlock flow
OKAY [ 14.791s]
finished. total time: 14.792s
Problem is now:
Orange state
Your device has been unlocked and can't be trust
Your device will boot in 5 seconds.
But it's not booting, just stuck at this screen.
Any help very much appreciated!
EDIT:
I was on V23 ROM which came per OTA.
EDIT-2:
I was able to flash it back to V23 with flashtool, but no root. Bootloader seems to be unlocked, the message still appears.
rom
"Custom Rom Doogee Shot (FreemeOS) :
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!""""
What do you say that this rom picks up on the oukitel k6000 plus ??
I need someone to help me my k6000 plus did not call any more after this procedure.
when I install the rom stock by flash sp this error appears
https://drive.google.com/file/d/0ByEkRDgYmbWtOXdpbngtcGJxQk0/view?usp=sharing
What do you want to do?
Flash the Stock ROM back with flashtool?
You should switch to "Download Only" and not "Firmware Upgrade".
Also the Download Agent was different when I flashed it, it was DA_PL.bin.
cojo11 said:
i follow every step ( iread many times before i do it)
But Phone dosent boot anymore
I got only this Message on Display :
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
But Nothing happend
When i try to flash stock rom with splash tool i got da brom error with 60002
Its bricked???
Click to expand...
Click to collapse
SIVAKUMAR: yes my mobile also same problem ...boot loop please help me oukitel k6000 plus MT6750T
------------- Orange State----------------
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds:crying:
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
sivakumarindia said:
SIVAKUMAR: yes my mobile also same problem ...MT6750T
------------- Orange State----------------
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds:crying:
Click to expand...
Click to collapse
SIVAKUMAR: I THINK THIS ROM DIFFERENT MT6750 AND MT6750T:crying:
---------- Post added at 11:19 AM ---------- Previous post was at 11:14 AM ----------
rolex0815 said:
i got the phone today and unlocked it for root and everything.
After
Code:
fastboot oem unlock
the following showed up:
Code:
...
(bootloader) start unlock flow
okay [ 14.791s]
finished. Total time: 14.792s
problem is now:
orange state
your device has been unlocked and can't be trust
your device will boot in 5 seconds.
but it's not booting, just stuck at this screen.
Any help very much appreciated!
Edit:
I was on v23 rom which came per ota.
Edit-2:
I was able to flash it back to v23 with flashtool, but no root. Bootloader seems to be unlocked, the message still appears.
Click to expand...
Click to collapse
sivakumar: My mobile also same condition boot loop
I got the same and this help me :
For this case, leave SP tool setting as normal. Before connect USB to device:
1. Press and hold vol +
2. Connect USB to device and hold vol + button.
3. Just release the button until you see the download process start working.
with this solution i have Flaht the v6 rom
Boot loop try this Back to STOCK ROM
Cheese-ass said:
Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted
Updates: ( All files from 4pda.ru )
Twrp Flashable zip Update to rom Version V9: https://yadi.sk/d/z8dbqfOM3Jk6w3
Twrp Flashable zip Update to rom Version V18 ( supersu integrated ) : https://yadi.sk/d/jlNSmqYN3L4xHK
I Flashed it over V9 without Wiping and it works for me lika a charm
Flashable Viper4Android : https://drive.google.com/file/d/0B5u-Eac1xV2CYUxqRmxFVkltNms/view?usp=sharing
If you dont need root you can flash V18 with SPflashtool:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
At this time there is no working twrp for V18
Custom Rom Doogee Shot (FreemeOS) : https://yadi.sk/d/YklP0V7b3LBFfV
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!
SPFlashtool FT V23:https://drive.google.com/file/d/0B1kz3pYtoOExemc0VkJtdXZRMVU/view
SPFlashtool FT V18:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
I also tried Magisk systemless on V9 and for me it works ( Working modules : Viper4android,dolby atmos,) but on V18 i cant install the new Magisk Framework and get bootloop
If Someone had Problems with SPFlashtool this is how i did it:
Install Spflashtool to C:
Copy flash file to C:
start spflashtool as Admin
select scatter file
BTW Sorry for my bad English XD
Click to expand...
Click to collapse
SIVAKUMAR INDIA: BOOT LOOP TRY THIS BACK TO STOCK ROM OUKITEL K6000 PLUS MT6750T
----------------------------ERROR BOOT LOOP -------------------------------------------
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
---------------------------TRY THIS STEPS RECOVERED STOCK ROM--------------------------
step1: Vcom+SPD+and+adb+driver+Installer+Windows+8_10
INSTALL DRIVERS
step2; SP_MDT_v3.1732 (DOWNLOAD )
EXTRACT AND RUN SP-MDT FLASH ,
SCAN ---------CONNECT MOBILE------FLASH SUCCEED----
step3: OUKITEL_K6000_Plus_V23_20170726
THIS LINK AVAILABLE OLD VERSION SP_MDT ONELY SEARCH AND DOWNLOAD NEW VERSION SP_MDT_v3.1732
LINKS: https://www.oukitel.com/latest-software-rom-for-all-oukitel-devices-48.html

[RECOVERY] TWRP 3.2.1 For C701F/DS [STABLE]

Team Win Recovery Project
It's Compatibe with Snapdragon Variants Of C7 Pro Such as C701F and C701F/DD.
If it's not working with your device or you have different model let me know. I would Build a Different Version of Recovery for your Model.
#include <std_disclaimer.h>
{
"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"
}
Special Notes:
1. READ THE GUIDE.
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However, this may not affect you if your country, European Union, for example, forces Samsung to provide hardware warranty regardless of software status.)
More Infos: https://en.m.wikipedia.org/wiki/Rooting_the_Android_operating_system
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
5. You HAVE to use newer version of Odin (>3.13) if you want to flash stock ROMs.
Download:
Galaxy C7 Pro (C701F/DS):
https://androidfilehost.com/?w=files&flid=275664
Sources:
https://github.com/TeamWin
https://github.com/aapav01/android_device_samsung_c7proltedd-twrp
Changelog:
Check #2.
Guide:
Check #3.
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
(You Can donate me Steam Gift Cards)
To contribute:
TWRP Code Review
Github pull requests will be ignored.
Change log:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
June 12, 2018 (twrp-3.2.1-0):
Fixed MTP
Fixed encryption on ASOP ROM (Samsung is unsupported)
Enable NTFS Support
Fixed Mount Issues of partition
Add Support OREO ROMs
Added EFS Backup
And MORE
Guides:
Notice: It may wipe all your data including those in internal storage.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [HOME BUTTON] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [HOME BUTTON] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [HOME BUTTON] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.
Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.
dear.......followed procedure....but... ( error is set warranty bit kernel..)...now any soln...pl reply..
thanxs with deep warm regards
I have the SM-C7018 version of this phone and, by following your guide, I was able to set up TWRP on Android 7.0 and flash GAPPS.
Thank you very much for this!
EDIT: Maybe it was just in my case, but for those of you that wish to install GAPPS on this device, keep in mind that you must not reset it to the factory conditions after installing GAPPS, as the Play services will FC once the phone boots up, and you will not be able to use it anymore. I had to re-flash the firmware. Also, I've used the Pico package, ARM x64, Android 7.0.
EDIT 2: Unfortunately, I couldn't manage to get the GApps working. The Google Framework Services would always crash when opening any google application for the first time or when trying to add the account from the Settings Menu. Anyone had any success with adding GApps on the Nougat firmware?
SPG30759 said:
dear.......followed procedure....but... ( error is set warranty bit kernel..)...now any soln...pl reply..
thanxs with deep warm regards
Click to expand...
Click to collapse
it's normal on samsung devices
aapav01 said:
it's normal on samsung devices
Click to expand...
Click to collapse
Hi, I did the steps you mentioned, but after completion I checked with Root Checker app it says "Root not installed properly". Do you know why?
My device is C7010. Can it use your TWRP as well?
c7 PRO c7018
Will this tprw work with c7018 model? and with c7018 + oreo?
aapav01 said:
Team Win Recovery Project
It's Compatibe with Snapdragon Variants Of C7 Pro Such as C701F and C701F/DD.
If it's not working with your device or you have different model let me know. I would Build a Different Version of Recovery for your Model.
#include <std_disclaimer.h>
Special Notes:
1. READ THE GUIDE.
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However, this may not affect you if your country, European Union, for example, forces Samsung to provide hardware warranty regardless of software status.)
More Infos: https://en.m.wikipedia.org/wiki/Rooting_the_Android_operating_system
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
5. You HAVE to use newer version of Odin (>3.13) if you want to flash stock ROMs.
Download:
Galaxy C7 Pro (C701F/DS):
https://androidfilehost.com/?w=files&flid=275664
Sources:
https://github.com/TeamWin
https://github.com/aapav01/android_device_samsung_c7proltedd-twrp
Changelog:
Check #2.
Guide:
Check #3.
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
(You Can donate me Steam Gift Cards)
To contribute:
TWRP Code Review
Github pull requests will be ignored.
Click to expand...
Click to collapse
Can I use this to port TWRP for 10.or G
Specs of 10.or G
Snap 626
4gb ram
Also pls reply what hardware needs to be same for porting.
And does kernel matter in Porting these images???
Thanx in advance
@aapav01 plz make twrp for C7000 oreo
tnks
a7 2015
Can build for me this same rom its humble request
Thank you!
c7 pro twrp for oreo
hi
i have series gapps problem .
can you plz make one for c7 pro sm-c7018 oreo .
twrp has no version for it .
baseband version: c7018zmu2cri1
buildnumber: r16nw.c7018zmu2cri1.
2018/09/14
ty
phone stucked at samsung logo and set bit : kernal
I followed same step and my phone isnt booting now
stucked at samsung logo and yellow top right says set bit: kernal
please help
try this
ashokrathi said:
I followed same step and my phone isnt booting now
stucked at samsung logo and yellow top right says set bit: kernal
please help
Click to expand...
Click to collapse
try pressing vol down and power at same time time then phone goes to power off then switch from vol down to vol up holding the power button now as soon as screen display starts leave both buttons it will now boot into twrp recovery go to wipe format data and type yes then flash no dm verity and magisk as per instruction given
My device is C7010. Can it use your TWRP as well?
aapav01 said:
Guides:
Notice: It may wipe all your data including those in internal storage.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [HOME BUTTON] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [HOME BUTTON] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [HOME BUTTON] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.
Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.
Click to expand...
Click to collapse
I want to try this but my phone (c701f-ds) never boots into download mode or recovery mode consistently. I bricked the phone trying to root it throught the magisk app, using this very version of twrp. I got it back. I was able to flash the original stock oreo rom using odin
But to get the phone back I didn't go through the (blue screen) Download Mode, Instaed I got into the recovery envoronment (very hit and miss) then chose to reboot into bootloader mode, where I saw it yellow at the top of the screen "download mode" but not the blue screen of the usual download mode.
In this bootloader/download mode environment I connected the phone to the laptop. Odin recognised the phone and I loaded the stock rom into AP, and the appropriate files into the other boxes (I used Home_CSC instead of CSS, essentila for getting VOLTE to work). It flashed successfully. (a status bar appeared on the phone which corresponded to the download process)
But that wasn't the method that anyone else recommended.
I would try flashing the twrp tar file in the same way but there is no guarentee I could get into the twrp environment since holding [VOLUME UP] + [HOME BUTTON] + [POWER] doesn't always, or even often, get me into recovery mode.
I can use adb to reboot into recovery and from there get into bootloader/download mode but not again if the os doesnt load
Any advice?
And you say that eventhough the phone is already in download mode, that after you connect the phone to the pc where odin is loaded and has initialized the tar file, you have to press and hold [VOLUME UP] + [HOME BUTTON] + [POWER] and then press start on Odin. Then continue to hold these 3 buttons till the phone reboots into twrp. Why not just press start on odin without holding these 3 buttons? If the phone just shuts off after flashing twrp, would turning it on by holding those 3 buttons bring the phone (except mine perhaps) into twrp recovery?
What happens if the phone doesn't boot into recovery/twrp? Is it bricked? And if it does boot into the os, could you use adb to get into twrp?
I am being cautious due to the difficulty in getting the phone back after bricking it last time and because there is no guarentee that an ke combos will definitely get my phone into recovery or download mode.
Help is appreciated.

CUBOT X19 [ TWRP 3.3.1 + Root ]

{
"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"
}
TWRP 3.3.1 + Root
This topic is the result of work mehanik6 (4PDA) my greetings to him
Tested on Android 9
1 - Remember that everything you do, you do at your own risk
2 - to install TWRP, we will have to unlock the bootloader, all data will be erased, Your device becomes out of warranty
3 - the you need to be installed adb driver For connecting your device to a computer (15 Second ADB Installer v1.5.3.zip)
How to install Best Android ADB Driver on your computer
How to Install Google USB Driver for Windows | ADB and FastBoot
installation
- download the archive delete_verity_key.zip without unpacking put on the sdcard (Attached file) delete_verity_key.zip (130.56 KB)
- download file Fix_vendor.zip without unpacking on the sdcard (Attached file) Fix_vendor.zip (347.64 KB)
- download file Magisk-v20.1.zip without unpacking on the sdcard (Attached file) Magisk-v20.1.zip (5.22 MB)
- download file adb.zip. unzip to your computer desktop adb.zip (22.02 MB)
- Enable developer options in Android
GO to Settings > Swipe down and tap on About Phone Keep tapping on the build number for 7 times
-Enable the USB debugging option
GO to Settings >System -> Developer options on your Android device and enable the USB debugging option.
-Enable “OEM Unlocking”
GO to Settings > Developer options on your Android device and enable the OEM Unlocking option.
when you plug the device into an PC, it will prompt you to allow USB debugging (as seen in the screenshot below).
- allow unlocking of the bootloader
- Decompress a folder adb.zip
- Open a command prompt inside a folder adb. right mouse button l menu, select to open a command window
- copy and paste command [adb devices] (Check Device by Sending below Command)
Example of making sure to connect to the phone
1
Code:
adb devices
2
Code:
adb reboot-bootloader
3
Code:
fastboot devices
If the device does not recognize the phone, it is on "fastboot" android adb interface
Installing [Google ADB Drivers] To Windows 7/8/8.1/10/XP/Vista
- download file Google ADB Drivers.zip
- unlock the bootloader
4
Code:
fastboot flashing unlock
- on the screen text appears, press the Volume + button (all data will be erased)
Attention
The following files(fileFix_vendor.zip+delete_verity_key.zip+Magisk-v20.1.zip) must be placed in an external card, because all phone data will be deleted
Then long press buttons (Power) to turn off the phone
- The bootloader is unlocked. You should see the Orange State (text).
Then turn ON the phone
one more time
- Enable developer options in Android
GO to Settings > Swipe down and tap on About Phone Keep tapping on the build number for 7 times
-Enable the USB debugging option
GO to Settings >System -> Developer options on your Android device and enable the USB debugging option.
when you plug the device into an PC, it will prompt you to allow USB debugging (as seen in the screenshot below).
- Open a command prompt inside a folder adb. right mouse button l menu, select to open a command window
1
Code:
adb devices
2
Code:
adb reboot-bootloader
3
Code:
fastboot devices
- Sew vbmeta.img (the error does not pay attention)
4
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5
Code:
fastboot flash recovery recovery.img
-After completing:
*Long press buttons (Power) to turn off the phone And quickly Boot into TWRP (buttons Power + Volume Up )
By pressing the volume up selects: recovery mode
and pressing the( volume down) to start TWRP
Changes will not be saved language and settings in (TWRP) Only after all stages have been completed
- Back to the section mount
And put a tick next to all sections on which are placed
- go to the section wipe
- click Format the Data
- In the terminal, Type "yes" and confirm (format action) by click the check mark in the lower right corner
- then you need to reboot again in TWRP
Boot into twrp buttons (Power + Volume Up )
By pressing the volume up selects: recovery mode
and pressing the( volume down) to start TWRP​one more time​
- Go to the section mount
And put a tick next to all sections on which are placed
Back to install
- Flash archive delete_verity_key.zip
- Flash archive Fix_vendor.zip
- Flash archive Magisk-v20.1.zip (Data again to not encrypt)
- Restart the phone
Like everything, use
NEXT
[GUIDE] CUBOT X19​
I just rooted my phone and this guide was very helpful.
- After formatting your phone, boot into recovery through TWRP as my phone keeps bringing up the "no command" error screen if I use "Vol Up + Power"
- When that happens, hold power button for 10 secs, your phone will either turn off or reboot, flash TWRP again and continue.
Successfully Installed TWRP 3.3.1 with SP tool what is did After selecting scatter file from stock firmware i replaced the stock recovery and edit the partition size in the scatter fie for recovery and changed the default path from sp tool default was Recovery-verified i switch it to the Recovery.img that i replaced it with.
Having issues: At the top of the screen its written in red letters as overlay: "TEE key not write Google key not write"
I already applied the "fix Orange state" fix.
Any ideas?
Actually I am using a CubotX19 S and finally I went back to stock rom. That fixed the issue.
However, when I flashed Stockrom I noticed at loading of MT6763 scatterfile, that there are 2 sections having "tee" in their names (see screenshot).
Maybe it would be enough to just flash one or both of those two sections.
I did not do any further research, but maybe this hint os of help for others .
BTW: my screenshot says "Download only" in the Droplist. Actually I flashed using "Firmware Upgrade"
best regards,
bul
where do i get the vbmeta file from?
brezzz said:
where do i get the vbmeta file from?
Click to expand...
Click to collapse
recovery.img + vbmeta.img in folder adb.zip above
or https://www.mediafire.com/file/owuv9h2444w264y/adb.zip/file
flashing vbmeta failed "this partition doesnt exist"
kusti420 said:
flashing vbmeta failed "this partition doesnt exist"
Click to expand...
Click to collapse
Try the following at your own risk ​
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
karim.a said:
Try the following at your own risk ​
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
View attachment 5188523
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
hmm, i tried it just like it said, still cant see a vbmeta partition
karim.a said:
Try the following at your own risk ​
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
View attachment 5188523
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
also i saw someone say that this vbmeta is android 9 thing, but cubot x19 came with android 8.1, should it even have the vbmeta partition? how could i create that partition?
My friend kusti420, follow the instructions below, including upgrading the phone to Android 9 . If your phone has a android 8
Try the following at your own risk​
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
For one reason or another, my serial number of my phone is 0123456789ABCDEF and I can't flash the recovery, neither boot from it, nor flash the modified firmware with it.
I tried to flash vbmeta, but it did not do anything.
chartek1 said:
For one reason or another, my serial number of my phone is 0123456789ABCDEF and I can't flash the recovery, neither boot from it, nor flash the modified firmware with it.
Click to expand...
Click to collapse
How to find phones serial number or IMEI number​
Step 1. Open the Phone app.
Step 2. Dial *#06# on the keypad.
Step 3. Details about your devices IMEI and serial number will automatically appear on the screen.
chartek1 said:
I tried to flash vbmeta, but it did not do anything.
Click to expand...
Click to collapse
format your phone
flash your phone if model number CUBOT X19
the latest firmware for CUBOT X19 upgrade 2020-04-21
select : format all + download
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
karim.a said:
format your phone
flash your phone if model number CUBOT X19
the latest firmware for CUBOT X19 upgrade 2020-04-21
select : format all + download
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
Trash, description on two pages, but no link to TWRP, much to do, nothing to get from./translate/
user132 said:
Successfully Installed TWRP 3.3.1 with SP tool what is did After selecting scatter file from stock firmware i replaced the stock recovery and edit the partition size in the scatter fie for recovery and changed the default path from sp tool default was Recovery-verified i switch it to the Recovery.img that i replaced it with.
Click to expand...
Click to collapse
How do i adjust the file?
karim.a said:
format your phone
flash your phone if model number CUBOT X19
the latest firmware for CUBOT X19 upgrade 2020-04-21
select : format all + download
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
Should I tick the preloader? I have heared that it might brick the device.
chartek1 said:
Should I tick the preloader? I have heared that it might brick the device.
Click to expand...
Click to collapse
I tick the preloader? NO​If the current Firmware (Stock ROM) for the phone is android 9​​​Instructions to Install​Charge the device battery up to 50%​
Make sure you follow and download all the required files and flash tools on your PC.
Open the flash tool exe file to open the SP Flash Tool User Interface
Tap on the Download option and load both the download agent and the scatter text file in the scatter-loading section.
Once you load the file, click the Download button
To start the upgrade process of stock ROM on your Cubot X19, you need to turn off your device and hold the Volume Down and Volume Up key together and Connect your Phone to PC/Laptop using USB Cable (Keep the Volume Down and Volume Up button until your computer detects the phone.)
When the phone connects, your device will start upgrading the stock firmware
Wait for a few minutes, If you see a green button on your flash tool which means the upgrading process has been completed.
That’s it! You can reboot your Cubot X19

MiUi 12 Global Pure Stock Rom with few Mods (OrangeFox/TWRP) Backup

MiUi 12 Global Pure Stock Rom with few Mods (OrangeFox/TWRP) Backup
{
"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"
}
Description​
Few Things Added In Stock MiUi 12
. Inbuild GCam Support
. WiFi + Hotspot will work at same time
. No Root By Default But You Can Install Magisk For ROOT
Instructions
FLASHING TWRP
1. Download TWRP Recovery LINK
2. Download & Extract Fastboot + ADB Folder LINK
3. Copy the TWRP Recovery file inside Fastboot + ADB Folder.
4. Switch off the phone, after that press & hold [Volume Down & Power Button] now ur Bootloader Screen will appear
5. Connect phone to PC.
6. Open the Fastboot + ADB Folder after that open file "Cmd Here".
7. Type "fastboot flash recovery TWRP" & press "tab Key then Enter Key".
8. After flashing is complete, Disconnect your Phone.
9. then press [Volume up & Power Button] to boot into TWRP Recovery
10. Now u have successfully flashed TWRP Recovery in ur Phone...
FLASHING OrangeFox
1. Download OrangeFox Recovery LINK
2. Download & Extract Fastboot + ADB Folder LINK
3. Switch off the phone, after that press & hold [Volume Down & Power Button] now ur Bootloader Screen will appear
4. Connect phone to PC.
5. Open the Fastboot + ADB Folder after that open file "Cmd Here".
6. Type "fastboot boot recovery" & press "tab Key then Enter Key".
7. Now dont disconnect your data cable
8. Your phone will boot into custom recovery mode now copy your OrangeFox zip File from your PC to Mobile.
9. after that flash OrangeFox zip file from mobile
10. after flashing Automatically OrangeFox Will ReBoot into Recovery Mode
11. Now u have successfully flashed OrangeFox Recovery in ur Phone.....
RESTORE TWRP/OrangeFox BACK FILES :
1. After flashing Custom Recovery
2. Download TWRP/OrangeFox Backup file GDrive LINK
3. Extract in PC then COPY the file in SD Card
4. Go to Recovery click on "Wipe" then "advanced wipe"
5. then select [all except sd card & Otg] after that swipe to wipe
6. click on Select Storage , select MicroSD Card
7. now u will see a folder of MiUi 12 Backup..........click on it
8. select swipe to RESTORE
9. click on Reboot System
10. NOW your system will boot in Miui 12.....enjoy
Download GCam apk - LINK
How to Root
1. Download and install as apk file Magisk v22.1 = LINK
Version Information
System Version : MiUi Global 12.0.2.0 Stable
ROM OS Version: Android 9 Pie
Based On: Stock MiUi 12 OS
Status: Stable
1. Orangefox Recovery - Folder name (Fox)
2. TWRP Recovery - Folder name (TWRP)
rename the main folder according to your installed recovery after extracting the RAR file
reserved.
Does it support atmos+viper?
rbarts said:
Does it support atmos+viper?
Click to expand...
Click to collapse
Yeah but by default its a pure stock rom with no root but if you want root access flash magisk
gourabpa said:
by default its a pure stock rom with no root but if you want root access flash magisk
Click to expand...
Click to collapse
Thanks for the info. I'm looking for a new ROM because my Magisk installed in my device is outdated and I want to try other options.
All links are Updated
req
when update again bro?
Can share the screen shots of the rom
How does it actually look
Be Careful !!!
Windows Defender report :
Trojan:AndroidOS/BoxerSms in : system.ext4.win001->(GZip)->/system/priv-app/SharedStorageBackup/SharedStorageBackup.apk and vendor.ext4.win->(GZip)->/overlay/CmccMmsTheme/CmccMmsRes.apk
and Trojan:AndroidOS/AndroRat in : system.ext4.win001->(GZip)->/system/priv-app/dpmserviceapp/dpmserviceapp.apk
ferreol-fr said:
Be Careful !!!
Windows Defender report :
Trojan:AndroidOS/BoxerSms in : system.ext4.win001->(GZip)->/system/priv-app/SharedStorageBackup/SharedStorageBackup.apk and vendor.ext4.win->(GZip)->/overlay/CmccMmsTheme/CmccMmsRes.apk
and Trojan:AndroidOS/AndroRat in : system.ext4.win001->(GZip)->/system/priv-app/dpmserviceapp/dpmserviceapp.apk
Click to expand...
Click to collapse
Lmao windows defender... that still exist lool what a joke, wasted .... try some serious AV... I don't say there isn't a virus, but defender is a bad joke..
You make my day loool.
To be sure put that files on virustotal...
drnightshadow said:
Lmao windows defender... that still exist lool what a joke, wasted .... try some serious AV... I don't say there isn't a virus, but defender is a bad joke..
You make my day loool.
To be sure put that files on virustotal...
Click to expand...
Click to collapse
Hello,
Sorry for my suspicious report. (but glad to make you loool)
Your are right Windows Defender is the only engine on virustotal to detect this files :cyclops:
Defender is not so bad for Windows files, but I agree it's really not a reference with android files
I've also verifed dpmserviceapp.apk on my xiaomi.eu 11.2 rom with the same result.
Will I be able able to revert to miui 10.3.2 if I restore this backup. Additionally, once restore rom, can I restore apps and data from previous miui version?
gourabpa said:
MiUi 11 Global Pure Stock Rom with few Mods (OrangeFox/TWRP) Backup
Description​
Few Things Added In Stock MiUi 11
. Inbuild GCam Support
. WiFi + Hotspot will work at same time
. No Root By Default But You Can Install Magisk For ROOT
Instructions
FLASHING TWRP
1. Download TWRP Recovery LINK
2. Download & Extract Fastboot + ADB Folder LINK
3. Copy the TWRP Recovery file inside Fastboot + ADB Folder.
4. Switch off the phone, after that press & hold [Volume Down & Power Button] now ur Bootloader Screen will appear
5. Connect phone to PC.
6. Open the Fastboot + ADB Folder after that open file "Cmd Here".
7. Type "fastboot flash recovery TWRP" & press "tab Key then Enter Key".
8. After flashing is complete, Disconnect your Phone.
9. then press [Volume up & Power Button] to boot into TWRP Recovery
10. Now u have successfully flashed TWRP Recovery in ur Phone...
FLASHING OrangeFox
1. Download OrangeFox Recovery LINK
2. Download & Extract Fastboot + ADB Folder LINK
3. Switch off the phone, after that press & hold [Volume Down & Power Button] now ur Bootloader Screen will appear
4. Connect phone to PC.
5. Open the Fastboot + ADB Folder after that open file "Cmd Here".
6. Type "fastboot boot recovery" & press "tab Key then Enter Key".
7. Now dont disconnect your data cable
8. Your phone will boot into custom recovery mode now copy your OrangeFox zip File from your PC to Mobile.
9. after that flash OrangeFox zip file from mobile
10. after flashing Automatically OrangeFox Will ReBoot into Recovery Mode
11. Now u have successfully flashed OrangeFox Recovery in ur Phone.....
RESTORE TWRP/OrangeFox BACK FILES :
1. After flashing Custom Recovery
2. Download TWRP Backup file MEGA LINK
3. Download OrangeFox Backup file MEGA LINK
3. Extract in PC then COPY the file in SD Card
4. Go to Recovery click on "Wipe" then "advanced wipe"
5. then select [all except sd card & Otg] after that swipe to wipe
6. after that click on Select Storage , select MicroSD Card
7. now u will see a folder of MiUi 11 Global Stock Rom Backup..........click on it
8. after that select swipe to RESTORE
9. after that click on Reboot System
10. NOW your system will boot in Miui 11.....enjoy
How to Root
1. Download and Flash Magisk v20.3 from custom Recovery LINK
2. Install as apk after flashing (Magisk.zip) Magisk Manager v7.5.1 = LINK
Version Information
System Version : MiUi Global 11.0.3 Stable
ROM OS Version: Andriod 9 Pie
Based On: Stock MiUi 11 OS
Status: Stable
Click to expand...
Click to collapse
Any chance you still have a copy of that 3.3.1-3 TWRP? All links on XDA/Google seem to be dead for that particular build, and it was the only one that didn't have the stupid Pin/Pattern, Pattern/Pin bug. Even the latest TWRP (3.5.1) still has that bug.
Thanks.
Thread Updated...
MiUi Updated Version from 11 to 12.0.2.0
all the link are added in 1st Page
New MiUi 12 Backup Uploaded You can try it
1. Orangefox Recovery - Folder name (Fox)
2. TWRP Recovery - Folder name (TWRP)
rename the main folder according to your installed recovery after extracting the RAR file
mik101 said:
Any chance you still have a copy of that 3.3.1-3 TWRP? All links on XDA/Google seem to be dead for that particular build, and it was the only one that didn't have the stupid Pin/Pattern, Pattern/Pin bug. Even the latest TWRP (3.5.1) still has that bug.
Thanks.
Click to expand...
Click to collapse
what is this rom ?
AhmedAlaa01 said:
what is this rom ?
Click to expand...
Click to collapse
Its a MiUi 12 Global Stock ROM TWRP/Orangefox recovery backup file....
Wifi + hotspot duel stanby & gcam support added
Updated to MiUi 12 last build
Skylark1790 said:
when update again bro?
Click to expand...
Click to collapse
gourabpa said:
Its a MiUi 12 Global Stock ROM TWRP/Orangefox recovery backup file....
Wifi + hotspot duel stanby & gcam support added
Click to expand...
Click to collapse
can you tell me how enable gcam , i enable "persist.camera.HAL3.enabled " but it doesn't work good

Categories

Resources