Database Info

[Completed] Can Clockwork or another recovery program find and backup your truly stock ROM?

My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
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.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.

Duende101 said:
My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
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.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Click to expand...
Click to collapse
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help

Sam Nakamura said:
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Click to expand...
Click to collapse
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks

Duende101 said:
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Click to expand...
Click to collapse
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs

Sam Nakamura said:
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
Totally cool. It's a tough question.
The OG firmware thing is the toughest part to understand. Just wanted to make sure I was clear in my explanation and question.

Any updates on TWRP?

Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds

in_dmand said:
Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds
Click to expand...
Click to collapse
I was just thinking this the other day. The whole scene of Rooting and flashing ROMs seems to be coming to a dead end. Kinda sucks, I've always enjoyed tweaking my phone in my spare time..

in_dmand said:
Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds
Click to expand...
Click to collapse
Used to take 1-2 weeks when things were simple and easier.
Your comment about factory builds doesn't make sense considering you don't need TWRP to flash custom ROMs etc

Mackay53 said:
Used to take 1-2 weeks when things were simple and easier.
Your comment about factory builds doesn't make sense considering you don't need TWRP to flash custom ROMs etc
Click to expand...
Click to collapse
True, but it does seem like it has greatly hindered rom development... It wasn't until very recently there were any roms even available.

in_dmand said:
True, but it does seem like it has greatly hindered rom development... It wasn't until very recently there were any roms even available.
Click to expand...
Click to collapse
More cheaper phones will have a higher user base so more development activity.
I think Pixels already has solid software so not much to add and the high price point will hold it back a little

in_dmand said:
Seems like development in general has really dropped off over the past year or two. Used to be TWRP would be out within 1-2 weeks, now it's almost 3 months and nothing. Makes me sad to see us going the direction of accepting factory builds
Click to expand...
Click to collapse
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html

Root-Maniac said:
I was just thinking this the other day. The whole scene of Rooting and flashing ROMs seems to be coming to a dead end. Kinda sucks, I've always enjoyed tweaking my phone in my spare time..
Click to expand...
Click to collapse
No we all just have to move on to next generation rooting an modding. Magisk can be flashed, or the Manager App is used to patch the boot.img manually and flash it afterwards. GSIs ROMs can be flashed via fastboot from fastboot mode as well. So in my opinion it is fastboot flashing an GSI.img, Custom (optionally Magisk patched) boot, or Stock Magisk patched boot. That's it. It's even more, as it's back to the roots of adb and fastboot. TWRP has been there on U12+ for as long as the device exists, bit I never used it, as I switched to GSIs instead, and of on Stock the Magisk ROMs of LeeDrOiD and Team Viper could be easily installed through Magisk Manager. We should all have taken a look at phhussons work much earlier to accommodate to the things that got moving by Googles change in architecture when they introduced treble. We've only been to lazy, and many of today's users on this board, hardly know anything in-depth about adb and fastboot, but only scratch the three or four superficial standard commands. Technical affinity is more in demand again, and our good old adaptability.
Sent from my Pixel 4 XL using XDA Labs

uicnren said:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Click to expand...
Click to collapse
Oh wow, thanks for posting that! I certainly don't expect dees Troy to handle that difficult of a problem by himself with his wife pregnant and everything. Thanks again

5m4r7ph0n36uru said:
No we all just have to move on to next generation rooting an modding. Magisk can be flashed, or the Manager App is used to patch the boot.img manually and flash it afterwards. GSIs ROMs can be flashed via fastboot from fastboot mode as well. So in my opinion it is fastboot flashing an GSI.img, Custom (optionally Magisk patched) boot, or Stock Magisk patched boot. That's it. It's even more, as it's back to the roots of adb and fastboot. TWRP has been there on U12+ for as long as the device exists, bit I never used it, as I switched to GSIs instead, and of on Stock the Magisk ROMs of LeeDrOiD and Team Viper could be easily installed through Magisk Manager. We should all have taken a look at phhussons work much earlier to accommodate to the things that got moving by Googles change in architecture when they introduced treble. We've only been to lazy, and many of today's users on this board, hardly know anything in-depth about adb and fastboot, but only scratch the three or four superficial standard commands. Technical affinity is more in demand again, and our good old adaptability.
Click to expand...
Click to collapse
I agree on most points of you. GSIs are wonderful especially for phones at release start when there are no custom roms available yet.
And luckily device specific custom roms can be flashed over fastboot, too.
But for one reason i want a twrp for our device:
I find data backups with twrp much more easier as without. At least on my pixel 4 xl i miss a twrp somehow because Titanium Backup doesn't work on the gsi which i'm using.
I must create all my app folders again on my phone when i update it and backup all my stuff manually on my pc in extra folders and files.
I could spare me all that with twrp.
(I know there is the Google Cloud too as possibility but i refuse to use it)

dhacke said:
I agree on most points of you. GSIs are wonderful especially for phones at release start when there are no custom roms available yet.
And luckily device specific custom roms can be flashed over fastboot, too.
But for one reason i want a twrp for our device:
I find data backups with twrp much more easier as without. At least on my pixel 4 xl i miss a twrp somehow because Titanium Backup doesn't work on the gsi which i'm using.
I must create all my app folders again on my phone when i update it and backup all my stuff manually on my pc in extra folders and files.
I could spare me all that with twrp.
(I know there is the Google Cloud too as possibility but i refuse to use it)
Click to expand...
Click to collapse
Why do you refuse to use Google cloud

ceelos218 said:
Why do you refuse to use Google cloud
Click to expand...
Click to collapse
Because i don't want to feed Big G with my data.
And GSIs give me the possibilty to use my pixel without all the Gapps and the Google Play Service. That's a reason too why i like GSIs.

dhacke said:
Because i don't want to feed Big G with my data.
And GSIs give me the possibilty to use my pixel without all the Gapps and the Google Play Service. That's a reason too why i like GSIs.
Click to expand...
Click to collapse
Privacy is an illusion unless you go completely offline.

zetsumeikuro said:
Privacy is an illusion unless you go completely offline.
Click to expand...
Click to collapse
So we should stop fighting for this? Sry but that isn't a option for me.
Yes complete privacy isn't possible mostly but there are ways to improve it. With privacy friendly services, FOSS Apps such as AfWall, AdAway and Ad and Tracking Blockers in Browsers, Linux instead if Windows and no use of Gapps etc.
I know that my comment is probably off topic so sry.

dhacke said:
So we should stop fighting for this? Sry but that isn't a option for me.
Yes complete privacy isn't possible mostly but there are ways to improve it. With privacy friendly services, FOSS Apps such as AfWall, AdAway and Ad and Tracking Blockers in Browsers, Linux instead if Windows and no use of Gapps etc.
I know that my comment is probably off topic so sry.
Click to expand...
Click to collapse
No worries man my comment was also off topic. I too used to a lot of what you currently do. Even using the magisk script Energized which does blocking of ads,trackers etc. But when I saw the sheer amount of information Google has collected even when I opted out of it, just made me realize how futile it almost all is. These companies will never be 100% transparent and honest with us since they're making money off selling our information.

zetsumeikuro said:
No worries man my comment was also off topic. I too used to a lot of what you currently do. Even using the magisk script Energized which does blocking of ads,trackers etc. But when I saw the sheer amount of information Google has collected even when I opted out of it, just made me realize how futile it almost all is. These companies will never be 100% transparent and honest with us since they're making money off selling our information.
Click to expand...
Click to collapse
I have a hobby of reversing stuff, Ive given up trying to go private. With gms code I've seen, they check for so much it's ridiculous. I think a better method for the future is us (the custom rom community) coming together to find a way to block outgoing traffic via an open source app

Surge1223 said:
I think a better method for the future is us (the custom rom community) coming together to find a way to block outgoing traffic via an open source app
Click to expand...
Click to collapse
I think we already have this with AfWall+.

I just wanted to chime in here with a tip to help fill the TWRP void that many are facing right now, especially with Android 10. You can use a manual file flashing app to do most of the same things that TWRP allows you to do, minus the recovery part, of course. You can flash all the TWRP mods you want using this method without needing a custom recovery. Just in case some people didn't know.
You can even install image files too, which means you don't need to be tethered to a computer once you get all set up. This guide should help you understand the power of manual file flashers without having to rely on TWRP for installing certain mod files.

StrifeSoldierVII said:
I just wanted to chime in here with a tip to help fill the TWRP void that many are facing right now, especially with Android 10. You can use a manual file flashing app to do most of the same things that TWRP allows you to do. You can flash all the TWRP mods you want using this method without needing a custom recovery. You can even install image files too, which means you don't need to be tethered to a computer once you get all set up. This guide should help you understand the power of manual file flashers without having to rely on TWRP.
Click to expand...
Click to collapse
It's not Just about flashing. It's about recovery. You can't use a flashing app if you are in a bootloop.

Tulsadiver said:
It's not Just about flashing. It's about recovery. You can't use a flashing app if you are in a bootloop.
Click to expand...
Click to collapse
Oh definitely! Nothing worse than a bootloop. I was just specifically talking about the flashing part. I know a lot of people have been lost without TWRP, so they aren't installing certain mods as much right now since it takes more steps without it. But you can at least do the installing part without TWRP using a file flasher. I don't think as many people are aware of this. It's handy to know. You can use it as a stop-gap until TWRP arrives for any device you want.

the backup and restore functionality of twrp is what i am missing most. just in case something goes wrong with a flash.
is there a way to backup/restore without a custom recovery?

Turn a non-Project-Treble-compatible device into a compatible one?

Hi everyone,
Not sure how to put it, because I'm not trying to do anything illegal here, nor am I trying to make you guys cough up tips & tricks that could land you in jail in your respective countries, so just bear with me on a hypothetical level, OK?
My phone is a Leagoo T5c that shipped with Android 7.0. As such, it isn't de facto Project Treble compatible, and I shouldn't dream of flashing an AOSP GSI on it.
Thing is, I read this thread in the forum where it says explicitly that some devices can be made to be Treble compatible somehow.
If so, how? Does it involve rooting the device (suppose so, but I may be wrong), enlist it with Google someway or another, or something else?
I'm asking this because as some of you may know now, I would really like to upgrade the Android version on this phone, and have been hitting a brickwall for some time now, so before I completely ditch the idea and throw the phone away (not likely, because I don't have the money to buy another one at the moment), I want to make sure I've investigated all possible avenues.
Color me thorough. (or stubborn.)
EDIT: Where is the picture I uploaded? I only see its description at the end of my post, but I can't see the picture itself.

UglyStuff said:
Hi everyone,
Not sure how to put it, because I'm not trying to do anything illegal here, nor am I trying to make you guys cough up tips & tricks that could land you in jail in your respective countries, so just bear with me on a hypothetical level, OK?
My phone is a Leagoo T5c that shipped with Android 7.0. As such, it isn't de facto Project Treble compatible, and I shouldn't dream of flashing an AOSP GSI on it.
Thing is, I read this thread in the forum where it says explicitly that some devices can be made to be Treble compatible somehow.
If so, how? Does it involve rooting the device (suppose so, but I may be wrong), enlist it with Google someway or another, or something else?
I'm asking this because as some of you may know now, I would really like to upgrade the Android version on this phone, and have been hitting a brickwall for some time now, so before I completely ditch the idea and throw the phone away (not likely, because I don't have the money to buy another one at the moment), I want to make sure I've investigated all possible avenues.
Color me thorough. (or stubborn.)
EDIT: Where is the picture I uploaded? I only see its description at the end of my post, but I can't see the picture itself.
Click to expand...
Click to collapse
You would have to have an unlocked bootloader TWRP for your device, without that, there is no point in trying to find a GSI for your device and there is no point in trying to find a way to force your device to be Treble compatible.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
You would have to have an unlocked bootloader TWRP for your device, without that, there is no point in trying to find a GSI for your device and there is no point in trying to find a way to force your device to be Treble compatible.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hi, and thanks for taking the time!
I'm still trying to get the hang of it all, but my device is rooted, bootloader is unlocked in Settings, and TWRP is installed. What exactly would I need to do in TWRP to install a GSI on my phone?
Pardon me if I sound obtuse, but I'm still trying to wrap my head around how a rooted Android phone works and performs.

UglyStuff said:
Hi, and thanks for taking the time!
I'm still trying to get the hang of it all, but my device is rooted, bootloader is unlocked in Settings, and TWRP is installed. What exactly would I need to do in TWRP to install a GSI on my phone?
Pardon me if I sound obtuse, but I'm still trying to wrap my head around how a rooted Android phone works and performs.
Click to expand...
Click to collapse
I'm not sure, in the link that you posted, it mentions making a device treble compatible and references a link that supposedly discusses the required files to flash. But when I went to that page, I didn't see anything that said anything about what needed to be flashed or modified to make a device compatible.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
I'm not sure, in the link that you posted, it mentions making a device treble compatible and references a link that supposedly discusses the required files to flash. But when I went to that page, I didn't see anything that said anything about what needed to be flashed or modified to make a device compatible.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Same here. In his preamble, the author alludes to the fact that for devices that don't exactly fit Treble requirements, there ***would*** be a way to make them Treble-compatible anyhow, but it doesn't say how.
I'm also still unsure what GSI I should choose, anyway: the SoC on my phone is an x86_64 chip, but it supports arm64 instructions, as, I suppose, all Android-capable chipsets do, so if I were to try and flash a GSI, should I use one for x86_64, or the arm64 version?
I know there's a compatibility layer in most x86 chips for Android, but what would be the best choice, from an end-user standpoint?

I need help with upgrading - Samsung Galaxy W (SGH-T679M)

I'm searching these forums, the web, every single website, and I still haven't came across a solution. Cyanogen, clockworkmod, they don't want to cooperate. I really am desperate now.
I'm trying to find a way to easily run a ROM on my phone, or maybe just install it. I'm aiming for Kitkat, but I have no idea how, as almost all of the posts on this forum contain broken links. Please, someone help!!!
Alex

Tell me about your fone.
Whats your skill set, as in do you KNOW how to unlock bootloader? Do you know how to root?
Firmware creators are too busy creating firmware. And fixing Bugs.
If your a noob, I can handle that, in effect, I need more information, because all those broken links are irelevant when what you actually need is found in millions of posts here..
The very reason developers dont answer

Pachacouti said:
Tell me about your fone.
Whats your skill set, as in do you KNOW how to unlock bootloader? Do you know how to root?
Firmware creators are too busy creating firmware. And fixing Bugs.
If your a noob, I can handle that, in effect, I need more information, because all those broken links are irelevant when what you actually need is found in millions of posts here..
The very reason developers dont answer
Click to expand...
Click to collapse
Okay.
My phone is a Samsung Galaxy W. It's model number is SGH-T679M and it is currently running Gingerbread.
And so I wanted to change that version because... Gingerbread is unsupported, right? So I landed on this forum first, trying out all the ways that I could, and most of them lead me to dead links as I said.
So I went on different web pages, the Android subreddit, all that. Ended up finding this zip file supposedly containing KitKat or something earlier.
I tried to install it how they told me. Already knew how to go into recovery mode, then it told me to go to the apply update from sd card (used the internal storage instead because i could) and it said the MODEL NUMBER WAS WRONG.
It was for the Samsung Exhibit II, model I8150, and that makes no sense. Because they are LITERALLY THE SAME PHONE.
Thought this was gonna be simple but it was being rough on me. This is why I need help, because I honestly don't know what to do anymore. It is so confusing.

Look at this:
h**ps://www.youtube.com/watch?v=et0AnYkBlc4
correct the link above copy n paste in your browser
Then say if you can handle the work, nothing more. If you are up for it, your best here

Pachacouti said:
Look at this:
h**ps://www.you tube.com/watch?v=et0AnYkBlc4
Then say if you can handle the work, nothing more. If you are up for it, your best here
Click to expand...
Click to collapse
Thank you, I will try it. I'll keep you updated if i didn't mess something up lol
Sincerely, Alex

The struggle... (64 bit recovery porting)

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.