i was having problems with my comp recognizing my phone forever so i just got around to flashing cwm3 last night and flashing some ext4 roms. no problems or glitches other than launcher pro's settings not sticking after reboot. i installed bonsai's 2.0.1 and flashed the gingerbread theme, after rebooting all my widgets are gone and it doesnt save the launcher pro plus product code or any settings. i tried a few times wiping and trying different roms, but it keeps happening....... does anyone have any ideas?
Related
Hey all, I'm having a problem that I can't seem to figure out at all. Last night I flashed Myn's 2.2, the colin_ph battery tweak, and the stock kernel that is modded to be able to run the tweak. I also flashed the riptide theme and couple add ons to it as well. I backed all my apps and data up with Titanium backup pro prior to flashing anything. Before I went to bed last night, I put my phone down while titanium was restoring everything. This morning when I woke up, I played around with it for about an hour, made sure that the battery tweak was running correctly, and surfed the web a little bit. I then remembered that Titanium recommended to reboot after a restore when switching from a custom rom to a custom rom( I was running CM6 and Snap7.6&turbo beforehand). So after rebooting, before my homescreen can even load I get a error that says "adroid.process.acore" not found. And another one that I cant remember, and from that point on it just keeps boot looping. This has happened 3 times in a row, so I know that something is wrong.
Any ideas of how I can fix this? When I restore my base Myns2.2 Nand backup I have no problems at all, or even when I reboot with all of the above mentioned flashed before restoring my apps and data with titanium I have no problems, only after doing the initial reboot after installing all apps and data do I have this problem.
Update: Just rebooted with Myns2.2, battery tweak, and theme and had no problems what so ever, so I know that somewhere in the process of restoring my apps and data and then rebooting following that, something is going wrong.
Try wiping your dalvik-cache and see if that helps
Hi All,
Been having a problem with the touchscreen randomly becoming unresponsive or the phone rebooting on its own ever since when I'm (trying) to run MIUI ROMs.
By "random" I mean that it sometimes occurs while typing, switching home screens, opening an app, or even just when the phone's idle.
Not experiencing any unexpected FCs throughout the MIUI ROMs that I've tried however... so at least that's a good thing?
I don't experience any of these problems at all when running a stock Sense ROM, so I'm hoping it's not the same rebooting problem described in another thread that requires sending it in for repairs as that would be very troublesome.
The phone's a HKCSL Desire that was rooted using unRevoked. The problems occur even when I don't install any apps onto the phone and when the phone's just idle with the screen off (for randomly rebooting).
Any suggestions would be greatly appreciated =) and I hope I'm not just SOL for MIUI ROMs since no one else seems to really be having these problems.
---
List of things I've tried:
1. Full wipe with Dalvik & cache before flashing a ROM (many, many times)
2. Updating to 32.48.00.32U_5.11.05.14 radio and downgrading to the suggested 32.44.00.32U_5.09.05.30_2 (Thought it might've been caused by WiFi connection as I always have it on... but doesn't seem like it)
3. Using different versions of Clockworkmod (2.5.0.7, 2.5.0.1, 2.5.0.1 modified by MIUI.cn)
4. Repartitioning/formatting SDCard before/after flashing a new ROM
5. RUU-ing the phone and redoing everything from scratch
6. Using an untranslated base MIUI-Desire ROM
7. "Upgrading" the ROM by flashing on top of the 10.15 build
Versions of MIUI ROMs I've tried:
Pretty much all the releases of 10.15 and 10.22. Currently fiddling around with eevek's stock 10.29 and mobiousdigital et al.'s 10.29 builds.
Hopeful bump =)
I need help finding a stable rom. I've tried a lot over the past few months, and they all have problems rendering my tablet inconvenient for use.
Before I was using a CM7 mod which was working pretty well, but then I upgraded to an ICS rom somewhere around September. That's when the performance started to drop. Then somewhere around March I upgraded to a Jelly Bean rom, and that's where the serious problems started.
At first I tried SmoothRom, but that just wouldn't install until I did some tweaks (removed an "assert" line of code). And even then, stuff in settings kept crashing. So I tried the HellFire rom, which worked but was having some serious performance problems. The launcher I was using (Apex) was slow and unresponsive at times, and various apps (browser, music player) kept crashing at times.
A few weeks later, I tried SmoothRom again, and it seems to work better. No more tweaking needed to flash it, and no more crashing in settings. But the problems were even worse. My browsers (Dolphin, Chrome) kept crashing frequently when I browse, the music player (winamp) kept stopping, and worst of all, sometimes my kindle won't wake up from sleep (I have to hold my finger on the power button to turn it off before turning it back on).
I just don't know why I keep having problems. So today I tried using the modified stock roms. The http://forum.xda-developers.com/showthread.php?t=2211872 won't even flash (something about failing). So I tried the older modaco rom. I had a problem with a launcher (Holo) where it kept saying "holo launcher stopped unexpectedly" every time I tried to run it. I tried rebooting, clearing the cache, but it still had problems. Plus I found out not a lot of apps were compatible with my gingerbread based android os, so now I'm going to give this rom a shot:
http://forum.xda-developers.com/showthread.php?t=2051331
But basically, why am I running into so many problems? Is this normal, or is there something abnormal with my kindle fire?
Do a full wipe while installing a new rom. I don't think Holo Launcher works with stock. And for the stock modded, are you sure you downloaded the main not alt zip?
Sent from a DROID Pro that is rooted and runs vanillalvl's CM7
Hmm......I use twa_priv's latest CM10.1 ROM (4-01-13) and it runs sweet. I have my Kindle set up to boot either CM7 or JB.....the CM7 ROM is sblood's November 2012 release. When I get tired of JB, I will switch to GB. There are certain apps that won't perform correctly on JB but run flawlessly on CM7.
You need to start with a truly clean wiped system and SD card partition, but please make sure you have the ability to mount the Kindle's storage from recovery to place the ROM after wiping SD. Install apps sparingly so it's easier to weed out potential culprits of malfunction......it sure is hard to figure out what is going on if you install 50 apps all at once.
And remember no OS is flaw free.....they are like human beings, unique and not perfect
There are plenty of stable enough for daily use ROMs, some faring better than others.
Sent from my Amazon Kindle Fire using xda premium
Yeah, I have TWRP and I always wipe and factory reset before flashing a ROM.
Try using an Official CM10.1 from hash ode. It seems to be the most stable out there
Sent from my Amazon Kindle Fire using xda premium
You need wipe all the cache before you install any new rom
I have the Galaxy S3 and had it rooted with CWM and Superuser, and running CM 10.1 RC5. I used Titanium to make a backup and flashable zip before going from CM 10 to 10.1 RC5 and flashed the zip after upgrading to RC5. Everything worked fine until about 12 hours later when I tried to take a picture and my phone crashed and rebooted itself. Then I noticed Titanium running saying it was restoring my app data. My wallpaper was reset back to the default but my lockscreen wallpaper wasn't reset. I also noticed that my icons for my apps were changed from what they were before this. They were all the same apps just in a different order. Which may have been what they were when I made the backup. Now my phone won't connect to my WIFI at home though my 2 laptops do, and my phone will connect to the WIFI at my friends and all the open networks at the places I go. I have entered the password over a dozen times and have even tried changing it and entering that but nothing seems to work. Also, I have already done a complete factory reset back to the original stock ROM, and still it won't connect to my WIFI. Any help would be greatly appreciated. And just to let you know I have rooted my phone again with CWM and Superuser and I am currently running CM 10. And yes I tried connecting to my WIFI and it wouldn't when it was stock.
Hello,
I had on my Note 2 t0ltecan Dn3V5 and it started to restart ever so often and my youtube app dissapeared and woudnt work. So I tried to wipe the data and it didnt work, from many TWRP versions and Philz recovery. Then i used Odin to install a stock rom, which then finally everything worked and I then tried to restore my Dn3.
Everything worked except my Action Memo which stopped working so I did the procedure again. Samething, so I tried installing Dn3V5 rom instead of restore. It didnt work because it kept saying bad zip, I tried TWRP 2.8+, 2.7.1, 2.6.3, 2.6.1, 2.5 and Philz. Only 2.5 worked but it woudnt boot after the graphic logo. Then i tried again and the same thing. So i restored again and this time it either doesnt boot after graphic logo or I get IMS Framework problem.
What should I do, restore Stock or DN4?? What could my problem be?
UPDATE:
I used odin again to install stock kernel again, this si the farthest I have got with it booting and not restarting. It is still doing that, sometimes more than others, but I have disabled 5 apps, one google play services and the other google chrome. So far so good, nothing has happened but I will have to experiment more.
I have been formating it many times and closing and opening it by taking out battery, will that affect my phone?
UPDATE 2:
I found the problem, I used my bros Note 2 battery and everything ran fine. My original battery died so I had bought a second hand battery. The whole time (for 2 months) it was causing me problems but I did not realize. After ripping the sticker off the battery I figured out it says 2000mAh on the inside XD.