So I'll preface this by saying I'm pretty new to this whole thing and don't exactly know what I'm doing (big surprise to most of you, I'm sure). Around a month ago I attempted to flash CM9 on my Epic 4G Touch, and after a few hours and a lot of reading through this forum I was able to get it to work without any major issues. I liked it but continued to experience issues with various wireless capabilities (wifi, mobile data, GPS) that I'm pretty sure are just a problem with the phone, but today I decided to try to give CM10 a go anyways to see if it might solve the problem.
Here's where I made two very stupid mistakes - first, I assumed that since I figured it out before I would be able to do it again this time from memory. Second, and probably worse, I did not really keep track of what exactly I did, so I can't explain with certainty the steps leading to the problem.
So, here's what I think I did:
Pretty sure I started off by going into download mode and and using the Odin one-click executable to flash the rooted stock EL29 ROM (SPH-D710.EL29_CL852097_ROOTED-OneClick.exe). I was able to boot after this, and everything seemed to work fine for stock Gingerbread. I then installed ROM Manager, and flashed ClockworkMod recovery.
Then here's where I think I first ran into problems: I tried to reboot the phone into recovery mode. From the last time I flashed a custom ROM, I remember having an issue where I would get CWM on the first reboot, but after that it would go back to normal (or is this the intended design?). I cant quite remember, but I think I booted into recovery mode and somehow only had the default recovery. At this point, for some reason I decided that as long as I was here I should go ahead and factory reset and clear the cache (why I did that, I don't know). I know with some Samsung devices there is a bug where the factory reset can brick you phone, but I thought this was only when doing it from an ICS rom and I'm pretty positive that I did this from Gingerbread.
Instead of just reflashing the stock ROM and starting over I decided to just flash CWM again from Odin. I booted into download mode and opened up Odin 1.85. I selected a file called "StockCWM-EL26.tar" for PDA. I'm not quite sure where I got that, it was left over in my phone folder from when I flashed CM9. I do think it works, however in what I'm absolutely sure was a big mistake I was also under the impression that I needed to repartition and loaded "1_02_20110310_emmc_EXT4.pit" in the PIT field. I'm not sure where I got that one either, but from a search I did on the name I got the impression that you should never use it.
At this point I was able to boot into CWM, but when I tried to navigate to "install zip from sdcard"->"choose zip from internal sdcard" it gave an error, saying something about not being able to mount emmc. When trying to boot up normally, I also got an error message about a firmware update having failed and needing to use Kies. Not able to proceed, I tried to use the Odin one-click executable to go back to EL29. It failed, giving the following output:
<ID:0/003> 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/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> recovery.bin
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
This happened on additional attempts as well. Thinking I was suffering from the EMMC brick problem, I followed Jaymoon's post in this thread and used Odin to flash the EL30 ROM with the "Q1_20110914_16GB-patched.pit" PIT file. Afterwards the phone would show the standard spring "4G" boot animation, and would enter a boot loop thereafter.
That's about it. I've spent the last several hours looking through the forums, but I haven't been able to find any additional information that I'm sure would help. I figure this is about the time to ask you guys instead of probably mucking it up further on my own.
EDIT: I should say that I am able to get into download mode without a problem, as well as recovery mode (I can flash CWM with Odin and that works as well, although some directories can't be mounted).
Can you still get into download mode? If so find the fi27 one click. Use it. Do not use pit files in regular odin.
sent from MY BAD A$$ ET4G
Yes, this is where you likely borked it:
Jumpy89 said:
I was able to boot after this, and everything seemed to work fine for stock Gingerbread. I then installed ROM Manager, and flashed ClockworkMod recovery.
Click to expand...
Click to collapse
If you can't get into download mode you've probably hosed the bootloader by doing this. Really hope you have TEP and can replace it.
And I'm seeing this a lot lately so I've got to ask - where did you read that it's okay to install ROM Manager on this phone? It's been posted here for almost a year or more to not use it. I'd like to address that with your source as I think more and more are hitting that same location lately.
Thanks!
garwynn said:
Yes, this is where you likely borked it:
If you can't get into download mode you've probably hosed the bootloader by doing this. Really hope you have TEP and can replace it.
And I'm seeing this a lot lately so I've got to ask - where did you read that it's okay to install ROM Manager on this phone? It's been posted here for almost a year or more to not use it. I'd like to address that with your source as I think more and more are hitting that same location lately.
Thanks!
Click to expand...
Click to collapse
Thanks, but what's the problem with ROM Manager? Pretty much all of the "Install a custom ROM" tutorials I've seen recommend using it (although not on this site). Should I just use Odin instead? I actually can get into download mode just fine, but I do have TEP in case that's what I need to do.
Jumpy89 said:
Thanks, but what's the problem with ROM Manager? Pretty much all of the "Install a custom ROM" tutorials I've seen recommend using it (although not on this site). Should I just use Odin instead? I actually can get into download mode just fine, but I do have TEP in case that's what I need to do.
Click to expand...
Click to collapse
Rom Manager is outdated and very buggy the last time I used it which has been some time now I switched to RomToolBox for a while but didn't like it so now I don't use a "rom manager program" on any of my phones
You can find everything you need here on XDA
Jumpy89 said:
Thanks, but what's the problem with ROM Manager? Pretty much all of the "Install a custom ROM" tutorials I've seen recommend using it (although not on this site). Should I just use Odin instead? I actually can get into download mode just fine, but I do have TEP in case that's what I need to do.
Click to expand...
Click to collapse
Don't use ROM manager...it doesn't work correctly.....
Since you can get to recovery and Odin mode you might be able to still save this.
Try this:
http://forum.xda-developers.com/showthread.php?t=1865102
...and we'll go from there.
garwynn said:
Since you can get to recovery and Odin mode you might be able to still save this.
Try this:
http://forum.xda-developers.com/showthread.php?t=1865102
...and we'll go from there.
Click to expand...
Click to collapse
Thanks. Unfortunately, this happened last night and I realized that without proper firmware the battery won't charge, so I either need to first get a different battery or charger or just call it a loss and file a TEP claim.
Those instructions seem well but I would've just said to ODIN the Direct boot EL29.tar found in one of cyanogenmod's post and flashed CM10 (AFTER wiping everything)
Sent from my SPH-D710 using xda premium
Tr0LL-$_$ said:
Those instructions seem well but I would've just said to ODIN the Direct boot EL29.tar found in one of cyanogenmod's post and flashed CM10 (AFTER wiping everything)
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Seeing as he tried flashing EL29 and it failed - on recovery nonetheless - it seems something else is at play here.
OP, you might want to try a newer build as an alternative - for example, the FL16 stock restore.
The flash order changed over EL29 and the first thing flashed is the bootloader.
If this is where the problem is it may fix it and allow the rest to flash.
garwynn said:
Seeing as he tried flashing EL29 and it failed - on recovery nonetheless - it seems something else is at play here.
OP, you might want to try a newer build as an alternative - for example, the FL16 stock restore.
The flash order changed over EL29 and the first thing flashed is the bootloader.
If this is where the problem is it may fix it and allow the rest to flash.
Click to expand...
Click to collapse
Now this is strange - I downloaded the FL16 stock (rooted) Odin one-click executable here and, borrowing a friend's battery, was able to get it to complete successfully. Unfortunately it was asking me for a PIN number (don't remember having one enabled) and I didn't know what to give it. It wouldn't give me the option to just wipe my data after entering it incorrectly several times, either. Thinking I might be OK, I tried to flash the EL26 build again but it failed at the same point as before. Then I tried flashing FL16 again, but using the version that wipes user data thinking it might remove the lock. This one failed for some reason too. So I just flashed the first FL16 version again and I can't get in but at least my battery charges. Any idea on where to proceed from here?
EDIT: If I try to boot into (stock) recovery mode I get a lot of errors saying "failed to mount /data (Invalid argument)." Not sure if that reveals anything.
EDIT2: Here's what it says when I try to flash the "restore" FL16 ROM instead of the "nodata" version:
<ID:0/008> 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/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> cache.img
<ID:0/008>
<ID:0/008>
<OSM> All threads completed. (succeed 0 / failed 1)
How about FI27 instead? New flash order but ICS.... might have luck with your data partition from there, even if it is just a factory reset.
Or you could try just Agat's FI27 kernel and repacked recovery after flashing FL16 since that seems to be okay...
Sent from my SPH-L900 using Tapatalk 2
garwynn said:
How about FI27 instead? New flash order but ICS.... might have luck with your data partition from there, even if it is just a factory reset.
Or you could try just Agat's FI27 kernel and repacked recovery after flashing FL16 since that seems to be okay...
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Nice, the FI27 "reset" version worked! From there I just went back to EL29, flashed CWM, then updated to CM 10. I'm wondering if the problem might possibly have been with the battery. The only successful flashes I had were when using my friend's battery until I got working firmware and was able to fully charge my own again. Don't know if it's possible but it might have had enough juice for download mode to start but not enough to really complete the flashing process. Either way, thank you for all your help.
Related
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 can boot into download mode and my PC sees it, it shows up in odin, but it just gets stuck when flashing, no matter what I try.
You have tried EL29 stock odin one click?
BluesRulez said:
You have tried EL29 stock odin one click?
Click to expand...
Click to collapse
I did, but I'll try it again right now... thank you.
BluesRulez said:
You have tried EL29 stock odin one click?
Click to expand...
Click to collapse
Stuck on recovery.bin for a while. I'll leave it for a while, just in case, though I don't have too much hope.
yeah.. If custom recovery is still there, try this - http://forum.xda-developers.com/showthread.php?t=1865102
davidcv5 said:
Stuck on recovery.bin for a while. I'll leave it for a while, just in case, though I don't have too much hope.
Click to expand...
Click to collapse
I wish it was there... but no, is the weirdest thing. when I try to flash through odin it gets stuck, and when I try to boot into recovery, it only shows one line saying "CWM-based Recovery v6.0.1.4", but nothing else, it doesn't really load CWM, is just one line.
davidcv5 said:
I wish it was there... but no, is the weirdest thing. when I try to flash through odin it gets stuck, and when I try to boot into recovery, it only shows one line saying "CWM-based Recovery v6.0.1.4", but nothing else, it doesn't really load CWM, is just one line.
Click to expand...
Click to collapse
Might want to try a different one click such as FI27. It's possible that the flash order is different and that a different flash order may get you back in the game. Also suggest don't pull the plug on a flash. That too can mess this up.
Without knowing any more it really sounds like this is something new and that there is another factory in play.
garwynn said:
Might want to try a different one click such as FI27. It's possible that the flash order is different and that a different flash order may get you back in the game. Also suggest don't pull the plug on a flash. That too can mess this up.
Without knowing any more it really sounds like this is something new and that there is another factory in play.
Click to expand...
Click to collapse
Thank you garwynn, I'll try that one too, I've tried EL29 and FK23 so far. What other factor do you have in mind. Please let me know so I can provide as much information as possible.
Thank you all for the help.
garwynn said:
Might want to try a different one click such as FI27. It's possible that the flash order is different and that a different flash order may get you back in the game. Also suggest don't pull the plug on a flash. That too can mess this up.
Without knowing any more it really sounds like this is something new and that there is another factory in play.
Click to expand...
Click to collapse
This is as far as it gets with FI27
<ID:0/003> 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/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
Then it gets stuck.
Just tried Odin 3 with FK23 tar and got the results below.
At least this time didn't get stuck, seems like my memory card is not allowing to copy anything, don't know if give a try to re-partitioning? what do you guys think? I have read that this would be the last resort.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_SPH-D710.FK23_549262_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
you said you partially boot into cwm. does the usb connect? can you adb once it gets in that partially booted cwm?
Well where you were getting stuck did not seem like the traditional super brick where it was the /data partition and while any of the partitions could be affected it seemed like you were getting stuck at the beginning.
I would based off what I have seen so far call this as not a super brick but a phone that has had a failure period. But I could be wrong.
um do you have the epic touch or the s2 international? (what's the model under the battery). I'm just asking the dumb question because I've seen similar issues in the I9100 forums.
calisro said:
um do you have the epic touch or the s2 international? (what's the model under the battery). I'm just asking the dumb question because I've seen similar issues in the I9100 forums.
Click to expand...
Click to collapse
I have the Epic 4G Touch (Sprint) - SPH-D710
calisro said:
you said you partially boot into cwm. does the usb connect? can you adb once it gets in that partially booted cwm?
Click to expand...
Click to collapse
You rock! This is the first sigh of relief since the phone crashed. I can adb into the phone, I'll try to push some ROM, I guess EL29 for now to be safe.
What do you recommend?
Thanks a lot!
calisro said:
you said you partially boot into cwm. does the usb connect? can you adb once it gets in that partially booted cwm?
Click to expand...
Click to collapse
It reboots after 2 or 3 minutes automatically, weird. Let's see if it let's me install the new rom without restarting.
calisro said:
you said you partially boot into cwm. does the usb connect? can you adb once it gets in that partially booted cwm?
Click to expand...
Click to collapse
Actually I'm kind of lost here. I'm sorry for my ignorance, been more than a year with this device and everything went smooth until now.
How can I flash (or something) using adb?
Thank you
davidcv5 said:
Actually I'm kind of lost here. I'm sorry for my ignorance, been more than a year with this device and everything went smooth until now.
How can I flash (or something) using adb?
Thank you
Click to expand...
Click to collapse
What I am thinking is this. If you can ADB in. Then perhaps you can try this post and see if you can manually dd the partition info.
http://forum.xda-developers.com/showthread.php?t=1865102
You can do it in parts if it auto reboots on you... Look at the 2nd post for the automated method. It will have you running dd commands after you do adb pushes to your phone of the software.
calisro said:
What I am thinking is this. If you can ADB in. Then perhaps you can try this post and see if you can manually dd the partition info.
http://forum.xda-developers.com/showthread.php?t=1865102
You can do it in parts if it auto reboots on you... Look at the 2nd post for the automated method. It will have you running dd commands after you do adb pushes to your phone of the software.
Click to expand...
Click to collapse
Thank you. Was trying this solution but for some reason, I can only run the first dd command successfully, the rest just get stuck, so can't continue doing the rest.
It really sounds like hardware failure....
---------- Post added at 10:54 PM ---------- Previous post was at 10:49 PM ----------
can always try repartitioning. idk dude. but here:
http://forum.xda-developers.com/showthread.php?t=1052813
Hi,
I decided to install the nightly version of CM10 from the stable. After using recovery to install CM10 nightly, I am stuck at CyanogenMod loading screen and cannot boot into recovery nor download mode. Anyone experience the same thing? Help please
Thanks,
How are you trying to get into recovery?
Sent from my SGH-T999 using xda premium
---------- Post added at 04:13 AM ---------- Previous post was at 04:12 AM ----------
Watch zedomax do it at around 3.5 minutes in and try again
http://forum.xda-developers.com/showthread.php?t=1735561
Sent from my SGH-T999 using xda premium
gary.liu07 said:
Hi,
I decided to install the nightly version of CM10 from the stable. After using recovery to install CM10 nightly, I am stuck at CyanogenMod loading screen and cannot boot into recovery nor download mode. Anyone experience the same thing? Help please
Thanks,
Click to expand...
Click to collapse
Same issue. I installed CM10.1 12/17, everything worked fine for a couple of days, wanted to do a benchmark, moved to lightning rev3, worked fine. And then I went to recovery again, wiped. And now, I can't install anything and nothing but the recovery and download works.
I tried resetting it a >10 times through ODIN to no avail (odin 3.04).
Error: <OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVALH2_T999TMBALH2_T999UVALH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
And the error message hasn't changed in the past hour.
Stock roms seem to install fine through recovery, but they freeze at the kernel boot screen. AOSP roms are not even installing giving set_perms error (status 7).
Did you try to odin back to stock. Cm10.1 messes with sd card no bueno
sent from my Samsung Gangster S III on the T-Mobile network
md1008 said:
Did you try to odin back to stock. Cm10.1 messes with sd card no bueno
Click to expand...
Click to collapse
Yea, I downloaded both "T999UVALH2_T999TMBALH2_TMB.zip" (the old one) and "T999UVDLJA_T999TMBDLJA_TMB.zip" (the new one), and tried both. I don't think that a CM10 flashable tar/md5 is even available right now. According to TWRP, everything about the SD card seems fine. In the file explorer, I saw that except /data/media/0/, there is nothing in /media, so i moved everything from media/0 to media/ (because TWRP can do this). However, I can't run fix-permissions because I haven't booted into the ROM yet. Any suggestions? I looked up somethings, and ended up finding this: http://forum.xda-developers.com/showthread.php?t=1161769, but windows 8 is too fast. It finds and installs the drivers for my phone before I have a chance to use it through the drivers in the link ^. Any other suggestions?
No odin is only good for going back tp stock rom. I would back up sd card, odin back to stock, factory reset then flash "no tripping counter odin tar. Then flash twrp via goo manager and not flash cm10.1 till its more stable
sent from my Samsung Gangster S III on the T-Mobile network
---------- Post added at 04:13 AM ---------- Previous post was at 04:12 AM ----------
If the above doesn't work than I am all out of ideas
sent from my Samsung Gangster S III on the T-Mobile network
md1008 said:
No odin is only good for going back tp stock rom. I would back up sd card, odin back to stock, factory reset then flash "no tripping counter odin tar. Then flash twrp via goo manager and not flash cm10.1 till its more stable
If the above doesn't work than I am all out of ideas
Click to expand...
Click to collapse
Wait, was I missing something, I was flashing the stock ROMs. in the two .zips are the official Samsung .tar.md5 images taht can be flashed through ODIN. Problem is, I can't get it flashing. I don't mind if I lose my data, I have nothing there I haven't backed up in the past month. I just want my phone back.
And I figured out part of the problem. Whenever I flash one of the stock ROMs (I have Darthstalker 6 and Wicked JB 5 to work with right now) through recovery, the system is not for whatever reason mounted, and this causes most of the data to be lost. /system is empty except for a single folder /system/bin. When I chmod'ed it to 777, it gained 1 more folder and a couple more files. However, it still doesn't boot. So is this a device problem? That it not able to mount and stay mounted through a flash? Is this why the Download mode isn't working either?
ERMAGHERD! I FIXED IT. So it turns out that my old phone (t989) (which is now my mom's) has an SD card. I initially suspected that the rom zips were corrupt right? So it turns out they were. I just began to do a backup, and I had this genius idea to dl cm10.1 again and move it to my internal. Installed. Works. Boots up, but ODIN still doesn't work (not that it really matters anymore).
Hi forum,
I was going for a clean install of CM 10.1 today, when I accidentally wiped too much. After the cache and dalvik, I also did a factory reset, system wipe, and internal and external storage wipe (In TWRP). As far as I can tell there's almost nothing left on there now. I can boot into ANYTHING (the most I get a is samsung screen). Flashing a recovery through odin doesn't work (never completes a reset) and the PC doesn't seem to recognize the phone either. I've seen posts by people who either wiped the system or internal storage, but I haven't seen a solution to having flash both. Any experts know how to deal with this compounded problem?
PS: I'm a long time lurker and big fan...wish I didn't wait until something like this to start posting.
Please help!
Thanks,
Batk
Just wanted to add, the only thing I can do is get into download mode..but even then odin won't flash anything successfully.
batkbatk said:
Just wanted to add, the only thing I can do is get into download mode..but even then odin won't flash anything successfully.
Click to expand...
Click to collapse
Have you tried different USB ports(or a different computer)? Some people who had Odin problems had to keep trying it a bunch of times until it works.
Try kies emergency firmware recovery
Sent from XDA app
ndwstd staff
gc84245 said:
Try kies emergency firmware recovery
Sent from XDA app
Click to expand...
Click to collapse
But how do I get Kies to recognize the device for the emergency recovery if the phone won't turn on or be recognized.
meekrawb said:
Have you tried different USB ports(or a different computer)? Some people who had Odin problems had to keep trying it a bunch of times until it works.
Click to expand...
Click to collapse
So I tried a bunch of different usb ports with a bunch of different recoveries. Every time Odin said it failed...but all of the sudden the phone booted into TWRP...I already had cm 10.1 RC5 loaded (only think I loaded after wiping the system), so I flashed that...and it worked. Phone is back, not sure how. thanks for your help guys
batkbatk said:
So I tried a bunch of different usb ports with a bunch of different recoveries. Every time Odin said it failed...but all of the sudden the phone booted into TWRP...I already had cm 10.1 RC5 loaded (only think I loaded after wiping the system), so I flashed that...and it worked. Phone is back, not sure how. thanks for your help guys
Click to expand...
Click to collapse
U shuld flash the stock rom or ur phone is gone die thia happen to me to
Sent from my SGH-T989 using Tapatalk 2
Happened to me too, it didn't recognize the phone right away but after I selected emergency firmware upgrade it worked. So what happens when you try to turn it on or put in download mode, any sign of life at all?
Sent from XDA app
esema1o said:
U shuld flash the stock rom or ur phone is gone die thia happen to me to
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Do you mean as a transition or permanently?
batkbatk said:
Do you mean as a transition or permanently?
Click to expand...
Click to collapse
I tried going back to stock using these instructions:
http://galaxys2root.com/t-mobile-ga...-to-ics-stock-on-t-mobile-galaxy-s2-sgh-t989/
But Odin fails with this message and the phone doesnt boot (only gives samsung/telus splash screen)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T989UVLE1_T989TMBLE1_T989UVLE1_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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> amss.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Download the drivers again.
Are you using a phone from telus? Did you use the telus firmware or the tmobile firmware? You need the telus firmware if you have a telus phone.
Sent from my Nexus 7 using xda app-developers app
gc84245 said:
Are you using a phone from telus? Did you use the telus firmware or the tmobile firmware? You need the telus firmware if you have a telus phone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I think that's probably what was wrong!
I managed to use Odin to flash TWRP 2.4.2, got into the recovery, mounted internal storage, loaded stock KOODO rom from here:
http://someandroidinfo.blogspot.ca/2012/08/cwm-koodo-sgh-t989d-ics-404-stock-rom.html
and flashed it successfully and I wiped the dalvik/cache. The phone now flashes the KOODO sign, the samsung S sign, but never boots into the ROM. Could it be a recovery compatibility problem?
I at least have a recovery I get into and that works well, I don't think there is much of anything else. I want to get back to as stock as possible (without un rooting)
I ran the emergency firmware recovery tool, set my phone into recovery mode and let it run. Then I got a notice where the text was all boxes. I pressed ok and the emergency procedure ended. Any ideas?
Also, there are no folders on my internal storage, just the .android_secure and TWRP folder
PROBLEM SOLVED
I used odin to flash "T989DTLUMC4_T989OYBMC4_T989DTLUMC4_HOME.tar.md5" (stock JB for T989D KOODO)
Everything works with Odin, I get the green "Pass", but when the phone reboots its stuck in the "S samsung galaxy s2 splash screen"
I went into the recovery (which is now stock, not TWRP) and did a wipe and factory reset.
Thanks everyone! XDA rocks.
So, I decided to try out the CM11 Rom because it was looking stable enough to not have many issues. I used Odin 3.7 and installed CWM 6.0.2.3, Wen't to load up the rom and got the Status 7 install aborted, No big deal, I read if I received it that I needed to upgrade to the newest CWM, which is now 6.0.4.3. Not a problem, just need to reboot the phone and download in rom manager. This is where the problem lies, if I try to reboot the phone, I am stuck at the Samsung Galaxy S III screen, have kept it on there for 20+ minutes to make sure it wasn't just a delayed boot. I tried to reload a stock rom and will either get a failure on Odin or failure in CWM. Stuck here in an infinite loop with a semi-bricked phone.
I have the 6.0.4.3 disk image file, If I can find a version to load in with Odin I think I should be able to at least install CM 11, but no matter what else I have tried, nothing has worked, been at the computer all day trying to fix it, can anyone help? Many thanks in advance!!!
Well if I understand correctly, I think you should first check if you can get into Recovery or Download mode. If you can get to Recovery, first try wipe Dalvik +Cache. If that didn't help, flash another Rom AFTER a Factory Reset. Don't forget to wipe Dalvik +Cache before or after.
If you can't get to Recovery but can get Download, then Odin Flash Stock Rom. Root66 is a good Candidate. After that flash latest CWM and then try CM 11.
Perseus71 said:
Well if I understand correctly, I think you should first check if you can get into Recovery or Download mode. If you can get to Recovery, first try wipe Dalvik +Cache. If that didn't help, flash another Rom AFTER a Factory Reset. Don't forget to wipe Dalvik +Cache before or after.
If you can't get to Recovery but can get Download, then Odin Flash Stock Rom. Root66 is a good Candidate. After that flash latest CWM and then try CM 11.
Click to expand...
Click to collapse
Im positive I have done that, but not sure if I flashed cashe and Dalvik each time. I tried to flash root666 on Odin and get a failure, Will try again and share exactly what the error is.
edit: I can do both download and recovery but that is it, no actual boot
Just attempted to run root666 via Odin 3.7 and this is what I get.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDMD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
attempted to flash CM 10.1.3 d2tmo and received the status 7 again, downloading CM 10.0.0 to see if I have better luck
Dabesiv said:
attempted to flash CM 10.1.3 d2tmo and received the status 7 again, downloading CM 10.0.0 to see if I have better luck
Click to expand...
Click to collapse
It won't help. Don't try to Odin again (yet).
What's the model number of your phone, and did you get the 4.3 update prior to this?
Aerowinder said:
It won't help. Don't try to Odin again (yet).
What's the model number of your phone, and did you get the 4.3 update prior to this?
Click to expand...
Click to collapse
yup, did nothing. model number is SGH T-999, I did the 4.3 update roughly 8 hours prior to this which I am sure didn't make things easier.
On the bright side, I just got it working. I took a big risk and removed the assert line off the CM 10.0.0 code and was able to boot in CM. From here I should be good, but thank you guys for trying to help. I hope if anyone else has this issue what I did helps.
Fyi, once you take the full update to 4.3, you cannot flash any previous firmware anymore. Dont try to force it or you'll brick.
IDK how I did it then, but I am now running CM 11 post 4.3 update, with only a small hiccup that got fixed.
Dabesiv said:
IDK how I did it then, but I am now running CM 11 post 4.3 update, with only a small hiccup that got fixed.
Click to expand...
Click to collapse
Do not attempt to Odin anything unless it is 4.3 or you will hard brick. You can still Odin recoveries, but don't try to flash the older firmware or modems.
You can install any ROM you want so long as you remove the asserts from the install script.
While attempting to root my galaxy note 4 I somehow managed to get caught it a boot loop when trying to revert to a rooted stock room please help
Double check the ROM you're trying to flash, if it is the correct one for your device.
Sent from my GT-I9505 using XDA Free mobile app
yilun said:
Double check the ROM you're trying to flash, if it is the correct one for your device.
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Before the boot loop odin failed on me while trying to flash N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5
LeoPRide said:
Before the boot loop odin failed on me while trying to flash N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5
Click to expand...
Click to collapse
Most likely can't flash that unlocked bootloader from a reactivation locked bootloader. What is your current bootloader? Most likely not OB7 because it's blocked to Odin.
Try to restore the last TWRP backup that ran after last update. No current backup, you need to Odin a tar. Maybe Noterized ROM will flash.
If you want to figure out which tar you can flash in Odin, Odin TWRP with no auto reboot and battery/USB pull for 30 seconds when done. Copy your TWRP log to sdcard and read it. Near the bottom it will tell your current bootloader. Flash that tar if you're stuck on boot loop.
I hope you didn't enable the reactivation lock in Settings/Security. That should be disabled prior to Odin flash. There's also an OEM unlock in Odin 3.10 series. You should use that but I'm not saying it bypasses the failure to disable reactivation lock. May have to call Sprint if that happened. It's anybody's guess if they can override that.
Sent from my SM-N910P using Tapatalk
Ive learned in the last 30 hours I have been fighting with rooting my friends 910p. I also have the note 4 910p and failed to realize he had updated to og5 (5.1.1 if I understand correctly.) Well I tried flashing the same way I did my phone using CF auto root and flashing Noterized Stable 3. Didn't even get through auto root and been looking for this boot loop fix since then. Tried flashing stock og5 and it didn't help. Also tried beastmode kernal with twrp. TWRP works fine and once out of about 35 flashes let me make it to android setup. Halfway though, it rebooted into boot loop. I've only tried Hybrid-X rom and a stock og5 .tar and it hasn't work. I'm about to try and figure out which boot loader I am working with (see previous posters statement saying "Most likely can't flash that unlocked boot loader from a reactivation locked boot loader. What is your current boot loader? Most likely not OB7 because it's blocked to Odin.") and try and match a stock file. After that ill be trying Sacs rom and what a previous poster in this page had said. Sounds like we are dealing with the same demon so I will update you if I make any progress with those ideas. Sorry for mispellings and if I dont make sense. I promised him Id have it figured out and im exhausted from up all night and then working. (side note I broke the laptop screen halfway diagnal across, because I somehow got the phone battery between the screen and keyboard hauling it home from work. If you fix your boot loop issue please post how :highfive: :fingers-crossed:
Also I left my friend the backing up process (he came to me wanting this because of mine.) and he only backed up photos, google, and contacts. I've been surfing this forum off and on for years (since my first smart phone Samsung Moment) for the knowledge you guys have that goes with my love of android. Hope to become a helpful active member.
Edit: I just seen a main difference where you failed odin and mine passes. Not sure if that matters.
store2426gm said:
Ive learned in the last 30 hours I have been fighting with rooting my friends 910p. I also have the note 4 910p and failed to realize he had updated to og5 (5.1.1 if I understand correctly.) Well I tried flashing the same way I did my phone using CF auto root and flashing Noterized Stable 3. Didn't even get through auto root and been looking for this boot loop fix since then. Tried flashing stock og5 and it didn't help. Also tried beastmode kernal with twrp. TWRP works fine and once out of about 35 flashes let me make it to android setup. Halfway though, it rebooted into boot loop. I've only tried Hybrid-X rom and a stock og5 .tar and it hasn't work. I'm about to try and figure out which boot loader I am working with (see previous posters statement saying "Most likely can't flash that unlocked boot loader from a reactivation locked boot loader. What is your current boot loader? Most likely not OB7 because it's blocked to Odin.") and try and match a stock file. After that ill be trying Sacs rom and what a previous poster in this page had said. Sounds like we are dealing with the same demon so I will update you if I make any progress with those ideas. Sorry for mispellings and if I dont make sense. I promised him Id have it figured out and im exhausted from up all night and then working. (side note I broke the laptop screen halfway diagnal across, because I somehow got the phone battery between the screen and keyboard hauling it home from work. If you fix your boot loop issue please post how :highfive: :fingers-crossed:
Also I left my friend the backing up process (he came to me wanting this because of mine.) and he only backed up photos, google, and contacts. I've been surfing this forum off and on for years (since my first smart phone Samsung Moment) for the knowledge you guys have that goes with my love of android. Hope to become a helpful active member.
Edit: I just seen a main difference where you failed odin and mine passes. Not sure if that matters.
Click to expand...
Click to collapse
First flash with CFAutoRoot will boot loop due to not using the kernel exploit and SuperSU zip (rooting stock? Just Odin of TWRP and pre-rooted Hybrid X would have been for OG5 stock).
2nd attempt with TWRP and Beastmode should have included the SuperSU zip prior to boot. But I don't think that should cause a boot loop.
If Odin isn't failing but you're getting boot loops, try installing CWM. It seems that if TWRP gets crashed on the reactivation bootloader, it no longer works to recover with a successful flash.
http://downloadandroidrom.com/file/GalaxyNote4/CWM/philz_touch_6.59.0-trlte.tar
I suspect that is the case with both phones in this thread.
Sent from my SM-N910P using Tapatalk
So flash a stock og5 file then reboot and wipe dalv and then use oden to flash cwm. After that flash a custom rom that's og5? This correct? Is there an easier way with having a non loading rom and TWRP on there now? Main thing I feel hurt this root was it was 5.1.1 and I didn't realize that.
Thank you for the fast replies!
store2426gm said:
So flash a stock og5 file then reboot and wipe dalv and then use oden to flash cwm. After that flash a custom rom that's og5? This correct? Is there an easier way with having a non loading rom and TWRP on there now? Main thing I feel hurt this root was it was 5.1.1 and I didn't realize that.
Thank you for the fast replies!
Click to expand...
Click to collapse
You can try just Odin CWM and flash the pre-rooted OG5 ROM. The ROM likely does most of the wiping for you if it's Hybrid X.
That should be enough. If not, format data partition and Odin OG5 tar and CWM then the pre-rooted ROM.
Sent from my SM-N910P using Tapatalk
It went all the way through the installer for the Hybrid 3.0 rom. After reboot it black screens with blue LED fading in and out. CWM worked amazingly!! Should I try and figure out the steps to find what boot loader its stuck on? Maybe it tried to take the 5.0.1 version and it stuck???
Progress baby, progress
store2426gm said:
It went all the way through the installer for the Hybrid 3.0 rom. After reboot it black screens with blue LED fading in and out. CWM worked amazingly!! Should I try and figure out the steps to find what boot loader its stuck on? Maybe it tried to take the 5.0.1 version and it stuck???
Progress baby, progress
Click to expand...
Click to collapse
I'm not familiar with Hybrid X 3.0 The Sprint yellow splash with blinking blue LED was common for many TW OB7 ROMs. IDK, that may been an indication it's installing the deodex ROM prior to optimizing and starting apps which would pop-up a notification screen.
Maybe let it sit 10 minutes or more and see if it updates the status? As long as the blue LED is blinking and phone doesn't vibrate and go off or loop, that may be acceptable if it actually completes the install.
Sent from my SM-N910P using Tapatalk
So while waiting on the black screen and blue led I fell asleep. still didnt work. Re downloading a good og5 tar to try and flash again. Also I am still struggling to figure out how to find which bootloader its on. Would it hurt to try flashing a 5.0.1 rom? Ill be giving him my sphone to use until I get this fixed. Hate to do that because I need my phone but it isnt his fault.
Also I have changed to odin 3.10.7 and it failed last try. It may have been my settings on odin though.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Erase...
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> carrier.img.ext4
<ID:0/004> RTN for Sprint
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
OP, is any of this helping? I dont mean to hijack your thread but figured we could work through it together. Otherwise if you like I can get my own thread going because this is a pain in the butt...... lol
store2426gm said:
So while waiting on the black screen and blue led I fell asleep. still didnt work. Re downloading a good og5 tar to try and flash again. Also I am still struggling to figure out how to find which bootloader its on. Would it hurt to try flashing a 5.0.1 rom? Ill be giving him my sphone to use until I get this fixed. Hate to do that because I need my phone but it isnt his fault.
Also I have changed to odin 3.10.7 and it failed last try. It may have been my settings on odin though.
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Erase...
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
persist.img.ext4
modem.bin
cache.img.ext4
carrier.img.ext4
RTN for Sprint
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
OP, is any of this helping? I dont mean to hijack your thread but figured we could work through it together. Otherwise if you like I can get my own thread going because this is a pain in the butt...... lol
Click to expand...
Click to collapse
Did you have the OEM unlock checked in Odin options? Was this OG5 tar?
Try to Odin the stock kernel first. Then try to recover with KIES. Odin or KIES might work after flashing the kernel, modem and recovery separately. It's risky doing it with OB7 individual Odin flashes but I believe it was done successfully on an OE1 update that crashed the reactivation locked bootloader. The gap may have been plugged on OG5.
IDK if CWM has a log like TWRP does. I can see the partitions by version in TWRP log written to sdcard.
You may also try just flashing an OG5 ROM or Noterized.
Edit: I no longer see OEM unlock in Odin 3.10.7; not sure which version had that or just bad recall; sorry for the bad info.
Sent from my SM-N910P using Tapatalk
So this is the stock file I been flashing.
ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB5691107_REV00_user_low_ship_MULTI_CERT.tar
Is that correct? I am not sure what modem or anything from before. I know it was the 5.1.1 and he updated earlier Aug. Is there a way to find out? Also I am still able to access and install twrp or cwm, use odin to flash tar files so I am not completely screwed yet. I am not used to using kies but wonder if I should get used to it quickly.
In 3.10.7 that failed (see post earlier), I had Nand erase, ??? for sprint, and f. reset time checked. The time it failed was the first time I seen a message on the phone saying to "use kies or recovery to fix a firmware issue."
Wasnt there some roms that requires it be pushed through odin?
I just tried the noterized stable 3 build (older version thats on my phone) and flashed stock tar and cwm, then tried stock tar and twrp. Never worked. Just starts spark screen then goes black with blue led slowly flashing. Also when trying to flash a rom through recovery it would start install then juat power off. Did this on 2 diff roms.
Ughhh so far away from getting this done i feel.
Somwtimes i see a message saying "skipping md5 check. No md5 file" or something along those lines.
Sent from my SM-N910P using XDA Free mobile app
store2426gm said:
Wasnt there some roms that requires it be pushed through odin?
I just tried the noterized stable 3 build (older version thats on my phone) and flashed stock tar and cwm, then tried stock tar and twrp. Never worked. Just starts spark screen then goes black with blue led slowly flashing. Also when trying to flash a rom through recovery it would start install then juat power off. Did this on 2 diff roms.
Ughhh so far away from getting this done i feel.
Somwtimes i see a message saying "skipping md5 check. No md5 file" or something along those lines.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
If developer doesn't include md5, the setting should be do not check md5 or something similar. Most do not include md5 from my experience on Note 4.
I thought you had established some success with CWM recovery. It usually works where TWRP fails.
I don't think it's necessary to flash a ROM prior to Odin of stock tar. I think I'd be wiping everything but sdcard plus data partition format or factory reset and powering down prior to Odin if it was boot looping. Did you try the stock recovery factory reset?
Sent from my SM-N910P using Tapatalk
I have done all that except the stock recovery factory reset. Trying that now. I have tried over and over variationd of using odin for stock tar then either superbeast, then a cwm or twrp, then try just that or then try to put a rom on. Twrp logs havnt helped other than seeing some "unable mount /data " just figured it was the rom due to trying to get root. Idk...
What could have possibly happened using auto root on a 5.1.1? It will sit ob spark screen for 5 min then just shut off. Other trys have gotten me to a boot loop 10 sec into booting...
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 02:00 AM ---------- Previous post was at 01:57 AM ----------
Also i have wiped everything including sd. Ive done this several ways too.
Its like it tries then half way during whatever its doing it just locks up then shuts off. Kinda like a random reboot but leads to boot loop..
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
Im re flashing stock tar now then when it goes dark during spark screen ill give it a few and batt drip. Then recovery and factory reset and let you know.
Sent from my SM-N910P using XDA Free mobile app
Anyone know how i flash these? I just need to get this phone working. Stock, rooted, doesnt matter..
Sent from my SM-N910P using XDA Free mobile app
So the latest is flashed stock tar, factory reset with recovery, then flashed stock tar again. Got all the way to optimizing apps 3 of xxx and shut off. Just powered off. Not sure why. Going to wipe dalv and reboot. May just load cwm and a rom to see what happens.
Sent from my SM-N910P using XDA Free mobile app
Here are a few pics to show what i am seeing. It made it to optimizing app 2 of 25 then just shuts off.
Sent from my SM-N910P using XDA Free mobile app
Got it! Had to format sd card twice. Then flash tar (no reboot), flash cwm and factory resets, then flash tar with reboot on this time. It is now a stock note 4 again and working. He wont let me try the 5.1.1 root method now that i know the new steps. Lol
Thanks for all the help! Hope to return the favor and pass along the info someday!
Sent from my SM-N910P using XDA Free mobile app