When did this device become a POS? - Samsung Galaxy Note 9 Questions & Answers

I'm on Android 10, latest security update, etc. I've got an unlocked Note 9 on Verizon.
Last year 'round this time I was beta testing Android 9, and I reported a few bugs. I remember two in particular:
1.) When Samsung Keyboard minimizes about the upper 10% of the keyboard remains visible at the bottom of the display
2.) Often, after text has been selected, the UI doesn't present the user with the option to copy, web search, etc.
We're a year on, and I'm still having the same problems as well as myriad others. I know Samsung is a hardware rather than a software company, but I'm staggered at how poor their support for this device is.

Can't say I have experienced the same issues you have mentioned.
What other problems have you had?

Have you tried wiping the Cache Partition in Recovery Mode?
If all else fails then I would recommend that you manually reinstall Samsung's Stock Android 10 back onto your Note 9 using Odin.

Related

Oreo vs Pie - a few questions

Morning folks,
Had my Note 9 a few weeks now. Quite happy with it, and haven't updated from stock oreo yet.
Now that people have had a chance to tweak and play with Pie, I have a few questions -
1) how does battery life compare?
2) are you still able to remap the Bixby button? Currently using bxactions.
3) is split screen still available?
4) what functions have been lost, if any?
5) start functions have been gained, if any?
Look forward to hearing your thoughts.
Cheers for now,
John
There are threads here already about Pie in general (e.g. https://forum.xda-developers.com/galaxy-note-9/help/pie-one-ui-impressions-t3896792) and about your specific questions (e.g. https://forum.xda-developers.com/galaxy-note-9/help/pie-battery-life-experience-t3895668).
Jwsail said:
Morning folks,
Had my Note 9 a few weeks now. Quite happy with it, and haven't updated from stock oreo yet.
Now that people have had a chance to tweak and play with Pie, I have a few questions -
1) how does battery life compare?
2) are you still able to remap the Bixby button? Currently using bxactions.
3) is split screen still available?
4) what functions have been lost, if any?
5) start functions have been gained, if any?
Look forward to hearing your thoughts.
Cheers for now,
John
Click to expand...
Click to collapse
I can give you Information about my device with my personal using, but remember things can be diffrent from device to device and User to user.
1. Battery getting better and better. Atm i get 2.5 Days runtime with 6 h SoT
2. I guess yes. My bixbyremapper ist working fine so far..
3. You mean this app paring that you can use 2 apps together at the screen ? Then yes *Edit* maybe im too stupid but i cant find this function anymore?! ? Strange..
4. Wifi WPS for example.. more i dont know.
5. Hm my Bad english. Dont understand what you mean. I will translate and edit Posting later okay ?
Gary02468 said:
There are threads here already about Pie in general (e.g. https://forum.xda-developers.com/galaxy-note-9/help/pie-one-ui-impressions-t3896792) and about your specific questions (e.g. https://forum.xda-developers.com/galaxy-note-9/help/pie-battery-life-experience-t3895668).
Click to expand...
Click to collapse
Thanks Gary. I've had a look at these and they don't what to have been added to for a few months. Maybe they were for the beta?
John
Treasarion said:
I can give you Information about my device with my personal using, but remember things can be diffrent from device to device and User to user.
1. Battery getting better and better. Atm i get 2.5 Days runtime with 6 h SoT
2. I guess yes. My bixbyremapper ist working fine so far..
3. You mean this app paring that you can use 2 apps together at the screen ? Then yes *Edit* maybe im too stupid but i cant find this function anymore?! ? Strange..
4. Wifi WPS for example.. more i dont know.
5. Hm my Bad english. Dont understand what you mean. I will translate and edit Posting later okay ?
Click to expand...
Click to collapse
Thanks for that. I'll keep looking into it.
Cheers for now,
John
Jwsail said:
Thanks Gary. I've had a look at these and they don't what to have been added to for a few months. Maybe they were for the beta?
Click to expand...
Click to collapse
No, they're post-beta. Android Pie started distributing to US Note9s in January.
One big problem if you haven't updated yet is that your phone may be exposed to several critical remote-takeover vulnerabilities that have been fixed during the past few months.
Gary02468 said:
No, they're post-beta. Android Pie started distributing to US Note9s in January.
One big problem if you haven't updated yet is that your phone may be exposed to several critical remote-takeover vulnerabilities that have been fixed during the past few months.
Click to expand...
Click to collapse
I find the new security update really interesting.
Remote takeover? I just wonder who why and how this could be done? I just dont get it
clax6 said:
Remote takeover? I just wonder who why and how this could be done? I just dont get it
Click to expand...
Click to collapse
There's plenty of introductory material online that explains how security vulnerabilities work. Also, Google and Samsung publish monthly descriptions of the vulnerabilities they fix.
Remote-takeover vulnerabilities allow others anywhere in the world to monitor and record everything you type on your phone (including account credentials) and everything you read, see, and hear on your phone. Attackers can read, write, delete, or modify any information or media stored on your phone, or send messages from you to your contacts or to others. They can track your location and turn on your microphone and cameras.
You don't have to be singled out. Many attacks these days are automated and unleashed on millions of target devices. Large international crime organizations increasingly carry out such attacks. The most common reason is theft, but blackmail is also a growing concern. Or attackers can use your phone as a distribution center for material that they don't want traced to them.
Gary02468 said:
There's plenty of introductory material online that explains how security vulnerabilities work. Also, Google and Samsung publish monthly descriptions of the vulnerabilities they fix.
Remote-takeover vulnerabilities allow others anywhere in the world to monitor and record everything you type on your phone (including account credentials) and everything you read, see, and hear on your phone. Attackers can read, write, delete, or modify any information or media stored on your phone, or send messages from you to your contacts or to others. They can track your location and turn on your microphone and cameras.
You don't have to be singled out. Many attacks these days are automated and unleashed on millions of target devices. Large international crime organizations increasingly carry out such attacks. The most common reason is theft, but blackmail is also a growing concern. Or attackers can use your phone as a distribution center for material that they don't want traced to them.
Click to expand...
Click to collapse
Is there actually any proof that this has happened?
clax6 said:
Is there actually any proof that this has happened?
Click to expand...
Click to collapse
There's proof that some of it has happened and that all of it is easily accomplished using known exploits. What you do about it is a tradeoff, similar to home-security issues. You can leave your front door unlocked and probably not get robbed; or you can use locks, alarms etc. and possibly still get robbed. The tighter your security, the less likely it is for there to be a breach; but tighter security comes at a cost (money, convenience, etc.). So you need to weigh what you stand to lose against what you stand to gain, and that depends on individual circumstances.
Call recording and Swift installer support. Two biggest reasons for staying on Oreo for me.
This update is so bad I can only compare it to Windows ME & Vista. I downgraded thanking God because my bootloader stayed in v1.0.
It really seems like the Note 9 hardware is not built for this One UI Pie.
I'm sorry to be reading all this dislike of the Pie+OneUI update. I just bought the Note9 and really wanted to go straight to Pie+OneUI because of themes and because by now Pie should be in good shape--after all, Android 9 is a year old and has been rolled out to this device for three months? My note has been turned on for about 30 minutes, and I'm applying OS updates as I type. How bad can it possibly be?
gruuvin said:
I'm sorry to be reading all this dislike of the Pie+OneUI update. I just bought the Note9 and really wanted to go straight to Pie+OneUI because of themes and because by now Pie should be in good shape--after all, Android 9 is a year old and has been rolled out to this device for three months? My note has been turned on for about 30 minutes, and I'm applying OS updates as I type. How bad can it possibly be?
Click to expand...
Click to collapse
Just do the updates to the OS and then factory reset device.
Good as Gold from there on
Hazzay88 said:
Just do the updates to the OS and then factory reset device.
Good as Gold from there on
Click to expand...
Click to collapse
Ouch! I just booted for the first time (into a year old version of Android8), walked through initial wifi, Google, and Samsung account setup, did all the sequential updates (about 7 or 8 downloads and reboots) to get to the latest version ***CSD1 of Android9+OneUI, and then I installed about 30 of my apps, and finally installed Nova Prime and setup my homescreen (all took a few hours).
Think there will be performance issues because of all the sequential updates? Only to be remedied now by doing a factory reset? (assuming the idea is to load ***CSD1 without all the incremental update steps)... And just to confirm, a factory reset would roll me back to the latest Android9 version with security updates which were released in April this year, and not to the original year-old Android 8 that the phone device shipped with, correct? (I don't see why the updates would not also update the factory reset image)........
Okay, as I think about this... I believe there is no "factory reset image".... The way Android works is the /system partition IS the "factory reset image", and a factory reset operation simply wipes everything in the /data partition (and cache, etc). Therefore, since I did my updates before installing all of my apps, then I believe that doing a factory reset now and re-installing all of my apps would only result in a possible change to the 'stuff' in /data that relates to the initial setup: wifi, Google, and Samsung account setup--app-reinstall would result in the same states, since in both cases, apps were installed after all updates. And since wifi and account setup data is likely no different on the Oreo ROM vs Pie, a factory reset at this point seems like a complete waste of time and probably bad advice. Not so sure there is any reason to do a factory reset immediately after initial account setup and updates. I think I just rubber-chickened this thread!
In any case,
What can I test and what results should I look for to see if the sequence of updates has caused performance issues that a factory reset would cure?
Thanks for your response, Hazzay!
gruuvin said:
Ouch! I just booted for the first time (into a year old version of Android8), walked through initial wifi, Google, and Samsung account setup, did all the sequential updates (about 7 or 8 downloads and reboots) to get to the latest version ***CSD1 of Android9+OneUI, and then I installed about 30 of my apps, and finally installed Nova Prime and setup my homescreen (all took a few hours).
Think there will be performance issues because of all the sequential updates? Only to be remedied now by doing a factory reset? (assuming the idea is to load ***CSD1 without all the incremental update steps)... And just to confirm, a factory reset would roll me back to the latest Android9 version with security updates which were released in April this year, and not to the original year-old Android 8 that the phone device shipped with, correct? (I don't see why the updates would not also update the factory reset image)........
Okay, as I think about this... I believe there is no "factory reset image".... The way Android works is the /system partition IS the "factory reset image", and a factory reset operation simply wipes everything in the /data partition (and cache, etc). Therefore, since I did my updates before installing all of my apps, then I believe that doing a factory reset now and re-installing all of my apps would only result in a possible change to the 'stuff' in /data that relates to the initial setup: wifi, Google, and Samsung account setup--app-reinstall would result in the same states, since in both cases, apps were installed after all updates. And since wifi and account setup data is likely no different on the Oreo ROM vs Pie, a factory reset at this point seems like a complete waste of time and probably bad advice. Not so sure there is any reason to do a factory reset immediately after initial account setup and updates. I think I just rubber-chickened this thread!
In any case,
What can I test and what results should I look for to see if the sequence of updates has caused performance issues that a factory reset would cure?
Thanks for your response, Hazzay!
Click to expand...
Click to collapse
In your case you don't need a factory reset, you updated your device straight out of the box which is just as good as a clean install. A factory reset sometimes helps users who have been running apps for a while on the previous version, and restoring user data causes system instability due to the OS major upgrade.
Also, I've done exactly the same thing 3 months ago, and haven't had a single issue [emoji846]
Sent from my SM-N960F using Tapatalk
gruuvin said:
Ouch! I just booted for the first time (into a year old version of Android8), walked through initial wifi, Google, and Samsung account setup, did all the sequential updates (about 7 or 8 downloads and reboots) to get to the latest version ***CSD1 of Android9+OneUI, and then I installed about 30 of my apps, and finally installed Nova Prime and setup my homescreen (all took a few hours).
Think there will be performance issues because of all the sequential updates? Only to be remedied now by doing a factory reset? (assuming the idea is to load ***CSD1 without all the incremental update steps)... And just to confirm, a factory reset would roll me back to the latest Android9 version with security updates which were released in April this year, and not to the original year-old Android 8 that the phone device shipped with, correct? (I don't see why the updates would not also update the factory reset image)........
Okay, as I think about this... I believe there is no "factory reset image".... The way Android works is the /system partition IS the "factory reset image", and a factory reset operation simply wipes everything in the /data partition (and cache, etc). Therefore, since I did my updates before installing all of my apps, then I believe that doing a factory reset now and re-installing all of my apps would only result in a possible change to the 'stuff' in /data that relates to the initial setup: wifi, Google, and Samsung account setup--app-reinstall would result in the same states, since in both cases, apps were installed after all updates. And since wifi and account setup data is likely no different on the Oreo ROM vs Pie, a factory reset at this point seems like a complete waste of time and probably bad advice. Not so sure there is any reason to do a factory reset immediately after initial account setup and updates. I think I just rubber-chickened this thread!
In any case,
What can I test and what results should I look for to see if the sequence of updates has caused performance issues that a factory reset would cure?
Thanks for your response, Hazzay!
Click to expand...
Click to collapse
You won't have an issue as you had a new phone with no previous data on it.
Ps of you factory reset a device it won't go back to the OS version it came out of the box. It will remain on the latest version of the update.
Updated to Pie immediately after turning on the Note 9 for the first time, then installed my apps, then installed my sim. This is THE SMOOTHEST, best OS, best battery efficiency, best looking.....
..... it's the best!
is the note 9 Pie's camera quality improved? Still staying on Oreo for months as I have not ever heard of praises for improved cameras and still some users need to install GCam but seems note 9 Pie does not support GCam ?

Downgrade to Android 8.1

My Razer Phone 2 has, I believe, a bad battery. It shuts down without any warning whatsoever, often with as much as 40-50% remaining battery power (according to the battery indicator in the status bar). When plugged in, it operates completely normally.
I opened a support case with Razer. They initially told me, based on my serial number, that my phone was under warranty (I didn't think it was, as I bought it more than a year prior). Now, they're telling me it's not, and want me to pay a $99 diagnostic fee, and if the battery is bad, there'll be an ADDITIONAL charge (I'm guesstimating at least $200) for parts and labor. Rather than pay all that (and, on top of everything else, they're EXTREMELY slow in responding to me, often taking more than a week!), I found someone selling an OEM Razer battery for a Phone 2 on eBay, that they describe as "open box" (whatever that means), for roughly $100. I found a Razer Phone 2 tear-down video on YouTube, which makes getting to the battery seem not too terribly difficult, so I bought the battery and will attempt to replace it myself.
Anyway, once I do that, I want to re-flash the software onto my phone, and start from scratch with it. I have this app on my phone called Font Changer Lite, which I use to change the font system-wide on my phone (it requires root). Lately, it's been informing me, if I attempt to open it, that it requires system write access, which it doesn't have, and so it immediately closes. It worked fine when I first got the phone and rooted it, and I'm not sure what happened. I'm thinking it might be a result of my phone having Android 9 on it, now. When I rooted it, it was running 8.1, and I don't remember how it got 9 on it (it won't take OTA updates, since it's rooted) - give me a break; I'm old here, LOL! ? I did install TWRP, so maybe it got on there that way (it's been a while, and I don't remember exactly what procedure I followed to install TWRP).
Anyway, can I flash 8.1 from Razer's factory images, without bricking the phone (considering it's running 9, now)? I had a Nexus 6 that I somehow temporarily bricked by flashing an older version of Android (I was able to eventually recover it), and I don't want to do the same to my Razer Phone 2! I'm thinking (hoping?) that my Font Changer Lite app will work OK running on 8.1.
Thanks.
Welp, apparently there's no downgrading from Android 9 to 8.1, on these phones. I was able to replace my battery (it really wasn't difficult, at all), and now the phone operates just fine, exactly like when it was new.
However, I tried to flash the newest 8.1 release, and the phone just wouldn't boot up - it was just stuck forever at the swirling energy screen. I then flashed the most recent Android 9 release from Razer's factory images page, and it booted right up! So, I'm on Android 9, now, rooted and with TWRP.
Of course, my Font Changer Lite app is again complaining it doesn't have write access to the system partition, and it the closes, rendering it useless (it's an old app the developer stopped supporting years ago). So, I deleted it, but I'm able to use Root Explorer to change the font system-wide, by simply renaming copies of my preferred font (FuturaHandwritten) to whatever font I want to replace in System/Fonts, and it seems to be working perfectly.
One question I do have is, my phone is now again alerting me there's a system update, but it won't take (I'm sure because I'm rooted, or have TWRP as a custom recovery). It's relatively small (it was either 80 or 800 MB in size - I don't remember which; far smaller than a full system update), and said it contained security updates through July, 2020.
Is there any way to take or apply this update, without flashing back to stock, and then having to re-root/flash TWRP, and then having to go through and completely set my phone up, again (there's a LOT of time-consuming customization I perform on my phone, like changing the fonts)? I really don't want to have to do that!
Thanks.
dmw_4814 said:
Welp, apparently there's no downgrading from Android 9 to 8.1, on these phones. I was able to replace my battery (it really wasn't difficult, at all), and now the phone operates just fine, exactly like when it was new.
However, I tried to flash the newest 8.1 release, and the phone just wouldn't boot up - it was just stuck forever at the swirling energy screen. I then flashed the most recent Android 9 release from Razer's factory images page, and it booted right up! So, I'm on Android 9, now, rooted and with TWRP.
Of course, my Font Changer Lite app is again complaining it doesn't have write access to the system partition, and it the closes, rendering it useless (it's an old app the developer stopped supporting years ago). So, I deleted it, but I'm able to use Root Explorer to change the font system-wide, by simply renaming copies of my preferred font (FuturaHandwritten) to whatever font I want to replace in System/Fonts, and it seems to be working perfectly.
One question I do have is, my phone is now again alerting me there's a system update, but it won't take (I'm sure because I'm rooted, or have TWRP as a custom recovery). It's relatively small (it was either 80 or 800 MB in size - I don't remember which; far smaller than a full system update), and said it contained security updates through July, 2020.
Is there any way to take or apply this update, without flashing back to stock, and then having to re-root/flash TWRP, and then having to go through and completely set my phone up, again (there's a LOT of time-consuming customization I perform on my phone, like changing the fonts)? I really don't want to have to do that!
Thanks.
Click to expand...
Click to collapse
so i have att unlocked razer phone 2 and have camera issue ( when you start camera app screen is black for about 40seconds and then camera starts but autofocus is not working, back camera functions normal) and most annoying sometimes while in call people cant hear me well. on roms site theres only 2 roms for att. 8.1 and 9 tried 8.1 and stuck on powered by android screen. then installed 9 and it worked but my issues still there...
what if I flash rom for global version? will it brick?
or maybe any other suggestions on how to fix this issues?

Some hand holding with firmware upgrades, running LOS+microg

I have been running LineageOS+MicroG on my last 3 phones but am mostly a novice. LineageOS just packages things well enough that getting it installed is pretty easy. Most recently, I updated to 17.1 on my Payton device, and voila, I've got a problem where the phone reboots after powering on. Happens much faster with the radios on, much slower with safe mode and airplane mode on. So the obvious answer is usually "flash back to stock and try again". Here come my questions... Please keep in mind I also run Linux.
1. When people talk about going back to stock, doesn't this always entail losing your data? How do those of you who use your phone as a daily driver manage this? I've not heard great things about doing TWRP backups, and the amount of configuration I have to do at new-install time is crazy.
2. While running LineageOS or other such custom ROMs... How do you get "hardware updates": upgrades to things like modem/radio firmware that are outside the realm of the OS (if there is such a thing). I've had a few problems (including the current one) that I _suspect_ are related to running old "firmware" as I would normally call it. The solutions that I _think_ I've seen for this look like they are Windows-specific and also require going back to stock or losing your data. It's puzzling to me why updating hardware would require going back to stock, unless you need to let the stock OTA updates install in order to actually GET that firmware.
1) To my knowledge and at least for me, 'we' are using Android 9 firmware with Android 10 OS. I do not expect any further firmware updates.
2) I've been told that LOS is running slower on X4 compared to other ROMs such as Pixel Experience, but I can't speak for either as I use HAVOC. I can't speak for the rebooting issue though, I haven't looked at the X4 LOS thread much.
*3) LOS to my knowledge woln't work with MicroG because it doesn't allow for spoofing. HAVOC does, and personally I was using Android 9 w/ HAVOC and MicroG so I could use the GCam but due to personal reasons I had to install GPlay and so at the same time I also upgraded to Android 10. One point at least in my experience, the phone was getting more and more difficult to use over time but rebooting the phone fixed it completely. I almost never rebooted my phone back on 9 so it caught me off guard personally.
It sounds like you might be trying to go down a more privacy centered phone like I was until recently. Personally, I liked the Android 9 w/ HAVOC and MicroG. I can give you my list of apps I used but you probably know most of them (Simple Mobile Tools, OSMAND, K9, Fennec, NewPipe, VLC ect.) The launcher would get a little buggy (context menus would stop working after a while on app icons) and for some reason the audio would start for a split second, pause, for a sec, then continue. Other than that, it was great. I used that config setup for a year.
On a completely unrelated note, AT&T will most likely not work with the unlocked X4 after a couple of years, doesn't affect me but just a heads up.

Prosecution in Canada can zap Samsung phones.

It happened 4 times, the first 3 were over 8 hours, the screen turns black with some slight flickering, no hard reset, powering off works.The phone was fully debloated via adb with 0 processes running with dev options, the only thing left was Samsung Assist but who knows what’s in those system apps. The 4th time fried it making me lose my 2fa keys. It happened on Android 9 and 10.
I had the full system tracing on from dev options running because I knew he was about to do it again.
I was doing nothing nor am I a criminal, I proved my innocence and this was after my trial.
There’s a reason they won’t allow root but anyway we all know they’re garbage. Google allows root if you’re able but those things are just surveillance devices.
Sounds like a software issue... but could hardware too.

Downgrading S20 FE 5G SM-G780G Android 13 One Ui 5.1 to Android 11

hello
i've never downgraded/flashed any firmware on this device before, so before i do something that might be fatal/result in bricking my phone i would like to ask is it possible to downgrade a S20 FE android 13 to android 11? while my one ui version is 5.1 i haven't updated the security patch to the april one (the one that changes your binary) it's currently the 1 march 2023 one
i've already checked & downloaded a firmware with the correct binary number so now all i need to do is flash it
Welcome to XDA.
You're limited by the bootloader version to how far you can roll it back. If the bootloader was upgraded too, you're boned. The 5th digit from the rear is the significant digit that determines that. If the rom's 5th digit is the same or higher value you can flash it. If lower, no go.
kiyan_ said:
hello
i've never downgraded/flashed any firmware on this device before, so before i do something that might be fatal/result in bricking my phone i would like to ask is it possible to downgrade a S20 FE android 13 to android 11? while my one ui version is 5.1 i haven't updated the security patch to the april one (the one that changes your binary) it's currently the 1 march 2023 one
i've already checked & downloaded a firmware with the correct binary number so now all i need to do is flash it
Click to expand...
Click to collapse
Hi, I downgraded my S20 FE several times from 13 to 12 with the same binary (obviously) with no issues at all, so you can downgrade easily.
In my experience on samsung devices (literally I flashed a hundred times on different devices) it's very unlikely that you brick your device with odin, even if you use a wrong firmware for your device....the only thing that it may brick a device is because it has a hardware damage
rgrapow said:
Hi, I downgraded my S20 FE several times from 13 to 12 with the same binary (obviously) with no issues at all, so you can downgrade easily.
In my experience on samsung devices (literally I flashed a hundred times on different devices) it's very unlikely that you brick your device with odin, even if you use a wrong firmware for your device....the only thing that it may brick a device is because it has a hardware damage
Click to expand...
Click to collapse
Hello
This will depend on your variant.
on the G780G (binary 3) and G781B (binary 4)
You can download to android 11.
since it has the same binary.
Of course, you should do it from 0.
do not install via CSC_HOME.
The installation must be clean.
before all make backup.
blackhawk said:
Welcome to XDA.
You're limited by the bootloader version to how far you can roll it back. If the bootloader was upgraded too, you're boned. The 5th digit from the rear is the significant digit that determines that. If the rom's 5th digit is the same or higher value you can flash it. If lower, no go.
Click to expand...
Click to collapse
yes it is the same value
mine G780GXXU3EWB2
the firmware i downloaded G780GXXU3AUH5
which would make both binaries '3' right? would this be okay?
rgrapow said:
Hi, I downgraded my S20 FE several times from 13 to 12 with the same binary (obviously) with no issues at all, so you can downgrade easily.
In my experience on samsung devices (literally I flashed a hundred times on different devices) it's very unlikely that you brick your device with odin, even if you use a wrong firmware for your device....the only thing that it may brick a device is because it has a hardware damage
Click to expand...
Click to collapse
thank you for your answer & sharing your experience, this is what i've been looking for
kiyan_ said:
yes it is the same value
mine G780GXXU3EWB2
the firmware i downloaded G780GXXU3AUH5
which would make both binaries '3' right? would this be okay?
Click to expand...
Click to collapse
since it has the same binary.
Of course, you should do it from 0.
do not install via CSC_HOME.
The installation must be clean.
before all make backup.
rgrapow said:
the only thing that it may brick a device is because it has a hardware damage
Click to expand...
Click to collapse
Or if the battery has insufficient charge or capacity. Any time you flash a device you take some level of risk. A power outage with no or insufficient battery backup for the PC would also end badly.
The risk is also greater with Androids because it's not a small couple dozen MB flash that's done in seconds. Lots more time and data for things to go wrong. If my Canon pro cam had a bad flash, Canon would likely repair for free or a reasonable charge. Samsung will do neither of these... repair cost plus a new mobo loaded with the latest firmware. perfect.
mezacorleehone said:
on the G780G (binary 3)
Click to expand...
Click to collapse
yes that is my phone variant
mezacorleehone said:
do not install via CSC_HOME.
Click to expand...
Click to collapse
may i ask why is that?
kiyan_ said:
yes that is my phone variant
may i ask why is that?
Click to expand...
Click to collapse
the CSC_HOME file
comes in the software you just downloaded.
unlike normal CSC.
The CSC_HOME is used to only update the system, without deleting anything.
in your case you are going to downgrade, use the normal CSC without _home.
thank you everyone for the help & answers
kiyan_ said:
thank you everyone for the help & answers
Click to expand...
Click to collapse
You are welcome.
where possible we collaborate.
blackhawk said:
Or if the battery has insufficient charge or capacity. Any time you flash a device you take some level of risk. A power outage with no or insufficient battery backup for the PC would also end badly.
The risk is also greater with Androids because it's not a small couple dozen MB flash that's done in seconds. Lots more time and data for things to go wrong. If my Canon pro cam had a bad flash, Canon would likely repair for free or a reasonable charge. Samsung will do neither of these... repair cost plus a new mobo loaded with the latest firmware. perfect.
Click to expand...
Click to collapse
I'm referring about samsung devices based on my experience (trial and error), I had a lot of bricks, soft bricks and I was able to solve it with odin.
kiyan_ said:
yes it is the same value
mine G780GXXU3EWB2
the firmware i downloaded G780GXXU3AUH5
which would make both binaries '3' right? would this be okay?
Click to expand...
Click to collapse
Yes, exactly. Why do you want to roll it back?
If it's a specific issue finding a work around may be easier.
Android 11 is no picnic either. I prefer Pie, Android 10 is ok; I'm running both and will likely never upgrade them.
Regardless you will need to lock it down so it can't do OTA upgrades/updates. That's the first thing I do on my Samsung's... once bitten, twice shy Upgrades and updates can and do break Samsung's... then you have find work arounds and fixes.
blackhawk said:
Yes, exactly. Why do you want to roll it back?
If it's a specific issue finding a work around may be easier.
Android 11 is no picnic either. I prefer Pie, Android 10 is ok; I'm running both and will likely never upgrade them.
Regardless you will need to lock it down so it can't do OTA upgrades/updates. That's the first thing I do on my Samsung's... once bitten, twice shy Upgrades and updates can and do break Samsung's... then you have find work arounds and fixes.
Click to expand...
Click to collapse
other than battery run out faster & the phone feeling a bit sluggish nothing specific....it's just i've already debloated my phone & disabled many features of the phone that i dont use and dont plan on updating my phone anymore and while that does help improve things quite significantly i just thought at this point why dont i just might aswell downgrade the phone
before i had this phone i was fine staying years with a phone that stopped receiving updates after android 6 lol just that it eventually ran its course and after several hardware problems & the phone giving up by itself (every 3 weeks or so it'll get stuck on bootloop for no reason) i assume it was time for me to buy a new one...too bad
rgrapow said:
I'm referring about samsung devices based on my experience (trial and error), I had a lot of bricks, soft bricks and I was able to solve it with odin.
Click to expand...
Click to collapse
I'm glad that's working well for you. I use to always be playing with my PC's like that. With Androids I took a more conservative approach; less down time, more play time.
I leave the firmware be on my 2 stock N10+'s. They run very good, fulfill their mission and it's simply not worth the risk or time. I don't allow firmware upgrades or updates. This N10+ in my hand is still running on Pie, firmware is 3.5 yo, and the current load will be 3 yo this June. No malware in all that time; security isn't an issue. Still fast, very stable with minimal maintenance. It's also heavily optimized and running well; I have zero incentive to change the playing field by altering the firmware.
My SQlite scores are lower than they should be in spite of my fast disk r/w scores so eventually I may do a factory reset to try to resolve that. Lol, that's the full extent of my ambition at the moment.
blackhawk said:
Upgrades and updates can and do break Samsung's... then you have find work arounds and fixes.
Click to expand...
Click to collapse
yep. i learned the hard way
i'm quite green at this stuff and at first i just thought "more upgrades & updates means good! i should get the most out of this device" but alas after some serious overheating & battery draining problems over loads of features i dont even use.....
kiyan_ said:
other than battery run out faster & the phone feeling a bit sluggish nothing specific....it's just i've already debloated my phone & disabled many features of the phone that i dont use and dont plan on updating my phone anymore and while that does help improve things quite significantly i just thought at this point why dont i just might aswell downgrade the phone
before i had this phone i was fine staying years with a phone that stopped receiving updates after android 6 lol just that it eventually ran its course and after several hardware problems & the phone giving up by itself (every 3 weeks or so it'll get stuck on bootloop for no reason) i assume it was time for me to buy a new one...too bad
Click to expand...
Click to collapse
Anything below Android 9 is suspectable to partition worming nasties like Xhelper. Run Android 9 or higher. Android 9 is relatively secure unless you do stupid things.
All Samsung's should be optimized. You will still have scoped storage running on Android 11 anyway. If you don't mind the UI of Android 13 I would try to find what's causing the issues.
Disable global power management then go after the power hogs on an individual case by case basis. A logging firewall is useful in finding them. Cloud, and social media apps are prime offenders. Try temporarily disabling Google play Services and see if this helps; Google backup Transport, Gmail and Playstore are dependencies of it. Enable as needed. 5G can also suck a lot of power and is inefficient when doing small bandwidth transfers. Wifi isn't needed if you have an unlimited data plan. Use Package Disabler or abd/ladb edits to take out the really problem apps that can't be resolved in settings. Don't go too nuts though; target the hogs and totally worthless apps like Digital Wellbeing. Most of the dozens a small Samsung system apps are best left alone as many modify the UI and consume very little resources. Understand what the app does and it's dependencies if any before disabling whenever possible.
Play with it...
blackhawk said:
Anything below Android 9 is suspectable to partition worming nasties like Xhelper. Run Android 9 or higher. Android 9 is relatively secure unless you do stupid things.
All Samsung's should be optimized. You will still have scoped storage running on Android 11 anyway. If you don't mind the UI of Android 13 I would try to find what's causing the issues.
Disable global power management then go after the power hogs on an individual case by case basis. A logging firewall is useful in finding them. Cloud, and social media apps are prime offenders. Try temporarily disabling Google play Services and see if this helps; Google backup Transport, Gmail and Playstore are dependencies of it. Enable as needed. 5G can also suck a lot of power and is inefficient when doing small bandwidth transfers. Wifi isn't needed if you have an unlimited data plan. Use Package Disabler or abd/ladb edits to take out the really problem apps that can't be resolved in settings. Don't go too nuts though; target the hogs and totally worthless apps like Digital Wellbeing. Most of the dozens a small Samsung system apps are best left alone as many modify the UI and consume very little resources. Understand what the app does and it's dependencies if any before disabling whenever possible.
Play with it...
Click to expand...
Click to collapse
i've done all that hahahah
other than youtube i don't have any other social media apps installed and i've already got rid of chrome & switched to a lighter browser
yep i like to experiment, i suppose the flashing stuff is the next step after all of that (yes have tried factory reset several times too, i don't mind as there aren't any important data in my phone but still, possibly getting a priceful item bricked over my messing around isn't something i'm too excited about, that's why i still like to ask around)
also what got me the idea was that i've also read from several people with the same device saying that with every android updates the phone gets even more sluggish
kiyan_ said:
yep. i learned the hard way
i'm quite green at this stuff and at first i just thought "more upgrades & updates means good! i should get the most out of this device" but alas after some serious overheating & battery draining problems over loads of features i dont even use.....
Click to expand...
Click to collapse
I learned the hard way with Samsung's too.
After the upgrade to 13 did you do a factory reset? If not, now is the time. Don't use SmartSwitch; do a clean load by importing all the critic data yourself.
At the very least clear the system cache.
I use Package Disabler to disable about 70 apps. It's not as bad as it first seems. Android 10 literally has about 100 more new system apps than 9. Most of those new ones should be left alone. My disable list for the Android 9 N10+ vs the Android 10 one is almost identical though.
Samsung's do lots of cool things so don't be too concerned until you learn more about the features. Bixby got killed right out of the gate; it's a hog and it's EULA is one of the worst I've ever read.

Categories

Resources