[EDK2][Boot] EDK2 port for G9500 - Samsung Galaxy S8 Guides, News, & Discussion

This EDK2 Port can now boot Windows bootaa64.efi with repartition to userdata partition. [I'll wirte a tool after then.]
You can download boot.img at my github release page
Evsio0n/edk2sdm
Also you can see it on my Twitter 
 @boby2001820
And flash it with TWRP recovery to see UEFI loader
(Strongly suggest you backup boot.img first , beacuse at this stage It's still can't boot any OS.( Needs repartition))
Stay tuned for further news

Wow, awesome!!! Looking forward to this???

This is amazing, well done! Do you think we will have the same luck with sd845? Also after some googleing i noticed two different s8s, did you manage to fully brick one of them, to the point of no fix?

Hi! Could this also work with the Exynos version?

If you all read the articles. Nothing works. No touch no nothing so it's useless. A cool concept but that's it

Related

[A510][Kernel]Development Questions

Hi Folks,
I already spent some years in customizing Linux kernels and in the last time I was already playing around with Android devices and the possibility they offer to boot customized kernel. Now, thanks to NoThrill, we have a working CWM and my interest rises again. I already compiled the Acer Kernel Sources but I got into trouble booting it. Few months ago, I did the same with a lenovo IdeaPad a1 and it should be possible on the A510 too to boot an outside kernel using the command fastboot boot kernel ramdisk.gz. Problem is, that it does download and boot the kernel - but then it returns to fastboot mode instead of booting android. First I thought, it may be due to kernel errors but it does the same if I am using the stock kernel or the boot.img provided by working ROMs. So my questions are:
Is there any possibility to test an experimental kernel without flashing it first? Do I understand correctly, that it is relatively safe to flash it to the boot partition as long as recovery keeps untouched?
What exactly does the (unexplained) command fastboot continue? I thought it may be used to continue booting process with a downloaded kernel, but unfortunately it seems like it does just the same like a normal reboot ...
Simply pack the kernel into a boot.img and flash it to the /boot partition. If something goes wrong, simply reboot into recovery and flash your original boot.img back. Recovery will always work because it uses its own kernel and therefor is independent of whatever kernel you flash to /boot.
A word of warning though: The Acer kernelsource contains code that could brick your tablet. That needs to be fixed before you experiment any further.
Nevertheless, any work done on the A510 kernel is always encouraged :good:
NoThrills said:
Simply pack the kernel into a boot.img and flash it to the /boot partition. If something goes wrong, simply reboot into recovery and flash your original boot.img back. Recovery will always work because it uses its own kernel and therefor is independent of whatever kernel you flash to /boot.
A word of warning though: The Acer kernelsource contains code that could brick your tablet. That needs to be fixed before you experiment any further.
Nevertheless, any work done on the A510 kernel is always encouraged :good:
Click to expand...
Click to collapse
by the way, nothrills, did you set-up a git or something like that to share kernel mods and stuff like that ?
BENETNATH said:
by the way, nothrills, did you set-up a git or something like that to share kernel mods and stuff like that ?
Click to expand...
Click to collapse
Actually, no, because (call me stupid) I really have no clue how git works. I know how to get stuff from it, and used it alot, but never looked into actually setting something up or submitting patches.
I am very ashamed
NoThrills said:
Actually, no, because (call me stupid) I really have no clue how git works. I know how to get stuff from it, and used it alot, but never looked into actually setting something up or submitting patches.
I am very ashamed
Click to expand...
Click to collapse
THAT is something really easy you know..
but if it's something that you agree, i can upload it to my git if you don't want to use time for that.
i can clearly state about the source and then.. work can be shared and commit done.
otherwise, yu have to set-up a free account and follow this :
https://help.github.com/articles/create-a-repo
it would REALLY help you know

[ROM[6.0.1][VFD-1400][OFFICIAL] Vodafone Prime Tab 7

Pretty tricky to find anything for this tablet, but I managed to find a way to get an official image.
What you need:
Alcatel Mobile Upgrade Q 5.1.7 (or newer), get it here.
This will overwrite all your data on the device.
1. Install Mobile Upgrade Q
2. Run "C:\Program Files (x86)\Mobile Upgrade Q\tool\usb_driver\installdriver\DriverInstaller.exe" to install the USB Drivers.
3. Enable USB Debugging
4. adb reboot edl
5. Mobile Upgrade Q and select "VF1400" (note it also lists 9030G and 9030Q, the unbranded variants of this tablet (yet unreleased?), but unfortunately you can't flash these, it will just download the Vodafone branded image)
6. It will download the image files into "C:\Program Files (x86)\Mobile Upgrade Q\bin\download" (note while it's downloading the image files, these are just filled with 0s)
7. After it downloaded the image it starts flashing ("initialisation") and you can copy the files to some place safe (from bin\VF1400-2AVDXXX), it deletes some after it's done
B1BEB0B0CD00.mbn is the boot image, R1BEB0B0CD00.mbn the recovery. Some of the files have partition information, probably can use these to flash with QPST.
Going to have a look into compiling a TWRP, now that I have the kernel
Also, Alcatel seems to have released a *very incomplete* kernel source (build scripts and other things missing) over at https://sourceforge.net/projects/alcatel/files/, see OT_VDF_1400_20160520.tar.xz.
A bummer since the kernel in the official image seems to have all kinds of debugging stuff enabled.
Some more findings. You can coax SUGAR QCT_SP (and maybe Alcatel Mobile Upgrade Q 5.1.7?) into flashing any images.
Before starting SUGAR QCT_SP, copy your backup of the VF1400-2AVDDE1 folder into bin/. It should flash these files.
I flashed a ported recovery, but I couldn't boot it (always boots stock recovery). I guess because of secure boot? Read something about the recovery-from-boot.p file...
Don't worry about bricking, you can get the tab into edl mode with an edl cable. http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Some progress, if anyone cares :laugh: (doubt it).
Flashed boot with altered build.pros, selinux is off, but adb root kills the adbd.
Same on recovery, but kind of pointless with zip verification. Now it's either compile a recovery or add a custom key too boot and sign the supersu zip myself.
Also flashed a slimmer system, minus all the google apps I don't use anyway. Stock image carries 1GB of empty space that is being flashed every time
One more interesting thing: You can get into fastboot by flashing a recovery with the wrong kernel and then booting to recovery. Fastboot is crippled though and does nothing useful, can't even flash with it.
Btw to turn off the device if you are stuck in a bootloop to recovery: With usb cable unconnected, hold Power and Volume down. It screen goes black after 5 sec, keep holding the buttons. It should come up again and very shortly after, let go of the buttons screen when the screen goes black a second time.
So, at the moment there is no way to root?
Geeting the device tomrrow
Yes there is. After getting rid of selinux, you can get temporary root using dirty cow, or bake supersu into the boot or system image.
Also I'm working on porting a recovery. It works, more or less already.
I just flashed SuperSU via the recovery I ported. Seems to work
Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?
gella1992 said:
Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?
Click to expand...
Click to collapse
I can upload it later.
Fastboot is crippled and you can't boot into it directly, at least on mine. Try booting into it (hold power + vol down). Otherwise see my earlier posts on how to do the initial flash. A little inconvenient, but it's only once
Will post detailed instructions with the recovery.
gella1992 said:
Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560
Working on a frankenkernel with some salvaged parts from the incomplete kernel source from alcatel: https://github.com/852Kerfunkle/android_kernel_vodafone_vfd1400
Works for booting into recovery.
While trying some things with caf android builds, I flashed aboot, thinking I could always get back into download mode with the makeshift EDL cable. Turns out you can't.
Do not mess with aboot unless you are 100% sure (unlike me). The device will only register as HS-USB Diagnostic 900E. Even with an EDL cable.
For anyone who did: your device is not dead, but it's a bit of a mission.
1. Take of the back cover: Remove the screw behind the sim/sd latch and open the device with one of these plastic opener thingies, start at the latch.
2. Bridge the pin marked on the image (take a cable and connect the pin to the ground of the usb connector, i.e. the metal bit).
3. Plug in the usb cable.
4. It should register as HS-USB QDloader 9008 (assuming you have the right drivers).
5. Flash with Sugar.
Hopefully everything is working great again!
Do you think it would be possible to port a Lineage OS to this Tab?
I know how to compile from source, but actually not developing a Rom
gella1992 said:
Hopefully everything is working great again!
Do you think it would be possible to port a Lineage OS to this Tab?
I know how to compile from source, but actually not developing a Rom
Click to expand...
Click to collapse
Yeah it's working alright again, thanks
I tried, no luck yet. Am stuck on a crash in libsdm. Once I had it boot to the point where it was initialising the apps (dexopt or whatever?), but it crashed right after.
For now I am focusing on codeaurora android. If I get that working, maybe the caf parts can be used to make a working LineageOS build.
I also have little to no idea how to do anything android related, so most of the time is spent reading and googling silly errors. Just give it a go, if you get stuck I can help out with what I found so far.
At the moment I am busy. Will give it a try when I have more time :fingers-crossed:
fused#1 said:
Working on a frankenkernel with some salvaged parts from the incomplete kernel source from alcatel:
Works for booting into recovery.
Click to expand...
Click to collapse
Are you still working on this ?
I'm currently considering the option of running a git diff against the CAF msm-3.18 "LA.UM.5.1-03210-8x37.0" TAG/branch, which the released incomplete kernel source appears to be based on.
Then going through the patches and applying them one by one on the newest CAF 8937 TAG/branch.
Although getting LA.UM.5.1-03210-8x37.0 to work with the patches applied would be nice already.
My ultimate goal is OMNI, im not interested in CM/Lineage.
Problem is at the moment i don't have much time for this.
But we'll see :good:
nevexc said:
Are you still working on this ?
I'm currently considering the option of running a git diff against the CAF msm-3.18 "LA.UM.5.1-03210-8x37.0" TAG/branch, which the released incomplete kernel source appears to be based on.
Then going through the patches and applying them one by one on the newest CAF 8937 TAG/branch.
Although getting LA.UM.5.1-03210-8x37.0 to work with the patches applied would be nice already.
My ultimate goal is OMNI, im not interested in CM/Lineage.
Problem is at the moment i don't have much time for this.
But we'll see :good:
Click to expand...
Click to collapse
Hey,
That's pretty much what I was doing before I got caught up in other stuff
Was stuck at trying to figure out how to actually build caf android. Which of the files on the rom belong the the proprietary blobs and how to properly include them in the makefiles so it actually builds...
Hit me up with a PM, maybe we can coordinate our efforts :fingers-crossed:
Thanks for this Guide, but I have a quick question:
I am currently trying to restore my VF-1497 to a stock rom with Mobile Upgrade Q 5.1.7, but the Upgrader always kicks my Tablet out of edl, and throws the error:
'There is no greater version available to upgrade your phone, actual version of your phone is the latest'
Is there any way to restore this device back to stock?
Thank you in advance
ASP
Hi is there a custom "clean" firmware for vdf1400 that can go instead of the latest 6.0.1 150fkg1

AIO Alcatel ToolKit- Windows/Linux

AIO Alcatel ToolKit
Built By: PizzaG & LgPWN'd
Build Version Paid: 2.14
Build Version Free: 2.03
Paid Features
All Options 99.9% Fully Automated
Install ADB/Fastboot Drivers to PC
Free Features
Telegram + Download Link​https://t.me/Android_General_Chat​
New Website Live: 12-20-2019
Website Updated: 12-26-2019
AIO Software Versions Updated: 12-26-2019
AIO Features Added: 12-26-2019
..
Wowzers,
Thread been up since 16th October 2019 and nobody bothered with 1 post?
Well... Good work Broski we got the best AIO tool for Alcatel Tetra around
Question is there an updated site or something for download? When click on link just gives dns error.
thugporn* said:
Question is there an updated site or something for download? When click on link just gives dns error.
Click to expand...
Click to collapse
I just checked it, all links are working fine here....
still getting error message.
PizzaG said:
I just checked it, all links are working fine here....
Click to expand...
Click to collapse
thugporn* said:
Click to expand...
Click to collapse
please share both the ERROR and the Link your trying to use
otherwise i can't help you.
I am 1 of the site dev's
Download link doesn't exist.
Dns error
Also getting link error
Link to image. https://ibb.co/qdVzXzr
https: // ibb.co / qdVzXzr
Added spaces to link in hopes of it coming through so you can see the error
SORRY FOR THE CONFUSION OUR SERVER HAS MOVED LOCATIONS....
For current links to our website our notes our Roms and our Tools AIO included plz check our Telegram Group it stays up-to-date.
https://t.me/Android_General_Chat
@PizzaG - Question for you - I see in one screenshot that there is an option, "enable fastboot". I have an A501DL, and currently using mtk-su with Magisk successfully, but no access to fastboot to unlock bl, and no chance of r/w access in system otherwise. Could this help me get into fastboot, and, if so, is there some way I could try to just make that happen, without necessarily using the program?
Here's more detail, if you want :
https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
https://forum.xda-developers.com/showthread.php?p=81911519#post81911519
Thanks
levone1 said:
@PizzaG - Question for you - I see in one screenshot that there is an option, "enable fastboot". I have an A501DL, and currently using mtk-su with Magisk successfully, but no access to fastboot to unlock bl, and no chance of r/w access in system otherwise. Could this help me get into fastboot, and, if so, is there some way I could try to just make that happen, without necessarily using the program?
Here's more detail, if you want :
https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
https://forum.xda-developers.com/showthread.php?p=81911519#post81911519
Thanks
Click to expand...
Click to collapse
You have to have the fastboot lk to unlock bootloader. Unless you can find that, not gonna happen.
PS- 1 option that comes to mind is trying to flash a bad boot to the device with sugar and then hope and pray that it reboots into fastboot. It's my understanding that fastboot is still there, just the commands to get to it have been removed. I was able to recovery from a bad brick on my device by flashing a bad boot to it and it rebooted to fastboot. Get ahold of me on Telegram if you'd like to discuss itmore
PizzaG said:
You have to have the fastboot lk to unlock bootloader. Unless you can find that, not gonna happen.
PS- 1 option that comes to mind is trying to flash a bad boot to the device with sugar and then hope and pray that it reboots into fastboot. It's my understanding that fastboot is still there, just the commands to get to it have been removed. I was able to recovery from a bad brick on my device by flashing a bad boot to it and it rebooted to fastboot. Get ahold of me on Telegram if you'd like to discuss itmore
Click to expand...
Click to collapse
Thanks for the reply. I'm new to mtk. I guess by 'lk' you mean little kernel. From the searching I did, it seems a bit over my head. Is there a way to get that?
I'll look into Sugar at some point. Back on my Xperia XC running Sailfish at the moment..
levone1 said:
Thanks for the reply. I'm new to mtk. I guess by 'lk' you mean little kernel. From the searching I did, it seems a bit over my head. Is there a way to get that?
I'll look into Sugar at some point. Back on my Xperia XC running Sailfish at the moment..
Click to expand...
Click to collapse
Yes, Little Kernel on MTK is where fastboot lives. I have a couple ideas you could try to force the device into fastboot . Our fastboot lk's we were lucky enough to find in an old dump. Best bet is to scour the net looking for the oldest dump you can and pray the fastboot lk is enabled. You can find me here live: https://t.me/Android_General_Chat
This Should Be Updated Into the OP But @PizzaG will have to do that as he has ownership of the thread.
Group on Telegram listed in OP is still the place to find Us and others who can help you out.
Our Site Is HERE:
https://a-team-solutions-downloads.myddns.rocks/Site
and a direct shortcut to the Free Version Of the Tool Is HERE:
https://a-team-solutions-downloads.myddns.rocks/Free/AIO-ToolKit/
It's available in several flavors.
windows and linux on the free.
It was still functioning for the basics like it alwas has last i checked.
However the Paid version does have some neat perks
Hope This Helps everyone
sorry for my late reply as i've said elsewhere i am very busy and don't see XDA much.
If needed i can be found on the telegram group in OP.
LgPWNd

Question TWRP coming?

Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup.
That said, does anyone know how long it typically takes for TWRP to be supported on a new device (i.e. G-Stylus 2021)? Just curious what the norm is. Thanks!
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
DM.IDOL said:
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
Click to expand...
Click to collapse
I'd look around on github
THIS is a TEST build for the Moto G stylus XT2115-1 minsk_t
(please mind that i have never done this before and i am at least trying to figure out how to create custom recoveries. i just need a good teacher with a little time. .)​
*Touch Screen does not work. OTG mouse necessary.*
(not too sure how to fix this error)
*Mount points were for testing*
(modied fstab files in ramdisk to fix mount points)
*modified ramdisk and split_image from Moto G 9 plus unofficial 3.5.1 twrp*
https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-g9-plus-odessa.4195729/
i tried to put a recovery together for this device but im not sure where i went wrong or what to do next. booting into this recovery works but /vendor and /system_root have denied permissions. when it is flashed within twrp and rebooted to recovery or system the screen says no OS installed press power to power off. If anyone can help me figure this one out i would be greatly appreciative. If you need anything i can pull from my device just let me know. Anyone willing to help work on this recovery and figure out what needed to be fixed i would greatly appreciate it!
*EDIT*
i got /data to back without digest verification. Was not able to try to restore the backup as i got NO OS error when i rebooted to restore.
*EDIT*
i was able to figure out pretty much everything except the touch part of the recovery. it has a novatek_ts (NVT-ts)
not sure what to do to enable the drivers for twrp. any feed back would be great.
*EDIT*
Found the driver. I'll post it here and see what you can do. I'll also work on it as I'm still learning where stuff should go in the recovery. And also seems to b that i cannot access external sd from twrp either.
*EDIT*
resolved sd card issues. mountpoint was incorrect. only thing left to get working is touchscreen and not have to use otg mouse.
updated twrp for minsk_t is in files now.
*EDIT*
I found the proper elements to configure the recovery's touchscreen capabilities. Will be recompiling later on today. After I have tested it I will post the new working TWRP recovery. Thanks everybody.
*deleted*
sosthenisRR said:
*deleted*
Click to expand...
Click to collapse
So this is fully functioning now right? Is there any reason to use this over the OrangeFox recovery that has been posted?
Also, if I did install OrangeFox, and decided I wanted to install this later, would it be as simple as flashing using fastboot from ADB, overtop of OrangeFox? Or would the procedure be a little more complex?

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.

Categories

Resources