Ever since I upgraded my Verizon S8+ to firmware G955USQS1AQI6 two months ago, I have been noticing decreased battery life (last night my phone lost 22% with aod turned off, most of the drain coming from Android System and Android OS) and more stuttering in general, which is why I have been scared to install anymore updates on my phone. I want to downgrade to the G955USQU1AQGL firmware, which was what I had before installing the crippling update. The question is, if I flash the firmware to my phone from my computer using Odin, will I lose any data?
Yes, you will lose your data. Although I believe if you don't flash a CSC file, it won't wipe it. Don't take my word for it, though.
In most software packages, there will be a CSC file and a CSC_HOME (or HOME_CSC) file. If you flash the file with "home" in it, it should retain your userdata. It will still say "erasing" as it wipes out your cache but when it reboots it should still have your data. Be careful, though. Rolling backwards without a wipe might cause even more issues/drain as it's not an official upgrade path.
Related
Hi all,
I have Galaxy Note 2 LTE N7015T version on Telstra firmware.
I was previously on 4.1.1 rooted with CF-Auto Root
I wanted to upgrade to 4.1.2 and had a few issues in the process. I finally got phone to allow upgrade since it was showing as modified. I did an upgrade via Kies and had an issue where when it was at the stage uploading firmware to phone it got stuck at 4%
I was doing upgrade via the USB 3 port and heard this can cause issues. I pulled the plug and then Kies wanted to do an emergency firmware upgrade which by all accounts worked to 4.1.2 and still remained data intact
Now I noticed lately that phone was lagging so I did a full factory reset and start again. But still I am getting some lag issues. I did not re-root since going to 4.1.2 but one thing I noticed is that I used the app ES File Explorer it allows me to navigate to the Root folder which I thought required Root Access?
Anyway I noticed there is still a folder in there called root I guess from before?
Any recommendations to fix phone from lag? Should I reflash firmware from here using Odin? Does that reformat the root dir? Cheers
I've done a lot of digging through the forum and can't find an answer, so forgive me if this is an already-answered question.
I have a T-mobile S4 with a camera stuck on the classic "updating camera firmware" error message with black screen. If I open Snapchat the front facing camera will work, but with a slight delay in projection.
Here's the thing...this has happened on two separate phones now and on both of them it happened about 48 hours after I signed into the phone with my google account. Is it possible there is some kind of malware attached to my google account?
In the newest phone I have done a clean full wipe using TWRP, then Odin-flashed a full firmware package I found here on xda (recovery, OS, modem, kernel). Cache wipe and factory reset immediately after rebooting from Odin mode. Still have problem.
Have switched out known good cameras from other phones, and the phone I'm working on was functioning perfectly until I signed into it with my account. Totally stumped here, and really need some assistance.
Phone is:
M919 logic board in I337 body
Kitkat 4.4.4
Baseband: M919UVUFNH7
Kernel: 3.4.9-6281449, [email protected] #1
Build: KTU84P.M919UVUFOK3
Security software version: MDF v1.0 release 3, VPN v1.4 release 2
If anybody's got some ideas, please let me know!
Ok, no answers yet but plenty of views, so either this is an extremely rare issue that no one knows a solution for, or it's a ridiculously stupid question that everyone knows the answer to. I'm going to try and keep a log of what I'm doing with this phone in case any other rookies need assistance in the future.
So far I've flashed three different versions of stock Kitkat onto the phone....OH3, OK3 and NH7. When I flash OK3 my build number doesn't match my baseband (baseband reads NH7)...not sure what's going on there. Also, if I flash OK3 I lose my wifi....do not have this problem with other versions of firmware. Each flash is done after a full clean wipe with TWRP.
I found a thread that mentions an almost identical camera issue being caused on an M919 that was flashed with Nottache Xposed framework for AT&T phones. The OP said they could fix the issue by wiping the framework off the phone. Since my M919 motherboard is installed in an I337 body, I'm wondering if this is something related to a compatibility issue between T-Mobile and AT&T components. Best lead I've got so far.
Two posts have mentioned a fix. One says he opened Google Edition Camera Photosphere and his problem went away. He was running a different machine than mine so I haven't tried this yet, but I'm doubtful. The other user said they have only been able to solve the cam issue by installing a stock modded kernel by @jovy23. All the links I've found to this kernel are dead now, so no dice there.
I'm gonna put my M919 motherboard into an M919 body, wipe and flash stock rom again and see if somehow that does anything.
As a side note, I started getting "SIM not inserted" errors just before I began flashing different roms, and since the initial flash I've lost my SIM completely. So now I've got no camera, no SIM card being read, and sometimes losing wifi. I need this phone for work, so this is kind of sh*tty.
You cant downgrade once youve updated to OK3. The order would have to have been NH7, OH3 then OK3. It seems like mabey its not flashing correctly. Try a different odin program 3.04 3.07 3.09 are good ones. Flash it twice, untick auto reboot and manually power off and back into download mode and flash again. Dont use adv reboot menu to boot into download or it may not flash correctly. If that doesnt work I'm not sure what else to try. Good Luck
Ok, latest update for future readers...
It seems that lordodin912 is right when he says that flashing to OK3 means you can't flash backwards to a previous baseband/build. I hadn't seen that info anywhere so I didn't know about it. I'm not sure how to go about finding this kind of info on the forum but it would have been nice to know ahead of time. Anyhow...thank you for that information lordodin.
Here's where I'm at now:
-I was originally on NH7 with the camera error and sim card error. Flashed NH7 full stock after doing a full wipe and still had problems.
-Flashed OK3 full stock after full wipe and still had the problems, and also lost wifi capabilites (as in the phone wouldn't turn on wifi at all). At this point the baseband read as NH7 but the build read as OK3. I don't know why.
-Tried flashing OH3 after that (didn't know any better) and it wouldn't take. At this point wifi capabilites returned but still no cam and not reading sim card.
-Flashed OK3 again and wifi returned but still no cam and no sim. A couple hours later I powered the phone off and then back on, and Samsung then notified me of OTA updates. This update notification hadn't appeared before I manually rebooted the phone. I took the updates and now have wifi, sim card is being read, and my camera appears to be functioning properly as well. About 20 minutes or so after the updates are applied, the sim card error returned and told me to restart the phone. I did so and now the phone is reading the sim card again.
Right now my best guess is that when I was on NH7 I had accidentally made some app and update settings changes that prevented me from receiving some of the important OTA updates connected to camera and sim functioning, and this caused incompatibility between certain parts of the firmware that had been updated and others that had not. Trying to flash OH3 failed to solve the issue because I had already flashed OK3 before that and you can't go backwards from OK3. I don't know why the initial OK3 flash failed to fix anything, but I'm guessing the flash just didn't take as well as I thought it did. Flashing OK3 twice in a row seems to have done the trick, I presume because it reset and updated everything so that all firmware was compatible with itself.
I don't know how this could have happened (I try to be very careful about what I freeze and uninstall), but it's the most likely culprit because after flashing the latest firmware manually (twice) and allowing OTA updates my phone returns to proper function. Why OK3 didn't work correctly at first is beyond me....I don't see why it should have taken a few hours or a second reboot for OK3 to begin offering updates but whatever.
I'm doubtful that the camera will continue to work after the next 48 hours, but we'll see. I'll report back in with what happens after a few days go by.
Leaving an update here as I said I would.
For two months the phone has been functioning properly. Camera, sim and wifi have all been good. About one week ago my camera started acting glitchy again and then stopped working. The problem is the same as before- upon opening camera app the screen is black with a message saying "updating camera firmware", then nothing happens. This occurred around the same time I started using google hangouts frequently...don't know if that is related to the issue or not.
Yesterday the phone began showing the error message about sim card not being read, and then today it stopped reading the card altogether.
I repeated the same procedure that seemed to fix these problems two months ago and it hasn't done the trick. Full clean wipe of phone using TWRP, then installation of Chainfire's Autoroot, then flashed OK3 stock firmware twice with battery pulls between installations. Factory reset immediately after install of stock ROM. When connecting to wifi, no OTA updates appear. Camera not functioning, sim card not being read.
Phone shows baseband and build number are matching. I have no ****ing idea what the problem is with this phone. Beyond frustrated.
Anyhow, I'll keep updates going as long as I am working with this thing, maybe it'll help someone later. Anyone knows anything that could help, feel free to chime in.
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
aclays said:
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
Click to expand...
Click to collapse
What model?(network)
aclays said:
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
Click to expand...
Click to collapse
go install a custom rom like jasmineROM or EmotionOS, straight up stock can sometimes be unstable when you are rooted.
ziggy71 said:
What model?(network)
Click to expand...
Click to collapse
Verizon SM-N910V retail
weard1212 said:
go install a custom rom like jasmineROM or EmotionOS, straight up stock can sometimes be unstable when you are rooted.
Click to expand...
Click to collapse
I can't even get it stable on full stock. I Odin'd in the Full Firmware for CPF3 in this thread: [Firmware] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU2CPF3] by hsbadr which overwrote TWRP and seemingly removed all traces of rooting, yet the instability is still there.
It occasionally is giving me the error "System process stopped", occasionally is rebooting entirely, there have been a few times where it wouldn't boot up at all. I had to pull the battery and leave it out for 5-10 minutes to get it to boot. I'm running out of ideas on what to flash over to fix it. Is it possible that the Kernel I installed while rooted is causing problems? The full firmware for CPF3 should have overwritten it, correct?
aclays said:
Verizon SM-N910V retail
I can't even get it stable on full stock. I Odin'd in the Full Firmware for CPF3 in this thread: [Firmware] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU2CPF3] by hsbadr which overwrote TWRP and seemingly removed all traces of rooting, yet the instability is still there.
It occasionally is giving me the error "System process stopped", occasionally is rebooting entirely, there have been a few times where it wouldn't boot up at all. I had to pull the battery and leave it out for 5-10 minutes to get it to boot. I'm running out of ideas on what to flash over to fix it. Is it possible that the Kernel I installed while rooted is causing problems? The full firmware for CPF3 should have overwritten it, correct?
Click to expand...
Click to collapse
I've had some issues myself. I originally used paul pizz PJ2, which is an awesome rom. Gives you stability of stock, but feel of custom. I then went to PL1 and EmotionOS. After a few days, I noticed, reduced connectivity, camera wouldn't focus, and button reassignments. So, I just wiped cache and Dalvik, stuck in boot loop. I downloaded the newest EmotionOS. Wiped everything, installed it. boot loop. So I did a another wipe and installed the deodexed Ricks ROM V2. So far so good, but it has only been a day. If you do a full retail firmware flash, that should fix your issues. If you did a full firmware, then yes, it would be overwritten. Try going back to 5.1.1 PA1 full firmware flash. Then you could allow the phone to take the OTA if you wish. But, that should fix the issue. If not let me know. And I will keep you informed of the new rom. Also, if you have a card reader, check your sd. Take anything that you want off of it, and wipe it as well. These Notes are finicky.
ziggy71 said:
I've had some issues myself. I originally used paul pizz PJ2, which is an awesome rom. Gives you stability of stock, but feel of custom. I then went to PL1 and EmotionOS. After a few days, I noticed, reduced connectivity, camera wouldn't focus, and button reassignments. So, I just wiped cache and Dalvik, stuck in boot loop. I downloaded the newest EmotionOS. Wiped everything, installed it. boot loop. So I did a another wipe and installed the deodexed Ricks ROM V2. So far so good, but it has only been a day. If you do a full retail firmware flash, that should fix your issues. If you did a full firmware, then yes, it would be overwritten. Try going back to 5.1.1 PA1 full firmware flash. Then you could allow the phone to take the OTA if you wish. But, that should fix the issue. If not let me know. And I will keep you informed of the new rom. Also, if you have a card reader, check your sd. Take anything that you want off of it, and wipe it as well. These Notes are finicky.
Click to expand...
Click to collapse
So I did actually go back to stock 5.1.1 and successfully take the 6.0.1 OTA, the issue didn't resolve. At that point I flashed the full stock CPF3, still no changes.
A new thing has popped up too. When I try to boot into recovery it says it's installing an update, then after about 5 minutes it goes to a black screen and nothing happens. I end up having to pull the battery to restart it. Discovered that when I tried to go clear all the caches and such before flashing CPF3, and it is still doing the same thing after flashing CPF3. I thought that by flashing the full firmware for CPF3 it would solve that.
aclays said:
So I did actually go back to stock 5.1.1 and successfully take the 6.0.1 OTA, the issue didn't resolve. At that point I flashed the full stock CPF3, still no changes.
A new thing has popped up too. When I try to boot into recovery it says it's installing an update, then after about 5 minutes it goes to a black screen and nothing happens. I end up having to pull the battery to restart it. Discovered that when I tried to go clear all the caches and such before flashing CPF3, and it is still doing the same thing after flashing CPF3. I thought that by flashing the full firmware for CPF3 it would solve that.
Click to expand...
Click to collapse
So you are full stock? Does the update issue happen on the stock recovery?
ziggy71 said:
So you are full stock? Does the update issue happen on the stock recovery?
Click to expand...
Click to collapse
Yep it did. So I think I've actually fixed it now. I thought that flashing the full firmware would also flash the boot loader and modem, but I Odin'd both of those in and so far so good! It did the whole updating thing again just like before this time, but when it was done it actually loaded up recovery like it was supposed to. So at that point I wiped the cache, factory reset, then used Odin to flash in the boot loader and modem for CPF3 that I found in that thread.
I've been using my phone and installing things for a couple hours now and haven't had a single hang. Before I did this, it would hang very quickly. Maybe I'll get brave and try rooting and whatnot again later, but for now I'm just going to back off for a bit. Thanks for the help!
And so much for that. It was more stable than it had been in ages so I started installing all my apps and whatnot, now it's just as unstable as it used to be, just took a couple days to happen. I'm running out of ideas
Hi All,
was very happy with P2 and decided to go for Nougat update, phone was great, no issue after, no errors, I was impressed, then updated to 233, and again phone was just fine, battery life was even better, Bluetooth was working better, very happy, but after one week phone gone crazy, sim management, android system and media keep eating battery, tried wipe cache in recovery, no help, decided to do hard reset, no help, but now phone can't find any music on sd card, and even better, there in no any tones, alarms, anything left on the phone, any advise please?? many thanks..
I'm sorry this happened to you. Did you do a hard reset after upgrading to s233?
Hard reset on this model basically means you wiped the whole internal memory clean. Are you sure the phone is supposed to find any files when it's not?
Yes, I done it, tried reflash 232 but always fail on 50%, when I reflash 233 let me do it, but is only small ota 78mb, not changing anything, and factory reset again, not repairing anything..
You're on custom ROM? I've read about the SIM-managment drain on some of them.
NO, I am on stock Nougat Rom S232 and had OTA update S233, and after week phone for some reason gone crazy, and I am trying to work out why, and if someone somwhere got Full S233 rom, not just OTA, which I could reflash in Lenovo recovery...
When I reinstalled full stock S233 , and problem was fixed, it must be something with sd card, and I finded problem, it was corrupted photos and video file on sd card. all back to normal SOT 12-13 hour per charge..
i had no issues what so ever as i wiped everything before and after the update if you look on the forum there is a way to downgrade to mm (thats what i think you should do then wipe everything hard reset through recovery) leave your device for a couple days then re-upgrade to N do another wipe through the recovery option and it should fix any issues (i know its a lot of hastle but its the best way to stop issues)
Anybody else with this problem? My 6 Pro gets soft bricked with the
SD1A.210817.036.
It loses the signal (Tmobile) then restarts to recovery saying
“Cannot Load Android System. Your Data May Be Corrupt” It gives me the option to "Try again." or to "Factory data reset."
Device Completely stock
This is what I have done
1
Try Again (Same behavior)
2
Factory Reset (Multiple times), would let me finish the setup but as soon restores my data and apps happens all over again.
3
Sideload Rescue OTA (SD1A.210817.036.) same ****
4 now with heavy weapons
Unlocked bootloader, manually flashed factory images (Unlocked) the factory image it's an older version but seems to work perfectly (I'm able to set up and restore my data, but the phone automatically downloads the OTA update and the same thing all over.
5
Got a device replacement (Hella lucky they had my device in stock)
6
Different new Pixel 6 Pro Same behavior as soon the OTA hits and finishes to restore my apps.
7
Tried Manually flash, use the online google tool with different builds (tried the Tmobile stock)
Always the same problem.
There's any way to wipe/repartition only the System portion? I remember having something similar back in the days with an S2 and was able to fix it with a Reflashing of the PIT partition through Odin
Any suggestions?
Only thing I see consistent is the data being restored. That data could be corrupted. Not sure if that's possible. Try setting up as new device or from a different backup.
I think"new device" is the way to go. Over the years I've found some apps don't work with a new update.
Points 5 and 6 suggest that it's something to do with your data and app restore causing the issue.
How modified was your previous device?
Just got my Pixel 6 Pro yesterday. I have had to restore 3 times. The first two were from a back up and the third time, from scratch and the same thing is happening. It took a while for the third time to happen (over night and a few hours into the day) and I thought I was safe and put a screen protector on and then bam! Just before it happens I get a lot of the Google apps like phone app and some heat app crashing, then it reboots and says Android is corrupt.
Corrupted data error message after December update
Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
forum.xda-developers.com