Database Develop

[REQ] Rogers Stock Firmware UXJJ6

UPDATE: 27/11/11
I have started a thread in the development section that contains all this information, please leave any findings or questions there, I believe members will find it more helpful there.
The thread can be found here
I have removed the file links from the OP to stop any confusion in the future. All files can be found in the other thread where it will be maintained and updated (if necessary) in the future.
Thanks for reading.
UPDATE: 27/11/11
Andrew_Low has provided a copy of his stock FROYO backup, which I tested on my tab and confirm that it is working. The kernel is rooted, other than that it is a clean ROGERS rom.
He was also able to capture the GINGERBREAD update, (which I have not tested as of yet, any testers please post your results) this is the stock update available from KIES.
Many thanks to him for this, if it helps you, hit his thank you button[/URL]. If you find this thread helpful as well, hit my thank you button.
Instructions on flashing are not provided. If you need these files it means you know how to flash your device, have flashed a custom ROM previously, and require this to return to a stock state.
Both downloads can be found in the link
downloads here
ORIGINAL POST:
I am looking for the stock firmware for a Rogers Galaxy Tab (P1000UXJJ6)
There are many posts mentioning it, even asking for it, but no firmware to be found.
If anyone has a copy of it can you please post a link here or PM me, or even if you have a backup of the original ROM (or if you can make a backup if you have the original software on your tab). Anything will do, as searching for it has not showed any results.
MODEL: P1000R
IC: 649E-SGHI987
ORIGINAL FIRMWARE:
Version: FROYO.UXJJ6
P1000UXJJ6
The SamFIT web shows
Model: P1000
Region: Rogers - Canada, (Branded: yes)
Available languages: en, fr,
October 2010 Revision: 6
Thanks in advance.
RED

Not an easy ROM to find is it?
Anybody ?

Any fresh ROGERS tabs out there???

I just picked up a used Galaxy Tab that has this firmware on it. I'm not new to hacking Android devices, but the Tab is new to me.
I haven't installed Kies yet, but will in a couple of days and can make a backup.

That would be just great, thank you very much, and I assure you that you will be glad that you made a backup for yourself as well in the future (hopefully not though, I don't expect you to have problems or anything like that but you know what I mean).
If possible, can you make the backup before you root the device, otherwise it seems to be a bit of a headache trying to get it un-rooted after the fact.
Many thanks.
EDIT: I guess i'm thinking more of a temp root than a perm root before backup

Sigh, I'm in noobville here with Kies.
Cross booted to Windows XP (I normally use Linux as my desktop) - installed Kies and sorted out USB connectivity.
I don't see where in Kies I can do a firmware backup. The backup just grabs the user data from the device.
It detects my firmware version and offers me the chance to update (which I assume would be a bad idea). Quickly looking on the net, you can 'capture' the firmware files during an update - but that doesn't help grab the version I'm running. Seems there may be a registry hack that lets you install older versions in Kies? If that's true, why can't anyone with a Rogers tab just get the old firmware easily?
Looking for a bit of hand holding.
Oh yeah, and device is bone stock. I'll likely root, unlock and install CyanogenMod - but I'm in no rush. Happy to try to help capture the stock ROM. It may help me out in the future, you never know.

Search for Roto-backup, it is a way to back it up bit by bit. It's a thread by Rotohammer, using his technique members were able to provide UN-ROOTED firmware, which are posted in the dev section. Have a little read see what you think.

The Roto-backup link was helpful, but that requires rooting.
Here's what I've done. Starting with a bone stock, factory reset device. I rooted the device using SuperOneClick 2.2. Sadly I had to run this under Windows to get it to work, mono + Ubuntu didn't seem to work out
I used the default "auto" method of rooting with SuperOneClick, and I did install busybox. In theory - if you really wanted to have an un-rooted stock, you could use the Unroot option of SuperOneClick.
Then I used the roto-backup script. This seems to have worked and I've got a 250MB zip file that I believe contains the stock firmware.
Are you brave enough to test it?
Files were zipped into a single file then split into chunks using RAR to get around upload limits. Grab them from skydrive.

Nice. I have a backup I came across but it's screwy and can't be un-rooted. The root method you used was temporary or perm?, the difference would be one disappears after a reboot.
When I originaly did my backup I used a temp root and came up with a file that I'm pretty sure was about the same size.
Brave you ask? I'm downloading the 3 RARs right now and will check it out.
Many thanks, will flash and tell you how it goes.

Well, Andrew_Low, it worked like a charm. The flash went smooth I will attempt to un-root shortly, and tell you how it went.

Glad it worked. Let me know if unroot via SuperOnClick 2.2 goes ok.
Why do you want non root? Warranty claim?
Slightly off topic, what ROM would you recommend? Seems any AT&T compatible ROM should play ok on the Rogers tab. I'm partial to CM being that's what is on my phone.
Sent from my GT-I9000 using XDA App

It is for warranty reasons, I have two tabs one was acting up. I did re stock it and sent it back but I wasn't able to un-root so I'll see if it goes through with samsung.
I HAD my stock rom that I somehow deleted (or just misplaced, cause I can't find it anywhere) Then I figured that I am not the only one who may need this, and since it is harder to find, I thought that I would try and help out the P1000R folks by getting a stock rogers rom for those who would like to revert. I was going to wait until I receive my tab back and see what they did to it and maybe have a fresh rogers rom on it to backup. I plan on posting it for members to have.
Our Rogers tabs are great for flashing anything on it really (p1000 related of course). Currently I have BOCA on mine, I had HC RC1 on it previously for a good little bit, and was going to put the ICS alpha build on it, but now since I'm left with one I use it for business purposes and require full functionality out of it. The tab that I sent back had OVERCOME KRATOS on it. Funny enough, this tab is the one that i'm always flashing different roms on and overclocking and plain old abusing it yet it was the other one that crapped out.
I recommend the OVERCOME rom as it is very stable, fast and reliable with almost no bugs. Combined with the bell modem it could also be used for phone calls if necessary. But experiment with any one you want until you find one that suits your needs, I found both my tabs hard to brick so I wouldn't worry too much if I were you. I can't wait for an ICS beta rom to stick on this one.

Cool. I'm interested in a clean stock ROM if one shows up, please post to this thread. I'll try the unroot and see if that works for me.
Open to pointers on how to soft root and capture ROM. Seems feasible, but I didn't find a way to soft root and give me enough to roto backup.
Sent from my GT-I9000 using XDA App

Looking for a clean stock ROM for Rogers as well for warranty work, thanks!

Can't folk use the 2.3 firmware from kies? I haven't tried, but if you flash the rooted UXJJ6 from this thread then use Kies to upgrade to 2.3 you'd be in an unrooted stock state.
Sent from my GT-I9000 using XDA App

theREDlegion said:
Well, Andrew_Low, it worked like a charm. The flash went smooth I will attempt to un-root shortly, and tell you how it went.
Click to expand...
Click to collapse
Hmm, very interesting. I ran the unroot on my device and it did manage to remove the superuser apk, but beyond that the device appears to still be rooted - busybox is still installed, and when I shell in over adb I get the # indicating root access.
I suspect just removing the superuser app is enough to make it appear 'as stock' - but any expert digging into the device and it's easy to see things are not stock.
If I were to try again - seems zergRush may be the local root you want to use, then from there figure out how to backup the ROM.
[edit] Ooh... reboot and adb has lost the # - I still see busybox installed in /system/xbin/busybox - I suspect this is pretty close to 'stock' if I punt the /system/xbin stuff entirely.
I'm not sure I'm that motivated to chase this further - I can't guarantee it is 100% stock, and it's the same as dl'ing the files I previously uploaded and running SuperOneClick 2.2 unroot + removing the busybox stuff as I specified above. The only mystery here is really what causes adb to have root privs when rooted.

Sweet - appears I was able to grab the ROM from Kies during the 2.3 upgrade - so I've got a copy of the clean/stock Rogers GINGERBREAD.UXKG1 firmware.
Will upload and link here in the next couple of days.

Very sweet, I will post it in the OP for reference.

pback said:
Looking for a clean stock ROM for Rogers as well for warranty work, thanks!
Click to expand...
Click to collapse
I will post the Froyo version on the first post for reference, but if you are willing to wait Andrew_Low is generously going to provide a stock rogers Gingerbread rom which I will post for you and others in the OP.

Gingerbread is here https://skydrive.live.com/redir.aspx?cid=61f79860d644cd72&resid=61F79860D644CD72!124
+1 to theREDlegion for cleaning this stuff up and making the thread useful.

[Q] Restore to 4.3 NB4

OK it's been a while and I have screwed up some stuff.
I have the att note 3 and I"m rooted running 4.3 build NB4. I had some stuff frozen and xposed things setup. Been running fine and really haven't messed with anything for 6-7 months. I'm selling the phone and told the person buying it I would leave it on 4.3 stock rooted.
So I just did a factory reset / wipe cache. Now when it boots up I get a samsung keyboard force close error and can't do anything until I change to something else. I figure there will be other issues also, I realize now I should have undone things, but it's to late.
So what do people recommend. My first thought was to somehow flash the NB4 files, but i don't have custom recovery.
So any suggestions, steps or files would be much appreciated.

Can you not just odin to reflash it back to stock 4.3?

Maybe but i cant locate the files to odin and im not that famaliar with how to use odin. Can some provide a liitle guidance.

cd23murray said:
OK it's been a while and I have screwed up some stuff.
I have the att note 3 and I"m rooted running 4.3 build NB4. I had some stuff frozen and xposed things setup. Been running fine and really haven't messed with anything for 6-7 months. I'm selling the phone and told the person buying it I would leave it on 4.3 stock rooted.
So I just did a factory reset / wipe cache. Now when it boots up I get a samsung keyboard force close error and can't do anything until I change to something else. I figure there will be other issues also, I realize now I should have undone things, but it's to late.
So what do people recommend. My first thought was to somehow flash the NB4 files, but i don't have custom recovery.
So any suggestions, steps or files would be much appreciated.
Click to expand...
Click to collapse
I don't think you will find it NB4 build for odin. I was looking for firmware for some time and had no success. You need to get back to NI9 than find update NI9 to MJ5 and then MJ5 to NB4. So i will suggest find this updates so you can sideload after you get stock NI9. and i think you have all files you need to do this here : http://forum.xda-developers.com/showpost.php?p=51468226&postcount=10

[Q] My phone is stuck in a bootloader loop

I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them. *fixed

Caelrie said:
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them.
Click to expand...
Click to collapse
Easy fix. ODIN flash the stock COD6 software. Then start over again with cf auto root. There is a thread that had all of the files you need in one zip.
Sent from my SM-N910T using XDA Free mobile app

Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.

Caelrie said:
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Click to expand...
Click to collapse
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)

absinthesummer said:
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
Click to expand...
Click to collapse
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile

Caelrie said:
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Click to expand...
Click to collapse
Cool, glad you got it sorted. Yeah as long as you can access download mode you're golden, and a bonus if you can get into recovery as well.
Excellent job actually searching and reading and fixing your problem, far too many people want answers just handed to them, so kudos to you for that.
Just for the future if you need help, try to remember and list all steps you took (even if you don't know where you went wrong) in excruciating detail because it helps us troubleshoot and figure out what the problem is. Without certain pertinent info it could take a lot longer to solve it.
Overall good job, glad you're up & running.

Go to rapture download the rom and load it to sd card. Then follow directions exactly and u will be ok. No loading anything. Fresh start
BAD ASS NOTE 4

I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.

ElAguila said:
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
Click to expand...
Click to collapse
Technically you shouldn't be flashing just the partial firmware. It sets up a base so that you can flash a lollipop rom in recovery without issues. I'm not sure why someone is recommending just flashing the partial firmware only. I guess they figured it wouldn't cause issues.
Anyway, here is how the partial firmware should be used:
Flash partial firmware in Odin
Flash flashable stock lollipop in recovery.
Set up rom, make a backup.
From here you can restore your old kitkat backups without the problems that some are seeing (those who Odin the full firmware are having problems restoring kitkat backups/flashing kitkat roms without Odining ank4 first). The partial firmware prevents that but it's designed to be flashed right before flashing a lollipop rom.
I hope that helps some of you who are having issues.

[Q] How to go back to stock rom with a unlocked, 30.BC bootloader

Here is the problem.
I updated my xt1058 to 5.0.1 , so my bootloader was updated to the 30.BC version. It still is unlocked and I've TWRP installed too working good. After the update, a few days later using the stock rom, my phone got stuck on a bootloop, even after I wiped everything using TWRP the bootloop continued. In order to continue using the phone I installled the official CM12.1 rom over the stock, did all the wipes and then I could boot and use the phone.
My problem is that CM12.1 isn't fully functional yet, and I get random reboots, signal loss, and some apps crashes the phone and I really wish to come back to stock rom since I miss some stock features. There is a way to do this or I have to wait for a 5.0.1 SBF appear? And there is really no way to go back to stock 4.4.4 because the bootloader update right?
Thanks in advance for the help!

There may be ways that some will suggest using part from one rom, and parts from another... HOWEVER while that might give you what appears to be a "working phone" you may find some features not working, or some bugs that weren't there before because you have mismatched "parts" on your phone. And you will be at great risk for bricking your phone should you take an OTA in the future.
And yes, there is no 100% safe, and "will never brick" way to downgrade, even with an unlocked bootloader. It is why I spent the time writing this -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 (which includes a collection of links to threads where people did brick trying to downgrade)
At this point, if you don't want to risk bricking your phone, and want to SAFELY get back to a Stock Motorola ROM, you need to wait until we see a leak of the Stock Moto SBF that is the same or newer build than the last update you flashed on your phone. It will bring all parts/pieces of your phone back into line.

So I'll have to wait the SBF, hope it doesn't take too long!
Thanks for the help.

blueflyingllama said:
So I'll have to wait the SBF, hope it doesn't take too long!
Thanks for the help.
Click to expand...
Click to collapse
It takes as long as it takes...
You wont see a 5.1 SBF util sometime after 5.1 starts pushing to ALL PHONES on all carriers, Moto has posted the Developer Images on their web site anywhere from a few weeks to a few months after the OTA update has been pushed. For all other carriers, since MOTO doesn't post/publish them, we are at the mercy of someone on the inside grabbing them and leaking them, so there is no telling how long that might take, and if it will definitely happen.

I9305 FM Receiver

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