yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Wild-Owl:
Hey guys I was able to go from stock to twrp rooted and encryption disabled with this!

https://xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389

If anyone would like a easy step by step just post a reply!

Thanks
[MENTION=5437200]PizzaG[/MENTION]
[MENTION=6037748]Zackptg5[/MENTION]
[Android Q&A, Help & Troubleshooting] Wild-Owl:
One stop shop OH NO! sorry I wasn't clear!

I update with sugar, change .mbn, update again, fastboot oem unlock, flash boot.img, install magisk, flash twrp recovery, boot into twrp, advanced wipe data to F2FS, and then flash zip

all steps from your guide I just flash zip instead of editing fstab

Can you tell me how your are installing the GSI roms do you fastboot flash system.img?

I opened the Android Pie rom added the line from your guide to the build prop fastboot flashed system.img but it still hung on boot!

Thanks for your work [MENTION=5437200]PizzaG[/MENTION]
[Android Q&A, Help & Troubleshooting] :
It's all posted in my Updated Tutorial. It all depends on what date rom you're trying to use and which one. I have all GSI roms for a-only booting no issue, Provided you are only using roms built from march and above. GSI roms can be flashed from Fastboot or Treble-enabled Custom Recovery. I made all 3 recoveries I've released treble flashing ready. Easiest to use TWRP imo. The tutorial only uses fastboot 1 time now, check it out. If you can't get GSI booting, Run through the full tutorial and then ask for help. I'll no longer provide any type of support for anyone who doesn't follow the updated guide. My old guide was broken in spots. This guide is spot on and I was able to go from Stock to android 9 in about 15-20 minutes. Editing the fstab does more than disable things. It also enables rw to system and vendor, which the flashable patch doesn't do., at least not that i'm aware of. You cannot take apart the GSI image and change things. At least I have not gotten one to boot that I have changed. You have to make changes with the system already installed. I include the fstab in my package now, no more needing to manually edit that file. The build.prop you edit once the system is already installed. If you tore apart the GSI image and edited the build.prop and then put the image back together and flashed it, I can guarantee that is your problem. If not, grab my stuff and start over. Make sure you are running the latest stock firmware. I use one of the TWRP Recoveries to flash system images. If you still need help, i'm best reached on telegram for live chat
[Android Q&A, Help & Troubleshooting] Wild-Owl:
Thanks man

You are the expert i'm just a noob playing around trying to learn things!

I'm going to try ripping apart those GSI roms on my ole Linux machine simg2img to raw editing and then img2simg back and see what I get!
[Android Q&A, Help & Troubleshooting] :
Good idea, that's oe thing i didn't try was editing them raw. Let me know how it goes
[Android Q&A, Help & Troubleshooting] Wild-Owl:
Editing the images raw works beautifully I edited the prop on one of the GSI images last night and the setup started in about 1 to 2 minutes nice! I also removed some of the extra apps I don't use! I did a backup of the stock image with TWRP I think i'll rip out all the bloat junk apps like weather etc slim it down some. I'm also looking at the dmesg log on different GSI roms see whats working and not!

Lots of work but having fun :good:
[Android Q&A, Help & Troubleshooting] :
Would you care to run me through that process? I figured editing the raw image would work but have never been able to figure out how to do that. The tutorials all seem old and outdated. That way I would be able to directly edit the roms and re-release them on here with fixes already integrated, making it alot less frustrating for the end-user

Also, in case you didn't know, get rid of the Ignite ATT app. It's responsible for downloading and installing all the bloatware that really makes the phone run like crap.
[Android Q&A, Help & Troubleshooting] Wild-Owl:
on your favorite linux distro

install Simg2img and Img2simg

i create a directory named work in home

put the system.img in work directory

i create a directory named sys in home

move to work directory in terminal

simg2img system.img sys.raw

sudo mount -t ext4 -o loop sys.raw /home/username/sys

open sys as root in gui

make edits

img2simg sys.raw system2.img

unmount sys

delete sys directory

system2.img is in work directory
[Android Q&A, Help & Troubleshooting] Wild-Owl:
[MENTION=5437200]PizzaG[/MENTION]

My biggest question I have never found a answer to is...

I have setup pc configured everything and have the entire source for cm-15.0 downloaded

$ source build/envsetup.sh

$ breakfast ?????

How do you create or obtain the device specific configuration and kernel if in this case the Alcatel Tetra code is not there?

If you or anyone you know could pm me the process involved in short form no need for indepth i'm guessing this is huge task requiring several people!

Thanks
[Android Q&A, Help & Troubleshooting] :
As far as I know, you would have to create your own device tree for it. I have no clue how to do such a thing but Many people have done it so I know it's at least possible. There is a TWRP device tree for this device but I don't think that's enough.
[Android Q&A, Help & Troubleshooting] Wild-Owl:
Today i'm thinking about dumping aboot.bin and removing the bootloader unlocked warning!

Any suggestions before I toast this thing? :laugh:
[Android Q&A, Help & Troubleshooting] :
This phone doesn't have an aboot.bin. What you are probably looking for is the little kernel file. That's the file in my Tetra package in the Little Kernel Downgrade folder. I looked at it a couple months ago with a hex editor and that line is def in there along with some other lines for red state and such. I did edit that out but at the time I had no way to flash it so I didn't worry about it. At this point, I'm much more confident that we have a way to flash it. Don't worry if you mess it up, Sugar will reflash the file and all will be well again. Good luck and let me know what you figure out. Would be nice to get rid of that nag at boot but not a biggie either way.
[Android Q&A, Help & Troubleshooting] Wild-Owl:
Sweet!

After reading your reply the light in my brain came on, yes that is what I was looking for and it is wonderful that sugar will replace if I mess it up very good to know! I have learned so much from your files and posts!

Thanks again!
[Android Q&A, Help & Troubleshooting] marcgarcia322:
hello i'm a noob here and need help with rooting my wife's alcatel tetra 5041C

i wish to unlock the boot loader install twrp recovery

and root original 8.1v os if possible

please any help would be much appreciated thank you in advance
[Android Q&A, Help & Troubleshooting] :
Hey there, if you can wait until tomorrow, I'll have a brand new 10 minute procedure all done up and uploaded. That's what I've been working on the last few days is getting the process first from an hour, then 20 minutes and now even shorter. You've come to the right place, I'm running android 9 on it at the moment. You have a bunch of custom GSI roms to choose from when you get that far. Very decent little phone once it's all modded up. I think My older root package is still located a page or 2 back if you can't wait. If you need any help, hop on telegram. I posted the link to get ahold of me on there.
[Android Q&A, Help & Troubleshooting] Wild-Owl:
Works good! I just edited out the nagging bootloader unlocked text in the lk file and was surprised it let me just copy and replace the lk file while it was running! For more fun you could grab the logo.bin from the stock file customize the logo and make a cool boot animation then your all set!
[Android Q&A, Help & Troubleshooting] gjutzy:
Awesome step-by-step!

Thanks for the great links and instruction! I am having a slight problem when I get to the "change file system" part. Which partition do you change to f2fs? I have tried "system" partition, and cannot find anything in the system folder on the next step. I have not tried other partitions yet. I am restoring to just before this step, and will try it with the others, one by one, till everything works. Any suggestions would save me some time. Everything else works great until I get to this step.

Thanks again!
[Android Q&A, Help & Troubleshooting] :
oops, you made a booboo, lol. The instructions don't say to select the Data partition for that? You should be putting Data partition to f2fs. You will have to start over fresh prolly to fix your mistake to the system. you wiped it and have no OS. Make sure you put system back to ext4. Wow, def my bad on that. I just looked and i forgot to say to select the Data partition in the tutorial. I'm sorry for that and will upload my new package today which is even easier. Custom bootanimation and everything.

---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------

That's awesome man, I was 98% sure that would work, just been so busy trying to get the initial process down and such. Could you share that LK file so i can include it in the package please? I'll give you creds for patching that out of it of course. I've already replaced the bootanimation in my newest package I'm getting ready to release, but it's not in logo.bin. Are you referring to another bootanimation? Or the the initial logo when you turn the phone on?
[Android Q&A, Help & Troubleshooting] gjutzy:
Going smoothly now

Just wanted to thank PizzaG again for the great tutorial. I would have probably figured it out. I know just enough to be dangerous, and willing to try whatever it takes to wipe AT&T out of my phone so I can use my Google Fi Sim card in this phone.

So far, I have made it all the way through Part 1 of the tutorial with no errors! The only parts that took longer at first were figuring out which files I should download to my sdcard and have them local on the phone, and which files should be on my PC. That, and the data partition bit.

Got it all worked out so far, and now for part deux...
[Android Q&A, Help & Troubleshooting] gjutzy:
Trouble with cellular network and wifi

Hey there, I am not sure if I am doing this wrong, but I have now tried many of the Android 9 images, and having the same issues with each of them. I cannot seem to connect to any wifi networks, and I cannot grab a network signal using the Google Fi Sim in my phone. My phone was a pay-as-you-go from AT&T, and the 30 days is done, so that sim is not active anymore. I have a Google Fi account, and cannot seem to get it to find any cell network. Any suggestions? I am pretty new to this stuff, but finding this forum really helpful. So glad that someone out there is doing this great work, and knows what they are doing!

---------- Post added at 07:50 PM ---------- Previous post was at 07:31 PM ----------

Okay, so I think, as I read through the rest of the information on each image that I install, I see the patches folders and such. Looking through them, I notice that each of the issues I mention above, and them some, has a patch file. I guess I need to figure out how to load these into the build. Sideloading? Root? I am getting pretty good at making backups now so I don't have to go so far back to correct the mayhem!
[Android Q&A, Help & Troubleshooting] :
If you are talking about the patches.zip, those patches are already applied to whatever corresponding rom you downloaded. Those patches are for if you are building your own roms and want them incorporated. What rom and what's the rom date? I honestly haven't used wifi so i'm not sure. If it's not working, hop on telegram and talk to Phhusson, he's the GSI Guru who made all this possible and he's constantly helping people out. Best I can do is see if it's working on mine. If the rom says su, you need the superuser app to control root. LOS has complete root already set up, you have to enable it in dev settings.
[Android Q&A, Help & Troubleshooting] gjutzy:
Aha, ok. Good to know about the patches. My next task was to sit down and try to figure out how to install those suckers! No need. So, the current rom I am working with is AOSP 9.0 v112, and I noticed Phhusson's name everywhere on the link, so I figured this rom would be a good one to try. The rom was released on April 2. I used the boot time fix and charging fix, and while I have not been able to power off the phone to charge it and test that function, I am enjoying much MUCH faster boot times than before! I have also sideloaded a couple of apks, and things seem to work. just not as a phone or wifi device yet. getting there...
[Android Q&A, Help & Troubleshooting] :
LOS from march is what I found to be the best. I never moved to the April build of anything because I have a buddy who has a phone with the same Soc who let me know the April builds broke more stuff than they fixed. I would personally try the March 9 2019 LOS 16 build. That was where it was at for me. Did you plan to share the modified little kernel file or will i have to patch that myself? I'd like to get the updated package zipped up and uploaded and I'd love to have that file in there without the nag. I'm too wore out to fuss with patching much more of anything right now. It's been a long week and I'm exhausted. I'm also doing things for another Alcatel phone I have that i finally was able to get updated after i abandoned the project about 8 months back, lol.

EDIT: I just got confirmation, LOS and RR from April is broken. Apparently the rest from April are fine.
[Android Q&A, Help & Troubleshooting] gjutzy:
Thanks, I will give LOS a shot. I will share anything if it helps. Not sure what modified kernel file you mean. The boot time and charging fix I mentioned came from your post with the tutorial, and the sideloading was just practice with a couple of things to see if it worked.
[Android Q&A, Help & Troubleshooting] :
Sorry about that, I mistook you for the wrong person. I was referring to Wild-Owl who has the nag free little kernel file.

USB isn't working in general yet in TWRP. That and the screen coming back on when you turn the screen off in TWRP and when the screen times out are 2 bugs I plan to try to fix to get TWRP 100%, but those 2 things are my last priority as TWRP functions perfectly fine for our main needs. In the meantime, I just disable screen timeout in TWRP settings. Since Wild-Owl has the nag free little kernel file and I don't want to patch it, I'm waiting for his response before I release my final package that includes pre-made TWRP flashable Vendor image, Custom Stock System image and Pre-rooted magisk boot.img. With those 3 images, nobody will have to do anything but use sugar, unlock bootloader with fastboot, format Data partition and flash those 3 images. That will be the entire easiest method possible. Also, if you are trying to use the magisk boot.img from earlier in the thread, that will break wifi and data most likely. The boot.img released by other people in the thread is for an old update and we can't use that file. So if by chance you used it, that's your issue.

The new tutorial explains where to place all the files before you start, so that should help clear up any confusion as well for noobs. I assumed at the time, when the process was much more difficult, people were doing a bit of research about the basics first, that's why I included the disclaimer in my Release Post. When I first started working on this phone, the process was really only for the hard core people that knew what they were doing. Now it has progressed to the point where anybody will be able to do this with ease.

[MENTION=9765625]Wild-Owl[/MENTION] could you please share the nag free little kernel file so I can include it in the Main Package please?
[Android Q&A, Help & Troubleshooting] Wild-Owl:
Sorry I have been working on another interesting phone be back shortly!

---------- Post added at 01:55 AM ---------- Previous post was at 01:24 AM ----------

patched lk file http://s000.tinyupload.com/index.php?file_id=89512609256233521952
[Android Q&A, Help & Troubleshooting] Wild-Owl:
Woo Woo!

Yes I was talking about the first logo! [MENTION=4916584]ankadnikov[/MENTION] has a logo builder program you can make some cool stuff with, as for the boot animation I like [MENTION=631273]Chainfire[/MENTION] LiveBoot its sweet!
[Android Q&A, Help & Troubleshooting] svaethier:
i think the replace mbn file part of the tutorial will need an update as the latest version is now 8M8YUAY0
[Android Q&A, Help & Troubleshooting] :
...............
[Android Q&A, Help & Troubleshooting] Wild-Owl:
Excellent work [MENTION=5437200]PizzaG[/MENTION] :good:
[Android Q&A, Help & Troubleshooting] svaethier:
do i need to install the disable dm verity zip if my phone bootloops to the 'phone bootloader is unlocked' alcatel screen when i flash a rom?
[Android Q&A, Help & Troubleshooting] :
Use my newest package and you don't have to "install" anything. All the work has been done for you. Check it out and post back. I need some feedback to know it's as easy as possible.
[Android Q&A, Help & Troubleshooting] svaethier:
i have everything already done, i'm just trying to install the phh android 9 rom and it either bootloops at that screen or it just stays at that screen for a long time.
[Android Q&A, Help & Troubleshooting] :
I haven't tried any April builds of anything. All I can say is that if the March 9th build of LOS16 doesn't work, you're missing something. Did you apply the boot time fix for android 9 roms? If you continue to have issues, start at booting TWRP step in my new guide. Have you tried other roms?
[Android Q&A, Help & Troubleshooting] svaethier:
well i got the pie rom to work but the wifi didnt work even when i restored to a backup so i had to restart from the beginning, i'm starting to think that treble roms wont work all the way for this phone or any mediatek phone with the same chipset since not a lot of people have a phone with it.
[Android Q&A, Help & Troubleshooting] :
LOL, I beg to differ my friend. I've been using Pie for 3 months with only issues that I've posted. And yes, there are other phones out there with this chipset and alot of time has already been spent to get this chipset in working condition on Pie roms.

I'll say this. You can't use the kernel from A-Update with B-Update and vica versa. Basically, my older packages are all garbage as the updates have changed. So if you update with sugar right now, and then try to use my older packages, Your phone will produce issues like you have described. I wouldn't have released this stuff if it didn't work guys, I've spent alot of time on this project and there would only be 2 of us running anything, had I not released everything. So please, act like I have a clue what I'm talking about here.
[Android Q&A, Help & Troubleshooting] svaethier:
i had to use the old tutorial starting after the twrp custom recovery flash because the cricket rom backup you made doesn't work as you cant select any partitions to restore as none even show up. I think that backup can only be used by you, you should just upload the cricket rom you have for the guide or delete the cricket backup flash from the guide entirely.
[Android Q&A, Help & Troubleshooting] :
You moved the whole TWRP folder over to external SD card? There is nothing binding backups to 1 device that I'm aware of. I think I will wait for more feedback before I do all that. I still am thinking you are trying to run old files on a newer update, and you will never get anywhere that way. Best of luck

Also, are you using my newest May TWRP? That is modified for restoring properly.

The backup files are fine. Maybe your device creates a different named folder. Make a quick boot backup on your device and compare folder names. If your folder is different, just drop my files in it and see what happens. You're coming to all these wild conclusions before trying anything in-between which to me is where i'd start first
[Android Q&A, Help & Troubleshooting] svaethier:
yes i'm using the latest twrp you have in the newest version of your guide

edit: I did what you suggested and got the cricket rom to flash now. how exactly will this rom help me with booting into the android 9 treble rom?
[Android Q&A, Help & Troubleshooting] :
Ok so first off, was the problem that each device creates a different numbered TWRP folder? I need to know that so I can adjust the guide based off of that info. I had just assumed it spit out the same numbered folder for each device of the same model.

The rom itself is just the stock system image modified. It's the pre-modified Vendor partition in the backup where all the fixes and patches are already incorporated by me. So now that I know 100% what point you're at, it's much easier to provide support. So once you have restored the Backup, you are ready to flash any GSI system image you want to try. I've already added the Android 9 boot time fix, the fstab is already edited to get rid of force encryption on the data partition and the Vendor/System partition is changed from read-only to read/write. You shouldn't have any more issues with wifi and such unless it's broken in the GSI image. You run the risk of messing up the vendor stuff when you edit and modify stuff, that's why i redid everything, to make it easy. Let me know how GSI roms work moving forward.

Also, i apologize if I seemed a bit short. I can get like that at times, alot going on at home and such. Anyways, I hope Android 9 runs better for you now.
[Android Q&A, Help & Troubleshooting] svaethier:
yes it seems that twrp does different backup folders for each device and i still had wifi issues with the may build of PHH android 9 rom. i redid everything but installed the android 9 build with fastboot after unlocking the bootloader and had no wifi issues whatsoever so i think magisk doesnt work with that build or something else is up.
[Android Q&A, Help & Troubleshooting] svaethier:
magisk 19.1 does seem to work with pie kinda as everything works except superuser from what i can tell. i'm having quite a few issues though such as not being able to use the home and recent apps button on my phone with the pie rom but that might be an easy fix.
[Android Q&A, Help & Troubleshooting] :
I had the Home button issue as well, I found that was only on 1 of the roms I tried. Keep in mind, a little over 3 months ago, phone service and data didn't even work on this chipset for GSI. So it has come a long way in a fairly short time. Little things like Home button not working, that vary by rom, are rom issues. Major issues like phone service and data not working, those are things you would want to take to Phh. He can be found on Telegram and without his help, we'd all be having 40 minute boot times on ALL Android 9 roms. We only applied a band-aid for that particular issue, but you see what I mean. LOS16 had Everything working except for Hotspot. Not a good idea to use native hotspot anyways unless you pay for it. I found that out the hard way, lol. Trust me on that. If you pay for or want to use your payed for Data how you'd like, use PdaNet. They aren't able to monitor that usage like they can native hotspot. That's how I spread out my Unlimited data to my whole house without paying the extra $10 for hotspot. I find it ridiculous to have to pay extra for something built into android, especially when I'm already paying extra for totally unlimited data.
[Android Q&A, Help & Troubleshooting] svaethier:
yea the android 9 treble roms really have come a long way since then for sure, i think the boot time hasnt been long as i think the last reboot i did was less than a few minutes and i didnt even touch the build.prop file at all. anyways i think we should continue this conversation on telegram as it would be easier to message on there.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] topolong:
i don't know why, i just can't type anything in the blank :(:(
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] le_cactus:
Don't use the Quick Reply, just hit the Reply button
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bapssystupr3m3:
what does this have to do with kaiser rom development?

go back to using the internet class or using a forum class:)