Database Info

Any advice for an Android beginner?

I just got the Captivate about a month ago. Had a regular phone for about a year, touch screen went out, bought a replacement digitizer but knew it was a temporary fix anyway and wanted a new phone. Convinced the maternal unit to use her contract extension to get me a new phone, and snagged the Captivate for $30 from RadioShack. My first Android phone, and I have to say I'm horribly disappointed, but I guess I'm doing something wrong here.
First two or three weeks, my mom had the phone and got to play around with it for a while. Wasn't until the 29th that I got the phone, and I just played around with it for a week and got all the apps I deemed useful and worthwhile. Eventually realized I couldn't use Flash in the browser, nor Skype, etc., without upgrading to 2.2.
So, I went through the tutorial Samsung provided, watched videos on Youtube just to be sure, but followed everything Samsung's tutorial said word for word. ... only for my phone to end up completely screwed up. Gallery, Browser, Music Player, Video Player, and many other default applications were missing. Now I'm smart enough with technology to think, okay, something's wrong. I knew about the factory reset, so I went to go to settings to do that, and realized. ... oh wait, the Settings menu is also missing. Wonderful. There was no "Settings" button in the Applications list, and if I tried getting to it from the menu button, it simply did nothing at all.
Found Odin, flashed back to 2.1, and then factory reset and got rid of every application I had and etc., so that absolutely nothing was on it, basically a stock phone. Tried upgrading again fresh, still following the instructions very closely. Same problem occurred, and I was pissed. Gave up on 2.2, tried flashing back to 2.1 /again/ with Odin, only for my phone to decide it didn't want to enter download mode anymore. Forced it using 'adb reboot download', but alas, it locked up in the middle of flashing back to 2.1 and wouldn't do anything. I waited about 30 minutes to see if it'd resume the flashing process at all, but nothing, so I regrettably had to disconnect the USB cable and hard brick the phone (wouldn't turn on or anything).
Still under warranty, so I replaced it from RadioShack, and now have a new Captivate. Went ahead and installed all the applications I needed, used the Sideload Wonder Machine to install a few third-party applications, had no problem doing that for a while. Didn't bother attempting to upgrade. However, my computer got a trojan and deleted the MBR. Repaired using the XP boot disc, but it meant I was back on SP2. After installing every last one of the damn updates all over again, I decided to check up on some new applications to install via sideloading.
Hooked up my phone, it detected all the new hardware again since the drivers seemingly were also lost amongst everything else during the repair, only for it to encounter an error on the "Samsung Android Composite ADB Interface". So, I uninstalled the drivers, tried installing them manually. Hooked up the phone, but it still wanted to try to install that one driver and failed. I've restarted my computer, uninstalled the drivers, attempted manually installing them through device manager, you name it. Still can't get it to work -- it keeps having a fatal error every time. However, it's only when my phone has USB Debugging on. Installs every single driver perfectly fine when it's off, in MTP/Mass Storage/Kies mode. Just has a "fatal error" in USB Debugging on that one driver.
tl;dr, the drivers are broken on my computer and I can't fix them despite actually /not/ being computer illiterate. And, I kind of still want 2.2, but apparently the stock 2.2 update is a pain in the rear end and I no longer have a warranty through RadioShack now, so I can't risk bricking my phone due to a faulty update process. Any suggestions?

err, the only thing you should have needed to do was install the latest version of Kies, plugged the phone in, it would have prompted you to do the update. It's quite painless..

Edit: Sorry irrelevant

sw411 said:
err, the only thing you should have needed to do was install the latest version of Kies, plugged the phone in, it would have prompted you to do the update. It's quite painless..
Click to expand...
Click to collapse
At the time I tried, Kies itself didn't support the Captivate. Only Kies mini. And in order to do that upgrade, I had to install the drivers, then put the phone into download mode to install more drivers for some odd reason, restart the phone (taking out the battery and putting it back in), then hook it up. Kies mini wouldn't detect the phone for several tries at first, finally got it about the 10th time in. Then go to the "Upgrade phone" link, and yeah. I followed the instructions from Samsung's official SGH-i897 Froyo upgrade guide.
I did EXACTLY as the instructions say, down to the wire. Still ended up both times with all those applications missing and the settings panel missing, unable to do a factory reset without flashing back to 2.1 first.

Install z4root and root phone
Install rom manager
Flash clockwordmod recovery from rom manager
Choose a 2.2 rom from the forums
Download and copy to SD card
Install via rom manager
????????
Profit
Hope this helps. Btw I reccomend firefly or serendipity for the rom
Sent from my Captivate running CyanogenMod7 using XDA Premium App

brendanmurphy said:
Install z4root and root phone
Install rom manager
Flash clockwordmod recovery from rom manager
Choose a 2.2 rom from the forums
Download and copy to SD card
Install via rom manager
????????
Profit
Hope this helps. Btw I reccomend firefly or serendipity for the rom
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
Only downside to rooting the phone is the voided warranty. I don't entirely know what I'm doing there when it comes to flashing, and if I manage to do something wrong and brick the phone again, I'm completely wiped. I don't have the money to replace the phone at all. I have no job. ._. Only reason I got the phone was because I managed to get some spare money fixing up a friend's computer, and the maternal unit's contract extension was available. I'm not paying for the phone, still my parents. Damn economy in this state is so broken, and I'm screwed over worse since I have no diploma.
However, I was looking into info on the roms, and while I was tempted to try out CM7 for the fact it was 2.3, I actually considered getting Paragon RC6 from what I had read. Just decided not to because I can't replace the phone if I screwed up. In the slim chance I do opt to risk not having a phone at all if I do something wrong, would you say Paragon's worthwhile or would it be better to go with Serendipity? I do like TouchWiz, and Wifi access is a must (200 MB plan isn't going to cover it with how I use data; I'm frequently using Wifi in as many places as is possible), but I'm pretty sure both of those are fine there. Just not really sure which would be better overall, performance-wise.
I can't do either of them right now anyway until I figure out why the drivers aren't installing. So that's my first issue.

Don't worry about bricking I almost guarantee you will brick your phone once. But that is what Odin is for and it's almost impossible to hard brick a phone these days. Just install paragon with the instructions I gave its really fool proof these days to install rom. You will learn by trying if you mess up so be it that's what xda is here for to help.
Drop me a pm anytime if you need help
Sent from my Captivate running CyanogenMod7 using XDA Premium App

brendanmurphy said:
Don't worry about bricking I almost guarantee you will brick your phone once. But that is what Odin is for and it's almost impossible to hard brick a phone these days. Just install paragon with the instructions I gave its really fool proof these days to install rom. You will learn by trying if you mess up so be it that's what xda is here for to help.
Drop me a pm anytime if you need help
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
Well. Despite it being almost impossible, I've managed it once already within the first month of having one. Kind of why I'm a bit skittish about actually going through with it. I'm definitely all about modding and customizing things to your liking, but not having the funds to fall back on if I /do/ screw up bigtime again, yeeeeah.
After looking at Firefly and Serendipity thoroughly, though, I'm impressed. It's a tough choice between the three (Paragon, Serendipity, and Firefly). I'm leaning towards Serendipity now though after watching a video just to see the interface. Kinda not a huge fan of the GB launcher -- I liked the side-scrolling app launcher more, honestly -- but that's not a big deal.
So, let's see if I've got the details down right before I try anything. Search z4root in Market, install. Subsequently get Rom Manager, install it. Flash ClockworkMod (via Rom Manager). Pick a 2.2 rom (which will be a tough choice), and download it to my microSD card to put in the phone. Install said rom (via Rom Manager). And then, voila, it's done.
Did I miss anything, or am I actually following instructions right here?
Edit: Nope, can't find z4root in the Market anyways. Means I'd have to Sideload it, and until I get this driver issue solved, that's not gonna work either. That's gonna be the first thing necessary to fix since it also means I can't use Odin if I do anything wrong... Downloading Serendipity now though, so if I can get that fixed, I may go ahead and try this out after I get some sleep. But since I'm nocturnal, time for some rest. Hoping for some tips or pointers when I get back on. Definitely looking forward to good experiences with XDA and my Android phone.

Yea those are the exact steps its really simple. http://forum.xda-developers.com/showthread.php?t=944418 try this it will install drivers for you ans sideload apps. This is a useful tool
Sent from my Captivate running CyanogenMod7 using XDA Premium App

The.Se7enth said:
Only downside to rooting the phone is the voided warranty.
Click to expand...
Click to collapse
Quick question. Did you purchase the insurance through AT&T for the phone? If so, you will most likely always be able to get it replaced even if it's been rooted. It's just as simple as calling the help line, and saying that you have no idea what happened, and it won't work now. Of course that is worst case scenario
From my experience, the Captivate is a pretty difficult phone to hard brick compared to some others. For a beginner, all of this can be somewhat overwhelming, we've all been there. But once you get the hang of the whole process, you'll be good to go!

Yeah I've done that once already. Just called in and told them that it seems like a software problem and they replaced it no charge.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Beginner help....
AT&T warranty is for 1 year on new phones, 90 days on phones you purchase as refurbished. (30 day "I just don't like THIS phone" replacement/return in both cases.) If Radio Shack will not replace the phone, AT&T should swap. If neither is willing to help, Samsung will honor their 1 year warranty, but it requires shipping back to Samsung.
Your situation sounds like your Windows PC is the problem. A complete reinstall of Windows & apps (not just a quick MBR repair / install over top of existing stuff) may be your best bet if you can't use a different machine.
Kies Mini should upgrade your phone to 2.2 painlessly - without you having to do anything but plug it in and click the on screen button.

Also if you root and need to return it just flash back to stock which will take away root and at$t is none the wiser, most likely

peypey008 said:
Quick question. Did you purchase the insurance through AT&T for the phone? If so, you will most likely always be able to get it replaced even if it's been rooted. It's just as simple as calling the help line, and saying that you have no idea what happened, and it won't work now. Of course that is worst case scenario
From my experience, the Captivate is a pretty difficult phone to hard brick compared to some others. For a beginner, all of this can be somewhat overwhelming, we've all been there. But once you get the hang of the whole process, you'll be good to go!
Click to expand...
Click to collapse
Nope. Don't feel their insurance policies are worth it. You spend more money on the insurance policy in total, even if it's month-to-month, than you would on a brand new contractless phone. Besides, I had only made $120 from fixing up three ancient computers (so ancient they actually had ISA slots and DIMM SD-RAM memory -- one was even a Pentium II), and only had $50 by the time I bought the phone which was a couple months later. My $50 went towards the phone and a pack of screen protectors, while my mom covered the upgrade fee. Couldn't afford the insurance policy even if we wanted to.
But I do greatly appreciate the encouragement. I'll give it a go in a bit, and try out flashing Serendipity. I'll follow the official instructions from their own website though, because I read this on their FAQ:
"Never use ROM Manager. EVER, EVER, EVER, EVER, EVER!"
pouelle said:
AT&T warranty is for 1 year on new phones, 90 days on phones you purchase as refurbished. (30 day "I just don't like THIS phone" replacement/return in both cases.) If Radio Shack will not replace the phone, AT&T should swap. If neither is willing to help, Samsung will honor their 1 year warranty, but it requires shipping back to Samsung.
Your situation sounds like your Windows PC is the problem. A complete reinstall of Windows & apps (not just a quick MBR repair / install over top of existing stuff) may be your best bet if you can't use a different machine.
Kies Mini should upgrade your phone to 2.2 painlessly - without you having to do anything but plug it in and click the on screen button.
Click to expand...
Click to collapse
RadioShack replaced the phone the first time, but the manager there said after replacing it once, the warranty was thus void. I'm not sure if profanity is allowed here, but you can figure out which word I wanted to reply to him. It's eight letters long, starts with bull.
I've read posts on AT&T forums saying if the phone's bricked or can't be repaired by user methods though, especially if it's rooted, that they won't honor the warranty at all and will consider it user error and that you're out of luck. Even people who tried to upgrade to 2.2 stock had issues with that. But I dunno.
Anyways, my machine works perfectly for everything else. Before the repair, when I tried to upgrade? It was a fresh install. I had just reformatted it because it was performing sluggish before and I decided I wanted a single-boot installation instead of having my old dual-boot of Windows 7 and XP. It's now just XP for the time being, seeing as how the hardware's limited and I want to get the best out of it for gaming (I can run 7 with ease, but it uses more resources than XP, thus games don't run as well).
I realize earlier I may have come off as implying the upgrade to 2.2 process was difficult. I don't mean it was "difficult" by any means necessary. It was simply a plug the phone in, let all the drivers install, unhook and put in download mode, hook up again for more drivers. Restart phone, start up kies, hook up phone, and click "Upgrade phone" button. Accept the terms of service or whatever, and wait. Upgrade starts, phone flips into download mode on it's own, restarts a couple times, and voila, you're on 2.2. I thought it was a piece of cake. My issue is that regardless of how easy it was, it still ended up rather broken because all those applications were missing, on top of the fact the Settings panel was also gone, leaving me unable to perform a factory reset.
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?

The.Se7enth said:
At the time I tried, Kies itself didn't support the Captivate. Only Kies mini. And in order to do that upgrade, I had to install the drivers, then put the phone into download mode to install more drivers for some odd reason, restart the phone (taking out the battery and putting it back in), then hook it up. Kies mini wouldn't detect the phone for several tries at first, finally got it about the 10th time in. Then go to the "Upgrade phone" link, and yeah. I followed the instructions from Samsung's official SGH-i897 Froyo upgrade guide.
I did EXACTLY as the instructions say, down to the wire. Still ended up both times with all those applications missing and the settings panel missing, unable to do a factory reset without flashing back to 2.1 first.
Click to expand...
Click to collapse
Fail, Kies Mini works from Kies mode on the phone. It puts the phone into download mode when you start the upgrade from Kies Mini.
Just saying...

The.Se7enth said:
Nope. Don't feel their insurance policies are worth it. You spend more money on the insurance policy in total, even if it's month-to-month, than you would on a brand new contractless phone. Besides, I had only made $120 from fixing up three ancient computers (so ancient they actually had ISA slots and DIMM SD-RAM memory -- one was even a Pentium II), and only had $50 by the time I bought the phone which was a couple months later. My $50 went towards the phone and a pack of screen protectors, while my mom covered the upgrade fee. Couldn't afford the insurance policy even if we wanted to.
But I do greatly appreciate the encouragement. I'll give it a go in a bit, and try out flashing Serendipity. I'll follow the official instructions from their own website though, because I read this on their FAQ:
"Never use ROM Manager. EVER, EVER, EVER, EVER, EVER!"
RadioShack replaced the phone the first time, but the manager there said after replacing it once, the warranty was thus void. I'm not sure if profanity is allowed here, but you can figure out which word I wanted to reply to him. It's eight letters long, starts with bull.
I've read posts on AT&T forums saying if the phone's bricked or can't be repaired by user methods though, especially if it's rooted, that they won't honor the warranty at all and will consider it user error and that you're out of luck. Even people who tried to upgrade to 2.2 stock had issues with that. But I dunno.
Anyways, my machine works perfectly for everything else. Before the repair, when I tried to upgrade? It was a fresh install. I had just reformatted it because it was performing sluggish before and I decided I wanted a single-boot installation instead of having my old dual-boot of Windows 7 and XP. It's now just XP for the time being, seeing as how the hardware's limited and I want to get the best out of it for gaming (I can run 7 with ease, but it uses more resources than XP, thus games don't run as well).
I realize earlier I may have come off as implying the upgrade to 2.2 process was difficult. I don't mean it was "difficult" by any means necessary. It was simply a plug the phone in, let all the drivers install, unhook and put in download mode, hook up again for more drivers. Restart phone, start up kies, hook up phone, and click "Upgrade phone" button. Accept the terms of service or whatever, and wait. Upgrade starts, phone flips into download mode on it's own, restarts a couple times, and voila, you're on 2.2. I thought it was a piece of cake. My issue is that regardless of how easy it was, it still ended up rather broken because all those applications were missing, on top of the fact the Settings panel was also gone, leaving me unable to perform a factory reset.
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
Click to expand...
Click to collapse
Yea once you have serendipity installed don't use rom manager but for initial install your fine
Sent from my Captivate running CyanogenMod7 using XDA Premium App

cappysw10 said:
Fail, Kies Mini works from Kies mode on the phone. It puts the phone into download mode when you start the upgrade from Kies Mini.
Just saying...
Click to expand...
Click to collapse
You can "say" all you want, my good sir, but google the instructions. They tell you clearly to put the phone into download mode TO FINISH INSTALLING DRIVERS. You don't start up Kies mini until after all the drivers are installed, at which point you hook up the phone with USB Debugging, not Kies mode. I appreciate your willingness to help, but be sure to read everything I say before you correct me. I'm not that slow. I read instructions thoroughly and I've read quite a lot of posts on these forums. I work with computers regularly -- just not Android. The issue had nothing to do with that anyway, so that doesn't even matter.
brendanmurphy said:
Yea once you have serendipity installed don't use rom manager but for initial install your fine
Sent from my Captivate running CyanogenMod7 using XDA Premium App
Click to expand...
Click to collapse
I'm sure it's possible, and I don't mean to come off disrespectful, but I'm just gonna go with the instructions on their website. Just seems a safer route to install a ROM by the creator's instructions, you know? Only thing I'm not sure about is what they mean by "Flash it in 2e recovery (twice)." on ClockworkMod.
The.Se7enth said:
I have one last question. If I do somehow manage to get these drivers to work again (without reformatting, which I don't have the time to do), should I have the SIM card out while flashing the ROM? I'm wondering, subconsciously, if somehow that may have had something to do with the upgrade to 2.2 screwing up so bad. I had the SIM card in, with all my applications installed at first. Second time, no apps or anything were installed, but the SIM card was still in.
Edit: Well aware of most forums having a "do not double post" rule, as much as I want to bump this thread with an update on the issue. But, I've restarted my computer, tried a different USB cable, uninstalled and reinstalled the drivers from numerous different sources, and still the same "fatal error" issue on "Samsung Android ADB Composite Interface". I simply cannot get that to install whatsoever, and without it, the phone isn't detected as being hooked up even by SWM, much less anything else. Seriously, what do I do? I'm not reformatting my computer, because I simply see no reason for it, but I have no other computer I can use. How do I get these drivers to install properly like they did before?
Click to expand...
Click to collapse
These two are still my top questions now. Is it a good idea to have the SIM card out during the upgrade process, and not put it back in until after the update is 100% complete?
Also, I'm really frustrated about this whole driver thing. I know the drivers aren't broken because I used them on this very computer before, and the repair shouldn't have damaged anything because absolutely everything else is working flawlessly. But every time I've uninstalled the drivers completely, and hook up the phone, it keeps getting a fatal error on that. Apparently "S3C6410 Android ADB" is the name of the device that can't install drivers.

[Q] com.Android.phone crashes after root Samsung Admire

Last week I rooted my primary phone, a Samsung Admire with Gingerbread 2.3.4. This was done only after successfully rooting my older LG Optimus T running Fryo. I had no trouble with either phone during the process. However, as of 2 days ago the Admire has had some troubles, namely that the phone function crashes when I press the send key. I get the error message stating “Sorry! The process com.android.phone has stopped unexpectedly. Please try again.” It will receive incoming calls but they cannot be answered and when I try, it crashes
I’ve spent much of the time since researching the problem to find the cause and it’s fix. In doing d\so I have read of multiple causes from screen resolution changes to attempted over clocking, which I have played with. I’ve read that there might be problems with the phones attempting to switch from 2g to 3g too rapidly, something this phone cannot do I believe.
I came to the conclusion, probably erroneously, that I needed to reset it back to factory and then reinstall apps and data out of the backup I made using Titanium Backup prior to the phones troubles. So I did so, doing the three button cocktail I’ve read about here on XDA Forums. After doing this, the problem persists. I’ve read some more becoming more baffled as I went along. So I tried to reroot the phone using one click root, and that was unsuccessful as well, no root. I then read that all I needed to do was to install Superuser from the Market. In attempting this I found my device was no longer recognized by Market and after going through their troubleshooting process it’s still unrecognized, Next I decided, also most likely erroneously to reset the phone again using the three button combo as before. This time I noticed at the bottom of the screen written in yellow, E: File is written: not updated
Also as a side note my phone currently says that there are 133MB available and after the reset(s) my bloat ware has not returned,
So that’s it. I seem to have deleted something that kills the phone app and prevents me from rooting. Other than those two things the phone is working well. However as it sits it’s merely a small Internet tablet with no phone capability. Can anyone help me out with this? And yes, I have read and read and read about it but clearly this is beyond my ability to fix on my own.
Thanks,
Zeke

Hey, my skill level ranges between beginner and intermediate, but honestly in a situation like that I would odin back to stock. I have an epic 4g, so I have no idea what your download mode is or if you have one or if you have to use quick boot or fast boot? Its one of those. If **** ever hits the fan on me (Thank god it hasn't yet) I would odin to an old stock rom and root it and install a recovery and wipe and flash a ROM. Good luck I hope I helped and didn't sound like too much of a scrub.

Reached said:
Hey, my skill level ranges between beginner and intermediate, but honestly in a situation like that I would odin back to stock. I have an epic 4g, so I have no idea what your download mode is or if you have one or if you have to use quick boot or fast boot? Its one of those. If **** ever hits the fan on me (Thank god it hasn't yet) I would odin to an old stock rom and root it and install a recovery and wipe and flash a ROM. Good luck I hope I helped and didn't sound like too much of a scrub.
Click to expand...
Click to collapse
I will research this Odin you mention as I have no clue as to what it is. Thanks, anyone else care to chime in?
Zeke

[Q] Should I let OTA updates install?

Hi there, I just got this tablet with its awesome screen a couple of days ago and as the title says I'm not sure if I should let the OTA run.
I already have a GS2 so I was aware of the eMMC bug and I also have an overly cautious nature so I said no to the updates and turned the auto check for updates feature off.
I got the P6810 version.
Currently it is on a ROM the firmware websites don't recognise:
2.6.36-P6810DTKL4-CL602212
I have no idea what version it will update to as if I ask it to check and agree to the disclaimers the download size is listed as less than a megabyte.
I have read quite a few of the threads here but none of them made things completely clear as to what to do in this situation. One of the posts said not to do a wipe with a Honeycomb based ROM which is what this is.
By the sounds of it we should get Jelly Bean in a month or so, well it is rumored and that would be great. I'm not sure I really need a rooted custom ROM but I definitely need to be off Honeycomb!
Thanks for your time.

I was having problems with my wi-fi connection and had to set it manually, I thought that perhaps the update might address that so I let it update.
It was 0.07Mb and has taken it to:
2.6.36-P6810DTKL5-CL604290
Now it says no updates available but the firmware sites say there are a few newer versions including an ICS based one. I guess I need to do that manually or via Kies, which I don't really trust.
I'll wait for advice from more knowledgeable people.

I would and have trusted Samsung Kies before for updates... not on this device, but on my Notes... and it did just fine...
good luck

jimmbomb said:
I would and have trusted Samsung Kies before for updates... not on this device, but on my Notes... and it did just fine...
good luck
Click to expand...
Click to collapse
Thanks for the reply Jimmbomb, I had a bit of a think about it and figured if it died I'd just be without it while it got fixed or replaced. Given I wasn't used to having it I probably wouldn't miss it so I gave Kies another try. This is unlike my phone which I need to work and, after it wiped and failed to restore my data and settings, I haven't updated my phone. I know I really should but once burnt twice shy.
I haven't used Kies for over a year, in that time it has improved significantly and actually did what it claimed to!
My initial reluctance to use it was based off my initial experience with it, it seems like Samsung have listened to feedback and fixed it up which is good news for us.
Now we just need to patiently wait for the JB release, hopefully it will be like the update for the GS2 and include the fancy features, smart stay being the one I expect will be most useful for a tablet.

I was wrong, Kies still has some problems.
I thought I'd plug my SGS2 in to see what would happen, it doesn't detect it although windows has no problems talking to it and letting me copy files via explorer.
I did the 'troubleshoot connection' procedure and all it does is reinstall the USB driver, since doing that neither device will connect to Kies!
Time to uninstall and try again I guess, SO frustrating given the size of company Samsung is.

Yep.
Samsung fraks it up on a number of fronts.
I think they need to learn that putting 5000 versions of devices on the market and then providing crappy support is an approach to business that leaves a bad impression.

Galaxy S4 i9507 (Aus/HK only) custom firmware success!

Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
UPDATE 3/6/14
I installed a snapshot of CM 11 (KitKat) onto my device with little issues. I'll update this guide with the links to that firmware, and also update the existing links because of changes CyanogenMod made to how they aggregate their S4 devices now. They are treating them all as derivatives of 'jftle', so basically one firmware fits all devices, including the i9507! (even if not official yet).
Please read the bottom of this post if you wish to install KitKat on your device.
CUSTOM FIRMWARE ON SAMSUNG GALAXY S4 i9507 - Aus/HK
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
If you're looking to root this device, I found that by treating it essentially as an international i9505 I was able to fulfil all three of the things I mentioned above.
UPDATE: THIS WILL VOID YOUR WARRANTY AND RESULT IN 'KNOX WARRANTY VOID 0x1' BEING DISPLAYED WHEN YOU ENTER DOWNLOAD MODE ON THE DEVICE. PLEASE BE SURE YOU ARE OKAY WITH THIS HAPPENING BEFORE TRYING THIS FOR YOURSELF. AS IT STANDS, KNOX CANNOT BE RESET, IT IS AT A HARDWARE LEVEL.
[ROOT i9507]
Using Chainfire's guide to CF-Auto-Root in the Galaxy S 4 i9505 Original Android Development section of this forum; I was able to root my device despite it being an i9507. Being a new user, I wasn't sure exactly what things to test out whether the root worked/was permanent, but I did install AdBlock Plus and it asked me for Superuser privileges, then proceeded to work. I also restarted the device and tested whether the root was still present; it was.
[INSTALL CLOCKWORKMOD]
I decided to install CyanogenMod as I have heard from friends that have it; and read online about it being one of the more stable custom ROMs available. It has been a while since I last owned an Android device! So, continuing with my theme of treating this device as being an international i9505, I obtained CM 10.2.0, a stable release of the jfltexx CM, based on from their website (as of December 2013, this was the most recent). Their custom installer app on Windows did not support my phone, so I had to use their guide for manual installation.
Their guide contained steps to installing ClockworkMod Recovery as well as the ROM installation. Following the guide, I installed it without a hitch. When rebooting the phone from ClockworkMod, it prompted me about the fact that the phone may reflash its own recovery tool, but this did not happen. Once again, a success.
[INSTALL CYANOGENMOD]
The last task was to install CM. This was quite an endeavour as I decided to use someone else's Windows 8 laptop (being the only Windows device I had access to at the time) and I forgot how much of a struggle it can be! Again, I used CM's guide to installing 10.2.0 (which by the way is Android 4.3.1, whereas the stock firmware is bloated and heavy at 4.2.2). This went off without a hitch once I reminded myself how the ADT works. I also did as CM suggested and installed the Google Apps pack alongside the ROM.
So, currently this is where I'm at. The device boots and reboots fine. Some users in certain threads had issues with loading 4.4 (KitKat) ROMs or custom ROMs that they didn't allude to the names of, so I don't know if they were having issues with CM or not. There are other threads, but that was the one that kickstarted my attempts to get this all to work. Their issues with the custom ROMs seemed to be related to the 4.4 ROM not recognising the modem of the i9507; I'm not sure why this is but the i9507 was made specifically for Australian/Hong Kong networks so perhaps 4.4 has not been updated yet or something of the like. Anyway, on 4.3.1, or CM 10.2.0, my SMS, calling, and internet are working fine (it displays Virgin Mobile as my carrier). My 4G reception is somewhat iffy in this town (or in particular my house), and the reception seems to be switching between 3G and H so whether that is indicative of 4G not working, I'm not sure. LTE is definitely checked in the settings, however, and my area does have 4G, but my parents' iPhone 5Ss sometimes do not have 4G in this house either. I'll report back tomorrow after having tested the phone for a day to see if the 4G does activate.
As it stands, however, the phone seems to be functioning well. Oddly the Settings report that the phone is an i9505, I assume that's normal as I'm using a ROM for that particular phone!
[CONCLUSION]
So, I hope that anyone who has been looking for a way to remove the carrier/Samsung bloat from their i9507 device will have a good time using the guides I've used. I followed them to the letter and I had no issues.
DISCLAIMER: I had no troubles, but that's not to say you won't either. Please be careful, as you may potentially risk affecting your phone negatively. I'm simply telling you what I did, not giving you a 100% correct and flawless guide that will work no matter what.
Also if you're looking for a 4.4 ROM then you might be out of luck, least till some dev or coder takes notice of this device's existence and helps out to develop a specific way of rooting this phone/installing custom ROMs for this phone. Overall though, it seems to all work fine so perhaps the 4.3.1 CM isn't such a bad thing.
If you try this and want the original firmware back on your phone, use this link. I believe that OPS is the Australian firmware, the other one is for Hong Kong. So, for the second link, HK is Hong Kong, and the one without is for Aus.
UPDATE 3/6/14
I've successfully managed to install a Nightly build of CM 11, based on KitKat. Read my latest post in this forum for more info. I essentially found that upgrading from within the phone itself caused a number of issues so I did a fresh flash. Please note that such a flash of a new OS wipes all personal data but not things like images, videos, etc. I lost all my contacts, SMS, browsing history, apps etc. But my Gallery, Downloads folder, etc remained intact.
I followed my guide to flashing the phone again, but I used a Nightly build of CM 11, based on KitKat. As I write this, there are actually stable versions of CM that you can use in place of the CM 10.2.0 I used in the above guide. If you follow those steps but use this firmware you'll find no issue. Feel free to use CM's guide, but don't, under any circumstances, forget to flash Google Apps to your phone!!!
If you need a hand or want a question answered, feel free to post here and I'll do my best to help you out. Thanks!

kaiserwatson said:
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
If you're looking to root this device, I found that by treating it essentially as an international i9505 I was able to fulfill all three of the things I mentioned above.
[ROOT i9507]
Using Chainfire's guide to CF-Auto-Root in the Galaxy S 4 i9505 Original Android Development section of this forum; I was able to root my device despite it being an i9507. Being a new user, I wasn't sure exactly what things to test out whether the root worked/was permanent, but I did install AdBlock Plus and it asked me for Superuser privileges, then proceeded to work. I also restarted the device and tested whether the root was still present; it was.
[INSTALL CLOCKWORKMOD]
I decided to install CyanogenMod as I have heard from friends that have it; and read online about it being one of the more stable custom ROMs available. It has been a while since I last owned an Android device! So, continuing with my theme of treating this device as being an international i9505, I obtained the latest stable release of the jfltexx CM from their website (it was the most recent stable release at the time, may be out of date by the time you get to doing this yourself). Their custom installer app on Windows did not support my phone, so I had to use their guide for manual installation.
Their guide contained steps to installing ClockworkMod Recovery as well as the ROM installation. Following the guide, I installed it without a hitch. When rebooting the phone from ClockworkMod, it prompted me about the fact that the phone may reflash its own recovery tool, but this did not happen. Once again, a success.
[INSTALL CYANOGENMOD]
The last task was to install CM. This was quite an endeavour as I decided to use someone else's Windows 8 laptop (being the only Windows device I had access to at the time) and I forgot how much of a struggle it can be! Again, I used CM's guide to installing 10.2.0 (which by the way is Android 4.3.1, whereas the stock firmware is bloated and heavy at 4.2.2). This went off without a hitch once I reminded myself how the ADT works. I also did as CM suggested and installed the Google Apps pack alongside the ROM.
So, currently this is where I'm at. The device boots and reboots fine. Some users in certain threads had issues with loading 4.4 (KitKat) ROMs or custom ROMs that they didn't allude to the names of, so I don't know if they were having issues with CM or not. There are other threads, but that was the one that kickstarted my attempts to get this all to work. Their issues with the custom ROMs seemed to be related to the 4.4 ROM not recognising the modem of the i9507; I'm not sure why this is but the i9507 was made specifically for Australian/Hong Kong networks so perhaps 4.4 has not been updated yet or something of the like. Anyway, on 4.3.1, or CM 10.2.0, my SMS, calling, and internet are working fine (it displays Virgin Mobile as my carrier). My 4G reception is somewhat iffy in this town (or in particular my house), and the reception seems to be switching between 3G and H so whether that is indicative of 4G not working, I'm not sure. LTE is definitely checked in the settings, however, and my area does have 4G, but my parents' iPhone 5Ss sometimes do not have 4G in this house either. I'll report back tomorrow after having tested the phone for a day to see if the 4G does activate.
As it stands, however, the phone seems to be functioning well. Oddly the Settings report that the phone is an i9505, I assume that's normal as I'm using a ROM for that particular phone!
[CONCLUSION]
So, I hope that anyone who has been looking for a way to remove the carrier/Samsung bloat from their i9507 device will have a good time using the guides I've used. I followed them to the letter and I had no issues.
DISCLAIMER: I had no troubles, but that's not to say you won't either. Please be careful, as you may potentially risk affecting your phone negatively. I'm simply telling you what I did, not giving you a 100% correct and flawless guide that will work no matter what.
Also if you're looking for a 4.4 ROM then you might be out of luck, least till some dev or coder takes notice of this device's existence and helps out to develop a specific way of rooting this phone/installing custom ROMs for this phone. Overall though, it seems to all work fine so perhaps the 4.3.1 CM isn't such a bad thing.
If you try this and want the original firmware back on your phone, use this link or this one. I believe that OPS is the Australian firmware, the other one is for Hong Kong. So, for the second link, HK is Hong Kong, and the one without is for Aus.
If you have any questions, please feel free to ask. I'll post later tomorrow when I've tested the phone for a day to see if it's still working, and to see if the 4G/LTE does actually work. Fingers crossed nothing goes wrong in the meantime!
Click to expand...
Click to collapse
I've had my i-9507 rooted for about a month now with foxhound rom, also on the optus variant.
One thing i've noted is, its next to impossible to update the MODEM for it.
I think because our latest modem for this variant is the one we have stock. And new updates haven't been put in terms of modem specifically for our variant yet.
We should keep this thread stickied for Australian OPTUS GT-i9507 discussion.
OR open up a sub forum for it.

kaiserwatson said:
I'll post later tomorrow when I've tested the phone for a day to see if it's still working, and to see if the 4G/LTE does actually work. Fingers crossed nothing goes wrong in the meantime!
Click to expand...
Click to collapse
Firstly, thank you for creating this complete description of your experiences with customising the i9507.
Secondly, just wanted confirmation that you do now have the pesky "KNOX WARRANTY VOID: 0x1" displayed when your device is in Download mode, right?
Lastly, any updates, issues? All still working, including 4G/LTE?

Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
I do have the Knox 0x1, which I assume means my warranty is void. There's conjecture as to whether that will actually affect warranty for this device in Australia, as I've read up on the Knox system but i think the ACCC would have serious issues with this system actually affecting the warranty. But yes, it would seem my warranty is void, let's hope the phone lasts two years!
I have been able to access 4G, the phone says 4G or LTE, sometimes switching between the two. Again, the reception in the town I'm currently staying in is pisspoor so I can't say for certain whether the antenna/modem is fully functioning to the degree it would be on the stock firmware, but I can definitely access the Optus 4G network.
One issue I did have was that I sent an SMS then immediately turned my screen off, 40 minutes later the message was still 'sending'. I have recreated the same scenario but I haven't been able to get it to happen again, perhaps just a weird tower-side quirk. I know people were having issues with the modem and the phone sleeping but this doesn't seem to be related. Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.

kaiserwatson said:
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
I do have the Knox 0x1, which I assume means my warranty is void. There's conjecture as to whether that will actually affect warranty for this device in Australia, as I've read up on the Knox system but i think the ACCC would have serious issues with this system actually affecting the warranty. But yes, it would seem my warranty is void, let's hope the phone lasts two years!
I have been able to access 4G, the phone says 4G or LTE, sometimes switching between the two. Again, the reception in the town I'm currently staying in is pisspoor so I can't say for certain whether the antenna/modem is fully functioning to the degree it would be on the stock firmware, but I can definitely access the Optus 4G network.
One issue I did have was that I sent an SMS then immediately turned my screen off, 40 minutes later the message was still 'sending'. I have recreated the same scenario but I haven't been able to get it to happen again, perhaps just a weird tower-side quirk. I know people were having issues with the modem and the phone sleeping but this doesn't seem to be related. Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
Click to expand...
Click to collapse
That occurs because the modem signal cuts out after you switch your phone off, or lock it.
This issue can be resolved by updating our modems, but with our current variant we can't update it yet apparently, until the correct new modem for our specific variant has been released.

Hi guys,
I thought I would also post here.
I have the optus 9507 and I tried a couple of different kitkat 4.4 roms. They all worked perfectly except for the fact that they lost data completely as soon as the phone went to sleep. the weird thing is, the phone showed 0 bars but i could take calls just fine, just had data issues.
i tried the slimkat rom and the echoe rom with the same issue
i went back to stock firmware, rooted, ran a debloat script i found on xda, removed a bunch more apps, then unrooted again because i need to run good for enterprise for work.
im getting decent battery life with the debloated stock rom but i would like to move to 4.4 if theres a rom that works. ive been watching the optus and sammobile site hoping there will be a newer modem for the hk version because i think optus will take their time releasing 4.3 for this model.

kaiserwatson said:
Hi all, made an account in anticipation of my night spent mucking around with my new Galaxy S4 i9507. I had been reading about people who have had success and some who have had less success with getting custom ROMs on their devices. None said what methods they used, so I decided to compile together what I did today.
Tonight I have managed to root the device's stock firmware (I have the Australian Optus/Virgin device); install ClockworkMod Recovery on the stock firmware, and then use it to install CyanogenMod 10.2.0 (jfltexx) on the device.
......
Click to expand...
Click to collapse
Thanks for your experience sharing,
I also started with Cyanogen and shared about the same experience.
Just didn't know the Knox thing before I started.. should had read up more before doing it.
So you did the Recovery with Heimdall also? What has made you switch to the customized Rom camp

kaiserwatson said:
Hey sorry its been more than a day, I've been swamped with work, that Christmas time feel.
Click to expand...
Click to collapse
Hey, no worries at all, anyone who works weekends can take all the time they need...
But yes, it would seem my warranty is void, let's hope the phone lasts two years!
Click to expand...
Click to collapse
Yea, I've done some reading also and you're right, it seems to be all conjecture, I really doubt handset warranty refusal can be based on the KNOX Warranty chip. I think the Samsung Enterprise Security Group VP explains it well here.
Overall I'm really happy with how this has all gone. My battery life has been increased by at least 40% and the phone is so much faster. Very pleased.
Click to expand...
Click to collapse
Great to hear, based on this I can ge ahead and 'burn out' my eFuse, happy in the knowledge that my Knox warranty has gone to a good cause. :fingers-crossed:
---------- Post added at 08:49 PM ---------- Previous post was at 08:40 PM ----------
opelcalibra said:
then unrooted again because i need to run good for enterprise for work.
Click to expand...
Click to collapse
I can only assume your "enterprise for work" has nothing to do with KNOX, right? Coz that option would be closed for you now...

CuriosityBrah said:
That occurs because the modem signal cuts out after you switch your phone off, or lock it.
This issue can be resolved by updating our modems, but with our current variant we can't update it yet apparently, until the correct new modem for our specific variant has been released.
Click to expand...
Click to collapse
That odd message not sending was the only issue I've had with this sort of thing; I can still download things, receive messages and calls just fine while my phone is sleeping, how do you know if the modem signal is cutting off? Perhaps it's just a selective thing, not sure. Don't know how to test if it's happening to me because it doesn't seem to be, lol.
opelcalibra said:
I have the optus 9507 and I tried a couple of different kitkat 4.4 roms. They all worked perfectly except for the fact that they lost data completely as soon as the phone went to sleep. the weird thing is, the phone showed 0 bars but i could take calls just fine, just had data issues.
Click to expand...
Click to collapse
Hey mate if you check the forum that I linked to the Knox issue; someone on there posted a fix for sound/WiFi issues post-Knox voiding, maybe that fix'll work for you. Sorry I can't link you to the exact post but it was about 10-20 pages in.
opelcalibra said:
i went back to stock firmware, rooted, ran a debloat script i found on xda, removed a bunch more apps, then unrooted again because i need to run good for enterprise for work.
im getting decent battery life with the debloated stock rom but i would like to move to 4.4 if theres a rom that works. ive been watching the optus and sammobile site hoping there will be a newer modem for the hk version because i think optus will take their time releasing 4.3 for this model.
Click to expand...
Click to collapse
Yeah I reckon they'll take ages, they have pretty much left everyone who's getting this phone in the next couple of months in the dark because of the (as I can tell) severe lack of devs etc in Aus who have Samsung phones and are willing to hack them to the ****. I wish I could help out somehow, but I don't have the time to learn so I figured I'd help out by putting up my experiences. I'm still learning as I go haha.
As for your KitKat problem, I have read that 4.4 didn't do so well in terms of battery life and bloat, what are your reasons for wanting to go to it? I wanted the most recent build also but I figured that if they're still having issues with it then it was better to go with something I knew would work (ie. 4.3.1).
phileasx said:
Thanks for your experience sharing,
I also started with Cyanogen and shared about the same experience.
Just didn't know the Knox thing before I started.. should had read up more before doing it.
So you did the Recovery with Heimdall also? What has made you switch to the customized Rom camp
Click to expand...
Click to collapse
I followed the Windows process on the CM wiki to the letter, so yeah I did the Heimdall also.
Mate legitimately I went from my stock firmware taking up so much space on the hard drive to the real lightweight CM, seeing as I haven't bought a micro SD yet that was a big deal. Also battery life was a major reason for me buying the S4 so to be able to further improve it is just hella.
siganid said:
Hey, no worries at all, anyone who works weekends can take all the time they need...
Yea, I've done some reading also and you're right, it seems to be all conjecture, I really doubt handset warranty refusal can be based on the KNOX Warranty chip. I think the Samsung Enterprise Security Group VP explains it well.Great to hear, based on this I can ge ahead and 'burn out' my eFuse, happy in the knowledge that my Knox warranty has gone to a good cause. :fingers-crossed:
Click to expand...
Click to collapse
In Australia I think we're pretty good. Funny that Samsung and Optus have given us this nice present and it's only a matter of time before someone cracks it open and remains above the warranty voiding
I have read that Knox may be software-based, which would make sense, and maybe it's a matter of time before someone cracks that too. Hehe.
Go ahead, post here if you have any issues and I'll see if I can help you out. What ROM would you be planning on using? A 4.3.x one?

kaiserwatson said:
I followed the Windows process on the CM wiki to the letter, so yeah I did the Heimdall also.
Mate legitimately I went from my stock firmware taking up so much space on the hard drive to the real lightweight CM, seeing as I haven't bought a micro SD yet that was a big deal. Also battery life was a major reason for me buying the S4 so to be able to further improve it is just hella.
Click to expand...
Click to collapse
Welcome to the rom flashing side
After read up more, I realize Odin is a more popular method for Galaxy S4 flashing,
Besides that, Stock rom battery life should also be all right. Samsung did quite some efforts to make the software user friendly.
Anyway, the Bloatware chunk are really irritating have to say.

because i cant keep still i have flashed my phone again lol.
i flashed the official CM 11 (4.4.2) and gapps for kitkat and all is working awesome so far.
no issues with losing signal when going to sleep. seems very fast. right now im happy with it.

Could someone please find new links for the original software posted in the OP?
Links are dead, would be greatly appreciated! =)
Also, Opelcalibra, you have no issues with network/signal on CM 4.4.2 with the Optus i9507?
I better give it a try then lol

RE: Signal issues
Hi,
I also have the AU i9507 Opus S4, I flashed the Omega based 4.4.2 KitKat (i9505 version) and had wifi problems (Greyed out) I tried various fixes and went back to 4.3 based Omega, this had its problems with cell signal being lost when locking the mobile.
I fixed this by going into settings and experimented with mobile networks i.e. Settings, more networks, mobile networks, network mode and tried all 4x options with (for me at least) the GSM ONLY option selected, great rom and worth losing the 4g which is very patchy in my part of Melbourne.
D

Anyone else had any sort of success rooting this phone without tripping Knox.
Also, is it just me, or does it suck pretty hard that we Aussies get stuck with an inferior version of a phone? (Snapdragon 600 in the I9507 vs the 800 in the other international versions)

Update
Hi
Just wondering if anyone has an update on this? Success or otherwise...
One of the main reasons I'm looking to root is to boost volume levels - I find the volume to be way too low. Does anyone know of a way to do that without rooting? Of course I'd like to remove bloatware but could live with it if volume was fixed.
Thanks in advance.

thestuntman80 said:
Anyone else had any sort of success rooting this phone without tripping Knox.
Also, is it just me, or does it suck pretty hard that we Aussies get stuck with an inferior version of a phone? (Snapdragon 600 in the I9507 vs the 800 in the other international versions)
Click to expand...
Click to collapse
Hey bro, no one has cracked without tripping Knox yet because as far as I can tell it's a phone specific fix/hack. So, because our phone is a different and 'rare' model, I doubt that the major heads in the Knox-proofing scene (CF comes to mind) will have the time to make a fix for the knox trip. So for now, either suffer in your jocks (QQ) get a different phone (uh, not likely) or wait for the minute chance that someone actually cares about Aussies )
As for your second point, yeah, it does suck. We get shafted with all sorts of things like prices, release dates, localization...the list goes on. Unfortunately the people who make these ploys know we're desparate and will pay the exorbitant prices anyway :/
jameshef said:
Hi
Just wondering if anyone has an update on this? Success or otherwise...
One of the main reasons I'm looking to root is to boost volume levels - I find the volume to be way too low. Does anyone know of a way to do that without rooting? Of course I'd like to remove bloatware but could live with it if volume was fixed.
Thanks in advance.
Click to expand...
Click to collapse
Hey mate, the rooting was probably the easiest part of the whole situation. You can follow my guide in the OP if you're having trouble. Just be aware about the warranty issues etc because your audio issue may be hardware related rather than software? Is the volume issue in the headphones or the speaker? Some apps may not utilise the phones full volume and also be sure to go into the settings of the phone and make sure the volume limiter is turned OFF. This **** me to tears for the longest time but once I figured out what the issue was, all good!
The only thing I'd say is just make sure its not a hardware issue because you don't want to root your phone, find out that it wasn't a software issue, take your phone into Samsung and have them tell you that your warranty is voided because you rooted. Obviously that's a worse case scenario but just be on the safe side.
I hope I helped you guys!

kaiserwatson said:
Hey mate, the rooting was probably the easiest part of the whole situation. You can follow my guide in the OP if you're having trouble. Just be aware about the warranty issues etc because your audio issue may be hardware related rather than software? Is the volume issue in the headphones or the speaker? Some apps may not utilise the phones full volume and also be sure to go into the settings of the phone and make sure the volume limiter is turned OFF. This **** me to tears for the longest time but once I figured out what the issue was, all good!
The only thing I'd say is just make sure its not a hardware issue because you don't want to root your phone, find out that it wasn't a software issue, take your phone into Samsung and have them tell you that your warranty is voided because you rooted. Obviously that's a worse case scenario but just be on the safe side.
I hope I helped you guys!
Click to expand...
Click to collapse
I'm fairly certain it's a software issue. I've done a fair bit of reading on it and the low volume is a very common complaint about the S4. My volute limiter is turned off - thanks for that tip though!
I'm going to try to root this weekend. I really hope that it works and I don't have any issues with reception dropping when the phone goes to sleep! Feels risky.

I've changed my firmware from Optus to XSA, but am still on 4.2.2, how do I upgrade now?
Kies says I have the latest release.

has anyone got links to newer modem files for this phone? been given one to update it to 4.4, but i know from experience that doing so without at least a 4.4 GSM modem, it wont behave right.
to the people without working wifi after updating: flash the Ktoonz kernel, he has a fix for that.

Hi All,
I recently updated to the new official 4.3 update from optus in order to update my baseband etc.
Then i immediately updated to the i9505 Goldeneye 4.4.2 rom. Ran a ebloat script to get rid of alot of the extras and its running very nicely.
Since updating the modem I get 4g at home which i never did before.
optus rom here
http://www.sammobile.com/firmwares/3/?download=27109
flashed via odin (will lose root and custom recovery). re-root and install recovery after flashing this room.
goldeneye rom here
http://forum.xda-developers.com/showthread.php?t=2313469
obviously this will flag knox, mine was flagged long ao

How to upgrade Note 20 Ultra from...Android 5.1. Seriously.

I need help from someone a lot smarter than me. First time poster, but no stranger to rooting. (If I break some protocol, please correct me, I want to be a good citizen.)
Background (can be skipped)
I bought a Note 20 Ultra 5G (model #SM-N9860F) from a guy for a steal of a deal. Now I know why. Before buying we started it up and made a phone call, so I figured most everything else would be fine. Took it home and started messing with it, only to find it laggy and exhibiting other odd behaviors. So I went to check for updates before loading it up with my stuff.
But there was no Update button. I tapped "Software Info" and the next thing I saw made me read it three times. It showed, "Android version: 5.1."
Issues
So...
The phone functions but with lag and issues. SIM is recognized, then unrecognized. SIM cannot be used for data (though wifi is fine).
Not kidding, Kingo Root says it was able to root this Snapdragon phone. Root Checker Basic confirms it as rooted.
Using all the various key combinations posted all over the Internet, I cannot get into Download mode. I've tried for days.
Rebooting into Recovery shows Chinese options. (After many days of messing with it I finally found a way for it to show the English list...happy to share how I got there if anyone cares.)
The phone does connect to a Windows PC successfully via USB and can share files to internal and external memory.
Interestingly, the 500GB of internal memory only shows a fraction of it as available. Wondering if Android 5.1 just can't recognize that much space.
Bottom line
I am unable to get into Download mode. When I do get to where I think Download mode should be, the green Android guy is lying down with the words "No command" underneath. Therefore I can't use Odin, or a paid service, or Samsung Smart Switch...even tried the old Kies, since it has Android 5.1 on it. ALL of them require me to get into Download mode, and it just won't go.
Plan B?: I've heard repeatedly that rooting a Note 20 Ultra is (nearly?) impossible. Since multiple apps on my device insist I successfully rooted it, I was hoping I could use the TWRP app (it's installed) to flash something that could help. But I don't know what that would be, or if it would help at all. TWRP doesn't recognize the .zip, .tar, or any other files I've found and copied to the device. Maybe it's looking for a .img? I'm just not sure, and I don't even know what to look for.
Additional info
I've attached a few screen shots and photos.
I'd be ever so grateful for anyone's guidance. Again,
How can I get into Download mode? Seems that would get me back on the paths I know better.
And/or what can I flash using TWRP on what appears to be a rooted device? Would that even help?
Thank you!

kbtraveler said:
I need help from someone a lot smarter than me. First time poster, but no stranger to rooting. (If I break some protocol, please correct me, I want to be a good citizen.)
Background (can be skipped)
I bought a Note 20 Ultra 5G (model #SM-N9860F) from a guy for a steal of a deal. Now I know why. Before buying we started it up and made a phone call, so I figured most everything else would be fine. Took it home and started messing with it, only to find it laggy and exhibiting other odd behaviors. So I went to check for updates before loading it up with my stuff.
But there was no Update button. I tapped "Software Info" and the next thing I saw made me read it three times. It showed, "Android version: 5.1."
Issues
So...
The phone functions but with lag and issues. SIM is recognized, then unrecognized. SIM cannot be used for data (though wifi is fine).
Not kidding, Kingo Root says it was able to root this Snapdragon phone. Root Checker Basic confirms it as rooted.
Using all the various key combinations posted all over the Internet, I cannot get into Download mode. I've tried for days.
Rebooting into Recovery shows Chinese options. (After many days of messing with it I finally found a way for it to show the English list...happy to share how I got there if anyone cares.)
The phone does connect to a Windows PC successfully via USB and can share files to internal and external memory.
Interestingly, the 500GB of internal memory only shows a fraction of it as available. Wondering if Android 5.1 just can't recognize that much space.
Bottom line
I am unable to get into Download mode. When I do get to where I think Download mode should be, the green Android guy is lying down with the words "No command" underneath. Therefore I can't use Odin, or a paid service, or Samsung Smart Switch...even tried the old Kies, since it has Android 5.1 on it. ALL of them require me to get into Download mode, and it just won't go.
Plan B?: I've heard repeatedly that rooting a Note 20 Ultra is (nearly?) impossible. Since multiple apps on my device insist I successfully rooted it, I was hoping I could use the TWRP app (it's installed) to flash something that could help. But I don't know what that would be, or if it would help at all. TWRP doesn't recognize the .zip, .tar, or any other files I've found and copied to the device. Maybe it's looking for a .img? I'm just not sure, and I don't even know what to look for.
Additional info
I've attached a few screen shots and photos.
I'd be ever so grateful for anyone's guidance. Again,
How can I get into Download mode? Seems that would get me back on the paths I know better.
And/or what can I flash using TWRP on what appears to be a rooted device? Would that even help?
Thank you!
Click to expand...
Click to collapse
Sounds like you got what you paid for, it's probably a fake Note20 Ultra.
From what I can tell, the model & build numbers conflict, they're from different models of the Note 20 Ultra, that's why I think it's a fake.
Even the model number doesn't look right, it has a hybrid Chinese/European model number........

KOLIOSIS said:
Sounds like you got what you paid for, it's probably a fake Note20 Ultra.
From what I can tell, the model & build numbers conflict, they're from different models of the Note 20 Ultra, that's why I think it's a fake.
Even the model number doesn't look right, it has a hybrid Chinese/European model number........
Click to expand...
Click to collapse
Hi Koliosis,
Yeah, thanks, that has crossed my mind, and that's why I posted those images. If it's fake it's a really good one, but I am aware I could have to chalk that up to experience.
Still, why in the world would a fake have Android 5.1 on it? And it works(-ish)! Isn't that still bizarre? Anything that can be done to force it into Download mode or to flash something with TWRP to at least get an OS from the modern era?
Thanks again...

kbtraveler said:
Hi Koliosis,
Yeah, thanks, that has crossed my mind, and that's why I posted those images. If it's fake it's a really good one, but I am aware I could have to chalk that up to experience.
Still, why in the world would a fake have Android 5.1 on it? And it works(-ish)! Isn't that still bizarre? Anything that can be done to force it into Download mode or to flash something with TWRP to at least get an OS from the modern era?
Thanks again...
Click to expand...
Click to collapse
There should be several threads/tutorials here that show how to flash firmware using Odin (& of course,includes how to get into download mode).
Before you try that out,have you tried to use Samsung's Smart Switch program on your PC?
Given the information you've posted,it's difficult to determine which model you have,which makes matters worse since we don't want to make a bad situation worse.
I'd start with the Samsung Smart Switch, hopefully it'll be able to determine the make of your phone & flashing stock firmware should be a breeze. (If it's indeed a genuine Samsung Device).

KOLIOSIS said:
There should be several threads/tutorials here that show how to flash firmware using Odin (& of course,includes how to get into download mode).
Before you try that out,have you tried to use Samsung's Smart Switch program on your PC?
Given the information you've posted,it's difficult to determine which model you have,which makes matters since we don't want to make a bad situation worse.
I'd start with the Samsung Smart Switch, hopefully it'll be able to determine the make of your phone & flashing stock firmware should be a breeze. (If it's indeed a genuine Samsung Device).
Click to expand...
Click to collapse
Yes sir, and that's my problem. I've rooted and changed ROMs on a dozen devices or more in the past (thanks to XDA!!), always using Odin. But this phone simply will not go into Download mode at all. Using every key combination I can find I either wind up with the Chinese recovery selections I mentioned or I get that "No command" screen with the Android lying on its back.
So far I've tried these PC apps:
Odin (several versions)
Smart Switch
Kies
FixPPO (https://android.imyfone.com/android-issues/android-no-command-error/)
DroidKit (https://www.imobie.com/android-system-recovery/fix-android-no-command-error.htm)
Some, like Odin and the paid options, require Download mode - which isn't working for me - so those apps can even tell I've plugged a phone into the USB port.
Just to put it out there, when the phone is booted into the OS and attach it to the PC, Windows recognizes it's connected but Smart Switch does not. That supports your point that it may not be a Samsung device, but I wondered if it could also have something to do with Smart Switch coming after 5.1 was old.
I just wondered if somebody who didn't know what they were doing somehow downgraded this phone to Android 5.1 before I accept it as a full loss. Still hoping...

kbtraveler said:
Yes sir, and that's my problem. I've rooted and changed ROMs on a dozen devices or more in the past (thanks to XDA!!), always using Odin. But this phone simply will not go into Download mode at all. Using every key combination I can find I either wind up with the Chinese recovery selections I mentioned or I get that "No command" screen with the Android lying on its back.
So far I've tried these PC apps:
Odin (several versions)
Smart Switch
Kies
FixPPO (https://android.imyfone.com/android-issues/android-no-command-error/)
DroidKit (https://www.imobie.com/android-system-recovery/fix-android-no-command-error.htm)
Some, like Odin and the paid options, require Download mode - which isn't working for me - so those apps can even tell I've plugged a phone into the USB port.
Just to put it out there, when the phone is booted into the OS and attach it to the PC, Windows recognizes it's connected but Smart Switch does not. That supports your point that it may not be a Samsung device, but I wondered if it could also have something to do with Smart Switch coming after 5.1 was old.
I just wondered if somebody who didn't know what they were doing somehow downgraded this phone to Android 5.1 before I accept it as a full loss. Still hoping...
Click to expand...
Click to collapse
Makes since you tried Kies (given the stated Android version).
Can you download/sideload any apps that may help identify the phone (& check for Knox 0x0) such as this one:
Phone INFO+ (SAM) - Apps on Google Play
All-in-one INFO and TOOLS for Samsung devices.
play.google.com
AIDA64 - Apps on Google Play
Hardware and software information utility for Android devices
play.google.com
I wish I had more to offer,it's been years since I've dealt w/a rooted Samsung (Note 5).
Hopefully,others will chime in & offer a solution.
FWIW,Definitely following this thread, I'm interested in how things work out, hopefully for the better.

Aah i made an account just to respond to you
i had an iPhone 7 Jet Black replica with android 5.1 once upon a time, same symptoms- 8GB actual storage but will show 128GB when connected to PC
So here are my two cents: These devices won't be recognized by samsung tools as they are not having motherboards made by samsung. I would recommend that you check actual specs from AIDA64 and you will find out which company has made the motherboard or device, mine had strange MediaTek processor though. And hopefully you will find some chinese websites where people are talking about how to flash firmwares in these phones but i recommend not to do that, i had to lose my device as it got bricked.

Well, that's exactly why I come here. I'd never come across that AIDA64 app, and I've attached screen shots. I've never heard of a "Kirin," but sure enough, it's Huawei. Dang it!
@priteshsolanki, hate to hear about your experience. Thanks for the heads up.
So...does Huawei have a Smart Switch equivalent, lol? And by the way, even if I got this working, would Huawei have enough hardware in this bugger to be able to listen in and send data back to Mother China?? I don't know how that kind of thing works...

kbtraveler said:
Well, that's exactly why I come here. I'd never come across that AIDA64 app, and I've attached screen shots. I've never heard of a "Kirin," but sure enough, it's Huawei. Dang it!
@priteshsolanki, hate to hear about your experience. Thanks for the heads up.
So...does Huawei have a Smart Switch equivalent, lol? And by the way, even if I got this working, would Huawei have enough hardware in this bugger to be able to listen in and send data back to Mother China?? I don't know how that kind of thing works...
Click to expand...
Click to collapse
This is strange, i think The AIDA64 app is being fooled here too! To find which company has made it, Its gonna be same experience as finding father of an orphan child which just had permanent memory loss
Its not Kirin, its not huawei.. why?-
So its showing ARMv7 32bit processor, which is definitely not Kirin 1020. because kirin 1020 is a high end processor itself too and uses 5nm technology and Cortex A78 architecture! (While yours is showing stone age 28nm with Cortex A7)
Then there is Platform MT6799. When i look up for that, its again showing totally different company- MediaTek chipset "Helio X30 (MT6799)" which is a deca core processor but what we got here in your details is a Quad core processor.
What we know about your processor:
- its Cortex A7 @1301 MHz and has 28nm manufacturing process
(can't be 5G at any cost)
- From above details it seems like an ancient processor which came out somewhere around 2012, probably thats why its running 5.1.
- The performance is equivalent to high end Android Jellybean device, but definitely not suitable for using in 2022
- The storage and RAM amount shown there are just to fulfill fantasies, dont expect it to be reliable. Its probably a 1 or 2GB Ram with 4 or 8GB storage.
- The software in the phone is really fantastic, i have never thought that a clone can be so perfect that even Apps like AIDA64 will have a hard time finding the facts!
Now coming to the main questions:
1) Can it be upgraded?
90% no based on research i have done in google, this phone is totally non existent for google. for remaining 10% you can expect the rom maker to contact you in DMs after seeing your thread here and offer you an upgrade lol
2) Should you use any file syncing tools with it?
Quick answer: Syncios app is your best bet to sync data between phone and back, but only luck can help you find actual firmware of the device
Slightly long answer: So according to our findings all these data shown in phone settings fake, and syncing apps back in 2011-12 i think its going to give you hard time finding a working one. Android 5.1 in todays time is not something you should be using as daily driver for sure. I suggest you to just treat it like a toy.
About my iPhone 7 back in the day, i bought that one for some 60USD but it was worth it, had some kind of apple music app which never required login but was able to stream any songs for free. so ive used that one out for music only.
I really wish there was a better way to put it, but you can try one last dry hope at needrom website to see if they have any details about this device.

kbtraveler said:
But there was no Update button. I tapped "Software Info" and the next thing I saw made me read it three times. It showed, "Android version: 5.1."
Click to expand...
Click to collapse
Like has been said, sounds like you got a fake, Software info is one of the first things I would have checked before buying, not after you have bought it and then start having issues. Unfortunately you only really have yourself to blame. like is quite often said if the deal "seems to good to be true" there are reasons why.

@samorgs60, you are very right. I've taken many chances like this one on many electronic devices, and to my recollection, this is the first time I got burned. It's kind of like speeding: I don't always obey the speed limit to the letter (number?), so in the past when I got what I believe was an unfair speeding ticket - I was accused of going faster than I was - I dealt with it my accepting it as a balance in the universe for all the times I should have been busted.
@priteshsolanki, what a catch! Wow. That is kinda amazing, and would explain why it has 5.1 on it. I'm actually astonished at the quality of the device in every way, other than the obvious.
So I hate to ask this, but...isn't it true that carriers (I won't mention mine by name here) make offers for value against a new phone if your current phone simply 1) turns on and 2) does not have a cracked screen? That kinda seems to describe what I've got right now. Not interested in misleading on purpose, but what is the likelihood this would qualify as a trade-in? If they took it initially, what's the likelihood of it coming back to haunt me (the carrier contacting me about it not being a Samsung)?
Really appreciate the help, guys!

It sucks that you got a fake. If you paid with PayPal or Credit, I'd file a claim/dispute and try to return for a refund. Carriers usually log the IMEI of trade ins and if it doesn't match the model or is blacklisted in any way, the trade will be denied.