This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that
First!
Sent from my Pixel 2 XL using Tapatalk
slothdabski said:
First!
Click to expand...
Click to collapse
Crap missed it..
sixohtew said:
This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that
Click to expand...
Click to collapse
does google camera work with hdr+? do you get unlimited photo storage?
sixohtew said:
This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that
Click to expand...
Click to collapse
We should all be here not everyone can do what you do..
I can't get twrp to load after flashing.....it just hangs at the start up screen. Any suggestions? I went back to stock and flashed over that.
cdnsnOw said:
We should all be here not everyone can do what you do..
Click to expand...
Click to collapse
What I meant was if you don't know how to use fastboot, you probably shouldn't be messing with your phone because you used the wrong code and bricked it..no offense
What is the difference flashing with TWRP and fastboot method?
So far no luck getting it to boot. This is what I did.
fastboot flash system_a system.img
fastboot flash vbmeta_a vbmeta.img
then boot into twrp and wipe data and reboot
Going to update to the leatest April image and try again.
gforceriders said:
So far no luck getting it to boot. This is what I did.
fastboot flash system_a system.img
fastboot flash vbmeta_a vbmeta.img
then boot into twrp and wipe data and reboot
Going to update to the leatest April image and try again.
Click to expand...
Click to collapse
Maybe after flashing vbmeta reboot bootloader then load up twrp
cdnsnOw said:
What is the difference flashing with TWRP and fastboot method?
Click to expand...
Click to collapse
This is a system.img and needs to be flashed to the system which requires fastboot..in twrp you MUST make sure you're flashing to the system_a partition
sixohtew said:
Maybe after flashing vbmeta reboot bootloader then load up twrp
Click to expand...
Click to collapse
Yeah did that still no luck getting it to boot. Can't even switch to slot A without getting an error after fastbooting the images.
abduleo77 said:
I can't get twrp to load after flashing.....it just hangs at the start up screen. Any suggestions? I went back to stock and flashed over that.
Click to expand...
Click to collapse
Try booting twrp right after the vbmeta.img
gforceriders said:
Yeah did that still no luck getting it to boot. Can't even switch to slot A without getting an error after fastbooting the images.
Click to expand...
Click to collapse
Which device? Pixel 2 xl?
sixohtew said:
Which device? Pixel 2 xl?
Click to expand...
Click to collapse
Yep, the pixel 2 XL.
gforceriders said:
Yep, the pixel 2 XL.
Click to expand...
Click to collapse
Did you come from another rom or were you stock? This boots just fine for me
sixohtew said:
Did you come from another rom or were you stock? This boots just fine for me
Click to expand...
Click to collapse
Yes, came from another rom and when that didn't work I went back to stock and still wouldn't boot.
gforceriders said:
Yes, came from another rom and when that didn't work I went back to stock and still wouldn't boot.
Click to expand...
Click to collapse
Does it bootloop? Or boot back to the bootloader? If it boot loops are you seeing the aokp boot animation? Could you possibly get a logcat?
sixohtew said:
Does it bootloop? Or boot back to the bootloader? If it boot loops are you seeing the aokp boot animation? Could you possibly get a logcat?
Click to expand...
Click to collapse
It bootloops. No aokp boot animation. I will try and use the bootloop fix script and flash full stock and test again here shortly.
gforceriders said:
It bootloops. No aokp boot animation. I will try and use the bootloop fix script and flash full stock and test again here shortly.
Click to expand...
Click to collapse
Yeah if you tried to flash it over another rom instead of stock, issues could arise..I'll put a script together that will flash stock with the new system.img and add the vbmeta.img to it so it flashes all the necessary files
Related
Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices
motcher41 said:
Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices
Click to expand...
Click to collapse
How did you get to DP3? Did you enroll in the beta program?
Badger50 said:
How did you get to DP3? Did you enroll in the beta program?
Click to expand...
Click to collapse
yes and weirdly using a factory image on my Mi A1 gave no error
motcher41 said:
yes
Click to expand...
Click to collapse
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:
Badger50 said:
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:
Click to expand...
Click to collapse
i would but i am currently soft bricked. have access to bootloader only
even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc
motcher41 said:
even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc
Click to expand...
Click to collapse
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.
but are they all the same target as the .img name
Badger50 said:
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.
Click to expand...
Click to collapse
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too
motcher41 said:
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too
Click to expand...
Click to collapse
Hey, as long as it worked your good. Welcome :good:
Yeah my format userdata may have been off. I was going by memory from my 6p. P2XL might be different. Sorry.
Any idea when TWRP will have builds for the Pixel 3/3XL?
Looking forward to having TWRP available for this phone.
TWRP is in Hawaii, I think TWRP tweeted he will build it when get gets out of rehab. So, hold your breath and it will show up in ROM section, hopefully...
OR it's open source and you could build and test it yourself? I make crap up a lot so who knows if that was even true..?
Truth - Dees_Troy may be the dev to follow but please never ask (it's rude and a big no no) Kinda like asking your neighbor when they are going to bake a cake and give it to you...and you have never talked to them before.
This could be another Pixel C situation where it will take quite some time before we get twrp. It's still possible to get ROMs, they would just need to be flashed in fastboot instead or use a script to flash the rom in the opposite boot slot.
The device is still very young, even if we had twrp that wouldn't bring ROMs to table immediately.
Hell I remember the old days when it was required to flash a rom through your computer, but all of that took time.
Sent from my Pixel 3 XL using Tapatalk
It is done by the master! https://twitter.com/topjohnwu/status/1057739432495906826?s=19
Sent from my Pixel 3 XL using XDA-Developers Legacy app
Eudeferrer said:
It is done by the master! https://twitter.com/topjohnwu/status/1057739432495906826?s=19
Click to expand...
Click to collapse
Gimme gimme gimme
Sent from my crosshatch using XDA Labs
Eudeferrer said:
It is done by the master! https://twitter.com/topjohnwu/status/1057739432495906826?s=19
Sent from my Pixel 3 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
mannn the party is just getting started
masri1987 said:
mannn the party is just getting started
Click to expand...
Click to collapse
Can't wait to get my hands on it.
Sent from my Pixel 3 XL using XDA-Developers Legacy app
Is this real and we haven't figured out how to get it loaded onto our phones?
This is awesome and I am sure it will be out soon but I would def rather they take their time and work out all the kinks.
Yais!!! Hopefully it'll be out by Monday, just in time for the security update to come out!
Dam. Was hoping it'd be released today... just getting mine today in about 2 hours and was hoping it's be out by the time I got mine
Eudeferrer said:
It is done by the master! https://twitter.com/topjohnwu/status/1057739432495906826?s=19
Sent from my Pixel 3 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
what screen protector is that?
brandonpa said:
Is this real and we haven't figured out how to get it loaded onto our phones?
Click to expand...
Click to collapse
Once it's made public, install should be pretty similar to OGP and P2's...
Sent from my Pixel 3 XL using Tapatalk
MArtyChubbs said:
Once it's made public, install should be pretty similar to OGP and P2's...
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
for those of us unfamiliar with that method please inform us
masri1987 said:
for those of us unfamiliar with that method please inform us
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=74362968
Sent from my Pixel 3 XL using Tapatalk
MArtyChubbs said:
https://forum.xda-developers.com/showthread.php?p=74362968
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
okay so similar to op6 method.
Temp boot into TWRP
Flash TWRP within the temp one.
Voila
masri1987 said:
okay so similar to op6 method.
Temp boot into TWRP
Flash TWRP within the temp one.
Voila
Click to expand...
Click to collapse
Yes sir.
Will this workflow work if this is like Pixel 2 XL? I see the 3 XL files on TWRP HERE:
https://dl.twrp.me/crosshatch/
Here is my procedure to update to a new factory lmk if you all think it will work:
1) Download Magisk, place apk, zip, twrp and uninstaller on device.
2) Download latest factory image
3) adb reboot-bootloader
4)
fastboot flash bootloader bootloader-x.img
fastboot reboot-bootloader
fastboot flash radio radio-x.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot-bootloader
5) optional - clean caches
6) boot normally 1x
7) place payloads on device
MagiskManager-apk
Magisk-uninstaller-x.zip
Magisk-vx.zip
twrp-3.2.x-x-x.img
8) reboot normally
9) boot into recovery (TWRP) (temp boot)
fastboot boot twrp-3.2.x-x-x.img
10) install magisk via zip while in twrp.
11) reboot normally
12) check magisk with magisk app
13) check safety net pass
14) use monkey to start all apps.
15) done.
Let me know if this workflow "should work". in your opinion, thats what I followed in the PrePixel2 days. Always worked nicely.
mickrussom said:
Will this workflow work if this is like Pixel 2 XL? I see the 3 XL files on TWRP HERE:
https://dl.twrp.me/crosshatch/
Here is my procedure to update to a new factory lmk if you all think it will work:
1) Download Magisk, place apk, zip, twrp and uninstaller on device.
2) Download latest factory image
3) adb reboot-bootloader
4)
fastboot flash bootloader bootloader-x.img
fastboot reboot-bootloader
fastboot flash radio radio-x.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot-bootloader
5) optional - clean caches
6) boot normally 1x
7) place payloads on device
MagiskManager-apk
Magisk-uninstaller-x.zip
Magisk-vx.zip
twrp-3.2.x-x-x.img
8) reboot normally
9) boot into recovery (TWRP) (temp boot)
fastboot boot twrp-3.2.x-x-x.img
10) install magisk via zip while in twrp.
11) reboot normally
12) check magisk with magisk app
13) check safety net pass
14) use monkey to start all apps.
15) done.
Let me know if this workflow "should work". in your opinion, thats what I followed in the PrePixel2 days. Always worked nicely.
Click to expand...
Click to collapse
Clearly twrp is available...
Has anyone dared to flash it?
masri1987 said:
Clearly twrp is available...
Has anyone dared to flash it?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-3-xl/development/twrp-3-2-3-0-pixel-3-xl-t3861623
Yep.
Fastbooted twrp img, then flashed twrp zip and then magisk 17.4...rebooted and then magic!!!!!!!!!!! Until I rebooted to recovery and no touchscreen. Np, booting to twrp.img for me. I just use it to install magisk.
Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?
welp, just tried to flash the factory image and got this:
error: failed to load 'image-crosshatch-pq1a.181205.006.zip': Not enough space
mac208x said:
Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?
Click to expand...
Click to collapse
fastboot flash boot --slot all boot.img
#6 in this guide.
Homeboy76 said:
fastboot flash boot --slot all boot.img
#6 in this guide.
Click to expand...
Click to collapse
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?
mac208x said:
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?
Click to expand...
Click to collapse
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- Edit: Kernel of your choice
- Add more zips
- magisk-17.3.zip
- reboot system
Homeboy76 said:
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- ElementalX 1.02.zip
- Add more zips
- magisk-17.3.zip
- reboot system
Click to expand...
Click to collapse
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery
mac208x said:
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery
Click to expand...
Click to collapse
After installing the TWRP.zip change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.
airmaxx23 said:
Change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.
Click to expand...
Click to collapse
Im so sorry but what do you mean by slot?
mac208x said:
Im so sorry but what do you mean by slot?
Click to expand...
Click to collapse
When you're in TWRP go to reboot, then switch from your current slot to the other.
airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp
mac208x said:
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp
Click to expand...
Click to collapse
Are you flashing Magisk in both slots?
airmaxx23 said:
Are you flashing Magisk in both slots?
Click to expand...
Click to collapse
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?
mac208x said:
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?
Click to expand...
Click to collapse
Try just that first and see if you can fully boot the phone.
airmaxx23 said:
Try just that first and see if you can fully boot the phone.
Click to expand...
Click to collapse
No bootloop back to trwp. Now its stuck on the white google logo screen wont go pass it
airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
jd1639 said:
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've been doing it all along whenever I flash anything.
mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
You'll have to flash back to stock in fastboot.
mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app
airmaxx23 said:
I've been doing it all along whenever I flash anything.
You'll have to flash back to stock in fastboot.
Click to expand...
Click to collapse
jd1639 said:
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip
mac208x said:
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip
Click to expand...
Click to collapse
Do you have the latest sdk platform tools. If not Google that, download the zip and extract it. Replace what you do have. I create a folder c:adb and put everything in that. Then set an environment variable path in Windows so fastboot and adb are available no matter what folder I'm working in.
Sent from my [device_name] using XDA-Developers Legacy app
Has anyone tried to flash it? I remember there being an issue with the layout of our partitions and what not. Just thought I'd ask because it's pretty nice on my pixel 3.
https://developer.android.com/topic/generic-system-image/releases
can't download, when you put gmail ans password account there is the security code from usb? what is it? if you have other link ill be appreciated thanks
Oh that is weird, I've never seen that before.
Me too, I will try it but I can't find the file to download
I just tried flashing system and vbmeta and also did fastboot -w, but its showing android logo at boot screen, and animation is a bootloop. Luckily adb devices shows my phone, but unauthorized
Sparker0i said:
I just tried flashing system and vbmeta and also did fastboot -w, but its showing android logo at boot screen, and animation is a bootloop. Luckily adb devices shows my phone, but unauthorized
Click to expand...
Click to collapse
where you downloaded ? can you provide a functional link? thanks
iaio72 said:
where you downloaded ? can you provide a functional link? thanks
Click to expand...
Click to collapse
Official site where the Android 11 gsi is available
Sparker0i said:
Official site where the Android 11 gsi is available
Click to expand...
Click to collapse
Yes of course but download doesn't work...
iaio72 said:
Yes of course but download doesn't work...
Click to expand...
Click to collapse
Sure you can't download the arm64 + gms zip from here: https://developer.android.com/topic/generic-system-image/releases . I can download..
Sparker0i said:
Sure you can't download the arm64 + gms zip from here: https://developer.android.com/topic/generic-system-image/releases . I can download..
Click to expand...
Click to collapse
ok im flashed but at reboot the phone remain in "qualcomm crash dump test"
i think not is good for our op7t
iaio72 said:
ok im flashed but at reboot the phone remain in "qualcomm crash dump test"
i think not is good for our op7t
Click to expand...
Click to collapse
Not really in crashdump mode, but for me it was on bootloop at Android logo screen
i have the same issue i believe we need an updated version of vbmeta and a custom boot.img because i have been able to get it to boot but as previously stated before it just bootloops on the android screen
how did you flash the android 11 gsi and the vbmeta?
i flashed it via fastboot commands
I tried several times and still trying . with system.img and vbmeta.img from google stuck at boot screen (Android logo waiting on screen) . Other custom builds (like erfangsi) is giving qualcomm crash dump without google vbmeta . No lack to boot until now . BUt there are some successful boot videos on internet with especially xiaomi phones . I don't know it is real or not . As far as I know op7t %100 of treble compatible phone and it should work .
intana said:
I tried several times and still trying . with system.img and vbmeta.img from google stuck at boot screen (Android logo waiting on screen) . Other custom builds (like erfangsi) is giving qualcomm crash dump without google vbmeta . No lack to boot until now . BUt there are some successful boot videos on internet with especially xiaomi phones . I don't know it is real or not . As far as I know op7t %100 of treble compatible phone and it should work .
Click to expand...
Click to collapse
I don't mean to ask a obvious question that I'm sure you did after you flashed but did you try flashing then booting into recovery and wiping caches and reboot? Prob won't work but worth a try
SICKMADE said:
I don't mean to ask a obvious question that I'm sure you did after you flashed but did you try flashing then booting into recovery and wiping caches and reboot? Prob won't work but worth a try
Click to expand...
Click to collapse
Yes I did . But it didn't work . I am trying every new build and custom roms about op7t-hotdogb and op7tpro-hotdog also . As you know op7tpro's custom roms are running on op7t with some minor problems like fod . Thanks for the advice
SICKMADE said:
I don't mean to ask a obvious question that I'm sure you did after you flashed but did you try flashing then booting into recovery and wiping caches and reboot? Prob won't work but worth a try
Click to expand...
Click to collapse
lol long time no see dude remember you from way back in note 4 days
btw ive been trying to get this to work for a few days lol still trying hopeful it will work
with which fastboot commands did you flash the gsi and the vbmeta
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
fastboot flash system_a GSI.img
fastboot flash system_b GSI.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
ChrisFeiveel84 said:
with which fastboot commands did you flash the gsi and the vbmeta
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
fastboot flash system_a GSI.img
fastboot flash system_b GSI.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
after "fastboot reboot fastboot" and fastboot -w I used same commands and used system.img and vbmeta.img from the below link (it includes its own vbmeta.img and it says it is AVB verification disabled) then reboot recovery delete cache and data again .
"https://developer.android.com/preview/gsi-release-notes"
OnePlus 7T OxygenOS 11.0.1.1.HD65AA Global boot.img
Stock: https://mega.nz/file/GMtlFIwR#6-J_kxKul0N4KGcBUn0vilyMJqtiRpqdteEWZTWlAvo
Magisk v23.0 Patched: https://mega.nz/file/7QknRQaL#eWBYPAw4-x_DRdMiQRDOauSF_PNgQBOIVZXPu1kxrV0
thexile said:
OnePlus 7T OxygenOS 11.0.1.1.HD65AA Global boot.img
Stock: https://srv-store1.gofile.io/download/9sV6fm/e23f3ec51a5f37cb2b979cc77845fbf9/boot.img
Magisk v23.0 Patched: https://srv-store1.gofile.io/downlo...1f9a1476987252769df2/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks - just tried 11.0.1.1 - Works fine so far. https://forum.xda-developers.com/t/stable-oxygen-os-11-now-released.4250755/post-85078197 (screenies, etc)
thexile said:
OnePlus 7T OxygenOS 11.0.1.1.HD65AA Global boot.img
Stock: https://srv-store1.gofile.io/download/9sV6fm/e23f3ec51a5f37cb2b979cc77845fbf9/boot.img
Magisk v23.0 Patched: https://srv-store1.gofile.io/downlo...1f9a1476987252769df2/magisk_patched-23000.img
Click to expand...
Click to collapse
fastboot boot magisk.img gets me stuck in a boot loop. had the same issue with the last android 11 update
posiblyLopsided said:
fastboot boot magisk.img gets me stuck in a boot loop. had the same issue with the last android 11 update
Click to expand...
Click to collapse
Usually, "fastboot boot [image.img]" is done where you just wish to temporarily try/boot without flashing a self-sufficient image, like some version of TWRP. I'm not sure what your intent was. If it was to just do what we did ^^, and flash the patched image, the statement would be more like this:
First one is for example flashing magisk_patched.img to the B partition. I'd also flash it to the boot_a partition.
fastboot flash boot_b magisk_patched.img
fastboot flash boot_a magisk_patched.img
Or if a pre-dual-partitioning system, then fastboot flash boot {imagename}
hachamacha said:
Usually, "fastboot boot [image.img]" is done where you just wish to temporarily try/boot without flashing a self-sufficient image, like some version of TWRP. I'm not sure what your intent was. If it was to just do what we did ^^, and flash the patched image, the statement would be more like this:
First one is for example flashing magisk_patched.img to the B partition. I'd also flash it to the boot_a partition.
fastboot flash boot_b magisk_patched.img
fastboot flash boot_a magisk_patched.img
Or if a pre-dual-partitioning system, then fastboot flash boot {imagename}
Click to expand...
Click to collapse
i always boot before flashing in case smth like this happens like getting stuck in a boot loop then i dont risk losing data. is there a difference between flashing and booting that could cause it to boot loop?
Did dirty upgrade from 11.0.0.2 to 11.0.1.1. Took longer than usual to boot, but it booted up. Then did fastboot flast boot magisk_patched-23000.img (no _a or _b), rebooted, and got my root back. Went to store and paid with GPay.
Links are not working.
Can you please add any mirror
zaibansari20 said:
Links are not working.
Can you please add any mirror
Click to expand...
Click to collapse
Fixed
thexile said:
Fixed
Click to expand...
Click to collapse
Links are broken again, can you add a mirror
TurnrDev said:
Links are broken again, can you add a mirror
Click to expand...
Click to collapse
Here you go: https://gofile.io/d/L1u4hF
thexile said:
Here you go: https://gofile.io/d/L1u4hF
Click to expand...
Click to collapse
Link is dead, can you reupload please?
gmpetrov said:
Link is dead, can you reupload please?
Click to expand...
Click to collapse
96 MB file on MEGA
mega.nz
thexile said:
96 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
Thx you. Can you share also the stock image please ?
gmpetrov said:
Thx you. Can you share also the stock image please ?
Click to expand...
Click to collapse
Check first post.
Meri flashl Kam nahin kar rahi sahi se