I have wanted for some time to have more control over my device and thought I should learn to flash roms. So I bought an old second hand Galaxy S2 for cheap, knowing I was likely to break it while learning. I have learned a lot, but not enough to recover it now that I have soft bricked it. Here is a more detailed description of the situation:
I was not able to install a custom recovery (twrp), I followed several guides and no matter what I did it always booted to the stock recovery. I have used both Odin and Heimdal, but I prefer Heimdal. I broke the phone by using adb sideload, after which it entered a boot loop and recovery was no longer accessible. Using Heimdall I was able get recovery mode back by flashing a stock rom but the recovery mode now has less options and sideload is not there. The phone still does not boot. I tried a few other things but I could not improve on that so far.
One of the major problems I am having is finding the correct roms. Samsung charges money for stock roms that old. On this forum most of the links to older roms are dead. From what I can gather it seems that Lineage might not be the best option for such an old phone and I might be better off trying Cyanogen, but I can't find any reliable seeming links for that either.
If anyone can offer suggestions as to how I should proceed I would be very grateful. The goal is to learn how to recover a phone and how to load custom roms, having a working phone at the end would be a good sign of success but is not the priority.
TiredPseudonym said:
I have wanted for some time to have more control over my device and thought I should learn to flash roms. So I bought an old second hand Galaxy S2 for cheap, knowing I was likely to break it while learning. I have learned a lot, but not enough to recover it now that I have soft bricked it. Here is a more detailed description of the situation:
I was not able to install a custom recovery (twrp), I followed several guides and no matter what I did it always booted to the stock recovery. I have used both Odin and Heimdal, but I prefer Heimdal. I broke the phone by using adb sideload, after which it entered a boot loop and recovery was no longer accessible. Using Heimdall I was able get recovery mode back by flashing a stock rom but the recovery mode now has less options and sideload is not there. The phone still does not boot. I tried a few other things but I could not improve on that so far.
One of the major problems I am having is finding the correct roms. Samsung charges money for stock roms that old. On this forum most of the links to older roms are dead. From what I can gather it seems that Lineage might not be the best option for such an old phone and I might be better off trying Cyanogen, but I can't find any reliable seeming links for that either.
If anyone can offer suggestions as to how I should proceed I would be very grateful. The goal is to learn how to recover a phone and how to load custom roms, having a working phone at the end would be a good sign of success but is not the priority.
Click to expand...
Click to collapse
Have you tried Odin ?
Sent from my Titanium Vista 4G using Tapatalk
SachinBorkar said:
Have you tried Odin ?
Click to expand...
Click to collapse
Yes.
Can you link any roms that will work with odin for a GS2?
TiredPseudonym said:
Yes.
Can you link any roms that will work with odin for a GS2?
Click to expand...
Click to collapse
Try to find on firmwarefiles.com
I flashed ROM on my friends phone I don't have this phone right now.
Sent from my Titanium Vista 4G using Tapatalk
firmwarefiles.com there is no site there. Could you link the one you mean?
TiredPseudonym said:
firmwarefiles.com there is no site there. Could you link the one you mean?
Click to expand...
Click to collapse
https://firmwarefile.com
Search on it.
/* If you want to ask me something always quote me */
Sent from my Titanium Vista 4G using Tapatalk
SachinBorkar said:
https://firmwarefile.com
/* If you want to ask me something always quote me */
Click to expand...
Click to collapse
Thanks for the rom site, I hadn't found that one and it appears to have a lot of useful stuff.
When I try to flash it just sits on "File Analysis" for ages. I let it sit for like an hour to be sure but nothing is happening. This was one of the reasons I preferred Heimdal to Odin, there is no feedback. Is there a way to make it more verbose so I can see what it is doing?
edit: I tried to extract the contents of the archive to try it in heimdall but the extractor said there was an error in the file. That is the only s2 rom they have so I guess I need new rom link
TiredPseudonym said:
Thanks for the rom site, I hadn't found that one and it appears to have a lot of useful stuff.
When I try to flash it just sits on "File Analysis" for ages. I let it sit for like an hour to be sure but nothing is happening. This was one of the reasons I preferred Heimdal to Odin, there is no feedback. Is there a way to make it more verbose so I can see what it is doing?
edit: I tried to extract the contents of the archive to try it in heimdall but the extractor said there was an error in the file. That is the only s2 rom they have so I guess I need new rom link
Click to expand...
Click to collapse
Maybe file you downloaded is currupt.
If Odin fails try older version of Odin or newer one.
If still problem then use miraclebox.
/* please give me more info about your device since it made by Samsung there must be stock ROM available on internet */
Sent from my Titanium Vista 4G using Tapatalk
Related
I was using Samsgung Galaxy SIII Toolkit v1.0 to root my (Sprint) device ( didn't realize v2.0 was out ) and at step 9 when the device was supposed to reboot on its own it just turned off and did not reboot. When I try to boot it I get a quick flash of SAMSUNG and then it turns off. I am able to boot into Download mode. USB Debugging is not enabled.
Any help is appreciated.
Thank you.
Update:
I tried downloading a few different versions of the toolkit, and they all seem to check for USB DEBUGGING before starting the rooting process. I'm not sure which version I had downloaded initially (just that it was v1.0) where it didn't... But that part of the process had a NOTE saying to turn it on, restart the phone and plug it back in to continue...
I also tried booting into recovery mode and factory resetting - no dice.
You're in the section of the international phone, not the US-version.
Most probably something went wrong with replacing the kernel, flash your RAM through Odin again and it should boot fine.
Just use CF-root (or whichever kernel applies to the US-version) through Odin instead of using these tools. People always recommend them and I'd had to revive my fair share of devices which were softbricked (that's what your device is) through their usage.
d4fseeker said:
You're in the section of the international phone, not the US-version.
Most probably something went wrong with replacing the kernel, flash your RAM through Odin again and it should boot fine.
Just use CF-root (or whichever kernel applies to the US-version) through Odin instead of using these tools. People always recommend them and I'd had to revive my fair share of devices which were softbricked (that's what your device is) through their usage.
Click to expand...
Click to collapse
This. Don't trust toolkits. Do yourself a favour and take time to learn how to use adb and on this phone, Odin, properly. It's unfortunate you had to learn why many people are against toolkits the hard way but if you follow the above advice and use Odin to flash a factory Rom for your phone all shall be well.
Sent from my GT-I9300 using Tapatalk 2
dr.m0x said:
This. Don't trust toolkits. Do yourself a favour and take time to learn how to use adb and on this phone, Odin, properly. It's unfortunate you had to learn why many people are against toolkits the hard way but if you follow the above advice and use Odin to flash a factory Rom for your phone all shall be well.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Mm.. I'm trying an Odin approach now. Initially I tried a Heimdall approach, but it kept failing. :\
Thanks for the response.
Odin and Heimdall both do the same stuff; they use the Samsung firmware update mode to push the device's firmware.
Download your ROM off samfirmware.com if you can't revive it through a simple kernel flash.
You might have to factory-reset your phone tough, hopefully not.
d4fseeker said:
Odin and Heimdall both do the same stuff; they use the Samsung firmware update mode to push the device's firmware.
Download your ROM off samfirmware.com if you can't revive it through a simple kernel flash.
You might have to factory-reset your phone tough, hopefully not.
Click to expand...
Click to collapse
I am currently writing a stock ROM to my phona via Odin. Once I'm back to stock I'll start messing around with it again. I just like touching base after I screw things up, if that makes sense.
I only bought the phone a few days ago so there's not much going on to lose, and I did do a full backup, so I'm not concerned. I already did a reset anyway when I first broke it.
I appreciate your help, and do now see that I'm in the wrong forum. In the future I'll post in the correct forum. Sorry again. Very embarrassing.
Thanks.
I just like touching base after I screw things up, if that makes sense.
Click to expand...
Click to collapse
Yep. That's how (and most other people learn their stuff. Learning by breaking (and after having gained some knowledge, fixing)
Sorry again. Very embarrassing.
Click to expand...
Click to collapse
It's more a problem for you than for us. If you were to flash a linked zip without really taking care you could hard-softbrick (only revivable through USB-Jig) or possibly hardbrick (only revivable through JTAG) your phone so it's best to stick in the correct section with the correct files =)
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem
Hi I tried to root my phone using this method ( http://forum.xda-developers.com/showthread.php?t=1504218 ) and it left my phone stuck on the reboot. I then tried to flash the stock kernel via odin, and when that didn't work I flashed cwm via odin and then a rogers kernel through cwm and it is still stuck on the rogers logo.......?
could someone help me......?
AirForce 1 said:
Hi I tried to root my phone using this method ( http://forum.xda-developers.com/showthread.php?t=1504218 ) and it left my phone stuck on the reboot. I then tried to flash the stock kernel via odin, and when that didn't work I flashed cwm via odin and then a rogers kernel through cwm and it is still stuck on the rogers logo.......?
could someone help me......?
Click to expand...
Click to collapse
I see your post count and realize you cannot post in the development section yet. that should not however stop you from reading. maybe you have but you may not have read the whole thread. i know that may seem like a daunting task, it is for me. so what I o is go to the most recent post or last page and start reading backwards. that way I get the most up to date information even on an older thread as you are referring to.
if you did that you would have seen a post from AGOATTAMER.
http://rootgalaxynote.com/galaxy-note-i717-roms/how-to-root-att-galaxy-note-sgh-i717-icsgingerbreadeasiest-method/
this is also the method I used. believe me, if I can pull it off, anybody can.
more tips..............
make sure you have all the files you need
rehearse the process
I know it sounds crazy, but these phones aint cheap and if you mess it up, can be pretty screwed.
so what is more valuable???? your phone or acting crazy and talking to yourself for a few minutes.
if you can still get download mode, your good, no brick
good luck
You flashed an older incompatible kernel with a newer ROM, but I guess you know that now. Flash the stock ROM found here using odin.
http://www.hotfile.com/dl/213010140/75bf7e2/I717RUXMD1_I717RRWCMD1_RWC.zip.html
Go into recovery after install and do a factory reset. Then start over. Many have used the link that captemo has mentioned. There are newer versions of recovery than the one listed on that site but it will get you rooted. Look at this thread also. Since you are installing the stock ROM via odin you will not have to deal with the script mentioned here.
http://forum.xda-developers.com/showthread.php?t=2485336
Just flash twrp with Odin, don't reboot into android, not directly into recovery after the flash finishes...
In recovery wipe data/factory reset.
When you go to boot it'll see you're not rooted and ask if you want to.
The easiest method to root.
Edit: note to self
Self,
check links before posting to avoid repeating yourself
studacris said:
Edit: note to self
Self,
check links before posting to avoid repeating yourself
Click to expand...
Click to collapse
Good advice is always worth repeating.
Sent from my Big Ass Outlaw Phone.
I received this verizon Galaxy Tab 10.1 as a gift and a project, but haven't been able to make any progress.
The tablet was bought from a taxi company that used it was in car entertainment. When booted, an app immediately starts up and removes the navigation bar. If you are fast enough, you can get to the settings and uninstall this app before it starts, or what I have found to be easier, just use shell commands to hit home and uninstall while the app tries to regain control.
The table is currently running 3.2, and cannot update over wifi, nothing happens.
Root was gained by an unknown method, but the SU app won't open up. I can access su through the shell however.
I have tried flashing a cwm recovery through ODIN which says is successful but if it is booted straight to the recovery it is still stock.
Flashing ROM's through ODIN appear to be successful, but just boots right back to the original rom and recovery.
Adding anything to the SD card or anywhere else accessable to the stock recovery does not work either because the SD card is reformatted to the original contents every time.
This also occurs with any apps that are installed, each one is removed when rebooted except for SU. And Rom Manager FC's when CWM is attempting to flash.
nvflash will not work either because the bootloader is locked.
I don't know much about the boot sequence for android, but I looked for any init. files that are out of the ordinary and cannot find anything.
I'm giving this tablet away when I finally figure it out, I just want to fix it. Any help would be awesome and let me know if I've left something out.
Even if no one has any specific suggestions, can someone post a PIT file for a SCH-i905? I have seen the stock firmware that can be flashed through ODIN but it does not stick on my unit.
Thanks!
Excuse my English but my original language is Spanish.
The default verizon tablet brings in recovery an option that reloads the original recovery. If units installed CWM via Odin must access the recovery option (Vol +) on 1st boot and enter the option to leave cmw (reboot) will give you the option of not recovering the recovery.
The other alternative is to flash via odin the original software look it by google "PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE20110704_0708"
in this case the tab stay with the factory version.
if the team does not have SIM must type top left - top right - bottom left, bottom right and then vol + to unlock.
good look
This is the post that you are needing.
http://forum.xda-developers.com/showthread.php?t=1342995
Sent from my SM-N900V using XDA Premium 4 mobile app
i had the same problem but pulling the sim and unlocking as mentioned above helped a lot then went through the whole rooting process through odin and have not had any issues with anything reverting back to stock. only issue now is not very many roms for our model "bummer" all in all still a good droid tablet for what i paid lol if you still havent got it going let me know and i will give you all the directions and steps i used
I have tried installing PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE2011070 4_0708 through Odin3.
I do boot directly into recovery after installing CWM, the stock recovery still persists. I have tried several times because I know sometimes it does not stick.
I have also tried flashing the factory image linked in that xda post "[ROM]EG01 - Factory STOCK ODIN Image - VZW LTE Tab 10.1".
Boots right back up and starts the same taxi cab show case media software it normally does.
One thing I did not note in the first post. I do have root access when the tablet is booted into the os, but I do not when the tablet is in recover. I dont know if this is unusual or not.
I can also install busy box, but have yet to find out his would be useful.
I also do not have access to nvflash, but I think this is normal because the bootloader is not unlocked.
http://forum.xda-developers.com/showthread.php?p=49924392
Might work for you too. This is a post I made in another thread.
Sent from my Nexus 4 using Tapatalk
baystallion said:
http://forum.xda-developers.com/showthread.php?p=49924392
Might work for you too. This is a post I made in another thread.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Awesome, I'll give this a go when I get home.
Was there a p4vzw twrp version some where in those links?
Looks like all of the ones referenced were 3g and wifi only.
Sidenote: I don't care if I keep 4g functionality or not, I will only be using this for wifi, if that makes fixing the problem any easier.
hsbr said:
Was there a p4vzw twrp version some where in those links?
Looks like all of the ones referenced were 3g and wifi only.
Sidenote: I don't care if I keep 4g functionality or not, I will only be using this for wifi, if that makes fixing the problem any easier.
Click to expand...
Click to collapse
Search for infamous AOKP 4.2 thread. I think it has twrp for p4vzw.
Sent from my GT-P7500 using Tapatalk
eushaun99 said:
Search for infamous AOKP 4.2 thread. I think it has twrp for p4vzw.
Sent from my GT-P7500 using Tapatalk
Click to expand...
Click to collapse
I was able to find the thread, thanks!
After downloading the odin flashable twrp, I tried first with Odin3, but it failed. Then I flashed with JOdin, this first pulled a PIT file from the tab then failed to repartition. If I ran it without repartitioning it said it was sucessful, but if I boot straight into recovery the stock android recovery still comes up.
I have a way to get a pit file now though, so that's nice.
hsbr said:
I was able to find the thread, thanks!
After downloading the odin flashable twrp, I tried first with Odin3, but it failed. Then I flashed with JOdin, this first pulled a PIT file from the tab then failed to repartition. If I ran it without repartitioning it said it was sucessful, but if I boot straight into recovery the stock android recovery still comes up.
I have a way to get a pit file now though, so that's nice.
Click to expand...
Click to collapse
Don't use the Odin way. First flash cwm recovery, then flash the twrp zip file.
Sent from my GT-P7500 using Tapatalk
eushaun99 said:
Don't use the Odin way. First flash cwm recovery, then flash the twrp zip file.
Sent from my GT-P7500 using Tapatalk
Click to expand...
Click to collapse
I can't flash CWM in the first place. I have listed all of the different methods I tried flashing CWM with in the OP.
hsbr said:
I can't flash CWM in the first place. I have listed all of the different methods I tried flashing CWM with in the OP.
Click to expand...
Click to collapse
Oh, then I can't help you then. Sorry.
Sent from my GT-P7500 using Tapatalk
hsbr said:
Even if no one has any specific suggestions, can someone post a PIT file for a SCH-i905? I have seen the stock firmware that can be flashed through ODIN but it does not stick on my unit.
Thanks!
Click to expand...
Click to collapse
Yes please i have an issue my tablet got stuck on samsung logo i tried to flash another rom because i cant fing any rom for this tablet US Callular
i905. Tab 2 10.1.
If any one can provide a stock odin or something to make this tablet work i would appreciated?
I've searched the forums and haven't found a solution to my problem. I have rooted S4 MK2 and wanted to put Gummy ROM on it, only finding out after I had installed TWRP that this wouldn't be possible. No big deal, but now, I can't get away from the stupid downloading screen for TWRP. No longer do I get the screen before it warning about tinkering with your operating system, and once it's stuck on the screen, getting the phone to boot properly sometimes takes a while, and a lot of foul language. I've tried several things to bypass/delete/overwrite TWRP, to no avail. ODIN doesn't work for me, tried several versions, ROM Manager and CWM doesn't work, when I try to boot into CWM mode it goes to downloading screen of TWRP. I finally gave up, decided to nuke it from space and do a factory reset... which took me straight to the damnedable downloading screen! This tells me I will probably be unable to update or use any ASOP ROMs that I might run into, because once on the downloading screen, nothing works, the phone isn't recognized by my computer, two different versions of ODIN failed to get its attention, unable to to load .pit or .tar files... I'm at wits end folks, and haven't found a solution in any other threads on xda, or the net in general, any help and suggestions would be much appreciated. I've not used ADB before, but if need be, I'll learn if there's a fix going that route.
roshane said:
I've searched the forums and haven't found a solution to my problem. I have rooted S4 MK2 and wanted to put Gummy ROM on it, only finding out after I had installed TWRP that this wouldn't be possible. No big deal, but now, I can't get away from the stupid downloading screen for TWRP. No longer do I get the screen before it warning about tinkering with your operating system, and once it's stuck on the screen, getting the phone to boot properly sometimes takes a while, and a lot of foul language. I've tried several things to bypass/delete/overwrite TWRP, to no avail. ODIN doesn't work for me, tried several versions, ROM Manager and CWM doesn't work, when I try to boot into CWM mode it goes to downloading screen of TWRP. I finally gave up, decided to nuke it from space and do a factory reset... which took me straight to the damnedable downloading screen! This tells me I will probably be unable to update or use any ASOP ROMs that I might run into, because once on the downloading screen, nothing works, the phone isn't recognized by my computer, two different versions of ODIN failed to get its attention, unable to to load .pit or .tar files... I'm at wits end folks, and haven't found a solution in any other threads on xda, or the net in general, any help and suggestions would be much appreciated. I've not used ADB before, but if need be, I'll learn if there's a fix going that route.
Click to expand...
Click to collapse
Does Odin "see" your phone? If so, what build are you trying to install?
I know the damage is done, but a little reading before hand would have let you know that with MK2 you can't install a custom recovery. Only Safestrap works with compatible Touchwiz 4.3 Roms
Edit: Maybe this thread will help. http://forum.xda-developers.com/showthread.php?t=2578209
Edit #2: My apologies. Just re-read your post and I see you said, more than once, that Odin isn't seeing your phone. I'm afraid I won't be any help. Good luck.
Odin sees the phone, but fails at all attempts to install anything. .pit, .tar etc. I originally wanted to install Gummy but now I know that won't ever work, then I just tried to install stock .tar file and it also fails.
roshane said:
I've searched the forums and haven't found a solution to my problem. I have rooted S4 MK2 and wanted to put Gummy ROM on it, only finding out after I had installed TWRP that this wouldn't be possible. No big deal, but now, I can't get away from the stupid downloading screen for TWRP. No longer do I get the screen before it warning about tinkering with your operating system, and once it's stuck on the screen, getting the phone to boot properly sometimes takes a while, and a lot of foul language. I've tried several things to bypass/delete/overwrite TWRP, to no avail. ODIN doesn't work for me, tried several versions, ROM Manager and CWM doesn't work, when I try to boot into CWM mode it goes to downloading screen of TWRP. I finally gave up, decided to nuke it from space and do a factory reset... which took me straight to the damnedable downloading screen! This tells me I will probably be unable to update or use any ASOP ROMs that I might run into, because once on the downloading screen, nothing works, the phone isn't recognized by my computer, two different versions of ODIN failed to get its attention, unable to to load .pit or .tar files... I'm at wits end folks, and haven't found a solution in any other threads on xda, or the net in general, any help and suggestions would be much appreciated. I've not used ADB before, but if need be, I'll learn if there's a fix going that route.
Click to expand...
Click to collapse
If you had taken 5 minutes of time to research...you wouldn't have bricked your phone...Countless threads on this very thing.
Sent from my SCH-I545 using XDA Premium 4 mobile app
roshane said:
Odin sees the phone, but fails at all attempts to install anything. .pit, .tar etc. I originally wanted to install Gummy but now I know that won't ever work, then I just tried to install stock .tar file and it also fails.
Click to expand...
Click to collapse
What exactly are you trying to install with Odin?
no bricking, just, let's say a small pebble.
riker147 said:
What exactly are you trying to install with Odin?
Click to expand...
Click to collapse
My most recent attempt was SCH-I545.pit, didn't work... I also tried Philz_Touch, gummy, and one other ROM which, of course didn't work, now I know why the roms didn't, but no sure why the .pit file won't work. All I really want to do now is remove all traces of TWRP. My phone isn't bricked, totally usable, it just won't be able to be updated or customized until I get rid of TWRP
roshane said:
My most recent attempt was SCH-I545.pit, didn't work... I also tried Philz_Touch, gummy, and one other ROM which, of course didn't work, now I know why the roms didn't, but no sure why the .pit file won't work. All I really want to do now is remove all traces of TWRP. My phone isn't bricked, totally usable, it just won't be able to be updated or customized until I get rid of TWRP
Click to expand...
Click to collapse
It looks to me like your only option is to Odin back to stock MK2. Did you check out the link I gave you in my first post?
riker147 said:
It looks to me like your only option is to Odin back to stock MK2. Did you check out the link I gave you in my first post?
Click to expand...
Click to collapse
I'm reading over it now, considering doing the full wipe. Now that I know custom ROMS are going to be limited to ASOP I don't mind going stock and unrooted. I really appreciate your help
roshane said:
I'm reading over it now, considering doing the full wipe. Now that I know custom ROMS are going to be limited to ASOP I don't mind going stock and unrooted. I really appreciate your help
Click to expand...
Click to collapse
If you get it straightened out I would recommend reading this thread after. http://forum.xda-developers.com/showthread.php?t=2606501
Let me know how you make out. Good luck.
From reading this I think you're confusing TWRP with Odin. TWRP doesnt have a downloading screen, but Odin does and thats exactly the screen you want to be on to flash a stock Odin tar. You will need to flash a full stock tar. And if you respond saying it didnt work please include the Odin error log.
Sent from my SCH-I545 using XDA Premium 4 mobile app
riker147 said:
If you get it straightened out I would recommend reading this thread after. http://forum.xda-developers.com/showthread.php?t=2606501
Let me know how you make out. Good luck.
Click to expand...
Click to collapse
no luck so far, got the full wipe downloaded, put everything into Odin, and in the Odin message box it says setupconnection.. not real sure what to do...
roshane said:
no luck so far, got the full wipe downloaded, put everything into Odin, and in the Odin message box it says setupconnection.. not real sure what to do...
Click to expand...
Click to collapse
You making sure you have the proper USB drivers as well as a good USB cable?
Also like surge said its kind of confusing I think you're confusing Odin with twrp as well at times.
So now your trying to load which file from within Odin???
Sent from my SCH-I545 using Tapatalk
Mistertac said:
You making sure you have the proper USB drivers as well as a good USB cable?
Also like surge said its kind of confusing I think you're confusing Odin with twrp as well at times.
So now your trying to load which file from within Odin???
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Got everything working, I'm all stock and all systems are go. Thank you very much for your kind help. I'm going to now patiently wait for the official 4.4 update to arrive and otherwise leave my phone stock.