Marshmallow 6.0 official firmware update and now no downloads - G4 Q&A, Help & Troubleshooting

The phone updated to Marshmallow and now all downloads just hang. Nothing happens at all for hours.
Googling suggests that I need to wipe the cache partition (well something to try before a full wipe) and I in order to that I need to get into recovery.
And that's where my problems start (well besides the initial problem). I can't get the phone to boot into recovery. Does it perhaps not have a stock recovery (international version)?
If it doesn't what recovery should I install? (Phone is currently not rooted and has a locked bootloader as far as I know). Just want something to wipe the cache partition, nothing fancy as the phone is meant to stay as stock as possible.
Or how else should I proceed (before I get to the full wipe/factory restore option)?

Don't bother, just go for the full wipe now and save yourself days of wasted time.
Marshmallow update requires a factory wipe after installation, I don't know why LG didn't make this part of the update but they didn't.
If it's still broken afterward then flash the full firmware again using bridge.

Well that's fantastic news....
I really didn't want to resort to that.
The rest works great/as good as before, it's just the downloads that are stuck...sigh...oh well. Thanks.
Here's to 2-3 days of downloading and setting everything up again anyways (slow net) :/

Use the LG backup app, it isn't perfect but I was up and running again within a couple of hours.

Related

[Q] Grand rebooting problem help

my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
chrowley said:
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
Click to expand...
Click to collapse
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
ashwin77sgg said:
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
Click to expand...
Click to collapse
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
chrowley said:
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
Click to expand...
Click to collapse
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
ashwin77sgg said:
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
Click to expand...
Click to collapse
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
chrowley said:
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
Click to expand...
Click to collapse
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
ashwin77sgg said:
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
Click to expand...
Click to collapse
i already tried it sir but it didnt solve the problem, it passes the setup but after a few minutes the phone reboots.
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
naufalhadyan said:
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
Click to expand...
Click to collapse
This is probably the best explained and most direct definition of what to do and what may be happening with our ever-rebooting Grands.... Thank you!!!
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
victorsmarotta said:
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
Click to expand...
Click to collapse
Even iam facing the same issue
phone reboots automatically and doesnt even start... infinite bootloop. Was working fine and suddenly this issue came up from nowhere(past 2 weeks) ..
Iam using Resurrection rom 5.7.4 (Marshmallow)
Damn I was on AICP 11, when this exact strange bootloop problem occurred for no rhyme and reason. I know the hardware is fine, the issue arises from installing apps from playstore, the moment it goes beyond a certain app limit in the device, it will start endless bootloop, I am sure this is Google's doing. Anyways this is not a hardware issue and I know more people will be coming here looking for answer to this issue. I have tried both the opengapps and deltagapps, same behaved this way, it never happened before and lately google have introduced one other app which is google's android instant app that will sit in your device, even though you need it not not. very well google for using our precious internal data to around 500Mb to 1Gb.
formating data partition solves this issue, temporarily but you lose your apps and data.
I had successfully avoided this issue when I stopped installing more apps on my device, It took me 2 tries and I found a perfect balance of 4-5 apps, it came crashing again when I tried installing the 7th app.
I don't know if other ROMs will be able to handle this bug, but I know it's time for me to look for another ROM, I was happy with AICP 11, for more than a year. Sad.
Reading about this issue, I came to know this is prevalent on all CM marshmallow based ROMs. So, going to flash Nougat or kitkat or the stock ROM should probably fix this.
Try a new battery.

What the What?!

Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )

Need major help/advice from the community

I'm so disconcerted right now. I have the Verizon LG G3, everything stock but rooted, and just recently was fiddling with the Bump bootloader bypass. Everything was going well, and I remember this thread from a while back because I'm heavy on customizing my phone. Long story short, I download the "Clean Lockscreen" mod, flashed it, and now I get a "unfortunately the process com.android.systemui has stopped" when I boot up my phone. Skips the lockscreen, the home pages load up normally, but the only thing I can interact with is the Power Menu and the "Ok" to dismiss the "unfortunately..." message.
(mod was directly from http://forum.xda-developers.com/lg-g3/themes-apps/theme-g3-clean-look-kk-4-4-2-t2834442)
Short of factory resetting, is there any quick dirty fix that will let me stop having a panic attack? I'm so lazy/dumb for not having a backup, but I was so eager to start flashing things I couldn't be bothered to set one up. I gambled and lost. Hard.
Also, is there anyway to extract my photos before, worst case scenario, I do have to factory reset? I have so many pictures since I bought this phone that losing them all because of this little mistake is what's driving me crazy, on top of losing every little tweak I did here and there for the past few months.
Lastly, if I do factory reset, does that also erase everything on my SD card? The Quick Circle case is on there pretty snug.
**My theory is that someone with a Verizon LG G3 V10B (didn't update because I was afraid to lose root) has the original file that whatever the "Clean Lockscreen mod" file replaced, and I can just flash that and be sane again** please please please
TL;DR --> Verizon user, got Bump, got excited, started flashing things with no backup (dumb dumb dumb), going crazy, now hoping that I can replace that one thing I flashed with the stock original and be fine (whatever the Clean Lockscreen mod changed)
BE VERY CAREFUL READING THIS POST, IF YOU FOLLOW MY SUGGESTIONS AND LOSE YOUR PICTURES FOR ANY REASON I AM NOT RESPONSABLE.
~ You shoulda done a backup.
Just booting into recovery is 90% of the work needed to do a backup, The other 10% of the work is just clicking "backup" and waiting 15 seconds. (You were just lazy/impatient, Not dumb.)
~ Did you flash a mod that was specifically for your exact model?
~ Can you still get into your custom recovery?
~ Before you try anything in my list I would first see if you can locate the stock lockscreen files on the internet for your model and flash them back onto your phone.
~ The FC issues you're having is usually related to not having the proper permissions.
If you can still go into recovery, Boot into recovery and wipe the Cache, Dalvik cache, & go to advanced and click fix permissions.
~ It looks like to me that your launcher may be pooched.
(In my experience the lockscreen/keyguard seems to be tied to the actual launcher/UI itself, Which is why I believe your UI is broken)
Because you can't install a new launcher in the operating system I would try and find a flashable .zip version of another launcher, like nova launcher or something and flash that in recovery.
~ I'm 99% sure a Factory reset won't help your situation.
I'm almost positive you're gonna have to re-flash your firmware to return your phone to working condition.
~ Try a dirty flash, Using same type of rom. (YOU "COULD" LOSE YOUR PICTURES DOING THIS, BUT PROBLY WON'T, Use as one of your last resorts)
Try and find a flashable .zip rom that is flashable in recovery, One that is the same type as your current rom and try a dirty flash "without" wiping anything.
Only flash using the recovery without wiping "OR YOU WILL LOSE ALL YOUR PICS", Also if you flash using your PC it WILL DELETE EVERYTHING.
(If your current rom is stock or stock based rom, Find a stock/stock based .zip based rom and dirty flash in custom recovery)
(If your current rom is AOSP based rom, Find a AOSP based .zip based rom and dirty flash in custom recovery)
After you dirty flash, Backup your pictures & anything else you may need then do a clean flash.
~ There are apps that can recover "deleted/inaccessible" data. (THIS IS ABSOLUTLY LAST RESORT, DON'T TRY THIS UNTIL YOU HAVE ABSOLUTLY NO OTHER OPTION.)
When you delete something off a storage device, It doesn't delete the actual data, It deletes the operating systems directories where the said info is stored, Resulting in what looks like to the operating system as "empty space" Which it actually isn't.
If you "have to" wipe your phone before being able to recover your pictures, Avoid installing ANYTHING you can (If/when possible) until you recover your pictures if you have to wipe your phone, Because anything that goes on your phone while your stuff is deleted CAN be overwritten. (You're gonna have to google a bit to find what apps are capable of this on android.)

Can I safely run the OTA update (4.1.1 to 4.1.6) and maintain data/settings?

This has been my biggest problem with my OP3 and OOS. I want to be able to safely dirty flash my rom without losing data.
Im a long time Android power user. CyanogenMod would always be a nice easy upgrade to the latest version. Dirty unicorns, albeit buggy on my Oppo Find 7, would upgrade easily.
The last time I tried an OTA update, it trashed all my data and settings. Subsequent updates have been major upgrades (updating kernels. Major changes like OOS 3.X to 4.X. etc etc), so I haven't tried doing a OTA/Dirty flash in a while. I have been cautious since the data wipe last time.
Any advice on how I can do an OTA easily and safely?
I have TWRP. I'm UNrooted and on OOS 4.1.1.
Backup everything.. Wipe system flash 4.1.1 and it should be fine, if not restore your back up. System does not contain any data nor settings.
Ok. Will it work with the 4.1.6 OTA I got? Or should I download the full room from the website
You have to download the full zip if you have TWRP installed. You can't update via ota.
I would recommend a TWRP backup and system, cache/dalvic wipe too.
Gucci! Thanks fam
ssjaken said:
Gucci! Thanks fam
Click to expand...
Click to collapse
Well, you know, I had the same issue with my wife's 3T. Was terrible (and lucky), right out of the box, try to upgrade like you want to do, and the update would fail in the middle, requiring to wipe the phone to have it boot.
Luckily, as I said, the phone was new like 5 minutes old. I don't imagine what would happen after a few months use.
What I did to make it work was to use the stock recovery to flash the full rom zip from OP servers, and that worked.
All subsequent updates went well (with a little bit of stress we all know : will it boot, won't it? and if it does not, will I keep my head?)
Haha. Of course, you must be on stock recovery to do so, but it's easy to do, just follow the official way to do it "manually".
Oh, and backup all your stuff

Android Q beta2 Rollback

Hi all
Does anyone know the best way to roll back from updating to AndroidQ?
I have issues (android auto, casting etc) so would like to roll back to the lastest stable release
I am having a right pain restoring to to anything at the moment
Thanks
nick w said:
Hi all
Does anyone know the best way to roll back from updating to AndroidQ?
I have issues (android auto, casting etc) so would like to roll back to the lastest stable release
I am having a right pain restoring to to anything at the moment
Thanks
Click to expand...
Click to collapse
Yeah you can either use the "flash-all.bat" file that comes in the android p stock image zip or fastboot boot twrp.img and once booted into twrp just restore a backup. But you'll need to create a folder on you sdcard called TWRP. Then put a backup in it. I've even booted twrp then flashed pixel dust. It's not as critical as it was years ago when once you went up bootloader then downgraded which would cause bricking. At least I haven't run into any issues. Just make sure you turn off any lock screens and have "USB debugging" enabled.
If you are enrolled in the beta, just opt out on the website where you opted in. You'll get an OTA, which will wipe your device, so back up first. Just did this last night. Couldn't have gone any more smoothly.
For some odd reason when I rolled back my battery refuses to charge up to 100% any one else having this issue?
You have to have your phone unlocked... Yes, you will lose everything from internal memory, but can restore all your apps and settings.
I made this path twice, on beta 1 and now on beta 2.
First, make sure you have twrp. Back up on twrp everything but you will need only the data partition. Also don't forget to backup your internal memory (different from the data partition).
After that, just flash normally the last factory image from Pie, or at least the same version that you have on your nandroid backup.
After finish the installation, install again twrp. Go into twrp and restore ONLY the data partition!!! You can also restore the boot if you like (if you had magisk installed for instance). This worked flawless with me.
I repeat, no use if you try to restore ALL partitions on twrp!! At least with me, twrp would just reboot in the middle of restoring the system partition (no idea why that happened on beta 1 and now on 2). Second, the same if you try to flash factory image without the -w (without wiping internal memory), it just reboot every time it tries to enter android.
reno218 said:
For some odd reason when I rolled back my battery refuses to charge up to 100% any one else having this issue?
Click to expand...
Click to collapse
This is a bug that was fixed in Q. You can alternatively fix it in pie by flashing a kernel that has Q patches merged in.

Categories

Resources