Related
Has anyone come up with an unroot method for the fascinate. I just got one and it really sucks out of the box. I was going to play around with rooting it and see if I can make it fully functional again but I might end up just returning it and getting an incredible. Before rooting it I want to make sure I can go back to stock so it can be returned.
trevoryour said:
Has anyone come up with an unroot method for the fascinate. I just got one and it really sucks out of the box. I was going to play around with rooting it and see if I can make it fully functional again but I might end up just returning it and getting an incredible. Before rooting it I want to make sure I can go back to stock so it can be returned.
Click to expand...
Click to collapse
I'm coming from an Incredible and it is true that there is not as much hacks on the Fascinate yet, but there is a lot of activity already:
We have a way to backup and restore:
h**p://forum.xda-developers.com/showthread.php?t=782204
The Fascinate has been rooted (the first day mind you):
h**p://forum.xda-developers.com/showthread.php?t=779238
There is the usual Galaxy S lag fix:
h**p://forum.xda-developers.com/showthread.php?t=779597
List of crap apps to remove safely:
h**p://forum.xda-developers.com/showthread.php?t=779948
And the very first custom-ish ROM:
h**p://forum.xda-developers.com/showthread.php?t=782250
So plenty of action for the first week, I'm sure by the end of the month we will be eating Vanilla Froyo, the best flavor !
Am I wrong for thinking that Unroot = undoing the lag fix, and then just doing a system wipe from the privacy settings?
When I have done this, I have had to re-root the phone each time. So I'm thinking yes.
Daswolven said:
Am I wrong for thinking that Unroot = undoing the lag fix, and then just doing a system wipe from the privacy settings?
When I have done this, I have had to re-root the phone each time. So I'm thinking yes.
Click to expand...
Click to collapse
You don't even need to do the system wipe, you can just remove the files you copied over initially. The root process is minimally invasive.
Always undo the lag-fix first.
If a system wipe is easier for you, then un-do the lag fix and wipe the system.
namebrandon said:
You don't even need to do the system wipe, you can just remove the files you copied over initially. The root process is minimally invasive.
Always undo the lag-fix first.
If a system wipe is easier for you, then un-do the lag fix and wipe the system.
Click to expand...
Click to collapse
Lol. easy.
Now for a custom recovery. I need nandroid damnit.
Would wiping the phone work if I deleted instead of renaming some of the files on the phone? I deleted a bunch of the bloatware, and hoping that wiping the phone would just undo the root. I didn't do the lag fix. Just the root process and removed applications.
trevoryour said:
Has anyone come up with an unroot method for the fascinate. I just got one and it really sucks out of the box. I was going to play around with rooting it and see if I can make it fully functional again but I might end up just returning it and getting an incredible. Before rooting it I want to make sure I can go back to stock so it can be returned.
Click to expand...
Click to collapse
Here's my rooting instructions: http://forum.xda-developers.com/showthread.php?t=798064
Yes, it can be unrooted. Do everything in the instructions and it is a much better phone.
EDIT: I also just added a guide to get back to stock.
I am hearing some people who removed bloatware got soft bricked and then some are saying they didn't. Is there an official word on this? I removed some of the Samsung bloat because I would never use it.
If there is anyone HERE (on a forum I actually trust) that has updated their Vibrant to J16 after removing bloatware and didn't get a softbrick- then I will update. If not, does anyone have the bloat apks? I'd rather just download and install them all again then have to ODIN.
Never mind
DreamcastDC said:
Never mind
Click to expand...
Click to collapse
Never mind what? Does this have anything to do with my question?
I did. I removed a bunch of the programs that came installed wroth the phone, such as mobitv, gogo, the gps program by using Titanium Backup.
I had to reflash mine due to this problem.
Sent from my SGH-T959 using XDA App
Mine soft bricked and didn't even have bloat removed... all I had was root... no lag fix, nothing...... bricked and recovered in less than ten minutes... you would spend more time downloading and installing the bloat back... and when your device bricks anyways your gonna need odin so just use it or leave your phone alone...
I'm hardware blocked from accessing Recovery and Download so I'm trying not to softbrick my phone at all. Not because I don't want to use ODIN but because I do not wanna risk my phone being inoperable.
I was rooted and removed ALL of the Samsung crapware, and yes my phone bricked as a result of the OTA. I was able to flash JI6 via ODIN and everything is working again.
After the OTA, my Vibrant was stuck at the Samsung Vibrant screen.
Would I be able to do all of that through ADB? I'm hardware locked. Not only that, ODIN won't recognize my device!
Yes I removed a lot of bloat and still updated fine through Odin.
Btw, there is now a fix for hardware locked phones. I tried it last night and now my phone can access download and recovery through the vol buttons. Go ahead and get adb set up though--you'll need it to remove the hardware lock.
If Odin isn't working for you, (1) do you have the Samsung phone drivers, and (2) what version of Odin are you using?
Sent from my SGH-T959 using XDA App
Yeah I removed a bunch of stuff that I didn't user using titanium and I was also using the one click roote and I updated fine using odin.
Just a question, why would people want to remove these applications? does it have something to do with the battery life? or to have more memory for more applications?
It was kind of superfluous in my case since I have more app space than I'll ever need.
Sent from my SGH-T959 using XDA App
iynfynity said:
Just a question, why would people want to remove these applications? does it have something to do with the battery life? or to have more memory for more applications?
Click to expand...
Click to collapse
Because I know I'll never use them and they take up space in the app menu as well as the memory, also a bunch of them start themselves and take up processing power, like the Tel-Nav GPS app.
I rooted then unrooted, can someone explain what exactly Odin is doing and why people's phones are getting bricked? I don't really want to flash a rom or something if that's what Odin is doing. My goal is to keep everything stock minus the bloatware apps.
richiehd said:
If there is anyone HERE (on a forum I actually trust) that has updated their Vibrant to J16 after removing bloatware and didn't get a softbrick- then I will update. If not, does anyone have the bloat apks? I'd rather just download and install them all again then have to ODIN.
Click to expand...
Click to collapse
I have updated my Vibrant successfully without any bricks having removed bloatware each time before each upgrade.
I was always stock since I got the phone on release date. Now until JI5 came out, I had never decided to update the phone. When I updated to JI5 on the same day that was leaked, I did so via ODIN and had all the bloatware apps removed (TeleNav, GoGo, Slacker, etc).
When JI6 was leaked, I had done the same process again as above. I already had the bloatware removed before and once again after updating when it all came back.
When the official OTA JI6 came out, I waited a few days but flashed that over the leaked JI6 update without any issues once again via ODIN. I did the same thing again, had removed bloatware prior and again after. I honestly did not believe there was any difference in either prior nor do I see so after. Especially by file size or any fixes that weren't already in the leaked one.
This was just my experience and having removed the bloatware apps and not getting bricked. I never once applied any other modifications either (such as the battery ones, etc).
I did have 2 lag fixes applied (not at the same time) when I was on stock. The first one with terminal commands from a post here on the forums which was removed when I decided to try out One Click Lag Fix which was then removed before I flashed JI5. I have yet to apply a lag fix again with JI5 or JI6, nor will I be anytime soon I think either.
When you say everything is working again, did your bloatware come back? ARe you able to remove it if it did? For some reason I cannot remove the bloatware when it came back.
EDIT:
Woops, I meant to ask J3ST3RM4A3 this.
but has anyone seen this problem? after going to JI6 the bloat comes back and is not removable?
and if you did remove bloat, with what? ADB? Root explorer? Astro? Titanium? None of these worked for me
i purchased root explorer after i updated to JI6, it seems like such an useful app.
that allowed me to remove all the bloatware after the update.
i updated via KIES mini not OTA (i heard too much **** happened to people who did it the OTA way)
so when you delete your bloatware, they would just pop back? Cause i had that issue prior to updating root explorer. After i updated root explorer (purchasing the latest) i was able to successfully remove the bloat
richiehd said:
I am hearing some people who removed bloatware got soft bricked and then some are saying they didn't. Is there an official word on this? I removed some of the Samsung bloat because I would never use it.
If there is anyone HERE (on a forum I actually trust) that has updated their Vibrant to J16 after removing bloatware and didn't get a softbrick- then I will update. If not, does anyone have the bloat apks? I'd rather just download and install them all again then have to ODIN.
Click to expand...
Click to collapse
I had bloat removed prior to JI6. I did step 2 of this and had no trouble whatsoever.
Same. I soft bricked with the OTA update but Odin worked fine. I've heard there may be an issue with leaving the update.zip on your phone while you try to update.
OK, congratulate me!! Thanks. I did it on the first try, no issue or hiccups what-so-ever.
Now for the info. I'm not sure that anyone will be interested, but I'm guessing other people in my position at least might be.
I'm very experienced with computers, but not working directly with rooting/unlocking devices. But I would say anyone who reads up a bit and can follow directions properly could pull it off pretty easily.
So I run 2.2.2, and I used superoneclick 1.6.3.
After opening superoneclick, I switched it from psneuter to rageagainsthecage. I had no idea if I was supposed to do this, but I read all about rageagainstthecage, and never heard of psneuter.
I had my phone connected to my PC, and I left my SD in the phone, but I unmounted it in settings. I have used ADB before, so I knew the drivers were installed and working, and I hit the button root.
After reading this site, http://forum.xda-developers.com/showthread.php?t=803682, I started with debugging off, and turned it on as it said. I then turned it off, but didn't get a chance to turn it back on and off and on, so I just turned it back on (debugging) when it got to "Waiting for device" for the second time.
That was it! It asked to test and see if root was in fact accomplished, and it was. I then installed setCPU (which is basically the only reason I wanted to do this) and as far as I can tell it seems to be working fine.
I have been reading a lot about this for the past few days, but the actual procedure only took a couple of minutes. Keeping in mind, of course, that I already had ADB and drivers working.
Nothing was wiped off my phone, which surprisingly was hard to confirm on the web. I did read somewhere that only unlocking wipes data, but still, you never know.
I hope this helps anyone else who is new and unsure of the process, and I'd be happy to answer any other specific questions based on what I have learned of the last week or so. I know that people hesitate to ask questions in case they have already been asked lots of times, but are buried and hard to find (because that's the position I was in ).
Thanks for posting your "rooting" experience. I'm sure there are people that will find it helpful.
I think when I did mine, it was something along the lines of:
fastboot-oem-unlock
fastboot flash recovery <whatever>
reboot into recovery and flash rom
Other than the ability to install custom ROM's I've yet to see a huge deal in rooting my phone. Anyone care to tell me what I can do with a rooted N1 that is a must have? So far I tried to change some fonts, which didn't work, and discovered that I have to install a custom ROM to change the color of the notification bar, and I can't make the default Google music and news widgets slightly transparent. So educate me, what's the huge deal with rooting, aside from a custom ROM?
Set cpu of course like being said. I remember the first time I rooted my phone was universal androot it was a breeze. Then I lost root and use super one click to gain out back. Root really easy as well
Sent from my Nexus One using XDA App
- Backup application, like MyBackup, can backup your app data(including game save...) if your device is rooted.
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7?
2/ Can I always restore backups, nomatter what rom I come from or to?
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away?
Sorry, if I ask silly questions ..
Built in trackball colors, call blocker, hide frequently called list in the favorites tab, remove unnecessary apps, tmobile wifi calling, notification bar power toggles, trackball wake and unlock, quiet hours, themes, etc., etc., etc. Just off the top of my head. Oh, and Gingerbread!!!
Sent from my Nexus One using Tapatalk
Some apps want to bypass the home screen "5 second rule" like widget locker, you need root. I setup a widget to reboot (nice!).
brettbellaire said:
...I did read somewhere that only unlocking wipes data, but still, you never know.
Click to expand...
Click to collapse
Unlocking the Bootloader wipes data, rooting does not. This is probably what you read.
offenberg said:
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7? Yes you can. Often if the ROM is the next version in a series, you can flash without wiping data or cache, but some ROMs require you to do this first.
2/ Can I always restore backups, nomatter what rom I come from or to? A Nandroid backup can be reinstalled from any ROM, or even just from Recovery if there is no ROM.
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away? Yes. Either restore your stock ROM Nandroid backup or a passimg.zip.
Sorry, if I ask silly questions ..
Click to expand...
Click to collapse
offenberg said:
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7?
2/ Can I always restore backups, nomatter what rom I come from or to?
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away?
Sorry, if I ask silly questions ..
Click to expand...
Click to collapse
1. As a rule, if you are going from 1 ROM to another totally different ROM, it's always a good idea to wipe. It only takes a few seconds to sign back in to everything. You can bypass immediate sign in and activate wifi if you need it.
2. Nandroids can be reinstalled anytime. However, a nandroid does not contain your HBOOT and Radio. So if you updated those to use a specific ROM, they would stay in place with the nandroid restore.
3. When GB does finally make it out to our specific device, there is no way you would get an OTA before the ROM devs here had you up and running.
***Also note, the 1-click root tools may or may not work right away with the OTA 2.3. So to anyone that rooted using those tools and unrooted to hurry up and get an OTA, you may be stuck on stock until it gets fixed.
Know-Fear said:
1. As a rule, if you are going from 1 ROM to another totally different ROM, it's always a good idea to wipe. It only takes a few seconds to sign back in to everything. You can bypass immediate sign in and activate wifi if you need it.
Click to expand...
Click to collapse
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
bigmout said:
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
Click to expand...
Click to collapse
So what do you lose (if anything) when flashing a new ROM if you backup and do things the right way?
Another question would be if you just flash a new kernal do you lose any/all data?
brettbellaire said:
So what do you lose (if anything) when flashing a new ROM if you backup and do things the right way?
The only thing you'd lose is the old rom
Another question would be if you just flash a new kernal do you lose any/all data?
Click to expand...
Click to collapse
Nope
Sent from my Nexus One using XDA App
kmiloco49 said:
Nope
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Interesting... Thanks!
@ brettbellaire
I've rooted before, and lost root when ota's came. I've rooted again using superoneclick, and am contemplating cm7. But I feel very cautious about flashing a different rom, I'd cry if I bricked my phone. However, I'm probably going to do it during the next week (unless gingerbread ota arrives).
Andy
Sent from my Nexus One using XDA App
Hmmm, I have been anxious for GB too.... but I'm not sure it's worth it. I don't think it's such a big update. I don't think there's too much of a danger of brinking these days.
I have been contemplating doing what I have to to overclock, see what kind of a difference that makes...
bigmout said:
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
Click to expand...
Click to collapse
I am a newbie to root. Can Titanium Backup restore the paid apps? because some apps require online verification with Google at the first time of use.
Also, Z4root does not work on my N1. I want to use superoneclick but where can I find the driver for my win7? thanks
unroot
is it possible to go back and unroot the phone? i.e. hide the padlock during phone startup ..I am using N1 ForYo 2.2.2..Thanks
zmalach said:
is it possible to go back and unroot the phone? i.e. hide the padlock during phone startup ..I am using N1 ForYo 2.2.2..Thanks
Click to expand...
Click to collapse
If you see the padlock, you've got an unlocked boot-loader. This can't be re-locked.
Sent from my Nexus One using XDA App
Hi, (this is my first post here)
well I have a really nasty problem. Since my kitkat update there have been apps facing a lot of issues, thanks to their bugs/wanted changes with the permission setup and so on... In an attempt to fix that I tried to flash the new A7 firmware yesterday. (was on the unbranded A6 from Poland)
The problem was that because I'm unbranded, it FAILED at the end of the flash. So the obvious solution would be to flash the FW with a PIT file. But I don't want to loose my data and restore everything. It will take me 8 hours at least. (and this with nandroid backups and what not)
Well after some trial and error it booted up. But the system was corrupted i.e FCs and and and... So I flashed A6 back. All worked/works well now but I have an enormous problem:
The Bluetooth is broken. It tries to turn itself on but doesn't get anywhere. And in the eventually it stops, after 30/40 seconds. And after that it starts again. Well the obvious solution would be to go and delete the bluetooth data/cache and also delete the /data/misc/bluedroid/ folder. But nope. No success. And the same goes for reflashing/dalvik cache+cache wiping and so on. I also tried to take the battery out for some time.
Well the catlog show a lot of problems. It seems to be permission problems in this case too. I know that you suggest that I should only wipe it. But if i restore this **** will get back too. And re-installing everything from scratch will take me 2.5 days. I have like 750 apps or something.
Please help me with this, I beg you!
This is the catlog(filtered):
ht tp://pastebin.com/Hy99A10y
And here is the complete log aswell (the one with the timestamp):
ht tps://drive.google.com/folderview?id=0B9fgteM7eke-MHFBOFpWcmZtVjg&usp=sharing
Anyone? ;(
kevin_1351 said:
Anyone? ;(
Click to expand...
Click to collapse
Visit service center and make a fresh update
Sent from my Nexus 5 using Tapatalk
Mr hOaX said:
Visit service center and make a fresh update
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm rooted so I tripped my knox. I have not warranty anymore...
But anyway I know that I can fix it if i restore fresh. But I want to repair the Bluetooth, without factory resets.
kevin_1351 said:
I'm rooted so I tripped my knox. I have not warranty anymore...
But anyway I know that I can fix it if i restore fresh. But I want to repair the Bluetooth, without factory resets.
Click to expand...
Click to collapse
This is why I use cwm to make a backup...
But seriously, it looks like you might need to do a complete wipe... It sounds like some fragment of the A7 rom has been left there to corrupt your bluetooth....
Pain I know but sometimes this is the only way....
ultramag69 said:
This is why I use cwm to make a backup...
But seriously, it looks like you might need to do a complete wipe... It sounds like some fragment of the A7 rom has been left there to corrupt your bluetooth....
Pain I know but sometimes this is the only way....
Click to expand...
Click to collapse
I love many things about android, but one thing that seems to completely miss is the ability to factory reset only certain things like your settings, radios and so on.
Is there really no way to extract everything there has to be, from A6? Like zeroing all bluetooth files but nothing else?
kevin_1351 said:
I love many things about android, but one thing that seems to completely miss is the ability to factory reset only certain things like your settings, radios and so on.
Is there really no way to extract everything there has to be, from A6? Like zeroing all bluetooth files but nothing else?
Click to expand...
Click to collapse
Nope, unfortunately not...
Did you edit or flash the platform.xml(extSD fix KK) by any chance??
If so, others have reported Bluetooth breaking (among other things) after editing/flashing the platform.xml. The only fix was to start from scratch (factory reset).
Sent from my SM-N9005 using Tapatalk
denski101 said:
Did you edit or flash the platform.xml(extSD fix KK) by any chance??
If so, others have reported Bluetooth breaking (among other things) after editing/flashing the platform.xml. The only fix was to start from scratch (factory reset).
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Yeah you're right. But I still can't wipe... Like that would mean hell for me.
I really DON'T UNDERSTAND why I can't reverse it. Why flashing that zip messed eveything up. Like why doesn't it work now that I've restored the platform.xml backup? Are you shure that there isn't any way? It really doesn't make any sense at all.
kevin_1351 said:
Yeah you're right. But I still can't wipe... Like that would mean hell for me.
I really DON'T UNDERSTAND why I can't reverse it. Why flashing that zip messed eveything up. Like why doesn't it work now that I've restored the platform.xml backup? Are you shure that there isn't any way? It really doesn't make any sense at all.
Click to expand...
Click to collapse
Well, I didn't encounter this problem when I edited the file. But I'm just relaying other's, who had this prob and had to factory reset. I would of thought restoring the old platform.xml, setting right permission & rebooting would have fixed it, but apparently that doesn't work. You could possibly try this as a last ditch effort, but going by what other's have experienced, I think resetting is going to be the only fix.
Would you like me to upload my platform file for you to test?
EDIT: (you'll need root) here's one I prepared earlier- rename the xls to xml, move to /system/etc/permissions and set permissions (file)6,4,4: http://forum.xda-developers.com/showthread.php?p=49574602
Sent from my SM-N9005 using Tapatalk
kevin_1351 said:
I'm rooted so I tripped my knox. I have not warranty anymore...
Click to expand...
Click to collapse
Who in this world put that crazy idea in your head??? Did you even try? Maybe you should
Well I really love android, I do. And it has too many good aspects to switch back to iOS, BUT, Two things really are missing:
an uncomplicated, selfupdating store for mods (it's slowly getting better with the arrival of xposed framework but we still aren't at the same level).
Before xposed, xda was the only place for mods. And devs have to implement auto updating features in their apps themselves if they want it...
With xposed it's as I said better but not really the same actually.
And the last thing is really about my problem here. Nandroid backups/etc are good but not always an option with 25/30 gb of data on your phone (im not including media only apps and so on). So I really ask myself why there isn't a restore/reset option for some things like the system backbone, wifi, bluetooth etc. And this whole permission thing is really pathetic.
I also miss Icloud because it does backups without living a big fingerprint on the device. No bat drain and no errors. Carbon/Helium and all that other crap even titanium are really good but to complicated and battery/process hungry compared to icloud.
So while almost everything else is awesome about android IMO, this really sucks ass. And it's not that I am a noob or to stupid to backup. It's about the fact that it's not as convenient.
Well well....
Getting rid of OTA updates on a rooted device by freezing "Software Update" apps
I have a rooted Galaxy s10+ with android pie. Doesn't freezing "Software Update" system apps of my android by Titanium Backup make booting problems for my device? Is it safe for me to freeze those apps? I ask because I've heard freezing some system apps like "Device Care" stops the device from booting. As other fellas I get ota update notifications and I wanna get rid of them by freezing those apps.
not a soul to answer?
dont know, never used it on this app
why dont you just hide the notifications?
TexasHoldemJoker said:
dont know, never used it on this app
why dont you just hide the notifications?
Click to expand...
Click to collapse
because they come back, of course I tried that. you cannot just hide their notifications. They are system apps which android doesn't let you to hide their notifications. you can even stop the apps with some apps but they come back. I just wanna know the answer to my question because all other ways has already been tried and they were unsuccessful.
You can freeze the software update without issues, or at least you could back in Galaxy S4 days. Pie might work differently than lollipop.
StoneyJSG said:
You can freeze the software update without issues, or at least you could back in Galaxy S4 days. Pie might work differently than lollipop.
Click to expand...
Click to collapse
thank you for your reply but that is what I'm afraid of. As I have so many data and customization on my phone, I wanna be 100% sure that Android Pie works fine and boots successfully with frozen "Software Update" apps (there are two apps).
sorena2 said:
because they come back, of course I tried that. you cannot just hide their notifications. They are system apps which android doesn't let you to hide their notifications. you can even stop the apps with some apps but they come back. I just wanna know the answer to my question because all other ways has already been tried and they were unsuccessful.
Click to expand...
Click to collapse
I am Sure Auto notifications can hide them permanently, and it works in pie
TexasHoldemJoker said:
I am Sure Auto notifications can hide them permanently, and it works in pie
Click to expand...
Click to collapse
Thanks, I'd tried that too, it worked messy on my phone and used much of my mobile's resources. still waiting for someone to say that s/he tried to freeze the source of the problem and wiped the problem clean successfully.
sorena2 said:
Thanks, I'd tried that too, it worked messy on my phone and used much of my mobile's resources. still waiting for someone to say that s/he tried to freeze the source of the problem and wiped the problem clean successfully.
Click to expand...
Click to collapse
If you are willing to wait until i geht my next Update notifications i can try it for you, but this might Take Long?
TexasHoldemJoker said:
If you are willing to wait until i geht my next Update notifications i can try it for you, but this might Take Long?
Click to expand...
Click to collapse
lol that is very nice of you. If you don't mind messing with your Android Pie you can do it now because I just wanna see that the OS boots after freezing "software update" apps using Titanium Backup
sorena2 said:
not a soul to answer?
Click to expand...
Click to collapse
Some ideas:
Autonotification blocks permanent notifications permanently .
Or make a Nandroid backup with TWRP and restore if necessary.
Or use TWRP file manager (or aroma file manager https://forum.xda-developers.com/showthread.php?t=1646108) to backup packages .xml file (should work also on PIE) in the data/system folder, which contains information About enabled and disabled packages.
ninestarkoko said:
Some ideas:
Autonotification blocks permanent notifications permanently .
Or make a Nandroid backup with TWRP and restore if necessary.
Or use TWRP file manager (or aroma file manager https://forum.xda-developers.com/showthread.php?t=1646108) to backup packages .xml file (should work also on PIE) in the data/system folder, which contains information About enabled and disabled packages.
Click to expand...
Click to collapse
Thank you, I still wanna wait for someone who has done the freezing way. No TWRP on my mobile and I also want things to be done clean. don't like any overload by other apps like autonotification.
sorena2 said:
Thank you, I still wanna wait for someone who has done the freezing way. No TWRP on my mobile and I also want things to be done clean. don't like any overload by other apps like autonotification.
Click to expand...
Click to collapse
Ok.
Always know that having root without having a custom recovery (TWRP) can be very risky because, in case you or some root-app make your phone bootloop, you cannot recover easily (And you lose your data).
ninestarkoko said:
Ok.
Always know that having root without having a custom recovery (TWRP) can be very risky because, in case you or some root-app make your phone bootloop, you cannot recover easily (And you lose your data).
Click to expand...
Click to collapse
Thanks for your advice. Yea you are right but at the moment s10+ was just released and its TWRP wasn't working properly. I'm an advanced user but I just don't have enough time to do it all over again let alone getting back up gets much time itself.
Still waiting for the answer folks ?
SO basically you are asking someone else to potentially F*** up their phone because you are not willing to try it yourself ? Sorry, but that's how it sounds....
Cholerabob said:
SO basically you are asking someone else to potentially F*** up their phone because you are not willing to try it yourself ? Sorry, but that's how it sounds....
Click to expand...
Click to collapse
Of course not. Some people have enough time to try different software and ways to make phones better. Some even have recovery software like TWRP which can undo if something go wrong. I'm asking them to share if they had the experience I mentioned. I was one of them a while ago.
sorena2 said:
Of course not. Some people have enough time to try different software and ways to make phones better. Some even have recovery software like TWRP which can undo if something go wrong. I'm asking them to share if they had the experience I mentioned. I was one of them a while ago.
Click to expand...
Click to collapse
Cool:good: