Related
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Dr. Light said:
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Click to expand...
Click to collapse
first of all you can't flash anything on a stock recovery hence the need of a custom recovery. Second you don't accept the OTA when rooted as it can cause the exact issue that you have. Last there isn't a way to fix your problem via another android device that I know of.
U are going to need a pc and then u will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery. Then you can access your backups.
Always_Jonezen said:
U will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery.
Click to expand...
Click to collapse
He doesn't have access to his PC PLUS he already knows what to do on that end.
jmxc23 said:
He doesn't have access to his PC PLUS he already knows what to do on that end.
Click to expand...
Click to collapse
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Thanks for all of advice guys. I'll prob just wait it out till Monday. Thanks again.
Always_Jonezen said:
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Click to expand...
Click to collapse
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
jmxc23 said:
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
Click to expand...
Click to collapse
hey all, I've been reading , downloading etc for hours trying to get back into my GS3.. i was as usual roaming around and saw a post that said something to this effect "do ya need to get back to stock?" and figured yes i need to so i jumped in with both feet ..i had my boot loader unlocked and for some reason locked the darned thing remembering it was locked before i rooted and then i get the screen that says ie: "System software not authorized ~~~~~~~~~~~~" with a yellow triangle over it with an "!" mark in it..
all would have been ok except the line up of the way to do things was kinda outta line.. after i had locked bootloader "which is the way the GS3 came" i thought. at any rate i am now where i said i was and if i can be helped it would be appreciated.. and no repeated.. next time i'll read their whole line up first.. so help me if ya can and i am game right now for about anything ..
Hi everyone. After scouring the forums here for hours, multiple failed attempts, and tons of misery; I've finally successfully rooted my T-Mobile G2 on 4.4.2.
As many are finding, people who have bought their G2 recently are having colorful lines whenever you try to turn on your screen when on KitKat Roms. This method fixes that (with this ROM only).
This is for people who are currently running the latest firmware (D80120A_00). I assume it'll also work with newer updates, but I can't make any promises.
---
As we've all seen, IORoot does not work on 4.4.2 on Tmobile devices for some reason. To get around that, we need to downgrade our devices to stock firmware. We will be following hyelton's guide, and lrwjr1964's discovery.
--Downgrade to 4.2.2--
First, navigate to hyelton's guide. Download the 4.2.2 stock firmware, from his link. On his Storage Cow site, navigate to the TMobile G2 folder, and then download the D80120C_00.kdz file. This is our stock firmware that we will be flashing to our device. You will also need to navigate to the link to the R&D Flash tool. The file is the LGMOBILEAX file. Install the LG Mobile Support tool. Launch the tool.
Next, we will be using lrwjr1964's discovery (post 2902 in the same thread). Plug in your phone, install any drivers needed, and let it get connected. Once you're all good to go, click 'options' in the top right hand corner, and then 'upgrade recovery'. What this will do, is download the latest D80120A_00.kdz file, and install it to your phone. How the program works, is it downloads the file to your computer, then transfers the file and flashes it. What we are going to do, is interrupt that process, insert our .kdz, and let it flash for us. Pretty nifty, huh?
You'll want to watch it super closely as it downloads. As soon as it finishes, yank the usb out of your phone. (I've done this twice without consequence. I don't make any guarantees, though.) This interrupts the file transfer, and throws you an error screen. Navigate to the folder "C:\ProgramData\LGMOBILEAX' . ProgramData is a hidden folder, so you'll need to make hidden folders visible. Rename your D80120C file exactly to what the file name of the other file is. Then, copy it over. Once it's finished, replug in your phone, let it connect, and let it resume the process. When it finishes, your phone will be running 4.2.2. How sweet is that?
--Root 4.2.2--
Now, this should work just as you're used to if you've done this before. Autoprime explains how to do this really well, so take a look at his thread here
--Install TWRP--
Again, if you've done this before, you're right at home. If not, WACOMalt has a thread you should check out here Make sure you download the correct .img for your phone. The Tmobile one. There's many different methods of flashing TWRP, but using the app Flashify worked easiest for me. It's on the Google Play store, and makes flashing it a cinch.
--Install KitKat and Re-Root--
This is one step you want to be careful with. Mess this one up, and you could be back at page one. SmiLey497 has the stock rom here. Ensure you not only snag the rom itself but get the SU file in the 'attached files' section.
Copy both files onto your phone, and boot to TWRP. You can do this easily from within the Flashify app.
Within TWRP, you need to do a standard wipe. After that, flash the ROM file first, and then the SU file after. DO NOT reboot your phone in between the files. If you do, you'll have just flashed the rom you had two hours ago when you began, and still not have SU. Once you do have them both flashed, reboot your phone and you're done.
--Celebration--
Congrats!! Your phone should now be running 4.4.2, and you should have root access. Go have some fun. Watch some Community, go for a jog, take a nap, eat dinner...do something FUN! You've earned it.
-----
I hope this guide is helpful. It very possibly could not work for you, or even mess up your phone. As far as I know, only myself and lrwjr1964 has used this method. I have very limited developing knowledge, so I likely won't be able to help with any too technical problems. Still, I'll be around to help as I can.
If this works for you, comment to let others know.
The best of luck!
utesred
Exactly what I was looking for! I ended up on the G2 when my wife decided she didn't like it and I was waiting on the M8 to switch us from VZW to T-Mobile. She put it on KK in the few days she had it. I've always had HTCs and know my way around them quite well. This will go a long ways towards helping do the same on LG.
Sent from my LG-D801 using XDA Premium 4 mobile app
LOBBS said:
Exactly what I was looking for! I ended up on the G2 when my wife decided she didn't like it and I was waiting on the M8 to switch us from VZW to T-Mobile. She put it on KK in the few days she had it. I've always had HTCs and know my way around them quite well. This will go a long ways towards helping do the same on LG.
Sent from my LG-D801 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I hope it works out for you. I was looking at the M8 myself, but decided to go for the G2 last week. The battery combined with the cost was more than enough to sway me. I was surprised at how rough it was to root myself, coming from an HTC sensation and having rooted a Samsung Note 10.1 2014.
Let us know when you go for it, and how it goes for you.
utesred said:
I hope it works out for you. I was looking at the M8 myself, but decided to go for the G2 last week. The battery combined with the cost was more than enough to sway me. I was surprised at how rough it was to root myself, coming from an HTC sensation and having rooted a Samsung Note 10.1 2014.
Let us know when you go for it, and how it goes for you.
Click to expand...
Click to collapse
I'm loving the G2 so far. It was my back-up choice in case there was something I really didn't like about the M8 so I'm not exactly suffering here. My ultimate goal is to get on an AOSP ROM so I really just need to get back to JB so that I can get root and recovery.
Sent from my LG-D801 using XDA Premium 4 mobile app
Thank you sooo much! Just what the doctor ordered!
---------- Post added at 10:25 PM ---------- Previous post was at 09:54 PM ----------
18.4009 said:
Thank you sooo much! Just what the doctor ordered!
Click to expand...
Click to collapse
Dang it. Tried you method to the letter but it fails at 49% on the LG and 47% on the pc. once I reboot and factory reset it boots back into kitkat 4.4.2
18.4009 said:
Thank you sooo much! Just what the doctor ordered!
---------- Post added at 10:25 PM ---------- Previous post was at 09:54 PM ----------
Dang it. Tried you method to the letter but it fails at 49% on the LG and 47% on the pc. once I reboot and factory reset it boots back into kitkat 4.4.2
Click to expand...
Click to collapse
Damn, that's a bummer! I'm assuming that it's failing while flashing the .kdz, right?
Sorry I can't be of much help on this one. Only thing I could suggest is to try it again. Maybe something went wrong? Make sure you've got the correct files and everything. You probably already know all of that, though.
I hope it works for you the second time around...or at least, the IORoot gets updated to work with our devices soon.
Yeah something has changed since my flash to stock kitkat. When I attempt to boot into recovery it isn't there (that's why ioroot25 won't work) but anyways. I think for one reason or another I am stuck...But that being said I work 12 hour night shifts and its my last night off with nothing to do.. So will attempt this again in a few different scenarios.
Hello guys, for rooting back from 4.4.2 to 4.2.2 on a Tmobile d801, do you use the d80110c_00 kdz or the d80110g_00 kdz ? I am not sure what the differences are either.
deepac said:
Hello guys, for rooting back from 4.4.2 to 4.2.2 on a Tmobile d801, do you use the d80110c_00 kdz or the d80110g_00 kdz ? I am not sure what the differences are either.
Click to expand...
Click to collapse
I used the 'C' .kdz file.
The 'G' one is another update. It is still 4.2.2, I believe.
Use d80110c
deepac said:
Hello guys, for rooting back from 4.4.2 to 4.2.2 on a Tmobile d801, do you use the d80110c_00 kdz or the d80110g_00 kdz ? I am not sure what the differences are either.
Click to expand...
Click to collapse
To avoid issues, you must use the D80110C .kdz. Users reported screen artifacts (lines) when using D80110G.
missiveusa said:
To avoid issues, you must use the D80110C .kdz. Users reported screen artifacts (lines) when using D80110G.
Click to expand...
Click to collapse
I may be wrong, but I don't think that the screen artifacts are caused by the D80110G. Using the same process, I went to the 80110C and tried flashing various roms afterwards. I got the artifacts on every other rom, except for the KK stock rom I used above.
From what I've seen and read from other users with the artifacts, they appear only on KK roms, with certain TMobile G2s. It seems that all phones that came with 80110G or 80110A preinstalled have issues.
Of course...I could be completely mistaken. That's just what I've noticed.
Give it time, root will happen for KitKat on T-Mobile.
I hope so, I spent all day yesterday trying until I just gave up. Guess its the waiting game for me.
For anyone having trouble downgrading using the KDZ method, just use the TOT method instead. It works perfect.
2strokenut said:
For anyone having trouble downgrading using the KDZ method, just use the TOT method instead. It works perfect.
Click to expand...
Click to collapse
Can you please direct me toward a tutorial that has the TOT method? I tried to find one online but was not able to. I have a D801. The KDZ method doesn't work for me.
I've tried your method, replaced the file it was loaded onto phone and the phone is now stock in boot load. It displays T-mobile icon and keeps resetting itself.
The biggest issue I have had in this whole downgrade, root, twrp, flash, is loosing twrp. I have tried multiple ways, but every single time I upgrade to 4.4.2 I lose custom recovery.
I even flashed twrp 2.7.0.0 over 2.3.6.2, but I have had no luck.
I have yet to try Flashify, but that will be my next move. I am Loki'd out lol
Help
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
utesred said:
Hi everyone. After scouring the forums here for hours, multiple failed attempts, and tons of misery; I've finally successfully rooted my T-Mobile G2 on 4.4.2.
As many are finding, people who have bought their G2 recently are having colorful lines whenever you try to turn on your screen when on KitKat Roms. This method fixes that (with this ROM only).
This is for people who are currently running the latest firmware (D80120A_00). I assume it'll also work with newer updates, but I can't make any promises.
---
As we've all seen, IORoot does not work on 4.4.2 on Tmobile devices for some reason. To get around that, we need to downgrade our devices to stock firmware. We will be following hyelton's guide, and lrwjr1964's discovery.
--Downgrade to 4.2.2--
First, navigate to hyelton's guide. Download the 4.2.2 stock firmware, from his link. On his Storage Cow site, navigate to the TMobile G2 folder, and then download the D80120C_00.kdz file. This is our stock firmware that we will be flashing to our device. You will also need to navigate to the link to the R&D Flash tool. The file is the LGMOBILEAX file. Install the LG Mobile Support tool. Launch the tool.
Next, we will be using lrwjr1964's discovery (post 2902 in the same thread). Plug in your phone, install any drivers needed, and let it get connected. Once you're all good to go, click 'options' in the top right hand corner, and then 'upgrade recovery'. What this will do, is download the latest D80120A_00.kdz file, and install it to your phone. How the program works, is it downloads the file to your computer, then transfers the file and flashes it. What we are going to do, is interrupt that process, insert our .kdz, and let it flash for us. Pretty nifty, huh?
You'll want to watch it super closely as it downloads. As soon as it finishes, yank the usb out of your phone. (I've done this twice without consequence. I don't make any guarantees, though.) This interrupts the file transfer, and throws you an error screen. Navigate to the folder "C:\ProgramData\LGMOBILEAX' . ProgramData is a hidden folder, so you'll need to make hidden folders visible. Rename your D80120C file exactly to what the file name of the other file is. Then, copy it over. Once it's finished, replug in your phone, let it connect, and let it resume the process. When it finishes, your phone will be running 4.2.2. How sweet is that?
--Root 4.2.2--
Now, this should work just as you're used to if you've done this before. Autoprime explains how to do this really well, so take a look at his thread here
--Install TWRP--
Again, if you've done this before, you're right at home. If not, WACOMalt has a thread you should check out here Make sure you download the correct .img for your phone. The Tmobile one. There's many different methods of flashing TWRP, but using the app Flashify worked easiest for me. It's on the Google Play store, and makes flashing it a cinch.
--Install KitKat and Re-Root--
This is one step you want to be careful with. Mess this one up, and you could be back at page one. SmiLey497 has the stock rom here. Ensure you not only snag the rom itself but get the SU file in the 'attached files' section.
Copy both files onto your phone, and boot to TWRP. You can do this easily from within the Flashify app.
Within TWRP, you need to do a standard wipe. After that, flash the ROM file first, and then the SU file after. DO NOT reboot your phone in between the files. If you do, you'll have just flashed the rom you had two hours ago when you began, and still not have SU. Once you do have them both flashed, reboot your phone and you're done.
--Celebration--
Congrats!! Your phone should now be running 4.4.2, and you should have root access. Go have some fun. Watch some Community, go for a jog, take a nap, eat dinner...do something FUN! You've earned it.
-----
I hope this guide is helpful. It very possibly could not work for you, or even mess up your phone. As far as I know, only myself and lrwjr1964 has used this method. I have very limited developing knowledge, so I likely won't be able to help with any too technical problems. Still, I'll be around to help as I can.
If this works for you, comment to let others know.
The best of luck!
utesred
Click to expand...
Click to collapse
The problem I think I am having, is in the Flashing TWRP guide, the t-mobile version, even though it states ver 2.6.3.3, its actually 2.6.3.2. I can not get TWRP to stick for the life of me.
---------- Post added at 03:48 PM ---------- Previous post was at 03:41 PM ----------
tpaxadpom said:
I've tried your method, replaced the file it was loaded onto phone and the phone is now stock in boot load. It displays T-mobile icon and keeps resetting itself.
Click to expand...
Click to collapse
hold the power button down until the screen goes blank, then press and hold the power and volume rocker down. when the LG logo appears release both buttons and quickly press and hold both power and volume rocker down. This will allow a factory (hard reset) and will get you out of the boot loop.
frigginmike said:
hold the power button down until the screen goes blank, then press and hold the power and volume rocker down. when the LG logo appears release both buttons and quickly press and hold both power and volume rocker down. This will allow a factory (hard reset) and will get you out of the boot loop.
Click to expand...
Click to collapse
I've tried your method but it doesn't work. Thanks for suggestion though. I had to put the phone in download mode (volume button down and then plug the usb), then I used LGLauncher.exe to recover it. I have tried the method described by OP twice. Both times I ended up with t-mobile logo played in the infinite loop.
I've renamed t-mobile USA D80110C_00.kdz to D80120A_00.kdz and overwritten the file. In the original instructions it says D80120C_00.kdz file but I believe OP meant D80110C_00.kdz as D80120C_00.kdz is not available at the posted link.
tpaxadpom said:
I've tried your method but it doesn't work. Thanks for suggestion though. I had to put the phone in download mode (volume button down and then plug the usb), then I used LGLauncher.exe to recover it. I have tried the method described by OP twice. Both times I ended up with t-mobile logo playe in the infinity loop.
I've renamed t-mobile USA D80110C_00.kdz to D80120A_00.kdz and overwritten the file. In the original instructions it says D80120C_00.kdz file but I believe OP meant D80110C_00.kdz as D80120C_00.kdz is not available at the posted link.
Click to expand...
Click to collapse
its sort of tricky due to the weird button placement, but that method works, 100%. May have to do it multiple times. I only know this, because I have returned to stock on this device about 25 times trying to get TWRP and root to stick when upgrading to KitKat. lol
frigginmike said:
its sort of tricky due to the weird button placement, but that method works, 100%. May have to do it multiple times. I only know this, because I have returned to stock on this device about 25 times trying to get TWRP and root to stick when upgrading to KitKat. lol
Click to expand...
Click to collapse
So I've looked on the related thread post 2901 (not 2902 as it says in OP), the reset is required. I've tried your method to reset and also one mentioned here but the phone continues to stay in the boot loop. This LG G2 is a PITA to get rooted.
Never mind. You are right. I've tried again your method and it worked. Performing reset now...
Before I go on to give tutorial, I want to see how many people actually use this phone and if it's common enough for me to give the tutorial. I've noticed many people have tried to flash this phone and always end up bricking it or doing something wrong. I have successfully flashed it, no brick and everything working. I would love to give tutorial, but before I do so I must see how many actually need it. :good:
Jbeat69 said:
Before I go on to give tutorial, I want to see how many people actually use this phone and if it's common enough for me to give the tutorial. I've noticed many people have tried to flash this phone and always end up bricking it or doing something wrong. I have successfully flashed it, no brick and everything working. I would love to give tutorial, but before I do so I must see how many actually need it. :good:
Click to expand...
Click to collapse
Let me first say thank you bcuz I'm just trying to get my boys phone updated from jb an he's got the st version but I can't find a recovery anywhere, so I'd u could even just inform me on where to get the recovery I'd be good lol
soupysoup said:
Let me first say thank you bcuz I'm just trying to get my boys phone updated from jb an he's got the st version but I can't find a recovery anywhere, so I'd u could even just inform me on where to get the recovery I'd be good lol
Click to expand...
Click to collapse
Your Welcome, and I want to apologize for not answering right away i'm still trying to get xda setup on my phone. I have school most of the day and will only be available at nights. But you say you only want recovery? Download an app called ez-recovery for VZW Galaxy S3 on the play store. Yes this is the Verzion Galaxy S3 Variant but it works for this device because of where it uses uses Verizon towers. Then once you download the app, open it up and flash the clockworkmod recovery, not the touch or twrp. Let me know your results You might come across some failed to mount SD card errors in the recovery menu. If you do it doesn't take a lot to fix..
I've been looking for this for some time now
Jbeat69 said:
Your Welcome, and I want to apologize for not answering right away i'm still trying to get xda setup on my phone. I have school most of the day and will only be available at nights. But you say you only want recovery? Download an app called ez-recovery for VZW Galaxy S3 on the play store. Yes this is the Verzion Galaxy S3 Variant but it works for this device because of where it uses uses Verizon towers. Then once you download the app, open it up and flash the clockworkmod recovery, not the touch or twrp. Let me know your results You might come across some failed to mount SD card errors in the recovery menu. If you do it doesn't take a lot to fix..
Click to expand...
Click to collapse
I've managed to gain root and flash recovery for verizon sch-i535. would just like to know if that's correct and also need flash image and I also still looking for a compatible ROM. I've been to scared to download and install one.
Very interested!!
Jbeat69 said:
Before I go on to give tutorial, I want to see how many people actually use this phone and if it's common enough for me to give the tutorial. I've noticed many people have tried to flash this phone and always end up bricking it or doing something wrong. I have successfully flashed it, no brick and everything working. I would love to give tutorial, but before I do so I must see how many actually need it. :good:
Click to expand...
Click to collapse
I have been driving myself crazy trying to find this information. I would be very grateful to you for the information on flashing the firmware and upgrading to KitKat 4.4 on the SCH S968C. It's impossible to get the info from ST or Samsuck.
Thanks
dijjay said:
I have been driving myself crazy trying to find this information. I would be very grateful to you for the information on flashing the firmware and upgrading to KitKat 4.4 on the SCH S968C. It's impossible to get the info from ST or Samsuck.
Thanks
Click to expand...
Click to collapse
here for the latest roms and fixes for this device
http://forum.xda-developers.com/showthread.php?t=2516498&page=30
Sent from my SCH-S968C using Tapatalk
Jbeat69 said:
Before I go on to give tutorial, I want to see how many people actually use this phone and if it's common enough for me to give the tutorial. I've noticed many people have tried to flash this phone and always end up bricking it or doing something wrong. I have successfully flashed it, no brick and everything working. I would love to give tutorial, but before I do so I must see how many actually need it. :good:
Click to expand...
Click to collapse
i use this model and have been surfing these forums for some links to the stock rom since samsung doesn't provide it on their website. I was going to try to flash it back to stock but to be honest i have no idea what im doing and could use all the help i can get.
I've looked all over and watched and listened and read, and other than using oneclickroot to root my sch-968c, I'm too apprehensive on doing anything else before I know better. It's using 4.1.2 jellybean and theres a few things that I'd like my phone to be able to do considering its cost. I want to get KitKat 4.4 on my Galaxy s3. Samsung doesn't offer support, Straight Talk doesn't offer support. I understand its up to me to make this happen but I'd appreciate any help! Thanks!!
edit: So I havent used oneclickroot yet, I needed to download a samsung driver. I did use odin to flash a rom onto my device properly, but I'm pretty sure all i did was put exactly what I had on before it. Maybe I need to look for a custom rom, but I have a hard time finding the right sources. I need to look for a custom rom for sch-s968c with 4.4 kitkat? Need someone to tell me otherwise...
sch s-968c update os , help please
GS3 SCH S-968c its h2, I am trying to update the os to at least 4.4 so I can download an app that currently is'nt compatible with the 4.1.2 jellybean, for my husband. I just rooted it, using odin, first time messing with a phones insides...intimidating but I figured it out. lots of bad information for this phone...can anyone please help me figure out how and where to go to download the update for th os? thank you so much!
this would be awesome
Jbeat69 said:
Before I go on to give tutorial, I want to see how many people actually use this phone and if it's common enough for me to give the tutorial. I've noticed many people have tried to flash this phone and always end up bricking it or doing something wrong. I have successfully flashed it, no brick and everything working. I would love to give tutorial, but before I do so I must see how many actually need it. :good:
Click to expand...
Click to collapse
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
GS3 SCH S-968c its h2, I am trying to update the os to at least 4.4 so I can download an app that currently is'nt compatible with the 4.1.2 jellybean, for my husband. I just rooted it, using odin, first time messing with a phones insides...intimidating but I figured it out. lots of bad information for this phone...can anyone please help me figure out how and where to go to download the update for th os? thank you so much!
Droidriven said:
here for the latest roms and fixes for this device
http://forum.xda-developers.com/showthread.php?t=2516498&page=30
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
dijjay said:
I have been driving myself crazy trying to find this information. I would be very grateful to you for the information on flashing the firmware and upgrading to KitKat 4.4 on the SCH S968C. It's impossible to get the info from ST or Samsuck.
Thanks
Click to expand...
Click to collapse
Hi, Did you ever find the rom? I rooted my phone successfully, after much ado with tedious searching all night...any info would be appreciated. thank you!
saucyredhead said:
GS3 SCH S-968c its h2, I am trying to update the os to at least 4.4 so I can download an app that currently is'nt compatible with the 4.1.2 jellybean, for my husband. I just rooted it, using odin, first time messing with a phones insides...intimidating but I figured it out. lots of bad information for this phone...can anyone please help me figure out how and where to go to download the update for th os? thank you so much!
this would be awesome
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
GS3 SCH S-968c its h2, I am trying to update the os to at least 4.4 so I can download an app that currently is'nt compatible with the 4.1.2 jellybean, for my husband. I just rooted it, using odin, first time messing with a phones insides...intimidating but I figured it out. lots of bad information for this phone...can anyone please help me figure out how and where to go to download the update for th os? thank you so much!
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
Hi, Did you ever find the rom? I rooted my phone successfully, after much ado with tedious searching all night...any info would be appreciated. thank you!
Click to expand...
Click to collapse
Most of the ROMS from 4.4 and newer require using a SIM and some extra setup to get mobile data(3G) and stock MMS(photo/audio/video messages) working.
Fortunately for you I have a copy of a CM11 4.4 Kit Kat ROM that doesn't require a SIM for mobile data(3G) to work, the only down side is that you can't use the stock MMS app, you'd have to use some kind of 3rd party texting app such as GoSMS or Textra or Chomps or a similar app.
If you want to have working stock MMS then you'll need a CDMA SIM card.
A GSM SIM will not work. A SIM from AT&T/T-mobile or any network under them won't work, neither will the AT&T/T-mobile SIMs from the Straight Talk BYOP activation package, it has to be CDMA.
I can help you painlessly get the SIM set up and APNs configured correctly so that MMS works. Any CDMA Verizon 4G/LTE(you'll need a previously activated SIM if you use a Verizon SIM, it won't work if it's a never been activated SIM from Verizon) or a Tracfone CDMA SIM will work, or any of Tracfone's subsidiary networks (Total Wireless/Net10/Straight Talk/etc..)
As for ROMs, I suggest one of the following:
1) the d2vzw CM11 4.4 that I have a copy of along with a SIM(you'll have working stock MMS and won't need anything extra) it's a rock solid ROM with the SIM setup correctly and uses less battery than the newer ROMs.
2) d2vzw OctOS 5.1.1 if you can find it, it will need a SIM also to have working mobile data and stock MMS.
3) d2vzw OctOS 6.1.1 if you can find it, needs SIM also.
As for there being bad information out there about this device. I've been posting accurate information about this model number for 3 years or more. I've posted information about this model all over the internet. It is all accurate and works, some information is old and no longer necessary due to processes and methods changing but it isn't "bad" information. The old information can still be used, it just involves more steps and has been simplified over time due to improvements in development for this device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Need to upgrade to at least Android 4.2
"Fortunately for you I have a copy of a CM11 4.4 Kit Kat ROM that doesn't require a SIM for mobile data(3G) to work, the only down side is that you can't use the stock MMS app, you'd have to use some kind of 3rd party texting app such as GoSMS or Textra or Chomps or a similar app."
Can you help me? You seem to be very knowledgeable about this phone. My husband just bought a new Galaxy and he gave his old S3 to our seven year old grandson who is one of those kids who loves and understands all things electronic. He has been craving an Android device for some time now. (He already has an iPod touch).
My husband returned the phone to factory settings today and I brought it over to a very excited grandson. My daughter said she was going to use her gmail account to set up the phone and then create an additional account from her account that she could use parental controls on. Alas, this feature only works if you have at least version 4.2 or higher, and this Straight Talk Model S968C has version 4.1.2
This phone will not be connected to a cellular service, just wifi. He doesn't need to be able to send or receive MMS or even texts. He mostly wants to create videos and and download and use some of his favorite apps from Google Play, and use the web (with restrictions that my daughter will set. It won't help to create a separate Gmail account for him because setting restrictions will still not be possible due to the Android Version.
Is there a relatively easy way to do this? I've never done anything like this to a phone before but I'm pretty tech literate and understand most of the terms.
Thank you very much for any help you can provide to me.
Lesa
lirn44 said:
"Fortunately for you I have a copy of a CM11 4.4 Kit Kat ROM that doesn't require a SIM for mobile data(3G) to work, the only down side is that you can't use the stock MMS app, you'd have to use some kind of 3rd party texting app such as GoSMS or Textra or Chomps or a similar app."
Can you help me? You seem to be very knowledgeable about this phone. My husband just bought a new Galaxy and he gave his old S3 to our seven year old grandson who is one of those kids who loves and understands all things electronic. He has been craving an Android device for some time now. (He already has an iPod touch).
My husband returned the phone to factory settings today and I brought it over to a very excited grandson. My daughter said she was going to use her gmail account to set up the phone and then create an additional account from her account that she could use parental controls on. Alas, this feature only works if you have at least version 4.2 or higher, and this Straight Talk Model S968C has version 4.1.2
This phone will not be connected to a cellular service, just wifi. He doesn't need to be able to send or receive MMS or even texts. He mostly wants to create videos and and download and use some of his favorite apps from Google Play, and use the web (with restrictions that my daughter will set. It won't help to create a separate Gmail account for him because setting restrictions will still not be possible due to the Android Version.
Is there a relatively easy way to do this? I've never done anything like this to a phone before but I'm pretty tech literate and understand most of the terms.
Thank you very much for any help you can provide to me.
Lesa
Click to expand...
Click to collapse
Go to settings>about>build number, tell me if it has H1 or H2 on the end of that number.
If you have H1 I can make it very easy for you with just a couple of apps, a good internet connection and about 30-45 minutes.
If you have H2 you'll need a PC, about 1.5 hours and a good USB cord.
Or you can skip all of that and just go straight for the PC method, it works on H1 and H2. You'll probably need to get familiar with the tool that is involved in the process so that you'll know how to restore the device if there are issues later on. The device will be rooted(stock devices do not ship with root access), root means the system partition has been "unlocked" to write permissions, which means the daughter/grandson could inadvertently delete the wrong thing and render the device inoperable.
Of course, you could also remove root from the device, then he wouldn't be able to modify the system partition, he could install and modify/customize everything else though. But that can, in some cases, also cause issues, which then requires flashing the stock firmware via PC or using custom recovery to restore a backup or reinstall your ROM.
This device has the potential to do many things, there are a lot of custom 4.4 and newer operating systems for this device, each with their own flavors of UI and features. If you're not going to have the device activated on a network then you can probably use any of the 4.4+ ROMs without the SIM, probably all the way up to the newest 7.1 or newer builds. Maybe even the new Android Oreo 8.0+ if they build it for this device, someone probably will, the OctOS team still builds new ROMs weekly for this device. If he likes Pokemon Go you might have issues with it seeing that the device is rooted or you might have GPS issues on this device. They can be solved in most cases though.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Upgrading s3
The build number ends in H1.
I wouldn't want it to be easy for him to accidentally render it inoperable.
I have a good internet connection and the time to do this, if you can take me step by step through it. I'm a visual learner, I learn very well from watching videos of people doing things, so I really need clear step by step written instructions. Do you have the time to help me? That would be SO great!
And if it's just as easy to install a more up to date version of the OS, of course I'd rather do that! (and my grandson would be thrilled!)
Thank you so much!
Droidriven said:
Go to settings>about>build number, tell me if it has H1 or H2 on the end of that number.
If you have H1 I can make it very easy for you with just a couple of apps, a good internet connection and about 30-45 minutes.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
---------- Post added at 03:23 AM ---------- Previous post was at 03:17 AM ----------
He probably doesn't care about Pokemon Go. he likes to create his own emojis, make videos with visual and sound effects, use graphics programs, stuff like that. Also loves music and likes to download apps to create his own music. The more photography and graphics stuff he can do the happier he'll be.
I just want him to be able to use it and he can't without the parental restrictions in place. Whatever you recommend, I'll try.
It's H1, cool. You'll be amazed how easy this is. You'll be doing all of this, except downloading your ROM and Google apps, directly from the device.
Use PC to download these files then connect the S3 to PC and copy them to external SD card.
1) download this file, it's the last release of Octos 6.0.1 marshmallow(there is also 7.1.1 available but I haven't used it so I can't verify stability), it's a very good ROM, I used it for over a year on this device, store it on an external SD card as a file by itself, not in a folder.
https://basketbuild.com/filedl/devs...lease/d2vzw/OCT-M-R3-6.0.1-20161025-d2vzw.zip
2) Go to http://opengapps.org/, select:
ARM
6.0
Micro
Then click the red download circle. This is the Gapps(the stock Google apps) package that you need to flash with the ROM, they are flashed separately because they can't be included in the ROM file. Place this file on the SD card with the ROM file, as a file by itself, not in a folder.
Now, on the device:
1) Go to system settings>security> unknown sources and enable it (it will prompt you warning that it can be dangerous to install apps from unknown sources, you only need it to install the Towelroot app to root on the device).
Also, go to system settings>about>build number, tap it repeatedly until you see the message saying you are a developer, this unlocks developer options, go back to system settings>developer options>USB debugging and enable it.
2) using the devices mobile browser, go to https://towelroot.com/ and tap the big red lambda symbol to download the Towelroot app. (you might get a warning about the site being dangerous, don't worry, this is because Google sees the Towelroot app as a virus because it can be used to modify your system partition which is actually what you want, you will be removing root when you're done but right now you need it)
3) Drag down the notification in status bar for the app that you downloaded, tap on it and install the app, once installed, open it, tap the "make it rain" button, you'll be rooted in about 10 seconds, you can uninstall the Towelroot app now, it isn't needed anymore.
4) Go to PlayStore and search for "SuperSU", install it, open it, it will ask you to update binaries, when it asks which method, choose "normal", reboot the device if it doesn't do it automatically. (if you get a prompt asking you to grant superuser permission while doing this, grant it, this is what allows you to write to /system)
5) when the device reboots, go to PlayStore, search for "TWRP Manager", install it, open it(grant superuser permission if prompted at any time while using TWRP Manager)
Now you're ready to follow my guide, starting from the ***FLASHING WITH TWRP MANAGER*** section.
When you get TWRP installed, skip to the ***BACKING UP YOUR STOCK ROM** section and continue from there, you can ignore all the stuff about SIM and APNs. I recommend doing a clean install of your ROM, coming from stock to custom ROM usually causes a bootloop, clean install avoids this. After you get your backup created, read the troubleshooting section in post #2 of my guide, it explains how to perform a clean install, just make absolutely sure that you create your stock backup before you do it. You will be wiping the operating system and everything on the device out before installing the new ROM, don't worry, everything is still safe in the backup you created. This is similar to wiping a PC and reinstalling Windows, the device won't boot without OS so you must flash the new ROM before trying to reboot the device. Sounds scary but it's really simple.
https://forum.xda-developers.com/ga...de-to-flashsetup-sim-apn-cm-cm-based-t3351290
After you get the device signed in with Google, you can go ahead and remove root permission from the device. To do this, open the SuperSU app, open its app settings menu, find the option to "cleanup for unroot and uninstall", it will remove root. Reboot the device and you should be done. You're ready to setup for the grandson.
Just make sure you charge the battery to full before you start flashing the ROM and Gapps, if the battery dies before it is finished, it will damage the device and it's a headache to fix yourself.
If you have questions I'm here.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Thank you!
Thanks so much. I have cleared the rest of my afternoon to attempt this.
---------- Post added at 06:21 PM ---------- Previous post was at 06:06 PM ----------
Did I mention this S3 is from Straight Talk? When I look at a list of supported devices for TWRP, it doesn't list ST as one of the S3s supported. Just want to make sure before I start.
lirn44 said:
Thanks so much. I have cleared the rest of my afternoon to attempt this.
---------- Post added at 06:21 PM ---------- Previous post was at 06:06 PM ----------
Did I mention this S3 is from Straight Talk? When I look at a list of supported devices for TWRP, it doesn't list ST as one of the S3s supported. Just want to make sure before I start.
Click to expand...
Click to collapse
The Verizon S3 d2vzw and the Straight Talk S3 d2tfnvzw are the same device, they use the same TWRP and ROMs. That is all explained in the guide that I created, starting from the top of the thread. My guide has pretty much everything you need to know about this device as far as what you can flash, how to flash it and how to get it set up correctly.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Guide
---------- Post added at 09:09 PM ---------- Previous post was at 08:23 PM ----------
I'm having a little trouble with downloading towelroot to the phone. Found the link/lambda symbol fine. When I tap it to download and swipe down the notifications, it just shows that it's in progress. This went on for about ten minutes before I canceled it and tried again. It's now been about three minutes and it's doing the same thing. I have a very fast internet connection with Xfinity so it's not that. Just keep canceling and trying? (I even tried holding down the lambda symbol and saving the link--same problem). The phone is fully charged. I have unknown sources checked and also USB debugging.
ADDENDUM: I've tried this a few times now. I tried using Chrome to see if that would help--it didn't. The download is in progress for about ten minutes, then says download failed no matter what browser. I've double and triple checked all the settings are correct.
Is it possible to download it to my laptop and transfer it to the phone?
ADDENDUM: finally got it!
Thanks.
Sorry to have so many questions! I appreciate your help.
flashing recovery
Got to the point of using TWRP Manager. Selected device ( Verizon S3 d2vzw) and it downloaded the file and asked if I wanted to flash the recovery and said please make sure the bootloader is unlocked. (I didn't see that in the guide but will go back and look again). I said yes. I got an error message:
Something went wrong
flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occurred. Would you like to attempt rebooting to recovery now?
I'm just going to leave the phone on until I get your opinion of how I should answer that question. Reboot or no?
Thank you!
lirn44 said:
Got to the point of using TWRP Manager. Selected device ( Verizon S3 d2vzw) and it downloaded the file and asked if I wanted to flash the recovery and said please make sure the bootloader is unlocked. (I didn't see that in the guide but will go back and look again). I said yes. I got an error message:
Something went wrong
flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occurred. Would you like to attempt rebooting to recovery now?
I'm just going to leave the phone on until I get your opinion of how I should answer that question. Reboot or no?
Thank you!
Click to expand...
Click to collapse
I've never had issues using TWRP manager.
Are you sure that you have rooted the device before trying TWRP manager? There is an option in TWRP manager that will show you the "installed recovery" that you have currently on the device, it should tell you whether you have stock recovery or custom. Don't reboot until you're certain that it has flashed the recovery. If it did something wrong before, it might not reboot, slight chance but possible. Still fixable if it doesn't, just more junk to do to get there.
Can you find the folder that TWRP manager downloaded the recovery.img file to? If so, you can install the Flashify app from Playstore, also linked in my guide. Then use it to flash the recovery.img from the folder that TWRP manager downloaded it to. I mention in my guide to use Flashify if you have issues using TWRP Manager.
This should be a simple process, I've done this many times. Since you're having issues, I'd rather have some form of faster communication. Do you know how to use Google hangouts? If you have Firefox on PC you can install the hangouts add-on in Firefox, then I can text in real time to make this much simpler to walk you through. I can send you a PM here with my Gmail address, use it to find me in hangouts and start a conversation thread.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
THANK YOU!
Well, all these hours later, with your amazing patience, I have Android 6.0.1 running on my old Galaxy S3 from Straight Talk!
I can't thank you enough! My grandson is going to be ecstatic!
Thank you again for spending so much time taking me through it step by step!
I have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.
I bought this in New Zealand from Spark. I assume it is locked?
Is the bootloader locked?
I couldnt find the matching build on Chainfire, Can this particular model be rooted?
Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.
I can't even find the original stock rom.
Is rooting not similar to jailbreaking in the way it is done?
My specs:
Model: SM-G920I
Android: 5.0.2
Build: LRX22G.G920IDVU1AOD1
Thank you in advance.
AAANNNDDDYYY said:
I have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.
I bought this in New Zealand from Spark. I assume it is locked?
Is the bootloader locked?
I couldnt find the matching build on Chainfire, Can this particular model be rooted?
Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.
I can't even find the original stock rom.
Is rooting not similar to jailbreaking in the way it is done?
My specs:
Model: SM-G920I
Android: 5.0.2
Build: LRX22G.G920IDVU1AOD1
Thank you in advance.
Click to expand...
Click to collapse
I have the SM-G920I and it's rooted.
Rooting the G920I is apparently not as straightforward as others but still possible.
I had to flash TWRP via Odin, then flash the [BETA][2015.04.28] SuperSU v2.49 package via recovery.
Details when I get back from work, or some kind soul decides to help.
There is a stock image thread and a few stock roms floating around. Request / search lower down in that thread
Thanks, is it better to reset the s6 before rooting? For a clean root?
And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?
AAANNNDDDYYY said:
Thanks, is it better to reset the s6 before rooting? For a clean root?
And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?
Click to expand...
Click to collapse
Here is my experience, a fellow kiwi on Spark (with a 2D branded phone). I too have the 920I running on A0D1 via OTA.
It is unlikely Spark firmwares have locked bootloaders.
So long as you can get to download mode (holding volume down, home and the power button for up to 10 seconds), you can bring your phone back to life if something goes wrong . You will want a copy of Spark's firmware handy before you start, you can get it from here . Just in case.
Use the USB cable that come with your phone and make sure you have the drivers installed.
Any ways, first I flashed TWRP via Odin (through download mode Andy), flash was successful, however booting into recovery hung my phone. Managed to get back to download mode from there and flashed CF-Root for 920I. Boot loop.
Back to download mode and flashed CF-Root for 920F. Success, rooted and booted. Andy, if all you are looking for is root, avoiding the TWRP flash may work and going straight to CF-Root. Others have had issues with this, I'm not sure. I'd try the 920I first and if no good try the 920F. Again, as long as you can get to download mode, you can flash Sparks firmware through Odin to restore it to stock. Good luck and remember, attempting any of this WILL trip KNOX. If your using this as a company phone, you will run into issues. Can't imagine we will see Samsung pay any time soon in NZ.
For those interested in TWRP, after the root was obtained, my recovery was still busted. I flashed the TWRP image via Flashify and now I have also have TWRP. Good times.
Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.
This tutorial the way to go?
youtube.com/watch?v=BW5P8zqkFpY
AAANNNDDDYYY said:
Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.
This tutorial the way to go?
youtube.com/watch?v=BW5P8zqkFpY
Click to expand...
Click to collapse
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Yes the G920I listed on Chainfires site is for the AOC6 build, but I am on the AOD1 build.
Another thing, should i factory reset before rooting?
AAANNNDDDYYY said:
Yes the G920I listed on Chainfires site is for the AOC6 build, but I am on the AOD1 build.
Another thing, should i factory reset before rooting?
Click to expand...
Click to collapse
Nah, don't bother. The process will retain all your settings and data too.
So just confirm that i can root my g920I with build AOD1 with this meathod?
---------- Post added at 05:45 PM ---------- Previous post was at 05:33 PM ----------
d0ce said:
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Click to expand...
Click to collapse
So just confirm that i can root my g920I with build AOD1 with this meathod?
d0ce said:
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Click to expand...
Click to collapse
So were you able to install TWRP?
CF Root works for me with 920I version, but flashing TWRP forces it not to boot past the Samsung Logo.
Likewise with flashing a custom kernel also forces it not to boot past the Samsung Logo
Im on the C4 Australia build.. thinking about trying to flash a later 920I build to see if it'll help
s3ct0r said:
So were you able to install TWRP?
CF Root works for me with 920I version, but flashing TWRP forces it not to boot past the Samsung Logo.
Likewise with flashing a custom kernel also forces it not to boot past the Samsung Logo
Im on the C4 Australia build.. thinking about trying to flash a later 920I build to see if it'll help
Click to expand...
Click to collapse
Did someone figure this out? I have the Sm-920i and I get stuck at the Samsung splash screen after flashing twrp! So I have to Odin the cf-auto-root... I've tried flashify also... It won't work... Stuck @ Galaxy S6 screen what gives is it the SM-920I OR ME? I have had many Galaxy phones in the past but this one is pissing me off
Kjc99 said:
Did someone figure this out? I have the Sm-920i and I get stuck at the Samsung splash screen after flashing twrp! So I have to Odin the cf-auto-root... I've tried flashify also... It won't work... Stuck @ Galaxy S6 screen what gives is it the SM-920I OR ME? I have had many Galaxy phones in the past but this one is pissing me off
Click to expand...
Click to collapse
Yeah flash the New Zealand 1D firmware and TWRP will work perfectly. But note that to get root, you will have to use cf-auto-root for the 920G Model
Best of luck
s3ct0r said:
Yeah flash the New Zealand 1D firmware and TWRP will work perfectly. But note that to get root, you will have to use cf-auto-root for the 920G Model
Best of luck
Click to expand...
Click to collapse
How come it has to be the New Zealand? I'm trying to backup my carriers crappy baked rom just in case I need to return... Is there anyway to back it up without a custom recovery but rooted? Because if I flash the new Zealand before making a backup and have to return they will see I have messed with the phone because they put a boot animation
Kjc99 said:
How come it has to be the New Zealand? I'm trying to backup my carriers crappy baked rom just in case I need to return... Is there anyway to back it up without a custom recovery but rooted? Because if I flash the new Zealand before making a backup and have to return they will see I have messed with the phone because they put a boot animation
Click to expand...
Click to collapse
Doesn't have to be the New Zealand one, I just used it since I'm in Australia. Any 920I firmware should work just make sure it's at least 1D. I only tried those firmwares, and always had success
My carrier is GCI wireless in Alaska, USA... No way to download there firmware...also is twrp it? No more cwm or philz recovery?
Sorry forgot to add current firmware pic
s3ct0r said:
Doesn't have to be the New Zealand one, I just used it since I'm in Australia. Any 920I firmware should work just make sure it's at least 1D. I only tried those firmwares, and always had success
Click to expand...
Click to collapse
Cool thanks for the info!
Update thank you @s3ct0r...worked on the 1st try.... Now I'm working on the deep sleep issue...
Kjc99 said:
Update thank you @s3ct0r...worked on the 1st try.... Now I'm working on the deep sleep issue...
Click to expand...
Click to collapse
Flash the ktoonsez Kernel, or the flashable zip from the Cf-AutoRoot topic
s3ct0r said:
Flash the ktoonsez Kernel, or the flashable zip from the Cf-AutoRoot topic
Click to expand...
Click to collapse
Is ktoonsez a stable kernel, I remember using it on my S4 but skipped it last year on my S5 because it had to many tweaks... Can I use it with a stock rom? Alliance?
I recently got my Samsung Galaxy S6 and decided to root and install TWRP for a custom rom. I was able to root the phone and then installed their android app. TWRP Manager (ROOT).
After that I went to the app and one of the sidebars labeled install TRWP on the app then to the codename zeroflte for the Samsung Galaxy S6. It told me to restart my phone and I did but after that I was not able to use my phone again. Whenever I would turn on my phone it would show the normal Samsung s6 screen with a unlock picture and the words custom underneath. After that it would display a turquoise color screen with a words
Start Up Failed. Your device didn’t start up successfully. Use the Verizon Software Repair Assistant on a computer to repair your device.
I tried to google and see if anyone had a similar problem but nothing popped up. I don’t know where to find a copy for the Verizon Software Repair Assistant for the Galaxy S6.
I also tried and factory reset the phone or anything but the only combinations of buttons that would work on my phone were the down volume + power button. It gave me a list of options including factory reset but every option that I chose would lead me back to the same screen. The turquoise screen saying Start Up Failed.
Any help would be great. I don’t know what to do now. Tomorrow I am going to down to a local repair store and see what they can do. But if you know of anything that would be great. Thank you for your time and have a nice day.
inolil said:
I recently got my Samsung Galaxy S6 and decided to root and install TWRP for a custom rom. I was able to root the phone and then installed their android app. TWRP Manager (ROOT).
After that I went to the app and one of the sidebars labeled install TRWP on the app then to the codename zeroflte for the Samsung Galaxy S6. It told me to restart my phone and I did but after that I was not able to use my phone again. Whenever I would turn on my phone it would show the normal Samsung s6 screen with a unlock picture and the words custom underneath. After that it would display a turquoise color screen with a words
Start Up Failed. Your device didn’t start up successfully. Use the Verizon Software Repair Assistant on a computer to repair your device.
I tried to google and see if anyone had a similar problem but nothing popped up. I don’t know where to find a copy for the Verizon Software Repair Assistant for the Galaxy S6.
I also tried and factory reset the phone or anything but the only combinations of buttons that would work on my phone were the down volume + power button. It gave me a list of options including factory reset but every option that I chose would lead me back to the same screen. The turquoise screen saying Start Up Failed.
Any help would be great. I don’t know what to do now. Tomorrow I am going to down to a local repair store and see what they can do. But if you know of anything that would be great. Thank you for your time and have a nice day.
Click to expand...
Click to collapse
Have you tried to Odin back to stock?
http://forum.xda-developers.com/verizon-galaxy-s6/development/5-15-stock-odin-tar-t3109676
Ya, you'll need to odin back to stock like he said. And TWRP isn't available for our phone since we don't have an unlocked bootloader. Do not try and install TWRP again. You'll want to use Flashfire if you need to flash anything.
brholt6 said:
Ya, you'll need to odin back to stock like he said. And TWRP isn't available for our phone since we don't have an unlocked bootloader. Do not try and install TWRP again. You'll want to use Flashfire if you need to flash anything.
Click to expand...
Click to collapse
Awesome thank you
I need help!
I did the exact same thing with my Galaxy s6, i tried to do the same thing with my newly acquired root, I am very new but very interested in rooting and customizing my phone, when I plug my phone into a computer it only pops up with the start up failed screen, I installed the odin thing but i have no clue where to go from here and any assistance would be greatly appreciated. thank you
Bubblegum Mage said:
I did the exact same thing with my Galaxy s6, i tried to do the same thing with my newly acquired root, I am very new but very interested in rooting and customizing my phone, when I plug my phone into a computer it only pops up with the start up failed screen, I installed the odin thing but i have no clue where to go from here and any assistance would be greatly appreciated. thank you
Click to expand...
Click to collapse
Keep in mind XDA is a community for developers by developers. People are also willing to help, but you got to put forth your own effort. You will get ignored if you think people on this site are going to act as free tech support. Your question is posted just a few posts down from a link to the process on using odin to return to stock. You need to just follow those instructions. If you don't understand a step then Google it. I'm saying this because I noticed you joined XDA to ask this question. Or at least it's your first post. You will make a lot of enemies here if you don't take the time to read and research things before posting.
HELP
I have the same problem (Start up failed) but ODIN is not working for me... I am using the stock firmware for the GS6 edge and it says failed... what should I do?
Bee Funny said:
I have the same problem (Start up failed) but ODIN is not working for me... I am using the stock firmware for the GS6 edge and it says failed... what should I do?
Click to expand...
Click to collapse
If you have an edge you should use their forum. It's different than the GS6.
Just had to Odin my Verizon S6 (sm-g920v) to get it back to factory defaults.
I've been rooted for months with no issues and have known my bootloader was locked with no nice way around it but then i read some stupid guides saying to go get twrp manager to load custom roms on the Galaxy s6 phones and they even included the sm-g920v model number. I went to the app store, downloaded twrp manager, followed the first few steps, rebooted and that was that. Could not boot up anymore without Start Up Failed. A few checks and warning would have been greatly appreciated from the app developers but oh well.
Well that was fun. Now to redo everything on my phone.
Oooah said:
Just had to Odin my Verizon S6 (sm-g920v) to get it back to factory defaults.
I've been rooted for months with no issues and have known my bootloader was locked with no nice way around it but then i read some stupid guides saying to go get twrp manager to load custom roms on the Galaxy s6 phones and they even included the sm-g920v model number. I went to the app store, downloaded twrp manager, followed the first few steps, rebooted and that was that. Could not boot up anymore without Start Up Failed. A few checks and warning would have been greatly appreciated from the app developers but oh well.
Well that was fun. Now to redo everything on my phone.
Click to expand...
Click to collapse
Same exact crap just happened to me. I was running CleanRom Lite....thought I could use TWRP...some times I do stupid things...should have just stuck with FlashFire.
I've tried odin back to stock, it keeps failing. it says nand write fail and it stops. I've tried many different times. I've run Odin 3.10.6 and 3.10.7 I have the latest drivers, it recognizes the device but it will not load anything via odin. I've tried on two different computers as well.
...
Gizmoe said:
...
Click to expand...
Click to collapse
I have a Galaxy s6 edge btw. Not much info on the edge, in desperation, I'm combing thru galaxy s6 forums seeking answers. I have been rooted for awhile. I wanted to turn off the nagging volume warning so I downloaded a zip file to flash but only to find that my twrp recovery was no longer there. So I try to download twrp and flash. Now I'm in a boot loop with the turquoise screen telling me to use a verzion tool to reset the device. Klies says my phone isn't compatible as well as smart switch. Odin fails every time after NAND WRITE. I'm about to microwave this crap and get new phone.
keith7120 said:
I have a Galaxy s6 edge btw. Not much info on the edge, in desperation, I'm combing thru galaxy s6 forums seeking answers. I have been rooted for awhile. I wanted to turn off the nagging volume warning so I downloaded a zip file to flash but only to find that my twrp recovery was no longer there. So I try to download twrp and flash. Now I'm in a boot loop with the turquoise screen telling me to use a verzion tool to reset the device. Klies says my phone isn't compatible as well as smart switch. Odin fails every time after NAND WRITE. I'm about to microwave this crap and get new phone.
Click to expand...
Click to collapse
Did you ever get your phone up and running? I ran into similar issue with odin. After looking around on web I found a forum that mentioned using an older version of odin.
---------- Post added at 06:50 PM ---------- Previous post was at 06:44 PM ----------
Fe Mike said:
Did you ever get your phone up and running? I ran into similar issue with odin. After looking around on web I found a forum that mentioned using an older version of odin.
Click to expand...
Click to collapse
Sorry I saw you tried other odin versions 3. 10.x, I meant going lower. 3.09 is recommended for jb/kk but that worked for me.