Hey everyone! So I kinda messed up when I was rooting my phone. I ended up using Kingo Android ROOT to Root my Samsung S III. Well, things didn't exactly go quite as planned (person left out a step which caused it to mess up). Through some online research I downloaded the latest Samsung update from samsung-updates. I extracted the .md5 file into Odin and followed someone else's online steps. I noticed in the videos that in both Kingo and Odin beside the name it says the model number, and it did for me the first time. Now Odin just says "Odin3 Model Name " and nothing there. It went through the process and said Pass! at the top and the (success 1/fail 0) however when I go to restart the device it just stays at the "Samsung" screen with the LED light fading in and out.
The mess up with Kingo was I didn't reset it with the cable still attached, it said it was finished so I unplugged it - I guess that's where I went wrong.
With Odin I only left "Auto Reboot" and "F. Reset Time" checked, I didn't do anything else.
Does anyone know how to fix this issue from here? I feel like I'm right on the edge of fixing the phone but not quite there.
As with many people I seriously need my phone right now, my girlfriend and I are moving from Alberta (Canada) to B.C. (also Canada) at the end of the month as well as buying a new car... I need my phone right away for everyone to be able to contact me.
If anyone has questions, I'll do my best to answer them as clearly and with as much information as possible.
Thanks!
Boot recovery and factory reset. Hopfully thatll take care of it. (It will wipe internal sd card and apps)
When I flash with Odin, I often manually restart the phone rather than using Odin. I remove the cable when I see the word "reset" appear in the status window and it hasn't caused a problem for me yet.
Related
Hello all! Let me start by saying that i have researched a ton and there is a lot of great information on here. The info I've read however doesn't seem to work for me.
My situation is I spilled a little bit of water on my phone (really not much), but it got inside my phone a little, which was already rooted using auto root. My power button thinks its constantly being pushed (i think). It doesn't bootloop, but as soon as i pop the battery in it turns on, and my phone was unresponsive to me clicking the power button. The rest of the phone was fully functional and i checked with Tmobile and it is still under warrenty (didn't mention the water). They told me to backup the phone which i was able to do in kies with no problem. Then they said do a factory reset, which again I did with no problem. It didn't solve my issue which i kinda knew it wouldn't, so the next step for me was to unroot my phone so i can return it. I popped it in odin, selected the original firmware and it started , then it disconnected by itself. Now the firmware upgrade screen pops up, but i am still able to get it into download mode (for me since the power button is suspect) i just have to hold the home and volume down, pop in the battery and it goes to download mode. The problem is that every time i try to hit start in Odin it gets to the part about the PIT partition and disconnects and says there is no PIT partition. Everywhere i've read says to either use a PIT partition (can't find one for the M919) or that the partition is in the m5 file, which as far as i can tell it is not (at least not it's own file). I've tried downloading the stock firmware from a multitude of different places even Sammobile with no luck and I've also tried different computers, different cables, and all the USB ports available to me.
Can anyone please tell me where to go from here please? I need to get this replaced asap!
Are you asking for a .pit file to repartition? If so, I've attached one for a 16GB SGH-M919 ONLY, dumped from my own SGH-M919 through Heimdall. Download the .zip, unzip it somewhere. In Odin, check repartition, and click PIT and select this file. Hopefully this fixes your problem, but use this at your own risk.
View attachment SGH-M919.zip
Well my first flashing attempt didn't go too well. I'm new to all things Android so please go easy on me here. I decided to dip my toes in this flashing business and look where it got me? LOL! Hopefully the following description makes some sense. I'd appreciate any help in this matter.
Device: Samsung Galaxy Tab 3 SM-T210R Wifi
Goal: Flash to KitKat 4.4.2 following a guide on droidviews.com.
I followed the guide in the link above and thought everything was humming along fine. Once I got into Odin and added the md5 flash file, it looked like it was running fine and then I got the dreaded FAIL. So what I did next was unplug the usb cable from my PC and then shut off the Galaxy Tab afterwards wanting to start over from scratch again. But it appears that I did more harm than good. Now I'm not able to get back into "Download mode" via the "Volume Down + Home + Power" button combination. The only thing that'll come up on the screen is the following:
ODIN MODE
PRODUCT NAME: SN-T210R
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
HW REV: 0x5
Yellow Exclamation icon
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
After Googling for workarounds to this dilemma, I'm seeing people say that flashing back to stock firmware is likely the best idea. But from what I'm gathering, in order to do this, I'd have to get the tablet to boot into "Download mode" and this is where I'm stuck, because I'm not able to get to that part in order to flash back to stock firmware. I've read that you have to go to sammobile.com and find the region-appropriate stock firmware file and apparently the U.S. version is called "Cellular south" for some reason, so I went ahead and downloaded that particular file. But now what? Is there another method that I should try to get to "Download mode"? No matter what buttons and combination of buttons I push, the dreaded screen description I posted above is what comes up.
Any ideas?
Thanks
Solved.
Called my nephew. He had it fixed within 5 minutes. He did everything so quickly, so I didn't really follow how he did it, but he said basically to unplug the USB cable, reboot computer, plug USB cable into PC but leave the other end of the cable unplugged from Galaxy Tab. Open Odin and input the md5 file. Once Odin shows the file is loaded up, then plug other end of cable into Galaxy Tab and click Start. Voila!
Nice,
I like to see users reporting. I know it is your first and yourself where not sure. That is fine. But Report or Feedback helps others, by learning from your mistakes.
This is the time we realize we are getting OLD. Our nephews can do what we can not in no time!! Boy I hate this.
I had rooted this phone, and yesterday, gave ti to my son. We paid it off yesterday. He went home and wanted to downgrade, because he had read that the home button issue we were having was related to an update. I am actually not sure whether the phone was running 4.4.2 or 4.4.3, as of the time I rooted the phone. It's been months.
The phone is now in a state of being write protected from any attempt made to flash it using Odin. The message, with a Yellow Triangle, on the phone was "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." In the upper left corner of the screen was a message of several lines in length, the last two lines are greyed:
"WRITE PROTECTION: ENABLE
eMMC BURST MODE: enabled"
Today, after school, we tried to flash it using Odin again. He has found basically the same information I have, but he understands it better than I do. I fear I do not grok the vernacular very well (recovery, rom, flash, PIT,... ) I am only a Linux guy.
Now the results, over and over, are "FAIL!" in red on Odin, and approximately "write failed."
We are all distraught about this. I rooted the phone because an application I needed required it to be rooted, and never felt comfortable with the process. Pleased it worked. My son had no idea of all this, but has gallantly trudged onward as he ploughs through the various web sites offering soliutions.
We would all be very pleased to find a way out of this. Is there hope?
Second, we don't know what kind of shops might exist that can help us out. Who can perform the procedures, for a fee. Maybe T-Mobile or Samsung?
Thank you in advance. Heck I'd even be stoked to receive some suggestions for "Android unrooting for dummies" reading.
Thank you,
Alan
Flash latest 4.4.4 NH7 in Odin, should fix you right up. Links to firmwares are in general section
You bricked your phone. Check out this link...
http://www.androidayos.com/2014/03/...-s4-m919-t-mobile-unbrick-and-recovery-guide/
I'm a total newb at hacking on my device, and my device wont start. I've got a bone stock t889, never been rooted or tampered with. for the last month or so when i reboot the device, i'm greeted with something about my UUID's being messed up (please forgive my lack of proper terminology here, i can't remember exactly and thats what my memory serves) and to proceed with caution. So i click the "I'm feeling lucky button" and continue on with normal use. Things were'nt totally right, apps wouldnt work and would randomly shut off. I let the device die one night. it got stuck and wouldnt reboot - hangs on the "Samsung Note 2" screen. If i plug in the charger it hangs on the image of the drained battery (wont show the battery with a little bit of green).
Now really getting to the point ... Just for poking around's sake i gave it the 3 finger salute and brought up recovery - which worked. It however speaks of system errors. Here what i see verbatim `E:failed to mount /system (Invalid arguments)`. It also says something about `# Manual Mode #` and then some more failed to mount (same as before).
So, can someone shed some light on whats going on? I did a factory reset/cache reset if that matters. Ultimately id like to just wipe everything and a newer os on it like 5.0.
So my second question is, with my device in this jacked up state, can/how would i go about flashing everything?
Like i said, im new to all this and have googled around on lunch breaks and have come across all kinds of stuff on rooting the device / copying files to it first then going into recovery ... / using odin to just do it / < enter x amount of articels on the subject >. I'm not totally sure where which way to turn.
Thanks for any help!
i would say try to odin it back to stock 4.3 with the factory image available on sammobile.com. read up before you do it though. theres plenty of walkthroughs for it
thanks, but im still on 4.3. i've done nothing to the device. i'm gathering intel before doing something.
initial post was long winded, togonna boil it down:
- can i recover from an error such as "E:failed to load /system (invalid arguments)" ?
- can i recover my device if and only if its booting only into recovery.
i know its a possibility, but i dont want to permabrick this thing if i can help it.
thats why you odin it back to stock. it'll put it or should put it back to the way it was when you took it out the box
tmobile hasn't released 4.4.2 for our note 2's yet let alone 5.0, which is why i said 4.3
sounds to me like a hardware issue which odin won't fix but worth A shot to get it working.
other then that i don't know what to tell ya.
ok understood re the versions.
im on a mac, so i dont have odin. i tried jodin3/heimdal, but given the state of my device i can't connect to it. adb wont detect. however, if i putthe device into "apply update from adb" or "apply update from external storage" i can get adb to _see_ the device.
idk, so far no good.
@overdrive, what makes you think this is a hardware issue?
based on original post. system sounds borked to me. almost sounds like internal storage space could be having problems reading. i could be wrong though
you don't have access to a pc? borrow a neighbors long enuff to run odin, put your device in download mode and connect it. let odin find it and load the md5 file and start it. see if it has any problems when restoreing system partition. it'll tell you. if it works fine then your device is fine and will boot right up when it's done.
now, i have no idea if this is the actual definition of "soft bricked"... so ill just tell you my story.
ok... so a quick history... phone was never rooted... ota update in november caused the phone to reboot every time the screen went off. had to install "wakelock app" to make it usable... update in december caused the phone to not be able to turn on. im not sure what happened. started the update, let the phone sit for a little while... when i looked at it again... nothing. it was just dead. no buttons would turn it on. had to get a new phone. note 4 was a private purchase, so no warranty options.
after leaving the battery out for a week, it would turn on but get stuck on verizon screen, get real hot, and every 30 seconds, blip a vibrate and a screen flash.... so... i tried clearing cache, tried a FDR... nothing. so i basically tried what is on this page:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
with the newest firmware through odin... i unzipped the file, put the phone in download mode, connected it, waited for blue box, browsed to tar.md5 in "ap" box, and hit start when ready. got an error, after a while, i pulled the battery, and now when i turn on in download mode it says "your device didnt update successfully. use the verizon software repair assistant on a computer to repair your device and complete the update"
kies does not recognize my phone... i can't find a software repair assistant. if i try to run odin again, it just gives me "complete(write) operation failed"
hoping i can figure out how to salvage this thing. not super hip to phone software. ive managed to root numerous phones in the past. this is the first time ive had an issue, and its with the first phone i didnt root.
thanks in advance. sorry if this is totally newb level stuff. i just really need help, and get lost real quickly trying to do my own research... but trust me, ive tried.
idiggplants said:
now, i have no idea if this is the actual definition of "soft bricked"... so ill just tell you my story.
ok... so a quick history... phone was never rooted... ota update in november caused the phone to reboot every time the screen went off. had to install "wakelock app" to make it usable... update in december caused the phone to not be able to turn on. im not sure what happened. started the update, let the phone sit for a little while... when i looked at it again... nothing. it was just dead. no buttons would turn it on. had to get a new phone. note 4 was a private purchase, so no warranty options.
after leaving the battery out for a week, it would turn on but get stuck on verizon screen, get real hot, and every 30 seconds, blip a vibrate and a screen flash.... so... i tried clearing cache, tried a FDR... nothing. so i basically tried what is on this page:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
with the newest firmware through odin... i unzipped the file, put the phone in download mode, connected it, waited for blue box, browsed to tar.md5 in "ap" box, and hit start when ready. got an error, after a while, i pulled the battery, and now when i turn on in download mode it says "your device didnt update successfully. use the verizon software repair assistant on a computer to repair your device and complete the update"
kies does not recognize my phone... i can't find a software repair assistant. if i try to run odin again, it just gives me "complete(write) operation failed"
hoping i can figure out how to salvage this thing. not super hip to phone software. ive managed to root numerous phones in the past. this is the first time ive had an issue, and its with the first phone i didnt root.
thanks in advance. sorry if this is totally newb level stuff. i just really need help, and get lost real quickly trying to do my own research... but trust me, ive tried.
Click to expand...
Click to collapse
do a battery pull to shut off your phone then boot into download mode like normal unzip and flash this ( https://www.androidfilehost.com/?fid=24588232905720219 ) in the ap slot.
do a battery pull to shut off your phone then boot into download mode like normal unzip and flash this , link was here, in the ap slot.
OP, did you try this process listed above and did it fix your problem or did you something else? Thank you.
SPIRITJCC98 said:
do a battery pull to shut off your phone then boot into download mode like normal unzip and flash this , link was here, in the ap slot.
OP, did you try this process listed above and did it fix your problem or did you something else? Thank you.
Click to expand...
Click to collapse
nope, didnt work. was pretty pissed at the time. i had to give up and get a lgv20.