I tried to remove amazon fire launcher with the first two commands on this thread "http://forum.xda-developers.com/amazon-fire/development/tut-remove-default-launcher-amazon-fire-t3288310" but now its buged out and i can't fix it. I can root if needed but is there a easy fix. I did try a ota update but that did not work. Also i would like to keep my data.
Reuben
Reuben Talbott said:
I tried to remove amazon fire launcher with the first two commands on this thread "http://forum.xda-developers.com/amazon-fire/development/tut-remove-default-launcher-amazon-fire-t3288310" but now its buged out and i can't fix it. I can root if needed but is there a easy fix. I did try a ota update but that did not work. Also i would like to keep my data.
Click to expand...
Click to collapse
Reload FireOS 5.3.1 (or 5.3.2 if you don't immediately care about root) from the stock recovery menu. Your apps and data will remain intact.
I tried that 5 times two days ago But it does nothing
Davey126 said:
Reload FireOS 5.3.1 (or 5.3.2 if you don't immediately care about root) from the stock recovery menu. Your apps and data will remain intact.
Click to expand...
Click to collapse
Reuben Talbott said:
I tried that 5 times two days ago But it does nothing
Click to expand...
Click to collapse
Well, once would have been sufficient.
If the problem persists:
- FireOS reloads are not occurring successfully (assume you have ruled that out)
- may have to bite the bullet and wipe the user data partition prior to reloading FireOS
- defective device (seems highly unlikely...)
If still no joy you can root, install FlashFire and use the 'wipe' function to completely purge your device of all content. Then reload FireOS via the stock recovery menu which will yield a fresh-out-of-the-box experience. Recommend using the 'SuperTool' to root as it also installs SuperSU (and removes KingUser) which is a FlashFire prerequisite.
I don't think I have a defective device I have had it sense July and its worked well until I Dido those commands
Davey126 said:
Well, once would have been sufficient.
If the problem persists:
- FireOS reloads are not occurring successfully (assume you have ruled that out)
- may have to bite the bullet and wipe the user data partition prior to reloading FireOS
- defective device (seems highly unlikely...)
If still no joy you can root, install FlashFire and use the 'wipe' function to completely purge your device of all content. Then reload FireOS via the stock recovery menu which will yield a fresh-out-of-the-box experience. Recommend using the 'SuperTool' to root as it also installs SuperSU (and removes KingUser) which is a FlashFire prerequisite.
Click to expand...
Click to collapse
Do you think i could wipe only the system partition and keep my data?
Reuben Talbott said:
I don't think I have a defective device I have had it sense July and its worked well until I Dido those commands
Click to expand...
Click to collapse
Reuben Talbott said:
Do you think i could wipe only the system partition and keep my data?
Click to expand...
Click to collapse
Can't hurt to try. Be aware that once you wipe the system partition the device will no longer boot into FireOS. If necessary you will need to power down the device (long press power button) and then boot into stock recovery using <power>+<vol-up>. Also note that while well considered/executed wipes are generally safe there is always the chance something could go wrong leaving you with an unbootable brick. Rather rare but would be irresponsible not to point out possibility since you seem to have some valuable data on the device. Might want to copy that to the SD card in advance (if possible).
Davey126 said:
Can't hurt to try. Be aware that once you wipe the system partition the device will no longer boot into FireOS. If necessary you will need to power down the device (long press power button) and then boot into stock recovery using <power>+<vol-up>. Also note that while well considered/executed wipes are generally safe there is always the chance something could go wrong leaving you with an unbootable brick. Rather rare but would be irresponsible not to point out possibility since you seem to have some valuable data on the device. Might want to copy that to the SD card in advance (if possible).
Click to expand...
Click to collapse
That is what is what I was thinking of doing.
Does any one know were app data is stored?
Reuben Talbott said:
Does any one know were app data is stored?
Click to expand...
Click to collapse
Many places. There are guidelines but somedevelopers opt to ignore. You'll need to do some searching and hope that you find everything. Could also try Android's native app backup/restore commands which operate via adb (USB tether). Do some goggling for syntax.
Related
I have installed Avast AntiTheft today on my Nexus6 and after Simulation test I can't access my phone.
It says to enter PIN to access Android Device.
Any of my PINs are not working.
I'm unlocked, rooted with TWRP.
What can I do to access my device?
I have installed CM12 today so I have no problem with loosing any data if wipe is the only solutions.
But I'm not sure if I can do this.
Surely you'll have some sort of admin panel on an avast website where you set a pin.
rootSU said:
Surely you'll have some sort of admin panel on an avast website where you set a pin.
Click to expand...
Click to collapse
I've already done that. Didn't help.
maturb said:
I've already done that. Didn't help.
Click to expand...
Click to collapse
Contact Avast and I'm sure they can help then.
rootSU said:
Contact Avast and I'm sure they can help then.
Click to expand...
Click to collapse
I've already done this but no help at the moment.
Other people have same problem.
I can't also find anything about wiping encrypted phone.
maturb said:
I've already done this but no help at the moment.
Other people have same problem.
I can't also find anything about wiping encrypted phone.
Click to expand...
Click to collapse
Its the same as wiping an unencrypted phone.
There are changes in 5.1 though
rootSU said:
Its the same as wiping an unencrypted phone.
There are changes in 5.1 though
Click to expand...
Click to collapse
You mean I can do the Factory Reset in TWRP and then re-install CM12?
maturb said:
You mean I can do the Factory Reset in TWRP and then re-install CM12?
Click to expand...
Click to collapse
You can factory reset via twrp.
Not sure why you'd need to reflash the ROM though.
rootSU said:
You can factory reset via twrp.
Not sure why you'd need to reflash the ROM though.
Click to expand...
Click to collapse
TWRP can't mount DATA without password (i've never set this password) So how can I wipe it?
maturb said:
TWRP can't mount DATA without password (i've never set this password) So how can I wipe it?
Click to expand...
Click to collapse
If you've not set a pin/pattern in android, use the default twrp one which I imagine is in the twrp thread somewhere. If you have set an android pin/pattern, use that.
rootSU said:
If you've not set a pin/pattern in android, use the default twrp one which I imagine is in the twrp thread somewhere. If you have set an android pin/pattern, use that.
Click to expand...
Click to collapse
I did flash stock image.
Any of these solutions you wrote or I found on xda didn't help.
Anyway thank you for your time.
Regardless, you're still going to need to learn how to use twrp properly. Unless you're planning in staying stock.
rootSU said:
Regardless, you're still going to need to learn how to use twrp properly. Unless you're planning in staying stock.
Click to expand...
Click to collapse
I'm learning sth new every day. Every problem I have is a new lesson.
Maybe I'm not so good at the moment but trying to be better...
maturb said:
I'm learning sth new every day. Every problem I have is a new lesson.
Maybe I'm not so good at the moment but trying to be better...
Click to expand...
Click to collapse
You'll get there.
maturb said:
TWRP can't mount DATA without password (i've never set this password) So how can I wipe it?
Click to expand...
Click to collapse
Better to use FACTORY recovery for this. TWRP doesn't just "wipe" the userdata partition, it wants to do a selective clear of it.
Basically, there is a directory in the userdata partition called "media" that it tries to regard as a separate device.
The problem is in the backup functions implemented on custom recoveries. They create a backup of the userdata partition to the absolute STUPIDEST place in the entire world -- the userdata partition ITSELF.
So they have a hack separation, they leave out the media subdirectory from the backup source, and set the backup target to within that directory, then instead of performing a proper mkfs on the partition to clear it, they mount the partition (requires the pass code) and *erase* everything besides the media subdirectory.
Pretty stupid, isn't it?
** THE ONLY SANE PLACE TO BACK DATA UP TO, IS A SEPARATE DEVICE. Or in the very least, a different PARTITION.
Alternative is to clear the userdata partition with fastboot. Boot into bootloader/fastboot, and type (on your computer with the fastboot binary installed) "fastboot format userdata".
As far as the password goes, did you ever set a lockscreen security code? Maybe a pattern or pin unlock? That is what it is asking for. Its possible that the program you installed forced that down your throat with some random junk.
FYI: Google has this feature built in already, there is no need to install potentially dangerous 3rd party software. You can enable it in the program "google settings" --> security, under "android device manager". You can then go here https://www.google.com/android/devicemanager and log in with your google account to locate, lock, erase, ring, etc.
I have rooted my phone, but am not doing any custom ROMS or anything. I notice that I have an OTA update, and figure that it may be in my best interest to install it, and it would stop nagging me then too. I know if i un-root, I will loose everything. I use Titanium backup. So if I do a full backup, un-root, install update(s), re-root, I can re-install Titanium (I have the paid version) and recover everything right where I left off correct?
I am assuming that you unlocked the bootloader even though you are just rooting. That is how I roll. If so it would be far easier to download the latest image for your phone and flash it. Just skip flashing the user partition. That will save your apps, data and settings.
It is a 10 minute process and far less prone to errors. TI backups are great but can create lots of little gremlins when you restore them.
And with root there are so many other things you could have changed that might cause the update to fail that it just isn't worth the effort.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
I am assuming that you unlocked the bootloader even though you are just rooting. That is how I roll. If so it would be far easier to download the latest image for your phone and flash it. Just skip flashing the user partition. That will save your apps, data and settings.
It is a 10 minute process and far less prone to errors. TI backups are great but can create lots of little gremlins when you restore them.
And with root there are so many other things you could have changed that might cause the update to fail that it just isn't worth the effort.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Awesome! Good to know. I know how to use the search function, but what should I search for to find how to do what you've recommended?
Thanks again
therealcrazy8 said:
Awesome! Good to know. I know how to use the search function, but what should I search for to find how to do what you've recommended?
Thanks again
Click to expand...
Click to collapse
Googling "nexus factory images" will get you where you need to go. But also I'd like to add that on the SuperSU forums there are posts about using the SuperSU app's built in "full unroot" feature with systemless root allows usage of ota's. It works by just restoring a backup of your boot image that the SuperSU.zip takes before rooting with the new systemless root method. The caveat to this is that when you install the zip via TWRP you need to select the "Leave /system read-only" option upon first install and also not mount /system as R/W at any time during your usage of root.
The way I've personally been doing ota's lately is just taking a "system-image" backup in TWRP before modding anything that way when the ota rolls around I just restore the backup, apply the ota update the backup reflash twrp and root. Doesn't really save any time versus using a factory image but 10mb ota vs 2gb image is easier for me with crummy data limited internets
StykerB said:
...The way I've personally been doing ota's lately is just taking a "system-image" backup in TWRP before modding anything that way when the ota rolls around I just restore the backup, apply the ota update the backup reflash twrp and root. Doesn't really save any time versus using a factory image but 10mb ota vs 2gb image is easier for me with crummy data limited internets
Click to expand...
Click to collapse
Interesting. As a rooted user though, why is flashing the entire (new) factory image an option, rather than just cherry-picking the files that you need (i.e boot.img, radio etc if altered)? I mean, I realize that you still have to download the whole image, but there are far fewer steps involved to getting a revised security update on your device than with resurrecting a stock Nandroid, applying the OTA, and then rooting again.
therealcrazy8 said:
Awesome! Good to know. I know how to use the search function, but what should I search for to find how to do what you've recommended?
Thanks again
Click to expand...
Click to collapse
At the top this sub forum is an FAQ that will get you going. Also in the development forum is a thread for Wugfresh NRT toolkit. It will do everything you need.
The option you are looking for in that is the 'no wipe' option to save your data.
But you should do it manually first, so you understand what is what if something goes wrong. And you should TI backup just in case.
If it bootloops or freaks out don't panic. It is fixable, as long as the bootloader is unlocked.
Sent from my Nexus 6 using XDA Labs
Not_A_Dev said:
Interesting. As a rooted user though, why is flashing the entire (new) factory image an option, rather than just cherry-picking the files that you need (i.e boot.img, radio etc if altered)? I mean, I realize that you still have to download the whole image, but there are far fewer steps involved to getting a revised security update on your device than with resurrecting a stock Nandroid, applying the OTA, and then rooting again.
Click to expand...
Click to collapse
It's only restoring the /system so data and apps remain but the main goal of mine is just saving data by not having to downloading a factory image. Regardless of how you do it you still have a PC in the mix at some point so I might as well save some of my data plan.
Hi,
I have a Nexus 6 with a shattered screen, and just bought another one to replace it (exact same model, XT1103 32GB).
I want to make a Nandroid dump of the old device by booting into TWRP temporarily, then restoring the backup to the new phone using the same method. Both phones are bootloader unlocked and totally stock (latest Android update).
Is there anything in particular that I should watch out for? Which partitions should I not touch - a friend on another forum suggested that I should not touch EFS?
Cheers,
Su
If you restore the efs from one to the other you'll loose your imei number on the second one
needleyepoke
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
I've cloned a Nexus 5 but I'm not sure if it's the same way.... P.S. of course your not supposed to do it unless you own both phones... From what I've been told
needleyepoke
Hi,
I don't want to mess about with the IMEI etc - I just want the same system settings, apps etc.
What partitions should I backup/restore? I guess just System, Data, Cache, Boot & Recovery should be enough?
Thanks,
Su
[edit] This seems to suggest just System, Data and Boot is ok - but is that all I need if I am restoring to another device?
Sumanji said:
Hi,
I don't want to mess about with the IMEI etc - I just want the same system settings, apps etc.
What partitions should I backup/restore? I guess just System, Data, Cache, Boot & Recovery should be enough?
Thanks,
Su
[edit] This seems to suggest just System, Data and Boot is ok - but is that all I need if I am restoring to another device?
Click to expand...
Click to collapse
Yes if they're on the same version. I cloned a 32 into a 64.
Ok I just tried this now, and it is not working...
The restore to the new device worked fine, but when I power up I get the "your device is corrupt screen" (which I think is normal if you use TWRP), but then after that it's just a blank screen...
The phone is still able to boot into bootloader and recovery (stock).
Any ideas what could have gone wrong please?
Thanks,
Suman
I think this might be something to do with encryption... when booting into TWRP the new phone still requires the encryption pin I set up from its original software....
Do I need to start again?
Ok, I flashed the new phone with the factory image and started again... this time, when I restore the backup it just hangs on the white Google logo screen...
Any help appreciated please!
Thanks,
Su
If your firs N6 was encrpted (default) there's no way to clone it. Android will generate different encryption keys etc.
Secure lockscreen is a big no-no too. With it, you can't even properly restore backup on the same device!
Trying to take the lazy way out is just asking for trouble. There are many things that can go wrong.
Also just a side note. Cloning devices is illegal, even if you own both devices. The was set by the cell phone cloning laws set up by the FCC.
Your best bet is just to reset it up from scratch.
zelendel said:
Trying to take the lazy way out is just asking for trouble. There are many things that can go wrong.
Also just a side note. Cloning devices is illegal, even if you own both devices. The was set by the cell phone cloning laws set up by the FCC.
Your best bet is just to reset it up from scratch.
Click to expand...
Click to collapse
Oh well,
I'm remembering what I did and I did not restore the Nandroid from Device A to Device B, I titanium Backup'd all the apps and moved them to TitaniumBackup folder on the new phone, restored from there.
For /sdcard/ I had to copy and paste it from one phone to the other...
I'm going to reply this to your reddit thread also.
Lawstorant said:
If your firs N6 was encrpted (default) there's no way to clone it. Android will generate different encryption keys etc.
Secure lockscreen is a big no-no too. With it, you can't even properly restore backup on the same device!
Click to expand...
Click to collapse
Ah dang, so there is no way for me to do what I want then... that's annoying, I would have bought a different phone in that case!
I believe Google requires encryption to be active in all devices with Android 6.0.1 installed, so any new device you purchase will have this (non-) issue.
Think of the alternative however. You could always be dealing with Samsung and Knox.
Strephon Alkhalikoi said:
I believe Google requires encryption to be active in all devices with Android 6.0.1 installed, so any new device you purchase will have this (non-) issue.
Think of the alternative however. You could always be dealing with Samsung and Knox.
Click to expand...
Click to collapse
I believe that is correct. All Nexus devices going forward will have the kernel force encryption. The only way around it is to format data in TWRP (completely wipe the phone) and then when you re setup your ROM (or even the stock image) just make sure you flash a custom kernel that doesn't force encryption (which pretty much all custom kernels don't) before booting into OS for the first time. I run mine unencrypted because nandroid backups are wayyyyy quicker without encryption. I know the security isn't as good but not a deal breaker for me.
I asked this question a while back when I was in the same situation, and was told that it's a bad idea.
TriguyRN said:
I asked this question a while back when I was in the same situation, and was told that it's a bad idea.
Click to expand...
Click to collapse
It is a bad idea. Restoring any system files from one device to another is a risky game. I wouldn't even recommend restoring data from one device to another.
Start fresh, clean. No need to bring junk over, or risk issues. Takes 15 minutes to setup a phone how I like it after a clean rom flash. That's not a long time.
Last year I returned my N6 because of the peeling-back problem. I had a full TWRP backup on my laptop. I loaded it on to the replacement N6, renamed the backup folder to the new device id, and restored it. Worked perfectly, no problems.
I have a Fire 7" that is mysteriously failing when trying to flash with FlashFire. My process is:
- Downgrade FireOS
- Root using KingRoot
- Install SuperSU
- Install FlashFire
I've been restoring a backup of a Fire tablet that is set up how I need to. This process has worked on several other Fire 7 tablets recently, and in general I've been able to do this on about 50 tablets. On this particular tablet, I tried flashing the restore image twice with FlashFire 0.50, once with 0.51, and then the last time I decided to directly flash the CM 12.1 and GApps instead of restoring.
Every time, FlashFire appears to quite somewhere in the middle of flashing and I get stuck in a boot loop. I can sideload the downgraded FireOS to get it running again.
So, I was curious if anyone had any ideas as to how to approach this? Hopefully this is the last of these damn things I need to do this with.
Radixdiaboli said:
I have a Fire 7" that is mysteriously failing when trying to flash with FlashFire. My process is:
- Downgrade FireOS
- Root using KingRoot
- Install SuperSU
- Install FlashFire
I've been restoring a backup of a Fire tablet that is set up how I need to. This process has worked on several other Fire 7 tablets recently, and in general I've been able to do this on about 50 tablets. On this particular tablet, I tried flashing the restore image twice with FlashFire 0.50, once with 0.51, and then the last time I decided to directly flash the CM 12.1 and GApps instead of restoring.
Every time, FlashFire appears to quite somewhere in the middle of flashing and I get stuck in a boot loop. I can sideload the downgraded FireOS to get it running again.
So, I was curious if anyone had any ideas as to how to approach this? Hopefully this is the last of these damn things I need to do this with.
Click to expand...
Click to collapse
In your shoes (and given your experience) I might try a stand alone, full-on wipe with FlashFire which, with any luck, will yield an 'empty', unbootable device. You can then reload FireOS via recovery menu and do the prep-for-custom-rom dance again. If FlashFire behaves the same way you might want to cut your losses and request an exchange from Amazon.
Davey126 said:
In your shoes (and given your experience) I might try a stand alone, full-on wipe with FlashFire which, with any luck, will yield an 'empty', unbootable device. You can then reload FireOS via recovery menu and do the prep-for-custom-rom dance again. If FlashFire behaves the same way you might want to cut your losses and request an exchange from Amazon.
Click to expand...
Click to collapse
Word, I'll give that a shot. This one is already an exchange (last batch had a lot of stuck pixels), not sure I have the mettle to go through all that again.
Davey126 said:
In your shoes (and given your experience) I might try a stand alone, full-on wipe with FlashFire which, with any luck, will yield an 'empty', unbootable device. You can then reload FireOS via recovery menu and do the prep-for-custom-rom dance again. If FlashFire behaves the same way you might want to cut your losses and request an exchange from Amazon.
Click to expand...
Click to collapse
Curious; doing a wipe (all boxes checked) with FlashFire 0.51 seems to just result in a factory reset. Blah.
Radixdiaboli said:
Curious; doing a wipe (all boxes checked) with FlashFire 0.51 seems to just result in a factory reset. Blah.
Click to expand...
Click to collapse
Suggests the system partition is not writable in the manner FlashFire uses which points to a larger issue such as an underlying permission issue. Not sure how to further diagnose/remediate.
Couple of quick (probably stupid) questions about wiping and rebuilding the phone:
I haven't done a "flash-all.bat" in quite a few iterations of Android updates. I keep hearing from different people how smooth and how fast and bug free their phone is after doing a "Flash-all.bat" on it.
Is this true or do you all think it's just a placebo effect?
I've already done a Titanium Backup of my apps. Do you all recommend doing it that way or, re-installing the apps and re-set everything up from the Play Store all over again?
I've backed up my "userdata" folder to my PC. Is there a way, after wiping the phone to completely erase the SD card and/or check for errors? Or, not necessary?
I've seen some discussion that people are no longer using Chainfire's SU any more and have moved on to something else (the other SU name escapes me at the moment)?
An unlocked Bootloader now trips SafetyNet? So there is no real reason to try and install "SUHide" and the like in order to get Android Pay working? I've not messed around
with trying to bypass the SafetyNet and just resigned myself to never being able to use A.P. Should I even mess with all of that?
Anything else you all might recommend on a "restart" of a device, I'd be eager to hear!
Thanks all!
1. FlashAll is way too drastic. It deletes every single file you had on your emmc. Doing factory reset from TWRP only deletes the apps and settings and leaves all your photos, documents, downloads, etc.
2. I let Google install my apps after a new setup and then let TB restore the data for those that Google couldn't. Since MM even Google manages to restore some data too.
3. Unless you want to sell it, there's no need to wipe it completely.
4. PHH's superuser is completely open source and more and more people use it.
5. Yep, you need a custom kernel for SafetyNet if your bootloader is open. There is one already for 7.0 too
Sent from my Nexus 6P running Nougat DP 7.1 using Tapatalk
istperson said:
1. FlashAll is way too drastic. It deletes every single file you had on your emmc. Doing factory reset from TWRP only deletes the apps and settings and leaves all your photos, documents, downloads, etc.
2. I let Google install my apps after a new setup and then let TB restore the data for those that Google couldn't. Since MM even Google manages to restore some data too.
3. Unless you want to sell it, there's no need to wipe it completely.
4. PHH's superuser is completely open source and more and more people use it.
5. Yep, you need a custom kernel for SafetyNet if your bootloader is open. There is one already for 7.0 too
Sent from my Nexus 6P running Nougat DP 7.1 using Tapatalk
Click to expand...
Click to collapse
1) Ok, so I will just do a "factory reset" in TWRP then.
2) I will have to take a look at the TB Backup, I've only done "Backup all user apps". I'll check if there is just a setting for "Data for user apps" then.
3) Ok. Point taken. Just thought wiping the internal storage might get rid of any "ghosts in the system" so to speak.
4) Thank you for refreshing my memory. Forgot the name of the other SU.
5) I'll check to see if Franco Kernel has that, or plans on implementing it. I've been using F.K. forever so hopefully he will get around to releasing one.
** Unrelated note: Your 6p, in hindsight, was it worth the upgrade from the 6? Since the new Pixels are out, I'm assuming the 6P are going to start dropping in price at this point **
Thanks again for the suggestions / help
usafle said:
** Unrelated note: Your 6p, in hindsight, was it worth the upgrade from the 6? Since the new Pixels are out, I'm assuming the 6P are going to start dropping in price at this point **
Thanks again for the suggestions / help
Click to expand...
Click to collapse
This was indeed worth it, it was a store display model activated for a couple of months, I got it for half price.
But I needed a daily device while I develop Nougat for my N6. Then switch them and develop it for the 6P.
But as a device I'm very pleased with it, it's faster, the camera is better, and the 7.1 DP is already better than the official 7.0.
Sent from my Nexus 6P running Nougat DP 7.1 using Tapatalk