This tool is out of date. See the main R9S thread for an updated tool by Wu Xianlin which gives you an improved TWRP recovery and access to more ROMs.
Original post is below for historical purposes only.
Oppo R9S (Chinese version) TWRP installation tool
Only works on Chinese OS release 005 which can be downloaded here and flashed in stock recovery.
Earlier versions will not work, nor will later versions. It has to be this specific version.
P̶r̶o̶b̶a̶b̶l̶y̶ doesn't work on international editions either.
DOWNLOAD - R9S_TWRP.zip - V1.01
DOWNLOAD - R9S_TWRP.zip - V1.0
Changelog
1.01 - Tweaked timings to try and improve success rate
1.01 - Changed how text is output to hopefully improve appearance on Windows 7
This script uses an exploit by Chinese developer Wu Xianlin to gain temp root, then it flashes his TWRP build that works on the R9S despite the locked bootloader.
From there you can attempt to perma-root your phone, install a custom ROM etc. etc.
Thanks to the following XDA members, without whom this would not have been possible:
jacksmack
celoxocis
{
"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"
}
Antivirus issues
Some AV's may complain about this file containing a Trojan. They are technically correct. It's called "dirtycow" and is being used in the wild to hack into Linux systems. It cannot affect Windows systems, but I use it to hack a linux-based system (your phone)
If your AV refuses to let my script run you will have to disable it temporarily. Feel free to read through my script (root1.bat) to check what it is doing.
Useful things to flash in TWRP
CyanogenMod13 - by Wu Xianlin
Stock Recovery - by Wu Xianlin
GApps (ARM64) - by opengapps.org
Updated basebands, ripped from ColorOS
Use these only if you have issues with phone/GPS/etc. after installing CM. Otherwise leave alone.
[2017-01-11 v0180] - released ROM (China) - by me!
[2017-01-24 v1470] - ALPHA ROM (China) - by me!
Note: The version number on basebands stays the same, but the MD5s are different. No idea what has changed, but they work!
Unbrick instructions:
Does not work in Windows 10. Tested working in Windows 7
Download this unbrick package
Install the quallcommmtkdriver package
Run daanav-enabler as administrator
Run msmdownloadtool as administrator
Click through any timeout error you get
Click on the titlebar of MSMDownloadTool and press F6 to enable the options
Fully power down your phone by holding vol-, vol+ and power for 10 seconds
Hold vol- and vol+ while connecting the USB cable (use the stock Oppo cable)
MSM should now show your phone.
Press F5 to decide what to flash. For the first attempt choose "All except userdata".
Click the start button.
After 5 minutes your phone should reboot into ColorOS.
If ColorOS hangs on boot, then repeat the above staps and this time flash all, including userdata. This will wipe your photos etc. sorry!
This will leave you on V004 of the OS. You will need to upgrade to 005 before attempting to root again.
Can I request a version of this that stops at permanent rooting? Unless you think there would be a problem with the fact that I intend on using it on a r9s plus.
Or a link to what I maybe overlooked, in case it already exists.
Unfortunately this program doesn't perma-root. It gains a temp root and uses that to flash TWRP. TWRP can then be used to flash a custom ROM or a rooting tool.
It also doesn't unlock the bootloader. Wu Xianlin somehow managed to make a version of TWRP that the locked bootloader is happy with!
however if you edit root1.bat and scroll down to line 181. Change it from:
Code:
type root3.txt | adb shell /data/local/tmp/root2.sh
to:
Code:
adb shell /data/local/tmp/root2.sh
Then the script will just drop you to a root shell. Unfortunately you are then on your own as to how you get perma-root.
I have no idea whether this method will work on the R9SPlus. In theory it should do but I've not tried it. I won't be held responsible if you brick your phone and probably won't be able to help, though you should be able to do a three-finger reboot and then boot into recovery and reflash ColorOS.
Optional modifications you can make that will make the script neater:
You can also remove lines 178 and 179
Code:
echo Copying TWRP
adb push r9s-twrp-3.0.2.0-20170107.img /sdcard/twrp.img
and change line 184 from
Code:
pause
REM ---- CHINESE TWRP HELP ----
to
Code:
pause
exit
REM ---- CHINESE TWRP HELP ----
I will take your "I have no idea if this will work fo r9s+" at face value and try to be patient for something more certain, thanks for your contribution nonetheless
I saw the translation you posted and am a bit depressed Wu recommended to return the phone...
Oppo make amazing hardware but terrible software that is never updated. I used to be ok with this because they actively encouraged rooting and custom ROMs but this change in attitude from them makes it very hard to recommend the phone.
I would be interested to know if this exploit does gain root on the Plus. In theory it should work, and there's also a decent chance that TWRP will too as the hardware is very similar, but will require someone very brave/stupid to try it
BTW. Anyone who is going to try this on the Plus. Ensure you have a flashable .ozip of a working ColorOS (full install, not OTA) saved to internal storage as the stock Oppo recovery is a POS that doesn't provide ADB, MTP or USB.
If you end up wrecking your OS and don't have that image in place ready to flash from recovery you are screwed.
Likewise do not flash TWRP until you are sure that your OS is still bootable, and also take a dump of the stock recovery first! (and post it in the other thread as it's bloody useful to have!)
Sent from my OPPO R9s using XDA Labs
Hi the Unbrick pack RAR is corrupted and can not unzip.
Also there is Trojan in DOWNLOAD - R9S_TWRP.zip - V1.0 - Dirtycow file and the NOD Antivirus is deleting this file.
Please advice how to proceed ?
NOD is correctly detecting that this is a hacking tool using a well known exploit (dirtycow).
Since you actually want to do that, you're going to have to disable NOD until you're done.
Sent from my OPPO R9s using XDA Labs
Lum_UK said:
NOD is correctly detecting that this is a hacking tool using a well known exploit (dirtycow).
Since you actually want to do that, you're going to have to disable NOD until you're done.
Sent from my OPPO R9s using XDA Labs
Click to expand...
Click to collapse
Hi I got to somewhere but I am stuck now...
Please check the pic and advice how to install the CyangenMode. (I have uploaded the pic in your thread in Oppo Community forum please check it there because I am new here and can not post with external links..)
Sorry for the inconvenience. Looks like I am few steps away to finish the job but something is missing...
Goro1234’s image: http://s27.postimg.org/8usudi9g3/IMG_20170207_133854.jpg
You need to do a wipe data/cache/dalvik as CM won't install on top of incompatible data.
Note that this will wipe your installed apps, settings, app data, saved games etc. but will not wipe your photos, music, downloads or anything else saved to internal storage.
You may wish to take a backup from within TWRP first. Apps like Titanium Backup and Nandroid Manager are reasonably good at restoring apps and data from a TWRP backup.
Also don't forget to install GApps
Sent from my OPPO R9s using XDA Labs
For the unbrick package you need 7-Zip to extract it.
Lum_UK said:
`Also don't forget to install GAaps`
Hi I am on Cyanogen now !!! Thanks for the help. Can you please tell me now which is the correct gapps version for our device. I have installed random one which does not make connection with google. I have tried to install ARM 64, but cant flash because systems says that is incompatible... Thanks
Click to expand...
Click to collapse
Select ARM64, android 6.0 and whichever variant you like (I recommend the Pico version)
Sent from my OPPO R9s using XDA Labs
Sorry for the English, I made a mess with the phone, after unlocking everything, and held the phone for several days with CM13, I saw that GPS was not working, so vovelo return to the origin, but now I can not installing Stock Recovery more to put the stock rom, I tried to do unbrick, but when I press start of msmdownloadtool, the program stops and closes. If some kind soul gives me some advice. Done everything under win 7 reset. Thank you so much Gianfranco.
GPS should be working. I'm using it all the time on CM13 as my phone is my satnav.
Maybe wipe and reflash, or try one of the baseband updates?
Sent from my OPPO R9s using XDA Labs
Now, the problem is more to do so that I can not leave,
I installed through the files Stock TWRP Recovery as a boot, and I hand the boot source and installing the original rom, after the reboot remains on oppo screen. what can I do. Thank you so much Gianfranco.
hold all three buttons for 10 seconds to forceibly power off the phone and then try to boot to recovery.
If you get the Oppo recovery then try to do a factory reset and then flash the stock ROM,
if you get TWRP then try to flash Cyanogen.
If you can't do either then you're going to have to run the unbrick tool. Do you have another PC you can try it on?
Thanks, but I have tried various solutions, when I install the boot ROM from stock, is successful, the reboot hangs installation applications. I wanted to know if you can other software for unlocking. Thank you very much for giving me some advice, thanks ancora.Gianfranco.
Related
Hello :laugh:,
I have an ZTE Grand Memo V9815 N5 Flagship Phone APQ8064 Quad Core 2G 16G Android 4.1.2 5.7inch from China, and i was wandering if anyone allready has found something to Root this device.
I have tried the standard superoneclick, but thats not working and crashes when in progress.:silly:
I want to root it, cause i need Google play on it. I have installed Google Services/Google Framework, and i can setup an account in Google Play, but after the account stuff Google Framework/Google Services/Youtube service/Google Play crashes constantly
So i contacted ZTE for support, but there is no Rom, or any update for this phone.
I googled some, and at some websites they wrote to Root the device, so its not crashing anymore.
Please help me to get Root on my phone, so i can install Google Play Store.
Thanks in Advance !!
Same problem
Hello Reppo,
I have the same problem. I am not able to root this fantastic phone ... I need to install Google Play on ti .. :crying:
Please advise me if you will find the rooting procedure for ZTE N5 Grand Memo.
Ciao!
Alfredo
alphredo said:
Hello Reppo,
I have the same problem. I am not able to root this fantastic phone ... I need to install Google Play on ti .. :crying:
Please advise me if you will find the rooting procedure for ZTE N5 Grand Memo.
Ciao!
Alfredo
Click to expand...
Click to collapse
I've root Grand memo. What's your specific problems? Did you install unofficial recovery and ADB drive?
HI 123sharon456,
I have no idea how to do it.
I just need procedure and also advice about where to find all the requested files.
Can you give me some advice?
Thanks!
123sharon456 said:
I've root Grand memo. What's your specific problems? Did you install unofficial recovery and ADB drive?
Click to expand...
Click to collapse
alphredo said:
HI 123sharon456,
I have no idea how to do it.
I just need procedure and also advice about where to find all the requested files.
Can you give me some advice?
Thanks!
Click to expand...
Click to collapse
1. Install driver
{
"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"
}
Check your device manager. If it looks like the image follows, it means your ADB driver does not been installed successful.
This is the successful status.
If you can't install ADB driver by automatic installation. You can install ZTE Join Me(mobile phone manager software), it will intall ADB.
2. Recovery
Extract it into any directory.
Click flashrecovery.cmd (antepenultimate) to this interface:
It will run automatically and reboot your phone. If not, reboot your phone and computer, then try again.
If everything is fine, try to enter the recovery.
Shutdown the phone, pressing on volume key by right hand + pressing on power key by left hand. When you see the screen light up and feel the vibration, release the power button. KEEP PRESS ON VOLUME KEY until you see the recovery interface.
-upgrade your system from SD card
-use slideload to upgrade your system
-wipe out data/restore the factory data
-wipe out cache
-backup and restore
-mount and storage
-advanced options
-shutdown
Choose
-wipe out data/restore the factory data
-wipe out cache
and
-upgrade your system from SD card (copy this ROOT ROM in your SD card, and choose it in this step http://dl.xda-developers.com/attach...832b60d/5192289d/1/9/6/1/1/6/8/rootforN52.zip)
LOOK LUCK
123sharon456 said:
1. Install driver
Check your device manager. If it looks like the image follows, it means your ADB driver does not been installed successful.
This is the successful status.
If you can't install ADB driver by automatic installation. You can install ZTE Join Me(mobile phone manager software), it will intall ADB.
2. Recovery
Extract it into any directory.
Click flashrecovery.cmd (antepenultimate) to this interface:
It will run automatically and reboot your phone. If not, reboot your phone and computer, then try again.
If everything is fine, try to enter the recovery.
Shutdown the phone, pressing on volume key by right hand + pressing on power key by left hand. When you see the screen light up and feel the vibration, release the power button. KEEP PRESS ON VOLUME KEY until you see the recovery interface.
-upgrade your system from SD card
-use slideload to upgrade your system
-wipe out data/restore the factory data
-wipe out cache
-backup and restore
-mount and storage
-advanced options
-shutdown
Choose
-wipe out data/restore the factory data
-wipe out cache
and
-upgrade your system from SD card (copy this ROOT ROM in your SD card, and choose it in this step http://dl.xda-developers.com/attach...832b60d/5192289d/1/9/6/1/1/6/8/rootforN52.zip)
LOOK LUCK
Click to expand...
Click to collapse
Thanks A lot,
Im gonna try this, and will tell here about if it worked or not
Reppo1911 said:
Thanks A lot,
Im gonna try this, and will tell here about if it worked or not
Click to expand...
Click to collapse
Dear Sharon,
The link is broken for the RootforN52
Can you please put a good link on it ?
shrewd supllice
Reppo1911 said:
Thanks A lot,
Im gonna try this, and will tell here about if it worked or not
Click to expand...
Click to collapse
Im stucked at the Flashrecovery thing.
How do i open this adb folder, cause i dont have that one.
I have the ZTE Joinme installed, and now what?
Where do i find these recovery files, which i need to extract.
Please help me out, im kinda noobie in this stuff
Reppo1911 said:
Thanks A lot,
Im gonna try this, and will tell here about if it worked or not
Click to expand...
Click to collapse
where can i download unofficial recovery for grand memo
visarya said:
where can i download unofficial recovery for grand memo
Click to expand...
Click to collapse
you can find it here:
needrom.com/mobile/zte-n5/[/url]
I cant set the full link cause i did not more then 10 posts
Good!
took weeks breaking my head up late at night from surfing the net to find some way to rooting this stunning smartphone. But I've been stuck due to no knowledge of ADB commands and of course having no Chinese idea, since supposedly there's an app that automatically Root the phone, but I can not make it work.
Having my disability, I share with you all the information and resources I've got to give you hope someone knows the correct usage.
And it is a shame that a HIGH terminal does not remove all power performance not ROOT and therefore can not set you GAPPS
Web Recovery 4.2.2 ROM and instructions: w w w needrom com/mobile/zte-n5/ (Requires registration, but I am uploading files to my Dropbox so it is not necessary)
* Chinese Subforum: w w w zhongxingfans com/forum-560-1.html (Registration is required, I can spend my MP user you're needed)
* Chinese Tutorial on previous subforum: w w w zhongxingfans com/thread-51487-1-1.html
* Other Chinese Subforum: w w w popfen com/forum.php?mod=forumdisplay&fid=65&filter=typeid&typeid=167 (Same as above, I have also user)
*Another one: www gaojiquan com/forum-ZTEN5-1.html (I'm not registered, I think)
* DropBox folder with everything I've coseguido, even assuming the mobile program that automatically Root: w w w dropbox com/sh/ap64zaexa5sa8op/we9TXWX
* Future tutorials: h t tp : // es.ready2root.com/info/grand-memo-n5 (Now is empty)
[/ LIST]
Hope you have better luck than me, and if they have some known to speak Chinese would be helpful to us.
NOTE: These is a google traducction from a another post from a spanish forum, if you have problems with the links, you can go to the original post here: www . htcmania . com/showthread.php?t=664705
Found this on a chinese website, its not for root, but for better performance of the ZTE N5 :laugh:
Just translate the page with Google Chrome standard translator, and you will understand.
(im still not able to set full links )
link for website:
h t t p ://sjbbs. zol .com.cn/164/642_1635239 .html
link for download:
h t t p://devicedownload .zte. com.cn/cn/UpLoadFiles/product/0/242/soft/2013052815114637 .zip
Im still having the issue that i cannot install GOOGLE PLAY, anyone here that solved that problem???
I appreciate your help
Greets,
Reppo1911
How did you install cwm on zte v9815 please?
CCR
Reppo1911 said:
Thanks A lot,
Im gonna try this, and will tell here about if it worked or not
Click to expand...
Click to collapse
Hello,
Is there some lock in EU phones whereas at the end of the aforementioned process the phone does shutdown and remains, the terminal is waiting for device..., rebooting in system recovery cwm is still missing and every sideload fails, any clue? People on the River would be Happy to give from a remote location.
hxxp://postimg.org/image/42tvojjvh/
ps: all I obtain is this->hxxp://postimg.org/image/blbyq6khf/332da320/
Freedom and Democracy shouldn't mean being jailed within some digital cell while paying for acquiring it: Amendments.
Can anyone give detailed directions?
I just got the device. I tried installing a google play store apk (tried a few different versions) all installed but none work.
How can I install the play store? Do I have to root the device? If so, are there detailed (English) instructions somewhere?
Someone knows if the Mobileuncle MTK Tools can root zte v5? I need to find a" one-click" app...
Partial success
I have installed the rom from needrom for the N5 android v 4.2.2. Took a while to flash the recovery, which is in chainese (driver issues). But still have serious connections issues:
The 3G network disconnects on restart and takes forever to reconnect. Wifi doesn't work! Built in keyboard is awful and also... chainese!
But it is rooted and has the google apps.
Does any one recommend a better combination of recovery and rom?
This is my wife's phone and she is having a lot of trouble with it.
Monsanto
yanay zimran said:
I have installed the rom from needrom for the N5 android v 4.2.2. Took a while to flash the recovery, which is in chainese (driver issues). But still have serious connections issues:
The 3G network disconnects on restart and takes forever to reconnect. Wifi doesn't work! Built in keyboard is awful and also... chainese!
But it is rooted and has the google apps.
Does any one recommend a better combination of recovery and rom?
This is my wife's phone and she is having a lot of trouble with it.
Click to expand...
Click to collapse
How do you flash a Custom rom we cannot even install cwm?
I wrote the Valorous Chinese told me to ask somebody elsee hence I sorry under God shall wish China a Genuine Bankruptcy for denying us Private Property, Communism is a mental disease our Lord should Treat. hxxp://en.wikipedia.org/wiki/Orange,_Vaucluse
How to?
JPWK said:
How do you flash a Custom rom we cannot even install cwm?
I wrote the Valorous Chinese told me to ask somebody elsee hence I sorry under God shall wish China a Genuine Bankruptcy for denying us Private Property, Communism is a mental disease our Lord should Treat. hxxp://en.wikipedia.org/wiki/Orange,_Vaucluse
Click to expand...
Click to collapse
I Followed downloaded the files from the dropbox posted upper in this thread. and followd the instructions in the previous page. Pay special attention to installing the driver for the divice. As soon as it reboots into bootloader it requires another driver.
Also if you must not restart the phone before flashing the rom otherwise it won't last.
perfect aarmewdd um in slack
yanay zimran said:
I Followed downloaded the files from the dropbox posted upper in this thread. and followd the instructions in the previous page. Pay special attention to installing the driver for the divice. As soon as it reboots into bootloader it requires another driver.
Also if you must not restart the phone before flashing the rom otherwise it won't last.
Click to expand...
Click to collapse
I am very Confident Folks bould ask ya about this driver thus they can rush downloading it like gold diggers to the root Saint Cloud very much
postimg.org/image/n6bj2rgyd/
Hibook-ToolBox
For first - to write my english is bad, bad, very bad... But I understand english
I allowed myself to write a few batch files to help newcomers, as well as other users, under common title "Hibook-Toolbox".
Русскоязычная версия: http://4pda.ru/forum/index.php?s=&showtopic=741766&view=findpost&p=49156807
It allows you to:
Unlock the new tablet Bootloader.
Unprotect system partition from changing (remove "Verity Boot").
Install TWRP-recovery ver-2.8.7.0, which I have ported to this tablet.
Get the correct ROOT in the right way.
Flash custom firmware (which do not have to wait long, I think so)
And other…. I will add if still need to be.
Attention! Whatever you do, you do it at your own risk!
Download (needrom.com): http://www.needrom.com/download/unlocktwrproot/
Preparation:
Unzip the archive to PC, but try not to use special characters or folder names with space in the paths to files. Better way is unzip to a folder in the root of drive C: or D:
Turn on ADB-debugging: "Settings"-"About Tablet" >-> Taps under the item "build number" until the caption appears "you became a developer"-> Return one step back-> enter the item for developers "-> Enable" USB debugging ".
Connect the device to the PC.
Install the Intel driver IntelAndroidDrvSetup1.10.0.exe
Usage:
1.Unlock_Bootloader.bat - Run first. It will unlock the bootloader. Carefully follow the prescriptions of the script and on the screen of the tablet. ATTENTION! All settings, programs, as well as all data on internal SDCard will be destroyed! Data on external MicroSD and Windows will not suffer. After unlocking the device will reboot in factory recovery, which does not display anything (stupidly black screen with backlight), the process may take up to 10 minutes (I'm shocked, but it's true), then the device will reboot in Android pristine clean.
2.Unlock_Verity-boot.bat - Run second. It will unlocking the System partition to can be changed. Carefully follow the prescriptions of the script and on the screen of the tablet. The device will reboot. Data on external MicroSD and Windows will not suffer. After all unlock actions, be sure to enter the option for developers and turn ON the item "Factory unlock".
3.Outside_boot-TWRP-recovery.bat - (It is optional. For obtain ROOT access). The device will be rebooted into the temporary session of TWRP-recovery, to Internal sdcard will be placed UPDATE-SuperSU.zip - install it using TWRP. Previously, you can make TWRP backup (recommended!).
4.Flash-TWRP-recovery.bat - (It is optional) TWRP-recovery will be permanently flashed into the Tablet. (Not recommended! Some time firmware will update, TWRP cannot install OTA-update)
5.Flash-ORIGINAL-recovery.bat - (It is optional) Flash back to the original Recovery.
ADB_shell.bat - Just a comfortable CMD-window for ADB-debugging and work with Android Shell.
Flash-Custom_FW.bat – My flasher to flash custom firmware, which I am sure will appear in future.
Useful console commands (ADB_shell.bat):
ADB reboot bootloader - reboot to FastbootDroidboot (flashing) mode
ADB reboot recovery - reboot to TWRP or native Recovery mode.
ADB root – restart ADB-debug service as ROOT.
ADB remount - remounting Android system partition to write (you need root-adb mode see adb root)
ADB shell - run Android-console (ash) through which you can run Linux-scripts, internal system commands, etc.
fastboot boot * *.img – run user-compiled boot.img or recovery.img
fastboot reboot – reboot to system from DroidbootFastboot (flashing) mode.
fastboot flash [boot, recovery, system, data] [boot, recovery, system, data]. img - In DroidbootFastboot mode, It will flash specific image to specific partition, example: fastboot flash system c:\Custom_FW\system.img - will flash only system.img to Android system partition.
PS. Under any circumstances, when using TWRP, never do not wipe system partition! Also make sure the TWRP-settings option "Use rm-R instead of formatting" is ON and never leave it. The fact of the matter is that "Verity Boot" marked System partition itself. Withing format the label disappears - the tablet won't boot to Android! This problem can be solved, but why You would make a problem?
If You like may work, buy me a coffee. Please :|
Hibook-Toolbox was updated 06/04/2016
Nice work, it is really great to see the android side of the hibook 10 has root. this is an excellent tablet and I am ordering it as of now.
I hope you and others will continue working with this tablet, as android n would be great on here.
Thanks. :good:
Hi ! Can you share what tools you use for modding TWRP for HiBook and what files you have changed ? I need to do the same for Chuwi Hi10 DualOS, based on the same hardware, i want to port your TWRP on it..
I have installed root too whit this tutorial. It works perfect. If someone is interested in modding whit kernel or custom Rom i have accsess to all partitions from ubuntu on the tablet. Please ask me if you interested in somthink. The stock Rom and kernel are not the best.
Sent from my Samsung Galaxy S III using XDA Labs
kostyamat said:
Hibook-Toolbox was updated 06/04/2016
Click to expand...
Click to collapse
It works also on Chuwi Hibook pro??
Hi,
I´ve got my brandnew CHUWI HiBook Pro 2 in 1 Ultrabook Tablet PC (10") today. Could you pls confirm that your toolbox is suitable for this tablet as well?
I won´t brick it on the very first day using wrong software ...
many thanks in advance
cheers Andreas
I think its OK. It works perfekt for me. But if you not sure for yourself than dont do it. Thats all we can say. If you dont try it you dont See if it works or not. Its your choice. And dont get panic if the first vor second try dont work. I dont know how many trys i used and some times i was realy scared about my chuwi. But than i realized that i made something wrong vor forget somthing. After all the work and the shocks my chuwi worked perfect. But if you dont try it you dont know if it works.
Sent from my Samsung Galaxy S III using XDA Labs
Hi, it shows the links are broken, can you please update new links
thanks
I confirm successful rooting for chuwi hibook pro, too.
I want to ask... Do we update supersu from Play store??
Hi man
I will proceed later today to do this.
2 questions...
1) how did you compile the TWRP for our needs? or is it a general one?
2) regarding custom fw, is there cyanogen/remixos 3/anything else based on android 7 available??
Thanks
regards
Luca
Confirm, root sucess for chuwi hibook pro.
Thank you
Root works fine, thank you
I had to install SuperSU.zip from the SuperSU Website.
Reason: Binaries couldn't be updatet.
One problem with TWRP left.
Touch input isn't working well.
Seemes that the touch mask is shifted.
I have to connect a mouse via OTG
[EDIT]
I found another posting with newer TWRP Version (3.0.2.0).
Problem Solved.
modaco.com/forums/topic/377883-recovery-twrp-302-0-for-chuwi-vi10-plus-hi10-plus-hi10-pro-hibook-pro/
Hello,
After launching the first .bat file my tablet does not automatically restart. It restarts when I click the power button, and start when the tablet starts normally without data loss as specify
I attached pictures of my tablet after restarts automatically after launching the .bat file
What to do ? I am stuck.
{
"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"
}
It`s ok, I didn`t have reboot neither, nor data loss.
Hey guys, new Chuwi Hi10 Pro owner here. I just want to make sure this will work with the build number for my tablet. It's currently running 5.1.1-B2016081102, Remix OS version 2.0. I'm pretty familiar with rooting Android devices, but I still like to make sure I'm following the proper steps before attempting anything. Thanks in advance.
Nippylicious said:
Root works fine, thank you
I had to install SuperSU.zip from the SuperSU Website.
Reason: Binaries couldn't be updatet.
One problem with TWRP left.
Touch input isn't working well.
Seemes that the touch mask is shifted.
I have to connect a mouse via OTG
[EDIT]
I found another posting with newer TWRP Version (3.0.2.0).
Problem Solved.
modaco.com/forums/topic/377883-recovery-twrp-302-0-for-chuwi-vi10-plus-hi10-plus-hi10-pro-hibook-pro/
Click to expand...
Click to collapse
you have hibook or hibook pro? because modaco only have twrp for hibook pro.. is it compatible for hibook also?
eltdesign said:
you have hibook or hibook pro? because modaco only have twrp for hibook pro.. is it compatible for hibook also?
Click to expand...
Click to collapse
I have the HiBook Pro
DISCLAIMER: all operations descripted here should be done *only* by trained & expert guys... as every "hacking" operations, they involve the risk of soft/hard bricking your device making it unusable temporary or permanently. I will not be responsable in any way for it. So, pay attention and, if not sure, simply don't do it.
WARNING #1: this is a fast guide describing needed steps and providing needed files only for expert guys. It is *not*suitable* for newbies who need detailed instructions on how to install drivers, programs, flash partitions, etc...
WARNING #2: on this phone there are (strangely...) close ties between boot.img and recovery.img content. This involves that changing contents of recovery.img can produce bootloop and changing contents of boot.img can prevent to access recovery too, creating a soft brick condition. I don't know exactly why, BUT you are warned.
WARNING #3: the procedure and files provided are *only* for ROM1 firmware version 14 of 13 Aug 2016. It is indicated as OUKITEL_C4_V14.0_20160813 in "About phone" and as t637d-oq-s08-fdd3m-hd-64g8g-sd internally. If you are on a differently indicated version and/or release date, *don't*even*think* about trying to apply the provided files: bootloops and (at least) soft bricks are easy coming, expecially because of warning #2...
WARNING #4: all provided files are in .zip format only due to forum rules and limitations. They *all* need to be *unpacked* before use them.
CREDITS: this TWRP recovery has been compiled by Jemmini on 4PDA forum. Since of the Russian only language of that forum and the very hard way to subscribe on it for not Russians (needed to download files too...), I'm reporting it here with more explanations and my hints & experiences too...
Said that... Let's start! :highfive:
IF (and *only* if...) your firmware version is reported as OUKITEL_C4_V14.0_20160813 in your phone, these are the steps to follow:
- unlock your bootloader (no special code needed, just enable the apposite option slider in Developers section of Settings and unlock it by the standard fastboot command in fastload mode... you need adb, fastboot and adb/fastboot drivers installed in your pc obviously )
Please remember that, as ever, unlocking your bootloader will factory reset your phone (and void your warranty...), so take it in proper account....
- using SP Flash Tool (recent versions since of the new MT6737 used in C4... tested one is the v.5.1644, just Google for it) just flash the provided twrp-c4.img (by Jemmini on 4PDA) selecting "Download only" on top, using the provided scatter file and selecting only the recovery row (browsing to twrp-c4.img file). Then press Download button and connect your phone in OFF status. If all was OK and you have MTK drivers properly installed (Google for them... search for MT6737 drivers. To test them just try to connect your phone to PC as storage to check if it is properly seen...), you should see a green checking sign "v" on top of SP Flash tool.
If nothing happens, try to reinstall drivers and/or doublecheck your phone is in OFF status when connected.
- don't try to boot to system now. It simply doesn't anyway.
For some unknown reason connected to warning #2, flashing twrp introduces a bootloop (soft brick...) on this phone.
Nothing to be worried of anyway: systemless rooting will fix it!
To root simply flash by TWRP (yes, you need to enable /system modification on first twrp boot...) SuperSU v.2.78 "standard" version in zip format (just Google for it...).
For standard is intended the released one, not SRx or "forced to system" one... (tested version is SuperSU-v2.78-201609011115.zip) .
Just remember that, since of unability to boot system before flashing SuperSU, its zip have to be already on your device before flashing TWRP. Otherwise you can use a microSD card to flash from it...
If you do all fine you now have your rooted & TWRP 3.0.2-x provided Oukitel C4!!! :highfive:
If you are in a bootloop condition you aren't able to fix, just turn off your phone and, ever using SP Flash Tool in the same way, simply reflashing stock boot.img and recovery.img (both provided as zipped-to-to-be-unzipped attachment for... emergency reasons ).
After, if you want, you can install Xposed (in system mode) or busybox by app (it will be automatically installed in systemless mode since of supersu installation method...).
Don't even try to install Magisk v.9 instead: it will not work and will produce a soft brick (with no recovery access too...) that will requires a boot.img and recovery.img reflashing to be solved (with all this procedure to be redone one more time...).
This said... if you have questions... I'm here to answer them. Otherwise... have a nice time with your TWRP provided and systemless Rooted Oukitel C4!!! :fingers-crossed:
Reserved. :silly:
Can you please provide the 4PDA forum link of TWRP for this phone? Thanks for your post anyways
[email protected] said:
Can you please provide the 4PDA forum link of TWRP for this phone? Thanks for your post anyways
Click to expand...
Click to collapse
Added in OP. Don't expect to find more anyway...
I can confirm that this TWRP build also works fine with the newest OUKITEL_C4_V17.0_20161124 Firmware. Important: before flashing TWRP disable your boot lock code, otherwise you will softbrick your device.
Entec do you have an 4pda Account? If yes it would be really awesome if you could add the second TWRP recovery image for oukitel phones with the Rxx_xxxx ROM to OP.
EDIT:
I successfully installed XPOSED on my C4! This rocks the **** out of an 50 EUR budget phone!
Hello thank you for your information, could you provide us also TWRP for 32bits version (R06), I have tried to download from de forum but file is not avalaible.
regards
salvarez01 said:
Hello thank you for your information, could you provide us also TWRP for 32bits version (R06), I have tried to download from de forum but file is not avalaible.
regards
Click to expand...
Click to collapse
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
[email protected] said:
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
Click to expand...
Click to collapse
Hello thank you I have flashed 64 bits Rom and updated to V17, now all OK with TWRP and SuperSU.
Seam 64 bits version more slow than R06, but OK.
Thanks.
Hello I have tried to use native sip editing the files in /system/etc/permissions but the option is not available in phone menu. Someone know how to activate?
Enviado desde mi Redmi Note 4 mediante Tapatalk
[email protected] said:
Entec do you have an 4pda Account? If yes it would be really awesome if you could add the second TWRP recovery image for oukitel phones with the Rxx_xxxx ROM to OP.
Click to expand...
Click to collapse
[email protected] said:
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
Click to expand...
Click to collapse
I managed to create an account on 4pda.ru and downloaded twrp for all firmware versions!
Files are attached!
Use twrp_recovery_C4_V.zip if your phone uses the OUKITEL_C4_VXX.X_XXXXXXXX firmware (Tested with OUKITEL_C4_V17.0_20161124)
Use twrp_recovery_R0x.zip if your phone uses the R0X_XXXXXX firmware. (Tested with R06_102033)
Where is OUKITEL_C4_V17.0_20161124 firm now?
I can't find it at needrom.com.
pop003 said:
Where is OUKITEL_C4_V17.0_20161124 firm now?
I can't find it at needrom.com.
Click to expand...
Click to collapse
Which rom do you have on your device?
Now I have R06_102033 on my C4
pop003 said:
Now I have R06_102033 on my C4
Click to expand...
Click to collapse
No problem, just use the twrp_recovery_R0x.zip from my previous post.
https://forum.xda-developers.com/showpost.php?p=71584701&postcount=10
[email protected] said:
No problem, just use the twrp_recovery_R0x.zip from my previous post.
https://forum.xda-developers.com/showpost.php?p=71584701&postcount=10
(do not forget to give it a like)
Click to expand...
Click to collapse
Thank you. twrp_recovery_R0x installed successfully.
However, in my environment, I needed the latest version of SP_Flash_Tool_v 5.1712_Win.
With other versions of sp_flash_tool, I did not succeed any number of times.
pop003 said:
Thank you. twrp_recovery_R0x installed successfully.
However, in my environment, I needed the latest version of SP_Flash_Tool_v 5.1712_Win.
With other versions of sp_flash_tool, I did not succeed any number of times.
Click to expand...
Click to collapse
Glad to hear it worked!
salvarez01 said:
Hello I have tried to use native sip editing the files in /system/etc/permissions but the option is not available in phone menu. Someone know how to activate?
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
You can configure SIP by using an App called Activity Launcher.
Download and Install Activity Launcher
Start Activity Launcher
Choose 'All Activities'
Search for 'Phone'
Open 'Phone'
Search and Click 'Sip Settings', 'com.android.phone.services.telephony.sip.SipSettings'
{
"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"
}
Hello, yes I know this app to find secret menu. With this you can configure sip settings but when you try to make a call the dialer not offer choice to select calls with sip account
Enviado desde mi Redmi Note 4 mediante Tapatalk
salvarez01 said:
Hello, yes I know this app to find secret menu. With this you can configure sip settings but when you try to make a call the dialer not offer choice to select calls with sip account
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
After you added an Sip account you can choose you default dailing method as follows: Dailer -> Settings -> Accounts -> Dail With
You also see your SIP account as "additional SIM Card" when Opening the dailer!
Thank you!
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
New twrp 331-test 1 for this device is builded!
Now need period of tests...
http://www.mediafire.com/file/cnqw8d2qkjqtp6k/Twrp_331_test1_Umi_Power.rar/file
reserved 1
Reserved 2
TWRP Not Working for Me
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
I confirm the first part of this, same issue here... i'd like to flash a twrp for gsi purposes, but for now no luck
SeekerofLight.iz said:
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Root UMIDIGI Power with Magisk
mr A V said:
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Click to expand...
Click to collapse
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
Step 0 - Download the Attached Zip File Below
Google Drive Mirror
Mediafire Mirror
MEGA Mirror
Step 1 - Drivers
Install the MediaTek drivers by running "DriverInstaller.exe". These are the drivers that worked for me. But if you have issues with them in Step 5, Google "Mediatek MT65xx USB VCOM Drivers" (or some variation of that) and try some others you can find.
-----------------------------------
Step 2 - Install ADB Interface
Install the Android SDK (ADB Interface). To do this drop the platform-tools folder (from the Step 2 folder) into your C:\ directory. Press the windows start button and search for "Environment Variables" and click on "Edit environment variables" from the results. Under SYSTEM VARIABLES on the bottom (not User variables above it) click on the "Path" variable, and click edit. In the new window that appears, hit "Browse..." and click on the "platform-tools" folder that you placed in your C:\ directory.
All this does is allows you to easily input adb commands into command prompt with no issues. This will be used to verify that the device is appearing properly and issue commands in case of emergency.
{
"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"
}
-----------------------------------
Step 3 - Install Magisk
Copy the Magisk.apk to your phone and install it.
(This is where you can then copy the boot.img to your device and patch it via the Magisk app to create the "magisk_patched_boot.img" file, however I have included the already patched file in Step 6 for the UMIDIGI Power so you don't need to.)
Also, this is the Magisk v19.3 Beta, but you can install another version.
-----------------------------------
Step 4 - OEM Unlocking/USB Debugging Mode
On your phone, go to Settings >> System >> Developer Options. (If you haven't activated Developer Options yet, do that by going to About Phone >> Build number, and tap it a bunch of times, but I'm sure you already know this lol)
In Developer Options, turn on "OEM Unlocking" to unlock the bootloader, and USB Debugging.
-----------------------------------
Step 5 - Verify That Your Phone is Detected with ADB
Connect your phone to your PC. Make sure you click "Allow USB debugging" on your phone. Then open up Command Prompt. (Protip: Type "color a" and press Enter if you want to feel like a REAL HACKERMAN.) Now, type in "adb devices" and verify that your phone is detected by your computer. If it's detected, then that's perfect you can move on to Step 6. If not, then uh... you may have to try and find some other MediaTek drivers mentioned in Step 1.
-----------------------------------
Step 6 - Set up SP Flash Tool
Open up SP Flash Tool on your computer by running "flash_tool.exe" in the SP Flash Tool Folder. (If at any time it shows a "Processing" window for some reason, just close and reopen the program if it doesn't go away on its own.)
On the first line choose "MTK_AllInOne_DA.bin". And the third line "Authentication File" can be left blank.
On the second line where it shows "Scatter-loading File", hit "choose" and find the "MT6765_Android_scatter.txt" file in the Step 6 folder. It'll load up and show a bunch of green/white rows in the space below.
Now this looked intimidating to me at first, but it's actually quite simple. As far as I understand (and I could be wrong but), the scatter file just tells the program where to place certain files, like a map for the program to follow. The scatter file I provided is for the UMIDIGI Power. The only thing we'll worry about for now is the boot.img file (but in the future, this is where you could also install a TWRP recovery once we get one that is confirmed to work.)
So in the white/green list, scroll down to where it says "boot" in the "Name" column, and click on the blank area in the "Location" column. It will bring up a window where you can browse to the "magisk_patched_boot.img" that I provided.
-----------------------------------
Step 7 - The Big Huzzah (Rooting)
Power off your phone and make sure it's UNPLUGGED. On SP Flash Tool, click "Download". This prepares the program to begin flashing your phone as soon as it is connected. Grab your phone with one hand, and with your other hand plug in the USB cable (if you only have one hand, use your mouth I guess). Your screen should not turn on at all throughout this process, but if it's successful, you should see that the program begins to flash your device after a second or two. Now just wait until it reaches 100% and says "Download Ok" with a green checkmark. And you're pretty much done!
You can then boot up your phone and check the Magisk app, as well as download a root checker from the Play Store to confirm that your phone has root access! Have fun!
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
mr A V said:
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
Click to expand...
Click to collapse
No problem! Unfortunately I don't see many custom ROMs coming to this phone, considering it's not a very popular device. I'd guess our best bet is to hope that the UMIDIGI F1 gets some support, and that anything on there can hopefully be ported over to this phone, but even that device isn't very popular either. For me though, that's not a huge issue because I'm actually quite satisfied with the stock firmware it has on board. It's basically stock Android Pie, and I've been able to add all the extra goodies I want into the phone through Magisk Manager and EdXposed with very minor issues. Most notably Viper4Android to fix the slightly tinny speakers and pump up the overall headphone experience too, and Gravity Box for some extra minor software customization.
Overall, I'd say the biggest downside to this device is the limited camera capabilities, and its somewhat limited performance for heavier tasks like 3D games / game streaming. But other than that, this feels like a very premium device. :good:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
mr A V said:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
Click to expand...
Click to collapse
I definitely consider myself to be a major noob with the more advanced Android development stuff. I only know enough to find my way around the internet and flash compatible software, haha. I've never looked into creating ports myself, but it's certainly something I think might be worth learning, especially with the limited device support on these phones.
And yeah, in terms of performance I don't expect much out of a phone at this price point, but for all the essentials - music, 1080p YouTube, web browsing, and mid to light gaming, it's surprisingly great considering the price. I haven't had any issues with the memory as of yet, so I wouldn't be too concerned, although you're definitely right in that they probably source some pretty cheap parts for these kind of phones.
SeekerofLight.iz said:
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
"stubbed guide"
Click to expand...
Click to collapse
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------
ghost45 said:
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
Click to expand...
Click to collapse
Can i ask you a guide on how were you able to boot it? i'm only getting a bootloop after flashing that from SPFlash
I will build one other version of recovery soon...
mg95tux said:
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
Click to expand...
Click to collapse
Glad to hear it worked for you!
Still nothing. Unfortunately I haven't had any luck with booting into TWRP since I last tried it. Hoping ghost45 will be able to help us out with that when he gets the chance.
Bootloop - Secureboot
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Andre_Filho said:
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Click to expand...
Click to collapse
remember to allow oem unlock from developer settings in stock rom, otherwise it will fail!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Andre_Filho said:
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Click to expand...
Click to collapse
The trick to getting Viper4Android to work is to make sure you have SELinux set to "PERMISSIVE" rather than "ENFORCING" on your phone. Here's a handy little app designed to automatically set it to permissive on boot!
https://forum.xda-developers.com/devdb/project/?id=1561#downloads
And for BusyBox, I was having issues too at first because I think with systemless root, BusyBox can only be installed in /sbin, which gets wiped after each boot. So I searched for "BusyBox" in the Magisk app and found a module called "BusyBox for Android NDK" which has worked perfectly for me.
One thing to note...
Sometimes SELinux doesn't always get changed automatically everytime you boot up. It's pretty consistent, but every once in awhile you may need to manually set it to permissive mode again if things don't seem to be working. But it's literally just pressing a single button, so not a big deal.
The other thing is with Viper itself- At times when I launch the app, the driver status says "abnormal" even after I've toggled SELinux to permissive. If you go into settings and toggle "compatibility mode" or "attach audio effects" on and then off that seems to refresh the driver status. Not sure why, but it works.
Let me know if you have any issues.
TWRP for UMIDIGI POWER
I ask for help in creating TWRP for UMIDIGI POWER firmaware ROM v1.5
Please make for this model TWRP
I am very grateful to you - I unlocked the phone and got the rights Root rights.
It remains only to create a TWRP for UMIDIGI POWER
At this forum, competent specialists and for other models everything is already done.
Maybe there is a website where you can make an order to create a TWRP?
Unfortunately, I do not know English and I do not know how to apply.
I would be very grateful and ready to test your work.
Introduction
This is the LineageOS 17.0 (non-GSI) port for K-touch i9 a.k.a Anica i9. Due to the lack of kernel source code, this port comes with a prebuilt kernel image, but the ramdisk has been updated to support a proper System-as-Root system partition as is required by Android 10.
This is ONLY compatible with the MT6739 variant of this phone.
About the phone
The K-touch i9 is an ultra-mini phone produced by K-touch (Ktouch / Anica) based on the MT6739 SoC. I got the phone purely due to its interesting size (similar to the Palm phone) and the desire to port real custom ROMs to it to see if they can work well. I mainly use it as a backup phone, so this port might not be thoroughly tested enough for daily drive.
Known Issues
- Some particular animation / gifs will skip frames or repeat incorrectly
Images
{
"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"
}
Flashing instructions
1. Unlock the phone (reboot to bootloader by holding volume up on boot, run `fastboot flashing unlock` and confirm)
2. Flash TWRP image from here
3. Reboot to recovery (hold volume up and choose Recovery accordingly)
4. Backup all stock partitions whatever way you like (especially boot / vendor)
5. Flash this LOS 17 port image and format data
6. Reboot and enjoy
Please note that after flashing this LOS 17 image, you have to restore the stock boot.img before being able to install A-only Android 10 GSIs again. Although you MIGHT be able to boot phh A/B GSI 10 on the boot.img of this LOS 17 port, please note that this is not tested and you still need to shrink the image size before phh GSIs can work -- the same as the A-only situation.
Why not GSI
There is no reason why not to use a phh GSI on this phone, given that phh GSIs work pretty well and I have actually fixed a few bugs for it too and I absolutely love it. However we can't play with some certain things, for example, transitioning to System-as-Root, in a GSI, and that's why I started this port just for fun. Also this device has such a small system partition that GSIs won't work out-of-the-box and require some manual adjustments just for the device, which kind of defeats the purpose. Nevertheless, I will contribute my fixes to GSIs so that things will work as well on GSIs as on my device-specific ROM ports.
Downloads
20191025: https://www.androidfilehost.com/?fid=4349826312261605900
Alternatively, you may check the latest updates to both the TWRP and the LOS 17 port on my GitHub
Source code
https://github.com/PeterCxy/android_device_ktouch_i9
There is no kernel source code available for this device, unfortunately.
Credits
all the people that have worked on MTK devices before me.
twrp link does not work
theleftykid said:
twrp link does not work
Click to expand...
Click to collapse
It works here. It links to a GitHub release page where you can download recovery.img for TWRP
Hi,
I bought this phone, but with different CPU- MT6580, 5MP camera at the back, would this ROM be compatible with it well?
I've tried to flash the TWRP recovery, but it failed - "FAILED (remote: size too large)" so it mean the recovery image not compatible with my phone?
This device is really nice, but huge let down by the operation sys. The battery drain really fast, always "phone idle" take place at the top of battery consuming chart.
Thank you!
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
theleftykid said:
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
Click to expand...
Click to collapse
Based on the previous comment before you, you seem to have the MT6580 version of the phone. This means you have a different and smaller gpt than the one from the OP that uses MT6739. You can't flash this ROM or any recovery from the MT6739 since they have different hardware and different partition layout. If you flash something, it will end with a nice brick
Cheers!
Rortiz2 said:
Based on the previous comment before you, you seem to have the MT6580 version of the phone. This means you have a different and smaller gpt than the one from the OP that uses MT6739. You can't flash this ROM or any recovery from the MT6739 since they have different hardware and different partition layout. If you flash something, it will end with a nice brick
Cheers!
Click to expand...
Click to collapse
Well, I’m sending myne back to get the mt3739 so I could mount 128gb sd card and to try this buil. It look promissing.
theleftykid said:
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
Click to expand...
Click to collapse
You boot into the original OS and the recovery will be back.
Thank you for this ROM.
I used it on my K-touch i10. Its the same as the i9 but the shape is slightly different.
I have the 3gb - 64gb version and it seems OK.
I had to use BiTGApps-Q for Playstore to appear.
I also had to go into the USB developer options to set up file transfer from a PC.
And no wallpaper app from holding on home screen.
I hope you keep this up to date else I might have to try and work out how to apply security patches.
Thanks again
EDIT. Oh so are you saying I could just try and install the GSI?
Edit. OK so Wellbeing and problems with Gapps is to do with Android 10 and gapps.
I also found twrp hard to control. The swipe action and pressing near the edge was difficult.
I don't have face recognition to unlock, not sure if that's because lineage os doesn't have it or the i9 doesn't, but certainly possible on my i10.
The swipe action in lineage is also difficult.
Thanks again. Just want to let you know.
Edit. Also a problem for me is when it's charging, touch screen gives the odd ghost press when used.
Ive found forcedoze useful with this phone.
Works with K-Touch M16?
Theoretically speaking this Rom should work in the K-Touch M16 as it has the exact same specs, processors, etc. Being the only difference is that it has a fingerprint sensor.
So I was wondering does anyone know if this custom ROM and TWRP works on the K-Touch M16.?
how do i download this rom. there are no active links available!
PeterCxy said:
Downloads
20191025: https://www.androidfilehost.com/?fid=4349826312261605900
Alternatively, you may check the latest updates to both the TWRP and the LOS 17 port on my GitHub
Source code
https://github.com/PeterCxy/android_device_ktouch_i9
There is no kernel source code available for this device, unfortunately.
.
Click to expand...
Click to collapse
From the first post
m16 tried
I have tried this with my M16, which is very similar to i9, same cpu same spec, got fingerprint though... no luck, unable to boot into recovery, anyone successfully done?
It worked with my K-touch i10.
I guess you should start looking at TWRP. If you have the same processor you should be able to get TWRP going.
Sorry no help here, maybe try a TWRP forum or something.
chinese bootloader
hi, i just got the phone so i wanted to flash this rom. but my bootloader is in chinese and i don't speak/read chinese.
can anyone here please help me get trough the bootloader so i do all the steps correctly.
i attached the picture from bootloader and also what google translate offers for translation.
does volume up and down works correctly on your devices? on my it just jumps one step down and up on ether up key or down key when i press and hold the key ti gradually turns volume up on ether up or down key.
I have an i10 and am no expert.
When I reboot and hold up-volune I get 3 options. Recovery, Fastboot and Normal in that order.
Are you sure your phone is the mt3769. As I had an i10 which was was MT6580 and I got those options. I did have Fastboot though. Sorry don't still have it for reference.
I just found out on youtube this menu should pop up when you press volume down + power on. But on my phone it also boots to this menu when i press volume up + power on. Guess i received defective volume buttons on my phone. Too bad as it is such a nice little phone.
Are you able to use the volume keys to move up and down the menu you took a picture of? Moving in this menu and selecting should be the up and down volume keys. Guess then you could see for sure if you have a key problem.
I did manage to take my phone apart as when I dropped it I managed to disconnect the screen cable inside but was lucky to be able to fix it.
---------- Post added at 12:23 PM ---------- Previous post was at 11:44 AM ----------
PeterCxy said:
...you still need to shrink the image size before phh GSIs can work...
...
Also, this device has such a small system partition that GSIs won't work out-of-the-box and require some manual adjustments just for the device, which kind of defeats the purpose. Nevertheless, I will contribute my fixes to GSIs so that things will work as well on GSIs as on my device-specific ROM ports.
Click to expand...
Click to collapse
Hello I'd like to update this for myself. I thought I'd use the GSI image but you say it needs resizing before use. Can you give me any pointers as to how you do this?
free30 said:
Are you able to use the volume keys to move up and down the menu you took a picture of? Moving in this menu and selecting should be the up and down volume keys. Guess then you could see for sure if you have a key problem.
I did manage to take my phone apart as when I dropped it I managed to disconnect the screen cable inside but was lucky to be able to fix it.
Click to expand...
Click to collapse
i am unable to enter the correct bootloader that gives you three options you mentioned before. i already contacted the seller to see what we can do cause i just received the phone. on this chinese menu i can navigate only down (pressing volume up or down moves the selection down) and i can select the item via power button.