Related
i tried to upgrade my s3 i accidentally falshed with correpted file('i renamed the file .mb5 to .tar) it stuck and showing that needed to connect kies
.. and kies not detecting my device and it wont boot into recovery mode but after search i rooted again through cf auto root and then it can enter into recovery mode is it bricked/not what happend to my device currently it can enter into both recovery &download mode ......
pls help me with this
ghjsdf9 said:
i tried to upgrade my s3 i accidentally falshed with correpted file('i renamed the file .mb5 to .tar) it stuck and showing that needed to connect kies
.. and kies not detecting my device and it wont boot into recovery mode but after search i rooted again through cf auto root and then it can enter into recovery mode is it bricked/not what happend to my device currently it can enter into both recovery &download mode ......
pls help me with this
Click to expand...
Click to collapse
Welcome to the forum! Your phone's hardly bricked if you can get to download and recovery modes. Flashing the correct (stock) firmware should get you back to working conditions. What Android version were you on prior to it being stuck and what were you trying to upgrade to?
Larry2999 said:
Welcome to the forum! Your phone's hardly bricked if you can get to download and recovery modes. Flashing the correct (stock) firmware should get you back to working conditions. What Android version were you on prior to it being stuck and what were you trying to upgrade to?
Click to expand...
Click to collapse
THANKS FOR WELCOME PARTY:
and for the rly tooo.
i can get into both download mode as well as recovery mode ..... i'm not clear with my phones model-in odin mode it showing "PRODUCT NAME:-SGH-I747M" on starting it is running 4.1.2 (zsemc1) version i am not clear with baseband etc.
and i'm not clear with supported varient versions when i flashed with different version in odin mode it showing differnt causes for different version
ex: "unsupported dev type","secure check fail sb12",securechech fail aboot" for three different versions
ghjsdf9 said:
THANKS FOR WELCOME PARTY:
and for the rly tooo.
i can get into both download mode as well as recovery mode ..... i'm not clear with my phones model-in odin mode it showing "PRODUCT NAME:-SGH-I747M" on starting it is running 4.1.2 (zsemc1) version i am not clear with baseband etc.
and i'm not clear with supported varient versions when i flashed with different version in odin mode it showing differnt causes for different version
ex: "unsupported dev type","secure check fail sb12",securechech fail aboot" for three different versions
Click to expand...
Click to collapse
i747M is for the Canadian and Mexican variants. If you were on stock 4.1.2, you should be able to Odin back to stock 4.1.1 or upgrade to 4.3 via custom recovery. You can go to the thread below to check the correct stock image for your phone based on carrier. Make sure you use the correct image as flashing the wrong version could hard brick your phone. Download to your PC and then flash. If you select the 4.3 version, you would need to flash custom recovery to your phone via Odin, save the file to a (micro) SD card and then flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=1739426
Let me know if this works for you.
Larry2999 said:
i747M is for the Canadian and Mexican variants. If you were on stock 4.1.2, you should be able to Odin back to stock 4.1.1 or upgrade to 4.3 via custom recovery. You can go to the thread below to check the correct stock image for your phone based on carrier. Make sure you use the correct image as flashing the wrong version could hard brick your phone. Download to your PC and then flash. If you select the 4.3 version, you would need to flash custom recovery to your phone via Odin, save the file to a (micro) SD card and then flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=1739426
Let me know if this works for you.
Click to expand...
Click to collapse
i'm Asian it worked for local networks before bricked so i'm not clear with choosing in versions... ["help me with it"]
ghjsdf9 said:
i'm Asian it worked for local networks before bricked so i'm not clear with choosing in versions... ["help me with it"]
Click to expand...
Click to collapse
If we are going to flash a stock ROM, we would need to flash the correct version as there is risk of a worse brick if we flash the wrong one. When the phone was working normally, the old network would probably be showing during booting. If you got it from abroad, please check if you can get the information from the previous owner. If there is no way of telling the correct firmware, then you can flash custom recovery to the phone and try flashing a custom ROM via recovery. It's always tidier flashing a custom ROM to a device functioning normally but, unless we can be sure of the correct stock firmware to flash, your options may be limited.
Larry2999 said:
If we are going to flash a stock ROM, we would need to flash the correct version as there is risk of a worse brick if we flash the wrong one. When the phone was working normally, the old network would probably be showing during booting. If you got it from abroad, please check if you can get the information from the previous owner. If there is no way of telling the correct firmware, then you can flash custom recovery to the phone and try flashing a custom ROM via recovery. It's always tidier flashing a custom ROM to a device functioning normally but, unless we can be sure of the correct stock firmware to flash, your options may be limited.
Click to expand...
Click to collapse
and finally i found the correct version and when tried to flash through odin i came across this problem
it stuck at "initialization..." [more than hour..] help pls......
ghjsdf9 said:
and finally i found the correct version and when tried to flash through odin i came across this problem
it stuck at "initialization..." [more than hour..] help pls......
Click to expand...
Click to collapse
Sounds like a partition problem. Please let me know the firmware version you are trying to flash.
Larry2999 said:
Sounds like a partition problem. Please let me know the firmware version you are trying to flash.
Click to expand...
Click to collapse
it's version 4.3(I747MVLUEND2_I747MOYBEND2_SPC) at sammobiles.com............
and once "i tried with pit file by marking re partition" will this effect ??????????????
ghjsdf9 said:
it's version 4.3(I747MVLUEND2_I747MOYBEND2_SPC) at sammobiles.com............
and once "i tried with pit file by marking re partition" will this effect ??????????????
Click to expand...
Click to collapse
I've seen this particular problem reported several times and it's always been a problem with the pit file. Flashing a complete stock system should fix all partition problems though. If the stock file you are using is an Odin flashable file, you may try using Odin 3.09. Otherwise, I'd suggest you find a recovery flashable image and flash via (custom) recovery.
Hi Guys!
I need some help here. I have a galaxy s3 I747M . After I loaded the lastest 4.3 Jellybean I lost use of my USB port. I've tried everything I can do to make it work. Nothing has worked. I was on the phone with Samsung for 2 hours trying to fix this issue. I can charge my phone using the port, but that's all I can do. A house hold of Samsung phones, so I have tried all 6 other cables in the house etc. PC's don't see my phone(I've tried 5 different pc's btw) Nothing has worked. The highest Tech support Samsung can offer didn't help either. Seems under my Application manager under all apps. The USB setting is doing absolute nothing. Sitting at 0.00B... Tech guys says something went wrong with the loading of the 4.3 firmware. So he regrets to tell me that my phone is no longer under warranty and there isn't anything he can do. Like I mention I have hard reset to factory settings 4-5 times and nothing works. I know someone is going to say did you check off the Debugging... Yes I have. So there you go. I am unable to use ODIN to reflash firmware because the usb port doesn't work.
If someone can help me, that would be terrific. I should mention that I also tried using the SD Card and tried loading some firmware that I downloaded and tried using the Recovery Option boot to try to load the firmware that I got but I keep getting a error of "E Signature verification failed"
Samsung Galaxy S3
SGH-I747M
4.3 firmware
I747MVLUEMK5
Rogers Network Canada
Did you try different operating systems? You won't be able to load any custom software with a custom recovery.
I haven't no, I'm not sure how I would go about this. Like I mentioned, I've tried to put a md5 on my SD Card and tried to update that way, but keep getting an error. "E Signature verification failure" If I'm way off on how'd I'd do this, please do tell. I'm desperate and am willing to try anything...
BigPapaDune said:
I haven't no, I'm not sure how I would go about this. Like I mentioned, I've tried to put a md5 on my SD Card and tried to update that way, but keep getting an error. "E Signature verification failure" If I'm way off on how'd I'd do this, please do tell. I'm desperate and am willing to try anything...
Click to expand...
Click to collapse
can anyone help me on this???
If you are rooted, and were previously updated to 4.3 firmware, and if im reading correct are just trying to reflash that firmware, you can try using Mobile Odin. It won't flash the full firmware, but will do the kernel, modem, system and cache. Might be worth a shot. Otherwise look for a recovery flashable zip for the firmware. The .tar.md5 can only be used by Odin or Mobile Odin.
DocHoliday77 said:
If you are rooted, and were previously updated to 4.3 firmware, and if im reading correct are just trying to reflash that firmware, you can try using Mobile Odin. It won't flash the full firmware, but will do the kernel, modem, system and cache. Might be worth a shot. Otherwise look for a recovery flashable zip for the firmware. The .tar.md5 can only be used by Odin or Mobile Odin.
Click to expand...
Click to collapse
Hey Thanks for the reply "DocHoliday"
I am not rooted. I wish I was. I've poked around and I'm not sure how to use an .img file. I tried to put it on a micro SD and open it. I get a "E: Signature verification failed" Now all I did was throw the whole zip file on the SD card. Not sure if I have to extract it or what. If you can shed some light on how to do this I'd be a happy camper. All I can find is a JB 4.1.1 flashable zip.. I know i'm 4.3...Will this one work?
No. Do not flash older firmware over 4.3. It'll brick. Older roms are ok, but not the firmware. Can you link to what you are trying to flash? You said you were using an .md5 file earlier, but now you said you tried an .img and a .zip? I'm kinda confused as to exactly what you are trying to flash at this point. Zip files are for flashing in recovery. .tar.md5 files are for Odin. .img files are used differently.
DocHoliday77 said:
No. Do not flash older firmware over 4.3. It'll brick. Older roms are ok, but not the firmware. Can you link to what you are trying to flash? You said you were using an .md5 file earlier, but now you said you tried an .img and a .zip? I'm kinda confused as to exactly what you are trying to flash at this point. Zip files are for flashing in recovery. .tar.md5 files are for Odin. .img files are used differently.
Click to expand...
Click to collapse
Well Doc, I'm kinda confused as well, LOL... I was using odin files at first. not really knowing what i'm doing. I'm kind of starting to understand a few things like, .tar & .md5 files are used with Odin. I can't use odin because my usb on my S3 isn't working. So i'm trying to flash my firmware to either earlier(which I can't because i'm not rooted) or the same. In hopes to try to fix my usb port. My firmware is corrupted. So i've tried to put a stock 4.1.1 recovery zip on my sd card. But when I restart the s3 in recovery mode, and choose the zip file I get "E;signature verification failed" and it does nothing. I can't find a stock img zip file for i747M Rogers canada 4.3... I'm thinking i'm doomed here. What do you think??
I recently attempted to root my phone using this method http://forum.xda-developers.com/showthread.php?t=2387341 however despite ODIN being all OK I got the error Set Warranty Bit : Kernel and the phone would just do nothing after that. Then I tried this method http://forum.xda-developers.com/showthread.php?t=2364980 (although I had to sideload one of the zips rather than copy it) but I still get the same error. I can boot into Recovery and Download mode, but that's it. Thank you for any help.
Update; Now I've got a firmware from Sammobile but whenever I flash it with ODIN I get an error on hidden.img.ext4. Any ideas?
Hi, community
I tried to root my SM G-9600 but it all went wrong. First i went on twrp, it worked, but wiped my entire data. Then i tried make a factory reset o installation with odin and the latest firmware for my device, but it failed and showed this message labeled in red color: "sw rev check fail device 4 binary 3 error". then i found in this and other forums that it was because i used not the latest firmware. I downloaded the latest one, tried once to flash it via ODIN, and it failed again. Then when it restarted this message was shown : " An error has occurred while updating the devide software. Use the Emergency recovery function in the Smart Switch PC software. I donwloaded the smart switch, installed it, plugged my devide, but it shown that my device was "Unsupported". IDK what to do by now, so i need help from anyone on this forum. PLS
Greeting from Peru.
i had the same problem
(before processing to the next step try to redownload the firmware, i think i was using an old firmware and this is why i got this error)
i am assuming that you can not boot on twrp recovery
that's not a problem , you need to install twrp via odin and boot directly to it....
format the data and connect to your laptop (if it does recognize the phone but there is no storage dont worry, just reboot again to recovery (there is an option on reboot tab))
since you already tripped the knox just flash a custom rom, boot and set it up, and then try to flash stock image via odin as normal.
and sorry for my bad english.
Cant install a custom rom
Thanks. I made posible the TWRP installation, root, but i cannot install any custom rom i have. Can you suggest any one that will be suitable for my device (SM G-9600) ?, thats Samsung Galaxy S9 g9600 (Snapdragon SoC)
dimitrispas22 said:
i had the same problem
(before processing to the next step try to redownload the firmware, i think i was using an old firmware and this is why i got this error)
i am assuming that you can not boot on twrp recovery
that's not a problem , you need to install twrp via odin and boot directly to it....
format the data and connect to your laptop (if it does recognize the phone but there is no storage dont worry, just reboot again to recovery (there is an option on reboot tab))
since you already tripped the knox just flash a custom rom, boot and set it up, and then try to flash stock image via odin as normal.
and sorry for my bad english.
Click to expand...
Click to collapse
Thanks. I made posible the TWRP installation, root, but i cannot install any custom rom i have. Can you suggest any one that will be suitable for my device (SM G-9600) ?, thats Samsung Galaxy S9 g9600 (Snapdragon SoC)
Stevie1997 said:
Thanks. I made posible the TWRP installation, root, but i cannot install any custom rom i have. Can you suggest any one that will be suitable for my device (SM G-9600) ?, thats Samsung Galaxy S9 g9600 (Snapdragon SoC)
Click to expand...
Click to collapse
do you want to install a custom rom or revert back to stock?
For custom ROM I suggest Soldiers ROM here's the link to the thread. https://forum.xda-developers.com/ga...g96xf-fd-n-stock-rom-soldier9312-1-0-t3771346 . You can more information about it on the thread. Been using the moment I rooted my phone.
Xspidera said:
For custom ROM I suggest Soldiers ROM here's the link to the thread. https://forum.xda-developers.com/ga...g96xf-fd-n-stock-rom-soldier9312-1-0-t3771346 . You can more information about it on the thread. Been using the moment I rooted my phone.
Click to expand...
Click to collapse
i think he is out of lack it looks like he doesn't know exactly his model snapdragon samsung devices are different from our g960f exynos version and it may brick his device
i think hes only option is to flash the stock firmware and yea just that....
Hi,
I have a Samsung A32 SM-A325F and the bootloader is not unlocked.
The device was running Android 12 and i decided to update to Android 13 via OTA update; so i downloaded the OTA update and clicked 'install', then the device rebooted trying to apply that update but something went wrong and now the device is in bootloop, recovery and download mode are both accessible.
I already tried to download various firmwares (Android 12 and 13).
I tried to flash these firmwares both ways through SD Card and Odin (As Admin) and all flashed successfully but nothing changed, still in bootloop.
It's important for me to don't erase DATA (I flashed the firmwares with HOME_CSS and not the stock CSS, so DATA wouldn't be formatted)!
If someone knows how to fix this i would appreciate a comment,
Thanks.
Quark Thonos said:
Hi,
I have a Samsung A32 SM-A325F and the bootloader is not unlocked.
The device was running Android 12 and i decided to update to Android 13 via OTA update; so i downloaded the OTA update and clicked 'install', then the device rebooted trying to apply that update but something went wrong and now the device is in bootloop, recovery and download mode are both accessible.
I already tried to download various firmwares (Android 12 and 13).
I tried to flash these firmwares both ways through SD Card and Odin (As Admin) and all flashed successfully but nothing changed, still in bootloop.
It's important for me to don't erase DATA (I flashed the firmwares with HOME_CSS and not the stock CSS, so DATA wouldn't be formatted)!
If someone knows how to fix this i would appreciate a comment,
Thanks.
Click to expand...
Click to collapse
there's no way to solve it without wiping /data or taking to samsung
i think the only way you could solve it is by NAND Erasing and repartitioning the phone using a .pit file, but afaik that uses odim...
applesucksLmao said:
there's no way to solve it without wiping /data or taking to samsung
i think the only way you could solve it is by NAND Erasing and repartitioning the phone using a .pit file, but afaik that uses odim...
Click to expand...
Click to collapse
I double that. Only complete re-flashing. Here are the instructions. And here you can download the full stock firmware.
Ok,
Thank you.
Quark Thonos said:
Hi,
I have a Samsung A32 SM-A325F and the bootloader is not unlocked.
The device was running Android 12 and i decided to update to Android 13 via OTA update; so i downloaded the OTA update and clicked 'install', then the device rebooted trying to apply that update but something went wrong and now the device is in bootloop, recovery and download mode are both accessible.
I already tried to download various firmwares (Android 12 and 13).
I tried to flash these firmwares both ways through SD Card and Odin (As Admin) and all flashed successfully but nothing changed, still in bootloop.
It's important for me to don't erase DATA (I flashed the firmwares with HOME_CSS and not the stock CSS, so DATA wouldn't be formatted)!
If someone knows how to fix this i would appreciate a comment,
Thanks.
Click to expand...
Click to collapse
After downgrading android or any firmware is mandatory a format of the /data filesystem, otherwise, bootloop will happen. Maybe try setting up adb and pulling your files via the recovery mode.
Quark Thonos said:
Hi,
I have a Samsung A32 SM-A325F and the bootloader is not unlocked.
The device was running Android 12 and i decided to update to Android 13 via OTA update; so i downloaded the OTA update and clicked 'install', then the device rebooted trying to apply that update but something went wrong and now the device is in bootloop, recovery and download mode are both accessible.
I already tried to download various firmwares (Android 12 and 13).
I tried to flash these firmwares both ways through SD Card and Odin (As Admin) and all flashed successfully but nothing changed, still in bootloop.
It's important for me to don't erase DATA (I flashed the firmwares with HOME_CSS and not the stock CSS, so DATA wouldn't be formatted)!
If someone knows how to fix this i would appreciate a comment,
Thanks.
Click to expand...
Click to collapse
Flash your device using SP flash tool.
Please make a scatter firmware first using the odin files and then flash the phone in BROM mode.