Related
I am reading conflicting things trying to figure this out. Can someone who is absolutely sure please let me know? I can't afford to waste another entire day making educated guesses.
It doesn't seem like the TWRP version numbers correspond to the Android builds, but if they do please correct me.
Thank you
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
RokCruz said:
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
Click to expand...
Click to collapse
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
didymus said:
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
Click to expand...
Click to collapse
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
RokCruz said:
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
Click to expand...
Click to collapse
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I know I installed it correctly too because in the past week I've installed TWRP so many times I could practically do it blindfolded now.
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things. I just hope yall don't ban me before then, lol.
didymus said:
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things.
Click to expand...
Click to collapse
That screenshot was for this
didymus said:
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly.
Click to expand...
Click to collapse
If you're in android 11 forget the thread about android 9 & 10
RokCruz said:
That screenshot was for this
If you're in android 11 forget the thread about android 9 & 10
Click to expand...
Click to collapse
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
didymus said:
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
Click to expand...
Click to collapse
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
RokCruz said:
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
Click to expand...
Click to collapse
Im trying to install TWRP. I do it exactly how the thread says and then system never boots into OOS again and I just have fastboot and TWRP. Basically bricked. Then when I try to reboot to recovery which should be TWRP (right?) it just boots me into the regular "recovery".
Thats why I think this is broken and I resigned to just not updating into 11.
I've never had this much trouble doing this. Ever. Not even close.
Edit: Yeah, so I patched the 11 boot.img and now I have root again, but no TWRP. I don't know how to keep both in 11. When I was 9.5.3 I used the Magisk A/B retention script and kept it, but once it became 11 it bricked the phone and the TWRP logo just flashed. I had to reflash the OTA to boot again. Thats another reason why I thought it didn't work for OOS11.
Starting to think I have a learning disability, lmao. Wish I was joking.
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
caca12357 said:
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
Click to expand...
Click to collapse
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
@caca12357 I'm going to try to do a local OTA upgrade then before I reboot run the A/B retention script and then Magisks option for OTA and see if that does anything. If TWRP works for 11 something like that should make it work, but who knows. Have you messed with A/B Retention at all?
If you want to PM me we can figure it out together.
Thread moved to proper section
didymus said:
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
Click to expand...
Click to collapse
Yes, and do you know how I flash TWRP to my OP7P? First, I flashed Pixel Experience recovery by fastboot, and I used Pixel Experience recovery to sideload the official TWRP. (In other words, I never can temporarily or permanently flash TWRP directly). If I did not want to convert my /data to the f2fs file system I will not do this meaningless work...
Hello, I want to install official android 12 GSI ROM on my device (Mi A2). I have stock ROM installed on my device and I want to install it by following the official installation instructions. I doubt my device will work with official installation instructions, but my device is fully treble supported. Will my device work in this case? The only answer to this question will be to do this, but I'm afraid of bricking my device.
Everyone can answer you. Not means that he answer you because he knows the answer since he born !
He had search, read & get knowledge.
It always recommended to read about Gsi carefully before install it on your device if you fear bricking then find out on your responsibility.
Hope you got me.
Regards
Abdullah.Csit said:
Everyone can answer you. Not means that he answer you because he knows the answer since he born !
He had search, read & get knowledge.
It always recommended to read about Gsi carefully before install it on your device if you fear bricking then find out on your responsibility.
Hope you got me.
Regards
Click to expand...
Click to collapse
Thanks. I just want to know if anyone has successfully installed the official method.
LazCoder said:
Thanks. I just want to know if anyone has successfully installed the official method.
Click to expand...
Click to collapse
Every one followed the official method has get successfully installation. most devices has same instructions. sometimes you get stuck on Boot loop or system not booting just change the version of GSI build.
Good luck
Abdullah.Csit said:
Every one followed the official method has get successfully installation. most devices has same instructions. sometimes you get stuck on Boot loop or system not booting just change the version of GSI build.
Good luck
Click to expand...
Click to collapse
Thanks, then I'll have to take the risk. If the GSI does not boot I will install the stock ROM. I haven't reset it to factory reset since I bought it. Or I will buy a Pixel device to avoid dealing with all this, but Google Pixel devices are not sold in Turkey.
LazCoder said:
Hello, I want to install official android 12 GSI ROM on my device (Mi A2). I have stock ROM installed on my device and I want to install it by following the official installation instructions. I doubt my device will work with official installation instructions, but my device is fully treble supported. Will my device work in this case? The only answer to this question will be to do this, but I'm afraid of bricking my device.
Click to expand...
Click to collapse
I tried to install on my redmi 6a. Treble compatible. However failed. Even android 10 gsi not working! Bootloops only. I have bricked my phone 100 times because now i have found an easy way to unbrick it without taking off back cover!!!
mottaM said:
I tried to install on my redmi 6a. Treble compatible. However failed. Even android 10 gsi not working! Bootloops only. I have bricked my phone 100 times because now i have found an easy way to unbrick it without taking off back cover!!!
Click to expand...
Click to collapse
Just because your device is treble compatible doesn't mean it supports new Android versions. Did you check if it supports new versions?
mottaM said:
I tried to install on my redmi 6a. Treble compatible. However failed. Even android 10 gsi not working! Bootloops only. I have bricked my phone 100 times because now i have found an easy way to unbrick it without taking off back cover!!!
Click to expand...
Click to collapse
I have a Nokia 2.2 same chipset (mt6761) and android 12 gsi works
areallydumbperson said:
I have a Nokia 2.2 same chipset (mt6761) and android 12 gsi works
Click to expand...
Click to collapse
It doesn't matter which chip it is. It matters what version the phone was released with and whether it supports future GSI releases.
LazCoder said:
Just because your device is treble compatible doesn't mean it supports new Android versions. Did you check if it supports new versions?
Click to expand...
Click to collapse
There's probably this reason behind it: The kernel, Vendor etc of the stock rom is 32 bit only. Unfortunately there is no 32 bit gsi image. I tried finding some 64 bit OS for my device but there is none
mottaM said:
There's probably this reason behind it: The kernel, Vendor etc of the stock rom is 32 bit only. Unfortunately there is no 32 bit gsi image. I tried finding some 64 bit OS for my device but there is none
Click to expand...
Click to collapse
Sad for you.
mottaM said:
There's probably this reason behind it: The kernel, Vendor etc of the stock rom is 32 bit only. Unfortunately there is no 32 bit gsi image. I tried finding some 64 bit OS for my device but there is none
Click to expand...
Click to collapse
After researching I was wrong but 32 bit vendor just so interesting
@LazCoder
Your phone's SoC is 64-bit.
You will need to recompile your entire ROM as 64 bit, then flash the GSI
GSIs will need the vendor and kernel and well everything else to be 64 bit
jwoegerbauer said:
@LazCoder
Your phone's SoC is 64-bit.
You will need to recompile your entire ROM as 64 bit, then flash the GSI
GSIs will need the vendor and kernel and well everything else to be 64 bit
Click to expand...
Click to collapse
Can I simply flash android 11 then flash android 12 gsi?
aqiluii said:
Can I simply flash android 11 then flash android 12 gsi?
Click to expand...
Click to collapse
Official sources say it's possible. But you should check compatibility first.
I was wondering if anyone has tried running a GSI. Would that even be possible at this stage, since development is still in its infancy? Thank you and please have a nice day.
Kereshimei said:
I was wondering if anyone has tried running a GSI. Would that even be possible at this stage, since development is still in its infancy? Thank you and please have a nice day.
Click to expand...
Click to collapse
Yes. I have flashed every one possible lol. They work get in most cases with a few common GSI annoyances.. VNDK and vndk lite versions I've found best. Use arm64 ab../ arm64 ab vndk/lite.
estelocotemira said:
Yes. I have flashed every one possible lol. They work get in most cases with a few common GSI annoyances.. VNDK and vndk lite versions I've found best. Use arm64 ab../ arm64 ab vndk/lite.
Click to expand...
Click to collapse
So were you able to get the phone and messages working ?? My only problem is that it sees I'm on verizon but that's it .. doesn't see my number , hence, no communication.. if you can kindly direct me to directions and/or the ROM itself. I'd appreciate it ..
kevinchristopherson said:
So were you able to get the phone and messages working ?? My only problem is that it sees I'm on verizon but that's it .. doesn't see my number , hence, no communication.. if you can kindly direct me to directions and/or the ROM itself. I'd appreciate it ..
Click to expand...
Click to collapse
Umm honestly cant believe your able to gert verizon unloacked at all.. the newest eternetyson gsis LIR and CRdrom version 313 have come the closet to perfect. imactually doint it now. Ur problem is actually posible what ijust lierally ready of today.. It had to do with (mostlikely) version and ur acconit needing to have an option added call ?less provisioning? or something like that and also said to make sure u log out of and verzon messenger apps manually since they use rcs and ims sservivces simliar to iphone.. If u have telgram hit me up names RITMO or if not my cell is 856 896 7600 feell free to text me .. THere a ****load I can help you at least understand and many things to avoid that ive learned. but in mean time. flash brand new full stock firmware, boot it skip setup, logout of messages, enable devand dbug, then from there only erase system img, flash vmbeta, and theres a product gsi file to flsah so u do not need to delte any logical partitinos. Check out eternityson gsi on telegram or google for the files. fastboot -w, then factory reset in stock recov. then boot gsi.. setup same, then only then magisk and recovery.. also stick with VNDK or lite versions which allow magisk.. GOOD luck.. HIt me UP! Google android ims telephony hal layer probems on generic system image .. Your verizon pages should be there or just gogle versizon ims telephony not working gsi.. blabla..
I have the 2115-3 cricket version oem unlock is enabled in dev options but can't get bootloader unlock code thru Motorola but I did notice 4 GSI roms in the DSU would I be able to get root from one of those potentially?
I am coming from a OnePlus 5, I literally just got my hands on OnePlus 9 a couple of hours ago. It looks like a few things has changed and things are not as straight forward as flashing a zip file in TWRP. I have been reading through a few things and just want to ask some questions.
Is TWRP even needed anymore? Most instructions on flashing roms is done via sideloading and booting into recovery via fastboot (some requires OSS while others LOS recovery).
What is the easiest way to root (on OSS 12)? Seems to be a good mixture of different ways to root and reading comments does not make it any easier, if anything even more confusing.
Which OnePlus 9 do you have? I'm assuming you're on global OOS 12 as I don't think 12 has come to the T-Mobile variant officially, but I wanted to double check and see if I could point you in the right direction.
posar said:
Which OnePlus 9 do you have? I'm assuming you're on global OOS 12 as I don't think 12 has come to the T-Mobile variant officially, but I wanted to double check and see if I could point you in the right direction.
Click to expand...
Click to collapse
I got the 2115 model, I believe that is global. Can you not just flash ROMs in TWRP anymore? I see all of the ROMs requires sideload which means you need a computer. I am a bit of a flashaholic and even though sideload is not a big issue.
Z-Blade said:
I got the 2115 model, I believe that is global. Can you not just flash ROMs in TWRP anymore? I see all of the ROMs requires sideload which means you need a computer. I am a bit of a flashaholic and even though sideload is not a big issue.
Click to expand...
Click to collapse
Not really, unfortunately. For most ROMs, it seems you have to go to the most recent version of OOS 11 and then flash from there.
posar said:
Not really, unfortunately. For most ROMs, it seems you have to go to the most recent version of OOS 11 and then flash from there.
Click to expand...
Click to collapse
That is unfortunate. I got root going on OSS 12 but at this point I don't really see a reason to flash TWRP since the recommended way to flash custom ROMs is different. I hope all of the Devs ends up following a particular standard.
Z-Blade said:
That is unfortunate. I got root going on OSS 12 but at this point I don't really see a reason to flash TWRP since the recommended way to flash custom ROMs is different. I hope all of the Devs ends up following a particular standard.
Click to expand...
Click to collapse
Yeah, it seems as if the simple TWRP days are over, at least for OnePlus. Maybe someone smarter than me will get it working flawlessly.
Z-Blade said:
That is unfortunate. I got root going on OSS 12 but at this point I don't really see a reason to flash TWRP since the recommended way to flash custom ROMs is different. I hope all of the Devs ends up following a particular standard.
Click to expand...
Click to collapse
Can you tell me how did you obtain root on OSS 12? I tried severalmethods but ended up with errors an even some soft-bricked times. As you stated in the 1st message, there is plenty of ways around the internet and comments making it really confusing.
JustLeoSC said:
Can you tell me how did you obtain root on OSS 12? I tried severalmethods but ended up with errors an even some soft-bricked times. As you stated in the 1st message, there is plenty of ways around the internet and comments making it really confusing.
Click to expand...
Click to collapse
I downloaded the patched boot.img from the link below and I recommend you also down the normal stock boot.img as well.
[DISCONTINUED][OOS & PA] OnePlus 9 stock/patched boot images
Now as we have TWRP for any A11-13 ROMs, there's no need for boot image patching, just flash magisk in TWRP. Hi! There's a great root guide here on xda by @zymphad and i thought i'd share the boot images for different OOS and Paranoid Android...
forum.xda-developers.com
In that thread there is a link to a 'Great root guide', I used that root guide and the patched boot.img to root Android 12.
Nice! After several tries, some softbricks and a lot of haste for the different methos I finally got it rooted. Thank you man, it worked like a charm!
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.