[Q] Is The ACE GT-S5830T same as GT-S5830? - Galaxy Ace S5830 Q&A, Help & Troubleshooting

Hi Guys
I have a Telstra (australian version for a 850MHZ HSDPA version of the same phone.
I've tried every single method of rooting the phone, but the all seem to fail. I wonder if this is because I have a slightly different phone?
Details from my phone are as follows:
Model Number: GT-S5830T
Android Version 2.3.4
Baseband version: S5830TDVKQ3
Kernel version: [email protected]#1
Build number: Gingerbread.DVKQ3
Sorry if this is a stupid question... maybe I have missed something simple

What are the hardware specs on it? Are you given that information?

Well i think it might be diff, mine is GT-S5830B and i had some issues flashing ROM's for S5830. But about the root method, SuperOneClick worked just fine for me.

Sorry, The specs are identical to the GT-S5830B i.e. GSM 850,900,1800, 2100 and UMTS:850 and 2100.
The problem is when I use a root method intended for the S5830B, it says Installing from SD card complete, but then whenever I try to use a program that requires root, or test the root functionality using an app, I get a message saying I don't have root persmissions. (Although I do see a super user icon in my regular phone menu)
Does it make a difference if i'm seeing the following message when entereing recovery mode: applying Multi CSC
Can't access to '/system/csc/TLP/system?
Maybe I have stuffed something up?

Hi, I couldn't find the solution anywhere here aswell but after a quick look inside the rooting package i found the solution to be very easy.
- Unzip the upd_1 package and navigate to \META-INF\com\google\android.
- Open the updater_script file with notepad (i used notepad++) .
- At the very top you will see a list of devices. Add these two lines to the list (i added directly after the first two lines):
Code:
getprop("ro.product.device") == "GT-S5830T"
getprop("ro.build.product") == "GT-S5830T"
If you're new to scripting just make sure it looks the same as the rest of the list. Save the file.
- Then re-zip the package and flash as per usual. too easy.
First post BTW

jetpants said:
Hi, I couldn't find the solution anywhere here aswell but after a quick look inside the rooting package i found the solution to be very easy.
- Unzip the upd_1 package and navigate to \META-INF\com\google\android.
- Open the updater_script file with notepad (i used notepad++) .
- At the very top you will see a list of devices. Add these two lines to the list (i added directly after the first two lines):
Code:
(getprop("ro.product.device") == "GT-S5830T"
getprop("ro.build.product") == "GT-S5830T"
If you're new to scripting just make sure it looks the same as the rest of the list. Save the file.
- Then re-zip the package and flash as per usual. too easy.
First post BTW
Click to expand...
Click to collapse
@Jetpants - where do you buy your clothes?
The future I have been waiting for is here.
Have you got rocket boots too?
Sent from a phone with an app.

sdotmouse said:
@Jetpants - where do you buy your clothes?
The future I have been waiting for is here.
Have you got rocket boots too?
Sent from a phone with an app.
Click to expand...
Click to collapse
No need for rocket boots when you've already got the pants!

jetpants said:
Hi, I couldn't find the solution anywhere here aswell but after a quick look inside the rooting package i found the solution to be very easy.
- Unzip the upd_1 package and navigate to \META-INF\com\google\android.
- Open the updater_script file with notepad (i used notepad++) .
- At the very top you will see a list of devices. Add these two lines to the list (i added directly after the first two lines):
Code:
getprop("ro.product.device") == "GT-S5830T"
getprop("ro.build.product") == "GT-S5830T"
If you're new to scripting just make sure it looks the same as the rest of the list. Save the file.
- Then re-zip the package and flash as per usual. too easy.
First post BTW
Click to expand...
Click to collapse
hi.
thanks, but i am past this step. Without this, it wouldn't even apply the package.
With this fix, the package installs, but it still doesn't root the phone. Can you please do me a favour and boot into recovery mode, and see if you get the same message as I do down the bottom?
I think when I unlocked (service provider) the phone by using Omnius, it did something it isn't supposed to...

Yep, no weird errors, worked flawlessly. Being a noob i followed the tute in the sticky (how to upgrade, root, flash... etc) step by step except for adding the model# script.
No probs at all. Hope you get yours sorted.

Anyone have any ideas at all?
Is there any way to undo what Omnius may have done during unlocking?

The first time i sucessed on root was using an apk for rooting the phone, doesnt remember the name =/

Have u tried lastest ver of SOC (2.2) to root your SGA?

Don't know if you've solved your problem, but for anyone else out there with the Telstra 5830T version on 2.3.4, the error message you got when booting into recovery mode is normal for this phone, and I couldn't root it with this zip file either, even after the script edit.
It appears to work, but root access isn't granted.
I found the latest version of Super One Click worked, but I had to manually install superuser.

my fingers are crossed
unkit said:
Hi Guys
I have a Telstra (australian version for a 850MHZ HSDPA version of the same phone.
I've tried every single method of rooting the phone, but the all seem to fail. I wonder if this is because I have a slightly different phone?
Details from my phone are as follows:
Model Number: GT-S5830T
Android Version 2.3.4
Baseband version: S5830TDVKQ3
Kernel version: [email protected]#1
Build number: Gingerbread.DVKQ3
Sorry if this is a stupid question... maybe I have missed something simple
Click to expand...
Click to collapse
Did You by any chance manage to root your ace

tigerhotstone said:
Did You by any chance manage to root your ace
Click to expand...
Click to collapse
Are these phones by chance purchased from Telstra in Australia?

yes
johnny893 said:
Are these phones by chance purchased from Telstra in Australia?
Click to expand...
Click to collapse
Yes mine certainly is

Yeah, it is just an S5830. Check under the battery to double check.
Sent from my GT-S5830 using xda premium

same issue with S5830T
Hi unkit,
got EXACTLY the same problem ... sorry , but no solution (YET ??).
My phone is EXACLY same as yours .... build, firmware etc..etc..
I didnt need to modify any scripts .... but get same errors as you.
Surely there is SOMEONE out there who can root this phone.

got aceT but mine does not have problem with rooting it...mine just upgrade to 2.3.6 and then root it

BREKEL _ did u successfully root the s5830T
brekel said:
Don't know if you've solved your problem, but for anyone else out there with the Telstra 5830T version on 2.3.4, the error message you got when booting into recovery mode is normal for this phone, and I couldn't root it with this zip file either, even after the script edit.
It appears to work, but root access isn't granted.
I found the latest version of Super One Click worked, but I had to manually install superuser.
Click to expand...
Click to collapse
Hi Brekel,
Are u saying u actually DID root an S5830T on 2.3.4. using SuperOneClick... Could you confirm the firmware build - was it DVKQ3 or something else....
I used SuperOneClick v2.3.3 with no success.
Could u detail how to manually install superuser??
---------- Post added at 08:41 PM ---------- Previous post was at 08:37 PM ----------
johnny893 said:
Are these phones by chance purchased from Telstra in Australia?
Click to expand...
Click to collapse
Hi Johnny893,
Mine is as well.... any particular eason you ask >>>
Hopefully, we are getting closer to a solution....

Related

[TUT] Flash baseband and ONLY baseband

This will do nothing other than changing your baseband, nothing else will change and you can do it with whatever ROM you have installed, custom or stock.
1. Get the latest ROM for your region, the simplest way to do that is to use CheckFusDownloader which you can find here: http://fus.nanzen.se/
Start the program and choose firmware, phone (GT-S5570) and region on the right side, then click check firmware on the left side, finally click download and save it to c:\baseband.
2. Get Cygwin here: http://www.cygwin.com/
Install Cygwin (you don't need to change anything if you don't want to, just let setup run it's course until it's installed) and start the Cygwin terminal.
In cygwin, type:
Code:
cd /cygdrive/c/baseband
tar -xvf [filename of your downloaded ROM] amss
tar -H ustar -c amss > MODEM_S5570.tar
For example, if the filename of the ROM you downloaded with CheckFusDownloader is S5570XWKQG_S5570XWKQ5_S5570OXFKQ6_HOME.tar.md5 then you'd type:
Code:
cd /cygdrive/c/baseband
tar -xvf S5570XWKQG_S5570XWKQ5_S5570OXFKQ6_HOME.tar.md5 amss
tar -H ustar -c amss > MODEM_S5570.tar
Once you're done with that you have a baseband file in your C:\baseband directory called MODEM_S5570.tar that you can flash as one package using Odin.
Remember that basebands are intercompatible so just pick the one that is for your region.
And no, no custom rom will care about it regardless of what they say.
Hi
this seems cool trick but to what I understand it gets the baseband out from a downloaded firmware (please correct me if wrong)
Would it be possible to just extract the basesband from the phone?
thanks
Sorry sir I don't get it
Is this just change the baseband I mean just the appearance In about phone or change the system too?
Sent from my GT-S5570
droidface said:
Sorry sir I don't get it
Is this just change the baseband I mean just the appearance In about phone or change the system too?
Sent from my GT-S5570
Click to expand...
Click to collapse
the baseband countains file connected to your phone radio in which you get your phone signal and bluetooth and wifi stuff i may be wrong....!!!
Worked like a charm..
droidface said:
Sorry sir I don't get it
Is this just change the baseband I mean just the appearance In about phone or change the system too?
Sent from my GT-S5570
Click to expand...
Click to collapse
No, it will change the baseband in the phone as in replace your current baseband.
The baseband controls GSM/GPRS/G3/GPS settings which means that if you flash a ROM for another region than your own you might run into problems with all or some of those. For example, i can't remember how many posts i have read on this forum about GPS problems when people have flashed a ROM that isn't for their region.
You can use this procedure to fix that problem, just flash the baseband for your region and it will work fine on ANY ROM, custom or stock.
Basically, it's a universal fix to a problem that some people have.
kitrax59 said:
Worked like a charm..
Click to expand...
Click to collapse
Great, always good to get feedback.
TBH i mostly posted this thread because it was tiresome to repeat it, now i can just link them here.
so from as per the details above I assume we cannot extract the baseband from the phone?
jdwis said:
so from as per the details above I assume we cannot extract the baseband from the phone?
Click to expand...
Click to collapse
Nope, you'd need the block area on the phone where it's stored and dd it.
this is for flashing basebands on roms available and if your rom isn't it's because it's old, just use the checkfusdownloader to get the most recent and you'll be fine with that.
I thought i made it all clear in the first post.
Jinxxed said:
Nope, you'd need the block area on the phone where it's stored and dd it.
this is for flashing basebands on roms available and if your rom isn't it's because it's old, just use the checkfusdownloader to get the most recent and you'll be fine with that.
I thought i made it all clear in the first post.
Click to expand...
Click to collapse
I am sure you must have made it clear, only may b I did not understand clearly, and sorry I still do not get this how to do it.
Lets say I got the brand new phone and nothing has been modified, how do I take the baseband out from the PHONE for future use in case if I need to restore the baseband in future.
So anyways, if it is possbile to get it out of the PHONE, please explain it in details how do I do it, sorry I am quite new to this thats why.
thanks my friend.
jdwis said:
I am sure you must have made it clear, only may b I did not understand clearly, and sorry I still do not get this how to do it.
Lets say I got the brand new phone and nothing has been modified, how do I take the baseband out from the PHONE for future use in case if I need to restore the baseband in future.
So anyways, if it is possbile to get it out of the PHONE, please explain it in details how do I do it, sorry I am quite new to this thats why.
thanks my friend.
Click to expand...
Click to collapse
You don't, you download the latest ROM for your region with checkfusdownloader and use the rest to get whatever baseband you want INTO the phone.
If you already have the correct baseband for your region, why would you change it, if you have the wrong one, you replace it using the method in the OP.
It is possible, but i am not going to spend the time researching blocks to find it, so either you do that yourself for no reason what so ever, or you go with another amss from the same rom that you have which IS THE SAME BASEBAND.
It's not phone unique, it's unique to every region and you can find it or an updated version using the tool i referenced in the OP, if you cannot, your phone doesn't exist or at least Samsung haven't produced that phone.
I am not sure how to make this any more clear than that.
Jinxxed said:
You don't, you download the latest ROM for your region with checkfusdownloader and use the rest to get whatever baseband you want INTO the phone.
If you already have the correct baseband for your region, why would you change it, if you have the wrong one, you replace it using the method in the OP.
It is possible, but i am not going to spend the time researching blocks to find it, so either you do that yourself for no reason what so ever, or you go with another amss from the same rom that you have which IS THE SAME BASEBAND.
It's not phone unique, it's unique to every region and you can find it or an updated version using the tool i referenced in the OP, if you cannot, your phone doesn't exist or at least Samsung haven't produced that phone.
I am not sure how to make this any more clear than that.
Click to expand...
Click to collapse
Now it is quite clear to me, thanks.
The only reason I wanted to get one out from my phone was that, the things seem quite ok with the phone so my baseband is quite ok, but in other rom (for my region) if it is an updated one and if there are some better features or removed bugs (unknown to me) then I would install it through your method. But after installing new one if I find that my old baseband was working better than this new one, I would not have chance to put the old one back. So was the reason to backup the baseband from the phone just in case new one does not work good for me.
But as you have made it understood quite clear, thanks for this, really appreciated your help.
jdwis said:
Now it is quite clear to me, thanks.
The only reason I wanted to get one out from my phone was that, the things seem quite ok with the phone so my baseband is quite ok, but in other rom (for my region) if it is an updated one and if there are some better features or removed bugs (unknown to me) then I would install it through your method. But after installing new one if I find that my old baseband was working better than this new one, I would not have chance to put the old one back. So was the reason to backup the baseband from the phone just in case new one does not work good for me.
But as you have made it understood quite clear, thanks for this, really appreciated your help.
Click to expand...
Click to collapse
Ok, the point of this thread was to provide the TOOL (checkfusdownloader) and the WAY(the explained extraction and compilation of one file that will work.
I still don't get why you don't just use that information.
You CAN use even old basebands found via checkfusdownloader.
If you don't get how to use it, just say so because this seems a bit... puckered with nada.
WELL done Jinxxed I will try it right now.
but i have a query, suppose that i have the suitable firmware for my device, can i just extract the csc file from the package and grab the ops file, then load and flash them via odin?
abdovar said:
WELL done Jinxxed I will try it right now.
but i have a query, suppose that i have the suitable firmware for my device, can i just extract the csc file from the package and grab the ops file, then load and flash them via odin?
Click to expand...
Click to collapse
Wait, why would you flash the CSC, this tutorial is for flashing baebadn without ANYTHING else affected.
And that is what the procedure does, it just changes your baseband without chanign ganything else.
You can pretty much flash any file this way, including recovery or what have you.
So yeah, whatever firmware you want, with whatever baseband you need, this is how you do it.
abdovar said:
WELL done Jinxxed I will try it right now.
but i have a query, suppose that i have the suitable firmware for my device, can i just extract the csc file from the package and grab the ops file, then load and flash them via odin?
Click to expand...
Click to collapse
To answer this as the question is in need of answer.
Yes, you can do that with any rom file in any way you wish except for the boot, img and the arm11 file, just don't mess with those.
If yo REALLY want to, i can tell you how but at that point you'll want more than one phone per person.
my bad I mean the amss file that contains baseband and related stuff
since you had gently answered that is doable via ODIN, so what about the ops file should i leave it as he is.
sorry to bother you mate, and thanks again
abdovar said:
my bad I mean the amss file that contains baseband and related stuff
since you had gently answered that is doable via ODIN, so what about the ops file should i leave it as he is.
sorry to bother you mate, and thanks again
Click to expand...
Click to collapse
My wife died tonight.
YOu can use the regular way of flashing it or just electing out one part in the tass and flash it.
Now everyone will be wary of it because i made a mistake.. .it's not really a problem, you just comment out the line you won't use. i'll bet my left ball on that.
That said, i've experienced a lot lately, so bear with me if i'm slow but expect everything exactly correct.
I'm going to be offline for a while now, my wife died today.
Jinxxed said:
My wife died tonight.
YOu can use the regular way of flashing it or just electing out one part in the tass and flash it.
Now everyone will be wary of it because i made a mistake.. .it's not really a problem, you just comment out the line you won't use. i'll bet my left ball on that.
That said, i've experienced a lot lately, so bear with me if i'm slow but expect everything exactly correct.
I'm going to be offline for a while now, my wife died today.
Click to expand...
Click to collapse
my condolences sir..
For those who have trouble understanding the instructions, I have extracted a few baseband's myself.. (tried and tested)
KPD: http://www.mediafire.com/?m9m9if910u1db1h
KTH: http://www.mediafire.com/?khl8ewdm9zothkt
KQ7: http://www.mediafire.com/?2ncxyf1r1bbb5ey
Flash via Odin as one package with the normal ops, the same ops file that we have been using to flash stock ROMs, in Download mode as always.. now, only do this if you already have a custom ROM.. It will not wipe any data but it is recommended to do a nandroid backup just in case something goes wrong.. Check About Phone, Baseband Version to see the changes..
question
if i have 2.3.6 xwktn, can i use 2.3.6 dxkpd as my baseband? thanks.

p970g android 2.3.4 v20j root help

i recently bought a p970g from koodo android 2.3.4 with v20j firmware ..im a total newb at this and searched to no avail on how to get it rooted.... superone click hangs at root 7 stage ..unlock root can't find shell root .....lg drivers are installed sucessfully... tried cw method but that tutorial isnt for newbs and not too detailed ..can someone simplify it for me..or in other words spell it out and direct links to the exact downloads i need ..much appreciated thanks
Hi jaynjolie
Enter here search the download page and download UPK 3.7
inside that zip file you will find BlackJack then follow the instruccions to root your phone, it's really easy
Afaik blackjack doesn't work on GB firmware
FDN
do it work or not please? can someone verify this phone and be rooted and still work with koodo Canada provider? thank you
fw version doesn't matter, and blackjack won't work. you have to flash binary files with smartflash. later, you can easily update your apn config file with this. but before all, be sure that you've tried all known methodds correctly (superoneclick, unlockroot, esteem...)
Ilko said:
fw version doesn't matter, and blackjack won't work. you have to flash binary files with smartflash. later, you can easily update your apn config file
what would the best firmware to use on that model phone in canada ..and is that firmware root ready or already rooted? how difficult is it to flash into my phone ..also will i be able to save my original flash in case i need it? ..will i be able to reinstall it in case of brick or non working apn...i really want root so i can get rid of factory preinstalled junk ..my phone is constanstly running on low ram cause of apps i'll never use.....i have upk 3.7 with smartflash ...and link to a rom or bin would be awesum thanks
Click to expand...
Click to collapse
Apn for koodo
Apn = sp.koodo.com
Proxy = 74.49.0.18
Port = 80
I have the koodo fw in bin/fls format with cwm already injected so you'd just have to use smartflash to get it on your phone, then reboot into recovery and flash superuser to gain root access. Let me know or try the cwm inject method yourself. You can get the koodo branded fw at http://lg-phone-firmware.com/index.php?id_mod=1
Sent from my LG-P970g using XDA
jdayscokn said:
Apn for koodo
Apn = sp.koodo.com
Proxy = 74.49.0.18
Port = 80
I have the koodo fw in bin/fls format with cwm already injected so you'd just have to use smartflash to get it on your phone, then reboot into recovery and flash superuser to gain root access. Let me know or try the cwm inject method yourself. You can get the koodo branded fw at
Sent from my LG-P970g using XDA
Click to expand...
Click to collapse
sure would love to have that firmware ..would you provide the link or you can pm me if you don't prefer to upload it ? and do i need to enter the apn myself or is it not needed on your firmware? thanks
smartflash will erase everything, so backup all saveable things. CWM will let you to do backups after having flashed. A specific branded fw is not necessary, unless if it's your aim. this way you'll avoid additional apps included by the operator, but they're also downloadable on store maybe ?
erasing eveverything isnt a big deal ..my phone is a week old and only a few contacts to add ...im not concerned about that... i just want to install the best firmware compatable with my device with the cwm already added so i can flash it with smartflash ..so it is easier for me ...im very new to phone modification ..but im not bad with computers...what FW is recommended .....thanks for your responses
lean7 said:
Hi jaynjolie
Enter here search the download page and download UPK 3.7
Click to expand...
Click to collapse
note : it contains pdf guides. But I advice you to read the thread to inform yourself at least. you'll get some basics.
Ilko said:
note : it contains pdf guides. But I advice you to read the thread to inform yourself at least. you'll get some basics.
Click to expand...
Click to collapse
i see the v20o patched says deu ..will that still work with a canadIAN PROVIDER and its injected with touch my phone is p970g
?thanks for your help
no problem, it's only the default language of the fw. it should detect your network's language and switch automatically at first boot when the wizard is launched. if not, just change it in settings.
Ilko said:
no problem, it's only the default language of the fw. it should detect your network's language and switch automatically at first boot when the wizard is launched. if not, just change it in settings.
Click to expand...
Click to collapse
thanks a million will give it a whirl tommorrow after work ....hopin and praying ...much appreciated .
also, take a look at general section. there is a lot of infos about few things, tuts etc... good luck
successfully upgraded to v20o ..prone works no prob ...cant get into recovery mode with V- when powering up ...please info on what to do thanks
Download terminal emulater from market and type reboot recovery
Or download Rom manager and select reboot recovery in app
Sent from my LG-P970g using XDA
All's great love my new phone. Thanks everyone for their help for my rooted phone
since rooting with v20o signal strength seems lower
seems that after sucessfull root and reflash from v20j to v20o..the signal strength is always goin from 1 bar to 4 and sometimes unable to get signal any suggestions? or is this a isolated case thanks
I had the same issue with my telus p970. When i reflash stock telus fw I have perfect signal no idea why and no one seems to have an answer
Sent from my LG-P970g using XDA

[FIX][i9300][26/10/2013]Camera stopped working, error on Samsung based ROMs

I want to offer you a little fix for those of you who actually experience this problem. On some Samsung based ROMs, some people complain about not working cameras, no matter how often they tried to install a ROM after several wipes. This error may occur in case your camera uses a different firmware.
Most people however won´t experience this error.
I´ve created a little Fix which is actually very easy to apply as a flashable zip. It was intended to be used with my Samsung Galaxy S3 ROM, it may also work with every other Samsung based ROM
Here is the link: Camera Fix for Samsung based ROMs
Simply install this file through your custom recovery
Just in case this patch should not work for everyone, leave me a comment and I´ll see what I can do :angel:
What does it do?
Sent from my CM10.3 Galaxy S3.
This fix includes one missing binary which some specific cameras require in order to be able to be used.
If you don´t have any trouble starting the camera app, using the camera, you don´t need to flash this zip Even if everything works fine and you do install this fix, it wouldn´t harm your system
habylab said:
What does it do?
Sent from my CM10.3 Galaxy S3.
Click to expand...
Click to collapse
just flashed it, doesn`t work for me unfortunately. :crying: :crying: :crying:
i have this problem you told of since a very long time and i really can't get rid of it. makes me fckn sick. i could cry on and on.
what else is possible to do? every litte hint is very much appreciated.
There are more binaries available, the one I included is a more common one. Samsung uses 2 different cameras ( Sony or Samsung ).
Does your camera work 100% with a Stock ROM ? If so, have a closer look in /data/cfw and show me what you find inside ( eg. SlimISP_xx.bin ).
Flash a Stock Firmware, make sure to copy the file and add it here as a zip file. By installing custom ROMs, your cfw folder will be empty most the time if these files are not added by the ROM itself.
g.ott said:
just flashed it, doesn`t work for me unfortunately. :crying: :crying: :crying:
i have this problem you told of since a very long time and i really can't get rid of it. makes me fckn sick. i could cry on and on.
what else is possible to do? every litte hint is very much appreciated.
Click to expand...
Click to collapse
If that fix not help you can maybe make a camera fw upgrade.
[tapatalk]printed, scanned and faxed...[/tapatalk]
hi guys,
thx a lot for your words. here is what i've done:
i just flashed a stock rom and the camera works. then i installed cf root and root explorer but /data/cfw is an empty folder. so i can`t copy anything here.
with the custom rom and the cam not working i had a file like SlimlSp00.bin (or something similar) in this particular folder but not now.
what to do now or did i misunderstand something?
Gorgtech said:
There are more binaries available, the one I included is a more common one. Samsung uses 2 different cameras ( Sony or Samsung ).
Does your camera work 100% with a Stock ROM ? If so, have a closer look in /data/cfw and show me what you find inside ( eg. SlimISP_xx.bin ).
Flash a Stock Firmware, make sure to copy the file and add it here as a zip file. By installing custom ROMs, your cfw folder will be empty most the time if these files are not added by the ROM itself.
Click to expand...
Click to collapse
Just out of curiosity, did you try to remove this file ? Maybe your camera tries to load this binary though it´s not suitable for your model. You can try to create a different folder and first copy the found bin ( just to have a spare copy ), remove SlimlSpxxx out of your data/cfw folder.
Wipe your Dalvik Cache and restart the ROM
g.ott said:
hi guys,
thx a lot for your words. here is what i've done:
i just flashed a stock rom and the camera works. then i installed cf root and root explorer but /data/cfw is an empty folder. so i can`t copy anything here.
with the custom rom and the cam not working i had a file like SlimlSp00.bin (or something similar) in this particular folder but not now.
what to do now or did i misunderstand something?
Click to expand...
Click to collapse
this idea didn't come up of course
but i just tested it. i already had my custom rom backup restored. i moved the SlimlSP_BH.bin to my ext sd, so that /data/cfw was empty, rebooted to recovery, wiped dalvik and it doesn't worked. second try i wiped cache and dalvik and it also doesn`t work.
Gorgtech said:
Just out of curiosity, did you try to remove this file ? Maybe your camera tries to load this binary though it´s not suitable for your model. You can try to create a different folder and first copy the found bin ( just to have a spare copy ), remove SlimlSpxxx out of your data/cfw folder.
Wipe your Dalvik Cache and restart the ROM
Click to expand...
Click to collapse
If your camera doesn´t work with this binary, you may need another one..and there are lots of them to try but you have to chose one which is suitable for a Sony or a Samsung camera Well, there is a easier way out if you try to upgrade your camera firmware.
Before we proceed, I need some details first, which type of camera you have in order to pick up a suitable binary.
1) Dial *#34971539#
2) pick up this option: "Phone/Cam FW Check"
3) Show me what you see
4) Chose this option: "Phone/Cam FW Write"
A short explanation :
GDxxx = Sony
ZFxxx = Samsung
g.ott said:
this idea didn't come up of course
but i just tested it. i already had my custom rom backup restored. i moved the SlimlSP_BH.bin to my ext sd, so that /data/cfw was empty, rebooted to recovery, wiped dalvik and it doesn't worked. second try i wiped cache and dalvik and it also doesn`t work.
Click to expand...
Click to collapse
alright, i for sure will give you every information you need.
under "phone/cam fw ver check" i see
rear camera
cam fw ver: GDF
phone fw ver: GDFI02
front camera
cam&phone fw ver: S5K6A3
"Phone/Cam FW Write" isn't available in that form. options with "write" are only "phone to cam fw write (rear)" (but this is greyed out so i can't touch it) and "fw write count".
Gorgtech said:
If your camera doesn´t work with this binary, you may need another one..and there are lots of them to try but you have to chose one which is suitable for a Sony or a Samsung camera Well, there is a easier way out if you try to upgrade your camera firmware.
Before we proceed, I need some details first, which type of camera you have in order to pick up a suitable binary.
1) Dial *#34971539#
2) pick up this option: "Phone/Cam FW Check"
3) Show me what you see
4) Chose this option: "Phone/Cam FW Write"
A short explanation :
GDxxx = Sony
ZFxxx = Samsung
Click to expand...
Click to collapse
hi gorgtech, are you still here?
I´m still here but I´m not quite sure how to help you out. There is another way to enforce an upgrade of your Firmware but I´m not sure if this would work out for everyone.
I´ll see what I can do later and prepare a zip file for you
g.ott said:
hi gorgtech, are you still here?
Click to expand...
Click to collapse
Gorgtech said:
I want to offer you a little fix for those of you who actually experience this problem. On some Samsung based ROMs, some people complain about not working cameras, no matter how often they tried to install a ROM after several wipes. This error may occur in case your camera uses a different firmware.
Most people however won´t experience this error.
I´ve created a little Fix which is actually very easy to apply as a flashable zip. It was intended to be used with my Samsung Galaxy S3 ROM, it may also work with every other Samsung based ROM
Here is the link: Camera Fix for Samsung based ROMs
Simply install this file through your custom recovery
Just in case this patch should not work for everyone, leave me a comment and I´ll see what I can do :angel:
Click to expand...
Click to collapse
about time someone done this! thanks! i thought i corrupted the drivers, but thats for the fix!
Dude, brilliant, this works on KitKat roms also, I have spread the word and linked your thread to the benefit of all.
Thank you
Sent from my GT-I9300
does this really work? can someone add it to aosp code then? @XpLoDWilD @CarbonDev
ayoubij said:
does this really work? can someone add it to aosp code then? @XpLoDWilD @CarbonDev
Click to expand...
Click to collapse
Well it works perfectly for me, but @Moster2 says the md5 checksum is identical to the files already in place, but it works. I'm both happy but mildly confused! If you get the issue it's obviously with trying! You only need to flash the rom to remove it, so it's of no concern to try
Sent from my GT-I9300
metalgearhathaway said:
Well it works perfectly for me, but @Moster2 says the md5 checksum is identical to the files already in place, but it works. I'm both happy but mildly confused! If you get the issue it's obviously with trying! You only need to flash the rom to remove it, so it's of no concern to try
Sent from my GT-I9300
Click to expand...
Click to collapse
I'm wrong, this method went wayward for me in the end :banghead:
Sent from my GT-I9300
metalgearhathaway said:
I'm wrong, this method went wayward for me in the end :banghead:
Sent from my GT-I9300
Click to expand...
Click to collapse
Damn!
Sent from my Linaro SM'd CM11 Galaxy S3, with Archi's kernel. A proud Googy Beta tester.
Well done. Works perfectly.
I tried just about everything I could find regarding fixing the camera in my S3, including manually replacing the Camera2.apk and this is the first fix I tried that actually works. Thanks for putting the time and effort in to solve this annoying problem.

[SOLVED] 4.3 Update issue

Hi,
I would need some help , I got the 4.3 update on my htc one unlocked international today, First small update completed fine but the main one fails with this error message :
assert failed apply_patch_check ("system/xbin/nc"
( there is 2 quite long GUIDs after the message )
have anybody encountered this issue ?
Thanks
mystborn said:
Hi,
I would need some help , I got the 4.3 update on my htc one unlocked international today, First small update completed fine but the main one fails with this error message :
assert failed apply_patch_check ("system/xbin/nc"
( there is 2 quite long GUIDs after the message )
have anybody encountered this issue ?
Thanks
Click to expand...
Click to collapse
found that the file its referring to is most likely NetCat from busybox. ( I have also the sense 5 toolbox installed but not the Xposed framework, someone said that might cause issues )
have uninstalled both and re-downloading the update , will report back the result
mystborn said:
found that the file its referring to is most likely NetCat from busybox. ( I have also the sense 5 toolbox installed but not the Xposed framework, someone said that might cause issues )
have uninstalled both and re-downloading the update , will report back the result
Click to expand...
Click to collapse
for an OTA to work, you need to be on stock recovery and complete stock rom; cause the OTA checks the most/if not all of the files on the current rom, and if it sees a discrepancy (either missing file or different version), it won't (actually can't) update, cause the OTA is just a diff between two version.
nkk71 said:
for an OTA to work, you need to be on stock recovery and complete stock rom; cause the OTA checks the most/if not all of the files on the current rom, and if it sees a discrepancy (either missing file or different version), it won't (actually can't) update, cause the OTA is just a diff between two version.
Click to expand...
Click to collapse
I have the original stock rom with stock recovery relocked bootloader, s-off, rooted.
i havent modified other stuff, as far as i remember,
you think its best to wipe and reinstall stock ?
mystborn said:
I have the original stock rom with stock recovery relocked bootloader, s-off, rooted.
i havent modified other stuff, as far as i remember,
you think its best to wipe and reinstall stock ?
Click to expand...
Click to collapse
well the "assert failed apply_patch_check ("system/xbin/nc"" means that file (/system/xbin/nc) is not the version the OTA expected (ie 100% stock ROM), and therefore cannot update.
nkk71 said:
well the "assert failed apply_patch_check ("system/xbin/nc"" means that file (/system/xbin/nc) is not the version the OTA expected (ie 100% stock ROM), and therefore cannot update.
Click to expand...
Click to collapse
and the 2 long strings are hashes, one is the expected and the other is which I have...
so far I have found that file is NetCat, and quite possibly BusyBox modified it as it is included in it...
do you think it would be possible just to replace that file with an original ?
mystborn said:
and the 2 long strings are hashes, one is the expected and the other is which I have...
so far I have found that file is NetCat, and quite possibly BusyBox modified it as it is included in it...
do you think it would be possible just to replace that file with an original ?
Click to expand...
Click to collapse
I guess so, you could extract it from the stock rom.zip and adb push it to the correct location, since you have SU privileges.
nkk71 said:
I guess so, you could extract it from the stock rom.zip and adb push it to the correct location, since you have SU privileges.
Click to expand...
Click to collapse
I have tried via root explorers ( mounted the system RW ) but couldnt copy out for backup , also the file looks like 0
byte..
Bit the bullet and overwrote the file, the update proceeded past the issue , will report back
mystborn said:
I have tried via root explorers ( mounted the system RW ) but couldnt copy out for backup , also the file looks like 0
byte..
Bit the bullet and overwrote the file, the update proceeded past the issue , will report back
Click to expand...
Click to collapse
That did the job, now I am running 4.3
mystborn said:
That did the job, now I am running 4.3
Click to expand...
Click to collapse
Congrats mate, I thought I saw an earlier post with something like "OTA Check Tool"? What's that?
Anyway, glad it worked out :good::good:
You may want to change the main thread title to include [SOLVED] for other to know
It was the "ota verify tool" from scary alien it is in beta, gave me a bit of bollocks but should be something of a nice tool when it fleshes out properly
I will mark the thread solved , thanks for the note.
Although according to google I am the only one who cocked his phone up this way hehe
Sent from my HTC One using xda app-developers app
mystborn said:
It was the "ota verify tool" from scary alien it is in beta, gave me a bit of bollocks but should be something of a nice tool when it fleshes out properly
I will mark the thread solved , thanks for the note.
Although according to google I am the only one who cocked his phone up this way hehe
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hmm thanks, I'll check that tool out when I get a chance, but like you said, it doesn't seem very accurate (at least yet).
And yes, I do believe you had an interesting approach at flashing an OTA

[ODIN] J320A/J320AZ/J320AG links

J320A:
J320AUCS3BQL2 (current)
J320AUCU3BQI5
J320AUCS3AQG1
J320AUCU2AQC1
J320AUCU2AQA1
J320AUCU2APJ2
J320AUCU1APC4
J320AZ:
J320AZTUS3BQL1 (current)
J320AZTUU3BQJ5
J320AZTUS3AQG1
J320AZTUS3AQD2
J320AZTUU2APJ2
J320AZTUU1APD1
J320AG:
J320AUEU2BQJ4 (current)
J320AUEU2AQB1
J320AUES2APJ2
J320AUEU1APE9
Kernels:
J320A_EngBoot
J320A_EngRoot
J320AZ_EngBoot
Naming breakdown:
J320AUCU3AQG1
Model:
J320A
Region:
TUS
TUS
UCS
UCU
UES
UEU
Sboot version:
0
1
2
3
?:
A
Build year:
O=2015
P=2016
Q=2017
Build month:
A=January
B=February
C=March
D=April
E=May
F=June
G=July
H=August
I=September
J=October
K=November
L=December
Revision:
1=Revision 1
2=Revision 2
3=Revision 3
4=Revision 4
5=Revision 5
6=Revision 6
7=Revision 7
8=Revision 8
9=Revision 9
A=Revision 10
I did not test the current versions of these so use with caution.
DamienMc said:
The current J320A, J320AUCU2AQC1, is available for sale. If someone wanted to take one for the team.
And I can vouch for that site. I had to buy the newest AZ to fix my baseband.
Click to expand...
Click to collapse
Do you still need this one? I would be glad to help.
Thanks to @johngr77 for pointing out J320AUCU2AQC1 was available to download for free. It's now in the OP.
J320AUCS3AQG1 is the current att firmware, if anyone comes across it please share.
Found the AQG1 on one expensive paid site, so maybe it would appear somewhere for free:
http://www.sams-eng.com/index.php?a=browse&b=category&id=299
nice. In the mean time I added the OTA posted by @SBCarr
But please read post #2 before installing...i really put it here more for recovery reasons, cause if you're on J320AUCS3AQG1 and have to recover, you'll have to use AQC1 with broken baseband then upgrade using the OTA... and if your like me with no att sim, this is the only way
If my J320A isn't rooted, can I flash the stock AQC1 to AQG1 OTA file through the stock Samsung recovery ?
If yes, will there be any side effects?
Thanks
I'm going to assume no, but am unsure... maybe if you used the original file posted by sbcarr, mine was edited. But the issue is stock recovery flashes it from /cache/fota directory. stock recovery also at some point refuses to install from sd, sometimes it will let you tho
The AQG1 OTA download link is broken. @DamienMc
Mikizio said:
The AQG1 OTA download link is broken. @DamienMc
Click to expand...
Click to collapse
Late last night I used it and it failed, fiddled around a little and I was bricked. So I just pulled the link till I looked into it... want to test it? Lol
Ok links are back...the AZ ota was fine. but the A ota would fail if rooted without kingroot, with kingroot was fine tho. Weird?
I just edited the updater script more and everything is good now.
Mikizio said:
If my J320A isn't rooted, can I flash the stock AQC1 to AQG1 OTA file through the stock Samsung recovery ?
If yes, will there be any side effects?
Thanks
Click to expand...
Click to collapse
I was able to use the eng_root kernel, which technically isn't modifying your device, to push the AZ ota to my phone. But I had the legit db files to start with. When I get time I'll see I if I can't spoof a A ota db file and see if I can get it to update
AQG1 became avail. also on (paid) gsm-firmware, so maybe it'll show up soon somewhere for free
http://gsm-firmware.com/index.php?a=browse&b=category&id=10158
Figured out how to pull the firmware from smart switch, but could only get AZ, then found it here ... I'll add it to the OP a little later.
If anyone is on stock att on AQC1 feel free to inbox me and I'll help get the AQG1 files
DamienMc said:
Figured out how to pull the firmware from smart switch, but could only get AZ, then found it here ... I'll add it to the OP a little later.
If anyone is on stock att on AQC1 feel free to inbox me and I'll help get the AQG1 files
Click to expand...
Click to collapse
I'm currently on AQA1(J320A), but if I'll have the AQG1 files, I would flash to AQC1 then to AQG1, or should I be on AQC1 to get AQG1 files ?
Using smart switch I don't think it matters which your on because it's the full firmware, ota just patches files so you need aqc1... if you're not rooted hook up to smart switch and see if it says there's an update available and which one it offers
DamienMc said:
Using smart switch I don't think it matters which your on because it's the full firmware, ota just patches files so you need aqc1... if you're not rooted hook up to smart switch and see if it says there's an update available and which one it offers
Click to expand...
Click to collapse
I hooked up my phone (AQA1), and smart switch says "up to date", and doesn't offer anything.
I read on XDA that there is some method to trick smart switch using a free program called Fiddler.
Hmm ok it's not just me then, thought it was cause of my baseband or sim card. I downgrade to apj2 and it says the same.
Think that fiddler trick just spoofs your carrier, and that's what we're after att specific firmware
DamienMc said:
Hmm ok it's not just me then, thought it was cause of my baseband or sim card. I downgrade to apj2 and it says the same.
Think that fiddler trick just spoofs your carrier, and that's what we're after att specific firmware
Click to expand...
Click to collapse
If I will upgrade to AQC1, is there a method to get AQG1 (no root)? do you know one ?
Mikizio said:
If I will upgrade to AQC1, is there a method to get AQG1 (no root)? do you know one ?
Click to expand...
Click to collapse
Wait your not att?
That's why smart switch didn't work.
I don't know a way besides official ota
Thank you for this. This helped me recover my SM-J320A It was showing baseband, IMEI and IMEISV all Unknown, and Sim Card not detected. After using Flashfire I flashed with J320AUCS3AQG1 **see post #2 (OTA) and then Flashed J320AUCU2AQC1 (newest available) and now everything is back to normal and working great.
BTW I am still learning and Unfamiliar with OTA. What exactly is it and is it needed? I tried to do some searching on google but no information came up. Reason I ask is I read post #2 but was unsure what it exactly means and what the proper way to do this is. Since my phone is now working I didn't want to break it just yet again LOL.

Categories

Resources