Related
https://opensource.samsung.com/rece...hod=reception_search&searchValue=SGH-I777_ATT
this is awesome , this means we can have a rooted kernel on launch day!!!!
AT&T Galaxy S II Sub-Forum?
Where is the love for our own forum since we now have the kernel?
Edit: Well, it just happened this morning. Cool, our own forum.
The AT&T version is close enough to the international version that maybe they should keep the same forum? Or just have a sub forum for the dev board like i9003 on the i9000 board.
anilkuj said:
https://opensource.samsung.com/rece...hod=reception_search&searchValue=SGH-I777_ATT
this is awesome , this means we can have a rooted kernel on launch day!!!!
Click to expand...
Click to collapse
Hope the devs can find something they may be able to use on our version of this great phone.
I uploaded the file here also in case site goes down or anything
http://www.multiupload.com/R7CG8ZR085
Wow. Samsung releases something ahead of hardware and a carrier to boot. More reason to boot atnt.
I voided my warranty and your mum.
anilkuj said:
https://opensource.samsung.com/rece...hod=reception_search&searchValue=SGH-I777_ATT
this is awesome , this means we can have a rooted kernel on launch day!!!!
Click to expand...
Click to collapse
Nice head start for the devs
pukemon said:
Wow. Samsung releases something ahead of hardware and a carrier to boot. More reason to boot atnt.
I voided my warranty and your mum.
Click to expand...
Click to collapse
Awesome sig sir.
sent from my stock Infuse at Tranquility Base.
Looking forward to this... but I hear Sammy has been really good with the stock ROMs for this model. Great starting points for our amazing devs
Sure hope a custom ROM gets put up soon after launch. I'm sure the stock one will suffice for a few days. Not looking for anything fancy, just want some good 'ol root access.
bigblue95z said:
Sure hope a custom ROM gets put up soon after launch. I'm sure the stock one will suffice for a few days. Not looking for anything fancy, just want some good 'ol root access.
Click to expand...
Click to collapse
I'm sure you will be able to root it pretty quick. A custom kernel may take a few days... a good one will take a few weeks, if someone is able to dedicate some real time to it. Sure you will get some quick ROMs that are basically stock with a custom theme and bloatware removed, but I digress.
I THINK I read that DG already has something SETUP for the ATT version and just waiting to ha e it in hand to test it. Would be awesome to get some tentative roms set up before launch day so I can flash the same day
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
RockRatt said:
I THINK I read that DG already has something SETUP for the ATT version and just waiting to ha e it in hand to test it. Would be awesome to get some tentative roms set up before launch day so I can flash the same day
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
Click to expand...
Click to collapse
Heck yeah! Where'd you read that?
RockRatt said:
I THINK I read that DG already has something SETUP for the ATT version and just waiting to ha e it in hand to test it. Would be awesome to get some tentative roms set up before launch day so I can flash the same day
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
Click to expand...
Click to collapse
Yep He will be developing the same ROMs for both phones although the Kernel will have to be reoriented due to the button on the international version like the i9000 was re the Captivate. I believe ROMS will be interchangeable but not kernels.
anilkuj said:
https://opensource.samsung.com/rece...hod=reception_search&searchValue=SGH-I777_ATT
this is awesome , this means we can have a rooted kernel on launch day!!!!
Click to expand...
Click to collapse
Depends on how different the initramfs is - fortunately it probably won't be significantly different.
Here's a recommendation I have from my experience with the Infuse community - I'm on the fence about upgrading Sunday, but since the AT&T GSII variant has a smaller screen and no Wolfson I'm likely to stick with the Infuse:
On launch day, have some people on IRC coordinating. Once a root kernel is developed, don't immediately post it here. Pick a handful of people to flash and test. Once they have root, their first order of business should be getting a clean stock system dump.
Once you have a system dump you can make an Odin/Heimdall-flashable system image with root - have someone who did NOT flash the root-injection kernel flash THAT in order to get a dump of the stock kernel. Without that you'll be flying blind as far as initramfs.
A few tips:
http://forum.xda-developers.com/showpost.php?p=17777056&postcount=42 - my initial tips for the Epic 4G Touch crew
http://forum.xda-developers.com/showthread.php?t=1081239 - You'll need this to make a Heimdall-flashable image from your system dump
https://github.com/mistadman/Extract-Kernel-Initramfs - Once you've dumped a stock kernel image, use that script to extract the initramfs. Put that up on github ASAP.
Also, I strongly recommend putting a straight unmodified source tarball up on github, and then work on getting it to a compilable state from there. That way the process of "cleaning up" the Samsung source is documented in git commits. See the early commits from LinuxBozo at https://github.com/Entropy512/linux_kernel_sgh-i997r/commits/master?page=2 as an example
If all goes well, I will have my GS2 Sunday morning, and be on IRC as well, ready to test flash the rooted kernel for you guys.
Hmm, I get bored @ SGS2.
If someone can post stock initramfs, aka "adb pull /"
Remove /data and /cache from the local files on your computer and then zip it up and post it here, you have root
netchip said:
Hmm, I get bored @ SGS2.
If someone can post stock initramfs, aka "adb pull /"
Remove /data and /cache from the local files on your computer and then zip it up and post it here, you have root
Click to expand...
Click to collapse
Hmm - good point, I don't think anything in initramfs has permissions set such that a non-root ADB user can't read it.
Entropy512 said:
Hmm - good point, I don't think anything in initramfs has permissions set such that a non-root ADB user can't read it.
Click to expand...
Click to collapse
Sorry, miss understand.
It is not required to have root, I am now testing with my SGS2.
netchip said:
Sorry, miss understand.
It is not required to have root, I am now testing with my SGS2.
Click to expand...
Click to collapse
That's what I meant - Previously I was assuming that to get a "good" initramfs dump, root would be required. However, after reading your post I realized that all of the relevant files in the initramfs SHOULD be readable by any user, even without root permissions.
Still it's ideal to get a direct initramfs extract from the kernel zImage as soon as possible.
Entropy512 said:
That's what I meant - Previously I was assuming that to get a "good" initramfs dump, root would be required. However, after reading your post I realized that all of the relevant files in the initramfs SHOULD be readable by any user, even without root permissions.
Still it's ideal to get a direct initramfs extract from the kernel zImage as soon as possible.
Click to expand...
Click to collapse
Yeah, I know.
But I will give you root kernel if you give me: /lib, /res, all *.rc files, /vendor and /sbin.
Here is the link for the kernel source that JUST released by HTC.
http://www.htcdev.com/devcenter/downloads
I'm currently downloading it now and will reupload. The links are all the same so it doesnt matter which one you download. I'll post my mirror up soon.
Let the new kernels begin!
3.1.10 (International Model)
http://d-h.st/PLO
1.15.502.9 (AT&T Model)
http://d-h.st/tDe
hasoon2000 said:
Here is the link for the kernel source that JUST released by HTC.
http://www.htcdev.com/devcenter/downloads
I'm currently downloading it now and will reupload. The links are all the same so it doesnt matter which one you download. I'll post my mirror up soon.
Let the new kernels begin!
Click to expand...
Click to collapse
DAMN YOU! i was JUST about to go to bed
Lloir said:
DAMN YOU! i was JUST about to go to bed
Click to expand...
Click to collapse
I'm an a-hole, I know =D
It's so slowwwwwwwww. I have a 20 mbps connection. It's downloading at 70kb!
hasoon2000 said:
I'm an a-hole, I know =D
It's so slowwwwwwwww. I have a 20 mbps connection. It's downloading at 70kb!
Click to expand...
Click to collapse
i've already got it i'll have Maxwen take a look at it tomorrow for me, while i'm doing CM10 (CM10 has to be done ASAP because im rom less xD )
How different is the HoX+ kernel vs the OG HoX ?
Would love to have a kernel wizard like francisco working on this
Finally a reason for me to root!
*downloading*
*fires up linux box*
*logging to git*
Yeehaw
Is there a daring soul willing to flash and test the stock kernel I compiled? No warranties
I would test myself but I don't have time for unlocking/rooting today, expecting calls.
http://elite-force.eu/emoxp/kernel-onexp-stock-1.14.401.16.zip
(NOT WORKING UNTIL WE GET S-OFF)
Just flash in recovery and pray
Yeah, i will download tonight and look into it how different it is to onex source and then developing can start ! Finally work again
nik3r said:
Is there a daring soul willing to flash and test the stock kernel I compiled? No warranties
I would test myself but I don't have time for unlocking/rooting today, expecting calls.
http://elite-force.eu/emoxp/kernel-onexp-stock-1.14.401.16.zip
Just flash in recovery and pray
(It's based on int version)
Click to expand...
Click to collapse
Kernels can't be flashed via recovery if they are S-On. HTCDev still has the restriction. Only way to bypass it is if your phone has S-Off.
Also, can you make the kernel into a boot.img rather than a zImage? Users can place the system folder and the boot.img in my toolkit so they can flash it with a click of a button.
Also, users would have to flash the kernel TWICE or else BT/WiFi will not work. Since the kernel is secured, the first flash will unsecure it and the second flash will allow the modules to be pushed.
Good to know, I will look up how to do that when I get home. But does the zImage works? If it does we should setup a community git repo for others to fork, I have very fast upload at home so I could push it but someone else should maintain it, git hates me
Sent from my HTC One X+ using xda premium
nik3r said:
Good to know, I will look up how to do that when I get home. But does the zImage works? If it does we should setup a community git repo for others to fork, I have very fast upload at home so I could push it but someone else should maintain it, git hates me
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
zImage still wouldn't work. The kernel partition is restricted and must be flashed via fastboot.
Kernel devs should be popping up when people get the phone!
So basically I need boot.img from an unlocked and rooted HOX+ in order to make my own package until we get s-off?
Someone care to upload one?
Should be
Code:
# adb shell
# dd if=/dev/block/mmcblk0p? of=/sdcard/boot.img
EDIT: I have just finished the first basic round of performance tweaks in the kernel, can't wait to actually test it on my plus
If you guys send me a rooted boot.img I suppose I could inject the zImage and let you try.
nice!!!! let the Kernel Gurus begin!!!!!
https://github.com/Lloir/htc_enrc2b_kernel
it's up on my git if anyone wants to clone it fork it do whatever to it
can anyone extract and upload me the following files out of the onex+ please:
/system/vendor/firmware/fw_bcm4329.bin
/system/etc/firmware/fw_bcm4334.bin
would highly appreciate it (I only have a normal one X and dont have them)
n3ocort3x said:
can anyone extract and upload me the following files out of the onex+ please:
/system/vendor/firmware/fw_bcm4329.bin
/system/etc/firmware/fw_bcm4334.bin
would highly appreciate it (I only have a normal one X and dont have them)
Click to expand...
Click to collapse
Wish I could help but I am on AT&T version. N3o makes some beasty kernels. Someone needs to get him what he needs.
I am starting to worry about the AT&T version though. I am happy to test (and have a LOT of kernel testing experience) if you end up building a AT&T/Telus version
Sent from my HTC One X+ using Xparent Blue Tapatalk 2
Updated with AT&T source code!
hasoon2000 said:
Updated with AT&T source code!
Click to expand...
Click to collapse
WOW! This is awesome! I was hoping HTC wouldn't lag too far behind with releasing the kernel source code for the AT&T version. I'm really glad it is out so people can tinker with it now. The only thing better than the HOX+ is a modified HOX+.
Can't wait to play w/ the modified kernels we will eventually see. Especially looking forward to seeing if I got a good SoC that can handle some under volting action.
Can you use HTC One X+ (At&t) kernel on any stock rom.
If this kernel development is alive?
So I went ahead and put together a few different builds based on the stock 1.11.605.4 firmware and the styles they will come in are as follows:
Stock - Odexed no root (Must flash Superuser package to re-obtain root
Stock -Odexed root busybox
Stock - Odexed root busybox debloated
Stock - Deodexed root busybox
Stock - Deodexed root busybox debloated
These are basically for those that are looking for a specific something and hopefully these being one of those things, and also as a cushion in case you attempted something and you need that stock build to fall back on..
The problem I'm having is basically with the updater script for some odd reason and can not figure out why.. I went ahead and ran "cat /proc/emmc" to make sure the mount points are straight for system and data and I just can't figure out what the problem is whenever I try and flash something.. I know for sure the rest of the build is on point.... The error I'm getting is "Status 7" which is updater-script update binary and mount point related.... I just don't get it... Maybe someone with a little more knowledge in the edify script field can help me figure this out... Unless it has something to do with the script missing something it's suppose to be setting perms on or what have you but I think that would maybe be a "Status 6" error.............. Who knows.........
So yeah anyone willing to help me out so we can at least get some Verizon HTC One Max love here and hopefully and by all means please do so use these builds as bases for your own custom themed out work for the Vzw t6 crew!!! Hit me up!!!!!
Murda out......
Jcase is encouraging me to hand write my own updater-script as he says he hand writes his own all the time.... I said lololol haha.... I tried and failed! I'll upload the build and all mount point info and let someone take a crack it if you want... I even attempted out of curiosity to borrow the Sprint and International updater script with that Insertcoin based updater and that didn't work either.... Like I said heeeeelllllpppppppppp lol
While I was working with beaups he figured out that htc did not include most of the common commands used for scripting. There was no unzip, untar, etc. Maybe that is the issue?
I just got home from work now and I gotta run my kid to wrestling which is 45 minutes.. I'll be home by 7pm NY time and I'll be working on it then!
Jiggity Janx said:
While I was working with beaups he figured out that htc did not include most of the common commands used for scripting. There was no unzip, untar, etc. Maybe that is the issue?
Click to expand...
Click to collapse
Murrda said:
I just got home from work now and I gotta run my kid to wrestling which is 45 minutes.. I'll be home by 7pm NY time and I'll be working on it then!
Click to expand...
Click to collapse
Family first!
Just an update to anyone who cares, I got the updater-script done and it no longer kicks back any errors but now I'm having update binary issues which is most likely because I stop the Sprint One Max update binary... So I'm working on fixing that issue right now. As soon as I get this to flash and boot up and I know that calls data wifi and all that work I will begin uploading all the builds I had mentioned in the OP for the Verizon HTC One Max! Soooooo Stay tuned Vzw crew!
Murrda said:
Just an update to anyone who cares, I got the updater-script done and it no longer kicks back any errors but now I'm having update binary issues which is most likely because I stop the Sprint One Max update binary... So I'm working on fixing that issue right now. As soon as I get this to flash and boot up and I know that calls data wifi and all that work I will begin uploading all the builds I had mentioned in the OP for the Verizon HTC One Max! Soooooo Stay tuned Vzw crew!
Click to expand...
Click to collapse
Thanks Much Murrda, been waiting for a stock flashable VZW Rom for my semi broken One Max.
I'm really trying man, but yeah no problem. It will be nice to at least have something for us to have as a backup and something for others to base their work off of. Finally begin some type of ROM work for us Verizon users!!
mustangmao said:
Thanks Much Murrda, been waiting for a stock flashable VZW Rom for my semi broken One Max.
Click to expand...
Click to collapse
Murrda said:
I'm really trying man, but yeah no problem. It will be nice to at least have something for us to have as a backup and something for others to base their work off of. Finally begin some type of ROM work for us Verizon users!!
Click to expand...
Click to collapse
Absolutely, I have searched everywhere (both English speaking site as well as Chinese Google/Baidu and etc sites) but no one has even started any work on t
Absolutely, I have searched everywhere (both English speaking site as well as Chinese Google/Baidu and etc sites) but no one has even started any work on the Verizon One Max (stock or custom Rom). You are the Pioneer in this area. Thanks so much for your hard work, keep up the good work man. I’d be more than happy to donate some $$ to your Dev work.
he Verizon One Max (stock or custom Rom). You are the Pionner
No sweat dude... They are coming! Thanks
mustangmao said:
Absolutely, I have searched everywhere (both English speaking site as well as Chinese Google/Baidu and etc sites) but no one has even started any work on the Verizon One Max (stock or custom Rom). You are the Pioneer in this area. Thanks so much for your hard work, keep up the good work man. I’d be more than happy to donate some $$ to your Dev work.
he Verizon One Max (stock or custom Rom). You are the Pionner
Click to expand...
Click to collapse
Hi! I am rebel1699. I have done work on the S4 i337 (root for 4.4.2). Recently, I bought an SCH-R960 for something to do. After messing with it for a while, I have discovered that custom roms are indeed possible, but with some things that need work. Here is my current configuration
SlimKat 4.4.4
Philz Touch Recovery
As you may know, the touch recoveries do not respond to touch on this model. However, the vol +/- and power for select still work fine. After getting this ironed out, it was time to experiment. I downloaded SlimKat, and made a few modifications. Booted to recovery and made my nandroid. Then, on to wipes and install. Results---
Upon reboot, I was greeted with the "Warranty bit:kernel" on the top of the sceen. I didnt care. Warranty was long gone anyways. But, it booted into SlimKat just fine. Heres where the dev needs to begin. There is NO TOUCH. I even made a flashable of the stock 4.4.2 kernel modules, but still no help. Not unexpected, considering the recoveries do the same. Using my otg, I connected a mouse for navigation. It is indeed the custom kernel. WiFi, bt, and everything else seem to work fine. I cannot test cellular operation as I am not a US Cellular customer. So, there is another issue. I guess it could be possible to flash a correct radio. Not sure.
First things first---We need touch drivers working on this to go any further. We get that, and sky is the limit.
You probably have to backported the input drivers for your model
Just pull official kernel sources from samsung open modify the drivers of cm kernel
Sent from my HTC D816w using XDA Free mobile app
Grarak said:
You probably have to backported the input drivers for your model
Just pull official kernel sources from samsung open modify the drivers of cm kernel
Sent from my HTC D816w using XDA Free mobile app
Click to expand...
Click to collapse
Same as I was thinking. Sound is also out, but I fully expected that to be the case. Pulling the sammy input drivers should also allow for a custom touch recovery to be modified for the device. TWRP 2.7.0.1, preferrably. I will see what I can do over the next few days. Just started using a new laptop, so I have to get the time to sit down and set up a new dev environment. But again, I wont be able to test cellular radio compatibility. I use AT&T, so nno good for that.
Personally, Im buying the i9200 intl for my own use. But ill do what I can to help these US Cellular folks. They have not seen any development at all. Craigslist is littered with this SCH-R960. I understand why.
Why
Why are you saying that the touch recovery's don't work on this model. I flashed philz on mine and used it to gain root. Worked just fine for me!
MeatHammer311 said:
Why are you saying that the touch recovery's don't work on this model. I flashed philz on mine and used it to gain root. Worked just fine for me!
Click to expand...
Click to collapse
Because after flashing both philz touch and twrp 2.7.1.0 meliusltexxx recoveries, touch works on neither. The boot image does not contain the touch input drivers for the SCH-R960. Manual navigation is still operable
I guess you only have to enable some options in defconfig
Sent from my HTC D816w using XDA Free mobile app
Grarak said:
I guess you only have to enable some options in defconfig
Sent from my HTC D816w using XDA Free mobile app
Click to expand...
Click to collapse
Good to hear. I just got a new laltop and have been getting my enviro set back up and going.
Grarak said:
I guess you only have to enable some options in defconfig
Sent from my HTC D816w using XDA Free mobile app
Click to expand...
Click to collapse
These options your talking about, are they options to enable touch on these recovery's??
MeatHammer311 said:
These options your talking about, are they options to enable touch on these recovery's??
Click to expand...
Click to collapse
The recoveries, and the roms. All either is lacking are those thing within thier perspective kernels. Roms will still need more work, eg...audio. And as I said, I cannot comment on the celluler end of it since I do not have US Cellular service.
Some of the roms need an edit to thier updater script to install. Others do not. They just have to be checked first. Just edit out anything that call to Format "0". I cant remember the mmcblk #
Any more progress with this? I have a sch-r960 and I would gladly help test roms or do what I can.
Cheers
helpfull
statikrage said:
Any more progress with this? I have a sch-r960 and I would gladly help test roms or do what I can.
Cheers
Click to expand...
Click to collapse
I just bought one of these as well... have nandroid and stock... attempting to build up first rom/port.... we shall see... so device tree anywhere... tried to flash meliusltexx roms, but always get error 7
so cm 11 installed... shows lte... no touch... not sure where to go from here.... new to this... always just been a flasher..... never tried to port....
antimidas said:
I just bought one of these as well... have nandroid and stock... attempting to build up first rom/port.... we shall see... so device tree anywhere... tried to flash meliusltexx roms, but always get error 7
Click to expand...
Click to collapse
Did you edit the rom updater script before installing?
hmmmmm
not sure what to change other than specific model... it points to /system/xbin/touch, but there is no file there... yet in deodexedf stock rom the updater-script points to /system/bin/touch... which also is not in that zip either. gonna try to compile aosp then pull my touch file from phone i guess..... a bt difficult to find specific info at this point
antimidas said:
not sure what to change other than specific model... it points to /system/xbin/touch, but there is no file there... yet in deodexedf stock rom the updater-script points to /system/bin/touch... which also is not in that zip either. gonna try to compile aosp then pull my touch file from phone i guess..... a bt difficult to find specific info at this point
Click to expand...
Click to collapse
I would help more, but sadly I do not have the phone anymore. Anything more from me would be no more than wild speculation, lol.
rebel1699 said:
I would help more, but sadly I do not have the phone anymore. Anything more from me would be no more than wild speculation, lol.
Click to expand...
Click to collapse
i need idea of what to edit.... just changing model names doesnt seem like it would work... but maybe im wrong... hardware is the same as meliusxx.... so i just dont get it... just gonna experiment i guess.... gonna go in and change all reference i see.... also may try to remove the part that lists the touch... maybe if it isn't flashed the orig firmware i lay over top of will keep driver intact.... i dunno, just gonna keep at it.... cant seem to get help anywhere. at least you responded!!! Thank You for that. /bow
R960 vs I9205
What is the difference. Appear exactly the same in specs. Only difference appears to be the cellular provider. Has anyone tried to flash a I9205 to an R960 Mega 6.3 to see what happens? If so, what was the result??
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