I didn't know PAC ROM was available for sprint g2 until today, it may not have been but for anyone who wanted to give it a try here's the link
http://pacman.basketbuild.com/index.php?dir=main/ls980/nightly/
Sent from my LG-LS980 using xda app-developers app
I may give this a try sometime. I loved PAC when I had a Note 2.
Sent from my LG-LS980 using Tapatalk
I was looking forward to moving on up to KitKat with PAC ROM however I simply got bootloops after flashing both nightlies and the dr87 kernel. I'm on ZVA and I am to understand it would brick your phone to the point of returning to full stock without flashing the ZV8 radios or the dr87/Furnace kernel, but to get stuck in a bootloop lost me.
I was also surprised at how iffy it can be about getting into recovery.
However, I do look forward to checking the rom out when I can get things straight.
Edit: One more shot has it booting into setup. Used Furnace kernel this time as opposed to dr87's but it might've been something in the way I was flashing the ROM anyway.
seastones said:
I was looking forward to moving on up to KitKat with PAC ROM however I simply got bootloops after flashing both nightlies and the dr87 kernel. I'm on ZVA and I am to understand it would brick your phone to the point of returning to full stock without flashing the ZV8 radios or the dr87/Furnace kernel, but to get stuck in a bootloop lost me.
I was also surprised at how iffy it can be about getting into recovery.
However, I do look forward to checking the rom out when I can get things straight.
Edit: One more shot has it booting into setup. Used Furnace kernel this time as opposed to dr87's but it might've been something in the way I was flashing the ROM anyway.
Click to expand...
Click to collapse
d87's kernel won't work on PAC currently. Did you get phone FCs, where it constantly comes up, preventing usage of the device?
Koopa777 said:
d87's kernel won't work on PAC currently. Did you get phone FCs, where it constantly comes up, preventing usage of the device?
Click to expand...
Click to collapse
I wish I had known that kernel didn't work sooner, as it doesn't really warn against that in the OP...
I didn't flash the 03/04 nightly. My first thought was that it was the problem.
After sorting all this however, I was annoyed to find that the touch screen wasn't responding in the first application I installed, so I just went back to what I had. I'm sure it'll get worked out eventually (or I'll read about a fix soon enough, either way).
seastones said:
I wish I had known that kernel didn't work sooner, as it doesn't really warn against that in the OP...
I didn't flash the 03/04 nightly. My first thought was that it was the problem.
After sorting all this however, I was annoyed to find that the touch screen wasn't responding in the first application I installed, so I just went back to what I had. I'm sure it'll get worked out eventually (or I'll read about a fix soon enough, either way).
Click to expand...
Click to collapse
Really? I had no issues on 3/3 nightly, but 3/4 was all kinds of borked. It's SUPER early though, hell I'm amazed that it's as stable as it is, seeing as how it's the first few nightlies.
Related
I am kinda new to all this. I just inherited the thunderbolt from my brother bc my other phone is dead. I am rooted and s-off running santod's Official Thunderbolt ICS deoxed debloated. My question was if I am able to switch to one of the older ROMS like NuSense ROM or UnSense ROM or anyone for that matter that I feel like. I know the process of flashing since I have gotten this far, but I don't want to flash these and then be in some sort of loop with problems.. Thanks in advance:good: Also are radios universal or.. I keep seeing people say just try a different one?
You can flash any ROM you like.
As for radios, look in the post about the ROM, they usually specify what radio is best for that ROM. The newest radio is defiantly needed for the new crop of ICS ROMs based on the official OTA as the older radios cause issues.
Only thing I can add to the first response... Always make a backup first. So when you somehow get into a bad flash/bootloop situation, you have an easy way back to a working device. Also verify your download by checking it's md5 code before you flash. Almost (if not all) files you download will have it listed with the download link on the forum op you're getting it from.
LeftyGR said:
Only thing I can add to the first response... Always make a backup first. So when you somehow get into a bad flash/bootloop situation, you have an easy way back to a working device. Also verify your download by checking it's md5 code before you flash. Almost (if not all) files you download will have it listed with the download link on the forum op you're getting it from.
Click to expand...
Click to collapse
Thanks guys! I'm currently using thundershed v1.6 CM7 bc I am a BIG fan of CM. I have run into some issues with data and wifi though.. All of the sudden they stop working and I have to reboot and then they work again.. Maybe its the phone not sure..
lacoursiere18 said:
Thanks guys! I'm currently using thundershed v1.6 CM7 bc I am a BIG fan of CM. I have run into some issues with data and wifi though.. All of the sudden they stop working and I have to reboot and then they work again.. Maybe its the phone not sure..
Click to expand...
Click to collapse
It's not your phone but the Rom itself. That's a known issue with cm roms on this phone.
Sent from my ADR6400L using Tapatalk 2
I have the Galaxy Note 1 with Jellybean 4.1.2 on it. I have the phone rooted and all backed up on all counts. I'm trying to flash the aokp_quincyatt_unofficial_2013-08-28.zip file and it's giving me an error. Please don't ask what that error is because I can't make heads or tales of all the code. I can tell you its a status 7 error and it's telling me there is a problem in the zip file. I downloaded it 3 times and still get the same error. Can someone tell me what's going on. Did I not do something or need additional files?
Update your recovery to twrp........should fix your problem
2$HAYNE
shayneflashindaily said:
Update your recovery to twrp........should fix your problem
2$HAYNE
Click to expand...
Click to collapse
Can you tell me how to do that?...lol...sorry I been out of the game for a while here.
cougar214 said:
Can you tell me how to do that?...lol...sorry I been out of the game for a while here.
Click to expand...
Click to collapse
download file and flash like any other ROM and it will replace CWM.
can find file in ORIGINAL ANDROID DEVELOPMENT or SUPER EVERYTHING THREAD
Also with goo manager ...install open recovery
2$HAYNE
I installed CWM following the guide below and I just flashed the Blown Fuze AOKP rom with no issues.
http://androidlegend.com/touch-clockworkmod-recovery-for-att-samsung-galaxy-note-sgh-i717/
Twrp is better
2$HAYNE
shayneflashindaily said:
Twrp is better
2$HAYNE
Click to expand...
Click to collapse
I got it up and running. Thanks guys. But I will be flashing something else. This thing is running worse than the stock Rom. My messaging wont even load. It just keeps crashing out. I know there are mixed feelings about CM 10 based Roms and with this i'm gonna have to go with those that want to stay away from them.
cougar214 said:
I got it up and running. Thanks guys. But I will be flashing something else. This thing is running worse than the stock Rom. My messaging wont even load. It just keeps crashing out. I know there are mixed feelings about CM 10 based Roms and with this i'm gonna have to go with those that want to stay away from them.
Click to expand...
Click to collapse
aokp isnt a cm based rom its an aosp based rom
You may want to try to download the rom again and reflash. Make sure you see doing a full wipe. You can also get help within the AOKP thread.
Sent from my SGH-I717 using Tapatalk 4
Ok. So just to give it a fair chance I went ahead and did a another full data wipe. It is running better. I'm not sure if this has been an issue or even talked about in their thread, and being over 100 pages im not gonna look through it all...lol, But I used TB to restore my apps. no data. Just apps. I am aware that TB can screw up the build.prop on some Roms. So that is the main reason for the second data wipe. To see if that is in fact the cause of it running like crap. I also used sms backup to restore my texts.
And right now my phone is hanging like a ******.....Soooo....It looks like sms backup may be the culprit here. And you guys have to forgive me with all this because I have been out of the game for about a year now. When I first got this Note there were maybe 3 Roms out for it....lol. I am going to give this Rom it's fair run and just keep messing with things because I know all phones are not created equal. And from what I can see all you developers have done amazing work with these Roms.
That's why I'm back. I need to make my old phone new again... I was debating on whether or not to flash the Uber kernel. I know the basics of what a kernel is. But what I don't know is if I flash the kernel do you have to flash the Rom again or does the kernel just change and leave the OS intact?
You can flash the kernel no prob...........can someone tell me why people back up texts ...I don't get the point
2$HAYNE
cougar214 said:
Ok. So just to give it a fair chance I went ahead and did a another full data wipe. It is running better. I'm not sure if this has been an issue or even talked about in their thread, and being over 100 pages im not gonna look through it all...lol, But I used TB to restore my apps. no data. Just apps. I am aware that TB can screw up the build.prop on some Roms. So that is the main reason for the second data wipe. To see if that is in fact the cause of it running like crap. I also used sms backup to restore my texts.
And right now my phone is hanging like a ******.....Soooo....It looks like sms backup may be the culprit here. And you guys have to forgive me with all this because I have been out of the game for about a year now. When I first got this Note there were maybe 3 Roms out for it....lol. I am going to give this Rom it's fair run and just keep messing with things because I know all phones are not created equal. And from what I can see all you developers have done amazing work with these Roms.
That's why I'm back. I need to make my old phone new again... I was debating on whether or not to flash the Uber kernel. I know the basics of what a kernel is. But what I don't know is if I flash the kernel do you have to flash the Rom again or does the kernel just change and leave the OS intact?
Click to expand...
Click to collapse
You would not have to flash the rom again .. just the kernel. But the new Uber is for 4.3 and not 4.2 .. so it is not compatible.
The included kernel is built by Fuze to go with this rom.
Just to be sure you get the best experience with AOKP, your wipe should include Dalvik, Cache, Data, and system.
I restore with TiBu all my user apps and selected user app data.
I pretty much run the rom as is out of the box and it is doing a great job on my phone.
Shayne Some people restore texts to not lose certain conversations. That's why I do it. Bubba I am aware of the 4.3 kernel being incompatible. The older versions are however compatible. That's why I was considering it. The problem is, as everyone knows, all phones are the same. So one kernel may run super on your phone but not mine. I just want to get the best possible performance out of this Rom because I do like it. So far it is performing better after the second full wipe.
And by the way. My data connection is WAY better on this Rom than stock.
cougar214 said:
Shayne Some people restore texts to not lose certain conversations. That's why I do it. Bubba I am aware of the 4.3 kernel being incompatible. The older versions are however compatible. That's why I was considering it. The problem is, as everyone knows, all phones are the same. So one kernel may run super on your phone but not mine. I just want to get the best possible performance out of this Rom because I do like it. So far it is performing better after the second full wipe.
And by the way. My data connection is WAY better on this Rom than stock.
Click to expand...
Click to collapse
Glad it's working for ya.
I do have another question about that, or any, kernel. After flashing a kernel is it permanent? As in there is no flashing back to the previous kernel?
cougar214 said:
I do have another question about that, or any, kernel. After flashing a kernel is it permanent? As in there is no flashing back to the previous kernel?
Click to expand...
Click to collapse
Fuze has his posted in the op so you can revert back. Here is a link: Fuze Kernel The only other way would be to make your Nandroid prior to flashing the kernel .. then revert back.
I'm not sure that the Fuze kernel at that link would be exactly the same as the latest release .. he is constantly tweaking it.
shayneflashindaily said:
You can flash the kernel no prob...........can someone tell me why people back up texts ...I don't get the point
2$HAYNE
Click to expand...
Click to collapse
Are you married? If you are, I congradulate you on the most carefree marriage alive.
I on the other hand come across some of the he said she said moments where information is ammunition and need to prove innocence or guilt on occasion. I don't take a knife to a gun fight.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Lmao captemo. But it is true. Another fine reason to back up your texts. I don't know about you but arguing with a woman and not having the proof to back it up is totally useless.....lol
cougar214 said:
Lmao captemo. But it is true. Another fine reason to back up your texts. I don't know about you but arguing with a woman and not having the proof to back it up is totally useless.....lol
Click to expand...
Click to collapse
Arguing with a woman, even with proof is pointless!
Sent from my Nexus 7 using xda app-developers app
Hey Guys,
After seeing what we were able to do with the AOSP Rom and SafeStrap, couldn't help but wonder if the same be done with Cyanogen? I know Cyanogen normally boots with AOSP style kernels, but if a Google Edition ROM can be booted... shouldn't Cyan be able to? Couldn't we use the GE/CM11 Edition in the Development Section, then remove the cyan kernel (so ours goes untouched, not tripping KNOX)?
I know that it would be feature barren due to kernel differences, but its still cyan
I'm wondering if that kind of magic could be used to port this ROM over?
http://forum.xda-developers.com/showthread.php?t=2643031
Ground Broken
I have begun working using a CM11 Base (4.4.4) and building around our kernel. It looks to be promising so far. But only time will tell
AngryManMLS said:
I'm wondering if that kind of magic could be used to port this ROM over?
http://forum.xda-developers.com/showthread.php?t=2643031
Click to expand...
Click to collapse
They already have AOSP SafeStrap... just read the instructions the guy that figured it out left on the ATT thread and use them to port that one
npjohnson said:
They already have AOSP SafeStrap... just read the instructions the guy that figured it out left on the ATT thread and use them to port that one
Click to expand...
Click to collapse
Alright so I just tried to do that. I got as far as the boot ani then it simply loops repeatedly and vibration keeps going off. I let it sit for 10 minutes I don't know if I am missing something or forgot something on the build I worked on. I can upload it to my AFH account if you want me to so you can see if I am missing something.
Also best of luck on the CM11 stuff. :good:
AngryManMLS said:
I'm wondering if that kind of magic could be used to port this ROM over?
http://forum.xda-developers.com/showthread.php?t=2643031
Click to expand...
Click to collapse
nothing, this ROM is MDK only. im pretty sure cm is the same way. i highly doubt we can get CM booting just by screwing with the kernel. i actually brought up the idea but.. it's probably not possible.
skepticmisfit said:
nothing, this ROM is MDK only. im pretty sure cm is the same way. i highly doubt we can get CM booting just by screwing with the kernel. i actually brought up the idea but.. it's probably not possible.
Click to expand...
Click to collapse
Actually, you are right, just screwing around with the kernel WILL NOT work, but building CM from source using the "build with stock kernel" option SHOULD work. If AOSP/GE will work, it should. Just ripping the Boot.mg out and replacing with ours will not work.
But I started work today and forked a lot of Github repos and have begun work on CM for SafeStrap. Time Will Tell
npjohnson said:
Actually, you are right, just screwing around with the kernel WILL NOT work, but building CM from source using the "build with stock kernel" option SHOULD work. If AOSP/GE will work, it should. Just ripping the Boot.mg out and replacing with ours will not work.
Click to expand...
Click to collapse
Yeah we do have a bit of the ground work with the AOSP/GE ROMs that mostly work on NC5 that could be used towards getting CM11 working. Now I don't know beyond that what it will take to get CM11 to work with the stock kernel but I would have to think that at least if it does get working then the issues we have right now on the AOSP/GE ROMs can be fixed since we'd have the ROM source/Github/etc to work from on this.
Well if anything, the at&t rom gives me hope for the future.. That ROM is a great daily driver. They even have WiFi tethering fixed (its a manual fix that requires putting commands into terminal emulator, its still a fix though)
Also for those who miss USB file transfer.. I've always found it to be way too slow for any practical purposes. Airdroid is way faster than USB mtp on touchwiz.
Just noticed CM11 official for hltevzw is now getting monthly builds... funny, we have no CM12 or CM13!
http://download.cyanogenmod.com/?device=hltevzw&type=
It got me thinking, though... there are a ton of KK/based roms that are very smooth. In fact, I still think kitkat is the best base for this device as far as stability and battery life. Just look at the size of some of the custom ROMS like DU (180-190 MB) and the fact that they boot in under 20 seconds... even on the initial boot. Crazy efficiency.
I am sure that most people here disagree and interest in running CM11 is pretty low. But it still seems like it should be an option... especially since it is the most current official CM we have (last build is 6-12-2016)
The problem is that the radio in Kitkat doesn't work when coming from OF1. Theoretically, it should work if you ODIN back to KK... but that is not an option given the root/unlock scenarios we have.
So, question is...how do we get the radio working on CM11 coming from OF1... hmmm
I like your thinking mightysween. I saw the same thing last week and wondered myself. Can this be done?
Droidify said:
I like your thinking mightysween. I saw the same thing last week and wondered myself. Can this be done?
Click to expand...
Click to collapse
It would seem that flashing the modem would work... but I tried two KK modems with no luck.
Will post some logcats, and maybe we can figure out the right combo.
IDK I am now strongly considering downgrading to 4.4.2. There are a whole lot more stable ROMS available for KitKat than Lollipop for this device. I might pull the trigger this weekend. Currently investigating viability.
Any luck on this?
Sent from my SM-N900V using Tapatalk
bishop0114 said:
Any luck on this?
Click to expand...
Click to collapse
Not yet... but wow. If you put a new looking theme on any of the refined CM11 based stuff (like DU), people would be abuzz about how smooth and responsive this "new" rom is. I think these older devices are just happier with the older android versions.
Just can't seem to make the radio work...
Have tried as far back as NC4/NK1 modems... but they either don't work at all or exhibit the same problems as OF1.
I wonder if @Moepda might have any insight having worked on sm900 ROMS through the 4.4 to 5.1 updates...
Seems that there must be a modem that would work...or is the newer bootloader version a problem in running 4.4 based roms?
Well... Stupid me never checked to see if ODIN flashing the modems was actually working. It is not! I have tried both tar.md5 versions and directly flashing the modem.bin, and while it appears to work and ODIN says "pass", the modem stays on OF1.
So that's the issue...
That said, it is not a radio problem in general, it is an LTE registration issue. So, when set to 3g only it works AOK!
If I can figure out how to get the flash of NK1 or NC4 modem to stick, I believe LTE would work...
mightysween said:
Well... Stupid me never checked to see if ODIN flashing the modems was actually working. It is not! I have tried both tar.md5 versions and directly flashing the modem.bin, and while it appears to work and ODIN says "pass", the modem stays on OF1.
So that's the issue...
That said, it is not a radio problem in general, it is an LTE registration issue. So, when set to 3g only it works AOK!
If I can figure out how to get the flash of NK1 or NC4 modem to stick, I believe LTE would work...
Click to expand...
Click to collapse
Sounds promising. I wonder if there is a zip we can install via TWRP.
Sent from my SM-N900V using Tapatalk
bishop0114 said:
Sounds promising. I wonder if there is a zip we can install via TWRP.
Click to expand...
Click to collapse
There used to be flashable modems here on XDA, but all the links are dead. I suppose I could just make one and try.
FWIW, I am running an OLD Dirty Unicorns moepda build from 2014, and it is quite refreshing after so long with cm12 and cm13. Fast, stable, and seemingly lacking nothing I use compared to CM12/13
mightysween said:
FWIW, I am running an OLD Dirty Unicorns moepda build from 2014, and it is quite refreshing after so long with cm12 and cm13. Fast, stable, and seemingly lacking nothing I use compared to CM12/13
Click to expand...
Click to collapse
Sounds interesting. Can you provide an installation guide based upon what you've done? Versions used, steps taken, etc. If you don't want to publish it to prevent people from damaging something you can PM me.
Thanks
Droidify said:
Sounds interesting. Can you provide an installation guide based upon what you've done? Versions used, steps taken, etc. If you don't want to publish it to prevent people from damaging something you can PM me.
Thanks
Click to expand...
Click to collapse
No steps at all, really... it just works. Flashed and then switch to 3g preferred.
I don't need LTE... so I haven't spent much time trying to figure it out. Both this old DU and CM11 monthly are working fine as long as LTE is shut off
Obviously, CM11 is available from get.cm
...
the last version of DU 4.4.4 is here:
https://www.androidfilehost.com/?fid=95784891001606282
mightysween said:
Obviously, CM11 is available from get.cm
...
the last version of DU 4.4.4 is here:
https://www.androidfilehost.com/?fid=95784891001606282
Click to expand...
Click to collapse
I am going to give this a whirl. I have always had trouble with finding the right gapps for KitKat though. Which did you select?
Notice much drop off in using 3G instead of LTE?
BTW In an earlier post I mentioned I was going to downgrade. Well, that's not really possible and you might already know that. I attempted 4.4.2 and was abruptly stopped by the bootloader. I did read though that 4.4.4 was possible, but if we can do all this and get a stable ROM that has GPS and Bluetooth functional why bother?
Droidify said:
I am going to give this a whirl. I have always had trouble with finding the right gapps for KitKat though. Which did you select?
Notice much drop off in using 3G instead of LTE?
BTW In an earlier post I mentioned I was going to downgrade. Well, that's not really possible and you might already know that. I attempted 4.4.2 and was abruptly stopped by the bootloader. I did read though that 4.4.4 was possible, but if we can do all this and get a stable ROM that has GPS and Bluetooth functional why bother?
Click to expand...
Click to collapse
I am on wifi about 90% of the time, and when I am not it is usually while driving. So having only 3g doesn't bother me.
Bluetooth and GPS seem to work fine... GPS is certainly faster and more stable than LP/MM
Droidify said:
I am going to give this a whirl. I have always had trouble with finding the right gapps for KitKat though. Which did you select?
Notice much drop off in using 3G instead of LTE?
BTW In an earlier post I mentioned I was going to downgrade. Well, that's not really possible and you might already know that. I attempted 4.4.2 and was abruptly stopped by the bootloader. I did read though that 4.4.4 was possible, but if we can do all this and get a stable ROM that has GPS and Bluetooth functional why bother?
Click to expand...
Click to collapse
Oh, and I just use open gapps nano... works fine
I take that back... You need to set the preferred network to LTE, let it connect (and then fail), and THEN set to 3G in order for it to stick.
Love the feature set from DU, but have to say that the 6-12-2016 nightly is pretty smooth.
So is LTE working on the 4.4.4 build?
Sent from my SM-N900V using Tapatalk
bishop0114 said:
So is LTE working on the 4.4.4 build?
Click to expand...
Click to collapse
No... It connects, but then disconnects and reconnects repeatedly.
3G works fine
No tests have been done on this rom, I compiled it remotely it may or may not boot, I am unable to test due to my work, I work away from home, no computer and can't risk phone while away from home, I will do my own test once I get home and have complete access to computer.
Again this is untested alpha, all risks are on you, I can't provide and help, make sure you know how to get your phone in and out of bootloops, make sure splash tool is working for your phone, if something goes wrong you may need it to restore your phone.
To all that test this rom good luck, and post back your results, those that choose not to test, not a problem I fully understand, this is not to be taken lightly.
https://www.androidfilehost.com/?fid=457095661767098671
your bootloader will need to be unlocked
you need twrp recovery
Good Luck.
Kernel source
https://github.com/vampirefo/android_kernel_mediatek_mt6735
device tree is based on
https://github.com/vampirefo/android_device_elephone_p8000
Device tree/source files pls
Also good job on finally getting this to work! Gonna download soon.
+1 for the device tree please.
Before I flash, was this ROM built off the 6.6 image that locks us out of using SPFT? I don't know if it even works that way but I just figured I'd ask to be safe.
Gr8 m8 8/8
Release the device tree on GitHub.
Do it.
Please.
Sent from my LG G4 using XDA Labs
Currently trying it out, will report back later.
Getting a status 7, saying this device was made for "R1_HD" and not "P6601". Gonna remove the updater script line that checks that and flash again.
jasonmerc said:
Getting a status 7, saying this device was made for "R1_HD" and not "P6601". Gonna remove the updater script line that checks that and flash again.
Click to expand...
Click to collapse
I got that too, that should work too but I just switched to vampire's TWRP and that worked for me.
RainofOranges said:
I got that too, that should work too but I just switched to vampire's TWRP and that worked for me.
Click to expand...
Click to collapse
How's the ROM? Did it boot yet?
jasonmerc said:
How's the ROM? Did it boot yet?
Click to expand...
Click to collapse
Doesn't look like it. It's hanging on the logo.
RainofOranges said:
Doesn't look like it. It's hanging on the logo.
Click to expand...
Click to collapse
Mine kept getting status 7, even with vampire's TWRP. Leave it booting at the log, let me know if it changes. Sometimes initial boot can take like 10-15 mins.
jasonmerc said:
Mine kept getting status 7, even with vampire's TWRP. Leave it booting at the log, let me know if it changes. Sometimes initial boot can take like 10-15 mins.
Click to expand...
Click to collapse
I'll let it sit for a while, then. I don't think anything will change, though.
Edit: Nope. Back to stock ROM for now, this doesn't boot yet.
jasonmerc said:
Mine kept getting status 7, even with vampire's TWRP. Leave it booting at the log, let me know if it changes. Sometimes initial boot can take like 10-15 mins.
Click to expand...
Click to collapse
Usually thats because of a bad download from my experience , since i used to get that error alot.
Thanks for testing, When I get home, I will test it on my phone, check logcat and see what I can find.
This will probably be my last public testing, The next test ROM I release will be private.
I will post notice here when ready, and those that tested this version and still want to test any future versions will receive a download link via pm.
Thanks to all that tested ROM.
Sent from my BLU ENERGY X PLUS using Tapatalk
any progress update?
KazuDante said:
any progress update?
Click to expand...
Click to collapse
Due to work, I haven't had time to even look at it.
I am debating and what to do.
Sent from my NS-P08A7100 using Tapatalk
vampirefo said:
Due to work, I haven't had time to even look at it.
I am debating and what to do.
Sent from my NS-P08A7100 using Tapatalk
Click to expand...
Click to collapse
We understand. and man it really bothers me alot due to the fact i dont understand none of this yet because I could of been working on kernels or helping since i have so much free time.
Eagerly waiting for a stable version. I am no tech geek so dont wanna risk on Alpha version
aaceaze said:
Eagerly waiting for a stable version. I am no tech geek so dont wanna risk on Alpha version
Click to expand...
Click to collapse
Well, we all have a to start somewhere... An actual "stable" version of CM may never really happen. I'd be happy to try the first build that actually boots up. No matter how buggy it might turn out, just so I can give you feedback and get a general sense of what this phone should feel, look like and behave out of the box.
I really miss the several options and customizations from CM ROMs... But above all, I really miss having a nicely made custom kernel with a good kernel manager app (like EX kernel manager) to set it up exactly the way I like it... I have faith in this device. Particularly because this phone is selling so well. I really hope for an official CM development for the R1 HD. Hopefully even a good custom kernel...! That would be awesome! Maybe then I'd be able to retire my Nexus 5. I have really missed having an external SD card... 64GB vs 32GB makes a huge difference.
I think the problem is in the boot.img, the init.
Sent from my BLU R1 HD using Tapatalk