Is anyone else finding that the factory data reset (from Settings -> Backup and reset) isn't fully wiping the phone when they use it?
I've been jumping between the international and China only ROMs so trying to wipe properly in between rather than actually wanting my data to follow me. When I use the factory reset option then switch ROM using the "Local update" method there seems to be odd bits of data left over that shouldn't have any way to be there - for example I've just moved from B115 over to B111 and after the install process completed, my wallpaper from the previous setup on B115 was still present on the main screen for B111.
Is there a difference between using the Local Update and forcing a recovery with power + - in terms of what gets wiped? I'm used to doing a full wipe in TWRP on other phones before switching ROMs so finding it a bit strange to still see apps present etc after a ROM switch.
Related
Hey just wondering what process I go through to install FoxHound 1.1 Black Ed. 4.0.4.
I would like to keep all data on my phone if possible?
I am running 4.0.2 Android revolution HD2.1.2 GSM.
I believe it's running James Bond kernel 3.0.8-Gaaa2611 dirty [email protected]
base band 9250SCOLd.
Did all this side a while ago and just hoping someone could give me the run down on changing to this ROM?
Do I need to completely reset my phone to stock and start again or can I just install this ROM over and keep all my contacts, photos and settings?
If you're changing ROM a full wipe is in 99% necessary. For the 1% just do it to be sure.
To keep the data I recommend that you're using Titanium Backup. It's the best app for keeping
your data backed up.
But don't back up any system apps. Just your personal apps otherwise you could run into problems.
Contacts and calender data aren't a problem if you stored them in the Google Cloud.
The pictures shouldn't be affected but make a back up just in case.
BTW.
If you're changing ROM always perform a full wipe/ factory reset in the recovery. You can avoid many problems if you're doing so.
If you're upgrading your ROM wiping cache and dalvik should be okay. But always follow the devs instruction if he says otherwise.
google services
Hi
I just bought my htc from second hand. It already had viperone (kitkat sense 6) but im not able to connect with google services. Just can't connect, it says: "There was a problem communicating with Google servers.
Try again later". I'm using wifi, coz at the moment i don't have that micro micro sim(whatever). Phone is from UK, but i live in Poland. I just returned settings, wiped dalvik cache and it didn't help. Should i do factory reset and flash latest version of rom?
And there is one thing, bottom speaker doesn't work. But i heard that's software bug so if i understand good, it would dissapear with new rom, would it?
Try flashing a rom. Since you just got it hopefully any personal data you can't restore it isn't of much value. If you attempt a custom recovery factory reset (twrp) use the format data option that has you type YES before it formats it.... Some google apks are kept when you use that option. If you simply wipe the data partition it will remove and essential google apks that might prevent you from using their services entirely.
If you plan on using any rom based on a newer version of android remeber to get your hands on a recent firmware.zip from xda that has the updated hboot, radio, rcdata etc still in it. If you don't youll run into all kinds of issues trying to use a lollipop rom with a phone still thinking its on kitkat.
Thanks, i just did factory reset, wiped every possible data and flashed latest kitkat viperone, everything is working without problem now. Except speaker, bottom one is very quiet, probably hardware issue, blown speaker or smth - grill is clean, so i need to speak with guy about return. Thanks anyway. ; )
Hi everyone,
Looking for a solution to my stock, unrooted M8. Carrier - EE.
Android 6.0/Sense 7.0. Software 6.12.61.4
Have had the phone nearly two years so undertook a factory reset to clear it out. Initiated factory reset through settings in the normal UI.
Factory reset completed. Got the welcome screen etc. However, no nav bar, no status bar (with clock, battery at top), and no notification pull-down. Black screen (no default wallpaper), but all standard apps present.
Attempted factory reset again from bootloader. This time, as soon as it booted to the home screen, I got the error com.android.systemui has stopped unexpectedly. Regardless of whether I pressed "send" or "don't send" error report to HTC, the error message disappears and it begins to flash between a black screen and the default sense 7.0 wallpaper - but no sign of apps, icons, etc. The power button is responsive and displays the power off/restart options.
Reset a third time from stock recovery menu. Same result. Have also tried clearing cache, etc.
Weirdly, it optimises what I take to be a number of default apps each time during the factory reset - don't know if that's normal or not.
I'm assuming that my copy of the OS in the recovery partition has got buggered up somehow. But I'm new to this whole flashing/rooting business and most of the guides I've found seem to presuppose that I'm trying to get back to stock from having rooted my phone and installed something else, and I don't really understand them.
So -
1. any ideas about what's happened/how to fix it? I've spoken with HTC but they want me to send it in. 2-3 weeks!
2. assuming that I just need to reinstall a clean version of the software, how do I go about doing that? How do I know what the right version is, and where do I get it? Can I reinstall it without rooting the phone and installing a custom bootloader?
I did have a hunt through previous threads. The closest I found was this one http://forum.xda-developers.com/htc-one-m8/help/ui-htc-one-m8-t3024485 but it still leaves me uncertain about how to find the right software and actually install it.
Thanks very much in advance.
Michael
Okay, solved - somehow.
Formatted and removed SD card, just in case. Factory reset again, no joy.
Then also removed sim card, and factory reset again from stock recovery. This time performed cache wipe immediately before factory reset - whereas before I'd wiped cache, restarted, confirmed error still present, then factory reset as a second step.
Systemui and nav/status/pull-down bars all present as normal this time.
I find it hard to believe that the presence of the sim card could have made a difference, so I assume that the cache wipe and then immediate restart did the job.
Anyway, resolved now. Happy days.
I recently rooted and flashed a recovery on my M8.
I was experimenting with the Fake GPS Free app, and mock locations. Worked great.
But when I turned it off (developer settings, mock location-->None), Actual GPS doesn't work right.
Turned it off, removed mock location setting, deleted app, re-installed app, made sure it was turned off, deleted again.
'High Accuracy' sorta works. It gives an approx position. But using something like google maps navigation gives the message 'Searching for GPS...' and never finds it.
I tried a couple of apps 'GPS Status' and 'GPS Reset Com' which reset A-GPS, but it hasn't worked.
'Device Only' fails completely.
Tried clearing cache.
I even flashed a new ROM (Android Revolution HD (6.0)) but no luck.
I do have a factory reset option - but I'd rather avoid it if possible.
Anyone have any ideas of what else I can try?
Restore the nandroid backup you made (you made one right?) before flashing a new ROM or playing with apps from /system
I actually did not make one. I've just been reading up what it is and what I should have done and now I feel a bit silly.
When it said 'backup your phone' I thought it was just the contents (messages, data, media, etc).
Oops!
It's still all a bit new to me..
Anything else I can try?
Backup your data and sdcard content then flash appropriate RUU, if it's not gonna work it's probably an hardware issue.
I have exactly the same problem with my M8. I tried exactly the same steps and still have the GPS issue. I also restored a previously made backup and did a clean flash of CM13... this couldn't solve the problem.
It can't be a hardware issue
UPDATE: I don't know if it would have worked before, but after reflashing I placed my phone on the ground outside, started GPS Status & Toolbox and waited for a GPS signal. after ~1 minute GPS signal was found and it works fine since then. Maybe I was just too impatient before.
jamesb457 said:
Tried clearing cache.
I even flashed a new ROM (Android Revolution HD (6.0)) but no luck.
I do have a factory reset option - but I'd rather avoid it if possible.
Click to expand...
Click to collapse
Looks like you are new to the modding world. But if you are modding the phone (root, custom ROMs), you should always be prepared to recover from a factory reset (have your data backed up).
And if fact, if you are flashing ROMs without doing a factory reset (within TWRP) you are inviting all sorts of random bugs. In other words, the default wipe in TWRP (data, cache, Dalvik) is always recommended when flashing a new ROM.
Ever since updating to A10 on my OnePlus 5t, I can no longer access the "SIM & network" menu within "Wi-Fi & internet". Each time I do, it loads a white page briefly with com.android.phone.oneplusOPMSimActivity as text across the top before kicking back to the previous page. If I try more than once, then the popup for "com.android.phone keeps stopping" comes up with the options for "App info" or "Close app". Each time I try to open this menu, the cell network drops and then reconnects. All of the other options in the "Wi-Fi & internet" menu work as expected.
Yesterday is when I started this whole process. I initially had my phone on the OOS version from late December 2019 (I don't recall the exact version number) with TWRP 3.3.1-0 for recovery and Magisk 20.4. I went into recovery, flashed the A10 OTA full zip, flashed the TWRP 3.3.1-x blu_spark v9.110 recovery, flashed Magisk 20.4, then booted like normal but had no cell connectivity at all (no baseband, IMEI was unknown, etc). After a lot of troubleshooting and reflashing several times, it turns out the one Magisk module that I had installed was not compatible as once I removed it and rebooted, the cell connectivity worked fine.
Fast forward to today and I noticed that I could not access the "SIM & network" menu. I have tried reflashing everything again; removing Magisk and leaving TWRP; going back to full stock without root; booting into safe mode; flashing back to TWRP, wiping Dalvik / ART cache, Cache, and System, then flashing OTA, Magisk, and blu_spark kernel 199; booting into TWRP and wiping Dalvik / ART Cache, Cache, and System, then flashing the OTA without TRWP or Magisk; etc. I could not access the "SIM & network" menu without the app crash at any point, even in safe mode on the factory ROM without root or custom recovery. I also tried clearing the cache and data for com.android.phone, SIM Toolkit, and Phone without any change.
I have not yet tried to take my device completely back to factory state yet (wipe all partitions and start from scratch) as that will take an eternity to restore from. If I have to I will, but I will try every option available to me before I do.
I did a logcat through adb and reproduced the problem. I'm not an Android dev so the logs are of questionable use to me but may point me to something to look at.
Any thoughts on what I should do? Is this something having to do with the previous recovery or root? Is this something caused by existing files on my phone? Is this something broken in the factory OTA and I need to contact OnePlus? The phone is functional otherwise, but man it is annoying not being able to access this menu.
Have you tried wiping data while on "full stock" state? (you will not lose /sdcard)
If that doesn't work, I would suggest that you use Unbrick tool 9.0.11 (which wipes everything including /sdcard) and OTA to OOS 10 (and reunlock).
---------- Post added at 07:32 AM ---------- Previous post was at 07:31 AM ----------
Have you tried wiping data while on "full stock" state? (you will not lose /sdcard)
If that doesn't work, I would suggest that you use Unbrick tool 9.0.11 (which wipes everything including /sdcard) and OTA to OOS 10 (and reunlock).
I had the same problem, dirty flashing the ETA from this xda post has fixed the issue for me for now: https://www.xda-developers.com/oneplus-5-5t-stable-android-10-oxygenos-10-update/
So, I hadn't messed with this for a while and just put it on the back burner. That was until I realized that I could not make calls as I would just get a bunch of chirping, garbled, chipmunk like sound which made the call useless. It worked fine if I answered a call, but not if I made one. I figured it was related to this issue so I went through the process of trying to get things working again. I tried just flashing the A10 OTA again with the blu_spark TWRP and Magisk 20.4, but that didn't fix it. I then proceeded to try and do a full backup of my phone as I was going to try the full wipe and start over fresh, but trying to backup everything is a joke through the USB2.0 connection on this phone let alone trying to get everything just in case I wanted to roll back to how the phone was working prior to the wipe.
At some point I gave up on the backup stuff and just got my user data. Then I got the idea to try going back to the previous working version of Android Pie. I don't recall what my thought process was, but it didn't end up working. For whatever reason, the 53 update was doing the same thing the 54 update did where it would boot up and immediately power off once the lock screen came up. It worked fine before with update 53, but now it wasn't so I flashed back to A10. Now, suddenly, I've noticed that I can access the "Network & SIM" section of the menu without that error from before. I don't know when or what fixed that issue, but it works every time now. Mind you, I did wipe the Dalvik/ART cache, cache, system, and vendor partitions at various points in my attempt to get things working, some of them more than once. I also played around with what partitions were mounted within TWRP though I really did not know what I was doing.
The chipmunk, chirping, garbled thing is still there, but it sounds like many people have had that issue with A10 on other phones. So luckily enough, just turning on and off speaker phone fixes the issue immediately (but I believe for just that call). That is an easy enough work around for me. As much as I want to leave my phone alone, I still have an issue where the phone always boots into recovery first and I have to select reboot > system through TWRP for the phone to boot up normally. I tried reflashing things multiple times, wiping the various partitions, and even some commands from a Nokia forum, but nothing worked. I imagine this is because I messed with the mounted partitions within TWRP and did a flash, but I am not sure on that. I think it could be that the system is booting into recovery because it thinks that is the "normal" partition with the whole A/B partition system, but again, I am not sure on that. I may post again if I end up figuring that all out.