Used Clockwork, but I used Odin to flash the kernel afterwards and now I'm not sure what file system it's using. Can I check what it's using anywhere?
Thanks!
Connect to your PC and open adb shell, or download a terminal emulator, and type:
mount
If you see EXT4, it's EXT4. If you see RFS, it's RFS.
If you flashed a stock kernel via Odin, however, and your phone is working, it's RFS. Additionally, if it's CWM2.5 you have, not CWM3, it's RFS.
Also the first time you boot into Clockwork if it is 3.x it will start the conversion process to EXT4. It takes a few minutes for that so it is hard to miss.
Related
My USB port is broken for some reason. It only charges. The data lines seem to be messed up because I only get "unrecognized usb" errors when I plug it into the computer.
Anyways, I currently have ClockworkMod recovery installed and I would like to restore it to the stock recovery. Without the usb port is there a command I can use in "terminal emulator" that can flash the recovery? I have root access.
Thanks.
i dont think that,s possible. this is a stupid Q but did try diff cable.go to ClockworkMod and mount your usb there. what Rom are u using stock or custom..
Mobin Odin.. until chain fire release a version for our phone...
^^only way. and could brick your phone...good luck!
datzstr8 said:
My USB port is broken for some reason. It only charges. The data lines seem to be messed up because I only get "unrecognized usb" errors when I plug it into the computer.
Anyways, I currently have ClockworkMod recovery installed and I would like to restore it to the stock recovery. Without the usb port is there a command I can use in "terminal emulator" that can flash the recovery? I have root access.
Thanks.
Click to expand...
Click to collapse
Yes, it's possible. You need to have the .img file (not cwm flashable zip, if you only have the zip extract the recovery.img out of it, and copy it to your sdcard. There are many ways to do this wirelessly. Airdroid, wireless adb, cifs, etc. )
For this example, I'm going to assume the image file is named recovery.img, and is located on the root of your sdcard (/sdcard, depending on your install this'll be internal or external sd card, stock based roms it'll be internal). Go into the terminal, type su, hit enter. Make sure you give it root access. Now type the following:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
The actual usage is :
dd if=location of image of=/dev/block/mmblk0p22 (that is the location of our recovery partition)
Be careful here, especially with the /dev/block/mmcblk0p22 part, flashing the recovery to the wrong location, depending on the typo, can definitely hard brick your phone.
Hopefully that gets you going. Good luck.
If you encrypt your phone using ICS encryption on CM9 for example then you can't just put in a password to turn off the encryption feature like you can on a Samsung rom. Today my phone was completely unusable because I couldn't boot into recovery or Android, reverting to stock with Odin would make my phone hang at the Samsung logo when booting Android. We're going to flash a new recovery using Odin and format your /data partition so that you can mount your internal and external SD cards once again so your phone is usable.
Software required:
Odin
ADB
Files:
Odin
http://samsung-updates.com/Odin307.zip
Flashable CWM Recovery
https://www.dropbox.com/s/ukx3l58wpcb3h4b/connor.tar.md5
Open Odin and make sure Auto Reboot and F. Reset Time are checked, click PDA and open connor.tar.md5 then flash the phone.
Once the recovery is done flashing and your phone is rebooting remove the battery from your phone. Replace the battery and hold volume up, home (center button) and power. Once the Samsung logo appears release the power button and your phone will boot into recovery. From here we are going to format our data partition.
Start an adb shell.
Linux:
/android-sdk-linux/platform-tools/adb start-server
adb shell
Windows:
Open a CMD window in your ADB folder (shift click and click open new command window).
adb shell
From here we are going to format our data partition.
cat /etc/recovery.fstab
If /data is mmcblk0p15 then everything is going as planned.
mke2fs -t ext4 /dev/block/mmcblk0p15
What that command will do is format your /data partition.
mount /data
mount
You should see /dev/block/mmcblk0p15 mounted on /data
Flash a new rom and your broken phone is now usable.
Credits to koush for CWM and utkanos for helping me with the process.
Thanks for the info. However it seems to me that the encryption causes more problems than it helps. I've seen too many posts about how implementing encryption ends up screwing someone. But I've never seen a post that said...wow I am sure glad that I encrypted my phone! Let's face it...unless u are working for the government or the like...there's no need for it. And if u are working for the government, they will have some I.T. guy handling it for you. Its best to leave it alone and password protect your phone / files / data and then u wouldn't have to deal with the above steps.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
My friend runs his Galaxy Nexus rooted with no custom rom and has his phone encrypted because he's strange like that (when googling about illegal stuff he always uses an incognito browsing session), he's just paranoid I suppose. I encrypted mine just because I could without thinking that something like this could occur. There was absolutely no information on the internet about how to undo the encryption and this is the only possible way I know.
Hi, This is my first forum after study here for some time.
And I need a little help from my fellow XDA members here.
My issue happens when I flashed Devil 2 Kernel and managed to
formatted to F2FS file system with his instruction.
Then I decided to try another kernel, so I try to re-formatted file system back to ext4
which is worked fine until I reach the last step of formatting (I am not very sure about the text
but it seems like "format /sdcard and ...something i can't remember...")
and it just restarted itself and got stuck in a bootloop
Now I tried to fix that by..
- Installing another recovery, TWRP, it just shows splash screen in a loop. No Luck
- Try to make Devil Recovery zip file to be flashed by Odin. No Luck
...I have this error message...
$ tar -H ustar -c recyovery.img > recovery.tar
tar: recovery.img: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
- Force-flashed whole stock rom that I downloaded from sammobile.com via Odin. No Luck
It just stuck at "Getting PIT for mapping" forever.
All of them are just don't work for me.
So I kindly as XDA members here what I can do with this situation.
or at least.. How can I (properly) convert .zip file to .tar.md5 ??
Thank you very much.
not sure why would you want to convert zip to tar ? why do you need that ?
Have you considered reformatting the device partitions through adb ? I have never done this before but I think it should be possible
edit : you need to use the latest TWRP, anything before 2.7.0.0 had problems with f2fs, just in case you were trying an older version.
ticktock666 said:
not sure why would you want to convert zip to tar ? why do you need that ?
Have you considered reformatting the device partitions through adb ? I have never done this before but I think it should be possible
edit : you need to use the latest TWRP, anything before 2.7.0.0 had problems with f2fs, just in case you were trying an older version.
Click to expand...
Click to collapse
I don't know why, but I can't flash both TWRP 2.7.0.0 or Devil Recovery itself via recovery mode.
So I wanted to try if the result is the same if I flash it via Odin
But I interested in formatting my device through ADB. How ?
Because I can't enter recovery mode, and I have no system to boot into.
Sorry for this seems-to-be-noob question, but I really can't find the way.
PS. From my little understanding, PIT file can be used to partition my phone in Odin, right?
But will it play any role in this situation? Just curious...
download the tar version of twrp from their site and flash it through odin, see if that works
Hi I was wondering if someone could help me.
My dad's phone which is a S3 somehow soft bricked itself. It was on a stock rom before.
It turns on and then gets stuck on the Samsung Galaxy SIII screen.
I am able to boot into download mode as well as recovery.
I was able to flash a stock ODIN file UVUEMJC as well as the PIT file and everything went smoothly and it passed.
However, the same problem remains, it is still stuck on the Samsung Galaxy SIII screen when I boot it.
Also went into recovery and tried to wipe data, but it is unable to mount any partitions, e.g. can't mount cache, can't mount data, etc.
I was able to throw on TWRP and boot into that, and it gives me similar errors as the stock recovery. TWRP also says that my internal storage is 0 GB and I can't put any files onto the phone.
I am quite confused because if NAND was corrupted then I shouldn't I not be able to boot into recovery at all?
ADB is also working...can't push/pull anything though.
If someone could help me I would really appreciate it. Thanks.
So I flashed CWM cause I read on XDA someone said that formatting data through CWM works, now...it says there is no pit partition and there is a flash read failure whenever I try to flash a stock tar with odin w/ pit. Also tried flashing pit by itself, doesn't work.
Try installing cwm or twrp again, boot into recovery, mount sdcard0, connect to Windows machine, and try to format the partition using fat32.
I bought a new never used Tab 3 for the intended purpose of using it as a universal remote. I wanted to strip it down and started right away with installing custom recovery, or at least I tried. No matter what I did I was not able to get Odin to properly load TWRP. It went through all the steps but I was not able to get into recovery other than stock.
Fast forward to the next day, I finally get it to work and somewhere in this process I somehow deleted or unmounted (I really am not sure) my efs folder/partition. If I try to reset deleting all cache and wiping everything including pulling the battery for a few minutes and flashing the stock ROM again I get hung up at the "SAMSUNG' logo. I have tried several ROMs and even tried using Odin to flash a new pit file with I found HERE. When I load both the pit file and my ROM into Odin it eventually says 'FAIL'. I can flash ROMs all day with no issue.
I can only assume that the error I am getting in recovery that says E:failed to mount /efs (Invalid argument) is my issue.
Adb is not really an option for me since I have little to none, more like none at all knowledge of using it. I assume since I have flashed several tries that USB Debugging is not enabled anyway and isn't enabling it key to using ADB anyway?
I have been at this for 2 full days searching everywhere and trying everything I see. I am at a loss and hate to think this new Tab is already junk.
Any help would be greatly appreciated!
The EMCC or something like that requires replacement
andynroid said:
The EMCC or something like that requires replacement
Click to expand...
Click to collapse
So I should junk it then? I only paid $80 for this Tab.
One trial you may try to flash a Cyanogenmod based ROM see if it can write out the partitions else if no luck time to replace that item as mentioned
I have tried flashing CM and still the same issues.
I have since found out what my issue is (or at least 99% sure), I somehow wiped out my efs partition completely. So running a new pit file with Odin does nothing because the partition is gone.
This is fixable and easy for someone who knows shell, but I don't. So now I am trying to figure it out. It's a matter of pushing the 6 following files to the phone using the adb push [file] /sbin/ command using adb which I have done, now I need to figure out the rest.
e2fsck
mke2fs
parted
resize2fs
sdparted
tune2fs
T
you can't do that in the way you think, it requires disassembling the recovery image, making modifications and repacking then reflashing the image.
If you are using an older recovery, namely twrp, install a newer recovery , check @nels83 's thread for a "modern" twrp build.
You can also try one of my philz builds.
Being as you have been abusing Odin, you may actually have damaged your tab.
BUT if you are connecting to wifi without a problem then it's unlikely that you have damaged your efs partition. It's more likely an error with the recovery build you are using, probably in the fstab.
m