Related
Noob for tablets. Got the nexus 10 for the family for christmas. Want to get it all setup before I turn it over to the wolves.
I love using TBpro on my Droid Bionic. I thought it would be good to have a solid backup program on the tablet, and since I have it on my smartphone I thought I would hang with what I've sorta know already.
Dont really understand what unlocked/locked means for a bootloader, and why the N10 needs that why many smartphone can be rooted without being unlocked.
I would love to hear some views on the purposes of apps like ClockWorkMod and TWRP and what they do and provide. Seems like they do perform backups and more. Why TBpro is likely just a backup app. What functions do these recovery apps have the make them "must have".
thanks for the time answering the tablet noob
TBPro requires Root access and to acquire root access you have to be able to modify the operating system. You can't do that until the bootloader is unlocked. Once unlocked, you then need to flash Custom Recovery (either CMW or TWRP) in order to to flash/install the the files required to install the root binaries. Other uses of recovery include making NAND/System Backups and installing custom roms. They are essential if you are into modding your device. I have an LG G2x that is rooted and has a custom rom (CM7.2) and a Custom Kernel (Faux123 v54), as well as Beats Audio for Gingerbread. I installed all of those via ClockworkMod. I followed ZedoMax's instructions to root my Nexus 10 and had only the initial bootloop issue after unlocking the bootloader. That was easy to fix but I couldn't get ClockWorkMod to stay installed so I flashed TWRP instead. Works great. Just follow this thread and watch the vids. Hope I helped some.
http://forum.xda-developers.com/showthread.php?t=1997227
bg1906 said:
TBPro requires Root access and to acquire root access you have to be able to modify the operating system. You can't do that until the bootloader is unlocked. Once unlocked, you then need to flash Custom Recovery (either CMW or TWRP) in order to to flash/install the the files required to install the root binaries. Other uses of recovery include making NAND/System Backups and installing custom roms. They are essential if you are into modding your device. I have an LG G2x that is rooted and has a custom rom (CM7.2) and a Custom Kernel (Faux123 v54), as well as Beats Audio for Gingerbread. I installed all of those via ClockworkMod. I followed ZedoMax's instructions to root my Nexus 10 and had only the initial bootloop issue after unlocking the bootloader. That was easy to fix but I couldn't get ClockWorkMod to stay installed so I flashed TWRP instead. Works great. Just follow this thread and watch the vids. Hope I helped some.
http://forum.xda-developers.com/showthread.php?t=1997227
Click to expand...
Click to collapse
Thanks!
After unlocking, and using CMW or TWRP. I can then "root" my device. ok. After rooting, I can use TBpro.
At this point, do I need to remain "unlocked" Does it matter? For the N10 will I receive OTA after being unlocked/rooted,
or do I need to be in another state?
jetguat said:
Thanks!
After unlocking, and using CMW or TWRP. I can then "root" my device. ok. After rooting, I can use TBpro.
At this point, do I need to remain "unlocked" Does it matter? For the N10 will I receive OTA after being unlocked/rooted,
or do I need to be in another state?
Click to expand...
Click to collapse
Yes to all. Another option for you if you are not comfortable typing in the various commands is to use the Wufresh method. Watch the video by qbking777 here: http://forum.xda-developers.com/showthread.php?t=2015467
bg1906 said:
Yes to all. Another option for you if you are not comfortable typing in the various commands is to use the Wufresh method. Watch the video by qbking777 here: http://forum.xda-developers.com/showthread.php?t=2015467
Click to expand...
Click to collapse
Thanks again. I did stumble across that site and was trying to compare that to the mskip Nexus root tool kit. That was had so many options and I didnt (yet) find the cliff note's version on what they all do and why you'd need to.
The GUI for Wufresh is simple. Do you use it? I read a little about the root and the root+custom recovery choices. Not entirely clear which is preferred, at least for me needs. And I've not got a warm fuzzy feeling about what state the N10 should be in, such that OTA updates still happen. Can they happen when unlocked+rooted+custom recovery but still stock ROM (without system mods)
The wugfresh version automates what the zedomax version does by hand. I did mine via the zedomax way.
Sent from my Nexus 10 using xda app-developers app
jetguat said:
Thanks again. I did stumble across that site and was trying to compare that to the mskip Nexus root tool kit. That was had so many options and I didnt (yet) find the cliff note's version on what they all do and why you'd need to.
The GUI for Wufresh is simple. Do you use it? I read a little about the root and the root+custom recovery choices. Not entirely clear which is preferred, at least for me needs. And I've not got a warm fuzzy feeling about what state the N10 should be in, such that OTA updates still happen. Can they happen when unlocked+rooted+custom recovery but still stock ROM (without system mods)
Click to expand...
Click to collapse
I would suggest using the Wugfresh method, definitely the simplest to use. And a great recovery is TWRP, it is very clear and easy to understand what it is that each menu contains.
Also with the OTA updates, it really depends on the size and type of update. If it is a fairly major one, like JB 4.1 to JB 4.2 then you will have to use the option in Wugfresh toolkit to 'unroot', then update. After the update you can simply reuse the toolkit to root again. Sometimes if the OTA is small it will simply install over the rooted device, but I wouldn't count on it. It definitely shouldn't discourage you from rooting though, its relatively simple to fix
Hi all,
I am kinda new here and would like to put a question, hoping it's not a repetition (I have been browsing though this forum thoroughly, but apparently couldn't find a proper answer). This is the situation:
- bought a used Z2
- Z2 was from UK O2 operator and it had operator lock and unlockable bootloader
- network operator lock has been cleared with unlock code
- O2 customized firmware has been wiped away by flashing a recent 5.0.2 stock lollipop
- unlockable bootloader still exists so cannot upload any customized/rooted .zip system
Clearly, the only thing I can do to modify this phone is to upload .FTF firmares to it, due to unlockable bootloader. Right now, I see available online only unmodified stock .FTF firmwares.
THE QUESTION: is there ANY way to create a pre-rooted .FTF file (modding not strictly necessay but rooting essential) so that I can upload it to the phone?
Thanks for all your precious advice!!!
You can't modify .ftf files as they are signed by sony. easiest solution is to root your phone with kingroot , install nut's dual recovery and then flash any stock prerooted zip (or a custom rom if you want) you can find on this forum. kingroot will be gone when you finish the .zip install too
ptmaniac said:
You can't modify .ftf files as they are signed by sony. easiest solution is to root your phone with kingroot , install nut's dual recovery and then flash any stock prerooted zip (or a custom rom if you want) you can find on this forum. kingroot will be gone when you finish the .zip install too
Click to expand...
Click to collapse
Thanks for answering!
Wouldn't just installing kingroot be enough for a simple rooting of the stock fw?
All I need is the ability to run some apps which need root (e.g. ad-away, set dns, etc.) and nothing more. Is the latest version tested on Z2 running 5.0.2?
Thanks again!
derjaeger said:
Thanks for answering!
Wouldn't just installing kingroot be enough for a simple rooting of the stock fw?
All I need is the ability to run some apps which need root (e.g. ad-away, set dns, etc.) and nothing more. Is the latest version tested on Z2 running 5.0.2?
Thanks again!
Click to expand...
Click to collapse
Kingroot works fine on 5.0.2 but by itself will not disable sony RIC and you won't get a writable system. Nut's dual recovery will disable RIC on boot, just install it after rooting and you should be good to go.
I suggested flashing a preroot zip just because i don't like kingroot app to manage root permissions and it's hard to replace it with supersu. flash a preroot zip and you'll end with a clean stock rom+supersu+nut's dual recovery and fully writable system
Thanks a lot buddy!
I will try kingroot+nut recovery and see how I find myself.
I will always be one step away from uploading a custom .zip in case I need supersu.
You really made my day!!! )))
Drop bk to kitkat, root and recovery no problem using practically any tool, I used Z2 dual recover installer, once it reboots to recovery you flash su update from chainfire, rooted and recovery done.
Then just use prf creater to make an ftf into a flashable rooted room, yes you can add root and recovery to that too, flash that from recovery, job done.
You can use lollipop ftf to do that if you wish.
gazza35 said:
Drop bk to kitkat, root and recovery no problem using practically any tool, I used Z2 dual recover installer, once it reboots to recovery you flash su update from chainfire, rooted and recovery done.
Then just use prf creater to make an ftf into a flashable rooted room, yes you can add root and recovery to that too, flash that from recovery, job done.
You can use lollipop ftf to do that if you wish.
Click to expand...
Click to collapse
Thanks for your answer!
But isn't this procedure including downgrade somewhat longer than the previous suggested one?
gazza35 said:
Drop bk to kitkat, root and recovery no problem using practically any tool, I used Z2 dual recover installer, once it reboots to recovery you flash su update from chainfire, rooted and recovery done.
Then just use prf creater to make an ftf into a flashable rooted room, yes you can add root and recovery to that too, flash that from recovery, job done.
You can use lollipop ftf to do that if you wish.
Click to expand...
Click to collapse
Go back to kk? why? it's a waste of time nowadays... the solution i mentioned won't even need to touch flashtool it's easier and quicker...
Just one last question: reading thrads about 5.1.1 it looks that it's due in a few days.
Would it be better to root now (as kingroot is still untested on 5.1.1 ) and then flash 5.1.1.ftf or just wait for it and then root?
Thanks
ptmaniac said:
Go back to kk? why? it's a waste of time nowadays... the solution i mentioned won't even need to touch flashtool it's easier and quicker...
Click to expand...
Click to collapse
Very true and if all are happy then it's all good, just don't forget to check ya phone afterwards for all the intrusive crap that kingroot throws on ya phone, tried it and it definitely didn't root my Z2 or a load of others.
derjaeger said:
Just one last question: reading thrads about 5.1.1 it looks that it's due in a few days.
Would it be better to root now (as kingroot is still untested on 5.1.1 ) and then flash 5.1.1.ftf or just wait for it and then root?
Thanks
Click to expand...
Click to collapse
IF you root now and install nut's dual recovery, you'll just need to flash a preroot 5.1.1 zip when it's released.
gazza35 said:
Very true and if all are happy then it's all good, just don't forget to check ya phone afterwards for all the intrusive crap that kingroot throws on ya phone, tried it and it definitely didn't root my Z2 or a load of others.
Click to expand...
Click to collapse
Sure, i also don't like kingroot. Like i said before it does root fine but doesn't disable ric, flashing nut's recovery after solves this.
And if you flash a preroot zip after there will be no traces of kingroot on the phone. Downgrade to kk and flashtool is still not necessary...
ptmaniac said:
IF you root now and install nut's dual recovery, you'll just need to flash a preroot 5.1.1 zip when it's released.
Good afternoon!
I have been though your procedure and, I must say, kingroot and nut's recovery installed well. Now the phone is rooted. Also added Purify app. There is just one problem left.
At the moment I have a stock 23.1.A.1.28 FW installed, just wanted to make a try with a 23.2.A.1.62 to see how the whole process goes. Instead of preparing the full .zip file, I already had a ready one, so I uploaded it into the phone, plus another .zip for gapps. Then, trying to start recovery, the phone does not enter recovery, but boots normally.
I know that nut's recovery is installed well, as, after installation process, it showed up a recovery (philz's?) with grey keys, and I also went though its menus to check it up. Right now these are the ways I tried, failing, to start recovery:
- immediately after switching on the phone (after vibration), pressing volume up
- immediately after switching on the phone (after vibration), pressing volume down
- starting manually (any of the 3 proposed recoveries) from NDR UTILS app
- starting manually from XZRecovery app
None of these methods work, the phone sometimes makes a double reboot (i.e. stays at "sony" first screen goes black and then goes back to sony screen again) but always ends up with loading android system. Is this maybe due to my locked bootloader? In this case would the only option be every time doing FTF upgrade+kingroot+nut's? Or is there some sure method to boot the recovery and install whatever I want?
After all, if it started once, I believe it can start again....
Thanks!
Click to expand...
Click to collapse
derjaeger said:
ptmaniac said:
IF you root now and install nut's dual recovery, you'll just need to flash a preroot 5.1.1 zip when it's released.
Good afternoon!
I have been though your procedure and, I must say, kingroot and nut's recovery installed well. Now the phone is rooted. Also added Purify app. There is just one problem left.
At the moment I have a stock 23.1.A.1.28 FW installed, just wanted to make a try with a 23.2.A.1.62 to see how the whole process goes. Instead of preparing the full .zip file, I already had a ready one, so I uploaded it into the phone, plus another .zip for gapps. Then, trying to start recovery, the phone does not enter recovery, but boots normally.
I know that nut's recovery is installed well, as, after installation process, it showed up a recovery (philz's?) with grey keys, and I also went though its menus to check it up. Right now these are the ways I tried, failing, to start recovery:
- immediately after switching on the phone (after vibration), pressing volume up
- immediately after switching on the phone (after vibration), pressing volume down
- starting manually (any of the 3 proposed recoveries) from NDR UTILS app
- starting manually from XZRecovery app
None of these methods work, the phone sometimes makes a double reboot (i.e. stays at "sony" first screen goes black and then goes back to sony screen again) but always ends up with loading android system. Is this maybe due to my locked bootloader? In this case would the only option be every time doing FTF upgrade+kingroot+nut's? Or is there some sure method to boot the recovery and install whatever I want?
After all, if it started once, I believe it can start again....
Thanks!
Click to expand...
Click to collapse
Nut's dual recovery works fine on LB (i have unlockable bootloader too) probably something you installed messed up the recoveries, did you install/update busybox from the play store? Nut's dual recovery includes it's own busybox which can't be replaced / updated.
Reinstalling the recoveries with the installer on your pc should fix the problem and make them work again.
Click to expand...
Click to collapse
ptmaniac said:
derjaeger said:
Nut's dual recovery works fine on LB (i have unlockable bootloader too) probably something you installed messed up the recoveries, did you install/update busybox from the play store? Nut's dual recovery includes it's own busybox which can't be replaced / updated.
Reinstalling the recoveries with the installer on your pc should fix the problem and make them work again.
Click to expand...
Click to collapse
Hi,
it looks like the device was somewhat messed up. U were right that i had installed another busybox from gplay, nevertheless uninstalling it did not sort out any effect. Also nut's reinstall failed. Maybe there was some chaos still inside due to experiments done before using kingroot, like, for instance, trying towelroot.
This is how I acted to solve the issue:
- downloaded most recent fw with xperifirm (Telekom.de one, full of useless apps)
- completely flashed phone with .ftf
- reinstalled kingroot
- reinstalled nut's recovery
Now the phone is back again rooted and I deleted some stupid apps with root app delete.
I am now eagerly waiting for 5.1.1 release, hope there will be a vanilla firmware somewhere this week ))
Best would be to already download a patched .zip image.
Right now thanks for the ideas!
Click to expand...
Click to collapse
derjaeger said:
ptmaniac said:
Hi,
it looks like the device was somewhat messed up. U were right that i had installed another busybox from gplay, nevertheless uninstalling it did not sort out any effect. Also nut's reinstall failed. Maybe there was some chaos still inside due to experiments done before using kingroot, like, for instance, trying towelroot.
This is how I acted to solve the issue:
- downloaded most recent fw with xperifirm (Telekom.de one, full of useless apps)
- completely flashed phone with .ftf
- reinstalled kingroot
- reinstalled nut's recovery
Now the phone is back again rooted and I deleted some stupid apps with root app delete.
I am now eagerly waiting for 5.1.1 release, hope there will be a vanilla firmware somewhere this week ))
Best would be to already download a patched .zip image.
Right now thanks for the ideas!
Click to expand...
Click to collapse
It's all part of the experience of learning what's best, I always only use dual recovery because windows can install it directly and root at same time, there used to be plenty of rooting apps like kingroot but you don't see so many anymore, but I'm glad you're sorted, when ya get 5.1.1 just use prfcreater to make it into flashable zip then you don't lose root and have to go through the process all over again.
All the best
---------- Post added at 01:26 AM ---------- Previous post was at 01:21 AM ----------
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Click to expand...
Click to collapse
Thanks a lot!
Yes, it really goes this way, now waiting for an unbranded fw, as this night the first branded ones have started to roll out...
I am really happy: for a couple of months I thought I was buried behind that nasty unlockable bootloader, and now i discovered it's even better, as rooting it without touching bootloader allows the software to work at 100% of it specs
Coming from Samsung to Sony is kinda rough at first for nibbling but when the right instruments are present and clear it's worth dealing with superior hardware.
Also, must say that Sony is lately improving its behaviour, after so many years of mafia attitudes towards buyers
Inviato dal mio X500U utilizzando Tapatalk
I've had Samsung, HTC, Apple, blackberry and finally stuck with Sony, I guess they all have pros and cons, Samsung phones are the easiest to mod and flash, Sony is quite daunting for newcomers very much like HTC. Can be tricky to learn.
Horses for courses and all that, I much prefer a rooted phone with locked boot, no particular reason except the drm keys etc, I do think camera is better on lb, than the quality on ul, although there is a drm restore mod on cross Dev, for ul, it does make xreality work, but it doesn't remove the missing key error in security tests.
I read on a page that once drm keys are gone, Sony won't honour the warranty, very much like Samsung and the knox counter, I'm not sure tho, but I do know I'll always remain Lb and stock based rom.
Only problem I have is getting wifi tethering working properly, it's doing my head in, 4 weeks of decompiling and editing and still can't get my phone to broadcast on any other channel except 1.
GGGRRRRRR @ SONY.
#whattheheckhaveyoudonesony
All so true!
Btw1, when I reflashed last evening the phone was also complaining when I went to hotspot section in order to configure it.... I think they messed up something, but maybe 5.1.1 will have fix so let's see...
I have a couple of Mediacom X500U, which I discovered, besides being fairly nice phones after more than a year of use, that are basically rebranded HTC phones (this comes out of their factory hex code detected by Linux). Do you think they could be modded like for generic HTC or never heard about them?
derjaeger said:
All so true!
Btw1, when I reflashed last evening the phone was also complaining when I went to hotspot section in order to configure it.... I think they messed up something, but maybe 5.1.1 will have fix so let's see...
I have a couple of Mediacom X500U, which I discovered, besides being fairly nice phones after more than a year of use, that are basically rebranded HTC phones (this comes out of their factory hex code detected by Linux). Do you think they could be modded like for generic HTC or never heard about them?
Click to expand...
Click to collapse
Looks like a cheap option of unb
randed HTC, but no, I don't think a HTC section would help.
I think it's an Italian release, dual simply phone, simply Google pointed to an Italian forum androidiani androidiani, run the link through a webpage translator and you may be in luck for root and rom, I think towelroot may root it.
Actually framaroot already offered rooting at the price of a horrible hack (3-4 reboots before device is ready when turning on or rebooting, plus device instability on heavy loads), never tried towelroot on it.
But problem is not about rooting rather than getting rid of horrible stock firmware. The latest fw edition by Mediacom was a total disaster (forums cry loud) and I thought it would be great to try to put some mod on the phones: this is why I had in mind to ask you if there is a general toolkit for HTC phones (like flashtool for Sony) which I could use to try to take care of it and experiment....
Inviato dal mio X500U utilizzando Tapatalk
Hello,
Samsung Note 3
I REALLY want to root my phone to help test out the beta of f.lux. You can look it up if you want, should take you a a peachy orange page. Anyway, I really want that on my phone, and it needs root, and I've NEVER rooted a phone before, and I'm not sure what I'm doing.
I want to follow [this guide](http://www.phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247) PhoneArena link, but it doesn't say what android version it needs, and that worries me.
One more thing, I downloaded a file called "fastboot" and it has something to do with ADB that disables certain apps so that I'm not nagged to update. I'm on 4.4.4, and I can't find that file, I think it's in the root of C:\ but I ran them and it didn't work. So if I could reenable those apps to get on lollipop or marshmallow, if rooting would be easier, I'd do that. I've searched the forum, but I need baby steps.
Thanks.
timpster said:
Hello,
Samsung Note 3
I REALLY want to root my phone to help test out the beta of f.lux. You can look it up if you want, should take you a a peachy orange page. Anyway, I really want that on my phone, and it needs root, and I've NEVER rooted a phone before, and I'm not sure what I'm doing.
I want to follow [this guide](http://www.phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247) PhoneArena link, but it doesn't say what android version it needs, and that worries me.
One more thing, I downloaded a file called "fastboot" and it has something to do with ADB that disables certain apps so that I'm not nagged to update. I'm on 4.4.4, and I can't find that file, I think it's in the root of C:\ but I ran them and it didn't work. So if I could reenable those apps to get on lollipop or marshmallow, if rooting would be easier, I'd do that. I've searched the forum, but I need baby steps.
Thanks.
Click to expand...
Click to collapse
If you're just looking to try out f.lux you could give Cf.lumen a try first. It has a non-root mode.
If you want to root you can just flash a custom recovery like TWRP with Odin.
Sjant said:
If you're just looking to try out f.lux you could give Cf.lumen a try first. It has a non-root mode.
If you want to root you can just flash a custom recovery like TWRP with Odin.
Click to expand...
Click to collapse
You say, just flash, as if there is no risk. I want to get it right, no bricking. I'm on 900V (V for verizon), and I want a quick safe way to root. Also, thank you for mentioning Cf.lumen, I do have it, and the nonroot looks like ****, yes it works, but it's not remotely the same.
timpster said:
You say, just flash, as if there is no risk. I want to get it right, no bricking. I'm on 900V (V for verizon), and I want a quick safe way to root. Also, thank you for mentioning Cf.lumen, I do have it, and the nonroot looks like ****, yes it works, but it's not remotely the same.
Click to expand...
Click to collapse
I recommend visiting TWRP's website and pick out the latest version for your device and then flash the latest non-beta version of SuperSU which you can find here on XDA. Flash TWRP with Odin and then boot into recovery and simply reboot, it will then ask you if you'd like to root your device.
What model do you have? Find your model first then download TWRP recovery. Use odin to flash the recovery, then flash super su.
Odin - http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
Supersu - https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
Complete edit.
O.K., so I see that TWRP has a backup option. If I use this option, and should I "brick" my phone, could I flash the TWRP in odin, and figure out how to restore the backup, and unbrick the phone if I screw up the root process? Because that would be ****ing amazing, and I'd root IMMEDIATELY if that's the case, because, no worries -- I'd always have a backup! I love backups.
You need Root for TWRP to backup .
Suggest you read the stickeid FAQS and guides .
timpster said:
Complete edit.
O.K., so I see that TWRP has a backup option. If I use this option, and should I "brick" my phone, could I flash the TWRP in odin, and figure out how to restore the backup, and unbrick the phone if I screw up the root process? Because that would be ****ing amazing, and I'd root IMMEDIATELY if that's the case, because, no worries -- I'd always have a backup! I love backups.
Click to expand...
Click to collapse
First things first, EXACTLY what Note 3 model do you have? Go to Settings -> About -> Device model. If it is SM-N9005, that would be quite surprising, because we didn't get a 4.4.4 build.
American Note 3s got a 4.4.4 build, N900A, N900V (AT&T Note 3 and Verizon Note 3 respecitevly), and the methods for rooting THEM has nothing in common with the way a N9005 or N900 is rooted.
900V. Verizon, 4.4.****ing4. I had .3 but it kept nagging me to update like trial software and that was probably the end of my chances as I recall I most likely have a locked bootloader so I may not be able to do any of this.
Why can't I make a full backup on stock android anyway, seems like the responsible thing to do.
Verizon then use the verizon forum anything from here is wrong and may brick your phone .
Full backup requires a modified recovery therefore no longer stock .
Ah so it's the stock recovery that is used. So why do you think that lacks options for a full backup?
When you say use Verizon forums is that a section here or a dedicated Verizon forum?
Hi Guys,
I received my unlocked 900F today, and have been prepping to do some work on it. Already downloaded Odin, USB drivers, etc, getting ready to backup, flash CWM Recovery. All looks pretty straight forward. A couple things I'm not sure about though...
Much to my surprise, its already rooted with Kingroot present on the system. Cant say I'm real fond of it, is it wise to replace it with a 'normal' SU setup? Any caveats?
Second thing, is that the system is saying there is an update available. Is this wise, or do I risk messing up root, or anything else?
Thanks for any suggestions, advice, info.
K
KetoSoi said:
Hi Guys,
I received my unlocked 900F today, and have been prepping to do some work on it. Already downloaded Odin, USB drivers, etc, getting ready to backup, flash CWM Recovery. All looks pretty straight forward. A couple things I'm not sure about though...
Much to my surprise, its already rooted with Kingroot present on the system. Cant say I'm real fond of it, is it wise to replace it with a 'normal' SU setup? Any caveats?
Second thing, is that the system is saying there is an update available. Is this wise, or do I risk messing up root, or anything else?
Thanks for any suggestions, advice, info.
K
Click to expand...
Click to collapse
If your rooted updates won't install. Not sure what you want as an end result but if you want the latest Samsung official update then you will need to either use one of the latest debloated ROMs here in XDA development under S5 or download from Sam Mobile and use Odin to install. But personally I recommend either xXx or _Axelandr ROMs which are latest stock with root and other support. King root isn't the way to go because it doesn't use official super su. Also king root uses spyware... Not a great option. Also BACKUP YOUR EFS FOLDER NOW! DO IT! you'll only cry later when things go wrong. What model phone and firmware are you running now?!
RuffBuster said:
If your rooted updates won't install. Not sure what you want as an end result but if you want the latest Samsung official update then you will need to either use one of the latest debloated ROMs here in XDA development under S5 or download from Sam Mobile and use Odin to install. But personally I recommend either xXx or _Axelandr ROMs which are latest stock with root and other support. King root isn't the way to go because it doesn't use official super su. Also king root uses spyware... Not a great option. Also BACKUP YOUR EFS FOLDER NOW! DO IT! you'll only cry later when things go wrong. What model phone and firmware are you running now?!
Click to expand...
Click to collapse
Yeah, that was my concern. I didnt want to install the Samsung update if it will cause me root issues down the road. So best to NOT install it then?
I was surprised Kingroot came with the phone, what reading I did on it indicates its sketchy at best. Going to toss that quickly then.
At this point, my plan of attack is:
1. Flash CWM recovery.
2. Backup as it is now.
3. Backup EFS.
4. Remove Kingroot, install normal SU.
I'll start looking into other ROM's afterwards, when I have more time.
The phone is a SM-G900F, Build # LRX21T.G900FZHU1BOA1. Not sure if thats the firmware #, or something else. Nothing else jumps out at me.
Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE
I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works
RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.
does this require the developer version? btw how do i backup
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.
Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.
In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.
Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.
Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.
kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.
Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.