I can't seem to get Update All to work. I am rooted on cyanogen mod 7, running 2.3. When I click Update All most of the downloads/installs fail. and the eris is dog slow. Do I need to go back to updating one app at a time?
My Eris just hung then rebooted trying to use Update All. Oh well.
You don't say which ROM.
I had that problem with GSB, but I do not with CondemnedSoul's CM7 ROM. (Though, to be fair, GSB would eventually all update if I just kept doing it.)
my phone just started recieving an OTA froom verizon i am rooted on nils rom. i didnt knoiw a OTA was even scheduled. anyone else getting this?
Is this a different OTA from the one that was pushed out a week or 2 ago?
ota????
You gotta read the forums first bud. I all over the place.
The OTA gives you a new radio & a few other minor things, but you need to relock/unroot & reflash it to stock ROM to get it.
ok. got my phone 3 days ago, kept it stock for 2 days figured i would get the OTA then if it wasnt preinstalled, thanks
Just wanted to say a heartfelt THANK YOU to Zaclimon and others involved in CM11 for the YPG1.
My 11 yo son has had one for about two years, bought with his own birthday money when he turned 9, and loved the size of it but was increasingly running into apps and games that would no longer run on GB (Clash of Clans specifically). I've been on Android since the HTC G1 and have rooted and ROMed many Android devices over the years so he finally pestered me to see if I could find anything for his US model YPG1. So two nights ago I started digging around and apparently came across a lot of old and outdated information first because I banged my head on this thing for about 8 hours straight with various kernels and ROMs to no avail. Flashing a new kernel and CWM (STeVE's was the first I found) was very simple but finding a ROM that was current and actually worked was... rough. After 8 hours of no practical progress (except that I was now very familiar with Odin, Hemdall, Samsung, and the YPG1) I finally just flashed back to stock and was just thankful that at least still worked.
Next morning, after just two hours of sleep, I found this thread -- http://forum.xda-developers.com/showthread.php?t=2537248. Given the hassles of the night before I took a deep breath and braced for more hardship... but in just a short time and with no hassles whatsoever I had his player flashed to Zaclimon's CM11 and with BaNkS minimal gapps for Playstore access.
Later that day when my son saw he had KitKat 4.4.3 and could now run (and even screenrecord) Clash of Clans on his trusty YPG1 he was open-jaw awwed at me. So, thanks Zaclimon, BaNkS, and so many other devs who helped make this dad a hero to his 11 yo son... at least for a day or two.
knetknight said:
Just wanted to say a heartfelt THANK YOU to Zaclimon and others involved in CM11 for the YPG1.
My 11 yo son has had one for about two years, bought with his own birthday money when he turned 9, and loved the size of it but was increasingly running into apps and games that would no longer run on GB (Clash of Clans specifically). I've been on Android since the HTC G1 and have rooted and ROMed many Android devices over the years so he finally pestered me to see if I could find anything for his US model YPG1. So two nights ago I started digging around and apparently came across a lot of old and outdated information first because I banged my head on this thing for about 8 hours straight with various kernels and ROMs to no avail. Flashing a new kernel and CWM (STeVE's was the first I found) was very simple but finding a ROM that was current and actually worked was... rough. After 8 hours of no practical progress (except that I was now very familiar with Odin, Hemdall, Samsung, and the YPG1) I finally just flashed back to stock and was just thankful that at least still worked.
Next morning, after just two hours of sleep, I found this thread -- http://forum.xda-developers.com/showthread.php?t=2537248. Given the hassles of the night before I took a deep breath and braced for more hardship... but in just a short time and with no hassles whatsoever I had his player flashed to Zaclimon's CM11 and with BaNkS minimal gapps for Playstore access.
Later that day when my son saw he had KitKat 4.4.3 and could now run (and even screenrecord) Clash of Clans on his trusty YPG1 he was open-jaw awwed at me. So, thanks Zaclimon, BaNkS, and so many other devs who helped make this dad a hero to his 11 yo son... at least for a day or two.
Click to expand...
Click to collapse
Woow talk about enthusiasm. Happy to see that you managed to get your son's YP-G1 running CM11. I'm sorry though that you had to pass through a bit of pain to get it running. There was a lot of process to get the whole thing done but we're settled on that model so don't worry about it. I have my main computer cooking up a new CM build soon (a 4.4.4 based and fixing up the towelroot exploit) so you can get up-to-date.
Thanks. The thing I beat my head against the most was one of the first ROMs I flashed, just in attempt to get his YPG1 working even on GB again, was SGS_PORT_ARIO. This ROM is for the YPG1 but is a port of an i9000 ROM. On my son's YPG1 ARIO booted but was very unstable. Worse, something in the ARIO flash changed the ID of my son's YPG1 to assert itself as an i9000 so when I tried to flash a different YPG1 ROM over ARIO , maybe your 20140610 CM11, I got an error saying something like "this ROM is for the YPG1, not an i9000". I thought I was hosed at that point and figured trying to just go back to stock was my best bet. I used your thread here -- http://forum.xda-developers.com/showthread.php?t=1531850 -- to do that and it worked perfectly. That cleaned it up and paved the way for the next morning and subsequent rapid (and easy) success with your CM11 ROM.
One note, a very minor point. You have a step in your CM11 flash that says:
5. Flash the CM zip (Note: upon flashing it, your device will hang, IT'S NORMAL. Wait about 10-20 secs then force reboot your device)
Click to expand...
Click to collapse
FWIW, mine took a long time but it never actually hung... though it appeared at first that maybe it had. I was just patient and waited after flashing the CM11 zip, even did some other work, and eventually I came back to find the YPG1 had rebooted on its own and was just sitting peacefully at CWM6 recovery waiting for further guidance. So, fwiw, just wanted to let you know that mine didn't hang, and that perhaps it's just an apparent hang and that people should wait longer than 10-20 seconds before force rebooting. It's just my personal anecdote, I know, but just throwing it in there for your information.
I see your new build is up, I'll check it out.
Cheers.
knetknight said:
Thanks. The thing I beat my head against the most was one of the first ROMs I flashed, just in attempt to get his YPG1 working even on GB again, was SGS_PORT_ARIO. This ROM is for the YPG1 but is a port of an i9000 ROM. On my son's YPG1 ARIO booted but was very unstable. Worse, something in the ARIO flash changed the ID of my son's YPG1 to assert itself as an i9000 so when I tried to flash a different YPG1 ROM over ARIO , maybe your 20140610 CM11, I got an error saying something like "this ROM is for the YPG1, not an i9000". I thought I was hosed at that point and figured trying to just go back to stock was my best bet. I used your thread here -- http://forum.xda-developers.com/showthread.php?t=1531850 -- to do that and it worked perfectly. That cleaned it up and paved the way for the next morning and subsequent rapid (and easy) success with your CM11 ROM.
One note, a very minor point. You have a step in your CM11 flash that says:
FWIW, mine took a long time but it never actually hung... though it appeared at first that maybe it had. I was just patient and waited after flashing the CM11 zip, even did some other work, and eventually I came back to find the YPG1 had rebooted on its own and was just sitting peacefully at CWM6 recovery waiting for further guidance. So, fwiw, just wanted to let you know that mine didn't hang, and that perhaps it's just an apparent hang and that people should wait longer than 10-20 seconds before force rebooting. It's just my personal anecdote, I know, but just throwing it in there for your information.
I see your new build is up, I'll check it out.
Cheers.
Click to expand...
Click to collapse
Hmm that strange, I thought it was only an issue. I've left my device during 10 mins and it never rebooted, then I assumed that maybe something was left out so I'll try to get this worked out before we got our merge from the Cyanogenmod guys.
Long story short I have an M7 running 4.4.2 on AT&T that I haven't touched in about a year. I just booted it up everything is working properly except when I go to Software Update it tells me the software is up to date and that I can check again in 24 hours.
I've tried rebooting, no luck. Any other ideas? Thanks!
When you say you haven't touched it in a year, do you mean you don't use the phone at all? Or that you just haven't updated or modified it? If you just don't use the phone and don't mind starting from scratch you can run the 7.23.502.1 RUU. You can download it directly from HTC, http://www.htc.com/us/support/rom-downloads.html. I used this a couple of weeks ago and everything went smoothly and the phone runs great.
If you don't want to go that route and want the OTA, some have suggested changing the date on your phone ahead a few days and trying Software Update again. It may trigger the update. I have never tried that so can't say for sure if it'll work. And I haven't seen the OTA zips posted to update it manually.
I have a M9, for all intents new, was ATT, already unlocked, s-off'd TWRPd, and tried to flash the latest Lineage. It was a no go. Using himaul.
I did get Revolution HD running n it, but I wanted Lineage as it is what I was running n my M8.
I remember the process when they switched form CM to Lineage on my M8, is that you had to start with a base stable and then work your way through the nightlies if you had issues. But... I see as far back as the site goes, only nightlies.
So how does one fresh start a M9 that has never had Lineage before. (I even went to the directly listing whether the files are served, the oldest is still a nightly.)
I have tried removing the version asserts and it flashes, but then reboots right after the animation in a loop.
That is when I went to revolution just to get the phone back operational until I get a better solution.
I have been reading the helpful posts here for years, but first time I have ever not been able to just find a solution and therefor needed to ask.
Thanks for all the help over the years and hopefully in advance of this issue.
Appears solved
I updated the firmware to the latest OS, and it seems to have resolved the issue with the load, the latest nightly went in, and booted this time. I was on 1.32.509 went to 4.23.627. Not sure all is well yet, but lineage is in that is half the battle, will report back if issues.