Database Users

6055U Root method found

Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu

F
dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
Did a Google search for "sugar qct" and I see a couple of million hits for "The Sugar Act"... :laugh:
Tried Root Genius, and it, of course doesn't work...
If you happen to find a link for the app or method you stated, I would be eternally grateful... My lovely wife and I upgraded our phones to the Cricket 6055U, and, since, while not an Android developer, per se, can find my way around the device without being scared off...
So, with due respect, I'd ask if you have the app or name correct?
Thanks, friend, and best respect.
--- edit ---
Oops... was premature... found it and am giving it a try... I'll post my results after I give it a shot...

http://forum.gsmhosting.com/vbb/f606/vf-895n-smart-prime-6-stock-rom-flash-tool-2033867/
This should help with setting up sugar. The only difference here is to update it and you also need a username and password that I don't have on me at the moment. It will be a few hours until I get home but I will update asap.
Edit: nevermind lol, good luck friend. You may need a decent battery percentage as well

pauljulian said:
F
Did a Google search for "sugar qct" and I see a couple of million hits for "The Sugar Act"... :laugh:
Tried Root Genius, and it, of course doesn't work...
If you happen to find a link for the app or method you stated, I would be eternally grateful... My lovely wife and I upgraded our phones to the Cricket 6055U, and, since, while not an Android developer, per se, can find my way around the device without being scared off...
So, with due respect, I'd ask if you have the app or name correct?
Thanks, friend, and best respect.
--- edit ---
Oops... was premature... found it and am giving it a try... I'll post my results after I give it a shot...
Click to expand...
Click to collapse
----- edit 2 -----
OK... apparently I'm an idiot... Running Windows 10 Pro, and the installer says it's going to install to an appropriate folder on C:\... yet, trying to find it, it really is weird.... I'm going to try on a VMWare Win 7 virtual PC, and see if I'm able to find it there, and move it to my actual C: drive...
If it works, I'll be grateful for your contribution and praise you to the highest heaven! :laugh:

pauljulian said:
----- edit 2 -----
OK... apparently I'm an idiot... Running Windows 10 Pro, and the installer says it's going to install to an appropriate folder on C:\... yet, trying to find it, it really is weird.... I'm going to try on a VMWare Win 7 virtual PC, and see if I'm able to find it there, and move it to my actual C: drive...
If it works, I'll be grateful for your contribution and praise you to the highest heaven! :laugh:
Click to expand...
Click to collapse
Can't seem to get the beast to work...
If you would be so kind, would there be any way you'd be able to write up a concise step-by-step thing, if you've made it work... I've got the .chm file open on my desktop, and have spent a few hours trying to make it work to no avail.
Again, if it worked for you, your process would be welcome.
Cricket Alcatel Idol 4, 6055U
---------- Post added at 03:36 PM ---------- Previous post was at 02:40 PM ----------
pauljulian said:
Can't seem to get the beast to work...
If you would be so kind, would there be any way you'd be able to write up a concise step-by-step thing, if you've made it work... I've got the .chm file open on my desktop, and have spent a few hours trying to make it work to no avail.
Again, if it worked for you, your process would be welcome.
Cricket Alcatel Idol 4, 6055U
Click to expand...
Click to collapse
My point is that the site recommended seems to insist on Lollipop on the small beast... and there doesn't seem to be a recommendation for the .bin files, and, when installing on Win 10, it seems to install the Sugar app into some directory on my C: drive that is really not that accessible... Did it using a VMWare Win 7 32-bit virtual, and was able to access the directory, copy and paste to my regular C: drive (old Windows geek since Win 3.11... and DOS 3), and it seemed to run... (of course, running as Administrator), but it really doesn't seem to work for me... Again, I freely admit that I'm likely not doing something right, but even after some research and the included .chm file, I seem to be missing something.
Again, and begging your indulgence for seeming like a noob or a rube, but if I'm not making it happen, I rather think that the tips would be lost on someone for whom this is their first Android device...
Kinda frustrating, as, even though I've been a tech-support guy and database developer for more than 30 years, this thing has me stymied...
I found it fascinating for the *#*# command, earlier, from another noble soul, and, obviously, I also found that the device as configured says, basically... "Don't give a damn... you can turn this sucker on, but as soon as you exit this menu, I'm gonna turn it off again."
Just a little frustrating, and it seems that most of the tips and tricks elsewhere seem to be thinking that new owners of the 6055U are running Lollipop.... aaarrrgggghhh....
If it needs Lollipop to work, and if there's a relatively painless way to downgrade, and then upgrade from a ROM, I'm good with that... the Idol 3 seemed to require that, and it worked well for me, with just an evening's work. This one? Cricket seems to have had a warped sense of humor about it... I seriously dig the device, and, since my Idol 3 broke, and my lovely wife's LG G-Stylo (which was a pain in the ass, and next-to-impossible to root, and then be just perpetually stuck at the logo screen with an unfixable boot loop, if one screwed it up, and just required sending the beast back to LG, as long as one took out Cricket's warranty plan... <sigh>), we took the plunge on this one...
Not much for which I require root, but, since I spent good money on some legit apps (and lucked into a few ... ahem... not legit apps that worked for me), these things require root... I know there's a way to do it, and the Sugar app seems promising, but, mildly autistic guy that I am (and 60 years old, with a memory that doesn't work as it used to), a slimmed-down step-by-step doc would be helpful... should some noble soul put such together...
Apparently, the root method has worked for at least one member here.... But this weird old Jewish hippie doesn't see the mental diagram....
Any help would be welcome, my friends and mishpocheh... ("dear family" --- been here enough years, albeit a relatively quiet member, that y'all might as well be family... )

Hey everyone, sorry about the confusion. I installed on Windows 10 pro with no issues. As far as the page I linked you can disregard everything but the app itself. The update that downloads is marshmallow, and I've had no issues overwriting the latest version. I may have gotten sugar from a different location though, as soon as I get a chance I will do a better write up with everything. A helpful way to find the install directory would be right click on the shortcut from the start menu and click find Target / open file location. If it brings you to the folder with the shortcuts do it again and you will have the install directory. The app should be in (install dir)/tool and the downloaded updates go in (install dir)/bin under a folder that only shows up once you start the process within sugar. I will try to compile the information into a more user friendly format tonight but I can't make any promises on that.

Also just to clarify, I didn't use any chm file

I'm wondering if you could upload your version you have on your pc. I just spent the last month in jail here in Orlando fighting a case and the only proof I've got is on my phone on a phone that I deleted my videos on. I really need the videos back too get a not guilty if I gotta pay for it it's cool but I'm out on bond and all the recover videos apps require root

I got this to work last night. Typed up some instructions but didn't get them posted. They're on my PC at home and I'm at work.
Basically use the copy of sugar in the download package in this thread and then start it and let it update https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560
Those are the basic instructions too except we don't need to swap out bout and use the TWRP from deckersu thread.
Once flashed it'll automatically reboot. I found you had to make sure you caught this and booted into TWRP right away don't let the phone boot. Then transfer SuperSU in TWRP and flash.
---------- Post added at 11:29 AM ---------- Previous post was at 11:23 AM ----------
Asadullah said:
I'm wondering if you could upload your version you have on your pc. I just spent the last month in jail here in Orlando fighting a case and the only proof I've got is on my phone on a phone that I deleted my videos on. I really need the videos back too get a not guilty if I gotta pay for it it's cool but I'm out on bond an ind all the recover videos apps require root
Click to expand...
Click to collapse
FYI this root method wipes your phone so I don't know if this will help your situation or not.

In sugar there is an option to not wipe, it's under session settings or something to that effect

dbgr said:
In sugar there is an option to not wipe, it's under session settings or something to that effect
Click to expand...
Click to collapse
Wish I had noticed that!! Oh well, stoked to have root and it's good to start fresh. Got Xposed installed today and finally got that annoying charging light turned off. Working on getting wifi tetherng working. Then if I can figure out how to get the dialer to be friends with Google voice this phone will have all its annoyance fixed
Thanks so much for figuring this out and sharing!!

dbgr said:
In sugar there is an option to not wipe, it's under session settings or something to that effect
Click to expand...
Click to collapse
Appreciate the help

woodi5359 said:
https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560.
Click to expand...
Click to collapse
Thank you for finding this thread, it is the same one I found but I couldn't remember where it was the other day when I started this thread. Hopefully this will help the people who have been having issues, although I will admit a more painless method would be preferable. I'm currently working on modifying a dirtycow exploit to simply flash the recovery and reboot into twrp, if I get it to work I will zip it all up and post it here.

woodi5359 said:
Wish I had noticed that!! Oh well, stoked to have root and it's good to start fresh. Got Xposed installed today and finally got that annoying charging light turned off. Working on getting wifi tetherng working. Then if I can figure out how to get the dialer to be friends with Google voice this phone will have all its annoyance fixed
Thanks so much for figuring this out and sharing!!
Click to expand...
Click to collapse
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer

Asadullah said:
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer
Click to expand...
Click to collapse
I just tested this and it indeed does work. Great find friend!

Asadullah said:
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer
Click to expand...
Click to collapse
Thanks for figuring this out!!! I'd been messing with it for a few days. The renaming the apk to .oat was the piece I was missing. That and a reboot got it working!!

dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
so im getting ready to purchase this device so there is root and twrp for it or no

Dude, did you read the thread at all? I don't mind helping but you gotta do your part. Yes there is TWRP and Root

dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
do you hold volume down when it reboots

link22534 said:
do you hold volume down when it reboots
Click to expand...
Click to collapse
It's volume up and power

[GUIDE][OSPREY] Pass SafetyNet on Custom Roms

Hey guys,
After seeing this Magisk module https://github.com/DeicPro/xiaomi-safetynet-fix
I began to experiment to make SafetyNet pass on Osprey.
And finally I was able to do just that.
DO REMEMBER THAT THIS REQUIRES MAGISK WITH MAGISK HIDE ENABLED. THIS WILL NOT WORK WITH SUPERSU.
IF YOU ALREADY HAD SuperSU, CLEAN FLASH THE ROM AND THEN FLASH MAGISK ZIP.
Steps-
NOTE: SINCE GOOGLE HAS UPDATED SAFETYNET, THE BELOW METHOD NOW REQUIRES MAGISK v14.0+-
Open the build.prop file located in /system. [REQUIRES ROOT]
Add this line to the build.prop file-
For XT1550(Retail Asia | India (2GB))-
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
For XT1543(Retail Latin America (1GB)) -
ro.build.fingerprint=motorola/osprey_retla_ds/osprey_uds:6.0.1/MPI24.107-55-2/2:user/release-keys
For XT1540(Retail US (2GB)) -
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
For XT1540(Retail US (1GB))-
ro.build.fingerprint=motorola/osprey_retus/osprey_umts:6.0/MPI24.65-25.1/1:user/release-keys
Save and Exit.
Make sure you have enabled Magisk Hide in Magisk setings.
Reboot.
NEW! Magisk module is available here.
~Please read the Note section below~
---------------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE-
1. The fingerprint values need to be exactly the same. Any small change will trigger safetynet.
2. You can use any fingerprint value for your device. It's not necessary for you to take value specific to your device. As long as the fingerprint is valid, it will work.
3. This same trick should also work on Merlin devices.
4. Read this too please.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Thanks to -
@Rohi09 for providing stock ROM XT1550 build.prop
@Deic for his magisk module which inspired me to do this.
@KrisM22 for providing XT1540(2 GB) values.
@xMotoDA for providing XT1543 values.
@lettucecube for providing XT1540(1 GB) values and creating the Magisk module.

This method is working fine on purenexus rom

This is only for Asian Ospreys with 2GB of RAM, right?

Absolute killer! Thanks man.
Unfortunately, I still can't use digibank. Don't know what sort of check they perform.
xMotoDA said:
This is only for Asian Ospreys with 2GB of RAM, right?
Click to expand...
Click to collapse
Does that really matter?

Changing these specific values to the ones in the stock ROM makes SafetyNet pass! Since mine is dual sim and a different model I changed this in build.prop:
Code:
ro.product.name=osprey_retla_ds
ro.product.device=osprey_uds
ro.build.product=osprey_uds
ro.build.fingerprint=motorola/osprey_retla_ds/osprey_uds:6.0.1/MPI24.107-55-2/2:user/release-keys

bin.sayantan said:
Absolute killer! Thanks man.
Unfortunately, I still can't use digibank. Don't know what sort of check they perform.
Click to expand...
Click to collapse
Try to enable Magisk Hide for that specific app. Its there in the settings.

coolguy_16 said:
Try to enable Magisk Hide for that specific app. Its there in the settings.
Click to expand...
Click to collapse
Nothing happened. I even went a step further by totally uninstalling Magisk. Yet no luck.

bin.sayantan said:
Absolute killer! Thanks man.
Unfortunately, I still can't use digibank. Don't know what sort of check they perform.
Does that really matter?
Click to expand...
Click to collapse
I cant also log in my digi bank acount...i hav got a fixed deposit there....what is creating problem?any help
---------- Post added at 12:57 PM ---------- Previous post was at 12:35 PM ----------
Grt work....
I didnt found two lines in my build prop..so i add those...and safety net passed...
Thanx mate:good:

Can someone help me with this build.prop. Its from aex 4.2

Susan Dahal said:
Can someone help me with this build.prop. Its from aex 4.2
Click to expand...
Click to collapse
On AEX, you can simply add this line
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
anywhere in the build.prop.
Make sure the above value is exactly the same.

coolguy_16 said:
On AEX, you can simply add this line
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
anywhere in the build.prop.
Make sure the above value is exactly the same.
Click to expand...
Click to collapse
It worked Thanks

If you are willing could you look at mine - this is from a Moto G3 2015 XT1540 2GB US ATT
Thanks!
My stock is XT1540_OSPREY_RETUS_2GB_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml.zip
So I tried
ro.build.fingerprint=motorola/OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
also tried
ro.build.fingerprint=motorola/XT1540_OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.

KrisM22 said:
If you are willing could you look at mine - this is from a Moto G3 2015 XT1540 2GB US ATT
Thanks!
My stock is XT1540_OSPREY_RETUS_2GB_6.0_MPI24.65-25.1_cid9_subsidy-DEFAULT_CFC.xml.zip
So I tried
ro.build.fingerprint=motorola/OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
also tried
ro.build.fingerprint=motorola/XT1540_OSPREY_RETUS_2GB/osprey_ud2:6.0/MPI24.65-25.1/14:user/release-keys
but no go.
Click to expand...
Click to collapse
The problem here is that the value "ro.build.fingerprint" has to be the exact same as Motorola made it. Meaning even a small change(even CAPS) will trigger safetynet.
Anyways, I searched XDA for your device build.prop and found what you can replace that value with-
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
You can use the fingerprint value of my device too(the one mentioned in post). It will work without any issues.
I myself tried the fingerprint value of another model(that too a 1GB model) and it still worked.
Edit: I even tried the build.prop of your device on mine and that worked too.
Edit2: It seems like Step 2 in my OP is actually not necessary. Only fingerprint value is needed.

coolguy_16 said:
The problem here is that the value "ro.build.fingerprint" has to be the exact same as Motorola made it. Meaning even a small change(even CAPS) will trigger safetynet.
Anyways, I searched XDA for your device build.prop and found what you can replace that value with-
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
You can use the fingerprint value of my device too(the one mentioned in post). It will work without any issues.
I myself tried the fingerprint value of another model(that too a 1GB model) and it still worked.
Edit: I even tried the build.prop of your device on mine and that worked too.
Edit2: It seems like Step 2 in my OP is actually not necessary. Only fingerprint value is needed.
Click to expand...
Click to collapse
Huge thanks for your time. I realized I had not installed magisk so I installed that but I have supersu 2.79 installed so maybe need to uninstall that and install the special one for LinOS?

KrisM22 said:
Huge thanks for your time. I realized I had not installed magisk so I installed that but I have supersu 2.79 installed so maybe need to uninstall that and install the special one for LinOS?
Click to expand...
Click to collapse
I'm pretty sure it won't work with SuperSU.
Yep, remove SuperSu and also Magisk.
Then flash magisk zip again.This time it will install MagiskSU too(Magisk avoids MagiskSU if existing root solution is detected)

coolguy_16 said:
I'm pretty sure it won't work with SuperSU.
Yep, remove SuperSu and also Magisk.
Then flash magisk zip again.This time it will install MagiskSU too(Magisk avoids MagiskSU if existing root solution is detected)
Click to expand...
Click to collapse
It works! Huge thanks!
(This is LineageOS 5-11-17 )
When I removed SuperSU, I chose not to clean up the boot since I saw someone who supposedly bricked their phone doing that, so of course Magisk gave a nasty message about it when flashing,
so I wiped everything (dalvic/ART,Data,System,Cache) and rebuilt: flash rom, flash gapps, install, when get to desktop, install Magisk Mgr with play store and d/l zip(Magisk-v12.0.zip), and go back to TWRP and flash that zip (it does not say anything about su), but after boot I installed TBPro and discovered that yes, indeed I had root. Somewhere in there I set Magisk to "hide". So modified build.prop by only adding the one line you gave me up 2 posts (repeated below) and voila! And PokeGo works!
This is the line I added:
ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys
HINT: I used the JRummy Root Browser for a file manager to copy the line from a text file on my SDcard(from PC), to /system/build.prop and within that I use RB text editor. I say that because for some reason X-plore didn't work for me - edited fine, said saved, but didn't. Wasted time with that.
I do notice that HIDE is checked only for PokemonGo for me, so far, but I haven't tried any banking apps.
THANKS!!!.

Oops - next morning, no root access. Magisk status still shows good. Magisk/Superuser shows all 3 apps (BBS, JR RootBrowser, TBPro) and all switched ON.
EDIT: In Magisk/3 bars/Settings/Superuser - Superuser Access - Set it to "Apps and ADB". Root is back!

I believe @coolguy_16 has said this but I just went and tested and used the line from the 1st post:
ro.build.fingerprint=motorola/osprey_retasia_ds_2gb/osprey_ud2:6.0.1/MPIS24.107-55-2-12/14:user/release-keys
and safetynet works just fine. So it would seem that as long as you have a valid fingerprint for some phone, it doesn't seem to matter what phone you put it on.
It is unknown whether google's "snet" would eventually alert the safetynet folks to this incongruity and then block it. EDIT - I would guess in the long run it would probably be better to use an "exact" fingerprint that would look correct.
EDIT There is a short FAQ in the first post that may help for solving Magisk problems:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Guys just an FYI.
Even though one can pass safetynet, some apps will still refuse to work.
You can try to enable Magisk hide for that specific app(see Magisk settings)
This happens because -
1. The app is sh*t
2. The app checks for other "dangerous props"
So anything which the app finds wrong in your build.prop will cause that.
Well, to find out what your app is checking exactly for.. You will have to decompile it and check for yourself. (Google is your friend)

:good: Great, tks m8.
I am now able to use my banking app (KBC Sign)
(however the app has to be checked in Magisk Hide, otherwise it wont work) :good:

[EXP] Verizon Pixel/Pixel 2 (& XL) Potential Bootloader Unlock Method

Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
How to enable the experiment:
Download the attached APK
Sideload the APK
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[ ] com.pixeloembypass" is in the list
Type in "cmd overlay enable com.pixeloembypass", and hit enter
Reboot the phone
Go into Developer Options to see if "OEM unlocking" can now be toggled on. If so, congratulations!
If "OEM unlocking" is able to be enabled, do so, and reboot the phone into fastboot mode. Unlock as per directions on the factory images site.
NOTE: As usual, if bootloader is unlocked/relocked, a factory reset will be performed.
How to uninstall the experiment:
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[x] com.pixeloembypass" is in the list
Type in "cmd overlay disable com.pixeloembypass", and hit enter
Go into Settings->Apps, and uninstall "Pixel OEM Bypass"
Reboot the phone

This is amazing! Will try it here in about an hour and report back

Maybe tell these guys. They've been at it for a while. You might even get the bounty.
https://forum.xda-developers.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652

TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk

djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So? Come on dj! Lol
Sent from my Pixel 2 using XDA-Developers Legacy app

djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Click to expand...
Click to collapse
have more faith.. john mccain posted it after all

Hope it works
Sent from my Pixel 2 XL using Tapatalk

PresidentMcCain said:
Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
Click to expand...
Click to collapse
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Edit:
I downloaded it on my phone just to see what permissions is calls for and it doesn't open the file.

Didn't work for me. Any tips to try?

thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything

elliwigy said:
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything
Click to expand...
Click to collapse
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.

thompatry said:
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.
Click to expand...
Click to collapse
i understand lol.. when im lazy i just use a file browser n view as an archive lol

collinjames said:
Didn't work for me. Any tips to try?
Click to expand...
Click to collapse
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed

thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
That's okay, it's completely understandable. I agree - typically, you wouldn't want to install a random APK built by a stranger.
I wish I could test it myself, but both my Pixels are from the Google Store, and shelling out $650+ for a test device for a shot-in-the-dark experiment doesn't sound like very responsible spending.

Tried on my P2XL device and no luck..

nelsonTituaAa said:
Tried on my P2XL device and no luck..
Click to expand...
Click to collapse
Thanks for volunteering...have you gave this a try?
PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse

nelsonTituaAa said:
oops.. no haha.. will try again
Click to expand...
Click to collapse
PresidentMcCain said:
Thanks for volunteering...have you gave this a try?
Click to expand...
Click to collapse
tried it and still no luck.

PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse
Tried the command and doesn't seem like it disable android.auto_generated_rro__ on the overlay list.

tried this plus added recommendation and no luck. Verizon Pixel, 8.1

Anybody tried this on a Verizon Pixel 2? I'm willing to give it a shot, but would need a little more detail on the procedure if anyone is willing to help out.

Nethunter & Nexmon Installation

Hey I have installed Oreo 8.0.0 stock and Nethunter Successfully and i want to install Nexmon to the device so I can use frame injections etc. and skip the external wifi dongle.
I have a problem, when i try to compile the nexmon app I get some errors on my PC so I can't compile it... I found a pre-compiled apk on the internet and installed it and it seems to work fine...
Here are my problems, I can't install the framework/tools form the app.
I have Magisk instead of SuperSU because when i rooted the phone with SuperSU the phone gets in a bootloop.
On the nexmon site (http://nexmon.org/) my phone says it supported with Oreo 8.0.0
I think it something weird with Magisk because it is installed in a different way then SuperSU and therefore I don't have the "su" folder in root.
So my question is if someone have a tutorial or backup/rom or something i can flash or if you could help me to install the nexmon and its framework.
Thanks.

*bump*
No one ?

I also have this issue. And no, you are not at all a minority opinion.
I would like say, however, that do not expect much in re packet injection with the wlan(0)... Ideally, you are always going to want to have the ability to inject, as your post said, FRAMES. Not gonna happen, from my experience with the Nexus 5/6/Raspi. The 6p does have a different wireless card, but still, it remains an issue.
Then again, perhaps some of that may come from using encryption mode enabled, and when you use magisk, it is by definition enabled. In fact, I now can't celebrate Kali Linux 2019.2 edition of Nethunter, because magisk doesn't show up {nethunter tries to force no-verity, magisk tries to force encryption} and SuperSU results in error. I've no solution and doubt entirely it'll be found here.

hubrisnxs said:
I also have this issue. And no, you are not at all a minority opinion.
I would like say, however, that do not expect much in re packet injection with the wlan(0)... Ideally, you are always going to want to have the ability to inject, as your post said, FRAMES. Not gonna happen, from my experience with the Nexus 5/6/Raspi. The 6p does have a different wireless card, but still, it remains an issue.
Then again, perhaps some of that may come from using encryption mode enabled, and when you use magisk, it is by definition enabled. In fact, I now can't celebrate Kali Linux 2019.2 edition of Nethunter, because magisk doesn't show up {nethunter tries to force no-verity, magisk tries to force encryption} and SuperSU results in error. I've no solution and doubt entirely it'll be found here.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79606695&postcount=139
In principal you're right.
Especially Oreo and the 2019.2 release, which has the exact same kernel, aren't working fully or nearly that what they supposed to.
You can use Hijacker, which works so so.
So it's your decision.. ;/
If you're still interested in a working Nethunter build, which does not necessarily has a Oreo base, you gonna flip with this one.
Although I decided to limit my participation resp contributions, I am not so egomaniac that I keep my results for me..
From now and then (max. every 3rd day), I'll look into the according "Nethunter" thread.
Best of luck

UsPdSr said:
https://forum.xda-developers.com/showpost.php?p=79606695&postcount=139
In principal you're right.
Especially Oreo and the 2019.2 release, which has the exact same kernel, aren't working fully or nearly that what they supposed to.
You can use Hijacker, which works so so.
So it's your decision.. ;/
If you're still interested in a working Nethunter build, which does not necessarily has a Oreo base, you gonna flip with this one.
Although I decided to limit my participation resp contributions, I am not so egomaniac that I keep my results for me..
From now and then (max. every 3rd day), I'll look into the according "Nethunter" thread.
Best of luck
Click to expand...
Click to collapse
Wow thanks so much for the response, and for the not-necessary information. I don't know why most everyone keeps it like a secret, but, redundantly, thanks

hubrisnxs said:
Wow thanks so much for the response, and for the not-necessary information. I don't know why most everyone keeps it like a secret, but, redundantly, thanks
Click to expand...
Click to collapse
Don't mention it.
Every time I come a across a fellow Kali (Nethunter) user, I make a caper.
And, I agree with you, logically.

Wow, Update Central
UsPdSr,
I hope that I am the first one to inform you about the new beta release for nethunter, an extention of F-droid that operates, essentially, as the Kali Nethunter App Store.
It's supposedly still in Beta, but since they accidentally updated the news feed before almost immediately deleting it (though not the link itself), I have found that
A) The apps are absolutely useful... In our context, the Nexmon app and, in case I wasn't the only one, the nethunter terminal (since the 2019.2 update, I couldn't use up to display last command etc.)
B) If they didn't want anyone to use the store, they'd have brought down the store, not just the update that announced it.
https://store.nethunter.com/en/packages/

Do you know which Nethunter works? Trying different versions, it either is missing completely, or working, but only for a few minutes.

[GUIDE] Android 11 GSI With GApps and Root (magisk)

DON'T DO THIS ON A RAZER PHONE 1 OR IT WILL BE OMEGA BRICKED! ONLY DO THIS ON A RAZER PHONE 2!
This was just an experiment to see if i could cobble together some GSI install guides (that on their own are kinda confusing) to make something moderately more cohesive and understandable. Here's my moderately usable guide!
-----------------------------------------------------------------
VIDEO!
-----------------------------------------------------------------
-----------------------------------------------------------------
Things that work and don't work:
-----------------------------------------------------------------
This section will update periodically as issues arise or fixes arise for said issues.
Note: Things that work: Bluetooth*, all sensors, audio, LTE/SIM/phone stuff, 120hz (you need to go into the settings > Phh treble settings > Misc features > Force FPS > [email protected])
Things that probably work: N/A
Things that don't work for some reason: SafteyNet with Magisk. All modules that I've used work tho...??! Verizon.
Remember, you can always flash back to stock if something doesn't work properly.
-----------------------------------------------------------------
FIXES!!!
-----------------------------------------------------------------
AUDIO FIX!!! GO TO Phh Treble Settings > Qualcomm features > Use alternate audio policy.
Bluetooth audio stops working with this enabled. Disable it for Bluetooth audio. The audio fix doesn't apply to Bluetooth audio ether way.
BLUETOOTH FIX!!! Download a root file browser from the google play store and allow it to have root access. Delete BluetoothCommonRes.apk which is found in the overlay folder which is found in the vendor folder. After you delete BluetoothCommonRes.apk, rename the RazerAuraBluetoothRes.apk to BluetoothCommonRes.apk.
-----------------------------------------------------------------
Important notes
-----------------------------------------------------------------
THIS IS ASSUMING YOU HAVE ALREADY UNLOCKED THE BOOTLOADER OF YOUR DEVICE AND HAVE GOTTEN A SERIAL NUMBER OUTPUT FROM CMD AFTER TYPING IN "fastboot devices" AND MAKE SURE YOU HAVE TYPED IN "fastboot flashing unlock" AND "fastboot flashing unlock-critical".
***NOTE: I AM NOT RESPONSIBLE FOR ANY HARD BRICKED DEVICES OR ANGRY PARENTS. PLEASE DO NOT COME BACK AT ME SAYING I AM STUPID AND BRICKED YOUR PHONE. YOU DECIDED TO DO THIS. PLEASE PROCEED WITH CAUTION AND DON'T SKIM***
ANOTHER IMPORTANT NOTE: The stock firmware is actually really good for unbricking devices. Razer made it easy to fix your bricked device. So basically, if you can get in to fastboot mode, (which you basically always can do) you can unbrick your device super easily.
AGAIN JUST PLEASE, MAKE SURE TO FOLLOW ALL THESE INSTRUCTIONS CAREFULLY AND DONT SKIM OR ELSE YOU MIGHT BREAK SOMETHING!!!
-----------------------------------------------------------------
Introduction
-----------------------------------------------------------------
This is a quick and easy guide for how to install Android 11 on the Razer Phone 2. I'm kind of a noob here myself but I did this and it worked flawlessly. (also if you do run into any issues PLEASE don't count on me for troubleshooting tips (I'm not that great at that))
-----------------------------------------------------------------
Pre-requisites/Downloads
-----------------------------------------------------------------
Get the factory firmware for your phone. It's a good failsafe in case of a bootloop or a bad case of the phone not booting up. Download it here: P-SMR6-RC001-RZR-201022 (latest build at the time of writing)
Extract this with 7zip or WinRar (or windows. You will need 7zip or WinRar for the rest of this)
First you need the actual GSI. Get the latest version. (Make sure its not a pre-release). system-roar-arm64-ab-vndklite-gapps.img.xz is the version that you should get. The vndklite release will allow you to modify the system partition making it possible to get magisk. Note: If you want magisk, MAKE SURE TO COMPLETELY follow the magisk section of this guide aswell or else magisk will NOT install correctly and will NOT work.
This version also has GApps. It will give you Gmail, the google play store, google play services, etc.
Use 7zip or WinRar to extract this.
Your also gonna need the Trinity Kernel (v2). This gives you TWRP and I'm pretty sure you also need this to have the ability to boot up the phone (I may be wrong but it's required.)
use 7zip or WinRar to extract this.
You will also need this zip file made by arter97 I don't really know what it does but you need it. here is the download: Download.
Don't extract this.
Put all these in a known folder that you can access later.
Alright. Now that we're done with the downloads, time to test to make sure your ready to put this on your phone.
-----------------------------------------------------------------
Making sure your computer is ready
-----------------------------------------------------------------
First things first. Go open your platform tools folder, shift-right click and open a PowerShell, or command prompt window there. Shut down your Razer phone 2 and turn it back on with the power and volume down buttons.
Plug it into your PC and type in
Code:
fastboot devices
you should end up with the serial number of the device. if you don't, follow Razer's instructions on how to install USB drivers and then come back here. Link to PDF.
If you get a serial number, close that and flash stock firmware by going into the aura-p-release-etc. folder, then opening flash_all.bat.
When it finishes and the screen goes black, hold the power and volume down buttons again to get back in to fastboot mode.
open back up the CMD/PowerShell platform tools window thing again.
-----------------------------------------------------------------
Installing/Flashing
-----------------------------------------------------------------
In your CMD or PowerShell window, (while in fastboot mode on the phone) type
Code:
fastboot flash system <file name>
in the <file name> area, just drag and drop the system-roar-arm64-etc.img file into your command line. your command will look a little something like this:
Code:
fastboot flash system C:\Users\user\Desktop\system-roar-arm64-ab-gapps.img
Wait until it says complete or something similar like done or something and has no errors.
Then, time to flash the kernel. it should just be called boot.img.
We will be typing in:
Code:
fastboot flash boot <file name>
Do the same thing that you did for the last command which is drag and drop the boot.img file for the file name.
Again, wait until it says done or complete and has no errors.
After that is done, use the volume buttons to select reboot bootloader with your power button on your phone.
Go to recovery mode and swipe where it says to swipe.
Go to the wipe menu and then tap on format data. Type yes and then press enter/ok.
Go back to your computer and open file explorer.
Put the last zip file that I was talking about earlier (the f2fs thing) on the razer phone 2's internal storage. Head back to your phone, and press install.
Scroll down until you find the zip file and press it and install it. (ignore the errors that may or may not be there) After that, go back to the TWRP home screen (with the 8 options)
Go to the reboot menu, then reboot into recovery
Tap on format data and type in "yes" and tap ok. click on "don't install" because you don't need the TWRP app on your phone.
The phone will shut down. Turn it on normally and everything will work!
----------------------------------------------------------------------------------------------------------------------------------
GET THESE THINGS IF YOU WANT 120Hz, GCam, and a SNAZZY RAZER LOGO.
----------------------------------------------------------------------------------------------------------------------------------
To get 120Hz, you need to go into the settings > Phh treble settings > Misc features > Force FPS > [email protected].
If you want your Razer logo to light up again, use Logo+. here is a download: Logo+ APK
The default camera app sucks. Make sure to get GCam 7.4 from Cyanogen Mods (v8.0 is broken). you can get it here.
Download a root file browser from the google play store and allow it to have root access. Delete BluetoothCommonRes.apk which is found in the overlay folder which is found in the vendor folder. After you delete BluetoothCommonRes.apk, rename the RazerAuraBluetoothRes.apk to BluetoothCommonRes.apk.
-----------------------------------------------------------------
Magisk
-----------------------------------------------------------------
So this part was pretty long-awaited. It half-passes SafteyNet and modules work! (at least all the modules that I've used.)
Make sure you have the vndklite variant. That is the only way that this will work.
1. Open up an adb/fastboot powershell/cmd/windows terminal window.
2. Type adb root and hit enter.
3. Type adb shell and hit enter.
4. Type mount -o remount,rw / and hit enter.
5. Type mv /bin/resetprop_phh /bin/phh-resetprop and hit enter.
6. Type phh-securize.sh and hit enter.
The phone should reboot after you approve the request (if there is one) and you are now able to install magisk!
MAKE SURE THAT THE SUPERUSER APP IS NOT THERE AFTER RUNNING phh-securize.sh.
Get specifically this version of Magisk. Download the zip file.
Boot into TWRP and tap on mount, and select everything (usb storage doesn't matter in this case. it never mounts either way.)
Transfer over your zip file via file explorer, and go back to your phone.
Tap install, then scroll down until you find the zip file and tap it. Swipe to flash and wait. After it is done, you can reboot!
You should see Magisk manager in your app drawer. Open that. It might ask you to install it, if so, install it. Allow apps from this source then install. Open it up. You should see that Magisk is installed. Update it and turn on Magisk hide.
If it passes SafteyNet, it's a miracle.
-----------------------------------------------------------------
In case of failure
-----------------------------------------------------------------
If it starts bootlooping or is perpetually stuck at the razer logo, powered by android screen, go back into fastboot mode and run the flash_all.bat stock firmware thing. it will unbrick your phone automatically. Really make sure you don't skim if you try it again. If it did work (which it probably did), then have a good time with android 11!

There is one bug that has stopped me from going GSI. On every one I've tried, there is a game music bug that is common in many of the games I own. If the volume is set to below 50%, the music will cut in and out constantly. It resolves itself if you keep media volume above 50%. It may not be a deal breaker for everyone, but it was for me, as I use my RP2 heavily for games. Other than that, GSIs work beautifully. Thanks for the comprehensive guide!

Reznor7 said:
There is one bug that has stopped me from going GSI. On every one I've tried, there is a game music bug that is common in many of the games I own. If the volume is set to below 50%, the music will cut in and out constantly. It resolves itself if you keep media volume above 50%. It may not be a deal breaker for everyone, but it was for me, as I use my RP2 heavily for games. Other than that, GSIs work beautifully. Thanks for the comprehensive guide!
Click to expand...
Click to collapse
Just curious, what games have that issue?

Marcos8760 said:
Just curious, what games have that issue?
Click to expand...
Click to collapse
All of The Room games, Battle Chasers: Night War, and most premium games that I've bought. For some reason, Monster Hunter Stories doesn't. It seems like mostly games that have more complex audio/music.

Reznor7 said:
All of The Room games, Battle Chasers: Night War, and most premium games that I've bought. For some reason, Monster Hunter Stories doesn't. It seems like mostly games that have more complex audio/music.
Click to expand...
Click to collapse
Thanks for the info. I added that to the top of the thread.
EDIT: Fix at the top of the thread

Ultimately at the end of the day I could not get Dolby Atmos and the RGB lighting on the back of the phone to work on GSI 10. Hopefully someone will come up with a work around for those 2 items in GSI 11.
RJR

rrusek said:
Ultimately at the end of the day I could not get Dolby Atmos and the RGB lighting on the back of the phone to work on GSI 10. Hopefully someone will come up with a work around for those 2 items in GSI 11.
RJR
Click to expand...
Click to collapse
I got the Razer logo working flawlessly with logo+. I didn't really see the appeal for Dolby Atmos as all it did was made it louder and made the audio clip more.

I did have success getting Atmos to work with this module: https://github.com/reiryuki/Dolby-Atmos-Razer-Phone-2-Magisk-Module

Reznor7 said:
I did have success getting Atmos to work with this module: https://github.com/reiryuki/Dolby-Atmos-Razer-Phone-2-Magisk-Module
Click to expand...
Click to collapse
How can I get magisk on the phone though? it has Superuser pre-installed but it doesn't have support for modules and stuff (as far as I can tell). I really would like some info on how to install magisk if possible.

Marcos8760 said:
How can I get magisk on the phone though? it has Superuser pre-installed but it doesn't have support for modules and stuff (as far as I can tell). I really would like some info on how to install magisk if possible.
Click to expand...
Click to collapse
Actually, I may be misremembering. That may have been on a 10 GSI. I don't think I ever did get Magisk to work on an 11.

Reznor7 said:
Actually, I may be misremembering. That may have been on a 10 GSI. I don't think I ever did get Magisk to work on an 11.
Click to expand...
Click to collapse
Alright good to know. like the other info I've gathered, ill put that at the top of the thread until further notice.

The unofficial LOS GSI just got updated with supposed Magisk support. I'm going to give it a try in a few.

Reznor7 said:
The unofficial LOS GSI just got updated with supposed Magisk support. I'm going to give it a try in a few.
Click to expand...
Click to collapse
Nope, Magisk doesn't work.

Thank you. I got it all set up and mostly working well. I was wondering if you could try Minecraft and let me know if it will let you get to the actual login screen.

I cannot get flashing the Android 11 GSI to work.
I downloaded the latest factory image (MR6) and proceeded to install it. To do that, I had to copy the "fastboot.exe" from the SDK platform tools download to the "aura-p-release..." folder with the factory image.
I open a CMD line and type in "fastboot devices" which get me a string of numbers. Then I type in "fastboot flash system system-roar-arm64-ab-gapps.img.xz" which tries to install it but concludes with an error message, being 'Error: Last flash failed : Bad Buffer Size'.
I tried using different computers and cables, but I end up with the same thing. I'm able to flash the factory image just fine, but can't flash Android 11.

AgentXGhost said:
I cannot get flashing the Android 11 GSI to work.
I downloaded the latest factory image (MR6) and proceeded to install it. To do that, I had to copy the "fastboot.exe" from the SDK platform tools download to the "aura-p-release..." folder with the factory image.
I open a CMD line and type in "fastboot devices" which get me a string of numbers. Then I type in "fastboot flash system system-roar-arm64-ab-gapps.img.xz" which tries to install it but concludes with an error message, being 'Error: Last flash failed : Bad Buffer Size'.
I tried using different computers and cables, but I end up with the same thing. I'm able to flash the factory image just fine, but can't flash Android 11.
Click to expand...
Click to collapse
You forgot to extract it with winrar or 7zip. make sure it is a .img file and not a .xz file.

Wow. I spent close to 7 hours trying and trying again. But that's what I get when I don't read all the instructions. -____-
Thanks very much. It works perfectly.

AgentXGhost said:
Wow. I spent close to 7 hours trying and trying again. But that's what I get when I don't read all the instructions. -____-
Click to expand...
Click to collapse
oh noes!

When in TWRP, the system is not mounted, and I cannot see it on my PC nor in TWRP itself. Any ideas what I did wrong?

Gurcharan5 said:
When in TWRP, the system is not mounted, and I cannot see it on my PC nor in TWRP itself. Any ideas what I did wrong?
Click to expand...
Click to collapse
Try going to wipe, then format data. That might fix the problem. If not, try everything again.