Related
several weeks ago I used the Unrevoked method to root my phone. Now before you start flaming, I have a reasonable excuse.
I got called in for jury duty and needed to use my phone as a hotspot so I could get some work done via laptop during breaks/lunch.
So, a couple of weeks later and I want to root the proper way. What steps do I need to do at this point being rooted with Unrevoked?
Links, name calling, or any help appreciated.
I rooted my phone with unrevoked3! I thought it was a proper root.
Why would you need to root again/what's the point in only half rooting a phone with this unrevoked method?
Not sure if it's only half a root, but I would like to do it the long way and "get to know" my phone even more whom I've had since launch ^_^
Come on guys, help me out!
No one can get me started in the right direction? :\
I think I found what I needed ^_^
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
why not just use ADB and boot the phone into bootloader (fastboot), connect phone to computer using USB cable, open up fastboot, type in
fastboot oem unlock and root the phone? thats the quuickest way i know of rooting.
What's the nerd in that? ;D
I've looked at a few threads but they seem to involve flashing before rooting...
Is there a way to root without flashing? if so... how?
Thanks
You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.
unremarked said:
You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.
Click to expand...
Click to collapse
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???
sinatosk said:
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???
Click to expand...
Click to collapse
The bootloader is built into the phone, there's nothing to flash for that.
Think of it as a pre-recovery. Fastboot is a feature in the Android SDK which works with the bootloader to flash things such as recovery, or boot.imgs prior to actually having a custom recovery/root. However, it does require the bootloader to be unlocked which is where the fastboot oem unlock command comes in. Once you have a custom recovery on your phone, you flash things like normal.
From the stickied FAQ:
unremarked said:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot (aka the bootloader) mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
Click to expand...
Click to collapse
The first step helps you set up the SDK and drivers. The second step will tell you how to root, install recovery, and flash Superuser.
Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?
xspyda said:
Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?
Click to expand...
Click to collapse
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.
Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.
unremarked said:
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.
Click to expand...
Click to collapse
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...
xspyda said:
Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.
Click to expand...
Click to collapse
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
sinatosk said:
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...
Click to expand...
Click to collapse
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).
unremarked said:
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).
Click to expand...
Click to collapse
well yeah I know about ADB... just nothing about rooting
Hmm the phone shipped with 2.3 and I have yet to update but as 2.3.1 is an official update I can't see that being reason not to accept a return.
Hello, this is my first post on XDA forums so take it easy on me. Recently I've started taking interest in rooting my Xperia Z5. However I don't really know much at all about Linux, and I've never rooted an android device before. I am actually a coder, in fact I'm using a laptop with a HEAVILY modded version of Win10, and with several apps of my own. I've only recently, about a few months ago, bought a decent android phone. I got the Xperia Z5 off eBay for a good price, brand new for a couple hundred bucks. I'm interested in slowly learning basic coding and hacking on android, so I figured I'd go with the first major step and getting it rooted so I can actually mod the thing. The operating system is nice, doesn't have much bloatware, but I'd like to flash a new ROM on it. I've dug around a bit, and I've seen a few root and flash methods, but I really don't have any idea which one is trusted, or which would be the most stable option. I figured my best option would be to signup here, and ask for some advice. I saw ROMX here on the forums, and it looked very promising. But since I'm new to all this, I thought it would be wise for me to ask for advice on where to start what what would be a good rom to flash. I have the E6603 Model, Android 6.0.1, with the April 1, 2016 security patch. And yes, I do fully understand the risks and dangers as well as security concerns of rooting, and flashing. But to be honest, I probably do far more dangerous things on a weekly basis. I thank you all for your time, any help is appreciated.
spynathan said:
Hello, this is my first post on XDA forums so take it easy on me. Recently I've started taking interest in rooting my Xperia Z5. However I don't really know much at all about Linux, and I've never rooted an android device before. I am actually a coder, in fact I'm using a laptop with a HEAVILY modded version of Win10, and with several apps of my own. I've only recently, about a few months ago, bought a decent android phone. I got the Xperia Z5 off eBay for a good price, brand new for a couple hundred bucks. I'm interested in slowly learning basic coding and hacking on android, so I figured I'd go with the first major step and getting it rooted so I can actually mod the thing. The operating system is nice, doesn't have much bloatware, but I'd like to flash a new ROM on it. I've dug around a bit, and I've seen a few root and flash methods, but I really don't have any idea which one is trusted, or which would be the most stable option. I figured my best option would be to signup here, and ask for some advice. I saw ROMX here on the forums, and it looked very promising. But since I'm new to all this, I thought it would be wise for me to ask for advice on where to start what what would be a good rom to flash. I have the E6603 Model, Android 6.0.1, with the April 1, 2016 security patch. And yes, I do fully understand the risks and dangers as well as security concerns of rooting, and flashing. But to be honest, I probably do far more dangerous things on a weekly basis. I thank you all for your time, any help is appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
there is this which i followed to root my Z5 but with marshamall you do have to have a unlocked bootloader so you can use systemless root, it isnt neccisary to downgrade and backup your DRM but it is advised since sony doesnt seemingly like wanting to repair phones with missing DRM
basic how to:
- Download flashtool and a FTF of your choice
- use flashtool the extract the kernel.sin using tools > sin extractor (you will have to open the FTF file in winrar or something like to copy it)
~ you should get a kernel.elf when extracted
you can then use rootkernel to repack the kernel with a recovery menu like twrp and also disable some system verification stuff that will prevent things from working or the phone booting
this is when you need a unlocked bootloader
- from there you can flash your kernel and boot the device and flash superSU systemless (from the recovery menu )unless you havent downloaded that already
~ you can get to the recovery menu by pressing volume up while the yellow LED shows up on the bootsplash
i may have missed some stuff but that guide I linked has everything i explained here ^ this above is how ive rooted my phone and re-rooted when needed
Envious_Data said:
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
there is this which i followed to root my Z5 but with marshamall you do have to have a unlocked bootloader so you can use systemless root, it isnt neccisary to downgrade and backup your DRM but it is advised since sony doesnt seemingly like wanting to repair phones with missing DRM
basic how to:
- Download flashtool and a FTF of your choice
- use flashtool the extract the kernel.sin using tools > sin extractor (you will have to open the FTF file in winrar or something like to copy it)
~ you should get a kernel.elf when extracted
you can then use rootkernel to repack the kernel with a recovery menu like twrp and also disable some system verification stuff that will prevent things from working or the phone booting
this is when you need a unlocked bootloader
- from there you can flash your kernel and boot the device and flash superSU systemless (from the recovery menu )unless you havent downloaded that already
~ you can get to the recovery menu by pressing volume up while the yellow LED shows up on the bootsplash
i may have missed some stuff but that guide I linked has everything i explained here ^ this above is how ive rooted my phone and re-rooted when needed
Click to expand...
Click to collapse
Awesome thanks! I'll try it first thing tomorrow after work.
Ok so I've gotten everything done, backed up my drm unlocked the bootloader, and what not. Got to the last bit and I can't seem to get fastboot to work, it just says waiting for device. I've tried reinstalling all the drivers a few times, but nothing worked. Flashtool recognized the device, just couldn't get fastboot to recognize it. I'm running windows 10, I've made sure all the drivers are there but still no go. Any help would be greatly appreciated, I'm kinda stuck atm. EDIT, I found a fix for my case. Even though the drivers were installed, for some reason they weren't being read. Anyway all working now, thanks again.
spynathan said:
Ok so I've gotten everything done, backed up my drm unlocked the bootloader, and what not. Got to the last bit and I can't seem to get fastboot to work, it just says waiting for device. I've tried reinstalling all the drivers a few times, but nothing worked. Flashtool recognized the device, just couldn't get fastboot to recognize it. I'm running windows 10, I've made sure all the drivers are there but still no go. Any help would be greatly appreciated, I'm kinda stuck atm. EDIT, I found a fix for my case. Even though the drivers were installed, for some reason they weren't being read. Anyway all working now, thanks again.
Click to expand...
Click to collapse
atleast on windows 10 i found that i had to disable driver signature verifacation and sometimes i had to run command prompt in admin
I thought everything was fixable with flashtool as long as the bootloader is unlocked.. never been so wrong in my life.
Bought a used xperia z3 6166 t mobile version without knowing its support for custom roms (smh).. steps i did:
1)installed recovery.
2) rooted the device
3) unlocked the bootloader (successfully)
4) i thought i was ready to install custom roms like niaboc79's existenz which consequently I did, the phone did boot after that but was connecting in fastboot and flashboot so
5)using flashtool flash stock latest d6616 firmware and was back to step 1.
read somewhere that I could flash d6603 firmware because both phones have same specs so
6)flash d6603 firmware in order to get existenz working
7)flashtool gave some errors and failed
8)used fastboot to flash kernel
the device stops responding all of a sudden..
9) kept on charge for hours, still got nothing , no vibration, no lights , no hard rest via combination of buttons , nothing by pressing the yellow button inside the flap..
10) pc shows usb not recongnized after a couple of seconds of connecting ..
its been beyond frustrating going through the internet, scrolling through threads after thread but no avail.. people say at least the phone should be recognized by pc in any form other than usb not recongnized .. so I went to a local smartphone repair shop and gave it to him but he isnt too hopeful either.. I already have xperia z1c which i messed with so many times but it always responds to the flashtool.. but buying xperia z3 is literally the worst smartphone experience of my life!
is there any way to make this dead brick work again.. any unorthodox means to rewrite boot to make it jump start? any help is appreciated!
hash054 said:
I thought everything was fixable with flashtool as long as the bootloader is unlocked.. never been so wrong in my life.
Bought a used xperia z3 6166 t mobile version without knowing its support for custom roms (smh).. steps i did:
1)installed recovery.
2) rooted the device
3) unlocked the bootloader (successfully)
4) i thought i was ready to install custom roms like niaboc79's existenz which consequently I did, the phone did boot after that but was connecting in fastboot and flashboot so
5)using flashtool flash stock latest d6616 firmware and was back to step 1.
read somewhere that I could flash d6603 firmware because both phones have same specs so
6)flash d6603 firmware in order to get existenz working
7)flashtool gave some errors and failed
8)used fastboot to flash kernel
the device stops responding all of a sudden..
9) kept on charge for hours, still got nothing , no vibration, no lights , no hard rest via combination of buttons , nothing by pressing the yellow button inside the flap..
10) pc shows usb not recongnized after a couple of seconds of connecting ..
its been beyond frustrating going through the internet, scrolling through threads after thread but no avail.. people say at least the phone should be recognized by pc in any form other than usb not recongnized .. so I went to a local smartphone repair shop and gave it to him but he isnt too hopeful either.. I already have xperia z1c which i messed with so many times but it always responds to the flashtool.. but buying xperia z3 is literally the worst smartphone experience of my life!
is there any way to make this dead brick work again.. any unorthodox means to rewrite boot to make it jump start? any help is appreciated!
Click to expand...
Click to collapse
My sincerest apologize for your misfortune. I have not yet encountered this degree of issues. I am going to keep my bootloader locked I do believe. Just got this phone myself and I really wish I could help you. The TMO version of this phone is definitely the worst one I think given the lack of software support.
However I was wondering what method you followed to install recovery and if you attempted to install exposed.
arikdahn said:
My sincerest apologize for your misfortune. I have not yet encountered this degree of issues. I am going to keep my bootloader locked I do believe. Just got this phone myself and I really wish I could help you. The TMO version of this phone is definitely the worst one I think given the lack of software support.
However I was wondering what method you followed to install recovery and if you attempted to install exposed.
Click to expand...
Click to collapse
used the XZdualrecovery zip for locked bootloader.. it was fairly simple , did it twice without any problems! then used recovery to install superuser and update it binaries and the phone was rooted.. I didnt installed xposed because i want to upgrade from lollipop.. that I couldnt do! :crying:
May this thread be a warning to people who themselves arent developers but have a little knowledge about custom roms to do their homework before diving into things they cant get out of..
hash054 said:
used the XZdualrecovery zip for locked bootloader.. it was fairly simple , did it twice without any problems! then used recovery to install superuser and update it binaries and the phone was rooted.. I didnt installed xposed because i want to upgrade from lollipop.. that I couldnt do! :crying:
May this thread be a warning to people who themselves arent developers but have a little knowledge about custom roms to do their homework before diving into things they cant get out of..
Click to expand...
Click to collapse
I will second the f*** out of this, but I will also add that recovery TYPICALLY protects you from a ton of heartache. Not this time huh? Well, I cannot get Kingroot off my frickin' phone. I think it may have been commandeered by China. The uninstall always fails. So I may be in the same boat as you. Not sure if I can install recovery with it on there or not, but I do know it and SuperSU do not play nicely. I am debating which would be more risky, factory resetting a rooted phone to get rid of kingroot, or attempting to install recovery with this scary AF root manager. What a pain in the ass.
So this is the procedure you followed?
https://forum.xda-developers.com/showpost.php?p=60507399&postcount=171
arikdahn said:
I will second the f*** out of this, but I will also add that recovery TYPICALLY protects you from a ton of heartache. Not this time huh? Well, I cannot get Kingroot off my frickin' phone. I think it may have been commandeered by China. The uninstall always fails. So I may be in the same boat as you. Not sure if I can install recovery with it on there or not, but I do know it and SuperSU do not play nicely. I am debating which would be more risky, factory resetting a rooted phone to get rid of kingroot, or attempting to install recovery with this scary AF root manager. What a pain in the ass.
So this is the procedure you followed?
https://forum.xda-developers.com/showpost.php?p=60507399&postcount=171
Click to expand...
Click to collapse
No thats the rooting method.. I just simply flashed the recovery from http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 and just installed superuser and updated the binaries..
I did also have a problem with kingroot.. you can download the official ftf firmware for d6616 and just flash it in flashboot through flashtool.. its the only way to get rid of kingroot in my experience .. but I would give you caution to flash nothing else except official firmware through flashtool.. and do it only if you know how to handle it.. as far my experience is concerned, I did get rid of the kingroot this way not once but twice without problem .. its the stuff that followed bricked the phone.. also my bootloader was unlockable so it might have made a difference..maybe
hash054 said:
No thats the rooting method.. I just simply flashed the recovery from http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 and just installed superuser and updated the binaries..
I did also have a problem with kingroot.. you can download the official ftf firmware for d6616 and just flash it in flashboot through flashtool.. its the only way to get rid of kingroot in my experience .. but I would give you caution to flash nothing else except official firmware through flashtool.. and do it only if you know how to handle it.. as far my experience is concerned, I did get rid of the kingroot this way not once but twice without problem .. its the stuff that followed bricked the phone.. also my bootloader was unlockable so it might have made a difference..maybe
Click to expand...
Click to collapse
Well I guess I'll be doing that then. Thanks. So how do you flash that file without a recovery?
I do not know how to handle flash tool since I have only heard of it and never used it. It appears I'll be using it to get rid of kingroot. How does one learn how to handle it so's one doesn't go and mess anything up?
My bootloader is also unlockable but I don't wanna screw with all the things that unlocking it does to the phone so I'm leaving it alone. I like those features
Also did you ever try to remove bloat on the stock ROM? Everything I remove via titanium backup just reinstalls immediately after removal.
Sorry for all the questions instead of answers for you. You are one of the few still messing with this device and I appreciate all your help very much. All of the info on this forum is mostly applicable to when the phone came out. This means almost all of it only applies to android 4.4 or it doesn't apply to the T-Mobile variant b/c T-Mobile was less popular when this phone was a flagship and uses Wifi text/calling which requires special planning. That and the fact that the threads are several hundred pages long makes following along impossible and makes this site all but useless for these phones now.
Hi, I've recently bought a Google Pixel 7 Pro, and I've been trying nonstop, in vain, to install GrapheneOS. So please give me a detailed and ELI5 step by step guide for me.
Anyways, spiel out of the way, I've been trying everything to make it work and I've always encountered a problem, and the amount of bookmarked tabs I had became just unreal, so I decided to just start from scratch and make this post so I know exactly what to do when I run into whatever exception I'm gonna get.
I'm a pretty tech-smart dude, I know my way around a computer (i.e. mess around with the BIOS and know what I'm doing), and I'm pretty knowledgeable on Android phones (mostly software), though I don't really know how to effectively root or "flash" or whatever that is (I know what flashing is, I don't know how to do it). I've got a computer, a connection, knowledge, time and I'll check up on this thread pretty often.
So please help me install GrapheneOS. I want the most basic step by step guide, and to be answered when I run into an error, cuz every way I've tried ended up in a tangled spaghetti of errors and retries.
Thank you very much.
(Also YES, I have developer options, turned on OEM unlocking and USB debugging, the latest version of adb, I think.)
(No, actually, at this point, I've got three different versions; r16.0.1, r33.0.3, r34.0.3)
(I also disabled auto updates, because I'm very wary, but if I HAVE to update to make it work, please tell me)
INFO:
Pixel 7 Pro
Android 13
128GB
12GB RAM
and I don't know what else, ask me if you need it.
You should ask in grapheneOS channel
/Use this tool to unlock https://forum.xda-developers.com/t/pixelflasher-for-google-pixel-7-pro-support-thread.4505287/
Is OEM unlocking enabled in developer settings? Bootloader unlocked?
Easy peasy
GrapheneOS web installer
Web-based installer for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
bobnot said:
Is OEM unlocking enabled in developer settings? Bootloader unlocked?
Easy peasy
GrapheneOS web installer
Web-based installer for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
Click to expand...
Click to collapse
Yeah, thing is; I tried both the Web and CLI install. On the Web install, the "unlock bootloader" button showed me an empty menu, i.e. it didn't recognize my device. On the CLI install, it's asking me to use Linux, which I can, but held off on, because I didn't want to go through the trouble of changing the bootloader (on pc) from grub to the previous one. Anyways, I tried something like "fastboot flashing unlock", or anything that containted "fastboot", "flash", and "unlock", but all I got was a "<waiting for device>" message and it didn't budge for almost 10 minutes. Maybe I didn't wait long enough but when I think about how GrapheneOS's Web install couldn't detect my device, it made me think the fastboot one didn't either, and maybe it's something about the USB port.
Thanks though.
Another thing I should mention is that I'm not having too much trouble understanding the flashing part. I know it works just like a bootable USB for a PC. I'm mostly having trouble unlocking the bootloader, so I essentially want to make a flowchart for all possible solutions and whatever problem I encounted, using this thread. Thank you.
I have finally unlocked the bootloader, and I am preparing to flash the GrapheneOS image (cheetah-factory-2023061402.zip), although I have a question.
If I wish to use apps like Mixplorer and SD Maid, both of which require root for more advanced uses (in-depth cleaning, etc., also I'm smart enough to know what I shouldn't be touching), how do I proceed? Because from what I've read, I can't have both GrapheneOS and root the device at the same time. Yes, I know, big gaping security breach, but I don't require that level of secure. I only want to get rid of google, AND have root permissions.
Thank you very much.
Everything worked. Thanks a lot. If there ever is a way to have root permissions on Graphene, please tell me. Thank you very much.
If you just want to get rid of Google and don't require that level of security and want root do lineage without Gapps and do magisk.
Fastboot drivers can be a bit tricky glad you got that figured out.
hypomass said:
I have finally unlocked the bootloader, and I am preparing to flash the GrapheneOS image (cheetah-factory-2023061402.zip), although I have a question.
If I wish to use apps like Mixplorer and SD Maid, both of which require root for more advanced uses (in-depth cleaning, etc., also I'm smart enough to know what I shouldn't be touching), how do I proceed? Because from what I've read, I can't have both GrapheneOS and root the device at the same time. Yes, I know, big gaping security breach, but I don't require that level of secure. I only want to get rid of google, AND have root permissions.
Thank you very much.
Click to expand...
Click to collapse
I think what you read was referring to not being about to run GrapheneOS + root with a locked bootloader. Which actually you can, but it's a more complicated process.
With an unlocked bootloader tho you root the same way you would with any other rom. Patch init_boot.img (can find it in cheetah-factory-2023061402.zip) with Magisk, flash in fastboot:
Code:
fastboot flash init_boot init_boot_patched.img
Edit:
But if your goal is to deGoogle, @bobnot's comment is valid. Some custom roms have versions without any Google apps, like Lineage or RisingOS-AOSP
hypomass said:
Yeah, thing is; I tried both the Web and CLI install. On the Web install, the "unlock bootloader" button showed me an empty menu, i.e. it didn't recognize my device. On the CLI install, it's asking me to use Linux, which I can, but held off on, because I didn't want to go through the trouble of changing the bootloader (on pc) from grub to the previous one. Anyways, I tried something like "fastboot flashing unlock", or anything that containted "fastboot", "flash", and "unlock", but all I got was a "<waiting for device>" message and it didn't budge for almost 10 minutes. Maybe I didn't wait long enough but when I think about how GrapheneOS's Web install couldn't detect my device, it made me think the fastboot one didn't either, and maybe it's something about the USB port.
Thanks though.
Click to expand...
Click to collapse
I must agree that the CLI instructions from the GrapheneOS website might be clearer. It took me a couple of reads to understand that some sections only apply when running on Linux or Mac. I.e. the standalone platform tools section, flashing as non-root, connecting the phone... Some things only apply to one specific OS.
Glad you've been able to complete installation!
That being said, as @bobnot and @chrisz5z have mentioned: while it's possible to root GrapheneOS (look here), its primary aim is security -- rooting defeats that purpose. You might feel more like home with other ROMs if the main thing you're looking for is to deGoogle.