how to root i9205 on UCNA2 firmware? - Samsung Galaxy Mega

hi, i have a simple question, is it possible to root my device? i've never root my mega 6.3 since i bought it...... but i heard that the recent firmware have some problems in the possibility of rooting it.
there are a lots of guide but everyone say a different method. OK I AM A NOOB OF MODDING.
but is quite difficult to understand guides that are different in this way:
1) some indicates to just use an apk autorooting the device
2) some do require to change thekernel + manually install the superuser apk
3)not permanent root....
4) others......
so, please be patient......:angel: i only want to find a "normal" root method.......and IF POSSIBLE a root that could allow me to easily UNroot the device to be able to update my firmware OTA in the moment samsung will update our great device to kitkat

If you are a noob at modding don't even bother with rooting. Its dangerous and BTW I think your firmware has KNOX which the GMega doesn't have a workaround.
Sent from my GT-I9200 using Tapatalk

realista87 said:
hi, i have a simple question, is it possible to root my device? i've never root my mega 6.3 since i bought it...... but i heard that the recent firmware have some problems in the possibility of rooting it.
Click to expand...
Click to collapse
If you are brave enough you can try it using this tutorial
http://forum.xda-developers.com/showthread.php?t=2574953
But read it thoroughly and if you do not understand one thing though - do not attempt to try.
Read forums and learn till you can understand what you are doing lest you have quite expensive paperweight... I am not responsible for what you do with your phone!

my previous phone was rooter, the optimus 3d and the ascend mate.
i don't need toor for extreme modding but just to install a custom recovery for a nandroid backup and for use SOME APP THAT REQUIRE root to work properly.
i never installed a recovery but i read everywhere that it is a lot usefull in case of some errors, to restore the previous backup made 1:1 (nandroid)

Every modding attempt must start from root and (optionally) custom recovery. In fact - rooting itself is modding and quite heavy from system point of view. If you want to change ONE THING in system, you have to root your phone. Doing this you are tripping 'warranty flag' and from now on your warranty is void.
If you have firmware with KNOX and new bootloader - tripping this flag is irreversible. But as long as you do not attempt to flash older firmware (before KNOX) it does not affect the operation of the system. Trying to flash older firmware makes your phone softbrick because of tripping security mechanism in new bootloader.
If you already rooted your phone it is resonable to flash custom recovery and by this have wide possiblity making backups of your whole system (nandroid backup) or flashing custom ROMs

Related

[Q] Will the v4.1.2 Minor FW Update remove root?

GT-I9300 International No carrier
Current FW v 4.1.2
hxxp://i.imgur.com/DxDXONZ.png
Update Details
hxxp://i.imgur.com/18JE68Z.jpg
Phone Rooted using CF-Auto-Root
SuperSU and Busybox installed
CWM not installed
Using Stock ROM
Using Stock Kernel
As you can see Kies has prompted me an update and the update seems to have already downloaded OTA using WiFi.
It is prompting me to install the update again and again.
My question is, if I do select to install this update,
1.) Will it remove root?
2.) Will it completely wipe my phone? (previous incremental updates haven't wiped my data, but the phone wasn't rooted then.)
3.) Can I root again using CF-Auto-Root?
Thank you.
Jaxx89 said:
GT-I9300 International No carrier
Current FW v 4.1.2
hxxp://i.imgur.com/DxDXONZ.png
Update Details
hxxp://i.imgur.com/18JE68Z.jpg
Phone Rooted using CF-Auto-Root
SuperSU and Busybox installed
CWM not installed
Using Stock ROM
Using Stock Kernel
As you can see Kies has prompted me an update and the update seems to have already downloaded OTA using WiFi.
It is prompting me to install the update again and again.
My question is, if I do select to install this update,
1.) Will it remove root?
AS per thousands of posts YES.
2.) Will it completely wipe my phone? (previous incremental updates haven't wiped my data, but the phone wasn't rooted then.)
NO
3.) Can I root again using CF-Auto-Root?
YES
All this is posted multiple times .
jje
Click to expand...
Click to collapse
JJEgan said:
Jaxx89 said:
GT-I9300 International No carrier
Current FW v 4.1.2
hxxp://i.imgur.com/DxDXONZ.png
Update Details
hxxp://i.imgur.com/18JE68Z.jpg
Phone Rooted using CF-Auto-Root
SuperSU and Busybox installed
CWM not installed
Using Stock ROM
Using Stock Kernel
As you can see Kies has prompted me an update and the update seems to have already downloaded OTA using WiFi.
It is prompting me to install the update again and again.
My question is, if I do select to install this update,
1.) Will it remove root?
AS per thousands of posts YES.
2.) Will it completely wipe my phone? (previous incremental updates haven't wiped my data, but the phone wasn't rooted then.)
NO
3.) Can I root again using CF-Auto-Root?
YES
All this is posted multiple times .
jje
Click to expand...
Click to collapse
Sorry about that. Maybe my searching skills aren't good enough or maybe I don't know how to use this forum coz I found only one thread that too with a Gingerbread FW, which is why I posted this Q
Really sorry.
Thanks for the quick reply.
Click to expand...
Click to collapse
Device status modified and cannot update
tried using triangle away and did not reset the flash counter
Because triangle away can reset your flash counter only if you're running stock recovery, stock kernel, stock rom etc.
CF-AutoRoot should not make your status "modified" but probably like you see it did. Maybe some other apps did that, maybe not, nobody knows anyway. If you really need these updates then you should flash newest firmware from samsung through odin and then root it + reset flash counter, it should work also for further updates (but I'm not sure).
JustArchi said:
Because triangle away can reset your flash counter only if you're running stock recovery, stock kernel, stock rom etc.
CF-AutoRoot should not make your status "modified" but probably like you see it did. Maybe some other apps did that, maybe not, nobody knows anyway. If you really need these updates then you should flash newest firmware from samsung through odin and then root it + reset flash counter, it should work also for further updates (but I'm not sure).
Click to expand...
Click to collapse
Thanks a lot.
I know where to get the FW updates to flash via Odin but don't really understand how to reset the flash counter if not by using TriangleAway.
Could you please be kind enough to guide me?
And these are the apps I used after root
SuperSU
Busybox
Root checker
Titanium Backup
Lucky patcher
Market enabler
Greenify
Could any of these apps modify the stock kernel, rom or recovery? Coz I never flashed any custom ones just rooted using CF-Auto-Root and installed the root apps
P.S: I was able to do the FW update via Kies and now the status is back to normal, but I'm afraid to root coz the status might go back to modified.
It's more like, you know. If we're talking about warranty then they'll find that your rooted your phone anyway. If we're talking about updates then probably it's still better to keep an eye on some stock-based custom roms, mostly because of frequent updates (nearly instantly after new baseband), while you still need to wait some time for OTA to arrive. Of course it's much easier to apply OTA than whole custom rom but hey, how often are you doing that?
About your question - busybox is my choice because it modifies /system apps, many of them.
And lastly - in odin you have a checkbox to reset flash counter, so you don't need to worry about anything using this tool. At least in general.
Overall I'd stick with pure stock non-rooted firmware if you don't need it in general or rooted custom rom (f.e. mine ) for much better experience. I couldn't go back to stock after getting used to much better performance, less battery drain etc.
Choice is yours.
Lucky patcher
Warez is totally banned on XDA you are stealing from developers .
As its a warez app who knows what sort of malware it could add to your phone .
I would wipe the phone install original firmware .
http://forum.xda-developers.com/showthread.php?t=1978840
Then update it and to stick with unrooted stock .
jje
JustArchi said:
It's more like, you know. If we're talking about warranty then they'll find that your rooted your phone anyway. If we're talking about updates then probably it's still better to keep an eye on some stock-based custom roms, mostly because of frequent updates (nearly instantly after new baseband), while you still need to wait some time for OTA to arrive. Of course it's much easier to apply OTA than whole custom rom but hey, how often are you doing that?
About your question - busybox is my choice because it modifies /system apps, many of them.
And lastly - in odin you have a checkbox to reset flash counter, so you don't need to worry about anything using this tool. At least in general.
Overall I'd stick with pure stock non-rooted firmware if you don't need it in general or rooted custom rom (f.e. mine ) for much better experience. I couldn't go back to stock after getting used to much better performance, less battery drain etc.
Choice is yours.
Click to expand...
Click to collapse
Thanks for the quick response
I rooted mainly coz I needed to use market enabler
In Odin are you referring to the option F. Reset time??
I am using the Odin version provided by Chainfire in his S3 rooting thread in which all options are disabled except for Auto reboot.
@JJEgan I don't even know how to use half of the apps I mentioned, I only installed them as my friend suggested it as must have root apps.
As you might see, I am still a N00b at this and am in the learning process.
BTW Thanks for the link to the guide.
Jaxx89 said:
Thanks for the quick response
I rooted mainly coz I needed to use market enabler
In Odin are you referring to the option F. Reset time??
I am using the Odin version provided by Chainfire in his S3 rooting thread in which all options are disabled except for Auto reboot.
@JJEgan I don't even know how to use half of the apps I mentioned, I only installed them as my friend suggested it as must have root apps.
As you might see, I am still a N00b at this and am in the learning process.
Click to expand...
Click to collapse
I suggest going through my flashing guide located in ArchiDroid thread, with newest odin and newest methods for flashing/rooting.
JustArchi said:
I suggest going through my flashing guide located in ArchiDroid thread, with newest odin and newest methods for flashing/rooting.
Click to expand...
Click to collapse
Thanks a lot.
If I'm not mistaken, ArchiDroid is a Custom ROM(pre-rooted) which requires a Custom Recovery.
I will be learning a bit more first before I install a Custom ROM.
A question though. Will I have to take a backup of my app data if I decide to install a custom ROM?
Also if I want to install the stock FW via Odin, will I have to take a backup first?
Thanks and I'm really sorry about asking such questions.
Jaxx89 said:
Thanks a lot.
If I'm not mistaken, ArchiDroid is a Custom ROM(pre-rooted) which requires a Custom Recovery.
I will be learning a bit more first before I install a Custom ROM.
A question though. Will I have to take a backup of my app data if I decide to install a custom ROM?
Also if I want to install the stock FW via Odin, will I have to take a backup first?
Thanks and I'm really sorry about asking such questions.
Click to expand...
Click to collapse
Yes it requires custom recovery for installing .zip package.
There is nothing to learn if you ask me, you have complete guide for installing everything you need in step-by-step howto. If you want to keep your data then you need to use some nice app for that f.e. Titanium Backup but for that you need root and... yeah. It's easier to start from scratch on new pre-rooted rom.
I'd suggest flashing custom recovery (tutorial in my topic) and then you can create a backup directly from that, with everything you want to, including actual system, efs folder, recovery, kernel etc. So you can easily get back to original rom whenever you want to. Keep in mind that you still need custom recovery for that.
JustArchi said:
Yes it requires custom recovery for installing .zip package.
There is nothing to learn if you ask me, you have complete guide for installing everything you need in step-by-step howto. If you want to keep your data then you need to use some nice app for that f.e. Titanium Backup but for that you need root and... yeah. It's easier to start from scratch on new pre-rooted rom.
I'd suggest flashing custom recovery (tutorial in my topic) and then you can create a backup directly from that, with everything you want to, including actual system, efs folder, recovery, kernel etc. So you can easily get back to original rom whenever you want to. Keep in mind that you still need custom recovery for that.
Click to expand...
Click to collapse
Ok Now I'm really confused
I still haven't learnt how to use Titanium Backup to backup, or how to do a nandroid backup. I have read it's better to do a backup b4 installing a custom ROM. And if I'm not mistaken, I need ROOT to do a nandroid backup too.
As I said before that I used CF-Auto-Root, I just followed the instructions to the word.
I had tried doing a ADB backup before root, but for some reason it kept exiting(I guess coz I have just about 1GB memory left on my Internal memory SD card)
Thanks for the quick reply. Man ur really fast in answering questions. :good:
EDIT: Just did the CF-Auto_Root again and didn't install any other apps like busybox(uninstalled all root apps) and used triangleaway to reset the flash counter. But the counter still stuck on 1
The device status shows normal though.
Jaxx89 said:
Ok Now I'm really confused
I still haven't learnt how to use Titanium Backup to backup, or how to do a nandroid backup. I have read it's better to do a backup b4 installing a custom ROM. And if I'm not mistaken, I need ROOT to do a nandroid backup too.
As I said before that I used CF-Auto-Root, I just followed the instructions to the word.
I had tried doing a ADB backup before root, but for some reason it kept exiting(I guess coz I have just about 1GB memory left on my Internal memory SD card)
Thanks for the quick reply. Man ur really fast in answering questions. :good:
Click to expand...
Click to collapse
First of all you need custom recovery to perform nandroid backups. So you can stick with my first 10 steps in my howto. After that enter recovery, enter backup section and make a custom backup (or default, doesn't matter) of everything you have, especially /efs folder as it's really important. When you finish doing backup then boot to your normal system and copy these backups to your PC. Now you're sure that they won't disappear and if you want to backup your phone from that then simply put them back on your phone and restore them from the recovery.
But overall I'd suggest clean start without these backups. Of course it's always recommended and I recommend it as well but as long as you won't want to go back to original rom, there is no real point for backing it up. You can always download latest official firmware and flash it through odin.

[Q] Backing up and rooting/unlocking bootloader question.

Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
I see its been a few days and no one has replied so I will do my best to share what knowledge I have. I've been heavily flashing custom ROMs on my ASUS tablet now for the better part of a year and just got my Verizon GS4, so I have alot of the same questions as you.
1) I'm going to answer this in two parts.
​Nandroid, in my experience, refers to the type of backup, not necessarily the process by which to backup. Most common recoveries, including ClockworkMod and TWRP have a feature to create a 'nandroid backup'. This can take some time and files can be quite large, as they copy pretty much every single file on your device; almost like creating a snapshot of your device in that moment in time.
​To answer the later part of this question, (typically speaking) once you unlock a bootloader you cannot re-lock it, but that could be different for phones (my knowledge in phones is limited). And yes, using a nandroid backup will back up your device with root access, but using a tool such as Rom Toolbox, you can easily un-root (the program features a 'permanent unroot option'). For one, I would imagine that flashing the stock kernel would overwrite the root, as like you said earlier in the post the current root exploit works by flashing a pre-release kernel, applying root to the device, then re-flashing the current stock kernel. Another way to lose root is to get an over-the-air (OTA) update. You will see programs like OTA Rootkeeper that work to circumvent this, but in your case that may be a valid way to cover your arse in case you need to return it under VZW warranty (it is for this reason that I always buy Best Buy protection plans, because they could care less about the software state about your device [Disclaimer: I worked for Geek Squad so I have /somewhat/ intimate knowledge in this matter])
2) I just rooted my GS4 a few days ago, and nothing I read indicated that the all-in-one tool would unlock the bootloader. If you read the documentation about Loki, he explains this fact. I just found a good video (although it uses TWRP and GooManager instead of ROMManager and CWM) explaining that there isn't a bootloader "unlock" just yet; rather its a workaround to the bootloader that allows us to get custom ROMs on our devices (video is here)
3) "Bricking" a device means rendering the device useless; it won't operate to any fashion that it is useful to you, so its no better than a brick or a paper weight, etc. I would imagine you can re-flash a stock verizon ROM/kernel to restore any screw-ups, but keep in mind this device was released less than three months ago and any development is relatively new. Yes, we have had other Galaxy S series phones, but the S4 has this whole KNOX nonsense that is specifically designed to prevent the kinds of activities we do here on this forum
I really hope that helps. If I said anything that is incorrect, please please feel free to correct it so that at least we can all learn the proper information.
Thanks,
Opethfan89
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
DarkMenace said:
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
Click to expand...
Click to collapse
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
opethfan89 said:
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
Click to expand...
Click to collapse
I'm not n sure. It's the only one I ever used for banner blocking. You use the files with Odin as well after they are extracted.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium

[Q] Questions about rooting process, samsung updates, and Knox

I had long been using a rooted phone before I got the S5, but things seem a little different now. I held off on rooting the S5 because I wanted to be sure that I was going to keep it long term before I did. So yesterday I did some research on here and elsewhere and ended up rooting via towelroot and getting SuperSU installed without flashing. Now I just need to figure out a few things and was hoping to get some help understanding what comes next.
I've been reading about concerns over tripping "Knox" holding folks back from flashing custom recover and ROMs. I'm not a touchwiz fan but I can tolerate it. If there were no cost, I'd probably just install Xposed or something like that but is this Knox thing important? What am I giving up if I flash a custom recovery?
SuperSU "disabled" Knox when I started it. What functions of Knox are disabled? Can I flash recovery and roms without incident now that it is disabled?
Almost as soon as I got done rooting and installing SuperSU last night, I got a notification from samsung saying that "an update is required to access samsung services". Was that triggered by the rooting of the phone? Can I install that update without loosing root access?
Last question: Now that I have root, what do I need to do to keep it? Will it be rolled back by any OTA update, and if so, what must I do to prevent that?
Any help would be greatly appreciated.
RobsterCraw said:
SuperSU "disabled" Knox when I started it. What functions of Knox are disabled? Can I flash recovery and roms without incident now that it is disabled?
Click to expand...
Click to collapse
You wouldn't have had to search or read very far in the forum to find answers to all of your questions. These get asked over and over, pretty much every day.
If you are contemplating a custom recovery, then read a thread about e.g. TWRP to learn about it's advantages. As just one of many advantages, it's the only way that you can make a proper, 100% backup.
Installing a custom recovery will increment Knox because Knox has not been removed from the bootloader. However most people don't obsess about the Knox flag. The only significant downside to the flag is that it might invalidate a minority of warranty claims.
Block e.g. rename or freeze the OTA updater to avoid losing root. An update will generally break it and there is no assurance that you will always be able to reroot. SuperSU Pro has a feature that attempts to restore root after an update.
.

[Q] 'e-fuse' switch on root + lollipop un-root?

Hi all, thanks in advance for any help on this. I have a few general s5 rooting questions. I'm an experienced 'rooter' having rooted and installed custom ROMs on many previous devices.
- I've ready that the s5 has an 'e-fuse' that gets 'blown' when the device is rooted. this then voids the warranty and prevents things like Fort Knox from running. I get that, and understand the risks. But, I've also read that the lollipop update will remove root. These two things seem to contradict themselves.
- on other devices I've rooted, I've then installed a custom ROM. I don't plan to do this with my s5. I haven't been able to find much written on the experience of a rooted s5 running the samsung stock ROM/firmware. I'd like to use something like xposed to change parts of the ROM (like the white background that's so pervasive in the s5 flavor of lollipop). I'm curious if anyone is running lollipop on an s5 that is rooted but running stock samsung firmware and xposed.
thanks!
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
thanks!
stncldtex said:
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
Click to expand...
Click to collapse
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
scwtech said:
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
Click to expand...
Click to collapse
Right now there are threads that show you how to get rooted lollipop on your phone without tripping Knox which basically involves downgrading the kernel so you can root with towelroot, then using mobile Odin to flash lollipop and inject root in the process. It seems people are able to do this without issues. To this point, I do not think that anyone has found an exploit for lollipop.
The problem you will run into is that Xposed still does not run on lollipop so you cannot do much in the way of customization. Most of the G900F ROMs can run on the G900T so you might poke around in those threads to pick up more info.
Hope this helps a little.
If I or anybody on XDA helps you, please hit the "Thanks" button.
scwtech said:
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
Click to expand...
Click to collapse
System runtime is different. Art for lollipop compared to dalvik.. So it's not compatible as of now
Sent from my SM-G900T using XDA Free mobile app
This does not work with lollipop
---------- Post added at 07:30 PM ---------- Previous post was at 07:25 PM ----------
gspears said:
Right now there are threads that show you how to get rooted lollipop on your phone without tripping Knox which basically involves downgrading the kernel so you can root with towelroot, then using mobile Odin to flash lollipop and inject root in the process. It seems people are able to do this without issues. To this point, I do not think that anyone has found an exploit for lollipop.
The problem you will run into is that Xposed still does not run on lollipop so you cannot do much in the way of customization. Most of the G900F ROMs can run on the G900T so you might poke around in those threads to pick up more info.
Hope this helps a little.
If I or anybody on XDA helps you, please hit the "Thanks" button.
Click to expand...
Click to collapse
are you sure ? I have been able to downgrade. towelroot and flash lollipop and it boots but supersu does not work properly. root apps ask permission and supersu grants permission but the apps dont actually work
stncldtex said:
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
Click to expand...
Click to collapse
I don;t know where you heard that rooting won;'t trip Knox but I beleive you are wrong about that At least I know that Flashing cf auto root - flashing recovery or flashing custom roms all trip knox. If your phone can use Towel Root - that rooting process does not trip knox - but I am not sure if Towel Root works on Lollipop or on the S5 for that matter. (I may be wrong about Towel Root - I have never used that process so I can't say for sure)
Flashing a new rom via ODIN does not trip knox. It is just like getting an UPDATE from the carrier OTA.
BUT, If you are already rooted - you already have tripped knox - flashing Lollipop will remove root - but it will not do anything to change the fact that you tripped knox on your phone already.
As far as I know everything I have said is correct - based on what I have learned thru reading - flashing and using several different samsung phones -
finally, I see a lot of people paranoid as hell about tripping knox - and I can tell you without any hesitation that I have never had a problem getting service or replacements after rooting a phone - there have been a few times back when I first started flashing roms that I had issues with my phone and I took it in and got a replacement without any issue - once I broke my screen and got a replacement then too - both times I was rooted, running custom recovery - etc.
I hope this helps you
I used towel root on NE6. You can downgrade to that via Odin and not trip knox. As far as flashing 5.0 and losing root. I came from Alliance flash Twisted lollipop and kept root. Then used Odin to flash the bootloader and modem for OB1.
Do you still have Knox 0?
How did you flash lollipop?

[Q] Custom ROMs for the LG Transpyre (VS810PP)

Hi Everyone,
I've seen this question posted randomly in threads for other topics but didn't see a thread for the question itself so thought Id put it out there because
1. I'm curious to the answer myself.
2. Having this thread might back the search for others with the same question slightly less time consuming and a whole lot easier.
That being said, does anyone out there know of any custom roms for, or ones that will work on, the LG VS810PP (Transpyre)?? Also, since (as far as I can tell) the Transpyre and the LG Tribute are essentially the same phone, could one use a custom rom for the Tribute on the Transpyre? Surely, I wont be stuck with staying on stock! I MUST MOD!!! :cyclops: :fingers-crossed:
Any and all help IS GREATLY and WHOLEHEARTEDLY appreciated! Thanks soooo much in advance.
Calling all Modders! Calling all Modders!
I have this device as well and would love to get off the stock Rom an instal CM or other, hate the bloatware an Rom over all seems sluggish. I am sure there is someone with the knowledge out there that has this device an can help!!!!! Calling all Transpyre Modders! Its time to Rom Out!
Root, but no rom
Im a Transpyre user and was able to succesfully root but have yet to find any custom roms. in the meantime i have removed lots of bloatware and things are running a lil better and my battery is lasting a bit longer.
I was able to root, de-bloat and install TWRP. I also made a backup and was able to restore. I know that's not much info but every little bit helps.
Twrp backup needed vs810pp
lukedobson1980 said:
I was able to root, de-bloat and install TWRP. I also made a backup and was able to restore. I know that's not much info but every little bit helps.
Click to expand...
Click to collapse
Could you please send me one of your backups so I can straighten. My system out ty
lukedobson1980 said:
I was able to root, de-bloat and install TWRP. I also made a backup and was able to restore. I know that's not much info but every little bit helps.
Click to expand...
Click to collapse
A backup of the stock recovery? If so I'd love one of those right now, can't install 5.1.1 OTA without it (and I don't think I can install 5.1.1 with TWRP without someone making a custom flashable ROM?).
Does anyone have a list of the bloatware I can safely disable or uninstall? A short description of it would also be nice if possible to see if it's something I need or not. I am rooted and also have the transpyre. Not a bad phone for the price.
Same here I've been scouring the net looking for a custom Rom for the transpyre but cannot seem to find anything for it, makes me wonder why this phone is not so cared for as If it were a contract phone
I know what you mean, I understand wasn't a very popular phone but I know you and I ain't the only ones that have it. Just have to be patient I guess and wait for someone that has worked on it to help is.
Sent from my VS810PP using XDA Free mobile app
I ended up using the software upgrade assistant to get my transpyre to lollipop at last now I just need a root guide for it
Edit: found a root for it, now all I need is a proper img file for a recovery
root for transpyre lollipop?
What did it take to get root on a transpyre with lollipop 5.1.1 ?
Sakujo said:
I ended up using the software upgrade assistant to get my transpyre to lollipop at last now I just need a root guide for it
Edit: found a root for it, now all I need is a proper img file for a recovery
Click to expand...
Click to collapse
I used the kinguser app to get root on it. I doubted it would work but It did The trick. make sure you update the King user app to prevent most apps from saying you don't have root, also, A strange thing happened though I used the jrummy root checker and now it says my phone is an Lg F60. Not sure if that's a bad thing. Also keep in mind you will lose your custom recovery I've been looking for ways to flash the twrp/cwm recoveries but it seems to be locked to the stock recovery. I've been putting it off but I'm going to test pushing the files through adb and see if that does anything. I'll let you know whether It bricks or not
GRRR transpyre root
Any confirmations on kinguser app root for transpyre?
Sakujo said:
I used the kinguser app to get root on it. I doubted it would work but It did The trick. make sure you update the King user app to prevent most apps from saying you don't have root, also, A strange thing happened though I used the jrummy root checker and now it says my phone is an Lg F60. Not sure if that's a bad thing. Also keep in mind you will lose your custom recovery I've been looking for ways to flash the twrp/cwm recoveries but it seems to be locked to the stock recovery. I've been putting it off but I'm going to test pushing the files through adb and see if that does anything. I'll let you know whether It bricks or not
Click to expand...
Click to collapse
I used king root to root mine and have had no issue. I used the one for without pc
Sent from my VS810PP using XDA Free mobile app
I unboxed by Transpyre yesterday, it was running 5.1.1
I also used kingroot straight from kingroot.net to root mine, then SuperSU Me Pro to remove the Kingroot Apps. Reliable root now, been debloating today.
Kingroot method works
I also used Kingroot to root my phone then replaced the kingroot app with SuperSU
lukedobson1980 said:
I was able to root, de-bloat and install TWRP. I also made a backup and was able to restore. I know that's not much info but every little bit helps.
Click to expand...
Click to collapse
Do you have a backup of your rom? and could you post a link to it?
I was able to root using Kingroot 4.5 and replace it with SuperSU using the "Super-Sume Pro 9.2.1 apk" All newer versions of the Super-Sume Pro .apk hung up during the first phase of its operation and all of the free versions of Super-Sume I had tried (the most recent) caused my phone to hang at the Verizon screen during reboot.
I found a YouTube video:
"How to Install CyanogenMOD 12 on the LG F60 and LG Tribute"
Which claimed the procedure was the same for the Transpyre (vs810pp) and included links to another video:
"How To Install TWRP Recovery on the LG F60, LG Tribute and LG Transpyre"
As well as a download link for "twrp-2.8.6.0-e2nav.img" which is supposed to be correct for the Transpyre (vs810pp) phone.
However after I installed "twrp-2.8.6.0-e2nav.img" I received an error during reboot: "Secure booting Error! Error Code : 1003" Afterword my phone would not do a factory reset, and only displayed that error message on every attempt..
I had since installed:
csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW07S65232BYAJX41F92ORK/VS810PU4_08_ARB01.kdz
(The factory 5.1.1 ROM which I found here in another thread) restoring the factory recovery ROM using the guide: "How to flash firmware to LG smart phone with LG Flash Tool 2014" I was able to repair the boot error.
How are you guys getting TWRP to work well? Would one of you be kind enough to point me in the direction of the the TWRP file that is successfully being used?
Would any of you guys currently running TWRP be able to provide your bootloader and dependency files?
If so would you kindly make them available over at :
xda-developers - Android Development and Hacking - Miscellaneous Android Development - [RECOVERY][e2nam] TWRP 2.8.5.0 touch recovery LG MS395
It appears that there may be another, far more advanced enthusiast (I believe the author of the "twrp-2.8.6.0-e2nav.img" I mentioned earlier) posting over there who could potentially be able to put together something useful for those of us running the Lollipop 5.1.1 factory ROM.
does anyone have a stock rom? Im seriously screwed here without one

Categories

Resources