Related
So you've just gotten/inherited an I-777 and you need to get rid of the 2 year old UI and OS ASAP, but all the other guide threads are just as old and filled with old info, what to do?
DISCLAIMER: I am not responsible for phone bricks and the like. You follow this information at your own risk. This is just information I'm writing down as I update my wife's old bone stock phone
BACKUP your data from both cards, you are likely to lose the internal SD data in this operation
Let's get started:
Root the phone:
Go here: Framaroot.
Download the .apk, and put it on your phone.
Be sure to 1. Have install from unknown sources on. 2. Enable USB debugging.
Install the .apk and run it.
Choose SuperSU and then click on Aragorn (should automatically be detected).
Reboot the phone (power cycle is probably the only option in stock).
Congrats! You're now rooted!
Install a kernel
Go here: Mobile Odin.
Grab two apks; Mobile Odin Lite and the Flash kernel for i-777. (Flash kernel is many posts down from the top)
Extract the .apk from the Flash kernel .zip file, and plop both .apks on your phone.
Install the .apks
Go here: ShoStock and click on the 'older kernels + a tar version'
Download the .tar
Plop the .tar on your phone
EDIT: At this point you may want to also grab a rom and any other files you may need if you only have the internal sd available because you'll lose USB mount access past this point. So go ahead and transfer those files to the phone.
Open Mobile Odin Lite and select the .tar file
Flash it, the device will instantly reboot after flash.
The device won't fully boot now, but don't worry! Hold down POWER, VOL UP and VOL DOWN until the phone cycles and the logo appears, then let go of the buttons and you should be in CWM recovery which came with the jeboo kernel you flashed.
Install a ROM
You will have to wipe/factory reset first from the CWM menus.
Flash your rom, regardless, follow the instructions in the OP of the ROM thread you're interested in.
I flashed ShoStock first since it's likely more like an OTA update to bring partitions up to date before flashing anything else.
Be sure to hit THANKS on the posts you visit from this guide.
Nice to see an updated guide.
For your fifth step of Kernel install, you lead users to a jeboo kernel, which is great if they plan to go ShoStock. I believe that the Jeboo kernel is a mic swap kernel, and may not be suitable for other very popular and common ROMS for the I777 (any AOSP or stock samsung, or COOKED).
Therefore I suggest adding such a note, and providing a link to at least one of the Siyah(based) Kernels.
These are available in several versions, and in .tar or .img format; both of which can be flashed via mobile ODIN (extract the .zip, flash the boot.img)
if flashing to an ICS Rom:SiyahKernel S2-v5.0.1
If flashing to a JB Rom: AJK BOSS (newest available)
Edit: props to @othermark for compiling this simple updated means to root & rom on the i777
cyril279 said:
Nice to see an updated guide.
For your fifth step of Kernel install, you lead users to a jeboo kernel, which is great if they plan to go ShoStock. I believe that the Jeboo kernel is a mic swap kernel, and may not be suitable for other very popular and common ROMS for the I777 (any AOSP or stock samsung, or COOKED).
Click to expand...
Click to collapse
Most, if not all, roms here will come with the appropriate kernel which will be flashed during the ROM install. They would have to reflash the jeboo kernel to get something incompatible. This is just to get them something that 1. has CWM and 2. is a .tar they can flash with Mobile Odin Lite.
That said, sometimes you have to flash a compatible kernel before you flash a particular ROM.
othermark said:
...This is just to get them something that 1. has CWM and 2. is a .tar they can flash with Mobile Odin Lite...
Click to expand...
Click to collapse
Mobile Odin Lite (and Pro) will recognize and flash a zImage. So one can pull the zImage from any CWM flashable zip and use it.
cyril279 said:
Nice to see an updated guide.
For your fifth step of Kernel install, you lead users to a jeboo kernel, which is great if they plan to go ShoStock. I believe that the Jeboo kernel is a mic swap kernel, and may not be suitable for other very popular and common ROMS for the I777 (any AOSP or stock samsung, or COOKED).
Therefore I suggest adding such a note, and providing a link to at least one of the Siyah(based) Kernels.
These are available in several versions, and in .tar or .img format; both of which can be flashed via mobile ODIN (extract the .zip, flash the boot.img)
if flashing to an ICS Rom:SiyahKernel S2-v5.0.1
If flashing to a JB Rom: AJK BOSS (newest available)
Edit: props to @othermark for compiling this simple updated means to root & rom on the i777
Click to expand...
Click to collapse
So if i wanted to Do Cyanogen Mod(10.2), would it be okay to use the jeboo tar? Or should i download AJK, unzip it, and install the boot.img instead of the jeboo .tar?
TreatnHerRight said:
So if i wanted to Do Cyanogen Mod(10.2), would it be okay to use the jeboo tar? Or should i download AJK, unzip it, and install the boot.img instead of the jeboo .tar?
Click to expand...
Click to collapse
It should not matter which version of CWM recovery you use, so Jebo will be fine. When you install it, your system may not boot up, but just turn the phone off, then use the button combination for recovery mode.
Edit: boot.img is a partition file that Mobile Odin will recognize, the same as zImage, so you can use it to install AJK if you prefer. Again, it shouldn't matter which one you use.
TreatnHerRight said:
So if i wanted to Do Cyanogen Mod(10.2), would it be okay to use the jeboo tar? Or should i download AJK, unzip it, and install the boot.img instead of the jeboo .tar?
Click to expand...
Click to collapse
I can't vouch for the jeboo approach, but I expect that it works.
I did use this guide with the latest ajk-extracted boot.IMG as you describe, and it works as well.
Fyi: If you're using mobile Odin pro, you don't need the i777- kernel download, the pro version does it for you.
9. Open Mobile Odin Lite and select the .tar file
What do i click at this point(To Flash the .tar)? I opened Mobile ODIN Lite, now do i click Kernel, System, Data, Cache...., or Open file...?
Just wanna make sure.
Also:
cyril279 said:
I can't vouch for the jeboo approach, but I expect that it works.
I did use this guide with the latest ajk-extracted boot.IMG as you describe, and it works as well.
Fyi: If you're using mobile Odin pro, you don't need the i777- kernel download, the pro version does it for you.
Click to expand...
Click to collapse
To Do The Boot.IMG Which Would i click?
Select [kernel], navigate to and select the boot.img.
Then scroll down to the bottom of mobile Odin and select [flash firmware]
cyril279 said:
Select [kernel], navigate to and select the boot.img.
Then scroll down to the bottom of mobile Odin and select [flash firmware]
Click to expand...
Click to collapse
Used This Guide, Followed Everything Until the .tar File, i Instead flashed the AJK boot.IMG file. It Successfully Brought up CMW Recovery. When Attempting to Flash Cyanogen Mod or Paranoid Android I Got Error Status 7 (getprop("ro.product.device") == "SGH-I777 || getprop("ro.build.product") == "SGH-I777") Same Error for Both.
Steps i took to Fix.
Opened Unzipped Cyanogen Mod.
Open Build.prop and Rename SGH-I777 to i777 In those Two Spots (ro.build.product and ro.product.device)
Opened Updater-Script and Removed the First 2(or 3) Lines Referencing the SGH-i777
Then Re zipped them using this method - [UltimateGUIDE][How-to]Create your Own Custom ROM an easy way
Flashed in Recovery and it Successfully Worked. (Tested it With the Cyanogen Mod Zip Only, Got Error Previously With Both CM and PA Zips)
Me Attempting To Help Anyone Else In This Situation.
nice, do you guys know if it's possible to use this phone without a data plan on att? i recently upgraded my phone and wanted to give this one to my dad, he can use it to watch youtube videos and videochat with my grandmother via wifi at home, there was a thread i read on how to unlock the phone and it had an option for network lock, is that what i need to do? any help is very much appreciated
baoweezie said:
nice, do you guys know if it's possible to use this phone without a data plan on att? i recently upgraded my phone and wanted to give this one to my dad, he can use it to watch youtube videos and videochat with my grandmother via wifi at home, there was a thread i read on how to unlock the phone and it had an option for network lock, is that what i need to do? any help is very much appreciated
Click to expand...
Click to collapse
I don't really understand... You simply take the Sim card out and put the thing in airplane mode.
I did that with mine and the battery lasts a week. BTW you can turn on WiFi while in airplane mode. You can also uncheck "use data" in the mobile network settings.
There's nothing complicated to do.
Sent from my Nexus 4 using xda app-developers app
Yes I know about airplane mode but im trying to have him use this phone as a actual phone that can make calls but didn't want att to tack on an additional data plan to it because he never uses any data while out and about. Basically I want to use this phone on my dads line without having to add a monthly data plan.
He was using a T-Mobile phone that I unlocked for him before and they didn't add the data plan on cause att doesn't recognise T-Mobile imei, I could be wrong but if I can change something in the phones build prop to make it seem like a non att branded phone, would it not be detected as a smartphone and not trigger the data add on?
Sent from my SGH-I337 using xda app-developers app
baoweezie said:
nice, do you guys know if it's possible to use this phone without a data plan on att? i recently upgraded my phone and wanted to give this one to my dad, he can use it to watch youtube videos and videochat with my grandmother via wifi at home, there was a thread i read on how to unlock the phone and it had an option for network lock, is that what i need to do? any help is very much appreciated
Click to expand...
Click to collapse
This question, and it's resulting discussion are better suited in a separate thread. That helps to both get you views and answers that are more focused on your issue, as well as keeping this [GUIDE] thread clean and on-topic.
-Cyril
Nevermind, I figured it out.
The key combo to get into my recovery is Vol Up + Vol Down + Power
Is not clear for me in conclusion how obtain CWM in the i777 rooted??
pepe100 said:
Is not clear for me in conclusion how obtain CWM in the i777 rooted??
Click to expand...
Click to collapse
This has been answered for you already, several times. CWM is included in our kernels - you DO NOT flash it separately. Just pick a kernel that matches the android version you're on (ICS, JB etc.), flash it and it'll install CWM for you!
Sent from the i777
OK bro thanks for your concrete answer.
Sent from my SGH-I777 using xda app-developers app
i cant find the 'older kernels + a tar version' in shos thread .. pls help me !
nathan_42594 said:
i cant find the 'older kernels + a tar version' in shos thread .. pls help me !
Click to expand...
Click to collapse
It's in post #3.
jeboo said:
** OLD VERSION DOWNLOADS INCLUDING A TAR VERSION **
Code:
http://d-h.st/users/jeboo/?fld_id=9729
In a bind and need a tar version, just extract zImage from the zip and do: tar -H ustar -c zImage >> jeboo_kernel.tar
Click to expand...
Click to collapse
★ [N900V] [KitKat] [NC2 Firmware/Bootloader] [NC4 Modem/Recovery] [Boot Loop Fix] ★
This is a part of JasmineROM. It fixes the boot loop issue when entering (rebooting to) recovery on NC2 and upgrades the modem and recovery to NC4. Sure, by flashing this file in Odin, you can still roll back to Jelly Bean MJE with all the benefits of the leaked NC2 kernel.
An updated/unified version & instructions can be found here!
Thanks to:
@BeansTown106
@Hashcode
I'm going to be without a laptop for a week. Anyone try this that can leave some feedback? Thank you!
<Note3>
Fixing to try on the nc2 bootloader. running hyperdrive kk. Curious as to what I should wipe tho...... or if I just flash via odin
LeftyGR said:
I'm going to be without a laptop for a week. Anyone try this that can leave some feedback? Thank you!
<Note3>
Click to expand...
Click to collapse
I confirm that this works better than the NC2 modem––for me. The firmware file provided by @BeansTown106 doesn't include NC2 recovery, and that's why entering recovery fails resulting in a boot loop. You can fix the boot loop issue by just flashing the NC2 recovery. However, the linked file here includes upgraded NC4 recovery and modem together with the NC2 firmware/bootloader.
The only issue I had when flashing the NC4 modem is incorrect lockscreen PIN code. So, you may need to set the lockscreen to "swipe" before flashing and change it later. At any time, you can roll back to the NC2 package by flashing @BeansTown106 firmware file. You can also roll back to JB MJE if you wish––or for root/disaster recovery.
Anyway, I tried this several times before posting. I'm a developer in another field, but I wanted to say thanks to the great XDA community by posting something useful (it's my 1st post).
DdronD4L said:
Fixing to try on the nc2 bootloader. running hyperdrive kk. Curious as to what I should wipe tho...... or if I just flash via odin
Click to expand...
Click to collapse
Unset any lockscreen PIN/pattern, reboot to Download Mode, flash via Odin3, reboot to SafeStrap, wipe cache/dalvik, reboot to system, set your lockscreen security, and enjoy!
So this is basically like flashing the stripped nc4 modem .tar from the kitkat release? Im on ricks kitkat rom so this wouldn't affect anything else (only give me the newest radio) . The new recovery doesn't really improve anything since we are using safe strap correct?
Sent from my SM-N900V using Tapatalk
sfld said:
So this is basically like flashing the stripped nc4 modem .tar from the kitkat release? Im on ricks kitkat rom so this wouldn't affect anything else (only give me the newest radio) . The new recovery doesn't really improve anything since we are using safe strap correct?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Yes, but... The (new) recovery fixes the boot loop problem when accidentally rebooting to recovery from advanced power menu (for example). The NC2 firmware also gives the option of recovering from other boot loop problems. So, yes, its NC2 firmware/bootloader + NC4 modem + NC4 recovery in one file. You may not need it for now, if you've already flashed the new modem and NC2 recovery (not included in @BeansTown106 file), but it's still useful to have all of them in one small file that can be easily used for upgrading the modem and disaster recovery (e.g., rolling back to MJE for root before upgrading again to NC2).
sfld said:
So this is basically like flashing the stripped nc4 modem .tar from the kitkat release? Im on ricks kitkat rom so this wouldn't affect anything else (only give me the newest radio) . The new recovery doesn't really improve anything since we are using safe strap correct?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I don't think it will hurt anything. I flashed the NC4 modem without issue yesterday but not the one posted here.
Misterxtc said:
I don't think it will hurt anything. I flashed the NC4 modem without issue yesterday but not the one posted here.
Click to expand...
Click to collapse
Yes,it won't hurt anything. It'll upgrade the modem and fix the recovery boot loop issue. It also replaces the firmware file in @BeansTown106 post at http://forum.xda-developers.com/showthread.php?t=2726558.
hsbadr said:
Yes,it won't hurt anything. It'll upgrade the modem and fix the recovery boot loop issue. It also replaces the firmware file in @BeansTown106 post at http://forum.xda-developers.com/showthread.php?t=2726558.
Click to expand...
Click to collapse
Thank you for this. I would hit your thanks button but I used all my thanks up for the day. I wish XDA would allow more than 8 thanks per day.
Misterxtc said:
Thank you for this. I would hit your thanks button but I used all my thanks up for the day. I wish XDA would allow more than 8 thanks per day.
Click to expand...
Click to collapse
No problem! You're welcome.
I've also prepared files for rooted NC4 ROM + firmware, but I don't like to post them because NC4 bootloader is incremented. So, you can get fully rooted NC4 ROM, but at any major problem, you'll lose root and there's noway to roll back to MJE. Thanks to @Hashcode for the PSA at http://forum.xda-developers.com/showthread.php?t=2727876.
This is awesome. Thank you so much. Just installed this via Odin and let me tell you the NC4 modem is a huge upgrade over the NC2 one. Worth the few minutes to install just for that alone.
AngryManMLS said:
This is awesome. Thank you so much. Just installed this via Odin and let me tell you the NC4 modem is a huge upgrade over the NC2 one. Worth the few minutes to install just for that alone.
Click to expand...
Click to collapse
Great! Glad to help
Just for clarification
Thanks for the files! Just to be clear, what steps should I take if I'm already on the ROM that Beanstown posted? Just flash in Odin? That shouldn't wipe anything, correct?
RageSalamando said:
Thanks for the files! Just to be clear, what steps should I take if I'm already on the ROM that Beanstown posted? Just flash in Odin? That shouldn't wipe anything, correct?
Click to expand...
Click to collapse
Just flashing in Odin is enough, but it's recommended to unset any lockscreen security before flashing and wipe cache/dalvik then. Here's the recommended steps:
1. unset any lockscreen PIN/pattern
2. reboot to Download Mode
3. flash via Odin3
4. reboot to SafeStrap
5. wipe cache/dalvik
6. reboot to system
7. set your lockscreen security
This is recommended only if you installed Xposed modules and modified the lockscreen behaviour. Otherwise, just flash via Odin3!
is this pre-rooted?
Morlok8k said:
is this pre-rooted?
Click to expand...
Click to collapse
This isn't a ROM; it's just NC2 firmware/bootloader + NC4 modem/recovery. You need to be on the rooted NC2 to flash.
Morlok8k said:
is this pre-rooted?
Click to expand...
Click to collapse
lol.. a rooted radio...
kids these days
What would be the benefit of having the NC2 firmware over the NC4? I can understand the NC2 bootloader, but is there a difference with the firmware?
SirBindy said:
lol.. a rooted radio...
kids these days
Click to expand...
Click to collapse
hey, i just skimmed the original post, and thought it was a full-blown NC2 ROM with the NC4 radio, etc.
I am sorry if I am misunderstanding but if I'm on nc2 and flashed only the modem nc4 from Droid forums that means I can't roll back to mje?i haven't tried it and I haven't had issued just curious I'm happy where I am as I'm rooted still on nc2 with my mobile Hotspot and unlimited data so I couldn't be happier u just want to know if I'm going to have the option to roll back to me modem if I wanted to
I think I was reading this as the firmware not the radio sorry ignore my question long day at work and my brain is jello
Sent from my SM-N900V using XDA Free mobile app
I saw alot of people asking about these, so I've repacked the stock Modem, Bootloader, Kernel and Recovery from the full .tar separately as Odin flashable .tar's for anyone who needs them. And also created a recovery flashable stock kernel.
I've tested them all out and they work correctly for me, use at your own risk though. For G900T ONLY
Also, consider this: Warning flashing Bootloader/Modem/ FULL FIRMWARE LOLLIPOP
Flashable in Odin:
Bootloader/BL:
Bootloader
Bootloader Mirror
Phone/CP:
Modem
PDA/AP:
Kernel
Recovery
Full .tar thanks to @GSXeclipsePSI and SamMobile
Flashable in recovery(I used TWRP):
Stock Recovery Flashable .zip
Thanks so much for posting these. I upgraded modem, bootloader and kernel no problem.
Stock kernel seems to work better than the ktoonsez one (for me at least), but i don't think I can get SElinux to be permissive on the stock kernel (doesn't seem to stick when I use SElinux mode changer app), which in turn seems to mean I can't use Viper...so I flashed back ktoonsez kernel since I can't live without Viper
Any thoughts on what I may be doing wrong...I know this isn't a Viper thread, but I'm pretty sure I read over there that SElinux permissive was a must for Viper to work, so if stock kernel doesn't allow for that, then my next thought is it possible to have stock kernel that's SElinux permissive?
How did you guys install the stock kernel? I used odin, wiped cache, and all I get is the initial Galaxy S5 Power By Android logo and it never goes past this.
did you try pulling the battery before you start the phone up on download mode? I always have to do that first and the always works for me.
cyhamada said:
Thanks so much for posting these. I upgraded modem, bootloader and kernel no problem.
Stock kernel seems to work better than the ktoonsez one (for me at least), but i don't think I can get SElinux to be permissive on the stock kernel (doesn't seem to stick when I use SElinux mode changer app), which in turn seems to mean I can't use Viper...so I flashed back ktoonsez kernel since I can't live without Viper
Any thoughts on what I may be doing wrong...I know this isn't a Viper thread, but I'm pretty sure I read over there that SElinux permissive was a must for Viper to work, so if stock kernel doesn't allow for that, then my next thought is it possible to have stock kernel that's SElinux permissive?
Click to expand...
Click to collapse
I have the same problem, nothing sounds as good without Viper But i'm dealing with the stock kernel for now.
ALaz502 said:
How did you guys install the stock kernel? I used odin, wiped cache, and all I get is the initial Galaxy S5 Power By Android logo and it never goes past this.
Click to expand...
Click to collapse
As cyhamada says above, you sometimes have to pull the battery before going into Download mode. Also, try a different version of Odin. With Odin 3.09 flashing the full .tar results with my phone sitting on the boot logo.
Updated Bootloader/Modem, yet my Baseband hasn't changed from NK2, shouldn't it change to the OB1?
I'm running CM12, boots fine, LTE signal's been junk since upgrading to NK2 and was hoping this new modem would have some corrections. (Phoenix, AZ)
Paulenski said:
Updated Bootloader/Modem, yet my Baseband hasn't changed from NK2, shouldn't it change to the OB1?
I'm running CM12, boots fine, LTE signal's been junk since upgrading to NK2 and was hoping this new modem would have some corrections. (Phoenix, AZ)
Click to expand...
Click to collapse
You have to be on stock for it to stick, and sometimes it will take a couple tries of lashing it even then, usually the best way is to pull battery and then boot into download.
aaricchavez said:
You have to be on stock for it to stick, and sometimes it will take a couple tries of lashing it even then, usually the best way is to pull battery and then boot into download.
Click to expand...
Click to collapse
I actually got it to stick on cm12 after pulling battery.
spidey2483 said:
I actually got it to stick on cm12 after pulling battery.
Click to expand...
Click to collapse
Really? What i've always seen and experienced is that you have to be on stock, on previous updates I had to go to stock to get it to stick. I guess ymmv.
aaricchavez said:
Really? What i've always seen and experienced is that you have to be on stock, on previous updates I had to go to stock to get it to stick. I guess ymmv.
Click to expand...
Click to collapse
It stuck after I did a battery pull on the 3rd or 4th try, the blue "secure boot: enabled" appeared when it actually worked. I went from Recovery > Download, odin flashed, pulled battery, odin flashed and it worked.
bootloader went fine but modem causing me to hang on sammy screen and i cant seem to get past it no matter what i try.
tried kernel now im hung on GS5 screen. lol
aaricchavez said:
I saw alot of people asking about these, so I've repacked the stock Modem, Bootloader, Kernel and Recovery from the full .tar separately as Odin flashable .tar's for anyone who needs them. And also created a recovery flashable stock kernel.
I've tested them all out and they work correctly for me, use at your own risk though. For G900T ONLY
Also, consider this: Warning flashing Bootloader/Modem/ FULL FIRMWARE LOLLIPOP
Flashable in Odin:
Bootloader/BL:
Bootloader
Phone/CP:
Modem
PDA/AP:
Kernel
Recovery
Full .tar thanks to @GSXeclipsePSI and SamMobile
Flashable in recovery(I used TWRP):
Stock Recovery Flashable .zip
Click to expand...
Click to collapse
Bootloader link is not working for me can anyone provide working link? Thank you all in advance.
ledezma2003 said:
Bootloader link is not working for me can anyone provide working link? Thank you all in advance.
Click to expand...
Click to collapse
It looks like it's up from here. Here's a mirror though.
Bootloader Mirror
aaricchavez said:
It looks like it's up from here. Here's a mirror though.
Bootloader Mirror
Click to expand...
Click to collapse
Thank you this one worked.
is there a way to root if were on lolipop?
darren.wlsn1 said:
is there a way to root if were on lolipop?
Click to expand...
Click to collapse
Have you tried CF-Auto-Root? Next thing after that I would say install TWRP and exit, it will ask to root if it doesn't detect root.
aaricchavez said:
Have you tried CF-Auto-Root? Next thing after that I would say install TWRP and exit, it will ask to root if it doesn't detect root.
Click to expand...
Click to collapse
ya i got twrp on through cf but had to sideload in twrp but never got sideload to open but now in stuck on tmo screen and never been stuck there
darren.wlsn1 said:
ya i got twrp on through cf but had to sideload in twrp but never got sideload to open but now in stuck on tmo screen and never been stuck there
Click to expand...
Click to collapse
How long has it been on the boot animation? First boot/first clean boot(new kernel, etc.) for Lollipop takes a while to build ART.
aaricchavez said:
How long has it been on the boot animation? First boot/first clean boot(new kernel, etc.) for Lollipop takes a while to build ART.
Click to expand...
Click to collapse
any tar i flash now is hanging on tmo screen for as long as i let it sit, im at point i just want it vto boot no matter what build i use
bit the bullet and reset in stock recovery
darren.wlsn1 said:
any tar i flash now is hanging on tmo screen for as long as i let it sit, im at point i just want it vto boot no matter what build i use
Click to expand...
Click to collapse
Here's what I would do if I were in your situation. Grab the full OB1 .tar and Odin 3.07 along with TWRP. I would: Odin TWRP>Do a factory reset>Pull battery>Boot into Download mode>Flash OB1>Let it sit for about 20 min. If you have adb set up on your computer I would also do "adb logcat" to see what exactly is going on. Although I don't recall if it'll pickup after a factory reset, I just do it so often on mine I never pay attention.
If that failed I would Odin TWRP and grab one of the Lollipop roms and flash that.
i managed to get the OF6 sprint full rom file through kies.
this is only to be flashed using odin in the ap slot.
you will probably lose root and your custom recovery.
you may be able to root it and restore the data . That up to you to try.
This is the Sprint version Only!
here is the link: if someone wants to provide a mirror that would be appreciated.
Disabling 'Reactivation Lock' from 'Security' in the settings allowed me to root and add a custom recovery (TWRP).
your on your own from here!
https://onedrive.live.com/redir?resid=CD08CE789EB6B040!1155&authkey=!AIOZNh5nLeYDbcs&ithint=file,md5
here is another link thats a zipped MD5.tar file. this must be unzipped before putting the file into odin ap slot . (thanks to itskapil for the link)
http://www.theandroidsoul.com/download/download-sprint-galaxy-s5-android-5-0-2-update-odin-tar-file/
It's always great to have a TAR file on PC. Thanks!
But btw, this is Android 5.0 update, right? Have read on android blogs that OF6 has been 5.1 update for T-Mobile Galaxy S6 sets. So..
Okay, it's 5.0.2. Brings Reactivation lock.
itskapil said:
It's always great to have a TAR file on PC. Thanks!
But btw, this is Android 5.0 update, right? Have read on android blogs that OF6 has been 5.1 update for T-Mobile Galaxy S6 sets. So..
Okay, it's 5.0.2. Brings Reactivation lock.
Click to expand...
Click to collapse
Yes it's still 5.0
Sprint GS5 Moars 6.2
Any special features or affects on this update? Thanks for taking the time doing this for us
Sent from my SM-G900P using XDA Free mobile app
Son Rise said:
Any special features or affects on this update? Thanks for taking the time doing this for us
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
this
http://support.sprint.com/support/a...pdateTheSoftwareVersionOnYourSamsungGalaxy#!/
First is this a necessary update? Second does one have to update to OD3 first before doing the update. I'm still on OA6
Cmicasa the Great XvX said:
First is this a necessary update? Second does one have to update to OD3 first before doing the update. I'm still on OA6
Click to expand...
Click to collapse
no you dont have to update and no it isnt necessary. but if you are on stock OA6 I would take to guess that this rom is 5 months newer with improvements in alot of areas. they claim its for factory reset protection (so someone cant steal your phone and just factory reset it and it theirs now) and for reactivation protection (same thing so noone can reactivate the phone and make it theirs)
if i was on straight stock i would update. if i was on a stock rooted i would either try and root it or wait for someone to root the tar file and make it flashable through recovery.
thats my take on it.
cool... thanks. I like the security features, but at the same time I may wait till the new Moar comes out to do the work.
Is there a new radio and modem version with this update?
BrickedHouse said:
Is there a new radio and modem version with this update?
Click to expand...
Click to collapse
yes its the full rom, modem, and firmware
Robalboa said:
yes its the full rom, modem, and firmware
Click to expand...
Click to collapse
Thank you for this and by chance has anyone seen a firmware/modem update only for OF6 yet?
Edit: Found! Thanks tdunham - https://www.androidfilehost.com/?w=files&flid=21717
I was just gonna show you that. Lol
Sprint GS5 Moars 6.2
Has anyone successfully loaded a custom recovery and possibly one of the available OA6 ROMs after updating to this full tar?
I know there are separate modem and firmware files, but I was just curious if anyone has tried to go there from full stock.
DurhamHusker said:
Has anyone successfully loaded a custom recovery and possibly one of the available OA6 ROMs after updating to this full tar?
I know there are separate modem and firmware files, but I was just curious if anyone has tried to go there from full stock.
Click to expand...
Click to collapse
Yes. In fact, I did a full rom install, with nand erase all (after a bad flash), and I still went back to OA6 and OD3 stock deodexed roms.
Flashing TWRP from Odin works fine after flashing OF6 or OD3. I also used the CF one click root method, and that also worked for me.
Everything I did was in Odin 3.10.6.
Chainfires auto root makes odin complains about the recovery and shows 'fuse>3', which (I assume) means I've already burnt thru three of the 400+ fuses in the phone (kernel, recovery and probably rooting). I've tried odin 3.10.6 and the version that comes with chainfires auto root. Towelroot v3 says my phone isn't supported, even when using the command mod options.
I'll boot back into Windowz and try this a few more times. I don't see/know how joshdv rooted his phone...
edit: let's add insult to injury. I can't downgrade the firmware/OS to OA6, says it fails OS version.
joshdv said:
Yes. In fact, I did a full rom install, with nand erase all (after a bad flash), and I still went back to OA6 and OD3 stock deodexed roms.
Flashing TWRP from Odin works fine after flashing OF6 or OD3. I also used the CF one click root method, and that also worked for me.
Everything I did was in Odin 3.10.6.
Click to expand...
Click to collapse
@joshdv
Maybe it would help if you posted the link to the autoroot tar and any special steps you took to get it working.
Buddlespit said:
Chainfires auto root makes odin complains about the recovery and shows 'fuse>3', which (I assume) means I've already burnt thru three of the 400+ fuses in the phone (kernel, recovery and probably rooting). I've tried odin 3.10.6 and the version that comes with chainfires auto root. Towelroot v3 says my phone isn't supported, even when using the command mod options.
I'll boot back into Windowz and try this a few more times. I don't see/know how joshdv rooted his phone...
edit: let's add insult to injury. I can't downgrade the firmware/OS to OA6, says it fails OS version.
Click to expand...
Click to collapse
Yes, you're stuck on the newer firmware now.
tdunham said:
Yes, you're stuck on the newer firmware now.
Click to expand...
Click to collapse
Ya, before I flashed this, I knew I was probably stuck with OF6 and that there currently wasn't a reliable method to get root. Now, it's a waiting game to see if someone comes up with a method/hack to root this. GooooOOOOO CHAINFIRE!!!
Buddlespit said:
Ya, before I flashed this, I knew I was probably stuck with OF6 and that there currently wasn't a reliable method to get root. Now, it's a waiting game to see if someone comes up with a method/hack to root this. GooooOOOOO CHAINFIRE!!!
Click to expand...
Click to collapse
Depends how long you're willing to wait and if you want to keep the warranty bit untripped.
If it doesn't matter, you can still flash custom recovery in odin and any one of the pre-rooted custom or stock roms that will run on the lollipop bootloader.
I got root by just installing custom recovery and flashing super su. zip
Sent from my SM-G900P using Tapatalk
lascoul said:
I got root by just installing custom recovery and flashing super su. zip
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Link for Super user zip???
I have a Galaxy S6 SM-G920V rooted using PingPongRoot years ago. I've never updated the phone, so it's still on Android 5.0.2.
Recently it's been having battery indicator issues: thinks it's charging when it's not and vice versa. I replaced the battery and even the charging port (having to remove the screen and all that). Still no luck.
After backing up everything with Titanium backup, what are my options? I can't even perform a factory reset, since the phone gets stuck in a boot loop until I remove the battery. Will flashing the ROM using traditional methods (ODIN) even work with a Verizon phone? Is there a newer version of Android for this phone that still has root? (Nougat?) Without root, I probably can't reset everything I backed up with Titanium Backup.
Any advice would be greatly appreciated. Thanks.
shanebelcroft said:
I have a Galaxy S6 SM-G920V rooted using PingPongRoot years ago. I've never updated the phone, so it's still on Android 5.0.2.
Recently it's been having battery indicator issues: thinks it's charging when it's not and vice versa. I replaced the battery and even the charging port (having to remove the screen and all that). Still no luck.
After backing up everything with Titanium backup, what are my options? I can't even perform a factory reset, since the phone gets stuck in a boot loop until I remove the battery. Will flashing the ROM using traditional methods (ODIN) even work with a Verizon phone? Is there a newer version of Android for this phone that still has root? (Nougat?) Without root, I probably can't reset everything I backed up with Titanium Backup.
Any advice would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Google search:
"Return to stock (your specific model number)"
That will find what you need in order to reflash your stock firmware.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Google search:
"Return to stock (your specific model number)"
That will find what you need in order to reflash your stock firmware.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
If I reflash to stock, would my only option for root still be to just apply PingPongRoot again? Does root exist for a newer version of Android for a SM-G920V? or only other models like SM-G920F?
Thanks.
shanebelcroft said:
If I reflash to stock, would my only option for root still be to just apply PingPongRoot again? Does root exist for a newer version of Android for a SM-G920V? or only other models like SM-G920F?
Thanks.
Click to expand...
Click to collapse
If you flash the same firmware as what you had when you rooted your device, you will still be able to root using the same rooting method that you used the first time. If you flash a firmware that is newer than what you had, your rooting method may not work.
Flash your firmware then root with PingPongroot like you did before.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
If you flash the same firmware as what you had when you rooted your device, you will still be able to root using the same rooting method that you used the first time. If you flash a firmware that is newer than what you had, your rooting method may not work.
Flash your firmware then root with PingPongroot like you did before.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
With Odin I was able to flash a stock OE2 ROM (everything passed) following this guide: https://forum.xda-developers.com/verizon-galaxy-s6/verizon-s6-stock-restore-files-t3096000, but now the phone shuts off after showing the boot logo. "Custom" still appears in the logo. I tried a factory reset, per the guide, but that didn't change anything.
Are there any other things I can try?
Thanks
shanebelcroft said:
With Odin I was able to flash a stock OE2 ROM (everything passed) following this guide: https://forum.xda-developers.com/verizon-galaxy-s6/verizon-s6-stock-restore-files-t3096000, but now the phone shuts off after showing the boot logo. "Custom" still appears in the logo. I tried a factory reset, per the guide, but that didn't change anything.
Could the other options in Odin help? Repartition? NAND Erase All?
Thanks
Click to expand...
Click to collapse
What version of Odin are you using? Are you using a version of Odin from around the same time that your device was new to the market? Have you tried using the modified version of Odin that is available here? Have you tried Cosmy's Odin?
Don't use the NAND erase all option, that tends to cause more problems than it solves.
Yes, if you can find a copy of the PIT file for your specific device, you can flash it in the PIT tab in Odin along with the firmware in its slot(s) and select the "repartition" option in Odin while flashing the firmware and the PIT.
You can also try extracting the system.img from the firmware and convert it to an Odin flashable .tar.md5 then flash it in the AP slot. Then power of the device then immediately boot back into download mode and try flashing the entire firmware again.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
What version of Odin are you using? Are you using a version of Odin from around the same time that your device was new to the market? Have you tried using the modified version of Odin that is available here? Have you tried Cosmy's Odin?
Don't use the NAND erase all option, that tends to cause more problems than it solves.
Yes, if you can find a copy of the PIT file for your specific device, you can flash it in the PIT tab in Odin along with the firmware in its slot(s) and select the "repartition" option in Odin while flashing the firmware and the PIT.
You can also try extracting the system.img from the firmware and convert it to an Odin flashable .tar.md5 then flash it in the AP slot. Then power of the device then immediately boot back into download mode and try flashing the entire firmware again.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I've tried both Odin 3.10.6 and Odin3 v3.14.1_3B_PatcheD. Both pass without any issues. I still can't get passed the Samsung logo after flashing the stock OE2 ROM. For what it's worth, even plugging the phone into a charger just brings up the Samsung logo.
What's the reasoning for flashing system.img individually?
shanebelcroft said:
I've tried both Odin 3.10.6 and Odin3 v3.14.1_3B_PatcheD. Both pass without any issues. I still can't get passed the Samsung logo after flashing the stock OE2 ROM. For what it's worth, even plugging the phone into a charger just brings up the Samsung logo.
What's the reasoning for flashing system.img individually?
Click to expand...
Click to collapse
Because flashing the system.img by itself can solve the "custom" status and allow the full firmware to flash.
Did you try flashing your PIT along with the firmware and repartition?
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Because flashing the system.img by itself can solve the "custom" status and allow the full firmware to flash.
Did you try flashing your PIT along with the firmware and repartition?
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestions.
I extracted system.img, remade a tar, and flashed it alone. Still gave the custom logo. I then did a full flash again. No luck.
I tried flashing with the full firmware, with re-partition checked and ZEROFLTE_USA_VZW.pit selected as the pit file (supposedly the pit file for SM-G920V). Still no luck.
If this is an issue with the bootloader, and this being a Verizon phone, I'm probably not going to have much luck, am I?
shanebelcroft said:
Thanks for the suggestions.
I extracted system.img, remade a tar, and flashed it alone. Still gave the custom logo. I then did a full flash again. No luck.
I tried flashing with the full firmware, with re-partition checked and ZEROFLTE_USA_VZW.pit selected as the pit file (supposedly the pit file for SM-G920V). Still no luck.
If this is an issue with the bootloader, and this being a Verizon phone, I'm probably not going to have much luck, am I?
Click to expand...
Click to collapse
As long as your hardware isn't corrupted or damaged, you should be able to restore the device.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
As long as your hardware isn't corrupted or damaged, you should be able to restore the device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I wouldn't be surprised if it's the hardware. The phone is 5 years old. Maybe the battery level reading issue was a symptom of that instead of software or battery problems. Maybe as a last hail Mary, I'll disassemble the device again and make sure all the connectors are really connected. I don't think it's worth buying a new motherboard. Better to buy a new phone, one I can root, anyway.
Thanks for the help!
shanebelcroft said:
I wouldn't be surprised if it's the hardware. The phone is 5 years old. Maybe the battery level reading issue was a symptom of that instead of software or battery problems. Maybe as a last hail Mary, I'll disassemble the device again and make sure all the connectors are really connected. I don't think it's worth buying a new motherboard. Better to buy a new phone, one I can root, anyway.
Thanks for the help!
Click to expand...
Click to collapse
I'd say it is probably worth upgrading anyway, the unlocked unbranded Pixel phones are available for decent prices on Swappa.com. They can be used on Verizon, are easily rooted, currently have plenty of custom development and will continue to get custom development for years to come.
If you like using root and having custom software installed, do NOT get anything that is a Verizon branded device, they lock the bootloader on absolutely everything they offer these days.
Sent from my SM-S767VL using Tapatalk