Hello, has anybody tried some GSI roms? Maybe the havoc os? I've heard that they should work with any Snapdragon powered device. I need to wait 6 days until my bootloader is unlocked and maybe somebody tested some roms already. Thanks in advance and stay healthy
I'm currently running phh's gsi with gcam as a daily driver ?
bigyin said:
I'm currently running phh's gsi with gcam as a daily driver ?
Click to expand...
Click to collapse
Okay nice. Are there any major bugs or do you use it as a daily driver?
Effzeh1948 said:
Okay nice. Are there any major bugs or do you use it as a daily driver?
Click to expand...
Click to collapse
For me I'm running it as a daily, there are a few bugs ie finger print scanner doesn't work but I just use pin for security anyway.
I was quite surprised how well it actually runs and very fast compared to miui, great battery etc.
bigyin said:
For me I'm running it as a daily, there are a few bugs ie finger print scanner doesn't work but I just use pin for security anyway.
I was quite surprised how well it actually runs and very fast compared to miui, great battery etc.
Click to expand...
Click to collapse
And 90hz display also works? If yes I will try it out once my bootloader is unlocked
Effzeh1948 said:
And 90hz display also works? If yes I will try it out once my bootloader is unlocked
Click to expand...
Click to collapse
No sorry just 60hz just now but tbh I've not actually missed 90hz.
There's an aosp Rom in the works at the moment for our device, so this is a good substitute until it's out for me personally.
Okay and is there anything I have to do special when I want to flash it?
bigyin said:
For me I'm running it as a daily, there are a few bugs ie finger print scanner doesn't work but I just use pin for security anyway.
I was quite surprised how well it actually runs and very fast compared to miui, great battery etc.
Click to expand...
Click to collapse
Does VoLTE work in this ROM?My SIM is Jio.
pnsdhrn said:
Does VoLTE work in this ROM?My SIM is Jio.
Click to expand...
Click to collapse
No not for me sorry.
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
Effzeh1948 said:
Okay and is there anything I have to do special when I want to flash it?
Click to expand...
Click to collapse
For starters you must have "stock recovery" and not twrp as it won't work.
Are you good with fastboot etc?
Effzeh1948 said:
Hello, has anybody tried some GSI roms? Maybe the havoc os? I've heard that they should work with any Snapdragon powered device. I need to wait 6 days until my bootloader is unlocked and maybe somebody tested some roms already. Thanks in advance and stay healthy
Click to expand...
Click to collapse
So I can speak to using Phh's GSI ROM as I tried out the v222 patch not too long ago. They do infact work, but they are missing a couple of features - Fingerprint does not work at all, 90Hz is not working (stuck at 60Hz) even with forcing it with ADB refresh rate command, VoLTE / Wifi Calling does not work, but the core functionality works at least. The problem I had with using the GSI, is that I bought a Xiaomi Mi 10 because it was in the premium segment of smartphones... missing all these key features with something as simple as a in-screen fingerprint or 90Hz placed it below the premium device I originally purchased. That's just my personal opinion of course, it depends how much you value your freedom over your device as the GSI/project treble images allow you to do that. There is an entry on the Phh's list for our device for what works and what doesnt. Can't link due to posting verification. Nothing has changed in terms of me testing the v222 patch.
To get to the point of fastboot if you are not experienced with debugging shell scripting, this will be incredibly tricky. Some issues are not apparent unless you see them. For example, the instructions listed on the Phh table is the following:
$ fastboot flash recovery stock-recovery.img (using official miui recovery)
$ fastboot reboot fastboot
$ fastboot flash system system-quack-arm64-ab-gapps.img
$ fastboot -w (wipe userdata)
$ fastboot reboot
I can tell you these have a LOT of caveats. For example, do you know how to enable USB debugging on your device and have the correct fastboot for your OS? If you don't, you need to know how to. Secondly, inorder to reference the "stock recovery img" file, you must point it to the directory of the image file.. if you dont know how to do any of that youre going to have a seriously tough time. Lastly, one other protip I can give you is that during the fastbootd phase, ENSURE you have fastboot connectivity by doing "fastboot devices" ! That tripped me because I had the correct drivers for ADB and fastboot, but fastbootd is another implementation after android 10. So you must have the correct drivers if you dont see your device listed under fastboot devices during fastbootd. you can grab them by googling, they come from XIaomi cn website and enabling it through Windows device manager if you use Windows. They are not signed, so you will have to bypass signature verification on bootup setting for Windows. Good luck let me know if you go through with installing it, I'd like to see how Havok performs!
xda-jimjongs said:
So I can speak to using Phh's GSI ROM as I tried out the v222 patch not too long ago. They do infact work, but they are missing a couple of features - Fingerprint does not work at all, 90Hz is not working (stuck at 60Hz) even with forcing it with ADB refresh rate command, VoLTE / Wifi Calling does not work, but the core functionality works at least. The problem I had with using the GSI, is that I bought a Xiaomi Mi 10 because it was in the premium segment of smartphones... missing all these key features with something as simple as a in-screen fingerprint or 90Hz placed it below the premium device I originally purchased. That's just my personal opinion of course, it depends how much you value your freedom over your device as the GSI/project treble images allow you to do that. There is an entry on the Phh's list for our device for what works and what doesnt. Can't link due to posting verification. Nothing has changed in terms of me testing the v222 patch.
To get to the point of fastboot if you are not experienced with debugging shell scripting, this will be incredibly tricky. Some issues are not apparent unless you see them. For example, the instructions listed on the Phh table is the following:
$ fastboot flash recovery stock-recovery.img (using official miui recovery)
$ fastboot reboot fastboot
$ fastboot flash system system-quack-arm64-ab-gapps.img
$ fastboot -w (wipe userdata)
$ fastboot reboot
I can tell you these have a LOT of caveats. For example, do you know how to enable USB debugging on your device and have the correct fastboot for your OS? If you don't, you need to know how to. Secondly, inorder to reference the "stock recovery img" file, you must point it to the directory of the image file.. if you dont know how to do any of that youre going to have a seriously tough time. Lastly, one other protip I can give you is that during the fastbootd phase, ENSURE you have fastboot connectivity by doing "fastboot devices" ! That tripped me because I had the correct drivers for ADB and fastboot, but fastbootd is another implementation after android 10. So you must have the correct drivers if you dont see your device listed under fastboot devices during fastbootd. you can grab them by googling, they come from XIaomi cn website and enabling it through Windows device manager if you use Windows. They are not signed, so you will have to bypass signature verification on bootup setting for Windows. Good luck let me know if you go through with installing it, I'd like to see how Havok performs!
Click to expand...
Click to collapse
Which android 10 rom my phone need to be in (cn or global or it does not matter?) before I can flash GSI rom. Thanks for the answer.
[email protected] said:
Which android 10 rom my phone need to be in (cn or global or it does not matter?) before I can flash GSI rom. Thanks for the answer.
Click to expand...
Click to collapse
It doesn't particularly matter because you'll be replacing the system.img and recovery.img. Ensure you dont have TWRP and you're using stock recovery. You just need an unlocked bootloader and the necessary tools. Let us know how it goes.
Bluetooth audio dont works!
xda-jimjongs said:
So I can speak to using Phh's GSI ROM as I tried out the v222 patch not too long ago. They do infact work, but they are missing a couple of features - Fingerprint does not work at all, 90Hz is not working (stuck at 60Hz) even with forcing it with ADB refresh rate command, VoLTE / Wifi Calling does not work, but the core functionality works at least. The problem I had with using the GSI, is that I bought a Xiaomi Mi 10 because it was in the premium segment of smartphones... missing all these key features with something as simple as a in-screen fingerprint or 90Hz placed it below the premium device I originally purchased. That's just my personal opinion of course, it depends how much you value your freedom over your device as the GSI/project treble images allow you to do that. There is an entry on the Phh's list for our device for what works and what doesnt. Can't link due to posting verification. Nothing has changed in terms of me testing the v222 patch.
To get to the point of fastboot if you are not experienced with debugging shell scripting, this will be incredibly tricky. Some issues are not apparent unless you see them. For example, the instructions listed on the Phh table is the following:
$ fastboot flash recovery stock-recovery.img (using official miui recovery)
$ fastboot reboot fastboot
$ fastboot flash system system-quack-arm64-ab-gapps.img
$ fastboot -w (wipe userdata)
$ fastboot reboot
I can tell you these have a LOT of caveats. For example, do you know how to enable USB debugging on your device and have the correct fastboot for your OS? If you don't, you need to know how to. Secondly, inorder to reference the "stock recovery img" file, you must point it to the directory of the image file.. if you dont know how to do any of that youre going to have a seriously tough time. Lastly, one other protip I can give you is that during the fastbootd phase, ENSURE you have fastboot connectivity by doing "fastboot devices" ! That tripped me because I had the correct drivers for ADB and fastboot, but fastbootd is another implementation after android 10. So you must have the correct drivers if you dont see your device listed under fastboot devices during fastbootd. you can grab them by googling, they come from XIaomi cn website and enabling it through Windows device manager if you use Windows. They are not signed, so you will have to bypass signature verification on bootup setting for Windows. Good luck let me know if you go through with installing it, I'd like to see how Havok performs!
Click to expand...
Click to collapse
When I try to flash something to the system partition it says that there is no system partition. All I can flash to is the super partition.
i using Phh's GSI ROM but I have a problem with the bluetooth headphones are detected but I can't hear anything
Kabanoska said:
i using Phh's GSI ROM but I have a problem with the bluetooth headphones are detected but I can't hear anything
Click to expand...
Click to collapse
Unfortunately known issue.. You can use a USB C cable but it requires an additional fix: enable "using alternate audio policy" in phh setting->qualcomm feauture Fix for Media sound-> Fixed by enable "disable audio effects" in phh setting -> misc features
Basecatcherz said:
When I try to flash something to the system partition it says that there is no system partition. All I can flash to is the super partition.
Click to expand...
Click to collapse
Ensure you are on fastbootd not regular fastboot! It will be a different logo, like yellow/orange on your phone instead of blue. That is probably causing the error, you can get there by doing the command fastboot reboot fastboot.
is there any other gsi system will run on mi 10?
Kabanoska said:
is there any other gsi system will run on mi 10?
Click to expand...
Click to collapse
Probably most of them as they're GSIs
xda-jimjongs said:
Unfortunately known issue.. You can use a USB C cable but it requires an additional fix: enable "using alternate audio policy" in phh setting->qualcomm feauture Fix for Media sound-> Fixed by enable "disable audio effects" in phh setting -> misc features
Ensure you are on fastbootd not regular fastboot! It will be a different logo, like yellow/orange on your phone instead of blue. That is probably causing the error, you can get there by doing the command fastboot reboot fastboot.
Click to expand...
Click to collapse
Fastbootd is the fastboot user space, right? I got it in LR Team TWRP but fastboot doesnt recognize it.
How to enter the right one?
Mackay53 said:
Probably most of them as they're GSIs
Click to expand...
Click to collapse
I tried more than 10 none on mi10 did not start
Related
Hey guys, Kyuubi10 here again.
Recently I had an issue with my nexus 9, which is becoming increasingly common.
Where one can permanently soft-brick their nexus, for lack of ticking the "Enable OEM unlock" button, then bootlooping their device while locking their bootloader, thus making it impossible to reflash a system image through fastboot.
If you're lucky enough to still be able to access your custom recovery your device is still salvageable, but if as me you were performing a factory reimage when you locked your bootloader chances are that you have gone back to stock recovery, and only after realised that your OS was bootlooping.
From reading about it, I found out that it was virtually unrecoverable, unless you managed to keep your custom recovery, by either flashing a new system or if your recovery refuses to flash new system you can use this: http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539.
But in all of these cases you still need a custom recovery.
At the end most people gave up and either bought another device or used their warranty to replace their device (Which I am trying to attempt, if my warranty isn't completely voided.)
So, finally reaching the important point of this thread, I have had a couple ideas which could work to solve this issue but since I don't have enough knowledge I am unable to actually test the idea.
For the device to recognize the lock status of the device even without an OS present means that there must be a flag the bootloader reads. By reading further I found this. http://newandroidbook.com/Articles/Nexus9.html
This basecally explains that Nexus 9 has a partition called PST (Persist) whose only job is to provide the value of this flag. I was wondering whether it is possible by using Linux could get a more direct access to the partition and change its binary value to enable the "enable OEM unlock" variable (Described by fastboot as "Ability is 0").
I had this idea because one day when I bootlooped another device and ADB on windows failed to recognize the device I booted linux and used ADB from there. And the phone was reconized.
This works because Linux can view partitions with different filesystems, where as windowns can only see partitions which have been formatted into "Windows" partitions (e.g. FAT32, NTFS).
So in theory using a Linux OS to access the different partitions in Android should show up much more information, and give you better access. But apart from this I don't know much more. I will be testing this theory out in more detail. But I am challenging the more experienced contributors out there to help out in overcoming this issue!
Please, this is a real issue which is limiting newer nexus devices. If anyone has any new ideas please share by commenting, and lets help each other out to find a solution to this problem.
..
cam30era said:
@Kyuubi10
Have you seen this thread > http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
Click to expand...
Click to collapse
Yes, in fact I have the same exact link in the OP.
But unfortunately as I have described my case is quite unique in which I don't have a custom recovery. This in turn means I have no access to ADB because no partitions are mounted.... I'm stuck with using fastboot for now.
Kyuubi10 said:
Yes, in fact I have the same exact link in the OP.
But unfortunately as I have described my case is quite unique in which I don't have a custom recovery. This in turn means I have no access to ADB because no partitions are mounted.... I'm stuck with using fastboot for now.
Click to expand...
Click to collapse
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
@Halleyscomet is very right, the N preview saved me from this problem, allowing me to enable OEM unlock and then go back to stock marshmallow.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
defmetal96 said:
@Halleyscomet is very right, the N preview saved me from this problem, allowing me to enable OEM unlock and then go back to stock marshmallow.
Click to expand...
Click to collapse
Thank you guys for your reply!!
Unfortunately as described in my signature my N9 was stolen.
But I'll change the title of this thread to [SOLVED] so that others know where to find an answer.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
angerized said:
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
Click to expand...
Click to collapse
For that a Moderator needs to be made aware ) Let's try do that!
angerized said:
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
Click to expand...
Click to collapse
Any chance you still have this file? Doesn't seem to exist on the internet anymore.Having same issue.
joeish said:
Any chance you still have this file? Doesn't seem to exist on the internet anymore.Having same issue.
Click to expand...
Click to collapse
Hello,
I don't have this specific file anymore, but I think you can sideload the latest OTA from here:
Images OTA complètes pour les appareils Nexus et Pixel | Google Play services | Google for Developers
developers.google.com
Requirements:
[ROOT REQUIRED]
[OEM Unlocking must be allowed under the developer options before flashing this file AND stay activated
as long as you want the device to stay unlocked (OnePlus implemented security features which locks the device on reboot with the switch off)]
* I am not responsible for bricked devices, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about this method before using it!
* YOU are choosing to make these modifications.
* And if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
WARNING: THESE FILES ARE BASED ON THE OXYGEN OS 2.1.1 FIRMWARE, PLEASE ANALYZE YOUR DEVINFO IF THE VERSION IS DIFFERENT TO MAKE SURE NOT BRICKING SOMETHING!
I have not upgraded my device to 2.1.2 yet because there have been some issues with the newest firmware.
Tested and confirmed working on:
OxygenOS 2.2.0 - thanks to @pryggi
OxygenOS 2.1.1
Hydrogen OS 1.2.0 - thanks to @fareed_xtreme
I looked at this thread, thanks to Naman Bhalla for this great work.
and found out that the file attached to this post is the answer to my problem, described in another thread.
After the whole day of work analyzing and dumping and saving via adb from my device to the pc and the other way around i finally did it.
On the frist screenshot is my situation before flashing the new devinfo, on the second after flashing the devinfo from the thread mentioned above.
By changing the bits with a Hex Editor of your choice, or by flashing the files below via dd:
Code:
dd bs=4096 of=/dev/block/bootdevice/by-name/devinfo if=/sdcard/oneplus2-devinfo-factory.img
The output should look like the following:
Code:
0+1 records in
0+1 records out
1024 bytes transferred in 0.005 secs (204800 bytes/sec)
You can restore your OnePlus 2 to a factory state while still having root or unlock your phone again without having to wipe it! :highfive:
Credits:
Naman Bhalla
Also to segv11 who already managed this in the OnePlus One and Nexus devices
wow nice job m8
sent from rooted phone
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.
Screenshot Attached. Good Find @thedropdead
Thank you and thanks for testing it out on Hydrogen OS @fareed_xtreme
It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device.
fareed_xtreme said:
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.
Screenshot Attached. Good Find @thedropdead
Click to expand...
Click to collapse
thedropdead said:
Thank you and thanks for testing it out on Hydrogen OS @fareed_xtreme
It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device.
Click to expand...
Click to collapse
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
fareed_xtreme said:
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
Click to expand...
Click to collapse
Thats another good thing to do with it
It was a pleasure to help you out mate
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?
Just to clarify, the dd command should be executed in TWRP console?
Would be cool if someone could make an app for this like the Nexus devices have:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
pryggi said:
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?
Just to clarify, the dd command should be executed in TWRP console?
Would be cool if someone could make an app for this like the Nexus devices have:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Click to expand...
Click to collapse
Hello pryggi,
It should also work on OOS 2.2.0, you could check that by dumping the partition (by reversing the dd command) like this:
Code:
dd bs=4096 if=/dev/block/bootdevice/by-name/devinfo of=/sdcard/oneplus2-devinfo-oos220.img
And looking at the file in the hex editor for differences or by posting it here and i can check it for you.
I have executed the dd command from ADB Shell with the Phone connected via wireless ADB.
You can also execute dd in the Android Terminal Emulator App.
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
pryggi said:
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
Click to expand...
Click to collapse
Thank you for the Dump, i can confirm that the bit is at the same position and the unlock bit is the same.
I compared the file attached at my first post with yours and they are identical ( see attachment, sorry its german, meaning is they are identical).
So by flashing the factory.img from my first post or unchecking OEM Unlock allowed in the developer Settings your device should be locked again and can be unlocked by flashing the unlock.img via dd in ADB or the Android Terminal Emulator within the Phone.
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...
I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
pryggi said:
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...
I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
Click to expand...
Click to collapse
As i can remember i tried that too, by flashing the factory image partition via dd and leaving the switch on, the switch gets toggled off when rebooting, because the switch is just the representation of the unlocking bit in the partition. So when it is turned off, the software will set the bit to zero, means the device will get locked on reboot. Turning the switch on will not override the bit and the device can boot unlocked and the switch will stay on.
It is hard to explain
Your Idea about doing the same thing in TWRP since the ADB is available there is interesting.
I think the problem here is, that once you onlock and flash a custom recovery via fastboot, and relock the device, you already tampered with it, and twrp does provide much more options than the stock recovery image (ADB commands, ...).
So the problem here lies in flashing twrp.
I solved this problem by keeping the stock recovery and locking the device via the image file.
Once i want to use twrp, i unlock the phone by using the unlock.img and use "fastboot boot twrp.img" to boot twrp to backup my device or some other action.
I know that this means if my device gets bricked in this locked state with stock recovery i will have to unlock it normally, but before making any important changes to my software i always unlock my device first in case something goes wrong and with the stock recovery i could not even flash anything so making huge software changes requires me to unlock my device and boot twrp
Hope that this post helps somehow
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal
fareed_xtreme said:
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal
Click to expand...
Click to collapse
That is right, i just included the notice in the first post so nobody can tell me i have not told them
It is also possible that OnePlus changes the layout of that partition in one of the upcoming updates/releases and that is why it is still mentioned in the first post, thank you anyway.
@thedropdead I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
casual_kikoo said:
@thedropdead I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
Click to expand...
Click to collapse
That should be the plan if i have understood everything right.
So you are on the custom ROM, want to go back to the stock ROM?
If that is the case i do not see why you should want to flash any image.
You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?
Please someone correct me if i am wrong.
It would be great if you could tell me what you are trying to achieve.
The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
thedropdead said:
That should be the plan if i have understood everything right.
So you are on the custom ROM, want to go back to the stock ROM?
If that is the case i do not see why you should want to flash any image.
You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?
Please someone correct me if i am wrong.
It would be great if you could tell me what you are trying to achieve.
The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
Click to expand...
Click to collapse
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case .
casual_kikoo said:
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case .
Click to expand...
Click to collapse
Okay thanks for the clarification.
In the Case of using some unbrick Tool and thus resetting everything including recovery to stock your phone should lock on the first stock boot.
Once it is locked and you do not have root, which would be the case, you have no possibility to flash the img via fastboot or the emulator.
so in conclusion you are better off with wiping and flashing via twrp so you can still flash something if anything goes wrong
It works on OxygenOS 3.0.2 too. I edit the same location using a HEX Editor. And everything is fine.
Hey guys, sounds like this is exactly what I've been looking for. Thanks for figuring this out.
But, I'm a bit of a noob, so can you break it down into like a hundred very clear steps?
So now that the K20 Pro subforum is open, I'd like to make a post here to quickly sum up what we have right now before any device-specific AOSP development has started.
LR.Team/wzsx150's TWRP
Original thread: http://www.miui.com/thread-24561276-1-1.html
Mirrored here: https://drive.google.com/open?id=1miIo5BZqgEHh0t5PyjwFkFryosLuFOXk
Usage: unlock BL, flash recovery image to recovery and misc.bin to misc via fastboot
Status on GSIs
PHH wiki page: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Redmi-K20-Pro
TL;DR: the biggest issue is the pop-up camera, but that has been partially resolved by PHH (manual controls); other bugs are either generic to GSIs or not deal-breakers. I myself have been using my own LOS GSI for a week by now and I'd say it's good for daily driver, and certainly good enough as an intermediate stop before actual ROMs happen. Once the overlay I submitted is merged, all GSIs built afterwards should be on equal footing. I'll also keep eyes on the issues page in case PHH needs anything for another fix.
And finally, here's a script I made for users who want to use unencrypted storage - format /data and flash this. This one was actually made for Mix 2, but also works here, while Zackptg's universal script doesn't seem to work.
AndyYan said:
So now that the K20 Pro subforum is open, I'd like to make a post here to quickly sum up what we have right now before any device-specific AOSP development has started.
LR.Team/wzsx150's TWRP
Original thread: http://www.miui.com/thread-24561276-1-1.html
Mirrored here: https://drive.google.com/open?id=1miIo5BZqgEHh0t5PyjwFkFryosLuFOXk
Usage: unlock BL, flash recovery image to recovery and misc.bin to misc via fastboot
Status on GSIs
PHH wiki page: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Redmi-K20-Pro
TL;DR: the biggest issue is the pop-up camera, but that has been partially resolved by PHH (manual controls); other bugs are either generic to GSIs or not deal-breakers. I myself have been using my own LOS GSI for a week by now and I'd say it's good for daily driver, and certainly good enough as an intermediate stop before actual ROMs happen. Once the overlay I submitted is merged, all GSIs built afterwards should be on equal footing. I'll also keep eyes on the issues page in case PHH needs anything for another fix.
And finally, here's a script I made for users who want to use unencrypted storage - format /data and flash this. This one was actually made for Mix 2, but also works here, while Zackptg's universal script doesn't seem to work.
Click to expand...
Click to collapse
OMG! Thank you so much in advance! ???
---------- Post added at 06:47 PM ---------- Previous post was at 06:08 PM ----------
I'd love to see a more detailed "noob friendly" guide on how I can get this twrp working on my K20 Pro. Hope one will be available in YouTube soon.
melmarPH said:
I'd love to see a more detailed "noob friendly" guide on how I can get this twrp working on my K20 Pro. Hope one will be available in YouTube soon.
Click to expand...
Click to collapse
Uhh... What difficulty do you have with simply flashing TWRP? I believe that doesn't need a guide.
Thanks for your work with PHH on getting a usable GSI image. Do you have a PD charger? I was wondering if you still get 27W charging via PD?
I'll be ordering this in the next day or 2, now the prices have come down to a sensible level on AliExpress. Hopefully by the time it arrives and I get to unlock the bootloader a few more issues will have been resolved thanks to the now released kernel sources.
Thanks a lot bro!!!!!
how do you flash the misc using fastboot? and is this english language?
narugan26 said:
how do you flash the misc using fastboot? and is this english language?
Click to expand...
Click to collapse
fastboot flash misc misc.bin
Chinese default, and you can change to English in setting via same step as other official TWRPs.
AndyYan said:
Uhh... What difficulty do you have with simply flashing TWRP? I believe that doesn't need a guide.
Click to expand...
Click to collapse
Please correct me if im wrong..
1. Unlock bootloader
2. Fastboot flash recovery twrp.img
3. Fastboot flash misc misc.bin
Is that correct?
Robbo.5000 said:
Thanks for your work with PHH on getting a usable GSI image. Do you have a PD charger? I was wondering if you still get 27W charging via PD?
Click to expand...
Click to collapse
I didn't buy the optional 27W charger; stock 18W charger charges the phone at 9V 1.85A (~17W) as measured by a physical USB meter (I don't trust any software readings).
melmarPH said:
Please correct me if im wrong..
1. Unlock bootloader
2. Fastboot flash recovery twrp.img
3. Fastboot flash misc misc.bin
Is that correct?
Click to expand...
Click to collapse
Looks good to me.
Nice to see you here @AndyYan ! Loved your consistent work on the mix2! You bought the k20pro as well?
ugene1980 said:
Nice to see you here @AndyYan ! Loved your consistent work on the mix2! You bought the k20pro as well?
Click to expand...
Click to collapse
Yeah it's my new primary device. I don't plan to do any building/"development" here though, this device should be popular enough to attract more capable devs on its own - that is, after it's released internationally.
May I ask what is the purpose of tha misc.bin?
AndyYan said:
Yeah it's my new primary device. I don't plan to do any building/"development" here though, this device should be popular enough to attract more capable devs on its own - that is, after it's released internationally.
Click to expand...
Click to collapse
Hi Andy, quick question.
Do you think the non-pro version of the phone will receive the same level of custom ROM support as the pro version? If I am not mistaking, the only difference that affects developers is the SD730 instead of the SD855. The reason I am asking is because I dislike MIUI, but (currently) only the Xiaomi Mi 9T is available where I live. I do not mind buying the non-pro version, but I do want much custom ROM support. Do you suggest waiting for the Xiaomi Mi 9T Pro or importing the Redmi K20 Pro over buying the Xiaomi Mi 9T (w.r.t. custom ROM support)?
Krullendhaar said:
Hi Andy, quick question.
Do you think the non-pro version of the phone will receive the same level of custom ROM support as the pro version? If I am not mistaking, the only difference that affects developers is the SD730 instead of the SD855. The reason I am asking is because I dislike MIUI, but (currently) only the Xiaomi Mi 9T is available where I live. I do not mind buying the non-pro version, but I do want much custom ROM support. Do you suggest waiting for the Xiaomi Mi 9T Pro or importing the Redmi K20 Pro over buying the Xiaomi Mi 9T (w.r.t. custom ROM support)?
Click to expand...
Click to collapse
Past "parallel" sub-flagships like Mi 8 SE / Mi 9 SE aren't even close to their flagship counterparts in terms of support, plus SD730 is a chip only used by 2 devices so far. Wouldn't count on it.
Still, given the two's similarity, it should be a cakewalk to get GSI running on it with the same bugs, and if something gets fixed on one, the other should benefit as well.
dmj0shu4 said:
May I ask what is the purpose of tha misc.bin?
Click to expand...
Click to collapse
idk either, but all releases for all devices from wzsx150 include this step, so I figure can't go wrong with just copying his steps.
dmj0shu4 said:
May I ask what is the purpose of tha misc.bin?
Click to expand...
Click to collapse
AndyYan said:
idk either, but all releases for all devices from wzsx150 include this step, so I figure can't go wrong with just copying his steps.
Click to expand...
Click to collapse
Configures in misc partition decides the bootloader to boot from system or recovery.
In wzsx150's flash.bat (recovery-twrp一键刷入工具.bat) , he writes 'fastboot.exe reboot' command in the end. So if we don't change settings in misc partition, the bootloader will control your phone to boot to MIUI system and recover the TWRP to xiaomi official recovery.
Other way, we can use 'fastboot boot twrp.img' command in the end, instead of flashing that misc.bin. Maybe we can use 'fastboot reboot recovery' command (I have not tested).
In summary, that misc.bin prevent phone from booting into MIUI.
If there are any mistakes, please point out.
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
AndyYan's GSI works well with few bugs.
The only 2 unsatisfactory things I have discovered are:
This GSI LineageOS don't support to unlock phone via fingerprint when screen is off, I have to press the power button first.
And this GSI only have PWM driver when screen is 31% brightness below, while the MIUI supports all brightness DC ( however, xiaomi claimed that K20Pro have HARDWARE DC screen driver ). I have tried 3rd party apk for simulate DC driver, it works, but completely ruines the optical fingerprint at low brightness due to the screen is so dim that can't lit up the finger for fingerprint camera.
Fortunately, Magisk, Edxposed, GravityBox[P] and other xposed modules work, so I will never return to MIUI.
kumoilain said:
Configures in misc partition decides the bootloader to boot from system or recovery.
In wzsx150's flash.bat (recovery-twrp一键刷入工具.bat) , he writes 'fastboot.exe reboot' command in the end. So if we don't change settings in misc partition, the bootloader will control your phone to boot to MIUI system and recover the TWRP to xiaomi official recovery.
Other way, we can use 'fastboot boot twrp.img' command in the end, instead of flashing that misc.bin. Maybe we can use 'fastboot reboot recovery' command (I have not tested).
In summary, that misc.bin prevent phone from booting into MIUI.
Click to expand...
Click to collapse
So that's why... Thanks for the explanation!
I always hold down the key combo right after flashing though, so it wouldn't boot into MIUI anyway, but good to know I don't need to do that anymore at least for this device.
kumoilain said:
Configures in misc partition decides the bootloader to boot from system or recovery.
In wzsx150's flash.bat (recovery-twrp一键刷入工具.bat) , he writes 'fastboot.exe reboot' command in the end. So if we don't change settings in misc partition, the bootloader will control your phone to boot to MIUI system and recover the TWRP to xiaomi official recovery.
Other way, we can use 'fastboot boot twrp.img' command in the end, instead of flashing that misc.bin. Maybe we can use 'fastboot reboot recovery' command (I have not tested).
In summary, that misc.bin prevent phone from booting into MIUI.
If there are any mistakes, please point out.
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
AndyYan's GSI works well with few bugs.
The only 2 unsatisfactory things I have discovered are:
This GSI LineageOS don't support to unlock phone via fingerprint when screen is off, I have to press the power button first.
And this GSI only have PWM driver when screen is 31% brightness below, while the MIUI supports all brightness DC ( however, xiaomi claimed that K20Pro have HARDWARE DC screen driver ). I have tried 3rd party apk for simulate DC driver, it works, but completely ruines the optical fingerprint at low brightness due to the screen is so dim that can't lit up the finger for fingerprint camera.
Fortunately, Magisk, Edxposed, GravityBox[P] and other xposed modules work, so I will never return to MIUI.
Click to expand...
Click to collapse
Thank you for your clarification. So for now, there is no way to not flashing misc.bin? Because i do not want to touch this partition whatsoever.
xuananh94 said:
Thank you for your clarification. So for now, there is no way to not flashing misc.bin? Because i do not want to touch this partition whatsoever.
Click to expand...
Click to collapse
kumoilain said:
Other way, we can use 'fastboot boot twrp.img' command in the end, instead of flashing that misc.bin. Maybe we can use 'fastboot reboot recovery' command (I have not tested).
Click to expand...
Click to collapse
You can use the first commad above after "fastboot flash recovery twrp.img". It should work.
I think it's ok to overwrite misc partition because configures in misc is always changed (eg. reboot to system from twrp/ reboot to twrp from system)
kumoilain said:
You can use the first commad above after "fastboot flash recovery twrp.img". It should work.
I think it's ok to overwrite misc partition because configures in misc is always changed (eg. reboot to system from twrp/ reboot to twrp from system)
Click to expand...
Click to collapse
So let me clear what I need to do, please tell me if i am wrong:
- extract the .7z file
- take the .img file (64mb) and flash it via adb normally.
- boot to recovery and install whatever i like
I have been through hell and high water today with this Nord N200 5G today. Soft Brick after Soft Brick. iI only flashed TWRP and try to boot into OS after exiting TWRP but i get No OS you sure you want to reboot?. I also can't figure out how to get my internal storage viewed in TWRP. I've read multiple guides and still can't figure it out. I"m pretty new to this so . and they try to flash Magisk for root as well as super su during on adventure fiasco after fiasco today. The Bootloader and OEM unlock was simple straight forward. Most Guides though are not in LAMENS terms and have abbreviations that new people do not understand. i have had to reflash my phone 20+ today with factory due to the NO OS problem with TWRP and can't get it so i can view my internal data from twrp even though i've followed several guides and the ones that says to do the wipe thing i always get the error about it can't mount the data or it has encountered and error 255 and by got try looking things up for those and you you get sent all over the place. So If there is Anyone Out There That would like to help an old geezer out to be able to get a stable TWRP and a Stable root going on please Respond. Sorry Had to Vent......
Oh yea and not to mention Unable to install 3.6.2
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
weirdfate said:
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
Click to expand...
Click to collapse
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
jova33 said:
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
Click to expand...
Click to collapse
Obviously not who you were asking but I just updated to Lineage and it was fairly straightforward following the directions, just make sure you're on Android 11. Updates can be done through settings menu, I just actually applied an update and it worked fine. It can check for updates every day, week, month if you choose I don't know if it will automatically update it though. Camera I have not tried as I don't use it as an everyday phone but generally from what I've seen it's common to have quality go down using software other than stock but I could be wrong.
I can't speak on the difference in camera quality because I dont use it much. There is some loss of function between the stock camera app and the aftermarket rom camera app
This phone has no official twrp so it has tons of decrypting issues which explains almost all of your problems.
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
swee08315 said:
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Click to expand...
Click to collapse
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
MiniNinja2024 said:
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
swee08315 said:
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
Click to expand...
Click to collapse
how do i get the phone completely unbricked cause it's saying something like The Image[boot,recovery] has been destroyed please flash correct image or contact customer service to fix it
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Will be trying again in a week when i get my new unlock token. just took the phone to the store, said that the bricking of the phone happend during an update. They didn't have any Nord N200's in stock so they ordered one and said they would have it in the store in a day or two. onto the next phone til then. any ideas on a TCL A509DL Trac Phone?
MiniNinja2024 said:
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Click to expand...
Click to collapse
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
MiniNinja2024 said:
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
Click to expand...
Click to collapse
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
i don't have another machine only the one i'm using running MX linux. and with all the Distro's of linux i have installed and used there is no need to install drivers for phones for every phone, 3 that i have connected to my computer it' has recognized all 3 phones and runs adb and fastboot commands fine on them. Lol, Took me a minute to read your name but Love the Name.
Haha, don't flash it. Boot it. I ended up stop using it and am now using the Lineage OS Recovery. SUPER stable. I am in the works making a new TWRP as well... This unofficial variant just isn't working for me either. So, I figured since im making it doe myself, might as well release it
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
You can. Use virtualbox. I wouldn't bother with qemu.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
There is a command line alternative for Linux. It is originally made for flashing android boards, but works with phones as well.
Springles2 said:
You can. Use virtualbox. I wouldn't bother with qemu.
Click to expand...
Click to collapse
Interesting, that's actually useful to know. Thanks.
MiniNinja2024 said:
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I do adb push (File) partition
I have my bootloader unlocked.
I've downloaded the AOSP 13 Borneo Monthly Build.
I used
Code:
fastboot -w update .\aosp_borneo-img-Feb-Week4.zip
to install it. I don't have GApps now (as expected).
I've tried NUMEROUS things, but I always end up back to having to reinstall AOSP 13. And all the posts are almost 1-2 years old so outdated information. I tried to use the TWRP Android 11 based, but I of course got an error of "Cannot mount /data" despite no matter what I've done.
Is there any way to get GApps on the ASOP 13 build? I don't care about a custom rom and my phone has been wiped numerous times multiple different ways over the last our, so losing data (not that I did) isn't a problem.
EDIT: I don't mind if it's A11 or A12, A13 would be nice if possible. But I'd just like ASOP with GApps. Though I couldn't even find where the ASOP A11 and A12 builds for this phone would be (if there is any).
Try flashing BitGapps through TWRP and see if it works
traman124 said:
Try flashing BitGapps through TWRP and see if it works
Click to expand...
Click to collapse
I actually just install AOSP 13 and then flashed the Pixel Experience system image.
I've been doing this for like 8 hours of trial and error. I think what was confusing me most of the time was I didn't realize that you use fastboot in Bootloader and in fastboot. But you can only run certain fastboot commands in bootloader and only some in Fastboot mode. Which took me quite a bit to realize. Which means I would run a fastboot command in something like bootloader and it was meant for fastboot mode so it'd give me random errors that no one else got because they apparently knew the difference.
But that was confusing lol
EDIT: WELL ****E, NOW THE KEYBOARD DOESN'T WORK.
You didn't say that you wanted a PE GSI in the original post.
Also that was confusing for me the first time too (and moreso with the TCL Revvl 4)
traman124 said:
You didn't say that you wanted a PE GSI in the original post.
Also that was confusing for me the first time too (and moreso with the TCL Revvl 4)
Click to expand...
Click to collapse
Well I attempted PE GSI because there's no TWRP for AOSP 13 for this phone, the latest is A11 and that won't mount /data/
As well as the TWRP you listed doesn't work with my touchscreen and the other one avail doesn't do decryption.
There’s an SHRP build with decryption support for your phone… Would that work?
traman124 said:
There’s an SHRP build with decryption support for your phone… Would that work?
Click to expand...
Click to collapse
I've tried that myself, and decryption doesn't seem to be any better than twrp. That and it doesnt read AOSP 13 /data anyway. I've had the same problem trying to get gapps, even MagiskGapps doesn't seem to work. Is there a gapps package that can be flashed via fastboot maybe?
Not as far as I know... I’m sorry I can‘t help much further
ErraticFox said:
I actually just install AOSP 13 and then flashed the Pixel Experience system image.
I've been doing this for like 8 hours of trial and error. I think what was confusing me most of the time was I didn't realize that you use fastboot in Bootloader and in fastboot. But you can only run certain fastboot commands in bootloader and only some in Fastboot mode. Which took me quite a bit to realize. Which means I would run a fastboot command in something like bootloader and it was meant for fastboot mode so it'd give me random errors that no one else got because they apparently knew the difference.
But that was confusing lol
EDIT: WELL ****E, NOW THE KEYBOARD DOESN'T WORK.
Click to expand...
Click to collapse
Mind if I ask what you mean by "pixel experience system image"? Are you talking about the PE GSI?
Yes he means the GSI.
So. This works and you end with aosp 13 and gapps? For those of us with zero adb experience, is there a step by step on how to do this?
graewulf1 said:
So. This works and you end with aosp 13 and gapps? For those of us with zero adb experience, is there a step by step on how to do this?
Click to expand...
Click to collapse
I'm not sure how to get gapps, but you can flash aosp with fastboot update aosp.zip (replace aosp with the aosp file name). Just power off your phone, then power on while holding the volume down key to boot into the bootloader and perform this command.
LethalGamer2121 said:
I'm not sure how to get gapps, but you can flash aosp with fastboot update aosp.zip (replace aosp with the aosp file name). Just power off your phone, then power on while holding the volume down key to boot into the bootloader and perform this command.
Click to expand...
Click to collapse
right, i get that. i need to load gapps as well, i have too many paid apps there to not use it. since there is no TWRP for android 13, I need to figure out how to flash AOSP, then Gapps before the first boot.
graewulf1 said:
right, i get that. i need to load gapps as well, i have too many paid apps there to not use it. since there is no TWRP for android 13, I need to figure out how to flash AOSP, then Gapps before the first boot.
Click to expand...
Click to collapse
Well, let me know if you figure it out, cause i'm just as clueless about it as you are. I'm kind of suprised nobody's made a fastboot flashable gapps package yet.