So awhile back I bricked my Samsung Galaxy Tablet 4 by installing a 1 click root app and later restarting my tablet. I haven't been able to fix it since. I was using an app because of the locked bootloader. Is there a way to fix this? The tablet uses the T337AUCU2BOH4 firmware which I think I was able to find through google, although it said it only worked for nonrooted apps which I didn't understand.
You could search about Odin. With it you can install samsung stock firmware on your device, if you can still boot to download mode. Also it's best to avoid 1 click root apps(if possible) they seem to cause problems very often.
keikari said:
You could search about Odin. With it you can install samsung stock firmware on your device, if you can still boot to download mode. Also it's best to avoid 1 click root apps(if possible) they seem to cause problems very often.
Click to expand...
Click to collapse
I found the firmware files here
I set my device to download mode and chose the file for the BL, AP, CP, and CSC section of Odin3 and click start. The program than stalls at SetupConnection and fails. I run Odin3 a second time and it's now stalling at Initialization. Later attempts I get a log with "Can't open the serial(COM) port". I Googled something that suggested I download the USB driver for the tablet so I downloaded this, but it didn't help.
Here's my log:
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Here's my log after running Odin3 a second time
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
Later attempts it now does this:
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Can any help me figure out what I'm doing wrong here? I don't really know much about android so this stuff is all new to me.
WeirdoSarah said:
I found the firmware files here
I set my device to download mode and chose the file for the BL, AP, CP, and CSC section of Odin3 and click start. The program than stalls at SetupConnection and fails. I run Odin3 a second time and it's now stalling at Initialization.
Can any help me figure out what I'm doing wrong here? I don't really know much about android so this stuff is all new to me.
Click to expand...
Click to collapse
This guide says that you should only choose file for the AP, but I have no idea is that fix for your problem.
https://forum.xda-developers.com/tab-4/general/guide-how-to-restore-stock-firmware-t2979006
keikari said:
This guide says that you should only chose the file for the AP, but I have no idea is that fix for your problem.
https://forum.xda-developers.com/tab-4/general/guide-how-to-restore-stock-firmware-t2979006
Click to expand...
Click to collapse
Thanks for finding that! I was actually originally following that guide although I had to find the firmware files elsewhere. I tried just selecting the AP, but it didn't work. I'm still getting the same set of errors.
Edit: I restarted Odin3 and unplugged and the cord and plugged it back in and I think it's working now. It started downloading and the tablet rebooted when it was done. At first, it looked promising, but it booted to some AT&T logo in the middle and white background which scared me a little. After a minute or so it booted up to the welcome menu to configure the tablet. Thanks so much for your help!
WeirdoSarah said:
Thanks for finding that! I was actually originally following that guide although I had to find the firmware files elsewhere. I tried just selecting the AP, but it didn't work. I'm still getting the same set of errors.
Edit: I restarted Odin3 and unplugged and the cord and plugged it back in and I think it's working now. It started downloading and the tablet rebooted when it was done. At first, it looked promising, but it booted to some AT&T logo in the middle and white background which scared me a little. After a minute or so it booted up to the welcome menu to configure the tablet. Thanks so much for your help!
Click to expand...
Click to collapse
No problem. About that AT&T logo, you can get rid of it by finding "non-branded firmware" (or something like that I don't know the right term for it) or you can check if SM-T335 has same specs as your tablet(all its firmwares seem to be "non-branded"). Like with sm-t230 you can use sm-t231 roms. But be careful if you do that.
This site might have more firmwares http://forum.youmobile.org/downloads/?cat=151 thought I'm not sure have I ever tried to download from there. Atleast you can find build numbers there.
Or maybe rooting your device and changing boot animation.
Also there is a button for thanking : D (next to reply button) ---------------------------------------------------------------V
Related
Screen shows a picture of a cell phone and a computer with a yellow triangle.
Any way to get Odin to pick up on this to load the stock image back?
Yes, odin will work. Iv bricked my atleast 4 times.
Sent from my SPH-D700 using XDA App
Can you give me an idea how? I can't get into any other screen except this all black one with a white phone, yellow triangle, and white computer...I'm lost on this one - I never had an issue so far and this is my 3rd rooted android phone. I am far from noob.
Yep, got that screen a few times when first learning the in's and out of this phone.
Hold the #1 key on the slide out keyboard and press power to get into download mode. Use Odin to flash to stock and try again.
Ok - ODIN is giving me:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> home/n/Desktop/zImage
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What gives here? This is my first samsung, so ODIN is new to me.
Follow this.
http://forum.xda-developers.com/showthread.php?t=773032
Well, ODIN gets to "File analysis" now and just sits there.
Any other ideas?
Odin is now sitting at <ID:0/010> param.lfs
hasn't moved in 4 or 5 minutes....worrying me.
Well since you're not a noob, then I probably don't need to tell you that you should have odin open and ready, then plug the phone in, and THEN boot into download mode. In that order. you need to boot the phone into d/l mode before it starts charging once its plugged in. good luck.
infamousjax said:
Well since you're not a noob, then I probably don't need to tell you that you should have odin open and ready, then plug the phone in, and THEN boot into download mode. In that order. you need to boot the phone into d/l mode before it starts charging once its plugged in. good luck.
Click to expand...
Click to collapse
Yup, done all that. Trying another computer now - not sure why it gets stuck at that stoopid params file....
Got it working now. Thanks for the help guys.
Kcarpenter said:
Got it working now. Thanks for the help guys.
Click to expand...
Click to collapse
OK....
HOW did you get it working? Inquiring minds want to know.
I am sorry if this has been asked and answered, I've been searching the forum board for 4.5 hours trying to find the answer or some sort of point in the right direction. If you know the thread to answer my question, please don't flame me, just point it out...
With that said...
I attempted to upgrade my epic 4G from EB13 to EC05 last night. I did this with Odin3, everything said it passed no problem. Yet, it did not work. It would get to the Samsung screen then vibrate, pause, vibrate, pause, then nothing, just stayed there.
I followed the directions to flash the original EB13 that was on the phone to begin with. I followed the directions exactly, Odin failed, big surprise right? Now, Odin simply verified the MD5 said it was good and stopped. Now my phone just gets the 'phone-!-computer' icon, I can still boot into the downloading screen, but am unable to get Odin to do anything, am I missing something, or is there anything I can do to remedy this?
OK, I just tried the Samsung updater for eb13 and it failed at param.lfs
I am befuddled...
Try downloading the tar file for odin again and see ifthat works u might have a bad tar file
Sent from my SPH-D700 using XDA Premium App
Estewa_619 said:
Try downloading the tar file for odin again and see ifthat works u might have a bad tar file
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
It's worth a try but the Samsung updater has it's own tar already. I think the answer he's looking for is in the Wiki.
I've searched through the wiki. Am I missing something? I find the root/recovery programs, they all say how to root, but I am not finding how to recover. for example, "One Click Root and Recovery", even though I cannot boot my phone, will it still recover? I tried it in the download screen, but it does not connect. How do I use these to recover?
I tried redownloading the tar again, SPH-D700-EB13-8Gb-REL.tar.md5, but I get the same result, Odin checks the file says it's OK then stops doing anything.
Am I using the incorrect tar? is there a tar that's not an MD5?
Are you using your stock samsung cable?
Sent from my SPH-D700 using XDA App
From the Wiki-
"If you get a FAILED error after it writes "param.lfs", try this method:
1. Reboot the phone and reset Odin
2. Load the pit file and place the tar in the Phone section
3. Start the recovery
4. The process will hang while writing "factoryfs.rfs"
5. Reboot the phone and reset Odin
6. Load the pit file, place the tar in the PDA section, and start the recovery again
7. It should now complete in about 3 mins.
8. Congratulations! Thank noobnl
If that doesn't work, take out the battery and reboot into download mode with only the usb cord plugged in."
TimidBull said:
I tried redownloading the tar again, SPH-D700-EB13-8Gb-REL.tar.md5, but I get the same result, Odin checks the file says it's OK then stops doing anything.
Am I using the incorrect tar? is there a tar that's not an MD5?
Click to expand...
Click to collapse
Are u in download mode? (#1 on keyboard + power button) and are u putting the tar file under PDA?
Sent from my SPH-D700 using XDA Premium App
Remove the .md5 extension...it messes up Odin.
Do you BONSAI?
kennyglass123 said:
Remove the .md5 extension...it messes up Odin.
Do you BONSAI?
Click to expand...
Click to collapse
This right here, The tar will be tar.md5, simply remove the .md5 from the end and try it.
Odin gives me problems on certain PCs too, if you have another computer, give that a go.
mattallica76 From the Wiki-
"If you get a FAILED error after it writes "param.lfs", try this method:
1. Reboot the phone and reset Odin
2. Load the pit file and place the tar in the Phone section
3. Start the recovery...
Click to expand...
Click to collapse
I tried this already, same result after 25 attempts.
Are u in download mode? (#1 on keyboard + power button) and are u putting the tar file under PDA?
Click to expand...
Click to collapse
Yes I am in download mode, yellow work sign with digging android, "Downloading... Do not turn off Target.
Also yes, to placing the tar under PDA and using the stock cable, plugged directly into a directly soldered motherboard USB port
I am waiting for the tar to redownload, as soon as it does, I'll remove the .md5 extension.
I was trying to bonsai, that's how I got all screwed up.
Well....that didn't work.
Trying it now with the victory pit, and th eb13 tar. without the .md5 extension.
I got a small blue bar starting to show,
<ID:0/008> Added!!
<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!!
Been this way for about 5 minutes so far. **CROSSES FINGERS**
An obvious one seems missed. Try it on a different USB port.
Sent from my SPH-D700 using Tapatalk
I tried a different usb port, as well as a different computer, no change. After last attempt as decribed, Odin reported the following
<ID:0/008> Added!!
<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>
<ID:0/008> Re-Partition operation failed.
<ID:0/008> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I attempted this 10 times with the same result.
Hmmm...progress
<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..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> cache.rfs
<ID:0/008> datafs.rfs
Click to expand...
Click to collapse
Damn....phone shut off.
Trying again.
How did the phone shut off with a USB cable plugged in it? That makes no sense unless you have a really really bad cable.
Sent from my SPH-D700 using Tapatalk
I was just reading a post in which the user had used odin to put on d18 and he had no issue. Would this be detrimental to my phone since I started with eb13?
Do I need a different pit file instead of the victory_8G_100528.pit?
This is my first Android, been a Palm guy for years, but after my pre problems, I made the change. Theoretically going to older version shouldn't hurt, but I wanted to be sure.
One last thing, I seem to currently be getting to the datafs and nothing seems to happen after that, it's been about 10 minutes in this state, normal?
Thanks all for the help and assistance so far! it is much appreciated.
no idea how it shut off, it was on download screen, then black. took out battery, set back into downloading mode (#1 and power), now back at the datafs point, waiting...
oh, and the cable is brand new, using my wifes cable from her two day old epic.
Phone is working fine, but Odin says "There is no PIT partition" when I try to flash.
I have a GT-I9505 with the MDA version firmware, region EVR.
I've flashed it previously, successfully, to the latest ME2 firmware, but then I installed Chainfire3D which soft-bricked it.
I recovered using Kies firmware recovery, did a factory reset/cache wipe, have rooted the phone again... but now Odin won't flash the phone!
It says "There is no PIT partition", and when I try to re-partition using the PIT file from this thread, it just says "complete(write) operation failed".
I've tried Odin 1.8, 3.04, 3.07... all the same.
The phone is currently working fine and is rooted! I just want to flash to a newer firmware, is all.
Any thoughts?
Flash .pit file with the firmware, not alone make sure re-partition is ticked
Sent from my Galaxy using xda premium
samersh72 said:
Flash .pit file with the firmware, not alone make sure re-partition is ticked
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
I was doing both those things. Strangely, it worked when I used another computer! Thanks anyway.
I am having similar problems. Any other suggestions?
I'm trying to root my S4 for the first time. Just had the S4 factory reset itself before starting this attempt.
Seems like the USB connection keeps resetting. I don't have this problem on any other device and I've tried swapping USB cords as well as USB ports. Tried both USB 2.0 and 3.0 ports. I keep getting the same problems. I've even tried including the PIT file for re-partitioning. Even the Kies connection keeps resetting. Kies trouble shooting the USB connection resulting in reloading some drivers but that didn't have any effect.
ODIN output below:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Removed!!
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/011> Added!!
<ID:0/011> 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> Removed!!
<ID:0/011> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Added!!
Now, searching lead me to a thread for I think the S3 and they were saying these kinds of problems were defective motherboards on the phone. Do I need to take my phone back to Verizon for warranty replacement? It's not even a week old yet.
0reo said:
I am having similar problems. Any other suggestions?
I'm trying to root my S4 for the first time. Just had the S4 factory reset itself before starting this attempt.
Seems like the USB connection keeps resetting. I don't have this problem on any other device and I've tried swapping USB cords as well as USB ports. Tried both USB 2.0 and 3.0 ports. I keep getting the same problems. I've even tried including the PIT file for re-partitioning. Even the Kies connection keeps resetting. Kies trouble shooting the USB connection resulting in reloading some drivers but that didn't have any effect.
ODIN output below:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Removed!!
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/011> Added!!
<ID:0/011> 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> Removed!!
<ID:0/011> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Added!!
Now, searching lead me to a thread for I think the S3 and they were saying these kinds of problems were defective motherboards on the phone. Do I need to take my phone back to Verizon for warranty replacement? It's not even a week old yet.
Click to expand...
Click to collapse
uninstall driver then re-install it. make sure kies is not running. flash pit file with the firmware in odin
samersh72 said:
uninstall driver then re-install it. make sure kies is not running. flash pit file with the firmware in odin
Click to expand...
Click to collapse
For the record, I just convinced the local VZW store to swap me a NIB S4 as a warranty replacement. The new S4 is giving me the exact same problem so in all likelihood the phone is not my problem.
Going to try removing and reinstalling the drivers on the PC again.
Does USB debugging need to be checked / unchecked for ODIN to work?
0reo said:
For the record, I just convinced the local VZW store to swap me a NIB S4 as a warranty replacement. The new S4 is giving me the exact same problem so in all likelihood the phone is not my problem.
Going to try removing and reinstalling the drivers on the PC again.
Does USB debugging need to be checked / unchecked for ODIN to work?
Click to expand...
Click to collapse
NO NEED to check it. a lot of users brick their phones and can not boot to check usb debugging. so they went directly to odin flash and it was good to go :good:
0reo said:
For the record, I just convinced the local VZW store to swap me a NIB S4 as a warranty replacement. The new S4 is giving me the exact same problem so in all likelihood the phone is not my problem.
Going to try removing and reinstalling the drivers on the PC again.
Does USB debugging need to be checked / unchecked for ODIN to work?
Click to expand...
Click to collapse
Hi,
USB debugging needs to be ticked.
OK, I uninstalled and reinstalled the drivers and still get the same problems. Any other ideas?
0reo said:
OK, I uninstalled and reinstalled the drivers and still get the same problems. Any other ideas?
Click to expand...
Click to collapse
Hi,
Did you reboot your PC?
malybru said:
Hi,
Did you reboot your PC?
Click to expand...
Click to collapse
Yes, a number of times at every stage one would think it would make any difference. It didn't make any difference.
I did finally get my phone rooted. While I can't say for certain, it seems like the S4 needed to be booted normally, then connected via USB, then let Win7 auto install several drivers, then I initiated bhp090808's all-in-one root tool which rebooted the phone into ODIN mode. ODIN was then successful.
Contrast that with having the S4 disconnected from USB and manually booting into ODIN mode, then connect USB, then let Win7 install drivers, then initiate ODIN to start. That sequence gave me all the problems.
Thanks for the replies though. I do appreciate your willingness to help.
Solved same problem this way:
1) Connected phone by original cable directly to rear USB port
2) Turn off Kies (no need to uninstall)
3) Stopped 2 kies processes which still run even if kies is off.
4) There must be item "Samsung Android Phone" and cascaded item "Samsung android ADB interface" in device manager.
5) Enable USB Debugging in phone.
6) I had unchecked item "Check installed apps from ADB by USB" - Not sure if it is necessary.
7) When you connect phone there has to be popup with question: "Allow USB debugging from this computer?" followed by computer signature.
Check always, answer yes.
8) Use old Odin 3 V. 1.85
i9505+stock firmware+win7sp1
On pit partition found
samersh72 said:
I flashed cm 10.1 on my SAMSUNG Galaxy Ace Plus.Now I want to come back to my stock rom . I downloaded the stock rom and I am trying to flash it using ODIN.But I get the message that ON PIT PARTITION FOUND.
Click to expand...
Click to collapse
aa
---------- Post added at 08:53 AM ---------- Previous post was at 08:48 AM ----------
samersh72 said:
Flash .pit file with the firmware, not alone make sure re-partition is ticked
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
mpalka said:
Solved same problem this way:
1) Connected phone by original cable directly to rear USB port
2) Turn off Kies (no need to uninstall)
3) Stopped 2 kies processes which still run even if kies is off.
4) There must be item "Samsung Android Phone" and cascaded item "Samsung android ADB interface" in device manager.
5) Enable USB Debugging in phone.
6) I had unchecked item "Check installed apps from ADB by USB" - Not sure if it is necessary.
7) When you connect phone there has to be popup with question: "Allow USB debugging from this computer?" followed by computer signature.
Check always, answer yes.
8) Use old Odin 3 V. 1.85
i9505+stock firmware+win7sp1
Click to expand...
Click to collapse
]I flashed cm 10.1 on my SAMSUNG Galaxy Ace Plus.Now I want to come back to my stock rom . I downloaded the stock rom and I am trying to flash it using ODIN.But I get the message that ON PIT PARTITION FOUND
Sagar6699 said:
I flashed cm 10.1 on my SAMSUNG Galaxy Ace Plus.Now I want to come back to my stock rom . I downloaded the stock rom and I am trying to flash it using ODIN.But I get the message that ON PIT PARTITION FOUND
Click to expand...
Click to collapse
flash pit with the firmware http://forum.xda-developers.com/showthread.php?t=2065046
Re-Partition
samersh72 said:
flash pit with the firmware http://forum.xda-developers.com/showthread.php?t=2065046
Click to expand...
Click to collapse
Thanks!!
But now there is another problem........
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7500DDLD1_S7500ODDLD2_S7500DDLD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009>
<ID:0/009> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLZ HELP!!!!!!!!
probably solve with this
Well I did thgis ... searched another firmware mewer same carrier .. and I rebooted the Pc ..Nothing
But on a forum external some dude sayd ok .. If you use front USB ports theese are coted as external USB and they don't are recognized as internal USB hubs so change to a back side usb and will work I did and now after waiting like 5 minutes the process started my phone is under process restarting now ... And Voloa .. the new firmware,
Thanks for that suggestion. Switching to the back USB ports worked for me.
pisicutumic said:
Well I did thgis ... searched another firmware mewer same carrier .. and I rebooted the Pc ..Nothing
But on a forum external some dude sayd ok .. If you use front USB ports theese are coted as external USB and they don't are recognized as internal USB hubs so change to a back side usb and will work I did and now after waiting like 5 minutes the process started my phone is under process restarting now ... And Voloa .. the new firmware,
Click to expand...
Click to collapse
Moritzio said:
Thanks for that suggestion. Switching to the back USB ports worked for me.
Click to expand...
Click to collapse
and me as well!
thanks alot! :laugh::laugh:
yanivnn said:
and me as well!
thanks alot! :laugh::laugh:
Click to expand...
Click to collapse
And me too!
Moritzio said:
Thanks for that suggestion. Switching to the back USB ports worked for me.
Click to expand...
Click to collapse
For me too, you are genious!
Hey, if anyone could help me with this, I would love it. I NEED this phone working again and every source I've found either doesn't mention my model or doesn't work.
I tried rooting my US Cellular Galaxy S5 SM-G900R4 using CF Auto Root and Odin 3.10.6. I followed all the steps and made sure I started the process in download mode, 75% battery, did it in AP, unchecked re-partition, and also had the correct root file. It was going fine until it got stuck on "CACHE". I kept waiting until it eventually said "FAIL". My S5 was still showing the blue download bar but I figured it was OK anyway. I clicked "RESET" and it did. I unplugged my phone and then tried turning it on but it came up with a yellow triangle in between a desktop logo and my phone logo and it said "Firmware Update Encountered an Error. Select Restore in Kies and Try Again". It does go into download mode but besides that nothing else. It's just stuck there.
After some research I found out you could fix the issue with Samsung Kies, so I installed it and everything looked fine and the drivers installed so I connected the phone and it just stuck on the "connecting" screen forever. I unplugged and tried Samsung Kies 3 but it immediately said "phone unsupported". On Kies I tried going into the update initialization mode and I typed the model number but it said the S/N was incorrect. On the back of this phone it shows the IMEID (H) number and the IMEID (D) and I tried both...
So the last method I had was using ODIN 3.10.6 to flash the stock ROM. My phone was not rooted when this whole thing happened but it does have USB debugging enabled and yes, the Samsung USB drivers are installed. Anyway, I downloaded the stock ROM for my model, and I started it through AP and everything but it immediately failed and said this:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please please PLEASE help me! I am at such a loss and any help would be greatly appreciated
faur.ionutz said:
try to flash another build newer by release date
Trimis de pe al meu SM-G920F folosind Tapatalk
Click to expand...
Click to collapse
What I did try was flashing the official 6.0.1 stock but it failed
try a fresh download. where did you get yours from? sammobile.com is the most trustworthy place, its slow from there, but theyre legit. You probably have a bad download, its the most frequent cause of issues like these
youdoofus said:
try a fresh download. where did you get yours from? sammobile.com is the most trustworthy place, its slow from there, but theyre legit. You probably have a bad download, its the most frequent cause of issues like these
Click to expand...
Click to collapse
If you can give me the link to a legit download for my model that would be great. I tried a couple ROMS but they don't work, and SamsMobile doesn't carry the ROM for my model btw
Try this
http://upload.teamuscellular.com/36p
Or this
http://upload.teamuscellular.com/8zz
Which I found here. http://forum.xda-developers.com/galaxy-s5/unified-development/cellular-galaxy-s5-sm-g900r4-t3024022
I really messed up my phone :/
Hi, so about one month ago I decided to root my phone, but I did not know what I was doing since it was my first time and I was VERY confused. I ended up causing my phone to go into a bootloop, I'd first to even get it to work make it I'd make it go into download mode then restart from there. It'd just say in the top right corner "kernel is not seandroid enforcing" then afterwords it'd flicker the bottom buttons to just turn off completely. Any advice or help would be amazing , I won't mind spending time just to fix this so I'm all open
I recomend to flash the stock firmware on your phone.
Get the firmware file from fw.updato.com(fast but sometimes website is down)
Or
sammobile.com(slow but reliable)
Since you already sayd you tryed to root ur phone i suppose you know where to get odin3
Extract the firmware zip file y downloaded inside should be a .tar file put that in AP in odin and click start
Also i recomend a wipe but in theory it should* start working without.
Hope this helped you
Rainbow_Dash said:
I recomend to flash the stock firmware on your phone.
Get the firmware file from fw.updato.com(fast but sometimes website is down)
Or
sammobile.com(slow but reliable)
Since you already sayd you tryed to root ur phone i suppose you know where to get odin3
Extract the firmware zip file y downloaded inside should be a .tar file put that in AP in odin and click start
Also i recomend a wipe but in theory it should* start working without.
Hope this helped you
Click to expand...
Click to collapse
I've tried it before but I'll try it again, nothing really happens when I do it but mabey It'll work this time. I'll tell you whether it work or not
Nooooxa said:
I've tried it before but I'll try it again, nothing really happens when I do it but mabey It'll work this time. I'll tell you whether it work or not
Click to expand...
Click to collapse
Quick edit, my phone doesn't show up on the ID:COM area at all, I've tried other cables but it just won't work at all. I'm pretty sure it's from my phone itself and not the program
Nooooxa said:
Quick edit, my phone doesn't show up on the ID:COM area at all, I've tried other cables but it just won't work at all. I'm pretty sure it's from my phone itself and not the program
Click to expand...
Click to collapse
Oh no I forgot y need to have installed special drivers otherwise in some cases it won't show up. Get it from here în my experience first time it can take up to 1 hour for phone to be recognized. Also make sure ur phone is well enterd in download mode (volume down+home+volume up+power) a blueish screen appears and volume up again) there is no way it's bcuz of the phone. Also use the cable that came with the device and if it still doesn't work (for some reason) try in another pc (or mac)
Rainbow_Dash said:
Oh no I forgot y need to have installed special drivers otherwise in some cases it won't show up. Get it from here în my experience first time it can take up to 1 hour for phone to be recognized. Also make sure ur phone is well enterd in download mode (volume down+home+volume up+power) a blueish screen appears and volume up again) there is no way it's bcuz of the phone. Also use the cable that came with the device and if it still doesn't work (for some reason) try in another pc (or mac)
Click to expand...
Click to collapse
I got the driver installed and so far it's actually being able to connect ! but I have no luck at all, I put it in downloading mode, opened up oden then at a certain point my phone randomly went black then said "An error occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software" Which I did end up doing but even while using that it will randomly shut off :/. Here's the oden log
"<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> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
Nooooxa said:
I got the driver installed and so far it's actually being able to connect ! but I have no luck at all, I put it in downloading mode, opened up oden then at a certain point my phone randomly went black then said "An error occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software" Which I did end up doing but even while using that it will randomly shut off :/. Here's the oden log
"<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> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
Click to expand...
Click to collapse
Nevermind I found the issue! For some reason, my phone wasn't charged and my computer couldn't charge it enough. Dude, I can't thank you enough, I've been at this for a month now and never thought of going onto a forum. I was about to pay some guy $30 to fix it for me.
Nooooxa said:
I really messed up my phone :/
Hi, so about one month ago I decided to root my phone, but I did not know what I was doing since it was my first time and I was VERY confused. I ended up causing my phone to go into a bootloop, I'd first to even get it to work make it I'd make it go into download mode then restart from there. It'd just say in the top right corner "kernel is not seandroid enforcing" then afterwords it'd flicker the bottom buttons to just turn off completely. Any advice or help would be amazing , I won't mind spending time just to fix this so I'm all open
Click to expand...
Click to collapse
do you have flahed a custom rom?
or flash custom kernel? like audax kernel?