Looking at samfirmware site and clicking on firmware brings me to a dead end, anyone know some new links to their firmwares?
there you go
http://www.samfirmware.webs.com/
you might hav to register
regards
If you can get passed all the snags and bugs KIES has with connecting to your customized device, download it and use it to connect your phone to your computer and check for the latest firmware.
EarlZ said:
Looking at samfirmware site and clicking on firmware brings me to a dead end, anyone know some new links to their firmwares?
Click to expand...
Click to collapse
try this site wuala.com/Samsung%20Galaxy%20S?key=AfzUZSU4SpKU
just add www. I cant post links
Just downloaded the ZSJP2 Froyo flash from firmwares, and it says the file is encrypted and I need a password to extract the files. Anyone know what the deal is on this?
Cheers, Phil
dude... the pw is right at the page u download the firmware...
PhilPassmore said:
Just downloaded the ZSJP2 Froyo flash from firmwares, and it says the file is encrypted and I need a password to extract the files. Anyone know what the deal is on this?
Cheers, Phil
Click to expand...
Click to collapse
hi there i was trying to download the I9000UGJH2 firmware from samfirmware.com and upon extracting the rar file i was prompted with the password. So I tried to type in the password provided on the site (samsung-firmwares.com and samfirmware.com) and they dont work. I cant open the file says wrong password.. so HELP.
Or if anyone could post a link to I9000UGJH2 firmware download would really be much appreciated. Thank you.
BTW: Im from toronto using the BELL Samsung Galaxy S Vibrant
p0gsss said:
hi there i was trying to download the I9000UGJH2 firmware from samfirmware.com and upon extracting the rar file i was prompted with the password. So I tried to type in the password provided on the site (samsung-firmwares.com and samfirmware.com) and they dont work. I cant open the file says wrong password.. so HELP.
Or if anyone could post a link to I9000UGJH2 firmware download would really be much appreciated. Thank you.
BTW: Im from toronto using the BELL Samsung Galaxy S Vibrant
Click to expand...
Click to collapse
have you tried copy paste the password from the site, might be a space hidden some where in there.
p0gsss said:
hi there i was trying to download the I9000UGJH2 firmware from samfirmware.com and upon extracting the rar file i was prompted with the password. So I tried to type in the password provided on the site (samsung-firmwares.com and samfirmware.com) and they dont work. I cant open the file says wrong password.. so HELP.
Or if anyone could post a link to I9000UGJH2 firmware download would really be much appreciated. Thank you.
BTW: Im from toronto using the BELL Samsung Galaxy S Vibrant
Click to expand...
Click to collapse
.RAR password for that file is:
samsung-firmwares.com
Hi, I have a problem. I have a Motorola Atrix HD with philz recovery and running AOSB by probam.
I bought an unlock code, but when I insert another sim it does not ask me for an unlock code. It just says unable to connect to network. I have read that one solution is to reinstall the stock firmware. I have downloaded the stock firmware but I am not able to flash it. RSDLite on my Windows 8.1 computer does not recognize my phone and when I try to do anything with fastboot it says variable not supported. I do have Linux partition on my computer if that helps, but I don't know what tool to use.
My main goal is to sim unlock the phone. If there is a way to do that without returning to stock, that is ok. Otherwise if someone could help me, I would appreciate it. If you need any more information I can give it to you.
Did you try using Myth Tools?
I've been trying to download it all afternoon, but when I open it it says.
"Windows cannot open the folder. The compress folder Myth.....zip is invalid."
These are the two links I have been downloading from.
1.) https://docs.google.com/file/d/0B1ASqgUDJHBXX1Z2NzBUR1VLTkU/edit?usp=sharing
2.) http://d-h.st/eLA
I got them from this thread.
http://forum.xda-developers.com/showthread.php?t=2262726
I have a slow connection. Right now I am trying to download version 1.2 to see if that works.
Mythtools version 1.2 worked
Thank you for mentioning mythtools one more time. I decided to download version 1.2 and it installed and flashed my phone within a few minutes! Thank you very much.
Why dont u use 1.3 lol
After downloading 1.3 from both links on this page,
http://forum.xda-developers.com/showthread.php?t=2262726
When I try to unpack the zip, windows tells me, "Windows cannot open the folder. The compressed folder Myth.....zip is invalid."
I have a L925 (RM-910, Code 059S9S8), it stuck while upgrading to win 10 TP. I used WPRT to revert to win 8.1. Initially, WPRT detected the device and tried emergency driver or something which failed and since then my phone is not detected by WPRT, no response if the power and vol- buttons are held, but windows key flashes randomly.
I tried the un-bricking method mentioned in the original post, at the point where they suggest to uninstall the QHSUSB driver, i uninstalled it and continued the procedure until FLASHING THE BOOTLOADER step. It gave me the subject error and code, i retried several times and found two reasons suggested by people for the said error:
1. Incorrect drivers
2. Incorrect files (.hex)
When i retried the step of uninstalling the QHSUSB drivers, i found out that my system doesn't have these installed nor is my phone detected as QHSUSB device.
I have been trying to find if any solution for the above mentioned error has been stated anywhere but i couldn't find one. I have been trying to flash the bootloader (i am an accountant by profession and i don't even know the ABC of programming and this stuff but i learned quite much when WPRT bricked my L925), the subject error appears every time. I have made my .bin file, my own .hex file, .mbn file all for my model but i am still unable to figure out the real issue.
In the original post of un-bricking L925 without JTAG, it was mentioned that the subject error means that wrong drivers are installed. I am using windows 10 on my laptop, and the drivers available for win 7 & 8 are older than the ones on win 10 and when i try to install the drivers downloaded from the link provided in the original post, i got a prompt from win 10 that NEWER VERSION ALREADY INSTALLED.
I kept searching the forums and found someone mentioned that the subject error also appears due to incorrect .hex files and the also mentioned a way to correct the download-available .hex for my model, so i corrected the downloaded ones and even double checked it with my .bin files and i am now sure that i am using the correct files.
So,
1. My drivers are updated versions of those suggested in the post.
2. My .hex file matches with my .bin file (.bin was created using cmd prmpt and from my model)
I cannot find anyother solution or reason for the error which appears.
Any help or guidance from you guys will be really appreciated.
P.S. After failure on windows 10, I have also tried the whole procedure on win 8.1 and the results were no different.
Hoping to get some guidance or help
Yasir H. Qureshi
help anyone?? been more than two weeks since i am trying to get my cell back to work... :|
Hi!
It was a bad idea to flash 356510B0982Axon M RU image (available on Russian zte website) to my ATT ZTE Z999.
Phone bricked and only visible by my PC as QUSB_BULK. Looks like there is a way to restore it, but i need full original working stock ATT image (any version). Does someone can share it?
Found at many places, but all of them wants money I would pay, if it will be 5 but not 25euro
I flashed mine using this[Leakite]ROM_AXON_M_VDF_SDCARD_SOFTWARE_PACKAGE_MR00a and it's not turning on anymore. We need help :crying:
Looks like we need 348010B3014Z999V1.0.0B30.zip
But i can't find it in free access, only payment sites like easy-firmware and grt-dongle
Any idea how we can flash a rom on edl mode?
No ideas for now. But friend of mine works in cellphone service center, he helped me many times to unbrick some devices. For now he is found firmware to restore Chinese axonM, can't find at&t
Ok, i got image... 10$ wasted It really looks like correct AT&T image, but QFIL, MiFlash, QPST, QComDownloadTool (ZTE util) can't flash it
https://drive.google.com/file/d/1n0qjH1vaTQVwckFPizSAMDHrBh6uA8b6/view?usp=sharing
BRuTe007 said:
Ok, i got image... 10$ wasted It really looks like correct AT&T image, but QFIL, MiFlash, QPST, QComDownloadTool (ZTE util) can't flash it
https://drive.google.com/file/d/1n0qjH1vaTQVwckFPizSAMDHrBh6uA8b6/view?usp=sharing
Click to expand...
Click to collapse
You need the firehose programmer and use parts of that firmware to flash with it
BRuTe007 said:
Ok, i got image... 10$ wasted It really looks like correct AT&T image, but QFIL, MiFlash, QPST, QComDownloadTool (ZTE util) can't flash it
https://drive.google.com/file/d/1n0qjH1vaTQVwckFPizSAMDHrBh6uA8b6/view?usp=sharing
Click to expand...
Click to collapse
... If you can get to edl mode, try those Axon 7 firehose programmers. Since they are the same platform. QFIL should flash this image zip with no problem.
Honami754 said:
... If you can get to edl mode, try those Axon 7 firehose programmers. Since they are the same platform. QFIL should flash this image zip with no problem.
Click to expand...
Click to collapse
Are you sure because im under the impression you can only use the exact specific firehose even if its the same chip i think its hard encoded into the shara protocol it will only except the same firehose but mabye im wrong thats just what ive known
Tried Axon 7 EDL Tool and it's won't work
stopped futher research and replaced MB from broken one that bought on ebay
Anyone attempted to flash this? I just got a new one and I'm scared flashing again. I'm thinking of just buying an At&t prepaid sim just to get the latest update.
tidus1ph said:
Anyone attempted to flash this? I just got a new one and I'm scared flashing again. I'm thinking of just buying an At&t prepaid sim just to get the latest update.
Click to expand...
Click to collapse
No reason to flash it if your axon not bricked. I's a stok ATT version.
BRuTe007 said:
No reason to flash it if your axon not bricked. I's a stok ATT version.
Click to expand...
Click to collapse
The one my phone got is the october 1, 2017 patch with build number Z999V1.0.0B21. So the download file is the newer-ish right? Because on the website the latest is sept 18, 2018 patch with build number Z999V1.0.0B35.
tidus1ph said:
The one my phone got is the october 1, 2017 patch with build number Z999V1.0.0B21. So the download file is the newer-ish right? Because on the website the latest is sept 18, 2018 patch with build number Z999V1.0.0B35.
Click to expand...
Click to collapse
This one was named 348010B3014Z999V1.0.0B30.zip and i think B35 newer then this one.
Here are the Z999 and Z-01K firehose files, extracted from an Internal ZTE tool I have. Hope it helps people out
Z-01K (Japanese Axon M)
https://www.androidfilehost.com/?fid=1395089523397896977
Z999
https://www.androidfilehost.com/?fid=1395089523397896976
All I ask is if you use these files in a guide or anything that you credit me for providing them because i needed to pay to grab these.
deadman96385 said:
Here are the Z999 and Z-01K firehose files, extracted from an Internal ZTE tool I have. Hope it helps people out
Z-01K (Japanese Axon M)
https://www.androidfilehost.com/?fid=1395089523397896977
Z999
https://www.androidfilehost.com/?fid=1395089523397896976
All I ask is if you use these files in a guide or anything that you credit me for providing them because i needed to pay to grab these.
Click to expand...
Click to collapse
Forgive my ignorance. But what does these files do? z999 is the at&t's version right?
tidus1ph said:
Forgive my ignorance. But what does these files do? z999 is the at&t's version right?
Click to expand...
Click to collapse
The firehose is needed to flash the device with QFIL, miflash, etc so a device can be unbricked.
deadman96385 said:
The firehose is needed to flash the device with QFIL, miflash, etc so a device can be unbricked.
Click to expand...
Click to collapse
Tried to flash with Miflash but that failed starts flashing but then says : Cannot Read Port and stops flashing.
Also tried QFIL But also fails with this message : Download Fail:Sahara Fail:QSaharaServer Failrocess fail
hope somone can clarify if its even possible to recover.
this brick happend after update.
Reverender said:
Tried to flash with Miflash but that failed starts flashing but then says : Cannot Read Port and stops flashing.
Also tried QFIL But also fails with this message : Download Fail:Sahara Fail:QSaharaServer Failrocess fail
hope somone can clarify if its even possible to recover.
this brick happend after update.
Click to expand...
Click to collapse
Sounds like you have a driver issue make sure you install the Qualcomm drivers
deadman96385 said:
Sounds like you have a driver issue make sure you install the Qualcomm drivers
Click to expand...
Click to collapse
UPDATE:
figured out what is wrong with QFIL
the Firehose File you send reads only 0 bytes this is why qfil stoped working. might also be the problem with the rest of the flashers i tried.
anycase the elf file in the zip is broken ?
any case you have a .MBN version instat of a .ELF maybe that works ?
Seems im making progress.
im using ToolStudio right now.
the only thing i guess is holding me back is im missing 2 files: RAM and Boot image.
these are not present in the firmware file.
is there anyway i could get them ?
I was trying to switch back to MIUI from LineageOS-14 since my mobile banking apps doesn't run on custom ROM anymore.
However when I'm flashing the fastboot ROM (tgz) to the device using MiFlash, a warning "error:mismatching image and device" apprears.
As I googled for workaround it seems that it can be solved by removing two lines in the flash_*.bat file from the ROM files.
However I Im not sure about this, and therefore need some help here for the best practice on how to solve this, or in such case I've missed out any steps or other thing that may caused the error.
Thank you!
Update, unable to find a convincing solution on the device mismatch error form the Internet. Instead, installing MIUI ROM (zip) via TWRP. No problem at all. Case closed.