My S8500 is on bada 1.2 OS, I don't remember the firmware but it is the latest which is available in India, before that I had used a modified firmware for the SHP and had updated it via Kies to this firmware. The firmware was very unstable, it used to restart 3-4 times a day. But now it is just stuck on the first screen where Samsung Wave GT-S8500 is written. This screen just comes and disappears in an infinite loop. I can enter the download mode. Should I flash and go to some other older firmware or is there any other solution available?
I had a similar problem, I re-flashed my phone and the problem was solved.
I know that is one of the solution, but just wanted to know if there is an alternative or not as I had installed many apps which were free at that time and now they are paid. Also I'll lose my messages, settings and some contacts. Any other solutions?
You could check out what happens...
Flash ONLY Rsrc2_S8500_...(Mid).rc2
Then you should see "Bluescreen" with some infos...
If you need Backup from your data, now is harder...
Sorry. If Wave hang or loop it is for most users toooo late.
As no way known to repair easily without dataloss...
Best Regards
Rsrc2_S8500_...(Mid).rc2 needs to be of the same firmware on which my phone is currently?
Rsrc2_S8500_...(Mid).rc2 needs to be of the same firmware on which my phone is currently?
Click to expand...
Click to collapse
Not exact if you can't remember.
But be sure it is from nearest possible Firmware you can find...
So if India bada 1.2 you can remember. Then take from indian bada 1.2 RC2 file.
If you can't find MID. Upload, we can change for you...
Best Regards
And if it doesn't works out than I can still try full flash, right?
Edit : I tried to convert the low file to mid, but didn't quite understand the process. I also tried to download some firmwares but always ended up getting low file, so I'm attaching an low file to get converted to mid. Thanks in advance.
Related
hi all
a friend of mine tried to update his camera and it just bricked
he tried the fix on badaforums.net but it didn't help
any suggestions as fix using PSAS or what ever
the fix i mentioned is done by using Stune or Tk_file_explorer
you can find it on this link http://www.badaforums.net/forums/samsung-wave-tutorials/solution-camera-failed-t1615.html
so any thoughts will help
http://www.samfirmware.com/apps/blog/show/4942348-update-camera-fw-s8500
Maybe same, but maybe more Pictures.
I've NEVER tried this. I can only remember that once I see some Cam Error on my Test Wave...
But for my Test Wave I've used only Multiloader and flashed different Firmware from old to new or back to old Firmware... and it seems. Some internal mechanism force the Cam to autoupdate...
No idea how and when...
I only know, that you can't choose. And this is bad.
My Test Waves Cam is alive, but no idea how and when ... it repairs self.
Best Regards
Maybe we find one day. How it works, that Firmwareupdate forced also CAM to update...
As I nearly never use CAM on my Test Wave and also never did Masterreset or something like that.... Then maybe Fullflash with Multiloader is the reason?
And after initial blabla CAM is forced to autoupdate without chance that user can choose something...
Best Regards
So should i tell him to do a downgrade with a full firmware flash??
i saw another thread where people said that worked for them
what is your opinion adfree??
My opinion.
1.
Be sure, this Cam Error is after Firmware update via Multiloader or maybe Kies?
Hmmmm... maybe Kies force Cam Update?
I can't remember what I did before.
But my first try was to downgrade my Firmware with Multiloader.
I have somewhere Screenshot, I will upload soon...
2.
If this come after Update... then try first to go back to prior Firmware.
I'm NOT talking about CAM Firmware.
I only know that 1 user tried many things. I don't know in which order. But ever failed to repair Cam on S8530...
Only Samung Service was able to do this.
I hope your friend have more luck.
Best Regards
thanks adfree
the problem occured when he tried to upgrade the Cam fw from the hidden menu
i'll tell him to downgrade his firmware to the prior one and see if this fixes the problem
and i'll report right here the results
by the way he has a S8500
Heelp
Hi guys,
I've kinda got the same problem.
I've bought the Samsung Wave S8500 by ordering it on the internet, and came with the camera failed problem. Initial firmware was S8500BVJF1 / Bada 1.0. I've tried uploading camera fix s8500.rar files to the phone but it didn't work. So I tried upgrading it to the latest firmware using Samsung Kies. Now the firmware version is: S8500BVJK1 / Bada 1.0. Tried the patch process again and still didn't work.
From what I can see it's something wrong with phone reading the bin files (?). After I upload the .bin files if i try the *#17932864# thing and go to "(6)Video -> (3) Camera firmware -> (1) Phone/Cam FW Ver check" I get "ERROR: can't read version info". Then if I chose "(2) Phone to Cam FW Write" I get Phone to Cam FW Write [FAILED]. So my guess the format of the bin files might be different from what the current firmware expects. Ah also, the (4) FW Write Count is set to (00) : (00).
So the questions / requests are:
1. Do I need perhaps Bada 1.2 for the those files to work correctly?
2. Could you guys upload me some of your camera firmware bin files that work for you along with the name of the phone firmware version you are using (it would be ideal if somebody had S8500BVJK1 along with camera files that work).
3. If anyone else had this issue and got it resolved pleaaase help. S8500 is a great phone with a great camera and it would be a pitty if it didn't work.
Thanks,
Waiting for suggestions
well, a while ago when i corrupted my Bada OS booting a certain config of the Linux kernel my camera wasn't working after reflash, in the end i fixed it by doing a FULL reflash, then a Factory reset, then the camera app worked, and continued to do so after doing camera firmware update too.
Hi, I'm looking for the US version of the latest stock firmware for the P5210 United States version. I've looked at sammobile.com and tried to find it there but it seems EVERY other country in the world is listed except for US versions. Is there a reason for that? Some weird laws here that prevent that? I've wondered that for a while since my original tab 7" days and I could never find US firmware for that either and had to use the UK version.
Anyway, I'm trying to install Grievous 5.0 rom and this is the first ROM i've tried putting on it. Was rooted for a while, just flashed TWRP, that went fine, made a backup. Tried installing the rom, it said successful but when I went to re-boot it, I keep getting two boots to the samsung logo then right to the TWRP main menu.
Yes... I did follow the devs installation instructions exactly. Two or three times. Tried different resets, and installation combinations with no progress, and the same result. If it matters, the file I downloaded was the android file hosting one... currently downloading it again from Mega in hopes it was just a bad download. As of right now, this thing is pretty much dead in the water.
The stock firmware is linked in the OP of this thread http://forum.xda-developers.com/showthread.php?t=2421594
Flash it through ODIN and you should be good to go, I had a similar issue previously.
Thanks, did you ever get any ROM to install and load on yours? I'd really like to try one but so far this whole thing has been a mess. This is my first go at doing any modding on a Samsung device, I've done plenty of Motorola stuff, that just always seems to work for me with no issues. Thanks again for that link. I might have to play with this a little more when I have more time.
baune7 said:
Thanks, did you ever get any ROM to install and load on yours? I'd really like to try one but so far this whole thing has been a mess. This is my first go at doing any modding on a Samsung device, I've done plenty of Motorola stuff, that just always seems to work for me with no issues. Thanks again for that link. I might have to play with this a little more when I have more time.
Click to expand...
Click to collapse
I was attempting to flash Pimpdroid when I had the problems, and it seemed like every time I tried to wipe/flash something went wrong. I'm not 100% sure, but I think I ended up just flashing over the stock rom. That was a couple months ago, though, and I'm not sure if flashing techniques have changed or if it has gotten any easier.
Hey man , you have not looked the firmware properly. First of all , US firmware on sammobile is always written as the country 'cellular south' . So , buddy on sammobile firmware section type p5210 and then look for the country cellular south . I was also confused first but then I found my tab's pda code and csc code and then looked for the country and it matched with cellular south . So buddy search for cellular south country . And if you don't want to download from sammobile or you have any problems downloading from sammobile , here is the link https://mega.co.nz/#!sJZCxQ7T!hdJXKXTVZe_Rx63CYE3xPESxxNr9FWqgGQgmOz1DH3A P.S. - It the latest US stock firmware for GT-P5210. And the link which darthjader has provided, the firmware is of any European country because US firmware starts from UEU. And the latest U.S. firmware is P5210UEUAMK1 . I have provided you with the link of latest P5210UEUAMK1 . And to the answer for your 2nd question , Yes, I flashed the pimproid rom without any glitches and problems. What I did was that my tab was rooted and TWRP was installed . I just placed the pimproid rom in my tab's internal sd card , booted into TWRP recovery and then without any wiping I just installed the rom because TWRP automatically wipes the data and dalvik cache . I haven't tried the grevious rom . Ok my friend , after writing such a long post I hope that you find my post useful .
PLEASE HIT THANKS IF I HELPED YOU .
Sent from my GT-N7100
This is very interesting. When I go to the OP listed above, the file name is P5210XXUAMG6_P5210OXXAMG3. However, when I look at my firmware in the device, the Build Number is JDQ.P5210UEUAMK1. Not sure how Samsung Build Numbers relate. They could be country specific like mentioned above, or something else. I just don't know.
My concern is loading a build that is not the same as the one on my Tab. I have backed up the device using TWRP but I am not sure if that particular build is included in the backup as part of the system.
I too am not sure if I have loaded stuff correctly. I know I am ROOTED because a Root Check said so. I loaded a new Rom but really saw no real difference. So I am not sure if I have done things right. I did follow the letter of the procedures to the T.
added: you can also find the firmware at this address.
XAR-P5210UEUAMK1-20131209141149.zip
http://samsung-updates.com/details/18708/Galaxy_Tab_3_10.1_Wi-Fi/GT-P5210/XAR/P5210UEUAMK1.html
I have a Samsung Wave S8500 (running Bada 2.0), which I hadn't used in a couple of years. Now I am selling it, and for security purposes I reset it to factory settings, to erase all data. The thing is, personal information, contacts, old chats etc. on Samsung ChatON persists after factory reset!
I don't even know how on earth this is possible, but I have no way of either manually removing them or deleting the app (because it's a default app).
I could really need some help, in any shape or form.
I thought to try and reflash the phone, but I can't through Kies because it, frustratingly, says that the latest firmware is already there.
I thought to try and install a new firmware with Odin, but for the life of me, everything fails (I can't find a working rom - sammobile .zip files seem to be corrupt, I tried 4 different ones, and others report similar issues)
I googled trying to find a way to "get into the system" and just delete the @$#! ChatON app, but I can't (some mention a program called Trix), but I can't understand how to use it.
Any help at all? Thanks in advance!
First : Odin is for android devices and Wave is NOT an android device
Second : you can use multiloader to reflash your Wave or you can use emergency firmware recovery through kies
Best Regards
mylove90 said:
you can use multiloader to reflash your Wave or you can use emergency firmware recovery through kies
Click to expand...
Click to collapse
Thanks for the input. Kies, as I mentioned, does not allow me to use emergency firmware recovery, because the latest firmware is already there.
I also tried multiloader, but I can't find the roms anywhere. The sammobile .zips are corrupted. If you (or anyone else) is aware of another repository of roms, I'd appreciate it
As i recall....the emergency firmware recovery can be started from kies without even connecting the phone to the usb
You have to enter phone serial number and model then kies will instruct you to press key combo to start download mode
Sorry i don't have a pc to show you the steps but it was really pretty simple
Best Regards
Hi, I currently have a Samsung Galaxy S7 Active and while updating, it went into a bootloop. I cant boot into recovery, odin fails to flash the stock rom, and all I get when booting is:
SAMSUNG
Galaxy S7 Active
Powered By
android
screen. It doesn't even go to that, all it does is boots into recovery. I don't want to send it out for repairs (Mostly because I am broke).
If also, may I get answers from people that own one and been in this problem before and/or people that know how to repair this issue.
Also, I can only use the Stock Recovery.
Thanks, Nysean01'
Edit: I have also been to this. It was no help what so ever and got me deeper to this point in the post.
Edit 2: I have a backup phone and that one is currently working. I still wanna keep using my newer one.
which rom/version was you on?
which you trying to get to?
which ones have you tried in odin?
are you loading all the files ?
does it say it completes successfully ?
miniminus said:
which rom/version was you on?
which you trying to get to?
which ones have you tried in odin?
are you loading all the files ?
does it say it completes successfully ?
Click to expand...
Click to collapse
7.0
Not trying to change
Yes, I'm loading all the files
Nope. It says in red, FAIL.
then i would guess that the file is currupt, or maybe the cable is dodge...
but which version was you on before (QB2) and which you tried so far ? (QD4 ?)
miniminus said:
then i would guess that the file is currupt, or maybe the cable is dodge...
but which version was you on before (QB2) and which you tried so far ? (QD4 ?)
Click to expand...
Click to collapse
I was running the latest version of everything. 7.0 for phone, 10 for computer, and a mod odin.
Try a different Odin package, an older stock ROM and a different cable.
Which ones would you recommend?
Odin 3.12.4 and PI2, that is the earliest on BL2, try that, and if it works you should be able to OTA back up.
Mark as closed. I took it to the store, and even they said that they cant do nothing about it. So, Since I had the warranty (didn't know, was a hand me down), Samsung is sending me a new phone.
I have the same problem, got stuck on Nand writel. Already try different odin versions, I was on the last stock room, the problem was that I heva virus and had to do a hard reset, but when I finish got stuck on google verification, after try a lot of times I decided to fls stock room, but I fail.
What I can do it?
Hi, I'm new to the forum and was wondering if someone could help me just clarify a few things specific to my S9 that I am trying to remove frp from.After trying a lot of the youtube guides on bypassing the FRP using the "easy tools" and failing I thought of reflashing the OS. Since that doesn't exactly just work and you need a combination file, I was looking to figure out what combo file I need. The number from recovery menu is 10/QP1A.###/G960WVLS7ETH1 and the IC on the back of the phone is 649E-SMG960U.I found a tutorial saying you can make the combination file from the official firmware, but after getting that from SamMobile I could not find the sboot.bin.Iz4 in BL section. Then I tried looking online for a faster download of my firmware but none had the exact numbers right or the correct files in BL. (They had the right Ap files though). I also tried looking for a combo file directly but the same problem is I don't know the exact numbers/version that I need to make sure its correct for me to apply it into ODIN.I found a few links to combo files but they are all usually for android 8
Samsung SM-G960W Combination File ROM (Flash File)
Download Samsung SM-G960W Combination File (original flash file, rom) without any password for Free. We also provide the combination file for all Samsung devices.
samsungcombinationfile.com
Samsung Galaxy S9 SM-G960W Combination Firmware
Samsung Galaxy S9 SM-G960W Combination Firmware Samsung G960W Galaxy S9 Combination Firmware is a stable
www.full-repair-firmware.com
I just need to figure out what the software version (or baseband version?). Some threads say your phone model number must be the same and others say it only matters for the processor to be the same. Can I download the G960U files instead of a G960W or am I reading the wrong thing. Also can someone help with the bootloader version / build version. I think it is bootloader version 7 but its in place of the U that is written in most guides. and then the revision would be 1 right?Just would like some confirmation that I am looking for the right file. By what I have looked into so far the combo file with version G960U + android 8, bootloader version 7, and revision 1 will work regardless of the other numbers. or does it have to be G960W? F? X? any letter that has the same processor? Anything else I need to make sure of, is there an easier way to remove frp?Any help is appreciated, Thanks!
Update: Finally got into my frp locked S9. For anyone wondering I went with the combination file titled: COMBINATION_FAC_FA80_G960USQU7ASJ1_FACFAC_CL13230190_QB26521439_REV01_user_mid_noship_MULTI_CERT.tar that I got from the second link above.
I can conclude that the version of android does not make a difference since the combination file is simply like entering safe mode on your device. I'm not an expert but the SM-G960U file worked on SM-G960W phone and I made sure to get a file with same boot loader version and revision number, ignoring the letters that tell dates. From there I was able to OEM unlock and then reinstall the latest firmware I got from SamMobile.
Hi, I also needed to remove the google frp on my phone. I've tried so many different solutions online but nothing would work. ive tried every file in the link you've posted. a lot would Fail when it was loading it into my phone through Odin. always got Auth Fail or some other failure. some would cause infinite boot loop. some i couldnt use because it had password protection to unzip, i doubt it would have worked anyway lol.
My phones recover screen code or PDA? was G960WVLU9FUE2 I do not know what any of the letters or numbers mean after G960w, but i assume the 9 and the 2 are what are important and no files online match those numbers in the same file. I actually didnt find any combination files for U9 without needing to pay for it.
In the end i ended up just guessing the pattern password. I found a glitch that lets me keep guessing without a timer cool down. Now idk if this glitch is caused by my attempts of using these combination files then restoring it with the files from sammobile. but the glitch is easy to do.
First i did a factory reset. then when it boots up it asks to enter a network then to enter the pattern or sign into google. i dont know both so i started guessing the pattern. after a few tries it starts giving a timer cool down. I noticed you can bypass this timer by simply turning the screen off and on, then u can attempt again. when you fail the timer is still counting down from the previous attempt. like a 30 second cool down, but after screen turn off and a failed guess, the timer would be counting from like 22 seconds. then another attempt the timer would be at like 8 seconds until it resets back to 30 seconds when the timer runs out after another failed attempt.
I hope this info helps others get into their phones if Odin can't help you. Even if guessing passwords is a long tedious task.
Here's a tip for guessing node patterns. most people start from the top left corner and usually only use 5 maybe 6 nodes.