So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.
You are right about everything you've mentioned. Good research done for sure! ?
Do a backup with twrp. And yes, you can restore it and flash the stock recovery and you're good for the OTA.
Aosp/cm roms don't have the Moto features. But yes, you can return to stock and have them again. There's a few stick based custom roms that of course still have the features. The other roms, unless something changed, do come with some bugs unfortunately as well.
Most use stock, with gravity box for customizing.
And in case you missed it.... Never try to downgrade from 4.4.4....or you risk your device bricking. You can flash lower version custom roms, cause they won't try to change the bootloader. But don't downgrade stock firmware. Ever. ?
Enjoy!
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
Until there's a 4.4.4 SBF, yes. That's the safest bet.
newbie needs details
no_un_bot said:
So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.
Click to expand...
Click to collapse
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble
sherif2015 said:
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble
Click to expand...
Click to collapse
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.
no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
SBF.Droid-Developers.org hasn't been updated in a while, at least as far as the X (2013 or 1st Gen edition) Roms.
Another possible source is -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 however, they don't have a 4.4.4 SBF for the XT1053 either.
And you can keep an eye on https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images since Moto should post the 4.4.4 SBF for the Developer Editions. Eventually an XT1053 (GSM) and an XT1060(VZW) 4.4.4 should pop up there, whenever Moto finally gets around to it.
no_un_bot said:
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.
Click to expand...
Click to collapse
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time
sherif2015 said:
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time
Click to expand...
Click to collapse
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone
reply
no_un_bot said:
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone
Click to expand...
Click to collapse
Kitkat 4.4.2 xt1053
same phone, problems loading roms
I have the same phone, I also recently got second hand.
Moto x xt1053 (gsm) carrier unlocked, currently in kitkat4.4.2, running Kangakat 2 rom (came with it), unlocked bootloader, rooted and using SuperSU, newest version of twrp like 2.8 or something like that.
I want to load a custom rom but am having problems, downloaded P.A.C. and AOKP (two i have tried to use) for the device msm8960 using there stable versions not the nightlies. Went into twrp, created backup, factory wiped, flashed rom and g-apps, was "successful" no errors but on reboot of phone it gets stuck in boot loop and won't start up. for the P.A.C i was able to get into twrp and reflash my back up, for the AOKP twrp kept getting stuck on that teamwin image and i could only finally access it by having the usb cable plugged into my computer. I am not a noob, but definately not an expert.
So did you have any luck flashing a new rom to your phone? Does anyone have any advice for me? I really would like to try some different roms.
Thanks
[emoji15]
I hate Tapatalk for all the time spent writing a quick reply and its gone.
Anyways, first of all, make sure you have the latest recovery available, I remember back with my old phone, funky installations happened if you weren't on the latest recovery. I recommend philz one, has support for some pesky partitions that sometimes get messed and other recoveries won't back up.
Now, in my particular case, I first upgraded my 4.4.2 Nextel stock to 4.4.3 T-Mobile stock using RSDLite, then took the OTA to 4.4.4, and until then I figured I'd play with ROMs. Have had no issues other than something I've addressed on another thread and I ultimately fixed.
My suggestion is going back to full stock then doing everything yourself so you know what's actually going on.
You'll have to flash a custom recovery and then root it again but with an unlocked bootloader that's ezpz.
Remember never to downgrade (that is, flashing a lower android version than what you currently run) stock official images (such as the ones from sbf-developers) because you WILL brick your phone. People say you can downgrade when flashing custom ROMs but I wouldn't risk it, and I don't really see why I'd want that.
Double check whatever file you'll try to flash, always use stuff intended for your model, and when that's not possible verify if other users with your model have reported it works for them. As per the version thing, I believe the most recent development unified models under the GHOST parameter but take my words for what they are, that is, my view on things, you should always make one for yourself.
Ask if you don't completely understand a step BEFORE doing it, there's good people willing to help you out.
Best of luck.
Related
I'm not too worried about undoing the rooting (unless there's an easy way) but how to I get back to Android 2.1 like I had when I first got the phone? Can I just install the stock ROM and where do I find it?
Thanks
kbeeveer46 said:
I'm not too worried about undoing the rooting (unless there's an easy way) but how to I get back to Android 2.1 like I had when I first got the phone?
Thanks
Click to expand...
Click to collapse
Why would you want an unlocked bootloader with the OTA stock ROM? There is no way to relock the bootloader and regain your warranty.
CM is Android 2.1, just a better, faster version.
If you are concerned about OTA updates, the features are generally included in Cyanogen's ROM immediately upon release, but usually far before any OTA release.
No big reason why I want to right now but I like knowing there's a way to get back to stock in case something goes horribly wrong and I mess something up (and for the same reasons some of us reformat our computers often). I don't even notice a huge difference (speed and battery) running CM. I haven't installed many apps or themes though.
kbeeveer46 said:
No big reason why I want to right now but I like knowing there's a way to get back to stock in case something goes horribly wrong and I mess something up (and for the same reasons some of us reformat our computers often). I don't even notice a huge difference (speed and battery) running CM. I haven't installed many apps or themes though.
Click to expand...
Click to collapse
you cant go back to stock...you will never have a locked bootloader again...yet
xsnipuhx said:
you cant go back to stock...you will never have a locked bootloader again...yet
Click to expand...
Click to collapse
That's different than the stock rom, right? Is it possible to be unlocked and run the default rom that comes with the phone? Or is that combination not a possibility?
Sure you can do that, but I guess I just don't understand why...
You can always go back to stock everything except your bootloader will remain unlocked (unless someone finds a workaround or hack)
Anything you can screw up (except a bad radio flash) can be fixed by having an up to date Nandroid backup...
Just do what I do and make sure to Nandroid every other day or so. (Or before every time you change anything in the system/framework/boot/kernel etc.)
forum.xda-developers.com/showthread.php?t=619801
i think you can get the stock rom from here if you didnt do a nandroid backup
If i were going to sell the nexus one some time in the future, it would be good to know where the stock rom can be found. Some people don't want to be flashing ROMs all the time, and would prefer OTA updates. Once the phone is over a year old, the unlocked bootloader will be meaningless.
Simple, in the android development section at the top of the list as a sticky, [ROM] 22/Mar ERD79 -> EPE76 - Stock Nexus One images / zip / online kitchen / rooted, or heres the link, http://forum.xda-developers.com/showthread.php?t=619801, it gives you the stock rom. happy flashing
ernvillanueva90 said:
Simple, in the android development section at the top of the list as a sticky, [ROM] 22/Mar ERD79 -> EPE76 - Stock Nexus One images / zip / online kitchen / rooted, or heres the link, http://forum.xda-developers.com/showthread.php?t=619801, it gives you the stock rom. happy flashing
Click to expand...
Click to collapse
The download links in that thread don't seem to work any longer. It just redirects me to the homepage. I probably need an account or something. Blarg.
EDIT: Still don't work even with an account.
kbeeveer46 said:
The download links in that thread don't seem to work any longer. It just redirects me to the homepage. I probably need an account or something. Blarg.
EDIT: Still don't work even with an account.
Click to expand...
Click to collapse
That site uses an anti bandwidth stealing feature, just right click the link and save as.
Ok guys, i figured i've refrained from customizing my phone long enough.
I'm well aware of how to flash things onto the phone. I am currently running 4.2.2 on my C6606.
I have dualboot recovery flashed onto it, phone is rooted, and the only mod i have is pure audio.
I know i have to unlock my bootloader to be able to flash roms that require a custom kernel.
My question is, is there anything i should lookout for before flashing onto my phone?
I just want to know if these roms will also work on the t-mobile network. Haven't seen too much activity from C6606 users on here, so i'm a bit curious on that.
I don't believe you can unlock the bootloader on a C6606. If you could, you would need to back up your AT? partition; the one that has all your DRM keys and stuff. But you can still flash custom roms that are made for locked bootloaders, with stock kernels... I have flashed the stock roms from other regions and never had a problem with my C6606 working on the T-Mobile network.
Good luck!
i flashed NUT's 4.3 rom from 4.2 and running that, we have a locked bootloader which means we cant use a custom kernel. sony's ramdisk layout is bit different then im used to, im used to standard boot.img format on many devices. anyways the dual recovery script allows for booting custom ramdisks, if i can get a cm one setup and going then we could have cm booting on locked bootloaders. this is no easy task and something i have never done before, not to mention there may be issues that isnt there with a custom kernel.
shabbypenguin said:
i flashed NUT's 4.3 rom from 4.2 and running that, we have a locked bootloader which means we cant use a custom kernel. sony's ramdisk layout is bit different then im used to, im used to standard boot.img format on many devices. anyways the dual recovery script allows for booting custom ramdisks, if i can get a cm one setup and going then we could have cm booting on locked bootloaders. this is no easy task and something i have never done before, not to mention there may be issues that isnt there with a custom kernel.
Click to expand...
Click to collapse
Being able to get CM on the Z without unlocking the bootloader would be awesome.
iDroid8 said:
Being able to get CM on the Z without unlocking the bootloader would be awesome.
Click to expand...
Click to collapse
well i dont want peopel to get their hopes up about myself, its no easy feat and i applied for motorola financing last week, as i might end up going with a moto x. the bill with tmobile is a bit more than expected and going with a moto x would mean unlocked bootloader as well as lower monthly payments. you guys have some very talent people working on this device, it may end up happening on the z1 first and then get backported.
shabbypenguin said:
well i dont want peopel to get their hopes up about myself, its no easy feat and i applied for motorola financing last week, as i might end up going with a moto x. the bill with tmobile is a bit more than expected and going with a moto x would mean unlocked bootloader as well as lower monthly payments. you guys have some very talent people working on this device, it may end up happening on the z1 first and then get backported.
Click to expand...
Click to collapse
I'm just finding the process quite confusing. I haven't found any good videos detailing the entire process for a retard (myself).
iDroid8 said:
I'm just finding the process quite confusing. I haven't found any good videos detailing the entire process for a retard (myself).
Click to expand...
Click to collapse
videos on what?
shabbypenguin said:
videos on what?
Click to expand...
Click to collapse
Of flashing CM11. Most people aren't helpful and say if I can't unlock a bootloader then I shouldn't flash ROM's.
iDroid8 said:
Of flashing CM11.
Click to expand...
Click to collapse
its not possible with a locked bootloader at this time.
sbackus said:
I don't believe you can unlock the bootloader on a C6606. If you could, you would need to back up your AT? partition; the one that has all your DRM keys and stuff. But you can still flash custom roms that are made for locked bootloaders, with stock kernels... I have flashed the stock roms from other regions and never had a problem with my C6606 working on the T-Mobile network.
Good luck!
Click to expand...
Click to collapse
shabbypenguin said:
i flashed NUT's 4.3 rom from 4.2 and running that, we have a locked bootloader which means we cant use a custom kernel. sony's ramdisk layout is bit different then im used to, im used to standard boot.img format on many devices. anyways the dual recovery script allows for booting custom ramdisks, if i can get a cm one setup and going then we could have cm booting on locked bootloaders. this is no easy task and something i have never done before, not to mention there may be issues that isnt there with a custom kernel.
Click to expand...
Click to collapse
So say i tried to flash XperiaBlueLights, its a 4.2.2 rom, and it says its for a locked bootloader, it should work fine right?
Or the CriskeloRom, its 4.3 but it says it works on both locked and unlocked bootloaders. There shouldn't be an issue installing this on a C6606 should there?
Don't mean to ask so many questions, im usually the type to go and find out myself, but so far customizing my first sony phone isn't as fun, or easy as my past phones.
xDC23 said:
So say i tried to flash XperiaBlueLights, its a 4.2.2 rom, and it says its for a locked bootloader, it should work fine right?
Or the CriskeloRom, its 4.3 but it says it works on both locked and unlocked bootloaders. There shouldn't be an issue installing this on a C6606 should there?
Don't mean to ask so many questions, im usually the type to go and find out myself, but so far customizing my first sony phone isn't as fun, or easy as my past phones.
Click to expand...
Click to collapse
I think you would need to flash the C6606 kernel to be able to boot. I have written a C6606 tutorial for MIUI if you are interested in the Chinese version of Android. It is in the first post.
http://forum.xda-developers.com/showthread.php?p=46120012
C6606 user here. Currently running @niaboc79 4.3 Black Edition, and couldn't be happier.
I got my Z shortly after it became available, and have had a custom stock based ROM on it since day 1. I will admit there was a slight learning curve, but I knew I was switching to T-mobile and started reading up on the whole rooting/flashtool before I purchased and have stayed out of trouble (for the most part). Once you flash a ROM or two you will get the gist of it and it will become less confusing. The beauty of it is that we don't have to wait for T-Mobile to push out new Android versions. Once the Z gets it, so can we and no T-Mobile bloat. You will not have wifi calling if you haven't figured that out already.
Look for the "LB" (lockedbootloader) tag in the ROM title, and they should be good to go for us C6606 users.
Just follow the OP's instructions for installing and you will be fine. I haven't touched anything directly related to the C6606, other than APN's. I haven't had any luck doing the "download settings for internet and MMS" under wireless & networks settings.
I use these APN's every time I do a clean install and all network modes (3G, 4G, LTE) work just fine - http://forum.xda-developers.com/showthread.php?t=2236735
xDC23 said:
Ok guys, i figured i've refrained from customizing my phone long enough.
I'm well aware of how to flash things onto the phone. I am currently running 4.2.2 on my C6606.
I have dualboot recovery flashed onto it, phone is rooted, and the only mod i have is pure audio.
I know i have to unlock my bootloader to be able to flash roms that require a custom kernel.
My question is, is there anything i should lookout for before flashing onto my phone?
I just want to know if these roms will also work on the t-mobile network. Haven't seen too much activity from C6606 users on here, so i'm a bit curious on that.
Click to expand...
Click to collapse
yeah made sure you back your entire phone completely up! that way if something happens you can always go bck to the orginal state!
So... I have looked around and can't find a specific resource that tells me what I need to do, so I am posting this. If there is an existing thread or post you could point me to that would be appreciated. I unlocked my Moto X bootloader (US Cellular), rooted, and flash a new ROM a few weeks back. I love the custom ROM's but have gotten tired of random bugs and lack of the stock Moto X features (which I came to love over the year I had the phone before ever rooting it).
In any case, I need to know how I can go about getting the stock MotoX experience back and keep root.
ASK in Q&A section not in original Android developement!
Flash a stock based rom
Always start with the stickies in device sections, they usually have most things like this,
See this guide and check the returning to stock section...
http://forum.xda-developers.com/showthread.php?t=2603358
You will need to root again, but your bootloader is unlocked, so that's simple.
And don't downgrade your android version if you value your device. Same version or higher only. ?
i.Design said:
So... I have looked around and can't find a specific resource that tells me what I need to do, so I am posting this. If there is an existing thread or post you could point me to that would be appreciated. I unlocked my Moto X bootloader (US Cellular), rooted, and flash a new ROM a few weeks back. I love the custom ROM's but have gotten tired of random bugs and lack of the stock Moto X features (which I came to love over the year I had the phone before ever rooting it).
In any case, I need to know how I can go about getting the stock MotoX experience back and keep root.
Click to expand...
Click to collapse
For future reference, make a nandroid of your stock phone before you flash a custom ROM. Then you can just restore to stock using the nandroid and keep root.
However, if you want your texts messages from your phone restored, it is more complicated and right now I am having issues trying to restore text messages from an older version of android.
The app "sms backup and restore" has never failed to restore messages for me. ?
But that's off topic here. ?
KJ said:
The app "sms backup and restore" has never failed to restore messages for me.
But that's off topic here.
Click to expand...
Click to collapse
Thanks, does it do MMS too? I read MMS restore was in beta.
I don't know, it claims it does...but I can't say I've noticed.
Deleted, figured out my problem. Thanks all!
Oh boy I really hope I am just too tired to look and info I've got so far is incorrect. My i337 Got stolen today and I managed to get Galaxy S 4 Active from ATT i537. I looked up only 1 thing before I did because only system I can use is CM11, I mean stock Samsung makes me uneasy if I am on it for more then 15 seconds. Sounds, UI, just feel and look, totally garbage. So now I see that bootloader is locked AND there is no solution to unlock it. Only then we can install some kind of Dual boot thing ? I really hope this is not true. Can I just get rid of everything Samsung and stock and get CM11 ? I don't want to waste space with stock as "not used" system.
Please let me know because like I said I had really bad day with two thugs stealing my phone, spend money on new one and now this. I just rooted it and was thinking like always I get Rom Manager and from there I install recovery ..... but phone is not listed .... I am freaking out a bit right about now. Please let me know if possible on where to start getting custom recovery cause ODIN + tar recovery files gave me magic error or something like that just now.
Thank you guys !
UPDATE: Couldn't sleep.
So I have my new phone rooted with "towel", I install Safestrap and backed up my current ROM (I am on NE3) I see now reason why this dual system needed and stuff. I mean too bad Samsung locking bootloaders and oh well. I have only 2 questions. 1 can I just install latest build from https://download.cyanogenmod.org/?device=jactivelte in to rom SLOT-1 and use it or no. And how much space I can allow for my current ROM and CM I mean I am not planning to have anything on stock so I don't need space at same time I cant make it that when I do want to go on stock I'd have a problem with running it because of not enough space.
Thank you guys once again. I mean If you know few lines ..that's all I am asking. Cause I do see some pros and cons but .. I need straight up answer. Thanks !
Your frustration is understand. Swearing or bad language is not excused in this forum for any reason. Moderate at least title or be prepared to get warning and/or thread locked down.
russiandivxclub said:
Oh boy I really hope I am just too tired to look and info I've got so far is incorrect. My i337 Got stolen today and I managed to get Galaxy S 4 Active from ATT i537. I looked up only 1 thing before I did because only system I can use is CM11, I mean stock Samsung makes me uneasy if I am on it for more then 15 seconds. Sounds, UI, just feel and look, totally garbage. So now I see that bootloader is locked AND there is no solution to unlock it. Only then we can install some kind of Dual boot thing ? I really hope this is not true. Can I just get rid of everything Samsung and stock and get CM11 ? I don't want to waste space with stock as "not used" system.
Please let me know because like I said I had really bad day with two thugs stealing my phone, spend money on new one and now this. I just rooted it and was thinking like always I get Rom Manager and from there I install recovery ..... but phone is not listed .... I am freaking out a bit right about now. Please let me know if possible on where to start getting custom recovery cause ODIN + tar recovery files gave me magic error or something like that just now.
Thank you guys !
UPDATE: Couldn't sleep.
So I have my new phone rooted with "towel", I install Safestrap and backed up my current ROM (I am on NE3) I see now reason why this dual system needed and stuff. I mean too bad Samsung locking bootloaders and oh well. I have only 2 questions. 1 can I just install latest build from https://download.cyanogenmod.org/?device=jactivelte in to rom SLOT-1 and use it or no. And how much space I can allow for my current ROM and CM I mean I am not planning to have anything on stock so I don't need space at same time I cant make it that when I do want to go on stock I'd have a problem with running it because of not enough space.
Thank you guys once again. I mean If you know few lines ..that's all I am asking. Cause I do see some pros and cons but .. I need straight up answer. Thanks !
Click to expand...
Click to collapse
You cannot install CM. Since you have a locked bootloader, it is not possible to install any custom kernels, so ROMs that require a custom kernel (CM, AOSP, or any ROM based off those) will not work. Using SafeStrap you can flash TouchWiz-based ROMs since they can use you stock kernel.
Look in the AT&T S4 forums for ROMs that say they are compatible with SafeStrap, you should be able to use most of those. Since they are meant fir a different phone you'll have to flash the MasterPatch afterwards. A lot of people seen to like the Hyperdrive ROM.
O-T said:
Your frustration is understand. Swearing or bad language is not excused in this forum for any reason. Moderate at least title or be prepared to get warning and/or thread locked down.
Click to expand...
Click to collapse
My bad you're 100% correct I see how to edit op but not tutle.
Devo7v said:
You cannot install CM. Since you have a locked bootloader, it is not possible to install any custom kernels, so ROMs that require a custom kernel (CM, AOSP, or any ROM based off those) will not work. Using SafeStrap you can flash TouchWiz-based ROMs since they can use you stock kernel.
Look in the AT&T S4 forums for ROMs that say they are compatible with SafeStrap, you should be able to use most of those. Since they are meant fir a different phone you'll have to flash the MasterPatch afterwards. A lot of people seen to like the Hyperdrive ROM.
Click to expand...
Click to collapse
Got it. Thanks. I remember back in a day I've been using "theme" that allowed me to have Google stock feel u guess I need to look in this but for now I guess I'll just remove what I can and will suffer until Nexus 6 is in stock and I can afford it. Love that phone. Also I see 5.0 will be out for active next year so it's not that bad. Meanwhile should I do Ota update to latest stock firmware ?
russiandivxclub said:
Got it. Thanks. I remember back in a day I've been using "theme" that allowed me to have Google stock feel u guess I need to look in this but for now I guess I'll just remove what I can and will suffer until Nexus 6 is in stock and I can afford it. Love that phone. Also I see 5.0 will be out for active next year so it's not that bad. Meanwhile should I do Ota update to latest stock firmware ?
Click to expand...
Click to collapse
If you want, you can still root the latest firmware so you have nothing to lose.
I've posted about this here and there but I think that I have enough data for a wide audience now.
Let me start at the beginning.
I got an international I9305 from the Nordic region about 2,5 years ago, can't remember exactly which build of Android was on it, but it had a stock FM tuner app which I've used at school to check if the FM transmitter we built over the course of a class project was working. Shortly after that instance I got an OTA update( to 4.3 or 4.4.4, sadly can't recall) after which the app disappeared and I lost FM functionality(I had trouble rooting at the time, so Spirit FM was not helpful)
Currently I'm on a custom stock-based ROM made by @MaHo_66 from his thread here, running the UFPB1 build on NEE CSC(Props to him for doing a fine work with these ROMs ), but either the ROM or AGNi do not implement drivers/libraries/dependencies for FM functionality.
So now I turn to you.
I'm searching for devs that have this device and/or are willing to help with this, I'm way past warranty and will try anything to restore FM functionality, just for the sake of proving that it works. (And maybe this thread helps other people who have this device)
How do I support my statements you ask?
The FM is built into the WiFi/BT chip, which is the BCM4334, or as Samsung references it, the SWB-B53, which is probably a modified/proprietary version of the BCM4334 made by Samsung itself, so not much info on it or a separate datasheet. So we know the chip is there, it's just a matter of gaining access to it. Though the service manual shows the connector to the FM antenna to be grounded, this might not be the case for every single motherboard (as I know mine has worked in the past, there's no way it's grounded(OR it's supposed to be because the headphones are used as the antenna, not sure on this one))
I've attached screenshots of the system info, SD Insider showing that the chip is in fact the one talked about earlier, and shots of the motherboard disassembled. The chip that's right under the power button is the one we're looking for. This proves that the hardware is there, we just need software to run it
Sorry for the long post and thanks for your time in advance, all responses are valued
I won't be able to help that much here but FYI here is an old thread (2012) about this topic in case you missed it: FM Radio Not in most I9305 Firmwares, But it may be Hardware capable.
I take the opportunity to say that your post itself is very clear, well explained and nicely documented and it's a good idea to start it, I really hope you will get some help.
:fingers-crossed:
I've seen that thread, but it seems that the folks back then didn't arrive to a conclusion, and there's not much helpful data on the topic
I've also seen threads like this and this, where there's a lot of speculation talk and little concrete helpful information
And thanks, I study electronics engineering, I am required to provide a lot of data in a clean, well documented manner
xda seems to be choking with traffic today
Nice work! Good to see how we started with a notion and then the process of elimination until we proved it :good::highfive:
The thread @Wood Man mentioned is the one I was referencing to you earlier .:good:
Sent from my Samsung GT-I9305 using XDA Labs
@AlexJumper: I fully concur with the statements of @Wood Man and @alias_ z3d!
Precise, comprehensive where necessary but always concise. I'd be glad if I could read more of such posts on XDA.
Don't know if this thread is helpful; found the thread yesterday after flashing a S3 Mini (i8190) with this ROM.
alias_ z3d said:
Cool I'll have a look and thank your post once I get some back. I think @noc.jfcbs would offer invaluable assistance since he's started a lot of threads I've only got one.
Click to expand...
Click to collapse
But here, alias_z3d is wrong. I've only started three threads and nothing special; maybe a forth is coming soon.
You don't require any support; the way you commenced this thread is excellent.:good:
Spirit FM would be a solution, but either the ROM or the kernel I'm running right now doesn't have drivers for FM, so it won't work for me
Basically I'm looking for a way to implement(port?) drivers from firmware that has them to my current ROM, or a way to flash said firmware through custom recovery.
I've tried to downgrade through Odin, but I've been unsuccessful up to this point.
AlexJumper said:
Spirit FM would be a solution, but either the ROM or the kernel I'm running right now doesn't have drivers for FM, so it won't work for me
Basically I'm looking for a way to implement(port?) drivers from firmware that has them to my current ROM, or a way to flash said firmware through custom recovery.
I've tried to downgrade through Odin, but I've been unsuccessful up to this point.
Click to expand...
Click to collapse
What's your problem with Odin? Maybe, someone or me can help? BTW. Which recovery are you using? What's your bootloader?
Before I tried fiddling with rooting and whatnot, I was on stock 4.4.4 so that's definitely the Knox bootloader, after that I got TWRP when Unified Android Toolkit got support for all I9305 builds, then I was able to flash whatever I tried to through TWRP.
I got back to a 4.1.1 build following instructions from this thread, which describes a SIM unlock procedure but it also promises that
You can update, Root, flash custom and stock rom and everything you want. It will stay unlocked
Click to expand...
Click to collapse
(Thinking about it again, I may have misunderstood that )
Anyways, then I got to flashing one of MaHo's ROMs, the build that I'm on right now is I9305XXUFPB1.
But when I was trying to downgrade to find a build that had FM functionality, in one instance I got bootlooping and no recovery access, in another Odin failed to flash(because of it trying to flash an older bootloader over Knox's bootloader) and I had to emergency recover via Smart Switch.
It flashed a newer build though, and since that, every time I flash older firmware through I get bootloops. (Or I just suck at making Odin-flashable packages )
Here's what UAT has to say, seems like I have the latest bootloader now
Oh and I currently have TWRP 2.6.3.0 as custom recovery
noc.jfcbs said:
@AlexJumper: I fully concur with the statements of @Wood Man and @alias_ z3d!
Precise, comprehensive where necessary but always concise. I'd be glad if I could read more of such posts on XDA.
Don't know if this thread is helpful; found the thread yesterday after flashing a S3 Mini (i8190) with this ROM.
But here, alias_z3d is wrong. I've only started three threads and nothing special; maybe a forth is coming soon.
You don't require any support; the way you commenced this thread is excellent.:good:
Click to expand...
Click to collapse
Yes he doesn't need support it looks great I said that in regards to structuring a thread before I checked it out
I think your being modest considering you've got one pinned
Sent from my Samsung GT-I9305 using XDA Labs
AlexJumper said:
Before I tried fiddling with rooting and whatnot, I was on stock 4.4.4 so that's definitely the Knox bootloader, after that I got TWRP when Unified Android Toolkit got support for all I9305 builds, then I was able to flash whatever I tried to through TWRP.
I got back to a 4.1.1 build following instructions from this thread, which describes a SIM unlock procedure but it also promises that
(Thinking about it again, I may have misunderstood that )
Anyways, then I got to flashing one of MaHo's ROMs, the build that I'm on right now is I9305XXUFPB1.
But when I was trying to downgrade to find a build that had FM functionality, in one instance I got bootlooping and no recovery access, in another Odin failed to flash(because of it trying to flash an older bootloader over Knox's bootloader) and I had to emergency recover via Smart Switch.
It flashed a newer build though, and since that, every time I flash older firmware through I get bootloops. (Or I just suck at making Odin-flashable packages )
Here's what UAT has to say, seems like I have the latest bootloader now
View attachment 4168400
Oh and I currently have TWRP 2.6.3.0 as custom recovery
Click to expand...
Click to collapse
In the attached screenshot you see my Bootloader I9305XXUEMKC, I think it's still the one from 4.3 JB. And I definitely suggest to upgrade TWRP to 3.0.2-1 that I also use. I personally won't go to higher custom TWRP versions that are out, because I read about some issues with them; e.g. @alias_ z3d had issued a warning in rodman01's RR thread.
How about just to flash through Odin Chainfire's CF-Auto-Root for Android 4.1.1 again, and - if that works - to start from there
samsung
GT-I9305 m3zh m3 smdk4x12 exynos4 JRO03C.I9305ZHALI8 4.1.1 18 650 167 Download 8319b7feffffdc083ef73450acb1d145 476 430
Click to expand...
Click to collapse
Finally, this week I just rooted an i8190 via Odin and had initially a bad experience but finally a very easy solution. At the end of the ROM flash by Odin, the device automatically booted into system as this was ticked in Odin. It was constantly booting, I assume a bootloop, and after about 2 hours I lost patience. Took the battery out, inserted it again, and started into recovery (home+vol up+pwr). At that time, still the stock recovery was installed i.e. no real capabilities. But at least, I could wipe cache and data. Did that and initiated a boot into system. And that was it. Booting took about 2 minutes, and I had a rooted i8190. Next thing I did, was to flash TWRP 3.0.1 onto the i8190 by Heimdall.
So my course of action is:
1) Go back to 4.1.1
2) Flash CF Auto Root
3) Flash TWRP
4) Flash whatever else
Am I correct?
AlexJumper said:
So my course of action is:
1) Go back to 4.1.1
2) Flash CF Auto Root
3) Flash TWRP
4) Flash whatever else
Am I correct?
Click to expand...
Click to collapse
Affirmative. If I had to play with this device I'd try the following but not knowing if it works:
NO WARRANTY - Use at your own risk, I'm not responsible for bricking your device.
Flash the above linked CF AutoRoot tar.md5-file through Odin, which hopefully reverts you to the desired 4.1.1 (unless this file works try the other CF AutoRoot for 4.4.4 - that's actually the one, with which I rooted an i9305 months ago)
Flash TWRP 3.0.2-1 via Odin or apps like Flashify (the one I use) or Flashfire etc.
Further flashes depend on your desire. Other ROM (hopefully with FM radio drivers), baseband/modem etc.
Instead of using Odin you could certainly also take Heimdall. I used Heimdall only once thus far for the mentioned i8190 to flash a TWRP-3.0.1.img (explained here and here a bit more in detail).
I searched the web like hell for Samsung ROM FM radio driver but no joy.
Ok so I got back to the 4.1.1 build from the thread I linked in my previous post, apparently my bootloader somehow changed..
The CF Auto Root file though seems to be based on a slightly different build than the one I've got now (JRO03C.I9305ZHALI8 while I have JRO03C.I9305XXALI5), should I flash it or is there a possibility it breaks something?
Nevermind, it worked flawlessly
I also updated TWRP to 3.0.2-1.
Now to find a way to get to the builds I need
AlexJumper said:
Ok so I got back to the 4.1.1 build from the thread I linked in my previous post, apparently my bootloader somehow changed..
View attachment 4169145
The CF Auto Root file though seems to be based on a slightly different build than the one I've got now (JRO03C.I9305ZHALI8 while I have JRO03C.I9305XXALI5), should I flash it or is there a possibility it breaks something?
Click to expand...
Click to collapse
Super. I thought the main intention was to bring the device back to 4.1.1, and that was accomplished.
Is it (still) rooted?
If it is, I wouldn't continue with CF-AutoRoot as its only purpose is to get a device rooted.
If you still need root, I personally would continue but I don't know if you might brick the phone.
noc.jfcbs said:
Super. I thought the main intention was to bring the device back to 4.1.1, and that was accomplished.
Is it (still) rooted?
If it is, I wouldn't continue with CF-AutoRoot as its only purpose is to get a device rooted.
If you still need root, I personally would continue but I don't know if you might brick the phone.
Click to expand...
Click to collapse
No, I needed to get back to 4.1.1 as a start because flashing older builds was a pain with 4.4.4 and its bootloader.
AlexJumper said:
No, I needed to get back to 4.1.1 as a start because flashing older builds was a pain with 4.4.4 and its bootloader.
Click to expand...
Click to collapse
The e.g. i8190 has a FM receiver. Maybe it works if you grab some commits from firmware of the i8190 and incorporate it into your ROM. I know you can't compare S3 LTE and S3 Mini with their totally different hardwares but...
That would require them to have the same FM chip at least(which I doubt), as well as libraries/dependencies I guess.
noc.jfcbs said:
In the attached screenshot you see my Bootloader I9305XXUEMKC, I think it's still the one from 4.3 JB. And I definitely suggest to upgrade TWRP to 3.0.2-1 that I also use. I personally won't go to higher custom TWRP versions that are out, because I read about some issues with them; e.g. @alias_ z3d had issued a warning in rodman01's RR thread.
Click to expand...
Click to collapse
3.1.1-0 was not a custom TWRP!
It was official
Iller Chiller said:
3.1.1-0 was not a custom TWRP!
It was official
Click to expand...
Click to collapse
Yeah it was officiall twrp 3.1.1-0 for me from team win website. However I don't think I made it clear in my post.
Sent from my Samsung GT-I9305 using XDA Labs