Hi folks!
Sorry I'm posting this here, as I only found out after registration that for the first 10 posts I'm not allowed to post to the original Encryption Unsuccessful thread.
So here is my story about my SGS, Gingerbread, ICS, the Encryption Unsuccessful message and Jelly Bean – maybe this is of some help.
First of all my conclusion (for those who want to know more – read the story after conclusion). Note that this refers to SGS – I don’t know about other devices. The Encryption Unsuccessful message appears on ICS when the /data partition fails (can’t be mounted / accessed anymore – hardware issue). Other partitions may be failing, too. The failure may happen both after cold start of the device and suddenly while running. In the latter case, you may also get this message on Jelly Bean. BUT: If vital partitions fail at cold start of the device, Jelly Bean would not start booting until Encryption Unsuccessful message. Instead, it starts recovery mode. From there it may help to select restart of device – at least for me, after a few attempts, Jelly Bean starts normally (because finally the partition(s) could be mounted). If mounting of partitions fails on Gingerbread at cold start, Gingerbread keeps restarting the device (instead of entering recovery mode) until the partitions could be mounted successfully – and then Gingerbread starts normally. However, if partition(s) fail while Gingerbread is already running, system may hang or slow down (can’t say because it never happened to me).
Solutions I can think of:
1) Patch ICS to also enter recovery mode instead of booting if vital partitions could not be mounted. This way it behaves like Jelly Bean and at least doesn’t throw the Encryption Unsuccessful message after cold start (which – at least for me – is the only situation in which I get that message). Maybe one could even patch ICS / Jelly Bean to enter a boot loop like Gingerbread until the partition(s) could be mounted. This is – of course – not a real solution, because sooner or later the internal memory may fail completely. Especially because of the risk of data loss, solution 2) is to be preferred (but more difficult).
2) Somehow manage not to use the internal memory (at least not the failing parts of it). That means everything – apart from the /boot partition, which doesn’t seem to be affected – should be located on an external micro SD card. The problem: It’s not enough to swap mounting of internal and external SD card by changing the vold.fstab file. At least for me, during installation of Jelly Bean, vital partitions were still created on the internal memory. But maybe I did something wrong? It looks like if the internal memory is *completely* failing (so unlike my case), this may however work – see youtube -> watch?v=zdMhYYdMB08
If anyone knows how to make Android boot from external micro SD card – please let us know.
The story:
About half a year ago, my SGS (Gingerbread) suddenly went into a boot loop when I switched it on. After several attempts (reinsert battery etc.), it worked again. By time this and that wasn’t working properly anymore – settings gone, apps crashing, lags… As restarts didn’t help, I decided to flash ICS. This has worked until a few weeks ago. The battery went down and after the device switched itself off automatically, I inserted another battery, tried to start – and: Encryption Unsuccessful message. I thought maybe it didn’t properly switch itself off so that the internal memory didn’t get enough power and, consequently, data got corrupted. So I flashed ICS again. 3 days later, after I had turned the SGS off for about 2 hours, I got Encryption Unsuccessful message again. As I read that maybe only one person so far experienced that message on Jelly Bean, I flashed that one. Worked fine the first few hours, but then after device was switched off again for some time, it went to recovery mode at startup. Only after some restarts it finally booted Jelly Bean (which was then running without problems). At this point I was convinced that it’s a hardware issue (failure of internal memory). As warranty was still valid, I decided to flash stock ROM (Gingerbread) and updated it to 2.3.6 via Samsung Kies (as earlier, it went into a boot loop after cold start) and sent it to Samsung service (a company called w-support was supposed to repair the device). They only replaced the LCD (for whatever reason) and applied a software update. When I got it back, as expected, symptoms had not changed. The thought of sending it in again without a replacement of internal memory or mainboard really frustrated me. So I tried to make Jelly Bean use an external micro SD card instead of the internal by changing vold.fstab. It worked with respect to swapping USB memory and external memory. But it didn’t make Jelly Bean install on the external micro SD card. And that’s where I am now. I would love to get all the vital partitions installed on the external card – but that doesn’t happen. Anyone has any advice? I tried to do it the way described in the youtube video (see above), except that I didn’t want to install Linux just for repartitioning the micro SD card. So I used SD Formatter and MiniTool Partition Wizard Home Edition. I would have preferred to partition the external SD card using CWM, but V3.0.0.5 seems to be somehow buggy – it got that option, and within a second it says “done”, but nothing has happened to the external SD card.
Has anyone managed to install ICS or Jelly Bean on an external SD card?
Thanks a lot in advance!
Related
I have a couple problems that I've been having since rooting my phone and installing cyanogen. I'm currently using cyanogenmod 4.2.2 with recovery 1.4 on my t-mobile g1. Also, I have the CM updater.
1. When I am using my stock headset, the phone restarts automatically at random intervals. Also, when the headphones are plugged in when the phone initially starts, the phone will definitely restart shortly after the home screen finishes loading.
2. When I am listening to music through the stock headset (either through the base music app or pandora) and I receive a call or text message, I lose all sound functionality (including in-call sounds) When this happens I have to unplug my phone and restart it again to regain sound functionality.
Are these bugs with the following that others are experiencing that can't be avoided:
1. cyanogenmod or
2. root or
3. cyanogen recovery 1.4?
Am I the only one that has had these problems? Is there another ROM that anyone would recommend that would most likely rectify this?
Help!!!!
I have the same problem.
No idea how to fix it?
G1
CyanogenMod 4.2.2
I think I fixed my own problem
I flashed this new radio:
http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip
Then I backed up my sd card, formatted it, and partitioned it into a main fat32 partition and a 500mb ex2 partition.
Then I wiped and re-flashed cyanogen 4.2.2 and it works!!!
Also, it took me a while to figure out how to partition my sd card. It seems there is no easy way to do this with windows vista. I had to use Ubuntu's partition manager called "gparted". Apparently this can be done without actually installing Ubuntu if you just boot from the CD, but my computer wouldn't read the sd card through Ubuntu until I installed ubuntu and downloaded the updates. Then when I was done I tried to delete the Ubuntu partition (VERY BAD IDEA). Now my computer won't boot at all and I have to find a way to re-write my master boot record (MBR) which I don't know how to do. CRAP!!!
anoyment
ajchandler said:
Also, it took me a while to figure out how to partition my sd card. It seems there is no easy way to do this with windows vista. I had to use Ubuntu's partition manager called "gparted". Apparently this can be done without actually installing Ubuntu if you just boot from the CD, but my computer wouldn't read the sd card through Ubuntu until I installed ubuntu and downloaded the updates. Then when I was done I tried to delete the Ubuntu partition (VERY BAD IDEA). Now my computer won't boot at all and I have to find a way to re-write my master boot record (MBR) which I don't know how to do. CRAP!!!
Click to expand...
Click to collapse
Dude, take your HDD out of the computer, put it inside a USB enclosure and save your data, then just delete all partitions and install Windows again. Next time, you can just install Ubuntu from INSIDE Windows with "wubi.exe".
As for the sporadic resets, I am having the same problem. Only thing is: I had just flashed the 4.2.2 rom in the phone, wiped, and just then, being in the WC, I get a call, take the phone out of my pocket, it slips from my hand and drops right inside the can (yes, it had just been cleaned, Thank God), took it out fast enough, battery out. Couldn't find the screwdriver for it so I shook as much water as I could off, and let it dry in front of a full throttle fan for about 12 hrs.
It reset itself some times after that, but I don't know if the problem is the Rom, hope it is, (sorry). Next thing I know is, there's an update to ver. 4.2.5, so I updated, hasn't done it again yet, it's been 36hrs.
Hope I could help and anoy you some guys...
I have the same problem with my G1 (cyanogenMod-4.2.5 kernel 2.6.29.6-cm42 baseband 62.505.20.17H_2.22.19.26I), had to change from cyanogenMod-3.6.6 hoping it will fix the reboot problem, but it doesn't change
I reformat SD card (1 Gb) and repartitioned it, doesn't fix the problem. The difference is that is reboots now less frequently (with cyanogenMod-3.6.6 it started reboot suddenly and did it every 20min - 3 hrs, now 1-3 times a day).
Seems that it somehow related to WiFi connection, and may be email receiving process (may be free space problem? But as far as i can check there is free space available on the SD card).
If with cyanogenMod-3.6.6 i could assume that some new installed application caused it, then with 4.2.5 i didn't install anything, and it starts rebooting again recently.
Is there a way to write a log or something to see which app caused reboot? It's linux anyway, so should be smth to see the reason, right?
Updated to CM-4.2.7.1 and added a 4GB Class 6 TF
luk1 said:
I have the same problem with my G1 (cyanogenMod-4.2.5 kernel 2.6.29.6-cm42 baseband 62.505.20.17H_2.22.19.26I), had to change from cyanogenMod-3.6.6 hoping it will fix the reboot problem, but it doesn't change
I reformat SD card (1 Gb) and repartitioned it, doesn't fix the problem. The difference is that is reboots now less frequently (with cyanogenMod-3.6.6 it started reboot suddenly and did it every 20min - 3 hrs, now 1-3 times a day).
Seems that it somehow related to WiFi connection, and may be email receiving process (may be free space problem? But as far as i can check there is free space available on the SD card).
If with cyanogenMod-3.6.6 i could assume that some new installed application caused it, then with 4.2.5 i didn't install anything, and it starts rebooting again recently.
Is there a way to write a log or something to see which app caused reboot? It's linux anyway, so should be smth to see the reason, right?
Click to expand...
Click to collapse
LUKE, I AM YOUR FATHER, NOT...
Just kidding, just couldn't let a chance like this pass me by, sorry .
2 days ago I changed the 2GB TF (which was a class 1) with a 4GB TF, now a class 6. Wiped the phone and added an ext3 1GB partition.
Yesterday I updated the CYanogen Mod to ver 4.2.7.1. Haven't seen another reset since, but it could be that I haven't used the phone much other than for phone calls since the update. But altogether it seems pretty stable.
I just used the cm-updater and everything was done automatically.
If you don't already have it, download it from the market, check for new roms and download the one I said. Please let us know if it makes any difference for you.
ajchandler said:
Then when I was done I tried to delete the Ubuntu partition (VERY BAD IDEA). Now my computer won't boot at all and I have to find a way to re-write my master boot record (MBR) which I don't know how to do. CRAP!!!
Click to expand...
Click to collapse
To reinstall the Vista MBR:
http://support.microsoft.com/kb/927392/en-us
Hi, i'd like to share this piece of work that took me 2 days to figure out.
I am a fresh owner of a Samsung Galaxy Young. Very nice piece of hardware for the price, if i might say.
Since i like tuning, and shaping my computer, i started doing that on my device. Keep in mind, i own the European version of the phone(i'm italian.)
So everything started when i tried to upgrade to 2.3.6. No european firmware yet.
So i downloaded some asian version with English support and flashed through odin.
Everything was fine, except that my 8gb microsd seemed dead.
after many tries, i manage to make it up and running trough an usb micro-sd reader on an xp laptop, and seem to have solved the problem by running a very deep chkdsk.
A few days later(about a week) Dang! here we go again, the sd is dead again.
Strange thing was, that on my older phone (gt-s5230) it seemed to work just fine. So why wasn't it working on android or windows either?
There we go: somehow it seems that the sectors of my sd where corrupted in a very bad way, because once loaded the sd on linux( i used a virtualbox VM in conjunction with Gparted, but it worked fine since the controller uses a usb mass storage driver and not a mmc one.) dmesg showed me a very long list of errors from trying to read it's sectors.
This explains, by the way, why with the older phone it worked fine: it didn't care.
So gparted wasn't working, stuck on trying to read the partition table of the sd;
then i decided to try a crazy thing: a simple command line program:
dd if=/dev/sr0 of=/dev/sdb
It overwrote completely whatever remained of the bad sectors,along with the partition table and completely restored the sd to functionality; Just to be sure i formatted it in windows, fat32 FULL format(not the quick one).
Long story short, if you can't recover an sd, load it on linux, than launch this command:
dd if= (whatever file sufficiently long, say at least 400-700MBs, i used the cdrom because it was the fastest way in that occasion.) of=/dev/SDCARD (whatever device is the sd)
Then, full format under windows.
VERY IMPORTANT: if there is something that looks like /dev/SDCARD ,/dev/SDCARD1 or /dev/SDCARD2, do not put ANY number after the name of the device. we are going to do a brutal overwrite from sector zero; if you put in the number of the first partion or the second, you overwrite the partion without touching the sectors that our phones usually tries to read first, locking the sd.
So I have had CM10 on my phone for probably 8 months now (almost since I got the phone) and have had no issues with the ROM whatsoever.
I got a notification about an updated version of CM10 today and went ahead and downloaded and installed it, but when I finished the update, I had no personal data left on the phone, could not set up accounts to recover the data, could not (and still can't) recover backups through ROM Manager, and cannot recover backups through CWM. I get an error message which I can't remember at the moment and leads to a bricked phone upon reboot until I do a fresh install of CM10.0.
I read after I started having the issues that I wasn't supposed to directly upgrade from the CM Updater with an S3, but it was already too late. Supposedly the issue is something along the lines of an emulated version of my phone's internal storage? If that makes sense. So whenever it's pulling a piece of information it's looking in the spot it should be in, but on a non-physically-existent SD card, essentially. That's what I gathered anyways.
I have a 32gb external SD Card that is also in use with my S3. I have tried moving my ROM Backups to there and recovering from the External SD Card, but the same error message occurred, although ROM Manager was at least able to find the backups after they were moved (I also had to change the setting and request that it prefer to look through an external SD Card).
So I have a usable ROM as far as the software itself, but I no longer can use any accounts or information that is stored with them or any of the same widgets (not a game-breaker) as I was able to previously. Is there a way to fix this? I've never just been completely stuck before >.<
jkremis said:
So I have had CM10 on my phone for probably 8 months now (almost since I got the phone) and have had no issues with the ROM whatsoever.
I got a notification about an updated version of CM10 today and went ahead and downloaded and installed it, but when I finished the update, I had no personal data left on the phone, could not set up accounts to recover the data, could not (and still can't) recover backups through ROM Manager, and cannot recover backups through CWM. I get an error message which I can't remember at the moment and leads to a bricked phone upon reboot until I do a fresh install of CM10.0.
I read after I started having the issues that I wasn't supposed to directly upgrade from the CM Updater with an S3, but it was already too late. Supposedly the issue is something along the lines of an emulated version of my phone's internal storage? If that makes sense. So whenever it's pulling a piece of information it's looking in the spot it should be in, but on a non-physically-existent SD card, essentially. That's what I gathered anyways.
I have a 32gb external SD Card that is also in use with my S3. I have tried moving my ROM Backups to there and recovering from the External SD Card, but the same error message occurred, although ROM Manager was at least able to find the backups after they were moved (I also had to change the setting and request that it prefer to look through an external SD Card).
So I have a usable ROM as far as the software itself, but I no longer can use any accounts or information that is stored with them or any of the same widgets (not a game-breaker) as I was able to previously. Is there a way to fix this? I've never just been completely stuck before >.<
Click to expand...
Click to collapse
HY, try to flash cm again from theyre website (dont update it), but this time,erase cache 3 times with the command;fastboot erase cache,this may solve your problem.IF I HELPED PLEASE PRESS THANKS!!!!
johnyvlad said:
HY, try to flash cm again from theyre website (dont update it), but this time,erase cache 3 times with the command;fastboot erase cache,this may solve your problem.IF I HELPED PLEASE PRESS THANKS!!!!
Click to expand...
Click to collapse
Just to be clear, you're saying to try and flash CM10.0 and then do not update when prompted from the notification? The other part was clear enough lol.
Edit: Tried the above and did not fix the problem, but I didn't use fastboot specifically because I have a Samsung phone.
The error I'm getting is "unable to mount /system" when I try and restore a backup.
Bump. Still haven't figured this out.
Problem solved.
Re-flashed CM10.1; doing full data, cache, and dalvik wipes before and after the flash; and the problem was corrected.
Hello everydody, I am experiencing some difficulties with my Samsung, model GT-I9003-phone which "dropped off a lorry" somewhere next to my relatives somewhere in Asia. When I goth the device, it was in a non-working condition, except a boot-loop and the download-mode. Back then, I had the package of the phone where the exact version ( I don't know if this is what is called "Baseband" or at least is called baseband at my wife's GT-I5003) was specified. So, back then, I was able to find the exact ROM for the device. Unfortunately, the box with the version number now is - somewhere.
After flashing a stock-rom, I managed to enter recovery-mode where I read something about the internal memory being corrupt. As far as I can recall, I then mounted the external SD-Card and somehow managed to reboot the system back to almost normal operation. Even reboots appeared to work normal, besides the fact I had no memory access, neither to internal nor to external sd. In addition, GPS malfunctioned, too.
Unfortunately, even this state didn't last for long time. After several weeks of now-and-then-use, the system just broke down again into a boot-loop. After some time of flashing a variety of stock roms, I managed to flash clockworkmod recovery which works perfectly well. Unfortunately, I didn't manage to root the phone before it "collapsed" again. Besides the possibility, I'd guess this could be a resaon for CWM being unable to flash a custom rom? Otherwise, I'd just test my way through the varieties of versions .
Basically, I do have two questions: 1. is there a possibility to find out if internal memory has failed - and if yes: How?
2. Is it possible to install any version of CM on that phone in the condition it is in?
Thanks a lot in advance for any answers
Hello everybody, I finally found the box . It reads GT-I9003MKDTHL. Is my assumption right that there are no such things as basebands in the GT-I9003 any more and I should be able to flash pretty much any firmware? Furthermore, today I tried to format what is specified as "sd-card ext" in CWM fir GT-I9003 and it gives me an error-message. When I flash "sd-card", my external sd-card gets formatted. So, I'd presume the internal sd is just fried. I read about a workaround for GT-I 9000, where someone installed Androd on a partitioned external SD. Is there somebody who knows someboy having heard about somthing similar working with the GT-I9903?
One step forward...
Hello everybody, I finally managed to get some light into my issues as I once again figured out how to get a software installed and running . It's this one:
http://forum.xda-developers.com/showthread.php?t=2329200
Thanks a lot to the guy who just posted it somewhere where id could do good...
By the way, I figured out that this software actually includes the Baseband.
As in this version, the original recovery system is running and giving me an error message when I start it without external SD-card, I am now quite sure that the internal memory has just failed as this error message was specified in another posting of someone who had a similar issue with a GT-I9000.
The biiiig "Outch" is, that I am unable to install any CWM Recovery System with that Baseband..This results in me not being able to upgrade the software to ICS, where - as far as I read some troubleshoot-information - will enable me to mount an additional partition on my SD-Card as Data-Partition which isn't possible yet (i.e.: I can't access my SD for storing data or whatever - it's just specified as "not there").
I tried to install the XXKPE-Baseband to be able to go for KPQ which would enable me to install CWM Recovery. I also installed Bagarias CWM-normalboot-image via Heimdall - but I was unable both to boot the OS and to find any trace of a zip-file on the SD-card.
Edit: I managed to install the right CWM - it's mentioned in the post where I've got the firmware from... now, I only have to figure out how to deal with the fact that "officially" there is no SD-card inserted - or, better, that this SD-card is now flagged as "internal SD" - and how that machine can find the zip-file on it
Thanks for every bit of help with that issue
Try Aroma File Manager with Terminal
For SDCard issue you could probably switch them in vold.fstab in /system/etc
Good Luck !!!
try this- http://forum.xda-developers.com/showthread.php?t=2329200
Hello folks, yesterday I installed 4.2.2 update (ubranded with MG8 ending, i9105p), everything is working fine, with exception to my SD card.
In Settings -> Storage it doesn’t shows up, and the "mount" button is greyed out, just like no card was inserted. The SD card itself is working (checked on other devices), it uses FAT partition (I even tried to re-formate it) and, since the Recovery can acces (and eventualy flash files) from it, Android OS doesn’t see it. I tried mounting via ADB but I have no previous experience with it. I also tried wiping cache.
I’m gonna try re-flashing another firmware tommorow, I hope it will work. :cyclops:
But is there any easier way to fix it? Thx
UPDATE: The card was working fine after re-flashing, but sometimes when copying files on it, File manager hangs, and files wont copy. This issue also unmounts the SD and makes it unable to be mounted until you restart. Propably some sort of kernel issue? (According to testing and 1+ year of trouble-free expirience with the card on another device this doesnt look like a malfunctionic card)