Related
In this Thread i will explain how to set up MTK drivers and Flashtools.
Guideline:
Post #1 : Set up MTK drivers in Windows 8 / 8.1 / 10
Post #2 : Use Flashtools for MTK Devices
Post #3 : How to Flash Custom Roms / Roms download Guide / How to Root Stock Rom
Post #4 : Windows 10 MTK Drivers installation ( just in case post #1 dont work )
Post #5 : Lost IMEI Backup
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
How to Install MTK drivers in Windows 8 / 8.1 / 10
what we need:
MTK Vcom Preloader Driver 2.0
Download : https://www.androidfilehost.com/?fid=24438995911977169
First thing we need is to Disable the Signed Driver verification on Windows :
To disable driver signature verification, we’re going to need to get into the Troubleshooting options from the boot manager.
The easiest way to bring this screen up is using this secret trick.
Hold down the SHIFT key while you click Restart.
{
"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"
}
Once your computer has rebooted you will be able to choose the Troubleshoot option.
Then head into Advanced options.
Then Startup Settings.
Since we are modifying boot time configuration settings, you will need to restart your Computer one last time.
After restarting your computer a second time,
choose Disable driver signature enforcement from the list by typing the number 7 on your keyboard.
That’s all there is to it. Your PC will then reboot and you will be able to install unsigned drivers.
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Now its Time to open SP_Driver_v2.0.zip and start the DriverInstall.exe
it will open the install prompt . Press okay and dont change the installation path
Code:
C: // program files / Mediatek / Driver Package
during the installation it will start the verification window security.
Click on Install this driver software anyway
There will be an Error Message . - We Ignore it !
-Now Open your Device Manager and leave it open.
-Power Off your Phone and connect it with your Pc.
-you will see Under ports ( COM & LPT ) a Preloader unknown device
right click on there and click on Driver update/installation.
-Choose manually search for drivers
-Browse to C:// program files / Mediatek / Driver Package and apply.
-If all went good you have successfully installed the MTK Vcom Drivers. :good:
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
How to Use Flashtools
i use SP_Flash_Tool_Windows_v5.1520.00.000 and never had a problem with it.
Its for most all MTK Phones and for all Elephone Devices
Download Link: https://www.androidfilehost.com/?fid=24438995911977217
- Extract the Flashtool zip folder to your Desktop
- Click flash_tool.exe to open the Tool
- You will see two "folder buttons" Download agent and Scatter-loading
- Into Download agent place the MTK_AllInOne_DA.bin file .
its in your Flashtools folder
- Into Scatter-loading place the Scatter.txt
All Stock Roms / Custom Recoverys have one Scatter.txt in their Zip files.
- Make sure that every partition is checked
-IMPORTANT NOW, Flashing Part-
-Power Off your Device!
-Press on the Download Button!
-Connect your Device with PC and wait until all is flashed
-you will see a Green Mark when all is done
-Disconnect your Device and press Power button to Reboot.
:fingers-crossed::good::fingers-crossed:
------------------------------------------------------------------------------------------------------------------------------------------------
How to Install Custom Roms
You don't need to root your phone to use Custom Roms like
Eragon Rom
or
Nexus Rom
because within installation it will get root with SuperSU
P.s: if you run into a problem e.g Bootloop . (newest Rom dont work well with our Custom Roms , related to its Partition.Img)
You could Flash the Stock ROM 02150725 to solve it
--------------------------------------------------------------------------------------------------
1. Place the Rom.Zip into your Internal or External Sdcard
2. If you are on Stock Rom just Flash a Custom Recovery
Best Recovery without any bug is Philz v2 but you can also use Twrp Recovery
3. Hold Vol+ and Power simultaneously
you will get into the Bootloader Menu
4. Navigate with Vol+ to Recovery and apply with Vol-
5. In Recovery perform a Fullwipe , wipe System , Data , Cache , Dalvik
(In Philz Recovery wipe "clean to install a new rom"
In TWRP Recovery Wipe /advanced Wipe /wipe System,Data,Cache,dalvik)
6. Install the Rom.Zip located in your Sdcard
7. Reboot
<><><><><><><><><><><><><><><><><><><><><><><><><> <><><><><><><><><><><><><><><><><><><><><><><><>
Custom Roms and Stock Roms
Eragon Rom - http://forum.xda-developers.com/elephone-p8000/development/rom-06-9-eragon-1-0-android-5-1-t3195007
Nexus Rom - http://forum.xda-developers.com/elephone-p8000/development/rom-nexus-t3235626
CyanogenMod 12.1 - http://forum.xda-developers.com/elephone-p8000/orig-development/rom-cyanogenmod-12-1-p8000-t3259022
Flyme - http://bbs.elephone.hk/thread-8682-1-1.html#.VuQ3WYQrHIU flash via Flashtools
Vibe - http://bbs.elephone.hk/thread-8192-1-1.html Flash via Flashtools
Emui - http://forum.xda-developers.com/ele...-emui-v3-1-lite-04-02-2016-android-5-t3309296
Stock Roms
2015.07.25 - http://bbs.elephone.hk/thread-6536-1-4.html#.VuQ3C4QrHIU
2015.08.15 - http://bbs.elephone.hk/thread-7096-1-4.html#.VuQ3DoQrHIU
2015.09.07 - http://bbs.elephone.hk/thread-7743-1-2.html#.VuQ3QYQrHIU
2015.10.14 - http://bbs.elephone.hk/thread-8751-1-2.html#.VuQ3K4QrHIU
2015.11.05 - http://bbs.elephone.hk/thread-9163-1-2.html#.VuQ3NYQrHIU
2015.12.03 - http://bbs.elephone.hk/thread-9415-1-1.html#.VuQ3UYQrHIU
2016.02.17 - http://bbs.elephone.hk/thread-9898-1-1.html#.VuQ3SYQrHIU
Custom Recoverys
Philz v2: https://www.androidfilehost.com/?fid=24052804347838441
Twrp 2.8.7.0 : https://www.androidfilehost.com/?fid=24269982086997788 thx hanuma
Twrp 3.0.0.0 : https://mega.nz/#!wZM01byD!JTkRCVaJoxm5YmE2sFQBB2e1wnDIYo1AWAetqY8e60o thx hanuma
SuperSU root
Thread:
http://forum.xda-developers.com/showthread.php?t=1538053
100% bug free Supersu v.2.46.zip
https://download.chainfire.eu/696/SuperSU/
<><><><><><><><><><><><><><><><><><><><><><><><><> <><><><><><><><><><><><><><><><><><><><><><><><>
How to Root Stock Rom
-If you want to Root your prefered Stock Rom
-Place SuperSU into your Sdcard
-Flash a Custom Recovery with Flashtools and its Scatter.txt
-Hold Vol+ and Power to get into Bootloader Menu
-Navigate with Vol+ and apply Recovery with Vol-
-Flash Supersu.zip
-Reboot
Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial
To determine the version of Windows 10 that you have (32 bit or 64 bit):
- Right-click on Start then click on System
- In the System window that opens, in System section, you will find your version of Windows next to System type
To disable Windows 10 64 bit driver signature enforcement:
- On your 64 bit Windows 10 desktop click on Start then on Settings
- Click on Update & security then in the left pane click on Recovery
- Under Advanced startup click on Restart now button
- Click on Troubleshoot then on Advanced options
- Click on Startup Settings then on Restart button
- The computer will restart with the Startup Settings screen
- To disable the driver signature enforcement until next restart press on number key 7 or F7 on your keyboard.
- After restart you can proceed with the unsigned MTK drivers installation for your 64 bit Windows
- After you install the unsigned drivers, to use them again in the future, you have to repeat this procedure
To install the MTK VCOM USB Drivers on 32 & 64 bit Windows 10:
- Download the drivers *.zip archive and extract the folder from inside on to the desktop:
https://www.androidfilehost.com/?fid=24269982087012126
Right-click on Start then click on Device Manager
In the Device Manager Window click on the first item – your computer name
Click on Action then Add legacy hardware
On the Welcome to the Add hardware Wizard window click on Next button
Select Install the hardware that I manually select from a list (Advanced) and then click on Next button
Click on Show All Devices then on Next button
In the Add Hardware window click on Have Disk… button
In the Install From Disk windows click on Browse… button
In the next window – Locate file – browse for the folder that you have extracted on the desktop at the beginning
Select the version of the driver according to your Windows 10 version – x64 for 64 bit and x86 for 32 bit and click Open button
Click the OK button to load the driver
From the list of drivers select MTK USB Port and click on Next button
If a red warning window will open, click on Install this driver software anyway
This action will add the following drivers in to the operating system:
- MediaTek DA USB VCOM Port
- MediaTek PreLoader USB VCOM Port – for transferring the firmware to your device
- MTK USB DEBUG Port
- MTK USB Modem Port
- MTK USB port – for transfering PreLoader to your device (and recovery in case of bad or corrupt firmware)
Now we need to remove the device that we have installed but leave the drivers in the operating system.
To do that, in the Device Manager window we expand Ports (COM & LPT) section
Right-click and click Uninstall on the MTK USB Port
- In the Confirm Device Uninstall window make sure that the box Delete the driver software for this device is empty
- You need to leave the drivers in the operating system and only remove the device that you added
- Click on the OK button to finalise
Now, when you will connect your turned off MTK device to the Windows 10 computer by USB, the device will be recognized either trough a MediaTek Preloader USB VCOM Port interface or as a MTK USB port if it is bricked or it has bad/corrupt firmware. The SP Flash Tool will be able to transfer the firmware to your device trough this interfaces. Make sure you connect the device after you press the Download button in SP Flash Tool, as the communication interface will only be alive for 2 seconds if no data is being sent.
Download SP Flash Tool v3 & v5 – Latest versions:
http://laurentiumihet.ro/technology/download-sp-flash-tool-v3-v5-latest-versions/
TUT found here : http://laurentiumihet.ro/technology...-for-32-64-bit-drivers-installation-tutorial/
cheers
Lost IMEI Restore
A common problem many face in their phone is loss of IMEI no. This is results in no network detection by your phone. U can come to know you have lost your IMEI by checking Settings->About phone->Phone information. There under IMEI section you won’t be finding your mobile IMEI numbers displayed.
Don’t worry you can restore your IMEI’s. Just follow this guide and you will be able to restore your IMEI. I will split the tutorial into two parts.
BACKING IMEI :
-First step before performing all these things is that your phone should be rooted.
When your phone is in normal state with everything functioning install Root explorer and navigate to the below location
Code:
>ROOT>DATA>NVRAM>MD>NVRAM>NVD_IMEI>MP0B_001
-Now copy this MP0b_001 file to your SD card or PC whichever place you feel the file we be safer.
-Now download MTK Droid tools .
-Now extract the zip file and open the MTK droid tools exe file.
-Now in your phone turn on USB Debugging by going to Settings->About phone-> Developer options and there turn on USB debugging.
-Now connect your phone and MTK droid tools should be able to detect your phone. U should see a window like this appearing after your
phone has been detected.
-Now press the ROOT button present in lower right corner. When it asks Supersu grant in your mobile click allow. After MTK droid gets
access u should see a green colour box appearing in the lower left corner which means u have correctly granted access to MTK droid.
-Now click on the IMEI/Nvram tab. A window should open and click backup NVRAM and MTK droid tools would take a backup of NVram in
its folder.
RESTORING IMEI :
-Now when you lose IMEI first try this method. Now take the MPDB_001 file which you took backup at the first step and navigate through
Root explorer to this location ->ROOT->DATA->NVRAM->MD->NVRAM->NVD_IMEI.
-Now paste that file and replace the one present there. Set the permissions for that file as RWER-ER-E. Now reboot your phone and you
should be able to get your IMEI back.
If you still haven’t got IMEI open MTK droid tools and connect your phone and press ROOT again and give MTK droid tools root access.
-Now click on IMEI/Nvram tab and select Restore option and restore the NVram backup which you took earlier. Now reboot your phone and
you should be able to get your IMEI.
Extreme method :
-After performing all the above if you haven’t still got IMEI. Now switch off your phone and open SP Tools and connect your phone.
Click on format and format your whole phone. ( This wipes whole of the phone including NVram region ).
-Now flash stock ROM through SP Tools and after it completes start up your phone. ( Don’t be surprised. Your IMEI will still be in lost state
only ). Now root your phone.
-After successful rooting now connect your phone to MTK Droid tools and again press ROOT button and grant root access to MTK Droid
tools. Now click on IMEI/NVram tab.
-Now as you see in the image above you can see two boxes IMEI1 and IMEI 2. Now enter your device IMEI numbers manually in those two
boxes.( You can get your IMEI no’s from your phone box ). Now click replace IMEI. Now reboot your phone and you should be definitely able
to get your IMEI restored.
MTK DROID TOOLS LINK : https://www.androidfilehost.com/?fid=24438995911972546
found: http://www.androiddevs.net/restoring-lost-imei-mtk-phone/
Beautiful @skeleton1911
What a gread job!
Gesendet von meinem Elephone P8000 mit Tapatalk
Thanks for this great work.
And for all the Linux Users out there. SPFlashtool also work perfekt with x86-64 Linux distros.
The most anoying point and greatest drawback is, that with newer Ubuntu based distros like Mint, since 14.04, the builtin modem-manager don't like Mediatek, so you have to blacklist Mediatek in the udev rules.
How this will done, is written in that great tutorial by Miss Montage.
Cheers
The direct link for Tapatalk Users: http://forum.xda-developers.com/general/rooting-roms/tutorial-how-to-setup-spflashtoollinux-t3160802
jknarf said:
Thanks for this great work.
And for all the Linux Users out there. SPFlashtool also work perfekt with x86-64 Linux distros.
The most anoying point and greatest drawback is, that with newer Ubuntu based distros like Mint, since 14.04, the builtin modem-manager don't like Mediatek, so you have to blacklist Mediataek in the udev rules.
How this will done, is written in that great tutorial by Miss Montage.
Cheers
The direct link for Tapatalk Users: http://forum.xda-developers.com/general/rooting-roms/tutorial-how-to-setup-spflashtoollinux-t3160802
Click to expand...
Click to collapse
arnicika said:
Beautiful @skeleton1911
What a gread job!
Gesendet von meinem Elephone P8000 mit Tapatalk
Click to expand...
Click to collapse
thank you very much
This should be pinned!
BlueFlame4 said:
This should be pinned!
Click to expand...
Click to collapse
Already done
Gesendet von meinem Elephone P8000 mit Tapatalk
A German Translation for #1 and #2 is available there: http://www.android-hilfe.de/thema/a...n-und-anwenden-unter-windows-8-8-1-10.759025/
skeleton1911 said:
Lost IMEI Restore
RESTORING IMEI :
-Now when you lose IMEI first try this method. Now take the MPDB_001 file which you took backup at the first step and navigate through
Root explorer to this location ->ROOT->DATA->NVRAM->MD->NVRAM->NVD_IMEI.
[...]
Click to expand...
Click to collapse
Please note neither the name of the IMEI file nor its position seem to be constant, but may vary from one Stock ROM version to another.
In my case (Stock Rom version 20151203) it took me some time to find a file named "MP0B_001" within the following location:
/nvdata/md/NVRAM/NVD_IMEI
Maybe the easiest way to find the IMEI file is to search for the keyword "NVD_IMEI" within some root file manager as this does not seem to change.
@skeleton1911 I'm having problems with MTK DROID TOOLS, it won't detect my elephone p8000.
I was wondering can you help me with this?
Rav3r1 said:
@skeleton1911 I'm having problems with MTK DROID TOOLS, it won't detect my elephone p8000.
I was wondering can you help me with this?
Click to expand...
Click to collapse
you want to restore your imei?
do this: it just takes a minute
You can solve your imei problem with this "MTK Engineering Mode" from playstore.
You open the app and go to: MTK Settings, Connectivity, CDS Information, Radio Information, Phone 1.
Here you have at the top "AT+". here you complete to >>AT+EGMR=1,7,"123456789012345"<<, of course with your imei, which ist standing on the akku-cover.
Then, very important: You have to put in a space after "AT+", so it looks like >>AT+ EGMR=1,7,"123456789012345"<<
Click "SEND AT COMMAND". Thats it.
For the second imei do the same with >>AT+ EGMR=1,10,"123456789012345"<<
In Lost IMEI Restore part of tutorial MtkDroidTools v2.5.3.zip link to infected file. PLEASE REMOVE or change to https://androiddatahost.com/cj8vrp
SHA256: 40fe0934c24b17bc49e9b96c24c873fc5c4e0744ee31c8c5193c50168ee43839
File name: MtkDroidTools v2.5.3.zip
Detection ratio: 32 / 52
Analysis date: 2016-12-15 22:42:21 UTC ( 2 days, 1 hour ago )
virustotal.com/en/file/40fe0934c24b17bc49e9b96c24c873fc5c4e0744ee31c8c5193c50168ee43839/analysis/
@skeleton1911
I believe that first post need a big refresh.
The new All-In-One Mediatek driver don't need to disable driver signing. and contain both USB ADB and USB preloader driver for Mediatek chips
For the Flashtool version (Windows/Linux) there is a specific thread where you can redirect all user to get latest version of Flashtool program.
I bought the XZ1C from USA to India as it is not available at all in Indian markets (and never will be - because no compact devices were launched in India). I love this device except for one thing. Low internal memory - and I bet others might also be annoyed by this. There's two workarounds that I could immediately think of but can't be implemented with this Device.
1. Adoptable storage : Adopt external SD card as internal storage - this is one of the coolest features Oreo has to offer, but can't be used in this device. I went through a lot of blog posts and followed the steps, also read about the adoptable storage leading to no solution. I have a Samsung 128GB EVO SD card and I tried to adopt it as an internal storage in more than one ways with no success.
2. Move apps to SD : I thought I could move at least some apps if not all to external SD but this feature that was introduced in Android 2.2 (I remember using it on my Samsung Galaxy Apollo i5801) and re-introduced in 5.0. But this is also not working. I also tried enabling 'Force allow apps on external' under developer options which didn't work.
As I don't have this phone officially supported in my country, I want to check if someone can contact Sony support in their country (US, UK, Germany) to help fix this through an update maybe?
Another purpose of this thread is to discuss alternate workarounds if anyone has tried any and worked for them.
Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.
mhaha said:
Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.
Click to expand...
Click to collapse
I agree with you. I am going to wait for a while and see if Sony pushes an update that provides move apps to SD option (which I highly doubt they will). But if there comes a point where I desperately need space, I will root the phone. Out of 6 phones that I've used in past 6 years, this is the first one I haven't rooted and ain't planning to.
Possible Solution
I've looked at a thread from the sony forums. Some people were able to get the microSD card to work by factory resetting the phone with the SD card inside. Hope this helps.
What I've done now is to factory reset the phone with the sd card inserted and boot and setup the phone with the sd card in place this time. Then format it again thru the phone (I have not activated sd card encryption yet) and all of a sudden spotify, netflix, ... work with the sd card just as expected.
So perhaps one of you, who experience the same thing, might want try out if this is reproduceable.
Keep the sd card in the phone
Factory reset (I did it via the Xperia companion desktop software)
Boot it up again
Format SD Card
Click to expand...
Click to collapse
Antilogy said:
I've looked at a thread from the sony forums. Some people were able to get the microSD card to work by factory resetting the phone with the SD card inside. Hope this helps.
Click to expand...
Click to collapse
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disable by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
That means the TC should be able to do that.
Antilogy said:
That means the TC should be able to do that.
Click to expand...
Click to collapse
What r u referring to?
( and "tc" =?... This ain't Twitter u know.. U can write as long as u can ?)
Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
Dany XP said:
What r u referring to?
( and "tc" =?... This ain't Twitter u know.. U can write as long as u can )
Click to expand...
Click to collapse
Sorry. I meant to say topic creator. In this case that would be @kaustubhg123.
You can actually use a little neat trick:
Unlock your bootloader
Install XperiFix ( https://www.xperifix.com ) - XDA Thread to restore camera and X-R,BionZ functions (thanks a lot Sony, for nothing)
Xperifix auto install Magisk 16
Use [Magisk Module] Magic Folder Binder (fbind) module to "join" your internal folders with SDCARD and bind folders like Downloads, DCIM, .android
For example if you download a file, even if the phone downloads it to the internal memory it will be actually on the SDCARD. fbind also moves the old data to sdcard when you configure fbind.
mhaha said:
Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.
Click to expand...
Click to collapse
I'm still very very green to android and to using Xperia Android phones ... what consequences and compromises are to be faced wtih rooting bootloader? From looking at former threads from over 4yrs ago it seemed that rooting was THE holy grail and raison de T'etre for having an Android (reason for being/having).
Supa_Fly said:
I'm still very very green to android and to using Xperia Android phones ... what consequences and compromises are to be faced wtih rooting bootloader? From looking at former threads from over 4yrs ago it seemed that rooting was THE holy grail and raison de T'etre for having an Android (reason for being/having).
Click to expand...
Click to collapse
Sony have given developers and java enthusiasts the finger with this latest bootloader. There isn't a way to save the encrypted keys (unique to your phone) before unlocking it. So you can unlock it to do development, but it's a one way step, which breaks the camera and a few other functions.
In the past my two main reasons for rooting were to theme the phone a different colour and to save battery. Theming can be done without root now and my battery lasts three days anyway.
Having said that, I have just flashed sToRm//'s TWRP + KERNEL + ROOT + DRM fix/restore (because there’s a rooting enthusiast inside every android owner) and everything is working perfectly. The camera is working and all the software functions correctly.
But rooting the phone to get you control over moving apps to the SD card is a bit extreme and a lot of work for a very minor inconvenience. What are you doing with a small compact phone if you want to use two or three hundred apps?
Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
What good reasons?
I have enabled all apps to save their things on SD card (The camera app stores all photos on SD by default but the stupid Album app stores its thumbnails data on internal memory for no reason). My main big issue is with WhatsApp which stores its data on internal memory and provides no option to store it on SD card. WhatsApp is almost 11GB on my phone now.
mhaha said:
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that..
Click to expand...
Click to collapse
The Xperia V & Z1c both allowed apps to store their data on SD (Spotify, Audible, etc.) but can't do it on this phone :/ Apparently, Oreo blocks us from using our SD card in this way.
luminoso said:
You can actually use a little neat trick:
Unlock your bootloader
Install XperiFix ( https://www.xperifix.com ) - XDA Thread to restore camera and X-R,BionZ functions (thanks a lot Sony, for nothing)
Xperifix auto install Magisk 16
Use [Magisk Module] Magic Folder Binder (fbind) module to "join" your internal folders with SDCARD and bind folders like Downloads, DCIM, .android
For example if you download a file, even if the phone downloads it to the internal memory it will be actually on the SDCARD. fbind also moves the old data to sdcard when you configure fbind.
Click to expand...
Click to collapse
so, luminoso, in that case, can i transfer apps from phone to sd card?
because you are talking about bind the download folder, but having 10gb on my whatsaap i was really interested in move this ffrom phone storage to sd card
reckfield said:
so, luminoso, in that case, can i transfer apps from phone to sd card?
because you are talking about bind the download folder, but having 10gb on my whatsaap i was really interested in move this ffrom phone storage to sd card
Click to expand...
Click to collapse
You can bind whatsapp folder in that case
luminoso said:
You can bind whatsapp folder in that case
Click to expand...
Click to collapse
I decided to go ahead with xperifix, i have g441 compact xz1 european version, last firmware a.12a.179. i tried several times , but its not working with xperifix 2.5 last version
i attached some logs
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
06-6-2018_18-14-51 ===> List /system
Luminoso, do you have any idea¨?
reckfield said:
I decided to go ahead with xperifix, i have g441 compact xz1 european version, last firmware a.12a.179. i tried several times , but its not working with xperifix 2.5 last version
i attached some logs
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
06-6-2018_18-14-51 ===> List /system
Luminoso, do you have any idea¨?
Click to expand...
Click to collapse
Patching of your twrp recovey is needed.
I had to patch it with the last recovery (26. May) https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
if you do it your twrp is not safe !
At first download Android kitchen, extract it.
Copy your twrp file into the folder and open unpackimgbat
After finish you have a folder called "ramdisk", open it.
Inside you open the file "prop.default" with your texteditor.
find the following two parameter and set them to 0:
ro.secure=1
ro.adb.secure=1
save the file, go one folder up and click on repackimg.bat.
You have a "new-recovery.img" file.
Boot your device into fastboot:
fastboot flash recovery <path of your new recovery.img>
The solution works, but device security is in danger.
You can use it, or wait for a new twrp.
Raz0Rfail said:
Patching of your twrp recovey is needed.
I had to patch it with the last recovery (26. May) https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
if you do it your twrp is not safe !
At first download Android kitchen, extract it.
Copy your twrp file into the folder and open unpackimgbat
After finish you have a folder called "ramdisk", open it.
Inside you open the file "prop.default" with your texteditor.
find the following two parameter and set them to 0:
ro.secure=1
ro.adb.secure=1
save the file, go one folder up and click on repackimg.bat.
You have a "new-recovery.img" file.
Boot your device into fastboot:
fastboot flash recovery <path of your new recovery.img>
The solution works, but device security is in danger.
You can use it, or wait for a new twrp.
Click to expand...
Click to collapse
Thanks raz0rfail, it seems that has a solution in this.
three considerations allow me to ask you.
1. firstly, im encouraged to follow your instructions, but im entering a completely new field, Idont know whats android kitchen , how to copy "my twrp file into the folder", and after carrying out this instructions, should I open again xperifix, and launch the rooting process? if so, There is any risk xperfix overwrite the "previous patched" twrp as you told me in the last post?
2. when will the new twrp launch? because the last update on twrp's website was december 2017
3. Storm's xperifix 3.0 it is worth it to wait its release? because maybe waiting one month more, probably my twrp problem could be solved?
I'm confused, but thank you for you reply, at least you give me a little of chance of fix this problem
reckfield said:
Thanks raz0rfail, it seems that has a solution in this.
three considerations allow me to ask you.
1. firstly, im encouraged to follow your instructions, but im entering a completely new field, Idont know whats android kitchen , how to copy "my twrp file into the folder", and after carrying out this instructions, should I open again xperifix, and launch the rooting process? if so, There is any risk xperfix overwrite the "previous patched" twrp as you told me in the last post?
Xperifix will always download the twrp image from his servers, you have to go a little around to use your twrp file, or he updates his img-file on his server.
2. when will the new twrp launch? because the last update on twrp's website was december 2017
Your device twrp has nothing to do with the generic release from twrp. Read the text below your qoute.
3. Storm's xperifix 3.0 it is worth it to wait its release? because maybe waiting one month more, probably my twrp problem could be solved?
I don't know what he will change, but if he always redownload the twrp file from his server, he has to update the img-file.
I'm confused, but thank you for you reply, at least you give me a little of chance of fix this problem
Click to expand...
Click to collapse
OK I will start from scratch with explaining:
TWRP (TeamWin Recovery Project) brought a TWRP version out called 3.2.1 or so, but released twrp version is generic for all android devices.
So some devices have special requirements for a working twrp recovery and a Device Developer patch the generic twrp version to get it working on this device.
It needs time but on many devices it's mandatory.
So i meant in the last thread entry not the generic twrp version from TWRP creator, i meant the modificated version from our device developer which creates our twrp version.
Currently he hasn't released a version which works with the last XZ1 compact firmware 47.1.A.12.205.
And if you use a different twrp which not works on your new firmware, you will get the message $ADB_VENDOR_KEYS is not set or the message adb device is unauthorized.
My tutorial shows you how to modificate your twrp version which you get from Xperifix to get it working with the new firmware.
But if you use my twrp, your device isn't secured as you used a the correct twrp recovery from our device developer.
So you can decide if you want to use the new firmware and magisk and my cam and stay a little unsecure or you wait if the device has created a working twrp for the firmware and xperifix has updated the img-file on his server.
Execution steps for patching your twrp recovery image and get cam and magisk working again on new firmware.
At first download Android Image kitchen from here:
https://forum.xda-developers.com/showthread.php?t=2073775
Download minimal adb and fastboot from here:
https://androidfilehost.com/?fid=962187416754459552
Extract both Zip-Files on a place you want.
Then you have under C:\Xperifix\DATA\TWRP an .img-File called xz1c-twrp.img if Storm didn't change the paths.
Copy this file into the folder where you extracted Android Image Kitchen.
Execute Unpackimg.bat and change parameter in the file as described. Then execute repackimg.bat.
Open cmd.exe with windows-key + r-key. Enter cmd.exe and execute it.
Open the folder where you have extracted minimal adb and fastboot and copy the filepath of it.
switch back to cmd and enter the command cd + your path and press enter.
You should now be inside your folder inside cmd.
Then open the folder where you have extracted android Image Kitchen and right click on the new-recovery.img and in contextmenu click copy path.
switch back to cmd and enter the following command:
fastboot flash recovery and right click and click on insert to insert the image path. But don't execute it!
Next step have to do with Xperiix:
Reboot your phone into fastboot and start executing XperiFix.
if You got the message in XperiFix that the recovery is flashed unplug your phone and boot it again into fastboot.
Now execute the command inside cmd.exe
click up on your keyboard to get the last command inside cmd and replace the word "flash" with "boot" and your phone start booting into correct twrp image.
Now let Xperifix work until it's finished and you should have a working cam and magisk.
Raz0Rfail said:
OK I will start from scratch with explaining:
TWRP (TeamWin Recovery Project) brought a TWRP version out called 3.2.1 or so, but released twrp version is generic for all android devices.
So some devices have special requirements for a working twrp recovery and a Device Developer patch the generic twrp version to get it working on this device.
It needs time but on many devices it's mandatory.
So i meant in the last thread entry not the generic twrp version from TWRP creator, i meant the modificated version from our device developer which creates our twrp version.
Currently he hasn't released a version which works with the last XZ1 compact firmware 47.1.A.12.205.
And if you use a different twrp which not works on your new firmware, you will get the message $ADB_VENDOR_KEYS is not set or the message adb device is unauthorized.
My tutorial shows you how to modificate your twrp version which you get from Xperifix to get it working with the new firmware.
But if you use my twrp, your device isn't secured as you used a the correct twrp recovery from our device developer.
So you can decide if you want to use the new firmware and magisk and my cam and stay a little unsecure or you wait if the device has created a working twrp for the firmware and xperifix has updated the img-file on his server.
Execution steps for patching your twrp recovery image and get cam and magisk working again on new firmware.
At first download Android Image kitchen from here:
https://forum.xda-developers.com/showthread.php?t=2073775
Download minimal adb and fastboot from here:
https://androidfilehost.com/?fid=962187416754459552
Extract both Zip-Files on a place you want.
Then you have under C:\Xperifix\DATA\TWRP an .img-File called xz1c-twrp.img if Storm didn't change the paths.
Copy this file into the folder where you extracted Android Image Kitchen.
Execute Unpackimg.bat and change parameter in the file as described. Then execute repackimg.bat.
Open cmd.exe with windows-key + r-key. Enter cmd.exe and execute it.
Open the folder where you have extracted minimal adb and fastboot and copy the filepath of it.
switch back to cmd and enter the command cd + your path and press enter.
You should now be inside your folder inside cmd.
Then open the folder where you have extracted android Image Kitchen and right click on the new-recovery.img and in contextmenu click copy path.
switch back to cmd and enter the following command:
fastboot flash recovery and right click and click on insert to insert the image path. But don't execute it!
Next step have to do with Xperiix:
Reboot your phone into fastboot and start executing XperiFix.
if You got the message in XperiFix that the recovery is flashed unplug your phone and boot it again into fastboot.
Now execute the command inside cmd.exe
click up on your keyboard to get the last command inside cmd and replace the word "flash" with "boot" and your phone start booting into correct twrp image.
Now let Xperifix work until it's finished and you should have a working cam and magisk.
Click to expand...
Click to collapse
the descriptions are absolutely precise to follow and thanks you,
in the folder data, according your description there must be this directory C:\Xperifix\DATA\TWRP an .img-File.
on my xperifix there is not such folder. attach you some images, (I also reinstall xperfix 2.5 ruling out if I lost some folders)
{
"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"
}
WP17 is a rugged phone with Infrared Night Vision Camera, Helio G95 8GB+128GB 6.78“FHD+ 90Hz 64MP Triple Camera+16MP Selfie 8300mAh Android 11 Global Version.
{
"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"
}
Bought me a Oukitel WP17, but couldn't find much information about this phone.
So I'm going to post info here for everyone to see and participate in how to flash, root and update the phone.
Update:
Using the MTK-bypass Small utility to disable bootrom protection(sla and daa).
According to this Exploit, this MT6785 Oukitel WP17 is fully unlocked, and should be flashable:
Windows10:
[2022-10-13 02:45:23.376773] Found device = 0e8d:0003
[2022-10-13 02:45:23.766358] Device hw code: 0x813
[2022-10-13 02:45:23.776413] Device hw sub code: 0x8a00
[2022-10-13 02:45:23.786386] Device hw version: 0xca00
[2022-10-13 02:45:23.796588] Device sw version: 0x0
[2022-10-13 02:45:23.806536] Device secure boot: False
[2022-10-13 02:45:23.816739] Device serial link authorization: False
[2022-10-13 02:45:23.816739] Device download agent authorization: False
[2022-10-13 02:45:23.836660] Disabling watchdog timer
[2022-10-13 02:45:23.846734] Insecure device, sending payload using send_da
[2022-10-13 02:45:23.896695] Found send_dword, dumping bootrom to bootrom_813.bin
Linux:
[2022-10-13 09:15:03.350097] Found port = /dev/ttyACM0
[2022-10-13 09:15:03.423994] Device hw code: 0x813
[2022-10-13 09:15:03.425119] Device hw sub code: 0x8a00
[2022-10-13 09:15:03.425523] Device hw version: 0xca00
[2022-10-13 09:15:03.425902] Device sw version: 0x0
[2022-10-13 09:15:03.426248] Device secure boot: False
[2022-10-13 09:15:03.426595] Device serial link authorization: False
[2022-10-13 09:15:03.426923] Device download agent authorization: False
However, flashing this phone in any Sp flash tool, is ending up in:
ERROR : STATUS_SEC_PUBK_AUTH_MISMATCH_N (0xC002001B)
The PUBK_AUTH part of this error message, is the Authorization for flashing Signed/verified image files. In the Oukitel WP17 firmware folder, downloaded from Oukitel Downlod Center, are their only certain files marked as verified.img, and now after testing in Sp flash tool, loading ALL non-verified files, you can flash these files to the phone without problems.
.
Stock Oukitel Android 11 recovery
Let's fix this phoneDownload these files:Oukitel WP17 firmware: ASW2100YJ_2201_T2046
Python 6.3.1
Mediatek VCOM, CDC, USB Serial & Smartwatch Drivers
UsbDk_Brom-mode
MTKClient
Flash_Tool_v5.2028
Computer with internet
But before we can start, we need to format the phone, to delete all old configurations and settings.
1. Start by extracting the firmware file to your desktop. Now open up the MTKClient zip file and drag all files to your firmware folder.
2. Now you Install all needed drivers: Mediatek VCOM, CDC, USB / UsbDk_Brom-mode.
3. Extract the Flash_Tool to your desktop and open the flash_tool.exe.
ONLY check the UNverified files. We will flash the verified files later. Click on the Download button when you're done. Take your dead phone and connect it to the computer with the USB cable. Hold down Volume+ Volume- and power-button together, hold the buttons until the flashing start.
Once you have flashed the UN-verified files to your phone, we start the process of flashing the verified files.
4. Now we need access to the verified files. open a prompt in the firmware.
To do that, go to the start menu and type CMD.
4. Right-click and copy the address and paste it in the prompt window.
5. Now we have to configure MTKClient to be able to communicate with the phone.
Past in these commands one at a time in to the promt window.
Code:
python setup.py install
pip3 install -r requirements.txt
6. And now finally after you have set up the environment in python.
The flashing of the verified files to you phone can begin. copy and paste in the hole commands.
Code:
python mtk w md1img,spmfw,scp1,scp2,sspm_1,sspm_2,cam_vpu1,cam_vpu2,cam_vpu3,gz1,gz2,lk,lk2,logo,dtbo,tee1,tee2 md1img-verified.img,spmfw-verified.img,scp-verified.img,scp-verified.img,sspm-verified.img,sspm-verified.img,cam_vpu1-verified.img,cam_vpu2-verified.img,cam_vpu3-verified.img,gz-verified.img,gz-verified.img,lk-verified.img,lk-verified.img,logo-verified.bin,dtbo-verified.img,tee-verified.img,tee-verified.img
Press Enter,
On the phone: Hold down Volume+ Volume- and power-button together, hold the buttons until the flashing start. Sit back and wait
.
Your phone will end up like this after boot.
Done ....
Now Update your phone by Android update service by going in to 'Settings / System and update phone.
.
-- IMEI Restore --
After formatting the phone. I use ModemMETA tool to restore my IMEI.
Select the “Smart Phone” option from “Platform Type” section. Same as , select “USB” option from “PORT” section.
Press the Connect button in Modem METAtool. Hold down the Volume+ Volume- and power buttons at the same time while plugging in the USB cable. Meta tool will detect the device and it will start to load Boot file, karnel port etc. You can see all the process in “Connection Stages” section.
After completing the configuration process, you will be able to see “Connect” message at the bottom of the tool.
Now click on “Load DB”. “Load Database file from target”.
Now click on search box and select IMEI download option from drop down menu.
A new IMEI window will pop up in front of you.
Type in yor IMEI : and hit on “Write” button from same window.
ILLEGAL to Creating your own: 12345.12345.1234
if everything went well, it looks like this.
Update:
Easy rooting with Magisk ......
This will Unlock your bootloader!.
Unlocking your bootloader will send your phone in to a emergency state, and delete all personal data on the device. Back up everything that is important to you, before proceeding with rooting your phone -
Download and extract AA - Install Android to your desktop. Turn off your phone and enter 'fastboot mode'. Connect your phone to the computer and open AA - Install ROOT.dat.
Install Magisk25.
.
-- WARNING --Thinking of upgrading to Android 12 / Android 13 ?
The camera drivers found in the Android 11 version your phone was shipped with -Are NOT in the Android 11 version from the Oukitel Download Center !.You will brake your 64MP Camera if you flash GSI ore the version from Download Center .
Although I copied all the files required to restore the camera, which you can find below in a zip file -
Are the drivers in all other roms and GSI's to control the camera missing.
--FM drivers are located in kernel. Most other oem drivers are in vendor. And the definitions are in system
However, there is an easy fix for this, and that is to make a backup of your working phone firmware before you start installing other versions of Android, so that you can always restore your phone from this backup, with the correct drivers and get a fully functional phone again.
Dump/extract/backup your Oukitel WP17 firmware.It is ALWAYS a good practice to backup your firmware. Any phones sooner or later will have issues and since you don't have a copy to restore yor phone, you will spend money sending it in for repair which sometimes costs more than the phone is worth. There are many ways to make a copy of your phone's firmware. search on the internet or use this simple guide:
All the files you need can be found under this video
And to everyone who already broken their phone and is now looking for a way to restore their phone. Have I already ordered a new WP17 that I will create a firmware backup of, and make available for you and a manual for how to restore. I will keep you updated on that, but it takes a long time to get things shipped from China these days.
.
Android 12 / 13 on Oukitel WP17 -I created a small script that quickly installs Android 12 and 13 on your phone.
Get rid of the pesky red text on the screen.
Android 12 ...
Android 13 ...
To begin with, you need to decide which version of Android you want on your phone.
To help you on your way, I suggest you check out the link below. It's important that you choose the ARM64 AB version.
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
In this example, let's say you want to install Spark OS Android 13.
Go to the download page and select the latest version.
1. Extract Android 13 from the downloaded file to your desktop.
2. Rename the file to GSI.img
3. Download and extract AA - Install Android to your desktop
4. Move the GSI.img file to the install folder.
Double-click on AA - Install Android.
Turn off your phone.
Press and hold Volume+ Power and Ptt button until you get to the bootloader menu.
Select Fastboot mode.
Connect your USB cable to your phone, Look at your phone, and press Volume+ button 2 times when prompted to start. That's all. Sit back and relax for a couple of minutes.
The installation script will install your chosen Android version and reboot the phone when everything is done. After boot install Magisk25.
.
Udate:
I have created a new lk.img file to remove the 'Orange State' Warning during boot of Android.
The file is added to the installation scripts.
Hi,
I've just intalled SparkOS (the same file you show in the tutorial) on my WP17.
The default camera has been replaced and now I can't use the triple camera or infrared.
I was wondering if you knew how to install/flash the NightVision Camera_Oukitel WP17.zip back onto the phone. Or maybe where to put the files?
Best regards, picipi.
PS: keep on the great work!
.
No. Sorry, not yet. The problem is the drivers for the camera. The Android version your phone is shipped with has these drivers pre-installed. As I wrote before, if you flash GSI or other versions of android, these drivers are not included, and you will have problems with your camera.
This forum is aimed primarily at those who have had problems with their phone and need help getting their phone to a working condition for calling and normal daily operation. However the NightVision Camera can be partly fixt by installing the default camera app.
It's important for EVERYONE with Android 11 stock firmware, to extract a copy of the firmware as a backup, before flashing other GSI roms. And share a link here on the forum, so others can restore their phones to.
There are many ways to do this. Find a method that suits you best:
pull Stock Android Firmware - Google Search
Perhaps this one for Windows users:
How to use SP Flash tool to backup Mediatek firmware
Update: I suggest you use Wwr tool + SP flash tool for the dump instead of SP Flash tool alone as you can proceed without first having the scatter file and using MTK Droid Tools (which is now outdated
www.hovatek.com
PS..
When you extract you firmware. DO NOT copy the USERDATA partition!, this partition can hold up to 20-40 gigabits of your old useless user data, of you using your phone on a daily bases.
.
--- BlissOS Android 13 and lightning fast ---
This rom has the bare minimum of needed apps, no bloatware and lightning fast.
highly recommended and fit's the Oukitel WP17 spec perfectly.
Download the rom here:
BlissOSv16.0-arm64-bgN-slim-Unofficial
1. Extract Android 13 from the downloaded file to your desktop.
2. Rename the file to GSI.img
3. Download and extract AA - Install Android to your desktop
4. Move the GSI.img file to the install folder.
Enjoy ...
If you choose to go back to stock rom, and you have formatted the phone to flash GSI, is the precise partition deleted, and you end up with missing google key / Red txt on the top of your phone.
Here is the file you flash to get rid of that Red txt…
Code:
fastboot flash persist persist.img
_____________________________________________________________________________________
Update:
Some users reported it doesn't work for them.
For me it did the trick, but it doesn't work for everyone.
.
.
.....
Hey, thank you so much, got my WP17 working again but now I don't have IMEI and I'm getting a watermark saying "No google key and tee key" any ideas how to fix this ?
JustNabus said:
Hey, thank you so much, got my WP17 working again but now I don't have IMEI and I'm getting a watermark saying "No google key and tee key" any ideas how to fix this ?
Click to expand...
Click to collapse
.
The IMEI fix: https://forum.xda-developers.com/t/...rm64-a-b-treble-enabled.4504207/post-87571063
Working on a solution for the "No google key and tee key".
Don't forget to update the Android system for camera fix.
.
SwedishForenger said:
.
The IMEI fix: https://forum.xda-developers.com/t/...rm64-a-b-treble-enabled.4504207/post-87571063
Working on a solution for the "No google key and tee key".
Don't forget to update the Android system for camera fix.
.
Click to expand...
Click to collapse
I forgot to say that I don't have any backup on my IMEI and I've no idea where the box is. Is there any other way to get it ? I've sent an email to Oukitel but no answer so far
.
Yes. just copy and paste these numbers. Ore just scramble the numbers around.
IMEI 1: 35524555061532
IMEI 2: 35524555061573
If you don't want to use these IMEI numbers, you can just take the IMEI number under the battery from one of your old phones you already have lying around. it doesn't matter how old they are, even an old Nokia from 1990 works perfectly fine.
_______________________________________________________________________________________DisclaimerEditing or changing the serial number or IMEI of your device is illegal in some countries.
I take no responsibility for your actions. This is for educational purposes only.
.
To remove the Red txt "No google key and tee key".Some people have sent me a pm and say that flashing persist.img didn't work for them.
Try this instead:
Code:
adb devices
pm uninstall -k --user 0 com.mediatek.engineermode
Reboot the phone.
.
noob here, can you create a youtube video on how to install a custom rom to this phone?
dalelad said:
noob here, can you create a youtube video on how to install a custom rom to this phone?
Click to expand...
Click to collapse
.
It's not relay necessary.
There are only 4 small simple steps to perform, the Installer does everything else for you.
Oukitel WP17 [Root][GSI ARM64 A/B Treble-Enabled]
WP17 is a rugged phone with Infrared Night Vision Camera, Helio G95 8GB+128GB 6.78“FHD+ 90Hz 64MP Triple Camera+16MP Selfie 8300mAh Android 11 Global Version. Bought me a Oukitel WP17, but couldn't find much information about this phone. So...
forum.xda-developers.com
It's important for EVERYONE with Android 11 stock firmware, to extract a copy of the firmware as a backup, before flashing other GSI roms. And share a link here on the forum, so others can restore their phones to.
There are many ways to do this. Find a method that suits you best:
pull Stock Android Firmware - Google Search
.
{
"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"
}
StatiXOS for Redmi K40 | Mi 11X | POCO F3 (alioth/aliothin)
What is StatiXOS?
StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal while providing quality of life improvements and up to date security patches.
Spoiler: Known Issues
Changing the intensity of haptics does not work.
Battery stats in Settings show nothing.
Please report anything else you run into!
Spoiler: Download StatiXOS Here!
Primary
Spoiler: How To Flash
Detailed Flashing instructions in Post #3
Download the fastbootimage zip
Unlock your bootloader, and reboot to bootloader
Type in
Bash:
fastboot format:f2fs --fs-options=casefold,projid
[This will format all of the data in your phone including internal storage (photos, files, everything!)] (Skip this step if you are coming from a previous build)
Connect your phone to PC and type in
Bash:
fastboot update statix_alioth-XXXXXX-13-v6.1-TIRAMISU-img.zip
(XXXXXX denotes the date of the build)
Wait for a while until the flashing process completes, it will reboot your device
Enjoy!
Note: This ROM has GApps!
Spoiler: Stay in touch with our Telegram channels!
Official Releases & Announcements Channel
Android version: 13
Linux Kernel Version: 4.19.157
Source code: GitHub
Kernel Source code: GitHub
Code Review: Gerrit
Changelogs
6 February 2023
Initial build
7 February 2023
February 2023 Security patch
11 February 2023
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
23 April 2023
April Security Patch
Upgraded blobs to MIUI 14.x
Better pickup sensor implementation
Multi-Gen LRU enabled by default
Several Battery optimisations
5 May 2023
May Security Patch
Fixed the random reboot issues faced by some users
Detailed Flashing instructions:
NOTE: These instructions are for first time users only! If you are upgrading from previous StatiX Builds, you DO NOT NEED TO FORMAT DATA!
To flash StatixOS, you need these pre-requisites:
A PC with ADB/Fastboot installed
Redmi K40/Mi 11X/POCO F3 device
USB Cable
StatiXOS Build
Backup your internal storage before this process.
This guide assumes you are coming from MIUI 13.x with an unlocked bootloader.
For Windows Users:
Download SDK platform tools for Windows (do not use the latest platform tools, use any older than the r34) and extract it to anywhere you like.
Install ADB/Fastboot Drivers
Assuming you have unlocked bootloader, and enabled Developer Options, navigate to Additional Settings > Developer Options, scroll down to find USB Debugging, and enable it.
Connect your device to PC
From your PC, navigate to the extracted platform-tools
In the folder you need to check if there are some dll files and a few executables (.exe files). We're majorly concerned with adb.exe and fastboot.exe.
Whilst pressing Shift key, Right click in the folder, and there shall be an option to "Open powershell window here" or "Open Command Prompt here"
In the powershell window, type in .\adb.exe devices, now check your phone, there will a window asking to allow connection, allow it on phone. (If you don't do quicky, it may show as unauthorised in the powershell window, which is nothing to be worried about, just repeat the command)
Once the device is authorised, type in .\adb.exe reboot bootloader, your device shall reboot to a FASTBOOT screen, this is the bootloader mode.
Now ensure your drivers are proper. Type in .\fastboot.exe devices. If it shows nothing, it means that your drivers are not proper, google search on how you should fix them as it is out of the scope of this guide. Once you get an output like 2398534953 fastboot, it means that your device is detected.
(You do not have to do this step if you are upgrading from a previous StatiXOS build) In powershell, type in .\fastboot.exe format:f2fs --fs-options=casefold,projid userdata, this will completely wipe your internal storage.
Now, type in .\fastboot.exe update ''path\to\StatiXOS\Build\zip'' (replace path\to\StatiXOS\Build\zip with actual path to the fastboot images zip file) Pro Tip: You can right click and copy the zip and then paste into powershell window. Make sure you paste in between the quotes ' '.
It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
Wait till the process finishes, it will reboot the device automatically.
That's all! Enjoy StatiX on your device!
For Linux Users:
Install adb and fastboot according to your distro, and install proper udev rules.
Assuming you have unlocked bootloader, and enabled Developer Options, navigate to Additional Settings > Developer Options, scroll down to find USB Debugging, and enable it.
Connect your device to PC
From your PC, open Terminal
In the terminal window, type in adb devices, now check your phone, there will a window asking to allow connection, allow it on phone. (If you don't do quicky, it may show as unauthorised in the powershell window, which is nothing to be worried about)
Once the device is authorised, type in adb reboot bootloader, your device shall reboot to a FASTBOOT screen, this is the bootloader mode.
Type in fastboot devices, you'll get an output like 2398534953 fastboot, it means that your device is detected.
(You do not have to do this step if you are upgrading from a previous StatiXOS build) In powershell, type in fastboot format:f2fs --fs-options=casefold,projid userdata, this will completely wipe your internal storage.
Now, type in fastboot update ''path/to/StatiXOS/Build/zip'' (replace path/to/StatiXOS/Build/zip with actual path to the fastboot images zip file).
It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
Wait till the process finishes, it will reboot the device automatically.
That's all! Enjoy StatiX on your device!
Wow,
Yet another new rom for our great device,
i will have to give it a try soon,
would it be possible to make a "simple. zip" file that could be installed using TWRP or Orangefox recovery.
NOW FIXED By using Post no. 10
I wish you well with this rom and look forward to future updates
many thanks Murali
johnr64 said:
Wow,
Yet another new rom for our great device,
i will have to give it a try soon,
would it be possible to make a "simple. zip" file that could be installed using TWRP or Orangefox recovery.
I wish you well with this rom and look forward to future updates
many thanks Murali
Click to expand...
Click to collapse
I didn't make a simple zip file as custom recoveries don't support the new emulated storage changes.
Fastboot method is easier and more convenient than AOSP or in fact any recovery method.
Always having a PC is a good thing when flashing a ROM, as you can quickly restore your device to a working state without any worries if your device goes into bootloop (which should not happen with statix).
do you have some screenshots for this on poco f3? please post them
Update!
Changelog:
February 2023 security patch
Download from OP
exodius48 said:
do you have some screenshots for this on poco f3? please post them
Click to expand...
Click to collapse
Screenshots have been attached to OP
m_vaisakh said:
Update!
Changelog:
February 2023 security patch
Download from OP
Click to expand...
Click to collapse
Murali,
Your FAST.
Hi Murali,
I use a small standalone ADB program to install Temporary Recovery.
I have modified it a bit and added some basic adb FastBoot commands,
i have now included your install files as well:
-------------------------- UPDATED ! -------------------------
Now confirmed working
================================================================================
. ---------- Connect your phone to a PC in FASTBOOT mode to use this program ----------
.
.
Select Option:
.=========
.
1) Install TWRP Recovery (Remember to MOUNT SD Card in TWRP, wait 3 seconds and plug in your OTG adaptor)
2) Install OrangeFox Recovery (Remember to MOUNT SD Card in OFRecovery, wait 3 seconds and plug in your OTG adaptor)
3) Fastboot Devices
4) Reboot Bootloader
5) Reboot Recovery
6) Reboot
7) ADB Command line:
8) (WARNING)------------------ Format:f2fs
9) (WARNING)------------------ Install Statix_alioth-XXXX-XXXX XXXX-TIRAMISU-img.zip
10) Exit
.
.
. -To enter FASTBOOT, Power Off your Phone followed by Pressing and holding the Power and Volume down Buttons for 3 seconds,
.
.------------- Please read the INSTALL.txt file ---------------
.
Type option:
================================================================================
Also included in the .7z file are Magisk V25.2 and Migrate-GPE.
Download and unzip:
Statix-XXXX-XXXX-TIRAMISU + TEMP TWRP - OrangeFox (FASTBOOT) V1.0
Download Statix_Alioth-XXXX-XXXX-TIRAMISU, Rename it to rom.zip
and copy into the Statix_Alioth-XXXX-XXXX-TIRAMISU + TWRP - OrangeFox (FASTBOOT) V1.0.7 Folder.
Using this method, it is now easy to install this ROM as Murali explained and add Recovery if needed,
Thank you Murali for all your hard work,
I hope users find this little proggie helpful.
Update!
Hotfix for camera
Changelog:
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
Download from OP
m_vaisakh said:
Update!
Hotfix for camera
Changelog:
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
Download from
Apps in playstore not updating . always shows try again. Facebook messanger chats not loading .
Click to expand...
Click to collapse
Doesn't look like a statix issue to me. Did you format data using the given commands?
m_vaisakh said:
Doesn't look like a statix issue to me. Did you format data using the given commands?
Click to expand...
Click to collapse
Yes i am from MIUI 13.0.9 and formatted data .facebook messenger chat working fine but play store app updates not working. an now when plugging charger no sign of charging shown in the battery icon though the battery % is increasing. its only me with these problem? please look those.
gulmeli said:
Yes i am from MIUI 13.0.9 and formatted data .facebook messenger chat working fine but play store app updates not working. an now when plugging charger no sign of charging shown in the battery icon though the battery % is increasing. its only me with these problem? please look those.
Click to expand...
Click to collapse
You didn't understand my question. How did you format your data? What commands?
I didn't face any issue as charging indication not showing up, but one of my testers reported it today. I'll look into the issue.
m_vaisakh said:
You didn't understand my question. How did you format your data? What commands?
I didn't face any issue as charging indication not showing up, but one of my testers reported it today. I'll look into the issue.
Click to expand...
Click to collapse
(.\fastboot.exe format:f2fs --fs-options=casefold,projid userdata ) i used this
gulmeli said:
(.\fastboot.exe format:f2fs --fs-options=casefold,projid userdata ) i used this
Click to expand...
Click to collapse
That's correct. None of my testers, or I face the play store issue.
Can you try this?
Open Play Store > Tap on your Account picture in Top Right > Settings > Expand About > tap on Update Play store.
Or if that doesn't work, try rebooting the device once and check if your updates work or not.
m_vaisakh said:
That's correct. None of my testers, or I face the play store issue.
Can you try this?
Open Play Store > Tap on your Account picture in Top Right > Settings > Expand About > tap on Update Play store.
Or if that doesn't work, try rebooting the device once and check if your updates work or not.
Click to expand...
Click to collapse
Thank You Very much. it works fine now thanks again for the beautiful rom for great device.
Hi,
I tried the rom today,
the things i found:-
it seems to take a long time between the Poco F3 Logo and the boot animation,
i wasn`t able to find Face Unlock in the security setting,
Using the "Standalone ADB program" has made a massive difference,
as it simplifies every thing for me.
The rom is good but is in need of some TLC (Tender Loving Care),
I look forward to the next update,
Thank you again for all your hard work
m_vaisakh said:
I didn't make a simple zip file as custom recoveries don't support the new emulated storage changes.
Fastboot method is easier and more convenient than AOSP or in fact any recovery method...
Click to expand...
Click to collapse
I think you could explain also that this ROM uses vendorboot-as-recovery.
Hey guys, i have tested the new method posted by g96818 and it works perfect.
Since he has more experience than me with OnePlus rooting I'll delete this post soon.
My fear is the future proofing of my method and i understand that his method is better in the case of future updates and less risky.
Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.
hitzzzzzzzz said:
Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.
Click to expand...
Click to collapse
Hey man, but there is a full OTA for that, you just need to subtract the info you need from it.
Since i dont have that device, i dont want to tell you what to do.
Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451
scott.hart.bti said:
Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451
Click to expand...
Click to collapse
Yeah that's true that would be nice.
Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device
scottlam1 said:
Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device
Click to expand...
Click to collapse
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable
blasbenoit said:
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me and other guys in this forum.
Important notes to consider: A big thanks to azsl1326 he got us the Patched Init_boot to make this possible.
-You need to unlock the bootloader of your device. This means you'll lose the data ect ect ect.
-People are losing Netflix access after this process, right now we haven't found a "cure" for this, but is pretty normal if you have root a Oneplus device before, when i found the fix i'll edit this right away.
-I'll write this for experts and newcomers a like just in case so they don't have to start asking for simple questions.
-After the root some people have the issue that they cant use security like passwords, fingerprint...ect ect. (as of now the only fix they have is to reset everything and doing the rooting again for 2+times). If i find the "cure" i'll let you guys know.
Spoiler: Issues connecting your device to the PC?
To some people the USB debugging is not working at all, because the phone turn it off after you try to use it or connect it to the PC.
I personally had this issue so i just workaround it. This is what i did:
1- Connect the OnePlus to the same network as your PC.
2- Turn On Wireless debugging on your OP11 and select Pair device with pairing code:
3- Then use this on your PC after you open CMD of course:
Then put the code you have.
The check with this command to see if it is connected:
Now that it is connected you can enter bootloader and connect it to your PC in that mode normally with:
OK now back to the deal:
1- Download the latest platform tools from here:
-Unzip it and put it in the desktop for easy access.
2-The bootloader
Spoiler: Unlock the Bootloader
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
{
"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"
}
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot flashing unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
3- Flashing the Init_Boot.img
In this case i'll provide the already patched Init_boot.img for A07!!! so you don't have to look for it, is attached to this thread.
Download the img and put it in the same folder as the platform tools for easy access.
Spoiler: Magisk Canary
After you enter the device.
1. Dowload the Magisk Canary version from this link:
2. Install it on you device.
Spoiler: Opening CMD (Command Prompt)
After you got everything in place open the platform folder and type CMD on the location box, then press Enter.
If that doesn't work, just open CMD and type:
CD and write the location of the platform folder to get it to work.
Now to the "flashing"
Enter the bootloader like before to start, now type this:
The above command should automatically flash the init_boot to both the slots. However, if you face any issues while executing that command, then you could also manually specify the slots while flashing. Like this:
And
4-Restart your phone and check the magisk canary app that everything is OK.
Spoiler: Bypassing Safetynet
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
Download a safetynet check just to be sure.
And thats pretty much it, if you guys find some issues after the root, please post them here so i'll start adding more and more info about it for future references and fixes.
Click to expand...
Click to collapse
You are so helpful! This worked flawlessly!
ChrisFeiveel84 said:
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable
Click to expand...
Click to collapse
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key
scottlam1 said:
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key
Click to expand...
Click to collapse
i never use adb over wifi sorry
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first
ChrisFeiveel84 said:
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first
Click to expand...
Click to collapse
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated
H4X0R46 said:
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated
Click to expand...
Click to collapse
I didn't have an issue with my lock screen and stuff. I also didn't do anything to the phone other than unlock bootloader and root. Once I did this my lock screen and fingerprint and stuff wasn't an issue at all. Maybe I got lucky.
H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
The password issue has nothing to do with rooting, it is caused by unlocking the bootloader. Before you do any rooting, first lock and unlock the bootloader 3 times. After the third time, you can set the password (or pin, or pattern/etc) and THEN do the actual rooting.
Do you have boot.img instead i rather have temp root
i accidentally pushed the patched init boot img to phone before updating, now i keep getting failed system update, any way to revert back to original A06 init_boot.img so i can take update and then come back and root
SappyHanger said:
Do you have boot.img instead i rather have temp root
Click to expand...
Click to collapse
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.
blasbenoit said:
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.
Click to expand...
Click to collapse
can you point me to the init boot image on A06, i accidentally pushed the patched a07 version to a06 w/o updating to a07
So I did the above and magisk turns into a green android icon and won't start. It did start before I flashed the init boot.... ?? Tried to re-install magisk, same thing. green icon.....
Do I need to sideload magisk? (adb sideload Magisk-v25.2.zip) ???