I was flashing a new ROM and accidentally ticked the option to wipe "Internal Storage." Now, I cannot access any files because they have obviously been deleted. I am stuck in TWRP with nothing to flash and no OS installed. Is there some way I can fix this?
pandag said:
I was flashing a new ROM and accidentally ticked the option to wipe "Internal Storage." Now, I cannot access any files because they have obviously been deleted. I am stuck in TWRP with nothing to flash and no OS installed. Is there some way I can fix this?
Click to expand...
Click to collapse
Unroot your phone to factory image then root again.
OR flash clockmod revoir to access storage (haven't tried b4 thou)
Reboot into the boot loader (Hold down power and volume down) and and then fast boot the factory image.
Google "how to restore nexus 4 to stock, fast boot"
http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html
it's easy.
pandag said:
I was flashing a new ROM and accidentally ticked the option to wipe "Internal Storage." Now, I cannot access any files because they have obviously been deleted. I am stuck in TWRP with nothing to flash and no OS installed. Is there some way I can fix this?
Click to expand...
Click to collapse
Just ADB Push your files connecting your phone to the PC while TWRP is on.
i also want to wipe internal storage using twrp in my nexus 5. i have my rom in flash drive. can i flash the rom that I have in my flash drive if I mount it after I wiped internal storage?
Current TWRPs support MTP, all you need to do is wipe the storage and plug your phone into the PC. Just make sure that MTP is checked in the "mount" menu of TWRP. You can then proceed to put the ROM's zip onto the internal storage and flash like you normally would.
So I had my phone with TWRP and rooted, but then I upgraded to the latest firmware using Smart Switch on my PC.
Without doing any research I then stupidly flashed TWRP to my phone thinking I would just re-root it using TWRP and flashing the latest SUPERSU file; however, now TWRP doesn't recognize my internal storage and it is stuck in a boot loop unless I can flash SUPERSU or DT Verity fix. The internal storage is not recognized by my computer either when I plug my phone on even if I enable MTP in TWRP, I think this is something to do with the last USB debugging options but I am not sure?
What is my best solution without wiping my data?
If I copy the files to an SD card will TWRP recognize them? I am guessing no?
Can I flash stock back over TWRP to save my data? If so I am on Wind Mobile Canada, what file should I be flashing?
Lastly, I believe there is someway to send the files over ADP but I can't find any straight forward instructions on how to do so.
Thanks,
superskid said:
So I had my phone with TWRP and rooted, but then I upgraded to the latest firmware using Smart Switch on my PC.
Without doing any research I then stupidly flashed TWRP to my phone thinking I would just re-root it using TWRP and flashing the latest SUPERSU file; however, now TWRP doesn't recognize my internal storage and it is stuck in a boot loop unless I can flash SUPERSU or DT Verity fix. The internal storage is not recognized by my computer either when I plug my phone on even if I enable MTP in TWRP, I think this is something to do with the last USB debugging options but I am not sure?
What is my best solution without wiping my data?
If I copy the files to an SD card will TWRP recognize them? I am guessing no?
Can I flash stock back over TWRP to save my data? If so I am on Wind Mobile Canada, what file should I be flashing?
Lastly, I believe there is someway to send the files over ADP but I can't find any straight forward instructions on how to do so.
Thanks,
Click to expand...
Click to collapse
I bet your internal storage is encrypted, so that TWRP won't be able to read from it because it's not supported yet.
If you copy the supersu zip to an external SD and install it from TWRP you won't loose any data and you will be ok.
The boot loop is caused when you swipe on the first screen in TWRP and don't install anything (installing either dm-verify of supersu will let you boot again).
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.
Tried sideloading OS zip but got a cannot read error in powershell, please help.
Not much can be done now. I have had this issue twice where I lost GBs of Data. Try MSM tool to recover your phone, worked for me as latest as two days back.
Check this
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
I had this happen to me a while back. I had lost TWRP also though but was able to fastboot into it, so needed a PC. I too had the issue of the internal storage being encrypted so couldn't flash the full OTA ROM from my internal storage. Luckily I had an OTG cable adapter and a pendrive on hand. I copied the OTA and TWRP zips from my PC to that and flashed them from USB after booting into TWRP from fastboot. I've never used the MSMTool but managed to get my phone back up and running using this method. From my experience, you need to let the ROM boot fully to the point where you have entered your pin. Once you get past that, your internal storage should be able to decrypt in TWRP if you reboot into TWRP after that.
Hope this helps.
I'm on OxygenOS 9.0.14 and tried update to OxygenOS 9.0.15. Unfortunately I have some problem with slot B - which is encrypted (probably my earlier mistake - I changed TWRP with active pin lock or because I restore backup in TWRP, I'm not sure why) . Slot A is ok. When I try to update to OxygenOS 9.0.15, the phone stuck on stock recovery (because slot B is encrypted?). When I change to slot A, phone works again on OxygenOS 9.0.14.
Is there any solution to fix it (decrypt slot B?) without factory reset?
Now I haven't got any pin/pattern/fingerprint lock, my TWRP: 3.3.1-6 Unofficial by mauronofrio.
Miedzio said:
Is there any solution to fix it (decrypt slot B?) without factory reset?
Click to expand...
Click to collapse
Once it's encrypted, the only thing I know of is to format data. There's nothing the matter with doing that--you will need to back up all your personal files first.
Did you install 9.0.15 via the System Update installer? That might be better, and after the installation and successful booting of 9.0.15, be prepared to re-install TWRP via ADB etc.
Yes, I tried to install 9.0.15 via the System Update installer, via TWRP too, but the result was the same. Couple of times I had to re-install TWRP via ADB or restored nandroid backup via TWRP. I think the problem is encrypted slot B.
Summary: I need to format data (factory reset)? I have backup from Titanium Backup, but even that, it take some time to restore (it isn't 1 to 1 backup). So I need more free time to do this and now I have to stay with 9.0.14.
When you flashed 9.0.15 in TWRP did you flash the TWRP installer as well? As in flash OOS to slot a, change slots, then flash OOS AND the TWRP installer zip (not IMG), as the installer zip flashes TWRP to both slots automatically. That should remove any possibility of booting into the stock recovery. Be smart and make a backup of your data onto your computer, another phone, whatever device that's not your 6T. That way, should any encryption issues persist, it's no big deal to go ahead and format data (not factory reset) both slots, and problem should be fixed.
A small hint: i personally COPY everything I want to backup (pictures, music, Magisk modules, ROM zips, etc) to one folder then zip that folder into a single archive, use whatever compression you like, I go with none as the whole point is to just transfer one single large file instead of hundreds or even thousands of individual files and directories... It helps with transfer time.
lordcheeto03 said:
When you flashed 9.0.15 in TWRP did you flash the TWRP installer as well? As in flash OOS to slot a, change slots, then flash OOS AND the TWRP installer zip (not IMG), as the installer zip flashes TWRP to both slots automatically. That should remove any possibility of booting into the stock recovery. Be smart and make a backup of your data onto your computer, another phone, whatever device that's not your 6T. That way, should any encryption issues persist, it's no big deal to go ahead and format data (not factory reset) both slots, and problem should be fixed.
A small hint: i personally COPY everything I want to backup (pictures, music, Magisk modules, ROM zips, etc) to one folder then zip that folder into a single archive, use whatever compression you like, I go with none as the whole point is to just transfer one single large file instead of hundreds or even thousands of individual files and directories... It helps with transfer time.
Click to expand...
Click to collapse
Sorry, I didn't describe it clearly. When I flashed 9.0.15 via System Update, the phone goes to stock recovery - I need to install TWRP via ADB to back to slot A or I must do factory reset.
When I flashed 9.0.15 via TWRP, after that I install TWRP (img and zip). Unfortunately after reboot, 6T always goes to TWRP in slot B, but everything is encrypted. When I back to slot A, phone boots into 9.0.14 (no problem witch encryption).
I have all backup on my computer (all storage + Titanium Backup + TWRP backup). If I will format data, will be enough to just copy all files from computer? I'm not sure it will work. What about settings etc.?
When flashing in TWRP, there is no need to flash both the TWRP img AND the zip. Just do that how I said. Boot to TWRP, flash 9.0.15 on slot a, without rebooting, change to slot b and flash 9.0.15 again along with the TWRP installer zip. At this point, I say reboot back to recovery, whether you are going to flash Magisk or not. If everything is encrypted, go on and format data on both slots and boot, do the initial setup and all, then move your data back and flash root. Otherwise, if you can recognize your files and folders when you reboot to recovery, you can go on and either flash Magisk or boot on into OOS. If it's not just a bunch of random crap, you shouldn't even have to worry about your backup data as everything should be exactly as it was before you started, except you'll be on 9.0.15 instead of .14.
Should you end up having to format after doing what I said, there may be a way to restore all your settings, I'm not sure. Again, me personally, all I save is my titanium backup folder, anything in my download folder, and any other folders and all my Magisk modules. All my pictures and videos I have set to automatically backup to Google photos, but if you don't do that you'll want to include that too. I don't worry about my settings, call logs, messages, all that type stuff, I just go back through set it up fresh. Again, there might be a way to restore all that stuff, but I only keep the most important stuff. As far as the TWRP backup goes, I haven't had any luck restoring my TWRP data so that as well is something I don't bother saving (or even making in the first place.)
If you have to format, once whatever you want saved is backed up to another device, (computer, another phone, thumb drive, whatever) all you have to do is format both slots and reboot. You SHOULD at that point be able to boot into 9.0.15 and perform your initial setup; add Google account, fingerprint/face unlock data, etc. Once you're at the home screen and all the initial setup is complete, then you can move your data back to the device.
The most important thing is to put your data back in whatever directories it was in before the format. The only directories I backup are directories I have added something to, have downloaded to, or that I have created. Directories like Alarms, Android, Movies, any hidden directories (unless I created them and subsequently hid them) all that I just delete.
As long as you put all that back where it was before the format, everything should be just like it was before the format. Your Titanium Backup files, once placed back in internal storage/Titanium Backup will show up in Titanium Backup and you can restore it all through the app. Your pictures, if you backup any, will show up automatically in your gallery once placed back into internal storage/DCIM, etc.
You'll obviously have to reflash Magisk and any modules and relevant setup.
TL;DR
As long as you put your data back into the directories it came from, everything minus your settings will be back to how it was before formatting.