tl;dr: I cannot save pictures or screenshots on my phone, as well as a few other small quirks, can someone help?
Hello XDA, I've just recently encountered a strange issue with my Nexus 5 and I was hoping one of you might be able to help me out. I'd like to have screenshots to break up the text wall, but due to the nature of my issue, that's out of the question.
So my big problem started about two days ago, when I wanted to flash the omnirom nightly (1/27 to be exact) to my phone.
While doing the factory reset before flashing the rom, TWRP got stuck (and I'm talking about 10 minutes) formatting /data not including internal media. I was left with no choice but to hold volume down and power and hope for the best. This is what I bet screwed things up. After that I tried again, and the formatting worked, and omnirom booted, but with the error message of something about device UIDs being inconsistent and recommending I format my data partition.
Well since the rom was a nightly, I felt like ignoring the message, but I did notice issues: I could install and uninstall apps, but none of them could really access the internal storage (for example, any attempts to save a picture, like through chrome, would fail. I also couldn't restore from titanium backup. Connecting to my pc would not display my files).
Dismayed, I obeyed the message and did a full wipe of the data partition and tried again (not just the factory reset one, but the full wipe of /data, and don't worry, I could still backup using ADB pull so I haven't lost anything). This caused the UID error message to go away but I still had issues-not as bad as before-but still issues. Titanium backup worked, so I used that to restore successfully, but I couldn't make new backups. I was frustrated and blamed my issues on using a nightly so I did another full reset and went back to stock.
Now, I wasn't given another UID message, and ALMOST everything works, but I am left with the issue that is the reason I post this thread. I can't take pictures, video, or screenshots and a select few apps fail to recognize the internal sd card (reddit sync, for example, will fail to save pictures when I try to download them, but other apps, like chrome, will succeed to do so, so it is a non-issue. I could also connect to pc again, yay!).
The camera (app and hardware) will still work, and I can tell it takes the picture because the little thumbnail that slides to the side after taking a picture appears. It just fails to save the picture. When I swipe to view the picture, it shows up only as a dark gray box. If I view it in the photos app, I am greeted with the message "media not found." When I try to take videos, Camera will force close the moment I press record.
I've tried a few things, like clearing the camera's data, but that was unsuccessful. Different camera apps (I tried Focal) result in the same problem. Using the Root File Browser app, I also made sure that permissions weren't locking access to that folder. I've also tried deleting the DCIM folder by connecting to PC and then taking another picture, but that still did nothing.
I don't know what else I could do besides another /data format, but I already did that and I don't feel like another format would really do anything since I already did one. I'm left with little that I could think would fix this, but I'm sure someone here could help me.
It is late now and I have school in the morning, so I'll check back on this thread in about 16 or so hours when I'm done with that. Then if anyone has a potential fix, I could try it. If I don't see a fix, I could post a video describing my problem or any more information you might find useful. Thank you all and goodnight.
fatwad said:
tl;dr: I cannot save pictures or screenshots on my phone, as well as a few other small quirks, can someone help?
Hello XDA, I've just recently encountered a strange issue with my Nexus 5 and I was hoping one of you might be able to help me out. I'd like to have screenshots to break up the text wall, but due to the nature of my issue, that's out of the question.
So my big problem started about two days ago, when I wanted to flash the omnirom nightly (1/27 to be exact) to my phone.
While doing the factory reset before flashing the rom, TWRP got stuck (and I'm talking about 10 minutes) formatting /data not including internal media. I was left with no choice but to hold volume down and power and hope for the best. This is what I bet screwed things up. After that I tried again, and the formatting worked, and omnirom booted, but with the error message of something about device UIDs being inconsistent and recommending I format my data partition.
Well since the rom was a nightly, I felt like ignoring the message, but I did notice issues: I could install and uninstall apps, but none of them could really access the internal storage (for example, any attempts to save a picture, like through chrome, would fail. I also couldn't restore from titanium backup. Connecting to my pc would not display my files).
Dismayed, I obeyed the message and did a full wipe of the data partition and tried again (not just the factory reset one, but the full wipe of /data, and don't worry, I could still backup using ADB pull so I haven't lost anything). This caused the UID error message to go away but I still had issues-not as bad as before-but still issues. Titanium backup worked, so I used that to restore successfully, but I couldn't make new backups. I was frustrated and blamed my issues on using a nightly so I did another full reset and went back to stock.
Now, I wasn't given another UID message, and ALMOST everything works, but I am left with the issue that is the reason I post this thread. I can't take pictures, video, or screenshots and a select few apps fail to recognize the internal sd card (reddit sync, for example, will fail to save pictures when I try to download them, but other apps, like chrome, will succeed to do so, so it is a non-issue. I could also connect to pc again, yay!).
The camera (app and hardware) will still work, and I can tell it takes the picture because the little thumbnail that slides to the side after taking a picture appears. It just fails to save the picture. When I swipe to view the picture, it shows up only as a dark gray box. If I view it in the photos app, I am greeted with the message "media not found." When I try to take videos, Camera will force close the moment I press record.
I've tried a few things, like clearing the camera's data, but that was unsuccessful. Different camera apps (I tried Focal) result in the same problem. Using the Root File Browser app, I also made sure that permissions weren't locking access to that folder. I've also tried deleting the DCIM folder by connecting to PC and then taking another picture, but that still did nothing.
I don't know what else I could do besides another /data format, but I already did that and I don't feel like another format would really do anything since I already did one. I'm left with little that I could think would fix this, but I'm sure someone here could help me.
It is late now and I have school in the morning, so I'll check back on this thread in about 16 or so hours when I'm done with that. Then if anyone has a potential fix, I could try it. If I don't see a fix, I could post a video describing my problem or any more information you might find useful. Thank you all and goodnight.
Click to expand...
Click to collapse
I would flash the stock image again to solve your problem, backup files first. Here is a tutorial http://forum.xda-developers.com/showthread.php?t=2513701.
gee2012 said:
I would flash the stock image again to solve your problem, backup files first. Here is a tutorial http://forum.xda-developers.com/showthread.php?t=2513701.
Click to expand...
Click to collapse
Thank you, it worked! Camera is saving pictures again and nothing is acting up. And it all was way less painful than I thought it would be
This is a very strange issue, I'll describe it here. I bought recently a OnePlus One in Spain. I've followed these steps:
1. Install CWM from High on Android guide
2. Install Android 5.1.1 from Gizbot guide (which comes from this XDA guide).
I finished the steps and got Android working perfectly. I love how smooth it is and all. However, I was ready to leave so I unplugged the USB (official cable). The phone freezes for few seconds and then it reboots. Now, I have tried many things and been in the same point many times, so there are two behaviours that can occur:
- When starting from the beginning with the cable unplugged, the Dirty Unicorn spinning wheel just freezes and reboot. It keeps doing so constantly. Reboot hell.
- When starting with the USB connected, but after a reset from disconnecting it, it goes into "Android is starting... Optimizing app 8 of X". There are two odd things here: the X is a different number each time it reboots, like 55 or 90, and then it freezes apparently at Google Apps and reboots again. Same reboot hell, but longer.
Now, I can turn it off, enter into recovery mode and reinstall everything. This is what allowed me to test exactly when it breaks. In any case it will only even start the Android 5.1.1 if the USB is connected.
My question is, any idea why this is happening? Any recommended step once inside Android to try to avoid this?Otherwise I'll try with another ROM, but I think that it's super odd and it looks like it might be fixed easily by someone who understands the system better than me...
Few extra details:
- Battery is 100%, so no apparent problem there.
- I'm using Ubuntu 15.04 on the computer side.
- I don't have a SIM card yet.
PS, if trying other ROM/gapps, which one do you recommend?
fpresencia said:
This is a very strange issue, I'll describe it here. I bought recently a OnePlus One in Spain. I've followed these steps:
1. Install CWM from High on Android guide
2. Install Android 5.1.1 from Gizbot guide (which comes from this XDA guide).
I finished the steps and got Android working perfectly. I love how smooth it is and all. However, I was ready to leave so I unplugged the USB (official cable). The phone freezes for few seconds and then it reboots. Now, I have tried many things and been in the same point many times, so there are two behaviours that can occur:
- When starting from the beginning with the cable unplugged, the Dirty Unicorn spinning wheel just freezes and reboot. It keeps doing so constantly. Reboot hell.
- When starting with the USB connected, but after a reset from disconnecting it, it goes into "Android is starting... Optimizing app 8 of X". There are two odd things here: the X is a different number each time it reboots, like 55 or 90, and then it freezes apparently at Google Apps and reboots again. Same reboot hell, but longer.
Now, I can turn it off, enter into recovery mode and reinstall everything. This is what allowed me to test exactly when it breaks. In any case it will only even start the Android 5.1.1 if the USB is connected.
My question is, any idea why this is happening? Any recommended step once inside Android to try to avoid this?Otherwise I'll try with another ROM, but I think that it's super odd and it looks like it might be fixed easily by someone who understands the system better than me...
Few extra details:
- Battery is 100%, so no apparent problem there.
- I'm using Ubuntu 15.04 on the computer side.
- I don't have a SIM card yet.
PS, if trying other ROM/gapps, which one do you recommend?
Click to expand...
Click to collapse
Same issue here, did you ever figure it out?
Had the same issue today but with another rom. Fixed it by first installing CM12 latest release and booting, then flashing custom rom + Gapps + Kernel.
Maybe this helps for you as well!
Hi guys
any solution to this issue?? It happens to me as well, now with latest Oxygen ROM (from yesterday).
When it is unplugged it will reboot. not if plugged in.
Help!!
Can you give us specific details as to what ROM, Kernel, and Gapps versions you used? This problem is a seemingly unfixable one at the moment.
Im new to all this so pay no attention if its nonsence...
My S5 G900f has a qualcomm snapdragon chipset, that doesn't support monitor mode, which i believe means that it doesnt support packet injections or packet capturing (driver related?)
using the dsploit.apk for things like session hijacking, replacing web page images of a target and using script 'injection' to inject custom java script into a target web page, all sounds like things you'd need monitor mode to do. and if it is then i was able to do it with my S5.
I dont know a lot about coding or how it all fits together and communicates with the hardware, so i may sound completely stupid, but this has done my head in for ages, so why not get it out there.
1. when i attempted to upgrade from my first custom rom, i had a bit of trouble, softbricked my phone and then flashed the two roms in various, alternate, wipe, format and install combinations until it finally booted to set up, and i stopped panicking. but this caused features from the first rom to appear within the second rom.
ie: 3minute battery mod was installed through a add-on zip along with the first rom and nothing to do with the second at all.
2. inconsistencies within the file system, like file names that were apps included with the first rom.
3. dsploit.apk was bugged and crashed every 5 or 10 minutes. then would seem to glitch or stutter for a couple seconds before correcting its self and accomplishing its pen test.
4. i also remember watching green text in the terminal as it failed to connect or ID some part of the system but continued to retry in quick succession until it glitched and worked. (i think this was a similar type of app i was trying out at the same time but instead of GUI stutters, i could see the text rapidly stuttering and glitching.)
4. the dsploit.apk worked for me back then, even though it was temperamental. ive downloaded the apk a couple times since with various roms and ive got no where with it...
was thinking maybe different aspects of the two roms had been filed or grouped together and created unstable triggers within the software, allowing it to briefly communicate with the chipset. i may be way off, but ive been sat here waiting for someone to solve this issue forever, i thought id share my thoughts, on the off chance it turns out to be something and i can finally get my S5 into monitor mode without OTG cables and other unwanted auxiliary components.
thanks in advance
G Carter
Do a clean install of you ROM, and please, don't panick. If you want to have a good time flashing ROMs and stuff, panicking is the last thing you want to do, it will cause stress and stress can lead to not being careful enough so stuff like this happens, well, always, if you are experiencing issues do a clean install. Just boot into recovery (I recommend TWRP) and wipe everything except external sd. Open ADB and sideload the ROM (or, if you have enough memory on a flash drive, plug it into your android and flash it from there) and then Google Apps.
I've seen a ton of "Sim Card Not Detected" threads here and elsewhere, but I think I'm having a different problem. It started yesterday, when my phone spontaneously rebooted (just looked over and saw the boot animation!) and came up saying "No SIM card", when it had been working fine a minute or two before. Since then I have tried:
* Rebooting, many times
* Reseating / cleaning the card, many times, both while powered on and off
* Cache wipe
* Factory reset
* Reflashing from factory image (m4b30z)
Here's where it gets strange. I get no GPS lock in Pokemon Go (grey pin in Google Maps, I haven't installed a dedicated GPS tester yet). I also don't seem to be able to rotate the screen -- I have checked that Auto-Rotate is enabled but it stubbornly refuses to change orientation when turned. All these things worked fine yesterday morning, so I have to assume the failures are related.
If a factory image flash doesn't fix it, I'm guessing it's not going to get better, but I'd at least like to know what kind of (hardware?) failure could lead to all those things going wrong at once. Is it worth bringing to the local repair shop (out of warranty, obvs) or do I just leave new Android iPod at home forever and start phone shopping tomorrow?
Sounds like a hardware problem since the software changes and resets did not resolve the issue.
If the screen and body are in good shape, I would look for a used Nexus 5 with a smashed screen and working motherboard to perform a motherboard swap. It's very easy to do.
Iam there too, seems last update broke something, iam switching to a custom rom
I bought the Oukitel WP10 as my replacement for my previous phone, an AGM X2, which is was getting on in age. Reasons for purchase: 5g, ruggedized phone, giant battery, POGO pins on the backside for connecting ???
The phone, physically, is fine, It's giant brick with a big battery, a decent camera and all the usual sensors are there. It as the potential to be a really neat phone....and then you boot it up. Something was and is.....not right. The developers lobotomized their rom. Why? Who knows. Will they fix it? {edit: they did sorta}. The app drawer is missing so the phone dumps all your apps out on the home pages. 3rd party widgets don't work : you can set them up but if you reboot the phone, they don't update. The recent apps tab works with gestures and 3 button navigation but only with the stock launcher, which appears to be launcher 3 but is named quickstep? 3rd party launchers load, but can not access the recent apps tab. Some 3rd party apps refuse to load producing various error codes. The user interface feels like someone had an iphone and tried to model it's interface to this phone. This person did not succeed.
I have emailed the company my complaints and reasonably expect nothing to happen as I am sure the person who did this to this phone did it on purpose. May they be cursed with pubic lice and hemorrhoids.
That being said, if the phone's UI could be fixed, it would be a really nice phone and I have plans to mate those POGO pins with an Arduino or a PI because, let's face it, they aren't gonna make any accessories, are they? But I can make some really neat ones out of an Arduino and a 3d printed cover that fits over those POGO pins.
So the plan will be: 1. Root the phone - accomplished. 2. Compile TWRP against it. 3. Modify the stock rom so it it is fully functional. 4. Begin development of a customizable Android 10 rom. 5. Begin development of an Android 11 rom.
At this time, I can confirm that the bootlooder can be unlocked, you can sideload things with ADB, and a stock rom apparently exists and can be accessed through the Oukitel website. There is some kind of flashing tool too, but everything is in chinese. I downloaded the stock rom and it appears to be the same build as on the phone. I tried flashing just for giggles but kept getting signature errors. There was something in the chinese instructions about coping and renaming some files prior to flashing but I have not had time to figure it out yet as it is all in chinese.
I will be trying to extract the boot img as it appears that Magisk would work if I can patch the boot img and reflash. If/when I am successful, I will post it here. Any help is welcome.
**** 02/03/2021: Well wouldn't you know it, they released an update....so maybe not do this right away*******
Guide to rooting the Oukitel WP10.
disclaimer: I have tried to make the steps straightforward yet detailed. This is a high-risk activity with a high probability of failure.
Prologue: This guide assumes basic familiarity with ADB, fastboot, sideloading, and booting into your recovery. Please note ADB, fastboot commands will vary slightly depending on your installation, and whether you are a PC, a Mac or a Linux box.
Preplanning: inevitability screwing up your phone.
i. Back up, copy over and otherwise remove any valuable data from your phone. This process will delete all your old data.
ii. Obtain a copy of the stock rom. At the time of writing it is: OUKITEL_WP10_EEA_V10-R11 .zip which is hosted on Mega. You can find it at the Oukitel site -> Downloads.
iii. To reflash the stock rom you apparently need a tool called SPMDT. I am not familiar this tool and the instructions from Oukitel are all in Chinese so this will not be covered here at this time. It may be easier to do all of this using SPMDT. Review chinese Oukitel instructions on how to swap checksums and how to use SPMDT to restore your phone.
1. Install Magisk Manager - this is the tool we will use to root this phone. A more detailed explanation about how it works is here. Download directly on your phone and install or download to your computer and sideload using ADB.
Code:
adb install MagiskManager-v8.0.7.apk
2. Open Magisk Manager and verify that you can install Magisk. This phone does have a ramdisk, is encrypted but does not have a/b partitioning. There are 3 options: At this time, I can't find a TWRP custom recovery and do not yet know how to make one so downloading a zip to load with TWRP is not possible. A direct install seems to be for updating a previous Magisk installation? I am not sure and available information seems ambiguous. This leaves option 2: patch the stock boot image.
-2a. On your computer, open the stock rom and extract the boot.img file. Using ADB, upload it to your phone:
Code:
adb push boot.img /sdcard
This should send it to the users default directory. The /sdcard part may vary.
-2b. Open Magisk Manager on your phone and select option 2. Choose the boot.img file and Magisk will give it the clap.
-2c. Download the file to your desktop. Can probably open "Android Storage" in your file system and copy it over or use the following ADB command:
Code:
adb pull /sdcard/Download/magisk_patched_mzhsO.img ~/Desktop
Again, the *.img name and your preferred directory may vary and adjust command syntax for your OS.
3. Unlock the bootloader. You must first enable developer tools on your phone and then go to Settings ->System ->Advanced ->Developer Options -> OEM unlocking (turn slider on). This does not unlock the bootloader. It just allows you to unlock the bootloader. To unlock the bootloader, plug your phone into your computer using the USBc cable, make sure USB debugging is on and reboot your phone into fastboot by holding down the vol up and power buttons as the phone reboots. In the bootloader menu, choose fastboot by using the volume up to cycle through the menu options and then the volume down key to start fastboot. When all is ready:
Code:
fastboot flashing unlock
and a teeny-tiny prompt will pop up asking if you really want to do that. Use volume keys to navigate.
To relock the bootloader later (not now):
Code:
fastboot flashing lock
will button it up again. You might not need this ever.
4. I can't remember if it forces you to reboot at this point but if it does, just boot into fastboot again. Do not try to install the modified boot img file yet. If you do, you will send it into a fastboot bootloop (soft bricking your phone). This happened to me. I then learned that this phone, and I assume, most android phones past Android 8 are protected by Android Verified Boot which is part of a system that verifies that the firmware you are running is legit. In this case, it causes the bootloader to verify the boot and recovery partitions. We have to disable it to install the modified boot img. I borrowed the following commands from these threads here and here and here
-4a. vbmeta.img apparently contains checksums of the boot, recovery and maybe system partitions. The guy from the first link installed a custom vbmeta.img using the command below. I do not know whether this is generic vbmeta, whether it is vendor specific so I did not use the custom vbmeta he created.
-4a. Since I didn't know whether to use a vbmeta.img from another phone, I poked around until I found the 3rd link above which stated that I could just use a dummy vbmeta.img generated by using a python script AVBtool
I cloned it into Pycharm (or your preferred IDE...or you can rawdog it from the command line) from Google's github and ran the script as below:
Python:
avbtool make_vbmeta_image --flags 2 --padding_size 4096 --output vbmeta_disabled.img
-4b. I installed the vbmeta_disabled.img using fastboot.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_disabled.img
-4c. I then installed the modified boot.img (as discussed above):
Code:
fastboot flash boot magisk_patched_mzhsO.img
-4d. and rebooted: fastboot reboot
5. The system rebooted into the modified stock rom and I reinstalled everything I had backed up earlier. I confirmed Magisk had given me root access. HOWEVER: SafetyNet failed the ctsProfile check! There seems to be a fix for it here but since I don't know what it means or what it does and since the phone appears to be working, it will have to wait for later.
Epilogue. I am happy to report, that, after a bit of fiddling around, Magisk's Quickswitch module coupled with a very dodgy alpha Lawnchair2 apk I got from APKmirror through their Telegram group has resulted in a mostly functional rom! I now have an app drawer and gestures mostly works with the Lawnchair 2 launcher. Widgets still need to be reinstalled if you reboot. So...it now sucks a lot less.
Gentle reminder: this guide is rough and the result of only 1 pass through. And I screwed it up.
Due to an OTA update being provided from Oukitel it became necessary to learn how to use the SP Flash Tool.
Guide to reinstalling the Stock firmware for your Oukitel WP10.
(the bootloader will remain unlocked if you unlocked it as in the previous post)I loosely borrowed from the gents at GetDroidTips This process assumes you are using a Debian based linux distro.
1. Download the stock rom OUKITEL_WP10_EEA_V10-R11. Extract rom folder.
2. Download the latest SP Flash Tool . Extract.
3. On linux, there is an error regarding libpng12 which deprecated in newer versions of linux. For the reckless, a nice person from SO made up a custom .deb to install to fix this problem here. Otherwise you have to manually install it so that this program can find it.
4. Open your SP Flash Tool folder and run flash_tool. A nice little gui should pop up if it runs.
4a. Go to the Download tab and choose "MTK_AllInOne_DA.bin" as your download agent.
4b. Under scatter-loading file, navigate to the stock rom folder and "MT6873_Android_scatter.txt" should be the only option and choose it.
4c. Reading the windows instructions here recommended unticking the "preloader" in the payload section below these options on the Download tab as it might brick the phone, so I did. I do not know if this is necessary.
5. Turn off your phone. Then plug the USB cord in and hold the volume up key down so the flash tool will detect the device via USB. Can also try holding the volume down key down. Do not press power button like you would if you were planning to boot into fastboot.
If all goes well the flash tool will reflash the stock rom and reboot into stock rom. The bootloader will remain unlocked until you use fastboot to relock in the post above. There was an OTA update yesterday: OUKITEL WP10 EEA_V14_20210118 . The phone UI feels a little snappier but it appears that the stock rom launcher still does not have an app drawer. This might be a Google thing and not a Oukitel thing. However, 3rd party launchers with app drawers now work with 3 button navigation! The recents tab and app drawer appear to be functional. Gesture control still appears to be not functional with 3rd party launchers and some but not all not all widgets will update after a reboot. Cause to be determined. I have not tried to repeat the root procedure above.
hello, I am new and have been looking for threads about rooting c19 oukitel, but seems non exists. How could i start one?
dreadeye said:
hello, I am new...
Click to expand...
Click to collapse
....for phones that have a small user base, you can just start a thread for your phone under general like I did. Xda may be like Stack Xch where you need to have a certain number of posts before you can start your own thread. I don't recall. If so, you will have to reply to some posts first.
calfax said:
Will they fix it? {edit: they did sorta}.
Click to expand...
Click to collapse
Hey Calfax, not to hijack your thread, but I am thinking about getting this phone, would you mind explaining what the new update did and did not fix?
glitchhawk said:
Hey Calfax, not to hijack your thread, but I am thinking about getting this phone, would you mind explaining what the new update did and did not fix?
Click to expand...
Click to collapse
It fixed your ability to use a 3rd party launcher. It did not fix the widgets issue. I think this is an Android 10 issue more that Oukitel specific. Having a phone with an 8000 mAh battery has helped tremendously over the last few days.
The phone does not like to use 4g data and I do not know why.
sup op,
Just got oukitel wp10 today. I have just done a quick read through everything here and am probably going to try and get root going asap.
I have read elsewhere that treble based phones (such as this one) can basically have any treble enabled custom rom installed on them. I know very little about this but is it a concept your are familiar with?
am very glad someone has taken the intitiative here regardless. thanks for that!!
p.s. ditto on the pubic lice and hemorrhoids thing and also for whoever designed the xda app
Also, I bet the 4g issue your having is related to what bands the phone operates on. Who is your carrier?
I have obtained root and have a few nuggets of wisdom to offer regarding OP's instructions. First off BIG THANKS TO OP ONCE AGAIN FOR TAKING THE INITIATIVE!!
1. The first problem I ran into was with creating a vbmeta dummy image at OP's #4a in his second comment on this thread. There is a link to AVB Tools in the first paragraph and what is supposed to be a link to the tool on google's github page in the second paragraph but the link in the second paragraph to the github page is not working, so I defaulted to the first link but the AVB tool on that page, for whatever reason, is not working properly, while the tool on googles github page DOES WORK AS INTENDED.
I think what OP intended to link to was the following: https://github.com/PixelExperience/external_avb
REGARDLESS, I have attached a copy of my vbmeta "dummy" image to this post, so you can just use that instead if you prefer.
2. If you update your phone after isntalling magisk, you will have to go through the fastboot process again, and yes this means YOU HAVE TO DO THE VBMETA STEP AGAIN BEFORE THE MAGISK STEP OR YOU WILL BRICK YOUR PHONE.
3. I bricked my phone and was having trouble running the SPFLASH tool, linked in OP's third comment on this thread. IF YOU ARE HAVING ANY TROUBLE RUNNING THIS TOOL JUST DOWNLOAD THE LATEST VERSION OF UBUNTU AND RUN THE SPFLASH TOOL FROM AN UBUNTU LIVE USB. I tried on a couple different linuxes with the right kernel version and still had trouble so just do it from ubuntu live if you are having trouble.
4. If you are stuck in a bootloop like I was, you can still run the SPFLASH tool. Just get the tool setup, press download, then plug in your phone and hold the volume up button as it enters the off-stage of the bootloop, the SPFLASH tool will pick it up and start the flash process if you time it right.
5. OP says he is still having trouble with third part launchers but I was able to get Nova launcher running by installing it, then when holding down on the nova launcher icon on the home screen of the default launcher, there is an option to make nova the default launcher from there. idk if every 3rd party launcher will be able to do this, but Nova was.
6. OP also mentioned having issues with gestures, and pointed to it seeming to be a Google issue, and I have confirmed that it most certainly is, as there is a message in My Nova launcher settings that says:
Android 10 gestures Navigation
Google has not yet made gesture navigation compatible with 3rd party launchers. There is nothing that Nova Launcher can do to change this until a future Android update.
Click to expand...
Click to collapse
CURSED BE TO GOOGLE. PRAISES TO OP
Found this in the stock rom zip and translated it (was half in Chinese). Thought someone might find the info useful
Project Name: S1000D-Cloud Base-S85
Clients: Ozzie ...
Customer Configuration:
MT6873, FLASH: 128GB+8GB (Integrated UfS+DDR4X), Global GSM 4-band (2/3/5/8)+W 7-band(1/2/4/5/6/8/19, with RXD)+TD 2-band(34/39)+TDD 5-band(34/38/39/40/41)+FDD 18-band(1/3/5/8)+W 7-band(1/2/4/5/6/8/19, with RXD)+TD 2-band (34/39) + TDD 5-band (34/38/39/40/41) + FDD 18-band (1/3/5/5/6/8/19, with RXD 1/2/3/4/5/7/8/12/13/17/18/19/20/25/26/28A/28B/66) + CDMA 3-band (BC0/BC1/BC10, with RXD) + 5G 11-band (N1/3/5/8/20/28/38/41/77/78/79），Support NFC,support LCD screen (3 and backlight), support 9V2A charging, support oncell/incell TP (motherboard does not support separate TP connector), three rear camera: 4800W main rear camera+1300W wide angle camera+200W macro camera does not support thermal imaging, front camera 1600W, support fingerprint, battery built-in non-removable, does not support front flash, support secondary board SIM card, does not support T card, does not support RGB signal light (FPC), does not support HALL, support side buttons, support earpiece (connector FPC), support dual silicon wheat (main mic sub-board patch, sub-mic motherboard patch), smart amplifier, support TYPE-C headset (sub-board end), support light distance sensor (FPC), support G-Sensor, support GPS/WIFI/Bluetooth/FM, support geomagnetic, support gyroscope, support OTG, support rear camera flash (connector, FPC), support/laser distance measurement (sub-bo
ard end)/temperature measurement/night vision (plug-in) Support wireless charging (sub-board compatible）, Does not support UV / heart rate/air pressure / volatile gas detection/intercom plug-in / encryption chip/night vision fill light (FPC), antenna shrapnel (battery cover full paste&screen shrapnel full paste), support motherboard side ANT6 antenna, support motor, support power button，
Software version: //192.168.1.50/alps_q0_mp2_1/s1000_mt73_A_L/s1000d-yj-s85-a2-66-l-128G8G-fhdp-bom5-q0-cts-eu/R11
Release Date: 2020-12-17 16:08
LCD: 6.67FHD.Huaxing glass, middle perforated, cover glass Corning 3rd generation FT8756
SENSOR:
Wide Angle CAM Win-win-win-win-win I., SWAQ6925001A-VA S5K3L6XX03-FGX9
Macro Shadow Collar I., YL-YJS85-02M1-WJ 200W GC02M2
Post-secondary Shadow Collar I., YL-YJS85-02M1-WJ GC032A
Ex CAM Win-win-win-win-win I., SWAC205S100B-VA S5K3P9SP04-FGX9
Flash Model:
UFS+LPDDR4X(128GB+8GB) H9HQ16AFAMMDAR-KEM
UFS+LPDDR4X(128GB+8GB) H9HQ15AFAMADAR-KEM
UFS+LPDDR4X(128GB+8GB) KM8V8001JM-B813
Language Type: Multi-lingual
Version Download Instructions: Normal download, no need to erase
Download tool version: SP_MDT_AFterSale_20.32
Release Notes: First Archive
Click to expand...
Click to collapse
Hard bricked my wp10 with spflash. DO NOT FORGET TO UNTICK PRELOADER USING SPFLASH TOOL.
Hopefully the oukitel people can help cause I have spent hours now trying different fixes and have only managed to get a blank black screen by opening the phone, unplugging and replugging the battery (so technically some progress). But i can't justify spending any more time trying to fix.
This phone is (was) great and its nice to have no restrictions on rooting or whatever but great power/responsibility/etc, u know the drill
kinda surprised there isn't more activity around this phone on XDA though Cuz it is a sweet one.
Has anyone pursued anything further with this beast of a phone?
I have purchased one and used it several weeks now, and did find the operating system leaving a lot to be desired, and really dislike the iPhone-like swiping gestures that I initiate accidentally all the time. My company phone for my job is a newer iPhone with the same gesture motions, unlike my previous employer-provided iPhone.
This WP10 has amazing potential but really could still use a better custom ROM.
And my 6800mah Blackview BV9800 battery outlasts this 8000mah battery.
My biggest complaint so far is the GPS fixing using Locus Maps Pro or Google Maps.
I get a display of a multitude of satellites within view,but within 5 seconds, all GPS satellite fixing disappears on the Locus satellite display screen,and I can no longer get a location fix.
Same problem with Google maps, although I don't have any advanced tools to see the satellites being used as I do with Locus.
With locust, I can refresh the GPS connection and they reappear, but then still disappear immediately. This is very annoying when using a rugged outdoor smartphone for rugged outdoor navigation.
I might be replacing the faulty touch screen interface on my 1-year-old Blackview BV9800 if I cannot find an easy solution for this Oukitel WP10GPS issue.
A custom ROM or updated upgraded ROM would be very nice!
I'm not sure why the battery does not last as long as the Blackview's smaller battery, but I liked the size of the battery on this better than the current flagship Blackview models, and I also liked the more ruggedized case with far more screws securing the case halves together.
The BV9800 was the last of its kind from Blackview, the BV9900 has a slightly smaller battery and a less rugged appearing case, & the new 5G rugged version using the BL6000 is just an upgraded 5G version of the BV9900, same case design, battery still smaller than BV9800.
This is why I jumped ship after 3 Blackview rugged phones and tried out this Oukitel WP10. It has potential to be superior to the BV9800, but ROM issues are making me question switching back to the BV9800.
chuck.lambert78 said:
Has anyone pursued anything further with this beast of a phone?
I have purchased one and used it several weeks now, and did find the operating system leaving a lot to be desired, and really dislike the iPhone-like swiping gestures that I initiate accidentally all the time. My company phone for my job is a newer iPhone with the same gesture motions, unlike my previous employer-provided iPhone.
This WP10 has amazing potential but really could still use a better custom ROM.
And my 6800mah Blackview BV9800 battery outlasts this 8000mah battery.
My biggest complaint so far is the GPS fixing using Locus Maps Pro or Google Maps.
I get a display of a multitude of satellites within view,but within 5 seconds, all GPS satellite fixing disappears on the Locus satellite display screen,and I can no longer get a location fix.
Same problem with Google maps, although I don't have any advanced tools to see the satellites being used as I do with Locus.
With locust, I can refresh the GPS connection and they reappear, but then still disappear immediately. This is very annoying when using a rugged outdoor smartphone for rugged outdoor navigation.
I might be replacing the faulty touch screen interface on my 1-year-old Blackview BV9800 if I cannot find an easy solution for this Oukitel WP10GPS issue.
A custom ROM or updated upgraded ROM would be very nice!
I'm not sure why the battery does not last as long as the Blackview's smaller battery, but I liked the size of the battery on this better than the current flagship Blackview models, and I also liked the more ruggedized case with far more screws securing the case halves together.
The BV9800 was the last of its kind from Blackview, the BV9900 has a slightly smaller battery and a less rugged appearing case, & the new 5G rugged version using the BL6000 is just an upgraded 5G version of the BV9900, same case design, battery still smaller than BV9800.
This is why I jumped ship after 3 Blackview rugged phones and tried out this Oukitel WP10. It has potential to be superior to the BV9800, but ROM issues are making me question switching back to the BV9800.
Click to expand...
Click to collapse
i think the gesture issue might be an android 10 problem although i dont recall having this sort of problem b4 bricking my phone.
the gps issue i did experience and i can say that on other devices i have seen improvement to gps services from installing custom rom, walking/driving forward while trying to get directions or current location on map app, also enable wifi and bluetooth monitoring (google.says it helps but in most situations/locations i doubt it does)
É possível instalar o gsi treble rom no wp10? Notei vários erros.