Related
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
LordGrahf said:
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
Click to expand...
Click to collapse
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Thank you sir!
obsanity said:
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Click to expand...
Click to collapse
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
I'm kinda curious myself. I had no idea root killed OTA's. Maybe I wouldn't have done that if I knew that. I'm very new to the Nexus device. It's my 1st. I unlocked the bootloader and rooted already.
Sent from Mark's Nexus 6
crowbarman said:
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
LordGrahf said:
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
Click to expand...
Click to collapse
not sure what you mean by GI, but according to some others, after uninstalling root via SuperSU an OTA will still not install. This should not be the case unless the boot or recovery images are modified. Easily fixed by following the procedures above to fastboot the stock images on your phone.
kjnangre said:
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
Click to expand...
Click to collapse
Yes, it behaves exactly the same.
crowbarman said:
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
obsanity said:
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
Click to expand...
Click to collapse
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
crowbarman said:
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
Click to expand...
Click to collapse
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
obsanity said:
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
Click to expand...
Click to collapse
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
obsanity said:
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
Click to expand...
Click to collapse
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
LordGrahf said:
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
Click to expand...
Click to collapse
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
obsanity said:
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
Click to expand...
Click to collapse
There is an argument that publishing the method would allow Google to close it that much quicker, I suppose.
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
I assume that the encryption doesn't get in the way of being able to flash the images?
When I went from 5.0 to 5.0.1 on my old Nexus 5 all I did was flash the two new 5.0.1 images I extracted from the full factory image, then re-rooted. This is far cleaner than reverting back to the previous image then doing an OTA. I've not had to update my N6 yet so I don't know if my method will work still, but I hope it does.
Chainfire said:
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
Click to expand...
Click to collapse
Thanks for the additional information.
I did spend a fair amount of time reading your documentation but failed to utilize a hex editor. I am not 'whining' about the lack of open source, rather, simply mildly surprised, but your website aptly describes the challenges with 5.0. Many are used to various root methods being available.
Your solution is fine with me.. I love your work.
Edit: I thought I'd add that the discussion has devolved from the OP, which was whether an OTA can be applied after uninstalling root. The answer was no, due to the unknowns about what still might be modified following the uninstall via SuperSU.
Hey, so I've rooted and unlocked the bootloader of my htc desire. I wanted to install viper4android, the latest version, but unfortunately, it never installs correctly. It always says installed, please reboot your phone. Ive done that numerous times, but nothing ever happens. Somtimes, it says I need to install busybox, and ive done that through the app and by flashing. It still gives me the same two errors. Thanks for the help in advance!
Have you flashed a kernel that has write protection disabled?
Teet1 said:
Have you flashed a kernel that has write protection disabled?
Click to expand...
Click to collapse
I dont think so, the only thing i installed is twrp recovery, busybox and the super user
You must have a kernel with write protection disabled or S-OFF in order to write something into /system/ or flash viper via recovery. What is your carrier?
I too have viper.
Ok so i did just now flash a custom kernel and got the drivers to work. Sorry, i didnt know the kernel was write protected. This is my first htc phone so I just got confused, but thanks for your help!
Sent from my 0PCV1 using XDA Free mobile app
No problem, glad I can help! HTC devices have write protection enabled even when unlocking the bootloader and being rooted. The 510 has S-OFF in development but the kernel disables that write protection that being S-ON has.
Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
xda123455 said:
Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
Click to expand...
Click to collapse
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
kal250 said:
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
Click to expand...
Click to collapse
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
xda123455 said:
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
Click to expand...
Click to collapse
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
kal250 said:
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
Click to expand...
Click to collapse
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
devanttrio said:
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
Click to expand...
Click to collapse
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Autolounge said:
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Click to expand...
Click to collapse
I did.
I also tried the apps, of the ones that have apps.
devanttrio said:
I did.
I also tried the apps, of the ones that have apps.
Click to expand...
Click to collapse
You're going to have to do it manually.
no go on kingo
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
consider yourself blessed my friend, i'd like to root mine just to get marshmallow.... i have lollipop and checked for updates and says i'm up to date, i can only install 1 app at a time because there is no room on the internal storage, i have to move every app to sd card and then clean cache for each and every app i want.. never recommending blu to anyone
trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
ray2jerry said:
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
Click to expand...
Click to collapse
I found a option in developer settings that is "Enable OEM unlocking" and it makes it so you can unlock the bootloader from fastboot, if you do adb reboot-bootloader and then fastboot unlock it should undo the bootloader for you
zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
CreativiTimothy said:
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
Click to expand...
Click to collapse
I too am trying to root this device, and am unclear on a few of the steps here. I actually found your site with the recovery and boot images independently, really appreciated! I am at the point where I just need to patch the boot image, though I am not sure how to do this. If you could help me out with this step I might be able to put together some sort of list of steps to get through the whole process if you don't have the time.
Any help would be appreciated, thanks!
I have tried unsuccessfully to root the phone with SuperSU following the instructions provided in forum and on other websites. Rooting with Magisk works but I prefer SuperSU. Has anyone got this to work? Help appreciated. Thank you.
I could not...I tried, it never actually rooted, although it seemed to go through the process..Had to re-flash the stock boot.img and flash Magisk.
smokinjoe2122 said:
I could not...I tried, it never actually rooted, although it seemed to go through the process..Had to re-flash the stock boot.img and flash Magisk.
Click to expand...
Click to collapse
Thanks for the reply. There are a number of negative reports in the twrp/root threats, but I do not recall any reports of success. I wonder if folks just write the guides without actually testing them.
Hello, I'm wondering if they've made any advancement on the Samfail root method for the Note 8 AT&T version. I'm finding that I'm running into circumstances where I need to be able to flash a zip. This is still not possible, correct?
2Tone23 said:
Hello, I'm wondering if they've made any advancement on the Samfail root method for the Note 8 AT&T version. I'm finding that I'm running into circumstances where I need to be able to flash a zip. This is still not possible, correct?
Click to expand...
Click to collapse
Just check the Samfail thread. It's up to v3 for the latest 7.1.1 software we have. It does not root Oreo, but it will downgrade you from it back to 7.1.1 to be able to root.
Jammol said:
Just check the Samfail thread. It's up to v3 for the latest 7.1.1 software we have. It does not root Oreo, but it will downgrade you from it back to 7.1.1 to be able to root.
Click to expand...
Click to collapse
Thank you, Jammol. I'm actually rooted, but I was out of the loop due awhile and I was wondering if full root had been managed. They finally achieved it on the Note 5 AT&T version, only after I got rid of it. Hoping lightning will strike twice, you know?
2Tone23 said:
Thank you, Jammol. I'm actually rooted, but I was out of the loop due awhile and I was wondering if full root had been managed. They finally achieved it on the Note 5 AT&T version, only after I got rid of it. Hoping lightning will strike twice, you know?
Click to expand...
Click to collapse
Full root as in TWRP and such? We have full root but with a locked bootloader. Flashfire can be used to flash stock roms for the Snapdragon variant. Safestrap was just released for it as well but currently only the "Stock" slot can be used. And yes the 80% battery limit is very much still there.
So I can actually flash custom roms with this lock bootloader on this variant? Also, safestrap will allow me to flash custom roms as well?
Jammol said:
Full root as in TWRP and such? We have full root but with a locked bootloader. Flashfire can be used to flash stock roms for the Snapdragon variant. Safestrap was just released for it as well but currently only the "Stock" slot can be used. And yes the 80% battery limit is very much still there.
Click to expand...
Click to collapse
So I can actually flash custom roms with this locked bootloader on this variant?. Also, safestrap will allow me to flash custom roms as well? I hope I understand you right, Jammol. To be able to finally do that would make me a happy man. Also, is there any advantage to using Safestrap over Samfail? I used Safestrap with my S5.
2Tone23 said:
So I can actually flash custom roms with this locked bootloader on this variant?. Also, safestrap will allow me to flash custom roms as well? I hope I understand you right, Jammol. To be able to finally do that would make me a happy man. Also, is there any advantage to using Safestrap over Samfail? I used Safestrap with my S5.
Click to expand...
Click to collapse
Correct, but you can't get to Safestrap without being rooted first, which requires Samfail.
Jammol said:
Correct, but you can't get to Safestrap without being rooted first, which requires Samfail.
Click to expand...
Click to collapse
Thanx. I'm Samfail rooted already. Going to install safestrap. Can you direct toward some custom stock roms that might flash? I've had no luck thus far.... And thank you for all the info. If not for you I wouldn't even know Safestrap and flashing was even available.
2Tone23 said:
Thanx. I'm Samfail rooted already. Going to install safestrap. Can you direct toward some custom stock roms that might flash? I've had no luck thus far.... And thank you for all the info. If not for you I wouldn't even know Safestrap and flashing was even available.
Click to expand...
Click to collapse
Currently there are only 2 roms we can flash. FENNEC and Culpeo.
FENNEC is based on the U1 (unlocked firmware), so there's no carrier bloatware.
Culpeo is based on U or carrier firmware. The bloat will come with the CSC you flash for your particular firmware. There are CSC edits in there for things such as VoLTE, Wi-Fi Calling, etc.
These are both based on the latest 7.1.1 version respectively. I have personally ran both but I was partial to FENNEC because I hate carrier bloat.
Both are located on the Development section. There are more roms coming so don't be deterred.
Jammol said:
Currently there are only 2 roms we can flash. FENNEC and Culpeo.
FENNEC is based on the U1 (unlocked firmware), so there's no carrier bloatware.
Culpeo is based on U or carrier firmware. The bloat will come with the CSC you flash for your particular firmware. There are CSC edits in there for things such as VoLTE, Wi-Fi Calling, etc.
These are both based on the latest 7.1.1 version respectively. I have personally ran both but I was partial to FENNEC because I hate carrier bloat.
Both are located on the Development section. There are more roms coming so don't be deterred.
Click to expand...
Click to collapse
Jammol, I really appreciate your responsiveness and all of the knowledge you've provided. Thanks you!
Jammol, trying to figure out why Safestrap won't take. Busybox up and running. After hitting install it goes thru its paces and says I install successfully, or something similar, but above that where it says State it still reads not installed. I see it with granted access in Su. But when rebooting I do not get the splash screen. Any ideas?
2Tone23 said:
Jammol, trying to figure out why Safestrap won't take. Busybox up and running. After hitting install it goes thru its paces and says I install successfully, or something similar, but above that where it says State it still reads not installed. I see it with granted access in Su. But when rebooting I do not get the splash screen. Any ideas?
Click to expand...
Click to collapse
I have the free version of Busy Box installed. Tried installing the pro version in case that would somehow facilitate the installation of Safestrap and the pro version won't install either. The notice suggests I try installing in another location. Not sure how to do that. Can anyone advise me on this and /or how I can get Safestrap to install?
2Tone23 said:
Jammol, trying to figure out why Safestrap won't take. Busybox up and running. After hitting install it goes thru its paces and says I install successfully, or something similar, but above that where it says State it still reads not installed. I see it with granted access in Su. But when rebooting I do not get the splash screen. Any ideas?
Click to expand...
Click to collapse
In the Safestrap thread there were a few users that had that issue occur. I don't know what the Fix was for them, if it was fixed, as I haven't followed that development for a few days now. I suggest giving the OP of that thread a full read through again and read through the comments/replies of what others have done so far to solve their issues.
Thanx Jammol. Actually perused that before my last post. Will look again. Hope I missed something, but I dont think so.
Jammol said:
In the Safestrap thread there were a few users that had that issue occur. I don't know what the Fix was for them, if it was fixed, as I haven't followed that development for a few days now. I suggest giving the OP of that thread a full read through again and read through the comments/replies of what others have done so far to solve their issues.
Click to expand...
Click to collapse
Thanx Jammol. Actually perused that before my last post. Will look again. Hope I missed something, but I dont think so.
2Tone23 said:
Thanx Jammol. Actually perused that before my last post. Will look again. Hope I missed something, but I dont think so.
Click to expand...
Click to collapse
No problem. Let me know. There are some bugs with it though so posting Safestrap related questions there would be the best thing to do. I merely fiddled with it for about a day at most and had to return to stock(work reasons).
Thanks, J. Really appreciate your feedback. Will let you know if something gives.
Jammol said:
No problem. Let me know. There are some bugs with it though so posting Safestrap related questions there would be the best thing to do. I merely fiddled with it for about a day at most and had to return to stock(work reasons).
Click to expand...
Click to collapse
Thanks, J. Really appreciate your feedback. Will let you know if something gives.
(Eventually, I'm going to get this reply thing right. ?)
2Tone23 said:
Thanks, J. Really appreciate your feedback. Will let you know if something gives.
(Eventually, I'm going to get this reply thing right. ?)
Click to expand...
Click to collapse
Lol, no problem.