Related
Following this tut;
http://forum.xda-developers.com/showthread.php?t=1125414
Step 5: Connect your device to your PC and start Odin3 v1.83. If you installed Samsung Kies correctly, you should see the box in the top left corner of Odin underneath where it says ID:COM should be Yellow and displaying the name of a Com Port your device is connected to.
I cant get there, it doesnt go yellow. I have kies installed correctly, not sure whats wrong
New to rooting btw
However i do get this error come up;
screensnapr.*com/e/ZXruBp.png
xSirAKx said:
Following this tut;
http://forum.xda-developers.com/showthread.php?t=1125414
Step 5: Connect your device to your PC and start Odin3 v1.83. If you installed Samsung Kies correctly, you should see the box in the top left corner of Odin underneath where it says ID:COM should be Yellow and displaying the name of a Com Port your device is connected to.
I cant get there, it doesnt go yellow. I have kies installed correctly, not sure whats wrong
Click to expand...
Click to collapse
Try this guide - it is tried and tested. http://forum.xda-developers.com/showthread.php?t=1075278
Cheers!
Now its working but it shows FAIL
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
<ID:0/011> Added!!
<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> PK
<ID:0/011> NAND Write Start!!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Did you make sure you are in Download mode, and the drivers were installed correctly? Also, did you make sure you added the kernel file in the correct section? (without ticking any unnecessary things)
Yes.
Now it wont switch on.
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Did you tick the PIT box?
Edit - sorry, just reread, you haven't. I hope..
No i didn't. I restored the original firmware but it still wont turn on normally.
Did you have kies running in the background? Make sure you end all kies applications - end process
Nope had shut kies.
Could be a cable failure. Try a different USB cable.
I only have 1 cable. I restored the kernels and it went green that it worked. But my phone doesn't work.
xSirAKx said:
I only have 1 cable. I restored the kernels and it went green that it worked. But my phone doesn't work.
Click to expand...
Click to collapse
You can get a new USB cable for a couple of bucks. I've got like 6 due to all the devices I've had over the years, and 2 of them are bad. They don't last forever.
Managed to restore device using tutorial i found on google androidcute.*com/install-android-2-3-6-gingerbread-for-samsung-galaxy-s2.html
after restoring i decided to give rooting another go.
all worked out fine, i installed rom manager after and it keeps rebooting itself after every few mins
i have cpu tuner installed too i also restored the original kernel after rooting.
xSirAKx said:
after restoring i decided to give rooting another go.
all worked out fine, i installed rom manager after and it keeps rebooting itself after every few mins
i have cpu tuner installed too i also restored the original kernel after rooting.
Click to expand...
Click to collapse
ROM Manager is the devil. I don't think it plays well with CWM. How are you rooting? If you root using a CF-Root kernel, it will auto-install the CWM app, which I believe does everything ROM Manager does.
I used S2 Root, i uninstalled rom manager though.
xSirAKx said:
I used S2 Root, i uninstalled rom manager though.
Click to expand...
Click to collapse
Is it still rebooting?
Sent from my GT-I9100 using XDA App
It was fine the past 3 hours but its just rebooted again 2 twice in the last 10mins.
xSirAKx said:
It was fine the past 3 hours but its just rebooted again 2 twice in the last 10mins.
Click to expand...
Click to collapse
Last time I had this issue, it was some app I installed, but I couldn't figure out which one. I flashed back to stock and was more selective in which apps I chose to reinstall. I've also made sure that all the apps are on phone memory instead of SD card as there was some speculation flying around that this could also contribute to this issue. Haven't had a random reboot in months now.
Hi,
Hoping someone can help me, i've searched for a couple of days for answers and tried out suggestions and followed procedures but not getting anywhere so could do with some direct help I think.
Handset details:
Galaxy S3 not locked to any UK network nor does it have any network specific software on it.
Not had any modifications done other than normal OTA software updates and is currently running ICS.
Problem:
Woke up one morning to find the handset frozen on the black & white splashscreen after it being fine the night before and still having plenty of charge. Now won't respond to powering off, just goes blank then returns to splashscreen, only way is to remove battery. Will not respond to normal reset method (vol up + home + power) but will enter download mode (vol down + home + power) and connect to PC.
Attempted solutions:
Have downloaded Odin3 v3.07 along with various firmware .tar files and followed the procedure to reflash the handset but it fails everytime at the 'NAND write' stage.
*Kies is not running at the same time as Odin3
*All drivers are installed and working correctly
*All different USB ports have been tried
*Only have the one USB cable to use
*All settings on Odin3 are correct with regards to checkboxes, etc.
The following is what appears in the message box after each failed attempt: (the <OSM> stages all complete fine)
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialization..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> Boot.img
<ID:0/006> NAND write start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be much appreciated as I am completely at a loss as to why this has happened considering i've done nothing to the handset with regards to rooting, etc. and I don't really want to send my handset away for repair if I can help it.
Thanks in advance.
Nand fail = service centre repair .
jje
Thanks for the reply, I had a bad feeling that it would need sent away
Any ideas as to why the handset should just stop working all of a sudden? I could understand it if I had tried to install some dodgy software or otherwise mess about with it but there's been no tinkering, no liquid ingress, nothing.
Service center for u buddy.. sorry
Sent from my GT-I9300 using xda premium
Hello everybody!
First of all, I'm not sure about my english skills...please have mercy on me :fingers-crossed:
Here I go:
I got my S3 in August/Sept with a T-Mobile Branding. My first action was getting it rootet and flashed with an official Samsung Rom just to get rid of the branding.
Two days ago I woke up to my charging S3 only showing the "Samsung..." Bootlogo. Removed the battery, nothing changed. Tried the Volume up-HomeButton-PowerButton Combo and it only resulted in a blinking logo (the logo disappears for a few seconds). The only thing I have access to is the Download-Mode.
What I tried since then:
Flashing a new one-part-rom with Odin, this was the result:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md 5 is valid.
<OSM> MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
<OSM> CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noshi p.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003>*Odin*v.3 engine (ID:3)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!*
<ID:0/003>*
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Same with a three-part-rom.
Then I tried to downgrade the bootloader with ADB. But I don't get the drivers (Universal-Naked-Drivers) running. The S3 shows up as "unknown device" at the device manager but it doesn't want to be updated with the right drivers. PdaNet also refused to install USB-Drivers.
It's like they don't recognize the S3.. Perhaps I don't have USB-Debugging enabled? I'm not sure about this, because this brick just happened from one day to another.
I installed and uninstalled the "normal Samsung USB-Driver for mobile phones" often while trying to get the other drivers running. When installed, the S3 showed up in the device manager as one of the USB-Controllers.
Installed Kies for a factory reset but it didn't recognize the S3..
This shows up in Download-Mode:
ODIN*MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
I guess it's no sudden death because it shows the product name? Also I have no idea why it has three flash counts, I just flashed it once seven month ago.
Since I never updated to Jelly Bean the S3 was running on ICS 4.0.4
Edit:
Next steps I tried:
Flashing with an older version of Odin (v.1.85) But also failed at <ID:0/003> Complete(Write) operation failed
Flashing CF-Root v.6.4 to get the recovery mode back. Failed at <ID:0/003> Complete(Write) operation failed
Flashing Resurrection Odin CheckRom EvoHD v.4. Failed at <ID:0/003> Complete(Write) operation failed
Repartition with 20120329.pit and mx.pit. Failed at <ID:0/003> Complete(Write) operation failed
I'd still appreciate any kind of help or feedback!
It sounds like partial nand failure or simple partition corruption. Search here in q&a for solutions to repartition, but if that fails then your nand is probably toast.
try flashing a pit file
not sure if it will help but..
connect it to computer..when it fails to install drivers..Turn off and Pull battery out for few secs restart..
sometimes this helps to reinstall drivers..not sure in your case of a bootloop though?
Thanks for your answers!
I tried to repartition with a PIT-File but it didn't work.
At first I tried the GT-I9300_mx_20120329.pit with this 3-part-rom:
CODE_I9300XXALE8_554452_REV00_user_low_ship.tar.md5 is valid.
MODEM_I9300XXLE8_REV02_REV04_CL1145430.tar.md5 is valid.
CSC_OJV_I9300OJVALE7_CL547448_REV00_user_low_noship.tar.md5 is valid.
But the same error appeared.. also the error appeared so fast I don't think there happened a repartition at all?
<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> 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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Second try was 3-part-rom recommended with the mx.pit-File:
CODE_I9300XXALEF_611327_REV00_user_low_ship.tar.md5 is valid.
MODEM_I9300XXLEF_REV02_REV04_CL1147871.tar.md5 is valid.
CSC_OXF_I9300OXFALEA_613742_REV00_user_low_ship.tar.md5 is valid.
With the same result...
It's always the same error, again and again...
Any further ideas?
you are done
Only two answers one wrong PIT or partition damaged .
Two Nand damaged see how much will a new motherboard cost .
jje
Thanks again!
With the GT-I9300_mx_20120220.pit-File I got my S3 responding for the first time since it died. It showed the blue loading-bar, but it didn't move at all and Odin stopped at <ID:0/004> NAND Write Start!!
Tried this rescue-version http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 with mx.pit but of course it didn't work..
you are done
Click to expand...
Click to collapse
seems like you're right, unfortunately..
But if you have ANY idea what I could try, please post it.
Are you sure it's a NAND damage or could it be a bootloader problem? I found this thread: http://forum.xda-developers.com/showthread.php?t=1916796 but I don't understand what they are talking about yet.
Update:
I couldn't find a solution and send it to a Samsung repair service and it was repaired under warranty. Don't know why exactly..they didn't need to because of my flash-counter. There was a letter in the package that said the mainboard was replaced and that's all!
Anyways, thanks for the help!
Can be closed!
Possible Solution
xylakant said:
Update:
I couldn't find a solution and send it to a Samsung repair service and it was repaired under warranty. Don't know why exactly..they didn't need to because of my flash-counter. There was a letter in the package that said the mainboard was replaced and that's all!
Anyways, thanks for the help!
Can be closed!
Click to expand...
Click to collapse
I had a similar problem, my phone just froze in the middle of a phone call, had to pull out battery, and when i tried to turn it on, it wouldn't pass the second "SAMSUNG" logo, just stayed there forever, with the blue light (Official JB 4.1.2 - not rooted)... Anyway, after 3 days of trying, downloaded bunch of firmwares, but all of them gave me the infamous "Complete(Write) operation failed". This is how I MANAGED to revive my i9300 16Gb Int:
1.Open ODIN, load ONLY the pit file corresponding to your phone (In my case i9300 16Gb Int'l - GT-I9300_mx_20120220.pit), check "Repartition" and "F.Reset Time" and hit "Start".
- If this step goes OK (All threads completed. (succeed 1 / failed 0))
2. Click on the "Reset" button in Odin (or close and re-open it), in PDA select "recovery-cwm-touch-6.0.1.2-i9300.tar", make sure only "F.Reset Time" and "Auto Reboot" are checked, and flash it. If everything goes OK, you should now have CWM instead of Stock recovery.
3. Take any microSD card, any size, and put THIS file on the root of the microSD using a card reader or whatever you prefer - but be careful, copy the zip as it is - do not unzip it.
4. Insert the memory card in the phone, enter recovery*, and select "Install zip from External Storage" and choose the file you put on the root of the card (by the way, it's a 4.0.4 downgrade bootloader), it should flash in a second, the phone will restart, and that's it!
5. Download and flash 4.0.4 Stock FW using Odin (i used "I9300XXBLH1_OXEBLF1.zip"), everything should go OK, and the phone will be bootable again.
*(my phone didn't wanted to enter recovery the old fashioned way using 3-button combo, but i managed to enter recovery from charging mode, by connecting the charger on a switched off phone, and as soon it starts charging press Vol Up + Home + Power, and when the FIRST Logo (Galaxy S III GT-I9300) appears, let go of the power button, keep pressing the Vol Up + Home, and it enters recovery).
ATRAC3 said:
1.Open ODIN, load ONLY the pit file corresponding to your phone (In my case i9300 16Gb Int'l - GT-I9300_mx_20120220.pit), check "Repartition" and "F.Reset Time" and hit "Start".
- If this step goes OK (All threads completed. (succeed 1 / failed 0))
Click to expand...
Click to collapse
Odin Stuck at "Set Partition" ^^
"<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
Help ?
Did you give it the pit file? Pit is really a last resort AFTER you've ruled out sending for repair
Sent from my GT-I9300 using Tapatalk 4
I have the pit file and Checked the Box ^^
MrFraggii said:
I have the pit file and Checked the Box ^^
Click to expand...
Click to collapse
Correct PIT file ??? for your phone ??
Flashing PIT 99% kill the phone .
You require a service centre .
Warranty will depend upon their report .
jje
Have the right Pit file ^^ But odin Stuck at Set mapping
MrFraggii said:
Have the right Pit file ^^ But odin Stuck at Set mapping
Click to expand...
Click to collapse
Where can you download these 16, 32 or 64 .pit files ? I couldn't find them anywhere ...
If you start playing with PIT files you will end up with a dead phone and at best have to buy a new motherboard .
They might be found on sammobile
jje
JJEgan said:
If you start playing with PIT files you will end up with a dead phone and at best have to buy a new motherboard .
They might be found on sammobile
jje
Click to expand...
Click to collapse
Thanks for the lead, I will look for them on Sammobile.
But Please, this is the only answer I could reald along my searches "do not mess with .pit file". That does not answers the "where" and "which file" questions. I think people know playing with .pit files is touchy and they have a reason to ask for it.Stop being their mother and just answer the question accurately !
tris16 said:
Thanks for the lead, I will look for them on Sammobile.
But Please, this is the only answer I could reald along my searches "do not mess with .pit file". That does not answers the "where" and "which file" questions. I think people know playing with .pit files is touchy and they have a reason to ask for it.Stop being their mother and just answer the question accurately !
Click to expand...
Click to collapse
Your sense of entitlement is awe inspiring, if you searched and read you would find many people who flashed pit files to fix just a soft brick and then had to pay for a new motherboard.
So no, we won't help people wreck their phones.
Pit Files
tris16 said:
Where can you download these 16, 32 or 64 .pit files ? I couldn't find them anywhere ...
Click to expand...
Click to collapse
This is where i got mine.
http://forum.xda-developers.com/showthread.php?p=30547929
Hello, guys. First of all sorry for my english, but I need help.
I am here because I dont know what to do, I have tried everything without success. Let me explain: I have a S3 GT-I9300, I have had it since 2013 and I have gone through everything with it: brick, several rom, resets, etc. On saturday I woke up and my phone was in a boot loop, but I said ''bah, I can fix it in 20 mins'', but as you can see I couldnt do it. First of all, NAND write start error appeared, I havent seen that error before, then partition errors appeared too.
I can enter to dowload mode and it says GT-I9300 in product name, I can enter to recovery but I cant do anything there
I have tried to flash the same stock rom that I always have, it is an emergency firmware that I have used like 5 times, so.... It is weird that it cannot fix this up. I also have tried with Sammobile's firmware, with and without pit, in 3 usb ports and with 2 usb cables and always the same result: FAIL.
I hope you can help me, buying another phone in my country is difficult.
It can be a hardware issue on emmc of the phone if failed after so many different tries
dusterphil said:
It can be a hardware issue on emmc of the phone if failed after so many different tries
Click to expand...
Click to collapse
And what can I do about it?
What is the Odin error? Post the Odin log.
audit13 said:
What is the Odin error? Post the Odin log.
Click to expand...
Click to collapse
This is one of those:
<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> Get PIT for mapping...
Then it does not do anything (in this case I used 4 files + pit, and those files and pit are the ones that I have always used)
The other one is this:
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
This was the first error that appeared. (this is with sammobile's firmware)
The sboot.bin file is the bootloader. It's probably failing to flash for one or more of the following reasons:
the bootloader in the phone is newer than the bootloader in the ROM being flashed;
the ROM is not for the phone being flashed;
need to try a different USB cable;
need to try a different USB port; and/or
the memory chip in the phone is damaged.
Borked nand. If the rom and cable are known to be good and 2 pc's fail then dead nand. It's unfortunate but it happens.
Beamed in by telepathy
I think the phone is dead, it have faught a lot in this years. Thank you anyways
jeanavila_ said:
I think the phone is dead, it have faught a lot in this years. Thank you anyways
Click to expand...
Click to collapse
It's time for you to get a new model
Hello , I've searched for any similar threat the whole night but I couldn't find any with the same problem as mine!
I was trying to root my Samsung Galaxy Grand Prime Pro SM-J250F/DS.
After enabling OEM Unlock and USB Debugging,
I used Odin to flash TWRP , Odin executed the file without any problem and stated PASS.
BUT when I try to boot on recovery mode, I still had the basic samsung recovery mode.
I tried to flash it severals times, each time showed pass, but the same recovery mode was still there.
I couldn't find anyone else facing this problem on any other forum neither.
I decided to try other root's threat that I found on other forum where I was suggested to download an image.tar.md5 then flash it with Odin for rooting process of my phone.
After I did this , the operation was PASS but upon booting up my device, my phone was on boot loop :'(
I tried being cautious all the way to root this reading every information carefully to avoid this kind of problems, but still I fail
I dont know what to do, I spent the whole night looking for answers on the web but I couldnt find anything similar.
I cant even enter recovery mode it booting all over again. I only have access to download mode.
Thus, I tried to download a fresh firmware from samsmobile, I dont know how to do to know which Country/PDA/CSC to choose from
I tried to download a random one and flash it with odin but the operation failed and here's the logs;
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Can anyone please help me solving this problem , this is my only phone and I'm going to end in a lot of problem without it
Help please . :crying: :crying: :crying:
Hi , in order to help you you need to give me little more information ....
Where did you bought your phone which region ? Is on some provider Sprint , Verizon , etc
Up
Up got exactly the same need help please :crying:
Same phone same problem
Nadir Boodhoo said:
Hello , I've searched for any similar threat the whole night but I couldn't find any with the same problem as mine!
I was trying to root my Samsung Galaxy Grand Prime Pro SM-J250F/DS.
After enabling OEM Unlock and USB Debugging,
I used Odin to flash TWRP , Odin executed the file without any problem and stated PASS.
BUT when I try to boot on recovery mode, I still had the basic samsung recovery mode.
I tried to flash it severals times, each time showed pass, but the same recovery mode was still there.
I couldn't find anyone else facing this problem on any other forum neither.
I decided to try other root's threat that I found on other forum where I was suggested to download an image.tar.md5 then flash it with Odin for rooting process of my phone.
After I did this , the operation was PASS but upon booting up my device, my phone was on boot loop :'(
I tried being cautious all the way to root this reading every information carefully to avoid this kind of problems, but still I fail
I dont know what to do, I spent the whole night looking for answers on the web but I couldnt find anything similar.
I cant even enter recovery mode it booting all over again. I only have access to download mode.
Thus, I tried to download a fresh firmware from samsmobile, I dont know how to do to know which Country/PDA/CSC to choose from
I tried to download a random one and flash it with odin but the operation failed and here's the logs;
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Can anyone please help me solving this problem , this is my only phone and I'm going to end in a lot of problem without it
Help please . :crying: :crying: :crying:
Click to expand...
Click to collapse
Alpha45amg said:
Up got exactly the same need help please :crying:
Same phone same problem
Click to expand...
Click to collapse
Hey......when you got vibration after flashing twrp in odin, then immediately remove the battery and after some time put it back reboot to recovery bro.....
Hope this helps
If anyone needs here is the PIT file for the latest factory firmware of J2.
firmware version reference:
HTML:
AP_J250FXXS2ARE1_CL13338766
BL_J250FXXS2ARE1_CL13338766
CP_J250FXXS2ARF1_REV00
CSC_OJV_J250FOJV2ARD4
HOME_CSC_OJV
dude if u can still enter download mode, then is not bad..snap ur device in download mode and send it to me, let me provide u with a solution
Nadir Boodhoo said:
Hello , I've searched for any similar threat the whole night but I couldn't find any with the same problem as mine!
I was trying to root my Samsung Galaxy Grand Prime Pro SM-J250F/DS.
After enabling OEM Unlock and USB Debugging,
I used Odin to flash TWRP , Odin executed the file without any problem and stated PASS.
BUT when I try to boot on recovery mode, I still had the basic samsung recovery mode.
I tried to flash it severals times, each time showed pass, but the same recovery mode was still there.
I couldn't find anyone else facing this problem on any other forum neither.
I decided to try other root's threat that I found on other forum where I was suggested to download an image.tar.md5 then flash it with Odin for rooting process of my phone.
After I did this , the operation was PASS but upon booting up my device, my phone was on boot loop :'(
I tried being cautious all the way to root this reading every information carefully to avoid this kind of problems, but still I fail
I dont know what to do, I spent the whole night looking for answers on the web but I couldnt find anything similar.
I cant even enter recovery mode it booting all over again. I only have access to download mode.
Thus, I tried to download a fresh firmware from samsmobile, I dont know how to do to know which Country/PDA/CSC to choose from
I tried to download a random one and flash it with odin but the operation failed and here's the logs;
Can anyone please help me solving this problem , this is my only phone and I'm going to end in a lot of problem without it
Help please . :crying: :crying: :crying:
Click to expand...
Click to collapse
Did you try restoring the factory firmware image using samsung smart switch or odin?
check this guide:
http://mobilesolutionru.blogspot.com/2018/05/samsung-galaxy-grand-prime-pro-sm-j250f.html
if you have already official firmware just flash boot.img and recovery.img only to cure hang problem
Try this 4 Repair file
There are three types of PDAs:
XX
DX
XW
Here is a video can help to fix this problem. Fix Samsung system issues like Stuck on Boot Loop, Stuck at Samsung logo and more
https://www.youtube.com/watch?v=zXSHe3oorIM
Nadir Boodhoo said:
Hello , I've searched for any similar threat the whole night but I couldn't find any with the same problem as mine!
I was trying to root my Samsung Galaxy Grand Prime Pro SM-J250F/DS.
After enabling OEM Unlock and USB Debugging,
I used Odin to flash TWRP , Odin executed the file without any problem and stated PASS.
BUT when I try to boot on recovery mode, I still had the basic samsung recovery mode.
I tried to flash it severals times, each time showed pass, but the same recovery mode was still there.
I couldn't find anyone else facing this problem on any other forum neither.
I decided to try other root's threat that I found on other forum where I was suggested to download an image.tar.md5 then flash it with Odin for rooting process of my phone.
After I did this , the operation was PASS but upon booting up my device, my phone was on boot loop :'(
I tried being cautious all the way to root this reading every information carefully to avoid this kind of problems, but still I fail
I dont know what to do, I spent the whole night looking for answers on the web but I couldnt find anything similar.
I cant even enter recovery mode it booting all over again. I only have access to download mode.
Thus, I tried to download a fresh firmware from samsmobile, I dont know how to do to know which Country/PDA/CSC to choose from
I tried to download a random one and flash it with odin but the operation failed and here's the logs;
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Can anyone please help me solving this problem , this is my only phone and I'm going to end in a lot of problem without it
Help please . :crying: :crying: :crying:
Click to expand...
Click to collapse
Same happened to me once,what i just did was
1.installed twrp for samsung j250f
2.installed a custom rom of j250f using twrp