I could really use some help. Quick story, I was at a wedding today and I pulled my phone out of my pocket only to see the Google logo (I'm unlocked). I thought that was odd, but figured maybe it was a random reboot. Happens, right? But it never actually rebooted. I left it on that screen for maybe half an hour. Then I pulled the batter thinking my latest ROM was acting up so I would just flash back to my last nandroid. Only after pressing Vol+;Vol-;Power I got... nothing. Blank screen. Later, I could see that the LCD was actually powered up (I could see a faint light) on the Fastboot screen but nothing was actually showing. I could, however, use Vol-;Power and see the Odin Mode screen. But if I choose "Start" I go back to the Google logo and then it never boots. Crazy! I pulled the battery and just stuffed it back in my pocket until I could get home and try out ADB. :fingers-crossed:
So I got home, plugged it in and booted it up. No matter what mode I try it won't show up in ADB. I tried the Google screen, I tried the blank screen after the vol+-power and tried the Oden Mode that I could see. None of them will let me use Fastboot or any ADB commands.
I've been searching for over an hour now and haven't found a solution. So, I'm asking now. I'm not a super-user but I'm no n00b for sure. I just don't know what to do now. I can't flash a factory image because I can't get the device to show up in ADB and fastboot. What could I be missing?
Thanks for reading my story. I hope it gives you enough info for ideas on how to help. Some final info:
Model: Toroplus rooted and unlocked
ROM: Last CM Nightly (11/16/12)
Recovery: ClockworkMod 6.0.1.5
I'm seeing three screens. Google, What I think is supposed to be Fastboot and the Odin Mode. Not 100% sure on the terms there, sorry.
I took the battery out all night to let it deep reset. Still nothing. Just sits at the Google screen indefinitely.
What am I missing?
Sent from my Nexus 7 using Tapatalk 2
Had the same thing happen to me. Thought it was the battery, so I tried a different one. No go. Luckily, being unlocked and running different roms, was able to get to recovery, and since I always keep a nandroid of my current rom, I was able to flash it and all is good now.
---------- Post added at 12:17 PM ---------- Previous post was at 12:13 PM ----------
But yours won't go to recovery? That's weird man, don't know what to tell ya.
That's the tough part. If I could just get to recovery I could fix this with no problems. But I can't seem to get it to load up. I'm wondering if there something that can be done from that Odin Mode screen where I can see it says "Download. Do not turn off target." ?
Update:
OK, I guess you can never search enough. I found shabby's guide and realized it might help. I'll try this and see if it will read the device. Wish me luck....
http://forum.xda-developers.com/showthread.php?t=1620036
Good luck, let us know how it goes.
Well, Odin Mode is allowing a connection, and it seems to be writing to the phone (that seems like good news!) BUT it keeps stalling while flashing the radio-cdma image file. I've tried it about 6 times now on two different computers and two different USB cables (one of which is the stock cable) and it won't go past this point. I'm encrouaged that the Odin software (using Odin3 v.1.87) can see it and flash the first images. This is what I'm seeing:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9250XXSPH-L700FH05.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> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> system.img
<ID:0/004> userdata.img
<ID:0/004> boot.img
<ID:0/004> radio-cdma.img
I can't seem to find another TAR to try though. Shabbypenguin's is the only one I can find. Is it possible to flash the seperate IMGs from the stock FH05 via Google in Odin? I can't seem to find a how-to on that. They all say to flash it in Fastboot, which I can't access.
UPDATE:
Odin would't flash any TARs with the radio-cdma.img in them. I built a new one using MSkips Toolkit and left out the cdma radio, which Odin took and flashed. But no progress on the problem. I think my CDMA radio might be fried? Does this match anyone else's experience with this?
Last report: Took the device to Sprint repair store. Absolutely couldn't fix it so having it replaced. Consider this topic closed.
Related
OK--1st post EVER in a forum, so I feel like I'm gonna get layed into,
but here goes:
Just got Epic Touch two days ago and felt I needed root so I downloaded
and used the EL29 Odin one-click method of flashing the stock rooted ROM.
This was yesterday. No problems. Took 15 minutes. I installed some apps,
then I installed ROM Manager And tried to use it to install CW, but I'm not sure if that was successful, as I tried to do a couple of NAND backups from within the GUI
of ROM Manager and failed both times, going to the stock android recovery screen.
I think I pulled the battery both times.
Then I installed Widget Locker, was playing around with that for a bit, took
a photo and tried to attach it to a text response, then the phone locked while
I was sending that. Pulled battery, wont get past Samsung startup screen.
Looked around a bit, decided to try and reflash using the one-click method.
I get:
<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 v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.bin
every time. BTW, I cannot access anything with VolUP+power buttons.
I've tried different combos of that, always Samsung boot screen hang.
I can get into Odin, and Odin sees my device. but never has the device indicated
that anything is happening. No progress bar.
Also, I have tried the two USB cables that i have in all the ports of my computer,
but I do not have another handy.
So I poked around and found this:
http://forum.xda-developers.com/showthread.php?t=1492771
which suggested I individually flash ROM, kernel, and modem.
none of that has worked, either.
Flashing the modem does get a green progress bar(in Odin, not on the device),
but then it hangs at--
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> modem.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
flashing kernel yields:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_KERNEL_PDA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
...and a hang.
So....... haven't foud anything else adressing this. Lotta stuff out there about
careless ICS/CWM brickers, but I didn't do anything fancy, did I?
Just stock rooted, 5 hours of use and blammo.
Thanks for the assistance.
Are you using Kies or the full Samsung driver suite? Also, have you tried (with the phone still unplugged) running the one-click odin on the pc, getting into odin mode on the phone and THEN plugging the phone in?
Edit: If you need them, the samsung drivers are here:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Please remove kies prior to installing them. In any case, you should probably uninstall what you have now and install the driver suite if it's still not working, then reboot the pc and try again. Sometimes the drivers aren't working correctly and require a reinstall.
I was gonna suggest a pc reboot as well, often times that helps when Odin hangs on me.
Once you get recovered I'd suggest not using cwm manager to install a custom recovery, instead get one from these forums which is specifically for the epic touch.
The original epic had a method of reaching download mode with the battery removed, not sure if that's an option here maybe someone can give the procedure.
Sent from my SPH-D710 using XDA
I think what Rocket meant to say is not use Rom Manager any more.
Sent from my SPH-D710 using XDA
RE:
>> Are you using Kies or the full Samsung driver suite? Also, have you tried (with the phone still unplugged) running the one-click odin on the pc, getting into odin mode on the phone and THEN plugging the phone in?<<<<
I have BOTH installed...but Kies I only installed midway (i.e. this morning)
through troubleshooting. nonetheless i will uninstall/reboot/reinstall/reboot
with these guys. Which is better?
And YES, EVERY time i've tried something with either EL29 oneclick or 1.85 regular Odin, I have always started Odin first, and then plugged the phone in.
If I plug the phone in before putting it in download mode, it just displays an empty battery charging icon, and cannot be turned off except by removing battery.
RE:
>>>>I was gonna suggest a pc reboot as well, often times that helps when Odin hangs on me.
Once you get recovered I'd suggest not using cwm manager to install a custom recovery, instead get one from these forums which is specifically for the epic touch.
The original epic had a method of reaching download mode with the battery removed, not sure if that's an option here maybe someone can give the procedure. <<<<<<<<<<
I HAVE rebooted, several times, though perhaps the driver/drivers are an issue.
I have to go out of town tonight so I'll try some more tomorrow and repost.
Pep talk, though: If it goes into download mode, there's a 99.9 percent chance that I can recover it, right?
Thanks for the replies.
iguai said:
I HAVE rebooted, several times, though perhaps the driver/drivers are an issue.
I have to go out of town tonight so I'll try some more tomorrow and repost.
Pep talk, though: If it goes into download mode, there's a 99.9 percent chance that I can recover it, right?
Click to expand...
Click to collapse
It sounds like you're ok but Kies needs to go, it conflicts with the regular drivers and causes issues using odin. Goood luck and let us know how it goes.
make sure the samsung drivers are on you PC/Laptop. make sure your computer sees your phone. I have read that sometimes trying different USB ports and cables can be helpful as well when using Odin. hope this helps.
OK--- uninstalled Kies and reinstalled Samsung drivers and restarted and such.
Tried oneclick and still getting stuck at recovery bin.
Tried all three usb ports.
iguai said:
OK--- uninstalled Kies and reinstalled Samsung drivers and restarted and such.
Tried oneclick and still getting stuck at recovery bin.
Tried all three usb ports.
Click to expand...
Click to collapse
You're likely bricked. Sorry. Rom Manager has been bad for almost all Samsung phones.
Sent from my SPH-D710 using XDA
Allow your phone to charge for SEVERAL hours.
Follow this guide to the letter: http://forum.xda-developers.com/showthread.php?t=1274337
Flash this rom which has root: http://forum.xda-developers.com/showthread.php?t=1703406
If you follow this correctly and your phone does not boot. You are bricked.
Sounds like somehow you reversed the modem or rom and flashed them between the phone and pda (which I hope you didn't because you are bricked if you did... but its good in away because you can take it back and say look what I woke to...).
Let us know if it works...
Edit- and if it does boot, don't ever try to install cwm with rom manager on this phone.
No dice. I am, however, going to give it one more try on a friends computer this evening. That's my last throw though, I think, unless I get some fresh inspiration.
I'll report back tomorrow.
OK---I gave it everything, and no dice.
This phone was bricked.
I believe using ROMManager to try and install CWM f'd some things,
and perhaps when I was trying to do individual flashes
in Odin I flashed a modem in PDA.
Thanks for all responses.
Tried everything and nothing
So I wasn't trying anything crazy with my phone, left it charging, and went to check the time and it was off, tried turning it on and nothing.
I was running CM10 Beta 2... so I went into recovery mode, tried to run do wipe factory reset, wipe dalvik, wipe cache, flash the CM10 again, and it was getting stuck.
Mounted usb on pc and tried to save some files to flash the full tar through odin, in the middle of that copy it failed, so I tried to odin the tar anyway and it was getting stucked.
Tried flashing modem separately - stuck on Wait 2 mintues...
Tried flashing kernel separately - stuck on NAND Write Start!!
Tried flashing rom - stuck
Tried flashing pit file - stuck
Tried one click - stuck
The thing is that I can't just say to samsung service that I didn't do anything to the phone, because when you try to boot in recovery it shows CWM 6..., but only one line, it doesn't really load cwm.
So even if I use a usb jig to reset odin counter, they'll notice I had done some stuff to the phone, even when I wasn't really doing anything when it crashed.
Any new way to fix the phone? I don't have insurance or anything, so I might be pretty much screwed
Anything else I could do? Thank you very much!
I've been using the CM9 6/18 nightly, and it was working perfectly, no problems or glitches, until this afternoon when I left the phone on my desk for an hour, not connected to any computer or charger.
The screen wouldn't turn on, even after repeated tries and long waits, so I held the power button until it restarted. When it did, it booted to a screen that said that the encryption of the phone's storage had been interrupted, plus an option to do a factory reset. I couldn't get to the launcher or any other part of the phone. I'm baffled by this, because I don't remember ever touching any setting having to do with encryption! I honestly don't know why it would be encrypting anything.
Knowing that doing a factory reset on one of the leaked ICS kernels could cause a brick, I just restarted the phone again to see what would happen. This time, the phone froze part way through the CM9 boot animation, so I said "screw it, I'll just Odin EL29 recovery," which worked. I then flashed the CM9 Alpha 5 build on top. I did not wipe because I was hoping I could just flash over like I'd been doing with all the other CM9 Alpha 5/Nightly builds to hopefully retain my data. In retrospect, this was probably really stupid. The rom seemed to flash successfully, but when I restarted the phone, it never got past the Samsung logo.
Then I remembered the Alpha 5 had no built-in recovery, so... I decided to Odin EL29 again. This time, however, Odin never got past:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> StockCWM-EL29.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> Firmware update start..
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!
I tried EL29 OneClick, but that also never gets past flashing the first thing, recovery.bin. When I try to boot the phone normally now, it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
So, any suggestions? Am I totally out of luck?
Any help or opinions
I hate to do this, but this post has been up a while and I'm getting desperate, I know I've done everything I can think of but the fact remains that everything I Odin stalls as soon it actually tries to write to the memory of the phone. ADB does not connect. My fear is that the phone's storage was in fact partially or wholly encrypted, and therefore inaccessible.
However, I know there are many people here who are much more knowledgeable than I am, all I would love is an educated opinion or suggestion about whether there is anything that I could possibly try. Otherwise I guess I'm going to have to order a USB jig and reset the counter, then try to get Credo Mobile to replace my phone under the limited warranty...
Search for the Odin el26 one click for recovery. It will get you back to complete stock. The file is like 300mb or something. It "should" fix your issues.
Sent from my SPH-D710 using XDA
brooksyx said:
Search for the Odin el26 one click for recovery. It will get you back to complete stock. The file is like 300mb or something. It "should" fix your issues.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I appreciate your help; unfortunately, I've tried the el26 one click, as well as a few other GB one clicks. It's always the same thing: Odin hangs at flashing recovery.bin.
On another note: out of my vast, desperate stupidity, I tried to flash a .pit file through Odin. It hung, just like everything else. I let it sit for 30 mins, but nothing happened, so, despite the warning NOT TO TURN OFF the phone, I pulled the battery and disconnected. Now, all I get is a constant blue light.
I guess my only hope is that the USB jig I just ordered will let me get back into download mode.
I figured I would post this as a basic how to for people who brick their phones because they are in a similar situation.
Sprint Samsung Galaxy Note II SPH L900
Used this root method because it was for Samsung Note II owners who already had Android 4.3.*,
http://honai-android.blogspot.com/2013/06/how-to-root-galaxy-note-2-sprint-sph.html
Installed TWRP but it didn't stick to Download mode. I could boot into TWRP when my phone was up even after rebooting but could not boot the device directly into TWRP to access my custom recovery image.
Installed Perseus and Macks Rom AllStar V5.0 after saving them to my SD Card and did this after booting into TWRP from within my stock ROM.
Like an idiot I didn't read all the comments on ChainFire 3D when I was searching root 3d because I'm on a big kick right now of making it all 3d like.
Instead of flashing ChainFire 3d from recovery I used my in rom option since I had all my root programs running nicely and thought why not its just a button click instead of rebooting into TWRP. There was my mistake.
Alright so now I am bricked out of my phone in a boot loop. Nothing is happening but ChainFire said when you install not to freak out if your phone hangs for awhile, pull the battery after two minutes. Well I did and still bricked in a boot loop.
Scour the forums and Internet because I know I still have access to my phone through Odin. I don't have debug mode turned on so I can't even create an ADB shell to my device. That was my first through, run ADB shell, launch TWRP and restore my custom recovery. Would have worked except I had no way of getting to TWRP. Tried installing the Samsung ToolKit. Couldn't recognize my device.
Opened Odin back up and thought why not try to flash TWRP and have it reboot, maybe TWRP will launch. Well I don't know if that would have worked or not because every time I tried to reflash TWRP Odin encountered an error.
Alright, abandoned that idea and did some more research. I knew I could still flash to my phone but I didn't have anything to reset the caches to install another ROM and I didn't want to install something else where things could go potentially worse. I needed my damn phone back. Boom! Found some very helpful articles on restoring to stock and found the stock recovery one click solutions.
I am making this so lengthy in case you are going through something similar where you are stuck in a boot loop, locked out of TWRP but can still flash to your phone with Odin.
These two threads were massive help and they take you to the file locations:
http://forum.xda-developers.com/showthread.php?t=2116490
http://www.sxtpdevelopers.com/showthread.php?t=154
I restarted my phone in download mode which was a little tricky because when I put the battery in it would start booting. Had to make sure volume down, home and power were pressed while sliding the battery in. It's tricky but you can do it with one hand and use the other to insert the battery. Don't give up just because if you put the battery in your phone automatically boots!
I used this specific file. http://rwilco12.com/Files/Devices/S...Unrooted/SPH-L900_MA5_853599_Stock_Nodata.exe
I didn't know if my phone was MA5 or MA7. I was worried that something would be off if I downloaded the wrong one but I chose MA5 oneclick exe and it did the trick. I used the Rooted version that didn't delete my data so when the phone came back on all my changes were still there. Everything from the kernel was gone but my settings and etc were unaffected.
By the way I had to disconnect and reconnect my phone in download mode when running the Odin OneClick MA5 restore to get it to light up yellow and establish the connect. I tried to run it a couple times and it failed which made me pretty discouraged. I thought that it was because I downloaded MA5 restore and not MA7. It wasn't because of that, it was because even though the computer recognized the oneclick program didn't.
So anyways, there are some resources and an additional thread. I'm pretty tech savvy but when the damn thing bricked I wasn't for sure what to do. Hopefully this is semi helpful for someone.
*Cliff Notes:
If you brick yourself out of your Sprint Samsung Galaxy Note 2 (II) and you can't access recovery, go download one of these oneclick solutions from sextape or garwynn (big ups to you guys) and reflash it from download mode using their programs. If you rooted your phone using Odin you will feel right at home with their software and it is no big deal. Phone will be back up in no time.
Edit: So after I got back to my stock ROM and tried to reflash my previous roms they wouldn't stick. E Signature verification kept failing but I still had root. Used CWM Recovery straight out of the app store and rebooted in recovery. Wiped everything. Used the esignature toggle and disabled it. Bam was able to reinstall roms and I am back to tinkering
The title was misleading. I thought you meant a hard brick. What you encountered was a soft brick aka bootloop. Thanks for writing it up for the noobs though.
Sent from my SPH-L900 using Tapatalk 4
Yes title is misleading but great post for us thats need it
Thank u much for ur time to make this
SGN2
I bricked my sph l900 also..I had 4.3 rooted then went to jellybomb had a back up of my 4.3 rooted. Flashed back to it and it's now stuck in note 2 animation. Can't get into recovery or adb. Plz can anyone help ?
Sent from my SM-N900P using xda app-developers app
Is there a fix ?
Sent from my SM-N900P using xda app-developers app
odin oneclick failure
I followed your guide above using Odin OneClick MA5 restore and this is the results I get everytime in ODIN. My issue is not solved.
<ID:0/004> 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/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>
<OSM> All threads completed. (succeed 0 / failed 1)
kevo7000 said:
I followed your guide above using Odin OneClick MA5 restore and this is the results I get everytime in ODIN. My issue is not solved.
<ID:0/004> 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/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>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to use the original Samsung USB cable.:good:
new battery issue
gizmoscoop said:
You need to use the original Samsung USB cable.:good:
Click to expand...
Click to collapse
I used every cable I owned oven the original cable for my Note 2. I ended up taking it to sprint and replaced it. With this new note I've had two batteries completely fry. 100 % but will not power on without charger.smh
What is it that you did when the onclick kept failing?!!?
By the way I had to disconnect and reconnect my phone in download mode when running the Odin OneClick MA5 restore to get it to light up yellow and establish the connect. I tried to run it a couple times and it failed which made me pretty discouraged. I thought that it was because I downloaded MA5 restore and not MA7. It wasn't because of that, it was because even though the computer recognized the oneclick program didn't.
I keep running the NA5 Stock NoData exe and it keeps failing
Hello Guys!! I'm hoping someone can give me a hand. I got a Samsung Galaxy Tab Pro 8.4 (SM-T320) that is soft brick. If i'm not mistaken the device was been updated via OTA and crashed. Every time i try to turn on the device I get the following message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". For some reason I'm not able to boot the device into recovery mode. It seems the partition got damaged. Please note that I'm using the following commands to boot into recovery mode (volume up+home+power). I have tried connecting my tablet to Samsung Kies v2.6.3.14074_11 and use the option "Firmware Upgrade & Initialisation" but at the end of the procedure I get the following message "This version of the device cannot be updated". I have attempted to flash the device using Odin v3.07. The stock ROM I used was T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5. The Odin PASSED and reset device but the phone did not boot back up. It just gets stuck on the boot screen. I have also tried to flash the device with custom recovery cwmr-20140605.tar. but I didn't have any luck. If anyone has any ideas or solutions, please let me know. I'll greatly appreciated.
bmesta said:
Hello Guys!! I'm hoping someone can give me a hand. I got a Samsung Galaxy Tab Pro 8.4 (SM-T320) that is soft brick. If i'm not mistaken the device was been updated via OTA and crashed. Every time i try to turn on the device I get the following message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". For some reason I'm not able to boot the device into recovery mode. It seems the partition got damaged. Please note that I'm using the following commands to boot into recovery mode (volume up+home+power). I have tried connecting my tablet to Samsung Kies v2.6.3.14074_11 and use the option "Firmware Upgrade & Initialisation" but at the end of the procedure I get the following message "This version of the device cannot be updated". I have attempted to flash the device using Odin v3.07. The stock ROM I used was T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5. The Odin PASSED and reset device but the phone did not boot back up. It just gets stuck on the boot screen. I have also tried to flash the device with custom recovery cwmr-20140605.tar. but I didn't have any luck. If anyone has any ideas or solutions, please let me know. I'll greatly appreciated.
Click to expand...
Click to collapse
Very strange.
Did you tried another firmware version using odin?
edlabh said:
Very strange.
Did you tried another firmware version using odin?
Click to expand...
Click to collapse
I just attempted to use odin v3.09 but I'm still having the same problem. It keeps getting stuck on the samsung galaxy tab pro sm-t320 screen without recovery mode. I have attempted to flash cmw again but the problem persists. I also noticed the battery won't charge anymore. I'm not sure if this was due to a failed flash. Anyone has any other ideas?
bmesta said:
I just attempted to use odin v3.09 but I'm still having the same problem. It keeps getting stuck on the samsung galaxy tab pro sm-t320 screen without recovery mode. I have attempted to flash cmw again but the problem persists. I also noticed the battery won't charge anymore. I'm not sure if this was due to a failed flash. Anyone has any other ideas?
Click to expand...
Click to collapse
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
I managed to get my tablet to charge by tearing down the device and reconnecting the battery. After doing this, i plugged it directly to the wall. I got this idea from a youtube video. Im going to leave the battery charging all night. Hopefully tom its a good day and i have a working device
bmesta said:
I managed to get my tablet to charge by tearing down the device and reconnecting the battery. After doing this, i plugged it directly to the wall. I got this idea from a youtube video. Im going to leave the battery charging all night. Hopefully tom its a good day and i have a working device
Click to expand...
Click to collapse
Wow!
just now I realize this problem with non-removable battery. This really sucks!
How did you charge the battery? Maybe a lipo charger?
edlabh said:
Wow!
just now I realize this problem with non-removable battery. This really sucks!
How did you charge the battery? Maybe a lipo charger?
Click to expand...
Click to collapse
Im really happy to say that now i got a working tablet. I guess removing the battery did the trick.
'edlabh' thanks for all your help. I was able to charge the battery by plugging it directly to the wall. Please note that i had to take the entire tablet apart and disconnect the batteryfor 15 min before reconnecting it. Thank god im good with teardowns and i dont give up that easy
crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
Hello, I was wondering if you would help with the kernel... Idk how to do it. I have done everything he did and even opened my tablet and took out the battery but it still did not work. :crying:
---------- Post added at 07:01 PM ---------- Previous post was at 06:32 PM ----------
crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
I already tried flashing TWRP, CWM, CF Autoroot (to be able to install a custom recovery). I opened it and removed the battery for 15 mins. unlike this guy, it didnt work for me. I also tried flashing CM12. The tablet wont turn on without being plugged in and I can only access "Downloading Mode"
Perhaps the kernel is broken, but how do I fix it?
This is Odin's message, after flashing stock firmware.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320XXU1BOC1_T320UVS1BOC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
But it still wont boot past the splash screen nor can I access recovery mode.
Install Kies 3 from Samsung and try the tools -> emergency firmware recover option before anything else gets messed up.
Odin is not safe to mess around with, if you accidentally check a wrong option or use any field other then AP, you might end up with perm brick
Sometimes the vol keys are reversed try Power + the other vol key
otyg said:
Install Kies 3 from Samsung and try the tools -> emergency firmware recover option before anything else gets messed up.
Odin is not safe to mess around with, if you accidentally check a wrong option or use any field other then AP, you might end up with perm brick
Sometimes the vol keys are reversed try Power + the other vol key
Click to expand...
Click to collapse
Also, another thing is the when I plug it in and press the power button it lights up and shows the battery icon with no charge stuck in a loading icon that is not animated.
I will try your suggestion but I had already try (on Kies) Update and Recovery but it didnt work (perhaps because of the tablet being in Downloading mode?)
UPDATE: Kies 3 wont recognize tablet, even in Downloading mode (which is the only mode I can access).
Thanks!
This thread is very old. But I've the same problem, stuck at samsung logo and only get into download mode. Accessing the twrp recovery mode is not possible. I've not flashed the device and the battery had over 90% percent. I started the device suddenly it turned of and it was not possible to start it again. Has anyone solved this problem?
I didn't thought that the battery was the problem, because one time the devices started and showed about 90%, but it was the battery. The batteries are very bad for this device, this is my third one.
Hi, I've searched hi and low for help, but can't find anything that seem to apply to my phone or case. I have a Canadian Mobilicity S3 model SGH-T999V that just bricked itself. Everything is official other than I unlocked it to switch to Wind: Binary Count = 0.
The Story: Last week (Tuesday Sep 22nd 2015) The phone restarted a few times for no apparent reason, then the next day errors about missing files started to pop up to the point that I had to reset the phone to be able to use it. Start fresh all good for a week, then one restart yesterday (Sep 30) and this morning I have a screen that says: "Device Memory Damaged - the data partition has been corrupted.you need to reset your device to factory defaults.this will erase all your date. (reset device button)" I press the button nothing happens, so I take out the battery, leave it while at work, then try again: same thing - I try to reboot into recovery but fail: I get a down android with an open belly cover and a red triangle picture for a bit and the phone reboots back to the damaged memory screen. I can get into the download mode, but Odin doesn't see the phone.
Any advice on how to proceed from here would be greatly appreciated.
I've used Odin before on my Nexus S, but that was many moons ago, it's dead now...
Thanks in advance.
Can you get into download mode? If you can, yet flashing the stock ROM from sammobile.com and flash it using Odin.
Thanks for the reply.
Odin doesn't see the phone and I don't remember exactly how to use it either, but I know it's very model specific, as to files and ROMs to download and install, hence the advise seeking. I guess I'm hoping someone in the know can tell me "follow the instructions for such [more popular] model #, that will work on the 999"...
The T999v is a very popular model in Canada as it was used by Wind and Videotron.
Are you able to boot the phone into download mode? The Samsung drivers are installed? Are you using a Win7 machine?
Yes it boots into Download mode but not into recovery. I have Kies installed along with the drivers, could reinstall that just in case. Running Windows 10 Pro Preview, in the process of upgrading to the final release.
I recommend grabbing the latest firmware from sammobile.com for the phone and flash it in Odin 3.07 with the phone in download mode. I would not bother with Kies.
I've updated my build of Windows 10, that may have been one of my problems, now Odin reacts to the phone but fails:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNH2_T999VYVLFNH2_T999VVLUFNH2_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> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone says in red: "Secure Check Fail: aboot
So much for that! guess it's fried at the hardware level.
I'm thinking you are suffering from a hardware failure as stated by the message you mentioned before. It has happened to others and I can't recall anyone having much success in restoring functionality.
If you want to try again though, uninstall kies from your computer as it interferes with Odin. There is also a newer version of Odin, but I doubt that would make much difference on the S3.
If you are unable to get it working again and want a relatively cheap fix, search ebay for a used motherboard or a device that has a broken screen but otherwise works. Then swap out the board.
Sent from my SGH-T999 using Tapatalk
The update is failing because the ROM you are flashing has a bootloader that is older than the version currently installed on the phone as verified by the following stop error in Odin:
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
I have a feeling DocHoliday77 is probably right, I've bought a new phone from my provider for 9$ (Alcatel onetouch Pop D3) and posted a wanted ad for broken S3 ... not ready to completely give up on the S3 just yet, but neither do I have high hopes.
Getting rid of Kies
The firmware is the most recent for the SGH-T999V on sammobile.com - I can try without the V maybe
Only T999V firmware will work on the T999V.
If you are selling it and it has a good working display you should be able to get a decent amount for it still. Not sure how much they are going for these days but it's always been the most expensive and in demand part for the device.