[Q] Soft brick S6 ( SM-G920F) 5.1.1.
Tried to flash it with S6_UniKernel_v8-0002-ODIN, cf-autoroot, and it did only say pass and the phone started to reboot but it didnt get pass the logo part. So I tried to go back to stock firmware, and it only got fail so I tried with 5.0.2 instead and that didnt work either. Both case gave me this kind of error.
The firmware was from sammobile.
I didnt saw OEM in "Developer options" hope that I didnt miss it, but some post did say some phone have bootloader unlocked at start, so it should be noproblem to flash the phone. But it didnt work out for me so well.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOCV_G920FTEF1AOC1_G920FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
KFelix said:
.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOCV_G920FTEF1AOC1_G920FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Install Smart Switch (Kies for newer models) on a computer, and use the option Emergency software recovery and initialization.
cf-autoroot is outdated, and you can't downgrade to 5.0.2 after you've had 5.1.1
Try to flash the kernel again and see if it boots. Otherwise do what the previous post says.
Also, flashing unikernel would have rooted it with no other steps needed.
Calnyx said:
cf-autoroot is outdated, and you can't downgrade to 5.0.2 after you've had 5.1.1
Try to flash the kernel again and see if it boots. Otherwise do what the previous post says.
Also, flashing unikernel would have rooted it with no other steps needed.
Click to expand...
Click to collapse
I tried to connect phone with Kies, nothing happend, just "connecting.." what can I do?
Tried flashing kernel alot of times, same problem .
Just re-read his post, one small problem, the box i have is a bit damage and i can't find the S/N , is there any chance I can get the S/N , I have the ART code and some numbers under a bar but wasn't the S/N with numbers and chars?
Thanks for the help
Can't find the S/N on my box due to damage , is there other way? Do they still have the S/N inprinted under the battery? And when I'am in Odin "Binary : Custom , System : Official , Knox : 1" So it did someone "half-rooted" it or something but I have tried to reflash unikernel v8 still the same problem, is there any way to fix it without going back to the latest stable firmware with the S/N in Kies?
first you should flash TWRP recovery in Odin from here https://dl.twrp.me/zeroflte/
for Odin you need the file with .tar at the end.
Then you can try Adam Kernel by Wanam from here http://forum.xda-developers.com/galaxy-s6/orig-development/kernel-adam-kernel-t3093569
and you can try Wanam Rom from here http://forum.xda-developers.com/galaxy-s6/development/mod-wanamlite-1-0-t3095155
in this is the Kernel included.
I use his ROM my self without any problems.
Ghostrider
Ghostrider said:
first you should flash TWRP recovery in Odin from here https://dl.twrp.me/zeroflte/
for Odin you need the file with .tar at the end.
Then you can try Adam Kernel by Wanam from here http://forum.xda-developers.com/galaxy-s6/orig-development/kernel-adam-kernel-t3093569
and you can try Wanam Rom from here http://forum.xda-developers.com/galaxy-s6/development/mod-wanamlite-1-0-t3095155
in this is the Kernel included.
I use his ROM my self without any problems.
Ghostrider
Click to expand...
Click to collapse
Wow, dont know what to say but this did WORK , didn't know that I could open TWRP, because I tried to go to recovery mode but the phone didn't react so I just thought it was messed up. Thanks friend.
you're Welcome
good to hear it Worked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
I have followed many tutorials to the T and I have flashed with philz_touch_6.55.0-p5110 and GT-P5110_ClockworkMod-Recovery_6.0.1.0 to absouetely no avail whatsoever.
My counter is up to 15 and when I go into the recovery mode I get the default. I cannot for the life of me get the tablet to launch the recovery screens.
I have been at this for 4hours. I cant even update the device as it says the device altered. It also show custom , yet I CANNOT load the recovery other than the default.
What am I missing?
Android 4.2.2
Table: GT-P5113
More details:
From ODIN:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.5.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Odin both 3.5 and 1.85 I tried. Both say pass. I am completely and totally frustrated.
kjsphoto said:
I have followed many tutorials to the T and I have flashed with philz_touch_6.55.0-p5110 and GT-P5110_ClockworkMod-Recovery_6.0.1.0 to absouetely no avail whatsoever.
My counter is up to 15 and when I go into the recovery mode I get the default. I cannot for the life of me get the tablet to launch the recovery screens.
I have been at this for 4hours. I cant even update the device as it says the device altered. It also show custom , yet I CANNOT load the recovery other than the default.
What am I missing?
Android 4.2.2
Table: GT-P5113
More details:
From ODIN:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.5.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Odin both 3.5 and 1.85 I tried. Both say pass. I am completely and totally frustrated.
Click to expand...
Click to collapse
Flash recovery in Odin again but this time with auto reboot UNCHECKED. After it flashes, wait 10 seconds, unplug tablet, and boot into recovery (hold in combo until you see recovery screen. It will exit download mode.) Wipe cache and Dalvik and reboot. I'd recommend flashing @Android-Andi's TWRP for a good touch based recovery.
Sent from my SGH-T989
jrc2 said:
Flash recovery in Odin again but this time with auto reboot UNCHECKED. After it flashes, wait 10 seconds, unplug tablet, and boot into recovery (hold in combo until you see recovery screen. It will exit download mode.) Wipe cache and Dalvik and reboot. I'd recommend flashing @Android-Andi's TWRP for a good touch based recovery.
Sent from my SGH-T989
Click to expand...
Click to collapse
Thank you very much! Once I unchceked the re-boot and then rebooted holding down the key it worked!
I am not sure what you mean by the TWRP flash?
Again, thank you very much for y our help..
Kindest Regards...
kjsphoto said:
Thank you very much! Once I unchceked the re-boot and then rebooted holding down the key it worked!
I am not sure what you mean by the TWRP flash?
Again, thank you very much for y our help..
Kindest Regards...
Click to expand...
Click to collapse
TWRP is another recovery. @Android-Andi has a recovery thread in the development section. If you go to his download page, there is a .zip and a .tar file. The .tar is for Odin and the .zip is if you want to flash it in your current recovery. You just choose one file and flash it accordingly.
Sent from my SGH-T989
Hi folks .
Present some servise firmwares , including BL , AP , CP , CSC with PIT-file , for SM-T53X and SM-T33X .For KitKat and Lollipop .
Flash via Odin .
Link https://www.androidfilehost.com/?w=files&flid=35515
Don't forget press "Thanks" button
I added a few firmware
Added few firmwares for Tab 4 8.0 (5.1.1)
service firmwares will come as OTA updates?
patsio said:
service firmwares will come as OTA updates?
Click to expand...
Click to collapse
Flash via Odin .
Click to expand...
Click to collapse
Read OP
repey6 said:
Read OP
Click to expand...
Click to collapse
Yes, i only wondered if service firmwares will come later as OTA updates. I got Galaxy 335, i guess SM-T335XXU1BOF8_AUT_SERVICE_LP_5.1.1 is for me as i'm on LP T335XXU1BOF8_T335OXA1BOF8_T335XXU1BOF3_Home.
patsio said:
Yes, i only wondered if service firmwares will come later as OTA updates. I got Galaxy 335, i guess SM-T335XXU1BOF8_AUT_SERVICE_LP_5.1.1 is for me as i'm on LP T335XXU1BOF8_T335OXA1BOF8_T335XXU1BOF3_Home.
Click to expand...
Click to collapse
Yes it is . Why do you want Service firmware ?
repey6 said:
Yes it is . Why do you want Service firmware ?
Click to expand...
Click to collapse
Because ServiceFirmware updates offer the latest stability enchancements, security buf fixes etc, right? By the way, the zip contains 4 files, could you pls explain what each file initials stand for?
Thanks!
patsio said:
Because ServiceFirmware updates offer the latest stability enchancements, security buf fixes etc, right? By the way, the zip contains 4 files, could you pls explain what each file initials stand for?
Thanks!
Click to expand...
Click to collapse
The main difference between a service firmware from a usual stock - forced reset to factory settings and provided wipe system (command "csc = factory" in the file on the way cache.img/recovery/command; for regular firmware it looks like "csc = home"). CSC file contains PIT-file to force the file system layout verification.
Caution! Service firmware produces wipe user data:
- removes section USERDATA and recreate it with the factory settings;
- removes SD-CARD partition and recreate it with the factory settings (format Internal sd-card).
It makes:
- the system state official: in Downloading mode Current Binary: Official and System Status: Official;
@repey6, I read the complete thread, but I'm still not clear on which of these files I should flash. Do I only flash AP_T530XXU1BOD8_CL4741109_QB4756762_REV00_user_low_ship_MULTI_CERT.tar.md5, or all 3? And if all 3, in which order? (Asking here, since I don't want spam sub77's ROM thread)
SomeDuder said:
@repey6, I read the complete thread, but I'm still not clear on which of these files I should flash. Do I only flash AP_T530XXU1BOD8_CL4741109_QB4756762_REV00_user_low_ship_MULTI_CERT.tar.md5, or all 3? And if all 3, in which order? (Asking here, since I don't want spam sub77's ROM thread)
Click to expand...
Click to collapse
All three files simultaneously .
repey6 said:
All three files simultaneously .
Click to expand...
Click to collapse
What, like so?:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cuz I did that, and it seems to only flash the stock ROM. Anyway, the result is the same - it keeps stuck at the bootlogo and, after a while, becomes responsive to touch, but with no screen updates...
SomeDuder said:
What, like so?:
Cuz I did that, and it seems to only flash the stock ROM. Anyway, the result is the same - it keeps stuck at the bootlogo and, after a while, becomes responsive to touch, but with no screen updates...
Click to expand...
Click to collapse
Try to reflash again and tick re-partition checkbox
I did:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_T530XXU1BOD8_CL4741109_QB4756762_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_BTU_T530BTU1BOE1_CL4973560_QB5048859_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_T530XXU1BOD8_CL4741109_QB4756762_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Le proof (Click for image).
It says I've got firmware/bootloader (I don't think there's a way to tell which version of the BL you have) version T530XXU1BOD8, so that seems to be the same as the Lollipop stock ROM (T530XXU1BOD8_T530OXA1BOD8_HOME.tar.md5).
It still won't boot into anything resembling an OS, but I'm gonna go through the whole TWRP and CM installation again. Who knows, maybe it'll do the trick.
I'm afraid this is a different problem tho, like it's not loading the correct display drivers or something...
After flashing you must hear Samsung music normal and wait 8-10 min
repey6 said:
After flashing you must hear Samsung music normal and wait 8-10 min
Click to expand...
Click to collapse
Yup, heard the startup tune, Kies recognized my device again:
(And I let it update the firmware to the latest official whatever)
But it still will not show anything else than the bootlogo as I'm writing this (+10 minutes). I'll keep it plugged in for the rest of the afternoon, maybe something will happen. If not, I'll try again in a few months, maybe it's just some weird bug with the device, idk.
Anyway, thank you for your assistance @repey6!
SomeDuder said:
Yup, heard the startup tune, Kies recognized my device again:
(And I let it update the firmware to the latest official whatever)
But it still will not show anything else than the bootlogo as I'm writing this (+10 minutes). I'll keep it plugged in for the rest of the afternoon, maybe something will happen. If not, I'll try again in a few months, maybe it's just some weird bug with the device, idk.
Anyway, thank you for your assistance @repey6!
Click to expand...
Click to collapse
Strange all . Try to go to stock recovery and do factory reset . May be this help ?
Good afternoon. I have next situation - my phone stucks on the label of "Samsung Galaxy s6". I can't enter to recovery mode, only to downloading mode. When flashing rom via odin everything passes without errors, but the phone does not boot further "Samsung Galaxy s6". If i turn it off and connect to charger it shows the same inscription but does not indicate charging. This rom was flashing by odin G920FXXU5DQA8_G920FOXE5DQA3_G920FXXU5DPL3_HOME.tar.md5 but nothing did not help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
Have you tried flashing a custom recovery and booting to it? Maybe something is broken and you may need to wipe the partition...
All the best,
~Lord
Sent from my Galaxy S7 Edge (SM-935F) using Tapatalk Beta
I have tried to flash but received message "recovery is not seandroid enforcing"
I just flashed twrp, but i can not enter to recovery mode.
Odin log is
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1205)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
just flash cf auto root for your model
flyinginthedreams said:
I have tried to flash but received message "recovery is not seandroid enforcing"
Click to expand...
Click to collapse
My Samsung S4 Value Edition also stucked for months. I used original charger to charge and power on. It worked and it is working till now. I kept that mobile for around 1 year. Tried all of my best thing i could do. Later on the charger was the problem.
i did, the same result
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
and now have message " Recovery is not seandroid enforsing"
flyinginthedreams said:
i did, the same result
and now have message " Recovery is not seandroid enforsing"
Click to expand...
Click to collapse
Ok, but is it still stuck on logo while booting?
As for the message you can ignore it, same as kernel is not seandriod enforcing while booting.
If you want not to have these messages, run emergency initialization via Smart Switch, you can check my topics, made instructions with screenshots on how to use it to flash stock fw and stock recovery, but if DRK is messed up it will still be stuck on logo with official fw.
What I would do if I were you is:
1. run emergency initialization via Smart Switch - this will make phone stock, but like I said above it will be stuck on logo, because DM verity would fail if DRK is messed up.
2. flash cf auto root via Odin - custom kernel which bypass DM verity check - nevermind the seandroid enforcing messages, they are normal.
At this point you should have a bootable rooted phone with stock fw and stock recovery.
brenner650 said:
Ok, but is it still stuck on logo while booting?
As for the message you can ignore it, same as kernel is not seandriod enforcing while booting.
If you want not to have these messages, run emergency initialization via Smart Switch, you can check my topics, made instructions with screenshots on how to use it to flash stock fw and stock recovery, but if DRK is messed up it will still be stuck on logo with official fw.
Click to expand...
Click to collapse
Yes, nothing did not change. Same logo
flyinginthedreams said:
Yes, nothing did not change. Same logo
Click to expand...
Click to collapse
even with cf autoroot flashed afterwards?
brenner650 said:
even with cf autoroot flashed afterwards?
Click to expand...
Click to collapse
yes
That is weird, maybe try any other kernel, or flash full fw with corresponding pit, but it looks like hw to me
brenner650 said:
That is weird, maybe try any other kernel, or flash full fw with corresponding pit, but it looks like hw to me
Click to expand...
Click to collapse
when i try to flash anything i receive every time that
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
flyinginthedreams said:
when i try to flash anything i receive every time that
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
Click to expand...
Click to collapse
It looks like it has been flashed successfully.
Is it the same with Smart Switch emergency initialization with sn of the phone, and flashing custom kernel afterwards?
I had the same problem.
In the laboratory they told me that my processor has been burned...
Sent from my Redmi 3S using Tapatalk
Hi everyone,
I've been trying the whole afternoon to fix my cellphone with my limited knowledge on Android. My cellphone tried to update his firmware yesterday but it showed an error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Than I plugged my cellphone with SmartSwitch but it bricked the cellphone and suggested to use the Emergency Recovery, which didn't work (stop at 83% and show an error message). I downloaded the ROM to be installed with Odin (G920W8VLU5DQI2_G920W8OYA5DQI2_G920W8VLU5DQI2_HOME.tar.md5) but still not working.
Then I tried to install a previous ROM but I keep getting fail on Odin:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On phone:
Odin mode
PRODUCT NAME: SM-6920W8
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0X0500)
APSWREV: B:4 K:2 S:2
SECURE CHECK FAIL: (PIT)
I was able to reach once the boot recovery menu on the phone but by trying to reinstall the ROM, I came back to the start point. Since, I no more reached that menu again.
That galaxy S6 was provided by Koodo here in Canada.
Can someone help me to go through this process please.
Thanks so so much for your support
dragonwood said:
Hi everyone,
I've been trying the whole afternoon to fix my cellphone with my limited knowledge on Android. My cellphone tried to update his firmware yesterday but it showed an error
Than I plugged my cellphone with SmartSwitch but it bricked the cellphone and suggested to use the Emergency Recovery, which didn't work (stop at 83% and show an error message). I downloaded the ROM to be installed with Odin (G920W8VLU5DQI2_G920W8OYA5DQI2_G920W8VLU5DQI2_HOME.tar.md5) but still not working.
Then I tried to install a previous ROM but I keep getting fail on Odin:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On phone:
Odin mode
PRODUCT NAME: SM-6920W8
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0X0500)
APSWREV: B:4 K:2 S:2
SECURE CHECK FAIL: (PIT)
I was able to reach once the boot recovery menu on the phone but by trying to reinstall the ROM, I came back to the start point. Since, I no more reached that menu again.
That galaxy S6 was provided by Koodo here in Canada.
Can someone help me to go through this process please.
Thanks so so much for your support
Click to expand...
Click to collapse
Actually I downloaded the original PIT file of my cellphone and went around the security and it worked.!!
Hey guys
I did the update from marshmallow to nougat on my J7 Prime G610F
But I found any problems in the process:
I tried update the nougat via Odin and appear an error for me about Pit file.
So I watched a video that a guy was using miracle to get pit file, but I didn't know what the miracle was. So I repeated the process that the guy did and my cellphone was updated to nougat( video)
But I think something is wrong, since the firmware file comes with 5 files and I used only one and my cellphone was update to nougat
Now I'm trying to use Odin to update the other files and I can't. I've already tried to use PIT file from backup that the miracle did, unsucessfully. Pit file from the CSC file on firmware folder, same thing. I downloaded some pit files from sammobile site, same thing.
here are some bugs that have been returned to me
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> userdata.img
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> userdata.img
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> userdata.img
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
I tried remove the pit file from csc and update, selecting an external pit file. Unsucessfull every time.
This was a firmware I used: ROM 1_G610FDDU1BQH9_INDIA_7.0
Cell phone is working so far, showed no error.
In Phone INFO:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
I downloaded another version of firmware, from sammobile.
G610FXXU1BRB4_G610FODI1BRB4_INS.zip - India
But I'll wait for someone to give me a hand to proceed.
Sorry for my bad english.
I'm grateful already.
I downloaded another version of firmware, from sammobile.
G610FXXU1BRB4_G610FODI1BRB4_INS.zip - India
But I'll wait for someone to give me a hand to proceed.
Click to expand...
Click to collapse
I got flash the AP and HOME CSC, but I can't flash BL and CP (including my 4g is not working, because that, i think)
I noticed that there are different models 610f and 610f / ds (my model). Can this be the problem? if that's the problem, where can I find the rom for my model?
Maybe I can't help you that much but I only know you must flash the right .pit file with the stock rom. I did this on my SM-J700F and everything worked, before that my phone was dead for me. Just Google your phone models pit file, finding that file wasn't easy for me but I found it. You can also use SamFirm, a tool that I found in XDA. You can download your stock ROM (for Samsung) with fullspeed, and it is also reliable. The STOCK ROM should everytime work right with the right STOCK ROM file and the right PIT file. I found that link on the internet I can't guarantee it's the right one. You can also Google it yourself from a reliable resource. But I don't think it's wrong.
The PIT File----dosya.co/0zv84005icrk/SM-G610F_7-4-2017_10-0-3.pit.html
If you are using a Custom ROM read this:
And I had another problem, the ROM didn't even recognize my SIM card. there is actually nothing much to do. I heard much about methods. Some say if you are using something like Cyanogenmod or LineageOS try disabling System profiles, or take a backup of your stock ROM's Radio and EFS and restore them in your new ROM. Nothing worked for me. My ROM's developer published a new version of the ROM and that solved it. But If you are not good enough to edit the ROM then there is not something I think you can do.
I hope I solved your problem...