Hello,
I just got my replacement S3 and I rooted it with SuperSu-GS3_Debugfs and then unlocked my bootloader with the tool posted here and then I downloaded Goomanager and installed a custom recovery but it continues to boot into the Samsung recovery...? I never had this issue before.... Right after Goomanager downloaded the recovery I was able to enter custom recovery once so that I could make a backup but after I made a backup I cannot get back into custom...? Weird, maybe I am just tired but I have done this plenty of times and don't see why it's not working... This is the first replacement that I received with the newest Verizon OTA on it though... Other than that I don't see what the deal is? Thanks in advance!! I'm sure it is something simple I am missing here...
Download ez recovery and just reinstall the recovery.
Sent from my sexy white Eclipsed galaxy S3
kintwofan said:
Download ez recovery and just reinstall the recovery.
Sent from my sexy white Eclipsed galaxy S3
Click to expand...
Click to collapse
I thought of that but I just don't understand why Goomanager would not do it.... I really want TWRP so that is my main goal here... You think goomanager is the culprit even though it allowed me to enter TWRP to make a backup already....?
Did it ever boot into recovery? The first time I was in cwm recovery it went then I clicked through a screen that asks you to click yes to boot into it every time. When I rebooted to recovery it took me to stock recovery. I went into rom manager and flashed it again, then made sure I chose yes on the screen that warns you that it might boot into stock recovery.
Sent from my SCH-I535 using XDA Premium HD app
edjm711 said:
Did it ever boot into recovery? The first time I was in cwm recovery it went then I clicked through a screen that asks you to click yes to boot into it every time. When I rebooted to recovery it took me to stock recovery. I went into rom manager and flashed it again, then made sure I chose yes on the screen that warns you that it might boot into stock recovery.
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
Yes I made my first backup in TWRP after I flashed it.... Now it will go straight to Samsungs recovery...
EDIT: Just tried the recovery program from the app store and it's doing the same thing....? I can get into custom recovery once and after I reboot I seem to lose it? This **** is weird!
Anybody??
What build number is it? I remember on my droid charge Samsung put a command to flash stock recovery on boot. You could just install the recovery, boot into it and immediately install a custom ROM.
Sent from my sexy white Eclipsed galaxy S3
kintwofan said:
What build number is it? I remember on my droid charge Samsung put a command to flash stock recovery on boot. You could just install the recovery, boot into it and immediately install a custom ROM.
Sent from my sexy white Eclipsed galaxy S3
Click to expand...
Click to collapse
It is baseband version I535VRLG7
IMM76D.I535VRALG7- build number
This is just the latest build right? I should not have any issues... Its got me sooo pissed off right now!
Ya that's strange? You could try to Odin rout66 or a stock ROM and try again
Sent from my sexy white Eclipsed galaxy S3
kintwofan said:
Ya that's strange? You could try to Odin rout66 or a stock ROM and try again
Sent from my sexy white Eclipsed galaxy S3
Click to expand...
Click to collapse
Ya I am trying that now.... Thanks for the replies though! :good:
kintwofan said:
What build number is it? I remember on my droid charge Samsung put a command to flash stock recovery on boot. You could just install the recovery, boot into it and immediately install a custom ROM.
Sent from my sexy white Eclipsed galaxy S3
Click to expand...
Click to collapse
Okay... So as you said earlier about your Charge, I think Verizon is getting tricky here cause I tried EVERYTHING and I had to flash a custom rom to get my custom recovery to stick on the latest build and I have never had to do that.... This has never been an issue so something has changed?? I finally got Cleanrom on it with TWRP cause I was determined not to go back to the old build! I installed TWRP again and again but it would not stick after a reboot so I just quickly flashed a rom while I was in TWRP and I'm golden now so idk what the deal was.... Verizon is a pain in my ASS!!! I never had to go through all this **** to install a rom on this device. Glad I had patience today cause I was gettin angry!! Oh well it is solved for the moment.... :victory: I am glad that at least one person tried to help me out ( kintwofan).... I thought I would have gotten more feedback but I guess that's what I get for thinkin...
Glad you got it going
Sent from my sexy white Eclipsed galaxy S3
kintwofan said:
Glad you got it going
Sent from my sexy white Eclipsed galaxy S3
Click to expand...
Click to collapse
You just about got all my thanks today just because you at least tried to give me a solution.... Soooo Thanks! LOL
No problem, since I can't develop I try to help in some way.
Sent from my sexy white Eclipsed galaxy S3
kintwofan said:
No problem, since I can't develop I try to help in some way.
Sent from my sexy white Eclipsed galaxy S3
Click to expand...
Click to collapse
Ya me too but I was kinda let down today.... Oh well, people got their own **** to deal with I guess but this was really my first time I was REALLY in need for some help and no one showed up to the party.... LOL Have a good night buddy! Thread closed!
That also happened to me.
After upgrading to latest AT&T OTA same thing happened to me.
I downloaded ROM Manager and instaled CWM recovery.
I was able to reboot in recovery once and then at boot a message would appear saying (something really fast) and then back to stock recovery.
Anyway in ROM manager it would recognize again that I had flashed the CWM recovery.
After I installed CWM touch it stop doing it. SO.
Best luck
I'm due to get my replacement tomorrow but what's funny is I ran into the same issue with my current device after I had gone back to stock and rooted again. Thinking it just has something to do with the update they pushed but ill report back tomorrow after I get it all rooted to see if I run into it again.
Sent from my SCH-I535 using xda app-developers app
There is a file somewhere I'm not sure that you can delete and it should stop this. It is strange though because I don't recall this being an issue with this phone. I'll see if I can't find where that file would be.
imurg said:
After upgrading to latest AT&T OTA same thing happened to me.
I downloaded ROM Manager and instaled CWM recovery.
I was able to reboot in recovery once and then at boot a message would appear saying (something really fast) and then back to stock recovery.
Anyway in ROM manager it would recognize again that I had flashed the CWM recovery.
After I installed CWM touch it stop doing it. SO.
Best luck
Click to expand...
Click to collapse
bc760 said:
I'm due to get my replacement tomorrow but what's funny is I ran into the same issue with my current device after I had gone back to stock and rooted again. Thinking it just has something to do with the update they pushed but ill report back tomorrow after I get it all rooted to see if I run into it again.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
JBO1018 said:
There is a file somewhere I'm not sure that you can delete and it should stop this. It is strange though because I don't recall this being an issue with this phone. I'll see if I can't find where that file would be.
Click to expand...
Click to collapse
Ya this was my first time I had ever encountered a problem and I have had 3 different refurbs.... So what they are doing is forcing the device to go into Samsung's recovery instead of your custom... But as long as you transfer a rom over the first time you boot into custom recovery and flash it your all good.... Just took me awhile to figure it out... Them bastards!! LOL
I did mine this weekend but it had been rooted prior to the OTA update, and I didnt do the update, I'm running AOKP JB..
My GFs has the update and just now I tried doin hers to put JB on it and it won't boot into CWM, just keeps goin to the Samsung recovery. I used the EZ-unlock tool v1.2, and Odin to put CWM on.
Hopefully we can get some help....
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
OK, HA, shoulda read some first
So if I flash a custom rom through odin I can do this? Can someone point me to somewhere there is a guide?
I'm new to this stuff, my last phone was a motorola i3. LOL
Related
Well everyone here is the moment we have all been waiting for a little GB love for our SGS4G http://hotfile.com/dl/121009639/fc3e54d/T595VUVKF1.rar.html down load file run through odin Gingerbread Goodness credit to birgertime for the find.
Password For the file is samfirmware.com
This Rom is not Rooted
Currently no way to get back to our own roms right now with that GB rom! I cannot for the life of me restore my backups.
Eric-1987 said:
Currently no way to get back to our own roms right now with that GB rom! I cannot for the life of me restore my backups.
Click to expand...
Click to collapse
Sorry for your woes. Hope u get things worked out. If you do get things worked out wait until one of the devs fixes this issue. I'm sure well see a deodexed version soon, I hope.
Sent from my SGH-T959V using XDA Premium App
I love it, downloading right now. Lets see how our phone files
This is huge. Has anyone rooted this yet? That's the question. Superoneclick doesn't seem to do the trick.
Sent from my SGH-T959V using XDA Premium App
Eric-1987 said:
Currently no way to get back to our own roms right now with that GB rom! I cannot for the life of me restore my backups.
Click to expand...
Click to collapse
pretty sure you need a root before you can do that buddy
Eric-1987 said:
Currently no way to get back to our own roms right now with that GB rom! I cannot for the life of me restore my backups.
Click to expand...
Click to collapse
You can odin a ROM that's gotten rooted so you can use quickreboot or adb to get into recovery mode, then you can use CWM from there if you had it installed already. I just had to flash an old rooted ROM to be able to get to recover my CWM backup.
EDIT:
OP, by the way the password for the file at that link is
samfirmware.com
FBis251 said:
You can odin a ROM that's gotten rooted so you can use quickreboot or adb to get into recovery mode, then you can use CWM from there if you had it installed already. I just had to flash an old rooted ROM to be able to get to recover my CWM backup.
EDIT:
OP, by the way the password for the file at that link is
samfirmware.com
Click to expand...
Click to collapse
Thanks will update original post
Ah man I just got my phone to my liking lol.
I think I'll wait a bit though as this is almost like a KC1 for froyo. Leaked build, so there will probably be a final build avail via OTA and Kies.
nothing better to do might as well flash and play lol worse comes to worse can always odin back and recover with clockwork
super!
flashing rite now. let you guys know how it goes later.
Just curious ....Anyone else not able to get into download mode or stock recovery via ANY METHOD ?
Bl4ckpheniX said:
Just curious ....Anyone else not able to get into download mode or stock recovery via ANY METHOD ?
Click to expand...
Click to collapse
That would be no bueno. Definitely interested to hear if you can get into Download mode, recovery not as much. DL at least you have ODIN.
^^uh oh
10chara
I tried to flash without the bootloader using Heimdall so I can flash back. it finished flashing but wont boot to the OS. so I Odined back to KD1.
try the home button should allow u to flash back via odin
fknfocused said:
^^uh oh
10chara
Click to expand...
Click to collapse
I think on the galaxy s phones they couldn't get into recovery or dl mode unless they flashed the gingerbread boot loader
Sent from my HTC Glacier using XDA Premium App
Just flashed with no problem. Everything seems to work fine. I dont see much changes just some of the menu settings. Phone seems to run smooth. Gonna use it for a bit and let you guys know.
Thanksssssssssssssssss!!!
To going to download mode first you must open ODIN. Assume your phone is off. Then press and hold the volume + and - then plug the USB to your PC. You should see a BIG yellow triangle on the phone said Download mode. Hope this helps.
Keymapping is changed in GB. Not familiar with your phone nut on the original Vibrant GB bootloaders now require one volume key instead of two.
Okay, So I just rooted and unlocked the bootloader on my Verizon Galaxy S III and tried to flash Cyanogenmod 10 (the latest on on rom manager) and its now stuck on the boot animation. I created a backup before I did this through rommanager but when I try to utilize it, it says the file is empty. HELP PLEASE!! :crying:
Rom Manager strikes again. lol Odin back to stock and start over.
jljones06 said:
Okay, So I just rooted and unlocked the bootloader on my Verizon Galaxy S III and tried to flash Cyanogenmod 10 (the latest on on rom manager) and its now stuck on the boot animation. I created a backup before I did this through rommanager but when I try to utilize it, it says the file is empty. HELP PLEASE!! :crying:
Click to expand...
Click to collapse
I have used it a couple of years ago on my galaxy s fascinate but i forgot how to use odin. Any download links and tutorials you know of? Thanks again
Pulled link from other noob. Yall on a roll today. LOL
http://forum.xda-developers.com/showthread.php?t=1762709
If everything you need not in that section read the rest of Droidstyle's thread.
prdog1 said:
Pulled link from other noob. Yall on a roll today. LOL
http://forum.xda-developers.com/showthread.php?t=1762709
If everything you need not in that section read the rest of Droidstyle's thread.
Click to expand...
Click to collapse
What's wrong with RomManager? Screwing everything up.
Anayalata said:
What's wrong with RomManager? Screwing everything up.
Click to expand...
Click to collapse
You should always be sure to check the total size of the backup file before continuing with low level flashing. With the SGS III CWM has been notorious for not working properly with recovery processes. I switched over to TWRP after my dilemma with CWM.
So yeah, ODIN back to stock and start over.
Be thankful you only have a bootloop and not a total brick.
tekrhino said:
You should always be sure to check the total size of the backup file before continuing with low level flashing. With the SGS III CWM has been notorious for not working properly with recovery processes. I switched over to TWRP after my dilemma with CWM.
So yeah, ODIN back to stock and start over.
Be thankful you only have a bootloop and not a total brick.
Click to expand...
Click to collapse
Well I ended up reflashing the stock rom last night then tried to unlock bootloader again and when I started the ez unlock app it said my phone didnt have root access. So I rooted again the same way I did the first time and now when I try to launch the app it just sits there with a white screen. So then I downloaded a rootchecker app from the market and it says I dont have root access which is probably why the EZ_Unlock app isnt working properly. Thoughts?
jljones06 said:
Well I ended up reflashing the stock rom last night then tried to unlock bootloader again and when I started the ez unlock app it said my phone didnt have root access. So I rooted again the same way I did the first time and now when I try to launch the app it just sits there with a white screen. So then I downloaded a rootchecker app from the market and it says I dont have root access which is probably why the EZ_Unlock app isnt working properly. Thoughts?
Click to expand...
Click to collapse
Open up superuser and update the binaries
Sent from my S3 running Eclipse 2.1
kintwofan said:
Open up superuser and update the binaries
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
That worked! So now that I've pretty much back to step one, is there anything I should watch out for while trying to flash another ROM? Maybe any ROM suggestions? Thanks
Just flash the ROM yourself in recovery, don't count on RM.
apacseven said:
Just flash the ROM yourself in recovery, don't count on RM.
Click to expand...
Click to collapse
Ill for sure keep that in mind.
Once you get on CM10 their built in updater works pretty well. I haven't heard anyone complain except for the fact it doesn't do an autobackup for you, it just dirty flashes it.
Ok so I have been trying to flash a rom to my phone for a while now. This isn't my first rodeo but I am far from being one of you technology gurus (whom I am very thankful for). SO I picked Blackbean 5. Now I downloaded it to my phone, and after magically....ok accidentally I got it on there I think. However, now all my phone is doing is getting stuck at the Baked Logo. I've tried Odin but that doesn't seem to work. Any suggestions?
Ok so I have been trying to flash a rom to my phone for a while now. This isn't my first rodeo but I am far from being one of you technology gurus (whom I am very thankful for). SO I picked Blackbean 5. Now I downloaded it to my phone, and after magically....ok accidentally I got it on there I think. However, now all my phone is doing is getting stuck at the Baked Logo. I've tried Odin but that doesn't seem to work. Any suggestions?
Click to expand...
Click to collapse
Suggestions on what?? Do u have a recovery installed?? Cwm/twrp..
Sent from gs3..
P2o8wer said:
Suggestions on what?? Do u have a recovery installed?? Cwm/twrp..
Sent from gs3..
Click to expand...
Click to collapse
I had Cwmr installed but nothing was working. It was just stuck on the boot screen. I figured out the fix though. So I'll post it in the off chance some other noob comes along and has the same problem. I just reflashed the rom and it worked fine. I always seem to have one hiccup everytime I root. This was the first time I figured out the fix on my own.
Here's the story:
I got excited about the bootloader vulnerability (Loki) being released, and I saw that a few devs had updated their ROMs to work with Loki so I decided to give it a shot.
The easiest, fail-free way of installing a recovery was to install TWRP through goomanager. I had only ever used CWM, but I figured it couldn't be that difficult to learn/use. And it wasn't, I'm just dumb. I went to wipe my S4 and I misunderstood what I was supposed to do and ended up formatting the phone instead. On CWM, this is normal and basically just means factory restore, but on TWRP this wipes everything, including the OS. This might not have been as big of a problem if that wipe hadn't just erased the ROM I was intending to install.
Long story short, with no OS on the phone, I was stuck on the Samsung boot screen and I could not even get into recovery. I tried ODIN restoring the stock firmware twice, but despite the fact that ODIN said "SUCCESS", my phone was in the same state. After panicking for a couple of hours :crying: and trying different things (including just leaving the phone alone for a while in hopes that I would come back and it would be magically fixed) I downloaded Kies. I figured, Kies comes directly from Samsung. If there's a way to fix my phone, this has to be it.
I did the emergency firmware recovery, and it took forever and when it was done it looked like I was going to end up right where I started, when after about a minute of the Samsung boot screen, I saw the heavenly blue-purple swish of the boot animation. :victory:
tl;dr: I thought I bricked my phone. I brought it back to life with Kies.
That's my story. Hopefully it'll help someone who is panicking that they just borked their new phone and helps them restore it.
I'm sad to say that I also wiped a phone with TWRP. It wasn't an S4 and I didn't need Kies.
I had no idea that it would delete the OS - I don't think there was even a warning.
What ROM were you going to use that supported Loki?? I can't seem to find one anywhere...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
drucquerkellan said:
What ROM were you going to use that supported Loki?? I can't seem to find one anywhere...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
okzygen said:
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
Click to expand...
Click to collapse
OK thanks I'll try them in a little bit and report back here how it goes!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
You can still mount to USB through recovery and transfer a ROM zip over and then flash it.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
okzygen said:
Here's the story:
I got excited about the bootloader vulnerability (Loki) being released, and I saw that a few devs had updated their ROMs to work with Loki so I decided to give it a shot.
The easiest, fail-free way of installing a recovery was to install TWRP through goomanager. I had only ever used CWM, but I figured it couldn't be that difficult to learn/use. And it wasn't, I'm just dumb. I went to wipe my S4 and I misunderstood what I was supposed to do and ended up formatting the phone instead. On CWM, this is normal and basically just means factory restore, but on TWRP this wipes everything, including the OS. This might not have been as big of a problem if that wipe hadn't just erased the ROM I was intending to install.
Long story short, with no OS on the phone, I was stuck on the Samsung boot screen and I could not even get into recovery. I tried ODIN restoring the stock firmware twice, but despite the fact that ODIN said "SUCCESS", my phone was in the same state. After panicking for a couple of hours :crying: and trying different things (including just leaving the phone alone for a while in hopes that I would come back and it would be magically fixed) I downloaded Kies. I figured, Kies comes directly from Samsung. If there's a way to fix my phone, this has to be it.
I did the emergency firmware recovery, and it took forever and when it was done it looked like I was going to end up right where I started, when after about a minute of the Samsung boot screen, I saw the heavenly blue-purple swish of the boot animation. :victory:
tl;dr: I thought I bricked my phone. I brought it back to life with Kies.
That's my story. Hopefully it'll help someone who is panicking that they just borked their new phone and helps them restore it.
Click to expand...
Click to collapse
all you have to do is boot to recovery, and push a rom through adb to your phone. I've done this dozens of times accidentally and the easiest way to avoid it is to keep a backup rom on your sd at all times
mcmb03 said:
all you have to do is boot to recovery, and push a rom through adb to your phone. I've done this dozens of times accidentally and the easiest way to avoid it is to keep a backup rom on your sd at all times
Click to expand...
Click to collapse
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
niceppl said:
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
yeah, either way kies was probably at the bottom of the list for solutions since you were trying to put a different rom on your phone anyways
niceppl said:
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
Or the easiest of the options that I already mentioned 4 posts up... Don't even need to bother with adb or taking off your back cover. Plug in, mount, click-and-drag file transfer, unmount, flash, done.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I'm just glad you got it taken care of OP. Hopefully this thread will help others who may have a mishap while flashing ROMs.
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
This is incredible. Incredible how badly you almost screwed yourself over with, and incredible that Kies was actually helpful.
I installed Kies to backup contacts, once. After that? Thing crashes on updates, takes 30 minutes to load, hated any music I threw at it, didnt like my wireless transfer setting....
idk I had a pretty bad experience with Kies, i'm glad to hear that program isnt all useless.
okzygen said:
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
Click to expand...
Click to collapse
Yea that part doesn't make sense though. Many times I've seen people try to boot out of recovery with no system and always be able to get right back into recovery. Not that I don't believe you, just saying it's weird. Which leads me to the guy above... he didn't really screw himself that bad, no danger of bricking at all, just needed a reflash.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Just FYI on Kies
Am not sure on windows pc, but on my imac adb does not work with Kies. Had to use the Kies uninstaller to get if off imac then use adb. Maybe this isn't an issue on all phones?
Just got s4, and coming from HTC One S. So, if this is old news, sorry--
okzygen said:
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
Click to expand...
Click to collapse
I'm pretty sure you have to wipe cache once you do odin in order to boot back in OS or else you'll just get stuck at logo
polish_pat said:
I'm pretty sure you have to wipe cache once you do odin in order to boot back in OS or else you'll just get stuck at logo
Click to expand...
Click to collapse
I'm curious, is there a way to do this in download mode (via Odin or otherwise)? As far as I know, I can only do that through recovery. Do I have to adb and wipe /cache?
Sent from my SGH-I337 using xda app-developers app
okzygen said:
I'm curious, is there a way to do this in download mode (via Odin or otherwise)? As far as I know, I can only do that through recovery. Do I have to adb and wipe /cache?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
i do it thru recovery, thats always how it worked for me. You cant do it thru adb since you need root to do that and odin wipes root
okzygen said:
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
Click to expand...
Click to collapse
OK I installed the AOKP one and it works like a charm. Only thing is NFC doesn't work so once that works it will be pretty Much perfect
Sent from my SGH-I337 using Tapatalk 2
jasbur17 said:
I'm sad to say that I also wiped a phone with TWRP. It wasn't an S4 and I didn't need Kies.
I had no idea that it would delete the OS - I don't think there was even a warning.
Click to expand...
Click to collapse
Yeah me too, was and still am not happy about it. Should gave stuck to CWM. TWRP is a cool recovery, as long as you realize what you hit.
Glad Kies worked! Now that I have an Att phone I can utilize it again. Wouldn't recognize my International SGS3, so Kies was useless.
Sent from GT-I9505 transformed SGH-I337
Can someone point me the way to rooting this phone? I'm sorry just very confused, first Samsung phone I have had .. Thank you
Sent from my SCH-I535 using Tapatalk
You'll see it if you're looking closely. Best advice I can provide is: read, read, read and make sure you know what you're doing before you try it.
That's the thing.. I've rooted a droid bionic, droid RAZR, and a galaxy nexus.. But I have no idea how to root this
Sent from my SCH-I535 using Tapatalk
devildogmp said:
That's the thing.. I've rooted a droid bionic, droid RAZR, and a galaxy nexus.. But I have no idea how to root this
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Try the manual method
soul gaeaty
SlimSnoopOS said:
Try the manual method
Click to expand...
Click to collapse
Failed root and now phone wont even boot... please helpp
devildogmp said:
Failed root and now phone wont even boot... please helpp
Click to expand...
Click to collapse
At what step does it fail and what software were you on? Shouldn't be any issues up through JB 4.1.2.
SlimSnoopOS said:
At what step does it fail and what software were you on? Shouldn't be any issues up through JB 4.1.2.
Click to expand...
Click to collapse
4.1.2 The very first file im supposed to flash.. phone would never boot back up after that
I tried to root my sptint gs3 with chainfire and it passed in odin and rebooted with the red logo like in the video but I don't have root access and every time I try to ho into recovery mode it runs chainfire again but nothing happens? ?????????????????????????
devildogmp said:
4.1.2 The very first file im supposed to flash.. phone would never boot back up after that
Click to expand...
Click to collapse
So it flashed successfully in Odin? You don't boot back into your rom, you pull the battery then continue onto the next step after putting the phone back into Download mode.
dub913 said:
I tried to root my sptint gs3 with chainfire and it passed in odin and rebooted with the red logo like in the video but I don't have root access and every time I try to ho into recovery mode it runs chainfire again but nothing happens? ?????????????????????????
Click to expand...
Click to collapse
I was going to tell you to post in the Sprint S3 Q/A section, but I see you just made a thread. Good luck.
SlimSnoopOS said:
So it flashed successfully in Odin? You don't boot back into your rom, you pull the battery then continue onto the next step after putting the phone back into Download mode.
I was going to tell you to post in the Sprint S3 Q/A section, but I see you just made a thread. Good luck.
Click to expand...
Click to collapse
I mean the phone wont boot. pulled battery and all that but phone wont turn on, wont boot into recovery or downloading mode. nothing
devildogmp said:
I mean the phone wont boot. pulled battery and all that but phone wont turn on, wont boot into recovery or downloading mode. nothing
Click to expand...
Click to collapse
So you flashed the bootchain in PDA, waited for the tar file to flash, your S3 rebooted on its own and it would not boot back up? Or did something else happen? I've used that thread and many others as you can see in there with no issues.
Cuz unfortunately that sounds like a hard brick and there's two ways of recovering from that. The first way is doing this which requires you to have a class 10 sdcard that is the same size as your phone's internal storage. The other way is paying and shipping it off to a third party service like MobileTechVideos.
SlimSnoopOS said:
So you flashed the bootchain in PDA, waited for the tar file to flash, your S3 rebooted on its own and it would not boot back up? Or did something else happen? I've used that thread and many others as you can see in there with no issues.
Cuz unfortunately that sounds like a hard brick and there's two ways of recovering from that. The first way is doing this which requires you to have a class 10 sdcard that is the same size as your phone's internal storage. The other way is paying and shipping it off to a third party service like MobileTechVideos.
Click to expand...
Click to collapse
I gave up. I went to the store and bought a Galaxy Note 2. I won't be rooting any more phones any time soon..
SlimSnoopOS said:
So it flashed successfully in Odin? You don't boot back into your rom, you pull the battery then continue onto the next step after putting the phone back into Download mode.
I was going to tell you to post in the Sprint S3 Q/A section, but I see you just made a thread. Good luck.
Click to expand...
Click to collapse
Ok now when I try to use cwm it says can't mount can't mount can't open can't mount the it aborts ????
Use Odin to flash to stock then use casual to root/install recovery, ezz
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 08:54 PM ---------- Previous post was at 08:52 PM ----------
Darwin award
devildogmp said:
I gave up. I went to the store and bought a Galaxy Note 2. I won't be rooting any more phones any time soon..
Click to expand...
Click to collapse
Sent from my SCH-I535 using xda app-developers app