Database Info

How to find stock ROM files for my BL unlocked XT925 with no backups?

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!

[Completed] Wacom Cintiq Companion Hybrid ( DTH-A1300L ) android needs custom rom or stock bad

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."

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?

Trouble returning to stock? Possible solution.

I spent half yesterday, into the wee hours of the morning trying to get my pixel back to life. Figured I'd post my goof as it may help someone later.
I flashed the aosp build using the android flash tool just out of curiosity. Realizing dual sim did not work on asop without gapps of some sort, I decided to go back to the public builds. That's where things went crashing down, fast and hard. Literally 6 hours trying everything I knew and everything I could find. Tried 3 different computers, multiple different cables, made sure adb and fastboot were updated like 5 times, tried using the flash tool, tried downloading and using flash all, tried erasing everything and starting over, tried lineage, tried side loading via adb, tried fastboot flashing individual images... All failed, flash tool complaining about not enough space, local installs complaining about missing partitions, not valid files, just everything that could go wrong did. The only thing I could successfully get installed was aosp.
The solution? What was preventing it? I use ublock and privacy badger. Disabling those, off to the races, everything went smoothly and I'm back up and running. What puzzled me, how could I used the flash tool to go to aosp but not back? Why, or how was it interfering with a local flash? Maybe things got screwed up somehow and that was messing with the local flash...idk but if you're in my position try disabling those and give it a whirl.

Which flash tool are you talking about? Everything you're doing sounds overly complicated.
I recommend sticking with cmd for windows, and terminals in linux .

noidea24 said:
Which flash tool are you talking about? Everything you're doing sounds overly complicated.
I recommend sticking with cmd for windows, and terminals in linux .
Click to expand...
Click to collapse
I tried that, I tried using the flash all bat for windows and then I tried flashing individual images via adb. Nothing worked. I have no clue why the local installations kept failing unless, as I said something got messed up using the android flash tool via chrome.
Here's the flash tool which I used to load aosp.

I can't understand what problem you were facing:
use newest platform tools
use newest Google USB drivers
use firmware image of google developers page
reboot into fastboot (by volDown + Power or via adb)
flash-all
working smooth like butter if you can read

hanni2301 said:
I can't understand what problem you were facing:
use newest platform tools
use newest Google USB drivers
use firmware image of google developers page
reboot into fastboot (by volDown + Power or via adb)
flash-all
working smooth like butter if you can read
Click to expand...
Click to collapse
I'm guessing you can't read, I did all that. I'm simply posting this in case someone else runs into the same issue I did. As I said, I'm not sure if trying the aosp build changed anything or any of my numerous attempts fouled something. The only way back was disabling ublock and privacy badger and using the flash tool. For clarification, I've been doing this since the very first android, the T-Mobile G1 and am not new to this game.

You were right, I didn't read carefully enough, or to call it by it's name, I misunderstood your posts. The title of your thread lets believe that you have trouble returning to stock and you need help on that.
That something goofy kicked you out of routine I didn't read (was reading from newest to oldest post, so tbh, that was not clever)
I'm also not new to this, so let us stay calm. Nice that you share your experiences.
I would suggest to change the title in: 'try this if you have trouble with returning to stock' I r something similar.
Have a good time!

hanni2301 said:
You were right, I didn't read carefully enough, or to call it by it's name, I misunderstood your posts. The title of your thread lets believe that you have trouble returning to stock and you need help on that.
That something goofy kicked you out of routine I didn't read (was reading from newest to oldest post, so tbh, that was not clever)
I'm also not new to this, so let us stay calm. Nice that you share your experiences.
I would suggest to change the title in: 'try this if you have trouble with returning to stock' I r something similar.
Have a good time!
Click to expand...
Click to collapse
No problem. I'm still at a loss as to what went wrong but needless to say, for myself, I won't be trying AOSP via the flash tool again.

Little late on this, but I was in a rut as well then realized I had adblockers on which caused issue with the flash tool.

Easiest way to get back to stock is by using Android Flash Tool https://flash.android.com/back-to-public

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.