MODS--- PLEASE DELETE...found my answer...thank you
First, MODs if this is in the wrong area, please fell free to move or merge.
I'm pretty sure Devs have tried this, but I'd like to know for sure as I havent seen any talk about it, as of my searching. We all are aware of the engineering sboot over in the TMobile forums... It was removed per Samsungs request. But, did anyone attempt a flash of that sboot to the SM-G920V, in same order as in the TMobile thread? My idea was -- engineering sboot, a stock modified permissive kernel, then TWRP. Just wondering if it was attempted. thanks for the effort and hard work guys. And thanks in advance for an answer to my question.
Sorry if there's somewhere this is already posted, but I can't seem to find a stock rom of 6045 model anywhere on the site (or at least one that I can flash through twrp). If anyone can provide a copy of their stock rom a one, that would be greatly appreciated.
I derped my rom and not I can't the the incoming interface when someone is calling.... and I can't make phone calls cause I somehow deleted that app.
lowbo* said:
Sorry if there's somewhere this is already posted, but I can't seem to find a stock rom of 6045 model anywhere on the site (or at least one that I can flash through twrp). If anyone can provide a copy of their stock rom a one, that would be greatly appreciated.
I derped my rom and not I can't the the incoming interface when someone is calling.... and I can't make phone calls cause I somehow deleted that app.
Click to expand...
Click to collapse
Easiest solution is to use the Mobile Q software to reset your phone to factory condition. Start here: http://forum.xda-developers.com/idol-3/general/idol-3-mobile-upgrade-app-download-t3182517
Failing that if you just have to have a twrp backup.....
http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
[Post #3]
Questions to the appropriate thread.
Thank you so much for the help man. I tried the first link you pointed out but I had issues getting it to work. Now with the second link I saw this before was unsure about the links. Are they actually zip version of the rom I can just flash or do I have to turn then into a zip? Not really sure what to with it, lol. Thanks a again for all your help. I really appreciate it.
lowbo* said:
Thank you so much for the help man. I tried the first link you pointed out but I had issues getting it to work. Now with the second link I saw this before was unsure about the links. Are they actually zip version of the rom I can just flash or do I have to turn then into a zip? Not really sure what to with it, lol. Thanks a again for all your help. I really appreciate it.
Click to expand...
Click to collapse
The instructions in the first couple of posts explain everything you are asking. If you search, I'm sure someone has also written step by step to getting the Mobile Q software working.
lowbo* said:
Sorry if there's somewhere this is already posted, but I can't seem to find a stock rom of 6045 model anywhere on the site (or at least one that I can flash through twrp). If anyone can provide a copy of their stock rom a one, that would be greatly appreciated.
I derped my rom and not I can't the the incoming interface when someone is calling.... and I can't make phone calls cause I somehow deleted that app.
Click to expand...
Click to collapse
You should find the answer of your problem with this post:
http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Not even sure if it's rooted still. That lack of permission has any fix i know blocked. I need to access settings any suggestions on how without a pc? Your site can tell if it's. Rooted. Using it via the toolbar. Learned it's an LS740 and it's boost. Been attempting "secret codes" zero have actually worked. If someone can please offer up a solution I would greatly appreciate it. I'm still just attempting to learn. Also if the site gate keepers could advise me as to root status of this currently used device. I could know then if maybe I can push a recovery img.
Well no questions finding help yet. I just now downloaded a gapps package. Correct me please if I'm wrong but didn't that basically confirm the device is still rooted? I'm certain there's no flashify or similar app in here. No recovery so can I push a recovery img. So it potentially gets the gapps package in. Look I'm spitballing basically trying to beg for helpful advice hopefully from someone who knows these things. A previous device I failed to find advice and eventually made a good guess and pushed a gapps package which solved a very similar problem. This device has settings out with no permissions for outsourced apps. A bit harder to work around for a newbie. Yes a couple successful guesses don't reach above newbie. Help please.
Hi, could any of you help me and send me your persist.img file?
Some time ago I broke Widevine on my phone, probably by flashing the bad persist.img, I already tried all the ways to recover Widevine L1, I used the MSM Tool, I flash the system via fastboot, I even sent the phone to the repair service, but nothing helped, so I didn't ask for advice because I have probably checked all possible ideas except one, i.e. flashing persist, but to do this I must first get this file from someone, please help
Here, its from a post of fastboot rom
Did your problem is solved now ?
Rayekk said:
Hi, could any of you help me and send me your persist.img file?
Some time ago I broke Widevine on my phone, probably by flashing the bad persist.img, I already tried all the ways to recover Widevine L1, I used the MSM Tool, I flash the system via fastboot, I even sent the phone to the repair service, but nothing helped, so I didn't ask for advice because I have probably checked all possible ideas except one, i.e. flashing persist, but to do this I must first get this file from someone, please help
Click to expand...
Click to collapse
Did your problem is solved now?. Because I am also having the same problem I flashed accidentally persist img file and I lossed my L1 . People are suggest to give on service centre. But after seeing your post I think that is waste of time and data. If you found any solution pls share it
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.