How to break ICS encryption to save your phone. ATT -d2att ONLY - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

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.

Related

[Q] Shattered screen & backup (solved)

Hi everyone, for Christmas my screen was crushed by a car .
The screen is completely destroyed (both touch screen & display screen).
However the phone is booting, so I can put it in recovery mod (I rooted the phone and I have clockworkmod).
After many trials, I succeeded in having adb connecting to my phone in blind mode.
I did this:
Code:
adb mount /data
adb pull /data /a_backup_folder
adb mount /system
adb pull /system /another_backup_folder
... and copied back my SD to my computer. I plan to buy another Desire and to revert the instruction by issuing a push for the data & system. This is:
Code:
adb mount /data
adb push /a_backup_folder /data
adb mount /system
adb push /another_backup_folder /system
Will it work ? Or is the system in sync with the flashed firmware ?
Can I selectively push some of the folders (namely applications, and the whole data). I hope to get back my settings, contacts etc...
I'm afraid I cannot do a whole lot more, since I do everything in blind mode.
Any advice on this ?
Thank you !
Just make a nandroid, should be able to restore as long as you don't have a different screen version (AMOLED to SLCD) but not 100% sure.
TheGhost1233 said:
Just make a nandroid, should be able to restore as long as you don't have a different screen version (AMOLED to SLCD) but not 100% sure.
Click to expand...
Click to collapse
Thank you for your suggestion.
Can I do it even if I do not have a screen ? I've tried to launch it but I fear it needs busybox (it says that it cannot find nc) and I think I do not have it (and don't know how to put it without the screen).
What are the supplementary steps that nandroid does ?
This is for CWM 2.5.0.7.
Sorry mist the part that you have to do everything blind, when in recovery press 5 times down on the volume rocker and then 2 times on the OJ let it sit for 10 min, should be done sooner but i don't know how to check if it's finished. After 10 min press once again on the OJ, your phone should reboot and in the Clockwork folder on the SD card should be a backup folder with a folder with the current date and time of the back up.
Unfortunately it did not work.
It did the steps as provided, and indeed the phone rebooted, but there is no clockworkmod folder on the sd card.
Is there any way to do a similar operation with adb ? This would be easier since when I'm in adb shell, I can type from the PC .
Try installing amon ra recovery. You should be able to do it. This is what the amon ra thread says:
Scripts available via adb :
* Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start.
Explenation: http://forum.xda-developers.com/showpost.php?p=3046976&postcount=1
I think that this is what you are looking for
Use the command below to find out what partitions each mtd is for (I don't remember)
cat /process/mtd
Then backup with
cat /dev/mtd/mtdx > /sdcard/mtd.img
(Replacing x with whatever number)
Get all the partitions you need, boot, cache, data and system. Then flash to your new phone from fastboot.
fastboot flash boot mtdx.img
You might want to get hold of a tool called unyaffs and take a look inside the images you make to check its all ok before you bin your old phone or send it back.
mercianary said:
Use the command below to find out what partitions each mtd is for (I don't remember)
cat /process/mtd
Then backup with
cat /dev/mtd/mtdx > /sdcard/mtd.img
(Replacing x with whatever number)
Get all the partitions you need, boot, cache, data and system. Then flash to your new phone from fastboot.
fastboot flash boot mtdx.img
You might want to get hold of a tool called unyaffs and take a look inside the images you make to check its all ok before you bin your old phone or send it back.
Click to expand...
Click to collapse
Ok the first step worked, but unyaffs does not want to open my imgs.
The size are as follow:
Code:
3*145*728 boot.img
3*145*728 boot_ro.img
41*943*040 cache.img
41*943*040 cache_ro.img
655*360 misc.img
655*360 misc_ro.img
4*718*592 recovery.img
4*718*592 recovery_ro.img
262*144*000 system.img
262*144*000 system_ro.img
154*796*032 userdata.img
154*796*032 userdata_ro.img
which seems good (I also made images from the mtdXro). However I should be able to extract userdata and system from my understanding. I tried with unyaffs both on linux and on windows, on both I get a segmentation fault.
Do I have a way to verify that theses images are good ? I do not want to trash the new phone I will buy with a faulty image...
Flash the same rom from recovery on your new phone, then flash the data image from fastboot, if it works the first boot should take a while as it builds the cache. If it doesn't work just clear data and it wont have done any damage to your new phone.
You will have to zip the data image before you fastboot flash it because it's too big for fastboot to receive.
If you have s-off on your old phone I would flash amon-ra recovery from fastboot then use the nandroid script over adb.
As long as you don't try to flash the recovery you backed up I don't think there's any chance of damaging your new phone doing this.
Ok the final solution was to use the new phone (rooted and with clockworkmod) as a reference.
I did the same backup sequence on the two phones, and have been able to restore the backup on the new phone.
Thank you everyone for your help !
Glad you got it sorted...don't drop your phone under a car again.
Sent from my HTC Desire using XDA App

[Q] CWM can't delete data lg nitro hd

There doesn't appear to be anyone that has this problem, and I wasn't able to find anything in the development forum for CWM.
Per what everyone says, can't format /data or "factory reset" in CWM due to some sort of partition thing.
1. I boot to CWM
2. I go to mounts and storage and unmount /data
3. I plug the usb into the computer
4. Open Command Prompt and go to the adb directory
5. Enter Command adb shell and opens ~# at least that is what it looks like
6: I type "/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p30"
7: the response "/sbin/sh: /sbin/mke2fs_static: not found"
What am I doing wrong?
Edit: I figured it out. I ended up having to reinstall practically everything. But it worked
1 Loaded backed up rom from cwm
2 reinstalled adb
3 copied the backup recovery image back to it's original place.
4 factory reset
5 copy the cwm back
6 boot to recovery mode
7 adb commands work!!!
edit: I really should learn better grammar. I cleaned the wording up a bit.
edit2: I solved my own problem
The command not being recognized was a result of not having the latest CWM from bytecode installed. He updated it from his initial release to add support for these commands. Glad you figured it out! It can be frustrating when stuff like that happens.
Personally I'm avoiding CWM all together at this point. It's been almost a month with not a single problem (besides the BT incident) with no CWM installed, no boot loops, no reboots. There is something seriously wrong with current CWM...
[email protected] said:
Personally I'm avoiding CWM all together at this point. It's been almost a month with not a single problem (besides the BT incident) with no CWM installed, no boot loops, no reboots. There is something seriously wrong with current CWM...
Click to expand...
Click to collapse
You are right, i brick my phone today.
I was lucky that Bell change it for a brand new.
Rom development is not that safe with a so bad recovery...
HO!NO! said:
You are right, i brick my phone today.
I was lucky that Bell change it for a brand new.
Rom development is not that safe with a so bad recovery...
Click to expand...
Click to collapse
Indeed, but I have been ok since not touching /data via CWM. The manual format of /data works fine. I have flashed my own ROM zips over 20 times without issue.
Sent from my LG Nitro HD
[email protected] said:
Personally I'm avoiding CWM all together at this point. It's been almost a month with not a single problem (besides the BT incident) with no CWM installed, no boot loops, no reboots. There is something seriously wrong with current CWM...
Click to expand...
Click to collapse
I still feel CWM is a very important safety net if anything goes serious wrong ( I saw there is some download mode, but I still feel cwm is much easier to use than download mode).
For example, if you phone /system messed up, how do you fix, you only have download mode, right? If you have cwm, you will have one more option.
HO!NO! said:
You are right, i brick my phone today.
I was lucky that Bell change it for a brand new.
Rom development is not that safe with a so bad recovery...
Click to expand...
Click to collapse
I saw these unfortunately case several times in this forum, even though I never met for my self ( I following instructions never touched /data), so when you say brick, what happen exactly? Can you boot into cwm?
gte460z said:
The command not being recognized was a result of not having the latest CWM from bytecode installed. He updated it from his initial release to add support for these commands. Glad you figured it out! It can be frustrating when stuff like that happens.
Click to expand...
Click to collapse
I figured I just had a bad install. Because I think the version was the same...
but anyway, it was most definitely a fun experience.
I love CWM if it weren't for CWM I wouldn't be able to reset my phone. Which was way necessary...porting a new rom over existing data instead of a clean system caused some really interesting errors.
adb shell
umount /data
/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p30
/sbin/e2fsck_static -y /dev/block/mmcblk0p30
its working on LG SU640,you can try

/efs partition not being mounted

I just got a note 2 (i317m - canadian carrier model) that got messed up some how. When attempted to boot the phone it said unable to mount efs partition. My research tells me that partition that contains module info such as IMEI, bluetooth, wifi are stored in that partition. Now I realize why the repair guy wanted $350 to fix it.
Is there a way I can tackle this problem on my own and try and fix it? Apparently there is a tool here in XDA that can wipe the partition but I am not sure if that would rebuild it and allow me to mount it so I can create a new data file with the IMEI number in it.
Where should I start to attempt to fix the problem.
Please note, I can still access recovery (currently TWRP installed) and download mode and use ODIN if necessary to flash back a stock rom BUT can't mount to the computer for any file transfers nor can I boot the android device (stays at samsung logo). I have no issue using ADB is neccessary if I am lead in the right direction. This phone is already trashed in the eyes of the owner so its basically a little project for me to tackle when i have time to kill.
Bloodyskullz said:
I just got a note 2 (i317m - canadian carrier model) that got messed up some how. When attempted to boot the phone it said unable to mount efs partition. My research tells me that partition that contains module info such as IMEI, bluetooth, wifi are stored in that partition. Now I realize why the repair guy wanted $350 to fix it.
Is there a way I can tackle this problem on my own and try and fix it? Apparently there is a tool here in XDA that can wipe the partition but I am not sure if that would rebuild it and allow me to mount it so I can create a new data file with the IMEI number in it.
Where should I start to attempt to fix the problem.
Please note, I can still access recovery (currently TWRP installed) and download mode and use ODIN if necessary to flash back a stock rom BUT can't mount to the computer for any file transfers nor can I boot the android device (stays at samsung logo). I have no issue using ADB is neccessary if I am lead in the right direction. This phone is already trashed in the eyes of the owner so its basically a little project for me to tackle when i have time to kill.
Click to expand...
Click to collapse
Have you tried flashing your official rom? Flash your official firmware by downloading it from sampro.pl or sammobile.com, flash it with PC Odin under PDA tab.
After you done, don't let reboot your phone, goto recovery by pressing vol up+ menu key then power key(continuously hold it until your phone restarts might be 4~8 secs.) Then check 'Wipe Cache Partition', and then reboot phone.
Yup and nothing worked.
Anyone?
So the only solution is a $300 fix?

McAfee Livesafe Locked device

So a customer brought in a Tab3 to me with this horrible McAfee Livesafe software on it that had locked it.
it is asking for a pin, he is adamant that he never set this up.
you can't click "forgot pin" because it needs a data connection and I can't activate the data connection because the device is locked.
I have successfully flashed the device in Odin but it just starts up and lands back at the McAfee locked screen
Is there anyway around this ?
the customers data is not important and can be wiped.
smithbyrne said:
So a customer brought in a Tab3 to me with this horrible McAfee Livesafe software on it that had locked it.
it is asking for a pin, he is adamant that he never set this up.
you can't click "forgot pin" because it needs a data connection and I can't activate the data connection because the device is locked.
I have successfully flashed the device in Odin but it just starts up and lands back at the McAfee locked screen
Is there anyway around this ?
the customers data is not important and can be wiped.
Click to expand...
Click to collapse
do u have wipped data?
Danielito88 said:
do u have wipped data?
Click to expand...
Click to collapse
I'm not sure I understand you, i have flashed it already if thats what you mean
Flashing in Odin does not wipe user data. You need to boot into recovery and perform a factory reset to wipe the user data.
smithbyrne said:
I'm not sure I understand you, i have flashed it already if thats what you mean
Click to expand...
Click to collapse
Are you certain the device isn't stolen?
okay, if you can reflash the device with a good custom recovery, meaning being able to run adb shell as root for push/pull
and parted is built into the recovery, AND losing data is truly not an issue,
first try twrp for it's format data function which will wipe ALL of userdata. if nogo
try philz (more options) while in recovery connect via adb shell # and run
parted /dev/block/mmcblk0 --- wait for the prompt...
(parted)
then enter
print all
copy that output for reference, at the beginning of each line the number corresponds to the mmcblk0p##
note the block ## for cache and run
dd if=/dev/zero of=/dev/block/mmcblk0p[cache's block##]
then
reboot recovery
have a stock rom ready to flash or push to device's external card.
in philz format data and internal sdcard, flash rom and reboot.
if you still hit the lockout, something's living probably in /efs or /param.
param block on tab3 can be dumped or pulled via adb
via adb shell
dd if=/dev/block/mmcblk0p[param block##] of=/storage/extSdCard ---> your actual mount point may vary, adb pull off device
via adb [as root]
adb pull /dev/block/mmcblk0p[param block##] param.bin
param extraction and repackaging [works on tab3 10, note 10]
tar xf param.bin
look through it or just pull param from another known clean and correct model and replace
if there is something skunky and you can remove it, then to repack param.bin --make sure to move old param.bin out of $PWD
tar cf - `ls | sort -t.` > param.bin
then push back to device and reflash/write
dd if=/[$PWD]/param.bin of=/dev/block/mmcblk0p[param block##]
reboot
m
edit - remember to reformat cache through recovery

E:failed to mount /efs (Invalid argument), Did I brick my tablet?

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

Categories

Resources