Update 2:
So now I can see most of the files with ES, but OI file manager isn't seeing them. What the heck is going on? Ghost files?
Alright, so I'm in a bit of a pickle.
I was having problems with Rdio and wanted to wipe all traces of it from my phone to install an older version. Using ES File Explorer, I searched for all the files related to the app in "/" and once I found them, I foolishly used select all and delete. Problem is, it seems "select all" actually selected all the folders in / and not only those found using the search function.
The odd part is I can see all the folders in / when I use OI file manager (though some are empty, namely /data and /datadata), but not when I use ES.
Does anybody have an idea as to what I can do? Odd thing is the phone is working fine and not all files on it have been deleted (the files inside EFS seem to have been though, but I still have signal). I'm afraid to reboot it since I figure it might become bricked. I've got a recent Nandroid backup which wasn't deleted, so I'll be fine if I can get to recovery, but is there any chance of that not happening?
Anyways, I'm feeling really dumb and stressed out.
Thanks for looking and/or helping!
Cheers!
Update
Making a call seems to have restored the files (.bak and others) in the efs folder and some other files seem to be reappearing. Maybe if I just wait it out all the files will come back from the dead? Files that weren't showing 10 minutes ago are back and are dated earlier than today.
Again, I'm mainly looking to know if I can reboot into recovery (or normally?) without many problems.
Thanks!
Related
Hi guys,
Ok, so I've been Googling like a mofo for the past 3-4 days, trying this and that, investigating my issues, and I still need some help.
I've got a Bell I9000M that I would describe as the following:
1) Boots into any rom I flash via Odin (so far just GB and Froyo)
2) Internal SD works (I can see my files via USB), but "Internal Storage" shows unavailable.
3)I also flashed this phone before backing up my EFS folder so my unlock number is scrambled. I have a backup of the post unlocking-attempt EFS folder, but am unable to copy this back to where it needs to be. I've tried with ADB and no dice and I've tried copying it in with the phone on using Root Explorer - Root Explorer will copy the files back (and I'll even get the no SIM icon after a few minutes), but everything's gone and the EFS folder is empty when I reboot.
I'm kinda stuck. I just got this phone off CL last week thinking I'd flash it and go on my merry way like I normally do. I wasn't aware of the I9000M's horrid reliability. Anyway, any help would be appreciated!
ch0g0nda said:
Hi guys,
Ok, so I've been Googling like a mofo for the past 3-4 days, trying this and that, investigating my issues, and I still need some help.
I've got a Bell I9000M that I would describe as the following:
1) Boots into any rom I flash via Odin (so far just GB and Froyo)
2) Internal SD works (I can see my files via USB), but "Internal Storage" shows unavailable.
3)I also flashed this phone before backing up my EFS folder so my unlock number is scrambled. I have a backup of the post unlocking-attempt EFS folder, but am unable to copy this back to where it needs to be. I've tried with ADB and no dice and I've tried copying it in with the phone on using Root Explorer - Root Explorer will copy the files back (and I'll even get the no SIM icon after a few minutes), but everything's gone and the EFS folder is empty when I reboot.
I'm kinda stuck. I just got this phone off CL last week thinking I'd flash it and go on my merry way like I normally do. I wasn't aware of the I9000M's horrid reliability. Anyway, any help would be appreciated!
Click to expand...
Click to collapse
use the solutions on Quick fixes and solutions link below, especially the guide on how to make efs stick after reboots
Ok, so I did the making the IMEI/efs stick and it seems to have rectified everything for me! IMEI is back to what it should be, baseband is back, storage reads properly. Wow! I'm ecstatic right now! I've been dicking with this thing since last Friday and you've got me sorted in under 10 minutes, brilliant!
If you ever pass through British Columbia, let me know! I'll buy you a beer or something
Thanks again!
Hi,
Ive always used CWM to make my recoveries. But now, with Nexus 7 (CWM touch 6.0.1.9), Im unable to locate the backup files. There is no BACKUP folder in the clockwork folder and while I did a search using google and found many answers for my question, none of them was right. And I didnt make update from 4.1.2 - I cleaned the whole device and flashed stock 4.2.1 via fastboot, so I dont believe there is some directory tree change mess. And there is no BLOBS folder either.
I just flashed the ROM, rooted it using Toolkit, flashed CWM, made a backup - and boom, nothing there, while it is visible in both CWM recovery and ROM manager. I tried renaming the backup in ROM manager and searching for its new name using File Manager (with root privileges), but I was unsuccessful ...
So, please help me or provide me with a relevant link as I dont like TWRP ...
EDIT: I deleted the /SDCARD/CLOCKWORK folder and flashed TWRP. Now, I returned to CWM, made a backup using CWM and not only I dont see the backup itself, it didnt even recreate the CLOCKWORK folder. I just made a full search in the whole filesystem and there is nothing with "clock" in name (nothing relevant). Where is the backup hidden?????
Tried using it today. Its in some God forsaken rabbit hole. First enable root in es file explorer settings. Then look in system for data, media and eventually clockworkmod. That's the help I can give u.
Sent from my Nexus 7 using xda app-developers app
r3a1ist said:
Tried using it today. Its in some God forsaken rabbit hole. First enable root in es file explorer settings. Then look in system for data, media and eventually clockworkmod. That's the help I can give u.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but that not the place for me. /data is empty and the only folder found containing "clock" in the file structure is /sstorage/emulated/0/clockwork ... the same as /sdcard/clockwork I was talking about. only three small files and thats it, no BACKUP or BLOBS.
GOT IT!!! I dont know why it wasnt visible with rooted File Manager, but I tried ES and its there ... bam ... THANKS A LOT!
Now, whats the best way to save this stuff to a computer?
its because Jellybean 4.2 uses diff storage paths...
Android 4.2 significantly changes the way how sdcards are handled internally, your data is moved from /sdcard/ into /sdcard/0 on first boot (0 is the 'home directory' of the default user). If you go back to 4.1.2: Don't forget to move the data in 0/ back to the root of your sdcard.
Click to expand...
Click to collapse
Ather said:
its because Jellybean 4.2 uses diff storage paths...
Click to expand...
Click to collapse
Well, Im aware of that. But that doesnt explain why the files are under /data/media/clockwork. Neither it does explain why it wasnt shown/found by File manager with root privileges - although I guess its the problem of the File manager, as ES File Explorer sees that without any problems ...
Now, I switched CWM to save to TAR and made a backup. It created a folder "/data/media/clockwork/backup/2013-01-08-1214" with 9 files, size about 1,1GB. Is it sufficient for me to copy this file to my computer? Im talking about backing up the backup (heh) ...
Also, is it ok that files cache.ext4.tar, data.ext4.tar and system.ext4.tar are 0mb? Thanks!
EDIT: I tried moving a backup folder to my pc, making factory reset, copying it back to where it was and restoring - everything works fine. Although I dont get why google messed the sw insides so much - my Nexus S seems to be much better in the matter of directory tree - and doesnt wipe all my files when doing stock restore from PC ...
Hey guys, big problem here.
I was backing up, preparing for the 4.3 upgrade. I was cleaning some files off the storage using my pc, including the weird storage folder that only contained (more) titanium backup stuff.
Well, next thing I know, my phone doesn't see any of my files anymore. They're not there on PC now either, and no root-enabled file manager can see anything. However, 9gb of space is still being used by "other"!
Please help!
If it helps, I think I broke the symbolic links. Any solution? Or have I screwed this?
There might be an adb pull command to grab all files in /media. However I don't know the full syntax. Google adb pull sd card and you should hopefully find the correct command. You might have to play with the path a bit to get it right. It's something like /data/media/ on the One.
I'm not close to a pc so can't see what it should be.
Sent from my HTC One using Tapatalk 4
No luck. After major research online, the files are gone - I'd have to use recovery software after performing a very long backup in order to retrieve, and there wasn't that much that I lost since the last backup, a few photos just.
More a pain in the ass really. I never would have thought that those directories could do that. Kinda dangerous.
(accidental double post)
I was trying to cleanup carrier bloatware off my phone and I think I deleted some apps that were critical.
I deleted ItsOnService.apk (NetworkSystemProvider) and ItsOnUID.apk. Unfortunately I didn't make a backup of them. Then, wifi and LTE/3g stopped working (even if Wifi is connected, internet is permanently not available).
The worst part of this is that the issue persists after reflashing back to stock. The problem is I don't think the stock roms contain the /carrier directory. And now I cannot complete the setup wizard because at first boot, I'm forced to select a wifi network and once I connect internet is not available, so the wizard won't proceed.
Is there anything I can do? If someone were to send me the missing APKs could I use recovery mode and sideload them?
Chanman said:
I was trying to cleanup carrier bloatware off my phone and I think I deleted some apps that were critical.
I deleted ItsOnService.apk (NetworkSystemProvider) and ItsOnUID.apk. Unfortunately I didn't make a backup of them. Then, wifi and LTE/3g stopped working (even if Wifi is connected, internet is permanently not available).
The worst part of this is that the issue persists after reflashing back to stock. The problem is I don't think the stock roms contain the /carrier directory. And now I cannot complete the setup wizard because at first boot, I'm forced to select a wifi network and once I connect internet is not available, so the wizard won't proceed.
Is there anything I can do? If someone were to send me the missing APKs could I use recovery mode and sideload them?
Click to expand...
Click to collapse
do you still have the rooted system image on ur sdcard?? just reroot
Google~Android said:
do you still have the rooted system image on ur sdcard?? just reroot
Click to expand...
Click to collapse
I do have the rooted image, as well as the stock image, I have applied both, the problem still exists. I think when I reroot or reflash it's not writing the /carrier directory, that must have come from somewhere else. I confirmed this by unpacking the TOT file and looking inside, it has all the apps, but it does not have the /carrier directory. Do you have ItsOnService.apk and ItsOnUID.apk? Maybe I could try sideloading them?
Chanman said:
I do have the rooted image, as well as the stock image, I have applied both, the problem still exists. I think when I reroot or reflash it's not writing the /carrier directory, that must have come from somewhere else. I confirmed this by unpacking the TOT file and looking inside, it has all the apps, but it does not have the /carrier directory. Do you have ItsOnService.apk and ItsOnUID.apk? Maybe I could try sideloading them?
Click to expand...
Click to collapse
nope i don't have a g4 as of now...shud be here in a week
Chanman said:
I was trying to cleanup carrier bloatware off my phone and I think I deleted some apps that were critical.
I deleted ItsOnService.apk (NetworkSystemProvider) and ItsOnUID.apk. Unfortunately I didn't make a backup of them. Then, wifi and LTE/3g stopped working (even if Wifi is connected, internet is permanently not available).
The worst part of this is that the issue persists after reflashing back to stock. The problem is I don't think the stock roms contain the /carrier directory. And now I cannot complete the setup wizard because at first boot, I'm forced to select a wifi network and once I connect internet is not available, so the wizard won't proceed.
Is there anything I can do? If someone were to send me the missing APKs could I use recovery mode and sideload them?
Click to expand...
Click to collapse
You need to know exactly what you deleted. The itsonuid is in the system/priv-app directory. I didn't see the itsonservice but didn't spend much time looking. You need to know if you deleted things out of carrier partition or vendor partition or both... Get a list together...
Agimax said:
You need to know exactly what you deleted. The itsonuid is in the system/priv-app directory. I didn't see the itsonservice but didn't spend much time looking. You need to know if you deleted things out of carrier partition or vendor partition or both... Get a list together...
Click to expand...
Click to collapse
Thanks, I can confirm what you're saying, I did find ItsOnUID in system/priv-app, so at least I can restore that one. However, I am pretty sure ItsOnService is in /carrier and I deleted it using ES File Explorer. I had deleted ItsOnUID with Titanium Backup. Titanium Backup was not able to find ItsOnService, so that's why I had used ES File Explorer, which confirms that ItsOnService must have been in /carrier.
Since it looks like there is no /carrier directory in these TOT files, is there some other way I can get ItsOnService.apk? Can anyone out there send it to me?
Chanman said:
Thanks, I can confirm what you're saying, I did find ItsOnUID in system/priv-app, so at least I can restore that one. However, I am pretty sure ItsOnService is in /carrier and I deleted it using ES File Explorer. I had deleted ItsOnUID with Titanium Backup. Titanium Backup was not able to find ItsOnService, so that's why I had used ES File Explorer, which confirms that ItsOnService must have been in /carrier.
Since it looks like there is no /carrier directory in these TOT files, is there some other way I can get ItsOnService.apk? Can anyone out there send it to me?
Click to expand...
Click to collapse
Might be a little late but here ya go.
2348z said:
Might be a little late but here ya go.
Click to expand...
Click to collapse
Thanks a lot!!!
Chanman said:
Thanks a lot!!!
Click to expand...
Click to collapse
No problem buddy. ?
Ive used my droid turbo for 18 month or so. I always enjoy the convenience of installing an app first and drag data into the obb folder under emulated/0/Android.
But yesterday, I can't find it anymore(all those app data is not lost). I wanted to create a new obb folder but the phone tell me that the folder already exists. When I connect the phone to my computers(both mac and windows), I still can't find the obb folder and as I drag in a blank obb folder that I've just created, my phone crashed and restart. I used shell to check permission and it turns out the folder is there and I have full permission to Read and Write. And I backed up my device and give it a wipe. But no luck.
So, I know that the obb folder is still there, but hidden. I think it may be the Es explorer since the problem happens after I used es explorer to clean app residue after deleting an app which could trigger the write protection?
So Im bit frustrated after working on the issue or this long. So Im asking you guys, have you ever run into issues like this? Is there a viable solution?
Are you rooted? If so, try Root Explorer to see if you can see it.
Wouldn't hurt to re-flash SuperSu again in TWRP, either.
On the droid turbo it was a pain to find this folder, went with some suggestions creating new one, copying the whole folder. etc none worked, I gave up on the phone at that time also bootloader was locked, I went with moto maxx, what a ease
siberian85 said:
On the droid turbo it was a pain to find this folder, went with some suggestions creating new one, copying the whole folder. etc none worked, I gave up on the phone at that time also bootloader was locked, I went with moto maxx, what a ease
Click to expand...
Click to collapse
you are saying the problem is solved with an unlocked bootloader?
ChazzMatt said:
Are you rooted? If so, try Root Explorer to see if you can see it.
Wouldn't hurt to re-flash SuperSu again in TWRP, either.
Click to expand...
Click to collapse
Sadly, I haven't rooted my device yet....any alternatives?