Rooted phone, went to flash rom then accidentally selected to install TWRP app, read somewhere that doing so bricks your phone so I wiped everything. I accidentally selected to wipe internal storage along with this, so now I have no OS, no files on my phones internal storage, and can't figure this out.
I tried mounting usb with TWRP, but OTG reads as 0mb, and on my computer my Pixel XL shows up as AOSP on msm8996, and trying to copy files to it just freezes explorer.exe
I had the though of doing an adb push for the ROM, or even a factory OTA image but don't know the commands for this since it's not an SD card or anything.
I'm taking shots in the dark with this and nothing works, any responses and help is greatly appreciated
Phone is a Pixel XL. Already made a post on my devices section but I'm in a bit of a rush to figure this out so I took it here as well. Reeee indeed.
Never mind. after cmd and powershell weren't working I downloaded the all in one tool and just dragged the files over to the phones storage. In the future if anybody goes full retard like me, just do that
Related
Hey everyone,
So I got my tablet today and have been working on it for the past 8 hours!! I finally got CWmod on it and running. Had a nightmare of a time getting it to work correctly and after using NVFLASH to nuke the whole tablet and install the stock ROM, then updating i was able to get CWmod to run. Now I'm having a really odd issue.
I can boot into CWmod. I repartitioned the SD card, mounted it. I can see the device in windows but when I add ANYTHING to the internal SD card it is completely gone once I reboot the device. I'm trying to get a ROM on it but it's like the drive is locked or something really weird. It copys onto the tablet just fine. the second I reboot everything is deleted.
I feel like I'm missing something here. I had that issue with it when I ran the stock ROM. I could change something and it would not stick after a reboot. For example registering my device on kindle and then downloading books. as soon as I reboot the machine it's as if i never registered it. I'm really at a loss as to what to do with this. I can't seem to get it to save anything on the internal storage.
Well after fiddling with it for a while longer I'm about to give up. I used NVFLASH to get it to the stock ROM again. updated to 3588 and yet again, I can't get any changes to stick. I can change anything and everything on it while it's powered on. The second I power it off and reboot it nukes everything I did (and takes close to 5-6 minutes to boot). I even mounted it and deleted every single file on the internal storage. They all came back upon reboot. I reformatted the entire SDCARD, I reformatted all the user data, did a cache wipe.. nothing works. I'm wondering if my unit is defective? at this point I would love to just have a tablet that I can actually use. I can't understand how it's even possible to not be able to make any changes on the device unless it's reinstalling the ROM everytime I reboot?
What version of CWM are you using and how did you install it?
I was running CWM 8. I couldn't install it via the internal storage. It would boot into recovery mode and "install" but once the machine rebooted it would not boot into CWM. I tried it several times same deal. I could install it but once it rebooted, nothing :/..
So I had to use the micro SD card to install it. I edited the recovery command file and pointed it to the SDCARD2. It installed finally, and stuck!
I tried using the microSD card to install the other ROMs. But unfortunately it will not mount in CWM.
I'm trying to get CWM back on it after doing yet another wipe with NVFLASH. We'll see if I can get it to work..
So i'm basically sitting here with a brick.. unless I never power it off lol!
Ok well another odd thing is going on with this. I'm up and running with CWM 08 again. I can turn on USB mass storage mount. The tablet shows up in windows and on my linux box. I can make whatever changes I want, adding files, deleting everything on it. Nothing matters cause once I unmount and remount the device it's all back to normal. It seems like nothing is allowed to write to the internal storage even though it thinks it does write to it??
Hey all,
I stumbled into an issue a few days ago and I'm trying to figure out how to get it resolved with minimum headache.
I downloaded the latest CyanogenMod download from h8rift's get.cm website, but unfortunately I didn't notice that it was CM9 rather than CM10 until I had flashed it and the boot animation popped up.
I didn't have a CM10 zip saved to my SD card partition, and TWRP, for some reason, would not mount to USB on either my Mac or my PC. The phone wouldn't boot into CM9, so I couldn't download the zip from there either.
So, I hit 'factory reset'.. twice, both from the bootloader, and from TWRP. Well, no luck. Now the file browser in TWRP doesn't even show my SD card's contents, just the TWRP folder. Every time I see a command line in TWRP, it tells me the SD card couldn't be mounted.
So, crap. Are all my files gone? I didn't realize factory resetting wipes the phone. I have all my photos on the SD card partition as well as a somewhat recent Titanium backup, so I'd really, really, really not like to lose those.
I understand that running a RUU will probably fix my issue, but the thing is, on the off chance that my SD card contents are still around, I'd like to be able to keep them. Will running a RUU wipe the SD card, if it still is in there somewhere? Are there any other suggestions re: getting the phone to boot, or be recognized as a USB disk? Also, if I do end up RUUing, I assume I have to unlock the bootloader again. Sigh, that was a hassle the first time.
tl;dr I'm complaining about a lot of stuff that I'll probably have to do anyways because I did something stupid and wasn't smart enough to keep backups, but if anyone wants to give pointers that'll make this process easier I will kiss your shoes and worship you forever.
Thanks.
If you end up needing to wipe your SDCard, here are some helpful tips
[Q] E:Can't mount/SD card http://forum.xda-developers.com/show....php?t=1751803
---------- Post added at 11:52 PM ---------- Previous post was at 11:29 PM ----------
denversc said:
If you end up needing to wipe your SDCard, here are some helpful tips
[Q] E:Can't mount/SD card http://forum.xda-developers.com/show....php?t=1751803
Click to expand...
Click to collapse
Oops, here is the full url:
http://forum.xda-developers.com/showthread.php?t=1751803
So I just managed to boot into CyanogenMod 9, without actually doing anything.
So it boots but can't mount the SD card. I have no idea either. Any way to mount the SD card without relocking bootloader?
Have you tried to access your sd card with a file manager app like solid explorer to see if anything is still on the card?
Sent from my Nocturnalized One XL using Forum Runner
Factory reset from the bootloader appears to wipe the sdcard and leave it in an unformatted state. I did this yesterday and fixed it by letting the phone boot back into the sense rom I was running.
Not quite sure what you can do in CM9. Have you tried connecting to your computer and seeing if windows detects a valid drive? If it doesn't maybe let windows format it, yeah I don't like this idea either, so you can at last get some files on it.
I had a similar problem after flashing a nocturnal update...
Here's what I did to resolve:
Wipe all - SD card, factory reset (all can be done inside TWRP)...then plug your phone into your computer via usb and on your phone in TWRP main screen, navigate to Mount and select USB storage. It WILL show up on your computer as unformatted - just reformat (which will wipe it again) and then let you copy files in. Just download the latest CM10 (which is working great) and flash away...
I am using a Mac computer running win xp via parallels and it worked great - I don't remember what file structure to format the SD card as, but it was the default when it brought up the format dialogue...
Hope that helps!
Sent from my One X using xda premium
Hello everyone,
I need your help. Sorry for the long post.
I have a OnePlus One. It was running on CM 13.0 (Android 6.0.1). I had TWRP and MultiROM installed.
I have had an issue where whenever I flash a zip file in TWRP, the phone will show an error after installing the zip: "Unable to mount storage". This appeared in red color on the screen right after showing the progress of the zip installation. The phone worked fine and all the flashed zips worked great as well. However, the error that appeared every single time when I flash a zip file bothered me. So I tried to fix it. (I know, if it's not broken don't fix it, but sadly I tired).
I followed this video to get rid of the error => (https://www.youtube.com/watch?v=X7yDPszoQ5s). However, instead of getting rid of the error, I ended up with a huge problem. My phone couldn't recognize the data in the internal storage. It showed that the internal storage was empty. When I tired to reboot in TWRP, It said: "No OS installed are you sure you wish to reboot". I realized that the video I followed was for a different problem and that I ended up with the same issue the video was trying to fix! I tried every single option the video suggested to fix the problem and nothing helped.
I connected my phone to my laptop and downloaded the latest CyanogenMod zip for my phone and I flashed it. when I rebooted my phone I got a screen that asked for my password. I typed a random password (I discovered later that the phone will accept any password and say it's correct). I got the following error: "Decryption Unsuccessful... The password you entered is correct, but unfortunately your data is corrupt... To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your google account...Then the only thing I can select is "reset phone." ". I pressed the reset button on the screen, the phone rebooted and showed the same error. Then I tired flashing PAC ROM and I got the same error again. Then I flashed OmniROM and the phone worked! It didn't show the error.
I have a Titanium backup for all my apps and I also have a nandroid backup for my previous ROM (in my memory stick using an OTG cable). However, I don't have any backups for my internal storage (photos, videos, documents... etc). I am guessing that these files are still in my internal storage. I didn't copy any new files to my phone because I think if I do, then the phone will keep replacing my old files (that I can't see) with the new ones.
My question is: Is there a way to get back these old photos and videos from the internal storage? Note that I didn't delete these files, but the phone can't read them. Also, I checked the nandroid backup that I have and the file system type of the previous ROM was EXT4. My current file system type is the same, EXT4.
Thank you for the help!
First post, sorry if this isn't the correct place to start the thread
Alright so I'm running resurrection remix 6.1.0 rom on my rooted oneplus 3T (android version 8.1.0)
The other day, I was trying to input a usb otg into my phone but it would not recognise. Searched all over the settings but there were no options for the usb otg (didnt seem like RRemix supported it)
Now what I did next was kinda stupid on my part, so after searching over the internet and various forums, I tried two approaches
First one was to go to the terminal, entered 'su' to get root access and entered 'sm set-force-adoptable true'
Now I'll admit that I didn't know what this command was at that time, but it still didn't make my phone recognise the otg usb
Next I installed the StickMount app from playstore, mounted the mass storage, but again didnt make my phone recognise the otg usb
But then the problems started to arise, and note that I had enough internal storage (60%)
First I couldnt update some apps (says not enough storage while 11% through download)
Couldnt take pictures nor screenshots (again says no storage)
Also couldnt delete any files Ive downloaded through the default file app ( but can delete any apps)
However I could still download new apps or new files from the internet
So I'm guessing I stuffed up the SD card/ internal storage systems. I was thinking of flashing the RR rom again and starting the phone fresh but that would be a waste of time as I have to set up everything again
I have also tried the command 'sm set-force-adoptable false' but no success
So I'm wondering, are there any ways of undoing whatever I just did, without having to wipe everything and restart??
Thank you so much for any replies, I'll make sure to know what I'm doing in the future before I follow instructions on the net haha
also just curious, but would greatly appreciate if someone could tell me what I just did, searched over the internet but couldnt find a precise answer. My phone also does not have an external SD card
What you did was tell the device to use an external storage device as part of the Interminal storage.
You will have to start over from scratch. Make sure to back everything up.
What you want to do is part of their closed sources rom. I have never had a single aosp based roms with otg.
Sent from my SM-G955U using Tapatalk
zelendel said:
What you did was tell the device to use an external storage device as part of the Interminal storage.
You will have to start over from scratch. Make sure to back everything up.
What you want to do is part of their closed sources rom. I have never had a single aosp based roms with otg.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Ah I see what hapenned, thanks for your reply!
Luckily I decided to do a reboot and super glad it fixed everything. Camera app works perfectly and my phone can recognise my storage again
Hi all. Apologies for the wall of text, I have a few questions following all of the background below.
Device info: Samsung Galaxy S7 32GB running LineageOS 16.0, NOT rooted; SD Card in question is a 128GB Sandisk MicroSD. All commands being run on computer running Ubuntu 19.10.
Yesterday, my phone gave me the "SD Card Missing" notification suddenly, and in the settings it said it was corrupted. I had had it set up as adopted storage, so it isn't a matter of just losing photos and such unfortunately - it seems as though there's important app and system data on it.
After trying several recovery programs to no avail, I came across this thread:
https://forum.xda-developers.com/general/help/corrupted-sd-card-adoptable-storage-t3801250
Which is very similar to my situation. Unfortunately I didn't find a fix here, but I did manage to make a full .img copy of the card itself, and find the encryption key at "/data/misc/vold/expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key" as per https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html . The problem I ran into with this guide was that I couldn't get the dmsetup command to work. However, when reading the comments of the post to see if anyone else had the problem, I saw someone mention retrieving the files through TWRP. So, I put the card back in the phone, and booted into TWRP.
In TWRP, I was able to browse through the SD Card perfectly normally with the file manager, despite the fact that it still read as corrupted when booting back into the system. So, I used adb pull (side question on this later) to retrieve the folders I was most worried about - largely what I could find of app data, my photos and videos, etc. I did not just pull the whole card at once, and I'll elaborate on why when I get to the side question about adb pull.
So, here are my questions:
1. Is it possible to mount this SD Card back to normal through TWRP? If so, how? I'd like just enough so that I can restore my apps as is onto the phone, and then convert the card to portable storage to avoid this mess again. While I do have the data pulled, it's little things like NewPipe playlists that I've got in mind here.
2. If above is not possible, how much loss am I looking at if I choose to 'forget' the adopted card? Will I have to do a factory reset?
3. (adb) When doing the adb pull, it was unable to skip any files it couldn't copy - i.e. corrupted images - and would simply stop on finding one. This means that, for example, in one folder it hit a corrupted file after 3400 successes, and stopped without copying the remaining 300. Naturally, if I had just done 'adb pull /external_sd/', then I probably would have lost a lot more because of this. Can I add any options to the command adb pull to circumvent this? I was unable to find any decent documentation on the command, but maybe I was searching for the wrong thing.
Any and all help is much appreciated, thanks in advance!
johnfr92 said:
Hi all. Apologies for the wall of text, I have a few questions following all of the background below.
Device info: Samsung Galaxy S7 32GB running LineageOS 16.0, NOT rooted; SD Card in question is a 128GB Sandisk MicroSD. All commands being run on computer running Ubuntu 19.10.
Yesterday, my phone gave me the "SD Card Missing" notification suddenly, and in the settings it said it was corrupted. I had had it set up as adopted storage, so it isn't a matter of just losing photos and such unfortunately - it seems as though there's important app and system data on it.
After trying several recovery programs to no avail, I came across this thread:
https://forum.xda-developers.com/general/help/corrupted-sd-card-adoptable-storage-t3801250
Which is very similar to my situation. Unfortunately I didn't find a fix here, but I did manage to make a full .img copy of the card itself, and find the encryption key at "/data/misc/vold/expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key" as per https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html . The problem I ran into with this guide was that I couldn't get the dmsetup command to work. However, when reading the comments of the post to see if anyone else had the problem, I saw someone mention retrieving the files through TWRP. So, I put the card back in the phone, and booted into TWRP.
In TWRP, I was able to browse through the SD Card perfectly normally with the file manager, despite the fact that it still read as corrupted when booting back into the system. So, I used adb pull (side question on this later) to retrieve the folders I was most worried about - largely what I could find of app data, my photos and videos, etc. I did not just pull the whole card at once, and I'll elaborate on why when I get to the side question about adb pull.
So, here are my questions:
1. Is it possible to mount this SD Card back to normal through TWRP? If so, how? I'd like just enough so that I can restore my apps as is onto the phone, and then convert the card to portable storage to avoid this mess again. While I do have the data pulled, it's little things like NewPipe playlists that I've got in mind here.
2. If above is not possible, how much loss am I looking at if I choose to 'forget' the adopted card? Will I have to do a factory reset?
3. (adb) When doing the adb pull, it was unable to skip any files it couldn't copy - i.e. corrupted images - and would simply stop on finding one. This means that, for example, in one folder it hit a corrupted file after 3400 successes, and stopped without copying the remaining 300. Naturally, if I had just done 'adb pull /external_sd/', then I probably would have lost a lot more because of this. Can I add any options to the command adb pull to circumvent this? I was unable to find any decent documentation on the command, but maybe I was searching for the wrong thing.
Any and all help is much appreciated, thanks in advance!
Click to expand...
Click to collapse
Hey...did u get dmsetup to work?