Related
Hi guys,
I am new to the XDA forums so forgive me if this is really stupid or if someone has posted the same problems. I searched for an answer but couldn't seem to find someone with my problem. Forgive me if this is long. I just want to make sure you guys know all the details so we can figure out what went wrong.
I recently flashed the Evil Fascination 3.6 Rom from a modified stock version of ED04 (debloated/debinged). I believe that my version of CWM recovery was 2.5.1 or something like that (w/ voodoo lagfix). I am pretty new to the Android world but I do believe I did everything correctly. I wiped Cache and Dalvik Cache and Data multiple times and made nandroid backups etc.
I flashed the Rom with no problems and everything worked just fine. I was trying out Regina 3D launcher at the time (I regularly use Launcher Pro), and for some reason it seemed a little slow to load up (I figured it had to do with it being the first time with the new rom). I kept having loadup problems with the launcher so I uninstalled it and went back to Launcher Pro. Launcher Pro even seemed like it was acting weird but I didn't take much notice to it.
Now yesterday I downloaded the OTB 1.6 Touchwiz kernel. Everything I've read said it was compatable with Evil Fascination. I tried to flash it from CWM recovery and it didn't work. My phone stayed stuck on the Evil Fascination boot up screen and finally I just popped the battery out. I went back into CWM and just wiped everything and reflashed Evil Fascination. It seemed to work fine with Launcher Pro (again a little glitchy at times, but I took no notice really).
I again tried to flash the OTB 1.6 kernel. This time instead of doing it from the recovery I downloaded an app called SGS kernel flasher. I did what it said and it flashed the kernel for me with no boot up problems like CWM did. I rebooted and then booted into CWM to check it and it was changed from version 2.5.1 (voodoo) to 3.2.0.0.otb. I figured this meant that the kernel flash was sucessful. I went to reboot my phone and when the home screen came on it was a froyo style launcher with only 2 or three icons on the page. I pressed the app drawer and none of my apps showed up that were on my sd card. finally i pressed the home button and it asked for which launcher to choose : LauncherPro or the default and I chose LauncherPro. My regular setup appeared and my apps were in the app drawer. I found it weird that my apps showed in LauncherPro but not in the default launcher.
Now with doing phone reboots my phone always goes to the default launcher with no apps from my sd card and I have to wait to press the home button for LauncherPro to appear. I set it as my default launcher but it never loads when my phone is rebooted.
I was just recently (within the last hour) doing regular things on my phone (texting, internet , email etc) ad all of a sudden I got the shut down boot animation from my rom and my phone turned off. I went to turn it back on and my phone stayed stuck on the boot screen again. Now you can figure what I did again. I went through and did everything over and reloaded the rom and kernel. I am still having the same problems with the launcher as I did before and I have no idea whats going on. I just want to avoid going through this again. Anyone have any idea what the heck is going on???
If I were to guess I would say your problems comes from trying to flash the otb kernel with a 2.x.x.x recovery..i don't believe that recovery supports edify scripting.....i would odin a 3.x.x.x recovery and re flash the otb kernel...and I don't know much about that app you are referring to, but I wouldn't use a market app to try to install a kernel unless specifically directed to in the author's o.p.
I'm not a dev..just a flash-a-holic! but I think that should help your problem
Sent from my SCH-I500 using XDA App
I'm also no expert but after running into constant force closes and random problems with launcherpro I decided to go with go launcher and its been a great switch for me.
Sent from my SCH-I500 using XDA Premium App
Hey guys, still no luck. I don't know what it is. I wish I knew more about hacking and doing all this kind of stuff
Try flashing a PBJ kernel!
can you get into CWM with the three finger salute?
[hold down the two volume buttons and the power until your phone reboots and you see samsung then let go]
See if you can mount as usb to get the kernel on there, if that doesnt work go to staples get a microsd card reader [under $15] and toss the pbj on your card then flash that.
When i was on EF and Comm Rom my phone didnt like the OTB kernels
Good Luck!
My recovery menu works fine and I can boot into it from the ROM without problem. My problem is that when I reboot the phone the ROM's default launcher is setup (and it is missing all of my apps) even though I set Launcher Pro as my default. I have to reset all my defaults in Launcher Pro every time my phone is turned off or rebooted. I would be on PB&J but I like to overclock my phone and PB&J doesn't support voltage control and I don't want to pay for and overclocking app.
efan450 said:
If I were to guess I would say your problems comes from trying to flash the otb kernel with a 2.x.x.x recovery..i don't believe that recovery supports edify scripting.....i would odin a 3.x.x.x recovery and re flash the otb kernel...and I don't know much about that app you are referring to, but I wouldn't use a market app to try to install a kernel unless specifically directed to in the author's o.p.
I'm not a dev..just a flash-a-holic! but I think that should help your problem
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
From what I've read many people have disagreements on whether 2.5 supports Edify or not....because a lot of people have success with it while others don't so I really don't know. Its never given me problems in the past. I actually had more problems with 3.X recoveries (It wouldn't allow me to make nandroid backups and other things that were essential) so I flashed 2.5 and it worked perfect (again I've read about people having the same problems with 3.0 versions of CWM).
Okay what I've found is that this has nothing to do with Launcher Pro. I downloaded He Launcher and when I reboot my phone everytime it asks me to pick a default launcher. And when I'm using He Launcher, none of the apps on my SD card show up in the app drawer (they don't show up in the default ROM launcher either, they only show up in launcher pro)
Efan450 I tried what you said and it worked! I odined a 3.X recovery and wiped everything oof my phone then flashed the ROM and kernel and everything is working perfectly now. Thank you very much!!!
Just wondering if anyone can help me out. A few days ago I installed the new market apk that was floating around. It installs fine, and once it loads the main title screen it FC's.
I've tried all install methods, uninstalling the old, overwriting the the vending.apk.. as well as combinations of wipe cache/data for market, and market updater. I've also tried wiping cache/dav cache as well.
Now tonight I just tried the updated gapps package.. flashed from CWM, and same problem.
I'm telus fascinate, cm7 galaxysmtd70, glitch v11.
Any help?
Thanks.
FYI, I have CM7 Build 3 from nightlies thread.
I installed the new market ('vending.apk'), it is not fc'ing for me. But it does seem to take longer to load than the old version of the Android Market. My LauncherPro, however, does force close from time to time.
Try running 'permission fix' from ROM manager that came with CM7.
I ran this fix and the first time my phone booted, it was on 'safe mode.' Pulled battery and everything was fine. I have yet to find any fc'ing issues after doing so.
Try your luck!
Go into settings then force stop and delete data for Market. Reboot, then try opening the Market.
Thanks for the suggestions, but neither worked. I got to figure this out. If I do, I will keep this post updated.
I cannot figure this out for the life of me. I've tried everything. Including full wipe and reinstall. Still getting the FC's.
MrManiacNF said:
Now tonight I just tried the updated gapps package.. flashed from CWM, and same problem.
I'm telus fascinate, cm7 galaxysmtd70, glitch v11.
Any help?
Thanks.
Click to expand...
Click to collapse
which recovery did you try to flash the gapps. zip with? Did you use the power button menu reboot recovery...or did you three finger boot to recovery?...im just saying I've done it by accident/force of habit!...just covering the bases since this is the first I've heard of gaps not installing correctly or fc'ing left and right on anyone.
Sent from my SCH-I500 using XDA App
Hi all,
I installed CM7 on my TP a ways back but never really used it and stuck with WebOS. I decided to upgrade to CM9 Alpha2 yesterday and did without any issues. I then got curious about CherryKang and decided what the heck. I was able to install CherryKang but now I am having a few issues:
1. When booting CM is still listed in MoBoot and CherryKang is not. If I select CM, then I get the CM boot screen for a sec and then CherryKang boot screen comes up. Not that big of a deal, just hoping to get it setup right.
2. The Gallery force closes every single time.
3. Occasionally unresponsive when trying to wake it up. I always put it to sleep when I am done by pressing the power button, but I have to reset it to wake it up about 30-40% of the time.
Those are my only issues so far. Other than that I'm diggin' ICS.
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
svenerator said:
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
Click to expand...
Click to collapse
I tried wiping the cache, dalvik cache from CWM but no luck. Then re-downloaded and reflashed but still no luck. Ended up going back to CM9 Alpha2 and so far has been stable. I've been able to wake it up without issue far....
You may want to try and restall CM9 with the Acmeinstaller2 method. I read that although you can use CWM to go from CM7 to CM9, you can get leftover files/directories that could may or may not cause issues in CM9.
after using Acmeinstaller2 to get to CM9, you can safely use CWM to flash other CM9 roms. Also, before you flash, use classicnerd's moboot uimage and tga cleaner to wipe out previous boot images left by other roms.
Many people just wipe the cache and dalvik caches before flashing, and don't do the factory reset. I always do, because the roms seem to have less issues if I do the factory reset.
I've had a couple of instances in more than one rom where the lock screen doesn't respond (touch screen doesn't work) and I have to reboot, so I just disable the lock screen all together.
Gallery is currently working on my install of cherrykang, but I prefer Quickpic from the market, and usually install it right away.
I believe the boot option issue is because it uses the standard CM kernel, so that's what it boots up. If you flash the Bricked kernel, and entry will appear for that, even though you're using the CherryKang.
I too was getting the problem where it became unresponsive. What seemed to mostly work was setting the minimum clock up to 384mhz. You can use SetCPU from the market, or CPU Master (free in the market -- that's what i used). I had some problems again last night, but overall it seemed to help. His latest version did set the min clock speed to 200-something.
Thanks for all the tips guys. Still running strong with no lockups after going back to the original Alpha2.
I actually tried setting the min CPU higher prior to going back to [email protected] but that didn't work either. I still have my kids TP to install CM9 on so I might try CherryKang on that.
I was listening to music on my Evo 3D over bluetooth today, when I put it in my pocket and paused the music. After going back to my phone, I noticed it had reboot itself, and now it's stuck on a boot loop. Does this sound familiar to anyone? I can't think of any reason why it would boot loop like this. Wiping cache+dalvik doesn't fix the boot loop. After clearing cache+dalvik and booting the phone, it does go to the screen saying that Android is updating apps, but as soon as it finishes it goes right back to the boot loop. I'd appreciate any assistance in figuring this out. Thanks!
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Kite-G said:
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Click to expand...
Click to collapse
Yeah, I ultimately had to restore from a backup. This is an almost stock ICS rom, deodex plus a few other apps baked into the ROM, and the stock kernel.
Now this doesn't happen every single time I turn the screen off with bluetooth turned on, or every time I turn off bluetooth. This is just a random boot loop that hits out of nowhere. Since I can't figure out what causes it, I was hoping someone who had encountered it would know.
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Kite-G said:
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Click to expand...
Click to collapse
Just FYI, the Wild For The Night OP specifically says do NOT use superwipes. Superwipe scripts and AOSP Roms don't always play together nicely. That's and CM Rom. Factory reset wipe in recovery is fine.
I am aware of that. But thanks for pointing it out. Althought I haven't had any problems with AOSP roms & superwipes when I wipe manually after the superwipe, only when I don't. But then again results may vary. At least in my case, I'm pretty satisfied with the results.
Sent from my HTC EVO V 4G using xda app-developers app
Welcome to wilson3q's CM12 Unoffical Build!
As requested by some users, I started to build cm12 for I605. I don't own a I605, please help to test. If you like my work, you can donate here.
Disclaimer: I take no responsibility for bad things that happen as a result of flashing this.
My kernel source is standard cm12 kernel without any modifications.
SaberMod tool chain source is HERE.
All the rests are pretty standard cm12 stuffs, except a few patches I applied on top of them.
[Download]
ROM (please don't mirror):
build - 20150513
build - 20150602
Gapp:
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Recommended launcher:
Nova Launcher (really like its JB zoom app animation, hate L slide up animation)
Recommended theme:
Deep Darkness
If you need enable soft buttons, flash this: View attachment softkeys.zip or soft+hardkeys.zip
[Flashing Guide]
1. Reboot to CWM/TWRP recovery
2. Flash ROM zip file
3. Flash Gapps
4. Reboot
* Wipe data first if you come from another rom *
* Newer boot loader, modem and recovery is highly recommended (don't use twrp 2.8.4, use 2.8.1 instead) *
* No other kernel will be supported, use the stock one, for your best experiences too *
[Patches]
My additional patches over cm12 includes:
Enhancements and bug fixes cherry-picked from other ROMs, including Slim LP, Nameless
SaberMod for ROM and kernel
O3, JustArchi optimization
Pthread enabled & strict aliasing
Latest sqlite db library
Added Boeffla sound engine 1.67
Added CPU governor zzmoove, smartassv2, savagedzen
Added io scheduler row, bfq, zen, vr
Disabled some useless Samsung processes
Fixed GPS
Fixed low in call volume
Video playback forward/backward fix
Removed all kernel debuging stuffs
Fixed keyboard not showing up during setup wizard
Fixed a crash of music app
Changed DPI to 280
Fixed Camera issue
Fixed Day Dream
Fixed Netflix streaming (one more reboot needed after installation of Netflix)
Enabled Multi-user
LMK minfree tweaks
Misc tweaks
more...
For better experience, change Nova animation/scroll speed to Fast...
[Known Bugs]
I am not sure what issues you will get, but one thing is for sure: YOUR PHONE WILL FLY!
chrome glitch: type chrome://flags as URL and disable GPU thank @bigmarv31)
Thank cm team for the amazing ROM.
Thank sabermod for the amazing toolchain.
Special thanks to: @DerTeufel1980, @sbrissen, @rogersb11, @TheBr0ken, @DreamFX, @frankie...
[Screenshots]
Always nice to see a new thread for i605. This doesn't happen often. Thank you!
Thanks again for building this for us we all appreciate it!
will be testing this out and see how it spars. thanks for this! I was going to try and "port" it over from the t0lte with replacing some libs and such, lol.
Thank you! I'm downloading right now. Looking like a slow day at work, so why not?
Downloaded files. Backed everything up. Rebooted to recovery. Wiped / Factory Reset using TWRP. Installed both zips sequentially. Apprehensive when I rebooted. Took a couple of minutes of sweating watching the CM Logo swirl around, and then bam! I'm up and running Lollipop. I'll update soon...
UPDATE
thefinancemaster said:
Downloaded files. Backed everything up. Rebooted to recovery. Wiped / Factory Reset using TWRP. Installed both zips sequentially. Apprehensive when I rebooted. Took a couple of minutes of sweating watching the CM Logo swirl around, and then bam! I'm up and running Lollipop. I'll update soon...
Click to expand...
Click to collapse
So, I've got it up and running. It's fast and smooth, but there's a couple of glaring issues stopping me from testing any farther. The first screen that comes up after you initially select your language, is a new (to me) "Activating Cellular Service" screen. It has a message on the screen saying this "can take up to 5 minutes". I let it go for longer than that, but I got an error that it was unable to activate and I was able to try again, or skip it. I'll skip it for now just to see how the rest of the ROM works. Next screen is Wifi login, works fine., but you still have to hit "skip" even after you sign in to wifi.
Then it checks connections, for updates, etc and I keep getting the error that google play services has stopped. I haven't even logged into it yet...
Next screen is Tap N Go. Option to transfer all of your stuff off your old phone using NFC. Great idea, but I'm not testing because my new phone IS my old phone.
Then, it's google login time. Worked fine, standard stuff we're used to with options to download/backup your apps using google. It takes a minute here, and I kept getting popups about all of the google apps stopping, each individually. Annoying a bit... I hit the "RESTORE" option, this is my second try, and the first time I didn't have Root, so I couldn't download Titanium to restore everything. I also skipped the google restore last time, so I tried it this time. This is a new screen for me, but it takes me to a "Restoring" screen for a bit. It's not as annoying as on previous Android versions, having to individually approve each app that was updating/downloading. I keep getting the popups about one Google app or another stopping.
I get past the restore page, and the phone locks up. Reboot... After reboot, I have to go into the play store to download Titanium. It seems quite a few apps were restored by Google, but not all. I looked at the "My Apps" section of the play store, and there's a ton of apps cued up to download. It's what I was trying to avoid... So I hit "Stop" at the top, and it stops them all.
**I mentioned earlier that this is my 2nd try, the first try was about the same, but I didn't have root access. I downloaded SuperSU, but it wouldn't update the binaries, so it was useless. I tried SuperUser, it didn't work either. So, I rebooted to recovery, wiped, flashed the ROM, GApps, and the SuperSU zip I had saved on my SD card from my previous Omni Rom. Then I rebooted and now you can read what happened.
At this point, I'm having problems downloading Titanium Backup, SuperSU, or anything I really want. The Play Store is hanging and force closing. I can't even open the SuperSU I flashed from TWRP. There must be compatibility issues. I read somewhere that Lollipop has issues with root somehow, but I'm not sure. On my first try, I was able to download Titanium Backup no problem, but it wouldn't work because I didn't have root access. SuperSU and SuperUser didn't help after downloading. CM has always been pre-rooted on all of the other devices I've installed it on.
For now, I'm just going to restore my backup of Omni Rom and be content with 4.4.4 for now.
I'll try again if anyone can help with actually being on the VZW Network and Root. I didn't get a chance to play with the other stuff in Lollipop yet, but I would love to.
thefinancemaster said:
So, I've got it up and running. It's fast and smooth, but there's a couple of glaring issues stopping me from testing any farther. The first screen that comes up after you initially select your language, is a new (to me) "Activating Cellular Service" screen. It has a message on the screen saying this "can take up to 5 minutes". I let it go for longer than that, but I got an error that it was unable to activate and I was able to try again, or skip it. I'll skip it for now just to see how the rest of the ROM works. Next screen is Wifi login, works fine., but you still have to hit "skip" even after you sign in to wifi.
Then it checks connections, for updates, etc and I keep getting the error that google play services has stopped. I haven't even logged into it yet...
Next screen is Tap N Go. Option to transfer all of your stuff off your old phone using NFC. Great idea, but I'm not testing because my new phone IS my old phone.
Then, it's google login time. Worked fine, standard stuff we're used to with options to download/backup your apps using google. It takes a minute here, and I kept getting popups about all of the google apps stopping, each individually. Annoying a bit... I hit the "RESTORE" option, this is my second try, and the first time I didn't have Root, so I couldn't download Titanium to restore everything. I also skipped the google restore last time, so I tried it this time. This is a new screen for me, but it takes me to a "Restoring" screen for a bit. It's not as annoying as on previous Android versions, having to individually approve each app that was updating/downloading. I keep getting the popups about one Google app or another stopping.
I get past the restore page, and the phone locks up. Reboot... After reboot, I have to go into the play store to download Titanium. It seems quite a few apps were restored by Google, but not all. I looked at the "My Apps" section of the play store, and there's a ton of apps cued up to download. It's what I was trying to avoid... So I hit "Stop" at the top, and it stops them all.
**I mentioned earlier that this is my 2nd try, the first try was about the same, but I didn't have root access. I downloaded SuperSU, but it wouldn't update the binaries, so it was useless. I tried SuperUser, it didn't work either. So, I rebooted to recovery, wiped, flashed the ROM, GApps, and the SuperSU zip I had saved on my SD card from my previous Omni Rom. Then I rebooted and now you can read what happened.
At this point, I'm having problems downloading Titanium Backup, SuperSU, or anything I really want. The Play Store is hanging and force closing. I can't even open the SuperSU I flashed from TWRP. There must be compatibility issues. I read somewhere that Lollipop has issues with root somehow, but I'm not sure. On my first try, I was able to download Titanium Backup no problem, but it wouldn't work because I didn't have root access. SuperSU and SuperUser didn't help after downloading. CM has always been pre-rooted on all of the other devices I've installed it on.
For now, I'm just going to restore my backup of Omni Rom and be content with 4.4.4 for now.
I'll try again if anyone can help with actually being on the VZW Network and Root. I didn't get a chance to play with the other stuff in Lollipop yet, but I would love to.
Click to expand...
Click to collapse
Did you flash the andriod 5 gapps? Do a full wipe?
You also need latest twrp recovery or philz touch recovery...
baseband unknown no data
bigmarv31 said:
baseband unknown no data
Click to expand...
Click to collapse
Will fix this today.
Keep a close look.
wilson3q said:
Will fix this today.
Keep a close look.
Click to expand...
Click to collapse
Yes Sir Thanks
New build online...
Giving this a try!! Downloading now
Update- Downloaded and installed without any problems. I did have to skip the network verification set-up as it never went anywhere and wifi set-up worked as with setting up my g-mail account,.
Everything seems good except for no service, baseband version still unknown and no service or apn's for data.
going back to Liquid till this gets updated.
LvnInOC said:
Giving this a try!! Downloading now
Update- Downloaded and installed without any problems. I did have to skip the network verification set-up as it never went anywhere and wifi set-up worked as with setting up my g-mail account,.
Everything seems good except for no service, baseband version still unknown and no service or apn's for data.
going back to Liquid till this gets updated.
Click to expand...
Click to collapse
Can you get a logcat?
I guess my proprietary blobs are not correct...
wilson3q said:
Can you get a logcat?
I guess my proprietary blobs are not correct...
Click to expand...
Click to collapse
I already went back to Liquid but I dont mind doing another try at it especially if it would benefit. let me get ir flashed and try to get you the Logcat
. give me a few
---------- Post added at 05:38 AM ---------- Previous post was at 05:10 AM ----------
ok so I got this flashed again strange this time after booting it said no sim card inserted and to insert my sim, it was not out and i skipped and moved to wifi , setup worked all the way and I got a log cat, hope I did it correct as this is new to me. I have to re-flash to Liquid for now so that I have a working phone as I go to work in an hour,
Again let me know if you need any more details
Same on this build baseband unknown so no data
wilson3q said:
Did you flash the andriod 5 gapps? Do a full wipe?
You also need latest twrp recovery or philz touch recovery...
Click to expand...
Click to collapse
Yes, I flashed the gapps from your post. gapps-lp-20141109 is what the file name was. I use TWRP, not sure if it's the latest but it works fine. I always do the "factory reset" wipe option in twrp, because I believe that's a full wipe with one swipe... Now, just to test it out and see if I was doing something wrong, I tried the Liquid Smooth build (latest nightly) from 1/7, and it loaded and booted just fine. Had to flash the ROM, Gapps, GPS Fix, and Super SU (so I can restore my apps in Titanium). It connected to data, and ran me through the setup in a flash. It's working well enough to be a daily driver. Do you have any other suggestions? I'm willing to help if you want me to try something else.
Going to give this a try. Thank you for giving this phone options. It is greatly appreciated.
"Chance Favors the Prepared"
glockman4519 said:
Going to give this a try. Thank you for giving this phone options. It is greatly appreciated.
"Chance Favors the Prepared"
Click to expand...
Click to collapse
You're like me you change roms by the hour.
DreamFX said:
You're like me you change roms by the hour.
Click to expand...
Click to collapse
I love to flash and then go through a process of testing. I actually got 2 gt-n5110s so I could test a couple builds at same time, kind of a back to back comparison.
I would love to pick up another i650 that still has unlocked bootloader for testing that way on this device as well.
Well back to this rom, I couldn't get past the getting data screen and had to abort. I did a clean flash and wiped everything with both philz and TWRP 2.8.3.0. I tried both stock and shift kernels.
Lets face it, I'm a flashaholic. lol.....
"Chances Favors the Prepared"