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.
Related
Well here is the issue, I bought the HTC Thunderbolt awhile ago. I then rooted my phone but left the original ROM on it since the custom roms were not stable. I noticed verizon was pushing me some update and I just ignored them. I woke up today to see my phone rebooted with the screen on an exsclamation point. And then my Thunderbolt keeps rebooting itself now. I tried going into ROM Manager to download a Custom ROM but the phone just reboots before I can do it. I just installed Liquid Gingersense v1.6 rom with the MR2 OTA Radio which said it installed just fine after installing the Liquid Gingersense rom. I went through setting up the google account fine and after it booted to the main screen now my phone boots all over again, get stuck at htc screen for a bit then loads the phone fine then boots again. I am really not sure what the heck is going on. I am new to the MR2 OTA Radio since I cam from the Droid 1. So I hope it was not the install order I did it. I Have turned off the phone booted it with still same rebooting over and over issue. If anyone has idea's please let me know. Much appreciated. Thanks
I'm in the same boat. I have wiped the SD card and done a factory reset on the phone. It is no longer rooted, as I can't install and run apps requiring root permission. The update fails every time it tries to install, I also get the exclamation point android screen when the update tries to install. I'll take the update, I don't care. I just want a reliable phone again.
I'm seeing this issue come up a lot. Some of you folks seem pretty upset by it, and reasonably so. Search through the threads and you'll find you solution.
For those who are STILL running that antique and wildly obsolete ROM that the jcase rooting process leaves you with, I'd like to set a few facts before you. First of all, that ROM wasn't provided as a long-term daily driver. It's OLD and it's not very efficient with the battery. Second, simply because it's stock doesn't mean it's inherently stable. It's probably less stable than the custom ROMs out there. Third, the only ROMs really struggling with stability were the 2.01 RUU gingerbread builds. That build is obsolete, but not nearly as obsolete as the ROM that the rooting process leaves you with. The stability issues with the second OTA had nothing to do with the ROM, but rather, the radio that came with the RUU. In short, it's foolhardy to believe that custom ROMs are somehow inherently dangerous or unstable.
I'd like to suggest to whoever might be running the rooted ancient ROM the rooting process leaves you with to abandon it at your earliest convenience. Flash an MR2 radio, and if you like stock, use the stock rooted debloated ROM based on the 1.70 RUU. If you decide not to do this, and your phone auto-accepts the update, you'll probably lose everything on the phone trying to get it working again. Save yourself that hassle. Flashing ROMs isn't hard and people do it everyday.
I had android 4.4 Omnirom on my phone earlier today and yesterday. Today there was an update for the nightly. I decided to download it and updated through the recovery as a normal update would've. However, after waiting for almost an hour for the android is upgrading prompt to go away, I figured it was stuck in a boot loop. Well it turns out it more than likely was so don't say I'm impatient :d. So I forced it to shut down and it rebooted, but it didn't get past the Omni logo for almost an hour as well. So I decided to downgrade to the previous nightly. That didn't fix anything. After that, I tried to restore to cm 10.2 but it wouldn't let me for some reason. So I figured I was screwed. I downloaded Odin and attempted to restore to the stock rom. Well, Odin failed. So I was literally desperate and out of nowhere decided to try to downgrade the kernel. I attempted a downgrade to AJK 4.9 mic swap and it worked. So I installed MIUI after that (I'm too lazy to try adb) and it loaded up fine. I was so happy that at least something worked. After that I noticed the back and search buttons were not functioning. I decided to restore to cm 10.2 and it worked. Everything SEEMS fine but I'm not too sure if everything is. Can anyone tell me if my process is correct? Or if I messed up everything
Thanks!
I had to wipe the caches after i flashed the nightly to get it to boot.
The CM nightlies didnt work for me either. Something about the build.prop in Omni calling my phone both the ATT and ST version of the phone. I did what you did. Flashed AJ 4.7 i had, rebooted the Recovery, and Nandroid restored.
I liked Omni and ill be back but that battery life right now Ugh. Good luck Entropy and Co!
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
9859834534
prsterero said:
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
Click to expand...
Click to collapse
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Speedsterspeed277 said:
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Click to expand...
Click to collapse
It could be. There have been people that get weird issues with twrp so you may want to test out a different recovery to see if the issue persists.
prshosting.org
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
NOTE: Most, if not all of these ROMs are designed for ATT.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
I had the same problem and switched to Philz Touch instead of TWRP, I like TWRP a lot more and most people say its more stable, but that's what fixed it for me.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Umm... Don't reboot
Sent from my SCH-I545 using xda app-developers app
I have read, on CM's site somewhere I believe, they recommend using CWM for a recovery. I use 6.0.4.4 and have no issues with getting stuck at the boot logo. There was an issue with that but CM addressed it in one of the nightlies about two weeks ago.
I had that issue when I had a newer twrp recovery I have the .2 whatever one and I havnt had it since.
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.