Hello, greetings from Venezuela! (sorry for my english)
Here's my problem. i recently got a Samsung Galaxy S3 mini GT-I8200. everyting looks good for me for a moment after i started to use the phone. it keeps restating, more often if i'm connect to wifi. the weird thing is. when it turns on again, everything i've done is gone, and it have the configurating from before. i've tried to install the stock rom again through Odin but it fails after the first step of copying into NAND. A closer look at the device made me think that it have a wrong rom installed. i don't know if that is a motive to the phone to behave like that.
look at the differences:
this is what it says in the sticker behind the battery:
{
"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"
}
it clearly say: GT-I8200. but when i turn on the device, in the logo says GT-I8200L
even the IMEI is different from the one in the sticker:
here's all i've done so far.
enter recovery mode. wipe data/ factory reset it pass but won't work. wipe cache partition throw an error and restart.
Note: in the bottom of the screem appers this message:
when i try the Odin, i get this as soon as it start to copy the files into the phone (i've used three different Stock rooms from different countries but i get the same in all):
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8200LUBUANI1_I8200LZTOANI1_I8200LUBUANI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> timh.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> obm.bin
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
here is capture of the event:
i've tried PIT/re-partition and i got the same after start. i dunno what else to do. i try even take the phone to a Repair shop and they say it's the mother board. is it true? i even came to think it's the NAND memory, and i've read that i need something called JTag.
All replies will be good. thank you for reading
AxLRuleX said:
Hello, greetings from Venezuela! (sorry for my english). Here's my problem. i recently got a Samsung Galaxy S3 mini GT-I8200. everyting looks good for me for a moment after i started to use the phone. it keeps restating, more often if i'm connect to wifi. the weird thing is. when it turns on again, everything i've done is gone, and it have the configurating from before...
Click to expand...
Click to collapse
I don't have this device but, you should be able to obtain some member guidance within one of the following threads specific to your device.
https://forum.xda-developers.com/showthread.php?t=2826565
https://forum.xda-developers.com/showthread.php?t=2990545
https://forum.xda-developers.com/showthread.php?t=2662082
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I don't have this device but, you should be able to obtain some member guidance within one of the following threads specific to your device.
https://forum.xda-developers.com/showthread.php?t=2826565
https://forum.xda-developers.com/showthread.php?t=2990545
https://forum.xda-developers.com/showthread.php?t=2662082
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thank you for your answer, but those threads are dead, as my phone guess i'll have to resign that it's gone for good.
AxLRuleX said:
Thank you for your answer, but those threads are dead, as my phone guess i'll have to resign that it's gone for good.
Click to expand...
Click to collapse
Unfortunately, it sounds like two different things are going on. First, the random reboots with loss of data does suggest bad NAND to me. And that's the ultimate problem. Secondly, it sound like whomever owned the phone before you attempted to fix it, got desperate, and flashed the i8200L ROM image. This shouldn't kill it though... that NAND being bad is the real issue, and yes, I think the phone is indeed done for.
Related
So after replacing the digitizer I can't boot up the phone. As I've said in title, I'm stuck at the 'Samsung Galaxy Core 2, powered by android' screen.
I tried to re-flash the stock ROM via Odin, everything passes but i always get stuck at the same boot spot.
Power+VolUp+Home doesn't work, only Power+VolDown+Home work.
Does anyone have any suggestion what to do?
electrified said:
So after replacing the digitizer I can't boot up the phone. As I've said in title, I'm stuck at the 'Samsung Galaxy Core 2, powered by android' screen.
I tried to re-flash the stock ROM via Odin, everything passes but i always get stuck at the same boot spot.
Power+VolUp+Home doesn't work, only Power+VolDown+Home work.
Does anyone have any suggestion what to do?
Click to expand...
Click to collapse
i have the same problem!!!!!
please if anyone knows help
---------- Post added at 11:32 AM ---------- Previous post was at 10:43 AM ----------
i found the solution my friend,you have to let the phone boot with the old digitizer,then when the boot its complete,remove the lcd and digitizer,replace with the new digitizer but be carefull the phone has to stay on .and conect back the lcd and its works but if you reboot the phone will stuck again.this is my short fix.
i hope i helped
Hi guys same problem
have you found a solution ?
electrified said:
So after replacing the digitizer I can't boot up the phone. As I've said in title, I'm stuck at the 'Samsung Galaxy Core 2, powered by android' screen.
I tried to re-flash the stock ROM via Odin, everything passes but i always get stuck at the same boot spot.
Power+VolUp+Home doesn't work, only Power+VolDown+Home work.
Does anyone have any suggestion what to do?
Click to expand...
Click to collapse
did u wipe the data?
Azhero said:
did u wipe the data?
Click to expand...
Click to collapse
No, i couldn't access anything, and i haven't found any solution.. sold the phone as is.
electrified said:
No, i couldn't access anything, and i haven't found any solution.. sold the phone as is.
Click to expand...
Click to collapse
do you still have the same problem? i fix somebody's phone last week with this kind of issue...
alexutpangsut said:
do you still have the same problem? i fix somebody's phone last week with this kind of issue...
Click to expand...
Click to collapse
Yep i got this problem i can rec video
this all logs
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G355HXXU0ANJ3_G355HOXE0ANJ3_G355HXXU0ANJ3_REV04_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<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> BL_G355HXXU0ANHB_2631775_REV04_user_low_ship.tar.md5 is valid.
<OSM> AP_G355HXXU0ANHB_2631775_REV04_user_low_ship.tar.md5 is valid.
<OSM> CP_G355HXXU0ANHB_2631775_REV04_user_low_ship.tar.md5 is valid.
<OSM> CSC_OXE_G355HOXE0ANHB_2631775_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
______________________________________________________________________________
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
View attachment 3245449
Similar Problem [PLEASE HELP]
electrified said:
So after replacing the digitizer I can't boot up the phone. As I've said in title, I'm stuck at the 'Samsung Galaxy Core 2, powered by android' screen.
I tried to re-flash the stock ROM via Odin, everything passes but i always get stuck at the same boot spot.
Power+VolUp+Home doesn't work, only Power+VolDown+Home work.
Does anyone have any suggestion what to do?
Click to expand...
Click to collapse
I am experiencing a similar problem with my Samsung Galaxy Core Prime.
I used Kingroot to root my device. I then continued to attempt to install a custom recovery which i eventually accomplished about three hours later, and then attempted to install a custom rom(I don't know if it worked or not!) 9 hours later, I tried to reboot my device. When i turned my phone back on, the screen froze and would not finish booting. (Volume Up+Home+Power and Volume Down+Home+Power both work. I can select different options in bootloader, but when i go to the download page it also freezes)
{
"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"
}
aadonald55 said:
I am experiencing a similar problem with my Samsung Galaxy Core Prime.
I used Kingroot to root my device. I then continued to attempt to install a custom recovery which i eventually accomplished about three hours later, and then attempted to install a custom rom(I don't know if it worked or not!) 9 hours later, I tried to reboot my device. When i turned my phone back on, the screen froze and would not finish booting. (Volume Up+Home+Power and Volume Down+Home+Power both work. I can select different options in bootloader, but when i go to the download page it also freezes)
Click to expand...
Click to collapse
Don't worry
Just download stock firmware from sammobile.com and odin v3.0.9 and download samsung mobile drivers for pc. Then open download mod by pressing vol down +power+ home button and then open odin and choose downloaded firmware as pda and flash it. Now you can see a blue coloured progress bar on download mod. After it completes, it will reboot your device and it will boot successfully
Sent from my GT-I8262 using XDA-Developers mobile app
TEOKARAFOU said:
i have the same problem!!!!!
please if anyone knows help
---------- Post added at 11:32 AM ---------- Previous post was at 10:43 AM ----------
i found the solution my friend,you have to let the phone boot with the old digitizer,then when the boot its complete,remove the lcd and digitizer,replace with the new digitizer but be carefull the phone has to stay on .and conect back the lcd and its works but if you reboot the phone will stuck again.this is my short fix.
i hope i helped
Click to expand...
Click to collapse
it's work....thx...just use old digitizer first...then change with new digitizer..phone stay on
---------- Post added at 06:22 PM ---------- Previous post was at 06:16 PM ----------
lupo77 said:
Hi guys same problem
have you found a solution ?
Click to expand...
Click to collapse
just use old digitizer / touchscreen .... and you can do hard reset (power + up key + home key)
......try change new touchscreen phone stay on (insert battery)
electrified said:
So after replacing the digitizer I can't boot up the phone. As I've said in title, I'm stuck at the 'Samsung Galaxy Core 2, powered by android' screen.
I tried to re-flash the stock ROM via Odin, everything passes but i always get stuck at the same boot spot.
Power+VolUp+Home doesn't work, only Power+VolDown+Home work.
Does anyone have any suggestion what to do?
Click to expand...
Click to collapse
See the phone model back to the cover.. Maybe you have galaxy core 2 sm-355hn and you have ordered digitizer for sm-355h that it doesn't fit
{
"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"
}
Visit galaxynroms.blogspot.com.
Disclaimer:
I/XDA/is not responsible for any kind of damage to your device,
or in case it explodes, etc.
Please use it at your own risk! Whatever you do with your phone it's your own choice!
Click to expand...
Click to collapse
Requirement:
1. PC/Laptop/Netbook.
2. Odin3 v3.09 or any other
3. TWRP_SM-G355H_V2.8.4.0.7z
4. TWRP_v2.8.4.0_by_Dhruvit_(flashable).zip
5. Samsung USB Driver
6. USB Cable.
Click to expand...
Click to collapse
How to install:
Tutorial 1 : By Odin
1. Install Samsung USB Driver on your PC/Laptop or something else
2. Extract odin and TWRP_SM-G355H_V2.8.4.0.7z in the same folder
3. Open Odin
4. Reboot phone in Download Mode by pressing and hold Home + Power + Volume Down buttons)
5. Connect phone and wait until detected on odin
6. Add the recovery.tar.md5 file to AP / PDA
7. Make sure re-partition is NOT ticked
8. Click the start button, sit back and wait a few minutes
9. Wait until the flashing process is complete.
Click to expand...
Click to collapse
Tutorial 2 : By Stock Recovery / CWM
1. Copy TWRP_v2.8.4.0_by_Dhruvit_(flashable).zip to External SD.
2. Go to Stock Recovery / CWM.
3. Install zip -> from sdcard.
4. Choose TWRP_v2.8.4.0_by_Dhruvit_(flashable).zip and wait until finished.
5. Reboot system now.
Click to expand...
Click to collapse
How to go in Recovery:
1. Turn off your phone
2. Press and hold together Volume up + Home + Power buttons until phone vibrate then let go.
3. Now you are in recovery mode.
Click to expand...
Click to collapse
Warning:
Please do not try to repartition ext-sd with TWRP.
Credits goes to:
- TeamWin
- OmniROM (for bootable recovery)
- CyanogenMod (for sources)
- Y300-0100 (for device configs)
- Me (Dhruvit Pokharna)
- And all who contributed
Version Information
Status: Working
Created 2015-01-25
Last Updated 2015-01-25
IF YOU WANNA RESHARE THIS RECOVERY, PLEASE FOLLOW THIS RULES :
1. DON'T USE SHORTENER LINK (i.e. adfly, adfoc, etc)
2. DONT REUPLOAD MY TWRP BEFORE ASKING PERMISSIONS
Update- 2.8.5.0
- TWRP_SM-G355H_V2.8.5.0_By_Dhruvit_(odin).7z
- TWRP_v2.8.5.0_by_Dhruvit_(flashable).zip
Init.d support - Link
Do follow on Instagram- instagram.com/the_dhruv7
Dont forget to click thanks button
pls. OP can u attach the recovery here. . .I couldn't download from your link. .
I upload it on 4shared
http://www.4shared.com/archive/Y6dbMcbAba/TWRP_SM-G355H_V2840.html
@Dhruvit Pokharna : how do you enable cpu temperature on TWRP ?
Device configs - https://github.com/Y300-0100/twrp_samsung_kanas3gnfcxx?files=1
Android bootable recovery folder - https://github.com/omnirom/android_bootable_recovery?files=1
You should use Y300-0100 device config
I have some error when flashing TWRP
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
site - http://galaxynroms.weebly.com/twrp-touch-recovery-for-samsung-galaxy-core-2-sm-g355hg355hn.html
hahanhata123 said:
I have some error when flashing TWRP
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
take your mobile battery out and in and retry flashing procedure
click thanks if i helped
Worked or not
Dhruvit Pokharna said:
take your mobile battery out and in and retry flashing procedure
Click to expand...
Click to collapse
I have tried 5 times but it not work
Wait i am making flashable zip for you
Here
Try this and tell me if it works for you or not if worked then please hit thanks button
Please any comment
And may be you must have root to install from stock recovery
Dhruvit Pokharna said:
Try this and tell me if it works for you or not if worked then please hit thanks button
Click to expand...
Click to collapse
It work, thank you so much!
My pleasure
Hello everyone,
First of all I would just like to thank everyone and anyone in advance for any help at all they can give me. I would also like to says thanks for this awesome community with all this great information you all share! I am certain there are probably thousands of others who have asked for help with a very similar situation. Through all my research these SM-G870A phones seem to be a bit more problematic than most and less common as well, so I decided to open up a thread in hopes this will help more than just myself someday.
I attempted to root my Samsung galaxy S5 active AT&T (SM-G870A) last night and I have gotten in over my head on this one. I am a novice root android user obviously. I attempted to follow this guide from muniz_ri:
https://forum.xda-developers.com/at...to-root-g870aucu1aoa1-4-4-4-2-7-2015-t3025119
I think his guide is great, but it was the wrong one for me since I didn't already have root.
I didn't take my time and do enough research before attempting this and I know better than to do stupid things like that I really do. My phone has the OTA firmware 6.0.1 on it, so I don't think I should have tried to gain root access in this way unfortunately for me. I completed the first 4 steps and odin successfully completed flashing the G870A_NE4_Stock_Kernel, but now all my phone will do is boot up into android recovery over and over again. I believe this is referred to as boot looping.
I have tried wipe data/factory reset/reboot and I have tried wipe cache partition followed by rebooting with no luck. No matter what I seem to attempt I just get booted right back into android recovery.
I have done alot of reading all over the web, but mostly here at XDA and at this point I am lost about what I should do to recover my phone back to working condition. I would be satisfied just having my phone back with root or no root at this point. I think it is just boot looping from what I understand. I have searched everywhere for an original copy of the 6.0.1 firmware so I could flash it back with Odin, but no luck so far. It was really stupid of me not to make some kind of copy of my firmware and stuff first before trying this. I do have one thing that might help me, but I am not sure. I have a backup of my phone made using Samsung smart switch software on my SD which I copied over to my computer. I am going to continue researching and attempting to fix my phone anyway I can, if anyone would be willing to help me in any sort of way I would greatly appreciate that so much! If there is anymore information you would like me to provide please just ask!
It looks like some others having similar issues on their Samsung galaxy phones were able to resolve them by flashing the correct cf auto root file. I checked for a file on the cf auto root site that might work for my phone, but they don't have (SM-G870A) available. I did however find SM-G870W for 6.0.1 here
Here is the Odin log from the CF Auto Root attempt:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-kltecanactive-kltevlactive-smg870w.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Its not super clear, but here is what my phone shows after attempting CF Auto Root (SM-G870W) on my (SM-G870A) phone in download odin mode.
{
"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"
}
After further researching apparently this CF auto Root (SM-G870W) file wont work for my (SM-G870A) phone, because my build number is different. Here is all the info for the current OTA firmware installed on my phone.
Jan. 12, 2017 •What's new: Android device security updates
•Android version: 6.0.1
•Security patch level (SPL): December 1, 2016
•Baseband version: G870AUCS2DPK3
•Kernel version: 3.4.0-9723602
•Build number: MMB29M.G870AUCS2DPK3
•File size: 27.7MB
•Previous versions required: G870AUCU2DPK2
Update:
After many hours of reading and researching the web, I now have a better understanding of root, roms, firmwares etc.. which is great! I was able to find and save alot of info and files for the sm-g870a! What finally saved me from default booting into recovery mode was an excellent post here on XDA by AptLogic that I am thankful for! If you find yourself on the journey for knowledge that I am currently on then I hope my beginners post helps you in some way! You can find Aptlogic's post about how to downgrade Marshmallow 6 back to Lollipop 5 right here. It completely solved my problem! It is exactly what I have spent hours and hours looking for!
Good Luck Guys!
Hi guys , good evening to all of you.
i have galaxy j7 sm-j710fn , the phone keep rebooting after ( samsung galaxy j7 (6) powered by android ) then few seconds and the phone restart again.
i tried to flash stock firmware by using odin , os 6.0.1 , everything is okay , flash done , but the same problem "" phone keep restarting ""
i when i try to access to stock recovery , a blue screen with a droid , and under the droid thing , it says : installing system update then Eraze ... then installing system update then Eraze , forever
i said , why i didn't install custom recovery , so i installed TWRP
when i try to wipe dalvik and cach and system or data a page of errors show's up
{
"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"
}
when go to mount it looks like all things are not mounted !!!!!!!!!!! thats why recovery can't spot the storage
help guys , what should i do ?
Maybe eMMC/Pit File problem
I no Nothing about this
So Wait for an expert
qounik said:
Maybe eMMC/Pit File problem
I no Nothing about this
So Wait for an expert
Click to expand...
Click to collapse
yes , i think its PIT FILE
but i did not find firmware with pit file for my phone
HACKIMTOSH said:
yes , i think its PIT FILE
but i did not find firmware with pit file for my phone
Click to expand...
Click to collapse
Search deep in Google
Maybe your luck will favour You
I once found Pit for my GT9192
qounik said:
Search deep in Google
Maybe your luck will favour You
I once found Pit for my GT9192
Click to expand...
Click to collapse
yeah, i'm trying so hard to find the pit file but the problem is samsung mobiles names are so closed to each other , even google goes crazy
help please anyone ? i'm trying but nothing
ODIN LOG
<ID:0/006> 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/006> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I managed to something similar to my phone a while back. Only solution that i found was restoring the phone using Samsung Smart Switch app on PC. There are a few stepts the app tells you to do, after that it flashes the stock firmware, modem, recovery...evrything.
sesamo said:
I managed to something similar to my phone a while back. Only solution that i found was restoring the phone using Samsung Smart Switch app on PC. There are a few stepts the app tells you to do, after that it flashes the stock firmware, modem, recovery...evrything.
Click to expand...
Click to collapse
i tried it before ......... smart switch restore the phone and no error during Procedure
when the phone reboot , boom........same problem....keeep restarting
i need PIT file for this phone , anyone ?
Looks like you've flashed the wrong recovery to me.
ashyx said:
Looks like you've flashed the wrong recovery to me.
Click to expand...
Click to collapse
Don't we have only one recovery??? That official one TWRP?
qounik said:
Don't we have only one recovery??? That official one TWRP?
Click to expand...
Click to collapse
Is your device a J7 or ON8?
Please post the full specs of your device from the device itself.
Bravoo do not work......Why break the device?
I've got a Samsung Galaxy S6 (SM-G920F) which stucks on the Samsung logo screen after booting (Samsung Galaxy S6 powered by Android). I got it from a friend, he doesn't know what happened. Knox wasn't affected so it was just stock.
First I thought it was a dead battery because the phone didn't do anything. Only when the charger was connected, it would show a charging empty battery but no percentage. But after a hour in the charger I could boot into the Samsung logo where it get stuck (still no battery percentage however). I can also boot into download/odin mode. But I can't boot into recovery.
I already tried to flash the latest firmware for the S6 (PHN Netherlands G920FXXU6ERF5 https://www.sammobile.com/firmwares/galaxy-s6/SM-G920F/PHN/download/G920FXXU6ERF5/226355/) but that didn't help. It still doesn't boot and I still can't boot into recovery. Should I use some other options in Odin?
I also tried to flash TWRP, but even then I can't boot into recovery.
Flashing both stock firmware and TWRP give no error in Odin.
I found this guide:
https://forum.xda-developers.com/galaxy-s6/help/guide-downgrade-sm-g920f-nougat-to-t3639253
I want to try this, but I already get stuck in step 5.
5. Open SkipSoft Android Tool Kit and wait until you see the main menu. Then go to the installation folder of this tool and you should see an "INPUT" folder. Copy ONLY the boot.img, cache.img, recovery.img and system.img into that folder.
Click to expand...
Click to collapse
When I go to the installation folder (I'm not on the computer right now, something in C:\Program Files\nameofprogram ) there is no INPUT folder.
And in step 6, on my screen there is no option for 99. I got something like this: (picture is from google, not exactly what I got. But almost the same)
{
"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"
}
So I don't know what these steps do. Can't I just make the flashable file with winrar or 7zip or something?
Are there other options I can try? What can cause this behavior? Is it a faulty bootloader? If so, can't I just reflash just the bootloader?
Maybe I should try to flash 5.0.2 or 5.1.1, but I can't find these files on sammobile and updato.com. I found the original url to sammobile but those aren't working anymore:
5.0.2: G920FXXU1AOE3 G920FPHN1AODQ PHN
http://www.sammobile.com/firmwares/download/47427/G920FXXU1AOE3_G920FPHN1AODQ_PHN/
5.1.1: G920FXXU2BOGB G920FPHN2BOG8 PHN
http://www.sammobile.com/firmwares/download/52406/G920FXXU2BOGB_G920FPHN2BOG8_PHN/
Or can someone help me to get the 5.0.2 and/or 5.1.1 files for the G920F?
Typing 99 in the menu worked for me. Even though I also didn't see the corresponding option. It seems to be an update command, downloading the latest packages of adb, adb-fastboot and magisk.
Can you verify that you tried starting recovery mode IMMEDIATELY after flashing the TWRP? The original system seemed to override any changes, if you give it the chance to reboot normally.
Yes I tried TWRP with auto-reboot in Odin and immediately press VOL_UP+POWER+HOME after auto reboot. And TWRP with auto-reboot unchecked. So flash TWRP, force reboot with VOL_DOWN+POWER+HOME switch to VOL_UP+POWER+HOME before the Samsung logo appears. Bot both methods won't let me boot into recovery.
When I try to flash this rom:
G920FXXU3DPBG_G920FPHN3DPB2_PHN
I get this error in Odin (tried v3.10.6 and v3.12.4_4)
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU3DPBG_G920FPHN3DPB2_G920FXXU3DPB6_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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Why?
Phone says:
Code:
[CM] SW REV. CHECK FAIL. DEVICE: 6, BINARY: 3
Hi,
Were you able to figure out what the issue was? I'm in the exact same situation and have tried similar things with no success. I've kind of given up on it being a software issue at this point..
Nope, I'm going to sell it for parts.
Markos said:
Nope, I'm going to sell it for parts.
Click to expand...
Click to collapse
This happened to me after trying to get unstuck from a bootloop. I think I solved it by flashing it again a couple more times. And I remember it taking quit a while to actually boot up when it finally did.
I already flashed it a lot of times. Both original firmware as TWRP. Nothing helped.
I wanted to try early stock rom but can't find downloads
Markos said:
Or can someone help me to get the 5.0.2 and/or 5.1.1 files for the G920F?
Click to expand...
Click to collapse
I just want to suggest the SamMobile. Hahaha.
heidisteen said:
I just want to suggest the SamMobile. Hahaha.
Click to expand...
Click to collapse
As I said, they don't have it anymore
Markos said:
As I said, they don't have it anymore
https://youtu.be/zXSHe3oorIM
Click to expand...
Click to collapse
I found a video about fixing Samsung Galaxy Android system issues, sound helpful with you.