Related
It gives me an error "Run 'wipe dalvik' via ADB.
Should I be able to run it from the recovery? I suspect my recovery ROM copied incorrectly. Is there any way I can reflash the ROM without doing a factory reset and re-rooting.
If not, then will doing a factory reset via Recovery work? And will the phone need to be reprogrammed to work on Sprint with my number, etc?
Thanks!
fatkitty420 said:
It gives me an error "Run 'wipe dalvik' via ADB.
Should I be able to run it from the recovery? I suspect my recovery ROM copied incorrectly. Is there any way I can reflash the ROM without doing a factory reset and re-rooting.
If not, then will doing a factory reset via Recovery work? And will the phone need to be reprogrammed to work on Sprint with my number, etc?
Thanks!
Click to expand...
Click to collapse
Go download the 1.5.2 recovery ROM, flash it the same way you did the original instructions are there. If you still have the issue, post back.
I have had simaler problems in the past and sometimes I was able to just reboot the system and use the fresh kitchen go to create nandroid backup in the kitchen it used adb to reboot into recovery and then everything worked fine after that.
on the other hand there have been a couple times where I just had to bite the bullet RUU and reroot then flash a backup.
hope this helps a little
dam KCarpenter you lurk here as much as I do. lol
wtphoto said:
dam KCarpenter you lurk here as much as I do. lol
Click to expand...
Click to collapse
HAHA Refresh every hour or so lol.
But I was reposting to say that you should try to wipe from the pre kitchen and see what happens there.
I re-pushed and flashed 1.5.2 recovery. I still get the "run wipe davilk from ADB" error when trying to wipe it from within the recovery rom.
What do you mean wipe it from pre-kitchen? Could someone please post some instructions.
Is there a command to run it via CMD?
I have never had it work.. even on multiple Heros. and MANY Recover re-loads
tyrnight said:
I have never had it work.. even on multiple Heros. and MANY Recover re-loads
Click to expand...
Click to collapse
I get force closes on any update I do. I thought clearing the cache fixes this problem?
If not can someone point me to instructions on starting from scratch? I would like to factory reset it but I need to know if I'll have to re-activate the phone to work on Sprint, or if it just works?
They are talking about on the Fresh Pre Kitchen 0.2 . Also if you do a wipe you will not have to activate the phone it will just reinstall the OS. I actually clearfed rteh cache using the pre-kitchen and it works fine now
athlet1c said:
They are talking about on the Fresh Pre Kitchen 0.2 . Also if you do a wipe you will not have to activate the phone it will just reinstall the OS. I actually clearfed rteh cache using the pre-kitchen and it works fine now
Click to expand...
Click to collapse
I see. I just factory reset my phone.
Now the question is; since I still I have my recovery ROM do I still need to root the phone again?
fatkitty420 said:
I see. I just factory reset my phone.
Now the question is; since I still I have my recovery ROM do I still need to root the phone again?
Click to expand...
Click to collapse
Oh, so I did a factory reset, re-rooted the phone, and installed Modaco's newest custom ROM.
I'm still getting force closes.
If I clear the cache will it fix the errors?
it depends if you just used the wipe data/factory reset in the recovery menue or if you actually used the RUU to reflash back to stock. if you used the RUU then yes you will have to reroot if you just used the recovery menue then no you will not have to.
wtphoto said:
it depends if you just used the wipe data/factory reset in the recovery menue or if you actually used the RUU to reflash back to stock. if you used the RUU then yes you will have to reroot if you just used the recovery menue then no you will not have to.
Click to expand...
Click to collapse
Great, I think I have this figured out now.
I went ahead and used Fresh's pre-Kicthen. It seems to be working great now.
Thanks guys!
Np good luck
and remember if you like any of flipzmode's stuff visit his site www.geekfor.me and help him out by either donating or at least click the adds
wtphoto said:
Np good luck
and remember if you like any of flipzmode's stuff visit his site www.geekfor.me and help him out by either donating or at least click the adds
Click to expand...
Click to collapse
I read "at least click the adds" wrong in my head and it turned out someting really dirty...
I have some problems.
I can not wipe cache and after install ROM I've got 'Force Close' apps.
How can I resolve that issues? I install again ROM and still ocurs errors.
Pls give me instructions what I must do.
Thanks
Why was I referred to this as a fix? For one, the command isn't even posted. Is their a command to wipe the dalvik-cache? If yes, what is the command that I would run?
I notice two options:
-w
Wipe the data partition
-d
Flash the data partition
Well if you don't use a2sd, this is the fix
That's a known "issue", the wipe script gives an error because it tries to wipe the dalvik-cache from the ext partition after it erased the dalvik-cache from /data. Since you don't have an ext partition it will exit and throw the error.
Don't worry about it, your dalvik-cache IS WIPED, even when you see the error.
Thanks regaw_leinad,
I kept attempting it with the latest fresh-toast rom but it would continue rebooting. It's the only rom that wouldn't have a successful dalvik wipe. I gave up and went back to damageless's SprintUpdate2.zip.
Thanks,
Zac
I've been reading something that interested me.
https://www.reddit.com/r/MotoX/comments/2kx2lv/how_do_you_encrypt_a_rooted_moto_x/
Specifically.
I had the same issue today. Booted into safe mode, then I was able to encrypt.
Press power button to get power off popup menu. Press and hold power off. You will get another popup offering to reboot in safe mode.
Safe mode worked. This uncomplicates my process of rooting, unrooting, encrypting, and having issues rerooting after encryption. This is also a crazy easy single step process for an issue that has given me months of headaches.
You shall be the first person ever that I have given gold to.
Thank you so much!
Click to expand...
Click to collapse
I enter my password in the encryption settings menu and hit the Encrypt button
Click to expand...
Click to collapse
How would encryption effect flashing a new rom?
What are your guys thoughts on encryptimg a unlocked and rooted phone?
I do not want to enable it yet till it is comfirmed its ok.
Thanks.
Um I haven't had a problem and I've encrypted the software many times as I have installed many rooms and I always encrypt after setting everything up post root so it should just work without issue. Maybe they just weren't being patient and it can take a bit of time
timde9 said:
Um I haven't had a problem and I've encrypted the software many times as I have installed many rooms and I always encrypt after setting everything up post root so it should just work without issue. Maybe they just weren't being patient and it can take a bit of time
Click to expand...
Click to collapse
What about unencrypting? To say to flash a new kernel or rom?
Well that's an interesting question. I am testing twrp builds from hashbang to try and get encryption fully supported for this device in twrp. Until that time you can actually still flash zips via adb sideload no problem
timde9 said:
Well that's an interesting question. I am testing twrp builds from hashbang to try and get encryption fully supported for this device in twrp. Until that time you can actually still flash zips via adb sideload no problem
Click to expand...
Click to collapse
Ohh. Cool. I'll have to learn adb.
@timde9
I've got twrp installed.
To get to recovrry mode, do I go into recovery mode in twrp and then the recovery button in twrp to install packages m zips from adb?
to install packages via adb is pretty simple really you just open twrp go to advanced menu and open "adb sideload" from there. Then connect your device to your computer install adb and sideload an app with this syntax
"adb sideload ***.zip"
That is radical. Ty for this.
Encryption went like a breeze.
took no more than 20 min. I feel safe now.
timde9 said:
Well that's an interesting question. I am testing twrp builds from hashbang to try and get encryption fully supported for this device in twrp. Until that time you can actually still flash zips via adb sideload no problem
Click to expand...
Click to collapse
Just found out after encrypting twrp fails to mount data to backup. I might restore without encryption. That way I have access to backups on my phone too.
So I am having a problem restoring a backup. Since I cannot decrypt, to get rid of data from being locked down, do I flash with a rom? I am stuck.
Ok I have to do a factory reset. But not sure if this exists and works through twrp. Or if I have to do a factory reset some otherway.
Ok I skipped trying to reinstall rom and did a little searching.
This guy but with a 6P had exact issue.
For me to wipe data I need to
Code:
fastboot format userdata
https://www.reddit.com/r/Nexus6P/comments/3qnzz0/twrp_unable_to_mount_data/
Hitti2 said:
Ok I skipped trying to reinstall rom and did a little searching.
This guy but with a 6P had exact issue.
For me to wipe data I need to
Code:
fastboot format userdata
https://www.reddit.com/r/Nexus6P/comments/3qnzz0/twrp_unable_to_mount_data/
Click to expand...
Click to collapse
Is this ok to do? I don't want mess anything up.
Hitti2 said:
Is this ok to do? I don't want mess anything up.
Click to expand...
Click to collapse
That will erase all your data including files, apps, etc. Anything installed to /system should be untouched.
asuhoops8628 said:
That will erase all your data including files, apps, etc. Anything installed to /system should be untouched.
Click to expand...
Click to collapse
Thanks for confirming this. Exactly what I need when time comes to decrypt "wipe" I will use this.
I wasn't sure if it would delete the partition or wipe, this is why I asked.
Ty.
Hitti2 said:
Thanks for confirming this. Exactly what I need when time comes to decrypt "wipe" I will use this.
I wasn't sure if it would delete the partition or wipe, this is why I asked.
Ty.
Click to expand...
Click to collapse
Upon reading this again, just to be safe, you might want to start with just a fastboot erase. I think format does the same thing, but I have never used it.
Since you would be specifying the partition with both commands, I do not think you are in risk of completely blowing up your user partition if you choose to use fastboot format, but once again, I have always just used fastboot erase.
Hitti2 said:
Ok I skipped trying to reinstall rom and did a little searching.
This guy but with a 6P had exact issue.
For me to wipe data I need to
Code:
fastboot format userdata
https://www.reddit.com/r/Nexus6P/comments/3qnzz0/twrp_unable_to_mount_data/
Click to expand...
Click to collapse
So I went to use this. I got an error.
Code:
Formatting is not supported for filesystem with type 'raw'
So now, that I am guessing, since twrp can now decrypt, I should just be able to go into twrp and do a full wipe and reinstall of the trupurexmm 2.5 And encryption should be gone?
Hitti2 said:
So I went to use this. I got an error.
Code:
Formatting is not supported for filesystem with type 'raw'
So now, that I am guessing, since twrp can now decrypt, I should just be able to go into twrp and do a full wipe and reinstall of the trupurexmm 2.5 And encryption should be gone?
Click to expand...
Click to collapse
Nope. Encryption is still enabled. I flashed trupurexmm 2.5 following
5. How To Install A ROM with TWRP Recovery
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Click to expand...
Click to collapse
I'm having an issue encrypting. Encryption will not start on my rooted moto x. I factory reset and encrypted, but could not get root working. Flashed everything via adb sideload in twrp but root refueses to work. Any ideas
Sent from my XT1575 using Tapatalk
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
kunal_07 said:
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
Click to expand...
Click to collapse
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
kunal_07 said:
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
Click to expand...
Click to collapse
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Heisenberg said:
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Click to expand...
Click to collapse
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
kunal_07 said:
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
Click to expand...
Click to collapse
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Heisenberg said:
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Click to expand...
Click to collapse
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
the log says:
E:Unable to decrypt with default password, you may need to perform a format data.
E:unable to mount storage
E:unable to mount settings storage during GUI startup.
kunal_07 said:
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
Click to expand...
Click to collapse
That's odd, I can't think of why 3.0.0-1 wouldn't boot, but 2.8.7.2 definitely won't work as it obviously can't decrypt. You might not be able to backup.
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
kunal_07 said:
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
Click to expand...
Click to collapse
I think you're pretty much stuck, you could try disabling all security.
is it possible to sideload supersu somehow?
kunal_07 said:
is it possible to sideload supersu somehow?
Click to expand...
Click to collapse
Maybe, you could try adb sideload in TWRP, but SuperSU needs to access the data partition which TWRP can't decrypt.
I tried it and it got to
**Boot image patcher**
patching sepolicy.
Failure, aborting.
i seem to have the same issues too. unable to access recovery and lost root. phone cant be detected in fastboot.
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Great news
1. Yes.
2. I don't think such a command exists. You'd need to use the "fastboot format userdata" command instead if you want to decrypt anyway. Just remember to backup all your data first.
3. You'd need to flash a custom kernel today doesn't force encryption. Otherwise your data well will automatically encrypt on the first boot after formatting.
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
kauemelhado said:
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
Click to expand...
Click to collapse
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
kunal_07 said:
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
Click to expand...
Click to collapse
Tks,
I found it 2 seconds later I asked you. LOL
Anyhow, thank you bro.
Just got my RMA, so of course I instantly unlock, root, and go to disable forced encryption and i keep getting a password error, my only pin i've ever used won't work, so I flashed factory, reset it up, made sure i didn't use a pin or anything, tried again, still asks for a password and won't accept mine. Am I missing something or is the fact they sent me a remanufactured phone screwing me because of the previous users pin?
kickenwing13 said:
Just got my RMA, so of course I instantly unlock, root, and go to disable forced encryption and i keep getting a password error, my only pin i've ever used won't work, so I flashed factory, reset it up, made sure i didn't use a pin or anything, tried again, still asks for a password and won't accept mine. Am I missing something or is the fact they sent me a remanufactured phone screwing me because of the previous users pin?
Click to expand...
Click to collapse
What TWRP version are you using? Are you on the newest 3.03? If not that's more than likely your problem.
murphyjasonc said:
What TWRP version are you using? Are you on the newest 3.03? If not that's more than likely your problem.
Click to expand...
Click to collapse
OMG I'm confident it's 3.02. So I need to update that before I try the decrypting thing. I need to go root, twrp 3.3 then unencrypt ?
Thanks man I wouldn't ahve thought of that .
kickenwing13 said:
OMG I'm confident it's 3.02. So I need to update that before I try the decrypting thing. I need to go root, twrp 3.3 then unencrypt ?
Thanks man I wouldn't ahve thought of that .
Click to expand...
Click to collapse
Just download the updated TWRP from this link. Boot back into recovery and choose flash IMG instead of zip. Install to recovery partition and then reboot. You should be good to go.
http://dl.twrp.me/angler/
murphyjasonc said:
Just download the updated TWRP from this link. Boot back into recovery and choose flash IMG instead of zip. Install to recovery partition and then reboot. You should be good to go.
http://dl.twrp.me/angler/
Click to expand...
Click to collapse
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
found something on a N6 thread that says wipe user data and it should work .
kickenwing13 said:
found something on a N6 thread that says wipe user data and it should work .
Click to expand...
Click to collapse
Yeah that will work and shouldn't be an issue backing up everything with a new phone. TWRP should be able to read an encrypted device though as long as you gave it permissions to change system. No kernel will decrypt a device but most do not force encrypt.
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
kickenwing13 said:
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
Click to expand...
Click to collapse
Are you by chance trying to restore a backup on your RMA?
kickenwing13 said:
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
Click to expand...
Click to collapse
I had a similar problem with TWRP 3.0.3-0 when I tried to restore a backup. It asked for a password, which has never happened before. I couldn't access my backup or any of my data or boot up. I had to restore stock. Clearing user data did nothing.
murphyjasonc said:
Yeah that will work and shouldn't be an issue backing up everything with a new phone. TWRP should be able to read an encrypted device though as long as you gave it permissions to change system. No kernel will decrypt a device but most do not force encrypt.
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
Are you by chance trying to restore a backup on your RMA?
Click to expand...
Click to collapse
I was not . Just trying to disable force encrypt root and get PN back on it . Wiping worked for me. Also on 3.03, but that alone didn't solve, had to wipe . May be because I was using WUGS instead of manually doing it . Not sure, but it worked .
kickenwing13 said:
I was not . Just trying to disable force encrypt root and get PN back on it . Wiping worked for me. Also on 3.03, but that alone didn't solve, had to wipe . May be because I was using WUGS instead of manually doing it . Not sure, but it worked .
Click to expand...
Click to collapse
Hey, I'm running into the same problem after an RMA. I'm currently on stock unrooted 7.1.1 and want to flash custom rom but want to disable encryption beforehand. Can you advise proper wipe steps, or is this correct?
- unlock bootloader
- restart phone, enable developer options for USB debugging
- fastboot twrp-3.0.3-0-angler.img
- factory reset
- wipe everything (all checkboxes) including internal? (will this format with no encryption?)
- wipe system, data, cache
- push ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip to phone via ADB in TWRP
- flash ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip
- restart
Or is there another way to decrypt data or is it not an issue when clean wiping a new ROM?
Thanks and appreciate any help.
martinomac said:
Hey, I'm running into the same problem after an RMA. I'm currently on stock unrooted 7.1.1 and want to flash custom rom but want to disable encryption beforehand. Can you advise proper wipe steps, or is this correct?
- unlock bootloader
- restart phone, enable developer options for USB debugging
- fastboot twrp-3.0.3-0-angler.img
- factory reset
- wipe everything (all checkboxes) including internal? (will this format with no encryption?)
- wipe system, data, cache
- push ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip to phone via ADB in TWRP
- flash ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip
- restart
Or is there another way to decrypt data or is it not an issue when clean wiping a new ROM?
Thanks and appreciate any help.
Click to expand...
Click to collapse
You need to Format Data, Not Wipe to decrypt. It WILL wipe EVERYTHING so make sure anything in internal storage you want is backed up.
CyberpodS2 said:
You need to Format Data, Not Wipe to decrypt. It WILL wipe EVERYTHING so make sure anything in internal storage you want is backed up.
Click to expand...
Click to collapse
Thanks for confirming, I wasn't aware that there's a difference between Format Data and Wipe Data. After formatting data, I should be able to sideload the ROM, gapps, etc back via TWRP right?
I always try to keep an emergency folder on the PC with the minimum needed to copy back to the phone through recovery. In my case I keep a copy of pure nexus, dynamic gapps, supersu and elementalx. That combination never fails to boot and I know it well enough to get back in business in short order if it all went to hell. Do what's best for you.
Sent from my Nexus 6 using XDA-Developers Legacy app
Can you/has anyone flashed 8.0 using FlashFire? Full image and just flashing Boot, System, and Vendor from 7.1.2? The reason I ask, I have never had luck doing just downloading the OTA, and flashing that with FlashFire
Thanks
idbl_fanatic said:
Can you/has anyone flashed 8.0 using FlashFire? Full image and just flashing Boot, System, and Vendor from 7.1.2? The reason I ask, I have never had luck doing just downloading the OTA, and flashing that with FlashFire
Thanks
Click to expand...
Click to collapse
Update, flashing the OTA zip file does not work, I ended up flashing the full system and only selecting Boot, System, and Vendor, so fare so good
Did you grab the factory image? I noticed that it reads Not for TMO/USCC/Fi
Bangincrazy said:
Did you grab the factory image? I noticed that it reads Not for TMO/USCC/Fi
Click to expand...
Click to collapse
Yes, Factory image, I am on AT&T
idbl_fanatic said:
Yes, Factory image, I am on AT&T
Click to expand...
Click to collapse
Now all you need to do is manually flash the bootloader and modem via fastboot.
v12xke said:
Now all you need to do is manually flash the bootloader and modem via fastboot.
Click to expand...
Click to collapse
you can always ran the flash-all.bat file after editing the file and removing the -w from it.
If you want to keep your system decrypted simply boot to bootloader/recoery and flash any moded kernel. either way, using flashboot is simple enough so you don't have to use flashfire.
idbl_fanatic said:
Update, flashing the OTA zip file does not work, I ended up flashing the full system and only selecting Boot, System, and Vendor, so fare so good
Click to expand...
Click to collapse
This worked for me, except that it erased TWRP even when I selected to option to back up recovery. At the end it wouldn't boot up and had to perform a factory reset, so in the end, I got a clean, stock 8.0, unrooted.
patriot76 said:
This worked for me, except that it erased TWRP even when I selected to option to back up recovery. At the end it wouldn't boot up and had to perform a factory reset, so in the end, I got a clean, stock 8.0, unrooted.
Click to expand...
Click to collapse
I wonder why it did that, I had no issues, I have had it do that before on 7.1.2 however.
I downloaded the full ota file from Google site, and flashed it like a normal ota + root afterwards with flashfire.
Been 3 days since, Android o works like a charm!
ixayman said:
I downloaded the full ota file from Google site, and flashed it like a normal ota + root afterwards with flashfire.
Been 3 days since, Android o works like a charm!
Click to expand...
Click to collapse
Wow that's good news, what phone & What carrier are you using? Did FlashFire read it the way it does with a Nougat OTA update
fiverings said:
Wow that's good news, what phone & What carrier are you using? Did FlashFire read it the way it does with a Nougat OTA update
Click to expand...
Click to collapse
my phone is 6p 64g, for my carrier I'm using a local one here in israel so idk if it's relevant to the issues you guys get :C.
in terms of flashing i flashed it like any normal monthly security patch lol, just went on google ota page, downloaded the ~1gb file.. then on flashfire i chose ota, selected said file + inject superSu afterwards, for wiping i chose cache and dalvik only. and done.
ixayman said:
my phone is 6p 64g, for my carrier I'm using a local one here in israel so idk if it's relevant to the issues you guys get :C.
in terms of flashing i flashed it like any normal monthly security patch lol, just went on google ota page, downloaded the ~1gb file.. then on flashfire i chose ota, selected said file + inject superSu afterwards, for wiping i chose cache and dalvik only. and done.
Click to expand...
Click to collapse
I have 6p 64gb also. We're you on the August build 7.1.2. and you only wiped dalvik and Cache and did you uncheck Data & 3rd party apps.so you just wiped dalvik & cache and nothing else. I usually flash the factory image to get monthly update because my bootloader is unlocked. So I don't get OTA updates thru my phone.
fiverings said:
I have 6p 64gb also. We're you on the August build 7.1.2. and you only wiped dalvik and Cache and did you uncheck Data & 3rd party apps.so you just wiped dalvik & cache and nothing else. I usually flash the factory image to get monthly update because my bootloader is unlocked. So I don't get OTA updates thru my phone.
Click to expand...
Click to collapse
i think i was on may or June's build i don't remember correctly. I also have bootloader unlocked but i never allow automatic OTA updates threw my phone, I just download the file manually (from here https://developers.google.com/android/ota) and flash it with flashfire, that way i continue where i left off without loosing any data (+root ). you should try it. and yeah on wipe options i untick everything except cache and dalvik.
ixayman said:
i think i was on may or June's build i don't remember correctly. I also have bootloader unlocked but i never allow automatic OTA updates threw my phone, I just download the file manually (from here https://developers.google.com/android/ota) and flash it with flashfire, that way i continue where i left off without loosing any data (+root ). you should try it. and yeah on wipe options i untick everything except cache and dalvik.
Click to expand...
Click to collapse
Thanks ixayman, going to wait a few days, because the OTA says it's not compatible with T-Mobile, us Cellular, Fi. All those are in my fi that I use. And I read that people who down loaded either Factory image or OTA are not working with Fi . When they fix this I try it then.
Thanks, you've been a big help