Had a bad USB connection in my old phone, so AT&T just swapped it for a new one.
I immediately flashed Clockwork recovery and tried installing SlimBeam ROM.
Noticed some weird problems:
the notification bar is blank (I've got the toggles, but nothing else)
the home button didn't work (does nothing)
maps and other location-services failed to work (no network location errors)
Calendar data gives errors trying to sync with my Google account,
Contacts not syncable at all (doesn't even show as an option in sync settings)
So booted back to recovery and:
did a factory reset
cleared cache
formatted /system
installed slim & slim gapps.
Didn't install any of my own apps, didn't restore anything from Titanium Backup.
Not only did the problems persist, but I got android keyboard (aosp) errors on all text entry fields.
I thought I'd try a different rom.
Trying to install Paranoid Android gave me an assert error, so I SWITCHED FROM CLOCKWORK RECOVERY TO TWRP.
In TWRP, I did a factory reset, wiped data, wiped cache, wiped dalvik cache, wiped system, then installed Paranoid Android and the latest Google Apps.
SAME PROBLEMS, including the keyboard issue.
And I get an error connecting to the Play Store.
Anybody ever hear of something like this before?
The problem can't be in /system or /data, since I have wiped those before reinstalling.
And they appear to be independent of ROM and recovery package.
While it could be hardware related, in my gut I feel it must be something in the software.
Could there be a problem with files that ROMs and Recoveries don't touch? Something in the /dev, /efs, /sys, or some other folder?
I am curious to know what's going on, and am willing to do some troubleshooting and posting of logs.
But, more importantly, what can I do to get all this functionality working properly?
Related
So, I recently flashed Omega 10, did a full wipe. Had Omega 8.1 prior. All of a sudden, Im getting "not enough space. free some up" etc. And this is after a fresh flash. So thinking it might be a bug, I wiped again, flashed 8.1 back on and behold same problem. The odd thing is, I can take photos fine, etc, boat load of storage, I just cant open gallery. Installed a 3rd party app called quickpics, that opens fine, but spams me with "cannot open database" messages.
Any idea?
Have tried just going into settings apps/all and wiping the cache for your gallery.
sounds like it may just need to be cleared out.
Yeh, in recovery when I flashed, I wiped SYSTEM, CACHE, DALVIK, BATTERY & DATA. Just finished putting the stock rom back on, and excatly the same issue.
not thorugh CWM......through settings.
you will not be wiping the cache partition of the phone you will be wiping the cache of the app.
and worse case have tried just removing the app, rebooting and placing it back.....it may fix that memory error upon reinstallation if the wipe of the Gallery Cache does not work.
I wiped cache/data of both Gallery and Media storage apps, same thing. Copied the APK for gallery, removed it with rom toolbox, and reinstalled, same thing.
currently restoring to my nandroid backup, see how we go.
Restoring nandroid did the trick.
Good deal, glad it worked out
As of yesterday, my CM7.1 phone won't boot - it gets stuck at the "rotating arrow" blue Android for ever. It's a Samsung Galaxy S II GT-9100.
I have been running CM 7.1.0 for several happy months now, and haven't tried to install or upgrade my ROM. The last action I took before this happened is that I made a full system backup (using CWM 5.0.2.6).
That backup is present on the internal memory. I can boot into recovery, mount drives and access devices using adb shell. So I do have an opportunity to fix what's broken, if I can work out what it is.
Given that the last thing I did was a backup, I checked to see if any of the partitions were full, but none are. (None is more than 42% full according to df; although strangely, df does not show any partition mounted on /.) I tried making another backup, watching carefully - that worked fine. I tried restoring the first backup - no improvement.
I've also tried wiping everything Recovery allows me to that's non data-destructive - cache, Dalvik cache etc. It hasn't helped.
How do I work out what's wrong? Is there a boot log file anywhere which might give me a clue as to what is wrong? I've searched for "*.log" but can't find anything obvious.
I don't want to do a factory wipe if I can avoid it, because obviously that will lose all my data. If I do a factory wipe and restore just the data partition, does that put me pretty much back where I was? If so, how do I restore just the data partition? The Restore option in CWM Recovery seems to do full backups only, and only from a particular directory.
The original CM and Google Apps zips are still on the internal SD (same versions as are currently not working). Would it be worth trying to reinstall those, without wiping? Or would that be data-destructive?
Any other ideas?
Thanks!
Gerv
SOLVED - remove 0-byte data/system/profiles.xml
I tried doing a full factory reset from Recovery. This got the phone booting again, but without any of my data . Fortunately, ClockWorkMod has a "partial backup restore" function. I restored the data partition... and the phone stopped booting again.
So this is progress. I now had some idea where the problem lay. I finally found it using a laborious 5-minutes-per-cycle manual bisection technique. Delete half the stuff on the data partition, reboot, if it still fails, delete more, reboot... once you get it to boot, restore the data partition, narrow it down further. Once you find a top-level directory, repeat the process inside it.
The result: the existence of a single 0-byte file stopped my phone from booting entirely. The file was: data/system/profiles.xml.
I have no idea what that file does (there are only a few references online), how a 0-byte version of it got created, or why having it existent but empty breaks things but if it's not present everything works fine. I have no idea if anyone else will ever see this problem, or if they will ever find this forum post. But still, here's my Wisdom of the Ancients (google the phrase for the relevant XKCD comic).
Hello, I'm running RR 2.6.1 with Dorimanx's latest kernel and I've run into a huge problem.
I'm not sure what the trigger is but I think it could be updating the SuperSU app, or it could just be that I'm super unlucky. In any case, I really really hope someone will be able to help me here.
I was facing random freezes and SODs on the kernel but I was in the midst of tweaking my settings to see if I could fix it. I updated the SuperSU app on the bus on the way home, went home & tried to power my phone on but it wouldn't work so I force-restarted by holding down the power button. When it rebooted, I had all sorts of FCs so I went to CWM Recovery & cleared cache & dalvik & fixed permissions. Nothing worked. Here's what I've tried so far:
- reflashing the kernel
- reflashing the ROM
- re-rooting via Odin
- flashing another kernel (I tried fluxi but it was stuck at the animation screen & wouldn't boot)
- Googled for how to fix process.acore and Gapps FCs, tried to clear all the Google-related apps' data but they wouldn't clear
- trying to delete the apparent offending files from /data/data/... via adb and Android Explorer but it didn't work, kept saying it was read-only or something, even though I followed all the instructions to SU and mount as RW
By this time, exTweaks didn't recognise the kernel as compatible, Whatsapp and TB FC'd, just about everything FC'd.
I went into CWM Recovery to try and make a Nandroid but it said "Error while making a backup of /data".
I am truly at my wits' end. My phone wouldn't even let me access it after the right passcode was input. At this point, I just want to go in and backup my Whatsapp and relevant TB apps.
Please, if anyone is able to help me, PM me or something. I'm on Skype if you're so kind as to be willing to walk me through anything you think may help.
Thank you.
Flash a clean ROM, wipe cache and dalvik, do a factory reset and start from scratch.
Multiple fc can be caused due to several reasons like:
-wrong phone.apk
-wrong framework
-wrong ROM
-too much undervolt
Sorry for telling but my first sentence might be your fastest approach.
Tapatalked from my Samsung GT9100
Tyrol said:
Hello, I'm running RR 2.6.1 with Dorimanx's latest kernel and I've run into a huge problem.
I'm not sure what the trigger is but I think it could be updating the SuperSU app, or it could just be that I'm super unlucky. In any case, I really really hope someone will be able to help me here.
I was facing random freezes and SODs on the kernel but I was in the midst of tweaking my settings to see if I could fix it. I updated the SuperSU app on the bus on the way home, went home & tried to power my phone on but it wouldn't work so I force-restarted by holding down the power button. When it rebooted, I had all sorts of FCs so I went to CWM Recovery & cleared cache & dalvik & fixed permissions. Nothing worked. Here's what I've tried so far:
- reflashing the kernel
- reflashing the ROM
- re-rooting via Odin
- flashing another kernel (I tried fluxi but it was stuck at the animation screen & wouldn't boot)
- Googled for how to fix process.acore and Gapps FCs, tried to clear all the Google-related apps' data but they wouldn't clear
- trying to delete the apparent offending files from /data/data/... via adb and Android Explorer but it didn't work, kept saying it was read-only or something, even though I followed all the instructions to SU and mount as RW
By this time, exTweaks didn't recognise the kernel as compatible, Whatsapp and TB FC'd, just about everything FC'd.
I went into CWM Recovery to try and make a Nandroid but it said "Error while making a backup of /data".
I am truly at my wits' end. My phone wouldn't even let me access it after the right passcode was input. At this point, I just want to go in and backup my Whatsapp and relevant TB apps.
Please, if anyone is able to help me, PM me or something. I'm on Skype if you're so kind as to be willing to walk me through anything you think may help.
Thank you.
Click to expand...
Click to collapse
Try the following:
-Download this: Ultimate kernel cleaning script
-Reboot to CWM recovery
-Flash Ultimate kernel cleaning script
-Under kernel specific option, Reset extweaks settings
-format /system (under Mount and storage)
-Flash ROM (RR 2.61)
-Flash Gapps
-wipe cache partion
-wipe dalvik cache (under advanced)
-fix permissions (under advanced)
-Reboot your phone
My above steps will not wipe your and should definitely fix your problem
good luck
Thank you both for your suggestions!
Unfortunately, I didn't get to try them but I'll definitely be checking this again if (touch wood) this happens again. Hopefully it'll be useful to someone else facing similar issues, I know I couldn't find clear answers on what to do.
@jokesy If the /data partition is somehow stuck at read-only, I'm not sure formatting /system will help. I could be wrong, I apologise if I sound ungrateful ('cause I do appreciate your help) but wouldn't reflashing a ROM kind of overwrite the existing /system files already?
I'm not aware of the details and technicalities of what exactly happens during a ROM flash but according to the AROMA installer, it seems like /system is wiped first.
What I did
Gave up on backing up apps & WhatsApp through the normal ways, most of my TB apps are backed up daily anyway, just lost some data like that for Sleepbot.
Pulled WhatsApp database files from /data/data/com.whatsapp via ADB, restored the previous day's Nandroid backup & copied the database files to the relevant directory. I guess it may seem minor, but as everything was melting down on my phone, I kept getting messages from friends about project work in school & other stuff that I couldn't read so I really wanted to not lose all the new messages that had come in.
Restoring my Nandroid (thank God I backup daily) fixed everything, fortunately, but there are little quirks I'm still ironing out. Eg. My Godville app can't seem to connect to the main server & retrieve details of my character despite clearing data, uninstalling & reinstalling. Not too sure why.. :/
-----------------------
サンソングガラクシS II からタパトクで書いた。
@Tyrol
Ididn't know you were using aroma installer though, but formatting /system has nothing to ago with /data sms vice versa
Following my wouldn't have hurt though, ur would only ensure a clean system partition before install.
I'm happy for you
Better luck next time
Swyped from my Samsung Galaxy SII
I recently had a very similar problem. The only way I could resolve it was to also format /data during the usual full wipe re-install
Karl.morteo said:
I recently had a very similar problem. The only way I could resolve it was to also format /data during the usual full wipe re-install
Click to expand...
Click to collapse
Tough luck man. I don't know why the data corrupts spontaneously, it happened once to me when I was playing Plague, everything started FC-ing all of a sudden while I was in-game. Bizarre. Didn't want to do a full wipe so I just restored the /data partition from my latest Nandroid.
-----------------------
サンソングガラクシS II からタパトクで書いた。
Hey guys.Im kinda a noob, so bear with me. I have a SGH i747 (att galaxy s3) and I rooted it on my mac using motochopper. I backed up all my apps and system data with titianium backup to my SD card, and i also backed up my stock ROM to my internal storage using ROM Manager. I then downloaded liquid smooth using my phones browser, and then I selected it within ROM manager and clicked "reboot and install' (keep in mind, i didn't wipe memory or anything) So it was stuck at the boot screen. Then i realized what i did and went and wiped data/factory reset, dalvic cache, and the other cache, within Clockworld mod recovery (vol up + power + home). After that, it worked, but only to find that all my apps were gone, and the play store and browser app didnt work. so basically softbricked however I can make phone calls and text (lost all contacts). Then i went into cwm and tried to restore my phone, at first it came up with two backups (neither of which had the name I named my backup) but said no files found and then when I mounted my storage, the bottom one said md5 mismatch but the top one worked. the top one would work for about 6 min then while it was restoring data it would reboot into liquid smooth and i would have like 3 apps i didnt have before (other times i would get stuck at the boot screen). I also tried restoring it right after I wiped data/ factory reset and cleared the caches, but then it would get stuck at the liquidsmooth boot screen. Tried pretty much everything.
I just want my phone back the way it was before root or anything, with all my data. But I backed up all my stuff besides apps to KIES, so willing to reset it to stock firmware if possible
need all the help i can get. thank you all very much
Hi,
I'm new around, hope this is the right forum...
I have a galaxy s1 (i1900) which I flashed with a new ROM (2.3.6) in the past and then installed 4.2.2 from a zip, and it worked fine for a few months.
Having the same ROM file I used before, I tried to get it back to 2.3.6, as the 4.2.2 didn't work quite well, causing some problems when trying to make phone calls / receive calls.
After flashing the 2.3.6 again, the phone kept rebooting itself. Having read a few different guides online I tried all options - wipe data, wipe cache, wipe dalvik cache... then did some dramatic things like formatting /system, /cache /sdcard... I know it's not a very smart things to do when you don't know what you're doing, but I guess I felt I have nothing to lose at this point...
I also tried to reinstall 4.2.2 again and it only rebooted to the recovery mode whenever turning it on.
When mounting to USB I see no files in the device at all, only a folder called 'clockworkmod' with file called '.recovery_version' inside, and 2 empty folders named 'external_sd' and 'LOST.DIR'. It also shows it has 13.2GB free out of 13.2GB, which is weird, because the os doesn't occupy any of the capacity.
How do I save this poor device?
Many thanks in advance for your kind help!
Naama