Hello ladies and gents, I'm in the process of completely revamping my Hero. I am not new to CM, was on 6 and then 7.0.3. Was getting sick of low storage space so decided to try FireRats custom partitions (set it to 100 4); seemed to run without a hitch as CM booted no problems. However, even though I DEFINITELY installed gapps, Market doesn't show! Have tried reflashing gapps from CWM 2.5.7 three times now, and each time, to no avail. I am very confused, and don't know where to go from here. I ran unrevoked last night and am now S-OFF, don't know if that might have something to do with it, but I can't imagine it does. Also of interest is that Rom Manager tells me I don't have SU privileges! Anyone have any ideas? Thanks a ton in advance!
T
P.S. Just realized I should clarify I ran unrevoked last night so I could run Sprint RUU to install PRL 00001. That is working beautifully. FireRats and CM7.1 I did about two hours ago. Thanks again!
Related
ok guys
can a ROM that has been successfully downloaded and installed on the g1 and run for several weeks degrade?
i mean the actual .zip file
i was using drizzy blur_hero for the longest but when i tried out the motoblur i had problems
i went as far as to reformat and repartition my sdcard but it seems that every time i reinstalled after that i had lag and massive FC all the time...
never happened till i went playing with another ROM
any info would be appreciated cuz im curious
I've been tinkering with this phone for probably around a year now. I have a good understanding of flashing and whatnot, but that is probably the extent of it. I've had tons and tons of roms on this phone, and never once been given trouble.
Recently, I flashed to King's Eris2G1 rom, and that seemed to start my problems. I had lots of problems getting this ROM to work properly. Eventually, I got a working load, but I noticed that Apps2SD stopped working. Everything else seemed to work OK so I ignored it and used the rom.
Now, this morning, I went to flash his Legend2G1 rom, and got an error during verification that files were corrupt. Redownloaded and tried to reflash, same thing. So I said screw it, tried going back to an older 1.5 senses rom (I forget which, MLING or something like that), and I got errors on verification for that too. I never had any trouble previously installing that rom. So, I tried Eris2G1 again, and got the same errors there. Last time, it always flashed fine, just worked a little buggy.
So I tried Kings AOSP2.1. That worked. It flashed fine, booted fine, but I did notice, Apps2SD isn't working here either. So, my thoughts are all the Senses roms failed because they are larger and install files to the SD card, where as this smaller rom does not?
I went to test my theory by popping in a different SD card, but I got the exact same errors. So, it's not the card, it's the phone, but it appears to be related to the card. I am able to access the FAT32 partition without problems. I tried repartitioning the card many times (96-128MB swap, 128-512MB ext2) and I tried with ext2, 3, and 4. No luck no matter what.
So, does anyone have any ideas as to 1.) what happened and 2.) how can I fix it? I am not 100% sure what all I have on my phone as far as SPL, recovery, ect go. On recovery, it says "Build: RA-dream-v1.5.2". No idea what SPL I am using... I flashed it a little bit ago to whatever a particular rom I was interested in required. All I know is I never had a single problem like this, and now even the roms that used to work like a champ are not functioning. I've got my phone to a usable state with this current ROM, but i'd really like to play around with the Senses roms more (nevermind the fact that I want A2SD back). Can anyone help?
EDIT: For ****s I just tried flashing 1.6.2 recovery, as well as reflashing radio and SPL. Didn't make a difference.
i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.
I have been lurking and reading for a couple of weeks now. I bought a used NC with 1.1 and used Autonooter to root it. Works great.
I bought a second NC which had the 1.2 s/w on it. I used the manualnooter process to root it. That works pretty well.
Now I'm thinking about getting into the nightly CM7 game. I'm wondering is there anything I need to watch out for with the 2 NC's I have if I do this. Do I have to take them back to stock? Can I just follow the CM7 instructions?
Any insight and guidance would be appreciated
50 views and no replies. If you read this and can help I would really appreciate some info. I'm reluctant to proceed until I hear from someone who has traveled the road before. Thanks
You can run CM7, stable or nightly, off of an SD card. You don't have to change anything on your Nooks to do this. In fact, they don't even need to be rooted. Running CM7 on the SD card will not change anything on the built-in memory of the Nook.
Look for the "size agnostic" thread, follow the directions, and you're good to go.
ps. I enjoy your music.
yeah, just follow the instructions on flashing cm7 for the first time. and make sure you understand the CWM instructions. you may want to try a stable rom for now. there are lots of battery and kernel issues right now with the nightly builds. but not to fear the devs are working hard to fix them. just stay with the stable's and your be fine. I hope this was helpful...
boxcar8028 said:
yeah, just follow the instructions on flashing cm7 for the first time. and make sure you understand the CWM instructions. you may want to try a stable rom for now. there are lots of battery and kernel issues right now with the nightly builds. but not to fear the devs are working hard to fix them. just stay with the stable's and your be fine. I hope this was helpful...
Click to expand...
Click to collapse
is this the one you mean?
http://forum.xda-developers.com/showpost.php?p=11452450&postcount=19
Well, I went ahead figuring "How hard could it be anyway?".
I did the nand backup with CWM 3.0.2.8
I then ran ROM manager V4.2.0.2 from internal memory.
I choose the option that allows me to download ROMS.
I chose CyanogenMod, and then chose 7.0.3.
I downloaded the ROM
I then chose Install ROM from SD card
It asked me about clearing caches, etc and I chose the default values already checked.
It installed without errors.
I rebooted and it got to the last part of the boot process where the word "color" is rapidly changing and stayed there indefinitely,
I rebooted with CWM on the SD card and tried to reinstall the Manualnooter I loaded on this NC a week ago.
Rebooted. Still hung up.
I copied my nand backup to the CWN SD card and chose restore.
It booted back to my manualnooter install successfully.
So I'm successfully back where I started.
Can someone help me understand what I did wrong on what I need to do to make it work? Thanks
Not sure what went wrong, but I would also suggest trying verygreen's size-agnostic approach. You keep your manual nooter and can run CM7 from an SD card to see if you want to go all the way and remove the stock BN software.
Try this thread:
http://forum.xda-developers.com/showthread.php?t=1000957
Or, if you want to go crazy, you could try racks' dual boot SD card image of Phiremod 6.2 (a variation of CM7) and Honeycomb. That's what I'm using and Phiremod works great (aside from battery life ) and honeycomb is just plain slick to use.
http://forum.xda-developers.com/showthread.php?t=1045018
I loaded CM7 7.0.2 stable and was able to get it going. Thanks
Hey all, I'm running CM7 7.1 rc-1... I just installed dalingrin's latest oc kernel... And it killed my wifi.. It's really bugging me. My nc is currently oc'd @ 1200.. With a min speed of 600. Is the kernel killing my wifi? Or is it the overclocking?
Thanks in advance.
Hi,
interesting. I had the same experience. My case went a little bit further than that as I lost my whole config after trying to fix it ... long story short, after fixing my nook and re-installing back to stock (1.0.1 then upgrade to 1.3). I tried again, installed same distro on SD but I put all the zip files at the same time on the sd card for install (7.1, gapps and OC); everything got installed and no more wifi problems. I also upgraded to full nightly 212. So far, so good.
I also noticed something: after testing a few apps, I would get a weird behavior. In rom manager, fix permissions would fix most of the issues.
Olivier! said:
Hi,
interesting. I had the same experience. My case went a little bit further than that as I lost my whole config after trying to fix it ... long story short, after fixing my nook and re-installing back to stock (1.0.1 then upgrade to 1.3). I tried again, installed same distro on SD but I put all the zip files at the same time on the sd card for install (7.1, gapps and OC); everything got installed and no more wifi problems. I also upgraded to full nightly 212. So far, so good.
I also noticed something: after testing a few apps, I would get a weird behavior. In rom manager, fix permissions would fix most of the issues.
Click to expand...
Click to collapse
hmm.. interesting. I'll give that a try and tell you what happens.
update:
I tried to install the stock firmware by deleting cwm, repartitioning boot to stock (after installing stock 1.1)... now it just loops on the "nook color by bn" screen. any suggestions?
Follow the instructions here and start all over. Choose nightly 200 or higher and make sure you use the latest version of CWR (3.2.0.1): http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
patruns said:
Follow the instructions here and start all over. Choose nightly 200 or higher and make sure you use the latest version of CWR (3.2.0.1): http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
Click to expand...
Click to collapse
brilliant! that worked wonderfully. for future reference, the latest version of CWR seemed to do the trick. thanks!