Related
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.
Hello Guys
Today I was trying to flash a ROM but the recovery logs says unable to mount storage , I read that the stock rom [Make sure you have a not encrypted device and OEM unlock is enabled in developer settings!!]
It's unlocked but how to decrypt the device !
Twrp can't decrypt the phone, you need to wipe the phone and install some dm-verify patch, its all in the twrp thread.
Talal Aziz said:
Hello Guys
Today I was trying to flash a ROM but the recovery logs says unable to mount storage , I read that the stock rom [Make sure you have a not encrypted device and OEM unlock is enabled in developer settings!!]
It's unlocked but how to decrypt the device !
Click to expand...
Click to collapse
go in to twrp slide right to allow modification then format data not wipe this is most important the re boot recovery and then flash rom
strikerdj2011 said:
go in to twrp slide right to allow modification then format data not wipe this is most important the re boot recovery and then flash rom
Click to expand...
Click to collapse
Thank you, I had the same problem and this solved it for me.
Hi, I keep seeing that some people brick their phones due to the changes in the process. Question, Due to some battery drainage I am getting, I am trying to do a phone reset.
I currently have TWRP installed and rooted the phone using the jccuando method. What is the best way to reset the phone to factory so I can re-root again and do what I need to do without bricking? Any advice would be much appreciated!
matteosaeed said:
Hi, I keep seeing that some people brick their phones due to the changes in the process. Question, Due to some battery drainage I am getting, I am trying to do a phone reset.
I currently have TWRP installed and rooted the phone using the jccuando method. What is the best way to reset the phone to factory so I can re-root again and do what I need to do without bricking? Any advice would be much appreciated!
Click to expand...
Click to collapse
Definitely boot to twrp via hardware keys or a boot to recovery app.. Do not do it from the settings menu. It will put you into twrp bootloop until you boot from the hard keys anyway. Just remember to flash supersu after you factory reset before you boot or you'll have to boot back into twrp again and flash it.
Swizzle82 said:
Definitely boot to twrp via hardware keys or a boot to recovery app.. Do not do it from the settings menu. It will put you into twrp bootloop until you boot from the hard keys anyway. Just remember to flash supersu after you factory reset before you boot or you'll have to boot back into twrp again and flash it.
Click to expand...
Click to collapse
Thank you so much. So I see I can get to twrp no problem. What to do inside twrp before I bootloop or do I need to reset factory before I get to twrp? Then what to do after I am in a bootloop ?
matteosaeed said:
Thank you so much. So I see I can get to twrp no problem. What to do inside twrp before I bootloop or do I need to reset factory before I get to twrp? Then what to do after I am in a bootloop ?
Click to expand...
Click to collapse
If you used the method I told you there should be no bootloop. Just got to the section wipe and slide the slider for a factory reset. Then afterwards press back and go to your external sd and flash supersu again then reboot it will reboot twice after you flash supersu so don't worry.
Swizzle82 said:
If you used the method I told you there should be no bootloop. Just got to the section wipe and slide the slider for a factory reset. Then afterwards press back and go to your external sd and flash supersu again then reboot it will reboot twice after you flash supersu so don't worry.
Click to expand...
Click to collapse
Thank you. I actuallt just got done. I did factory reset instead and booted up fine. I took your advice and flashed supersu after the factory reset and i am all good now. I wonder the difference between factory reset and the format data. I was a little scared to factory reset so it woud not erase the rom.
matteosaeed said:
Thank you. I actuallt just got done. I did factory reset instead and booted up fine. I took your advice and flashed supersu after the factory reset and i am all good now. I wonder the difference between factory reset and the format data. I was a little scared to factory reset so it woud not erase the rom.
Click to expand...
Click to collapse
Format data erases all user data. Factory reset erases all but internal storage. So data format is more extensive.
Swizzle82 said:
Format data erases all user data. Factory reset erases all but internal storage. So data format is more extensive.
Click to expand...
Click to collapse
Cool thank you. I didnt have a problem since i backed up my apps with titanium.
Swizzle82 said:
Format data erases all user data. Factory reset erases all but internal storage. So data format is more extensive.
Click to expand...
Click to collapse
Hi, did everything with no problem. I got another question and not sure if you have the answer. I was hoping to re-lock the bootloader again. Do you know of a way to do that and get the phone to boot up to the system? I am trying to avoid the bootloader reboot message after turning on the phone! Thank you for all your help!
matteosaeed said:
Hi, did everything with no problem. I got another question and not sure if you have the answer. I was hoping to re-lock the bootloader again. Do you know of a way to do that and get the phone to boot up to the system? I am trying to avoid the bootloader reboot message after turning on the phone! Thank you for all your help!
Click to expand...
Click to collapse
Do not relock unless you're pure stock no twrp or modded boot img. The annoying message will always be there.
Swizzle82 said:
Do not relock unless you're pure stock no twrp or modded boot img. The annoying message will always be there.
Click to expand...
Click to collapse
Cool. I tried to relock and unlock. No problem. I just want the stock recovery. Do you know if this is flash able yet ?
matteosaeed said:
Cool. I tried to relock and unlock. No problem. I just want the stock recovery. Do you know if this is flash able yet ?
Click to expand...
Click to collapse
There is a new thread about how to return to stock somewhere here in the forum..
Swizzle82 said:
There is a new thread about how to return to stock somewhere here in the forum..
Click to expand...
Click to collapse
Sweet. I have been looking at the forum and everything says tarp has to be installed and running . I'll keep looking. Thank you sir .
Absolutely do not re-lock your bootloader unless you are 100% stock. If you brick the phone with a locked bootloader, you are screwed.
I have unlocked the boot-loader and also installed TWRP recovery on my X00_TD device which has 'Pie' as it's Stock ROM.
Now, I would like to know how to proceed to do rooting on this device.
Is it necessary to run decrypt zip file before we run 'magisk-v19.1' to root?
Please advise!
Decrypt removes another variable from the process, so yeah it might be good to remove a probable failure point.
Decrypt and then Magisk?
arko9699 said:
Decrypt removes another variable from the process, so yeah it might be good to remove a probable failure point.
Click to expand...
Click to collapse
So , irrespective of the state of the device one needs to flash the decrypt file first and then flash the magisk to root the device, right?
Please advise!
Kudla said:
So , irrespective of the state of the device one needs to flash the decrypt file first and then flash the magisk to root the device, right?
Please advise!
Click to expand...
Click to collapse
When rooting mine I used the decrypt.zip . When you factory reset the phone will take some time to encrypt your data and this prevents that. It will hinder you from flashing stuff from the internal storage in TWRP. You can use magisk without it too.
Unable to Mount Storage?
arko9699 said:
When rooting mine I used the decrypt.zip . When you factory reset the phone will take some time to encrypt your data and this prevents that. It will hinder you from flashing stuff from the internal storage in TWRP. You can use magisk without it too.
Click to expand...
Click to collapse
I went ahead and flashed magisk without flashing decrypt. The root was successful!
Now, when tried to clear cache via TWRP it says 'Unable to Mount Storage'. What could be the reason here?
Is it safe to wipe dalvik/art cache?
Please advise!
Kudla said:
I went ahead and flashed magisk without flashing decrypt. The root was successful!
Now, when tried to clear cache via TWRP it says 'Unable to Mount Storage'. What could be the reason here?
Is it safe to wipe dalvik/art cache?
Please advise!
Click to expand...
Click to collapse
Try to run decrypt.zip it should fix the problem. I used a OTG device since I didn't have a SD card. Unless you run decrypt.zip you cannot use the internal storage. So I would recommend running it despite my last statement.
hey guys, i really need your help urgently.
i just finished setting up my OP8Pro to my needs and then i restored wifi networks from my Titanium Backup from Android 8, i booted and it won't boot anymore.
i get a FATAL EXCEPTION IN SYSTEM PROCESS: WifiHandlerThread...
so now i need to reset these settings via stock recovery and i already modified my recovery to enable ADB but i can't access /data
anyone has a hint for me how to access /data and where to find the wifi config on Android 11?
it's not stored in /data/misc/wifi anymore :/
thanks a lot in advance!
You can reset WiFi within WiFi settings in settings.
But I would probably just clear data on the app you restored either in settings/apps or simply via titanium.
If it still fails then boot to recovery and wipe system.
Your storage will remain unaffected.
You could also try safe mode, power off and hold vol up and down as soon as you see the bootloader warning
Fyi I wouldn't bother restoring WiFi passwords like that, there's other ways of doing it.
Google can back these up for you for example, there are apps which can do it like swift (I think can do it)
dladz said:
You can reset WiFi within WiFi settings in settings.
But I would probably just clear data on the app you restored either in settings/apps or simply via titanium.
If it still fails then boot to recovery and wipe system.
Your storage will remain unaffected.
You could also try safe mode, power off and hold vol up and down as soon as you see the bootloader warning
Fyi I wouldn't bother restoring WiFi passwords like that, there's other ways of doing it.
Google can back these up for you for example, there are apps which can do it like swift (I think can do it)
Click to expand...
Click to collapse
thanks for your answer but unfortunately i can't boot anymore and i can't decrypt /data anymore even after reflashing stock recovery.
what's the best way to flash via fastboot to preserve data?
thank you!
eis0r said:
thanks for your answer but unfortunately i can't boot anymore and i can't decrypt /data anymore even after reflashing stock recovery.
what's the best way to flash via fastboot to preserve data?
thank you!
Click to expand...
Click to collapse
You'd have to grab one of the fastboot ROMs then flash.
Why can't you open recovery? Isn't your pin / password being accepted?
If it's not and fastboot installation can't be done then honestly I'd just MSM your current firmware..it's easier than fastboot tbh.
You'd need to bootloader unlock after but this is going to wipe everything anyway.
dladz said:
You'd have to grab one of the fastboot ROMs then flash.
Why can't you open recovery? Isn't your pin / password being accepted?
If it's not and fastboot installation can't be done then honestly I'd just MSM your current firmware..it's easier than fastboot tbh.
You'd need to bootloader unlock after but this is going to wipe everything anyway.
Click to expand...
Click to collapse
my bootloader is already unlocked and i was rooted on 11.0.0... i can boot into fastboot and recovery but i'm not prompted my unlock pattern.
this was working before testing adb integrated recovery and restoring stock recovery...
eis0r said:
my bootloader is already unlocked and i was rooted on 11.0.0... i can boot into fastboot and recovery but i'm not prompted my unlock pattern.
this was working before testing adb integrated recovery and restoring stock recovery...
Click to expand...
Click to collapse
I don't get you mate??
I'm saying that if you use the MSM tool it will lock your bootloader so you'll need to unlock it again.
In regards to your recovery if you can get to it then choose English, then wipe, then system, then wipe system.
That will get you back like I said in my previous post.
If it's not asking for your pin/password (there is no pattern)
Then you're fine
I've not used that recovery but I don't see a point in using it
dladz said:
I don't get you mate??
I'm saying that if you use the MSM tool it will lock your bootloader so you'll need to unlock it again.
In regards to your recovery if you can get to it then choose English, then wipe, then system, then wipe system.
That will get you back like I said in my previous post.
If it's not asking for your pin/password (there is no pattern)
Then you're fine
I've not used that recovery but I don't see a point in using it
Click to expand...
Click to collapse
sorry i haven't used MSM yet so i didn't know it'll relock the bootloader but i'm more familiar with fastboot flashing so i'd like to stick with that also because i read of problems with the fingerprint reader when relocking the bootloader.
i thought i could delete reset the faulty wifi config via adb by using the adb-enabled stock recovery but i wasn't able to mount /data with it since it's encrypted and it's not asking for my pattern to decrypt it.
neither the stock recovery is asking for it now...
i don't want to lose my data hence i'm looking for a way to get it back running without completely reinstalling.
do you think it could work by only flashing system partition via fastboot?
thanks man!
eis0r said:
sorry i haven't used MSM yet so i didn't know it'll relock the bootloader but i'm more familiar with fastboot flashing so i'd like to stick with that also because i read of problems with the fingerprint reader when relocking the bootloader.
i thought i could delete reset the faulty wifi config via adb by using the adb-enabled stock recovery but i wasn't able to mount /data with it since it's encrypted and it's not asking for my pattern to decrypt it.
neither the stock recovery is asking for it now...
i don't want to lose my data hence i'm looking for a way to get it back running without completely reinstalling.
do you think it could work by only flashing system partition via fastboot?
thanks man!
Click to expand...
Click to collapse
Use the thanks button buddy
I think you've certainly got a shot at it and what's the worst that can happen?
Did you actually try to wipe system in recovery? That would be my way to go.
MSM is extremely easy but I understand not wanting to lose storage.
That being said if you're correct about decryption then it won't matter anyway
dladz said:
Use the thanks button buddy
I think you've certainly got a shot at it and what's the worst that can happen?
Did you actually try to wipe system in recovery? That would be my way to go.
MSM is extremely easy but I understand not wanting to lose storage.
That being said if you're correct about decryption then it won't matter anyway
Click to expand...
Click to collapse
well after trying lots of different things i ended up wiping system settings in stock recovery. atleast i didn't lose storage.
thanks a lot for your help tho!
eis0r said:
well after trying lots of different things i ended up wiping system settings in stock recovery. atleast i didn't lose storage.
thanks a lot for your help tho!
Click to expand...
Click to collapse
You're very welcome mate, I've done the same a few times..it's not that much of a loss really, a lot of apps pick up where they left off and if you do have titanium then your back ups are retained.
Glad you're sorted.
PS: this would have had the same effect that installing system would have had, only this time you get a clean slate