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.
hi guys
after restoring twrp backup (data and system)
WIFI is broken, no way to make it work again, even restoring persist backup from twrp or flashing the original persist
not either deleting file contect of wifi_mac.bin in root/persist
does anyone know how to make wifi working again after TWRP restore of data and system?
differently TWRP is totally useless for backup in Mi A2 at the current state.
Espmic86 said:
hi guys
after restoring twrp backup (data and system)
WIFI is broken, no way to make it work again, even restoring persist backup from twrp or flashing the original persist
not either deleting file contect of wifi_mac.bin in root/persist
does anyone know how to make wifi working again after TWRP restore of data and system?
differently TWRP is totally useless for backup in Mi A2 at the current state.
Click to expand...
Click to collapse
flash the original boot.img from the same system version installed in your device.
If V9.6.15.0.ODIMIFE, download the same OTA image version package, unzip it, get only boot.img and use fastboot to flash it into your device.
fastboot flash boot_b boot.img
fastboot flash boot_a boot.img
I hope this works
Espmic86 said:
hi guys
after restoring twrp backup (data and system)
WIFI is broken, no way to make it work again, even restoring persist backup from twrp or flashing the original persist
not either deleting file contect of wifi_mac.bin in root/persist
does anyone know how to make wifi working again after TWRP restore of data and system?
differently TWRP is totally useless for backup in Mi A2 at the current state.
Click to expand...
Click to collapse
Flash this kernel from temp twrp. https://forum.xda-developers.com/mi-a2/development/kernel-hex-t3855773
It worked for me.
Tnx man. After flash kernel magisk doesn work.
How do i reinstall magisk now? You Need the "patch boot Image" method in order to support OTA. But boot Image now is not stock, cause It s updated with the new kernel so i cant use the official boot.img , should extract the new One from My device? How?
Or should i flash magisk 17.1 from TWRP? But still cant, because TWRP install s It in Active slot offline TWRP (at the moment) and not in the needed boot partition.
****, help It s getting too annoying ahahah
Espmic86 said:
Tnx man. After flash kernel magisk doesn work.
How do i reinstall magisk now? You Need the "patch boot Image" method in order to support OTA. But boot Image now is not stock, cause It s updated with the new kernel so i cant use the official boot.img , should extract the new One from My device? How?
Or should i flash magisk 17.1 from TWRP? But still cant, because TWRP install s It in Active slot offline TWRP (at the moment) and not in the needed boot partition.
****, help It s getting too annoying ahahah
Click to expand...
Click to collapse
Download the magisk zip and boot into twrp and just flash it. You can switch the partitions in twrp and flash magisk. Just don't reboot twrp after switching the partitions.The latest twrp from Tingyichen can be downloaded from this thread.
https://forum.xda-developers.com/mi-a2/development/recovery-unofficial-twrp-recovery-mi-a2-t3825146
the command is fastboot boot twrp-3.2.3-jasmine-20181020.img and it goes straight into twrp with no flashing required.
booting directly in twrp with command and without flashing it in any partion caused me bootloop and data wipe, also have read this in another thread (twrp one)
Did you use the latest one from 20/10?
Something recently broke Twrp so now I cant touch my /data partition, ive read that I need to format my phone to fix this issue, the problem is that a recent update from Lineage OS is what broke it I believe, and I updated from within LOS (check for new updates download and install) which auto restarted, so when I went to go back into TWRP to reflash Magisk I started getting the issue
So now I have no root, and no twrp abilities that I know off, which means I cant use a decent backup program
can anyone help?
EDIT: I don't know if they has any relevance but ADB does have root permissions,
EDIT 2: I found out that I can reinstall magisk VIA ADB Sideload from within TWRP, as such I now have root again
@foxtrotdragon: If you can get into TWRP then reflashing Magisk shouldn't be a problem. However, if /data is encrypted then Magisk may not flash, it needs to be able to place some files there. You'll lose everything on internal storage, but formatting /data is the only way forward.
If you can't boot into TWRP then the obvious solution is to reflash recovery from a PC.
AnonVendetta said:
@foxtrotdragon: If you can get into TWRP then reflashing Magisk shouldn't be a problem. However, if /data is encrypted then Magisk may not flash, it needs to be able to place some files there. You'll lose everything on internal storage, but formatting /data is the only way forward.
If you can't boot into TWRP then the obvious solution is to reflash recovery from a PC.
Click to expand...
Click to collapse
Getting into twrp is no issue, the issue is that TWRP cannot read the internal storage, it can read external fine, but fails to read internal storage, which means i cant flash anything, an reflashing twrp does nothing
im fine with reformatting the phone, but i need to backup my stuff first, which i can not do since no root
@foxtrotdragon: Unfortunately for you, backing up the contents of your internal storage is no longer possible, unless you can think of some ingenius method to decrypt without formatting. Formatting /data is your only option. In the future, you should make backups *BEFORE* disaster strikes.
[Solved (look at bottom of post)]
so, hopfully this is in the right place.
Following the procedure I've done on my nexus 6p many times over; I created a TWRP backup on my 6t then tried restoring the backup I made with twrp and when it finished I pressed reboot to system. The device then only booted into twrp. I saw it was on the "a" partition and I knew I was previously on the b partition so I manually switch partitions and now I'm stuck in fastboot boatloader I have tried flashing a temp twrp.img but im getting an error "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" in fastboot
After that I switched active partition in fast boot and got into twrp but my data appears to be encrypted and after restoring sys,data,efs,vendor (skipping boot as it holds the recovery now) I only have fast boot in both a/b partitions. I'm going to try to fast boot twerp then install twerp permanently and see if i can get a wotking twrp if not then ill have to get a factory image to get back to stock but was hoping to get some data off but whatever..
I'm kind of new to this a/b partition setup. any help is appreciated.
Edit: for future reference All I was doing was trying to restore a backup? how do I restore a backup on an a/b partition system? As far as I know I did it right...
1) remove lockscreen pin ect..
2) backup boot,sys,ven,data
When restoring
1) mount partitions
2) select restore backup and restore all .....
What am I missing?
____
Solved:
twrp for 6t is borked when it comes to backing up/ restoring...
The version in question: twrp-installer-fajita-3.2.3-1.zip
I restored my 6t to stock with msmdownloadtool and reinstalled twrp then made a test backup. After restoring it I was left in a twrp bootloap and encrypted data partition.
I don't think you should ever need to manually switch slots.
If you are on slot A, and flash an update, it will install to slot B. When you restart your phone, it will automatically switch to B for you.
Also, you shouldn't be flashing the TWRP.img, but booting it instead.
You could try starting fresh with the msmdownloadtool which is found in these forums.
fireeyeeian said:
[Solved (look at bottom of post)]
so, hopfully this is in the right place.
Following the procedure I've done on my nexus 6p many times over; I created a TWRP backup on my 6t then tried restoring the backup I made with twrp and when it finished I pressed reboot to system. The device then only booted into twrp. I saw it was on the "a" partition and I knew I was previously on the b partition so I manually switch partitions and now I'm stuck in fastboot boatloader I have tried flashing a temp twrp.img but im getting an error "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" in fastboot
After that I switched active partition in fast boot and got into twrp but my data appears to be encrypted and after restoring sys,data,efs,vendor (skipping boot as it holds the recovery now) I only have fast boot in both a/b partitions. I'm going to try to fast boot twerp then install twerp permanently and see if i can get a wotking twrp if not then ill have to get a factory image to get back to stock but was hoping to get some data off but whatever..
I'm kind of new to this a/b partition setup. any help is appreciated.
Edit: for future reference All I was doing was trying to restore a backup? how do I restore a backup on an a/b partition system? As far as I know I did it right...
1) remove lockscreen pin ect..
2) backup boot,sys,ven,data
When restoring
1) mount partitions
2) select restore backup and restore all .....
What am I missing?
____
Solved:
twrp for 6t is borked when it comes to backing up/ restoring...
The version in question: twrp-installer-fajita-3.2.3-1.zip
I restored my 6t to stock with msmdownloadtool and reinstalled twrp then made a test backup. After restoring it I was left in a twrp bootloap and encrypted data partition.
Click to expand...
Click to collapse
I'm currently stuck in TWRP with encrypted data after restoring a backup. I didn't know you couldn't restore backups on this phones. That sucks. I guess I'm going to have to start over now. That really really sucks.
imucarmen said:
I'm currently stuck in TWRP with encrypted data after restoring a backup. I didn't know you couldn't restore backups on this phones. That sucks. I guess I'm going to have to start over now. That really really sucks.
Click to expand...
Click to collapse
Yup, I felt the same.. it's a huge bummer especially when you get it all set up and perfect. Use msm to fix it if you can't use twrp. Hopefully twrp gets fixed soon (I'm really surprised I can't find more people who have noticed this or even twrp team talking about it) for now Im waiting for proof it works on the op6t. I even tried to use Chainfire's flashfire to make a backup and.. no it doesn't work.
fireeyeeian said:
Yup, I felt the same.. it's a huge bummer especially when you get it all set up and perfect. Use msm to fix it if you can't use twrp. Hopefully twrp gets fixed soon (I'm really surprised I can't find more people who have noticed this or even twrp team talking about it) for now Im waiting for proof it works on the op6t. I even tried to use Chainfire's flashfire to make a backup and.. no it doesn't work.
Click to expand...
Click to collapse
I think I just hard bricked my phone. https://forum.xda-developers.com/oneplus-6t/help/bricked-phone-t3914413
imucarmen said:
I think I just hard bricked my phone. https://forum.xda-developers.com/oneplus-6t/help/bricked-phone-t3914413
Click to expand...
Click to collapse
Use Msm download tool:
https://www.google.com/amp/s/forum....-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
I think that's the right post but make sure it matches your device. I used msmdownloadtool around 6 time just testing twrp and only had one hiccup where Msm wasn't detecting my one plus 6t but I eventually got it working.
use the other twrp unofficial but problem you had with would be fixed with big file system fat32 can't do it right
ecompton59 said:
use the other twrp unofficial but problem you had with would be fixed with big file system fat32 can't do it right
Click to expand...
Click to collapse
Could you post a link to it and are you sure? I used the unofficial version so which one are you talking about? I'd really not like to have to re-setup my daily driver from scratch.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482 your using early version of twrp the black one is made by same guy download unofficial twrp.zip not twrp.img reboot recovery flash twrp.zip then magisk it may work if not then format data (erases phone) then twrp,magisk reboot recovery to see if it stuck I flash magisk again when it starts up go to magisk thread get the manager 18.1 don't insall it
ecompton59 said:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482 your using early version of twrp the black one is made by same guy download unofficial twrp.zip not twrp.img reboot recovery flash twrp.zip then magisk it may work if not then format data (erases phone) then twrp,magisk reboot recovery to see if it stuck I flash magisk again when it starts up go to magisk thread get the manager 18.1 don't insall it
Click to expand...
Click to collapse
Which one? I've tried the 3.2.3.28 last and restoring didn't work. Should I try the most recent installer in the list? And can you confirm that backup&restoring works on the one plus 6t? Also is there anyway to backup my phone without twrp before I try this? I'd really would not like to have to use msm again?
sorry that didn't help format data then flash twrp then magisk should boot without msm
---------- Post added at 01:06 PM ---------- Previous post was at 12:52 PM ----------
i had to use extfat format on htc 8gb backup to get it to work maybe devs will fix that
Has there been an improvement on twrp for the 6t yet? Just curious if I can rely on a backup is there any updates?
Hello, I've been trying to root my phone, I followed a guide that tell me to
Code:
fastboot flash twrp.img
and got all my data wiped for some reason. LATER, i found out that you souldn't be doing that, instead you should be doing
Code:
fastboot boot twrp.img
But by then, I got everything on my phone deleted (i flashed an original rom from MI forums and restored a manual backup of data and some apps i had, but still I lost like a day setting up everything).
My questions are, if I hotboot TWRP will I get my data wiped again? (my bootloader is still unlocked so no danger there)
If not, can I backup my data normally using TWRP GUI on hotboot?
Also, once I've installed magisk, will I stop receiving OTAs?
Thanks
No, you won't get data wiped if you boot twrp. I'm doing this periodically and everithing is ok.
Probably you flashed twrp wrong. It should be
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
You can receive ota's with magisk. Prior to installing ota, you should uninstall/"restore partitions" with magisk but not reboot. After ota is installed, you install magisk into secondary partition (with magisk manager) and reboot.
BlackChimaera said:
No, you won't get data wiped if you boot twrp. I'm doing this periodically and everithing is ok.
Probably you flashed twrp wrong. It should be
You can receive ota's with magisk. Prior to installing ota, you should uninstall/"restore partitions" with magisk but not reboot. After ota is installed, you install magisk into secondary partition (with magisk manager) and reboot.
Click to expand...
Click to collapse
But isn't HIGHLY recommended to NOT flash the recovery?
I'm not flashing it too, just "fastboot boot" it when I need it.
BlackChimaera said:
I'm not flashing it too, just "fastboot boot" it when I need it.
Click to expand...
Click to collapse
I hotbooted TWRP and made a backup, after rebooting from TWRP, the phone boots slowly and hangs at the lock screen. Any ideas what could have triggered this?
The only "abnormal"thing i did was to rename the media folder in "data" so TWRP could include it into the backup. After that I renamed the folder to "media" again, and rebooted.
There was a "mediadrm" folder, but I don't remember if it was already there or not.
Why do you want to include media folder into backup? It has only mount points to sdcards. Do you want to include sdcard content into backup? Where is backup stored? On the same sdcard which content you backing up?
BlackChimaera said:
Why do you want to include media folder into backup? It has only mount points to sdcards. Do you want to include sdcard content into backup? Where is backup stored? On the same sdcard which content you backing up?
Click to expand...
Click to collapse
Media folder has internal storage. Anyway, i was able to boot again by flashing to latest stock rom and then restoring "data" from my backup.
Enviado desde mi Mi A1 mediante Tapatalk
BlackChimaera said:
No, you won't get data wiped if you boot twrp. I'm doing this periodically and everithing is ok.
Probably you flashed twrp wrong. It should be
You can receive ota's with magisk. Prior to installing ota, you should uninstall/"restore partitions" with magisk but not reboot. After ota is installed, you install magisk into secondary partition (with magisk manager) and reboot.
Click to expand...
Click to collapse
On Mi A1, TWRP can't be flashed from fastboot, because it doesn't have /recovery