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
Related
I can't seem to find a recovery that will flash a rom for MY phone. I have the MetroPCS version/variant of the sgh-t599n and I really want to be able to flash a custom rom to my phone, but I can't seem to find anyone with (codinMetroPCS) files for it. The only reason I say that is because when I finally got CWM 6.0.3.2 downloaded and working, tried to flash beanstalk rom and it told me "THIS ROM IS FOR CODINALTE PHONES NOT CODINMETROPCS PHONES" Is there a different rom for the Metro phones? Or am I doing something wrong....Im rooted through cydiaimpactor, well, i guess technically through the pre-rooted stock rom I had to flash through Odin...BTW-Over the last two weeks I've learned that flashing a rom on a samsung (at least mine) takes a custom recovery, which needs to be flashed via Odin (something I didn't know how to do at the time)...I almost feel like Im starting to get confused with all these different programs needed to run or flash or download this or that....I'm not sure if the info is even in the correct order in my head......could someone please walk me through this? or call me! lmao...this is giving me a headache. lol....but I REALLY REALLY want to know what Im doing.....ANYONE? PLEASE??
Cdbarron727 said:
I can't seem to find a recovery that will flash a rom for MY phone. I have the MetroPCS version/variant of the sgh-t599n and I really want to be able to flash a custom rom to my phone, but I can't seem to find anyone with (codinMetroPCS) files for it. The only reason I say that is because when I finally got CWM 6.0.3.2 downloaded and working, tried to flash beanstalk rom and it told me "THIS ROM IS FOR CODINALTE PHONES NOT CODINMETROPCS PHONES" Is there a different rom for the Metro phones? Or am I doing something wrong....Im rooted through cydiaimpactor, well, i guess technically through the pre-rooted stock rom I had to flash through Odin...BTW-Over the last two weeks I've learned that flashing a rom on a samsung (at least mine) takes a custom recovery, which needs to be flashed via Odin (something I didn't know how to do at the time)...I almost feel like Im starting to get confused with all these different programs needed to run or flash or download this or that....I'm not sure if the info is even in the correct order in my head......could someone please walk me through this? or call me! lmao...this is giving me a headache. lol....but I REALLY REALLY want to know what Im doing.....ANYONE? PLEASE??
Click to expand...
Click to collapse
Just flash the recovery listed in the BeanStalk thread.
There's 3 variants of the phone; T599, T599N, T599V (codinatmo, codinametropcs/codinanewcotmo, codinavid) they're pretty much the same exact phone, there's just slight differences in proprietary files - so the developers decided to unify the all of them into one (codinalte), as it's easier to build for one phone then three seperate times. The recovery's responsible for the phone; which is why the recovery plays a key-role, basically the recovery you have right now can only accept roms that are specifically 'titled' as codinametropcs, and by flashing that recovery, you'll be able to flash any of the 4.4.x roms (BeanStalk, Vanir, OmniROM, CM, AOKP, and soon pure-vanialla AOSP).
ok so....
Exothermic said:
Just flash the recovery listed in the BeanStalk thread.
There's 3 variants of the phone; T599, T599N, T599V (codinatmo, codinametropcs/codinanewcotmo, codinavid) they're pretty much the same exact phone, there's just slight differences in proprietary files - so the developers decided to unify the all of them into one (codinalte), as it's easier to build for one phone then three seperate times. The recovery's responsible for the phone; which is why the recovery plays a key-role, basically the recovery you have right now can only accept roms that are specifically 'titled' as codinametropcs, and by flashing that recovery, you'll be able to flash any of the 4.4.x roms (BeanStalk, Vanir, OmniROM, CM, AOKP, and soon pure-vanialla AOSP).
Click to expand...
Click to collapse
?
When you say flash....you mean through Android System Recovery (stock recovery)? right? ....sry man...back when i was rooting my droid x, I never ran into any issues and it seemed a little easier to flash roms
Cdbarron727 said:
?
When you say flash....you mean through Android System Recovery (stock recovery)? right? ....sry man...back when i was rooting my droid x, I never ran into any issues and it seemed a little easier to flash roms
Click to expand...
Click to collapse
flash it through odin.
Thank you....now....I think I've actually gotten this far already.....had cwm installed...then tried to flash beanstalk with cwm and I got the codin error saying "this is not for codinmetropcs" ...if I get that problem again...is there something conflicting with it in some way? Or where did I go wrong? do i have to have twrp?
sorry to bug bro
Exothermic said:
Just flash the recovery listed in the BeanStalk thread.
There's 3 variants of the phone; T599, T599N, T599V (codinatmo, codinametropcs/codinanewcotmo, codinavid) they're pretty much the same exact phone, there's just slight differences in proprietary files - so the developers decided to unify the all of them into one (codinalte), as it's easier to build for one phone then three seperate times. The recovery's responsible for the phone; which is why the recovery plays a key-role, basically the recovery you have right now can only accept roms that are specifically 'titled' as codinametropcs, and by flashing that recovery, you'll be able to flash any of the 4.4.x roms (BeanStalk, Vanir, OmniROM, CM, AOKP, and soon pure-vanialla AOSP).
Click to expand...
Click to collapse
I just flashed cwm through odin and it passed....I havn't rebooted just yet, but I know it was working before.... But just saw that the cwm I downloaded from the beanstalk thread says its for kitkat builds only. My phone is running 4.1.2..does that matter? or does that mean I just need a 4.4 rom to be flashed with it? Sorry if these are dumb questions
Cdbarron727 said:
I just flashed cwm through odin and it passed....I havn't rebooted just yet, but I know it was working before.... But just saw that the cwm I downloaded from the beanstalk thread says its for kitkat builds only. My phone is running 4.1.2..does that matter? or does that mean I just need a 4.4 rom to be flashed with it? Sorry if these are dumb questions
Click to expand...
Click to collapse
It's cool; it just means you can only flash 4.4 roms, so you cannot flash cm10.1, cm10.2, and pac. It doesn't matter that your phone's running 4.1.2.
Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.
Nicholo said:
Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.
Click to expand...
Click to collapse
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.
simple_fear85 said:
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.
Click to expand...
Click to collapse
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.
If you want to stick to CM11, you can upgrade your baseband to 24A and use jackpotclavin's build, it works well but it hasn't been updated past 4.4.2 I believe.
Nicholo said:
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.[/QUOTE
no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
All aosp roms now that are 4.4.4 are running the 24a bootstack or kitkat.
Click to expand...
Click to collapse
no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
Click to expand...
Click to collapse
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
You use autorec for twrp?
Sent from my LG-VS980 using XDA Free mobile app
Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
Do you have a custom recovery? If so, flash the 2.7.x.x zip within your current recovery, then reboot recovery. If you don't have a custom recovery, then use autorec or freedom tool to install one.
Sent from my VS980 4G using XDA Premium 4 mobile app
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.
Hi Guys,
Hope someone a bit more clued up than myself can clarify my questions or guide me..
I've done some searching, but am not 100% confident.
So, I have a I9305 running a Boeffla Kernel 5.2. If I recall correctly, I upgraded from 4.1.2 to 4.3, but
kept my old bootloader. So I am rooted and have TWRP on this 4.3 based CFW. No KNOX anywhere.
(Did all this about 12 months ago or more, and have had some significant life events in the last year,
so have been completely out of the scene.. )
Anyway, I was considering upgrading to 4.4.4 (stock)
Can anyone tell me if I can do this and remain Knox free and have a custom recovery such as TWRP.
(If so can you point me to a working guide?)
Thanks Heaps in Advance,
BrikHaus
BrikHaus said:
Hi Guys,
Hope someone a bit more clued up than myself can clarify my questions or guide me..
I've done some searching, but am not 100% confident.
So, I have a I9305 running a Boeffla Kernel 5.2. If I recall correctly, I upgraded from 4.1.2 to 4.3, but
kept my old bootloader. So I am rooted and have TWRP on this 4.3 based CFW. No KNOX anywhere.
(Did all this about 12 months ago or more, and have had some significant life events in the last year,
so have been completely out of the scene.. )
Anyway, I was considering upgrading to 4.4.4 (stock)
Can anyone tell me if I can do this and remain Knox free and have a custom recovery such as TWRP.
(If so can you point me to a working guide?)
Thanks Heaps in Advance,
BrikHaus
Click to expand...
Click to collapse
Hi,
you have 3 options:
- Option #1: Stay with your old 4.1.2 firmware base with OLD bootloader and you can flash which custom KitKat ROM you want (N4 Elite ROM, TGP, AMCHA KK, etc.). If your favorite ROM is NOT compatible with TWRP, you will have to flash PHILZ recovery 6.48.4 instead and then flash the ROM. If the custom ROM is compatible with TWRP, you will only have to flash the ROM.
When you will flash the ROM, don't forget to choose a KK modem (XXUFNI3, XXUFNJ1 or XXUFOA1 depending on the ROM base) to have a working baseband and also, don't forget to choose a compatible Kernel with OLD bootloader (AGNi, HBO kernel or Dlite). Note : Stock kernel is not 100% compatible with OLD bootloader : WIFI will not work.
- Option #2: Upgrade to latest official 4.4.4 stock (I9305XXUFOC1) for i9305 with ODIN : this way, you will have new 4.4.4 KNOX bootloader and you will not have custom recovery anymore. If you want to stay like this, you will be 100% stock and 100% up-to-date from Sammy.
- Option #3: Follow the option #2 and then root your phone and flash custom recovery. You could finally stay like this or flash a custom ROM. If you choose to flash a custom ROM, one good thing is that you will be able to use stock kernel (100% working including WIFI) if available with this ROM.
You can follow that guide from @MaHo_66 : http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
Reminder: To go VERY clean wipe and install a custom firmware :
1. Backup all your data
2. Full wipe (data, cache and dalvik) in recovery including internal sdcard (internal sdcard format option in mounts and storage settings)
3. Flash a i9305 official firmware (4.1.2, 4.3 or 4.4.4) via ODIN. IMPORTANT : If you don't want KNOX BL because of warranty purpose, don't flash official 4.3 or 4.4.4 via ODIN.
4. Root
5. Flash custom recovery : (Philz for instance)
6. Install custom ROM
Steps 4 and 5 can be permuted.
PS: Off topic : @MaHo_66, you're now a RC, well done !
Thanks @FLooDW
Btw. youre spot on as always helping others, very good explanation you gave here :good:
MaHo_66 said:
Thanks @FLooDW
Btw. youre spot on as always helping others, very good explanation you gave here :good:
Click to expand...
Click to collapse
Thanks
Ok, if it's good, I hope it will help BrikHaus.
FLooDW said:
Thanks
Ok, if it's good, I hope it will help BrikHaus.
Click to expand...
Click to collapse
Im pretty sure it will
Legend!
Thank you VERY MUCH @FLooDW! Wish I could give you 10x Thanks!
Just the answer I was after. I wasn't sure if it was even possible to have a custom recovery on KNOX 4.4.4 bootloader.
I dropped out of the scene just as KNOX raised its ugly head...
I'm not worried about the warranty at all. Phone is two years old and well out of warranty period.
I'll go Option #3, sounds like just what I was after.
Thanks again!
BrikHaus said:
Thank you VERY MUCH @FLooDW! Wish I could give you 10x Thanks!
Just the answer I was after. I wasn't sure if it was even possible to have a custom recovery on KNOX 4.4.4 bootloader.
I dropped out of the scene just as KNOX raised its ugly head...
I'm not worried about the warranty at all. Phone is two years old and well out of warranty period.
I'll go Option #3, sounds like just what I was after.
Thanks again!
Click to expand...
Click to collapse
Yes you can have custom recovery with Knox BL. It's my case and everything is ok for me.
I hope you'll be ok
Please let us know.
I saw your sig..
Philz looks like it has more features than TWRP.. Might try that.
How do you find your performance with that kernel & rom?
Cheers Mate.
BrikHaus said:
I saw your sig..
Philz looks like it has more features than TWRP.. Might try that.
How do you find your performance with that kernel & rom?
Cheers Mate.
Click to expand...
Click to collapse
I'm very happy about perf with latest Amcha and AGNi. I have between 26000 and 26600 in AnTuTu without any overclock.
User experience is great in my case.
I don't use Fly-on mod (available in Amcha for instance) because I've noticed some big lags with my config on my phone.
All went pretty well. Had a couple of hangs, but got them all sorted.
Currently restoring, but having an issue where the phone switches from "USB Media mode" to "Dock Mode" and back and forth.
Weird issue I've never seen before....
BrikHaus said:
All went pretty well. Had a couple of hangs, but got them all sorted.
Currently restoring, but having an issue where the phone switches from "USB Media mode" to "Dock Mode" and back and forth.
Weird issue I've never seen before....
Click to expand...
Click to collapse
About your USB media / Dock issue, I've never read such problem. Moreover, I don't use dock at all. I will not be very helpful about this. Sorry.
FLooDW said:
About your USB media / Dock issue, I've never read such problem. Moreover, I don't use dock at all. I will not be very helpful about this. Sorry.
Click to expand...
Click to collapse
Yeah I don't use dock either. It seems it gets confused about what its actually plugged into..
Anyway, I'll figure it out. Thanks heaps for your help Mate. Very much appreciated.
Hi,
I took the plunge and rooted + flashed my phone last week after finding that the CM13 ROM is supposed to support a G800H dual sim. Unfortunately CM13 doesn't find either of my SIM cards.
So I spent a long time reflashing other custom ROMs to see if I could get one to work. I finally managed to find the CM12.1 ROM which finds my SIM cards but the recent and back button isn't functioning and when I try to uninstall an app the phone reboots and the app remains.
Can anyone help me get one of these ROMs to work properly?
Alternatively, my wife has exactly the same phone as me (unrooted and running everything as the it was out of the box), is there a way I can clone her device to mine then factory reset it?
Thanks in advance.
Flash the first Russian Lollipop twice. Yes, it's weird but if you downgrade sometimes you need to flash it twice to fully downgrade, then flash CM. If you still can't get SIMs to work on stock Lollipop, downgrade to KitKat then use OTA to go to Lollipop.
About cloning, to do a full clone you need to use TWRP as far as I know.
@lfom
Thank you for your reply my friend.
I have resorted to using Samsung Smart Switch and re initialised my phone back to stock. I think I am out of my depth as I don't even understand your reply lol!
Thanks again!
jcwd said:
@lfom
Thank you for your reply my friend.
I have resorted to using Samsung Smart Switch and re initialised my phone back to stock. I think I am out of my depth as I don't even understand your reply lol!
Thanks again!
Click to expand...
Click to collapse
Sorry, I will try to explain. You've used Odin to root, right? You have to use Odin to flash any stock ROM that is not to the same country as your original ROM (different CSC code). All Marshmallow ROMs are based on the first Russian Lollipop ROM released by Samsung, that's why if you flash them over other ROMs you have problems like no SIM.
Ahhh I think that might be the problem! (Yes I used Odin.)
In the instructions it clearly says "1. Make sure you have updated to stock 5.1.1" - I didn't do that - what an idiot.
I take it when you say "flash any stock ROM" I need to get a 5.1.1 stock ROM - where would I get one of those from?
EDIT: would this be suitable? http://www.youmobile.org/blogs/entr...-Android-5-1-1-Lollipop-update-is-Rolling-out
Thanks for your persistence.
jcwd said:
Ahhh I think that might be the problem! (Yes I used Odin.)
In the instructions it clearly says "1. Make sure you have updated to stock 5.1.1" - I didn't do that - what an idiot.
I take it when you say "flash any stock ROM" I need to get a 5.1.1 stock ROM - where would I get one of those from?
EDIT: would this be suitable? http://www.youmobile.org/blogs/entr...-Android-5-1-1-Lollipop-update-is-Rolling-out
Thanks for your persistence.
Click to expand...
Click to collapse
To avoid issues, if you want to run any my CM13 (Marshmallow) ROM, you need to flash through Odin the first 5.1.1 Russian version, for what I said before. The common and easiest place, although slow, is from SamMobile website:
http://www.sammobile.com/firmwares/download/56934/G800HXXU1BOI2_G800HOXY1BOI2_SER/
@Ifom Thanks very much I will start the download when I get back from work and install it when it finishes (some time next week).
Thanks again.