Related
I know there are a lot of questions about this on XDA, but no one seems to give a straight answer on how to fix this or even prevent it.
I flashed kh2 deodexed today via CWM, everything went fine.. I installed titanium backup to restore my apps, which I did, they worked fine until I rebooted the phone. Then the apps dissapeared, and the home screen shortcuts display the SD card icon and they won't open "Application is not installed on your phone".
Then, I did a wipe to data and cache partitions, but this time I restored apps only (without data) one by one, as I needed. Not as a batch, as I did last time, and was working ok. Though, I thought I'd try the ICBINB kh2 ROM, so I flashed it fine. Restored apps through titanium backup, this time one by one, mostly apps only (some of them w/ data) and was working fine, but suddenly the apps dissapeared again.
I'm about to wipe the phone to fix this... but, is there a way to prevent this from happening again?
Is restoring data from titanium causing this?
Well there has been many direct answers on this topic. Factory reset. restore from cwm, not TB.
Sent from my SGH-T959V using xda premium
hey, didn't know that. **presses thanks button**
I just restored apps via cwm, fixed permissions and it's working. It even got my settings back.. wtf. I was living under a rock all this time.
But is it completely safe? I guess that for GB builds, doing backups and restoring this way may be harmless, but probably not the same story if coming from a froyo rom.
Anyway, thanks a lot.
yea, what i did was flash both 2.2.1 and 2.3+ fresh. then backup each and whatever rom you go to, flash the corresponding backup.
I am overjoyed to see that there is finally an official gingerbread update that I can flash, and then a CM7 for this kernel, that doesn't have any bugs that are too annoying. However, it's been a while since I became an expert on flashing my old LG Eve. Is there a thread somewhere that outlines exactly how to do this for this exact phone and mod?
I've got a D2G, with Fission ROM. the phone is unlocked and rooted. I have an original ROM saved to flash to the phone if need be. Everything I would ever need is backed up using Titanium Backup. I've downloaded the GB update and CM7. I think I'm ready to go.
Questions:
- Is there a thread that answers all this already?
- Am I going to run into any problems being unlocked or rooted?
- Does the phone revert back to being locked once the new GB is installed? That would not be good considering I'm in Canada, not on Verizon. I bought my phone unlocked so I don't know how to just unlock it again.
- I remember using nandroid before to make a complete backup of the contents of my phone so that if I screwed up I could just go back to it seamlessly. Same thing this time around?
- I'm not completely illiterate here though, so I'm going to give it a go and you can just correct me where I am wrong. First, put the CM7 and GB files on the SD card. then do a nandroid backup of the phone. Clear data, clear cache. Then use clockworkmod to flash the GB update. then use clockworkmod again to flash CM7. then use clockworkmod again to flash gapps. Start up phone, do a complete restore with Titanium and I'll have all my apps and settings, call history and texts back. I'm probably wrong somewhere in all this, but where?
If there's not already a comprehensive thread on this, let this be it!
You will need to SBF to stock to be able to install the update.
Refer to the following for some instructions:
http://droid.koumakan.jp/wiki/SBF
http://droid.koumakan.jp/wiki/4.5.607_Firmware
http://droid.koumakan.jp/wiki/CyanogenMod
Ok, I read these all over about 5 times. So in a nutshell, these are the steps:
- use rsdlite to put your phone back to the stock firmware 2.4.330
- unroot and remove cwm
- use android recovery to install gingerbread 4.5.607
- root again and install cwm again
- use cwm to install cyanogen and gapps.
Correct?
Also, I am running fission. According to my system info it is firmware 2.4.3. I would rather skip step 1 and just install gingerbread. I am guessing I can't, but please confirm.
Sent from my DROID2 GLOBAL using XDA App
You don't need to unroot and remove CWM after flashing the SBF.
Otherwise everything's correct.
You cannot install the official Gingerbread firmware update onto a phone that is not running stock unrooted 2.4.330 without CWM and with all bundled software intact.
Note: if you need to backup your applications and configuration data, you can do so with CWM. Make a backup under Fission, then perform all those steps above, and once you're running CM7 on 4.5.607, use CWM's advanced restore feature to only restore /data.
So here I am in Gingerbread on my D2G (already further than I thought I'd get!) and you would think it would be smooth sailing from here... except I can't root it now! Is there a different technique for rooting in Gingerbread? I used Z4 before, and it worked in seconds.
OK, I figured out how to root using another thread. and when i am in adb shell I get "#" and not "$" after entering a string of commands.
But, apps think that I'm not rooted. All I need is to install CWM, but it runs into errors, presumably because I am not rooted.
The phone is in some sort of weird half-rooted state.
really weird experience with rooting. I realized that I hadn't done the additional steps where you push superuser to the phone and a couple other commands. So I did that, and then root check said i was rooted. I rebooted, and adb shell was acting like I wasn't rooted! yet root check still said I was. I was able to flash CWM and reboot, and then install CM7. Everything seems great!
except, right from the start I was getting repeated FCs for com.android.phone.
I remember that there's an issue with needing to reboot after switching to GSM... so I'm trying that now. Let's hope that stops the FCs.
So what ended up happening was, I rebooted and stopped getting the FCs for the phone after switching to GSM. So that is good. However, aside from the two minor bugs that I was prepared to live with, this is happening now:
- I have phone and SMS service, just no data. Wireless works fine, and so do GPS and Bluetooth to my knowledge.
- When attempting to select a network to register on, I get the dreaded “Your SIM card does not allow connection to this network” message. I have tried doing this with data/roaming enabled/disabled and with “only 2G” selected. I have also tried a couple of tips I found online such as removing the battery for 15 minutes and also getting a new SIM card.
- At first I was able to enter new APNs, but they wouldn’t save. I hit menu, then save, but it goes back to the APN screen and none are listed. Now, what happens is, if I hit menu, then “add new apn”, nothing happens.
I went into the telephony.db file to manually enter my APNs, and it seems that they are already there, which is good. I re-entered them all manually using sqlite anyway. This did not work. I also noticed that Verizon was listed with a “1” in current, which probably means that Verizon is my current APN. So I removed that 1 and placed it on all my rogers APN entries. Still, nothing is saved at the APN screen in settings, and I can’t enter them through that screen, either. And no data.
Suppose it turns out that this is just a bug with CM7 right now and it’s unusable for me. Obviously I don’t want to go all the way back to Fission on Froyo when I can use gingerbread. How far back into this process do I have to go? Can I just flash GB and it will overwrite CM7?
Did you make a CWM backup of your freshly installed Gingerbread? If so, just restore.
If not, I don't see how you're going to “just flash Gingerbread” without SBF'ing to 2.4.x.
Well, I have done a lot of testing and troubleshooting. I went back to the start of this whole process, and I backed up my APNs and fully tested the phone at every turn, and my conclusion is that CM7 is not friendly to APNs. There was no problem with stock Froyo or stock Gingerbread. With the working APNs that I had, I was able to use data on both. Once CM7 was installed, it was a no go.
I used a couple of apps to backup my APNs both in Froyo and Gingerbread prior to installing CM7, and when CM7 inevitably didn't allow me to use data, I tried to restore my APNs using these programs as well. They say that they worked, and it's true that if you go into root explorer the APNs are there as you entered them or restored them using a program. But it seems these APNs are not going to work unless you actually see them at the APN page in settings. And nothing I have tried up to this point has been able to make any APN show up at that screen.
I think the “Your SIM card does not allow connection to this network” message at the network operators screen, as well as my inability to enter APNs, are 100% related. I also bet there is a simple solution to it!
If anyone has any ideas about how to make an APN stick, and how to force a phone to start using it, please let me know. I'll also post this at the CM7 forum.
I am having a problem with switching ROMs on my sensation which just started a few days ago. I am currently running ARHD 3.1.1 and it is very stable and I have had no problems whatsoever, but like many here, I like trying out different and new ROMs. Anyways, I did a backup and installed ARHD 3.6.2, and it was forcing close on several apps, and kept getting soft reboots, so I tried RCMix's, and it would load and automatically install some apps and settings that I had on my previous ROM, and it was working fine, but then I started getting soft reboots when I would open any app, so I tried about 2 other ROMs (S3n5eay/Pyramid3D) and same thing, so being fed up I restored my backup and then I began to have superuser problems, so I unistalled updates, cleared data, and still was unable to gain root access. I kept clearing data, installed superuser 2.3.6 then 3.02 and finally got root again, but everytime I reboot I lose root. I then again tried different ROMs, and same thing is happening. I have used superwipe script, ARHD's wipe script, P3D wipe script, formated from CWM, and no matter what, I am still unable to keep a new ROM and keep losing root with my backup. I'm sorry for a long post, but can anyone please help me figure this out. I have upgraded ROMs many a times in the past on this phone and others, and have never experienced these problems, so can someone please help me.
I kinda had the same problem with you, with that being root was the problem. But the ROM's are pre-rooted so that shouldn't be a problem. Try to flash the root file again, until it is succesfull flashed.
Thanks. I'll go ahead and try that.
Sent from Sensational toy running ARHD 3.1.1
Geez, that sounds horrible, man. It never ceases to surprise me how different every one of these seemingly identical devices are.
West0000 said:
Geez, that sounds horrible, man. It never ceases to surprise me how different every one of these seemingly identical devices are.
Click to expand...
Click to collapse
Well for the most part everyone downloads different software. For that just one of the factors that make us all somewhat "different" this is why everyone has some sort of problems here and there.
Most times a fix can be a reboot or reinstall of the app. Even clearing of caches helps because of data conflicts on the phone. Especially when someone like me that flashes different ROMS, that's why nandroids and backups are key so that if you fudge up your phone, you can always revert back to your nandroid.
And for all the people who are trying to revert back to their nandroid after flashing a different rom, you need to use the wipe data scripts in ARHD or Coredroid to reformat the ext4 before reverting your nandroid. Just a FYI.
All I know is that wiping everything before flashing a new ROM does not guarantee that you won't get FCs and soft reboots.
For example, I did a factory reset, wiped cache, wiped dalvik, and then did superwipe (yes I know redundant), and then flashed a ROM and I thought nothing could go wrong. Then while setting up I went ahead and setup my google account during the setup process, and once I was finished I began restoring my apps+data from Titanium Backup. While that was happening Market started auto-reinstalling my apps, and this instantly conflicted with the fact that I was doing the same thing from TB. It caused a few of my apps to FC all the time. So make sure you skip adding your google account during setup.
You can also get stuff to go haywire if you restore system data from TB. Doing so will conflict with the ROM and cause FCs and reboots. For example, I didn't know how to easily back up texts and contacts for a while, and I would go in to TB and restore everything that said something like mms, messages, texts, messages widget, etc. and doing so actually caused my messages to go haywire. Same thing with contacts. The only things you should be restoring from TB are your user apps+data. As already noted, you should also superwipe before restoring a nandroid because it is exactly like flashing a new ROM. If you're on a ROM you just flashed that has 1 version of superuser, and then you go straight into recovery and restore a nandroid without wiping everything first (and has a different version of superuser), you're going to get issues with superuser.
The rule of thumb when it comes to avoiding FCs and reboots is to avoid letting data conflict. Don't mix ROM data, don't mix app data, don't restore system settings from your old ROM on your new one, etc.
Believe me, I have attempted everything without any success. I guess I'm going to stay on my current ROM until I get the time to deal with all of this, and hoping that for whatever reason I don't have to reboot my phone, or that it randomly reboots in order not to deal with the problems. I have always wiped going/coming from different ROMs, but have never experienced this before, and it is very frustrating especially when I like to try different developers mods. I'll keep attempting to try to figure this out, and if I find a solution, I will update.
cbrvnm said:
Believe me, I have attempted everything without any success. I guess I'm going to stay on my current ROM until I get the time to deal with all of this, and hoping that for whatever reason I don't have to reboot my phone, or that it randomly reboots in order not to deal with the problems. I have always wiped going/coming from different ROMs, but have never experienced this before, and it is very frustrating especially when I like to try different developers mods. I'll keep attempting to try to figure this out, and if I find a solution, I will update.
Click to expand...
Click to collapse
Keep trying different ROMs and different strategies of when you wipe/restore stuff. It's quite interesting that theoretically identical phones can have different responses to the exact same actions. 2 people can install a ROM in the exact same way and for 1 it will work, the other it won't. You just gotta work it out until you figure out how to manage your particular issues.
Yeah, I hear you. It's just very frustrating when in the past I have switched ROMs on all the phones that I have ever owned without any problems until now. But I'll try different methods and see what happens. I appreciate everyones input. Thanks. Oh, and if anybody has any other suggestions, please, share.
Ok, I was able to get Pyramid3D v0.8.0 working so far. I flashed with superwipe about 3 times then installed the ROM. I did not sign into my account, and installed my apps from titanium first, and then signed in. I got several reboots with setcpu so I unistalled it. I also get a few market fcs. Now the problem that I have is that I installed the 4EXT recovery and my phone is unable to play my music files through any of the music players. I am able to open them with astro, but not music player. But I guess I'll try to figure this one out now. Thanks for the advice.
The Janitor Mop said:
All I know is that wiping everything before flashing a new ROM does not guarantee that you won't get FCs and soft reboots.
For example, I did a factory reset, wiped cache, wiped dalvik, and then did superwipe (yes I know redundant), and then flashed a ROM and I thought nothing could go wrong. Then while setting up I went ahead and setup my google account during the setup process, and once I was finished I began restoring my apps+data from Titanium Backup. While that was happening Market started auto-reinstalling my apps, and this instantly conflicted with the fact that I was doing the same thing from TB. It caused a few of my apps to FC all the time. So make sure you skip adding your google account during setup.
You can also get stuff to go haywire if you restore system data from TB. Doing so will conflict with the ROM and cause FCs and reboots. For example, I didn't know how to easily back up texts and contacts for a while, and I would go in to TB and restore everything that said something like mms, messages, texts, messages widget, etc. and doing so actually caused my messages to go haywire. Same thing with contacts. The only things you should be restoring from TB are your user apps+data. As already noted, you should also superwipe before restoring a nandroid because it is exactly like flashing a new ROM. If you're on a ROM you just flashed that has 1 version of superuser, and then you go straight into recovery and restore a nandroid without wiping everything first (and has a different version of superuser), you're going to get issues with superuser.
The rule of thumb when it comes to avoiding FCs and reboots is to avoid letting data conflict. Don't mix ROM data, don't mix app data, don't restore system settings from your old ROM on your new one, etc.
Click to expand...
Click to collapse
Good post. I didn't realize I should be doing so much wiping even before restoring a backup.
Incidentally, I'm kicking myself now, but in the excitement of flashing my first custom ROM, I forgot to backup my original system. Doh. It's the only time I haven't backed up before changing ROMs, but that's arguably the most important backup to make.
Hi,
I'va had CM7 a10 flashed on my Sensation for a few days. A couple of days ago I've decided to get back to Stock ROM, and then the problems started. Before installing CM7 everything was fine. After restoring my backup from before flashing CM7 weird things started to happen (apps dissapearing, settings changing on their own, hangs, and other stuff). So I've done a SuperWipe a few times, and flashed a completely new Stock ROM via USB using: RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed file. Then I've done a few factory resets, just in case. But still weird things are happening (eg. now I have a clean phone - once again - and trying to setup the sync options and the options app hangs everytime. and installing something from market is like praying for a miracle). I've tried doing factory reset, clear cache/dalvik (but with dalvik CWM recovery says that the partition or files wasn't found). Don't know what to do. Does anyone have any ideas ?? Please help. Phone worked fine before, and after CM7 everything is f*cked up
Wierd, looks like you've tried everything I could think of while reading the post.
Do you still have a nandroid backup of CM7, if so does that work if you restore ?
Can you use ADB to get to the phone ? If so you could check some things from there.
When you installed the RUU from the PC, did it install without errors ? Presumably you had to re-install CWM after that.
CM7 nand backup works fine after restore.
I can use ADB to comunicate with the phone.
No errors while updating RUU.exe / CWM recovery flashed without problems also after that.
I think that there's something screwed up with the file permissions.
I've downloaded and installed about 20 apps since the last HR, and now I have about 40 apps more queued in Market, and as before the downloads are stuck every 1-2 apps. Then I have to restart to CWM recovery and run fix permissions. After that another 1-2 apps will download and get stuck again, and so on...
Anyone has any ideas what the hell is going on ? Because my I'm getting more then irritated by this, and beggining to think that the best solution will be to send my phone flying through the window.
A few questions first.
What country are you in?
Who is your carrier?
What version did your phone originally come with? I believe 1.5xxxxx RUU was released recently, but I could be wrong.
Did you ever change your CID?
Have you ever flashed a new radio and RIL?
Did you copy all of the data from your SD card to your computer, then format your SD card using the phone?
Answer these questions and try the SD card thing, then report back. I may be able to help.
Poland.
T-Mobile (Sensation) / Play Mobile (Gio)
Don't remeber what version my Sensation originally came with - I have a 1.50.401.1 RUU that I'm flashing with currently.
Yes, I've changed CID to 11111111 some time ago, but I'm back to original HTC__001 now.
No I haven't changed my radio or RIL.
I've tried formatting the SD card using the phone, my laptop, my linux NAS, my other phones.
The weird thing is that yesterday all of this was progressing. It came to a point that after a factory reset or even a whole ROM reflash nothing would install (not even Market update). And this also started to happen on my Samsung Gio. So after very very very frustrating evening, and part of the night I gave up. And in the morning it was still the same (on both my android phones). But now things are starting to work (updates/installs). So I think I'm going to blame the whole thing on Google and Market. I'll see what happens while I'll install all my apps in the next few hours.
Still have to restart the phone every 1-3 apps installed. This is driving me crazy
I followed the instructions exactly on this page: http://forum.xda-developers.com/showthread.php?t=1663169
CM9 seemed to work fine for a while. I installed Titanium Backup and brought back my apps and just a bit of system data (contacts, voicemail, texts, etc). After I had restored those things, it said it suggested a reboot. I did that, but now it just reboots over and over. I can't get in to the OS for more than a few seconds before it reboots again. Help please!
As that thread specifies, I have a MX2 from CSpire. For now I don't care so much about getting CM9 working as just getting my phone back to a working state. I have both a nandroid and titanium backup on the sd card. I just need very specific instructions on how to get back to the way it was (2.3.6) given that I can't get in to the OS.
Edit: Pulling the battery doesn't resolve anything
Does it let you stay in long enough to remove the app/settings you restored? Are you able to get into recovery mode at all?
If you can get into recovery you might first want to try Fix Permissions and see how that works. If this does not solve it then consider doing a factory wipe and start restoring your apps/settings again one by one and rebooting in between until you get to the particular one that started your reboot problem.
What ROM were you on prior to CM9? Although they should be largely universal sometimes there are some slight changes in custom ROMs that might work well in many other ROMs but not in a select few. Other times it is an app that is not compatible.
The post below might be of some help since your phone seems to have a different method of getting into recovery than what I have dealt with so far.
http://forum.xda-developers.com/member.php?u=4395758
Factory Restore DX2
This might help. It's a factory restore, like you just bought it. http://forum.xda-developers.com/showthread.php?t=1317707
After much sweat, tears, and button pressing, I have gotten it back to stock CM9 and it seems to be behaving as expected. I am going to install apps one by one and reboot between every install. Hopefully I'll find the culprit soon enough.