I have unlocked my bootloader, I have gone through the process of installing TWRP RC1, I have also installed SU 2.79 as guides have shown to do. I have also installed adaway after rooting, as well as titanium backup.
What is left to do now? I have read that if I stay on stock but rooted, when a security update comes out next month and I take it, my device turns into brickmode. I don't intend to stay on stock, I am taking the time to learn all the ins and outs of each rom that exists currently and trying to make a decision which one I like best, and especially what kind of challenging process exists for flashing the rom as well as putting TWRP back on then SU, and the confusing part about doing the vendor image. So yea, still learning. The last time I rooted and flashed anything was LGG3 days, so it's a learning curve again.
Am I supposed to be using a flash drive for anything? Or is that not needed if following the installation process for whatever rom is out there.
Thanks in advance, everyone has been very helpful so far.
There is no need for a flash drive. You can easily disable OTA on stock, and there is no need for a custom rom. In fact, I am rooted on stock. Also, the OTA should not be able to go through while rooted but I have seen myself that it does work surprisingly. My guess is this is because of the dual partitions, but no, you will not get bricked if you accept an OTA. The worst that would happen is that you would lose root. I'm guessing this is due to the dual slots. The OTA overwrites the other slot and swaps it on reboot. You should be able to just get in again but without root.
And if it does fail you can download the full OTA from google and install it with TWRP or adb install it.
Turn off updates in dev options. A couple of people have gotten hit with big data bills from it downloading over and over.
I'm unlocked but not rooted. I installed Franko kernel but need to be rooted to use his app. I'm trying to figure out root yet stay stock for now.
Sent from my Pixel XL using Tapatalk
b4u2 said:
I'm unlocked but not rooted. I installed Franko kernel but need to be rooted to use his app. I'm trying to figure out root yet stay stock for now.
Click to expand...
Click to collapse
So you want to root it now so you can use his app? Second to the last post in the thread below.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
TonikJDK said:
So you want to root it now so you can use his app? Second to the last post in the thread below.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
Click to expand...
Click to collapse
Yes and thank you very much!
Related
Sorry if this question has been asked before, but i could not find any.
So i got the Nexus beast yesterday, and it's already blazing me off with it's greatness. But i got a few problems though:
1. I got the jakjuxw, not the jakju, will i get the same updates as the jakju OTA, but only a week later or so?
2. I did not root the phone before starting using it, but i regret that now. Is there any way i can root it and NOT lose all of my apps and data? I have spent so many hours to customize this device and i dont want to start all over (yes i know about app backup's, but they are slow)
3. If i root but stay with the stock rom, will i still be getting the original OTA updates or does i have to flash the roms manually and wipe the phone every time?
I'd appreciate it if anyone could answer all the questions =)
Baguett said:
Sorry if this question has been asked before, but i could not find any.
So i got the Nexus beast yesterday, and it's already blazing me off with it's greatness. But i got a few problems though:
1. I got the jakjuxw, not the jakju, will i get the same updates as the jakju OTA, but only a week later or so?
Click to expand...
Click to collapse
Not sure about this, it probably depends on what they want to release. I don't think there's any kind of guarantee they'll get the same updates, but there's also probably no reason why they wouldn't.
2. I did not root the phone before starting using it, but i regret that now. Is there any way i can root it and NOT lose all of my apps and data? I have spent so many hours to customize this device and i dont want to start all over (yes i know about app backup's, but they are slow)
Click to expand...
Click to collapse
You need to unlock the bootloader to root, and unlocking the bootloader wipes the device. Sorry. Someday an exploit might be found for ICS that allows you to root without unlocking.
3. If i root but stay with the stock rom, will i still be getting the original OTA updates or does i have to flash the roms manually and wipe the phone every time?
Click to expand...
Click to collapse
If you keep stock recovery, you'll still get OTA updates when rooted. If you use custom recovery like ClockworkMod, you'll have to do them manually (but you won't need to wipe). In both cases, applying the update will probably cause you to lose root and you'll have to re-root. This is easy if you've unlocked the bootloader.
If you root by using some future exploit, you might find that the update you just installed removed root and closed the hole that allowed you to gain it without unlocking the bootloader, and now you're left stuck without root. I'd say just unlock the bootloader now and be done with it. It'll be a pain, but then you don't need to worry about it again.
phazerorg said:
If you keep stock recovery, you'll still get OTA updates when rooted. If you use custom recovery like ClockworkMod, you'll have to do them manually (but you won't need to wipe). In both cases, applying the update will probably cause you to lose root and you'll have to re-root. This is easy if you've unlocked the bootloader.
Click to expand...
Click to collapse
ok thanks
Just unlocked it and rooted it, but i think im gonna install the official google 4.0.2 rom, i wil get the OTA updates then too right?
edit: how am i able to flash a rom without CWM? Also do i really not need to wipe my phone if i use CWM? i had to do it on my Desire.
Baguett said:
ok thanks
Just unlocked it and rooted it, but i think im gonna install the official google 4.0.2 rom, i wil get the OTA updates then too right?
Click to expand...
Click to collapse
Yes, but the updates will probably unroot you. You should be able to just re-root after. If using CWM you can probably flash superuser right after flashing the update and not lose root at all. This is what I always did with my Nexus One when I still had the rooted stock ROM.
edit: how am i able to flash a rom without CWM?
Click to expand...
Click to collapse
If the ROM comes as images (like the Google factory images) you can flash with fastboot. The Google ones come with a script that uses fastboot to do it for you.
Also do i really not need to wipe my phone if i use CWM? i had to do it on my Desire.
Click to expand...
Click to collapse
I meant installing updates here... you don't usually need to wipe if you are installing updates to your current ROM, such as OTA updates to the stock ROM. You need to wipe if you're changing ROMs. It's probably no different than your Desire.
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Currently I'm at v4.3 (touchwiz) and haven't done the latest OTA yet (presumably it's v4.4.2). It'd be best to do the OTA update and then root, right? Reading the earlier post, it
appears this method works for v4.4...
While posting, also is it possible to downgrade back to v4.3 from v4.4? Not that I'm planning on it, but have read both yes and no on doing it and just wondered.
Thanks in advance and do advise if there's anything I should watch out for while doing this!!
wha2do said:
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Currently I'm at v4.3 (touchwiz) and haven't done the latest OTA yet (presumably it's v4.4.2). It'd be best to do the OTA update and then root, right? Reading the earlier post, it
appears this method works for v4.4...
While posting, also is it possible to downgrade back to v4.3 from v4.4? Not that I'm planning on it, but have read both yes and no on doing it and just wondered.
Thanks in advance and do advise if there's anything I should watch out for while doing this!!
Click to expand...
Click to collapse
1) If you flash twrp then you can't do OTA any more
2) The root instruction would work but will trip the Knox and void warranty.
3) Not possible to downgrade back to 4.3
4) if you not use twrp but reflash stock recovery image then OTA would work but will wipe out root if you take the OTA upgrade what ever that maybe 4.4.3?
wha2do said:
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Click to expand...
Click to collapse
I used these full instructions for Kit-Kat: http://forum.xda-developers.com/showthread.php?t=2719750
One step in that is the CF-autoroot, but there are other steps as well. I just ignored the "To Flash New Update" part, but maybe you need it. I was already on the latest OTA before I started. Trips knox but I'm sure you knew that.
buhohitr said:
1) If you flash twrp then you can't do OTA any more
2) The root instruction would work but will trip the Knox and void warranty.
3) Not possible to downgrade back to 4.3
4) if you not use twrp but reflash stock recovery image then OTA would work but will wipe out root if you take the OTA upgrade what ever that maybe 4.4.3?
Click to expand...
Click to collapse
1) That's why I figured best to do the OTA first - just had other devices that didn't have root methods for the newest update & wanted to thought best to ask first!
2) I'm out of warranty (due to drop and repaired screen) so warranty is of no issue...but thanks for the warning
3) Thought that to be the case, but again hearing it may be possible and also can't. Don't foresee doing it, but was curious...
4) Plan on flashing the latest (CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5) via odin, reboot, flash twrp v2.6.x as I hear 2.7.x may have a few issues. Only problems I've read are potential with Super SU - not sure if it's part of the root flash, needs to be flashed
separately, or just dl'd from Google Play Store? Guess will just flash root, see if app is there, if not try Play Store. If not, then go back and find the flashable SU dl.
Thanks!
deV14nt said:
I used these full instructions for Kit-Kat: http://forum.xda-developers.com/showthread.php?t=2719750
One step in that is the CF-autoroot, but there are other steps as well. I just ignored the "To Flash New Update" part, but maybe you need it. I was already on the latest OTA before I started. Trips knox but I'm sure you knew that.
Click to expand...
Click to collapse
Thanks! Yep, not concerned about warranty at this point... And figure will do the OTA and then root...
Actually latest posts appear to show some issues with SU when using CF-autoroot (maybe due to them being on kitkat?). Appears flashing CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 does the trick. Sounding like it's part
of the flash, and can then just flash twrp (figuring be safe with v2.6.x for now).
If not reading this right, anyone feel free to correct me before I "jump", lol!
wha2do said:
Thanks! Yep, not concerned about warranty at this point... And figure will do the OTA and then root...
Actually latest posts appear to show some issues with SU when using CF-autoroot (maybe due to them being on kitkat?). Appears flashing CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 does the trick. Sounding like it's part
of the flash, and can then just flash twrp (figuring be safe with v2.6.x for now).
If not reading this right, anyone feel free to correct me before I "jump", lol!
Click to expand...
Click to collapse
Su is fine with me after cf root.
In my signature is a guide to rooting with kitkat (second post)
Follow that and you'll be good : good:
Sent from my Nexus 4 using Tapatalk
wha2do said:
1) That's why I figured best to do the OTA first - just had other devices that didn't have root methods for the newest update & wanted to thought best to ask first!
2) I'm out of warranty (due to drop and repaired screen) so warranty is of no issue...but thanks for the warning
3) Thought that to be the case, but again hearing it may be possible and also can't. Don't foresee doing it, but was curious...
4) Plan on flashing the latest (CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5) via odin, reboot, flash twrp v2.6.x as I hear 2.7.x may have a few issues. Only problems I've read are potential with Super SU - not sure if it's part of the root flash, needs to be flashed
separately, or just dl'd from Google Play Store? Guess will just flash root, see if app is there, if not try Play Store. If not, then go back and find the flashable SU dl.
Thanks!
Click to expand...
Click to collapse
Yeah you want TWRP 2.6.3.3. It won't work right with 2.7.x. Might as well flash the SuperSU. Most of the root apps worked fine but Viper4Androod did not find Busybox even after using the installer. Need to go back a version of V4A too due to bugs but it still didn't work. Tried freezing Knox apps that might be interfering but eventually just installed that MagazineUX ROM and now it works. Everything else should work easier.
22sl22 said:
Su is fine with me after cf root.
In my signature is a guide to rooting with kitkat (second post)
Follow that and you'll be good : good:
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks - that was the post had been reading through - appears after the kitkat OTA, latest posts mentioned problems with SU when running the original CF-AUTO Root method (flashing autorootp600mj4.tar.md5). Wondering if flashing the "newer" CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5
would be best. At this point feel confident either way!
deV14nt said:
Yeah you want TWRP 2.6.3.3. It won't work right with 2.7.x. Might as well flash the SuperSU. Most of the root apps worked fine but Viper4Androod did not find Busybox even after using the installer. Need to go back a version of V4A too due to bugs but it still didn't work. Tried freezing Knox apps that might be interfering but eventually just installed that MagazineUX ROM and now it works. Everything else should work easier.
Click to expand...
Click to collapse
Yep, will be downloading TWRP v2.6.3.3 and flash it and SuperSU after rooting. After rooting, will be curious to see where I sit with superuser (sorry, reading the latest posts kind of muddy whether a SU app is already installed or not, lol)...
Thanks everyone for all the great input & help!!
Hi all, new to all of this. Please keep this in mind as you read this thread.
Well first of all I have been reading about Cyanogenmod and how it helps saves battery. I also wanted to use cputuner to overclock my phone a little. I have in the past rooted this phone and installed cputuner not knowing that it could damage your phone if you didn't have a custom kernel that supported overclocking. After I found that out I uninstalled it and unrooted in fear of damage to my phone. Anyways I have a few questions and was looking knowledge, resources, and help about a few things.
Questions:
Is installing a custom rom and things needed to install a custom rom possible with a PC?
Can I safely reroot my device since I unrooted through #SU?
What do I need to do besides reroot my device in order to install a custom rom? (Cyanogenmod)
Thanks in advance!
Other INFO:
My device is a Samsung Galaxy S3 I-747
Firmware 4.4.2 KitKat
Device was rooted before using towelroot but I unrooted using #SU.
.
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
jason2678 said:
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
KentuckyGuy447 said:
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
Click to expand...
Click to collapse
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
dawgdoc said:
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
Click to expand...
Click to collapse
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
KentuckyGuy447 said:
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
Click to expand...
Click to collapse
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
dawgdoc said:
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
Click to expand...
Click to collapse
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
KentuckyGuy447 said:
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
Click to expand...
Click to collapse
I'm stuck.
You can install a custom recovery without having root, if you have a PC. You would use either Odin, Heimdall, or maybe adb.
You can install a custom recovery without a PC if you have root. You would use an app Like Flashify, Rom Manager, or Goo Manager (if it still exists).
You can flash a rom without a PC if you have a custom recovery, root is not needed.
Some roms, usually stock, can be flashed without a custom recovery if you have a PC.
I don't know the solution until you have access to a PC. I could see it being possible using a live USB with persistence of a Linux distribution, but you still have need for a PC. It's been a while since I created a live USB. The method I used required a small installation on the PC. so I don't see this as an immediate solution for you.
Oh sorry. I don't think towelroot works once you're on nj1, unless it has been updated.
If you get access to a PC, rooting is still fairly easy. You can use download mode and odin or heimdall to flash a custom recovery (be sure to uncheck reboot if using odin, or be really ready to pull battery). Don't let your phone reboot normally, you'll have to pull battery once odin is done.
Reboot to custom recovery, then flash supersu and you'll be rooted again, and set up to do whatever you want with your phone.
Sent from my LG-V410 using XDA Free mobile app
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
KentuckyGuy447 said:
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
Click to expand...
Click to collapse
excuse for butting in .... but if you dont know your bootloader/modem info. here is an app called 'samsung info' that should tell you.
your question "...... but theres no bootloader for my phone model right?" kinda worried me. its important to know because they should match AND trying to downgrade can brick your device. on the plus side ; i've never seen a custom ROM include bootloader/modem in it.
again , just a thought and not trying to butt in.:good:
https://www.dropbox.com/s/4ka74x02tg1rrn1/org.vndnguyen.phoneinfo-1.apk?dl=0
"all i can really do , is stay out of my own way and let the will of heaven be done"
As mrrocketdog stated, the Samsung Info app will tell you your bootloader and modem. If what you previously stated is correct, they should both be NJ1. You can get the same info by issuing these commands in a terminal emulator on the phone:
Code:
getprop ro.bootloader
and
Code:
getprop | grep version.baseband
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
KentuckyGuy447 said:
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
Click to expand...
Click to collapse
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
You have lifted a burden off my shoulders friend! Ever since I wanted to flash a custom Rom I've been worried if my phones bootloader was locked! I can now be at ease now that I know its unlocked. Will check upon that info about bootloader/modem.
Here is the info mrrocketdog
Is there a reason you can't use a PC to install a ROM?
I'm asking because I also do not know of a way to install a ROM without having root.
If you are able to root, you could try using the CM installer again.
audit13;5898140 said:
Thanks friend no worries, mrrocketdog helped me figure it out, than to all who helped!
Click to expand...
Click to collapse
KentuckyGuy447 said:
Here is the info mrrocketdog
Click to expand...
Click to collapse
Those are the latest versions of the bootloader and modem. You will be good for CM 12 or CM 11, and other custom ROMs based on CM. Older versions will work with them, but you probably need to edit the updater-script. (The older versions are not likely to include the NJ1 versions in the checks as they were not out when the ROMs were last updated.) NJ1 will also work with any of the ROMs based on the KitKat TouchWiz releases by Samsung.
As soon as you can find a PC to borrow you should be in business. Any chance of using one at a public library?
Appreciate all the help you gave me too friend, providing the links to cm and gapps, gonna borrow my friends laptop Sunday and try to root flash C-F Root through Odin. Thats the part that scares me but I should be good as people has confirmed it works for NJ1. Wish me luck friend. Would you recommend installing CM12? I personally like kit Kat and I know CM11 is based on that but is CM12 better? I guess its based on Lollipop
Do you think we will ever get something like towelroot for the 5X?
After 5 years of unlocking, messing with bootloaders, kernels, and roms I'm tired. I just want to enjoy my nexus. All I really want is root.
Thanks in advance for your thoughts.
I guess not.
It's so easy to flash superSU I don't know why that would be necessary. It only takes a few minutes.
Sent from my Nexus 5X using Tapatalk
thesoldier said:
It's so easy to flash superSU I don't know why that would be necessary. It only takes a few minutes.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
My understanding is that the OP wants root without having to flash all the images, and ROMs, to keep the phone up to date. OTAs are convenient and don't require much effort other than hitting "Reboot now" and waiting a minute or two. Flashing ROMs, right now, means that you have to download the whole ROM with the latest updates and security patches, boot into recovery, flash the ROM and whatever kernel or gapps you need, and then reboot.
I'm guessing the OP just wants plain root with all the conveniences and privileges that the stock ROM and OTA updates provide. Strangely enough, I'm leaning towards that route myself. I don't mind getting a boot img and custom ROM and kernel, but I don't want to have to flash so many items every single time when an OTA would sufficed.
daver68 said:
I'm guessing the OP just wants plain root with all the conveniences and privileges that the stock ROM and OTA updates provide. Strangely enough, I'm leaning towards that route myself. I don't mind getting a boot img and custom ROM and kernel, but I don't want to have to flash so many items every single time when an OTA would sufficed.
Click to expand...
Click to collapse
This is my situation as well. Especially now that Android security updates should be coming out on a monthly basis, I'm reluctant to give up the convenience of an OTA to get my security patches without needing to flash anything.
OTA updates will fail even if you are on stock and just rooted. I think chainfire is testing a root method that will allow you to take ota's because it doesn't modify the system partition.
This is a nexus device.. Something like towel root is not needed.. Just unlock the bootloader, boot (not flash) recovery and flash supersu..then you have stock just rooted..
Root methods like towel root etc.. Are mostly made for devices where you can't unlock the bootloader.. This is a nexus for Pete sake...It's not needed.. Unlocking the bootloader and rooting is easy enough in nexus devices..
Sent from my Nexus 5X using Tapatalk
Hi!
I had 2 nexus 5x phones. One rooting went fine, the other is stuck at the Welcome to Android cycle.
I unlocked the bootloader, and I used chainfire auto-root script from linux.
When the phone boots up it has the blue welcome screen. I setup wifi and then it forces me to install an android update. It downloads the update, reboots, tries to install it, fails, and then boots into android where it tries to force me into the update.
How can get out of the loop?
Just flash your favorite custom ROM from recovery (or stock if that pleases you) and ignore OTAs.
draggehn said:
Just flash your favorite custom ROM from recovery (or stock if that pleases you) and ignore OTAs.
Click to expand...
Click to collapse
not everyone is after custom roms, some people are more than happy with their (rooted) stock experience.
OP, the way googles OTAs work these days, is that they basically check your system partitions for any modification (e.g. root). if that check fails, so does the update. now what can you do about your little update trap?
if i recall correctly, chainfire includes ways to revert to unrooted. so there is you first possible option. use it, fire up your phone, let it take the OTA (make sure you're on the latest version after that) and attempt to root again.
if that is not an option, you could grab the newest factory image directly from google, flash the whole thing and then root again.
once your phone is up and running (and rooted ofc), it won't be able to apply future OTAs, but instead of forcing you to update, it will only show a notification.
Broken303 said:
not everyone is after custom roms, some people are more than happy with their (rooted) stock experience.
Click to expand...
Click to collapse
Which is why there was a parenthetical note that you can also flash stock.