GrapheneOS for Pixel 4a Sunfish
This is the updated March 2021 security patch
OTA update, flash through recovery. https://releases.grapheneos.org/sunfish-ota_update-2021.03.02.10.zip
Full update, double click on flash-all in bootloader mode. https://releases.grapheneos.org/sunfish-factory-2021.03.02.10.zip
Warning, full update will wipe device unless you edit the flash-all file with notepad and remove the -w before the update file.
Graphene does not and will never include gapps and can not be installed on this rom.
MicroG is also not included but can be added separately.
No signature spoofing without rebuilding the rom and that would defeat the security/privacy of this rom.
Awesome, thank you very much.
TheSayaMan said:
GrapheneOS for Pixel 4a Sunfish
https://releases.grapheneos.org/sunfish-factory-2021.01.05.03.zip
Simple install. Extract link to your ADB tools folder. Double click on flash-all and let the flashing do the work on it's own.
This is the updated January 2021 security patch
Graphene does not and will never include gapps and can not be installed on this rom.
MicroG is also not included but can be added separately.
Signature spoofing is also not supported.
Click to expand...
Click to collapse
Is there a good guide that explains how to add signature spoofing. It all seems to be outdated info
kev15058 said:
Is there a good guide that explains how to add signature spoofing. It all seems to be outdated info
Click to expand...
Click to collapse
A patch for signature spoofing on Android 11 only works from Magisk if the ROM's services.jar already contains classes.dex which this does not. So as stated in the OP, signature spoofing is not supported with this ROM. This ROM could be rebuilt to allow such a thing but that would defeat the purpose of the ROM.
GrapheneOS is designed for the privacy/security users. So you won't ever see Google stuff in GrapheneOS unless someone does what @TheSayaMan said, but then that defeats the purpose of the ROMs focus of privacy/security.
I can recommend CalyxOS too. Its awesome. Both projects are awesome.
kev15058 said:
Is there a good guide that explains how to add signature spoofing. It all seems to be outdated info
Click to expand...
Click to collapse
Check this out : https://www.paulligocki.com/installing-graphineos-on-the-google-pixel-4a/
Moto_Fan said:
Check this out : https://www.paulligocki.com/installing-graphineos-on-the-google-pixel-4a/
Click to expand...
Click to collapse
This will not enable signature spoofing and also I don't recommend as stated on this link to lock the bootloader. You should never ever lock the bootloader on a custom rom. You can not flash software firmware on a locked bootloader and if you have a issue unlocking it afterwards then your screwed.
Updated February 2021 patch in OP.
TheSayaMan said:
This will not enable signature spoofing and also I don't recommend as stated on this link to lock the bootloader. You should never ever lock the bootloader on a custom rom. You can not flash software firmware on a locked bootloader and if you have a issue unlocking it afterwards then your screwed.
Click to expand...
Click to collapse
If you check out the Developer site, they tell you to RELOCK BOOTLOADER, these are the same instructions, much more straight forward.
*remember*
Don't forget to fact check, so I avoid sticking in .....
Edit
ATTACHED FOOT
Moto_Fan said:
If you check out the Developer site, they tell you to RELOCK BOOTLOADER, these are the same instructions, much more straight forward.
*remember*
Don't forget to fact check, so I avoid sticking in .....
Edit
ATTACHED FOOT
Click to expand...
Click to collapse
And...
My mans above you gives you a concrete reason to not listen to those knuckle dragging idiots...
Because... Unlike them... We have to listen to how you've destroyed your device by listening to the crayon eating morons...
If you ain't stock... Don't lock the damn bootloader
Edit: I will eat my words if Graphene or Calyx buys you a device for following their instructions
rignfool said:
And...
My mans above you gives you a concrete reason to not listen to those knuckle dragging idiots...
Because... Unlike them... We have to listen to how you've destroyed your device by listening to the crayon eating morons...
If you ain't stock... Don't lock the damn bootloader
Edit: I will eat my words if Graphene or Calyx buys you a device for following their instructions
Click to expand...
Click to collapse
Its is basically a stock ROM, cleaned up code, mods to harden security, name of the file is even stock bud.
I think imma listen to the morons... I got (2) sunfishes, let's call it a sacrifice on me....
TheSayaMan said:
This will not enable signature spoofing and also I don't recommend as stated on this link to lock the bootloader. You should never ever lock the bootloader on a custom rom. You can not flash software firmware on a locked bootloader and if you have a issue unlocking it afterwards then your screwed.
Click to expand...
Click to collapse
#2 you never flash custom or stock over a LOCKED BL. FASTBOOT will NOT allow it...
*Edit*
When u say "This won't allow Signature Spoofing," can you be a little more specific? What exactly is "This"?
I followed the instructions to the letter on my Windows 10 laptop. This is not the entire process, but did unlock the bootloader, flashed Grapheneos. Then locked the bootloader before rebooting and setting up the OS. I can say I am not 100% ready for a no Google os, but I will investigate more for alternative apps to meet my needs. I followed the same instructions to go back to stock (factory image) both unlocking the bootloader, flashing, and then re-locking bootloader before setting up factory os. This is not an endorsement of the process, and there is always issues that can come up with flashing. Use at your own risk
bill_in_mtl said:
I followed the instructions to the letter on my Windows 10 laptop. This is not the entire process, but did unlock the bootloader, flashed Grapheneos. Then locked the bootloader before rebooting and setting up the OS. I can say I am not 100% ready for a no Google os, but I will investigate more for alternative apps to meet my needs. I followed the same instructions to go back to stock (factory image) both unlocking the bootloader, flashing, and then re-locking bootloader before setting up factory os. This is not an endorsement of the process, and there is always issues that can come up with flashing. Use at your own risk
Click to expand...
Click to collapse
Yea, i hear ya about the NO GAPPS, i been using F-Droid which has a lot of alternatives. Everything flash back to stock ok?
Moto_Fan said:
Yea, i hear ya about the NO GAPPS, i been using F-Droid which has a lot of alternatives. Everything flash back to stock ok?
Click to expand...
Click to collapse
Yep, flashed back without issue. Back on stock with a locked bootloader. Going to spend some time going through all the non-google options to see if I can give it a real go
thanks
I'm having trouble setting up a APN with this OS. Does anyone know how to allow user access to APN Setting in Graphene?
Moto_Fan said:
Its is basically a stock ROM, cleaned up code, mods to harden security, name of the file is even stock bud.
I think imma listen to the morons... I got (2) sunfishes, let's call it a sacrifice on me....
Click to expand...
Click to collapse
All good and dandy know it all. Now that you locked the bootloader, try flashing back to stock android with the google factory images. You can't do it!!!!!!!!!!
Moto_Fan said:
#2 you never flash custom or stock over a LOCKED BL. FASTBOOT will NOT allow it...
*Edit*
When u say "This won't allow Signature Spoofing," can you be a little more specific? What exactly is "This"?
Click to expand...
Click to collapse
On Android, all applications are signed (usually using SHA1 with RSA). The certificate/key-combinations used to sign apps are self-signed. This means there is no PKI / certificate authority to verify a key to be owned by a person/company/entity. Thus everyone can come up with a key that has a equally valid Google certificate as keys used by Google to publish their apps.
TheSayaMan said:
All good and dandy know it all. Now that you locked the bootloader, try flashing back to stock android with the google factory images. You can't do it!!!!!!!!!!
Click to expand...
Click to collapse
Exactly, in this case you would have to fastboot oem unlocking to unluck bootloader before fastboot flashing Factory Images, obviously...
Related
Thanks to some questions and awnsers I was able to create the
rooted boot.img for our HTC Bolt devices.
This was tested on the HTC Bolt Software 1.17.651.11 Android N 7
How To: (downloads at bottom of page)
Connect Device to computer
Insure that usb debugging is on as well as OEM unlock is checked.
The device must be Boot-loader unlocked to do this!
place both the patched_boot.img and the magisk_cache.img in the same directory your fastboot files are setup at ( c:/android/sdk/fastboot or wherever you have it)
Boot the phone into Download mode. ( Power + VOL down)
Open up terminal on the computer and run both these commands:
fastboot devices
fastboot flash boot patched_boot.img
fastboot flash cache magisk_cache.img
followed by fastboot reboot
you'll need to head over to :
http://forum.xda-developers.com/htc-10/development/root-magisk-autoroot-magisk-phhs-t3507505
Grab the manager.apk and the super user apk to complete the setup.
Give these guys a thanks also for getting this going, gonna build a rom with debloat next and see if the twrp will flash it with this boot.img behind it.
shall see
Thanks to:
@OMJ Everything!
@topjohnwu magisk
@Captain_Throwback -twrp,root
@Chainfire - root
Downloads
Patched boot.img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528674
Cache img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528673
***********DevDigitel Custom Images************
Secure Boot Img: https://www.androidfilehost.com/?fid=457095661767122602
Unsecure Boot Img: https://www.androidfilehost.com/?fid=745425885120693359
Flashable ZIPS:
SuperSU:
https://www.androidfilehost.com/?fid=673368273298916495
Radio Fix Zip/FP Scanner Fix : https://www.androidfilehost.com/?fid=673368273298916521
Device will bootloop once, and when done will install su. Please be patient
Nice!
suprised that it went so smoothly, su being systemless is a little buggy here and there with Android N, but otherwise i was able to navigate the internals, remove the bloat, make some build prop edits and theyve stuck. so far so good.
Went ahead and tried to use flashify and flash the twrp image from other post. Flashed and was able to make a backup to sd only. I didn't flash or try to restore it yet but I did have to relock and restore 3x with the stock ruu after removing too much system and trying to flash xposed
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
S off
urbster1 said:
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
Click to expand...
Click to collapse
Not sure.. Probably gonna be some time with Android N.
I was able to change carrier types in Ui.
Got vzw 1x 3g 4G icons
Hot-spot mod
And a few other things working.
No radios to flash.. No kernels and I don't dev kernels.
So I don't need s-off really.. It's more so just having to re-lock
To go back to stock.
I just ordered a Bolt, can't wait to play
Screen shots
OMJ said:
I just ordered a Bolt, can't wait to play
Click to expand...
Click to collapse
Yey can't wait! It didn't want to be the only one working
On it!
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
Use the other supported devices section at bottom.
Just follow the steps on htc dev.
Save the unlock.bin file HTC will email you. You need it Every time you need to lock/unlock. Without s-off (removing the 2nd lock that protects the radios)
* the phone has to be re-locked to be restored with the stock htc software "ruu's"
Htc ruu is a 1 click style restore program...similar to odin that Will run on the PC and restore phone to stock.
It also comes in a update.zip format that can be flashed with the stock Signed recovery only via sd card slot.
Twrp is currently working on bolt / but has limitations because Its not 100%
More screenshots
Random stuff that can be unlocked hidden in the phone.
urbster1 said:
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
Click to expand...
Click to collapse
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
OMJ said:
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
Click to expand...
Click to collapse
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
jcase said:
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
Click to expand...
Click to collapse
@jcase let me know if you need any more partitions, or anything else dumped... Worse case I can send you mine.
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Team DevDigitel said:
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Click to expand...
Click to collapse
I actually just switched to this method after s-off, due to safetynet failing after detecting a unlocked bootloader...magisk can hide the detection
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Team DevDigitel said:
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Click to expand...
Click to collapse
yep...AP is my only goal
there's a kernel patch to bypass detection but I don't know squat about kernel modding
As a friendly reminder to those unfamiliar with unlocking/re-locking their bootloaders;
Unless your on 100% stock, and planning on reselling your phone, don't re-lock the bootloader.
For some reason re-locking the bootloader while you have a custom ROM installed will cause the phone not to boot (in a way, soft bricking it.)
And, leave "OEM unlocking" in the "Developer Options" CHECKED, once that is unchecked you cannot unlock the phone once a soft brick happens.
The official advice from Essential about re-locking your phone is ONLY for the official firmware. Pretend they never said that on their site, it has caused more trouble then necessary. It's even dangerous to re-lock while running the Oreo beta.
Concerning un-bricking the device, at the moment there is no known way.
And it will be this way until someone figures out a way to exploit the bootloader or reverse engineer it.
So please don't flood this thread with asking for help to un-brick your device, I nor anyone else can help you on that at this given time, all I'm doing is trying to is prevent that happening.
So, safe unlocking! And happy holidays!
EDITS:
1) According to some reports, when you lock your bootloader it will also automatically untoggle the "OEM Unlocking" option.
2) It appears when re-locking the phone on a non-stock ROM some partitions are becoming corrupt, and resulting in the "red boot warning" screen. Under most circumstances you can fix that screen, but not while the bootloader is locked (since you need the fastboot flash command.)
3) When the partitions become corrupt you cannot boot into any mode, including the stock recovery. This is why Essential's suggestions are pointless at this stage of the brick.
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
avd said:
Should be pinned and in the OP of every mod thread
Click to expand...
Click to collapse
totally agree, i made this "trick" with one of my first android phone and it never happen me again. But new user who would flash Los or other rom should be aware of this issue, specially when jtag is not an option. As far we'll make some powerfull 500$ brick :crying:. it's our duty to make people aware of this. @invisiblek you guy made an incredible work and so fast but like he said i think you should warn people of the risk in the OP
avd said:
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Ellises said:
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Click to expand...
Click to collapse
It's very easy to ask for a thread to get stuck to the top.
Just use the report post button, and ask, whether or not becomes a sticky is up to the Mods.
How to Report a Post.
Sent from my XT1254 using XDA Labs
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
ericzhf said:
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
Click to expand...
Click to collapse
Ellises said:
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
Click to expand...
Click to collapse
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
ericzhf said:
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
Click to expand...
Click to collapse
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
tech_head said:
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
Click to expand...
Click to collapse
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
ericzhf said:
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
Click to expand...
Click to collapse
FDR is not "back to stock".
You must to a full flash to get back to stock.
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Ellises said:
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Click to expand...
Click to collapse
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
I could also mention on their stock build page it wants you to unlock the bootloader to manually update through the bootloader. But on the oreo beta page it mentions nothing about having to be unlocked, or locked to do it via the stock recovery. So the average user could presume they need to be unlocked.
NaterTots said:
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
Click to expand...
Click to collapse
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
No.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Obamaloominaty said:
No.
Click to expand...
Click to collapse
tech_head said:
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Click to expand...
Click to collapse
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
WiddleyScudds said:
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
Click to expand...
Click to collapse
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
tech_head said:
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
Click to expand...
Click to collapse
I just got an ota notification for OPM1. 180104.092. think I'll be safe I I take it, then factory reset and then lock? Because I can't seem to locate stock NMK24B to flash. Maybe I'm not looking hard enough .
Hi,
Unfortunaltelly my magisk cant hide gpay (safetynet true). Im wondering about unroot my pixel3.
Please tell me, which way is the best to unroot/lock bootloader? If I flash blueline-image with - w in flash-all.bat, can i lock bootloader with any problems (bricks)? Sorry for my english.
Thx for advice.
Wysłane z mojego Pixel 3 przy użyciu Tapatalka
If you successfully flashed the factory image (no errors) without removing the -w flag you should be able to relock the bootloader, yes. I believe locking the bootloader will induce another wipe so be sure you have things backed up if you have used the phone since flashing the factory image.
I have not rooted my devices since Pixel 1 and things have changed since then so someone else can chime in to confirm, but flashing the full factory image should be a reliable way to return to pure stock.
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
jd1639 said:
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
Click to expand...
Click to collapse
Unrooted and unlocked will cause Google Pay not to work. I would suggest to just leave "Allow OEM unlocking" enabled.
'
83097markcynt said:
Unrooted and unlocked will cause Google Pay not to work. I would suggest to just leave "Allow OEM unlocking" enabled.
'
Click to expand...
Click to collapse
That's good to know. I don't use gpay so didn't know that.
Unlocking Verizon Bootloader
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
jkday3 said:
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
Click to expand...
Click to collapse
I'm not sure what you're asking? Is what possible?
jkday3 said:
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
Click to expand...
Click to collapse
jd1639 said:
I'm not sure what you're asking? Is what possible?
Click to expand...
Click to collapse
You cannot unlock the bootloader on a Verizon device. It's software locked based on IMEI. The ones sold at Best Buy are Verizon versions and are fully locked.
Gpay works fine with magisk. If it's not working for you, I'd dig into why before unrooting and relocking.
If you don't want to do that, just flash the magisk uninstaller to get rid of root and then flash a custom kernel. Pretty much all custom kernels will hide an unlocked bootloader and allow you to pass safety net.
New here to this community.
I bought a pixel 3xl a few weeks ago and i wanted to root just to see what's new, but i now realize I don't need to root this almost perfect phone. I unrooted the phone with magisk. I have the factory img. File to use incase i did something wrong when rooting. I just want to be able to let my phone boot up normally again. Can someone please help me?
NightWingJbr said:
I bought a pixel 3xl a few weeks ago and i wanted to root just to see what's new, but i now realize I don't need to root this almost perfect phone. I unrooted the phone with magisk. I have the factory img. File to use incase i did something wrong when rooting. I just want to be able to let my phone boot up normally again. Can someone please help me?
Click to expand...
Click to collapse
I'm not sure what you mean by boot up normally? Do you mean the bootloader unlock warning when it first starts to boot? You can get rid of that by locking the bootloader but before I'd do that I'd flash the full factory image, including wiping the device with the -w not removed in the flash-all batch file.
jd1639 said:
I'm not sure what you mean by boot up normally? Do you mean the bootloader unlock warning when it first starts to boot? You can get rid of that by locking the bootloader but before I'd do that I'd flash the full factory image, including wiping the device with the -w not removed in the flash-all batch file.
Click to expand...
Click to collapse
Yes and thank you for your reply. J just want to know how to wipe the device" with the -w not removed in the flash-all batch file". That's the only thing i don't understand. If you could explain. So i can go back to boot up without the warning.
NightWingJbr said:
Yes and thank you for your reply. J just want to know how to wipe the device" with the -w not removed in the flash-all batch file". That's the only thing i don't understand. If you could explain. So i can go back to boot up without the warning.
Click to expand...
Click to collapse
See the "Factory reset via fastboot" section at https://forum.xda-developers.com/pixel-3/how-to/complete-pixel-3-how-to-guide-newbie-t3922269
This will not remove the warning at boot, but is a necessary step. To lock the bootloader, read all the posts (especially the ones that detail the consequences of relocking) at https://forum.xda-developers.com/pixel-3-xl/help/how-to-lock-bootloader-t3866074 and pick a method.
I strongly recommend against relocking the boot loader, though. It is easy to brick your phone during the relock process. Also, a locked bootloader severely limits your ability to recover a bricked phone. Just ignore the warning at boot message. Removing it may come at a high cost.
Thank you so much. I will ignore then..
what is -w..
jd1639 said:
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
Click to expand...
Click to collapse
i was wondering what -w is? probably a dumb question but i couldnt find anything on google about it
comic_nightwing said:
i was wondering what -w is? probably a dumb question but i couldnt find anything on google about it
Click to expand...
Click to collapse
In the flash-all batch file in the factory image the -w (part of a line in the batch file) controls whether it wipes clean or does a dirty install leaving apps and data (user).
First of all, I am not a dev and this write up contains steps used by various devs to achieve fulll root. For some, these steps have worked out well. But, not for me. I had issues with some of the steps not fully working as they should, so I did some research until I could piece together something that worked for me. Here's what I did and managed to get fully rooted using the boot.img from the stock firmware after doing all the steps from this link Articul8Madness's Rooting Guide and couldn't get full root access even after using the steps from this link Articul8Madness's Guide for R/W Access. As I have said, these steps worked for most people. I wasn't one of them.
I followed the steps up to the step where the boot.img is modded by Magisk. This is where I omitted using the modded boot.img and used the original boot.img from the stock firmware and I then ran the flashfile script as mentioned in the steps. After everything was applied I then, rebooted the phone, started setup, disabled System Updates, and I then proceeded to install TWRP using the steps from this link https://drive.google.com/drive/folders/1KZ0xhstQ9V_7TYt3xs7P5XdroYX61CEA after opening Minimal ADB and Fastboot applying these scripts
adb reboot fastboot
then apply this
fastboot flash recovery twrp-3.5.2_10-kiev.img
I then rebooted into recovery and installed TWRP to all available partitions. I then installed Magisk, enabled Systemless Hosts in settings, and rebooted. Afterwards, I used the steps here Munjeni's RW in Super Partition Tool to get RW in super partitions after downloading and using superrepack. I had omitted the ./superrepack /dev/block/bootdevice/by-name/super system_a in order to have it applied to all available partitions. Everything worked out great. I then rebooted, updated Magisk, installed Root Checker and Root Explorer with Superuser root access. I then installed Adaway from https://github.com/AdAway/AdAway and clicking on the Get It On AdAway image. Anything that requires root access here on out, can now be installed. As for the SafetyNet issue, I have not had any problem with it at all even though the check had failed. All is now working well and I sincerely hope that this guide will help others as it have helped me. I may have done this write up but, all credits goes to the true devs.
Time for devs to start making custom Roms now that TWRP can be installed.
Your first link doesn't work for me. The Adaway link works. FYI.
RETIEF said:
Your first link doesn't work for me. The Adaway link works. FYI.
Click to expand...
Click to collapse
WOW!!! I see what I did wrong. All links are now working.
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Sorry, but you will have to ask one of the Devs in the links that I've provided in the OP. Perhaps they are more suited to help with that.
eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Linux will work fine. All the commands required are done thru a terminal session. Use a text editor to get the long unlock code from the phone.
Good luck.
Ok about terminal. I used cmd , but bootloader cannot be unlocked official way nor at&t unlockable coz i don't live in usa.I will try 3rd party helpers.
iceman19631 said:
First of all, I am not a dev...
Click to expand...
Click to collapse
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.
egalambos said:
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.
Click to expand...
Click to collapse
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.
iceman19631 said:
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.
Click to expand...
Click to collapse
Any plans for an update to 3.6.0 for Android 11??
egalambos said:
Any plans for an update to 3.6.0 for Android 11??
Click to expand...
Click to collapse
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.
iceman19631 said:
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.
Click to expand...
Click to collapse
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I don't have an answer for that at this time since I'm still on 10. That'd be too much like a blind man in a desert looking for shade and telling another which way to go.
Greetings, I have a few questions. re the Moto G 5G (One 5G Ace)
I've not found a TWRP for this phone yet which were you using?
In other phones it was important to backup the IMEI (EFS ) and 'persistent' partitions. Do we not do that with this phone as well?
Thx in advance
Sorry for the late reply. I used this version of TWRP twrp-3.5.2_10-kiev.img. As far as the IMEI (EFS) question, it wasn't required when using this root process. However, you can back those up if you like.
hello! First of all, I don't know if this topic is in this subforum or in another. If it's not here, I'm sorry. I've been trying to lock the bootloader for days before flashing the stock immediately. I try it from fasboot flashing lock and I get this: "failed (remote: 'invalid android images, skip locking') fastboot: error: command failed ". I have the r33 of Adb fasboot. I have restarted in fasboot and from there choose to restart in bootloader as I read in the forums and the same. what happens is that regardless of the ROM, root or mod to pass the safetynet. wallet and among other apps it detects them as root or similar....
juaki said:
hello! First of all, I don't know if this topic is in this subforum or in another. If it's not here, I'm sorry. I've been trying to lock the bootloader for days before flashing the stock immediately. I try it from fasboot flashing lock and I get this: "failed (remote: 'invalid android images, skip locking') fastboot: error: command failed ". I have the r33 of Adb fasboot. I have restarted in fasboot and from there choose to restart in bootloader as I read in the forums and the same. what happens is that regardless of the ROM, root or mod to pass the safetynet. wallet and among other apps it detects them as root or similar....
Click to expand...
Click to collapse
I assume you're trying to relock the bootloader? You cannot do this if any of the images have been modified, including Magisk patching. You have to flash back to stock first.
If you are trying to use payment apps, please see this thread.
yes of course. I have the stock of May. no root or patched init.boot or magisk. Totally stock except for the bootloader, which I intend to close since with no method or module I can get the wallet and other things to work for me. in wallet it says "this device does not meet the requirements". I don't know if a partition has been touched or something, because before I had the crDroid...
juaki said:
yes of course. I have the stock of May. no root or patched init.boot or magisk. Totally stock except for the bootloader, which I intend to close since with no method or module I can get the wallet and other things to work for me. in wallet it says "this device does not meet the requirements". I don't know if a partition has been touched or something, because before I had the crDroid...
Click to expand...
Click to collapse
I wonder why that is. I don't use wallet for payments but I did use it for Megadeth last year and I have my Covid info on it.
I see people having issues so I tried to add a few cards and had no issues, but I know there are people like you where it just doesn't work
HipKat said:
I wonder why that is. I don't use wallet for payments but I did use it for Megadeth last year and I have my Covid info on it.
I see people having issues so I tried to add a few cards and had no issues, but I know there are people like you where it just doesn't work
Click to expand...
Click to collapse
The fact is that it worked perfectly for me with root, stock ROM, safetynet 2.40 mod 1.2 module and Kira kernel. anyway...
juaki said:
The fact is that it worked perfectly for me with root, stock ROM, safetynet 2.40 mod 1.2 module and Kira kernel. anyway...
Click to expand...
Click to collapse
Um you stated no method or module worked for you. Now you are saying you had Wallet and "other things" working with root.
indeed. What I wanted to say is that it used to work for me, and suddenly it has stopped working for me in any ROM. with module or without it, with root or without it. and when flashing the stock in both slots and doing the relevant process, I can't block the bootloader. I honestly don't know what to do anymore. The phone passes the safetynet test.
juaki said:
indeed. What I wanted to say is that it used to work for me, and suddenly it has stopped working for me in any ROM. with module or without it, with root or without it. and when flashing the stock in both slots and doing the relevant process, I can't block the bootloader. I honestly don't know what to do anymore. The phone passes the safetynet test.
Click to expand...
Click to collapse
For locking the bootloader, you many want to try Android Flash Tool. Select "Force Flash all Partitions", "Lock Device" and "Wipe".
What @Lughnasadh has said is your best bet if you are not familiar manually wiping/modifying your phone. If you are not rooted and your phone system image is stock, then you need to lock your bootloader.
As Google has posted on their site a good number of times, you cannot use any of their security based services with an unlocked bootloader.
With root access, you can circumvent these restrictions. But without root access, you need to lock your bootloader. And when you attempt to do so, be sure that you don't utilize the newer versions of platform-tools as they seem to still cause problems.
juaki said:
The fact is that it worked perfectly for me with root, stock ROM, safetynet 2.40 mod 1.2 module and Kira kernel. anyway...
Click to expand...
Click to collapse
The newest working Safetynet Module is 2.4.0-MOD_1.2 by Kdrag0n
I uploaded it to my Mediafire
HipKat said:
The newest working Safetynet Module is 2.4.0-MOD_1.2 by Kdrag0n
I uploaded it to my Mediafire
Click to expand...
Click to collapse
The original USNF module was indeed developed by @kdrag0n but the working module is the fork by @Displax .
It is always best to link to the official source of the module, rather than re-uploading it, due to the potential of someone modifying it for malicious purpose.
Here is the official source
V0latyle said:
The original USNF module was indeed developed by @kdrag0n but the working module is the fork by @Displax .
It is always best to link to the official source of the module, rather than re-uploading it, due to the potential of someone modifying it for malicious purpose.
Here is the official source
Click to expand...
Click to collapse
Yeah if I could have found it but the version I have on my phone is the one I listed, or it's named wrong
HipKat said:
Yeah if I could have found it but the version I have on my phone is the one I listed, or it's named wrong
Click to expand...
Click to collapse
Apologies in advanced if I misunderstood...
the one you listed & the one on your phone is the same one in the Github V0latyle linked (from Displax's very own USNF fork Github) -- it is not named wrong, but if you look at your own screenshot from your own device; it displays "modded by Displax"
Again, sorry if I'm taking it wrong that you didn't get it, but the words "but" and "or it's named wrong" in your post led me under that impression you think you are under kdrag0n's main branch just by name itself....
simplepinoi177 said:
Apologies in advanced if I misunderstood...
the one you listed & the one on your phone is the same one in the Github V0latyle linked (from Displax's very own USNF fork Github) -- it is not named wrong, but if you look at your own screenshot from your own device; it displays "modded by Displax"
Again, sorry if I'm taking it wrong that you didn't get it, but the words "but" and "or it's named wrong" in your post led me under that impression you think you are under kdrag0n's main branch just by name itself....
Click to expand...
Click to collapse
You are correct, I did not notice the Modded by in the name and did think this was Drag0n's but it's all good. It's the one that works and that's the important thing