Database Users

J500FN rapidly running out of space

As a bog standard user I naively assumed that I could put apps on my SD card as and when I wanted. Instead the majority refuse to be put there or cause problems.
If I root my Samsung J500fn (Marshmallow) will I be able to chose the location for putting apps? Can I get rid totally of the stuff Google/Samsung think I need but I never use? Can I make better use of my SD card that is practically empty? Are there any drawbacks to keeping Marshmallow as installed or would rooting overwrite it? Is there a better way than to root? Is "One Click root" safe to use? Am I better of using various programs like Odin, TWRP etc. mentioned in various threads here?
Thanks to any and all who can answer my questions. :fingers-crossed:
Anne

webelan said:
As a bog standard user I naively assumed that I could put apps on my SD card as and when I wanted. Instead the majority refuse to be put there or cause problems.
If I root my Samsung J500fn (Marshmallow) will I be able to chose the location for putting apps? Can I get rid totally of the stuff Google/Samsung think I need but I never use? Can I make better use of my SD card that is practically empty? Are there any drawbacks to keeping Marshmallow as installed or would rooting overwrite it? Is there a better way than to root? Is "One Click root" safe to use? Am I better of using various programs like Odin, TWRP etc. mentioned in various threads here?
Thanks to any and all who can answer my questions. :fingers-crossed:
Anne
Click to expand...
Click to collapse
Hi Anne,
We all have the same trouble with storage on our J5.
If you chose to root your phone then yes you will be able to uninstall alot of the bloat ware that is on your phone.
You will also have the option of using adaptable storage.
There are lots of threads on here that will guide you through the process. Just make sure that you read the guides properly and download and install the CORRECT zips.
I don't know if the one click root is safe to use.
I would advice installing TWRP and then flashing super su. Again all of the guides are on here.
If you do install TWRP via Odin then you will have the option of flashing custom ROMs..
Have a good look at the guides. Ask all the questions that you need to. People in here will be happy to help.
It's really nice to see you on here
Have fun
John

Don't need root for adoptable storage.

Hi
Did u get the info that you need ?

Rooting
johnhux7 said:
Hi
Did u get the info that you need ?
Click to expand...
Click to collapse
Hi again, thanks for asking.
I downloaded TWRP from https://www.androidfilehost.com/?w=files&flid=55922, version for SM-J500FN dated May 6, 2016. Also ODIN-v3.10.7 and SU SR4-SuperSU-v2.78-SR4-20161115184928 as well as the Samsung USB drivers. All check sums were fine. Odin 3 installed fine on my PC. I used Odin 3 to install the TWRP on my phone. However, when I try to go into Volume up - home - power on - I get a screen that does not resemble at all what I thought TWRP should look like.
I get the yellow/green Android thingy which says "installing system update" follows by "no command" followed by a screen which says:
Android Recovery
MMB29M.J500FNXXU1BPH1
samsung/j5nltexx/j5nlte
6.0.1/MMB29M/J500FNXXU1BPH1
user/release-keys
Use volume up/down and power. (all in yellow)
Followed by a menu which includes "apply update from SD card" but which doesn't install the SU zip file that I put in the download section of the SD card.
--------
So I am a bit lost and bewildered. Is the menu correct for TWRP? I haven't seen anything on the web or in YouTube that looks at all like what I'm getting. Did TWRP install properly - Odin 3 seemed to think so, but I'm beginning to wonder.
Any help, comment appreciated.
Anne

webelan said:
Hi again, thanks for asking.
I downloaded TWRP from https://www.androidfilehost.com/?w=files&flid=55922, version for SM-J500FN dated May 6, 2016. Also ODIN-v3.10.7 and SU SR4-SuperSU-v2.78-SR4-20161115184928 as well as the Samsung USB drivers. All check sums were fine. Odin 3 installed fine on my PC. I used Odin 3 to install the TWRP on my phone. However, when I try to go into Volume up - home - power on - I get a screen that does not resemble at all what I thought TWRP should look like.
I get the yellow/green Android thingy which says "installing system update" follows by "no command" followed by a screen which says:
Android Recovery
MMB29M.J500FNXXU1BPH1
samsung/j5nltexx/j5nlte
6.0.1/MMB29M/J500FNXXU1BPH1
user/release-keys
Use volume up/down and power. (all in yellow)
Followed by a menu which includes "apply update from SD card" but which doesn't install the SU zip file that I put in the download section of the SD card.
--------
So I am a bit lost and bewildered. Is the menu correct for TWRP? I haven't seen anything on the web or in YouTube that looks at all like what I'm getting. Did TWRP install properly - Odin 3 seemed to think so, but I'm beginning to wonder.
Any help, comment appreciated.
Anne
Click to expand...
Click to collapse
If your phone is looking like that then you have the wrong version of TWRP for the version of android that your using.
I did the same thing.
I hadn't got the time at the mo to find you the correct version but that is the problem for sure.
You want the one by Garnesh Varma which if on the Roms & kernels thread
John

johnhux7 said:
If your phone is looking like that then you have the wrong version of TWRP for the version of android that your using.
I did the same thing.
I hadn't got the time at the mo to find you the correct version but that is the problem for sure.
You want the one by Garnesh Varma which if on the Roms & kernels thread
John
Click to expand...
Click to collapse
Hi john,
Following your suggestion I downloaded the TWRP version http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 by searching for Garnesh Varma. It successfully installed, but the problem remains the same. I do not get the TWRP recovery page just the same as before.
I shall continue to look to see if I can find another version from Garnesh, although it seemed correct ie SM-J500FN Android version 6.0.1 Build number MMB29M.J500FNXXU1BPH1, security patch level 1 August 2016.
Will let you know how I get on.
Thanks again,
Anne

webelan said:
Hi john,
Following your suggestion I downloaded the TWRP version http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 by searching for Garnesh Varma. It successfully installed, but the problem remains the same. I do not get the TWRP recovery page just the same as before.
I shall continue to look to see if I can find another version from Garnesh, although it seemed correct ie SM-J500FN Android version 6.0.1 Build number MMB29M.J500FNXXU1BPH1, security patch level 1 August 2016.
Will let you know how I get on.
Thanks again,
Anne
Click to expand...
Click to collapse
Ahah! The trick was to turn off the phone and not to permit ODIN to do a reboot. I didn't know how to turn off so I pulled the battery. Then went into volume up - home - power on and got the correct menu. Whew. Rooted now according to root checker. Now to get some of the stuff off the phone and make some space.#
Thanks for your help,
Anne

webelan said:
Ahah! The trick was to turn off the phone and not to permit ODIN to do a reboot. I didn't know how to turn off so I pulled the battery. Then went into volume up - home - power on and got the correct menu. Whew. Rooted now according to root checker. Now to get some of the stuff off the phone and make some space.#
Thanks for your help,
Anne
Click to expand...
Click to collapse
Nice one. I'm pleased that you got it sorted !
Next you will be on the custom roms ! If you need any help just shout !
John

@webelan
Hello Anne!
Once you are rooted you can remove any Google/Samsung app. But removing some system apps can lead to bootloop. You can recover from bootloop by re-flashing stock rom.
I can make a flashable zip which removes unnecessary system apps, including the Google/Samsung apps which you want (you flash the zip in recovery and you're done). So let me know which Google/Samsung apps you wanna remove.
You can find some more basic informations in our Q&A thread: http://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-qa-thread-galaxy-j5-series-t3382922 .
I recommend you to try cm 12.1 (5.1.1 lollipop) by Nick Verse if you don't care about Samsung Camera, Memo and Browser. I use Open Camera, Color Note and Dolphin Browser (has sound/brightness sliders in videos) as alternatives. Unlike Touchwiz, CM 12.1 is faster than Touchwiz and has more free ram. But latest release has a bug (random reboot reported by users) which can be fixed manually. I'm running latest release without any problem.
Have a nice day!
Robert.
PS: You have a nice name

more woe
johnhux7 said:
Nice one. I'm pleased that you got it sorted !
Next you will be on the custom roms ! If you need any help just shout !
John
Click to expand...
Click to collapse
Don't know if I should start another thread but...
I used Aps2SD to create a second partition on my phone after making a backup of the SD card using that program. Restored the SD card and then I linked various apps to the new partition. When everything was done, and working, I used the option "Broken ap cleaner" just in case there were any residue files with "select all"
My error may have been to do a hard shutdown afterwards because now I get "Android System There's an internal problem with your device, and it may be unstable until you factory data reset." Then several aps, including a Google app, Photos, CM security and Gmail stop, in fact all those that run automatically at startup. Gmail and Google are on the internal drive now but were previously linked; CM is on the external partition still. The first thing after that I noticed after the hard shut down was that the icons for linked aps had disappeared and the aps keep stopping if I try to run them.
I read the Aps2SD FAQ and followed the two suggestions regard SU, ie "enable su at boot" and disabled "namespace separation" option.
Any suggestions? Should I
(a) do a "factory data reset"
(b) wipe the SD card and partition and completely reinstall the aps I want? Although if Google app is not working don't know if it can be reinstalled as I'm not sure which oneis meant.
(c) Bite the bullet and install a custom rom?
(d) something else?
Any help as usual very much appreciated,
Anne

webelan said:
Don't know if I should start another thread but...
I used Aps2SD to create a second partition on my phone after making a backup of the SD card using that program. Restored the SD card and then I linked various apps to the new partition. When everything was done, and working, I used the option "Broken ap cleaner" just in case there were any residue files with "select all"
My error may have been to do a hard shutdown afterwards because now I get "Android System There's an internal problem with your device, and it may be unstable until you factory data reset." Then several aps, including a Google app, Photos, CM security and Gmail stop, in fact all those that run automatically at startup. Gmail and Google are on the internal drive now but were previously linked; CM is on the external partition still. The first thing after that I noticed after the hard shut down was that the icons for linked aps had disappeared and the aps keep stopping if I try to run them.
I read the Aps2SD FAQ and followed the two suggestions regard SU, ie "enable su at boot" and disabled "namespace separation" option.
Any suggestions? Should I
(a) do a "factory data reset"
(b) wipe the SD card and partition and completely reinstall the aps I want? Although if Google app is not working don't know if it can be reinstalled as I'm not sure which oneis meant.
(c) Bite the bullet and install a custom rom?
(d) something else?
Any help as usual very much appreciated,
Anne
Click to expand...
Click to collapse
It sounds like the app has been corrupted, don't really know how to best advice you.
It sounds like you have to do s factory reset.
I would install a custom ROM.
The only trouble with this is that all the roms have just been shut down so you will have trouble downloading any.
Why model do you have ?
If you want to use a custom ROM pm me and I will send you a link.
The custom roms are much better (in my opinion )
John
Sent from my j5nltexx using XDA Labs

#Henkate said:
@webelan
Hello Anne!
Once you are rooted you can remove any Google/Samsung app. But removing some system apps can lead to bootloop. You can recover from bootloop by re-flashing stock rom.
I can make a flashable zip which removes unnecessary system apps, including the Google/Samsung apps which you want (you flash the zip in recovery and you're done). So let me know which Google/Samsung apps you wanna remove.
You can find some more basic informations in our Q&A thread: http://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-qa-thread-galaxy-j5-series-t3382922 .
I recommend you to try cm 12.1 (5.1.1 lollipop) by Nick Verse if you don't care about Samsung Camera, Memo and Browser. I use Open Camera, Color Note and Dolphin Browser (has sound/brightness sliders in videos) as alternatives. Unlike Touchwiz, CM 12.1 is faster than Touchwiz and has more free ram. But latest release has a bug (random reboot reported by users) which can be fixed manually. I'm running latest release without any problem.
Have a nice day!
Robert.
PS: You have a nice name
Click to expand...
Click to collapse
Hi Robert,
Thanks for the offer. So far I have not deleted anything but have used software to partition my SD card and to move stuff out of internal memory onto it - or rather link it. I managed to mess up a bit but seem to have recovered - or at least got a phone with items I want to use. Next week when I've more time I'm hoping to install a Custom ROM. In the meantime I've spent what little time available trying to read as much as I can so that when I do put a Custom ROM on, it goes right first time.
Best wishes,
Anne

webelan said:
Hi Robert,
Thanks for the offer. So far I have not deleted anything but have used software to partition my SD card and to move stuff out of internal memory onto it - or rather link it. I managed to mess up a bit but seem to have recovered - or at least got a phone with items I want to use. Next week when I've more time I'm hoping to install a Custom ROM. In the meantime I've spent what little time available trying to read as much as I can so that when I do put a Custom ROM on, it goes right first time.
Best wishes,
Anne
Click to expand...
Click to collapse
Hi Anne!
Note that once you flash TWRP, Knox will become 0x1 (initially is 0x0) which means that you void the warranty. In my opinion, I don't care about the warranty because I prefer to have a better experience with my phone. I cannot live without root after I rooted a phone for first time
Regarding the ROM, if you wanna try cm12.1 (which I recommend it, best ROM which is closest to AOSP and never lagged) I'll recommend you to wait some more time because I'll download CM 12.1 sources and build a new update with the help of Nick Verse . He doesn't have enough space on his PC to have both cm12 & cm13 sources. I'm currently trying to extend my Linux partition to have enough space to build though. Is needed about 80gb in total average and I have about 20 and can't resize my partition. I might try to reinstall Linux.
If you have any other question, feel free to ask here (new thread if it's related to something else) or PM me.
Have a nice day!
Robert.

Having a similar issue, i have got my phone so it boots to TWRP 3.1.1-0 but cannot find a ROM file that will install, they all seem to be for j5nlte, even if the file name states j5nltexx. I have tried to ammend/remove the assert lines in the install package to no avail...
any advice would be good
Thanks in advance
PB

ashyx said:
Don't need root for adoptable storage.
Click to expand...
Click to collapse
Then what to do

#Henkate said:
Hi Anne!
Note that once you flash TWRP, Knox will become 0x1 (initially is 0x0) which means that you void the warranty. In my opinion, I don't care about the warranty because I prefer to have a better experience with my phone. I cannot live without root after I rooted a phone for first time
Regarding the ROM, if you wanna try cm12.1 (which I recommend it, best ROM which is closest to AOSP and never lagged) I'll recommend you to wait some more time because I'll download CM 12.1 sources and build a new update with the help of Nick Verse . He doesn't have enough space on his PC to have both cm12 & cm13 sources. I'm currently trying to extend my Linux partition to have enough space to build though. Is needed about 80gb in total average and I have about 20 and can't resize my partition. I might try to reinstall Linux.
If you have any other question, feel free to ask here (new thread if it's related to something else) or PM me.
Have a nice day!
Robert.
Click to expand...
Click to collapse
Please work on camera that is the only thing cm 12.1 lackss thank youu

The Simple Guide To Rooting The Alcatel Idol 4

Credit goes to dbgr for finding this:
https://forum.xda-developers.com/idol-4s/how-to/6055u-root-method-t3598947
Link to download .rar:
https://mega.nz/#!U24zwYbQ!MwbIX_D01OyHHldd8c_9iCmht6wzcw1duNpGO-PRyWI
This is just a simpler, more detailed guide on how to root this phone.
Forgive me for the lack of pictures, its pretty straightforward anyways. I have included a .rar with this post that has all the essential files you will need.
(I only compressed the .rar, everything else credit goes to the creators)
1. Download the rootpackage.rar i have included, and decompress to somewhere safe.
2. Install SugarQct and install the drivers that came with it. (In the SugarQct installer, not the usb driver folder)
3. After that has finished, open the usb driver folder and run the setup.vbs script there. It should only take a second or two to run.
4. Plug phone into pc.
5. Place supersu.zip onto phone. You can put this anywhere, doesn't really matter.
6. Turn phone off and place into download mode. (Phone must be plugged in to allow download mode)
4. Open sugar with phone plugged in. Be sure to upgrade sugar if you can't see the 6055u in the list.
Set to 6055u, go to options, select save user data. Now press upgrade.
5. While sugar is downloading overwrite the r*****.mbn in bin/6055-*****. This folder appears once you start to download to the phone. You must rename the twrp_recovery_idol4_6055.img to the name of the r*****.mbn.
6. Overwrite again while files are being written. Do this as many times as you please. I only overwrote it more than once as a safety precaution.
7. Before sugar has completed fully, but after files are written, this should be around the time when it starts to download more files. As long as the writing completes you are good to go.
8. Turn phone on and enter recovery mode (power + volume up).
9. In the custom recover menu tap install and install the supersu.zip from the directory you placed it in.
10. Give it a couple of seconds (mine took 30 or so)
11. Allow phone to be rebooted and its now rooted!
Now I've had some interest in using magisk instead of supersu, but i haven't been able to install it after supersu. Choose your rom to flash wisely, as its a pain in the ass to go back from.
Please enjoy your newly rooted Alcatel Idol 4!
Thanks all!
P.S. If someone can dump their standard rom before they flash supersu.zip onto their phone, i'd like to try and find a way to get a custom rom goin and that would help.

I'm not seeing the download for the .RAR file. Am I missing something?

SeanMcCarte said:
I'm not seeing the download for the .RAR file. Am I missing something?
Click to expand...
Click to collapse
I thought i attached it to the thread, give me a second and i'll try again.
Edit:
It seems my rar is too large, i'm headed to work now, but i'll try and get something uploaded in a bit.

Thank you. Much appreciated. Also,can I unplug the phone before rebooting to recovery,or does it have to be plugged in!

SeanMcCarte said:
Thank you. Much appreciated. Also,can I unplug the phone before rebooting to recovery,or does it have to be plugged in!
Click to expand...
Click to collapse
As far as i know it doesn't have to be, but when i was successful i believe i had the phone plugged in. I did try to do somethings earlier today and unplugged the phone, and it was not successful. I do not know if it was because i unplugged the phone or if it was because i had failed to rewrite the recovery flash.

Thank you. I actually didn't want to wait for .rar so I just pieced the files from the forum here. Thank you anyway,at least somebody else will get the RAR. Also,my phone was plugged in when it worked.

I got magisk working for me I unistalled super super went into twrp and installed magisk ( I needed magisk to play fire emblem heroes lol) I'm not sure if I did something else but that's what I remember doing

Is this guide working for all the idol 4 variants or just for the cricket one? I've got the 6055k and I'm wondering if this guide works for my phone too.

scofield119 said:
Is this guide working for all the idol 4 variants or just for the cricket one? I've got the 6055k and I'm wondering if this guide works for my phone too.
Click to expand...
Click to collapse
Theres another guide for the 6055k, i'm not sure if this will work for that one. I know it works for the cricket version and i see no reason why it wouldn't work for the 6055k, but it is a better idea to follow the guide made for the 6055k.

link22534 said:
I got magisk working for me I unistalled super super went into twrp and installed magisk ( I needed magisk to play fire emblem heroes lol) I'm not sure if I did something else but that's what I remember doing
Click to expand...
Click to collapse
Would you mind checking if snapchat works on magisk? I know it doesn't work on supersu, and i've unrooted my phone because i was having troubles getting it installed after supersu.

NeonWhitey said:
Would you mind checking if snapchat works on magisk? I know it doesn't work on supersu, and i've unrooted my phone because i was having troubles getting it installed after supersu.
Click to expand...
Click to collapse
Yep it works I had to change a setting to get magisk hied working it was magisk core only mode and I pass the netsaftey check

link22534 said:
Yep it works I had to change a setting to get magisk hied working it was magisk core only mode and I pass the netsaftey check
Click to expand...
Click to collapse
Thanks for the info, but funnily enough i'm having difficulties getting the damn thing rooted again.

Thanks for the write up, I've flashed and reflashed many times... you have to be carefully about when you interrupt the process. Also know that a newer version is out. Cheers mate.

I'm not sure if it's the latest version of Sugar, but I've been trying so many times, but to no avail. Has anyone had any luck on the new version?
SUGAR QCT_SP V11.3.0
I've gotten to the point that when I start the upgrade with Sugar, it says my phone is already rooted. However, when I try to access Recovery, there is no option to install TWRP. It looks like it just loaded the same old recovery...no matter how fast and how many times I replace the Rxxxxxx.mbn file.
Cheers,
Wickster

6055p
is there any guide to root 6055p model

no luck getting this to work guys, could really use some help

Having the same problems as PizzaG - tried all the timing tips no TWRP
Having the same situation as PizzaG - same Cricket version, using the newer version of Sugar QCT 11.1.3. I've tried starting right after it reaches the last written file (4095M), Ive even tried waiting until you get the vibrate and Alcatel logo (which happens at the very end of the download, but was someone's tip), same story, boots into Android recovery. Any other tips?

Possible Solution to Rooting Troubles
I was having the same troubles as the above posters. What seemed to be the problem was that I had set a pin code to unlock my device, which made it encrypted. Unfortunately, the only way to remove a pin is to do a factory reset. Anyway, I did a factory reset and ran sugar immediately after - making sure to start the phone before sugar finished - and it worked! Perhaps there is something simpler to do and I didn't have to do a factory reset, but I don't know what that is, and this worked.

Someone have try with the 6055A?

hmm, im noticing mine says encrypted as well but i never set anything for security. just the swipe. @ ThisEndsInTears did you do a factory reset from stock recovery or from withing the phone settings? Thanks much, hopefully one step closer to getting this rooted. Y has nobody developed cm for 6.0.1 for this? cm13 im pretty sure it is

Rooting SM-S920L

Tracfone version
I'm having no luck with Kingroot. It says no root available for device.
According to 'one-click-root' website, the device has no way of rooting it.
Is there any updated information?
.
device specifics:
model: SM-S920LZAATFN
android: 5.0.2
build: LRX22G.S920LUDU1APK2
hardware version: S920L.03
.
[edit: was hoping to change the title to reflect that this post is about the tracfone version]

TWRP recovery method?
TWRP recovery method?
I've read that a phone may possibly be able to be rooted by using odin to download a TWRP recovery, then booting into that new recovery using hardware keys, instead of rebooting normally. And this results in a rooted phone?
I think I have seen a TWRP that may work with this phone. Any help is appreciated. I'd like to be able to update this thread to include a step by step approach to this and other versions of the same model 920.
I'll continue to post updates as I discover more information.

DIY time : crash course in brain surgery
Ok, so I've read a bit of stuff in the forums on the SM-S920L, mostly about the StraightTalk variant, which apparently uses the same system rom, though I'm not so sure.
At any rate, rather than just throw carp at the phone and hope it sticks, I'm going to teach myself how to do it all myself, a-z, 1,2,3... etc., starting with making stock images of the various components, for recovery purposes. Perhaps the phone can be used as a TracFone again someday, though I have no desire to do so, having already bought another for cheaper that even works better, though not as fancy, just newer.
So, I'll leave it here for now and just update the primary with new information as I discover it, starting with the extraction of the stock images, hopefully without goofing up the phone, lol.
This is an unpopular phone, at least for hackers. But it will be a good tool for expanding my knowledge.
Any help appreciated, such as, 'Is this even necessary? There are files here here and here that will do it all'.
(lol, nope... so far I've discovered there is no root option, kingroot no work, etc. There seems to be no posts with information specifically regarding the TracFone 'variant' of this model. It suggests that i can use the StraightTalk files for it, which may work, but there are many questionable unanswered problems.)

friimynd said:
Ok, so I've read a bit of stuff in the forums on the SM-S920L, mostly about the StraightTalk variant, which apparently uses the same system rom, though I'm not so sure.
At any rate, rather than just throw carp at the phone and hope it sticks, I'm going to teach myself how to do it all myself, a-z, 1,2,3... etc., starting with making stock images of the various components, for recovery purposes. Perhaps the phone can be used as a TracFone again someday, though I have no desire to do so, having already bought another for cheaper that even works better, though not as fancy, just newer.
So, I'll leave it here for now and just update the primary with new information as I discover it, starting with the extraction of the stock images, hopefully without goofing up the phone, lol.
This is an unpopular phone, at least for hackers. But it will be a good tool for expanding my knowledge.
Any help appreciated, such as, 'Is this even necessary? There are files here here and here that will do it all'.
(lol, nope... so far I've discovered there is no root option, kingroot no work, etc. There seems to be no posts with information specifically regarding the TracFone 'variant' of this model. It suggests that i can use the StraightTalk files for it, which may work, but there are many questionable unanswered problems.)
Click to expand...
Click to collapse
Definitely don't use kingroot.
Do you have a laptop or pc? If so I can help you out. I have the same phone. Mine is straight talk, but it's sm-s920l a tracefone just through straight talk.

c3p0u812 said:
Definitely don't use kingroot.
Do you have a laptop or pc? If so I can help you out. I have the same phone. Mine is straight talk, but it's sm-s920l a tracefone just through straight talk.
Click to expand...
Click to collapse
Ya I got the straight talk, I have been using king root but I totally bricked and wiped my phone on purpose because I wanted to start fresh and let it update. Having a problem though I used twrp and nuked all my ****, or so I thought. I'm trying to OTA update I'm currently on 5.0.2 and it's saying I have a system update and even after I checked everything to be deleted it still says error and one of my files is modified or some**** like that. I think it's like admin.prop so **** it. I do however want to go systemless root. What do you suggest is the best root and rom for our device?
To answer op question yes your phone is the same as ours. Mine even shows tracphone on boot.

Inuyashian said:
Ya I got the straight talk, I have been using king root but I totally bricked and wiped my phone on purpose because I wanted to start fresh and let it update. Having a problem though I used twrp and nuked all my ****, or so I thought. I'm trying to OTA update I'm currently on 5.0.2 and it's saying I have a system update and even after I checked everything to be deleted it still says error and one of my files is modified or some**** like that. I think it's like admin.prop so **** it. I do however want to go systemless root. What do you suggest is the best root and rom for our device?
To answer op question yes your phone is the same as ours. Mine even shows tracphone on boot.
Click to expand...
Click to collapse
Well for our phone there is only one custom ROM and it's LineageOS 13.0 https://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-13-0-galaxy-t3491494 It's android 6.0 and it can be rooted too. It's not being updated anymore for our device as far as I know. There is Lineage 14.* but not for our variant.
For systemless root you'll want to go with Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 I had Lineage, and don't get me wrong it's worth checking out, but I downgraded back to stock and went with Magisk. You can even get Xposed throughMagisk.
If I was you, I would flash back to stock. You can go to this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and download the first two, Stock Boot and Stock Recovery. Make sure to unzip them because you need the md5 files they extract. I'd wipe everything again and then get into download mode. On your PC fire up Odin, I'm using version 3.10 http://odindownload.com/download/clean/Odin_3.10.0.zip Click BL use the stick boot md5 and then under ap use the stock recovery md5. When it reboots and you set it up do not turn reactivation lock on.
If you don't already have Magisk on your sd card get it on there and install through twrp. It will ask if you want to root. Might make a back up after. I always make backups and then transfer from sd to my pc. I can restore to like 6 different versions of my phone right now lol I'm no expert, I haven't been messing around with all this for long so I hope that all makes sense. :fingers-crossed:

c3p0u812 said:
Well for our phone there is only one custom ROM and it's LineageOS 13.0 https://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-13-0-galaxy-t3491494 It's android 6.0 and it can be rooted too. It's not being updated anymore for our device as far as I know. There is Lineage 14.* but not for our variant.
For systemless root you'll want to go with Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 I had Lineage, and don't get me wrong it's worth checking out, but I downgraded back to stock and went with Magisk. You can even get Xposed throughMagisk.
If I was you, I would flash back to stock. You can go to this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and download the first two, Stock Boot and Stock Recovery. Make sure to unzip them because you need the md5 files they extract. I'd wipe everything again and then get into download mode. On your PC fire up Odin, I'm using version 3.10 http://odindownload.com/download/clean/Odin_3.10.0.zip Click BL use the stick boot md5 and then under ap use the stock recovery md5. When it reboots and you set it up do not turn reactivation lock on.
If you don't already have Magisk on your sd card get it on there and install through twrp. It will ask if you want to root. Might make a back up after. I always make backups and then transfer from sd to my pc. I can restore to like 6 different versions of my phone right now lol I'm no expert, I haven't been messing around with all this for long so I hope that all makes sense. :fingers-crossed:
Click to expand...
Click to collapse
Haha ya it does I just wish they didn't treat our phone like it has Ebola or some****. All kinds of **** for the other ones. I agree on the magisk because I really want to try that out. Alright thanks for all the helpful links I come to this site to find **** for ours and I end up looking at a bunch of cool stuff I can't have.
I'm waiting on the pixel 2 XL before I upgrade. We just missing out on too much stuff. I think magisk will keep me busy in the meantime though. Thanks again man I'm Soo add once I get here on all the stuff then I wonder well will this work or this work and by then just like awwww **** it.

Inuyashian said:
Haha ya it does I just wish they didn't treat our phone like it has Ebola or some****. All kinds of **** for the other ones. I agree on the magisk because I really want to try that out. Alright thanks for all the helpful links I come to this site to find **** for ours and I end up looking at a bunch of cool stuff I can't have.
I'm waiting on the pixel 2 XL before I upgrade. We just missing out on too much stuff. I think magisk will keep me busy in the meantime though. Thanks again man I'm Soo add once I get here on all the stuff then I wonder well will this work or this work and by then just like awwww **** it.
Click to expand...
Click to collapse
Hey, I thought I'd let you know LineageOS 14.1 is available to us now. I can't find a specific thread on it, but you can download it from http://grandprime.ddns.net/jenkins/job/LOS_Builds/# Flash it with twrp. You will want to flash that and then flash open gapps [ARM - 7.1] and then whichever from here http://opengapps.org/ I did all that first, set it up rebooted and then installed Magisk.
It has Substratum pre-installed and it let's you theme it nicely. There is only an unofficial xposed version so far.
Anywho, thought I'd throw that out there.

thanks for the replies, gives me inspiration to keep on trying; the phone is pretty ho-hum with default stuff and the general blah blah of social media, etc.;
thanks for the tips, feel free to post more details as they come in

My Turn
I'm about to try and put 14.1 and Magisk on mine. Wish me luck!

downloading twrp recovery and rooting
in google search up twrp click on the first link then click on devices on the top right corner then search up your phone download the twrp.img.tar file
power off your phone and press volume down + home button + power button to boot into download mode
in odin select AP then select the twrp.img.tar you downloaded then press start
your phone will reboot then download the SuperSU zip file
then go to settings then go to find my mobile you have to get a samsung account then you will see reactivation lock option turn that off
then power off your phone then press volume up + home button + power button to reboot into twrp recovery
once booted tap the install option then select where you downloaded the supersu zip file swipe to flash it once done flashing you will see the reboot system option to reboot your phone
then your phone should be rooted!

Upgrading to Magisk 17.3 when you already have Nov (Pie) patch and TWRP

Installed the November OTA successfully yesterday. I've got TWRP on both partitions, Magisk 17.2, and MM (Magisk Manager) 6.0.1 already installed.
The changelog for Magisk 17.3 discusses better handling for phones like ours with A/B boot partitions. Apparently, MM 6.0.1 is already equipped to handle installs for A/B boot partitions, but I don't see much discussion here about it. I'd like to know if I can simply install 17.3 directly from MM's "Install" button. According to the changelog, it should patch the image properly. I'm concerned about two things:
There is some caveat about the boot partition needing to be stock (if I'm understanding that correctly). If both of mine have TWRP (as I'm sure most of you do as well), what would happen?
Would I need to remove my screen lock/fingerprint details prior to doing this?
If I need to flash a stock boot prior to using that MM install feature, I figure I might as well take it all directly into TWRP, and flash everything there. If someone would be so kind to detail the simplest steps for that process, I'd greatly appreciate it! And I assume removing the screen lock/fingerprint details are required for this approach?
Thanks in advance!

Go into magisk manager and hit install.
Then hit direct install (recommended).
Install
Reboot
Sent from my PH-1 using XDA Labs

avd said:
Go into magisk manager and hit install.
Then hit direct install (recommended).
Install
Reboot
Click to expand...
Click to collapse
Thank you for the suggestion. Is your phone set up similarly to mine, and how many times have you done this yourself so far? What concerns me is that some have said you can expect "strange" things to happen (later) if you're not on stock boot. It's a shame it can't preemptively stop you when that's the case.

BigMatza said:
Thank you for the suggestion. Is your phone set up similarly to mine, and how many times have you done this yourself so far? What concerns me is that some have said you can expect "strange" things to happen (later) if you're not on stock boot. It's a shame it can't preemptively stop you when that's the case.
Click to expand...
Click to collapse
I've been doing this forever. If your phone is rooted upgrades will work. I was able to downgrade successfully from a borked 17.4 but I lost the database and had to authorize all my apps from scratch.
Sent from my PH-1 using XDA Labs

avd said:
I've been doing this forever. If your phone is rooted upgrades will work. I was able to downgrade successfully from a borked 17.4 but I lost the database and had to authorize all my apps from scratch.
Click to expand...
Click to collapse
Thanks for your help. I applied via "Direct Install" as you suggested, and the update appears to have been successful. I did not remove my lock pattern, and TWRP works just fine with the existing pattern unlock to decrypt.
I did notice a few interesting changes after reboot:
No extended reboot menu when holding the power button (though I can't recall if I ever had this on my PH-1)
When connecting the phone to my PC, the "control" has reverted back to the PC as the controller, instead of the phone. Applying the 17.2 Magisk zip in TWRP (when I did the OTA patch a couple days ago) did not have this affect.
One unfortunate side effect that occurred after the OTA patch a few days ago is that I can't "Enable Fingerprint Authentication" in MM. The toast states "Authentication Failed" when I attempt to turn the switch on. I thought 17.3 might fix this, but it did not. I'm pretty sure this has to do with my clearing my lock pattern prior to the OTA patch. Clearing the MM data didn't help. Any thoughts on this?

Patched 11.0.12.12.KB05AA ROM for rooted users - install from Fastbootd!!!

[UPDATE]:
**********
I got sick of my phone telling me I needed to update but I couldn't because I'm rooted. So finally got around to patching the last full ROM today w/ the incremental.
This is the fastbootd w/ flash_all.bat script to update to 11.0.12.12.KB05AA. The package for KB05AA (Global/US) is not yet available, hence I'm still making it available here. Be sure to alter the flash script (remove the "rem" before boot.img and recovery.img if you DO NOT want to keep your custom kernel + TWRP) ****************
3.14 GB file on MEGA
mega.nz
THIS IS ONLY FOR 11.0.9.9.KB05AA, BUT READ IT ANYWAY!!!!: ***************
I think this is the first time anyone has actually made a working incremental update for a rooted OOS device, or any with a payload.bin update method that I know of. This method doesn't require any wiping and TWRP / rooted boot.img / custom OOS kernel can be installed right after the script finishes (or left on the device), and you don't even change your active slot (usually, incremental updates will flash to the inactive slot).
I won't get into that many specifics except it was EXTREMELY DIFFICULT, but it works now. Read here if you want to do it yourself in the future, or on another phone. Should work on just about any phone that uses payload.bin files https://forum.xda-developers.com/t/...11-0-9-9-kb05aa-posted.4314677/#post-85425949
You may have to edit the .bat file to pick your RAM type (the lp5 ones are for devices with LPDDR5; it is preset for most of the phones using the LPDDR4 RAM). On the Op8T at least you can do this from adb shell:
adb shell getprop ro.boot.ddr_type; where a 0 is LPDDR4 and 1 is LPDDR5 ram. If it's 1 returned, you need to flash the lp5 files instead of the same named otherwise files in the .bat file (so edit it).
That weird -cow stuff is temp files that prevented the update from working. Not documented anywhere I could find (well, minimally explained by Google), took hours to figure out they were filling the super partition up. I had to re-engineer a Linux project (linked above) to get this working, and have officially updated from 11.0.8.13 to 11.0.9.9 COMPLETELY now. While rooted, without switching slots, and TWRP installed.
You just have to ensure you're on the latest ADB and Fastboot tools and an adb reboot bootloader, followed by a fastboot reboot fastboot should get you there. You can check with: fastboot getvar is-userspace
If it says yes, you're in fastbootd. It actually will work with TWRP installed, I found out later, as long as you reboot in TWRP to fastboot and confirm with the command above you're in fastbootd.
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows/releases/tag/v1.7 has a script that will get you the Latest ADB and Fastboot and put it in a folder for you.
I uploaded it to Mega. Just use some common sense and look at the flash_all.bat file before flashing. I'd write more but I'm tired as hell from getting this working. Now we'll never have to wait for an incremental update while rooted again, at least in the foreseeable future.

I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145

g96818 said:
I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145
Click to expand...
Click to collapse
That never worked for me and others, Always resulted in either bootloop or booting back to previous build

nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.

g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....

nujackk said:
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....
Click to expand...
Click to collapse
It's good that you found a band-aid fix.

nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
Of course I tried that solution first, it didn't work on my device.
I'm glad it did on others' devices, kudos to you for posting it (and I DO appreciate your work), but this is the only one that worked on mine. Why? Who knows. I also followed another guide that didn't work. Or else I wouldn't have wasted all my time making this (it took many, many hours to assemble). I'm not saying it's the best solution (I really hope someone just uses what I put in the other thread and assembles it into an easier format for others to use), but I have a full time job (2 actually) so I can't work on it anymore. But it works, no data loss, and TWRP can be installed. Until the next incremental update comes out, then I'll post another version using the tools I used for this, if your build doesn't work on my device. But only when I have the time...

g96818 said:
It's good that you found a band-aid fix.
Click to expand...
Click to collapse
LoL band-aid fix... Call it whatever you want, it works.
It's actually a patched 11.0.8.3.KB05AA with the incremental update applied to it for 11.0.9.9.KB05AA. So it flashes to the active slot and TWRP / rooted custom kernel can all be installed at the same time, even while you are still rooted with Magisk, and even if TWRP is installed. No data loss. I never claimed perfection on this project, just that it works for me.
Keep doing what you're doing, I'll keep doing what I'm doing. We both just aim to help others anyway. I just couldn't get any other method to work so I came up with this one, extending on the incomplete / abandoned work of others. I didn't come up with Payload extraction. Never claimed to. I didn't come up with fastbootd flashing either.
All the forked and modified code is at my GitHub repo. The fork goes back to several other devs' forks (mine is the 3rd modified fork).

Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.

mslezak said:
Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.
Click to expand...
Click to collapse
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot

5star02707 said:
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot
Click to expand...
Click to collapse
I think maybe you misunderstood what I did in this thread. I patched a full ROM with the incremental update of 11.0.9.9.KB05AA. So while OnePlus does not have a full ROM available for download (yet), it is available for download here.
Yeah the method you propose is the "normal" rooted way, but if you're rooted already it forces you to full ROMs not OTAs. You'll be on 11.0.8.3.KB05AA. The goal here is to get on 11.0.10.10.KB05AA (someone NOT ROOTED could download the OTA update using Oxygen Updater and upload it here so I could make a patched version for those that want to keep their root / custom kernel / TWRP / etc and avoid the hassle of unrooting first, which wipes your data partition). At least my Oxygen Updater won't let me download incremental updates even with Magisk Images removed (don't try this unless you're on Op8 / Op8 Pro; some people are having big system update issues on Op8T incremental hence why this thread exists.) It jacked up my system pretty bad (Magisk images removed, Settings / System / System Updates method) until after a boot.img and super restore from TWRP. Not all devices were setup the same (mine is a US carrier converted to US KB05AA). To my knowledge, no direct download has been posted for KB05AA incremental update. Here or on TG. If you have found one, please post a link here. The only one out I've seen works on European ROMs. OnePlus always does KB05AA last for whatever reason.

11.0.10.10.KB05AA posted with caveats - please back up your data as suggested in case the Phone Services APK doesn't fix your SIM after a flash, and you end up formatting the data partition. You may want to try some other methods or just plan on restoring (not with TWRP Alpha in my experience).

mslezak said:
Guys, bad news. So 11.0.10.10.KB05AA incremental does something to the data partition and kills your SIM access.
...
Click to expand...
Click to collapse
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).

BillGoss said:
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).
Click to expand...
Click to collapse
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.

@mslezak, When I get an update I:
- use a terminal session (you could also use ADB) to restore the stock boot and recovery (this way I don't lose root yet)
- install the update but don't reboot
- copy the new boot image and patch it
- turn on airplane mode (to avoid SafetyNet and certification issues in the next step)
- reboot the phone and the updated system comes up
- flash the patched boot image and TWRP in fastboot/bootloader
- reboot and disable airplane mode
This is basically @osm0sis' process from https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
No, I'm not saying flash to both slots, because that will make it impossible to fall back to the current system if the update fails (though this is meaningless if you're manually flashing partitions).
I've got into the habit of syncing active to inactive (after I'm happy with the update) simply because it's required when going from OOS to a custom ROM (I use a shell script based on the LineageOS sync zip). And, after the sync, I can now access the data partition from the inactive slot (which wasn't the case just after the update due to the different keys).

mslezak said:
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.
Click to expand...
Click to collapse
Thats not very hacked/hacked at all, and quite a few use that setup

xstefen said:
Thats not very hacked/hacked at all, and quite a few use that setup
Click to expand...
Click to collapse
LoL I gave up fastbootd flashed to 11.0.10.10.KB05AA and formatted data, let Google download everything it backed up, and am back in business. Just have a lot of apps to login to / Magisk modules to add / etc.
So yeah my patched 11.0.10.10.KB05AA works but the data must be formatted or the SIM doesn't work (at least for me; I don't know if anyone else has tried it since I just posted it a few hours ago; it could be that it works for some without causing issues, I don't have any idea). The goal was to not have to mess up the data partition.... but I can't control what OnePlus does in their updates... Try what worked for others posted here first I'd suggest, or just make solid backups of everything knowing you're going to likely need to reinstall / re-login to everything and format the data partition. New pin, new fingerprint, etc. Re-login to your wifi blah blah.
It's still a full unreleased ROM so I posted it for those that don't mind taking backups (outside of TWRP) if they want to keep root & TWRP on the new release... Yeah a pain to setup if you aren't warned to use another backup method (maybe there is a better backup method, maybe Migrate (app store early access) is developed enough for easy transfer now, I know many people said it worked well in the past but haven't been following the updates. Still free).

It dawned on me later that since the only thing that didn't work using this method going from 11.0.9.9.KB05AA to 11.0.10.10.KB05AA was phone services, that I should just include the working version in this post. Since I already did it the hard way and restored everything back to normal. AS I SAID ABOVE, IF PHONE SERVICES ISN'T ENOUGH TO FIX THE ISSUE, PM ME AND I CAN EXTRACT MORE RELATED FILES UNTIL IT WORKS AGAIN. Unfortunately, I can't just downgrade to 11.0.9.9.KB05AA and keep trying fastbootd over and over again as I don't have the time.

g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
The whole point of this is to AVOID the unbrick tool, reinstalling an outdated version, updating each new ROM build since the brick tool was made, and starting over clean. I think... Have a hunch at least we're almost there on 11.0.10.10.KB05AA with an APK install... Although just backing up everything first will always work (if you don't mind formatting your data partition) just as it's posted here already. Always an issue for us rooted users (especially on Global) since we're always last in line to get a full ROM. This IS a full ROM, payload extracted and patched with incremental updates. Still not available from OnePlus Global (KB05AA) as I checked today, so still relevant.

Ladies and Gents,
I have removed some off topic posts from this thread because I believe we could express the same meaning in more civil words. Please try to do that from now on.
Thanks.
Jerry
FSM