Related
any time i try to install anything from the market, it hangs in starting download and never goes. then FC
i recently followed the guide here to root my phone. everything works fine on the phone, only problem im having is with the marketplace.
i get a FC
"process com.google.process.gapps has stopped please try again"
dont know what the problem is, did another g1 just before i did this one and havent had any issues. does the size of the SD card matter? the one i use is a 2gb the other is a class 2 8gb. any help would be greatly appreciated. i want my phone back dangit
What rom are you on? Cyanogenmod by any chance?
If you're on Cyanogenmod rom then you need to wipe, wipe ext and dalvik, flash defanged 1.6 and re-flash CM again. That should do it.
If you're NOT on CM rom then wipe your phone, dalvik and re-flash your rom.
But, BEFORE doing any of that, try going into Settings-Applications-Manage applications and wipe data from Market, that just might do it.
Good luck
im running the most recent version of Cyanogen (4.2.15.1)
so just wipe everything and reflash it? would the size of my SD card have anything to do with it?
Sd size has nothing to do with your market.
silver2kgti said:
im running the most recent version of Cyanogen (4.2.15.1)
so just wipe everything and reflash it? would the size of my SD card have anything to do with it?
Click to expand...
Click to collapse
Wipe and reflash rom...
I had the same problem today. I went to wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod and followed the directions under: Flash Android1.6 & CyanogenMod latest and all was well. (if you don't install the signed-dream_devphone_userdebug-ota-14721.zip file in the last step the market and contacts won't work.)
EARLY this morning I decided to try out a new ROM. I flashed Clockworkmod recovery and installed Fresh 2.1.1 from my SD card. Now my phone is stuck in a constant loop of trying to boot up. This same process went fine when I installed Damage Control a few weeks ago. Only thing I've done since then was partition my SD card (also done thru Clockwork app). I would really appreciate any help. Thanks in advance
ksharp5580 said:
EARLY this morning I decided to try out a new ROM. I flashed Clockworkmod recovery and installed Fresh 2.1.1 from my SD card. Now my phone is stuck in a constant loop of trying to boot up. This same process went fine when I installed Damage Control a few weeks ago. Only thing I've done since then was partition my SD card (also done thru Clockwork app). I would really appreciate any help. Thanks in advance
Click to expand...
Click to collapse
Wipe everything (data, dalvik, and your SD card) and reflash. Yes, I know you just partitioned that's probably the problem.
This sounds like a silly question, but would a complete wipe UNDO the partition? Or is that just a way to get the system to wipe ext?
ksharp5580 said:
This sounds like a silly question, but would a complete wipe UNDO the partition? Or is that just a way to get the system to wipe ext?
Click to expand...
Click to collapse
it just wipes the ext it doesnt undo the partition
I'm in recovery mode right now. Wipe Dalvik is in advanced options. On main screen I see wipe data/factory reset. Is that the one I want?
ksharp5580 said:
I'm in recovery mode right now. Wipe Dalvik is in advanced options. On main screen I see wipe data/factory reset. Is that the one I want?
Click to expand...
Click to collapse
You want both data and dalvik at a minimum. If you want to try to reflash without reformatting your card, do the following:
Boot to recovery
Wipe data/factory reset
Wipe dalvik
Flash the ROM
(optional but I always do this anyway - takes 10 seconds and is extra insurance)
Wipe data/factory reset
Wipe dalvik
Boot
If that doesn't work, I'd recommend removing your microSD card and formatting it cleanly on your PC (fat32 format) and re-copying the ROM and attempting the above again.
Give it a go and report back.
if you're using the latest version of clockwork recovery, it's not compatible with a2sd on any rom but darch. I suggest godspeed or amon ra 1.6.2 if not running DD 2.7
Question, why would u wipe after installing the rom?
Sent from my ADR6300 using XDA App
no reason to, but most roms it won't hurt anything, as it only wipes /data and /cache, however, some roms do add apps to /data/app on flashing, and you would be removing those apps then.
Is that a Hero thing or is that in general?
I just had someone test the ClockworksMod on Darktremor Apps2SD for a Nexus One and it worked just fine.
danaff37 said:
if you're using the latest version of clockwork recovery, it's not compatible with a2sd on any rom but darch. I suggest godspeed or amon ra 1.6.2 if not running DD 2.7
Click to expand...
Click to collapse
I don't know. Clockwork mod gave me a lot of problems. Stick with amon ra based recoveries and had much fewer problems.
Sent from my Hero CDMA using XDA App
Actually, was just looking back into it, and I may be wrong on it's compatibility, but it is just in my experience that it doesn't work too well for whatever reason. I like the idea of some of the features it offers, but it never worked right on backing up and restoring for me, and I may have just assumed that was the reason. Our I may have confused it with amon ra 1.7
Sent from my Hero CDMA using XDA App
I use Godspeed and been really happy with it. I was just curious since I've never used ClockworksMod.
danaff37 said:
I don't know. Clockwork mod gave me a lot of problems. Stick with amon ra based recoveries and had much fewer problems.
Sent from my Hero CDMA using XDA App
Click to expand...
Click to collapse
Hey sorry if this has been asked before i couldn't find it anywhere so there is some problem with my phone i don't know what is happening every time i use to install a new Rom it use to install perfectly without any fc's boot loop errors etc, but from past 2 days i don't know why any ROM i try to install (even the one which i use to work perfectly) will not install perfectly there will be fc's boot loop error wont pass the X when i switch on the phone. Please help its driving me crazy
Make sure your wiping old data in recovery.. and if flashed a new kernal or radio could also cause a problem too
ilostchild said:
Make sure your wiping old data in recovery.. and if flashed a new kernal or radio could also cause a problem too
Click to expand...
Click to collapse
yes i did Wipe data/factory reset ,Wipe cache,Wipe Dalvik-cache but just now i discovered that after doing this and still last installed rom has not been wiped its still there wtf what should i do and yes i did install 2.6.34.1_AVS-925mV_BFS_1113Mhz kernel how do i completely wipe everything???
Umm also do wipe sd partition, then do another wipe factory and cache-.. then do a repair sd then try to flash new rom.. this is what i usually do when i install new roms
still no luck i even did clear storage then wiped everything and i dont use app2sd(ext) i dontunderstand what to do i even tried with the clockworkmod's recovery still the same
sorry man, My only guess and idea is try to flash back to a normal kernal, then flash rom.. only thing i can come up with atm, or you can wait and see if some one that comes up with a better solution
where can i find norman kernel or any kernel which can fix this?
Okay the first question:
Ive rooted my device using Unrevoked 3.22 at my HTC Buzz (Wildfire) 1.25 (I think thats the version, its 2.1Update1). And now i maybe want to unroot my phone to install the updates (The 1.27 update doesnt install, is there a solution to this without unrooting?) So, on to the question. How to unroot my device when ive used Unrevoked 3? I rooted it on my brothers MAC OSX, becuase its much safer in my opinion.
Second question:
Okay, Now i have installed the CM 6.10 Stable version. How long will it take to boot? It has been in the boot state for 2 hours and 15 minutes for now. Ive wiped the SD Card and Cache and the Factory reset before install. It does only say HTC with a white blank screen and green letters (as normal).
Thanks for your time reading!
Yours
Antezz
It took me less than 15 minutes. Obvious suggestion, but have you tried turning it off and on (pull the battery and try again).
Why did you wipe your sd card? Lol
Sent from my HTC Wildfire using XDA App
kevin2516 said:
Why did you wipe your sd card? Lol
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Get cyanogen on your sd card, and try to flash it again?
argeoff said:
Get cyanogen on your sd card, and try to flash it again?
Click to expand...
Click to collapse
Okay to be honest i didnt really wipe my SD card. I have tried rebooting this 2 times, and Reflashing it 3 times. It doesnt work. I tried to flash openfire 2.3 today and it works perfectly, but ive heard that the Cyanogen is much better.
howzit man.
restore your original backup with nandroid.
then .
1.) wipe cache
2.) factory reset
3.) go into advanced on clockwork recovery and wipe dalvik cache.
I had the same problem! this works
if not, redownload CM and transfer to your phone again. and go to number 1
let me know how it goes..
You should wipe your /CACHE, /DATA, /SYSTEM, /SDCARD, /SD-EXT
That way you'll be sure NOTHING will be on your phone...
After that, connect your phone with USB to pc. Mount the sdcard.
Put Cyanogenmod.zip on it. Unmount it. Reboot into recovery.
You select: under main-> clear cache, clear default settings (or something like that), under advanced -> clear Dalvik cache, clear Battery status.
Now you just flash the zip on it and everything will be just fine... trust me...
Let me know how it worked out for you. k?
Just make sure that everytime your flash a .zip to the device you give it time to
settle down in the ROM... so that means you'll need to restart after each .zip you flash.
That's what I do and I've never head any problems with it.
Greetings, Jason
@Jason
Thank you!
It worked perfectly. And i have no further questions.
It booted after 10 min, ít started to show the costum startup screen after appox. 30 sec. THANK YOU!
Antezz!
Hey guys-
I just tried to update from cm7.0.2 emmc stable to the nightly 64, and after flashing it and rebooting my nc is locked. It boots to the word android on the left top side and the it goes to dark screen! I hope someone can help me!
Thanks In Advance,
Jim
Jimbo67 said:
Hey guys-
I just tried to update from cm7.0.2 emmc stable to the nightly 64, and after flashing it and rebooting my nc is locked. It boots to the word android on the left top side and the it goes to dark screen! I hope someone can help me!
Thanks In Advance,
Jim
Click to expand...
Click to collapse
Jim,
This question's been answered in other threads already, but here's the link to the one specifically regarding this problem. I included it in your response to this question on the other thread as well. Good luck....
http://forum.xda-developers.com/showthread.php?t=1068309
What a disaster!!! I am Bricked! I wish now, that I had Never left 7.0.2.
I cant even boot into CWR!
Any Ideas?
Jimbo67 said:
What a disaster!!! I am Bricked! I wish now, that I had Never left 7.0.2.
I cant even boot into CWR!
Any Ideas?
Click to expand...
Click to collapse
You're NOT bricked...... The Nook gives boot priority to your sd drive. Worst case scenario, you need to use a bootable recovery sd to reflash a stable version of CM7.
First things first..... Don't panic. LOL
1. Power down.
2. Power up holding both the power button & the n button for 6 seconds.
Does that get you to recovery?
hockeyfamily737 said:
You're NOT bricked...... The Nook gives boot priority to your sd drive. Worst case scenario, you need to use a bootable recovery sd to reflash a stable version of CM7.
Click to expand...
Click to collapse
I just put a new 3.0.2.8 .img file on my sd card should I put it in and see if it boots into CWR from the card? If it does, before I flash 7.0.2, what should I format? Just the cache?
Thanks!
Jimbo67 said:
I just put a new 3.0.2.8 .img file on my sd card should I put it in and see if it boots into CWR from the card? If it does, before I flash 7.0.2, what should I format? Just the cache?
Thanks!
Click to expand...
Click to collapse
First try booting into your EMMC recovery the way I just posted ( power & n button for 6 seconds).
If that works.... do a full wipe and restore your backup of 7.0.2 stable.
It won't boot into recovery with the power and N button. Tried it many times! I still get the android for a few, and then a small dot in the upper right!
Jimbo67 said:
It won't boot into recovery with the power and N button. Tried it many times! I still get the android for a few, and then a small dot in the upper right!
Click to expand...
Click to collapse
Ok.....Now it's time to use your recover SD. Put it in, boot to recover and do a full wipe (System, Data, Cache, & Dalvik). Then reflash CM7.0.2. When you're done and booted into CM7, report back for follow up instructions, so this doesn't happen to you again.
Man, I got all the way to wipe dalvik cache and it locked up on the advanced and debugging menu??? oh my god!
Jimbo67 said:
Man, I got all the way to wipe dalvik cache and it locked up on the advanced and debugging menu??? oh my god!
Click to expand...
Click to collapse
Yeah that's perfectly normal. Hard shutdown and boot right back to recovery. Flash the rom and gapps (no OC kernel yet....I'll explain once you're up and running again).
Whew! I am back up on cm7.0.2! Seems that the nightly 64 and the 0424 OC kernel dont play well together!
Jimbo67 said:
Whew! I am back up on cm7.0.2! Seems that the nightly 64 and the 0424 OC kernel dont play well together!
Click to expand...
Click to collapse
Make sure you go back to the market and re-download Rom Manager. Once you do that, flash recovery to your EMMC (device memory). Make sure you keep that recovery up to date. The SD recovery you just used did not flash your machine.....Your machine booted from it.
Now for your overclocking info. The recent CWM update requires the use of a kernel with an updated ext.4 script, explained in the following link.......http://forum.xda-developers.com/showthread.php?t=925451&page=239
Going from stable to nightly requires only a Cache & Dalvik wipe + the flashing of the ext 4 OC kernel, however returning from nightlies to stable will require a full wipe (system, data, cache, & dalvik) for safety's sake.
Always make back ups of good rom's, use titanium to back up your apps & data, keep your recovery up to date, read, read, read.......and if I helped you out click my thanks tab
just one more question--what is the best way to add the OC kernel to cm7.0.2 now, or should I update to 7.0.3 " Gasp"
Jimbo67 said:
just one more question--what is the best way to add the OC kernel to cm7.0.2 now, or should I update to 7.0.3 " Gasp"
Click to expand...
Click to collapse
I'd wait on 7.0.3 to see what's up with it..... Some people were reporting the MD5 sums not matching. Stick with 7.0.2, follow the threads to see what's up with any rom you run, and then once you know all's well (from reading the posts).....then flash the update. Keep in mind it's always easier to read first and flash after, then to freak out thinking you bricked your device and spend 2 hours in a panic trying to fix it.
For the OC kernel boot into recovery (the one you should have flashed to EMMC from Rom Manager), and flash the 4/24 kernel with the updated script for ext. 4
hockeyfamily737 said:
Make sure you go back to the market and re-download Rom Manager. Once you do that, flash recovery to your EMMC (device memory). Make sure you keep that recovery up to date. The SD recovery you just used did not flash your machine.....Your machine booted from it.
Now for your overclocking info. The recent nightly builds are Android 2.3.4 and require and ext 4 kernel..... available here in post 2382 of this thread......http://forum.xda-developers.com/showthread.php?t=925451&page=239
The stable builds are Android 2.3.3 which require the kernel you have been using right along (prob. the 4/24 1.3 GHz).
Going from stable to nightly requires only a Cache & Dalvik wipe + the flashing of the ext 4 OC kernel, however returning from nightlies to stable will require a full wipe (system, data, cache, & dalvik).
Always make back ups of good rom's, use titanium to back up your apps & data, keep your recovery up to date, read, read, read.......and if I helped you out click my thanks tab
Click to expand...
Click to collapse
I would like to get on the Nightly band wagon, and use the ext4 OC kernel but this link does not work for me. Is there another place to get the 1.3 OC kernel that will work for nightly builds?
Thanks!
Jimbo67 said:
I would like to get on the Nightly band wagon, and use the ext4 OC kernel but this link does not work for me. Is there another place to get the 1.3 OC kernel that will work for nightly builds?
Thanks!
Click to expand...
Click to collapse
http://www.unvisible.org/files/ext4-...mmc-042411.zip
Here you go.