After using ICS on Samsung devices, people started noticing problems with the devices, mostly rebooting and getting the message Encryption unsuccessful. Often these devices wouldn't start again, and trying to flash them failed. The conclusion was that in these cases the internal storage had become unusable, possibly damaged. This may or may not be the same as the superbrick bug.
At this moment there doesn't seem to be a way to get the internal storage working again. There is a workaround, which consists of disabling the internal storage, and using external storage in place of internal, however, this doesn't enable the internal storage.
I was wondering if this problem could affect the Tab. I've been trying ICS for a while now, and I have had problems flashing hidden.rfs in some ROM's. Trying again has worked so far, but it could be a first symptom. Running ICS I've had the Encryption unsuccessful message. So far rebooting has worked, even though this results in a factory reset. These messages seem to occur more frequently lately. I've switched back to GB, CM7 to be precise, but updating Froyo to GB via Kies OTA failed last time, and only was successful after a emergency recovery.
I'm afraid the internal storage may be developing a problem, and I was wondering if this could have been caused by ICS?
@ableeker
Just wondering if you've made any more progress on this issue? I've seen your comments in some of the other threads but wanted to bump this one to see if we can get an updated synopsis on the state of this error.
For starters, it appears to mainly affect CDMA Tabs. Or, have you come across any GSM P1000's being affected?
Would be nice to have a dedicated thread to this issue so all Tab users can reference and build a collaborative knowledgebase (in one reference thread - ie. like the ones for the Samsung Captivate and Vibrant EU threads).
I understand the EU screen has damaged internal storage on the Captivate. There's a Captivate thread called [Guide] Encryption Unsuccessful - Reset Android [ICS Issue] with a lot of information. There are no real solutions so far it seems. I've had no responses in the Tab forums so far, people don't seem worried. However, I have seen threads like [FIX] [UPDATED] Internal SDCARD Damaged where Tab owners acknowledge the internal storage has been damaged beyond repair. It looks like some of the owners have GSM Tabs.
ableeker said:
I understand the EU screen has damaged internal storage on the Captivate ...
Click to expand...
Click to collapse
That's probably the biggest ongoing discussion for the EU (AFAIK). Woodrube esp. has been following the EU in various devices: Captivate, Vibrant, SGS2, Transformer, Nook, etc.
Lots of theories but still no sound proof as to the cause.
On a bright note, a handful of Captivate and Vibrant users have had their internal sdcards magically come back to life - ie. giving hope that the internal sd's are actually salvageable (if you're lucky). The downside is no one has put forth verifiable methodology to replicate those positive results. It's a crapshoot so far.
ableeker said:
... I have seen threads like [FIX] [UPDATED] Internal SDCARD Damaged where Tab owners acknowledge the internal storage has been damaged beyond repair. It looks like some of the owners have GSM Tabs.
Click to expand...
Click to collapse
This is what concerns me about our SGT7's. It definitely seems to be damage happening in these cases.
Related
Carrier: AT&T
Country / Language: USA / English
OS / Browser / build number (if applicable): Android 2.1, 2.2, CM 5.0.6
My Nexus One is restarting randomly. I have unlocked the bootloader in order to test out different ROMs and have experienced the issue with Cyanogen's Mod, Android 2.1, Android 2.2 and the HTC Sense Rom. It doesn't seem to be limited to a single app, either. I have reset the phone to as close to stock as I can (2.1, no new apps, stock bootloader as well), and I still have these random restarts. I notice it the most when there is a data transfer going on OTA, whether 3G, Edge or WiFi. Could it be a kernal issue or radio issue? I have done my best to troubleshoot via the internet and my limited knowledge, but nothing is working! Please help!
Try reflashing the recovery, wiping the data/cache etc and reflashing both the ROM and the radio. I had this problem too and doing one of these ended up fixing it. Hope this helps!
My phone did the same and it seemed to be a hardware error. I have returned it to HTC and am awaiting a new device. Hopefully it is not the same for you and a reflash will solve it.
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
chordmasta said:
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
Click to expand...
Click to collapse
Please post an update once you get your new phone. I am in exactly the same boat - had the exact same symptoms with the same result - returned the device and awaiting the new phone which should arrive tomorrow or wednesday.
How were the two of you able to send in your phones after unlocking the bootrom, thus invalidating your warranty?
esmurdo said:
How were the two of you able to send in your phones after unlocking the bootrom, thus invalidating your warranty?
Click to expand...
Click to collapse
Hate to necro a thread that is starting to get old but I am having the same issue. Will they still send you a new phone if it is indeed bad RAM? How long does it usually take from the time you send it in?
I have the exactly the same phone and have the exact same problem. Problem is I am in Costa Rica and I would have to send it back with my uncle on the 10th, but then I wont get it back for another month. If I just buy another nexus while I get the current one repaired, do you think I will get another one with the same problem? You can still buy an at&t nexus if you are an android developer correct?
esmurdo said:
How were the two of you able to send in your phones after unlocking the bootrom, thus invalidating your warranty?
Click to expand...
Click to collapse
It only invalidates your warranty if you damaged your phone by unlocking. This is a problem that came stock with the phone, we only unlocked it to try fix the problem.
is it a confirmed hardware issue? i started getting this symptom and downgraded to 2.1, flashed the Froyo FRF85 and so far its ok. I also had to format SD card.
If HTC/Google has a confirmed hardware issue on their hand...i smell something akin to antennagate albeit with less finger pointing
Hi guys, I started having issues with my SMS this morning. Now, I can't send messages reliably, I'm not sure if I'm receiving them properly now either. On top of that, I am was having issues with 3g, sometimes the icon would not appear at all, and others it would not load web pages or send data via internet enabled apps, i.e. facebook. I must stress that I did not change absolutely anything, and that it just started happening. could this be a flaw with cognition? or is it just AT&T being... well... AT&T?
I assume it's just AT&T being AT&T, I had issues with that exact scenario about a month ago. Cog is working fine for me, but you can always try to backup and re-flash and see if that helps.
vunuts said:
I assume it's just AT&T being AT&T, I had issues with that exact scenario about a month ago. Cog is working fine for me, but you can always try to backup and re-flash and see if that helps.
Click to expand...
Click to collapse
If it persists I will re-flash... pain, but what ever. Any-who I'm about to get an inspire 4g anyways so meh.
Thanks for reassuring me that I'm not the only one who has encountered this problem. I tend to have one-in-6-billion luck like that.
Please post in the Cog sticky instead of creating new threads.
oh and for the record I'm running 3.04. Looking in to 4.1 anyways, wondering if I can update it without having to wipe everything. Can I restore apps + Data if I go from 3.04 to 4.1, or will that cause all sorts of hairy issues still?
No problem at all. Did you do your research around the forums and see all the reviews about the inspire not being all that it's cracked up to be? Not trying to sway your decision or anything, just making sure you know what you'll be getting into.
iamtheculprit said:
oh and for the record I'm running 3.04. Looking in to 4.1 anyways, wondering if I can update it without having to wipe everything. Can I restore apps + Data if I go from 3.04 to 4.1, or will that cause all sorts of hairy issues still?
Click to expand...
Click to collapse
I don't think I wiped anything when I updated, but when I restored system apps with TiBu, I got some FC's when it came to a few of the system apps and data, don't recall which ones though.
vunuts said:
No problem at all. Did you do your research around the forums and see all the reviews about the inspire not being all that it's cracked up to be? Not trying to sway your decision or anything, just making sure you know what you'll be getting into.
Click to expand...
Click to collapse
I've been fiddling with it at the at&t store... I like it a lot but I'm looking in to the possibility of getting a different carrier's phone unlocked... I'll check out some of the discussion though. thanks
im not a big fan of how hard it is to remove the battery panel and the panel where the memory card would be at. but the phone looks nice. androidcentral has a video review about it
Hi all!
Can you help me with my following questions please:
My nook has the faulty chip, and I read that Verygreen had enabled the Trim function in the stable 10.2, so can I update to that rom?
Is there anyway to solve the lag problems without wiping all of my data. I don't dare to try the trim kernel as I'm living in Vietnam, and there's no nook store in case I brick my device.
Thank you very much. I'm looking forward to your answer.
bebubanche said:
Hi all!
Can you help me with my following questions please:
My nook has the faulty chip, and I read that Verygreen had enabled the Trim function in the stable 10.2, so can I update to that rom?
Is there anyway to solve the lag problems without wiping all of my data. I don't dare to try the trim kernel as I'm living in Vietnam, and there's no nook store in case I brick my device.
Thank you very much. I'm looking forward to your answer.
Click to expand...
Click to collapse
In theory trim has been fixed but it is up to you if you have the faulty chip and can't get service then you need to decide if it is worth it or not. The only way to beat lag seems to be with trim, the wipe and restore method, and you can try using an SDcard to keep your data. I only keep apps on mine all data movies, music, books are stored on SD and I don't seem to run into lag and that is on two different devices.
Hi all, I hope I can provide reliable good news: LG support says some providers made some changes to some repeaters (e.g. E-Plus in Germany). They have a solution and provide us with an update released around the end of October.
Now is probably a good time to point LG to some of the major problems introduced with the JB update (4.1.3), as the new Update will likely be a smaller improvement of the latter.
In my case:
- very slow return to home screen when closing apps and problems navigating the home screens, when some more icons and widgets are present
- can't write onto external SD with some backup apps (e.g. Super Backup)
EDIT: I would be totally happy about a way to port the updated system files, once they are out, to other Roms (e.g. the ICS Stock Rom).
I'm extremely skeptical that LG would release an update for our phone. Are you sure our model is on the list?
I called them personally regarding a prior support case (repair order -> "no error found") because somebody reported the techs had replaced some parts (new IMEI) and solved the problem. I wanted the same for my P880. They told me about the changes to some repeaters, the upcoming update, and the soon following update for the P920 (?) Optimus 3D.
I am as surprised and sceptical as you are. But as I have read about this update from a second, independent, source (the German forum at AndroidPit.de), I am starting to believe and, thus, spreading the news.
pegnose said:
I called them personally regarding a prior support case (repair order -> "no error found") because somebody reported the techs had replaced some parts (new IMEI) and solved the problem. I wanted the same for my P880. They told me about the changes to some repeaters, the upcoming update, and the soon following update for the P920 (?) Optimus 3D.
I am as surprised and sceptical as you are. But as I have read about this update from a second, independent, source (the German forum at AndroidPit.de), I am starting to believe and, thus, spreading the news.
Click to expand...
Click to collapse
Can you please point us to that article on androidpit.de. Thanks
I Tried to find but no result.
See here (look for "FETTES UPDATE" on top of the page):
http://www.androidpit.de/forum/562054/lg-optimus-4x-hd-reorganisation-interner-prozesse/page/2
Sorry, this is a German post. Although the writer confused repeater with router, P920 with P990, and another user confused software and hardware update.
EDIT: My support guy explicitly statet that this will be an OTA update. I am sceptical, as it happens often with LG that updates have to be installed manually/via PC. Very likely he meant that I won't have to "bring in" my device again.
I just called them again and explicitly named the increasing delay when returning to and browsing the home sreen as the major problem with the official JB rom on the P880. If some hundred more users do the same, LG hopefully addresses the issue as well.
pegnose said:
I just called them again and explicitly named the increasing delay when returning to and browsing the home sreen as the major problem with the official JB rom on the P880. If some hundred more users do the same, LG hopefully addresses the issue as well.
Click to expand...
Click to collapse
I just don't think that some repair guy from LG can do anything else then told you what you want to hear and mark it as solved. I think they are just waiting till you buy new device. I'm lucky because I have no such problems with RIL. I disabled PIN protection and installed Mahdi. Now I sometimes (once per day?) can see no signal for second or two but it's ok.. no problems (there is no way for no signal, I'm living next to the mobile transmitter and I usualy have full signal bar). There is only one thing which gets me so angry - lags, usualy when listening music from youtube on background and browsing the Internet. My friend with Galaxy S laughs when my phone gets his lucky mood and he sees it, his phone is more smooth then mine, it's crazy.
Of course, this might all be a big hoax. BUT:
By now, I know of three different people who got pretty much the same information from LG support. Although you never know, for my part, I wouldn't like to suspect that LG internally agreed on certain standards on how to efficiently lie to their customers in this particular matter through personal communication - especially by giving an approximate release date (end of october) for the update AND outlining the release for the P920 as well. But that's just me thinking positively of other people and of the future.
Btw, could you elaborate a bit on this Mahdi thing you mentioned? I tried different Roms (Cyanogen, OmniRom) and none of them solved the RIP (Reorganizing internal processes) issue. Plus I unsuccessfully tried to fix it with EPRJ RIL implementation following this guide (experts might go *facepalm*, I tried anyways):
http://forum.xda-developers.com/showthread.php?t=2496075
Therefore I came to believe that RIP (my ideosyncratic acronym) and RIL are two pairs of shoes. No? Also, I don't really understand, what PIN protection has to do with anything.
pegnose said:
Of course, this might all be a big hoax. BUT:
By now, I know of three different people who got pretty much the same information from LG support. Although you never know, for my part, I wouldn't like to suspect that LG internally agreed on certain standards on how to efficiently lie to their customers in this particular matter through personal communication - especially by giving an approximate release date (end of october) for the update AND outlining the release for the P920 as well. But that's just me thinking positively of other people and of the future.
Btw, could you elaborate a bit on this Mahdi thing you mentioned? I tried different Roms (Cyanogen, OmniRom) and none of them solved the RIP (Reorganizing internal processes) issue. Plus I unsuccessfully tried to fix it with EPRJ RIL implementation following this guide (experts might go *facepalm*, I tried anyways):
http://forum.xda-developers.com/showthread.php?t=2496075
Therefore I came to believe that RIP (my ideosyncratic acronym) and RIL are two pairs of shoes. No? Also, I don't really understand, what PIN protection has to do with anything.
Click to expand...
Click to collapse
Mahdi is mod like Cyanogenmod, we have unofficial support from alfsamsung (he's great developer) you can find the thread in Optimus 4x development section (without "original"). He did a lot of changes in baseband driver & ril. Btw that reorganising bug is only in stock isn't it? I think in CM based roms is only crashing ril and asking for pin again or full crash of ril and baseband driver so you have to reboot your phone.
When I was running stock I never saw it (that reorganising..) I only saw someone talking about it here on xda.
I'm not optimistic because LG said that our phone won't get any update in future. I just don't think that they changed their opinion because of few people crying to their hotlink.
I'm so sorry about my english, my skills are just terrible
An update for Germany is out:
http://www.android-hilfe.de/lg-optimus-4x-hd-p880-forum/623458-update-v20c.html
Looks like the problem is gone!!!
Got my hands - ( don't ask how ) - on what appears to be a fake S5 Mini. Everything about it says Samsung, however neither Kies nor Odin detect the phone and the specs are all wrong anyway. Attached are screenshots from Device Info and CPU-Z.
The phone actually works OK, though it's not nearly as good as a real S5 Mini. But there are several glitches in the system: some apps or options just don't work, multi-language support is deficient, etc.
Nothing surprising from a clone.
Question: is there a ROM I can try to load to that device to see if I can make it work better? I was reading up on MoKee (because of the serrano3g identifier in the model name displayed by CPU-Z), would one of those ROMs work? The phone/wifi/BT portions all work correctly, so I guess there's no need to flash a new radio. Then again, I haven't flashed an Android device in a couple years, I'm basically like a newbie at that stuff, so if anyone can provide me with information on what/how to flash, I'd be grateful.
Thanks!
neat
Any pictures of the phone itself?
SOC seems to be a MediaTek MT6572 if correct see this thread http://forum.xda-developers.com/showthread.php?t=2687487
@protogenxl: Visually, it's an exact replica of a Samsung S5 Mini, with the brandname and all. So if you check out the Samsung site, you'll find plenty of pictures there!
As for the thread you mentioned, I had already read it but I'm still not sure whether that particular ROM can be installed on my device, even though it's a MT6572 ROM. And keep in mind that I am a newbie on flashing devices, so I'm not even sure where to start, what tools to use and what I should be looking for.
Thanks for the suggestion, though!
s5
I have a S5 Mini G8800-F, so the most interesting part would be the layout of the inside of the battery compartment, is the dead space for a second sim there etc....
I would say first order of business is getting a custom recovery installed and getting full backups of original OS in a safe place, after that should be relatively hard to completely brick it as I seriously doubt the clone company put any effort in to boot security
@protogenxl: I'll try and upload a picture of the battery compartment later today. Don't recall seeing a second SIM slot in there, though.
And I agree with you that the clone company didn't put any effort on securing the device. It was rooted when I got it, it's got one of those chinese bootloader menus (I found a video on Youtube explaining what each option means).
As for the custom recovery, should I just pick any of them or are there any recommendations specific to this chipset (or do I even have to care about the chipset at that stage)?
@protogenxl it has been to long since I messed with sisters then boyfriend's phone to get it usable but if memory serves I got a custom made version of CWM from the ChinaPhoneArenea forum.
@protogenxl: here's a youtube video I found which describes the exact device I have: https://www.youtube.com/watch?v=k_-OoKhkD_0
It shows it with its back cover open around the 2:30 mark.