How do I create/acquire all of the necessary firmware files to use Tool Studio 4.6? - Verizon Samsung Galaxy S III

I don't have access to a computer SD card reader (my laptop keeps crashing and won't boot, for some reason), so I just have my desktop with a microUSB cable. I am trying to use Tool Studio 4.6 to get stock firmware back onto my hard bricked S3 SCH-S968C and boot it up, but apparently the firmware I downloaded from SAMMOBILE doesn't have everything I need (go figure ). It's missing two .xml files, for one thing, and some files aren't named right either. Attached is a screen cap of the folder containing the firmware I downloaded. Any input on how to get FULL firmware to flash onto my phone would be much appreciated, thanks.
EDIT: I can't get into download or recovery mode, so that's why I'm trying to use Tool Studio. If anyone has a better suggestion for flashing firmware on a phone that can't get into either mode, please feel free to add it here. Thanks again!

Related

[Q] Can the Atrix 2 work directly with Filedropper?

Is there any way to configure the Atrix 2 so it can download files directly from filedropper?
I've seen more than a few roms and patches hosted there, but I find every time I try to download them directly to my phone the downloads immediately time out. I have to get on my laptop, download the file, then transfer it over to my phone myself.
Which I can do, of course, but it would be so much more convenient to download the file directly to my phone and go on from there...
... has anyone managed to get this to work? Is there a trick I'm overlooking?

Bricked phone build.prop missing

Hi to all here. i just want to ask anyone what to do with my phone. well first of all, my phone is a sky pantech vega racer im-a760s, not really a match for samsungs popularity but budget wise this is the model for me. it has a dual core. now my problem starts when i started editing the build.prop in its system (tweaked for some texting problem of limited character sending). of course i know what im doing on that part, but the only thing i didn't think that would happen was, i copied it in my computer, i edited it there, then i saved it as "all" in file type so it wont become a ".txt" format. but when i placed it in my phone. the file instantly disappeared, i think it was only hidden and the phone just cant identify it nor read it like something. now i restarted the phone, it booted up to its logo then it just went blank and it just stops there. i tried pushing recovery with adb in my pc cmd. but it cannot detect my device(no problem with my adb installation to eliminate this from the question), i also tried putting an sd card with a recovery file but there was no option for sd card path. but the phone can still function well, i know because it can still be loaded under flashboot, download screen and S / W upgrade menu and it can still perform wipes for all partition and caches and can reset for factory settings etc. but whenever i will reboot, its not going to complete. anyone please help me how to make my phone be detected by my pc. The usb drivers are just fine, updated it many times, read all procedure for making the driver connect perfectly. i reformatted the sd so it wont be a problem when i put it in. but in the recovery menu i just cant see my sd card, theres just the option for "update from external storage" but it doesn't have anything inside. what a mess. i cant make my phone reflashed cause its not responding with the connection with my pc. but when i am opening an odin (just used for connection monitoring) there are two yellow boxes with com port like these: 0:[com7] and 0:[com9], so i know it is still somehow communicating with my pc. please help any advice, i dont want to resort to jtag for im not sure if it will support my phone and it's already avialable for the model but definitely not going to send my phone for repair cause it will be costly. thanks to all who will respond. Please help thank you. additionally: OS was ics version 4.0.4 and rooted. already gone through rooting several times with no problem. just the editing part.
to edit Android files on Windows use only Notepad++ anyway do not use Windows notepad this is for Windows files formatting only
well, you have to get build.prop from your phone edit on PC then copy back
so enter recovery connect phone to PC create a folder say C:\tmp
to get build.prop from phone
Code:
adb devices
adb shell
mount system
exit
that's to mount system partition then
Code:
adb pull /system/build.prop C:\tmp\build.prop
edit it and copy back to phone
Code:
adb push C:\tmp\build.prop /system/build.prop
maybe is not your case ? but I wanted to give you an idea
@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot
cruelink said:
@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot
Click to expand...
Click to collapse
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again
ruscan.calin said:
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again
Click to expand...
Click to collapse
Hi, cant still afford to make the adb component in my device manager to appear, but it's good to inform you that it helped me a bit because i was able to see the storage of my phone and i was also able to put some files in there without any hassle that alone was satisfying me that my phone is not really dead. sad to say i did everything i could to have my pc detect my phone via recovery menu, but still no devices found. it's really weird that some links are saying that i should make my phone's "usb debugging" enabled, wherein fact i cant even go beyond my original problem(bricked phone), i can't even see the inside of my phones directory, only the storage one that was activated just recently. i even did a reinstallation of my usb, uninstalled every other phone related usb installation to avoid conflicts reinstalled my phones proper usb installer then restart. no progress still to be called. it makes me feel that the phone was just trap in the state of booting and not knowing what to do because it cant see any command inside its system. i cant go into the systems directory as well. and that's the only way i think i could revive my phone in replacing a new build.prop, as you advised to be edited in a notepad++ which i recently acquired and installed. by the way how do i save the build.prop to its original file format, and what is the extension. thanks alot for helping out. im getting a little brighter each step of the way, im not loosing it to come to smashing my phone to pieces instead of keeping a very expensive paper weight.
usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail
isa. rgiespea
ruscan.calin said:
usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail
Click to expand...
Click to collapse
that's great news, you actually come to emailing the phones manufacturer? wow, im flattered. well you're a very nice guy to help me out on this. and i have good news too. i found out that i have a little conflicting usb drivers, as i have installed samsung for my previous phone(samsung galaxy 1) i had it liquidated for this new one. but a little hard on the support. you gave me a new idea about the usb. so i uninstalled all the related usb drivers and have it reinstalled. now i am able to communicate with OTA firmware server, and i got a reading that was not happening before(stucked in just detecting the phone) now i have a percentage reading of downloading or so. but i still have to wait if it will complete and have it repaired. so by now you can give me a little more help cause im still not at it in pushing through the use of adb programming. and the link you mentioned, i'll wait for the progress about it and see what really was it. and thanks a lot. really appreciate it.
fixed bricked phone via OTA by fixing link to pc.
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.
cruelink said:
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.
Click to expand...
Click to collapse
that's good news ! and thanks for feedback
feedback is an invaluable resource ! (some just forget about that from my experience :laugh: NOT your case ! )

I need a tutorial.....

Hi everybody!
I need to find a good tutorial before I stupidly hard brick my android....I have already managed the soft brick.
" Connect your phone to the computer using the USB cable in the mass storage mode and then copy the Flash APK File which you downloaded to your device... Now, disconnect the phone from computer, head to the apk file where you placed, open the same and follow the on screen instructions to update the same in your phone or tablet".
Yes, I am a "noob".
What I have learned is basic, I have managed somehow to install C.W.M.6 on my Samsung Galaxy W with Odin and can flash a ROM! Oh boy!
Also... where can I find a tutorial that will show me how to use a terminal emulator and copy image files with Odin ?
Any help would be sincerely appreciated!
Any suggestions?
B.Marky said:
Hi everybody!
I need to find a good tutorial before I stupidly hard brick my android....I have already managed the soft brick.
" Connect your phone to the computer using the USB cable in the mass storage mode and then copy the Flash APK File which you downloaded to your device... Now, disconnect the phone from computer, head to the apk file where you placed, open the same and follow the on screen instructions to update the same in your phone or tablet".
Yes, I am a "noob".
What I have learned is basic, I have managed somehow to install C.W.M.6 on my Samsung Galaxy W with Odin and can flash a ROM! Oh boy!
Also... where can I find a tutorial that will show me how to use a terminal emulator and copy image files with Odin ?
Any help would be sincerely appreciated!
Any suggestions?
Click to expand...
Click to collapse
You might want to look at this to see if it will help you
http://forum.xda-developers.com/showthread.php?t=1467128

Stuck in bootloader with no volume keys, and windows won't recognise device

Hi,
I have a 5" android tablet recently acquired through Amazon, and it appears to be completely brandless, so I have no idea who made it.
I rooted the device and changed the bootloader image using the app "Boot animations". It booted, then loaded the animation and gets stuck there. it cycles through this three times before giving up and booting into recovery. Once in recovery I have no way of selecting any option other than "Reboot system now" as the only hardware button on the device is the power button. there are no volume, home or menu buttons of any sort.
There is a reset button on the back which simply takes the slightest click and it reboots the device. neither this, the power button, or any sequence of the two together provide me with anything other than a reboot.
I Then tried installing SDK with platform-tools and the usb driver, I also downloaded the generic android usb driver from google, and i've tried running ADB to no avail, neither of them will see the device, and device manager does not show the device under "Other", it simply displays it as a mass storage device briefly while it runs through the attempted boot sequence before entering recovery where it no longer appears in device manager.
I have a new 64gb SD card for it which i have done nothing with, I'm hoping that maybe there's a way of using it given i have no hardware buttons?
Does anyone have any idea of how I can factory reset this device?
I'm desperate here and have researched every forum google has thrown at me over the last two weeks.
Many thanks
Jody
hello @jody-michael
I don't know if there is a way to fix the problem.
Please see this post. If there is adequate time to change the boot animation file bwfore the device reboots, maybe it can help you.
Are there details of the device model under its battery?
Have a great day
Hello @yairku
Thanks for your reply. Unfortunately I stupidly didn't turn usb debugging on, so when it does briefly show up as mass storage, I can't actually access the storage, so can't access or change the bootloader files.
The other issue is its a sealed unit so I can't access the battery either. If anything I could do with some kind of clever windows app that can see the device and run a factory reset bypassing the debugging mode as it's not activated.
Hi @jody-michael
If the device has an mtk chipset, it might be possible to use sp flash tool to get the firmware from the device, edit it and flash it.
To use sp flash tool, a scatter file is needed.
I found this tutorial that shows how to create a scatter file.
I hope that It will be possible to replace the boot animation that causes the problem, with a good one.
If you are willing to try to create the scatter file, please let me know and I might be able to help you with it. I understand the steps of the tutorial.
Good day
There should be written something on the back of the tablet. Something more than just a serial. try to post a photograph. Once the device is identified, look for a ROM in an update.zip format. Copy the update.zip into the root directory of a sd card, turn device off, apply sd card and turn the device on. Hopefully, it will discover the update on the sd card and install it.
Best wishes...
Unfortunately sp flash tool doesn't see the device either. I've persisted with driver installs etc. I haven't been able to get the existing scatter file read or figure out where to get one for my device.
yairku said:
Hi @jody-michael
If the device has an mtk chipset, it might be possible to use sp flash tool to get the firmware from the device, edit it and flash it.
To use sp flash tool, a scatter file is needed.
I found this tutorial that shows how to create a scatter file.
I hope that It will be possible to replace the boot animation that causes the problem, with a good one.
If you are willing to try to create the scatter file, please let me know and I might be able to help you with it. I understand the steps of the tutorial.
Good day
Click to expand...
Click to collapse
Thanks JoachimP,
I like this idea, however I don't know what rom to use. As you can see in the attached images, there's no indication of manufacturer name, model, serial or anything. All I have is its a 5 inch brick right now
JoachimP said:
There should be written something on the back of the tablet. Something more than just a serial. try to post a photograph. Once the device is identified, look for a ROM in an update.zip format. Copy the update.zip into the root directory of a sd card, turn device off, apply sd card and turn the device on. Hopefully, it will discover the update on the sd card and install it.
Best wishes...
Click to expand...
Click to collapse
Hi, look at your 1st picture: CIOtCUD is the hint to the topic you should google for. Look at http://www.mastfun4u.com/2015/09/find-all-china-tablet-flashing-file.html, maybe this is helpful.
Regards, Joachim

How to Flash Samsung Software.

Hey everyone.
Last year I taught myself, how to Flash Samsung software.
After I learnt everything I needed, I made a step by step guide in my notes in case I need to do it again.
I posted that step by step guide in another discussion and it seems to have got a lot of views and hopefully helped.
As its at the bottom of a forum I thought I would post it in the next comment so people can get better access and I can help more.
Hope it helps.
Notes Before The Method
the cable you are using to connect to the pc should be the original charging cable. (If you don't have the original then use the one your using and see if it works)
Your phone needs to be at least at 60% battery.
Older phones sometimes don't work with newer versions of Odin so if this is happening download a older version.
If it's a new phone and you want to personalize it from scratch then no need to back up and restore any data.
Remove your SIM card to prevent it from being SIM locked to one network. ( I read it somewhere, not sure how true this is but I do it and seems to work)
After removing your memory card, plug it into your computer using a memory card extension and copy photos to your computer. Just in case the phone formats the memory card when entered back in to the phone, after the firmware is installed.
Method
1. Go to Sammobile via Google chrome in incognito mode. (If you don't do this they will re-direct you to a sign up page, everytime you press download)
2. Download Firmware, find this by picking the lastest firmware thats with your network and match the Baseband version or the last part of build number. (found in system info in the settings)
3. Install the latest version of Odin and install Samsung secondary device drivers on your pc/Laptop.
4. (On your mobile) back up your data in the samsung cloud.
Setting>Cloud and Accounts>Samsung Cloud>Backup settings> Back up.
If you have a memory card, move all your photos ect to it and remove it from your phone.
5. Go into setting and tap build number 7 times to unlock developer options. After unlocking it, enter developer options and enable usb debugging.
Setting>developer options>USB Debugging.
6. Once the firmware file has stopped downloading on your pc extract it and send it to your Downloads File.
7. Open Odin and load each part of firmware in the right box e.g. AP with AP, BL with BL, CSC with CSC ect (Do not load up Home CSC this is used for when your moving a branded device to another brand, E.g. EE to 3)
8. Before you plug your phone up to the computer. Turn your phone off and enter Odin mode(Download mode). Each device has a different way of doing this so just google how to do it on your specific samsung device.
9. Once your phone is in download mode plug it into the computer and press start. This should take a couple of minutes but some files may take longer.
10. Once the Odin confirms the process is done by showing the pass sign unplug your phone and turn it on. First time you turn it on May take a minute or two to load.
11. Enter your google email and password, and restore all your data on google.
12. Then enter your Samsung user and password, after that press restore and choose the date you backed up on before you flashed your phone (at point 4)
13. Enjoy all done.

Categories

Resources