Is there a trick to getting the Epic EI22 Stock GB rooted?
Trying to root my wife's phone, because she's complaining of poor battery life.
I'm on a rooted Epic Touch, so I don't know the nuances of the EPIC 4G.
I tried to flash kernel-GB-3a.tar.md5 using odin 1.81 and it was on com4, successfully verified the checksum and tried to flash something, but failed to verify.
reference: http://forum.xda-developers.com/showthread.php?t=1307980
Has something changed recently with EI22 that makes it harder to root? I guess the oneclick method no longer works?
Has anyone successfully rooted from EI22 stock?
A little forum search in General will show you a "how to root the OTA or Google update". It requires a custom kernel like samurai, nubernel or shadowkernel. You can also simply Odin in CWM 5.0.2.7 without reboot checked. Remove from Odin, boot directly into CWM and flash a custom prerooted GB ROM.
Sent from my SPH-D700 using XDA App
Thanks kenny,
found it: http://forum.xda-developers.com/showthread.php?t=1339478
QBKing77 Videos are the greatest for info and how to's
trying to root, getting the following ODIN warning:
using: kernel-GB-3a.tar.md5 and ODIN 1.85 to flash, "auto-reboot" checked, F. Rest Time unchecked.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> kernel-GB-3a.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the box on the Upper Left says FAIL!, right above ID:COM :[com3]
badkarmah187 said:
trying to root, getting the following ODIN warning:
using: kernel-GB-3a.tar.md5 and ODIN 1.85 to flash, "auto-reboot" checked, F. Rest Time unchecked.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> kernel-GB-3a.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the box on the Upper Left says FAIL!, right above ID:COM :[com3]
Click to expand...
Click to collapse
Cable is probably going bad. Try it again without the battery in and using the computer and USB cords as power to get into download mode.
badkarmah187 said:
trying to root, getting the following ODIN warning:
using: kernel-GB-3a.tar.md5 and ODIN 1.85 to flash, "auto-reboot" checked, F. Rest Time unchecked.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> kernel-GB-3a.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the box on the Upper Left says FAIL!, right above ID:COM :[com3]
Click to expand...
Click to collapse
That's happened to me before. You either need to unplug and replug the USB cable or you need to unplug, reboot into download mode, and then replug in the USB cable. I can't remember which one was the fix and which one just annoyed me more.
OK, shortly after I posted the error message I soft bricked my phone. Probably a bad factory cable.
I used this post to Restore it back to Froyo,
[How to] Restore a semi-bricked Epic or Bring it back from the brink!: http://forum.xda-developers.com/showthread.php?t=1052813
Another words, I flashed to following:
victory_8G_100528.pit and SPH-D700-EC05-8Gb-REL.tar
I also used a non stock cable!
After this I was able to Flash ACSRecovery1.0.0.5.tar.md5, and than CleanGB.
I think the Baseband went back to EC05, should I flash the EI22 modem? (if there is one available)
There is no EI22 modem.bin file. There is a flashable delta for EC05toEI22 in the modems thread in the stickies in Development. I have found the modem works well.
Sent from my SPH-D700 using XDA App
Related
I have been trying to fix my soft bricked Galaxy S3 for a couple of days and nearly tearing my hair out at this point...
Ok I installed a nightly and yep came up dirty. So I needed to restore it. Any help would be fantastic
So far I have tried 2 different computers, two different USB cables, all the different ports on each computer.
I have tried every Odin version and nothing seems to help. I have tried restoring the latest Samsung updates (back to stock) and a root ROM....nothing. Is there a way that I can reset the binary counter since I believe this to be the problem? i know I can download triangle away from the Google Play store but how do I put it in the phone that is soft bricked? I can put it in Recovery Mode or Download Mode but as you see fixing it with Odin has proved illusive.
The farthest I have gotten is this:
In Odin 3.04
<ID:0/003> 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/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
For the the Samsung stock I only get as far as "leave the cs" then when I wipe the data/cache and reboot I get that dreadful Samsung logo and it stays that way for hours.
Help???
Thanks!
the.seeker said:
I have been trying to fix my soft bricked Galaxy S3 for a couple of days and nearly tearing my hair out at this point...
Ok I installed a nightly and yep came up dirty. So I needed to restore it. Any help would be fantastic
So far I have tried 2 different computers, two different USB cables, all the different ports on each computer.
I have tried every Odin version and nothing seems to help. I have tried restoring the latest Samsung updates (back to stock) and a root ROM....nothing. Is there a way that I can reset the binary counter since I believe this to be the problem? i know I can download triangle away from the Google Play store but how do I put it in the phone that is soft bricked? I can put it in Recovery Mode or Download Mode but as you see fixing it with Odin has proved illusive.
The farthest I have gotten is this:
In Odin 3.04
<ID:0/003> 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/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
For the the Samsung stock I only get as far as "leave the cs" then when I wipe the data/cache and reboot I get that dreadful Samsung logo and it stays that way for hours.
Help???
Thanks!
Click to expand...
Click to collapse
this is why you should have a nandroid. try fully wiping and restart. if that doesn't work try to use a different odin and make sure you downloaded the correct firmware.
You posted this already in an existing thread maybe 15mins ago and I answered a few min ago. No need to double post. Just be patient. It can sometimes take a few hours or more before someone who knows how to help will come on and answer. Especially later in the evening during the week.
Sent from my SGH-T999L using xda premium
Hi Every body:
That is really a bad day, just woke up this morning to find my device (was plugged for charging over night) to find it stuck at (GALAXY NOTE II N-7100)
tried several times to pull the battery and put it back hopefully to get it boot...but nothing happened.
I can access only the download mood and NO access to the custom recovery!!
I was running Android 4.1.1 WITH ROOT!
As advised in many other posts, tried to update to 4.1.2 using odin but the whole process failed with the following log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMC3_N7100OJVDMC1_N7100XXDLK7_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas and suggestions will be really appreciated.
Samsung maintenance in my place may take forever to get it fixed (almost 2 weeks!!)
Use odin 1.85 , check samsung usb drivers installed , exit kies, disable antivirus and firewall and try..
"<ID:0/004> Can't open the serial(COM) port." And try another usb port.
" Android 4.1.1" ?... Be careful about sudden death...
Primokorn said:
"<ID:0/004> Can't open the serial(COM) port." And try another usb port.
" Android 4.1.1" ?... Be careful about sudden death...
Click to expand...
Click to collapse
Thanks for the reply, really appreciate it..
I changed the USB port and got the following log from odin:
<OSM> N7100XXDMC3_N7100OJVDMC1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?
drsayed_958 said:
Any ideas?
Click to expand...
Click to collapse
Did u try another Odin version? 1.85 or 3.04
Primokorn said:
Did u try another Odin version? 1.85 or 3.04
Click to expand...
Click to collapse
Tried both, got the same result.:crying:
You can flash with pit in Odin, it should work. The pit file can be found around here somewhere, can't find it for you right now.
Sent from my GT-N7100 using Tapatalk 2
http://forum.xda-developers.com/showpost.php?p=32273406
Not sure that it solves your issue.
same problem can anyone help ? no pit partition , or Can't open the serial(COM) port. , all drivers are installed i installed kies for driver the uninstalled without drivers
Ok, I got a new Note II the other day with 4.3 already installed via Kies or OTA. I attempted to push, via ODIN, "CF-Auto-Root-d2tmo-d2tmo-sght999.tar". I REALIZE THIS IS THE ROOT FOR S3; I KNOW I FLASHED THE WRONG FILE. PLEASE DO NOT POST SAYING I FLASHED THE WRONG FILE. I KNOW I SCREWED UP BIG TIME, AND I'M HOPING SOMEONE IS NICE ENOUGH TO TRY AND HELP ME THROUGH THIS. My laptop sat there for the better part of 2 hours acting like ODIN was cranking along but the bar never moved. After 2 hours, I had to pull the cord from the phone (stupid move, I know!), and this is, of course, where the problem began.
Now, I get the coveted "Firmware Upgrade encountered an issue. Please select recovery mode in Kies & try again." screen. The phone will, obviously, go no further than this in booting up. I am able to get to download mode.
I attempted to install JellyBean Release 4.3 (December 2013) from this thread to alleviate the issue. Here's the ODIN result:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T889UVUCMK7_2.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> cache.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Now, as I sit here and write this, I think installing a stock firmware like this one might not work at all. I need to install a recovery (stock or otherwise) to make this problem disappear. I tried to reinstall the CF-Auto-Root file and got this result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-d2tmo-d2tmo-sght999.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-d2tmo-d2tmo-sght999.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..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Again, it didn't do anything for hours. I pulled the cord again since it didn't look like it was actually writing anything to my phone.
I don't think I can use KIES as a last resort since I never backed up the phone through KIES before. I am out of ideas, and I would really like to get this phone operational again. Also, the serial number has been removed from the device (Igot the phone from Ebay), so I don't think I could use this route either.
Any and all help would be greatly appreciated.
Thanks in advance!
Download and flash CF auto-root for sgh-t889(link below)it includes recovery, then perform factory reset by rebooting in to recovery.
http://download.chainfire.eu/266/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltetmo-t0ltetmo-sght889.zip
Sent from my SGH-T889 using xda app-developers app
My phone just boots to the "Saumsung Galaxy Note II" screen and it is stuck there. I dont think its a loop because it doesnt loop (by that I mean it doesnt disappear and appear).
I m afraid using odin would erase everything.
I want to save my data, what should I do? Which rom do i use?
I tried downloading 3 to 4 note 2 roms but they all failed in odin.
Please specify what I need to download in order to save my data.
At this point, I am also ready to just give up and restore factory settings. I went to the at&t technicans, who are completely useless and they used their roms and couldnt help at all. I went to a fix phone place and they couldnt do anything either.
Please help!
Your request is ambiguous at best.
.
We have absolutely no idea what you have done beyond flashing multiple roms to the device..
I assume the device is dirty due too multiple frameworks being flashed over one another..
If it were my device...I'd go clean slate and restore the device to a stock configuration and work up from there.
.
It's a mess in there for sure.
So see the return to stock thread in the general section...and use Odin if possible....and IMHO...stay away from kies....g
i have no idea either. for all i know, none of them did anything since they all failed after this boot freeze has been happening.
im trying to go clean slate but i cant even do that.
im trying to odin with http://www.sammobile.com/firmwares/confirm/13212/I317UCAMA4_I317ATTAMA4_ATT/
but it doesnt work either!!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user _low_ship.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
downloaded both roms and both failed again
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This morning I flashed Lineage 14.1 and there were no errors. But it got stuck at the Samsung logo during reboot. I waited about 15 minutes. I could not figure out how to fix it so I decided to flash the stock firmware using Odin. It passed but also got stuck at the same screen during reboot. Then I did a hard system recovery but still could not boot past the Samsung logo. After that I install Samsung Kies 3, but it said the phone is no longer supported. Then I tried Kies 2.6 but it said the phone SGH-M919 does not support initialization. Now I can't get to the system recovery screen anymore. It would say there is an issue with the firmware update and try again in Kies. I cannot flash the stock firmware in Odin anymore either. It would fail with a complete write error. I don't know what else to try. Please help me.
Did you confirm the phone's model # in download mode?
You tried different USB cables, different USB ports, and different versions of Odin?
What was the exact Odin error?
Yes, the model is correct SGH-M919. I've tried Odin 3.0.7 and 3.10.6. I used Odin 3.0.7 to root and install TWRP recovery using the same original Samsung USB cable. So the cable and port should be OK. I tried it again this morning and noticed it took a long time after the message "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried it again using a different USB port and this time it failed right away. I didn't see the line "Get PIT for mapping" this time. Here are the messages in Odin.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I was using the USB ports at the front of the PC and none of them worked. I tried one port at the back and it worked. Thank you very much. I never thought this would make a difference because I use the ports in the front all the time with my other iPhones, iPads, USB memory sticks and never had a problem. I lost all my data on the phone but that's OK. I would not dare to install custom ROM again. It looked so easy in youtube videos. Thanks again.
Glad you got it working. I always use the ports at the back of my desktop because I find it more reliable than the front case ports.