Related
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!
I have SGN3 N900a build # n900aucubnb4 how can I flash recovery (twrp/cwm) ? Can't find ANYTHING about it anywhere.
Sent from my SAMSUNG-SM-N900A using Tapatalk
JunkheadINC said:
I have SGN3 N900a build # n900aucubnb4 how can I flash recovery (twrp/cwm) ? Can't find ANYTHING about it anywhere.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
You can't flash any custom recoveries because the bootloader is locked. The only thing we have close to it is Safestrap. Look at the Safestrap thread in the development section. It will tell you all you need to know.
And for the record, there is a TON of stuff out there about the locked bootloader preventing custom recoveries, kernels, AOSP ROMs, etc.
Do I need to update to KK And I'll be able to use regular recovery?
- junkheadINC
{[/Galaxy Note 3, N900A/]}
I did not want to update due to the fact I could send apps to the SD anymore.
- junkheadINC
{[/Galaxy Note 3, N900A/]}
The bootloader is locked on KitKat as well. "Upgrading" to KitKat would be even worse because there is no root for it yet and once you install the official update you cannot go back to 4.3.
There is absolutely NO way to use custom recoveries, custom kernels, or AOSP ROMs on the N900A because the bootloader is locked in all firmware versions for the N900A. There is no way to unlock it and probably never will be unless AT&T releases an update that unlocks it, which is very unlikely.
If you want TWRP, CM11, and custom kernels, sell your AT&T Note 3 and buy the T-Mobile version. It has an unlocked bootloader so you can do whatever you want to it. It is fully compatible with AT&T's network. There are guides around here somewhere that go more in depth and explain how too do it.
Thanks man. I got safestrap installed now. What r the down sides to using that? I'm on the ATT next program. I return my phones every 18months for new ones so I can't trade or sell it.
- junkheadINC
{[/Galaxy Note 3, N900A/]}
The only major downsides in my opinion are if you try to do the hold volume up+home+power button to get to recovery (or is it volume down? I forget...), you go straight to the stock recovery instead of Safestrap. Also, if you don't hit the button to boot into Safestrap in time you have to wait for the phone to finish booting, turn it off, and try again. You can't flash kernels with it either, but that's not Safestrap's fault.
It has its upsides as well. You get several slots for flashing ROMs and mods so you can run several different ROMs at the same time without having to wipe out your phone to try a new ROM. Each ROM you flash has to be based off the same version of android, though. That means no Fire Note in the stock slot, Dynamic KitKat in the first, S5 experience in the second, etc. There's more discussion about that in the Safestrap thread.
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.
Ok so its been a while searching for info and i think its time to ask, is there a way to flash a custom recovery? or i did really messed up when updated to this version? i managed to root and i remember following a tutorial before i knew the bootloader thing and it says custom when it boots up.
So, is there a way? if i update should i be able to flash a custom recovery?
varyz said:
Ok so its been a while searching for info and i think its time to ask, is there a way to flash a custom recovery? or i did really messed up when updated to this version? i managed to root and i remember following a tutorial before i knew the bootloader thing and it says custom when it boots up.
So, is there a way? if i update should i be able to flash a custom recovery?
Click to expand...
Click to collapse
This phone's bootloader is completely locked down. There is simply no way to install a custom recovery (or custom kernel for that matter) no matter what version of android you are on. Sorry
that really sucks, i have the sgh-i537 and would have loved to put a custom rom on it. i rooted it as per the instructions that were posted on these forums.
xxreddragonxx said:
that really sucks, i have the sgh-i537 and would have loved to put a custom rom on it. i rooted it as per the instructions that were posted on these forums.
Click to expand...
Click to collapse
This is why I will never buy an AT&T-branded phone again. I just recently acquired a T-Mobile variant Galaxy S5, and I'm loving it, installed Cyanogenmod the first chance I got and never looked back. I missed CM soooooooo much. AT&T and Verizon should never have started locking down their bootloaders (or if they must, at least give those willing and able a method to unlock it like on HTC devices) it's total B.S. and a complete death knell to their development communities
thisisapoorusernamechoice said:
This is why I will never buy an AT&T-branded phone again. I just recently acquired a T-Mobile variant Galaxy S5, and I'm loving it, installed Cyanogenmod the first chance I got and never looked back. I missed CM soooooooo much. AT&T and Verizon should never have started locking down their bootloaders (or if they must, at least give those willing and able a method to unlock it like on HTC devices) it's total B.S. and a complete death knell to their development communities
Click to expand...
Click to collapse
the s4 active was my first root i managed to accomplish. I have other phones lying around but i cannot try rooting any of them yet. I got:
2 sprint galaxy s3 (one has a busted port and other has issues with volume up button)
htc evo from sprint (lost it somewhere in the house and cannot find it)
my galaxy s4 active (rooted but i think i did something wrong bc my battery life is shot to hell)
cricket galaxy s5 (amoled screen is busted and currently waiting to gather funds for repairs, will consider putting cm on it as soon as i get it fixed. Will be my next project.)
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