Related
Before flashing Cyanogenmod I really need to install ClockWorkMod? Because when I press power + volume some kind of pre-installed CWM appears and do have all the function I need (wipe/factory reset, select update from sd card etc) Can't I Install Cyanogenmod from there?
Sorry if I have bad english :angel:
Yes, you do need to install CWM. Also meaning of pre-installed CWM, it is Samsung Stock Recovery. It is very easy method to get CWM on your note.
i2nice said:
Yes, you do need to install CWM. Also meaning of pre-installed CWM, it is Samsung Stock Recovery. It is very easy method to get CWM on your note.
Click to expand...
Click to collapse
Thanks for answering! I got it, but I have another doubt, If I install Cyanogenmod in my device, I will have lower graphics in-game? Something like no developer optimisation for my ROM (no antialiasing, poor texture quality etc)? Or This depends of the device not the ROM?
flashing CWM also is very important because it has Backup and restore options which are not included in stock recovery
1st thing I do for years is taking nand backup to restore in case on any failure (which happens alot with trying roms and mods)
thermax04 said:
flashing CWM also is very important because it has Backup and restore options which are not included in stock recovery
1st thing I do for years is taking nand backup to restore in case on any failure (which happens alot with trying roms and mods)
Click to expand...
Click to collapse
I got it!
But If I install Cyanogenmod in my device, I will have lower graphics in-game? Something like no developer optimisation for my ROM (no antialiasing, poor texture quality etc)? Or This depends of the device not the ROM?
There is some way for I get custom Android themes and apps with samsung's ROM? Like update the apps to custom android apps? Can I substitute the notification bar too?
kokero said:
I got it!
But If I install Cyanogenmod in my device, I will have lower graphics in-game? Something like no developer optimisation for my ROM (no antialiasing, poor texture quality etc)? Or This depends of the device not the ROM?
There is some way for I get custom Android themes and apps with samsung's ROM? Like update the apps to custom android apps? Can I substitute the notification bar too?
Click to expand...
Click to collapse
Get Apex launcher or one of the other launchers available. Easy to theme and remains stock.
I don't believe you should have problems in games as the cm10 team use the aosp or aokp rom. Straight from google like on the nexus series. They then tweak and theme as they please...
ultramag69 said:
Get Apex launcher or one of the other launchers available. Easy to theme and remains stock.
I don't believe you should have problems in games as the cm10 team use the aosp or aokp rom. Straight from google like on the nexus series. They then tweak and theme as they please...
Click to expand...
Click to collapse
Ok, I I'm going to install Cyanogenmod, but I have Windows 8 so I need to disable driver signature enforcement, I've already did it, long time ago, to Install jelly bean on my Xperia Mini Pro, I need to do It again every time I'm going to install any custom ROM or it's a lifelong kind of thing?
kokero said:
Ok, I I'm going to install Cyanogenmod, but I have Windows 8 so I need to disable driver signature enforcement, I've already did it, long time ago, to Install jelly bean on my Xperia Mini Pro, I need to do It again every time I'm going to install any custom ROM or it's a lifelong kind of thing?
Click to expand...
Click to collapse
Every time I flash a custom rom I simply download the zip file and copy to the sd card. Flash using CWM...
Never disabled anything on my PC and it always works. I too have win 8...
ultramag69 said:
Every time I flash a custom rom I simply download the zip file and copy to the sd card. Flash using CWM...
Never disabled anything on my PC and it always works. I too have win 8...
Click to expand...
Click to collapse
So how did you flashed CWM? Cyanogenmod official wiki tells me this:
"NOTE: On Windows 8 you must disable driver signature enforcement in order to use zadig"
Link: http://wiki.cyanogenmod.org/w/Install_CM_for_n8000
kokero said:
So how did you flashed CWM? Cyanogenmod official wiki tells me this:
"NOTE: On Windows 8 you must disable driver signature enforcement in order to use zadig"
Link: http://wiki.cyanogenmod.org/w/Install_CM_for_n8000
Click to expand...
Click to collapse
You're using Heimdall, not ODIN.. ODIN easier to use though Heimdall good too.
If you are rootedalready you can also use Mobile ODIN, pro version to be safe.... Easiest way I know how...
ultramag69 said:
You're using Heimdall, not ODIN.. ODIN easier to use though Heimdall good too.
If you are rootedalready you can also use Mobile ODIN, pro version to be safe.... Easiest way I know how...
Click to expand...
Click to collapse
Im going tp use Cyanogenmod's official way of install, because I don't need to root first, thanks for helping me! I owe you one!
ultramag69 said:
You're using Heimdall, not ODIN.. ODIN easier to use though Heimdall good too.
If you are rootedalready you can also use Mobile ODIN, pro version to be safe.... Easiest way I know how...
Click to expand...
Click to collapse
For sure Odin method is better! But I need to root my device first? Or not?
I'm goig to do this procedure:
http://www.androidegis.com/how-to/i...ckworkmod-touch-recovery-on-galaxy-note-10-1/
And then:
http://www.androidegis.com/how-to/install-official-cyanogenmod-10-1-nightlies-for-galaxy-note-10-1/
kokero said:
For sure Odin method is better! But I need to root my device first? Or not?
I'm goig to do this procedure:
http://www.androidegis.com/how-to/i...ckworkmod-touch-recovery-on-galaxy-note-10-1/
And then:
http://www.androidegis.com/how-to/install-official-cyanogenmod-10-1-nightlies-for-galaxy-note-10-1/
Click to expand...
Click to collapse
Yep, that should be ok... Root and CWM first then CM10...
Just a suggestion, in ODIN untick "reboot". This way you can go to recovery before it reboots and changes back to stock recovery... It does this so you do need to boot to recovery afterwards manually. volume up + power until logo appears then release power button... Then you can flash CM10 but make sure to follow all the steps...
Oh yeah, in ODIN, DON'T TICK REPARTITION... You will end up with a big problem if you do...
I bought this nexus 5 from a previous user, noticed bootloader unlocked, diferente kernel(althought i flashed another already), but something caught my eye, im not sure if i have the stock rom, as i get an update of 16mb and fails.
"devcheck app"
Under system = Codename: Hammerhead
5.1.1
Build: LMY48I
Is this stock?
Help?
Sent from my Nexus 5 using XDA Free mobile app
I think nobody wants help a KILLER
HIGKILLER said:
I bought this nexus 5 from a previous user, noticed bootloader unlocked, diferente kernel(althought i flashed another already), but something caught my eye, im not sure if i have the stock rom, as i get an update of 16mb and fails.
"devcheck app"
Under system = Codename: Hammerhead
5.1.1
Build: LMY48I
Is this stock?
Click to expand...
Click to collapse
It is not stock. Unlocked bootloader is fine, everything else is a no-go. The different kernel is the glaring problem, you can not apply an OTA with that non-stock kernel. The first, most complete, easiest option is to flash the latest factory image. Seeing as this is a new phone to you, I can't imagine that you have a ton of personal info to save. For me personally, I'd flash the image just so I know that I'm starting with a fresh clean slate. Then you can read up and root/mod how you'd prefer.
Yaz75 said:
It is not stock. Unlocked bootloader is fine, everything else is a no-go. The different kernel is the glaring problem, you can not apply an OTA with that non-stock kernel. The first, most complete, easiest option is to flash the latest factory image. Seeing as this is a new phone to you, I can't imagine that you have a ton of personal info to save. For me personally, I'd flash the image just so I know that I'm starting with a fresh clean slate. Then you can read up and root/mod how you'd prefer.
Click to expand...
Click to collapse
I have experience with custom roms all that, i did flash this kernel, but the room, is what bothers me. and thank you, i was kinda sure this wasent stock rom! Thank you
HIGKILLER said:
"devcheck app"
Under system = Codename: Hammerhead
5.1.1
Build: LMY48I
Is this stock?
Click to expand...
Click to collapse
Not enough information from this to say. The custom kernel you installed is enough to prevent OTA updating.
Wakamatsu said:
Not enough information from this to say. The custom kernel you installed is enough to prevent OTA updating.
Click to expand...
Click to collapse
i can never find a decent post, how can i be sure this is stock rom, without having to flash the stock one?
HIGKILLER said:
i can never find a decent post, how can i be sure this is stock rom, without having to flash the stock one?
Click to expand...
Click to collapse
It would be easy to say if the build didn't match a legit N5 image. If the build info in build.prop isn't informative, look for apps/features that shouldn't be in a stock image, eg. AOSP apps replacing the Google versions. Unfortunately, you do have to have some familiarity with stock Google to be able to spot something that's out of place.
Wakamatsu said:
It would be easy to say if the build didn't match a legit N5 image. If the build info in build.prop isn't informative, look for apps/features that shouldn't be in a stock image, eg. AOSP apps replacing the Google versions. Unfortunately, you do have to have some familiarity with stock Google to be able to spot something that's out of place.
Click to expand...
Click to collapse
thank you sir
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 Sorry for the noobie questions, but I'm about to get my mi mix 3 and this is the first time doing a lot of this stuff so I had a couple of questions. I read a few things on the forum and I see different answers to things so I'm hoping to get some things straightened out, if you could even link an article/post for me to read that'd great too.
So I read that unlocking the bootloader erases all data, which is fine cause I plan to do this first. After unlocking the bootloader and when the Global rom become available, will flashing the rom erase all the data as well?
Is there any risks to having the bootloader unlocked? If so could I lock the bootloader up once I've flashed it with the Global rom?
Thanks!
x1vietnguyen said:
Hi Sorry for the noobie questions, but I'm about to get my mi mix 3 and this is the first time doing a lot of this stuff so I had a couple of questions. I read a few things on the forum and I see different answers to things so I'm hoping to get some things straightened out, if you could even link an article/post for me to read that'd great too.
So I read that unlocking the bootloader erases all data, which is fine cause I plan to do this first. After unlocking the bootloader and when the Global rom become available, will flashing the rom erase all the data as well?
Is there any risks to having the bootloader unlocked? If so could I lock the bootloader up once I've flashed it with the Global rom?
Thanks!
Click to expand...
Click to collapse
If you are on Chinese Rom and want to flash global Rom it will wipe the data.
If your phone comes with Chinese Rom you can't lock bootloader on global Rom
Never had any issues before as long as the Rom has safety net passing. If it doesn't pass you can't use banking apps.
If you lose phone and if someone sees phone is unlocked they can wipe it using fastboot etc
Mackay53 said:
If you are on Chinese Rom and want to flash global Rom it will wipe the data.
If your phone comes with Chinese Rom you can't lock bootloader on global Rom
Never had any issues before as long as the Rom has safety net passing. If it doesn't pass you can't use banking apps.
If you lose phone and if someone sees phone is unlocked they can wipe it using fastboot etc
Click to expand...
Click to collapse
Oh okay so flashing a new Rom would also delete everything. I read that Chinese Roms dont have google frame work and thats why we flash the Global rom, but I've seen people say mix 3 has google frame work so is there really a need to flash to a Global rom when its available?
x1vietnguyen said:
Oh okay so flashing a new Rom would also delete everything. I read that Chinese Roms dont have google frame work and thats why we flash the Global rom, but I've seen people say mix 3 has google frame work so is there really a need to flash to a Global rom when its available?
Click to expand...
Click to collapse
You can get by on the Chinese Rom with no problems.
Only downside for me is some apps have Chinese writing in them but so far that's limited to apps like music/themes/browser/Mi AI, basically anything that requires an Internet connection
The app "Google installer v3" will install Google framework and apps for you. Just remember to go into the app permissions for the contacts app and make sure they are all given otherwise it won't sync.
Other option is to unlock boot and install xiaomi eu rom when it's released
Mackay53 said:
Other option is to unlock boot and install xiaomi eu rom when it's released
Click to expand...
Click to collapse
If it's released. Do we know it will be for sure?
invisiblewave said:
If it's released. Do we know it will be for sure?
Click to expand...
Click to collapse
It's just delayed, it will be released when it's ready.
Maybe today when the downloads are all re-uploaded with fixes
Mackay53 said:
It's just delayed, it will be released when it's ready.
Maybe today when the downloads are all re-uploaded with fixes
Click to expand...
Click to collapse
Be nice to see a non-Chinese version of TWRP too.... that would give me a little more confidence the phone might be worth keeping.
invisiblewave said:
Be nice to see a non-Chinese version of TWRP too.... that would give me a little more confidence the phone might be worth keeping.
Click to expand...
Click to collapse
The phone has only been out for a month, twrp and roms etc take time
Mackay53 said:
The phone has only been out for a month, twrp and roms etc take time
Click to expand...
Click to collapse
Yes, I know, but who will put the time into them now the device is going to be obsolete in a couple of months?
invisiblewave said:
Yes, I know, but who will put the time into them now the device is going to be obsolete in a couple of months?
Click to expand...
Click to collapse
It's not going to be obsolete, just going to be another variant on the market
Mackay53 said:
It's not going to be obsolete, just going to be another variant on the market
Click to expand...
Click to collapse
That's my point, it's not a variant, it's a different chipset, which means different drivers, essentially a completely different device in terms of software support.
invisiblewave said:
That's my point, it's not a variant, it's a different chipset, which means different drivers, essentially a completely different device in terms of software support.
Click to expand...
Click to collapse
And the mix 3 standard edition will still be sold, and will still he supported.
What's the point in buying any phone when you know 6 months down the line it's going to be replaced.
EU rom is now out so weekly updates
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...