I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
finnroth69 said:
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Your device already have TWRP [Firmware version: OUKITEL_WP16_RU_V04_20220621 ] but you not need Custom Recovery for install GSI. Use stock recovery.
About GSI with a night vision camera support so is much expensive solving that. You can try but need very experience and patience of the tests and solutions.
lopestom said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
finnroth69 said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
No! Search my repository in the github in the release option.
finnroth69 said:
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
Click to expand...
Click to collapse
As I wrote before, it is very difficult to solve issues like the original stock ROM camera. There are even one or two people who managed to get this to work.
Now what you don't understand: If you want a Custom ROM, use GSI and adapt, solve, analyze and test by changing some stock ROM files in GSI. You must understand that you need experience and time. You can even compile a Custom ROM - any GSI - specifically for your device. So you just need to have the source code of your device, have the GSI source code and know how to compile the file so that you can do the tests. Again, you must understand that you need experience and time.
If you haven't researched what is GSI and still think that Custom ROMs portability that happened before until Android 7.1 then look, read and update yourself.
In your questions, be as detailed as possible. You write a lot of parts and you scramble the words.
As for having GSI normally I already wrote where there is an instruction to install and you follow. As for TWRP, look it up on my github.
As for solving something in the GSI, if you managed to install it and still used the phh options to try to fix any bad part, then it is only you who will be able to solve any error/adaptation/bug/extra installations that there.
Trust me when I say I understand what you're saying. I have done some testing I have watched tutorials, I have studied. but everything that I have seen is basically switching a file from a folder on the stock ROM to a folder in the ported ROM with the same name as what's in the stock ROM, and possibly adding a little script to something. What I'm trying to figure out is what I asked. Fstab is not in recovery on my phone's stock ROM. It is in something else. But fstab is in and a part of recovery for TWRP. So even though there might be a TWRP for my phone doesn't help me to know if I should be creating that same folder that's in my stock ROM in the ported one for fstab or other files that are like it. I have downloaded the TWRP from your profile and I've gone to the 4pda and discovered that you're the dev who ported it with and without encryption. Nice work and thank you! I would like to move beyond being a flash baby though. So I'm simply trying asking that one specific question to help me learn because it is something I am lost on. Whether it is to port recovery, port a ROM, or whatever, I don't know what to do when the location of the files I need to port from the stock aren't matching with the with the location of the files in the port itself. Fstab is just one example. I'm gonna send you a friend request. Later when I fire up my laptop, I'll take screenshots to physically show you exactly what I mean. Please be patient and don't get upset at me for trying to learn. As well as please take your time in responding. It's no rush since I've got a business to run and this is something I'm trying to teach myself on the side. It really is something I'm lost on, and if I'm lost on it, how many others has it confused as well?
As for the camera app issue. We can forget I asked that also. I understand completely what you're saying about it being far beyond my reach right now. Thank you for the heads up on that.
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
finnroth69 said:
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
Click to expand...
Click to collapse
The problem is not in the vbmeta file. You can use this one if you can: Post in thread 'Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO' https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
The big fact is that the company put a recovery.img stock file inside /vendor/etc/ and you should know how to deal with it. So only removing this recovery.img and repacking modified vendor.img made by u; install that in your device so you can have TWRP.
jwoegerbauer said:
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
Click to expand...
Click to collapse
I'm not sure to be honest with you. Like I told lopestom, I'm just trying to teach myself as I can in my free time. A lot of what I do is imitate what I see or read. While reading post about flashing twrp i had read something about flashing an empty vbmeta file.
Related
First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.
Please be sure and thank the person who decides to do your homework for you.
:laugh:
FlynnErik said:
First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.
Click to expand...
Click to collapse
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.
ryphil said:
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.
Click to expand...
Click to collapse
Fully agreed! That's why I came to the experts. I have done my homework but the thing is my homework leads me to several different files from before the ICS update. There has only been 1 thread on 1 forum that has been post ICS update, and no real feedback on it. I think I even found one that uses ADB (I understand that concept, but would prefer not to use it since I don't know Linux well enough).
I would love to know what files to use, which ones to stay away from. As I said I have the concepts, I have the understanding, its the actual files that I want to verify, I can rattle off tons of files from tons of sites, but they may or may not be correct (and may have the same name as a correct one but still be incorrect, ie "update.zip" appears a few times on different threads from different time frames).
There is only post in the teamhacksung CM10 wiki that was last edited 8/12/2012, but that could have been anything that was updated, not the files/links to be used.
So I thank you in advance for your help, and you will certainly get a thank you in the forum for help you are providing, I always give credit where credit is due.
Well here goes nothing, going to reboot (to ensure the Kies drivers are installed and loaded into the system 100%), and try the instructions from this link http://forum.xda-developers.com/showthread.php?t=1788625
It seems to work for most, the only concern I have is that I have a different end to the build than most others do (and I am not sure why?)
Did I screw myself?
I rooted, and have CWM installed.
Is it to late to create a ROM backup of my device for when i go to install CM10 (I need a drink for now, so I might install it tomorrow night lol).
That link I posted in the last post is good to go if anyone else needs a safe bet set of directions.
Seriously though, I didn't do a backup, am I screwed now?
EDIT: I just did a back up and it said no sdcard/.android secure found, skipping of backup of apps
and
no sd-ext found skipping backup of that.
is that normal? Did it backup to my microSD?
Still hope I didn't screw myself by backing it up after rooting.
First a few disclaimers to explain why I'm here.
- My secondary intention with this question is finding some answer as generic as possible to also help other people. Of course my primary intention is fixing my own issue, but the biggest part of it from what I can tell in the past 8 hours have been finding ROM files. All links are broken, except for 4.1.2 and none of those worked for me. In fact, they bricked my phone pretty hard.
- I'm on a mac. It's a nightmare finding tools for the mac, but I doubt any of them would really be any use for my case, one reason why I didn't even bother going for a windows vm. Another one is I'm traumatised by installing and running VMs. Finally this is for the challenge and learning a bit more.
- I've being trying to fix this through lots of research in the past 8 hours and I do know a few bits about going around and doing things (so sad this guide had no repercussion so far). But clearly, I'm dumb enough to brick my phone twice with no backups. At least could figure it out the first time (I had more time in hands as well). Please consider this. This means I've tried a lot of stuff you may wanted to advise, but it also mean I may have missed something obvious in the middle.
Okay...
By "bricked" I mean:
1. I can't go through the same process I did before to flash any CM image. CWM won't flash CM11 and CM12 recovery complains my bootloader isn't 4.4.
2. Both CWM and twrp recoveries should allow touch. None work, so I an't use twrp.
3. Battery keeps getting low and I've got no clue how to charge it to full again or even see how much it is at without installing twrp, which keeps getting uninstalled randomly at reboots, despite all of this topic about a solution. `fastboot getvar battery-voltage` doesn't show it. The mac script (which I was about to write myself based on op) also doesn't seem to help. In my case, I've removed the `./fastboot` because I've got it on my shell path.
I believe (1) happened, as I said on the disclaimer, right after I've flashed one of those 4.1.2 ROMs. By "flashed" I mean running the BAT file which mostly works on mac. ECHO of course wouldn't show the messages of progress there, but all fastboot commands do run.
And I also believe if only I could find 4.4 stock ROM files they might work or, at least, bring bootloader back to where it was so I could install CM12 again. And as far as I could notice without having Windows to try, no windows tool would really help here. That RSD Lite for instance, looks like it's just a GUI to run fastboot commands.
Above ALL
I just wanted to find a ROM stock file which I could fastboot flash into xt925 to reset it as hard as possible from zero and that the link will probably not break in the future for whoever may need it.
I figured THIS shouldn't be too hard to find, even for mac only, but it has been.
PS: Being able to fix the battery thing is also very important and quite a relevant follow up on the question! Right now I'm stuck with a ROM file that might work, but got no battery to try! ( 10 hours debugging now... )
only one stock kitkat rom for XT925 ! i'll upload this for you !
You know, if this works I'll have to, at least, go through some of your 187 posts and find a dozen or so to thank you way more than once!
I've now downloaded [this one](http://forum.xda-developers.com/showpost.php?p=63163078&postcount=6), which [he also posted again later on](http://forum.xda-developers.com/showpost.php?p=63272842&postcount=2), hoping it will do it! If it does, I'll try to upload in this post, as it looks like XDA hosted files last for much longer than anything else.
Only problem for flashing anything now is I can't seem to get enough battery!
I have a Wacom Cintiq Companion Hybrid ( DTH-A1300L ) android version needs help in so many ways. I bought it because I really need one for one of my jobs, yet can't really afford the crazy overpriced insanity that is a new Wacom so the reason it was so cheap was "can't connect to the Play Store. I know, hella foolish, I thought I could fix it by rooting it, but this thing is like level 10 as there is so little info as no one wanted to touch them it seems. I did find one guy on this forum that at one point rooted I am fair to average at rooting and the understanding of all that surrounds it. I have happily and successfully rooted my phones and tablet but I am no pro and fairly good at having gaping invisible holes in my info or logic when it comes to things like this.
Most frustrating is this thing is stuck on android 4 . 1 . 1 for no good reason I can imagine. It has dev tools installed after factory data reset but no google apps. (It arrived factory data reset)
I tried the relevant framework and store and the delete the cache trick to no avail. It can not update and can not even get to the Play Store.
Sooo the bad news is; no Google apps. No updates offered and stuck on some weird what looks like not stock version of 4 .1 .1 Jellybean.
When I plug it into my PC via USB it does not even show up in device manager.
The good news is I rooted it. Checked with root checker (unfortunately for now its Kingroot)
1. I have no idea how to make a back up from here. (no USB connection to PC issue)
or
2. what rom will work as my device is not listed on any of them. It would be great to find the stock rom as I am afraid this things cool and weird cintiq mode, pen function like abilities may be disabled or rendered useless with just any android rom.
Is there anyway to somehow find the stock OS on my device through boot loader? A place to find my stock or like rom. A clever work around?
Thanks in advance. for any who take up the challenge and offer any help or thoughts.
Cheers
Anyone know
What clockwork or custom recovery should I use?
Duende101 said:
I have a Wacom Cintiq Companion Hybrid ( DTH-A1300L ) android version needs help in so many ways. I bought it because I really need one for one of my jobs, yet can't really afford the crazy overpriced insanity that is a new Wacom so the reason it was so cheap was "can't connect to the Play Store. I know, hella foolish, I thought I could fix it by rooting it, but this thing is like level 10 as there is so little info as no one wanted to touch them it seems. I did find one guy on this forum that at one point rooted I am fair to average at rooting and the understanding of all that surrounds it. I have happily and successfully rooted my phones and tablet but I am no pro and fairly good at having gaping invisible holes in my info or logic when it comes to things like this.
Most frustrating is this thing is stuck on android 4 . 1 . 1 for no good reason I can imagine. It has dev tools installed after factory data reset but no google apps. (It arrived factory data reset)
I tried the relevant framework and store and the delete the cache trick to no avail. It can not update and can not even get to the Play Store.
Sooo the bad news is; no Google apps. No updates offered and stuck on some weird what looks like not stock version of 4 .1 .1 Jellybean.
When I plug it into my PC via USB it does not even show up in device manager.
The good news is I rooted it. Checked with root checker (unfortunately for now its Kingroot)
1. I have no idea how to make a back up from here. (no USB connection to PC issue)
or
2. what rom will work as my device is not listed on any of them. It would be great to find the stock rom as I am afraid this things cool and weird cintiq mode, pen function like abilities may be disabled or rendered useless with just any android rom.
Is there anyway to somehow find the stock OS on my device through boot loader? A place to find my stock or like rom. A clever work around?
Thanks in advance. for any who take up the challenge and offer any help or thoughts.
Cheers
Anyone know
What clockwork or custom recovery should I use?
Click to expand...
Click to collapse
Greetings and welcome to assist. If you have root yoy can try installing gapps through flashify it may work. For custom rom there is an excellent guide here
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and for custom recovery an excellent guide here
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. If you have root yoy can try installing gapps through flashify it may work. For custom rom there is an excellent guide here
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and for custom recovery an excellent guide here
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good luck
Sawdoctor
Click to expand...
Click to collapse
Thanks, I will see what I can find out and report back. Also editing from device to check date
sawdoctor said:
Greetings and welcome to assist. If you have root yoy can try installing gapps through flashify it may work. For custom rom there is an excellent guide here
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and for custom recovery an excellent guide here
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good luck
Sawdoctor
Click to expand...
Click to collapse
Excuse my noobness. Flashify looks good, I installed it, but don't I need some image from somewhere either the stock OS or a new one for it to work? Not sure how to get Gapps from there.
It did I think, find something, a "restore kernel" and "stock recovery" I am unsure did it find my stock kernel and recovery and or ROM and I should boot from that? ( again apologies a-lot of new info and its getting a bit swirly) In otherwords since my device is not listed any where and at this point any working Android version will do, I am wrong to try and reboot from this? These devices are supposed to come stock on 4.2.2, so I am hoping perhaps incorrectly it will go back to that? That would be ideal at this point.
So I can work again whatever works.
Also I a bit concerned about the "date" I posted from on one of these. I think I posted from the Wacom. Perhaps the problem in deeper than I thought as that is Linux time 0?
I think it self corrected but originally it said I posted on Jan 1 1970...
As for custom ROM, I probably wont be able to make my own custom ROM, even though I would love to take to the time to learn, for now I have too many art and work related deadlines.
I was hoping for one that already existed that would work with my device.
Perhaps I misunderstood something about how all this works? Also I do not have Unbuntu. I should as I support an open internet, but WINE really does not run the Adobe products I need for work so
I am stuck with Windows.
Duende101 said:
Excuse my noobness. Flashify looks good, I installed it, but don't I need some image from somewhere either the stock OS or a new one for it to work? Not sure how to get Gapps from there.
It did I think, find something, a "restore kernel" and "stock recovery" I am unsure did it find my stock kernel and recovery and or ROM and I should boot from that? ( again apologies a-lot of new info and its getting a bit swirly) In otherwords since my device is not listed any where and at this point any working Android version will do, I am wrong to try and reboot from this? These devices are supposed to come stock on 4.2.2, so I am hoping perhaps incorrectly it will go back to that? That would be ideal at this point.
So I can work again whatever works.
Also I a bit concerned about the "date" I posted from on one of these. I think I posted from the Wacom. Perhaps the problem in deeper than I thought as that is Linux time 0?
I think it self corrected but originally it said I posted on Jan 1 1970...
As for custom ROM, I probably wont be able to make my own custom ROM, even though I would love to take to the time to learn, for now I have too many art and work related deadlines.
I was hoping for one that already existed that would work with my device.
Perhaps I misunderstood something about how all this works? Also I do not have Unbuntu. I should as I support an open internet, but WINE really does not run the Adobe products I need for work so
I am stuck with Windows.
Click to expand...
Click to collapse
If you just want to be able to install apps from the playstore then this is a simple alternative
https://www.xda-developers.com/unshackle-your-device-from-the-google-play-store-with-apkupdater/
If your phone is rooted then flashify can flash zips like gapps without the need for a custom recovery. If you are serious about trying to make your own rom/recovery then use a virtualbox in windows. http://www.osboxes.org/ has plenty of prebuilt virtual linux machines that will run on windows
Regards
Sawdoctor
I appreciate all your help. I got the "google of every kind from Gapps on has stopped" is over, which was intense as it popped up every few seconds, I somehow got that to quit by reloading the proper one from the APK Pure app which was an odd work around but nothing else was working. Still have this unsettling bare bones screen and none of the stock apps as well as it being stuck in 4.1.1. This device was made for 4.2. and I assume it was on here at one point.
I wonder if that alone could cause hardware issues. I thought about taking out the battery, until I realized that thing is inaccessible as a thing can be without wrecking the industrial glues and taking the entire thing apart which sounds
like an accident waiting to happen and possible making things worse. I imagine that is last case scenario.
Like I said I would love to make my stock reload, at this point that would be great as this thing seems unstable and no trick makes the play store work or allow me to sign into the device with my google email.
I think you are saying to make my own recovery/ROM of my own device I need to do the virtual box thing. Correct? Or is that for writing your own custom ROM? I can try that; make my own recovery that is, as it is not on CWM or TWRPs supported devices list so I have no choice and all in all would prefer the thing to load as if it was fresh out of the box not this 4.1. One serious hiccup I have found trying to use my PC is my device is not recognized as a storage device or otherwise. Not sure if this is due to the weird settings of Cintiq mode or simply because the thing is in a very weird state of 4.1.1. So that may make making changes via computer impossible. I am not the type to give up. Thanks again Saw
Here also is a sum up I added to a the just basic question of Can you find the Stock from a recovery device. Basically is there any way to return a device to stock with no ROMs available to do so, as in extract if from the device itself.
Additional backstory if helpful.
"I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers."
Hello, I've tried to install multiple roms on my phone and none of them work.
I tried to install many versions of twrp without success. Some of them include twrp for Ulefone Armor 6, Armor 2, twrp for mediatek mt6750, mt6739, and even supposedly twrp for Ulephone Armor 5 (not to be confused with my model, which is 5s) and others.
I even tried orangefox, philz, redwolf and clockworkmod.
None of them worked. What happened is when I tried to boot into recovery, it would turn on, turn off, turn on again and boot into the stock OS.
I even tried to install ROMS without a custom recovery, using fastboot.
I tried a custom version of lineage os, supposedly made for ulefone armor 5 (I tried the arm64 a only version.) : https [column//] sourceforge [dot] net/projects/andyyan-gsi/files/lineage-16.x/
I tried resurrection remix too (oreo arm64 a only)
the command I used is fastboot flash system custom_rom.img
After installing each rom, each time I tried to boot a custom rom, it would turn on, show me the message that my device is in the orange state, shut off, reboot and repeat. So yeah, I bricked my phone. Then, I installed the firmware for ulefone armor 5s with SP flash tool and I'm back to square one.
I don't know if I should try graphene os, since inside a folder containing the image files, there is a text file which states that a sargo board is required, whatever that means. ("require board=sargo")
So yeah, I don't know what to do. I need a rom that is open source, and without gapps.
Any help is appreciated.
I'm even willing to try ubuntu touch, if that works
I'm even willing to try ubuntu touch, if that works
3simplex said:
This phone is a tank, I don't want to be stuck with Android 9 forever.
Click to expand...
Click to collapse
Do a Google search for:
"Custom ROMs for (your specific model number)"
If there are any ROMs for your device, that search will find them, if it does not find anything then there is nothing for your device. This means that if you want to use custom ROMs on your device, you will have to build your own TWRP or port TWRP from a similar device to work on your device then you will have to build your own custom ROMs or port custom ROMs from a similar device. If you're wanting or waiting for someone to build them for you, you are in for a very long wait. Developers build ROMs for the devices they personally own, they do not build ROMs for devices that other people own if the developer does not own the device. In other words, around here, we help people find what they are looking for but we will not do the work for them. If you want it but it doesn't exist, you will have to be the one to create it for yourself, not someone else.
Sent from my SM-S767VL using Tapatalk
3simplex said:
Great advice we are obviously idiots, thanks for pointing it out for us. I will Google search and see if I can find your balls. Hmm, nope I guess they don't exist. Troll elsewhere douche.
Click to expand...
Click to collapse
Who is trolling? Trolls get reported here, which I could do to you for the words you are using. I'll give you a pass this time because I'm a nice guy but that is your only freebie from me, your next disrespectful post will not receive the same exception.
What I posted is how things go here and what to expect, you just didn't want the truth. If that offends you, then that is a failing on your part. You're more than welcome to find another android website where they are willing to lead you by the hand and spoonfeed you when you want something that you are too lazy to find, do for yourself or have the ability to achieve on your own mental merit, because you surely won't find that here at XDA. If you choose to stay at XDA, be prepared to do the real work yourself.
Accept it or not, that is the way it is. Spouting childish insults won't change that.
Sent from my SM-S767VL using Tapatalk
Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup.
That said, does anyone know how long it typically takes for TWRP to be supported on a new device (i.e. G-Stylus 2021)? Just curious what the norm is. Thanks!
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
DM.IDOL said:
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
Click to expand...
Click to collapse
I'd look around on github
THIS is a TEST build for the Moto G stylus XT2115-1 minsk_t
(please mind that i have never done this before and i am at least trying to figure out how to create custom recoveries. i just need a good teacher with a little time. .)
*Touch Screen does not work. OTG mouse necessary.*
(not too sure how to fix this error)
*Mount points were for testing*
(modied fstab files in ramdisk to fix mount points)
*modified ramdisk and split_image from Moto G 9 plus unofficial 3.5.1 twrp*
https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-g9-plus-odessa.4195729/
i tried to put a recovery together for this device but im not sure where i went wrong or what to do next. booting into this recovery works but /vendor and /system_root have denied permissions. when it is flashed within twrp and rebooted to recovery or system the screen says no OS installed press power to power off. If anyone can help me figure this one out i would be greatly appreciative. If you need anything i can pull from my device just let me know. Anyone willing to help work on this recovery and figure out what needed to be fixed i would greatly appreciate it!
*EDIT*
i got /data to back without digest verification. Was not able to try to restore the backup as i got NO OS error when i rebooted to restore.
*EDIT*
i was able to figure out pretty much everything except the touch part of the recovery. it has a novatek_ts (NVT-ts)
not sure what to do to enable the drivers for twrp. any feed back would be great.
*EDIT*
Found the driver. I'll post it here and see what you can do. I'll also work on it as I'm still learning where stuff should go in the recovery. And also seems to b that i cannot access external sd from twrp either.
*EDIT*
resolved sd card issues. mountpoint was incorrect. only thing left to get working is touchscreen and not have to use otg mouse.
updated twrp for minsk_t is in files now.
*EDIT*
I found the proper elements to configure the recovery's touchscreen capabilities. Will be recompiling later on today. After I have tested it I will post the new working TWRP recovery. Thanks everybody.
*deleted*
sosthenisRR said:
*deleted*
Click to expand...
Click to collapse
So this is fully functioning now right? Is there any reason to use this over the OrangeFox recovery that has been posted?
Also, if I did install OrangeFox, and decided I wanted to install this later, would it be as simple as flashing using fastboot from ADB, overtop of OrangeFox? Or would the procedure be a little more complex?