Develop Bugs

[ROOT] Oppo Recovery + Root method for Find 7 X9076

***
All thanks go to our awesome XDA-Developers, the developers at Oppo, and also to scumpicule for this working root method.
It doesn't require any alterations to the recovery system, just stick with the one that Oppo has provided.
This has only been tested on the X9076, it should theoretically work for other versions of the Find 7 as well, but please do this under your own discretion.
**Update: It has been reported that the newest Rom release of 1.2.2i or 1.2.3i and onward might not work with this root method! If this is the case, you will need to use these instructions from this post: http://forum.xda-developers.com/showpost.php?p=53902937&postcount=10
________________________________________________________________________________
CONTINUE with these instructions if you have Rom Version: 1.2.1i, otherwise if you have updated, click on the above link ^
INSTRUCTIONS:
Download the "Find7_ROOT4.3_bbs.oppo.cn.zip" file.
** It is also available at:
http://forum.xda-developers.com/showthread.php?t=2739102&highlight=find+7 **
Then Copy/Paste it in your phone on your root folder
Turn Off your phone
Simultaneously press the buttons ' power ' and 'volume down ' until you feel a vibration.
Your phone will reboot into recovery mode. ( Should be the OPPO recovery ! )
Select ' Choose English ' & Install zip file
Then choose the zip file that you have downloaded in step 1 & click "YES" to install.
Hit "Reboot" once everything is completed.
Go into app drawer and select the SuperSU app. Update the binary by selecting the "NORMAL" method.
Reopen SuperSU and make sure binary is okay.
Try downloading "Root Checker" or a app that requires root.
Congratulations, your device is now Rooted!!
________________________________________________________________________________
If you run into any errors, try updating the SuperSU binary again, or check under "NOTES" on the link above that scumpicule has posted.
________________________________________________________________________________
HIT THE THANKS BUTTON IF THIS HAS HELPED YOU.
Credits & Thanks
@karben @kedro @tk @Jimmy McGee
@scumpicule

installation failed unfortunately
i followed your steps and my device number is X9076

crackjas said:
installation failed unfortunately
i followed your steps and my device number is X9076
Click to expand...
Click to collapse
I'm pretty sure I used the same .zip file earlier today with the stock recovery, installation failed here too. (X9076).
Fortunately this worked perfectly: Click Here

binaryfalcon said:
I'm pretty sure I used the same .zip file earlier today with the stock recovery, installation failed here too. (X9076).
Fortunately this worked perfectly: Click Here
Click to expand...
Click to collapse
Thanks. It works!:good:

crackjas said:
installation failed unfortunately
i followed your steps and my device number is X9076
Click to expand...
Click to collapse
Were you able to get to SuperSU in the app drawer? Make sure that the binary was installed properly.
It's interesting because I was able to get it to work perfectly.
See attached photos of Root Checker.

Does not work on ColorOS 1.2.2i
I just got my Find 7 phone and after the OTA upgraded the system to 1.2.2i, when I tried to install the root file and it failed to install.

Installation Failed
No luck. Failed at the zip file installation part. Please let me know if you have any solution. Thanks. Cheers.:cyclops:

KoTP said:
No luck. Failed at the zip file installation part. Please let me know if you have any solution. Thanks. Cheers.:cyclops:
Click to expand...
Click to collapse
I'm having the same problem. When installing the zip from Oppo Recovery, it fails immediately every time. Tried both the Find7_ROOT4.3 and the Find7_GSM4.3 files. Any suggestions?

I think that after the update to 1.2.2i, the root might not work anymore. For all those that don't have it working, can you confirm if you have the 1.2.2i Rom version?
Sent from my X9076 using XDA Free mobile app

Good news!
I have found the Rooting method and instructions for Rom version 1.2.2i
It should work for every Oppo Find 7 and 7a (not confirmed) with any system (till 1.2.2i at least).
In the end system, bootloader and recovery will be intact - > stock rooted.
WORKING ON: x9077, x9076, x9006 (confirmed by #Oiler)
(NOTE):
Android SDK is required (which gives ADB and FASTBOOT files), if you have these files already on your computer, then you can just download TWRP, STOCK RECOVERY (oppo), and SUPERSU.
All the files are located below:
Preparation:
1. Phone with at least 30% battery.
2. Install Oppo drivers from "OPPO Driver" phone partition.
3. Download and unzip: AndroidSDKSlim - https://mega.co.nz/#!SEhFXbzL!Xy4PrX_NKFnAZvPaggQL-1Vw1PESzRCyqXiPrMlvWVM
4. Download: TWRP - https://mega.co.nz/#!gF0GhBzT!HGaWCcQfqr_ns2z7ZEIeeF-0KvXFliEOAFZ_Z-wHcdw and put it in "platform-tools" folder wich u get from zip above. (img file)
5. Download: Stock Recovery - https://mega.co.nz/#!rVQWXKhD!Ljy9pw_sy0VlKzxqJwuD4UoZGMwF_dOmOYWgR1mMRc4 Mod or Stock Recoveryhttp://ge.tt/2EQ5h2m1/v/0?c *2 and put it in "platform-tools" folder. (img file)
6. Download: SuperSU - http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip?retrieve_file=1 and put it on phone internal storage. (do not unpack)
Changing Recovery Menu:
1. Turn Off phone.
2. Press Volume UP + Power
3. Now u should see small discription on screen: fastboot
5. Plug the phone to PC.
4. Open command prompt inside "platform-tools" folder -> press SHIFT + Right Mouse Click, pick open command prompt here.
5. Write:
Code:
fastboot devices
6. You should see:
Code:
"your phone product code" Dartmoor
7. If you don't see your device listed, make sure drivers are installed properly. Next, write:
Code:
fastboot flash recovery twrp-x9077.img
after few second you should see OKAY. (No need to turn off phone) *1
Rooting the phone:
1. Power off the phone.
2. Hold volume DOWN and the POWER button to get into the TWRP Recovery.
3. Pick install and find the SuperSU zip file, confirm the flash.
4. Reboot the phone. (cash and davlik wipe not nessesary)
5. Phone is now rooted. (Check if there is working SuperSU app. Update binary if needed.)
Restoring stock Recovery Menu:
1. Power off the phone.
2. Press Volume UP + Power
3. Open command prompt on your PC inside "platform-tools" folder -> press SHIFT + Right Mouse Click, pick open command prompt here.
4. Write:
Code:
fastboot flash recovery x9077-official-recovery-mod.img
after few second you should see OKAY.
5. REBOOT, or turn off phone by pressing POWER for 3 sec.
6. Check Recovery Menu (Volume DOWN + Power)
____________________________________________________________________
NOTES:
*1 turning off after installing Recovery Mod is unnecessary, this is because the phone won't startup automatically into the installed Recovery Mod.
*2 Stock Recovery is provided as genuine by #Zeus (Oppo Official Staff). The other one - Stock Recovery Mod is provided by #Kedros which have removed checking of Oppo system (provides possibility to install custom files like roms or SuperSU etc.). #Kedros confirmed that OTA update is still available on it.
____________________________________________________________________
Give a Like if it helped
SOURCE: Jach0o from OPPO forums

JiraffeLeung said:
I think that after the update to 1.2.2i, the root might not work anymore. For all those that don't have it working, can you confirm if you have the 1.2.2i Rom version?
Sent from my X9076 using XDA Free mobile app
Click to expand...
Click to collapse
Yes. Mine is 1.2.2i

Same for me on the version number. 1.2.2I I was hoping the process would be easier. Oh well.

The link to the TWRP recovery is down. I tried to download it in every possible way, but I always get an error. WHen I click download once I get to MEGA, it is saying "temporary error, retrying". Please fix, thanks.
Edit - NM working now, thanks just in case you fixed it.
Edit - Rooted phone, left TWRP on if I ever go to CM11s. Had to do a few things diffrent than what you said, but got it to work. Thanks
JiraffeLeung said:
Good news!
I have found the Rooting method and instructions for Rom version 1.2.2i
It should work for every Oppo Find 7 and 7a (not confirmed) with any system (till 1.2.2i at least).
In the end system, bootloader and recovery will be intact - > stock rooted.
WORKING ON: x9077, x9076, x9006 (confirmed by #Oiler)
(NOTE):
Android SDK is required (which gives ADB and FASTBOOT files), if you have these files already on your computer, then you can just download TWRP, STOCK RECOVERY (oppo), and SUPERSU.
All the files are located below:
Preparation:
1. Phone with at least 30% battery.
2. Install Oppo drivers from "OPPO Driver" phone partition.
3. Download and unzip: AndroidSDKSlim - https://mega.co.nz/#!SEhFXbzL!Xy4PrX_NKFnAZvPaggQL-1Vw1PESzRCyqXiPrMlvWVM
4. Download: TWRP - https://mega.co.nz/#!gF0GhBzT!HGaWCcQfqr_ns2z7ZEIeeF-0KvXFliEOAFZ_Z-wHcdw and put it in "platform-tools" folder wich u get from zip above. (img file)
5. Download: Stock Recovery - https://mega.co.nz/#!rVQWXKhD!Ljy9pw_sy0VlKzxqJwuD4UoZGMwF_dOmOYWgR1mMRc4 Mod or Stock Recoveryhttp://ge.tt/2EQ5h2m1/v/0?c *2 and put it in "platform-tools" folder. (img file)
6. Download: SuperSU - http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip?retrieve_file=1 and put it on phone internal storage. (do not unpack)
Click to expand...
Click to collapse

Great stuff.
Feel free to share how you got it Rooted and which steps you took. It will help others here as well.
Sent from my X9076 using XDA Free mobile app

JiraffeLeung said:
Great stuff.
Feel free to share how you got it Rooted and which steps you took. It will help others here as well.
Sent from my X9076 using XDA Free mobile app
Click to expand...
Click to collapse
Total newbie. Could you explain preparation step 2 to me? (2. Install Oppo drivers from "OPPO Driver" phone partition.)
Will this method work with version 1.2.3i?
Many thanks.

Hey, yes the method should work for the most recent version as well. When you plug in your phone to you pc, it prompts you install the drivers from OPPO, just continue and install them.
If you don't see "Developer Options" in your settings ( in "More" ) then go into "About Phone" and click on "Build number" 5 times until you receive a message indicating that developer options is enabled.
Then plug in your phone and see if the drivers get updated. This process has been tested to work on Windows 7.
Sent from my X9076

I'm eager to try
JiraffeLeung said:
Hey, yes the method should work for the most recent version as well. When you plug in your phone to you pc, it prompts you install the drivers from OPPO, just continue and install them.
If you don't see "Developer Options" in your settings ( in "More" ) then go into "About Phone" and click on "Build number" 5 times until you receive a message indicating that developer options is enabled.
Then plug in your phone and see if the drivers get updated. This process has been tested to work on Windows 7.
Sent from my X9076
Click to expand...
Click to collapse
Thanks. Just waiting to find the time to try. I'll post the result.
Thanks again.

One more thing, you'll have to enable "USB Debugging" in developer options, then try plugging the phone in again.

Failed
JiraffeLeung said:
One more thing, you'll have to enable "USB Debugging" in developer options, then try plugging the phone in again.
Click to expand...
Click to collapse
Hi,
Thanks a lot for your help.
Though I'm pretty sure I've followed your instructions to the letter the phone would fail to install the update.SuperUser file so I can't get to get it rooted.
Any idea, suggestion, tip etc, will be much appreciated.
Thanks

How far were you able to get to? Any errors or freezing? What version of Rom are you on?

Xposed Framework Bootloop under Firmware 2.20.40.160 (551ML) - Possible Fix

Once rooted, you will try to install XPOSED Framework. You most probably need it for the Greenify + experimental like i did.
NOTES:
Use this guide if you think you want to preserve the files of your internal memory.
You have a very crappy internet connection so you can't download files larger than 500MB
You need to use your phone urgently
You have no prior experience in flashing
If you are not confident with the steps I provided, please stop. Try to search for other posts that may help you instead
As of this moment, January 13, 2016, PLEASE DON'T USE the Xposed Installer from this link as your current firmware isn't supported yet. You will face bootloops.
If you are currently in a bootloop, here is how I fix mine.
What you'll need:
1. Download and install ADB and Fastboot in your PC
2. Download One Click Root. You will need the Xoa_root.bat which is the root remover. Put this file on your adb folder which is usually at C:\adb
3. Download Asus Firmware 2.20.40.160. Just download the update version which is around 20MB only. Put this file on your adb folder which is usually at C:\adb
4. A little patience and good eyesight
What you'll do:
I will assume that you are already rooted since you want to install xposed framework
Follow the steps in order as I do not know the complications if one zip file is flash earlier than the other
STEPS:
1. You are in the Asus Boot Logo (the one with a small loading circle and not moving)
2. Boot into Bootloader (hold power + vol up)
3. Once in Bootloader, don't touch anything. You will see [Normal Boot] in green
4. Go to your folder where you put the One Click Root. Extract the zip file on a separate folder. Once extracted, open Xoa_root.bat on your Notepad. Remove this 3 lines since you cannot access ADB at this point.
adb wait-for-devices
adb reboot bootloader
sleep 30
Click to expand...
Click to collapse
5. Once removed, click Xoa_root.bat. make sure your phone is connected with your PC.
6. Wait until the removal of root is finished
7. Reboot
8. Open your phone to Bootloader again [power + volume up]
9. Once in Bootloader, go to [Recovery] by clicking the Volume down. Then press power button
10. Phone will reboot. Then you will proceed with the sleeping android with Red !
11. Hold Power Button and click Volume Up
12. Release Volume Up and you will proceed with Recovery
13. Once in Recovery, go to Sideload ADB. For extensive tutorial go to this link
14. Click Apply Update from ADB
15. On your PC, open a cmd or command prompt
16. type cd C:\adb
17. then type adb sideload NameOfZipFileUpdate.zip
18. wait until update is finished
19. choose wipe cache partition [optional]
20. Voila! your zenfone is working again - minus the root
SOME NOTES ON WHY I FOLLOWED THESE STEPS
1. ADB cannot detect your Zenfone 2 while in Asus Boot Logo. It may be detected but it will show as Error: Unauthorized blah blah blah blah. This has something to do with the RSA key of your device. Hence, you cannot issue a command to uninstall the XPOSED FRAMEWORK since you are not authorized to issue command to your phone.
2. ADB cannot detect your Z2 while in Fastboot Mode obviously. You can only issue a fastboot command from it. Hence, you cannot issue a command to uninstall the XPOSED FRAMEWORK
3. You cannot issue a custom command in ADB while in Recovery Mode. You can only issue the command ADB Sideload once you click the Apply Update via ADB.
4. If you go directly installing the Firmware Update without removing Root, you will face bootloops again.
5. You can issue an install/uninstall command via fastboot mode. Hence, the Xoa_root.bat will help you to remove root
6. The firmware update will flash all the folders that the XPOSED FRAMEWORK was intalled into so flashing the updated Firmware will fix your bootloop.
If you got question & suggestions, let me know.
---------------------------------------------------------------------------------------------------------------------------
Summary:
1. Make sure phone is connected to PC
2. On Bootloader/fastboot, open Xoa_boot.bat & remove the ADB commands
3. Run Xoa_boot.bat
4. When done, go to Recovery Mode and choose Apply Update via ADB
5. sideload Newest Firmware Update using ADB. Type adb sideload NameOfZipFileUpdate.zip
6. choose wipe cache partition [optional]
7. Done.
Click to expand...
Click to collapse
As advised by KrasCGQ, you may download the full firmware so you can have a clean system installed. I have a very slow connection so I wasn't able to test if it will work. As per his advise, you will also retain your files in internal memory.
Use full firmware instead. I don't think if you could:
1. Install OTA package over the same version as OTA package has;
2. Fix bootloops only by installing OTA package.
OTA package only patch system files to update the system. If there is mismatch blocks on the file, it'll abort.
In this scenario, it's the best to flash the whole system with full firmware. Even if it's too big, it'll give 100% clean system; without need to unroot it.
Click to expand...
Click to collapse
Vernel

I would rather flash the entire rom ... Thats simple and easy

Oh well, its up to you. At least my files are not deleted.

vernel1008 said:
Oh well, its up to you. At least my files are not deleted.
Click to expand...
Click to collapse
Even If u flash it entirely it won't delete your stuff

Great guide!
A little scratches and corrections from me:
1st:
Do the steps in the order I provided above otherwise you will not be able to fix your bootloop for the following reasons:
Click to expand...
Click to collapse
The best is to move these below the "What you'll do" sentence. Then, replace it with notes word. It looks like notes than situations where end-users couldn't be able to fix bootloops they had.
Edit: #1: And remove "...for the following reasons:" words, too.
2nd:
2. ADB cannot detect your Z2 while in Fastboot mode obviously. Hence, you cannot issue a command to uninstall the XPOSED FRAMEWORK.
Click to expand...
Click to collapse
Maybe I need to add a sentence between 1st and 2nd sentences like this:
Code:
2. ADB cannot detect your Z2 while in Fastboot mode obviously. [Color='red']You can only issue a fastboot command from it.[/color] Hence, you cannot issue a command to uninstall the XPOSED FRAMEWORK.
But, it's optional and up to you.
3rd:
Use full firmware instead. I don't think if you could:
1. Install OTA package over the same version as OTA package has;
2. Fix bootloops only by installing OTA package.
OTA package only patch system files to update the system. If there is mismatch blocks on the file, it'll abort.
In this scenario, it's the best to flash the whole system with full firmware. Even if it's too big, it'll give 100% clean system; without need to unroot it.
4th, but optional:
Wipe cache partition (and dalvik cache). It's a complementary procedure.
That's all for now. And I hope if anyone who have problems with Xposed on 2.20.40.160 firmware and even Z008 users with latest firmware could use this guide to solve their problems.
And...uh!
I can't take a look on 2.20.40.160 firmware because my Z00A is still at service center outside my hometown.
Sent from my GT-I9500

This thread saved me. Very nice guide for those who tripped at the starting line and for those who failed to backup very important information and files. Weird is i can't root it back through 1-click root.

[GUIDE] Rooting Teclast X16Plus (for both Remix OS 2.0 and Default Android 5.1)

(I wrote the 'new' version of rooting out of memory / conjecture, it should not do irreversible harm to your tablet, however, always apply common sense and proceed with caution. Caveat - I am neither a developer nor software engineer.)
'New' version of rooting procedures can be carried out with relative ease now that @krustymars has done the heavy lifting and ported TWRP to Teclast X16Plus; applies to both native android 5.1.1 and Remix 2.0.
In his write-up, it wasn't mentioned that TWRP can only be installed if X16 Plus's bootloader is 'OEM unlocked' and ROM will only boot if X16 Plus's boot image is patched (insecured), after the flashing of TWRP.
To unlock is not difficult (fastboot oem unlock), but it will also wipe /data of the ROM (making it unbootable too?). Question mark here as I am uncertain whether this action will render the ROM unbootable or not. For the sake of not doing double jobs, we assume it will.
The third condition for the ROM to first boot properly after flashing is the original recovery must be present (again I am not sure if a patched boot image will do the trick; for the same reason above, we assume it won't)
Therefore the only way out is to ensure the bootloader is not re-locked after the flashing of ROM, for us to be able to flash an effective TWRP AFTER the ROM has finished its first boot.
I believe the above are the main reasons why @stratos7 faced difficulties when intending to root via TWRP.
A simple and rudimentary step by step guide as below (you will LOSE ALL DATA in the tablet, backup all your important stuffs before proceeding):
1) Rename the ROM's original recovery.img to recovery.org. Copy krustymars' TWRP over and rename it recovery.img
This is to ensure that after the flashing, the reboot process will fail and the script will not re-lock the bootloader
2) Flash the ROM as per normal (enter DNX Fastboot by pressing vol+ vol- and power button concurrently, then use Intel Platform Flash Tool Program to flash).
3) After a successful flash, the tablet will enter recovery (TWRP) first time during reboot, and failed. It will be stuck in a boot loop (showing TWRP error).
4) Force shut it by pressing the power button for 10-15secs.
5) Enter fastboot by pressing vol- and power button concurrently.
6) Flash the orginal recovery via adb fastboot.
fastboot flash recovery recovery.img
7) Reboot normally and the ROM will load properly (1st successful boot will take a while; as long as you see the Remix OS logo flashing, all are good).
8) 10x click on Build Number to activate Developer's Menu
9) Activate USB debugging
10) Reboot into fastboot by typing
adb reboot fastboot
11) Check to ensure that bootloader is still unlocked.
12) Flash krustymars' TWRP
fastboot flash recovery TWRP_TeclastX16Plus_by_krustymars.img
13) Flash patched boot image
fastboot flash boot boot.img
14) Choose Recovery Mode, ensure X16 Plus boots into TWRP fine
15) Reboot into ROM from TWRP
16) If you are satisfied that all are fine after rebooting into the ROM, and have copied the latest downloaded SuperSU.zip flashable file into the Internal or Micro SD memory, you can either adb reboot fastboot or shutdown the tablet and vol- power button into fastboot, and then choose Recovery Mode from within fastboot to enter TWRP to flash SuperSU to get root.
Do note that you cannot update binaries within Android, you can update the SuperSU app though if a new version comes up in Play store, just not the binaries. If your binaries become outdated, you will need to flash the latest SuperSU.zip again via TWRP.
The necessary files (minus SuperSU, do grab that from Chainfire's site) - https://www.mediafire.com/?3blso8sjw4kb3e6
Once again, proceed with caution / common sense and the above shouldn't land you in any irreversible situation. All the best!
_____________________________________________________________________________________________________________________________
OLD METHOD
The below instructions for rooting Teclast X16 Plus originated from Teclast's forums. All credits go to the respective creator(s), I merely translated them to post here.
1) Download the standard rooting package from http://www.mediafire.com/download/nrez4ggzau1u8ax/Root.X16Plus.V1.zip
2) Download your corresponding edited boot image file and extracted build prop file (for either Remix OS 2.0 ver B2016062701 or Android 5.1 ver 1.07)
- for Remix OS http://www.mediafire.com/download/b6aazky2y9eqch7/Remix_OS_2.0.zip
- for Android 5.1 http://www.mediafire.com/download/zz40a8cgav385l3/android5.1.zip
3) Download and install Intel's tools and drivers in the order below - http://www.mediafire.com/download/p723or9hxip5eu8/Intel_Flash_Tools.rar
You can omit this step if these drivers are already installed.
- iSocUSB-Driver-Setup-1.2.0.exe
- IntelAndroidDrvSetup1.10.0.zip
- PhoneFlashToolLite_5.5.2.0_win32.exe
4) Download kingroot tool from below, copy the apk file to your X16 Plus and install. There is no need to run the installed app now.
5) Ensure USB debugging is switched on under developer options in your ROM
6) Unzip both the rooting package and your corresponding edited boot image and extracted build.prop files. Cut and paste the unzipped boot image and build prop files into the unzipped rooting package directory.
7) Launch command prompt and change directory to the unzipped rooting package directory
8) Connect your X16 Plus via USB
9) Type and enter - adb reboot bootloader
10) X16 Plus will reboot into fastboot mode
11) Type and enter - fastboot flash boot boot-root.img
12) Type and enter - fastboot reboot
13) X16 Plus will reboot into normal mode, wait for the bootup process to finish
14) Type and enter - su.bat
15) Run the previously install Kingroot app, Kingroot will prompt you to repair root privileges, allow it to do so.
16) Reboot your X16 Plus after the above repair and you will have full root access. If root access is still incomplete, run the above step 14) su.bat command again

Just one thanks cannot say how much grateful I am. THANKS. It work.

Thanks a lot Potatohead ! You rock !
I will try this instruction and post a feedback as soon as possible !

potatohead,
I have just finish to root my tablet. It's very easy and everything is fine.
Once again, thanks a lot ! :good:

great job !!
all are OK under win XP
Thx

Hi @potatohead , Hi @TrYkeR ,
I've just discovered a new firmware V1.07 for our X16 plus on the Teclast website (in the download section) . My tablet is running with the V1.04 version.
Do you know you to flash it, cause TeclastOTA is unable to ugrade it both with the Online mode ("undiscover new version") and the Local mode ?
Reno.

I'm using 1.07, I use a tutorial from their webside.
The big problem is download the firmware, their server sucks a lot. I use jdownload since chrome crash 2 times and do not recover the download
Firmware:
http://pan.baidu.com/s/1nvKVjnF
https://yadi.sk/d/TrUPzmkXsFrXJ (mirror)
here they talk about it:
http://techtablets.com/forum/topic/teclast-x16-plus-i-want-to-change-from-v-1-04-to-v-1-07/
I didn't find the post that I use, but was really easy, like paste the .img files into a folder, put teclast plus in "download mode", they called it diferent, and run an script (.bat)

Hi @TrYkeR,
Thanks for your prompt reply.
I searched for the tuto but I didn't find it too (I already have the V1.07 download). I do not want to do it by myself, i'm not enough confident.
If you find it...
Reno

renofaringite said:
Hi @TrYkeR,
Thanks for your prompt reply.
I searched for the tuto but I didn't find it too (I already have the V1.07 download). I do not want to do it by myself, i'm not enough confident.
If you find it...
Reno
Click to expand...
Click to collapse
I didn't found the exactly post I've use.
Was in this forum:
http://techtablets.com/forum/forums/teclast/general-discussion/page/1/

im new users teclast x16 plus .. is better remixos or android 5.1 firmware 1.0.7 (for drain battery etc..)

Hello friends,
I have the same question.... is better remixos or android 5.1 firmware 1.0.7?
Thanks a lot !!

Renew link
Potatohead, could you please post another link to root.x16plus.v1.zip?
Mediafire removed the file, nowhere else to be found (according to google...)
Thanks in advance!

So did anyone else happen to pick this up from tinydeal while they had it for $79? Not sure if it's arriving with 5.1 or Remix, but this is good to know.

Henk S. said:
Potatohead, could you please post another link to root.x16plus.v1.zip?
Mediafire removed the file, nowhere else to be found (according to google...)
Thanks in advance!
Click to expand...
Click to collapse
As you, I'm looking for this file to root my tablet.

Henk S. said:
Potatohead, could you please post another link to root.x16plus.v1.zip?
Mediafire removed the file, nowhere else to be found (according to google...)
Thanks in advance!
Click to expand...
Click to collapse
bja9 said:
As you, I'm looking for this file to root my tablet.
Click to expand...
Click to collapse
Guys, you can get it here
Link:
pan.baidu.com/s/1eSfpVW2
Password:
xc1u
---------- Post added at 05:20 AM ---------- Previous post was at 05:17 AM ----------
potatohead said:
The below instructions for rooting Teclast X16 Plus originated from Teclast's forums. All credits go to the respective creator(s), I merely translated them to post here.
...
Click to expand...
Click to collapse
I followed the instructions and flashed boot-root.img successfully, however I'm unable to run adb remount in su.bat
it says "remount of system failed: Permission denied", "remount failed"
any ideas?

btc002 said:
Guys, you can get it here
Link:
pan.baidu.com/s/1eSfpVW2
Password:
xc1u
---------- Post added at 05:20 AM ---------- Previous post was at 05:17 AM ----------
I followed the instructions and flashed boot-root.img successfully, however I'm unable to run adb remount in su.bat
it says "remount of system failed: Permission denied", "remount failed"
any ideas?
Click to expand...
Click to collapse
Tank you for the link to the file. It works fine for me !

Rooting in progress.
Did someone sucessfully installed Remix OS 3.0 or W10 ? (W10 i get acpi boot error :/)

I followed the instructions and flashed boot-root.img successfully, however I'm unable to run adb remount in su.bat
it says "remount of system failed: Permission denied", "remount failed"
any ideas?
Click to expand...
Click to collapse
me too...any ideas?
best regards

:good:

..

Dirty flash Realme UI V 2.0

I successfully dirty flashed Realme UI V 2.0 over stock android 10 without losing anything and now on Android 11.
Links available in telegram channel for Rm5p.
Anybody can do it...just dont forget to flash vbmeta with disable verity......

SShots

Do you have steps how to do it? I didnt actually get the steps in the telegram.

Kristopher28 said:
Do you have steps how to do it? I didnt actually get the steps in the telegram.
Click to expand...
Click to collapse
Yes, I will post now

Dirty flash Realme UI V 2.0. (Zero risk of losing any data if things are done as mentioned)
Things you will need.
1. A PC to use fastboot command.
Will definitely need adb and fastboot drivers installed. (folder C:/ADB)
2. You need to be on stock firmware V c.14, the latest one.
3. Custom recovery. Orangefox recovery R .11 stable version. (any other recovery latest version might work, just find the keywords mentioned)
Note: You will lose any custom recovery installed after Android 11 installation. (use system recovery and recovery ROM provided in telegram to revert back to A10 )
I am going to use Orangefox recovery as base here.
Download from telegram:
Realme UI 2.0 ozip and vbmeta.img, recovery.img (if you want-I have not installed any recovery as of now)
Download and place the vbmeta.img in your ADB folder.
Reboot phone to recovery and DO NOT WIPE anything.
Inside recovery find the entry called TERMINAL (under MENU), open it and type this first:
--------------------------------------------------------------------------------------------
setprop ro.separate.soft 19691
--------------------------------------------------------------------------------------------
xxxxxx [do not type this line]- just for your infoxxxxxxxxxxxxxxxxxxxxxxxxx
-[setprop(space)ro(dot)separate(dot)soft(space)19691]-----[do not type this line]
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Press enter
Back to ROM installation under FILES browse to UI V2 ozip.
Flash Realme UI 2.0 ozip (4fab98b6-6964-4c1d-9c5c-dcd92064ae14.ozip)
CAUTION - do not press reboot but instead just go back to MENU find option REBOOT and select reboot to BOOTLOADER or fastboot mode.
Now in your PC, press SHIFT + right mouse button on ADB folder and select OPEN COMMAND WINDOW HERE
In the command window type or paste this command
(copy below command from here and in the command window mouse-right-click and select paste) then press enter:
--------------------------------------------------------------------------------------------
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
--------------------------------------------------------------------------------------------
You should see SUCCESS message in your PC command window.
Then reboot your phone by selecting START in orangefox recovery.
I really love UI 2. Everyone should try this----safely.
Ensure your fastboot command works. I had a slight issue with fastboot on windows 7 x64 bit. I had win 7 x86 abd installation folder. Copy pasted the files from there to X64 and problem solved.
I was rooted while in A10 and magisk installed, didnt uninstall it, still had no issues. Just in case if any issue arise, I suggest you uninstall Magisk in A10 and proceed with A11 installation.

jijojamie said:
Dirty flash Realme UI V 2.0. (Zero risk of losing any data if things are done as mentioned)
Things you will need.
1. A PC to use fastboot command.
Will definitely need adb and fastboot drivers installed. (folder C:/ADB)
2. You need to be on stock firmware V c.14, the latest one.
3. Custom recovery. Orangefox recovery R .11 stable version. (any other recovery latest version might work, just find the keywords mentioned)
Note: You will lose any custom recovery installed after Android 11 installation. (use system recovery and recovery ROM provided in telegram to revert back to A10 )
I am going to use Orangefox recovery as base here.
Download from telegram:
Realme UI 2.0 ozip and vbmeta.img, recovery.img (if you want-I have not installed any recovery as of now)
Download and place the vbmeta.img in your ADB folder.
Reboot phone to recovery and DO NOT WIPE anything.
Inside recovery find the entry called TERMINAL (under MENU), open it and type this first:
--------------------------------------------------------------------------------------------
setprop ro.separate.soft 19691
--------------------------------------------------------------------------------------------
xxxxxx [do not type this line]- just for your infoxxxxxxxxxxxxxxxxxxxxxxxxx
-[setprop(space)ro(dot)separate(dot)soft(space)19691]-----[do not type this line]
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Press enter
Back to ROM installation under FILES browse to UI V2 ozip.
Flash Realme UI 2.0 ozip (4fab98b6-6964-4c1d-9c5c-dcd92064ae14.ozip)
CAUTION - do not press reboot but instead just go back to MENU find option REBOOT and select reboot to BOOTLOADER or fastboot mode.
Now in your PC, press SHIFT + right mouse button on ADB folder and select OPEN COMMAND WINDOW HERE
In the command window type or paste this command
(copy below command from here and in the command window mouse-right-click and select paste) then press enter:
--------------------------------------------------------------------------------------------
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
--------------------------------------------------------------------------------------------
You should see SUCCESS message in your PC command window.
Then reboot your phone by selecting START in orangefox recovery.
I really love UI 2. Everyone should try this----safely.
Ensure your fastboot command works. I had a slight issue with fastboot on windows 7 x64 bit. I had win 7 x86 abd installation folder. Copy pasted the files from there to X64 and problem solved.
I was rooted while in A10 and magisk installed, didnt uninstall it, still had no issues. Just in case if any issue arise, I suggest you uninstall Magisk in A10 and proceed with A11 installation.
Click to expand...
Click to collapse
Is your phone rooted?

I have actually found a bug in the rui 2.0 where phone storage can't be read i thought my phone is bricked for good, but instead i installed their rui recovery then i format my phone and it's okay now

Kristopher28 said:
I have actually found a bug in the rui 2.0 where phone storage can't be read i thought my phone is bricked for good, but instead i installed their rui recovery then i format my phone and it's okay now
Click to expand...
Click to collapse
If it was a bug, I would have encountered the same, but no. Except the windows version I used caused fastboot command error once and that too solved within minutes, I had zero errors. I was rooted on A10, but not on A11.
Please elaborate what you encountered. Maybe you did something wrong or else tips that might be helpful for others.

jijojamie said:
If it was a bug, I would have encountered the same, but no. Except the windows version I used caused fastboot command error once and that too solved within minutes, I had zero errors. I was rooted on A10, but not on A11.
Please elaborate what you encountered. Maybe you did something wrong or else tips that might be helpful for others.
Click to expand...
Click to collapse
Well in my case i did a clean wipe to avoid issues flashing the official rom , as you can see in the telegram post I did everything it shows there 1st is wiping in twrp (dalvik, data,system,cache, and vendor) then i installed the c.14 then terminal and so forth but i think there's a wrong part I've done where i dont use the commands in fastboot properly, flashing vbmeta where the disable verification is in. In my case i just flash the vbmeta with "fastboot flash vbmeta vbmeta.img" but after i understand that you have to use a specific commands for the vbmeta i flash it again with the proper codes. Then after that i reboot the phone and it works, but the problem where i dont have a storage is there.

Kristopher28 said:
Well in my case i did a clean wipe to avoid issues flashing the official rom , as you can see in the telegram post I did everything it shows there 1st is wiping in twrp (dalvik, data,system,cache, and vendor) then i installed the c.14 then terminal and so forth but i think there's a wrong part I've done where i dont use the commands in fastboot properly, flashing vbmeta where the disable verification is in. In my case i just flash the vbmeta with "fastboot flash vbmeta vbmeta.img" but after i understand that you have to use a specific commands for the vbmeta i flash it again with the proper codes. Then after that i reboot the phone and it works, but the problem where i dont have a storage is there.View attachment 5347851
Click to expand...
Click to collapse
After i saw the problem i wipe the data by using the rui 2.0 stock recovery then the problem is gone but there's another bug where a specific files cant read by the phone. I dont know if its a bug or i just flashed wrong but it cannot read it. So i decided to go back to the rui 1.0 c.14 patch. And after i got back my files is okay and ready to be use.

I dont know but the early access of 2.0 seems a little bit buggy for me

Kristopher28 said:
" but there's another bug where a specific files cant read by the phone."
Click to expand...
Click to collapse
This is what i didn't understand. You mean to say, after rom installation you got into Ui 2.0 Android 11 and you cannot access your storage inside file manager.
Or else did you mean you got into bootloop.
After custom rom installation we have to do a data format to actually boot into it.
Try doing a factory reset or wipe data.
By the way i am using rm5p Indian variant.

Flashing the vbmeta wrongly or wrong command usage May cause trouble. You may get boot destroyed msg but that can be solved by getting back to FB and installing properly the vbmeta.

jijojamie said:
After custom rom installation we have to do a data format to actually boot into it.
Try doing a factory reset or wipe data.
By the way i am using rm5p Indian variant.
Click to expand...
Click to collapse
Oh i think that's it. Because after i flash the rom and made a mistake in flashing vb meta verification. i didnt wipe the data i just reboot the system and I thought that it worked but as i discovered there's no storage. So after i saw that i flash the rui 2.0 stock recovery then wipe the data.

jijojamie said:
This is what i didn't understand. You mean to say, after rom installation you got into Ui 2.0 Android 11 and you cannot access your storage inside file manager.
Click to expand...
Click to collapse
Yeah after the rom and then the vbmeta error it got worked but as soon as i open the storage there was none. After that i installed the rui 2.0 stock recovery and then wipe the data and then restart. After that the storage seems fine, but a specific files i want to see in my sd card is nowhere to be found. The "android data" specifically.

Kristopher28 said:
Yeah after the rom and then the vbmeta error it got worked but as soon as i open the storage there was none. After that i installed the rui 2.0 stock recovery and then wipe the data and then restart. After that the storage seems fine, but a specific files i want to see in my sd card is nowhere to be found. The "android data" specifically.
Click to expand...
Click to collapse
Now, this is precise. I just tried to access the data folder through es file explorer. Then system asked to grant permission and then system file manager came up. I just granted permission in that and the data folder is listed and visible.

Please be more specific which ROM did you dirty flash?

Its ok I managed to find the telegram group and files. I will try this out on monday after i have made a backup of my phone.

Point number 2. Stock firmware latest.

Cant find the files . Which telegram channel.
Link plz

Question Find Device storage corrupted. Your device is unsafe now.( POCO F3 and Other MIUI Devices)

Last night I do have a problem with the custom rom that I have installed, because of the battery problem keeps on dropping, so I decided to go back to the official stock rom which is for global however after flashing the fastboot rom via Miflash Tool, I have a welcome message that says Find Device storage corrupted. Your device is unsafe now. I thought that I just need to activate this to the device admin, after a reboot I tried to check it out if this message if this message will still pop up, and it keeps on popping up. I have flashed the rom again and it keeps on happening.
Things that I have Tried:
So I tried to check for other ways that I could get rid of this but this doesnt work on the terminal via TWRP. "
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now".
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now". How to fix "Find Device storage corrupted. Your device is unsafe now" ? (At your own risk... I'm not responsible for damage or brick) Required : - Be rooted and...
forum.xda-developers.com
".
The one that works:
Things that you needed:
1. Download Mi Flash Tool(https://www.xiaomiflash.com/)
2. Minimal ADB and Fastboot
3. 7zip or BreeZip
4. TWRP A12(
TWRP A12.rar
drive.google.com
) if you are using other MIUI and devices and want to check it this will work then just use your twrp that is recommended for your mui device.
5. Global Rom (https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.6.0.RKHMIXM/)
warning: make sure that you are using the right rom for your device, my device that I am using is a global variant so I need to flash a global version, if you are using other MIUI device and want to check it out just download the miui that works for you must be on a later update of the rom if the latest current rom that you are working on right now didnt work.
Steps to follow.
1. Extract the Rom which you have downloaded using the 7zip or BreeZip, so for me I extracted the version 12.5.6.0 take note that this is not the latest rom but for this to work we need to be in a later update this rom is an android version 11.
2. after extracting the fastboot rom file type TGZ you will notice that the one that you extracted is on a TAR file type, and you need to extract the TAR file type for you to have the folder "alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global_62b4f5d6ca"
3. Using the Mi Flash Tool, just pick the clean all and start the flashing.
4. After flashing the rom set up the phone but do not update it.
5. On your extracted folder for the rom go to the folder that says images and look for 'persist" this is an img file. copy the persist img file and paste it on your Internal memory of your phone.
6. Turn off your phone and go to fastboot by pressing the volume down as well as the power button. You will notice that the fastboot logo is the older version since we are using an older rom.
7. Extract the TWRP A12 and you should have the disc recovery image of it, copy and paste it on your Minimal ADB and Fastboot folder and rename it "recovery".
8. While you are on the Minimal ADB Fastboot folder make sure that your phone is plug in to the usb port on your computer, click the cmd here on the Minimal ADB and Fastboot Folder and you should able to run the cmd.
9. run the following commands:
fastboot devices (then press the enter)
warning: make sure that the fastboot devices is able to see your device.
after seeing the device run this command:
fastboot boot recovery.img (then press enter)
the device should boot to the twrp if its on chinese look for settings and set it to english. we are not flashing the twrp we are just going to use it temporarily thats why we are only going to boot it to twrp recovery.
10. On your twrp, go to install, click the install image and look for your persist.img that we have copied earlier to your internal memory
you should find it on the sdcard folder. just flash and you will see that you have successfully flashed the persist image and then just reboot your phone.
After rebooting your phone you will notice that the "Find Device storage corrupted. Your device is unsafe now." will not prompt. Since I already have the current fastboot rom I have tried to flash the current fastboot rom and locked my device and fixed the problem permanently without any problem.

You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine

uvzen said:
You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine
Click to expand...
Click to collapse
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.

mizuhored said:
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.
Click to expand...
Click to collapse
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).

uvzen said:
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).
Click to expand...
Click to collapse
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.

mizuhored said:
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.
Click to expand...
Click to collapse
Could you please confirm if flashing persist.img doesn't mess up with sensor like fingerprint, l1, compass etc..? I have seen other forums talking about possibility of losing these in case perist is flashed from rom. I have this message for some time now, but all other sensors work fine, even l1 certification and saftynet. Thanks in advance.