Related
BEFORE you judge me lol : I'm a new android user, and I've searched and read through the forum and FAQs alike.
Sorry if this is already answered. I've tried the search and read through the FAQs already but there's so much information my head will just explode from it.
Also I'm a fresh android user (just switched over from the iPhone, yay?). I was a very enthusiastic jailbreaker for the iPhone when I was still using that device. Hence my enthusiasm for all things "hackable" for the Android device as well.
All my blabbering aside, I'm just wondering this.
When the Froyo update hits the i9000, your root and everything with it(custom firmwares and stuff?) will be "broken" and be restore as the "stock" Froyo firmware/build right?
Am I even making sense to anyone?
for new firmware, you have to flash it, and so, everything will loss, storage in your internal and external SD will remain but all you app, mod, messages, call log, contact, etc will be lost
like you've partition your home PC with app data saved in C drive and all other documents in D drive, when you reinstall your OS, you wipe off your C and install it again and everything in D should remain (if you do it the right way )
correct me if i am wrong
We won't know for sure, but the way HTC handles Froyo updates, there is no data loss.
But to reply OP, yes, root will most probably be lost. But ability to flash custom firmware should still be available. Afterall, in the first place we don't even need root to flash custom firmwares in the first place, at least on the SGS.
kenkiller said:
We won't know for sure, but the way HTC handles Froyo updates, there is no data loss.
But to reply OP, yes, root will most probably be lost. But ability to flash custom firmware should still be available. Afterall, in the first place we don't even need root to flash custom firmwares in the first place, at least on the SGS.
Click to expand...
Click to collapse
So this does mean that we will be able to get the froyo update through kies even though we are running rooted custom ROM?
alright thanks for the speedy reply and clarification. i have a lot of new terms i'll need to learn for the android now. lol.
sorry, OP, are you talking about an official Samsung firmware update using kies or the one using odin3?
Sent from my GT-I9000 using XDA App
nickporwal said:
So this does mean that we will be able to get the froyo update through kies even though we are running rooted custom ROM?
Click to expand...
Click to collapse
Most probably not. You might have to return to stock firmware to get any updates from Kies.
But what's the point? The Froyo firmware will be available in the Odin form certainly.
chluk2425 said:
sorry, OP, are you talking about an official Samsung firmware update using kies or the one using odin3?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
i think the stock official firmware update. i'm also afraid that flashing a new OS for my current 2.1 will screw up any local settings. i need to do more research about this whole flashing, rooting thing...
shall spare you guys my questions. lol.
ironic from my previous post, i'll just like to ask one simple question.
since i'm a totally new android user, i should just wait for the OFFICIAL Froyo for the SGSi9000, update it and wait for some modified version of the OS, and i'll flash it over for a speedier, more accessable phone?
(i've read the FAQ a thousand times lol.)
Adevem said:
ironic from my previous post, i'll just like to ask one simple question.
since i'm a totally new android user, i should just wait for the OFFICIAL Froyo for the SGSi9000, update it and wait for some modified version of the OS, and i'll flash it over for a speedier, more accessable phone?
(i've read the FAQ a thousand times lol.)
Click to expand...
Click to collapse
the official one is somewhat released near September as i remember... so you have to wait till that time to do it.... i know nothing about flashing using Kies since I am a new user to android as well
but what i am thinking is: either you flash the current firmware (JP3, JP2, etc) using Odin3 or the official firmware using the Kies, the chance is if you brick your phone, samsung will also not responsible for it, so... unless you take your phone to the customer service, you are still risking
well you definitely know more than me lol thanks for the information folks. imma root my phone, don't think there's any risk ye. wish me luck lol.
I am gonna necro this thread since I am an absolute idiot.
It took me a few days just to understand that root is not the SAME as flashing. Finally got that through my head. Hence I can keep my stock JG4 firmware while having root.
But what happens when Froyo comes along. As someone already said, we are going to lose root if we update via KIES. Then what? Do we just use the One Click Root to root our phone again? (Right now I haven't found a reason to flash to a custom ROM yet.)
I am asking this since I am sick of losing all my data in my phone every time I have to upgrade my firmware, but if I can't root my phone afterwards, titanium backup won't work.
snapper.fishes said:
...
I am asking this since I am sick of losing all my data in my phone every time I have to upgrade my firmware, but if I can't root my phone afterwards, titanium backup won't work.
Click to expand...
Click to collapse
as backup tool I use MyBackup Pro (paid app). it backups all (SMS, MMS, Call Logs, Settings ...) and your Apps too.
good stuff.
This may be a noob question but I would like to modify/flash my phone but I have a question before I do. I have done a few searches to find an answer but came up with nothing so far.
I have been browsing the forums for different mods that you can do for the Samsung Captivate. Out of all the mods that I have seen (One Click Lag Fix, Root, Cyanogen, Leaked Froyo Build, GPS settings changes, Removal of AT&T bloatware, unlocking phone for other carriers, side loading enable, and various others), they can ALL be undone using the Odin3 One-Click Stock Rom process correct?
ttp://forum.xda-developers.com/showthread.php?t=731989
Hoever, each captivate has unique phone identification information such as IMEI, Device ID, Wi-Fi MAC Address, etc? Are there any mods that change the unique information for each specific phone? If so, how does Odin3 One-Click Stock ROM process correct that? When Odin3 reflashes to "Stock" ROM, I just want to know how that works if each phone has specific information.
Thanks in advance!
yes they can be undone with odin one click, however once you stray from stock it is most likeley that you wont be able to update to the official 2.2 from att.
personally im going to wait and update to official 2.2 from att then root and nandroid backup and the fun will begin because I will have a backup of the official update with my unique device id to fall back on. in my opinion this is the safest way to make sure I dont screww myself and not be able to update. once that is done it wont be long untill someone builds a decent rom from scratch plus like I stated before I will have a nandroid backup of the update for my phone if I try something and dont like it.
If you still feel compelled I havent gone to the leaked 2.2 but I did have verry good results with stock 2.1 and voodoo lagfix on anather captivate. the phone was verry fast with verry few side effects well woth it if you really cant wait.. But just remember once you stray from stock I believe the only way you will get to 2.2 will be through these forums.
shadow65781 said:
But just remember once you stray from stock I believe the only way you will get to 2.2 will be through these forums.
Click to expand...
Click to collapse
anyway whatever you get from these forums will be much faster and cleaner then stock versions...
anyway i got question about the topic - i had stock 2.1 (JF6), backuped it, tried some cognition 2.2 beta, then flashed with odin to stock and the restored my backuped jf6
did my IMEI, Device ID changed?
(wifi's mac address cannot be changed)
thanks in advance
I am speculating here.
I dont think it can change any hardware I.D info but software I.D is anather story it could possibly cause problems with the O.S interfaceing with other stuff like market.
someone with more knowledge please chime in
Theres a new app in the app store (as of a few days ago) that allows you to change your Android ID#. Called Android ID changer
Unfortunately, it won't figure out what your unique # is. If you install Cognition, you have the same ID# as everyone else.
I'm not sure about Odin - stock. My Odin 2.1 # is different than the Cognition one. Ends in 43b1. I'd be really interested to know if anyone else could check their Odin 2.1 eclair JF6 (all stock, not modified) android ID # and see if it ends the same as mine. If it's different, then that means you can always revert to JF6 to figure out your real #. If it's the same, then I guess that means for the time being your SOL for figuring that out for now.
You can always check it before making modifications....
Shadow; you are probably right, but at the end of the day software is all that matters...
Thanks for the responses. Judging from what I have been reading on the replies so far, nothing can bring me back to my original stock android 2.1 OS with all original software IDs my phone had even if I use the steps outlined in the
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
forum post.
How do you find out what your android ID is?
gormander said:
Thanks for the responses. Judging from what I have been reading on the replies so far, nothing can bring me back to my original stock android 2.1 OS with all original software IDs my phone had even if I use the steps outlined in the
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
forum post.
How do you find out what your android ID is?
Click to expand...
Click to collapse
Just as long as you are running any of the stock eclair 2.1 without any mods all your unique id's wil display correctly, even if you have flashed to cog 2.2 or leaked 2.2 if and when you flash back to a truly stock eclair 2.1 the id's will return correct.
The android id changer app from the market will display the current android id your phone has when you open the app - it shows the current id just above the entry field where you can change your id. So download the app open it get you id write it down, save it in a safe place, then if you flash any rom the does not populate you unique id correctly you can reinstall the android id changer and enter your correct id manually.
Is [STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY method a "truly stock eclair 2.1" as you mentioned in your post Davy? Also, are there any other IDs I should be aware of and take note before I flash/mod anything?
Thanks.
gormander said:
Is [STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY method a "truly stock eclair 2.1" as you mentioned in your post Davy? Also, are there any other IDs I should be aware of and take note before I flash/mod anything?
Thanks.
Click to expand...
Click to collapse
I believe odin 3 one click in that thread is a straight rom off a phone with samsung jf6 stock install - yes I'm fairly certain it is stock. There is another odin 3 one click for the leaked 2.2 which is obviously not stock.
If you download an app from the market named simply " ID " it still give you four of your phones id numbers for your info.
I'm pretty sure all your phones id numbers are either generated from hardware coded info or your google account - so as long as you gave properly coded software on your phone these wil always populate correct - even if you install something that messes these up of you remove the bad software replace it with good software it should then populate the id numbers correctly again.
Such as the android id in the leaked froyo that isn't being generated but simply being copied to every phone it is installed on - when you replace the froyo leak or any of the roms built off the leak with one of the stock samsung roms your phone will then generate the id correctly again.
No thread jack but i thought id ask in here.
If im rooted and ONLY rooted on 2.1 will that not allow me to update to official froyo?
Nickel Dime Bay said:
No thread jack but i thought id ask in here.
If im rooted and ONLY rooted on 2.1 will that not allow me to update to official froyo?
Click to expand...
Click to collapse
maybe, maybe not. Some of the people who were rooted only (no mods) were able to update to the jh7 update. And from what I have heard mini kies has worked to update for everyone that flashed back to stock and tried to update that way - but this is all some what of a guess as we don't know exactly how att and/or samsung will role out froyo for the captivate.
You are all really funny. Your worried about getting an official OTA from AT&T so you won't mod your phones, lol. Your choice I guess but the last AT&T OTA bricked a lot of phones that had not even been rooted. The ROMS that you find on these forums are way better than any of the stock Samsung and AT&T put on them with their bloaty, buggy software. I won't do any OTA updates, I wait until the developers here fix them, remove the crap AT&T put's on them and speed them up. I give you guys credit though, staying stock sucks bad, it freaks me out to see that stock screen everytime I flash back to stock before flashing a new ROM to my phone. I only stayed stock for 2 weeks and never turned back, glad I did it too. I would've bought an I Phone 3g if I wanted to stay stock and not mod a phone. Go look around the forums and read the threads, don't just skim them or you won't learn anything. See what custom ROMS and kernels are cooking and what people are experiencing with them. We had the OTA rooted on here a few hours after the update was rolled out, you won't miss anything by not recieving it officailly from AT&T. Hell we already have some good Froyo ROMS and kernels. Keep waiting if you want but there's plenty of goodies here why wait?
Rhiannon224 said:
You are all really funny. Your worried about getting an official OTA from AT&T so you won't mod your phones, lol. Your choice I guess but the last AT&T OTA bricked a lot of phones that had not even been rooted. The ROMS that you find on these forums are way better than any of the stock Samsung and AT&T put on them with their bloaty, buggy software. I won't do any OTA updates, I wait until the developers here fix them, remove the crap AT&T put's on them and speed them up. I give you guys credit though, staying stock sucks bad, it freaks me out to see that stock screen everytime I flash back to stock before flashing a new ROM to my phone. I only stayed stock for 2 weeks and never turned back, glad I did it too. I would've bought an I Phone 3g if I wanted to stay stock and not mod a phone. Go look around the forums and read the threads, don't just skim them or you won't learn anything. See what custom ROMS and kernels are cooking and what people are experiencing with them. We had the OTA rooted on here a few hours after the update was rolled out, you won't miss anything by not recieving it officailly from AT&T. Hell we already have some good Froyo ROMS and kernels. Keep waiting if you want but there's plenty of goodies here why wait?
Click to expand...
Click to collapse
Different strokes for different folks man, Its not like im using the tw3.0 and the blue bubble background lol ive customized stock 2.1 how i want it to look and its working PERFECT for ME, fast as hell, gps locks on quick etc. Flashing a rom is nice and all but the risk of bricking youre phone is high (theres always odin i know) and if stock is working for people then more power to them.
The way I look at it is, the phone belongs to you, do what you want with it or to it as you please.
but I do agree with one point above, I personally would not trust a samsung/att update to not mess up my phone. But that does not mean it won't work well for you or that you won't be happy with it that way.
gormander said:
However, each captivate has unique phone identification information such as IMEI, Device ID, Wi-Fi MAC Address, etc? Are there any mods that change the unique information for each specific phone? If so, how does Odin3 One-Click Stock ROM process correct that? When Odin3 reflashes to "Stock" ROM, I just want to know how that works if each phone has specific information.
Thanks in advance!
Click to expand...
Click to collapse
IMEI can never change. I don't think your device ID can change buy your Android ID can change as you've been told by those before me. If it possible to change your WiFi MAC address, only I'm not sure how to do it. If you can do it in a full version of Linux, I don't see why it's not possible on our phones. Also, before you do any mods, make sure you backup a couple files onto your computer for safe keeping. The ones I'm talking about are in the /efs directory of your phone and relate to unlocking the phone for other networks. The second you go to mod your phone, these files will be erased and replaced with ones that are harder to get your unlock code out of.
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.
Hi there folks!
Im getting mighty confused about this flashing thing.
Im looking to change my ROM to something else then the ICS from Samsung.
Here is the deal.
I read the warning posts and it say (what i think it means) that my build "XLP9" ICS 4.0.3 from Samsung is not safe to do anything on.
I look around on the net to see if there is a way (despite what i read here).
It looks promising.
But all the things i find is ether a lower version of Android (like 2.3.x) or someone is telling me about tons of stuff to download and do before.
So this is were i ask you all.
Do (been searching for 2 days, perhaps my search terms are bad) anyone know if there is a working way to for me to change my version to AOKP for e.g without destroying my phone?
Like i said before, my Build is: XLP9, android version 4.0.3 (from Samsungs update service).
Phone is rooted using CWM.
Its a Note version for the .EU market bought like a few weeks ago (came with 2.3.x i believe).
If you know a thread that contains step by step instructions that will allow me to change the rom, please post it to me here.
Or if I´m screwed for updating to ICS just tell me so to
Cheers
Honken
Hello again.
Yet another day and cant locate any information that im after.
So i tought perhaps there is a way to downgrade the phone back to the factory settings (not ICS).
But since i did the upgrade to ICS is the old rom still on the phone?
I mean to reset it back (same as thode recovery discs on a computer).
Any help or points in the right direction is helpfull at this time.
cheers
Honken
honken08 said:
Hi there folks!
Im getting mighty confused about this flashing thing.
Im looking to change my ROM to something else then the ICS from Samsung.
Here is the deal.
I read the warning posts and it say (what i think it means) that my build "XLP9" ICS 4.0.3 from Samsung is not safe to do anything on.
I look around on the net to see if there is a way (despite what i read here).
It looks promising.
But all the things i find is ether a lower version of Android (like 2.3.x) or someone is telling me about tons of stuff to download and do before.
So this is were i ask you all.
Do (been searching for 2 days, perhaps my search terms are bad) anyone know if there is a working way to for me to change my version to AOKP for e.g without destroying my phone?
Like i said before, my Build is: XLP9, android version 4.0.3 (from Samsungs update service).
Phone is rooted using CWM.
Its a Note version for the .EU market bought like a few weeks ago (came with 2.3.x i believe).
If you know a thread that contains step by step instructions that will allow me to change the rom, please post it to me here.
Or if I´m screwed for updating to ICS just tell me so to
Cheers
Honken
Click to expand...
Click to collapse
It have too many method to change from stock rom to custom rom or aokp. My suggestion is choose your favourite rom and read carefully with the installation method provided at op, then you be fine.
Sent from my GT-N7000 using xda premium
honken08 said:
Hello again.
Yet another day and cant locate any information that im after.
So i tought perhaps there is a way to downgrade the phone back to the factory settings (not ICS).
But since i did the upgrade to ICS is the old rom still on the phone?
I mean to reset it back (same as thode recovery discs on a computer).
Any help or points in the right direction is helpfull at this time.
cheers
Honken
Click to expand...
Click to collapse
Now that you have upgraded to ICS. Those are the factory settings.
Easiest way to downgrade to GB Is by flashing a stock GB rom via pc Odin.
Most of the new ICS custom ROMs now just require you to install AbyssKernel 4.2, then select advanced options and select reboot recovery. Then you wipe your device (wipe data, cache and dalvik cache). From this moment you're free to flash. It all takes less then a minute if you hurry (joking, don't rush when flashing your phone), and it's not very complicated. Do it once and you'll know it's simple.
You need to have a root access first. Plenty of guides how to do it out there.
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