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??
Related
Hey again, as usual i don't post something unless i feel that something is being left out or forgotten.
Nothing big but as you may know we xperia play verison or (CDMA) users are often forgotten in rom development. That's where i come in
i feel that the cdma xperia is neglected and does not much dedicated support. One example is GB roms. If you didn't know (or it does not affect you) when trying to install a R800i ROM to a R800x phone after the bootanimation you usually get stuck on a blank or slightly gray screen (depending on the rom makers theme.) It is VERY annoying and it is IMPOSSIBLE to get past it. But i have threw together a little patch for VERIZON CDMA USERS ONLY!!! that corrects this issue. to use is very easy.
just flash this zip immediately after flashing your GB rom of choice!! and boot
NOTE:a small FC will appear, THIS IS NORMAL! And then the verizon setup will appear. done!
Also: THIS DOES NOT FIX CDMA 3G/4G SERVICE!
THE PATCH IS FIXED AND READY TO GO!!
DOWNLOAD
I'll have to try this out sometime. I just recently got MIUI installed onto my device (thanks to CosmicDan). I've always wanted to try the Gin2JellyBean ROM and the True Ancestor ROM. Thanks for this, I'll definitely try this out soon. :3
So is this a CDMA patch to allow any GSM rom to he installed then flash this patch and it will work? I spent months trying to get a working cdma patch but to no avail. Best I got was a the dialer wouldn't force close and it would attempt to make a call but would then just sit there. Ill have to try this out.
Sent from my R800x using xda premium
This thread holds my interest....
Finally some good developer fought of the other people and their inability to use ROMS.....
ozzmanj1 said:
So is this a CDMA patch to allow any GSM rom to he installed then flash this patch and it will work? I spent months trying to get a working cdma patch but to no avail. Best I got was a the dialer wouldn't force close and it would attempt to make a call but would then just sit there. Ill have to try this out.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
No it doesn't fix cdma, I tried it with Dixperia. And it booted to show the homescreen and just sat there with "no network available." Up in the notification bar.
If this works, YOU.ARE.AWESOME!
cj360 said:
No it doesn't fix cdma, I tried it with Dixperia. And it booted to show the homescreen and just sat there with "no network available." Up in the notification bar.
Click to expand...
Click to collapse
Maybe you should read the op to see what this does. Clearly you did not
cj360 said:
No it doesn't fix cdma, I tried it with Dixperia. And it booted to show the homescreen and just sat there with "no network available." Up in the notification bar.
Click to expand...
Click to collapse
He made this to make GSM roms run on CDMA devices, the purpose of this patch, if I'm correct, is to help these GSM only developers develop for CDMA users, and wizard CDMA developers can take care of the signal, then make a full universal patch within the near future. That's my perspective.
I'm impressed either way!
It took this long for this to be released? Surprised no one has done this yet for locked people. Good job!
swebosdev said:
Maybe you should read the op to see what this does. Clearly you did not
Click to expand...
Click to collapse
I thought he was asking if this fixed network for cdma, which your right it doesn't. But oh well I was wrong in my post :silly:
Anyone else getting an error code when attempting to flash this? I get the "status 6"........ or am I missing something something and this is not supposed to be flashed?
No I got the same thing. I took the files from his mod and added them to the rom I tested. I think the binary in the zip is bad but I'm not sure.
Sent from my Xperia Play
NOTE: this does not fix the network btw, this allows you to install GB roms
xdarkmario said:
NOTE: this does not fix the network btw, this allows you to install GB roms
Click to expand...
Click to collapse
Are you supposed to flash this file to any GB Rom you install? As I noted above when I attempted to flash of gives me the error code Status 6.
Sent from my R800x using xda premium
ozzmanj1 said:
Are you supposed to flash this file to any GB Rom you install? As I noted above when I attempted to flash of gives me the error code Status 6.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
hmm that's weird i'll take a look.
ozzmanj1 said:
Are you supposed to flash this file to any GB Rom you install? As I noted above when I attempted to flash of gives me the error code Status 6.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
ok i see what you mean. its a script error on my hand. i am fixing and reuploading now
Ok just fixed and re uploaded the zip, it works now!
Just to clarify... this DOES NOT allow me to use the phone features of a GSM rom on my CDMA device right? It just fixes the phone from freezing when flashing certain GB roms correct?
Xperia Player said:
Just to clarify... this DOES NOT allow me to use the phone features of a GSM rom on my CDMA device right? It just fixes the phone from freezing when flashing certain GB roms correct?
Click to expand...
Click to collapse
yes this ONLY allows you to install any gsm rom on our cdma phones no network
Just tried to instance the system.sin for a stock SE based rom and got kobworking homescreen. Just a tip though flashing true ancestor the rom works out the door without the need to flash this patch but again nobworking phone functions and none of the aokp, ft5, cyanogenmod cdma patches work. So if you just want a working device with no phone functions then the true ancestor works out the door no need tobflash this patch.
Sent from my R800x using xda premium
I've been running AOSP 4.2 on my S4 for quite a while with no issues. Upon trying to upgrade to 4.3 though, boots take upwards of 5 minutes and the baseband isn't recognized (it literally shows "Baseband Version: Unknown"). I then tried to revert to one of the various 4.2 ROMs still out there, and am encountering quite a bit of general instability (lots of FCs), however, the baseband works fine. Any idea what is going on?
I should add that though I am using the ME7 modem, everything else is MDK and that these symptoms are pervasive through several different ROMs.
Update:
When trying to switch to RUIM/SIM in the Radio Settings, I get the following logcat:
Code:
/CdmaSubscriptionListPreference( 1762): Setting Cdma subscription source failed
I/Use2GOnlyCheckBoxPreference( 1762): get preferred network type, exception=com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
have you gone into network settings and verified that your subscription is set to RUIM/SIM instead of NV?
Did you compile the AOSP yourself? What build are you using? Project Elite's baseband and network all work out of the box no problems. I'm not sure if they posted it yet though.
Dubbsy said:
have you gone into network settings and verified that your subscription is set to RUIM/SIM instead of NV?
Click to expand...
Click to collapse
Yes; Whenever I do that I get the logcat I mentioned above and the setting doesn't stick (ie it immediately changes back to NV).
Edit:
When I retried, I got:
Code:
E/CdmaSubscriptionListPreference( 1618): Setting Cdma subscription source failed
Dubbsy said:
Did you compile the AOSP yourself? What build are you using? Project Elite's baseband and network all work out of the box no problems. I'm not sure if they posted it yet though.
Click to expand...
Click to collapse
No; this is with several 4.3 based ROMs including CM and Pacman.
Edit 2:
I'm downloading the Darkslide ROM to try to get that baseband installed and will keep this thread up to date with the result.
murphycr said:
Yes; Whenever I do that I get the logcat I mentioned above and the setting doesn't stick (ie it immediately changes back to NV).
Edit:
When I retried, I got:
Code:
E/CdmaSubscriptionListPreference( 1618): Setting Cdma subscription source failed
No; this is with several 4.3 based ROMs including CM and Pacman.
Edit 2:
I'm downloading the Darkslide ROM to try to get that baseband installed and will keep this thread up to date with the result.
Click to expand...
Click to collapse
Oh you aren't running pure aosp. Gotcha.
I was able to hold subscription on PAC, Slim, and CM10.2
Did you edit anything prior to install? Was your phone's data working just before switching to 4.3?
Dubbsy said:
Oh you aren't running pure aosp. Gotcha.
I was able to hold subscription on PAC, Slim, and CM10.2
Did you edit anything prior to install? Was your phone's data working just before switching to 4.3?
Click to expand...
Click to collapse
Yes. It also works if I switch back to 4.2, but then other things break. Anyway, I'm about to flash the baseband you referred to, so I'll see where that gets me.
Thanks!
murphycr said:
Yes. It also works if I switch back to 4.2, but then other things break. Anyway, I'm about to flash the baseband you referred to, so I'll see where that gets me.
Thanks!
Click to expand...
Click to collapse
the baseband used in all 4.3 builds I've used was MDK.
Me7 baseband is not as good as some people like to claim. It is buggy, and in my opinion it was rushed to release because Verizon wanted to quick kick everyone in the nuts. I tried me7 a few times and everytime I had worse spottier service.
The project elite aosp I was talking about is actually full aosp. And I haven't seen a post for it yet.
Another thing I've noticed in general... What recovery are you using? I don't trust CWM(any variation) at all anymore. I've seen too many installs act up and just not work right at all with CWM and after trying it on twrp 2.5.0.2 the same exact installer worked fine. :silly: I don't know why, but regardless the layout of CWM is piss poor anyway. If you are using CWM, click the link in my sig to go to my GE build. In the second post I have flashable recoveries posted. You can try one out just to see and if you get the same results just flash back to your desired/current recovery:good:
I was having the same problem with my own cm10.2 builds. I blew out my device and vendor repos several times and finally decided that there had to be something in frameworks that doesn't like the dev edition radios. The nightlies wouldn't even work. I ultimately wound up using the official cwm (non-loki only) and was finally able to change from nv to ruim/sim.
Sent from my SCH-I545 Dev Edition using xda app-developers app
So you used the non-loki'd CWM to do what fixed it? (I presume simply having it installed didn't fix it automatically)
On the dev edition, the general consensus in the beginning was that philz touch(cwm based) was the recovery to use probably because he offered a non-loki version. We don't need loki fortunately because of our unlocked bootloader. I later found out that official cwm was also not lokified. If you have the retail version, unfortunately you are stuck with the loki recovery. I was just suggesting that you might try a different cwm since they are not all created equal.
Edit: I guess what I was really trying to say is just try another recovery. Not necessarily one over the other (cwm vs. twrp). It's not the non-loki part that will make the difference. Hopefully you'll find one that works for you. But who would have known that would cause it.
Sent from my SCH-I545 using xda app-developers app
OLD&SLOW said:
On the dev edition, the general consensus in the beginning was that philz touch(cwm based) was the recovery to use probably because he offered a non-loki version. We don't need loki fortunately because of our unlocked bootloader. I later found out that official cwm was also not lokified. If you have the retail version, unfortunately you are stuck with the loki recovery. I was just suggesting that you might try a different cwm since they are not all created equal.
Edit: I guess what I was really trying to say is just try another recovery. Not necessarily one over the other (cwm vs. twrp). It's not the non-loki part that will make the difference. Hopefully you'll find one that works for you. But who would have known that would cause it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I've tried both TWRP and PhilZ. Neither seemed to do it. At this point I'm just going to do a full ODIN.
Thanks for all the help though!
No problem, I just hope you figure it out. There are too many people using aosp 4.3 roms with no problems for this to be impossible. :thumbup:
Sent from my SCH-I545 using xda app-developers app
murphycr said:
I've tried both TWRP and PhilZ. Neither seemed to do it. At this point I'm just going to do a full ODIN.
Thanks for all the help though!
Click to expand...
Click to collapse
I have an already Loki patched cwm touch posted in my list if you wanted to try it too.
I've found Odin helps clean all the garbage out though. So either way
Good luck!
sent from my Verizon Galaxy sIV
Hey guys so basically the thread title says it all. I need a few testers who have the Canadian variant sgh-i527m who can test a rom base for me. What I need is confirmation that everything works on the base ie Bluetooth, data, WiFi, NFC,etc. Once deemed a stable base I can work on making the magic happen of adding cool features.
Of course the standard risks apply: you are responsible for anything you flash or that happens as a result. As always please make a nandroid backup before flashing and ensure you are using the latest, stable recovery
At this point the ROM is rooted, deodexed, zipaligned all apks and Knox free
Here is the link
https://mega.co.nz/#!KRRQXKBb!183bVTwJsmg_Wd-VfjHO-YYhKa4tlea7R4Cf6R3sN7g
Please share your results
Thanks
Sent from my GT-I9205 using Tapatalk
markbencze said:
Hey guys so basically the thread title says it all. I need a few testers who have the Canadian variant sgh-i527m who can test a rom base for me. What I need is confirmation that everything works on the base ie Bluetooth, data, WiFi, NFC,etc. Once deemed a stable base I can work on making the magic happen of adding cool features.
Of course the standard risks apply: you are responsible for anything you flash or that happens as a result. As always please make a nandroid backup before flashing and ensure you are using the latest, stable recovery
At this point the ROM is rooted, deodexed, zipaligned all apks and Knox free
Here is the link
https://mega.co.nz/#!KRRQXKBb!183bVTwJsmg_Wd-VfjHO-YYhKa4tlea7R4Cf6R3sN7g
Please share your results
Thanks
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
Hello,
I'm testing it on a i9205....
I installed it over a 4.2.2 bootloader as I never installed KK. So it looks like KK is installing over 4.2.2 Mega fire bootloader
.
I'm finishing up to setup all my account and let you know. So far its working well, the first run Wizard even detect my country "France", it did not before in 4.2.
I ll keep you posted but so far looking good.
Thanks
see screenshot attached
Just a small adjustement, on the i9205 the wifi is not turning on... I dont know why, a driver issue maybe. I will try replace wifi firmware and modules if I can.
Also when I go to ->Setting->security it says setting has stopped. then the phone is rebooting
pierrottls31 said:
Just a small adjustement, on the i9205 the wifi is not turning on... I dont know why, a driver issue maybe. I will try replace wifi firmware and modules if I can.
Also when I go to ->Setting->security it says setting has stopped. then the phone is rebooting
Click to expand...
Click to collapse
OK thanks for the feedback. If you're still on the ROM can you run a lotcat and try wifi and also go back to settings security. And then send me the logcat. If you send me it with those issues recreated I should be able to see what the problem is
Sent from my Nexus 5 using Tapatalk
markbencze said:
OK thanks for the feedback. If you're still on the ROM can you run a lotcat and try wifi and also go back to settings security. And then send me the logcat. If you send me it with those issues recreated I should be able to see what the problem is
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sorry I cant, I had to go back to Mega Fire rom as I had no Wifi and cannot install Titanium to restore everything (As I cannot access security options) I had to revert to 4.2.2.
I also tried to modified your zip with a i9205 boot.img and all the System files into your zip from another 4.4.2 i9205, and I had the same issue. I'm starting to wonder if I dont have a radio issue compatibilty or my bootloader 4.2 is messing with some feature (like android finding knox is not on the bootloader). If you have any idea, I dont mind trying again but so far I would like to preserve my bootloader as my phone still under warranty.
pierrottls31 said:
Sorry I cant, I had to go back to Mega Fire rom as I had no Wifi and cannot install Titanium to restore everything (As I cannot access security options) I had to revert to 4.2.2.
I also tried to modified your zip with a i9205 boot.img and all the System files into your zip from another 4.4.2 i9205, and I had the same issue. I'm starting to wonder if I dont have a radio issue compatibilty or my bootloader 4.2 is messing with some feature (like android finding knox is not on the bootloader). If you have any idea, I dont mind trying again but so far I would like to preserve my bootloader as my phone still under warranty.
Click to expand...
Click to collapse
At this point my best guess is boot loader but who knows. Hopefully I can get more user feedback and i257m feedback most importantly. Thanks for your time
Sent from my Nexus 5 using Tapatalk
FYI, someone else tried it :
Originally Posted by pierrottls31 View Post
Hi, when you did test the rom from your link did you had same issues as I did? Wifi did not turn on, and when you go to Parameters-> Security i got a message saying security had to close. 5 secondes later the phone is rebooting.
I ve tried another rom 4.4.2 as a zip file and same issues. I revert it back to MF V11X and it works as normal.
I'm wondering if those issues are related to the bootloader (like for Param-Security) phone is looking for knox info and cannot find them.
reply:
Anyway for now my bootloader still in 4.2
I never checked wifi (I barely use wifi as is) System settings kept force closing on me and the ROM overall was a bit laggy (compared to MegaFire - probably not a fair comparison though - lol). My phone did keep rebooting every time I went into certain system settings to make changes (I don't remember which ones at this point). To be honest, I was just trying to see if I could flash it onto my phone. I had no intent to fully test the ROM for stability. Mega's ROMs are rock steady stable so I was just trying that 4.4.2 ROM while waiting for Mega to finish and post MegaKat.
see post from here:
http://forum.xda-developers.com/showthread.php?p=54072684 post #1994
Hi,
I just test the megakat rom from megafire, with the newbootloader and its all working. I can confirm wifi and setting issue were due to the bootloader
You should take a look at megakat op and rom, u will work with a almost bug free rom
Sent from my GT-I9205 using XDA Free mobile app
pierrottls31 said:
Hi,
I just test the megakat rom from megafire, with the newbootloader and its all working. I can confirm wifi and setting issue were due to the bootloader
You should take a look at megakat op and rom, u will work with a almost bug free rom
Sent from my GT-I9205 using XDA Free mobile app
Click to expand...
Click to collapse
you're missing the point of this thread! I'm not interested in another rom!!! I'm looking for sgh-i527m testers!!! i appreciate your efforts though
Okay i will give it whirl and see how the rom runs as i have the i527m mega (Canadian version).
Mega i527 bootloader is locked...no custom roms can go on it
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
scoobthegambler said:
Mega i527 bootloader is locked...no custom roms can go on it
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Read the op andthread title. I'm not looking for i527 testers:banghead::banghead::banghead:
Sent from my Nexus 5 using XDA Free mobile app
markbencze said:
Read the op andthread title. I'm not looking for i527 testers:banghead::banghead::banghead:
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
i527 boot loader is locked. Just because you put an M at the end doesn't automatically make it unlocked....pssh noobs. ?
edit>>> @scoobthegambler, you are right, I made a mistake, my apologies
@pierrottls31 it's very poor etiquette to post another devs rom in someone else's rom thread. Please help to keep development threads eleventh to the threads they pertain to
Thanks in advance
@GT247 I never posted or mention another developer's rom I merely stated that the i527 had a locked bootloader and the op restated that he was talking about i527m
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
just tried the rom, works fine except i got no wifi, my baseband is still NA3. Any way to get it updated to NE4 or NE5 ?
apen83 said:
i527 boot loader is locked. Just because you put an M at the end doesn't automatically make it unlocked....pssh noobs. ?
Click to expand...
Click to collapse
No it doesnt, but the M does have a recovery and is able to flash any of Sileshnair's roms.
It is not an ATT device.
GT......what are you doing here?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
No it doesnt, but the M does have a recovery and is able to flash any of Sileshnair's roms.
It is not an ATT device.
GT......what are you doing here?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
So if I put an M at the end of my Nexus5 can I flash Sileshnairs Roms?
@captemo, I'm watching my friend at work building roms, and hopefully keeping you out of trouble. Don't mess with Apen..lol
btw, I'm sure Mark Bencze will really appreciate if you'd stick around while he works this out.
---------- Post added at 10:53 PM ---------- Previous post was at 10:23 PM ----------
apen83 said:
So if I put an M at the end of my Nexus5 can I flash Sileshnairs Roms?
Click to expand...
Click to collapse
as the user you get to choose if adding that m does that
GT247 said:
edit>>> @scoobthegambler, you are right, I made a mistake, my apologies
@pierrottls31 it's very poor etiquette to post another devs rom in someone else's rom thread. Please help to keep development threads eleventh to the threads they pertain to
Thanks in advance
Click to expand...
Click to collapse
I did not mean too, I just wanted him to know you can go from more clean room to start than stock... Stock rom is buggy and all... I took the rom from megafire and tweak it my way, this way I dont have to re-correct all the bug.... but sorry if it was mis-understood... I did mention it for reference only.... cheers
This is the Q&A thread for the Squid Kernel for Moto E LTE. All device specific questions should go here.
Will this kernel work for the CDMA Boost Mobile XT1526? I noticed that you had uploaded a stock kernel for the Canadian XT1527 for recovery, but I don't want to brick my phone in case something goes wrong.
imprint89 said:
Will this kernel work for the CDMA Boost Mobile XT1526? I noticed that you had uploaded a stock kernel for the Canadian XT1527 for recovery, but I don't want to brick my phone in case something goes wrong.
Click to expand...
Click to collapse
Good question. I don't have a Boost mobile variant to test with, but it will probably work. I didn't see any special settings in the kernel for GSM vs CDMA variants. The Canadian XT1527 stock kernel will probably also work, though of course your bootloader needs to be unlocked to flash it. Just to be safe, I'd recommend making a Nandroid backup of both your system and boot partitions before flashing.
Does not read Sim on boost Mobile variant everything else seems OK .my camera is working again
bzo22 said:
Does not read Sim on boost Mobile variant everything else seems OK .my camera is working again
Click to expand...
Click to collapse
OK, thanks for letting me know. So if it fails to read the SIM, I guess cellular connectivity doesn't work? I'll look into settings for CDMA variant.
EDIT: I'm now suspecting there is a difference between the ramdisk images for the CDMA and GSM variants. I'll investigate the issue.
I have a copy of my boot.IMG if u need it
bzo22 said:
I have a copy of my boot.IMG if u need it
Click to expand...
Click to collapse
Thanks for the offer. I already have a boot.img for the Boost Mobile variant. As I guessed, the kernel is effectively the same, but the ramdisks differ. The Boost mobile version has a few extra parameters set, and contains lots of carrier crapware. I'll continue discussion of the differences on the main development thread.
Boost Mobile has a lot of carrier crapware. They have what's called MobileID which auto installs Boost's apps and what not. The apps it auto installs are Boost Zone, Boost 411, Boost Mobile Wallet, AirG, NBA game time, Scout GPS, pretty much anything that can be defined as bloatware. Im willing to help assist any of you on further testing or what not.
Also, I am wondering if anyone has successfully rooted and their camera still works. I've tried everything I could find on that, and it works for a while but ultimately I get the infamous "Camera Busy"
imprint89 said:
Boost Mobile has a lot of carrier crapware. They have what's called MobileID which auto installs Boost's apps and what not. The apps it auto installs are Boost Zone, Boost 411, Boost Mobile Wallet, AirG, NBA game time, Scout GPS, pretty much anything that can be defined as bloatware. Im willing to help assist any of you on further testing or what not.
Also, I am wondering if anyone has successfully rooted and their camera still works. I've tried everything I could find on that, and it works for a while but ultimately I get the infamous "Camera Busy"
Click to expand...
Click to collapse
Thanks for testing. When I have time (over the next few days), I'll make a CDMA variant of my kernel for yourself and others to try out. I'm trying to figure out what parts are needed and what can be stripped out of the ramdisk.
As for the rooted camera issue, while I've heard that it's due to SELinux, I've never experienced it myself, even on the stock kernel with SELinux enabled. Maybe it is specific to certain carrier variants. Just to be clear, you never had the camera issue appear on my kernel, right?
imprint89 said:
Boost Mobile has a lot of carrier crapware. They have what's called MobileID which auto installs Boost's apps and what not. The apps it auto installs are Boost Zone, Boost 411, Boost Mobile Wallet, AirG, NBA game time, Scout GPS, pretty much anything that can be defined as bloatware. Im willing to help assist any of you on further testing or what not.
Also, I am wondering if anyone has successfully rooted and their camera still works. I've tried everything I could find on that, and it works for a while but ultimately I get the infamous "Camera Busy"
Click to expand...
Click to collapse
I made a test kernel for the CDMA version. Try it out and let me know whether or not cellular connectivity works.
Squid,I just want to say thanks for being a dev on this phone. As far as your original kernel goes, I have not tested it. I would be more than willing to, if I could back up my existing kernel. I'm still kinda new to this, but I have made a nandroid backup in TWRP. Would that back up the kernel as well? I downloaded your CDMA version of the kernel, but I'm waiting to hear back from you (or anyone) on how to back up the kernel, or if I already did it via TWRP in making a backup.
imprint89 said:
Squid,I just want to say thanks for being a dev on this phone. As far as your original kernel goes, I have not tested it. I would be more than willing to, if I could back up my existing kernel. I'm still kinda new to this, but I have made a nandroid backup in TWRP. Would that back up the kernel as well? I downloaded your CDMA version of the kernel, but I'm waiting to hear back from you (or anyone) on how to back up the kernel, or if I already did it via TWRP in making a backup.
Click to expand...
Click to collapse
A Nandroid of the boot and system partitions should back up your kernel. With that said, could you do me a favour while still on the stock kernel? I want to make a TWRP flashable zip for the XT1526 stock kernel. I have the boot images, but I don't yet have the kernel modules to go with it. Could you run the following command, and send me the modules folder you get from it:
Code:
adb pull /system/lib/modules modules
Your help would be much appreciated.
squid2 said:
A Nandroid of the boot and system partitions should back up your kernel. With that said, could you do me a favour while still on the stock kernel? I want to make a TWRP flashable zip for the XT1526 stock kernel. I have the boot images, but I don't yet have the kernel modules to go with it. Could you run the following command, and send me the modules folder you get from it:
Code:
adb pull /system/lib/modules modules
Your help would be much appreciated.
Click to expand...
Click to collapse
Dang, lol. I just flashed the new kernel you made for the Boost variant... I can confirm it works and has mobile data, phone and text is all there. Camera works (as of now, to soon to see if it breaks). However, the new kernel is very slow to boot, and load apps. very noticeable. I'm not sure why, but from what I understand is that the kernel affects clock speed and voltages correct? Just reporting that to you. I will load my backup of my most recent nandroid and get that to you ASAP.
Here you go Squid. The stock kernel as requested.
imprint89 said:
Dang, lol. I just flashed the new kernel you made for the Boost variant... I can confirm it works and has mobile data, phone and text is all there. Camera works (as of now, to soon to see if it breaks). However, the new kernel is very slow to boot, and load apps. very noticeable. I'm not sure why, but from what I understand is that the kernel affects clock speed and voltages correct? Just reporting that to you. I will load my backup of my most recent nandroid and get that to you ASAP.
Click to expand...
Click to collapse
Glad to hear that CDMA works. Try rebooting and see if it gets better. I found that it boots slowly the first one or two times, then gets much faster.
squid2 said:
Glad to hear that CDMA works. Try rebooting and see if it gets better. I found that it boots slowly the first one or two times, then gets much faster.
Click to expand...
Click to collapse
Will do. Thanks again for helping out.
imprint89 said:
Here you go Squid. The stock kernel as requested.
Click to expand...
Click to collapse
Stock kernel for Boost Mobile is now up on the stock kernels thread.
squid2 said:
Stock kernel for Boost Mobile is now up on the stock kernels thread.
Click to expand...
Click to collapse
I've been using your custom kernel you made for Boost. The slow boot and app loading did go away after a few reboots. Everything works great, and still no camera bug! Further testing will prove the camera is fixed, but rooted and everything is great! We just need some ROM development for our phones.
Xt1524 4G LTE?
Nice work! Works on xt 4g lte 1524 ? (EU Orange versión)
ENRIQUEMM said:
Nice work! Works on xt 4g lte 1524 ? (EU Orange versión)
Click to expand...
Click to collapse
The GSM version of the kernel would probably work on the XT1524. I'd recommend making a Nandroid backup with the stock kernel before flashing.
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