Hi everyone,
Just wanted to give you a few details before I get into where I'm at now.
I decided for the first time to root and flash CM11 on my Samsung Galaxy S4 and everything went flawlessly so I wanted to try it on my S3 T999. I had a lot of trouble this time around every step of the way. I tried using CM's installer that they have but every time I would switch the USB mode from MTP to PTP using the CM OneClick app, my phone would no longer get recognized AT ALL through my computer, so I factory reset it through Samsung's settings and decided to just do it using ODIN and a guide here help me along.
So I started over and followed http://forum.xda-developers.com/showthread.php?t=2563955 this guide. Downloaded ODIN, I downloaded TWRP v2.5.0.0 because it states the dt2mo users might have problems with 2.6+. Followed the rest of the guide, everything went well. Then I downloaded cm-11-20140210-SNAPSHOT-M3-d2tmo.zip and Gapps for CM 11.
Currently:
Booted into recovery, backed up to my SD card, did a factory reset, then went to install the above snapshot. It failed saying error executing updater binary in zip. I tried to restore my backup I just made and rebooted and it just sits at the Samsung logo. Not sure where to go from here. Someone in another thread mentioned to flash the latest twrp using ODIN but I tried to connect to ODIN when in download mode and the S3 doesn't get recognized.
EDIT: Two more things. I did an Advanced Wipe once. Dalvik Cache, System, Data, and Cache. And After failing to flash, when I try to reboot, TWRP states I lost root and asking if I wanted it back...
follow the instructions in this thread and flash the root 66(pre-rooted firmware) firmware for your T999:
http://forum.xda-developers.com/showthread.php?t=1949687
T999_UVUEMJC
Official JB Firmware - Latest JB 4.3 Firmware
Cobra281 said:
follow the instructions in this thread and flash the root 66(pre-rooted firmware) firmware for your T999:
http://forum.xda-developers.com/showthread.php?t=1949687
T999_UVUEMJC
Official JB Firmware - Latest JB 4.3 Firmware
Click to expand...
Click to collapse
I'm currently downloading root 66 for T999 but I have tried to connect through ODIN before and it is no longer recognizing my phone. Nothing happens. I had this problem all day yesterday after messing with the usb connections that I mentioned in my first post.
EDIT!:
It seems as though already having connected the phone to the computer and THEN booting into download mode recognized the phone and started downloading the drivers.
3itmn said:
I'm currently downloading root 66 for T999 but I have tried to connect through ODIN before and it is no longer recognizing my phone. Nothing happens. I had this problem all day yesterday after messing with the usb connections that I mentioned in my first post.
EDIT!:
It seems as though already having connected the phone to the computer and THEN booting into download mode recognized the phone and started downloading the drivers.
Click to expand...
Click to collapse
also i presume that you're using the stock\original Samsung USB cable that came with the S3?
Cobra281 said:
also i presume that you're using the stock\original Samsung USB cable that came with the S3?
Click to expand...
Click to collapse
Thank you for linking me to that firmware! That worked, I'm back up and running 4.3. I would still like to be able to flash CM11 but I don't know what I did wrong. Should I have went with the latest TWRP or used something else?
3itmn said:
Thank you for linking me to that firmware! That worked, I'm back up and running 4.3. I would still like to be able to flash CM11 but I don't know what I did wrong. Should I have went with the latest TWRP or used something else?
Click to expand...
Click to collapse
not a problem. personally, i like TWRP, especially since it installs automatically when you download the GooManager app
Related
edit: on a whim I looked at the heimdall command line options and saw "close pc screen" as one of the arguments and tried that and it booted up perfectly!!!!! So relieved it was something that simple!
I got my S4 last night and immediately tried to root it after I got it, I read up on some stuff (not new to rooting, I've rooted multiple devices in the past) and attempted to flash TWRP via Odin but then it said it failed for some reason, I tried again and it failed. I figured everything was fine until I rebooted and got "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again." I tried to connect it to my old Windows XP pc (my main pc runs Arch Linux) and kies kept saying "connecting" no matter how many times I tried to make it connect or reinstall the drivers.
I can get to download mode and I'm trying to flash the stock firmware via heimdall but it's taking forever to uncompress the image. I got the images from here: http://forum.xda-developers.com/showthread.php?t=2258628
I tried to flash cf-autoroot with heimdall in hopes that it would restore my bootloader but it wouldn't flash because it said it was missing an XML file.
I think I'm just missing the bootloader/recovery image but I'm not sure. Am I heading in the right direction?
If you have root and still have access to the phone when u turn it on flash cwm recovery via Odin or if Ur phone turns on nd have root then download goomanager nd you can install twrp with that app with no problems
Sent from my SGH-M919 using xda premium
im having the same issue...
i am flashing Modem_UVUAMDL.tar and philz touch 5.08.5-jfltetmo as recovery, OUDHS jfltetmo also, but nothing is working
i was running infamous 4.0 ROM, flashed the cyanogenmod nightly and somehow everything exploded and now the only thing on my screen is the SGS4 stock image... it wont boot into recovery mode only download.
i am on an OSX using heimdall and i do not ever have access to a PC!
icecreamwithyou said:
im having the same issue...
i am flashing Modem_UVUAMDL.tar and philz touch 5.08.5-jfltetmo as recovery, OUDHS jfltetmo also, but nothing is working
i was running infamous 4.0 ROM, flashed the cyanogenmod nightly and somehow everything exploded and now the only thing on my screen is the SGS4 stock image... it wont boot into recovery mode only download.
i am on an OSX using heimdall and i do not ever have access to a PC!
Click to expand...
Click to collapse
Did you find a fix I have the same issue but I do have a pc?
brando56894 said:
edit: on a whim I looked at the heimdall command line options and saw "close pc screen" as one of the arguments and tried that and it booted up perfectly!!!!! So relieved it was something that simple!
I got my S4 last night and immediately tried to root it after I got it, I read up on some stuff (not new to rooting, I've rooted multiple devices in the past) and attempted to flash TWRP via Odin but then it said it failed for some reason, I tried again and it failed. I figured everything was fine until I rebooted and got "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again." I tried to connect it to my old Windows XP pc (my main pc runs Arch Linux) and kies kept saying "connecting" no matter how many times I tried to make it connect or reinstall the drivers.
I can get to download mode and I'm trying to flash the stock firmware via heimdall but it's taking forever to uncompress the image. I got the images from here: http://forum.xda-developers.com/showthread.php?t=2258628
I tried to flash cf-autoroot with heimdall in hopes that it would restore my bootloader but it wouldn't flash because it said it was missing an XML file.
I think I'm just missing the bootloader/recovery image but I'm not sure. Am I heading in the right direction?
Click to expand...
Click to collapse
I just recently purchased a rooted S4 and I downloaded a ROM from this site that wasn't compatible with my S4 and flashed it (BIG mistake I know now). So now I can't start up my phone. I read here that I should wipe out the divalk cache/cache and restart (didn't work). Reset to factory settings and reboot (didn't work). Download the TWRP flashable zip and flash it from the Recovery memory then reboot (didn't work). Now I'm really worried. Can you please help me?
Warrior1016 said:
I just recently purchased a rooted S4 and I downloaded a ROM from this site that wasn't compatible with my S4 and flashed it (BIG mistake I know now). So now I can't start up my phone. I read here that I should wipe out the divalk cache/cache and restart (didn't work). Reset to factory settings and reboot (didn't work). Download the TWRP flashable zip and flash it from the Recovery memory then reboot (didn't work). Now I'm really worried. Can you please help me?
Click to expand...
Click to collapse
What does it do when you boot up?
I tried to update my samasung s3 and after I did it will only boot to recovery. I tried to us ODIN but everytime it just goes to failed. I have used the pda and it just errors out. I also tried to mount it in revocery and that fails. ODIN shows it connected when I enter download mode. I think parmissions is messed up too but I don't know. Thanks
cool_kyle_3000 said:
I tried to update my samasung s3 and after I did it will only boot to recovery. I tried to us ODIN but everytime it just goes to failed. I have used the pda and it just errors out. I also tried to mount it in revocery and that fails. ODIN shows it connected when I enter download mode. I think parmissions is messed up too but I don't know. Thanks
Click to expand...
Click to collapse
More details, what did you try to update to? Did you update to 4.3 prior to this problem?
yes i was on the lastest att software then went to update and now it won't boot past recovery mode. I have rooted and done custom roms in the past no problem. At this time of updating phone was bone stock with no root. I was trying to upgrade to Android 4.4 KitKat but didn't know there were different models of the S3 so I tried to install from sd card the incorrect rom. Tried the correct rom and still got an error.
I followed this tutorial http://true-android.blogspot.com/2013/12/android-442-kitkat-slimkat-rom-for-at.html but selected the wrong phone the i9300 and tried to install the wrong kitkat. Then I found the link above for the att S3 and followed it and still got an error. I feel the error is from trying to install the wrong rom a couple of times. Not it WILL NOT load past clockwork recovery
By updating to stock AT&T ROM, it would have loaded the latest bootloader onto your phone. You can't use desktop Odin to revert to stock as AT&T never released a complete stock 4.3 ROM.
Do you have the latest CWM or TWRP on your phone? If you do, you could try and do a full wipe and install a custom ROM.
My phone was 100% screwed. There was NO saving it. I did EVERYTHING that I could. So I just took it back to BestBuy and they said phone is no good and agreed to give me a new one. Just waiting on it to come in the mail.
Ok so today I tried to flash TWRP on my Note II today through the GooManager app from the Play Store, it went well and then asked to reboot. After the reboot it is stuck on the SAMSUNG Galaxy Note II screen in all white, with a black background. I know I should try to flash the stock firmware with Odin but when in download mode (which it can enter but not the Recovery or OS) it is not detected. I have tried on a Windows XP, Vista and 7 computer with no luck on each. I have downloaded Heimdall for my Mac and again it is not detected. I have read that there could be an eMMC problem or something like that but I was working just fine like two minutes ago. Again it will not boot into either the Recovery or OS after sitting there for minutes, I can upload a photo if need be but I dont think its that hard to imagine. Oh I was on OmniRom the release the one before the one released yesterday with CWM. I wanted to update but since i was on CWM i needed to flash TWRP and it was not downloading for whatever reason so i went with the app method, which has worked before on my Xperia X10 so i was semi confident, anyway I'm rambling now... Again if anyone would be able o help me I will buy you a beer! wait I can't I'm underage, well when I turn 21 I'll buy you a beer!
Thanks!
Yoshi5005 said:
Ok so today I tried to flash TWRP on my Note II today through the GooManager app from the Play Store, it went well and then asked to reboot. After the reboot it is stuck on the SAMSUNG Galaxy Note II screen in all white, with a black background. I know I should try to flash the stock firmware with Odin but when in download mode (which it can enter but not the Recovery or OS) it is not detected. I have tried on a Windows XP, Vista and 7 computer with no luck on each. I have downloaded Heimdall for my Mac and again it is not detected. I have read that there could be an eMMC problem or something like that but I was working just fine like two minutes ago. Again it will not boot into either the Recovery or OS after sitting there for minutes, I can upload a photo if need be but I dont think its that hard to imagine. Oh I was on OmniRom the release the one before the one released yesterday with CWM. I wanted to update but since i was on CWM i needed to flash TWRP and it was not downloading for whatever reason so i went with the app method, which has worked before on my Xperia X10 so i was semi confident, anyway I'm rambling now... Again if anyone would be able o help me I will buy you a beer! wait I can't I'm underage, well when I turn 21 I'll buy you a beer!
Thanks!
Click to expand...
Click to collapse
Your phone was on OMNI ROM with CWM recovery, you installed TWRP via goo manager and since then it's not booting up, right ?
I think the easiest option now is to flash stock via ODIN. Did you ever connect your phone using USB ?
Are you trying with the cable that came along with this phone ? I know samsung drivers can get messy, try installing KIES it will automatically install the appropriate drivers, then exit KIES and start odin with Admin right(right click-> Run as Administrator).
If you have a full back-up and if Odin works try flashing CWM first via ODIN and the reboot in to recovery and restore your backup.
ciphercodes said:
Your phone was on OMNI ROM with CWM recovery, you installed TWRP via goo manager and since then it's not booting up, right ?
I think the easiest option now is to flash stock via ODIN. Did you ever connect your phone using USB ?
Are you trying with the cable that came along with this phone ? I know samsung drivers can get messy, try installing KIES it will automatically install the appropriate drivers, then exit KIES and start odin with Admin right(right click-> Run as Administrator).
If you have a full back-up and if Odin works try flashing CWM first via ODIN and the reboot in to recovery and restore your backup.
Click to expand...
Click to collapse
I tried installing Kies, closing it with Task Manager and then using both Odin v3.07 and v1.8.5. With both they never detected my phone, and in Heimdall it still does not recognize my phone. And yes that is exactly what happened.
Oh and Windows finally said something and it said that the usb device connected cannot be recognized...
Sorry fixed it!
Yeah so... The USB cable I was using was broken or whatever so I changed it and yeah its detected, thanks anyway!
Glad to know it's fixed.
Sent from my SGH-T889 using xda app-developers app
I flashed Slimkat 4.4.4 a couple weeks ago and don't like it so I attempted to change it to AOSP tonight and I wiped the cache, partition, formatted the system and attempted to flash the rom and got a "fail" sign. Now when I reboot from TWRP menu, it keeps going back into TWRP recovery, after I see the Samsung and Slimkat words on my phone. I tried rebooting into system, keeps going back into recovery. I was going to attempt to reflash Slimkat but now my laptop won't recognize my phone. I saw where someone pulled the battery out and it just booted into recovery. Please help me and thank you in advance.
This is why you should never manually format your /system partition. If your rom flash fails, you have no OS to boot into. I really dont know why so many people still say to do this.
You need to either use Odin to flash your firmware, or download another rom (or your previous one) and flash it from TWRP. Youll have to plug your external SD Card into your computer and copy it to there, then put the card back in and flash.
DocHoliday77 said:
This is why you should never manually format your /system partition. If your rom flash fails, you have no OS to boot into. I really dont know why so many people still say to do this.
You need to either use Odin to flash your firmware, or download another rom (or your previous one) and flash it from TWRP. Youll have to plug your external SD Card into your computer and copy it to there, then put the card back in and flash.
Click to expand...
Click to collapse
Lesson learned. I really don't know who to listen to, I should have just left it alone like a good girl. But I really did not like Slimkat. :laugh: My laptop is not recognizing my phone through usb. Would Odin recognize it if I put it in download mode?
Its worth a try I think. But otherwise do you have a way to plug your sd card into the computer? You could copy a rom to flash im recovery that way.
If not youll probably need to try installing different drivers. You can get plenty to try from the link in my sig.
I usually say to just follow the instructions in the OP of what you are trying to flash. If they tell you to format system, I would ignore that part unless they have a good explanation for why.
DocHoliday77 said:
Its worth a try I think. But otherwise do you have a way to plug your sd card into the computer? You could copy a rom to flash im recovery that way.
If not youll probably need to try installing different drivers. You can get plenty to try from the link in my sig.
I usually say to just follow the instructions in the OP of what you are trying to flash. If they tell you to format system, I would ignore that part unless they have a good explanation for why.
Click to expand...
Click to collapse
I'm guessing the only other way to plug an sd card into my computer is to stick the card in another phone? Meanwhile I will try to install drivers and get my computer to recognize my phone.
You can usually find an adapter for a few bucks online or at places like wal mart. Sorry. Was just assuming you had one. Without it, yes youll have to try different drivers or find another way to get it going via one of the two methods I mentioned.
When trying different drivers, just installing the package doesn't always do the job. You should go into device manager and manually select update drivers, then browse to the folder in Program Files and choose it there.
When you plug in now, does it at least detect it? Are you trying while in Download Mode?
DocHoliday77 said:
You can usually find an adapter for a few bucks online or at places like wal mart. Sorry. Was just assuming you had one. Without it, yes youll have to try different drivers or find another way to get it going via one of the two methods I mentioned.
When trying different drivers, just installing the package doesn't always do the job. You should go into device manager and manually select update drivers, then browse to the folder in Program Files and choose it there.
When you plug in now, does it at least detect it? Are you trying while in Download Mode?
Click to expand...
Click to collapse
I tried putting my SD card into my daughters phone which is a Samsung but different model and I thought I put the old Slimkat rom what looked to be the extsdcard folder but when I went to recovery to install the rom I saw the corrupt rom I attempted to install last night. When I went to device manager to manually update the drivers, the computer recognizes my phone but said that the drivers couldn't be installed. Maybe I'm getting confused with this TWRP recovery I'm not familiar with. It has an install feature, so I tried to flash the rom last night using that. Did I screw up?
Ok....I finally managed to get the files onto my SD card. I attempted to install the Slim rom (the one that's been on my phone the last couple weeks) and heres the message I get:
Format and Mount System, Mount Data.....
Symlinks and permissions....
set_metadata-recursive: some changes failed
E:Error executing updater binary in zip ' /extern
Error flashing zip '/external_sd/Slim-d2lte-4.4.
Updating partition details....
FAILED
What version of TWRP are you using? You could try flashing CWM or Philz recoveries and try the rom again. If you still get flashing errors you may have to find a way to get Odin to work.
Try uninstalling drivers from device manager. Then with the phone unplugged, reinstall the driver package. Plug phone back in and hopefully itll automatically install the drivers and work.
And have you tried connecting while booted to Download Mode?
DocHoliday77 said:
What version of TWRP are you using? You could try flashing CWM or Philz recoveries and try the rom again. If you still get flashing errors you may have to find a way to get Odin to work.
Try uninstalling drivers from device manager. Then with the phone unplugged, reinstall the driver package. Plug phone back in and hopefully itll automatically install the drivers and work.
And have you tried connecting while booted to Download Mode?
Click to expand...
Click to collapse
I'm using TWRP 2.6.3.0. Ok friggin awesome...I rebooted it into download mode and the computer recognizes my phone.
You might need an updated recovery to flash that rom. Latest TWRP is 2.7.1.0.
But since you can connect in Download Mode you can flash your firmware via Odin...hopefully.
If you have the I747, it depends on if you have ever updated via ota. If so, do you remember if you had updated to 4.3 or 4.4.2?
DocHoliday77 said:
You might need an updated recovery to flash that rom. Latest TWRP is 2.7.1.0.
But since you can connect in Download Mode you can flash your firmware via Odin...hopefully.
If you have the I747, it depends on if you have ever updated via ota. If so, do you remember if you had updated to 4.3 or 4.4.2?
Click to expand...
Click to collapse
I have the i747. I've never been able to do an OTA update, I heard because it was rooted. When I tried to unroot it, I still wasn't able to do an OTA update. I'm going to try to update the recovery first and then the rom. Which rom do you use? The main reason I don't like SlimKat is because of the Google search bar on the home screen and all the extra crap on the lockscreen I couldn't get rid of.
Update: I flashed the latest TWRP and it still bootlooped. So I flashed CWM instead and it booted right back into CWM recovery.
I have a T999 and I only use Touchwiz roms. Personal preference.
When you are in Download Mode, if you do not see a Warranty Bit, youll be free to flash any firmware you want with Odin. You can download it at http://sammobile.com/firmwares
DocHoliday77 said:
I have a T999 and I only use Touchwiz roms. Personal preference.
When you are in Download Mode, if you do not see a Warranty Bit, youll be free to flash any firmware you want with Odin. You can download it at http://sammobile.com/firmwares
Click to expand...
Click to collapse
Doc, Thank you so much for helping me. I flashed the slimkat rom in cwm recovery and its fine now. However I don't want Slimkat and I was eyeing Touchwiz. Someone was saying how great a rom it is so I'm going to try that shortly. No more TWRP for me. I'm comfortable with CWM. Thanks again. :victory:
I have a Samsung Galaxy S3 AT&T and for about a year and a half always wanted to root it but had no idea how. I had an iPhone a while back and used to jailbreak it I became an expert at it. Rooting is not so easy compared at least with the problems I've been experiencing
I started by watching hundreds of root videos and ended up rooting it with Odin and Kit Kat tar file im not sure of the specific file but I'm almost 100% it was my version 4.4.2 that I flashed.
After I did this I downloaded the basics and tried to get TWRP but gooManager wasnt working for some reason.
I tried to flash the Cyanongen 11 onto my phone using the installer for the comp and on google play store and it worked up until the end I got the dead droid symbol for a bit and it finished downloading to show the "ROM may flash stock recover on boot. Fix?" error message and I selected no and "Root Access Possibly Lost Fix?" I also selected no. My phone booted with no custom rom still rooted and most of my apps are unresponsive and close randomly except facebook and youtube.
I decided I wanted to return it to stock rom and try again but when I downloaded the stock tar file and tried to flash it I got this
I'm not sure what to do because I cant return it to stock rom, clockmod recovery has stopped working, and every video I watch about how to fix it is only making it worse.
If you have any idea what I can do or what I'm doing wrong let me know.
Odin failed because you cannot flash older firmware. Your best bet is to reflash recovery via Odin, then if you want stock go to enewman17's stock rom/system dump thread in development and flash the rom and factory reset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Odin failed because you cannot flash older firmware. Your best bet is to reflash recovery via Odin, then if you want stock go to enewman17's stock rom/system dump thread in development and flash the rom and factory reset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I tried to flash cwm recovery onto my phone usb debugging selected and now odin doesnt even show that my phones recognized. This is so frustrating.
I suggest installing Philz Touch recovery via Odin and using Philz to flash a custom ROM to at least get your phone up and running.
devito35 said:
I tried to flash cwm recovery onto my phone usb debugging selected and now odin doesnt even show that my phones recognized. This is so frustrating.
Click to expand...
Click to collapse
If Kies is on your computer, remove it. Have you tried reinstalling drivers?
Sent from my SAMSUNG-SGH-I747 using Tapatalk