hello.
i have run into some problems when trying to install the stable mod described in the guide from the sticky post at the top of this category. well more or less, i referenced other guides as well but they were all effectively the same.
after rebooting post installing the cyanogenmod image my phone seemed to be functioning fine. i noticed that the google apps were not available (despite having used the backup and restore proprietary google apps from the recovery menu) so i restarted the phone in recovery mode and flashed the google addon and rebooted again. as soon as the phone came up this time it started throwing up error messages:
"Sorry! The process com.android.phone has stopped unexpectedly. Please try again."
i can dismiss the error dialog but another replaces it. sometimes the process named is different. i cannot recall the other examples right now. i have tried to turn the phone off with the power button, the confirm dialog does appear but is buried under the error messages mentioned above and i cannot get to it to confirm. i have tried holding the power button down hoping there is some hardware shut down. no dice. i am getting ready to pull the battery but thought i better throw this out to the masses before i did so.
huh interesting. it just stopped doing the above. it chimed and then displayed the boot screen in a frozen state.
the only way i deviated from the general directions in the above mentioned post were to flash the google addon package after a reboot as mentioned before.
how safe is it to pull the battery and what would the next steps be? if i wipe the "data/factory reset " and then reinstall the cyanogen img will i be back where i was before the google addon install? i am not really sure what command eliminates the android installation. perhaps i need to do a more extreme wipe of the device. alternatively i can execute a nandroid restore.
now it is back to the dialogs again.
i am mostly concerned that pulling the battery may brick the phone. am i being irrational?
the phone is a nexus one. i am in the uk on vodafone if that is relevant. the packages i installed are the ones listed on posting above.
i did not flash the radio.
any help would be greatly appreciated.
e
edit- i have fixed the issue. i was able to use the adb reboot utility to boot to recovery mode. from there i was able to restore my backup image. i then retried installing the cm and addon packages and kept having the same issue. finally i tried to download a new version of the addon img and that worked. for some reason i had to unmount and remount my sd card after i got everything working again.
correction
sorry the packages i installed were not the ones listed in the post above. they were the ar recovery img (that was the same) the cyanogenmod 5.0.6 image and the google addon.
Related
I literally cant do a damn thing with my Droid 2. This all started when I started noticing an increasing number of Force Close popups. I hadn't installed anything new recently so I just rebooted and dealt with it. At this point, it was a completely stock Droid 2 with only market-approved apps installed.
So, I decided to do a factory restore and... it didnt work. It sat at the recovery screen and did nothing. I pressed search and selected wipe data\cache and it said something to the effect of "Cant open E:\recovery\something" but the Wipe data\cache completed successfully. Needless to say, my issue remained.
So I found the stock recovery SBF and went to flash it... it got to 98% on the final step and then said FAIL. Error message: Failed flashing process. Error verifying Code Group 31 checksums. File 0x4BAF (0x4007031); phone connected. The phone still show SW Update when this occurs, and then eventually "completes", reboots, and boots back up as if nothing ever happened.
So then I tried the root process so I could install rom manager and try EUnleashed or something. The rooting steps all took, and I tried to open the Superuser app it just stuck on a blank screen. So I rebooted, and wtf.. it disappeared.
So then I went to Applications and uninstalled every single application except for Maps, rebooted, and WTF THEY ALL CAME BACK AGAIN. I did this 3 times and each time every single app was reinstalled and working after a reboot. Only now I cant complete the root process again, and Rom Manager doesnt work.
So, to recap... I cant do a factory restore. I cant flash the stock SBF. I cant root. I cant do f*$&#*$ ANYTHING!
If I cant fix this today I will be giving this junk phone to my 2 year old because that's about the only thing this POS is good for. I never had any of these issues on my Droid, Droid X, or Samsung Captivate. How Motorola could fail so hard while simultaneously succeeding so well with other devices is mind-boggling.
HELP!
lwright84 said:
I literally cant do a damn thing with my Droid 2. This all started when I started noticing an increasing number of Force Close popups. I hadn't installed anything new recently so I just rebooted and dealt with it. At this point, it was a completely stock Droid 2 with only market-approved apps installed.
So, I decided to do a factory restore and... it didnt work. It sat at the recovery screen and did nothing. I pressed search and selected wipe data\cache and it said something to the effect of "Cant open E:\recovery\something" but the Wipe data\cache completed successfully. Needless to say, my issue remained.
So I found the stock recovery SBF and went to flash it... it got to 98% on the final step and then said FAIL. Error message: Failed flashing process. Error verifying Code Group 31 checksums. File 0x4BAF (0x4007031); phone connected. The phone still show SW Update when this occurs, and then eventually "completes", reboots, and boots back up as if nothing ever happened.
So then I tried the root process so I could install rom manager and try EUnleashed or something. The rooting steps all took, and I tried to open the Superuser app it just stuck on a blank screen. So I rebooted, and wtf.. it disappeared.
So then I went to Applications and uninstalled every single application except for Maps, rebooted, and WTF THEY ALL CAME BACK AGAIN. I did this 3 times and each time every single app was reinstalled and working after a reboot. Only now I cant complete the root process again, and Rom Manager doesnt work.
So, to recap... I cant do a factory restore. I cant flash the stock SBF. I cant root. I cant do f*$&#*$ ANYTHING!
If I cant fix this today I will be giving this junk phone to my 2 year old because that's about the only thing this POS is good for. I never had any of these issues on my Droid, Droid X, or Samsung Captivate. How Motorola could fail so hard while simultaneously succeeding so well with other devices is mind-boggling.
HELP!
Click to expand...
Click to collapse
I think you might be overreacting here.
First, I haven't flashed the SBF yet but I do remember seeing the fail screen on original Droid SBF flashes and it was something you could ignore. You booted back into Android, right? That means it worked.
Second, the Superuser app is supposed to show a blank screen because the purpose of it to manage apps to which you have granted to superuser permissions. If you just installed it, there would be nothing listed.
Third, Froyo restores apps if you have "back up my data" checked under Privacy settings.
Fourth, you never mentioned the Droid 2 bootstrapper. I wouldn't expect ROM Manager to work properly without it.
First, no that doesnt mean it worked. I boot back into my exact same Android install as before. Same settings, same notifications, same alarm, same problems, same everything. If it was successful, it would be like a factory restore (Which I cant even do).
Second, ok that makes sense. But after rebooting it disappeared and RomManager wouldn't recognize that it was rooted. Now the rooting process wont work at all when I try and redo it.
Third, I dont think this is the same thing. It's not restoring apps... the apps are there as if they were never removed. Same customizations, settings, etc.
Its like my D2 is stuck with a certain "image" on it, and it wont let me edit, delete, format, reinstall, or reimage. It's infuriating.
Also, ROM Manager works without bootstrapper as long as you have Superuser. Ive used it fine on my Captivate.
lwright84 said:
First, no that doesnt mean it worked. I boot back into my exact same Android install as before. Same settings, same notifications, same alarm, same problems, same everything. If it was successful, it would be like a factory restore (Which I cant even do).
Second, ok that makes sense. But after rebooting it disappeared and RomManager wouldn't recognize that it was rooted. Now the rooting process wont work at all when I try and redo it.
Third, I dont think this is the same thing. It's not restoring apps... the apps are there as if they were never removed. Same customizations, settings, etc.
Its like my D2 is stuck with a certain "image" on it, and it wont let me edit, delete, format, reinstall, or reimage. It's infuriating.
Also, ROM Manager works without bootstrapper as long as you have Superuser. Ive used it fine on my Captivate.
Click to expand...
Click to collapse
Captivate is not a Droid 2. I'd be surprised if it works without the bootstrapper, since that's the only way to flash anything on a Droid 2.
My suggestion is to keep trying the SBF. Once you get it to work, get the SW update and then root. From there, I wouldn't go messing with anything in ROM Manager until you confirm the files are 100% legit for the Droid 2. As far as I know, only a few themes are working without issue on the Droid 2 - the ROMs all have bugs.
The same thing happened to me. I am assuming we were using the same instructions to flash the .sbf. Here is a link to instructions I followed.
http://forum.xda-developers.com/showthread.php?p=8245826#post8245826
I did not heed the red flag I got when I unzipped the .jpg file. I saw some error message and ignored it, and went ahead with the procedure to end up as many others with "fail".
Long story short, I deleated the .jpg file and downloaded it again.
When I used 7 Zip to extract the files, this time I had no error msg and everything went smoothly.
If a moderator can remove this thread, please go ahead!
I dug deeper into fallingup's recovery thread. It never occurred to me that it might make a difference to clear cache and factory reset AFTER doing an update. I did that, which seemed to clear up my FC loop. I fell into a page that asked me what language I was speaking, and was prompted to set up my google account -- which failed. Couldn't connect to data services, not even WIFI. So *228 and Activated my phone (again). Google still wouldn't log in. Went to Settings/Privacy/Factory reset. Selected English, google logged in this time. My phone appears to be completely back to its original stock state. Root is gone. Even bing is back, lovely. Thanks angel12!
... now if I could just figure out why that update.zip paired with the modem.tar that started all this wouldn't sing for me in recovery mode.
>>>>>>>>>>>>>>>>>>
First off, I apologize for cluttering this forum, but I'm at a bit of a loss here. I also failed to find the server for IRC. I'd really appreciate a small push.
Here goes: I got into download mode from the command line. I flashed over my modem with Odin, got a PASS, rebooted fully (shouldn't have done this) with no errors. Next, I popped into recovery mode. From there, I decided to factory reset _and_ wipe my cache -- it seemed like a good idea at the time. It seems like a bad idea now. Finally, I told recovery to apply update.zip from my sdcard. It flat out refused! Complained that the .zip wasn't signed. So, I rebooted.
I then experienced my first FC loop! The culprit is TouchWiz launcher, which just repeatedly closes unexpectedly.
So then I restored the DI01 modem, which didn't change a thing. Next, I ran Stock-i500-VZW-System.tar.md5 through Odin. It updated with no problems.
However, I still have my Force Close Loop, which I expected going to stock would fix.
What I think is really going on is I'd been using ADW Launcher, coupled with an app that switched it to being the 'default'. Something somewhere, must be giving TWiz a hard time.
The good news is I still have adb shell access and root.
* Is there anything I can do to make that homescreen switcher app run on my phone without using a launcher (from shell, for instance)?
* Is there some important point I'm missing about my recovery (I've flashed back everything I changed, at least in my mind)
* Perhaps I could flash something else from Recovery, and that would clear this up?
* It would be great to know what I did that messed this up.
EDIT:
I meant DI01, not "Di05". Nice catch!
It turned out in my case that data wipes were crucial - the factory wipe in system, and the data/factory reset &or cache partition in recovery mode.
http://forum.xda-developers.com/showthread.php?t=782204
Follow this to the letter. Been there, done that. Home Switcher isn't what went wrong. You'll be fine in 10 minutes.
Wait. DI05??? Do you mean DI01 or DJ05? You need to make sure you flash the modem that matches your ROM. Either easy is fine, and probably didn't have anything to do with your force close loop, but make sure they match or you won't be able to text.
And PDA in Odin.
I have tried flashing a couple different roms, including Bonsai, TrulyEpic Rebirth. I get everything up and running, and a few reboots later, I turn my phone on, and I'm back at the setup screen, where you enter your gmail acct info, and it teaches you how to use the Swype keyboard and everything. I get through all that, and i just have a barrage of "this program force-closed" windows. Everytime I do that, I have to start all over. I've had to do this 5 or 6 times since I got the phone on Monday.
What I do is:
Flash DK28 with Odin.
One-click root/clockwork recovery 3.0.0.5
Let the system do the ext4 conversion
factory reset, clear cache partition, clear dalvik cache 3x
flash rom
restore all my apps
then, a few reboots later, I end up with the setup screen, and the barrage of FC notifications.
Am I missing something?
EDIT: WHOOPS. I'm half asleep and didn't read that right. When you say restore apps, are you restoring a cwm backup or are you talking about the app restoration build into the setup wizard?l
Built in setup app.
I used to have this problem too, it was very frustrating. For me, I finally narrowed it down to somehow corrupting the ROM by using the 3-button instant reboot method. Since I was using the no-journaling mod I figured that somehow I was forcing a re-boot while the system was writing something? I don't really know for sure though, but I can say now that I use QuickBoot and avoid the 3-button method, I haven't had any problems. Good luck!
Thanks. I have yet to try the no-journaling mod, nor do I know what the 3 button method is. I've been using a widget called "boot control", but I'll switch back to quick-boot (i've used it in the past) to see if that helps.
So ive been using OmniROM 4.4 on my Samsung Galaxy S3 GT-19300 for over 6-7 months now (since around 22/11/2013). It has all been working as a treat. Two nights ago something seemed to of happened on my phone and few apps disappeared (they had the green android robot logo). I was also notified that some apps have updated. I am unsure what these apps were (my guess would be the googles apps; google books, google movies etc. because they were all next to each other in alphabetical order). So because of this i decided to turn my phone off. When i turned it back on, it would be stuck on the OmniROM Logo whilst booting up. It would be stuck on this for a few hours. So I left it over night. Then the next morning it had booted up and a error message popped up saying "Stystem UID's Inconsistent" with a button saying "I'm Feeling Lucky". So I clicked the button and unlocked the phone. Then the homescreen was black and blank. There was no background image, apps, widgets etc. However, I can access the notification bar. If i had any notifications, for an example a message on kik. I can click on it and it will take me to kik and it can use it as normal. When i click the home button it takes me back to a black blank screen.
So, My first reaction was to create a nandroid backup (of the black blank screen OmniROM) then wipe everything (data/factory, cache partition and dalvik cache) in CWM Recovery v6.0.4.4. After this I restored my old nandroid backup, this is my backup i created before i moved onto OmniROM so it was the Samsung galaxy s3 stock 4.1.2. So once i did this i was again greeted with the error message saying "Stystem UID's Inconsistent" with a button saying "I'm Feeling Lucky". So i clicked the button and set up my device. During this and after this Ive had about a billion pop up error messages saying "Unfortunately, the process com.google.process.gapps has stopped." and "Google books has stopped working" and it did this for all the other google apps. So its pretty clear that it must be something to do with Gapps (Correct me if i'm wrong please). Also, It did not allow me to get anything from the play store apart from twitter and rom manager. snapchat and the google app updates didn't work (that is all i have tried). I had error messages saying that i couldnt download it. I have tried installing gapps and OmniROM again and it works but i still get the error messages saying that gapps and google apps have stopped. I have also restored by nandroid backup of the omnirom (that I did before i wiped everything) and i still get the blank black homescreen.
So, I want to know whether it is gapps that has caused this? If so what do i need to do? Do i need to unistall it and install it again? How do i do that?
All I want is to go back to OmniROM and it works and this problem wont happen again. Also if i can get all my data (apps, pictures etc.) that i saved in my nandroid back that i did when i was on OmniROM (before i wiped everything) then that would be great!
I appreciate it very much if you have read this and helped me out.
Despite you have given lots of details, you didn't specify which GAPPS package you're using. Who's the maintainer of the package? Are you sure it's for 4.4.x?
Nonetheless, get the latest PA GAPPS package. As @TKruzze says on the official thread: "We consider these apps as important as our ROM. It is sad that the ROM scene deals with so many broken/outdated or buggy packages."
Lots of issues could be caused by a messy GAPPS package or a messy recovery.
Now I suggest doing the following:
1) Take a backup of user files (pics, music, etc...) and don't take backup of app data as that could be messy or corrupted or at least take the backup of app data but don't restore it.
2) Download the latest OmniROM nightly, SuperSU and PA GAPPS (stock package seems the one for you) and check the files' MD5 after you download to be 100% sure the files aren't corrupted.
3) Download the latest official TWRP. For the love of Android, it's been stated by OmniROM developers that it's the officially supported recovery.
4) Flash TWRP and do a full wipe (system, data, cache and both SD and internal memory).
5) Do a reboot to recovery after wiping then flash the ZIP's in this order: OmniROM > PA GAPPS > SuperSU (don't flash any custom stuff or addons for now).
6) Reboot into system and restore data gradually. Install most important apps and keep on monitoring your phone for abnormalities and make sure you clean up your SD and internal memory backups from any redundant files before you get them back on the phone (there should be a "clockworkmod" folder that's not needed).
7) All should be fine now.
Notes:
1) Uninstalling GAPPS can be done by wiping the system, cache and dalvik-cache then flashing the ROM again but I didn't suggest that as the data partition is probably already messy.
2) NANDROID backups are ZIP files, you can extract them and get some data manually. You've made a NANDROID on a bad state so you can alternatively restore that before doing any of the above and selectively backup data using Titanium Backup and the files using casual methods.
Hope that helps and sorry for it being long. But such issues are hard to tackle on and you'll be better off doing a clean install.
Happy flashing!
Hi all, wasn't quite sure where to post this so I posted here. I have a Samsung Galaxy S4 SM-S975L (straighttalk) running jflte cm13 and I am having an issue. I usually get much of my advice from googling around and that leads me to xda, so since googling hasn't solved my issue I figure I'd make an account here. the problem I'm having is with Link2sd. When I first installed cm13 link2sd wasn't working, it threw an error for mount scripts, an issue resolved at the following link
http://forum.xda-developers.com/showpost.php?p=65411424&postcount=19
For those who don't wanna click I typed in terminal (on the phone)
su
cd dev/block/vold
ls
ln -s public:179_66 179:66 (my directory was 179_66)
doing so solved the issue.
However after I started experiencing google play error code 504 when trying to install previously installed and uninstalled apps I found that the only solution was a factory reset (even titanium backup wouldn't work).
The first time I factory reset to solve this issue I had reset the SD card and backed up all the data, making sure to re-partition the second partition to ext2 like I had before, and link2sd worked fine.
I again experienced the same 504 issue when trying to reinstall a previously installed app so naturally I did the same process I did previously however this time after I do the terminal process to recreate the mount scripts for link2sd and reboot, and then after reboot I link the apps to the SD and reboot again for any reason, cm13 stays at the "jflte optimized cyanogenmod13" loading screen.
If I pull the battery and remove the SD card and then try to boot, everything boots fine, of course without the apps that are linked to the SD. If I put the SD card back in with the phone on, link2sd demands I recreate the mount scripts again or reboot. no matter what option I choose the phone will stay stuck at the cm13 loading screen. I read in a couple xperia threads something about an init.d script where the solution to that being to install init.d toggler from the play store and enabling init.d. I have tried this and still find myself stuck at the cm13 loading screen.
Can anyone offer an alternative solution to the ones that I have tried? I'm open to anything.
I think you should flash the stock firmware. There might be no other way. Either install the backup if you've made previously using custom recovery.
munimjaffer said:
I think you should flash the stock firmware. There might be no other way. Either install the backup if you've made previously using custom recovery.
Click to expand...
Click to collapse
I haven't tried that yet, but that will have to be my next step. I've tried wiping dalvik&cache and then wiped everything and reinstalled the original cm13 zip I had, but I still get the same result. Link2sd was working for a time, so something happened to make it not work and continue to not work now..
noozman7190 said:
I haven't tried that yet, but that will have to be my next step. I've tried wiping dalvik&cache and then wiped everything and reinstalled the original cm13 zip I had, but I still get the same result. Link2sd was working for a time, so something happened to make it not work and continue to not work now..
Click to expand...
Click to collapse
Hmm I'm certain that would surely work for you.
I fixed both the issues. Very stupid solutions, almost too stupid to mention, and I feel stupid for not thinking of it. Solved the stuck at boot issue by not linking all the apps at once and instead linking five or six at a time then rebooting and repeating until all my apps were finally linked. Solved the google play 504 error by going into link2sd and selecting the "clean up second partition" option, the apps wouldn't install because there were still files linked from the previous time I had installed it. Thank you for your help.