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.
Related
My girlfriend asked me to turn off LTE to save battery and I remembered reading that you need a custom kernel to do that.
So, start from her stock ICS, how should I proceed?
The "Road and Ref Map" post seems to say that I should first flash CWM thru Odin then flash SU, is this the correct way to root now?
Then... which kernel shall I flash to be able to turn off LTE? Or do I actually need a custon ROM? I'm fine with flashing stuff since I've been playing with a Droid X for a year, but I'm not sure she'll agree to flash any ROM other than the stock...
Thank you very much!
kinnerful said:
My girlfriend asked me to turn off LTE to save battery and I remembered reading that you need a custom kernel to do that.
So, start from her stock ICS, how should I proceed?
The "Road and Ref Map" post seems to say that I should first flash CWM thru Odin then flash SU, is this the correct way to root now?
Then... which kernel shall I flash to be able to turn off LTE? Or do I actually need a custon ROM? I'm fine with flashing stuff since I've been playing with a Droid X for a year, but I'm not sure she'll agree to flash any ROM other than the stock...
Thank you very much!
Click to expand...
Click to collapse
You are on the right track. ..
Read read read! !!
The process is solid, but "your " knowledge is the key to a flawless root.
Take notes of the process and get your pc environment ready and then your good to go! !
Once rooted a custom rom is needed to control network...however it may be possible to toggle off the LTE function without root using a network code. ..unless you want root also. ...(i would )
Rooted custom roms are awesome. ...and i prefer the UCLF6 build from FlappJaxxx.
For code options, you'll need another user to help as i don't have them. ...and im not sure it will even work.
There are many great members here that are willing to help. ..
And i hope I've helped you today. ..g
:good:
The stock at&t modem is locked so users cannot mess with it. If you key *#2263# you will see.
The stock Rogers modem is not restricted. Using the dialer code it is theoretically possible to toggle 4g/3//2g. To me that means it could be possible to use one of the widgets in the market to toggle. But for some reason the phone slows to a crawl after flashing this modem.
Most of the roms in the development section don't have the toggle for 4g/3g/2g. I say most because there might be one that does but I've never seen anyone mention this feature.
I would like more input here because this could give better battery performance.
Thank you all for the info! Maybe I'll just root and install some sort of stock rooted ROMs instead.
The battery life got dramatically worse after the ICS OTA: it could last a day without problem before, but now it died in the middle of her working day. I tried Better Battery Stat and found that AlarmManager kept the phone awake almost all the time, which to my knowledge didn't point to any specific problem.
Could battery life be better just by installing a debloated stock rooted ROM?
Try flashing the Canadian ROM with the Canadian radio together. It is unbranded and will look almost exactly like the ATT ROM. I have been using the complete package together (my version, not sam's version) and have experienced no slowdown experiences. I am on ATT however my phone is a Rogers Note and not an ATT note. Some users have reported a slowdown issue with the ATT I717 and a Canadian modem.
http://forum.xda-developers.com/showthread.php?t=1801689
What ^^^^^^^^^ said ....g
Under stock gingerbread I was able to turn off/on LTE with the menu when code *#*#4636#*#* was dialed, but under ICS, that no longer works
rangercaptain said:
The stock at&t modem is locked so users cannot mess with it. If you key *#2263# you will see.
The stock Rogers modem is not restricted. Using the dialer code it is theoretically possible to toggle 4g/3//2g. To me that means it could be possible to use one of the widgets in the market to toggle. But for some reason the phone slows to a crawl after flashing this modem.
Most of the roms in the development section don't have the toggle for 4g/3g/2g. I say most because there might be one that does but I've never seen anyone mention this feature.
I would like more input here because this could give better battery performance.
Click to expand...
Click to collapse
I am going to try Agoattamer's suggestion. I will post the steps and links if it does what we want.
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??
I was wondering if there was a way to flash AT&T ROM to work on the verizon model. I know how to flash international Roms but not AT&T.
For example, currently I am running Echoe 32.1 (International version), but when I try to flash Goldenfinger (AT&T) my phone calls work but I get no SMS or data.
Any help is appreciated!
Thanks!
Someone with ROM building (from source or porting) experience can better explain this, but the simplest answer is that because the frequencies that AT&T and T-Mobile operate on differ from those of Verizon and Sprint (typically). So the ROM you are trying to use has different radio drivers for frequencies your phone doesn't use, which results in most or all your antennas to not function. I know that at the very least you need to modify the ROM to utilize the Verizon radios. There may also be some system configurations to be altered in the install of the ROM so it's instructed to use the right frequencies, though a more qualified individual will need to verify that.
Hope that gives you a general idea.
http://forum.xda-developers.com/showthread.php?t=2674280
This patch can be used to flash roms from international and other carriers. It has an aroma installer allowing to decide how much Verizon stuff you want to install, anywhere from just the APN's to the full phone & messaging apk's. Read the OP and thread to understand which patch to use and how to use it.
joshm.1219 said:
http://forum.xda-developers.com/showthread.php?t=2674280
This patch can be used to flash roms from international and other carriers. It has an aroma installer allowing to decide how much Verizon stuff you want to install, anywhere from just the APN's to the full phone & messaging apk's. Read the OP and thread to understand which patch to use and how to use it.
Click to expand...
Click to collapse
Thank you for the help! But I tried the patch you suggested on two different AT&T ROMs, and I didn't have any luck. It works on international version ROMs, but not AT&T..
And I just realized I forgot to put in the OP that im on Safestrap
luke24 said:
Thank you for the help! But I tried the patch you suggested on two different AT&T ROMs, and I didn't have any luck. It works on international version ROMs, but not AT&T..
And I just realized I forgot to put in the OP that im on Safestrap
Click to expand...
Click to collapse
Yeah, unfortunately things have been weird with that patch lately. It's a mix of the dev not having time to update while everything has been getting significant updates pretty quickly and lost user interest overall. I've used that patch with AT&T roms before, but admittedly not since Jelly Bean. It should theoretically work still, but there's other variables you have to consider. All I can say is that if you're really interested in running one of those roms, read through the patch thread to see what particular aroma settings and additional zips, etc. people are using to get those roms to boot.
And Safestrap users can use that patch too. I would PM @shindiggity for assistance. He seems like a helpful guy and he uses that patch on Safestrap.
joshm.1219 said:
Yeah, unfortunately things have been weird with that patch lately. It's a mix of the dev not having time to update while everything has been getting significant updates pretty quickly and lost user interest overall. I've used that patch with AT&T roms before, but admittedly not since Jelly Bean. It should theoretically work still, but there's other variables you have to consider. All I can say is that if you're really interested in running one of those roms, read through the patch thread to see what particular aroma settings and additional zips, etc. people are using to get those roms to boot.
And Safestrap users can use that patch too. I would PM @shindiggity for assistance. He seems like a helpful guy and he uses that patch on Safestrap.
Click to expand...
Click to collapse
Thank you for all your help! Im gonna PM him and read through the thread and if and when I find a solution, I will post it here.
I've flashed Goldfinger and it does work. These are the steps that I do. Flash rom, patch,signal bar fix, modules and finally SU. In the patch I select minimal and everything else I leave pre selected. First boot does take a couple minutes. Let me know if that works.
http://www.androidfilehost.com/?fid=23501681358559252
http://www.androidfilehost.com/?fid=23578570567713275
I have an unlocked moto e LTE that I just finished rooting. My goal is to enable band 12 again, but I'm unclear how to move forward.
What is the easiest path to reenabling band 12 for better T-Mobile LTE coverage?
Will simply installing CM13 or some other custom rom do it?
Thanks
For the XT1527, Band 12 was only active on the launch firmware, and was disabled in the first update. People have tried flashing the launch radio on later updates, but it didn't enable Band 12, so there's something else besides the radio needed to make Band 12 work.
Filename: SURNIA_RETUS_5.0.2_LXI22.50-24.1_cid9_subsidy-DEFAULT_CFC.xml.zip
Does that mean I just need to downgrade back to 5.0 or whatever the initial firmware that supported band 12 was? Is there a guide or has this not been achieved yet?
ctenc001 said:
Does that mean I just need to downgrade back to 5.0 or whatever the initial firmware that supported band 12 was? Is there a guide or has this not been achieved yet?
Click to expand...
Click to collapse
The original baseband from 5.02 is needed, but I wouldn't recommend the stock 5.02 ROM. Later versions disable band 12 in both the baseband and the ROM. The 5.02 baseband + CM12.1 seems to be the most stable.
spiked_mistborn said:
The original baseband from 5.02 is needed, but I wouldn't recommend the stock 5.02 ROM. Later versions disable band 12 in both the baseband and the ROM. The 5.02 baseband + CM12.1 seems to be the most stable.
Click to expand...
Click to collapse
What files need to be flashed to downgrade the baseband? Just NON-HLOS.bin and fsg.mbn? Or is there something more?
xtermmin said:
What files need to be flashed to downgrade the baseband? Just NON-HLOS.bin and fsg.mbn? Or is there something more?
Click to expand...
Click to collapse
That's all. Just make sure to download a copy of the current ROM that you're running in case you want to go back to your current baseband. Check this post here for instructions http://forum.xda-developers.com/showpost.php?p=64871207&postcount=3
From what I understand, a full copy of 5.01 is not available? And that is the only version that included band 12 support, correct? So does that mean there is no way to downgrade? If it is possible, could you give some direction as to where that ROM / baseband files are located?
ctenc001 said:
From what I understand, a full copy of 5.01 is not available? And that is the only version that included band 12 support, correct? So does that mean there is no way to downgrade? If it is possible, could you give some direction as to where that ROM / baseband files are located?
Click to expand...
Click to collapse
The Moto E2 never had 5.01. It launched with 5.0.2. I provided the full filename of the file you should grab in Post #2. The full firmwares are in the firmware topic here: http://forum.xda-developers.com/moto-e-2015/general/stocks-firmwares-moto-e-t3113235
I believe that firmware version is in one of the Mega folders.
spiked_mistborn said:
The original baseband from 5.02 is needed, but I wouldn't recommend the stock 5.02 ROM. Later versions disable band 12 in both the baseband and the ROM. The 5.02 baseband + CM12.1 seems to be the most stable.
Click to expand...
Click to collapse
Does that mean that that this wouldn't work?
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
I wanted to try out cm13 and it doesn't look like it will work with the 5.02 baseband. I want to move that way since I want to use the sd card internal storage feature for data.
Thanks
seringen said:
Does that mean that that this wouldn't work?
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
I wanted to try out cm13 and it doesn't look like it will work with the 5.02 baseband. I want to move that way since I want to use the sd card internal storage feature for data.
Thanks
Click to expand...
Click to collapse
It's possible that band12 might be able to be turned back on using that method, but I haven't been willing to try it myself. It seems like there is a much higher risk of bricking your device than just your standard ROM and kernel flashing, but that's just my opinion. It's not a risk I'm willing to take at this point since this phone is my daily driver.
I can say that I'm currently running the 5.02 baseband with squid2's CM13 0321 build and the r16 kernel and it's been working well. I've only had a single random reboot so far, and ironically it was when I was on xda reading about the baseband requirements for CM13. Battery life has been excellent even when just leaving wifi on, so I've started doing that and it's worked well so far for avoiding the wifi toggle reboot issue. I'm willing to deal with that to have band12 working for now. SD card Internal storage works well also. The only issue I've had is that Titanium backup doesn't see apps that are moved to the SD card, so any apps that I want to freeze have to be left on internal storage.
Good luck if you decide to try the baseband modification, let us know how it goes.
spiked_mistborn said:
The original baseband from 5.02 is needed, but I wouldn't recommend the stock 5.02 ROM. Later versions disable band 12 in both the baseband and the ROM. The 5.02 baseband + CM12.1 seems to be the most stable.
Click to expand...
Click to collapse
spiked_mistborn said:
It's possible that band12 might be able to be turned back on using that method, but I haven't been willing to try it myself. It seems like there is a much higher risk of bricking your device than just your standard ROM and kernel flashing, but that's just my opinion. It's not a risk I'm willing to take at this point since this phone is my daily driver.
I can say that I'm currently running the 5.02 baseband with squid2's CM13 0321 build and the r16 kernel and it's been working well. I've only had a single random reboot so far, and ironically it was when I was on xda reading about the baseband requirements for CM13. Battery life has been excellent even when just leaving wifi on, so I've started doing that and it's worked well so far for avoiding the wifi toggle reboot issue. I'm willing to deal with that to have band12 working for now. SD card Internal storage works well also. The only issue I've had is that Titanium backup doesn't see apps that are moved to the SD card, so any apps that I want to freeze have to be left on internal storage.
Good luck if you decide to try the baseband modification, let us know how it goes.
Click to expand...
Click to collapse
If there was a way of doing it without Windows, I would try it, mainly since I'm only interested in adding the one band and the hardware was designed for it. If someone could do it where I could then flash the file, I would give it a go and report back.
seringen said:
If there was a way of doing it without Windows, I would try it, mainly since I'm only interested in adding the one band and the hardware was designed for it. If someone could do it where I could then flash the file, I would give it a go and report back.
Click to expand...
Click to collapse
You could always try it in a Windows VM. MS actually has some ready to go on their dev site here https://dev.windows.com/en-us/microsoft-edge/tools/vms/
Just use import appliance in VirtualBox, give it a couple gigs of ram, and then you should be able to select which usb devices you pass to the VM.
spiked_mistborn said:
You could always try it in a Windows VM. MS actually has some ready to go on their dev site here
Just use import appliance in VirtualBox, give it a couple gigs of ram, and then you should be able to select which usb devices you pass to the VM.
Click to expand...
Click to collapse
OK I'll try it this weekend. Last time I tried something similar I couldn't get adb to work but hopefully this will.
I flashed the 5.1 baseband and decided to give this a try, but I can't figure out how to enable the diag mode in cm13. It looks like it might be possible from the stock rom, but I'm using adopted storage and I don't really feel like going through the hassle that it would entail to go from cm13, to stock, and back again without losing everything.
If anybody knows how to enable usb diag mode in cm13 please let me know.
I started a new thread in general http://forum.xda-developers.com/moto-e-2015/general/guide-enable-lte-bands-surnia-t3351673
Hope this gets things started,
DETAILS
Stock Korean firmware base AQF5
Rooted
Init d
Deodex
Zip aligned
Busybox
Sqlite
Thanks to
Chainfire for supersu
Ashyx for custom twrp and rooting process
Samsung for the base
Take all care back up, beyond that, your responsibility
Link :-
Android file host
https://www.androidfilehost.com/?fid=889764386195921470
Hit thanks or buy me a coffee if you wish
https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
Leave some posts so I know it works OK, I'm new to this
It would be good if someone could post if this rom was ok, as have a T825 rom built with the same method that I cannot test, due to having a T820 myself. So speak up please
Thank you for this. Now I have to ask a couple of newbie questions. I've been exclusively in the Sony Xperia and Nexus worlds before, this being my first Samsung. In trying to figure out if the processes I've become familiar with are applicable to this device, using your ROM.
For instance, my Sony's were pretty easy after the initial root. Kind souls in the community took new releases and created a pre-rooted firmware with TWRP and SuperSU built-in. I could then just dirty flash the ROM from TWRP, sometimes wiping cache/dalvic, and like magic my device is upgraded with no loss of data.
Is this how it works with this AQF5 ROM? I'm starting with a rooted (@ashyx method) T820 with AQBB. Do I just download the rooted ROM to SD card, boot to TWRP, dirty flash and go?
Thanks again!
Hi,
Dirty flash should work, sometimes I try that first and if I get any strange behaviour, do a wipe and re flash then load the rest back with titanium backup. Make sure you have all your backups organised first before starting.
Let me know how it works out. The risk with the first option is something residual being left that may result in force closes or just defeating the purpose.
Just beware if for some reason it doesn't root DM verity will occur and you will be forced to format internal data so back that up to your external card too, before, just in case, shouldn't happen though. I have no idea how many others have used this yet as there have been no replies to say all ok
rorymc928 said:
Just beware if for some reason it doesn't root DM verity will occur and you will be forced to format internal data so back that up to your external card too, before, just in case, shouldn't happen though. I have no idea how many others have used this yet as there have been no replies to say all ok
Click to expand...
Click to collapse
Not sure I can use this ROM in Germany, what kind of modifications are made? Would love to see some development
As long as you have the same model T-820 you can, some local variants have a local customisation but it's likely to be minor with this model. From memory when I set it up on mine all common languages were available, if that's your concern, make sure you have a twrp backup and you can always roll back
The only mods were as listed above, seems slightly quicker, perhaps the zip aligning, but it will allow more mods as they come along
Will flashing this trip the knox counter?
DarkXoa said:
Will flashing this trip the knox counter?
Click to expand...
Click to collapse
Always, Knox is there to tell Samsung if you've done this sort of thing, it's just what you accept with custom roms
rorymc928 said:
Always, Knox is there to tell Samsung if you've done this sort of thing, it's just what you accept with custom roms
Click to expand...
Click to collapse
I bought you a beer, but didn't find time to try it out
vonschau said:
I bought you a beer, but didn't find time to try it out
Click to expand...
Click to collapse
Thank you very much, most appreciated, let me know how it goes
Any development on tab S3 ROMs???
rorymc928 said:
As long as you have the same model T-820 you can, some local variants have a local customisation but it's likely to be minor with this model. From memory when I set it up on mine all common languages were available, if that's your concern, make sure you have a twrp backup and you can always roll back
The only mods were as listed above, seems slightly quicker, perhaps the zip aligning, but it will allow more mods as they come along
Click to expand...
Click to collapse
I have always wondered about that. Flashing a base from another country. Like I live in the US so I always have flashed USA versions. You are
saying that I CAN flash this Korean version on my T-820 phone and have all working ok with English ?
Thank you
Thibor69 said:
I have always wondered about that. Flashing a base from another country. Like I live in the US so I always have flashed USA versions. You are
saying that I CAN flash this Korean version on my T-820 phone and have all working ok with English ?
Thank you
Click to expand...
Click to collapse
For the record, I don't live in the us but bought mine from best buys whilst there, it was rooted within a couple of hours from memory,..... can't help myself ?.
I Flashed a firmware from another country after that,, just because it was a later series, can't remember which.
I use the Tweaked one as my daily driver, people seem to be finding that good. I have found the latest firmware now seems to carry out a full wipe, and I haven't managed to flash a rom over it yet, so reverted back to the Tweaked version I have.
It may require an update to TWRP
If you have any problems restore your backup, if you want to persist flash the firmware that its based on first,AQF5, then flash the ROM over it, with our without wipe.
Link to Tweaked,
https://forum.xda-developers.com/galaxy-tab-s3/development/rom-sm-t820-tweaked-t3659433
rorymc928 said:
For the record, I don't live in the us but bought mine from best buys whilst there, it was rooted within a couple of hours from memory,..... can't help myself [emoji20].
I Flashed a firmware from another country after that,, just because it was a later series, can't remember which.
I use the Tweaked one as my daily driver, people seem to be finding that good. I have found the latest firmware now seems to carry out a full wipe, and I haven't managed to flash a rom over it yet, so reverted back to the Tweaked version I have.
It may require an update to TWRP
If you have any problems restore your backup, if you want to persist flash the firmware that its based on first,AQF5, then flash the ROM over it, with our without wipe.
Link to Tweaked,
https://forum.xda-developers.com/galaxy-tab-s3/development/rom-sm-t820-tweaked-t3659433
Click to expand...
Click to collapse
It will still work in English you just have to find which is your main language in the very beginning
Sent from my [device_name] using XDA-Developers Legacy app
Works great on T820, no issues so far...
kbroh said:
Works great on T820, no issues so far...
Click to expand...
Click to collapse
Thanks,
This rom is not being developed any more,but the tweaked version in this forum, is based off the stock firmware which came after this,it runs stable, has a few enhancements and being a later base it's got a number of Samsung security updates too.
Would this thread be applicable to a Wi-Fi only S3 model "SM-T820NZKAXAR" ?
Zoandroid said:
Would this thread be applicable to a Wi-Fi only S3 model "SM-T820NZKAXAR" ?
Click to expand...
Click to collapse
Sure is. That's what I got.
DarkXoa said:
Will flashing this trip the knox counter?
Click to expand...
Click to collapse
After 10 years of the same answer its still YES...rooting always trips..