Related
Hello to you all people of XDA, firstly I must state that I've scoured the forums far and wide and have yet to find some valuable info regarding my problem.
So what we're doing is developing (or trying to, as is obvious from this post) a custom rom for the Galaxy S2 which would be used for a single medical application for sensor tracking and the processing and displaying of said data on the SGS2, while at the same time sending it to his/her doctor.
What we need to be able to achieve with this rom is to put it into the hands of the end-user (a chronical patient which will in turn be able to stay at home instead of being hospitalized) and be able to completely lock down the phone for his use (I know, it sounds terrible) so that he loses the phone/sms/games/youtube/internet functionality as we need the phone to run as stable and for as long as possible without any additional battery stress (the constant sending, processing and processing of data seems enough of a problem for now).
I've searched into some custom roms but we eventually came up with the need for a stock Samsung rom which could be modified as we want to.
See this is where the problem begins, we can't seem to get the phone rooted, the ROM customized and then unrooted again so that the phone can't be fiddled with anymore, except when it's completely dead and we need to fix it.
So to cap it all up:
It needs to allow for a custom load and bootscreen (I almost got this to work)
It needs to be completely locked down for the end user.
It has to have full BT, NFC and WiFi functionality
It has to be able to call out and reciev calls, but only to/from specific numbers (911, doctor, etc..)
It has to basically allow for 2-3 programs to be running, while the others simply don't exist on the phone.
I am terribly sorry if anything like this has been asked about before, I swear I put 2 days of me life into researching already.
Any help, any help at all, ideas and solutions, but mostly links are welcome.
Thank you and good day to all.
Just a detail, but the SGS2 doesn't have the NFC functionality. Project seems to be possible, I would look into CyanogenMod sources if I was you.
Sent from my GT-I9100 using XDA App
Why are you afraid of leaving the phone rooted and in hands of the patient?
Is he so uncritical that he can search the web and find means of unrooting a mobile phone and then get around to actually doing it?
LucLucLuc said:
Hello to you all people of XDA, firstly I must state that I've scoured the forums far and wide and have yet to find some valuable info regarding my problem.
So what we're doing is developing (or trying to, as is obvious from this post) a custom rom for the Galaxy S2 which would be used for a single medical application for sensor tracking and the processing and displaying of said data on the SGS2, while at the same time sending it to his/her doctor.
What we need to be able to achieve with this rom is to put it into the hands of the end-user (a chronical patient which will in turn be able to stay at home instead of being hospitalized) and be able to completely lock down the phone for his use (I know, it sounds terrible) so that he loses the phone/sms/games/youtube/internet functionality as we need the phone to run as stable and for as long as possible without any additional battery stress (the constant sending, processing and processing of data seems enough of a problem for now).
I've searched into some custom roms but we eventually came up with the need for a stock Samsung rom which could be modified as we want to.
See this is where the problem begins, we can't seem to get the phone rooted, the ROM customized and then unrooted again so that the phone can't be fiddled with anymore, except when it's completely dead and we need to fix it.
So to cap it all up:
It needs to allow for a custom load and bootscreen (I almost got this to work)
It needs to be completely locked down for the end user.
It has to have full BT, NFC and WiFi functionality
It has to be able to call out and reciev calls, but only to/from specific numbers (911, doctor, etc..)
It has to basically allow for 2-3 programs to be running, while the others simply don't exist on the phone.
I am terribly sorry if anything like this has been asked about before, I swear I put 2 days of me life into researching already.
Any help, any help at all, ideas and solutions, but mostly links are welcome.
Thank you and good day to all.
Click to expand...
Click to collapse
Block all internet access apart from ones you want or you can just setup iptables rules, shouldnt need root apart from when setting it up
As far as removing programs, just delete the apks from the zip, or before you remove root. My sig has a list of all apks in a upto date rom and what they do.
You can use gemini app manager to control autoruns (stop them etc) also to block (hide and disable apps)
As far removing root, your best bet is to once you are done, use adb (from the android sdk) to remove the superuser.apk then flash the stock kernel back, as far as I know without superuser apps cant grain root permisions.
OR
This app will allow you to block any app behind a password
This app will block incoming and outgoing sms and calls on white and blacklists
Custom boot logo (the first screen before the animation)
Custom boot animation need to go into system/media, I am not sure about the format but there are loads around, like this thread has loads, stock kernel should support them.
I hope that helps
Most of that is easily possible.
If you listed the apps needing removed, the apk files just need deleted.
To control calls, you can use a third party app from market for that.
It's possible to have the custom rom unrooted, and easily flashed, regardless of how badly the phone gets rooted
Boot animation is easy anyway... If you can provide it in a zip like other ones (zip containing numbered png's) then it's a piece of cake.
A little bit of clever firewall stuff would prevent any web traffic, in or out, except to your defined server, which is obviously a concern when a phone is handling sensitive medical info.
genieass said:
Why are you afraid of leaving the phone rooted and in hands of the patient?
The phones are going to be used by around 500.000 people in a year, it's not that we want to take anything away from the user, it's more about not having any problems with the firmware - like ever.
Thanks for all the help!
Click to expand...
Click to collapse
genieass said:
Why are you afraid of leaving the phone rooted and in hands of the patient?
The phones are going to be used by around 500.000 people in a year, it's not that we want to take anything away from the user, it's more about not having any problems with the firmware - like ever.
Thanks for all the help!
Click to expand...
Click to collapse
LucLucLuc, not sure where you live, but you're entering the patient confidentiality minefield with big, big boots.
Apart from the legal considerations, your question is definitely OS related and not device related.
I see what you want, but legally - where I live anyway - it's too much of a grey area to get involved with.
I use call recording a lot for referrals and info from other doctors, but I've always asked the other party if they're OK with it. I won't record patient conversations, and I won't accept any files whatsoever that have seen RIS or PACS first - not worth it.
Can't see it's worth your while, but I'd appreciate it if you keep me informed should you decide to work on it.
Big boots indeed
We are from Slovenia, Europe.
I'm actually just a student doing the research and some basic Android programming, thank god I wasn't let into the bigger of the projects
But yes, this project is a colaboration of several european firms and you can read more about it at chiron-project.eu - it's a very very interesting project afaic.
I don't think we'll be swimming with lawyer piranhas soon though, the project uses sensor data (which sorta is a privacy issue) which will be monitored on a tablet running Android (currently testing the Galaxy tab 10.1 - we were lucky to order one before Steve had another one of his fits), proccessed in real time and then stored on the central server, from where it will only be accessible by the patients doctor.
Patient consents are dealt with before we even start talking about mobile hospitalizations.
It's very encouraging to see some actual interest, if anyone wants to know more about anything related to this project contact me at [email protected]
Thanks again for all the help.
Hi all,
I recently acquired a Jetstream in the US (AT&T) to bring back to France.
I'm pretty new to Android but I got the bootloader unlocked through htcdev.com, then managed to apply DoomLoRD's root and CWM recovery succesfully (excellent tutorial, BTW).
I now want to unlock the phone and reconfigure BT so I can use my regular BT headset (Nokia BH-109, supports HFP & HSP but no A2DP) following the instructions on http://forum.xda-developers.com/showthread.php?t=1418235, but that fails to work as the /system/build.prop file remains read-only.
Is there anything I've missed? Would that be because my Jetstream is still S-ON?
thanks in advance for any hint that gets me going!
François
Hi,
Welcome to the Jetstream community.
1st off, for you to be able to edit the /system/build.prop file, you need Root Explorer, navigate to the file, before opening it with the text editor, make sure to click on the R-W/R-R which you can find around the top left side of screen- it will basically change from read to write functionality in the system files. You will then be able to enable the options.
2nd, after following the steps, you will be able to get the phone app to show and you will be able to use MMI codes of the *123# sort perfectly. Coming to the call however, you will be able to make calls but no sound on either side of the calls. Still some bugs to be figured out and fixed. Some have got some clue about how to solve it - mentioned in the post with the instructions.
3rd, after following those instructions, you will be able to send and receive messages using a 3rd part app like GO SMS. Works perfectly well.
4th, the S-ON to S-OFF transition needs a lot of help from developers which is not happening as of yet. Hoping that someone will be able to really achieve this for us. It has been done for many other devices as well and we all here hope it will happen for the Jetstream too.
Hope it helps you and hope to have more people join the community of this wonderful device like you have just joined us and get this device moving soon.
-Kaialsh.
Hi Kaialsh,
thanks for taking the time to share your experience. I will look into Root Explorer for sure, even though I actually managed to answer my question when writing my original post got me thinking.
I'll write down what I found as it may be of help to others.
As I understood the problem was with the /system partition being mounted R/O I looked on the Market and found mount /system (rw/ro) and it seemed to work giving me a successful status, but the build.prop file remained R/O in vi, and Astro would not save it properly.
I then saw that DoomLoRD's custom kernel included R/W system partition and looking into that I found the adb remount command which did what I wanted, except it failed on my system.
Last bit was to boot the tablet into DoomLoRD's insecure kernel image (as I did before to root the Jetstream), then issue "adb remount", then edit build.prop and reboot again.
As you can see, it's not really straightforward and I wish I saw your post before all of this!
I did see the Audio problems with making calls and will be following the forum for a potential fix to this problem, but I have another issue right now...
Noise cancellation does not work at all and any attempt to make a VoIP call (SIP or Google Talk for instance) results in terrible echo at the other end of the line. The only way out is to use a headset and Bluetooth seems a reasonable choice.
Before the build.prop change, my Nokia headset (with HFP and HSP) would be detected and paired but would remain disconnected and no profile was listed (only options are to delete pairing or rename device). A set of Bluetooth headphones with A2DP support worked fine.
After the change, the device is paired and the headset profile listed as expected, but it still remains disconnected even though when I select it I get a "connected" popup. Of course, the headset will not give audio in any application, and the speaker works normally.
I'd be interested if someone around here has any hints into getting a regular cell phone Bluetooth headset to work with the Jetstream, as well as maybe a fix on the echo cancellation problem.
In any case, this forum is a goldmine
I too face the problem with google talk and sort-noise cancellation is bad. I however circumvented the problem by using a wired headset-no echo with that but the gain on audio was a bit low. I don't own a Bluetooth device myself to check and am kind of busy studying for exams go out and get myself one.
However, the basic problem seems to lie in the Mic settings and as mentioned in the section on enabling gsm calls, we need to check the codec files and anything related to Mic and htc audio libs. I did sit once checking for any potential files that contain details regarding this, but I was dumb enough not to note things down then and there so don't remember very well and haven't found the time to check it again. Will do so the earliest possible and share my findings. There was something about a particular file missing in the devices lost which seemed to be necessary for phone functionality.
Also, just out of curiosity, what is your main application with the Jetstream?
Sent from my HTC PG09410 using XDA
It's a shame I don't know enough about the platform to look into it myself, but I'm ready to try out any suggestion that comes forward!
What I intend to use the tablet for is remote desktop/VNC access to remote systems through ssh tunnels and voice/video conferencing, but at the moment I'm still in the discovery stages.
François
Cool. Welcome aboard once again.
Sent from my HTC PG09410 using XDA
I just tested this with a harmless test page with my GSM 3D EVO, and, using the stock browser, the USSD code was executed immediately without asking for confirmation (in this case the test page only used the USSD code for IMEI number, so no big deal). I am using one of the popular ICS+Sense based ROMS from the GSM section, but this will probably affect all the ROMs derived from the official HTC ICS update.
Not too concerned because I use Chrome (which is not affected by the exploit), but this is one more reason to wait anxiously for CM10 to be ready.:laugh:
I ran the test link on this page on my CDMA Evo 3D and it doesn't seem to be affected, but I'm using the default browser from MeanROM ICS 2.6 which is different from the stock ICS browser. My impression from reading a couple articles on this exploit is that it only affects GSM phones.
ramjet73
Just ran the exploit with the default browser in SOS 2.6.1 and it works. Strange since it's based on Mean.
... with Tapatalk 2
Ok so my phone can automatically do a factory reset, bigger deal if you are stock with no backup, that's why nandroids are so important
Signature (Don't ask me for help, couldn't careless if your phone explodes)
On SOS 2.6.1, stock browser and my phone does not seem to be affected.
Checked it through this website http://dylanreeve.com/phone.php
If your phone is vulnerable to the recently disclosed tel: URL attack then this website will cause your phone to open the dialler and display the IMEI code. With other USSD codes it could do any number of other things, including wipe all phone data.
You can find some more information and a simple workaround here: http://dylanreeve.posterous.com/remote-ussd-attack
What does it all mean?!
If visiting this page automatically causes your phone's dialler application to pop up with *#06# displayed then you are not vulnerable. If, however, the dialler pops up and then you immediately see your phone IMEI number (a 14- or 16-digit number) then you are potentially vulnerable to attack.
Click to expand...
Click to collapse
It seems only gsm phones are effected, unfortunately I am in that category, I believe it would be more of an issue if you run a stock phone.
signature( don't ask me for help, as could care less if you phone explodes)
flashallthetime said:
It seems only gsm phones are effected, unfortunately I am in that category, I believe it would be more of an issue if you run a stock phone.
Click to expand...
Click to collapse
From the article linked in my post above:
In conclusion, what is the risk to my phone?
The risk is that, upon visiting a website, a USSD code could begin running in the background, which is undoubtedly a serious breach of security. However, you shouldn't panic just yet: so far, no cases in the wild are known where this security breach has been exploited.
Click to expand...
Click to collapse
ramjet73
We all knew things like this would come to our phones. Members of XDA used to push better security programs for our phones back in the day. I'm tellin ya. Firewalls are going to be a real thing on our phones soon.
Yes I love the fact that miui has a built in firewall app. Always better safe than sorry.
Sent from my PC36100 using xda app-developers app
It seems that even if our Evo 3d shows up the IMEI code when visiting one of the many test pages, we are quite safe from the really harmful codes.
See here for a more detailed explanation.
I tested the factory reset code from the dialer (after a Nandroid backup, of course!!!) and it does not execute on my phone. :good:
I found this article talking about the samsung gallaxy s3 problem. There is also a link in the article to an app in the play store block the USSD codes from executing at all. I tested the app on my phone and it did stop the USSD codes I tested.
Article:
http://www.pcworld.com/article/2010867/samsung-android-hole-also-leaves-sim-cards-vulnerable.html
App:
https://play.google.com/store/apps/details?id=org.mulliner.telstop
Is there a good fire wall app for evo 3d until such a firewall can be integrated with our phones?
I got an update for avast antivirus and apparently the USSD exploit is patched in the update
First thanks to all the great info and efforts here -- lots to read and learn from.
I am looking for a concise way to accomplish the following:
Record both sides of a phone conversation not using speaker phone or "announcing" the call is being recorded.
I have found an app called "Call Recorder" by skvalex. This app uses the " 2-way call recording" available on my phone which is a Verizon HTC Incredible 4G LTE.
Originally I was able to record both sides with a different app, however after a time -- likely when I did the Verizon software update -- that application was unable to record the other side of the conversation. So I sought a different app, tried several, and reached the following conclusion after much digging (googling, reading forums) -- that I needed to use the " 2-way call recording" functionality of the phone's kernel.
According to the developer skvalex, I need to root the phone to allow his application to utilize this 2-way call recording (2wcr) functionality.
I have found the following regarding the device:
http://www.xda-developers.com/andro...te-finally-gets-non-htcdev-bootloader-unlock/
and the companion thread
http://forum.xda-developers.com/showthread.php?t=1986346
However, I'm not clear on the exact steps I need to take -- and want to be "uber" cautious giving I am not traditionally an android developer and have never rooted a phone before. Nor is it clear that the "boot unlock" is necessarily the full picture. My impression is that I need to do these things before the Call Recorder app can access the 2wcr functionality of the kernel.
Run the unlock process from "Team fireballas FakeCid AUTOMATIC bootloader unlock" stepping carefully through the process
Follow Captain Rewind's instructions and add the TWRP recovery software to enable full phone backups (seems this is actually part of root process?) and the Super user
http://teamw.in/project/twrp2/139
From these as I'm understanding it the CWM noted in Captain Rewind' instructions are not applicable (and obsolete based on that link) if you're using TWRP. Is that correct??
If I'm reading this process correctly it's basically these steps:
Fool the CID to be the nonstandard 11111111 and use 'other supported devices' to download from HTC's unlock boot loader listing to unlock the phone's bootloader
Install TWRP
Install Superuser
After this, the phone's apps can access the kernel and the Call Recorder app should be able to record *both* sides of the conversation. In this scenario is there a way to keep those apps from accessing other things? Or is that in the permissions of the apps themselves (i.e. don't allow them to do X)?
I recognize this will need to be a clear-headed, step-by-careful-step walkthru to do it. So I want to make sure its truly necessary and that I am not missing something important -- like how do I ensure that someone doesn't call or text or email isn't picked up during the process? Or is that handled by USB debugging mode being on and the phone being connected to the computer?
What am I missing?
Thanks in advance for any assistance!!
-B.
(typically a PHP, MySQL deveioper)
BTW, I really do like my phone aside from this aspect -- and the earlier app I'd tried did a wonderful job until it appears that the software update closed the hole it might have used to access the other side of the conversation without doing speakerphone which doesn't work well for my purpose.
For those who might comment/wonder about the legality of the 2-sided recording, I have the legal approvals (signed legal documents) in place for doing it. It needs to be without interruption of the announcement to avoid impacting the information, so a call service isn't an option.
My phone software info:
Android 4.0.4
HTC Sense version 4.1
Software number 2.17.605.2 710RD
Model number ADR6410VW
Dual core processor, 1GB memory
Last software update ADR6410LVW_2.17.605.2-1.43.605.3
Kernel version 3.0.8-01620-gabf7709
Kernel feature
Sent from my Incredible 4G LTE using xda app-developers app
jose51197 said:
Kernel feature
Sent from my Incredible 4G LTE using xda app-developers app
Click to expand...
Click to collapse
Perhaps you could amplify on your comment.
I realize that 2wcr is a feature on the kernel.
My understanding is this feature must be turned ON in a setting somewhere that accesses the kernel to allow the Call Recording application to work and record both sides of the call from the application and that you need to root the phone to access that feature.
But I am unclear exactly what you are saying in your brief comment.
Perhaps I wasn't clear in my question -- I'm looking for how to enable that feature so the app works.
Thanks!
so you want root to get your app to work?
here's what i did...
http://forum.xda-developers.com/showthread.php?t=2039601
I too am interested in getting callrecorder to work. I just installed the latest viper rom, and callrecorder doesn't seem to work. Is there a specific rom or kernel that one can install which supports call recording? I had it working just fine on my old rezound with pretty much any rom.
I recently upgraded to the S23 Ultra and discovered that there's no option to unlock the bootloader. The root functions I value most are:
A firewall that will block apps from phoning home and/or accessing the internet without using the Android vpn (not sure if I could do that even if rooted...I just want to block apps from phoning home and use a vpn at the same time))
A call recorder (currently using Cube ACR, which actually works pretty good)
A way to 'image' the entire phone (i.e., like TWRP back up/restore)
A way to uninstall the bloatware that doesn't have an uninstall function.
Barring some method that will unlock the bootloader on this phone, what are methods/apps that will help me get as close to a rooted state as possible?
Well your first point is solved with what I use for privacy and adblocking. NextDNS (free option or $12/yr) you get a private DNS server and you control what is blocked and what isn't with all the customization you want. As for call recording, I've used skvalex (free with paid pro option but pro only adds automatic backup) for years whether rooted or not and it always works just fine. Though I will admit when it's connected to my car with Bluetooth it only records my side but I rarely talk while in the car so not a deal breaker for me. Thirdly, you could use adb to make a backup (from what I've read) but I use shizuku to give swift backup more permissions and it backups everything for me.
Thanks for your comments, spart0n.
I looked over NextDNS. It seems to have a lot of features. I do use my vpn's DNS, but they're various US servers are slow, plus NextDNS seems to have more features.
One thing I'm not clear on is can it slectively block apps from connecting to the internet, both on mobile /and/or wifi connection, much like a firewall?
I also did a quick perusal of skvalex, but I'm not sure how it's different from Cube ACR? One concern with cube is security...are they doing nefarious things with my data.
Cube also won't record the other side of a conversation when I'm using a bluetooth device (earbuds, car).
Is skvalex ' more respecting of privcy? In what ways do you deem it superior to other options such as Cube?
I'll be looking into Shizku and Swift backup, but am I correct in that it seems to be more of a 'Titanium' type app than a complete phone backup?
I really appreciate the pointers.
Sam Sung said:
Thanks for your comments, spart0n.
I looked over NextDNS. It seems to have a lot of features. I do use my vpn's DNS, but they're various US servers are slow, plus NextDNS seems to have more features.
One thing I'm not clear on is can it slectively block apps from connecting to the internet, both on mobile /and/or wifi connection, much like a firewall?
I also did a quick perusal of skvalex, but I'm not sure how it's different from Cube ACR? One concern with cube is security...are they doing nefarious things with my data.
Cube also won't record the other side of a conversation when I'm using a bluetooth device (earbuds, car).
Is skvalex ' more respecting of privcy? In what ways do you deem it superior to other options such as Cube?
I'll be looking into Shizku and Swift backup. I really appreciate the pointers.
Click to expand...
Click to collapse
I've tried cube in the past and it had a lot of denied connections in the background but over the years skvalex has worked perfectly even if I completely block all internet connectivity even from the start of installation except for checking for pro version.
As for NextDNS it does work on wifi and cellular. Personally I pay for the pro and have it setup on my home router plus all my phones too
Try freezing the Apps you cannot uninstall - e.g. SuperFreezZ or SD Maid.
Have a look here for some other goodies that may be useful:
https://alternativeto.net/list/28655/the-ultimate-f-droid-setup/
elmor0 said:
Try freezing the Apps you cannot uninstall - e.g. SuperFreezZ or SD Maid.
Have a look here for some other goodies that may be useful:
https://alternativeto.net/list/28655/the-ultimate-f-droid-setup/
Click to expand...
Click to collapse
There's no such thing as not able to uninstall. With adb commands you can uninstall literally any app, even system apps.
spart0n said:
There's no such thing as not able to uninstall. With adb commands you can uninstall literally any app, even system apps.
Click to expand...
Click to collapse
My understanding is that the system apps don't get truly uninstalled but are effectively disabled (frozen)......?
spart0n said:
I've tried cube in the past and it had a lot of denied connections in the background but over the years skvalex has worked perfectly even if I completely block all internet connectivity even from the start of installation except for checking for pro version.
As for NextDNS it does work on wifi and cellular. Personally I pay for the pro and have it setup on my home router plus all my phones too
Click to expand...
Click to collapse
The problem I've seen with Cube is that it sometimes randomly ends a recording before the call is finished.
Your earlier comment about using ABD to backup the phone - I found this and several other similar articles/guides outlining the method I think you alluded to. Seems pretty straight-forward. I also turned up info on uninstalling. Thanks for that - ABD seems the way to go.
The link:
How To Create a Full Android Phone or Tablet Backup Without Rooting or Unlocking Your Device
Android includes a built-in way to back up and restore the contents of your phone or tablet. All you need is a computer and a device running Android 4.0 (Ice Cream Sandwich) or newer.
www.howtogeek.com
Adding this link:
How to uninstall carrier/OEM bloatware without root access
If you want to get rid of carrier/OEM apps from your phone, here's how you can uninstall bloatware from your device without root access!
www.xda-developers.com
elmor0 said:
My understanding is that the system apps don't get truly uninstalled but are effectively disabled (frozen)......?
Click to expand...
Click to collapse
They do get uninstalled, but they remain inside the recovery partition so that when you reset the device they get reinstalled. You can disable or uninstall from Android any system app, even breaking the system, but the app will not get deleted from recovery unless you flash twrp or another custom recovery which deletes the stock recovery
Sam Sung said:
The problem I've seen with Cube is that it sometimes randomly ends a recording before the call is finished.
Your earlier comment about using ABD to backup the phone - I found this and several other similar articles/guides outlining the method I think you alluded to. Seems pretty straight-forward. I also turned up info on uninstalling. Thanks for that - ABD seems the way to go.
The link:
How To Create a Full Android Phone or Tablet Backup Without Rooting or Unlocking Your Device
Android includes a built-in way to back up and restore the contents of your phone or tablet. All you need is a computer and a device running Android 4.0 (Ice Cream Sandwich) or newer.
www.howtogeek.com
Adding this link:
How to uninstall carrier/OEM bloatware without root access
If you want to get rid of carrier/OEM apps from your phone, here's how you can uninstall bloatware from your device without root access!
www.xda-developers.com
Click to expand...
Click to collapse
Those are okay but dated guides for bloatware removal. There's 2 easy ways right now. One open source and not as feature rich and then there's a free/pro app that has more features.
Open source is universal android debloater gui (unless you want command line) from GitHub really easy to find with Google.
Or adb app control from cybercat. He's very active in his telegram support group and helpful
spart0n said:
Those are okay but dated guides for bloatware removal. There's 2 easy ways right now. One open source and not as feature rich and then there's a free/pro app that has more features.
Open source is universal android debloater gui (unless you want command line) from GitHub really easy to find with Google.
Or adb app control from cybercat. He's very active in his telegram support group and helpful
Click to expand...
Click to collapse
So they are. Not stuck on terminal. I've found and bookmarked AppControl download page.
Looking again, the ADB guide I linked to is aged too...is that still the best method? A Windows GUI would be nice for that too. Is there a reliable app or is ADB still my best bet?
Sam Sung said:
So they are. Not stuck on terminal. I've found and bookmarked AppControl download page.
Looking again, the ADB guide I linked to is aged too...is that still the best method? A Windows GUI would be nice for that too. Is there a reliable app or is ADB still my best bet?
Click to expand...
Click to collapse
Yeah there's a gui for adb, it's called universal android debloater from GitHub and in the release section they have a gui version
GitHub - 0x192/universal-android-debloater: Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device.
Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device. - GitHub - 0x192/universal-android-debloater:...
github.com
spart0n said:
Yeah there's a gui for adb, it's called universal android debloater from GitHub and in the release section they have a gui version
GitHub - 0x192/universal-android-debloater: Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device.
Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device. - GitHub - 0x192/universal-android-debloater:...
github.com
Click to expand...
Click to collapse
Rereading, I can see I wasn't clear at all. I should have specified 'for backup'. I'm doing a bit of searching for something now and this week. I doubt I can image the entire phone, but I'm hoping to find as complete and 'nandroid-like' backup solution as I can. If you know of anything, I'd appreciate it. Or maybe my best bet actually is ABD and commandline.
Sam Sung said:
Rereading, I can see I wasn't clear at all. I should have specified 'for backup'. I'm doing a bit of searching for something now and this week. I doubt I can image the entire phone, but I'm hoping to find as complete and 'nandroid-like' backup solution as I can. If you know of anything, I'd appreciate it. Or maybe my best bet actually is ABD and commandline.
Click to expand...
Click to collapse
Honestly I don't know any good ones, I use swift backup with shizuku. That's all I really know of. It works like titanium backup did but without root, even with shizuku, is somewhat limited.
adb pull /sdcard will get your files
Sometimes adb pull will fail on a specific file or folder and just puke on itself and refuse to continue. If that happens, you just have to delete the file/folder and try again. I've only had this happen once though.
Swift Backup with shizuku will back up apps and their downloaded data but not user data. Pair it with Google Backup and Google will restore *some* app data... Realistically though, you'll be losing some or a lot of app data, depending on app policies.
Thanks for your responses. Regrettably, there's no option in Dev options to unlock the boot-loader., so I'm stuck with whatever is available. Now I know. I should have either switched carriers or bought an unlocked phone, which I think comes with its own caveats.
User data, photos and such isn't too much of an issue here. My client data from apps is backed up to PC regularly, as are any photos I want to keep etc.
I like Nandroid backups because they backup everything including texts, call logs and OS (nice in case something happens and the OS bites the dust or gets crippled).
The real issue is my texts and call logs, moreso the texts..
How reliable is Swift (which is looking more and more attractive) compared to ABD, and can ABD back up more?
Also, side note, but my late wife's phone is an S7. I lost a previous phone and ergo my texts, so the texts on her phone are all I have of our texts over the years.
I was thinking I'd use Smart Switch or something to transfer the texts from her phone over to the S10 I just upgraded from. Is that practical?
I appreciate your remarks. Thanks!
Sam Sung said:
Thanks for your responses. Regrettably, there's no option in Dev options to unlock the boot-loader., so I'm stuck with whatever is available. Now I know. I should have either switched carriers or bought an unlocked phone, which I think comes with its own caveats.
User data, photos and such isn't too much of an issue here. My client data from apps is backed up to PC regularly, as are any photos I want to keep etc.
I like Nandroid backups because they backup everything including texts, call logs and OS (nice in case something happens and the OS bites the dust or gets crippled).
The real issue is my texts and call logs, moreso the texts..
How reliable is Swift (which is looking more and more attractive) compared to ABD, and can ABD back up more?
Also, side note, but my late wife's phone is an S7. I lost a previous phone and ergo my texts, so the texts on her phone are all I have of our texts over the years.
I was thinking I'd use Smart Switch or something to transfer the texts from her phone over to the S10 I just upgraded from. Is that practical?
I appreciate your remarks. Thanks!
Click to expand...
Click to collapse
As for bootloader unlocking anything Samsung, you can't buy the north America models, any other country model will have the option for unlocking. As for swift vs adb without root? Swift does call logs and text backups locally on the device and on several cloud services of your choice if you wish.
spart0n said:
As for bootloader unlocking anything Samsung, you can't buy the north America models, any other country model will have the option for unlocking. As for swift vs adb without root? Swift does call logs and text backups locally on the device and on several cloud services of your choice if you wish.
Click to expand...
Click to collapse
Thanks, sprt0n. I'll give Swift a try, along with Shizuku. Regarding the old S7 texts...do you recommend Swift there as well? WIll there be an issue transfering texts between the s7 and s10 given their age? S10 is Android 12, S7 is Android 8.
Sam Sung said:
Thanks, sprt0n. I'll give Swift a try, along with Shizuku. Regarding the old S7 texts...do you recommend Swift there as well? WIll there be an issue transfering texts between the s7 and s10 given their age? S10 is Android 12, S7 is Android 8.
Click to expand...
Click to collapse
You can try it says on the Google Play store listing page that supports Android 6 and up so it should work
I'll do that, Thx.
Y'all have given me direction regarding uninstalling apps and back up, and even firewalling, if NextDNS allows.
I may be back for future questions after I research this stuff. I appreciate all your comments, particularly spart0n.