Related
I have a US (i535) Verizon S3 that was messed up with the update to 4.4.2. I would like to root it but I cannot connect to wifi or data. Is there any root available that will work on this device?
I found a root for 4.4.2 but it required a data/WiFi connection.
chinook9 said:
I have a US (i535) Verizon S3 that was messed up with the update to 4.4.2. I would like to root it but I cannot connect to wifi or data. Is there any root available that will work on this device?
I found a root for 4.4.2 but it required a data/WiFi connection.
Click to expand...
Click to collapse
So after update to 4.4.2 your wifi/data not working anymore?? If it's the case why don't you odin full 4.4.2 firmware to fix wifi/data issue, then do root with towelroot?
buhohitr said:
So after update to 4.4.2 your wifi/data not working anymore?? If it's the case why don't you odin full 4.4.2 firmware to fix wifi/data issue, then do root with towelroot?
Click to expand...
Click to collapse
Thank you. I will go ahead and do some research to find the needed software and learn how to use odin to do this. I believe I used odin once a few years ago but I have very little experience. Basically an amateur PC guy (old retired) who messes with android on occasion.
buhohitr said:
So after update to 4.4.2 your wifi/data not working anymore?? If it's the case why don't you odin full 4.4.2 firmware to fix wifi/data issue, then do root with towelroot?
Click to expand...
Click to collapse
chinook9 said:
Thank you. I will go ahead and do some research to find the needed software and learn how to use odin to do this. I believe I used odin once a few years ago but I have very little experience. Basically an amateur PC guy (old retired) who messes with android on occasion.
Click to expand...
Click to collapse
I tried to update the 4.4.2 with Odin but all attempts were unsuccessful.
I also tried a CF-Auto-Root but that didn't work either. I wasn't able to find out much about it so I'm not sure I should have expected it to work but it didn't.
Anyone know of any other rooting software I can download on the PC and then transfer to the S3?
Have you tried using "Verizon Wireless Software Utility Application for Android – Samsung" ([[http]] [[;//]] www [[dot]] verizonwireless [[dot]] com/support/devices/knowledge_base.html/80200/) for repairing the update? It works in a similar fashion to manually doing it with Odin. Just keep in mind that the process will completely wipe out the phone and your data will be lost in the process.
Also, you should be able to just download the Towelroot APK from your computer at towelroot dot com and then copy it to your phone either by putting it on the SD card or hooking your phone up via USB. Trouble is that you'll still need to install the APK either by getting an installer app from the Play store or by using ADB (which should work whether the repair fixed your radio or not).
With ADB installed on your computer, you would need the phone hooked up via USB and "USB Debugging" enabled, as well. Go to "Settings >> About Phone", then tap on "Build number" seven times. This will open Developer options. Then, in Developer options, enable "USB debugging". In "Settings > Security", you'll also probably want to enable "Unknown sources", so that you can install stuff from outside of the Play store.
You'll then want to launch ADB by opening a command prompt from the folder in which it resides. In the command prompt, verify ADB sees your phone by entering:
Code:
adb devices
If it shows a device connected, continue along. For the sake of examples, we're going to assume a location for the Towelroot APK at C:\downloads\tr.apk. Given this, to push the install you will want to enter the following in the command prompt:
Code:
adb install C:\downloads\tr.apk
If it returns "SUCCESS", Towelroot is now installed, and it does a nice one-tap root.
This has worked in my experience, but it couldn't hurt to have a second opinion before trying any of this.
ledzilla said:
Have you tried using "Verizon Wireless Software Utility Application for Android – Samsung" ([[http]] [[;//]] www [[dot]] verizonwireless [[dot]] com/support/devices/knowledge_base.html/80200/) for repairing the update? It works in a similar fashion to manually doing it with Odin. Just keep in mind that the process will completely wipe out the phone and your data will be lost in the process.
Also, you should be able to just download the Towelroot APK from your computer at towelroot dot com and then copy it to your phone either by putting it on the SD card or hooking your phone up via USB. Trouble is that you'll still need to install the APK either by getting an installer app from the Play store or by using ADB (which should work whether the repair fixed your radio or not).
With ADB installed on your computer, you would need the phone hooked up via USB and "USB Debugging" enabled, as well. Go to "Settings >> About Phone", then tap on "Build number" seven times. This will open Developer options. Then, in Developer options, enable "USB debugging". In "Settings > Security", you'll also probably want to enable "Unknown sources", so that you can install stuff from outside of the Play store.
You'll then want to launch ADB by opening a command prompt from the folder in which it resides. In the command prompt, verify ADB sees your phone by entering:
Code:
adb devices
If it shows a device connected, continue along. For the sake of examples, we're going to assume a location for the Towelroot APK at C:\downloads\tr.apk. Given this, to push the install you will want to enter the following in the command prompt:
Code:
adb install C:\downloads\tr.apk
If it returns "SUCCESS", Towelroot is now installed, and it does a nice one-tap root.
This has worked in my experience, but it couldn't hurt to have a second opinion before trying any of this.
Click to expand...
Click to collapse
Thank you very much for the response. I will try what you recommend.
chinook9 said:
Thank you very much for the response. I will try what you recommend.
Click to expand...
Click to collapse
I was able to get the towelroot apk on the phone and installed but towelroot requires an internet connection to work and neither wireless or data works on the phone.
I did try the Verizon Software Upgrade Assistant but it indicates that it does not work with my firmware (4.4.2).
I'll keep researching and see what I can find.
chinook9 said:
I was able to get the towelroot apk on the phone and installed but towelroot requires an internet connection to work and neither wireless or data works on the phone.
I did try the Verizon Software Upgrade Assistant but it indicates that it does not work with my firmware (4.4.2).
I'll keep researching and see what I can find.
Click to expand...
Click to collapse
Tell us more about the history of your phone.
1) you have stock 4.3 with root?
2) how did you upgrade and mess-up?
3) I assumed that you have stock recovery?
4) Never flash any custom firmware like CM11?
Thanks,
buhohitr said:
Tell us more about the history of your phone.
1) you have stock 4.3 with root?
2) how did you upgrade and mess-up?
3) I assumed that you have stock recovery?
4) Never flash any custom firmware like CM11?
Thanks,
Click to expand...
Click to collapse
Thank you very much for your reply.
My phone is not rooted and was never rooted with 4.3.
My phone was trashed with the original OTA Verizon update from 4.3 to 4.4. KitKat. I did a phone reset (thinking it would take me back to the original android version) but all it did was empty all my data and settings and still had 4.4.3 with no functioning data connection, wifi, or GPS.
I have never flashed any custom firmware.
I can get into 4.4 Kitkat or download mode.
I tried the Verizon Software Upgrade Assistant but it didn't work. Got a message indicating it wouldn't work with my firmware (4.4)
I also installed the Verizon Software Utility for Android-Samsung but all it does is tell me there is no update for my firmware.
I tried using Odin to root the phone using CF-Auto-Root-d2vzw-d2vzw-schi535.tar.md5 but it didn't work. Not designed for4.4 I think.
I tried using Odin to update with a new install of 4.4 but it didn't work.
I installed and ran Towelroot but it requires internet access.
I looked for a way to get USB internet access but what I found requires a rooted phone.
I will try anything to get it operational but I'd just as soon root it. I have another smart phone so I will just play with this one.
Any help would be appreciated.
It seems like the OTA may mess something up, but nothing out of the norm. I would try a different USB cable and a different USB port on your PC. Also make sure use Odin 3.09.
1) pull the battery then reinstall - make sure the battery is full
2) Boot into recovery and do a factory reset
3) Boot into Odin mode then re flash
Good luck!
buhohitr said:
It seems like the OTA may mess something up, but nothing out of the norm. I would try a different USB cable and a different USB port on your PC. Also make sure use Odin 3.09.
1) pull the battery then reinstall - make sure the battery is full
2) Boot into recovery and do a factory reset
3) Boot into Odin mode then re flash
Good luck!
Click to expand...
Click to collapse
Well buhohitr, I now have 4.4.2 functioning on the S3 and everything is working fine.
It did not go as expected but trying what you recommended, and with some luck, I got there.
I did #1 and #2 successfully but the Odin flash was not successfull.
After the unsuccessfull flash the phone the warning screen came up indicating the software upgrade was unsuccessful and to try the Verizon Software Upgrade Assistant.
I had tried the Verizon Software Upgrade Assistant previously and it had recognized the phone.
I tried it again, however, and everything went swimmingly. It downloaded the update and installed it on the phone.
I expect the factory reset was what enabled the Software Upgrade Assistant to recognize and upgrade the phone.
Thank you very much.
I will probably play with the phone a bit before I root it.
ZTE Z830: As some of you (who have recently broke your high-end devices like me!) know this is a cheap "GoPhone" you might have purchased as a replacement. As some of us know: the phones Hardware isn't bad for a low-end device. All very capable. The problem however; THE DAMN RESTRICTIONS ZTE HAS PUT ON THE PHONE.
Here are the problems in case you don't own a Z830:
No Apps are allowed on the SD-card
The bloatware cannot be uninstalled
Almost no internal memory (ZTE claims "4 Gigs of internal storage" but there is only around 800MB when disabling all unnecessary apps)
Anyways if you are stuck like me and have been suckered into buying this prepackaged paperweight. You most likely have one goal: ROOT IT. Which is the main point of this thread; as all of the other forum posts about this phone seem to be with people who have even less knowledge than I have about rooting. I want to figure out how to root this phone so it can live up to its capabilities.
I'm posting here about the methods I've been trying to root this phone with; so someone who has more knowledge about general rooting and coding then they can chime in and add some info.
First Attempt (FAILED) to Root the Device
ALSO KNOWN AS UPDATE.ZIPThe BREAKTHROUGH Information: I've managed to find the stock recovery from the phone's firmware. By pressing Volume Up + Power I got into the phones menu with various options to "update the firmware" It looks like this:
Android system recovery <
Z830V1 . 0 . 0B14
Volume up/down to move
highlight;
Press power to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
apply update from sdcard
apply update from cache
md5 cache
So I tried to the original rooting method and this is what happened
-- Install /sdcard ...
(Installs about 25%)
Package corrupt.
Installation aborted.
So anyways: I would love some help trying to discover how to root this damn thing. If you own one of these and find some more breakthrough info I would love to know; because I am as well messing with this thing to see if this will ever work.
Just Tried TowelRoot. Doesn't support the z830.
Bump
I didn't want to post a new thread, is there any new information on this front? It doesn't seem like this was a popular enough phone to warrant it's own set of instructions
**************************************
A few of us were successful in finding a perm root. I know the phone has aged a bit now, but it really is a nice cheap spare phone without the bloatware.
The following instructions for the ZMAX worked perfectly but TWRP does not support the touch screen for the z830 so you have to use an OTG mouse to use TWRP. Touch functionality works fine once the entire process is complete. Uninstalling bloatware seems to have to be done with a 3rd party app such as Purify.
https://boycracked.com/2016/04/16/how-to-root-installing-twrp-v3-0-1-recovery-on-zte-zmax-z970/
I have this phone and have been trying various automatic root programs for some time. No luck.
qaz1233 said:
I have this phone and have been trying various automatic root programs for some time. No luck.
Click to expand...
Click to collapse
Yeah it seems like the phone uses some sort of bizarre coding.
........
I try everthing... nothing works....
all apps and PC methods fail...
Does adb work on your device? What are the different modes for your devices? Can you get into the bootloader?
Sent from my Z970 using XDA Free mobile app
TecheTag said:
Does adb work on your device? What are the different modes for your devices? Can you get into the bootloader?
Click to expand...
Click to collapse
Hey, I decided to pitch in as I also have this unfortunate phone. adb does in fact work, but it is crippled. I cannot perform "adb reboot bootloader" as it will simply reboot the phone normally. I tried to boot into the bootloader by pressing volume down+power and was entered into field test mode, as I have come to understand (says FTM on a white rectangle). Volume UP + power does put me in recovery mode, which is cool. Most interestingly, hold UP+DOWN+POWER mounts on my windows machine as ZTE handset diagnostic interface DFU... which apparently is made for flashing firmware with zte's own utility. adb reboot fastboot also just rebooted it normally.
if anyone knows of a useful test i could perform or a could point me towards new strategies i would appreciate it.
Well that sounds promising. It seems like we're breaking new ground here though.
830ingarg said:
Most interestingly, hold UP+DOWN+POWER mounts on my windows machine as ZTE handset diagnostic interface DFU... which apparently is made for flashing firmware with zte's own utility. adb reboot fastboot also just rebooted it normally..
Click to expand...
Click to collapse
Do you think there is something that can be used to flash our own custom firmware on it?
Please someone bump
I have the same phone and it's about worthless without root. Hopefully someone cam figure it out. I would even donate some cash for a solution.
Sort of temporary root achieved with KingRoot
So, I have this goofy phone and I did manage to get something that appears to be root using KingRoot. The PC version didn't work, and neither did TowelRoot or OneClickRoot. Downloading the apk for KingRoot and running it gave me root access, but only until I rebooted the phone. I managed to install SuperSU which allowed me to confirm that I had root. Unfortunately I was not able to uninstall any pre-loaded software while rooted via KingRoot or KingUser. KingRoot acted like it had successfully uninstalled the pre-installed software, but all it uninstalled were the updates. I didn't get a list of software when I tried to uninstall software via KingUser.
So we can boot into Recovery, and can get temporary root. Any ideas on how to get farther with this crippled phone?
pippinstrano said:
So, I have this goofy phone and I did manage to get something that appears to be root using KingRoot. The PC version didn't work, and neither did TowelRoot or OneClickRoot. Downloading the apk for KingRoot and running it gave me root access, but only until I rebooted the phone. I managed to install SuperSU which allowed me to confirm that I had root. Unfortunately I was not able to uninstall any pre-loaded software while rooted via KingRoot or KingUser. KingRoot acted like it had successfully uninstalled the pre-installed software, but all it uninstalled were the updates. I didn't get a list of software when I tried to uninstall software via KingUser.
So we can boot into Recovery, and can get temporary root. Any ideas on how to get farther with this crippled phone?
Click to expand...
Click to collapse
Did you actually gain any space when you uninstalled items with that temporary root? I am able to uninstall updates on default apps even without root. I had one time with KingoApp where it claimed to be rooted, but I lost it with reboot and haven't gotten it back. Very frustrating. Wish I had avoided the reboot.
nothing works
I too got temporary root with kingroot, got to ambitious with uninstalling system apps and got into a force close loop. A factory reset from the stock recovery got me back in business. I didn't think that a factory reset was supposed to recover apps deleted while in root access. Also kingroot didn't work the first time for me, had to try several times, that was with latest apk, 4.1 I think.
Has anyone contacted zte about a bootloader unlock code? I know most phones it is necessary to unlock the bootloader to gain permanent root access. Plus then maybe we could get a custom recovery. I tried contacting them with no luck.
Talked to zte today, won't give unlock code since it will void warranty. Told them I didn't care about warranty since phone is worthless as is, no luck.
It could work the method used in the ZTE Z970? http://forum.xda-developers.com/general/help/zte-zmax-rooted-kingroot-t3110178
I was able to get temp root with Kingroot but doesn't stick after reboot. Today I got root to stick by using Flashify to flash superuser zip (http://download.chainfire.eu/supersu). I then deleted Kingroot apps. I was able to uninstall some ATT apps but not google apps. I tried SD Card Fix but didn't work and still can't change/mount r/w in root explorer.
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
val3nteen said:
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
Click to expand...
Click to collapse
Start here, http://forum.xda-developers.com/showthread.php?p=53439068. I'd return to stock and start all over, it will wipe your device, see the return to stock thread linked there. Then don't be lazy and read some more in the thread I linked you to. The n5 is one of the easiest devices to work with and you don't need kingroot, tool kits and junk like that
Sent from my Nexus 5 using XDA Free mobile app
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
deelan_chan said:
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
Click to expand...
Click to collapse
Thanks, but that is not possible, as I have not enabled USB debugging before bootloop. I need to unlock the bootloader (wipe) to install TWRP and backup data.
Can you get into fastboot mode? You can flash twrp from there no USB debugging needed
Sent from my Nexus 5 using Tapatalk
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
wangdaning said:
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
Click to expand...
Click to collapse
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
val3nteen said:
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
Click to expand...
Click to collapse
But it is so fun to use fastboot. I remember almost dunking my wife's G2 until I got it to fastboot. Pain in the butt, but the command prompt does not lie
So, I finally got my phone (SM-J320FN) rooted, thanks to info and downloads on this forum.
But now I have some questions, to which I haven't found the answers to anywhere else on the web.
1. To root, I followed instructions that told me to switch-on OEM unlock and USB debugging. However, there was no mention about turning them off again after root. Should they be on, or off?
2. Part of my rooting process involved installing/flashing TWRP. I did read that TWRP can be removed after root. What are the advantages/disadvantages of leaving or removing?
3. Now my phone is rooted, what is the best app/way to prevent it becoming unrooted by updates?
That's all for now, thanks.
SGJ3 said:
So, I finally got my phone (SM-J320FN) rooted, thanks to info and downloads on this forum.
But now I have some questions, to which I haven't found the answers to anywhere else on the web.
1. To root, I followed instructions that told me to switch-on OEM unlock and USB debugging. However, there was no mention about turning them off again after root. Should they be on, or off?
2. Part of my rooting process involved installing/flashing TWRP. I did read that TWRP can be removed after root. What are the advantages/disadvantages of leaving or removing?
3. Now my phone is rooted, what is the best app/way to prevent it becoming unrooted by updates?
That's all for now, thanks.
Click to expand...
Click to collapse
It's better to let them on.
You can remove the TWRP recovery by flashing stock recovery. But TWRP can backup your whole android partitions (nandroid backup) that can restore your android if anything goes wrong.
TWRP can flash custom roms, mods, mount partitions, and many more. So, it's better to you have TWRP(custom recovery) installed.
If you are using SuperSU superuser app then in option you found OTA survival that prevent root from OTA updates.
I think you can't get OTA updates because you are rooted. If you get OTA updates and applied on rooted android then it chances of brick your android.
Hi every one. First sorry for bad grammar I am not so good at english. Now to the problem at hand.
Jester day I bought a smj320fn and realise it is not what I paid for, so I tried to root witk KingoRoot and fail. Then I realised there is a "bootlock" witch prevents root (I think it does that).
So I tried ODIN and installed a custom FMW and it worked, allso I instaled a custom twrp and boot win.rar file. and there is the problem.
Every time I hold the power buton the samsung logo apears for 5 seconds and then goes black. It wont take any commands. I tride the recover meny to open, no it wont, but I can restars it to boot again and fails every time.
I tried to do it from a youtube tutorial and maby I know what I did wrong. I Instaled a Sm-j320h boot on my smj320fn so I think thats the problem. Any whay how do I fix this. All and any solution are good.
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.