Hey!
A friend of mine recently got her S2 bricked due to a faulty OTA update. She was prompted to install ICS, even though the network operator's branded version is not to be released for another week or so (2 weeks after the stock release).
Now the device won't start, and customer support says she needs to hand it over to reset the phone. Although this fixes the phone, she would like to keep her pictures etc. that is saved in the phones internal memory.
Is it possible to mount the /data partition (or /user or whatever) to a Windows PC, and recover the files? I do believe the phone can boot in recovery, and I am moderately experienced with using ADB.
Optionally, is it possible to "abort" the update, and reset the phone to it's previous state? I was thinking to wipe the cache partition, but i'd love your input on this matter!
--excubated
You could try flashing a GB rom via Odin. Or if you can, flash CWM recovery and mount the internal card (its sd_card, I think). Otherwise, I haven't a clue.
Sent from my GT-I9100 using XDA
Try Recuva
jje
JJEgan said:
Try Recuva
jje
Click to expand...
Click to collapse
Recuva is for deleted files (which also doesn't work too well on flash memory).
If she's got a custom recovery like ClockworkMod, skip to step 2.
Step. 1) download and install ClockworkMod recovery onto the device.
Step. 2) boot into CWM.
Step. 3) Go to Mounts and Storage.
Step. 4) Select Mount USB Storage.
Step. 5) Download (the .zip version) and extract the Android SDK.
Step. 6) Open a command prompt (CTRL+R, type cmd, hit enter).
Step. 7) CD to where ever you extracted to the SDK, like say C:\Android_SDK
Step. 8) CD to \platform-tools
Step. 9) In the command prompt, enter:
adb pull /sdcard/DCIM DCIM\
That should pull the camera folder. If there's photos outside that folder, try adb pull /sdcard SDCARD\
If you're looking to delete the photos, go back into Mounts and Storage, and hit format /sdcard.
But, if you can, as stated above, try flashing to a Gingerbread ROM and copying over like normal. A lot less hassle than the above.
screamworks.
Try It
excubated said:
Hey!
A friend of mine recently got her S2 bricked due to a faulty OTA update. She was prompted to install ICS, even though the network operator's branded version is not to be released for another week or so (2 weeks after the stock release).
Now the device won't start, and customer support says she needs to hand it over to reset the phone. Although this fixes the phone, she would like to keep her pictures etc. that is saved in the phones internal memory.
Is it possible to mount the /data partition (or /user or whatever) to a Windows PC, and recover the files? I do believe the phone can boot in recovery, and I am moderately experienced with using ADB.
Optionally, is it possible to "abort" the update, and reset the phone to it's previous state? I was thinking to wipe the cache partition, but i'd love your input on this matter!
--excubated
Click to expand...
Click to collapse
try using different ROM of any other country but of same Model no. (e.g. GT-I9100) in the downloading mode throug ODIN3. And formatting Cache partition will not change anything, but speed up the phone. firmware up gradation will not wipe your phone internal memory.
Hope it works for you....
Thanks for your answers so far, but I do believe flashing over any recovery or firmware will void the warranty on the device? She's not very eager to venture into the realm of warrantylessness, unfortunately ..
If whe was, she'd have had the MIUI ICS experience from the day it was launched Need to keep everything stock, and if there is no way to retrieve the files without voiding the warranty, she'd rather send it in and lose all her data..
screamworks said:
adb pull /sdcard/DCIM DCIM\
Click to expand...
Click to collapse
Can't I enter the normal recovery's terminal with adb shell? From there I mean to remember it is possible to mount and pull whatever I want..
Even without installing a custom recovery (CMW), the SGSII will allow you to go in to either Download Mode or Recovery mode. And I believe you should be able enter either mode even if the phone isn't booting up successfully (from a failed upgrade).
To enter recovery mode, you press and hold the Up Volume, Home Key and Power buttons.
To enter Download mode, you press and hold the Down Volume, Home Key and Power buttons.
You should be able to find the latest official/stock Gingerbread ROM in the forums here, and then you use Odin to install the GB ROM (from Download mode). This won't increase the count of "unofficial" Roms on the phone and shouldn't void the warranty.
While Odin is often referred to as a means to flash a custom ROM, it's not limited to only that. And the same for recovery mode. Most posts reference the CMW recovery that allows you to change to custom kernels and update "unofficial" packages on a rooted phone.
But you should still be able to revert back to a GB-based ROM and not void any warranty.
[if you boot the phone in to the official Samsung Download mode, it will display a message on the screen about the number of non-Samsung ROMs have been installed on the phone, and you should not see any number, or maybe "Zero"... I can't check to be sure because I forgot my phone in the office when leaving work today After you downgrade to GB, you can verify that the number is still blank or "Zero" by going back in to Download mode after you're sure the GB install was successful (it's not destructive to go in to Download mode just to view the counter. just power it off (as long as you're in the middle of pushing code to the phone ) and then reboot]
I'm not as experienced as a lot of the folks on the site, but everything I've outlined above I've done at least a few times on my phone (to custom ROMs, back to official, even resetting/clearing the "counter", and I've always been able to recovery from a "bad install").
I hope that helps,
Hey,
I am currently trying to help my best friends dad out. He dropped his GS2 during his holiday. Now the lcd is dead. The digitizer is not broken and seems to be working, as I get a feedback from the lockscreen when I tap on it, but I am having a small suspicion, that one half of the digitizer doesn't work anymore. The phone has a pin lock screen, it is not rooted and developer options are not turned on.
Is there any way to get access to the internal storage, and recover files from there? (He wants the pictures back he made on holiday )
Btw: I haven't owned any Samsung smartphone yet and I don't know how the recovery stuff works there so if there is a solution for this problem I would really appreciate a step by step tutorial. I have knowledge about rooting, flashing and stuff, so if it would be a solution to root the phone, I could do that, as my best friends dad doesn't want to repair the device anyways.
Greetings
Bl4ckX
Nobody any idea? :/
Sent from my HTC One X using XDA Premium 4 mobile app
Related
I'm selling my Droid Eris and want to wipe it so no personal information is stored on it. I'd also like to keep root and the Gingerbread ROM on it because the buyer would like 2.3. Is this possible? I'd like the phone to be so that when you turn it on, it brings you through the steps to activate your phone.
Any advice would be great.
Thanks
On a side note, thank you to everyone in this forum for all the help you've provided over the year. I truly appreciate it. I've upgraded to a Droid Incredible and I'm glad to still be a part of the Android family
Performing a "wipe data/factory reset", followed by a format of the SD card should destroy all "personal" information.
Of course, that deletes all the market apps as well - not sure if that is what you had in mind. But the baseline (system) stuff is still on the phone in /system after that wipe, and the new owner can just boot into the rooted ROM you installed and configure it the way they want. (Or you could help them).
I am 99.999% certain that the "/data" partition is completely empty when you wipe it - there is not even any "leftover" data that a forensics expert could get at, without using CIA/NSA-level techniques (extremely expensive). This is an artifact of the way that a "yaffs2" filesystem works when it is erased (and also because eraseblocks in our Nand are 128K in size).
If the formatting performed on the SD card is of a "quick/lazy" variety, there still may be information on the SD card that a forensics expert could recover, but certainly not by anyone that was a casual user. If that concerns you, you can mount the SD card on the PC and use a wiping program such as "sdelete" (Microsoft Windows Sysinternals utilities) to perform a security wipe of it.
The only thing that won't be affected by these procedures is the phone's activation status, you can only clear that if you have a stock recovery and stock ROM on the phone. Strictly speaking though, if you take the phone in to Verizon, (or maybe even call them) and have them dis-associate the phone's ESN/MEID from your plan, the activation status that is recorded on the phone will be useless.
HTH
bftb0
PS - Just read your post more carefully (about the activation part). You will need to completely unroot the phone (including having a stock recovery), and perform a factory reset to clear the activation status. Once you've done this, you will need to re-root your phone after bypassing the activation screen. This means might want to prepare ahead of time with everything you need on your SD card, unless you can get what you want via WiFi.
It's a fair bit of work to do all that. It might be easier to just leave the phone activated, and have Verizon disassociate it from their end of things - the buyer should be able to activate it after he/she has had the phone added to their account with their carrier, and then make a *228 call. (That's all the activation screen is anyway).
TL;DR if your phone is unlocked (not restricted by network) just delete what's mentioned above and flash a gingerbread ROM with root.
When you boot the phone to make sure it's working, don't go through the activation process at all. Just turn it off.
Sorted.
- Swyped from my rooted HTC Legend -
TS;DR
lol
jpzsports said:
I'd like the phone to be so that when you turn it on, it brings you through the steps to activate your phone.
Click to expand...
Click to collapse
There is another way to do this which is less complicated than unrooting and re-rooting if you really insist - but it only works if you have the S-OFF bootloader (v 1.49.2000) on your phone, and have gotten fastboot to work (USB drivers installed) on your PC.
Basically, it boils down to using fastboot to direct-boot a stock recovery to your phone, and then using the "factory reset" menu from within the stock recovery. Doing things this way allows the existing (custom) recovery to stay put (untouched) in flash memory, and the stock recovery will do BOTH the data wipe and the NVRAM reset that clears the phone's activation.
Prerequisites: 1.49.2000 S-OFF bootloader; fastboot program; USB Drivers installed on your PC
(1) Download the Leak-V3 PB00IMG.ZIP from this XDA post
(2) Unpack that zip file; you are interested in the "recovery.img" file.
(3) Charge your phone completely (100%), turn it off, and then re-start it in Fastboot mode (Send+End)
(4)
Code:
fastboot boot recovery.img
You will see an image with a black background, a phone, and a red triangle with an exclamation point in it. That's the splash screen of the stock recovery. To see the menu, press Vol-Up+End together. When the menu appears, the text will be in a blue/magenta color.
(5) Select the "Factory Reset / Wipe data" menu entry.
Note that when it runs, the first thing that it mentions is "Restore factory NV setting..." - that's the bit where the activation is being cleared. After that, it will do all the wipes you are familiar with in Amon_RA (or Clockworkmod). (Be patient, there is a small delay).
That's it - other than cleaning up your SD card.
Be aware that some Froyo/GB ROMs are going to be a little flaky about handling the activation - the whole business of needing to press the Menu key to get a keyboard to show up and then toggling to numeric layout to be able to generate a DTMF tone ("press 1 to activate") - are not going to be obvious to someone that is new to the phone. Unless you are planning on assisting the buyer after the sale, it's probably easier to just sell them a returned-to-stock phone.
cheers
bftb0
Hmmm okay thank you so much for the detailed responses. I really appreciate it. It seems like it's more complicating than I thought.
If I just wanted to return the phone to stock 2.1 unrooted (and avoid having to unroot, and re-root the phone, and reinstall a ROM) how would I do that?
Just get it to like brand new with steps to activate your phone on boot.
Thanks!
jpzsports said:
Hmmm okay thank you so much for the detailed responses. I really appreciate it. It seems like it's more complicating than I thought.
If I just wanted to return the phone to stock 2.1 unrooted (and avoid having to unroot, and re-root the phone, and reinstall a ROM) how would I do that?
Just get it to like brand new with steps to activate your phone on boot.
Thanks!
Click to expand...
Click to collapse
Install the "FlashBack21" ROM (find it here on XDA in the dev forum). Charge your phone to 100% and use the ROM with the radio to return the phone to the July OTA stock condition.
When that completes, boot it up and then skip account setup (and any other setups) and do a
Menu -> Settings -> Privacy -> Factory data reset
When the phone boots next, you will see that it is asking for activation; power the phone off.
Note that you need to tell Verizon to disassociate the phone from your account prior to handing it over to the buyer; otherwise if they run the activation, the phone will just re-activate to your account.
bftb0 said:
Install the "FlashBack21" ROM (find it here on XDA in the dev forum). Charge your phone to 100% and use the ROM with the radio to return the phone to the July OTA stock condition.
When that completes, boot it up and then skip account setup (and any other setups) and do a
Menu -> Settings -> Privacy -> Factory data reset
When the phone boots next, you will see that it is asking for activation; power the phone off.
Note that you need to tell Verizon to disassociate the phone from your account prior to handing it over to the buyer; otherwise if they run the activation, the phone will just re-activate to your account.
Click to expand...
Click to collapse
ok sounds good to me. So I'll install the FlashBack ROM, do a factory reset, and format my SD card and it should be clean right?
What's the best way to format my SD Card?
And since I already activated a Droid Incredible, doesn't that automatically disassociate the Eris from my account? You can't have 2 active phones right?
jpzsports said:
ok sounds good to me. So I'll install the FlashBack ROM, do a factory reset, and format my SD card and it should be clean right?
What's the best way to format my SD Card?
Click to expand...
Click to collapse
Sure. Or format it first (after backing it up to your PC); you can use the Amon_RA menu to format the SD card if you don't have a media slot or card reader on your PC. Won't really matter if there's one ROM file on the SD card.
The most secure way to do things is what I already discussed - format it any way you please, and then mount it to the PC and use that "sdelete" utility from Microsoft. (read the docs on how to wipe an "empty" drive). The most convenient, and probably least secure way to format it is using the phone menus - either the OS menu, or the Amon_RA format menu.
jpzsports said:
And since I already activated a Droid Incredible, doesn't that automatically disassociate the Eris from my account? You can't have 2 active phones right?
Click to expand...
Click to collapse
Yes, that sounds right, but I would call Verizon before you ship/hand over the phone and ask them to be sure.
Thank You so much for all your help! You've been awesome!
I'm going to go ahead with this process now and hopefully everything will work out.
EDIT: It worked perfect and boots to the Activation screen. Thanks again!
A friend of mine sent me his SGS2 which has some strange issue that happened after trying to root and/or simunlock. (not sure what caused this issue).
The phone has stock rom (Telcel Mexico) and is rooted, has CWM and boots properly, but two issues happen:
* Each time your reboot it kind of "factory resets", deleting wifi networks, apps, settings, etc.
* If you flash anything, it succeeds apparently but after rebooting it's still on the same ROM/kernel versions it was before flashing. NO ERRORS. This applies for Odin, with CWM, I have tried installing CM7 and CM9 roms (downloaded 2-3 times) and all say "Can't open /sdcard............./....zip (bad)"
I was hoping that following this thread would help:
http://forum.xda-developers.com/showthread.php?t=1457458
However, even flashing the bootloader makes no difference. The count on download mode is stuck on 2 no matter if I install ROMs, kernels, bootloader, etc.
Edit: what's even wirder, I put my microSD card in the phone and it formatted it and replaced my content with my friend's last snapshot. How can such a thing happen? It's as if the phone was locked into some strange "restore" mode...
What can I do with this? I feel kind of stuck with this situation... Have not found any information so far...
Regards
there was similar thread some time ago, it seemedvthat I think the whole system was read only, I'll try to search a bit for that
EDIT: I could't find it but try to mount system and data and stuff in cwm and then tey to flash aome rom, then unmount (I'm not pro but this is what I would try)
Sent from my sgs2 running cm9
Well,
I think the FS mounting issue would work with cwm installable roms, but if I have reinstalled everything from odin, even the bootloader, isn't it strange in that way? I also don't understand why rebooting the phone even rewrites an SD card.
Even the counter on the download mode is stuck on 2, no matter how many times I flash a kernel, rom, bootloader. Odin always reports a successfull upload...
Yep, thag sd card thingy is pretty weird and I have no ide what's causing that.
Sent from my sgs2 running cm9
Well,
I have researched a bit more and found this for the Nexus S:
http://forum.xda-developers.com/showthread.php?t=993403
This phone has exactly the same symptoms, but as the yellow triangle is on and it always boots into a rooted version, I would like to see if I can do anything so the phone can be sent back for warranty...
Any thoughts?
If you can .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Still problems use usb jig to set rom counter to zero .
Return to service centre .
Well,
Have tried everything, but no success. This is really weird, it's as if the whole phone had a backup and restores to this point on every reboot including sd card. Every odin flash comes out as "succeed", but nothing changes.
Will try to build a usb jig and test if it at least gets rid of the yellow triangle. I also can't flash anything via CWM as somehow the memory is "locked"... An external SD card is overwritten if inserted...
Regards
OK so let me start off with, great site. I have read a ton of information.
First: Siyah 4.3.3 (Latest) Kernel which now has been put to AJK v1.48s
ROM; SHOstock3 v2.5.9
PreMod Settings: SGS2 AT&T SGH-i777. Started with GB > AT&T OTA (KIES) 4.0.3 > AT&T OTA WIFI 4.0.4 (caused huge freaking headaches with battery, charging, turn off the phone loop, battery draining, etc.)
Issues:
Original Issue posted in this thread (viewing Single Post) http://forum.xda-developers.com/showpost.php?p=39350619&postcount=18
Creepy offered something to try. That never worked as all I was able to do was download mode or stare at the Samsung Galaxy S2 Splash Screen. Well, I took to his download repository and other links and used his One-Click Recovery to stock GB Rom to make part of my phone usable, using this link here: http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
While it is Gingerbread at least my phone is usable. I want to try his STOCK ICS method but that mentions the eMMC super-brick bug.
So this is what I have tried so far. I have tried installing Siyah 4.3.3 nomswap for my kernel using Mobil-Odin Lite. That works but it never reboots or actually says finished. What it does do is stay at the wicked purple splash with the yin yang symbol. I left it like that last night until I woke up this morning and it never changed. So I rebooted the phone and the Kernel is on there. I reboot into recovery so that I can install SHOstock3 v2.5.9. That goes off flawlessly except here the last few times it won't reboot when I go to the GO BACK. It sticks and doesn't do anything. Rebooting shows the SHOstock3 Engine Boot Animation. Once it stops it goes to ask me for the encryption password. Well I put in my password (was the same one to the unlock screen) and it reboots and you see the nifty Samsung animation logo and then goes to the Samsung Galaxy S2 Animation Logo and then just stays there. It really pisses me off.
So after all that I finally put a new Kernel on there,AJK 1,48s. Pretty cool it loads up and then reboots. Well AJK shows up after the light-blue bar fills up and then goes black and the 4 touch sensitive row keys are lit up for a bit before going dark but the phone is still on. So I rebooted to recovery (CWM now with the Kernel) fixed tweaks, went to advanced and saw all sorts of options. Tried clearing caches for ROM 2 and restarting,no effect. I removed ROM 2 and went through reboot and nothing. Restored ROM 2 and nothing. Re installed SHOstock3 v2.5.9. Did the same thing after install and not backing out when I hit GO BACK. Rebooted, same scenario that happened before with requiring password. Entering password does the same thing with a reboot and then staying on Samsung Splash Screen. If I Don't enter the password and reboot,same thing happens. So after being irritated and pissed off I ran Creepy's One-Click Fix again and paid attention to the phone and noticed it mentioned not being able to access the AT&T section or partition or something like that. So while part of my phone works under normal circumstances I want to figure out how to remove that encryption part of the phone and get full access (even though full memory and space are shown under Windows 7 and the files on the phone). The password I put on there isn't taking and I don't know if using PC methods for removing encryption (which could take awhile I know) needs to be employed (and if so which methods) or if that part is just screwed and I can't put on any other kernels or custom ROMs. Perhaps tell me where I messed up. Should I try swapping the ROMs from Advanced setting in CWM Recovery? Can I try a different ROM (kernel didn't seem to help)? I have done several factory resets dalvik cache wipes cache wipes formats,etc. and it is still there. I can say that before the whole encryption debacle (even though I was encrypted I did get in my phone after encrypting it) my pin unlock for my SIM wouldn't work and I actually SIM locked my phone. Had to go to AT&T and get a new SIM and was up and running. I put a 4 digit pin lock for the SIM (it let me do it) and when I went to unlock it after a reboot, it wanted an 8 pin for the PUK and wouldn't take what I put. I tried to change the PIN but to no avail. Once that happened I guess it snowballed. Any help is appreciated. I have searched and tried some things that looked to match my issue but none have totally helped. I do have ADB set up on my wife's laptop which I use to restore my phone to GB Stock ROM. I haven't been able to reboot the phone into Bootloader to do any fastboot commands as when I tried to do it the commands just sent the phone into normal reboot (though adb reboot recovery does boot to recovery). I Haven't tried booting to the bootloader using the new Kernel though so I will wait for confirmation or additional information before I try. Thanks guys.
Eagle
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
creepyncrawly said:
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
Click to expand...
Click to collapse
Thank you so much creepy. I will give that a try later and see how it goes. I hope the information I gave actually gives enough info. I know folks usually want enough. Ill post back my findings.
Eagle
quick follow up and what I tried
creepyncrawly said:
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
Click to expand...
Click to collapse
Hey Creepy, I have a quick follow up and want to tell you what I have tried.
So I had already used Kies to move to AT&T v 4.0.4 ICS on my phone when I read your post. Rather than flashback again to GB I went ahead and put Siyah 4.3.3 on my phone. Went great, rebooted and installed quick and everything. Well I rebooted into recovery and went to mounts and storage and formatted the data and all that there and even formatted the secondrom data and all that. Did it a couple times to make sure everything was clean and good to go. Even put AJKs kernel on there after I ran the cleanrom script and it went flawlessly. I did factory resets and wipes and all that and installed SHOstock3 v2.5.9 and started up great. Well it got past the animation and the damn Password for encryption popped up. Well I put the wrong password in and it rebooted without the SAMSUNG screen and went through the boot ani and back to the password for encryption screen. I put the right password in, it reboots and you see the Samsung logo flash quickly and then it sticks on the Samsung Galaxy S2 Splash screen. I don't know what is holding it up from going forward unless when I messed up the first go around and it deleted everything if it didn't take out the bootload command or what have you. So I don't know if this idea will work but I am going to flashback to GB and put the siyah version on there that you linked and see if that will work.
One tihng, when Iencrypted the device the first go round, I onlydid the used data and area not the whole thing. Is this affecting it somehow? Any other ideas to try? I figured a full data format would remove the encryption but it never pops up saying all encryption will be removed. What I need is access to that area of the phone if I could just mount it on the computer. Is it possible after formatting the data, or before, that I should mount internal USB, DATA, etc and try another format/wipe or at least mount them to see if they can be used? Thanks for the help. For anyone else viewing this post (which actually is a lot) any help or ideas are appreciated. I am thinking I may need to format everything and get ahold of Samsung to see if they will reset my phone for me. I just wonder if the PIN lock on my SIM card that got locked when it wouldn't take my PIN didn't mess something up as well.
Eagle
WarEagleUS said:
Hey Creepy, I have a quick follow up and want to tell you what I have tried.
So I had already used Kies to move to AT&T v 4.0.4 ICS on my phone when I read your post. Rather than flashback again to GB I went ahead and put Siyah 4.3.3 on my phone. Went great, rebooted and installed quick and everything. Well I rebooted into recovery and went to mounts and storage and formatted the data and all that there and even formatted the secondrom data and all that. Did it a couple times to make sure everything was clean and good to go. Even put AJKs kernel on there after I ran the cleanrom script and it went flawlessly. I did factory resets and wipes and all that and installed SHOstock3 v2.5.9 and started up great. Well it got past the animation and the damn Password for encryption popped up. Well I put the wrong password in and it rebooted without the SAMSUNG screen and went through the boot ani and back to the password for encryption screen. I put the right password in, it reboots and you see the Samsung logo flash quickly and then it sticks on the Samsung Galaxy S2 Splash screen. I don't know what is holding it up from going forward unless when I messed up the first go around and it deleted everything if it didn't take out the bootload command or what have you. So I don't know if this idea will work but I am going to flashback to GB and put the siyah version on there that you linked and see if that will work.
One tihng, when Iencrypted the device the first go round, I onlydid the used data and area not the whole thing. Is this affecting it somehow? Any other ideas to try? I figured a full data format would remove the encryption but it never pops up saying all encryption will be removed. What I need is access to that area of the phone if I could just mount it on the computer. Is it possible after formatting the data, or before, that I should mount internal USB, DATA, etc and try another format/wipe or at least mount them to see if they can be used? Thanks for the help. For anyone else viewing this post (which actually is a lot) any help or ideas are appreciated. I am thinking I may need to format everything and get ahold of Samsung to see if they will reset my phone for me. I just wonder if the PIN lock on my SIM card that got locked when it wouldn't take my PIN didn't mess something up as well.
Eagle
Click to expand...
Click to collapse
Should I try TWRP instead of CWM and if so where should I grab it from?
Status Update
So this is what I have tried so far as of this moment.
I reflashed using your Stock + Root Gingerbread ROM.
Wiped DATA and everything in recovery menu several times.
Used Kernel Wipe and ROM Nuke for extra cleaning power.
Reinstalled the Kernel AJK and SHOstock3 ROM
Haven't installed any themes though I had Johns Blue and Villians Poison Base Theme (I believe that is what it is) on there when this all went down. Should I put them back on there?
Password still pops up. So what it looks like is that unless I stick with the unencrypted portion of the phone, I am screwed with any custom ROMs as the correct password has the phone restart and then stick at the Samsung Galaxy S2 Splash Screen. Apparently I still cannot access that area of the phones memory to wipe it at all no matter what I do. I need to access it somehow. Really driving me crazy and thinking I may need to talk with AT&T(as Samsung told me to earlier this morning lol) and see what they can do.
One thing I do notice is when I use your stock root program it actually removes the encryption or decrypts the section of the phone for the stock ROM to go on the phone which is cool.
Eagle
Any other things to try from anyone is greatly appreciated.
Been away all day. Sorry, I can't offer any other suggestions, but I have no experience with encryption. As you said, what you need to know is where the encryption is stored in memory so you can wipe or format that and restore it to original. If you can get to the right person, probably not level 1 tech support, then maybe you can find out. Somebody somewhere knows the answer to this.
would restoring my original EFS before this whole process help or is the encryption section totally blocked off?
WarEagleUS said:
would restoring my original EFS before this whole process help or is the encryption section totally blocked off?
Click to expand...
Click to collapse
I have no idea whether the encryption is stored there. What kind of efs backup did you take?
creepyncrawly said:
Been away all day. Sorry, I can't offer any other suggestions, but I have no experience with encryption. As you said, what you need to know is where the encryption is stored in memory so you can wipe or format that and restore it to original. If you can get to the right person, probably not level 1 tech support, then maybe you can find out. Somebody somewhere knows the answer to this.
Click to expand...
Click to collapse
Thx bro. yeah I need to run some forensic tools and see if I can mount the whole phone system on my PC and run the tools.
creepyncrawly said:
I have no idea whether the encryption is stored there. What kind of efs backup did you take?
Click to expand...
Click to collapse
a full efs backup. I made two or three actuakky using advanced efs, nitrality, and recovery.
WarEagleUS said:
a full efs backup. I made two or three actuakky using advanced efs, nitrality, and recovery.
Click to expand...
Click to collapse
A little research indicates that there is quite a bit of stuff stored in efs besides carrier specific data. So maybe encryption could be in there. Of those tools, nitrality for sure and maybe advanced efs should be able to restore the entire efs partition. If you are comfortable with the risk - a damaged efs would render the phone useless - then you might try this to see if it clears up the encryption issue. BTW, you should learn how to back up the efs partition yourself using terminal and linux commands.
creepyncrawly said:
A little research indicates that there is quite a bit of stuff stored in efs besides carrier specific data. So maybe encryption could be in there. Of those tools, nitrality for sure and maybe advanced efs should be able to restore the entire efs partition. If you are comfortable with the risk - a damaged efs would render the phone useless - then you might try this to see if it clears up the encryption issue. BTW, you should learn how to back up the efs partition yourself using terminal and linux commands.
Click to expand...
Click to collapse
Yeah I should have used ADB to do that from the get go. I should have used the wife's laptop like I started to instead of my WIN 8 machine has it seems to be finicky with Android SDK (the portion at least needed to run ADB). Linux commands really aren't much different than terminal and I have done both. I was actually trying to get fastboot commands to work but my bootloader wasn't cooperating and for the life of me I couldn't find how to unlock it. I may try restoring that EFS. If nothing else I would love to be able to format that EFS and replace it with my original copy though as you said a damaged EFS may actually cause issues (who knows if it is damaged). I do know that I am fixing to chat with AT&T support. I hope I don't have to drive down to Hoover, AL to the repair facility. I would rather them send me a phone and send this one back. I am on stock 4.0.4 ICS from AT&T and any root that may be on there (though I doubt there is now) I can remove and what not
Thanks for the advice and insight Creepy. I know you tried like hell to get me an answer but in doing research on here with other problems I found out some useful information going forward my friend.
Eagle
Well, looks like I will be getting a special early upgrade and the wife will as well. I will be keeping this phone, however, to mess with this and see if I cannot get this problem fixed. Thanks Creepy so much. I appreciate your research and help more than you know. If possible I would love to keep this thread open for a while just in case I figure this out and fix the issue. It may take me a week or so but I will get back to messing with it again.
A side note. You don't need the whole sdk to get adb. You can download just the files you need from my signature.
Sent from my SGH-I777 using xda premium
Hi,
after crashing my phones display (in fact it was my girlfriend :cyclops I sent my HOX+ to HTC repair service to replace the display.
After finally getting it back today, all seemed perfect, my Custom ROM (AOKP 2.2.2) was reset - but I expected that. (cleared /data and /cache I guess) I thought OK directly upgrade to latest version of AOKP from maxwen, flashed new kernel from the zip first then tried to copy the rom to sd card via windows explorer - and there was the problem: it showed an 'SD Card' Link but now size/space and just empty. I first thought about stupid windows drivers etc. but I found out that was not the problem...
So I restored my nandroid backup I made before sending it to repair service via CWM. After the restore process finished I found that google play was crashing because the SD card was missing! I checked storage information and found that my internal storage now shows 56GB? I'm not sure how it behaved before, but I though the /sdcard partition is separated from the other space?
I then checked stock android explorer which just gives an error that storage is not available or so. then I checked es explorer and it just showed a broken link 'sd card' in /mnt/.
I restarted into CWM 6.0.2.7 and chose 'install zip from sdcard' and CWM was able to access my sd card without problems... I tried installing an older AOKP version still on the ROM - same errors as above (sure after cleaning everything).
I also reformatted the /sdcard partition but still it won't show up in Android! :\
I also flashed back the old kernel (which came with the old ROM I restored via nandroid) but no change. The damn sdcard link seems somehow broken. It is accessable in CWM recovery without problems, but none of my ROMs seems to be able to access it...
I really wonder what the repair service did... Is my device somehow repartitioned? :\
Help?!?
[update]: I flashed TWRP recovery and tried sideloading a ROM cause my 'sdcard' (or whetever which internal partition it now is) is empty: adb brings an error 'sdcard not found in /etc/fstab' so I am not even able to upload a rom anymore.... ??
[update]: OK I was able to upload AOKP rom via adb push, flashed it via TWRP - still stock explorer says 'file or folder was not found' :\ also in android settings only internal storage is visible...
Thanks a lot!!
Boernsb
Is there something like this here for HOX+?
http://forums.team-nocturnal.com/in...ountable-internal-storage-on-the-htc-one-xxl/
This guy seems to circumvent the need for RUU with a self-made recovery image he flashes and then do 'factory reset' from boot loader?
bboerny said:
Is there something like this here for HOX+?
http://forums.team-nocturnal.com/in...ountable-internal-storage-on-the-htc-one-xxl/
This guy seems to circumvent the need for RUU with a self-made recovery image he flashes and then do 'factory reset' from boot loader?
Click to expand...
Click to collapse
Alright, with the storage partitions messed up I would really advice you as mentioned to flash the RUU , look around on howto depending on your CID, If you did send it to HTC repair service and It came back broken up then I think you should just call them again and tell them? You wouldn't want your phone damaged and just let it go do you?
In the meantime do an RUU, and do a factory reset.
But just to clarify, can you or can you NOT adb push files to your storage?
Ghand0ur said:
Alright, with the storage partitions messed up I would really advice you as mentioned to flash the RUU , look around on howto depending on your CID, If you did send it to HTC repair service and It came back broken up then I think you should just call them again and tell them? You wouldn't want your phone damaged and just let it go do you?
In the meantime do an RUU, and do a factory reset.
But just to clarify, can you or can you NOT adb push files to your storage?
Click to expand...
Click to collapse
OK I was able to solve the problem by relocking and Re-RUU the device. After that all was back to normal. Unlocked again via HTCDev etc. and now all works fine.
For the next time - and I strongly advice all others - when I send a device to repair service I will put it in original state by myself. And yes I was able to push the rom via adb push... (just still don't understand where the difference between sideload and adb push is...)
btw: flashed newest stable of Cyanogenmod and now I have the first custom ROM on HOX+ where loudness of phone speaker is not only as good as original rom - but much louder
bboerny said:
OK I was able to solve the problem by relocking and Re-RUU the device. After that all was back to normal. Unlocked again via HTCDev etc. and now all works fine.
For the next time - and I strongly advice all others - when I send a device to repair service I will put it in original state by myself. And yes I was able to push the rom via adb push... (just still don't understand where the difference between sideload and adb push is...)
btw: flashed newest stable of Cyanogenmod and now I have the first custom ROM on HOX+ where loudness of phone speaker is not only as good as original rom - but much louder
Click to expand...
Click to collapse
Glad to be of help ^^
Hello,
I broke my SII screen, I can not unlock it or see anything anymore. Obvioulsly, I'd like to access to internal storage *but* I did not activate USB debugging, or install any custom rom.
I manage to got to the device with adb, but as the phone is not rooted, I did not manage to mount internal storage in order to pull files from my phone. I also try Kied but I need to unlock the phone to access files.
I search the web and xda but I did not found a working solution (maybe my keywords were wrong).
Does someone has a solution ? For instance, a way just to be root easily on the phone in order to mount Internal storage ? Any other id ?
Thank you very much in advance. Doms.
PS: I do not want to change the screen as the price for the screen is too high. I do not have access to another SII phone in order to plug its screen on my mother board.
Flash a custom kernel/root the phone/get CWM, then find someone who uses the version of CWM that comes with that kernel to walk you through doing a nandroid backup (how many button presses to get through menus, etc) ?
MistahBungle said:
Flash a custom kernel/root the phone/get CWM, then find someone who uses the version of CWM that comes with that kernel to walk you through doing a nandroid backup (how many button presses to get through menus, etc) ?
Click to expand...
Click to collapse
Thank you for your answer. I'd like to install CWM but is it possible without putting the phone in debug mode ? How can I put the file on the phone as I can not mount storage under adb ?
Thenk you for your help.
Doms.
You can flash a custom kernel via Odin (like Siyah) in download mode, the file you're flashing is on your PC, not on the phone, and this will root your phone and install CWM at the same time. All you need to know beforehand is what Android version you currently have on the phone so you choose the right build to flash, otherwise you'll end up with bootloop.
Search for the Siyah threads on here & read to work out which build you need to flash.
MistahBungle said:
You can flash a custom kernel via Odin (like Siyah) in download mode, the file you're flashing is on your PC, not on the phone, and this will root your phone and install CWM at the same time. All you need to know beforehand is what Android version you currently have on the phone so you choose the right build to flash, otherwise you'll end up with bootloop.
Search for the Siyah threads on here & read to work out which build you need to flash.
Click to expand...
Click to collapse
Thank you again. Will try to get in download mode (more difficult than recovery as I need to validate at some moment without screen, adb do no want to do it as the phone is not rooted).
One last question: will it erase the internal storage or not?
Best regards. Doms.
If you have problems getting into DL mode, order a jig, or try the thread in General section where people have offered to lend their jigs to people nearby; might be someone near you who has one (not sure if the thread is still updated, but worth a look).
No, flashing a custom kernel will only do exactly that, replace your stock kernel with the custom kernel & your stock recovery with CWM, nothing else is touched.
Edit - The end result of this will be a nandroid backup, and you'll still have to get your data out of that. The easiest possible way will be to find someone else with an S2, restore your backup to their phone, get your data, and then have that person restore their setup. You can pull data from a nandroid (with just a PC), but it can be a bit fiddly if you've never done it before. We'll cross that bridge once you actually have a backup though.
MistahBungle said:
If you have problems getting into DL mode, order a jig, or try the thread in General section where people have offered to lend their jigs to people nearby; might be someone near you who has one (not sure if the thread is still updated, but worth a look).
No, flashing a custom kernel will only do exactly that, replace your stock kernel with the custom kernel & your stock recovery with CWM, nothing else is touched.
Click to expand...
Click to collapse
Thank you for all. I just DL the kernel, will try this evening.
Doms.
You're welcome Good luck, post here when you've flashed it/if you have problems.
Hello,
Just to thank you again. I just have time to try it and it works fine ! Get and remove my 2 Gb of photo from my old phone.
Best regards. Doms.
No worries. Nice work, glad you got your data