So after 2 weeks of debugging and trying to figure out why Treble GSI were not booting, then booting only for some users the final answer has been found.
This bootloader is way too stateful.
So if you try directly with proper vbmeta & system.img, you won't notice anything, it will just work, that's why some people say it works.
If you try system first without doing vbmeta, then it will mark the slot as not bootable. Flashing vbmeta afterwards will NOT mark it as bootable.
it also requires the latest fastboot with --disable-verity and --disable-verification, don't know why yet exactly.
Now if you bootloop to mark it as bootable again, you need to flash the boot partition of the slot.
Even worse than that "fastboot boot" works only if current slot is not marked as not bootable, so any try to launch TWRP fails once your in this mode.
This same issue also applies to users trying to restore to stock sometimes.
This means that the One Plus 6 will require proper documentation on how to do things, and people will have to stick to it, see official instructions in post 2.
Now that we know what the exact cause is, and how to deal with it, let the development begin.
PS
Doesn't seem to be OP fault, just stock Qualcomm bootloader.
Credits to Phhusson and me for making this possible, providing phh a device, documenting the findings and all.
WARNING This is still ALPHA
OFFICIAL INSTRUCTIONS
Correct installation procedure of a GSI on the One Plus 6, determined together with @phhusson
Make sure you unlocked the bootloader and that you have the absolute latest ADB and Fastboot from Google, none of the minimal packages we know of will work!
Then in fastboot flash the following, WITHOUT rebooting in between! this needs to be done all in one go!
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Use the STOCK boot image!
Then flash the GSI system image of your choice
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
Then flash STOCK vbmeta image with the specific commands!
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then just fastboot reboot or select start on the phone.
---------------------------------------------------------------------------------------------------------------------------------------------------
If the above fails and you get a bootloop you will have to repeat all the steps above.
---------------------------------------------------------------------------------------------------------------------------------------------------
So if its marking it as unbootable can't you fastboot --set-active=other to get back to a bootable state?
@Exelios
Thank you for sharing.
Thread moved. Since this appears to be documentation rather than a physical product, this is the proper subforum.
Thank you!
-RJ
Great work man,
I had held off trying as I didn't know if it would work for me or not. Looking forward to trying this out!!!
Sent from my OnePlus6 using XDA Labs
joemossjr said:
So if its marking it as unbootable can't you fastboot --set-active=other to get back to a bootable state?
Click to expand...
Click to collapse
Yeah you can do that once, but to get your first slot back you will need to re flash boot also at some point.
And remember once you flash boot you need to root and TWRP again.
Sent from my OnePlus 6 using XDA Labs
CertifiedBlyndGuy said:
Thread moved. Since this appears to be documentation rather than a physical product, this is the proper subforum.
Thank you!
-RJ
Click to expand...
Click to collapse
An actual piece of software will be added by the end of the day.
Sent from my OnePlus 6 using XDA Labs
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
DocRambone said:
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
Click to expand...
Click to collapse
Give it a day, phh is trying to implement fixes to the findings in a more elegant and easier way for the end user, this thread was more intended to share our findings with other devs.
DocRambone said:
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
Click to expand...
Click to collapse
I've booted multiple roms comsic aosp aosip they boot just gotta get it right the first time
Exelios said:
An actual piece of software will be added by the end of the day.
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Ok. Just PM me and I'll move the thread when it happens
Still investigating, there is probably still something to this I'm missing
Exelios said:
Still investigating, there is probably still something to this I'm missing
Click to expand...
Click to collapse
What is the findings so far?
DocRambone said:
What is the findings so far?
Click to expand...
Click to collapse
Other then what's in the OP there seems to be also something else causing issues, not sure yet what exactly it is
Nope, phh just gave me the wrong vbmeta.img, one needs to use stock vbmeta not a modified one omg
I feel like an idiot now
But LOS still doesn't boot, something regarding sensors, stuck on boot logo.
Exelios said:
Other then what's in the OP there seems to be also something else causing issues, not sure yet what exactly it is
Nope, phh just gave me the wrong vbmeta.img, one needs to use stock vbmeta not a modified one omg
I feel like an idiot now
But LOS still doesn't boot, something regarding sensors, stuck on boot logo.
Click to expand...
Click to collapse
I couldn't get v19 of phh's AOSP to boot for the longest time until I tried this! Thanks man!! :good:
I have cleaned up the OP and added clear instructions in post 2.
Tho LOS still doesn't boot for now, but that's because of a bug specific to the GSI, not a bootloader issue.
Delete
CertifiedBlyndGuy said:
Ok. Just PM me and I'll move the thread when it happens
Click to expand...
Click to collapse
Might I ask to make this a sticky?
Because every developer needs to be aware of it, this doesn't affect just GSI, one can run in the same issue even if flashing TWRP or restoring to stock or anything.
And every user should know about the official way to do things on the One Plus 6, which is slightly different then all other phones.
Thanks
The instructions in post 2 is the same as in the treble thread, still no boot other than aosp v18
Related
Hey guys! So, as You know, OP6 has Treble, but when You flash GSI's on it, it will take You to EDL mode instead. Why? Well.. because of A/B and VBMETA partition. So... how do we fix it? It's actually pretty simple! Follow the guide and You will be able to boot GSI roms on Your OP6
Note: Before You can flash any GSI, You have to unlock Your bootloader. To do that, simply type: fastboot oem unlock . Just remember that it will wipe Your data!
Important: Flash 5.1.6 or above before flashing v20. It looks like 5.1.6 fixed Treble problems. Files have been updated to: 5.1.7
Step 1: Download any GSI rom You want, in this guide I'll be using Phh Treble latest build: Phh Treble A/B v20 with GApps and SU
(Make sure to extract it before flashing. You can do that with 7zip)
Step 2: Download this zip. It contains stock VBMETA as well as stock boot image, just in case if Your device is rooted. Link: Treble OP6 Files 5.1.7
Step 3: Extract those files on Your desktop for example and open terminal/cmd in the same folder as Your files. (Before You can do that, You should download latest minimal ADB and Fastboot available here: ADB & Fastboot XDA Thread Link ) Now. Copy and paste those commands:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This command will let You boot non OOS roms, like Phh Treble or any other Treble GSI.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Those commands will flash stock non rooted boot image to both of Your boot partitions (Treble roms need slightly different root that's why we need to use stock boot image for now)
fastboot flash system_a system-arm64-ab-gapps-su.img
fastboot -w flash system_b system-arm64-ab-gapps-su.img
Okay, these commands will flash Phh GSI to both of Your partitions. The only difference is that second command will wipe Your data partition which is most likely required to have a bug free boot. So backup Your data before!
Aaand that's it! :victory: Enjoy Your new GSI rom.
Thanks to Dewang Rocker for making a tutorial video! Make sure to like and subscribe
And one more Thanks to @AxM2 for posting my guide on Github!
OnePlus 6 Treble Github Page
Q/A
Q: Does this method work for all GSI images?
Yes! It should work fine, as long as Your GSI supports A/B partitioning. Most Devs build A/B GSIs so no worries.
Q: Bugs?
Build v20:
Stock camera has problems with focus, but if You install OOS camera it works fine.
Notch is covering screen a little.
Q: I want to see some screenshots!
Credits:
Phhusson for Wonderful GSI!
FunkWizard for latest firmware!
@dylanneve1 for being an awesome friend and helping me with many of my projects.
OnePlus for OP6 and releasing updates that are actually useful!
James Muir for Pixel 2 Guide on Github.
Google for creating Treble for us.
Looks promising! Anyone tried and confirm that the roms boot?
And what does wiping of data partition means? Will that wipe the internal storage too? or just the "data" (The apps and stuff).
any idea what treble rom/s that has the feature of stretching third party apps to use 18:9/19:9 aspect ratio or whatever instead of it being cropped?
Joyarup said:
Looks promising! Anyone tried and confirm that the roms boot?
And what does wiping of data partition means? Will that wipe the internal storage too? or just the "data" (The apps and stuff).
Click to expand...
Click to collapse
It does boot, tried the guide 3 times already just to make sure that it works. And -w will wipe Your internal storage, not just apps. So make sure to backup everything. Or You can just wipe data in TWRP and then boot GSI. This way Your internal storage won't be deleted. But a full backup is always recommended! Even if You flash new fonts or something .
ProtoDeVNan0 said:
It does boot, tried the guide 3 times already just to make sure that it works. And -w will wipe Your internal storage, not just apps. So make sure to backup everything. Or You can just wipe data in TWRP and then boot GSI. This way Your internal storage won't be deleted. But a full backup is always recommended! Even if You flash new fonts or something .
Click to expand...
Click to collapse
Alright thank you for clearing things, I will give it a try and will let you know!
Thank you for your work.
I get unknown option when running the fastboot --disable-verity command
eminem5055 said:
I get unknown option when running the fastboot --disable-verity command
Click to expand...
Click to collapse
Make sure the drivers and adb and fastboot is installed and your command line is in the exact location as your fastboot.
Joyarup said:
Make sure the drivers and adb and fastboot is installed and your command line is in the exact location as your fastboot.
Click to expand...
Click to collapse
That worked thanks!
Abaddon said:
any idea what treble rom/s that has the feature of stretching third party apps to use 18:9/19:9 aspect ratio or whatever instead of it being cropped?
Click to expand...
Click to collapse
No idea if any rom has settings for 18:9/19:9 displays. But there's also the notch that covers the screen. In OOS we can hide the notch, but in Treble roms the notch will cover some parts of the screen in all apps. YouTube should support 18:9/19:9 though. Maybe there is some app that can help with the notch? Or some Magisk module? I think that GravityBox should allow us to resize status bar so that apps won't be covered, but games hide the status bar so it will be useless in games. We might have to wait for Android P to take care of all the notch problems in GSIs.
Thank you for this!!
How is the camera on treble roms?
I think we need to wait P for notch support, or maybe some modders can do something
Thanks for this guide. Looking forward to trying it out. With that said, just so I have my bases covered - What's the best way return to stock OOS if necessary?
Thanks!
I don't think calling works yet, I am getting a soft reboot every time I try.
azsl1326 said:
Thanks for this guide. Looking forward to trying it out. With that said, just so I have my bases covered - What's the best way return to stock OOS if necessary?
Thanks!
Click to expand...
Click to collapse
I got mine back to stock by following this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
sis3970 said:
I got mine back to stock by following this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
Thanks. Did you try this Treble version?
azsl1326 said:
Thanks. Did you try this Treble version?
Click to expand...
Click to collapse
No. Not yet. Planning to tonight.
Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk
sis3970 said:
No. Not yet. Planning to tonight.
Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk
Click to expand...
Click to collapse
Same for me. Also found this forum on XDA for Treble development - https://forum.xda-developers.com/project-treble/trebleenabled-device-development
No boot for me and phhusson, this guide does nothing different then what is mentioned already here as not working > https://forum.xda-developers.com/oneplus-6/help/dev-oneplus-6-luck-treble-seeking-help-t3795202
Tested on a total of 3 devices, no boot on neither, tho Mishaal just told me he got a boot, so it most be something else somewhere we have not yet identified.
Until then I would put a big EXPERIMENTAL and DANGEROUS on this thread.
Can confirm this works, our display tester Dylan Raga got the LineageOS GSI booting.
MishaalRahman said:
Can confirm this works, our display tester Dylan Raga got the LineageOS GSI booting.
Click to expand...
Click to collapse
Exelios said:
tho Mishaal just told me he got a boot, so it most be something else somewhere we have not yet identified.
Click to expand...
Click to collapse
If phh cannot get a boot on his own rom...
I am starting this thread for us users and experiences while using Android Q. What works, what doesn't. I am not a dev. I am a user. Not here to bash anyone if something doesn't work. @topjohnwu just got root released for this last night.
So one thing I found which I am sure will fixed soon is
SD MAID not working.
Afwall is working.
Systemui tuner working
Button mapper working
I am sure as we go on and they will all work great. But like I said this is just a post what you found thread. If something does work, post it. If something doesn't, post it. Even if someone needs something like an apk. Ask and shall receive. This is a time of helping each other. Not flaming and bashing. Thank you to everyone that has read this and thank you to all the great devs out there and thank you to us users that can exchange information peacefully.
Is it still not possible to write to /system?
w0rdie said:
Is it still not possible to write to /system?
Click to expand...
Click to collapse
Same here. I would think the File Explorer devs would have to update to support Q?
Quickswitch is not working, back button did not work for me with it installed
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
I am using a custom kernel so I didn't try to root the stock boot image. But it seems other people are rooting the stock boot image. I would hope they can help you. If I get around to it, I will try and root the stock boot image to see if it works. Someone should be able to help. Custom kernel roots just fine
kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
Make sure you are flashing the patched boot image to both slots.
Sent from my Pixel 3 XL
Eudeferrer said:
Make sure you are flashing the patched boot image to both slots.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
I ran fastboot flash boot_b magisk_patched.img
then
fastboot flash boot_a magisk_patched.img
Same issue still bootloops.
Thanks.
Kevin
so im guessing custom kernels are a no no?
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kevdog98 said:
I ran fastboot flash boot_b magisk_patched.img
then
fastboot flash boot_a magisk_patched.img
Same issue still bootloops.
Thanks.
Kevin
Click to expand...
Click to collapse
I ran into the same issue... it started bootlooping, so I flashed dp4 from scratch and then skipped setup, grabbed the boot.img from the dp4 folder on pc, put it on my phone, installed the newest app.release from canary builds and patched it..... rebooted to bootloader and flashed the boot.img in both slots and rebooted .. it worked
i42o said:
so im guessing custom kernels are a no no?
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
I ran into the same issue... it started bootlooping, so I flashed dp4 from scratch and then skipped setup, grabbed the boot.img from the dp4 folder on pc, put it on my phone, installed the newest app.release from canary builds and patched it..... rebooted to bootloader and flashed the boot.img in both slots and rebooted .. it worked
Click to expand...
Click to collapse
Custom kernel. Singular is a go. That's what I'm running. I didn't have to flash both slots. That doesn't make sense at all. I am going to get my lazy ass off the veranda and flash the rooted boot image.
Edit: I have Pie in my inactive slot and QBeta 4 in my active slot. If that makes any sense to you guys?
What's the problem? Flashed to active slot only.
Your doing something wrong if you can't root the stock boot image
When I originally rooted Q I did it ota patch inactive slot. Bootlooped. I just went to factory recovery and wiped data. Has worked ever since. I believe mine was looping to modules not being compatible with Q yet. Also if you grab the Q image and pull the boot image. You can patch it that way too. With Q, it is finicky with apps because of isolated storage. Which is weird because zarchiver still sees all files but amaze only sees root directory. Files app I noticed is saying some files I have are folders and not disk images. Zarchiver says it right still. Fastboot -w to manually remove all data too. Sometimes Titan m drive can cause weird things that is why I go to stock recovery and wipe it that way, wipes the Titan m drive too.
Did anybody already try to flash ainur sound mod and can report if it's working? For me the main reason to unlock bootloader again and start root procedure on Q...
kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
Same problem here. Already posted the issue at the Magisk thread.
alex1301 said:
Same problem here. Already posted the issue at the Magisk thread.
Click to expand...
Click to collapse
Very strange. Are you guys on the MM Canary channel?
Magisk Manager 228
Magisk Canary 19304
Golf c said:
Very strange. Are you guys on the MM Canary channel?
Magisk Manager 228
Magisk Canary 19304
Click to expand...
Click to collapse
Yeah, updated everyhting before getting started.
alex1301 said:
Yeah, updated everyhting before getting started.
Click to expand...
Click to collapse
Do you have any modules for magisk on your phone? Almost none work at the moment. They are working to get them up and running. Also old data can cause bootloops. Did you leave the Preserve AVB unchecked? If you have Q up and running, check that you are getting the latest magisk zip when patching too.
S8rooted&tooted said:
Do you have any modules for magisk on your phone? Almost none work at the moment. They are working to get them up and running. Also old data can cause bootloops. Did you leave the Preserve AVB unchecked? If you have Q up and running, check that you are getting the latest magisk zip when patching too.
Click to expand...
Click to collapse
Nothing left. My Pixel had never any modules activated or anything else. What is preserve AVB?
Used the latest files.
alex1301 said:
Nothing left. My Pixel had never any modules activated or anything else. What is preserve AVB?
Used the latest files.
Click to expand...
Click to collapse
Click on advanced settings. And make sure when you did patch it, it wasn't checked. It should not be now with 10. With pie it is. Q will not work with it checked. It will double check system to the other partition. And the slot with magisk doesn't match the untouched slot.
I hope you already know how to flash GSI on devices with dyamic partition already. If not then you can follow this guide: https://forum.xda-developers.com/t/...ynamic-super-partition.4256667/#post-85271987
If youre on stock before flashing GSI then dont "fastboot delete-logical-partition product" like other tutorials may suggest. Just flash the product image (fastboot flash product [insert img here]) attached below and it will get resized automatically as well, giving you plenty of space to flash your GSI.
If youve already flashed GSI before following this guide and have done "fastboot delete-logical-partition product" then just create product partition (fastboot create-logical-partition product [size]) and flash the img on product.
whichever course youve taken you can now flash magisk through twrp or patch the boot img and flash that.
Please note that this product image wasnt made by me and the credit for it goes to: @Allexwin50
tested on infinix zero 8 X687
Thanks for the tutorial, I will give it a try but have one question: you said to" create product partition and give size " I don't understand about size!
shjeanpy said:
Thanks for the tutorial, I will give it a try but have one question: you said to" create product partition and give size " I don't understand about size!
Click to expand...
Click to collapse
when you create partition you also need to specify its size, just add some number
kusti420 said:
when you create partition you also need to specify its size, just add some number
Click to expand...
Click to collapse
What size would you advise me please
shjeanpy said:
What size would you advise me please
Click to expand...
Click to collapse
idk, i used 400000000
Thank you very much for your great tutorial. it worked for me on my device.
Thanks a lot for putting this together. I was stuck for a day and a half trying to figure out how to flash Magisk with no product partition. Great work.
nickelnine said:
Thanks a lot for putting this together. I was stuck for a day and a half trying to figure out how to flash Magisk with no product partition. Great work.
Click to expand...
Click to collapse
and i was stuck for multiple months...
@kusti420 if I've flashed a GSI on to stock (apart from flashing vbmeta and TWRP) can I fastboot flash that product.img and then successfully TWRP flash magisk or patch with app (using Phh SU temporarily for root) ? is that enough ?
EDIT 1: thought I'd just see for myself, flashed the product_gsi.img and my phone (S20FE 5G) still booted. tried flashing magisk 21.4 zip from TWRP and got a bootloop. will check later if I can patch my boot.img and post.
Hey, where did you take this product_gsi.img? I think it does not work with Android 12, I wonder if it can be updated or something like that.
felipecassiors said:
Hey, where did you take this product_gsi.img? I think it does not work with Android 12, I wonder if it can be updated or something like that.
Click to expand...
Click to collapse
it was sent to me in telegram, where i also traced it back to @Allexwin50, afaik he made it. worked fine on android 10 and 11. asking him for img for a12 could be an option
Sir, When I Flashed any GSI rom A11 , any way to remove the standard superuser root from rom ? if some solution , please advise me , (my device use fastboot commands not use twrp)
gamal001 said:
Sir, When I Flashed any GSI rom A11 , any way to remove the standard superuser root from rom ? if some solution , please advise me , (my device use fastboot commands not use twrp)
Click to expand...
Click to collapse
idk wtf u mean by "standard superuser root" prolly phh su, if yes then there is definetly a way to get rid of that
Right, so what to do after installing the GSI like this. How to install Magisk? I don't have TWRP. Do I have to "securize" first? Help.
K1569GHENT said:
Right, so what to do after installing the GSI like this. How to install Magisk? I don't have TWRP. Do I have to "securize" first? Help.
Click to expand...
Click to collapse
maybe, cant remember by heart, dont have enough time to test it out myself
Working on Nippon Android Tiramisu SGSI on Pixel 3a, very nice
K1569GHENT said:
Right, so what to do after installing the GSI like this. How to install Magisk? I don't have TWRP. Do I have to "securize" first? Help.
Click to expand...
Click to collapse
Obtain a stock copy of your boot.img.
Patch it through the magisk app before you do your whole thing installing your chosen gsi.
Once you have the patched image, you can fastboot it using fastboot flash boot boot.img in cmd onto your gsi ROM.
Make sure to install the boot.img to both slots A and B. Then go back to your active slot.
ninjasinabag said:
Obtain a stock copy of your boot.img.
Patch it through the magisk app before you do your whole thing installing your chosen gsi.
Once you have the patched image, you can fastboot it using fastboot flash boot boot.img in cmd onto your gsi ROM.
Make sure to install the boot.img to both slots A and B. Then go back to your active slot.
Click to expand...
Click to collapse
he talked about removing phh-superuser
kusti420 said:
he talked about removing phh-superuser
Click to expand...
Click to collapse
It's locked to your boot image, so using 100% stock image removes superuser since it's no longer system as root.
kusti420 said:
I hope you already know how to flash GSI on devices with dyamic partition already. If not then you can follow this guide: https://forum.xda-developers.com/t/...ynamic-super-partition.4256667/#post-85271987
If youre on stock before flashing GSI then dont "fastboot delete-logical-partition product" like other tutorials may suggest. Just flash the product image (fastboot flash product [insert img here]) attached below and it will get resized automatically as well, giving you plenty of space to flash your GSI.
If youve already flashed GSI before following this guide and have done "fastboot delete-logical-partition product" then just create product partition (fastboot create-logical-partition product [size]) and flash the img on product.
whichever course youve taken you can now flash magisk through twrp or patch the boot img and flash that.
Please note that this product image wasnt made by me and the credit for it goes to: @Allexwin50
Click to expand...
Click to collapse
Hello kusti420
I had already deleted the product partition when I found your post.
The GSI was not cool.
I reflash the product partition and reflash the GSI, now it's good.
Thanks for the file and the tip.
Does anyone know where I can find a stock Rom preferably android 10 that I can flash in TWRP? I have the fastboot roms but when flashing vbmeta there is no partition choice to flash it to but the partition exists on both a and b slots after a gdisk print command. And I have no clue on how I would flash the bin files in TWRP. Also the same problem exists for bootloader and a few others just like vbmeta. I need stock because I completely screwed my A11 stock after a faulty magisk install and didn't know I couldn't install customs from A11. I've been away for a little bit and instead of doing homework I acted as if everything was the same from 10 to 11 and well...here I am. No computer access so fastboot is out of the question. Am I screwed until I have computer access? Thanks again,
Rooster
bigrooster88 said:
Does anyone know where I can find a stock Rom preferably android 10 that I can flash in TWRP? I have the fastboot roms but when flashing vbmeta there is no partition choice to flash it to but the partition exists on both a and b slots after a gdisk print command. And I have no clue on how I would flash the bin files in TWRP. Also the same problem exists for bootloader and a few others just like vbmeta. I need stock because I completely screwed my A11 stock after a faulty magisk install and didn't know I couldn't install customs from A11. I've been away for a little bit and instead of doing homework I acted as if everything was the same from 10 to 11 and well...here I am. No computer access so fastboot is out of the question. Am I screwed until I have computer access? Thanks again,
Rooster
Click to expand...
Click to collapse
Hi rooster, have a look at the link below. The rom is from trusted guys who have been doing moto stuff for years. Follow the instructions, and hopefully you have a good result.
Motorola Stock ROM: Sofiap // Pro
telegra.ph
Beetle84 said:
Hi rooster, have a look at the link below. The rom is from trusted guys who have been doing moto stuff for years. Follow the instructions, and hopefully you have a good result.
Motorola Stock ROM: Sofiap // Pro
telegra.ph
Click to expand...
Click to collapse
OK brother I just flashed the Rom following all instructions minus erase userdata, which is a step I usually take but I don't have fastboot right now, and it's still booting up has been for 2-3 minutes but it finally vibrated when I started it up so I'm expecting good things. Thanks so much....and there she is she started lol perfect timing! You have helped me so much as this is my daily now that I've lost my OnePlus.
Edit
everything seems to be working fine except for my calls. They don't come through but they show as missed and when I try to dial out it goes to call but then goes straight to call ended. Everything else is working tho.
One more thing..is there a certain process to root? When I flashed the magisk zip it sent me into a boot loop.
Hello!
I tried the search function but my search-fu isn't strong today. I got a Vortex V22 phone from Standup Wireless. I must have been half asleep, because when i flashed what I assumed was the correct boot.img, I got stuck in a boot loop.
On further investigation, I had flashed the boot for another device called Vortex. I am having incredible difficulty in finding the right boot image. The info I have from the side of the box is:
Vortex V22 4G LTE
Color: Graphite Blue
ROM 32GB
RAM 3GB
OS Android 11
FCC ID 2ADLJ-V22
I deeply appreciate any and all help. Thanks so much!
i was trying to find a phone case for the phone what model number is yours ?
If you're still searching I can try to make a rom dump, I have this phone as well brand new untouched or registered.
I'd just need a tutorial on the proper way to dump and extract the files so I can upload the boot.img
_
I've never used it cause I put the StandUp Wireless sim in my T-Mo InSeeGo 5G HotSpot and prefer to use my Galaxy S8 with Keyboard Cover Case and Unihertz Titan Pocket
Just dumping the firmware from mine, using SP Flash Tool. Used this guide: https://www.hovatek.com/forum/thread-12719.html
Will remove userdata & cache, but there is a LOT of gbs of system data. This phone is appearently Treble-enabled with VNDK ver 30, so yes, you can flash a GSI on there. Will provide a custom recovery necessary.
Edit: if you were wondering, this phone has a MT6761 with a eMMC flash.
PicelBoi said:
Just dumping the firmware from mine, using SP Flash Tool. Used this guide: https://www.hovatek.com/forum/thread-12719.html
Will remove userdata & cache, but there is a LOT of gbs of system data. This phone is appearently Treble-enabled with VNDK ver 30, so yes, you can flash a GSI on there. Will provide a custom recovery necessary.
Edit: if you were wondering, this phone has a MT6761 with a eMMC flash.
Click to expand...
Click to collapse
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
In fastboot not fastboot d do
Fastboot flash unlocking
And it'll ask ya if u agree bs....
& Click yes.
Mtkclient unlocks bootloader as well
defcondoc said:
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
Click to expand...
Click to collapse
Sorry for waiting so long! Yeah, I got the firmware! Also follow previous guys post! Do you want my boot.img? Make sure you disable Android Verified Boot too!
PicelBoi said:
Sorry for waiting so long! Yeah, I got the firmware! Also follow previous guys post! Do you want my boot.img? Make sure you disable Android Verified Boot too!
Click to expand...
Click to collapse
No worries. Yes! Do you have the entire rom? The boot.img would definitiely be great as well.
mee too
defcondoc said:
No worries. Yes! Do you have the entire rom? The boot.img would definitiely be great as well.
Click to expand...
Click to collapse
Yea, will post it later this day! Do you need anything else like my super partition?
PicelBoi said:
Yea, will post it later this day!
Click to expand...
Click to collapse
Also this is a GSI image that works with this device - https://github.com/phhusson/treble_experimentations/releases/tag/v313 - newer versions might not work unfortunately.
defcondoc said:
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
Click to expand...
Click to collapse
You need to reboot to userland fastboot, which you could do by rebooting to normal fastboot then telling fastboot to reboot to fastboot by typing in fastboot reboot fastboot. You will see a new screen, and now you could flash a GSI to the phone.
PicelBoi said:
Also this is a GSI image that works with this device - https://github.com/phhusson/treble_experimentations/releases/tag/v313 - newer versions might not work unfortunately.
Click to expand...
Click to collapse
I was able to get a bunch of GSI's that work with it, including the phone you posted, but I was looking to get root and found a couple pre-rooted GSI's that work as well. Newer ones do work as well I has 13 rooted and working. However, I liked the Pixel ROMs the best and would prefer to install those instead and then root. So I need the firmware for that so I can patch a modified boot.img.
PicelBoi said:
You need to reboot to userland fastboot, which you could do by rebooting to normal fastboot then telling fastboot to reboot to fastboot by typing in fastboot reboot fastboot. You will see a new screen, and now you could flash a GSI to the phone.
Click to expand...
Click to collapse
Thank you. I understand and have a lot of experience with this. However, I still never understood why there is two Fastboot's.
I can't get it to boot in one I flash the super that I backed up that don't get it to boot maybe I could use a good super. What about vbmeta?
atsalchenberg said:
I can't get it to boot in one I flash the super that I backed up that don't get it to boot maybe I could use a good super. What about vbmeta?
Click to expand...
Click to collapse
Are you looking for a good GSI ROM?
As of right now I'm just trying to get it booted up with any room. I got it rooted and then something I ****ed up when I tried to flash a GSI. And I started messing with the boot a boot b vbMeta from system and blank. And I don't have the firmware an the super that I backed up won't boot when I flash it.
But yes I am indeed looking for a good running a12 rom
atsalchenberg said:
As of right now I'm just trying to get it booted up with any room. I got it rooted and then something I ****ed up when I tried to flash a GSI. And I started messing with the boot a boot b vbMeta from system and blank. And I don't have the firmware an the super that I backed up won't boot when I flash it.
Click to expand...
Click to collapse
I completely messed up one messing with partitions and it took many tries trying to get to was able to still get to the bootloader fastboot and then recovery to fastbootD. You should be able to get it booted into fastbootd and flash as it seems you can.
Try the one below. you should be able to find it with a google search. If you can't let me know and I will try to look and see where I downloaded it from as I cannot remember where I found it.
I've tried many GSI ROM's Some boot fully, some only boot to the boot screen and some won't boot at all.
I'm using 13 rooted LineageOS GSI version 20-20230324-UNOFFICIAL-arm64_bvS
It is vanilla. I can't remember if there is a GAPPS version or not. But you can load it all after with magisk. But its rooted.
I still would like if picelboi could share the stock rom, so we can have a boot.img. I would like to try other ROM's that are not PRE-Rooted.
atsalchenberg said:
But yes I am indeed looking for a good running a12 rom
Click to expand...
Click to collapse
I can't remember which A12 I had working but I was looking for root and the one A12 that was prerooted I had issues with so I went to A13.
This is an A13. LineageOS GSI version 20-20230324-UNOFFICIAL-arm64_bvS
There may be a newer version of it now.
Also, these phones seem have that internet connect issue with some GSI ROMS and this is one of them I think, they connect to wifi but they won't actually connect to internet, but there is a easy fix for it.